
From john@jlc.net  Fri Jul  1 04:48:37 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 37E3221F8714 for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 04:48:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[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 Ffy93WhFcg0e for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 04:48:36 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 05BD621F871E for <ietf@ietf.org>; Fri,  1 Jul 2011 04:48:36 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id C6F9133C28; Fri,  1 Jul 2011 07:48:34 -0400 (EDT)
Date: Fri, 1 Jul 2011 07:48:34 -0400
From: John Leslie <john@jlc.net>
To: IETF-Discussion list <ietf@ietf.org>
Subject: SORBS blacklist
Message-ID: <20110701114834.GF52796@verdi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 11:48:37 -0000

   Hey, folks!

   mail.ietf.org[64.170.98.30] got listed on SORBS for spamming.

   It's not that hard to get off... Fix it!

--
John Leslie <john@jlc.net>

From jmh@joelhalpern.com  Fri Jul  1 06:08:04 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 69BB111E82DB; Fri,  1 Jul 2011 06:08:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.588
X-Spam-Level: 
X-Spam-Status: No, score=-102.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NK0fUZFKCo2Y; Fri,  1 Jul 2011 06:08:04 -0700 (PDT)
Received: from hgblob.out.tigertech.net (hgblob.out.tigertech.net [74.114.88.71]) by ietfa.amsl.com (Postfix) with ESMTP id 0ACE211E82F7; Fri,  1 Jul 2011 06:08:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id E5367325B2B9; Fri,  1 Jul 2011 06:07:33 -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 67BC2325B2B7; Fri,  1 Jul 2011 06:07:33 -0700 (PDT)
Message-ID: <4E0DC68F.2060306@joelhalpern.com>
Date: Fri, 01 Jul 2011 09:07:27 -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: IETF discussion list <ietf@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Subject: Review: draft-ietf-mpls-tp-identifiers-06- Tunnel Identifier
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, 01 Jul 2011 13:08:04 -0000

In performing a gen-art review of this document, which seems quite good 
over all, I noticed a minor question, but did not remember to include it 
in my gen-art review.

The defines a Tunnel-Identifier, identifying the end-point of a tunnel 
within a node.
That identifier is defined as 16 bits.
In one sense, that seems sufficient.  But it is more restrictive than 
the number of parallel LSPs that the node could be an end-point for (by 
a factor of 16.)  So it seems that there ought to at least be an 
explanation for the mismatch.

Thank you,
Joel


From moore@network-heretics.com  Fri Jul  1 06:36:35 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 8485011E8148; Fri,  1 Jul 2011 06:36:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.569
X-Spam-Level: 
X-Spam-Status: No, score=-3.569 tagged_above=-999 required=5 tests=[AWL=0.030,  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 oi6MpFJXu2Hr; Fri,  1 Jul 2011 06:36:34 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 5406821F84D7; Fri,  1 Jul 2011 06:36:14 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 5552B20905; Fri,  1 Jul 2011 09:36:12 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Fri, 01 Jul 2011 09:36: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:content-transfer-encoding:message-id:references:to; s=smtpout; bh=qpQfdnE3I93odyBFsVX+LbxFeGs=; b=lUGVFN02KT0lSochgz5ZpIhKBdjHgELi0QT1TSItpDuRMfgJ29blkR+YfktT/xUZuV86O+fdGjB/jlNanGfWhjtAxRlKxrMy5DwPp8Bff3WcTWtVnVlDhJDhQHNWBrkTMrg650AZdsyRCFY43LHJtukQ6BkGyE/CWHP+kLCKV3k=
X-Sasl-enc: i0cKhgjK5+moYNIol8osIEUhU+TVYZyUBERv5RehBeVl 1309527371
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 3E91A40444B; Fri,  1 Jul 2011 09:36:11 -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: <0B6FEF9D-430B-4C56-BB21-40C5ED888B51@townsley.net>
Date: Fri, 1 Jul 2011 09:35:53 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A8AB09DB-AD86-4DB9-8980-53759EB2F1B9@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> <DC5C1553-38E9-4853-9AEA-61FC34FC5EC8@network-heretics.com> <0B6FEF9D-430B-4C56-BB21-40C5ED888B51@townsley.net>
To: Mark Townsley <mark@townsley.net>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Discussion <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 13:36:35 -0000

On Jul 1, 2011, at 4:53 AM, Mark Townsley wrote:

> The idea is not to go out of our way for IPv4, but if the topic is IP =
agnostic anyway, so be it. To be clear, there is no *requirement* to =
support IPv4 here. However, there is no requirement to avoid IPv4 *if* =
it doesn't cause significant concession in the IPv6 design either.
>=20
> This cuts both ways, if there is something that is working well in =
IPv4 that we need to carry over to IPv6 with simple extensions, we'll do =
that and capitalizing on that running-code should be considered a good =
thing. We don't want to invent new v6 protocols from scratch that don't =
work with IPv4 when there is no need. For example (and I think this is =
hinted at in the charter), we might use naming and service discovery =
that already exists for IPv4, adapted the the v6 homenet. This doesn't =
mean we need to re-invent a v6-only naming system from scratch - i'd =
much rather use one that is there, which very well may support v4 and =
v6.=20
>=20
>>=20
>> please don't constrain home networks to work only within the confines =
of IPv4 brain damage.
>=20
> What I think I am saying here is that we will do our best to perform =
as if our brains are not damaged, and equally try to avoid damaging our =
brains in the process.

+1

Keith


From rdroms@cisco.com  Thu Jun 30 09:10:52 2011
Return-Path: <rdroms@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 9954511E8220; Thu, 30 Jun 2011 09:10:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.867
X-Spam-Level: 
X-Spam-Status: No, score=-8.867 tagged_above=-999 required=5 tests=[AWL=-1.732, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rZ+yNzpOEVLA; Thu, 30 Jun 2011 09:10:48 -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 2F17E11E821A; Thu, 30 Jun 2011 09:10:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rdroms@cisco.com; l=941; q=dns/txt; s=iport; t=1309450248; x=1310659848; h=subject:references:content-transfer-encoding:from: in-reply-to:message-id:date:to:cc:mime-version; bh=bMk/E1TDsXlPxJTkXcj6b8wz2UZNv0T/jdC8hjpXTns=; b=lGSFZf0ZySMxw5azPr4ZInL6j5rbfrCASHU8wQJUa79ImDLVdMxDBlt9 +uDhGliKYOT/54S//c/BgmIVByQyvNt/W4Bs1hA7b5x60FKLf3lu0j16R 7Pf+57YN9odm+TaEZo4rfeyS8PtU8G+wybCBRFtK+1kkw2cW4nrhxrORF c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlkGAMyeDE6tJXG9/2dsb2JhbABSpmtpAneIeKFzngGGMQSSL4R/hzuEEA
X-IronPort-AV: E=Sophos;i="4.65,450,1304294400"; d="scan'208";a="724860735"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by sj-iport-6.cisco.com with ESMTP; 30 Jun 2011 16:10:47 +0000
Received: from xbh-rcd-201.cisco.com (xbh-rcd-201.cisco.com [72.163.62.200]) by rcdn-core2-2.cisco.com (8.14.3/8.14.3) with ESMTP id p5UGAljP016732;  Thu, 30 Jun 2011 16:10:47 GMT
Received: from xmb-rcd-202.cisco.com ([72.163.62.209]) by xbh-rcd-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 30 Jun 2011 11:10:46 -0500
Received: from 144.254.231.94 ([144.254.231.94]) by XMB-RCD-202.cisco.com ([72.163.62.209]) with Microsoft Exchange Server HTTP-DAV ;  Thu, 30 Jun 2011 16:10:47 +0000
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> <4E0C9D58.30002@gont.com.ar>
Content-Transfer-Encoding: quoted-printable
thread-topic: [fun] [homegate] HOMENET working group proposal
thread-index: Acw3QEVSasHua7EIRTmly+ZH07zAOQ==
From: "Ralph Droms (rdroms)" <rdroms@cisco.com>
Content-Type: text/plain; charset="us-ascii"
In-Reply-To: <4E0C9D58.30002@gont.com.ar>
Message-ID: <A371107A-2DD1-461F-B37F-BF5D481B05AB@cisco.com>
Date: Thu, 30 Jun 2011 12:11:31 -0400
To: "Fernando Gont" <fernando@gont.com.ar>
MIME-Version: 1.0 (iPad Mail 8J3)
X-OriginalArrivalTime: 30 Jun 2011 16:10:46.0824 (UTC) FILETIME=[455FC280:01CC3740]
X-Mailman-Approved-At: Fri, 01 Jul 2011 08:27:22 -0700
Cc: fun@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, 30 Jun 2011 16:10:52 -0000

"Gone" isn't so important as "not worth expending any more energy on.". So I=
'm with Keith and would like to find some words like "when it doesn't take a=
ny more work."

- Ralph

On Jun 30, 2011, at 12:00 PM, "Fernando Gont" <fernando@gont.com.ar> 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 no=
t 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)
>=20
> Thanks,
> --=20
> Fernando Gont
> e-mail: fernando@gont.com.ar || fgont@acm.org
> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
>=20
>=20
>=20
> _______________________________________________
> fun mailing list
> fun@ietf.org
> https://www.ietf.org/mailman/listinfo/fun

From palm@broadcom.com  Thu Jun 30 09:17:32 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 3E13D11E8229; Thu, 30 Jun 2011 09:17: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=[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 Y8ZRQmqh1xnI; Thu, 30 Jun 2011 09:17:31 -0700 (PDT)
Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by ietfa.amsl.com (Postfix) with ESMTP id A809811E8228; Thu, 30 Jun 2011 09:17:31 -0700 (PDT)
Received: from [10.9.200.131] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Thu, 30 Jun 2011 09:21:59 -0700
X-Server-Uuid: D3C04415-6FA8-4F2C-93C1-920E106A2031
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 09:17:23 -0700
Received: from [10.9.254.251] (unknown [10.9.254.251]) by mail-irva-13.broadcom.com (Postfix) with ESMTP id 933FA74D03; Thu, 30 Jun 2011 09:17:23 -0700 (PDT)
Message-ID: <4E0CA192.1040801@broadcom.com>
Date: Thu, 30 Jun 2011 09:17:22 -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: "Ralph Droms (rdroms)" <rdroms@cisco.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> <4E0C9D58.30002@gont.com.ar> <A371107A-2DD1-461F-B37F-BF5D481B05AB@cisco.com>
In-Reply-To: <A371107A-2DD1-461F-B37F-BF5D481B05AB@cisco.com>
X-WSS-ID: 62127D2D62O16854628-01-01
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 01 Jul 2011 08:27:22 -0700
Cc: Keith Moore <moore@network-heretics.com>, 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 16:17:32 -0000

It is not for "us" to decide when a user's network is not worth expending
any more energy on. They have deployed their network...
and do not want to expend any more energy themselves.  If their SP deploys
IPv6 inelegantly, the user would have a lot of frustration/work.  Which
will generate many expensive tech support calls... and potentially lost customers.

It's not the protocols... it's the DEPLOYED APPLICATIONS and DEVICES that users have.

regards, kiwin

On 6/30/2011 9:11 AM, Ralph Droms (rdroms) wrote:
>
> "Gone" isn't so important as "not worth expending any more energy on.". So I'm with Keith and would like to find some words like "when it doesn't take any more work."
>
> - Ralph
>
> On Jun 30, 2011, at 12:00 PM, "Fernando Gont"<fernando@gont.com.ar>  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.
>>>
>>> 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
>>
>>
>>
>> _______________________________________________
>> fun mailing list
>> fun@ietf.org
>> https://www.ietf.org/mailman/listinfo/fun
> _______________________________________________
> 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 rdroms@cisco.com  Thu Jun 30 09:21:16 2011
Return-Path: <rdroms@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 42DD011E8239; Thu, 30 Jun 2011 09:21:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.002
X-Spam-Level: 
X-Spam-Status: No, score=-8.002 tagged_above=-999 required=5 tests=[AWL=-0.866, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9PTIlDJWfBmo; Thu, 30 Jun 2011 09:21:15 -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 8C9DD11E80D4; Thu, 30 Jun 2011 09:21:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rdroms@cisco.com; l=2480; q=dns/txt; s=iport; t=1309450875; x=1310660475; h=subject:references:content-transfer-encoding:from: in-reply-to:message-id:date:to:cc:mime-version; bh=/YzFBoYDbdtyVhNXYbVadblZkB8sZSySOSL6BylsKg0=; b=mn0C6V3+tx5dnzcm6e8f5rMTh8Bm1uWpKQE0S2YJnhvMWtKeKc3+HtmM aIQVLjIWdmm48dJRaURgtn35BmkaRbuoS9zOlExHd+mF9htbP+tgXRHfM XG530ltTATh0MxeijkV3t+JL8cLvGyE9zER7JqikXNuP8FNwUjYnvEGlo E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlsGAEaiDE6tJV2a/2dsb2JhbABMBqZraQJ3iHihVJ1+gzmCeASSL4R/hzuEEA
X-IronPort-AV: E=Sophos;i="4.65,451,1304294400"; d="scan'208";a="389366045"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by sj-iport-2.cisco.com with ESMTP; 30 Jun 2011 16:20:55 +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 p5UGKtjw016359;  Thu, 30 Jun 2011 16:20:55 GMT
Received: from xmb-rcd-202.cisco.com ([72.163.62.209]) by xbh-rcd-302.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 30 Jun 2011 11:20:54 -0500
Received: from 144.254.231.94 ([144.254.231.94]) by XMB-RCD-202.cisco.com ([72.163.62.209]) with Microsoft Exchange Server HTTP-DAV ;  Thu, 30 Jun 2011 16:20:55 +0000
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> <4E0C9D58.30002@gont.com.ar> <A371107A-2DD1-461F-B37F-BF5D481B05AB@cisco.com> <4E0CA192.1040801@broadcom.com>
Content-Transfer-Encoding: quoted-printable
thread-topic: [fun] [homegate] HOMENET working group proposal
thread-index: Acw3Qa+fE64S74PiSiOlBT71kq/XFw==
From: "Ralph Droms (rdroms)" <rdroms@cisco.com>
Content-Type: text/plain; charset="us-ascii"
In-Reply-To: <4E0CA192.1040801@broadcom.com>
Message-ID: <5289C05E-1105-4427-8459-D86E582BD23C@cisco.com>
Date: Thu, 30 Jun 2011 12:21:37 -0400
To: "Stephen [kiwin] PALM" <palm@broadcom.com>
MIME-Version: 1.0 (iPad Mail 8J3)
X-OriginalArrivalTime: 30 Jun 2011 16:20:54.0718 (UTC) FILETIME=[AFB505E0:01CC3741]
X-Mailman-Approved-At: Fri, 01 Jul 2011 08:27:22 -0700
Cc: Keith Moore <moore@network-heretics.com>, 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 16:21:16 -0000

On Jun 30, 2011, at 12:17 PM, "Stephen [kiwin] PALM" <palm@broadcom.com> wro=
te:

> It is not for "us" to decide when a user's network is not worth expending
> any more energy on. They have deployed their network...
> and do not want to expend any more energy themselves.  If their SP deploys=

> IPv6 inelegantly, the user would have a lot of frustration/work.  Which
> will generate many expensive tech support calls... and potentially lost cu=
stomers.

Agreed that we need to avoid any disruptions of existing networks, devices a=
nd deployment scenarios.  I think we should avoid expending energy on *new* f=
unctions for IPv4.

- Ralph

>=20
> It's not the protocols... it's the DEPLOYED APPLICATIONS and DEVICES that u=
sers have.
>=20
> regards, kiwin
>=20
> On 6/30/2011 9:11 AM, Ralph Droms (rdroms) wrote:
>>=20
>> "Gone" isn't so important as "not worth expending any more energy on.". S=
o I'm with Keith and would like to find some words like "when it doesn't tak=
e any more work."
>>=20
>> - Ralph
>>=20
>> On Jun 30, 2011, at 12:00 PM, "Fernando Gont"<fernando@gont.com.ar>  wrot=
e:
>>=20
>>> 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 n=
ot 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)
>>>=20
>>> Thanks,
>>> --
>>> Fernando Gont
>>> e-mail: fernando@gont.com.ar || fgont@acm.org
>>> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> fun mailing list
>>> fun@ietf.org
>>> https://www.ietf.org/mailman/listinfo/fun
>> _______________________________________________
>> fun mailing list
>> fun@ietf.org
>> https://www.ietf.org/mailman/listinfo/fun
>>=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

From mark@townsley.net  Thu Jun 30 09:34:16 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 2B14E11E8244; Thu, 30 Jun 2011 09:34:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.499
X-Spam-Level: 
X-Spam-Status: No, score=-3.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j72G+ipxciEH; Thu, 30 Jun 2011 09:34:15 -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 1E85711E8085; Thu, 30 Jun 2011 09:34:14 -0700 (PDT)
Received: by wyj26 with SMTP id 26so1915743wyj.31 for <multiple recipients>; Thu, 30 Jun 2011 09:34:14 -0700 (PDT)
Received: by 10.216.237.8 with SMTP id x8mr256345weq.37.1309451653969; Thu, 30 Jun 2011 09:34:13 -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 d7sm1227232wek.21.2011.06.30.09.34.11 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 30 Jun 2011 09:34:12 -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: <0F995E91-9853-4018-91F0-0699E1A7A06F@network-heretics.com>
Date: Thu, 30 Jun 2011 18:33:58 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <780C3063-AD82-46F3-874A-C4E1E61EE508@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> <0F995E91-9853-4018-91F0-0699E1A7A06F@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Fri, 01 Jul 2011 08:27:22 -0700
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:34:16 -0000

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


From mark@townsley.net  Fri Jul  1 01:53:44 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 3A9F721F87AA; Fri,  1 Jul 2011 01:53:44 -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 tM0+oPmkZUNK; Fri,  1 Jul 2011 01:53:43 -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 0965C21F86F4; Fri,  1 Jul 2011 01:53:42 -0700 (PDT)
Received: by wyj26 with SMTP id 26so2373562wyj.31 for <multiple recipients>; Fri, 01 Jul 2011 01:53:41 -0700 (PDT)
Received: by 10.216.132.214 with SMTP id o64mr2564631wei.75.1309510421783; Fri, 01 Jul 2011 01:53:41 -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 u38sm700625weq.37.2011.07.01.01.53.38 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 01 Jul 2011 01:53:39 -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: <DC5C1553-38E9-4853-9AEA-61FC34FC5EC8@network-heretics.com>
Date: Fri, 1 Jul 2011 10:53:37 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0B6FEF9D-430B-4C56-BB21-40C5ED888B51@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> <0F995E91-9853-4018-91F0-0699E1A7A06F@network-heretics.com> <780C3063-AD82-46F3-874A-C4E1E61EE508@townsley.net> <DC5C1553-38E9-4853-9AEA-61FC34FC5EC8@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Fri, 01 Jul 2011 08:27:22 -0700
Cc: IETF Discussion <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 08:53:44 -0000

On Jun 30, 2011, at 6:36 PM, Keith Moore wrote:

> 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.
>=20
> when the group can define something that is useful in IPv6, it =
shouldn't matter whether it's also useful for IPv4.

The idea is not to go out of our way for IPv4, but if the topic is IP =
agnostic anyway, so be it. To be clear, there is no *requirement* to =
support IPv4 here. However, there is no requirement to avoid IPv4 *if* =
it doesn't cause significant concession in the IPv6 design either.

This cuts both ways, if there is something that is working well in IPv4 =
that we need to carry over to IPv6 with simple extensions, we'll do that =
and capitalizing on that running-code should be considered a good thing. =
We don't want to invent new v6 protocols from scratch that don't work =
with IPv4 when there is no need. For example (and I think this is hinted =
at in the charter), we might use naming and service discovery that =
already exists for IPv4, adapted the the v6 homenet. This doesn't mean =
we need to re-invent a v6-only naming system from scratch - i'd much =
rather use one that is there, which very well may support v4 and v6.=20

>=20
> please don't constrain home networks to work only within the confines =
of IPv4 brain damage.

What I think I am saying here is that we will do our best to perform as =
if our brains are not damaged, and equally try to avoid damaging our =
brains in the process.

- Mark

>=20
> Keith
>=20
> _______________________________________________
> homegate mailing list
> homegate@ietf.org
> https://www.ietf.org/mailman/listinfo/homegate


From alexandru.petrescu@gmail.com  Fri Jul  1 08:28:36 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 DA3B99E806B for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 08:28:36 -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 jC3V8BRGTo+O for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 08:28:36 -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 A7CA59E805E for <ietf@ietf.org>; Fri,  1 Jul 2011 08:28:35 -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 p61FSXqJ023378 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 1 Jul 2011 17:28:33 +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 p61FSXsk031842; Fri, 1 Jul 2011 17:28:33 +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 p61FSXPL003077; Fri, 1 Jul 2011 17:28:33 +0200
Message-ID: <4E0DE7A1.10104@gmail.com>
Date: Fri, 01 Jul 2011 17:28:33 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; 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-6man-flow-3697bis-05.txt> (IPv6 Flow Label Specification) to Proposed Standard
References: <20110629225251.13122.14929.idtracker@ietfa.amsl.com>
In-Reply-To: <20110629225251.13122.14929.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 15:28:37 -0000

For text in section 10 "Mobility".

First,

Please cite RFC3963 "NEMOv6" in this section.  I am a co-author.  For 
example, instead of current:
>    Mobile IPv6 [RFC3775] and associated specifications [RFC3776]
>    [RFC4877] allow a node to change its point of attachment within the
>    Internet, while maintaining (and using) a permanent address.

it could be:
>    Mobile IPv6 [RFC3775] and associated specifications [RFC3776] [RFC3963]
>    [RFC4877] allow a node to change its point of attachment within the
>    Internet, while maintaining (and using) a permanent address.

NEMOv6 implementations are widely available as open source (at least on 
linux) and actively maintained since some time.

This is _not_ the case for other mobility-related RFC's which _are_ cited.

Second,

It is strange to read this:
>    The definition of Mobile IP
>    includes requirements for the following types of nodes:
[...]
>       - all IPv6 routers

because there is nothing in Mobile IPv6 which requires modifications of 
all the IPv6 routers.   The Internet infrastructure of routers can 
continue to work as before when deploying Mobile IPv6.

Alex

Le 30/06/2011 00:52, The IESG a écrit :
>
> The IESG has received a request from the IPv6 Maintenance WG (6man) to
> consider the following document:
> - 'IPv6 Flow Label Specification'
>    <draft-ietf-6man-flow-3697bis-05.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-07-13. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     This document specifies the IPv6 Flow Label field and the minimum
>     requirements for IPv6 nodes labeling flows, IPv6 nodes forwarding
>     labeled packets, and flow state establishment methods.  Even when
>     mentioned as examples of possible uses of the flow labeling, more
>     detailed requirements for specific use cases are out of scope for
>     this document.
>
>     The usage of the Flow Label field enables efficient IPv6 flow
>     classification based only on IPv6 main header fields in fixed
>     positions.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-6man-flow-3697bis/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-6man-flow-3697bis/
>
>
> 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
>


From brian.e.carpenter@gmail.com  Fri Jul  1 08:44:12 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 7346111E8078 for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 08:44:12 -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 l1I8aHI4X7tZ for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 08:44:11 -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 DD2579E8088 for <ietf@ietf.org>; Fri,  1 Jul 2011 08:44:10 -0700 (PDT)
Received: by iye7 with SMTP id 7so3653626iye.31 for <ietf@ietf.org>; Fri, 01 Jul 2011 08:44:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=p0lEaZdHv6L2bz+9op6xtsSIysiB6l7A3iQ2jv/oIQw=; b=Lxq/SH3ZV+d/SnK5lGmOr1naVhBIbZZjRHQjzwIxE7A+X6DazkMlaTFb8C9IZdZPV4 UnJoXrmmPSKfjwPm335HHeepiNsGVlJ36GDE+to3jifL1G2jgmiIId97Kj3e5sW1Cc/B HVliTWrMS8da0ga/tABe45zQZ4Wdx3F+5KuqE=
Received: by 10.42.5.148 with SMTP id 20mr1361536icw.167.1309535050305; Fri, 01 Jul 2011 08:44:10 -0700 (PDT)
Received: from [10.255.25.75] (74-95-74-1-Indianapolis.hfc.comcastbusiness.net [74.95.74.1]) by mx.google.com with ESMTPS id hw7sm3456704icc.15.2011.07.01.08.44.08 (version=SSLv3 cipher=OTHER); Fri, 01 Jul 2011 08:44:09 -0700 (PDT)
Message-ID: <4E0DEB3D.1090100@gmail.com>
Date: Sat, 02 Jul 2011 03:43: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: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-flow-3697bis-05.txt> (IPv6 Flow Label Specification) to Proposed Standard
References: <20110629225251.13122.14929.idtracker@ietfa.amsl.com> <4E0DE7A1.10104@gmail.com>
In-Reply-To: <4E0DE7A1.10104@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jul 2011 15:44:12 -0000

Hi Alexandru,

I don't know which draft you are commenting on, but it isn't
draft-ietf-6man-flow-3697bis, which has no discussion of mobility.
Could you please retransmit with the correct Subject header?

Regards
   Brian Carpenter

On 2011-07-02 03:28, Alexandru Petrescu wrote:
> For text in section 10 "Mobility".
>=20
> First,
>=20
> Please cite RFC3963 "NEMOv6" in this section.  I am a co-author.  For
> example, instead of current:
>>    Mobile IPv6 [RFC3775] and associated specifications [RFC3776]
>>    [RFC4877] allow a node to change its point of attachment within the=

>>    Internet, while maintaining (and using) a permanent address.
>=20
> it could be:
>>    Mobile IPv6 [RFC3775] and associated specifications [RFC3776]
>> [RFC3963]
>>    [RFC4877] allow a node to change its point of attachment within the=

>>    Internet, while maintaining (and using) a permanent address.
>=20
> NEMOv6 implementations are widely available as open source (at least on=

> linux) and actively maintained since some time.
>=20
> This is _not_ the case for other mobility-related RFC's which _are_ cit=
ed.
>=20
> Second,
>=20
> It is strange to read this:
>>    The definition of Mobile IP
>>    includes requirements for the following types of nodes:
> [...]
>>       - all IPv6 routers
>=20
> because there is nothing in Mobile IPv6 which requires modifications of=

> all the IPv6 routers.   The Internet infrastructure of routers can
> continue to work as before when deploying Mobile IPv6.
>=20
> Alex
>=20
> Le 30/06/2011 00:52, The IESG a =C3=A9crit :
>>
>> The IESG has received a request from the IPv6 Maintenance WG (6man) to=

>> consider the following document:
>> - 'IPv6 Flow Label Specification'
>>    <draft-ietf-6man-flow-3697bis-05.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-07-13. Exceptionally, comments may=
 be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>
>>     This document specifies the IPv6 Flow Label field and the minimum
>>     requirements for IPv6 nodes labeling flows, IPv6 nodes forwarding
>>     labeled packets, and flow state establishment methods.  Even when
>>     mentioned as examples of possible uses of the flow labeling, more
>>     detailed requirements for specific use cases are out of scope for
>>     this document.
>>
>>     The usage of the Flow Label field enables efficient IPv6 flow
>>     classification based only on IPv6 main header fields in fixed
>>     positions.
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-6man-flow-3697bis/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-6man-flow-3697bis/
>>
>>
>> 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
>>
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From paul.hoffman@vpnc.org  Fri Jul  1 09:09:44 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 90FA821F8698 for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 09:09:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.69
X-Spam-Level: 
X-Spam-Status: No, score=-102.69 tagged_above=-999 required=5 tests=[AWL=-0.091, 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 O94u3ZOg3Bbw for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 09:09:43 -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 2765B21F8696 for <ietf@ietf.org>; Fri,  1 Jul 2011 09:09:29 -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 p61G9HWf052775 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 1 Jul 2011 09:09:17 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: SORBS blacklist
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: <20110701114834.GF52796@verdi>
Date: Fri, 1 Jul 2011 09:09:22 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <397A4E66-2F31-4D71-B0CE-4A466654002D@vpnc.org>
References: <20110701114834.GF52796@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, 01 Jul 2011 16:09:44 -0000

On Jul 1, 2011, at 4:48 AM, John Leslie wrote:

>   Hey, folks!
> 
>   mail.ietf.org[64.170.98.30] got listed on SORBS for spamming.
> 
>   It's not that hard to get off... Fix it!


It's also not that hard not to use poorly-managed blacklists. Just sayin'....

--Paul Hoffman


From glen@amsl.com  Fri Jul  1 09:42:09 2011
Return-Path: <glen@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 703491F0C60 for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 09:42:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.373
X-Spam-Level: 
X-Spam-Status: No, score=-105.373 tagged_above=-999 required=5 tests=[AWL=-0.786, BAYES_00=-2.599, FAKE_REPLY_C=2.012, 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 eoacih5R2BHB for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 09:42:08 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by ietfa.amsl.com (Postfix) with ESMTP id EBC471F0C4C for <ietf@ietf.org>; Fri,  1 Jul 2011 09:42:08 -0700 (PDT)
Received: by c1a.amsl.com (Postfix, from userid 1000) id E4B0D1C38512; Fri,  1 Jul 2011 09:42:08 -0700 (PDT)
Date: Fri, 1 Jul 2011 09:42:08 -0700
From: Glen <glen@amsl.com>
To: ietf@ietf.org
Subject: Re: SORBS blacklist
Message-ID: <20110701164208.GA2481@amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.17 (2007-11-01)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 16:42:09 -0000

On Jul 1, 2011, at 4:48 AM, John Leslie wrote:                                  
>   Hey, folks!                                                                 
>                                                                               
>   mail.ietf.org[64.170.98.30] got listed on SORBS for spamming.               
>                                                                               
>   It's not that hard to get off... Fix it!                                    
                                                                                And just a reminder to all that the "folks" who do the fixing of these 
things can be reached at:

	ietf-action@ietf.org

We encourage everyone to report known problems there, rather than to this
list, which the action team does not generally monitor.

More details about this can be seen at: http://www.ietf.org/secretariat.html

Thanks! :-)

Glen
Glen Barney
IT Director
AMS (IETF Secretariat)


From dwm@xpasc.com  Fri Jul  1 09:46:49 2011
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D40AD1F0C64 for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 09:46:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.307
X-Spam-Level: 
X-Spam-Status: No, score=-1.307 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sk+ywoJNARn6 for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 09:46:49 -0700 (PDT)
Received: from mail.xpasc.com (mail.xpasc.com [68.164.244.189]) by ietfa.amsl.com (Postfix) with ESMTP id 720811F0C41 for <ietf@ietf.org>; Fri,  1 Jul 2011 09:46:49 -0700 (PDT)
Received: from bslepgate.xpasc.com (localhost.localdomain [127.0.0.1]) by bslepgate.xpasc.com (Postfix-out) with ESMTP id 9B8FB101842 for <ietf@ietf.org>; Fri,  1 Jul 2011 09:46:45 -0700 (PDT)
X-Propel-Return-Path: <dwm@xpasc.com>
Received: from mail.xpasc.com ([10.1.2.88]) by [127.0.0.1] ([127.0.0.1]) (port 7027) (Abaca EPG outproxy filter 3.1.2.exported $Rev: 9262 $) id iz6Urb71gKJ0; Fri, 01 Jul 2011 09:46:45 -0700
Received: from xpasc.com (egate.xpasc.com [10.1.2.49]) by bslepgate.xpasc.com (Postfix-out) with ESMTP id 7846A101841 for <ietf@ietf.org>; Fri,  1 Jul 2011 09:46:45 -0700 (PDT)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id p61Gkjxl019107 for <ietf@ietf.org>; Fri, 1 Jul 2011 09:46:45 -0700
Date: Fri, 1 Jul 2011 09:46:45 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: IETF-Discussion list <ietf@ietf.org>
Subject: Re: SORBS blacklist
In-Reply-To: <397A4E66-2F31-4D71-B0CE-4A466654002D@vpnc.org>
Message-ID: <Pine.LNX.4.64.1107010943410.16238@egate.xpasc.com>
References: <20110701114834.GF52796@verdi> <397A4E66-2F31-4D71-B0CE-4A466654002D@vpnc.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Propel-ID: iz6Urb71gKJ0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 16:46:50 -0000

On Fri, 1 Jul 2011, Paul Hoffman wrote:

> On Jul 1, 2011, at 4:48 AM, John Leslie wrote:
> 
> >   Hey, folks!
> > 
> >   mail.ietf.org[64.170.98.30] got listed on SORBS for spamming.
> > 
> >   It's not that hard to get off... Fix it!
> 
> 
> It's also not that hard not to use poorly-managed blacklists. Just sayin'....

And from my own experience, I know it can be impossible to get removed
from SORBS if you are a small business subject to the whims of their
ISPs. AFAIK, no spam has ever originated from my networks but SORBS didn't
like something about my network addresses. I tried jumping through their 
hoops but it was impossible.

From john@jlc.net  Fri Jul  1 09:59:13 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 8D9BB1F0CA8 for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 09:59:13 -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 IkafyTF6jZDh for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 09:59:13 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id AD18D1F0CA9 for <ietf@ietf.org>; Fri,  1 Jul 2011 09:59:12 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 7DF2233C24; Fri,  1 Jul 2011 12:59:12 -0400 (EDT)
Date: Fri, 1 Jul 2011 12:59:12 -0400
From: John Leslie <john@jlc.net>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: SORBS blacklist
Message-ID: <20110701165912.GK52796@verdi>
References: <20110701114834.GF52796@verdi> <397A4E66-2F31-4D71-B0CE-4A466654002D@vpnc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <397A4E66-2F31-4D71-B0CE-4A466654002D@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, 01 Jul 2011 16:59:13 -0000

Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> On Jul 1, 2011, at 4:48 AM, John Leslie wrote:
> 
>> mail.ietf.org[64.170.98.30] got listed on SORBS for spamming.
>> 
>> It's not that hard to get off... Fix it!
> 
> 
> It's also not that hard not to use poorly-managed blacklists. Just sayin'....

   I'm _really_ poor at flame-wars, but Paul is begging here...

   It's exceptionally hard for folks to avoid poorly-managed blacklists
when the incoming-email setup isn't under their control. (Not true for
me, of course, nor for my customers if they think to ask.)

   IMHO, it's entirely reasonable to use even poorly-managed blacklists
as input to spam-assassin. And it's not up to _you_ to say what the
scoring algorithm should be for one of my customers.

   Also, it's really not rocket-science to log the 550 replies to
mailing-list distribution attempts: these _will_ accumulate quickly
if something the size of mail.ietf.org gets on a blacklist (poorly-
managed or otherwise).

   The state-of-the-art in spam-abatement is far short of what it
should be. Folks who receive 100 spams per day tend to ask for more
aggressive spam-abatement, and it's not good business to refuse.

   Also, poorly-managed is in the eye of the beholder. sorbs.net is
among the mainstream, alas; and while _I_ won't argue whether they're
well-managed, there are plenty of folks who will.

   I recommend against blanket "blame-the-receiver" policies. I have
customers that have received over 6,000 spams per day when I turned
off "all" spam-abatement for them: that's far beyond reasonable
"blame-the-receiver" territory. They _must_ do something, and I'm
not going to criticize what they do.

   Please, everyone, understand that recipients _can't_ do the whole
job on spam-abatement. Folks running mailing-lists for organizations
like the IETF need to do their part, and are in a better position
than some of my customers to bear the cost.

   (BTW, I did get a ticket in the system _well_ before my posting
here. I won't quote the reply; but I think it would be helpful for
the folks who process such tickets to post on this thread.)

--
John Leslie <john@jlc.net>

From john@jlc.net  Fri Jul  1 10:08:22 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 A35951F0C79 for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 10:08:22 -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 atPUKORuu6Sc for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 10:08:22 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 291FC1F0C58 for <ietf@ietf.org>; Fri,  1 Jul 2011 10:08:22 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 1113633C24; Fri,  1 Jul 2011 13:08:22 -0400 (EDT)
Date: Fri, 1 Jul 2011 13:08:22 -0400
From: John Leslie <john@jlc.net>
To: David Morris <dwm@xpasc.com>
Subject: Re: SORBS blacklist
Message-ID: <20110701170821.GL52796@verdi>
References: <20110701114834.GF52796@verdi> <397A4E66-2F31-4D71-B0CE-4A466654002D@vpnc.org> <Pine.LNX.4.64.1107010943410.16238@egate.xpasc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.64.1107010943410.16238@egate.xpasc.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, 01 Jul 2011 17:08:22 -0000

David Morris <dwm@xpasc.com> wrote:
>> On Jul 1, 2011, at 4:48 AM, John Leslie wrote:
>>  
>>> mail.ietf.org[64.170.98.30] got listed on SORBS for spamming.
>>> 
>>> It's not that hard to get off... Fix it!
>>... 
> 
> And from my own experience, I know it can be impossible to get removed
> from SORBS if you are a small business subject to the whims of their
> ISPs. AFAIK, no spam has ever originated from my networks but SORBS didn't
> like something about my network addresses. I tried jumping through their 
> hoops but it was impossible.

   A reasonable contribution to this discussion. Indeed, a number of
folks have complained similarly.

   Alas, that's not enough for me to refuse to use SORBS for my customers
who ask for it. (I hear other reports of success at getting removed --
in particular, I have been told that mail.ietf.org has succeeded.)

   But my actual reply is to repeat that receivers can't bear the entire
cost of weaknesses in spam-abatement. If you wish to run a serious
mailing-list operation, you need to do your part.

   (BTW, I've never had trouble "fixing" blacklisting here -- but I do
change IP addresses if the "response" isn't fast enough...)

--
John Leslie <john@jlc.net>

From joelja@bogus.com  Fri Jul  1 10:10: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 EBAE721F86CD for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 10:10:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NJbjiKsbbkWt for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 10:10:28 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 5959721F86B2 for <ietf@ietf.org>; Fri,  1 Jul 2011 10:10:28 -0700 (PDT)
Received: from [192.168.11.127] (c-76-115-172-69.hsd1.wa.comcast.net [76.115.172.69]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p61HAQcx086811 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 1 Jul 2011 17:10:26 GMT (envelope-from joelja@bogus.com)
Subject: Re: SORBS blacklist
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <20110701165912.GK52796@verdi>
Date: Fri, 1 Jul 2011 10:10:21 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <44C0302E-4CD1-46E5-8C50-5FA875426F2E@bogus.com>
References: <20110701114834.GF52796@verdi> <397A4E66-2F31-4D71-B0CE-4A466654002D@vpnc.org> <20110701165912.GK52796@verdi>
To: John Leslie <john@jlc.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]); Fri, 01 Jul 2011 17:10:27 +0000 (UTC)
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, 01 Jul 2011 17:10:29 -0000

On Jul 1, 2011, at 9:59 AM, John Leslie wrote:

>   Please, everyone, understand that recipients _can't_ do the whole
> job on spam-abatement. Folks running mailing-lists for organizations
> like the IETF need to do their part, and are in a better position
> than some of my customers to bear the cost.

the ietf has some of the more heavily and consistently moderated mailing =
lists on the planet. the notion that we're not doing our part or that =
the ietf lists are a source or relay for spam is patently false.

joel

>   (BTW, I did get a ticket in the system _well_ before my posting
> here. I won't quote the reply; but I think it would be helpful for
> the folks who process such tickets to post on this thread.)
>=20
> --
> John Leslie <john@jlc.net>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From Kurt.Zeilenga@Isode.COM  Fri Jul  1 10:39:21 2011
Return-Path: <Kurt.Zeilenga@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 810EA1F0C53 for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 10:39:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.774
X-Spam-Level: 
X-Spam-Status: No, score=-102.774 tagged_above=-999 required=5 tests=[AWL=-0.175, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 395wOU31eaJN for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 10:39:20 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 302CC1F0C40 for <ietf@ietf.org>; Fri,  1 Jul 2011 10:39:20 -0700 (PDT)
Received: from [192.168.42.5] (75-141-240-242.dhcp.reno.nv.charter.com [75.141.240.242])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <Tg4GQwB=gDfg@rufus.isode.com>; Fri, 1 Jul 2011 18:39:17 +0100
Subject: Re: SORBS blacklist
From: Kurt Zeilenga <Kurt.Zeilenga@Isode.COM>
In-Reply-To: <44C0302E-4CD1-46E5-8C50-5FA875426F2E@bogus.com>
Date: Fri, 1 Jul 2011 10:39:13 -0700
Message-Id: <BEB2FFFB-5B31-4448-BE7E-C0225CBC1D9A@Isode.COM>
References: <20110701114834.GF52796@verdi> <397A4E66-2F31-4D71-B0CE-4A466654002D@vpnc.org> <20110701165912.GK52796@verdi> <44C0302E-4CD1-46E5-8C50-5FA875426F2E@bogus.com>
To: Joel Jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1242)
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: IETF-Discussion list <ietf@ietf.org>, John Leslie <john@jlc.net>, 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, 01 Jul 2011 17:39:21 -0000

On Jul 1, 2011, at 10:10 AM, Joel Jaeggli wrote:

> the ietf has some of the more heavily and consistently moderated =
mailing lists on the planet.

but how well does the IETF do in not producing email in response to =
SPAM?   Seems the IETF generates a lot of backscatter, and aside from =
scattering this to individual boxes all over the Internet, it's going to =
scatter into various spam traps=85 and that's likely to cause a listing =
in any services that use spam traps.  Those who implement spam traps do =
put filters on them, so that commonly produced bounces don't cause =
listing, but it's had to deal with the many custom bounce messages =
(especially ones which don't use standard headers to indicate they are =
auto-generated).

Has anyone examined all the various sorts of auto-generated messages the =
IETF produces to make sure they are reasonably detected as =
auto-generated messages?

That should be part of us doing our part to help deal with SPAM.

-- Kurt=

From paul.hoffman@vpnc.org  Fri Jul  1 10:58:13 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 42CD711E8085 for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 10:58:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.682
X-Spam-Level: 
X-Spam-Status: No, score=-102.682 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g4Caas32o3Gm for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 10:58:12 -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 C7FB811E8076 for <ietf@ietf.org>; Fri,  1 Jul 2011 10:58:11 -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 p61Hw42W057407 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 1 Jul 2011 10:58:04 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: SORBS blacklist
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: <20110701165912.GK52796@verdi>
Date: Fri, 1 Jul 2011 10:58:09 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <22C6ACF4-F6BC-4A2C-9216-AB17BF0DBFC4@vpnc.org>
References: <20110701114834.GF52796@verdi> <397A4E66-2F31-4D71-B0CE-4A466654002D@vpnc.org> <20110701165912.GK52796@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, 01 Jul 2011 17:58:13 -0000

On Jul 1, 2011, at 9:59 AM, John Leslie wrote:

>   I'm _really_ poor at flame-wars, but Paul is begging here...

Actually, no I wasn't. People in the email world who know me know that I =
leave flamewars about spam before they even flicker.

What I am questioning is the notion that the IETF should spend money =
trying to avoid damage being done by popular but poorly-run services of =
any type. We could be having this argument about the IETF web site and a =
browser that will put up a warning if the HTML on a page is not fully =
compliant. I think you and I simply disagree on where it is useful to =
put IETF resources.

>   Please, everyone, understand that recipients _can't_ do the whole
> job on spam-abatement.

No one said they should. There is a huge difference between "recipients =
must do the whole job" and "recipients who choose poor tools should not =
expect the rest of the internet to try to work with their poor choices". =
It really is OK for us to say "there are better choices out there".

--Paul Hoffman


From joelja@bogus.com  Fri Jul  1 11:04:25 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 175A111E809E for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 11:04:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l4Tz6McCa-Uq for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 11:04:24 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id C6C6E11E8078 for <ietf@ietf.org>; Fri,  1 Jul 2011 11:04:23 -0700 (PDT)
Received: from [192.168.11.127] (c-76-115-172-69.hsd1.wa.comcast.net [76.115.172.69]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p61I4LoA087941 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 1 Jul 2011 18:04:21 GMT (envelope-from joelja@bogus.com)
Subject: Re: SORBS blacklist
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=windows-1252
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <BEB2FFFB-5B31-4448-BE7E-C0225CBC1D9A@Isode.COM>
Date: Fri, 1 Jul 2011 11:04:15 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <BDF14B5F-BAFE-4E64-91E4-CE4049CA1428@bogus.com>
References: <20110701114834.GF52796@verdi> <397A4E66-2F31-4D71-B0CE-4A466654002D@vpnc.org> <20110701165912.GK52796@verdi> <44C0302E-4CD1-46E5-8C50-5FA875426F2E@bogus.com> <BEB2FFFB-5B31-4448-BE7E-C0225CBC1D9A@Isode.COM>
To: Kurt Zeilenga <Kurt.Zeilenga@Isode.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, 01 Jul 2011 18:04:22 +0000 (UTC)
Cc: IETF-Discussion list <ietf@ietf.org>, John Leslie <john@jlc.net>, 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, 01 Jul 2011 18:04:25 -0000

On Jul 1, 2011, at 10:39 AM, Kurt Zeilenga wrote:

>=20
> On Jul 1, 2011, at 10:10 AM, Joel Jaeggli wrote:
>=20
>> the ietf has some of the more heavily and consistently moderated =
mailing lists on the planet.
>=20
> but how well does the IETF do in not producing email in response to =
SPAM?   Seems the IETF generates a lot of backscatter, and aside from =
scattering this to individual boxes all over the Internet, it's going to =
scatter into various spam traps=85 and that's likely to cause a listing =
in any services that use spam traps.  Those who implement spam traps do =
put filters on them, so that commonly produced bounces don't cause =
listing, but it's had to deal with the many custom bounce messages =
(especially ones which don't use standard headers to indicate they are =
auto-generated).
>=20
> Has anyone examined all the various sorts of auto-generated messages =
the IETF produces to make sure they are reasonably detected as =
auto-generated messages?
>=20
> That should be part of us doing our part to help deal with SPAM.

I watch all the bounces for about half a dozen of  the high traffic =
lists.

One of the more annoying things I see is bounces from subscribed members =
due to the sender being listed somewhere. when this happens with =
frequency those particapants that bounce messages to mailman get ejects =
from the list... We don't have the luxury of just ejecting someone from =
list because the source ip they are using today is listed in spamhaus =
but if you recject enough mail from us you're going to fall off.

Honestly I think the backscatter is frankly rather low as a purportion =
of net volume but the volume is large.

A busy day on the ietf discuss list bursts out to a few hundred thousand =
messages however, for a single list.

> -- Kurt
>=20


From mrex@sap.com  Fri Jul  1 11:08:53 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 D8D891F0C3F for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 11:08:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.135
X-Spam-Level: 
X-Spam-Status: No, score=-10.135 tagged_above=-999 required=5 tests=[AWL=0.114, 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 z4fX3ucV91jR for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 11:08:53 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id B4D7511E8114 for <ietf@ietf.org>; Fri,  1 Jul 2011 11:07:29 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p61I7Oot010515 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 1 Jul 2011 20:07:25 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201107011807.p61I7O4X018846@fs4113.wdf.sap.corp>
Subject: Re: HOMENET working group proposal
To: jhw@apple.com (james woodyatt)
Date: Fri, 1 Jul 2011 20:07:24 +0200 (MEST)
In-Reply-To: <2EDF9C8B-FBDA-411E-840C-2AE0831AEF21@apple.com> from "james woodyatt" at Jun 30, 11 05:09:40 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, 01 Jul 2011 18:08:54 -0000

james woodyatt wrote:
>
>                                     There is nothing about NAT or
> dynamic subscriber IP assignment that provides any mitigation
> whatsoever of the risks

I'm more than a little concerned by the message that you're sending
here.  European legislators have enacted a "E-Privacy Directive"
also dubbed "European Cookie Directive" in order to protect the
privacy of citizens, and you're suggesting here that the IETF
should actively subvert this legislation and similar ongoing
legislative initiatives in the US by assigning static IPv6
addresses to home DSL subscribers so that cookies are completely
obviated and everyone can be trivially tracked based on his
static IP-Address.  This means you want to make IPv6 addresses
and all communications with that address direct personally
identifiable information, something for which a "must informed
beforehand", let alone an "opt opt" is technically impossible?


james woodyatt wrote:
> 
> 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.

That regime where this happened was the US.  So you're declaring
the entire US out-of-scope and the entire European Union out-of-scope?

I was under the impression we were talking about _the_Internet_
for which the IETF is usually producing standards and technology,
and seem to have confused this with your discussion about matters
of some other network somewhere, that happend to got redistributed
by the IETF mailing list exploder only by accident.


-Martin


From moore@network-heretics.com  Fri Jul  1 11:31: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 74F8111E8126; Fri,  1 Jul 2011 11:31:57 -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 Op0VQuAdkVHM; Fri,  1 Jul 2011 11:31:56 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 73BA911E8128; Fri,  1 Jul 2011 11:31:18 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 25FD320976; Fri,  1 Jul 2011 14:31:18 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Fri, 01 Jul 2011 14:31:18 -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=vizbAscX1JZsrvh8qXkP9afekLc=; b=AXf7b7DTSkzF9Klow/mf2xAmj2I5OPLmd8z+nmkhZJCzDebsVWyEo6RA34ZPLaIg2UL8HzPNswbRdioH33jWY0VE2ycxk/6Cl/Gr+2NkWtcfCnLbbL05VeTsQk/+NW0+4qNLiTb2RIaABcxD7IQyxZST9VIOG6CK7pV7T/1WJIs=
X-Sasl-enc: ZdXZ+RdhyiwIO3rTQFOYDi5/ezfTTrS2oc4IYoqkVnDW 1309545077
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 CDC94405EAA; Fri,  1 Jul 2011 14:31:16 -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: <4E0CA192.1040801@broadcom.com>
Date: Fri, 1 Jul 2011 14:30:58 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <75CB375A-C9AD-4FE9-9D37-08EBFCA9A0AB@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> <A371107A-2DD1-461F-B37F-BF5D481B05AB@cisco.com> <4E0CA192.1040801@broadcom.com>
To: Stephen [kiwin] PALM <palm@broadcom.com>
X-Mailer: Apple Mail (2.1084)
Cc: "fun@ietf.org" <fun@ietf.org>, IETF Discussion <ietf@ietf.org>, "Ralph Droms \(rdroms\)" <rdroms@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jul 2011 18:31:57 -0000

Anytime we develop standards, the standards apply to future products.  =
There's no point in defining standards for applications and devices that =
are already deployed.

Sure, it's nice to have backward compatibility.  But I don't think =
anyone is likely to propose standards for HOMENET that will =
significantly break compatibility with existing products.  It's not as =
if the set of applications and devices that one uses in a home network =
is disjoint from the set of applications and devices used in other =
networks.   And it's reasonable to expect that users of existing =
applications and devices might need to do some special-case =
configuration to get those applications and devices to continue to work. =
=20

Just to pick one example, if a legacy device is v4-only, and the only =
access available is NATted v4 or native v6, there might be a need to =
configure the device to be externally accessible using a v6 address.  =
The home network might support v4 internally but there might not be v4 =
service available outside that enclave.

Backward compatibility =3D good.  Insisting that home networks always =
use the same kludges that are used now =3D bad.

Maybe the right answer is that the HOMENET group should consider what =
means are needed to provide some measure of compatibility with legacy =
devices and applications, that might continue to be used with networks =
meeting the new standards.  The working group seems like it's in a much =
better position than the IETF list to propose reasonable compromises on =
these issues.

Keith


On Jun 30, 2011, at 12:17 PM, Stephen [kiwin] PALM wrote:

> It is not for "us" to decide when a user's network is not worth =
expending
> any more energy on. They have deployed their network...
> and do not want to expend any more energy themselves.  If their SP =
deploys
> IPv6 inelegantly, the user would have a lot of frustration/work.  =
Which
> will generate many expensive tech support calls... and potentially =
lost customers.
>=20
> It's not the protocols... it's the DEPLOYED APPLICATIONS and DEVICES =
that users have.
>=20
> regards, kiwin
>=20
> On 6/30/2011 9:11 AM, Ralph Droms (rdroms) wrote:
>>=20
>> "Gone" isn't so important as "not worth expending any more energy =
on.". So I'm with Keith and would like to find some words like "when it =
doesn't take any more work."
>>=20
>> - Ralph
>>=20
>> On Jun 30, 2011, at 12:00 PM, "Fernando Gont"<fernando@gont.com.ar>  =
wrote:
>>=20
>>> 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)
>>>=20
>>> Thanks,
>>> --
>>> Fernando Gont
>>> e-mail: fernando@gont.com.ar || fgont@acm.org
>>> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> fun mailing list
>>> fun@ietf.org
>>> https://www.ietf.org/mailman/listinfo/fun
>> _______________________________________________
>> fun mailing list
>> fun@ietf.org
>> https://www.ietf.org/mailman/listinfo/fun
>>=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
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From moore@network-heretics.com  Fri Jul  1 11:33: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 95F1D11E8141 for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 11:33:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.553
X-Spam-Level: 
X-Spam-Status: No, score=-3.553 tagged_above=-999 required=5 tests=[AWL=0.046,  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 wpWR+YMsyE4p for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 11:33:50 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 1602C11E813F for <ietf@ietf.org>; Fri,  1 Jul 2011 11:33:50 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id BFF31208DB; Fri,  1 Jul 2011 14:33:49 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 01 Jul 2011 14:33: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=hZLIpoSG/P02H52ma2vbeDd1wwg=; b=G2HYyHaRvX/KfMYCTOa+XXdd8ZE9Dko8WX0knA2dHoGSKAH3+OSN1x9fui8XpOKvvLN1vVvVCGb8snuCQq6ZNrf4zZetRLx0ICceuy8y8kFaswg7gmYtbHu7wkqW50wEMElHJwv8Kt4oji3IridJpT80fOD+4W9Kgsu0QTPH86M=
X-Sasl-enc: 9nxET+kx9KvLiU7ty08JAfzzqI8MC/ChqW+cLJDmKSuf 1309545229
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 DA15940BAE8; Fri,  1 Jul 2011 14:33:48 -0400 (EDT)
Subject: Re: SORBS blacklist
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: <20110701165912.GK52796@verdi>
Date: Fri, 1 Jul 2011 14:33:30 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2513461B-AAE2-44A5-9A9A-A1F7A4D3E2D1@network-heretics.com>
References: <20110701114834.GF52796@verdi> <397A4E66-2F31-4D71-B0CE-4A466654002D@vpnc.org> <20110701165912.GK52796@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, 01 Jul 2011 18:33:50 -0000

On Jul 1, 2011, at 12:59 PM, John Leslie wrote:

> Paul Hoffman <paul.hoffman@vpnc.org> wrote:
>> On Jul 1, 2011, at 4:48 AM, John Leslie wrote:
>>=20
>>> mail.ietf.org[64.170.98.30] got listed on SORBS for spamming.
>>>=20
>>> It's not that hard to get off... Fix it!
>>=20
>>=20
>> It's also not that hard not to use poorly-managed blacklists. Just =
sayin'....
>=20
>   I'm _really_ poor at flame-wars, but Paul is begging here...
>=20
>   It's exceptionally hard for folks to avoid poorly-managed blacklists
> when the incoming-email setup isn't under their control. (Not true for
> me, of course, nor for my customers if they think to ask.)
>=20
>   IMHO, it's entirely reasonable to use even poorly-managed blacklists
> as input to spam-assassin. And it's not up to _you_ to say what the
> scoring algorithm should be for one of my customers.

blacklists are the email version of terrorism, holding people's email =
service hostage in exchange for arbitrary tribute.

Keith


From joelja@bogus.com  Fri Jul  1 11:34:42 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 C432A11E813A for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 11:34:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7QwNboC4bIbI for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 11:34:41 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 48AFC11E8135 for <ietf@ietf.org>; Fri,  1 Jul 2011 11:34:36 -0700 (PDT)
Received: from [192.168.11.127] (c-76-115-172-69.hsd1.wa.comcast.net [76.115.172.69]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p61IYQnR088557 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 1 Jul 2011 18:34:26 GMT (envelope-from joelja@bogus.com)
Subject: Re: HOMENET working group proposal
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <201107011807.p61I7O4X018846@fs4113.wdf.sap.corp>
Date: Fri, 1 Jul 2011 11:34:21 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <57873F86-D06C-4C9E-AD2A-49AA739C90D3@bogus.com>
References: <201107011807.p61I7O4X018846@fs4113.wdf.sap.corp>
To: mrex@sap.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, 01 Jul 2011 18:34:27 +0000 (UTC)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jul 2011 18:34:42 -0000

On Jul 1, 2011, at 11:07 AM, Martin Rex wrote:
> james woodyatt wrote:
>>=20
>>                                    There is nothing about NAT or
>> dynamic subscriber IP assignment that provides any mitigation
>> whatsoever of the risks
>=20
> I'm more than a little concerned by the message that you're sending
> here.  European legislators have enacted a "E-Privacy Directive"
> also dubbed "European Cookie Directive" in order to protect the
> privacy of citizens, and you're suggesting here that the IETF
> should actively subvert this legislation and similar ongoing
> legislative initiatives in the US by assigning static IPv6
> addresses to home DSL subscribers so that cookies are completely
> obviated and everyone can be trivially tracked based on his
> static IP-Address.  This means you want to make IPv6 addresses
> and all communications with that address direct personally
> identifiable information, something for which a "must informed
> beforehand", let alone an "opt opt" is technically impossible?

The IETF has several times veered away from the deep water where =
internet standards cross paths with regulatory requirements.

http://tools.ietf.org/html/rfc2804
=20
We are not legal experts we are not qualified to interpret the statutory =
requirements of various nation states, our own or others. We need to be =
clear on what is in vs out of scope for IETF work. Focus on what would =
be percieved to be in the best interests the users and the network. =
Nation states will do whatever they do and sovereign by definition can =
impose whatever mandate they find necessary on their network operations =
and citizens.=

From johnl@iecc.com  Fri Jul  1 11:37:34 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 C36BD22800E for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 11:37:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.661
X-Spam-Level: 
X-Spam-Status: No, score=-110.661 tagged_above=-999 required=5 tests=[AWL=0.538, 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 oNJwdudMP0sd for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 11:37:34 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 3CE6A21F8662 for <ietf@ietf.org>; Fri,  1 Jul 2011 11:37:15 -0700 (PDT)
Received: (qmail 37291 invoked from network); 1 Jul 2011 18:37:11 -0000
Received: from gal.iecc.com (64.57.183.53) by mail2.iecc.com with SMTP; 1 Jul 2011 18:37:11 -0000
Received: (qmail 14428 invoked from network); 1 Jul 2011 18:37:11 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 1 Jul 2011 18:37:11 -0000
Date: 1 Jul 2011 18:36:49 -0000
Message-ID: <20110701183649.56719.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: SORBS blacklist
In-Reply-To: <20110701170821.GL52796@verdi>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: 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: Fri, 01 Jul 2011 18:37:34 -0000

> Alas, that's not enough for me to refuse to use SORBS for my
> customers who ask for it.

There are a few blacklists that are well enough run to be worth
expending effort to find out why you're listed and get removed.  SORBS
used to be one of those lists, but hasn't been at least since Michelle
sold it.

If your customers want to use SORBS, and as a consequence reject mail
from the IETF that they want to receive, that is their problem, not
the IETF's.

R's,
John

From joelja@bogus.com  Fri Jul  1 11:38:48 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 54FAA22800D for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 11:38: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=[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 5rn-M6Ohpu4h for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 11:38:48 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id EC7B8228006 for <ietf@ietf.org>; Fri,  1 Jul 2011 11:38:45 -0700 (PDT)
Received: from [192.168.11.127] (c-76-115-172-69.hsd1.wa.comcast.net [76.115.172.69]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p61IcgQx088675 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 1 Jul 2011 18:38:43 GMT (envelope-from joelja@bogus.com)
Subject: Re: SORBS blacklist
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <2513461B-AAE2-44A5-9A9A-A1F7A4D3E2D1@network-heretics.com>
Date: Fri, 1 Jul 2011 11:38:37 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <42B72449-866B-4C2D-B2DD-1F012F0E260B@bogus.com>
References: <20110701114834.GF52796@verdi> <397A4E66-2F31-4D71-B0CE-4A466654002D@vpnc.org> <20110701165912.GK52796@verdi> <2513461B-AAE2-44A5-9A9A-A1F7A4D3E2D1@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]); Fri, 01 Jul 2011 18:38:43 +0000 (UTC)
Cc: IETF-Discussion list <ietf@ietf.org>, John Leslie <john@jlc.net>, 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, 01 Jul 2011 18:38:48 -0000

This rathole does not require further exploration.

joel

On Jul 1, 2011, at 11:33 AM, Keith Moore wrote:

>=20
> On Jul 1, 2011, at 12:59 PM, John Leslie wrote:
>=20
>>=20
>>  IMHO, it's entirely reasonable to use even poorly-managed blacklists
>> as input to spam-assassin. And it's not up to _you_ to say what the
>> scoring algorithm should be for one of my customers.
>=20
> blacklists are the email version of terrorism, holding people's email =
service hostage in exchange for arbitrary tribute.
>=20
> Keith
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From swallow@cisco.com  Fri Jul  1 11:39:43 2011
Return-Path: <swallow@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 8725211E8160; Fri,  1 Jul 2011 11:39:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.202
X-Spam-Level: 
X-Spam-Status: No, score=-109.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, 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 Go2mKgB64xYW; Fri,  1 Jul 2011 11:39:42 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id 99DCE11E8155; Fri,  1 Jul 2011 11:39:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=swallow@cisco.com; l=2976; q=dns/txt; s=iport; t=1309545582; x=1310755182; h=date:subject:from:to:message-id:in-reply-to:mime-version; bh=ktvI87/7QxpdUHJ0OIypNafkVxzs7TYc05ksGpmdHfQ=; b=Xc9afFpspG2brY2XgnyWZwYPsRJTO3rTfTUCRAeYjgaPiFoak4REw3R7 +JuANdIQk+QW5tIhpcsPOrWssEVGNJkf7ZZzV/8TPRKISent9I7YhM70G Nk6LB8PIwUKFnz2bHpG6NvmKMTqVL/wb3SwYZV7F5hR0A4CttadY2Fk7X A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAAgTDk6tJXG+/2dsb2JhbABSglGkQm53iHmjIZ1shjIEkjKEf4tO
X-IronPort-AV: E=Sophos;i="4.65,460,1304294400";  d="scan'208,217";a="351609598"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by sj-iport-3.cisco.com with ESMTP; 01 Jul 2011 18:39:42 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core2-3.cisco.com (8.14.3/8.14.3) with ESMTP id p61IdfDK011177;  Fri, 1 Jul 2011 18:39:41 GMT
Received: from xmb-rcd-106.cisco.com ([72.163.62.148]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 1 Jul 2011 13:39:41 -0500
Received: from 10.86.244.99 ([10.86.244.99]) by XMB-RCD-106.cisco.com ([72.163.62.148]) with Microsoft Exchange Server HTTP-DAV ;  Fri,  1 Jul 2011 18:39:41 +0000
User-Agent: Microsoft-Entourage/12.29.0.110113
Date: Fri, 01 Jul 2011 14:39:40 -0400
Subject: Re: [mpls] Review: draft-ietf-mpls-tp-identifiers-06- Tunnel Identifier
From: George Swallow <swallow@cisco.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, IETF discussion list <ietf@ietf.org>, <mpls@ietf.org>
Message-ID: <CA338CAC.1110E%swallow@cisco.com>
Thread-Topic: [mpls] Review: draft-ietf-mpls-tp-identifiers-06- Tunnel Identifier
Thread-Index: Acw37/Of5BdGrxOFR9KA3LaJwlR13QALkjBa
In-Reply-To: <4E0DC68F.2060306@joelhalpern.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3392375980_148694742"
X-OriginalArrivalTime: 01 Jul 2011 18:39:41.0398 (UTC) FILETIME=[3D354F60:01CC381E]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 18:39:43 -0000

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

--B_3392375980_148694742
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

The primary motivation is to allow for a compact form for the Tunnel MEP_ID.
A secondary motivation is compatibility with existing MPLS/GMPLS Session
objects.

...George


On 7/1/11 9:07 AM, "Joel M. Halpern" <jmh@joelhalpern.com> wrote:

> In performing a gen-art review of this document, which seems quite good
> over all, I noticed a minor question, but did not remember to include it
> in my gen-art review.
> 
> The defines a Tunnel-Identifier, identifying the end-point of a tunnel
> within a node.
> That identifier is defined as 16 bits.
> In one sense, that seems sufficient.  But it is more restrictive than
> the number of parallel LSPs that the node could be an end-point for (by
> a factor of 16.)  So it seems that there ought to at least be an
> explanation for the mismatch.
> 
> Thank you,
> Joel
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 


--B_3392375980_148694742
Content-type: text/html;
	charset="US-ASCII"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [mpls] Review: draft-ietf-mpls-tp-identifiers-06- Tunnel Identif=
ier</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:10pt=
'>The primary motivation is to allow for a compact form for the Tunnel MEP_I=
D. &nbsp;A secondary motivation is compatibility with existing MPLS/GMPLS Se=
ssion objects.<BR>
<BR>
...George<BR>
<BR>
<BR>
On 7/1/11 9:07 AM, &quot;Joel M. Halpern&quot; &lt;<a href=3D"jmh@joelhalpern=
.com">jmh@joelhalpern.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><=
SPAN STYLE=3D'font-size:10pt'>In performing a gen-art review of this document,=
 which seems quite good<BR>
over all, I noticed a minor question, but did not remember to include it<BR=
>
in my gen-art review.<BR>
<BR>
The defines a Tunnel-Identifier, identifying the end-point of a tunnel<BR>
within a node.<BR>
That identifier is defined as 16 bits.<BR>
In one sense, that seems sufficient. &nbsp;But it is more restrictive than<=
BR>
the number of parallel LSPs that the node could be an end-point for (by<BR>
a factor of 16.) &nbsp;So it seems that there ought to at least be an<BR>
explanation for the mismatch.<BR>
<BR>
Thank you,<BR>
Joel<BR>
<BR>
_______________________________________________<BR>
mpls mailing list<BR>
<a href=3D"mpls@ietf.org">mpls@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/mpls">https://www.ietf.org/m=
ailman/listinfo/mpls</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--B_3392375980_148694742--


From scott.brim@gmail.com  Fri Jul  1 11:56:39 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 3513411E8178 for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 11:56:39 -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 mXP5lZ8L4zXJ for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 11:56:38 -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 09EB111E8144 for <ietf@ietf.org>; Fri,  1 Jul 2011 11:56:20 -0700 (PDT)
Received: by iye7 with SMTP id 7so3812257iye.31 for <ietf@ietf.org>; Fri, 01 Jul 2011 11:56:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=wRMKWHBY4tY9XB6kmyG6iXcGQeXO1ecIuFPSEg3zFIg=; b=XZMNYEuuOXWI1S39o56UWvS4+pYuvin0Ott8lGK892IC5EIPy96LfJrNInBwJxqS4Z QsU08RtKKym1vV1NSsOEThzu59gKnzoi0XR/eUFJe8+U+p6qR6fGdVIBoXOXep9IxDjf dGFQpQfVm98mvFdsD/D+JtoBzH+QdSlVVTOx0=
Received: by 10.231.24.193 with SMTP id w1mr3112031ibb.41.1309546575089; Fri, 01 Jul 2011 11:56:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.31.197 with HTTP; Fri, 1 Jul 2011 11:55:55 -0700 (PDT)
In-Reply-To: <57873F86-D06C-4C9E-AD2A-49AA739C90D3@bogus.com>
References: <201107011807.p61I7O4X018846@fs4113.wdf.sap.corp> <57873F86-D06C-4C9E-AD2A-49AA739C90D3@bogus.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Fri, 1 Jul 2011 14:55:55 -0400
Message-ID: <BANLkTi=Tk0uXHoKukT4yKLOLTioSkZJd7Q@mail.gmail.com>
Subject: Re: HOMENET working group proposal
To: Joel Jaeggli <joelja@bogus.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, 01 Jul 2011 18:56:39 -0000

On Fri, Jul 1, 2011 at 14:34, Joel Jaeggli <joelja@bogus.com> wrote:
>
> On Jul 1, 2011, at 11:07 AM, Martin Rex wrote:
>> james woodyatt wrote:
>>>
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
There is nothing about NAT or
>>> dynamic subscriber IP assignment that provides any mitigation
>>> whatsoever of the risks
>>
>> I'm more than a little concerned by the message that you're sending
>> here. =A0European legislators have enacted a "E-Privacy Directive"
>> also dubbed "European Cookie Directive" in order to protect the
>> privacy of citizens, and you're suggesting here that the IETF
>> should actively subvert this legislation and similar ongoing
>> legislative initiatives in the US by assigning static IPv6
>> addresses to home DSL subscribers so that cookies are completely
>> obviated and everyone can be trivially tracked based on his
>> static IP-Address. =A0This means you want to make IPv6 addresses
>> and all communications with that address direct personally
>> identifiable information, something for which a "must informed
>> beforehand", let alone an "opt opt" is technically impossible?
>
> The IETF has several times veered away from the deep water where internet=
 standards cross paths with regulatory requirements.
>
> http://tools.ietf.org/html/rfc2804
>
> We are not legal experts we are not qualified to interpret the statutory =
requirements of various nation states, our own or others. We need to be cle=
ar on what is in vs out of scope for IETF work. Focus on what would be perc=
ieved to be in the best interests the users and the network. Nation states =
will do whatever they do and sovereign by definition can impose whatever ma=
ndate they find necessary on their network operations and citizens.

Joel, the issue is very clear: what the IETF does must not make
privacy and confidentiality impossible.  It's not just some arbitrary
regulation from a committee, there are whole cultures who take this
very seriously.  You cite the wiretapping decision -- note we didn't
make wiretapping impossible, we just didn't support it.  In this case
it is very easy to make privacy (the right to control personal
information) and confidentiality (the right to know that private
information you share with one party will be kept within that scope)
impossible -- that's a position you may not take as someone making the
Internet work, since the ultimate stakeholders are those humans out at
the edges.  See also "Changes to Internet Architecture Can Collide
With Privacy" <http://www.ietf.org/proceedings/79/slides/intarea-3.pdf>
for a discussion of mobility.

When you think "oh right, I have to come up with a security
considerations section", include privacy and confidentiality
implications in your checklist of things to think about.

As to the technical issues here, higher layers don't need to use IP
addresses as identifiers, they have their own.  The only layer that
needs to care about IP addresses is the IP layer itself.  Privacy
addresses are well-defined and well-deployed.  The only issue with
using them is monitoring and logging activity.  The first hop router
can make the necessary correlations, but some access providers think
that's expensive.  Lawsuits over breach of confidentiality can be even
more expensive.  So is reworking protocols when a third of the world
won't use them.

Scott

From joelja@bogus.com  Fri Jul  1 12:12:39 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 5144A11E813A for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 12:12:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3RlnCocWIwV1 for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 12:12:38 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id D35B611E80A2 for <ietf@ietf.org>; Fri,  1 Jul 2011 12:12:37 -0700 (PDT)
Received: from [192.168.11.127] (c-76-115-172-69.hsd1.wa.comcast.net [76.115.172.69]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p61JCWPY089394 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 1 Jul 2011 19:12:33 GMT (envelope-from joelja@bogus.com)
Subject: Re: HOMENET working group proposal
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <BANLkTi=Tk0uXHoKukT4yKLOLTioSkZJd7Q@mail.gmail.com>
Date: Fri, 1 Jul 2011 12:12:27 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <5D32AC41-1D44-4ECB-A9EE-78748ABE7E91@bogus.com>
References: <201107011807.p61I7O4X018846@fs4113.wdf.sap.corp> <57873F86-D06C-4C9E-AD2A-49AA739C90D3@bogus.com> <BANLkTi=Tk0uXHoKukT4yKLOLTioSkZJd7Q@mail.gmail.com>
To: Scott Brim <scott.brim@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, 01 Jul 2011 19:12:33 +0000 (UTC)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jul 2011 19:12:39 -0000

On Jul 1, 2011, at 11:55 AM, Scott Brim wrote:

> On Fri, Jul 1, 2011 at 14:34, Joel Jaeggli <joelja@bogus.com> wrote:
>>=20
>> On Jul 1, 2011, at 11:07 AM, Martin Rex wrote:
>>> james woodyatt wrote:
>>>>=20
>>>>                                    There is nothing about NAT or
>>>> dynamic subscriber IP assignment that provides any mitigation
>>>> whatsoever of the risks
>>>=20
>>> I'm more than a little concerned by the message that you're sending
>>> here.  European legislators have enacted a "E-Privacy Directive"
>>> also dubbed "European Cookie Directive" in order to protect the
>>> privacy of citizens, and you're suggesting here that the IETF
>>> should actively subvert this legislation and similar ongoing
>>> legislative initiatives in the US by assigning static IPv6
>>> addresses to home DSL subscribers so that cookies are completely
>>> obviated and everyone can be trivially tracked based on his
>>> static IP-Address.  This means you want to make IPv6 addresses
>>> and all communications with that address direct personally
>>> identifiable information, something for which a "must informed
>>> beforehand", let alone an "opt opt" is technically impossible?
>>=20
>> The IETF has several times veered away from the deep water where =
internet standards cross paths with regulatory requirements.
>>=20
>> http://tools.ietf.org/html/rfc2804
>>=20
>> We are not legal experts we are not qualified to interpret the =
statutory requirements of various nation states, our own or others. We =
need to be clear on what is in vs out of scope for IETF work. Focus on =
what would be percieved to be in the best interests the users and the =
network. Nation states will do whatever they do and sovereign by =
definition can impose whatever mandate they find necessary on their =
network operations and citizens.
>=20
> Joel, the issue is very clear: what the IETF does must not make
> privacy and confidentiality impossible.  It's not just some arbitrary
> regulation from a committee, there are whole cultures who take this
> very seriously.  You cite the wiretapping decision -- note we didn't
> make wiretapping impossible, we just didn't support it.  In this case
> it is very easy to make privacy (the right to control personal
> information) and confidentiality (the right to know that private
> information you share with one party will be kept within that scope)
> impossible -- that's a position you may not take as someone making the
> Internet work, since the ultimate stakeholders are those humans out at
> the edges.  See also "Changes to Internet Architecture Can Collide
> With Privacy" =
<http://www.ietf.org/proceedings/79/slides/intarea-3.pdf>
> for a discussion of mobility.

You and I are in complete agreement when is comes to not making privacy =
or confidentiality impossible...=20

Where I object strenuously is when a directive wether it comes from the =
EU, the USA or the PRC becomes the consideration for framing a debate. =
The dictates of sovereigns are likely effectively impossible to =
reconcile if included fully in this space.

in 2804 the summary position is quite succinct in this regard:

   The IETF has decided not to consider requirements for wiretapping as
   part of the process for creating and maintaining IETF standards.

We know therefore without equivocation where a doucment like the =
following fits in the IETF standards context.

http://tools.ietf.org/html/rfc3924

we do not disallow the publication of such a document, in fact we should =
enoucorage it. but we also don't design to the soverign's requirements =
in the protocol specific.

> When you think "oh right, I have to come up with a security
> considerations section", include privacy and confidentiality
> implications in your checklist of things to think about.

In this context if we fail that badly we have a problem.

> As to the technical issues here, higher layers don't need to use IP
> addresses as identifiers, they have their own.  The only layer that
> needs to care about IP addresses is the IP layer itself.  Privacy
> addresses are well-defined and well-deployed.  The only issue with
> using them is monitoring and logging activity.  The first hop router
> can make the necessary correlations, but some access providers think
> that's expensive.  Lawsuits over breach of confidentiality can be even
> more expensive.  So is reworking protocols when a third of the world
> won't use them.
>=20
> Scott
>=20


From cb.list6@gmail.com  Fri Jul  1 12:42:02 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 E5E549E800E for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 12:42:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.91
X-Spam-Level: 
X-Spam-Status: No, score=-2.91 tagged_above=-999 required=5 tests=[AWL=0.689,  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 cwbGZp53BTR6 for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 12:42: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 B57C39E8014 for <ietf@ietf.org>; Fri,  1 Jul 2011 12:42:01 -0700 (PDT)
Received: by wyj26 with SMTP id 26so2771467wyj.31 for <ietf@ietf.org>; Fri, 01 Jul 2011 12:42:00 -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:content-transfer-encoding; bh=5BvL4ulZN1ip1oBvnCSoGNFlCFv9HNxsMBD8/viZttA=; b=w6RSWEjShcPCDEHw6wfvWczRlvlilUvBKd1XO4ljYq2vsBtOaG86VWJxzQGNpYQ4Oi BbD4jxqsbqInYOYs4kNNJY6nBMvyUAkrmDzst89a78TaFMLa0JCQKYlDGI/i3T3twvjh kpopH9SXSJGJBViCFv940w8U70InZ6rCkAA60=
MIME-Version: 1.0
Received: by 10.216.82.205 with SMTP id o55mr1392706wee.64.1309549320640; Fri, 01 Jul 2011 12:42:00 -0700 (PDT)
Received: by 10.216.39.83 with HTTP; Fri, 1 Jul 2011 12:42:00 -0700 (PDT)
In-Reply-To: <5D32AC41-1D44-4ECB-A9EE-78748ABE7E91@bogus.com>
References: <201107011807.p61I7O4X018846@fs4113.wdf.sap.corp> <57873F86-D06C-4C9E-AD2A-49AA739C90D3@bogus.com> <BANLkTi=Tk0uXHoKukT4yKLOLTioSkZJd7Q@mail.gmail.com> <5D32AC41-1D44-4ECB-A9EE-78748ABE7E91@bogus.com>
Date: Fri, 1 Jul 2011 12:42:00 -0700
Message-ID: <BANLkTimsTxAPRccQUFo_Sw636wmZsdrjqQ@mail.gmail.com>
Subject: Re: HOMENET working group proposal
From: Cameron Byrne <cb.list6@gmail.com>
To: Joel Jaeggli <joelja@bogus.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, 01 Jul 2011 19:42:03 -0000

On Fri, Jul 1, 2011 at 12:12 PM, Joel Jaeggli <joelja@bogus.com> wrote:
>
> On Jul 1, 2011, at 11:55 AM, Scott Brim wrote:
>
>> On Fri, Jul 1, 2011 at 14:34, Joel Jaeggli <joelja@bogus.com> wrote:
>>>
>>> On Jul 1, 2011, at 11:07 AM, Martin Rex wrote:
>>>> james woodyatt wrote:
>>>>>
>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0There is nothing about NAT or
>>>>> dynamic subscriber IP assignment that provides any mitigation
>>>>> whatsoever of the risks
>>>>
>>>> I'm more than a little concerned by the message that you're sending
>>>> here. =A0European legislators have enacted a "E-Privacy Directive"
>>>> also dubbed "European Cookie Directive" in order to protect the
>>>> privacy of citizens, and you're suggesting here that the IETF
>>>> should actively subvert this legislation and similar ongoing
>>>> legislative initiatives in the US by assigning static IPv6
>>>> addresses to home DSL subscribers so that cookies are completely
>>>> obviated and everyone can be trivially tracked based on his
>>>> static IP-Address. =A0This means you want to make IPv6 addresses
>>>> and all communications with that address direct personally
>>>> identifiable information, something for which a "must informed
>>>> beforehand", let alone an "opt opt" is technically impossible?
>>>
>>> The IETF has several times veered away from the deep water where intern=
et standards cross paths with regulatory requirements.
>>>
>>> http://tools.ietf.org/html/rfc2804
>>>
>>> We are not legal experts we are not qualified to interpret the statutor=
y requirements of various nation states, our own or others. We need to be c=
lear on what is in vs out of scope for IETF work. Focus on what would be pe=
rcieved to be in the best interests the users and the network. Nation state=
s will do whatever they do and sovereign by definition can impose whatever =
mandate they find necessary on their network operations and citizens.
>>
>> Joel, the issue is very clear: what the IETF does must not make
>> privacy and confidentiality impossible. =A0It's not just some arbitrary
>> regulation from a committee, there are whole cultures who take this
>> very seriously. =A0You cite the wiretapping decision -- note we didn't
>> make wiretapping impossible, we just didn't support it. =A0In this case
>> it is very easy to make privacy (the right to control personal
>> information) and confidentiality (the right to know that private
>> information you share with one party will be kept within that scope)
>> impossible -- that's a position you may not take as someone making the
>> Internet work, since the ultimate stakeholders are those humans out at
>> the edges. =A0See also "Changes to Internet Architecture Can Collide
>> With Privacy" <http://www.ietf.org/proceedings/79/slides/intarea-3.pdf>
>> for a discussion of mobility.
>
> You and I are in complete agreement when is comes to not making privacy o=
r confidentiality impossible...
>
> Where I object strenuously is when a directive wether it comes from the E=
U, the USA or the PRC becomes the consideration for framing a debate. The d=
ictates of sovereigns are likely effectively impossible to reconcile if inc=
luded fully in this space.
>


Bases some "Wikipedia research", there is some regulations about
browser cookies, and no mention of IP addresses.

There is some mention about web servers not retaining info without an
opt-out clause...  My analysis is very high level, i don't have the
details, but at first brush it seems like there is some conflation
going on here between cookies and IP addresses and what a home network
looks like vs what web servers retain in their logs.

I fail to see how this an IPv4 vs IPv6 issue?  Static vs Dynamic?

Cameron

> in 2804 the summary position is quite succinct in this regard:
>
> =A0 The IETF has decided not to consider requirements for wiretapping as
> =A0 part of the process for creating and maintaining IETF standards.
>
> We know therefore without equivocation where a doucment like the followin=
g fits in the IETF standards context.
>
> http://tools.ietf.org/html/rfc3924
>
> we do not disallow the publication of such a document, in fact we should =
enoucorage it. but we also don't design to the soverign's requirements in t=
he protocol specific.
>
>> When you think "oh right, I have to come up with a security
>> considerations section", include privacy and confidentiality
>> implications in your checklist of things to think about.
>
> In this context if we fail that badly we have a problem.
>
>> As to the technical issues here, higher layers don't need to use IP
>> addresses as identifiers, they have their own. =A0The only layer that
>> needs to care about IP addresses is the IP layer itself. =A0Privacy
>> addresses are well-defined and well-deployed. =A0The only issue with
>> using them is monitoring and logging activity. =A0The first hop router
>> can make the necessary correlations, but some access providers think
>> that's expensive. =A0Lawsuits over breach of confidentiality can be even
>> more expensive. =A0So is reworking protocols when a third of the world
>> won't use them.
>>
>> Scott
>>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

From listbounce-01@voort.ca  Fri Jul  1 13:03:59 2011
Return-Path: <listbounce-01@voort.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 5F2E411E80A9; Fri,  1 Jul 2011 13:03: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 qw7feMyG37OV; Fri,  1 Jul 2011 13:03:58 -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 B1BA59E805F; Fri,  1 Jul 2011 13:03:58 -0700 (PDT)
Received: by gxk19 with SMTP id 19so1788673gxk.31 for <multiple recipients>; Fri, 01 Jul 2011 13:03:58 -0700 (PDT)
Received: by 10.91.212.15 with SMTP id o15mr3348168agq.189.1309550638086; Fri, 01 Jul 2011 13:03:58 -0700 (PDT)
Received: from Kens-MacBook-Pro.local (76-10-173-233.dsl.teksavvy.com [76.10.173.233]) by mx.google.com with ESMTPS id 6sm1241265anu.31.2011.07.01.13.03.56 (version=SSLv3 cipher=OTHER); Fri, 01 Jul 2011 13:03:57 -0700 (PDT)
Message-ID: <4E0E282B.1060400@voort.ca>
Date: Fri, 01 Jul 2011 16:03:55 -0400
From: Kenneth Voort <listbounce-01@voort.ca>
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: ietf@ietf.org, fun@ietf.org
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.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jul 2011 20:03:59 -0000

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

I would also add that future IPv6 capable devices should allow end users to reach the IPv6 Internet
from an IPv4-only provider through some means, perhaps tunneling, with no or minimal administrator
intervention. I can see many providers remaining IPv4-only long into the future.

On 11-06-30 5: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


- -- 
Kenneth Voort - kenneth {at} voort <SPAMGUARD> {dot} ca
FDF1 6265 EBAB C05C FD06 1AED 158E 14D6 37CD E87F | pgp encrypted email preferred
-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAk4OKCsACgkQFY4U1jfN6H8gawCgkTQmlcodjih+Pawf8YTLZYiI
7M4AoI2Bm7F+uBc2lmoo+IdHEpeklcf6
=Hv52
-----END PGP SIGNATURE-----

From dougb@dougbarton.us  Fri Jul  1 13:13:48 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 E5F8911E818E for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 13:13: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 El34-lggyezG for <ietf@ietfa.amsl.com>; Fri,  1 Jul 2011 13:13:48 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id D580D11E816D for <ietf@ietf.org>; Fri,  1 Jul 2011 13:13:47 -0700 (PDT)
Received: (qmail 13216 invoked by uid 399); 1 Jul 2011 20:13:46 -0000
Received: from unknown (HELO 65-241-43-4.globalsuite.net) (dougb@dougbarton.us@65.241.43.4) by mail2.fluidhosting.com with ESMTPAM; 1 Jul 2011 20:13:46 -0000
X-Originating-IP: 65.241.43.4
X-Sender: dougb@dougbarton.us
Message-ID: <4E0E2A75.6040207@dougbarton.us>
Date: Fri, 01 Jul 2011 13:13:41 -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.18) Gecko/20110624 Thunderbird/3.1.11
MIME-Version: 1.0
To: Kenneth Voort <listbounce-01@voort.ca>
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> <4E0E282B.1060400@voort.ca>
In-Reply-To: <4E0E282B.1060400@voort.ca>
X-Enigmail-Version: 1.1.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 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: Fri, 01 Jul 2011 20:13:49 -0000

On 07/01/2011 13:03, Kenneth Voort wrote:
> I would also add that future IPv6 capable devices should allow end users to reach the IPv6 Internet
> from an IPv4-only provider through some means, perhaps tunneling, with no or minimal administrator
> intervention. I can see many providers remaining IPv4-only long into the future.

This is an area that we very clearly do not need to get involved in 
because it will solve itself due to market forces. Right now there is no 
IPv6-only content that anyone cares about. When that changes, users will 
start demanding that their provider give them access to it, or vote with 
their feet.

That said, I don't see IPv6-only content happening any time in the next 
5 years, at least. Content providers do not want to cut themselves off 
from 99.9% of their potential user base.

What's going to encourage IPv6 adoption on the content side are things 
like smart phones that use it natively (which is already happening). 
Content providers will see (and many are already seeing) that it is in 
their own best interest to get their content up on IPv6.

The ISP side will be dragged kicking and screaming into the IPv6 world 
in the next couple of years as the IPv4 addresses really do dry up, and 
the cost of obtaining more on the gray market begins to exceed the cost 
of deploying IPv6. And of course, some just won't make the transition, 
and will ultimately fail. C'est la vie.

To summarize my main point once again, there is nothing for the IETF to 
do here, the problem will take care of itself.


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 jnc@mercury.lcs.mit.edu  Fri Jul  1 13:43:02 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 ADABB11E81B9; Fri,  1 Jul 2011 13:43:02 -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 0vTni4UzN5Hd; Fri,  1 Jul 2011 13:43:02 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 3B0B011E815B; Fri,  1 Jul 2011 13:43:02 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 069D218C14E; Fri,  1 Jul 2011 16:43:01 -0400 (EDT)
To: fun@ietf.org, ietf@ietf.org
Subject: Re: [homegate] HOMENET working group proposal
Message-Id: <20110701204301.069D218C14E@mercury.lcs.mit.edu>
Date: Fri,  1 Jul 2011 16:43:01 -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, 01 Jul 2011 20:43:02 -0000

    > From: Kenneth Voort <listbounce-01@voort.ca>

    > future IPv6 capable devices should allow end users to reach the IPv6
    > Internet from an IPv4-only provider through some means, perhaps
    > tunneling, with no or minimal administrator intervention.

<Innocent face=on>
You mean, like with 6to4?
<Innocent face=off>

(Sorry, couldn't resist! :-)

	Noel

From moore@network-heretics.com  Fri Jul  1 14:14: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 1F44711E80C2; Fri,  1 Jul 2011 14:14:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.511
X-Spam-Level: 
X-Spam-Status: No, score=-3.511 tagged_above=-999 required=5 tests=[AWL=0.088,  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 QGXt1YxjqXKU; Fri,  1 Jul 2011 14:14: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 8F4FE9E8030; Fri,  1 Jul 2011 14:14:44 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 47FFD20B66; Fri,  1 Jul 2011 17:14:44 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Fri, 01 Jul 2011 17:14: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:content-transfer-encoding:message-id:references:to; s=smtpout; bh=buOpRo1nF+/CDebHb6OPZQpBxs0=; b=d6Ae3iWnV9BAL6727cSHBpQbIFXAlYbtFzSWCgnryoJWDq6kb5t9S/3EJQWO4gNwh3e2btFmdXLJ1BdE70+P16RAYpYr0gwBqrzeBq5yjp9TNEAmlAf8UJKGQVaF+i5LG4tRl5uQJ8kOYHBROAOibrXB/JM7z7sz0dY8wOpUBaA=
X-Sasl-enc: awSei0P5APbP1lCOvKQOKSBm3/7GfmiLwfP9DaNRZYcc 1309554883
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 859B140399D; Fri,  1 Jul 2011 17:14:43 -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: <4E0E282B.1060400@voort.ca>
Date: Fri, 1 Jul 2011 17:14:25 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B9E883AA-549E-4F2E-83D7-5E8F27881BD4@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> <4E0E282B.1060400@voort.ca>
To: Kenneth Voort <listbounce-01@voort.ca>
X-Mailer: Apple Mail (2.1084)
Cc: 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: Fri, 01 Jul 2011 21:14:45 -0000

On Jul 1, 2011, at 4:03 PM, Kenneth Voort wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> I would also add that future IPv6 capable devices should allow end =
users to reach the IPv6 Internet
> from an IPv4-only provider through some means, perhaps tunneling, with =
no or minimal administrator
> intervention. I can see many providers remaining IPv4-only long into =
the future.

+1


From moore@network-heretics.com  Fri Jul  1 14:18: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 C6E4411E81BA; Fri,  1 Jul 2011 14:18:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.516
X-Spam-Level: 
X-Spam-Status: No, score=-3.516 tagged_above=-999 required=5 tests=[AWL=0.083,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3eE02o+NEcDe; Fri,  1 Jul 2011 14:18:17 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id DF40E11E81CA; Fri,  1 Jul 2011 14:18:10 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 95F3C20BB3; Fri,  1 Jul 2011 17:18:10 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Fri, 01 Jul 2011 17:18: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:content-transfer-encoding:message-id:references:to; s=smtpout; bh=CJQyH/9A9W3WHOTxT5h3GdnHf7Y=; b=cDISCaw+zPLrjDtXVmZMEtDW+mNTUY7lsO4tDq1JWWcRcU1jAKDFqjJecQLW7vQnxWDI9RiRExiPSdAnfvxAJyLogf7PrI3TMpFMfmZQCO/Gg/VKQMR6+msaQSSZrzxSX/7whkVnRbE4oJ62VszCWUynPlB35ZI1a0ntKyiX5YI=
X-Sasl-enc: A6yFzRmGFRRs4XK8FCl+rRR8I80hy/ZVKMNDfJxw8U3a 1309555090
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 8B5B840A931; Fri,  1 Jul 2011 17:18:09 -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: <4E0E2A75.6040207@dougbarton.us>
Date: Fri, 1 Jul 2011 17:17:51 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F863D9FD-5A5F-4E6C-88D3-E0F941D79622@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> <4E0E282B.1060400@voort.ca> <4E0E2A75.6040207@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
X-Mailer: Apple Mail (2.1084)
Cc: 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: Fri, 01 Jul 2011 21:18:17 -0000

On Jul 1, 2011, at 4:13 PM, Doug Barton wrote:

> On 07/01/2011 13:03, Kenneth Voort wrote:
>> I would also add that future IPv6 capable devices should allow end =
users to reach the IPv6 Internet
>> from an IPv4-only provider through some means, perhaps tunneling, =
with no or minimal administrator
>> intervention. I can see many providers remaining IPv4-only long into =
the future.
>=20
> This is an area that we very clearly do not need to get involved in =
because it will solve itself due to market forces. Right now there is no =
IPv6-only content that anyone cares about. When that changes, users will =
start demanding that their provider give them access to it, or vote with =
their feet.

Whenever people talk about the Internet as if it were just about "access =
to content", I have to wonder.    The Internet has always been more =
about conversation than content. =20

> To summarize my main point once again, there is nothing for the IETF =
to do here, the problem will take care of itself.

Quite the contrary.  We still don't have a good transition mechanism =
that HOMENET could specify.   6to4 has problems as we're now painfully =
aware; configured tunnels and Teredo have different problems.  There's =
still room for work in this space if better solutions can be identified. =
 Though it doesn't seem appropriate to ask the HOMENET WG to develop =
them.

Keith


From mohta@necom830.hpcl.titech.ac.jp  Sat Jul  2 00:20:54 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 B10951F0C3B for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 00:20:54 -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 BeWElxiaic3m for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 00:20:54 -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 D38AE1F0C3D for <ietf@ietf.org>; Sat,  2 Jul 2011 00:20:51 -0700 (PDT)
Received: (qmail 91665 invoked from network); 2 Jul 2011 07:33: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; 2 Jul 2011 07:33:33 -0000
Message-ID: <4E0EC6C1.2000304@necom830.hpcl.titech.ac.jp>
Date: Sat, 02 Jul 2011 16:20:33 +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: <201107011807.p61I7O4X018846@fs4113.wdf.sap.corp>
In-Reply-To: <201107011807.p61I7O4X018846@fs4113.wdf.sap.corp>
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, 02 Jul 2011 07:20:54 -0000

Martin Rex wrote:

> This means you want to make IPv6 addresses
> and all communications with that address direct personally
> identifiable information, something for which a "must informed
> beforehand", let alone an "opt opt" is technically impossible?

If what you want is "opt out" from static IP addresses, use proxies
at an application layer or IP over IP at the network layer.

						Masataka Ohta

From moore@network-heretics.com  Sat Jul  2 07:52: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 1FA6921F863A for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 07:52:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.52
X-Spam-Level: 
X-Spam-Status: No, score=-3.52 tagged_above=-999 required=5 tests=[AWL=0.079,  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 0HzwU61RoLkL for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 07:52: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 2EBDF21F860D for <ietf@ietf.org>; Sat,  2 Jul 2011 07:52:28 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 5ED6C20963; Sat,  2 Jul 2011 10:52:27 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Sat, 02 Jul 2011 10:52:27 -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=a38r4xxh0TR1SVqnzkTJuSPtVeA=; b=lCdTeHfIeutBCjYq+dLCZJGAaH8lZKF2B5t54GhejZLKNwICsVs7Ynf1FYbW0Ab8QH+KTWE7dVDMwRlRs0icMUX221Ct5waiIzouniqC1Aki/E3SskdyMgYNd3LJRS0ITseCKwmtoksqzgQ8UaeyTP8Kpjw1JejbVKrwohxzqhk=
X-Sasl-enc: 0NKmh7DNyfRdcgUaxxd8rkDuxxDrSdISX1+8Xpudw9Y3 1309618346
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 2A1EA40C86A; Sat,  2 Jul 2011 10:52:26 -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: <BANLkTi=Tk0uXHoKukT4yKLOLTioSkZJd7Q@mail.gmail.com>
Date: Sat, 2 Jul 2011 10:52:08 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <1B0E6A5D-0BF1-400B-A063-D59D8ED2C766@network-heretics.com>
References: <201107011807.p61I7O4X018846@fs4113.wdf.sap.corp> <57873F86-D06C-4C9E-AD2A-49AA739C90D3@bogus.com> <BANLkTi=Tk0uXHoKukT4yKLOLTioSkZJd7Q@mail.gmail.com>
To: Scott Brim <scott.brim@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: Sat, 02 Jul 2011 14:52:29 -0000

On Jul 1, 2011, at 2:55 PM, Scott Brim wrote:
>>=20
>> The IETF has several times veered away from the deep water where =
internet standards cross paths with regulatory requirements.
>>=20
>> http://tools.ietf.org/html/rfc2804
>>=20
>> We are not legal experts we are not qualified to interpret the =
statutory requirements of various nation states, our own or others. We =
need to be clear on what is in vs out of scope for IETF work. Focus on =
what would be percieved to be in the best interests the users and the =
network. Nation states will do whatever they do and sovereign by =
definition can impose whatever mandate they find necessary on their =
network operations and citizens.
>=20
> Joel, the issue is very clear: what the IETF does must not make
> privacy and confidentiality impossible.  It's not just some arbitrary
> regulation from a committee, there are whole cultures who take this
> very seriously.  You cite the wiretapping decision -- note we didn't
> make wiretapping impossible, we just didn't support it.  In this case
> it is very easy to make privacy (the right to control personal
> information) and confidentiality (the right to know that private
> information you share with one party will be kept within that scope)
> impossible -- that's a position you may not take as someone making the
> Internet work, since the ultimate stakeholders are those humans out at
> the edges.  See also "Changes to Internet Architecture Can Collide
> With Privacy" =
<http://www.ietf.org/proceedings/79/slides/intarea-3.pdf>
> for a discussion of mobility.
>=20
> When you think "oh right, I have to come up with a security
> considerations section", include privacy and confidentiality
> implications in your checklist of things to think about.

Very much agree.=20

I strongly disagree with the statement that every home network should =
have only ephemeral external addresses and that it should NAT to stable =
internal addresses.  I also strongly disagree with the assertion that EU =
law requires IETF to make it so.  But the underlying concerns are quite =
valid and important. =20

I don't want to cripple all home networks and applications by imposing =
ephemeral addresses and/or NATs on them.  But having a stable address =
prefix associated with every device in one's home network that =
communicates with the public Internet can indeed threaten the user's =
privacy.  (Note that privacy addresses don't really solve the problem as =
they still all have the same prefix.)  Some applications and hosts =
require stable addresses; others do not.   So it might be that a home =
network needs to be able to support two prefixes - a stable one that can =
be used by those applications that need it, and an ephemeral one that =
can be used by everything else.   That's not difficult to do by itself, =
but my next question is how to arrange these things such that ordinary =
consumers can understand such details and manage them?

Anyway, to me it seems reasonable for the HOMENET group to consider =
privacy issues associated with address assignment.

> As to the technical issues here, higher layers don't need to use IP
> addresses as identifiers, they have their own.  The only layer that
> needs to care about IP addresses is the IP layer itself. =20

This has been demonstrated many times to be false.

Keith


From rbonica@juniper.net  Sat Jul  2 09:38:27 2011
Return-Path: <rbonica@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46E0E11E80AC; Sat,  2 Jul 2011 09:38:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.126
X-Spam-Level: 
X-Spam-Status: No, score=-106.126 tagged_above=-999 required=5 tests=[AWL=-0.127, 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 l+HvRaWHUaWu; Sat,  2 Jul 2011 09:38:26 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id 82E2C11E808C; Sat,  2 Jul 2011 09:38:26 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKTg9Jgiw+T/SvYqTY0/hYPSXulrBMqvql@postini.com; Sat, 02 Jul 2011 09:38:26 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.2.254.0; Sat, 2 Jul 2011 09:36:07 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Sat, 2 Jul 2011 12:36:06 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "v6ops@ietf.org" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
Date: Sat, 2 Jul 2011 12:36:05 -0400
Subject: draft-ietf-v6ops-6to4-to-historic
Thread-Topic: draft-ietf-v6ops-6to4-to-historic
Thread-Index: Acw41iMv6/qWspvgTzCQB463JqIp+A==
Message-ID: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Jul 2011 16:38:27 -0000

Folks,

Whereas there has been considerable controversy regarding draft-ietf-v6ops-=
6to4-to-historic, the v6ops chairs and document author have agreed to the f=
ollowing course of action:

- the V6OPS WG will withdraw its request to publish draft-ietf-v6ops-6to4-t=
o-historic
- The author will introduce a new draft, intended for standards track publi=
cation. The new draft will update RFCs 3056 and 3068. It will say that if 6=
-to-4 is implemented, it must be turned off by default.=20
- In order for the new draft to be published, it must achieve both V6OPS WG=
 and IETF consensus

If anyone objects to this course of action, please speak up soon.

                                                    Ron
                                                    <Speaking as OPS Area A=
D>

From osa.peter@gmail.com  Sat Jul  2 12:16:04 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 2559322800E for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 12:16:04 -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 VJrkCv0l+5RA for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 12:16:03 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id BF41221F85B2 for <ietf@ietf.org>; Sat,  2 Jul 2011 12:16:02 -0700 (PDT)
Received: by ewy19 with SMTP id 19so1704420ewy.31 for <ietf@ietf.org>; Sat, 02 Jul 2011 12:16:01 -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=DytKzb3tM/XgcNnAMU8d7+0cmaR2EIsPEazZCRqwfuQ=; b=vK6ZaKBFtdn8hlQciV3ql7RsWBvUvtgQe88XLF9UQBtrYMka8wxvXUMhvIj7BxfEr5 sb+v47MLAv6p8DYjI3YD4XcB8K929Wykte7UQdFQKOhB+oOa10v5yDg2XrdOyyDFgJTP G3+vwmuOIS4I3p/z1f7VQfmLuhkJyAM+7bwfY=
Received: by 10.213.14.4 with SMTP id e4mr1051258eba.51.1309634160692; Sat, 02 Jul 2011 12:16:00 -0700 (PDT)
Received: from 172.18.212.183 (bda-178-239-87-86.bis7.eu.blackberry.com [178.239.87.86]) by mx.google.com with ESMTPS id 74sm3388069eet.19.2011.07.02.12.15.58 (version=SSLv3 cipher=OTHER); Sat, 02 Jul 2011 12:15:59 -0700 (PDT)
X-rim-org-msg-ref-id: 1202456751
Message-ID: <1202456751-1309634157-cardhu_decombobulator_blackberry.rim.net-2091144183-@b1.c19.bise7.blackberry>
Content-Transfer-Encoding: base64
X-Priority: Normal
References: <mailman.15.1309633204.4524.ietf@ietf.org>
In-Reply-To: <mailman.15.1309633204.4524.ietf@ietf.org>
Sensitivity: Normal
Importance: Normal
Subject: Re: Ietf Digest, Vol 38, Issue 6
To: ietf@ietf.org
From: osa.peter@gmail.com
Date: Sat, 2 Jul 2011 19:15:55 +0000
Content-Type: text/plain
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: osa.peter@gmail.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Jul 2011 19:16:04 -0000

Q29uc2lkZXJpbmcgdGhlIG5vLiBPZiB1c2VycyBhdCBldmVyeSBzZWNvbmQgaXQgd2lsbCBub3Qg
YmUgcG9zc2libGUgdG8gYWNoaWV2ZSBkaXJlY3QgcHJpdmFjeSBhZGRyZXNzaW5nIHN5c3RlbSwg
Zm9yIG1lIElFVEYgc2hsZCBkZXNpZ24gYSBzeXN0ZW0gd2hpY2ggd2lsbCBlbmhhbmNlIERNWiBu
ZXR3b3JrICBjb25uZWN0aW9uIGRldGVjdGlvbiBhbmQgbW9uaXRvcmluZyBzeXN0ZW0uIA0KQW1l
bmF3b24gT3NhIFBldGVyDQpTZW50IGZyb20gbXkgQmxhY2tCZXJyeSB3aXJlbGVzcyBkZXZpY2Ug
ZnJvbSBTYXBlbmFORVQNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGlldGYt
cmVxdWVzdEBpZXRmLm9yZw0KU2VuZGVyOiBpZXRmLWJvdW5jZXNAaWV0Zi5vcmcNCkRhdGU6IFNh
dCwgMDIgSnVsIDIwMTEgMTI6MDA6MDQgDQpUbzogPGlldGZAaWV0Zi5vcmc+DQpSZXBseS1Ubzog
aWV0ZkBpZXRmLm9yZw0KU3ViamVjdDogSWV0ZiBEaWdlc3QsIFZvbCAzOCwgSXNzdWUgNg0KDQpJ
ZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGRpZ2VzdCB3aXRob3V0IGFsbCB0aGUgaW5kaXZpZHVh
bCBtZXNzYWdlDQphdHRhY2htZW50cyB5b3Ugd2lsbCBuZWVkIHRvIHVwZGF0ZSB5b3VyIGRpZ2Vz
dCBvcHRpb25zIGluIHlvdXIgbGlzdA0Kc3Vic2NyaXB0aW9uLiAgVG8gZG8gc28sIGdvIHRvIA0K
DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lldGYNCg0KQ2xpY2sgdGhl
ICdVbnN1YnNjcmliZSBvciBlZGl0IG9wdGlvbnMnIGJ1dHRvbiwgbG9nIGluLCBhbmQgc2V0ICJH
ZXQNCk1JTUUgb3IgUGxhaW4gVGV4dCBEaWdlc3RzPyIgdG8gTUlNRS4gIFlvdSBjYW4gc2V0IHRo
aXMgb3B0aW9uDQpnbG9iYWxseSBmb3IgYWxsIHRoZSBsaXN0IGRpZ2VzdHMgeW91IHJlY2VpdmUg
YXQgdGhpcyBwb2ludC4NCg0KDQoNClNlbmQgSWV0ZiBtYWlsaW5nIGxpc3Qgc3VibWlzc2lvbnMg
dG8NCglpZXRmQGlldGYub3JnDQoNClRvIHN1YnNjcmliZSBvciB1bnN1YnNjcmliZSB2aWEgdGhl
IFdvcmxkIFdpZGUgV2ViLCB2aXNpdA0KCWh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vaWV0Zg0Kb3IsIHZpYSBlbWFpbCwgc2VuZCBhIG1lc3NhZ2Ugd2l0aCBzdWJqZWN0IG9y
IGJvZHkgJ2hlbHAnIHRvDQoJaWV0Zi1yZXF1ZXN0QGlldGYub3JnDQoNCllvdSBjYW4gcmVhY2gg
dGhlIHBlcnNvbiBtYW5hZ2luZyB0aGUgbGlzdCBhdA0KCWlldGYtb3duZXJAaWV0Zi5vcmcNCg0K
V2hlbiByZXBseWluZywgcGxlYXNlIGVkaXQgeW91ciBTdWJqZWN0IGxpbmUgc28gaXQgaXMgbW9y
ZSBzcGVjaWZpYw0KdGhhbiAiUmU6IENvbnRlbnRzIG9mIElldGYgZGlnZXN0Li4uIg0KDQoNClRv
ZGF5J3MgVG9waWNzOg0KDQogICAxLiBSZTogSE9NRU5FVCB3b3JraW5nIGdyb3VwIHByb3Bvc2Fs
IChNYXNhdGFrYSBPaHRhKQ0KICAgMi4gUmU6IEhPTUVORVQgd29ya2luZyBncm91cCBwcm9wb3Nh
bCAoS2VpdGggTW9vcmUpDQogICAzLiBkcmFmdC1pZXRmLXY2b3BzLTZ0bzQtdG8taGlzdG9yaWMg
KFJvbmFsZCBCb25pY2EpDQoNCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQpNZXNzYWdlOiAxDQpEYXRlOiBT
YXQsIDAyIEp1bCAyMDExIDE2OjIwOjMzICswOTAwDQpGcm9tOiBNYXNhdGFrYSBPaHRhIDxtb2h0
YUBuZWNvbTgzMC5ocGNsLnRpdGVjaC5hYy5qcD4NClRvOiBpZXRmQGlldGYub3JnDQpTdWJqZWN0
OiBSZTogSE9NRU5FVCB3b3JraW5nIGdyb3VwIHByb3Bvc2FsDQpNZXNzYWdlLUlEOiA8NEUwRUM2
QzEuMjAwMDMwNEBuZWNvbTgzMC5ocGNsLnRpdGVjaC5hYy5qcD4NCkNvbnRlbnQtVHlwZTogdGV4
dC9wbGFpbjsgY2hhcnNldD1JU08tMjAyMi1KUA0KDQpNYXJ0aW4gUmV4IHdyb3RlOg0KDQo+IFRo
aXMgbWVhbnMgeW91IHdhbnQgdG8gbWFrZSBJUHY2IGFkZHJlc3Nlcw0KPiBhbmQgYWxsIGNvbW11
bmljYXRpb25zIHdpdGggdGhhdCBhZGRyZXNzIGRpcmVjdCBwZXJzb25hbGx5DQo+IGlkZW50aWZp
YWJsZSBpbmZvcm1hdGlvbiwgc29tZXRoaW5nIGZvciB3aGljaCBhICJtdXN0IGluZm9ybWVkDQo+
IGJlZm9yZWhhbmQiLCBsZXQgYWxvbmUgYW4gIm9wdCBvcHQiIGlzIHRlY2huaWNhbGx5IGltcG9z
c2libGU/DQoNCklmIHdoYXQgeW91IHdhbnQgaXMgIm9wdCBvdXQiIGZyb20gc3RhdGljIElQIGFk
ZHJlc3NlcywgdXNlIHByb3hpZXMNCmF0IGFuIGFwcGxpY2F0aW9uIGxheWVyIG9yIElQIG92ZXIg
SVAgYXQgdGhlIG5ldHdvcmsgbGF5ZXIuDQoNCgkJCQkJCU1hc2F0YWthIE9odGENCg0KDQotLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0KTWVzc2FnZTogMg0KRGF0ZTogU2F0LCAyIEp1
bCAyMDExIDEwOjUyOjA4IC0wNDAwDQpGcm9tOiBLZWl0aCBNb29yZSA8bW9vcmVAbmV0d29yay1o
ZXJldGljcy5jb20+DQpUbzogU2NvdHQgQnJpbSA8c2NvdHQuYnJpbUBnbWFpbC5jb20+DQpDYzog
aWV0ZkBpZXRmLm9yZw0KU3ViamVjdDogUmU6IEhPTUVORVQgd29ya2luZyBncm91cCBwcm9wb3Nh
bA0KTWVzc2FnZS1JRDoNCgk8MUIwRTZBNUQtMEJGMS00MDBCLUEwNjMtRDU5RDhFRDJDNzY2QG5l
dHdvcmstaGVyZXRpY3MuY29tPg0KQ29udGVudC1UeXBlOiB0ZXh0L3BsYWluOyBjaGFyc2V0PXVz
LWFzY2lpDQoNCk9uIEp1bCAxLCAyMDExLCBhdCAyOjU1IFBNLCBTY290dCBCcmltIHdyb3RlOg0K
Pj4gDQo+PiBUaGUgSUVURiBoYXMgc2V2ZXJhbCB0aW1lcyB2ZWVyZWQgYXdheSBmcm9tIHRoZSBk
ZWVwIHdhdGVyIHdoZXJlIGludGVybmV0IHN0YW5kYXJkcyBjcm9zcyBwYXRocyB3aXRoIHJlZ3Vs
YXRvcnkgcmVxdWlyZW1lbnRzLg0KPj4gDQo+PiBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9y
ZmMyODA0DQo+PiANCj4+IFdlIGFyZSBub3QgbGVnYWwgZXhwZXJ0cyB3ZSBhcmUgbm90IHF1YWxp
ZmllZCB0byBpbnRlcnByZXQgdGhlIHN0YXR1dG9yeSByZXF1aXJlbWVudHMgb2YgdmFyaW91cyBu
YXRpb24gc3RhdGVzLCBvdXIgb3duIG9yIG90aGVycy4gV2UgbmVlZCB0byBiZSBjbGVhciBvbiB3
aGF0IGlzIGluIHZzIG91dCBvZiBzY29wZSBmb3IgSUVURiB3b3JrLiBGb2N1cyBvbiB3aGF0IHdv
dWxkIGJlIHBlcmNpZXZlZCB0byBiZSBpbiB0aGUgYmVzdCBpbnRlcmVzdHMgdGhlIHVzZXJzIGFu
ZCB0aGUgbmV0d29yay4gTmF0aW9uIHN0YXRlcyB3aWxsIGRvIHdoYXRldmVyIHRoZXkgZG8gYW5k
IHNvdmVyZWlnbiBieSBkZWZpbml0aW9uIGNhbiBpbXBvc2Ugd2hhdGV2ZXIgbWFuZGF0ZSB0aGV5
IGZpbmQgbmVjZXNzYXJ5IG9uIHRoZWlyIG5ldHdvcmsgb3BlcmF0aW9ucyBhbmQgY2l0aXplbnMu
DQo+IA0KPiBKb2VsLCB0aGUgaXNzdWUgaXMgdmVyeSBjbGVhcjogd2hhdCB0aGUgSUVURiBkb2Vz
IG11c3Qgbm90IG1ha2UNCj4gcHJpdmFjeSBhbmQgY29uZmlkZW50aWFsaXR5IGltcG9zc2libGUu
ICBJdCdzIG5vdCBqdXN0IHNvbWUgYXJiaXRyYXJ5DQo+IHJlZ3VsYXRpb24gZnJvbSBhIGNvbW1p
dHRlZSwgdGhlcmUgYXJlIHdob2xlIGN1bHR1cmVzIHdobyB0YWtlIHRoaXMNCj4gdmVyeSBzZXJp
b3VzbHkuICBZb3UgY2l0ZSB0aGUgd2lyZXRhcHBpbmcgZGVjaXNpb24gLS0gbm90ZSB3ZSBkaWRu
J3QNCj4gbWFrZSB3aXJldGFwcGluZyBpbXBvc3NpYmxlLCB3ZSBqdXN0IGRpZG4ndCBzdXBwb3J0
IGl0LiAgSW4gdGhpcyBjYXNlDQo+IGl0IGlzIHZlcnkgZWFzeSB0byBtYWtlIHByaXZhY3kgKHRo
ZSByaWdodCB0byBjb250cm9sIHBlcnNvbmFsDQo+IGluZm9ybWF0aW9uKSBhbmQgY29uZmlkZW50
aWFsaXR5ICh0aGUgcmlnaHQgdG8ga25vdyB0aGF0IHByaXZhdGUNCj4gaW5mb3JtYXRpb24geW91
IHNoYXJlIHdpdGggb25lIHBhcnR5IHdpbGwgYmUga2VwdCB3aXRoaW4gdGhhdCBzY29wZSkNCj4g
aW1wb3NzaWJsZSAtLSB0aGF0J3MgYSBwb3NpdGlvbiB5b3UgbWF5IG5vdCB0YWtlIGFzIHNvbWVv
bmUgbWFraW5nIHRoZQ0KPiBJbnRlcm5ldCB3b3JrLCBzaW5jZSB0aGUgdWx0aW1hdGUgc3Rha2Vo
b2xkZXJzIGFyZSB0aG9zZSBodW1hbnMgb3V0IGF0DQo+IHRoZSBlZGdlcy4gIFNlZSBhbHNvICJD
aGFuZ2VzIHRvIEludGVybmV0IEFyY2hpdGVjdHVyZSBDYW4gQ29sbGlkZQ0KPiBXaXRoIFByaXZh
Y3kiIDxodHRwOi8vd3d3LmlldGYub3JnL3Byb2NlZWRpbmdzLzc5L3NsaWRlcy9pbnRhcmVhLTMu
cGRmPg0KPiBmb3IgYSBkaXNjdXNzaW9uIG9mIG1vYmlsaXR5Lg0KPiANCj4gV2hlbiB5b3UgdGhp
bmsgIm9oIHJpZ2h0LCBJIGhhdmUgdG8gY29tZSB1cCB3aXRoIGEgc2VjdXJpdHkNCj4gY29uc2lk
ZXJhdGlvbnMgc2VjdGlvbiIsIGluY2x1ZGUgcHJpdmFjeSBhbmQgY29uZmlkZW50aWFsaXR5DQo+
IGltcGxpY2F0aW9ucyBpbiB5b3VyIGNoZWNrbGlzdCBvZiB0aGluZ3MgdG8gdGhpbmsgYWJvdXQu
DQoNClZlcnkgbXVjaCBhZ3JlZS4gDQoNCkkgc3Ryb25nbHkgZGlzYWdyZWUgd2l0aCB0aGUgc3Rh
dGVtZW50IHRoYXQgZXZlcnkgaG9tZSBuZXR3b3JrIHNob3VsZCBoYXZlIG9ubHkgZXBoZW1lcmFs
IGV4dGVybmFsIGFkZHJlc3NlcyBhbmQgdGhhdCBpdCBzaG91bGQgTkFUIHRvIHN0YWJsZSBpbnRl
cm5hbCBhZGRyZXNzZXMuICBJIGFsc28gc3Ryb25nbHkgZGlzYWdyZWUgd2l0aCB0aGUgYXNzZXJ0
aW9uIHRoYXQgRVUgbGF3IHJlcXVpcmVzIElFVEYgdG8gbWFrZSBpdCBzby4gIEJ1dCB0aGUgdW5k
ZXJseWluZyBjb25jZXJucyBhcmUgcXVpdGUgdmFsaWQgYW5kIGltcG9ydGFudC4gIA0KDQpJIGRv
bid0IHdhbnQgdG8gY3JpcHBsZSBhbGwgaG9tZSBuZXR3b3JrcyBhbmQgYXBwbGljYXRpb25zIGJ5
IGltcG9zaW5nIGVwaGVtZXJhbCBhZGRyZXNzZXMgYW5kL29yIE5BVHMgb24gdGhlbS4gIEJ1dCBo
YXZpbmcgYSBzdGFibGUgYWRkcmVzcyBwcmVmaXggYXNzb2NpYXRlZCB3aXRoIGV2ZXJ5IGRldmlj
ZSBpbiBvbmUncyBob21lIG5ldHdvcmsgdGhhdCBjb21tdW5pY2F0ZXMgd2l0aCB0aGUgcHVibGlj
IEludGVybmV0IGNhbiBpbmRlZWQgdGhyZWF0ZW4gdGhlIHVzZXIncyBwcml2YWN5LiAgKE5vdGUg
dGhhdCBwcml2YWN5IGFkZHJlc3NlcyBkb24ndCByZWFsbHkgc29sdmUgdGhlIHByb2JsZW0gYXMg
dGhleSBzdGlsbCBhbGwgaGF2ZSB0aGUgc2FtZSBwcmVmaXguKSAgU29tZSBhcHBsaWNhdGlvbnMg
YW5kIGhvc3RzIHJlcXVpcmUgc3RhYmxlIGFkZHJlc3Nlczsgb3RoZXJzIGRvIG5vdC4gICBTbyBp
dCBtaWdodCBiZSB0aGF0IGEgaG9tZSBuZXR3b3JrIG5lZWRzIHRvIGJlIGFibGUgdG8gc3VwcG9y
dCB0d28gcHJlZml4ZXMgLSBhIHN0YWJsZSBvbmUgdGhhdCBjYW4gYmUgdXNlZCBieSB0aG9zZSBh
cHBsaWNhdGlvbnMgdGhhdCBuZWVkIGl0LCBhbmQgYW4gZXBoZW1lcmFsIG9uZSB0aGF0IGNhbiBi
ZSB1c2VkIGJ5IGV2ZXJ5dGhpbmcgZWxzZS4gICBUaGF0J3Mgbm90IGRpZmZpY3VsdCB0byBkbyBi
eSBpdHNlbGYsIGJ1dCBteSBuZXh0IHF1ZXN0aW9uIGlzIGhvdyB0byBhcnJhbmdlIHRoZXNlIHRo
aW5ncyBzdWNoIHRoYXQgb3JkaW5hcnkgY29uc3VtZXJzIGNhbiB1bmRlcnN0YW5kIHN1Y2ggZGV0
YWlscyBhbmQgbWFuYWdlIHRoZW0/DQoNCkFueXdheSwgdG8gbWUgaXQgc2VlbXMgcmVhc29uYWJs
ZSBmb3IgdGhlIEhPTUVORVQgZ3JvdXAgdG8gY29uc2lkZXIgcHJpdmFjeSBpc3N1ZXMgYXNzb2Np
YXRlZCB3aXRoIGFkZHJlc3MgYXNzaWdubWVudC4NCg0KPiBBcyB0byB0aGUgdGVjaG5pY2FsIGlz
c3VlcyBoZXJlLCBoaWdoZXIgbGF5ZXJzIGRvbid0IG5lZWQgdG8gdXNlIElQDQo+IGFkZHJlc3Nl
cyBhcyBpZGVudGlmaWVycywgdGhleSBoYXZlIHRoZWlyIG93bi4gIFRoZSBvbmx5IGxheWVyIHRo
YXQNCj4gbmVlZHMgdG8gY2FyZSBhYm91dCBJUCBhZGRyZXNzZXMgaXMgdGhlIElQIGxheWVyIGl0
c2VsZi4gIA0KDQpUaGlzIGhhcyBiZWVuIGRlbW9uc3RyYXRlZCBtYW55IHRpbWVzIHRvIGJlIGZh
bHNlLg0KDQpLZWl0aA0KDQoNCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNCk1l
c3NhZ2U6IDMNCkRhdGU6IFNhdCwgMiBKdWwgMjAxMSAxMjozNjowNSAtMDQwMA0KRnJvbTogUm9u
YWxkIEJvbmljYSA8cmJvbmljYUBqdW5pcGVyLm5ldD4NClRvOiAidjZvcHNAaWV0Zi5vcmciIDx2
Nm9wc0BpZXRmLm9yZz4sIElFVEYgRGlzY3Vzc2lvbiA8aWV0ZkBpZXRmLm9yZz4NClN1YmplY3Q6
IGRyYWZ0LWlldGYtdjZvcHMtNnRvNC10by1oaXN0b3JpYw0KTWVzc2FnZS1JRDoNCgk8MTMyMDVD
Mjg2NjYyREU0Mzg3RDlBRjNBQzMwRUY0NTZEM0YzNTA3RURBQEVNQlgwMS1XRi5qbnByLm5ldD4N
CkNvbnRlbnQtVHlwZTogdGV4dC9wbGFpbjsgY2hhcnNldD0idXMtYXNjaWkiDQoNCkZvbGtzLA0K
DQpXaGVyZWFzIHRoZXJlIGhhcyBiZWVuIGNvbnNpZGVyYWJsZSBjb250cm92ZXJzeSByZWdhcmRp
bmcgZHJhZnQtaWV0Zi12Nm9wcy02dG80LXRvLWhpc3RvcmljLCB0aGUgdjZvcHMgY2hhaXJzIGFu
ZCBkb2N1bWVudCBhdXRob3IgaGF2ZSBhZ3JlZWQgdG8gdGhlIGZvbGxvd2luZyBjb3Vyc2Ugb2Yg
YWN0aW9uOg0KDQotIHRoZSBWNk9QUyBXRyB3aWxsIHdpdGhkcmF3IGl0cyByZXF1ZXN0IHRvIHB1
Ymxpc2ggZHJhZnQtaWV0Zi12Nm9wcy02dG80LXRvLWhpc3RvcmljDQotIFRoZSBhdXRob3Igd2ls
bCBpbnRyb2R1Y2UgYSBuZXcgZHJhZnQsIGludGVuZGVkIGZvciBzdGFuZGFyZHMgdHJhY2sgcHVi
bGljYXRpb24uIFRoZSBuZXcgZHJhZnQgd2lsbCB1cGRhdGUgUkZDcyAzMDU2IGFuZCAzMDY4LiBJ
dCB3aWxsIHNheSB0aGF0IGlmIDYtdG8tNCBpcyBpbXBsZW1lbnRlZCwgaXQgbXVzdCBiZSB0dXJu
ZWQgb2ZmIGJ5IGRlZmF1bHQuIA0KLSBJbiBvcmRlciBmb3IgdGhlIG5ldyBkcmFmdCB0byBiZSBw
dWJsaXNoZWQsIGl0IG11c3QgYWNoaWV2ZSBib3RoIFY2T1BTIFdHIGFuZCBJRVRGIGNvbnNlbnN1
cw0KDQpJZiBhbnlvbmUgb2JqZWN0cyB0byB0aGlzIGNvdXJzZSBvZiBhY3Rpb24sIHBsZWFzZSBz
cGVhayB1cCBzb29uLg0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgUm9uDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgPFNwZWFraW5nIGFzIE9QUyBBcmVhIEFEPg0KDQoNCi0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLQ0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KSWV0ZiBtYWlsaW5nIGxpc3QNCklldGZAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaWV0Zg0KDQoNCkVuZCBvZiBJZXRmIERpZ2VzdCwg
Vm9sIDM4LCBJc3N1ZSA2DQoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKg0K


From cb.list6@gmail.com  Sat Jul  2 12:21: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 57DBF21F85A3; Sat,  2 Jul 2011 12:21:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.839
X-Spam-Level: 
X-Spam-Status: No, score=-2.839 tagged_above=-999 required=5 tests=[AWL=0.159,  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 NDUPI3u9+Jbp; Sat,  2 Jul 2011 12:21: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 57D9021F85A0; Sat,  2 Jul 2011 12:21:39 -0700 (PDT)
Received: by wyj26 with SMTP id 26so3199946wyj.31 for <multiple recipients>; Sat, 02 Jul 2011 12:21:38 -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=mTapDQ5YaVBLKKvebEItCJwFK3aFFm8RVm+YoDP0K4k=; b=lVgv5ZxWa0QVQDhM0oAtk9JyT0QANsLVbh6bwnlvfcaFh+94+nsMvmDieixQ2URRoZ 8L4TW/NfY6HxCHxxALnSxhz0fu5Qg8frqM4uOLmsEfAfPxS7A5dEpqKFAVUZEeK++IIc yI6wkDQd3jjQv1ODFGygUcnQ7ld9AXmkM192g=
MIME-Version: 1.0
Received: by 10.216.63.131 with SMTP id a3mr3780289wed.64.1309634496662; Sat, 02 Jul 2011 12:21:36 -0700 (PDT)
Received: by 10.216.39.83 with HTTP; Sat, 2 Jul 2011 12:21:36 -0700 (PDT)
Received: by 10.216.39.83 with HTTP; Sat, 2 Jul 2011 12:21:36 -0700 (PDT)
In-Reply-To: <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com>
Date: Sat, 2 Jul 2011 12:21:36 -0700
Message-ID: <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
From: Cameron Byrne <cb.list6@gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/alternative; boundary=000e0cdfd8bcf58cff04a71b0aa7
Cc: "v6ops@ietf.org" <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: Sat, 02 Jul 2011 19:21:40 -0000

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

On Jul 2, 2011 11:55 AM, "Lorenzo Colitti" <lorenzo@google.com> wrote:
>
> On Sat, Jul 2, 2011 at 6:36 PM, Ronald Bonica <rbonica@juniper.net> wrote:
>>
>> - In order for the new draft to be published, it must achieve both V6OPS
WG and IETF consensus
>>
>> If anyone objects to this course of action, please speak up soon.
>
>
> Great, back to square one.
>
> Is the reasoning behind the decision explained somewhere? My reading of
the threads on the subject in v6ops was that the opposition to 6to4-historic
was a small but vocal minority, and I thought that qualified as rough
consensus. But perhaps I missed some discussion.
>

I saw the same thing. It is a shame that work that directly removes barriers
to REAL ipv6 deployment gets shouted down by a few people not involved in
REAL ipv6 deployment.

Welcome to the ietf indeed.

Cb

> Also, why do the author and the chairs think that the new draft will do
any better than 6to4-historic? I would assume that the same people who spoke
up against 6to4-historic will speak up against the new document, and since
that level of opposition was sufficient to prevent the publication
of 6to4-historic, it may be sufficient to prevent publication of the new
document as well. If so, we will have spent 3-6 months arguing about it for
naught.
>
> Please, nobody answer this question with "welcome to the IETF" :-)
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

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

<p><br>
On Jul 2, 2011 11:55 AM, &quot;Lorenzo Colitti&quot; &lt;<a href=3D"mailto:=
lorenzo@google.com">lorenzo@google.com</a>&gt; wrote:<br>
&gt;<br>
&gt; On Sat, Jul 2, 2011 at 6:36 PM, Ronald Bonica &lt;<a href=3D"mailto:rb=
onica@juniper.net">rbonica@juniper.net</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; - In order for the new draft to be published, it must achieve both=
 V6OPS WG and IETF consensus<br>
&gt;&gt;<br>
&gt;&gt; If anyone objects to this course of action, please speak up soon.<=
br>
&gt;<br>
&gt;<br>
&gt; Great, back to square one.<br>
&gt;<br>
&gt; Is the reasoning behind the decision explained somewhere?=A0My reading=
 of the threads on the subject in v6ops was that the opposition to 6to4-his=
toric was a small but vocal minority, and I thought that qualified as rough=
 consensus. But perhaps I missed some discussion.<br>

&gt;</p>
<p>I saw the same thing. It is a shame that work that directly removes barr=
iers to REAL ipv6 deployment gets shouted down by a few people not involved=
 in REAL ipv6 deployment. </p>
<p>Welcome to the ietf indeed.</p>
<p>Cb</p>
<p>&gt; Also, why do the author and the chairs think that the new draft wil=
l do any better than 6to4-historic? I would assume that the same people who=
 spoke up against 6to4-historic will speak up against the new document, and=
 since that level of opposition was sufficient to prevent the publication o=
f=A06to4-historic, it may be sufficient to prevent publication of the new d=
ocument as well.=A0If so, we will have spent 3-6 months arguing about it fo=
r naught.<br>

&gt;<br>
&gt; Please, nobody answer this question with &quot;welcome to the IETF&quo=
t; :-)<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>
&gt;<br>
</p>

--000e0cdfd8bcf58cff04a71b0aa7--

From moore@network-heretics.com  Sat Jul  2 13:03:07 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 4436C11E8167; Sat,  2 Jul 2011 13:03:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.224
X-Spam-Level: 
X-Spam-Status: No, score=-3.224 tagged_above=-999 required=5 tests=[AWL=-0.225, 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 rGZ-Xs8hx5ma; Sat,  2 Jul 2011 13:03:06 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 9511C11E8101; Sat,  2 Jul 2011 13:03:06 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 388F120993; Sat,  2 Jul 2011 16:03:06 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Sat, 02 Jul 2011 16:03: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=hUu01AXkvMIq+ZetFsoCH7tVWog=; b=Vxz3h0rEhnDQUpgb6maYIEi3835gVX6Xk6j2Qeuv/agxPeICX0TGWFMC1bmU0AYIftQyhfERlwhh55MUpEsLdcCPwX+ebQal3EqpUYBcciWs7CZ7enVaXCaRy7EQPpLg9+nkG5z0O0XbuLE654A5/9U5D+DUTvygB5oMB94FIbI=
X-Sasl-enc: l/PVn8LFmu7XCa6u+pGgXJRbLJkgmPQFp7TFnz8LkcYm 1309636985
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 2DEDF404E9A; Sat,  2 Jul 2011 16:03:05 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
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: <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com>
Date: Sat, 2 Jul 2011 16:02:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DE414D2B-82ED-4C32-AFDF-EDAAB6D743B2@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org" <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: Sat, 02 Jul 2011 20:03:07 -0000

> Is the reasoning behind the decision explained somewhere? My reading =
of the threads on the subject in v6ops was that the opposition to =
6to4-historic was a small but vocal minority, and I thought that =
qualified as rough consensus.=20

Even if there was rough consensus within v6ops, rough consensus of v6ops =
does not equate to rough consensus of the entire IETF community.=20

> Also, why do the author and the chairs think that the new draft will =
do any better than 6to4-historic? I would assume that the same people =
who spoke up against 6to4-historic will speak up against the new =
document, and since that level of opposition was sufficient to prevent =
the publication of 6to4-historic, it may be sufficient to prevent =
publication of the new document as well. If so, we will have spent 3-6 =
months arguing about it for naught.

I hope that the author(s) of the new document and the v6ops WG will =
understand that their task is to craft a document that can earn =
community-wide consensus, not merely the approval of v6ops.  As long as =
the document is brief and to-the-point, I don't see any problem.  I =
personally don't have any objection to the notion that 6to4 should be =
off by default and should require explicit configuration to enable it.

Keith


From moore@network-heretics.com  Sat Jul  2 13:25: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 60A7F11E80C1; Sat,  2 Jul 2011 13:25:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.513
X-Spam-Level: 
X-Spam-Status: No, score=-3.513 tagged_above=-999 required=5 tests=[AWL=0.086,  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 I+Z3pdJOAV6E; Sat,  2 Jul 2011 13:25: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 BA65411E80A6; Sat,  2 Jul 2011 13:25:55 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id 614B8206BE; Sat,  2 Jul 2011 16:25:55 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute5.internal (MEProxy); Sat, 02 Jul 2011 16:25: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=cwcqUjGIVfUhdmfVrFqiDYA/mr0=; b=at8VwFCOv+npiRw3gIjoxtNLENbTH8SbyhtWTRT1q6B0aKiAv5MIY9hR5D8DMXgM9Ui2paugkYUFBJ603lMezsdC8j2qhRrZy/nw1pYFWKOqKOUHBlKoi1bgOjKk8zzcX9V87squKYgzPFTKInRk1Yq/BCJCc+u0nDxFWFBnPBE=
X-Sasl-enc: I7Rm47nxU3NLYf1OrycGESP4bUNkrguOZizvTTQSRxVn 1309638355
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 7F52940C8DF; Sat,  2 Jul 2011 16:25:54 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
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: <4E0F7E12.8060901@raszuk.net>
Date: Sat, 2 Jul 2011 16:25:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3D17B847-7424-4A31-8072-761DDFDCA5B1@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net>	<CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <DE414D2B-82ED-4C32-AFDF-EDAAB6D743B2@network-heretics.com> <4E0F7E12.8060901@raszuk.net>
To: robert@raszuk.net
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org" <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: Sat, 02 Jul 2011 20:25:56 -0000

On Jul 2, 2011, at 4:22 PM, Robert Raszuk wrote:

> Hi Keith,
>=20
>> I personally don't have any objection to the notion that 6to4 should
>> be off by default and should require explicit configuration to enable
>> it.
>=20
> Is there any feature (perhaps other then netboot) on commercial or =
open source routers which is not off by default and which would require =
explicit configuration to enable it ?

I have understood that in the past there were a few routers that enabled =
6to4 by default, though I don't know whether this is the case any =
longer.  =20
I also believe that there are currently hosts that enable 6to4 by =
default if there is no native v6 connectivity and the host has a public =
IPv4 address.

Keith


From danny@tcb.net  Sat Jul  2 14:12:01 2011
Return-Path: <danny@tcb.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1961F11E8151 for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 14:12:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.901
X-Spam-Level: 
X-Spam-Status: No, score=-105.901 tagged_above=-999 required=5 tests=[AWL=-0.698, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 TFHqcsJYj54m for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 14:11:58 -0700 (PDT)
Received: from exprod6og104.obsmtp.com (exprod6og104.obsmtp.com [64.18.1.187]) by ietfa.amsl.com (Postfix) with ESMTP id C23F311E80D9 for <ietf@ietf.org>; Sat,  2 Jul 2011 14:11:56 -0700 (PDT)
Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob104.postini.com ([64.18.5.12]) with SMTP ID DSNKTg+Jm0Uo4RlcCtW3Gj72EUHW03KsD4cV@postini.com; Sat, 02 Jul 2011 14:11:56 PDT
Received: from dul1wnexcn03.vcorp.ad.vrsn.com (dul1wnexcn03.vcorp.ad.vrsn.com [10.170.12.113]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id p62LBs7Z021572; Sat, 2 Jul 2011 17:11:54 -0400
Received: from dul1dmcphers-m2.vcorp.ad.vrsn.com ([10.100.0.243]) by dul1wnexcn03.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.4675); Sat, 2 Jul 2011 17:11:53 -0400
Subject: Re: Comments surrounding draft-iab-dns-applications-01
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Danny McPherson <danny@tcb.net>
In-Reply-To: <a06240800c9df29c0bf75@[10.31.203.186]>
Date: Sat, 2 Jul 2011 17:11:53 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B8FD63DA-3047-4CE5-8CA0-BA12B54617A1@tcb.net>
References: <a06240800c9df29c0bf75@[10.31.203.186]>
To: Edward Lewis <Ed.Lewis@neustar.biz>
X-Mailer: Apple Mail (2.1084)
X-OriginalArrivalTime: 02 Jul 2011 21:11:53.0455 (UTC) FILETIME=[AAC05FF0:01CC38FC]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Jul 2011 21:12:01 -0000

On Apr 28, 2011, at 10:40 AM, Edward Lewis wrote:

> These comments were sent to the IAB already.  I was encouraged to send =
them to the general IETF list.  This is mostly a re-posting of the =
comments, with one added paragraph (there's marker there).
>=20
> The referenced document is:
> =
http://www.ietf.org/internet-drafts/draft-iab-anycast-arch-implications-01=
.txt

Ed et al.,=20
In collecting and attempting to accommodate reviews on the Anycast =
Architectural Implications ID to which the link just above references, =
it's clear to me (and quite possibly everyone that read your message) =
that you meant to reference draft-iab-dns-applications-01, to which the =
subject and feedback concerns, available here:

<http://tools.ietf.org/html/draft-iab-dns-applications-01>

That said, a new revision of the Anycast document will be available in =
very short order, and I welcome feedback on it as well :-)

Thanks,=20

-danny


>=20
> It's hard to make comments on a document whose mission is not at all =
clear.  The problem I have is that the document has a faulty baseline =
and incorrectly assesses extensions and variations.  Having spent 15 =
years with the DNS and having to come to a deep architectural =
understanding of it in order to define DNSSEC, my view of the DNS is =
vastly different than that documented by the IAB.  With this it is hard =
to tell what the document is trying to guard against.  Or push towards.
>=20
> Starting with what the DNS is and why it exists has to recognize that =
a lot of work we think is native to it actually preceded it in the =
/etc/hosts.txt file and in similarly built systems.  DNS is not =
principally there to translate names to numbers as the draft opens with, =
although that is a high-profile use case.  The DNS did not define a =
uniform naming scheme.  DNS is there principally to build on the =
previous solution (a text file distributed once a week from a central =
location).
>=20
> If I were asked to list the bullet points that describe the DNS core =
competency, they would be
> - availability
> - resilience
> - speed in response
> - speed in propagating data
> - distributed management
> - neutral
> Where the DNS is weak is in the data plane and the management plane. =
The basic lookup/search algorithm is stilted, inflexible, and hard for =
many to understand.  The biggest dilemma that it faces is that in order =
to be strong it uses an unreliable transport substrate as it's primary =
communication mechanism, the same substrate that is the source of the =
protocol's chief technical challenges.
>=20
> In a way, DNS is a balancing act, it is all about using UDP "right."
>=20
> To a lesser extent, the fact that the DNS is not a client-server =
protocol, as it is usually treated in text, but a client-cache-server =
protocol complicates understanding it's architecture.  This is the very =
reason DNSSEC exists, the ingrained middle-man in the client-server =
exchange.  Attempts to empower the middle-man are the chief obstacle to =
improving the overall health of the DNS and it's cooperation with other =
protocol systems.
>=20
> Over time there really hasn't been progress in the way of making the =
DNS support applications.  Despite what is in the IAB draft, there has =
been just one application that is built into the DNS, done at the "dawn =
of time" and not even in a significant way.  Mail is the only =
application with built in support in DNS.  No other application has ever =
changed the DNS definition.  To understand this we should look a =
chronology of changes to the DNS concept and specification.
>=20
> The original DNS specification is as defined in STD 13's documents. I =
won't bore you with repeating what's there, except to point out that a =
few seminal types are included in the original set.
>=20
> It is also important to quantify what's meant by DNS support for an =
application.  The baseline for any type is, given a name, class, and =
type, the returned value will have a set of data.  Any resource record =
type that follows this baseline is considered to have "no special =
processing," the label put on sensitive types.
>=20
> Types that have no special processing include the A, AAAA, and PTR =
records.  Some of these types do contain domain name that can be =
compressed and this is confused as special processing - but that is not =
special to the protocol, just special to the marshalling of the =
parameters.  Surprising to some folks, SRV and NAPTR also have no =
special processing, in fact aren't even subject to message compression.  =
This point is one I have to make because the draft uses SRV and NAPTR as =
evidence of application scope creep into the DNS.
>=20
> Types that do have special processing include this list (not =
exclusively) SOA, NS, MX, CNAME, DNAME, and the DNSSEC types.  These are =
the types that are cause considerations for the DNS.  MX is the mail =
application dedicated type.  It's impact is that it causes additional =
data (address records) to be included in a response.  A very lightweight =
action, but special processing nonetheless.
>=20
> One of the concerns that is conflated with NAPTR, TXT, DNSSEC and IPv6 =
records is the concern over protocol data unit size.  This issue is =
generic to the DNS and stems from the UDP transport "dependency" and not =
on application demands.  (Back to the balancing act involving UDP.)
>=20
> Back to the chronology, looking for application-intelligence creep.
>=20
> These are what I consider to be the turning points in DNS history:
>=20
> RFC 1995/1996 - event-driven and incremental updates of zone contents
> RFC 2136 - dynamic updating of a zone's contents
> RFC 2181 - reduction in gullibility of caches
> RFC 2308 - negative caching and the introduction of mnemonics
> RFC 2671 - extended DNS header/trailer
> RFC 2672 - DNAME (non-terminal query redirection)
> "Views" - BIND's feature supporting query-source tailored responses
> RFC 4033 - DNSSEC (cache poisoning defense)
>=20
> If one gains an understanding of those RFCs (and the BIND feature), =
they will have a workable impression of the DNS.  Not complete and with =
some gaps, but the architecture would be roughed in.
>=20
> Internationalized domain names have no impact on the architecture of =
the DNS, the same as for the DDDS and SRV record.  IDNs and SRVs do rely =
on their own naming conventions, but that isn't an issue for the DNS.  =
SRV's naming convention obviates the use of wildcards, but that is not a =
concern for the DNS protocol's architecture.
>=20
> The recent push to support tailored responses, that is, responses =
based on QNAME, QTYPE, QCLASS plus information about or inside the query =
message, has been happening for nearly a decade.  I don't recall the =
exact version of BIND that introduced Views, but I do know I was using =
it in 2003 when I worked at ARIN.  Views was in response to outside =
demands, unknown to me, and I was aware of statefull firewalls that did =
something similar back into the late 90's.  This effort is sustained by =
latent demand, not a provider's recent desire.
>=20
> (Paragraph added for IETF list) In my opinion, merely adding a RR type =
to the DNS does not represent an architectural change which is why I =
launched in to this history.  Applications have added record types over =
time.  The addition of a type is not a significant event, in fact, it is =
an event that has not happened frequently enough.  To me, significant =
changes to the architecture would include  updates to the algorithm in =
RFC 1034, section 4.3.2.  To date though, that section has only been =
updated for DNAME and fixed for CNAME (in RFC 2672 and 4592 =
respectively).  Architectural changes may not impact that algorithm, but =
such changes signal architectural impacts more so than a newly defined =
type.
>=20
> So far I've summed up the reasons why I disagree with the beginning of =
the document.  After writing this I went back to the document again to =
see if I better understood the point of the draft.
>=20
> In section 4 there are four guiding principles that center on =
enforcing the idea that there is complete coherency across queries for =
QNAME, QTYPE, and QCLASS.  In my opinion this is archaic. Although the =
IETF has ignored in-coherency in DNS (the failure of =
http://tools.ietf.org/html/draft-krishnaswamy-dnsop-dnssec-split-view-04 =
to even become an WG item) in the "real world" this has been going on =
since the late 90's.
>=20
> One reason why such in-coherency exists today, having stood the test =
of at least a decade in operations (running code) is that in-coherency =
is not a radical idea despite the perception.  In the original framing =
of the DNS data was static, quickly a dynamic nature was added.  In a =
static world, coherency is a measurable and achievable condition, with =
dynamic elements, it is not.  Seeing a zone change rapidly is isomorphic =
to a server responding differently based on source IP address when =
examining the traffic crossing port 53.  =46rom this observation, =
combining the concept of tailored responses with the DNS is fairly easy.
>=20
> Later in section 4 there are five other cautionary tales.  Most of =
these are "not a problem" today.
>=20
> One of these describes a true concern - relying on knowledge of the =
DNS management model to assist in authorization determination, that is, =
knowing where zone cuts exist.  An application that relies on the =
management of data in another application has abdicated it's authority =
and will suffer the consequences at some point.  This is not unique to =
the DNS.
>=20
> Mapping real world objects or concepts to domain names can be as =
complicated as anyone wants.  For example, naming routers with multiple =
interfaces, a problem seen on NOG lists periodically.  The complexity in =
the mapping is immaterial, so long as the application developers can do =
it consistently.  Perhaps the most complex mapping is hashing, as is =
done for DNSSEC's NSEC3.
>=20
> Sensitive data can be in the DNS if other protections are taken. E.g., =
most companies consider their internal hardware topology to be sensitive =
but still run DNS for the benefit of their employees.  They then keep =
this DNS "private."  (Again, this practice is not documented by the =
IETF.)  Some ENUM work has been done to make ENUM work in places where =
telephone number information is considered sensitive.
>=20
> The remaining points are outmoded.  While it is true that =
synchronizing zone contents with external sources of data take work, it =
can be made to work.  Maybe the misperception is that this is only about =
the DNS.  But sometimes putting more work on the DNS alleviates other =
systems.  In this case, the DNS can be operated as it should be, making =
use of the dynamic update features the IETF approved and the zone data =
propagation approaches already defined with the result of assisting in =
traffic management.  Not perfectly, but helping.
>=20
> The recommendations in section 4 are arguable.  There are fairly solid =
arguments why the recommendations (except perhaps one of them) are =
wrong.  I am not saying the recommendations mentioned have merit, but =
they are not worthy of being backed by the IAB.
>=20
> In section 3, well, in trying not to get into a blow-by-blow =
discussion, I'll summarize my thoughts that the IAB appears to be saying =
"avoid these things because they will be bad" even though some of them =
have been in play for more than a decade.  It's like a parent telling =
their teenager not to smoke after the teen has already developed the =
habit.
>=20
> I have to mention 3.3.1.  The red herring about the size of data in =
DNS has been around for a long time.  There is no issue.  TCP is not a =
problem for DNS, at least architecturally speaking.  Yes, some =
implementations don't have this right, but the situation can be fixed.  =
Inside the DNS, size is just a number.  All applications have size =
issues.  All that is needed is to keep in mind what the strengths of the =
DNS are, and let applications try to live within the constraints.
>=20
> If the IAB is going to make such a statement, they should remind =
applications what the strengths and limitations of the DNS are and have =
recommendations on who to solve generic problems.  As written the =
document sounds like a sad, almost pathetic plea for folks to stop =
innovating with the DNS.  It's almost as bad as the IAB statement on a =
unique root, which caused more problems than it solved.  (I've never =
bothered to read the the "extend DNS" document after the first few =
revisions of it.)
>=20
> Finally, as the document stands now, I'd rather not be listed as a =
contributor.  It's not fair to me to be associated with the draft's =
architectural view.  It is fair to say I've submitted comments, but =
don't give the impression I endorse the document as it is.
>=20
> --=20
> =
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
> Edward Lewis
> NeuStar                    You can leave a voice message at =
+1-571-434-5468
>=20
> Me to infant son: "Waah! Waah! Is that all you can say?  Waah?"
> Son: "Waah!"
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From dougb@dougbarton.us  Sat Jul  2 18:04:35 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 A373711E809E for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 18:04:35 -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 WSuiX38J2ki9 for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 18:04:35 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id D18FE11E809D for <ietf@ietf.org>; Sat,  2 Jul 2011 18:04:34 -0700 (PDT)
Received: (qmail 4969 invoked by uid 399); 3 Jul 2011 01:04: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; 3 Jul 2011 01:04:33 -0000
X-Originating-IP: 65.241.43.4
X-Sender: dougb@dougbarton.us
Message-ID: <4E0FC01B.7010709@dougbarton.us>
Date: Sat, 02 Jul 2011 18:04:27 -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.18) Gecko/20110624 Thunderbird/3.1.11
MIME-Version: 1.0
To: Cameron Byrne <cb.list6@gmail.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net>	<CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com>
In-Reply-To: <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.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: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 01:04:35 -0000

On 07/02/2011 12:21, Cameron Byrne wrote:
>
> On Jul 2, 2011 11:55 AM, "Lorenzo Colitti" <lorenzo@google.com
> <mailto:lorenzo@google.com>> wrote:
>  >
>  > On Sat, Jul 2, 2011 at 6:36 PM, Ronald Bonica <rbonica@juniper.net
> <mailto:rbonica@juniper.net>> wrote:
>  >>
>  >> - In order for the new draft to be published, it must achieve both
> V6OPS WG and IETF consensus
>  >>
>  >> If anyone objects to this course of action, please speak up soon.
>  >
>  >
>  > Great, back to square one.
>  >
>  > Is the reasoning behind the decision explained somewhere? My reading
> of the threads on the subject in v6ops was that the opposition to
> 6to4-historic was a small but vocal minority, and I thought that
> qualified as rough consensus. But perhaps I missed some discussion.
>  >
>
> I saw the same thing. It is a shame that work that directly removes
> barriers to REAL ipv6 deployment gets shouted down by a few people not
> involved in REAL ipv6 deployment.

I can't speak to the "REAL" bit, but I agree that this is a very 
disappointing turn of events. Consensus is not the same as "universal 
agreement," and I don't think the fact that a few people are repeating 
the same marginally-relevant-at-best points over and over again should 
have sidetracked this process.


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  Sat Jul  2 18:31:51 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 A2FC321F864F for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 18:31:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.479
X-Spam-Level: 
X-Spam-Status: No, score=-3.479 tagged_above=-999 required=5 tests=[AWL=0.120,  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 ZWdt5tp5IBrp for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 18:31:50 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 7860921F8620 for <ietf@ietf.org>; Sat,  2 Jul 2011 18:31:50 -0700 (PDT)
Received: (qmail 3655 invoked by uid 399); 3 Jul 2011 01:31:49 -0000
Received: from unknown (HELO 65-241-43-4.globalsuite.net) (dougb@dougbarton.us@65.241.43.4) by mail2.fluidhosting.com with ESMTPAM; 3 Jul 2011 01:31:49 -0000
X-Originating-IP: 65.241.43.4
X-Sender: dougb@dougbarton.us
Message-ID: <4E0FC683.6020900@dougbarton.us>
Date: Sat, 02 Jul 2011 18:31:47 -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.18) Gecko/20110624 Thunderbird/3.1.11
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>	<alpine.DEB.2.00.1106300923280.19581@uplift.swm.pp.se>	<558D0669-8B2A-4514-B3FB-C690C40A4EF8@townsley.net> <4E0E282B.1060400@voort.ca> <4E0E2A75.6040207@dougbarton.us> <F863D9FD-5A5F-4E6C-88D3-E0F941D79622@network-heretics.com>
In-Reply-To: <F863D9FD-5A5F-4E6C-88D3-E0F941D79622@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: 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: Sun, 03 Jul 2011 01:31:51 -0000

On 07/01/2011 14:17, Keith Moore wrote:
> On Jul 1, 2011, at 4:13 PM, Doug Barton wrote:
>
>> On 07/01/2011 13:03, Kenneth Voort wrote:
>>> I would also add that future IPv6 capable devices should allow
>>> end users to reach the IPv6 Internet from an IPv4-only provider
>>> through some means, perhaps tunneling, with no or minimal
>>> administrator intervention. I can see many providers remaining
>>> IPv4-only long into the future.
>>
>> This is an area that we very clearly do not need to get involved in
>> because it will solve itself due to market forces. Right now there
>> is no IPv6-only content that anyone cares about. When that changes,
>> users will start demanding that their provider give them access to
>> it, or vote with their feet.
>
> Whenever people talk about the Internet as if it were just about
> "access to content", I have to wonder.    The Internet has always
> been more about conversation than content.

The overwhelming majority of Internet users are consumers of content. 
Some of that content is stuff like Skype, instant messaging, etc.

The overwhelming majority of businesses that make the Internet work are 
the content providers, and the ISPs that enable the consumers of that 
content to reach it.

Failure to recognize these 2 critical facts leads to producing standards 
documents that have no relevance in the real world.

>> To summarize my main point once again, there is nothing for the
>> IETF to do here, the problem will take care of itself.
>
> Quite the contrary.  We still don't have a good transition mechanism
> that HOMENET could specify.

And as I pointed out in the bits of my message that you snipped, we 
don't need one.


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 rbonica@juniper.net  Sat Jul  2 19:27:04 2011
Return-Path: <rbonica@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB6F611E80B5; Sat,  2 Jul 2011 19:27:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.284
X-Spam-Level: 
X-Spam-Status: No, score=-106.284 tagged_above=-999 required=5 tests=[AWL=-0.286, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 NBFSrj-ZXm8q; Sat,  2 Jul 2011 19:27:03 -0700 (PDT)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by ietfa.amsl.com (Postfix) with ESMTP id D2CC211E8085; Sat,  2 Jul 2011 19:27:01 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKTg/TdYx9PcSLjmb0OL3Sosif+bm1WQt0@postini.com; Sat, 02 Jul 2011 19:27:02 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.2.254.0; Sat, 2 Jul 2011 19:22:34 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Sat, 2 Jul 2011 22:22:33 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Lorenzo Colitti <lorenzo@google.com>
Date: Sat, 2 Jul 2011 22:22:32 -0400
Subject: RE: [v6ops] draft-ietf-v6ops-6to4-to-historic
Thread-Topic: [v6ops] draft-ietf-v6ops-6to4-to-historic
Thread-Index: Acw46ZSDGm+GNc0bSFSdbCjnIAF0mQAPKgmw
Message-ID: <13205C286662DE4387D9AF3AC30EF456D3F3507F08@EMBX01-WF.jnpr.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com>
In-Reply-To: <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@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_13205C286662DE4387D9AF3AC30EF456D3F3507F08EMBX01WFjnprn_"
MIME-Version: 1.0
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 02:27:04 -0000

--_000_13205C286662DE4387D9AF3AC30EF456D3F3507F08EMBX01WFjnprn_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Lorenzo,

You pose very reasonable questions.  I will try to reiterate them:


1)      What are the criteria for determining consensus? What makes you thi=
nk that there was no consensus on 6-to-4-historic?

2)      What makes you think that the new draft is just as good?

3)      What makes you think that the new draft will do any better than 6-t=
o-4-historic?

Responses follow:


1)      Because we do not vote in the IETF, the process for determining con=
sensus is squishy. A simple majority does not win the day. A few strongly h=
eld objections backed by even a scintilla of technical rational can increas=
e the size of the super-majority required to declare consensus. While it wa=
s not clear that the IETF has achieved consensus regarding 6-to-4-historic,=
 it also was not clear that the IETF had not achieved consensus.  In this c=
ase, we had a choice between spending cycles arguing about consensus, or fi=
nding a solution that everybody could live with.

2)      IMHO, the new draft will not be as good as 6-to-4-historic. However=
, it solves the operational problem by disabling 6-to-4 by default. That's =
much better than nothing.

3)      I have been working behind the scenes with a few of those who objec=
ted to 6-to-4-historic. They didn't object to the new draft. However, I inv=
ite those people to speak for themselves.

                                                                           =
                                  Ron


From: Lorenzo Colitti [mailto:lorenzo@google.com]
Sent: Saturday, July 02, 2011 2:55 PM
To: Ronald Bonica
Cc: v6ops@ietf.org; IETF Discussion
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic

On Sat, Jul 2, 2011 at 6:36 PM, Ronald Bonica <rbonica@juniper.net<mailto:r=
bonica@juniper.net>> wrote:
- In order for the new draft to be published, it must achieve both V6OPS WG=
 and IETF consensus

If anyone objects to this course of action, please speak up soon.

Great, back to square one.

Is the reasoning behind the decision explained somewhere? My reading of the=
 threads on the subject in v6ops was that the opposition to 6to4-historic w=
as a small but vocal minority, and I thought that qualified as rough consen=
sus. But perhaps I missed some discussion.

Also, why do the author and the chairs think that the new draft will do any=
 better than 6to4-historic? I would assume that the same people who spoke u=
p against 6to4-historic will speak up against the new document, and since t=
hat level of opposition was sufficient to prevent the publication of 6to4-h=
istoric, it may be sufficient to prevent publication of the new document as=
 well. If so, we will have spent 3-6 months arguing about it for naught.

Please, nobody answer this question with "welcome to the IETF" :-)

--_000_13205C286662DE4387D9AF3AC30EF456D3F3507F08EMBX01WFjnprn_
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=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft 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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:632365828;
	mso-list-type:hybrid;
	mso-list-template-ids:1789323666 67698705 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:2137137626;
	mso-list-type:hybrid;
	mso-list-template-ids:-448608868 67698705 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	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 vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Lorenzo,<=
o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;f=
ont-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></=
p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
","sans-serif";color:#1F497D'>You pose very reasonable questions. &nbsp;I w=
ill try to reiterate them:<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'=
><o:p>&nbsp;</o:p></span></p><p class=3DMsoListParagraph style=3D'text-inde=
nt:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style=3D'font=
-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style=
=3D'mso-list:Ignore'>1)<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span style=3D'font-=
size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>What are the =
criteria for determining consensus? What makes you think that there was no =
consensus on 6-to-4-historic?<o:p></o:p></span></p><p class=3DMsoListParagr=
aph style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportList=
s]><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color=
:#1F497D'><span style=3D'mso-list:Ignore'>2)<span style=3D'font:7.0pt "Time=
s New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]=
><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#=
1F497D'>What makes you think that the new draft is just as good?<o:p></o:p>=
</span></p><p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list=
:l0 level1 lfo1'><![if !supportLists]><span style=3D'font-size:11.0pt;font-=
family:"Calibri","sans-serif";color:#1F497D'><span style=3D'mso-list:Ignore=
'>3)<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; </span></span></span><![endif]><span style=3D'font-size:11.0pt;font-fa=
mily:"Calibri","sans-serif";color:#1F497D'>What makes you think that the ne=
w draft will do any better than 6-to-4-historic?<o:p></o:p></span></p><p cl=
ass=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><sp=
an style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F49=
7D'>Responses follow:<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p=
>&nbsp;</o:p></span></p><p class=3DMsoListParagraph style=3D'text-indent:-.=
25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span style=3D'font-size=
:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style=3D'ms=
o-list:Ignore'>1)<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span style=3D'font-size:1=
1.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Because we do not v=
ote in the IETF, the process for determining consensus is squishy. A simple=
 majority does not win the day. A few strongly held objections backed by ev=
en a scintilla of technical rational can increase the size of the super-maj=
ority required to declare consensus. While it was not clear that the IETF h=
as achieved consensus regarding 6-to-4-historic, it also was not clear that=
 the IETF had not achieved consensus. &nbsp;In this case, we had a choice b=
etween spending cycles arguing about consensus, or finding a solution that =
everybody could live with.<o:p></o:p></span></p><p class=3DMsoListParagraph=
 style=3D'text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1=
F497D'><span style=3D'mso-list:Ignore'>2)<span style=3D'font:7.0pt "Times N=
ew Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><s=
pan style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F4=
97D'>IMHO, the new draft will not be as good as 6-to-4-historic. However, i=
t solves the operational problem by disabling 6-to-4 by default. That&#8217=
;s much better than nothing.<o:p></o:p></span></p><p class=3DMsoListParagra=
ph style=3D'text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists=
]><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:=
#1F497D'><span style=3D'mso-list:Ignore'>3)<span style=3D'font:7.0pt "Times=
 New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1=
F497D'>I have been working behind the scenes with a few of those who object=
ed to 6-to-4-historic. They didn&#8217;t object to the new draft. However, =
I invite those people to speak for themselves.<o:p></o:p></span></p><p clas=
s=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-s=
erif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span=
 style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D=
'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Ron<o:p></o:p></span></p=
><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri"=
,"sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNorm=
al><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color=
:#1F497D'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;border-top:=
solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal style=
=3D'margin-left:.5in'><b><span style=3D'font-size:10.0pt;font-family:"Tahom=
a","sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-famil=
y:"Tahoma","sans-serif"'> Lorenzo Colitti [mailto:lorenzo@google.com] <br><=
b>Sent:</b> Saturday, July 02, 2011 2:55 PM<br><b>To:</b> Ronald Bonica<br>=
<b>Cc:</b> v6ops@ietf.org; IETF Discussion<br><b>Subject:</b> Re: [v6ops] d=
raft-ietf-v6ops-6to4-to-historic<o:p></o:p></span></p></div><p class=3DMsoN=
ormal style=3D'margin-left:.5in'><o:p>&nbsp;</o:p></p><div><p class=3DMsoNo=
rmal style=3D'margin-left:.5in'>On Sat, Jul 2, 2011 at 6:36 PM, Ronald Boni=
ca &lt;<a href=3D"mailto:rbonica@juniper.net">rbonica@juniper.net</a>&gt; w=
rote:<o:p></o:p></p><p class=3DMsoNormal style=3D'margin-left:.5in'>- In or=
der for the new draft to be published, it must achieve both V6OPS WG and IE=
TF consensus<br><br>If anyone objects to this course of action, please spea=
k up soon.<o:p></o:p></p><div><p class=3DMsoNormal style=3D'margin-left:.5i=
n'><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal style=3D'margin-lef=
t:.5in'>Great, back to square one.<o:p></o:p></p></div><div><p class=3DMsoN=
ormal style=3D'margin-left:.5in'><o:p>&nbsp;</o:p></p></div><div><p class=
=3DMsoNormal style=3D'margin-left:.5in'>Is the reasoning behind the decisio=
n explained somewhere?&nbsp;My reading of the threads on the subject in v6o=
ps was that the opposition to 6to4-historic was a small but vocal minority,=
 and I thought that qualified as rough consensus. But perhaps I missed some=
 discussion.<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'margin-=
left:.5in'><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal style=3D'ma=
rgin-left:.5in'>Also, why do the author and the chairs think that the new d=
raft will do any better than 6to4-historic? I would assume that the same pe=
ople who spoke up against 6to4-historic will speak up against the new docum=
ent, and since that level of opposition was sufficient to prevent the publi=
cation of&nbsp;6to4-historic, it may be sufficient to prevent publication o=
f the new document as well.&nbsp;If so, we will have spent 3-6 months argui=
ng about it for naught.<o:p></o:p></p></div><div><p class=3DMsoNormal style=
=3D'margin-left:.5in'><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal =
style=3D'margin-left:.5in'>Please, nobody answer this question with &quot;w=
elcome to the IETF&quot; :-)<o:p></o:p></p></div></div></div></body></html>=

--_000_13205C286662DE4387D9AF3AC30EF456D3F3507F08EMBX01WFjnprn_--

From dougb@dougbarton.us  Sat Jul  2 19:39:13 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 E7D7521F8671 for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 19:39:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.513
X-Spam-Level: 
X-Spam-Status: No, score=-3.513 tagged_above=-999 required=5 tests=[AWL=0.086,  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 hiQ5GbMWN31F for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 19:39:13 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 0C4AE21F866E for <ietf@ietf.org>; Sat,  2 Jul 2011 19:39:12 -0700 (PDT)
Received: (qmail 7012 invoked by uid 399); 3 Jul 2011 02:39:07 -0000
Received: from unknown (HELO 65-241-43-4.globalsuite.net) (dougb@dougbarton.us@65.241.43.4) by mail2.fluidhosting.com with ESMTPAM; 3 Jul 2011 02:39:07 -0000
X-Originating-IP: 65.241.43.4
X-Sender: dougb@dougbarton.us
Message-ID: <4E0FD649.6000305@dougbarton.us>
Date: Sat, 02 Jul 2011 19:39:05 -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.18) Gecko/20110624 Thunderbird/3.1.11
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net>	<CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F3507F08@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F3507F08@EMBX01-WF.jnpr.net>
X-Enigmail-Version: 1.1.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 02:39:14 -0000

On 07/02/2011 19:22, Ronald Bonica wrote:
> 1)Because we do not vote in the IETF, the process for determining
> consensus is squishy. A simple majority does not win the day. A few
> strongly held objections backed by even a scintilla of technical
> rational can increase the size of the super-majority required to declare
> consensus. While it was not clear that the IETF has achieved consensus
> regarding 6-to-4-historic, it also was not clear that the IETF had not
> achieved consensus.  In this case, we had a choice between spending
> cycles arguing about consensus, or finding a solution that everybody
> could live with.

IMO that is the wrong goal. Consensus does not mean universal agreement. 
Trying to get "a solution that everybody could live with" all too often 
results in a product with no operational value.


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  Sat Jul  2 19:44:27 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 BB6B421F8501 for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 19:44:27 -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 7cLw+9whpNFy for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 19:44:27 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id B33DC21F84F6 for <ietf@ietf.org>; Sat,  2 Jul 2011 19:44:26 -0700 (PDT)
Received: (qmail 10313 invoked by uid 399); 3 Jul 2011 02:44:25 -0000
Received: from unknown (HELO 65-241-43-4.globalsuite.net) (dougb@dougbarton.us@65.241.43.4) by mail2.fluidhosting.com with ESMTPAM; 3 Jul 2011 02:44:25 -0000
X-Originating-IP: 65.241.43.4
X-Sender: dougb@dougbarton.us
Message-ID: <4E0FD788.3000305@dougbarton.us>
Date: Sat, 02 Jul 2011 19:44:24 -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.18) Gecko/20110624 Thunderbird/3.1.11
MIME-Version: 1.0
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net>	<CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com>	<BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com> <20110703112048.4a3c7111@opy.nosense.org>
In-Reply-To: <20110703112048.4a3c7111@opy.nosense.org>
X-Enigmail-Version: 1.1.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 02:44:27 -0000

On 07/02/2011 18:50, Mark Smith wrote:
> Where is the evidence that 6to4 is holding back native IPv6
> deployment?

It's been discussed ad nauseum in numerous fora. Bad 6to4 (which almost 
all of it is) results in a poor user experience when the largest content 
providers enable AAAA records. Thus, they are less inclined to enable them.

I realize that there are a lot of people that dismiss both the evidence 
that's been put forward and the rationale, but it's been presented and 
discussed pretty thoroughly.


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 jnc@mercury.lcs.mit.edu  Sat Jul  2 20:05:52 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 37D0921F86A1; Sat,  2 Jul 2011 20:05:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NYvsS+EmyH6p; Sat,  2 Jul 2011 20:05:51 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id B413021F868E; Sat,  2 Jul 2011 20:05:51 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 7BF9618C1BA; Sat,  2 Jul 2011 23:05:48 -0400 (EDT)
To: ietf@ietf.org, v6ops@ietf.org
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Message-Id: <20110703030548.7BF9618C1BA@mercury.lcs.mit.edu>
Date: Sat,  2 Jul 2011 23:05:48 -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: Sun, 03 Jul 2011 03:05:52 -0000

    > From: Cameron Byrne <cb.list6@gmail.com>

    > It is a shame that work that directly removes barriers to REAL ipv6
    > deployment gets shouted down

So, perhaps you can explain something to me, since nobody else has been
able to.

I think there is pretty much complete consensus that i) 6to4 doesn't work
in several very common environments (behind a NAT, etc, etc), and that
therefore, ii) at the very least, it should be disabled by default (and
therefore only turned on by knowledgeable users who know they are not in
one of those situations).

Given and assuming a document that makes all that formal, _what else_ does
the _additional_ step of making 6to4 historic buy?

Are you thinking that people will see this knob called '6to4' and turn it
on, and cause support issues? This seems unlikely to me - e.g. they don't
seem to commonly turn off DHCP on their NAT boxes (a switch most NAT boxes
seem to provide).

Or perhaps the concept is that nuking 6to4 will help force ISPs to deploy
native IPv6, since it removes one way for users to get IPv6 if their
provider doesn't supply it? If so, why not ditch Teredo, too? (Not to
mention that 'mandate it and they will come' hasn't worked to well so far.)

In short, I just cannot fathom what concrete benefit the _additional_ step
of marking the protocol 'historic' provides, _over and above_ just issuing
the 'do not enable 6to4 automatically because it has problems' document.

Can you point to such a benefit?

	Noel

From melinda.shore@gmail.com  Sat Jul  2 20:08:57 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 AC21B21F86B2; Sat,  2 Jul 2011 20:08:57 -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 cLrgKm128EQx; Sat,  2 Jul 2011 20:08: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 35E0E21F86B1; Sat,  2 Jul 2011 20:08:57 -0700 (PDT)
Received: by pzk5 with SMTP id 5so5441275pzk.31 for <multiple recipients>; Sat, 02 Jul 2011 20:08:56 -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=tr5nBUmA0YlgeOd/Rt6/Kt8PJ42ZDOYwRmJBnKWlJ6g=; b=AVMDY4ooN65lRDiyAbX4BO9ORCcXPqk0UYNohbyjuQsrcWGoqAYCAW5sMm2DO3QgBS ZoVKklbSJcMejIfOpx1hvgE4wu4muI4ZOIm5wQuGiACEezyNhRg/TXopukEMnXTzKjSZ iV+lmpfWA31TXJea61S8xrPuA4hq2NTRjAESc=
Received: by 10.142.249.4 with SMTP id w4mr2221507wfh.118.1309662536748; Sat, 02 Jul 2011 20:08:56 -0700 (PDT)
Received: from polypro.local (216-67-41-245-rb1.fai.dsl.dynamic.acsalaska.net [216.67.41.245]) by mx.google.com with ESMTPS id w24sm3171876wfd.17.2011.07.02.20.08.54 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 02 Jul 2011 20:08:55 -0700 (PDT)
Message-ID: <4E0FDD44.2030207@gmail.com>
Date: Sat, 02 Jul 2011 19:08:52 -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: Doug Barton <dougb@dougbarton.us>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net>	<CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F3507F08@EMBX01-WF.jnpr.net> <4E0FD649.6000305@dougbarton.us>
In-Reply-To: <4E0FD649.6000305@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 03:08:57 -0000

On 7/2/11 6:39 PM, Doug Barton wrote:
> IMO that is the wrong goal. Consensus does not mean universal agreement.
> Trying to get "a solution that everybody could live with" all too often
> results in a product with no operational value.

"Everybody can live with" is pretty much the universal operating
definition of "consensus" in organizations that use consensus
decision-making.  I've got some concerns, as well, that effort
is being put into technologies that there's no incentive to use,
but in terms of *process* Ron is spot-on.

Melinda

From moore@network-heretics.com  Sat Jul  2 20:11:07 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 1354A21F86BF; Sat,  2 Jul 2011 20:11:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.517
X-Spam-Level: 
X-Spam-Status: No, score=-3.517 tagged_above=-999 required=5 tests=[AWL=0.081,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KPEVMZ8t9pho; Sat,  2 Jul 2011 20:11:06 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 71B4721F86BA; Sat,  2 Jul 2011 20:11:06 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 24914207EF; Sat,  2 Jul 2011 23:11:06 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Sat, 02 Jul 2011 23:11: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:message-id:references:to; s=smtpout; bh=42755ZXt8T0wBFyoIcKDMRMdMdk=; b=YkVijo4vVOpUYQksklAJ0OnNzICsxuGuuxj3dhElwbW9pHCmp+0gTKzHRIA1FHVQ9FwVDNI+O3Gmn4ICwkV3CGJN3Mrv8XSbIwJGOJlZgju2vgxqh5+7K0tt7KtCphvJmxadGZbfhFk6ALmX/FRiAinLrAN3o3bXQupWro3BlA8=
X-Sasl-enc: oSMYFF5J/NcilPC+4NdTMxfOua8GRvvEfbkURmMuINqb 1309662665
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 05C55400782; Sat,  2 Jul 2011 23:11:04 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-111-642965515
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com>
Date: Sat, 2 Jul 2011 23:10:47 -0400
Message-Id: <E817A524-9DB7-4553-A76F-25A9907E7C2D@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com>
To: Cameron Byrne <cb.list6@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 03:11:07 -0000

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

On Jul 2, 2011, at 3:21 PM, Cameron Byrne wrote:
> I saw the same thing. It is a shame that work that directly removes =
barriers to REAL ipv6 deployment gets shouted down by a few people not =
involved in REAL ipv6 deployment
>=20

I find myself wondering what you mean by REAL IPv6.  For me, REAL IPv6 =
is code that uses the IPv6 programming model, 128 bit addresses, =
end-to-end transparency, no NATs.  6to4 certainly qualifies.

Keith


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

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jul 2, 2011, at 3:21 PM, Cameron Byrne =
wrote:</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; "><p>I saw the =
same thing. It is a shame that work that directly removes barriers to =
REAL ipv6 deployment gets shouted down by a few people not involved in =
REAL ipv6 deployment</p></span></blockquote><br></div><div>I find myself =
wondering what you mean by REAL IPv6. &nbsp;For me, REAL IPv6 is code =
that uses the IPv6 programming model, 128 bit addresses, end-to-end =
transparency, no NATs. &nbsp;6to4 certainly =
qualifies.</div><div><br></div><div>Keith</div><div><br></div></body></htm=
l>=

--Apple-Mail-111-642965515--

From moore@network-heretics.com  Sat Jul  2 20:12:05 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 8D00721F86E3; Sat,  2 Jul 2011 20:12:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.22
X-Spam-Level: 
X-Spam-Status: No, score=-3.22 tagged_above=-999 required=5 tests=[AWL=-0.222,  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 L1aGcJU7+DGw; Sat,  2 Jul 2011 20:12: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 7919E21F86E4; Sat,  2 Jul 2011 20:12:02 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id 2DFE5207B5; Sat,  2 Jul 2011 23:12:02 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Sat, 02 Jul 2011 23:12: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:message-id:references:to; s=smtpout; bh=4dY+MfqvK0OjceVca2gdYy8l5YE=; b=ieefxvqlOno4eAnt4yjMG0Qz0UCYlSs/84ow3fzS5ZQG6XsHMd8MLNx+NcmCisiANQHi+nwOvJO6H8WEyIzv0PsT5i9xVPfRDgJIhuTqzABpVaT+z2XXCUTPT2awD/IeFcpjHnnYprbBJFjXONiSGyXPintEb5t+rS6yayoagiY=
X-Sasl-enc: WObtovw2RtEQF+AMrYn8+KbANYsHa5xpXf6c5HTRysIp 1309662721
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 1B8EA400782; Sat,  2 Jul 2011 23:12:01 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-112-643022195
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <CAKD1Yr0=pJwOzRvTNskS7YDBNa7Fc=8srGzH2qJUKwGHdCAELg@mail.gmail.com>
Date: Sat, 2 Jul 2011 23:11:43 -0400
Message-Id: <A1DA82E2-B979-4719-9F78-DEB263B256A1@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <DE414D2B-82ED-4C32-AFDF-EDAAB6D743B2@network-heretics.com> <CAKD1Yr0=pJwOzRvTNskS7YDBNa7Fc=8srGzH2qJUKwGHdCAELg@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 03:12:05 -0000

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

On Jul 2, 2011, at 9:10 PM, Lorenzo Colitti wrote:

> On Sat, Jul 2, 2011 at 10:02 PM, Keith Moore =
<moore@network-heretics.com> wrote:
> > Is the reasoning behind the decision explained somewhere? My reading =
of the threads on the subject in v6ops was that the opposition to =
6to4-historic was a small but vocal minority, and I thought that =
qualified as rough consensus.
>=20
> Even if there was rough consensus within v6ops, rough consensus of =
v6ops does not equate to rough consensus of the entire IETF community.
>=20
> And who says that "rough consensus of the entire IETF community" is =
that this draft should not be published? Were there public discussions =
to that effect that came to this conclusion?

There's clearly a lack of consensus to support it.

Keith


--Apple-Mail-112-643022195
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 Jul 2, 2011, at 9:10 PM, Lorenzo Colitti wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Sat, Jul 2, 2011 at 10:02 PM, 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 class="im">&gt; Is the reasoning behind the decision explained somewhere? My reading of the threads on the subject in v6ops was that the opposition to 6to4-historic was a small but vocal minority, and I thought that qualified as rough consensus.<br>


<br>
</div>Even if there was rough consensus within v6ops, rough consensus of v6ops does not equate to rough consensus of the entire IETF community.<br></blockquote><div><br></div><div>And who says that "rough consensus of the entire IETF community"&nbsp;is that this draft should not be published? Were there public discussions to that effect that came to this conclusion?</div>

</div></blockquote><br></div><div>There's clearly a lack of consensus to support it.</div><div><br></div><div>Keith</div><div><br></div></body></html>
--Apple-Mail-112-643022195--

From moore@network-heretics.com  Sat Jul  2 20:15: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 2319821F86F9; Sat,  2 Jul 2011 20:15:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.511
X-Spam-Level: 
X-Spam-Status: No, score=-3.511 tagged_above=-999 required=5 tests=[AWL=0.087,  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 MFme1Tun3G5z; Sat,  2 Jul 2011 20:15: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 9512521F86EA; Sat,  2 Jul 2011 20:15:12 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 4B07B20834; Sat,  2 Jul 2011 23:15:12 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Sat, 02 Jul 2011 23:15: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=fYMKkohlyBAoTkhZurh9g5VFceY=; b=UbcKQx1RHKLKJ9t3EAIiWfRFl1GgzT4DeQKViQEB7U9/xRd5oIPzpKLspPXiDPGOHGFQqg21FUeP7HF+LF5lQkc29xtnQseyO53L2NHGyMk5E/VeGNK8JY2DJIw49DYyzaqwsFnNvFXN+YoEzKcQMAQOuaT7tqrqBQCyfxxS50Q=
X-Sasl-enc: sS74L6oRMJzubBc9XT2FGhPy3HVVTxbt84h/Nw/hpkD3 1309662911
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 335AF402C3F; Sat,  2 Jul 2011 23:15:11 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-113-643211734
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <CAAedzxoFxM--XmLsATcwQiBjOoo_O5n4zcN4E02QSpY2NCOjwA@mail.gmail.com>
Date: Sat, 2 Jul 2011 23:14:53 -0400
Message-Id: <F6B39069-1644-4BE4-A00D-2D3EAC42E668@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <20110703100844.68eb8b7d@opy.nosense.org> <CAAedzxpCsxW2zJtpGa9HRMRACkK1defrt2g2Xao_y0f7qevvkA@mail.gmail.com> <20110703112420.3fcaa58c@opy.nosense.org> <CAAedzxoFxM--XmLsATcwQiBjOoo_O5n4zcN4E02QSpY2NCOjwA@mail.gmail.com>
To: Erik Kline <ek@google.com>
X-Mailer: Apple Mail (2.1084)
Cc: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>, "v6ops@ietf.org" <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: Sun, 03 Jul 2011 03:15:13 -0000

--Apple-Mail-113-643211734
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

On Jul 2, 2011, at 10:00 PM, Erik Kline wrote:

>> Since 6rd depends on 6to4, as it is a variant of it, would 6to4 being
>> declared historic also mean that 6rd needs to become historic as well?
> 
> http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05
> Section 1, in which the draft clarifies that 6rd supersedes 6to4,

which is of course completely incorrect.

Keith



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

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jul 2, 2011, at 10:00 PM, Erik Kline 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; "><blockquote =
type=3D"cite">Since 6rd depends on 6to4, as it is a variant of it, would =
6to4 being<br></blockquote><blockquote type=3D"cite">declared historic =
also mean that 6rd needs to become historic as =
well?<br></blockquote><br><a =
href=3D"http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05">h=
ttp://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05</a><br>Sect=
ion 1, in which the draft clarifies that 6rd supersedes =
6to4,<br></span></blockquote><br></div><div>which is of course =
completely =
incorrect.</div><div><br></div><div>Keith</div><div><br></div><div><br></d=
iv></body></html>=

--Apple-Mail-113-643211734--

From moore@network-heretics.com  Sat Jul  2 20:20: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 3978321F86F5; Sat,  2 Jul 2011 20:20:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.214
X-Spam-Level: 
X-Spam-Status: No, score=-3.214 tagged_above=-999 required=5 tests=[AWL=-0.216, 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 4M31d8-W+iIn; Sat,  2 Jul 2011 20:20: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 5F7CD21F86C0; Sat,  2 Jul 2011 20:20:57 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 175EB2074C; Sat,  2 Jul 2011 23:20:57 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Sat, 02 Jul 2011 23:20:57 -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=yu0HP7mIftKZwNl/Je9pW3TqftE=; b=sFjKx0xINnNsnOshAjHe52+so4bH/iG3Ngv0WlsF1NzNIsXViy4h4FBEE6CGdSCuZG8diH/PTD93DT54pzeKPzqfGdpPkmIdx4qUK01gSzDaj6nC2RzQp0MRDfOg2UNdfs+0V/TKysc8mU99rJ53j3pyVx4avpE1vYI6SCSkee4=
X-Sasl-enc: Sni4OBGbe9THY2gQTHljkohdDIescHVSTj0VsbwBhnbI 1309663256
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 A62BD4033D6; Sat,  2 Jul 2011 23:20:55 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-114-643556105
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E0FD649.6000305@dougbarton.us>
Date: Sat, 2 Jul 2011 23:20:37 -0400
Message-Id: <99063FC4-467D-477A-A369-D22AA60881FD@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net>	<CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F3507F08@EMBX01-WF.jnpr.net> <4E0FD649.6000305@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 03:20:59 -0000

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

On Jul 2, 2011, at 10:39 PM, Doug Barton wrote:

> On 07/02/2011 19:22, Ronald Bonica wrote:
>> 1)Because we do not vote in the IETF, the process for determining
>> consensus is squishy. A simple majority does not win the day. A few
>> strongly held objections backed by even a scintilla of technical
>> rational can increase the size of the super-majority required to =
declare
>> consensus. While it was not clear that the IETF has achieved =
consensus
>> regarding 6-to-4-historic, it also was not clear that the IETF had =
not
>> achieved consensus.  In this case, we had a choice between spending
>> cycles arguing about consensus, or finding a solution that everybody
>> could live with.
>=20
> IMO that is the wrong goal. Consensus does not mean universal =
agreement. Trying to get "a solution that everybody could live with" all =
too often results in a product with no operational value.

IMO you're thinking about this the wrong way.  if a document is to be =
published with IETF's imprimatur, it needs to adhere to IETF's rules.  =
Those rules require, for a standards action, at least rough =
community-wide consensus. =20

When a narrowly focused working group declares consensus within itself, =
that clearly doesn't speak for the whole IETF.  The fact that the =
consensus was quite rough even within the v6ops group should have been =
understood as a sign that the proposed action might not win consensus =
overall - especially given that several of the objections came from =
non-operators who are not well represented in v6ops.

Keith


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

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jul 2, 2011, at 10:39 PM, Doug Barton wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>On =
07/02/2011 19:22, Ronald Bonica wrote:<br><blockquote =
type=3D"cite">1)Because we do not vote in the IETF, the process for =
determining<br></blockquote><blockquote type=3D"cite">consensus is =
squishy. A simple majority does not win the day. A =
few<br></blockquote><blockquote type=3D"cite">strongly held objections =
backed by even a scintilla of technical<br></blockquote><blockquote =
type=3D"cite">rational can increase the size of the super-majority =
required to declare<br></blockquote><blockquote type=3D"cite">consensus. =
While it was not clear that the IETF has achieved =
consensus<br></blockquote><blockquote type=3D"cite">regarding =
6-to-4-historic, it also was not clear that the IETF had =
not<br></blockquote><blockquote type=3D"cite">achieved consensus. =
&nbsp;In this case, we had a choice between =
spending<br></blockquote><blockquote type=3D"cite">cycles arguing about =
consensus, or finding a solution that =
everybody<br></blockquote><blockquote type=3D"cite">could live =
with.<br></blockquote><br>IMO that is the wrong goal. Consensus does not =
mean universal agreement. Trying to get "a solution that everybody could =
live with" all too often results in a product with no operational =
value.<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>IMO =
you're thinking about this the wrong way. &nbsp;if a document is to be =
published with IETF's imprimatur, it needs to adhere to IETF's rules. =
&nbsp;Those rules require, for a standards action, at least rough =
community-wide consensus. &nbsp;</div><div><br></div><div>When a =
narrowly focused working group declares consensus within itself, that =
clearly doesn't speak for the whole IETF. &nbsp;The fact that the =
consensus was quite rough even within the v6ops group should have been =
understood as a sign that the proposed action might not win consensus =
overall - especially given that several of the objections came from =
non-operators who are not well represented in =
v6ops.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-114-643556105--

From michel@arneill-py.sacramento.ca.us  Sat Jul  2 20:21:48 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 2236921F861C; Sat,  2 Jul 2011 20:21:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.665
X-Spam-Level: 
X-Spam-Status: No, score=-1.665 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bQAL3H4z3+Ab; Sat,  2 Jul 2011 20:21:47 -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 7BA6721F85D9; Sat,  2 Jul 2011 20:21:47 -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: draft-ietf-v6ops-6to4-to-historic
x-mimeole: Produced By Microsoft Exchange V6.5
Date: Sat, 2 Jul 2011 20:21:47 -0700
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF5DD@newserver.arneill-py.local>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-v6ops-6to4-to-historic
Thread-Index: Acw41iMv6/qWspvgTzCQB463JqIp+AAWaB7g
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Ronald Bonica" <rbonica@juniper.net>, <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: Sun, 03 Jul 2011 03:21:48 -0000

Subject to reading the not-available-yet text, I support this approach.
It appears to be reasonable political compromise.

Michel.


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Ronald Bonica
Sent: Saturday, July 02, 2011 9:36 AM
To: v6ops@ietf.org; IETF Discussion
Subject: draft-ietf-v6ops-6to4-to-historic

Folks,

Whereas there has been considerable controversy regarding
draft-ietf-v6ops-6to4-to-historic, the v6ops chairs and document author
have agreed to the following course of action:

- the V6OPS WG will withdraw its request to publish
draft-ietf-v6ops-6to4-to-historic
- The author will introduce a new draft, intended for standards track
publication. The new draft will update RFCs 3056 and 3068. It will say
that if 6-to-4 is implemented, it must be turned off by default.=20
- In order for the new draft to be published, it must achieve both V6OPS
WG and IETF consensus

If anyone objects to this course of action, please speak up soon.

                                                    Ron
                                                    <Speaking as OPS
Area AD>
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

From rbonica@juniper.net  Sat Jul  2 20:36:38 2011
Return-Path: <rbonica@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 505D921F865C; Sat,  2 Jul 2011 20:36:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.268
X-Spam-Level: 
X-Spam-Status: No, score=-106.268 tagged_above=-999 required=5 tests=[AWL=-0.269, 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 Z3KUJgzpGn3A; Sat,  2 Jul 2011 20:36:37 -0700 (PDT)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id F067821F8652; Sat,  2 Jul 2011 20:36:34 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKTg/jwcvfip3vVp0DtyymeNJgLTBDDd44@postini.com; Sat, 02 Jul 2011 20:36:37 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.2.254.0; Sat, 2 Jul 2011 20:31:58 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Sat, 2 Jul 2011 23:31:57 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Randy Bush <randy@psg.com>, Lorenzo Colitti <lorenzo@google.com>
Date: Sat, 2 Jul 2011 23:31:55 -0400
Subject: RE: [v6ops] draft-ietf-v6ops-6to4-to-historic
Thread-Topic: [v6ops] draft-ietf-v6ops-6to4-to-historic
Thread-Index: Acw4/+4kG+zoOyaUR+WA27uNwTu/kgALaaKQ
Message-ID: <13205C286662DE4387D9AF3AC30EF456D3F3507F14@EMBX01-WF.jnpr.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <m2y60g9xiw.wl%randy@psg.com>
In-Reply-To: <m2y60g9xiw.wl%randy@psg.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: IPv6 Ops 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: Sun, 03 Jul 2011 03:36:38 -0000

Randy,

You have three points that deserve to be addressed. These are:

1) "as measured on the real internet, not the ietf bar, 6to4 sucks caterpil=
lar snot"
2) "perhaps that minority was also vocal in the back room"
3) "yes, but that will be a year from now.  in the ietf, delay is one form =
of death"

Responses follow:

1) While not stated so colorfully, draft-ietf-v6ops-6to4-advisory made this=
 point. It has been approved for publication.
2) While there was no back-room activity, an appeal had been filed at the W=
G level. Since WG consensus was stronger than IETF consensus, it is reasona=
ble to assume that the appeal would be escalated to the IESG level if it wa=
s not approved at the WG level. So, any way you look at it, there would be =
delays.
3) The new document may not take a year to publish. Since it is a short dra=
ft, it could be produced in a few days. Once it is produced, we could immed=
iately initiate a WG last call and an IETF last call immediately after that=
. So, we might be talking about a six-week delay.

Now, I have a question for you, Lorenzo and Doug. If our goal is to take 6-=
to-4 off of the Internet, does not disabling it by default solve most of th=
e problem? AFAIKS, very few users would enable it and service providers wou=
ld not be economically incented to support 6-to-4 relay routers.=20

Comments?

                                    Ron




=20

-----Original Message-----
From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of R=
andy Bush
Sent: Saturday, July 02, 2011 5:35 PM
To: Lorenzo Colitti
Cc: IPv6 Ops WG; IETF Discussion
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic

>> If anyone objects to this course of action, please speak up soon.

i object.  as measured on the real internet, not the ietf bar, 6to4
sucks caterpillar snot.  it is damaging to the users and to the users'
view of ipv6.

> Great, back to square one.
>=20
> Is the reasoning behind the decision explained somewhere? My reading of t=
he
> threads on the subject in v6ops was that the opposition to 6to4-historic =
was
> a small but vocal minority, and I thought that qualified as rough consens=
us.

perhaps that minority was also vocal in the back room

> But perhaps I missed some discussion.
>=20
> Also, why do the author and the chairs think that the new draft will do a=
ny
> better than 6to4-historic? I would assume that the same people who spoke =
up
> against 6to4-historic will speak up against the new document,

yes, but that will be a year from now.  in the ietf, delay is one form
of death.

> and since that level of opposition was sufficient to prevent the
> publication of 6to4-historic, it may be sufficient to prevent
> publication of the new document as well. If so, we will have spent 3-6
> months arguing about it for naught.
>=20
> Please, nobody answer this question with "welcome to the IETF" :-)

this is nutso.  but this is normal.

welcome to the ietf

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

From joelja@bogus.com  Sat Jul  2 20:41:11 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 674BB21F8622; Sat,  2 Jul 2011 20:41:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.049, 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 vLytmaxKRLlP; Sat,  2 Jul 2011 20:41:11 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 89C1621F861E; Sat,  2 Jul 2011 20:41:10 -0700 (PDT)
Received: from [192.168.11.127] (c-76-115-172-69.hsd1.wa.comcast.net [76.115.172.69]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p633euuE024477 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 3 Jul 2011 03:40:57 GMT (envelope-from joelja@bogus.com)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-8-644769954
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <F6B39069-1644-4BE4-A00D-2D3EAC42E668@network-heretics.com>
Date: Sat, 2 Jul 2011 20:40:51 -0700
Message-Id: <8EB62DB6-1073-40F1-AC26-071958FA9080@bogus.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <20110703100844.68eb8b7d@opy.nosense.org> <CAAedzxpCsxW2zJtpGa9HRMRACkK1defrt2g2Xao_y0f7qevvkA@mail.gmail.com> <20110703112420.3fcaa58c@opy.nosense.org> <CAAedzxoFxM--XmLsATcwQiBjOoo_O5n4zcN4E02QSpY2NCOjwA@mail.gmail.com> <F6B39069-1644-4BE4-A00D-2D3EAC42E668@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]); Sun, 03 Jul 2011 03:40:58 +0000 (UTC)
Cc: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>, Erik Kline <ek@google.com>, "v6ops@ietf.org" <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: Sun, 03 Jul 2011 03:41:11 -0000

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


On Jul 2, 2011, at 8:14 PM, Keith Moore wrote:

> On Jul 2, 2011, at 10:00 PM, Erik Kline wrote:
>=20
>>> Since 6rd depends on 6to4, as it is a variant of it, would 6to4 =
being
>>> declared historic also mean that 6rd needs to become historic as =
well?
>>=20
>> http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05
>> Section 1, in which the draft clarifies that 6rd supersedes 6to4,
>=20
> which is of course completely incorrect.

While 6rd shares a mechanism with 6 to 4 and can be implemented by =
reusing code, it is a mistake to conclude a standards action that =
impacts the later would impact the former, or that they are =
substitutable for each other.

> Keith
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


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

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jul 2, 2011, at 8:14 PM, 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 Jul 2, 2011, at =
10:00 PM, Erik Kline 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; "><blockquote =
type=3D"cite">Since 6rd depends on 6to4, as it is a variant of it, would =
6to4 being<br></blockquote><blockquote type=3D"cite">declared historic =
also mean that 6rd needs to become historic as =
well?<br></blockquote><br><a =
href=3D"http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05">h=
ttp://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05</a><br>Sect=
ion 1, in which the draft clarifies that 6rd supersedes =
6to4,<br></span></blockquote><br></div><div>which is of course =
completely incorrect.</div></div></blockquote><div><br></div><div>While =
6rd shares a mechanism with 6 to 4 and can be implemented by reusing =
code, it is a mistake to conclude a standards action that impacts the =
later would impact the former, or that they are substitutable for each =
other.</div><br><blockquote type=3D"cite"><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; =
"><div>Keith</div><div><br></div><div><br></div></div>____________________=
___________________________<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">https://www.ietf.org/m=
ailman/listinfo/ietf</a><br></blockquote></div><br></body></html>=

--Apple-Mail-8-644769954--

From moore@network-heretics.com  Sat Jul  2 20:44: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 CBDE721F8628; Sat,  2 Jul 2011 20:44:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.507
X-Spam-Level: 
X-Spam-Status: No, score=-3.507 tagged_above=-999 required=5 tests=[AWL=0.092,  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 SvfvOnUQ-ywP; Sat,  2 Jul 2011 20:44:08 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 483FA21F8624; Sat,  2 Jul 2011 20:44:08 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id DD24720681; Sat,  2 Jul 2011 23:44:07 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute5.internal (MEProxy); Sat, 02 Jul 2011 23:44: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:content-transfer-encoding:message-id:references:to; s=smtpout; bh=KFtKT1wOQMMFYg95XvMIWdKAuGw=; b=eBeArItriehufQIUPNWTU3BkfbjTVH4Ha3HaPvUrLoaWB5EKbOqD2gl27QFecbtvN5RBSy3eg466QZriKlJVCZ/m57F7dO11CDBWav9jjYAuUPiLZubRKFrCiwvdlfdUxQqtmelyDXSslr9DTXvsjVEdKO2E2mVo2+iveG0Ty80=
X-Sasl-enc: xXxK+SvQdMzqITS6vXVxEnfQPkViZSxv+0d9IT3KLdcz 1309664647
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 CCEDA403F96; Sat,  2 Jul 2011 23:44:06 -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: <4E0FC683.6020900@dougbarton.us>
Date: Sat, 2 Jul 2011 23:43:49 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B1D63130-A217-4AD3-BABA-41F109CEBD4C@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> <4E0E282B.1060400@voort.ca> <4E0E2A75.6040207@dougbarton.us> <F863D9FD-5A5F-4E6C-88D3-E0F941D79622@network-heretics.com> <4E0FC683.6020900@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
X-Mailer: Apple Mail (2.1084)
Cc: 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: Sun, 03 Jul 2011 03:44:08 -0000

On Jul 2, 2011, at 9:31 PM, Doug Barton wrote:

> On 07/01/2011 14:17, Keith Moore wrote:
>>=20
>>=20
>> Whenever people talk about the Internet as if it were just about
>> "access to content", I have to wonder.    The Internet has always
>> been more about conversation than content.
>=20
> The overwhelming majority of Internet users are consumers of content. =
Some of that content is stuff like Skype, instant messaging, etc.

The point is that the Internet is not primarily about producers in the =
center doling out content to users at the edge.  Granted, netflix uses a =
lot of bandwidth.  But a lot of what has driven use of the Internet, and =
continues to drive it, is users engaging in conversation of one form or =
another.  This was true when email and Usenet were the apps consuming =
the most bandwidth, and it's true today for Skype, Facebook, Youtube, =
IM, blogs, etc.

Meanwhile, traditional producer-to-consumer media channels of all types =
are steadily dying.   They tend to blame it on copyright violation, or =
"free" access to content on the Internet.  The real problem is that most =
of what they produce is crap.  They're stuck in an old model that says =
that a few people should decide what's good for everybody else, but now =
people are in a position to decide what's good for themselves and/or =
create their own content.

> The overwhelming majority of businesses that make the Internet work =
are the content providers, and the ISPs that enable the consumers of =
that content to reach it.
>=20
> Failure to recognize these 2 critical facts leads to producing =
standards documents that have no relevance in the real world.

Insistence on sticking to anachronistic models of "the real world" will =
do the same thing.  =20

Keith


From cb.list6@gmail.com  Sat Jul  2 21:02:05 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 A37A921F86A3; Sat,  2 Jul 2011 21:02:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.929
X-Spam-Level: 
X-Spam-Status: No, score=-1.929 tagged_above=-999 required=5 tests=[AWL=-0.830, BAYES_00=-2.599, MANGLED_SONATA=2.5, 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 Cbc9Ka3SWd8K; Sat,  2 Jul 2011 21:02:05 -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 BFBEF21F86A1; Sat,  2 Jul 2011 21:02:04 -0700 (PDT)
Received: by wwe5 with SMTP id 5so2839559wwe.13 for <multiple recipients>; Sat, 02 Jul 2011 21:02:03 -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:content-transfer-encoding; bh=ceWeITE2q0ONf7eHtHLii56jFmdL0ZO9Vt18y1kvF3o=; b=bQKEeG1uQqQWTdi/otK7NPw3etspKd9w1vZTTo7873Yd8WbAO/zmsl+1hMMlz2UBNr efdHmLVFBNsdHze/IICiweTjPURP5UphKDObZ2kcGCFiZINeosioGySxFGrUiM4uEpZv ex2aPF9auZqIYUgTYlkAZqyJgzZpFsDCSPKfE=
MIME-Version: 1.0
Received: by 10.216.63.131 with SMTP id a3mr3978240wed.64.1309665722780; Sat, 02 Jul 2011 21:02:02 -0700 (PDT)
Received: by 10.216.39.83 with HTTP; Sat, 2 Jul 2011 21:02:02 -0700 (PDT)
In-Reply-To: <E817A524-9DB7-4553-A76F-25A9907E7C2D@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com> <E817A524-9DB7-4553-A76F-25A9907E7C2D@network-heretics.com>
Date: Sat, 2 Jul 2011 21:02:02 -0700
Message-ID: <CAD6AjGTN0bi20TjidwwXeHB=CPyBSZWB4=Lka2YG-5FG4Y1+Pw@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
From: Cameron Byrne <cb.list6@gmail.com>
To: Keith Moore <moore@network-heretics.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 04:02:05 -0000

On Sat, Jul 2, 2011 at 8:10 PM, Keith Moore <moore@network-heretics.com> wr=
ote:
> On Jul 2, 2011, at 3:21 PM, Cameron Byrne wrote:
>
> I saw the same thing. It is a shame that work that directly removes barri=
ers
> to REAL ipv6 deployment gets shouted down by a few people not involved in
> REAL ipv6 deployment
>
> I find myself wondering what you mean by REAL IPv6. =A0For me, REAL IPv6 =
is
> code that uses the IPv6 programming model, 128 bit addresses, end-to-end
> transparency, no NATs. =A06to4 certainly qualifies.

That's not what it means to me.  REAL IPv6 is a replacement for IPv4
and can address greater than 100s of billions of endpoint and is
suitable for very large traffic loads.  As an access network provider,
i need content on native IPv6.  It does not make sense to anyone in my
organization or industry to deploy IPv6 unilaterally.  There is no
benefit in this approach vs just doing NAT444.  If there is IPv6
content on a meaningful scale ( by the numbers that means for "my
network": Google, Facebook, Yahoo and their CDNs ...), then i have a
solid business case for IPv6 access networks. Full Stop.

If the content guys say 6to4 is a pain, and they do, then i need to
help them find a way to solve that pain.  I operate in an address
exhausted world, so NAT44 is my only IPv4 tool for growth.

In the meantime, i null route the 6to4 anycast address because it
creates half open state in my CGN.  Been doing that for at least 5
years.  My next step is filtering AAAA over IPv4 access because 6to4
client brokeness won't die on its own, that will be rolled out in a
few months.  Operating a network means making the tweeks that keep the
wheels rolling, and we don't find many technology purist in my line of
work.

Other access providers like 6to4 so much that they want to NAT it.
This is the reason why historic is the proper term.

http://tools.ietf.org/html/draft-kuarsingh-v6ops-6to4-provider-managed-tunn=
el-02

I look forward to that discussion on ietf@

Cameron


> Keith
>

From dougb@dougbarton.us  Sat Jul  2 21:26:41 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 59CF321F86E3 for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 21:26:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.544
X-Spam-Level: 
X-Spam-Status: No, score=-3.544 tagged_above=-999 required=5 tests=[AWL=0.055,  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 2TU+aIMdAdBs for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 21:26:40 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 4FEE721F86E1 for <ietf@ietf.org>; Sat,  2 Jul 2011 21:26:40 -0700 (PDT)
Received: (qmail 15530 invoked by uid 399); 3 Jul 2011 04:26:36 -0000
Received: from unknown (HELO 65-241-43-4.globalsuite.net) (dougb@dougbarton.us@65.241.43.4) by mail2.fluidhosting.com with ESMTPAM; 3 Jul 2011 04:26:36 -0000
X-Originating-IP: 65.241.43.4
X-Sender: dougb@dougbarton.us
Message-ID: <4E0FEF7A.4060606@dougbarton.us>
Date: Sat, 02 Jul 2011 21:26:34 -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.18) Gecko/20110624 Thunderbird/3.1.11
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net>	<CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com>	<m2y60g9xiw.wl%randy@psg.com> <13205C286662DE4387D9AF3AC30EF456D3F3507F14@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F3507F14@EMBX01-WF.jnpr.net>
X-Enigmail-Version: 1.1.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Randy Bush <randy@psg.com>, IPv6 Ops 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: Sun, 03 Jul 2011 04:26:41 -0000

On 07/02/2011 20:31, Ronald Bonica wrote:
> Randy,
>
> You have three points that deserve to be addressed. These are:
>
> 1) "as measured on the real internet, not the ietf bar, 6to4 sucks caterpillar snot"
> 2) "perhaps that minority was also vocal in the back room"
> 3) "yes, but that will be a year from now.  in the ietf, delay is one form of death"
>
> Responses follow:
>
> 1) While not stated so colorfully, draft-ietf-v6ops-6to4-advisory made this point. It has been approved for publication.
> 2) While there was no back-room activity,

You yourself mentioned that you were in private discussion with some who 
objected to the "historic" draft. There's nothing wrong with that, it's 
how the world works, and personally I would expect it of you. But please 
don't then turn around and say that it's not happening. :)

> an appeal had been filed at the WG level. Since WG consensus was stronger than IETF consensus, it is reasonable to assume that the appeal would be escalated to the IESG level if it was not approved at the WG level. So, any way you look at it, there would be delays.
> 3) The new document may not take a year to publish. Since it is a short draft, it could be produced in a few days. Once it is produced, we could immediately initiate a WG last call and an IETF last call immediately after that. So, we might be talking about a six-week delay.
>
> Now, I have a question for you, Lorenzo and Doug. If our goal is to take 6-to-4 off of the Internet, does not disabling it by default solve most of the problem? AFAIKS, very few users would enable it and service providers would not be economically incented to support 6-to-4 relay routers.

Speaking for myself, my goal is not to take STF off the Internet. My 
goal is to do everything we can to get the best possible IPv6 deployed 
in the most places as fast as possible. STF is a hindrance to that goal, 
so I'd like it to go away.

As I've said in the past, I was in the extreme wing of the WG that would 
have preferred to that we came down on the "turn it off, yesterday" 
side. So can I accept "off by default on the client side" as a step in 
the right direction? Sure, why not. But as others have pointed out the 
difference between that and "historic" is that the latter gives vendors 
active DIScouragement to support it at all. IMO that would be better. 
Much better.


Hope I answered your question,

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  Sat Jul  2 21:40:20 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 3EDC811E8091; Sat,  2 Jul 2011 21:40:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.51
X-Spam-Level: 
X-Spam-Status: No, score=-3.51 tagged_above=-999 required=5 tests=[AWL=0.089,  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 R+noIjNvzYLT; Sat,  2 Jul 2011 21:40:19 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id DFECB11E8088; Sat,  2 Jul 2011 21:40:18 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 9227A20878; Sun,  3 Jul 2011 00:40:15 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Sun, 03 Jul 2011 00:40:15 -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=vz86DUjx02iRxD8sOKn1UuvyGJI=; b=ftQIdYjUD8rvHftXBtKR/dsA8ma1xk+hNo7Ph6jbTFe0id2yrotLzMaobru1QcGz41w//NyX40Jd6gyEH9hlG72z4zi/KwaFxLK9J/FRRJkW4Ia0w5/HRU0qbkvpF/ixp40TLUzp/gM3vNPFC3PLvbCYCLJkc7HQCXn6Cpf2VX0=
X-Sasl-enc: SBToi3IeGhuUR6VO2jr2W1YgXvVsgvflkRQF4Urlpkcb 1309668014
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 634BC404F8E; Sun,  3 Jul 2011 00:40:14 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
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: <CAD6AjGTN0bi20TjidwwXeHB=CPyBSZWB4=Lka2YG-5FG4Y1+Pw@mail.gmail.com>
Date: Sun, 3 Jul 2011 00:39:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <CFCBC34F-9D3F-4D52-A2F3-E26E711EDE98@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com> <E817A524-9DB7-4553-A76F-25A9907E7C2D@network-heretics.com> <CAD6AjGTN0bi20TjidwwXeHB=CPyBSZWB4=Lka2YG-5FG4Y1+Pw@mail.gmail.com>
To: Cameron Byrne <cb.list6@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 04:40:20 -0000

On Jul 3, 2011, at 12:02 AM, Cameron Byrne wrote:

> On Sat, Jul 2, 2011 at 8:10 PM, Keith Moore =
<moore@network-heretics.com> wrote:
>> On Jul 2, 2011, at 3:21 PM, Cameron Byrne wrote:
>>=20
>> I saw the same thing. It is a shame that work that directly removes =
barriers
>> to REAL ipv6 deployment gets shouted down by a few people not =
involved in
>> REAL ipv6 deployment
>>=20
>> I find myself wondering what you mean by REAL IPv6.  For me, REAL =
IPv6 is
>> code that uses the IPv6 programming model, 128 bit addresses, =
end-to-end
>> transparency, no NATs.  6to4 certainly qualifies.
>=20
> That's not what it means to me.  REAL IPv6 is a replacement for IPv4
> and can address greater than 100s of billions of endpoint and is
> suitable for very large traffic loads.  As an access network provider,
> i need content on native IPv6.  It does not make sense to anyone in my
> organization or industry to deploy IPv6 unilaterally.  There is no
> benefit in this approach vs just doing NAT444.  If there is IPv6
> content on a meaningful scale ( by the numbers that means for "my
> network": Google, Facebook, Yahoo and their CDNs ...), then i have a
> solid business case for IPv6 access networks. Full Stop.

Chicken-and-egg.  You can't justify widespread deployment of IPv6 until =
there are a lot of content/people/applications using it, and there won't =
be a lot of content/people/applications using it until it's widely =
available.

The whole purpose of mechanisms like 6to4 is to help break that logjam.  =
We need to fix the existing mechanisms, and/or provide better ones, =
rather than killing things that work... even if they only work in corner =
cases.

(Basing the argument entirely on "content", IMO, is misguided, because =
it neglects significant potential drivers of IPv6 adoption, and because =
there's still no incentive to move to v6 as long as the same content is =
available on v4.)

> If the content guys say 6to4 is a pain, and they do, then i need to
> help them find a way to solve that pain. =20

So you want to help the "content" guys at the expense of other =
legitimate uses of 6to4.   Frankly, I don't think that's reasonable.  =
The net doesn't exist just for content delivery.

> In the meantime, i null route the 6to4 anycast address because it
> creates half open state in my CGN.  Been doing that for at least 5
> years.  My next step is filtering AAAA over IPv4 access because 6to4
> client brokeness won't die on its own, that will be rolled out in a
> few months.

So you admit you're sabotaging the network?

Keith


From moore@network-heretics.com  Sat Jul  2 21:41: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 E7A0A21F8432; Sat,  2 Jul 2011 21:41:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.513
X-Spam-Level: 
X-Spam-Status: No, score=-3.513 tagged_above=-999 required=5 tests=[AWL=0.086,  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 zN2b3WqUU8p4; Sat,  2 Jul 2011 21:41: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 35A0721F8587; Sat,  2 Jul 2011 21:41:27 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id D60702016E; Sun,  3 Jul 2011 00:41:26 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Sun, 03 Jul 2011 00:41:26 -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=XPG3l+CzHTFwweWqD8c2d/5SbSw=; b=BdRX6MNzyIhA3QSSIrus1H2hgEsJvOuhjRBy4eETbhhRlOXxahK5OwUVF2VNC8kna+sMvSzogIFv7R6+kt/PUYlKyyMZuMFOknlWDtvCmrJXcPoP2uilwHWJ7/U6bcHZ6CwnMvAa8xWnRiKDFIsCc9V8TQRvjIGcLyQZNMIf9/Q=
X-Sasl-enc: 5IHrhDPiw+LjzichACPBkCH7Uxk4nk5iRz+V4l8DWTvn 1309668086
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 ABEDF4051FC; Sun,  3 Jul 2011 00:41:25 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
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: <4E0FEF7A.4060606@dougbarton.us>
Date: Sun, 3 Jul 2011 00:41:07 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D50C4652-A564-4481-92B3-9C5DD41DBC96@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net>	<CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com>	<m2y60g9xiw.wl%randy@psg.com> <13205C286662DE4387D9AF3AC30EF456D3F3507F14@EMBX01-WF.jnpr.net> <4E0FEF7A.4060606@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
X-Mailer: Apple Mail (2.1084)
Cc: Randy Bush <randy@psg.com>, IPv6 Ops 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: Sun, 03 Jul 2011 04:41:46 -0000

On Jul 3, 2011, at 12:26 AM, Doug Barton wrote:

> Speaking for myself, my goal is not to take STF off the Internet. My =
goal is to do everything we can to get the best possible IPv6 deployed =
in the most places as fast as possible. STF is a hindrance to that goal, =
so I'd like it to go away.

STF is also helping that goal.=20

Keith


From joelja@bogus.com  Sat Jul  2 21:59:43 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 A004D21F8683; Sat,  2 Jul 2011 21:59:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.256
X-Spam-Level: 
X-Spam-Status: No, score=-102.256 tagged_above=-999 required=5 tests=[AWL=-0.257, 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 xDGMJH2TLzqB; Sat,  2 Jul 2011 21:59:43 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id A876321F8688; Sat,  2 Jul 2011 21:59:42 -0700 (PDT)
Received: from [192.168.11.127] (c-76-115-172-69.hsd1.wa.comcast.net [76.115.172.69]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p634xTLY025922 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 3 Jul 2011 04:59:30 GMT (envelope-from joelja@bogus.com)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <20110703141519.1bb90022@opy.nosense.org>
Date: Sat, 2 Jul 2011 21:59:24 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <BEEDDF78-7E0A-4B44-A2F5-49E70BF2D8F2@bogus.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com> <E817A524-9DB7-4553-A76F-25A9907E7C2D@network-heretics.com> <CAD6AjGTN0bi20TjidwwXeHB=CPyBSZWB4=Lka2YG-5FG4Y1+Pw@mail.gmail.com> <20110703141519.1bb90022@opy.nosense.org>
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.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]); Sun, 03 Jul 2011 04:59:30 +0000 (UTC)
Cc: IETF Discussion <ietf@ietf.org>, "v6ops@ietf.org" <v6ops@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: Sun, 03 Jul 2011 04:59:43 -0000

This line of discussion is not productive...=20

Between them the 4 largest north american wireless carriers need ~18 /8s =
to assign public ipv4 addresses to their wireless cpe... they don't have =
that and there's no-where to get it, then there's the rest of the world.
=20
On Jul 2, 2011, at 9:45 PM, Mark Smith wrote:

> On Sat, 2 Jul 2011 21:02:02 -0700
> Cameron Byrne <cb.list6@gmail.com> wrote:
>=20
> <snip>
>> In the meantime, i null route the 6to4 anycast address because it
>> creates half open state in my CGN.  Been doing that for at least 5
>> years.
>=20
>=20
> So, to be clear, you're not making an observation that 6to4 is broken,
> based on measurement or actual use, you're actively breaking it.
>=20
>> My next step is filtering AAAA over IPv4 access because 6to4
>> client brokeness won't die on its own, that will be rolled out in a
>> few months.  Operating a network means making the tweeks that keep =
the
>> wheels rolling, and we don't find many technology purist in my line =
of
>> work.
>>=20
>=20
> I think the root cause of your issues is the deployment of IPv4 CGN in
> the first place before IANA and the RIRs ran out of IPv4 addresses by
> the sounds of it. I think then means that any protocol that your
> customers try to use that would create unwanted state in your IPv4 CGN
> should be, by your definition, declared "historic", not just 6to4. =
When
> a customer signs up to your service, are they informed as to which
> protocols and applications they are allowed to use? My opinion is that
> if there are restrictions on what protocols and applications customers
> can operate then their service is not a real Internet service. The
> majority of, if not all, residential broadband service providers in my
> market hold the same belief - it seems to be the "pure" mobile
> carriers that commonly don't.
>=20
>> Other access providers like 6to4 so much that they want to NAT it.
>> This is the reason why historic is the proper term.
>>=20
>> =
http://tools.ietf.org/html/draft-kuarsingh-v6ops-6to4-provider-managed-tun=
nel-02
>>=20
>> I look forward to that discussion on ietf@
>>=20
>> Cameron
>>=20
>>=20
>>> Keith
>>>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>=20


From moore@network-heretics.com  Sat Jul  2 22:47:35 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 6A41221F86C3; Sat,  2 Jul 2011 22:47:35 -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.218, 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 sZE8NxCOhrMB; Sat,  2 Jul 2011 22:47:34 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id EE01921F86A0; Sat,  2 Jul 2011 22:47:30 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 699FE20615; Sun,  3 Jul 2011 01:47:30 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Sun, 03 Jul 2011 01:47: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=VSASbIj3b0tPYjvAL716FYNlZqo=; b=KKl6RpIKDoqgWWPzIcRaYRoKZ7rg94je0b6iNTWZokZTXdbBGPU5mD5uRbvwj+cWvhh998YYWjujWlRPradCyH2X7dK5KjtyWAx8gZ0JP96YgBbDLDfTu6qXFWkIdwrid0tiI9rPC2rdXX4L4jsKEIs6Gdj8fftMjeRyNBsf42k=
X-Sasl-enc: JQJUsz6WSxtPLJphUBh2B3bFh9/j3Gm9nMf5N6dfKeWL 1309672049
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 2702E40C8F8; Sun,  3 Jul 2011 01:47:29 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-115-652349629
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <CAKD1Yr34UZO7jRAy8hL9uKW2yJ5dDuvOCzrQJ7zn9MmBTovnCg@mail.gmail.com>
Date: Sun, 3 Jul 2011 01:47:11 -0400
Message-Id: <D3733DF4-0313-4651-BDC2-24E4124994EF@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <DE414D2B-82ED-4C32-AFDF-EDAAB6D743B2@network-heretics.com> <CAKD1Yr0=pJwOzRvTNskS7YDBNa7Fc=8srGzH2qJUKwGHdCAELg@mail.gmail.com> <A1DA82E2-B979-4719-9F78-DEB263B256A1@network-heretics.com> <CAKD1Yr34UZO7jRAy8hL9uKW2yJ5dDuvOCzrQJ7zn9MmBTovnCg@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 05:47:35 -0000

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

On Jul 3, 2011, at 1:29 AM, Lorenzo Colitti wrote:

> On Sun, Jul 3, 2011 at 5:11 AM, Keith Moore =
<moore@network-heretics.com> wrote:
>> And who says that "rough consensus of the entire IETF community" is =
that this draft should not be published? Were there public discussions =
to that effect that came to this conclusion?
>=20
> There's clearly a lack of consensus to support it.
>=20
> Nope. The v6ops chairs saw consensus in v6ops to support it. Can you =
point to significant strength of opinion of the wider IETF community, =
but not in v6ops, that has reason to oppose it?

That's not how it works.  You have to get consensus in IETF, not in =
v6ops.  (And it doesn't matter what you think of other people's reasons =
to oppose -historic.)

> If all you can point to is the same people that were opposing it in =
v6ops, then I think they don't count, because the rough consensus in =
v6ops was that the document should be published.

Your logic is flawed.   When you separately sample two dissimilar groups =
it isn't statistically valid to combine the two samples.   The correct =
way to think about it is that the consensus was very rough already in =
v6ops (even the official writeup says so), and it only moved further =
away from rough consensus when the comments from outside of v6ops were =
taken into account.

I agree that the people who objected on v6ops and also objected on the =
ietf list shouldn't be counted twice as opposing the standards action.   =
But when I did the tally, I found only a small amount of overlap between =
people opposing -historic in v6ops, and people opposing it on the ietf =
list.

> So, I ask again: where are the statements made in opposition of this =
proposal made outside of v6ops? Can you point to them?

Some of them were posted to the IETF list.  IESG may have received =
others privately.  That is permitted by our process.

Keith



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

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jul 3, 2011, at 1:29 AM, Lorenzo Colitti wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
class=3D"gmail_quote">On Sun, Jul 3, 2011 at 5:11 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></div><div =
class=3D"h5"><div><blockquote type=3D"cite"><div =
class=3D"gmail_quote"><div>And who says that "rough consensus of the =
entire IETF community"&nbsp;is that this draft should not be published? =
Were there public discussions to that effect that came to this =
conclusion?</div>

</div></blockquote></div></div></div><div>There's clearly a lack of =
consensus to support =
it.</div></div></blockquote><div><br></div><div>Nope. The v6ops chairs =
saw consensus in v6ops to support it. Can you point to significant =
strength of opinion of the wider IETF community, but not in v6ops, that =
has reason to oppose it? </div></div></blockquote><div><br></div>That's =
not how it works. &nbsp;You have to get consensus in IETF, not in v6ops. =
&nbsp;(And it doesn't matter what you think of other people's reasons to =
oppose -historic.)</div><div><br></div><div><blockquote type=3D"cite"><div=
 class=3D"gmail_quote"><div>If all you can point to is the same people =
that were opposing it in v6ops, then I think they don't count, because =
the rough consensus in v6ops was that the document should be =
published.</div></div></blockquote><div><br></div><div>Your logic is =
flawed. &nbsp; When you separately sample two dissimilar groups it isn't =
statistically valid to combine the two samples. &nbsp; The correct way =
to think about it is that the consensus was very rough already in v6ops =
(even the official writeup says so), and it only moved further away from =
rough consensus when the comments from outside of v6ops were taken into =
account.</div><div><br></div><div>I agree that the people who objected =
on v6ops and also objected on the ietf list shouldn't be counted twice =
as opposing the standards action. &nbsp; But when I did the tally, I =
found only a small amount of overlap between people opposing -historic =
in v6ops, and people opposing it on the ietf =
list.</div><div><br></div><blockquote type=3D"cite"><div =
class=3D"gmail_quote">

<div>So, I ask again: where are the statements made in opposition of =
this proposal made outside of v6ops? Can you point to them?</div></div>
</blockquote><br></div><div>Some of them were posted to the IETF list. =
&nbsp;IESG may have received others privately. &nbsp;That is permitted =
by our =
process.</div><div><br></div><div>Keith</div><div><br></div><br></body></h=
tml>=

--Apple-Mail-115-652349629--

From mohta@necom830.hpcl.titech.ac.jp  Sat Jul  2 23:04:56 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 E89C121F86FD for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 23:04:56 -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 SxWJ8qEWxDdM for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 23:04:56 -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 3149621F86A0 for <ietf@ietf.org>; Sat,  2 Jul 2011 23:04:49 -0700 (PDT)
Received: (qmail 18859 invoked from network); 3 Jul 2011 06:17:41 -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; 3 Jul 2011 06:17:41 -0000
Message-ID: <4E10063B.9050206@necom830.hpcl.titech.ac.jp>
Date: Sun, 03 Jul 2011 15:03: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.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net>	<CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com>	<BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com>	<E817A524-9DB7-4553-A76F-25A9907E7C2D@network-heretics.com> <CAD6AjGTN0bi20TjidwwXeHB=CPyBSZWB4=Lka2YG-5FG4Y1+Pw@mail.gmail.com>
In-Reply-To: <CAD6AjGTN0bi20TjidwwXeHB=CPyBSZWB4=Lka2YG-5FG4Y1+Pw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jul 2011 06:04:57 -0000

Cameron Byrne wrote:

> That's not what it means to me.  REAL IPv6 is a replacement for IPv4
> and can address greater than 100s of billions of endpoint and is
> suitable for very large traffic loads.

Then, port restricted IPv4 should be the real IPv6.

Very long address of false IPv6 causes a lot of problems including
performance ones.

						Masataka Ohta

From moore@network-heretics.com  Sat Jul  2 23:15:09 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 CC9A121F8758; Sat,  2 Jul 2011 23:15:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.509
X-Spam-Level: 
X-Spam-Status: No, score=-3.509 tagged_above=-999 required=5 tests=[AWL=0.090,  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 8PuRarBtiXYR; Sat,  2 Jul 2011 23:15:06 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 3B9AA21F8755; Sat,  2 Jul 2011 23:15:06 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id E58122083F; Sun,  3 Jul 2011 02:15:05 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Sun, 03 Jul 2011 02:15: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=KHGkkWETEOdB651nariamhZNqqM=; b=C4lVTdMsStdwLUj0hRLssjBCNdkkyBI4hhYtgPLX//Dut8nwsf1afkmIl9ciT+ConqZ7jqTe2K8LCeg2vFktrI1tfLik0kCb0IovXOAejpbW2wg3f94EdeqbMk5CUBFAtW/vbcZiw0uvH5wGUJm/exq8Rx6KYEfz3dUMKy40yCI=
X-Sasl-enc: Mbwup/AebCXZjtv0raEHZm4omCN7rWm3bLcnBZDVW2jx 1309673705
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 C3EC240BBA9; Sun,  3 Jul 2011 02:15:04 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
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: <CAKD1Yr232NFv=bss_+S-FUGY4m3vghg3bCbeFU0YuT0+uC0j1A@mail.gmail.com>
Date: Sun, 3 Jul 2011 02:14:46 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2A012002-999D-44BD-B243-B0147967F05B@network-heretics.com>
References: <20110703030548.7BF9618C1BA@mercury.lcs.mit.edu> <CAKD1Yr232NFv=bss_+S-FUGY4m3vghg3bCbeFU0YuT0+uC0j1A@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.1084)
Cc: v6ops@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: Sun, 03 Jul 2011 06:15:09 -0000

On Jul 3, 2011, at 1:23 AM, Lorenzo Colitti wrote:

> I think it's clear by now that the vast majority of users don't know =
what IPv6 is, and that they do not ask for it.

No, but they do want their applications to work well.  That's constantly =
getting more difficult in IPv4.   The workarounds for NATs and other =
forms of brain damage in the network keep changing, and each application =
requires not only its own code but also its own infrastructure to deal =
with that brain damage.     So a solution that allows applications to =
use IPv6 whether or not all of the networks between the peers support =
native v6, is very badly needed.  We can't wait for ISPs to give =
everybody IPv6 before applications start using it.

And I agree that most users don't know what IPv6 is, at the moment.  But =
if they learn that it will help their apps work better, they'll want it.=20=


(I also remember when most people didn't know what the Internet was.  =
And then, almost in an instant, everybody knew, and a cartoon in the New =
Yorker magazine about the internet and a dog was something everybody =
could understand.  Users will understand IPv6 also, soon enough.)

Keith

p.s. I often wear a t-shirt that says "there's no place like ::1".  =
Non-computer people ask me what it means, and in response, I tell them =
it's the address of their own machine in IPv6.   So far, nobody has =
asked me what IPv6 means.   Everyone who has asked me about the shirt =
has heard of IPv6 and understood at some level that it's the next =
version of the Internet.  If anything, there seems to be a disconnect =
between what "ordinary users" know about IPv6 and what their ISPs are =
telling them - because for the most part, the ISPs seem to keep publicly =
pretending that it doesn't exist.


From moore@network-heretics.com  Sat Jul  2 23:27:33 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 BB93221F8772; Sat,  2 Jul 2011 23:27:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.511
X-Spam-Level: 
X-Spam-Status: No, score=-3.511 tagged_above=-999 required=5 tests=[AWL=0.087,  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 LPTgvmIOBRPo; Sat,  2 Jul 2011 23:27:33 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 001F121F8767; Sat,  2 Jul 2011 23:27:32 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id AC50F2078B; Sun,  3 Jul 2011 02:27:32 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute5.internal (MEProxy); Sun, 03 Jul 2011 02:27:32 -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=OXMxgsQYEAvYkdTR95gUJc/WtHY=; b=La2i/3b8c0gLKlqw2mTYB/mGkRH+ky9mdp7eVgHcpUP5QzSF43KCOY76+ZZd/NWAZvtgTxTuUOhnkUOTrnU4vzS0fbzlmedbXRH5sG4s3jgME3LHFfapBTsW4V3ym4cEct0MWFtEJxbcmmRQU+Ym71mHuYfvyefoeY4La/fLrzQ=
X-Sasl-enc: 7E6o3u2lgB4H4DTp4uFYmBMmFYbDNC2jkL5A1qaKq0ad 1309674451
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 30D1440BAF2; Sun,  3 Jul 2011 02:27:31 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-116-654751406
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <CAKD1Yr0dU8xGPc5tY8qK7w7Vc57zzj2BBipCb3b3VsXLov-JUw@mail.gmail.com>
Date: Sun, 3 Jul 2011 02:27:13 -0400
Message-Id: <9BDD213D-A4A4-4999-B64C-E66AFB7254B6@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com> <20110703112048.4a3c7111@opy.nosense.org> <4E0FD788.3000305@dougbarton.us> <20110703131913.28142ec0@opy.nosense.org> <CAKD1Yr0dU8xGPc5tY8qK7w7Vc57zzj2BBipCb3b3VsXLov-JUw@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.1084)
Cc: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>, "v6ops@ietf.org" <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: Sun, 03 Jul 2011 06:27:33 -0000

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


On Jul 3, 2011, at 1:53 AM, Lorenzo Colitti wrote:

> On Sun, Jul 3, 2011 at 5:49 AM, Mark Smith =
<ipng@69706e6720323030352d30312d31340a.nosense.org> wrote:
> Declaring 6to4 to be historic might encourage native IPv6 deployment,
> but I think it will also make trialing IPv6 much harder.
>=20
> We don't need to trial the IPv6 protocol. There are hundreds of =
thousands of native users accessing production-grade IPv6 services, like =
Google's, every day. We know the IPv6 protocol works. ISPs do need to =
trial IPv6 deployment. But 6to4 does not help there, because 6to4 is not =
deployed by ISPs.

6to4 allows applications to use IPv6 even when ISPs don't support it.   =
The idea is to allow application deployment, and use of IPv6, to develop =
independently of ISP deployment of native IPv6.

> They will need to trial native deployments, or 6rd. If *users* want to =
trial IPv6 until native IPv6 is available, then they can use configured =
tunnels.

Uh, no.  If you're an application developer, shipping code that requires =
every single user to set up a tunnel is a nonstarter.  And as well all =
know, configured tunnels often route very suboptimally.   In many cases =
6to4 works better.

It's not as if the only applications that matter are those that are =
layered over HTTP.

> The involvement in World IPv6 day by large content providers and the
> apparent lack of significant problems would be suggest the opposite is
> now the case. Google continuing to provide youtube video content to =
6to4
> tunnel users (such as myself), nearly a month later, suggests that any
> problems with it are tractable.
>=20
> I would assert that the problems with 6to4 are not tractable without =
disabling 6to4. Our IPv6 brokenness statistics for before and after =
World IPv6 Day are very similar.

The only unfixable problem that 6to4 has is its inability to work with =
NATs, including LSN.     Some of those fixes would require code updates =
to host implementations, but disabling 6to4 would also require code =
updates.

> 6to4 users are easy to spot by the 2002::/16 prefix, so if Google =
needed to they could probably quite easily limit their IPv6 content =
delivery to native only IPv6 users.
>=20
> No, that's not how it works. There is no problem with 6to4 when it =
works as well as IPv4. The problem is that 6to4 only works *at all* =
(never mind works "as well as IPv4") 80% of the time.

That figure is not based on a representative sample of all 6to4 use, so =
it's hard to know how much confidence to have in it.

Keith


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

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jul 3, 2011, at 1:53 AM, Lorenzo Colitti =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div class=3D"gmail_quote">On Sun, Jul 3, 2011 at 5:49 AM, =
Mark Smith <span dir=3D"ltr">&lt;<a =
href=3D"mailto:ipng@69706e6720323030352d30312d31340a.nosense.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:1px #ccc solid;padding-left:1ex"><div>Declaring 6to4 to =
be historic might encourage native IPv6 deployment,</div>
but I think it will also make trialing IPv6 much =
harder.<br></blockquote><div><br></div><div>We don't need to trial the =
IPv6 protocol. There are hundreds of thousands of native users accessing =
production-grade IPv6 services, like Google's, every day. We know the =
IPv6 protocol works.&nbsp;ISPs do need to trial IPv6 deployment. But =
6to4 does not help there, because 6to4 is not deployed by ISPs. =
</div></div></blockquote><div><br></div><div>6to4 allows applications to =
use IPv6 even when ISPs don't support it. &nbsp; The idea is to allow =
application deployment, and use of IPv6, to develop independently of ISP =
deployment of native IPv6.</div><br><blockquote type=3D"cite"><div =
class=3D"gmail_quote"><div>They will need to trial native deployments, =
or 6rd.&nbsp;If *users* want to trial IPv6 until native IPv6 is =
available, then they can use configured =
tunnels.</div></div></blockquote><div><br></div>Uh, no. &nbsp;If you're =
an application developer, shipping code that requires every single user =
to set up a tunnel is a nonstarter. &nbsp;And as well all know, =
configured tunnels often route very suboptimally. &nbsp; In many cases =
6to4 works better.</div><div><br></div><div>It's not as if the only =
applications that matter are those that are layered over =
HTTP.</div><div><br><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>The involvement in World IPv6 day by large content providers and =
the</div>
apparent lack of significant problems would be suggest the opposite =
is<br>
now the case. Google continuing to provide youtube video content to =
6to4<br>
tunnel users (such as myself), nearly a month later, suggests that =
any<br>
problems with it are tractable.</blockquote><div><br></div><div>I would =
assert that the problems with 6to4 are not tractable without disabling =
6to4. Our IPv6 brokenness statistics for before and after World IPv6 Day =
are very similar.</div></div></blockquote><div><br></div>The only =
unfixable problem that 6to4 has is its inability to work with NATs, =
including LSN. &nbsp; &nbsp;&nbsp;Some of those fixes would require code =
updates to host implementations, but disabling 6to4 would also require =
code updates.</div><div><br><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">6to4 users are easy to =
spot by the&nbsp;2002::/16 prefix, so if Google needed to they could =
probably quite&nbsp;easily limit their IPv6 content delivery to native =
only IPv6 users.</blockquote>


<div><br></div><div>No, that's not how it works. There is no problem =
with 6to4 when it works as well as IPv4. The problem is that 6to4 only =
works *at all* (never mind works "as well as IPv4") 80% of the =
time.</div></div></blockquote><div><br></div><div>That figure is not =
based on a representative sample of all 6to4 use, so it's hard to know =
how much confidence to have in =
it.</div><div><br></div></div>Keith<div><br></div></body></html>=

--Apple-Mail-116-654751406--

From moore@network-heretics.com  Sat Jul  2 23:30:33 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 3B88F21F8796; Sat,  2 Jul 2011 23:30:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.514
X-Spam-Level: 
X-Spam-Status: No, score=-3.514 tagged_above=-999 required=5 tests=[AWL=0.084,  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 E9dfpI9RUvzZ; Sat,  2 Jul 2011 23:30:32 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 566F821F8795; Sat,  2 Jul 2011 23:30:32 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 0CDF220870; Sun,  3 Jul 2011 02:30:32 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Sun, 03 Jul 2011 02:30:32 -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=BgkXrRNxO3W+H7KUp49KgYW7rIQ=; b=T3lgvTcf2++FoqQRVtHabd85ssHz8nEcWs8tmKW+rZYeALBON9gNOmxIksHBRzZtHQrT09F9FPBxXlTTcuis3GnI1Qrq/DUv74Sg4fqGXptjD12d2NP9ZUzBS+xbLpn4ZpA4j6XRz6oy7/8TAobWBfN0uAL5ByVUMyyG2p2Aaq8=
X-Sasl-enc: 9kkdES1T+bMCcXd0izcd+gXGkTWQQ0k/gJX9f4ddhSe1 1309674631
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 E007A4002AB; Sun,  3 Jul 2011 02:30:30 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-117-654931490
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <CAKD1Yr1qN6qjEMNq7GDNoX8UifDpxHBcMLYUVwmCWQG=JFyVvQ@mail.gmail.com>
Date: Sun, 3 Jul 2011 02:30:13 -0400
Message-Id: <F1F0D7CF-FBB7-45A5-8F0C-D556E2C50D63@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <20110703100844.68eb8b7d@opy.nosense.org> <CAKD1Yr1qN6qjEMNq7GDNoX8UifDpxHBcMLYUVwmCWQG=JFyVvQ@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.1084)
Cc: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>, "v6ops@ietf.org" <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: Sun, 03 Jul 2011 06:30:33 -0000

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

On Jul 3, 2011, at 1:58 AM, Lorenzo Colitti wrote:

> On Sun, Jul 3, 2011 at 2:38 AM, Mark Smith =
<ipng@69706e6720323030352d30312d31340a.nosense.org> wrote:
> I don't object to what has been proposed, yet I object to
> "6to4-historic" because I'm an extremely happy anycast 6to4 user
>=20
> "It works for me, so there's obviously no problem". When you think of =
6to4-historic, please think of the 20% of anycast 6to4 users that are =
broken.


6to4 used to be far less reliable than that, but has improved as =
additional relays were deployed.   It's reasonable to expect that the =
publication of -advisory will improve the situation further.

Keith


--Apple-Mail-117-654931490
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 Jul 3, 2011, at 1:58 AM, Lorenzo Colitti wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Sun, Jul 3, 2011 at 2:38 AM, Mark Smith <span dir="ltr">&lt;<a href="mailto:ipng@69706e6720323030352d30312d31340a.nosense.org">ipng@69706e6720323030352d30312d31340a.nosense.org</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I don't object to what has been proposed, yet I object to<br>
"6to4-historic" because I'm an extremely happy anycast 6to4 user</blockquote><div><br></div><div>"It works for me, so there's obviously no problem". When you think of 6to4-historic, please think of the 20% of anycast 6to4 users that are broken.</div></div></blockquote></div><div><br></div><div>6to4 used to be far less reliable than that, but has improved as additional relays were deployed. &nbsp; It's reasonable to expect that the publication of -advisory will improve the situation further.</div><div><br></div><div>Keith</div><div><br></div></body></html>
--Apple-Mail-117-654931490--

From moore@network-heretics.com  Sat Jul  2 23:36: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 BD60C21F86DA; Sat,  2 Jul 2011 23:36:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.517
X-Spam-Level: 
X-Spam-Status: No, score=-3.517 tagged_above=-999 required=5 tests=[AWL=0.082,  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 X+53AYMgxYDj; Sat,  2 Jul 2011 23:36: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 36C5721F8679; Sat,  2 Jul 2011 23:36:44 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id DE86B20725; Sun,  3 Jul 2011 02:36:43 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Sun, 03 Jul 2011 02:36: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=MVPV9YsY3THaeLYd8FuQGAiAL+A=; b=DFfT3t0DBGwllUpKW8/AQ8iL1hxCy/jWr7LyFHbvMxuiesbxFxHb+Z8XwahCBkagkQOIRk42YTUFFsS2dAtG1d0YWZbpMe6dOn3kZeOtZwdX7diaP2A22kgwVQiQPv15izmc9BCxFn/wwVIT3tQST4rUeKOVDdv7R+9jnCYUhmQ=
X-Sasl-enc: neAXyusjyDZ8YY42WS3LePGDZ5khSmY3RjUIZ+1FoX9u 1309675003
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 E87B940BF83; Sun,  3 Jul 2011 02:36:42 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
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: <4E100ACB.70907@globis.net>
Date: Sun, 3 Jul 2011 02:36:25 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <806331F9-2A3D-459C-8774-BED1346C475F@network-heretics.com>
References: <4E100ACB.70907@globis.net>
To: Ray Hunter <v6ops@globis.net>
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: Sun, 03 Jul 2011 06:36:44 -0000

On Jul 3, 2011, at 2:23 AM, Ray Hunter wrote:

> IMHO Right now, we need services with native IPv6 based interfaces, =
with equivalent performance and equivalent features and equivalent price =
that we have today with IPv4. Anything that detracts from the roll out =
of native IPv6 based service interfaces at this time is a bad move IMVHO =
and hastens the day that the Internet fragments into a bunch of CGN =
zones, that is dominated by businesses that can afford to buy public =
IPv4 addresses for their servers or services, or whose business model =
relies on NAT traversal being difficult. I personally don't want that =
sort of Internet.

Right now, applications developers need to be able to write and ship =
code that uses IPv6 and can talk to other application instances using =
IPv6.   Anything that detracts from the ability of applications to use =
IPv6 at this time is a bad move IMHO and decreases the chance that there =
will ever be sufficient use of IPv6 (of any kind) to justify widespread =
deployment of native IPv6.

> Given that development and engineering support time is finite, I'd =
much rather that 6to4 was declared historic so that developers and =
engineers could spend more time on deployment of native IPv6 service =
interfaces.

I have a better suggestion: let's declare NAT historic.  That would free =
up lots of developers and engineers to spend time on both native v6 and =
better v6 transition mechanisms.  Not only would they not need to =
engineer new NATs, applications developers wouldn't need to engineer new =
workarounds for new NATs.  Everybody would win.

Keith


From moore@network-heretics.com  Sat Jul  2 23:56: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 EF0B621F8728; Sat,  2 Jul 2011 23:56:02 -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.221, 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 GafZlTtI90ko; Sat,  2 Jul 2011 23:56: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 2FE8921F8727; Sat,  2 Jul 2011 23:56:02 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id C5399206CF; Sun,  3 Jul 2011 02:56:01 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Sun, 03 Jul 2011 02:56: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:message-id:references:to; s=smtpout; bh=BC8rc0+wani4ljDmz/LKziHJX7w=; b=heBa7CcWlj4BMWLI57u7zeHO2FL7JHm78VlP11UUTEVmeIrp0jgSh1jq8NHKNu7hb4qIZ3RSEIo7ug5dS4R0ZbB4T8LtBhow/MnDudXH2trRP1Klz8gvPuqL7YNc4pbV+Rz96Ufl9QuCgplr7oBB8Fov1/jHNzNlB8a6DJyIAkM=
X-Sasl-enc: b/bBEFvt1+LFQXaApuoA5jgCaC6K5PBoTFA+YWlhL/Na 1309676160
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 5CD384009CD; Sun,  3 Jul 2011 02:56:00 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-118-656460945
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <AEFA1403-74C5-4982-A056-4AF7E5734BEA@nominum.com>
Date: Sun, 3 Jul 2011 02:55:42 -0400
Message-Id: <703700EE-07B8-473A-ACFC-E712F44481A0@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <DE414D2B-82ED-4C32-AFDF-EDAAB6D743B2@network-heretics.com> <CAKD1Yr0=pJwOzRvTNskS7YDBNa7Fc=8srGzH2qJUKwGHdCAELg@mail.gmail.com> <A1DA82E2-B979-4719-9F78-DEB263B256A1@network-heretics.com> <CAKD1Yr34UZO7jRAy8hL9uKW2yJ5dDuvOCzrQJ7zn9MmBTovnCg@mail.gmail.com> <D3733DF4-0313-4651-BDC2-24E4124994EF@network-heretics.com> <AEFA1403-74C5-4982-A056-4AF7E5734BEA@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org Operations" <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: Sun, 03 Jul 2011 06:56:03 -0000

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


On Jul 3, 2011, at 2:37 AM, Ted Lemon wrote:

> On Jul 3, 2011, at 1:47 AM, Keith Moore wrote:
>> Some of them were posted to the IETF list.  IESG may have received =
others privately.  That is permitted by our process.
>=20
> This is a frustrating conversation.   Everybody who supported the =
consensus in v6ops is an IETF participant, and their wishes count toward =
the IETF consensus. =20

Yes their wishes do count.   But the consensus was marginal even in =
v6ops, and v6ops isn't representative of the breadth of interests in the =
entire IETF.   It should hardly be surprising that a very rough =
consensus within a working group doesn't translate to a rough consensus =
within IETF as a whole.

v6ops isn't special in this regard.  The same is true for any other =
working group.  Unfortunately, it's really easy for a working group that =
is focused on a particular set of concerns, to neglect concerns from the =
wider community.

> The draft is good.   It encourages people to do the right things: keep =
6to4 relays active, but not ship products with 6to4 enabled by default.  =
This works for everyone=97for people like me who are using 6to4 for our =
IPv6 connectivity, it works because the relays stay up.   For people who =
do not have global IPv4 addresses, they do not wind up with IPv6 routes =
that go nowhere.   It certainly serves Keith Moore's needs, no matter =
how vehemently, nor how often, he may insist that it does not.

You are not in a good position to evaluate what I need.

> So this really does look like another IETF night of long knives, where =
a good draft gets scuttled in secret because a few very loud people =
manage to create enough of a fuss to make the person or persons calling =
the consensus feel like they're going to get fricasseed if they call the =
consensus in favor of the draft.

No, it's not a good draft.  It's misleading in many places.  And the =
label of Historic is simply inappropriate for something that is still =
quite useful for many people and for which no good replacement yet =
exists. =20

The "right things" that you refer to get obscured by the overall message =
of the Historic label.  And the -advisory draft says the "right things" =
much better.

> Have we actually had a formal consensus call for the IETF?   Who =
called the consensus?   Can we have a summary?   I haven't seen one.

That's what the IETF Last Call was.   IESG is supposed to evaluate =
consensus as well as technical merit in its balloting.

Keith


--Apple-Mail-118-656460945
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 Jul 3, 2011, at 2:37 AM, Ted Lemon 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 Jul 3, 2011, at =
1:47 AM, Keith Moore wrote:</div><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Optima; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div>Some of =
them were posted to the IETF list. &nbsp;IESG may have received others =
privately. &nbsp;That is permitted by our =
process.</div></span></blockquote><br></div><div>This is a frustrating =
conversation. &nbsp; Everybody who supported the consensus in v6ops is =
an IETF participant, and their wishes count toward the IETF consensus. =
&nbsp; </div></div></blockquote><div><br></div>Yes their wishes do =
count. &nbsp; But the consensus was marginal even in v6ops, and v6ops =
isn't representative of the breadth of interests in the entire IETF. =
&nbsp; It should hardly be surprising that a very rough consensus within =
a working group doesn't translate to a rough consensus within IETF as a =
whole.</div><div><br></div><div>v6ops isn't special in this regard. =
&nbsp;The same is true for any other working group. &nbsp;Unfortunately, =
it's really easy for a working group that is focused on a particular set =
of concerns, to neglect concerns from the wider =
community.</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>The draft is good. &nbsp; =
It encourages people to do the right things: keep 6to4 relays active, =
but not ship products with 6to4 enabled by default. &nbsp;This works for =
everyone=97for people like me who are using 6to4 for our IPv6 =
connectivity, it works because the relays stay up. &nbsp; For people who =
do not have global IPv4 addresses, they do not wind up with IPv6 routes =
that go nowhere. &nbsp; It certainly serves Keith Moore's needs, no =
matter how vehemently, nor how often, he may insist that it does =
not.</div></div></blockquote><div><br></div>You are not in a good =
position to evaluate what I need.</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>So this really does =
look like another IETF night of long knives, where a good draft gets =
scuttled in secret because a few very loud people manage to create =
enough of a fuss to make the person or persons calling the consensus =
feel like they're going to get fricasseed if they call the consensus in =
favor of the draft.</div></div></blockquote><div><br></div>No, it's not =
a good draft. &nbsp;It's misleading in many places. &nbsp;And the label =
of Historic is simply inappropriate for something that is still quite =
useful for many people and for which no good replacement yet exists. =
&nbsp;</div><div><br></div><div>The "right things" that you refer to get =
obscured by the overall message of the Historic label. &nbsp;And the =
-advisory draft says the "right things" much =
better.</div><div><br></div><div><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div>Have we actually had a =
formal consensus call for the IETF? &nbsp; Who called the consensus? =
&nbsp; Can we have a summary? &nbsp; I haven't seen =
one.</div></div></blockquote><br></div><div>That's what the IETF Last =
Call was. &nbsp; IESG is supposed to evaluate consensus as well as =
technical merit in its =
balloting.</div><div><br></div><div>Keith</div><div><br></div></body></htm=
l>=

--Apple-Mail-118-656460945--

From dougb@dougbarton.us  Sat Jul  2 23:58:58 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 5170721F8793 for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 23:58:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.553
X-Spam-Level: 
X-Spam-Status: No, score=-3.553 tagged_above=-999 required=5 tests=[AWL=0.046,  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 XBY0qJvbVwkQ for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 23:58:57 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 6D9D821F874F for <ietf@ietf.org>; Sat,  2 Jul 2011 23:58:57 -0700 (PDT)
Received: (qmail 9437 invoked by uid 399); 3 Jul 2011 06:58:56 -0000
Received: from unknown (HELO 65-241-43-4.globalsuite.net) (dougb@dougbarton.us@65.241.43.4) by mail2.fluidhosting.com with ESMTPAM; 3 Jul 2011 06:58:56 -0000
X-Originating-IP: 65.241.43.4
X-Sender: dougb@dougbarton.us
Message-ID: <4E10132E.3050902@dougbarton.us>
Date: Sat, 02 Jul 2011 23:58:54 -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.18) Gecko/20110624 Thunderbird/3.1.11
MIME-Version: 1.0
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net>	<CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com>	<BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com>	<20110703112048.4a3c7111@opy.nosense.org>	<4E0FD788.3000305@dougbarton.us> <20110703131913.28142ec0@opy.nosense.org>
In-Reply-To: <20110703131913.28142ec0@opy.nosense.org>
X-Enigmail-Version: 1.1.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 06:58:58 -0000

On 07/02/2011 20:49, Mark Smith wrote:
> On Sat, 02 Jul 2011 19:44:24 -0700
> Doug Barton<dougb@dougbarton.us>  wrote:
>
>> On 07/02/2011 18:50, Mark Smith wrote:
>>> Where is the evidence that 6to4 is holding back native IPv6
>>> deployment?
>>
>> It's been discussed ad nauseum in numerous fora.
>
> Discussion isn't evidence, as people usually don't post any data to
> support their assertions.

And yet, they did.

This whole thing is getting silly, and I'm tired of repeating myself. I 
think Lorenzo did a great job of explaining some more of the downsides 
of 6to4 and I don't have anything useful to add beyond what I've already 
said.


-- 

	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 sm@resistor.net  Sun Jul  3 00:14:46 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 30BC821F87A2; Sun,  3 Jul 2011 00:14: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 ghetzTGn2u+S; Sun,  3 Jul 2011 00:14:40 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D6E521F879E; Sun,  3 Jul 2011 00:14:40 -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 p637ESau001018;  Sun, 3 Jul 2011 00:14:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1309677274; bh=DFT9PczvGme1UWrWTchcNy++eVwCzNWDybcxaAxFSEk=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=zks8WDCWQxSlln/c/t50FcI1b2rH1iLLEphh1q/9c3ObGD2Fr7sPhlqHNSnxecW/Q HnqxsX9V0fxxj24Drl/mTQrGFU+LsZ+g6uPJxoCUBntHFVzlHYkydUXDvaTUZj0bVr ehIWGxf5MXgYXmU0Bw6QxwjpjirfGeOfZeOgsrxA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1309677274; bh=DFT9PczvGme1UWrWTchcNy++eVwCzNWDybcxaAxFSEk=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=TMuBtt0W3rsXvJXE/N5h3ZDA8vr3MwgjfWmOqXZ8gUt1tBU4oSkmljZnHz0WNPx0Z zT2IhfiIETu9kqkHdELAPJb17e6WR2EH5qBOLxNegp2sz71Oemb8iDYUeRqh6HcBz1 pEKYaB6TanKiPJ3X8ZMPIP/fjHe2T0A7dmwfzWks=
Message-Id: <6.2.5.6.2.20110702232627.0350a6d8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 02 Jul 2011 23:29:58 -0700
To: IETF Discussion <ietf@ietf.org>
From: SM <sm@resistor.net>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
In-Reply-To: <BEEDDF78-7E0A-4B44-A2F5-49E70BF2D8F2@bogus.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com> <E817A524-9DB7-4553-A76F-25A9907E7C2D@network-heretics.com> <CAD6AjGTN0bi20TjidwwXeHB=CPyBSZWB4=Lka2YG-5FG4Y1+Pw@mail.gmail.com> <20110703141519.1bb90022@opy.nosense.org> <BEEDDF78-7E0A-4B44-A2F5-49E70BF2D8F2@bogus.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: 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: Sun, 03 Jul 2011 07:14:46 -0000

At 21:59 02-07-2011, Joel Jaeggli wrote:
>Between them the 4 largest north american wireless carriers need ~18 
>/8s to assign public ipv4 addresses to their wireless cpe... they 
>don't have that and there's no-where to get it, then there's the 
>rest of the world.

http://aboba.drizzlehosting.com/IAB/arin.txt

Regards,
-sm 


From moore@network-heretics.com  Sun Jul  3 00:17: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 F35C611E8081; Sun,  3 Jul 2011 00:17:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.513
X-Spam-Level: 
X-Spam-Status: No, score=-3.513 tagged_above=-999 required=5 tests=[AWL=0.086,  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 vZXvqSFk2T7S; Sun,  3 Jul 2011 00:17: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 D7ECA21F87CF; Sun,  3 Jul 2011 00:17:19 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id 5FF462061D; Sun,  3 Jul 2011 03:17:19 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute5.internal (MEProxy); Sun, 03 Jul 2011 03:17: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=82yFeWwDQRzelBxU7NTqfDtI2cw=; b=eiYvY2hpHNLkOLc1rQnJNw+ksIc3GsuT0spIJ1XXaE1Z0Pi9QVDwSiJWpVnxPX3eKB8smI9pPlDMlB2JZ+7wqjTiBgd6XFMISE2UFpukwfAoL/QbNEbzHV7IjEmA5FvoJNCtu02lxtxpFM3PZExrFTA6+yEFFSq/uGyrslZtqys=
X-Sasl-enc: z2yE0UA4tI14u6CzbJx0fO/Z6Mw7m87BffOZe8DRyaoD 1309677438
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 3DBEE40CC1C; Sun,  3 Jul 2011 03:17:18 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
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: <4E10132E.3050902@dougbarton.us>
Date: Sun, 3 Jul 2011 03:17:00 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <240CA88D-961E-4ECC-A2AA-A7829B409B75@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net>	<CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com>	<BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com>	<20110703112048.4a3c7111@opy.nosense.org>	<4E0FD788.3000305@dougbarton.us> <20110703131913.28142ec0@opy.nosense.org> <4E10132E.3050902@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
X-Mailer: Apple Mail (2.1084)
Cc: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>, "v6ops@ietf.org" <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: Sun, 03 Jul 2011 07:17:21 -0000

On Jul 3, 2011, at 2:58 AM, Doug Barton wrote:

> On 07/02/2011 20:49, Mark Smith wrote:
>> On Sat, 02 Jul 2011 19:44:24 -0700
>> Doug Barton<dougb@dougbarton.us>  wrote:
>>=20
>>> On 07/02/2011 18:50, Mark Smith wrote:
>>>> Where is the evidence that 6to4 is holding back native IPv6
>>>> deployment?
>>>=20
>>> It's been discussed ad nauseum in numerous fora.
>>=20
>> Discussion isn't evidence, as people usually don't post any data to
>> support their assertions.
>=20
> And yet, they did.

I think it's been adequately supported that the interaction of 6to4 with =
(a) misconfigured relay routers and/or (b) protocol 41 filters, hinders =
one kind of native v6 deployment - i.e. providing the same content via =
both v4 and v6, where the client's host prefers v6 (including 6to4) =
destinations over v4 destinations.  There's clearly a disincentive to a =
content provider to advertise v6 addresses for its domains, if use of =
those v6 addresses will result in significantly slower or less reliable =
access for any significant set of users.   That much should be obvious.

However,  that's not the only kind of IPv6 deployment that matters.

Meanwhile misconfigured relay routers can be fixed, or their =
advertisements filtered; and hosts can and should be updated to prefer =
IPv4 destinations over 6to4 destinations.  6to4, even when enabled, =
should be a "last resort". =20

All of these fixes should be implemented.  But that last fix alone =
should address (no pun intended) the v4/v6 content providers' concerns =
while still preserving use of 6to4 for cases where IPv6 is really =
needed.  And that last fix can be deployed much more quickly than the =
"nuclear option" of trying to get 6to4 support removed from products.

Keith


From moore@network-heretics.com  Sun Jul  3 00:29: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 9C7E121F87E4; Sun,  3 Jul 2011 00:29:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.366
X-Spam-Level: 
X-Spam-Status: No, score=-2.366 tagged_above=-999 required=5 tests=[AWL=-1.067, BAYES_00=-2.599, MANGLED_WANT=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 OrzHAkPsscqg; Sun,  3 Jul 2011 00:29: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 C215D21F87E3; Sun,  3 Jul 2011 00:29:40 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 61D5620A21; Sun,  3 Jul 2011 03:29:40 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Sun, 03 Jul 2011 03:29: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=6O3TkT4AUABAeZqpfCRBdWmOEvo=; b=LNN33/7jJGk7XoWO1Ym3JqpyUn2ig4ShFnLy8Zx2Sa8dB35v9tnVgMkMocBMa/pvHrv8K5z4KzZ3EhOzkEo+ZLvv1Yf+CtoIg5fRwfVPfJoUbfqrDD3UVJ4V3WUJVzcfp8Rpch1FR9J4wyntgvy4Spm3JnhSAqbjiVgbVlGxBws=
X-Sasl-enc: XuZq3qwW8Gt/W1NiS3CwtfjGwsO6ogGCxImbvbk5UJ7u 1309678179
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 58CD440348E; Sun,  3 Jul 2011 03:29:39 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
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: <4E10172F.3070105@globis.net>
Date: Sun, 3 Jul 2011 03:29:21 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9601ECDE-CFBF-498A-B12D-86A1D1EE4EAC@network-heretics.com>
References: <4E100ACB.70907@globis.net> <806331F9-2A3D-459C-8774-BED1346C475F@network-heretics.com> <4E10172F.3070105@globis.net>
To: Ray Hunter <v6ops@globis.net>
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: Sun, 03 Jul 2011 07:29:41 -0000

On Jul 3, 2011, at 3:15 AM, Ray Hunter wrote:

> Keith Moore wrote:
>>=20
>> On Jul 3, 2011, at 2:23 AM, Ray Hunter wrote:
>>=20
>>  =20
>>> IMHO Right now, we need services with native IPv6 based interfaces, =
with equivalent performance and equivalent features and equivalent price =
that we have today with IPv4. Anything that detracts from the roll out =
of native IPv6 based service interfaces at this time is a bad move IMVHO =
and hastens the day that the Internet fragments into a bunch of CGN =
zones, that is dominated by businesses that can afford to buy public =
IPv4 addresses for their servers or services, or whose business model =
relies on NAT traversal being difficult. I personally don't want that =
sort of Internet.
>>>    =20
>>=20
>> Right now, applications developers need to be able to write and ship =
code that uses IPv6 and can talk to other application instances using =
IPv6.   Anything that detracts from the ability of applications to use =
IPv6 at this time is a bad move IMHO and decreases the chance that there =
will ever be sufficient use of IPv6 (of any kind) to justify widespread =
deployment of native IPv6.
>>=20
>>  =20
>>> Given that development and engineering support time is finite, I'd =
much rather that 6to4 was declared historic so that developers and =
engineers could spend more time on deployment of native IPv6 service =
interfaces.
>>>    =20
>>=20
>> I have a better suggestion: let's declare NAT historic.  That would =
free up lots of developers and engineers to spend time on both native v6 =
and better v6 transition mechanisms.  Not only would they not need to =
engineer new NATs, applications developers wouldn't need to engineer new =
workarounds for new NATs.  Everybody would win.
>>=20
>> Keith
>>=20
>>  =20
> I'm presuming your second comment was facetious.

Mostly.   Though I do think that declaring NAT historic is absolutely as =
valid as declaring 6to4 historic.    Both 6to4 and NAT are things that =
are useful in some cases and cause harm in others.  Except that 6to4 =
doesn't actually cause harm except in conjunction with other dubious =
practices (bogus anycast route advertisements, protocol 41 filtering, =
use public IPv4 addresses behind LSN) which are outside of 6to4's scope, =
whereas NAT inherently causes harm.

But it wan't a serious suggestion, just an analogy.

> I'm also presuming from your first comment that you will thus oppose =
the proposal to turn off 6to4 by default.
>=20
> Am I correct?

I've already said on several occasions that I agree that 6to4 should be =
off by default.   It's mostly the Historic label that I have the problem =
with.   (I have other objections to the document also, but those are =
just places where I think the wording is misleading.  The label is the =
big thing.)

Keith


From hannes.tschofenig@gmx.net  Sun Jul  3 00:36:33 2011
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F3DB21F875F for <ietf@ietfa.amsl.com>; Sun,  3 Jul 2011 00:36: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 Yo+8ozNhwPPW for <ietf@ietfa.amsl.com>; Sun,  3 Jul 2011 00:36:33 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 9D45021F874C for <ietf@ietf.org>; Sun,  3 Jul 2011 00:36:32 -0700 (PDT)
Received: (qmail invoked by alias); 03 Jul 2011 07:36:31 -0000
Received: from letku101.adsl.netsonic.fi (EHLO [10.0.0.8]) [194.29.195.101] by mail.gmx.net (mp064) with SMTP; 03 Jul 2011 09:36:31 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX196sNo5Kjd62FrqGAYICYSCjMXDTEsvZCO0beqTGC bCS7K+OD5CF/Bz
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: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <11CBFBA2-434B-43FC-90C4-DADBACB49226@mnot.net>
Date: Sun, 3 Jul 2011 10:36:29 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <623429C9-70E2-4442-8ECF-AB827FD95251@gmx.net>
References: <11CBFBA2-434B-43FC-90C4-DADBACB49226@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
X-Mailer: Apple Mail (2.1084)
X-Y-GMX-Trusted: 0
Cc: "ietf@ietf.org IETF" <ietf@ietf.org>, Eran Hammer-Lahav <eran@hueniverse.com>, oauth WG <oauth@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jul 2011 07:36:33 -0000

I also never really understood why XRD was re-used.=20

Btw, XRD is not used by any of the current OAuth WG documents, see =
http://datatracker.ietf.org/wg/oauth/


On Jun 22, 2011, at 8:08 AM, Mark Nottingham wrote:

> * 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.


From cb.list6@gmail.com  Sun Jul  3 05:32:34 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 AACA721F87AC; Sun,  3 Jul 2011 05:32:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.563
X-Spam-Level: 
X-Spam-Status: No, score=-1.563 tagged_above=-999 required=5 tests=[AWL=-0.865, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, MANGLED_WANT=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 N4FpSYqV0Jod; Sun,  3 Jul 2011 05:32:33 -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 999A421F876A; Sun,  3 Jul 2011 05:32:24 -0700 (PDT)
Received: by wyj26 with SMTP id 26so3426223wyj.31 for <multiple recipients>; Sun, 03 Jul 2011 05:32:23 -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=Opp2cZ1zmtuZwRhX16bpqEZ87wCKJmobHMDB5uYD5Zs=; b=di+cdXj8nmLe6U/d/vrlOl/9QZiCKezLyNlcgLBwo+hqBGFi+Qy2gp1w+UHNzMdg3D 4wNzPZljWyi4Go31YEqtmtxcdfSQJQv/FUTX6pA2s+HOvS8UEPowvYWnmrw9czWFmouU RV8OmxRo7mf4FiKNDor3dJPrqHK8youxd43rQ=
MIME-Version: 1.0
Received: by 10.216.198.146 with SMTP id v18mr884886wen.94.1309696343497; Sun, 03 Jul 2011 05:32:23 -0700 (PDT)
Received: by 10.216.39.83 with HTTP; Sun, 3 Jul 2011 05:32:23 -0700 (PDT)
Received: by 10.216.39.83 with HTTP; Sun, 3 Jul 2011 05:32:23 -0700 (PDT)
In-Reply-To: <9601ECDE-CFBF-498A-B12D-86A1D1EE4EAC@network-heretics.com>
References: <4E100ACB.70907@globis.net> <806331F9-2A3D-459C-8774-BED1346C475F@network-heretics.com> <4E10172F.3070105@globis.net> <9601ECDE-CFBF-498A-B12D-86A1D1EE4EAC@network-heretics.com>
Date: Sun, 3 Jul 2011 05:32:23 -0700
Message-ID: <CAD6AjGTBhGs4SfXzcxt_tvk=vVjmgmL1h4JFkMVP0hnX0TqLdQ@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
From: Cameron Byrne <cb.list6@gmail.com>
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=0016e6d59e1b515c5704a72971fa
Cc: Ray Hunter <v6ops@globis.net>, "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: Sun, 03 Jul 2011 12:32:34 -0000

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

On Jul 3, 2011 12:29 AM, "Keith Moore" <moore@network-heretics.com> wrote:
>
>
> On Jul 3, 2011, at 3:15 AM, Ray Hunter wrote:
>
> > Keith Moore wrote:
> >>
> >> On Jul 3, 2011, at 2:23 AM, Ray Hunter wrote:
> >>
> >>
> >>> IMHO Right now, we need services with native IPv6 based interfaces,
with equivalent performance and equivalent features and equivalent price
that we have today with IPv4. Anything that detracts from the roll out of
native IPv6 based service interfaces at this time is a bad move IMVHO and
hastens the day that the Internet fragments into a bunch of CGN zones, that
is dominated by businesses that can afford to buy public IPv4 addresses for
their servers or services, or whose business model relies on NAT traversal
being difficult. I personally don't want that sort of Internet.
> >>>
> >>
> >> Right now, applications developers need to be able to write and ship
code that uses IPv6 and can talk to other application instances using IPv6.
  Anything that detracts from the ability of applications to use IPv6 at
this time is a bad move IMHO and decreases the chance that there will ever
be sufficient use of IPv6 (of any kind) to justify widespread deployment of
native IPv6.
> >>
> >>
> >>> Given that development and engineering support time is finite, I'd
much rather that 6to4 was declared historic so that developers and engineers
could spend more time on deployment of native IPv6 service interfaces.
> >>>
> >>
> >> I have a better suggestion: let's declare NAT historic.  That would
free up lots of developers and engineers to spend time on both native v6 and
better v6 transition mechanisms.  Not only would they not need to engineer
new NATs, applications developers wouldn't need to engineer new workarounds
for new NATs.  Everybody would win.
> >>
> >> Keith
> >>
> >>
> > I'm presuming your second comment was facetious.
>
> Mostly.   Though I do think that declaring NAT historic is absolutely as
valid as declaring 6to4 historic.    Both 6to4 and NAT are things that are
useful in some cases and cause harm in others.  Except that 6to4 doesn't
actually cause harm except in conjunction with other dubious practices
(bogus anycast route advertisements, protocol 41 filtering, use public IPv4
addresses behind LSN) which are outside of 6to4's scope, whereas NAT
inherently causes harm.
>

Right. Because you are not accountable for growing the internet or customer
experience. The people that say kill 6to4 are. I hope that is clear to iesg.
Please look closely at the motives.

Cb

> But it wan't a serious suggestion, just an analogy.
>
> > I'm also presuming from your first comment that you will thus oppose the
proposal to turn off 6to4 by default.
> >
> > Am I correct?
>
> I've already said on several occasions that I agree that 6to4 should be
off by default.   It's mostly the Historic label that I have the problem
with.   (I have other objections to the document also, but those are just
places where I think the wording is misleading.  The label is the big
thing.)
>
> Keith
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

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

<p><br>
On Jul 3, 2011 12:29 AM, &quot;Keith Moore&quot; &lt;<a href=3D"mailto:moor=
e@network-heretics.com">moore@network-heretics.com</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; On Jul 3, 2011, at 3:15 AM, Ray Hunter wrote:<br>
&gt;<br>
&gt; &gt; Keith Moore wrote:<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; On Jul 3, 2011, at 2:23 AM, Ray Hunter wrote:<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt; IMHO Right now, we need services with native IPv6 based i=
nterfaces, with equivalent performance and equivalent features and equivale=
nt price that we have today with IPv4. Anything that detracts from the roll=
 out of native IPv6 based service interfaces at this time is a bad move IMV=
HO and hastens the day that the Internet fragments into a bunch of CGN zone=
s, that is dominated by businesses that can afford to buy public IPv4 addre=
sses for their servers or services, or whose business model relies on NAT t=
raversal being difficult. I personally don&#39;t want that sort of Internet=
.<br>

&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Right now, applications developers need to be able to write a=
nd ship code that uses IPv6 and can talk to other application instances usi=
ng IPv6. =A0 Anything that detracts from the ability of applications to use=
 IPv6 at this time is a bad move IMHO and decreases the chance that there w=
ill ever be sufficient use of IPv6 (of any kind) to justify widespread depl=
oyment of native IPv6.<br>

&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt; Given that development and engineering support time is fi=
nite, I&#39;d much rather that 6to4 was declared historic so that developer=
s and engineers could spend more time on deployment of native IPv6 service =
interfaces.<br>

&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; I have a better suggestion: let&#39;s declare NAT historic. =
=A0That would free up lots of developers and engineers to spend time on bot=
h native v6 and better v6 transition mechanisms. =A0Not only would they not=
 need to engineer new NATs, applications developers wouldn&#39;t need to en=
gineer new workarounds for new NATs. =A0Everybody would win.<br>

&gt; &gt;&gt;<br>
&gt; &gt;&gt; Keith<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt; I&#39;m presuming your second comment was facetious.<br>
&gt;<br>
&gt; Mostly. =A0 Though I do think that declaring NAT historic is absolutel=
y as valid as declaring 6to4 historic. =A0 =A0Both 6to4 and NAT are things =
that are useful in some cases and cause harm in others. =A0Except that 6to4=
 doesn&#39;t actually cause harm except in conjunction with other dubious p=
ractices (bogus anycast route advertisements, protocol 41 filtering, use pu=
blic IPv4 addresses behind LSN) which are outside of 6to4&#39;s scope, wher=
eas NAT inherently causes harm.<br>

&gt;</p>
<p>Right. Because you are not accountable for growing the internet or custo=
mer experience. The people that say kill 6to4 are. I hope that is clear to =
iesg. Please look closely at the motives. </p>
<p>Cb <br></p>
<p>&gt; But it wan&#39;t a serious suggestion, just an analogy.<br>
&gt;<br>
&gt; &gt; I&#39;m also presuming from your first comment that you will thus=
 oppose the proposal to turn off 6to4 by default.<br>
&gt; &gt;<br>
&gt; &gt; Am I correct?<br>
&gt;<br>
&gt; I&#39;ve already said on several occasions that I agree that 6to4 shou=
ld be off by default. =A0 It&#39;s mostly the Historic label that I have th=
e problem with. =A0 (I have other objections to the document also, but thos=
e are just places where I think the wording is misleading. =A0The label is =
the big thing.)<br>

&gt;<br>
&gt; Keith<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>

--0016e6d59e1b515c5704a72971fa--

From moore@network-heretics.com  Sun Jul  3 06:01:51 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 8350721F87F6; Sun,  3 Jul 2011 06:01:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.487
X-Spam-Level: 
X-Spam-Status: No, score=-3.487 tagged_above=-999 required=5 tests=[AWL=0.112,  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 Bc+v4wBPoAxd; Sun,  3 Jul 2011 06:01:50 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id C978521F87E6; Sun,  3 Jul 2011 06:01:50 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id 792682354E; Sun,  3 Jul 2011 09:01:50 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Sun, 03 Jul 2011 09:01:50 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=TCbl8boC0QZnqNndqR1+78kCkI0=; b=JpNP7njdGkM0ZGwSGeFENVtd3SzOn2GUIr4wk49LGEjLr/LHnFWlXd9wHSnI01lDjS4HWHWPQQWaoxhX4NgKKoNntb0ux75kkIlmvd2DKSn1NAk5rwFEq68lplPOA/OkISaJKEvGWA9z+W9ZuhQOcBUzYI3g9H8bacpZMPv9x+o=
X-Sasl-enc: 4sy93sHtML0Cxa4TtKDsu5Spqkdkh/84WQCXezRnp/Tv 1309698109
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 6F42B400556; Sun,  3 Jul 2011 09:01:49 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
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: <20110703111047.GB2304@Space.Net>
Date: Sun, 3 Jul 2011 09:01:31 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <1F8EDDA8-21A8-4C6C-93D1-F8852245E173@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <DE414D2B-82ED-4C32-AFDF-EDAAB6D743B2@network-heretics.com> <CAKD1Yr0=pJwOzRvTNskS7YDBNa7Fc=8srGzH2qJUKwGHdCAELg@mail.gmail.com> <A1DA82E2-B979-4719-9F78-DEB263B256A1@network-heretics.com> <20110703111047.GB2304@Space.Net>
To: Gert Doering <gert@space.net>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 13:01:51 -0000

On Jul 3, 2011, at 7:10 AM, Gert Doering wrote:

> On Sat, Jul 02, 2011 at 11:11:43PM -0400, Keith Moore wrote:
>> There's clearly a lack of consensus to support it.
>=20
> There's two very vocal persons opposing it and a much larger number of
> people that support it, but have not the time to write a similarily
> large amount of e-mails.  For me, this is enough for "rough =
consensus".

There were several people opposing it at Last Call - enough that no =
amount of emails in favor would result in rough consensus.   What this =
is, is an attempt to railroad this through IETF without getting =
consensus.

> (And I second everything Lorenzo, Randy and Cameron said - there's=20
> theoretical possibilities, and real world.  6to4 fails the real-world
> test.  Get over it, instead of attacking people that run real-world
> networks for the decisions they need to do to keep the networks =
running
> in a world without enough IPv4 addresses).

In the real world, there are lots of people successfully using 6to4, and =
there's no good replacement for it.

Keith


From moore@network-heretics.com  Sun Jul  3 06:14:36 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 0A77F21F86D3; Sun,  3 Jul 2011 06:14:36 -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.109,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nRYzrSQUsftQ; Sun,  3 Jul 2011 06:14:35 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 37CF921F86D2; Sun,  3 Jul 2011 06:14:35 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id E1E10295AE; Sun,  3 Jul 2011 09:14:33 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Sun, 03 Jul 2011 09:14:33 -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=sVMVYztyxl8bZOt29/PC57A+kmE=; b=TF1z8zrqHPoVu8TebqvM0PE4Tad35twTud5EDG/lwuao2Udw11wNjwh/PuTjfLO2HCk04qYoJXDSuoLKhgvq+viiby0MjgCxq6zzi/7Jv6NISniNQ8g1LicIf4S5ICErCVYsL27A/rIIPb4Q8MnYnW9YwjZ3SFEd65COLtB/m6s=
X-Sasl-enc: BpmkNjQ55xNalyIGL4G+1bojexTzV9K5n0VZ8ciXk9jO 1309698873
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 BF63A40034F; Sun,  3 Jul 2011 09:14:32 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-119-679173293
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <CAD6AjGTBhGs4SfXzcxt_tvk=vVjmgmL1h4JFkMVP0hnX0TqLdQ@mail.gmail.com>
Date: Sun, 3 Jul 2011 09:14:14 -0400
Message-Id: <94253014-42C1-467F-9752-42ED4231DDB6@network-heretics.com>
References: <4E100ACB.70907@globis.net> <806331F9-2A3D-459C-8774-BED1346C475F@network-heretics.com> <4E10172F.3070105@globis.net> <9601ECDE-CFBF-498A-B12D-86A1D1EE4EAC@network-heretics.com> <CAD6AjGTBhGs4SfXzcxt_tvk=vVjmgmL1h4JFkMVP0hnX0TqLdQ@mail.gmail.com>
To: Cameron Byrne <cb.list6@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Ray Hunter <v6ops@globis.net>, "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: Sun, 03 Jul 2011 13:14:36 -0000

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

On Jul 3, 2011, at 8:32 AM, Cameron Byrne wrote:
> > > I'm presuming your second comment was facetious.
> >
> > Mostly.   Though I do think that declaring NAT historic is =
absolutely as valid as declaring 6to4 historic.    Both 6to4 and NAT are =
things that are useful in some cases and cause harm in others.  Except =
that 6to4 doesn't actually cause harm except in conjunction with other =
dubious practices (bogus anycast route advertisements, protocol 41 =
filtering, use public IPv4 addresses behind LSN) which are outside of =
6to4's scope, whereas NAT inherently causes harm.
> >
>=20
> Right. Because you are not accountable for growing the internet or =
customer experience. The people that say kill 6to4 are. I hope that is =
clear to iesg. Please look closely at the motives.
>=20

Note that the ONLY substantive thing we're arguing about here is the =
Historic label.    I don't see any significant disagreement about the =
technical details.

Keith


--Apple-Mail-119-679173293
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 Jul 3, 2011, at 8:32 AM, Cameron Byrne wrote:</div><blockquote type="cite"><p>
&gt; &gt; I'm presuming your second comment was facetious.<br>
&gt;<br>
&gt; Mostly. &nbsp; Though I do think that declaring NAT historic is absolutely as valid as declaring 6to4 historic. &nbsp; &nbsp;Both 6to4 and NAT are things that are useful in some cases and cause harm in others. &nbsp;Except that 6to4 doesn't actually cause harm except in conjunction with other dubious practices (bogus anycast route advertisements, protocol 41 filtering, use public IPv4 addresses behind LSN) which are outside of 6to4's scope, whereas NAT inherently causes harm.<br>

&gt;</p><p>Right. Because you are not accountable for growing the internet or customer experience.&nbsp;The people that say kill 6to4 are. I hope that is clear to iesg. Please look closely at the motives.</p></blockquote></div><div>Note that the ONLY substantive thing we're arguing about here is the Historic label. &nbsp; &nbsp;I don't see any significant disagreement about the technical details.</div><div><br></div><div>Keith</div><div><br></div></body></html>
--Apple-Mail-119-679173293--

From moore@network-heretics.com  Sun Jul  3 06:59:51 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 5FC2721F86EA; Sun,  3 Jul 2011 06:59:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.492
X-Spam-Level: 
X-Spam-Status: No, score=-3.492 tagged_above=-999 required=5 tests=[AWL=0.107,  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 QTr7lLimmtYU; Sun,  3 Jul 2011 06:59:50 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id BEAEB21F86E7; Sun,  3 Jul 2011 06:59:50 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id E1E4523ACF; Sun,  3 Jul 2011 09:59:49 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Sun, 03 Jul 2011 09:59: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=5N7vBNX+REBdp2bIu6p2Xnf9G6M=; b=LeDN7+adZ5OG0hp+kuDfbg5FZ/iHQipUyKeGQ9A77iBqhALeOGFqjjia6/mW3687Uj5m9j6pf9vE++MYfjGp01+iZsFyH0V5VmipVdTVBj/r4UpIotChkFcANLhdiJ1b8+GgyxKLOXdEIBQT+k94oHO76ZKOFvLcPelFMu8mFHY=
X-Sasl-enc: IWIHsdIm4tFZIX3W8+UkF4PFLfN+EcZCmpOVJx/bmBLW 1309701589
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 0AF90400537; Sun,  3 Jul 2011 09:59:48 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
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: <m27h7zketa.wl%randy@psg.com>
Date: Sun, 3 Jul 2011 09:59:31 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2DBDB375-BA46-47B5-A170-8B564CD811A7@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com> <20110703112048.4a3c7111@opy.nosense.org> <4E0FD788.3000305@dougbarton.us> <20110703131913.28142ec0@opy.nosense.org> <4E10132E.3050902@dougbarton.us> <m27h7zketa.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1084)
Cc: IPv6 Ops 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: Sun, 03 Jul 2011 13:59:51 -0000

On Jul 3, 2011, at 3:23 AM, Randy Bush wrote:

> geoff's presos show the 6to4 train wreck pretty clearly.  and it ain't
> pretty.
>=20
> yes, a few geeks such as rob austein, keith moore, ... who desperately
> want to test ipv6 can manage to get it working.  big whoopie doo.=20

I don't understand the desire to dismiss applications developers or =
existing 6to4 users as "a few geeks", but it's clearly a =
misrepresentation.

> it is a disaster for a significant percentage of the end users.  it =
needs to be stopped.

no, it needs to be fixed.  and many of the fixes have nothing to do with =
6to4 implementations, but rather, with operators.

Keith


From jnc@mercury.lcs.mit.edu  Sun Jul  3 07:07:40 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 B889221F86EF; Sun,  3 Jul 2011 07:07:40 -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 c0FZ+yhhWmWq; Sun,  3 Jul 2011 07:07:40 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 4700E21F86EC; Sun,  3 Jul 2011 07:07:40 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 08F5C18C13C; Sun,  3 Jul 2011 10:07:39 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Message-Id: <20110703140739.08F5C18C13C@mercury.lcs.mit.edu>
Date: Sun,  3 Jul 2011 10:07:39 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: v6ops@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: Sun, 03 Jul 2011 14:07:40 -0000

    > From: Lorenzo Colitti <lorenzo@google.com>

    > Compared to the alternative of publishing 6to4-historic now, it:

    > a) Delays the time of any statement made by the IETF on the question
    > by at least a number of months, while vendors and home gateways are
    > *still shipping* products that implement 6to4 and enable it by
    > default.

draft-ietf-v6ops-6to4-advisory - which already exists, and which nobody is
objecting to - already contains text which tells manufacturers of both
home routers and hosts to disable 6to4 by default, etc, etc. If acting
ASAP is desirable, that ID could be approved just as quickly as
draft-ietf-v6ops-6to4-to-historic-05.txt could be (to be later updated by
the new document mentioned in the recent announcement).

    > b) Even assuming it were to gain consensus in any sort of reasonable
    > timescale, it would provide a less clear statement, and thus be less
    > of an incentive for implementors such as home gateway manufacturers
    > to do the right thing and remove it.

First, killing 6to4 is an additional goal, above and beyond 'stop 6to4
from causing problems'. The only conceivable reason I can think of for
that additional step seems to be the possibility that somehow 6to4 will
cause problems anyway, even if it is normally disabled? This seems
unlikely to me. Is there any reason beyond that to kill 6to4?

Second, what reason is there to believe that a document that says 'remove
6to4' is going to meet with greater/faster compliance from vendors than a
document that says 'disable it'? I would argue that the former takes more
engineering time, and is actually marginally less likely to be timely
responded to.

	Noel

From jnc@mercury.lcs.mit.edu  Sun Jul  3 07:12: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 7749721F866E; Sun,  3 Jul 2011 07:12:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C9bmU8A6hEY4; Sun,  3 Jul 2011 07:12:12 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 07CA321F85BB; Sun,  3 Jul 2011 07:12:09 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 6B3BD18C13C; Sun,  3 Jul 2011 10:12:09 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Message-Id: <20110703141209.6B3BD18C13C@mercury.lcs.mit.edu>
Date: Sun,  3 Jul 2011 10:12:09 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: v6ops@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: Sun, 03 Jul 2011 14:12:12 -0000

    > From: Doug Barton <dougb@dougbarton.us>

    > Bad 6to4 (which almost all of it is)

draft-ietf-v6ops-6to4-advisory says:

  The experiment conducted by Aben recorded a failure rate of between 9%
  and 20% of all 6to4 connection attempts. The experiment conducted by
  Huston has recorded a failure rate of between 9% and 19% of all 6to4
  clients.

20% != "almost all of it".

    > I realize that there are a lot of people that dismiss both the
    > evidence that's been put forward

This is again a complete misrepresentation of the actual situation. Please
name _one_ person who thinks that automatically enabled 6to4 is not
causing any problems.

	Noel

From moore@network-heretics.com  Sun Jul  3 07:12: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 9A42621F8722; Sun,  3 Jul 2011 07:12:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.495
X-Spam-Level: 
X-Spam-Status: No, score=-4.495 tagged_above=-999 required=5 tests=[AWL=1.104,  BAYES_00=-2.599, GB_I_LETTER=-2, 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 fn8b1xPBJ25s; Sun,  3 Jul 2011 07:12: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 7B10F21F8713; Sun,  3 Jul 2011 07:12:30 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 3394F293E9; Sun,  3 Jul 2011 10:12:30 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Sun, 03 Jul 2011 10:12: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:content-transfer-encoding:message-id:references:to; s=smtpout; bh=hFHhoS8/PCpbJzQAOSVEoV+KIP4=; b=odgPwfuT69SC9J0rZNNxF5zy65R5VyQvRiy58rME3rHjajuIPGjBcV5BD1ohirIf8DsfsS8Ys5UHurcRvMjUdeYUIAVTB3ucfm6tDTyixN6SJdPUGAaK+3OyYJc3a/9FO7xjx7oBJ0wiOs3qksNAy1I/T5uuv4vE1H3NKqUkHc4=
X-Sasl-enc: QrgxGVXaHBrJfuKYWwqs2HbYyJL7+aJwR9jLxm8+RNZ+ 1309702349
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 E9E3E401B68; Sun,  3 Jul 2011 10:12:28 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
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: <m1QdKfr-0001jNC@stereo.hq.phicoh.net>
Date: Sun, 3 Jul 2011 10:12:11 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E3CF6B2C-B177-4A6A-898C-4EA8C8CA65D5@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com> <20110703112048.4a3c7111@opy.nosense.org> <4E0FD788.3000305@dougbarton.us> <20110703131913.28142ec0@opy.nosense.org> <CAKD1Yr0dU8xGPc5tY8qK7w7Vc57zzj2BBipCb3b3VsXLov-JUw@mail.gmail.com> <m1QdKfr-0001jNC@stereo.hq.phicoh.net>
To: Philip Homburg <pch-v6ops@u-1.phicoh.com>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 14:12:31 -0000

On Jul 3, 2011, at 7:17 AM, Philip Homburg wrote:

> In your letter dated Sun, 3 Jul 2011 07:53:46 +0200 you wrote:
>> Unfortunately, in the 20% of the time that it's not working, Google =
has no
>> idea that the user has a 2002::/16 address. Google only knows, after =
the
>> fact, that the user suffered a 20 or 75-second timeout and was not =
happy. So
>> it would serve no purpose to avoid serving users that successfully =
connect
>> from 2002::/16 addresses; once the AAAA record is handed out, the =
damage is
>> done. What Google could do, however, is stop handing out AAAA records =
to
>> networks that have significant number of 6to4 users in the future. =
We're
>> considering this.
>=20
> I think this clearly illustrates why the IETF should issue a strong =
statement
> that no new 6to4 installation should be deplayed and the existing 6to4 =
users
> should migrate to other tunneling techniques (if native is not =
available).

I think this clearly illustrates why IETF should issue a strong =
statement that

a) operators of 6to4 relays should not advertise those relays via BGP =
unless they're routing traffic for all of 2002://16 or native v6, =
respectively
b) operators should not filter protocol 41traffic
c) (maybe) operators using LSN should use RFC 1918 addresses behind =
those NATs unless/until there's another address range that 6to4 host =
implementations know about
d) 6to4 should be disabled by default in both hosts and routers
e) host implementations should prefer native v4 destinations over 6to4 =
destinations when both are available and the application can use either =
IPv4 or IPv6

Saying that no new 6to4 installation should be deployed and that =
existing 6to4 users should migrate to other tunneling techniques assumes =
that all installations and users have the same needs, namely, to access =
content over IPv6 that is also available over IPv4.

> The problem with 6to4 is it was rolled out on a relatively large scale =
when=20
> there was essentially no IPv6 content. As a result, the people who had =
a
> broken 6to4 setup would only find out when content providers would =
start
> adding AAAA records.=20
>=20
> In other words, it was ticking time bomb.

The label "broken 6to4 setup" is misleading.   Most of the time, the =
thing that breaks 6to4 is not the user's "setup"; it's an ISP somewhere =
that is either (a) advertising a bad relay or (b) filtering protocol 41. =
  (If the problem were the users' setups, the providers could just say =
"not our problem; fix your 6to4 setup")

> What worries me is that people will start using 6to4 for bittorrent. =
Bittorrent
> will of course completely hide broken setups and worse, it will also =
hide=20
> broken 6to4 relays.=20

=46rom my understanding of bittorrent, it will just find other routes.

> And all of this, because a few hobbyists are afraid that declaring =
6to4 as
> historic will require them to search a bit harder in the furture for a
> router that supports 6to4.

You completely misunderstand both the situation, and the size and =
diversity of 6to4 users. =20

Keith


From moore@network-heretics.com  Sun Jul  3 07:22: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 6C11A21F8722; Sun,  3 Jul 2011 07:22:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.522
X-Spam-Level: 
X-Spam-Status: No, score=-3.522 tagged_above=-999 required=5 tests=[AWL=0.077,  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 dF9lkCBYQeMo; Sun,  3 Jul 2011 07:22: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 7806421F870B; Sun,  3 Jul 2011 07:22:54 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id 3136129546; Sun,  3 Jul 2011 10:22:54 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Sun, 03 Jul 2011 10:22: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=RozvxWDOR7rE4WYhIiKMnefS0vA=; b=aBZqiZVS652UfbBHtH7dw9+g6s+JJSur93/u2DpOpIn+cjesjpJsTl9Yuw5YQ/tYwEA2jsaXAqrhEzA6Onvm0wLhfbb7OtOysJI7gDSylgQsMhoUQ1pw/6ag1zLbSTW4j/u7n6Qb3nJoG+KZ67sA4bCvQXXZXzuRGHUPNwBNcro=
X-Sasl-enc: dkCFA6qusTVA8lQcuKdK7zTu8poGz4GDTxkgTCVVEXQo 1309702973
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 68BA540471B; Sun,  3 Jul 2011 10:22:53 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
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: <20110703140739.08F5C18C13C@mercury.lcs.mit.edu>
Date: Sun, 3 Jul 2011 10:22:35 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C6ED5256-91C0-4CFE-9D4E-471585370988@network-heretics.com>
References: <20110703140739.08F5C18C13C@mercury.lcs.mit.edu>
To: jnc@mercury.lcs.mit.edu (Noel Chiappa)
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: Sun, 03 Jul 2011 14:22:57 -0000

On Jul 3, 2011, at 10:07 AM, Noel Chiappa wrote:

> draft-ietf-v6ops-6to4-advisory - which already exists, and which =
nobody is
> objecting to - already contains text which tells manufacturers of both
> home routers and hosts to disable 6to4 by default, etc, etc. If acting
> ASAP is desirable, that ID could be approved just as quickly as
> draft-ietf-v6ops-6to4-to-historic-05.txt could be (to be later updated =
by
> the new document mentioned in the recent announcement).

It's already been approved.  The announcement went out on July 1.  =
Though to be fair, the document is Informational rather than an update =
to a standards track document.

Keith


From cb.list6@gmail.com  Sun Jul  3 07:32:36 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 7FB011F0C64; Sun,  3 Jul 2011 07:32:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.569
X-Spam-Level: 
X-Spam-Status: No, score=-3.569 tagged_above=-999 required=5 tests=[AWL=1.429,  BAYES_00=-2.599, GB_I_LETTER=-2, 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 2S33+16RRlWN; Sun,  3 Jul 2011 07:32:35 -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 186C81F0C65; Sun,  3 Jul 2011 07:32:34 -0700 (PDT)
Received: by wyj26 with SMTP id 26so3460063wyj.31 for <multiple recipients>; Sun, 03 Jul 2011 07:32:34 -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=UPpl7RuX5cLitJ4smKzinUamUAvqFFg/r8fK+Z7b/w8=; b=gundcwjWFqN8VMWexhjPcHhux2oEkA1ICzOFSoK9PweEBwK03QmtOChmTOf3yJUudM /6Qv56CNg4gfjQG/gztapKd5MRc7v2n+uVD/jVXLoMEqh8BzIBkcoikJK2OoTV/I0eqk 3xcXIhG8vBznBY9xy1ZvGWyyCBI2lau05R5LU=
MIME-Version: 1.0
Received: by 10.216.63.131 with SMTP id a3mr4261316wed.64.1309703553084; Sun, 03 Jul 2011 07:32:33 -0700 (PDT)
Received: by 10.216.39.83 with HTTP; Sun, 3 Jul 2011 07:32:32 -0700 (PDT)
Received: by 10.216.39.83 with HTTP; Sun, 3 Jul 2011 07:32:32 -0700 (PDT)
In-Reply-To: <E3CF6B2C-B177-4A6A-898C-4EA8C8CA65D5@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com> <20110703112048.4a3c7111@opy.nosense.org> <4E0FD788.3000305@dougbarton.us> <20110703131913.28142ec0@opy.nosense.org> <CAKD1Yr0dU8xGPc5tY8qK7w7Vc57zzj2BBipCb3b3VsXLov-JUw@mail.gmail.com> <m1QdKfr-0001jNC@stereo.hq.phicoh.net> <E3CF6B2C-B177-4A6A-898C-4EA8C8CA65D5@network-heretics.com>
Date: Sun, 3 Jul 2011 07:32:32 -0700
Message-ID: <CAD6AjGSUEmdKk3trTdRXMyrnp8FFyvHUWBSgeBrHT_2jPjXUBA@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
From: Cameron Byrne <cb.list6@gmail.com>
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=000e0cdfd8bc0aec8504a72b1f2b
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, Philip Homburg <pch-v6ops@u-1.phicoh.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: Sun, 03 Jul 2011 14:32:36 -0000

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

On Jul 3, 2011 7:14 AM, "Keith Moore" <moore@network-heretics.com> wrote:
>
> On Jul 3, 2011, at 7:17 AM, Philip Homburg wrote:
>
> > In your letter dated Sun, 3 Jul 2011 07:53:46 +0200 you wrote:
> >> Unfortunately, in the 20% of the time that it's not working, Google has
no
> >> idea that the user has a 2002::/16 address. Google only knows, after
the
> >> fact, that the user suffered a 20 or 75-second timeout and was not
happy. So
> >> it would serve no purpose to avoid serving users that successfully
connect
> >> from 2002::/16 addresses; once the AAAA record is handed out, the
damage is
> >> done. What Google could do, however, is stop handing out AAAA records
to
> >> networks that have significant number of 6to4 users in the future.
We're
> >> considering this.
> >
> > I think this clearly illustrates why the IETF should issue a strong
statement
> > that no new 6to4 installation should be deplayed and the existing 6to4
users
> > should migrate to other tunneling techniques (if native is not
available).
>
> I think this clearly illustrates why IETF should issue a strong statement
that
>
> a) operators of 6to4 relays should not advertise those relays via BGP
unless they're routing traffic for all of 2002://16 or native v6,
respectively
> b) operators should not filter protocol 41traffic
> c) (maybe) operators using LSN should use RFC 1918 addresses behind those
NATs unless/until there's another address range that 6to4 host
implementations know about
> d) 6to4 should be disabled by default in both hosts and routers
> e) host implementations should prefer native v4 destinations over 6to4
destinations when both are available and the application can use either IPv4
or IPv6
>

You will not get "consensus" on these statements in the IETF or by the
various companies that implement gear and networks in the REAL world.

Can we let this thread die now? If the ietf will not kill 6to4, there are
several other methods to deal with it in the REAL world (dns whitelisting,
null routes, rfp's, blocking aaaa on ipv4 ....). Just like the NAT debacle
of years past , the IETF has once again proven its irrelevance.

Thanks for your time and have a great weekend.

Cb

> Saying that no new 6to4 installation should be deployed and that existing
6to4 users should migrate to other tunneling techniques assumes that all
installations and users have the same needs, namely, to access content over
IPv6 that is also available over IPv4.
>
> > The problem with 6to4 is it was rolled out on a relatively large scale
when
> > there was essentially no IPv6 content. As a result, the people who had a
> > broken 6to4 setup would only find out when content providers would start
> > adding AAAA records.
> >
> > In other words, it was ticking time bomb.
>
> The label "broken 6to4 setup" is misleading.   Most of the time, the thing
that breaks 6to4 is not the user's "setup"; it's an ISP somewhere that is
either (a) advertising a bad relay or (b) filtering protocol 41.   (If the
problem were the users' setups, the providers could just say "not our
problem; fix your 6to4 setup")
>
> > What worries me is that people will start using 6to4 for bittorrent.
Bittorrent
> > will of course completely hide broken setups and worse, it will also
hide
> > broken 6to4 relays.
>
> From my understanding of bittorrent, it will just find other routes.
>
> > And all of this, because a few hobbyists are afraid that declaring 6to4
as
> > historic will require them to search a bit harder in the furture for a
> > router that supports 6to4.
>
> You completely misunderstand both the situation, and the size and
diversity of 6to4 users.
>
> Keith
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

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

<p><br>
On Jul 3, 2011 7:14 AM, &quot;Keith Moore&quot; &lt;<a href=3D"mailto:moore=
@network-heretics.com">moore@network-heretics.com</a>&gt; wrote:<br>
&gt;<br>
&gt; On Jul 3, 2011, at 7:17 AM, Philip Homburg wrote:<br>
&gt;<br>
&gt; &gt; In your letter dated Sun, 3 Jul 2011 07:53:46 +0200 you wrote:<br=
>
&gt; &gt;&gt; Unfortunately, in the 20% of the time that it&#39;s not worki=
ng, Google has no<br>
&gt; &gt;&gt; idea that the user has a 2002::/16 address. Google only knows=
, after the<br>
&gt; &gt;&gt; fact, that the user suffered a 20 or 75-second timeout and wa=
s not happy. So<br>
&gt; &gt;&gt; it would serve no purpose to avoid serving users that success=
fully connect<br>
&gt; &gt;&gt; from 2002::/16 addresses; once the AAAA record is handed out,=
 the damage is<br>
&gt; &gt;&gt; done. What Google could do, however, is stop handing out AAAA=
 records to<br>
&gt; &gt;&gt; networks that have significant number of 6to4 users in the fu=
ture. We&#39;re<br>
&gt; &gt;&gt; considering this.<br>
&gt; &gt;<br>
&gt; &gt; I think this clearly illustrates why the IETF should issue a stro=
ng statement<br>
&gt; &gt; that no new 6to4 installation should be deplayed and the existing=
 6to4 users<br>
&gt; &gt; should migrate to other tunneling techniques (if native is not av=
ailable).<br>
&gt;<br>
&gt; I think this clearly illustrates why IETF should issue a strong statem=
ent that<br>
&gt;<br>
&gt; a) operators of 6to4 relays should not advertise those relays via BGP =
unless they&#39;re routing traffic for all of 2002://16 or native v6, respe=
ctively<br>
&gt; b) operators should not filter protocol 41traffic<br>
&gt; c) (maybe) operators using LSN should use RFC 1918 addresses behind th=
ose NATs unless/until there&#39;s another address range that 6to4 host impl=
ementations know about<br>
&gt; d) 6to4 should be disabled by default in both hosts and routers<br>
&gt; e) host implementations should prefer native v4 destinations over 6to4=
 destinations when both are available and the application can use either IP=
v4 or IPv6<br>
&gt;</p>
<p>You will not get &quot;consensus&quot; on these statements in the IETF o=
r by the various companies that implement gear and networks in the REAL wor=
ld. </p>
<p>Can we let this thread die now? If the ietf will not kill 6to4, there ar=
e several other methods to deal with it in the REAL world (dns whitelisting=
, null routes, rfp&#39;s, blocking aaaa on ipv4 ....). Just like the NAT de=
bacle of years past , the IETF has once again proven its irrelevance. </p>

<p>Thanks for your time and have a great weekend. </p>
<p>Cb</p>
<p>&gt; Saying that no new 6to4 installation should be deployed and that ex=
isting 6to4 users should migrate to other tunneling techniques assumes that=
 all installations and users have the same needs, namely, to access content=
 over IPv6 that is also available over IPv4.<br>

&gt;<br>
&gt; &gt; The problem with 6to4 is it was rolled out on a relatively large =
scale when<br>
&gt; &gt; there was essentially no IPv6 content. As a result, the people wh=
o had a<br>
&gt; &gt; broken 6to4 setup would only find out when content providers woul=
d start<br>
&gt; &gt; adding AAAA records.<br>
&gt; &gt;<br>
&gt; &gt; In other words, it was ticking time bomb.<br>
&gt;<br>
&gt; The label &quot;broken 6to4 setup&quot; is misleading. =A0 Most of the=
 time, the thing that breaks 6to4 is not the user&#39;s &quot;setup&quot;; =
it&#39;s an ISP somewhere that is either (a) advertising a bad relay or (b)=
 filtering protocol 41. =A0 (If the problem were the users&#39; setups, the=
 providers could just say &quot;not our problem; fix your 6to4 setup&quot;)=
<br>

&gt;<br>
&gt; &gt; What worries me is that people will start using 6to4 for bittorre=
nt. Bittorrent<br>
&gt; &gt; will of course completely hide broken setups and worse, it will a=
lso hide<br>
&gt; &gt; broken 6to4 relays.<br>
&gt;<br>
&gt; From my understanding of bittorrent, it will just find other routes.<b=
r>
&gt;<br>
&gt; &gt; And all of this, because a few hobbyists are afraid that declarin=
g 6to4 as<br>
&gt; &gt; historic will require them to search a bit harder in the furture =
for a<br>
&gt; &gt; router that supports 6to4.<br>
&gt;<br>
&gt; You completely misunderstand both the situation, and the size and dive=
rsity of 6to4 users.<br>
&gt;<br>
&gt; Keith<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>

--000e0cdfd8bc0aec8504a72b1f2b--

From moore@network-heretics.com  Sun Jul  3 07:41: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 2046221F85B4; Sun,  3 Jul 2011 07:41:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.223
X-Spam-Level: 
X-Spam-Status: No, score=-3.223 tagged_above=-999 required=5 tests=[AWL=-0.225, 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 oqnb8ruJHMaH; Sun,  3 Jul 2011 07:41:13 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 46A7721F85AE; Sun,  3 Jul 2011 07:41:13 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id F3A79296E5; Sun,  3 Jul 2011 10:41:12 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Sun, 03 Jul 2011 10:41: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:message-id:references:to; s=smtpout; bh=Lga1f8m1Rj5X3iNY6RrCUUc47a8=; b=WD1I8kr8a1pakPn1kny8zEfO3h7/1KU6iULm2cM1F0JgRF319WZVkVGoW0tIniWmR+YmoTm/Jj44XNEwc3Iz0TkuC7T+NjulLhRwfO1rN0oWtMaa/MKyatHtD7ojXrM0fHZZ9EhI7jXJ5cx6wn0qBObKV/jS2LIerywS9BHpRSU=
X-Sasl-enc: czp1FHzGwYZ045GXhT7RV+fdtWsp6OHFplxyfPdJGKh+ 1309704072
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 90808404889; Sun,  3 Jul 2011 10:41:11 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-122-684372071
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <CAD6AjGSUEmdKk3trTdRXMyrnp8FFyvHUWBSgeBrHT_2jPjXUBA@mail.gmail.com>
Date: Sun, 3 Jul 2011 10:40:53 -0400
Message-Id: <100DA5A2-0276-45B8-A8CD-AB7B0D947AC4@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com> <20110703112048.4a3c7111@opy.nosense.org> <4E0FD788.3000305@dougbarton.us> <20110703131913.28142ec0@opy.nosense.org> <CAKD1Yr0dU8xGPc5tY8qK7w7Vc57zzj2BBipCb3b3VsXLov-JUw@mail.gmail.com> <m1QdKfr-0001jNC@stereo.hq.phicoh.net> <E3CF6B2C-B177-4A6A-898C-4EA8C8CA65D5@network-heretics.com> <CAD6AjGSUEmdKk3trTdRXMyrnp8FFyvHUWBSgeBrHT_2jPjXUBA@mail.gmail.com>
To: Cameron Byrne <cb.list6@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, Philip Homburg <pch-v6ops@u-1.phicoh.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: Sun, 03 Jul 2011 14:41:14 -0000

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

On Jul 3, 2011, at 10:32 AM, Cameron Byrne wrote:
> > >
> > > I think this clearly illustrates why the IETF should issue a =
strong statement
> > > that no new 6to4 installation should be deplayed and the existing =
6to4 users
> > > should migrate to other tunneling techniques (if native is not =
available).
> >
> > I think this clearly illustrates why IETF should issue a strong =
statement that
> >
> > a) operators of 6to4 relays should not advertise those relays via =
BGP unless they're routing traffic for all of 2002://16 or native v6, =
respectively
> > b) operators should not filter protocol 41traffic
> > c) (maybe) operators using LSN should use RFC 1918 addresses behind =
those NATs unless/until there's another address range that 6to4 host =
implementations know about
> > d) 6to4 should be disabled by default in both hosts and routers
> > e) host implementations should prefer native v4 destinations over =
6to4 destinations when both are available and the application can use =
either IPv4 or IPv6
> >
>=20
> You will not get "consensus" on these statements in the IETF or by the =
various companies that implement gear and networks in the REAL world.
>=20
why not?  all of those recommendations are clearly appropriate and =
desirable, with the possible exception of (c) because ISP use of RFC =
1918 addresses is likely to conflict with customer user of the same =
address ranges.
> Can we let this thread die now? If the ietf will not kill 6to4, there =
are several other methods to deal with it in the REAL world (dns =
whitelisting, null routes, rfp's, blocking aaaa on ipv4 ....). Just like =
the NAT debacle of years past , the IETF has once again proven its =
irrelevance.
>=20

and the attitude from v6ops reminds me of nothing so much as a lynch =
mob.   it has gotten way out of hand.=20

Keith


--Apple-Mail-122-684372071
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 Jul 3, 2011, at 10:32 AM, Cameron Byrne wrote:</div><blockquote type="cite"><p>
&gt; &gt;<br>
&gt; &gt; I think this clearly illustrates why the IETF should issue a strong statement<br>
&gt; &gt; that no new 6to4 installation should be deplayed and the existing 6to4 users<br>
&gt; &gt; should migrate to other tunneling techniques (if native is not available).<br>
&gt;<br>
&gt; I think this clearly illustrates why IETF should issue a strong statement that<br>
&gt;<br>
&gt; a) operators of 6to4 relays should not advertise those relays via BGP unless they're routing traffic for all of <a href="2002://16">2002://16</a> or native v6, respectively<br>
&gt; b) operators should not filter protocol 41traffic<br>
&gt; c) (maybe) operators using LSN should use RFC 1918 addresses behind those NATs unless/until there's another address range that 6to4 host implementations know about<br>
&gt; d) 6to4 should be disabled by default in both hosts and routers<br>
&gt; e) host implementations should prefer native v4 destinations over 6to4 destinations when both are available and the application can use either IPv4 or IPv6<br>
&gt;</p><p>You will not get "consensus" on these statements in the IETF or by the various companies that implement gear and networks in the REAL world.</p></blockquote>why not? &nbsp;all of those recommendations are clearly appropriate and desirable, with the possible exception of (c) because ISP use of RFC 1918 addresses is likely to conflict with customer user of the same address ranges.</div><div><blockquote type="cite"><p>Can we let this thread die now? If the ietf will not kill 6to4, there are several other methods to deal with it in the REAL world (dns whitelisting, null routes, rfp's, blocking aaaa on ipv4 ....). Just like the NAT debacle of years past , the IETF has once again proven its irrelevance. </p></blockquote></div><div>and the attitude from v6ops reminds me of nothing so much as a lynch mob. &nbsp; it has gotten way out of hand.&nbsp;</div><div><br></div><div>Keith</div><div><br></div></body></html>
--Apple-Mail-122-684372071--

From moore@network-heretics.com  Sun Jul  3 08:11: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 2969A21F85AB; Sun,  3 Jul 2011 08:11:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.518
X-Spam-Level: 
X-Spam-Status: No, score=-3.518 tagged_above=-999 required=5 tests=[AWL=0.080,  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 XZZ+8HvPqnQV; Sun,  3 Jul 2011 08:11: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 D67B621F859E; Sun,  3 Jul 2011 08:11:10 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id BAFEF2960B; Sun,  3 Jul 2011 11:11:08 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Sun, 03 Jul 2011 11:11: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=mD7BoE/R745i9a1pDSRsos/mIf4=; b=Xn5ltpWg6ColQUQPv5gESsM5po+XjPasJV0AZQW/vefRt+W/Mgc9eKWPcSM2uUD8YnCFg+2shbEAmnc9It/HjBnoxeY2JBu9hu8FWGSnb8TRgODWjKRUI5V/bXlESMSsLTiuRs8ufFAkdAWjVV/M9J+fMXApxWGNTPbgP5ZXlY8=
X-Sasl-enc: p9iR6dDrKTWi1HFYa+X4Zx/dfSJ4u5726rExbOQjZHLF 1309705867
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 443D1404EB9; Sun,  3 Jul 2011 11:11:07 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-123-686167784
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <CB106539-9C0F-489C-BBC0-E4ADAF3B8F45@gmail.com>
Date: Sun, 3 Jul 2011 11:10:49 -0400
Message-Id: <746A967B-16AF-4428-8424-298AF8001F87@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com> <20110703112048.4a3c7111@opy.nosense.org> <4E0FD788.3000305@dougbarton.us> <20110703131913.28142ec0@opy.nosense.org> <CAKD1Yr0dU8xGPc5tY8qK7w7Vc57zzj2BBipCb3b3VsXLov-JUw@mail.gmail.com> <m1QdKfr-0001jNC@stereo.hq.phicoh.net> <E3CF6B2C-B177-4A6A-898C-4EA8C8CA65D5@network-heretics.com> <CAD6AjGSUEmdKk3trTdRXMyrnp8FFyvHUWBSgeBrHT_2jPjXUBA@mail.gmail.com> <100DA5A2-0276-45B8-A8CD-AB7B0D947AC4@network-heretics.com> <CB106539-9C0F-489C-BBC0-E4ADAF3B8F45@gmail.com>
To: Arturo Servin <arturo.servin@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: IPv6 Operations <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: Sun, 03 Jul 2011 15:11:13 -0000

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

On Jul 3, 2011, at 10:58 AM, Arturo Servin wrote:

> On 3 Jul 2011, at 11:40, Keith Moore wrote:
>=20
>>> > I think this clearly illustrates why IETF should issue a strong =
statement that
>>> >
>>> > a) operators of 6to4 relays should not advertise those relays via =
BGP unless they're routing traffic for all of 2002://16 or native v6, =
respectively
>>> > b) operators should not filter protocol 41traffic
>>> > c) (maybe) operators using LSN should use RFC 1918 addresses =
behind those NATs unless/until there's another address range that 6to4 =
host implementations know about
>>> > d) 6to4 should be disabled by default in both hosts and routers
>>> > e) host implementations should prefer native v4 destinations over =
6to4 destinations when both are available and the application can use =
either IPv4 or IPv6
>>> >
>>>=20
>>> You will not get "consensus" on these statements in the IETF or by =
the various companies that implement gear and networks in the REAL =
world.
>>>=20
>> why not?  all of those recommendations are clearly appropriate and =
desirable, with the possible exception of (c) because ISP use of RFC =
1918 addresses is likely to conflict with customer user of the same =
address ranges.
>=20
>=20
> 	And b.
>=20
> 	And probably it is too much effort for something that will go =
away (probably sooner that we expect) with the exhaustion of IPv4 =
addresses for each ISP's customer (6to4 does not work with NATs, and =
they are here).

It's clearly inappropriate for operators to be filtering protocol 41.   =
Not only does this break 6to4, it also breaks other tunneling =
mechanisms.  More generally, it's inappropriate for operators to be =
favoring one kind of traffic over another.

The ISPs I've talked to tell me that they see no reason why static, =
public IPv4 addresses cannot continue to be given to those that request =
them, indefinitely, as long as they're paying for business service.=20

If the overriding concern is that imposition of LSN will break 6to4 even =
more and thus generate even more support calls,  that's understandable.  =
However:

- LSN will break a lot more than 6to4, and generate support calls for =
many other reasons, and this shouldn't surprise anyone.
- declaring 6to4 Historic will not reduce the number of support calls, =
while the above measures will.

The most effective single measure that I can see to reduce the number of =
6to4 support calls is to get OS vendors to patch their customers' =
systems to implement (e), and perhaps (d), ASAP.   That shouldn't break =
6to4 for anyone who is using it as a means of supporting IPv6 apps, and =
it should reduce the largest source of complaints both from users and =
content providers. =20

(The reason I say "perhaps" (d) is that (d) would break those who are =
currently depending on 6to4.  "Off by default"  is perfectly appropriate =
for new installations, but not necessarily so for automatic updates.)

Keith


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

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jul 3, 2011, at 10:58 AM, Arturo Servin =
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>On 3 Jul 2011, at =
11:40, Keith Moore 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; "><blockquote =
type=3D"cite"><p>&gt; I think this clearly illustrates why IETF should =
issue a strong statement that<br>&gt;<br>&gt; a) operators of 6to4 =
relays should not advertise those relays via BGP unless they're routing =
traffic for all of&nbsp;<a =
href=3D"x-msg://1551/2002://16">2002://16</a>&nbsp;or native v6, =
respectively<br>&gt; b) operators should not filter protocol =
41traffic<br>&gt; c) (maybe) operators using LSN should use RFC 1918 =
addresses behind those NATs unless/until there's another address range =
that 6to4 host implementations know about<br>&gt; d) 6to4 should be =
disabled by default in both hosts and routers<br>&gt; e) host =
implementations should prefer native v4 destinations over 6to4 =
destinations when both are available and the application can use either =
IPv4 or IPv6<br>&gt;</p><p>You will not get "consensus" on these =
statements in the IETF or by the various companies that implement gear =
and networks in the REAL world.</p></blockquote>why not? &nbsp;all of =
those recommendations are clearly appropriate and desirable, with the =
possible exception of (c) because ISP use of RFC 1918 addresses is =
likely to conflict with customer user of the same address =
ranges.</span></blockquote></div><br></div></blockquote><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; =
"><div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>And =
b.</div><div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>And probably it is too much =
effort for something that will go away (probably sooner that we expect) =
with the exhaustion of IPv4 addresses for each ISP's customer (6to4 does =
not work with NATs, and they are =
here).</div></div></blockquote><div><br></div>It's clearly inappropriate =
for operators to be filtering protocol 41. &nbsp; Not only does this =
break 6to4, it also breaks other tunneling mechanisms. &nbsp;More =
generally, it's inappropriate for operators to be favoring one kind of =
traffic over another.</div><div><br></div><div>The ISPs I've talked to =
tell me that they see no reason why static, public IPv4 addresses cannot =
continue to be given to those that request them, indefinitely, as long =
as they're paying for business =
service.&nbsp;</div><div><br></div><div>If the overriding concern is =
that imposition of LSN will break 6to4 even more and thus generate even =
more support calls, &nbsp;that's understandable. =
&nbsp;However:</div><div><br></div><div>- LSN will break a lot more than =
6to4, and generate support calls for many other reasons, and this =
shouldn't surprise anyone.</div><div>- declaring 6to4 Historic will not =
reduce the number of support calls, while the above measures =
will.</div><div><br></div><div>The most effective single measure that I =
can see to reduce the number of 6to4 support calls is to get OS vendors =
to patch their customers' systems to implement (e), and perhaps (d), =
ASAP. &nbsp; That shouldn't break 6to4 for anyone who is using it as a =
means of supporting IPv6 apps, and it should reduce the largest source =
of complaints both from users and content providers. =
&nbsp;</div><div><br></div><div>(The reason I say "perhaps" (d) is that =
(d) would break those who are currently depending on 6to4. &nbsp;"Off by =
default" &nbsp;is perfectly appropriate for new installations, but not =
necessarily so for automatic =
updates.)</div><div><br></div><div>Keith</div><div><br></div></body></html=
>=

--Apple-Mail-123-686167784--

From Ed.Lewis@neustar.biz  Sun Jul  3 08:33:33 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 EEDA81F0C65 for <ietf@ietfa.amsl.com>; Sun,  3 Jul 2011 08:33:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.099
X-Spam-Level: 
X-Spam-Status: No, score=-107.099 tagged_above=-999 required=5 tests=[AWL=-0.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 gZmG4Whm4OMx for <ietf@ietfa.amsl.com>; Sun,  3 Jul 2011 08:33:32 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id 4D1B91F0C64 for <ietf@ietf.org>; Sun,  3 Jul 2011 08:33:32 -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 p63FXUjm002743; Sun, 3 Jul 2011 11:33:30 -0400 (EDT) (envelope-from Ed.Lewis@neustar.biz)
Received: from [192.168.1.108] by Work-Laptop-2.local (PGP Universal service); Sun, 03 Jul 2011 11:33:32 -0400
X-PGP-Universal: processed; by Work-Laptop-2.local on Sun, 03 Jul 2011 11:33:32 -0400
Mime-Version: 1.0
Message-Id: <a06240800ca363beefeba@[10.31.204.102]>
In-Reply-To: <B8FD63DA-3047-4CE5-8CA0-BA12B54617A1@tcb.net>
References: <a06240800c9df29c0bf75@[10.31.203.186]> <B8FD63DA-3047-4CE5-8CA0-BA12B54617A1@tcb.net>
Date: Sun, 3 Jul 2011 11:32:57 -0400
To: Danny McPherson <danny@tcb.net>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Subject: Re: Comments surrounding draft-iab-dns-applications-01
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
Cc: Edward Lewis <Ed.Lewis@neustar.biz>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2011 15:33:33 -0000

At 17:11 -0400 7/2/11, Danny McPherson wrote:

>...that you meant to reference draft-iab-dns-applications-01

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

I'm overly entertained.

From tjc@ecs.soton.ac.uk  Sun Jul  3 09:10:53 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 45AF321F857B; Sun,  3 Jul 2011 09:10:53 -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_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CYlKaDpFZRVa; Sun,  3 Jul 2011 09:10:49 -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 0F58521F8578; Sun,  3 Jul 2011 09:10:46 -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 p63GAgK9013280; Sun, 3 Jul 2011 17:10:42 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p63GAgK9013280
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1309709442; bh=qc2jzdagHeL6DKNXgINdUb7yqsE=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=FNcz3ULf18cwSNDzW4TP7Im/28zXG23ClE2DCbbcupxnA2Y05h3mGDpOtOgcfapft a9HhvDW7RxN3pUlP1tENgB4p9pHWIXNrRHEp4ysGB2szU0a/GATtwgH6kiYxH+4JUa 27j4DZrEJEdITOAIvHZ/GhEKK8/J915VEODCeWf8=
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 n62HAg0366129716Ga ret-id none; Sun, 03 Jul 2011 17:10:42 +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 p63G9KUh002645 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 3 Jul 2011 17:09:21 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <20110703111047.GB2304@Space.Net>
Date: Sun, 3 Jul 2011 17:09:20 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|9c8bf9e7fa0e59322f84c8ec6df2b8b9n62HAg03tjc|ecs.soton.ac.uk|04B2CF82-78EC-4A2B-A681-7710E3EFCDBE@ecs.soton.ac.uk>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <DE414D2B-82ED-4C32-AFDF-EDAAB6D743B2@network-heretics.com> <CAKD1Yr0=pJwOzRvTNskS7YDBNa7Fc=8srGzH2qJUKwGHdCAELg@mail.gmail.com> <A1DA82E2-B979-4719-9F78-DEB263B256A1@network-heretics.com> <20110703111047.GB2304@Space.Net> <04B2CF82-78EC-4A2B-A681-7710E3EFCDBE@ecs.soton.ac.uk>
To: IPv6 Operations <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n62HAg036612971600; tid=n62HAg0366129716Ga; 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: p63GAgK9013280
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: Sun, 03 Jul 2011 16:10:53 -0000

On 3 Jul 2011, at 12:10, Gert Doering wrote:

> On Sat, Jul 02, 2011 at 11:11:43PM -0400, Keith Moore wrote:
>> There's clearly a lack of consensus to support it.
>=20
> There's two very vocal persons opposing it and a much larger number of
> people that support it, but have not the time to write a similarily
> large amount of e-mails.  For me, this is enough for "rough =
consensus".
>=20
> (And I second everything Lorenzo, Randy and Cameron said - there's=20
> theoretical possibilities, and real world.  6to4 fails the real-world
> test.  Get over it, instead of attacking people that run real-world
> networks for the decisions they need to do to keep the networks =
running
> in a world without enough IPv4 addresses).

I'm with Gert, Lorenzo, Randy and others here.=20

It seemed that both the -advisory and -historic drafts had strong =
support in v6ops, which isn't just any WG, it's the WG that anyone with =
a vested interest in IPv6 deployment takes part.  Thus its view on IPv6 =
deployment practices should be given due regard.  The opposition on the =
IETF list seemed to be a vocal minority, and of course one person seemed =
to post a disproportionate number of replies.

The problems with 6to4 (20% minimum failure rate, and poor performance =
when it does connect) are well documented and have led to various =
'counter measures' from the IETF, including:
a) 6to4 off by default, as per 6to4-advisory
b) IPv4 being preferred to 6to4 transport, as per 3484-bis (widely =
implemented already)
c) a fast fallback mechanism from IPv6 to IPv4, as per happy eyeballs (a =
simplistic version is already in Chrome)

Those measures indicate how bad a problem 6to4 creates.  If we're going =
to the trouble of coming up with all these measures, there seems to be a =
good case for 6to4 to Historic, which would be a steer to implementors =
to no longer include 6to4 support at all.  I do agree however that the =
most important point is publishing the -advisory text.

As a provider of a (not large) enterprise, I know that a fraction of 1% =
of connections to our site suffer a 10 second+ delay to a dual-stack web =
site where they suffer no delay to an IPv4-only one.  There's no way to =
know for sure how much of that 'IPv6 brokenness' is 6to4, but measures =
(a), (b), and (c) should minimise that figure.  Having said that, less =
than 1% of users who connect to our site over IPv6 use 6to4, so we =
wouldn't be aggrieved to see it disappear in terms of loss of users, as =
those users could almost certainly still reach us over IPv4.  Our own =
users who want IPv6 connectivity when offsite use tunnel brokers, which =
provide a much better (and more predictable) service, one that also =
works from behind a NAT, which in the reality of home, hotel, and other =
hotspot networks is quite important.
=20
As for operators 'fixing' 6to4, well, I'd rather see operators invest =
that effort in deploying IPv6, rather than making 6to4 work better, for =
some value of 'better'.

Tim=

From moore@network-heretics.com  Sun Jul  3 11:13:20 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 584A821F85DF; Sun,  3 Jul 2011 11:13:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.22
X-Spam-Level: 
X-Spam-Status: No, score=-3.22 tagged_above=-999 required=5 tests=[AWL=-0.221,  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 l27amNnMF9jI; Sun,  3 Jul 2011 11:13:19 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 7828B21F85DC; Sun,  3 Jul 2011 11:13:19 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 257E52351D; Sun,  3 Jul 2011 14:13:19 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Sun, 03 Jul 2011 14:13: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=l7063sh1wj+YzNHeZo9YmMErWOc=; b=deARNsgwrtXTxxcbHIjttfkCofLKoz7bWb8Ha+dHEFCLp6BuageQ9Ns3cjdPcmug2+zH/SthfiSgDLRxBYVLHl/6AXpvtGhVeJgwf1ugNpX0tGh5dwYlVx8gTXGMU1SRAN7mus9unIyRxqax/02yNRw24mE2fKmyWHw3IqRx3tk=
X-Sasl-enc: SGgqJHhvVe+d8U6JftrBi7+qn4mklWrAZKk4TU35HdOy 1309716798
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 D79C6405054; Sun,  3 Jul 2011 14:13:17 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
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|9c8bf9e7fa0e59322f84c8ec6df2b8b9n62HAg03tjc|ecs.soton.ac.uk|04B2CF82-78EC-4A2B-A681-7710E3EFCDBE@ecs.soton.ac.uk>
Date: Sun, 3 Jul 2011 14:13:00 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C4FF7877-287B-4484-B81C-0160AC53A42F@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <DE414D2B-82ED-4C32-AFDF-EDAAB6D743B2@network-heretics.com> <CAKD1Yr0=pJwOzRvTNskS7YDBNa7Fc=8srGzH2qJUKwGHdCAELg@mail.gmail.com> <A1DA82E2-B979-4719-9F78-DEB263B256A1@network-heretics.com> <20110703111047.GB2304@Space.Net> <04B2CF82-78EC-4A2B-A681-7710E3EFCDBE@ecs.soton.ac.uk> <EMEW3|9c8bf9e7fa0e59322f84c8ec6df2b8b9n62HAg03tjc|ecs.soton.ac.uk|04B2CF82-78EC-4A2B-A681-7710E3EFCDBE@ecs.soton.ac.uk>
To: Tim Chown <tjc@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.1084)
Cc: IPv6 Operations <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: Sun, 03 Jul 2011 18:13:20 -0000

On Jul 3, 2011, at 12:09 PM, Tim Chown wrote:

> It seemed that both the -advisory and -historic drafts had strong =
support in v6ops, which isn't just any WG, it's the WG that anyone with =
a vested interest in IPv6 deployment takes part.

That's simply false.   For instance, both users and applications =
developers are drastically underrepresented in that group.  =20

The interests of operators are certainly important and should be given =
due regard, but they are not the only interests that need to be =
considered.

>  Thus its view on IPv6 deployment practices should be given due =
regard.  The opposition on the IETF list seemed to be a vocal minority, =
and of course one person seemed to post a disproportionate number of =
replies.

One person's view should only be counted as one person's view, no matter =
how many messages he sends.     And yet, when even one person speaks up =
for the interests of an under-represented group, the merit of his =
arguments should be considered.

The reason we make decisions by consensus in IETF, rather than by =
voting, is that there's no way to have a representative sample of all =
interests.

And yes, a vocal minority can be sufficient to cause IETF to fail to =
reach consensus.  That's intentional.

> The problems with 6to4 (20% minimum failure rate, and poor performance =
when it does connect) are well documented and have led to various =
'counter measures' from the IETF, including:
> a) 6to4 off by default, as per 6to4-advisory
> b) IPv4 being preferred to 6to4 transport, as per 3484-bis (widely =
implemented already)
> c) a fast fallback mechanism from IPv6 to IPv4, as per happy eyeballs =
(a simplistic version is already in Chrome)
>=20
> Those measures indicate how bad a problem 6to4 creates.

False.   The problems associated with 6to4 were not created by 6to4; =
they were created by dubious operational practices. =20

But I note that all of the counter measures you cite are widely agreed =
on and well on their way to being reality.    Making 6to4 Historic in =
addition to these will not help; it will only hurt users who are =
successfully using it now.

>  If we're going to the trouble of coming up with all these measures, =
there seems to be a good case for 6to4 to Historic, which would be a =
steer to implementors to no longer include 6to4 support at all.

In other words, it's an attempt to sabotage 6to4 for those who are =
currently successfully using it, and without giving them a viable =
replacement.  It's an attempt to shift the pain from the operators to =
the users, for problems that were mostly caused by operators.

> As for operators 'fixing' 6to4, well, I'd rather see operators invest =
that effort in deploying IPv6, rather than making 6to4 work better, for =
some value of 'better'.

6to4 might need fixing, but it's not up to operators to fix it.    I =
think it's just fine if operators do things that they should normally be =
doing, i.e.: make a best effort to deliver all traffic (including =
protocol 41);  make sure that routers work properly; make sure that =
route advertisements are accurate.

Of course, if 6to4 could be replaced with something better, that would =
be a win for everyone.  For operators, I think that means deploying some =
form of v6 concurrently with LSN.   But I don't think the net can afford =
to trust that all operators will do this.

Keith


From trejrco@gmail.com  Sun Jul  3 11:53:37 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 A506421F85CE; Sun,  3 Jul 2011 11:53:37 -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 D3DENVfjL4LF; Sun,  3 Jul 2011 11:53:37 -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 9C4EE21F85C7; Sun,  3 Jul 2011 11:53:36 -0700 (PDT)
Received: by bwb17 with SMTP id 17so4363327bwb.31 for <multiple recipients>; Sun, 03 Jul 2011 11:53:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=knM6DIyAgPsSyQEb48FI63BA51LRK00V2+/jvJAnLW4=; b=mjgoV3uxxE/PMhPjOpQs3Gebj7z/l8TNk7M5MwzQjd4K1nW4tZqf4yIjz9ivwlglrI VZ2rVV5NM5fkNUSjJ5e1IoCGJShKGp8nqhtkFtFIILCP3BgNPcHsPM2eG1ZIchZ1LF+s n2xfDdTKGr6tTs9jAOayh+dAgXETKwTr9RA7g=
Received: by 10.204.122.210 with SMTP id m18mr4792144bkr.138.1309719215178; Sun, 03 Jul 2011 11:53:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.204.81.163 with HTTP; Sun, 3 Jul 2011 11:53:15 -0700 (PDT)
In-Reply-To: <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com>
From: TJ <trejrco@gmail.com>
Date: Sun, 3 Jul 2011 14:53:15 -0400
Message-ID: <CALOgxGY0A-8u1k0vS9dTe88mNpPjpUF5AwOWV6XY9mwU_XQV1g@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
To: "v6ops@ietf.org" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=0016e6d6419d93841504a72ec40c
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: Sun, 03 Jul 2011 18:53:37 -0000

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

On Sat, Jul 2, 2011 at 15:21, Cameron Byrne <cb.list6@gmail.com> wrote:

>
> On Jul 2, 2011 11:55 AM, "Lorenzo Colitti" <lorenzo@google.com> wrote:
> >
> > Great, back to square one.
> >
> > Is the reasoning behind the decision explained somewhere? My reading of
> the threads on the subject in v6ops was that the opposition to 6to4-historic
> was a small but vocal minority, and I thought that qualified as rough
> consensus. But perhaps I missed some discussion.
> >
>
> I saw the same thing. It is a shame that work that directly removes
> barriers to REAL ipv6 deployment gets shouted down by a few people not
> involved in REAL ipv6 deployment.
>
> As a member of that "small but vocal minority" I think you are being a
little unfair here; some of us are working quite hard in getting IPv6
deployed in a number of different places.

> Also, why do the author and the chairs think that the new draft will do
> any better than 6to4-historic? I would assume that the same people who spoke
> up against 6to4-historic will speak up against the new document, and since
> that level of opposition was sufficient to prevent the publication
> of 6to4-historic, it may be sufficient to prevent publication of the new
> document as well. If so, we will have spent 3-6 months arguing about it for
> naught.
>

And, FWIW, I have no objections to having it off by default.  In fact, I
welcome that.


/TJ

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

<div class=3D"gmail_quote">On Sat, Jul 2, 2011 at 15:21, Cameron Byrne <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:cb.list6@gmail.com">cb.list6@gmail.com<=
/a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<p><br>
On Jul 2, 2011 11:55 AM, &quot;Lorenzo Colitti&quot; &lt;<a href=3D"mailto:=
lorenzo@google.com" target=3D"_blank">lorenzo@google.com</a>&gt; wrote:</p>=
<div class=3D"im">&gt;<br></div>
&gt; Great, back to square one.<br>
&gt;<br>
&gt; Is the reasoning behind the decision explained somewhere?=A0My reading=
 of the threads on the subject in v6ops was that the opposition to 6to4-his=
toric was a small but vocal minority, and I thought that qualified as rough=
 consensus. But perhaps I missed some discussion.<br>



&gt;<p></p>
<p>I saw the same thing. It is a shame that work that directly removes barr=
iers to REAL ipv6 deployment gets shouted down by a few people not involved=
 in REAL ipv6 deployment. </p>
<p></p></blockquote><div>As a member of that &quot;small but vocal minority=
&quot; I think you are being a little unfair here; some of us are working q=
uite hard in getting IPv6 deployed in a number of different places.</div>

<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex;"><p>&gt; Also, why do the aut=
hor and the chairs think that the new draft will do any better than 6to4-hi=
storic? I would assume that the same people who spoke up against 6to4-histo=
ric will speak up against the new document, and since that level of opposit=
ion was sufficient to prevent the publication of=A06to4-historic, it may be=
 sufficient to prevent publication of the new document as well.=A0If so, we=
 will have spent 3-6 months arguing about it for naught.<br>

</p></blockquote><div><br></div><div>And, FWIW, I have no objections to hav=
ing it off by default. =A0In fact, I welcome that.</div><div><br></div><div=
><br></div><div>/TJ</div></div>

--0016e6d6419d93841504a72ec40c--

From moore@network-heretics.com  Sun Jul  3 12:31:05 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 5F4E521F8648; Sun,  3 Jul 2011 12:31:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.515
X-Spam-Level: 
X-Spam-Status: No, score=-3.515 tagged_above=-999 required=5 tests=[AWL=0.083,  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 L9knbBipP9hR; Sun,  3 Jul 2011 12:31:04 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 84A4C21F8647; Sun,  3 Jul 2011 12:31:04 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 1D3BF25E06; Sun,  3 Jul 2011 15:31:04 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Sun, 03 Jul 2011 15:31:04 -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=3YxmxhrQRiZRs8lT0xDfrR0bVOA=; b=EocOpyoQomoXwqiLeOdUX/h+RATmx5CBaxbdSeXrXNiWbPt539WeEgsfISNhelCHDkJxjkpliBVkCIpgEfaqtJV+EuUvbHI+iMz+yVVPK8qDUpYKE5XSqsEY+tRTuJ6KND7xXtqfZUTI4Oo/4w1calpAGNAB58aaE5Dc8TotZ/U=
X-Sasl-enc: r/eqzW5NahkugxwfVFLXDqprNdVO0Jca1NUlhywd3t4K 1309721463
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 A3E36403FC3; Sun,  3 Jul 2011 15:31:02 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-2-701763140
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <DFD19CC6-219F-4449-B0F4-8125193B6FF6@gmail.com>
Date: Sun, 3 Jul 2011 15:30:44 -0400
Message-Id: <D30FDDB9-A19A-46C3-9E06-68070300F32A@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com> <20110703112048.4a3c7111@opy.nosense.org> <4E0FD788.3000305@dougbarton.us> <20110703131913.28142ec0@opy.nosense.org> <CAKD1Yr0dU8xGPc5tY8qK7w7Vc57zzj2BBipCb3b3VsXLov-JUw@mail.gmail.com> <m1QdKfr-0001jNC@stereo.hq.phicoh.net> <E3CF6B2C-B177-4A6A-898C-4EA8C8CA65D5@network-heretics.com> <CAD6AjGSUEmdKk3trTdRXMyrnp8FFyvHUWBSgeBrHT_2jPjXUBA@mail.gmail.com> <100DA5A2-0276-45B8-A8CD-AB7B0D947AC4@network-heretics.com> <CB106539-9C0F-489C-BBC0-E4ADAF3B8F45@gmail.com> <746A967B-16AF-4428-8424-298AF8001F87@network-heretics.com> <DFD19CC6-219F-4449-B0F4-8125193B6FF6@gmail.com>
To: Arturo Servin <arturo.servin@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: IPv6 Operations <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: Sun, 03 Jul 2011 19:31:05 -0000

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

On Jul 3, 2011, at 3:17 PM, Arturo Servin wrote:
>>>=20
>>> 	And b.
>>>=20
>>> 	And probably it is too much effort for something that will go =
away (probably sooner that we expect) with the exhaustion of IPv4 =
addresses for each ISP's customer (6to4 does not work with NATs, and =
they are here).
>>=20
>> It's clearly inappropriate for operators to be filtering protocol 41. =
  Not only does this break 6to4, it also breaks other tunneling =
mechanisms.  More generally, it's inappropriate for operators to be =
favoring one kind of traffic over another.
>=20
> 	Many corporate networks filter them because security concerns (I =
am not saying that is right or wrong, it just happens and it breaks =
6to4). They won't change their mind because 6to4.

Fair enough.  (It bothers me when ISPs filter them, but I consider it =
within the rights of an enterprise network to do that.  What an =
enterprise does with its own traffic should be its own business, and =
they can benefit and/or suffer from the consequences of their choices.  =
Though I do think that there are probably better ways to handle the =
(legitimate) security concerns than to merely filter protocol 41.  e.g. =
ICMP unreachable.)

And of course protocol 41 becomes problematic for those behind a NAT of =
any kind, including LSN.    (I do see LSN as "best effort" delivery; =
it's just that the state of the the network has made "best" pretty sad =
these days.)

So if we were able to omit or finesse considerations (b) and (c) could =
we get consensus around the remaining items in that list?

>> The ISPs I've talked to tell me that they see no reason why static, =
public IPv4 addresses cannot continue to be given to those that request =
them, indefinitely, as long as they're paying for business service.=20
>=20
> 	Call one not in the USA. China or India perhaps.

I'll take your word for it.   6to4 is only going to work in corner =
cases, and those corners are somewhat defined by geography.

Honestly I'd be happy to declare 6to4 Historic if we had a suitable =
replacement - one that could be automatically configured by hosts, used =
by applications, and worked better than 6to4 in most cases.  I don't =
think it exists yet. =20

(That oft-touted 80% reliability figure needs to be compared with =
similar figures for other methods, along with the realization that =
manual configuration, lack of platform support,  congestion at =
heavily-used tunnel endpoints, are all significant sources of failure.  =
Note that you can't measure this by looking only at traffic in the =
network.   And for those who insist that all v6 traffic should be =
native, note that from the perspective of an application developer, =
there is close to a 0% reliability for this at present.  80% is a huge =
improvement over that, though still not good enough.)

Keith


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

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jul 3, 2011, at 3:17 PM, Arturo Servin =
wrote:</div><blockquote type=3D"cite"><div><blockquote =
type=3D"cite"><blockquote type=3D"cite"><font class=3D"Apple-style-span" =
color=3D"#000000"><br></font></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>And =
b.<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>And probably it is too much =
effort for something that will go away (probably sooner that we expect) =
with the exhaustion of IPv4 addresses for each ISP's customer (6to4 does =
not work with NATs, and they are =
here).<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">It's clearly =
inappropriate for operators to be filtering protocol 41. &nbsp;&nbsp;Not =
only does this break 6to4, it also breaks other tunneling mechanisms. =
&nbsp;More generally, it's inappropriate for operators to be favoring =
one kind of traffic over another.<br></blockquote><br><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>Many =
corporate networks filter them because security concerns (I am not =
saying that is right or wrong, it just happens and it breaks 6to4). They =
won't change their mind because =
6to4.<br></div></blockquote><div><br></div>Fair enough. &nbsp;(It =
bothers me when ISPs filter them, but I consider it within the rights of =
an enterprise network to do that. &nbsp;What an enterprise does with its =
own traffic should be its own business, and they can benefit and/or =
suffer from the consequences of their choices. &nbsp;Though I do think =
that there are probably better ways to handle the (legitimate) security =
concerns than to merely filter protocol 41. &nbsp;e.g. ICMP =
unreachable.)</div><div><br></div><div>And of course protocol 41 becomes =
problematic for those behind a NAT of any kind, including LSN. &nbsp; =
&nbsp;(I do see LSN as "best effort" delivery; it's just that the state =
of the the network has made "best" pretty sad these =
days.)</div><div><br></div><div>So if we were able to omit or finesse =
considerations (b) and (c) could we get consensus around the remaining =
items in that list?</div><div><br><blockquote =
type=3D"cite"><div><blockquote type=3D"cite">The ISPs I've talked to =
tell me that they see no reason why static, public IPv4 addresses cannot =
continue to be given to those that request them, indefinitely, as long =
as they're paying for business service. <br></blockquote><br><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>Call one =
not in the USA. China or India =
perhaps.<br></div></blockquote></div><br><div>I'll take your word for =
it. &nbsp; 6to4 is only going to work in corner cases, and those corners =
are somewhat defined by geography.</div><div><br></div><div>Honestly I'd =
be happy to declare 6to4 Historic if we had a suitable replacement - one =
that could be automatically configured by hosts, used by applications, =
and worked better than 6to4 in most cases. &nbsp;I don't think it exists =
yet. &nbsp;</div><div><br></div><div>(That oft-touted 80% reliability =
figure needs to be compared with similar figures for other methods, =
along with the realization that manual configuration, lack of platform =
support, &nbsp;congestion at heavily-used tunnel endpoints, are all =
significant sources of failure. &nbsp;Note that you can't measure this =
by looking only at traffic in the network. &nbsp; And for those who =
insist that all v6 traffic should be native, note that from the =
perspective of an application developer, there is close to a 0% =
reliability for this at present. &nbsp;80% is a huge improvement over =
that, though still not good =
enough.)</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-2-701763140--

From rogerj@gmail.com  Sun Jul  3 12:32:47 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 D337811E807B; Sun,  3 Jul 2011 12:32:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=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 hvJFgx9bu9Zd; Sun,  3 Jul 2011 12:32:47 -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 B62E121F8670; Sun,  3 Jul 2011 12:32:46 -0700 (PDT)
Received: by wwe5 with SMTP id 5so3041147wwe.13 for <multiple recipients>; Sun, 03 Jul 2011 12:32:45 -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=JpUYA+FMIu+rQxXeaeNvOCEUe7ZkDm+w1R2ALdpnCs4=; b=wWLi44MfXEYBgHRWT5MnTs9U4oqYfk7d0Ot1pkk9wwmMMc4zk2j4MYlxSu/+DFkk79 0skOrNB8jGztn2gI8XXu+5eoxMyjmsLUmb8ZwAgP3jx40deQvoA0t2TRWEtlrVorp5no s22O9gBfapjGQ+KrlY8Yk+hg/JWle+H9Ab4q0=
MIME-Version: 1.0
Received: by 10.227.162.200 with SMTP id w8mr4645594wbx.114.1309721565835; Sun, 03 Jul 2011 12:32:45 -0700 (PDT)
Received: by 10.227.142.137 with HTTP; Sun, 3 Jul 2011 12:32:45 -0700 (PDT)
Received: by 10.227.142.137 with HTTP; Sun, 3 Jul 2011 12:32:45 -0700 (PDT)
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net>
References: <Acw41iMv6/qWspvgTzCQB463JqIp+A==> <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net>
Date: Sun, 3 Jul 2011 21:32:45 +0200
Message-ID: <CAKFn1SGvL2KQ3KVoR6cE8Q=Mqb+zjXL_uVAhdic_nOHC=f_q1A@mail.gmail.com>
Subject: Re:draft-ietf-v6ops-6to4-to-historic
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Ronald Bonica <rbonica@juniper.net>
Content-Type: multipart/alternative; boundary=20cf30025e36afb2e804a72f509b
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 19:32:47 -0000

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

A bit late since this threat will be moderated soon. But I strongly object
to this delay of needed action.

I guess the other way the problem, which will hurt muchmuch more is maybe to
considering a filter of 6to4 on isp level?
I will suggest it when we start deploying native ipv6.

--- Roger J. ---
 On Jul 2, 2011 6:39 PM, "Ronald Bonica" <rbonica@juniper.net> wrote:
> Folks,
>
> Whereas there has been considerable controversy regarding
draft-ietf-v6ops-6to4-to-historic, the v6ops chairs and document author have
agreed to the following course of action:
>
> - the V6OPS WG will withdraw its request to publish
draft-ietf-v6ops-6to4-to-historic
> - The author will introduce a new draft, intended for standards track
publication. The new draft will update RFCs 3056 and 3068. It will say that
if 6-to-4 is implemented, it must be turned off by default.
> - In order for the new draft to be published, it must achieve both V6OPS
WG and IETF consensus
>
> If anyone objects to this course of action, please speak up soon.
>
> Ron
> <Speaking as OPS Area AD>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

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

<p>A bit late since this threat will be moderated soon. But I strongly obje=
ct to this delay of needed action. </p>
<p>I guess the other way the problem, which will hurt muchmuch more is mayb=
e to considering a filter of 6to4 on isp level? <br>
I will suggest it when we start deploying native ipv6.<br></p>
<p>--- Roger J. ---<br>
</p>
<div class=3D"gmail_quote">On Jul 2, 2011 6:39 PM, &quot;Ronald Bonica&quot=
; &lt;<a href=3D"mailto:rbonica@juniper.net">rbonica@juniper.net</a>&gt; wr=
ote:<br type=3D"attribution">&gt; Folks,<br>&gt; <br>&gt; Whereas there has=
 been considerable controversy regarding draft-ietf-v6ops-6to4-to-historic,=
 the v6ops chairs and document author have agreed to the following course o=
f action:<br>
&gt; <br>&gt; - the V6OPS WG will withdraw its request to publish draft-iet=
f-v6ops-6to4-to-historic<br>&gt; - The author will introduce a new draft, i=
ntended for standards track publication. The new draft will update RFCs 305=
6 and 3068. It will say that if 6-to-4 is implemented, it must be turned of=
f by default. <br>
&gt; - In order for the new draft to be published, it must achieve both V6O=
PS WG and IETF consensus<br>&gt; <br>&gt; If anyone objects to this course =
of action, please speak up soon.<br>&gt; <br>&gt;                          =
                           Ron<br>
&gt;                                                     &lt;Speaking as OP=
S Area AD&gt;<br>&gt; _______________________________________________<br>&g=
t; 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></div>

--20cf30025e36afb2e804a72f509b--

From rbonica@juniper.net  Sun Jul  3 13:58:07 2011
Return-Path: <rbonica@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B87311E8089; Sun,  3 Jul 2011 13:58:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.252
X-Spam-Level: 
X-Spam-Status: No, score=-106.252 tagged_above=-999 required=5 tests=[AWL=-0.253, 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 5VTdspjpMx+O; Sun,  3 Jul 2011 13:58:06 -0700 (PDT)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by ietfa.amsl.com (Postfix) with ESMTP id 608FB11E807D; Sun,  3 Jul 2011 13:58:06 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKThDX3S6ONtWkIqSQYJyJuphtGm8abK40@postini.com; Sun, 03 Jul 2011 13:58:06 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; Sun, 3 Jul 2011 13:57:23 -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; Sun, 3 Jul 2011 16:57:22 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "v6ops@ietf.org" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
Date: Sun, 3 Jul 2011 16:57:21 -0400
Subject: RE: draft-ietf-v6ops-6to4-to-historic
Thread-Topic: draft-ietf-v6ops-6to4-to-historic
Thread-Index: Acw41iMv6/qWspvgTzCQB463JqIp+AA69FxA
Message-ID: <13205C286662DE4387D9AF3AC30EF456D3F3507F3A@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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Jul 2011 20:58:07 -0000

Folks,

I think that I get it. There is no IETF consensus regarding the compromise =
proposed below. So, at very least, we will have to abandon the compromise.

Right now, the only alternative that I see is to reintroduce draft-ietf-v6o=
ps-6to4-to-historic and let the appeal process run its course. I hate to do=
 this, because the appeals process can be an incredible time sync and distr=
action. If anybody sees another alternative, please propose it.

                                                              Ron
                                                              <speaking as =
AD>

P.S. This thread has generated over 100 messages in the last 28 hours. Let'=
s all take two days to cool off and spend some time with our families.

-----Original Message-----
From: Ronald Bonica=20
Sent: Saturday, July 02, 2011 12:36 PM
To: v6ops@ietf.org; IETF Discussion
Subject: draft-ietf-v6ops-6to4-to-historic

Folks,

Whereas there has been considerable controversy regarding draft-ietf-v6ops-=
6to4-to-historic, the v6ops chairs and document author have agreed to the f=
ollowing course of action:

- the V6OPS WG will withdraw its request to publish draft-ietf-v6ops-6to4-t=
o-historic
- The author will introduce a new draft, intended for standards track publi=
cation. The new draft will update RFCs 3056 and 3068. It will say that if 6=
-to-4 is implemented, it must be turned off by default.=20
- In order for the new draft to be published, it must achieve both V6OPS WG=
 and IETF consensus

If anyone objects to this course of action, please speak up soon.

                                                    Ron
                                                    <Speaking as OPS Area A=
D>

From jnc@mercury.lcs.mit.edu  Sun Jul  3 14:29:06 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 A836E21F85CD; Sun,  3 Jul 2011 14:29:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.722
X-Spam-Level: 
X-Spam-Status: No, score=-5.722 tagged_above=-999 required=5 tests=[AWL=-0.877, BAYES_00=-2.599, FRT_FOLLOW1=1.332, FRT_FOLLOW2=0.422, 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 HHxpeS6DEozG; Sun,  3 Jul 2011 14:29:06 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 305BC21F85CC; Sun,  3 Jul 2011 14:29:05 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 34DB218C1C2; Sun,  3 Jul 2011 17:29:05 -0400 (EDT)
To: ietf@ietf.org, v6ops@ietf.org
Subject: RE: draft-ietf-v6ops-6to4-to-historic
Message-Id: <20110703212905.34DB218C1C2@mercury.lcs.mit.edu>
Date: Sun,  3 Jul 2011 17:29: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: Sun, 03 Jul 2011 21:29:06 -0000

    > From: Ronald Bonica <rbonica@juniper.net>

    > I think that I get it. There is no IETF consensus regarding the
    > compromise proposed below. ...
    > Right now, the only alternative that I see is to reintroduce
    > draft-ietf-v6ops-6to4-to-historic 

But there is no rough consensus to do that either.

There is simply no IETF-wide agreement on _any_ action with regard to killing
off 6to4.

So the only possible response is the IETF's normal response when there is no
rough consensus on what to do, which is to defer any action.

At least, as has been pointed out, we have draft-ietf-v6ops-6to4-advisory,
which has already been OKs, and which, _if folllowed_, would alleviate most
of the problems.

	Noel


From rbonica@juniper.net  Sun Jul  3 16:49:12 2011
Return-Path: <rbonica@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44BC11F0C3F; Sun,  3 Jul 2011 16:49:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.525
X-Spam-Level: 
X-Spam-Status: No, score=-106.525 tagged_above=-999 required=5 tests=[AWL=0.074, 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 x10toxGDkIJS; Sun,  3 Jul 2011 16:49:11 -0700 (PDT)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by ietfa.amsl.com (Postfix) with ESMTP id CEE871F0C3C; Sun,  3 Jul 2011 16:49:09 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKThD/9eFoLc0qkBSgfnxsDCSg6aKcKNiK@postini.com; Sun, 03 Jul 2011 16:49:11 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; Sun, 3 Jul 2011 16:49:06 -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; Sun, 3 Jul 2011 19:49:06 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, "ietf@ietf.org" <ietf@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Date: Sun, 3 Jul 2011 19:49:04 -0400
Subject: RE: draft-ietf-v6ops-6to4-to-historic
Thread-Topic: draft-ietf-v6ops-6to4-to-historic
Thread-Index: Acw5yD3/2VY+9nwqQ2OF+Gari0e9dwAEsFhA
Message-ID: <13205C286662DE4387D9AF3AC30EF456D3F3507F50@EMBX01-WF.jnpr.net>
References: <20110703212905.34DB218C1C2@mercury.lcs.mit.edu>
In-Reply-To: <20110703212905.34DB218C1C2@mercury.lcs.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: Sun, 03 Jul 2011 23:49:12 -0000

Comments inline........

-----Original Message-----
From: Noel Chiappa [mailto:jnc@mercury.lcs.mit.edu]=20
Sent: Sunday, July 03, 2011 5:29 PM
To: ietf@ietf.org; v6ops@ietf.org
Cc: jnc@mercury.lcs.mit.edu
Subject: RE: draft-ietf-v6ops-6to4-to-historic

    > From: Ronald Bonica <rbonica@juniper.net>

    > I think that I get it. There is no IETF consensus regarding the
    > compromise proposed below. ...
    > Right now, the only alternative that I see is to reintroduce
    > draft-ietf-v6ops-6to4-to-historic=20

But there is no rough consensus to do that either.

RB> That is the claim of an appeal on the table. Let's run the appeal proce=
ss
RB> and figure out whether that claim is valid. We certainly aren't having =
any
RB> success reaching a decision on the mailing list.
RB>
RB>                                      Ron


From marka@isc.org  Sun Jul  3 17:55:04 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 5759521F85CC; Sun,  3 Jul 2011 17:55:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.356
X-Spam-Level: 
X-Spam-Status: No, score=-2.356 tagged_above=-999 required=5 tests=[AWL=-0.357, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6S1iJ8oP9Z+t; Sun,  3 Jul 2011 17:55:03 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id E289F21F85CA; Sun,  3 Jul 2011 17:55:02 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 7830E5F98EF; Mon,  4 Jul 2011 00:54:45 +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 25822216C7B; Mon,  4 Jul 2011 00:54:43 +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 D2531116B88C; Mon,  4 Jul 2011 10:54:38 +1000 (EST)
To: Tim Chown <tjc@ecs.soton.ac.uk>
From: Mark Andrews <marka@isc.org>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <DE414D2B-82ED-4C32-AFDF-EDAAB6D743B2@network-heretics.com> <CAKD1Yr0=pJwOzRvTNskS7YDBNa7Fc=8srGzH2qJUKwGHdCAELg@mail.gmail.com> <A1DA82E2-B979-4719-9F78-DEB263B256A1@network-heretics.com> <20110703111047.GB2304@Space.Net> <04B2CF82-78EC-4A2B-A681-7710E3EFCDBE@ecs.soton.ac.uk> <EMEW3|9c8bf9e7fa0e59322f84c8ec6df2b8b9n62HAg03tjc|ecs.soton.ac.uk|04B2CF82-78EC-4A2B-A681-7710E3EFCDBE@ecs.soton.ac.uk>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
In-reply-to: Your message of "Sun, 03 Jul 2011 17:09:20 +0100." <EMEW3|9c8bf9e7fa0e59322f84c8ec6df2b8b9n62HAg03tjc|ecs.soton.ac.uk|04B2CF82-78EC-4A2B-A681-7710E3EFCDBE@ecs.soton.ac.uk>
Date: Mon, 04 Jul 2011 10:54:38 +1000
Message-Id: <20110704005438.D2531116B88C@drugs.dv.isc.org>
Cc: IPv6 Operations <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: Mon, 04 Jul 2011 00:55:04 -0000

In message <EMEW3|9c8bf9e7fa0e59322f84c8ec6df2b8b9n62HAg03tjc|ecs.soton.ac.uk|0
4B2CF82-78EC-4A2B-A681-7710E3EFCDBE@ecs.soton.ac.uk>, Tim Chown writes:
> 
> On 3 Jul 2011, at 12:10, Gert Doering wrote:
> 
> > On Sat, Jul 02, 2011 at 11:11:43PM -0400, Keith Moore wrote:
> >> There's clearly a lack of consensus to support it.
> > 
> > There's two very vocal persons opposing it and a much larger number of
> > people that support it, but have not the time to write a similarily
> > large amount of e-mails.  For me, this is enough for "rough consensus".
> > 
> > (And I second everything Lorenzo, Randy and Cameron said - there's 
> > theoretical possibilities, and real world.  6to4 fails the real-world
> > test.  Get over it, instead of attacking people that run real-world
> > networks for the decisions they need to do to keep the networks running
> > in a world without enough IPv4 addresses).
> 
> I'm with Gert, Lorenzo, Randy and others here. 
> 
> It seemed that both the -advisory and -historic drafts had strong support in 
> v6ops, which isn't just any WG, it's the WG that anyone with a vested interes
> t in IPv6 deployment takes part.  Thus its view on IPv6 deployment practices 
> should be given due regard.  The opposition on the IETF list seemed to be a v
> ocal minority, and of course one person seemed to post a disproportionate num
> ber of replies.
> 
> The problems with 6to4 (20% minimum failure rate, and poor performance when i
> t does connect) are well documented and have led to various 'counter measures
> ' from the IETF, including:
> a) 6to4 off by default, as per 6to4-advisory
> b) IPv4 being preferred to 6to4 transport, as per 3484-bis (widely implemente
> d already)
> c) a fast fallback mechanism from IPv6 to IPv4, as per happy eyeballs (a simp
> listic version is already in Chrome)
>
> Those measures indicate how bad a problem 6to4 creates.

No.  The 20% connect failure rate shows how bad AUTOMATIC 6to4 is.
It show NOTHING about how bad 6to4 itself is.  As for longer RTT
that is something people accept as part of using 6to4.  I know I
accept that they are there for the trans Pacific tunnel I use.

As for high failure rates.  EDNS (RFC 2671) had/has a similar or
higher failure rates with any UDP packets that are bigger that 512
bytes or UDP packets that get fragmented or packets that have a OPT
record in the additional section or have DO (RFC 3225) set in the
OPT record.  Firewalls are a pain in the proverbial but we don't
stop attempting to use EDNS because they are there.  Nameservers
tailor their queries to to work around firewalls (happy eyeballs)
and log that they needed to use the workarounds.

>  If we're going to th
> e trouble of coming up with all these measures, there seems to be a good case
>  for 6to4 to Historic, which would be a steer to implementors to no longer in
> clude 6to4 support at all.  I do agree however that the most important point 
> is publishing the -advisory text.

As for the counter measures, some of them need to be there independently
of 6to4.  Google Chome was the only brower that could reach
www.ietf.org in a timely manner from any dual stack client connecting
via Hurricane Electric for half of last week.  The noc @HE responded
to the issue within 1/2 a hour of it being raised via email by
raising a trouble ticket with AT&T.  It still took 2-3 days for the
problem to be fixed.

> As a provider of a (not large) enterprise, I know that a fraction of 1% of co
> nnections to our site suffer a 10 second+ delay to a dual-stack web site wher
> e they suffer no delay to an IPv4-only one.

Which for the most part wouldn't be there if 6to4 required explicit
configuration.

> There's no way to know for sure 
> how much of that 'IPv6 brokenness' is 6to4, but measures (a), (b), and (c) sh
> ould minimise that figure.  Having said that, less than 1% of users who conne
> ct to our site over IPv6 use 6to4, so we wouldn't be aggrieved to see it disa
> ppear in terms of loss of users, as those users could almost certainly still 
> reach us over IPv4.  Our own users who want IPv6 connectivity when offsite us
> e tunnel brokers, which provide a much better (and more predictable) service,
>  one that also works from behind a NAT, which in the reality of home, hotel, 
> and other hotspot networks is quite important.
>
> As for operators 'fixing' 6to4, well, I'd rather see operators invest that ef
> fort in deploying IPv6, rather than making 6to4 work better, for some value o
> f 'better'.

The fixes for 6to4 are deploying suitable sized 6to4 relay boxes
and removing protocol 41 filters once the isp has some IPv6
connectivity.  The time and effort required to do this is minimal
compared to the time and effort required to deploy IPv6 to all of
its customers.

Remember you don't need to bill for this as the billing is already
taken care of with IPv4.  You don't need to do address assignments
as they are taken care of with IPv4.

> Tim
> _______________________________________________
> 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  Sun Jul  3 18:44:26 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 077B221F854A for <ietf@ietfa.amsl.com>; Sun,  3 Jul 2011 18:44:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.171
X-Spam-Level: 
X-Spam-Status: No, score=-10.171 tagged_above=-999 required=5 tests=[AWL=0.078, 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 XPf29JuhItdb for <ietf@ietfa.amsl.com>; Sun,  3 Jul 2011 18:44:25 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id DD43821F8525 for <ietf@ietf.org>; Sun,  3 Jul 2011 18:44:24 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p641iMMV000113 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 4 Jul 2011 03:44:22 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201107040144.p641iLN3007722@fs4113.wdf.sap.corp>
Subject: Re: HOMENET working group proposal
To: moore@network-heretics.com (Keith Moore)
Date: Mon, 4 Jul 2011 03:44:21 +0200 (MEST)
In-Reply-To: <1B0E6A5D-0BF1-400B-A063-D59D8ED2C766@network-heretics.com> from "Keith Moore" at Jul 2, 11 10:52:08 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: Mon, 04 Jul 2011 01:44:26 -0000

Keith Moore wrote:
> 
> Some applications and hosts require stable addresses; others do not.

Very few, and they should be carefully selected and such apps definitely
should obtained informed consent of the user before they use a
static/fixed address.


>
> So it might be that a home network needs to be able to support two
> prefixes - a stable one that can be used by those applications that
> need it, and an ephemeral one that can be used by everything else.
> That's not difficult to do by itself, but my next question is how
> to arrange these things such that ordinary consumers can understand
> such details and manage them?

Two addresses might work.  The ephemeral address needs to be short-lived
regularly randomly reassigned from a pool and shared by as many
ISP customers as possible.

ALL of the outgoing connections should use the ephememeral address.

And I believe even incoming connections should use the ephemeral
one, obtained by something like IGDP-via-UPnP or NAT-PMP.  Using the
static address should require significantly more work than the ephemeral
one, or we'll see too many apps that will take the easy route.

I know that there are a few hundred million folks that strip naked
at varying levels on social networks.  But we should not make it
difficult to folks that care about privacy to _not_ get laid by
careless (or on-purpose) apps.  Apps similar to customer affiliation
programs from supermarkets, where lots of folks loose their privacy
for a few pennies.

legislators can regulate browser cookies, but there is little legislators
could do to protect citizens that use static IPv6 addresses.


>
> I also strongly disagree with the assertion that EU law requires IETF
> to make it so.

I never said that.  I said that by issuing static/fixed IPv6 addresses
to home DSL subscribers (or personal mobile devices) that you're
subverting legal initiatives to protect privace, such as the
E-Privacy directive that exists in the EU, and the "do not track"
in discussion in the US.  For someone with a static IPv6 address,
you do not need any cookies at all.  The IP address itself becomes
personally identfiable (PII) information.

Collecting PII is regulated in the EU, and allowed only under very
specific conditions.  With IPv6 static addresses issued to personal
devices and private households, logging client IP-Addresses will
become, without any doubt, subject to Data Privacy legislation, and
that means in many cases illegal.

This isn't actually new, and it has already been decided to apply to
current IPv4 addresses as well by a german court in 2007
http://www.daten-speicherung.de/data/Urteil_IP-Speicherung_2007-03-27.pdf


> 
> I don't want to cripple all home networks and applications by imposing
> ephemeral addresses and/or NATs on them.

You're not crippling anything here and you are significantly exaggerating
the burden.  Just asking for some extra effort to protect privacy.
Think about it, most addresses for personal mobile devices and for home
subscribers are currently using NAT-ed dynamic IPv4 addresses already,
so it works fine, its being done, and internet is still usable.


>
> But having a stable address prefix associated with every device in
> one's home network that communicates with the public Internet can
> indeed threaten the user's privacy.

Public information to map a static IP-address to a name accumulates
in a matter of a several days to a few weeks, at most.  With static
addresses, you will not have "false positive", so one single
datum that correlates a name with that address, and privacy is gone.

It's like a photo with your name being exposed to internet search engines
just once, you can hardly undo that (maybe do damage control by having
your real name changed, but that nothing you want everyone having to
do every few months, would you?


>
> (Note that privacy addresses don't really solve the problem as
> they still all have the same prefix.)

Full anonymity is not possible at all.  What we need and can achieve
is what is currently done: share the addresses among a huge number
of subscribers and randomly reassign new addresses from the pool.


> 
> Anyway, to me it seems reasonable for the HOMENET group to
> consider privacy issues associated with address assignment.

Definitely.

-Martin

From moore@network-heretics.com  Sun Jul  3 19:07: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 2E54A21F8553 for <ietf@ietfa.amsl.com>; Sun,  3 Jul 2011 19:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.517
X-Spam-Level: 
X-Spam-Status: No, score=-3.517 tagged_above=-999 required=5 tests=[AWL=0.082,  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-UeoD-3jVJd for <ietf@ietfa.amsl.com>; Sun,  3 Jul 2011 19:07: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 A5D0D21F8534 for <ietf@ietf.org>; Sun,  3 Jul 2011 19:07:56 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 1492821124; Sun,  3 Jul 2011 22:07:56 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Sun, 03 Jul 2011 22:07: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:content-transfer-encoding:message-id:references:to; s=smtpout; bh=9UVip4ruAae90FUnAGhw/XoRop0=; b=uBtIVKEsBLhfLTGfQ7M3I//+B11YNtVthED14R8xqld8Hk2Dv/fs8jfZeqrTxGI1vvRqGHvbFtMM+vGhLRhfechfUqgoauX+zT7z4GSt05r0OxEE11pIQOiPLL5LmeCkv4ZtiPK8B09EvgfJo7+IE8RDOrV9DAXkv2bwoHQKfjE=
X-Sasl-enc: orfWXhy/P0XWPX7wPOWy2+W2hXeR+ctGLESdzAdd4I5V 1309745275
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 22D1E400E2A; Sun,  3 Jul 2011 22:07:55 -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: <201107040144.p641iLN3007722@fs4113.wdf.sap.corp>
Date: Sun, 3 Jul 2011 22:07:37 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9CDA1B45-2077-46D9-8507-FDE618472DE4@network-heretics.com>
References: <201107040144.p641iLN3007722@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: Mon, 04 Jul 2011 02:07:58 -0000

I'm not going to keep debating this on the ietf list.  I think I said =
already that this would be a good discussion topic for the WG.

On Jul 3, 2011, at 9:44 PM, Martin Rex wrote:

> Keith Moore wrote:
>>=20
>> Some applications and hosts require stable addresses; others do not.
>=20
> Very few, and they should be carefully selected and such apps =
definitely
> should obtained informed consent of the user before they use a
> static/fixed address.

...

etc.


From moore@network-heretics.com  Sun Jul  3 19:36:53 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 966B89E8005; Sun,  3 Jul 2011 19:36:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.519
X-Spam-Level: 
X-Spam-Status: No, score=-3.519 tagged_above=-999 required=5 tests=[AWL=0.080,  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 XOpiePPrjxdJ; Sun,  3 Jul 2011 19:36:53 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id EB8031F0C39; Sun,  3 Jul 2011 19:36:52 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id B1BB82122B; Sun,  3 Jul 2011 22:36:50 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Sun, 03 Jul 2011 22:36:50 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=BbYL0HomHjjNRzJd8LZ1Xnaa1hw=; b=UfzH4cWgMSo+NRDHvvoSB5JyGWTG3Vpc/xaIjdwZ8sWTSjPI347dAkwl9MK0atO8/aDrycjiwj0P9E6IQQG6D8fmSDCDkKdmRRZuHYR1aPbsafwX2Hxy8HZg+LK2++2cVKbwRYQb+TnOot0Wf+4dQVvt/Ds9PJ2SkdVQUepBCl0=
X-Sasl-enc: MPkGfPJXw1M79Q6Rvrqdbv+KvZUFFtI9dHeYfeMnW5Uo 1309747010
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 BABE8400E38; Sun,  3 Jul 2011 22:36:49 -0400 (EDT)
Subject: 6to4 to Experimental? (was: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic)
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: <13205C286662DE4387D9AF3AC30EF456D3F3507F3A@EMBX01-WF.jnpr.net>
Date: Sun, 3 Jul 2011 22:36:31 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4E80A8E8-7B29-426B-BB43-8FC269330E4B@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507F3A@EMBX01-WF.jnpr.net>
To: Ronald Bonica <rbonica@juniper.net>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org" <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: Mon, 04 Jul 2011 02:36:53 -0000

On Jul 3, 2011, at 4:57 PM, Ronald Bonica wrote:

> Folks,
>=20
> I think that I get it. There is no IETF consensus regarding the =
compromise proposed below. So, at very least, we will have to abandon =
the compromise.
>=20
> Right now, the only alternative that I see is to reintroduce =
draft-ietf-v6ops-6to4-to-historic and let the appeal process run its =
course. I hate to do this, because the appeals process can be an =
incredible time sync and distraction. If anybody sees another =
alternative, please propose it.
>=20
>                                                              Ron
>                                                             <speaking =
as AD>

The alternative that I proposed to IESG and to the chairs (and never =
received any feedback about) was to reclassify 6to4 as Experimental.   =
Experimental seems completely appropriate for a protocol that is useful, =
but only in corner cases.  And I think it's also appropriate and useful =
to try to learn from the experience with 6to4, even if we realize that =
6to4 will never be a generally applicable IPv6 transition solution =
again.

And maybe, just maybe, Experimental will be enough of a "slap" at 6to4 =
to mollify the "kill it yesterday" crowd.  For one thing, it clearly =
indicates that 6to4 is no longer a standard.

But in order to quieten down the discussion here, I suggest that people =
reply to me privately if they can't live with this.   If I get lots of =
those replies, I'll know that it's not worth pursuing.

Keith


From sustrik@250bpm.com  Mon Jul  4 00:42:11 2011
Return-Path: <sustrik@250bpm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB9EF21F86E4 for <ietf@ietfa.amsl.com>; Mon,  4 Jul 2011 00:42:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.694
X-Spam-Level: 
X-Spam-Status: No, score=-0.694 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SK=1.35, HOST_EQ_SK=0.555]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OzY2I8FnTT79 for <ietf@ietfa.amsl.com>; Mon,  4 Jul 2011 00:42:11 -0700 (PDT)
Received: from mail.moloch.sk (chrocht.moloch.sk [62.176.169.44]) by ietfa.amsl.com (Postfix) with ESMTP id 295E421F86D5 for <ietf@ietf.org>; Mon,  4 Jul 2011 00:42:10 -0700 (PDT)
Received: from [10.9.1.2] (chello089173046084.chello.sk [89.173.46.84]) by mail.moloch.sk (Postfix) with ESMTPSA id 28FEA180008E; Mon,  4 Jul 2011 09:42:08 +0200 (CEST)
Message-ID: <4E116ED8.10506@250bpm.com>
Date: Mon, 04 Jul 2011 09:42:16 +0200
From: Martin Sustrik <sustrik@250bpm.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: John Levine <johnl@iecc.com>
Subject: Re: Comments surrounding draft-iab-dns-applications-01
References: <20110429023630.46187.qmail@joyce.lan>
In-Reply-To: <20110429023630.46187.qmail@joyce.lan>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Ed.Lewis@neustar.biz, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jul 2011 07:42:11 -0000

On 04/29/2011 04:36 AM, John Levine wrote:

> So my advice would be to back up and write down in one or two
> sentences what problem this document is supposed to fix or at least
> describe, and then see how much of the rest of it might be salvaged.

I was thinking of storing data in DNS and the document proved valuable 
to determine whether its a good idea or not. I mean, not whether it is 
technically feasible, but whether it makes sense at all.

So, while the mission statement may be a bit unclear, it's definitely a 
useful document.

Martin

From johnl@iecc.com  Mon Jul  4 07:02:19 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 8307411E807C for <ietf@ietfa.amsl.com>; Mon,  4 Jul 2011 07:02:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.54
X-Spam-Level: 
X-Spam-Status: No, score=-102.54 tagged_above=-999 required=5 tests=[AWL=0.060, 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 d8VDERzU6Trk for <ietf@ietfa.amsl.com>; Mon,  4 Jul 2011 07:02:19 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 560E921F8681 for <ietf@ietf.org>; Mon,  4 Jul 2011 07:02:18 -0700 (PDT)
Received: (qmail 21055 invoked from network); 4 Jul 2011 14:02:17 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=523e.4e11c7e9.k1107; bh=lB6bL7pKbWadfFZYzA/s4fekaRH4YlR3bWOa/k7kPSM=; b=r4mTyiLlENARIT9qNsGwL6nzMcVGPfbdZF5HpjvwQO5+8vyaNjKzdK0yZddY4kUUXiqIcr5heHP0lyXcFkGbfoqny/7Ma6A3L1zA4fYUZGALAXyuwZ90KE2ytJ/BzuB3dgsHu++XnELm5u4vG2Te6kY2ry/L/BuaGvL5vcm4KS4=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1) with (DHE-RSA-AES256-SHA encrypted) SMTP; 4 Jul 2011 14:01:54 -0000
Date: 4 Jul 2011 10:02:15 -0400
Message-ID: <alpine.BSF.2.00.1107040940090.60353@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Martin Sustrik" <sustrik@250bpm.com>
Subject: Re: Comments surrounding draft-iab-dns-applications-01
In-Reply-To: <4E116ED8.10506@250bpm.com>
References: <20110429023630.46187.qmail@joyce.lan> <4E116ED8.10506@250bpm.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: Ed.Lewis@neustar.biz, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jul 2011 14:02:19 -0000

>> So my advice would be to back up and write down in one or two
>> sentences what problem this document is supposed to fix or at least
>> describe, and then see how much of the rest of it might be salvaged.
>
> I was thinking of storing data in DNS and the document proved valuable to 
> determine whether its a good idea or not. I mean, not whether it is 
> technically feasible, but whether it makes sense at all.
>
> So, while the mission statement may be a bit unclear, it's definitely a 
> useful document.

I agree that such a document would be useful, but this isn't it. 
Applications are poorly suited for the DNS if they need fuzzy matches, or 
range queries, or have query patterns that don't cache well.  (IPv6 rDNS 
has that last problem.)  You can argue about how large query and response 
sizes should be, although DNSSEC has forced an answer to that one.

Applications that map fixed query names to (more or less) fixed responses 
work fine on top of the DNS, even if the query doesn't look much like a 
host name and the response looks nothing at all like an A record, e.g., 
NAPTR.

A document that described the actual technical architecture of the DNS, 
without confusing it with the design of applications built on top of the 
DNS would be a good idea.  I suppose I could try and write one.

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 RCosta@ptinovacao.pt  Mon Jul  4 15:02:39 2011
Return-Path: <RCosta@ptinovacao.pt>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 373081F0C42; Mon,  4 Jul 2011 15:02:39 -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 JyXzKojjnqtO; Mon,  4 Jul 2011 15:02:35 -0700 (PDT)
Received: from owa.ptinovacao.pt (owa.ptinovacao.pt [194.65.138.99]) by ietfa.amsl.com (Postfix) with ESMTP id 5CCDF1F0C3B; Mon,  4 Jul 2011 15:02:35 -0700 (PDT)
Received: from INOAVREX11.ptin.corpPT.com ([10.112.15.121]) by inoavrcas01.ptin.corpPT.com ([10.112.15.99]) with mapi; Mon, 4 Jul 2011 23:02:33 +0100
From: Rui Costa <RCosta@ptinovacao.pt>
To: "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
Date: Mon, 4 Jul 2011 23:02:31 +0100
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity Verification, Continuity Check and Remote Defect indication for MPLS	Transport	Profile) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity Verification, Continuity Check and Remote Defect indication for MPLS	Transport	Profile) to Proposed Standard
Thread-Index: Acw3LJ0GTOqQfPcUQOGUhgK/1kXgjgDPfXWg
Message-ID: <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B3D5@INOAVREX11.ptin.corpPT.com>
References: <20110630134642.1281.3095.idtracker@ietfa.amsl.com>
In-Reply-To: <20110630134642.1281.3095.idtracker@ietfa.amsl.com>
Accept-Language: pt-PT
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: pt-PT
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jul 2011 22:02:39 -0000

IMHO and for the record:=09

ITU-T comments regarding this draft haven't been discussed with ITU-T but w=
ere simply ignored. No LS describing these comments' resolution was sent.=09

Several service providers regarded this draft as not meeting their transpor=
t networks' needs.=09

[The v03 draft was published in Feb and went to WG LC.=09
The v04 draft addressing WG LC comments was published on the 28th June (sam=
e date as the proto write-up).=09
When was the WG LC launched, to verify LC comments resolution?]=09

Regards,=09
Rui


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of The=
 IESG
Sent: quinta-feira, 30 de Junho de 2011 14:47
To: IETF-Announce
Cc: mpls@ietf.org
Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive=
 Connectivity Verification, Continuity Check and Remote Defect indication f=
or MPLS Transport Profile) to Proposed Standard


The IESG has received a request from the Multiprotocol Label Switching WG
(mpls) to consider the following document:
- 'Proactive Connectivity Verification, Continuity Check and Remote
   Defect indication for MPLS Transport Profile'
  <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract

   Continuity Check, Proactive Connectivity Verification and Remote
   Defect Indication functionalities are required for MPLS-TP OAM.

   Continuity Check monitors the integrity of the continuity of the
   label switched path for any loss of continuity defect. Connectivity
   verification monitors the integrity of the routing of the label
   switched path between sink and source for any connectivity issues.
   Remote defect indication enables an End Point to report, to its
   associated End Point, a fault or defect condition that it detects on
   a pseudo wire, label switched path or Section.

   This document specifies methods for proactive continuity check,
   continuity verification, and remote defect indication for MPLS-TP
   label switched paths, pseudo wires and Sections using Bidirectional
   Forwarding Detection.


The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/


No IPR declarations have been submitted directly on this I-D.
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls



From marka@isc.org  Mon Jul  4 16:14: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 1C75521F8809 for <ietf@ietfa.amsl.com>; Mon,  4 Jul 2011 16:14:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.629
X-Spam-Level: 
X-Spam-Status: No, score=-2.629 tagged_above=-999 required=5 tests=[AWL=-0.030, 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 cBMjePkqi5+m for <ietf@ietfa.amsl.com>; Mon,  4 Jul 2011 16:14:55 -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 83B7E21F874F for <ietf@ietf.org>; Mon,  4 Jul 2011 16:14:55 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.pao1.isc.org (Postfix) with ESMTPS id 8CB0AC94D6; Mon,  4 Jul 2011 23:14: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 F3CD4216C7B; Mon,  4 Jul 2011 23:14:43 +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 023081171247; Tue,  5 Jul 2011 09:14:41 +1000 (EST)
To: "John R. Levine" <johnl@iecc.com>
From: Mark Andrews <marka@isc.org>
References: <20110429023630.46187.qmail@joyce.lan> <4E116ED8.10506@250bpm.com> <alpine.BSF.2.00.1107040940090.60353@joyce.lan>
Subject: Re: Comments surrounding draft-iab-dns-applications-01
In-reply-to: Your message of "04 Jul 2011 10:02:15 -0400." <alpine.BSF.2.00.1107040940090.60353@joyce.lan>
Date: Tue, 05 Jul 2011 09:14:41 +1000
Message-Id: <20110704231442.023081171247@drugs.dv.isc.org>
Cc: Ed.Lewis@neustar.biz, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jul 2011 23:14:57 -0000

In message <alpine.BSF.2.00.1107040940090.60353@joyce.lan>, "John R. Levine" wr
ites:
> >> So my advice would be to back up and write down in one or two
> >> sentences what problem this document is supposed to fix or at least
> >> describe, and then see how much of the rest of it might be salvaged.
> >
> > I was thinking of storing data in DNS and the document proved valuable to 
> > determine whether its a good idea or not. I mean, not whether it is 
> > technically feasible, but whether it makes sense at all.
> >
> > So, while the mission statement may be a bit unclear, it's definitely a 
> > useful document.
> 
> I agree that such a document would be useful, but this isn't it. 
> Applications are poorly suited for the DNS if they need fuzzy matches, or 
> range queries, or have query patterns that don't cache well.  (IPv6 rDNS 
> has that last problem.)  You can argue about how large query and response 
> sizes should be, although DNSSEC has forced an answer to that one.

Reverse IPv6 caches well.  You just can't pre-populate servers with PTR
records for all 2^64 ptr records in a normal IPv6 subnet.  You need to
use tools that add records for nodes that actually exist.  Those tools
are a decade old now.
 
> Applications that map fixed query names to (more or less) fixed responses 
> work fine on top of the DNS, even if the query doesn't look much like a 
> host name and the response looks nothing at all like an A record, e.g., 
> NAPTR.
> 
> A document that described the actual technical architecture of the DNS, 
> without confusing it with the design of applications built on top of the 
> DNS would be a good idea.  I suppose I could try and write one.
> 
> 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
> _______________________________________________
> 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 johnl@iecc.com  Mon Jul  4 17:23:55 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 136E521F8796 for <ietf@ietfa.amsl.com>; Mon,  4 Jul 2011 17:23:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.55
X-Spam-Level: 
X-Spam-Status: No, score=-102.55 tagged_above=-999 required=5 tests=[AWL=0.050, 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 FpQQMKF-Doed for <ietf@ietfa.amsl.com>; Mon,  4 Jul 2011 17:23:54 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 3F2EC21F877E for <ietf@ietf.org>; Mon,  4 Jul 2011 17:23:53 -0700 (PDT)
Received: (qmail 25401 invoked from network); 5 Jul 2011 00:23: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=6338.4e125997.k1107; bh=tU7M1fDvRkfmkBJKZnzu3AKGN6daI/GDdIFt0gHdMgo=; b=2bsh2PNhg656/UsLH2tC8KZwGGyleEovMH/tGdbp5Vo/wU3L3L02/mf50RQH2R5Yq7kYmZt5U3a3Lk2Pen6hh9l83QTUvxhMG7L6jzq/YKwd86gL0ItY0ns0aFdCoCCuCVs+hvG4V8MqAEXakSDit3ro89h7iUdVzll2rtJdat8=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1) with (DHE-RSA-AES256-SHA encrypted) SMTP; 5 Jul 2011 00:23:29 -0000
Date: 4 Jul 2011 20:23:50 -0400
Message-ID: <alpine.BSF.2.00.1107041959400.29602@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Mark Andrews" <marka@isc.org>
Subject: Re: Comments surrounding draft-iab-dns-applications-01
In-Reply-To: <20110704231442.023081171247@drugs.dv.isc.org>
References: <20110429023630.46187.qmail@joyce.lan> <4E116ED8.10506@250bpm.com> <alpine.BSF.2.00.1107040940090.60353@joyce.lan> <20110704231442.023081171247@drugs.dv.isc.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, 05 Jul 2011 00:23:55 -0000

> Reverse IPv6 caches well.  You just can't pre-populate servers with PTR
> records for all 2^64 ptr records in a normal IPv6 subnet.  You need to
> use tools that add records for nodes that actually exist.  Those tools
> are a decade old now.

Over in e-mail land, we've been pondering the behavior of spammers, who 
will likely hop to a different IPv6 address for every spam. If you do rDNS 
lookups, your cache will fill up with useless entries, maybe PTR, maybe 
NXDOMAIN, it hardly matters.  DNSBLs and DNSWLs, if done the same way as 
they are in IPv4, have the same problem.  These issues are well known in 
the mail ops community, where it's now the standard advice not to try rDNS 
lookups on incoming IPv6 mail.

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 marka@isc.org  Mon Jul  4 17:56:53 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 5F75921F87E9 for <ietf@ietfa.amsl.com>; Mon,  4 Jul 2011 17:56:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.627
X-Spam-Level: 
X-Spam-Status: No, score=-2.627 tagged_above=-999 required=5 tests=[AWL=-0.027, 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 60xh9yXAv+Nn for <ietf@ietfa.amsl.com>; Mon,  4 Jul 2011 17:56:53 -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 CD11021F87E7 for <ietf@ietf.org>; Mon,  4 Jul 2011 17:56:52 -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 4091FC94C4; Tue,  5 Jul 2011 00:56: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 C5AF9216C7B; Tue,  5 Jul 2011 00:56: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 D3F52117252B; Tue,  5 Jul 2011 10:56:40 +1000 (EST)
To: "John R. Levine" <johnl@iecc.com>
From: Mark Andrews <marka@isc.org>
References: <20110429023630.46187.qmail@joyce.lan> <4E116ED8.10506@250bpm.com> <alpine.BSF.2.00.1107040940090.60353@joyce.lan> <20110704231442.023081171247@drugs.dv.isc.org> <alpine.BSF.2.00.1107041959400.29602@joyce.lan>
Subject: Re: Comments surrounding draft-iab-dns-applications-01
In-reply-to: Your message of "04 Jul 2011 20:23:50 -0400." <alpine.BSF.2.00.1107041959400.29602@joyce.lan>
Date: Tue, 05 Jul 2011 10:56:40 +1000
Message-Id: <20110705005640.D3F52117252B@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, 05 Jul 2011 00:56:53 -0000

In message <alpine.BSF.2.00.1107041959400.29602@joyce.lan>, "John R. Levine" wri
tes:
> > Reverse IPv6 caches well.  You just can't pre-populate servers with PTR
> > records for all 2^64 ptr records in a normal IPv6 subnet.  You need to
> > use tools that add records for nodes that actually exist.  Those tools
> > are a decade old now.
> 
> Over in e-mail land, we've been pondering the behavior of spammers, who 
> will likely hop to a different IPv6 address for every spam. If you do rDNS 
> lookups, your cache will fill up with useless entries, maybe PTR, maybe 
> NXDOMAIN, it hardly matters.  DNSBLs and DNSWLs, if done the same way as 
> they are in IPv4, have the same problem.  These issues are well known in 
> the mail ops community, where it's now the standard advice not to try rDNS 
> lookups on incoming IPv6 mail.
 
Or you just tune the cache retention times.  For NXDOMAIN/NODATA
that's 3 hours by default for named but could be tuned down to 10
minutes or lower without ill effects.  RFC 2308 recommends 1-3 hours.

I also don't see the point in worrying about this.  Caches cope
with spammers using a different From domains on each piece of email
which is looked up in the DNS.  The worst using a different IPv6
address per email can do is double the cache requirements for the
same volume of email.

LRU cleaning of the cache will cope with this.

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

From johnl@iecc.com  Mon Jul  4 19:05: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 327A721F8742 for <ietf@ietfa.amsl.com>; Mon,  4 Jul 2011 19:05:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.557
X-Spam-Level: 
X-Spam-Status: No, score=-102.557 tagged_above=-999 required=5 tests=[AWL=0.043, 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 riHgU2-7w7pu for <ietf@ietfa.amsl.com>; Mon,  4 Jul 2011 19:05:36 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 4158B21F8741 for <ietf@ietf.org>; Mon,  4 Jul 2011 19:05:35 -0700 (PDT)
Received: (qmail 26055 invoked from network); 5 Jul 2011 02:05:34 -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=65c6.4e12716e.k1107; bh=qLOD5CTUrDsN5lgpWwYGKHhuUoV6a7s7CgWZQfNVc5I=; b=Adhu/Qr3ceEkNHyj9ckd0ELflBZxEYjIzLJ88ptVVjvrj/91WMigaOV9q5irfRxpmvZZmjxRga9WRsyslYOCQ45/isyjHQjzpkGly87WcKzrWkSvxd4ZrXqHFPS2HpCQvK6M82N+Cp3rT9+6QVAfgRr3IE2yKCJEAUVLmRURXN4=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1) with (DHE-RSA-AES256-SHA encrypted) SMTP; 5 Jul 2011 02:05:11 -0000
Date: 4 Jul 2011 22:05:33 -0400
Message-ID: <alpine.BSF.2.00.1107042151340.62218@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Mark Andrews" <marka@isc.org>
Subject: Re: Comments surrounding draft-iab-dns-applications-01
In-Reply-To: <20110705005640.D3F52117252B@drugs.dv.isc.org>
References: <20110429023630.46187.qmail@joyce.lan> <4E116ED8.10506@250bpm.com> <alpine.BSF.2.00.1107040940090.60353@joyce.lan> <20110704231442.023081171247@drugs.dv.isc.org> <alpine.BSF.2.00.1107041959400.29602@joyce.lan> <20110705005640.D3F52117252B@drugs.dv.isc.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, 05 Jul 2011 02:05:37 -0000

>> Over in e-mail land, we've been pondering the behavior of spammers, who
>> will likely hop to a different IPv6 address for every spam. If you do rDNS
>> lookups, your cache will fill up with useless entries, maybe PTR, maybe
>> NXDOMAIN, it hardly matters.  DNSBLs and DNSWLs, if done the same way as
>> they are in IPv4, have the same problem.  These issues are well known in
>> the mail ops community, where it's now the standard advice not to try rDNS
>> lookups on incoming IPv6 mail.
>
> Or you just tune the cache retention times.  For NXDOMAIN/NODATA
> that's 3 hours by default for named but could be tuned down to 10
> minutes or lower without ill effects.  RFC 2308 recommends 1-3 hours.

DNSBLs already set the min pretty low, e.g. 150 sec for Spamhaus. 
Doesn't really matter how low it is if you have so many entries that they 
force out the useful ones.

> I also don't see the point in worrying about this.  Caches cope
> with spammers using a different From domains on each piece of email
> which is looked up in the DNS.

Modern spam filters don't usually look up the author domain, since it's 
usually a genuine address taken from the spam list so it's unrelated to 
the real sender.  Even if they did, universe of domains that exist is a 
vastly smaller set than even IPv4 addresses, and one which caches pretty 
well since so many of them are at large sites like Yahoo and Hotmail.

In any event, we can argue about how good or bad an idea it is to use IPv6 
rDNS, but that's tangential to the issues of deciding what are reasonable 
applications for the DNS.  If you're right and rDNS caches well, it's a 
good application for DNS.  If I'm right and it doesn't cache at all, it's 
not such a good application.

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  Mon Jul  4 20:02: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 C35E621F86F2 for <ietf@ietfa.amsl.com>; Mon,  4 Jul 2011 20:02:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.519
X-Spam-Level: 
X-Spam-Status: No, score=-3.519 tagged_above=-999 required=5 tests=[AWL=0.080,  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 mYN789zg2yLn for <ietf@ietfa.amsl.com>; Mon,  4 Jul 2011 20:02:03 -0700 (PDT)
Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id CCD8E21F86E9 for <ietf@ietf.org>; Mon,  4 Jul 2011 20:02:03 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id 70C3120969; Mon,  4 Jul 2011 23:02:03 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Mon, 04 Jul 2011 23:02: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=AF/m9Rr9Sw6doPhFhXT+ssXkV24=; b=kQpzRe6X1zZ1h2oW+PSS+sVhOAtZsd4a/q7tDdNylSxZCLOZK/ThQ/fFU06niFmPtgxpk7qXfb45UPBWUEgF/Co80yYI4WEsBfsEsXa9RN8TEKVRsz6EQM08+BTYlOuFh0PuV7Q2LJLFtQHKaCo3zn17nk+h7GbKeJodJhTtFxk=
X-Sasl-enc: sOA7wwSZdChiiBlNeUvhLFYnzY/InJMGQ6v0PlsS6+ch 1309834922
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 6F0B7440E45; Mon,  4 Jul 2011 23:02:02 -0400 (EDT)
Subject: Re: Comments surrounding draft-iab-dns-applications-01
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: <alpine.BSF.2.00.1107041959400.29602@joyce.lan>
Date: Mon, 4 Jul 2011 23:01:44 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <484E72AD-CE81-43A2-8077-E0C71CD56A51@network-heretics.com>
References: <20110429023630.46187.qmail@joyce.lan> <4E116ED8.10506@250bpm.com> <alpine.BSF.2.00.1107040940090.60353@joyce.lan> <20110704231442.023081171247@drugs.dv.isc.org> <alpine.BSF.2.00.1107041959400.29602@joyce.lan>
To: John R. 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: Tue, 05 Jul 2011 03:02:04 -0000

On Jul 4, 2011, at 8:23 PM, John R. Levine wrote:

>> Reverse IPv6 caches well.  You just can't pre-populate servers with =
PTR
>> records for all 2^64 ptr records in a normal IPv6 subnet.  You need =
to
>> use tools that add records for nodes that actually exist.  Those =
tools
>> are a decade old now.
>=20
> Over in e-mail land, we've been pondering the behavior of spammers, =
who will likely hop to a different IPv6 address for every spam. If you =
do rDNS lookups, your cache will fill up with useless entries, maybe =
PTR, maybe NXDOMAIN, it hardly matters.  DNSBLs and DNSWLs, if done the =
same way as they are in IPv4, have the same problem.  These issues are =
well known in the mail ops community, where it's now the standard advice =
not to try rDNS lookups on incoming IPv6 mail.

Yes, but rDNS PTR lookups always have been pretty much meaningless =
anyway, and will only get worse in IPv4 due to LSN.=20

Keith


From marka@isc.org  Mon Jul  4 20:05: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 8437D21F8714 for <ietf@ietfa.amsl.com>; Mon,  4 Jul 2011 20:05:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.625
X-Spam-Level: 
X-Spam-Status: No, score=-2.625 tagged_above=-999 required=5 tests=[AWL=-0.026, 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 XxpeYJobsoID for <ietf@ietfa.amsl.com>; Mon,  4 Jul 2011 20:05:58 -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 510C721F8711 for <ietf@ietf.org>; Mon,  4 Jul 2011 20:05:57 -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 22C795F984C; Tue,  5 Jul 2011 03:05:41 +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 B1F80216C7B; Tue,  5 Jul 2011 03:05:39 +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 9EE7711730B5; Tue,  5 Jul 2011 13:05:37 +1000 (EST)
To: "John R. Levine" <johnl@iecc.com>
From: Mark Andrews <marka@isc.org>
References: <20110429023630.46187.qmail@joyce.lan> <4E116ED8.10506@250bpm.com> <alpine.BSF.2.00.1107040940090.60353@joyce.lan> <20110704231442.023081171247@drugs.dv.isc.org> <alpine.BSF.2.00.1107041959400.29602@joyce.lan> <20110705005640.D3F52117252B@drugs.dv.isc.org> <alpine.BSF.2.00.1107042151340.62218@joyce.lan>
Subject: Re: Comments surrounding draft-iab-dns-applications-01
In-reply-to: Your message of "04 Jul 2011 22:05:33 -0400." <alpine.BSF.2.00.1107042151340.62218@joyce.lan>
Date: Tue, 05 Jul 2011 13:05:37 +1000
Message-Id: <20110705030537.9EE7711730B5@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, 05 Jul 2011 03:05:59 -0000

In message <alpine.BSF.2.00.1107042151340.62218@joyce.lan>, "John R. Levine" wri
tes:
> >> Over in e-mail land, we've been pondering the behavior of spammers, who
> >> will likely hop to a different IPv6 address for every spam. If you do rDNS
> >> lookups, your cache will fill up with useless entries, maybe PTR, maybe
> >> NXDOMAIN, it hardly matters.  DNSBLs and DNSWLs, if done the same way as
> >> they are in IPv4, have the same problem.  These issues are well known in
> >> the mail ops community, where it's now the standard advice not to try rDNS
> >> lookups on incoming IPv6 mail.
> >
> > Or you just tune the cache retention times.  For NXDOMAIN/NODATA
> > that's 3 hours by default for named but could be tuned down to 10
> > minutes or lower without ill effects.  RFC 2308 recommends 1-3 hours.
> 
> DNSBLs already set the min pretty low, e.g. 150 sec for Spamhaus. 
> Doesn't really matter how low it is if you have so many entries that they 
> force out the useful ones.

DNS[WB]L's are not rDNS.  rDNS is designed to associate a name with
a address.

DNS[WB]L's have never been a good fit to the DNS, rather they have
not been a bad enough fit to require something better to be done.

The naive approach of reversing the address, converting to nibbles
and appending a suffix won't scale.

For IPv6 if you did the reverse of /48, /52, /56, /60 and /64
prefixes, which matches delegation patterns along with NXDOMAIN
synthesis, you would still be fine.  You stop the search on NXDOMAIN
or data with perhaps a new value which says to continue searching
for white listed records.  One could even start with /32 if one is
worried about spammers pretending to be ISPs.

It requires slightly more intelligence in the MTA that faking up a
address lookup.  NXDOMAIN synthesis doesn't have to be done in the
DNS cache.  It can be done in the application provided it keeps
track of the ranges covered by the NSEC{3} records returned with
the negative responses.  DNSSEC validators that support DLV do this
sort of thing.

> > I also don't see the point in worrying about this.  Caches cope
> > with spammers using a different From domains on each piece of email
> > which is looked up in the DNS.
> 
> Modern spam filters don't usually look up the author domain, since it's 
> usually a genuine address taken from the spam list so it's unrelated to 
> the real sender.  Even if they did, universe of domains that exist is a 
> vastly smaller set than even IPv4 addresses, and one which caches pretty 
> well since so many of them are at large sites like Yahoo and Hotmail.

Both are effectively infinite compared to cache sizes.
 
> In any event, we can argue about how good or bad an idea it is to use IPv6 
> rDNS, but that's tangential to the issues of deciding what are reasonable 
> applications for the DNS.  If you're right and rDNS caches well, it's a 
> good application for DNS.  If I'm right and it doesn't cache at all, it's 
> not such a good application.
> 
> 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
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From johnl@iecc.com  Mon Jul  4 20:31: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 D5BAD11E8093 for <ietf@ietfa.amsl.com>; Mon,  4 Jul 2011 20:31:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.563
X-Spam-Level: 
X-Spam-Status: No, score=-102.563 tagged_above=-999 required=5 tests=[AWL=0.038, 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 EydOpBgnXWdB for <ietf@ietfa.amsl.com>; Mon,  4 Jul 2011 20:31:54 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 216B211E8091 for <ietf@ietf.org>; Mon,  4 Jul 2011 20:31:53 -0700 (PDT)
Received: (qmail 26793 invoked from network); 5 Jul 2011 03:31:52 -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=68a8.4e1285a8.k1107; bh=lyxCH8H4zoK8zzfVv+wQNr7NMEbPMC4G9mhFs84G8xc=; b=fo2+xuoYPDZu8u0ytiVpOopOmnmN0LKYpNEk5eeG8FxpnEvjw5uB3GmGO+GQfYCy9eeoaxYKJJi48+635dPzlElAw8RNHmazs/Jg8K8p0XvgeavYXhB0SOv5wrHZF2+lny+0wjfEcwhobupHMrPA3mxlLVriqCPIu1MemwTOY7Q=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1) with (DHE-RSA-AES256-SHA encrypted) SMTP; 5 Jul 2011 03:31:29 -0000
Date: 4 Jul 2011 23:31:51 -0400
Message-ID: <alpine.BSF.2.00.1107042329060.89019@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Mark Andrews" <marka@isc.org>
Subject: Re: Comments surrounding draft-iab-dns-applications-01
In-Reply-To: <20110705030537.9EE7711730B5@drugs.dv.isc.org>
References: <20110429023630.46187.qmail@joyce.lan> <4E116ED8.10506@250bpm.com> <alpine.BSF.2.00.1107040940090.60353@joyce.lan> <20110704231442.023081171247@drugs.dv.isc.org> <alpine.BSF.2.00.1107041959400.29602@joyce.lan> <20110705005640.D3F52117252B@drugs.dv.isc.org> <alpine.BSF.2.00.1107042151340.62218@joyce.lan> <20110705030537.9EE7711730B5@drugs.dv.isc.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, 05 Jul 2011 03:31:54 -0000

> The naive approach of reversing the address, converting to nibbles
> and appending a suffix won't scale.
>
> For IPv6 if you did the reverse of /48, /52, /56, /60 and /64
> prefixes, which matches delegation patterns along with NXDOMAIN
> synthesis, you would still be fine.  You stop the search on NXDOMAIN
> or data with perhaps a new value which says to continue searching
> for white listed records.  One could even start with /32 if one is
> worried about spammers pretending to be ISPs.

I don't necessarily disagree, but now you've just upgraded the DNS 
(NXDOMAIN synthesis is far from universal) and layered a probing protocol 
on top of it.  We can have a theological argument about whether that 
counts as "using the DNS".

R's,
John

From marka@isc.org  Mon Jul  4 23:25:08 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 E24C911E80B8 for <ietf@ietfa.amsl.com>; Mon,  4 Jul 2011 23:25:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.623
X-Spam-Level: 
X-Spam-Status: No, score=-2.623 tagged_above=-999 required=5 tests=[AWL=-0.024, 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 i0JHlHD5w5EI for <ietf@ietfa.amsl.com>; Mon,  4 Jul 2011 23:25:08 -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 4F04E11E8070 for <ietf@ietf.org>; Mon,  4 Jul 2011 23:25:07 -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 03A8B5F9904; Tue,  5 Jul 2011 06:24:47 +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 E50DC216C7B; Tue,  5 Jul 2011 06:24:45 +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 670CF117975D; Tue,  5 Jul 2011 16:24:43 +1000 (EST)
To: "John R. Levine" <johnl@iecc.com>
From: Mark Andrews <marka@isc.org>
References: <20110429023630.46187.qmail@joyce.lan> <4E116ED8.10506@250bpm.com> <alpine.BSF.2.00.1107040940090.60353@joyce.lan> <20110704231442.023081171247@drugs.dv.isc.org> <alpine.BSF.2.00.1107041959400.29602@joyce.lan> <20110705005640.D3F52117252B@drugs.dv.isc.org> <alpine.BSF.2.00.1107042151340.62218@joyce.lan> <20110705030537.9EE7711730B5@drugs.dv.isc.org> <alpine.BSF.2.00.1107042329060.89019@joyce.lan>
Subject: Re: Comments surrounding draft-iab-dns-applications-01
In-reply-to: Your message of "04 Jul 2011 23:31:51 -0400." <alpine.BSF.2.00.1107042329060.89019@joyce.lan>
Date: Tue, 05 Jul 2011 16:24:43 +1000
Message-Id: <20110705062443.670CF117975D@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, 05 Jul 2011 06:25:09 -0000

In message <alpine.BSF.2.00.1107042329060.89019@joyce.lan>, "John R. Levine" wri
tes:
> > The naive approach of reversing the address, converting to nibbles
> > and appending a suffix won't scale.
> >
> > For IPv6 if you did the reverse of /48, /52, /56, /60 and /64
> > prefixes, which matches delegation patterns along with NXDOMAIN
> > synthesis, you would still be fine.  You stop the search on NXDOMAIN
> > or data with perhaps a new value which says to continue searching
> > for white listed records.  One could even start with /32 if one is
> > worried about spammers pretending to be ISPs.
> 
> I don't necessarily disagree, but now you've just upgraded the DNS 
> (NXDOMAIN synthesis is far from universal)

No, just application smarts is needed.  The DNS already supports this
and it has been used for over 1/2 a decade now.

> and layered a probing protocol on top of it.  We can have a theological
> argument about whether that counts as "using the DNS".
>
> R's,
> John
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From fanf2@hermes.cam.ac.uk  Tue Jul  5 03:52:42 2011
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 237BD21F8777 for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 03:52: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 SWkIAYPK57za for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 03:52:41 -0700 (PDT)
Received: from ppsw-51.csi.cam.ac.uk (ppsw-51.csi.cam.ac.uk [131.111.8.151]) by ietfa.amsl.com (Postfix) with ESMTP id 2105621F8776 for <ietf@ietf.org>; Tue,  5 Jul 2011 03:52:39 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:39638) by ppsw-51.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:25) with esmtpa (EXTERNAL:fanf2) id 1Qe3F4-0002nD-Y5 (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Tue, 05 Jul 2011 11:52:34 +0100
Received: from fanf2 (helo=localhost) by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1Qe3F4-0004JM-Hf (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Tue, 05 Jul 2011 11:52:34 +0100
Date: Tue, 5 Jul 2011 11:52:34 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: "John R. Levine" <johnl@iecc.com>
Subject: Re: Comments surrounding draft-iab-dns-applications-01
In-Reply-To: <alpine.BSF.2.00.1107042151340.62218@joyce.lan>
Message-ID: <alpine.LSU.2.00.1107051145130.5578@hermes-2.csi.cam.ac.uk>
References: <20110429023630.46187.qmail@joyce.lan> <4E116ED8.10506@250bpm.com> <alpine.BSF.2.00.1107040940090.60353@joyce.lan> <20110704231442.023081171247@drugs.dv.isc.org> <alpine.BSF.2.00.1107041959400.29602@joyce.lan> <20110705005640.D3F52117252B@drugs.dv.isc.org> <alpine.BSF.2.00.1107042151340.62218@joyce.lan>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2011 10:52:42 -0000

John R. Levine <johnl@iecc.com> wrote:
>
> DNSBLs already set the min pretty low, e.g. 150 sec for Spamhaus. Doesn't
> really matter how low it is if you have so many entries that they force out
> the useful ones.

The really important records are the delegation chain NS records. It is
not so necessary to keep leaf records in the cache.

http://nms.csail.mit.edu/projects/dns/

> Modern spam filters don't usually look up the author domain, since it's
> usually a genuine address taken from the spam list so it's unrelated to the
> real sender.

I think it's still useful to reject mail with an unresolvable return path
domain.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Lundy, Fastnet: Southwest 4 or 5, increasing 6 or 7 later. Moderate or rough,
occasionally very rough later in Fastnet. Showers. Good.

From fanf2@hermes.cam.ac.uk  Tue Jul  5 03:56:29 2011
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 667E321F8605 for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 03:56:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 JM4yhoiDdphD for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 03:56:28 -0700 (PDT)
Received: from ppsw-41.csi.cam.ac.uk (ppsw-41.csi.cam.ac.uk [131.111.8.141]) by ietfa.amsl.com (Postfix) with ESMTP id AA65121F85FF for <ietf@ietf.org>; Tue,  5 Jul 2011 03:56:28 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:44928) by ppsw-41.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpa (EXTERNAL:fanf2) id 1Qe3Im-0005u6-Qa (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Tue, 05 Jul 2011 11:56:24 +0100
Received: from fanf2 (helo=localhost) by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1Qe3Im-0004wB-7Q (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Tue, 05 Jul 2011 11:56:24 +0100
Date: Tue, 5 Jul 2011 11:56:24 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: Mark Andrews <marka@isc.org>
Subject: Re: Comments surrounding draft-iab-dns-applications-01
In-Reply-To: <20110705030537.9EE7711730B5@drugs.dv.isc.org>
Message-ID: <alpine.LSU.2.00.1107051152550.5578@hermes-2.csi.cam.ac.uk>
References: <20110429023630.46187.qmail@joyce.lan> <4E116ED8.10506@250bpm.com> <alpine.BSF.2.00.1107040940090.60353@joyce.lan> <20110704231442.023081171247@drugs.dv.isc.org> <alpine.BSF.2.00.1107041959400.29602@joyce.lan> <20110705005640.D3F52117252B@drugs.dv.isc.org> <alpine.BSF.2.00.1107042151340.62218@joyce.lan> <20110705030537.9EE7711730B5@drugs.dv.isc.org>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: "John R. 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: Tue, 05 Jul 2011 10:56:29 -0000

Mark Andrews <marka@isc.org> wrote:
>
> DNS[WB]L's have never been a good fit to the DNS, rather they have
> not been a bad enough fit to require something better to be done.

Oh come off it, they are just as good a fit to the DNS as reverse DNS is.

> The naive approach of reversing the address, converting to nibbles
> and appending a suffix won't scale.

I don't understand why the setup is OK for reverse DNS but not blacklists.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Hebrides, Bailey, Fair Isle, Faeroes: Southeast 5 to 7, backing east or
northeast 4 or 5, occasionally 6 in north Bailey. Moderate or rough.
Occasional rain. Moderate or good, occasionally poor.

From fanf2@hermes.cam.ac.uk  Tue Jul  5 03:58:35 2011
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32F6A21F8731 for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 03:58:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Vc6EFHsq+Kz for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 03:58:34 -0700 (PDT)
Received: from ppsw-51.csi.cam.ac.uk (ppsw-51.csi.cam.ac.uk [131.111.8.151]) by ietfa.amsl.com (Postfix) with ESMTP id 947C521F8608 for <ietf@ietf.org>; Tue,  5 Jul 2011 03:58:34 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:44597) by ppsw-51.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:25) with esmtpa (EXTERNAL:fanf2) id 1Qe3Kq-00052o-WQ (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Tue, 05 Jul 2011 11:58:32 +0100
Received: from fanf2 (helo=localhost) by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1Qe3Kq-0005Fj-1E (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Tue, 05 Jul 2011 11:58:32 +0100
Date: Tue, 5 Jul 2011 11:58:32 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Comments surrounding draft-iab-dns-applications-01
In-Reply-To: <484E72AD-CE81-43A2-8077-E0C71CD56A51@network-heretics.com>
Message-ID: <alpine.LSU.2.00.1107051156480.5578@hermes-2.csi.cam.ac.uk>
References: <20110429023630.46187.qmail@joyce.lan> <4E116ED8.10506@250bpm.com> <alpine.BSF.2.00.1107040940090.60353@joyce.lan> <20110704231442.023081171247@drugs.dv.isc.org> <alpine.BSF.2.00.1107041959400.29602@joyce.lan> <484E72AD-CE81-43A2-8077-E0C71CD56A51@network-heretics.com>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: "John R. 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: Tue, 05 Jul 2011 10:58:35 -0000

Keith Moore <moore@network-heretics.com> wrote:
>
> Yes, but rDNS PTR lookups always have been pretty much meaningless
> anyway, and will only get worse in IPv4 due to LSN.

Reverse DNS for an LSN is just as informative as automatically populated
reverse DNS (and much more convenient than a whois lookup).

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Portland, Plymouth, Biscay: South 4 or 5, veering west or southwest 5 or 6.
Slight or moderate, occasionally rough later. Rain then showers. Moderate or
good.

From moore@network-heretics.com  Tue Jul  5 05:38: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 B709621F8715 for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 05:38:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.521
X-Spam-Level: 
X-Spam-Status: No, score=-3.521 tagged_above=-999 required=5 tests=[AWL=0.078,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 487c-KUh7+aB for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 05:38:59 -0700 (PDT)
Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id 125C621F86B5 for <ietf@ietf.org>; Tue,  5 Jul 2011 05:38:58 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id 3A15E20B23; Tue,  5 Jul 2011 08:38:58 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 05 Jul 2011 08:38:58 -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=5pLN0usf86RfLj25G6/gM/54DSw=; b=ZBABPuRPUy3+aTzcWhZqxmA5JZLdhR20BustDfcCBcpRTjBB0NYMluN/S+j5HE7caBk3c1sH1OnPYpQ+Rl4zn9DASH4BV+qisIWtGaC2qvujAlCzDbVCU+Xl63Ks6ksRu8EUfkSyRz/tOhX7cZkubY8arWuiNV3KW3Yg/frfldw=
X-Sasl-enc: 6nW/hr2nl3PLul84ZVUaTpP8mdbWh7zviXwT43PIbqJ4 1309869537
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 72098446B6B; Tue,  5 Jul 2011 08:38:57 -0400 (EDT)
Subject: Re: Comments surrounding draft-iab-dns-applications-01
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: <alpine.LSU.2.00.1107051156480.5578@hermes-2.csi.cam.ac.uk>
Date: Tue, 5 Jul 2011 08:38:39 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9BCB1D97-889E-4C09-AD73-3D84E1FCC814@network-heretics.com>
References: <20110429023630.46187.qmail@joyce.lan> <4E116ED8.10506@250bpm.com> <alpine.BSF.2.00.1107040940090.60353@joyce.lan> <20110704231442.023081171247@drugs.dv.isc.org> <alpine.BSF.2.00.1107041959400.29602@joyce.lan> <484E72AD-CE81-43A2-8077-E0C71CD56A51@network-heretics.com> <alpine.LSU.2.00.1107051156480.5578@hermes-2.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.1084)
Cc: "John R. 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: Tue, 05 Jul 2011 12:38:59 -0000

On Jul 5, 2011, at 6:58 AM, Tony Finch wrote:

> Keith Moore <moore@network-heretics.com> wrote:
>>=20
>> Yes, but rDNS PTR lookups always have been pretty much meaningless
>> anyway, and will only get worse in IPv4 due to LSN.
>=20
> Reverse DNS for an LSN is just as informative as automatically =
populated
> reverse DNS (and much more convenient than a whois lookup).

correct, in that both are meaningless.   but I think the percentage of =
lookups that return meaningful information will decrease - though more =
due to address space exhaustion than LSN, I suppose.

what LSN will decrease is the correlation between source IP address and =
source host, making any effort to associate a reputation with said =
addresses less valid.

Keith


From jnc@mercury.lcs.mit.edu  Tue Jul  5 07:44:31 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 D46F621F860A; Tue,  5 Jul 2011 07:44:31 -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 NDNQ-k9j00Be; Tue,  5 Jul 2011 07:44:31 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id EF3F121F85F5; Tue,  5 Jul 2011 07:44:30 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id DDFE218C10A; Tue,  5 Jul 2011 10:44:29 -0400 (EDT)
To: ietf@ietf.org, v6ops@ietf.org
Subject: RE: draft-ietf-v6ops-6to4-to-historic
Message-Id: <20110705144429.DDFE218C10A@mercury.lcs.mit.edu>
Date: Tue,  5 Jul 2011 10:44:29 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2011 14:44:32 -0000

    > From: Ronald Bonica <rbonica@juniper.net>

    >>> I think that I get it. There is no IETF consensus regarding the
    >>> compromise proposed below. ...

    >> But there is no rough consensus to do that either.

    > That is the claim of an appeal on the table. Let's run the appeal
    > process and figure out whether that claim is valid.

Sorry, this makes no sense.

You can't go ahead with draft-ietf-v6ops-6to4-to-historic if there is no
basic consensus in the IETF as a whole to do so - and your previous
declaration (on Saturday) basically accepted that there was no such basic
consensus (otherwise why withdraw the ID).

So now there is going to be a reversal, and the document is going to go ahead
- i.e. you must now be taking the position that there _is_ basic consensus in
the IETF (without which you could not proceed the ID).

The effect of this sort of thing on the reputation of I* should be obvious
to all.

	Noel

From lorenzo@google.com  Sat Jul  2 11:55:13 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 C9E6F1F0C5B for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 11:55:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.376
X-Spam-Level: 
X-Spam-Status: No, score=-105.376 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 ybp3SiMZd5-W for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 11:55:13 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id F18571F0C55 for <ietf@ietf.org>; Sat,  2 Jul 2011 11:55:12 -0700 (PDT)
Received: from wpaz5.hot.corp.google.com (wpaz5.hot.corp.google.com [172.24.198.69]) by smtp-out.google.com with ESMTP id p62ItBBK019608 for <ietf@ietf.org>; Sat, 2 Jul 2011 11:55:11 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1309632912; bh=q4CaM8rtSFf68OpzZDgzc7zKcyQ=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=Y/Yi36Q0S6YINGCkpG/WRLxzjk1UR3kaTHZge9XcLud+RIGQL2iY3Hc3f8kvBJ6zC DooR3ZGERBM3eZO0h/laQ==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type:x-system-of-record; b=IMqv09Vs0kEXTdxjbkzspjiJ73Lyxv7bsDa121PFMe02SJbYEvo4I3Iv1y8w48IQt Za4BMeIiWvyy7dogNBj8g==
Received: from yxn22 (yxn22.prod.google.com [10.190.4.86]) by wpaz5.hot.corp.google.com with ESMTP id p62ItAQu032149 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Sat, 2 Jul 2011 11:55:10 -0700
Received: by yxn22 with SMTP id 22so1340142yxn.28 for <ietf@ietf.org>; Sat, 02 Jul 2011 11:55:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=168jUnzc9zdoyIzQ+OAv9EjuGbo4CjljzeCOtLShr4Y=; b=TuxS0QygBItzOPeNXFXAa3Rz4r4hqoOlwaz8vS6jZEZouJ6hMGYzpHUe7Qgf0z82GX i7PrODxEpGIkiZTspMKA==
Received: by 10.150.116.1 with SMTP id o1mr3844893ybc.321.1309632910148; Sat, 02 Jul 2011 11:55:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.157.14 with HTTP; Sat, 2 Jul 2011 11:54:50 -0700 (PDT)
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sat, 2 Jul 2011 20:54:50 +0200
Message-ID: <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
To: Ronald Bonica <rbonica@juniper.net>
Content-Type: multipart/alternative; boundary=000e0cd3b04065468304a71aacb2
X-System-Of-Record: true
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:26 -0700
Cc: "v6ops@ietf.org" <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: Sat, 02 Jul 2011 18:55:13 -0000

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

On Sat, Jul 2, 2011 at 6:36 PM, Ronald Bonica <rbonica@juniper.net> wrote:

> - In order for the new draft to be published, it must achieve both V6OPS WG
> and IETF consensus
>
> If anyone objects to this course of action, please speak up soon.
>

Great, back to square one.

Is the reasoning behind the decision explained somewhere? My reading of the
threads on the subject in v6ops was that the opposition to 6to4-historic was
a small but vocal minority, and I thought that qualified as rough consensus.
But perhaps I missed some discussion.

Also, why do the author and the chairs think that the new draft will do any
better than 6to4-historic? I would assume that the same people who spoke up
against 6to4-historic will speak up against the new document, and since that
level of opposition was sufficient to prevent the publication
of 6to4-historic, it may be sufficient to prevent publication of the new
document as well. If so, we will have spent 3-6 months arguing about it for
naught.

Please, nobody answer this question with "welcome to the IETF" :-)

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

<div class=3D"gmail_quote">On Sat, Jul 2, 2011 at 6:36 PM, Ronald Bonica <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:rbonica@juniper.net">rbonica@juniper.=
net</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;">

- In order for the new draft to be published, it must achieve both V6OPS WG=
 and IETF consensus<br>
<br>
If anyone objects to this course of action, please speak up soon.<br></bloc=
kquote><div><br></div><div>Great, back to square one.</div><div><br></div><=
div>Is the reasoning behind the decision explained somewhere?=A0My reading =
of the threads on the subject in v6ops was that the opposition to 6to4-hist=
oric was a small but vocal minority, and I thought that qualified as rough =
consensus. But perhaps I missed some discussion.</div>

<div><br></div><div>Also, why do the author and the chairs think that the n=
ew draft will do any better than 6to4-historic? I would assume that the sam=
e people who spoke up against 6to4-historic will speak up against the new d=
ocument, and since that level of opposition was sufficient to prevent the p=
ublication of=A06to4-historic, it may be sufficient to prevent publication =
of the new document as well.=A0If so, we will have spent 3-6 months arguing=
 about it for naught.</div>

<div><br></div><div>Please, nobody answer this question with &quot;welcome =
to the IETF&quot; :-)</div></div>

--000e0cd3b04065468304a71aacb2--

From robert@raszuk.net  Sat Jul  2 12:28:21 2011
Return-Path: <robert@raszuk.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52EEE228011; Sat,  2 Jul 2011 12:28:21 -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, 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 ZWthvaIJesaS; Sat,  2 Jul 2011 12:28:20 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by ietfa.amsl.com (Postfix) with ESMTP id BC23122800F; Sat,  2 Jul 2011 12:28:20 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAGVwD06rRDoG/2dsb2JhbABSqAF3iHqjNp0ghjYEkjaEeItA
X-IronPort-AV: E=Sophos;i="4.65,465,1304294400"; d="scan'208";a="473996241"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-1.cisco.com with ESMTP; 02 Jul 2011 19:28:20 +0000
Received: from [192.168.1.66] (sjc-raszuk-87113.cisco.com [10.20.147.254]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p62JSIfT017667; Sat, 2 Jul 2011 19:28:19 GMT
Message-ID: <4E0F7156.4010307@raszuk.net>
Date: Sat, 02 Jul 2011 21:28:22 +0200
From: Robert Raszuk <robert@raszuk.net>
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: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com>
In-Reply-To: <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:25 -0700
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Jul 2011 19:28:21 -0000

Very well said Lorenzo.

+1

Unless Ron describes exactly one by one real reasons to give up on 
draft-ietf-v6ops-6to4-to-historic and majority of v6ops WG agrees with 
those reasons IMHO the document should proceed as is.

 > It will say that if 6-to-4 is implemented, it must be turned
 > off by default.

Last ... if something is turned on or off by default is an 
implementation choice and last time I checked IETF was not in business 
to mandate any implementation choice.

Thx,
R.


> On Sat, Jul 2, 2011 at 6:36 PM, Ronald Bonica <rbonica@juniper.net
> <mailto:rbonica@juniper.net>> wrote:
>
>     - In order for the new draft to be published, it must achieve both
>     V6OPS WG and IETF consensus
>
>     If anyone objects to this course of action, please speak up soon.
>
>
> Great, back to square one.
>
> Is the reasoning behind the decision explained somewhere? My reading of
> the threads on the subject in v6ops was that the opposition to
> 6to4-historic was a small but vocal minority, and I thought that
> qualified as rough consensus. But perhaps I missed some discussion.
>
> Also, why do the author and the chairs think that the new draft will do
> any better than 6to4-historic? I would assume that the same people who
> spoke up against 6to4-historic will speak up against the new document,
> and since that level of opposition was sufficient to prevent the
> publication of 6to4-historic, it may be sufficient to prevent
> publication of the new document as well. If so, we will have spent 3-6
> months arguing about it for naught.
>
> Please, nobody answer this question with "welcome to the IETF" :-)
>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From robert@raszuk.net  Sat Jul  2 13:22:40 2011
Return-Path: <robert@raszuk.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BF0511E80C1; Sat,  2 Jul 2011 13:22:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.539
X-Spam-Level: 
X-Spam-Status: No, score=-10.539 tagged_above=-999 required=5 tests=[AWL=0.060, 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 wUq9RGwI5FdS; Sat,  2 Jul 2011 13:22:40 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by ietfa.amsl.com (Postfix) with ESMTP id F02FB11E80A6; Sat,  2 Jul 2011 13:22:39 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EANt8D06rRDoJ/2dsb2JhbABSqAF3iHqjCJ0bhjYEkjaEeItA
X-IronPort-AV: E=Sophos;i="4.65,465,1304294400"; d="scan'208";a="288777999"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-4.cisco.com with ESMTP; 02 Jul 2011 20:22:39 +0000
Received: from [192.168.1.66] (sjc-raszuk-87113.cisco.com [10.20.147.254]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p62KMchj011052; Sat, 2 Jul 2011 20:22:38 GMT
Message-ID: <4E0F7E12.8060901@raszuk.net>
Date: Sat, 02 Jul 2011 22:22:42 +0200
From: Robert Raszuk <robert@raszuk.net>
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: Keith Moore <moore@network-heretics.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net>	<CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <DE414D2B-82ED-4C32-AFDF-EDAAB6D743B2@network-heretics.com>
In-Reply-To: <DE414D2B-82ED-4C32-AFDF-EDAAB6D743B2@network-heretics.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:25 -0700
Cc: "v6ops@ietf.org" <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
Reply-To: robert@raszuk.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Jul 2011 20:22:40 -0000

Hi Keith,

> I personally don't have any objection to the notion that 6to4 should
> be off by default and should require explicit configuration to enable
> it.

Is there any feature (perhaps other then netboot) on commercial or open 
source routers which is not off by default and which would require 
explicit configuration to enable it ?

Thx,
R.


From pch-b2B3A6689@u-1.phicoh.com  Sat Jul  2 14:18:58 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 745EB11E80DE; Sat,  2 Jul 2011 14:18:58 -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 5VIrWml1GoeA; Sat,  2 Jul 2011 14:18:58 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id AE63C11E80D9; Sat,  2 Jul 2011 14:18:57 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #55) id m1Qd7aY-0001hHC; Sat, 2 Jul 2011 23:18:54 +0200
Message-Id: <m1Qd7aY-0001hHC@stereo.hq.phicoh.net>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic 
From: Philip Homburg <pch-v6ops@u-1.phicoh.com>
Sender: pch-b2B3A6689@u-1.phicoh.com
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <DE414D2B-82ED-4C32-AFDF-EDAAB6D743B2@network-heretics.com> 
In-reply-to: Your message of "Sat, 2 Jul 2011 16:02:47 -0400 ." <DE414D2B-82ED-4C32-AFDF-EDAAB6D743B2@network-heretics.com> 
Date: Sat, 02 Jul 2011 23:18:52 +0200
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:25 -0700
Cc: "v6ops@ietf.org" <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: Sat, 02 Jul 2011 21:18:58 -0000

In your letter dated Sat, 2 Jul 2011 16:02:47 -0400 you wrote:
>
>> Is the reasoning behind the decision explained somewhere? My reading of the 
>threads on the subject in v6ops was that the opposition to 6to4-historic was a
> small but vocal minority, and I thought that qualified as rough consensus. 
>
>Even if there was rough consensus within v6ops, rough consensus of v6ops does 
>not equate to rough consensus of the entire IETF community. 

Is there any summary of the IETF community consensus? 

I sort of can't imagine that ISPs want to continue operating 6to4 relays
longer than strictly necessary. So I'm curious what the IETF community at
large considers the future of 6to4 in it's default-disabled mode.



From randy@psg.com  Sat Jul  2 14:35:07 2011
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B714221F85B2; Sat,  2 Jul 2011 14:35:07 -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_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uJHqrKW2PwKi; Sat,  2 Jul 2011 14:35:07 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 2F66921F84EB; Sat,  2 Jul 2011 14:35:06 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Qd7qC-000EHg-S5; Sat, 02 Jul 2011 21:35:05 +0000
Date: Sun, 03 Jul 2011 06:35:03 +0900
Message-ID: <m2y60g9xiw.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
In-Reply-To: <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:25 -0700
Cc: IPv6 Ops 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: Sat, 02 Jul 2011 21:35:07 -0000

>> If anyone objects to this course of action, please speak up soon.

i object.  as measured on the real internet, not the ietf bar, 6to4
sucks caterpillar snot.  it is damaging to the users and to the users'
view of ipv6.

> Great, back to square one.
> 
> Is the reasoning behind the decision explained somewhere? My reading of the
> threads on the subject in v6ops was that the opposition to 6to4-historic was
> a small but vocal minority, and I thought that qualified as rough consensus.

perhaps that minority was also vocal in the back room

> But perhaps I missed some discussion.
> 
> Also, why do the author and the chairs think that the new draft will do any
> better than 6to4-historic? I would assume that the same people who spoke up
> against 6to4-historic will speak up against the new document,

yes, but that will be a year from now.  in the ietf, delay is one form
of death.

> and since that level of opposition was sufficient to prevent the
> publication of 6to4-historic, it may be sufficient to prevent
> publication of the new document as well. If so, we will have spent 3-6
> months arguing about it for naught.
> 
> Please, nobody answer this question with "welcome to the IETF" :-)

this is nutso.  but this is normal.

welcome to the ietf

randy

From lorenzo@google.com  Sat Jul  2 18:03: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 2A27F11E808D for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 18:03:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.376
X-Spam-Level: 
X-Spam-Status: No, score=-105.376 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 vDWQD07tfzGZ for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 18:03:49 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by ietfa.amsl.com (Postfix) with ESMTP id B08F011E8078 for <ietf@ietf.org>; Sat,  2 Jul 2011 18:03:48 -0700 (PDT)
Received: from hpaq7.eem.corp.google.com (hpaq7.eem.corp.google.com [172.25.149.7]) by smtp-out.google.com with ESMTP id p6313bbe011187 for <ietf@ietf.org>; Sat, 2 Jul 2011 18:03:38 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1309655018; bh=LryEdj20RqyvNUT6d+2maFsjv9w=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=K0i8XSvzMh8eVEghX8RujhY2m4mTF/8dH7iORSJKSGntqCZamh+zb+Ft5uL9zQAV+ edLTqyjRoVdla2rmu7w+g==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type:x-system-of-record; b=nTN6IGf+jGEp+YQsszwXZsKYWngM4EPzQJXGA3CxHJQYdnaSQxGhEyUM1Cd7Gq2ve Adclhjsr9FixpNq1Yw4Jg==
Received: from gxk28 (gxk28.prod.google.com [10.202.11.28]) by hpaq7.eem.corp.google.com with ESMTP id p6313Z8v009124 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Sat, 2 Jul 2011 18:03:36 -0700
Received: by gxk28 with SMTP id 28so2598377gxk.27 for <ietf@ietf.org>; Sat, 02 Jul 2011 18:03:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=OfMW9y8g4+KdXIPqVEN7LiOXzg54dhcivmRYMK81yp0=; b=tomIPCBFbEQ+4gdqHWTZJYbUd7GjI6+VK62iKwk7S7xVLiIvhPs2lyt4fG4WHT7LjQ TVJRP8naI+ppgVg8lPhQ==
Received: by 10.150.61.21 with SMTP id j21mr3973922yba.378.1309655015353; Sat, 02 Jul 2011 18:03:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.157.14 with HTTP; Sat, 2 Jul 2011 18:03:15 -0700 (PDT)
In-Reply-To: <20110703100844.68eb8b7d@opy.nosense.org>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <20110703100844.68eb8b7d@opy.nosense.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sun, 3 Jul 2011 03:03:15 +0200
Message-ID: <CAKD1Yr05867hVEYKm9JpiXTcRhb38V=ViBm+VD-LU6vFn-7aEw@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Content-Type: multipart/alternative; boundary=000e0cd4b5d2f7ef2d04a71fd1a8
X-System-Of-Record: true
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:26 -0700
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 01:03:49 -0000

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

On Sun, Jul 3, 2011 at 2:38 AM, Mark Smith <
ipng@69706e6720323030352d30312d31340a.nosense.org> wrote:

> We know it can operate correctly and reliably if it
> is configured correctly.


... and in networks where there are public IP addresses and no firewalling,
and... etc. etc.

But we already had this discussion on v6ops, and since the consensus of the
WG was that the draft should be published, there's no point having it again.

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

<div class=3D"gmail_quote">On Sun, Jul 3, 2011 at 2:38 AM, Mark Smith <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:ipng@69706e6720323030352d30312d31340a.no=
sense.org">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;">We know it can operate correctly and reliab=
ly if it<br>
is configured correctly.</blockquote><div><br></div>... and in networks whe=
re there are public IP addresses and no firewalling, and... etc. etc.</div>=
<div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote">But we alre=
ady had this discussion on v6ops, and since the consensus of the WG was tha=
t the draft should be published, there&#39;s no point having it again.</div=
>


--000e0cd4b5d2f7ef2d04a71fd1a8--

From ek@google.com  Sat Jul  2 18:10:12 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 4DDFD21F851A for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 18:10:12 -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 4vtqM0MscHdZ for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 18:10:12 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id C925021F8514 for <ietf@ietf.org>; Sat,  2 Jul 2011 18:10:10 -0700 (PDT)
Received: from hpaq11.eem.corp.google.com (hpaq11.eem.corp.google.com [172.25.149.11]) by smtp-out.google.com with ESMTP id p631A6Kl019045 for <ietf@ietf.org>; Sat, 2 Jul 2011 18:10:06 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1309655406; bh=OaNIdD7RLY/s/nzS8KCAJJnKuK8=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=Qco9qFT88hSQpap5KwQaMEMBkU1Iha4gMGD/R8q5vV7Kwk3yuD0UMXGjHDeiq35uD cyooXvedOaWixVMfLlJuw==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:date: message-id:subject:from:to:cc:content-type:x-system-of-record; b=KYgTR9phkpJZwBeb5neDKUq89A8JtZfrdm2wVxHT7+bUog6zKPag5itex2LvpC/yo tNOlzh4DvVFnBXN3/ZpnA==
Received: from pvg3 (pvg3.prod.google.com [10.241.210.131]) by hpaq11.eem.corp.google.com with ESMTP id p631A46M024009 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <ietf@ietf.org>; Sat, 2 Jul 2011 18:10:05 -0700
Received: by pvg3 with SMTP id 3so4690466pvg.18 for <ietf@ietf.org>; Sat, 02 Jul 2011 18:10:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zIWEw0Ka1pq8K+2nDAQpwwFVcYfmad+NUMgS1ZUiW6I=; b=qUpUbmYqaZzcbrmAz+yye3NHHoUBKuiVrjzeOoBEyUmXs1mpHCnja8HkKKIrEnvGUe CRwPjvkG6TYKQXJ19n3g==
MIME-Version: 1.0
Received: by 10.142.121.15 with SMTP id t15mr2230844wfc.324.1309655403736; Sat, 02 Jul 2011 18:10:03 -0700 (PDT)
Received: by 10.142.179.17 with HTTP; Sat, 2 Jul 2011 18:10:03 -0700 (PDT)
In-Reply-To: <20110703100844.68eb8b7d@opy.nosense.org>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <20110703100844.68eb8b7d@opy.nosense.org>
Date: Sun, 3 Jul 2011 10:10:03 +0900
Message-ID: <CAAedzxpCsxW2zJtpGa9HRMRACkK1defrt2g2Xao_y0f7qevvkA@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
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: Tue, 05 Jul 2011 07:45:25 -0700
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 01:10:12 -0000

All,

> Perhaps declaring 6to4 deprecated rather than historic would have a
> better chance of consensus.

Pardon my ignorance, but where is the document describing the
implications of historic{,al} vs deprecated?

This (http://tools.ietf.org/html/rfc2026#section-4.2.4) is well known:

"""
   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.  (Purists have suggested that the
   word should be "Historical"; however, at this point the use of
   "Historic" is historical.)

   Note: Standards track specifications normally must not depend on
   other standards track specifications which are at a lower maturity
   level or on non standards track specifications other than referenced
   specifications from other standards bodies.  (See Section 7.)
"""

I don't know where similar explanatory language about "Deprecated"
might be (I'm sure I just didn't search correctly or long enough).

From lorenzo@google.com  Sat Jul  2 18:10:43 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 5E42021F8621 for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 18:10:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.376
X-Spam-Level: 
X-Spam-Status: No, score=-105.376 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 aHRrLnOmClrd for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 18:10: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 D25C121F8615 for <ietf@ietf.org>; Sat,  2 Jul 2011 18:10:37 -0700 (PDT)
Received: from wpaz1.hot.corp.google.com (wpaz1.hot.corp.google.com [172.24.198.65]) by smtp-out.google.com with ESMTP id p631AaEu009132 for <ietf@ietf.org>; Sat, 2 Jul 2011 18:10:36 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1309655437; bh=tC51SSlsa08/fg8IsM/Ckfnp2Tk=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=smCA6EgdXfFyPvXxfl5yrzrKD8IqWLWKesA4ey9EaKrnmULnZbUwf+1COzE2FtcGw zQZ+cdJDsVnGr9FDwisOg==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type:x-system-of-record; b=c7s6vGb3ZyWHxyvRqT806Icd58gPuBo1xOryzDMJtsMrsDy5a+/2hCwc1q0KJ2tRY ORBQg32/nvDxttSY3M55Q==
Received: from ywn13 (ywn13.prod.google.com [10.192.14.13]) by wpaz1.hot.corp.google.com with ESMTP id p631AZJl007923 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Sat, 2 Jul 2011 18:10:35 -0700
Received: by ywn13 with SMTP id 13so2067173ywn.7 for <ietf@ietf.org>; Sat, 02 Jul 2011 18:10:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=kVMhOhtA6nvvRqLlM+60LESlYV0TdqAap/xhFK//F4E=; b=u4uEIyFzWpGL6vtIRNo2a4XMYfNEvXaz31Qar9xkut9rEAzJHXmCER5b1gIN4rh+PQ GEU6texPNdly4Lo1973Q==
Received: by 10.150.183.3 with SMTP id g3mr4000949ybf.264.1309655435184; Sat, 02 Jul 2011 18:10:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.157.14 with HTTP; Sat, 2 Jul 2011 18:10:15 -0700 (PDT)
In-Reply-To: <DE414D2B-82ED-4C32-AFDF-EDAAB6D743B2@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <DE414D2B-82ED-4C32-AFDF-EDAAB6D743B2@network-heretics.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sun, 3 Jul 2011 03:10:15 +0200
Message-ID: <CAKD1Yr0=pJwOzRvTNskS7YDBNa7Fc=8srGzH2qJUKwGHdCAELg@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=000e0cd6ecd8fe0b5004a71fea11
X-System-Of-Record: true
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:26 -0700
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 01:10:43 -0000

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

On Sat, Jul 2, 2011 at 10:02 PM, Keith Moore <moore@network-heretics.com>wrote:

> > Is the reasoning behind the decision explained somewhere? My reading of
> the threads on the subject in v6ops was that the opposition to 6to4-historic
> was a small but vocal minority, and I thought that qualified as rough
> consensus.
>
> Even if there was rough consensus within v6ops, rough consensus of v6ops
> does not equate to rough consensus of the entire IETF community.
>

And who says that "rough consensus of the entire IETF community" is that
this draft should not be published? Were there public discussions to that
effect that came to this conclusion?

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

<div class=3D"gmail_quote">On Sat, Jul 2, 2011 at 10:02 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; Is the reasoning behind the decision explained somew=
here? My reading of the threads on the subject in v6ops was that the opposi=
tion to 6to4-historic was a small but vocal minority, and I thought that qu=
alified as rough consensus.<br>


<br>
</div>Even if there was rough consensus within v6ops, rough consensus of v6=
ops does not equate to rough consensus of the entire IETF community.<br></b=
lockquote><div><br></div><div>And who says that &quot;rough consensus of th=
e entire IETF community&quot;=A0is that this draft should not be published?=
 Were there public discussions to that effect that came to this conclusion?=
</div>

</div>

--000e0cd6ecd8fe0b5004a71fea11--

From randy@psg.com  Sat Jul  2 18:47:20 2011
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36B5D21F8674; Sat,  2 Jul 2011 18:47:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.572
X-Spam-Level: 
X-Spam-Status: No, score=-2.572 tagged_above=-999 required=5 tests=[AWL=0.027,  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 eeqjtgbyeGGt; Sat,  2 Jul 2011 18:47:19 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id A3F2321F8673; Sat,  2 Jul 2011 18:47:19 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76 (FreeBSD)) (envelope-from <randy@psg.com>) id 1QdBmF-000FMg-7I; Sun, 03 Jul 2011 01:47:15 +0000
Date: Sun, 03 Jul 2011 10:47:13 +0900
Message-ID: <m2oc1c9lum.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
In-Reply-To: <CAKD1Yr0=pJwOzRvTNskS7YDBNa7Fc=8srGzH2qJUKwGHdCAELg@mail.gmail.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <DE414D2B-82ED-4C32-AFDF-EDAAB6D743B2@network-heretics.com> <CAKD1Yr0=pJwOzRvTNskS7YDBNa7Fc=8srGzH2qJUKwGHdCAELg@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:25 -0700
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 01:47:20 -0000

> And who says that "rough consensus of the entire IETF community" is
> that this draft should not be published? Were there public discussions
> to that effect that came to this conclusion?

that is usually determined when the iesg last calls the document after
the wg has passed it to the iesg.

the ipv6 heads are amazingly immune to reality.

6to4 has been measured and clearly demonstrated to have failed in the
field.  yes, it could work.  but it doesn't.  we need to get over it.

randy

From ek@google.com  Sat Jul  2 19:00:41 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 27D5411E8085 for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 19:00:41 -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 V6Qgfu2HbPoy for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 19:00:40 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id 64CDF1F0C36 for <ietf@ietf.org>; Sat,  2 Jul 2011 19:00:40 -0700 (PDT)
Received: from hpaq1.eem.corp.google.com (hpaq1.eem.corp.google.com [172.25.149.1]) by smtp-out.google.com with ESMTP id p6320dW0029913 for <ietf@ietf.org>; Sat, 2 Jul 2011 19:00:39 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1309658439; bh=RHYbPHLdiRpmSUib6HEkRsyXkxI=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=lnXlJLpFkNDAFX17434lmTLhHfcfgznkEACmMjmcG3AOEjiq6FEq2tF22JfgiuOir GLt27Xbif0BZVXCQaQB5w==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:date: message-id:subject:from:to:cc:content-type: content-transfer-encoding:x-system-of-record; b=TtGloGCxujR/tYVRtkUCPZm7b/LYaowL83t9mQbErpHCaUVMvGNCdaVCEdov+JITw Lysdhj4mzcZzu1MMjeY9g==
Received: from pvg13 (pvg13.prod.google.com [10.241.210.141]) by hpaq1.eem.corp.google.com with ESMTP id p6320ORJ031769 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Sat, 2 Jul 2011 19:00:37 -0700
Received: by pvg13 with SMTP id 13so5083716pvg.12 for <ietf@ietf.org>; Sat, 02 Jul 2011 19:00:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=+LWpW1yNEPfYSUd+y7it3jBW8fRPZxJa7WJa+kkWGak=; b=vw7iJgGYzOXKeMCigggStEPB68dD/SXIfb2Tw8UwMLvdxYNdefHD53uvNVmvo3XjZi XeH8APx3KRuuvSNKOzlw==
MIME-Version: 1.0
Received: by 10.142.128.1 with SMTP id a1mr2159780wfd.438.1309658437337; Sat, 02 Jul 2011 19:00:37 -0700 (PDT)
Received: by 10.142.179.17 with HTTP; Sat, 2 Jul 2011 19:00:37 -0700 (PDT)
In-Reply-To: <20110703112420.3fcaa58c@opy.nosense.org>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <20110703100844.68eb8b7d@opy.nosense.org> <CAAedzxpCsxW2zJtpGa9HRMRACkK1defrt2g2Xao_y0f7qevvkA@mail.gmail.com> <20110703112420.3fcaa58c@opy.nosense.org>
Date: Sun, 3 Jul 2011 11:00:37 +0900
Message-ID: <CAAedzxoFxM--XmLsATcwQiBjOoo_O5n4zcN4E02QSpY2NCOjwA@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
From: Erik Kline <ek@google.com>
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:25 -0700
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 02:00:41 -0000

>> > Perhaps declaring 6to4 deprecated rather than historic would have a
>> > better chance of consensus.
>>
>> Pardon my ignorance, but where is the document describing the
>> implications of historic{,al} vs deprecated?
>>
>> This (http://tools.ietf.org/html/rfc2026#section-4.2.4) is well known:
>>
>> """
>> =C2=A0 =C2=A0A specification that has been superseded by a more recent
>> =C2=A0 =C2=A0specification or is for any other reason considered to be o=
bsolete is
>> =C2=A0 =C2=A0assigned to the "Historic" level. =C2=A0(Purists have sugge=
sted that the
>> =C2=A0 =C2=A0word should be "Historical"; however, at this point the use=
 of
>> =C2=A0 =C2=A0"Historic" is historical.)
>>
>> =C2=A0 =C2=A0Note: Standards track specifications normally must not depe=
nd on
>> =C2=A0 =C2=A0other standards track specifications which are at a lower m=
aturity
>> =C2=A0 =C2=A0level or on non standards track specifications other than r=
eferenced
>> =C2=A0 =C2=A0specifications from other standards bodies. =C2=A0(See Sect=
ion 7.)
>> """
>>
>> I don't know where similar explanatory language about "Deprecated"
>> might be (I'm sure I just didn't search correctly or long enough).
>
> Since 6rd depends on 6to4, as it is a variant of it, would 6to4 being
> declared historic also mean that 6rd needs to become historic as well?

http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05
Section 1, in which the draft clarifies that 6rd supersedes 6to4,
which meets the qualification in the first paragraph of the "Historic"
term.  With 6rd we clearly don't need to have anything built on top of
6to4 in the future, addressing the 2nd paragraph.

From frnkblk@iname.com  Sat Jul  2 19:27:31 2011
Return-Path: <frnkblk@iname.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B3771F0C58; Sat,  2 Jul 2011 19:27:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level: 
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ViYyfHk7VeOg; Sat,  2 Jul 2011 19:27:30 -0700 (PDT)
Received: from premieronline.net (smtp1-1.premieronline.net [96.31.0.21]) by ietfa.amsl.com (Postfix) with ESMTP id 2EB5F1F0C51; Sat,  2 Jul 2011 19:27:30 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=199.120.69.26; 
Received: from BULKFAMLAPTOP (unverified [199.120.69.26])  by premieronline.net (SurgeMail 5.0n) with ESMTP id 28002088-1729245  for multiple; Sat, 02 Jul 2011 21:27:29 -0500
From: "Frank Bulk" <frnkblk@iname.com>
To: "'Keith Moore'" <moore@network-heretics.com>, <robert@raszuk.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net>	<CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com>	<DE414D2B-82ED-4C32-AFDF-EDAAB6D743B2@network-heretics.com>	<4E0F7E12.8060901@raszuk.net> <3D17B847-7424-4A31-8072-761DDFDCA5B1@network-heretics.com>
In-Reply-To: <3D17B847-7424-4A31-8072-761DDFDCA5B1@network-heretics.com>
Subject: RE: [v6ops] draft-ietf-v6ops-6to4-to-historic
Date: Sat, 2 Jul 2011 21:27:21 -0500
Message-ID: <000901cc3928$bcecc390$36c64ab0$@iname.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Acw49ktlhIzQhtzbRsGEtIMtvA8XQgAMOZyg
Content-Language: en-us
X-Authenticated-User: fbulk@premieronline.net 
X-SpamDetect: : 0.000000 
X-Info: aspam skipped due to (useraccess)
X-MyRbl: Color=Yellow Age=0 Spam=0 Notspam=0 Stars=0 Good=0 Friend=278 Surbl=0 Catch=0 r=0 ip=199.120.69.26
X-IP-stats: Incoming Outgoing Last 0, First 847, in=13000838, out=61735, spam=0 Known=true ip=199.120.69.26
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:26 -0700
Cc: v6ops@ietf.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: frnkblk@iname.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jul 2011 02:27:31 -0000

Yes, the Linksys E2000, E3000, E4200, WRT610N, and a small batch of Apple
Airports had 6to4 on by default, but the latest firmware versions turn that
off.  

Frank

-----Original Message-----
From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of
Keith Moore
Sent: Saturday, July 02, 2011 3:26 PM
To: robert@raszuk.net
Cc: v6ops@ietf.org; IETF Discussion
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic

On Jul 2, 2011, at 4:22 PM, Robert Raszuk wrote:

> Hi Keith,
> 
>> I personally don't have any objection to the notion that 6to4 should
>> be off by default and should require explicit configuration to enable
>> it.
> 
> Is there any feature (perhaps other then netboot) on commercial or open
source routers which is not off by default and which would require explicit
configuration to enable it ?

I have understood that in the past there were a few routers that enabled
6to4 by default, though I don't know whether this is the case any longer.   
I also believe that there are currently hosts that enable 6to4 by default if
there is no native v6 connectivity and the host has a public IPv4 address.

Keith

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


From randy@psg.com  Sat Jul  2 22:06:42 2011
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5774021F8734; Sat,  2 Jul 2011 22:06:42 -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 oVrOghwHmuaX; Sat,  2 Jul 2011 22:06:41 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id B10FD21F8733; Sat,  2 Jul 2011 22:06:41 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76 (FreeBSD)) (envelope-from <randy@psg.com>) id 1QdEtC-000Foo-0O; Sun, 03 Jul 2011 05:06:38 +0000
Date: Sun, 03 Jul 2011 14:06:36 +0900
Message-ID: <m2mxgw9cmb.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ronald Bonica <rbonica@juniper.net>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F3507F14@EMBX01-WF.jnpr.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <m2y60g9xiw.wl%randy@psg.com> <13205C286662DE4387D9AF3AC30EF456D3F3507F14@EMBX01-WF.jnpr.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:25 -0700
Cc: IPv6 Ops 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: Sun, 03 Jul 2011 05:06:42 -0000

> 1) "as measured on the real internet, not the ietf bar, 6to4 sucks caterpillar snot"
> 2) "perhaps that minority was also vocal in the back room"
> 3) "yes, but that will be a year from now.  in the ietf, delay is one form of death"
> 
> Responses follow:
> 
> 1) While not stated so colorfully, draft-ietf-v6ops-6to4-advisory made
>    this point. It has been approved for publication. 

but then do we not draw the conclusion that therefore publishing
draft-ietf-v6ops-6to4-to-disgusting is the correct approach?

> 2) While there was no back-room activity, an appeal had been filed at
>    the WG level. Since WG consensus was stronger than IETF consensus,
>    it is reasonable to assume that the appeal would be escalated to
>    the IESG level if it was not approved at the WG level.

so these days people who do not get their way use the nuclear option?
we raised kids.  when those tactics resulted in "we are so sorry you do
not like the result, but that's the result" they soon stopped.

> So, any way you look at it, there would be delays.

welcome to the ietf, where process is our most important product.

> 3) The new document may not take a year to publish. Since it is a
>    short draft, it could be produced in a few days. Once it is
>    produced, we could immediately initiate a WG last call and an IETF
>    last call immediately after that. So, we might be talking about a
>    six-week delay.

so process this one in six weeks, please.

> Now, I have a question for you, Lorenzo and Doug. If our goal is to
> take 6-to-4 off of the Internet, does not disabling it by default
> solve most of the problem? AFAIKS, very few users would enable it and
> service providers would not be economically incented to support 6-to-4
> relay routers.

the economic incentive to half-assed service providers is that it gives
an excuse not to deploy ipv6.  the response of these folk will be web
pages instructing their users how to turn 6to4 on.

randy

From lorenzo@google.com  Sat Jul  2 22:23:28 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 8ADF121F8754 for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 22:23:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.676
X-Spam-Level: 
X-Spam-Status: No, score=-105.676 tagged_above=-999 required=5 tests=[AWL=0.300, 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 lW0jkWgo46iY for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 22:23: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 6034721F8757 for <ietf@ietf.org>; Sat,  2 Jul 2011 22:23:26 -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 p635NPA0004129 for <ietf@ietf.org>; Sat, 2 Jul 2011 22:23:25 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1309670606; bh=UGT2guVZNqhexTwrCs2UMMhXdMQ=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=hSBEFyfTgCjVeGSHXYsaK6iqzrr1smW/rBdYDTZCjshdeyacU8Iqn7fRDq/emM16t rANN7ESzK/89k7MV7ZjUA==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type:x-system-of-record; b=JTb2piv+k8e8HOfDShqnBWd2Nsmr7WGbyfGtlVXN6gjIm2WpgItnWZMzt1WFgOSio QmiMW4T6q6vA4xJ5Zc3tg==
Received: from yia27 (yia27.prod.google.com [10.243.65.27]) by wpaz21.hot.corp.google.com with ESMTP id p635NOu4001675 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Sat, 2 Jul 2011 22:23:24 -0700
Received: by yia27 with SMTP id 27so2230577yia.33 for <ietf@ietf.org>; Sat, 02 Jul 2011 22:23:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=RQetuOXemeZzQdy6ZMqJM/Kp24eTJGaOBKdf4TAfxaY=; b=pVGQVr6xlRut7D8ta3dIdN2PTEd+bIz5jYpwQ8qf9OlXso7FWPLO2JaZ+v1kI/WGj5 ggHLsbOpE0bFPPx5/KEw==
Received: by 10.151.21.20 with SMTP id y20mr4364696ybi.150.1309670604223; Sat, 02 Jul 2011 22:23:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.157.14 with HTTP; Sat, 2 Jul 2011 22:23:03 -0700 (PDT)
In-Reply-To: <20110703030548.7BF9618C1BA@mercury.lcs.mit.edu>
References: <20110703030548.7BF9618C1BA@mercury.lcs.mit.edu>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sun, 3 Jul 2011 07:23:03 +0200
Message-ID: <CAKD1Yr232NFv=bss_+S-FUGY4m3vghg3bCbeFU0YuT0+uC0j1A@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Content-Type: multipart/alternative; boundary=000e0cd4b31e2335e704a7237362
X-System-Of-Record: true
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:26 -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: Sun, 03 Jul 2011 05:23:28 -0000

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

On Sun, Jul 3, 2011 at 5:05 AM, Noel Chiappa <jnc@mercury.lcs.mit.edu>wrote:

> I think there is pretty much complete consensus that i) 6to4 doesn't work
> in several very common environments (behind a NAT, etc, etc), and that
> therefore, ii) at the very least, it should be disabled by default (and
> therefore only turned on by knowledgeable users who know they are not in
> one of those situations).
>
> Given and assuming a document that makes all that formal, _what else_ does
> the _additional_ step of making 6to4 historic buy?
>

Compared to the alternative of publishing 6to4-historic now, it:

a) Delays the time of any statement made by the IETF on the question by at
least a number of months, while vendors and home gateways are *still
shipping* products that implement 6to4 and enable it by default. I have
personally seen this in beta home gateway products with "new IPv6 firmware"
that aren't even released yet.
b) Even assuming it were to gain consensus in any sort of reasonable
timescale, it would provide a less clear statement, and thus be less of an
incentive for implementors such as home gateway manufacturers to do the
right thing and remove it. We have heard in the working group from real
implementors like Apple, who have said that even 6to4-historic may not go
far enough for them to justify actions such as removing support from their
products. We have heard, also, that when implementors such as home gateway
manufacturers are asked to remove 6to4 or disable it because it harms user
experience, they say that they don't see why they should do work to remove a
feature, in the absence of any guidance from the IETF.

Time is important, because over time, 6to4's reliability will get worse, not
better, as ISPs do things like use bogon IPv4 space plus carrier-grade NAT
for their users, because implementations will think they have public IPv4
addresses and thus turn on 6to4 (which will never work, because it's behind
a NAT).

Or perhaps the concept is that nuking 6to4 will help force ISPs to deploy
> native IPv6, since it removes one way for users to get IPv6 if their
> provider doesn't supply it? If so, why not ditch Teredo, too? (Not to
> mention that 'mandate it and they will come' hasn't worked to well so far.)
>

Normal users will not get IPv6 unless their ISP gives it to them. Period,
end of story. I think it's clear by now that the vast majority of users
don't know what IPv6 is, and that they do not ask for it. For a normal user,
having 6to4 is more a liability than an asset. Normal users don't rely on
6to4 to give them IPv6 connectivity, because they don't use or need IPv6;
everything they do today can be done with higher performance and higher
reliability using IPv4 and NAT traversal. However, if they get it "for free"
in the form of 6to4, then far from gaining a benefit (reliable IPv6
connectivity), they get something that only works 80% of the time, and 20%
of the time breaks dual-stack websites.

By "users" I explicitly do not include the tiny percentage of users on this
list who are technical enough to know that 6to4 exists and rely on it to get
IPv6 connectivity. Compared to the overwhelming number of users who have no
idea what IPv6 even is, they are so far away from the mainstream that they
don't matter at all, and they are knowledgeable enough to deploy other
solutions, such as managed tunnels, which in my experience are typically
lower latency and higher reliability (pretty much everything is higher
reliability than a 20% failure rate).

The only way you can incentivize ISPs to deploy IPv6 is to provide IPv6
content that they can use to justify the investment (for example, reduce the
load on the NATs that they will be deploying). ISPs have been saying for
years, and are still saying, that one of the reasons tha they are not
deploying IPv6 because there is no point, since so little content is
available over IPv6. Now we are hearing clearly from content providers that
they *do not want* 6to4, because its 80% failure rate is a concern for them,
and that in fact, its existence is one of the major barriers to lack of
adoption on the part of content providers.

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

<div class=3D"gmail_quote">On Sun, Jul 3, 2011 at 5:05 AM, Noel Chiappa <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:jnc@mercury.lcs.mit.edu">jnc@mercury.l=
cs.mit.edu</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

I think there is pretty much complete consensus that i) 6to4 doesn&#39;t wo=
rk<br>
in several very common environments (behind a NAT, etc, etc), and that<br>
therefore, ii) at the very least, it should be disabled by default (and<br>
therefore only turned on by knowledgeable users who know they are not in<br=
>
one of those situations).<br>
<br>
Given and assuming a document that makes all that formal, _what else_ does<=
br>
the _additional_ step of making 6to4 historic buy?<br></blockquote><div><br=
></div><div>Compared to the alternative of publishing 6to4-historic now, it=
:</div><div><br></div><div>a) Delays the time of any statement made by the =
IETF on the question by at least a number of months, while vendors and home=
 gateways are *still shipping* products that implement 6to4 and enable it b=
y default. I have personally seen this in beta home gateway products with &=
quot;new IPv6 firmware&quot; that aren&#39;t even released yet.</div>

<div>b) Even assuming it were to gain consensus in any sort of reasonable t=
imescale, it would provide a less clear statement, and thus be less of an i=
ncentive for implementors such as home gateway manufacturers to do the righ=
t thing and remove it. We have heard in the working group from real impleme=
ntors like Apple, who have said that even 6to4-historic may not go far enou=
gh for them to justify actions such as removing support from their products=
.=A0We have heard, also, that when implementors such as home gateway manufa=
cturers are asked to remove 6to4 or disable it because it harms user experi=
ence, they say that they don&#39;t see why they should do work to remove a =
feature, in the absence of any guidance from the IETF.</div>

<div><br></div><div>Time is important, because over time, 6to4&#39;s reliab=
ility will get worse, not better, as ISPs do things like use bogon IPv4 spa=
ce plus carrier-grade NAT for their users, because implementations will thi=
nk they have public IPv4 addresses and thus turn on 6to4 (which will never =
work, because it&#39;s behind a NAT).</div>

<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex;">Or perhaps the concept is th=
at nuking 6to4 will help force ISPs to deploy<br>
native IPv6, since it removes one way for users to get IPv6 if their<br>
provider doesn&#39;t supply it? If so, why not ditch Teredo, too? (Not to<b=
r>
mention that &#39;mandate it and they will come&#39; hasn&#39;t worked to w=
ell so far.)<br></blockquote><div><br></div><div>Normal users will not get =
IPv6 unless their ISP gives it to them. Period, end of story. I think it&#3=
9;s clear by now that the vast majority of users don&#39;t know what IPv6 i=
s, and that they do not ask for it. For a normal user, having 6to4 is more =
a liability than an asset. Normal users don&#39;t rely on 6to4 to give them=
 IPv6 connectivity, because they don&#39;t use or need IPv6; everything the=
y do today can be done with higher performance and higher reliability using=
 IPv4 and NAT traversal. However, if they get it &quot;for free&quot; in th=
e form of 6to4, then far from gaining a benefit (reliable IPv6 connectivity=
), they get something that only works 80% of the time, and 20% of the time =
breaks dual-stack websites.</div>

<div><br></div><div>By &quot;users&quot; I explicitly do not include the ti=
ny percentage of users on this list who are technical enough to know that 6=
to4 exists and rely on it to get IPv6 connectivity. Compared to the overwhe=
lming number of users who have no idea what IPv6 even is, they are so far a=
way from the mainstream that they don&#39;t matter at all, and they are kno=
wledgeable enough to deploy other solutions, such as managed tunnels, which=
 in my experience are typically lower latency and higher reliability (prett=
y much everything is higher reliability than a 20% failure rate).</div>

<div><br></div><div>The only way you can incentivize ISPs to deploy IPv6 is=
 to provide IPv6 content that they can use to justify the investment (for e=
xample, reduce the load on the NATs that they will be deploying). ISPs have=
 been saying for years, and are still saying, that one of the reasons tha t=
hey are not deploying IPv6 because there is no point, since so little conte=
nt is available over IPv6. Now we are hearing clearly from content provider=
s that they *do not want* 6to4, because its 80% failure rate is a concern f=
or them, and that in fact, its existence is one of the major barriers to la=
ck of adoption on the part of content providers.</div>

</div>

--000e0cd4b31e2335e704a7237362--

From lorenzo@google.com  Sat Jul  2 22:29:33 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 8DE2E21F8703 for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 22:29:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.376
X-Spam-Level: 
X-Spam-Status: No, score=-105.376 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 HHePg7khmkYw for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 22:29:33 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id 139B521F8739 for <ietf@ietf.org>; Sat,  2 Jul 2011 22:29:32 -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 p635TWrk000521 for <ietf@ietf.org>; Sat, 2 Jul 2011 22:29:32 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1309670972; bh=G14LFzpNITRh1GPgoeJ61vJbOrQ=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=kRfcifDFCy7Qyo+PSaRZWVHvj02UWtLNM32O4ujY1e1CGfkY68IXs1GwGMU/NAsr7 8vWFo9eZ/5DZRDguUBtPA==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type:x-system-of-record; b=SmG/klzHM2RclTye6jyDGI1jxXkQwC/hHuCOqo8gQdO/AWwdzv4vv5pHc7WH/OkIZ DT5+eqQztmK44Cof/H3xw==
Received: from gxk2 (gxk2.prod.google.com [10.202.11.2]) by hpaq12.eem.corp.google.com with ESMTP id p635TUDZ000621 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Sat, 2 Jul 2011 22:29:31 -0700
Received: by gxk2 with SMTP id 2so2785037gxk.22 for <ietf@ietf.org>; Sat, 02 Jul 2011 22:29:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Bt9XrncfUjxvoxMvUytd7YypN0QAVMBKjJqU/6QhfvI=; b=eaxHEcZrYC5stync2D3D1EwgjHaah/DGRfnA5Qr4G4+e5xl3wRNAYFAn2XNeMqa73I LudQSw7huQqpgIEFUknw==
Received: by 10.150.183.3 with SMTP id g3mr4067930ybf.264.1309670970151; Sat, 02 Jul 2011 22:29:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.157.14 with HTTP; Sat, 2 Jul 2011 22:29:10 -0700 (PDT)
In-Reply-To: <A1DA82E2-B979-4719-9F78-DEB263B256A1@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <DE414D2B-82ED-4C32-AFDF-EDAAB6D743B2@network-heretics.com> <CAKD1Yr0=pJwOzRvTNskS7YDBNa7Fc=8srGzH2qJUKwGHdCAELg@mail.gmail.com> <A1DA82E2-B979-4719-9F78-DEB263B256A1@network-heretics.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sun, 3 Jul 2011 07:29:10 +0200
Message-ID: <CAKD1Yr34UZO7jRAy8hL9uKW2yJ5dDuvOCzrQJ7zn9MmBTovnCg@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=000e0cd6ecd8f2d45704a723883b
X-System-Of-Record: true
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:26 -0700
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 05:29:33 -0000

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

On Sun, Jul 3, 2011 at 5:11 AM, Keith Moore <moore@network-heretics.com>wrote:

> And who says that "rough consensus of the entire IETF community" is that
> this draft should not be published? Were there public discussions to that
> effect that came to this conclusion?
>
> There's clearly a lack of consensus to support it.
>

Nope. The v6ops chairs saw consensus in v6ops to support it. Can you point
to significant strength of opinion of the wider IETF community, but not in
v6ops, that has reason to oppose it? If all you can point to is the same
people that were opposing it in v6ops, then I think they don't count,
because the rough consensus in v6ops was that the document should be
published.

So, I ask again: where are the statements made in opposition of this
proposal made outside of v6ops? Can you point to them?

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

<div class=3D"gmail_quote">On Sun, Jul 3, 2011 at 5:11 AM, 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><div></div><div class=3D"h5"><div>=
<blockquote type=3D"cite"><div class=3D"gmail_quote"><div>And who says that=
 &quot;rough consensus of the entire IETF community&quot;=A0is that this dr=
aft should not be published? Were there public discussions to that effect t=
hat came to this conclusion?</div>

</div></blockquote></div></div></div><div>There&#39;s clearly a lack of con=
sensus to support it.</div></div></blockquote><div><br></div><div>Nope. The=
 v6ops chairs saw consensus in v6ops to support it. Can you point to signif=
icant strength of opinion of the wider IETF community, but not in v6ops, th=
at has reason to oppose it? If all you can point to is the same people that=
 were opposing it in v6ops, then I think they don&#39;t count, because the =
rough consensus in v6ops was that the document should be published.</div>

<div><br></div><div>So, I ask again: where are the statements made in oppos=
ition of this proposal made outside of v6ops? Can you point to them?</div><=
/div>

--000e0cd6ecd8f2d45704a723883b--

From lorenzo@google.com  Sat Jul  2 22:54:10 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 8520221F8741 for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 22:54:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.826
X-Spam-Level: 
X-Spam-Status: No, score=-105.826 tagged_above=-999 required=5 tests=[AWL=0.150, 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 5qnH6BhmLGJa for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 22:54:10 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id 980AC21F874E for <ietf@ietf.org>; Sat,  2 Jul 2011 22:54:09 -0700 (PDT)
Received: from wpaz5.hot.corp.google.com (wpaz5.hot.corp.google.com [172.24.198.69]) by smtp-out.google.com with ESMTP id p635s75l012399 for <ietf@ietf.org>; Sat, 2 Jul 2011 22:54:08 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1309672448; bh=lrBnYxKWUAOOGV0P9mdsVLu/gsQ=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=sUqKr1e9xwbpZWZaj6crwPBTgB/EMPkW2ODWjaIrX4B55SBhsvWIbXuRkBoBjrjHt oKuImw2G9XbTyzCp4DAug==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type:x-system-of-record; b=G9Z5XwVqdZ4vcDnas0A9VnO2fxA7kuPEN8ngX34fpz0eE2x17YpocjQKzHG9rguPd +OiQjTvaIUnU+4h5oSIBw==
Received: from yib18 (yib18.prod.google.com [10.243.65.82]) by wpaz5.hot.corp.google.com with ESMTP id p635s6PP019339 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Sat, 2 Jul 2011 22:54:06 -0700
Received: by yib18 with SMTP id 18so2029766yib.20 for <ietf@ietf.org>; Sat, 02 Jul 2011 22:54:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=YUajFiSWCVNNPgE/+ZBgOp5wHLI32mFqQyuIQaOZN/0=; b=bGrVPrAxlPXMCWseVoCYM0d2HQgM5Qtdtx3EPJzdpT7X93MkJp9h7Yxbv1U10j8wut LtbPEuMUGxmLq8a15c+w==
Received: by 10.151.21.20 with SMTP id y20mr4372922ybi.150.1309672446234; Sat, 02 Jul 2011 22:54:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.157.14 with HTTP; Sat, 2 Jul 2011 22:53:46 -0700 (PDT)
In-Reply-To: <20110703131913.28142ec0@opy.nosense.org>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com> <20110703112048.4a3c7111@opy.nosense.org> <4E0FD788.3000305@dougbarton.us> <20110703131913.28142ec0@opy.nosense.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sun, 3 Jul 2011 07:53:46 +0200
Message-ID: <CAKD1Yr0dU8xGPc5tY8qK7w7Vc57zzj2BBipCb3b3VsXLov-JUw@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Content-Type: multipart/alternative; boundary=000e0cd4b31eee12e904a723e025
X-System-Of-Record: true
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:26 -0700
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 05:54:10 -0000

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

On Sun, Jul 3, 2011 at 5:49 AM, Mark Smith <
ipng@69706e6720323030352d30312d31340a.nosense.org> wrote:

> Declaring 6to4 to be historic might encourage native IPv6 deployment,
> but I think it will also make trialing IPv6 much harder.
>

We don't need to trial the IPv6 protocol. There are hundreds of thousands of
native users accessing production-grade IPv6 services, like Google's, every
day. We know the IPv6 protocol works. ISPs do need to trial IPv6 deployment.
But 6to4 does not help there, because 6to4 is not deployed by ISPs. They
will need to trial native deployments, or 6rd. If *users* want to trial IPv6
until native IPv6 is available, then they can use configured tunnels.


> The involvement in World IPv6 day by large content providers and the
> apparent lack of significant problems would be suggest the opposite is
> now the case. Google continuing to provide youtube video content to 6to4
> tunnel users (such as myself), nearly a month later, suggests that any
> problems with it are tractable.


I would assert that the problems with 6to4 are not tractable without
disabling 6to4. Our IPv6 brokenness statistics for before and after World
IPv6 Day are very similar.


> 6to4 users are easy to spot by the 2002::/16 prefix, so if Google needed to
> they could probably quite easily limit their IPv6 content delivery to native
> only IPv6 users.


No, that's not how it works. There is no problem with 6to4 when it works as
well as IPv4. The problem is that 6to4 only works *at all* (never mind works
"as well as IPv4") 80% of the time.

Unfortunately, in the 20% of the time that it's not working, Google has no
idea that the user has a 2002::/16 address. Google only knows, after the
fact, that the user suffered a 20 or 75-second timeout and was not happy. So
it would serve no purpose to avoid serving users that successfully connect
from 2002::/16 addresses; once the AAAA record is handed out, the damage is
done. What Google could do, however, is stop handing out AAAA records to
networks that have significant number of 6to4 users in the future. We're
considering this.

An update on that data would be useful.
>

As I said before, our data on IPv6 brokenness did not change significantly
after World IPv6 Day. Can you take that as a proxy that 6to4 has not
improved?

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

<div class=3D"gmail_quote">On Sun, Jul 3, 2011 at 5:49 AM, Mark Smith <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:ipng@69706e6720323030352d30312d31340a.no=
sense.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>Declaring 6to4 to be historic might enc=
ourage native IPv6 deployment,</div>
but I think it will also make trialing IPv6 much harder.<br></blockquote><d=
iv><br></div><div>We don&#39;t need to trial the IPv6 protocol. There are h=
undreds of thousands of native users accessing production-grade IPv6 servic=
es, like Google&#39;s, every day. We know the IPv6 protocol works.=A0ISPs d=
o need to trial IPv6 deployment. But 6to4 does not help there, because 6to4=
 is not deployed by ISPs. They will need to trial native deployments, or 6r=
d.=A0If *users* want to trial IPv6 until native IPv6 is available, then the=
y can 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>The involvement in World IPv6 day by large content providers and the</=
div>
apparent lack of significant problems would be suggest the opposite is<br>
now the case. Google continuing to provide youtube video content to 6to4<br=
>
tunnel users (such as myself), nearly a month later, suggests that any<br>
problems with it are tractable.</blockquote><div><br></div><div>I would ass=
ert that the problems with 6to4 are not tractable without disabling 6to4. O=
ur IPv6 brokenness statistics for before and after World IPv6 Day are very =
similar.</div>


<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">6to4 users are easy to spot by=
 the=A02002::/16 prefix, so if Google needed to they could probably quite=
=A0easily limit their IPv6 content delivery to native only IPv6 users.</blo=
ckquote>


<div><br></div><div>No, that&#39;s not how it works. There is no problem wi=
th 6to4 when it works as well as IPv4. The problem is that 6to4 only works =
*at all* (never mind works &quot;as well as IPv4&quot;) 80% of the time.</d=
iv>

<div><br></div><div>Unfortunately, in the 20% of the time that it&#39;s not=
 working, Google has no idea that the user has a 2002::/16 address. Google =
only knows, after the fact, that the user suffered a 20 or 75-second timeou=
t and was not happy. So it would serve no purpose to avoid serving users th=
at successfully connect from 2002::/16 addresses; once the AAAA record is h=
anded out, the damage is done. What Google could do, however, is stop handi=
ng out AAAA records to networks that have significant number of 6to4 users =
in the future. We&#39;re considering this.</div>


<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">An=A0update on that data woul=
d be useful.<br></blockquote><div><br></div><div>As I said before, our data=
 on IPv6 brokenness did not change significantly after World IPv6 Day. Can =
you take that as a proxy that 6to4 has not improved?</div>


</div>

--000e0cd4b31eee12e904a723e025--

From lorenzo@google.com  Sat Jul  2 22:59:22 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 253F921F865F for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 22:59:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.864
X-Spam-Level: 
X-Spam-Status: No, score=-105.864 tagged_above=-999 required=5 tests=[AWL=0.112, 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 jxQZJpMvYlJt for <ietf@ietfa.amsl.com>; Sat,  2 Jul 2011 22:59:21 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id 5D89D21F8661 for <ietf@ietf.org>; Sat,  2 Jul 2011 22:59:21 -0700 (PDT)
Received: from kpbe14.cbf.corp.google.com (kpbe14.cbf.corp.google.com [172.25.105.78]) by smtp-out.google.com with ESMTP id p635xJg9012355 for <ietf@ietf.org>; Sat, 2 Jul 2011 22:59:20 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1309672760; bh=qUkxC99frbwGJwhukAiAmrXStjA=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=bQptOfllxZbiel3jFYvTVolRKU0Yb1tS4tt5SiWu3M3U74ihq9NAeqZ+yAxxf/29W UQpK+1Ebj9JAPrLnhZimQ==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type:x-system-of-record; b=sSTcQ2N7cwoHRlLnQ2pziAPU6qmFCAbNz/v/56VBSR1g+rcijltxERMseY9sqEjeN OWBSkdyj8R4QF0DYpQg9g==
Received: from gxk27 (gxk27.prod.google.com [10.202.11.27]) by kpbe14.cbf.corp.google.com with ESMTP id p635xISN014700 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Sat, 2 Jul 2011 22:59:18 -0700
Received: by gxk27 with SMTP id 27so1989425gxk.29 for <ietf@ietf.org>; Sat, 02 Jul 2011 22:59:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=16bmiS/mHyMG0vOZYq3YEBvePs3ZmoBLGG0y+8kcPcI=; b=I9KUi74piJqG8/RetFlJImD8DW0hsEtuJ6tCshLCJQ/fAONYckW8JkGWECfd1Z+QdJ uwDrBr6nTERLTmcBSloA==
Received: by 10.151.24.10 with SMTP id b10mr4179543ybj.93.1309672758195; Sat, 02 Jul 2011 22:59:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.157.14 with HTTP; Sat, 2 Jul 2011 22:58:58 -0700 (PDT)
In-Reply-To: <20110703100844.68eb8b7d@opy.nosense.org>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <20110703100844.68eb8b7d@opy.nosense.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sun, 3 Jul 2011 07:58:58 +0200
Message-ID: <CAKD1Yr1qN6qjEMNq7GDNoX8UifDpxHBcMLYUVwmCWQG=JFyVvQ@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Content-Type: multipart/alternative; boundary=000e0cd23ef68634c004a723f393
X-System-Of-Record: true
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:26 -0700
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 05:59:22 -0000

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

On Sun, Jul 3, 2011 at 2:38 AM, Mark Smith <
ipng@69706e6720323030352d30312d31340a.nosense.org> wrote:

> I don't object to what has been proposed, yet I object to
> "6to4-historic" because I'm an extremely happy anycast 6to4 user


"It works for me, so there's obviously no problem". When you think of
6to4-historic, please think of the 20% of anycast 6to4 users that are
broken.

We know it can operate correctly and reliably if it is configured correctly.


But we also know that it's not configured correctly, to such an extent that
it does not work at all in 20% of cases (Geoff's data). And we know of no
reason why that would improve, though we do know of reasons why it would get
worse (e.g., due to ISPs giving bogon public space to their users).

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

<div class=3D"gmail_quote">On Sun, Jul 3, 2011 at 2:38 AM, Mark Smith <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:ipng@69706e6720323030352d30312d31340a.no=
sense.org">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;">I don&#39;t object to what has been propose=
d, yet I object to<br>
&quot;6to4-historic&quot; because I&#39;m an extremely happy anycast 6to4 u=
ser</blockquote><div><br></div><div>&quot;It works for me, so there&#39;s o=
bviously no problem&quot;. When you think of 6to4-historic, please think of=
 the 20% of anycast 6to4 users that are broken.</div>

<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex;">We know it can operate corre=
ctly and reliably if it=A0is configured correctly.</blockquote><div><br></d=
iv>

<div>But we also know that it&#39;s not configured correctly, to such an ex=
tent that it does not work at all in 20% of cases (Geoff&#39;s data). And w=
e know of no reason why that would improve, though we do know of reasons wh=
y it would get worse (e.g., due to ISPs giving bogon public space to their =
users).</div>

</div>

--000e0cd23ef68634c004a723f393--

From v6ops@globis.net  Sat Jul  2 23:23:45 2011
Return-Path: <v6ops@globis.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A85A421F8775; Sat,  2 Jul 2011 23:23:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 jZpDDSMIu1MF; Sat,  2 Jul 2011 23:23:44 -0700 (PDT)
Received: from globis01.globis.net (mail.globis.net [87.195.182.18]) by ietfa.amsl.com (Postfix) with ESMTP id 12C5021F876E; Sat,  2 Jul 2011 23:23:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 9E3168700DE; Sun,  3 Jul 2011 08:23:12 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at globis01.globis.net
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AFGH-9O0g9p4; Sun,  3 Jul 2011 08:23:07 +0200 (CEST)
Received: from Rays-iMac.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 382B3870030; Sun,  3 Jul 2011 08:23:07 +0200 (CEST)
Message-ID: <4E100ACB.70907@globis.net>
Date: Sun, 03 Jul 2011 08:23:07 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox Express 1.0.1 (Macintosh/20100705)
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>,  "v6ops@ietf.org WG" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Content-Type: multipart/alternative; boundary="------------040205010300000606020905"
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:25 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jul 2011 06:23:45 -0000

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

>
> Subject:
> Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
> From:
> Keith Moore <moore@network-heretics.com>
> Date:
> Sat, 2 Jul 2011 23:10:47 -0400
>
> To:
> Cameron Byrne <cb.list6@gmail.com>
> CC:
> "v6ops@ietf.org" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
>
> Precedence:
> list
> MIME-Version:
> 1.0 (Apple Message framework v1084)
> References:
> <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> 
> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> 
> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com>
> In-Reply-To:
> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com>
> Message-ID:
> <E817A524-9DB7-4553-A76F-25A9907E7C2D@network-heretics.com>
> Content-Type:
> multipart/alternative; boundary=Apple-Mail-111-642965515
> Message:
> 2
>
>
>
> I find myself wondering what you mean by REAL IPv6.  For me, REAL IPv6 
> is code that uses the IPv6 programming model, 128 bit addresses, 
> end-to-end transparency, no NATs.  6to4 certainly qualifies.
>
> Keith
Many people have many more requirements. For example, an SLA for 
availability and latency, low support costs, firewall security, DSCP 
quality of service, ability to log end point communications, intrusion 
detection, WAN acceleration, a deployment model that does not rely on 
allocating even more IPv4 addresses (that many don't have or won't have) 
or the good nature of other providers to provide a working relay .......

6to4 fails to meet many of those requirements. Granted, it isn't the 
only transition mechanism that fails to do so.

IMHO Right now, we need services with native IPv6 based interfaces, with 
equivalent performance and equivalent features and equivalent price that 
we have today with IPv4. Anything that detracts from the roll out of 
native IPv6 based service interfaces at this time is a bad move IMVHO 
and hastens the day that the Internet fragments into a bunch of CGN 
zones, that is dominated by businesses that can afford to buy public 
IPv4 addresses for their servers or services, or whose business model 
relies on NAT traversal being difficult. I personally don't want that 
sort of Internet.

Given that development and engineering support time is finite, I'd much 
rather that 6to4 was declared historic so that developers and engineers 
could spend more time on deployment of native IPv6 service interfaces.

Having said all that, 6to4 has also caused me issues with traffic 
predictability, and cost significant engineering time. Turning 6to4 off 
by default would not be the ideal solution in my view, but it should 
address many if not all of my own particular issues. If that's all 
that's on offer, I'll take it.

regards,
RayH

--------------040205010300000606020905
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 http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#ffffff" text="#000000">
<blockquote type="cite">
  <table class="header-part1" width="100%" border="0" cellpadding="0"
 cellspacing="0">
    <tbody>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline;">Subject:
        </div>
Re: [v6ops] draft-ietf-v6ops-6to4-to-historic</td>
      </tr>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline;">From: </div>
Keith Moore <a class="moz-txt-link-rfc2396E" href="mailto:moore@network-heretics.com">&lt;moore@network-heretics.com&gt;</a></td>
      </tr>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline;">Date: </div>
Sat, 2 Jul 2011 23:10:47 -0400</td>
      </tr>
    </tbody>
  </table>
  <table class="header-part2" width="100%" border="0" cellpadding="0"
 cellspacing="0">
    <tbody>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline;">To: </div>
Cameron Byrne <a class="moz-txt-link-rfc2396E" href="mailto:cb.list6@gmail.com">&lt;cb.list6@gmail.com&gt;</a></td>
      </tr>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline;">CC: </div>
<a class="moz-txt-link-rfc2396E" href="mailto:v6ops@ietf.org">"v6ops@ietf.org"</a> <a class="moz-txt-link-rfc2396E" href="mailto:v6ops@ietf.org">&lt;v6ops@ietf.org&gt;</a>, IETF Discussion
<a class="moz-txt-link-rfc2396E" href="mailto:ietf@ietf.org">&lt;ietf@ietf.org&gt;</a></td>
      </tr>
    </tbody>
  </table>
  <table class="header-part3" width="100%" border="0" cellpadding="0"
 cellspacing="0">
    <tbody>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline;">Precedence:
        </div>
list</td>
      </tr>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline;">MIME-Version:
        </div>
1.0 (Apple Message framework v1084)</td>
      </tr>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline;">References:
        </div>
<a class="moz-txt-link-rfc2396E" href="mailto:13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net">&lt;13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net&gt;</a>
<a class="moz-txt-link-rfc2396E" href="mailto:CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com">&lt;CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com&gt;</a>
<a class="moz-txt-link-rfc2396E" href="mailto:BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com">&lt;BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com&gt;</a></td>
      </tr>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline;">In-Reply-To:
        </div>
<a class="moz-txt-link-rfc2396E" href="mailto:BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com">&lt;BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com&gt;</a></td>
      </tr>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline;">Message-ID:
        </div>
<a class="moz-txt-link-rfc2396E" href="mailto:E817A524-9DB7-4553-A76F-25A9907E7C2D@network-heretics.com">&lt;E817A524-9DB7-4553-A76F-25A9907E7C2D@network-heretics.com&gt;</a></td>
      </tr>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline;">Content-Type:
        </div>
multipart/alternative; boundary=Apple-Mail-111-642965515</td>
      </tr>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline;">Message:
        </div>
2</td>
      </tr>
    </tbody>
  </table>
  <br>
  <div><br>
  </div>
  <div>I
find myself wondering what you mean by REAL IPv6. &nbsp;For me, REAL IPv6 is
code that uses the IPv6 programming model, 128 bit addresses,
end-to-end transparency, no NATs. &nbsp;6to4 certainly qualifies.</div>
  <div><br>
  </div>
  <div>Keith</div>
</blockquote>
Many people have many more requirements. For example, an SLA for
availability and latency, low support costs, firewall security, DSCP
quality of service, ability to log end point communications, intrusion
detection, WAN acceleration, a deployment model that does not rely on
allocating even more IPv4 addresses (that many don't have or won't
have) or the good nature of other providers to provide a working relay
.......<br>
<br>
6to4 fails to meet many of those requirements. Granted, it isn't the
only transition mechanism that fails to do so.<br>
<br>
IMHO Right now, we need services with native IPv6 based interfaces,
with equivalent performance and equivalent features and equivalent
price that we have today with IPv4. Anything that detracts from the
roll out of native IPv6 based service interfaces at this time is a bad
move IMVHO and hastens the day that the Internet fragments into a bunch
of CGN zones, that is dominated by businesses that can afford to buy
public IPv4 addresses for their servers or services, or whose business
model relies on NAT traversal being difficult. I personally don't want
that sort of Internet.<br>
<br>
Given that development and engineering support time is finite, I'd much
rather that 6to4 was declared historic so that developers and engineers
could spend more time on deployment of native IPv6 service interfaces.<br>
<br>
Having said all that, 6to4 has also caused me issues with traffic
predictability, and cost significant engineering time. Turning 6to4 off
by default would not be the ideal solution in my view, but it should
address many if not all of my own particular issues. If that's all
that's on offer, I'll take it.<br>
<br>
regards,<br>
RayH<br>
</body>
</html>

--------------040205010300000606020905--

From randy@psg.com  Sat Jul  2 23:29:44 2011
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E290421F8798; Sat,  2 Jul 2011 23:29:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.276
X-Spam-Level: 
X-Spam-Status: No, score=-2.276 tagged_above=-999 required=5 tests=[AWL=-0.277, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hNj6Bqhnwr55; Sat,  2 Jul 2011 23:29:44 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 4946D21F8795; Sat,  2 Jul 2011 23:29:44 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76 (FreeBSD)) (envelope-from <randy@psg.com>) id 1QdGBY-000G0P-NV; Sun, 03 Jul 2011 06:29:40 +0000
Date: Sun, 03 Jul 2011 15:29:39 +0900
Message-ID: <m2aacvkhbg.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
In-Reply-To: <D3733DF4-0313-4651-BDC2-24E4124994EF@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <DE414D2B-82ED-4C32-AFDF-EDAAB6D743B2@network-heretics.com> <CAKD1Yr0=pJwOzRvTNskS7YDBNa7Fc=8srGzH2qJUKwGHdCAELg@mail.gmail.com> <A1DA82E2-B979-4719-9F78-DEB263B256A1@network-heretics.com> <CAKD1Yr34UZO7jRAy8hL9uKW2yJ5dDuvOCzrQJ7zn9MmBTovnCg@mail.gmail.com> <D3733DF4-0313-4651-BDC2-24E4124994EF@network-heretics.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:25 -0700
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 06:29:45 -0000

>> Nope. The v6ops chairs saw consensus in v6ops to support it. Can you
>> point to significant strength of opinion of the wider IETF community,
>> but not in v6ops, that has reason to oppose it?
> 
> That's not how it works.  You have to get consensus in IETF, not in
> v6ops.

when it is last called.  and you can dos that mailing list then, and
threaten, and bluster.

randy

From Ted.Lemon@nominum.com  Sat Jul  2 23:37:49 2011
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB03121F87AF; Sat,  2 Jul 2011 23:37:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.298
X-Spam-Level: 
X-Spam-Status: No, score=-106.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_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 yq-rdIi2v5o8; Sat,  2 Jul 2011 23:37:49 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id 83FF121F87A7; Sat,  2 Jul 2011 23:37:48 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKThAOOzubqJWMhuO1JxIcYO92VZMnssDh@postini.com; Sat, 02 Jul 2011 23:37:48 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id A3C5E1B8338; Sat,  2 Jul 2011 23:37:47 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 8D3BC190052; Sat,  2 Jul 2011 23:37:47 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from exchange-01.WIN.NOMINUM.COM (64.89.228.50) by CAS-01.WIN.NOMINUM.COM (64.89.228.131) with Microsoft SMTP Server (TLS) id 14.1.289.1; Sat, 2 Jul 2011 23:37:47 -0700
Received: from vpna-148.vpn.nominum.com (64.89.227.148) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Sat, 2 Jul 2011 23:37:47 -0700
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
MIME-Version: 1.0 (Apple Message framework v1242)
Content-Type: multipart/alternative; boundary="Apple-Mail=_FD3C3BE2-5B2E-4A4C-B13C-935095499B5E"
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <D3733DF4-0313-4651-BDC2-24E4124994EF@network-heretics.com>
Date: Sun, 3 Jul 2011 02:37:43 -0400
Message-ID: <AEFA1403-74C5-4982-A056-4AF7E5734BEA@nominum.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <DE414D2B-82ED-4C32-AFDF-EDAAB6D743B2@network-heretics.com> <CAKD1Yr0=pJwOzRvTNskS7YDBNa7Fc=8srGzH2qJUKwGHdCAELg@mail.gmail.com> <A1DA82E2-B979-4719-9F78-DEB263B256A1@network-heretics.com> <CAKD1Yr34UZO7jRAy8hL9uKW2yJ5dDuvOCzrQJ7zn9MmBTovnCg@mail.gmail.com> <D3733DF4-0313-4651-BDC2-24E4124994EF@network-heretics.com>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1242)
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:25 -0700
Cc: "v6ops@ietf.org Operations" <v6ops@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: Sun, 03 Jul 2011 06:37:49 -0000

--Apple-Mail=_FD3C3BE2-5B2E-4A4C-B13C-935095499B5E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="windows-1252"

On Jul 3, 2011, at 1:47 AM, Keith Moore wrote:
> Some of them were posted to the IETF list.  IESG may have received =
others privately.  That is permitted by our process.

This is a frustrating conversation.   Everybody who supported the =
consensus in v6ops is an IETF participant, and their wishes count toward =
the IETF consensus.   The draft is good.   It encourages people to do =
the right things: keep 6to4 relays active, but not ship products with =
6to4 enabled by default.  This works for everyone=97for people like me =
who are using 6to4 for our IPv6 connectivity, it works because the =
relays stay up.   For people who do not have global IPv4 addresses, they =
do not wind up with IPv6 routes that go nowhere.   It certainly serves =
Keith Moore's needs, no matter how vehemently, nor how often, he may =
insist that it does not.

So this really does look like another IETF night of long knives, where a =
good draft gets scuttled in secret because a few very loud people manage =
to create enough of a fuss to make the person or persons calling the =
consensus feel like they're going to get fricasseed if they call the =
consensus in favor of the draft.

Have we actually had a formal consensus call for the IETF?   Who called =
the consensus?   Can we have a summary?   I haven't seen one.


--Apple-Mail=_FD3C3BE2-5B2E-4A4C-B13C-935095499B5E
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; =
"><div><div>On Jul 3, 2011, at 1:47 AM, Keith Moore =
wrote:</div><blockquote type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; font-family: Optima; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div>Some of =
them were posted to the IETF list. &nbsp;IESG may have received others =
privately. &nbsp;That is permitted by our =
process.</div></span></blockquote><br></div><div>This is a frustrating =
conversation. &nbsp; Everybody who supported the consensus in v6ops is =
an IETF participant, and their wishes count toward the IETF consensus. =
&nbsp; The draft is good. &nbsp; It encourages people to do the right =
things: keep 6to4 relays active, but not ship products with 6to4 enabled =
by default. &nbsp;This works for everyone=97for people like me who are =
using 6to4 for our IPv6 connectivity, it works because the relays stay =
up. &nbsp; For people who do not have global IPv4 addresses, they do not =
wind up with IPv6 routes that go nowhere. &nbsp; It certainly serves =
Keith Moore's needs, no matter how vehemently, nor how often, he may =
insist that it does not.</div><div><br></div><div>So this really does =
look like another IETF night of long knives, where a good draft gets =
scuttled in secret because a few very loud people manage to create =
enough of a fuss to make the person or persons calling the consensus =
feel like they're going to get fricasseed if they call the consensus in =
favor of the draft.</div><div><br></div><div>Have we actually had a =
formal consensus call for the IETF? &nbsp; Who called the consensus? =
&nbsp; Can we have a summary? &nbsp; I haven't seen =
one.</div><div><br></div></body></html>=

--Apple-Mail=_FD3C3BE2-5B2E-4A4C-B13C-935095499B5E--

From v6ops@globis.net  Sun Jul  3 00:16:38 2011
Return-Path: <v6ops@globis.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75D1521F87C9; Sun,  3 Jul 2011 00:16:38 -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 fmyIZ4MLCoF5; Sun,  3 Jul 2011 00:16:36 -0700 (PDT)
Received: from globis01.globis.net (mail.globis.net [87.195.182.18]) by ietfa.amsl.com (Postfix) with ESMTP id 5839F21F86FD; Sun,  3 Jul 2011 00:16:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 8D6328700DE; Sun,  3 Jul 2011 09:16:04 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at globis01.globis.net
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SENpc0eC544z; Sun,  3 Jul 2011 09:15:59 +0200 (CEST)
Received: from Rays-iMac.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 524AF870021; Sun,  3 Jul 2011 09:15:59 +0200 (CEST)
Message-ID: <4E10172F.3070105@globis.net>
Date: Sun, 03 Jul 2011 09:15:59 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox Express 1.0.1 (Macintosh/20100705)
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
References: <4E100ACB.70907@globis.net> <806331F9-2A3D-459C-8774-BED1346C475F@network-heretics.com>
In-Reply-To: <806331F9-2A3D-459C-8774-BED1346C475F@network-heretics.com>
Content-Type: multipart/alternative; boundary="------------030700020500050306040409"
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:25 -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: Sun, 03 Jul 2011 07:16:38 -0000

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

Keith Moore wrote:
> On Jul 3, 2011, at 2:23 AM, Ray Hunter wrote:
>
>    
>> IMHO Right now, we need services with native IPv6 based interfaces, with equivalent performance and equivalent features and equivalent price that we have today with IPv4. Anything that detracts from the roll out of native IPv6 based service interfaces at this time is a bad move IMVHO and hastens the day that the Internet fragments into a bunch of CGN zones, that is dominated by businesses that can afford to buy public IPv4 addresses for their servers or services, or whose business model relies on NAT traversal being difficult. I personally don't want that sort of Internet.
>>      
>
> Right now, applications developers need to be able to write and ship code that uses IPv6 and can talk to other application instances using IPv6.   Anything that detracts from the ability of applications to use IPv6 at this time is a bad move IMHO and decreases the chance that there will ever be sufficient use of IPv6 (of any kind) to justify widespread deployment of native IPv6.
>
>    
>> Given that development and engineering support time is finite, I'd much rather that 6to4 was declared historic so that developers and engineers could spend more time on deployment of native IPv6 service interfaces.
>>      
>
> I have a better suggestion: let's declare NAT historic.  That would free up lots of developers and engineers to spend time on both native v6 and better v6 transition mechanisms.  Not only would they not need to engineer new NATs, applications developers wouldn't need to engineer new workarounds for new NATs.  Everybody would win.
>
> Keith
>
>    
I'm presuming your second comment was facetious.

I'm also presuming from your first comment that you will thus oppose the 
proposal to turn off 6to4 by default.

Am I correct?

regards
RayH,

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Keith Moore wrote:
<blockquote
 cite="mid:806331F9-2A3D-459C-8774-BED1346C475F@network-heretics.com"
 type="cite">
  <pre wrap="">On Jul 3, 2011, at 2:23 AM, Ray Hunter wrote:

  </pre>
  <blockquote type="cite">
    <pre wrap="">IMHO Right now, we need services with native IPv6 based interfaces, with equivalent performance and equivalent features and equivalent price that we have today with IPv4. Anything that detracts from the roll out of native IPv6 based service interfaces at this time is a bad move IMVHO and hastens the day that the Internet fragments into a bunch of CGN zones, that is dominated by businesses that can afford to buy public IPv4 addresses for their servers or services, or whose business model relies on NAT traversal being difficult. I personally don't want that sort of Internet.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Right now, applications developers need to be able to write and ship code that uses IPv6 and can talk to other application instances using IPv6.   Anything that detracts from the ability of applications to use IPv6 at this time is a bad move IMHO and decreases the chance that there will ever be sufficient use of IPv6 (of any kind) to justify widespread deployment of native IPv6.

  </pre>
  <blockquote type="cite">
    <pre wrap="">Given that development and engineering support time is finite, I'd much rather that 6to4 was declared historic so that developers and engineers could spend more time on deployment of native IPv6 service interfaces.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
I have a better suggestion: let's declare NAT historic.  That would free up lots of developers and engineers to spend time on both native v6 and better v6 transition mechanisms.  Not only would they not need to engineer new NATs, applications developers wouldn't need to engineer new workarounds for new NATs.  Everybody would win.

Keith

  </pre>
</blockquote>
I'm presuming your second comment was facetious.<br>
<br>
I'm also presuming from your first comment that you will thus oppose
the proposal to turn off 6to4 by default.<br>
<br>
Am I correct?<br>
<br>
regards<br>
RayH,<br>
</body>
</html>

--------------030700020500050306040409--

From randy@psg.com  Sun Jul  3 00:23:50 2011
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65D8611E80C4; Sun,  3 Jul 2011 00:23:50 -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 iDHDnhCUfolH; Sun,  3 Jul 2011 00:23:50 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 84B4E11E8079; Sun,  3 Jul 2011 00:23:49 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76 (FreeBSD)) (envelope-from <randy@psg.com>) id 1QdH1u-000G8f-5C; Sun, 03 Jul 2011 07:23:46 +0000
Date: Sun, 03 Jul 2011 16:23:45 +0900
Message-ID: <m27h7zketa.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
In-Reply-To: <4E10132E.3050902@dougbarton.us>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com> <20110703112048.4a3c7111@opy.nosense.org> <4E0FD788.3000305@dougbarton.us> <20110703131913.28142ec0@opy.nosense.org> <4E10132E.3050902@dougbarton.us>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:25 -0700
Cc: IPv6 Ops 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: Sun, 03 Jul 2011 07:23:50 -0000

>> Discussion isn't evidence, as people usually don't post any data to
>> support their assertions.
> 
> And yet, they did.
> 
> This whole thing is getting silly, and I'm tired of repeating myself. I 
> think Lorenzo did a great job of explaining some more of the downsides 
> of 6to4 and I don't have anything useful to add beyond what I've already 
> said.

geoff's presos show the 6to4 train wreck pretty clearly.  and it ain't
pretty.

yes, a few geeks such as rob austein, keith moore, ... who desperately
want to test ipv6 can manage to get it working.  big whoopie doo.  it is
a disaster for a significant percentage of the end users.  it needs to
be stopped.

randy

From gert@space.net  Sun Jul  3 04:10:55 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 AFA3521F8570 for <ietf@ietfa.amsl.com>; Sun,  3 Jul 2011 04:10:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MrwoNLM8L+C1 for <ietf@ietfa.amsl.com>; Sun,  3 Jul 2011 04:10: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 34CE521F856D for <ietf@ietf.org>; Sun,  3 Jul 2011 04:10:50 -0700 (PDT)
Received: from mobil.space.net (localhost [127.0.0.1]) by mobil.space.net (Postfix) with ESMTP id 706AAF8514 for <ietf@ietf.org>; Sun,  3 Jul 2011 13:10: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 3EC7CF8512 for <ietf@ietf.org>; Sun,  3 Jul 2011 13:10:47 +0200 (CEST)
Received: (qmail 55907 invoked by uid 1007); 3 Jul 2011 13:10:47 +0200
Date: Sun, 3 Jul 2011 13:10:47 +0200
From: Gert Doering <gert@space.net>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Message-ID: <20110703111047.GB2304@Space.Net>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <DE414D2B-82ED-4C32-AFDF-EDAAB6D743B2@network-heretics.com> <CAKD1Yr0=pJwOzRvTNskS7YDBNa7Fc=8srGzH2qJUKwGHdCAELg@mail.gmail.com> <A1DA82E2-B979-4719-9F78-DEB263B256A1@network-heretics.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <A1DA82E2-B979-4719-9F78-DEB263B256A1@network-heretics.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:25 -0700
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 11:10:55 -0000

Hi,

On Sat, Jul 02, 2011 at 11:11:43PM -0400, Keith Moore wrote:
> There's clearly a lack of consensus to support it.

There's two very vocal persons opposing it and a much larger number of
people that support it, but have not the time to write a similarily
large amount of e-mails.  For me, this is enough for "rough consensus".

(And I second everything Lorenzo, Randy and Cameron said - there's 
theoretical possibilities, and real world.  6to4 fails the real-world
test.  Get over it, instead of attacking people that run real-world
networks for the decisions they need to do to keep the networks running
in a world without enough IPv4 addresses).

Gert Doering
        -- Operator
-- 
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  Sun Jul  3 04:17:21 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 0898E21F8699; Sun,  3 Jul 2011 04:17:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.299
X-Spam-Level: 
X-Spam-Status: No, score=-8.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, GB_I_LETTER=-2, 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 GMXplb5l4rAs; Sun,  3 Jul 2011 04:17:20 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id 84CCE21F856E; Sun,  3 Jul 2011 04:17:19 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #55) id m1QdKfr-0001jNC; Sun, 3 Jul 2011 13:17:15 +0200
Message-Id: <m1QdKfr-0001jNC@stereo.hq.phicoh.net>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic 
From: Philip Homburg <pch-v6ops@u-1.phicoh.com>
Sender: pch-b2B3A6689@u-1.phicoh.com
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com> <20110703112048.4a3c7111@opy.nosense.org> <4E0FD788.3000305@dougbarton.us> <20110703131913.28142ec0@opy.nosense.org> <CAKD1Yr0dU8xGPc5tY8qK7w7Vc57zzj2BBipCb3b3VsXLov-JUw@mail.gmail.com>
In-reply-to: Your message of "Sun, 3 Jul 2011 07:53:46 +0200 ." <CAKD1Yr0dU8xGPc5tY8qK7w7Vc57zzj2BBipCb3b3VsXLov-JUw@mail.gmail.com> 
Date: Sun, 03 Jul 2011 13:17:14 +0200
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:25 -0700
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 11:17:21 -0000

In your letter dated Sun, 3 Jul 2011 07:53:46 +0200 you wrote:
>Unfortunately, in the 20% of the time that it's not working, Google has no
>idea that the user has a 2002::/16 address. Google only knows, after the
>fact, that the user suffered a 20 or 75-second timeout and was not happy. So
>it would serve no purpose to avoid serving users that successfully connect
>from 2002::/16 addresses; once the AAAA record is handed out, the damage is
>done. What Google could do, however, is stop handing out AAAA records to
>networks that have significant number of 6to4 users in the future. We're
>considering this.

I think this clearly illustrates why the IETF should issue a strong statement
that no new 6to4 installation should be deplayed and the existing 6to4 users
should migrate to other tunneling techniques (if native is not available).

The problem with 6to4 is it was rolled out on a relatively large scale when 
there was essentially no IPv6 content. As a result, the people who had a
broken 6to4 setup would only find out when content providers would start
adding AAAA records. 

In other words, it was ticking time bomb.

This time bomb has been defused mostly because most operating system now prefer
any kind of IPv4 over a 6to4 address. So once again people can have a broken
6to4 setup without noticing it.

What worries me is that people will start using 6to4 for bittorrent. Bittorrent
will of course completely hide broken setups and worse, it will also hide 
broken 6to4 relays. 

So we may end up with a sizable group people who have an IPv6 setup that
completely doesn't work. And they don't know it.

Which will create all kinds of headaches for IPv6-only content because you
have to explain to users that yes, they have an IPv6 address and no, it is not
going to work.

And all of this, because a few hobbyists are afraid that declaring 6to4 as
historic will require them to search a bit harder in the furture for a
router that supports 6to4.



From arturo.servin@gmail.com  Sun Jul  3 07:58:41 2011
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E64A811E807C; Sun,  3 Jul 2011 07:58:41 -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 y1FA8musbaob; Sun,  3 Jul 2011 07:58:41 -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 1F74011E8074; Sun,  3 Jul 2011 07:58:41 -0700 (PDT)
Received: by vxi40 with SMTP id 40so4010471vxi.31 for <multiple recipients>; Sun, 03 Jul 2011 07:58:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer; bh=sQxxmDt6IKlD7LQ7K1/XV+XAnqjHH1EIQyQsSQBYbHk=; b=Xpq9rRIJGjNsNQegtZKacUeSZhEkxcc4OOxJfyATPO8oVhuiwdAk8bSmx9++Afq0n1 CW2tOvJcR4ZPvd//WIdG/3aJkVo57VVq1YGqaWaJZQZX0zUbAwejVF92Oj4qdSZJ3FKk VlhrA7zw3s97e1gUJZPaNuGSMltf1/tzv2Tds=
Received: by 10.52.115.130 with SMTP id jo2mr7297909vdb.43.1309705120391; Sun, 03 Jul 2011 07:58:40 -0700 (PDT)
Received: from [192.168.1.103] (r186-48-230-104.dialup.adsl.anteldata.net.uy [186.48.230.104]) by mx.google.com with ESMTPS id l18sm3042634vby.14.2011.07.03.07.58.37 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 03 Jul 2011 07:58:39 -0700 (PDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-167-685434716
From: Arturo Servin <arturo.servin@gmail.com>
In-Reply-To: <100DA5A2-0276-45B8-A8CD-AB7B0D947AC4@network-heretics.com>
Date: Sun, 3 Jul 2011 11:58:36 -0300
Message-Id: <CB106539-9C0F-489C-BBC0-E4ADAF3B8F45@gmail.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com> <20110703112048.4a3c7111@opy.nosense.org> <4E0FD788.3000305@dougbarton.us> <20110703131913.28142ec0@opy.nosense.org> <CAKD1Yr0dU8xGPc5tY8qK7w7Vc57zzj2BBipCb3b3VsXLov-JUw@mail.gmail.com> <m1QdKfr-0001jNC@stereo.hq.phicoh.net> <E3CF6B2C-B177-4A6A-898C-4EA8C8CA65D5@network-heretics.com> <CAD6AjGSUEmdKk3trTdRXMyrnp8FFyvHUWBSgeBrHT_2jPjXUBA@mail.gmail.com> <100DA5A2-0276-45B8-A8CD-AB7B0D947AC4@network-heretics.com>
To: IPv6 Operations <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:25 -0700
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: Sun, 03 Jul 2011 14:58:42 -0000

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


	And b.

	And probably it is too much effort for something that will go =
away (probably sooner that we expect) with the exhaustion of IPv4 =
addresses for each ISP's customer (6to4 does not work with NATs, and =
they are here).

-as

On 3 Jul 2011, at 11:40, Keith Moore wrote:

>> > I think this clearly illustrates why IETF should issue a strong =
statement that
>> >
>> > a) operators of 6to4 relays should not advertise those relays via =
BGP unless they're routing traffic for all of 2002://16 or native v6, =
respectively
>> > b) operators should not filter protocol 41traffic
>> > c) (maybe) operators using LSN should use RFC 1918 addresses behind =
those NATs unless/until there's another address range that 6to4 host =
implementations know about
>> > d) 6to4 should be disabled by default in both hosts and routers
>> > e) host implementations should prefer native v4 destinations over =
6to4 destinations when both are available and the application can use =
either IPv4 or IPv6
>> >
>>=20
>> You will not get "consensus" on these statements in the IETF or by =
the various companies that implement gear and networks in the REAL =
world.
>>=20
> why not?  all of those recommendations are clearly appropriate and =
desirable, with the possible exception of (c) because ISP use of RFC =
1918 addresses is likely to conflict with customer user of the same =
address ranges.


--Apple-Mail-167-685434716
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><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>And =
b.</div><div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>And probably it is too much =
effort for something that will go away (probably sooner that we expect) =
with the exhaustion of IPv4 addresses for each ISP's customer (6to4 does =
not work with NATs, and they are =
here).</div><div><br></div><div>-as</div><br><div><div>On 3 Jul 2011, at =
11:40, Keith Moore 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; "><blockquote =
type=3D"cite"><p>&gt; I think this clearly illustrates why IETF should =
issue a strong statement that<br>&gt;<br>&gt; a) operators of 6to4 =
relays should not advertise those relays via BGP unless they're routing =
traffic for all of<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"x-msg://1551/2002://16">2002://16</a><span =
class=3D"Apple-converted-space">&nbsp;</span>or native v6, =
respectively<br>&gt; b) operators should not filter protocol =
41traffic<br>&gt; c) (maybe) operators using LSN should use RFC 1918 =
addresses behind those NATs unless/until there's another address range =
that 6to4 host implementations know about<br>&gt; d) 6to4 should be =
disabled by default in both hosts and routers<br>&gt; e) host =
implementations should prefer native v4 destinations over 6to4 =
destinations when both are available and the application can use either =
IPv4 or IPv6<br>&gt;</p><p>You will not get "consensus" on these =
statements in the IETF or by the various companies that implement gear =
and networks in the REAL world.</p></blockquote>why not? &nbsp;all of =
those recommendations are clearly appropriate and desirable, with the =
possible exception of (c) because ISP use of RFC 1918 addresses is =
likely to conflict with customer user of the same address =
ranges.</span></blockquote></div><br></body></html>=

--Apple-Mail-167-685434716--

From eran@hueniverse.com  Sun Jul  3 09:51:07 2011
Return-Path: <eran@hueniverse.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12AEF21F86F4 for <ietf@ietfa.amsl.com>; Sun,  3 Jul 2011 09:51:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.418
X-Spam-Level: 
X-Spam-Status: No, score=-2.418 tagged_above=-999 required=5 tests=[AWL=0.180,  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 VDpJpkaagvqD for <ietf@ietfa.amsl.com>; Sun,  3 Jul 2011 09:51:06 -0700 (PDT)
Received: from p3plex1out02.prod.phx3.secureserver.net (p3plex1out02.prod.phx3.secureserver.net [72.167.180.18]) by ietfa.amsl.com (Postfix) with SMTP id 4078C21F86EC for <ietf@ietf.org>; Sun,  3 Jul 2011 09:51:06 -0700 (PDT)
Received: (qmail 5539 invoked from network); 3 Jul 2011 16:51:05 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.21) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 3 Jul 2011 16:51:04 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.19]) by P3PW5EX1HT003.EX1.SECURESERVER.NET ([72.167.180.21]) with mapi; Sun, 3 Jul 2011 09:51:04 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>, Mark Nottingham <mnot@mnot.net>
Date: Sun, 3 Jul 2011 09:50:58 -0700
Subject: Re: Second Last Call: <draft-hammer-hostmeta-16.txt> (Web Host Metadata) to Proposed Standard -- feedback
Thread-Topic: Second Last Call: <draft-hammer-hostmeta-16.txt> (Web Host Metadata) to Proposed Standard -- feedback
Thread-Index: Acw5oWW/qA3tk1TqROulYHVc1/IFeg==
Message-ID: <CA35E63A.15F21%eran@hueniverse.com>
In-Reply-To: <623429C9-70E2-4442-8ECF-AB827FD95251@gmx.net>
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
Content-Type: multipart/alternative; boundary="_000_CA35E63A15F21eranhueniversecom_"
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:25 -0700
Cc: "ietf@ietf.org IETF" <ietf@ietf.org>, oauth WG <oauth@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jul 2011 16:51:07 -0000

--_000_CA35E63A15F21eranhueniversecom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hannes,

None of the current OAuth WG document address discovery in any way, so clea=
rly there will be no use of XRD. But the OAuth community predating the IETF=
 had multiple proposals for it. In addition, multiple times on the IETF OAu=
th WG list, people have suggested using host-meta and XRD for discovery pur=
poses.

The idea that XRD was reused without merit is both misleading and mean-spir=
ited. Personally, I'm sick of it, especially coming from standards professi=
onals.

XRD was largely developed by the same people who worked on host-meta. XRD p=
redated host-meta and was designed to cover the wider use case. Host-meta w=
as an important use case when developing XRD in its final few months. It wa=
s done in OASIS out of respect to proper standards process in which the bod=
y that originated a work (XRDS) gets to keep it.

I challenge anyone to find any faults with the IPR policy or process used t=
o develop host-meta in OASIS.

XRD is one of the simplest XML formats I have seen. I bet most of the peopl=
e bashing it now have never bothered to read it. At least some of these peo=
ple have been personally invited by me to comment on XRD while it was still=
 in development and chose to dismiss it.

XRD was designed in a very open process with plenty of community feedback a=
nd it was significantly simplified based on that feedback. In addition, hos=
t-meta further simplifies it by profiling it down, removing some of the mor=
e complex elements like Subject and Alias (which are very useful in other c=
ontexts). XRD is nothing more than a cleaner version of HTML <LINK> element=
s with literally a handful of new elements based on well defined and widely=
 supported requirements. It's entire semantic meaning is based on the IETF =
Link relation registry RFC.

There is something very disturbing going on these days in how people treat =
XML-based formats, especially form OASIS.

When host-meta's predecessor - side=96meta =96 was originally proposed a fe=
w years ago, Mark Nottingham proposed an XML format not that different from=
 XRD. There is nothing wrong with JSON taking over as a simpler alternative=
. I personally prefer JSON much better. But it would be reckless and counte=
r productive to ignore a decade of work on XML formats just because it is n=
o longer cool. Feels like we back in high school.

If you have technical arguments against host-meta, please share. But if you=
r objections are based on changing trends, dislike of XML or anything OASIS=
, grow up.

EHL



From: Hannes Tschofenig <hannes.tschofenig@gmx.net<mailto:hannes.tschofenig=
@gmx.net>>
Date: Sun, 3 Jul 2011 00:36:29 -0700
To: Mark Nottingham <mnot@mnot.net<mailto:mnot@mnot.net>>
Cc: Hannes Tschofenig <hannes.tschofenig@gmx.net<mailto:hannes.tschofenig@g=
mx.net>>, "ietf@ietf.org<mailto:ietf@ietf.org> IETF" <ietf@ietf.org<mailto:=
ietf@ietf.org>>, Eran Hammer-lahav <eran@hueniverse.com<mailto:eran@huenive=
rse.com>>, oauth WG <oauth@ietf.org<mailto:oauth@ietf.org>>
Subject: Re: Second Last Call: <draft-hammer-hostmeta-16.txt> (Web Host Met=
adata) to Proposed Standard -- feedback

I also never really understood why XRD was re-used.

Btw, XRD is not used by any of the current OAuth WG documents, see http://d=
atatracker.ietf.org/wg/oauth/


On Jun 22, 2011, at 8:08 AM, Mark Nottingham wrote:

* XRD -- XRD is an OASIS spec that's used by OpenID and OAuth. Maybe I'm ju=
st scarred by WS-*, but it seems very over-engineered for what it does. I u=
nderstand that the communities had reasons for using it to leverage an exis=
ting user base for their specific user cases, but I don't see any reason to=
 generalise such a beast into a generic mechanism.



--_000_CA35E63A15F21eranhueniversecom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252"></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space;=
 -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14p=
x; font-family: Calibri, sans-serif; "><div>Hannes,</div><div><br></div><di=
v>None of the current OAuth WG document address discovery in any way, so cl=
early there will be no use of XRD. But the OAuth community predating the IE=
TF had multiple proposals for it. In addition, multiple times on the IETF O=
Auth WG list, people have suggested using host-meta and XRD for discovery p=
urposes.</div><div><br></div><div>The idea that XRD was reused without meri=
t is both misleading and mean-spirited. Personally, I'm sick of it, especia=
lly coming from standards professionals.</div><div><br></div><div>XRD was l=
argely developed by the same people who worked on host-meta. XRD predated h=
ost-meta and was designed to cover the wider use case. Host-meta was an imp=
ortant use case when developing XRD in its final few months. It was done in=
 OASIS out of respect to proper standards process in which the body that or=
iginated a work (XRDS) gets to keep it.</div><div><br></div><div>I challeng=
e anyone to find any faults with the IPR policy or process used to develop =
host-meta in OASIS.</div><div><br></div><div>XRD is one of the simplest XML=
 formats I have seen. I bet most of the people bashing it now have never bo=
thered to read it. At least some of these people have been personally invit=
ed by me to comment on XRD while it was still in development and chose to d=
ismiss it.</div><div><br></div><div>XRD was designed in a very open process=
 with plenty of community feedback and it was significantly simplified base=
d on that feedback. In addition, host-meta further simplifies it by profili=
ng it down, removing some of the more complex elements like Subject and Ali=
as (which are very useful in other contexts). XRD is nothing more than a cl=
eaner version of HTML &lt;LINK&gt; elements with literally a handful of new=
 elements based on well defined and widely supported requirements. It's ent=
ire semantic meaning is based on the IETF Link relation registry RFC.</div>=
<div><br></div><div>There is something very disturbing going on these days =
in how people treat XML-based formats, especially form OASIS.</div><div><br=
></div><div>When host-meta's predecessor - side=96meta =96 was originally p=
roposed a few years ago, Mark Nottingham proposed an XML format not that di=
fferent from XRD.&nbsp;There is nothing wrong with JSON taking over as a si=
mpler alternative. I personally prefer JSON much better. But it would be re=
ckless and counter productive to ignore a decade of work on XML formats jus=
t because it is no longer cool. Feels like we back in high school.</div><di=
v><br></div><div>If you have technical arguments against host-meta, please =
share. But if your objections are based on changing trends, dislike of XML =
or anything OASIS, grow up.</div><div><br></div><div>EHL</div><div><br></di=
v><div><br></div><div><br></div><span id=3D"OLK_SRC_BODY_SECTION"><div styl=
e=3D"font-family:Calibri; font-size:11pt; text-align:left; color:black; BOR=
DER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PAD=
DING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-R=
IGHT: medium none; PADDING-TOP: 3pt"><span style=3D"font-weight:bold">From:=
 </span> Hannes Tschofenig &lt;<a href=3D"mailto:hannes.tschofenig@gmx.net"=
>hannes.tschofenig@gmx.net</a>&gt;<br><span style=3D"font-weight:bold">Date=
: </span> Sun, 3 Jul 2011 00:36:29 -0700<br><span style=3D"font-weight:bold=
">To: </span> Mark Nottingham &lt;<a href=3D"mailto:mnot@mnot.net">mnot@mno=
t.net</a>&gt;<br><span style=3D"font-weight:bold">Cc: </span> Hannes Tschof=
enig &lt;<a href=3D"mailto:hannes.tschofenig@gmx.net">hannes.tschofenig@gmx=
.net</a>&gt;, &quot;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> IETF=
&quot; &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;, Eran Ham=
mer-lahav &lt;<a href=3D"mailto:eran@hueniverse.com">eran@hueniverse.com</a=
>&gt;, oauth WG &lt;<a href=3D"mailto:oauth@ietf.org">oauth@ietf.org</a>&gt=
;<br><span style=3D"font-weight:bold">Subject: </span> Re: Second Last Call=
: &lt;draft-hammer-hostmeta-16.txt&gt; (Web Host Metadata) to Proposed Stan=
dard -- feedback<br></div><div><br></div><blockquote id=3D"MAC_OUTLOOK_ATTR=
IBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5;=
 MARGIN:0 0 0 5;"><div><div><div>I also never really understood why XRD was=
 re-used. </div><div><br></div><div>Btw, XRD is not used by any of the curr=
ent OAuth WG documents, see <a href=3D"http://datatracker.ietf.org/wg/oauth=
/">http://datatracker.ietf.org/wg/oauth/</a></div><div><br></div><div><br><=
/div><div>On Jun 22, 2011, at 8:08 AM, Mark Nottingham wrote:</div><div><br=
></div><blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDE=
R-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div> * XRD -- X=
RD 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 generalis=
e such a beast into a generic mechanism.</div></blockquote><div><br></div><=
div><br></div></div></div></blockquote></span></body></html>

--_000_CA35E63A15F21eranhueniversecom_--

From wmills@yahoo-inc.com  Sun Jul  3 11:02:00 2011
Return-Path: <wmills@yahoo-inc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7E0B228013 for <ietf@ietfa.amsl.com>; Sun,  3 Jul 2011 11:02:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.548
X-Spam-Level: 
X-Spam-Status: No, score=-14.548 tagged_above=-999 required=5 tests=[AWL=3.050, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8sSjazha24EY for <ietf@ietfa.amsl.com>; Sun,  3 Jul 2011 11:01:59 -0700 (PDT)
Received: from nm7-vm0.bullet.mail.ac4.yahoo.com (nm7-vm0.bullet.mail.ac4.yahoo.com [98.139.52.228]) by ietfa.amsl.com (Postfix) with SMTP id 597D021F86C0 for <ietf@ietf.org>; Sun,  3 Jul 2011 11:01:59 -0700 (PDT)
Received: from [98.139.52.192] by nm7.bullet.mail.ac4.yahoo.com with NNFMP; 03 Jul 2011 18:01:56 -0000
Received: from [98.139.52.171] by tm5.bullet.mail.ac4.yahoo.com with NNFMP; 03 Jul 2011 18:01:56 -0000
Received: from [127.0.0.1] by omp1054.mail.ac4.yahoo.com with NNFMP; 03 Jul 2011 18:01:56 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 60209.16784.bm@omp1054.mail.ac4.yahoo.com
Received: (qmail 74029 invoked by uid 60001); 3 Jul 2011 18:01:55 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo-inc.com; s=ginc1024; t=1309716115; bh=3/SAPWdkOYBPRxqHxo9z8eWvP2so1RJBN+/47PMC4/g=; h=X-YMail-OSG:Received:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=U+CRuJQhCFVo1fTcqhPFLGf0x6XBWynipVJxtfRQ6q0QgoJwf+z/S/FQX+msQT4jnZrMweLJp/nrolYnIqlZHd+MOLQNlQe0861UmASpctpuDOrUL2pjBs8UY91FYOc0ttOE+UItrvwcEIZYu44pNqFNAxT1HKUCx8mTD/3A2Mg=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=ginc1024; d=yahoo-inc.com; h=X-YMail-OSG:Received:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=ryq3Lvou6hXs5q/wNc6HL+KHr574UR6LpsohHGmA4oldKVXzOADarj8hs7sPVadkQQwK4FHwTDHw46uWnZ+NTAVwPvAHrEJbQpr55riPe+cmMPU/9nPAi9+ldxMb9JTewN4oXmMfuaCpCXcf4pzY7bbdvLy5x+W0HlqAiVsqzVk=;
X-YMail-OSG: _QQgX8kVM1lGy4EnbZtDfkquf0jCJMql29wwxhJFARansqd m.hR96Y3_mtUMeStFXtD4YQwKx7PogQCt0aNitYfih1mpWCraBseQtbt0vWu qK.w8C7c5hOjC98M.L9rzIzhUQsV4zGJvzxoNWpOvVvuGQz0XCr2ueewe7Ri CNaEyLKtRCr_FGEXzWR31trlSxj3.DoIfI6L97tFn6V9.XzVG0fgzTIli350 jppW6Q3OZBWJ9zA_iBJ.1D9SFA_nr4BJgsAdLd37_w8DQwFVBPFNqHIKuoXE 5z.SfQH3MhRLqs_xtU3ZgEM9JUFumtqXKeucNzdT.YBP22VBtElOiUvPOlUi ew5.aOUzsk6fQhTudTAoVv.hWubhWX5.wrjIp_EIK
Received: from [209.131.62.115] by web31813.mail.mud.yahoo.com via HTTP; Sun, 03 Jul 2011 11:01:55 PDT
X-RocketYMMF: william_john_mills
X-Mailer: YahooMailWebService/0.8.112.310352
References: <623429C9-70E2-4442-8ECF-AB827FD95251@gmx.net> <CA35E63A.15F21%eran@hueniverse.com>
Message-ID: <1309716115.33071.YahooMailNeo@web31813.mail.mud.yahoo.com>
Date: Sun, 3 Jul 2011 11:01:55 -0700 (PDT)
From: "William J. Mills" <wmills@yahoo-inc.com>
Subject: Re: [OAUTH-WG] Second Last Call: <draft-hammer-hostmeta-16.txt> (Web Host Metadata) to Proposed Standard -- feedback
To: Eran Hammer-Lahav <eran@hueniverse.com>, Hannes Tschofenig <hannes.tschofenig@gmx.net>, Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CA35E63A.15F21%eran@hueniverse.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-541410507-1309716115=:33071"
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:25 -0700
Cc: "ietf@ietf.org IETF" <ietf@ietf.org>, oauth WG <oauth@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "William J. Mills" <wmills@yahoo-inc.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jul 2011 18:02:00 -0000

--0-541410507-1309716115=:33071
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

FYI there is a form of discovery for OAuth defined in http://tools.ietf.org=
/html/draft-mills-kitten-sasl-oauth-02 which uses LINK headers.=0A=0A=0A=0A=
________________________________=0AFrom: Eran Hammer-Lahav <eran@hueniverse=
.com>=0ATo: Hannes Tschofenig <hannes.tschofenig@gmx.net>; Mark Nottingham =
<mnot@mnot.net>=0ACc: "ietf@ietf.org IETF" <ietf@ietf.org>; oauth WG <oauth=
@ietf.org>=0ASent: Sunday, July 3, 2011 9:50 AM=0ASubject: Re: [OAUTH-WG] S=
econd Last Call: <draft-hammer-hostmeta-16.txt> (Web Host Metadata) to Prop=
osed Standard -- feedback=0A=0A=0AHannes,=0A=0ANone of the current OAuth WG=
 document address discovery in any way, so clearly there will be no use of =
XRD. But the OAuth community predating the IETF had multiple proposals for =
it. In addition, multiple times on the IETF OAuth WG list, people have sugg=
ested using host-meta and XRD for discovery purposes.=0A=0AThe idea that XR=
D was reused without merit is both misleading and mean-spirited. Personally=
, I'm sick of it, especially coming from standards professionals.=0A=0AXRD =
was largely developed by the same people who worked on host-meta. XRD preda=
ted host-meta and was designed to cover the wider use case. Host-meta was a=
n important use case when developing XRD in its final few months. It was do=
ne in OASIS out of respect to proper standards process in which the body th=
at originated a work (XRDS) gets to keep it.=0A=0AI challenge anyone to fin=
d any faults with the IPR policy or process used to develop host-meta in OA=
SIS.=0A=0AXRD is one of the simplest XML formats I have seen. I bet most of=
 the people bashing it now have never bothered to read it. At least some of=
 these people have been personally invited by me to comment on XRD while it=
 was still in development and chose to dismiss it.=0A=0AXRD was designed in=
 a very open process with plenty of community feedback and it was significa=
ntly simplified based on that feedback. In addition, host-meta further simp=
lifies it by profiling it down, removing some of the more complex elements =
like Subject and Alias (which are very useful in other contexts). XRD is no=
thing more than a cleaner version of HTML <LINK> elements with literally a =
handful of new elements based on well defined and widely supported requirem=
ents. It's entire semantic meaning is based on the IETF Link relation regis=
try RFC.=0A=0AThere is something very disturbing going on these days in how=
 people treat XML-based formats, especially form OASIS.=0A=0AWhen host-meta=
's predecessor - side=E2=80=93meta =E2=80=93 was originally proposed a few =
years ago, Mark Nottingham proposed an XML format not that different from X=
RD.=C2=A0There is nothing wrong with JSON taking over as a simpler alternat=
ive. I personally prefer JSON much better. But it would be reckless and cou=
nter productive to ignore a decade of work on XML formats just because it i=
s no longer cool. Feels like we back in high school.=0A=0AIf you have techn=
ical arguments against host-meta, please share. But if your objections are =
based on changing trends, dislike of XML or anything OASIS, grow up.=0A=0AE=
HL=0A=0A=0AFrom:  Hannes Tschofenig <hannes.tschofenig@gmx.net>=0ADate:  Su=
n, 3 Jul 2011 00:36:29 -0700=0ATo:  Mark Nottingham <mnot@mnot.net>=0ACc:  =
Hannes Tschofenig <hannes.tschofenig@gmx.net>, "ietf@ietf.org IETF" <ietf@i=
etf.org>, Eran Hammer-lahav <eran@hueniverse.com>, oauth WG <oauth@ietf.org=
>=0ASubject:  Re: Second Last Call: <draft-hammer-hostmeta-16.txt> (Web Hos=
t Metadata) to Proposed Standard -- feedback=0A=0A=0AI also never really un=
derstood why XRD was re-used. =0A>=0A>=0A>Btw, XRD is not used by any of th=
e current OAuth WG documents, see http://datatracker.ietf.org/wg/oauth/=0A>=
=0A>=0A>=0A>=0A>On Jun 22, 2011, at 8:08 AM, Mark Nottingham wrote:=0A>=0A>=
=0A>* 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 reaso=
n to generalise such a beast into a generic mechanism.=0A>=0A>=0A>=0A>=0A__=
_____________________________________________=0AOAuth mailing list=0AOAuth@=
ietf.org=0Ahttps://www.ietf.org/mailman/listinfo/oauth
--0-541410507-1309716115=:33071
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:Co=
urier New, courier, monaco, monospace, sans-serif;font-size:12pt"><div><spa=
n>FYI there is a form of discovery for OAuth defined in http://tools.ietf.o=
rg/html/draft-mills-kitten-sasl-oauth-02 which uses LINK headers.<br></span=
></div><div><br></div><div style=3D"font-family: Courier New,courier,monaco=
,monospace,sans-serif; font-size: 12pt;"><div style=3D"font-family: times n=
ew roman,new york,times,serif; font-size: 12pt;"><font face=3D"Arial" size=
=3D"2"><hr size=3D"1"><b><span style=3D"font-weight: bold;">From:</span></b=
> Eran Hammer-Lahav &lt;eran@hueniverse.com&gt;<br><b><span style=3D"font-w=
eight: bold;">To:</span></b> Hannes Tschofenig &lt;hannes.tschofenig@gmx.ne=
t&gt;; Mark Nottingham &lt;mnot@mnot.net&gt;<br><b><span style=3D"font-weig=
ht: bold;">Cc:</span></b> "ietf@ietf.org IETF" &lt;ietf@ietf.org&gt;; oauth=
 WG &lt;oauth@ietf.org&gt;<br><b><span style=3D"font-weight: bold;">Sent:</=
span></b>
 Sunday, July 3, 2011 9:50 AM<br><b><span style=3D"font-weight: bold;">Subj=
ect:</span></b> Re: [OAUTH-WG] Second Last Call: &lt;draft-hammer-hostmeta-=
16.txt&gt; (Web Host Metadata) to Proposed Standard -- feedback<br></font><=
br>=0A<div id=3D"yiv1633986425">=0A<div>Hannes,</div><div><br></div><div>No=
ne of the current OAuth WG document address discovery in any way, so clearl=
y there will be no use of XRD. But the OAuth community predating the IETF h=
ad multiple proposals for it. In addition, multiple times on the IETF OAuth=
 WG list, people have suggested using host-meta and XRD for discovery purpo=
ses.</div><div><br></div><div>The idea that XRD was reused without merit is=
 both misleading and mean-spirited. Personally, I'm sick of it, especially =
coming from standards professionals.</div><div><br></div><div>XRD was large=
ly developed by the same people who worked on host-meta. XRD predated host-=
meta and was designed to cover the wider use case. Host-meta was an importa=
nt use case when developing XRD in its final few months. It was done in OAS=
IS out of respect to proper standards process in which the body that origin=
ated a work (XRDS) gets to keep it.</div><div><br></div><div>I challenge an=
yone to find any faults with
 the IPR policy or process used to develop host-meta in OASIS.</div><div><b=
r></div><div>XRD is one of the simplest XML formats I have seen. I bet most=
 of the people bashing it now have never bothered to read it. At least some=
 of these people have been personally invited by me to comment on XRD while=
 it was still in development and chose to dismiss it.</div><div><br></div><=
div>XRD was designed in a very open process with plenty of community feedba=
ck and it was significantly simplified based on that feedback. In addition,=
 host-meta further simplifies it by profiling it down, removing some of the=
 more complex elements like Subject and Alias (which are very useful in oth=
er contexts). XRD is nothing more than a cleaner version of HTML &lt;LINK&g=
t; elements with literally a handful of new elements based on well defined =
and widely supported requirements. It's entire semantic meaning is based on=
 the IETF Link relation registry RFC.</div><div><br></div><div>There
 is something very disturbing going on these days in how people treat XML-b=
ased formats, especially form OASIS.</div><div><br></div><div>When host-met=
a's predecessor - side=E2=80=93meta =E2=80=93 was originally proposed a few=
 years ago, Mark Nottingham proposed an XML format not that different from =
XRD.&nbsp;There is nothing wrong with JSON taking over as a simpler alterna=
tive. I personally prefer JSON much better. But it would be reckless and co=
unter productive to ignore a decade of work on XML formats just because it =
is no longer cool. Feels like we back in high school.</div><div><br></div><=
div>If you have technical arguments against host-meta, please share. But if=
 your objections are based on changing trends, dislike of XML or anything O=
ASIS, grow up.</div><div><br></div><div>EHL</div><div><br></div><div><br></=
div><div><br></div><span id=3D"yiv1633986425OLK_SRC_BODY_SECTION"><div styl=
e=3D"font-family: Calibri; font-size: 11pt; text-align: left; color: black;
 border-width: 1pt medium medium; border-style: solid none none; border-col=
or: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; padding: 3p=
t 0in 0in;"><span style=3D"font-weight: bold;">From: </span> Hannes Tschofe=
nig &lt;<a rel=3D"nofollow" ymailto=3D"mailto:hannes.tschofenig@gmx.net" ta=
rget=3D"_blank" href=3D"mailto:hannes.tschofenig@gmx.net">hannes.tschofenig=
@gmx.net</a>&gt;<br><span style=3D"font-weight: bold;">Date: </span> Sun, 3=
 Jul 2011 00:36:29 -0700<br><span style=3D"font-weight: bold;">To: </span> =
Mark Nottingham &lt;<a rel=3D"nofollow" ymailto=3D"mailto:mnot@mnot.net" ta=
rget=3D"_blank" href=3D"mailto:mnot@mnot.net">mnot@mnot.net</a>&gt;<br><spa=
n style=3D"font-weight: bold;">Cc: </span> Hannes Tschofenig &lt;<a rel=3D"=
nofollow" ymailto=3D"mailto:hannes.tschofenig@gmx.net" target=3D"_blank" hr=
ef=3D"mailto:hannes.tschofenig@gmx.net">hannes.tschofenig@gmx.net</a>&gt;, =
"<a rel=3D"nofollow" ymailto=3D"mailto:ietf@ietf.org" target=3D"_blank"
 href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> IETF" &lt;<a rel=3D"nofoll=
ow" ymailto=3D"mailto:ietf@ietf.org" target=3D"_blank" href=3D"mailto:ietf@=
ietf.org">ietf@ietf.org</a>&gt;, Eran Hammer-lahav &lt;<a rel=3D"nofollow" =
ymailto=3D"mailto:eran@hueniverse.com" target=3D"_blank" href=3D"mailto:era=
n@hueniverse.com">eran@hueniverse.com</a>&gt;, oauth WG &lt;<a rel=3D"nofol=
low" ymailto=3D"mailto:oauth@ietf.org" target=3D"_blank" href=3D"mailto:oau=
th@ietf.org">oauth@ietf.org</a>&gt;<br><span style=3D"font-weight: bold;">S=
ubject: </span> Re: Second Last Call: &lt;draft-hammer-hostmeta-16.txt&gt; =
(Web Host Metadata) to Proposed Standard -- feedback<br></div><div><br></di=
v><blockquote id=3D"yiv1633986425MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=
=3D""><div><div><div>I also never really understood why XRD was re-used. </=
div><div><br></div><div>Btw, XRD is not used by any of the current OAuth WG=
 documents, see http://datatracker.ietf.org/wg/oauth/</div><div><br></div><=
div><br></div><div>On Jun
 22, 2011, at 8:08 AM, Mark Nottingham wrote:</div><div><br></div><blockquo=
te id=3D"yiv1633986425MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D""><div> =
* XRD -- XRD is an OASIS spec that's used by OpenID and OAuth. Maybe I'm ju=
st scarred by WS-*, but it seems very over-engineered for what it does. I u=
nderstand that the communities had reasons for using it to leverage an exis=
ting user base for their specific user cases, but I don't see any reason to=
 generalise such a beast into a generic mechanism.</div></blockquote><div><=
br></div><div><br></div></div></div></blockquote></span></div><br>_________=
______________________________________<br>OAuth mailing list<br><a ymailto=
=3D"mailto:OAuth@ietf.org" href=3D"mailto:OAuth@ietf.org">OAuth@ietf.org</a=
><br><a href=3D"https://www.ietf.org/mailman/listinfo/oauth" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/oauth</a><br><br><br></div></div>=
</div></body></html>
--0-541410507-1309716115=:33071--

From arturo.servin@gmail.com  Sun Jul  3 12:17:47 2011
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C2DF11E809E; Sun,  3 Jul 2011 12:17:47 -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 r5UZgdhCPvg5; Sun,  3 Jul 2011 12:17:47 -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 D1C5611E80A0; Sun,  3 Jul 2011 12:17:46 -0700 (PDT)
Received: by vxi40 with SMTP id 40so4093627vxi.31 for <multiple recipients>; Sun, 03 Jul 2011 12:17:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=jU0BX6VjJ3FgvtPqqhmZUTC1jFQK9id4ZhEN2kxscls=; b=poinsL1LkMgTaSuH2Ut/11HeWbS58QLDvPqeJ63nhkivelscWBJVOJdHZzxDlgWXgn d0R7cgVE7Y5ZQhbUlptghN35lTdmLuGnGxbwgdqbH5Jf0AApu0ttonzikTsRF8tMLrA3 iprRmkWnG5jchOXnXDK47dTXu1XrclcFnFTSE=
Received: by 10.220.213.202 with SMTP id gx10mr2078368vcb.77.1309720662688; Sun, 03 Jul 2011 12:17:42 -0700 (PDT)
Received: from [192.168.1.103] (r186-48-230-104.dialup.adsl.anteldata.net.uy [186.48.230.104]) by mx.google.com with ESMTPS id v3sm913271vcg.23.2011.07.03.12.17.40 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 03 Jul 2011 12:17:41 -0700 (PDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Arturo Servin <arturo.servin@gmail.com>
In-Reply-To: <746A967B-16AF-4428-8424-298AF8001F87@network-heretics.com>
Date: Sun, 3 Jul 2011 16:17:37 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <DFD19CC6-219F-4449-B0F4-8125193B6FF6@gmail.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com> <20110703112048.4a3c7111@opy.nosense.org> <4E0FD788.3000305@dougbarton.us> <20110703131913.28142ec0@opy.nosense.org> <CAKD1Yr0dU8xGPc5tY8qK7w7Vc57zzj2BBipCb3b3VsXLov-JUw@mail.gmail.com> <m1QdKfr-0001jNC@stereo.hq.phicoh.net> <E3CF6B2C-B177-4A6A-898C-4EA8C8CA65D5@network-heretics.com> <CAD6AjGSUEmdKk3trTdRXMyrnp8FFyvHUWBSgeBrHT_2jPjXUBA@mail.gmail.com> <100DA5A2-0276-45B8-A8CD-AB7B0D947AC4@network-heretics.com> <CB106539-9C0F-489C-BBC0-E4ADAF3B8F45@gmail.com> <746A967B-16AF-4428-8424-298AF8001F87@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:25 -0700
Cc: IPv6 Operations <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: Sun, 03 Jul 2011 19:17:47 -0000

>>=20
>>=20
>> 	And b.
>>=20
>> 	And probably it is too much effort for something that will go =
away (probably sooner that we expect) with the exhaustion of IPv4 =
addresses for each ISP's customer (6to4 does not work with NATs, and =
they are here).
>=20
> It's clearly inappropriate for operators to be filtering protocol 41.  =
 Not only does this break 6to4, it also breaks other tunneling =
mechanisms.  More generally, it's inappropriate for operators to be =
favoring one kind of traffic over another.

	Many corporate networks filter them because security concerns (I =
am not saying that is right or wrong, it just happens and it breaks =
6to4). They won't change their mind because 6to4.

>=20
> The ISPs I've talked to tell me that they see no reason why static, =
public IPv4 addresses cannot continue to be given to those that request =
them, indefinitely, as long as they're paying for business service.=20

	Call one not in the USA. China or India perhaps.

-as



From wwwrun@ietfa.amsl.com  Mon Jul  4 08:47:17 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 2490021F8677; Mon,  4 Jul 2011 08:47:17 -0700 (PDT)
From: NomCom Chair <nomcom-chair@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: Nomcom 2011-2012: Third Call for Volunteers 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110704154717.2490021F8677@ietfa.amsl.com>
Date: Mon,  4 Jul 2011 08:47:17 -0700 (PDT)
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:25 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jul 2011 15:47:17 -0000

This is the Third call for Volunteers for the 2011-12 Nomcom.  We are
almost 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 84 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 09:00 EDT on June 29 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 84 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 (Ting ZOU),FutureWei Technologies
Fernando Gont,UTN/FRH
Karen Seo,BBN Technologies
Jie Dong,Huawei Technologies
Mach Chen,Huawei Technologies Co. Ltd.
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 Inc.
Keyur Patel,Cisco Systems
Michael (Mike) Hamilton,BreakingPoint Systems
Behcet Sarikaya,Huawei USA
Mark Townsley,Cisco Systems
Fred Baker,Cisco Systems
Brian Trammell,ETH Zürich
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 Kühlewind,University of Stuttgart IKR
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 L.L.C.
Donald Eastlake,Huawei
Xiaohu Xu,Huawei Technologies co. Ltd.
Börje Ohlman,Ericsson
Deborah Brungard,AT&T
Magnus Westerlund,Ericsson
Zhen Cao,China Mobile
Hadriel Kaplan,Acme Packet
Lilla Dovner,Ericsson
John Jason Brzozowski,Comcast
Jonne Soininen,Renesas Mobile
Javier Ubillos,Swedish Institute of Computer Science
Eric Gray,Ericsson
Thomas Herbst,Silver Spring Networks
Ning Zong,Huawei Technologies
Haibin Song,Huawei Technologies
Yingjie Gu,Huawei Technologies
Hongyu Li,Huawei Technologies
Terry Manderson,ICANN
Ari Keranen,Ericsson
Jouni Korhonen,Nokia Siemens Networks
Bhumip Khasnabish,ZTE USA Inc.
Dapeng Liu,China Mobile
Fangwei Hu,ZTE Corporation
Ole Troan,Cisco
Pascal Thubert,Cisco
Wojciech Dec,Cisco
Gunter Van de Velde,Cisco
Ning So,Verizon Inc./University of Texas at Dallas
Guoman liu,ZTE
Simon Pietro Romano,Meetecho/University of Napoli
Luca Martini,Cisco
Bill VerSteeg,Cisco
Toerless Eckert,Cisco Systems
Joseph Salowey,Cisco Systems

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 very soon.

Thank you in advance for your participation.

Suresh Krishnan
Nomcom Chair 2011-2012
Email: nomcom-chair@ietf.org, suresh.krishnan@ericsson.com

From jricher@mitre.org  Tue Jul  5 06:24:21 2011
Return-Path: <jricher@mitre.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 9FB1D21F86A3; Tue,  5 Jul 2011 06:24:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.793
X-Spam-Level: 
X-Spam-Status: No, score=-5.793 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_URI_CONS7=0.306, URI_NOVOWEL=0.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 YUjK+s18aL2s; Tue,  5 Jul 2011 06:24:20 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 9916C21F85BE; Tue,  5 Jul 2011 06:24:20 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 7E70F21B13FE; Tue,  5 Jul 2011 09:24:19 -0400 (EDT)
Received: from imchub2.MITRE.ORG (imchub2.mitre.org [129.83.29.74]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 78BD921B0457; Tue,  5 Jul 2011 09:24:19 -0400 (EDT)
Received: from [129.83.50.1] (129.83.50.1) by imchub2.MITRE.ORG (129.83.29.74) with Microsoft SMTP Server id 8.3.159.2; Tue, 5 Jul 2011 09:24:19 -0400
Subject: Re: [OAUTH-WG] Second Last Call: <draft-hammer-hostmeta-16.txt> (Web Host Metadata) to Proposed Standard -- feedback
From: Justin Richer <jricher@mitre.org>
To: Eve Maler <eve@xmlgrrl.com>
In-Reply-To: <2F5498A8-CA85-49FE-BEB0-86483868D86D@xmlgrrl.com>
References: <CA35E63A.15F21%eran@hueniverse.com> <2F5498A8-CA85-49FE-BEB0-86483868D86D@xmlgrrl.com>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 5 Jul 2011 09:22:09 -0400
Message-ID: <1309872129.28669.6.camel@ground>
MIME-Version: 1.0
X-Mailer: Evolution 2.32.2 
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:25 -0700
Cc: Mark Nottingham <mnot@mnot.net>, "ietf@ietf.org IETF" <ietf@ietf.org>, Eran Hammer-Lahav <eran@hueniverse.com>, oauth WG <oauth@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2011 13:24:21 -0000

The OpenID Connect folks have been using Simple Web Discovery, which is
as I understand it a rough translation of XRD into JSON, with a couple
of simplifying changes. (Mike, want to throw your hat in on this one?)

http://tools.ietf.org/html/draft-jones-simple-web-discovery-00

 -- Justin

On Mon, 2011-07-04 at 00:27 -0400, Eve Maler wrote:
> FWIW, the "Dynamic OAuth Client Registration" proposal made by the
> User-Managed Access folks:
> 
> 
> http://tools.ietf.org/html/draft-hardjono-oauth-dynreg-00
> 
> 
> ...makes use of XRD, hostmeta, and discovery, as does the OAuth-based
> UMA protocol itself:
> 
> 
> http://www.ietf.org/internet-drafts/draft-hardjono-oauth-umacore-00.txt
> 
> 
> We'd be just as happy to use a JSON-based version of XRD if it can be
> standardized, and we did do some experimentation with this early on.
> But because XRD 1.0 is now stable and is straightforward enough to use
> for our needs, we decided to use it normatively for now. The UMA
> implementation used by http://smartam.net implements this today and it
> works fine.
> 
> 
> Eve
> 
> On 3 Jul 2011, at 9:50 AM, Eran Hammer-Lahav wrote:
> 
> > Hannes,
> > 
> > 
> > None of the current OAuth WG document address discovery in any way,
> > so clearly there will be no use of XRD. But the OAuth community
> > predating the IETF had multiple proposals for it. In addition,
> > multiple times on the IETF OAuth WG list, people have suggested
> > using host-meta and XRD for discovery purposes.
> > 
> > 
> > The idea that XRD was reused without merit is both misleading and
> > mean-spirited. Personally, I'm sick of it, especially coming from
> > standards professionals.
> > 
> > 
> > XRD was largely developed by the same people who worked on
> > host-meta. XRD predated host-meta and was designed to cover the
> > wider use case. Host-meta was an important use case when developing
> > XRD in its final few months. It was done in OASIS out of respect to
> > proper standards process in which the body that originated a work
> > (XRDS) gets to keep it.
> > 
> > 
> > I challenge anyone to find any faults with the IPR policy or process
> > used to develop host-meta in OASIS.
> > 
> > 
> > XRD is one of the simplest XML formats I have seen. I bet most of
> > the people bashing it now have never bothered to read it. At least
> > some of these people have been personally invited by me to comment
> > on XRD while it was still in development and chose to dismiss it.
> > 
> > 
> > XRD was designed in a very open process with plenty of community
> > feedback and it was significantly simplified based on that feedback.
> > In addition, host-meta further simplifies it by profiling it down,
> > removing some of the more complex elements like Subject and Alias
> > (which are very useful in other contexts). XRD is nothing more than
> > a cleaner version of HTML <LINK> elements with literally a handful
> > of new elements based on well defined and widely supported
> > requirements. It's entire semantic meaning is based on the IETF Link
> > relation registry RFC.
> > 
> > 
> > There is something very disturbing going on these days in how people
> > treat XML-based formats, especially form OASIS.
> > 
> > 
> > When host-meta's predecessor - sideâ€“meta â€“ was originally proposed a
> > few years ago, Mark Nottingham proposed an XML format not that
> > different from XRD. There is nothing wrong with JSON taking over as
> > a simpler alternative. I personally prefer JSON much better. But it
> > would be reckless and counter productive to ignore a decade of work
> > on XML formats just because it is no longer cool. Feels like we back
> > in high school.
> > 
> > 
> > If you have technical arguments against host-meta, please share. But
> > if your objections are based on changing trends, dislike of XML or
> > anything OASIS, grow up.
> > 
> > 
> > EHL
> > 
> > 
> > 
> > 
> > 
> > 
> > From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
> > Date: Sun, 3 Jul 2011 00:36:29 -0700
> > To: Mark Nottingham <mnot@mnot.net>
> > Cc: Hannes Tschofenig <hannes.tschofenig@gmx.net>, "ietf@ietf.org
> > IETF" <ietf@ietf.org>, Eran Hammer-lahav <eran@hueniverse.com>,
> > oauth WG <oauth@ietf.org>
> > Subject: Re: Second Last Call: <draft-hammer-hostmeta-16.txt> (Web
> > Host Metadata) to Proposed Standard -- feedback
> > 
> > 
> > 
> > > I also never really understood why XRD was re-used. 
> > > 
> > > 
> > > Btw, XRD is not used by any of the current OAuth WG documents, see
> > > http://datatracker.ietf.org/wg/oauth/
> > > 
> > > 
> > > 
> > > 
> > > On Jun 22, 2011, at 8:08 AM, Mark Nottingham wrote:
> > > 
> > > 
> > > > * 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.
> > > 
> > > 
> > > 
> > > 
> > _______________________________________________
> > OAuth mailing list
> > OAuth@ietf.org
> > https://www.ietf.org/mailman/listinfo/oauth
> 
> 
> Eve Maler                                  http://www.xmlgrrl.com/blog
> +1 425 345 6756                         http://www.twitter.com/xmlgrrl
> 



From david.black@emc.com  Tue Jul  5 07:29:38 2011
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4409E21F85F3; Tue,  5 Jul 2011 07:29:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.037
X-Spam-Level: 
X-Spam-Status: No, score=-104.037 tagged_above=-999 required=5 tests=[AWL=2.562, 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 RetrxpCpF+wp; Tue,  5 Jul 2011 07:29:37 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 480A221F8608; Tue,  5 Jul 2011 07:29:36 -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 p65ETLAC001552 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Jul 2011 10:29:22 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.253]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Tue, 5 Jul 2011 10:29:10 -0400
Received: from mxhub22.corp.emc.com (mxhub22.corp.emc.com [128.221.56.108]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p65ESYH3019126; Tue, 5 Jul 2011 10:28:34 -0400
Received: from mx14a.corp.emc.com ([169.254.1.245]) by mxhub22.corp.emc.com ([128.221.56.108]) with mapi; Tue, 5 Jul 2011 10:28:34 -0400
From: <david.black@emc.com>
To: <tsv-dir@ietf.org>, <tsv-area@ietf.org>, <ietf@ietf.org>, <c.raiciu@cs.ucl.ac.uk>, <m.handley@cs.ucl.ac.uk>, <d.wischik@cs.ucl.ac.uk>
Date: Tue, 5 Jul 2011 10:28:33 -0400
Subject: tsv-dir review of draft-ietf-mptcp-congestion-05
Thread-Topic: tsv-dir review of draft-ietf-mptcp-congestion-05
Thread-Index: Acw7H9G26311hfzYTG+iDWuKZd6Dmw==
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E05893924C1@MX14A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:25 -0700
Cc: multipathtcp@ietf.org, david.black@emc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2011 14:29:38 -0000

I've reviewed this document as part of the transport area directorate's ong=
oing
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 thei=
r
information and to allow them to address any issues raised. The authors sho=
uld
consider this review together with any other last-call comments they receiv=
e.
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 revi=
ew.

Comments:

This draft specifies the congestion control modifications for multi-path TC=
P.

Major:

I have one open issue - the first two goals (in the Introduction) are to ha=
ve multipath
TCP connections behave somewhat like single-path connections in terms of ef=
fects on
(fairness to) other traffic.  The algorithm specified accomplishes this sol=
ely by
coupling the additive increase functionality across the flows, but allowing=
 each flow
to react to drops and congestion separately (no decrease coupling).  The dr=
aft does
not explain why increase coupling along is sufficient to achieve these goal=
s or what
compromise to the goals results from only coupling increases.

Section 5 is a good start on this discussion, but it's not clear about what=
 compromises
to the goals results from increase coupling only.  Section 5 criticizes an =
alternative
that couples both increases and decreases for failing to achieve Goal 1, bu=
t doesn't
say what this approach achieves.  At most a few additional sentences in Sec=
tion 5 should
suffice to address this concern, and Section 2 should be edited to align wi=
th the
changes to Section 5.

Minor:

While the [NSDI] paper is a fine place to reference work published in confe=
rences
and/or journals, RFC 3124 on the Congestion Manager is related IETF work an=
d should
be cited here as an Informative Reference.

idnits 2.12.12 didn't find any nits.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------



From eve@xmlgrrl.com  Sun Jul  3 21:27:45 2011
Return-Path: <eve@xmlgrrl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B36C1F0C57; Sun,  3 Jul 2011 21:27:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.292
X-Spam-Level: 
X-Spam-Status: No, score=-1.292 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FROM_DOMAIN_NOVOWEL=0.5, HTML_MESSAGE=0.001, SARE_URI_CONS7=0.306, URI_NOVOWEL=0.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 39+OtHpzryHO; Sun,  3 Jul 2011 21:27:44 -0700 (PDT)
Received: from promanage-inc.com (eliasisrael.com [50.47.36.5]) by ietfa.amsl.com (Postfix) with ESMTP id 4895F1F0C53; Sun,  3 Jul 2011 21:27:44 -0700 (PDT)
Received: from [192.168.168.185] ([192.168.168.185]) (authenticated bits=0) by promanage-inc.com (8.14.4/8.14.4) with ESMTP id p644RaIQ014047 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 3 Jul 2011 21:27:36 -0700
Subject: Re: [OAUTH-WG] 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: multipart/alternative; boundary=Apple-Mail-246-733974962
From: Eve Maler <eve@xmlgrrl.com>
In-Reply-To: <CA35E63A.15F21%eran@hueniverse.com>
Date: Sun, 3 Jul 2011 21:27:36 -0700
Message-Id: <2F5498A8-CA85-49FE-BEB0-86483868D86D@xmlgrrl.com>
References: <CA35E63A.15F21%eran@hueniverse.com>
To: Eran Hammer-Lahav <eran@hueniverse.com>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Tue, 05 Jul 2011 07:45:58 -0700
Cc: Mark Nottingham <mnot@mnot.net>, "ietf@ietf.org IETF" <ietf@ietf.org>, oauth WG <oauth@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jul 2011 04:27:45 -0000

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

FWIW, the "Dynamic OAuth Client Registration" proposal made by the =
User-Managed Access folks:

http://tools.ietf.org/html/draft-hardjono-oauth-dynreg-00

...makes use of XRD, hostmeta, and discovery, as does the OAuth-based =
UMA protocol itself:

http://www.ietf.org/internet-drafts/draft-hardjono-oauth-umacore-00.txt

We'd be just as happy to use a JSON-based version of XRD if it can be =
standardized, and we did do some experimentation with this early on. But =
because XRD 1.0 is now stable and is straightforward enough to use for =
our needs, we decided to use it normatively for now. The UMA =
implementation used by http://smartam.net implements this today and it =
works fine.

	Eve

On 3 Jul 2011, at 9:50 AM, Eran Hammer-Lahav wrote:

> Hannes,
>=20
> None of the current OAuth WG document address discovery in any way, so =
clearly there will be no use of XRD. But the OAuth community predating =
the IETF had multiple proposals for it. In addition, multiple times on =
the IETF OAuth WG list, people have suggested using host-meta and XRD =
for discovery purposes.
>=20
> The idea that XRD was reused without merit is both misleading and =
mean-spirited. Personally, I'm sick of it, especially coming from =
standards professionals.
>=20
> XRD was largely developed by the same people who worked on host-meta. =
XRD predated host-meta and was designed to cover the wider use case. =
Host-meta was an important use case when developing XRD in its final few =
months. It was done in OASIS out of respect to proper standards process =
in which the body that originated a work (XRDS) gets to keep it.
>=20
> I challenge anyone to find any faults with the IPR policy or process =
used to develop host-meta in OASIS.
>=20
> XRD is one of the simplest XML formats I have seen. I bet most of the =
people bashing it now have never bothered to read it. At least some of =
these people have been personally invited by me to comment on XRD while =
it was still in development and chose to dismiss it.
>=20
> XRD was designed in a very open process with plenty of community =
feedback and it was significantly simplified based on that feedback. In =
addition, host-meta further simplifies it by profiling it down, removing =
some of the more complex elements like Subject and Alias (which are very =
useful in other contexts). XRD is nothing more than a cleaner version of =
HTML <LINK> elements with literally a handful of new elements based on =
well defined and widely supported requirements. It's entire semantic =
meaning is based on the IETF Link relation registry RFC.
>=20
> There is something very disturbing going on these days in how people =
treat XML-based formats, especially form OASIS.
>=20
> When host-meta's predecessor - side=96meta =96 was originally proposed =
a few years ago, Mark Nottingham proposed an XML format not that =
different from XRD. There is nothing wrong with JSON taking over as a =
simpler alternative. I personally prefer JSON much better. But it would =
be reckless and counter productive to ignore a decade of work on XML =
formats just because it is no longer cool. Feels like we back in high =
school.
>=20
> If you have technical arguments against host-meta, please share. But =
if your objections are based on changing trends, dislike of XML or =
anything OASIS, grow up.
>=20
> EHL
>=20
>=20
>=20
> From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
> Date: Sun, 3 Jul 2011 00:36:29 -0700
> To: Mark Nottingham <mnot@mnot.net>
> Cc: Hannes Tschofenig <hannes.tschofenig@gmx.net>, "ietf@ietf.org =
IETF" <ietf@ietf.org>, Eran Hammer-lahav <eran@hueniverse.com>, oauth WG =
<oauth@ietf.org>
> Subject: Re: Second Last Call: <draft-hammer-hostmeta-16.txt> (Web =
Host Metadata) to Proposed Standard -- feedback
>=20
>> I also never really understood why XRD was re-used.
>>=20
>> Btw, XRD is not used by any of the current OAuth WG documents, see =
http://datatracker.ietf.org/wg/oauth/
>>=20
>>=20
>> On Jun 22, 2011, at 8:08 AM, Mark Nottingham wrote:
>>=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
>>=20
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth


Eve Maler                                  http://www.xmlgrrl.com/blog
+1 425 345 6756                         http://www.twitter.com/xmlgrrl


--Apple-Mail-246-733974962
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; =
"><div>FWIW, the "Dynamic OAuth Client Registration" proposal made by =
the User-Managed Access folks:</div><div><br></div><div><a =
href=3D"http://tools.ietf.org/html/draft-hardjono-oauth-dynreg-00">http://=
tools.ietf.org/html/draft-hardjono-oauth-dynreg-00</a></div><div><br></div=
><div>...makes use of XRD, hostmeta, and discovery, as does the =
OAuth-based UMA protocol itself:</div><div><br></div><div><span =
class=3D"Apple-style-span" style=3D"font-family: monospace; "><a =
href=3D"http://www.ietf.org/internet-drafts/draft-hardjono-oauth-umacore-0=
0.txt">http://www.ietf.org/internet-drafts/draft-hardjono-oauth-umacore-00=
.txt</a></span></div><div><br></div><div>We'd be just as happy to use a =
JSON-based version of XRD if it can be standardized, and we did do some =
experimentation with this early on. But because XRD 1.0 is now stable =
and is straightforward enough to use for our needs, we decided to use it =
normatively for now. The UMA implementation used by <a =
href=3D"http://smartam.net">http://smartam.net</a> implements this today =
and it works fine.</div><div><br></div><div><span class=3D"Apple-tab-span"=
 style=3D"white-space:pre">	</span>Eve</div><br><div><div>On 3 Jul =
2011, at 9:50 AM, Eran Hammer-Lahav 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; color: rgb(0, 0, 0); font-size: =
14px; font-family: Calibri, sans-serif; =
"><div>Hannes,</div><div><br></div><div>None of the current OAuth WG =
document address discovery in any way, so clearly there will be no use =
of XRD. But the OAuth community predating the IETF had multiple =
proposals for it. In addition, multiple times on the IETF OAuth WG list, =
people have suggested using host-meta and XRD for discovery =
purposes.</div><div><br></div><div>The idea that XRD was reused without =
merit is both misleading and mean-spirited. Personally, I'm sick of it, =
especially coming from standards =
professionals.</div><div><br></div><div>XRD was largely developed by the =
same people who worked on host-meta. XRD predated host-meta and was =
designed to cover the wider use case. Host-meta was an important use =
case when developing XRD in its final few months. It was done in OASIS =
out of respect to proper standards process in which the body that =
originated a work (XRDS) gets to keep it.</div><div><br></div><div>I =
challenge anyone to find any faults with the IPR policy or process used =
to develop host-meta in OASIS.</div><div><br></div><div>XRD is one of =
the simplest XML formats I have seen. I bet most of the people bashing =
it now have never bothered to read it. At least some of these people =
have been personally invited by me to comment on XRD while it was still =
in development and chose to dismiss it.</div><div><br></div><div>XRD was =
designed in a very open process with plenty of community feedback and it =
was significantly simplified based on that feedback. In addition, =
host-meta further simplifies it by profiling it down, removing some of =
the more complex elements like Subject and Alias (which are very useful =
in other contexts). XRD is nothing more than a cleaner version of HTML =
&lt;LINK&gt; elements with literally a handful of new elements based on =
well defined and widely supported requirements. It's entire semantic =
meaning is based on the IETF Link relation registry =
RFC.</div><div><br></div><div>There is something very disturbing going =
on these days in how people treat XML-based formats, especially form =
OASIS.</div><div><br></div><div>When host-meta's predecessor - side=96meta=
 =96 was originally proposed a few years ago, Mark Nottingham proposed =
an XML format not that different from XRD.&nbsp;There is nothing wrong =
with JSON taking over as a simpler alternative. I personally prefer JSON =
much better. But it would be reckless and counter productive to ignore a =
decade of work on XML formats just because it is no longer cool. Feels =
like we back in high school.</div><div><br></div><div>If you have =
technical arguments against host-meta, please share. But if your =
objections are based on changing trends, dislike of XML or anything =
OASIS, grow =
up.</div><div><br></div><div>EHL</div><div><br></div><div><br></div><div><=
br></div><span id=3D"OLK_SRC_BODY_SECTION"><div =
style=3D"font-family:Calibri; font-size:11pt; text-align:left; =
color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; =
PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: =
#b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span =
style=3D"font-weight:bold">From: </span> Hannes Tschofenig &lt;<a =
href=3D"mailto:hannes.tschofenig@gmx.net">hannes.tschofenig@gmx.net</a>&gt=
;<br><span style=3D"font-weight:bold">Date: </span> Sun, 3 Jul 2011 =
00:36:29 -0700<br><span style=3D"font-weight:bold">To: </span> Mark =
Nottingham &lt;<a =
href=3D"mailto:mnot@mnot.net">mnot@mnot.net</a>&gt;<br><span =
style=3D"font-weight:bold">Cc: </span> Hannes Tschofenig &lt;<a =
href=3D"mailto:hannes.tschofenig@gmx.net">hannes.tschofenig@gmx.net</a>&gt=
;, "<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> IETF" &lt;<a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;, Eran Hammer-lahav =
&lt;<a href=3D"mailto:eran@hueniverse.com">eran@hueniverse.com</a>&gt;, =
oauth WG &lt;<a =
href=3D"mailto:oauth@ietf.org">oauth@ietf.org</a>&gt;<br><span =
style=3D"font-weight:bold">Subject: </span> Re: Second Last Call: =
&lt;draft-hammer-hostmeta-16.txt&gt; (Web Host Metadata) to Proposed =
Standard -- feedback<br></div><div><br></div><blockquote =
id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT: #b5c4df =
5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;" type=3D"cite"><div><div><div>I =
also never really understood why XRD was re-used. =
</div><div><br></div><div>Btw, XRD is not used by any of the current =
OAuth WG documents, see <a =
href=3D"http://datatracker.ietf.org/wg/oauth/">http://datatracker.ietf.org=
/wg/oauth/</a></div><div><br></div><div><br></div><div>On Jun 22, 2011, =
at 8:08 AM, Mark Nottingham wrote:</div><div><br></div><blockquote =
id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT: #b5c4df =
5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;" type=3D"cite"><div> * 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.</div></blockquote><div><br></div><div><br></div></div></div></b=
lockquote></span></div>
_______________________________________________<br>OAuth mailing =
list<br><a =
href=3D"mailto:OAuth@ietf.org">OAuth@ietf.org</a><br>https://www.ietf.org/=
mailman/listinfo/oauth<br></blockquote></div><br><div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: medium; 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; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Courier; font-size: 12px; 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; "><div><br =
class=3D"Apple-interchange-newline">Eve Maler &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;<a =
href=3D"http://www.xmlgrrl.com/blog">http://www.xmlgrrl.com/blog</a></div>=
<div>+1 425 345 6756 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a =
href=3D"http://www.twitter.com/xmlgrrl">http://www.twitter.com/xmlgrrl</a>=
</div></span></div></span></div></span></div></span></div>
</div>
<br></body></html>=

--Apple-Mail-246-733974962--

From ipng@69706e6720323030352d30312d31340a.nosense.org  Sat Jul  2 17:38:52 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 4290D11E80DE; Sat,  2 Jul 2011 17:38:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.295
X-Spam-Level: 
X-Spam-Status: No, score=-1.295 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NMV5UKTkdx0I; Sat,  2 Jul 2011 17:38:51 -0700 (PDT)
Received: from smtp4.adam.net.au (smtp4.adam.net.au [202.136.110.247]) by ietfa.amsl.com (Postfix) with ESMTP id 73ACC11E809D; Sat,  2 Jul 2011 17:38:51 -0700 (PDT)
Received: from 114-30-101-21.ip.adam.com.au ([114.30.101.21] helo=opy.nosense.org) by smtp4.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1QdAhy-0007Mt-7a; Sun, 03 Jul 2011 10:08:46 +0930
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 519D13B33E; Sun,  3 Jul 2011 10:08:45 +0930 (CST)
Date: Sun, 3 Jul 2011 10:08:44 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Message-ID: <20110703100844.68eb8b7d@opy.nosense.org>
In-Reply-To: <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com>
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; 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: Tue, 05 Jul 2011 07:46:17 -0700
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 00:38:52 -0000

On Sat, 2 Jul 2011 20:54:50 +0200
Lorenzo Colitti <lorenzo@google.com> wrote:

> On Sat, Jul 2, 2011 at 6:36 PM, Ronald Bonica <rbonica@juniper.net> wrote:
> 
> > - In order for the new draft to be published, it must achieve both V6OPS WG
> > and IETF consensus
> >
> > If anyone objects to this course of action, please speak up soon.
> >
> 
> Great, back to square one.
> 
> Is the reasoning behind the decision explained somewhere? My reading of the
> threads on the subject in v6ops was that the opposition to 6to4-historic was
> a small but vocal minority, and I thought that qualified as rough consensus.
> But perhaps I missed some discussion.
> 
> Also, why do the author and the chairs think that the new draft will do any
> better than 6to4-historic? I would assume that the same people who spoke up
> against 6to4-historic will speak up against the new document, and since that
> level of opposition was sufficient to prevent the publication
> of 6to4-historic, it may be sufficient to prevent publication of the new
> document as well. If so, we will have spent 3-6 months arguing about it for
> naught.
> 

I don't object to what has been proposed, yet I object to
"6to4-historic" because I'm an extremely happy anycast 6to4 user and
have been for many years (I just recently looked at the date in the
script I wrote to bring it up, and was quite surprised it was dated
2002). 

Unfortunately people do judge books by their cover - if there is an RFC
that says 6to4 is historic, people would likely consider it something
that can't be used. We know it can operate correctly and reliably if it
is configured correctly. If the criteria for declaring a
technology historic is that some people can't operate it correctly and
reliably, then they'll have to be plenty of other -historic RFCs.

Perhaps declaring 6to4 deprecated rather than historic would have a
better chance of consensus.


> Please, nobody answer this question with "welcome to the IETF" :-)

From ipng@69706e6720323030352d30312d31340a.nosense.org  Sat Jul  2 18:50:57 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 02F2B21F8674; Sat,  2 Jul 2011 18:50:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.295
X-Spam-Level: 
X-Spam-Status: No, score=-1.295 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mdSVT3KqeyRi; Sat,  2 Jul 2011 18:50:56 -0700 (PDT)
Received: from smtp4.adam.net.au (smtp4.adam.net.au [202.136.110.247]) by ietfa.amsl.com (Postfix) with ESMTP id 72BC421F8673; Sat,  2 Jul 2011 18:50:55 -0700 (PDT)
Received: from 114-30-101-21.ip.adam.com.au ([114.30.101.21] helo=opy.nosense.org) by smtp4.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1QdBph-0000mM-Jl; Sun, 03 Jul 2011 11:20:49 +0930
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 18B663B33E; Sun,  3 Jul 2011 11:20:49 +0930 (CST)
Date: Sun, 3 Jul 2011 11:20:48 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Cameron Byrne <cb.list6@gmail.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Message-ID: <20110703112048.4a3c7111@opy.nosense.org>
In-Reply-To: <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com>
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; 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: Tue, 05 Jul 2011 07:46:17 -0700
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 01:50:57 -0000

On Sat, 2 Jul 2011 12:21:36 -0700
Cameron Byrne <cb.list6@gmail.com> wrote:

> On Jul 2, 2011 11:55 AM, "Lorenzo Colitti" <lorenzo@google.com> wrote:
> >
> > On Sat, Jul 2, 2011 at 6:36 PM, Ronald Bonica <rbonica@juniper.net> wrote:
> >>
> >> - In order for the new draft to be published, it must achieve both V6OPS
> WG and IETF consensus
> >>
> >> If anyone objects to this course of action, please speak up soon.
> >
> >
> > Great, back to square one.
> >
> > Is the reasoning behind the decision explained somewhere? My reading of
> the threads on the subject in v6ops was that the opposition to 6to4-historic
> was a small but vocal minority, and I thought that qualified as rough
> consensus. But perhaps I missed some discussion.
> >
> 
> I saw the same thing. It is a shame that work that directly removes barriers
> to REAL ipv6 deployment 

Where is the evidence that 6to4 is holding back native IPv6 
deployment?


> gets shouted down by a few people not involved in
> REAL ipv6 deployment.
> 

How do you know that?



> Welcome to the ietf indeed.
> 
> Cb
> 
> > Also, why do the author and the chairs think that the new draft will do
> any better than 6to4-historic? I would assume that the same people who spoke
> up against 6to4-historic will speak up against the new document, and since
> that level of opposition was sufficient to prevent the publication
> of 6to4-historic, it may be sufficient to prevent publication of the new
> document as well. If so, we will have spent 3-6 months arguing about it for
> naught.
> >
> > Please, nobody answer this question with "welcome to the IETF" :-)
> >
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
> >

From ipng@69706e6720323030352d30312d31340a.nosense.org  Sat Jul  2 18:54: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 7B21A1F0C55; Sat,  2 Jul 2011 18:54:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.595
X-Spam-Level: 
X-Spam-Status: No, score=-1.595 tagged_above=-999 required=5 tests=[AWL=0.300,  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 zMgCGBw82k+I; Sat,  2 Jul 2011 18:54:22 -0700 (PDT)
Received: from smtp4.adam.net.au (smtp4.adam.net.au [202.136.110.247]) by ietfa.amsl.com (Postfix) with ESMTP id DA3781F0C51; Sat,  2 Jul 2011 18:54:21 -0700 (PDT)
Received: from 114-30-101-21.ip.adam.com.au ([114.30.101.21] helo=opy.nosense.org) by smtp4.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1QdBt6-0000qE-Nm; Sun, 03 Jul 2011 11:24:20 +0930
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 64AD73B33E; Sun,  3 Jul 2011 11:24:20 +0930 (CST)
Date: Sun, 3 Jul 2011 11:24:20 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Erik Kline <ek@google.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Message-ID: <20110703112420.3fcaa58c@opy.nosense.org>
In-Reply-To: <CAAedzxpCsxW2zJtpGa9HRMRACkK1defrt2g2Xao_y0f7qevvkA@mail.gmail.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <20110703100844.68eb8b7d@opy.nosense.org> <CAAedzxpCsxW2zJtpGa9HRMRACkK1defrt2g2Xao_y0f7qevvkA@mail.gmail.com>
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; 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: Tue, 05 Jul 2011 07:46:17 -0700
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 01:54:22 -0000

On Sun, 3 Jul 2011 10:10:03 +0900
Erik Kline <ek@google.com> wrote:

> All,
> 
> > Perhaps declaring 6to4 deprecated rather than historic would have a
> > better chance of consensus.
> 
> Pardon my ignorance, but where is the document describing the
> implications of historic{,al} vs deprecated?
> 
> This (http://tools.ietf.org/html/rfc2026#section-4.2.4) is well known:
> 
> """
>    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.  (Purists have suggested that the
>    word should be "Historical"; however, at this point the use of
>    "Historic" is historical.)
> 
>    Note: Standards track specifications normally must not depend on
>    other standards track specifications which are at a lower maturity
>    level or on non standards track specifications other than referenced
>    specifications from other standards bodies.  (See Section 7.)
> """
> 
> I don't know where similar explanatory language about "Deprecated"
> might be (I'm sure I just didn't search correctly or long enough).

Since 6rd depends on 6to4, as it is a variant of it, would 6to4 being
declared historic also mean that 6rd needs to become historic as well?


From ipng@69706e6720323030352d30312d31340a.nosense.org  Sat Jul  2 20:49:24 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 81C0621F8678; Sat,  2 Jul 2011 20:49:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.695
X-Spam-Level: 
X-Spam-Status: No, score=-1.695 tagged_above=-999 required=5 tests=[AWL=0.200,  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 xqsvqoYUrGIB; Sat,  2 Jul 2011 20:49:24 -0700 (PDT)
Received: from smtp4.adam.net.au (smtp4.adam.net.au [202.136.110.247]) by ietfa.amsl.com (Postfix) with ESMTP id AB9DC21F8677; Sat,  2 Jul 2011 20:49:23 -0700 (PDT)
Received: from 114-30-101-21.ip.adam.com.au ([114.30.101.21] helo=opy.nosense.org) by smtp4.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1QdDgJ-0003Mr-BE; Sun, 03 Jul 2011 13:19:15 +0930
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 297233B33E; Sun,  3 Jul 2011 13:19:14 +0930 (CST)
Date: Sun, 3 Jul 2011 13:19:13 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Message-ID: <20110703131913.28142ec0@opy.nosense.org>
In-Reply-To: <4E0FD788.3000305@dougbarton.us>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com> <20110703112048.4a3c7111@opy.nosense.org> <4E0FD788.3000305@dougbarton.us>
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; 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: Tue, 05 Jul 2011 07:46:17 -0700
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 03:49:24 -0000

On Sat, 02 Jul 2011 19:44:24 -0700
Doug Barton <dougb@dougbarton.us> wrote:

> On 07/02/2011 18:50, Mark Smith wrote:
> > Where is the evidence that 6to4 is holding back native IPv6
> > deployment?
> 
> It's been discussed ad nauseum in numerous fora.

Discussion isn't evidence, as people usually don't post any data to
support their assertions.

Since posting that question I remembered RFC6036 -
"Emerging Service Provider Scenarios for IPv6 Deployment". Here's what
is says about ISPs' views on 6to4. I don't think it supports the
assertion that 6to4 is holding back native deployment -

"2.5.  IPv6 Technologies

   Turning to technology choices, the overwhelming choice of approach
   (94%) is a dual-stack routing backbone, and the reason given is
   simplicity and cost. 39% run, or plan to run, a 6to4 relay as well,
   and 16% run or plan a Teredo server. "

"Diffusions of Innovations" discusses attributes of innovations that
influence their adoption. One of those attributes is trialability,
meaning how hard or easy is it to trial the innovation. If a
innovation requires a high level of commitment to trial, then it is
less likely to be trialed and therefore adopted. Once an residential
ISP as IPv6 transit, 6to4 is a simple and much lower cost way of
trialing IPv6 services and gaining experience with IPv6, before and
during the development and deployment of native IPv6 services and the
required supporting infrastructure, such as AAA, helpdesk training etc.

Declaring 6to4 to be historic might encourage native IPv6 deployment,
but I think it will also make trialing IPv6 much harder.

 Bad 6to4 (which almost 
>> all of it is) results in a poor user experience when the largest content 
> providers enable AAAA records. Thus, they are less inclined to enable them.
> 

The involvement in World IPv6 day by large content providers and the
apparent lack of significant problems would be suggest the opposite is
now the case. Google continuing to provide youtube video content to 6to4
tunnel users (such as myself), nearly a month later, suggests that any
problems with it are tractable. 6to4 users are easy to spot by the
2002::/16 prefix, so if Google needed to they could probably quite
easily limit their IPv6 content delivery to native only IPv6 users.
So, in other words, Google now consider 6to4 to be reliable enough to
continue to deliver content using it for one of their high profile
content sites.

> I realize that there are a lot of people that dismiss both the evidence 
> that's been put forward and the rationale, but it's been presented and 
> discussed pretty thoroughly.
> 

In Geoff Huston's report (Dec 2010), he says that he measured a 13%
failure rate with 6to4. A number of things have happened since then -
IANA has run out of IPv4 addresses, and World IPv6 day. Those two
events have increased the interest in IPv6 (the residential IPv6 trial
I was working on gained more participants due to these events),
which would have created an incentive for people to improve the quality
of their 6to4 operation, or possibly deploy a trial 6to4 relay. An
update on that data would be useful.


Regards,
Mark.

From ipng@69706e6720323030352d30312d31340a.nosense.org  Sat Jul  2 21:45:24 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 6A5CC11E809E; Sat,  2 Jul 2011 21:45:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.445
X-Spam-Level: 
X-Spam-Status: No, score=-1.445 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lJ5d6Z0gXW34; Sat,  2 Jul 2011 21:45:24 -0700 (PDT)
Received: from smtp4.adam.net.au (smtp4.adam.net.au [202.136.110.247]) by ietfa.amsl.com (Postfix) with ESMTP id 59A0711E8078; Sat,  2 Jul 2011 21:45:23 -0700 (PDT)
Received: from 114-30-101-21.ip.adam.com.au ([114.30.101.21] helo=opy.nosense.org) by smtp4.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1QdEYa-0004kz-Rw; Sun, 03 Jul 2011 14:15:20 +0930
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id A51C03B33E; Sun,  3 Jul 2011 14:15:19 +0930 (CST)
Date: Sun, 3 Jul 2011 14:15:19 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Cameron Byrne <cb.list6@gmail.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Message-ID: <20110703141519.1bb90022@opy.nosense.org>
In-Reply-To: <CAD6AjGTN0bi20TjidwwXeHB=CPyBSZWB4=Lka2YG-5FG4Y1+Pw@mail.gmail.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com> <E817A524-9DB7-4553-A76F-25A9907E7C2D@network-heretics.com> <CAD6AjGTN0bi20TjidwwXeHB=CPyBSZWB4=Lka2YG-5FG4Y1+Pw@mail.gmail.com>
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; 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: Tue, 05 Jul 2011 07:46:17 -0700
Cc: "v6ops@ietf.org" <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: Sun, 03 Jul 2011 04:45:24 -0000

On Sat, 2 Jul 2011 21:02:02 -0700
Cameron Byrne <cb.list6@gmail.com> wrote:

<snip>
> In the meantime, i null route the 6to4 anycast address because it
> creates half open state in my CGN.  Been doing that for at least 5
> years.


So, to be clear, you're not making an observation that 6to4 is broken,
based on measurement or actual use, you're actively breaking it.

>  My next step is filtering AAAA over IPv4 access because 6to4
> client brokeness won't die on its own, that will be rolled out in a
> few months.  Operating a network means making the tweeks that keep the
> wheels rolling, and we don't find many technology purist in my line of
> work.
> 

I think the root cause of your issues is the deployment of IPv4 CGN in
the first place before IANA and the RIRs ran out of IPv4 addresses by
the sounds of it. I think then means that any protocol that your
customers try to use that would create unwanted state in your IPv4 CGN
should be, by your definition, declared "historic", not just 6to4. When
a customer signs up to your service, are they informed as to which
protocols and applications they are allowed to use? My opinion is that
if there are restrictions on what protocols and applications customers
can operate then their service is not a real Internet service. The
majority of, if not all, residential broadband service providers in my
market hold the same belief - it seems to be the "pure" mobile
carriers that commonly don't.

> Other access providers like 6to4 so much that they want to NAT it.
> This is the reason why historic is the proper term.
> 
> http://tools.ietf.org/html/draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-02
> 
> I look forward to that discussion on ietf@
> 
> Cameron
> 
> 
> > Keith
> >
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

From ipng@69706e6720323030352d30312d31340a.nosense.org  Sun Jul  3 00:04:48 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 28E9421F879E; Sun,  3 Jul 2011 00:04:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.415
X-Spam-Level: 
X-Spam-Status: No, score=-1.415 tagged_above=-999 required=5 tests=[AWL=-0.120, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QLoDARWKoUHq; Sun,  3 Jul 2011 00:04:47 -0700 (PDT)
Received: from smtp4.adam.net.au (smtp4.adam.net.au [202.136.110.247]) by ietfa.amsl.com (Postfix) with ESMTP id 9BBB321F879A; Sun,  3 Jul 2011 00:04:46 -0700 (PDT)
Received: from 114-30-101-21.ip.adam.com.au ([114.30.101.21] helo=opy.nosense.org) by smtp4.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1QdGjM-00005z-Bb; Sun, 03 Jul 2011 16:34:36 +0930
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id E80563B33E; Sun,  3 Jul 2011 16:34:35 +0930 (CST)
Date: Sun, 3 Jul 2011 16:34:35 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Joel Jaeggli <joelja@bogus.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Message-ID: <20110703163435.681cdfe3@opy.nosense.org>
In-Reply-To: <BEEDDF78-7E0A-4B44-A2F5-49E70BF2D8F2@bogus.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com> <E817A524-9DB7-4553-A76F-25A9907E7C2D@network-heretics.com> <CAD6AjGTN0bi20TjidwwXeHB=CPyBSZWB4=Lka2YG-5FG4Y1+Pw@mail.gmail.com> <20110703141519.1bb90022@opy.nosense.org> <BEEDDF78-7E0A-4B44-A2F5-49E70BF2D8F2@bogus.com>
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; 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: Tue, 05 Jul 2011 07:46:17 -0700
Cc: IETF Discussion <ietf@ietf.org>, "v6ops@ietf.org" <v6ops@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: Sun, 03 Jul 2011 07:04:48 -0000

On Sat, 2 Jul 2011 21:59:24 -0700
Joel Jaeggli <joelja@bogus.com> wrote:

> This line of discussion is not productive... 
> 
> Between them the 4 largest north american wireless carriers need ~18 /8s to assign public ipv4 addresses to their wireless cpe...
> they don't have that and there's no-where to get it, then there's the
> rest of the world.

That's now, but what about when they chose to implement IPv4 CGN,
likely to be years ago.

>  

Cameron is choosing to blame 6to4 for a problem that any of the
stateless and/or unidirectional Internet protocols could cause on a
IPv4 CGN. His arguments to make 6to4 historic are not based on issues
specific to 6to4. If 6to4 is made historic, does he then start lobbying
for UDP-historic?

> On Jul 2, 2011, at 9:45 PM, Mark Smith wrote:
> 
> > On Sat, 2 Jul 2011 21:02:02 -0700
> > Cameron Byrne <cb.list6@gmail.com> wrote:
> > 
> > <snip>
> >> In the meantime, i null route the 6to4 anycast address because it
> >> creates half open state in my CGN.  Been doing that for at least 5
> >> years.
> > 
> > 
> > So, to be clear, you're not making an observation that 6to4 is broken,
> > based on measurement or actual use, you're actively breaking it.
> > 
> >> My next step is filtering AAAA over IPv4 access because 6to4
> >> client brokeness won't die on its own, that will be rolled out in a
> >> few months.  Operating a network means making the tweeks that keep the
> >> wheels rolling, and we don't find many technology purist in my line of
> >> work.
> >> 
> > 
> > I think the root cause of your issues is the deployment of IPv4 CGN in
> > the first place before IANA and the RIRs ran out of IPv4 addresses by
> > the sounds of it. I think then means that any protocol that your
> > customers try to use that would create unwanted state in your IPv4 CGN
> > should be, by your definition, declared "historic", not just 6to4. When
> > a customer signs up to your service, are they informed as to which
> > protocols and applications they are allowed to use? My opinion is that
> > if there are restrictions on what protocols and applications customers
> > can operate then their service is not a real Internet service. The
> > majority of, if not all, residential broadband service providers in my
> > market hold the same belief - it seems to be the "pure" mobile
> > carriers that commonly don't.
> > 
> >> Other access providers like 6to4 so much that they want to NAT it.
> >> This is the reason why historic is the proper term.
> >> 
> >> http://tools.ietf.org/html/draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-02
> >> 
> >> I look forward to that discussion on ietf@
> >> 
> >> Cameron
> >> 
> >> 
> >>> Keith
> >>> 
> >> _______________________________________________
> >> v6ops mailing list
> >> v6ops@ietf.org
> >> https://www.ietf.org/mailman/listinfo/v6ops
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
> > 
> 

From prvs=1167ce3bfc=jordi.palet@consulintel.es  Tue Jul  5 07:48:43 2011
Return-Path: <prvs=1167ce3bfc=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 891E921F863E for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 07:48: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 2qbozqrH5U6n for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 07:48:42 -0700 (PDT)
Received: from consulintel.es (mail.consulintel.es [213.172.48.142]) by ietfa.amsl.com (Postfix) with ESMTP id D056021F85D0 for <ietf@ietf.org>; Tue,  5 Jul 2011 07:48:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1309876816; x=1310481616; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: In-Reply-To:Mime-version:Content-type:Content-transfer-encoding: Reply-To; bh=BDqszopNSNI2pVZ0CXwgZCM0ISVTKGnVhO4f15vkHIQ=; b=bPM O31ah9jxXeY+eiqU63gg7sXBsG4JmKdlZKqPqb3bwObUuFHMpR+d5ZlvEahbx+yD 5mkiOkHoz1wNHwy4GlR1ZYxFxpFm3hUAzvcpvoOKqtH7TtVKLIt/Ad6L73ihqDrV yOZX34tH93igET6yh1ld68ynCzu9JROf+193CxVU=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=gT/kLITFgB1lKJiorbnEZ+d9fbAol8dlhJ+kHRmIcb7qSvNgOlvnEaiq4+Df QVp0wQJ76Uu/XzkIlSjo+qIAZEH2kPgV/zhbzbjA7srqcmbDNechp6hA4 KcC0jl9+amDbOGhJF/83YXjvYJ2TZEI8vVVV6DV3V3N+TJKcY1jwRI=;
X-MDAV-Processed: consulintel.es, Tue, 05 Jul 2011 16:40:16 +0200
Received: from [10.10.10.115] by consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50003935825.msg for <ietf@ietf.org>; Tue, 05 Jul 2011 16:40:15 +0200
X-Spam-Processed: consulintel.es, Tue, 05 Jul 2011 16:40:15 +0200 (not processed: message from trusted or authenticated source)
X-MDPtrLookup-Result: pass dns.ptr=160.red-217-126-187.staticip.rima-tde.net (ip=217.126.187.160) (consulintel.es)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:110705:md50003935825::MLc8n3tweF3ZVEPS:00002FVv
X-MDRemoteIP: 217.126.187.160
X-Return-Path: prvs=1167ce3bfc=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/14.12.0.110505
Date: Tue, 05 Jul 2011 16:47:59 +0200
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <CA38F05C.45888%jordi.palet@consulintel.es>
Thread-Topic: [v6ops] draft-ietf-v6ops-6to4-to-historic
In-Reply-To: <20110705144429.DDFE218C10A@mercury.lcs.mit.edu>
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
Reply-To: jordi.palet@consulintel.es
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2011 14:48:43 -0000

Totally agree.

Regardless of my position on this specific draft, if it has been declared
"no consensus", now it not wise to go forward, declare consensus and
accept the appeal.

Credibility is first.

Regards,
Jordi






-----Mensaje original-----
De: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Responder a: <jnc@mercury.lcs.mit.edu>
Fecha: Tue,  5 Jul 2011 10:44:29 -0400 (EDT)
Para: <ietf@ietf.org>, <v6ops@ietf.org>
CC: <jnc@mercury.lcs.mit.edu>
Asunto: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic

>    > From: Ronald Bonica <rbonica@juniper.net>
>
>    >>> I think that I get it. There is no IETF consensus regarding the
>    >>> compromise proposed below. ...
>
>    >> But there is no rough consensus to do that either.
>
>    > That is the claim of an appeal on the table. Let's run the appeal
>    > process and figure out whether that claim is valid.
>
>Sorry, this makes no sense.
>
>You can't go ahead with draft-ietf-v6ops-6to4-to-historic if there is no
>basic consensus in the IETF as a whole to do so - and your previous
>declaration (on Saturday) basically accepted that there was no such basic
>consensus (otherwise why withdraw the ID).
>
>So now there is going to be a reversal, and the document is going to go
>ahead
>- i.e. you must now be taking the position that there _is_ basic
>consensus in
>the IETF (without which you could not proceed the ID).
>
>The effect of this sort of thing on the reputation of I* should be obvious
>to all.
>
>	Noel
>_______________________________________________
>v6ops mailing list
>v6ops@ietf.org
>https://www.ietf.org/mailman/listinfo/v6ops



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




From johnl@iecc.com  Tue Jul  5 08:06:42 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 1C05311E81B7 for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 08:06:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.567
X-Spam-Level: 
X-Spam-Status: No, score=-102.567 tagged_above=-999 required=5 tests=[AWL=0.033, 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 fOFQjY8STJPQ for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 08:06:41 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 39A6511E8120 for <ietf@ietf.org>; Tue,  5 Jul 2011 08:06:23 -0700 (PDT)
Received: (qmail 33704 invoked from network); 5 Jul 2011 15:06:21 -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=83a7.4e13286d.k1107; bh=M0j+lit/BSIu5bUv48nWzHeE+Ytt4idKMJ5kAaxdyH4=; b=zryoIfa7Us5clfXjTtddczlY70P4l6JUt5XKQCTJza6+ocpnTIYr6tPEytfk18N4v1VyVgvyyT3afPt9ewCLH+jqTQ2LD9Oe/299+hLcgYXkwGA87g8F7XTgCHSTLsQs/Eo/4nnaTvkaqwOzEQRjnYWnOE+11/6jtydFw2XgmDE=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1) with (DHE-RSA-AES256-SHA encrypted) SMTP; 5 Jul 2011 15:05:59 -0000
Date: 5 Jul 2011 11:06:20 -0400
Message-ID: <alpine.BSF.2.00.1107051105040.77861@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Tony Finch" <dot@dotat.at>
Subject: Re: Comments surrounding draft-iab-dns-applications-01
In-Reply-To: <alpine.LSU.2.00.1107051152550.5578@hermes-2.csi.cam.ac.uk>
References: <20110429023630.46187.qmail@joyce.lan> <4E116ED8.10506@250bpm.com> <alpine.BSF.2.00.1107040940090.60353@joyce.lan> <20110704231442.023081171247@drugs.dv.isc.org> <alpine.BSF.2.00.1107041959400.29602@joyce.lan> <20110705005640.D3F52117252B@drugs.dv.isc.org> <alpine.BSF.2.00.1107042151340.62218@joyce.lan> <20110705030537.9EE7711730B5@drugs.dv.isc.org> <alpine.LSU.2.00.1107051152550.5578@hermes-2.csi.cam.ac.uk>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2011 15:06:42 -0000

>> The naive approach of reversing the address, converting to nibbles
>> and appending a suffix won't scale.
>
> I don't understand why the setup is OK for reverse DNS but not blacklists.

One obvious reason is that the most widely used DNSBL server doesn't 
return NODATA vs. NXDOMAIN according to current standards, so probing and 
NXDOMAIN synthesis doesn't work.  I'm planning to fix it, but it'll take a 
while.

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 rbonica@juniper.net  Tue Jul  5 08:07:55 2011
Return-Path: <rbonica@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F35B11E820E; Tue,  5 Jul 2011 08:07:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.532
X-Spam-Level: 
X-Spam-Status: No, score=-106.532 tagged_above=-999 required=5 tests=[AWL=0.067, 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 4fI4iCOFAtXt; Tue,  5 Jul 2011 08:07:53 -0700 (PDT)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by ietfa.amsl.com (Postfix) with ESMTP id 757DF11E820A; Tue,  5 Jul 2011 08:07:48 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKThMowztdvlvk2XyYYlZxBq+jbMrp+jrv@postini.com; Tue, 05 Jul 2011 08:07:50 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.2.254.0; Tue, 5 Jul 2011 08:06:28 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Tue, 5 Jul 2011 11:06:27 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, "ietf@ietf.org" <ietf@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Date: Tue, 5 Jul 2011 11:06:26 -0400
Subject: RE: draft-ietf-v6ops-6to4-to-historic
Thread-Topic: draft-ietf-v6ops-6to4-to-historic
Thread-Index: Acw7Ig2WKjysH42vSV2T3QH35x31TQAASRQQ
Message-ID: <13205C286662DE4387D9AF3AC30EF456D3F3508430@EMBX01-WF.jnpr.net>
References: <20110705144429.DDFE218C10A@mercury.lcs.mit.edu>
In-Reply-To: <20110705144429.DDFE218C10A@mercury.lcs.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: Tue, 05 Jul 2011 15:07:55 -0000

Noel,

I didn't say that I was going to push draft-ietf-v6ops-6to4-to-historic thr=
ough without running the process. I said that draft-ietf-v6ops-6to4-to-hist=
oric has made it all the way past IESG approval. There is an appeal on the =
table (at the WG level) questioning whether draft-ietf-v6ops-6to4-to-histor=
ic ever had WG consensus. We will run the appeal process. If the WG chairs =
cannot justify WG consensus, draft-ietf-v6ops-6to4-to-historic stops dead i=
n its tracks. If they can justify WG consensus, the appellant can escalate =
the appeal to the IESG (and to the IAB after that). If the appeal succeeds =
at any level, draft-ietf-v6ops-6to4-to-historic is not published.

                                                               Ron


-----Original Message-----
From: Noel Chiappa [mailto:jnc@mercury.lcs.mit.edu]=20
Sent: Tuesday, July 05, 2011 10:44 AM
To: ietf@ietf.org; v6ops@ietf.org
Cc: jnc@mercury.lcs.mit.edu
Subject: RE: draft-ietf-v6ops-6to4-to-historic

    > From: Ronald Bonica <rbonica@juniper.net>

    >>> I think that I get it. There is no IETF consensus regarding the
    >>> compromise proposed below. ...

    >> But there is no rough consensus to do that either.

    > That is the claim of an appeal on the table. Let's run the appeal
    > process and figure out whether that claim is valid.

Sorry, this makes no sense.

You can't go ahead with draft-ietf-v6ops-6to4-to-historic if there is no
basic consensus in the IETF as a whole to do so - and your previous
declaration (on Saturday) basically accepted that there was no such basic
consensus (otherwise why withdraw the ID).

So now there is going to be a reversal, and the document is going to go ahe=
ad
- i.e. you must now be taking the position that there _is_ basic consensus =
in
the IETF (without which you could not proceed the ID).

The effect of this sort of thing on the reputation of I* should be obvious
to all.

	Noel

From dhc2@dcrocker.net  Tue Jul  5 09:30:16 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 0FD2A11E80C8 for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 09:30:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zTRvg4fshUN9 for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 09:30:15 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1DB0C11E808F for <ietf@ietf.org>; Tue,  5 Jul 2011 09:30:15 -0700 (PDT)
Received: from [192.168.1.156] (adsl-67-124-149-98.dsl.pltn13.pacbell.net [67.124.149.98]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p65GU987029211 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Tue, 5 Jul 2011 09:30:14 -0700
Message-ID: <4E133C0F.4030604@dcrocker.net>
Date: Tue, 05 Jul 2011 09:30:07 -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: Comments surrounding draft-iab-dns-applications-01
References: <20110429023630.46187.qmail@joyce.lan> <4E116ED8.10506@250bpm.com>	<alpine.BSF.2.00.1107040940090.60353@joyce.lan>	<20110704231442.023081171247@drugs.dv.isc.org>	<alpine.BSF.2.00.1107041959400.29602@joyce.lan>	<20110705005640.D3F52117252B@drugs.dv.isc.org>	<alpine.BSF.2.00.1107042151340.62218@joyce.lan>	<20110705030537.9EE7711730B5@drugs.dv.isc.org> <alpine.LSU.2.00.1107051152550.5578@hermes-2.csi.cam.ac.uk>
In-Reply-To: <alpine.LSU.2.00.1107051152550.5578@hermes-2.csi.cam.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 05 Jul 2011 09:30:15 -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, 05 Jul 2011 16:30:16 -0000

On 7/5/2011 3:56 AM, Tony Finch wrote:
> Mark Andrews<marka@isc.org>  wrote:
>> DNS[WB]L's have never been a good fit to the DNS, rather they have
>> not been a bad enough fit to require something better to be done.
>
> Oh come off it, they are just as good a fit to the DNS as reverse DNS is.
>
>> The naive approach of reversing the address, converting to nibbles
>> and appending a suffix won't scale.
>
> I don't understand why the setup is OK for reverse DNS but not blacklists.


+1

This has been an on-going issue, with a kind of 'purity' argument from some 
folk. While concern for the stability of end-to-end DNS operations certainly is 
essential, the degree of resistance to these added uses of the service often is, 
indeed, inconsistent.

In general, the problematic logic requires a devotion to the narrow usage that 
has dominated the DNS, rather than what the design of DNS was intended to 
support.  (Reading the original RFCs is instructive for this broader view.)

However for the current thread, there really does appear to be an impending 
problem.  It seems pretty clear that DNS caching needs to be tailored to the 
types of applications making the queries and that mixed traffic could well mess 
with caching behavior.  (I think it uncontroversial to note that that having DNS 
caching functioning well is an important requirement for stable and efficient 
DNS use.)

For an application that is likely to encounter a different IP address for 
essentially every query, across a very large number of queries, the only 
solution I see available is to use a different cache.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From johnl@iecc.com  Tue Jul  5 10:32: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 7347321F87EC for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 10:32:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.508
X-Spam-Level: 
X-Spam-Status: No, score=-110.508 tagged_above=-999 required=5 tests=[AWL=0.691, 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 dYQIVoWrEDu1 for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 10:32:12 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id B279F21F87EB for <ietf@ietf.org>; Tue,  5 Jul 2011 10:32:10 -0700 (PDT)
Received: (qmail 35608 invoked from network); 5 Jul 2011 17:32:06 -0000
Received: from gal.iecc.com (64.57.183.53) by mail2.iecc.com with SMTP; 5 Jul 2011 17:32:06 -0000
Received: (qmail 67983 invoked from network); 5 Jul 2011 17:32:06 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 5 Jul 2011 17:32:06 -0000
Date: 5 Jul 2011 17:31:44 -0000
Message-ID: <20110705173144.21698.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Comments surrounding draft-iab-dns-applications-01
In-Reply-To: <4E133C0F.4030604@dcrocker.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: dcrocker@bbiw.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2011 17:32:12 -0000

>For an application that is likely to encounter a different IP address for 
>essentially every query, across a very large number of queries, the only 
>solution I see available is to use a different cache.

Seems reasonable.  I gather that there are already caches with the
ability to partition themselves so that records from different
subtrees compete for different pools of cache entries.

I'm also sort of surprised that we don't seem to have all that much
experimental data about cache behavior.  The MIT papers that Tony
cited are interesting, but they're also ten years old.

R's,
John


From dhc2@dcrocker.net  Tue Jul  5 10:41:12 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 9313921F8711 for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 10:41:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KF9UE+cakk+s for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 10:41:12 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id EF51621F8707 for <ietf@ietf.org>; Tue,  5 Jul 2011 10:41:11 -0700 (PDT)
Received: from [192.168.1.156] (adsl-67-124-149-98.dsl.pltn13.pacbell.net [67.124.149.98]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p65Hf5RM030949 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Tue, 5 Jul 2011 10:41:11 -0700
Message-ID: <4E134CAF.7060706@dcrocker.net>
Date: Tue, 05 Jul 2011 10:41:03 -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: Comments surrounding draft-iab-dns-applications-01
References: <20110705173144.21698.qmail@joyce.lan>
In-Reply-To: <20110705173144.21698.qmail@joyce.lan>
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, 05 Jul 2011 10:41:11 -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, 05 Jul 2011 17:41:12 -0000

On 7/5/2011 10:31 AM, John Levine wrote:
>> For an application that is likely to encounter a different IP address for
>> essentially every query, across a very large number of queries, the only
>> solution I see available is to use a different cache.
>
> Seems reasonable.  I gather that there are already caches with the
> ability to partition themselves so that records from different
> subtrees compete for different pools of cache entries.
>
> I'm also sort of surprised that we don't seem to have all that much
> experimental data about cache behavior.  The MIT papers that Tony
> cited are interesting, but they're also ten years old.


I doubt that partitioning according to DNS structure will work for this, since 
the DNS has no formal semantics to different parts.  Hard-coding knowledge of 
particular tree segments can work for specific examples, in small scale, but 
won't work for the constantly-changing IP Address behavior cited in this thread.

I believe that the solution is to have the applications, themselves, distinguish 
the cache they are using (or the containing library).  A blocklist app needs to 
use a different library/cache than a web browser.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From fanf2@hermes.cam.ac.uk  Tue Jul  5 10:59:31 2011
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC28621F891F for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 10:59:31 -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 mOn-gUmHh5+k for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 10:59:30 -0700 (PDT)
Received: from ppsw-41.csi.cam.ac.uk (ppsw-41.csi.cam.ac.uk [131.111.8.141]) by ietfa.amsl.com (Postfix) with ESMTP id 0A67921F891B for <ietf@ietf.org>; Tue,  5 Jul 2011 10:59:29 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:46187) by ppsw-41.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpa (EXTERNAL:fanf2) id 1Qe9uB-000170-Si (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Tue, 05 Jul 2011 18:59:27 +0100
Received: from fanf2 (helo=localhost) by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1Qe9uB-00018p-Sm (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Tue, 05 Jul 2011 18:59:27 +0100
Date: Tue, 5 Jul 2011 18:59:27 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: dcrocker@bbiw.net
Subject: Re: Comments surrounding draft-iab-dns-applications-01
In-Reply-To: <4E133C0F.4030604@dcrocker.net>
Message-ID: <alpine.LSU.2.00.1107051858160.5578@hermes-2.csi.cam.ac.uk>
References: <20110429023630.46187.qmail@joyce.lan> <4E116ED8.10506@250bpm.com> <alpine.BSF.2.00.1107040940090.60353@joyce.lan> <20110704231442.023081171247@drugs.dv.isc.org> <alpine.BSF.2.00.1107041959400.29602@joyce.lan> <20110705005640.D3F52117252B@drugs.dv.isc.org> <alpine.BSF.2.00.1107042151340.62218@joyce.lan> <20110705030537.9EE7711730B5@drugs.dv.isc.org> <alpine.LSU.2.00.1107051152550.5578@hermes-2.csi.cam.ac.uk> <4E133C0F.4030604@dcrocker.net>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2011 17:59:31 -0000

Dave CROCKER <dhc2@dcrocker.net> wrote:
>
> For an application that is likely to encounter a different IP address for
> essentially every query, across a very large number of queries, the only
> solution I see available is to use a different cache.

This has been operational common sense for many years.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Trafalgar: Northerly 5 or 6 in southeast, otherwise variable mainly westerly
veering northerly, 3 or 4. Moderate or rough. Fair. Moderate or good.

From dhc2@dcrocker.net  Tue Jul  5 11:11:00 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 E5A8B21F893D for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 11:11:00 -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 ApstU8BYFnJB for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 11:10:59 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6A69621F894D for <ietf@ietf.org>; Tue,  5 Jul 2011 11:10:44 -0700 (PDT)
Received: from [192.168.1.156] (adsl-67-124-149-98.dsl.pltn13.pacbell.net [67.124.149.98]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p65IAY0O031483 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Tue, 5 Jul 2011 11:10:39 -0700
Message-ID: <4E135398.3070605@dcrocker.net>
Date: Tue, 05 Jul 2011 11:10: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.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Tony Finch <dot@dotat.at>
Subject: Re: Comments surrounding draft-iab-dns-applications-01
References: <20110429023630.46187.qmail@joyce.lan> <4E116ED8.10506@250bpm.com> <alpine.BSF.2.00.1107040940090.60353@joyce.lan> <20110704231442.023081171247@drugs.dv.isc.org> <alpine.BSF.2.00.1107041959400.29602@joyce.lan> <20110705005640.D3F52117252B@drugs.dv.isc.org> <alpine.BSF.2.00.1107042151340.62218@joyce.lan> <20110705030537.9EE7711730B5@drugs.dv.isc.org> <alpine.LSU.2.00.1107051152550.5578@hermes-2.csi.cam.ac.uk> <4E133C0F.4030604@dcrocker.net> <alpine.LSU.2.00.1107051858160.5578@hermes-2.csi.cam.ac.uk>
In-Reply-To: <alpine.LSU.2.00.1107051858160.5578@hermes-2.csi.cam.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 05 Jul 2011 11:10: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: Tue, 05 Jul 2011 18:11:01 -0000

On 7/5/2011 10:59 AM, Tony Finch wrote:
> Dave CROCKER<dhc2@dcrocker.net>  wrote:
>>
>> For an application that is likely to encounter a different IP address for
>> essentially every query, across a very large number of queries, the only
>> solution I see available is to use a different cache.
>
> This has been operational common sense for many years.


In theory, practice is not much different from theory.  In practice...

    <http://thinkexist.com/quotation/common_sense_is_very/193303.html>

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From johnl@iecc.com  Tue Jul  5 11:12:00 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 C752821F893D for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 11:12:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.585
X-Spam-Level: 
X-Spam-Status: No, score=-110.585 tagged_above=-999 required=5 tests=[AWL=0.614, 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 dUFIW7mXf7rX for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 11:12:00 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 5122321F8936 for <ietf@ietf.org>; Tue,  5 Jul 2011 11:11:58 -0700 (PDT)
Received: (qmail 35876 invoked from network); 5 Jul 2011 18:11:55 -0000
Received: from gal.iecc.com (64.57.183.53) by mail2.iecc.com with SMTP; 5 Jul 2011 18:11:55 -0000
Received: (qmail 74135 invoked from network); 5 Jul 2011 18:11:55 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 5 Jul 2011 18:11:55 -0000
Date: 5 Jul 2011 18:11:33 -0000
Message-ID: <20110705181133.32700.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: DNSBLSs and caches, was Comments surrounding draft-iab-dns-applications-01
In-Reply-To: <4E134CAF.7060706@dcrocker.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: dcrocker@bbiw.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2011 18:12:00 -0000

>I believe that the solution is to have the applications, themselves,
>distinguish the cache they are using (or the containing library).  A
>blocklist app needs to use a different library/cache than a web
>browser.

You could do it either way.  Either you could adjust the MTAs to have
a new parameter for the address of the cache to use for DNSBLs vs. the
cache to use for MX, A, and AAAA, or you could tell the cache about
the list of DNSBLs that the local MTAs use (a list which in my
experience is rarely very long.)

Pick your poison, depends which software is older and cruddier.

Or there's the pessimal approach, add a new EDNS parameter so the MTA
can tell the cache what kind of lookup it's making, so you have to
upgrade and debug both of them!

R's,
John

From msk@cloudmark.com  Tue Jul  5 13:39:29 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 4CBA321F88F3; Tue,  5 Jul 2011 13:39:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.182
X-Spam-Level: 
X-Spam-Status: No, score=-103.182 tagged_above=-999 required=5 tests=[AWL=-0.584, 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 CYfhJ2Rc1UiZ; Tue,  5 Jul 2011 13:39:28 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by ietfa.amsl.com (Postfix) with ESMTP id 77EAB21F88EF; Tue,  5 Jul 2011 13:39:28 -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, 5 Jul 2011 13:39:28 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: IPv6 Operations <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
Date: Tue, 5 Jul 2011 13:39:26 -0700
Subject: RE: [v6ops] draft-ietf-v6ops-6to4-to-historic
Thread-Topic: [v6ops] draft-ietf-v6ops-6to4-to-historic
Thread-Index: Acw5t9BcScQ/ldurRnmLU7pMDnEQ1QBmzmaA
Message-ID: <F5833273385BB34F99288B3648C4F06F134EBC4B84@EXCH-C2.corp.cloudmark.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKD1Yr2Smvm0RY5iV2y06wD=RRz-uW4VbaaairnoAkSR7zLdtg@mail.gmail.com> <BANLkTimpRDNQKc1XTafSkKOo5dCX3Gc8Yw@mail.gmail.com> <20110703112048.4a3c7111@opy.nosense.org>	<4E0FD788.3000305@dougbarton.us> <20110703131913.28142ec0@opy.nosense.org> <CAKD1Yr0dU8xGPc5tY8qK7w7Vc57zzj2BBipCb3b3VsXLov-JUw@mail.gmail.com> <m1QdKfr-0001jNC@stereo.hq.phicoh.net> <E3CF6B2C-B177-4A6A-898C-4EA8C8CA65D5@network-heretics.com> <CAD6AjGSUEmdKk3trTdRXMyrnp8FFyvHUWBSgeBrHT_2jPjXUBA@mail.gmail.com> <100DA5A2-0276-45B8-A8CD-AB7B0D947AC4@network-heretics.com> <CB106539-9C0F-489C-BBC0-E4ADAF3B8F45@gmail.com> <746A967B-16AF-4428-8424-298AF8001F87@network-heretics.com> <DFD19CC6-219F-4449-B0F4-8125193B6FF6@gmail.com> <D30FDDB9-A19A-46C3-9E06-68070300F32A@network-heretics.com>
In-Reply-To: <D30FDDB9-A19A-46C3-9E06-68070300F32A@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_F5833273385BB34F99288B3648C4F06F134EBC4B84EXCHC2corpclo_"
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, 05 Jul 2011 20:39:29 -0000

--_000_F5833273385BB34F99288B3648C4F06F134EBC4B84EXCHC2corpclo_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I shudder to think that this is a prerequisite for declaring something Hist=
oric.

If some RFC meant to solve some problem turns out not only to be a bad idea=
 but also shows that the problem itself is essentially intractable, I don't=
 think it's practical at all to require a replacement before declaring the =
RFC Historic.

From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of K=
eith Moore
Sent: Sunday, July 03, 2011 12:31 PM
To: Arturo Servin
Cc: IPv6 Operations; IETF Discussion
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic

Honestly I'd be happy to declare 6to4 Historic if we had a suitable replace=
ment - one that could be automatically configured by hosts, used by applica=
tions, and worked better than 6to4 in most cases.  I don't think it exists =
yet.

[...]

Keith


--_000_F5833273385BB34F99288B3648C4F06F134EBC4B84EXCHC2corpclo_
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=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft 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-tab-span
	{mso-style-name:apple-tab-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=3DEN-US link=3Dblue vli=
nk=3Dpurple style=3D'word-wrap: break-word;-webkit-nbsp-mode: space;-webkit=
-line-break: after-white-space'><div class=3DWordSection1><p class=3DMsoNor=
mal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";colo=
r:#1F497D'>I shudder to think that this is a prerequisite for declaring som=
ething Historic.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbs=
p;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;fon=
t-family:"Calibri","sans-serif";color:#1F497D'>If some RFC meant to solve s=
ome problem turns out not only to be a bad idea but also shows that the pro=
blem itself is essentially intractable, I don&#8217;t think it&#8217;s prac=
tical at all to require a replacement before declaring the RFC Historic.<o:=
p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;fon=
t-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p>=
<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;paddin=
g:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'font-size:10.0p=
t;font-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font-si=
ze:10.0pt;font-family:"Tahoma","sans-serif"'> v6ops-bounces@ietf.org [mailt=
o:v6ops-bounces@ietf.org] <b>On Behalf Of </b>Keith Moore<br><b>Sent:</b> S=
unday, July 03, 2011 12:31 PM<br><b>To:</b> Arturo Servin<br><b>Cc:</b> IPv=
6 Operations; IETF Discussion<br><b>Subject:</b> Re: [v6ops] draft-ietf-v6o=
ps-6to4-to-historic<o:p></o:p></span></p></div></div><p class=3DMsoNormal><=
o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>Honestly I'd be happy to decl=
are 6to4 Historic if we had a suitable replacement - one that could be auto=
matically configured by hosts, used by applications, and worked better than=
 6to4 in most cases. &nbsp;I don't think it exists yet. &nbsp;<o:p></o:p></=
p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=
=3DMsoNormal><span style=3D'color:#1F497D'>[&#8230;]</span><o:p></o:p></p><=
/div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DM=
soNormal>Keith<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o=
:p></p></div></div></div></body></html>=

--_000_F5833273385BB34F99288B3648C4F06F134EBC4B84EXCHC2corpclo_--

From tjc@ecs.soton.ac.uk  Tue Jul  5 14:11:56 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 76A3421F899C; Tue,  5 Jul 2011 14:11:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level: 
X-Spam-Status: No, score=-2.561 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 JUBZK9QXDXid; Tue,  5 Jul 2011 14:11:54 -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 70C6D21F885C; Tue,  5 Jul 2011 14:11:50 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p65LBfNw012603;  Tue, 5 Jul 2011 22:11:41 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p65LBfNw012603
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1309900301; bh=KIr0cIoyaKRtt8L3cLYauLr/I5E=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=da6EPGupO6JmjYN6Vcx/lsLxNWkOmU2lo0GHdJMj+qtyc7sZRwQnHKV01i4e/HxgD 9DKxnprPrjA9PHYqJBgU7Gh3d6vpAoQH8nHayO9IgeI3LxFz0U0cK2qwYV2CKfZIOe 6N88b0rfkY70OTYsGcp3n4FcFopu6vEDJfhoamc0=
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 n64MBf0366144435Y0 ret-id none; Tue, 05 Jul 2011 22:11:41 +0100
Received: from [192.168.1.100] (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 p65LAIhf007346 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 5 Jul 2011 22:10:19 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Last Call: <draft-ietf-mboned-ssmping-08.txt> (Multicast Ping Protocol) to Proposed Standard
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <20110620175110.14625.38398.idtracker@ietfa.amsl.com>
Date: Tue, 5 Jul 2011 22:10:18 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|772969f9f078348e983706777abf5dbbn64MBf03tjc|ecs.soton.ac.uk|D17DB58C-6822-4192-B9F0-F9617CDBB4D1@ecs.soton.ac.uk>
References: <20110620175110.14625.38398.idtracker@ietfa.amsl.com> <D17DB58C-6822-4192-B9F0-F9617CDBB4D1@ecs.soton.ac.uk>
To: IETF Discussion <ietf@ietf.org>, MBONED WG <mboned@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n64MBf036614443500; tid=n64MBf0366144435Y0; 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: p65LBfNw012603
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, 05 Jul 2011 21:11:56 -0000

I think this draft specifies a very useful protocol, which we have used =
at our site and which has been a valuable multicast debugging tool.

The specification and implementations have evolved over maybe 5-6 years =
or so.  The implementations we've used have been of various stages of =
the protocol's development.  A student at our site implemented an =
earlier version of the protocol successfully.  I don't believe we've =
used a version at our site based on the spec in the final version of the =
text, so I can't comment on that specifically.

There are some parts of the text that I think indicate the protocol has =
evolved over a length of time; if it were rewritten from scratch it =
would probably be somewhat more compact, due to some level of repetition =
of aspects of the protocol.  However, I think it's more important to get =
the protocol published now, so I would support publishing it as is. =20

The protocol is defined in a fairly loose way, but the core elements are =
tight enough for implementation.  This is reflected in the text at the =
start of Section 6.

I noticed one nit in terms of the client ID. In Section 2 the text says:
"At runtime, a client generates a client ID that is unique for the ping =
test.  This ID is included in all messages sent by the client."
Then later in the more detailed spec, the text says:
"A client SHOULD always include this option in all messages (both Init =
and Echo Request)."
I would have expected the inclusion of the Client ID to be a MUST, based =
on the earlier explanation.  If it is a SHOULD, the introduction text =
should say "this ID is usually included in all messages sent by the =
client".

It would be nice to consider mechanisms to discover 'public' ssmping =
test servers, but that's a separate text :)

Tim

On 20 Jun 2011, at 18:51, The IESG wrote:

>=20
> The IESG has received a request from the MBONE Deployment WG (mboned) =
to
> consider the following document:
> - 'Multicast Ping Protocol'
>  <draft-ietf-mboned-ssmping-08.txt> as a Proposed Standard
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2011-07-04. Exceptionally, comments may =
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
> The Multicast Ping Protocol specified in this document allows for
> checking whether an endpoint can receive multicast, both Source-
> Specific Multicast (SSM) and Any-Source Multicast (ASM).  It can also
> be used to obtain additional multicast-related information such as
> multicast tree setup time.  This protocol is based on an
> implementation of tools called ssmping and asmping.
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-mboned-ssmping/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-mboned-ssmping/
>=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


From geoff.ietf@mulligan.com  Tue Jul  5 14:32:13 2011
Return-Path: <geoff.ietf@mulligan.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD25B21F87B1 for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 14:32:13 -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 aiNwQ7D0MC7q for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 14:32:13 -0700 (PDT)
Received: from server2.coslabs.com (server2.coslabs.com [64.111.18.234]) by ietfa.amsl.com (Postfix) with ESMTP id 3B84221F87AC for <ietf@ietf.org>; Tue,  5 Jul 2011 14:32:13 -0700 (PDT)
Received: from grab.coslabs.com (mail.coslabs.com [199.233.92.34]) by server2.coslabs.com (Postfix) with ESMTP id 85A1A184B4 for <ietf@ietf.org>; Tue,  5 Jul 2011 15:32:17 -0600 (MDT)
Received: from [199.233.92.6] (unknown [199.233.92.6]) by grab.coslabs.com (Postfix) with ESMTP id 1898B16030C for <ietf@ietf.org>; Tue,  5 Jul 2011 15:32:09 -0600 (MDT)
Subject: extra room avail IETF hotel at IETF rate
From: Geoff Mulligan <geoff.ietf@mulligan.com>
To: ietf@ietf.org
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 05 Jul 2011 15:32:11 -0600
Message-ID: <1309901531.1861.26.camel@d430>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.2 
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, 05 Jul 2011 21:32:14 -0000

I found that I have an extra reservation at the IETF rate
($229/night)for Sunday to Friday at the Hilton.

If anyone is interested I can transfer the reservation.

	geoff



From stig@venaas.com  Tue Jul  5 14:40:30 2011
Return-Path: <stig@venaas.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 554AE21F880B; Tue,  5 Jul 2011 14:40:30 -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 gfTyeRnP3QBq; Tue,  5 Jul 2011 14:40:29 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id A1C7121F87AC; Tue,  5 Jul 2011 14:40:28 -0700 (PDT)
Received: from [IPv6:2001:420:4:ea0c:5dbe:7b0b:efac:4f7e] (unknown [IPv6:2001:420:4:ea0c:5dbe:7b0b:efac:4f7e]) by ufisa.uninett.no (Postfix) with ESMTPSA id 100A78022; Tue,  5 Jul 2011 23:40:25 +0200 (CEST)
Message-ID: <4E1384C8.6070301@venaas.com>
Date: Tue, 05 Jul 2011 14:40:24 -0700
From: Stig Venaas <stig@venaas.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: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: [MBONED] Last Call: <draft-ietf-mboned-ssmping-08.txt>	(Multicast Ping Protocol) to Proposed Standard
References: <20110620175110.14625.38398.idtracker@ietfa.amsl.com>	<D17DB58C-6822-4192-B9F0-F9617CDBB4D1@ecs.soton.ac.uk> <EMEW3|772969f9f078348e983706777abf5dbbn64MBf03tjc|ecs.soton.ac.uk|D17DB58C-6822-4192-B9F0-F9617CDBB4D1@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|772969f9f078348e983706777abf5dbbn64MBf03tjc|ecs.soton.ac.uk|D17DB58C-6822-4192-B9F0-F9617CDBB4D1@ecs.soton.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: MBONED WG <mboned@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, 05 Jul 2011 21:40:30 -0000

On 7/5/2011 2:10 PM, Tim Chown wrote:
> I think this draft specifies a very useful protocol, which we have used at our site and which has been a valuable multicast debugging tool.
>
> The specification and implementations have evolved over maybe 5-6 years or so.  The implementations we've used have been of various stages of the protocol's development.  A student at our site implemented an earlier version of the protocol successfully.  I don't believe we've used a version at our site based on the spec in the final version of the text, so I can't comment on that specifically.
>
> There are some parts of the text that I think indicate the protocol has evolved over a length of time; if it were rewritten from scratch it would probably be somewhat more compact, due to some level of repetition of aspects of the protocol.  However, I think it's more important to get the protocol published now, so I would support publishing it as is.
>
> The protocol is defined in a fairly loose way, but the core elements are tight enough for implementation.  This is reflected in the text at the start of Section 6.
>
> I noticed one nit in terms of the client ID. In Section 2 the text says:
> "At runtime, a client generates a client ID that is unique for the ping test.  This ID is included in all messages sent by the client."
> Then later in the more detailed spec, the text says:
> "A client SHOULD always include this option in all messages (both Init and Echo Request)."
> I would have expected the inclusion of the Client ID to be a MUST, based on the earlier explanation.  If it is a SHOULD, the introduction text should say "this ID is usually included in all messages sent by the client".

Yes, I think it should be changed to say "usually". A basic client could
work without including the ID. But there are good reasons to include it
as listed in the draft.

Stig

> It would be nice to consider mechanisms to discover 'public' ssmping test servers, but that's a separate text :)
>
> Tim
>
> On 20 Jun 2011, at 18:51, The IESG wrote:
>
>>
>> The IESG has received a request from the MBONE Deployment WG (mboned) to
>> consider the following document:
>> - 'Multicast Ping Protocol'
>>   <draft-ietf-mboned-ssmping-08.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-07-04. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>
>> The Multicast Ping Protocol specified in this document allows for
>> checking whether an endpoint can receive multicast, both Source-
>> Specific Multicast (SSM) and Any-Source Multicast (ASM).  It can also
>> be used to obtain additional multicast-related information such as
>> multicast tree setup time.  This protocol is based on an
>> implementation of tools called ssmping and asmping.
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-mboned-ssmping/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-mboned-ssmping/
>>
>>
>> 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
>
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned


From touch@isi.edu  Tue Jul  5 15:13:15 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 C3D0F21F890D for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 15:13:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.732
X-Spam-Level: 
X-Spam-Status: No, score=-103.732 tagged_above=-999 required=5 tests=[AWL=-1.133, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DQuNi1g-XsgP for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 15:13:14 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 6A7C721F87DB for <ietf@ietf.org>; Tue,  5 Jul 2011 15:13:13 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id p65MCtuN028891 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 5 Jul 2011 15:12:55 -0700 (PDT)
Message-ID: <4E138C67.9020407@isi.edu>
Date: Tue, 05 Jul 2011 15:12:55 -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: Danny McPherson <danny@tcb.net>
Subject: Re: Comments surrounding draft-iab-dns-applications-01
References: <a06240800c9df29c0bf75@[10.31.203.186]> <B8FD63DA-3047-4CE5-8CA0-BA12B54617A1@tcb.net>
In-Reply-To: <B8FD63DA-3047-4CE5-8CA0-BA12B54617A1@tcb.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Edward Lewis <Ed.Lewis@neustar.biz>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2011 22:13:15 -0000

Hi, all,

This doc also claims that:

" The SRV record allows
    DNS resolvers to search for particular applications and underlying
    transports (for example, HTTP running over TLS, see [RFC2818]) and to
    learn the domain name and port where that service resides in a given
    administrative domain. "

The transports should be TCP, UDP, or (arguably or not) other transport 
protocols. TLS is not a transport.

Currently http is distinguished from https using the service names 
string, not the transport. I.e., IMO, in SRV records:

	service name = layers 5-7
	transport = layer 4

TLS is above layer 4.

---

Additionally, it's useful to distinguish The DNS (i.e., with the 
existing well-know roots) from A DNS -- the latter using the same 
protocols and records, but not sharing the same initial roots.

Joe

From mrex@sap.com  Tue Jul  5 17:54:38 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 6613521F87F9; Tue,  5 Jul 2011 17:54:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.179
X-Spam-Level: 
X-Spam-Status: No, score=-10.179 tagged_above=-999 required=5 tests=[AWL=0.070, 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 r2x6Y165dF1V; Tue,  5 Jul 2011 17:54:38 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id A04D821F87CC; Tue,  5 Jul 2011 17:54:37 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p660sT3V020939 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 6 Jul 2011 02:54:34 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201107060054.p660sTMl017973@fs4113.wdf.sap.corp>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
To: gert@space.net (Gert Doering)
Date: Wed, 6 Jul 2011 02:54:29 +0200 (MEST)
In-Reply-To: <20110703111047.GB2304@Space.Net> from "Gert Doering" at Jul 3, 11 01:10:47 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: v6ops@ietf.org, lorenzo@google.com, moore@network-heretics.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: Wed, 06 Jul 2011 00:54:38 -0000

Gert Doering wrote:
> 
> On Sat, Jul 02, 2011 at 11:11:43PM -0400, Keith Moore wrote:
> > There's clearly a lack of consensus to support it.
> 
> There's two very vocal persons opposing it

There were more than two clearly opposing, and there is no need to
further fuel the heated discussion by everyone becoming as vocal
as Keith.   The pain point is really the unnecessarily aggressive
"kill what we don't like" move-to-historic action.

This is a procedural issue, not a matter of personal taste.
There was an alternative reclassification suggested, that
could gather rough consensus.

I'm still waiting for a *clean* resolution of the procedural issue
(that means serious consideration of suggested alternatives).

-Martin

From dhc2@dcrocker.net  Tue Jul  5 18:07:58 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 36F7F21F8873 for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 18:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PLgE-levHpkH for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 18:07:57 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6210F21F883D for <ietf@ietf.org>; Tue,  5 Jul 2011 18:07:57 -0700 (PDT)
Received: from [192.168.1.156] (adsl-67-124-149-98.dsl.pltn13.pacbell.net [67.124.149.98]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p6617phX008244 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Tue, 5 Jul 2011 18:07:56 -0700
Message-ID: <4E13B564.3010404@dcrocker.net>
Date: Tue, 05 Jul 2011 18:07:48 -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: Comments surrounding draft-iab-dns-applications-01
References: <a06240800c9df29c0bf75@[10.31.203.186]>	<B8FD63DA-3047-4CE5-8CA0-BA12B54617A1@tcb.net> <4E138C67.9020407@isi.edu>
In-Reply-To: <4E138C67.9020407@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 05 Jul 2011 18:07:57 -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, 06 Jul 2011 01:07:58 -0000

On 7/5/2011 3:12 PM, Joe Touch wrote:
> " The SRV record allows
> DNS resolvers to search for particular applications and underlying
> transports (for example, HTTP running over TLS, see [RFC2818]) and to
> learn the domain name and port where that service resides in a given
> administrative domain. "
>
> The transports should be TCP, UDP, or (arguably or not) other transport
> protocols. TLS is not a transport.

Also, strictly speaking, the function that is performed is lookup or mapping, 
not "search".  The difference is large.


> Additionally, it's useful to distinguish The DNS (i.e., with the existing
> well-know roots) from A DNS -- the latter using the same protocols and records,
> but not sharing the same initial roots.

+1

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From heard@pobox.com  Tue Jul  5 19:22:57 2011
Return-Path: <heard@pobox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79BF421F8812 for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 19:22:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.442
X-Spam-Level: 
X-Spam-Status: No, score=-2.442 tagged_above=-999 required=5 tests=[AWL=-0.158, 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 wda-Gunu8wxA for <ietf@ietfa.amsl.com>; Tue,  5 Jul 2011 19:22:56 -0700 (PDT)
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80BCA21F881A for <ietf@ietf.org>; Tue,  5 Jul 2011 19:22:47 -0700 (PDT)
Received: (qmail 11496 invoked from network); 5 Jul 2011 19:22:46 -0700
Received: from shell4.bayarea.net (209.128.82.1) by shell4.bayarea.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 5 Jul 2011 19:22:46 -0700
Date: Tue, 5 Jul 2011 19:22:46 -0700 (PDT)
From: "C. M. Heard" <heard@pobox.com>
X-X-Sender: heard@shell4.bayarea.net
To: IETF <ietf@ietf.org>
Subject: draft-ietf-v6ops-6to4-advisory dependency on draft-ietf-v6ops-6to4-to-historic
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F3508430@EMBX01-WF.jnpr.net>
Message-ID: <Pine.LNX.4.64.1107051859520.2828@shell4.bayarea.net>
References: <20110705144429.DDFE218C10A@mercury.lcs.mit.edu> <13205C286662DE4387D9AF3AC30EF456D3F3508430@EMBX01-WF.jnpr.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2011 02:22:57 -0000

Greetings,

I note that draft-ietf-v6ops-6to4-advisory-02, now approved for 
publication and in the RFC Editor's queue, has a minor dependency on 
draft-ietf-v6ops-6to4-to-historic, specifically at the end of 
Section 1 (bottom of p. 3):


  "A companion document [I-D.ietf-v6ops-6to4-to-historic] proposes 
   to reclassify 6to4 as Historic.  However, this will not remove 
   the millions of existing hosts and customer premises equipments 
   that implement 6to4.  Hence, the advice in this document remains 
   necessary."

That may need to be changed (e.g., in AUTH48), depending on the 
outcome of the pending appeal against draft-ietf-v6ops-6to4-to-historic.  

//cmh

On Tue, 5 Jul 2011, Ronald Bonica wrote:
> Noel,
> 
> I didn't say that I was going to push 
> draft-ietf-v6ops-6to4-to-historic through without running the 
> process. I said that draft-ietf-v6ops-6to4-to-historic has made it 
> all the way past IESG approval. There is an appeal on the table 
> (at the WG level) questioning whether 
> draft-ietf-v6ops-6to4-to-historic ever had WG consensus. We will 
> run the appeal process. If the WG chairs cannot justify WG 
> consensus, draft-ietf-v6ops-6to4-to-historic stops dead in its 
> tracks. If they can justify WG consensus, the appellant can 
> escalate the appeal to the IESG (and to the IAB after that). If 
> the appeal succeeds at any level, 
> draft-ietf-v6ops-6to4-to-historic is not published.
> 
>                                                                Ron
> 
> 
> -----Original Message-----
> From: Noel Chiappa [mailto:jnc@mercury.lcs.mit.edu] 
> Sent: Tuesday, July 05, 2011 10:44 AM
> To: ietf@ietf.org; v6ops@ietf.org
> Cc: jnc@mercury.lcs.mit.edu
> Subject: RE: draft-ietf-v6ops-6to4-to-historic
> 
>     > From: Ronald Bonica <rbonica@juniper.net>
> 
>     >>> I think that I get it. There is no IETF consensus regarding the
>     >>> compromise proposed below. ...
> 
>     >> But there is no rough consensus to do that either.
> 
>     > That is the claim of an appeal on the table. Let's run the appeal
>     > process and figure out whether that claim is valid.
> 
> Sorry, this makes no sense.
> 
> You can't go ahead with draft-ietf-v6ops-6to4-to-historic if there is no
> basic consensus in the IETF as a whole to do so - and your previous
> declaration (on Saturday) basically accepted that there was no such basic
> consensus (otherwise why withdraw the ID).
> 
> So now there is going to be a reversal, and the document is going to go ahead
> - i.e. you must now be taking the position that there _is_ basic consensus in
> the IETF (without which you could not proceed the ID).
> 
> The effect of this sort of thing on the reputation of I* should be obvious
> to all.
> 
> 	Noel
> 

From brian.e.carpenter@gmail.com  Wed Jul  6 05:01: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 0068A21F84FE for <ietf@ietfa.amsl.com>; Wed,  6 Jul 2011 05:01:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.42
X-Spam-Level: 
X-Spam-Status: No, score=-103.42 tagged_above=-999 required=5 tests=[AWL=-0.136, 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 NnRYmNjpl2Ir for <ietf@ietfa.amsl.com>; Wed,  6 Jul 2011 05:01:10 -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 372F321F84F8 for <ietf@ietf.org>; Wed,  6 Jul 2011 05:01:10 -0700 (PDT)
Received: by iwn39 with SMTP id 39so7420575iwn.31 for <ietf@ietf.org>; Wed, 06 Jul 2011 05:01:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=D1FO/IQuoF4hhfgjsvUZ/rDeepyJ7wQBhEwMSG5JW1M=; b=rjYOFNUCZoo3X106fzZYxhocQOZwje3tlbEexsi68xtR/nSvnGjiAqN/fmp7NUjaZJ nH9sSraIQGcu1NyIOkqf6hGAK0WWmKfD2rF2Zty78NgJfuyZ3E0yZ1h5sf8fp7iG2Ajd g7Kg826ubdQI2LNckrzFUhTDhXeKmfAf0IuTw=
Received: by 10.42.244.195 with SMTP id lr3mr4035768icb.90.1309953669687; Wed, 06 Jul 2011 05:01:09 -0700 (PDT)
Received: from [10.255.25.118] (74-95-74-1-Indianapolis.hfc.comcastbusiness.net [74.95.74.1]) by mx.google.com with ESMTPS id e1sm8724224icv.8.2011.07.06.05.01.08 (version=SSLv3 cipher=OTHER); Wed, 06 Jul 2011 05:01:08 -0700 (PDT)
Message-ID: <4E144E77.1040908@gmail.com>
Date: Thu, 07 Jul 2011 00:00:55 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "C. M. Heard" <heard@pobox.com>
Subject: Re: draft-ietf-v6ops-6to4-advisory dependency on draft-ietf-v6ops-6to4-to-historic
References: <20110705144429.DDFE218C10A@mercury.lcs.mit.edu>	<13205C286662DE4387D9AF3AC30EF456D3F3508430@EMBX01-WF.jnpr.net> <Pine.LNX.4.64.1107051859520.2828@shell4.bayarea.net>
In-Reply-To: <Pine.LNX.4.64.1107051859520.2828@shell4.bayarea.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2011 12:01:11 -0000

Yes, I'm planning to check that in AUTH48 and wordsmith it as necessary.

Regards
   Brian Carpenter

On 2011-07-06 14:22, C. M. Heard wrote:
> Greetings,
> 
> I note that draft-ietf-v6ops-6to4-advisory-02, now approved for 
> publication and in the RFC Editor's queue, has a minor dependency on 
> draft-ietf-v6ops-6to4-to-historic, specifically at the end of 
> Section 1 (bottom of p. 3):
> 
> 
>   "A companion document [I-D.ietf-v6ops-6to4-to-historic] proposes 
>    to reclassify 6to4 as Historic.  However, this will not remove 
>    the millions of existing hosts and customer premises equipments 
>    that implement 6to4.  Hence, the advice in this document remains 
>    necessary."
> 
> That may need to be changed (e.g., in AUTH48), depending on the 
> outcome of the pending appeal against draft-ietf-v6ops-6to4-to-historic.  
> 
> //cmh
> 
> On Tue, 5 Jul 2011, Ronald Bonica wrote:
>> Noel,
>>
>> I didn't say that I was going to push 
>> draft-ietf-v6ops-6to4-to-historic through without running the 
>> process. I said that draft-ietf-v6ops-6to4-to-historic has made it 
>> all the way past IESG approval. There is an appeal on the table 
>> (at the WG level) questioning whether 
>> draft-ietf-v6ops-6to4-to-historic ever had WG consensus. We will 
>> run the appeal process. If the WG chairs cannot justify WG 
>> consensus, draft-ietf-v6ops-6to4-to-historic stops dead in its 
>> tracks. If they can justify WG consensus, the appellant can 
>> escalate the appeal to the IESG (and to the IAB after that). If 
>> the appeal succeeds at any level, 
>> draft-ietf-v6ops-6to4-to-historic is not published.
>>
>>                                                                Ron
>>
>>
>> -----Original Message-----
>> From: Noel Chiappa [mailto:jnc@mercury.lcs.mit.edu] 
>> Sent: Tuesday, July 05, 2011 10:44 AM
>> To: ietf@ietf.org; v6ops@ietf.org
>> Cc: jnc@mercury.lcs.mit.edu
>> Subject: RE: draft-ietf-v6ops-6to4-to-historic
>>
>>     > From: Ronald Bonica <rbonica@juniper.net>
>>
>>     >>> I think that I get it. There is no IETF consensus regarding the
>>     >>> compromise proposed below. ...
>>
>>     >> But there is no rough consensus to do that either.
>>
>>     > That is the claim of an appeal on the table. Let's run the appeal
>>     > process and figure out whether that claim is valid.
>>
>> Sorry, this makes no sense.
>>
>> You can't go ahead with draft-ietf-v6ops-6to4-to-historic if there is no
>> basic consensus in the IETF as a whole to do so - and your previous
>> declaration (on Saturday) basically accepted that there was no such basic
>> consensus (otherwise why withdraw the ID).
>>
>> So now there is going to be a reversal, and the document is going to go ahead
>> - i.e. you must now be taking the position that there _is_ basic consensus in
>> the IETF (without which you could not proceed the ID).
>>
>> The effect of this sort of thing on the reputation of I* should be obvious
>> to all.
>>
>> 	Noel
>>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 

From ron.even.tlv@gmail.com  Wed Jul  6 06:42:55 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 7EEDD21F8713; Wed,  6 Jul 2011 06:42:55 -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, 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 oZdfh3B7k+Lr; Wed,  6 Jul 2011 06:42:54 -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 35BA321F8619; Wed,  6 Jul 2011 06:42:54 -0700 (PDT)
Received: by wwe5 with SMTP id 5so4676536wwe.13 for <multiple recipients>; Wed, 06 Jul 2011 06:42:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:content-language:thread-index; bh=Px4adN/TtI2ADeozngwsuopgbTbxhE3JRFxq8p+A3mY=; b=U8vvhFbW5dvqmcYhRHuIOONz0J2GjMU+pBcL5jyrts+NZqG1DnuMzQbjloymhx0P7v gqX5a/cywVkktYQLCXxg3D/EFnFiOPw2b3ZyRScdxls6rcEAmeRHgtJaHfkFS9GGim3h +a02oGhAgE/+VFv4PHpC5Fck8BRafeMkjEQ5Q=
Received: by 10.216.156.70 with SMTP id l48mr5757172wek.5.1309959771454; Wed, 06 Jul 2011 06:42:51 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-176-41-148.red.bezeqint.net [79.176.41.148]) by mx.google.com with ESMTPS id z22sm4223819weq.2.2011.07.06.06.42.40 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 06 Jul 2011 06:42:50 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-6man-flow-3697bis.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-6man-flow-3697bis-05
Date: Wed, 6 Jul 2011 16:40:12 +0300
Message-ID: <4e14665a.16eed80a.092b.ffff8043@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0076_01CC3BFB.6E2E9B40"
X-Mailer: Microsoft Office Outlook 12.0
Content-language: en-us
Thread-index: Acw74iQO26mA5j/GQj2WGY7xsnmCWw==
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: Wed, 06 Jul 2011 13:42:55 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0076_01CC3BFB.6E2E9B40
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-6man-flow-3697bis-05

Reviewer: Roni Even

Review Date:2011-7-6

IETF LC End Date: 2011-7-13

IESG Telechat date: 

 

Summary: This draft is ready for publication as a standard track RFC.  One
nit

 

Major issues:

 

Minor issues:

 

Nits/editorial comments:  

In section 3 fifth paragraph ""An alternative approach is to to use"

 


------=_NextPart_000_0076_01CC3BFB.6E2E9B40
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 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.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>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: =
draft-ietf-6man-flow-3697bis-05<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;7&#8211;6<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;13<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 RFC.&nbsp; One =
nit<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:&nbsp; <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3 fifth paragraph &#8220;&#8221;An alternative approach is to to =
use&#8221;<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0076_01CC3BFB.6E2E9B40--


From stbryant@cisco.com  Wed Jul  6 07:15:32 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 BAF2621F85A7; Wed,  6 Jul 2011 07:15:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.599
X-Spam-Level: 
X-Spam-Status: No, score=-109.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, GB_MUTUALBENEFIT=2, 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 wvjs66umHkkv; Wed,  6 Jul 2011 07:15:31 -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 8861721F84EB; Wed,  6 Jul 2011 07:15:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=4009; q=dns/txt; s=iport; t=1309961730; x=1311171330; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=DUd7o9+p2p3D7Iu9viFzVbltTKBr1R2vcs/movTM2js=; b=DOHN+V71BosdwpA0iiACLAPgT8Gn/8uoWEenXSOA06+ly/G1NSQGv7Vt 0kukqBTq1gDf0uTFaGxu8zmllMASAEKRUCzgOqtjWgSF8LSU9wZClQNCs DTnLsylidTm+Z9fCrYnitpz86RJ3gg1wkoEs6zjLv//NKhtmbpGkiM5zr s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EANlsFE6Q/khL/2dsb2JhbABFDqgDd4h6pQODFQ8Bmw2DIYMVBJJBkD0
X-IronPort-AV: E=Sophos;i="4.65,487,1304294400"; d="scan'208";a="40865394"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 06 Jul 2011 14:15:29 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p66EFT6S009462; Wed, 6 Jul 2011 14:15:29 GMT
Received: from dhcp-gpk02-vlan300-64-103-65-77.cisco.com (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id p66EFS6m016947; Wed, 6 Jul 2011 15:15:28 +0100 (BST)
Message-ID: <4E146E49.9050403@cisco.com>
Date: Wed, 06 Jul 2011 15:16:41 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Rolf Winter <Rolf.Winter@neclab.eu>
Subject: Re: tsv-dir review of draft-ietf-pwe3-fat-pw-06
References: <791AD3077F94194BB2BDD13565B6295D05E6A0F3@PALLENE.office.hd>
In-Reply-To: <791AD3077F94194BB2BDD13565B6295D05E6A0F3@PALLENE.office.hd>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "draft-ietf-pwe3-fat-pw@tools.ietf.org" <draft-ietf-pwe3-fat-pw@tools.ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "tsv-dir@ietf.org" <tsv-dir@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: Wed, 06 Jul 2011 14:15:32 -0000

Rolf

Thank you for the review

On 19/05/2011 14:24, Rolf Winter wrote:
>
>
> CONTENT:
>
> Section 3 says:
> "If a flow LSE is present, it MUST be checked to determine whether it
> carries a reserved label.  If it is a reserved label the packet is
> processed according to the rules associated with that reserved label,
> otherwise the LSE is discarded."
> However section 1.2 states:
> "Note that the flow label MUST NOT be an MPLS reserved label."
> Isn't that a contradiction to a certain extend. I mean, if there is a reserved label in the flow LSE, isn't that an error and should not be processed?

Section 1.2 is saying that the flow label generator MUST NOT generate 
and apply a reserved label.

Section 3 is saying that if there is a label put in that position it 
must have been
put there by some application that wanted a diagnostic so process it.

The intent is careful what you send, liberal with what you receive.

>
> section 8.4:
> The second bullet in the section under: "The issues described above are mitigated by the following two factors:". I wonder whether that isn't a bit farfetched. I mean, in principle you suggest that customers could change e.g. the way their applications behave to let the ingress PE to be able to better apply the flow label. That sounds like asking a customer to change something on their application end to have a better network connectivity.

This is dealing with the single large flow case. There is no way to load 
balance a single large flow at the speeds we need to operate and at the 
price performance point needed. This is noting that the customer needs 
to help out.

Clearly if the user is unable to modify their application they get the 
performance they get, and indeed risk running foul of ingress policing 
by the provider.

  section 8.5. Isn't a bigger problem here that you cannot guarantee 
that the OAM packets follow the same ECMP path and that violates the 
fate sharing requirement?

I added:

"In addition MPLS-TP makes extensive use of the fate sharing between OAM 
and data packets, which is defeated by the flow LSE."
>
> section 12:
> You essentially say that the behaviour of IP packets are well defined regarding congestion and nothing needs to be done. Other payload needs to be dealt with by PW congestion avoidance (whatever that means). So IP packets that are not reacting to congestion (such as UDP) are no concern but other packets with the same behaviour are? Is that a correct reading of the text?
Yes. The PW assumes that all IP packets are as well behaved as the IETF 
requires them to be. It is not the job of PWE3 to specify or influence 
the congestion behavior of IP packets, we just carry them as a "wire" would.



>
> section 2:
> s/identify flows/identifies flows/
I am not sure. Let's leave it to RFCed.
>
>
> section 8.4:
> Option one says: "The operator can choose to do nothing and the system will work as it does without the flow label."
> Isn't this option to not use the flow label. If so a better wording would maybe be: "The operator can choose to do nothing, i.e. to not employ the flow label"
The point is that the operator would prefer for their own reasons to see 
load balancing so they probably want to turn it on and hope that at some 
future stage the user modifies their profile to the mutual benefit of 
user and provider.

The do nothing refers to taking no further action.

> Option 3: 2/flows,/flows./
>
> Why is section 9 not section 8.7? I mean it is concerned with applicability which is what section 8 is about.
PWS are not LSPs and there is work on this WRT LSPs in MPLS WG. This is 
a heads up that this other work is happening, that both parties are 
aware of what the other is doing. It seems reasonable to put it in its 
own section.

>
> section 9:
>
> s/This is can be regarded as/This can be regarded as/
This section was re-written following genart f/b from Mary Barns.

Regards

Stewart

From ipng@69706e6720323030352d30312d31340a.nosense.org  Tue Jul  5 08:08:21 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 0FF4311E8139; Tue,  5 Jul 2011 08:08:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.604
X-Spam-Level: 
X-Spam-Status: No, score=0.604 tagged_above=-999 required=5 tests=[AWL=-1.207,  BAYES_40=-0.185, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RgGm6QQanhng; Tue,  5 Jul 2011 08:08:20 -0700 (PDT)
Received: from smtp3.adam.net.au (smtp3.adam.net.au [202.136.110.249]) by ietfa.amsl.com (Postfix) with ESMTP id 7B1E511E821B; Tue,  5 Jul 2011 08:08:17 -0700 (PDT)
Received: from 182-239-205-173.ip.adam.com.au ([182.239.205.173] helo=opy.nosense.org) by smtp3.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1Qe7EW-0002hp-N3; Wed, 06 Jul 2011 00:38:16 +0930
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 556543B341; Wed,  6 Jul 2011 00:38:16 +0930 (CST)
Date: Wed, 6 Jul 2011 00:38:16 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Message-ID: <20110706003816.76531ca8@opy.nosense.org>
In-Reply-To: <20110705144429.DDFE218C10A@mercury.lcs.mit.edu>
References: <20110705144429.DDFE218C10A@mercury.lcs.mit.edu>
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Wed, 06 Jul 2011 08:09:43 -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: Tue, 05 Jul 2011 15:08:21 -0000

Just remember kids,

disagreeing is not attacking. accusing them of attacking when all
they're doing is disagreeing is an attack on them.

don't assume people have no real world experience or responsibilities if
they choose not to announce to the world their job title or their
affiliations in their emails.

=E2=90=84

From david.i.allan@ericsson.com  Tue Jul  5 08:52:43 2011
Return-Path: <david.i.allan@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 0A79911E80F3; Tue,  5 Jul 2011 08:52:43 -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 09LMb62ss31I; Tue,  5 Jul 2011 08:52:42 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by ietfa.amsl.com (Postfix) with ESMTP id AF08C11E80DC; Tue,  5 Jul 2011 08:52:41 -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 p65FqaAM012524; Tue, 5 Jul 2011 10:52:41 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.253]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Tue, 5 Jul 2011 11:52:39 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: Rui Costa <RCosta@ptinovacao.pt>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
Date: Tue, 5 Jul 2011 11:52:37 -0400
Subject: RE: [mpls] Last Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication for	MPLS	Transport	Profile) to Proposed Standard
Thread-Topic: [mpls] Last Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication for	MPLS	Transport	Profile) to Proposed Standard
Thread-Index: Acw3LJ0GTOqQfPcUQOGUhgK/1kXgjgDPfXWgAC+ZHdA=
Message-ID: <60C093A41B5E45409A19D42CF7786DFD52212CB37A@EUSAACMS0703.eamcs.ericsson.se>
References: <20110630134642.1281.3095.idtracker@ietfa.amsl.com> <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B3D5@INOAVREX11.ptin.corpPT.com>
In-Reply-To: <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B3D5@INOAVREX11.ptin.corpPT.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/mixed; boundary="_002_60C093A41B5E45409A19D42CF7786DFD52212CB37AEUSAACMS0703e_"
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 06 Jul 2011 08:09:43 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2011 15:52:43 -0000

--_002_60C093A41B5E45409A19D42CF7786DFD52212CB37AEUSAACMS0703e_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Rui:

Ignored is a strong word....and does not bear scrutiny if you comapre the c=
urrent document with the comments recevied. Attached is a spreadsheet of co=
mment disposition for comments received during LC which included MPLS WG, B=
FD WG and those comments received from Q10.

Dave


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Rui=
 Costa
Sent: Monday, July 04, 2011 3:03 PM
To: ietf@ietf.org; IETF-Announce
Cc: mpls@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proac=
tive Connectivity Verification, Continuity Check and Remote Defect indicati=
on for MPLS Transport Profile) to Proposed Standard

IMHO and for the record:=09

ITU-T comments regarding this draft haven't been discussed with ITU-T but w=
ere simply ignored. No LS describing these comments' resolution was sent.=09

Several service providers regarded this draft as not meeting their transpor=
t networks' needs.=09

[The v03 draft was published in Feb and went to WG LC.=09
The v04 draft addressing WG LC comments was published on the 28th June (sam=
e date as the proto write-up).=09
When was the WG LC launched, to verify LC comments resolution?]=09

Regards,=09
Rui


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of The=
 IESG
Sent: quinta-feira, 30 de Junho de 2011 14:47
To: IETF-Announce
Cc: mpls@ietf.org
Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive=
 Connectivity Verification, Continuity Check and Remote Defect indication f=
or MPLS Transport Profile) to Proposed Standard


The IESG has received a request from the Multiprotocol Label Switching WG
(mpls) to consider the following document:
- 'Proactive Connectivity Verification, Continuity Check and Remote
   Defect indication for MPLS Transport Profile'
  <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally, comments may be sent to ie=
sg@ietf.org instead. In either case, please retain the beginning of the Sub=
ject line to allow automated sorting.

Abstract

   Continuity Check, Proactive Connectivity Verification and Remote
   Defect Indication functionalities are required for MPLS-TP OAM.

   Continuity Check monitors the integrity of the continuity of the
   label switched path for any loss of continuity defect. Connectivity
   verification monitors the integrity of the routing of the label
   switched path between sink and source for any connectivity issues.
   Remote defect indication enables an End Point to report, to its
   associated End Point, a fault or defect condition that it detects on
   a pseudo wire, label switched path or Section.

   This document specifies methods for proactive continuity check,
   continuity verification, and remote defect indication for MPLS-TP
   label switched paths, pseudo wires and Sections using Bidirectional
   Forwarding Detection.


The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/


No IPR declarations have been submitted directly on this I-D.
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

--_002_60C093A41B5E45409A19D42CF7786DFD52212CB37AEUSAACMS0703e_
Content-Type: application/vnd.ms-excel;
	name="Last Call Comments with resolutionv6.xls"
Content-Description: Last Call Comments with resolutionv6.xls
Content-Disposition: attachment;
	filename="Last Call Comments with resolutionv6.xls"; size=53760;
	creation-date="Thu, 09 Jun 2011 17:22:21 GMT";
	modification-date="Tue, 05 Jul 2011 15:51:32 GMT"
Content-Transfer-Encoding: base64

0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAZwAAAAAAAAAA
EAAA/v///wAAAAD+////AAAAAGYAAAD/////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
//////////////////////////////////////////////////////////////////////////8J
CBAAAAYFABMgzQfJwAAABgMAAOEAAgCwBMEAAgAAAOIAAABcAHAABwAAZWFsbGRhdiAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEIAAgCwBGEBAgAAAMABAAA9AQYA
AQACAAMAnAACAA4AGQACAAAAEgACAAAAEwACAAAArwECAAAAvAECAAAAPQASAGgBeADTOxgkOAAA
AAAAAQBYAkAAAgAAAI0AAgAAACIAAgAAAA4AAgABALcBAgAAANoAAgAAADEAGgDIAAAA/3+QAQAA
AAAAAQUBQQByAGkAYQBsADEAGgDIAAAA/3+QAQAAAAAAAQUBQQByAGkAYQBsADEAGgDIAAAA/3+Q
AQAAAAAAAQUBQQByAGkAYQBsADEAGgDIAAAA/3+QAQAAAAAAAQUBQQByAGkAYQBsADEAGgCgAAAA
/3+QAQAAAAAAAQUBQQByAGkAYQBsADEAHgDcAAAA/3+QAQAAAAIAAQcBQwBhAGwAaQBiAHIAaQAx
ABoAyAAAAP9/kAEAAAACAAEFAUEAcgBpAGEAbAAxABoAyAABAAoAvAIAAAACAAEFAUEAcgBpAGEA
bAAxABoAyAABAP9/vAIAAAACAAEFAUEAcgBpAGEAbAAeBBwABQAXAAAiJCIjLCMjMF8pO1woIiQi
IywjIzBcKR4EIQAGABwAACIkIiMsIyMwXyk7W1JlZF1cKCIkIiMsIyMwXCkeBCIABwAdAAAiJCIj
LCMjMC4wMF8pO1woIiQiIywjIzAuMDBcKR4EJwAIACIAACIkIiMsIyMwLjAwXyk7W1JlZF1cKCIk
IiMsIyMwLjAwXCkeBDcAKgAyAABfKCIkIiogIywjIzBfKTtfKCIkIiogXCgjLCMjMFwpO18oIiQi
KiAiLSJfKTtfKEBfKR4ELgApACkAAF8oKiAjLCMjMF8pO18oKiBcKCMsIyMwXCk7XygqICItIl8p
O18oQF8pHgQ/ACwAOgAAXygiJCIqICMsIyMwLjAwXyk7XygiJCIqIFwoIywjIzAuMDBcKTtfKCIk
IiogIi0iPz9fKTtfKEBfKR4ENgArADEAAF8oKiAjLCMjMC4wMF8pO18oKiBcKCMsIyMwLjAwXCk7
XygqICItIj8/Xyk7XyhAXykeBBUApAAQAAAiWWVzIjsiWWVzIjsiTm8iHgQaAKUAFQAAIlRydWUi
OyJUcnVlIjsiRmFsc2UiHgQUAKYADwAAIk9uIjsiT24iOyJPZmYiHgRdAKcALAABWwAkAKwgLQAy
AF0AXAAgACMALAAjACMAMAAuADAAMABfACkAOwBbAFIAZQBkAF0AXAAoAFsAJACsIC0AMgBdAFwA
IAAjACwAIwAjADAALgAwADAAXAApAOAAFAAAAAAA9f8gAAAAAAAAAAAAAADAIOAAFAABAAAA9f8g
AAD0AAAAAAAAAADAIOAAFAABAAAA9f8gAAD0AAAAAAAAAADAIOAAFAACAAAA9f8gAAD0AAAAAAAA
AADAIOAAFAACAAAA9f8gAAD0AAAAAAAAAADAIOAAFAAAAAAA9f8gAAD0AAAAAAAAAADAIOAAFAAA
AAAA9f8gAAD0AAAAAAAAAADAIOAAFAAAAAAA9f8gAAD0AAAAAAAAAADAIOAAFAAAAAAA9f8gAAD0
AAAAAAAAAADAIOAAFAAAAAAA9f8gAAD0AAAAAAAAAADAIOAAFAAAAAAA9f8gAAD0AAAAAAAAAADA
IOAAFAAAAAAA9f8gAAD0AAAAAAAAAADAIOAAFAAAAAAA9f8gAAD0AAAAAAAAAADAIOAAFAAAAAAA
9f8gAAD0AAAAAAAAAADAIOAAFAAAAAAA9f8gAAD0AAAAAAAAAADAIOAAFAAAAAAAAQAgAAAAAAAA
AAAAAADAIOAAFAABACsA9f8gAAD4AAAAAAAAAADAIOAAFAABACkA9f8gAAD4AAAAAAAAAADAIOAA
FAABACwA9f8gAAD4AAAAAAAAAADAIOAAFAABACoA9f8gAAD4AAAAAAAAAADAIOAAFAABAAkA9f8g
AAD4AAAAAAAAAADAIOAAFAAAAAAAAQAoAAAQAAAAAAAAAADAIOAAFAAAAAAAAQAoAAAUAAAAAAAA
AADAIOAAFAAAAA4AAQAgAAAEAAAAAAAAAADAIOAAFAAAAA4AAQAoAAAUAAAAAAAAAADAIOAAFAAG
AAAAAQAgAAAIAAAAAAAAAADAIOAAFAAGAAAAAQAoAAAYAAAAAAAAAADAIOAAFAAHAAAAAQAoAAAY
AAAAAAAAAADAIOAAFAAAAAAAAQAhAAMQAAAAAAAAAADAIOAAFAAAAAAAAQApAAEQAAAAAAAAAADA
IOAAFAAIAAAAAQAoAAAYAAAAAAAAAADAIOAAFAAIAAAAAQAgAAAIAAAAAAAAAADAIOAAFAAJAAAA
AQAgAAAIAAAAAAAAAADAIJMCBAAQgAP/kwIEABGABv+TAgQAEoAE/5MCBAATgAf/kwIEAACAAP+T
AgQAFIAF/2ABAgAAAIUADgDucgAAAAAGAFNoZWV0MYUADgCuqQAAAAAGAFNoZWV0MoUADgC1qgAA
AAAGAFNoZWV0M4wABAABAAEAwQEIAMEBAAAivgEA/AAZIJIBAADwAAAACQAAQ29tbWVudGVyCQAA
Q29tbWVudCAjBwAAQ29tbWVudAwAAEpvZWwgSGFscGVybiwBAFRoZSBsYXN0IHBhcmFncmFwaCBv
ZiB0aGUgbWFpbiB0ZXh0IG9mIHNlY3Rpb24gMy41IHByb3BlciBzcGVjaWZpZXMgdGhhdCBMb2Nr
IEluc3RydWN0IC8gTG9jayBSZXBvcnQgYWN0IGFzIGlucHV0cyB0byB0aGUgQkZEIHN0YXRlIG1h
Y2hpbmUuIFNlY3Rpb24gMy41LjUgaW5kaWNhdGVzIHRoYXQgTEtSIGNhbiBjYXVzZSBhIHRyYW5z
aXRpb24gdG8gdGhlIERPV04gc3RhdGUuICBCdXQgc2VjdGlvbiAzLjUuMiBkb2VzIG5vdCBpbmNs
dWRlIExLUiBpbiBhbnkgb2YgaXRzIHRleHQgb24gRGVmZWN0IGVudHJ5IGNyaXRlcmlhLgYBAEkg
d291bGQgc3VnZ2VzdCB0aGF0IHRoZSBCRkQgQ0MgY29kZSBwb2ludCBiZSByZWZlcmVkIHRvIHdp
dGggYSBkaWZmZXJlbnQgcmVmZXJlbnQgdGhhbiB0aGUgQkdEIENWIGNvZGUgcG9pbnQgKEhIMSBh
bmQgSEgyIG1heWJlPyAgR0cgYW5kIEhIPyksIHVubGVzcyB0aGUgaW50ZW50IHdhcyB0aGF0IHRo
ZXkgYWN0dWFsbHkgYmUgdGhlIHNhbWUsIHdoaWNoIEkgZG8gbm90IGJlbGlldmUgd2FzIHRoZSBw
dXJwb3NlLiAgVGhpcyBpcyBpbiBzZWN0aW9uIDQuMS4/AQBUaGUgdGV4dCBmb3IgdGhlIE1FUC1J
RCBpbiBzZWN0aW9uIDMuMyBzbGlnaHRseSBkb2VzIG5vdCBtYXRjaCB0aGUgZmlndXJlLiAgVGhl
IGZpZ3VyZSBzaW1wbHkgc2F5cyAiVW5pcXVlIE1FUC1JRCBvZiB0aGUgc291cmNlIG9mIHRoZSBC
RkQgcGFja2V0LiIgIFRoZSB0ZXh0IHNheXMgdGhhdCB0aGlzIGlzIGFjdHVhbGx5IGEgVExWLiAg
Q2FuIHRoZSBmaWd1cmUgYmUgbW9kaWZpZWQgdG8gc2F5ICJNRVAtSVQgVExWIHdpdGggdW5pcXVl
IHNvdXJjZSBvZiB0aGUgQkZEIHBhY2tldCIgb3Igc29tZSByZWxhdGVkIHdvcmRpbmcgdGhhdCBp
bmNsdWRlcyBUTFY/iwIAQ2xhcmlmaWNhdGlvbiBxdWVzdGlvbjogIEl0IHNlZW1zIHRvIG1lIGxp
a2VseSBpbiBwcmFjdGljZSB0aGF0IHRoZSBjb25maWd1cmF0aW9uIGZvciBzaW5rIE1FUHMgb24g
YSBub2RlIGlzIGxpa2VseSB0byBjb3ZlciBhbGwgZW5kLXBvaW50cyByZXNpZGluZyBvbiB0aGF0
IG5vZGUuICBJdCBpcyB1bmxpa2VseSB0byBiZSBzZXNzaW9uIHNwZWNpZmljLiAgKFRvIHRoZSBw
b2ludCB0aGF0IGlmIG9uZSBlbmFibGVzIENDIFNpbmsgTUVQIGJlaGF2aW9yLCBhbmQgdGhlbiBh
IG5ldyBMU1AgaXMgY29uZmlndXJlZCwgdGhhdCB3b3VsZCBhbHNvIGJlIGFibGUgdG8gYmUgYSBT
aW5rIE1FUCB3aXRob3V0IGFueSBmdXJ0aGVyIGNvbmZpZ3VyYXRpb24uICBJcyB0aGlzIGNvbnNp
c3RlbnQgd2l0aCB0aGUgd29yZGluZyBpbiBzZWN0aW9uIDMuNCB0aGF0IHRoZSBCRkQgc2Vzc2lv
biBuZWVkcyB0byBiZSBlbmFibGVkIG9uIHRhIGNvbmZpZ3VyZWQgTWFpbnRlbmFuY2UgRW50aXR5
PyAgICAoVHJ5aW5nIHRvIGZpbmQgdGhpcyBsZXZlbCBvZiBkZXRhaWwgaW4gYWxsIHRoZSBkb2N1
bWVudHMgd2FzIGJleW9uZCBtZS4gIElmIHRoaXMgaXMgdGhlIHdheSB0aGluZ3MgYXJlIHJlZmVy
cmVkIHRvIGFsbCB0aGUgdGltZSwgdGhlbiB3ZSBhcmUgZmluZS4pvwAARWRpdG9yaWFsLCBidXQg
YW5ub3lpbmcgZW5vdWdoIHRvIG1lbnRpb24gZWFybHk6IFJGQyBFZGl0b3IgUG9saWN5IGlzIHRo
YXQgYWNyb255bXMgYXJlIG5vdCB1c2UgaW4gYWJzdHJhY3RzLCBhbmQgdGhhdCB0aGV5IHNob3Vs
ZCBiZSBleHBhbmRlZCBvbiB0aGVpciBmaXJzdCB1c2VzIGluIHRoZSBib2R5IG9mIHRoZSBkb2N1
bWVudC74AQBQcm9iYWJseSBlZGl0b3JpYWw6IFNlY3Rpb24gMywgdGhpcmQgbm9uLWJ1bGxldGVk
IHBhcmFncmFwaCBoYXMgdGhlIHN0cmluZzogICAgInRoZSBCRkQgUFctQUNILSAgICBlbmNhcHN1
bGF0ZWQgZm9yIFBXIGZhdWx0IGRldGVjdGlvbiBvbmx5IGVuY2Fwc3VsYXRpb24gY2FuIGJlIC4u
LiIgSSBhbSBub3Qgc3VyZSB3aGF0IGlzIGludGVuZGVkLCBidXQgbXkgYmVzdCBndWVzcyBpcyB0
aGF0IHRoaXMgd2FzIHN1cHBvc2VkIHRvIHNheTogdGhlIFBXLUFDSCBlbmNhcHN1bGF0aW9uIG9m
IEJGRCwgd2hpY2ggaXMgdXNlZCBvbmx5IGZvciBQVyBmYXVsdCBkZXRlY3Rpb24sIGNhbiBiZSAu
Li4gTm90ZTogSWYgdGhhdCBpcyBub3Qgd2hhdCBpcyBpbnRlbmRlZCwgdGhlbiB0aGUgc2VudGVu
Y2UgbmVlZHMgd29yayBzbyB0aGF0IHRoZSByZWFkZXIgY2FuIGZpZ3VyZSBvdXQgYXQgYWxsLCBy
YXRoZXIgdGhhbiBjdXJyZW50bHkgZ3Vlc3NpbmcgYWZ0ZXIgc3RhcmluZyBsb25nIGVub3VnaC4J
AABNYWNoIENoZW4EAABEYXRlqQAAMS5TZWN0aW9uIDMuNSwgbGFzdCBzZW50ZW5jZSBvZiBmaXJz
dCBwYXJhZ3JhcGg6IFBvbGwvZmluYWwgZGlzY2lwbGluZSBjYW4gb25seSB1c2VkIGZvciBWQ0NW
IGFuZCBVRFAvSVAgZW5jYXBzdWxhdGVkIEJGRC4gVGhlcmUgaXMgYSAiYmUiIGxvc3QgYmV0d2Vl
biAiY2FuIiBhbmQgIm9ubHkiLkMBADIuU2VjdGlvbiAzLjUuMjogMS4gQkZEIGNvbnRyb2wgcGFj
a2V0cyBhcmUgcmVjZWl2ZWQgd2l0aCBhbiB1bmV4cGVjdGVkIGVuY2Fwc3VsYXRpb24gKG1pcy1j
b25uZWN0aXZpdHkgZGVmZWN0KSwgdGhlc2UgaW5jbHVkZTogCgogICAgICAgICAgLSBhIFBXIHJl
Y2VpdmluZyBhIHBhY2tldCB3aXRoIGEgR0FMLCBTaW5jZSBHQUwgY2FuIGJlIHVzZWQgZm9yIFBX
KGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtcHdlMy1tcGxzLXRwLWdhbC1p
bi1wdy0wMCksIHRoaXMgc2hvdWxkIG5vdCBiZSBhIGRlZmVjdC4gU3VnZ2VzdCB0byByZW1vdmUg
aXQuKwEAMyBTZWN0aW9uIDMuNS4yOiAgNC4gUmVjZWlwdCBvZiBhbiBleHBlY3RlZCBzZXNzaW9u
IGRpc2NyaW1pbmF0b3Igd2l0aCBhbiB1bmV4cGVjdGVkIGxhYmVsIChtaXMtY29ubmVjdGl2aXR5
IGRlZmVjdCkuLCBGb3IgYSByZWNlaXZlciwgaG93IGRvZXMgaXQga25vdyB0aGF0IHRoZSBzZXNz
aW9uIGRpc2NyaW1pbmF0b3IgaXMgdmFsaWQgYnV0IHRoZSBsYWJlbCBpcyBpbnZhbGlkPyBJTUhP
LCB0aGlzIGRlZmVjdCBpcyBqdXN0IGFub3RoZXIgZGVzY3JpcHRpb24gb2YgZGVmZWN0IDMgLiBT
dWdnZXN0IHRvIHJlbW92ZSBpdC4YAQA0LlNlY3Rpb24gMy41LjQuMiAiIEV4aXQgZnJvbSBhIG1p
c2NvbmZpZ3VyYXRpb24gZGVmZWN0IG9jY3VycyB3aGVuIHR3byBjb25zZWN1dGl2ZSBDQyBvciBD
ViBmcmFtZXMgaGF2ZSBiZWVuIHJlY2VpdmVkIHdpdGggdGhlIGV4cGVjdGVkIE0gYml0IHNldHRp
bmcuIiBJTUhPLCB0aGlzIHNlbnRlbmNlIGlzIGxpdHRsZSBiaXQgdmFndWUsIGFuZCBzaW5jZSB0
aGlzIGRyYWZ0IG9ubHkgZGVmaW5lcyBmb3IgUDJQIExTUCwgd2h5IG5vdCBqdXN0IHNheSAiLi4u
d2l0aCBNIGJpdCBjbGVhci4i0gEANS4gU2VjdGlvbiAzLjUuNC4zICJFeGl0IGZyb20gYSBtaXMt
Y29ubmVjdGl2aXR5IGRlZmVjdCBzdGF0ZSBvY2N1cnMgd2hlbiBubyBDViBtZXNzYWdlcyBoYXZl
IGJlZW4gcmVjZWl2ZWQgd2l0aCBhbiBpbmNvcnJlY3Qgc291cmNlIE1FUC1JRCBmb3IgYSBwZXJp
b2Qgb2YgMy41IHNlY29uZHMuIiwgc2luY2UgdGhlcmUgYXJlIHNldmVyYWwgZGVmZWN0cyBsaXN0
ZWQgaW4gU2VjdGlvbiAzLjUuMiBhbmQgdGhpcyBpcyBvbmx5IG9uZSBjb25kaXRpb24gZm9yIGV4
aXRpbmcgZnJvbSBhIG1pcy1jb25uZWN0aXZpdHkgZGVmZWN0IHN0YXRlLiBIb3cgYWJvdXQgIkV4
aXQgZnJvbSBhIG1pcy1jb25uZWN0aXZpdHkgZGVmZWN0IHN0YXRlIG9jY3VycyB3aGVuIG5vIENW
IG1lc3NhZ2VzIHdpdGggbWlzLWNvbm5lY3Rpdml0eSBkZWZlY3RzIGhhdmUgYmVlbiByZWNlaXZl
ZCBmb3IgYSBwZXJpb2Qgb2YgMy41IHNlY29uZHMgIlwAADYuIFNlY3Rpb24gMy41LjUgSW4gRmln
dXJlIDUsIHNlZW1zIHRoYXQgaXQgaXMgbGFjayBvZiAiQUlTLUxESSwgTEtSIiBpbnB1dHMgZm9y
IERPV04gc3RhdGUuEAAAU2FzaGEgVmFpbnNodGVpbtICAEknZCBsaWtlIHRvIHJlbWluZCB5b3Ug
dGhhdCBSb2IgYW5kIEkgaGF2ZSBhbHJlYWR5IHF1ZXN0aW9uZWQgdGhlIGRlY2lzaW9uIHRvIGNo
YW5nZSB0aGUgQkZEIHN0YXRlIG1hY2hpbmUgYnkgZGlzYWJsaW5nIGluIHNvbWUgY2FzZSB0aGUg
UG9sbC9GaW5hbCBzZXF1ZW5jZS4gVGhlIHNpdHVhdGlvbiBhcyBwcmVzZW50ZWQgaW4gdGhlIGRy
YWZ0IHNlZW1zIHRvIGludHJvZHVjZSBldmVuIG1vcmUgcHJvYmxlbXMuIEUuZy4sIFJGQyA1ODg1
IGFsbG93cyB0byBydW4gQkZEIGluIFZDQ1Ygd2l0aG91dCBVRFAvSVAgZW5jYXBzdWxhdGlvbiBi
dXQgZm9sbG93cyB0aGUgcHJvY2VkdXJlcyBzcGVjaWZpZWQgaW4gUkZDIDU4ODAgYW5kIDU4ODEg
d2hpY2gsIHRvIHRoZSBiZXN0IG9mIG15IHVuZGVyc3RhbmRpbmcsIGluY2x1ZGUgdXNhZ2Ugb2Yg
UG9sbC9GaW5hbCBzZXF1ZW5jZS4gSXQgaXMgbXkgdW5kZXJzdGFuZGluZyB0aGF0IEJGRCBmb3Ig
YW4gTVBMUy1UUCBMU1Agd291bGQgbG9vayBleGFjdGx5IGFzIEJGRCBpbiBWQ0NWIChpbmNsdWRp
bmcgdGhlIHNhbWUgY29kZSBwb2ludCkuCklmIHRoaXMgaXMgY29ycmVjdCwgaG93IHNob3VsZCB0
aGUgaW1wbGVtZW50YXRpb24gZGlzdGluZ3Vpc2ggYmV0d2VlbiAiUFdFMyBtb2RlIiAod2hlcmUg
cG9sbC9maW5hbCBhcmUgdXNlZCkgYW5kICJNUExTLVRQIG1vZGUgd2hlcmUgdGhleSBzZWVtIHRv
IGJlIHByb2hpYml0ZWQ/DwAATWFydGluIFZpZ29yZXV44AAAaXQgbG9va3MgbGlrZSB5b3UgZGlk
IG5vdCBpbXBsZW1lbnQgdGhlIGNoYW5nZTogID4gT0xEOiBQb2xsL2ZpbmFsIGRpc2NpcGxpbmUg
Y2FuIG9ubHkgdXNlZCBmb3IgVkNDViBhbmQgVURQL0lQIGVuY2Fwc3VsYXRlZCBCRkQgID4gTkVX
OiBQb2xsL2ZpbmFsIGRpc2NpcGxpbmUgTVVTVCBub3QgYmUgdXNlZCBvbiB0aGUgQXNzb2NpYXRl
ZCBDaGFubmVscyB0aGlzIGRvY3VtZW50IGRlZmluZXMOAABLYW5uYW4gU2FtcGF0aFQCAU0AYQB5
ACAAYgBlACAAdABoAGUAIABmAG8AbABsAG8AdwBpAG4AZwAgAHMAZQBuAHQAZQBuAGMAZQAmIC4A
IAAgAEEAIABmAHUAcgB0AGgAZQByACAAYQByAHQAaQBmAGEAYwB0ACAAbwBmACAASQBQACAAZQBu
AGMAYQBwAHMAdQBsAGEAdABpAG8AbgAgAGkAcwAgAHQAaABhAHQAIABDAFYAIABtAGkAcwAtAGMA
bwBuAG4AZQBjAHQAaQB2AGkAdAB5ACAAZABlAGYAZQBjAHQAIABkAGUAdABlAGMAdABpAG8AbgAg
AGMAYQBuACAAYgBlACAAcABlAHIAZgBvAHIAbQBlAGQAIABiAHkAIABpAG4AZgBlAHIAcgBpAG4A
ZwAgAE0ARQBQAF8ASQBEACAAbwBuACAAdABoAGUAIABiAGEAcwBpAHMAIABvAGYAIAB0AGgAZQAg
AGMAbwBtAGIAaQBuAGEAdABpAG8AbgAgAG8AZgAgAHQAaABlACAAcwBvAHUAcgBjAGUAIABJAFAA
IABhAGQAZAByAGUAcwBzACAAYQBuAGQAIAAiAG0AeQAgAGQAaQBzAGMAcgBpAG0AaQBuAGEAdABv
AHIAIgAgAGYAaQBlAGwAZABzAC4AIAAgAEMAYQBuACAAYgBlACAAZQB4AHQAZQBuAGQAZQBkAC8A
cgBlAHAAaAByAGEAcwBlAGQAIABhAHMAIABmAG8AbABsAG8AdwBzACAAdABvACAAbQBhAGsAZQAg
AGkAdAAgAGUAeABwAGwAaQBjAGkAdAAgAGYAbwByACAASQBQACAAYgBhAHMAZQBkACAAQgBGAEQA
JiBBACAAZgB1AHIAdABoAGUAcgAgAGEAcgB0AGkAZgBhAGMAdAAgAG8AZgAgAEkAUAAgAGUAbgBj
AGEAcABzAHUAbABhAHQAaQBvAG4AIABpAHMAIAB0AGgAYQB0ACAAQwBWACAAbQBpAHMALQBjAG8A
bgBuAGUAYwB0AGkAdgBpAHQAeQAgAGQAZQBmAGUAYwB0ACAAZABlAHQAZQBjAHQAaQBvAG4AIABj
AGEAbgAgAGIAZQAgAHAAZQByAGYAbwByAG0AZQBkACAAYgB5ACAAaQBuAGYAZQByAHIAaQBuAGcA
IABNAEUAUABfAEkARAAgAG8AbgAgAHQAaABlACAAYgBhAHMAaQBzACAAbwBmACAAdABoAGUAIABj
AG8AbQBiAGkAbgBhAHQAaQBvAG4AIABvAGYAIAB0AGgAZQAgAHMAbwB1AHIAYwBlACAASQBQACAA
YQBkAGQAcgBlAHMAcwAgAGEAbgBkACAAIgBtAHkAIABkAGkAcwBjAHIAaQBtAGkAbgBhAHQAbwBy
ACIAIABmAGkAZQBsAGQAcwAuACAAVwBoAGUAbgAgAEEAQwBIACAAaQBzACAAbgBvAHQAIABiAGUA
aQBuAGcAIAB1AHMAZQBkACwAIABDAFYAIABpAHMAIABwAHUAcgBlAGwAeQAgAGIAYQBzAGUAZAAg
AG8AbgAgAFMAbwB1AHIAYwBlACAASQBQACAAQQBkAGQAcgBlAHMAcwAuAAoACgAKAABGZW5nIEh1
YW5nagIATFNQIE1FUCBJRCBpbiBkcmFmdC1pZXRmLW1wbHMtdHAtaWRlbnRpZmllcnMtMDMgaXM6
IE5vZGVfSUQ6OlR1bm5lbF9OdW06OkxTUF9OdW0sIGFuZCBmb3IgTFNQIE1FRyBJRDogKDcuMS4y
LjEuKSBTaW5jZSBhIE1FRyBwZXJ0YWlucyB0byBhIHNpbmdsZSBNUExTLVRQIExTUCwgSVAgY29t
cGF0aWJsZSBNRUdfSURzIGZvciBNUExTLVRQIExTUHMgYXJlIHNpbXBseSB0aGUgY29ycmVzcG9u
ZGluZyBMU1BfSURzLiAgV2Ugbm90ZSB0aGF0IHdoaWxlIHRoZSB0d28gaWRlbnRpZmllcnMgYXJl
IHN5bnRhY3RpY2FsbHkgaWRlbnRpY2FsLCB0aGV5IGhhdmUgICAgZGlmZmVyZW50IHNlbWFudGlj
cy4gIFRoaXMgc2VtYW50aWMgZGlmZmVyZW5jZSBuZWVkcyB0byBiZSBtYWRlIGNsZWFyLiAgRm9y
IGluc3RhbmNlIGlmIGJvdGggYSBNUExTLVRQIExTUF9JRCBhbmQgTVBMUy1UUCBMU1AgTUVHX0lE
cyBhcmUgdG8gYmUgZW5jb2RlZCBpbiBUTFZzIGRpZmZlcmVudCB0eXBlcyBuZWVkIHRvIGJlIGFz
c2lnbmVkIGZvciB0aGVzZSB0d28gaWRlbnRpZmllcnMuIHlvdSBjYW4gb25seSBkZXRlY3Qgd3Jv
bmcgTUVQIElELCB0aGF0J3MgVW5leHBlY3RlZCBNRVAsIGl0IGlzIG5vdCBNaXMtbWVyZ2UuFAAA
SmlzaG51IEFyYXZpbmRha3NoYW6lAAAgSW4gdGhlIGRyYWZ0IGl0IGlzIG1lbnRpb25lZCB0aGF0
IE1FUCBoYXMgdG8gYmUgY29uZmlndXJlZCBmb3Igb3BlcmF0aW9uIGFzIGVpdGhlciBDQyBNRVAg
b3IgYSBDViBNRVA/IEhvdyBkbyB5b3UgZG8gdGhpcz8gSXMgdGhlcmUgYW55IGRyYWZ0IG9uIE1F
UCBjb25maWd1cmF0aW9uPwoWAgBXaHkgaXMgdGhlcmUgYSBzaW5nbGUgY29kZSBwb2ludCBhbGxv
Y2F0ZWQgZm9yIGJvdGggQ0MgYW5kIENWPyBJZiB0aGVyZSB3ZXJlIHR3byBkaWZmZXJlbnQgY29k
ZSBwb2ludHMsIGl0IHdvdWxkIGFsbG93IG1pcy1jb25maWd1cmF0aW9uIGFsYXJtIHRvIGJlIGdl
bmVyYXRlZCBpbiBjYXNlIENDIG1vZGUgaXMgdXNlZCBiZXR3ZWVuIENWIE1FUHM/IFRoZSBwcmVz
ZW50IGRyYWZ0IGluIHNlY3Rpb24gMy4xIGhhcyBzYW1lIGZpbGxlciB2YWx1ZSAweEhIIHRvIGJl
IGZpbGxlZCBieSBJQU5BIFBXIEFDaCByZWdpc3RyeSBhbmQgaXMgbm90IGNsZWFyIGlmIHRoZXJl
IHdpbGwgYmUgdHdvIGRpZmZlcmVudCBBQ2ggIGNvZGUgcG9pbnQuIENhbiB5b3UgcGwgaGF2ZSBh
IG5vdGUgdGVsbGluZyB0aGF0IHRoZSBleHBlY3RhdGlvbiBmcm9tIElBTkEgaXMgdG8gZ2V0IHR3
byBkaWZmZXJlbnQgY29kZSBwb2ludHMgaW4gdGhlIGRyYWZ0IHRpbGwgd2UgZ2V0IHNwZWNpZmlj
IElBTkEgY29kZSBwb2ludCBtZW50aW9uZWQgYmVsb3cgYnkgeW91PwoJAABUb20gUGV0Y2h7AABB
IG1pbm9yIHF1aXJrOyB0aGUgZXhwYW5zaW9ucyBnaXZlbiBpbiBzMi4zIG9mIHRoaXMgSS1EIGZv
ciBNSVAgYW5kIE1FUCBhcmUgb3V0IG9mIGxpbmUgd2l0aCB0aG9zZSB1c2VkIGluIG90aGVyIE1Q
TFMgSS1Ecy4MAABFcmljIE9zYm9ybmWjAQBTZWN0aW9uIDE6IFRoZSBmaXJzdCBwYXJhZ3JhcGgg
aW50cm9kdWNlcyBDQyBhbmQgQ1YgYnV0IGRvZXNuJ3QgbWVudGlvbiBSREkuIFBlcmhhcHM6IE9M
RDogQm90aCBQV3MgYW5kIE1QTFMtVFAgTFNQcyBbMTBdIGVtdWxhdGluZyB0cmFkaXRpb25hbCB0
cmFuc3BvcnQgY2lyY3VpdHMgbmVlZCB0byBwcm92aWRlIHRoZSBzYW1lIENDIGFuZCBwcm9hY3Rp
dmUgQ1YgY2FwYWJpbGl0aWVzIGFzIHJlcXVpcmVkIGluIFJGQyA1ODYwWzNdLiBORVc6IEJvdGgg
UFdzIGFuZCBNUExTLVRQIExTUHMgWzEwXSBlbXVsYXRpbmcgdHJhZGl0aW9uYWwgdHJhbnNwb3J0
IGNpcmN1aXRzIG5lZWQgdG8gcHJvdmlkZSB0aGUgc2FtZSBSREkgYW5kIHByb2FjdGl2ZSBDQyBh
bmQgQ1YgY2FwYWJpbGl0aWVzIGFzIHJlcXVpcmVkIGluIFJGQyA1ODYwWzNdLmwAAFNlY3Rpb24g
Mi4xOiAiUkRJOiBSZW1vdGUgRGVmZWN0IEluZGljYXRpb24uICAiIFBlcmlvZCBhZnRlciAnSW5k
aWNhdGlvbicgdGhhdCBpc24ndCBwcmVzZW50IGluIG90aGVyIHRlcm1zLjwAICB6AABTZWN0aW9u
IDM6IEZpcnN0IHBhcmFncmFwaCByZWZlcnMgdG8gJ0FDaCBlbmNhcHN1bGF0ZWQgQkZEJywgc2hv
dWxkIHByb2JhYmx5IGJlICdBQ0ggZW5jYXBzdWxhdGVkJyBvciAnQUNILWVuYWNhcHN1bGF0ZWQn
LkcAAFNlY3Rpb24gMzogIHMvUkRJIGlzIGNvbW11bmljYXRlZDovUkRJIGlzIGNvbW11bmljYXRl
ZC8oc3B1cmlvdXMgY29sb24pdAEAU2VjdGlvbiAzOiBUaGUgcGFyYWdyYXBoIGF0IHRoZSBib3R0
b20gb2YgcC4gNSBiZWdpbnMgJ0EgZnVydGhlciBhcnRpZmFjdCBvZiBJUCBlbmNhcHN1bGF0aW9u
JyBidXQgbm90aGluZyBwcmlvciB0byB0aGF0IHJlZmVycyB0byBpdHNlbGYgYXMgYW4gJ2FydGlm
YWN0Jy4gIFBlcmhhcHM6ICJBZGRpdGlvbmFsbHksIHdoZW4gdXNpbmcgSVAgZW5jYXBzdWxhdGlv
biwgQ1YgbWlzLWNvbm5lY3Rpdml0eSBkZWZlY3QgZGV0ZWN0aW9uIGNhbiBiZSBwZXJmb3JtZWQg
YnkgaW5mZXJyaW5nIE1FUF9JRCBvbiB0aGUgYmFzaXMgb2YgdGhlIGNvbWJpbmF0aW9uIG9mIHRo
ZSBzb3VyY2UgSVAgYWRkcmVzcyBhbmQgIm15IGRpc2NyaW1pbmF0b3IiIGZpZWxkcy4ipQEAU2Vj
dGlvbiAzLjE6IiBCb3RoIENDIGFuZCBDViBtb2RlcyBhcHBseSB0byBQV3MsIE1QTFMgTFNQcyAo
aW5jbHVkaW5nIFNQTUVzKSwgYW5kIFNlY3Rpb25zLiIgSXQgaXMgdW5jbGVhciB3aGV0aGVyIHRo
aXMgc2VudGVuY2UgaXMgaW50ZW5kZWQgdG8gZXhjbHVkZSB0aGluZ3MgdG8gd2hpY2ggQ0MgYW5k
IENWIGRvIG5vdCBhcHBseSAoZS5nLiAiQm90aCBDQyBhbmQgQ1YgbW9kZXMgYXBwbHkgKm9ubHkq
IHRvIFBXcywgTVBMUyBMU1BzK1NQTUVzLCBhbmQgU2VjdGlvbnMiKSBvciB3aGV0aGVyIGl0J3Mg
c3VwcG9zZWQgdG8gYmUgaW5jbHVzaXZlICgiQm90aCBDQyBhbmQgQ1YgbW9kZXMgYXBwbHkgdG8g
YWxsIHBlcnRpbmVudCBNUExTLVRQIHN0cnVjdHVyZXMsIGluY2x1ZGluZyBQV3MsIExTUHMsIFNQ
TUVzLCBhbmQgU2VjdGlvbnMiLlwAAFNlY3Rpb24gMy4zOiAndHJhbnNtaXR0ZWQgYXMgTVBMUyBs
YWJlbGVkIHBhY2tldCcgLT4gJ3RyYW5zbWl0dGVkIGFzIGFuIE1QTFMgbGFiZWxlZCBwYWNrZXQn
6wAAU2VjdGlvbiAzLjMuMiBhbmQgMy4zLjM6IEEgbnVtYmVyIG9mIHJlZmVyZW5lY3MgdG8gInRo
aXJkIHR3byBiaXQiIGFuZCAic2l4dGVlbiBiaXQiIHJhdGhlciB0aGFuICIzMi1iaXQiIGFuZCAi
MTYtYml0Ii4gIFRoaXMgaXMgaW5jb25zaXN0ZW50IHdpdGggb3RoZXIgZG9jdW1lbnRzIGFuZCBw
YXJ0cyBvZiB0aGlzIGRyYWZ0OyBJTU8gbnVtYmVycywgcmF0aGVyIHRoYW4gd29yZHMsIHNob3Vs
ZCBiZSB1c2VkLsUAAFNlY3Rpb24gMy40OiBFeHRyYSBwdW5jdHVhdGlvbiBpbiAiIGNvbmZpZ3Vy
ZWQgTWFpbnRlbmFuY2UgRW50aXR5IChNRSkuLiIgQWxzbywgdGhpcyBzZWN0aW9uIGlzIGZpdmUg
cGFyYWdyYXBocyB0aGF0IGFyZSBlYWNoIG9uZSBzZW50ZW5jZSBsb25nLiBDb25zaWRlciBjb2xs
YXBzaW5nIHRoZW0gaW50byBvbmUgb3IgdHdvIHBhcmFncmFwaHM/4gAAU2VjdGlvbiAzLjU6IFRo
ZSBmaXJzdCB1c2Ugb2YgJ1RoZSBiYXNlIHNwZWMnICg1dGggcGFyYWdyYXBoKSBoYXMgbm8gcmVm
ZXJlbmNlLiAgVGhpcyBjYW4gYmUgZml4ZWQgYnkgY2hhbmdpbmcgdGhlIGZpcnN0IHNlbnRlbmNl
IGluIHRoZSBwcmV2aW91cyBwYXJhZ3JhcGggdG8gIiBDb29yZGluYXRlZCBvcGVyYXRpb24gaXMg
YXMgZGVzY3JpYmVkIGluIFs0XSwgdGhlIEJGRCBiYXNlIHNwZWMiLkMAAFNlY3Rpb24gMy41LjM6
ICd0cmFmZmljIGFzIGNvbnNlcXVlbnQnIC0+ICd0cmFmZmljIGFzIGEgY29uc2VxdWVudCcQAABT
RzE1L1ExMCBsaWFpc29uVQEAU2VjdGlvbiAzLjUuMiwgVGhlIHRleHQgc2F5cyAiQkZEIGNvbnRy
b2wgcGFja2V0cyBhcmUgcmVjZWl2ZWQgd2l0aCBhbiB1bmV4cGVjdGVkIGVuY2Fwc3VsYXRpb24g
KG1pcy1jb25uZWN0aXZpdHkgZGVmZWN0KSIuIEJGRCBjb250cm9sIHBhY2tldCBpcyBqdXN0IHBh
cnQgb2YgY2MtY3YtcmRpIE9BTSBhcyBpbiBGaWd1cmUgMywgc28gdGhlIHF1ZXN0aW9uIGlzIGlm
IHRoZSB2ZXJpZmljYXRpb24gaXMgb25seSBmb3IgdGhpcyBhcmVhIGV2ZW4gaWYgY3YgbW9kZS4g
SSBhc2sgZm9yIGNsYXJpZmljYXRpb24gd2l0aCB0ZXh0IHByb3Bvc2FsICMgVGhpcyB3YXMgYWRk
cmVzc2VkIGxhc3Qgd2Vlay49AQBTZWN0aW9uIDMuNS4yLCBUaGUgdGV4dCBzYXlzICJCRkQgY29u
dHJvbCBwYWNrZXRzIGFyZSByZWNlaXZlZCB3aXRoIGFuIHVuZXhwZWN0ZWQgZW5jYXBzdWxhdGlv
biAobWlzLWNvbm5lY3Rpdml0eSBkZWZlY3QpIi4gRXZlbiBpZiBvbmx5IEJGRCBjb250cm9sIHBh
Y2tldCwgd2hhdCBkb2VzIGl0IG1lYW4gYnkgInVuZXhwZWN0ZWQgZW5jYXBzdWxhdGlvbiI/IC0t
IGl0IGlzIG5vdGVkIHRoYXQgQkZEIGNvbnRyb2wgcGFja2V0IGluY2x1ZGVzIHRpbWVyIHZhbHVl
LCBzbyBkb2VzIHRoZSBzbyBjYWxsZWQgdW5leHBlY3RlZCBwZXJpb2QgbWVhbiB0aGlzP/YAAFNl
Y3Rpb24gMy41LjIgZW5kIG9mIDFzdCBwYXJhZ3JhcGgsIFRoZSB0ZXh0IHNheXMgIkJGRCBzZXNz
aW9uIHRpbWVzIG91dCAoTG9zcyBvZiBDb250aW51aXR5IGRlZmVjdCkiLiBXaHkgaXMgQkZEIHNl
c3Npb24gdGltZXMgb3V0IGRpcmVjdGx5IGRlYWx0IGFzIGVxdWFsIHRvIExPQyBQbGVhc2UgcHJv
dmlkZSB0aGUgY2xhcmlmaWVkIHRleHQgaGVyZS4gSXMgKGUuZy4gTG9zcyBvZiBDb250aW51aXR5
IGRlZmVjdCkgYmV0dGVyP8MAAFNlY3Rpb24gMy4zIGFmdGVyIDR0aCBwYXJhLCBYMSB0byBYMyBh
cmUgZGVmaW5lZC4gVGhlcmUgaXMgbm90IGRlc2NyaXB0aW9uIG9mIHRoZSBkZWZlY3QgZHVlIHRv
IHRoZSBtaXNtYXRjaCBYaSAoZS5nLiBzZW5kIGFzIFgxIGJ1dCByZWNlaXZlciBpcyBzZXQgWDIp
LiBUaGlzIHNob3VsZCBiZSBjbGFyaWZpZWQgaW4gc2VjdGlvbiAzLjUueB4BAFNlY3Rpb24gMy4x
LCBQYXJhIDMsIFBsIGFkZCBhIG5vdGUgbWVudGlvbmluZyB0aGF0IENDIGFuZCBDViB3aWxsIGhh
dmUgc2VwYXJhdGUgQUNoIENvZGUgUG9pbnQgYXMgaXQgaXMgbm90IGNsZWFyIHRoYXQgYm90aCB3
aWxsIGhhdmUgc2VwYXJhdGUgY29kZSBwb2ludCBhcyB0aGUgcGxhY2UgaG9sZGVyIGZvciBib3Ro
IG1lbnRpb24gMHhISCBpbiBhZGRpdGlvbiB0byB0aGUgb25lIG1lbnRpb25lZCBpbiBzZWN0aW9u
IDUgb3IgdXNlIHRoZSBzYW1lIHBsYWNlaG9sZGVyIGFzIGluIFNlY3Rpb24gNS40AQBTZWN0aW9u
IDMuNSwgUGFyYSAxICJJbiB0aGUgcmFyZSBjaXJjdW1zdGFuY2Ugd2hlcmUgYW4gb3BlcmF0b3Ig
aGFzIGEgcmVhc29uIHRvIGNoYW5nZSBzZXNzaW9uIHBhcmFtZXRlcnMsIHBvbGwvZmluYWwgZGlz
Y2lwbGluZSBpcyB1c2VkLiIgVGhpcyBjYW4gY3JlYXRlIGlzc3VlIG9mIGludGVyb3BlcmFiaWxp
dHkgaXNzdWUgaWYgb25lIGVuZCBNRVAgc3RhcnRzIGNoYW5naW5nIHRoZSByYXRlIGFsbCBvZiBz
dWRkZW4gZXZlbiBpZiBpdCBpcyBhIHJhcmUgY2FzZS4gVGhpcyBvcHRpb24gc2hvdWxkIG5vdCBi
ZSBldmVyIGluY2x1ZGVkLrMBAFNlY3Rpb24gNSwgUGFyYSA1ICIgVGhlIGJhc2Ugc3BlYyBpcyB1
bmNsZWFyIG9uIGFzcGVjdHMgb2YgaG93IGEgc2Vzc2lvbiB3aXRoIGEgQkZEIHNvdXJjZSBzZXQg
dG8gemVybyBpbnRlcnZhbCBiZWhhdmVzLiIgVGhlIGNsYXVzZSBzaG91bGQgc2F5IHRoYXQgaXQg
aXMgTk9UIHJlY29tbWVuZGVkIHRvIHNldCBCRkQgdG8gemVybyBpbnRlcnZhbCBmb3IgdGhlIHNh
a2Ugb2YgYXZvaWRpbmcgdW53YW50ZWQgY29uZmlndXJhdGlvbiBhbmQgaGVuY2UgdGhlIGFkZGl0
aW9uYWwgZGlzY3Vzc2lvbiBvbiB0aGUgZm9sbG93aW5nIHBhci4gc2hvdWxkIG5vdCBiZSBhZGRl
ZCBpbiB0aGUgZHJhZnQuIFRoZXJlIHNob3VsZCBiZSBhIGNvbmZpZ3VyYXRpb24gb3B0aW9uIHRv
IGtlZXAgdGhlIE1FRyBhbmQgTUVQIHdpdGhvdXQgQkZEIGFjdHVhbGx5IHJ1bm5pbmcgRTJFLvAA
AFNlY3Rpb24gMy41LjIsIFBhcmEgMSAmIDIsIElmIGEgTUVQIGNhbiBiZSBjb25maWd1cmVkIGFz
IGVpdGhlciBDQyAob3IgQ1YpbW9kZSwgdGhlbiBpdCBnZXRzIGEgQkZEIHdpdGggQ1YgY29kZSBw
b2ludCBpdCBzaGFsbCByYWlzZSBhIG1pc2NvbmZpZ3VyYXRpb24gYWxhcm0gYW5kIHZpY2UgdmVy
c2EuIEluIGNhc2UgTUVQIG9wZXJhdGUgaW4gQ0MgYW5kIENWIG1vZGUgdGhlbiB0aGlzIGlzIG5v
dCBhcHBsaWNhYmxlLowAAFNlY3Rpb24gMy41LjYsIFBhcmEgMSwgSXQgd291bGQgYmUgZ29vZCBp
ZiB3ZSBjYW4gbWVudGlvbiBhbGwgdGhlIHBhcmFtZXRlcnMgd2hpY2ggYXJlIGNvbmZpZ3VyYWJs
ZSBsaWtlIE1FUCBjYW4gYmUgaW4gQ0MsIENWIG9yIENDJkNWIG1vZGUu1gEAV2Ugd291bGQgbGlr
ZSBjbGFyaWZpY2F0aW9uIG9mIHRoZSBiYWNrd2FyZHMgY29tcGF0aWJpbGl0eSByZXF1aXJlbWVu
dHMgYW5kIGNvbnNpZGVyYXRpb25zLiBOb3RlIHRoZSByZXN1bHRzIG9mIHRoZSBpbnRlcm9wIHRl
c3RpbmcgYW5kIGFzayB3aGF0IHN0ZXBzIGFyZSBiZWluZyB0YWtlbiB0byBpbXByb3ZlIHRoZSBk
cmFmdCB0byBlbnN1cmUgdGhhdCB3ZSBoYXZlIGFuIGludGVyb3BlcmFibGUgZHJhZnQuIE5vdGUg
dGhhdCB0aGUgcmVxdWlyZW1lbnRzIGV4cHJlc3NlZCBieSBhIHNpZ25pZmljYW50IG51bWJlciBv
ZiBtZW1iZXJzIG9mIFNHMTUgaGF2ZSBub3QgYmVlbiBtZXQgYW5kIHRoYXQgU0cxNSB3aWxsIG5v
dCBiZSBhYmxlIHRvIHJlYWNoIGNvbnNlbnN1cyB0byBzdXBwb3J0IHRoaXMgZHJhZnQgb3IgdG8g
bWFrZSBub3JtYXRpdmUgcmVmZXJlbmNlcyB0byBpdCBmcm9tIElUVS1UIFJlY29tbWVuZGF0aW9u
cy4aAQBQbGVhc2UgYWRkIHRoZSBmb2xsb3dpbmcgcGFyYWdyYXBoLCB3aGV0aGVyIGluIGludHJv
ZHVjdGlvbiBvciBhcyBhIHNlcGFyYXRlIHNlY3Rpb24sIGFzIGl0IGlzIGFuIGltcG9ydGFudCBj
bGFyaWZpY2F0aW9uOgoiQkZELWJhc2VkIE9BTSBmdW5jdGlvbnMgZGVzY3JpYmVkIGluIHRoaXMg
ZHJhZnQgd2lsbCBOT1QgYmUgYmFja3dhcmRzIGNvbXBhdGlibGUgd2l0aCBSRkM1ODgwIGZyb20g
YSBuZXR3b3JrIHZpZXdwb2ludCwgYW5kIHdpbGwgbm90IGhhdmUgdGhlIHNhbWUgY29kZXBvaW50
LiIjAQBTZWN0aW9uIDMuMSBsYXN0IHBhci4sIFBsZWFzZSBhZGQgdGhlIHRleHQ6ICJCb3RoIEND
K0NWIHBhY2tldHMgbXVzdCBiZSBkZXBsb3llZCBpbiBldmVyeSBCRkQgaW5zdGFuY2Ugc28gYSBz
ZXJ2aWNlIGludGVyZXN0ZWQgaW4gQ1YgbmV2ZXIgcmVjZWl2ZXMgbGVha3MgZnJvbSBzZXJ2aWNl
cyBub3QgaW50ZXJlc3RlZCBpbiBDVi4iICJBdCBzeXN0ZW0gaW5pdGlhbGl6YXRpb24sIG9ubHkg
Q1ZzIGFyZSBleGNoYW5nZWQsIHRvIHByZXZlbnQgYSBtaXNjb25uZWN0ZWQgc2Vzc2lvbiBmcm9t
IGdvaW5nIHVwLiJBAQBTZWN0aW9uIDMuNS4yLFRoZSB0ZXh0ICJJRiBCRkQgYXV0aGVudGljYXRp
b24gaXMgdXNlZCwgcmVjZWlwdCBvZiBhIG1lc3NhZ2Ugd2l0aCBpbmNvcnJlY3QgYXV0aGVudGlj
YXRpb24gaW5mb3JtYXRpb24gKHBhc3N3b3JkLCBNRDUgZGlnZXN0LCBvciBTSEExIGhhc2gpIiBz
aG91bGQgYmUgY3V0IGZyb20gdGhpcyBsaXN0IG9mIENWIGVudHJ5IGNyaXRlcmlhLiBPdGhlcndp
c2UsIGEgbWFsaWNpb3VzIHVzZXIgKHRoZSByZWFzb24gdW5kZXJzdG9vZCB0byB1c2UgYXV0aGVu
dGljYXRpb24pIGNvdWxkIGVhc2lseSBicmluZyBzZXJ2aWNlIGRvd24gYXQgd2lsbC6ZAABTZWN0
aW9uIDMuNS42LCBDb3VsZCB0aGUgYXV0aG9ycyBwbGVhc2Ugc3RhdGUgdGhlIGZ1bGwgbGlzdCBv
ZiBwYXJhbWV0ZXJzIG9uZSBuZWVkcyB0byBjb25maWd1cmUgZm9yIGEgc2Vzc2lvbiwgYXMgY2Fw
dHVyZWQgaW4gdGhlIHdlZWsgMTQtMTgvRmViIGluIFExMD+LAABTZWN0aW9uIDMuNS43LCBJbiBR
MTAgY2xhcmlmaWNhdGlvbiBzZXNzaW9uLCBpdCB3YXMgZXhwbGFpbmVkIHRoYXQgZGlzY3JpbWlu
YXRvcnMgaGF2ZSBwbGF0Zm9ybSBzY29wZS4gUGxlYXNlIHJlZmxlY3QgdGhhdCBpbiB0aGlzIHNl
Y3Rpb24utgEAU2VjdGlvbiAzLjMmMy41LjIsIG1pc21lcmdpbmcgZGV0ZWN0aW9uLCB3aGVuIGRl
dGVjdGluZyBtaXNtZXJnaW5nIE1FUCBuZWVkIGV4cGVjdGVkIE1FUF9JRCBvciBNRUdfSUQsIHRo
ZXkgY2FuIGJlIGZvdW5kIGluICIgVW5pcXVlIE1FUC1JRCBvZiBzb3VyY2Ugb2YgdGhlIEJGRCBw
YWNrZXQiIHdoaWNoIGNvbnNpc3Qgb2YgMyBkaWZmZXJlbnQgVExWcy4gRGlmZmVyZW50IGNvbWJp
bmF0aW9uIG9mIHRoZXNlIFRMVnMgd2lsbCBpbnZvbHZlIGRpZmZlcmVudCBwb2xpY2llcyBmb3Ig
bWlzbWVyZ2luZyBkZXRlY3Rpb24gYW5kIGluIHNvbWUgY2FzZSBjb25maWd1cmF0aW9uIG1heSBi
ZSBuZWVkZWQgYmVjYXVzZSBjZXJ0YWluIFRMViBpcyBub3QgY2FycmllZCBpbiBwYWNrZXQuIEZ1
dGhlciBjbGFyaWZpY2F0aW9uIG1heSBiZSBuZWVkZWQgZm9yIHRoaXMgaXNzdWUuiwAAU2VjdGlv
biAzLjEgMiBkZXBlbmRlbmRhbnQgbW9kZSBmb3IgY2MgYW5kIGN2LCBob3cgdG8gZW5zdXJlIEND
IGFuZCBjdiBtb2RlIGFyZSB1c2VkIGFsbCBNRUcgaW4gb3JkZXIgdG8gZ3JhcnJlbnR1ZSA1MG1z
IHByb3RlY3Rpb24gc3dpdGNoP5wAAFNlY3Rpb24gMy4xIGNjLWN2LXJkaSBpcyB1c2VkIGluIHB3
LCBsc3AsIFNQTUUsIGhvdyB0byBzdXBwb3J0IFBXLCBpdCBpcyBub3QgY2xlYXIgaW4gdGhlIGRy
YWZ0LiBhbmQgaG93IHRvIGFsaWduIFZDQ1YgaW4gUFcsIGl0IGRlZmluZSA0dGggdHlwZSBvZiBQ
VyBWQ0NWP3UAAFNlY3Rpb24gMy4zLjEsIE1FUCBJRCByZWZlciB0byBkcmFmdC1pZCwgd2l0aCBJ
UCBiYXNlZCBNRVAgSUQsIGhvdyB0byBkaXN0aW5ndWlzaCBNSVAgbWlzY29uZmlndXJlIGFuZCBN
RUcgbWlzbWVyZ2VyP5cAAFNlY3Rpb24gMy41LCBkcmFmdC1jYy1jdi1yZGkgc3VwcG9ydCBvbmx5
IGNvLXJvdXRlZCBCaWRpcmVjdGlvbmFsIExTUCBhbmQgQXNzb2NpYXRlZCBCaWRpcmVjdGlvbmFs
IExTUCwgaG93IHRvIHN1cHBvcnQgVW5pZGlyZWN0aW9uYWwgcDJwIGFuZCBwMm1wIExTUD/eAABT
ZWN0aW9uIDMuNSwgd2hlbiBzdXBwb3J0IGFzc29jaWF0ZWQgYmlkaXJlY3Rpb25hbCBsc3AsIDIg
aW5kZXBlbmRhbnQgc2Vzc2lvbnMgdXNlZCwgaG93IHRvIGNvbm5lY3Rpb24gdGhpcyBpbmRlcGVu
ZGF0YW50IHNlc3Npb24sIGJlY2F1c2UgaXQgaXMgYmVsb25nIHRvIG9uZSBhY2NvY2lhdGVkIExT
UCwgZnJvbSBtYW5hZ2VtZW50IHZpZXcsIGl0IHNob3VsZCBiZSBvbmUgc2Vzc2lvbi44AQBTZWN0
aW9uIDMuNS4xIE9uIHRyYW5zaXRpb24gdG8gdGhlIFVQIHN0YXRlLCBtZXNzYWdlIHBlcmlvZGlj
aXR5IGNoYW5nZXMgdG8gdGhlIG5lZ290aWF0ZWQgYW5kL29yIGNvbmZpZ3VyZWQgcmF0ZSBhbmQg
dGhlIGRldGVjdCBpbnRlcnZhbCBzd2l0Y2hlcyB0byBkZXRlY3QgbXVsdGlwbGllciB0aW1lcyB0
aGUgc2Vzc2lvbiBwZWVyJ3MgVHggUmF0ZS4gSXQgaXMgYW1iaWd1b3VzIGZvciB1c2luZyB0aGUg
d29yZCAiYW5kL29yIi4gY2xhcmlmeSB0aGUgdXNlIG9mIHRoZSBjb25maWd1cmVkIHBlcmlvZGlj
aXR5IGR1cmluZyBuZWdvdGlhdGlvbi6OAABTZWN0aW9uIDMuNS4xIGl0IGlzIG5vdCBjbGVhciB0
byBob3cgdG8gY29uZmlndXJlIERldGVjdCBNdWx0IGFuZCBpbnN1cmUgaXQgaXMgbm90IGNoYW5n
ZSBkdXJpbmcgdHJhbnNwb3J0IG9yIGhvdyB0byBkZXRlY3QgbWlzIGNvbmZpZ3VyYXRpb24/pQAA
U2VjdGlvbiAzLjUuMSBuZWdvdGlvbi4gImFuZC9vciIgY29uZmlndXJhdGlvbiBwZXJpb2QgaXMg
dXNlZCBpbiBjYy1jdi1yZGksIGFuZCBCRkQgcGFja2V0IGluIEdhY2gsIGhvdyB0byBpbnRlcndv
cmsgd2l0aCBCRkQgaW4gSVAvTVBMUywgdGhpcyByZXF1aXJtZW50IGlzIHJlcXVlc3QuUgAAU2Vj
dGlvbiAzLjUuMiBNRVAgdG8gZW50ZXIgdGhlIGRlZmVjdCBzdGF0ZS0tIGlmIFNpbmdhbCBEZWdy
YWRlLCBob3cgdG8gZGVhbCB3aXRoP0MAAE5lZWQgdG8gY2xhcmlmeSB0aGUgYmVoYXZpb3VyIHdo
ZW4gWW91ckRpc2NyaW1pbmF0b3I9MCBpcyByZWNlaXZlZC6NAABOZWVkIHRvIGNsYXJpZnkgRGV0
ZWN0IE11bHQgYmVoYXZpb3VyLgpBZnRlcndhcmRzLCBpdCB3YXMgY2xhcmlmaWVkIHRoYXQgRGV0
ZWN0IE11bHQgaXMgZml4ZWQgdG8gMyB3aGVuIEJGRCBydW5zIHVuZGVyIHRoZSBuZXcgQUNIIGNv
ZGVwb2luPAAgIAB0c1wAAENsYXJpZnkgd2hhdCB0eXBlcyBvZiBwYWNrZXRzIGFyZSBleGNoYW5n
ZWQgZHVyaW5nIHRoZSBpbml0aWFsaXphdGlvbiBwcm9jZWR1cmU/IENWIHBhY2tldHMuPwAAQ2xh
cmlmeSB3aGV0aGVyIENWIG5lZWRzIHRvIGJlIHVzZWQgb24gYWxsIHRoZSBzZXNzaW9ucyBvciBu
b3QuNgAAQ2xhcmlmeSB0aGF0IFAvRiBpcyBpZ25vcmVkIGlmIHVzZWQgYnkgdGhlIG90aGVyIHBl
ZXIuZwAAQ2xhcmlmeSB0aGF0IGJhY2t3YXJkIGNvbXBhdGliaWxpdHkgaXMgYWNoaWV2ZWQgYnkg
c3VwcG9ydGluZyBib3RoIGJhc2UgQkZEIGFuZCBUUCBCRkQgb24gdGhlIHNhbWUgYm94LoQAAGNs
YXJpZnkgdGhhdCB0aGUgc3BlYyBjb3ZlciBib3RoIGJhc2UgQkZEIGFuZCBUUCBCRkQuIFRoZSB0
d28gYmVoYXZpb3VycyBjYW4gYmUgZ290IGJ5IGRpZmZlcmVudCBjb25maWd1cmF0aW9uIChtYXkg
aGVscCBhbiBleGFtcGxlKUEAAENsYXJpZnkgdGhhdCB0aGUgcHJvZmlsZSBpcyBhcHBsaWNhYmxl
IHRvIFNlY3Rpb25zLCBMU1BzIGFuZCBQV3MuugABaQBuAHQAcgBvAGQAdQBjAHQAaQBvAG4AOgAg
AGMAbABhAHIAaQBmAHkAIAB0AGgAZQAgAHMAdABhAHQAZQBtAGUAbgB0ACAAHCBQAHIAbwBjAGUA
ZAB1AHIAZQBzACAAZgBvAHIAIAB1AG4AaQAtAGQAaQByAGUAYwB0AGkAbwBuAGEAbAAgAEwAUwBQ
AHMAIABhAHIAZQAgAGYAbwByACAAZgB1AHIAdABoAGUAcgAgAHMAdAB1AGQAeQAdIC4AIABTAHUA
ZwBnAGUAcwB0AGUAZAAgAGMAaABhAG4AZwBlACAAHCBQAHIAbwBjAGUAZAB1AHIAZQBzACAAZgBv
AHIAIAB1AG4AaQAtAGQAaQByAGUAYwB0AGkAbwBuAGEAbAAgAFAAMgBQACAAYQBuAGQAIABQADIA
TQBQACAATABTAFAAcwAgAGEAcgBlACAAZgBvAHIAIABmAHUAcgB0AGgAZQByACAAcwB0AHUAZAB5
AB0gsAABcwBlAGMAdABpAG8AbgAgADMALgA1ADoAIABjAGwAYQByAGkAZgB5ACAAHCBDAG8AbwBy
AGQAaQBuAGEAdABlAGQAIABvAHAAZQByAGEAdABpAG8AbgAgAGkAcwAgAGEAcwAgAGQAZQBzAGMA
cgBpAGIAZQBkACAAaQBuACAAWwA0AF0AHSAuACAATgBvAHQAIABhAGwAbAAgAHQAaABlACAAYgBl
AGgAYQB2AGkAbwB1AHIAcwAgAGEAcgBlACAAdABoAGUAIABzAGEAbQBlACAAYQBuAGQAIAB0AGgA
ZQByAGUAZgBvAHIAZQAgAHMAaABvAHUAbABkACAAYgBlACAAaQBuAGQAaQBjAGEAdABlAGQAIAB3
AGgAaQBjAGgAIABvAG4AZQBzACAAYQByAGUAIABhAGMAYwBlAHAAdABhAGIAbABlACAAZgBvAHIA
IABCAEYARAAgAFQAUAAuAE4AAFNlY3Rpb24gMy41LjE6IENsYXJpZnkgdGhhdCB0aGUgcmF0ZSB3
aXRoIE1QTFMtVFAgd2lsbCBiZSB0aGUgY29uZmlndXJlZCByYXRlLjkAAGxpc3QgcGFyYW1ldGVy
cyB0aGF0IG5lZWQgdG8gYmUgY29uZmlndXJlZCAoaW4gYXBwZW5kaXg/KV0AAExDQzE6IGNsYXJp
ZnkgdGhlIGJlaGF2aW91ciBvZiB0aGUgaGFuZGxpbmcgZGlzY3JpbWluYXRvciBhbmQgdGhlIHJh
aXNpbmcvY2xlYXJpbmcgb2YgZGVmZWN0cyUAAExDQzI6IGRlc2NyaWJlIHRoZSBzdGFydC11cCBw
cm9jZWR1cmUtAABMQ0MzOiBjbGFyaWZ5IHRoZSB1c2Ugb2YgdGhlIG11bHRpcGxpZXIgZmlsZWR1
AABMQ0M0OiBkdXJpbmcgdGhlIGluaXRpYXRpb24gb2YgYSBjb25uZWN0aW9uIENWIHBhY2tldHMg
YXJlIGV4Y2hhbmdlZCwgY2xhcmlmeSBieSBzaG93aW5nIHRoZSBvcmRlciBhdCBzb3VyY2UgYW5k
IHNpbmtkAABMQ0M1OiB3aGljaCBwYXJ0IG9mIHRoZSBjb21wbGV0ZSBzZXQgb2YgaW5pdGlhdGlv
biBwYWNrZXQgZXhjaGFuZ2UgY2FuL3dpbGwgYmUgdXNlZCBieSBNUExTLVRQIC0gUElEUAAATEND
NjogY2xhcmlmeSB0aGUgZGlmZmVyZW5jZSBpbiBwZXJpb2RpY2l0eSBvZiB0aGUgQ0MgYW5kIENW
IHBhY2tldCB0cmFuc21pc3Npb244AABMQ0M3OiBjbGFyeWZ5IHRoZSB1c2Ugb2YgdGhlIFR4IGFu
ZCBSeCBmaWVsZHMgaW4gdGhlIFBEVWgAAExDQzg6IGNsYXJpZnkgdGhlIGJhY2t3YXJkcyBjb21w
YXRpYmlsaXR5IHdpdGggZS5nLiB0aGUgVkNDViBtb2RlIGFuZCBob3cgdGhpcyBhZmZlY3RzIHRo
ZSBjb25maWd1cmF0aW9uMAAATENDOTogd2hlcmUgYXJlIHRoZSByZXF1aXJlbWVudHMgZm9yIG5l
Z290aWF0aW9uOwAATENDMTA6IHdoZXJlIGFyZSB0aGUgcmVxdWlyZW1lbnRzIGZvciBpbmNsdWRp
bmcgZGlhZ25vc3RpY3NRAABMQ0MxMTogaG93IGlzIHRoZSBjb25maXJtYXRpb24gYWNoaWV2ZWQg
d2hlbiB0aGUgc2luayBNRVAgcmV0dXJucyB0byB0aGUgVVAgc3RhdGVjAABMQ0MxMjogY2xhcmlm
eSB0aGUgaW50ZXJwcmV0YXRpb24gb2YgUkRJLCBhbmQgaG93IHRoZSBzaW5rIE1FUCBpcyBrZXB0
IGluIHRoZSBVUCBzdGF0ZSBpbiB0aGlzIGNhc2VwAABMQ0MxMzogY2xhcmlmeSB0aGUgdXNlIG9m
IHRoZSBjb25maWd1cmVkIHBlcmlvZGljaXR5IGR1cmluZyBuZWdvdGlhdGlvbiwgYWxzbyBpbiB2
aWV3IG9mIGJhY2t3YXJkcyBjb21wYXRpYmlsaXR5UwAATENDMTQ6IGNsYXJpZnkgd2h5IHRoZSBi
YWNrd2FyZHMgY29tcGF0aWJpbGl0eSBkb2VzIG5vdCBhZmZlY3QgdGhlIGludGVyb3BlcmFiaWxp
dHlGAABMQ0MxNTogYXJlIENDIGFuZCBDViBhbHdheXMgb24/IGNsYXJpZnksIHNlZSBhbHNvIExD
QzYgZm9yIHBlcmlvZGljaXR5fwAATENDMTY6IGNsYXJpZnkgaG93IENDL0NWL1JESSBjYW4gYmUg
dXNlZCBpbiBhc3NvY2lhdGVkIGJpLWRpcmVjdGlvbmFsIGFwcGxpY2F0aW9ucywgYW5kIGlzIHRo
aXMgYXBwbGljYWJsZSBmb3IgTFNQIGFuZCBzZWN0aW9uP0UAAExDQzE3OiBpcyB0aGlzIChMQ0Mx
NikgYWxzbyBhcHBsaWNhYmxlIHRvIFBXIGFuZCBWQ0NWIGltcGxlbWVudGF0aW9uc10AAExDQzE4
OiBjbGFyaWZ5IHRoZSB1c2Ugb2YgcG9sbC1maW5hbCwgZXNwZWNpYWxseSB0aGUgZGVwZW5kZW5j
eSBvZiB0aGUgYXBwbGljYXRpb24vZGVwbG95bWVudD8AAExDQzE5OiBjb25zaWRlciBhZGRpbmcg
YW4gYXBwZW5kaXggdG8gc2hvdyB0eXBpY2FsIGFwcGxpY2F0aW9uc1EAAExDQzIwOiBjbGFyaWZ5
IHRoZSByYWlzaW5nL2NsZWFyaW5nIG9mIGRlZmVjdHMgYXMgd2VsbCBhcyBhbnkgY29uc2VxdWVu
dCBhY3Rpb25zLGUAAExDQzIxOiB1c2UgY29uc2lzdGVudCBkZWZlY3QgbmFtZXMsIGJ1dCBub3Qg
bmVjZXNzYXJpbHkgdGhlIElUVS1UIGNvb252ZW50aW9uIChlLmcgZERFRyBmb3IgREVHUkFERUQp
DgAAU2hhaHJhbSBEYXZhcmlUAABDb21tZW50IHJlbGF0aW5nIHRvIE5PVCB0cmVhdGluZyB1bmV4
cGVjdGVkIE9BTSBlbmNhcC4gQXMgYSBtaXMtY29ubmVjdGl2aXR5IGRlZmVjdC4WAABjbGFyaWZp
Y2F0aW9uIHJlcXVpcmVkKwAAdXBkYXRlIHRvIDMuMSwgMy4zLCAzLjUgcmVxdXJpZWQgdG8gY2xh
cmlmeSYAAXUAcABkAGEAdABlACAAZgBpAGcAdQByAGUAIAB0AG8AIABzAGEAeQAgAE0ARQBQAC0A
SQBEACAAbwBmACAAcwBvAHUAcgBjAGUAJiA7AAByZWFsbHkgYW4gT0FNIGZyYW1ld29yayBjbGFy
aWZpY2F0aW9uIHRoYXQgYSBNRVAgaXMgcGVyIExTUAoAAGVkaXRvcmlhbCAbAABPbiBob2xkIHBl
bmRpbmcgZGlzY3Vzc2lvbnMeAABPbiBob2xkIHBlbmRpbmcgUFdFIHJlc29sdXRpb25kAABjbGFy
aWZ5IDMgdG8gc2F5IGxhYmxlIGFuZCBkaXNjcmltaW5hdG9yIGRvIG5vdCBtYXRjaCwgYW5kIDQg
dG8gc2F5IGRpc2NyaW1pbmF0b3Igbm90IGluIG15IGRhdGFiYXNlCAAAYWNjZXB0ZWQbAABvbiBo
b2xkIHBlbmRpbmcgZGlzY3Vzc2lvbnNsAABjbGFyaWZ5IHRoYXQgdGhlcmUgaXMgb25lIGZvcm1h
dCBwZXIgc2VjdGlvbiwgb25lIHBlciBQVyBhbmQgcmVjZWl2aW5nIGFuIHVuZXhwZWN0ZWQgTUVH
IGVuY29kaW5nIGlzIGEgZmF1bHQtAABjb3ZlcmVkIGJ5IGNvbmZpZ3VyYXRpb24gYXBwZW5kaXgg
dG8gYmUgYWRkZWQTAABlZGl0b3JpYWwsIGFjY2VwdGVkCQAAZWRpdG9yaWFsEgAAaW5jbHVzaXZl
IGFjY2VwdGVkNgAAY2xlYW51cCwgcmVmIHRvIDU4ODAgc2hvdWxkIGJlIDU4ODQgdGhyb3VnaG91
dCB0aGUgZG9jawAAYmVsaWV2ZSBjb25mdXNpb24gaXMgYXJvdW5kICJjb250cm9sIiBwYWNrZXRz
LiBXZSB3aWxsIG1ha2UgZGVzY3JpcHRpb24gb2YgQkZEIHBhY2tldHMgY29uc2lzdGVudCB3aXRo
IDU4ODRxAAB3aWxsIHJldmlldyBkZWYnbiBvZiB1bnBleHBlY3RlZCBlbmNhcCwgdW5leHBlY3Rl
ZCBwZXJpb2QgZG9lcyByZWZlciB0byBCRkQgcGFja2V0IGNvbnRlbnRzLCB3aWxsIHJldmlldyB0
aGUgdGV4dBwAAG1pc3NpbmcgMyA9IExPQyBpcyBieSBkZXNpZ24SAABzYW1lIGFzIGNvbW1lbnQg
MTkOAABzZWUgY29tbWVudCAxNwgAAHJlamVjdGVkUAAAcmVqZWN0ZWQ6IHJlY2VpdmVyIGNhbm5v
dCBrbm93IHNlbmRlciBpbnRlcmxlYXZlLCBzbyByZWNlaXZpbmcgQ0MgaXMgbm90IGEgZmF1bHQi
AABhcyBtdWNoIGFzIHBvc3NpYmxlIC0gc2VlIFJGQyB4eHh4HAAAY292ZXJlZCBieSByZWZlcmVu
Y2UgdG8gNTg4MEkAAHRleHQgdG8gYmUgY2xhcmlmaWVkLCBpZiB5b3Ugd2FudCBBTEwgZGVmZWN0
cyBkZXRlY3RlZCB5b3UgaGF2ZSB0byBydW4gQ1Y5AAB0ZXh0IHRvIGJlIGNsYXJpZmllZCwgcmVw
bHkgbm90IGluIFJSTyBvciBtZ210IGVxdWl2YWxlbnQxAAByZWplY3RlZCwgZHJhZnQgZXhwbGlj
aXRseSBpZGVudGlmaWVzIHRoaXMgYXMgRkZTNAAAY2xhcmlmeSBjb29yL2luZGVwIGFwcGxpZXMg
b3QgYm90aCBhc3NvYyBvciBjb3JvdXRlZCgAAGRlZmF1bHRzIG9uIHRoZSBjb2RlIHBvaW50LCB3
aWxsIGNsYXJpZnkvAABjbGFyaWZ5IHRoYXQgZWFjaCBCRkQgc2Vzc2lvbiB1c2VzIGNvbW1vbiBl
bmNhcOsAAHJlamVjdGVkLCBCRkQgbm90IGRlc2lnbmVkIHRvIGRldGVjdCBzaWduYWwgZGVncmFk
YXRpb24sIG5vIHN1Y2ggY29uZGl0aW9uIGlzIGRlZmluZWQsIFBIWSBsYXllciBwcm9ibGVtcyBh
cmUgaW5wdXQgdG8gQkZEIGFzIGZhdWx0IG1hbmFnZW1lbnQgbWVzc2FnZXMsIGFkamFjZW50IGxp
bmsgZmFpbHVyZSBpbmRpY2F0aW9uIGNvdWxkIGJlIGNvbnNpZGVyZWQgYW4gaW5wdXQgdG8gdGhl
IHN0YXRlIG1hY2hpbmUpAABvbiBob2xkIHBlbmRpbmcgYm9vdHNndHJhcHBpbmcgZGlzY3Vzc2lv
bg0AAHNlZSBjb21lbnQgNTMOAABzZWUgY29tbWVudCA0Mg0AAHJlbGF0ZWQgdG8gNDIfAABvbiBo
b2xkIHBlbmRpbmcgUC9GIGRpc2N1c3Npb25zIQAAY292ZXJlZCBieSBjb25maWd1cmF0aW9uIGFw
cGVuZGl4DAAAd2lsbCBjbGFyaWZ5DgAAc2VlIGNvbW1lbnQgMjUhAABlZGl0b3JpYWwsIHdpbGwg
ZGVsZXRlIG5lZ290aWF0ZWQhAAByZWplY3RlZCBhcyB0b28gdmFndWUgdG8gYWN0IHVwb24OAABz
ZWUgY29tbWVudCA1Nw4AAHNlZSBjb21tZW50IDU4LwAAcmVqZWN0ZWQsIGRvY3VtZW50IGlzIGNs
ZWFyIG9uIG1pb25pbXVtIENWIHJhdGUXAAByZWplY3RlZCAsIHNlZSBSRkMgNTg4NA4AAHNlZSBj
b21tZW50IDYxPgAAc2VlIHJlcXVpcmVtZW50IGZvciB1c2Ugb2YgZXhpc3RpbmcgT0FNIG1lY2hh
bmlzbXMgaW4gUkZDIHh4eHg1AAByZWplY3RlZCwgc2VlIGJhc2Ugc3BlY2lmaWNhdGlvbiBTVEEg
ZmllbGQgaW4gdGhlIFBEVVIAAHJlamVjdGVkLCBzZXNzaW9uIHN0YXRlIGFuZCBkZWZlY3Qgc3Rh
dGUgbm90IHRoZSBzYW1lIHRoaW5nLCBhbmQgdGhlIGRyYWZ0IHNheXMgaXQbAABhZGRyZXNzZWQg
aW4gb3RoZXIgY29tbWVudHMOAABzZWUgY29tbWVudCA3Mx0AAGFkZHJlc3NlZCBpbiBlYXJsaWVy
IGNvbW1lbnRzCgAAc2VlIEcuODExMCMAAHdpbGwgY2hlY2sgZG9jdW1lbnQgZm9yIGNvbnNpc3Rl
bmN5CQAAd2l0aGRyYXduEwAAUHJvcG9zZWQgUmVzb2x1dGlvbhsAAHJlbW92ZSAib25seSBlbmNh
cHN1bGF0aW9uIgkAAERhdmUgV2FyZDwAAHRleHQgc2hvdWxkIGluZGljYXRlIHBlcmlvZGljaXR5
IGlzIGVxdWFsIGluIGJvdGggZGlyZWN0aW9ucwsAAEdyZWcgTWlyc2t5DAAAR3JlZyAgTWlyc2t5
XAIAU2VjdGlvbiAzLjUuMSBzdGF0ZXMgdGhhdCBtZXNzYWdlcyBpbiBET1dOIGFuZCBJTklUIHN0
YXRlcyB0cmFuc21pdHRlZCBhdCByYXRlIG9uZSBwZXIgc2Vjb25kLCAiSW4gYm90aCB0aGUgRE9X
TiBhbmQgSU5JVCBzdGF0ZXMgbWVzc2FnZXMgYXJlIHRyYW5zbWl0dGVkIGF0IGEgcmF0ZSBvZiBv
bmUgcGVyIHNlY29uZCAuLi4iIEJ1dCB0aGUgc2Vjb25kIHBhcnQgb2YgdGhlIHNlbnRlbmNlIHJl
ZmVycyBEZXRlY3Rpb24gVGltZSB0byBib3RoIHN0YXRlcyBldmVuIHRob3VnaCBpdCBoYXMgc2ln
bmlmaWNhbmNlLCBhcyBpbiBSRkMgNTg4MCwgb25seSBpbiB0aGUgSU5JVCBzdGF0ZSAiLi4uIGFu
ZCB0aGUgZGVmZWN0IGRldGVjdGlvbiBpbnRlcnZhbCBpcyBmaXhlZCBhdCAzLjUgc2Vjb25kcyIu
IFBlcmhhcHMgaWYgdGhlIHNlbnRlbmNlIHNwbGl0IGluIHRvIHdpbGwgbWFrZSBpdCBzdHJpY3Rl
cjoiSW4gYm90aCB0aGUgRE9XTiBhbmQgSU5JVCBzdGF0ZXMgbWVzc2FnZXMgYXJlIHRyYW5zbWl0
dGVkIGF0IGEgcmF0ZSBvZiBvbmUgcGVyIHNlY29uZC4gRGVmZWN0IERldGVjdGlvbiBUaW1lIGlu
IElOSVQgc3RhdGUgaXMgZml4ZWQgYXQgMy41IHNlY29uZHMiLh8CAEkgdGhpbmsgdGhhdCAiTVBM
UyBQcm9hY3RpdmUgQ1YiIGlzIG5vdCB0aGUgbW9zdCBkZXNjcmlwdGl2ZSB0YWcgZm9yIENWIG1v
ZGUgQUNIIGNvZGUgcG9pbnQgYmVjYXVzZSwgYXMgbWVudGlvbmVkIGluIFNlY3Rpb24gMywgYm90
aCBDViBhbmQgQ0MgbWVzc2FnZXMgYWxsb3dlZCB3aGVuIHRoaXMgQUNIIHVzZWQuIEkgcHJvcG9z
ZSB0byBuYW1lIEFDSCBjb2RlIHBvaW50IGZvciBDViBtb2RlICJNUExTIFByb2FjdGl2ZSBDQy9D
ViIgYXMgaW4gRmlndXJlIDEgQUNIIEluZGljYXRpb24gb2YgTVBMUy1UUCBDb25uZWN0aXZpdHkg
VmVyaWZpY2F0aW9uLiBJJ2Qgbm90ZSB0aGF0IGluIEZpZ3VyZSAzIEFDSCBzaG91bGQgYmUgY2hh
bmdlZCBmcm9tICIweEhIIEJGRCBDViBDb2RlIFBvaW50IiB0byAiMHhISCBCRkQgQ0MvQ1YgQ29k
ZSBQb2ludCIuIEFuZCBpdCBtaWdodCBiZSB1c2VmdWwgdG8gYWRkIG5ldyBEaWFnIGNvZGUgIlVu
aW50ZW5kZWQgY29ubmVjdGl2aXR5IGVycm9yIiBhbmQgcmVxdWVzdCBjb2RlIHBvaW50IGZyb20g
QkZEIHJlZ2lzdHJ5LuUBAFNpbmNlIElQIGVuY2Fwc3VsYXRpb24gb2YgQkZEIHByb2FjdGl2ZSBD
Qy9DViBjYW4gYmUgdXNlZCB0aGVuIGl0IG1pZ2h0IGJlIGhlbHBmdWwgdG8gbWVudGlvbiB0aGF0
IHByb2FjdGl2ZSBDQy9DViBvcGVyYXRlcyBpbiBDViBtb2RlIHN1cHBvcnRpbmcgQ0MgYW5kIENW
IGZ1bmN0aW9ucy4gQXMgZm9yIFJESSwgaW50ZXJwcmV0YXRpb24gb2YgRGlhZyB2YWx1ZSAzICJO
ZWlnaGJvciBTaWduYWxlZCBTZXNzaW9uIERvd24iIG1pZ2h0IG5vdCBiZSBjb25zaXN0ZW50IHdp
dGggb25lIGdpdmVuIGluIHRoZSBkb2N1bWVudCBhcyAiYSBjb25zZXF1ZW5jZSBvZiB0aGUgc2lu
ayBNRVAgcmVjZWl2aW5nIEFJUyB3aXRoIExESSBzZXQiLiBJdCBjb3VsZCBiZSB0aGF0IERpYWcg
dmFsdWUgNSAiUGF0aCBEb3duIiBpcyBiZXR0ZXIgc3VpdGVkIHRvIGJlIHVzZWQgYXMgaW5kaWNh
dGlvbiBvZiBNRVAgcmVjZWl2aW5nIEFJUyB3aXRoIExESSBiZWluZyBzZXQuCwAASGlkZWtpIEVu
ZG9EAABEZXNjcmlwdGlvbiBvZiBMU1AgTUVQIElEIHNob3VsZCBpbmRpY2F0ZSB0aGF0IGl0IGlz
IGdsb2JhbGx5IHVuaXF1ZScAAE5vIGRpYWdub3N0aWMgY29kZSBmb3IgTWlzLWNvbm5lY3Rpdml0
eTQAAERpc2N1c3Npb24gcG9pbnQsIGlmIG5vdCBuZWVkZWQgZHJhZnQgc2hvdWxkIHNheSB3aHk9
AABOZWVkIHRvIGJlIGNsZWFyIHRoYXQgaW4gbWlzLWNvbm5lY3Rpdml0eSB3ZSBraWxsIGV2ZXJ5
dGhpbmcuDAAAUm9iIFJlbm5pc29uQQAAQ2xhcmlmaWNhdGlvbiB0aGF0IGZpeGVkIGludGVydmFs
IGZvciBsaWZlIG9mIFVQIHN0YXRlIG9mIHNlc3Npb25AAAB3aGVuIGRvZXMgZGV0ZWN0IG11bHQg
c3dpdGNoIGZyb20gMy41IHNlYyB0byBiYXNlZCBvbiBSeGludGVydmFsCwAAQWN0dWFsIGVkaXQ9
AABTZWN0aW9uIDMuNS4yIGluY2x1ZGVzIGxvY2sgcmVwb3J0IGFzIGEgZGVmZWN0IGVudHJ5IGNy
aXRlcmlhIAAAQ2hhbmdlZCB1bml2c2FsbHkgdG8gWFggYW5kIFhYKzEPAABGaWd1cmUgMyBlZGl0
ZWQJAABObyBhY3Rpb24WAABNYW55IGVkaXRvcmlhbCBjaGFuZ2VzEQAAZWRpdGVkIHRvIGNsYXJp
ZnkSAABlZGl0ZWQgYWNjb3JkaW5nbHkPAABGaWd1cmUgNSBlZGl0ZWRgAABTZWN0aW9uIDMuMyBl
ZGl0ZWQgdG8gc2F5IG9ubHkgb25lIGVuY288AIgJAGRpbmcgd2lsbCBiZSB1c2VkLiAzLjUuMiBj
bGFyaWZpZWQgb24gdGhpcyBwb2ludCBhcyB3ZWxsLiEAAENvcnJlY3RlZCBvbiBKb2VscyBjb21t
ZW50IHJvdyA1LhEAAGVkaXRlZCBhY2NvcmRpbmx5EAAAQ2hhbmdlZCB0byBHLUFDaD4AAGV2ZXJ5
IHJlZmVyZW5jZSB0byBhbiBPQU0gcGFja2V0IGNoYW5nZWQgdG8gQkZEIGNvbnRyb2wgcGFja2V0
HQAAYWRkcmVzc2VkIGJ5IGVkaXRzIGZvciByb3cgMTkdAABhZGRyZXNzZWQgYnkgZWRpdHMgZm9y
IHJvdyAxNzQAAERvIG5vdCBiZWxpZXZlIHRoZSBkZXNjcmlwdGlvbiBjYW4gYmUgaW1wcm92ZWQg
dXBvbi4HAABubyBlZGl0IwAAQkZEIG9ubHkgcnVucyBiZXR3ZWVuIE1FUHMsIG5vIGVkaXRZAABT
dWdnZXN0ZWQgdGhhdCBhbiBlZGl0IGxpbmsgdGhlIHR3byBpbmRlcGVuZGVudCBzZXNzaW9ucyB0
b2dldGhlciBhcyBwYXJ0IG9mIHRoZSBzYW1lIE1FRzAAAE5vIGVkaXQsIGFzIHdlIHdpbGwgYmUg
cmVkb2luZyB0aGlzIHRleHQgZm9yIFAvRj0AAHRleHQgYWRkZWQgdG8gcGluIHRoZSBkZXRlY3Qg
bXVsdCBmb3IgeHggYW5kIHh4KzEgY29kZSBwb2ludHMZAAB0ZXh0IGFkZGVkIHRvIHNlY3Rpb24g
My41IQAAdGV4dCBhZGRlZCByZXNvbHZpbmcgcm93IDU2IGFib3ZlHgAAdGV4dCBhZGRlZCB0byAz
LjUuMSB0byBjbGFyaWZ5NgAAU2VjdGlvbiAzLjEgZWRpdGVkIHRvIGNsYXJpZnkgdGhhdCBDViBp
cyBhbHdheXMgaW4gdXNlGQAAdGV4dCBhZGRlZCB0byBzZWN0aW9uIDMuMBYAAGl0IHdhcyBhY3R1
YWxseSByb3cgMjgSAABjb21tZW50IDU2LCBlZGl0ZWQ0AAB0ZXh0IGFkZGVkIHRvIGluZGljYXRl
IElOSVQgc3RhdGUgUERVcyBhcmUgYWx3YXlzIENWIQAAY292ZXJlZCBpbiBjb25maWd1cmF0aW9u
IGFwcGVuZGl4TwAAdGV4dCBhZGRlZCB0byBjbGFyaWZ5IHRoZSBzZXBhcmF0aW9uIG9mIGRlZmVj
dCBhbmQgc2Vzc2lvbiBzdGF0ZSBpbiBzZWN0aW9uIDMuNRsAAGFkZHJlc3NlZCBpbiBwcmV2aW91
cyBlZGl0cw8AAG5vIGZ1cnRoZXIgZWRpdBYAADMuNSBlZGl0ZWQgYWNjb3JkaW5nbHkzAAAzLjUu
MyBpcyBjbGVhciBvbiB0aGlzLCBkaXNjYXJkIGFsbCBub24gT0FNIHRyYWZmaWMuAAB0ZXh0IGFk
ZGVkIGFzIGEgY29uc2VxdW5jZSB0byByZXNvbHZpbmcgcm93IDkzGQAAcmVzdWx0IG9mIFAvRiBk
aXNjdXNzaW9ucy0AAHVuaXF1ZSBhcHBlYXJzIHNldmVyYWwgdGltZXMgaW4gdGhlIHBhcmFncmFw
aCsAAHRleHQgYWRkZWQgdG8gc2F5IFNIT1VMRCBiZSBnbG9iYWxseSB1bmlxdWUYAABkcmFmdCBG
MzJzZWN0aW9uIDQgYWRkZWQVAABkcmFmdCBzZWN0aW9uIDQgYWRkZWRXAABOb3QgY2xlYXIgdGhh
dCB0aGVyZSBpcyBhbiBlZGl0IGluIHRoaXMgZ2l2ZW4gd2UndmUgY29sbGFwc2VkIHRvIG9uZSBt
b2RlIHR3byBQRFUgdHlwZXMGAABlZGl0ZWQtAABBZGRpdGlvbmFsIENvbW1lbnRzIGZyb20gQkZE
IGxpc3QgZGlzY3Vzc2lvbnNsAABTZXBhcmF0ZSBDViBwcm9jZXNzaW5nIGZyb20gdGhlIENDIGFu
ZCBCRkQgc3RhdGUgbWFjaGluZXMgc28gY2FuIGJlIHNwbGl0IG91dCBmcm9tIEgvVyBpbXBsZW1l
bnRhdGlvbnMgb2YgQ0MfAABBY2NlcHRlZCBhbmQgZWRpdGVkIGFjY29yZGluZ2x5IwAAVGV4dCBt
b2RpZmllZCBpbiBhIG51bWJlciBvZiBwbGFjZXMPAABSb2JlcnQgUmVubmlzb24ZAABSb2JlcnQg
UmVubmlzb24vSmVmZiBIYWFzTQAAUHV0IFBvbGwtRmluYWwgZGlzY2lwbGluZSBiYWNrIGludG8g
dGhlIGluaXRpYWxpemF0aW9uIHRvIGFsaWduIHdpdGggUkZDIDU4ODAIAABBY2NlcHRlZDgAAENs
YXJpZnkgaGFuZGluZyBvZiB1bmFjY2VwdGFibGUgc2Vzc2lvbiBjaGFuZ2Ugc2NlbmFyaW9zOwAA
UmVxdWVzdCBmb3IgYSBkaWFnbm9zdGljIGNvZGUgYWRkZWQgdG8gSUFOQSBjb25zaWRlcmF0aW9u
cy4OAABHZW9yZ2UgU3dhbGxvd1QAAElzc3VlIHdpdGggc2V0dGluZyBkaXNjcmltaW5hdG9yIHRv
IHplcm8gb24gdHJhbnNpdGlvbiB0byBkb3duLiBDb250ZXh0IGxvc3QgZm9yIFJESWIAAVQAZQB4
AHQAIABhAGQAZABlAGQAIAB0AG8AIABzAGUAYwB0AGkAbwBuACAAMwAuADUAIAB0AG8AIABkAGkA
cwBjAHUAcwBzACAAcAByAG8AcABvAHMAZQBkACAAYgBlAGgAYQB2AGkAbwByACAAZgBvAHIAIABi
AG8AdABoACAAYwBvAG8AcgBkAGkAbgBhAHQAZQBkACAAYQBuAGQAIABpAG4AZABlAHAAZQBuAGQA
ZQBuAHQAIABtAG8AZABlAHMAJiAgAABTZWN0aW9uIDMuNS4xIGVkaXRlZCBhY2NvcmRpbmdseVkA
AFRleHQgYWRkZWQgdG8gMy41LjEuIHRvIGRlc2NyaWJlIG9wdGlvbiBvZiBlaXRoZXIgaWdub3Jp
bmcgYSBwb2xsIG9yIHRha2luZyBzZXNzaW9uIGRvd24uEQAAZWRpdGVkIGFjb3JkaW5nbHknAABy
ZXZpc2VkIHRvIGluZGljYXRlIENDIG9ubHkgaXMgUkZDIDU4ODUIAABubyBlZGl0IBgAAGRpYWdu
b3N0aWMgY29kZXMgdXBkYXRlZP8A8gAIAPYHAAAMAAAALw4AAEUGAAA6FQAAUA0AAAcgAAAdGAAA
8iUAAAgeAAA+LQAANwUAAJszAACUCwAARz0AAEAVAACtQwAAphsAAJFIAABmAAAAbE0AAEEFAADN
TwAAogcAAHVSAABKCgAABVUAANoMAACMVgAAYQ4AAMRXAACZDwAAblkAAEMRAADLWwAAoBMAAI5c
AABjFAAAll0AAGsVAACxXgAAhhYAAM5jAACjGwAA/2YAANQeAAD+ZwAA0x8AADlpAADqAAAAq2oA
AFwCAADOawAAfwMAABxtAADNBAAAoW4AAFIGAADabwAAiwcAAGMIFQBjCAAAAAAAAAAAAAAVAAAA
AAAAAAIKAAAACQgQAAAGEAATIM0HycAAAAYDAAALAiAAAAAAAAEAAABtAAAATHkAADiIAABwlwAA
I6YAAF2pAAANAAIAAQAMAAIAZAAPAAIAAQARAAIAAAAQAAgA/Knx0k1iUD9fAAIAAQAqAAIAAAAr
AAIAAACCAAIAAQCAAAgAAAAAAAAAAAAlAgQAAAD/AIEAAgDBBBQAAAAVAAAAgwACAAAAhAACAAAA
TQCSBQAAQgByAG8AdABoAGUAcgAgAEgATAAtADIAMAAzADAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAEEAAbcALQEQ++ABwEAAQDqCm8IZAABAA8AWAIBAAEAWAICAAEATABlAHQA
dABlAHIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAQAAAAAAAAABAAAAAgAAAAEAAAD/////AAAAAAAAAAAAAAAAAAAAAERJ
TlUiAHgBtAMAAQiiSs8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADwAAAAEAAAAAAAAAAAAA
AAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAA
eAEAAFNNVEoAAAAAEABoAUIAcgBvAHQAaABlAHIAIABIAEwALQAyADAAMwAwAAAASW5wdXRCaW4A
QVVUTwBSRVNETEwAVW5pcmVzRExMAEJyX1Byb3BzaGVldABEaXNwbGF5AE1lZGlhVHlwZQBTVEFO
REFSRABCcl9Ub25lcnNhdmUAT0ZGAEJyX0RlbnNpdHkAT3B0aW9uMQBCcl9FcnJvclByaW50AFBS
SU5URVJfREVGQVVMVABSZXNvbHV0aW9uAE9wdGlvbjIAT3JpZW50YXRpb24AUE9SVFJBSVQAUGFw
ZXJTaXplAExFVFRFUgBIYWxmdG9uZQBIVF9QQVRTSVpFX0FVVE8AQnJfUmVQcmludABMYXN0Sm9i
AEJyX0pvYk5hbWUAT2ZmAEJyX0VuZEpvYk5hbWUAT2ZmAEJyX1NsZWVwADFfOTlfNQAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAABMSFVCAAAAAQAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAGVhbGxkYXYAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAABFVjAwMjVCMzJFMjZEQgAAAAABAP//AAH//wAAAAAAAAAAAAAAAAAAAAAA
AAAAAAChACIAAQBkAAEAAQABAAIAWAJYAgAAAAAAAOA/AAAAAAAA4D8BAFUAAgAIAH0ADAAAAAAA
2wwPAAIAAgB9AAwAAQABAAAdDwACAAIAfQAMAAIAAgCSDQ8AAgACAH0ADAADAAMAJEQPAAIAAgB9
AAwABAAEAAAiDwACAAIAfQAMAAUABQAAGg8AAgACAH0ADAAGAAYAbRMPAAIAAgAAAg4AAQAAAG0A
AAAAAAYAAAAIAhAAAQAAAAYA/wAAAAAAAAEPAAgCEAADAAAABgD8AwAAAAAAAQ8ACAIQAAQAAAAG
APwDAAAAAAABDwAIAhAABQAAAAYA+wQAAAAAAAEPAAgCEAAGAAAABgD3CAAAAAAAAQ8ACAIQAAcA
AAAGAP0CAAAAAAABDwAIAhAACAAAAAYA+QYAAAAAAAEPAAgCEAAJAAAABgD9AgAAAAAAAQ8ACAIQ
AAoAAAAGAPoFAAAAAAABDwAIAhAACwAAAAYA/AMAAAAAAAEPAAgCEAAMAAAABgD8AwAAAAAAAQ8A
CAIQAA0AAAAGAPoFAAAAAAABDwAIAhAADgAAAAYA/gEAAAAAAAEPAAgCEAAPAAAABgD1CgAAAAAA
AQ8ACAIQABAAAAAGAPwDAAAAAAABDwAIAhAAEQAAAAYA9gkAAAAAAAEPAAgCEAASAAAABgD3CAAA
AAAAAQ8ACAIQABMAAAAGAIwKAAAAAAABDwAIAhAAFAAAAAYACwQAAAAAAAEPAAgCEAAVAAAABgD+
AQAAAAAAAQ8ACAIQABYAAAAGAPoFAAAAAAABDwAIAhAAFwAAAAYA/gEAAAAAAAEPAAgCEAAYAAAA
BgD+AQAAAAAAAQ8ACAIQABkAAAAGAP8AAAAAAAABDwAIAhAAGgAAAAYA+wQAAAAAAAEPAAgCEAAb
AAAABgD6BQAAAAAAAQ8ACAIQABwAAAAGAP4BAAAAAAABDwAIAhAAHQAAAAYA/QIAAAAAAAEPAAgC
EAAeAAAABgD9AgAAAAAAAQ8ACAIQAB8AAAAGAP0CAAAAAAABDwAIAhAAIAAAAAYA/wAAAAAAAAEP
AP0ACgABAAAADwABAAAA/QAKAAEAAQAPAAAAAAD9AAoAAQACAA8ACwAAAP0ACgABAAMADwACAAAA
/QAKAAEABAAPAKAAAAD9AAoAAQAFAA8AsQAAAH4CCgADAAAADwAAAPA//QAKAAMAAQAPAAMAAAB+
AgoAAwACABcAINDjQP0ACgADAAMAFQAEAAAA/QAKAAMABAAPAGgAAAD9AAoAAwAFABUAsgAAAAYA
HwAEAAAADwAAAAAAAAAAQAAADAAp/QkARAMAAMAeAQAD/QAKAAQAAQAPAAMAAAB+AgoABAACABcA
INDjQP0ACgAEAAMAFgAFAAAA/QAKAAQABAAPAGkAAAD9AAoABAAFABUAswAAAAYAGwAFAAAADwAA
AAAAAAAIQAgABgAA/wUAAQUAAAC8BBMABQBEAAAAAEAJAEz//wDAHgEAA/0ACgAFAAEADwADAAAA
fgIKAAUAAgAXACDQ40D9AAoABQADABYABgAAAP0ACgAFAAQADwBqAAAA/QAKAAUABQAPALQAAAAG
ABsABgAAAA8AAAAAAAAAEEAIAAcAAP8FAAEFAAAA/QAKAAYAAQAPAAMAAAB+AgoABgACABcAINDj
QP0ACgAGAAMAFgAHAAAA/QAKAAYABAAVAGsAAAD9AAoABgAFAA8AtQAAAAYAGwAHAAAADwAAAAAA
AAAUQAgACAAA/wUAAQUAAAD9AAoABwABAA8AAwAAAH4CCgAHAAIAFwAg0ONA/QAKAAcAAwAVAAgA
AAD9AAoABwAEAA8AbAAAAP0ACgAHAAUADwC2AAAABgAbAAgAAAAPAAAAAAAAABhACAAJAAD/BQAB
BQAAAP0ACgAIAAEADwADAAAAfgIKAAgAAgAXACDQ40D9AAoACAADABUACQAAAP0ACgAIAAQADwCh
AAAA/QAKAAgABQAbAO0AAAAGABsACQAAAA8AAAAAAAAAHEAIAAoAAP8FAAEFAAAA/QAKAAkAAQAP
AAoAAAB+AgoACQACABgA4NDjQP0ACgAJAAMAFQAMAAAA/QAKAAkABAAPAG0AAAAGABsACgAAAA8A
AAAAAAAAIEAIAAsAAP8FAAEFAAAA/QAKAAoAAQAPAAoAAAB+AgoACgACABgA4NDjQP0ACgAKAAMA
FQANAAAA/QAKAAoABAAPAG4AAAAGABsACwAAAA8AAAAAAAAAIkAIAAwAAP8FAAEFAAAA/QAKAAsA
AQAPAAoAAAB+AgoACwACABgA4NDjQP0ACgALAAMAFgAOAAAA/QAKAAsABAAVAG8AAAD9AAoACwAF
AA8AtwAAAAYAGwAMAAAADwAAAAAAAAAkQAgADQAA/wUAAQUAAAD9AAoADAABAA8ACgAAAH4CCgAM
AAIAGADg0ONA/QAKAAwAAwAWAA8AAAD9AAoADAAEAA8AcAAAAP0ACgAMAAUADwC4AAAABgAbAA0A
AAAPAAAAAAAAACZACAAOAAD/BQABBQAAAP0ACgANAAEADwAKAAAAfgIKAA0AAgAYAODQ40D9AAoA
DQADABYAEAAAAP0ACgANAAQADwBwAAAA/QAKAA0ABQAPALgAAAAGABsADgAAAA8AAAAAAAAAKEAI
AA8AAP8FAAEFAAAA/QAKAA4AAQAPAAoAAAB+AgoADgACABgA4NDjQP0ACgAOAAMAFgARAAAA/QAK
AA4ABAAPAHAAAAD9AAoADgAFAA8AuQAAAAYAGwAPAAAADwAAAAAAAAAqQAgAEAAA/wUAAQUAAAD9
AAoADwABABUAEgAAAH4CCgAPAAIAGAAA0eNA/QAKAA8AAwAVABMAAAD9AAoADwAEAA8AcQAAAAYA
GwAQAAAADwAAAAAAAAAsQAgAEQAA/wUAAQUAAAD9AAoAEAABAA8AFAAAAH4CCgAQAAIAGAAA0eNA
/QAKABAAAwAVABUAAAD9AAoAEAAEAA8AcQAAAAYAGwARAAAADwAAAAAAAAAuQAgAEgAA/wUAAQUA
AAD9AAoAEQABAA8AFgAAAH4CCgARAAIAGAAg0eNA/QAKABEAAwAVABcAAAD9AAoAEQAEAA8AcAAA
AAECBgARAAUAHgAGABsAEgAAAA8AAAAAAAAAMEAIABMAAP8FAAEFAAAA/QAKABIAAQAPABgAAAB+
AgoAEgACABgAwNHjQP0ACgASAAMAFgAZAAAA/QAKABIABAAVAHIAAAD9AAoAEgAFABUAugAAAAYA
GwATAAAADwAAAAAAAAAxQAgAFAAA/wUAAQUAAAD9AAoAEwABABkAGgAAAH4CCgATAAIAGABg0uNA
/QAKABMAAwAaABwAAAD9AAoAEwAEAA8AbAAAAP0ACgATAAUAFQC7AAAABgAbABQAAAAPAAAAAAAA
ADJACAAVAAD/BQABBQAAAP0ACgAUAAEAGQAaAAAAfgIKABQAAgAYAGDS40D9AAoAFAADABUAGwAA
AP0ACgAUAAQAFQBzAAAA/QAKABQABQAPANkAAAAGABsAFQAAAA8AAAAAAAAAM0AIABYAAP8FAAEF
AAAA/QAKABUAAQAPAB0AAAB+AgoAFQACABgAgNLjQP0ACgAVAAMAFQAeAAAA/QAKABUABAAPAHQA
AAD9AAoAFQAFABsAuAAAAAYAGwAWAAAADwAAAAAAAAA0QAgAFwAA/wUAAQUAAAD9AAoAFgABAA8A
HwAAAH4CCgAWAAIAGADg0uNA/QAKABYAAwAWACAAAAD9AAoAFgAEAA8AdQAAAP0ACgAWAAUADwC8
AAAABgAbABcAAAAPAAAAAAAAADVACAAYAAD/BQABBQAAAP0ACgAXAAEADwAfAAAAfgIKABcAAgAY
AODS40D9AAoAFwADABYAIQAAAP0ACgAXAAQADwB1AAAA/QAKABcABQAPALwAAAAGABsAGAAAAA8A
AAAAAAAANkAIABkAAP8FAAEFAAAA/QAKABgAAQAPAB8AAAB+AgoAGAACABgA4NLjQP0ACgAYAAMA
FgAiAAAA/QAKABgABAAPAHUAAAD9AAoAGAAFAA8AvQAAAAYAGwAZAAAADwAAAAAAAAA3QAgAGgAA
/wUAAQUAAAD9AAoAGQABAA8AHwAAAH4CCgAZAAIAGADg0uNA/QAKABkAAwAWACMAAAD9AAoAGQAE
AA8AdQAAAP0ACgAZAAUADwC4AAAABgAbABoAAAAPAAAAAAAAADhACAAbAAD/BQABBQAAAP0ACgAa
AAEADwAfAAAAfgIKABoAAgAYAODS40D9AAoAGgADABYAJAAAAP0ACgAaAAQADwB1AAAA/QAKABoA
BQAPALgAAAAGABsAGwAAAA8AAAAAAAAAOUAIABwAAP8FAAEFAAAA/QAKABsAAQAPAB8AAAB+AgoA
GwACABgA4NLjQP0ACgAbAAMAFgAlAAAA/QAKABsABAAPAHYAAAD9AAoAGwAFAA8AuAAAAAYAGwAc
AAAADwAAAAAAAAA6QAgAHQAA/wUAAQUAAAD9AAoAHAABAA8AHwAAAH4CCgAcAAIAGADg0uNA/QAK
ABwAAwAVACYAAAD9AAoAHAAEAA8AdQAAAP0ACgAcAAUADwC4AAAABgAbAB0AAAAPAAAAAAAAADtA
CAAeAAD/BQABBQAAAP0ACgAdAAEADwAfAAAAfgIKAB0AAgAYAODS40D9AAoAHQADABUAJwAAAP0A
CgAdAAQADwB1AAAA/QAKAB0ABQAPALgAAAAGABsAHgAAAA8AAAAAAAAAPEAIAB8AAP8FAAEFAAAA
/QAKAB4AAQAPAB8AAAB+AgoAHgACABgA4NLjQP0ACgAeAAMAFQAoAAAA/QAKAB4ABAAPAHUAAAD9
AAoAHgAFAA8AuAAAAAYAGwAfAAAADwAAAAAAAAA9QAgAIAAA/wUAAQUAAAD9AAoAHwABAA8AHwAA
AH4CCgAfAAIAGADg0uNA/QAKAB8AAwAVACkAAAD9AAoAHwAEABUAdwAAAP0ACgAfAAUAGwDsAAAA
BgAbACAAAAAPAAAAAAAAAD5ACAAhAAD/BQABBQAAAP0ACgAgAAEADwAfAAAAfgIKACAAAgAYAODS
40D9AAoAIAADABUAKgAAAP0ACgAgAAQADwB1AAAA/QAKACAABQAPALgAAADXAEIAZA4AAFgCVABU
AGkAfABlAGUAZQBXAFcAZQBlAGUAZQBXAFcAYQBlAGUAZQBlAGUAZQBlAGUAZQBlAGUAZQBlAGUA
CAIQACEAAAAGAPsEAAAAAAABDwAIAhAAIgAAAAYA+wQAAAAAAAEPAAgCEAAjAAAABgD8AwAAAAAA
AQ8ACAIQACQAAAAGAP0CAAAAAAABDwAIAhAAJQAAAAYA/AMAAAAAAAEPAAgCEAAmAAAABgD8AwAA
AAAAAQ8ACAIQACcAAAAGAPoFAAAAAAABDwAIAhAAKAAAAAYA/AMAAAAAAAEPAAgCEAApAAAABgD+
AQAAAAAAAQ8ACAIQACoAAAAGAPkGAAAAAAABDwAIAhAAKwAAAAYA+wQAAAAAAAEPAAgCEAAsAAAA
BgD8AwAAAAAAAQ8ACAIQAC0AAAAGAPsEAAAAAAABDwAIAhAALgAAAAYA/gEAAAAAAAEPAAgCEAAv
AAAABgD+AQAAAAAAAQ8ACAIQADAAAAAGAPoFAAAAAAABDwAIAhAAMQAAAAYA/gEAAAAAAAEPAAgC
EAAyAAAABgD9AgAAAAAAAQ8ACAIQADMAAAAGAP4BAAAAAAABDwAIAhAANAAAAAYA/QIAAAAAAAEP
AAgCEAA1AAAABgD8AwAAAAAAAQ8ACAIQADYAAAAGAPwDAAAAAAABDwAIAhAANwAAAAYA/QIAAAAA
AAEPAAgCEAA4AAAABgD9AgAAAAAAAQ8ACAIQADkAAAAGAPkGAAAAAAABDwAIAhAAOgAAAAYA/gEA
AAAAAAEPAAgCEAA7AAAABgD9AgAAAAAAAQ8ACAIQADwAAAAGAP4BAAAAAAABDwAIAhAAPQAAAAYA
/gEAAAAAAAEPAAgCEAA+AAAABgD/AAAAAAAAAQ8ACAIQAD8AAAAGAP4BAAAAAAABDwAIAhAAQAAA
AAYA/gEAAAAAAAEPAAYAGwAhAAAADwAAAAAAAAA/QAgAIgAA/wUAAQUAAAD9AAoAIQABAA8AKwAA
AH4CCgAhAAIAGABA0+NA/QAKACEAAwAWACwAAAD9AAoAIQAEABUAeAAAAP0ACgAhAAUAFQC+AAAA
BgAbACIAAAAPAAAAAAAAAEBACAAjAAD/BQABBQAAAP0ACgAiAAEADwArAAAAfgIKACIAAgAYAEDT
40D9AAoAIgADABYALQAAAP0ACgAiAAQAFQB5AAAA/QAKACIABQAbAMEAAAAGABsAIwAAAA8AAAAA
AACAQEAIACQAAP8FAAEFAAAA/QAKACMAAQAPACsAAAB+AgoAIwACABgAQNPjQP0ACgAjAAMAFQAu
AAAA/QAKACMABAAPAHoAAAD9AAoAIwAFAA8AwgAAAAYAGwAkAAAADwAAAAAAAABBQAgAJQAA/wUA
AQUAAAD9AAoAJAABAA8AKwAAAH4CCgAkAAIAGABA0+NA/QAKACQAAwAVAC8AAAD9AAoAJAAEAA8A
ewAAAP0ACgAkAAUADwC/AAAABgAbACUAAAAPAAAAAAAAgEFACAAmAAD/BQABBQAAAP0ACgAlAAEA
DwArAAAAfgIKACUAAgAYAEDT40D9AAoAJQADABYAMAAAAP0ACgAlAAQADwB8AAAA/QAKACUABQAP
AMAAAAAGABsAJgAAAA8AAAAAAAAAQkAIACcAAP8FAAEFAAAA/QAKACYAAQAPACsAAAB+AgoAJgAC
ABgAQNPjQP0ACgAmAAMAFgAxAAAA/QAKACYABAAPAH0AAAD9AAoAJgAFAA8AwgAAAAYAGwAnAAAA
DwAAAAAAAIBCQAgAKAAA/wUAAQUAAAD9AAoAJwABAA8AKwAAAH4CCgAnAAIAGABA0+NA/QAKACcA
AwAWADIAAAD9AAoAJwAEAA8AfQAAAP0ACgAnAAUADwDCAAAABgAbACgAAAAPAAAAAAAAAENACAAp
AAD/BQABBQAAAP0ACgAoAAEADwArAAAAfgIKACgAAgAYAEDT40D9AAoAKAADABYAMwAAAP0ACgAo
AAQAFQB+AAAA/QAKACgABQAPAMIAAAAGABsAKQAAAA8AAAAAAACAQ0AIACoAAP8FAAEFAAAA/QAK
ACkAAQAPACsAAAB+AgoAKQACABgAQNPjQP0ACgApAAMAFgA0AAAA/QAKACkABAAVAHMAAAD9AAoA
KQAFAA8AwgAAAAYAGwAqAAAADwAAAAAAAABEQAgAKwAA/wUAAQUAAAD9AAoAKgABAA8AKwAAAH4C
CgAqAAIAGABA0+NA/QAKACoAAwAWADUAAAD9AAoAKgAEAA8AfwAAAP0ACgAqAAUAFQDCAAAABgAb
ACsAAAAPAAAAAAAAgERACAAsAAD/BQABBQAAAP0ACgArAAEADwArAAAAfgIKACsAAgAYAEDT40D9
AAoAKwADABUANgAAAP0ACgArAAQADwB9AAAA/QAKACsABQAVAMIAAAAGABsALAAAAA8AAAAAAAAA
RUAIAC0AAP8FAAEFAAAA/QAKACwAAQAPACsAAAB+AgoALAACABgAQNPjQP0ACgAsAAMAFQA3AAAA
/QAKACwABAAPAH0AAAD9AAoALAAFAA8AwgAAAAYAGwAtAAAADwAAAAAAAIBFQAgALgAA/wUAAQUA
AAD9AAoALQABAA8AKwAAAH4CCgAtAAIAGABA0+NA/QAKAC0AAwAVADgAAAD9AAoALQAEAA8AfQAA
AP0ACgAtAAUADwDCAAAABgAbAC4AAAAPAAAAAAAAAEZACAAvAAD/BQABBQAAAP0ACgAuAAEADwAr
AAAAfgIKAC4AAgAYAEDT40D9AAoALgADABUAOQAAAP0ACgAuAAQAFQBzAAAABgAbAC8AAAAPAAAA
AAAAgEZACAAwAAD/BQABBQAAAP0ACgAvAAEADwArAAAAfgIKAC8AAgAYAEDT40D9AAoALwADABUA
OgAAAP0ACgAvAAQADwCAAAAA/QAKAC8ABQAPAMIAAAAGABsAMAAAAA8AAAAAAAAAR0AIADEAAP8F
AAEFAAAA/QAKADAAAQAPACsAAAB+AgoAMAACABgAQNPjQP0ACgAwAAMAFQA7AAAA/QAKADAABAAP
AHsAAAD9AAoAMAAFABUAvwAAAAYAGwAxAAAADwAAAAAAAIBHQAgAMgAA/wUAAQUAAAD9AAoAMQAB
AA8AKwAAAH4CCgAxAAIAGABA0+NA/QAKADEAAwAVADwAAAD9AAoAMQAEABUAgQAAAP0ACgAxAAUA
FQC3AAAABgAbADIAAAAPAAAAAAAAAEhACAAEAAD/BQABBQAAAP0ACgAyAAEADwArAAAAfgIKADIA
AgAYAEDT40D9AAoAMgADABUAPQAAAP0ACgAyAAQADwBuAAAAAQIGADIABQAVAAYAGwAzAAAADwAA
AAAAAIBIQAgANAAA/wUAAQUAAAD9AAoAMwABAA8AKwAAAH4CCgAzAAIAGABA0+NA/QAKADMAAwAV
AD4AAAD9AAoAMwAEABUAggAAAP0ACgAzAAUAGwDDAAAABgAbADQAAAAPAAAAAAAAAElACAA1AAD/
BQABBQAAAP0ACgA0AAEADwArAAAAfgIKADQAAgAYAEDT40D9AAoANAADABUAPwAAAP0ACgA0AAQA
FQCDAAAA/QAKADQABQAVAMIAAAAGABsANQAAAA8AAAAAAACASUAIADYAAP8FAAEFAAAA/QAKADUA
AQAPACsAAAB+AgoANQACABgAQNPjQP0ACgA1AAMAFQBAAAAA/QAKADUABAAVAIQAAAD9AAoANQAF
ABsAxAAAAAYAGwA2AAAADwAAAAAAAABKQAgANwAA/wUAAQUAAAD9AAoANgABAA8AKwAAAH4CCgA2
AAIAGABA0+NA/QAKADYAAwAVAEEAAAD9AAoANgAEAA8AdQAAAP0ACgA2AAUAGwDFAAAABgAbADcA
AAAPAAAAAAAAgEpACAA4AAD/BQABBQAAAP0ACgA3AAEADwArAAAAfgIKADcAAgAYAEDT40D9AAoA
NwADABUAQgAAAP0ACgA3AAQADwCFAAAA/QAKADcABQAbAMYAAAAGABsAOAAAAA8AAAAAAAAAS0AI
ADkAAP8FAAEFAAAA/QAKADgAAQAPACsAAAB+AgoAOAACABgAQNPjQP0ACgA4AAMAFQBDAAAA/QAK
ADgABAAVAIYAAAD9AAoAOAAFABsAxwAAAAYAGwA5AAAADwAAAAAAAIBLQAgAOgAA/wUAAQUAAAD9
AAoAOQABAA8AKwAAAH4CCgA5AAIAGABA0+NA/QAKADkAAwAPAEQAAAD9AAoAOQAEABUAhwAAAP0A
CgA5AAUAGwDCAAAABgAbADoAAAAPAAAAAAAAAExACAA7AAD/BQABBQAAAP0ACgA6AAEADwArAAAA
fgIKADoAAgAYAEDT40D9AAoAOgADAA8ARQAAAP0ACgA6AAQAGwCIAAAABgAbADsAAAAPAAAAAAAA
gExACAA8AAD/BQABBQAAAP0ACgA7AAEADwArAAAAfgIKADsAAgAYAEDT40D9AAoAOwADABUARgAA
AP0ACgA7AAQADwCJAAAA/QAKADsABQAVAMgAAAAGABsAPAAAAA8AAAAAAAAATUAIAD0AAP8FAAEF
AAAA/QAKADwAAQAPACsAAAB+AgoAPAACABgAQNPjQP0ACgA8AAMAFQBHAAAA/QAKADwABAAPAIoA
AAD9AAoAPAAFABUAyQAAAAYAGwA9AAAADwAAAAAAAIBNQAgAPgAA/wUAAQUAAAD9AAoAPQABAA8A
KwAAAH4CCgA9AAIAGABA0+NA/QAKAD0AAwAPAEgAAAD9AAoAPQAEAA8AiwAAAP0ACgA9AAUAFQDK
AAAABgAbAD4AAAAPAAAAAAAAAE5ACAA/AAD/BQABBQAAAP0ACgA+AAEADwArAAAAfgIKAD4AAgAY
AEDT40D9AAoAPgADAA8ASQAAAP0ACgA+AAQADwCMAAAABgAbAD8AAAAPAAAAAAAAgE5ACABAAAD/
BQABBQAAAP0ACgA/AAEADwArAAAAfgIKAD8AAgAYAEDT40D9AAoAPwADABsASgAAAP0ACgA/AAQA
DwCOAAAA/QAKAD8ABQAVAMsAAAAGABsAQAAAAA8AAAAAAAAAT0AIAEEAAP8FAAEFAAAA/QAKAEAA
AQAPACsAAAB+AgoAQAACABgAQNPjQP0ACgBAAAMAGwBLAAAA/QAKAEAABAAPAI0AAAD9AAoAQAAF
ABUA2gAAANcARADyDgAAbAJlAGUAZQBlAGUAZQBlAGUAZQBlAGUAZQBlAFcAZQBlAGUAYQBlAGUA
ZQBlAGUAZQBlAFcAZQBlAGUAVwBlAAgCEABBAAAABgD/AAAAAAAAAQ8ACAIQAEIAAAAGAP0CAAAA
AAABDwAIAhAAQwAAAAYA/QIAAAAAAAEPAAgCEABEAAAABgD/AAAAAAAAAQ8ACAIQAEUAAAAGAP4B
AAAAAAABDwAIAhAARgAAAAYA/gEAAAAAAAEPAAgCEABHAAAABgD/AAAAAAAAAQ8ACAIQAEgAAAAG
AP8AAAAAAAABDwAIAhAASQAAAAYA/gEAAAAAAAEPAAgCEABKAAAABgD+AQAAAAAAAQ8ACAIQAEsA
AAAGAP4BAAAAAAABDwAIAhAATAAAAAYA/wAAAAAAAAEPAAgCEABNAAAABgD+AQAAAAAAAQ8ACAIQ
AE4AAAAGAP4BAAAAAAABDwAIAhAATwAAAAYA/gEAAAAAAAEPAAgCEABQAAAABgD+AQAAAAAAAQ8A
CAIQAFEAAAAGAP0CAAAAAAABDwAIAhAAUgAAAAYA/gEAAAAAAAEPAAgCEABTAAAABgD+AQAAAAAA
AQ8ACAIQAFQAAAAGAP8AAAAAAAABDwAIAhAAVQAAAAYA/gEAAAAAAAEPAAgCEABWAAAABgD/AAAA
AAAAAQ8ACAIQAFcAAAAGAP4BAAAAAAABDwAIAhAAWAAAAAYA/wAAAAAAAAEPAAgCEABZAAAABgD+
AQAAAAAAAQ8ACAIQAFoAAAAGAP4BAAAAAAABDwAIAhAAWwAAAAYA/gEAAAAAAAEPAAgCEABcAAAA
BgD/AAAAAAAAAQ8ACAIQAF0AAAAGAPgHAAAAAAABDwAIAhAAXgAAAAYA+QYAAAAAAAEPAAgCEABf
AAAABgD3CAAAAAAAAQ8ACAIQAGAAAAAGAP4BAAAAAAABDwAGABsAQQAAAA8AAAAAAACAT0AIAEIA
AP8FAAEFAAAA/QAKAEEAAQAPACsAAAB+AgoAQQACABgAQNPjQP0ACgBBAAMADwBMAAAA/QAKAEEA
BAAPAI8AAAD9AAoAQQAFABUAzAAAAAYAGwBCAAAADwAAAAAAAABQQAgABQAA/wUAAQUAAAD9AAoA
QgABAA8AKwAAAH4CCgBCAAIAGABA0+NA/QAKAEIAAwAVAE0AAAD9AAoAQgAEAA8AcAAAAP0ACgBC
AAUADwC4AAAABgAbAEMAAAAPAAAAAAAAQFBACABEAAD+BQABBQAAAP0ACgBDAAEADwArAAAAfgIK
AEMAAgAYAEDT40D9AAoAQwADABUATgAAAP0ACgBDAAQADwCMAAAABgAbAEQAAAAPAAAAAAAAgFBA
CABFAAD/BQABBQAAAP0ACgBEAAEADwArAAAAfgIKAEQAAgAYAEDT40D9AAoARAADAA8ATwAAAP0A
CgBEAAQADwCQAAAA/QAKAEQABQAPALgAAAAGABsARQAAAA8AAAAAAADAUEAIAEYAAP8FAAFFAAAA
vAQTAEUAWgAAAAAWCQBM//8AwB4BAAP9AAoARQABAA8AKwAAAH4CCgBFAAIAGABA0+NA/QAKAEUA
AwAPAFAAAAD9AAoARQAEABUAcwAAAP0ACgBFAAUADwDaAAAABgAbAEYAAAAPAAAAAAAAAFFACABH
AAD/BQABRQAAAP0ACgBGAAEADwArAAAAfgIKAEYAAgAYAEDT40D9AAoARgADABUAUQAAAP0ACgBG
AAQADwCRAAAA/QAKAEYABQAPAMIAAAAGABsARwAAAA8AAAAAAABAUUAIAEgAAP8FAAFFAAAA/QAK
AEcAAQAPACsAAAB+AgoARwACABgAQNPjQP0ACgBHAAMAFQBSAAAA/QAKAEcABAAPAJEAAAD9AAoA
RwAFAA8AwgAAAAYAGwBIAAAADwAAAAAAAIBRQAgASQAA/wUAAUUAAAD9AAoASAABAA8AKwAAAH4C
CgBIAAIAGABA0+NA/QAKAEgAAwAVAFMAAAD9AAoASAAEAA8AkgAAAP0ACgBIAAUADwDNAAAABgAb
AEkAAAAPAAAAAAAAwFFACABKAAD/BQABRQAAAP0ACgBJAAEADwArAAAAfgIKAEkAAgAYAEDT40D9
AAoASQADABUAVAAAAP0ACgBJAAQADwCTAAAA/QAKAEkABQAVAM4AAAAGABsASgAAAA8AAAAAAAAA
UkAIAEsAAP8FAAFFAAAA/QAKAEoAAQAPACsAAAB+AgoASgACABgAQNPjQP0ACgBKAAMAFQBVAAAA
/QAKAEoABAAPAJEAAAD9AAoASgAFAA8AwgAAAAYAGwBLAAAADwAAAAAAAEBSQAgATAAA/wUAAUUA
AAD9AAoASwABAA8AKwAAAH4CCgBLAAIAGABA0+NA/QAKAEsAAwAVAFYAAAD9AAoASwAEABUAlAAA
AP0ACgBLAAUADwDCAAAABgAbAEwAAAAPAAAAAAAAgFJACABNAAD/BQABRQAAAP0ACgBMAAEADwAr
AAAAfgIKAEwAAgAYAEDT40D9AAoATAADABUAVwAAAP0ACgBMAAQADwCVAAAA/QAKAEwABQAPAMIA
AAAGABsATQAAAA8AAAAAAADAUkAIAE4AAP8FAAFFAAAA/QAKAE0AAQAPACsAAAB+AgoATQACABgA
QNPjQP0ACgBNAAMAFQBYAAAA/QAKAE0ABAAPAJYAAAD9AAoATQAFABUAzwAAAAYAGwBOAAAADwAA
AAAAAABTQAgATwAA/wUAAUUAAAD9AAoATgABAA8AKwAAAH4CCgBOAAIAGABA0+NA/QAKAE4AAwAV
AFkAAAD9AAoATgAEABUAlwAAAP0ACgBOAAUADwDCAAAABgAbAE8AAAAPAAAAAAAAQFNACABQAAD/
BQABRQAAAP0ACgBPAAEADwArAAAAfgIKAE8AAgAYAEDT40D9AAoATwADABUAWgAAAP0ACgBPAAQA
FQCXAAAA/QAKAE8ABQAVAMIAAAAGABsAUAAAAA8AAAAAAACAU0AIAFEAAP8FAAFFAAAA/QAKAFAA
AQAPACsAAAB+AgoAUAACABgAQNPjQP0ACgBQAAMAFQBbAAAA/QAKAFAABAAVAJgAAAD9AAoAUAAF
AA8AwgAAAAYAGwBRAAAADwAAAAAAAMBTQAgAUgAA/wUAAUUAAAD9AAoAUQABAA8AKwAAAH4CCgBR
AAIAGABA0+NA/QAKAFEAAwAVAFwAAAD9AAoAUQAEABUAmQAAAP0ACgBRAAUAFQDQAAAABgAbAFIA
AAAPAAAAAAAAAFRACABTAAD/BQABRQAAAP0ACgBSAAEADwArAAAAfgIKAFIAAgAYAEDT40D9AAoA
UgADABUAXQAAAP0ACgBSAAQADwCaAAAA/QAKAFIABQAPAMIAAAAGABsAUwAAAA8AAAAAAABAVEAI
AFQAAP8FAAFFAAAA/QAKAFMAAQAPACsAAAB+AgoAUwACABgAQNPjQP0ACgBTAAMAFQBeAAAA/QAK
AFMABAAPAJEAAAD9AAoAUwAFABUAwgAAAAYAGwBUAAAADwAAAAAAAIBUQAgAVQAA/wUAAUUAAAD9
AAoAVAABAA8AKwAAAH4CCgBUAAIAGABA0+NA/QAKAFQAAwAVAF8AAAD9AAoAVAAEAA8AmwAAAP0A
CgBUAAUADwDRAAAABgAbAFUAAAAPAAAAAAAAwFRACABWAAD/BQABRQAAAP0ACgBVAAEADwArAAAA
fgIKAFUAAgAYAEDT40D9AAoAVQADABUAYAAAAP0ACgBVAAQADwCcAAAA/QAKAFUABQAVANIAAAAG
ABsAVgAAAA8AAAAAAAAAVUAIAFcAAP8FAAFFAAAA/QAKAFYAAQAPACsAAAB+AgoAVgACABgAQNPj
QP0ACgBWAAMAFQBhAAAA/QAKAFYABAAPAJwAAAD9AAoAVgAFAA8A0gAAAAYAGwBXAAAADwAAAAAA
AEBVQAgAWAAA/wUAAUUAAAD9AAoAVwABAA8AKwAAAH4CCgBXAAIAGABA0+NA/QAKAFcAAwAVAGIA
AAD9AAoAVwAEAA8AjAAAAAYAGwBYAAAADwAAAAAAAIBVQAgAWQAA/wUAAUUAAAD9AAoAWAABAA8A
KwAAAH4CCgBYAAIAGABA0+NA/QAKAFgAAwAVAGMAAAD9AAoAWAAEAA8AnQAAAP0ACgBYAAUADwDC
AAAABgAbAFkAAAAPAAAAAAAAwFVACABaAAD/BQABRQAAAP0ACgBZAAEADwArAAAAfgIKAFkAAgAY
AEDT40D9AAoAWQADABUAZAAAAP0ACgBZAAQADwCRAAAA/QAKAFkABQAPAMIAAAAGABsAWgAAAA8A
AAAAAAAAVkAIADMAAP8FAAFFAAAA/QAKAFoAAQAPACsAAAB+AgoAWgACABgAQNPjQP0ACgBaAAMA
FQBlAAAA/QAKAFoABAAPAJ4AAAB+AgoAWwAAAA8AAEBWQP0ACgBbAAEADwBmAAAAfgIKAFsAAgAX
AIDT40D9AAoAWwADABUAZwAAAP0ACgBbAAQADwCfAAAA/QAKAFsABQAPAMIAAAB+AgoAXAAAAA8A
AIBWQP0ACgBcAAEADwCiAAAAfgIKAFwAAgAXAEDU40D9AAoAXAADABUAowAAAP0ACgBcAAQADwBw
AAAA/QAKAFwABQAPANMAAAB+AgoAXQAAAA8AAMBWQP0ACgBdAAEADwCkAAAA/QAKAF0AAwAVAKcA
AAD9AAoAXQAEABsA2wAAAP0ACgBdAAUADwDuAAAAfgIKAF4AAAAPAAAAV0D9AAoAXgABAA8ApQAA
AP0ACgBeAAMAFQCoAAAAAQIGAF4ABAAfAP0ACgBeAAUADwDvAAAAfgIKAF8AAAAPAABAV0D9AAoA
XwABAA8ApAAAAP0ACgBfAAMAHQCmAAAA/QAKAF8ABAAPAHAAAAD9AAoAXwAFAA8AuAAAAH4CCgBg
AAAADwAAgFdA/QAKAGAAAQAPAKkAAAD9AAoAYAADABUAqgAAAP0ACgBgAAQAFQDXAAAA/QAKAGAA
BQAVANgAAADXAEQAaw4AAGwCZQBlAFcAZQB8AGUAZQBlAGUAZQBlAGUAZQBlAGUAZQBlAGUAZQBl
AGUAZQBXAGUAZQBXAFQAVABGAEIARgAIAhAAYQAAAAYA/QIAAAAAAAEPAAgCEABiAAAABgD+AQAA
AAAAAQ8ACAIQAGMAAAAGAP4BAAAAAAABDwAIAhAAZAAAAAYA/wAAAAAAAAEPAAgCEABnAAAABgD/
AAAAAAAAAQ8ACAIQAGkAAAAGAP4BAAAAAAABDwAIAhAAagAAAAYA/gEAAAAAAAEPAAgCEABrAAAA
BgD8AwAAAAAAAQ8ACAIQAGwAAAAGAPwDAAAAAAABDwB+AgoAYQAAAA8AAMBXQP0ACgBhAAEADwCp
AAAA/QAKAGEAAwAcAKsAAAD9AAoAYQAEABUArAAAAP0ACgBhAAUAGwDmAAAAfgIKAGIAAAAPAAAA
WED9AAoAYgABAA8AqQAAAP0ACgBiAAMAFQCtAAAA/QAKAGIABAAVANQAAAD9AAoAYgAFAA8AwgAA
AH4CCgBjAAAADwAAQFhA/QAKAGMAAQAPAK4AAAD9AAoAYwADABUArwAAAP0ACgBjAAQADwBoAAAA
/QAKAGMABQAVANUAAAB+AgoAZAAAAA8AAIBYQP0ACgBkAAEADwCuAAAA/QAKAGQAAwAVALAAAAD9
AAoAZAAEABUA1gAAAP0ACgBkAAUADwDcAAAA/QAKAGcAAQAgAN0AAAB+AgoAaQAAAA8AAMBYQP0A
CgBpAAEADwDhAAAA/QAKAGkAAwAVAN4AAAD9AAoAaQAEAA8A3wAAAP0ACgBpAAUAFQDgAAAAfgIK
AGoAAAAPAAAAWUD9AAoAagABAA8A4gAAAP0ACgBqAAMADwDjAAAA/QAKAGoABAAPAOQAAAD9AAoA
agAFABUA6gAAAH4CCgBrAAAADwAAQFlA/QAKAGsAAQAPAOIAAAD9AAoAawADAA8A5QAAAP0ACgBr
AAQADwDkAAAA/QAKAGsABQAVAOsAAAB+AgoAbAAAAA8AAIBZQP0ACgBsAAEADwDnAAAA/QAKAGwA
AwAPAOgAAAD9AAoAbAAEAA8A5AAAAP0ACgBsAAUAFQDpAAAA1wAWAPICAACgAEYARgBGAEYADgBG
AEYARgA+AhIAtgYAAAEAQAAAAAAAAAAAAAAAHQAPAAMiAAUAAAABACIAIgAFBe8ABgAFADcAAAAK
AAAACQgQAAAGEAATIM0HycAAAAYDAAALAhAAAAAAAAAAAAAAAAAAZqoAAA0AAgABAAwAAgBkAA8A
AgABABEAAgAAABAACAD8qfHSTWJQP18AAgABACoAAgAAACsAAgAAAIIAAgABAIAACAAAAAAAAAAA
ACUCBAAAAP8AgQACAMEEFAAAABUAAACDAAIAAACEAAIAAAChACIAAAD/AAEAAQABAAQAAAUFBQAA
AAAAAOA/AAAAAAAA4D8BAFUAAgAIAAACDgAAAAAAAAAAAAAAAAAAAD4CEgC2AAAAAABAAAAAAAAA
AAAAAAAdAA8AAwAAAAAAAAEAAAAAAAAA7wAGAAUANwAAAAoAAAAJCBAAAAYQABMgzQfJwAAABgMA
AAsCEAAAAAAAAAAAAAAAAABtqwAADQACAAEADAACAGQADwACAAEAEQACAAAAEAAIAPyp8dJNYlA/
XwACAAEAKgACAAAAKwACAAAAggACAAEAgAAIAAAAAAAAAAAAJQIEAAAA/wCBAAIAwQQUAAAAFQAA
AIMAAgAAAIQAAgAAAKEAIgAAAP8AAQABAAEABAAAAAAAAAAAAAAA4D8AAAAAAADgPwEAVQACAAgA
AAIOAAAAAAAAAAAAAAAAAAAAPgISALYAAAAAAEAAAAAAAAAAAAAAAB0ADwADAAAAAAAAAQAAAAAA
AADvAAYABQA3AAAACgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/v8AAAYAAgAAAAAAAAAAAAAAAAAAAAAAAQAAAOCF
n/L5T2gQq5EIACsns9kwAAAAoAAAAAcAAAABAAAAQAAAAAQAAABIAAAACAAAAFgAAAASAAAAaAAA
AAwAAACAAAAADQAAAIwAAAATAAAAmAAAAAIAAADkBAAAHgAAAAgAAABlYWxsZGF2AB4AAAAIAAAA
ZWFsbGRhdgAeAAAAEAAAAE1pY3Jvc29mdCBFeGNlbABAAAAAgPn50o7aywFAAAAAAFocaSs7zAED
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAP7/AAAGAAIAAAAAAAAAAAAAAAAAAAAAAAEAAAAC1c3VnC4bEJOX
CAArLPmuMAAAAOAAAAAJAAAAAQAAAFAAAAAPAAAAWAAAABcAAABsAAAACwAAAHQAAAAQAAAAfAAA
ABMAAACEAAAAFgAAAIwAAAANAAAAlAAAAAwAAAC9AAAAAgAAAOQEAAAeAAAADAAAAEVyaWNzc29u
AAAAAAMAAAAPJwsACwAAAAAAAAALAAAAAAAAAAsAAAAAAAAACwAAAAAAAAAeEAAAAwAAAAcAAABT
aGVldDEABwAAAFNoZWV0MgAHAAAAU2hlZXQzAAwQAAACAAAAHgAAAAsAAABXb3Jrc2hlZXRzAAMA
AAADAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAABAAAAAgAAAAMAAAAEAAAABQAAAAYAAAAHAAAACAAAAAkAAAAKAAAACwAAAAwA
AAANAAAADgAAAA8AAAAQAAAAEQAAABIAAAATAAAAFAAAABUAAAAWAAAAFwAAABgAAAAZAAAAGgAA
ABsAAAAcAAAAHQAAAB4AAAAfAAAAIAAAACEAAAAiAAAAIwAAACQAAAAlAAAAJgAAACcAAAAoAAAA
KQAAACoAAAArAAAALAAAAC0AAAAuAAAALwAAADAAAAAxAAAAMgAAADMAAAA0AAAANQAAADYAAAA3
AAAAOAAAADkAAAA6AAAAOwAAADwAAAA9AAAAPgAAAD8AAABAAAAAQQAAAEIAAABDAAAARAAAAEUA
AABGAAAARwAAAEgAAABJAAAASgAAAEsAAABMAAAATQAAAE4AAABPAAAAUAAAAFEAAABSAAAAUwAA
AFQAAABVAAAA/v///1cAAABYAAAAWQAAAFoAAABbAAAAXAAAAF0AAAD+////XwAAAGAAAABhAAAA
YgAAAGMAAABkAAAAZQAAAP7////9/////v//////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
/////////////1IAbwBvAHQAIABFAG4AdAByAHkAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAWAAUB//////////8CAAAAIAgCAAAAAADAAAAAAAAARgAAAAAAAAAA
AAAAAAAAAAAAAAAA/v///wAAAAAAAAAAVwBvAHIAawBiAG8AbwBrAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABIAAgH///////////////8AAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAvKsAAAAAAAAFAFMAdQBtAG0AYQByAHkASQBu
AGYAbwByAG0AYQB0AGkAbwBuAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAKAACAQEAAAADAAAA
/////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFYAAAAAEAAAAAAAAAUARABv
AGMAdQBtAGUAbgB0AFMAdQBtAG0AYQByAHkASQBuAGYAbwByAG0AYQB0AGkAbwBuAAAAAAAAAAAA
AAA4AAIB////////////////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAXgAA
AAAQAAAAAAAA

--_002_60C093A41B5E45409A19D42CF7786DFD52212CB37AEUSAACMS0703e_--

From hongyu.lihongyu@huawei.com  Tue Jul  5 18:31:03 2011
Return-Path: <hongyu.lihongyu@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 4BCF221F88EF; Tue,  5 Jul 2011 18:31:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id McLvwWnMYdhi; Tue,  5 Jul 2011 18:31:02 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 7E79621F88EC; Tue,  5 Jul 2011 18:31:02 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LNW000CQ1JNCF@szxga05-in.huawei.com>; Wed, 06 Jul 2011 09:30:59 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LNW00ER21JLOC@szxga05-in.huawei.com>; Wed, 06 Jul 2011 09:30:59 +0800 (CST)
Received: from 172.24.2.119 (EHLO szxeml208-edg.china.huawei.com) ([172.24.2.119])	by szxrg01-dlp.huawei.com (MOS 4.1.9-GA FastPath queued) with ESMTP id ACH30691; Wed, 06 Jul 2011 09:30:55 +0800 (CST)
Received: from SZXEML406-HUB.china.huawei.com (10.82.67.93) by szxeml208-edg.china.huawei.com (172.24.2.60) with Microsoft SMTP Server (TLS) id 14.1.270.1; Wed, 06 Jul 2011 09:30:51 +0800
Received: from SZXEML524-MBX.china.huawei.com ([169.254.4.58]) by szxeml406-hub.china.huawei.com ([10.82.67.93]) with mapi id 14.01.0270.001; Wed, 06 Jul 2011 09:30:49 +0800
Date: Wed, 06 Jul 2011 01:30:49 +0000
From: "Lihongyu(Hongyu)" <hongyu.lihongyu@huawei.com>
Subject: RE: GEN-ART review for draft-li-pwe3-ms-pw-pon-03
In-reply-to: <AE31510960917D478171C79369B660FA0E0325329B@MX06A.corp.emc.com>
X-Originating-IP: [10.70.40.71]
To: "kathleen.moriarty@emc.com" <kathleen.moriarty@emc.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-li-pwe3-ms-pw-pon.all@tools.ietf.org" <draft-li-pwe3-ms-pw-pon.all@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>,  Matthew Bocci <matthew.bocci@alcatel-lucent.com>
Message-id: <6EB34CB5D82C4645B826C56144826EA908DC02F0@szxeml524-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Accept-Language: en-US, zh-CN
Thread-topic: GEN-ART review for draft-li-pwe3-ms-pw-pon-03
Thread-index: Acw0y1h5B+aMJLm8RXy6PuQpHJ/2KAGsGS1w
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <AE31510960917D478171C79369B660FA0E0325329B@MX06A.corp.emc.com>
X-Mailman-Approved-At: Wed, 06 Jul 2011 08:09:44 -0700
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "Robin Zheng\(Ruobin\)" <zhengruobin@huawei.com>, 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: Wed, 06 Jul 2011 01:31:03 -0000

Hi Kathleen and Matthew,

Thank you for your review and comment. I have updated the draft according to most of your comments.




-----Original Message-----
From: kathleen.moriarty@emc.com [mailto:kathleen.moriarty@emc.com] 
Sent: Monday, June 27, 2011 9:09 PM
To: gen-art@ietf.org; draft-li-pwe3-ms-pw-pon.all@tools.ietf.org; ietf@ietf.org
Cc: Lihongyu(Hongyu); Robin Zheng(Ruobin); adrian.farrel@huawei.com
Subject: GEN-ART review for draft-li-pwe3-ms-pw-pon-03 

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please 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 introduction.  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 hongyu.lihongyu@huawei.com  Tue Jul  5 18:31:17 2011
Return-Path: <hongyu.lihongyu@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 1DBCF21F86EC; Tue,  5 Jul 2011 18:31:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=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 ifEXvghlERDs; Tue,  5 Jul 2011 18:31:16 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 830F821F86D5; Tue,  5 Jul 2011 18:31:16 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LNW004411K3IY@szxga03-in.huawei.com>; Wed, 06 Jul 2011 09:31:15 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LNW0095T1JYJS@szxga03-in.huawei.com>; Wed, 06 Jul 2011 09:31:15 +0800 (CST)
Received: from 172.24.2.119 (EHLO szxeml208-edg.china.huawei.com) ([172.24.2.119])	by szxrg01-dlp.huawei.com (MOS 4.1.9-GA FastPath queued) with ESMTP id ACH30713; Wed, 06 Jul 2011 09:31:14 +0800 (CST)
Received: from SZXEML403-HUB.china.huawei.com (10.82.67.35) by szxeml208-edg.china.huawei.com (172.24.2.60) with Microsoft SMTP Server (TLS) id 14.1.270.1; Wed, 06 Jul 2011 09:31:11 +0800
Received: from SZXEML524-MBX.china.huawei.com ([169.254.4.58]) by szxeml403-hub.china.huawei.com ([169.254.173.75]) with mapi id 14.01.0270.001; Wed, 06 Jul 2011 09:31:08 +0800
Date: Wed, 06 Jul 2011 01:31:08 +0000
From: "Lihongyu(Hongyu)" <hongyu.lihongyu@huawei.com>
Subject: Recall: GEN-ART review for draft-li-pwe3-ms-pw-pon-03
X-Originating-IP: [10.70.40.71]
To: "kathleen.moriarty@emc.com" <kathleen.moriarty@emc.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-li-pwe3-ms-pw-pon.all@tools.ietf.org" <draft-li-pwe3-ms-pw-pon.all@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>,  Matthew Bocci <matthew.bocci@alcatel-lucent.com>
Message-id: <6EB34CB5D82C4645B826C56144826EA908DC02F6@szxeml524-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Accept-Language: en-US, zh-CN
Thread-topic: GEN-ART review for draft-li-pwe3-ms-pw-pon-03
Thread-index: Acw7fGEzB+aMJLm8RXy6PuQpHJ/2KA==
X-CallingTelephoneNumber: IPM.Note
X-VoiceMessageDuration: 1
X-FaxNumberOfPages: 0
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Wed, 06 Jul 2011 08:09:44 -0700
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "Robin Zheng\(Ruobin\)" <zhengruobin@huawei.com>, 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: Wed, 06 Jul 2011 01:31:17 -0000

Lihongyu(Hongyu) would like to recall the message, "GEN-ART review for draft-li-pwe3-ms-pw-pon-03 ".

From randy@psg.com  Tue Jul  5 18:39:18 2011
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC69421F87F0; Tue,  5 Jul 2011 18:39:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.573
X-Spam-Level: 
X-Spam-Status: No, score=-2.573 tagged_above=-999 required=5 tests=[AWL=0.026,  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 BUog4cb+UM9t; Tue,  5 Jul 2011 18:39:18 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 5524321F87EA; Tue,  5 Jul 2011 18:39:18 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76 (FreeBSD)) (envelope-from <randy@psg.com>) id 1QeH52-0004Fu-Gf; Wed, 06 Jul 2011 01:39:08 +0000
Date: Wed, 06 Jul 2011 10:39:07 +0900
Message-ID: <m2liwcb32c.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Martin Rex <mrex@sap.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
In-Reply-To: <201107060054.p660sTMl017973@fs4113.wdf.sap.corp>
References: <20110703111047.GB2304@Space.Net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Mailman-Approved-At: Wed, 06 Jul 2011 08:09:44 -0700
Cc: v6ops@ietf.org, ietf@ietf.org, Gert Doering <gert@space.net>, moore@network-heretics.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2011 01:39:18 -0000

> The pain point is really the unnecessarily aggressive "kill what we
> don't like" move-to-historic action.

if we killed everything i do not like, there would be lot fewer rfcs. :)

what people are saying is kill it because it is broken, bad, and does a
dis-service to ipv6.

randy

From hongyu.lihongyu@huawei.com  Tue Jul  5 18:46:21 2011
Return-Path: <hongyu.lihongyu@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 6539521F8618; Tue,  5 Jul 2011 18:46:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.599
X-Spam-Level: 
X-Spam-Status: No, score=-5.599 tagged_above=-999 required=5 tests=[AWL=1.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 TXAbe4BiK6y3; Tue,  5 Jul 2011 18:46:19 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 00B4021F85E8; Tue,  5 Jul 2011 18:46:19 -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 <0LNW00BXD29529@szxga04-in.huawei.com>; Wed, 06 Jul 2011 09:46:18 +0800 (CST)
Received: from szxrg01-dlp.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 <0LNW00AO7295OG@szxga04-in.huawei.com>; Wed, 06 Jul 2011 09:46:17 +0800 (CST)
Received: from 172.24.2.119 (EHLO szxeml203-edg.china.huawei.com) ([172.24.2.119])	by szxrg01-dlp.huawei.com (MOS 4.1.9-GA FastPath queued) with ESMTP id ACH31702; Wed, 06 Jul 2011 09:46:17 +0800 (CST)
Received: from SZXEML404-HUB.china.huawei.com (10.82.67.59) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.270.1; Wed, 06 Jul 2011 09:46:13 +0800
Received: from SZXEML524-MBX.china.huawei.com ([169.254.4.58]) by szxeml404-hub.china.huawei.com ([fe80::75b7:3db9:fedc:a56d%13]) with mapi id 14.01.0270.001; Wed, 06 Jul 2011 09:46:14 +0800
Date: Wed, 06 Jul 2011 01:46:15 +0000
From: "Lihongyu(Hongyu)" <hongyu.lihongyu@huawei.com>
Subject: RE: GEN-ART review for draft-li-pwe3-ms-pw-pon-03
In-reply-to: <AE31510960917D478171C79369B660FA0E0325329B@MX06A.corp.emc.com>
X-Originating-IP: [10.70.40.71]
To: "kathleen.moriarty@emc.com" <kathleen.moriarty@emc.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-li-pwe3-ms-pw-pon.all@tools.ietf.org" <draft-li-pwe3-ms-pw-pon.all@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.com>, Matthew Bocci <matthew.bocci@alcatel-lucent.com>
Message-id: <6EB34CB5D82C4645B826C56144826EA908DC032E@szxeml524-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_JsxrnbhQr02eVzP7U72ZpQ)"
Content-language: zh-CN
Accept-Language: en-US, zh-CN
Thread-topic: GEN-ART review for draft-li-pwe3-ms-pw-pon-03
Thread-index: Acw0y1h5B+aMJLm8RXy6PuQpHJ/2KAGsiUMQ
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <AE31510960917D478171C79369B660FA0E0325329B@MX06A.corp.emc.com>
X-Mailman-Approved-At: Wed, 06 Jul 2011 08:09:44 -0700
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "Robin Zheng\(Ruobin\)" <zhengruobin@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: Wed, 06 Jul 2011 01:46:21 -0000

--Boundary_(ID_JsxrnbhQr02eVzP7U72ZpQ)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Hi Kathleen and Matthew,

Thank you for your review and comments. I have updated the draft according to most of your comments. I don't think it is right to talk about VCCV or complicated OAM mechanism in current draft. Probably there could be a new draft talking about this in the future. As for details about configuration parameters via OMCI, ITU-T is the right and better place to define and reference. ITU-T G.988 has all the details.

To all,

Besides, I made another two modification.
a) Modify all GPON to G-PON, according latest ITU-T G.987
b) Add XG-PON support. From MPLS PW or IETF point of view, XG-PON is exactly the same as G-PON, even though they have XGEM. In current draft, all "G-PON" related terminology could be simply add a "X" prefix and apply to XG-PON system directly. So, we would not need another draft for XG-PON.

Cheers,
Hongyu


-----Original Message-----
From: kathleen.moriarty@emc.com [mailto:kathleen.moriarty@emc.com] 
Sent: Monday, June 27, 2011 9:09 PM
To: gen-art@ietf.org; draft-li-pwe3-ms-pw-pon.all@tools.ietf.org; ietf@ietf.org
Cc: Lihongyu(Hongyu); Robin Zheng(Ruobin); adrian.farrel@huawei.com
Subject: GEN-ART review for draft-li-pwe3-ms-pw-pon-03 

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please 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 introduction.  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."






--Boundary_(ID_JsxrnbhQr02eVzP7U72ZpQ)
Content-type: text/plain; name=draft-li-pwe3-ms-pw-pon-04.txt
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=draft-li-pwe3-ms-pw-pon-04.txt;
 size=25823; creation-date="Wed, 06 Jul 2011 01:33:40 GMT";
 modification-date="Wed, 06 Jul 2011 01:33:41 GMT"
Content-description: draft-li-pwe3-ms-pw-pon-04.txt




pwe3 Working Group                                                 H. Li
Internet-Draft                                                  R. Zheng
Intended status: Informational                       Huawei Technologies
Expires: January 7, 2012                                       A. Farrel
                                                      Old Dog Consulting
                                                            July 6, 2011


          Multisegment Pseudowires in Passive Optical Networks
                       draft-li-pwe3-ms-pw-pon-04

Abstract

   This document describes the application of MPLS multi-segment
   pseudowires (MS-PWs) in a dual-technology environment comprising a
   Passive Optical Network (PON) and an MPLS Packet Switched Network
   (PSN).

   PON technology may be used in mobile backhaul networks to support the
   end segments closest to the aggregation devices.  In these cases,
   there may be a very large number of Pseudowire (PW) Terminating
   Provider Edge nodes (T-PEs).  The MPLS control plane could be used to
   provision these end segments, but support for the necessary protocols
   would complicate the management of the T-PEs and would significantly
   increase their expense.  Alternatively, static, or management plane,
   configuration could be used to configure the end segments, but the
   very large number of such segments in a PON places a very heavy
   burden on the network manager.

   This document describes how to set up the end segment of an end-to-
   end MPLS PW over a Gigabit-capable Passive Optical Network (G-PON) or
   10 Gigabit-capable Passive Optical Network (XG-PON) using the G-PON
   and XG-PON management protocol, Optical Network Termination
   Management and Control Interface (OMCI).  This simplifies and speeds
   up PW provisioning compared with manual configuration.

   This document also shows how a MS-PW may be constructed from an end
   segment supported over a PON, and switched to one or more segments
   supported over an MPLS PSN.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-



Li, et al.               Expires January 7, 2012                [Page 1]

Internet-Draft                  MS-PW-PON                      July 2011


   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 7, 2012.

Copyright Notice

   Copyright (c) 2011 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.




























Li, et al.               Expires January 7, 2012                [Page 2]

Internet-Draft                  MS-PW-PON                      July 2011


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Terminology for G-PON/XG-PON . . . . . . . . . . . . . . . . .  6
   3.  Multi-Segment Pseudowire over PON Network Reference Model  . .  7
   4.  Label Provisioning for Pseudowires over PON  . . . . . . . . . 10
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 10
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     7.1.  Normative References . . . . . . . . . . . . . . . . . . . 11
     7.2.  Informative References . . . . . . . . . . . . . . . . . . 12
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12







































Li, et al.               Expires January 7, 2012                [Page 3]

Internet-Draft                  MS-PW-PON                      July 2011


1.  Introduction

   The use of PWs in Packet Switched Networks (PSNs) is defined in
   [RFC3985].  This architecture is extended in [RFC5659] for multi-
   segment pseudowires (MS-PWs) satisfying the requirements in
   [RFC5254].  More detail on MS-PWs is provided in [RFC6073].

   A MS-PW is a useful technology for certain applications where there
   is an aggregation of paths toward a common point in the network, e.g.
   mobile backhaul; the segments can be aggregated within tunnels
   between PW switching points thus improving scalability and reducing
   the number of control plane adjacencies where a control plane is
   used.

   Segments of a MS-PW in a PSN can be setup using manual provisioning
   (static PWs) or using a dynamic control plane such as the Label
   Distribution Protocol (LDP)[RFC5036] [RFC4447].

   In many scenarios in access and metro networks, Passive Optical
   Network (PON) provides longer distance, higher bandwidth with better
   economy than other technologies like point-to-point Ethernet or
   Digital Subscriber Line (DSL).  Mobile backhaul with PON is already
   being deployed.

   Figure A depicts the physical infrastructure of an Optical
   Distribution Network (ODN).

                        |                                  |
                        |<--Optical Distribution Network-->|
                        |                                  |
                        |   branch               main      |
                  +-----+   fibers               fiber
   Base     ------|     |     |                    |
   Stations ------| ONU |\    |                    |
            ------|     |  \  V                    |
                  +-----+    \                     |
                               \  +----------+     |
                  +-----+        \|          |     |       +-----+
   Base     ------|     |         | Optical  |     V       |     |
   Stations ------| ONU |---------| Splitter |-------------| OLT |
            ------|     |        /|          |             |     |
                  +-----+      /  +----------+             +-----+
                             /
                  +-----+  /
   Base     ------|     |/
   Stations ------| ONU |
            ------|     |
                  +-----+



Li, et al.               Expires January 7, 2012                [Page 4]

Internet-Draft                  MS-PW-PON                      July 2011


                 Figure A: Typical PON System Architecture

   In a PON, the Optical Network Unit (ONU) and Optical Line Termination
   (OLT) are adjacent nodes connected by an Optical Distribution Network
   (ODN), which consists of optical fibers and optical splitters in a
   tree topology.  The link between each ONU and OLT is simulated as a
   point-to-point link, and there is no path redundancy between them.
   The OLT resides in the central office, while ONUs reside in customer
   premises.  ONUs are deployed in huge numbers and so they are cost
   sensitive.  More information about ODNs can be found in [G.984.1].

   In a mobile backhaul network, many 2G and 3G base stations still use
   legacy interfaces like TDM and ATM.  Therefore, these native services
   must be carried across the PON before they can be carried over the
   PSN using PWs.  This document describes how MS-PWs can be constructed
   with end segments that operate over the PON and are switched to
   further segments operated over the PSN.  In this case, the base
   stations are connected by access circuits (ACs) to the ONUs which act
   as Terminating Provider Edge nodes (T-PEs).  The OLT is a Switching
   Provider Edge (S-PE).  This model is shown in Figure B.

   Routing protocols and dynamic label distribution protocols like LDP
   would significantly increase the ONUs' cost and complexity as they
   place requirements on both hardware and software.  Besides coding and
   maintenance of these new protocols, a much more powerful CPU and more
   memory are also necessary for them to run smoothly.

   As there is no redundant path between each ONU and the OLT, routing
   and path selection are not necessary in the PON.  Therefore, static
   provision of PWs labels between ONUs and the OLT is simple, and is
   preferred because it can greatly reduce the cost of an ONU that acts
   as a T-PE.  However, use of a Network Management System (NMS) to
   provision PWs in a PON would require the network manager to configure
   each ONU, and to configure the OLT once for each PW.  Since there may
   be very many ONUs (and hence very many PWs) in a PON, this requires a
   large amount of operational effort.  Additionally, there is an issue
   that the configuration of each PW at the OLT and ONU might be
   inconsistent since these nodes are configured separately. .

   [G.988] defines the G-PON/XG-PON management protocol called the ONT
   Management and Control Interface (OMCI).  OMCI is an implementation
   requirement for all G-PON/XG-PON systems.  If OMCI is used to
   configure PWs on an ONU, no upgrade to an ONU's hardware is required
   and the extension to the OMCI implementation is negligible.  This
   provides a way of reducing the cost and complexity of provisioning
   PWs in a G-PON/XG-PON.

   This document shows how the two technologies (PON and PSN) can be



Li, et al.               Expires January 7, 2012                [Page 5]

Internet-Draft                  MS-PW-PON                      July 2011


   combined to provide an end-to-end multi-segment MPLS PW.  The MPLS
   PWs are also carried over the PON in MPLS LSP tunnels.  There is an
   MPLS LSP tunnel each direction between each ONU and the OLT in a one-
   to-one relationship with the underlying G-PON/XG-PON channel.  The
   OLT and ONU perform penultimate hop popping (PHP) [RFC3031] on this
   single-hop LSP so no labels are used on the wire for the MPLS LSP
   tunnel.  There is no change to the operation of MPLS PWs, and MPLS
   packets are carried by the G-PON link layer according to ITU-T
   [G.984.3amd1] or XG-PON link layer according to ITU-T [G.987.3].


2.  Terminology for G-PON/XG-PON

   We defined the following terms derived from [G.987]:

   o  Gigabit-capable Passive Optical Network (G-PON).  A variant of the
      Passive Optical Network (PON) access technology supporting
      transmission rates in excess of 1Gbps and based on the ITU-T
      G.984.x series of Recommendations [G.984].

   o  G-PON Encapsulation Method (GEM).  A data frame transport scheme
      used in G-PON systems that is connection-oriented and that
      supports fragmentation of the user data frames into variable sized
      transmission fragments.

   o  GEM Port.  An abstraction of the G-PON adaptation layer
      representing a logical connection associated with a specific
      client packet flow between the OLT and the ONU.

   o  10-gigabit-capable passive optical network (XG-PON): A PON system
      supporting nominal transmission rates on the order of 10 Gbit/s in
      at least one direction, and implementing the suite of protocols
      specified in the ITU-T G.987.x series Recommendations.

   o  XG-PON encapsulation method (XGEM): A data frame transport scheme
      used in XG PON systems that is connection-oriented and that
      supports fragmentation of user data frames into variable sized
      transmission fragments.

   o  XGEM port: An abstraction in the XGTC service adaptation sublayer
      representing a logical connection associated with a specific
      client packet flow.

   o  Optical Distribution network (ODN).  In the PON context, a tree of
      optical fibers in the access network, supplemented with power or
      wavelength splitters, filters, or other passive optical devices.





Li, et al.               Expires January 7, 2012                [Page 6]

Internet-Draft                  MS-PW-PON                      July 2011


   o  Optical Line Termination (OLT).  A device that terminates the
      common (root) endpoint of an ODN, implements a PON protocol, such
      as that defined by ITU-T G.984 series, and adapts PON PDUs for
      uplink communications over the provider service interface.  The
      OLT provides management and maintenance functions for the
      subtended ODN and ONUs.  In this document, the OLT is a network
      element with multiple PON ports and uplinks that provide switching
      capability to the PSN.

   o  Optical Network Termination (ONT).  A single subscriber device
      that terminates any one of the distributed (leaf) endpoints of an
      ODN, implements a PON protocol, and adapts PON PDUs to subscriber
      service interfaces.  An ONT is a special case of an ONU.

   o  Optical Network Unit (ONU).  A generic term denoting a device that
      terminates any one of the distributed (leaf) endpoints of an ODN,
      implements a PON protocol, and adapts PON PDUs to subscriber
      service interfaces.  In some contexts, an ONU implies a multiple
      subscriber device.  In this document, an ONU is a Provider Edge
      (PE) node with one or more ACs that map to the service interfaces.
      The ONU acts as a T-PE.

   o  ONT Management and Control Interface (OMCI).  The management and
      control channel between OLT and ONT in PON.  The OMCI protocol
      runs between the OLT Controller and the ONT Controller across a
      GEM connection that is established at ONT initialization.  The
      OMCI protocol is asymmetric: the Controller in the OLT is the
      master and the one in the ONT is the slave.  A single OLT
      Controller using multiple instances of the protocol over separate
      control channels may control multiple ONTs.  The OMCI protocol is
      used to manage the ONT in areas of configuration, fault
      management, performance and security.

   o  Passive Optical Network (PON).  An OLT connected using an ODN to
      one or more ONUs or ONTs.


3.  Multi-Segment Pseudowire over PON Network Reference Model

   [RFC5659] provides several pseudowire emulation edge-to-edge (PWE3)
   reference architectures for the multi-segment case.  These are
   general models extended from [RFC3985] to enable point-to-point
   pseudowires through multiple PSN tunnels.

   A G-PON/XGPON consists of an OLT, an ODN and multiple ONUs.  The ODN
   is actually a fiber tree that provides physical connections between
   the OLT and the ONUs.  G-PON/XG-PON has its own physical layer and
   link layer.  A GEM/XGEM Port is a logical point-to-point connection



Li, et al.               Expires January 7, 2012                [Page 7]

Internet-Draft                  MS-PW-PON                      July 2011


   between the OLT and each ONU over GPON Transmission Convergence (GTC)
   layer/XG-PON transmission convergence (XGTC) layer.  There can be
   more than one GEM/XGEM port between the OLT and an individual ONU.
   Each GEM/XGEM port can be assigned different QoS and bandwidth.

   Figure B shows how the MS-PW architecture is applied to a network
   comprising a PON and a PSN.  The Terminating PE1 (TPE1) is an ONU and
   the Switching PE1 (SPE1) is an OLT.  One or more PWs runs between the
   ONU and the remote end system (TPE2) to provide service emulation
   between CEs (CE1 and CE2).

   In each of the PON and PSN, the PW segments are carried in PSN
   tunnels.  In the PSN, the tunnel is established and operated as
   normal for PWs (see [RFC3985]).  In the PON, the tunnel used is a
   single-hop MPLS LSP tunnel so that the OLT and ONU are label edge
   routers.  The OLT and ONU make use of PHP on the MPLS LSP tunnel and,
   since this is a single hop LSP (there are no MPLS-capable nodes
   between the OLT and ONU) this means that there is no MPLS
   encapsulation for the MPLS LSP tunnel on the wire (that is, no label
   or shim header is used).  This results in the on-wire encapsulations
   shown in Figure C.

          Native  |<------Multi-Segment Pseudowire------>|  Native
          Service |       GEM/XGEM                       |  Service
           (AC)   |     |<--Port-->|                     |   (AC)
             |    |     |          |                     |     |
             |    |     |   PSN    |         PSN         |     |
             |    |     |<-Tunnel->|     |<-Tunnel->|    |     |
             |    V     V          V     V          V    V     |
             |    +----+           +-----+          +----+     |
      +----+ |    |TPE1|===========|S-PE1|==========|TPE2|     | +----+
      |    |------|..... PW.Seg't1....X....PW.Seg't3.....|-------|    |
      | CE1| |    |    |           |     |          |    |     | |CE2 |
      |    |------|..... PW.Seg't2....X....PW.Seg't4.....|-------|    |
      +----+ |    |    |===========|     |==========|    |     | +----+
   Base    ^      +----+           +-----+          +----+       ^
   Station |   Provider Edge 1        ^        Provider Edge 2   |
           |       ONU                |                          |
           |                  PW switching point                 |
           |                         OLT                         |
           |                                                     |
           |<------------------ Emulated Service --------------->|


             Figure B: MS-PW over PON Network Reference Model






Li, et al.               Expires January 7, 2012                [Page 8]

Internet-Draft                  MS-PW-PON                      July 2011


   Base   ----AC-- TPE1--PW over PON--SPE1--PW over PSN--TPE2--AC------
   Station
                          ----------        ----------
           --------      |Packetized|      |Packetized|        --------
          |Native  |     |Native    |      |Native    |       |Native  |
          |Service |     |Service   |      |Service   |       |Service |
           --------      |----------|      |----------|        --------
                         |Control   |      |Control   |
                         |Word      |      |Word      |
                         |----------|      |----------|
                         |PW Label  |      |PW Label  |
                         |----------|      |----------|
                         |GEM/XGEM  |      |MPLS      |
                         |----------|      |Tunnel    |
                         |GPON/XGPON|      |Label     |
                         |-Phy      |      |          |
                          ----------       |----------|
                                           |Link Layer|
                                           |----------|
                                           |Phy       |
                                            ----------

             Figure C: On-Wire Data Encapsulations for MS-PWs

   It should be noted that all PW segments are of the same technology,
   which is packet encapsulated.

   The use of the PW label enables multiple PWs to multiplexed over a
   single GEM/XGEM port within the MPLS LSP tunnel.  This enables the
   traffic for multiple base stations to be kept separate, and allows
   different services and separate ACs for a single base station to be
   supported.  Furthermore, the multiple ACs at an ONU can belong to
   different native services.

   At the same time, each ONU can support more than one GEM/XGEM port
   (each supporting a single MPLS LSP tunnel) connecting it to the OLT.
   This allows greater bandwidth and so more PWs.  It may also be used
   to provide a simple way to aggregate PWs intended to be routed across
   different PSN tunnels in the core network, or even across different
   core networks.

   At present, Ethernet over GEM/XGEM is the dominant encapsulation in
   G-PON/XG-PON.  For fast deployment of MPLS over G-PON/XG-PON, putting
   MPLS PWs over Ethernet over GEM/XGEM is an alternative way of
   transporting MPLS PWs over G-PON/XG-PON with existing hardware.






Li, et al.               Expires January 7, 2012                [Page 9]

Internet-Draft                  MS-PW-PON                      July 2011


4.  Label Provisioning for Pseudowires over PON

   For a MS-PW with a segment running over a PON, where the OLT acts as
   a S-PE and the ONU as a T-PE, PW provisioning can be performed
   through static configuration, e.g., from an NMS.  However, in this
   model, each ONU has to be configured as each PW is set up.  The huge
   number of ONUs (and PWs) makes this method quite forbidding.

   The labor of provisioning static labels at the ONUs for PWs can be
   significantly reduced by using a management protocol over PON.  This
   approach keeps the ONU simple by not requiring the implementation of
   a new dynamic control protocol.

   The usual management protocol in a G-PON/XG-PON system used to manage
   and control ONUs is OMCI.  It is used to perform all G-PON/XG-PON
   physical layer and data GTC/XGTC layer configuration on ONUs.  Per
   [G.984.4amd2] and [G.988], OMCI can also be used to set up PWs and
   the MPLS LSP Tunnels from ONUs to OLT.  When using OMCI to provision
   PWs in a G-PON/XG-PON, the network manager sends configuration
   information to the OLT only.  The OLT will select suitable PW labels
   and send all PW and MPLS LSP tunnel parameters to the ONUs through
   OMCI.  The AC can be identified in the OMCI signaling so that the
   network manager does not need to configure the PWs at each ONU.

   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.


5.  IANA Considerations

   This document makes no request for IANA action.


6.  Security Considerations

   G-PON/XG-PON has its own security mechanism to guarantee each ONU is
   isolated on the G-PON/XG-PON link layer.  Other security issues are
   unchanged from those applying as standard to PWs and MS-PWs.  Please
   refer to the referenced architectures and protocol specifications for
   further details.


7.  References







Li, et al.               Expires January 7, 2012               [Page 10]

Internet-Draft                  MS-PW-PON                      July 2011


7.1.  Normative References

   [G.984.1]  ITU-T, "Gigabit-capable passive optical networks (GPON):
              General characteristics", March 2008,
              <http://www.itu.int/rec/T-REC-G.984.1-200803-I>.

   [G.984.3amd1]
              ITU-T, "Gigabit-capable Passive Optical Networks (G-PON):
              Transmission convergence layer specification",
              February 2009,
              <http://www.itu.int/rec/T-REC-G.984.3-200902-I!Amd1>.

   [G.987]    "10-Gigabit-capable passive optical network (XG-PON)
              systems: Definitions, abbreviations, and acronyms",
              October 2010,
              <http://www.itu.int/rec/T-REC-G.987-201010-I>.

   [G.987.3]  "10-Gigabit-capable passive optical networks (XG-PON):
              Transmission convergence (TC) specifications",
              October 2010,
              <http://www.itu.int/rec/T-REC-G.987.3-201010-P>.

   [G.988]    ITU-T, "ONU management and control interface (OMCI)
              specification", 2010.

   [RFC3031]  "Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
              Label Switching Architecture", RFC 3031, January 2001.".

   [RFC3985]  Bryant, S. and P. Pate, "Pseudo Wire Emulation Edge-to-
              Edge (PWE3) Architecture", March 2005.

   [RFC4447]  "Martini, L., Rosen, E., El-Aawar, N., Smith, T., and G.
              Heron, "Pseudowire Setup and Maintenance Using the Label
              Distribution Protocol (LDP)", RFC 4447, April 2006.".

   [RFC5036]  "Andersson, L., Minei, I., and B. Thomas, "LDP
              Specification", RFC 5036, October 2007.".

   [RFC5254]  Bitar, N., Bocci, M., and L. Martini, "Requirements for
              Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3)",
              October 2008.

   [RFC5659]  Bocci, M. and S. Bryant, "An Architecture for Multi-
              Segment Pseudowire Emulation Edge-to-Edge", October 2009.







Li, et al.               Expires January 7, 2012               [Page 11]

Internet-Draft                  MS-PW-PON                      July 2011


7.2.  Informative References

   [G.984.4amd2]
              ITU-T, "Gigabit-capable passive optical networks (G-PON):
              ONT management and control interface specification",
              November 2009,
              <http://www.itu.int/rec/T-REC-G.984.4-200911-I!Amd2>.

   [RFC6073]  Martini, L., Metz, C., Nadeau, T., Bocci, M., and M.
              Aissaoui , "Segmented Pseudowire", January 2011.


Authors' Addresses

   Hongyu Li
   Huawei Technologies
   Huawei Industrial Base
   Shenzhen
   China

   Email: hongyu.lihongyu@huawei.com


   Ruobin Zheng
   Huawei Technologies
   Huawei Industrial Base
   Shenzhen
   China

   Email: robin@huawei.com


   Adrian Farrel
   Old Dog Consulting


   Email: adrian@olddog.co.uk














Li, et al.               Expires January 7, 2012               [Page 12]


--Boundary_(ID_JsxrnbhQr02eVzP7U72ZpQ)--

From alessandro.dalessandro@telecomitalia.it  Wed Jul  6 01:16:28 2011
Return-Path: <alessandro.dalessandro@telecomitalia.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 BEF9521F841D; Wed,  6 Jul 2011 01:16:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level: 
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EZi9vevlktyY; Wed,  6 Jul 2011 01:16:28 -0700 (PDT)
Received: from GRFEDG701RM001.telecomitalia.it (grfedg701rm001.telecomitalia.it [217.169.121.20]) by ietfa.amsl.com (Postfix) with ESMTP id CFE4221F84D5; Wed,  6 Jul 2011 01:16:13 -0700 (PDT)
Received: from grfhub702rm001.griffon.local (10.19.3.9) by GRFEDG701RM001.telecomitalia.it (10.173.88.20) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 6 Jul 2011 10:16:10 +0200
Received: from GRFMBX702RM001.griffon.local ([10.19.3.20]) by grfhub702rm001.griffon.local ([10.19.9.235]) with mapi; Wed, 6 Jul 2011 10:16:10 +0200
From: D'Alessandro Alessandro Gerardo <alessandro.dalessandro@telecomitalia.it>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Wed, 6 Jul 2011 10:16:09 +0200
Subject: R: [mpls] Last Call: <draft-ietf-mpls-tp-identifiers-06.txt> (MPLS-TP	Identifiers) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-tp-identifiers-06.txt> (MPLS-TP	Identifiers) to Proposed Standard
Thread-Index: Acw1F+fy2cc2fqAsQjWUdW71y7nF9QGmM/rQ
Message-ID: <A1F769BC58A8B146B2EEA818EAE052A2096B4DAB82@GRFMBX702RM001.griffon.local>
References: <20110627221611.11293.46784.idtracker@ietfa.amsl.com>
In-Reply-To: <20110627221611.11293.46784.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: it-IT
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, 06 Jul 2011 08:09:43 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2011 08:16:28 -0000

Dear all,
I have the following comments:

Sect 7: " A maintenance point is either a Maintenance
Entity Group End-point (MEP) or a Maintenance Entity Group
Intermediate Point (MIP). Maintenance points are uniquely associated
with a MEG."
>This is true for MEP. MIP, as currently defined, are not uniquely associat=
ed with a MEG.

Sec 7.4 " At a cross-connect point, in order to automatically generate MIP_=
IDs
for MPLS-TP, we simply use the IF_IDs of the two interfaces which are
cross-connected"
> the above given definition refers to "intermediate node". It should be ex=
tended to cover also the case of "end nodes" because MIPs could be located =
in such nodes when per-interface MEPs model is applied (e.g. draft-ietf-mpl=
s-tp-oam-framework and Yoshinori's contributions)
>a reference to sect 4, where IF_ID are defined, should be added

Best regards,
Alessandro
------------------------------------------------------------------
Telecom Italia
Alessandro D'Alessandro
Transport Innovation
Via Reiss Romoli, 274 - 10148 Torino
phone:  +39 011 228 5887
mobile: +39 335 766 9607
fax: +39 06 418 639 07


-----Messaggio originale-----
Da: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] Per conto di The I=
ESG
Inviato: marted=EC 28 giugno 2011 00:16
A: IETF-Announce
Cc: mpls@ietf.org
Oggetto: [mpls] Last Call: <draft-ietf-mpls-tp-identifiers-06.txt> (MPLS-TP=
 Identifiers) to Proposed Standard


The IESG has received a request from the Multiprotocol Label Switching WG
(mpls) to consider the following document:
- 'MPLS-TP Identifiers'
  <draft-ietf-mpls-tp-identifiers-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-07-11. Exceptionally, comments may be sent to ie=
sg@ietf.org instead. In either case, please retain the beginning of the Sub=
ject line to allow automated sorting.

Abstract

   This document specifies an initial set of identifiers to be used in
   the Transport Profile of Multiprotocol Label Switching (MPLS-TP).
   The MPLS-TP requirements (RFC 5654) require that the elements and
   objects in an MPLS-TP environment are able to be configured and
   managed without a control plane.  In such an environment many
   conventions for defining identifiers are possible.  This document
   defines identifiers for MPLS-TP management and OAM functions suitable
   to IP/MPLS conventions.

   This document is a product of a joint Internet Engineering Task Force
   (IETF) / International Telecommunication Union Telecommunication
   Standardization Sector (ITU-T) effort to include an MPLS Transport
   Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge
   (PWE3) architectures to support the capabilities and functionalities
   of a packet transport network as defined by the ITU-T.


The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-identifiers/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-identifiers/


No IPR declarations have been submitted directly on this I-D.


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, Thanks.


From david.i.allan@ericsson.com  Wed Jul  6 06:58:06 2011
Return-Path: <david.i.allan@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 C6CCE21F85D9; Wed,  6 Jul 2011 06:58:06 -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 iss-LtO1Aq2z; Wed,  6 Jul 2011 06:58:05 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by ietfa.amsl.com (Postfix) with ESMTP id BE68221F85E1; Wed,  6 Jul 2011 06:58:05 -0700 (PDT)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p66Dw49P012490; Wed, 6 Jul 2011 08:58:05 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.253]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Wed, 6 Jul 2011 09:57:57 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: Rui Costa <RCosta@ptinovacao.pt>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
Date: Wed, 6 Jul 2011 09:57:57 -0400
Subject: RE: [mpls] Last Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication for	MPLS	Transport	Profile) to Proposed Standard
Thread-Topic: [mpls] Last Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication for	MPLS	Transport	Profile) to Proposed Standard
Thread-Index: Acw3LJ0GTOqQfPcUQOGUhgK/1kXgjgDPfXWgAF5iQcA=
Message-ID: <60C093A41B5E45409A19D42CF7786DFD52212CB94E@EUSAACMS0703.eamcs.ericsson.se>
References: <20110630134642.1281.3095.idtracker@ietfa.amsl.com> <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B3D5@INOAVREX11.ptin.corpPT.com>
In-Reply-To: <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B3D5@INOAVREX11.ptin.corpPT.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: Wed, 06 Jul 2011 08:09:43 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2011 13:58:06 -0000

Hi Rui:

The comments were not ignored, the resolution of the Q10 comments as well a=
s those collected from the MPLS WG was presented at the last IETF. My sprea=
dsheet from which that report was generated and has been augmented to inclu=
de the BFD WG comments is available at http://www.pi.nu/~loa/cc-cv-rdi-Last=
-Call-Comments.xls

So you know...
Dave



-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Rui=
 Costa
Sent: Monday, July 04, 2011 3:03 PM
To: ietf@ietf.org; IETF-Announce
Cc: mpls@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proac=
tive Connectivity Verification, Continuity Check and Remote Defect indicati=
on for MPLS Transport Profile) to Proposed Standard

IMHO and for the record:=09

ITU-T comments regarding this draft haven't been discussed with ITU-T but w=
ere simply ignored. No LS describing these comments' resolution was sent.=09

Several service providers regarded this draft as not meeting their transpor=
t networks' needs.=09

[The v03 draft was published in Feb and went to WG LC.=09
The v04 draft addressing WG LC comments was published on the 28th June (sam=
e date as the proto write-up).=09
When was the WG LC launched, to verify LC comments resolution?]=09

Regards,=09
Rui


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of The=
 IESG
Sent: quinta-feira, 30 de Junho de 2011 14:47
To: IETF-Announce
Cc: mpls@ietf.org
Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive=
 Connectivity Verification, Continuity Check and Remote Defect indication f=
or MPLS Transport Profile) to Proposed Standard


The IESG has received a request from the Multiprotocol Label Switching WG
(mpls) to consider the following document:
- 'Proactive Connectivity Verification, Continuity Check and Remote
   Defect indication for MPLS Transport Profile'
  <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally, comments may be sent to ie=
sg@ietf.org instead. In either case, please retain the beginning of the Sub=
ject line to allow automated sorting.

Abstract

   Continuity Check, Proactive Connectivity Verification and Remote
   Defect Indication functionalities are required for MPLS-TP OAM.

   Continuity Check monitors the integrity of the continuity of the
   label switched path for any loss of continuity defect. Connectivity
   verification monitors the integrity of the routing of the label
   switched path between sink and source for any connectivity issues.
   Remote defect indication enables an End Point to report, to its
   associated End Point, a fault or defect condition that it detects on
   a pseudo wire, label switched path or Section.

   This document specifies methods for proactive continuity check,
   continuity verification, and remote defect indication for MPLS-TP
   label switched paths, pseudo wires and Sections using Bidirectional
   Forwarding Detection.


The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/


No IPR declarations have been submitted directly on this I-D.
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From fluffy@cisco.com  Wed Jul  6 08:38:48 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 489F821F8782 for <ietf@ietfa.amsl.com>; Wed,  6 Jul 2011 08:38:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.494
X-Spam-Level: 
X-Spam-Status: No, score=-110.494 tagged_above=-999 required=5 tests=[AWL=0.105, 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 HbY+tPSYCQWu for <ietf@ietfa.amsl.com>; Wed,  6 Jul 2011 08:38:47 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by ietfa.amsl.com (Postfix) with ESMTP id 9C08A21F8736 for <ietf@ietf.org>; Wed,  6 Jul 2011 08:38:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=139; q=dns/txt; s=iport; t=1309966727; x=1311176327; h=from:content-transfer-encoding:subject:date:message-id: to:mime-version; bh=E1m5+v7GBgmDd+pJ4xfjnCwyMWqR7tmYjHtUEzpzgqU=; b=HQhviGTHvlPLeIXz47E00O5sTnsSDPJu3IyrJ7B7kYL+Ngy8PEMof3U/ Q75FaTua4tCth1T5gy5xuO4A/XLGLAkEwyGgmN64Lg1udwnEAanart/mF WCXYwMmEKsfvoiqIIiiJNOfzW1zh5IzldLhlfT2r1DnMBbdf5dEh4UFXe Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAD+AFE6rRDoI/2dsb2JhbABTqAV3rHiBIp4nhjcEh0aKe4R6i2I
X-IronPort-AV: E=Sophos;i="4.65,487,1304294400"; d="scan'208";a="362404930"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by sj-iport-5.cisco.com with ESMTP; 06 Jul 2011 15:38:47 +0000
Received: from [192.168.4.100] (rcdn-fluffy-8712.cisco.com [10.99.9.19]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p66FciLN019817 for <ietf@ietf.org>; Wed, 6 Jul 2011 15:38:45 GMT
From: Cullen Jennings <fluffy@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: reading drafts on an ipad
Date: Wed, 6 Jul 2011 09:38:47 -0600
Message-Id: <061F84F2-E9A8-4A37-A506-7605391D837D@cisco.com>
To: IETF-Discussion list <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, 06 Jul 2011 15:38:48 -0000

Has anyone found a particularly good solution to reading drafts on an =
ipad? What about markup and notes on drafts?

Thanks, Cullen


From dave@cridland.net  Wed Jul  6 08:42:28 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 8C34221F87A4 for <ietf@ietfa.amsl.com>; Wed,  6 Jul 2011 08:42:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zJe56uYsvfQU for <ietf@ietfa.amsl.com>; Wed,  6 Jul 2011 08:42:25 -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 8960921F87A5 for <ietf@ietf.org>; Wed,  6 Jul 2011 08:42:24 -0700 (PDT)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id EECBF1168087; Wed,  6 Jul 2011 16:42:17 +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 jR4npt881-dF; Wed,  6 Jul 2011 16:42:16 +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 247541168067; Wed,  6 Jul 2011 16:42:16 +0100 (BST)
Subject: Re: reading drafts on an ipad
References: <061F84F2-E9A8-4A37-A506-7605391D837D@cisco.com>
In-Reply-To: <061F84F2-E9A8-4A37-A506-7605391D837D@cisco.com>
MIME-Version: 1.0
Message-Id: <19066.1309966936.138001@puncture>
Date: Wed, 06 Jul 2011 16:42:16 +0100
From: Dave Cridland <dave@cridland.net>
To: Cullen Jennings <fluffy@cisco.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, 06 Jul 2011 15:42:28 -0000

On Wed Jul  6 16:38:47 2011, Cullen Jennings wrote:
> 
> Has anyone found a particularly good solution to reading drafts on  
> an ipad? What about markup and notes on drafts?

Print them out using your ASR-33, then stick them on top.

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 loa@pi.nu  Wed Jul  6 08:44:13 2011
Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB56121F87B6; Wed,  6 Jul 2011 08:44:13 -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 bdFjL4ZKr2dA; Wed,  6 Jul 2011 08:44:12 -0700 (PDT)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by ietfa.amsl.com (Postfix) with ESMTP id 5D62321F860E; Wed,  6 Jul 2011 08:44:12 -0700 (PDT)
Received: from [192.168.1.64] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id C6249514044; Wed,  6 Jul 2011 17:44:09 +0200 (CEST)
Message-ID: <4E1482C8.6020701@pi.nu>
Date: Wed, 06 Jul 2011 17:44:08 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Rui Costa <RCosta@ptinovacao.pt>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>	(Proactive Connectivity Verification, Continuity Check and Remote Defect indication for MPLS	Transport	Profile) to Proposed Standard
References: <20110630134642.1281.3095.idtracker@ietfa.amsl.com> <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B3D5@INOAVREX11.ptin.corpPT.com>
In-Reply-To: <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B3D5@INOAVREX11.ptin.corpPT.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2011 15:44:13 -0000

All,

Since someone has commented about the process used for resolving 
questions on
draft-ietf-mpls-tp-cc-cv-rdi I am supplying some details below.

The history of draft-ietf-mpls-tp-cc-cv-rdi working group review
process is:

On February 3rd 2011 the working group last call was issued
on version -03

      This was copied to the the Ad Hoc Team List
      and liaised to SG15 also on February 3rd

      This working group last call ended om Feb 28


      On Feb 28 we also received a liaison with comments from SG15


The authors compiled a list of all comments received  as part the MPLS
working group last call; these  comments - and the intended resolution -
is included in the meeting minutes from the Prague meeting:


      http://www.ietf.org/proceedings/80/slides/mpls-9.pdf


  During the IETF meeting in Prague, we agreed with the BFD working
  group to do a separate working group last callfor the BFD working
  group

The (BFD) working group last call was started on March 30th and ran
for 13 days. The last call ended on April 11th.

  The authors have since worked hard to resolve comments, some
  issue has been brought to the working group mailing list for
  resolution.

  Version -04 of the document was published June 28th.

  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
  June 29th.

  The AD review resulted in a "New ID needed" due to mostly editorial
  comments. Version -05 was published on June 29 and the IETF last call
  started as soon as the new ID was avaialbe.

  The current list of Last Call Comments resoltion is also avaiable at:
  http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls

  The list of issues that the authors kept very carefully, shows without 
doubt
  that no comments been ignored.

  Loa
  mpls wg document shepherd

On 2011-07-05 00:02, Rui Costa wrote:
> IMHO and for the record:	
>
> ITU-T comments regarding this draft haven't been discussed with ITU-T but were simply ignored. No LS describing these comments' resolution was sent.	
>
> Several service providers regarded this draft as not meeting their transport networks' needs.	
>
> [The v03 draft was published in Feb and went to WG LC.	
> The v04 draft addressing WG LC comments was published on the 28th June (same date as the proto write-up).	
> When was the WG LC launched, to verify LC comments resolution?]	
>
> Regards,	
> Rui
>
>
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of The IESG
> Sent: quinta-feira, 30 de Junho de 2011 14:47
> To: IETF-Announce
> Cc: mpls@ietf.org
> Subject: [mpls] Last Call:<draft-ietf-mpls-tp-cc-cv-rdi-05.txt>  (Proactive Connectivity Verification, Continuity Check and Remote Defect indication for MPLS Transport Profile) to Proposed Standard
>
>
> The IESG has received a request from the Multiprotocol Label Switching WG
> (mpls) to consider the following document:
> - 'Proactive Connectivity Verification, Continuity Check and Remote
>     Defect indication for MPLS Transport Profile'
>    <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>     Continuity Check, Proactive Connectivity Verification and Remote
>     Defect Indication functionalities are required for MPLS-TP OAM.
>
>     Continuity Check monitors the integrity of the continuity of the
>     label switched path for any loss of continuity defect. Connectivity
>     verification monitors the integrity of the routing of the label
>     switched path between sink and source for any connectivity issues.
>     Remote defect indication enables an End Point to report, to its
>     associated End Point, a fault or defect condition that it detects on
>     a pseudo wire, label switched path or Section.
>
>     This document specifies methods for proactive continuity check,
>     continuity verification, and remote defect indication for MPLS-TP
>     label switched paths, pseudo wires and Sections using Bidirectional
>     Forwarding Detection.
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>
>
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

-- 


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

From klaas@cisco.com  Wed Jul  6 09:15:44 2011
Return-Path: <klaas@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 C269221F86C3 for <ietf@ietfa.amsl.com>; Wed,  6 Jul 2011 09:15:44 -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 NAwQbxR5Upms for <ietf@ietfa.amsl.com>; Wed,  6 Jul 2011 09:15:44 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id A21C721F8646 for <ietf@ietf.org>; Wed,  6 Jul 2011 09:15:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=klaas@cisco.com; l=522; q=dns/txt; s=iport; t=1309968943; x=1311178543; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=HI/uTT+Ui+xnkxMu8r1rvyDfJ4wvyP37wG3RNgx3PpU=; b=YYpEJ72/Q5Mv5KHC8NsbZZ85ot35TdhqXrZJd0r9lAEsu0OzExt2YB9C oSSfH1V9JZIQDRliIGZEcW+zqqh3S1cWcRY+6c697GHsVclOvu8/bPs0W EokFDjbnxbUr0ZCz3KnEkqOL6QJ3D74wKvaG8//UaB2OQvc75taKX+IWk 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAIACqJFE6Q/khM/2dsb2JhbABTmRmObHeuI54ghjcEkkGQPw
X-IronPort-AV: E=Sophos;i="4.65,487,1304294400"; d="scan'208";a="99962936"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 06 Jul 2011 16:15:38 +0000
Received: from macmini.wierenga.net (ams-kwiereng-8712.cisco.com [10.55.220.243]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p66GFc2J031191 for <ietf@ietf.org>; Wed, 6 Jul 2011 16:15:38 GMT
Message-ID: <4E148A29.5020609@cisco.com>
Date: Wed, 06 Jul 2011 18:15:37 +0200
From: Klaas Wierenga <klaas@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: reading drafts on an ipad
References: <061F84F2-E9A8-4A37-A506-7605391D837D@cisco.com>
In-Reply-To: <061F84F2-E9A8-4A37-A506-7605391D837D@cisco.com>
X-Enigmail-Version: 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: Wed, 06 Jul 2011 16:15:44 -0000

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

On 7/6/11 5:38 PM, Cullen Jennings wrote:
> 
> Has anyone found a particularly good solution to reading drafts on
> an ipad? What about markup and notes on drafts?

I use GoodReader

Klaas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4UiikACgkQH2Wy/p4XeFJkDwCgo2qFiFt6g9Ot6RX/kxvKfavg
7nEAn0HF4Ip2vixeWmffRkM7lr7xEqM3
=HvYc
-----END PGP SIGNATURE-----

From jhw@apple.com  Wed Jul  6 09:45:30 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 CB69521F889A; Wed,  6 Jul 2011 09:45:30 -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 57E-5WzZUABN; Wed,  6 Jul 2011 09:45:30 -0700 (PDT)
Received: from mail-out.apple.com (honeycrisp.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id 613B321F8896; Wed,  6 Jul 2011 09:45:30 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay12.apple.com ([17.128.113.53]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LNX004GL7TVRT91@mail-out.apple.com>; Wed, 06 Jul 2011 09:45:29 -0700 (PDT)
X-AuditID: 11807135-b7b76ae000001169-e2-4e1491a6233f
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 relay12.apple.com (Apple SCV relay) with SMTP id 39.73.04457.6A1941E4; Wed, 06 Jul 2011 09:47:35 -0700 (PDT)
Received: from 67-218-109-100.cust.layer42.net (67-218-109-100.cust.layer42.net [67.218.109.100]) by koseret.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LNX006PE7VPWL40@koseret.apple.com>; Wed, 06 Jul 2011 09:45:29 -0700 (PDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
From: james woodyatt <jhw@apple.com>
In-reply-to: <m2liwcb32c.wl%randy@psg.com>
Date: Wed, 06 Jul 2011 09:45:24 -0700
Message-id: <159599EA-8812-400C-A6CA-506996DB1EBF@apple.com>
References: <20110703111047.GB2304@Space.Net> <m2liwcb32c.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1244.3)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrJLMWRmVeSWpSXmKPExsUiON1OXXf5RBE/g3+NjBbPNs5nsTh9bC+z A5PHkiU/mQIYo7hsUlJzMstSi/TtErgydvV9ZCloYqs4ccGxgfEGSxcjJ4eEgInEvx1PmSFs MYkL99azdTFycQgJdDJJdM57zA6S4BUQlPgx+R5QAwcHs4C8xMHzsiBhZgEtie+PWlkg6jcx SezvWMsEkhAWMJP4sug0G4jNJqAi8e3yXbA4J1DDyV2rWEFsFgFVieaJ89khBoVKnOg8ywKx y0bizJPzYL1CAt4SLcuawY4TEZCTuHjiHSPEofISi1s+M05gFJiF5LxZCOfNQnLeAkbmVYyC Rak5iZWGRnqJBQU5qXrJ+bmbGEEB2FBouoPx0UL1Q4wCHIxKPLxdvSJ+QqyJZcWVuYcYJTiY lUR4JzkChXhTEiurUovy44tKc1KLDzFKc7AoifNWOXL5CQmkJ5akZqemFqQWwWSZODilGhjD buzY2Zr7U/SFSMytlTPmZU1NZfdvNmPhzPcI6ODQFHphseRsNEfBsbVNx4tXachKMC3nXJE4 r8d61oebzzXdCqJC2NZvUO7k3WCe+FvxaP7Pi/+SD6u1JU35vPrJi4aWgmO/2q76aLuZZ3ke thc9v7GrmalOwzhaiLm6Lezl8vZDlR+r1iqxFGckGmoxFxUnAgAKMV0PPAIAAA==
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: Wed, 06 Jul 2011 16:45:30 -0000

On Jul 5, 2011, at 6:39 PM, Randy Bush wrote:
> 
> what people are saying is kill it because it is broken, bad, and does a dis-service to ipv6.

Actually, I seem to have been the only person who proposed killing it-- the rest of you seem to have settled on merely looking at it crossly and hoping it will wither away in shame.

By that I mean, I wrote up and circulated an Internet Draft to specify a phase-out plan for RFC 3056 and RFC 3068.  I chose not to submit it when it was made clear to me that no such plan could be adopted as a working group item.

On a related note, I much prefer Keith Moore's proposal to reclassify RFC 3056 and RFC 3068 as Experimental.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From dhc2@dcrocker.net  Wed Jul  6 09:54:46 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 D418C21F863F for <ietf@ietfa.amsl.com>; Wed,  6 Jul 2011 09:54:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 EXtRMpHK7z8a for <ietf@ietfa.amsl.com>; Wed,  6 Jul 2011 09:54:46 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1D18721F8663 for <ietf@ietf.org>; Wed,  6 Jul 2011 09:54:46 -0700 (PDT)
Received: from [192.168.1.156] (adsl-67-124-149-98.dsl.pltn13.pacbell.net [67.124.149.98]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p66GseZ5003817 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Wed, 6 Jul 2011 09:54:45 -0700
Message-ID: <4E14934D.8030607@dcrocker.net>
Date: Wed, 06 Jul 2011 09:54:37 -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: reading drafts on an ipad
References: <061F84F2-E9A8-4A37-A506-7605391D837D@cisco.com>
In-Reply-To: <061F84F2-E9A8-4A37-A506-7605391D837D@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 06 Jul 2011 09:54:46 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2011 16:54:47 -0000

On 7/6/2011 8:38 AM, Cullen Jennings wrote:
> Has anyone found a particularly good solution to reading drafts on an ipad?
> What about markup and notes on drafts?


Text files are easily modified by any text editor.

What specific issues present a challenge for you on a tablet?

(I use an Android and haven't noticed problems reading or marking drafts on it,
so it really isn't obvious to me what you want to optimize.)

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From fluffy@cisco.com  Wed Jul  6 10:04:56 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 B1C8B21F87A8; Wed,  6 Jul 2011 10:04:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.511
X-Spam-Level: 
X-Spam-Status: No, score=-110.511 tagged_above=-999 required=5 tests=[AWL=0.088, 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 OjFrq6uJIpik; Wed,  6 Jul 2011 10:04:56 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by ietfa.amsl.com (Postfix) with ESMTP id 457BC21F8766; Wed,  6 Jul 2011 10:04:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=308; q=dns/txt; s=iport; t=1309971896; x=1311181496; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=5SzzMOFrmv8SVDN+aR1BeteHuaYDeI9yzNN/jO6Zhvg=; b=U7Ggjw5qCZE9XHNg8/4VxOyfTaqaNQfqPsKvQ/v6cPrImWVJFtBSoC7Z JrlU1deVGRt6KRMVE1irsDW//mfVffUObAckEMz8S75sg0yrmmGtDjjNK x47M48Ix1MHjCppYtYJgsBtZXaa59aGygeR2B1wW60+QKC9lnKCuzi29/ 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAF2VFE6rRDoH/2dsb2JhbABTqAV3iHqlN54ShjcEh0aKe4R6i2I
X-IronPort-AV: E=Sophos;i="4.65,488,1304294400"; d="scan'208";a="362488161"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-5.cisco.com with ESMTP; 06 Jul 2011 17:04:56 +0000
Received: from [192.168.4.100] (rcdn-fluffy-8712.cisco.com [10.99.9.19]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p66H4tsX007006; Wed, 6 Jul 2011 17:04:55 GMT
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
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <BLU0-SMTP801B5A24EB84B6151C06C2D8660@phx.gbl>
Date: Wed, 6 Jul 2011 11:04:57 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <B13E8E1A-0747-4F0E-BB68-41EE9CA4EC70@cisco.com>
References: <20110527203800.13071.15398.idtracker@ietfa.amsl.com> <BLU0-SMTP801B5A24EB84B6151C06C2D8660@phx.gbl>
To: Tom Taylor <tom111.taylor@bell.net>
X-Mailer: Apple Mail (2.1084)
Cc: pcn@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, 06 Jul 2011 17:04:56 -0000

On Jun 12, 2011, at 8:48 AM, Tom Taylor wrote:

> What I propose is that I submit the documents with the fixes that were =
carried out, and the IESG restart the Last Call process.=20

Tom, glad was caught this before this was an RFC. I think your proposal =
sounds like the right way to proceed.=20


From scott.brim@gmail.com  Wed Jul  6 10:07:11 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 E203621F87FC for <ietf@ietfa.amsl.com>; Wed,  6 Jul 2011 10:07:11 -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 eozhOTNi0lvq for <ietf@ietfa.amsl.com>; Wed,  6 Jul 2011 10:07:11 -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 7ECE621F866B for <ietf@ietf.org>; Wed,  6 Jul 2011 10:07:11 -0700 (PDT)
Received: by iwn39 with SMTP id 39so98917iwn.31 for <ietf@ietf.org>; Wed, 06 Jul 2011 10:07:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=uVjsn4l2Iq55PcOEAD0jzhd1nY+HWpVLuVQsv/EkTsk=; b=VaqWW3dmyXpr1BjeAX0i7zUV7dD+12zd2CsoNyiRHQemiGMRzyLdsgyJ3xxK43MZiw Fexeiz1dfHO+fca14504HkkXE9L6WGLC3RKnktPobdcuMYRN06FeHVz2zS1ogab+hnGX 2CDBUP/MJui3tC0hMpkH/r2mVg51fi6ey9ejo=
Received: by 10.231.24.193 with SMTP id w1mr8004201ibb.41.1309972031087; Wed, 06 Jul 2011 10:07:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.31.197 with HTTP; Wed, 6 Jul 2011 10:06:51 -0700 (PDT)
In-Reply-To: <4E14934D.8030607@dcrocker.net>
References: <061F84F2-E9A8-4A37-A506-7605391D837D@cisco.com> <4E14934D.8030607@dcrocker.net>
From: Scott Brim <scott.brim@gmail.com>
Date: Wed, 6 Jul 2011 13:06:51 -0400
Message-ID: <CAPv4CP_tO5Z0WRTGG2tfKxSt66-HnuwQC8bgo7K-dK3NdGC31g@mail.gmail.com>
Subject: Re: reading drafts on an ipad
To: dcrocker@bbiw.net
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2011 17:07:12 -0000

A few things apply, depending on how you fetch the drafts and what you
want to do.

- From some other machine, sync them into Dropbox and read and edit
them straight from Dropbox on the iPad using Plaintext (set its
directory to "/" which gives you all of the Dropbox directory,
otherwise it just looks in /plaintext)

- Instapaper - have a bookmark in your browser so you can save drafts
from the web to instapaper for offline reading.

- TexTastic is a syntax aware editor that even knows about XML and
DTDs and has a line of keys "commonly used in programming".

From dougb@dougbarton.us  Wed Jul  6 13:08:22 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 3563F21F8B4C for <ietf@ietfa.amsl.com>; Wed,  6 Jul 2011 13:08:22 -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 3Y6nXHyFfqTs for <ietf@ietfa.amsl.com>; Wed,  6 Jul 2011 13:08:21 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id D944421F8B17 for <ietf@ietf.org>; Wed,  6 Jul 2011 13:08:20 -0700 (PDT)
Received: (qmail 31371 invoked by uid 399); 6 Jul 2011 20:08:17 -0000
Received: from unknown (HELO 65-241-43-4.globalsuite.net) (dougb@dougbarton.us@65.241.43.4) by mail2.fluidhosting.com with ESMTPAM; 6 Jul 2011 20:08:17 -0000
X-Originating-IP: 65.241.43.4
X-Sender: dougb@dougbarton.us
Message-ID: <4E14C0AB.9080105@dougbarton.us>
Date: Wed, 06 Jul 2011 13:08:11 -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.18) Gecko/20110624 Thunderbird/3.1.11
MIME-Version: 1.0
To: james woodyatt <jhw@apple.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
References: <20110703111047.GB2304@Space.Net> <m2liwcb32c.wl%randy@psg.com> <159599EA-8812-400C-A6CA-506996DB1EBF@apple.com>
In-Reply-To: <159599EA-8812-400C-A6CA-506996DB1EBF@apple.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: 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: Wed, 06 Jul 2011 20:08:22 -0000

On 07/06/2011 09:45, james woodyatt wrote:
> Actually, I seem to have been the only person who proposed killing it-- the rest of you seem to have settled on merely looking at it crossly and hoping it will wither away in shame.

... as well it should. :)

Meanwhile I have stated several times that I'd like it to be gone, 
completely, yesterday. I was however willing to accept "historic" as a 
reasonable compromise.

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 mrex@sap.com  Wed Jul  6 13:14: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 0B05121F8B85; Wed,  6 Jul 2011 13:14:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.186
X-Spam-Level: 
X-Spam-Status: No, score=-10.186 tagged_above=-999 required=5 tests=[AWL=0.063, 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 GP6yOgGXqU6Q; Wed,  6 Jul 2011 13:14:46 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id DFA8021F8B82; Wed,  6 Jul 2011 13:14:45 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id p66KEcD8015293 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 6 Jul 2011 22:14:38 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201107062014.p66KEc4g024137@fs4113.wdf.sap.corp>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
To: dougb@dougbarton.us (Doug Barton)
Date: Wed, 6 Jul 2011 22:14:38 +0200 (MEST)
In-Reply-To: <4E14C0AB.9080105@dougbarton.us> from "Doug Barton" at Jul 6, 11 01:08:11 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
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, 06 Jul 2011 20:14:49 -0000

Doug Barton wrote:
> 
> Meanwhile I have stated several times that I'd like it to be gone, 
> completely, yesterday. I was however willing to accept "historic" as a 
> reasonable compromise.

"historic" as a compromise?  Between which two positions?
 
-Martin


From dougb@dougbarton.us  Wed Jul  6 13:18:48 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 EA30921F8BA2 for <ietf@ietfa.amsl.com>; Wed,  6 Jul 2011 13:18:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.562
X-Spam-Level: 
X-Spam-Status: No, score=-3.562 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 zt5A9EJfAbp8 for <ietf@ietfa.amsl.com>; Wed,  6 Jul 2011 13:18:44 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 6BC2121F8B85 for <ietf@ietf.org>; Wed,  6 Jul 2011 13:18:44 -0700 (PDT)
Received: (qmail 12132 invoked by uid 399); 6 Jul 2011 20:18:42 -0000
Received: from unknown (HELO 65-241-43-4.globalsuite.net) (dougb@dougbarton.us@65.241.43.4) by mail2.fluidhosting.com with ESMTPAM; 6 Jul 2011 20:18:42 -0000
X-Originating-IP: 65.241.43.4
X-Sender: dougb@dougbarton.us
Message-ID: <4E14C31E.4010603@dougbarton.us>
Date: Wed, 06 Jul 2011 13:18:38 -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.18) Gecko/20110624 Thunderbird/3.1.11
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
References: <201107062014.p66KEc4g024137@fs4113.wdf.sap.corp>
In-Reply-To: <201107062014.p66KEc4g024137@fs4113.wdf.sap.corp>
X-Enigmail-Version: 1.1.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Wed, 06 Jul 2011 20:18:48 -0000

On 07/06/2011 13:14, Martin Rex wrote:
> Doug Barton wrote:
>>
>> Meanwhile I have stated several times that I'd like it to be gone,
>> completely, yesterday. I was however willing to accept "historic" as a
>> reasonable compromise.
>
> "historic" as a compromise?  Between which two positions?

Nuking it from orbit, and erecting a statue in its honor?


:)

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 mrex@sap.com  Wed Jul  6 13:49:54 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 99D4521F8BBD; Wed,  6 Jul 2011 13:49:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.189
X-Spam-Level: 
X-Spam-Status: No, score=-10.189 tagged_above=-999 required=5 tests=[AWL=0.060, 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 peJ96uyRloII; Wed,  6 Jul 2011 13:49:53 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 927B821F8BB1; Wed,  6 Jul 2011 13:49:53 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id p66Knm35017687 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 6 Jul 2011 22:49:48 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201107062049.p66Knlfi026308@fs4113.wdf.sap.corp>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
To: dougb@dougbarton.us (Doug Barton)
Date: Wed, 6 Jul 2011 22:49:47 +0200 (MEST)
In-Reply-To: <4E14C31E.4010603@dougbarton.us> from "Doug Barton" at Jul 6, 11 01:18:38 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
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, 06 Jul 2011 20:49:54 -0000

Doug Barton wrote:
> 
> On 07/06/2011 13:14, Martin Rex wrote:
> >
> > Doug Barton wrote:
> > >
> > > I was however willing to accept "historic" as a reasonable compromise.
> >
> > "historic" as a compromise?  Between which two positions?
> 
> Nuking it from orbit, and erecting a statue in its honor?

Which to options that are actually available to the IESG?  I see

extremist-A:  nuke/kill 6to4 by moving 3056/3068 to historic

compromise:   move 3056/3068 off Standards Track,
              i.e. by reclassifying them as Experimental

blocked:      leave 3056/3068 at Proposed, publish only 6to4-advisory

extremist-B:  stick fingers in ears, sing la-la-la, pretend 6to4 is perfect


-Martin

From scott@kitterman.com  Wed Jul  6 13:57:52 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 E70E321F8A77 for <ietf@ietfa.amsl.com>; Wed,  6 Jul 2011 13:57:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sCdFTnvTJTWJ for <ietf@ietfa.amsl.com>; Wed,  6 Jul 2011 13:57:49 -0700 (PDT)
Received: from mailout00.controlledmail.com (mailout00.controlledmail.com [72.81.252.19]) by ietfa.amsl.com (Postfix) with ESMTP id A9F6E21F8A74 for <ietf@ietf.org>; Wed,  6 Jul 2011 13:57:49 -0700 (PDT)
Received: from mailout00.controlledmail.com (localhost [127.0.0.1]) by mailout00.controlledmail.com (Postfix) with ESMTP id B199538C101; Wed,  6 Jul 2011 16:57:48 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1309985869; bh=QPUb2L3LoQBXMDJbtbhp1ysI2si9b4t2VpEZxGufv1c=; h=From:To:Subject:Date:References:In-Reply-To:MIME-Version: Content-Type:Content-Transfer-Encoding:Message-Id; b=DV1RI5gADj+lm3+wRfUtdjy27s7Ozgw7SGlCw8Fth9gidJu5YFK4sHDzO+rJ1zYQv T6cwujvqNowe86SHjP0TBLnhdIIY95PzjZO0X4QG4tJV4uYLIDqErXAiHpjZBS5ehH sKNFXYrQikCnCCN/47SgKs/dNwxpJnhGnIxFIf2M=
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
Date: Wed, 6 Jul 2011 16:57:47 -0400
User-Agent: KMail/1.13.6 (Linux/2.6.38-8-generic-pae; KDE/4.6.2; i686; ; )
References: <201107062049.p66Knlfi026308@fs4113.wdf.sap.corp>
In-Reply-To: <201107062049.p66Knlfi026308@fs4113.wdf.sap.corp>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201107061657.47341.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, 06 Jul 2011 20:57:53 -0000

On Wednesday, July 06, 2011 04:49:47 PM Martin Rex wrote:
> Doug Barton wrote:
> > On 07/06/2011 13:14, Martin Rex wrote:
> > > Doug Barton wrote:
> > > > I was however willing to accept "historic" as a reasonable
> > > > compromise.
> > > 
> > > "historic" as a compromise?  Between which two positions?
> > 
> > Nuking it from orbit, and erecting a statue in its honor?
> 
> Which to options that are actually available to the IESG?  I see
> 
> extremist-A:  nuke/kill 6to4 by moving 3056/3068 to historic
> 
> compromise:   move 3056/3068 off Standards Track,
>               i.e. by reclassifying them as Experimental
> 
> blocked:      leave 3056/3068 at Proposed, publish only 6to4-advisory
> 
> extremist-B:  stick fingers in ears, sing la-la-la, pretend 6to4 is perfect

I think I've read this entire thread and I don't recall anyone advocating 
extremist-B.

Scott K

From mrex@sap.com  Wed Jul  6 14:40: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 3499821F8A9A for <ietf@ietfa.amsl.com>; Wed,  6 Jul 2011 14:40:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.192
X-Spam-Level: 
X-Spam-Status: No, score=-10.192 tagged_above=-999 required=5 tests=[AWL=0.057, 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 Q62+0xHsAH3X for <ietf@ietfa.amsl.com>; Wed,  6 Jul 2011 14:40:31 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 6585021F8862 for <ietf@ietf.org>; Wed,  6 Jul 2011 14:40:28 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id p66LeQxq021023 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 6 Jul 2011 23:40:26 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201107062140.p66LeQFL029228@fs4113.wdf.sap.corp>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
To: scott@kitterman.com (Scott Kitterman)
Date: Wed, 6 Jul 2011 23:40:26 +0200 (MEST)
In-Reply-To: <201107061657.47341.scott@kitterman.com> from "Scott Kitterman" at Jul 6, 11 04:57:47 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: Wed, 06 Jul 2011 21:40:33 -0000

Scott Kitterman wrote:
> 
> On Wednesday, July 06, 2011 04:49:47 PM Martin Rex wrote:
> > Doug Barton wrote:
> > > On 07/06/2011 13:14, Martin Rex wrote:
> > > > Doug Barton wrote:
> > > > > I was however willing to accept "historic" as a reasonable
> > > > > compromise.
> > > > 
> > > > "historic" as a compromise?  Between which two positions?
> > > 
> > > Nuking it from orbit, and erecting a statue in its honor?
> > 
> > Which to options that are actually available to the IESG?  I see
> > 
> > extremist-A:  nuke/kill 6to4 by moving 3056/3068 to historic
> > 
> > compromise:   move 3056/3068 off Standards Track,
> >               i.e. by reclassifying them as Experimental
> > 
> > blocked:      leave 3056/3068 at Proposed, publish only 6to4-advisory
> > 
> > extremist-B:  stick fingers in ears, sing la-la-la, pretend 6to4 is perfect
> 
> I think I've read this entire thread and I don't recall anyone advocating 
> extremist-B.

Neither do I.

The above just lists the entire spectrum of options for the IESG decision
after the IETF LC for the two documents (6to4-advisory, 6to4-to-historic)
had ended, and there was the unresolved procedural issue from IETF LC
against 6to4-to-historic based on the protocol action of
moving 3056,3068 to historic.

An option to undo the past is not available to IESG, such as travelling
back in time and preventing 3056 and 3068 from being developed.

-Martin

From gwz@net-zen.net  Wed Jul  6 19:36:28 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 2609D21F87E3 for <ietf@ietfa.amsl.com>; Wed,  6 Jul 2011 19:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id saFViLhL1l-f for <ietf@ietfa.amsl.com>; Wed,  6 Jul 2011 19:36:27 -0700 (PDT)
Received: from p3plsmtpa07-01.prod.phx3.secureserver.net (p3plsmtpa07-01.prod.phx3.secureserver.net [173.201.192.230]) by ietfa.amsl.com (Postfix) with SMTP id 4C91C21F87CA for <ietf@ietf.org>; Wed,  6 Jul 2011 19:36:27 -0700 (PDT)
Received: (qmail 22975 invoked from network); 7 Jul 2011 02:36:26 -0000
Received: from unknown (124.120.168.67) by p3plsmtpa07-01.prod.phx3.secureserver.net (173.201.192.230) with ESMTP; 07 Jul 2011 02:36:26 -0000
Message-ID: <4E151BA5.4070608@net-zen.net>
Date: Thu, 07 Jul 2011 09:36:21 +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.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: reading drafts on an ipad
References: <061F84F2-E9A8-4A37-A506-7605391D837D@cisco.com>
In-Reply-To: <061F84F2-E9A8-4A37-A506-7605391D837D@cisco.com>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/mixed; boundary="------------040904000901040805030802"
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, 07 Jul 2011 02:36:28 -0000

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

On 7/6/2011 10:38 PM, Cullen Jennings wrote:

> Has anyone found a particularly good solution to reading drafts on an ipad? What about markup and notes on drafts?

The iPad is a porn toy; get a real computer.

...

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


--------------040904000901040805030802--

From ynir@checkpoint.com  Thu Jul  7 01:31:46 2011
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 679C521F875F; Thu,  7 Jul 2011 01:31:46 -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 4VLDsroJUQVB; Thu,  7 Jul 2011 01:31:45 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id D25D521F874E; Thu,  7 Jul 2011 01:31:44 -0700 (PDT)
X-CheckPoint: {4E157CB0-9-1B221DC2-FFFF}
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id p678VX5Z026200;  Thu, 7 Jul 2011 11:31:33 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Thu, 7 Jul 2011 11:30:08 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "'mrex@sap.com'" <mrex@sap.com>, Doug Barton <dougb@dougbarton.us>
Date: Thu, 7 Jul 2011 11:30:06 +0300
Subject: RE: [v6ops] draft-ietf-v6ops-6to4-to-historic
Thread-Topic: [v6ops] draft-ietf-v6ops-6to4-to-historic
Thread-Index: Acw8HoFNI9mcKA6JSjSLaIL3Nj9C1wAYXRcA
Message-ID: <006FEB08D9C6444AB014105C9AEB133F01714C077305@il-ex01.ad.checkpoint.com>
References: <4E14C31E.4010603@dougbarton.us> from "Doug Barton" at Jul 6,	11 01:18:38 pm <201107062049.p66Knlfi026308@fs4113.wdf.sap.corp>
In-Reply-To: <201107062049.p66Knlfi026308@fs4113.wdf.sap.corp>
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: "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: Thu, 07 Jul 2011 08:31:46 -0000

Extremist-A should be to publish a "6to4 considered dangerous" draft with l=
ots of MUST NOT language.
=20

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Mar=
tin Rex
Sent: 06 July 2011 23:50
To: Doug Barton
Cc: v6ops@ietf.org; ietf@ietf.org
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic

Doug Barton wrote:
>=20
> On 07/06/2011 13:14, Martin Rex wrote:
> >
> > Doug Barton wrote:
> > >
> > > I was however willing to accept "historic" as a reasonable compromise=
.
> >
> > "historic" as a compromise?  Between which two positions?
>=20
> Nuking it from orbit, and erecting a statue in its honor?

Which to options that are actually available to the IESG?  I see

extremist-A:  nuke/kill 6to4 by moving 3056/3068 to historic

compromise:   move 3056/3068 off Standards Track,
              i.e. by reclassifying them as Experimental

blocked:      leave 3056/3068 at Proposed, publish only 6to4-advisory

extremist-B:  stick fingers in ears, sing la-la-la, pretend 6to4 is perfect


-Martin
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

Scanned by Check Point Total Security Gateway.

From nurit.sprecher@nsn.com  Thu Jul  7 02:59:25 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 40AD921F8699; Thu,  7 Jul 2011 02:59:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[AWL=5.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 cKMj8uREEE5u; Thu,  7 Jul 2011 02:59:24 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 0D26A21F85C2; Thu,  7 Jul 2011 02:59:23 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p679xJkI002144 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 7 Jul 2011 11:59:19 +0200
Received: from DEMUEXC048.nsn-intra.net ([10.159.32.94]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p679xC8i012016; Thu, 7 Jul 2011 11:59:18 +0200
Received: from DEMUEXC014.nsn-intra.net ([10.150.128.25]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 7 Jul 2011 11:59:13 +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: [mpls] R: Re: LastCall:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt>	(Proactive	Connectivity	Verification, Continuity Check and Remote Defect indicationfor	MPLS	Transport	Profile) to Proposed Standard
Date: Thu, 7 Jul 2011 11:59:12 +0200
Message-ID: <077E41CFFD002C4CAB7DFA4386A532640415A55F@DEMUEXC014.nsn-intra.net>
In-Reply-To: <14289796.745031309973638587.JavaMail.defaultUser@defaultHost>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] R: Re: LastCall:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt>	(Proactive	Connectivity	Verification, Continuity Check and Remote Defect indicationfor	MPLS	Transport	Profile) to Proposed Standard
Thread-Index: Acw8AvNmmGk+VU+zQLq6ipU76LivNgAf+uzg
References: <14289796.745031309973638587.JavaMail.defaultUser@defaultHost>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: <erminio.ottone_69@libero.it>, <RCosta@ptinovacao.pt>, <ietf@ietf.org>, "IETF-Announce" <ietf-announce@ietf.org>
X-OriginalArrivalTime: 07 Jul 2011 09:59:13.0322 (UTC) FILETIME=[864D90A0:01CC3C8C]
Cc: mpls@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jul 2011 09:59:25 -0000

Erminio,
I do not think the history is relevant for this specific discussion...=20
Also I find it inappropriate to give statements with no justifications
behind.=20
You say: "the solution in this draft is useless for many MPLS-TP
deployments.".  in order to seriously consider your comment, you have to
show why it is useless and which requirements are not satisfied.
Otherwise you cannot expect anyone to refer to your point.=20
Best regards,
Nurit

P.s. did you mean that the document is useless to available non-standard
deployments, e.g. T-MPLS?
=20

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
ext erminio.ottone_69@libero.it
Sent: Wednesday, July 06, 2011 8:34 PM
To: RCosta@ptinovacao.pt; ietf@ietf.org; IETF-Announce
Cc: mpls@ietf.org
Subject: [mpls] R: Re: LastCall: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
(Proactive Connectivity Verification,Continuity Check and Remote Defect
indicationfor MPLS Transport Profile) to Proposed Standard

The way this draft has been developed is a bit strange.

The poll for its adoption as a WG document was halted by the MPLS WG
chair=20
because "it is not possible to judge consensus":

http://www.ietf.org/mail-archive/web/mpls/current/msg04502.html

The lack of consensus was motivated by serious technical concerns raised
by=20
several transport experts during the poll.

Nevertheless the MPLS WG chair decided to adopt the draft as a WG
document:

http://www.ietf.org/mail-archive/web/mpls/current/msg04512.html

After several WG revisions and WG LCs, the technical issues have not
been=20
resolved.

>Several service providers regarded this draft as not meeting their
transport=20
networks' needs.=09

This is a true statement: the solution in this draft is useless for many
MPLS-
TP deployments.

>----Messaggio originale----
>Da: RCosta@ptinovacao.pt
>Data: 5-lug-2011 0.02
>A: "ietf@ietf.org"<ietf@ietf.org>,
"IETF-Announce"<ietf-announce@ietf.org>
>Cc: "mpls@ietf.org"<mpls@ietf.org>
>Ogg: Re: [mpls] Last Call:
&lt;draft-ietf-mpls-tp-cc-cv-rdi-05.txt&gt;=09
(Proactive	Connectivity	Verification, Continuity Check and
Remote Defect=20
indication for	MPLS	Transport	Profile) to Proposed Standard
>
>IMHO and for the record:=09
>
>ITU-T comments regarding this draft haven't been discussed with ITU-T
but=20
were simply ignored. No LS describing these comments' resolution was
sent.=09
>
>Several service providers regarded this draft as not meeting their
transport=20
networks' needs.=09
>
>[The v03 draft was published in Feb and went to WG LC.=09
>The v04 draft addressing WG LC comments was published on the 28th June
(same=20
date as the proto write-up).=09
>When was the WG LC launched, to verify LC comments resolution?]=09
>
>Regards,=09
>Rui
>
>
>-----Original Message-----
>From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
The=20
IESG
>Sent: quinta-feira, 30 de Junho de 2011 14:47
>To: IETF-Announce
>Cc: mpls@ietf.org
>Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
(Proactive=20
Connectivity Verification, Continuity Check and Remote Defect indication
for=20
MPLS Transport Profile) to Proposed Standard
>
>
>The IESG has received a request from the Multiprotocol Label Switching
WG
>(mpls) to consider the following document:
>- 'Proactive Connectivity Verification, Continuity Check and Remote
>   Defect indication for MPLS Transport Profile'
>  <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally, comments may
be
>sent to iesg@ietf.org instead. In either case, please retain the
>beginning of the Subject line to allow automated sorting.
>
>Abstract
>
>   Continuity Check, Proactive Connectivity Verification and Remote
>   Defect Indication functionalities are required for MPLS-TP OAM.
>
>   Continuity Check monitors the integrity of the continuity of the
>   label switched path for any loss of continuity defect. Connectivity
>   verification monitors the integrity of the routing of the label
>   switched path between sink and source for any connectivity issues.
>   Remote defect indication enables an End Point to report, to its
>   associated End Point, a fault or defect condition that it detects on
>   a pseudo wire, label switched path or Section.
>
>   This document specifies methods for proactive continuity check,
>   continuity verification, and remote defect indication for MPLS-TP
>   label switched paths, pseudo wires and Sections using Bidirectional
>   Forwarding Detection.
>
>
>The file can be obtained via
>http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>
>IESG discussion can be tracked via
>http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>
>
>No IPR declarations have been submitted directly on this I-D.
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls
>
>
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls
>


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From nurit.sprecher@nsn.com  Thu Jul  7 04:40:36 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 02A6E21F8811; Thu,  7 Jul 2011 04:40:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.439
X-Spam-Level: 
X-Spam-Status: No, score=-2.439 tagged_above=-999 required=5 tests=[AWL=4.160,  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 8Jbyy9dDmlJv; Thu,  7 Jul 2011 04:40:35 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id C239421F880C; Thu,  7 Jul 2011 04:40:34 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p67BeP16027363 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 7 Jul 2011 13:40:25 +0200
Received: from DEMUEXC047.nsn-intra.net ([10.159.32.93]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p67BeM2p004226; Thu, 7 Jul 2011 13:40:24 +0200
Received: from DEMUEXC014.nsn-intra.net ([10.150.128.25]) by DEMUEXC047.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 7 Jul 2011 13:40:24 +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: [mpls] R: Re: LastCall:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt>	(Proactive	Connectivity	Verification, Continuity Check and Remote Defect indicationfor	MPLS	Transport	Profile) to Proposed Standard
Date: Thu, 7 Jul 2011 13:40:22 +0200
Message-ID: <077E41CFFD002C4CAB7DFA4386A532640415A674@DEMUEXC014.nsn-intra.net>
In-Reply-To: <14289796.745031309973638587.JavaMail.defaultUser@defaultHost>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] R: Re: LastCall:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt>	(Proactive	Connectivity	Verification, Continuity Check and Remote Defect indicationfor	MPLS	Transport	Profile) to Proposed Standard
Thread-Index: Acw8AvNmmGk+VU+zQLq6ipU76LivNgAf+uzg
References: <14289796.745031309973638587.JavaMail.defaultUser@defaultHost>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: <erminio.ottone_69@libero.it>, <RCosta@ptinovacao.pt>, <ietf@ietf.org>, "IETF-Announce" <ietf-announce@ietf.org>
X-OriginalArrivalTime: 07 Jul 2011 11:40:24.0319 (UTC) FILETIME=[A8E630F0:01CC3C9A]
Cc: mpls@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jul 2011 11:40:36 -0000

Erminio,
I do not think the history is relevant for this specific discussion...=20
Also I find it inappropriate to give statements with no justifications
behind.=20
You say: "the solution in this draft is useless for many MPLS-TP
deployments.".  in order to seriously consider your comment, you have to
show why it is useless and which requirements are not satisfied.
Otherwise you cannot expect anyone to refer to your point.=20
Best regards,
Nurit

P.s. did you mean that the document is useless to available non-standard
deployments, e.g. T-MPLS?
=20

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
ext erminio.ottone_69@libero.it
Sent: Wednesday, July 06, 2011 8:34 PM
To: RCosta@ptinovacao.pt; ietf@ietf.org; IETF-Announce
Cc: mpls@ietf.org
Subject: [mpls] R: Re: LastCall: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
(Proactive Connectivity Verification,Continuity Check and Remote Defect
indicationfor MPLS Transport Profile) to Proposed Standard

The way this draft has been developed is a bit strange.

The poll for its adoption as a WG document was halted by the MPLS WG
chair=20
because "it is not possible to judge consensus":

http://www.ietf.org/mail-archive/web/mpls/current/msg04502.html

The lack of consensus was motivated by serious technical concerns raised
by=20
several transport experts during the poll.

Nevertheless the MPLS WG chair decided to adopt the draft as a WG
document:

http://www.ietf.org/mail-archive/web/mpls/current/msg04512.html

After several WG revisions and WG LCs, the technical issues have not
been=20
resolved.

>Several service providers regarded this draft as not meeting their
transport=20
networks' needs.=09

This is a true statement: the solution in this draft is useless for many
MPLS-
TP deployments.

>----Messaggio originale----
>Da: RCosta@ptinovacao.pt
>Data: 5-lug-2011 0.02
>A: "ietf@ietf.org"<ietf@ietf.org>,
"IETF-Announce"<ietf-announce@ietf.org>
>Cc: "mpls@ietf.org"<mpls@ietf.org>
>Ogg: Re: [mpls] Last Call:
&lt;draft-ietf-mpls-tp-cc-cv-rdi-05.txt&gt;=09
(Proactive	Connectivity	Verification, Continuity Check and
Remote Defect=20
indication for	MPLS	Transport	Profile) to Proposed Standard
>
>IMHO and for the record:=09
>
>ITU-T comments regarding this draft haven't been discussed with ITU-T
but=20
were simply ignored. No LS describing these comments' resolution was
sent.=09
>
>Several service providers regarded this draft as not meeting their
transport=20
networks' needs.=09
>
>[The v03 draft was published in Feb and went to WG LC.=09
>The v04 draft addressing WG LC comments was published on the 28th June
(same=20
date as the proto write-up).=09
>When was the WG LC launched, to verify LC comments resolution?]=09
>
>Regards,=09
>Rui
>
>
>-----Original Message-----
>From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
The=20
IESG
>Sent: quinta-feira, 30 de Junho de 2011 14:47
>To: IETF-Announce
>Cc: mpls@ietf.org
>Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
(Proactive=20
Connectivity Verification, Continuity Check and Remote Defect indication
for=20
MPLS Transport Profile) to Proposed Standard
>
>
>The IESG has received a request from the Multiprotocol Label Switching
WG
>(mpls) to consider the following document:
>- 'Proactive Connectivity Verification, Continuity Check and Remote
>   Defect indication for MPLS Transport Profile'
>  <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally, comments may
be
>sent to iesg@ietf.org instead. In either case, please retain the
>beginning of the Subject line to allow automated sorting.
>
>Abstract
>
>   Continuity Check, Proactive Connectivity Verification and Remote
>   Defect Indication functionalities are required for MPLS-TP OAM.
>
>   Continuity Check monitors the integrity of the continuity of the
>   label switched path for any loss of continuity defect. Connectivity
>   verification monitors the integrity of the routing of the label
>   switched path between sink and source for any connectivity issues.
>   Remote defect indication enables an End Point to report, to its
>   associated End Point, a fault or defect condition that it detects on
>   a pseudo wire, label switched path or Section.
>
>   This document specifies methods for proactive continuity check,
>   continuity verification, and remote defect indication for MPLS-TP
>   label switched paths, pseudo wires and Sections using Bidirectional
>   Forwarding Detection.
>
>
>The file can be obtained via
>http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>
>IESG discussion can be tracked via
>http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>
>
>No IPR declarations have been submitted directly on this I-D.
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls
>
>
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls
>


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From ogud@ogud.com  Thu Jul  7 06:26:28 2011
Return-Path: <ogud@ogud.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C0F021F85E7 for <ietf@ietfa.amsl.com>; Thu,  7 Jul 2011 06:26:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.444
X-Spam-Level: 
X-Spam-Status: No, score=-106.444 tagged_above=-999 required=5 tests=[AWL=0.155, 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 WOZUNgrRizJw for <ietf@ietfa.amsl.com>; Thu,  7 Jul 2011 06:26:28 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id F3C5921F85C7 for <ietf@ietf.org>; Thu,  7 Jul 2011 06:26:27 -0700 (PDT)
Received: from [IPv6:::1] (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id p67DQQ1M036939 for <ietf@ietf.org>; Thu, 7 Jul 2011 09:26:26 -0400 (EDT) (envelope-from ogud@ogud.com)
Message-ID: <4E15B400.7080803@ogud.com>
Date: Thu, 07 Jul 2011 09:26:24 -0400
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: extra room avail IETF hotel at IETF rate
References: <1309901531.1861.26.camel@d430>
In-Reply-To: <1309901531.1861.26.camel@d430>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jul 2011 13:26:28 -0000

I also have one I'm not going to use.

	Olafur


On 05/07/2011 5:32 PM, Geoff Mulligan wrote:
> I found that I have an extra reservation at the IETF rate
> ($229/night)for Sunday to Friday at the Hilton.
>
> If anyone is interested I can transfer the reservation.
>
> 	geoff
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
>
>


From dougb@dougbarton.us  Thu Jul  7 09:25:13 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 963C21F0C43 for <ietf@ietfa.amsl.com>; Thu,  7 Jul 2011 09:25:13 -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 7bJ60ocZFo2b for <ietf@ietfa.amsl.com>; Thu,  7 Jul 2011 09:25:12 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 9CCB61F0C3C for <ietf@ietf.org>; Thu,  7 Jul 2011 09:25:12 -0700 (PDT)
Received: (qmail 17055 invoked by uid 399); 7 Jul 2011 16:25:07 -0000
Received: from unknown (HELO 65-241-43-4.globalsuite.net) (dougb@dougbarton.us@65.241.43.4) by mail2.fluidhosting.com with ESMTPAM; 7 Jul 2011 16:25:07 -0000
X-Originating-IP: 65.241.43.4
X-Sender: dougb@dougbarton.us
Message-ID: <4E15DDDF.90909@dougbarton.us>
Date: Thu, 07 Jul 2011 09:25:03 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110706 Thunderbird/5.0
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
References: <4E14C31E.4010603@dougbarton.us> from "Doug Barton" at Jul 6, 11 01:18:38 pm <201107062049.p66Knlfi026308@fs4113.wdf.sap.corp> <006FEB08D9C6444AB014105C9AEB133F01714C077305@il-ex01.ad.checkpoint.com>
In-Reply-To: <006FEB08D9C6444AB014105C9AEB133F01714C077305@il-ex01.ad.checkpoint.com>
X-Enigmail-Version: 1.2pre
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Thu, 07 Jul 2011 16:25:13 -0000

... or to use Randy's language, "6to4 considered caterpillar snot," but
yes, that is what I was thinking that end of the spectrum looked like.


Doug


On 07/07/2011 01:30, Yoav Nir wrote:
> Extremist-A should be to publish a "6to4 considered dangerous" draft with lots of MUST NOT language.
>  
> 
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Martin Rex
> Sent: 06 July 2011 23:50
> To: Doug Barton
> Cc: v6ops@ietf.org; ietf@ietf.org
> Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
> 
> Doug Barton wrote:
>>
>> On 07/06/2011 13:14, Martin Rex wrote:
>>>
>>> Doug Barton wrote:
>>>>
>>>> I was however willing to accept "historic" as a reasonable compromise.
>>>
>>> "historic" as a compromise?  Between which two positions?
>>
>> Nuking it from orbit, and erecting a statue in its honor?
> 
> Which to options that are actually available to the IESG?  I see
> 
> extremist-A:  nuke/kill 6to4 by moving 3056/3068 to historic
> 
> compromise:   move 3056/3068 off Standards Track,
>               i.e. by reclassifying them as Experimental
> 
> blocked:      leave 3056/3068 at Proposed, publish only 6to4-advisory
> 
> extremist-B:  stick fingers in ears, sing la-la-la, pretend 6to4 is perfect
> 
> 
> -Martin
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
> Scanned by Check Point Total Security Gateway.



-- 

	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 erminio.ottone_69@libero.it  Wed Jul  6 10:26:32 2011
Return-Path: <erminio.ottone_69@libero.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 0511F21F8865; Wed,  6 Jul 2011 10:26:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level: 
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uCylgDjXPZiU; Wed,  6 Jul 2011 10:26:31 -0700 (PDT)
Received: from outrelay03.libero.it (outrelay03.libero.it [212.52.84.103]) by ietfa.amsl.com (Postfix) with ESMTP id B1CC521F85B9; Wed,  6 Jul 2011 10:26:30 -0700 (PDT)
X-CTCH-Spam: Unknown
X-CTCH-RefID: str=0001.0A0B020A.4E149AC0.019C,ss=1,re=0.000,fgs=0
X-libjamoibt: 1821
Received: from wmail39 (172.31.0.228) by outrelay03.libero.it (8.5.133) (authenticated as erminio.ottone_69@libero.it) id 4DE4FF1D02531A3D; Wed, 6 Jul 2011 19:26:24 +0200
Message-ID: <15271688.742501309973184714.JavaMail.defaultUser@defaultHost>
Date: Wed, 6 Jul 2011 19:26:24 +0200 (CEST)
From: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
To: <loa@pi.nu>, Rui Costa <RCosta@ptinovacao.pt>
Subject: R: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive Connectivity Verification, Continuity Check and Remote Defect indication for MPLS	Transport	Profile) to Proposed Standard
MIME-Version: 1.0
Content-Type: text/plain;charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-SenderIP: 79.31.158.220
X-Mailman-Approved-At: Thu, 07 Jul 2011 11:01:14 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2011 17:26:32 -0000

>  Version -04 of the document was published June 28th.
>
>  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
>  June 29th.
>

So when the WG LC to confirm the LC comment resolution has been launched?

The proto write-up says:

            It has also passed a working roup call to verify that LC comments 
were correctly with minor comments. 

It also says:

            The comments has been
            carefully discussed between the authors and people making the 
comments and
            has been resolved.

But it seems that some comments have not been discussed with the authors of 
the comments. When ITU-T Q10/15 has been involved in discussing its comments?

>----Messaggio originale----
>Da: loa@pi.nu
>Data: 6-lug-2011 17.44
>A: "Rui Costa"<RCosta@ptinovacao.pt>
>Cc: "mpls@ietf.org"<mpls@ietf.org>, "ietf@ietf.org"<ietf@ietf.org>, "IETF-
Announce"<ietf-announce@ietf.org>
>Ogg: Re: [mpls] Last Call: &lt;draft-ietf-mpls-tp-cc-cv-rdi-05.txt&gt;	
(Proactive Connectivity Verification, Continuity Check and Remote Defect 
indication for MPLS	Transport	Profile) to Proposed Standard
>
>All,
>
>Since someone has commented about the process used for resolving 
>questions on
>draft-ietf-mpls-tp-cc-cv-rdi I am supplying some details below.
>
>The history of draft-ietf-mpls-tp-cc-cv-rdi working group review
>process is:
>
>On February 3rd 2011 the working group last call was issued
>on version -03
>
>      This was copied to the the Ad Hoc Team List
>      and liaised to SG15 also on February 3rd
>
>      This working group last call ended om Feb 28
>
>
>      On Feb 28 we also received a liaison with comments from SG15
>
>
>The authors compiled a list of all comments received  as part the MPLS
>working group last call; these  comments - and the intended resolution -
>is included in the meeting minutes from the Prague meeting:
>
>
>      http://www.ietf.org/proceedings/80/slides/mpls-9.pdf
>
>
>  During the IETF meeting in Prague, we agreed with the BFD working
>  group to do a separate working group last callfor the BFD working
>  group
>
>The (BFD) working group last call was started on March 30th and ran
>for 13 days. The last call ended on April 11th.
>
>  The authors have since worked hard to resolve comments, some
>  issue has been brought to the working group mailing list for
>  resolution.
>
>  Version -04 of the document was published June 28th.
>
>  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
>  June 29th.
>
>  The AD review resulted in a "New ID needed" due to mostly editorial
>  comments. Version -05 was published on June 29 and the IETF last call
>  started as soon as the new ID was avaialbe.
>
>  The current list of Last Call Comments resoltion is also avaiable at:
>  http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
>
>  The list of issues that the authors kept very carefully, shows without 
>doubt
>  that no comments been ignored.
>
>  Loa
>  mpls wg document shepherd
>
>On 2011-07-05 00:02, Rui Costa wrote:
>> IMHO and for the record:	
>>
>> ITU-T comments regarding this draft haven't been discussed with ITU-T but 
were simply ignored. No LS describing these comments' resolution was sent.	
>>
>> Several service providers regarded this draft as not meeting their 
transport networks' needs.	
>>
>> [The v03 draft was published in Feb and went to WG LC.	
>> The v04 draft addressing WG LC comments was published on the 28th June 
(same date as the proto write-up).	
>> When was the WG LC launched, to verify LC comments resolution?]	
>>
>> Regards,	
>> Rui
>>
>>
>> -----Original Message-----
>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of The 
IESG
>> Sent: quinta-feira, 30 de Junho de 2011 14:47
>> To: IETF-Announce
>> Cc: mpls@ietf.org
>> Subject: [mpls] Last Call:<draft-ietf-mpls-tp-cc-cv-rdi-05.txt>  (Proactive 
Connectivity Verification, Continuity Check and Remote Defect indication for 
MPLS Transport Profile) to Proposed Standard
>>
>>
>> The IESG has received a request from the Multiprotocol Label Switching WG
>> (mpls) to consider the following document:
>> - 'Proactive Connectivity Verification, Continuity Check and Remote
>>     Defect indication for MPLS Transport Profile'
>>    <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>     Continuity Check, Proactive Connectivity Verification and Remote
>>     Defect Indication functionalities are required for MPLS-TP OAM.
>>
>>     Continuity Check monitors the integrity of the continuity of the
>>     label switched path for any loss of continuity defect. Connectivity
>>     verification monitors the integrity of the routing of the label
>>     switched path between sink and source for any connectivity issues.
>>     Remote defect indication enables an End Point to report, to its
>>     associated End Point, a fault or defect condition that it detects on
>>     a pseudo wire, label switched path or Section.
>>
>>     This document specifies methods for proactive continuity check,
>>     continuity verification, and remote defect indication for MPLS-TP
>>     label switched paths, pseudo wires and Sections using Bidirectional
>>     Forwarding Detection.
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>
>>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>
>-- 
>
>
>Loa Andersson                         email: loa.andersson@ericsson.com
>Sr Strategy and Standards Manager            loa@pi.nu
>Ericsson Inc                          phone: +46 10 717 52 13
>                                              +46 767 72 92 13
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls
>



From erminio.ottone_69@libero.it  Wed Jul  6 10:34:03 2011
Return-Path: <erminio.ottone_69@libero.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 B3F2D21F8903; Wed,  6 Jul 2011 10:34:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level: 
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tGdVvDjwRmv7; Wed,  6 Jul 2011 10:34:03 -0700 (PDT)
Received: from outrelay03.libero.it (outrelay03.libero.it [212.52.84.103]) by ietfa.amsl.com (Postfix) with ESMTP id A262F21F88F0; Wed,  6 Jul 2011 10:34:01 -0700 (PDT)
X-CTCH-Spam: Unknown
X-CTCH-RefID: str=0001.0A0B020A.4E149C86.0126,ss=1,re=0.000,fgs=0
X-libjamoibt: 1821
Received: from wmail39 (172.31.0.228) by outrelay03.libero.it (8.5.133) (authenticated as erminio.ottone_69@libero.it) id 4DE4FF1D025345C7; Wed, 6 Jul 2011 19:33:58 +0200
Message-ID: <14289796.745031309973638587.JavaMail.defaultUser@defaultHost>
Date: Wed, 6 Jul 2011 19:33:58 +0200 (CEST)
From: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
To: <RCosta@ptinovacao.pt>, "ietf@ietf.org" <ietf@ietf.org>,  IETF-Announce <ietf-announce@ietf.org>
Subject: R: Re: [mpls] Last Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication for	MPLS	Transport	Profile) to Proposed Standard
MIME-Version: 1.0
Content-Type: text/plain;charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-SenderIP: 79.31.158.220
X-Mailman-Approved-At: Thu, 07 Jul 2011 11:01:14 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2011 17:34:03 -0000

The way this draft has been developed is a bit strange.

The poll for its adoption as a WG document was halted by the MPLS WG chair 
because "it is not possible to judge consensus":

http://www.ietf.org/mail-archive/web/mpls/current/msg04502.html

The lack of consensus was motivated by serious technical concerns raised by 
several transport experts during the poll.

Nevertheless the MPLS WG chair decided to adopt the draft as a WG document:

http://www.ietf.org/mail-archive/web/mpls/current/msg04512.html

After several WG revisions and WG LCs, the technical issues have not been 
resolved.

>Several service providers regarded this draft as not meeting their transport 
networks' needs.	

This is a true statement: the solution in this draft is useless for many MPLS-
TP deployments.

>----Messaggio originale----
>Da: RCosta@ptinovacao.pt
>Data: 5-lug-2011 0.02
>A: "ietf@ietf.org"<ietf@ietf.org>, "IETF-Announce"<ietf-announce@ietf.org>
>Cc: "mpls@ietf.org"<mpls@ietf.org>
>Ogg: Re: [mpls] Last Call:	&lt;draft-ietf-mpls-tp-cc-cv-rdi-05.txt&gt;	
(Proactive	Connectivity	Verification, Continuity Check and Remote Defect 
indication for	MPLS	Transport	Profile) to Proposed Standard
>
>IMHO and for the record:	
>
>ITU-T comments regarding this draft haven't been discussed with ITU-T but 
were simply ignored. No LS describing these comments' resolution was sent.	
>
>Several service providers regarded this draft as not meeting their transport 
networks' needs.	
>
>[The v03 draft was published in Feb and went to WG LC.	
>The v04 draft addressing WG LC comments was published on the 28th June (same 
date as the proto write-up).	
>When was the WG LC launched, to verify LC comments resolution?]	
>
>Regards,	
>Rui
>
>
>-----Original Message-----
>From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of The 
IESG
>Sent: quinta-feira, 30 de Junho de 2011 14:47
>To: IETF-Announce
>Cc: mpls@ietf.org
>Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive 
Connectivity Verification, Continuity Check and Remote Defect indication for 
MPLS Transport Profile) to Proposed Standard
>
>
>The IESG has received a request from the Multiprotocol Label Switching WG
>(mpls) to consider the following document:
>- 'Proactive Connectivity Verification, Continuity Check and Remote
>   Defect indication for MPLS Transport Profile'
>  <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally, comments may be
>sent to iesg@ietf.org instead. In either case, please retain the
>beginning of the Subject line to allow automated sorting.
>
>Abstract
>
>   Continuity Check, Proactive Connectivity Verification and Remote
>   Defect Indication functionalities are required for MPLS-TP OAM.
>
>   Continuity Check monitors the integrity of the continuity of the
>   label switched path for any loss of continuity defect. Connectivity
>   verification monitors the integrity of the routing of the label
>   switched path between sink and source for any connectivity issues.
>   Remote defect indication enables an End Point to report, to its
>   associated End Point, a fault or defect condition that it detects on
>   a pseudo wire, label switched path or Section.
>
>   This document specifies methods for proactive continuity check,
>   continuity verification, and remote defect indication for MPLS-TP
>   label switched paths, pseudo wires and Sections using Bidirectional
>   Forwarding Detection.
>
>
>The file can be obtained via
>http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>
>IESG discussion can be tracked via
>http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>
>
>No IPR declarations have been submitted directly on this I-D.
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls
>
>
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls
>



From david.i.allan@ericsson.com  Wed Jul  6 10:35:48 2011
Return-Path: <david.i.allan@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 D5B7121F893B; Wed,  6 Jul 2011 10:35: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 tSV1SlarQFxx; Wed,  6 Jul 2011 10:35:47 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by ietfa.amsl.com (Postfix) with ESMTP id 3C06521F892D; Wed,  6 Jul 2011 10:35:44 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p66HZfF6026070; Wed, 6 Jul 2011 12:35:43 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.253]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Wed, 6 Jul 2011 13:35:36 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>, "loa@pi.nu" <loa@pi.nu>, Rui Costa <RCosta@ptinovacao.pt>
Date: Wed, 6 Jul 2011 13:35:35 -0400
Subject: RE: [mpls] R: Re: Last Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive Connectivity	Verification, Continuity Check and Remote Defect indication for	MPLS	Transport	Profile) to Proposed Standard
Thread-Topic: [mpls] R: Re: Last Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive Connectivity	Verification, Continuity Check and Remote Defect indication for	MPLS	Transport	Profile) to Proposed Standard
Thread-Index: Acw8AeQS0u6Io4DfRNinXiLBndDNcQAACzKQ
Message-ID: <60C093A41B5E45409A19D42CF7786DFD52212CBBDC@EUSAACMS0703.eamcs.ericsson.se>
References: <15271688.742501309973184714.JavaMail.defaultUser@defaultHost>
In-Reply-To: <15271688.742501309973184714.JavaMail.defaultUser@defaultHost>
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, 07 Jul 2011 11:01:14 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2011 17:35:49 -0000

Hi Erminio:

Two of the three document editors were present at SG15 plenary in February =
where the comments originated. The revised meeting schedule resulted in a d=
ay spent going through the document with the editors. IMO there were lots o=
f discussion and legitimate issues with the document identified and correct=
ed so it was a useful session. The liaison of same was in many ways *after =
the fact*.

Cheers
Dave=20

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of erm=
inio.ottone_69@libero.it
Sent: Wednesday, July 06, 2011 10:26 AM
To: loa@pi.nu; Rui Costa
Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
Subject: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Pr=
oactive Connectivity Verification, Continuity Check and Remote Defect indic=
ation for MPLS Transport Profile) to Proposed Standard

>  Version -04 of the document was published June 28th.
>
>  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent =20
> June 29th.
>

So when the WG LC to confirm the LC comment resolution has been launched?

The proto write-up says:

            It has also passed a working roup call to verify that LC commen=
ts were correctly with minor comments.=20

It also says:

            The comments has been
            carefully discussed between the authors and people making the c=
omments and
            has been resolved.

But it seems that some comments have not been discussed with the authors of=
 the comments. When ITU-T Q10/15 has been involved in discussing its commen=
ts?

>----Messaggio originale----
>Da: loa@pi.nu
>Data: 6-lug-2011 17.44
>A: "Rui Costa"<RCosta@ptinovacao.pt>
>Cc: "mpls@ietf.org"<mpls@ietf.org>, "ietf@ietf.org"<ietf@ietf.org>,=20
>"IETF-
Announce"<ietf-announce@ietf.org>
>Ogg: Re: [mpls] Last Call: &lt;draft-ietf-mpls-tp-cc-cv-rdi-05.txt&gt;=09
(Proactive Connectivity Verification, Continuity Check and Remote Defect=20
indication for MPLS	Transport	Profile) to Proposed Standard
>
>All,
>
>Since someone has commented about the process used for resolving=20
>questions on draft-ietf-mpls-tp-cc-cv-rdi I am supplying some details=20
>below.
>
>The history of draft-ietf-mpls-tp-cc-cv-rdi working group review=20
>process is:
>
>On February 3rd 2011 the working group last call was issued on version=20
>-03
>
>      This was copied to the the Ad Hoc Team List
>      and liaised to SG15 also on February 3rd
>
>      This working group last call ended om Feb 28
>
>
>      On Feb 28 we also received a liaison with comments from SG15
>
>
>The authors compiled a list of all comments received  as part the MPLS=20
>working group last call; these  comments - and the intended resolution=20
>- is included in the meeting minutes from the Prague meeting:
>
>
>      http://www.ietf.org/proceedings/80/slides/mpls-9.pdf
>
>
>  During the IETF meeting in Prague, we agreed with the BFD working =20
> group to do a separate working group last callfor the BFD working =20
> group
>
>The (BFD) working group last call was started on March 30th and ran for=20
>13 days. The last call ended on April 11th.
>
>  The authors have since worked hard to resolve comments, some  issue=20
> has been brought to the working group mailing list for  resolution.
>
>  Version -04 of the document was published June 28th.
>
>  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent =20
> June 29th.
>
>  The AD review resulted in a "New ID needed" due to mostly editorial =20
> comments. Version -05 was published on June 29 and the IETF last call =20
> started as soon as the new ID was avaialbe.
>
>  The current list of Last Call Comments resoltion is also avaiable at:
>  http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
>
>  The list of issues that the authors kept very carefully, shows=20
>without doubt
>  that no comments been ignored.
>
>  Loa
>  mpls wg document shepherd
>
>On 2011-07-05 00:02, Rui Costa wrote:
>> IMHO and for the record:=09
>>
>> ITU-T comments regarding this draft haven't been discussed with ITU-T=20
>> but
were simply ignored. No LS describing these comments' resolution was sent.=
=09
>>
>> Several service providers regarded this draft as not meeting their
transport networks' needs.=09
>>
>> [The v03 draft was published in Feb and went to WG LC.=09
>> The v04 draft addressing WG LC comments was published on the 28th=20
>> June
(same date as the proto write-up).=09
>> When was the WG LC launched, to verify LC comments resolution?]=09
>>
>> Regards,=09
>> Rui
>>
>>
>> -----Original Message-----
>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf=20
>> Of The
IESG
>> Sent: quinta-feira, 30 de Junho de 2011 14:47
>> To: IETF-Announce
>> Cc: mpls@ietf.org
>> Subject: [mpls] Last Call:<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> =20
>> (Proactive
Connectivity Verification, Continuity Check and Remote Defect indication fo=
r MPLS Transport Profile) to Proposed Standard
>>
>>
>> The IESG has received a request from the Multiprotocol Label=20
>> Switching WG
>> (mpls) to consider the following document:
>> - 'Proactive Connectivity Verification, Continuity Check and Remote
>>     Defect indication for MPLS Transport Profile'
>>    <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>  as a Proposed Standard
>>
>> The IESG plans to make a decision in the next few weeks, and solicits=20
>> final comments on this action. Please send substantive comments to=20
>> the ietf@ietf.org mailing lists by 2011-07-14. Exceptionally,=20
>> comments may be sent to iesg@ietf.org instead. In either case, please=20
>> retain the beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>     Continuity Check, Proactive Connectivity Verification and Remote
>>     Defect Indication functionalities are required for MPLS-TP OAM.
>>
>>     Continuity Check monitors the integrity of the continuity of the
>>     label switched path for any loss of continuity defect. Connectivity
>>     verification monitors the integrity of the routing of the label
>>     switched path between sink and source for any connectivity issues.
>>     Remote defect indication enables an End Point to report, to its
>>     associated End Point, a fault or defect condition that it detects on
>>     a pseudo wire, label switched path or Section.
>>
>>     This document specifies methods for proactive continuity check,
>>     continuity verification, and remote defect indication for MPLS-TP
>>     label switched paths, pseudo wires and Sections using Bidirectional
>>     Forwarding Detection.
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>
>>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>
>--
>
>
>Loa Andersson                         email: loa.andersson@ericsson.com
>Sr Strategy and Standards Manager            loa@pi.nu
>Ericsson Inc                          phone: +46 10 717 52 13
>                                              +46 767 72 92 13=20
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls
>


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From david.i.allan@ericsson.com  Wed Jul  6 11:24:59 2011
Return-Path: <david.i.allan@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 5173421F890F; Wed,  6 Jul 2011 11:24:59 -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 ilUXmnQYEfbQ; Wed,  6 Jul 2011 11:24:58 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by ietfa.amsl.com (Postfix) with ESMTP id 7F33621F8917; Wed,  6 Jul 2011 11:24:58 -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 p66IOuAH003866; Wed, 6 Jul 2011 13:24:58 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.253]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Wed, 6 Jul 2011 14:24:55 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>, "RCosta@ptinovacao.pt" <RCosta@ptinovacao.pt>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
Date: Wed, 6 Jul 2011 14:24:54 -0400
Subject: RE: [mpls] R: Re: Last	Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication	for	MPLS	Transport	Profile) to Proposed Standard
Thread-Topic: [mpls] R: Re: Last	Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication	for	MPLS	Transport	Profile) to Proposed Standard
Thread-Index: Acw8AvlCLDZgm+U5SBqkN4NxEuu8YgAAIlJQ
Message-ID: <60C093A41B5E45409A19D42CF7786DFD52212CBC63@EUSAACMS0703.eamcs.ericsson.se>
References: <14289796.745031309973638587.JavaMail.defaultUser@defaultHost>
In-Reply-To: <14289796.745031309973638587.JavaMail.defaultUser@defaultHost>
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, 07 Jul 2011 11:01:14 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2011 18:24:59 -0000

Hi Erminio:

<snipped>
>Several service providers regarded this draft as not meeting their=20
>transport networks' needs.=09

E> This is a true statement: the solution in this draft is useless for many=
 MPLS- TP deployments.

The two statements do not necessarily follow.=20

What we established during discussions at the SG15 plenary in February was =
that the issue some service providers had was that the IETF BFD solution ex=
ceeded their requirements in that there was additional functionality they d=
id not see a need for, and that they considered any additional functionalit=
y parasitic.

However this is a consequence of adapting an existing technology to a new a=
pplication. I do not see any way around that. And the entire joint project =
was based on the premise of engineering re-use not greenfield design. That =
is what it said on the tin up front, and IMO why when the IETF started down=
 this path packet transport transitioned from being a minority sport to mai=
nstream, so it is a bit late to cry foul....

My 2 cents
Dave

>----Messaggio originale----
>Da: RCosta@ptinovacao.pt
>Data: 5-lug-2011 0.02
>A: "ietf@ietf.org"<ietf@ietf.org>,=20
>"IETF-Announce"<ietf-announce@ietf.org>
>Cc: "mpls@ietf.org"<mpls@ietf.org>
>Ogg: Re: [mpls] Last Call:	&lt;draft-ietf-mpls-tp-cc-cv-rdi-05.txt&gt;=09
(Proactive	Connectivity	Verification, Continuity Check and Remote Defect=20
indication for	MPLS	Transport	Profile) to Proposed Standard
>
>IMHO and for the record:=09
>
>ITU-T comments regarding this draft haven't been discussed with ITU-T=20
>but
were simply ignored. No LS describing these comments' resolution was sent.=
=09
>
>Several service providers regarded this draft as not meeting their=20
>transport
networks' needs.=09
>
>[The v03 draft was published in Feb and went to WG LC.=09
>The v04 draft addressing WG LC comments was published on the 28th June=20
>(same
date as the proto write-up).=09
>When was the WG LC launched, to verify LC comments resolution?]=09
>
>Regards,=09
>Rui
>
>
>-----Original Message-----
>From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of=20
>The
IESG
>Sent: quinta-feira, 30 de Junho de 2011 14:47
>To: IETF-Announce
>Cc: mpls@ietf.org
>Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>=20
>(Proactive
Connectivity Verification, Continuity Check and Remote Defect indication fo=
r MPLS Transport Profile) to Proposed Standard
>
>
>The IESG has received a request from the Multiprotocol Label Switching=20
>WG
>(mpls) to consider the following document:
>- 'Proactive Connectivity Verification, Continuity Check and Remote
>   Defect indication for MPLS Transport Profile'
>  <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> as a Proposed Standard
>
>The IESG plans to make a decision in the next few weeks, and solicits=20
>final comments on this action. Please send substantive comments to the=20
>ietf@ietf.org mailing lists by 2011-07-14. Exceptionally, comments may=20
>be sent to iesg@ietf.org instead. In either case, please retain the=20
>beginning of the Subject line to allow automated sorting.
>
>Abstract
>
>   Continuity Check, Proactive Connectivity Verification and Remote
>   Defect Indication functionalities are required for MPLS-TP OAM.
>
>   Continuity Check monitors the integrity of the continuity of the
>   label switched path for any loss of continuity defect. Connectivity
>   verification monitors the integrity of the routing of the label
>   switched path between sink and source for any connectivity issues.
>   Remote defect indication enables an End Point to report, to its
>   associated End Point, a fault or defect condition that it detects on
>   a pseudo wire, label switched path or Section.
>
>   This document specifies methods for proactive continuity check,
>   continuity verification, and remote defect indication for MPLS-TP
>   label switched paths, pseudo wires and Sections using Bidirectional
>   Forwarding Detection.
>
>
>The file can be obtained via
>http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>
>IESG discussion can be tracked via
>http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>
>
>No IPR declarations have been submitted directly on this I-D.
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls
>
>
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls
>


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From touch@isi.edu  Thu Jul  7 13:37:26 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 6EA1F11E809A for <ietf@ietfa.amsl.com>; Thu,  7 Jul 2011 13:37:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.999
X-Spam-Level: 
X-Spam-Status: No, score=-103.999 tagged_above=-999 required=5 tests=[AWL=-1.400, 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 MPUoZzp-Ca8l for <ietf@ietfa.amsl.com>; Thu,  7 Jul 2011 13:37:25 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 7FF3811E807C for <ietf@ietf.org>; Thu,  7 Jul 2011 13:37:25 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id p67KauR2027878 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 7 Jul 2011 13:36:56 -0700 (PDT)
Message-ID: <4E1618E8.3090208@isi.edu>
Date: Thu, 07 Jul 2011 13:36:56 -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: dcrocker@bbiw.net
Subject: Re: Comments surrounding draft-iab-dns-applications-01
References: <a06240800c9df29c0bf75@[10.31.203.186]>	<B8FD63DA-3047-4CE5-8CA0-BA12B54617A1@tcb.net>	<4E138C67.9020407@isi.edu> <4E13B564.3010404@dcrocker.net>
In-Reply-To: <4E13B564.3010404@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Dave CROCKER <dhc2@dcrocker.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jul 2011 20:37:26 -0000

On 7/5/2011 6:07 PM, Dave CROCKER wrote:
>
>
> On 7/5/2011 3:12 PM, Joe Touch wrote:
>> " The SRV record allows
>> DNS resolvers to search for particular applications and underlying
>> transports (for example, HTTP running over TLS, see [RFC2818]) and to
>> learn the domain name and port where that service resides in a given
>> administrative domain. "
>>
>> The transports should be TCP, UDP, or (arguably or not) other transport
>> protocols. TLS is not a transport.
>
> Also, strictly speaking, the function that is performed is lookup or
> mapping, not "search". The difference is large.

Agreed. For those who *really* want to do other stuff beyond lookup with 
the DNS, I refer you to:

http://www.cs.ucr.edu/~michalis/TALKS/OOS-2001/touch-OOS.pdf.gz

Joe

From RCosta@ptinovacao.pt  Thu Jul  7 17:14:53 2011
Return-Path: <RCosta@ptinovacao.pt>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23C3521F883A; Thu,  7 Jul 2011 17:14:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E3HL8tZ7FXFj; Thu,  7 Jul 2011 17:14:51 -0700 (PDT)
Received: from owa.ptinovacao.pt (webmail.ptinovacao.pt [194.65.138.99]) by ietfa.amsl.com (Postfix) with ESMTP id DACED21F8838; Thu,  7 Jul 2011 17:14:45 -0700 (PDT)
Received: from INOAVREX11.ptin.corpPT.com ([10.112.15.121]) by inoavrcas01.ptin.corpPT.com ([10.112.15.99]) with mapi; Fri, 8 Jul 2011 01:14:43 +0100
From: Rui Costa <RCosta@ptinovacao.pt>
To: David Allan I <david.i.allan@ericsson.com>, Stewart Bryant <stbryant@cisco.com>
Date: Fri, 8 Jul 2011 01:14:42 +0100
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity Verification, Continuity Check and Remote Defect indication for MPLS	Transport	Profile) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity Verification, Continuity Check and Remote Defect indication for MPLS	Transport	Profile) to Proposed Standard
Thread-Index: Acw3LJ0GTOqQfPcUQOGUhgK/1kXgjgDPfXWgACJLxEA=
Message-ID: <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B6BC@INOAVREX11.ptin.corpPT.com>
Accept-Language: pt-PT
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: pt-PT
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2011 00:14:53 -0000

David,=09

Reading something, keeping it on record, without effect in the draft and "i=
gnoring comments" have IMHO similar outcomes. As author of the draft you ar=
e free to do it. These standards have a great impact in our work, so i'm al=
so free to write what i did.=09




Stewart,=09

My technical concerns regarding this draft were expressed...=09
...in the (ITU-T -> IETF, Feb/2011) liaison regarding it (LS281, i believe)=
;=09
...in operators' meetings' that took place during ITU-T's Feb/2011 plenary =
meeting;=09
...in a comparison session that took place during that same ITU-T meeting.=
=09
Some:=09

CC/CV=09
I don't understand the need for 2 types of packets: a single type allows CC=
; mismatching identifiers in the same CC packets allow CV.=09
Besides adding complexity, we whether always activate both or potentiate un=
detected mismerges.=09
(BTW: can't understand how we propose one ACH codepoint to CC, another for =
CV, [counting other drafts, another for frame loss ...] but don't consider =
assigning 1 single ACH protocol identifier codepoint as requested by ITU-T)=
=09

Uni P2P / P2MP=09
I can't see how BFD will support unidir and hence P2MP other than...=09
...eliminating the session "state variable" (down, init, up), aiming just t=
he state variables we really need, bringing us to something similar to 1731=
, eventually with other bits on the wire or...=09
...using IP to create the reverse way, which we cannot assume per requireme=
nts;=09
Will we create a complete different tool for that?=09
(BFD's B=3D"bidirectional")=09

Provisioning list=09
This is an MPLS profile/subset (and i heard) achievable through a particula=
r configuration. So, i expect each draft-ietf-mpls-TP-* to focus on that pr=
ofile/configuration. However, i keep seeing references f.i. to IP encapsula=
tions unexpected under TP's OAM.=09
I don't thus understand what the aim is: do we expect this in TP, are we ta=
lking about MPLS in general?... The TP profile is never quite delimited.=09
Does chapter 4 contain ALL the configurable parameters list agreed to provi=
de in the comparison session?=09

Backwards compatibility=09
This was the main argument risen to ground MPLS-TP OAM on BFD. It's not a b=
etter argument than grounding MPLS-TP OAM on 1731 due to its ETH deployment=
 plus coherence with SDH, OTN, as defended by ITU-T.=09
For reasons like the above, however, MPLS-TP BFD won't be backwards compati=
ble with previous BFD (even considering just CC/CV). They don't even share =
the same codepoint.=09

Simplicity=09
Whether we look to PDH, SDH, OTN or ETH, ITU-T's approach to CC is simpler:=
 in each flow, a standard defined nr of constant heartbeat signals (with st=
andard constant or provisioned period - no auto/negotiated -) means OK. A s=
tandard defined number of misses means lost Rx connection. An RDI, the only=
 articulation between Rx and Tx flows, meaningful in bidirectional applicat=
ions, allows each pear to identify Tx problems.=09
This OAM simplicity is the key for reliable fail finger pointing, performan=
ce reports and protection. Also to allow scaling, more implementation oppor=
tunities/manufacturers, which is valuable for operators.=09


IMHO, between your MPLS-TP view and MPLS/IP, it becomes more and more diffi=
cult to tell which is which.=09

Regards,=09
Rui=09









-----Original Message-----
From: David Allan I [mailto:david.i.allan@ericsson.com]=20
Sent: quarta-feira, 6 de Julho de 2011 19:25
To: erminio.ottone_69@libero.it; Rui Costa; ietf@ietf.org; IETF-Announce
Cc: mpls@ietf.org
Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>=
 (Proactive Connectivity Verification, Continuity Check and Remote Defect i=
ndication for MPLS Transport Profile) to Proposed Standard

Hi Erminio:

<snipped>
>Several service providers regarded this draft as not meeting their=20
>transport networks' needs.=09

E> This is a true statement: the solution in this draft is useless for many=
 MPLS- TP deployments.

The two statements do not necessarily follow.=20

What we established during discussions at the SG15 plenary in February was =
that the issue some service providers had was that the IETF BFD solution ex=
ceeded their requirements in that there was additional functionality they d=
id not see a need for, and that they considered any additional functionalit=
y parasitic.

However this is a consequence of adapting an existing technology to a new a=
pplication. I do not see any way around that. And the entire joint project =
was based on the premise of engineering re-use not greenfield design. That =
is what it said on the tin up front, and IMO why when the IETF started down=
 this path packet transport transitioned from being a minority sport to mai=
nstream, so it is a bit late to cry foul....

My 2 cents
Dave




-----Original Message-----
From: David Allan I [mailto:david.i.allan@ericsson.com]=20
Sent: quarta-feira, 6 de Julho de 2011 18:36
To: erminio.ottone_69@libero.it; loa@pi.nu; Rui Costa
Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>=
 (Proactive Connectivity Verification, Continuity Check and Remote Defect i=
ndication for MPLS Transport Profile) to Proposed Standard

Hi Erminio:

Two of the three document editors were present at SG15 plenary in February =
where the comments originated. The revised meeting schedule resulted in a d=
ay spent going through the document with the editors. IMO there were lots o=
f discussion and legitimate issues with the document identified and correct=
ed so it was a useful session. The liaison of same was in many ways *after =
the fact*.

Cheers
Dave




-----Original Message-----
From: erminio.ottone_69@libero.it [mailto:erminio.ottone_69@libero.it]=20
Sent: quarta-feira, 6 de Julho de 2011 18:34
To: Rui Costa; ietf@ietf.org; IETF-Announce
Cc: mpls@ietf.org
Subject: R: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Pr=
oactive Connectivity Verification, Continuity Check and Remote Defect indic=
ation for MPLS Transport Profile) to Proposed Standard

The way this draft has been developed is a bit strange.

The poll for its adoption as a WG document was halted by the MPLS WG chair=
=20
because "it is not possible to judge consensus":

http://www.ietf.org/mail-archive/web/mpls/current/msg04502.html

The lack of consensus was motivated by serious technical concerns raised by=
=20
several transport experts during the poll.

Nevertheless the MPLS WG chair decided to adopt the draft as a WG document:

http://www.ietf.org/mail-archive/web/mpls/current/msg04512.html

After several WG revisions and WG LCs, the technical issues have not been=20
resolved.

>Several service providers regarded this draft as not meeting their transpo=
rt=20
networks' needs.=09

This is a true statement: the solution in this draft is useless for many MP=
LS-
TP deployments.


-----Original Message-----
From: erminio.ottone_69@libero.it [mailto:erminio.ottone_69@libero.it]=20
Sent: quarta-feira, 6 de Julho de 2011 18:26
To: loa@pi.nu; Rui Costa
Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
Subject: R: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Pr=
oactive Connectivity Verification, Continuity Check and Remote Defect indic=
ation for MPLS Transport Profile) to Proposed Standard

>  Version -04 of the document was published June 28th.
>
>  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
>  June 29th.
>

So when the WG LC to confirm the LC comment resolution has been launched?

The proto write-up says:

            It has also passed a working roup call to verify that LC commen=
ts=20
were correctly with minor comments.=20

It also says:

            The comments has been
            carefully discussed between the authors and people making the=20
comments and
            has been resolved.

But it seems that some comments have not been discussed with the authors of=
=20
the comments. When ITU-T Q10/15 has been involved in discussing its comment=
s?




-----Original Message-----
From: Loa Andersson [mailto:loa@pi.nu]=20
Sent: quarta-feira, 6 de Julho de 2011 16:44
To: Rui Costa
Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proac=
tive Connectivity Verification, Continuity Check and Remote Defect indicati=
on for MPLS Transport Profile) to Proposed Standard

All,

Since someone has commented about the process used for resolving=20
questions on
draft-ietf-mpls-tp-cc-cv-rdi I am supplying some details below.

The history of draft-ietf-mpls-tp-cc-cv-rdi working group review
process is:

On February 3rd 2011 the working group last call was issued
on version -03

      This was copied to the the Ad Hoc Team List
      and liaised to SG15 also on February 3rd

      This working group last call ended om Feb 28


      On Feb 28 we also received a liaison with comments from SG15


The authors compiled a list of all comments received  as part the MPLS
working group last call; these  comments - and the intended resolution -
is included in the meeting minutes from the Prague meeting:


      http://www.ietf.org/proceedings/80/slides/mpls-9.pdf


  During the IETF meeting in Prague, we agreed with the BFD working
  group to do a separate working group last callfor the BFD working
  group

The (BFD) working group last call was started on March 30th and ran
for 13 days. The last call ended on April 11th.

  The authors have since worked hard to resolve comments, some
  issue has been brought to the working group mailing list for
  resolution.

  Version -04 of the document was published June 28th.

  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
  June 29th.

  The AD review resulted in a "New ID needed" due to mostly editorial
  comments. Version -05 was published on June 29 and the IETF last call
  started as soon as the new ID was avaialbe.

  The current list of Last Call Comments resoltion is also avaiable at:
  http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls

  The list of issues that the authors kept very carefully, shows without=20
doubt
  that no comments been ignored.

  Loa
  mpls wg document shepherd







-----Original Message-----
From: David Allan I [mailto:david.i.allan@ericsson.com]=20
Sent: quarta-feira, 6 de Julho de 2011 14:58
To: Rui Costa; ietf@ietf.org; IETF-Announce
Cc: mpls@ietf.org
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proac=
tive Connectivity Verification, Continuity Check and Remote Defect indicati=
on for MPLS Transport Profile) to Proposed Standard

Hi Rui:

The comments were not ignored, the resolution of the Q10 comments as well a=
s those collected from the MPLS WG was presented at the last IETF. My sprea=
dsheet from which that report was generated and has been augmented to inclu=
de the BFD WG comments is available at http://www.pi.nu/~loa/cc-cv-rdi-Last=
-Call-Comments.xls

So you know...=09
Dave


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Rui=
 Costa
Sent: segunda-feira, 4 de Julho de 2011 23:03
To: ietf@ietf.org; IETF-Announce
Cc: mpls@ietf.org
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proac=
tive Connectivity Verification, Continuity Check and Remote Defect indicati=
on for MPLS Transport Profile) to Proposed Standard

IMHO and for the record:=09

ITU-T comments regarding this draft haven't been discussed with ITU-T but w=
ere simply ignored. No LS describing these comments' resolution was sent.=09

Several service providers regarded this draft as not meeting their transpor=
t networks' needs.=09

[The v03 draft was published in Feb and went to WG LC.=09
The v04 draft addressing WG LC comments was published on the 28th June (sam=
e date as the proto write-up).=09
When was the WG LC launched, to verify LC comments resolution?]=09

Regards,=09
Rui


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of The=
 IESG
Sent: quinta-feira, 30 de Junho de 2011 14:47
To: IETF-Announce
Cc: mpls@ietf.org
Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive=
 Connectivity Verification, Continuity Check and Remote Defect indication f=
or MPLS Transport Profile) to Proposed Standard


The IESG has received a request from the Multiprotocol Label Switching WG
(mpls) to consider the following document:
- 'Proactive Connectivity Verification, Continuity Check and Remote
   Defect indication for MPLS Transport Profile'
  <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract

   Continuity Check, Proactive Connectivity Verification and Remote
   Defect Indication functionalities are required for MPLS-TP OAM.

   Continuity Check monitors the integrity of the continuity of the
   label switched path for any loss of continuity defect. Connectivity
   verification monitors the integrity of the routing of the label
   switched path between sink and source for any connectivity issues.
   Remote defect indication enables an End Point to report, to its
   associated End Point, a fault or defect condition that it detects on
   a pseudo wire, label switched path or Section.

   This document specifies methods for proactive continuity check,
   continuity verification, and remote defect indication for MPLS-TP
   label switched paths, pseudo wires and Sections using Bidirectional
   Forwarding Detection.


The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/


No IPR declarations have been submitted directly on this I-D.
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

From mail@sabahattin-gucukoglu.com  Thu Jul  7 19:30:43 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 4323921F89EF for <ietf@ietfa.amsl.com>; Thu,  7 Jul 2011 19:30:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.562
X-Spam-Level: *
X-Spam-Status: No, score=1.562 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_13=0.6, 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 jfsgSaa4HgCI for <ietf@ietfa.amsl.com>; Thu,  7 Jul 2011 19:30:42 -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 4857021F89ED for <ietf@ietf.org>; Thu,  7 Jul 2011 19:30:41 -0700 (PDT)
Received: from Mintaka.sabahattin-gucukoglu.com ([::ffff:127.0.0.1]:55857) by Mintaka.sabahattin-gucukoglu.com with [XMail 1.27 ESMTP Server] id <S36E72> for <ietf@ietf.org> from <mail@sabahattin-gucukoglu.com>; Fri, 24 Jun 2011 20:29:46 +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, 24 Jun 2011 20:29:45 +0100
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?  
In-Reply-To: <EDB52C83-25F6-40C4-A5D1-9AFCEC13CB74@network-heretics.com>
Date: Fri, 24 Jun 2011 20:29:43 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <5BF937D2-570A-4FC8-878F-E9F52CC37C3B@sabahattin-gucukoglu.com>
References: <6C4159EC-9C66-48B4-8856-AD772745A026@gmail.com> <EDB52C83-25F6-40C4-A5D1-9AFCEC13CB74@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-1311535786.148854@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, 08 Jul 2011 02:30:43 -0000

On 24 Jun 2011, at 16:54, Keith Moore wrote:
> 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

Another aspect, one that perhaps isn't appreciated as much, is one of =
reconciliation. People, given the chance to understand, will wish to =
understand (or at least, the people in the IETF often will).  They will =
wish to make up their differences.  They will wish to make compromises.  =
That is only possible when the consensus is in full public view, and not =
when it is somehow mediated by a potentially less able agent than =
oneself or ones other peers.

In this case, anybody not in the WG got the short end.  I don't say it's =
entirely my fault, but only because I'm wiser now than when the IESG =
decided to settle in favour of this document.  Of course I don't have to =
be happy about it, but I'll understand, so long as the rationale against =
is for the good.  A conclusion from the IESG would therefore be much =
appreciated, with details of how the decision was reached.  =46rom here, =
it looks like a bunch of objections were raised, in a place no IETF =
participant would expect to miss, and they were not satisfactorily =
addressed by the claimed supporters.  Those, whoever they may be, have =
retreated to the shadows of some majority I can't see, in the v6ops WG =
which, naturally, I have no reason to be a part of because their =
interests are totally unaligned from mine, legitimately or otherwise.

But certainly there must be some way, some definite way for people in =
the IETF to go to thrash out the last call period.  It simply can't be =
all about majority, much less unseen majority.  That isn't consensus, =
rough or not.

Cheers,
Sabahattin

From narten@us.ibm.com  Thu Jul  7 22:05:02 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 350C321F8948 for <ietf@ietfa.amsl.com>; Thu,  7 Jul 2011 22:05:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.446
X-Spam-Level: 
X-Spam-Status: No, score=-106.446 tagged_above=-999 required=5 tests=[AWL=-0.153, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_URI_CONS7=0.306, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id US1-vrOimXND for <ietf@ietfa.amsl.com>; Thu,  7 Jul 2011 22:05:01 -0700 (PDT)
Received: from e6.ny.us.ibm.com (e6.ny.us.ibm.com [32.97.182.146]) by ietfa.amsl.com (Postfix) with ESMTP id 5353E21F8944 for <ietf@ietf.org>; Thu,  7 Jul 2011 22:05:01 -0700 (PDT)
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e6.ny.us.ibm.com (8.14.4/8.13.1) with ESMTP id p684T9SW016311 for <ietf@ietf.org>; Fri, 8 Jul 2011 00:29:09 -0400
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p684rCx5481302 for <ietf@ietf.org>; Fri, 8 Jul 2011 00:53:16 -0400
Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p684rCBY018011 for <ietf@ietf.org>; Fri, 8 Jul 2011 00:53:12 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.176.22]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p684rCkH017884 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 8 Jul 2011 00:53:12 -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 p684r7EB008237 for <ietf@ietf.org>; Fri, 8 Jul 2011 00:53:07 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p684r2Z2008133 for ietf@ietf.org; Fri, 8 Jul 2011 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201107080453.p684r2Z2008133@rotala.raleigh.ibm.com>
Date: Fri, 08 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, 08 Jul 2011 05:05:02 -0000

Total of 209 messages in the last 7 days.
 
script run at: Fri Jul  8 00:53:02 EDT 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 17.22% |   36 | 17.15% |   261678 | moore@network-heretics.com
  1.91% |    4 |  7.23% |   110229 | david.i.allan@ericsson.com
  4.78% |   10 |  3.49% |    53224 | dougb@dougbarton.us
  3.35% |    7 |  4.26% |    65009 | lorenzo@google.com
  3.83% |    8 |  2.60% |    39595 | johnl@iecc.com
  3.35% |    7 |  2.86% |    43611 | joelja@bogus.com
  3.35% |    7 |  2.76% |    42062 | ipng@69706e6720323030352d30312d31340a.nosense.org
  2.87% |    6 |  3.11% |    47371 | rbonica@juniper.net
  2.39% |    5 |  3.25% |    49613 | cb.list6@gmail.com
  2.87% |    6 |  2.00% |    30526 | mrex@sap.com
  2.87% |    6 |  1.83% |    27936 | randy@psg.com
  2.39% |    5 |  2.31% |    35228 | marka@isc.org
  2.87% |    6 |  1.69% |    25707 | jnc@mercury.lcs.mit.edu
  1.44% |    3 |  3.04% |    46397 | hongyu.lihongyu@huawei.com
  2.39% |    5 |  1.64% |    24986 | dhc2@dcrocker.net
  1.91% |    4 |  1.29% |    19665 | dot@dotat.at
  0.96% |    2 |  1.65% |    25236 | rcosta@ptinovacao.pt
  0.96% |    2 |  1.43% |    21883 | v6ops@globis.net
  1.44% |    3 |  0.90% |    13795 | john@jlc.net
  0.96% |    2 |  1.30% |    19794 | nurit.sprecher@nsn.com
  0.96% |    2 |  1.20% |    18302 | erminio.ottone_69@libero.it
  0.96% |    2 |  1.10% |    16818 | tjc@ecs.soton.ac.uk
  0.96% |    2 |  1.01% |    15358 | arturo.servin@gmail.com
  0.96% |    2 |  1.00% |    15318 | brian.e.carpenter@gmail.com
  0.96% |    2 |  0.90% |    13737 | rdroms@cisco.com
  0.96% |    2 |  0.88% |    13397 | ek@google.com
  0.96% |    2 |  0.82% |    12522 | mark@townsley.net
  0.96% |    2 |  0.79% |    12078 | scott.brim@gmail.com
  0.48% |    1 |  1.26% |    19275 | eve@xmlgrrl.com
  0.96% |    2 |  0.71% |    10829 | pch-v6ops@u-1.phicoh.com
  0.48% |    1 |  1.17% |    17823 | wmills@yahoo-inc.com
  0.96% |    2 |  0.68% |    10321 | robert@raszuk.net
  0.48% |    1 |  1.11% |    16996 | danny@tcb.net
  0.96% |    2 |  0.63% |     9544 | fluffy@cisco.com
  0.96% |    2 |  0.60% |     9182 | paul.hoffman@vpnc.org
  0.96% |    2 |  0.60% |     9179 | touch@isi.edu
  0.96% |    2 |  0.54% |     8248 | mohta@necom830.hpcl.titech.ac.jp
  0.48% |    1 |  0.92% |    14072 | eran@hueniverse.com
  0.48% |    1 |  0.76% |    11593 | osa.peter@gmail.com
  0.48% |    1 |  0.67% |    10210 | ron.even.tlv@gmail.com
  0.48% |    1 |  0.66% |     9999 | msk@cloudmark.com
  0.48% |    1 |  0.62% |     9469 | jricher@mitre.org
  0.48% |    1 |  0.61% |     9380 | ted.lemon@nominum.com
  0.48% |    1 |  0.59% |     9047 | loa@pi.nu
  0.48% |    1 |  0.57% |     8674 | stbryant@cisco.com
  0.48% |    1 |  0.57% |     8636 | nomcom-chair@ietf.org
  0.48% |    1 |  0.56% |     8529 | narten@us.ibm.com
  0.48% |    1 |  0.53% |     8127 | swallow@cisco.com
  0.48% |    1 |  0.53% |     8125 | trejrco@gmail.com
  0.48% |    1 |  0.53% |     8120 | alessandro.dalessandro@telecomitalia.it
  0.48% |    1 |  0.50% |     7625 | rogerj@gmail.com
  0.48% |    1 |  0.49% |     7502 | stig@venaas.com
  0.48% |    1 |  0.47% |     7122 | jun@wide.ad.jp
  0.48% |    1 |  0.46% |     6978 | jordi.palet@consulintel.es
  0.48% |    1 |  0.46% |     6954 | alexandru.petrescu@gmail.com
  0.48% |    1 |  0.45% |     6921 | palm@broadcom.com
  0.48% |    1 |  0.44% |     6699 | david.black@emc.com
  0.48% |    1 |  0.42% |     6477 | jvasseur@cisco.com
  0.48% |    1 |  0.42% |     6356 | heard@pobox.com
  0.48% |    1 |  0.42% |     6335 | mail@sabahattin-gucukoglu.com
  0.48% |    1 |  0.37% |     5706 | jhw@apple.com
  0.48% |    1 |  0.37% |     5586 | listbounce-01@voort.ca
  0.48% |    1 |  0.37% |     5586 | frnkblk@iname.com
  0.48% |    1 |  0.36% |     5534 | melinda.shore@gmail.com
  0.48% |    1 |  0.35% |     5328 | klaas@cisco.com
  0.48% |    1 |  0.34% |     5231 | gert@space.net
  0.48% |    1 |  0.34% |     5199 | ynir@checkpoint.com
  0.48% |    1 |  0.33% |     4992 | sm@resistor.net
  0.48% |    1 |  0.32% |     4839 | michel@arneill-py.sacramento.ca.us
  0.48% |    1 |  0.32% |     4819 | scott@kitterman.com
  0.48% |    1 |  0.31% |     4780 | kurt.zeilenga@isode.com
  0.48% |    1 |  0.31% |     4707 | dwm@xpasc.com
  0.48% |    1 |  0.31% |     4694 | gwz@net-zen.net
  0.48% |    1 |  0.29% |     4401 | dave@cridland.net
  0.48% |    1 |  0.29% |     4391 | hannes.tschofenig@gmx.net
  0.48% |    1 |  0.28% |     4323 | jmh@joelhalpern.com
  0.48% |    1 |  0.28% |     4228 | glen@amsl.com
  0.48% |    1 |  0.27% |     4143 | ed.lewis@neustar.biz
  0.48% |    1 |  0.27% |     4095 | sustrik@250bpm.com
  0.48% |    1 |  0.26% |     3999 | ogud@ogud.com
  0.48% |    1 |  0.24% |     3621 | geoff.ietf@mulligan.com
--------+------+--------+----------+------------------------
100.00% |  209 |100.00% |  1525624 | Total

From rogerj@gmail.com  Fri Jul  8 00:16:27 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 811BA21F88E5; Fri,  8 Jul 2011 00:16:27 -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.000,  BAYES_00=-2.599, J_CHICKENPOX_13=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 PWuJU2pUJ8la; Fri,  8 Jul 2011 00:16:26 -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 C24C321F88E6; Fri,  8 Jul 2011 00:16:25 -0700 (PDT)
Received: by wyj26 with SMTP id 26so1290661wyj.31 for <multiple recipients>; Fri, 08 Jul 2011 00:16:24 -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:content-transfer-encoding; bh=JhDmquOv7EhaxNssIRxk/fmeOwqs1vqPuXJ3WEeYjNs=; b=SXGptf+uYQiOgtYI8nWszBfnbtrikjrevet5QDC3lzLNhhUFjhh5Wo1rd8+pEEZoRG 8EGm0fio0O4yXZVNIr0S9DDZ2RIF02N1Iv7ftGp5JiXNwySHwBOx03kmwQLx3kYrEwoI GlX8Q034sJa1V9nWsVoPHai/DkvbuRm7zLgCQ=
MIME-Version: 1.0
Received: by 10.227.160.140 with SMTP id n12mr1440430wbx.69.1310109384557; Fri, 08 Jul 2011 00:16:24 -0700 (PDT)
Received: by 10.227.142.137 with HTTP; Fri, 8 Jul 2011 00:16:24 -0700 (PDT)
In-Reply-To: <CAKFn1SGvL2KQ3KVoR6cE8Q=Mqb+zjXL_uVAhdic_nOHC=f_q1A@mail.gmail.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKFn1SGvL2KQ3KVoR6cE8Q=Mqb+zjXL_uVAhdic_nOHC=f_q1A@mail.gmail.com>
Date: Fri, 8 Jul 2011 09:16:24 +0200
Message-ID: <CAKFn1SEGVahkCSmVt0-QPAxFSVftpvcwCNcpnznfQiPyBH1Jww@mail.gmail.com>
Subject: Re: draft-ietf-v6ops-6to4-to-historic
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Ronald Bonica <rbonica@juniper.net>, IETF Discussion <ietf@ietf.org>,  "v6ops@ietf.org" <v6ops@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2011 07:16:27 -0000

Guess I should clearify something, the thing I am considering are to
drop all 2002::/16 addresses hard, of course preferable return a
correct error messages to.

wonder how many find 6to4 usable when ISPs start doing that? Nuclear
winter or not may follow.



--- Roger J ---

On Sun, Jul 3, 2011 at 9:32 PM, Roger J=F8rgensen <rogerj@gmail.com> wrote:
> A bit late since this threat will be moderated soon. But I strongly objec=
t
> to this delay of needed action.
>
> I guess the other way the problem, which will hurt muchmuch more is maybe=
 to
> considering a filter of 6to4 on isp level?
> I will suggest it when we start deploying native ipv6.
>
> --- Roger J. ---
>
> On Jul 2, 2011 6:39 PM, "Ronald Bonica" <rbonica@juniper.net> wrote:
>> Folks,
>>
>> Whereas there has been considerable controversy regarding
>> draft-ietf-v6ops-6to4-to-historic, the v6ops chairs and document author =
have
>> agreed to the following course of action:
>>
>> - the V6OPS WG will withdraw its request to publish
>> draft-ietf-v6ops-6to4-to-historic
>> - The author will introduce a new draft, intended for standards track
>> publication. The new draft will update RFCs 3056 and 3068. It will say t=
hat
>> if 6-to-4 is implemented, it must be turned off by default.
>> - In order for the new draft to be published, it must achieve both V6OPS
>> WG and IETF consensus
>>
>> If anyone objects to this course of action, please speak up soon.
>>
>> Ron
>> <Speaking as OPS Area AD>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>



--=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 rogerj@gmail.com  Fri Jul  8 00:46:03 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 DA7BA21F8785; Fri,  8 Jul 2011 00:46:03 -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=[AWL=0.300,  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 ZVw7mMVe2n-B; Fri,  8 Jul 2011 00:46:03 -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 CB6DE21F8783; Fri,  8 Jul 2011 00:46:02 -0700 (PDT)
Received: by wwe5 with SMTP id 5so1121525wwe.13 for <multiple recipients>; Fri, 08 Jul 2011 00:46:01 -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:content-transfer-encoding; bh=10KdA6BB7YTziXhvMqyGI62wfRhWPh8GL5XxYDwUtnY=; b=uQh/OqMyQg0zYDHG/JBiMWUvHJLdiUJclSuVpMkuXYkKMhqNvIy5WqxUZEPGKphNJX tb3BNyVstVFgTkcLLPzTCyhmN6IFJV9rl00gNA+31DE/y7LsOeZv4EH27l4iV/3CFOBs dIZj8eAGAC/lVzrZpNlecqjYBfCN7hCiEfvwY=
MIME-Version: 1.0
Received: by 10.227.55.136 with SMTP id u8mr966304wbg.99.1310111161085; Fri, 08 Jul 2011 00:46:01 -0700 (PDT)
Received: by 10.227.142.137 with HTTP; Fri, 8 Jul 2011 00:46:00 -0700 (PDT)
In-Reply-To: <4E0BE5FF.3000409@gont.com.ar>
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar> <BANLkTinuPcq2r85kzMctFCHDB3Ta=WgA4A@mail.gmail.com> <4E0BE5FF.3000409@gont.com.ar>
Date: Fri, 8 Jul 2011 09:46:00 +0200
Message-ID: <CAKFn1SF6yZK4wW==yK+7g+OzFnOFxGHT=FW-bXzYPOtxMWrF5g@mail.gmail.com>
Subject: Re: HOMENET working group proposal
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Fernando Gont <fernando@gont.com.ar>, Cameron Byrne <cb.list6@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: 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: Fri, 08 Jul 2011 07:46:04 -0000

On Thu, Jun 30, 2011 at 4:57 AM, Fernando Gont <fernando@gont.com.ar> wrote=
:
> 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=
.

A very good point, there are a few network that break e2e on purpose.
But I guess this mostly affect enterprises and not the general
Internet part, and still I would guess that the network on the
"inside" for those enterprises still use e2e quite heavily so it's
still relevant.



--=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 ichiroumakino@gmail.com  Fri Jul  8 02:00:30 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 D710A21F884B; Fri,  8 Jul 2011 02:00:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.849
X-Spam-Level: 
X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_13=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 HJAsOtZlAIyE; Fri,  8 Jul 2011 02:00: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 8A43D21F884A; Fri,  8 Jul 2011 02:00:29 -0700 (PDT)
Received: by bwb17 with SMTP id 17so1813650bwb.31 for <multiple recipients>; Fri, 08 Jul 2011 02:00:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=VLamD7OQ1HS6dL9n0MIrxBJsb7xL0BhL/0qiYkZxWug=; b=W8Vlm4s8xYRYeDfBz3HCp14/5HU6bMDQdpEOUiKpJmlm0vse86dDsksJNmxF575DJI U1kMCjIHT6o2kqXyZZtUlKHkyuYf6XkST0NODmcp1ZBsAXPjp7kRU9gyn553fNMF41a5 XMbjzqMOh+LXvRpvSYnTKzINEYB1R5S6m9CxU=
Received: by 10.204.20.65 with SMTP id e1mr1339593bkb.149.1310115628659; Fri, 08 Jul 2011 02:00:28 -0700 (PDT)
Received: from [192.168.2.102] (ip-98-56-72-178.dialup.ice.net [178.72.56.98]) by mx.google.com with ESMTPS id i8sm155580bke.47.2011.07.08.02.00.25 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 08 Jul 2011 02:00:27 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Subject: Re: draft-ietf-v6ops-6to4-to-historic
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Ole Troan <otroan@employees.org>
In-Reply-To: <CAKFn1SEGVahkCSmVt0-QPAxFSVftpvcwCNcpnznfQiPyBH1Jww@mail.gmail.com>
Date: Fri, 8 Jul 2011 11:00:22 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <CE6513DD-5408-457E-B3B5-609716BC2809@employees.org>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKFn1SGvL2KQ3KVoR6cE8Q=Mqb+zjXL_uVAhdic_nOHC=f_q1A@mail.gmail.com> <CAKFn1SEGVahkCSmVt0-QPAxFSVftpvcwCNcpnznfQiPyBH1Jww@mail.gmail.com>
To: =?iso-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org" <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, 08 Jul 2011 09:00:31 -0000

Roger,

> Guess I should clearify something, the thing I am considering are to
> drop all 2002::/16 addresses hard, of course preferable return a
> correct error messages to.
>=20
> wonder how many find 6to4 usable when ISPs start doing that? Nuclear
> winter or not may follow.

took me a while to warm up to PMT, but now I think that's a perfectly =
valid solution to rescue the set of innocent victims of 6to4.
=
http://tools.ietf.org/html/draft-kuarsingh-v6ops-6to4-provider-managed-tun=
nel-02

wouldn't be surprised if there already are commercial products that can =
do that.

cheers,
Ole


>=20
>=20
>=20
> --- Roger J ---
>=20
> On Sun, Jul 3, 2011 at 9:32 PM, Roger J=F8rgensen <rogerj@gmail.com> =
wrote:
>> A bit late since this threat will be moderated soon. But I strongly =
object
>> to this delay of needed action.
>>=20
>> I guess the other way the problem, which will hurt muchmuch more is =
maybe to
>> considering a filter of 6to4 on isp level?
>> I will suggest it when we start deploying native ipv6.
>>=20
>> --- Roger J. ---
>>=20
>> On Jul 2, 2011 6:39 PM, "Ronald Bonica" <rbonica@juniper.net> wrote:
>>> Folks,
>>>=20
>>> Whereas there has been considerable controversy regarding
>>> draft-ietf-v6ops-6to4-to-historic, the v6ops chairs and document =
author have
>>> agreed to the following course of action:
>>>=20
>>> - the V6OPS WG will withdraw its request to publish
>>> draft-ietf-v6ops-6to4-to-historic
>>> - The author will introduce a new draft, intended for standards =
track
>>> publication. The new draft will update RFCs 3056 and 3068. It will =
say that
>>> if 6-to-4 is implemented, it must be turned off by default.
>>> - In order for the new draft to be published, it must achieve both =
V6OPS
>>> WG and IETF consensus
>>>=20
>>> If anyone objects to this course of action, please speak up soon.
>>>=20
>>> Ron
>>> <Speaking as OPS Area AD>
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>=20
>=20
>=20
>=20
> --=20
>=20
> Roger Jorgensen           |
> rogerj@gmail.com          | - IPv6 is The Key!
> http://www.jorgensen.no   | roger@jorgensen.no
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From ichiroumakino@gmail.com  Fri Jul  8 02:03:23 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 3D03421F876E; Fri,  8 Jul 2011 02:03:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.224
X-Spam-Level: 
X-Spam-Status: No, score=-3.224 tagged_above=-999 required=5 tests=[AWL=0.375,  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 7kKbEW48HXDk; Fri,  8 Jul 2011 02:03:22 -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 4184521F872E; Fri,  8 Jul 2011 02:03:22 -0700 (PDT)
Received: by bwb17 with SMTP id 17so1815748bwb.31 for <multiple recipients>; Fri, 08 Jul 2011 02:03:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=tcQqfhDReocyCNB2rIHKjBb5qxNUed7PVnxDtX8CIM4=; b=EENQk+N0owC+X8tF/w6gOonW5s69em9oL1EUGl6/wCWLz9hpBgp5lyIbJQE9nqpjwA J0uG57CRFFqrfUthFxOd0woDeF2r3oXknA3K4ZYTENv08o2rdszVN/e92iGLu1Zupcrx iHQMrGXzCtKCOjtQLjPeZ4zesoxGy2LtcGFDQ=
Received: by 10.205.82.133 with SMTP id ac5mr251209bkc.386.1310115801381; Fri, 08 Jul 2011 02:03:21 -0700 (PDT)
Received: from [192.168.2.102] (ip-98-56-72-178.dialup.ice.net [178.72.56.98]) by mx.google.com with ESMTPS id u32sm156485bkk.49.2011.07.08.02.03.19 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 08 Jul 2011 02:03:20 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Subject: Re: 6to4 to Experimental? (was: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <4E80A8E8-7B29-426B-BB43-8FC269330E4B@network-heretics.com>
Date: Fri, 8 Jul 2011 11:03:16 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0622D8FB-2361-49C9-8E44-D70E7F1C2ADE@employees.org>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507F3A@EMBX01-WF.jnpr.net> <4E80A8E8-7B29-426B-BB43-8FC269330E4B@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org" <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, 08 Jul 2011 09:03:23 -0000

Keith,

> The alternative that I proposed to IESG and to the chairs (and never =
received any feedback about) was to reclassify 6to4 as Experimental.   =
Experimental seems completely appropriate for a protocol that is useful, =
but only in corner cases.  And I think it's also appropriate and useful =
to try to learn from the experience with 6to4, even if we realize that =
6to4 will never be a generally applicable IPv6 transition solution =
again.
>=20
> And maybe, just maybe, Experimental will be enough of a "slap" at 6to4 =
to mollify the "kill it yesterday" crowd.  For one thing, it clearly =
indicates that 6to4 is no longer a standard.
>=20
> But in order to quieten down the discussion here, I suggest that =
people reply to me privately if they can't live with this.   If I get =
lots of those replies, I'll know that it's not worth pursuing.

"Experimental" is certainly better than:
 - nothing
 - spending months on hold as appeals are processed.

cheers,
Ole=

From tjc@ecs.soton.ac.uk  Fri Jul  8 02:32:33 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 741BA21F875B for <ietf@ietfa.amsl.com>; Fri,  8 Jul 2011 02:32:33 -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 Gob5DjkyTnQi for <ietf@ietfa.amsl.com>; Fri,  8 Jul 2011 02:32:32 -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 4104921F86D1 for <ietf@ietf.org>; Fri,  8 Jul 2011 02:32:32 -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 p689WRk0022887 for <ietf@ietf.org>; Fri, 8 Jul 2011 10:32:27 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p689WRk0022887
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1310117547; bh=watmIS6EDjJcsYNTEDwo20fe4sQ=; h=Subject:References:From:In-Reply-To:Date:To:Mime-Version; b=DQgFIIMsHVzpSijAGAf9MjZtGhWmKV7BU/Yrygaw/Da4a9NZuITjJERpw+GEDzeNl f7PsNJPCCdMfKM6FRfMwAC+EuZytZQUfZlmnj+6Vj+C5u1cUXZwN09bEob+mvx/Jty Zh9rR58ojhZo2sBWjCyOWSAAJjgEPI5SF8S+JivE=
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 n67AWR0366161603pc ret-id none; Fri, 08 Jul 2011 10:32:27 +0100
Received: from [144.82.91.229] (dhcp-91-229.eduroam.ucl.ac.uk [144.82.91.229]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p689WKdE026527 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Fri, 8 Jul 2011 10:32:20 +0100
Subject: Re: reading drafts on an ipad
References: <061F84F2-E9A8-4A37-A506-7605391D837D@cisco.com> <4E151BA5.4070608@net-zen.net> <F4227BBA-507F-484A-B7A2-8DB71D827991@ecs.soton.ac.uk>
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: text/plain; charset=us-ascii
X-Mailer: iPad Mail (8J2)
In-Reply-To: <4E151BA5.4070608@net-zen.net>
Message-ID: <EMEW3|99b6d3955949fde5ff1d655f2f32ff2an67AWR03tjc|ecs.soton.ac.uk|F4227BBA-507F-484A-B7A2-8DB71D827991@ecs.soton.ac.uk>
Date: Fri, 8 Jul 2011 10:32:18 +0100
To: IETF-Discussion list <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (iPad Mail 8J2)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n67AWR036616160300; tid=n67AWR0366161603pc; 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: p689WRk0022887
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: Fri, 08 Jul 2011 09:32:33 -0000

On 7 Jul 2011, at 03:36, Glen Zorn <gwz@net-zen.net> wrote:

> On 7/6/2011 10:38 PM, Cullen Jennings wrote:
>=20
>> Has anyone found a particularly good solution to reading drafts on an ipa=
d? What about markup and notes on drafts?
>=20
> The iPad is a porn toy; get a real computer.

You could save drafts as PDF and use GoodReader, which is a very nice app, t=
o annotate comments, etc.  You can also fit a lot of drafts on a free DropBo=
x account, which GoodReader works fine with.

Tim=

From moore@network-heretics.com  Fri Jul  8 06:03: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 4542E21F8828; Fri,  8 Jul 2011 06:03:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.365
X-Spam-Level: 
X-Spam-Status: No, score=-3.365 tagged_above=-999 required=5 tests=[AWL=-0.066, 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 Z+MLeXXUcMmv; Fri,  8 Jul 2011 06:03:01 -0700 (PDT)
Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id A787021F8800; Fri,  8 Jul 2011 06:03:01 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 8782820BE3; Fri,  8 Jul 2011 09:03:00 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute3.internal (MEProxy); Fri, 08 Jul 2011 09:03: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=avnufLw1wkfZ6LBpBn5e8eDaejU=; b=G/7nxB4pLsJgTyhvK05OYtNDTNg2t8bKune2Wo8jpBl8vu0aWkSYqGYWbmKOSEoSghooudevT3LRqBrh8Y4A+EoJM+2WXbd+X0WFSRpPKNpRAb/buTxWSx3an20vQOw1u/ILRkLl/InP/sOX9Tmxacsfe6+08XqGl2uM+rDNRAI=
X-Sasl-enc: A/qraeRvgvPQoF83jwcr0r2D+fqRXfnGmcfvL2VbMhe3 1310130180
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 9728B4423CC; Fri,  8 Jul 2011 09:02:59 -0400 (EDT)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic
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: <CAKFn1SEGVahkCSmVt0-QPAxFSVftpvcwCNcpnznfQiPyBH1Jww@mail.gmail.com>
Date: Fri, 8 Jul 2011 09:02:58 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E3F939A5-373D-4BA4-9E45-60DDF9D589C3@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKFn1SGvL2KQ3KVoR6cE8Q=Mqb+zjXL_uVAhdic_nOHC=f_q1A@mail.gmail.com> <CAKFn1SEGVahkCSmVt0-QPAxFSVftpvcwCNcpnznfQiPyBH1Jww@mail.gmail.com>
To: =?iso-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org" <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, 08 Jul 2011 13:03:02 -0000

On Jul 8, 2011, at 3:16 AM, Roger J=F8rgensen wrote:

> Guess I should clearify something, the thing I am considering are to
> drop all 2002::/16 addresses hard, of course preferable return a
> correct error messages to.
>=20
> wonder how many find 6to4 usable when ISPs start doing that? Nuclear
> winter or not may follow.

seems like that just exacerbates the problem for your own customers and =
for other operators.

Keith


From turchanyi.geza@gmail.com  Fri Jul  8 06:12:52 2011
Return-Path: <turchanyi.geza@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0DF121F872E; Fri,  8 Jul 2011 06:12:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.332
X-Spam-Level: 
X-Spam-Status: No, score=-1.332 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7JAdzwmyFw26; Fri,  8 Jul 2011 06:12:52 -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 C47FA21F8672; Fri,  8 Jul 2011 06:12:51 -0700 (PDT)
Received: by vws12 with SMTP id 12so1829842vws.31 for <multiple recipients>; Fri, 08 Jul 2011 06:12:51 -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=ZLQIyLrEijf4Y/r5jVZaFdkekG4UkxpXnEfQePgVkYQ=; b=ceTsLneUU+i58rJJxnexB1f7TZsKW8FtToJE6tLenGWfOP5+kCttJq3h7dvrv/xnh0 AoXUZulFPtcUUAp/q4/kchyRASwXNj+aRN2zLpA3gYnIGBjWiHmDNF/NtvH88ub/wfpB 7rp5WvPqB2VqHcuMKgLokG8i5JmIfoJUJh9XU=
MIME-Version: 1.0
Received: by 10.52.107.33 with SMTP id gz1mr1820920vdb.153.1310130770058; Fri, 08 Jul 2011 06:12:50 -0700 (PDT)
Received: by 10.52.101.170 with HTTP; Fri, 8 Jul 2011 06:12:49 -0700 (PDT)
In-Reply-To: <alpine.BSF.2.00.1107081105430.63146@mignon.ki.iif.hu>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507F3A@EMBX01-WF.jnpr.net> <4E80A8E8-7B29-426B-BB43-8FC269330E4B@network-heretics.com> <0622D8FB-2361-49C9-8E44-D70E7F1C2ADE@employees.org> <alpine.BSF.2.00.1107081105430.63146@mignon.ki.iif.hu>
Date: Fri, 8 Jul 2011 15:12:49 +0200
Message-ID: <CAJfR-+Or-osHQFMpoJ6Z=hygz0oumxYx4czjEv=2X70M410DnA@mail.gmail.com>
Subject: Re: [v6ops] 6to4 to Experimental? (was: Re: draft-ietf-v6ops-6to4-to-historic)
From: Turchanyi Geza <turchanyi.geza@gmail.com>
To: Mohacsi Janos <mohacsi@niif.hu>
Content-Type: multipart/alternative; boundary=bcaec547c629289dbe04a78e97df
Cc: IETF Discussion <ietf@ietf.org>, "v6ops@ietf.org" <v6ops@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, 08 Jul 2011 13:12:52 -0000

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

+1

On Fri, Jul 8, 2011 at 11:13 AM, Mohacsi Janos <mohacsi@niif.hu> wrote:

>
>
>
> On Fri, 8 Jul 2011, Ole Troan wrote:
>
>  Keith,
>>
>>  The alternative that I proposed to IESG and to the chairs (and never
>>> received any feedback about) was to reclassify 6to4 as Experimental.
>>> Experimental seems completely appropriate for a protocol that is useful, but
>>> only in corner cases.  And I think it's also appropriate and useful to try
>>> to learn from the experience with 6to4, even if we realize that 6to4 will
>>> never be a generally applicable IPv6 transition solution again.
>>>
>>> And maybe, just maybe, Experimental will be enough of a "slap" at 6to4 to
>>> mollify the "kill it yesterday" crowd.  For one thing, it clearly indicates
>>> that 6to4 is no longer a standard.
>>>
>>> But in order to quieten down the discussion here, I suggest that people
>>> reply to me privately if they can't live with this.   If I get lots of those
>>> replies, I'll know that it's not worth pursuing.
>>>
>>
>> "Experimental" is certainly better than:
>> - nothing
>> - spending months on hold as appeals are processed.
>>
>
> I proposed experimental also when discussion started about future of 6to4.
> I support the idea.
>        Best Regards,
>                Janos Mohacsi
>
>
> ______________________________**_________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/**listinfo/v6ops<https://www.ietf.org/mailman/listinfo/v6ops>
>

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

+1<br><br><div class=3D"gmail_quote">On Fri, Jul 8, 2011 at 11:13 AM, Mohac=
si Janos <span dir=3D"ltr">&lt;<a href=3D"mailto:mohacsi@niif.hu">mohacsi@n=
iif.hu</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"><br>
<br>
<br>
On Fri, 8 Jul 2011, Ole Troan wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Keith,<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The alternative that I proposed to IESG and to the chairs (and never receiv=
ed any feedback about) was to reclassify 6to4 as Experimental. =A0 Experime=
ntal seems completely appropriate for a protocol that is useful, but only i=
n corner cases. =A0And I think it&#39;s also appropriate and useful to try =
to learn from the experience with 6to4, even if we realize that 6to4 will n=
ever be a generally applicable IPv6 transition solution again.<br>

<br>
And maybe, just maybe, Experimental will be enough of a &quot;slap&quot; at=
 6to4 to mollify the &quot;kill it yesterday&quot; crowd. =A0For one thing,=
 it clearly indicates that 6to4 is no longer a standard.<br>
<br>
But in order to quieten down the discussion here, I suggest that people rep=
ly to me privately if they can&#39;t live with this. =A0 If I get lots of t=
hose replies, I&#39;ll know that it&#39;s not worth pursuing.<br>
</blockquote>
<br>
&quot;Experimental&quot; is certainly better than:<br>
- nothing<br>
- spending months on hold as appeals are processed.<br>
</blockquote>
<br></div>
I proposed experimental also when discussion started about future of 6to4. =
I support the idea.<br>
 =A0 =A0 =A0 =A0Best Regards,<br><font color=3D"#888888">
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Janos Mohacsi</font><div><div></div><div cl=
ass=3D"h5"><br>
<br>
______________________________<u></u>_________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" target=3D"_blank">h=
ttps://www.ietf.org/mailman/<u></u>listinfo/v6ops</a><br>
</div></div></blockquote></div><br>

--bcaec547c629289dbe04a78e97df--

From jdrake@juniper.net  Fri Jul  8 06:30:28 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 BD5DA21F8A72; Fri,  8 Jul 2011 06:30:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.439
X-Spam-Level: 
X-Spam-Status: No, score=-5.439 tagged_above=-999 required=5 tests=[AWL=0.560,  BAYES_00=-2.599, J_CHICKENPOX_21=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 gDaWHTjiaYWR; Fri,  8 Jul 2011 06:30:27 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id B9BBD21F8A6A; Fri,  8 Jul 2011 06:30:26 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKThcGaHkJNGMWt8NOt5gFakIFFvy/IzGv@postini.com; Fri, 08 Jul 2011 06:30:26 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; Fri, 8 Jul 2011 06:25:57 -0700
From: John E Drake <jdrake@juniper.net>
To: "neil.2.harrison@bt.com" <neil.2.harrison@bt.com>, "RCosta@ptinovacao.pt" <RCosta@ptinovacao.pt>, "david.i.allan@ericsson.com" <david.i.allan@ericsson.com>, "stbryant@cisco.com" <stbryant@cisco.com>
Date: Fri, 8 Jul 2011 06:25:55 -0700
Subject: RE: [mpls] Last	Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication	for	MPLS	Transport	Profile) to Proposed Standard
Thread-Topic: [mpls] Last	Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication	for	MPLS	Transport	Profile) to Proposed Standard
Thread-Index: Acw3LJ0GTOqQfPcUQOGUhgK/1kXgjgDPfXWgACJLxEAAkhZucAANiFrQ
Message-ID: <5E893DB832F57341992548CDBB333163A0A8FAF79B@EMBX01-HQ.jnpr.net>
References: <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B6BC@INOAVREX11.ptin.corpPT.com> <6D3D47CB84BDE349BC23BF1C94E316E4405A7550DE@EMV62-UKRD.domain1.systemhost.net>
In-Reply-To: <6D3D47CB84BDE349BC23BF1C94E316E4405A7550DE@EMV62-UKRD.domain1.systemhost.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: "mpls@ietf.org" <mpls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "ietf-announce@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: Fri, 08 Jul 2011 13:30:28 -0000

Neil,

I have a question for clarification.  Have you actually read draft-ietf-mpl=
s-tp-cc-cv-rdi-05.txt?  I know you don't like doing this but generally it i=
s considered good form to read something before commenting on it.

Thanks,

John

Sent from my iPhone


> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> neil.2.harrison@bt.com
> Sent: Friday, July 08, 2011 12:16 AM
> To: RCosta@ptinovacao.pt; david.i.allan@ericsson.com;
> stbryant@cisco.com
> Cc: mpls@ietf.org; ietf@ietf.org; ietf-announce@ietf.org
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote
> Defect indication for MPLS Transport Profile) to Proposed Standard
>
> Got to say I agree with Rui on much of what he says here.  And I
> absolutely resonate with his point on the need for simplicity.  The
> reason OAM needs to be as simple as possible is because it must be
> super reliable....we do not want to consciously build in weaknesses,
> esp unnecessary ones.... this also implies minimal config.  We could
> all do better on this.  For example:
>
> -       Rui is dead right a CC function is fairly useless, we only need
> a CV function...the ATM OAM in I.610 suffers from this problem (and few
> others like AIS and the assumed use of request/response MLT to diagnose
> leaking/mismerging traffic...request/response OAM won't work with
> unidirectional defects).
>
> -       all packet layer networks should not have an AIS OAM
> message....very obvious for the cl-ps mode of course.  The co-ps mode
> is also not like the co-cs mode.  One has to consciously manufacture
> AIS messages and target them to specific clients in the co-ps
> mode....who may have taken action in their own layer network and 'moved
> elsewhere' anyway, ie a total waste of time now.  AIS is actually
> unnecessary wrt providing information anyway, it simply represents an
> in-built weakness of just something else to go wrong which itself will
> create problems.
>
> -       creating preconfigured TCM sublayers is just asking for trouble
> IMO.  It is far smarter to simply create a single end-end OAM CV (and
> when required PM) flow and tap this off at intermediate nodes on the
> *rare* occasions one wants to do.
>
> regards, Neil
>
> This email contains BT information, which may be privileged or
> confidential.
> It's meant only for the individual(s) or entity named above. If you're
> not the intended
> recipient, note that disclosing, copying, distributing or using this
> information
> is prohibited. If you've received this email in error, please let me
> know immediately
> on the email address above. Thank you.
> We monitor our email system, and may record your emails.
> British Telecommunications plc
> Registered office: 81 Newgate Street London EC1A 7AJ
> Registered in England no: 1800000
>
>
>
>
>
>
>
> > -----Original Message-----
> > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
> Of
> > Rui Costa
> > Sent: 08 July 2011 01:15
> > To: David Allan I; Stewart Bryant
> > Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
> > Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> > (Proactive Connectivity Verification, Continuity Check and Remote
> > Defect indication for MPLS Transport Profile) to Proposed Standard
> >
> > David,
> >
> > Reading something, keeping it on record, without effect in the draft
> > and "ignoring comments" have IMHO similar outcomes. As author of the
> > draft you are free to do it. These standards have a great impact in
> our
> > work, so i'm also free to write what i did.
> >
> >
> >
> >
> > Stewart,
> >
> > My technical concerns regarding this draft were expressed...
> > ...in the (ITU-T -> IETF, Feb/2011) liaison regarding it (LS281, i
> > believe);
> > ...in operators' meetings' that took place during ITU-T's Feb/2011
> > plenary meeting;
> > ...in a comparison session that took place during that same ITU-T
> > meeting.
> > Some:
> >
> > CC/CV
> > I don't understand the need for 2 types of packets: a single type
> > allows CC; mismatching identifiers in the same CC packets allow CV.
> > Besides adding complexity, we whether always activate both or
> > potentiate undetected mismerges.
> > (BTW: can't understand how we propose one ACH codepoint to CC,
> another
> > for CV, [counting other drafts, another for frame loss ...] but don't
> > consider assigning 1 single ACH protocol identifier codepoint as
> > requested by ITU-T)
> >
> > Uni P2P / P2MP
> > I can't see how BFD will support unidir and hence P2MP other than...
> >
> > ...eliminating the session "state variable" (down, init, up), aiming
> > just the state variables we really need, bringing us to something
> > similar to 1731, eventually with other bits on the wire or...
> > ...using IP to create the reverse way, which we cannot assume per
> > requirements;
> > Will we create a complete different tool for that?
> > (BFD's B=3D"bidirectional")
> >
> > Provisioning list
> > This is an MPLS profile/subset (and i heard) achievable through a
> > particular configuration. So, i expect each draft-ietf-mpls-TP-* to
> > focus on that profile/configuration. However, i keep seeing
> references
> > f.i. to IP encapsulations unexpected under TP's OAM.
> > I don't thus understand what the aim is: do we expect this in TP, are
> > we talking about MPLS in general?... The TP profile is never quite
> > delimited.
> > Does chapter 4 contain ALL the configurable parameters list agreed to
> > provide in the comparison session?
> >
> > Backwards compatibility
> > This was the main argument risen to ground MPLS-TP OAM on BFD. It's
> not
> > a better argument than grounding MPLS-TP OAM on 1731 due to its ETH
> > deployment plus coherence with SDH, OTN, as defended by ITU-T.
> > For reasons like the above, however, MPLS-TP BFD won't be backwards
> > compatible with previous BFD (even considering just CC/CV). They
> don't
> > even share the same codepoint.
> >
> > Simplicity
> > Whether we look to PDH, SDH, OTN or ETH, ITU-T's approach to CC is
> > simpler: in each flow, a standard defined nr of constant heartbeat
> > signals (with standard constant or provisioned period - no
> > auto/negotiated -) means OK. A standard defined number of misses
> means
> > lost Rx connection. An RDI, the only articulation between Rx and Tx
> > flows, meaningful in bidirectional applications, allows each pear to
> > identify Tx problems.
> > This OAM simplicity is the key for reliable fail finger pointing,
> > performance reports and protection. Also to allow scaling, more
> > implementation opportunities/manufacturers, which is valuable for
> > operators.
> >
> >
> > IMHO, between your MPLS-TP view and MPLS/IP, it becomes more and more
> > difficult to tell which is which.
> >
> > Regards,
> > Rui
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: David Allan I [mailto:david.i.allan@ericsson.com]
> > Sent: quarta-feira, 6 de Julho de 2011 19:25
> > To: erminio.ottone_69@libero.it; Rui Costa; ietf@ietf.org; IETF-
> > Announce
> > Cc: mpls@ietf.org
> > Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> > 05.txt> (Proactive Connectivity Verification, Continuity Check and
> > Remote Defect indication for MPLS Transport Profile) to Proposed
> > Standard
> >
> > Hi Erminio:
> >
> > <snipped>
> > >Several service providers regarded this draft as not meeting their
> > >transport networks' needs.
> >
> > E> This is a true statement: the solution in this draft is useless
> for
> > many MPLS- TP deployments.
> >
> > The two statements do not necessarily follow.
> >
> > What we established during discussions at the SG15 plenary in
> February
> > was that the issue some service providers had was that the IETF BFD
> > solution exceeded their requirements in that there was additional
> > functionality they did not see a need for, and that they considered
> any
> > additional functionality parasitic.
> >
> > However this is a consequence of adapting an existing technology to a
> > new application. I do not see any way around that. And the entire
> joint
> > project was based on the premise of engineering re-use not greenfield
> > design. That is what it said on the tin up front, and IMO why when
> the
> > IETF started down this path packet transport transitioned from being
> a
> > minority sport to mainstream, so it is a bit late to cry foul....
> >
> > My 2 cents
> > Dave
> >
> >
> >
> >
> > -----Original Message-----
> > From: David Allan I [mailto:david.i.allan@ericsson.com]
> > Sent: quarta-feira, 6 de Julho de 2011 18:36
> > To: erminio.ottone_69@libero.it; loa@pi.nu; Rui Costa
> > Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
> > Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> > 05.txt> (Proactive Connectivity Verification, Continuity Check and
> > Remote Defect indication for MPLS Transport Profile) to Proposed
> > Standard
> >
> > Hi Erminio:
> >
> > Two of the three document editors were present at SG15 plenary in
> > February where the comments originated. The revised meeting schedule
> > resulted in a day spent going through the document with the editors.
> > IMO there were lots of discussion and legitimate issues with the
> > document identified and corrected so it was a useful session. The
> > liaison of same was in many ways *after the fact*.
> >
> > Cheers
> > Dave
> >
> >
> >
> >
> > -----Original Message-----
> > From: erminio.ottone_69@libero.it
> [mailto:erminio.ottone_69@libero.it]
> > Sent: quarta-feira, 6 de Julho de 2011 18:34
> > To: Rui Costa; ietf@ietf.org; IETF-Announce
> > Cc: mpls@ietf.org
> > Subject: R: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> 05.txt>
> > (Proactive Connectivity Verification, Continuity Check and Remote
> > Defect indication for MPLS Transport Profile) to Proposed Standard
> >
> > The way this draft has been developed is a bit strange.
> >
> > The poll for its adoption as a WG document was halted by the MPLS WG
> > chair
> > because "it is not possible to judge consensus":
> >
> > http://www.ietf.org/mail-archive/web/mpls/current/msg04502.html
> >
> > The lack of consensus was motivated by serious technical concerns
> > raised by
> > several transport experts during the poll.
> >
> > Nevertheless the MPLS WG chair decided to adopt the draft as a WG
> > document:
> >
> > http://www.ietf.org/mail-archive/web/mpls/current/msg04512.html
> >
> > After several WG revisions and WG LCs, the technical issues have not
> > been
> > resolved.
> >
> > >Several service providers regarded this draft as not meeting their
> > transport
> > networks' needs.
> >
> > This is a true statement: the solution in this draft is useless for
> > many MPLS-
> > TP deployments.
> >
> >
> > -----Original Message-----
> > From: erminio.ottone_69@libero.it
> [mailto:erminio.ottone_69@libero.it]
> > Sent: quarta-feira, 6 de Julho de 2011 18:26
> > To: loa@pi.nu; Rui Costa
> > Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
> > Subject: R: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> 05.txt>
> > (Proactive Connectivity Verification, Continuity Check and Remote
> > Defect indication for MPLS Transport Profile) to Proposed Standard
> >
> > >  Version -04 of the document was published June 28th.
> > >
> > >  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
> > >  June 29th.
> > >
> >
> > So when the WG LC to confirm the LC comment resolution has been
> > launched?
> >
> > The proto write-up says:
> >
> >             It has also passed a working roup call to verify that LC
> > comments
> > were correctly with minor comments.
> >
> > It also says:
> >
> >             The comments has been
> >             carefully discussed between the authors and people making
> > the
> > comments and
> >             has been resolved.
> >
> > But it seems that some comments have not been discussed with the
> > authors of
> > the comments. When ITU-T Q10/15 has been involved in discussing its
> > comments?
> >
> >
> >
> >
> > -----Original Message-----
> > From: Loa Andersson [mailto:loa@pi.nu]
> > Sent: quarta-feira, 6 de Julho de 2011 16:44
> > To: Rui Costa
> > Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
> > Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> > (Proactive Connectivity Verification, Continuity Check and Remote
> > Defect indication for MPLS Transport Profile) to Proposed Standard
> >
> > All,
> >
> > Since someone has commented about the process used for resolving
> > questions on
> > draft-ietf-mpls-tp-cc-cv-rdi I am supplying some details below.
> >
> > The history of draft-ietf-mpls-tp-cc-cv-rdi working group review
> > process is:
> >
> > On February 3rd 2011 the working group last call was issued
> > on version -03
> >
> >       This was copied to the the Ad Hoc Team List
> >       and liaised to SG15 also on February 3rd
> >
> >       This working group last call ended om Feb 28
> >
> >
> >       On Feb 28 we also received a liaison with comments from SG15
> >
> >
> > The authors compiled a list of all comments received  as part the
> MPLS
> > working group last call; these  comments - and the intended
> resolution
> > -
> > is included in the meeting minutes from the Prague meeting:
> >
> >
> >       http://www.ietf.org/proceedings/80/slides/mpls-9.pdf
> >
> >
> >   During the IETF meeting in Prague, we agreed with the BFD working
> >   group to do a separate working group last callfor the BFD working
> >   group
> >
> > The (BFD) working group last call was started on March 30th and ran
> > for 13 days. The last call ended on April 11th.
> >
> >   The authors have since worked hard to resolve comments, some
> >   issue has been brought to the working group mailing list for
> >   resolution.
> >
> >   Version -04 of the document was published June 28th.
> >
> >   The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
> >   June 29th.
> >
> >   The AD review resulted in a "New ID needed" due to mostly editorial
> >   comments. Version -05 was published on June 29 and the IETF last
> call
> >   started as soon as the new ID was avaialbe.
> >
> >   The current list of Last Call Comments resoltion is also avaiable
> at:
> >   http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
> >
> >   The list of issues that the authors kept very carefully, shows
> > without
> > doubt
> >   that no comments been ignored.
> >
> >   Loa
> >   mpls wg document shepherd
> >
> >
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: David Allan I [mailto:david.i.allan@ericsson.com]
> > Sent: quarta-feira, 6 de Julho de 2011 14:58
> > To: Rui Costa; ietf@ietf.org; IETF-Announce
> > Cc: mpls@ietf.org
> > Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> > (Proactive Connectivity Verification, Continuity Check and Remote
> > Defect indication for MPLS Transport Profile) to Proposed Standard
> >
> > Hi Rui:
> >
> > The comments were not ignored, the resolution of the Q10 comments as
> > well as those collected from the MPLS WG was presented at the last
> > IETF. My spreadsheet from which that report was generated and has
> been
> > augmented to include the BFD WG comments is available at
> > http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
> >
> > So you know...
> > Dave
> >
> >
> > -----Original Message-----
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
> Of
> > Rui Costa
> > Sent: segunda-feira, 4 de Julho de 2011 23:03
> > To: ietf@ietf.org; IETF-Announce
> > Cc: mpls@ietf.org
> > Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> > (Proactive Connectivity Verification, Continuity Check and Remote
> > Defect indication for MPLS Transport Profile) to Proposed Standard
> >
> > IMHO and for the record:
> >
> > ITU-T comments regarding this draft haven't been discussed with ITU-T
> > but were simply ignored. No LS describing these comments' resolution
> > was sent.
> >
> > Several service providers regarded this draft as not meeting their
> > transport networks' needs.
> >
> > [The v03 draft was published in Feb and went to WG LC.
> > The v04 draft addressing WG LC comments was published on the 28th
> June
> > (same date as the proto write-up).
> > When was the WG LC launched, to verify LC comments resolution?]
> >
> > Regards,
> > Rui
> >
> >
> > -----Original Message-----
> > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
> Of
> > The IESG
> > Sent: quinta-feira, 30 de Junho de 2011 14:47
> > To: IETF-Announce
> > Cc: mpls@ietf.org
> > Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> > (Proactive Connectivity Verification, Continuity Check and Remote
> > Defect indication for MPLS Transport Profile) to Proposed Standard
> >
> >
> > The IESG has received a request from the Multiprotocol Label
> Switching
> > WG
> > (mpls) to consider the following document:
> > - 'Proactive Connectivity Verification, Continuity Check and Remote
> >    Defect indication for MPLS Transport Profile'
> >   <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally, comments
> may
> > be
> > sent to iesg@ietf.org instead. In either case, please retain the
> > beginning of the Subject line to allow automated sorting.
> >
> > Abstract
> >
> >    Continuity Check, Proactive Connectivity Verification and Remote
> >    Defect Indication functionalities are required for MPLS-TP OAM.
> >
> >    Continuity Check monitors the integrity of the continuity of the
> >    label switched path for any loss of continuity defect.
> Connectivity
> >    verification monitors the integrity of the routing of the label
> >    switched path between sink and source for any connectivity issues.
> >    Remote defect indication enables an End Point to report, to its
> >    associated End Point, a fault or defect condition that it detects
> on
> >    a pseudo wire, label switched path or Section.
> >
> >    This document specifies methods for proactive continuity check,
> >    continuity verification, and remote defect indication for MPLS-TP
> >    label switched paths, pseudo wires and Sections using
> Bidirectional
> >    Forwarding Detection.
> >
> >
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
> >
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls
> >
> >
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

From swallow@cisco.com  Fri Jul  8 06:39:49 2011
Return-Path: <swallow@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 A059F21F8A9D; Fri,  8 Jul 2011 06:39:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.901
X-Spam-Level: 
X-Spam-Status: No, score=-104.901 tagged_above=-999 required=5 tests=[AWL=-2.301, 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 5sg7HY5rTjS2; Fri,  8 Jul 2011 06:39:48 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id A114721F86D6; Fri,  8 Jul 2011 06:39:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=swallow@cisco.com; l=4678; q=dns/txt; s=iport; t=1310132388; x=1311341988; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version:content-transfer-encoding; bh=OUwE7mFBnkEf9TjCfHl/rZzCLnlztl7CAqGYuq5JNkQ=; b=UIxNjv8jKy4YS89Sw29wXknLdYIXF6IfyustRYdJXgGshgv2G8lH9f5x QcsHAh1hfvuwsWGKbUNE2ZeCuiGINQW8t21s0uXv7NZv+oU1mhiIXcom9 +t3SHXCIfQxA1kdj7tPyok0Ri9OPJ26h6WML5kBEVmgcgVUIOdgKdIM2p s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAKkHF06tJXG8/2dsb2JhbABMBqdFd4h7pHCdfgKDOoJ8BIcdiy+FBota
X-IronPort-AV: E=Sophos;i="4.65,499,1304294400";  d="scan'208";a="1042446"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-3.cisco.com with ESMTP; 08 Jul 2011 13:39:48 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core2-1.cisco.com (8.14.3/8.14.3) with ESMTP id p68DdlSB007050;  Fri, 8 Jul 2011 13:39:48 GMT
Received: from xmb-rcd-106.cisco.com ([72.163.62.148]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 8 Jul 2011 08:39:47 -0500
Received: from 10.86.244.217 ([10.86.244.217]) by XMB-RCD-106.cisco.com ([72.163.62.148]) with Microsoft Exchange Server HTTP-DAV ;  Fri,  8 Jul 2011 13:39:47 +0000
User-Agent: Microsoft-Entourage/12.29.0.110113
Date: Fri, 08 Jul 2011 09:39:46 -0400
Subject: Re: R: [mpls] Last Call: <draft-ietf-mpls-tp-identifiers-06.txt> (MPLS-TP Identifiers) to Proposed Standard
From: George Swallow <swallow@cisco.com>
To: "D'Alessandro Alessandro Gerardo" <alessandro.dalessandro@telecomitalia.it>, "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <CA3C80E2.11826%swallow@cisco.com>
Thread-Topic: R: [mpls] Last Call: <draft-ietf-mpls-tp-identifiers-06.txt> (MPLS-TP Identifiers) to Proposed Standard
Thread-Index: Acw1F+fy2cc2fqAsQjWUdW71y7nF9QGmM/rQAHDyCYo=
In-Reply-To: <A1F769BC58A8B146B2EEA818EAE052A2096B4DAB82@GRFMBX702RM001.griffon.local>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-OriginalArrivalTime: 08 Jul 2011 13:39:47.0561 (UTC) FILETIME=[80EFED90:01CC3D74]
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2011 13:39:49 -0000

Alessandro -

Thanks for the comments.  Will incorporate in next rev.

...George


On 7/6/11 4:16 AM, "D'Alessandro Alessandro Gerardo"
<alessandro.dalessandro@telecomitalia.it> wrote:

> Dear all,
> I have the following comments:
>=20
> Sect 7: " A maintenance point is either a Maintenance
> Entity Group End-point (MEP) or a Maintenance Entity Group
> Intermediate Point (MIP). Maintenance points are uniquely associated
> with a MEG."
>> This is true for MEP. MIP, as currently defined, are not uniquely associ=
ated
>> with a MEG.
>=20
> Sec 7.4 " At a cross-connect point, in order to automatically generate MI=
P_IDs
> for MPLS-TP, we simply use the IF_IDs of the two interfaces which are
> cross-connected"
>> the above given definition refers to "intermediate node". It should be
>> extended to cover also the case of "end nodes" because MIPs could be loc=
ated
>> in such nodes when per-interface MEPs model is applied (e.g.
>> draft-ietf-mpls-tp-oam-framework and Yoshinori's contributions)
>> a reference to sect 4, where IF_ID are defined, should be added
>=20
> Best regards,
> Alessandro
> ------------------------------------------------------------------
> Telecom Italia
> Alessandro D'Alessandro
> Transport Innovation
> Via Reiss Romoli, 274 - 10148 Torino
> phone:  +39 011 228 5887
> mobile: +39 335 766 9607
> fax: +39 06 418 639 07
>=20
>=20
> -----Messaggio originale-----
> Da: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] Per conto di The=
 IESG
> Inviato: marted=EC 28 giugno 2011 00:16
> A: IETF-Announce
> Cc: mpls@ietf.org
> Oggetto: [mpls] Last Call: <draft-ietf-mpls-tp-identifiers-06.txt> (MPLS-=
TP
> Identifiers) to Proposed Standard
>=20
>=20
> The IESG has received a request from the Multiprotocol Label Switching WG
> (mpls) to consider the following document:
> - 'MPLS-TP Identifiers'
>   <draft-ietf-mpls-tp-identifiers-06.txt> as a Proposed Standard
>=20
> The IESG plans to make a decision in the next few weeks, and solicits fin=
al
> comments on this action. Please send substantive comments to the ietf@iet=
f.org
> mailing lists by 2011-07-11. Exceptionally, comments may be sent to
> iesg@ietf.org instead. In either case, please retain the beginning of the
> Subject line to allow automated sorting.
>=20
> Abstract
>=20
>    This document specifies an initial set of identifiers to be used in
>    the Transport Profile of Multiprotocol Label Switching (MPLS-TP).
>    The MPLS-TP requirements (RFC 5654) require that the elements and
>    objects in an MPLS-TP environment are able to be configured and
>    managed without a control plane.  In such an environment many
>    conventions for defining identifiers are possible.  This document
>    defines identifiers for MPLS-TP management and OAM functions suitable
>    to IP/MPLS conventions.
>=20
>    This document is a product of a joint Internet Engineering Task Force
>    (IETF) / International Telecommunication Union Telecommunication
>    Standardization Sector (ITU-T) effort to include an MPLS Transport
>    Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge
>    (PWE3) architectures to support the capabilities and functionalities
>    of a packet transport network as defined by the ITU-T.
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-identifiers/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-identifiers/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>=20
> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle
> persone indicate. La diffusione, copia o qualsiasi altra azione derivante
> dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualo=
ra
> abbiate ricevuto questo documento per errore siete cortesemente pregati d=
i
> darne immediata comunicazione al mittente e di provvedere alla sua
> distruzione, Grazie.
>=20
> This e-mail and any attachments is confidential and may contain privilege=
d
> information intended for the addressee(s) only. Dissemination, copying,
> printing or use by anybody else is unauthorised. If you are not the inten=
ded
> recipient, please delete this message and any attachments and advise the
> sender by return e-mail, Thanks.
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From iljitsch@muada.com  Fri Jul  8 07:45:58 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 9948721F8786; Fri,  8 Jul 2011 07:45:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.378
X-Spam-Level: 
X-Spam-Status: No, score=-102.378 tagged_above=-999 required=5 tests=[AWL=0.222, 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 gf6XQBQsShHX; Fri,  8 Jul 2011 07:45:58 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [IPv6:2001:1af8:3100:a006:1::]) by ietfa.amsl.com (Postfix) with ESMTP id D4ECA21F8874; Fri,  8 Jul 2011 07:45:57 -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 p68EkMxj018992 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 8 Jul 2011 16:46:22 +0200 (CEST) (envelope-from iljitsch@muada.com)
Subject: Re: [BEHAVE] I-D Action: draft-ietf-behave-ftp64-12.txt
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: <20110708143707.20850.68943.idtracker@ietfa.amsl.com>
Date: Fri, 8 Jul 2011 16:45:50 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E6E88C48-9922-478E-9044-73CB1CC7EA5B@muada.com>
References: <20110708143707.20850.68943.idtracker@ietfa.amsl.com>
To: "behave@ietf.orgWG WG" <behave@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: draft-ietf-behave-ftp64@tools.ietf.org, TSV Dir <tsv-dir@ietf.org>, David Harrington <ietfdbh@comcast.net>, "behave-chairs@tools.ietf.org Chairs" <behave-chairs@tools.ietf.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2011 14:45:58 -0000

On 8 jul 2011, at 16:37, internet-drafts@ietf.org wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts =
directories. This draft is a work item of the Behavior Engineering for =
Hindrance Avoidance Working Group of the IETF.

> 	Title           : An FTP ALG for IPv6-to-IPv4 translation
> 	Author(s)       : Iljitsch van Beijnum
> 	Filename        : draft-ietf-behave-ftp64-12.txt
> 	Pages           : 17
> 	Date            : 2011-07-08

I made a cosmetic change to the short title used in the page headers =
and, after this week's discussion with Rockson Li, added this sentence:

   The ALG SHOULD ignore the AUTH command and not go into transparent
   mode if the server response is in the 4xx or 5xx ranges.

See the diff between -10 and -11 for more substantitative changes as a =
result of last call comments.

So I believe we now have the final version of this draft.

Iljitsch=

From iljitsch@muada.com  Fri Jul  8 07:50:44 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 82D9021F8A6A for <ietf@ietfa.amsl.com>; Fri,  8 Jul 2011 07:50:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.396
X-Spam-Level: 
X-Spam-Status: No, score=-102.396 tagged_above=-999 required=5 tests=[AWL=0.204, 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 PMCyHIdERRcT for <ietf@ietfa.amsl.com>; Fri,  8 Jul 2011 07:50:44 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [IPv6:2001:1af8:3100:a006:1::]) by ietfa.amsl.com (Postfix) with ESMTP id DB8E621F8A67 for <ietf@ietf.org>; Fri,  8 Jul 2011 07:50:43 -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 p68EpANr019026 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 8 Jul 2011 16:51:10 +0200 (CEST) (envelope-from iljitsch@muada.com)
Subject: Re: reading drafts on an ipad
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: <061F84F2-E9A8-4A37-A506-7605391D837D@cisco.com>
Date: Fri, 8 Jul 2011 16:50:38 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <41794549-D193-43AF-86AB-27B044B12FA9@muada.com>
References: <061F84F2-E9A8-4A37-A506-7605391D837D@cisco.com>
To: Cullen Jennings <fluffy@cisco.com>
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, 08 Jul 2011 14:50:44 -0000

On 6 jul 2011, at 17:38, Cullen Jennings wrote:

> Has anyone found a particularly good solution to reading drafts on an =
ipad?=20

I saw xml2rfc now has the option to convert to epub, which would make it =
easy to read drafts on the iPad and other mobile devices, but =
unfortunately when I tried to convert a draft it didn't work.

But then we'd still need the XML or epub versions of drafts to be made =
available to all.


From wwwrun@ietfa.amsl.com  Thu Jul  7 12:21:03 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 3260611E8074; Thu,  7 Jul 2011 12:21:03 -0700 (PDT)
From: NomCom Chair <nomcom-chair@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: Nomcom 2011-2012: Timeline and Selection Seeds 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110707192103.3260611E8074@ietfa.amsl.com>
Date: Thu,  7 Jul 2011 12:21:03 -0700 (PDT)
X-Mailman-Approved-At: Fri, 08 Jul 2011 08:07:14 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jul 2011 19:21:03 -0000

Hi All,

Timeline:
The following is the current timeline for the 2011-12 Nomcom:

   * Nomcom Chair Announcement made: June 7, 2011;
   * First Call for Volunteers issued: June 10, 2011;
   * Second Call for Volunteers issued: June 24, 2011;
   * Third Call for Volunteers issued: July 04, 2011;
   * Announce date of Random Selection and seeds: July 07, 2011;
   * Call for Volunteers closes: July 10, 2011 at 23:59 EDT
   * Announcement of Qualified Volunteers: July 11, 2011;
   * Raise issues on Qualified Volunteers by 23:59 EDT: July 15, 2011;
   * Seed values available from seed sources: July 18, 2011;
   * Run random selection algorithm and publish results: July 18, 2011;
   * Start Challenge period at 09:00 EDT:  July 18, 2011;
   * End of challenge period at 09:00 EDT : July 25, 2011;
   * Final List of Nomcom members published 10:00 EDT : July 25, 2011;
   * Nomcom 2011-12 self organizes during IETF-81: July 25-29, 2011

NOTE:  This timeline will be updated to address Nomcom activity after
IETF-81 and published as soon as possible.

Seeds:
The set of seed sources that are expected to be used in selecting the
committee members are as follows:

Canadian Lottery Lotto 649
Saturday July 16, 2011 Results:
  http://diffusion.loto-quebec.com/sw3/res/asp/index.asp?l=1&pRequest=2&cProduit=4
  (7 numbers including the bonus number: numbers between 1 and 49)

US National debt ("Debt Held by the Public"), published by the
Treasury department as of Friday, July 15, 2011
  http://www.treasurydirect.gov/NP/BPDLogin?application=np 
  Last 8 digits, ignore the commas and periods

US National debt ("Intragovernmental Holdings"), published by the
Treasury department as of Friday, July 15, 2011
  http://www.treasurydirect.gov/NP/BPDLogin?application=np 
  Last 8 digits, ignore the commas and periods

Euromillions Lottery
Friday July 15, 2011 Results:
  http://www.europeanlotteryguild.com/lottery_results/euromillions_results/draw_history?results_date=2011-08-01
  (7 numbers including the star balls: 5 numbers between 1 and 50 and 2 star balls between 1 and 11)

All the seeds are to be provided as input to the RFC 3797 selection algorithm.

Suresh Krishnan
Nomcom Chair 2011-2012
Email: nomcom-chair@ietf.org, suresh.krishnan@ericsson.com

From neil.2.harrison@bt.com  Fri Jul  8 00:16:06 2011
Return-Path: <neil.2.harrison@bt.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FE3821F87B1; Fri,  8 Jul 2011 00:16:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.446
X-Spam-Level: 
X-Spam-Status: No, score=-2.446 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_21=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 eGGk2vg0nWkC; Fri,  8 Jul 2011 00:16:04 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp61.intersmtp.COM [62.239.224.234]) by ietfa.amsl.com (Postfix) with ESMTP id D2EDA21F887C; Fri,  8 Jul 2011 00:16:03 -0700 (PDT)
Received: from EVMHT61-UKRD.domain1.systemhost.net (10.36.3.127) by RDW083A005ED61.smtp-e1.hygiene.service (10.187.98.10) with Microsoft SMTP Server (TLS) id 8.3.159.2; Fri, 8 Jul 2011 08:16:01 +0100
Received: from EMV62-UKRD.domain1.systemhost.net ([169.254.1.186]) by EVMHT61-UKRD.domain1.systemhost.net ([10.36.3.127]) with mapi; Fri, 8 Jul 2011 08:16:02 +0100
From: <neil.2.harrison@bt.com>
To: <RCosta@ptinovacao.pt>, <david.i.allan@ericsson.com>, <stbryant@cisco.com>
Date: Fri, 8 Jul 2011 08:15:57 +0100
Subject: RE: [mpls] Last Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication for	MPLS	Transport	Profile) to Proposed Standard
Thread-Topic: [mpls] Last Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication for	MPLS	Transport	Profile) to Proposed Standard
Thread-Index: Acw3LJ0GTOqQfPcUQOGUhgK/1kXgjgDPfXWgACJLxEAAkhZucA==
Message-ID: <6D3D47CB84BDE349BC23BF1C94E316E4405A7550DE@EMV62-UKRD.domain1.systemhost.net>
References: <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B6BC@INOAVREX11.ptin.corpPT.com>
In-Reply-To: <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B6BC@INOAVREX11.ptin.corpPT.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 08 Jul 2011 08:07:14 -0700
Cc: mpls@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: Fri, 08 Jul 2011 07:16:06 -0000

Got to say I agree with Rui on much of what he says here.  And I absolutely=
 resonate with his point on the need for simplicity.  The reason OAM needs =
to be as simple as possible is because it must be super reliable....we do n=
ot want to consciously build in weaknesses, esp unnecessary ones.... this a=
lso implies minimal config.  We could all do better on this.  For example:

-       Rui is dead right a CC function is fairly useless, we only need a C=
V function...the ATM OAM in I.610 suffers from this problem (and few others=
 like AIS and the assumed use of request/response MLT to diagnose leaking/m=
ismerging traffic...request/response OAM won't work with unidirectional def=
ects).

-       all packet layer networks should not have an AIS OAM message....ver=
y obvious for the cl-ps mode of course.  The co-ps mode is also not like th=
e co-cs mode.  One has to consciously manufacture AIS messages and target t=
hem to specific clients in the co-ps mode....who may have taken action in t=
heir own layer network and 'moved elsewhere' anyway, ie a total waste of ti=
me now.  AIS is actually unnecessary wrt providing information anyway, it s=
imply represents an in-built weakness of just something else to go wrong wh=
ich itself will create problems.

-       creating preconfigured TCM sublayers is just asking for trouble IMO=
.  It is far smarter to simply create a single end-end OAM CV (and when req=
uired PM) flow and tap this off at intermediate nodes on the *rare* occasio=
ns one wants to do.

regards, Neil

This email contains BT information, which may be privileged or confidential=
.
It's meant only for the individual(s) or entity named above. If you're not =
the intended
recipient, note that disclosing, copying, distributing or using this inform=
ation
is prohibited. If you've received this email in error, please let me know i=
mmediately
on the email address above. Thank you.
We monitor our email system, and may record your emails.
British Telecommunications plc
Registered office: 81 Newgate Street London EC1A 7AJ
Registered in England no: 1800000







> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> Rui Costa
> Sent: 08 July 2011 01:15
> To: David Allan I; Stewart Bryant
> Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote
> Defect indication for MPLS Transport Profile) to Proposed Standard
>
> David,
>
> Reading something, keeping it on record, without effect in the draft
> and "ignoring comments" have IMHO similar outcomes. As author of the
> draft you are free to do it. These standards have a great impact in our
> work, so i'm also free to write what i did.
>
>
>
>
> Stewart,
>
> My technical concerns regarding this draft were expressed...
> ...in the (ITU-T -> IETF, Feb/2011) liaison regarding it (LS281, i
> believe);
> ...in operators' meetings' that took place during ITU-T's Feb/2011
> plenary meeting;
> ...in a comparison session that took place during that same ITU-T
> meeting.
> Some:
>
> CC/CV
> I don't understand the need for 2 types of packets: a single type
> allows CC; mismatching identifiers in the same CC packets allow CV.
> Besides adding complexity, we whether always activate both or
> potentiate undetected mismerges.
> (BTW: can't understand how we propose one ACH codepoint to CC, another
> for CV, [counting other drafts, another for frame loss ...] but don't
> consider assigning 1 single ACH protocol identifier codepoint as
> requested by ITU-T)
>
> Uni P2P / P2MP
> I can't see how BFD will support unidir and hence P2MP other than...
>
> ...eliminating the session "state variable" (down, init, up), aiming
> just the state variables we really need, bringing us to something
> similar to 1731, eventually with other bits on the wire or...
> ...using IP to create the reverse way, which we cannot assume per
> requirements;
> Will we create a complete different tool for that?
> (BFD's B=3D"bidirectional")
>
> Provisioning list
> This is an MPLS profile/subset (and i heard) achievable through a
> particular configuration. So, i expect each draft-ietf-mpls-TP-* to
> focus on that profile/configuration. However, i keep seeing references
> f.i. to IP encapsulations unexpected under TP's OAM.
> I don't thus understand what the aim is: do we expect this in TP, are
> we talking about MPLS in general?... The TP profile is never quite
> delimited.
> Does chapter 4 contain ALL the configurable parameters list agreed to
> provide in the comparison session?
>
> Backwards compatibility
> This was the main argument risen to ground MPLS-TP OAM on BFD. It's not
> a better argument than grounding MPLS-TP OAM on 1731 due to its ETH
> deployment plus coherence with SDH, OTN, as defended by ITU-T.
> For reasons like the above, however, MPLS-TP BFD won't be backwards
> compatible with previous BFD (even considering just CC/CV). They don't
> even share the same codepoint.
>
> Simplicity
> Whether we look to PDH, SDH, OTN or ETH, ITU-T's approach to CC is
> simpler: in each flow, a standard defined nr of constant heartbeat
> signals (with standard constant or provisioned period - no
> auto/negotiated -) means OK. A standard defined number of misses means
> lost Rx connection. An RDI, the only articulation between Rx and Tx
> flows, meaningful in bidirectional applications, allows each pear to
> identify Tx problems.
> This OAM simplicity is the key for reliable fail finger pointing,
> performance reports and protection. Also to allow scaling, more
> implementation opportunities/manufacturers, which is valuable for
> operators.
>
>
> IMHO, between your MPLS-TP view and MPLS/IP, it becomes more and more
> difficult to tell which is which.
>
> Regards,
> Rui
>
>
>
>
>
>
>
>
>
> -----Original Message-----
> From: David Allan I [mailto:david.i.allan@ericsson.com]
> Sent: quarta-feira, 6 de Julho de 2011 19:25
> To: erminio.ottone_69@libero.it; Rui Costa; ietf@ietf.org; IETF-
> Announce
> Cc: mpls@ietf.org
> Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> 05.txt> (Proactive Connectivity Verification, Continuity Check and
> Remote Defect indication for MPLS Transport Profile) to Proposed
> Standard
>
> Hi Erminio:
>
> <snipped>
> >Several service providers regarded this draft as not meeting their
> >transport networks' needs.
>
> E> This is a true statement: the solution in this draft is useless for
> many MPLS- TP deployments.
>
> The two statements do not necessarily follow.
>
> What we established during discussions at the SG15 plenary in February
> was that the issue some service providers had was that the IETF BFD
> solution exceeded their requirements in that there was additional
> functionality they did not see a need for, and that they considered any
> additional functionality parasitic.
>
> However this is a consequence of adapting an existing technology to a
> new application. I do not see any way around that. And the entire joint
> project was based on the premise of engineering re-use not greenfield
> design. That is what it said on the tin up front, and IMO why when the
> IETF started down this path packet transport transitioned from being a
> minority sport to mainstream, so it is a bit late to cry foul....
>
> My 2 cents
> Dave
>
>
>
>
> -----Original Message-----
> From: David Allan I [mailto:david.i.allan@ericsson.com]
> Sent: quarta-feira, 6 de Julho de 2011 18:36
> To: erminio.ottone_69@libero.it; loa@pi.nu; Rui Costa
> Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
> Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> 05.txt> (Proactive Connectivity Verification, Continuity Check and
> Remote Defect indication for MPLS Transport Profile) to Proposed
> Standard
>
> Hi Erminio:
>
> Two of the three document editors were present at SG15 plenary in
> February where the comments originated. The revised meeting schedule
> resulted in a day spent going through the document with the editors.
> IMO there were lots of discussion and legitimate issues with the
> document identified and corrected so it was a useful session. The
> liaison of same was in many ways *after the fact*.
>
> Cheers
> Dave
>
>
>
>
> -----Original Message-----
> From: erminio.ottone_69@libero.it [mailto:erminio.ottone_69@libero.it]
> Sent: quarta-feira, 6 de Julho de 2011 18:34
> To: Rui Costa; ietf@ietf.org; IETF-Announce
> Cc: mpls@ietf.org
> Subject: R: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote
> Defect indication for MPLS Transport Profile) to Proposed Standard
>
> The way this draft has been developed is a bit strange.
>
> The poll for its adoption as a WG document was halted by the MPLS WG
> chair
> because "it is not possible to judge consensus":
>
> http://www.ietf.org/mail-archive/web/mpls/current/msg04502.html
>
> The lack of consensus was motivated by serious technical concerns
> raised by
> several transport experts during the poll.
>
> Nevertheless the MPLS WG chair decided to adopt the draft as a WG
> document:
>
> http://www.ietf.org/mail-archive/web/mpls/current/msg04512.html
>
> After several WG revisions and WG LCs, the technical issues have not
> been
> resolved.
>
> >Several service providers regarded this draft as not meeting their
> transport
> networks' needs.
>
> This is a true statement: the solution in this draft is useless for
> many MPLS-
> TP deployments.
>
>
> -----Original Message-----
> From: erminio.ottone_69@libero.it [mailto:erminio.ottone_69@libero.it]
> Sent: quarta-feira, 6 de Julho de 2011 18:26
> To: loa@pi.nu; Rui Costa
> Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
> Subject: R: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote
> Defect indication for MPLS Transport Profile) to Proposed Standard
>
> >  Version -04 of the document was published June 28th.
> >
> >  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
> >  June 29th.
> >
>
> So when the WG LC to confirm the LC comment resolution has been
> launched?
>
> The proto write-up says:
>
>             It has also passed a working roup call to verify that LC
> comments
> were correctly with minor comments.
>
> It also says:
>
>             The comments has been
>             carefully discussed between the authors and people making
> the
> comments and
>             has been resolved.
>
> But it seems that some comments have not been discussed with the
> authors of
> the comments. When ITU-T Q10/15 has been involved in discussing its
> comments?
>
>
>
>
> -----Original Message-----
> From: Loa Andersson [mailto:loa@pi.nu]
> Sent: quarta-feira, 6 de Julho de 2011 16:44
> To: Rui Costa
> Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote
> Defect indication for MPLS Transport Profile) to Proposed Standard
>
> All,
>
> Since someone has commented about the process used for resolving
> questions on
> draft-ietf-mpls-tp-cc-cv-rdi I am supplying some details below.
>
> The history of draft-ietf-mpls-tp-cc-cv-rdi working group review
> process is:
>
> On February 3rd 2011 the working group last call was issued
> on version -03
>
>       This was copied to the the Ad Hoc Team List
>       and liaised to SG15 also on February 3rd
>
>       This working group last call ended om Feb 28
>
>
>       On Feb 28 we also received a liaison with comments from SG15
>
>
> The authors compiled a list of all comments received  as part the MPLS
> working group last call; these  comments - and the intended resolution
> -
> is included in the meeting minutes from the Prague meeting:
>
>
>       http://www.ietf.org/proceedings/80/slides/mpls-9.pdf
>
>
>   During the IETF meeting in Prague, we agreed with the BFD working
>   group to do a separate working group last callfor the BFD working
>   group
>
> The (BFD) working group last call was started on March 30th and ran
> for 13 days. The last call ended on April 11th.
>
>   The authors have since worked hard to resolve comments, some
>   issue has been brought to the working group mailing list for
>   resolution.
>
>   Version -04 of the document was published June 28th.
>
>   The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
>   June 29th.
>
>   The AD review resulted in a "New ID needed" due to mostly editorial
>   comments. Version -05 was published on June 29 and the IETF last call
>   started as soon as the new ID was avaialbe.
>
>   The current list of Last Call Comments resoltion is also avaiable at:
>   http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
>
>   The list of issues that the authors kept very carefully, shows
> without
> doubt
>   that no comments been ignored.
>
>   Loa
>   mpls wg document shepherd
>
>
>
>
>
>
>
> -----Original Message-----
> From: David Allan I [mailto:david.i.allan@ericsson.com]
> Sent: quarta-feira, 6 de Julho de 2011 14:58
> To: Rui Costa; ietf@ietf.org; IETF-Announce
> Cc: mpls@ietf.org
> Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote
> Defect indication for MPLS Transport Profile) to Proposed Standard
>
> Hi Rui:
>
> The comments were not ignored, the resolution of the Q10 comments as
> well as those collected from the MPLS WG was presented at the last
> IETF. My spreadsheet from which that report was generated and has been
> augmented to include the BFD WG comments is available at
> http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
>
> So you know...
> Dave
>
>
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Rui Costa
> Sent: segunda-feira, 4 de Julho de 2011 23:03
> To: ietf@ietf.org; IETF-Announce
> Cc: mpls@ietf.org
> Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote
> Defect indication for MPLS Transport Profile) to Proposed Standard
>
> IMHO and for the record:
>
> ITU-T comments regarding this draft haven't been discussed with ITU-T
> but were simply ignored. No LS describing these comments' resolution
> was sent.
>
> Several service providers regarded this draft as not meeting their
> transport networks' needs.
>
> [The v03 draft was published in Feb and went to WG LC.
> The v04 draft addressing WG LC comments was published on the 28th June
> (same date as the proto write-up).
> When was the WG LC launched, to verify LC comments resolution?]
>
> Regards,
> Rui
>
>
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> The IESG
> Sent: quinta-feira, 30 de Junho de 2011 14:47
> To: IETF-Announce
> Cc: mpls@ietf.org
> Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote
> Defect indication for MPLS Transport Profile) to Proposed Standard
>
>
> The IESG has received a request from the Multiprotocol Label Switching
> WG
> (mpls) to consider the following document:
> - 'Proactive Connectivity Verification, Continuity Check and Remote
>    Defect indication for MPLS Transport Profile'
>   <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally, comments may
> be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>    Continuity Check, Proactive Connectivity Verification and Remote
>    Defect Indication functionalities are required for MPLS-TP OAM.
>
>    Continuity Check monitors the integrity of the continuity of the
>    label switched path for any loss of continuity defect. Connectivity
>    verification monitors the integrity of the routing of the label
>    switched path between sink and source for any connectivity issues.
>    Remote defect indication enables an End Point to report, to its
>    associated End Point, a fault or defect condition that it detects on
>    a pseudo wire, label switched path or Section.
>
>    This document specifies methods for proactive continuity check,
>    continuity verification, and remote defect indication for MPLS-TP
>    label switched paths, pseudo wires and Sections using Bidirectional
>    Forwarding Detection.
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>
>
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

From mohacsi@niif.hu  Fri Jul  8 02:13:08 2011
Return-Path: <mohacsi@niif.hu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FC5521F88FE; Fri,  8 Jul 2011 02:13:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.296
X-Spam-Level: 
X-Spam-Status: No, score=0.296 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, HELO_EQ_HU=1.35, HOST_EQ_HU=1.245]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yk6zeYIefgWD; Fri,  8 Jul 2011 02:13:07 -0700 (PDT)
Received: from mail.ki.iif.hu (mail.ki.iif.hu [IPv6:2001:738:0:411::241]) by ietfa.amsl.com (Postfix) with ESMTP id 3E60521F88CA; Fri,  8 Jul 2011 02:13:07 -0700 (PDT)
Received: from bolha.lvs.iif.hu (bolha.lvs.iif.hu [193.225.14.181]) by mail.ki.iif.hu (Postfix) with ESMTP id F100087588; Fri,  8 Jul 2011 11:13:05 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at bolha.lvs.iif.hu
Received: from mail.ki.iif.hu ([IPv6:::ffff:193.6.222.241]) by bolha.lvs.iif.hu (bolha.lvs.iif.hu [::ffff:193.225.14.72]) (amavisd-new, port 10024) with ESMTP id DYb-unXn0UwA; Fri,  8 Jul 2011 11:13:03 +0200 (CEST)
Received: by mail.ki.iif.hu (Postfix, from userid 9002) id B69B487581; Fri,  8 Jul 2011 11:13:03 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by mail.ki.iif.hu (Postfix) with ESMTP id B4CFB87548; Fri,  8 Jul 2011 11:13:03 +0200 (CEST)
Date: Fri, 8 Jul 2011 11:13:03 +0200 (CEST)
From: Mohacsi Janos <mohacsi@niif.hu>
X-X-Sender: mohacsi@mignon.ki.iif.hu
To: Ole Troan <otroan@employees.org>
Subject: Re: [v6ops] 6to4 to Experimental? (was: Re: draft-ietf-v6ops-6to4-to-historic)
In-Reply-To: <0622D8FB-2361-49C9-8E44-D70E7F1C2ADE@employees.org>
Message-ID: <alpine.BSF.2.00.1107081105430.63146@mignon.ki.iif.hu>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507F3A@EMBX01-WF.jnpr.net> <4E80A8E8-7B29-426B-BB43-8FC269330E4B@network-heretics.com> <0622D8FB-2361-49C9-8E44-D70E7F1C2ADE@employees.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Mailman-Approved-At: Fri, 08 Jul 2011 08:07:14 -0700
Cc: "v6ops@ietf.org" <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: Fri, 08 Jul 2011 09:13:08 -0000

On Fri, 8 Jul 2011, Ole Troan wrote:

> Keith,
>
>> The alternative that I proposed to IESG and to the chairs (and never received any feedback about) was to reclassify 6to4 as Experimental.   Experimental seems completely appropriate for a protocol that is useful, but only in corner cases.  And I think it's also appropriate and useful to try to learn from the experience with 6to4, even if we realize that 6to4 will never be a generally applicable IPv6 transition solution again.
>>
>> And maybe, just maybe, Experimental will be enough of a "slap" at 6to4 to mollify the "kill it yesterday" crowd.  For one thing, it clearly indicates that 6to4 is no longer a standard.
>>
>> But in order to quieten down the discussion here, I suggest that people reply to me privately if they can't live with this.   If I get lots of those replies, I'll know that it's not worth pursuing.
>
> "Experimental" is certainly better than:
> - nothing
> - spending months on hold as appeals are processed.

I proposed experimental also when discussion started about future of 6to4. 
I support the idea.
 	Best Regards,
 		Janos Mohacsi


From neil.2.harrison@bt.com  Fri Jul  8 06:37:13 2011
Return-Path: <neil.2.harrison@bt.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2512921F86C9; Fri,  8 Jul 2011 06:37:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.146
X-Spam-Level: 
X-Spam-Status: No, score=-2.146 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_21=0.6, J_CHICKENPOX_81=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 G9xl34RGXGGF; Fri,  8 Jul 2011 06:37:11 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp62.intersmtp.COM [62.239.224.235]) by ietfa.amsl.com (Postfix) with ESMTP id 01E6F21F86C5; Fri,  8 Jul 2011 06:37:10 -0700 (PDT)
Received: from EVMHT68-UKRD.domain1.systemhost.net (10.36.3.105) by RDW083A006ED62.smtp-e2.hygiene.service (10.187.98.11) with Microsoft SMTP Server (TLS) id 8.3.159.2; Fri, 8 Jul 2011 14:37:09 +0100
Received: from EMV62-UKRD.domain1.systemhost.net ([169.254.1.186]) by EVMHT68-UKRD.domain1.systemhost.net ([10.36.3.105]) with mapi; Fri, 8 Jul 2011 14:37:09 +0100
From: <neil.2.harrison@bt.com>
To: <jdrake@juniper.net>, <RCosta@ptinovacao.pt>, <david.i.allan@ericsson.com>, <stbryant@cisco.com>
Date: Fri, 8 Jul 2011 14:37:05 +0100
Subject: RE: [mpls] Last	Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication	for	MPLS	Transport	Profile) to Proposed Standard
Thread-Topic: [mpls] Last	Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication	for	MPLS	Transport	Profile) to Proposed Standard
Thread-Index: Acw3LJ0GTOqQfPcUQOGUhgK/1kXgjgDPfXWgACJLxEAAkhZucAANiFrQAABE91A=
Message-ID: <6D3D47CB84BDE349BC23BF1C94E316E4405A7555DD@EMV62-UKRD.domain1.systemhost.net>
References: <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B6BC@INOAVREX11.ptin.corpPT.com> <6D3D47CB84BDE349BC23BF1C94E316E4405A7550DE@EMV62-UKRD.domain1.systemhost.net> <5E893DB832F57341992548CDBB333163A0A8FAF79B@EMBX01-HQ.jnpr.net>
In-Reply-To: <5E893DB832F57341992548CDBB333163A0A8FAF79B@EMBX01-HQ.jnpr.net>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 08 Jul 2011 08:07:14 -0700
Cc: mpls@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, 08 Jul 2011 13:37:13 -0000

Not recently John.  But my comments are general and not specific to this dr=
aft.  But it seems you are implying that the draft recognises my points.  I=
f so I will look forward to reading it later today when I get chance and se=
eing AIS deprecated, TCM deprecated, CC functions deprecated, ability to ta=
p off end-end CV/PM flows at intermediate nodes.

regards, Neil

This email contains BT information, which may be privileged or confidential=
.
It's meant only for the individual(s) or entity named above. If you're not =
the intended
recipient, note that disclosing, copying, distributing or using this inform=
ation
is prohibited. If you've received this email in error, please let me know i=
mmediately
on the email address above. Thank you.
We monitor our email system, and may record your emails.
British Telecommunications plc
Registered office: 81 Newgate Street London EC1A 7AJ
Registered in England no: 1800000




> -----Original Message-----
> From: John E Drake [mailto:jdrake@juniper.net]
> Sent: 08 July 2011 14:26
> To: Harrison,N,Neil,DKQ7 R; RCosta@ptinovacao.pt;
> david.i.allan@ericsson.com; stbryant@cisco.com
> Cc: mpls@ietf.org; ietf@ietf.org; ietf-announce@ietf.org
> Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote
> Defect indication for MPLS Transport Profile) to Proposed Standard
>
> Neil,
>
> I have a question for clarification.  Have you actually read draft-
> ietf-mpls-tp-cc-cv-rdi-05.txt?  I know you don't like doing this but
> generally it is considered good form to read something before
> commenting on it.
>
> Thanks,
>
> John
>
> Sent from my iPhone
>
>
> > -----Original Message-----
> > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
> Of
> > neil.2.harrison@bt.com
> > Sent: Friday, July 08, 2011 12:16 AM
> > To: RCosta@ptinovacao.pt; david.i.allan@ericsson.com;
> > stbryant@cisco.com
> > Cc: mpls@ietf.org; ietf@ietf.org; ietf-announce@ietf.org
> > Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> > (Proactive Connectivity Verification, Continuity Check and Remote
> > Defect indication for MPLS Transport Profile) to Proposed Standard
> >
> > Got to say I agree with Rui on much of what he says here.  And I
> > absolutely resonate with his point on the need for simplicity.  The
> > reason OAM needs to be as simple as possible is because it must be
> > super reliable....we do not want to consciously build in weaknesses,
> > esp unnecessary ones.... this also implies minimal config.  We could
> > all do better on this.  For example:
> >
> > -       Rui is dead right a CC function is fairly useless, we only
> need
> > a CV function...the ATM OAM in I.610 suffers from this problem (and
> few
> > others like AIS and the assumed use of request/response MLT to
> diagnose
> > leaking/mismerging traffic...request/response OAM won't work with
> > unidirectional defects).
> >
> > -       all packet layer networks should not have an AIS OAM
> > message....very obvious for the cl-ps mode of course.  The co-ps mode
> > is also not like the co-cs mode.  One has to consciously manufacture
> > AIS messages and target them to specific clients in the co-ps
> > mode....who may have taken action in their own layer network and
> 'moved
> > elsewhere' anyway, ie a total waste of time now.  AIS is actually
> > unnecessary wrt providing information anyway, it simply represents an
> > in-built weakness of just something else to go wrong which itself
> will
> > create problems.
> >
> > -       creating preconfigured TCM sublayers is just asking for
> trouble
> > IMO.  It is far smarter to simply create a single end-end OAM CV (and
> > when required PM) flow and tap this off at intermediate nodes on the
> > *rare* occasions one wants to do.
> >
> > regards, Neil
> >
> > This email contains BT information, which may be privileged or
> > confidential.
> > It's meant only for the individual(s) or entity named above. If
> you're
> > not the intended
> > recipient, note that disclosing, copying, distributing or using this
> > information
> > is prohibited. If you've received this email in error, please let me
> > know immediately
> > on the email address above. Thank you.
> > We monitor our email system, and may record your emails.
> > British Telecommunications plc
> > Registered office: 81 Newgate Street London EC1A 7AJ
> > Registered in England no: 1800000
> >
> >
> >
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On
> Behalf
> > Of
> > > Rui Costa
> > > Sent: 08 July 2011 01:15
> > > To: David Allan I; Stewart Bryant
> > > Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
> > > Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> 05.txt>
> > > (Proactive Connectivity Verification, Continuity Check and Remote
> > > Defect indication for MPLS Transport Profile) to Proposed Standard
> > >
> > > David,
> > >
> > > Reading something, keeping it on record, without effect in the
> draft
> > > and "ignoring comments" have IMHO similar outcomes. As author of
> the
> > > draft you are free to do it. These standards have a great impact in
> > our
> > > work, so i'm also free to write what i did.
> > >
> > >
> > >
> > >
> > > Stewart,
> > >
> > > My technical concerns regarding this draft were expressed...
> > > ...in the (ITU-T -> IETF, Feb/2011) liaison regarding it (LS281, i
> > > believe);
> > > ...in operators' meetings' that took place during ITU-T's Feb/2011
> > > plenary meeting;
> > > ...in a comparison session that took place during that same ITU-T
> > > meeting.
> > > Some:
> > >
> > > CC/CV
> > > I don't understand the need for 2 types of packets: a single type
> > > allows CC; mismatching identifiers in the same CC packets allow CV.
> > > Besides adding complexity, we whether always activate both or
> > > potentiate undetected mismerges.
> > > (BTW: can't understand how we propose one ACH codepoint to CC,
> > another
> > > for CV, [counting other drafts, another for frame loss ...] but
> don't
> > > consider assigning 1 single ACH protocol identifier codepoint as
> > > requested by ITU-T)
> > >
> > > Uni P2P / P2MP
> > > I can't see how BFD will support unidir and hence P2MP other
> than...
> > >
> > > ...eliminating the session "state variable" (down, init, up),
> aiming
> > > just the state variables we really need, bringing us to something
> > > similar to 1731, eventually with other bits on the wire or...
> > > ...using IP to create the reverse way, which we cannot assume per
> > > requirements;
> > > Will we create a complete different tool for that?
> > > (BFD's B=3D"bidirectional")
> > >
> > > Provisioning list
> > > This is an MPLS profile/subset (and i heard) achievable through a
> > > particular configuration. So, i expect each draft-ietf-mpls-TP-* to
> > > focus on that profile/configuration. However, i keep seeing
> > references
> > > f.i. to IP encapsulations unexpected under TP's OAM.
> > > I don't thus understand what the aim is: do we expect this in TP,
> are
> > > we talking about MPLS in general?... The TP profile is never quite
> > > delimited.
> > > Does chapter 4 contain ALL the configurable parameters list agreed
> to
> > > provide in the comparison session?
> > >
> > > Backwards compatibility
> > > This was the main argument risen to ground MPLS-TP OAM on BFD. It's
> > not
> > > a better argument than grounding MPLS-TP OAM on 1731 due to its ETH
> > > deployment plus coherence with SDH, OTN, as defended by ITU-T.
> > > For reasons like the above, however, MPLS-TP BFD won't be backwards
> > > compatible with previous BFD (even considering just CC/CV). They
> > don't
> > > even share the same codepoint.
> > >
> > > Simplicity
> > > Whether we look to PDH, SDH, OTN or ETH, ITU-T's approach to CC is
> > > simpler: in each flow, a standard defined nr of constant heartbeat
> > > signals (with standard constant or provisioned period - no
> > > auto/negotiated -) means OK. A standard defined number of misses
> > means
> > > lost Rx connection. An RDI, the only articulation between Rx and Tx
> > > flows, meaningful in bidirectional applications, allows each pear
> to
> > > identify Tx problems.
> > > This OAM simplicity is the key for reliable fail finger pointing,
> > > performance reports and protection. Also to allow scaling, more
> > > implementation opportunities/manufacturers, which is valuable for
> > > operators.
> > >
> > >
> > > IMHO, between your MPLS-TP view and MPLS/IP, it becomes more and
> more
> > > difficult to tell which is which.
> > >
> > > Regards,
> > > Rui
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: David Allan I [mailto:david.i.allan@ericsson.com]
> > > Sent: quarta-feira, 6 de Julho de 2011 19:25
> > > To: erminio.ottone_69@libero.it; Rui Costa; ietf@ietf.org; IETF-
> > > Announce
> > > Cc: mpls@ietf.org
> > > Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-
> rdi-
> > > 05.txt> (Proactive Connectivity Verification, Continuity Check and
> > > Remote Defect indication for MPLS Transport Profile) to Proposed
> > > Standard
> > >
> > > Hi Erminio:
> > >
> > > <snipped>
> > > >Several service providers regarded this draft as not meeting their
> > > >transport networks' needs.
> > >
> > > E> This is a true statement: the solution in this draft is useless
> > for
> > > many MPLS- TP deployments.
> > >
> > > The two statements do not necessarily follow.
> > >
> > > What we established during discussions at the SG15 plenary in
> > February
> > > was that the issue some service providers had was that the IETF BFD
> > > solution exceeded their requirements in that there was additional
> > > functionality they did not see a need for, and that they considered
> > any
> > > additional functionality parasitic.
> > >
> > > However this is a consequence of adapting an existing technology to
> a
> > > new application. I do not see any way around that. And the entire
> > joint
> > > project was based on the premise of engineering re-use not
> greenfield
> > > design. That is what it said on the tin up front, and IMO why when
> > the
> > > IETF started down this path packet transport transitioned from
> being
> > a
> > > minority sport to mainstream, so it is a bit late to cry foul....
> > >
> > > My 2 cents
> > > Dave
> > >
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: David Allan I [mailto:david.i.allan@ericsson.com]
> > > Sent: quarta-feira, 6 de Julho de 2011 18:36
> > > To: erminio.ottone_69@libero.it; loa@pi.nu; Rui Costa
> > > Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
> > > Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-
> rdi-
> > > 05.txt> (Proactive Connectivity Verification, Continuity Check and
> > > Remote Defect indication for MPLS Transport Profile) to Proposed
> > > Standard
> > >
> > > Hi Erminio:
> > >
> > > Two of the three document editors were present at SG15 plenary in
> > > February where the comments originated. The revised meeting
> schedule
> > > resulted in a day spent going through the document with the
> editors.
> > > IMO there were lots of discussion and legitimate issues with the
> > > document identified and corrected so it was a useful session. The
> > > liaison of same was in many ways *after the fact*.
> > >
> > > Cheers
> > > Dave
> > >
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: erminio.ottone_69@libero.it
> > [mailto:erminio.ottone_69@libero.it]
> > > Sent: quarta-feira, 6 de Julho de 2011 18:34
> > > To: Rui Costa; ietf@ietf.org; IETF-Announce
> > > Cc: mpls@ietf.org
> > > Subject: R: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> > 05.txt>
> > > (Proactive Connectivity Verification, Continuity Check and Remote
> > > Defect indication for MPLS Transport Profile) to Proposed Standard
> > >
> > > The way this draft has been developed is a bit strange.
> > >
> > > The poll for its adoption as a WG document was halted by the MPLS
> WG
> > > chair
> > > because "it is not possible to judge consensus":
> > >
> > > http://www.ietf.org/mail-archive/web/mpls/current/msg04502.html
> > >
> > > The lack of consensus was motivated by serious technical concerns
> > > raised by
> > > several transport experts during the poll.
> > >
> > > Nevertheless the MPLS WG chair decided to adopt the draft as a WG
> > > document:
> > >
> > > http://www.ietf.org/mail-archive/web/mpls/current/msg04512.html
> > >
> > > After several WG revisions and WG LCs, the technical issues have
> not
> > > been
> > > resolved.
> > >
> > > >Several service providers regarded this draft as not meeting their
> > > transport
> > > networks' needs.
> > >
> > > This is a true statement: the solution in this draft is useless for
> > > many MPLS-
> > > TP deployments.
> > >
> > >
> > > -----Original Message-----
> > > From: erminio.ottone_69@libero.it
> > [mailto:erminio.ottone_69@libero.it]
> > > Sent: quarta-feira, 6 de Julho de 2011 18:26
> > > To: loa@pi.nu; Rui Costa
> > > Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
> > > Subject: R: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> > 05.txt>
> > > (Proactive Connectivity Verification, Continuity Check and Remote
> > > Defect indication for MPLS Transport Profile) to Proposed Standard
> > >
> > > >  Version -04 of the document was published June 28th.
> > > >
> > > >  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was
> sent
> > > >  June 29th.
> > > >
> > >
> > > So when the WG LC to confirm the LC comment resolution has been
> > > launched?
> > >
> > > The proto write-up says:
> > >
> > >             It has also passed a working roup call to verify that
> LC
> > > comments
> > > were correctly with minor comments.
> > >
> > > It also says:
> > >
> > >             The comments has been
> > >             carefully discussed between the authors and people
> making
> > > the
> > > comments and
> > >             has been resolved.
> > >
> > > But it seems that some comments have not been discussed with the
> > > authors of
> > > the comments. When ITU-T Q10/15 has been involved in discussing its
> > > comments?
> > >
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Loa Andersson [mailto:loa@pi.nu]
> > > Sent: quarta-feira, 6 de Julho de 2011 16:44
> > > To: Rui Costa
> > > Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
> > > Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> 05.txt>
> > > (Proactive Connectivity Verification, Continuity Check and Remote
> > > Defect indication for MPLS Transport Profile) to Proposed Standard
> > >
> > > All,
> > >
> > > Since someone has commented about the process used for resolving
> > > questions on
> > > draft-ietf-mpls-tp-cc-cv-rdi I am supplying some details below.
> > >
> > > The history of draft-ietf-mpls-tp-cc-cv-rdi working group review
> > > process is:
> > >
> > > On February 3rd 2011 the working group last call was issued
> > > on version -03
> > >
> > >       This was copied to the the Ad Hoc Team List
> > >       and liaised to SG15 also on February 3rd
> > >
> > >       This working group last call ended om Feb 28
> > >
> > >
> > >       On Feb 28 we also received a liaison with comments from SG15
> > >
> > >
> > > The authors compiled a list of all comments received  as part the
> > MPLS
> > > working group last call; these  comments - and the intended
> > resolution
> > > -
> > > is included in the meeting minutes from the Prague meeting:
> > >
> > >
> > >       http://www.ietf.org/proceedings/80/slides/mpls-9.pdf
> > >
> > >
> > >   During the IETF meeting in Prague, we agreed with the BFD working
> > >   group to do a separate working group last callfor the BFD working
> > >   group
> > >
> > > The (BFD) working group last call was started on March 30th and ran
> > > for 13 days. The last call ended on April 11th.
> > >
> > >   The authors have since worked hard to resolve comments, some
> > >   issue has been brought to the working group mailing list for
> > >   resolution.
> > >
> > >   Version -04 of the document was published June 28th.
> > >
> > >   The publication request for draft-ietf-mpls-tp-cc-cv-rdi was
> sent
> > >   June 29th.
> > >
> > >   The AD review resulted in a "New ID needed" due to mostly
> editorial
> > >   comments. Version -05 was published on June 29 and the IETF last
> > call
> > >   started as soon as the new ID was avaialbe.
> > >
> > >   The current list of Last Call Comments resoltion is also avaiable
> > at:
> > >   http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
> > >
> > >   The list of issues that the authors kept very carefully, shows
> > > without
> > > doubt
> > >   that no comments been ignored.
> > >
> > >   Loa
> > >   mpls wg document shepherd
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: David Allan I [mailto:david.i.allan@ericsson.com]
> > > Sent: quarta-feira, 6 de Julho de 2011 14:58
> > > To: Rui Costa; ietf@ietf.org; IETF-Announce
> > > Cc: mpls@ietf.org
> > > Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> 05.txt>
> > > (Proactive Connectivity Verification, Continuity Check and Remote
> > > Defect indication for MPLS Transport Profile) to Proposed Standard
> > >
> > > Hi Rui:
> > >
> > > The comments were not ignored, the resolution of the Q10 comments
> as
> > > well as those collected from the MPLS WG was presented at the last
> > > IETF. My spreadsheet from which that report was generated and has
> > been
> > > augmented to include the BFD WG comments is available at
> > > http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
> > >
> > > So you know...
> > > Dave
> > >
> > >
> > > -----Original Message-----
> > > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On
> Behalf
> > Of
> > > Rui Costa
> > > Sent: segunda-feira, 4 de Julho de 2011 23:03
> > > To: ietf@ietf.org; IETF-Announce
> > > Cc: mpls@ietf.org
> > > Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> 05.txt>
> > > (Proactive Connectivity Verification, Continuity Check and Remote
> > > Defect indication for MPLS Transport Profile) to Proposed Standard
> > >
> > > IMHO and for the record:
> > >
> > > ITU-T comments regarding this draft haven't been discussed with
> ITU-T
> > > but were simply ignored. No LS describing these comments'
> resolution
> > > was sent.
> > >
> > > Several service providers regarded this draft as not meeting their
> > > transport networks' needs.
> > >
> > > [The v03 draft was published in Feb and went to WG LC.
> > > The v04 draft addressing WG LC comments was published on the 28th
> > June
> > > (same date as the proto write-up).
> > > When was the WG LC launched, to verify LC comments resolution?]
> > >
> > > Regards,
> > > Rui
> > >
> > >
> > > -----Original Message-----
> > > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On
> Behalf
> > Of
> > > The IESG
> > > Sent: quinta-feira, 30 de Junho de 2011 14:47
> > > To: IETF-Announce
> > > Cc: mpls@ietf.org
> > > Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> > > (Proactive Connectivity Verification, Continuity Check and Remote
> > > Defect indication for MPLS Transport Profile) to Proposed Standard
> > >
> > >
> > > The IESG has received a request from the Multiprotocol Label
> > Switching
> > > WG
> > > (mpls) to consider the following document:
> > > - 'Proactive Connectivity Verification, Continuity Check and Remote
> > >    Defect indication for MPLS Transport Profile'
> > >   <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally, comments
> > may
> > > be
> > > sent to iesg@ietf.org instead. In either case, please retain the
> > > beginning of the Subject line to allow automated sorting.
> > >
> > > Abstract
> > >
> > >    Continuity Check, Proactive Connectivity Verification and Remote
> > >    Defect Indication functionalities are required for MPLS-TP OAM.
> > >
> > >    Continuity Check monitors the integrity of the continuity of the
> > >    label switched path for any loss of continuity defect.
> > Connectivity
> > >    verification monitors the integrity of the routing of the label
> > >    switched path between sink and source for any connectivity
> issues.
> > >    Remote defect indication enables an End Point to report, to its
> > >    associated End Point, a fault or defect condition that it
> detects
> > on
> > >    a pseudo wire, label switched path or Section.
> > >
> > >    This document specifies methods for proactive continuity check,
> > >    continuity verification, and remote defect indication for MPLS-
> TP
> > >    label switched paths, pseudo wires and Sections using
> > Bidirectional
> > >    Forwarding Detection.
> > >
> > >
> > > The file can be obtained via
> > > http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
> > >
> > > IESG discussion can be tracked via
> > > http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
> > >
> > >
> > > No IPR declarations have been submitted directly on this I-D.
> > > _______________________________________________
> > > mpls mailing list
> > > mpls@ietf.org
> > > https://www.ietf.org/mailman/listinfo/mpls
> > >
> > >
> > > _______________________________________________
> > > Ietf mailing list
> > > Ietf@ietf.org
> > > https://www.ietf.org/mailman/listinfo/ietf
> > > _______________________________________________
> > > mpls mailing list
> > > mpls@ietf.org
> > > https://www.ietf.org/mailman/listinfo/mpls
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls

From tnadeau@lucidvision.com  Fri Jul  8 08:26:39 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 9642E21F8AFC; Fri,  8 Jul 2011 08:26:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_21=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 Y+2GhRzo209m; Fri,  8 Jul 2011 08:26:38 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id D7BF221F8AD5; Fri,  8 Jul 2011 08:26:37 -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 B5E851C37658; Fri,  8 Jul 2011 11:26:36 -0400 (EDT)
Subject: Re: [mpls] Last Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt>	(Proactive	Connectivity	Verification, Continuity Check and Remote Defect	indication for	MPLS	Transport	Profile) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <6D3D47CB84BDE349BC23BF1C94E316E4405A7550DE@EMV62-UKRD.domain1.systemhost.net>
Date: Fri, 8 Jul 2011 11:26:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <BA2E2586-1B10-4954-93A2-E8EE9DF0427F@lucidvision.com>
References: <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B6BC@INOAVREX11.ptin.corpPT.com> <6D3D47CB84BDE349BC23BF1C94E316E4405A7550DE@EMV62-UKRD.domain1.systemhost.net>
To: <neil.2.harrison@bt.com>
X-Mailer: Apple Mail (2.1084)
Cc: mpls@ietf.org, ietf@ietf.org, david.i.allan@ericsson.com, ietf-announce@ietf.org, 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: Fri, 08 Jul 2011 15:26:39 -0000

On Jul 8, 2011, at 3:15 AM, <neil.2.harrison@bt.com> wrote:

> Got to say I agree with Rui on much of what he says here.  And I =
absolutely resonate with his point on the need for simplicity.  The =
reason OAM needs to be as simple as possible is because it must be super =
reliable....we do not want to consciously build in weaknesses, esp =
unnecessary ones.... this also implies minimal config.  We could all do =
better on this.  For example:
>=20
> -       Rui is dead right a CC function is fairly useless, we only =
need a CV function...the ATM OAM in I.610 suffers from this problem (and =
few others like AIS and the assumed use of request/response MLT to =
diagnose leaking/mismerging traffic...request/response OAM won't work =
with unidirectional defects).

	While you are entitled to your opinion, I personally think there =
are enough requirements elsewhere to have both CC and CV functions.  But =
we digress. Are you actually asking that the CC functionality be removed =
from the draft or just making a general comment?

> -       all packet layer networks should not have an AIS OAM =
message....very obvious for the cl-ps mode of course.  The co-ps mode is =
also not like the co-cs mode.  One has to consciously manufacture AIS =
messages and target them to specific clients in the co-ps mode....who =
may have taken action in their own layer network and 'moved elsewhere' =
anyway, ie a total waste of time now.  AIS is actually unnecessary wrt =
providing information anyway, it simply represents an in-built weakness =
of just something else to go wrong which itself will create problems.

	What does that comment have to do with the actual draft in =
question?

> -       creating preconfigured TCM sublayers is just asking for =
trouble IMO.  It is far smarter to simply create a single end-end OAM CV =
(and when required PM) flow and tap this off at intermediate nodes on =
the *rare* occasions one wants to do.

	Again, what does this have to do with the actual draft in =
question?

	--tom




>=20
> regards, Neil
>=20
> This email contains BT information, which may be privileged or =
confidential.
> It's meant only for the individual(s) or entity named above. If you're =
not the intended
> recipient, note that disclosing, copying, distributing or using this =
information
> is prohibited. If you've received this email in error, please let me =
know immediately
> on the email address above. Thank you.
> We monitor our email system, and may record your emails.
> British Telecommunications plc
> Registered office: 81 Newgate Street London EC1A 7AJ
> Registered in England no: 1800000
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>> -----Original Message-----
>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf =
Of
>> Rui Costa
>> Sent: 08 July 2011 01:15
>> To: David Allan I; Stewart Bryant
>> Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
>> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
>> (Proactive Connectivity Verification, Continuity Check and Remote
>> Defect indication for MPLS Transport Profile) to Proposed Standard
>>=20
>> David,
>>=20
>> Reading something, keeping it on record, without effect in the draft
>> and "ignoring comments" have IMHO similar outcomes. As author of the
>> draft you are free to do it. These standards have a great impact in =
our
>> work, so i'm also free to write what i did.
>>=20
>>=20
>>=20
>>=20
>> Stewart,
>>=20
>> My technical concerns regarding this draft were expressed...
>> ...in the (ITU-T -> IETF, Feb/2011) liaison regarding it (LS281, i
>> believe);
>> ...in operators' meetings' that took place during ITU-T's Feb/2011
>> plenary meeting;
>> ...in a comparison session that took place during that same ITU-T
>> meeting.
>> Some:
>>=20
>> CC/CV
>> I don't understand the need for 2 types of packets: a single type
>> allows CC; mismatching identifiers in the same CC packets allow CV.
>> Besides adding complexity, we whether always activate both or
>> potentiate undetected mismerges.
>> (BTW: can't understand how we propose one ACH codepoint to CC, =
another
>> for CV, [counting other drafts, another for frame loss ...] but don't
>> consider assigning 1 single ACH protocol identifier codepoint as
>> requested by ITU-T)
>>=20
>> Uni P2P / P2MP
>> I can't see how BFD will support unidir and hence P2MP other than...
>>=20
>> ...eliminating the session "state variable" (down, init, up), aiming
>> just the state variables we really need, bringing us to something
>> similar to 1731, eventually with other bits on the wire or...
>> ...using IP to create the reverse way, which we cannot assume per
>> requirements;
>> Will we create a complete different tool for that?
>> (BFD's B=3D"bidirectional")
>>=20
>> Provisioning list
>> This is an MPLS profile/subset (and i heard) achievable through a
>> particular configuration. So, i expect each draft-ietf-mpls-TP-* to
>> focus on that profile/configuration. However, i keep seeing =
references
>> f.i. to IP encapsulations unexpected under TP's OAM.
>> I don't thus understand what the aim is: do we expect this in TP, are
>> we talking about MPLS in general?... The TP profile is never quite
>> delimited.
>> Does chapter 4 contain ALL the configurable parameters list agreed to
>> provide in the comparison session?
>>=20
>> Backwards compatibility
>> This was the main argument risen to ground MPLS-TP OAM on BFD. It's =
not
>> a better argument than grounding MPLS-TP OAM on 1731 due to its ETH
>> deployment plus coherence with SDH, OTN, as defended by ITU-T.
>> For reasons like the above, however, MPLS-TP BFD won't be backwards
>> compatible with previous BFD (even considering just CC/CV). They =
don't
>> even share the same codepoint.
>>=20
>> Simplicity
>> Whether we look to PDH, SDH, OTN or ETH, ITU-T's approach to CC is
>> simpler: in each flow, a standard defined nr of constant heartbeat
>> signals (with standard constant or provisioned period - no
>> auto/negotiated -) means OK. A standard defined number of misses =
means
>> lost Rx connection. An RDI, the only articulation between Rx and Tx
>> flows, meaningful in bidirectional applications, allows each pear to
>> identify Tx problems.
>> This OAM simplicity is the key for reliable fail finger pointing,
>> performance reports and protection. Also to allow scaling, more
>> implementation opportunities/manufacturers, which is valuable for
>> operators.
>>=20
>>=20
>> IMHO, between your MPLS-TP view and MPLS/IP, it becomes more and more
>> difficult to tell which is which.
>>=20
>> Regards,
>> Rui
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>> -----Original Message-----
>> From: David Allan I [mailto:david.i.allan@ericsson.com]
>> Sent: quarta-feira, 6 de Julho de 2011 19:25
>> To: erminio.ottone_69@libero.it; Rui Costa; ietf@ietf.org; IETF-
>> Announce
>> Cc: mpls@ietf.org
>> Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
>> 05.txt> (Proactive Connectivity Verification, Continuity Check and
>> Remote Defect indication for MPLS Transport Profile) to Proposed
>> Standard
>>=20
>> Hi Erminio:
>>=20
>> <snipped>
>>> Several service providers regarded this draft as not meeting their
>>> transport networks' needs.
>>=20
>> E> This is a true statement: the solution in this draft is useless =
for
>> many MPLS- TP deployments.
>>=20
>> The two statements do not necessarily follow.
>>=20
>> What we established during discussions at the SG15 plenary in =
February
>> was that the issue some service providers had was that the IETF BFD
>> solution exceeded their requirements in that there was additional
>> functionality they did not see a need for, and that they considered =
any
>> additional functionality parasitic.
>>=20
>> However this is a consequence of adapting an existing technology to a
>> new application. I do not see any way around that. And the entire =
joint
>> project was based on the premise of engineering re-use not greenfield
>> design. That is what it said on the tin up front, and IMO why when =
the
>> IETF started down this path packet transport transitioned from being =
a
>> minority sport to mainstream, so it is a bit late to cry foul....
>>=20
>> My 2 cents
>> Dave
>>=20
>>=20
>>=20
>>=20
>> -----Original Message-----
>> From: David Allan I [mailto:david.i.allan@ericsson.com]
>> Sent: quarta-feira, 6 de Julho de 2011 18:36
>> To: erminio.ottone_69@libero.it; loa@pi.nu; Rui Costa
>> Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
>> Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
>> 05.txt> (Proactive Connectivity Verification, Continuity Check and
>> Remote Defect indication for MPLS Transport Profile) to Proposed
>> Standard
>>=20
>> Hi Erminio:
>>=20
>> Two of the three document editors were present at SG15 plenary in
>> February where the comments originated. The revised meeting schedule
>> resulted in a day spent going through the document with the editors.
>> IMO there were lots of discussion and legitimate issues with the
>> document identified and corrected so it was a useful session. The
>> liaison of same was in many ways *after the fact*.
>>=20
>> Cheers
>> Dave
>>=20
>>=20
>>=20
>>=20
>> -----Original Message-----
>> From: erminio.ottone_69@libero.it =
[mailto:erminio.ottone_69@libero.it]
>> Sent: quarta-feira, 6 de Julho de 2011 18:34
>> To: Rui Costa; ietf@ietf.org; IETF-Announce
>> Cc: mpls@ietf.org
>> Subject: R: Re: [mpls] Last Call: =
<draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
>> (Proactive Connectivity Verification, Continuity Check and Remote
>> Defect indication for MPLS Transport Profile) to Proposed Standard
>>=20
>> The way this draft has been developed is a bit strange.
>>=20
>> The poll for its adoption as a WG document was halted by the MPLS WG
>> chair
>> because "it is not possible to judge consensus":
>>=20
>> http://www.ietf.org/mail-archive/web/mpls/current/msg04502.html
>>=20
>> The lack of consensus was motivated by serious technical concerns
>> raised by
>> several transport experts during the poll.
>>=20
>> Nevertheless the MPLS WG chair decided to adopt the draft as a WG
>> document:
>>=20
>> http://www.ietf.org/mail-archive/web/mpls/current/msg04512.html
>>=20
>> After several WG revisions and WG LCs, the technical issues have not
>> been
>> resolved.
>>=20
>>> Several service providers regarded this draft as not meeting their
>> transport
>> networks' needs.
>>=20
>> This is a true statement: the solution in this draft is useless for
>> many MPLS-
>> TP deployments.
>>=20
>>=20
>> -----Original Message-----
>> From: erminio.ottone_69@libero.it =
[mailto:erminio.ottone_69@libero.it]
>> Sent: quarta-feira, 6 de Julho de 2011 18:26
>> To: loa@pi.nu; Rui Costa
>> Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
>> Subject: R: Re: [mpls] Last Call: =
<draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
>> (Proactive Connectivity Verification, Continuity Check and Remote
>> Defect indication for MPLS Transport Profile) to Proposed Standard
>>=20
>>> Version -04 of the document was published June 28th.
>>>=20
>>> The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
>>> June 29th.
>>>=20
>>=20
>> So when the WG LC to confirm the LC comment resolution has been
>> launched?
>>=20
>> The proto write-up says:
>>=20
>>            It has also passed a working roup call to verify that LC
>> comments
>> were correctly with minor comments.
>>=20
>> It also says:
>>=20
>>            The comments has been
>>            carefully discussed between the authors and people making
>> the
>> comments and
>>            has been resolved.
>>=20
>> But it seems that some comments have not been discussed with the
>> authors of
>> the comments. When ITU-T Q10/15 has been involved in discussing its
>> comments?
>>=20
>>=20
>>=20
>>=20
>> -----Original Message-----
>> From: Loa Andersson [mailto:loa@pi.nu]
>> Sent: quarta-feira, 6 de Julho de 2011 16:44
>> To: Rui Costa
>> Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
>> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
>> (Proactive Connectivity Verification, Continuity Check and Remote
>> Defect indication for MPLS Transport Profile) to Proposed Standard
>>=20
>> All,
>>=20
>> Since someone has commented about the process used for resolving
>> questions on
>> draft-ietf-mpls-tp-cc-cv-rdi I am supplying some details below.
>>=20
>> The history of draft-ietf-mpls-tp-cc-cv-rdi working group review
>> process is:
>>=20
>> On February 3rd 2011 the working group last call was issued
>> on version -03
>>=20
>>      This was copied to the the Ad Hoc Team List
>>      and liaised to SG15 also on February 3rd
>>=20
>>      This working group last call ended om Feb 28
>>=20
>>=20
>>      On Feb 28 we also received a liaison with comments from SG15
>>=20
>>=20
>> The authors compiled a list of all comments received  as part the =
MPLS
>> working group last call; these  comments - and the intended =
resolution
>> -
>> is included in the meeting minutes from the Prague meeting:
>>=20
>>=20
>>      http://www.ietf.org/proceedings/80/slides/mpls-9.pdf
>>=20
>>=20
>>  During the IETF meeting in Prague, we agreed with the BFD working
>>  group to do a separate working group last callfor the BFD working
>>  group
>>=20
>> The (BFD) working group last call was started on March 30th and ran
>> for 13 days. The last call ended on April 11th.
>>=20
>>  The authors have since worked hard to resolve comments, some
>>  issue has been brought to the working group mailing list for
>>  resolution.
>>=20
>>  Version -04 of the document was published June 28th.
>>=20
>>  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
>>  June 29th.
>>=20
>>  The AD review resulted in a "New ID needed" due to mostly editorial
>>  comments. Version -05 was published on June 29 and the IETF last =
call
>>  started as soon as the new ID was avaialbe.
>>=20
>>  The current list of Last Call Comments resoltion is also avaiable =
at:
>>  http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
>>=20
>>  The list of issues that the authors kept very carefully, shows
>> without
>> doubt
>>  that no comments been ignored.
>>=20
>>  Loa
>>  mpls wg document shepherd
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>> -----Original Message-----
>> From: David Allan I [mailto:david.i.allan@ericsson.com]
>> Sent: quarta-feira, 6 de Julho de 2011 14:58
>> To: Rui Costa; ietf@ietf.org; IETF-Announce
>> Cc: mpls@ietf.org
>> Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
>> (Proactive Connectivity Verification, Continuity Check and Remote
>> Defect indication for MPLS Transport Profile) to Proposed Standard
>>=20
>> Hi Rui:
>>=20
>> The comments were not ignored, the resolution of the Q10 comments as
>> well as those collected from the MPLS WG was presented at the last
>> IETF. My spreadsheet from which that report was generated and has =
been
>> augmented to include the BFD WG comments is available at
>> http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
>>=20
>> So you know...
>> Dave
>>=20
>>=20
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of
>> Rui Costa
>> Sent: segunda-feira, 4 de Julho de 2011 23:03
>> To: ietf@ietf.org; IETF-Announce
>> Cc: mpls@ietf.org
>> Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
>> (Proactive Connectivity Verification, Continuity Check and Remote
>> Defect indication for MPLS Transport Profile) to Proposed Standard
>>=20
>> IMHO and for the record:
>>=20
>> ITU-T comments regarding this draft haven't been discussed with ITU-T
>> but were simply ignored. No LS describing these comments' resolution
>> was sent.
>>=20
>> Several service providers regarded this draft as not meeting their
>> transport networks' needs.
>>=20
>> [The v03 draft was published in Feb and went to WG LC.
>> The v04 draft addressing WG LC comments was published on the 28th =
June
>> (same date as the proto write-up).
>> When was the WG LC launched, to verify LC comments resolution?]
>>=20
>> Regards,
>> Rui
>>=20
>>=20
>> -----Original Message-----
>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf =
Of
>> The IESG
>> Sent: quinta-feira, 30 de Junho de 2011 14:47
>> To: IETF-Announce
>> Cc: mpls@ietf.org
>> Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
>> (Proactive Connectivity Verification, Continuity Check and Remote
>> Defect indication for MPLS Transport Profile) to Proposed Standard
>>=20
>>=20
>> The IESG has received a request from the Multiprotocol Label =
Switching
>> WG
>> (mpls) to consider the following document:
>> - 'Proactive Connectivity Verification, Continuity Check and Remote
>>   Defect indication for MPLS Transport Profile'
>>  <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> as a Proposed Standard
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to =
the
>> ietf@ietf.org mailing lists by 2011-07-14. Exceptionally, comments =
may
>> be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>   Continuity Check, Proactive Connectivity Verification and Remote
>>   Defect Indication functionalities are required for MPLS-TP OAM.
>>=20
>>   Continuity Check monitors the integrity of the continuity of the
>>   label switched path for any loss of continuity defect. Connectivity
>>   verification monitors the integrity of the routing of the label
>>   switched path between sink and source for any connectivity issues.
>>   Remote defect indication enables an End Point to report, to its
>>   associated End Point, a fault or defect condition that it detects =
on
>>   a pseudo wire, label switched path or Section.
>>=20
>>   This document specifies methods for proactive continuity check,
>>   continuity verification, and remote defect indication for MPLS-TP
>>   label switched paths, pseudo wires and Sections using Bidirectional
>>   Forwarding Detection.
>>=20
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>>=20
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>=20
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>=20


From jdrake@juniper.net  Fri Jul  8 08:33:00 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 2294B21F872D; Fri,  8 Jul 2011 08:33:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.177
X-Spam-Level: 
X-Spam-Status: No, score=-5.177 tagged_above=-999 required=5 tests=[AWL=0.222,  BAYES_00=-2.599, J_CHICKENPOX_21=0.6, J_CHICKENPOX_81=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 7qKAdRTHS5eu; Fri,  8 Jul 2011 08:32:58 -0700 (PDT)
Received: from exprod7og119.obsmtp.com (exprod7og119.obsmtp.com [64.18.2.16]) by ietfa.amsl.com (Postfix) with ESMTP id 871E221F8706; Fri,  8 Jul 2011 08:32:57 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob119.postini.com ([64.18.6.12]) with SMTP ID DSNKThcjIQVEyrz6soZ1CNdu9F+/66h+rrKZ@postini.com; Fri, 08 Jul 2011 08:32:57 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Fri, 8 Jul 2011 08:30:38 -0700
From: John E Drake <jdrake@juniper.net>
To: "neil.2.harrison@bt.com" <neil.2.harrison@bt.com>, "RCosta@ptinovacao.pt" <RCosta@ptinovacao.pt>, "david.i.allan@ericsson.com" <david.i.allan@ericsson.com>, "stbryant@cisco.com" <stbryant@cisco.com>
Date: Fri, 8 Jul 2011 08:30:37 -0700
Subject: RE: [mpls] Last	Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication	for	MPLS	Transport	Profile) to Proposed Standard
Thread-Topic: [mpls] Last	Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication	for	MPLS	Transport	Profile) to Proposed Standard
Thread-Index: Acw3LJ0GTOqQfPcUQOGUhgK/1kXgjgDPfXWgACJLxEAAkhZucAANiFrQAABE91AAA+mDYA==
Message-ID: <5E893DB832F57341992548CDBB333163A0A8FAF8BB@EMBX01-HQ.jnpr.net>
References: <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B6BC@INOAVREX11.ptin.corpPT.com> <6D3D47CB84BDE349BC23BF1C94E316E4405A7550DE@EMV62-UKRD.domain1.systemhost.net> <5E893DB832F57341992548CDBB333163A0A8FAF79B@EMBX01-HQ.jnpr.net> <6D3D47CB84BDE349BC23BF1C94E316E4405A7555DD@EMV62-UKRD.domain1.systemhost.net>
In-Reply-To: <6D3D47CB84BDE349BC23BF1C94E316E4405A7555DD@EMV62-UKRD.domain1.systemhost.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: "mpls@ietf.org" <mpls@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, 08 Jul 2011 15:33:00 -0000

Neil,

AIS and CC are ITU requirements but I personally agree with you regarding t=
heir utility.  TCM is an ITU concept that doesn't really apply in an MPLS c=
ontext because of the way the label stack works, and as I have told you bef=
ore, the tap-off function you mention is sensible but it is strictly an imp=
lementation issue - no protocol work is required.

Thanks,

John

Sent from my iPhone


> -----Original Message-----
> From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com]
> Sent: Friday, July 08, 2011 6:37 AM
> To: John E Drake; RCosta@ptinovacao.pt; david.i.allan@ericsson.com;
> stbryant@cisco.com
> Cc: mpls@ietf.org; ietf@ietf.org
> Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote
> Defect indication for MPLS Transport Profile) to Proposed Standard
>
> Not recently John.  But my comments are general and not specific to
> this draft.  But it seems you are implying that the draft recognises my
> points.  If so I will look forward to reading it later today when I get
> chance and seeing AIS deprecated, TCM deprecated, CC functions
> deprecated, ability to tap off end-end CV/PM flows at intermediate
> nodes.
>
> regards, Neil
>
> This email contains BT information, which may be privileged or
> confidential.
> It's meant only for the individual(s) or entity named above. If you're
> not the intended
> recipient, note that disclosing, copying, distributing or using this
> information
> is prohibited. If you've received this email in error, please let me
> know immediately
> on the email address above. Thank you.
> We monitor our email system, and may record your emails.
> British Telecommunications plc
> Registered office: 81 Newgate Street London EC1A 7AJ
> Registered in England no: 1800000
>
>
>
>
> > -----Original Message-----
> > From: John E Drake [mailto:jdrake@juniper.net]
> > Sent: 08 July 2011 14:26
> > To: Harrison,N,Neil,DKQ7 R; RCosta@ptinovacao.pt;
> > david.i.allan@ericsson.com; stbryant@cisco.com
> > Cc: mpls@ietf.org; ietf@ietf.org; ietf-announce@ietf.org
> > Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> > (Proactive Connectivity Verification, Continuity Check and Remote
> > Defect indication for MPLS Transport Profile) to Proposed Standard
> >
> > Neil,
> >
> > I have a question for clarification.  Have you actually read draft-
> > ietf-mpls-tp-cc-cv-rdi-05.txt?  I know you don't like doing this but
> > generally it is considered good form to read something before
> > commenting on it.
> >
> > Thanks,
> >
> > John
> >
> > Sent from my iPhone
> >
> >
> > > -----Original Message-----
> > > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On
> Behalf
> > Of
> > > neil.2.harrison@bt.com
> > > Sent: Friday, July 08, 2011 12:16 AM
> > > To: RCosta@ptinovacao.pt; david.i.allan@ericsson.com;
> > > stbryant@cisco.com
> > > Cc: mpls@ietf.org; ietf@ietf.org; ietf-announce@ietf.org
> > > Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> 05.txt>
> > > (Proactive Connectivity Verification, Continuity Check and Remote
> > > Defect indication for MPLS Transport Profile) to Proposed Standard
> > >
> > > Got to say I agree with Rui on much of what he says here.  And I
> > > absolutely resonate with his point on the need for simplicity.  The
> > > reason OAM needs to be as simple as possible is because it must be
> > > super reliable....we do not want to consciously build in
> weaknesses,
> > > esp unnecessary ones.... this also implies minimal config.  We
> could
> > > all do better on this.  For example:
> > >
> > > -       Rui is dead right a CC function is fairly useless, we only
> > need
> > > a CV function...the ATM OAM in I.610 suffers from this problem (and
> > few
> > > others like AIS and the assumed use of request/response MLT to
> > diagnose
> > > leaking/mismerging traffic...request/response OAM won't work with
> > > unidirectional defects).
> > >
> > > -       all packet layer networks should not have an AIS OAM
> > > message....very obvious for the cl-ps mode of course.  The co-ps
> mode
> > > is also not like the co-cs mode.  One has to consciously
> manufacture
> > > AIS messages and target them to specific clients in the co-ps
> > > mode....who may have taken action in their own layer network and
> > 'moved
> > > elsewhere' anyway, ie a total waste of time now.  AIS is actually
> > > unnecessary wrt providing information anyway, it simply represents
> an
> > > in-built weakness of just something else to go wrong which itself
> > will
> > > create problems.
> > >
> > > -       creating preconfigured TCM sublayers is just asking for
> > trouble
> > > IMO.  It is far smarter to simply create a single end-end OAM CV
> (and
> > > when required PM) flow and tap this off at intermediate nodes on
> the
> > > *rare* occasions one wants to do.
> > >
> > > regards, Neil
> > >
> > > This email contains BT information, which may be privileged or
> > > confidential.
> > > It's meant only for the individual(s) or entity named above. If
> > you're
> > > not the intended
> > > recipient, note that disclosing, copying, distributing or using
> this
> > > information
> > > is prohibited. If you've received this email in error, please let
> me
> > > know immediately
> > > on the email address above. Thank you.
> > > We monitor our email system, and may record your emails.
> > > British Telecommunications plc
> > > Registered office: 81 Newgate Street London EC1A 7AJ
> > > Registered in England no: 1800000
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On
> > Behalf
> > > Of
> > > > Rui Costa
> > > > Sent: 08 July 2011 01:15
> > > > To: David Allan I; Stewart Bryant
> > > > Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
> > > > Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> > 05.txt>
> > > > (Proactive Connectivity Verification, Continuity Check and Remote
> > > > Defect indication for MPLS Transport Profile) to Proposed
> Standard
> > > >
> > > > David,
> > > >
> > > > Reading something, keeping it on record, without effect in the
> > draft
> > > > and "ignoring comments" have IMHO similar outcomes. As author of
> > the
> > > > draft you are free to do it. These standards have a great impact
> in
> > > our
> > > > work, so i'm also free to write what i did.
> > > >
> > > >
> > > >
> > > >
> > > > Stewart,
> > > >
> > > > My technical concerns regarding this draft were expressed...
> > > > ...in the (ITU-T -> IETF, Feb/2011) liaison regarding it (LS281,
> i
> > > > believe);
> > > > ...in operators' meetings' that took place during ITU-T's
> Feb/2011
> > > > plenary meeting;
> > > > ...in a comparison session that took place during that same ITU-T
> > > > meeting.
> > > > Some:
> > > >
> > > > CC/CV
> > > > I don't understand the need for 2 types of packets: a single type
> > > > allows CC; mismatching identifiers in the same CC packets allow
> CV.
> > > > Besides adding complexity, we whether always activate both or
> > > > potentiate undetected mismerges.
> > > > (BTW: can't understand how we propose one ACH codepoint to CC,
> > > another
> > > > for CV, [counting other drafts, another for frame loss ...] but
> > don't
> > > > consider assigning 1 single ACH protocol identifier codepoint as
> > > > requested by ITU-T)
> > > >
> > > > Uni P2P / P2MP
> > > > I can't see how BFD will support unidir and hence P2MP other
> > than...
> > > >
> > > > ...eliminating the session "state variable" (down, init, up),
> > aiming
> > > > just the state variables we really need, bringing us to something
> > > > similar to 1731, eventually with other bits on the wire or...
> > > > ...using IP to create the reverse way, which we cannot assume per
> > > > requirements;
> > > > Will we create a complete different tool for that?
> > > > (BFD's B=3D"bidirectional")
> > > >
> > > > Provisioning list
> > > > This is an MPLS profile/subset (and i heard) achievable through a
> > > > particular configuration. So, i expect each draft-ietf-mpls-TP-*
> to
> > > > focus on that profile/configuration. However, i keep seeing
> > > references
> > > > f.i. to IP encapsulations unexpected under TP's OAM.
> > > > I don't thus understand what the aim is: do we expect this in TP,
> > are
> > > > we talking about MPLS in general?... The TP profile is never
> quite
> > > > delimited.
> > > > Does chapter 4 contain ALL the configurable parameters list
> agreed
> > to
> > > > provide in the comparison session?
> > > >
> > > > Backwards compatibility
> > > > This was the main argument risen to ground MPLS-TP OAM on BFD.
> It's
> > > not
> > > > a better argument than grounding MPLS-TP OAM on 1731 due to its
> ETH
> > > > deployment plus coherence with SDH, OTN, as defended by ITU-T.
> > > > For reasons like the above, however, MPLS-TP BFD won't be
> backwards
> > > > compatible with previous BFD (even considering just CC/CV). They
> > > don't
> > > > even share the same codepoint.
> > > >
> > > > Simplicity
> > > > Whether we look to PDH, SDH, OTN or ETH, ITU-T's approach to CC
> is
> > > > simpler: in each flow, a standard defined nr of constant
> heartbeat
> > > > signals (with standard constant or provisioned period - no
> > > > auto/negotiated -) means OK. A standard defined number of misses
> > > means
> > > > lost Rx connection. An RDI, the only articulation between Rx and
> Tx
> > > > flows, meaningful in bidirectional applications, allows each pear
> > to
> > > > identify Tx problems.
> > > > This OAM simplicity is the key for reliable fail finger pointing,
> > > > performance reports and protection. Also to allow scaling, more
> > > > implementation opportunities/manufacturers, which is valuable for
> > > > operators.
> > > >
> > > >
> > > > IMHO, between your MPLS-TP view and MPLS/IP, it becomes more and
> > more
> > > > difficult to tell which is which.
> > > >
> > > > Regards,
> > > > Rui
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: David Allan I [mailto:david.i.allan@ericsson.com]
> > > > Sent: quarta-feira, 6 de Julho de 2011 19:25
> > > > To: erminio.ottone_69@libero.it; Rui Costa; ietf@ietf.org; IETF-
> > > > Announce
> > > > Cc: mpls@ietf.org
> > > > Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-
> > rdi-
> > > > 05.txt> (Proactive Connectivity Verification, Continuity Check
> and
> > > > Remote Defect indication for MPLS Transport Profile) to Proposed
> > > > Standard
> > > >
> > > > Hi Erminio:
> > > >
> > > > <snipped>
> > > > >Several service providers regarded this draft as not meeting
> their
> > > > >transport networks' needs.
> > > >
> > > > E> This is a true statement: the solution in this draft is
> useless
> > > for
> > > > many MPLS- TP deployments.
> > > >
> > > > The two statements do not necessarily follow.
> > > >
> > > > What we established during discussions at the SG15 plenary in
> > > February
> > > > was that the issue some service providers had was that the IETF
> BFD
> > > > solution exceeded their requirements in that there was additional
> > > > functionality they did not see a need for, and that they
> considered
> > > any
> > > > additional functionality parasitic.
> > > >
> > > > However this is a consequence of adapting an existing technology
> to
> > a
> > > > new application. I do not see any way around that. And the entire
> > > joint
> > > > project was based on the premise of engineering re-use not
> > greenfield
> > > > design. That is what it said on the tin up front, and IMO why
> when
> > > the
> > > > IETF started down this path packet transport transitioned from
> > being
> > > a
> > > > minority sport to mainstream, so it is a bit late to cry foul....
> > > >
> > > > My 2 cents
> > > > Dave
> > > >
> > > >
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: David Allan I [mailto:david.i.allan@ericsson.com]
> > > > Sent: quarta-feira, 6 de Julho de 2011 18:36
> > > > To: erminio.ottone_69@libero.it; loa@pi.nu; Rui Costa
> > > > Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
> > > > Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-
> > rdi-
> > > > 05.txt> (Proactive Connectivity Verification, Continuity Check
> and
> > > > Remote Defect indication for MPLS Transport Profile) to Proposed
> > > > Standard
> > > >
> > > > Hi Erminio:
> > > >
> > > > Two of the three document editors were present at SG15 plenary in
> > > > February where the comments originated. The revised meeting
> > schedule
> > > > resulted in a day spent going through the document with the
> > editors.
> > > > IMO there were lots of discussion and legitimate issues with the
> > > > document identified and corrected so it was a useful session. The
> > > > liaison of same was in many ways *after the fact*.
> > > >
> > > > Cheers
> > > > Dave
> > > >
> > > >
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: erminio.ottone_69@libero.it
> > > [mailto:erminio.ottone_69@libero.it]
> > > > Sent: quarta-feira, 6 de Julho de 2011 18:34
> > > > To: Rui Costa; ietf@ietf.org; IETF-Announce
> > > > Cc: mpls@ietf.org
> > > > Subject: R: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> > > 05.txt>
> > > > (Proactive Connectivity Verification, Continuity Check and Remote
> > > > Defect indication for MPLS Transport Profile) to Proposed
> Standard
> > > >
> > > > The way this draft has been developed is a bit strange.
> > > >
> > > > The poll for its adoption as a WG document was halted by the MPLS
> > WG
> > > > chair
> > > > because "it is not possible to judge consensus":
> > > >
> > > > http://www.ietf.org/mail-archive/web/mpls/current/msg04502.html
> > > >
> > > > The lack of consensus was motivated by serious technical concerns
> > > > raised by
> > > > several transport experts during the poll.
> > > >
> > > > Nevertheless the MPLS WG chair decided to adopt the draft as a WG
> > > > document:
> > > >
> > > > http://www.ietf.org/mail-archive/web/mpls/current/msg04512.html
> > > >
> > > > After several WG revisions and WG LCs, the technical issues have
> > not
> > > > been
> > > > resolved.
> > > >
> > > > >Several service providers regarded this draft as not meeting
> their
> > > > transport
> > > > networks' needs.
> > > >
> > > > This is a true statement: the solution in this draft is useless
> for
> > > > many MPLS-
> > > > TP deployments.
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: erminio.ottone_69@libero.it
> > > [mailto:erminio.ottone_69@libero.it]
> > > > Sent: quarta-feira, 6 de Julho de 2011 18:26
> > > > To: loa@pi.nu; Rui Costa
> > > > Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
> > > > Subject: R: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> > > 05.txt>
> > > > (Proactive Connectivity Verification, Continuity Check and Remote
> > > > Defect indication for MPLS Transport Profile) to Proposed
> Standard
> > > >
> > > > >  Version -04 of the document was published June 28th.
> > > > >
> > > > >  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was
> > sent
> > > > >  June 29th.
> > > > >
> > > >
> > > > So when the WG LC to confirm the LC comment resolution has been
> > > > launched?
> > > >
> > > > The proto write-up says:
> > > >
> > > >             It has also passed a working roup call to verify that
> > LC
> > > > comments
> > > > were correctly with minor comments.
> > > >
> > > > It also says:
> > > >
> > > >             The comments has been
> > > >             carefully discussed between the authors and people
> > making
> > > > the
> > > > comments and
> > > >             has been resolved.
> > > >
> > > > But it seems that some comments have not been discussed with the
> > > > authors of
> > > > the comments. When ITU-T Q10/15 has been involved in discussing
> its
> > > > comments?
> > > >
> > > >
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Loa Andersson [mailto:loa@pi.nu]
> > > > Sent: quarta-feira, 6 de Julho de 2011 16:44
> > > > To: Rui Costa
> > > > Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
> > > > Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> > 05.txt>
> > > > (Proactive Connectivity Verification, Continuity Check and Remote
> > > > Defect indication for MPLS Transport Profile) to Proposed
> Standard
> > > >
> > > > All,
> > > >
> > > > Since someone has commented about the process used for resolving
> > > > questions on
> > > > draft-ietf-mpls-tp-cc-cv-rdi I am supplying some details below.
> > > >
> > > > The history of draft-ietf-mpls-tp-cc-cv-rdi working group review
> > > > process is:
> > > >
> > > > On February 3rd 2011 the working group last call was issued
> > > > on version -03
> > > >
> > > >       This was copied to the the Ad Hoc Team List
> > > >       and liaised to SG15 also on February 3rd
> > > >
> > > >       This working group last call ended om Feb 28
> > > >
> > > >
> > > >       On Feb 28 we also received a liaison with comments from
> SG15
> > > >
> > > >
> > > > The authors compiled a list of all comments received  as part the
> > > MPLS
> > > > working group last call; these  comments - and the intended
> > > resolution
> > > > -
> > > > is included in the meeting minutes from the Prague meeting:
> > > >
> > > >
> > > >       http://www.ietf.org/proceedings/80/slides/mpls-9.pdf
> > > >
> > > >
> > > >   During the IETF meeting in Prague, we agreed with the BFD
> working
> > > >   group to do a separate working group last callfor the BFD
> working
> > > >   group
> > > >
> > > > The (BFD) working group last call was started on March 30th and
> ran
> > > > for 13 days. The last call ended on April 11th.
> > > >
> > > >   The authors have since worked hard to resolve comments, some
> > > >   issue has been brought to the working group mailing list for
> > > >   resolution.
> > > >
> > > >   Version -04 of the document was published June 28th.
> > > >
> > > >   The publication request for draft-ietf-mpls-tp-cc-cv-rdi was
> > sent
> > > >   June 29th.
> > > >
> > > >   The AD review resulted in a "New ID needed" due to mostly
> > editorial
> > > >   comments. Version -05 was published on June 29 and the IETF
> last
> > > call
> > > >   started as soon as the new ID was avaialbe.
> > > >
> > > >   The current list of Last Call Comments resoltion is also
> avaiable
> > > at:
> > > >   http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
> > > >
> > > >   The list of issues that the authors kept very carefully, shows
> > > > without
> > > > doubt
> > > >   that no comments been ignored.
> > > >
> > > >   Loa
> > > >   mpls wg document shepherd
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: David Allan I [mailto:david.i.allan@ericsson.com]
> > > > Sent: quarta-feira, 6 de Julho de 2011 14:58
> > > > To: Rui Costa; ietf@ietf.org; IETF-Announce
> > > > Cc: mpls@ietf.org
> > > > Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> > 05.txt>
> > > > (Proactive Connectivity Verification, Continuity Check and Remote
> > > > Defect indication for MPLS Transport Profile) to Proposed
> Standard
> > > >
> > > > Hi Rui:
> > > >
> > > > The comments were not ignored, the resolution of the Q10 comments
> > as
> > > > well as those collected from the MPLS WG was presented at the
> last
> > > > IETF. My spreadsheet from which that report was generated and has
> > > been
> > > > augmented to include the BFD WG comments is available at
> > > > http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
> > > >
> > > > So you know...
> > > > Dave
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On
> > Behalf
> > > Of
> > > > Rui Costa
> > > > Sent: segunda-feira, 4 de Julho de 2011 23:03
> > > > To: ietf@ietf.org; IETF-Announce
> > > > Cc: mpls@ietf.org
> > > > Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> > 05.txt>
> > > > (Proactive Connectivity Verification, Continuity Check and Remote
> > > > Defect indication for MPLS Transport Profile) to Proposed
> Standard
> > > >
> > > > IMHO and for the record:
> > > >
> > > > ITU-T comments regarding this draft haven't been discussed with
> > ITU-T
> > > > but were simply ignored. No LS describing these comments'
> > resolution
> > > > was sent.
> > > >
> > > > Several service providers regarded this draft as not meeting
> their
> > > > transport networks' needs.
> > > >
> > > > [The v03 draft was published in Feb and went to WG LC.
> > > > The v04 draft addressing WG LC comments was published on the 28th
> > > June
> > > > (same date as the proto write-up).
> > > > When was the WG LC launched, to verify LC comments resolution?]
> > > >
> > > > Regards,
> > > > Rui
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On
> > Behalf
> > > Of
> > > > The IESG
> > > > Sent: quinta-feira, 30 de Junho de 2011 14:47
> > > > To: IETF-Announce
> > > > Cc: mpls@ietf.org
> > > > Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> > > > (Proactive Connectivity Verification, Continuity Check and Remote
> > > > Defect indication for MPLS Transport Profile) to Proposed
> Standard
> > > >
> > > >
> > > > The IESG has received a request from the Multiprotocol Label
> > > Switching
> > > > WG
> > > > (mpls) to consider the following document:
> > > > - 'Proactive Connectivity Verification, Continuity Check and
> Remote
> > > >    Defect indication for MPLS Transport Profile'
> > > >   <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally,
> comments
> > > may
> > > > be
> > > > sent to iesg@ietf.org instead. In either case, please retain the
> > > > beginning of the Subject line to allow automated sorting.
> > > >
> > > > Abstract
> > > >
> > > >    Continuity Check, Proactive Connectivity Verification and
> Remote
> > > >    Defect Indication functionalities are required for MPLS-TP
> OAM.
> > > >
> > > >    Continuity Check monitors the integrity of the continuity of
> the
> > > >    label switched path for any loss of continuity defect.
> > > Connectivity
> > > >    verification monitors the integrity of the routing of the
> label
> > > >    switched path between sink and source for any connectivity
> > issues.
> > > >    Remote defect indication enables an End Point to report, to
> its
> > > >    associated End Point, a fault or defect condition that it
> > detects
> > > on
> > > >    a pseudo wire, label switched path or Section.
> > > >
> > > >    This document specifies methods for proactive continuity
> check,
> > > >    continuity verification, and remote defect indication for
> MPLS-
> > TP
> > > >    label switched paths, pseudo wires and Sections using
> > > Bidirectional
> > > >    Forwarding Detection.
> > > >
> > > >
> > > > The file can be obtained via
> > > > http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
> > > >
> > > > IESG discussion can be tracked via
> > > > http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
> > > >
> > > >
> > > > No IPR declarations have been submitted directly on this I-D.
> > > > _______________________________________________
> > > > mpls mailing list
> > > > mpls@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/mpls
> > > >
> > > >
> > > > _______________________________________________
> > > > Ietf mailing list
> > > > Ietf@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/ietf
> > > > _______________________________________________
> > > > mpls mailing list
> > > > mpls@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/mpls
> > > _______________________________________________
> > > mpls mailing list
> > > mpls@ietf.org
> > > https://www.ietf.org/mailman/listinfo/mpls

From nurit.sprecher@nsn.com  Fri Jul  8 08:34:06 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 297F621F8B62; Fri,  8 Jul 2011 08:34:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.832
X-Spam-Level: 
X-Spam-Status: No, score=-2.832 tagged_above=-999 required=5 tests=[AWL=3.167,  BAYES_00=-2.599, J_CHICKENPOX_21=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 8b15yd6KOj4Z; Fri,  8 Jul 2011 08:34:04 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 8627421F8B5A; Fri,  8 Jul 2011 08:34:03 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p68FXwL7015803 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 8 Jul 2011 17:33:58 +0200
Received: from DEMUEXC047.nsn-intra.net ([10.159.32.93]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p68FXw9x004046; Fri, 8 Jul 2011 17:33:58 +0200
Received: from DEMUEXC014.nsn-intra.net ([10.150.128.25]) by DEMUEXC047.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 8 Jul 2011 17:33:55 +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: [mpls] LastCall:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt>	(Proactive	Connectivity	Verification, Continuity Check and Remote Defect	indicationfor	MPLS	Transport	Profile) to Proposed Standard
Date: Fri, 8 Jul 2011 17:33:53 +0200
Message-ID: <077E41CFFD002C4CAB7DFA4386A53264041913F1@DEMUEXC014.nsn-intra.net>
In-Reply-To: <BA2E2586-1B10-4954-93A2-E8EE9DF0427F@lucidvision.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] LastCall:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt>	(Proactive	Connectivity	Verification, Continuity Check and Remote Defect	indicationfor	MPLS	Transport	Profile) to Proposed Standard
Thread-Index: Acw9g4ClkK2Lfv4zTLmOgxFNsD9RdAAADFOA
References: <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B6BC@INOAVREX11.ptin.corpPT.com><6D3D47CB84BDE349BC23BF1C94E316E4405A7550DE@EMV62-UKRD.domain1.systemhost.net> <BA2E2586-1B10-4954-93A2-E8EE9DF0427F@lucidvision.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext Thomas Nadeau" <tnadeau@lucidvision.com>, <neil.2.harrison@bt.com>
X-OriginalArrivalTime: 08 Jul 2011 15:33:55.0886 (UTC) FILETIME=[72DB64E0:01CC3D84]
Cc: mpls@ietf.org, ietf@ietf.org, ietf-announce@ietf.org, 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: Fri, 08 Jul 2011 15:34:06 -0000

Hi,
Just to make it clear, this is not a discussion on the requirements. I
would like to encourage this kind of discussion but in the right
context.
The CC-CV-RDI draft aims to satisfy the OAM requirements which are
specified in RFC 5860. One of the requirements there is to provide a
tool for CC as well as for CV.=20
In the context of this LC, we should focus now on the proposed solution.
Best regards,
Nurit

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
ext Thomas Nadeau
Sent: Friday, July 08, 2011 6:27 PM
To: neil.2.harrison@bt.com
Cc: mpls@ietf.org; ietf@ietf.org; ietf-announce@ietf.org;
stbryant@cisco.com
Subject: Re: [mpls] LastCall: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
(Proactive Connectivity Verification,Continuity Check and Remote Defect
indicationfor MPLS Transport Profile) to Proposed Standard


On Jul 8, 2011, at 3:15 AM, <neil.2.harrison@bt.com> wrote:

> Got to say I agree with Rui on much of what he says here.  And I
absolutely resonate with his point on the need for simplicity.  The
reason OAM needs to be as simple as possible is because it must be super
reliable....we do not want to consciously build in weaknesses, esp
unnecessary ones.... this also implies minimal config.  We could all do
better on this.  For example:
>=20
> -       Rui is dead right a CC function is fairly useless, we only
need a CV function...the ATM OAM in I.610 suffers from this problem (and
few others like AIS and the assumed use of request/response MLT to
diagnose leaking/mismerging traffic...request/response OAM won't work
with unidirectional defects).

	While you are entitled to your opinion, I personally think there
are enough requirements elsewhere to have both CC and CV functions.  But
we digress. Are you actually asking that the CC functionality be removed
from the draft or just making a general comment?

> -       all packet layer networks should not have an AIS OAM
message....very obvious for the cl-ps mode of course.  The co-ps mode is
also not like the co-cs mode.  One has to consciously manufacture AIS
messages and target them to specific clients in the co-ps mode....who
may have taken action in their own layer network and 'moved elsewhere'
anyway, ie a total waste of time now.  AIS is actually unnecessary wrt
providing information anyway, it simply represents an in-built weakness
of just something else to go wrong which itself will create problems.

	What does that comment have to do with the actual draft in
question?

> -       creating preconfigured TCM sublayers is just asking for
trouble IMO.  It is far smarter to simply create a single end-end OAM CV
(and when required PM) flow and tap this off at intermediate nodes on
the *rare* occasions one wants to do.

	Again, what does this have to do with the actual draft in
question?

	--tom




>=20
> regards, Neil
>=20
> This email contains BT information, which may be privileged or
confidential.
> It's meant only for the individual(s) or entity named above. If you're
not the intended
> recipient, note that disclosing, copying, distributing or using this
information
> is prohibited. If you've received this email in error, please let me
know immediately
> on the email address above. Thank you.
> We monitor our email system, and may record your emails.
> British Telecommunications plc
> Registered office: 81 Newgate Street London EC1A 7AJ
> Registered in England no: 1800000
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>> -----Original Message-----
>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
Of
>> Rui Costa
>> Sent: 08 July 2011 01:15
>> To: David Allan I; Stewart Bryant
>> Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
>> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
>> (Proactive Connectivity Verification, Continuity Check and Remote
>> Defect indication for MPLS Transport Profile) to Proposed Standard
>>=20
>> David,
>>=20
>> Reading something, keeping it on record, without effect in the draft
>> and "ignoring comments" have IMHO similar outcomes. As author of the
>> draft you are free to do it. These standards have a great impact in
our
>> work, so i'm also free to write what i did.
>>=20
>>=20
>>=20
>>=20
>> Stewart,
>>=20
>> My technical concerns regarding this draft were expressed...
>> ...in the (ITU-T -> IETF, Feb/2011) liaison regarding it (LS281, i
>> believe);
>> ...in operators' meetings' that took place during ITU-T's Feb/2011
>> plenary meeting;
>> ...in a comparison session that took place during that same ITU-T
>> meeting.
>> Some:
>>=20
>> CC/CV
>> I don't understand the need for 2 types of packets: a single type
>> allows CC; mismatching identifiers in the same CC packets allow CV.
>> Besides adding complexity, we whether always activate both or
>> potentiate undetected mismerges.
>> (BTW: can't understand how we propose one ACH codepoint to CC,
another
>> for CV, [counting other drafts, another for frame loss ...] but don't
>> consider assigning 1 single ACH protocol identifier codepoint as
>> requested by ITU-T)
>>=20
>> Uni P2P / P2MP
>> I can't see how BFD will support unidir and hence P2MP other than...
>>=20
>> ...eliminating the session "state variable" (down, init, up), aiming
>> just the state variables we really need, bringing us to something
>> similar to 1731, eventually with other bits on the wire or...
>> ...using IP to create the reverse way, which we cannot assume per
>> requirements;
>> Will we create a complete different tool for that?
>> (BFD's B=3D"bidirectional")
>>=20
>> Provisioning list
>> This is an MPLS profile/subset (and i heard) achievable through a
>> particular configuration. So, i expect each draft-ietf-mpls-TP-* to
>> focus on that profile/configuration. However, i keep seeing
references
>> f.i. to IP encapsulations unexpected under TP's OAM.
>> I don't thus understand what the aim is: do we expect this in TP, are
>> we talking about MPLS in general?... The TP profile is never quite
>> delimited.
>> Does chapter 4 contain ALL the configurable parameters list agreed to
>> provide in the comparison session?
>>=20
>> Backwards compatibility
>> This was the main argument risen to ground MPLS-TP OAM on BFD. It's
not
>> a better argument than grounding MPLS-TP OAM on 1731 due to its ETH
>> deployment plus coherence with SDH, OTN, as defended by ITU-T.
>> For reasons like the above, however, MPLS-TP BFD won't be backwards
>> compatible with previous BFD (even considering just CC/CV). They
don't
>> even share the same codepoint.
>>=20
>> Simplicity
>> Whether we look to PDH, SDH, OTN or ETH, ITU-T's approach to CC is
>> simpler: in each flow, a standard defined nr of constant heartbeat
>> signals (with standard constant or provisioned period - no
>> auto/negotiated -) means OK. A standard defined number of misses
means
>> lost Rx connection. An RDI, the only articulation between Rx and Tx
>> flows, meaningful in bidirectional applications, allows each pear to
>> identify Tx problems.
>> This OAM simplicity is the key for reliable fail finger pointing,
>> performance reports and protection. Also to allow scaling, more
>> implementation opportunities/manufacturers, which is valuable for
>> operators.
>>=20
>>=20
>> IMHO, between your MPLS-TP view and MPLS/IP, it becomes more and more
>> difficult to tell which is which.
>>=20
>> Regards,
>> Rui
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>> -----Original Message-----
>> From: David Allan I [mailto:david.i.allan@ericsson.com]
>> Sent: quarta-feira, 6 de Julho de 2011 19:25
>> To: erminio.ottone_69@libero.it; Rui Costa; ietf@ietf.org; IETF-
>> Announce
>> Cc: mpls@ietf.org
>> Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
>> 05.txt> (Proactive Connectivity Verification, Continuity Check and
>> Remote Defect indication for MPLS Transport Profile) to Proposed
>> Standard
>>=20
>> Hi Erminio:
>>=20
>> <snipped>
>>> Several service providers regarded this draft as not meeting their
>>> transport networks' needs.
>>=20
>> E> This is a true statement: the solution in this draft is useless
for
>> many MPLS- TP deployments.
>>=20
>> The two statements do not necessarily follow.
>>=20
>> What we established during discussions at the SG15 plenary in
February
>> was that the issue some service providers had was that the IETF BFD
>> solution exceeded their requirements in that there was additional
>> functionality they did not see a need for, and that they considered
any
>> additional functionality parasitic.
>>=20
>> However this is a consequence of adapting an existing technology to a
>> new application. I do not see any way around that. And the entire
joint
>> project was based on the premise of engineering re-use not greenfield
>> design. That is what it said on the tin up front, and IMO why when
the
>> IETF started down this path packet transport transitioned from being
a
>> minority sport to mainstream, so it is a bit late to cry foul....
>>=20
>> My 2 cents
>> Dave
>>=20
>>=20
>>=20
>>=20
>> -----Original Message-----
>> From: David Allan I [mailto:david.i.allan@ericsson.com]
>> Sent: quarta-feira, 6 de Julho de 2011 18:36
>> To: erminio.ottone_69@libero.it; loa@pi.nu; Rui Costa
>> Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
>> Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
>> 05.txt> (Proactive Connectivity Verification, Continuity Check and
>> Remote Defect indication for MPLS Transport Profile) to Proposed
>> Standard
>>=20
>> Hi Erminio:
>>=20
>> Two of the three document editors were present at SG15 plenary in
>> February where the comments originated. The revised meeting schedule
>> resulted in a day spent going through the document with the editors.
>> IMO there were lots of discussion and legitimate issues with the
>> document identified and corrected so it was a useful session. The
>> liaison of same was in many ways *after the fact*.
>>=20
>> Cheers
>> Dave
>>=20
>>=20
>>=20
>>=20
>> -----Original Message-----
>> From: erminio.ottone_69@libero.it
[mailto:erminio.ottone_69@libero.it]
>> Sent: quarta-feira, 6 de Julho de 2011 18:34
>> To: Rui Costa; ietf@ietf.org; IETF-Announce
>> Cc: mpls@ietf.org
>> Subject: R: Re: [mpls] Last Call:
<draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
>> (Proactive Connectivity Verification, Continuity Check and Remote
>> Defect indication for MPLS Transport Profile) to Proposed Standard
>>=20
>> The way this draft has been developed is a bit strange.
>>=20
>> The poll for its adoption as a WG document was halted by the MPLS WG
>> chair
>> because "it is not possible to judge consensus":
>>=20
>> http://www.ietf.org/mail-archive/web/mpls/current/msg04502.html
>>=20
>> The lack of consensus was motivated by serious technical concerns
>> raised by
>> several transport experts during the poll.
>>=20
>> Nevertheless the MPLS WG chair decided to adopt the draft as a WG
>> document:
>>=20
>> http://www.ietf.org/mail-archive/web/mpls/current/msg04512.html
>>=20
>> After several WG revisions and WG LCs, the technical issues have not
>> been
>> resolved.
>>=20
>>> Several service providers regarded this draft as not meeting their
>> transport
>> networks' needs.
>>=20
>> This is a true statement: the solution in this draft is useless for
>> many MPLS-
>> TP deployments.
>>=20
>>=20
>> -----Original Message-----
>> From: erminio.ottone_69@libero.it
[mailto:erminio.ottone_69@libero.it]
>> Sent: quarta-feira, 6 de Julho de 2011 18:26
>> To: loa@pi.nu; Rui Costa
>> Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
>> Subject: R: Re: [mpls] Last Call:
<draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
>> (Proactive Connectivity Verification, Continuity Check and Remote
>> Defect indication for MPLS Transport Profile) to Proposed Standard
>>=20
>>> Version -04 of the document was published June 28th.
>>>=20
>>> The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
>>> June 29th.
>>>=20
>>=20
>> So when the WG LC to confirm the LC comment resolution has been
>> launched?
>>=20
>> The proto write-up says:
>>=20
>>            It has also passed a working roup call to verify that LC
>> comments
>> were correctly with minor comments.
>>=20
>> It also says:
>>=20
>>            The comments has been
>>            carefully discussed between the authors and people making
>> the
>> comments and
>>            has been resolved.
>>=20
>> But it seems that some comments have not been discussed with the
>> authors of
>> the comments. When ITU-T Q10/15 has been involved in discussing its
>> comments?
>>=20
>>=20
>>=20
>>=20
>> -----Original Message-----
>> From: Loa Andersson [mailto:loa@pi.nu]
>> Sent: quarta-feira, 6 de Julho de 2011 16:44
>> To: Rui Costa
>> Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
>> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
>> (Proactive Connectivity Verification, Continuity Check and Remote
>> Defect indication for MPLS Transport Profile) to Proposed Standard
>>=20
>> All,
>>=20
>> Since someone has commented about the process used for resolving
>> questions on
>> draft-ietf-mpls-tp-cc-cv-rdi I am supplying some details below.
>>=20
>> The history of draft-ietf-mpls-tp-cc-cv-rdi working group review
>> process is:
>>=20
>> On February 3rd 2011 the working group last call was issued
>> on version -03
>>=20
>>      This was copied to the the Ad Hoc Team List
>>      and liaised to SG15 also on February 3rd
>>=20
>>      This working group last call ended om Feb 28
>>=20
>>=20
>>      On Feb 28 we also received a liaison with comments from SG15
>>=20
>>=20
>> The authors compiled a list of all comments received  as part the
MPLS
>> working group last call; these  comments - and the intended
resolution
>> -
>> is included in the meeting minutes from the Prague meeting:
>>=20
>>=20
>>      http://www.ietf.org/proceedings/80/slides/mpls-9.pdf
>>=20
>>=20
>>  During the IETF meeting in Prague, we agreed with the BFD working
>>  group to do a separate working group last callfor the BFD working
>>  group
>>=20
>> The (BFD) working group last call was started on March 30th and ran
>> for 13 days. The last call ended on April 11th.
>>=20
>>  The authors have since worked hard to resolve comments, some
>>  issue has been brought to the working group mailing list for
>>  resolution.
>>=20
>>  Version -04 of the document was published June 28th.
>>=20
>>  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
>>  June 29th.
>>=20
>>  The AD review resulted in a "New ID needed" due to mostly editorial
>>  comments. Version -05 was published on June 29 and the IETF last
call
>>  started as soon as the new ID was avaialbe.
>>=20
>>  The current list of Last Call Comments resoltion is also avaiable
at:
>>  http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
>>=20
>>  The list of issues that the authors kept very carefully, shows
>> without
>> doubt
>>  that no comments been ignored.
>>=20
>>  Loa
>>  mpls wg document shepherd
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>> -----Original Message-----
>> From: David Allan I [mailto:david.i.allan@ericsson.com]
>> Sent: quarta-feira, 6 de Julho de 2011 14:58
>> To: Rui Costa; ietf@ietf.org; IETF-Announce
>> Cc: mpls@ietf.org
>> Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
>> (Proactive Connectivity Verification, Continuity Check and Remote
>> Defect indication for MPLS Transport Profile) to Proposed Standard
>>=20
>> Hi Rui:
>>=20
>> The comments were not ignored, the resolution of the Q10 comments as
>> well as those collected from the MPLS WG was presented at the last
>> IETF. My spreadsheet from which that report was generated and has
been
>> augmented to include the BFD WG comments is available at
>> http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
>>=20
>> So you know...
>> Dave
>>=20
>>=20
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
Of
>> Rui Costa
>> Sent: segunda-feira, 4 de Julho de 2011 23:03
>> To: ietf@ietf.org; IETF-Announce
>> Cc: mpls@ietf.org
>> Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
>> (Proactive Connectivity Verification, Continuity Check and Remote
>> Defect indication for MPLS Transport Profile) to Proposed Standard
>>=20
>> IMHO and for the record:
>>=20
>> ITU-T comments regarding this draft haven't been discussed with ITU-T
>> but were simply ignored. No LS describing these comments' resolution
>> was sent.
>>=20
>> Several service providers regarded this draft as not meeting their
>> transport networks' needs.
>>=20
>> [The v03 draft was published in Feb and went to WG LC.
>> The v04 draft addressing WG LC comments was published on the 28th
June
>> (same date as the proto write-up).
>> When was the WG LC launched, to verify LC comments resolution?]
>>=20
>> Regards,
>> Rui
>>=20
>>=20
>> -----Original Message-----
>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
Of
>> The IESG
>> Sent: quinta-feira, 30 de Junho de 2011 14:47
>> To: IETF-Announce
>> Cc: mpls@ietf.org
>> Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
>> (Proactive Connectivity Verification, Continuity Check and Remote
>> Defect indication for MPLS Transport Profile) to Proposed Standard
>>=20
>>=20
>> The IESG has received a request from the Multiprotocol Label
Switching
>> WG
>> (mpls) to consider the following document:
>> - 'Proactive Connectivity Verification, Continuity Check and Remote
>>   Defect indication for MPLS Transport Profile'
>>  <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> as a Proposed Standard
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to
the
>> ietf@ietf.org mailing lists by 2011-07-14. Exceptionally, comments
may
>> be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>   Continuity Check, Proactive Connectivity Verification and Remote
>>   Defect Indication functionalities are required for MPLS-TP OAM.
>>=20
>>   Continuity Check monitors the integrity of the continuity of the
>>   label switched path for any loss of continuity defect. Connectivity
>>   verification monitors the integrity of the routing of the label
>>   switched path between sink and source for any connectivity issues.
>>   Remote defect indication enables an End Point to report, to its
>>   associated End Point, a fault or defect condition that it detects
on
>>   a pseudo wire, label switched path or Section.
>>=20
>>   This document specifies methods for proactive continuity check,
>>   continuity verification, and remote defect indication for MPLS-TP
>>   label switched paths, pseudo wires and Sections using Bidirectional
>>   Forwarding Detection.
>>=20
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>>=20
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>=20
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>=20

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From behcetsarikaya@yahoo.com  Fri Jul  8 12:10:52 2011
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1FC021F86DA for <ietf@ietfa.amsl.com>; Fri,  8 Jul 2011 12:10:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.199
X-Spam-Level: 
X-Spam-Status: No, score=-1.199 tagged_above=-999 required=5 tests=[AWL=-1.200, 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 7RaSf3YTQMRI for <ietf@ietfa.amsl.com>; Fri,  8 Jul 2011 12:10:46 -0700 (PDT)
Received: from nm8-vm0.bullet.mail.sp2.yahoo.com (nm8-vm0.bullet.mail.sp2.yahoo.com [98.139.91.194]) by ietfa.amsl.com (Postfix) with SMTP id E5DD821F8C60 for <ietf@ietf.org>; Fri,  8 Jul 2011 12:10:45 -0700 (PDT)
Received: from [98.139.91.66] by nm8.bullet.mail.sp2.yahoo.com with NNFMP; 08 Jul 2011 19:10:42 -0000
Received: from [98.139.91.24] by tm6.bullet.mail.sp2.yahoo.com with NNFMP; 08 Jul 2011 19:10:42 -0000
Received: from [127.0.0.1] by omp1024.mail.sp2.yahoo.com with NNFMP; 08 Jul 2011 19:10:42 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 579457.45322.bm@omp1024.mail.sp2.yahoo.com
Received: (qmail 37312 invoked by uid 60001); 8 Jul 2011 19:10:42 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1310152242; bh=2z8Emm1AK0Fqt/CUAxbVUXeadKD8veaEZjKW3dgFwqA=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=Tte2KOQm8WHetv3rTYGLuBGF1Q6wJLnz/BkYmlOEnokM/QxAUl+ckD5D3Kk/M2ogM/J51v/OlZXUa6DQQGB7IkvIzsWJwJ30k17w+fYidutQN733gjHyETI7SwAFephdPcZDmZCh+VRSVrmVtI+6H5lLbX+FPGpO5eRFdOm7AIs=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=pj8PUFPO/yr5uDWkAqILljUmlfX2TZXg/k84+UHS3a/Y99pDmtA0Ikw5yXx34u6OK/TOcUzjiplBQUON6DnPEN2VTVxxvJj50TU7vjWxwA19UfsuogrKWhJp54mKlLPxpkRHM7ArZNh4fLNDSSs/jl1nTRZLO6+Vt9cWRO9bYnA=;
X-YMail-OSG: 7UK.aCsVM1nUNnHAC9YRxxoBCVQT0owkpJAR4PFKZyqtEo0 YzrzqlSZzLVkn7fMAJBSYGJfFDcrbFTdzs3a9Wj3phLoiyIuD15QIkWN5EHR LxnU5TlJ2J7VgyRwZiqbnjLaDypFVDGXVWgYTSRWURqFfGdWP3ySpxz5BR57 vtgRL0522AupNv5_Fl.3uE9UuDhaW_1nseOAvGhLa4HOU6hBTAb_7FldCI0e YPlYoCLfF4m9iPQh1f11ohnpqmVF3HKfKNVjfgLfS2sxNBTL4RQr28Q8HNDc vqAdop0GEQ0Fjdg5bNHiWW.eG9TAhhc8GJODOeCo4wpkH5gn.CzSlcrxSATC qWuilmZaKqmJImHMYmsc_lDeOXFz0hujkM8S8FHTC1r6mZFNa0FASujWH6FF h.zHYkw--
Received: from [50.58.7.243] by web111401.mail.gq1.yahoo.com via HTTP; Fri, 08 Jul 2011 12:10:41 PDT
X-Mailer: YahooMailRC/572 YahooMailWebService/0.8.112.307740
References: <061F84F2-E9A8-4A37-A506-7605391D837D@cisco.com> <41794549-D193-43AF-86AB-27B044B12FA9@muada.com>
Message-ID: <1310152241.17290.YahooMailRC@web111401.mail.gq1.yahoo.com>
Date: Fri, 8 Jul 2011 12:10:41 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: reading drafts on an ipad
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <41794549-D193-43AF-86AB-27B044B12FA9@muada.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2011 19:10:53 -0000

-
> On 6 jul 2011, at 17:38, Cullen Jennings wrote:
> 
> > Has anyone found a  particularly good solution to reading drafts on an ipad? 

> 
> I saw xml2rfc  now has the option to convert to epub, which would make it easy 
>to read drafts  on the iPad and other mobile devices, but unfortunately when I 
>tried to convert  a draft it didn't work.
> 

Same here. It gives a bunch of error messages. Can someone please report it to 
xml2rfc mailing list?


Behcet

From brian.e.carpenter@gmail.com  Fri Jul  8 16:35:51 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 2EC441F0C38; Fri,  8 Jul 2011 16:35:51 -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=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 xig4CWbMqaQ7; Fri,  8 Jul 2011 16:35:50 -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 3811A1F0C39; Fri,  8 Jul 2011 16:35:50 -0700 (PDT)
Received: by fxe4 with SMTP id 4so3170341fxe.27 for <multiple recipients>; Fri, 08 Jul 2011 16:35:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=4UZCi/q3qCKTNw7ieuFfJl0zMF0M+vrx73553QoYQDA=; b=VkmISAwUWw5ICNVtffxHgpU55gdWnPoTjyn1UPsNDJ01gzxVViCfryhOWSq5GMXMrO uRpAd+Eqx3y8silaB2GbUusmOdjOcy5owCtehufegKhjNUuUEXqPTfmwl4Btat1PW4gg 7Z9byDibhwcA539/pYXwoxSZYMdNVwRbZ90bM=
Received: by 10.223.59.17 with SMTP id j17mr767105fah.120.1310168149294; Fri, 08 Jul 2011 16:35:49 -0700 (PDT)
Received: from ?IPv6:2001:388:f000::35? ([2001:388:f000::35]) by mx.google.com with ESMTPS id u20sm5522220fac.18.2011.07.08.16.35.44 (version=SSLv3 cipher=OTHER); Fri, 08 Jul 2011 16:35:48 -0700 (PDT)
Message-ID: <4E179442.3050405@gmail.com>
Date: Sat, 09 Jul 2011 11:35:30 +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: =?UTF-8?B?Um9nZXIgSsO4cmdlbnNlbg==?= <rogerj@gmail.com>
Subject: Dropping 2002::/16 considered very harmful
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net>	<CAKFn1SGvL2KQ3KVoR6cE8Q=Mqb+zjXL_uVAhdic_nOHC=f_q1A@mail.gmail.com> <CAKFn1SEGVahkCSmVt0-QPAxFSVftpvcwCNcpnznfQiPyBH1Jww@mail.gmail.com>
In-Reply-To: <CAKFn1SEGVahkCSmVt0-QPAxFSVftpvcwCNcpnznfQiPyBH1Jww@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "v6ops@ietf.org" <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, 08 Jul 2011 23:35:51 -0000

On 2011-07-08 19:16, Roger J=C3=B8rgensen wrote:
> Guess I should clearify something, the thing I am considering are to
> drop all 2002::/16 addresses hard, of course preferable return a
> correct error messages to.

This is an awesomely bad idea. As explained in the approved advisory
document, it makes things worse for everybody (the user, the content
provider, and the unfortunate person answering calls from either of
them at the help desk).

On the contrary - it's in everyone's interests to have the return
path working. Once a user manages to get a packet to the content
provider, everybody suffers if the return path fails.

(However, if you are announcing a route to 2002::/16, it must lead
to a relay that will relay all 6to4 packets, with no form of ACL).

   Brian


From cb.list6@gmail.com  Fri Jul  8 16:48:02 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 9512321F871A; Fri,  8 Jul 2011 16:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.139
X-Spam-Level: 
X-Spam-Status: No, score=-3.139 tagged_above=-999 required=5 tests=[AWL=0.459,  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 OXLfD+rcf6Cc; Fri,  8 Jul 2011 16:48:01 -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 6D46121F86E2; Fri,  8 Jul 2011 16:48:01 -0700 (PDT)
Received: by wyj26 with SMTP id 26so1869957wyj.31 for <multiple recipients>; Fri, 08 Jul 2011 16:48:00 -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=mj/fDV+H6wjpnvRMQTeJIv7L04T8pIHAFIunlCdenbw=; b=czF5m3L0aETsZj/lCjHf4sHBFhY9jFvw+Ebu+UTSX7jS2dm+orXThIWhKW/j04YWVu rbQJBJ0GoePeyUkESoVuuLNxe01fAjPABQHaN+e19NDRY7gVeq2CM7rle90mWmjchQO8 MOlXSoYwAmfXGqlo3nRnprzX856MANBmJxN4s=
MIME-Version: 1.0
Received: by 10.216.78.144 with SMTP id g16mr2139608wee.64.1310168878894; Fri, 08 Jul 2011 16:47:58 -0700 (PDT)
Received: by 10.216.39.83 with HTTP; Fri, 8 Jul 2011 16:47:58 -0700 (PDT)
Received: by 10.216.39.83 with HTTP; Fri, 8 Jul 2011 16:47:58 -0700 (PDT)
In-Reply-To: <4E179442.3050405@gmail.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F3507EDA@EMBX01-WF.jnpr.net> <CAKFn1SGvL2KQ3KVoR6cE8Q=Mqb+zjXL_uVAhdic_nOHC=f_q1A@mail.gmail.com> <CAKFn1SEGVahkCSmVt0-QPAxFSVftpvcwCNcpnznfQiPyBH1Jww@mail.gmail.com> <4E179442.3050405@gmail.com>
Date: Fri, 8 Jul 2011 16:47:58 -0700
Message-ID: <CAD6AjGRiU4-a+Lq7LSLMfD9UOaS0HQYzGE7Ze=dtrE3DYGHqrA@mail.gmail.com>
Subject: Re: Dropping 2002::/16 considered very harmful
From: Cameron Byrne <cb.list6@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=000e0ce0ce089f507504a797767d
Cc: IETF Discussion <ietf@ietf.org>, "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: Fri, 08 Jul 2011 23:48:02 -0000

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

I, for one, am not interested talking about 6to4 anymore.
On Jul 8, 2011 4:36 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
wrote:
> On 2011-07-08 19:16, Roger J=F8rgensen wrote:
>> Guess I should clearify something, the thing I am considering are to
>> drop all 2002::/16 addresses hard, of course preferable return a
>> correct error messages to.
>
> This is an awesomely bad idea. As explained in the approved advisory
> document, it makes things worse for everybody (the user, the content
> provider, and the unfortunate person answering calls from either of
> them at the help desk).
>
> On the contrary - it's in everyone's interests to have the return
> path working. Once a user manages to get a packet to the content
> provider, everybody suffers if the return path fails.
>
> (However, if you are announcing a route to 2002::/16, it must lead
> to a relay that will relay all 6to4 packets, with no form of ACL).
>
> Brian
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

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

<p>I, for one, am not interested talking about 6to4 anymore. </p>
<div class=3D"gmail_quote">On Jul 8, 2011 4:36 PM, &quot;Brian E Carpenter&=
quot; &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@=
gmail.com</a>&gt; wrote:<br type=3D"attribution">&gt; On 2011-07-08 19:16, =
Roger J=F8rgensen wrote:<br>
&gt;&gt; Guess I should clearify something, the thing I am considering are =
to<br>&gt;&gt; drop all 2002::/16 addresses hard, of course preferable retu=
rn a<br>&gt;&gt; correct error messages to.<br>&gt; <br>&gt; This is an awe=
somely bad idea. As explained in the approved advisory<br>
&gt; document, it makes things worse for everybody (the user, the content<b=
r>&gt; provider, and the unfortunate person answering calls from either of<=
br>&gt; them at the help desk).<br>&gt; <br>&gt; On the contrary - it&#39;s=
 in everyone&#39;s interests to have the return<br>
&gt; path working. Once a user manages to get a packet to the content<br>&g=
t; provider, everybody suffers if the return path fails.<br>&gt; <br>&gt; (=
However, if you are announcing a route to 2002::/16, it must lead<br>&gt; t=
o a relay that will relay all 6to4 packets, with no form of ACL).<br>
&gt; <br>&gt;    Brian<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/list=
info/ietf">https://www.ietf.org/mailman/listinfo/ietf</a><br>
</div>

--000e0ce0ce089f507504a797767d--

From mail@sabahattin-gucukoglu.com  Sat Jul  9 06:51:49 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 8034821F8575 for <ietf@ietfa.amsl.com>; Sat,  9 Jul 2011 06:51:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.423
X-Spam-Level: 
X-Spam-Status: No, score=-1.423 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HOST_MISMATCH_COM=0.311, 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 l0nd6X+GX2wd for <ietf@ietfa.amsl.com>; Sat,  9 Jul 2011 06:51:49 -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 3AA5C21F86E5 for <ietf@ietf.org>; Sat,  9 Jul 2011 06:51:47 -0700 (PDT)
Received: from Mintaka.sabahattin-gucukoglu.com ([::ffff:127.0.0.1]:59663) by Mintaka.sabahattin-gucukoglu.com with [XMail 1.27 ESMTP Server] id <S37E17> for <ietf@ietf.org> from <mail@sabahattin-gucukoglu.com>; Sat, 9 Jul 2011 14:51:46 +0100
Received: from [192.168.1.20] (host213-123-192-30.in-addr.btopenworld.com [213.123.192.30]) (using SMTP over TLS) by Mintaka.sabahattin-gucukoglu.com (tmda-ofmipd) with ESMTP; Sat, 09 Jul 2011 14:51:44 +0100
Subject: Re: Spurious MTU in IPv6 RAs Where WAN is PPPoE
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <48BBAE96-4557-436F-A8CC-699BA1E163CF@sabahattin-gucukoglu.com>
Date: Sat, 9 Jul 2011 14:51:43 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <C4293C11-766E-4E8E-9B77-2F9C5E19BC88@sabahattin-gucukoglu.com>
References: <357D4DFB-95CF-43B3-AABD-7C237AC7B6D7@sabahattin-gucukoglu.com> <CEE67A11-B91B-4BAD-B75F-19AFC25CFDFE@apple.com> <48BBAE96-4557-436F-A8CC-699BA1E163CF@sabahattin-gucukoglu.com>
To: james woodyatt <jhw@apple.com>
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
Cc: IPv6 Apple Developers <ipv6-dev@lists.apple.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Sabahattin Gucukoglu <mail-dated-1312811506.c51220@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: Sat, 09 Jul 2011 13:51:49 -0000

On 6 Jul 2011, at 22:52, Sabahattin Gucukoglu wrote:
On 6 Jul 2011, at 19:03, james woodyatt wrote:
>> You're invited to file a report with <http://bugreport.apple.com> =
about this.  Be sure to explain why fixing the broken path MTU discovery =
in the network is not an option and requiring the AirPort user to know =
enough about IPv6 router advertisement MTU options to set the value =
properly is an appropriate mitigation.
>=20
> Thank you, and what should the severity of the bug be?

This is bug #9739722, Airport: Configurable IPv6 RA link-MTU or MSS =
Clamping.  Severity 2.

Hurricane Electric very generously lowered my tunnel's MTU to 1476 bytes =
IPv6 payload, so I'm now back on the IPv6 Internet again.  (Yay!)

There is still one important detail to clear up, though.  My ISP, BT =
Infinity Business in the UK, seems to be ensuring that its links do not =
overflow by "Clamping" the MSS option in TCPv4 SYN packets to 1400, and =
no sight of ICMPv4 "Datagram too large and DF set" messages.  Can I take =
it for granted that you didn't choose the same value, or do a similar =
terrible thing, in the Airport products?  I don't have any other PPPoE =
servers to try it on.

Cheers,
Sabahattin

From julian.reschke@gmx.de  Sat Jul  9 07:08:21 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 ECD8F21F86A1 for <ietf@ietfa.amsl.com>; Sat,  9 Jul 2011 07:08:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.66
X-Spam-Level: 
X-Spam-Status: No, score=-104.66 tagged_above=-999 required=5 tests=[AWL=-2.061, 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 mMFcb8-yAVfw for <ietf@ietfa.amsl.com>; Sat,  9 Jul 2011 07:08:21 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id D4A3421F869C for <ietf@ietf.org>; Sat,  9 Jul 2011 07:08:20 -0700 (PDT)
Received: (qmail invoked by alias); 09 Jul 2011 14:08:19 -0000
Received: from p508FA64C.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.166.76] by mail.gmx.net (mp006) with SMTP; 09 Jul 2011 16:08:19 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19igDZBDpFijOzYiXU2D5oTXGUjNab+7COU6o+O/O 2+YJ1pTK/K+iPD
Message-ID: <4E1860C2.5050309@gmx.de>
Date: Sat, 09 Jul 2011 16:08:02 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Behcet Sarikaya <sarikaya@ieee.org>
Subject: Re: reading drafts on an ipad
References: <061F84F2-E9A8-4A37-A506-7605391D837D@cisco.com> <41794549-D193-43AF-86AB-27B044B12FA9@muada.com> <1310152241.17290.YahooMailRC@web111401.mail.gq1.yahoo.com>
In-Reply-To: <1310152241.17290.YahooMailRC@web111401.mail.gq1.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, Behcet Sarikaya <behcetsarikaya@yahoo.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, 09 Jul 2011 14:08:22 -0000

On 2011-07-08 21:10, Behcet Sarikaya wrote:
>> I saw xml2rfc  now has the option to convert to epub, which would make it easy
>> to read drafts  on the iPad and other mobile devices, but unfortunately when I
>> tried to convert  a draft it didn't work.
>>
>
> Same here. It gives a bunch of error messages. Can someone please report it to
> xml2rfc mailing list?
> ...

My own implementation is available here: 
<http://greenbytes.de/tech/webdav/rfc2629xslt.zip>. See 
<http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html#output.epub> 
for installation requirements and instructions.

Best regards, Julian

From iljitsch@muada.com  Sun Jul 10 05:52:58 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 DB72621F8659 for <ietf@ietfa.amsl.com>; Sun, 10 Jul 2011 05:52:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.412
X-Spam-Level: 
X-Spam-Status: No, score=-102.412 tagged_above=-999 required=5 tests=[AWL=0.188, 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 T5+SSjHsKIFZ for <ietf@ietfa.amsl.com>; Sun, 10 Jul 2011 05:52:58 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [IPv6:2001:1af8:3100:a006:1::]) by ietfa.amsl.com (Postfix) with ESMTP id 4C8A121F8551 for <ietf@ietf.org>; Sun, 10 Jul 2011 05:52:57 -0700 (PDT)
Received: from [IPv6:2001:470:1f0b:1289:223:12ff:fe56:36b2] ([IPv6:2001:470:1f0b:1289:223:12ff:fe56:36b2]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id p6ACrKgG033379 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 10 Jul 2011 14:53:21 +0200 (CEST) (envelope-from iljitsch@muada.com)
Subject: Re: Spurious MTU in IPv6 RAs Where WAN is PPPoE
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: <C4293C11-766E-4E8E-9B77-2F9C5E19BC88@sabahattin-gucukoglu.com>
Date: Sun, 10 Jul 2011 14:52:49 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7E362046-C8D4-4160-9865-ABFB1B3C767C@muada.com>
References: <357D4DFB-95CF-43B3-AABD-7C237AC7B6D7@sabahattin-gucukoglu.com> <CEE67A11-B91B-4BAD-B75F-19AFC25CFDFE@apple.com> <48BBAE96-4557-436F-A8CC-699BA1E163CF@sabahattin-gucukoglu.com> <C4293C11-766E-4E8E-9B77-2F9C5E19BC88@sabahattin-gucukoglu.com>
To: Sabahattin Gucukoglu <mail-dated-1312811506.c51220@sabahattin-gucukoglu.com>
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org, IPv6 Apple Developers <ipv6-dev@lists.apple.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jul 2011 12:52:59 -0000

On 9 jul 2011, at 15:51, Sabahattin Gucukoglu wrote:

>>> You're invited to file a report with <http://bugreport.apple.com> =
about this.  Be sure to explain why fixing the broken path MTU discovery =
in the network is not an option and requiring the AirPort user to know =
enough about IPv6 router advertisement MTU options to set the value =
properly is an appropriate mitigation.

> This is bug #9739722, Airport: Configurable IPv6 RA link-MTU or MSS =
Clamping.  Severity 2.

THIS IS A BAD IDEA.

MSS clamping is modifying packets exchanged between consenting hosts. As =
a rule the network doesn't get to do this. Unfortunately the situation =
with IPv4 is so bad that it's not realistically possible to avoid this =
when you have a path MTU smaller than 1500.

But with IPv6 we have a new chance to punish the people creating the =
problem rather than the ones implementing PMTUD properly, so The Right =
Thing To Do is NOT fix any PMTUD breakage in properly behaving systems, =
but rather push people that configure their systems incorrectly to fix =
this. And it seems to be working, PMTUD black holes happen with IPv6, =
but they're relatively rare.

Advertising MTUs smaller than 1500 when the uplink has an MTU smaller =
than 1500 is completely unnecessary because IPv6 has good path MTU =
discovery and doing this also limits the size of packets exchanged =
locally.

Advertising an MTU of 1500 is also not proper behavior, BTW.

However, I do think that it's a good idea for makers of home routers to =
allow users to set the MTU advertised in RAs to anything between 1280 =
and 1500 (inclusive, assuming ethernet), but this should not be done by =
default.

I still plan to get =
http://tools.ietf.org/html/draft-van-beijnum-multi-mtu-03 published at =
some point and having widespread reduced MTUs advertising in RAs means =
one more hurdle to an internet with larger packets. This is something =
that's sorely needed: 100 gigabit ethernet transmits more than two =
average sized IP packets in the time 10 megabit ethernet sends one bit =
with the current average packet size of ~ 500 bytes. Despite the fact =
that virtually all hardware supports larger packets these days. But =
unfortunately our friends over at the IEEE aren't in the position to =
increase the ethernet maximum packet size because that would break =
backward compatibility (of course with every new standard they create =
new stuff that's going to break if they eventually do it, those NE2000 =
cards aren't an issue anymore today). So if anyone is going to do it =
it's going to be us here at the IETF because unlike ethernet, IP allows =
for some parameter exchange between hosts during neighbor discovery (or =
ARP).=

From jmh@joelhalpern.com  Sun Jul 10 07:10:41 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 1564E21F86D4; Sun, 10 Jul 2011 07:10:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.587
X-Spam-Level: 
X-Spam-Status: No, score=-102.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gBJGGoDu-mDP; Sun, 10 Jul 2011 07:10:40 -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 4D09B21F86D1; Sun, 10 Jul 2011 07:10:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 964D7325BF6D; Sun, 10 Jul 2011 07:10:39 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.10.10.102] (pool-71-161-51-16.clppva.btas.verizon.net [71.161.51.16]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id 8D1AC3246B60; Sun, 10 Jul 2011 07:10:38 -0700 (PDT)
Message-ID: <4E19B2DC.4030003@joelhalpern.com>
Date: Sun, 10 Jul 2011 10:10:36 -0400
From: Joel 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>, "karp@ietf.org" <karp@ietf.org>,  IETF discussion list <ietf@ietf.org>
Subject: Re: notes from discussion of KARP design guidelines
References: <4E17210A.1070402@joelhalpern.com> <5662A966-70AD-4A63-BA31-8CE1C9635687@cisco.com> <4E1747BB.8080602@cisco.com>
In-Reply-To: <4E1747BB.8080602@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 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: Sun, 10 Jul 2011 14:10:41 -0000

Joe,
     THE KARP WG Chairs have reviewed your comments, in order to figure 
out what the best way to address them.   We would appreciate it if you 
could engage in discussion of this proposal on the KARP working group 
email list.  If you feel we are still not understanding your point, we 
would be happy to make some time avaialble for discussion at the WG 
session in Quebec City.  (Comments from anyone else, particularly WG 
members, on the proposals being made by the WG chairs are appreciated as 
well.)

Rather than a line by line response, we have tried to find the common 
themes and respond to them.  If we have missed major issues, please let 
us know.

You raised concern about the use of the term "on-the-wire."  Rather than 
replace the term, we would prefer to add descriptive text early in the 
document.  This text would note that it is a widely used term in IETF 
documents, including many RFCs.  It would also state for clarity that in 
this document it is used to refer to the message sent from one routing 
process to another.

With regard to your comment about identifiers, we can add in the 
description of protocol reviews indications that such reviews should be 
clear about what IDs the review considers need protecting, as that is 
important context for the protocol review.

As noted in other exchanges, the document abstract needs a complete 
rewrite.  It should be just an abstract, with the rest of the context 
either removed or moved to the introduction.  In doing so, we will add 
text describing briefly the general concept of the routing protocol 
transport.

In general however, protocol specific behaviors are to be left to the 
protocol analysis documents.  Equally, descriptions of detailed threats 
will be left either to the threat document or to the individual protocol 
analysis document as appropriate.

There are several items in your comments indicating that you would like 
to see more discussion in the design guidelines of the protocol 
layering.  That does not seem to be a useful addition to this document. 
  Again, individual protocol analysis documents will deal with that 
where it is appropriate, and avoid it where it is a distraction.  We do 
not see useful general statements of guidance that can be put into this 
document.

Adding some general text in the discussion of communication modes 
elaborating on the difference between the communication as seen by the 
routing and security components, and the actual communication (e.g. that 
what is seen as multicast may be delivered as broadcast or multiple 
uni-cast) does seem a helpful addition to the document, and we will do that.

Yours,
Joel and Brian


From mohta@necom830.hpcl.titech.ac.jp  Sun Jul 10 08:20:52 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 6EC1121F86EF for <ietf@ietfa.amsl.com>; Sun, 10 Jul 2011 08:20:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[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 60uY7qFnaggE for <ietf@ietfa.amsl.com>; Sun, 10 Jul 2011 08:20:52 -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 9A49421F86EE for <ietf@ietf.org>; Sun, 10 Jul 2011 08:20:51 -0700 (PDT)
Received: (qmail 46302 invoked from network); 10 Jul 2011 15:35:58 -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 Jul 2011 15:35:58 -0000
Message-ID: <4E19C323.7020405@necom830.hpcl.titech.ac.jp>
Date: Mon, 11 Jul 2011 00:20:03 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Spurious MTU in IPv6 RAs Where WAN is PPPoE
References: <357D4DFB-95CF-43B3-AABD-7C237AC7B6D7@sabahattin-gucukoglu.com> <CEE67A11-B91B-4BAD-B75F-19AFC25CFDFE@apple.com> <48BBAE96-4557-436F-A8CC-699BA1E163CF@sabahattin-gucukoglu.com> <C4293C11-766E-4E8E-9B77-2F9C5E19BC88@sabahattin-gucukoglu.com> <7E362046-C8D4-4160-9865-ABFB1B3C767C@muada.com>
In-Reply-To: <7E362046-C8D4-4160-9865-ABFB1B3C767C@muada.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: Sabahattin Gucukoglu <mail-dated-1312811506.c51220@sabahattin-gucukoglu.com>, ietf@ietf.org, IPv6 Apple Developers <ipv6-dev@lists.apple.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jul 2011 15:20:52 -0000

Iljitsch van Beijnum wrote:

> But with IPv6 we have a new chance to punish the people creating
> the problem rather than the ones implementing PMTUD properly,
> so The Right Thing To Do is NOT fix any PMTUD breakage in
> properly behaving systems, but rather push people that
> configure their systems incorrectly to fix this.

Let's see the reality.

IPv6 is broken to request packet too big ICMPs must be
generated even against multicast packets, which causes
serious periodic ICMP implosions when MTUs are, because of
tunneling, below 1500 near many receivers and is 1500 at a
sender and other part of the network.

It means that rational operators MUST filter some ICMP
and, not surprisingly, some operators will block all
ICMP or all packet too big ICMPs, which means PMTUD
won't work.

Who are the people to be punished for creating the problem?

					Masataka Ohta

From iljitsch@muada.com  Sun Jul 10 08:43:00 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 3534C21F86C3 for <ietf@ietfa.amsl.com>; Sun, 10 Jul 2011 08:43:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.425
X-Spam-Level: 
X-Spam-Status: No, score=-102.425 tagged_above=-999 required=5 tests=[AWL=0.175, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z5UAoztXNwiv for <ietf@ietfa.amsl.com>; Sun, 10 Jul 2011 08:42:59 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [IPv6:2001:1af8:3100:a006:1::]) by ietfa.amsl.com (Postfix) with ESMTP id 6760121F86B9 for <ietf@ietf.org>; Sun, 10 Jul 2011 08:42:59 -0700 (PDT)
Received: from [IPv6:2001:470:1f0b:1289:223:12ff:fe56:36b2] ([IPv6:2001:470:1f0b:1289:223:12ff:fe56:36b2]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id p6AFhQjv034211 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 10 Jul 2011 17:43:26 +0200 (CEST) (envelope-from iljitsch@muada.com)
Subject: Re: Spurious MTU in IPv6 RAs Where WAN is PPPoE
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: <4E19C323.7020405@necom830.hpcl.titech.ac.jp>
Date: Sun, 10 Jul 2011 17:42:53 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B60B86E-39B4-4693-BFE9-5AB0098D25CF@muada.com>
References: <357D4DFB-95CF-43B3-AABD-7C237AC7B6D7@sabahattin-gucukoglu.com> <CEE67A11-B91B-4BAD-B75F-19AFC25CFDFE@apple.com> <48BBAE96-4557-436F-A8CC-699BA1E163CF@sabahattin-gucukoglu.com> <C4293C11-766E-4E8E-9B77-2F9C5E19BC88@sabahattin-gucukoglu.com> <7E362046-C8D4-4160-9865-ABFB1B3C767C@muada.com> <4E19C323.7020405@necom830.hpcl.titech.ac.jp>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
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: Sun, 10 Jul 2011 15:43:00 -0000

On 10 jul 2011, at 17:20, Masataka Ohta wrote:

I was wondering what kind of unique perspective you would have here, and =
I wasn't disappointed:

> It means that rational operators MUST filter some ICMP
> and, not surprisingly, some operators will block all
> ICMP or all packet too big ICMPs

That is more or less ok as long as they don't send any packets larger =
than 1280 bytes.

If you want to send 1281-byte packets you MUST use PMTUD and thus you =
MUST accept incoming packet too big messages.=

From marka@isc.org  Sun Jul 10 09:12:54 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 7078D21F8744 for <ietf@ietfa.amsl.com>; Sun, 10 Jul 2011 09:12:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.722
X-Spam-Level: 
X-Spam-Status: No, score=-1.722 tagged_above=-999 required=5 tests=[AWL=-0.885, BAYES_00=-2.599, MISSING_SUBJECT=1.762]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qwLoXyNxIh8y for <ietf@ietfa.amsl.com>; Sun, 10 Jul 2011 09:12:54 -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 BE90121F8743 for <ietf@ietf.org>; Sun, 10 Jul 2011 09:12:53 -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 755E25F984C; Sun, 10 Jul 2011 16:12:27 +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 AAAC4216C7B; Sun, 10 Jul 2011 16:12:25 +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 D3F1511ACA6E; Mon, 11 Jul 2011 02:12:19 +1000 (EST)
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
From: Mark Andrews <marka@isc.org>
Date: Mon, 11 Jul 2011 02:12:19 +1000
Message-Id: <20110710161219.D3F1511ACA6E@drugs.dv.isc.org>
Cc: Sabahattin Gucukoglu <mail-dated-1312811506.c51220@sabahattin-gucukoglu.com>, Iljitsch van Beijnum <iljitsch@muada.com>, ietf@ietf.org, IPv6 Apple Developers <ipv6-dev@lists.apple.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jul 2011 16:12:54 -0000

References: <357D4DFB-95CF-43B3-AABD-7C237AC7B6D7@sabahattin-gucukoglu.com> <CEE67A11-B91B-4BAD-B75F-19AFC25CFDFE@apple.com> <48BBAE96-4557-436F-A8CC-699BA1E163CF@sabahattin-gucukoglu.com> <C4293C11-766E-4E8E-9B77-2F9C5E19BC88@sabahattin-gucukoglu.com> <7E362046-C8D4-4160-9865-ABFB1B3C767C@muada.com>  <4E19C323.7020405@necom830.hpcl.titech.ac.jp>
Subject: Re: Spurious MTU in IPv6 RAs Where WAN is PPPoE
In-reply-to: Your message of "Mon, 11 Jul 2011 00:20:03 +0900."
             <4E19C323.7020405@necom830.hpcl.titech.ac.jp>
--------

In message <4E19C323.7020405@necom830.hpcl.titech.ac.jp>, Masataka Ohta writes:
> Iljitsch van Beijnum wrote:
> 
> > But with IPv6 we have a new chance to punish the people creating
> > the problem rather than the ones implementing PMTUD properly,
> > so The Right Thing To Do is NOT fix any PMTUD breakage in
> > properly behaving systems, but rather push people that
> > configure their systems incorrectly to fix this.
> 
> Let's see the reality.
> 
> IPv6 is broken to request packet too big ICMPs must be
> generated even against multicast packets, which causes
> serious periodic ICMP implosions when MTUs are, because of
> tunneling, below 1500 near many receivers and is 1500 at a
> sender and other part of the network.
> 
> It means that rational operators MUST filter some ICMP
> and, not surprisingly, some operators will block all
> ICMP or all packet too big ICMPs, which means PMTUD
> won't work.
> 
> Who are the people to be punished for creating the problem?
> 
> 					Masataka Ohta
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

Which only happens if applications disable IPV6_USE_MIN_MTU for
multicast packets (the default is to fragment multicast packets
at network MTU (1280)).

So to get this you need a broken stack or a brain dead application.

Mark
-- 
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  Sun Jul 10 14:38: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 66D3B21F879F for <ietf@ietfa.amsl.com>; Sun, 10 Jul 2011 14:38: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 2WidRAeH0cog for <ietf@ietfa.amsl.com>; Sun, 10 Jul 2011 14:38:13 -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 8CF3B21F877B for <ietf@ietf.org>; Sun, 10 Jul 2011 14:38:12 -0700 (PDT)
Received: (qmail 50628 invoked from network); 10 Jul 2011 21:53:04 -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 Jul 2011 21:53:04 -0000
Message-ID: <4E1A1B71.6040702@necom830.hpcl.titech.ac.jp>
Date: Mon, 11 Jul 2011 06:36:49 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Spurious MTU in IPv6 RAs Where WAN is PPPoE
References: <357D4DFB-95CF-43B3-AABD-7C237AC7B6D7@sabahattin-gucukoglu.com> <CEE67A11-B91B-4BAD-B75F-19AFC25CFDFE@apple.com> <48BBAE96-4557-436F-A8CC-699BA1E163CF@sabahattin-gucukoglu.com> <C4293C11-766E-4E8E-9B77-2F9C5E19BC88@sabahattin-gucukoglu.com> <7E362046-C8D4-4160-9865-ABFB1B3C767C@muada.com> <4E19C323.7020405@necom830.hpcl.titech.ac.jp> <5B60B86E-39B4-4693-BFE9-5AB0098D25CF@muada.com>
In-Reply-To: <5B60B86E-39B4-4693-BFE9-5AB0098D25CF@muada.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jul 2011 21:38:13 -0000

Iljitsch van Beijnum wrote:

> I was wondering what kind of unique perspective you would
> have here, and I wasn't disappointed:

You always outperform me with your imagination.

>> It means that rational operators MUST filter some ICMP
>> and, not surprisingly, some operators will block all
>> ICMP or all packet too big ICMPs
> 
> That is more or less ok as long as they don't send any packets
> larger than 1280 bytes.

That's not an assumption on end users' behavior rational
operators can rely on.

> If you want to send 1281-byte packets you MUST use PMTUD and
> thus you MUST accept incoming packet too big messages.

End users might think they can, but operators won't, accept
them.

Note that it's operators who filter.

						Masataka Ohta

From Quittek@neclab.eu  Mon Jul 11 04:17:27 2011
Return-Path: <Quittek@neclab.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC99021F858E; Mon, 11 Jul 2011 04:17:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.85
X-Spam-Level: 
X-Spam-Status: No, score=-101.85 tagged_above=-999 required=5 tests=[AWL=-0.399, BAYES_00=-2.599, HELO_EQ_DE=0.35, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vMSMBfxuzggO; Mon, 11 Jul 2011 04:17:27 -0700 (PDT)
Received: from smtp0.netlab.nec.de (smtp0.netlab.nec.de [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id D77BF21F8553; Mon, 11 Jul 2011 04:17:26 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.netlab.nec.de (Postfix) with ESMTP id D143628000213; Mon, 11 Jul 2011 13:17:25 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office.hd)
Received: from smtp0.netlab.nec.de ([127.0.0.1]) by localhost (atlas1.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YGNhmiekGWrB; Mon, 11 Jul 2011 13:17:25 +0200 (CEST)
Received: from METHONE.office.hd (Methone.office.hd [192.168.24.54]) by smtp0.netlab.nec.de (Postfix) with ESMTP id B5F9E28000174; Mon, 11 Jul 2011 13:16:55 +0200 (CEST)
Received: from DAPHNIS.office.hd ([169.254.2.22]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0270.001; Mon, 11 Jul 2011 13:16:56 +0200
From: Juergen Quittek <Quittek@neclab.eu>
To: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "ietf@ietf.org" <ietf@ietf.org>, "irtf-chair@irtf.org" <irtf-chair@irtf.org>
Subject: Bar BOF for IRTF work on energy efficiency
Thread-Topic: Bar BOF for IRTF work on energy efficiency
Thread-Index: Acw/vAlXyn6sUzFFFUCPPLipvPwj5Q==
Date: Mon, 11 Jul 2011 11:16:54 +0000
Message-ID: <CA40A845.174C0%quittek@neclab.eu>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.10.0.110428
x-originating-ip: [10.1.2.219]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <939614CF3E763A41B780F2533258B57E@office.hd>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, eman mailing list <eman@ietf.org>, "smartpowerdir@ietf.org" <smartpowerdir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jul 2011 11:17:28 -0000

Dear all,

Energy-efficiency is of growing importance for the Internet and thus also
for the IETF.  There is already an IETF WG in the OPS area on energy
management (eman) and in several other WGs people are starting to consider
energy efficiency of the protocols they design.

It looks like energy efficiency has the potential to become a cross topic
affecting many areas we are working on.  But before adding action items on
energy efficiency to IETF WGs it appears to be wise to first investigate th=
e
general problems of IETF protocols concerning energy efficiency.  One
example are keep-alive messages that keep devices from going to sleep mode
even if there are no real service requests.

One way to address the problem is to start general investigations on energy
efficiency in the IRTF.  At http://www.green-communications.net/eerg/ we
make a proposal for a new energy efficiency research group (eerg) in the
IRTF.  Please note that we consider this rather as a proposal for new work
items.  We may find that these are better shared among existing RGs.  But i=
f
not, we would propose establishing a new RG.  There is also a mailing list
at https://listserv.netlab.nec.de/mailman/listinfo/eerg to discuss about
these issues.

For all those of you who are interested in this, we will organize a bar BOF
on Wednesday evening, July 27, after the plenary at 20:15.  The location
will be posted at the web site and on the mailing list mentioned above.  If
you would like to join, please create an entry at the doodle at
http://doodle.com/vvvpbgcmm2r78abi .  This helps organizing a location for
the bar BOF that fits all of us.

Please feel free to forward this announcement to further interested people.

See you at the bar BOF,

    Juergen


From rbarnes@bbn.com  Mon Jul 11 06:17:36 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 1329921F8B64; Mon, 11 Jul 2011 06:17:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[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 r+hqyy0DUOD8; Mon, 11 Jul 2011 06:17:35 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id 661D421F8B3D; Mon, 11 Jul 2011 06:17:35 -0700 (PDT)
Received: from [192.1.255.156] (port=57724 helo=col-dhcp-192-1-255-156.bbn.com) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1QgGMY-000Odn-QN; Mon, 11 Jul 2011 09:17:27 -0400
From: "Richard L. Barnes" <rbarnes@bbn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: secdir review of draft-ietf-6man-flow-3697bis
Date: Mon, 11 Jul 2011 09:17:24 -0400
Message-Id: <173612BD-2825-4A21-98C7-CA8BD5639368@bbn.com>
To: IETF Discussion <ietf@ietf.org>, The IESG <iesg@ietf.org>, secdir@ietf.org, draft-ietf-6man-flow-3697bis@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1082)
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, 11 Jul 2011 13:17:36 -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 describes how end hosts and intermediate nodes should =
populate and handle the IPv6 flow label field.  The document spends a =
fair bit of time discussing security considerations related to the flow =
label and its relation to IPsec in particular.  Overall, the document =
does a thorough job of discussing security considerations, and I don't =
think there's anything they've clearly missed. =20

The only request I would have would be for the authors to add a little =
more discussion around the "theft of service" threat.  It would be =
helpful to detail the assumptions/circumstances under which this threat =
aries -- namely that networks provide resources based on flow label and =
flow label values are set by end hosts.  Given the risks that this =
document discusses, it might be worth considering a recommendation that =
networks SHOULD NOT make resource allocation decisions based on flow =
labels without some external means of assurance.  Or some similar =
warning against making resource decisions on a completely unsecured =
field.

Also, purely from a terminology perspective, I found the phrase =
"unintended service" confusing and less accurate than the "better =
service" phrase used in RFC 3697.  It might be better to spell this out:=20=

"
... an adversary may be able to obtain a class of service that the =
network did not intend to provide ...
"

--Richard


From trammell@tik.ee.ethz.ch  Mon Jul 11 07:30:25 2011
Return-Path: <trammell@tik.ee.ethz.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E381221F8C41; Mon, 11 Jul 2011 07:30:25 -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 sL9sRGdlLsYx; Mon, 11 Jul 2011 07:30:25 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id A6F5821F8C40; Mon, 11 Jul 2011 07:30:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 1EF7ED9321; Mon, 11 Jul 2011 16:30:23 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id mWl1U5ymYGjw; Mon, 11 Jul 2011 16:30:22 +0200 (MEST)
Received: from pb-10243.ethz.ch (pb-10243.ethz.ch [82.130.102.152]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id BDDFBD930E; Mon, 11 Jul 2011 16:30:22 +0200 (MEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: MILE side meeting, IETF81 in Quebec, Monday night July 25th
From: Brian Trammell <trammell@tik.ee.ethz.ch>
Date: Mon, 11 Jul 2011 16:30:22 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A7CB63B8-DBE2-4862-BA76-9C0BFECBC725@tik.ee.ethz.ch>
References: <AE31510960917D478171C79369B660FA0E03253CAF@MX06A.corp.emc.com>
To: ietf@ietf.org, saag@ietf.org
X-Mailer: Apple Mail (2.1084)
Cc: mile@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jul 2011 14:30:26 -0000

Greetings, all,

To help us plan a bit for the (previously-announced) MILE pre-WG side =
meeting in Quebec, 19:30 Monday 25 July, after the technical plenary =
meeting, please let us know if you are interested in attending by =
filling out the doodle at:

http://www.doodle.com/e2w494tce6knmq6m

The working proposed charter is attached below for reference. Further =
details will be announced later.

Many thanks, and best regards,

Brian and Kathleen

Managed Incident Lightweight Exchange (mile)
--------------------------------------------

Proposed Working Group Charter

Chairs:
    Kathleen Moriarty <kathleen.moriarty@emc.com>
    Brian Trammell <trammell@tik.ee.ethz.ch>

Security Area Directors:
    Stephen Farrell =
<stephen.farrell@cs.tcd.ie<mailto:stephen.farrell@cs.tcd.ie>>
    Sean Turner <turners@ieca.com<mailto:turners@ieca.com>>

Security Area Advisor:
    Sean Turner <turners@ieca.com>

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

Description:

The Managed Incident Lightweight Exchange (MILE) pre-working group will =
develop standards and extensions for the purpose of improving incident =
information sharing and handling capabilities based on the work =
developed in the IETF Extended INCident Handling (INCH) working group.  =
The Incident Object Description Exchange Format (IODEF) in RFC5070 and =
Real-time Inter-network Defense (RID) in RFC6045 were developed in the =
INCH working group by international Computer Security Incident Response =
Teams (CSIRTs) and industry to meet the needs of a global community =
interested in sharing, handling, and exchanging incident information.  =
The extensions and guidance created by the MILE working group assists =
with the daily operations of CSIRTs at an organization, service =
provider, law enforcement, and at the country level.  The application of =
IODEF and RID to interdomain incident information cooperative exchange =
and sharing has recently expanded and the need for extensions has become =
more im
portant. Efforts continue to deploy IODEF and RID, as well as to extend =
them to support specific use cases covering reporting and mitigation of =
current threats such as anti-phishing extensions.

An incident could be a benign configuration issue, IT incident, an =
infraction to a service level agreement (SLA), a system compromise, =
socially engineered phishing attack, or a denial-of-service (DoS) =
attack, etc..  When an incident is detected, the response may include =
simply filing a report, notification to the source of the incident, a =
request to a third party for resolution/mitigation, or a request to =
locate the source.  IODEF defines a data representation that provides a =
standard format for sharing information commonly exchanged about =
computer security incidents.  RID enables the secure exchange of =
incident related information in an IODEF format providing options for =
security, privacy, and policy setting.

MILE leverages collaboration and sharing experiences with the work =
developed in the INCH working group which includes the data model =
detailed in the IODEF, 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 contexts. Related work, drafted =
outside of INCH will also be reviewed and includes RFC5941, Sharing =
Transaction Fraud Data.

The MILE working group provides coordination for these various extension =
efforts to improve the capabilities for exchanging incident information. =
 MILE has several objectives with the first being a description a subset =
of IODEF focused on ease of deployment and applicability to current =
information security data sharing use cases.  MILE also describes a =
generalization of RID for secure exchange of other security-relevant XML =
formats.  MILE produces additional guidance needed for the successful =
exchange of incident information for new use cases according to policy, =
security, and privacy requirements.  Finally, MILE produces a document =
template with guidance for defining IODEF extensions to be followed when =
producing extensions to IODEF as appropriate, for:

 * labeling incident reports with data protection, data retention, and =
other 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 =
confirmed 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 julian.reschke@gmx.de  Mon Jul 11 07:31:47 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 9A6BD21F8C41 for <ietf@ietfa.amsl.com>; Mon, 11 Jul 2011 07:31:47 -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 pneJYuzNdL08 for <ietf@ietfa.amsl.com>; Mon, 11 Jul 2011 07:31:47 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 9DC1D21F8C3E for <ietf@ietf.org>; Mon, 11 Jul 2011 07:31:46 -0700 (PDT)
Received: (qmail invoked by alias); 11 Jul 2011 14:31:45 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp025) with SMTP; 11 Jul 2011 16:31:45 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+GP/8/JDqGxy6zsiSQYf34geQqcr1hzIMDrVCL0y yLyYbPKZ3dem9P
Message-ID: <4E1B094F.4060603@gmx.de>
Date: Mon, 11 Jul 2011 16:31:43 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com>
In-Reply-To: <20110711140229.17432.23519.idtracker@ietfa.amsl.com>
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: Mon, 11 Jul 2011 14:31:47 -0000

Hi,

this document has an informative reference to an unstable document at 
<http://dev.w3.org/html5/websockets/>. It should be replaced by a 
reference to the actual W3C WG's Working Draft: 
<http://www.w3.org/TR/websockets/> (and potentially marked "work in 
progress").

Best regards, Julian

From david.i.allan@ericsson.com  Fri Jul  8 09:13:28 2011
Return-Path: <david.i.allan@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 0F58E21F8B92; Fri,  8 Jul 2011 09:13:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_31=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZPWSKA0CTMIr; Fri,  8 Jul 2011 09:13:26 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by ietfa.amsl.com (Postfix) with ESMTP id 58B3F21F8B90; Fri,  8 Jul 2011 09:13:26 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p68GDMRc002946; Fri, 8 Jul 2011 11:13:25 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.253]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Fri, 8 Jul 2011 12:13:21 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: Rui Costa <RCosta@ptinovacao.pt>, Stewart Bryant <stbryant@cisco.com>
Date: Fri, 8 Jul 2011 12:13:18 -0400
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity Verification, Continuity Check and Remote Defect indication for MPLS	Transport	Profile) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity Verification, Continuity Check and Remote Defect indication for MPLS	Transport	Profile) to Proposed Standard
Thread-Index: Acw3LJ0GTOqQfPcUQOGUhgK/1kXgjgDPfXWgACJLxEAApIjzAA==
Message-ID: <60C093A41B5E45409A19D42CF7786DFD522135449A@EUSAACMS0703.eamcs.ericsson.se>
References: <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B6BC@INOAVREX11.ptin.corpPT.com>
In-Reply-To: <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B6BC@INOAVREX11.ptin.corpPT.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: Mon, 11 Jul 2011 08:10:57 -0700
Cc: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2011 16:13:28 -0000

Rui:

You wrote:

>Reading something, keeping it on record, without effect in the draft and "=
ignoring comments" have IMHO similar outcomes. As author of the draft you a=
re free to do it. These standards have a great impact
>in our work, so i'm also free to write what i did.

Numerous comments did have effect on the draft and those that didn't were e=
ither simply not actionable, were rhetorical or not constructive, and a few=
 had to be balanced against comments coming from the MPLS & BFD WGs. I woul=
d translate "ingored" or "without effect" to "did not get one'e way". In th=
e standards process it happens.

Meanwhile as an editor of the document, I'll take the liberty of responding=
 to some of the points you raise...

>My technical concerns regarding this draft were expressed...
>...in the (ITU-T -> IETF, Feb/2011) liaison regarding it (LS281, i believe=
);
>...in operators' meetings' that took place during ITU-T's Feb/2011 plenary=
 meeting;

I and the WG don't really have access to private grumblings.

>...in a comparison session that took place during that same ITU-T meeting.

Lots of other opinions were expressed as well, and they did not all agree w=
ith you.

>Some:
>CC/CV
>I don't understand the need for 2 types of packets: a single type allows C=
C; mismatching identifiers in the same CC packets allow CV.
>Besides adding complexity, we whether always activate both or potentiate u=
ndetected mismerges.

OK, lets walk through this.

We want CV all the time so that any misconectivity can be detected, but on =
the list it was expressed that the group did not want the overhead of proce=
ssing the source MEP TLV in every packet in order to achieve this. We could=
 carry it in every packet and have the receiver simply ignore most of them,=
 but then that would make the defect entry criteria compeltely random and t=
he exit criteria unreliable as well, not really a good design. Hence they a=
re separated using different ACH code points and the receiver is obliged to=
 process every source MEP TLV it receives. I hope this is clear.

>(BTW: can't understand how we propose one ACH codepoint to CC, another for=
 CV, [counting other drafts, another for frame loss ...] but don't consider=
 assigning 1 single ACH protocol identifier codepoint >as requested by ITU-=
T)

Because that puts you into two protocol ID demultiplexing steps per OAM PDU=
 recevied to determine the intended function. Hence COSTS MORE. That is pre=
tty basic...

> Uni P2P / P2MP
> I can't see how BFD will support unidir and hence P2MP other than...
> ...eliminating the session "state variable" (down, init, up), aiming just=
 the state variables we really need, bringing us to something similar to 17=
31, eventually with other bits on the wire or...
> ...using IP to create the reverse way, which we cannot assume per require=
ments;
> Will we create a complete different tool for that?
> (BFD's B=3D"bidirectional")

I would not go so far as to say "similar to 1731", there is actually a lot =
of difference under the hood. As for uni-directional BFD, that is a BFD WG =
problem at the moment.

> Provisioning list
> This is an MPLS profile/subset (and i heard) achievable through a particu=
lar configuration. So, i expect each draft-ietf-mpls-TP-* to focus on that =
profile/configuration. However, i keep seeing
> references f.i. to IP encapsulations unexpected under TP's OAM.
> I don't thus understand what the aim is: do we expect this in TP, are we =
talking about MPLS in general?... The TP profile is never quite delimited.
> Does chapter 4 contain ALL the configurable parameters list agreed to pro=
vide in the comparison session?

It should. As for encapsulations, unless TP is in a complete island not con=
nected to anything (which as a network is rather useless) it will be expect=
ed to interoperate with the rest of the MPLS architecture, and the stated i=
ntention of tool development was that what resulted was applicable to the b=
roader MPLS architecture. Which means backwards compatiblity and procedures=
 for interoperation.

> Backwards compatibility
> This was the main argument risen to ground MPLS-TP OAM on BFD. It's not a=
 better argument than grounding MPLS-TP OAM on 1731 due to its ETH deployme=
nt plus coherence with SDH, OTN, as defended by ITU-T.
> For reasons like the above, however, MPLS-TP BFD won't be backwards compa=
tible with previous BFD (even considering just CC/CV). They don't even shar=
e the same codepoint.

The issue is not code point, which is the trivial part. It is reuse of the =
majority of the implementation. Again, pretty basic.

>Simplicity
>Whether we look to PDH, SDH, OTN or ETH, ITU-T's approach to CC is simpler=
: in each flow, a standard defined nr of constant heartbeat signals (with s=
tandard constant or provisioned period - no
>auto/negotiated -) means OK. A standard defined number of misses means los=
t Rx connection. An RDI, the only articulation between Rx and Tx flows, mea=
ningful in bidirectional applications, allows each
>pear to identify Tx problems.
>This OAM simplicity is the key for reliable fail finger pointing, performa=
nce reports and protection. Also to allow scaling, more implementation oppo=
rtunities/manufacturers, which is valuable for
>operators.

Well IMO there was not a lot of interest in T-MPLS until the IETF was going=
 to re-define it and make it compatible with IP/MPLS. So there was an indus=
try wide "design intent" implied here.

> IMHO, between your MPLS-TP view and MPLS/IP, it becomes more and more dif=
ficult to tell which is which.

That is because MPLS-TP is not a new techology, it is an addition to the en=
tire MPLS protocol suite.

Hope this helps
D









-----Original Message-----
From: David Allan I [mailto:david.i.allan@ericsson.com]
Sent: quarta-feira, 6 de Julho de 2011 19:25
To: erminio.ottone_69@libero.it; Rui Costa; ietf@ietf.org; IETF-Announce
Cc: mpls@ietf.org
Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>=
 (Proactive Connectivity Verification, Continuity Check and Remote Defect i=
ndication for MPLS Transport Profile) to Proposed Standard

Hi Erminio:

<snipped>
>Several service providers regarded this draft as not meeting their
>transport networks' needs.

E> This is a true statement: the solution in this draft is useless for many=
 MPLS- TP deployments.

The two statements do not necessarily follow.

What we established during discussions at the SG15 plenary in February was =
that the issue some service providers had was that the IETF BFD solution ex=
ceeded their requirements in that there was additional functionality they d=
id not see a need for, and that they considered any additional functionalit=
y parasitic.

However this is a consequence of adapting an existing technology to a new a=
pplication. I do not see any way around that. And the entire joint project =
was based on the premise of engineering re-use not greenfield design. That =
is what it said on the tin up front, and IMO why when the IETF started down=
 this path packet transport transitioned from being a minority sport to mai=
nstream, so it is a bit late to cry foul....

My 2 cents
Dave




-----Original Message-----
From: David Allan I [mailto:david.i.allan@ericsson.com]
Sent: quarta-feira, 6 de Julho de 2011 18:36
To: erminio.ottone_69@libero.it; loa@pi.nu; Rui Costa
Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>=
 (Proactive Connectivity Verification, Continuity Check and Remote Defect i=
ndication for MPLS Transport Profile) to Proposed Standard

Hi Erminio:

Two of the three document editors were present at SG15 plenary in February =
where the comments originated. The revised meeting schedule resulted in a d=
ay spent going through the document with the editors. IMO there were lots o=
f discussion and legitimate issues with the document identified and correct=
ed so it was a useful session. The liaison of same was in many ways *after =
the fact*.

Cheers
Dave




-----Original Message-----
From: erminio.ottone_69@libero.it [mailto:erminio.ottone_69@libero.it]
Sent: quarta-feira, 6 de Julho de 2011 18:34
To: Rui Costa; ietf@ietf.org; IETF-Announce
Cc: mpls@ietf.org
Subject: R: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Pr=
oactive Connectivity Verification, Continuity Check and Remote Defect indic=
ation for MPLS Transport Profile) to Proposed Standard

The way this draft has been developed is a bit strange.

The poll for its adoption as a WG document was halted by the MPLS WG chair =
because "it is not possible to judge consensus":

http://www.ietf.org/mail-archive/web/mpls/current/msg04502.html

The lack of consensus was motivated by serious technical concerns raised by=
 several transport experts during the poll.

Nevertheless the MPLS WG chair decided to adopt the draft as a WG document:

http://www.ietf.org/mail-archive/web/mpls/current/msg04512.html

After several WG revisions and WG LCs, the technical issues have not been r=
esolved.

>Several service providers regarded this draft as not meeting their
>transport
networks' needs.

This is a true statement: the solution in this draft is useless for many MP=
LS- TP deployments.


-----Original Message-----
From: erminio.ottone_69@libero.it [mailto:erminio.ottone_69@libero.it]
Sent: quarta-feira, 6 de Julho de 2011 18:26
To: loa@pi.nu; Rui Costa
Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
Subject: R: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Pr=
oactive Connectivity Verification, Continuity Check and Remote Defect indic=
ation for MPLS Transport Profile) to Proposed Standard

>  Version -04 of the document was published June 28th.
>
>  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
> June 29th.
>

So when the WG LC to confirm the LC comment resolution has been launched?

The proto write-up says:

            It has also passed a working roup call to verify that LC commen=
ts were correctly with minor comments.

It also says:

            The comments has been
            carefully discussed between the authors and people making the c=
omments and
            has been resolved.

But it seems that some comments have not been discussed with the authors of=
 the comments. When ITU-T Q10/15 has been involved in discussing its commen=
ts?




-----Original Message-----
From: Loa Andersson [mailto:loa@pi.nu]
Sent: quarta-feira, 6 de Julho de 2011 16:44
To: Rui Costa
Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proac=
tive Connectivity Verification, Continuity Check and Remote Defect indicati=
on for MPLS Transport Profile) to Proposed Standard

All,

Since someone has commented about the process used for resolving
questions on
draft-ietf-mpls-tp-cc-cv-rdi I am supplying some details below.

The history of draft-ietf-mpls-tp-cc-cv-rdi working group review
process is:

On February 3rd 2011 the working group last call was issued
on version -03

      This was copied to the the Ad Hoc Team List
      and liaised to SG15 also on February 3rd

      This working group last call ended om Feb 28


      On Feb 28 we also received a liaison with comments from SG15


The authors compiled a list of all comments received  as part the MPLS
working group last call; these  comments - and the intended resolution -
is included in the meeting minutes from the Prague meeting:


      http://www.ietf.org/proceedings/80/slides/mpls-9.pdf


  During the IETF meeting in Prague, we agreed with the BFD working
  group to do a separate working group last callfor the BFD working
  group

The (BFD) working group last call was started on March 30th and ran
for 13 days. The last call ended on April 11th.

  The authors have since worked hard to resolve comments, some
  issue has been brought to the working group mailing list for
  resolution.

  Version -04 of the document was published June 28th.

  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
  June 29th.

  The AD review resulted in a "New ID needed" due to mostly editorial
  comments. Version -05 was published on June 29 and the IETF last call
  started as soon as the new ID was avaialbe.

  The current list of Last Call Comments resoltion is also avaiable at:
  http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls

  The list of issues that the authors kept very carefully, shows without
doubt
  that no comments been ignored.

  Loa
  mpls wg document shepherd







-----Original Message-----
From: David Allan I [mailto:david.i.allan@ericsson.com]
Sent: quarta-feira, 6 de Julho de 2011 14:58
To: Rui Costa; ietf@ietf.org; IETF-Announce
Cc: mpls@ietf.org
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proac=
tive Connectivity Verification, Continuity Check and Remote Defect indicati=
on for MPLS Transport Profile) to Proposed Standard

Hi Rui:

The comments were not ignored, the resolution of the Q10 comments as well a=
s those collected from the MPLS WG was presented at the last IETF. My sprea=
dsheet from which that report was generated and has been augmented to inclu=
de the BFD WG comments is available at http://www.pi.nu/~loa/cc-cv-rdi-Last=
-Call-Comments.xls

So you know...
Dave


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Rui=
 Costa
Sent: segunda-feira, 4 de Julho de 2011 23:03
To: ietf@ietf.org; IETF-Announce
Cc: mpls@ietf.org
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proac=
tive Connectivity Verification, Continuity Check and Remote Defect indicati=
on for MPLS Transport Profile) to Proposed Standard

IMHO and for the record:

ITU-T comments regarding this draft haven't been discussed with ITU-T but w=
ere simply ignored. No LS describing these comments' resolution was sent.

Several service providers regarded this draft as not meeting their transpor=
t networks' needs.

[The v03 draft was published in Feb and went to WG LC.
The v04 draft addressing WG LC comments was published on the 28th June (sam=
e date as the proto write-up).
When was the WG LC launched, to verify LC comments resolution?]

Regards,
Rui


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of The=
 IESG
Sent: quinta-feira, 30 de Junho de 2011 14:47
To: IETF-Announce
Cc: mpls@ietf.org
Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive=
 Connectivity Verification, Continuity Check and Remote Defect indication f=
or MPLS Transport Profile) to Proposed Standard


The IESG has received a request from the Multiprotocol Label Switching WG
(mpls) to consider the following document:
- 'Proactive Connectivity Verification, Continuity Check and Remote
   Defect indication for MPLS Transport Profile'
  <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract

   Continuity Check, Proactive Connectivity Verification and Remote
   Defect Indication functionalities are required for MPLS-TP OAM.

   Continuity Check monitors the integrity of the continuity of the
   label switched path for any loss of continuity defect. Connectivity
   verification monitors the integrity of the routing of the label
   switched path between sink and source for any connectivity issues.
   Remote defect indication enables an End Point to report, to its
   associated End Point, a fault or defect condition that it detects on
   a pseudo wire, label switched path or Section.

   This document specifies methods for proactive continuity check,
   continuity verification, and remote defect indication for MPLS-TP
   label switched paths, pseudo wires and Sections using Bidirectional
   Forwarding Detection.


The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/


No IPR declarations have been submitted directly on this I-D.
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

From neil.2.harrison@bt.com  Fri Jul  8 09:13:56 2011
Return-Path: <neil.2.harrison@bt.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDE8721F8B9C; Fri,  8 Jul 2011 09:13:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.046
X-Spam-Level: 
X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_21=0.6, J_CHICKENPOX_81=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 6MlsPAWD8Iai; Fri,  8 Jul 2011 09:13:54 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp64.intersmtp.COM [62.239.224.237]) by ietfa.amsl.com (Postfix) with ESMTP id 7C7F721F8B9B; Fri,  8 Jul 2011 09:13:53 -0700 (PDT)
Received: from EVMHT64-UKRD.domain1.systemhost.net (10.36.3.101) by RDW083A008ED64.smtp-e4.hygiene.service (10.187.98.13) with Microsoft SMTP Server (TLS) id 8.3.159.2; Fri, 8 Jul 2011 17:13:52 +0100
Received: from EMV62-UKRD.domain1.systemhost.net ([169.254.1.186]) by EVMHT64-UKRD.domain1.systemhost.net ([10.36.3.101]) with mapi; Fri, 8 Jul 2011 17:13:52 +0100
From: <neil.2.harrison@bt.com>
To: <tnadeau@lucidvision.com>
Date: Fri, 8 Jul 2011 17:13:36 +0100
Subject: RE: [mpls] Last Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication for	MPLS	Transport	Profile) to Proposed Standard
Thread-Topic: [mpls] Last Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication for	MPLS	Transport	Profile) to Proposed Standard
Thread-Index: Acw9g2/gPYlO1BBvSs613Cw7wIf+bwABd9Xg
Message-ID: <6D3D47CB84BDE349BC23BF1C94E316E4405A75577E@EMV62-UKRD.domain1.systemhost.net>
References: <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B6BC@INOAVREX11.ptin.corpPT.com> <6D3D47CB84BDE349BC23BF1C94E316E4405A7550DE@EMV62-UKRD.domain1.systemhost.net> <BA2E2586-1B10-4954-93A2-E8EE9DF0427F@lucidvision.com>
In-Reply-To: <BA2E2586-1B10-4954-93A2-E8EE9DF0427F@lucidvision.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 11 Jul 2011 08:10:57 -0700
Cc: mpls@ietf.org, ietf@ietf.org, david.i.allan@ericsson.com, 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: Fri, 08 Jul 2011 16:13:57 -0000

Thanks Tom...these are general observations which I think are valid and res=
pond to Rui's point about the need for simplicity....and they are as much d=
irected to folks pushing overblown OAM in ITU as folks in IETF.  You may of=
 course disagree with them.  I recall someone once saying MPLS did not need=
 DP OAM at all....

regards, Neil

> -----Original Message-----
> From: Thomas Nadeau [mailto:tnadeau@lucidvision.com]
> Sent: 08 July 2011 16:27
> To: Harrison,N,Neil,DKQ7 R
> Cc: RCosta@ptinovacao.pt; david.i.allan@ericsson.com;
> stbryant@cisco.com; mpls@ietf.org; ietf@ietf.org; ietf-
> announce@ietf.org
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote
> Defect indication for MPLS Transport Profile) to Proposed Standard
>
>
> On Jul 8, 2011, at 3:15 AM, <neil.2.harrison@bt.com> wrote:
>
> > Got to say I agree with Rui on much of what he says here.  And I
> absolutely resonate with his point on the need for simplicity.  The
> reason OAM needs to be as simple as possible is because it must be
> super reliable....we do not want to consciously build in weaknesses,
> esp unnecessary ones.... this also implies minimal config.  We could
> all do better on this.  For example:
> >
> > -       Rui is dead right a CC function is fairly useless, we only
> need a CV function...the ATM OAM in I.610 suffers from this problem
> (and few others like AIS and the assumed use of request/response MLT to
> diagnose leaking/mismerging traffic...request/response OAM won't work
> with unidirectional defects).
>
>       While you are entitled to your opinion, I personally think there
> are enough requirements elsewhere to have both CC and CV functions.
> But we digress. Are you actually asking that the CC functionality be
> removed from the draft or just making a general comment?
>
> > -       all packet layer networks should not have an AIS OAM
> message....very obvious for the cl-ps mode of course.  The co-ps mode
> is also not like the co-cs mode.  One has to consciously manufacture
> AIS messages and target them to specific clients in the co-ps
> mode....who may have taken action in their own layer network and 'moved
> elsewhere' anyway, ie a total waste of time now.  AIS is actually
> unnecessary wrt providing information anyway, it simply represents an
> in-built weakness of just something else to go wrong which itself will
> create problems.
>
>       What does that comment have to do with the actual draft in
> question?
>
> > -       creating preconfigured TCM sublayers is just asking for
> trouble IMO.  It is far smarter to simply create a single end-end OAM
> CV (and when required PM) flow and tap this off at intermediate nodes
> on the *rare* occasions one wants to do.
>
>       Again, what does this have to do with the actual draft in
> question?
>
>       --tom
>
>
>
>
> >
> > regards, Neil
> >
> > This email contains BT information, which may be privileged or
> confidential.
> > It's meant only for the individual(s) or entity named above. If
> you're not the intended
> > recipient, note that disclosing, copying, distributing or using this
> information
> > is prohibited. If you've received this email in error, please let me
> know immediately
> > on the email address above. Thank you.
> > We monitor our email system, and may record your emails.
> > British Telecommunications plc
> > Registered office: 81 Newgate Street London EC1A 7AJ
> > Registered in England no: 1800000
> >
> >
> >
> >
> >
> >
> >
> >> -----Original Message-----
> >> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
> Of
> >> Rui Costa
> >> Sent: 08 July 2011 01:15
> >> To: David Allan I; Stewart Bryant
> >> Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
> >> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> >> (Proactive Connectivity Verification, Continuity Check and Remote
> >> Defect indication for MPLS Transport Profile) to Proposed Standard
> >>
> >> David,
> >>
> >> Reading something, keeping it on record, without effect in the draft
> >> and "ignoring comments" have IMHO similar outcomes. As author of the
> >> draft you are free to do it. These standards have a great impact in
> our
> >> work, so i'm also free to write what i did.
> >>
> >>
> >>
> >>
> >> Stewart,
> >>
> >> My technical concerns regarding this draft were expressed...
> >> ...in the (ITU-T -> IETF, Feb/2011) liaison regarding it (LS281, i
> >> believe);
> >> ...in operators' meetings' that took place during ITU-T's Feb/2011
> >> plenary meeting;
> >> ...in a comparison session that took place during that same ITU-T
> >> meeting.
> >> Some:
> >>
> >> CC/CV
> >> I don't understand the need for 2 types of packets: a single type
> >> allows CC; mismatching identifiers in the same CC packets allow CV.
> >> Besides adding complexity, we whether always activate both or
> >> potentiate undetected mismerges.
> >> (BTW: can't understand how we propose one ACH codepoint to CC,
> another
> >> for CV, [counting other drafts, another for frame loss ...] but
> don't
> >> consider assigning 1 single ACH protocol identifier codepoint as
> >> requested by ITU-T)
> >>
> >> Uni P2P / P2MP
> >> I can't see how BFD will support unidir and hence P2MP other than...
> >>
> >> ...eliminating the session "state variable" (down, init, up), aiming
> >> just the state variables we really need, bringing us to something
> >> similar to 1731, eventually with other bits on the wire or...
> >> ...using IP to create the reverse way, which we cannot assume per
> >> requirements;
> >> Will we create a complete different tool for that?
> >> (BFD's B=3D"bidirectional")
> >>
> >> Provisioning list
> >> This is an MPLS profile/subset (and i heard) achievable through a
> >> particular configuration. So, i expect each draft-ietf-mpls-TP-* to
> >> focus on that profile/configuration. However, i keep seeing
> references
> >> f.i. to IP encapsulations unexpected under TP's OAM.
> >> I don't thus understand what the aim is: do we expect this in TP,
> are
> >> we talking about MPLS in general?... The TP profile is never quite
> >> delimited.
> >> Does chapter 4 contain ALL the configurable parameters list agreed
> to
> >> provide in the comparison session?
> >>
> >> Backwards compatibility
> >> This was the main argument risen to ground MPLS-TP OAM on BFD. It's
> not
> >> a better argument than grounding MPLS-TP OAM on 1731 due to its ETH
> >> deployment plus coherence with SDH, OTN, as defended by ITU-T.
> >> For reasons like the above, however, MPLS-TP BFD won't be backwards
> >> compatible with previous BFD (even considering just CC/CV). They
> don't
> >> even share the same codepoint.
> >>
> >> Simplicity
> >> Whether we look to PDH, SDH, OTN or ETH, ITU-T's approach to CC is
> >> simpler: in each flow, a standard defined nr of constant heartbeat
> >> signals (with standard constant or provisioned period - no
> >> auto/negotiated -) means OK. A standard defined number of misses
> means
> >> lost Rx connection. An RDI, the only articulation between Rx and Tx
> >> flows, meaningful in bidirectional applications, allows each pear to
> >> identify Tx problems.
> >> This OAM simplicity is the key for reliable fail finger pointing,
> >> performance reports and protection. Also to allow scaling, more
> >> implementation opportunities/manufacturers, which is valuable for
> >> operators.
> >>
> >>
> >> IMHO, between your MPLS-TP view and MPLS/IP, it becomes more and
> more
> >> difficult to tell which is which.
> >>
> >> Regards,
> >> Rui
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: David Allan I [mailto:david.i.allan@ericsson.com]
> >> Sent: quarta-feira, 6 de Julho de 2011 19:25
> >> To: erminio.ottone_69@libero.it; Rui Costa; ietf@ietf.org; IETF-
> >> Announce
> >> Cc: mpls@ietf.org
> >> Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> >> 05.txt> (Proactive Connectivity Verification, Continuity Check and
> >> Remote Defect indication for MPLS Transport Profile) to Proposed
> >> Standard
> >>
> >> Hi Erminio:
> >>
> >> <snipped>
> >>> Several service providers regarded this draft as not meeting their
> >>> transport networks' needs.
> >>
> >> E> This is a true statement: the solution in this draft is useless
> for
> >> many MPLS- TP deployments.
> >>
> >> The two statements do not necessarily follow.
> >>
> >> What we established during discussions at the SG15 plenary in
> February
> >> was that the issue some service providers had was that the IETF BFD
> >> solution exceeded their requirements in that there was additional
> >> functionality they did not see a need for, and that they considered
> any
> >> additional functionality parasitic.
> >>
> >> However this is a consequence of adapting an existing technology to
> a
> >> new application. I do not see any way around that. And the entire
> joint
> >> project was based on the premise of engineering re-use not
> greenfield
> >> design. That is what it said on the tin up front, and IMO why when
> the
> >> IETF started down this path packet transport transitioned from being
> a
> >> minority sport to mainstream, so it is a bit late to cry foul....
> >>
> >> My 2 cents
> >> Dave
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: David Allan I [mailto:david.i.allan@ericsson.com]
> >> Sent: quarta-feira, 6 de Julho de 2011 18:36
> >> To: erminio.ottone_69@libero.it; loa@pi.nu; Rui Costa
> >> Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
> >> Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> >> 05.txt> (Proactive Connectivity Verification, Continuity Check and
> >> Remote Defect indication for MPLS Transport Profile) to Proposed
> >> Standard
> >>
> >> Hi Erminio:
> >>
> >> Two of the three document editors were present at SG15 plenary in
> >> February where the comments originated. The revised meeting schedule
> >> resulted in a day spent going through the document with the editors.
> >> IMO there were lots of discussion and legitimate issues with the
> >> document identified and corrected so it was a useful session. The
> >> liaison of same was in many ways *after the fact*.
> >>
> >> Cheers
> >> Dave
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: erminio.ottone_69@libero.it
> [mailto:erminio.ottone_69@libero.it]
> >> Sent: quarta-feira, 6 de Julho de 2011 18:34
> >> To: Rui Costa; ietf@ietf.org; IETF-Announce
> >> Cc: mpls@ietf.org
> >> Subject: R: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> 05.txt>
> >> (Proactive Connectivity Verification, Continuity Check and Remote
> >> Defect indication for MPLS Transport Profile) to Proposed Standard
> >>
> >> The way this draft has been developed is a bit strange.
> >>
> >> The poll for its adoption as a WG document was halted by the MPLS WG
> >> chair
> >> because "it is not possible to judge consensus":
> >>
> >> http://www.ietf.org/mail-archive/web/mpls/current/msg04502.html
> >>
> >> The lack of consensus was motivated by serious technical concerns
> >> raised by
> >> several transport experts during the poll.
> >>
> >> Nevertheless the MPLS WG chair decided to adopt the draft as a WG
> >> document:
> >>
> >> http://www.ietf.org/mail-archive/web/mpls/current/msg04512.html
> >>
> >> After several WG revisions and WG LCs, the technical issues have not
> >> been
> >> resolved.
> >>
> >>> Several service providers regarded this draft as not meeting their
> >> transport
> >> networks' needs.
> >>
> >> This is a true statement: the solution in this draft is useless for
> >> many MPLS-
> >> TP deployments.
> >>
> >>
> >> -----Original Message-----
> >> From: erminio.ottone_69@libero.it
> [mailto:erminio.ottone_69@libero.it]
> >> Sent: quarta-feira, 6 de Julho de 2011 18:26
> >> To: loa@pi.nu; Rui Costa
> >> Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
> >> Subject: R: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> 05.txt>
> >> (Proactive Connectivity Verification, Continuity Check and Remote
> >> Defect indication for MPLS Transport Profile) to Proposed Standard
> >>
> >>> Version -04 of the document was published June 28th.
> >>>
> >>> The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
> >>> June 29th.
> >>>
> >>
> >> So when the WG LC to confirm the LC comment resolution has been
> >> launched?
> >>
> >> The proto write-up says:
> >>
> >>            It has also passed a working roup call to verify that LC
> >> comments
> >> were correctly with minor comments.
> >>
> >> It also says:
> >>
> >>            The comments has been
> >>            carefully discussed between the authors and people making
> >> the
> >> comments and
> >>            has been resolved.
> >>
> >> But it seems that some comments have not been discussed with the
> >> authors of
> >> the comments. When ITU-T Q10/15 has been involved in discussing its
> >> comments?
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: Loa Andersson [mailto:loa@pi.nu]
> >> Sent: quarta-feira, 6 de Julho de 2011 16:44
> >> To: Rui Costa
> >> Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
> >> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> >> (Proactive Connectivity Verification, Continuity Check and Remote
> >> Defect indication for MPLS Transport Profile) to Proposed Standard
> >>
> >> All,
> >>
> >> Since someone has commented about the process used for resolving
> >> questions on
> >> draft-ietf-mpls-tp-cc-cv-rdi I am supplying some details below.
> >>
> >> The history of draft-ietf-mpls-tp-cc-cv-rdi working group review
> >> process is:
> >>
> >> On February 3rd 2011 the working group last call was issued
> >> on version -03
> >>
> >>      This was copied to the the Ad Hoc Team List
> >>      and liaised to SG15 also on February 3rd
> >>
> >>      This working group last call ended om Feb 28
> >>
> >>
> >>      On Feb 28 we also received a liaison with comments from SG15
> >>
> >>
> >> The authors compiled a list of all comments received  as part the
> MPLS
> >> working group last call; these  comments - and the intended
> resolution
> >> -
> >> is included in the meeting minutes from the Prague meeting:
> >>
> >>
> >>      http://www.ietf.org/proceedings/80/slides/mpls-9.pdf
> >>
> >>
> >>  During the IETF meeting in Prague, we agreed with the BFD working
> >>  group to do a separate working group last callfor the BFD working
> >>  group
> >>
> >> The (BFD) working group last call was started on March 30th and ran
> >> for 13 days. The last call ended on April 11th.
> >>
> >>  The authors have since worked hard to resolve comments, some
> >>  issue has been brought to the working group mailing list for
> >>  resolution.
> >>
> >>  Version -04 of the document was published June 28th.
> >>
> >>  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
> >>  June 29th.
> >>
> >>  The AD review resulted in a "New ID needed" due to mostly editorial
> >>  comments. Version -05 was published on June 29 and the IETF last
> call
> >>  started as soon as the new ID was avaialbe.
> >>
> >>  The current list of Last Call Comments resoltion is also avaiable
> at:
> >>  http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
> >>
> >>  The list of issues that the authors kept very carefully, shows
> >> without
> >> doubt
> >>  that no comments been ignored.
> >>
> >>  Loa
> >>  mpls wg document shepherd
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: David Allan I [mailto:david.i.allan@ericsson.com]
> >> Sent: quarta-feira, 6 de Julho de 2011 14:58
> >> To: Rui Costa; ietf@ietf.org; IETF-Announce
> >> Cc: mpls@ietf.org
> >> Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> >> (Proactive Connectivity Verification, Continuity Check and Remote
> >> Defect indication for MPLS Transport Profile) to Proposed Standard
> >>
> >> Hi Rui:
> >>
> >> The comments were not ignored, the resolution of the Q10 comments as
> >> well as those collected from the MPLS WG was presented at the last
> >> IETF. My spreadsheet from which that report was generated and has
> been
> >> augmented to include the BFD WG comments is available at
> >> http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
> >>
> >> So you know...
> >> Dave
> >>
> >>
> >> -----Original Message-----
> >> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
> Of
> >> Rui Costa
> >> Sent: segunda-feira, 4 de Julho de 2011 23:03
> >> To: ietf@ietf.org; IETF-Announce
> >> Cc: mpls@ietf.org
> >> Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> >> (Proactive Connectivity Verification, Continuity Check and Remote
> >> Defect indication for MPLS Transport Profile) to Proposed Standard
> >>
> >> IMHO and for the record:
> >>
> >> ITU-T comments regarding this draft haven't been discussed with ITU-
> T
> >> but were simply ignored. No LS describing these comments' resolution
> >> was sent.
> >>
> >> Several service providers regarded this draft as not meeting their
> >> transport networks' needs.
> >>
> >> [The v03 draft was published in Feb and went to WG LC.
> >> The v04 draft addressing WG LC comments was published on the 28th
> June
> >> (same date as the proto write-up).
> >> When was the WG LC launched, to verify LC comments resolution?]
> >>
> >> Regards,
> >> Rui
> >>
> >>
> >> -----Original Message-----
> >> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
> Of
> >> The IESG
> >> Sent: quinta-feira, 30 de Junho de 2011 14:47
> >> To: IETF-Announce
> >> Cc: mpls@ietf.org
> >> Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> >> (Proactive Connectivity Verification, Continuity Check and Remote
> >> Defect indication for MPLS Transport Profile) to Proposed Standard
> >>
> >>
> >> The IESG has received a request from the Multiprotocol Label
> Switching
> >> WG
> >> (mpls) to consider the following document:
> >> - 'Proactive Connectivity Verification, Continuity Check and Remote
> >>   Defect indication for MPLS Transport Profile'
> >>  <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally, comments
> may
> >> be
> >> sent to iesg@ietf.org instead. In either case, please retain the
> >> beginning of the Subject line to allow automated sorting.
> >>
> >> Abstract
> >>
> >>   Continuity Check, Proactive Connectivity Verification and Remote
> >>   Defect Indication functionalities are required for MPLS-TP OAM.
> >>
> >>   Continuity Check monitors the integrity of the continuity of the
> >>   label switched path for any loss of continuity defect.
> Connectivity
> >>   verification monitors the integrity of the routing of the label
> >>   switched path between sink and source for any connectivity issues.
> >>   Remote defect indication enables an End Point to report, to its
> >>   associated End Point, a fault or defect condition that it detects
> on
> >>   a pseudo wire, label switched path or Section.
> >>
> >>   This document specifies methods for proactive continuity check,
> >>   continuity verification, and remote defect indication for MPLS-TP
> >>   label switched paths, pseudo wires and Sections using
> Bidirectional
> >>   Forwarding Detection.
> >>
> >>
> >> The file can be obtained via
> >> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
> >>
> >> IESG discussion can be tracked via
> >> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
> >>
> >>
> >> No IPR declarations have been submitted directly on this I-D.
> >> _______________________________________________
> >> mpls mailing list
> >> mpls@ietf.org
> >> https://www.ietf.org/mailman/listinfo/mpls
> >>
> >>
> >> _______________________________________________
> >> Ietf mailing list
> >> Ietf@ietf.org
> >> https://www.ietf.org/mailman/listinfo/ietf
> >> _______________________________________________
> >> mpls mailing list
> >> mpls@ietf.org
> >> https://www.ietf.org/mailman/listinfo/mpls
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls
> >


From david.i.allan@ericsson.com  Fri Jul  8 09:30:16 2011
Return-Path: <david.i.allan@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 94F8421F8BA8; Fri,  8 Jul 2011 09:30:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, J_CHICKENPOX_21=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 XY4lJmmz2VqF; Fri,  8 Jul 2011 09:30:14 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by ietfa.amsl.com (Postfix) with ESMTP id C411F21F8BA6; Fri,  8 Jul 2011 09:30:14 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p68GU94S006108; Fri, 8 Jul 2011 11:30:11 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.253]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Fri, 8 Jul 2011 12:30:08 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: Thomas Nadeau <tnadeau@lucidvision.com>, "neil.2.harrison@bt.com" <neil.2.harrison@bt.com>
Date: Fri, 8 Jul 2011 12:30:07 -0400
Subject: RE: [mpls] Last Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication for	MPLS	Transport	Profile) to Proposed Standard
Thread-Topic: [mpls] Last Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication for	MPLS	Transport	Profile) to Proposed Standard
Thread-Index: Acw9g3d5g1+ZEhf1RAmo9qGC9yjrgAAB+HhQ
Message-ID: <60C093A41B5E45409A19D42CF7786DFD52213544C9@EUSAACMS0703.eamcs.ericsson.se>
References: <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B6BC@INOAVREX11.ptin.corpPT.com> <6D3D47CB84BDE349BC23BF1C94E316E4405A7550DE@EMV62-UKRD.domain1.systemhost.net> <BA2E2586-1B10-4954-93A2-E8EE9DF0427F@lucidvision.com>
In-Reply-To: <BA2E2586-1B10-4954-93A2-E8EE9DF0427F@lucidvision.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: Mon, 11 Jul 2011 08:10:57 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "ietf-announce@ietf.org" <ietf-announce@ietf.org>, "stbryant@cisco.com" <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: Fri, 08 Jul 2011 16:30:16 -0000

I think there is some confusion here....

The only CC in isolation in the draft is the option to use RFC 5885. Which =
then is a network design issue.

Draft cc-cv-rdi used by itself is CV always on. It is just not EVERY PDU th=
at requires CV processing so there are CC and CV PDUs interleaved. Mis-conn=
ectivity detection is network wide and fairly authoritative (unless we are =
discussing a mode of failure in which only "some" packets leak, which means=
 even an always on CV may not be so unlucky as to leak and be detected).

So I think we are in agreement on that front...
Dave



-----Original Message-----
From: Thomas Nadeau [mailto:tnadeau@lucidvision.com]
Sent: Friday, July 08, 2011 8:27 AM
To: neil.2.harrison@bt.com
Cc: RCosta@ptinovacao.pt; David Allan I; stbryant@cisco.com; mpls@ietf.org;=
 ietf@ietf.org; ietf-announce@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proac=
tive Connectivity Verification, Continuity Check and Remote Defect indicati=
on for MPLS Transport Profile) to Proposed Standard


On Jul 8, 2011, at 3:15 AM, <neil.2.harrison@bt.com> wrote:

> Got to say I agree with Rui on much of what he says here.  And I absolute=
ly resonate with his point on the need for simplicity.  The reason OAM need=
s to be as simple as possible is because it must be super reliable....we do=
 not want to consciously build in weaknesses, esp unnecessary ones.... this=
 also implies minimal config.  We could all do better on this.  For example=
:
>
> -       Rui is dead right a CC function is fairly useless, we only need a=
 CV function...the ATM OAM in I.610 suffers from this problem (and few othe=
rs like AIS and the assumed use of request/response MLT to diagnose leaking=
/mismerging traffic...request/response OAM won't work with unidirectional d=
efects).

        While you are entitled to your opinion, I personally think there ar=
e enough requirements elsewhere to have both CC and CV functions.  But we d=
igress. Are you actually asking that the CC functionality be removed from t=
he draft or just making a general comment?

> -       all packet layer networks should not have an AIS OAM message....v=
ery obvious for the cl-ps mode of course.  The co-ps mode is also not like =
the co-cs mode.  One has to consciously manufacture AIS messages and target=
 them to specific clients in the co-ps mode....who may have taken action in=
 their own layer network and 'moved elsewhere' anyway, ie a total waste of =
time now.  AIS is actually unnecessary wrt providing information anyway, it=
 simply represents an in-built weakness of just something else to go wrong =
which itself will create problems.

        What does that comment have to do with the actual draft in question=
?

> -       creating preconfigured TCM sublayers is just asking for trouble I=
MO.  It is far smarter to simply create a single end-end OAM CV (and when r=
equired PM) flow and tap this off at intermediate nodes on the *rare* occas=
ions one wants to do.

        Again, what does this have to do with the actual draft in question?

        --tom




>
> regards, Neil
>
> This email contains BT information, which may be privileged or confidenti=
al.
> It's meant only for the individual(s) or entity named above. If you're
> not the intended recipient, note that disclosing, copying,
> distributing or using this information is prohibited. If you've
> received this email in error, please let me know immediately on the email=
 address above. Thank you.
> We monitor our email system, and may record your emails.
> British Telecommunications plc
> Registered office: 81 Newgate Street London EC1A 7AJ Registered in
> England no: 1800000
>
>
>
>
>
>
>
>> -----Original Message-----
>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
>> Of Rui Costa
>> Sent: 08 July 2011 01:15
>> To: David Allan I; Stewart Bryant
>> Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
>> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
>> (Proactive Connectivity Verification, Continuity Check and Remote
>> Defect indication for MPLS Transport Profile) to Proposed Standard
>>
>> David,
>>
>> Reading something, keeping it on record, without effect in the draft
>> and "ignoring comments" have IMHO similar outcomes. As author of the
>> draft you are free to do it. These standards have a great impact in
>> our work, so i'm also free to write what i did.
>>
>>
>>
>>
>> Stewart,
>>
>> My technical concerns regarding this draft were expressed...
>> ...in the (ITU-T -> IETF, Feb/2011) liaison regarding it (LS281, i
>> believe); ...in operators' meetings' that took place during ITU-T's
>> Feb/2011 plenary meeting; ...in a comparison session that took place
>> during that same ITU-T meeting.
>> Some:
>>
>> CC/CV
>> I don't understand the need for 2 types of packets: a single type
>> allows CC; mismatching identifiers in the same CC packets allow CV.
>> Besides adding complexity, we whether always activate both or
>> potentiate undetected mismerges.
>> (BTW: can't understand how we propose one ACH codepoint to CC,
>> another for CV, [counting other drafts, another for frame loss ...]
>> but don't consider assigning 1 single ACH protocol identifier
>> codepoint as requested by ITU-T)
>>
>> Uni P2P / P2MP
>> I can't see how BFD will support unidir and hence P2MP other than...
>>
>> ...eliminating the session "state variable" (down, init, up), aiming
>> just the state variables we really need, bringing us to something
>> similar to 1731, eventually with other bits on the wire or...
>> ...using IP to create the reverse way, which we cannot assume per
>> requirements; Will we create a complete different tool for that?
>> (BFD's B=3D"bidirectional")
>>
>> Provisioning list
>> This is an MPLS profile/subset (and i heard) achievable through a
>> particular configuration. So, i expect each draft-ietf-mpls-TP-* to
>> focus on that profile/configuration. However, i keep seeing
>> references f.i. to IP encapsulations unexpected under TP's OAM.
>> I don't thus understand what the aim is: do we expect this in TP, are
>> we talking about MPLS in general?... The TP profile is never quite
>> delimited.
>> Does chapter 4 contain ALL the configurable parameters list agreed to
>> provide in the comparison session?
>>
>> Backwards compatibility
>> This was the main argument risen to ground MPLS-TP OAM on BFD. It's
>> not a better argument than grounding MPLS-TP OAM on 1731 due to its
>> ETH deployment plus coherence with SDH, OTN, as defended by ITU-T.
>> For reasons like the above, however, MPLS-TP BFD won't be backwards
>> compatible with previous BFD (even considering just CC/CV). They
>> don't even share the same codepoint.
>>
>> Simplicity
>> Whether we look to PDH, SDH, OTN or ETH, ITU-T's approach to CC is
>> simpler: in each flow, a standard defined nr of constant heartbeat
>> signals (with standard constant or provisioned period - no
>> auto/negotiated -) means OK. A standard defined number of misses
>> means lost Rx connection. An RDI, the only articulation between Rx
>> and Tx flows, meaningful in bidirectional applications, allows each
>> pear to identify Tx problems.
>> This OAM simplicity is the key for reliable fail finger pointing,
>> performance reports and protection. Also to allow scaling, more
>> implementation opportunities/manufacturers, which is valuable for
>> operators.
>>
>>
>> IMHO, between your MPLS-TP view and MPLS/IP, it becomes more and more
>> difficult to tell which is which.
>>
>> Regards,
>> Rui
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: David Allan I [mailto:david.i.allan@ericsson.com]
>> Sent: quarta-feira, 6 de Julho de 2011 19:25
>> To: erminio.ottone_69@libero.it; Rui Costa; ietf@ietf.org; IETF-
>> Announce
>> Cc: mpls@ietf.org
>> Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
>> 05.txt> (Proactive Connectivity Verification, Continuity Check and
>> Remote Defect indication for MPLS Transport Profile) to Proposed
>> Standard
>>
>> Hi Erminio:
>>
>> <snipped>
>>> Several service providers regarded this draft as not meeting their
>>> transport networks' needs.
>>
>> E> This is a true statement: the solution in this draft is useless
>> E> for
>> many MPLS- TP deployments.
>>
>> The two statements do not necessarily follow.
>>
>> What we established during discussions at the SG15 plenary in
>> February was that the issue some service providers had was that the
>> IETF BFD solution exceeded their requirements in that there was
>> additional functionality they did not see a need for, and that they
>> considered any additional functionality parasitic.
>>
>> However this is a consequence of adapting an existing technology to a
>> new application. I do not see any way around that. And the entire
>> joint project was based on the premise of engineering re-use not
>> greenfield design. That is what it said on the tin up front, and IMO
>> why when the IETF started down this path packet transport
>> transitioned from being a minority sport to mainstream, so it is a bit l=
ate to cry foul....
>>
>> My 2 cents
>> Dave
>>
>>
>>
>>
>> -----Original Message-----
>> From: David Allan I [mailto:david.i.allan@ericsson.com]
>> Sent: quarta-feira, 6 de Julho de 2011 18:36
>> To: erminio.ottone_69@libero.it; loa@pi.nu; Rui Costa
>> Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
>> Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
>> 05.txt> (Proactive Connectivity Verification, Continuity Check and
>> Remote Defect indication for MPLS Transport Profile) to Proposed
>> Standard
>>
>> Hi Erminio:
>>
>> Two of the three document editors were present at SG15 plenary in
>> February where the comments originated. The revised meeting schedule
>> resulted in a day spent going through the document with the editors.
>> IMO there were lots of discussion and legitimate issues with the
>> document identified and corrected so it was a useful session. The
>> liaison of same was in many ways *after the fact*.
>>
>> Cheers
>> Dave
>>
>>
>>
>>
>> -----Original Message-----
>> From: erminio.ottone_69@libero.it
>> [mailto:erminio.ottone_69@libero.it]
>> Sent: quarta-feira, 6 de Julho de 2011 18:34
>> To: Rui Costa; ietf@ietf.org; IETF-Announce
>> Cc: mpls@ietf.org
>> Subject: R: Re: [mpls] Last Call:
>> <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
>> (Proactive Connectivity Verification, Continuity Check and Remote
>> Defect indication for MPLS Transport Profile) to Proposed Standard
>>
>> The way this draft has been developed is a bit strange.
>>
>> The poll for its adoption as a WG document was halted by the MPLS WG
>> chair because "it is not possible to judge consensus":
>>
>> http://www.ietf.org/mail-archive/web/mpls/current/msg04502.html
>>
>> The lack of consensus was motivated by serious technical concerns
>> raised by several transport experts during the poll.
>>
>> Nevertheless the MPLS WG chair decided to adopt the draft as a WG
>> document:
>>
>> http://www.ietf.org/mail-archive/web/mpls/current/msg04512.html
>>
>> After several WG revisions and WG LCs, the technical issues have not
>> been resolved.
>>
>>> Several service providers regarded this draft as not meeting their
>> transport
>> networks' needs.
>>
>> This is a true statement: the solution in this draft is useless for
>> many MPLS- TP deployments.
>>
>>
>> -----Original Message-----
>> From: erminio.ottone_69@libero.it
>> [mailto:erminio.ottone_69@libero.it]
>> Sent: quarta-feira, 6 de Julho de 2011 18:26
>> To: loa@pi.nu; Rui Costa
>> Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
>> Subject: R: Re: [mpls] Last Call:
>> <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
>> (Proactive Connectivity Verification, Continuity Check and Remote
>> Defect indication for MPLS Transport Profile) to Proposed Standard
>>
>>> Version -04 of the document was published June 28th.
>>>
>>> The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
>>> June 29th.
>>>
>>
>> So when the WG LC to confirm the LC comment resolution has been
>> launched?
>>
>> The proto write-up says:
>>
>>            It has also passed a working roup call to verify that LC
>> comments were correctly with minor comments.
>>
>> It also says:
>>
>>            The comments has been
>>            carefully discussed between the authors and people making
>> the comments and
>>            has been resolved.
>>
>> But it seems that some comments have not been discussed with the
>> authors of the comments. When ITU-T Q10/15 has been involved in
>> discussing its comments?
>>
>>
>>
>>
>> -----Original Message-----
>> From: Loa Andersson [mailto:loa@pi.nu]
>> Sent: quarta-feira, 6 de Julho de 2011 16:44
>> To: Rui Costa
>> Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
>> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
>> (Proactive Connectivity Verification, Continuity Check and Remote
>> Defect indication for MPLS Transport Profile) to Proposed Standard
>>
>> All,
>>
>> Since someone has commented about the process used for resolving
>> questions on draft-ietf-mpls-tp-cc-cv-rdi I am supplying some details
>> below.
>>
>> The history of draft-ietf-mpls-tp-cc-cv-rdi working group review
>> process is:
>>
>> On February 3rd 2011 the working group last call was issued on
>> version -03
>>
>>      This was copied to the the Ad Hoc Team List
>>      and liaised to SG15 also on February 3rd
>>
>>      This working group last call ended om Feb 28
>>
>>
>>      On Feb 28 we also received a liaison with comments from SG15
>>
>>
>> The authors compiled a list of all comments received  as part the
>> MPLS working group last call; these  comments - and the intended
>> resolution
>> -
>> is included in the meeting minutes from the Prague meeting:
>>
>>
>>      http://www.ietf.org/proceedings/80/slides/mpls-9.pdf
>>
>>
>>  During the IETF meeting in Prague, we agreed with the BFD working
>> group to do a separate working group last callfor the BFD working
>> group
>>
>> The (BFD) working group last call was started on March 30th and ran
>> for 13 days. The last call ended on April 11th.
>>
>>  The authors have since worked hard to resolve comments, some  issue
>> has been brought to the working group mailing list for  resolution.
>>
>>  Version -04 of the document was published June 28th.
>>
>>  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
>> June 29th.
>>
>>  The AD review resulted in a "New ID needed" due to mostly editorial
>> comments. Version -05 was published on June 29 and the IETF last call
>> started as soon as the new ID was avaialbe.
>>
>>  The current list of Last Call Comments resoltion is also avaiable at:
>>  http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
>>
>>  The list of issues that the authors kept very carefully, shows
>> without doubt  that no comments been ignored.
>>
>>  Loa
>>  mpls wg document shepherd
>>
>>
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: David Allan I [mailto:david.i.allan@ericsson.com]
>> Sent: quarta-feira, 6 de Julho de 2011 14:58
>> To: Rui Costa; ietf@ietf.org; IETF-Announce
>> Cc: mpls@ietf.org
>> Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
>> (Proactive Connectivity Verification, Continuity Check and Remote
>> Defect indication for MPLS Transport Profile) to Proposed Standard
>>
>> Hi Rui:
>>
>> The comments were not ignored, the resolution of the Q10 comments as
>> well as those collected from the MPLS WG was presented at the last
>> IETF. My spreadsheet from which that report was generated and has
>> been augmented to include the BFD WG comments is available at
>> http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
>>
>> So you know...
>> Dave
>>
>>
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
>> Of Rui Costa
>> Sent: segunda-feira, 4 de Julho de 2011 23:03
>> To: ietf@ietf.org; IETF-Announce
>> Cc: mpls@ietf.org
>> Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
>> (Proactive Connectivity Verification, Continuity Check and Remote
>> Defect indication for MPLS Transport Profile) to Proposed Standard
>>
>> IMHO and for the record:
>>
>> ITU-T comments regarding this draft haven't been discussed with ITU-T
>> but were simply ignored. No LS describing these comments' resolution
>> was sent.
>>
>> Several service providers regarded this draft as not meeting their
>> transport networks' needs.
>>
>> [The v03 draft was published in Feb and went to WG LC.
>> The v04 draft addressing WG LC comments was published on the 28th
>> June (same date as the proto write-up).
>> When was the WG LC launched, to verify LC comments resolution?]
>>
>> Regards,
>> Rui
>>
>>
>> -----Original Message-----
>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
>> Of The IESG
>> Sent: quinta-feira, 30 de Junho de 2011 14:47
>> To: IETF-Announce
>> Cc: mpls@ietf.org
>> Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
>> (Proactive Connectivity Verification, Continuity Check and Remote
>> Defect indication for MPLS Transport Profile) to Proposed Standard
>>
>>
>> The IESG has received a request from the Multiprotocol Label
>> Switching WG
>> (mpls) to consider the following document:
>> - 'Proactive Connectivity Verification, Continuity Check and Remote
>>   Defect indication for MPLS Transport Profile'
>>  <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally,
>> comments may be sent to iesg@ietf.org instead. In either case, please
>> retain the beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>   Continuity Check, Proactive Connectivity Verification and Remote
>>   Defect Indication functionalities are required for MPLS-TP OAM.
>>
>>   Continuity Check monitors the integrity of the continuity of the
>>   label switched path for any loss of continuity defect. Connectivity
>>   verification monitors the integrity of the routing of the label
>>   switched path between sink and source for any connectivity issues.
>>   Remote defect indication enables an End Point to report, to its
>>   associated End Point, a fault or defect condition that it detects on
>>   a pseudo wire, label switched path or Section.
>>
>>   This document specifies methods for proactive continuity check,
>>   continuity verification, and remote defect indication for MPLS-TP
>>   label switched paths, pseudo wires and Sections using Bidirectional
>>   Forwarding Detection.
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>
>>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>


From neil.2.harrison@bt.com  Fri Jul  8 09:39:42 2011
Return-Path: <neil.2.harrison@bt.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B00E21F8B61; Fri,  8 Jul 2011 09:39:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level: 
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_21=0.6, J_CHICKENPOX_81=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 Hg367DnS1a1z; Fri,  8 Jul 2011 09:39:40 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp64.intersmtp.COM [62.239.224.237]) by ietfa.amsl.com (Postfix) with ESMTP id 5536121F8B5F; Fri,  8 Jul 2011 09:39:40 -0700 (PDT)
Received: from EVMHT63-UKRD.domain1.systemhost.net (10.36.3.100) by RDW083A008ED64.smtp-e4.hygiene.service (10.187.98.13) with Microsoft SMTP Server (TLS) id 8.3.159.2; Fri, 8 Jul 2011 17:39:39 +0100
Received: from EMV62-UKRD.domain1.systemhost.net ([169.254.1.186]) by EVMHT63-UKRD.domain1.systemhost.net ([10.36.3.100]) with mapi; Fri, 8 Jul 2011 17:39:39 +0100
From: <neil.2.harrison@bt.com>
To: <david.i.allan@ericsson.com>, <tnadeau@lucidvision.com>
Date: Fri, 8 Jul 2011 17:39:32 +0100
Subject: RE: [mpls] Last Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication for	MPLS	Transport	Profile) to Proposed Standard
Thread-Topic: [mpls] Last Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication for	MPLS	Transport	Profile) to Proposed Standard
Thread-Index: Acw9g3d5g1+ZEhf1RAmo9qGC9yjrgAAB+HhQAABF93A=
Message-ID: <6D3D47CB84BDE349BC23BF1C94E316E4405A7557A0@EMV62-UKRD.domain1.systemhost.net>
References: <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B6BC@INOAVREX11.ptin.corpPT.com> <6D3D47CB84BDE349BC23BF1C94E316E4405A7550DE@EMV62-UKRD.domain1.systemhost.net> <BA2E2586-1B10-4954-93A2-E8EE9DF0427F@lucidvision.com> <60C093A41B5E45409A19D42CF7786DFD52213544C9@EUSAACMS0703.eamcs.ericsson.se>
In-Reply-To: <60C093A41B5E45409A19D42CF7786DFD52213544C9@EUSAACMS0703.eamcs.ericsson.se>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 11 Jul 2011 08:10:57 -0700
Cc: mpls@ietf.org, ietf@ietf.org, ietf-announce@ietf.org, 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: Fri, 08 Jul 2011 16:39:42 -0000

Thanks Dave.  If we don't have this (ie CV function on all connections/LSPs=
) then there is potential security risk wrt leaking traffic.  Note that bes=
ides trad nested sublayered LSPs in the same layer network this also applie=
s to nested LSPs belonging to different MPLS-TP layer networks (may be same=
 or different party ownership).  This point about the OAM CV function also =
ought to be captured in any security drafts.

regards, Neil

> -----Original Message-----
> From: David Allan I [mailto:david.i.allan@ericsson.com]
> Sent: 08 July 2011 17:30
> To: Thomas Nadeau; Harrison,N,Neil,DKQ7 R
> Cc: RCosta@ptinovacao.pt; stbryant@cisco.com; mpls@ietf.org;
> ietf@ietf.org; ietf-announce@ietf.org
> Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote
> Defect indication for MPLS Transport Profile) to Proposed Standard
>
> I think there is some confusion here....
>
> The only CC in isolation in the draft is the option to use RFC 5885.
> Which then is a network design issue.
>
> Draft cc-cv-rdi used by itself is CV always on. It is just not EVERY
> PDU that requires CV processing so there are CC and CV PDUs
> interleaved. Mis-connectivity detection is network wide and fairly
> authoritative (unless we are discussing a mode of failure in which only
> "some" packets leak, which means even an always on CV may not be so
> unlucky as to leak and be detected).
>
> So I think we are in agreement on that front...
> Dave
>
>
>
> -----Original Message-----
> From: Thomas Nadeau [mailto:tnadeau@lucidvision.com]
> Sent: Friday, July 08, 2011 8:27 AM
> To: neil.2.harrison@bt.com
> Cc: RCosta@ptinovacao.pt; David Allan I; stbryant@cisco.com;
> mpls@ietf.org; ietf@ietf.org; ietf-announce@ietf.org
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote
> Defect indication for MPLS Transport Profile) to Proposed Standard
>
>
> On Jul 8, 2011, at 3:15 AM, <neil.2.harrison@bt.com> wrote:
>
> > Got to say I agree with Rui on much of what he says here.  And I
> absolutely resonate with his point on the need for simplicity.  The
> reason OAM needs to be as simple as possible is because it must be
> super reliable....we do not want to consciously build in weaknesses,
> esp unnecessary ones.... this also implies minimal config.  We could
> all do better on this.  For example:
> >
> > -       Rui is dead right a CC function is fairly useless, we only
> need a CV function...the ATM OAM in I.610 suffers from this problem
> (and few others like AIS and the assumed use of request/response MLT to
> diagnose leaking/mismerging traffic...request/response OAM won't work
> with unidirectional defects).
>
>         While you are entitled to your opinion, I personally think
> there are enough requirements elsewhere to have both CC and CV
> functions.  But we digress. Are you actually asking that the CC
> functionality be removed from the draft or just making a general
> comment?
>
> > -       all packet layer networks should not have an AIS OAM
> message....very obvious for the cl-ps mode of course.  The co-ps mode
> is also not like the co-cs mode.  One has to consciously manufacture
> AIS messages and target them to specific clients in the co-ps
> mode....who may have taken action in their own layer network and 'moved
> elsewhere' anyway, ie a total waste of time now.  AIS is actually
> unnecessary wrt providing information anyway, it simply represents an
> in-built weakness of just something else to go wrong which itself will
> create problems.
>
>         What does that comment have to do with the actual draft in
> question?
>
> > -       creating preconfigured TCM sublayers is just asking for
> trouble IMO.  It is far smarter to simply create a single end-end OAM
> CV (and when required PM) flow and tap this off at intermediate nodes
> on the *rare* occasions one wants to do.
>
>         Again, what does this have to do with the actual draft in
> question?
>
>         --tom
>
>
>
>
> >
> > regards, Neil
> >
> > This email contains BT information, which may be privileged or
> confidential.
> > It's meant only for the individual(s) or entity named above. If
> you're
> > not the intended recipient, note that disclosing, copying,
> > distributing or using this information is prohibited. If you've
> > received this email in error, please let me know immediately on the
> email address above. Thank you.
> > We monitor our email system, and may record your emails.
> > British Telecommunications plc
> > Registered office: 81 Newgate Street London EC1A 7AJ Registered in
> > England no: 1800000
> >
> >
> >
> >
> >
> >
> >
> >> -----Original Message-----
> >> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
> >> Of Rui Costa
> >> Sent: 08 July 2011 01:15
> >> To: David Allan I; Stewart Bryant
> >> Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
> >> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> >> (Proactive Connectivity Verification, Continuity Check and Remote
> >> Defect indication for MPLS Transport Profile) to Proposed Standard
> >>
> >> David,
> >>
> >> Reading something, keeping it on record, without effect in the draft
> >> and "ignoring comments" have IMHO similar outcomes. As author of the
> >> draft you are free to do it. These standards have a great impact in
> >> our work, so i'm also free to write what i did.
> >>
> >>
> >>
> >>
> >> Stewart,
> >>
> >> My technical concerns regarding this draft were expressed...
> >> ...in the (ITU-T -> IETF, Feb/2011) liaison regarding it (LS281, i
> >> believe); ...in operators' meetings' that took place during ITU-T's
> >> Feb/2011 plenary meeting; ...in a comparison session that took place
> >> during that same ITU-T meeting.
> >> Some:
> >>
> >> CC/CV
> >> I don't understand the need for 2 types of packets: a single type
> >> allows CC; mismatching identifiers in the same CC packets allow CV.
> >> Besides adding complexity, we whether always activate both or
> >> potentiate undetected mismerges.
> >> (BTW: can't understand how we propose one ACH codepoint to CC,
> >> another for CV, [counting other drafts, another for frame loss ...]
> >> but don't consider assigning 1 single ACH protocol identifier
> >> codepoint as requested by ITU-T)
> >>
> >> Uni P2P / P2MP
> >> I can't see how BFD will support unidir and hence P2MP other than...
> >>
> >> ...eliminating the session "state variable" (down, init, up), aiming
> >> just the state variables we really need, bringing us to something
> >> similar to 1731, eventually with other bits on the wire or...
> >> ...using IP to create the reverse way, which we cannot assume per
> >> requirements; Will we create a complete different tool for that?
> >> (BFD's B=3D"bidirectional")
> >>
> >> Provisioning list
> >> This is an MPLS profile/subset (and i heard) achievable through a
> >> particular configuration. So, i expect each draft-ietf-mpls-TP-* to
> >> focus on that profile/configuration. However, i keep seeing
> >> references f.i. to IP encapsulations unexpected under TP's OAM.
> >> I don't thus understand what the aim is: do we expect this in TP,
> are
> >> we talking about MPLS in general?... The TP profile is never quite
> >> delimited.
> >> Does chapter 4 contain ALL the configurable parameters list agreed
> to
> >> provide in the comparison session?
> >>
> >> Backwards compatibility
> >> This was the main argument risen to ground MPLS-TP OAM on BFD. It's
> >> not a better argument than grounding MPLS-TP OAM on 1731 due to its
> >> ETH deployment plus coherence with SDH, OTN, as defended by ITU-T.
> >> For reasons like the above, however, MPLS-TP BFD won't be backwards
> >> compatible with previous BFD (even considering just CC/CV). They
> >> don't even share the same codepoint.
> >>
> >> Simplicity
> >> Whether we look to PDH, SDH, OTN or ETH, ITU-T's approach to CC is
> >> simpler: in each flow, a standard defined nr of constant heartbeat
> >> signals (with standard constant or provisioned period - no
> >> auto/negotiated -) means OK. A standard defined number of misses
> >> means lost Rx connection. An RDI, the only articulation between Rx
> >> and Tx flows, meaningful in bidirectional applications, allows each
> >> pear to identify Tx problems.
> >> This OAM simplicity is the key for reliable fail finger pointing,
> >> performance reports and protection. Also to allow scaling, more
> >> implementation opportunities/manufacturers, which is valuable for
> >> operators.
> >>
> >>
> >> IMHO, between your MPLS-TP view and MPLS/IP, it becomes more and
> more
> >> difficult to tell which is which.
> >>
> >> Regards,
> >> Rui
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: David Allan I [mailto:david.i.allan@ericsson.com]
> >> Sent: quarta-feira, 6 de Julho de 2011 19:25
> >> To: erminio.ottone_69@libero.it; Rui Costa; ietf@ietf.org; IETF-
> >> Announce
> >> Cc: mpls@ietf.org
> >> Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> >> 05.txt> (Proactive Connectivity Verification, Continuity Check and
> >> Remote Defect indication for MPLS Transport Profile) to Proposed
> >> Standard
> >>
> >> Hi Erminio:
> >>
> >> <snipped>
> >>> Several service providers regarded this draft as not meeting their
> >>> transport networks' needs.
> >>
> >> E> This is a true statement: the solution in this draft is useless
> >> E> for
> >> many MPLS- TP deployments.
> >>
> >> The two statements do not necessarily follow.
> >>
> >> What we established during discussions at the SG15 plenary in
> >> February was that the issue some service providers had was that the
> >> IETF BFD solution exceeded their requirements in that there was
> >> additional functionality they did not see a need for, and that they
> >> considered any additional functionality parasitic.
> >>
> >> However this is a consequence of adapting an existing technology to
> a
> >> new application. I do not see any way around that. And the entire
> >> joint project was based on the premise of engineering re-use not
> >> greenfield design. That is what it said on the tin up front, and IMO
> >> why when the IETF started down this path packet transport
> >> transitioned from being a minority sport to mainstream, so it is a
> bit late to cry foul....
> >>
> >> My 2 cents
> >> Dave
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: David Allan I [mailto:david.i.allan@ericsson.com]
> >> Sent: quarta-feira, 6 de Julho de 2011 18:36
> >> To: erminio.ottone_69@libero.it; loa@pi.nu; Rui Costa
> >> Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
> >> Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> >> 05.txt> (Proactive Connectivity Verification, Continuity Check and
> >> Remote Defect indication for MPLS Transport Profile) to Proposed
> >> Standard
> >>
> >> Hi Erminio:
> >>
> >> Two of the three document editors were present at SG15 plenary in
> >> February where the comments originated. The revised meeting schedule
> >> resulted in a day spent going through the document with the editors.
> >> IMO there were lots of discussion and legitimate issues with the
> >> document identified and corrected so it was a useful session. The
> >> liaison of same was in many ways *after the fact*.
> >>
> >> Cheers
> >> Dave
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: erminio.ottone_69@libero.it
> >> [mailto:erminio.ottone_69@libero.it]
> >> Sent: quarta-feira, 6 de Julho de 2011 18:34
> >> To: Rui Costa; ietf@ietf.org; IETF-Announce
> >> Cc: mpls@ietf.org
> >> Subject: R: Re: [mpls] Last Call:
> >> <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> >> (Proactive Connectivity Verification, Continuity Check and Remote
> >> Defect indication for MPLS Transport Profile) to Proposed Standard
> >>
> >> The way this draft has been developed is a bit strange.
> >>
> >> The poll for its adoption as a WG document was halted by the MPLS WG
> >> chair because "it is not possible to judge consensus":
> >>
> >> http://www.ietf.org/mail-archive/web/mpls/current/msg04502.html
> >>
> >> The lack of consensus was motivated by serious technical concerns
> >> raised by several transport experts during the poll.
> >>
> >> Nevertheless the MPLS WG chair decided to adopt the draft as a WG
> >> document:
> >>
> >> http://www.ietf.org/mail-archive/web/mpls/current/msg04512.html
> >>
> >> After several WG revisions and WG LCs, the technical issues have not
> >> been resolved.
> >>
> >>> Several service providers regarded this draft as not meeting their
> >> transport
> >> networks' needs.
> >>
> >> This is a true statement: the solution in this draft is useless for
> >> many MPLS- TP deployments.
> >>
> >>
> >> -----Original Message-----
> >> From: erminio.ottone_69@libero.it
> >> [mailto:erminio.ottone_69@libero.it]
> >> Sent: quarta-feira, 6 de Julho de 2011 18:26
> >> To: loa@pi.nu; Rui Costa
> >> Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
> >> Subject: R: Re: [mpls] Last Call:
> >> <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> >> (Proactive Connectivity Verification, Continuity Check and Remote
> >> Defect indication for MPLS Transport Profile) to Proposed Standard
> >>
> >>> Version -04 of the document was published June 28th.
> >>>
> >>> The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
> >>> June 29th.
> >>>
> >>
> >> So when the WG LC to confirm the LC comment resolution has been
> >> launched?
> >>
> >> The proto write-up says:
> >>
> >>            It has also passed a working roup call to verify that LC
> >> comments were correctly with minor comments.
> >>
> >> It also says:
> >>
> >>            The comments has been
> >>            carefully discussed between the authors and people making
> >> the comments and
> >>            has been resolved.
> >>
> >> But it seems that some comments have not been discussed with the
> >> authors of the comments. When ITU-T Q10/15 has been involved in
> >> discussing its comments?
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: Loa Andersson [mailto:loa@pi.nu]
> >> Sent: quarta-feira, 6 de Julho de 2011 16:44
> >> To: Rui Costa
> >> Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
> >> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> >> (Proactive Connectivity Verification, Continuity Check and Remote
> >> Defect indication for MPLS Transport Profile) to Proposed Standard
> >>
> >> All,
> >>
> >> Since someone has commented about the process used for resolving
> >> questions on draft-ietf-mpls-tp-cc-cv-rdi I am supplying some
> details
> >> below.
> >>
> >> The history of draft-ietf-mpls-tp-cc-cv-rdi working group review
> >> process is:
> >>
> >> On February 3rd 2011 the working group last call was issued on
> >> version -03
> >>
> >>      This was copied to the the Ad Hoc Team List
> >>      and liaised to SG15 also on February 3rd
> >>
> >>      This working group last call ended om Feb 28
> >>
> >>
> >>      On Feb 28 we also received a liaison with comments from SG15
> >>
> >>
> >> The authors compiled a list of all comments received  as part the
> >> MPLS working group last call; these  comments - and the intended
> >> resolution
> >> -
> >> is included in the meeting minutes from the Prague meeting:
> >>
> >>
> >>      http://www.ietf.org/proceedings/80/slides/mpls-9.pdf
> >>
> >>
> >>  During the IETF meeting in Prague, we agreed with the BFD working
> >> group to do a separate working group last callfor the BFD working
> >> group
> >>
> >> The (BFD) working group last call was started on March 30th and ran
> >> for 13 days. The last call ended on April 11th.
> >>
> >>  The authors have since worked hard to resolve comments, some  issue
> >> has been brought to the working group mailing list for  resolution.
> >>
> >>  Version -04 of the document was published June 28th.
> >>
> >>  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
> >> June 29th.
> >>
> >>  The AD review resulted in a "New ID needed" due to mostly editorial
> >> comments. Version -05 was published on June 29 and the IETF last
> call
> >> started as soon as the new ID was avaialbe.
> >>
> >>  The current list of Last Call Comments resoltion is also avaiable
> at:
> >>  http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
> >>
> >>  The list of issues that the authors kept very carefully, shows
> >> without doubt  that no comments been ignored.
> >>
> >>  Loa
> >>  mpls wg document shepherd
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: David Allan I [mailto:david.i.allan@ericsson.com]
> >> Sent: quarta-feira, 6 de Julho de 2011 14:58
> >> To: Rui Costa; ietf@ietf.org; IETF-Announce
> >> Cc: mpls@ietf.org
> >> Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> >> (Proactive Connectivity Verification, Continuity Check and Remote
> >> Defect indication for MPLS Transport Profile) to Proposed Standard
> >>
> >> Hi Rui:
> >>
> >> The comments were not ignored, the resolution of the Q10 comments as
> >> well as those collected from the MPLS WG was presented at the last
> >> IETF. My spreadsheet from which that report was generated and has
> >> been augmented to include the BFD WG comments is available at
> >> http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
> >>
> >> So you know...
> >> Dave
> >>
> >>
> >> -----Original Message-----
> >> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
> >> Of Rui Costa
> >> Sent: segunda-feira, 4 de Julho de 2011 23:03
> >> To: ietf@ietf.org; IETF-Announce
> >> Cc: mpls@ietf.org
> >> Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> >> (Proactive Connectivity Verification, Continuity Check and Remote
> >> Defect indication for MPLS Transport Profile) to Proposed Standard
> >>
> >> IMHO and for the record:
> >>
> >> ITU-T comments regarding this draft haven't been discussed with ITU-
> T
> >> but were simply ignored. No LS describing these comments' resolution
> >> was sent.
> >>
> >> Several service providers regarded this draft as not meeting their
> >> transport networks' needs.
> >>
> >> [The v03 draft was published in Feb and went to WG LC.
> >> The v04 draft addressing WG LC comments was published on the 28th
> >> June (same date as the proto write-up).
> >> When was the WG LC launched, to verify LC comments resolution?]
> >>
> >> Regards,
> >> Rui
> >>
> >>
> >> -----Original Message-----
> >> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
> >> Of The IESG
> >> Sent: quinta-feira, 30 de Junho de 2011 14:47
> >> To: IETF-Announce
> >> Cc: mpls@ietf.org
> >> Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> >> (Proactive Connectivity Verification, Continuity Check and Remote
> >> Defect indication for MPLS Transport Profile) to Proposed Standard
> >>
> >>
> >> The IESG has received a request from the Multiprotocol Label
> >> Switching WG
> >> (mpls) to consider the following document:
> >> - 'Proactive Connectivity Verification, Continuity Check and Remote
> >>   Defect indication for MPLS Transport Profile'
> >>  <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally,
> >> comments may be sent to iesg@ietf.org instead. In either case,
> please
> >> retain the beginning of the Subject line to allow automated sorting.
> >>
> >> Abstract
> >>
> >>   Continuity Check, Proactive Connectivity Verification and Remote
> >>   Defect Indication functionalities are required for MPLS-TP OAM.
> >>
> >>   Continuity Check monitors the integrity of the continuity of the
> >>   label switched path for any loss of continuity defect.
> Connectivity
> >>   verification monitors the integrity of the routing of the label
> >>   switched path between sink and source for any connectivity issues.
> >>   Remote defect indication enables an End Point to report, to its
> >>   associated End Point, a fault or defect condition that it detects
> on
> >>   a pseudo wire, label switched path or Section.
> >>
> >>   This document specifies methods for proactive continuity check,
> >>   continuity verification, and remote defect indication for MPLS-TP
> >>   label switched paths, pseudo wires and Sections using
> Bidirectional
> >>   Forwarding Detection.
> >>
> >>
> >> The file can be obtained via
> >> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
> >>
> >> IESG discussion can be tracked via
> >> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
> >>
> >>
> >> No IPR declarations have been submitted directly on this I-D.
> >> _______________________________________________
> >> mpls mailing list
> >> mpls@ietf.org
> >> https://www.ietf.org/mailman/listinfo/mpls
> >>
> >>
> >> _______________________________________________
> >> Ietf mailing list
> >> Ietf@ietf.org
> >> https://www.ietf.org/mailman/listinfo/ietf
> >> _______________________________________________
> >> mpls mailing list
> >> mpls@ietf.org
> >> https://www.ietf.org/mailman/listinfo/mpls
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls
> >


From david.i.allan@ericsson.com  Fri Jul  8 09:42:29 2011
Return-Path: <david.i.allan@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 E390021F8A49; Fri,  8 Jul 2011 09:42:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.913
X-Spam-Level: 
X-Spam-Status: No, score=-5.913 tagged_above=-999 required=5 tests=[AWL=-0.514, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, J_CHICKENPOX_81=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 H0O6w90nWFBo; Fri,  8 Jul 2011 09:42:28 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by ietfa.amsl.com (Postfix) with ESMTP id 2514821F8B23; Fri,  8 Jul 2011 09:42:26 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p68Gg5Dp008246; Fri, 8 Jul 2011 11:42:22 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.253]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Fri, 8 Jul 2011 12:42:02 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: "neil.2.harrison@bt.com" <neil.2.harrison@bt.com>, "tnadeau@lucidvision.com" <tnadeau@lucidvision.com>
Date: Fri, 8 Jul 2011 12:42:01 -0400
Subject: RE: [mpls] Last Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication for	MPLS	Transport	Profile) to Proposed Standard
Thread-Topic: [mpls] Last Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication for	MPLS	Transport	Profile) to Proposed Standard
Thread-Index: Acw9g3d5g1+ZEhf1RAmo9qGC9yjrgAAB+HhQAABF93AAAFWVAA==
Message-ID: <60C093A41B5E45409A19D42CF7786DFD52213544E5@EUSAACMS0703.eamcs.ericsson.se>
References: <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B6BC@INOAVREX11.ptin.corpPT.com> <6D3D47CB84BDE349BC23BF1C94E316E4405A7550DE@EMV62-UKRD.domain1.systemhost.net> <BA2E2586-1B10-4954-93A2-E8EE9DF0427F@lucidvision.com> <60C093A41B5E45409A19D42CF7786DFD52213544C9@EUSAACMS0703.eamcs.ericsson.se> <6D3D47CB84BDE349BC23BF1C94E316E4405A7557A0@EMV62-UKRD.domain1.systemhost.net>
In-Reply-To: <6D3D47CB84BDE349BC23BF1C94E316E4405A7557A0@EMV62-UKRD.domain1.systemhost.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-Mailman-Approved-At: Mon, 11 Jul 2011 08:10:58 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "ietf-announce@ietf.org" <ietf-announce@ietf.org>, "stbryant@cisco.com" <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: Fri, 08 Jul 2011 16:42:30 -0000

Hi Neil:

As a result of Adrians AD review, some text to that effect was added to the=
 Security Considerations section.

Have a good weekend
Dave

-----Original Message-----
From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com]
Sent: Friday, July 08, 2011 9:40 AM
To: David Allan I; tnadeau@lucidvision.com
Cc: RCosta@ptinovacao.pt; stbryant@cisco.com; mpls@ietf.org; ietf@ietf.org;=
 ietf-announce@ietf.org
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proac=
tive Connectivity Verification, Continuity Check and Remote Defect indicati=
on for MPLS Transport Profile) to Proposed Standard

Thanks Dave.  If we don't have this (ie CV function on all connections/LSPs=
) then there is potential security risk wrt leaking traffic.  Note that bes=
ides trad nested sublayered LSPs in the same layer network this also applie=
s to nested LSPs belonging to different MPLS-TP layer networks (may be same=
 or different party ownership).  This point about the OAM CV function also =
ought to be captured in any security drafts.

regards, Neil

> -----Original Message-----
> From: David Allan I [mailto:david.i.allan@ericsson.com]
> Sent: 08 July 2011 17:30
> To: Thomas Nadeau; Harrison,N,Neil,DKQ7 R
> Cc: RCosta@ptinovacao.pt; stbryant@cisco.com; mpls@ietf.org;
> ietf@ietf.org; ietf-announce@ietf.org
> Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote
> Defect indication for MPLS Transport Profile) to Proposed Standard
>
> I think there is some confusion here....
>
> The only CC in isolation in the draft is the option to use RFC 5885.
> Which then is a network design issue.
>
> Draft cc-cv-rdi used by itself is CV always on. It is just not EVERY
> PDU that requires CV processing so there are CC and CV PDUs
> interleaved. Mis-connectivity detection is network wide and fairly
> authoritative (unless we are discussing a mode of failure in which
> only "some" packets leak, which means even an always on CV may not be
> so unlucky as to leak and be detected).
>
> So I think we are in agreement on that front...
> Dave
>
>
>
> -----Original Message-----
> From: Thomas Nadeau [mailto:tnadeau@lucidvision.com]
> Sent: Friday, July 08, 2011 8:27 AM
> To: neil.2.harrison@bt.com
> Cc: RCosta@ptinovacao.pt; David Allan I; stbryant@cisco.com;
> mpls@ietf.org; ietf@ietf.org; ietf-announce@ietf.org
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote
> Defect indication for MPLS Transport Profile) to Proposed Standard
>
>
> On Jul 8, 2011, at 3:15 AM, <neil.2.harrison@bt.com> wrote:
>
> > Got to say I agree with Rui on much of what he says here.  And I
> absolutely resonate with his point on the need for simplicity.  The
> reason OAM needs to be as simple as possible is because it must be
> super reliable....we do not want to consciously build in weaknesses,
> esp unnecessary ones.... this also implies minimal config.  We could
> all do better on this.  For example:
> >
> > -       Rui is dead right a CC function is fairly useless, we only
> need a CV function...the ATM OAM in I.610 suffers from this problem
> (and few others like AIS and the assumed use of request/response MLT
> to diagnose leaking/mismerging traffic...request/response OAM won't
> work with unidirectional defects).
>
>         While you are entitled to your opinion, I personally think
> there are enough requirements elsewhere to have both CC and CV
> functions.  But we digress. Are you actually asking that the CC
> functionality be removed from the draft or just making a general
> comment?
>
> > -       all packet layer networks should not have an AIS OAM
> message....very obvious for the cl-ps mode of course.  The co-ps mode
> is also not like the co-cs mode.  One has to consciously manufacture
> AIS messages and target them to specific clients in the co-ps
> mode....who may have taken action in their own layer network and
> 'moved elsewhere' anyway, ie a total waste of time now.  AIS is
> actually unnecessary wrt providing information anyway, it simply
> represents an in-built weakness of just something else to go wrong
> which itself will create problems.
>
>         What does that comment have to do with the actual draft in
> question?
>
> > -       creating preconfigured TCM sublayers is just asking for
> trouble IMO.  It is far smarter to simply create a single end-end OAM
> CV (and when required PM) flow and tap this off at intermediate nodes
> on the *rare* occasions one wants to do.
>
>         Again, what does this have to do with the actual draft in
> question?
>
>         --tom
>
>
>
>
> >
> > regards, Neil
> >
> > This email contains BT information, which may be privileged or
> confidential.
> > It's meant only for the individual(s) or entity named above. If
> you're
> > not the intended recipient, note that disclosing, copying,
> > distributing or using this information is prohibited. If you've
> > received this email in error, please let me know immediately on the
> email address above. Thank you.
> > We monitor our email system, and may record your emails.
> > British Telecommunications plc
> > Registered office: 81 Newgate Street London EC1A 7AJ Registered in
> > England no: 1800000
> >
> >
> >
> >
> >
> >
> >
> >> -----Original Message-----
> >> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On
> >> Behalf Of Rui Costa
> >> Sent: 08 July 2011 01:15
> >> To: David Allan I; Stewart Bryant
> >> Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
> >> Subject: Re: [mpls] Last Call:
> >> <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> >> (Proactive Connectivity Verification, Continuity Check and Remote
> >> Defect indication for MPLS Transport Profile) to Proposed Standard
> >>
> >> David,
> >>
> >> Reading something, keeping it on record, without effect in the
> >> draft and "ignoring comments" have IMHO similar outcomes. As author
> >> of the draft you are free to do it. These standards have a great
> >> impact in our work, so i'm also free to write what i did.
> >>
> >>
> >>
> >>
> >> Stewart,
> >>
> >> My technical concerns regarding this draft were expressed...
> >> ...in the (ITU-T -> IETF, Feb/2011) liaison regarding it (LS281, i
> >> believe); ...in operators' meetings' that took place during ITU-T's
> >> Feb/2011 plenary meeting; ...in a comparison session that took
> >> place during that same ITU-T meeting.
> >> Some:
> >>
> >> CC/CV
> >> I don't understand the need for 2 types of packets: a single type
> >> allows CC; mismatching identifiers in the same CC packets allow CV.
> >> Besides adding complexity, we whether always activate both or
> >> potentiate undetected mismerges.
> >> (BTW: can't understand how we propose one ACH codepoint to CC,
> >> another for CV, [counting other drafts, another for frame loss ...]
> >> but don't consider assigning 1 single ACH protocol identifier
> >> codepoint as requested by ITU-T)
> >>
> >> Uni P2P / P2MP
> >> I can't see how BFD will support unidir and hence P2MP other than...
> >>
> >> ...eliminating the session "state variable" (down, init, up),
> >> aiming just the state variables we really need, bringing us to
> >> something similar to 1731, eventually with other bits on the wire or..=
.
> >> ...using IP to create the reverse way, which we cannot assume per
> >> requirements; Will we create a complete different tool for that?
> >> (BFD's B=3D"bidirectional")
> >>
> >> Provisioning list
> >> This is an MPLS profile/subset (and i heard) achievable through a
> >> particular configuration. So, i expect each draft-ietf-mpls-TP-* to
> >> focus on that profile/configuration. However, i keep seeing
> >> references f.i. to IP encapsulations unexpected under TP's OAM.
> >> I don't thus understand what the aim is: do we expect this in TP,
> are
> >> we talking about MPLS in general?... The TP profile is never quite
> >> delimited.
> >> Does chapter 4 contain ALL the configurable parameters list agreed
> to
> >> provide in the comparison session?
> >>
> >> Backwards compatibility
> >> This was the main argument risen to ground MPLS-TP OAM on BFD. It's
> >> not a better argument than grounding MPLS-TP OAM on 1731 due to its
> >> ETH deployment plus coherence with SDH, OTN, as defended by ITU-T.
> >> For reasons like the above, however, MPLS-TP BFD won't be backwards
> >> compatible with previous BFD (even considering just CC/CV). They
> >> don't even share the same codepoint.
> >>
> >> Simplicity
> >> Whether we look to PDH, SDH, OTN or ETH, ITU-T's approach to CC is
> >> simpler: in each flow, a standard defined nr of constant heartbeat
> >> signals (with standard constant or provisioned period - no
> >> auto/negotiated -) means OK. A standard defined number of misses
> >> means lost Rx connection. An RDI, the only articulation between Rx
> >> and Tx flows, meaningful in bidirectional applications, allows each
> >> pear to identify Tx problems.
> >> This OAM simplicity is the key for reliable fail finger pointing,
> >> performance reports and protection. Also to allow scaling, more
> >> implementation opportunities/manufacturers, which is valuable for
> >> operators.
> >>
> >>
> >> IMHO, between your MPLS-TP view and MPLS/IP, it becomes more and
> more
> >> difficult to tell which is which.
> >>
> >> Regards,
> >> Rui
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: David Allan I [mailto:david.i.allan@ericsson.com]
> >> Sent: quarta-feira, 6 de Julho de 2011 19:25
> >> To: erminio.ottone_69@libero.it; Rui Costa; ietf@ietf.org; IETF-
> >> Announce
> >> Cc: mpls@ietf.org
> >> Subject: RE: [mpls] R: Re: Last Call:
> >> <draft-ietf-mpls-tp-cc-cv-rdi- 05.txt> (Proactive Connectivity
> >> Verification, Continuity Check and Remote Defect indication for
> >> MPLS Transport Profile) to Proposed Standard
> >>
> >> Hi Erminio:
> >>
> >> <snipped>
> >>> Several service providers regarded this draft as not meeting their
> >>> transport networks' needs.
> >>
> >> E> This is a true statement: the solution in this draft is useless
> >> E> for
> >> many MPLS- TP deployments.
> >>
> >> The two statements do not necessarily follow.
> >>
> >> What we established during discussions at the SG15 plenary in
> >> February was that the issue some service providers had was that the
> >> IETF BFD solution exceeded their requirements in that there was
> >> additional functionality they did not see a need for, and that they
> >> considered any additional functionality parasitic.
> >>
> >> However this is a consequence of adapting an existing technology to
> a
> >> new application. I do not see any way around that. And the entire
> >> joint project was based on the premise of engineering re-use not
> >> greenfield design. That is what it said on the tin up front, and
> >> IMO why when the IETF started down this path packet transport
> >> transitioned from being a minority sport to mainstream, so it is a
> bit late to cry foul....
> >>
> >> My 2 cents
> >> Dave
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: David Allan I [mailto:david.i.allan@ericsson.com]
> >> Sent: quarta-feira, 6 de Julho de 2011 18:36
> >> To: erminio.ottone_69@libero.it; loa@pi.nu; Rui Costa
> >> Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
> >> Subject: RE: [mpls] R: Re: Last Call:
> >> <draft-ietf-mpls-tp-cc-cv-rdi- 05.txt> (Proactive Connectivity
> >> Verification, Continuity Check and Remote Defect indication for
> >> MPLS Transport Profile) to Proposed Standard
> >>
> >> Hi Erminio:
> >>
> >> Two of the three document editors were present at SG15 plenary in
> >> February where the comments originated. The revised meeting
> >> schedule resulted in a day spent going through the document with the e=
ditors.
> >> IMO there were lots of discussion and legitimate issues with the
> >> document identified and corrected so it was a useful session. The
> >> liaison of same was in many ways *after the fact*.
> >>
> >> Cheers
> >> Dave
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: erminio.ottone_69@libero.it
> >> [mailto:erminio.ottone_69@libero.it]
> >> Sent: quarta-feira, 6 de Julho de 2011 18:34
> >> To: Rui Costa; ietf@ietf.org; IETF-Announce
> >> Cc: mpls@ietf.org
> >> Subject: R: Re: [mpls] Last Call:
> >> <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> >> (Proactive Connectivity Verification, Continuity Check and Remote
> >> Defect indication for MPLS Transport Profile) to Proposed Standard
> >>
> >> The way this draft has been developed is a bit strange.
> >>
> >> The poll for its adoption as a WG document was halted by the MPLS
> >> WG chair because "it is not possible to judge consensus":
> >>
> >> http://www.ietf.org/mail-archive/web/mpls/current/msg04502.html
> >>
> >> The lack of consensus was motivated by serious technical concerns
> >> raised by several transport experts during the poll.
> >>
> >> Nevertheless the MPLS WG chair decided to adopt the draft as a WG
> >> document:
> >>
> >> http://www.ietf.org/mail-archive/web/mpls/current/msg04512.html
> >>
> >> After several WG revisions and WG LCs, the technical issues have
> >> not been resolved.
> >>
> >>> Several service providers regarded this draft as not meeting their
> >> transport
> >> networks' needs.
> >>
> >> This is a true statement: the solution in this draft is useless for
> >> many MPLS- TP deployments.
> >>
> >>
> >> -----Original Message-----
> >> From: erminio.ottone_69@libero.it
> >> [mailto:erminio.ottone_69@libero.it]
> >> Sent: quarta-feira, 6 de Julho de 2011 18:26
> >> To: loa@pi.nu; Rui Costa
> >> Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
> >> Subject: R: Re: [mpls] Last Call:
> >> <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> >> (Proactive Connectivity Verification, Continuity Check and Remote
> >> Defect indication for MPLS Transport Profile) to Proposed Standard
> >>
> >>> Version -04 of the document was published June 28th.
> >>>
> >>> The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
> >>> June 29th.
> >>>
> >>
> >> So when the WG LC to confirm the LC comment resolution has been
> >> launched?
> >>
> >> The proto write-up says:
> >>
> >>            It has also passed a working roup call to verify that LC
> >> comments were correctly with minor comments.
> >>
> >> It also says:
> >>
> >>            The comments has been
> >>            carefully discussed between the authors and people
> >> making the comments and
> >>            has been resolved.
> >>
> >> But it seems that some comments have not been discussed with the
> >> authors of the comments. When ITU-T Q10/15 has been involved in
> >> discussing its comments?
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: Loa Andersson [mailto:loa@pi.nu]
> >> Sent: quarta-feira, 6 de Julho de 2011 16:44
> >> To: Rui Costa
> >> Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
> >> Subject: Re: [mpls] Last Call:
> >> <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> >> (Proactive Connectivity Verification, Continuity Check and Remote
> >> Defect indication for MPLS Transport Profile) to Proposed Standard
> >>
> >> All,
> >>
> >> Since someone has commented about the process used for resolving
> >> questions on draft-ietf-mpls-tp-cc-cv-rdi I am supplying some
> details
> >> below.
> >>
> >> The history of draft-ietf-mpls-tp-cc-cv-rdi working group review
> >> process is:
> >>
> >> On February 3rd 2011 the working group last call was issued on
> >> version -03
> >>
> >>      This was copied to the the Ad Hoc Team List
> >>      and liaised to SG15 also on February 3rd
> >>
> >>      This working group last call ended om Feb 28
> >>
> >>
> >>      On Feb 28 we also received a liaison with comments from SG15
> >>
> >>
> >> The authors compiled a list of all comments received  as part the
> >> MPLS working group last call; these  comments - and the intended
> >> resolution
> >> -
> >> is included in the meeting minutes from the Prague meeting:
> >>
> >>
> >>      http://www.ietf.org/proceedings/80/slides/mpls-9.pdf
> >>
> >>
> >>  During the IETF meeting in Prague, we agreed with the BFD working
> >> group to do a separate working group last callfor the BFD working
> >> group
> >>
> >> The (BFD) working group last call was started on March 30th and ran
> >> for 13 days. The last call ended on April 11th.
> >>
> >>  The authors have since worked hard to resolve comments, some
> >> issue has been brought to the working group mailing list for  resoluti=
on.
> >>
> >>  Version -04 of the document was published June 28th.
> >>
> >>  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
> >> June 29th.
> >>
> >>  The AD review resulted in a "New ID needed" due to mostly
> >> editorial comments. Version -05 was published on June 29 and the
> >> IETF last
> call
> >> started as soon as the new ID was avaialbe.
> >>
> >>  The current list of Last Call Comments resoltion is also avaiable
> at:
> >>  http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
> >>
> >>  The list of issues that the authors kept very carefully, shows
> >> without doubt  that no comments been ignored.
> >>
> >>  Loa
> >>  mpls wg document shepherd
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: David Allan I [mailto:david.i.allan@ericsson.com]
> >> Sent: quarta-feira, 6 de Julho de 2011 14:58
> >> To: Rui Costa; ietf@ietf.org; IETF-Announce
> >> Cc: mpls@ietf.org
> >> Subject: RE: [mpls] Last Call:
> >> <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> >> (Proactive Connectivity Verification, Continuity Check and Remote
> >> Defect indication for MPLS Transport Profile) to Proposed Standard
> >>
> >> Hi Rui:
> >>
> >> The comments were not ignored, the resolution of the Q10 comments
> >> as well as those collected from the MPLS WG was presented at the
> >> last IETF. My spreadsheet from which that report was generated and
> >> has been augmented to include the BFD WG comments is available at
> >> http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
> >>
> >> So you know...
> >> Dave
> >>
> >>
> >> -----Original Message-----
> >> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On
> >> Behalf Of Rui Costa
> >> Sent: segunda-feira, 4 de Julho de 2011 23:03
> >> To: ietf@ietf.org; IETF-Announce
> >> Cc: mpls@ietf.org
> >> Subject: RE: [mpls] Last Call:
> >> <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> >> (Proactive Connectivity Verification, Continuity Check and Remote
> >> Defect indication for MPLS Transport Profile) to Proposed Standard
> >>
> >> IMHO and for the record:
> >>
> >> ITU-T comments regarding this draft haven't been discussed with
> >> ITU-
> T
> >> but were simply ignored. No LS describing these comments'
> >> resolution was sent.
> >>
> >> Several service providers regarded this draft as not meeting their
> >> transport networks' needs.
> >>
> >> [The v03 draft was published in Feb and went to WG LC.
> >> The v04 draft addressing WG LC comments was published on the 28th
> >> June (same date as the proto write-up).
> >> When was the WG LC launched, to verify LC comments resolution?]
> >>
> >> Regards,
> >> Rui
> >>
> >>
> >> -----Original Message-----
> >> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On
> >> Behalf Of The IESG
> >> Sent: quinta-feira, 30 de Junho de 2011 14:47
> >> To: IETF-Announce
> >> Cc: mpls@ietf.org
> >> Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> >> (Proactive Connectivity Verification, Continuity Check and Remote
> >> Defect indication for MPLS Transport Profile) to Proposed Standard
> >>
> >>
> >> The IESG has received a request from the Multiprotocol Label
> >> Switching WG
> >> (mpls) to consider the following document:
> >> - 'Proactive Connectivity Verification, Continuity Check and Remote
> >>   Defect indication for MPLS Transport Profile'
> >>  <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally,
> >> comments may be sent to iesg@ietf.org instead. In either case,
> please
> >> retain the beginning of the Subject line to allow automated sorting.
> >>
> >> Abstract
> >>
> >>   Continuity Check, Proactive Connectivity Verification and Remote
> >>   Defect Indication functionalities are required for MPLS-TP OAM.
> >>
> >>   Continuity Check monitors the integrity of the continuity of the
> >>   label switched path for any loss of continuity defect.
> Connectivity
> >>   verification monitors the integrity of the routing of the label
> >>   switched path between sink and source for any connectivity issues.
> >>   Remote defect indication enables an End Point to report, to its
> >>   associated End Point, a fault or defect condition that it detects
> on
> >>   a pseudo wire, label switched path or Section.
> >>
> >>   This document specifies methods for proactive continuity check,
> >>   continuity verification, and remote defect indication for MPLS-TP
> >>   label switched paths, pseudo wires and Sections using
> Bidirectional
> >>   Forwarding Detection.
> >>
> >>
> >> The file can be obtained via
> >> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
> >>
> >> IESG discussion can be tracked via
> >> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
> >>
> >>
> >> No IPR declarations have been submitted directly on this I-D.
> >> _______________________________________________
> >> mpls mailing list
> >> mpls@ietf.org
> >> https://www.ietf.org/mailman/listinfo/mpls
> >>
> >>
> >> _______________________________________________
> >> Ietf mailing list
> >> Ietf@ietf.org
> >> https://www.ietf.org/mailman/listinfo/ietf
> >> _______________________________________________
> >> mpls mailing list
> >> mpls@ietf.org
> >> https://www.ietf.org/mailman/listinfo/mpls
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls
> >


From neil.2.harrison@bt.com  Fri Jul  8 09:44:03 2011
Return-Path: <neil.2.harrison@bt.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A59A221F8BCC; Fri,  8 Jul 2011 09:44:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.966
X-Spam-Level: 
X-Spam-Status: No, score=-1.966 tagged_above=-999 required=5 tests=[AWL=-0.120, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_21=0.6, J_CHICKENPOX_81=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 7kStQifBiFiH; Fri,  8 Jul 2011 09:44:02 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp64.intersmtp.COM [62.239.224.237]) by ietfa.amsl.com (Postfix) with ESMTP id 2D75221F8BC8; Fri,  8 Jul 2011 09:44:01 -0700 (PDT)
Received: from EVMHT68-UKRD.domain1.systemhost.net (10.36.3.105) by RDW083A008ED64.smtp-e4.hygiene.service (10.187.98.13) with Microsoft SMTP Server (TLS) id 8.3.159.2; Fri, 8 Jul 2011 17:44:00 +0100
Received: from EMV62-UKRD.domain1.systemhost.net ([169.254.1.186]) by EVMHT68-UKRD.domain1.systemhost.net ([10.36.3.105]) with mapi; Fri, 8 Jul 2011 17:44:00 +0100
From: <neil.2.harrison@bt.com>
To: <david.i.allan@ericsson.com>, <tnadeau@lucidvision.com>
Date: Fri, 8 Jul 2011 17:43:56 +0100
Subject: RE: [mpls] Last Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication for	MPLS	Transport	Profile) to Proposed Standard
Thread-Topic: [mpls] Last Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication for	MPLS	Transport	Profile) to Proposed Standard
Thread-Index: Acw9g3d5g1+ZEhf1RAmo9qGC9yjrgAAB+HhQAABF93AAAFWVAAAAE9vA
Message-ID: <6D3D47CB84BDE349BC23BF1C94E316E4405A7557A8@EMV62-UKRD.domain1.systemhost.net>
References: <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B6BC@INOAVREX11.ptin.corpPT.com> <6D3D47CB84BDE349BC23BF1C94E316E4405A7550DE@EMV62-UKRD.domain1.systemhost.net> <BA2E2586-1B10-4954-93A2-E8EE9DF0427F@lucidvision.com> <60C093A41B5E45409A19D42CF7786DFD52213544C9@EUSAACMS0703.eamcs.ericsson.se> <6D3D47CB84BDE349BC23BF1C94E316E4405A7557A0@EMV62-UKRD.domain1.systemhost.net> <60C093A41B5E45409A19D42CF7786DFD52213544E5@EUSAACMS0703.eamcs.ericsson.se>
In-Reply-To: <60C093A41B5E45409A19D42CF7786DFD52213544E5@EUSAACMS0703.eamcs.ericsson.se>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 11 Jul 2011 08:10:57 -0700
Cc: mpls@ietf.org, ietf@ietf.org, ietf-announce@ietf.org, 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: Fri, 08 Jul 2011 16:44:03 -0000

Excellent...well done Adrian!  Thanks Dave for the info.  Have a nice one y=
ourself....

regards, Neil

> -----Original Message-----
> From: David Allan I [mailto:david.i.allan@ericsson.com]
> Sent: 08 July 2011 17:42
> To: Harrison,N,Neil,DKQ7 R; tnadeau@lucidvision.com
> Cc: RCosta@ptinovacao.pt; stbryant@cisco.com; mpls@ietf.org;
> ietf@ietf.org; ietf-announce@ietf.org
> Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote
> Defect indication for MPLS Transport Profile) to Proposed Standard
>
> Hi Neil:
>
> As a result of Adrians AD review, some text to that effect was added to
> the Security Considerations section.
>
> Have a good weekend
> Dave
>
> -----Original Message-----
> From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com]
> Sent: Friday, July 08, 2011 9:40 AM
> To: David Allan I; tnadeau@lucidvision.com
> Cc: RCosta@ptinovacao.pt; stbryant@cisco.com; mpls@ietf.org;
> ietf@ietf.org; ietf-announce@ietf.org
> Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote
> Defect indication for MPLS Transport Profile) to Proposed Standard
>
> Thanks Dave.  If we don't have this (ie CV function on all
> connections/LSPs) then there is potential security risk wrt leaking
> traffic.  Note that besides trad nested sublayered LSPs in the same
> layer network this also applies to nested LSPs belonging to different
> MPLS-TP layer networks (may be same or different party ownership).
> This point about the OAM CV function also ought to be captured in any
> security drafts.
>
> regards, Neil
>
> > -----Original Message-----
> > From: David Allan I [mailto:david.i.allan@ericsson.com]
> > Sent: 08 July 2011 17:30
> > To: Thomas Nadeau; Harrison,N,Neil,DKQ7 R
> > Cc: RCosta@ptinovacao.pt; stbryant@cisco.com; mpls@ietf.org;
> > ietf@ietf.org; ietf-announce@ietf.org
> > Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> > (Proactive Connectivity Verification, Continuity Check and Remote
> > Defect indication for MPLS Transport Profile) to Proposed Standard
> >
> > I think there is some confusion here....
> >
> > The only CC in isolation in the draft is the option to use RFC 5885.
> > Which then is a network design issue.
> >
> > Draft cc-cv-rdi used by itself is CV always on. It is just not EVERY
> > PDU that requires CV processing so there are CC and CV PDUs
> > interleaved. Mis-connectivity detection is network wide and fairly
> > authoritative (unless we are discussing a mode of failure in which
> > only "some" packets leak, which means even an always on CV may not be
> > so unlucky as to leak and be detected).
> >
> > So I think we are in agreement on that front...
> > Dave
> >
> >
> >
> > -----Original Message-----
> > From: Thomas Nadeau [mailto:tnadeau@lucidvision.com]
> > Sent: Friday, July 08, 2011 8:27 AM
> > To: neil.2.harrison@bt.com
> > Cc: RCosta@ptinovacao.pt; David Allan I; stbryant@cisco.com;
> > mpls@ietf.org; ietf@ietf.org; ietf-announce@ietf.org
> > Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> > (Proactive Connectivity Verification, Continuity Check and Remote
> > Defect indication for MPLS Transport Profile) to Proposed Standard
> >
> >
> > On Jul 8, 2011, at 3:15 AM, <neil.2.harrison@bt.com> wrote:
> >
> > > Got to say I agree with Rui on much of what he says here.  And I
> > absolutely resonate with his point on the need for simplicity.  The
> > reason OAM needs to be as simple as possible is because it must be
> > super reliable....we do not want to consciously build in weaknesses,
> > esp unnecessary ones.... this also implies minimal config.  We could
> > all do better on this.  For example:
> > >
> > > -       Rui is dead right a CC function is fairly useless, we only
> > need a CV function...the ATM OAM in I.610 suffers from this problem
> > (and few others like AIS and the assumed use of request/response MLT
> > to diagnose leaking/mismerging traffic...request/response OAM won't
> > work with unidirectional defects).
> >
> >         While you are entitled to your opinion, I personally think
> > there are enough requirements elsewhere to have both CC and CV
> > functions.  But we digress. Are you actually asking that the CC
> > functionality be removed from the draft or just making a general
> > comment?
> >
> > > -       all packet layer networks should not have an AIS OAM
> > message....very obvious for the cl-ps mode of course.  The co-ps mode
> > is also not like the co-cs mode.  One has to consciously manufacture
> > AIS messages and target them to specific clients in the co-ps
> > mode....who may have taken action in their own layer network and
> > 'moved elsewhere' anyway, ie a total waste of time now.  AIS is
> > actually unnecessary wrt providing information anyway, it simply
> > represents an in-built weakness of just something else to go wrong
> > which itself will create problems.
> >
> >         What does that comment have to do with the actual draft in
> > question?
> >
> > > -       creating preconfigured TCM sublayers is just asking for
> > trouble IMO.  It is far smarter to simply create a single end-end OAM
> > CV (and when required PM) flow and tap this off at intermediate nodes
> > on the *rare* occasions one wants to do.
> >
> >         Again, what does this have to do with the actual draft in
> > question?
> >
> >         --tom
> >
> >
> >
> >
> > >
> > > regards, Neil
> > >
> > > This email contains BT information, which may be privileged or
> > confidential.
> > > It's meant only for the individual(s) or entity named above. If
> > you're
> > > not the intended recipient, note that disclosing, copying,
> > > distributing or using this information is prohibited. If you've
> > > received this email in error, please let me know immediately on the
> > email address above. Thank you.
> > > We monitor our email system, and may record your emails.
> > > British Telecommunications plc
> > > Registered office: 81 Newgate Street London EC1A 7AJ Registered in
> > > England no: 1800000
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >> -----Original Message-----
> > >> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On
> > >> Behalf Of Rui Costa
> > >> Sent: 08 July 2011 01:15
> > >> To: David Allan I; Stewart Bryant
> > >> Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
> > >> Subject: Re: [mpls] Last Call:
> > >> <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> > >> (Proactive Connectivity Verification, Continuity Check and Remote
> > >> Defect indication for MPLS Transport Profile) to Proposed Standard
> > >>
> > >> David,
> > >>
> > >> Reading something, keeping it on record, without effect in the
> > >> draft and "ignoring comments" have IMHO similar outcomes. As
> author
> > >> of the draft you are free to do it. These standards have a great
> > >> impact in our work, so i'm also free to write what i did.
> > >>
> > >>
> > >>
> > >>
> > >> Stewart,
> > >>
> > >> My technical concerns regarding this draft were expressed...
> > >> ...in the (ITU-T -> IETF, Feb/2011) liaison regarding it (LS281, i
> > >> believe); ...in operators' meetings' that took place during ITU-
> T's
> > >> Feb/2011 plenary meeting; ...in a comparison session that took
> > >> place during that same ITU-T meeting.
> > >> Some:
> > >>
> > >> CC/CV
> > >> I don't understand the need for 2 types of packets: a single type
> > >> allows CC; mismatching identifiers in the same CC packets allow
> CV.
> > >> Besides adding complexity, we whether always activate both or
> > >> potentiate undetected mismerges.
> > >> (BTW: can't understand how we propose one ACH codepoint to CC,
> > >> another for CV, [counting other drafts, another for frame loss
> ...]
> > >> but don't consider assigning 1 single ACH protocol identifier
> > >> codepoint as requested by ITU-T)
> > >>
> > >> Uni P2P / P2MP
> > >> I can't see how BFD will support unidir and hence P2MP other
> than...
> > >>
> > >> ...eliminating the session "state variable" (down, init, up),
> > >> aiming just the state variables we really need, bringing us to
> > >> something similar to 1731, eventually with other bits on the wire
> or...
> > >> ...using IP to create the reverse way, which we cannot assume per
> > >> requirements; Will we create a complete different tool for that?
> > >> (BFD's B=3D"bidirectional")
> > >>
> > >> Provisioning list
> > >> This is an MPLS profile/subset (and i heard) achievable through a
> > >> particular configuration. So, i expect each draft-ietf-mpls-TP-*
> to
> > >> focus on that profile/configuration. However, i keep seeing
> > >> references f.i. to IP encapsulations unexpected under TP's OAM.
> > >> I don't thus understand what the aim is: do we expect this in TP,
> > are
> > >> we talking about MPLS in general?... The TP profile is never quite
> > >> delimited.
> > >> Does chapter 4 contain ALL the configurable parameters list agreed
> > to
> > >> provide in the comparison session?
> > >>
> > >> Backwards compatibility
> > >> This was the main argument risen to ground MPLS-TP OAM on BFD.
> It's
> > >> not a better argument than grounding MPLS-TP OAM on 1731 due to
> its
> > >> ETH deployment plus coherence with SDH, OTN, as defended by ITU-T.
> > >> For reasons like the above, however, MPLS-TP BFD won't be
> backwards
> > >> compatible with previous BFD (even considering just CC/CV). They
> > >> don't even share the same codepoint.
> > >>
> > >> Simplicity
> > >> Whether we look to PDH, SDH, OTN or ETH, ITU-T's approach to CC is
> > >> simpler: in each flow, a standard defined nr of constant heartbeat
> > >> signals (with standard constant or provisioned period - no
> > >> auto/negotiated -) means OK. A standard defined number of misses
> > >> means lost Rx connection. An RDI, the only articulation between Rx
> > >> and Tx flows, meaningful in bidirectional applications, allows
> each
> > >> pear to identify Tx problems.
> > >> This OAM simplicity is the key for reliable fail finger pointing,
> > >> performance reports and protection. Also to allow scaling, more
> > >> implementation opportunities/manufacturers, which is valuable for
> > >> operators.
> > >>
> > >>
> > >> IMHO, between your MPLS-TP view and MPLS/IP, it becomes more and
> > more
> > >> difficult to tell which is which.
> > >>
> > >> Regards,
> > >> Rui
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: David Allan I [mailto:david.i.allan@ericsson.com]
> > >> Sent: quarta-feira, 6 de Julho de 2011 19:25
> > >> To: erminio.ottone_69@libero.it; Rui Costa; ietf@ietf.org; IETF-
> > >> Announce
> > >> Cc: mpls@ietf.org
> > >> Subject: RE: [mpls] R: Re: Last Call:
> > >> <draft-ietf-mpls-tp-cc-cv-rdi- 05.txt> (Proactive Connectivity
> > >> Verification, Continuity Check and Remote Defect indication for
> > >> MPLS Transport Profile) to Proposed Standard
> > >>
> > >> Hi Erminio:
> > >>
> > >> <snipped>
> > >>> Several service providers regarded this draft as not meeting
> their
> > >>> transport networks' needs.
> > >>
> > >> E> This is a true statement: the solution in this draft is useless
> > >> E> for
> > >> many MPLS- TP deployments.
> > >>
> > >> The two statements do not necessarily follow.
> > >>
> > >> What we established during discussions at the SG15 plenary in
> > >> February was that the issue some service providers had was that
> the
> > >> IETF BFD solution exceeded their requirements in that there was
> > >> additional functionality they did not see a need for, and that
> they
> > >> considered any additional functionality parasitic.
> > >>
> > >> However this is a consequence of adapting an existing technology
> to
> > a
> > >> new application. I do not see any way around that. And the entire
> > >> joint project was based on the premise of engineering re-use not
> > >> greenfield design. That is what it said on the tin up front, and
> > >> IMO why when the IETF started down this path packet transport
> > >> transitioned from being a minority sport to mainstream, so it is a
> > bit late to cry foul....
> > >>
> > >> My 2 cents
> > >> Dave
> > >>
> > >>
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: David Allan I [mailto:david.i.allan@ericsson.com]
> > >> Sent: quarta-feira, 6 de Julho de 2011 18:36
> > >> To: erminio.ottone_69@libero.it; loa@pi.nu; Rui Costa
> > >> Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
> > >> Subject: RE: [mpls] R: Re: Last Call:
> > >> <draft-ietf-mpls-tp-cc-cv-rdi- 05.txt> (Proactive Connectivity
> > >> Verification, Continuity Check and Remote Defect indication for
> > >> MPLS Transport Profile) to Proposed Standard
> > >>
> > >> Hi Erminio:
> > >>
> > >> Two of the three document editors were present at SG15 plenary in
> > >> February where the comments originated. The revised meeting
> > >> schedule resulted in a day spent going through the document with
> the editors.
> > >> IMO there were lots of discussion and legitimate issues with the
> > >> document identified and corrected so it was a useful session. The
> > >> liaison of same was in many ways *after the fact*.
> > >>
> > >> Cheers
> > >> Dave
> > >>
> > >>
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: erminio.ottone_69@libero.it
> > >> [mailto:erminio.ottone_69@libero.it]
> > >> Sent: quarta-feira, 6 de Julho de 2011 18:34
> > >> To: Rui Costa; ietf@ietf.org; IETF-Announce
> > >> Cc: mpls@ietf.org
> > >> Subject: R: Re: [mpls] Last Call:
> > >> <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> > >> (Proactive Connectivity Verification, Continuity Check and Remote
> > >> Defect indication for MPLS Transport Profile) to Proposed Standard
> > >>
> > >> The way this draft has been developed is a bit strange.
> > >>
> > >> The poll for its adoption as a WG document was halted by the MPLS
> > >> WG chair because "it is not possible to judge consensus":
> > >>
> > >> http://www.ietf.org/mail-archive/web/mpls/current/msg04502.html
> > >>
> > >> The lack of consensus was motivated by serious technical concerns
> > >> raised by several transport experts during the poll.
> > >>
> > >> Nevertheless the MPLS WG chair decided to adopt the draft as a WG
> > >> document:
> > >>
> > >> http://www.ietf.org/mail-archive/web/mpls/current/msg04512.html
> > >>
> > >> After several WG revisions and WG LCs, the technical issues have
> > >> not been resolved.
> > >>
> > >>> Several service providers regarded this draft as not meeting
> their
> > >> transport
> > >> networks' needs.
> > >>
> > >> This is a true statement: the solution in this draft is useless
> for
> > >> many MPLS- TP deployments.
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: erminio.ottone_69@libero.it
> > >> [mailto:erminio.ottone_69@libero.it]
> > >> Sent: quarta-feira, 6 de Julho de 2011 18:26
> > >> To: loa@pi.nu; Rui Costa
> > >> Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
> > >> Subject: R: Re: [mpls] Last Call:
> > >> <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> > >> (Proactive Connectivity Verification, Continuity Check and Remote
> > >> Defect indication for MPLS Transport Profile) to Proposed Standard
> > >>
> > >>> Version -04 of the document was published June 28th.
> > >>>
> > >>> The publication request for draft-ietf-mpls-tp-cc-cv-rdi was
> sent
> > >>> June 29th.
> > >>>
> > >>
> > >> So when the WG LC to confirm the LC comment resolution has been
> > >> launched?
> > >>
> > >> The proto write-up says:
> > >>
> > >>            It has also passed a working roup call to verify that
> LC
> > >> comments were correctly with minor comments.
> > >>
> > >> It also says:
> > >>
> > >>            The comments has been
> > >>            carefully discussed between the authors and people
> > >> making the comments and
> > >>            has been resolved.
> > >>
> > >> But it seems that some comments have not been discussed with the
> > >> authors of the comments. When ITU-T Q10/15 has been involved in
> > >> discussing its comments?
> > >>
> > >>
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: Loa Andersson [mailto:loa@pi.nu]
> > >> Sent: quarta-feira, 6 de Julho de 2011 16:44
> > >> To: Rui Costa
> > >> Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
> > >> Subject: Re: [mpls] Last Call:
> > >> <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> > >> (Proactive Connectivity Verification, Continuity Check and Remote
> > >> Defect indication for MPLS Transport Profile) to Proposed Standard
> > >>
> > >> All,
> > >>
> > >> Since someone has commented about the process used for resolving
> > >> questions on draft-ietf-mpls-tp-cc-cv-rdi I am supplying some
> > details
> > >> below.
> > >>
> > >> The history of draft-ietf-mpls-tp-cc-cv-rdi working group review
> > >> process is:
> > >>
> > >> On February 3rd 2011 the working group last call was issued on
> > >> version -03
> > >>
> > >>      This was copied to the the Ad Hoc Team List
> > >>      and liaised to SG15 also on February 3rd
> > >>
> > >>      This working group last call ended om Feb 28
> > >>
> > >>
> > >>      On Feb 28 we also received a liaison with comments from SG15
> > >>
> > >>
> > >> The authors compiled a list of all comments received  as part the
> > >> MPLS working group last call; these  comments - and the intended
> > >> resolution
> > >> -
> > >> is included in the meeting minutes from the Prague meeting:
> > >>
> > >>
> > >>      http://www.ietf.org/proceedings/80/slides/mpls-9.pdf
> > >>
> > >>
> > >>  During the IETF meeting in Prague, we agreed with the BFD working
> > >> group to do a separate working group last callfor the BFD working
> > >> group
> > >>
> > >> The (BFD) working group last call was started on March 30th and
> ran
> > >> for 13 days. The last call ended on April 11th.
> > >>
> > >>  The authors have since worked hard to resolve comments, some
> > >> issue has been brought to the working group mailing list for
> resolution.
> > >>
> > >>  Version -04 of the document was published June 28th.
> > >>
> > >>  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was
> sent
> > >> June 29th.
> > >>
> > >>  The AD review resulted in a "New ID needed" due to mostly
> > >> editorial comments. Version -05 was published on June 29 and the
> > >> IETF last
> > call
> > >> started as soon as the new ID was avaialbe.
> > >>
> > >>  The current list of Last Call Comments resoltion is also avaiable
> > at:
> > >>  http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
> > >>
> > >>  The list of issues that the authors kept very carefully, shows
> > >> without doubt  that no comments been ignored.
> > >>
> > >>  Loa
> > >>  mpls wg document shepherd
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: David Allan I [mailto:david.i.allan@ericsson.com]
> > >> Sent: quarta-feira, 6 de Julho de 2011 14:58
> > >> To: Rui Costa; ietf@ietf.org; IETF-Announce
> > >> Cc: mpls@ietf.org
> > >> Subject: RE: [mpls] Last Call:
> > >> <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> > >> (Proactive Connectivity Verification, Continuity Check and Remote
> > >> Defect indication for MPLS Transport Profile) to Proposed Standard
> > >>
> > >> Hi Rui:
> > >>
> > >> The comments were not ignored, the resolution of the Q10 comments
> > >> as well as those collected from the MPLS WG was presented at the
> > >> last IETF. My spreadsheet from which that report was generated and
> > >> has been augmented to include the BFD WG comments is available at
> > >> http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
> > >>
> > >> So you know...
> > >> Dave
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On
> > >> Behalf Of Rui Costa
> > >> Sent: segunda-feira, 4 de Julho de 2011 23:03
> > >> To: ietf@ietf.org; IETF-Announce
> > >> Cc: mpls@ietf.org
> > >> Subject: RE: [mpls] Last Call:
> > >> <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> > >> (Proactive Connectivity Verification, Continuity Check and Remote
> > >> Defect indication for MPLS Transport Profile) to Proposed Standard
> > >>
> > >> IMHO and for the record:
> > >>
> > >> ITU-T comments regarding this draft haven't been discussed with
> > >> ITU-
> > T
> > >> but were simply ignored. No LS describing these comments'
> > >> resolution was sent.
> > >>
> > >> Several service providers regarded this draft as not meeting their
> > >> transport networks' needs.
> > >>
> > >> [The v03 draft was published in Feb and went to WG LC.
> > >> The v04 draft addressing WG LC comments was published on the 28th
> > >> June (same date as the proto write-up).
> > >> When was the WG LC launched, to verify LC comments resolution?]
> > >>
> > >> Regards,
> > >> Rui
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On
> > >> Behalf Of The IESG
> > >> Sent: quinta-feira, 30 de Junho de 2011 14:47
> > >> To: IETF-Announce
> > >> Cc: mpls@ietf.org
> > >> Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> > >> (Proactive Connectivity Verification, Continuity Check and Remote
> > >> Defect indication for MPLS Transport Profile) to Proposed Standard
> > >>
> > >>
> > >> The IESG has received a request from the Multiprotocol Label
> > >> Switching WG
> > >> (mpls) to consider the following document:
> > >> - 'Proactive Connectivity Verification, Continuity Check and
> Remote
> > >>   Defect indication for MPLS Transport Profile'
> > >>  <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally,
> > >> comments may be sent to iesg@ietf.org instead. In either case,
> > please
> > >> retain the beginning of the Subject line to allow automated
> sorting.
> > >>
> > >> Abstract
> > >>
> > >>   Continuity Check, Proactive Connectivity Verification and Remote
> > >>   Defect Indication functionalities are required for MPLS-TP OAM.
> > >>
> > >>   Continuity Check monitors the integrity of the continuity of the
> > >>   label switched path for any loss of continuity defect.
> > Connectivity
> > >>   verification monitors the integrity of the routing of the label
> > >>   switched path between sink and source for any connectivity
> issues.
> > >>   Remote defect indication enables an End Point to report, to its
> > >>   associated End Point, a fault or defect condition that it
> detects
> > on
> > >>   a pseudo wire, label switched path or Section.
> > >>
> > >>   This document specifies methods for proactive continuity check,
> > >>   continuity verification, and remote defect indication for MPLS-
> TP
> > >>   label switched paths, pseudo wires and Sections using
> > Bidirectional
> > >>   Forwarding Detection.
> > >>
> > >>
> > >> The file can be obtained via
> > >> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
> > >>
> > >> IESG discussion can be tracked via
> > >> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
> > >>
> > >>
> > >> No IPR declarations have been submitted directly on this I-D.
> > >> _______________________________________________
> > >> mpls mailing list
> > >> mpls@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/mpls
> > >>
> > >>
> > >> _______________________________________________
> > >> Ietf mailing list
> > >> Ietf@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/ietf
> > >> _______________________________________________
> > >> mpls mailing list
> > >> mpls@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/mpls
> > > _______________________________________________
> > > mpls mailing list
> > > mpls@ietf.org
> > > https://www.ietf.org/mailman/listinfo/mpls
> > >


From brian.e.carpenter@gmail.com  Mon Jul 11 13:54:43 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 0E58C11E8130; Mon, 11 Jul 2011 13:54:43 -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 KQdm6d5wT-aR; Mon, 11 Jul 2011 13:54:42 -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 C96C711E8117; Mon, 11 Jul 2011 13:54:39 -0700 (PDT)
Received: by vxi40 with SMTP id 40so4437237vxi.31 for <multiple recipients>; Mon, 11 Jul 2011 13:54:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=993dpZ3mqA6vmypVYVwgRZbr4FNcOi3L+YMEMEsqr7U=; b=DIbZh6g7340vyuYsgzArTkDqmdgAysrIkHOXuGR+PY6gX2kvyQLrj7h+O1hfjJog55 Gd2O8neIb/UNYQ//AT/wC1ZnxEU6mh7Ccu+6NTQUSDY9PGSASQgQl1z6gOjkedKtd/PV aGjaxX92tm2l6F/JcnZ0nK/sj79UARgAQ9kew=
Received: by 10.52.99.131 with SMTP id eq3mr789562vdb.51.1310417679283; Mon, 11 Jul 2011 13:54:39 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id dq5sm8294674vbb.16.2011.07.11.13.54.35 (version=SSLv3 cipher=OTHER); Mon, 11 Jul 2011 13:54:38 -0700 (PDT)
Message-ID: <4E1B6309.4050008@gmail.com>
Date: Tue, 12 Jul 2011 08:54: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: "Richard L. Barnes" <rbarnes@bbn.com>
Subject: Re: secdir review of draft-ietf-6man-flow-3697bis
References: <173612BD-2825-4A21-98C7-CA8BD5639368@bbn.com>
In-Reply-To: <173612BD-2825-4A21-98C7-CA8BD5639368@bbn.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: secdir@ietf.org, draft-ietf-6man-flow-3697bis@tools.ietf.org, IETF Discussion <ietf@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jul 2011 20:54:43 -0000

Richard,

Thanks for the review.

On 2011-07-12 01:17, Richard L. Barnes wrote:
> I have reviewed this document as part of the security
> directorate's ongoing effort to review all IETF documents
> being processed by the IESG.  These comments were written
> primarily for the benefit of the security area directors.
> Document editors and WG chairs should treat these comments
> just like any other last call comments.
> 
> This document describes how end hosts and intermediate nodes
> should populate and handle the IPv6 flow label field.  The
> document spends a fair bit of time discussing security
> considerations related to the flow label and its relation to
> IPsec in particular.  Overall, the document does a thorough
> job of discussing security considerations, and I don't think
> there's anything they've clearly missed.
> 
> The only request I would have would be for the authors to add
> a little more discussion around the "theft of service"
> threat.  It would be helpful to detail the
> assumptions/circumstances under which this threat aries --
> namely that networks provide resources based on flow label
> and flow label values are set by end hosts.  

The difficulty about doing this is that (as the WG wanted) we
have dropped almost all of the discussion of flow state
establishment methods, which is really where these risks arise.
To be frank I think that anything we could add would be
hand-waving.

> Given the risks
> that this document discusses, it might be worth considering a
> recommendation that networks SHOULD NOT make resource
> allocation decisions based on flow labels without some
> external means of assurance.  Or some similar warning against
> making resource decisions on a completely unsecured field.

Yes, that makes sense when *not* in the stateless load
distribution scenario.

> 
> Also, purely from a terminology perspective, I found the
> phrase "unintended service" confusing and less accurate than
> the "better service" phrase used in RFC 3697.  It might be
> better to spell this out: " ... an adversary may be able to
> obtain a class of service that the network did not intend to
> provide ... "

Agreed.

However - the I-D cutoff is upon us, so although I will post an
update in the next few minutes, I'm afraid these changes will
not be made before the IESG telechat.

Regards
   Brian Carpenter

From brian.e.carpenter@gmail.com  Mon Jul 11 19:58:35 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 1114711E80D2 for <ietf@ietfa.amsl.com>; Mon, 11 Jul 2011 19:58:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.584
X-Spam-Level: 
X-Spam-Status: No, score=-103.584 tagged_above=-999 required=5 tests=[AWL=-0.141, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tl401Uk-veYH for <ietf@ietfa.amsl.com>; Mon, 11 Jul 2011 19:58:34 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id 4365E11E8072 for <ietf@ietf.org>; Mon, 11 Jul 2011 19:58:34 -0700 (PDT)
Received: by qyk29 with SMTP id 29so3021100qyk.10 for <ietf@ietf.org>; Mon, 11 Jul 2011 19:58:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=sJF9xtYH6JhkYwj7QEHJio2o5b9apQD4isl2/jOsYrA=; b=ge5/0kP1kfnIiHVBxIsGmk7fYmWSqbWkrJe+U44mZEBeZMDlEgq4ayvsiblPcS1qoB O/0JCG9+Tt8d47ov53XMvMeCnl0SNBMkncIQb+8aGdr9mmLUxDfAKV25Tf4VKE1UmTLs yQ/26ZfTiEtYxzJthsMFaOplzJzwjYlG436dk=
Received: by 10.224.137.147 with SMTP id w19mr139963qat.207.1310439513700; Mon, 11 Jul 2011 19:58:33 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id e18sm10752227qcs.5.2011.07.11.19.58.31 (version=SSLv3 cipher=OTHER); Mon, 11 Jul 2011 19:58:33 -0700 (PDT)
Message-ID: <4E1BB856.7040601@gmail.com>
Date: Tue, 12 Jul 2011 14:58:30 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Repetitions and consensus
Content-Type: text/plain; charset=UTF-8
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, 12 Jul 2011 02:58:35 -0000

Hi,

We quite often discuss here how to judge rough consensus. In a completely=
 non-IETF
context, I came upon a reference to an article published in 2007 with the=
 catchy title
"Inferring the Popularity of an Opinion From Its Familiarity: A Repetitiv=
e Voice Can
Sound Like a Chorus". Here's an extract from the abstract:

"...people do not always correctly estimate the distribution of opinions
within their group. One important mechanism underlying such misjudgments
is people=E2=80=99s tendency to infer that a familiar opinion is a preval=
ent one,
even when its familiarity derives solely from the repeated expression
of 1 group member. Six experiments demonstrate this effect and show that
it holds even when perceivers are consciously aware that the opinions com=
e
from 1 speaker."

The article by Weaver et al was in the Journal of Personality and Social
Psychology, 2007, Vol. 92, No. 5, 821=E2=80=93833. I found it at
http://www.apa.org/pubs/journals/releases/psp-925821.pdf

--=20
Regards
   Brian Carpenter




From evnikita2@gmail.com  Mon Jul 11 21:40:11 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 1628C21F8F42; Mon, 11 Jul 2011 21:40:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.493
X-Spam-Level: 
X-Spam-Status: No, score=-3.493 tagged_above=-999 required=5 tests=[AWL=0.106,  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 RXN8qlz6ib01; Mon, 11 Jul 2011 21:40:10 -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 B984721F8F3C; Mon, 11 Jul 2011 21:40:09 -0700 (PDT)
Received: by fxe4 with SMTP id 4so5757106fxe.27 for <multiple recipients>; Mon, 11 Jul 2011 21:40:08 -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=+1Eih9ROKdXmiPP4U7A1oEHgSHH9POku0zrYcidWreQ=; b=wOf2y+ruSoLU+5eg1m48o+W/uaaRnHIaxNI24TsqP0AKWz2BtuAnvXgozms6BY2U+h Z3zh7TMDZ1uk9Bt3fxUh3qaCUYlVnybchUTZEcXzlMnOHw1RjWo813LMSWMNUztZ2U2F yc8K85Xf6J0V209OaAxr+aUtKRftJGArTJDHk=
Received: by 10.223.7.66 with SMTP id c2mr8746584fac.35.1310445608634; Mon, 11 Jul 2011 21:40:08 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id n27sm9663985faa.4.2011.07.11.21.40.06 (version=SSLv3 cipher=OTHER); Mon, 11 Jul 2011 21:40:07 -0700 (PDT)
Message-ID: <4E1BD054.7010103@gmail.com>
Date: Tue, 12 Jul 2011 07:40:52 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com>
In-Reply-To: <20110711140229.17432.23519.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: hybi@ietf.org, draft-ietf-hybi-thewebsocketprotocol@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2011 04:40:11 -0000

Hello,

I'd like to comment the draft-ietf-hybi-thewebsocketprotocol-10, which 
is currently in IETF Last Call.

Throughout the document:

>     _This section is non-normative._

are quite unusual.  Such statements occur at the beginning of 
Introduction, which is meant to be nob-normative a priori, its 
subsections, and Section 4.7, Examples.  These sections, IMO, doesn't 
need to be additionally marked as non-normative.

Section 2.1 makes use of a bit unusual notation; explicitly, it often 
excludes possibility to reference ABNF productions in angle brackets in 
the text.  I don't object to the existing notation (but see below), but 
ABNF rules should be referenced in other way.

Section 3.  I propose to rewrite the first paragraph as follows:

>     This specification defines two URI schemes for WebSocket protocol -
>     'ws' and 'wss'.  Their syntax is defined below using ABNF [RFC5234]
>     in the<ws-uri>  and<wss-uri>, respectively:
>
>       ws-uri  = "ws:" "//" host [ ":" port ] path-abempty [ "?" query ]
>       wss-uri = "wss:" "//" host [ ":" port ] path-abempty [ "?" query ]
>
>     where the<host>,<port>,<path-abempty>  and<query>  rules are
>     defined in RFC 3986 [RFC3986].

Rationale: (1) The first paragraph gets clearer. (2) ABNF is changed not 
ot use pros-vals (RFC 5234) (3) s/path/path-abempty/ to directly import 
it from RFC 3986 (4) Several editorial issues fixed.

I see a number of times the term "WebSocket URI" is used in the draft.  
I would be useful to clarify that the "WebSocket URI" is either a valid 
'ws' or 'wss' URI.

Section 4.2.  I have a concern with usage of ABNF here.  Let's see:

>     frame-fin               = %x0 ; more frames of this message follow
>                             / %x1 ; final frame of this message

Looking at RFC 5234, Section 2.3 we find:

>     Rules resolve into a string of terminal values, sometimes called
>     characters.

Which means that ABNF represents characters only; no bits may be 
represented by it.  Creating the normative and formal definition of a 
header is just impossible.  The above rule will be correctly interpreted as:

>     frame-fin               =<ASCII NUL character 0x00>
>                             /<ASCII SOH character 0x01>

which isn't what you mean.  Changing "x" to "d" to represent binary 
values won't help, since all other bits will be considered to be zeros 
and the result will be the same.  Conclusion: there is no other way 
other that to remove the ABNF definition of WS message here.

Sections 4.5.2. and 4.5.3.  I think the names "ping" and "pong" can 
better be replaced with "echo request" and "echo response".

Section 5.2.2, bullet 3, sub-bullet 4.  When defining the ABNF for a 
header, the header name should be included in it as well.  So the first 
line should be:

> sec-websocket-accept-header = "Sec-WebSocket-Accept:" base64-value

This will also deal with the issue regarding the name of ABNF production 
for the header.

Section 9.1:

>           extension-token = registered-token / private-use-token

If you want RFC 2616 ABNF, this should be changed to:

>           extension-token = registered-token | private-use-token

Ibid:

>           Sec-WebSocket-Extensions: bar; baz=2
>
>     is exactly equivalent to
>
>           Sec-WebSocket-Extensions: foo, bar; baz=2

These two examples don't match the aforementioned ABNF; the space before 
"baz=2" should be removed.

Section 11.1:

> 11.1.  Registration of "ws:" Scheme

The ":" colon isn't included in the scheme name.  So replacing "ws:" 
with 'ws' should be OK.

>     A |ws:| URI identifies a WebSocket server and resource name.

In Section 2.1 you mentioned that |foo| is used when "foo" is a header.  
Please use simple quotes.

>        In ABNF terms using the terminals from the URI specifications:
>        [RFC5234] [RFC3986]
>
>             "ws" ":" hier-part [ "?" query ]

This isn't what you described in Section 3. <hier-part> includes the 
<userinfo> part, which shouldn't be present in WebSocket URIs.  This 
ABNF should be fixed to match one in Section 3.

>        The<path>  [RFC3986] and<query>  components form the resource name
>        sent to the server to identify the kind of service desired.  Other
>        components have the meanings described in RFC3986.

If you adopt my proposal to Section 3, this should be fixed in the same way.

>     References.
>        RFC XXXX

References here mean (from RFC 4395):

>     References.
>        Include full citations for all referenced documents.  Registration
>        templates for provisional registration may be included in an
>        Internet Draft; when the documents expire or are approved for
>        publication as an RFC, the registration will be updated.

So this field should refer to Section 14 of the draft.

Section 11.2: the same applies.

Section 11.12:

>        Version Number  | Reference
>      -+----------------+-----------------------------------------+-
>       | 0              + draft-ietf-hybi-thewebsocketprotocol-00 |
>      -+----------------+-----------------------------------------+-
>         [ . . . ]
>      -+----------------+-----------------------------------------+-
>       | 9              + draft-ietf-hybi-thewebsocketprotocol-09 |
>      -+----------------+-----------------------------------------+-

This looks very strange, since all revisions of the draft will become a 
single RFC.  I propose:

>        Version Number  | Reference
>      -+----------------+-----------------------------------------+-
>       | 1              + This document                           |
>      -+----------------+-----------------------------------------+-

Moreover, what is the allowed range of version numbers (and all other 
values for which the registries are created)?  What entries are 
Unassigned and what are Reserved (I suppose 0 might be Reserved, others 
- Unassigned).

I find the only 2 definitions of syntax of header field described in 
your document - Sec-WebSocket-Accept and Sec-WebSocket-Extensions.  
Where are the other syntax definitions for those header fields 
registered in Section 11?

References.  RFC 3490 is a downward reference here; RFC 3967 procedure 
should have been used.  All other of them seem OK.

I hope my comments were useful.

Thanks,
Mykyta Yevstifeyev

11.07.2011 17:02, The IESG wrote:
> The IESG has received a request from the BiDirectional or
> Server-Initiated HTTP WG (hybi) to consider the following document:
> - 'The WebSocket protocol'
>    <draft-ietf-hybi-thewebsocketprotocol-10.txt>  as a Proposed Standard

From turchanyi.geza@gmail.com  Mon Jul 11 23:36:33 2011
Return-Path: <turchanyi.geza@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9D1121F9149 for <ietf@ietfa.amsl.com>; Mon, 11 Jul 2011 23:36:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.954
X-Spam-Level: 
X-Spam-Status: No, score=-2.954 tagged_above=-999 required=5 tests=[AWL=0.489,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aPBZeq1q034F for <ietf@ietfa.amsl.com>; Mon, 11 Jul 2011 23:36:32 -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 BBB9121F9144 for <ietf@ietf.org>; Mon, 11 Jul 2011 23:36:32 -0700 (PDT)
Received: by vxi40 with SMTP id 40so4796631vxi.31 for <ietf@ietf.org>; Mon, 11 Jul 2011 23:36:32 -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=JHG/uwrw1Cz9aQsLeOhdKMrcNnqLwEPs1QJRUYFqt/I=; b=g0552teNTVdLxgP8yDpwv2+IHmyYUZTrboDGkGSZcvpr0bDSH/zCVQ7oODivp2pWmP gQdIC1rxVZ0kvh9Q9wVm2RSpSPbcIOCrouoNmDnVapuDVIbQHoeNXwj5HG73FHNUxwwU 0+j/rzajmPvIjbA4W3h5fQqEeKRDF3UJKk7J4=
MIME-Version: 1.0
Received: by 10.52.115.105 with SMTP id jn9mr3466450vdb.495.1310452590226; Mon, 11 Jul 2011 23:36:30 -0700 (PDT)
Received: by 10.52.113.35 with HTTP; Mon, 11 Jul 2011 23:36:30 -0700 (PDT)
In-Reply-To: <4E1BB856.7040601@gmail.com>
References: <4E1BB856.7040601@gmail.com>
Date: Tue, 12 Jul 2011 08:36:30 +0200
Message-ID: <CAJfR-+OzKx3ZsWR5t4+xJ2TZrLmhGDemwsibLpQGanLc+Sdkww@mail.gmail.com>
Subject: Re: Repetitions and consensus
From: Turchanyi Geza <turchanyi.geza@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec548aa3922abfb04a7d98544
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: Tue, 12 Jul 2011 06:36:33 -0000

--bcaec548aa3922abfb04a7d98544
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Brian,

I repeat, you are right.

Your statement might receive even full consensus ;-)

Regards,

G=E9za



On Tue, Jul 12, 2011 at 4:58 AM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> Hi,
>
> We quite often discuss here how to judge rough consensus. In a completely
> non-IETF
> context, I came upon a reference to an article published in 2007 with the
> catchy title
> "Inferring the Popularity of an Opinion From Its Familiarity: A Repetitiv=
e
> Voice Can
> Sound Like a Chorus". Here's an extract from the abstract:
>
> "...people do not always correctly estimate the distribution of opinions
> within their group. One important mechanism underlying such misjudgments
> is people=92s tendency to infer that a familiar opinion is a prevalent on=
e,
> even when its familiarity derives solely from the repeated expression
> of 1 group member. Six experiments demonstrate this effect and show that
> it holds even when perceivers are consciously aware that the opinions com=
e
> from 1 speaker."
>
> The article by Weaver et al was in the Journal of Personality and Social
> Psychology, 2007, Vol. 92, No. 5, 821=96833. I found it at
> http://www.apa.org/pubs/journals/releases/psp-925821.pdf
>
> --
> Regards
>   Brian Carpenter
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

--bcaec548aa3922abfb04a7d98544
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Brian,<br><br>I repeat, you are right.<br><br>Your statement might receive =
even full consensus ;-)<br><br>Regards,<br><br>G=E9za<br><br><br><br><div c=
lass=3D"gmail_quote">On Tue, Jul 12, 2011 at 4:58 AM, Brian E Carpenter <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.c=
arpenter@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Hi,<br>
<br>
We quite often discuss here how to judge rough consensus. In a completely n=
on-IETF<br>
context, I came upon a reference to an article published in 2007 with the c=
atchy title<br>
&quot;Inferring the Popularity of an Opinion From Its Familiarity: A Repeti=
tive Voice Can<br>
Sound Like a Chorus&quot;. Here&#39;s an extract from the abstract:<br>
<br>
&quot;...people do not always correctly estimate the distribution of opinio=
ns<br>
within their group. One important mechanism underlying such misjudgments<br=
>
is people=92s tendency to infer that a familiar opinion is a prevalent one,=
<br>
even when its familiarity derives solely from the repeated expression<br>
of 1 group member. Six experiments demonstrate this effect and show that<br=
>
it holds even when perceivers are consciously aware that the opinions come<=
br>
from 1 speaker.&quot;<br>
<br>
The article by Weaver et al was in the Journal of Personality and Social<br=
>
Psychology, 2007, Vol. 92, No. 5, 821=96833. I found it at<br>
<a href=3D"http://www.apa.org/pubs/journals/releases/psp-925821.pdf" target=
=3D"_blank">http://www.apa.org/pubs/journals/releases/psp-925821.pdf</a><br=
>
<br>
--<br>
Regards<br>
 =A0 Brian Carpenter<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>

--bcaec548aa3922abfb04a7d98544--

From julian.reschke@gmx.de  Mon Jul 11 23:56:52 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 8C09521F8E90 for <ietf@ietfa.amsl.com>; Mon, 11 Jul 2011 23:56:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.495
X-Spam-Level: 
X-Spam-Status: No, score=-104.495 tagged_above=-999 required=5 tests=[AWL=-1.896, 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 pkjQaZQ5esHm for <ietf@ietfa.amsl.com>; Mon, 11 Jul 2011 23:56:51 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 045A421F8DD0 for <ietf@ietf.org>; Mon, 11 Jul 2011 23:56:48 -0700 (PDT)
Received: (qmail invoked by alias); 12 Jul 2011 06:56:45 -0000
Received: from p508FD648.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.214.72] by mail.gmx.net (mp022) with SMTP; 12 Jul 2011 08:56:45 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18fGxlOsAMfK8kcFthymxgcvVVz9y3zaCWgUlksOG aUN3c5Jqkq7+Iu
Message-ID: <4E1BF026.6090908@gmx.de>
Date: Tue, 12 Jul 2011 08:56:38 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The	WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com>
In-Reply-To: <20110711140229.17432.23519.idtracker@ietfa.amsl.com>
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: Tue, 12 Jul 2011 06:56:52 -0000

On 2011-07-11 16:02, The IESG wrote:
> ..

I believe Section 11 (IANA Considerations) should be grouped to into URI 
scheme registrations, HTTP header field registrations, and new registries.

Best regards, Julian

From julian.reschke@gmx.de  Mon Jul 11 23:59:53 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 8A39121F9162 for <ietf@ietfa.amsl.com>; Mon, 11 Jul 2011 23:59:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.422
X-Spam-Level: 
X-Spam-Status: No, score=-104.422 tagged_above=-999 required=5 tests=[AWL=-1.823, 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 48zCRPeVR-aM for <ietf@ietfa.amsl.com>; Mon, 11 Jul 2011 23:59: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 8046821F9161 for <ietf@ietf.org>; Mon, 11 Jul 2011 23:59:52 -0700 (PDT)
Received: (qmail invoked by alias); 12 Jul 2011 06:59:46 -0000
Received: from p508FD648.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.214.72] by mail.gmx.net (mp007) with SMTP; 12 Jul 2011 08:59:46 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18F9GxhqW8FBGM+958RZE27y0PuirBeCVNv0s03Hl mcghBhIN9/bezN
Message-ID: <4E1BF0D6.4090702@gmx.de>
Date: Tue, 12 Jul 2011 08:59:34 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <4E1BD054.7010103@gmail.com>
In-Reply-To: <4E1BD054.7010103@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: hybi@ietf.org, ietf@ietf.org, draft-ietf-hybi-thewebsocketprotocol@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2011 06:59:53 -0000

On 2011-07-12 06:40, Mykyta Yevstifeyev wrote:
> ...
> Throughout the document:
>
>> _This section is non-normative._
>
> are quite unusual. Such statements occur at the beginning of
> Introduction, which is meant to be nob-normative a priori, its
> subsections, and Section 4.7, Examples. These sections, IMO, doesn't
> need to be additionally marked as non-normative.
> ...

+1

> Section 3. I propose to rewrite the first paragraph as follows:
>
>> This specification defines two URI schemes for WebSocket protocol -
>> 'ws' and 'wss'. Their syntax is defined below using ABNF [RFC5234]
>> in the<ws-uri> and<wss-uri>, respectively:
>>
>> ws-uri = "ws:" "//" host [ ":" port ] path-abempty [ "?" query ]
>> wss-uri = "wss:" "//" host [ ":" port ] path-abempty [ "?" query ]
>>
>> where the<host>,<port>,<path-abempty> and<query> rules are
>> defined in RFC 3986 [RFC3986].
>
> Rationale: (1) The first paragraph gets clearer. (2) ABNF is changed not
> ot use pros-vals (RFC 5234) (3) s/path/path-abempty/ to directly import
> it from RFC 3986 (4) Several editorial issues fixed.

-10

Granted, it doesn't use prose values anymore, but then it get's 
incomplete. I believe putting references to ABNF productions from other 
specs into prose values is absolutely the right thing to do (as opposed 
to just mention them in prose).

> Section 5.2.2, bullet 3, sub-bullet 4. When defining the ABNF for a
> header, the header name should be included in it as well. So the first
> line should be:
> ...

Why?

> Section 9.1:
>
>> extension-token = registered-token / private-use-token
>
> If you want RFC 2616 ABNF, this should be changed to:
> ...

yes.

>> extension-token = registered-token | private-use-token
>
> Ibid:
>
>> Sec-WebSocket-Extensions: bar; baz=2
>>
>> is exactly equivalent to
>>
>> Sec-WebSocket-Extensions: foo, bar; baz=2
>
> These two examples don't match the aforementioned ABNF; the space before
> "baz=2" should be removed.
 > ...

They do, as the RFC 2616 ABNF allows implied Linear Whitespace.

That being said, it might be a good idea to revisit the choice of 
syntax, or at least to clarify the LWS situation.

>> In ABNF terms using the terminals from the URI specifications:
>> [RFC5234] [RFC3986]
>>
>> "ws" ":" hier-part [ "?" query ]
>
> This isn't what you described in Section 3. <hier-part> includes the
> <userinfo> part, which shouldn't be present in WebSocket URIs. This ABNF
> should be fixed to match one in Section 3.

...or removed. Why are there two?

>> The<path> [RFC3986] and<query> components form the resource name
>> sent to the server to identify the kind of service desired. Other
>> components have the meanings described in RFC3986.
>
> If you adopt my proposal to Section 3, this should be fixed in the same
> way.
>
>> References.
>> RFC XXXX
>
> References here mean (from RFC 4395):
>
>> References.
>> Include full citations for all referenced documents. Registration
>> templates for provisional registration may be included in an
>> Internet Draft; when the documents expire or are approved for
>> publication as an RFC, the registration will be updated.
>
> So this field should refer to Section 14 of the draft.

"Section 14 of this document".

> Section 11.2: the same applies.
>
> Section 11.12:
>
>> Version Number | Reference
>> -+----------------+-----------------------------------------+-
>> | 0 + draft-ietf-hybi-thewebsocketprotocol-00 |
>> -+----------------+-----------------------------------------+-
>> [ . . . ]
>> -+----------------+-----------------------------------------+-
>> | 9 + draft-ietf-hybi-thewebsocketprotocol-09 |
>> -+----------------+-----------------------------------------+-
> ...


This is indeed fishy and I would be really surprised if IESG and RFC 
Editor let this pass.

If 0..9 can't be reassigned then let's just state they are reserved.

> ...

Best regards, Julian

From julian.reschke@gmx.de  Tue Jul 12 01:12:53 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 412C221F904A for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 01:12:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.157
X-Spam-Level: 
X-Spam-Status: No, score=-104.157 tagged_above=-999 required=5 tests=[AWL=-1.858, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iYXD6h3bXPak for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 01:12:52 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id EA10221F8696 for <ietf@ietf.org>; Tue, 12 Jul 2011 01:12:51 -0700 (PDT)
Received: (qmail invoked by alias); 12 Jul 2011 08:12:48 -0000
Received: from p508FD648.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.214.72] by mail.gmx.net (mp012) with SMTP; 12 Jul 2011 10:12:48 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19JMJpo35FJbEcB25sKM4bmiGhw2sMabiVhSVg6ZB uUyl7WaERDAHx3
Message-ID: <4E1C01F3.4070906@gmx.de>
Date: Tue, 12 Jul 2011 10:12:35 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: =?UTF-8?B?ScOxYWtpIEJheiBDYXN0aWxsbw==?= <ibc@aliax.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <4E1BD054.7010103@gmail.com> <CALiegf=JjAYgjQRNh3-5NNvEP-cbAzB4hnuMV2R2WpEo3=1_ew@mail.gmail.com>
In-Reply-To: <CALiegf=JjAYgjQRNh3-5NNvEP-cbAzB4hnuMV2R2WpEo3=1_ew@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: hybi@ietf.org, ietf@ietf.org, draft-ietf-hybi-thewebsocketprotocol@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2011 08:12:53 -0000

On 2011-07-12 09:48, IÃ±aki Baz Castillo wrote:
> 2011/7/12 Mykyta Yevstifeyev<evnikita2@gmail.com>:
>>>           Sec-WebSocket-Extensions: bar; baz=2
>>>
>>>     is exactly equivalent to
>>>
>>>           Sec-WebSocket-Extensions: foo, bar; baz=2
>>
>> These two examples don't match the aforementioned ABNF; the space before
>> "baz=2" should be removed.
>
> Hi, are you sure of that? In SIP protocol (which inherits from HTTP
> grammar) a header parameter (;foo=lalala) can contain spaces anywhere
> (before/after the ";", before/after the "="). So something like:
>
>     Sec-WebSocket-Extensions: foo  , bar  ; baz = 2
>
> is valid.
>
> However it's not clear for me wheter in this example "baz=2" is a
> header param or a param just for the value "bar". In the last case it
> would mean a specific header syntax, so spaces could be not allowed.
> Could you please point to the ABNF grammar you meant?

According to 
<http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-10#section-9.1> 
it's a parameter of "bar".

That being said, I'm not happy with

          extension-param = token [ "=" token ]

In HTTP header fields, parameters usually support both token and 
quoted-string form.

Making this special means that existing header field parser code can't 
be easily re-used.

Best regards, Julian


From julian.reschke@gmx.de  Tue Jul 12 01:51:53 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 DC6D221F8906 for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 01:51:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.097
X-Spam-Level: 
X-Spam-Status: No, score=-104.097 tagged_above=-999 required=5 tests=[AWL=-1.798, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sJ9AQKjf30RY for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 01:51:53 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 44E1E21F8915 for <ietf@ietf.org>; Tue, 12 Jul 2011 01:51:53 -0700 (PDT)
Received: (qmail invoked by alias); 12 Jul 2011 08:51:50 -0000
Received: from p508FD648.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.214.72] by mail.gmx.net (mp066) with SMTP; 12 Jul 2011 10:51:50 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+VdqgrvfGV6qMb+qHZt/++aQUMF9tGeq6BIO0uT6 rWJ6CXC42T/MZR
Message-ID: <4E1C0B1F.1030305@gmx.de>
Date: Tue, 12 Jul 2011 10:51:43 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: =?UTF-8?B?ScOxYWtpIEJheiBDYXN0aWxsbw==?= <ibc@aliax.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <4E1BD054.7010103@gmail.com> <CALiegf=JjAYgjQRNh3-5NNvEP-cbAzB4hnuMV2R2WpEo3=1_ew@mail.gmail.com> <4E1C01F3.4070906@gmx.de> <CALiegfmKK+Rka+eqU8=3zFVkL12wSh_w+VjoDxOYurgrmob_+A@mail.gmail.com>
In-Reply-To: <CALiegfmKK+Rka+eqU8=3zFVkL12wSh_w+VjoDxOYurgrmob_+A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: hybi@ietf.org, ietf@ietf.org, draft-ietf-hybi-thewebsocketprotocol@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2011 08:51:54 -0000

On 2011-07-12 10:23, IÃ±aki Baz Castillo wrote:
> 2011/7/12 Julian Reschke<julian.reschke@gmx.de>:
>> That being said, I'm not happy with
>>
>>          extension-param = token [ "=" token ]
>>
>> In HTTP header fields, parameters usually support both token and
>> quoted-string form.
>
> Right.
>
>
>> Making this special means that existing header field parser code can't be
>> easily re-used.
>
> Well, not exaclty as any parser supporting tokens and quoted-strings
> would also parse "just" tokens :)

But if they *are* re-used, those recipients will accept quoted-strings 
as well (thus accepting invalid header fields). This could be harmless, 
or it could cause them to be used in practice, forcing other recipients 
to accept them as well.

> ...

Best regards, Julian

From evnikita2@gmail.com  Tue Jul 12 01:59: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 A256F21F911F for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 01:59:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.497
X-Spam-Level: 
X-Spam-Status: No, score=-3.497 tagged_above=-999 required=5 tests=[AWL=0.102,  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 ln9nLEPNKVcK for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 01:59:13 -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 EF09F21F90F3 for <ietf@ietf.org>; Tue, 12 Jul 2011 01:59:12 -0700 (PDT)
Received: by bwb17 with SMTP id 17so4526687bwb.31 for <ietf@ietf.org>; Tue, 12 Jul 2011 01:59:12 -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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=6CVMsD4tE3L8Cyr/iZ3uojaS2+PAFy0mBhYmNHcV5vE=; b=jQ5t/zwxt7iHfpylAGu3JnuZiEQtq1O0X+jmddc49apdOQktWiiQDrjGnmTKh8Ak5K O2JywjgKfCHtCkEeLzoS2YCu4Vhb3qoWxUPg48qqJU45ncEjN35KobhE8W+F9o9An+px NI0HL1cIn66UCrW+veIvgERg0P/0pL/vGYemQ=
Received: by 10.204.10.67 with SMTP id o3mr3018105bko.161.1310461152019; Tue, 12 Jul 2011 01:59:12 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id n5sm780088bkw.11.2011.07.12.01.59.10 (version=SSLv3 cipher=OTHER); Tue, 12 Jul 2011 01:59:11 -0700 (PDT)
Message-ID: <4E1C0D0C.9040802@gmail.com>
Date: Tue, 12 Jul 2011 11:59:56 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The	WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <4E1BF026.6090908@gmx.de>
In-Reply-To: <4E1BF026.6090908@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2011 08:59:13 -0000

12.07.2011 9:56, Julian Reschke wrote:
> On 2011-07-11 16:02, The IESG wrote:
>> ..
>
> I believe Section 11 (IANA Considerations) should be grouped to into 
> URI scheme registrations, HTTP header field registrations, and new 
> registries.
This is quite reasonable. +1.

Mykyta
>
> Best regards, Julian
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


From evnikita2@gmail.com  Tue Jul 12 02:09: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 CFED921F8FDB; Tue, 12 Jul 2011 02:09:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.499
X-Spam-Level: 
X-Spam-Status: No, score=-3.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sHC-EwR-3u+J; Tue, 12 Jul 2011 02:09:13 -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 A66EA21F8F90; Tue, 12 Jul 2011 02:09:12 -0700 (PDT)
Received: by bwb17 with SMTP id 17so4535151bwb.31 for <multiple recipients>; Tue, 12 Jul 2011 02:09:11 -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=C+lwESc0dmfbKS4TBD/fjZ1fyx464NK2YubP1AD1lkU=; b=dcL8ENHRYaX49yHmQWHoS8BY+tGdnOT0K+tSZiqEPzcJRBgZyHg/3e6+xJi6sulqNa r/X/60DKrOiinQ9CC1F5ZeUqbBA5mPP4Wl+qorR94j0WZZ/c3k+gy/CpvRfQf3WrV0nU Yy57PYjUi+174mojXVwoDKZDH38kcUg4TMZdQ=
Received: by 10.204.14.212 with SMTP id h20mr3012907bka.132.1310461751524; Tue, 12 Jul 2011 02:09:11 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id n5sm783461bkw.11.2011.07.12.02.09.09 (version=SSLv3 cipher=OTHER); Tue, 12 Jul 2011 02:09:10 -0700 (PDT)
Message-ID: <4E1C0F63.8060206@gmail.com>
Date: Tue, 12 Jul 2011 12:09:55 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <4E1BD054.7010103@gmail.com> <4E1BF0D6.4090702@gmx.de>
In-Reply-To: <4E1BF0D6.4090702@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: hybi@ietf.org, ietf@ietf.org, draft-ietf-hybi-thewebsocketprotocol@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2011 09:09:13 -0000

12.07.2011 9:59, Julian Reschke wrote:
> On 2011-07-12 06:40, Mykyta Yevstifeyev wrote:
>
> [ . . . ]
>
>> Section 3. I propose to rewrite the first paragraph as follows:
>>
>>> This specification defines two URI schemes for WebSocket protocol -
>>> 'ws' and 'wss'. Their syntax is defined below using ABNF [RFC5234]
>>> in the<ws-uri> and<wss-uri>, respectively:
>>>
>>> ws-uri = "ws:" "//" host [ ":" port ] path-abempty [ "?" query ]
>>> wss-uri = "wss:" "//" host [ ":" port ] path-abempty [ "?" query ]
>>>
>>> where the<host>,<port>,<path-abempty> and<query> rules are
>>> defined in RFC 3986 [RFC3986].
>>
>> Rationale: (1) The first paragraph gets clearer. (2) ABNF is changed not
>> ot use pros-vals (RFC 5234) (3) s/path/path-abempty/ to directly import
>> it from RFC 3986 (4) Several editorial issues fixed.
>
> -10
>
> Granted, it doesn't use prose values anymore, but then it get's 
> incomplete. I believe putting references to ABNF productions from 
> other specs into prose values is absolutely the right thing to do (as 
> opposed to just mention them in prose).
I don't have any string position in the way of importing the productions 
from other documents.  However, what is above is what I like more.  
However, what we can see, eg. in 
http://tools.ietf.org/html/rfc5538#appendix-A can be fine as well.
>
>> Section 5.2.2, bullet 3, sub-bullet 4. When defining the ABNF for a
>> header, the header name should be included in it as well. So the first
>> line should be:
>> ...
>
> Why?
There is the following formulation:

> The 'Foo' headers takes the form of <foo-header> ABNF rules below:
>
> foo-header = *(APHA/DIGIT)

will result in the message headers like:

>          Upgrade: TLS/1.2
>          Connection: Upgrade
>          gfr134

and "gfr134" will be the 'Foo' header.  "foo-header = "Foo:" 
*(APHA/DIGIT)" will result in valid:

>          Upgrade: TLS/1.2
>          Connection: Upgrade
>          Foo: gfr134

See also eg. RFC 3282, RFC 2616.

>
> [ . . . ]
>
> That being said, it might be a good idea to revisit the choice of 
> syntax, or at least to clarify the LWS situation.
The document may reference the httpbis-p1 where the <n>#<m>rule 
extension will be described for valid ABNF.  See 
http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-15#section-1.2.1
>
> [ . . . ]
>> Section 11.2: the same applies.
>>
>> Section 11.12:
>>
>>> Version Number | Reference
>>> -+----------------+-----------------------------------------+-
>>> | 0 + draft-ietf-hybi-thewebsocketprotocol-00 |
>>> -+----------------+-----------------------------------------+-
>>> [ . . . ]
>>> -+----------------+-----------------------------------------+-
>>> | 9 + draft-ietf-hybi-thewebsocketprotocol-09 |
>>> -+----------------+-----------------------------------------+-
>> ...
>
>
> This is indeed fishy and I would be really surprised if IESG and RFC 
> Editor let this pass.
>
> If 0..9 can't be reassigned then let's just state they are reserved.
I believe there is no problems to make the 0..9 spare, except 1, for 
this version of WS.

Mykyta Yevstifeyev
>
>> ...
>
> Best regards, Julian
>


From julian.reschke@gmx.de  Tue Jul 12 02:15:07 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 7249821F901B for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 02:15:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.191
X-Spam-Level: 
X-Spam-Status: No, score=-104.191 tagged_above=-999 required=5 tests=[AWL=-1.592, 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 dH4TC505N+Cd for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 02:15:06 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 4E98A21F901A for <ietf@ietf.org>; Tue, 12 Jul 2011 02:15:06 -0700 (PDT)
Received: (qmail invoked by alias); 12 Jul 2011 09:15:03 -0000
Received: from p508FD648.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.214.72] by mail.gmx.net (mp011) with SMTP; 12 Jul 2011 11:15:03 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/FnrMsosbFFgnkQrWX6DJkgX5QJmO62Bvw/g2AMt b8TegHazSEhAil
Message-ID: <4E1C108E.7010800@gmx.de>
Date: Tue, 12 Jul 2011 11:14:54 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <4E1BD054.7010103@gmail.com> <4E1BF0D6.4090702@gmx.de> <4E1C0F63.8060206@gmail.com>
In-Reply-To: <4E1C0F63.8060206@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: hybi@ietf.org, ietf@ietf.org, draft-ietf-hybi-thewebsocketprotocol@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2011 09:15:07 -0000

On 2011-07-12 11:09, Mykyta Yevstifeyev wrote:
> ...
>>> Section 5.2.2, bullet 3, sub-bullet 4. When defining the ABNF for a
>>> header, the header name should be included in it as well. So the first
>>> line should be:
>>> ...
>>
>> Why?
> There is the following formulation:
>
>> The 'Foo' headers takes the form of <foo-header> ABNF rules below:
>>
>> foo-header = *(APHA/DIGIT)

It should say: "The 'Foo' header field's value takes the form..."

> will result in the message headers like:
>
>> Upgrade: TLS/1.2
>> Connection: Upgrade
>> gfr134
>
> and "gfr134" will be the 'Foo' header. "foo-header = "Foo:"
> *(APHA/DIGIT)" will result in valid:
>
>> Upgrade: TLS/1.2
>> Connection: Upgrade
>> Foo: gfr134
>
> See also eg. RFC 3282, RFC 2616.

Have a look at the HTTPbis drafts.

>
>>
>> [ . . . ]
>>
>> That being said, it might be a good idea to revisit the choice of
>> syntax, or at least to clarify the LWS situation.
> The document may reference the httpbis-p1 where the <n>#<m>rule
> extension will be described for valid ABNF. See
> http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-15#section-1.2.1

It could, but my guess is that HyBi doesn't want to wait for HTTPbis.

> ...

Best regards, Julian

From evnikita2@gmail.com  Tue Jul 12 02:16:02 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 8C26221F90CA; Tue, 12 Jul 2011 02:16:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.351
X-Spam-Level: 
X-Spam-Status: No, score=-3.351 tagged_above=-999 required=5 tests=[AWL=-0.052, 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 O9mhAjsuB1RT; Tue, 12 Jul 2011 02:16:02 -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 D83A221F90B0; Tue, 12 Jul 2011 02:16:00 -0700 (PDT)
Received: by bwb17 with SMTP id 17so4540117bwb.31 for <multiple recipients>; Tue, 12 Jul 2011 02:16:00 -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=i8lpE6kjWU6HpGGSGZr6AXsG0s4kWv0tCVTrhB6ZxaM=; b=KNXwPEjlnU1F7xkt8FON7xuyeoJ8cfttBHYosITz9TI1zVDMycLqcFwRio+brZQGDR 0jdmM7DkM2UeQGLZsqSGWv95ZgkeT3WEbf3iDVEEn71enJx13uCTfHqdgsTRspUay142 nT8bGhmRXr9CE5Jd7+ECA68js6Zh/VP7x+pNE=
Received: by 10.205.65.133 with SMTP id xm5mr2217690bkb.396.1310462159874; Tue, 12 Jul 2011 02:15:59 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id lb15sm1295404bkb.34.2011.07.12.02.15.58 (version=SSLv3 cipher=OTHER); Tue, 12 Jul 2011 02:15:59 -0700 (PDT)
Message-ID: <4E1C10FB.6020404@gmail.com>
Date: Tue, 12 Jul 2011 12:16:43 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: =?UTF-8?B?ScOxYWtpIEJheiBDYXN0aWxsbw==?= <ibc@aliax.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <4E1BD054.7010103@gmail.com> <CALiegf=JjAYgjQRNh3-5NNvEP-cbAzB4hnuMV2R2WpEo3=1_ew@mail.gmail.com>
In-Reply-To: <CALiegf=JjAYgjQRNh3-5NNvEP-cbAzB4hnuMV2R2WpEo3=1_ew@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: hybi@ietf.org, ietf@ietf.org, draft-ietf-hybi-thewebsocketprotocol@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2011 09:16:02 -0000

12.07.2011 10:48, IÃ±aki Baz Castillo wrote:
> 2011/7/12 Mykyta Yevstifeyev<evnikita2@gmail.com>:
>>>           Sec-WebSocket-Extensions: bar; baz=2
>>>
>>>     is exactly equivalent to
>>>
>>>           Sec-WebSocket-Extensions: foo, bar; baz=2
>> These two examples don't match the aforementioned ABNF; the space before
>> "baz=2" should be removed.
> Hi, are you sure of that? In SIP protocol (which inherits from HTTP
> grammar) a header parameter (;foo=lalala) can contain spaces anywhere
> (before/after the ";", before/after the "="). So something like:
>
>     Sec-WebSocket-Extensions: foo  , bar  ; baz = 2
>
> is valid.
No, its' everything OK with this issue.  LWS is allowed between 
<extension> productions in the header, but not between the parts of this 
productions: <extension-token>s and <extension-param>s.  See 
http://tools.ietf.org/html/rfc2616#section-2.1 and 
http://tools.ietf.org/html/rfc2616#section-2.1.

>
> However it's not clear for me wheter in this example "baz=2" is a
> header param or a param just for the value "bar". In the last case it
> would mean a specific header syntax, so spaces could be not allowed.
> Could you please point to the ABNF grammar you meant?
This was meant to be the parameter for the "bar", as far as I understand.

Mykyta
>
> Thanks.
>


From evnikita2@gmail.com  Tue Jul 12 02:20: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 854D021F912D; Tue, 12 Jul 2011 02:20:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.5
X-Spam-Level: 
X-Spam-Status: No, score=-3.5 tagged_above=-999 required=5 tests=[AWL=0.099, 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 2I3CqiKy64jC; Tue, 12 Jul 2011 02:20:51 -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 9E26A21F9110; Tue, 12 Jul 2011 02:20:49 -0700 (PDT)
Received: by bwb17 with SMTP id 17so4543720bwb.31 for <multiple recipients>; Tue, 12 Jul 2011 02:20:48 -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=VdyuQTeOV4DrFUwy+DhXZ8byGYlpidF/d1t6w3vv7es=; b=sDRMGDsrsSI4kTMxPIgqPCRljNIFMxCZHc9Nm7asjc6JHpknZTd7ZO/lccZ06wfTjs BSHitT9f4RZY1M4h08FdBrmcOLu6ELwss2LQamDLbGTUTcFVqGD656ZhetIm84VMRwCB KUkiR5RmQArVbVbp1KGl8fojngmE74lEWrd38=
Received: by 10.204.79.194 with SMTP id q2mr3111775bkk.181.1310462447905; Tue, 12 Jul 2011 02:20:47 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id g13sm10186937bkd.10.2011.07.12.02.20.45 (version=SSLv3 cipher=OTHER); Tue, 12 Jul 2011 02:20:47 -0700 (PDT)
Message-ID: <4E1C121B.2070601@gmail.com>
Date: Tue, 12 Jul 2011 12:21:31 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <4E1BD054.7010103@gmail.com> <4E1BF0D6.4090702@gmx.de> <4E1C0F63.8060206@gmail.com> <4E1C108E.7010800@gmx.de>
In-Reply-To: <4E1C108E.7010800@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: hybi@ietf.org, ietf@ietf.org, draft-ietf-hybi-thewebsocketprotocol@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2011 09:20:51 -0000

12.07.2011 12:14, Julian Reschke wrote:
> On 2011-07-12 11:09, Mykyta Yevstifeyev wrote:
>> ...
>>>> Section 5.2.2, bullet 3, sub-bullet 4. When defining the ABNF for a
>>>> header, the header name should be included in it as well. So the first
>>>> line should be:
>>>> ...
>>>
>>> Why?
>> There is the following formulation:
>>
>>> The 'Foo' headers takes the form of <foo-header> ABNF rules below:
>>>
>>> foo-header = *(APHA/DIGIT)
>
> It should say: "The 'Foo' header field's value takes the form..."
This will eliminate the problem.  Currently we have:

> The ABNF of this header is defined as follows:

not its entity.
>
>> will result in the message headers like:
>>
>>> Upgrade: TLS/1.2
>>> Connection: Upgrade
>>> gfr134
>>
>> and "gfr134" will be the 'Foo' header. "foo-header = "Foo:"
>> *(APHA/DIGIT)" will result in valid:
>>
>>> Upgrade: TLS/1.2
>>> Connection: Upgrade
>>> Foo: gfr134
>>
>> See also eg. RFC 3282, RFC 2616.
>
> Have a look at the HTTPbis drafts.
They should also be clear about whether they mean the header field or 
the header field's entity.
>
>>
>>>
>>> [ . . . ]
>>>
>>> That being said, it might be a good idea to revisit the choice of
>>> syntax, or at least to clarify the LWS situation.
>> The document may reference the httpbis-p1 where the <n>#<m>rule
>> extension will be described for valid ABNF. See
>> http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-15#section-1.2.1 
>>
>
> It could, but my guess is that HyBi doesn't want to wait for HTTPbis.
That's up to them.

Mykyta
>
>> ...
>
> Best regards, Julian
>


From ben@nostrum.com  Mon Jul 11 09:01: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 E4D7D21F8E58 for <ietf@ietfa.amsl.com>; Mon, 11 Jul 2011 09:01:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.204
X-Spam-Level: 
X-Spam-Status: No, score=-101.204 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 TAHKv2903pQw for <ietf@ietfa.amsl.com>; Mon, 11 Jul 2011 09:01:31 -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 CE6E321F8E4F for <ietf@ietf.org>; Mon, 11 Jul 2011 09:01:26 -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 p6BG1O4H054438 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 11 Jul 2011 11:01:25 -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: <AE447DE4-CD85-4386-9C97-2008524D2402@nist.gov>
Date: Mon, 11 Jul 2011 11:01:23 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5BB77043-1674-4FD6-87CB-17DDC1CEEC1C@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> <16FAD31E-CC87-4110-A43F-4DFBD46536A5@nostrum.com> <AE447DE4-CD85-4386-9C97-2008524D2402@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: Tue, 12 Jul 2011 08:06:28 -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, 11 Jul 2011 16:01:33 -0000

Sorry for the late response--I just got back from vacation.

Yes, I was referring to the title and also the last paragraph of section =
1. Your proposed change, along with something similar in section 1, =
would IMHO resolve the issue.

Thanks!

Ben.

On Jun 27, 2011, at 9:15 AM, Scott Rose wrote:

> Ben,
> Are you referring to the title ("Update to the DNAME...")?  Then yes, =
that could be confusing - that was missed in the revision.
>=20
> Would trimming the title to the shorter "DNAME Redirection in the DNS" =
fix that?  It's the simplest fix.
>=20
> Scott
>=20
> On Jun 24, 2011, at 6:18 PM, Ben Campbell wrote:
>=20
>> 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
>=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
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From gregw@intalio.com  Mon Jul 11 19:09:01 2011
Return-Path: <gregw@intalio.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8342421F8FFC for <ietf@ietfa.amsl.com>; Mon, 11 Jul 2011 19:09:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.656
X-Spam-Level: 
X-Spam-Status: No, score=-2.656 tagged_above=-999 required=5 tests=[AWL=0.321,  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 0gRA+kmtv79q for <ietf@ietfa.amsl.com>; Mon, 11 Jul 2011 19:09:00 -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 88D6A21F8FFA for <ietf@ietf.org>; Mon, 11 Jul 2011 19:09:00 -0700 (PDT)
Received: by vxi40 with SMTP id 40so4645805vxi.31 for <ietf@ietf.org>; Mon, 11 Jul 2011 19:09:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.170.205 with SMTP id ao13mr2952879vdc.509.1310436539824; Mon, 11 Jul 2011 19:08:59 -0700 (PDT)
Received: by 10.52.115.103 with HTTP; Mon, 11 Jul 2011 19:08:59 -0700 (PDT)
Date: Tue, 12 Jul 2011 12:08:59 +1000
Message-ID: <CAH_y2NF0hH+bBQ6Nkr5HueP45DG-xOKAJ+aWa_c4fcCibbQA-g@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: Greg Wilkins <gregw@intalio.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Tue, 12 Jul 2011 08:06:28 -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, 12 Jul 2011 02:09:01 -0000

For the benefit of the wider ietf@ietf.org audience, I'd like to
summaries an unresolved issue from the Hybi WG with the websocket
draft protocol.

Draft 10 if this document contains the "deflate-stream" extension in
section 9.2.1

This extension does not comply with any of the anticipated uses of
extensions listed in section 4.8, at best this makes it a poor
exemplar of an extension, as worst it makes it an unexpected total
change to the framing seen on the wire.

Because the extension changes the framing of bytes on the wire, this
will force all tools and intermediaries that wish to observe the frame
boundaries, to implement this extension, making it non optional.  For
example, intermediaries that do not implement this extension will be
unable to buffer/forward on frame boundaries.

Because default-stream is applied after the masking of client sent
frames, it is highly inefficient, with little or no compression being
achieved due to the random masking keys and the masking of any regular
patterns in the payload.

The intent of masking was to prevent bytes sent on the wire being
being controlled by an attacker.  However, a security concern has been
raised that the predictability of the deflate algorithm to convert
byte patterns into shorter bit sequences may allow a payload to be
crafted that would predictably produce bytes on the wire regardless of
the masking applied.

A reasonable alternative has been proposed that does not apply
deflation to the stream. Rather it applies it only to the application
data before masking, while keeping the compression dictionary between
frames.   This alternative proposal is a good exemplar extension (in
line with 4.8), provides efficient compression and does not suffer
from the security concern raised.

Since draft -7, there have been many voices in the WG calling for the
withdrawal of deflate-stream and nobody has spoken in favour of the
retention of deflate-stream on any grounds other than it is already
implemented/deployed.

I fail to understand why a non essential feature that was put into
draft-3 without  discussion or consensus, that has demonstrable
deficiencies, security concerns and vocal opponents has been left in
the draft all the way to final call?


regards

Greg Wilkins

From wwwrun@ietfa.amsl.com  Mon Jul 11 20:20:36 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 2D6E211E8238; Mon, 11 Jul 2011 20:20:36 -0700 (PDT)
From: NomCom Chair <nomcom-chair@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: Nomcom 2011-2012: Final List of Volunteers 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110712032036.2D6E211E8238@ietfa.amsl.com>
Date: Mon, 11 Jul 2011 20:20:36 -0700 (PDT)
X-Mailman-Approved-At: Tue, 12 Jul 2011 08:06:28 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2011 03:20:36 -0000

I would like to thank everyone who volunteered to serve on this year's
Nominating Committee. As specified in my earlier timeline
announcement, the solicitation for volunteers is now closed. All
volunteers have been checked by the secretariat to verify their
eligibility to serve, and I have notified them of the same.

Below is the list of 120 people who have volunteered and are eligible
to serve. If your name is not on the list and you think it should be
or if it is and it shouldn't be, please contact me as soon as
possible.

Any challenges as to the eligibility of these people to serve on the
Nomcom should be received by 23:59 EDT on Thursday, July 14th 2011. If
there are no challenges, the process will proceed with this list.
Assuming any raised challenges have been resolved, the resulting list
will then be published before any of the random seeds (as previously
published) have selected their numbers. If there are unresolved
issues, then a notice will be sent, and new seeds announced, before
the seeds have selected values.

     1	Jaap Akkerhuis, NLnet labs
     2	Alia Atlas, Juniper Networks
     3	Ignas Bagdonas, Cisco Systems
     4	Gabor Bajko, Nokia
     5	Fred Baker, Cisco Systems
     6	Richard Barnes, BBN Technologies
     7	Ray Bellis, Nominet UK
     8	Lou Berger, LabN Consulting
     9	Deborah Brungard, AT&T
    10	Randy Bush, Internet Initiative Japan
    11	Zhen Cao, China Mobile
    12	Samita Chakrabarti, Ericsson
    13	Gang Chen, China Mobile
    14	Mach Chen, Huawei Technologies Co.
    15	Subir Das, Telcordia Technologies Inc
    16	Wojciech Dec, Cisco
    17	Hui Deng, China Mobile
    18	Thomas D. Nadeau, CA Technologies
    19	Jie Dong, Huawei Technologies
    20	Lilla Dovner, Ericsson
    21	Keith Drage, Alcatel-Lucent
    22	Donald Eastlake, Huawei
    23	Toerless Eckert, Cisco Systems
    24	John E Drake, Juniper Networks
    25	Byron Ellacott, APNIC
    26	Mehmet Ersue, Nokia Siemens Networks
    27	Hannu Flinck, NSN
    28	Wesley George, Time Warner Cable
    29	Fernando Gont, UTN/FRH
    30	Eric Gray, Ericsson
    31	Chris Griffiths, Comcast
    32	Yingjie Gu, Huawei Technologies
    33	Wassim Haddad, Ericsson
    34	Michael Hamilton, BreakingPoint Systems
    35	Stephen Hanna, Juniper Networks
    36	Tony Hansen, AT&T
    37	Sam Hartman, Painless Security
    38	Jia He, Huawei Technologies Co.
    39	Thomas Herbst, Silver Spring Networks
    40	Christer Holmberg, LM Ericsson
    41	Fangwei Hu, ZTE Corporation
    42	John Jason Brzozowski, Comcast
    43	Cullen Jennings, Cisco
    44	Sheng Jiang, Huawei Technologies Co. Ltd.
    45	Benno J. Overeinder, NLnet Labs
    46	Hadriel Kaplan, Acme Packet
    47	Stephen Kent, BBN Technologies
    48	Ari Keranen, Ericsson
    49	Sohel Khan, Comcast
    50	Bhumip Khasnabish, ZTE USA
    51	Krisztian Kiss, Nokia
    52	Peter Koch, DENIC eG
    53	Jouni Korhonen, Nokia Siemens Networks
    54	Mirja Kühlewind, University of Stuttgart
    55	Matt Lepinski, BBN Technologies
    56	Marco Liebsch, NEC
    57	Hongyu Li, Huawei Technologies
    58	Dapeng Liu, China Mobile
    59	Guoman liu, ZTE
    60	Yiu L. Lee, Comcast
    61	Andrew Malis, Verizon
    62	Terry Manderson, ICANN
    63	Scott Mansfield, Ericsson
    64	Luca Martini, Cisco
    65	Andrew McLachlan, Cisco
    66	David Meyer, Cisco Systems/University of Oregon
    67	George Michaelson, APNIC
    68	Karen O'Donoghue, Internet Society
    69	Börje Ohlman, Ericsson
    70	Dimitri Papadimitriou, Alcatel-Lucent
    71	Keyur Patel, Cisco Systems
    72	Simon Pietro Romano, Meetecho/University of Napoli
    73	Leon Portman, NICE Systems
    74	Robert Raszuk, Cisco
    75	Adam Roach, Tekelec
    76	Allyn Romanow, Cisco Systems
    77	Joseph Salowey, Cisco Systems
    78	Behcet Sarikaya, Huawei USA
    79	Teemu Savolainen, Nokia
    80	Christian Schmidt, Nokia Siemens Networks
    81	Shida Schubert, NTT
    82	John Scudder, Juniper Networks
    83	Karen Seo, BBN Technologies
    84	Rifaat Shekh-Yusef, Avaya
    85	Sean Shen, CNNIC
    86	Jonne Soininen, Renesas Mobile
    87	Haibin Song, Huawei Technologies
    88	Ning So, Verizon Inc./University of Texas at Dallas
    89	Nurit Sprecher, Nokia Siemens Networks
    90	Ond&#345;ej Surý, CZ.NIC
    91	George Swallow, Cisco Systems
    92	Pascal Thubert, Cisco
    93	Mark Townsley, Cisco Systems
    94	Brian Trammell, ETH Zürich
    95	Ole Troan, Cisco
    96	Tina Tsou, FutureWei Technologies
    97	Javier Ubillos, Swedish Institute of Computer Science
    98	Gunter Van de Velde, Cisco
    99	Olivier Vautrin, Juniper Networks
   100	Simo Veikkolainen, Nokia
   101	Stig Venaas, Cisco
   102	Bill VerSteeg, Cisco
   103	Samuel Weiler, Cobham
   104	Jason Weil, Time Warner Cable
   105	Yaacov Weingarten, Nokia Siemens Networks
   106	Stephan Wenger, Bidyo
   107	Magnus Westerlund, Ericsson
   108	IJsbrand Wijnands, Cisco
   109	Qin Wu, Huawei
   110	Lin Xiao, Nokia Siemens Networks
   111	Xiaohu Xu, Huawei Technologies co.
   112	Jiankang Yao, CNNIC
   113	Zachary Zeltsan, Alcatel-Lucent
   114	Dacheng Zhang, Huawei
   115	Lixia Zhang, UCLA
   116	Fei Zhang, ZTE Corporation
   117	Yi Zhao, Huawei
   118	Lianshu Zheng, Huawei Technologies
   119	Ning Zong, Huawei Technologies
   120	Glen Zorn, Network Zen

I will run the random selection algorithm on July 18th 2011 with the
seed sources specified in

https://datatracker.ietf.org/ann/nomcom/2985/ 

and selecting people in order subject to the constraint that no more
than two people with the same affiliation be among the members making
up the voting membership of the nominating committee.

Suresh Krishnan
Nomcom Chair 2011-2012
Email: nomcom-chair@ietf.org, suresh.krishnan@ericsson.com


From ibc@aliax.net  Tue Jul 12 00:48:51 2011
Return-Path: <ibc@aliax.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79C8621F90E4; Tue, 12 Jul 2011 00:48:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Level: 
X-Spam-Status: No, score=-2.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 ZrLKmLmkIOCI; Tue, 12 Jul 2011 00:48: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 A94F121F90D7; Tue, 12 Jul 2011 00:48:50 -0700 (PDT)
Received: by qwc23 with SMTP id 23so3270654qwc.31 for <multiple recipients>; Tue, 12 Jul 2011 00:48:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.105.95 with SMTP id s31mr4267743qco.228.1310456929704; Tue, 12 Jul 2011 00:48:49 -0700 (PDT)
Received: by 10.229.228.9 with HTTP; Tue, 12 Jul 2011 00:48:49 -0700 (PDT)
In-Reply-To: <4E1BD054.7010103@gmail.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <4E1BD054.7010103@gmail.com>
Date: Tue, 12 Jul 2011 09:48:49 +0200
Message-ID: <CALiegf=JjAYgjQRNh3-5NNvEP-cbAzB4hnuMV2R2WpEo3=1_ew@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 12 Jul 2011 08:06:28 -0700
Cc: hybi@ietf.org, ietf@ietf.org, draft-ietf-hybi-thewebsocketprotocol@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2011 07:48:51 -0000

2011/7/12 Mykyta Yevstifeyev <evnikita2@gmail.com>:
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Sec-WebSocket-Extensions: bar; baz=3D2
>>
>> =C2=A0 =C2=A0is exactly equivalent to
>>
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Sec-WebSocket-Extensions: foo, bar; ba=
z=3D2
>
> These two examples don't match the aforementioned ABNF; the space before
> "baz=3D2" should be removed.

Hi, are you sure of that? In SIP protocol (which inherits from HTTP
grammar) a header parameter (;foo=3Dlalala) can contain spaces anywhere
(before/after the ";", before/after the "=3D"). So something like:

   Sec-WebSocket-Extensions: foo  , bar  ; baz =3D 2

is valid.

However it's not clear for me wheter in this example "baz=3D2" is a
header param or a param just for the value "bar". In the last case it
would mean a specific header syntax, so spaces could be not allowed.
Could you please point to the ABNF grammar you meant?

Thanks.

--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From ibc@aliax.net  Tue Jul 12 01:23:09 2011
Return-Path: <ibc@aliax.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5950521F90DE; Tue, 12 Jul 2011 01:23:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Level: 
X-Spam-Status: No, score=-2.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 TD-wUeJm40fJ; Tue, 12 Jul 2011 01:23:08 -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 9A52421F90DB; Tue, 12 Jul 2011 01:23:08 -0700 (PDT)
Received: by qyk9 with SMTP id 9so2085467qyk.10 for <multiple recipients>; Tue, 12 Jul 2011 01:23:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.173.70 with SMTP id o6mr4688405qaz.322.1310458988080; Tue, 12 Jul 2011 01:23:08 -0700 (PDT)
Received: by 10.229.228.9 with HTTP; Tue, 12 Jul 2011 01:23:07 -0700 (PDT)
In-Reply-To: <4E1C01F3.4070906@gmx.de>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <4E1BD054.7010103@gmail.com> <CALiegf=JjAYgjQRNh3-5NNvEP-cbAzB4hnuMV2R2WpEo3=1_ew@mail.gmail.com> <4E1C01F3.4070906@gmx.de>
Date: Tue, 12 Jul 2011 10:23:07 +0200
Message-ID: <CALiegfmKK+Rka+eqU8=3zFVkL12wSh_w+VjoDxOYurgrmob_+A@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 12 Jul 2011 08:06:28 -0700
Cc: hybi@ietf.org, ietf@ietf.org, draft-ietf-hybi-thewebsocketprotocol@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2011 08:23:09 -0000

2011/7/12 Julian Reschke <julian.reschke@gmx.de>:
> That being said, I'm not happy with
>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 extension-param =3D token [ "=3D" token ]
>
> In HTTP header fields, parameters usually support both token and
> quoted-string form.

Right.


> Making this special means that existing header field parser code can't be
> easily re-used.

Well, not exaclty as any parser supporting tokens and quoted-strings
would also parse "just" tokens :)
However I agree that making new/custom grammar for a simple header
makes no sense.


--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From francis@aspl.es  Tue Jul 12 07:14:01 2011
Return-Path: <francis@aspl.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE83321F9175; Tue, 12 Jul 2011 07:14:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.884
X-Spam-Level: ****
X-Spam-Status: No, score=4.884 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_HOST_ALMOST_IP=1.889, HOST_EQ_STATIC=1.172, HOST_EQ_STATICIP=1.511, 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 KVRCILMAgSjh; Tue, 12 Jul 2011 07:14:01 -0700 (PDT)
Received: from mail.aspl.es (196.Red-212-170-101.staticIP.rima-tde.net [212.170.101.196]) by ietfa.amsl.com (Postfix) with ESMTP id 4537321F9171; Tue, 12 Jul 2011 07:13:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.aspl.es (Postfix) with ESMTP id B4179FCC1F7; Tue, 12 Jul 2011 16:13:55 +0200 (CEST)
X-Virus-Scanned: amavisd-new at aspl.es
Received: from mail.aspl.es ([127.0.0.1]) by localhost (dolphin.aspl.es [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CTIRERmHfrQM; Tue, 12 Jul 2011 16:13:54 +0200 (CEST)
Received: from [192.168.0.132] (barracuda [10.0.0.4]) by mail.aspl.es (Postfix) with ESMTP id A9487FCC076; Tue, 12 Jul 2011 16:13:54 +0200 (CEST)
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard: request for max frame size
From: Francis Brosnan Blazquez <francis@aspl.es>
To: Hybi <hybi@ietf.org>
In-Reply-To: <4E1BD054.7010103@gmail.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <4E1BD054.7010103@gmail.com>
Content-Type: text/plain; charset="ISO-8859-15"
Organization: ASPL
Date: Tue, 12 Jul 2011 16:13:56 +0200
Message-ID: <1310480036.26452.329.camel@vulcan.aspl.local>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Tue, 12 Jul 2011 08:06:28 -0700
Cc: ietf@ietf.org, draft-ietf-hybi-thewebsocketprotocol@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2011 14:14:02 -0000

Hi,

Recently, I posted [1] that websocket protocol should include an
indication about max frame size that is willing to accept the connecting
peer. 

Many pointed this is not an issue because you could use a stream
oriented API (like TCP send/recv and others), but that only bypasses the
problem (in some cases) not solves it.

Websocket protocol is frame based and every frame based protocol
designed until now has/need such feature or similar. Even TCP, for those
that proposes to use a stream oriented API as a solution, includes a
more complex mechanism than a simple max frame size (window based ack),
so each party can control/inform the sender. This is critical.

A good example for this would be the next. Let suppose you have a
constrained memory device (either because it is small or because it
accepts a large amount of connections). On that device you deploy a
websocket app that only accepts small messages (< 512 bytes, let's
say). 

In this context, you can hard code at your web app (javascript) that
must not send messages larger than this size (so you control websocket
payload size) and in the case you need to, you must split them
properly. 

However, even with this mechanism, you have no warranty that the browser
or an intermediary will join those messages into a single frame, causing
your device to receive a bigger message/frame than expected.

Assuming this I think we would require either to include a
Max-Frame-Size indication (or a really poor solution: to explicitly
state on the draft that frames must not be coalesced by intermediaries
or browsers). 

Regards,

[1] http://www.ietf.org/mail-archive/web/hybi/current/msg07641.html
-- 
Francis Brosnan Blázquez <francis.brosnan@aspl.es>
ASPL
91 134 14 22 - 91 134 14 45 - 91 116 07 57

AVISO LEGAL

Este mensaje se dirige exclusivamente a su destinatario. Los datos
incluidos en el presente correo son confidenciales y sometidos a secreto
profesional, se prohíbe divulgarlos, en virtud de las leyes vigentes. Si
usted no lo es y lo ha recibido por error o tiene conocimiento del mismo
por cualquier motivo, le rogamos que nos lo comunique por este medio y
proceda a destruirlo o borrarlo.

En virtud de lo dispuesto en la Ley Orgánica 15/1999, de 13 de
diciembre, de Protección de Datos de Carácter Personal, le informamos de
que sus datos de carácter personal, recogidos de fuentes accesibles al
público o datos que usted nos ha facilitado previamente, proceden de
bases de datos propiedad de Advanced Software Production Line, S.L.
(ASPL). No obstante, usted puede ejercitar sus derechos de acceso,
rectificación, cancelación y oposición dispuestos en la mencionada Ley
Orgánica, notificándolo por escrito a:
ASPL - Protección Datos, C/Antonio Suárez 10 A-102, 28802, Alcalá de
Henares (Madrid).


From evnikita2@gmail.com  Tue Jul 12 09:49:38 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 6E3AE21F8D6C for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 09:49:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.5
X-Spam-Level: 
X-Spam-Status: No, score=-3.5 tagged_above=-999 required=5 tests=[AWL=0.099, 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 dxH5yOo-i8JR for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 09:49:34 -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 266B621F8CED for <ietf@ietf.org>; Tue, 12 Jul 2011 09:49:33 -0700 (PDT)
Received: by bwb17 with SMTP id 17so4916038bwb.31 for <ietf@ietf.org>; Tue, 12 Jul 2011 09:49:33 -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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=6BsOeya3fDMuLU24luC65tcEyBXU4jkazgCinmhxJBM=; b=iwVfo3CiwP7nP4W8tA+nsyBwvfY8znUZDOOrqJWPCfByWlwNuOcyiLebKBIs+2lCJY TYRNAEQPBS/dufPBRoJ/20hQfXaxrCVWNSj/ec88rCSzntQZPKSv52/Vu5ys3utBHKxh EdCtmOxKPYLHRjlsQvkKYx9xxBNSvWH7SrAQ4=
Received: by 10.204.74.67 with SMTP id t3mr70269bkj.192.1310489372680; Tue, 12 Jul 2011 09:49:32 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id g13sm10313619bkd.10.2011.07.12.09.49.30 (version=SSLv3 cipher=OTHER); Tue, 12 Jul 2011 09:49:31 -0700 (PDT)
Message-ID: <4E1C7B48.4070000@gmail.com>
Date: Tue, 12 Jul 2011 19:50:16 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: Last Call: <draft-yevstifeyev-ion-report-06.txt> (Report on the Experiment with IETF Operational Notes (IONs)) to Informational RFC
References: <20110712143944.20141.23357.idtracker@ietfa.amsl.com>
In-Reply-To: <20110712143944.20141.23357.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2011 16:49:38 -0000

Hello,

As Russ agreed to sponsor this document on I-D submission cut-off date, 
I did make only some minor changed proposed by him during AD 
evaluation.  However I thought the document would be incomplete without 
analysis, so after LC I propose to add the following sub-section in the 
draft:

> 3.4. Analysis and Results
>
>    IONs were intended to serve as a means to document issues related to
>    procedures used by IETF or other parties, but to be more stable as a
>    simple web page and to have a more lightweight procedures for
>    approval than Best Current Practice (BCP) or other sort of RFC.  Even
>    though such middle-ground approach might be quite useful, it also
>    brings a number of complexities and negative effects, which are
>    described below.
>
>    First of all, IONs were mainly scoped to IETF procedural questions.
>    A number of IONs were published defining procedures used by IETF
>    community, such as ion-ad-sponsoring.  However, it should be noted
>    that the formal procedure of IONs approval, laid out in RFC 4693
>    [RFC4693] did not imply community involvement, unlike one for BCP or
>    other IETF Stream RFC.  Even though RFC 4693 intended IONs to cover
>    issues not sufficient for documenting in BCP, this regulation was
>    often overlooked.  This might have resulted in community non-
>    acceptance of such procedures, partial or full, if IONs were adopted
>    on the persistent basis.
>
>    Moreover, as IONs were lower in the hierarchy of IETF documents that
>    RFCs, published RFCs may override what mentioned in a particular ION
>    (whereas a published RFC may change already established procedures),
>    which might result in them not being sufficiently followed, creating
>    documentation conflicts.
>
>    Several IONS were published that describe the procedures used by IESG
>    or its members internally, such as ion-discuss-criteria or ion-tsv-
>    alt-cc.  Such material is obviously more appropriate for publication
>    as IESG Statements, which are also meant to be quite stable when
>    published and are approved at IESG's discretion.
>
>    A number of IONs were published covering different IAOC issues.  Such
>    IONs included ion-execd-tasks and ion-subpoena.  However, even though
>    IAOC works tightly with IETF, they have an ability to publish such
>    material on their site - <http://iaoc.ietf.org/>.
>
>    A one ION - ion-procdocs - was a reference guide to the IWTF Process
>    documents.  An other ION - ion-2026-practice - provided the criticism
>       and operational experience on RFC 2026 [RFC2026].  Both this
>    documents are fine as web pages, since the material contained in it
>    might change quickly and often.
>
>    ion-ion-format and ion-ion-store were published for the purpose of
>    the IONs series itself and were discarded upon experiment closure.
>    They are not analyzed here.
>
>    The aforementioned facts claim that IONs were less useful than the
>    equivalent information published in other way, and should be
>    abandoned, as proposed by Section 4 of RFC 4693 [RFC4693].

In order not to request the 2nd LC after this text is included, I'd like 
to seek community feedback on it during this Last Call.

Thanks,
Mykyta Yevstifeyev

12.07.2011 17:39, The IESG wrote:
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Report on the Experiment with IETF Operational Notes (IONs)'
>    <draft-yevstifeyev-ion-report-06.txt>  as an Informational RFC
>
> [ . . . ]


From stpeter@stpeter.im  Tue Jul 12 12:36:47 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 1A00E21F8C4C for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 12:36:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.509
X-Spam-Level: 
X-Spam-Status: No, score=-102.509 tagged_above=-999 required=5 tests=[AWL=0.090, 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 bJTpQ8kZmJ3p for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 12:36:42 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id C205521F8BB6 for <ietf@ietf.org>; Tue, 12 Jul 2011 12:36:42 -0700 (PDT)
Received: from dhcp-64-101-72-201.cisco.com (unknown [64.101.72.201]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 10634410EE; Tue, 12 Jul 2011 13:37:02 -0600 (MDT)
Message-ID: <4E1CA248.7060009@stpeter.im>
Date: Tue, 12 Jul 2011 13:36:40 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: Second Last Call: <draft-hammer-hostmeta-16.txt> (Web Host Metadata) to Proposed Standard -- feedback
References: <11CBFBA2-434B-43FC-90C4-DADBACB49226@mnot.net>
In-Reply-To: <11CBFBA2-434B-43FC-90C4-DADBACB49226@mnot.net>
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org IETF" <ietf@ietf.org>, 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: Tue, 12 Jul 2011 19:36:47 -0000

On 6/21/11 11:08 PM, Mark Nottingham wrote:
> 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.

How about publishing it on the standards track but not as a general
mechanism (i.e., why not clarify when it is and is not appropriate)?

Clearly, both service providers (Google, Yahoo, etc.) and spec authors
(draft-hardjono-oauth-dynreg-00, draft-hardjono-oauth-umacore-00) have
found hostmeta somewhat useful in certain contexts.

RFC 2026 says:

   A Proposed Standard specification is generally stable, has resolved
   known design choices, is believed to be well-understood, has received
   significant community review, and appears to enjoy enough community
   interest to be considered valuable.

and:

   Usually, neither implementation nor operational experience is
   required for the designation of a specification as a Proposed
   Standard.  However, such experience is highly desirable, and will
   usually represent a strong argument in favor of a Proposed Standard
   designation.

The spec seems to be stable at this point, it's received significant
review, people seem to understand what it does and how it works, it's
had both implementation and operational experience, and it appears to
enjoy enough community interest to be considered valuable in certain
contexts. I also think it has resolved the design choices and solved the
requirements that it set out to solve, although you might be right that
it doesn't solve all of the problems that a more generic metadata
framework would need to solve.

As a result, it seems like a fine candidate for Proposed Standard, i.e.,
an entry-level document on the standards track that might be modified or
even retracted based on further experience.

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

Again, perhaps we need to clarify that it is not necessarily a general
component of the web architecture, although it can be used to solve more
specific problems.

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

As discussed in responses to your message, XRD seems to have been an
appropriate tool for the job in this case. Whether XRD, too, is really a
general component of the web architecture is another question.

> * 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.

That could be something to work on if and when folks try to advance this
technology to the next maturity level (currently Draft Standard).

> * Scope of hosts -- The document doesn't crisply define what a "host"
> is.

This seems at least somewhat well-defined:

   a "host" is not a single resource but the entity
   controlling the collection of resources identified by Uniform
   Resource Identifiers (URI) with a common URI host [RFC3986].

That is, it references Section 3.2.2 of RFC 3986, which defines "host"
with some precision (albeit perhaps not "crisply").

> * 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.

It would be helpful to hear from folks who have deployed hostmeta to
hear if they have run into any operational issues of the kind you
describe here.

> * 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.
> 
> 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.

That sounds like good input to a more generic approach. Many discovery
protocols do seem to have an inherent chattiness about them, but you
might be right that ideally the round trips could be kept to a minimum.

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

Again, I think some clarifying language about the applicability of the
technology is in order.

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

And my apologies for taking so long to reply.

Peter

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



From mrex@sap.com  Tue Jul 12 13:06: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 B7D789E8024 for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 13:06:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.931
X-Spam-Level: 
X-Spam-Status: No, score=-9.931 tagged_above=-999 required=5 tests=[AWL=0.318,  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 wNyyOOFsNTvP for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 13:06: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 802C39E801C for <ietf@ietf.org>; Tue, 12 Jul 2011 13:06:14 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p6CK69qR018578 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 12 Jul 2011 22:06:09 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201107122006.p6CK68YT022236@fs4113.wdf.sap.corp>
Subject: Re: Second Last Call: <draft-hammer-hostmeta-16.txt> (Web Host
To: stpeter@stpeter.im (Peter Saint-Andre)
Date: Tue, 12 Jul 2011 22:06:08 +0200 (MEST)
In-Reply-To: <4E1CA248.7060009@stpeter.im> from "Peter Saint-Andre" at Jul 12, 11 01:36:40 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: mnot@mnot.net, ietf@ietf.org, eran@hueniverse.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: Tue, 12 Jul 2011 20:06:15 -0000

Peter Saint-Andre wrote:
> 
> On 6/21/11 11:08 PM, Mark Nottingham wrote:
> > 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.
> 
> How about publishing it on the standards track but not as a general
> mechanism (i.e., why not clarify when it is and is not appropriate)?

How about publishing as Informational?

RFC 2026 says:

   4.  THE INTERNET STANDARDS TRACK

   Specifications that are intended to become Internet Standards evolve
   through a set of maturity levels known as the "standards track".
   These maturity levels -- "Proposed Standard", "Draft Standard", and
   "Standard" -- are defined and discussed in section 4.1.

If there is no strong consensus and commitment to work the document
along the standards track up to full standard, then it shouldn't
be on the standards track at all.

For documents where the only purpose of publishing it is only to obtain
an rfc number for it, but otherwise just describe "this is how others
have solved a particular problem before" and let vendors and implementors
wiggle out interop, then Informational is quite appropriate.


-Martin

From barryleiba.mailing.lists@gmail.com  Tue Jul 12 14:28:10 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 A8F4521F8BDF for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 14:28:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.11
X-Spam-Level: 
X-Spam-Status: No, score=-104.11 tagged_above=-999 required=5 tests=[AWL=0.867, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, GB_I_LETTER=-2, 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 Xmx02bJj6BAX for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 14:28:10 -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 A449421F8BE0 for <ietf@ietf.org>; Tue, 12 Jul 2011 14:28:09 -0700 (PDT)
Received: by yxp4 with SMTP id 4so2668526yxp.31 for <ietf@ietf.org>; Tue, 12 Jul 2011 14:28:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=XzCYSzJTmgtVYDodHK5BdqaMLMSGj8Qh1gzkwD0lmVY=; b=x+AqK3kbir6q7h9UyaiizpAqeOLhF33n2GWcp2hRx8PIloD7LuCZZfY50D+0zEyCel bHtlW286LH0//Pt1q5LzsHHRR3+g6WiJzgSmy8FMTl9Od9IG8KO2t4NHjl9MkbqPVhC0 8dGjbzoAFgbgesv1Vk4muVtcJCLF2N3jtX7NU=
MIME-Version: 1.0
Received: by 10.150.144.3 with SMTP id r3mr583013ybd.176.1310506089133; Tue, 12 Jul 2011 14:28:09 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.172.10 with HTTP; Tue, 12 Jul 2011 14:28:09 -0700 (PDT)
Date: Tue, 12 Jul 2011 17:28:09 -0400
X-Google-Sender-Auth: zIz4jtBTYHhBC0hv0bYDZfSo_QY
Message-ID: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com>
Subject: Confidentiality notices on email messages
From: Barry Leiba <barryleiba@computer.org>
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2011 21:28:10 -0000

I am increasingly seeing IETF participants posting messages to IETF
mailing lists, sending messages to chairs and ADs, and so on, where
their messages include confidentiality/security/legal notices at the
bottom.  You know the ones; here are excerpts from two recent
examples:
--------------------------------
> Information Security Notice: The information contained in this
> mail is solely the property of the sender's organization. This
> mail communication is confidential. Recipients named above are
> obligated to maintain secrecy and are not permitted to disclose
> the contents of this communication with others.
--------------------------------
> CONFIDENTIALITY NOTICE
> The information contained in this e-mail and any attachments is
> CONFIDENTIAL and is intended only for the use of the addressee.
> Any unauthorized use, disclosure, distribution, dissemination,
> or copying is strictly prohibited and may be unlawful. If you are
> not the intended recipient, you are prohibited from any further
> viewing of the e-mail or any attachments or from making any use
> of the e-mail or attachments.
--------------------------------

Those are just the beginnings of them -- they go on, and continue for
another paragraph each.  I've seen them in Spanish, French, and
German, as well as English.

Now, apart from being long and annoying, they're in conflict with the
IETF's Note Well, which applies to anything posted to IETF mailing
lists or sent to anyone in IETF leadership about IETF business:
http://www.ietf.org/about/note-well.html

I'd also argue that those posting such messages are running afoul of
their own organizations' rules by posting "confidential" messages
publicly.  Of course, that's nonsense, but, hey, folks, it wouldn't be
the first time a company might behave irrationally and discipline
someone base on the letter, rather than the intent, of a rule.

Of course, I know that these messages are put there automatically,
according to your companies' policies.  No one is actually including
them on purpose, and most probably aren't even aware, any more, that
they're there.  But they are.

I don't think this merits any official statement by the IESG, though
the IESG might want to consider for itself whether it does.  But how
about if we try to deal with this as a community?  It rather makes you
look silly to have those notices there.  And you don't want to look
silly, right?  So have a look at your posts, everyone, and if yours
have any such junk at the bottoms of them, please do one of two
things, tout de suite:

1. Arrange not to have them put there.  If there's some way you can
get an exception to your company's rule for things sent to the IETF,
do it.

2. Get a non-company address, and use that for your IETF
participation.  You can get free addresses easily.  This option also
has the advantage that if you should change employers, your
IETF-related email address doesn't need to change.

Barry

From cntreras@gmail.com  Tue Jul 12 14:37:10 2011
Return-Path: <cntreras@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 259579E8035 for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 14:37:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.598
X-Spam-Level: 
X-Spam-Status: No, score=-104.598 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, GB_I_LETTER=-2, 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 G5IiCfowCAOE for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 14:37:09 -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 7BED721F853D for <ietf@ietf.org>; Tue, 12 Jul 2011 14:36:48 -0700 (PDT)
Received: by fxe4 with SMTP id 4so6751696fxe.27 for <ietf@ietf.org>; Tue, 12 Jul 2011 14:36:47 -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=NDb/RaKPYvfi62wh7KRsqLcKU2D7GFOyAmwjgaqMegY=; b=Rq9WmrT7i3GW6477+Mhaly6qdwQBFcMawrId9IGp6JVlQaSBydW/fjgjCNbDC1KXXz 76qnNfPqz4/bwcm3Z3s+J9K/MIsIeZ6+s9nBvR9925Z0ufX2kOr3EvMXLlrH7oxr2pl6 q/3vmXj3Cdxb1WKl3YjsIb3jQtsMRLOxG0s8o=
MIME-Version: 1.0
Received: by 10.223.68.22 with SMTP id t22mr498496fai.145.1310506607353; Tue, 12 Jul 2011 14:36:47 -0700 (PDT)
Received: by 10.223.102.70 with HTTP; Tue, 12 Jul 2011 14:36:47 -0700 (PDT)
In-Reply-To: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com>
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com>
Date: Tue, 12 Jul 2011 16:36:47 -0500
Message-ID: <CAP0PwYYmLxPSoPvUqYOO_y=Hdn9vBSTRC5ax4wnjzE1SD1+aLg@mail.gmail.com>
Subject: Re: Confidentiality notices on email messages
From: Jorge Contreras <cntreras@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary=0015174c1326cea04b04a7e618c2
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: Tue, 12 Jul 2011 21:37:10 -0000

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

Barry,

You may want to refer to Section 5.2 of RFC 5378, which addresses this
issue:

"Each Contributor agrees that any statement in a Contribution, whether
generated automatically or otherwise, that states or implies that the
Contribution is confidential or subject to any privilege, can be disregarded
for all purposes, and will be of no force or effect."

Best regards,
Jorge

On Tue, Jul 12, 2011 at 4:28 PM, Barry Leiba <barryleiba@computer.org>wrote:

> I am increasingly seeing IETF participants posting messages to IETF
> mailing lists, sending messages to chairs and ADs, and so on, where
> their messages include confidentiality/security/legal notices at the
> bottom.  You know the ones; here are excerpts from two recent
> examples:
> --------------------------------
> > Information Security Notice: The information contained in this
> > mail is solely the property of the sender's organization. This
> > mail communication is confidential. Recipients named above are
> > obligated to maintain secrecy and are not permitted to disclose
> > the contents of this communication with others.
> --------------------------------
> > CONFIDENTIALITY NOTICE
> > The information contained in this e-mail and any attachments is
> > CONFIDENTIAL and is intended only for the use of the addressee.
> > Any unauthorized use, disclosure, distribution, dissemination,
> > or copying is strictly prohibited and may be unlawful. If you are
> > not the intended recipient, you are prohibited from any further
> > viewing of the e-mail or any attachments or from making any use
> > of the e-mail or attachments.
> --------------------------------
>
> Those are just the beginnings of them -- they go on, and continue for
> another paragraph each.  I've seen them in Spanish, French, and
> German, as well as English.
>
> Now, apart from being long and annoying, they're in conflict with the
> IETF's Note Well, which applies to anything posted to IETF mailing
> lists or sent to anyone in IETF leadership about IETF business:
> http://www.ietf.org/about/note-well.html
>
> I'd also argue that those posting such messages are running afoul of
> their own organizations' rules by posting "confidential" messages
> publicly.  Of course, that's nonsense, but, hey, folks, it wouldn't be
> the first time a company might behave irrationally and discipline
> someone base on the letter, rather than the intent, of a rule.
>
> Of course, I know that these messages are put there automatically,
> according to your companies' policies.  No one is actually including
> them on purpose, and most probably aren't even aware, any more, that
> they're there.  But they are.
>
> I don't think this merits any official statement by the IESG, though
> the IESG might want to consider for itself whether it does.  But how
> about if we try to deal with this as a community?  It rather makes you
> look silly to have those notices there.  And you don't want to look
> silly, right?  So have a look at your posts, everyone, and if yours
> have any such junk at the bottoms of them, please do one of two
> things, tout de suite:
>
> 1. Arrange not to have them put there.  If there's some way you can
> get an exception to your company's rule for things sent to the IETF,
> do it.
>
> 2. Get a non-company address, and use that for your IETF
> participation.  You can get free addresses easily.  This option also
> has the advantage that if you should change employers, your
> IETF-related email address doesn't need to change.
>
> Barry
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

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

Barry,<br><br>You may want to refer to Section 5.2 of RFC 5378, which addre=
sses this issue:<br><br>&quot;Each
   Contributor agrees that any statement in a Contribution, whether
   generated automatically or otherwise, that states or implies that the
   Contribution is confidential or subject to any privilege, can be
   disregarded for all purposes, and will be of no force or effect.&quot;<b=
r><br>Best regards,<br>Jorge<br><br><div class=3D"gmail_quote">On Tue, Jul =
12, 2011 at 4:28 PM, Barry Leiba <span dir=3D"ltr">&lt;<a href=3D"mailto:ba=
rryleiba@computer.org">barryleiba@computer.org</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">I am increasingly seeing IETF participants =
posting messages to IETF<br>
mailing lists, sending messages to chairs and ADs, and so on, where<br>
their messages include confidentiality/security/legal notices at the<br>
bottom. =A0You know the ones; here are excerpts from two recent<br>
examples:<br>
--------------------------------<br>
&gt; Information Security Notice: The information contained in this<br>
&gt; mail is solely the property of the sender&#39;s organization. This<br>
&gt; mail communication is confidential. Recipients named above are<br>
&gt; obligated to maintain secrecy and are not permitted to disclose<br>
&gt; the contents of this communication with others.<br>
--------------------------------<br>
&gt; CONFIDENTIALITY NOTICE<br>
&gt; The information contained in this e-mail and any attachments is<br>
&gt; CONFIDENTIAL and is intended only for the use of the addressee.<br>
&gt; Any unauthorized use, disclosure, distribution, dissemination,<br>
&gt; or copying is strictly prohibited and may be unlawful. If you are<br>
&gt; not the intended recipient, you are prohibited from any further<br>
&gt; viewing of the e-mail or any attachments or from making any use<br>
&gt; of the e-mail or attachments.<br>
--------------------------------<br>
<br>
Those are just the beginnings of them -- they go on, and continue for<br>
another paragraph each. =A0I&#39;ve seen them in Spanish, French, and<br>
German, as well as English.<br>
<br>
Now, apart from being long and annoying, they&#39;re in conflict with the<b=
r>
IETF&#39;s Note Well, which applies to anything posted to IETF mailing<br>
lists or sent to anyone in IETF leadership about IETF business:<br>
<a href=3D"http://www.ietf.org/about/note-well.html" target=3D"_blank">http=
://www.ietf.org/about/note-well.html</a><br>
<br>
I&#39;d also argue that those posting such messages are running afoul of<br=
>
their own organizations&#39; rules by posting &quot;confidential&quot; mess=
ages<br>
publicly. =A0Of course, that&#39;s nonsense, but, hey, folks, it wouldn&#39=
;t be<br>
the first time a company might behave irrationally and discipline<br>
someone base on the letter, rather than the intent, of a rule.<br>
<br>
Of course, I know that these messages are put there automatically,<br>
according to your companies&#39; policies. =A0No one is actually including<=
br>
them on purpose, and most probably aren&#39;t even aware, any more, that<br=
>
they&#39;re there. =A0But they are.<br>
<br>
I don&#39;t think this merits any official statement by the IESG, though<br=
>
the IESG might want to consider for itself whether it does. =A0But how<br>
about if we try to deal with this as a community? =A0It rather makes you<br=
>
look silly to have those notices there. =A0And you don&#39;t want to look<b=
r>
silly, right? =A0So have a look at your posts, everyone, and if yours<br>
have any such junk at the bottoms of them, please do one of two<br>
things, tout de suite:<br>
<br>
1. Arrange not to have them put there. =A0If there&#39;s some way you can<b=
r>
get an exception to your company&#39;s rule for things sent to the IETF,<br=
>
do it.<br>
<br>
2. Get a non-company address, and use that for your IETF<br>
participation. =A0You can get free addresses easily. =A0This option also<br=
>
has the advantage that if you should change employers, your<br>
IETF-related email address doesn&#39;t need to change.<br>
<br>
Barry<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>

--0015174c1326cea04b04a7e618c2--

From barryleiba.mailing.lists@gmail.com  Tue Jul 12 14:39: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 385229E8030 for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 14:39:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.132
X-Spam-Level: 
X-Spam-Status: No, score=-103.132 tagged_above=-999 required=5 tests=[AWL=-0.155, 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 7yxnnS5ADqXS for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 14:39: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 9BCBC21F853D for <ietf@ietf.org>; Tue, 12 Jul 2011 14:39:49 -0700 (PDT)
Received: by ywp31 with SMTP id 31so1789615ywp.31 for <ietf@ietf.org>; Tue, 12 Jul 2011 14:39:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=cyhzr1+wIAT31JM3sZfwlmyIuVLusVP6gaIz/SEGcDk=; b=cQ9JaIi0LweiGsRDe1xl/vVK3DVgVjrIpgg2MDnKb7GkpI6q7WU25gr1aihMQQZgvg TqFjZXaBc+2bc2o4zMI4YIV9PNZH5k1XjdIzNPq6LiAUiLM9FWlqorH37Two7xP6qNRi B6dKmT/V250o0zdqa+8c3LMluKPjPz5zOks1c=
MIME-Version: 1.0
Received: by 10.146.88.15 with SMTP id l15mr476701yab.6.1310506789174; Tue, 12 Jul 2011 14:39:49 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.172.10 with HTTP; Tue, 12 Jul 2011 14:39:49 -0700 (PDT)
In-Reply-To: <CAP0PwYYmLxPSoPvUqYOO_y=Hdn9vBSTRC5ax4wnjzE1SD1+aLg@mail.gmail.com>
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <CAP0PwYYmLxPSoPvUqYOO_y=Hdn9vBSTRC5ax4wnjzE1SD1+aLg@mail.gmail.com>
Date: Tue, 12 Jul 2011 17:39:49 -0400
X-Google-Sender-Auth: AnHLDIinNBV_q_IaVUHpnNyE8wI
Message-ID: <CAC4RtVCwbCsj5vH5UwxWYEpJnAZePRr5HWyLFJ6t1U=_gXfODQ@mail.gmail.com>
Subject: Re: Confidentiality notices on email messages
From: Barry Leiba <barryleiba@computer.org>
To: Jorge Contreras <cntreras@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2011 21:39:50 -0000

Hi, Jorge.

> You may want to refer to Section 5.2 of RFC 5378, which addresses this
> issue:
>
> "Each Contributor agrees that any statement in a Contribution, whether
> generated automatically or otherwise, that states or implies that the
> Contribution is confidential or subject to any privilege, can be disregarded
> for all purposes, and will be of no force or effect."

Yes, I'm aware of that.  My point was exactly that: that the
confidentiality statement is pointless.  I'm asking people to try to
get rid of them entirely.

Barry

From brian.e.carpenter@gmail.com  Tue Jul 12 15:20:20 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 7CC9A21F8C28 for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 15:20:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.645
X-Spam-Level: 
X-Spam-Status: No, score=-103.645 tagged_above=-999 required=5 tests=[AWL=-0.046, 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 meTrCPtfQfYX for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 15:20:19 -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 A9B1421F8C24 for <ietf@ietf.org>; Tue, 12 Jul 2011 15:20:19 -0700 (PDT)
Received: by qwc23 with SMTP id 23so3726001qwc.31 for <ietf@ietf.org>; Tue, 12 Jul 2011 15:20:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=KRfqrB2ifYLGtmTuMYkLJmROln3XdjHBlG11JjPV4Gw=; b=VieKil7QEdezKhj4qX1guJyM7R+9TaivKgWOfl8s+SxjbrJj+Vpfer37SLgZfnUaud /Zd5K/hPLmBDxppK41rBgRdU1aQJZVn/990nKfv8M6z8f2gfk7RFM3UgpsBxSraRJjpm vfHHsdSY14K2yD1lH8o7leym0gwO+ixrKAj2w=
Received: by 10.224.204.72 with SMTP id fl8mr468371qab.150.1310509218391; Tue, 12 Jul 2011 15:20:18 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id g16sm11410322qcs.35.2011.07.12.15.20.16 (version=SSLv3 cipher=OTHER); Tue, 12 Jul 2011 15:20:18 -0700 (PDT)
Message-ID: <4E1CC89E.7010907@gmail.com>
Date: Wed, 13 Jul 2011 10:20:14 +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: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Last Call: <draft-yevstifeyev-ion-report-06.txt> (Report on the Experiment with IETF Operational Notes (IONs)) to Informational RFC
References: <20110712143944.20141.23357.idtracker@ietfa.amsl.com> <4E1C7B48.4070000@gmail.com>
In-Reply-To: <4E1C7B48.4070000@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: Tue, 12 Jul 2011 22:20:20 -0000

Mykyta,

I think the draft is fine without this addition, which contains some statements
that I disagree with. I don't think analysis is needed; this all ancient history
anyway.

Regards
   Brian

On 2011-07-13 04:50, Mykyta Yevstifeyev wrote:
> Hello,
> 
> As Russ agreed to sponsor this document on I-D submission cut-off date,
> I did make only some minor changed proposed by him during AD
> evaluation.  However I thought the document would be incomplete without
> analysis, so after LC I propose to add the following sub-section in the
> draft:
> 
>> 3.4. Analysis and Results
>>
>>    IONs were intended to serve as a means to document issues related to
>>    procedures used by IETF or other parties, but to be more stable as a
>>    simple web page and to have a more lightweight procedures for
>>    approval than Best Current Practice (BCP) or other sort of RFC.  Even
>>    though such middle-ground approach might be quite useful, it also
>>    brings a number of complexities and negative effects, which are
>>    described below.
>>
>>    First of all, IONs were mainly scoped to IETF procedural questions.
>>    A number of IONs were published defining procedures used by IETF
>>    community, such as ion-ad-sponsoring.  However, it should be noted
>>    that the formal procedure of IONs approval, laid out in RFC 4693
>>    [RFC4693] did not imply community involvement, unlike one for BCP or
>>    other IETF Stream RFC.  Even though RFC 4693 intended IONs to cover
>>    issues not sufficient for documenting in BCP, this regulation was
>>    often overlooked.  This might have resulted in community non-
>>    acceptance of such procedures, partial or full, if IONs were adopted
>>    on the persistent basis.
>>
>>    Moreover, as IONs were lower in the hierarchy of IETF documents that
>>    RFCs, published RFCs may override what mentioned in a particular ION
>>    (whereas a published RFC may change already established procedures),
>>    which might result in them not being sufficiently followed, creating
>>    documentation conflicts.
>>
>>    Several IONS were published that describe the procedures used by IESG
>>    or its members internally, such as ion-discuss-criteria or ion-tsv-
>>    alt-cc.  Such material is obviously more appropriate for publication
>>    as IESG Statements, which are also meant to be quite stable when
>>    published and are approved at IESG's discretion.
>>
>>    A number of IONs were published covering different IAOC issues.  Such
>>    IONs included ion-execd-tasks and ion-subpoena.  However, even though
>>    IAOC works tightly with IETF, they have an ability to publish such
>>    material on their site - <http://iaoc.ietf.org/>.
>>
>>    A one ION - ion-procdocs - was a reference guide to the IWTF Process
>>    documents.  An other ION - ion-2026-practice - provided the criticism
>>       and operational experience on RFC 2026 [RFC2026].  Both this
>>    documents are fine as web pages, since the material contained in it
>>    might change quickly and often.
>>
>>    ion-ion-format and ion-ion-store were published for the purpose of
>>    the IONs series itself and were discarded upon experiment closure.
>>    They are not analyzed here.
>>
>>    The aforementioned facts claim that IONs were less useful than the
>>    equivalent information published in other way, and should be
>>    abandoned, as proposed by Section 4 of RFC 4693 [RFC4693].
> 
> In order not to request the 2nd LC after this text is included, I'd like
> to seek community feedback on it during this Last Call.
> 
> Thanks,
> Mykyta Yevstifeyev
> 
> 12.07.2011 17:39, The IESG wrote:
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'Report on the Experiment with IETF Operational Notes (IONs)'
>>    <draft-yevstifeyev-ion-report-06.txt>  as an Informational RFC
>>
>> [ . . . ]
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 

From touch@isi.edu  Tue Jul 12 15:24:25 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 6119121F8C49; Tue, 12 Jul 2011 15:24:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.62
X-Spam-Level: 
X-Spam-Status: No, score=-105.62 tagged_above=-999 required=5 tests=[AWL=0.979, 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 1Bfx+e1ifI94; Tue, 12 Jul 2011 15:24:24 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 72CF721F8C47; Tue, 12 Jul 2011 15:24:24 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p6CMNoiP020361 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 12 Jul 2011 15:23:50 -0700 (PDT)
Message-ID: <4E1CC976.9000007@isi.edu>
Date: Tue, 12 Jul 2011 15:23:50 -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 Halpern <jmh@joelhalpern.com>
Subject: Re: notes from discussion of KARP design guidelines
References: <4E17210A.1070402@joelhalpern.com> <5662A966-70AD-4A63-BA31-8CE1C9635687@cisco.com> <4E1747BB.8080602@cisco.com> <4E19B2DC.4030003@joelhalpern.com>
In-Reply-To: <4E19B2DC.4030003@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: stbryant@cisco.com, IETF discussion list <ietf@ietf.org>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2011 22:24:25 -0000

Hi, Joel (et al.),

On 7/10/2011 7:10 AM, Joel Halpern wrote:
> Joe,
> THE KARP WG Chairs have reviewed your comments, in order to figure out
> what the best way to address them. We would appreciate it if you could
> engage in discussion of this proposal on the KARP working group email
> list. If you feel we are still not understanding your point, we would be
> happy to make some time avaialble for discussion at the WG session in
> Quebec City. (Comments from anyone else, particularly WG members, on the
> proposals being made by the WG chairs are appreciated as well.)
>
> Rather than a line by line response, we have tried to find the common
> themes and respond to them. If we have missed major issues, please let
> us know.
>
> You raised concern about the use of the term "on-the-wire." Rather than
> replace the term, we would prefer to add descriptive text early in the
> document. This text would note that it is a widely used term in IETF
> documents, including many RFCs. It would also state for clarity that in
> this document it is used to refer to the message sent from one routing
> process to another.

That's a great example of why this term should be removed. The message 
sent from one BGP to another is sent *inside* a TCP connection, and 
nobody would ever call the TCP bytestream payload the message "on the 
wire".

This term is simply sloppy, and just as the security community rightly 
raises issues with similarly poor use of its terms (e.g., "random" where 
pseudorandom or arbitrary are intended, or "authenticated" where 
integrity protection is intended), I consider this a *significant* 
transport issue.

> With regard to your comment about identifiers, we can add in the
> description of protocol reviews indications that such reviews should be
> clear about what IDs the review considers need protecting, as that is
> important context for the protocol review.

OK.

> As noted in other exchanges, the document abstract needs a complete
> rewrite. It should be just an abstract, with the rest of the context
> either removed or moved to the introduction. In doing so, we will add
> text describing briefly the general concept of the routing protocol
> transport.

OK.

> In general however, protocol specific behaviors are to be left to the
> protocol analysis documents. Equally, descriptions of detailed threats
> will be left either to the threat document or to the individual protocol
> analysis document as appropriate.

My goal is to make some transport properties as notable and discussed in 
as much (or as little) detail as, e.g., multicast and unicast already 
are in the current document.

> There are several items in your comments indicating that you would like
> to see more discussion in the design guidelines of the protocol
> layering. That does not seem to be a useful addition to this document.
> Again, individual protocol analysis documents will deal with that where
> it is appropriate, and avoid it where it is a distraction. We do not see
> useful general statements of guidance that can be put into this document.

As noted above, this is already in the document w.r.t. 
multicast/unicast; I'm suggesting that it's equally appropriate to 
include similar discussion of the issues of other layers on routing 
protocol security.

> Adding some general text in the discussion of communication modes
> elaborating on the difference between the communication as seen by the
> routing and security components, and the actual communication (e.g. that
> what is seen as multicast may be delivered as broadcast or multiple
> uni-cast) does seem a helpful addition to the document, and we will do
> that.

I'm not sure if this is basically all I'm asking for; see above. The 
intent was to add discussion of some known transport issues that are as 
relevant as the multicast/unicast difference already discussed, in 
similar detail.

Joe

From randy@qualcomm.com  Tue Jul 12 15:32:56 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 19AD221F8AED for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 15:32:56 -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 9vLju3thuywO for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 15:32:51 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id CFCCF21F85F5 for <ietf@ietf.org>; Tue, 12 Jul 2011 15:32:51 -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=1310509971; x=1342045971; h=message-id:x-mailer:date:to:from:subject:mime-version: content-type:x-random-sig-tag:x-originating-ip; z=Message-ID:=20<p0624064dca427b67bdfa@loud.pensive.org> |X-Mailer:=20Eudora=20for=20Mac=20OS=20X|Date:=20Tue,=201 2=20Jul=202011=2015:32:18=20-0700|To:=20<ietf@ietf.org> |From:=20Randall=20Gellens=20<randy@qualcomm.com> |Subject:=20LAST=20CALL:=20=20Room=20at=20the=20Hilton=20 for=20CAD$229/night|MIME-Version:=201.0|Content-Type:=20t ext/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=u3b51uPIyovqGFGwLW4sKfdbua1lTAXWzbjJUOsQOCs=; b=vOTI66ffirLDrFqcuj1opIeJRwHidCrZ4e/Nk4vScD+rBJQ/f8jJGaXM mvNmGOsDBddpNQVh0c8C864b6tKdPqQLpfYzWe8Gk3YxlEiv0liPUTjgF ZoHEH9AFPKKehnPiDVEl3IqBMOQudeeHkluu+T07pBBpq4TGMFUn4dB06 0=;
X-IronPort-AV: E=McAfee;i="5400,1158,6405"; a="103146208"
Received: from ironmsg02-r.qualcomm.com ([172.30.46.16]) by wolverine02.qualcomm.com with ESMTP; 12 Jul 2011 15:32:51 -0700
X-IronPort-AV: E=Sophos;i="4.65,521,1304319600"; d="scan'208";a="155071138"
Received: from nasanexhc05.na.qualcomm.com ([172.30.48.2]) by ironmsg02-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 12 Jul 2011 15:32:50 -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.323.0; Tue, 12 Jul 2011 15:32:19 -0700
Message-ID: <p0624064dca427b67bdfa@loud.pensive.org>
X-Mailer: Eudora for Mac OS X
Date: Tue, 12 Jul 2011 15:32:18 -0700
To: <ietf@ietf.org>
From: Randall Gellens <randy@qualcomm.com>
Subject: LAST CALL:  Room at the Hilton for CAD$229/night
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, 12 Jul 2011 22:32:56 -0000

Last call before I cancel this.  If you would like a room at the 
Hilton for CAD$229/night please let me know.  I seem to have a spare.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Every word is like an unnecessary stain on silence and nothingness.
                                                         --Beckett

From stbryant@cisco.com  Tue Jul 12 15:35:33 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 BEC741F0C37; Tue, 12 Jul 2011 15:35:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.536
X-Spam-Level: 
X-Spam-Status: No, score=-110.536 tagged_above=-999 required=5 tests=[AWL=0.063, 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 v1j0VNFsDk4w; Tue, 12 Jul 2011 15:35:33 -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 846501F0C36; Tue, 12 Jul 2011 15:35:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=4769; q=dns/txt; s=iport; t=1310510132; x=1311719732; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=XTiWrkE8cE518f7Gy7x8/JEyRrRSC3acpsQ3VHe/gHM=; b=XAgDvJJQQM8SeL++jNN2BkeNADr7z+QRoBrpi25saJ0Q/OSom8T/I4ni +lo7NoCnmrW+w+ccVe7BThvey0dMYH95keFRV+a64HOCBBz1gyR/cxQSr wxxf/pUEPiKToAM5eWuA8WQjG2CzZwRHMV40ufbdFd3A0cuQSnTKCPVXC k=;
X-IronPort-AV: E=Sophos;i="4.65,522,1304294400"; d="scan'208";a="42528593"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 12 Jul 2011 22:35:31 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p6CMZOcA018654; Tue, 12 Jul 2011 22:35:31 GMT
Received: from stbryant-mac2.local (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id p6CMZLNR007031; Tue, 12 Jul 2011 23:35:22 +0100 (BST)
Message-ID: <4E1CCC76.9090409@cisco.com>
Date: Tue, 12 Jul 2011 23:36:38 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: notes from discussion of KARP design guidelines
References: <4E17210A.1070402@joelhalpern.com> <5662A966-70AD-4A63-BA31-8CE1C9635687@cisco.com> <4E1747BB.8080602@cisco.com> <4E19B2DC.4030003@joelhalpern.com> <4E1CC976.9000007@isi.edu>
In-Reply-To: <4E1CC976.9000007@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2011 22:35:33 -0000

On 12/07/2011 23:23, Joe Touch wrote:
> Hi, Joel (et al.),
>
> On 7/10/2011 7:10 AM, Joel Halpern wrote:
>> Joe,
>> THE KARP WG Chairs have reviewed your comments, in order to figure out
>> what the best way to address them. We would appreciate it if you could
>> engage in discussion of this proposal on the KARP working group email
>> list. If you feel we are still not understanding your point, we would be
>> happy to make some time avaialble for discussion at the WG session in
>> Quebec City. (Comments from anyone else, particularly WG members, on the
>> proposals being made by the WG chairs are appreciated as well.)
>>
>> Rather than a line by line response, we have tried to find the common
>> themes and respond to them. If we have missed major issues, please let
>> us know.
>>
>> You raised concern about the use of the term "on-the-wire." Rather than
>> replace the term, we would prefer to add descriptive text early in the
>> document. This text would note that it is a widely used term in IETF
>> documents, including many RFCs. It would also state for clarity that in
>> this document it is used to refer to the message sent from one routing
>> process to another.
>
> That's a great example of why this term should be removed. The message 
> sent from one BGP to another is sent *inside* a TCP connection, and 
> nobody would ever call the TCP bytestream payload the message "on the 
> wire".
>
> This term is simply sloppy, and just as the security community rightly 
> raises issues with similarly poor use of its terms (e.g., "random" 
> where pseudorandom or arbitrary are intended, or "authenticated" where 
> integrity protection is intended), I consider this a *significant* 
> transport issue.

Joe

Please can you suggest a suitable generic term that covers the
set of cases that we need to deal with in routing - i.e.
over the MAC, over IP, over UDP and over TCP, so that we can
discuss inter routing entity message passing as an abstract
operation.

As Joel says when we get to the detailed design of each routing
protocol we will discuss the details, but we want a high level
discussion in this document.

Note BTW that 186 RFCs use the term "on the wire" in this
sort of situation.

- Stewart
>
>> With regard to your comment about identifiers, we can add in the
>> description of protocol reviews indications that such reviews should be
>> clear about what IDs the review considers need protecting, as that is
>> important context for the protocol review.
>
> OK.
>
>> As noted in other exchanges, the document abstract needs a complete
>> rewrite. It should be just an abstract, with the rest of the context
>> either removed or moved to the introduction. In doing so, we will add
>> text describing briefly the general concept of the routing protocol
>> transport.
>
> OK.
>
>> In general however, protocol specific behaviors are to be left to the
>> protocol analysis documents. Equally, descriptions of detailed threats
>> will be left either to the threat document or to the individual protocol
>> analysis document as appropriate.
>
> My goal is to make some transport properties as notable and discussed 
> in as much (or as little) detail as, e.g., multicast and unicast 
> already are in the current document.
>
>> There are several items in your comments indicating that you would like
>> to see more discussion in the design guidelines of the protocol
>> layering. That does not seem to be a useful addition to this document.
>> Again, individual protocol analysis documents will deal with that where
>> it is appropriate, and avoid it where it is a distraction. We do not see
>> useful general statements of guidance that can be put into this 
>> document.
>
> As noted above, this is already in the document w.r.t. 
> multicast/unicast; I'm suggesting that it's equally appropriate to 
> include similar discussion of the issues of other layers on routing 
> protocol security.
>
>> Adding some general text in the discussion of communication modes
>> elaborating on the difference between the communication as seen by the
>> routing and security components, and the actual communication (e.g. that
>> what is seen as multicast may be delivered as broadcast or multiple
>> uni-cast) does seem a helpful addition to the document, and we will do
>> that.
>
> I'm not sure if this is basically all I'm asking for; see above. The 
> intent was to add discussion of some known transport issues that are 
> as relevant as the multicast/unicast difference already discussed, in 
> similar detail.
>
> Joe
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html



From mrex@sap.com  Tue Jul 12 15:51:22 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 D12C821F8B56 for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 15:51:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.86
X-Spam-Level: 
X-Spam-Status: No, score=-9.86 tagged_above=-999 required=5 tests=[AWL=0.233,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17f2kOJBE9dl for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 15:51:22 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 1BCB321F8B55 for <ietf@ietf.org>; Tue, 12 Jul 2011 15:51:21 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p6CMpKxw024317 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 13 Jul 2011 00:51:20 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201107122251.p6CMpJC6002069@fs4113.wdf.sap.corp>
Subject: Re: Repetitions and consensus
To: brian.e.carpenter@gmail.com (Brian E Carpenter)
Date: Wed, 13 Jul 2011 00:51:19 +0200 (MEST)
In-Reply-To: <4E1BB856.7040601@gmail.com> from "Brian E Carpenter" at Jul 12, 11 02:58:30 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: Tue, 12 Jul 2011 22:51:22 -0000

Brian E Carpenter wrote:
> 
> We quite often discuss here how to judge rough consensus.

That issue turns up most of the time in inappropriate situations.

I regularly see folks _counting_ opinions when issues have been raised
instead of actually resolving the issues.  As previously said,
the most important thing is to drill down and sort out matters of
personal taste from issues are technical or procedural.

Matters of personal taste can be settled by signficant majority,
and "rough" applies almost exclusively to issues of personal taste.

Technical and procedural issues need to be addressed with an issue
resolution process, where alternatives are seriously evaluated.


Here is a snipped from an IESG response to an appeal:

                                                       However, several
  ADs felt that the issue was technical, not stylistic, thus the IESG
  as a whole did not have consensus that the issue was non-technical in
  this case.

Trying to gauge "(rough) consensus" by counting voiced opinions when an
issue has not been reliably determined to be non-technical and
non-procedural _is_ inappropriate.  At least that is what I believe
that the IESG thought a couple of years ago.


-Martin

From randy@qualcomm.com  Tue Jul 12 16:12:31 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 D61CF21F8C5E for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 16:12:31 -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 CSOeoUv2WgSt for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 16:12:27 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 3A0CD21F8C5D for <ietf@ietf.org>; Tue, 12 Jul 2011 16:12:27 -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=1310512347; x=1342048347; 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<p0624064fca428419c7be@loud.pensive.org> |In-Reply-To:=20<CAC4RtVBGgk74VMEty9u5Yq+DFy=3DoR5tOnbZ3R 5x83Gyee6mRNw@mail.gmail.com>|References:=20<CAC4RtVBGgk7 4VMEty9u5Yq+DFy=3DoR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> |X-Mailer:=20Eudora=20for=20Mac=20OS=20X|Date:=20Tue,=201 2=20Jul=202011=2016:12:12=20-0700|To:=20Barry=20Leiba=20< barryleiba@computer.org>,=20IETF=20discussion=20list=0D =0A=09<ietf@ietf.org>|From:=20Randall=20Gellens=20<randy@ qualcomm.com>|Subject:=20Re:=20Confidentiality=20notices =20on=20email=20messages|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.48.1]; bh=DjYmFK9/eXcfOCPhMPYuVGMw+AwRqKQy3ZuJATSq//4=; b=nbYISRrgrEARPgmvrnpDNNbfdtH958hSOmcefIg6iSSCNaZgl+hEzhOt UhR77SCf/7aAU/WwpvNmrGy7G5CBfjuY2ThLw8CDY7xY6pfKfKR9Wqi7l IbKvfEWtBa9MJtctZuKQ4hx5blIWowcYgGIRivtzZo6pvIgkRRIuVeOmU Y=;
X-IronPort-AV: E=McAfee;i="5400,1158,6405"; a="103152515"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine02.qualcomm.com with ESMTP; 12 Jul 2011 16:12:27 -0700
X-IronPort-AV: E=Sophos;i="4.65,521,1304319600"; d="scan'208";a="85852005"
Received: from nasanexhc05.na.qualcomm.com ([172.30.48.2]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 12 Jul 2011 16:12:26 -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.323.0; Tue, 12 Jul 2011 16:12:25 -0700
Message-ID: <p0624064fca428419c7be@loud.pensive.org>
In-Reply-To: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com>
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com>
X-Mailer: Eudora for Mac OS X
Date: Tue, 12 Jul 2011 16:12:12 -0700
To: Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: Confidentiality notices on email messages
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, 12 Jul 2011 23:12:32 -0000

Barry,

I'm not a lawyer and I don't play one on TV or the net, so I likely 
don't understand the situation.  As a point of possibly interesting 
information, once upon a time, at a training session held by a lawyer 
regarding how to protect confidential information, we were admonished 
not to slap a "confidential" label on anything automatically or 
without consideration, because, we were warned, doing so can cause 
the label to lose meaning for everything.  In other words, if we 
labelled everything "confidential," then we were really saying 
nothing was confidential.

Ever since, I've wondered if these notices were set up by someone who 
is a lawyer and does understand the situation, or if they were set up 
by someone who saw others do it, or heard that this sort of thing was 
needed.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
I always avoid prophesying beforehand, because it is a much better
policy to prophesy after the event has already taken place.
    --Winston Churchill

From housley@vigilsec.com  Tue Jul 12 16:44:35 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 8076711E8085 for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 16:44: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=[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 WoHzljn0HXP6 for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 16:44:34 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id B2A2711E8073 for <ietf@ietf.org>; Tue, 12 Jul 2011 16:44:34 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 535CEF240C0 for <ietf@ietf.org>; Tue, 12 Jul 2011 19:44:52 -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 ImSsuu4rS4Go for <ietf@ietf.org>; Tue, 12 Jul 2011 19:44:31 -0400 (EDT)
Received: from [192.168.2.102] (pool-96-255-45-210.washdc.fios.verizon.net [96.255.45.210]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 3AFD5F240B8 for <ietf@ietf.org>; Tue, 12 Jul 2011 19:44:51 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Last Call: <draft-yevstifeyev-ion-report-06.txt> (Report on the Experiment with IETF Operational Notes (IONs)) to Informational RFC
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4E1CC89E.7010907@gmail.com>
Date: Tue, 12 Jul 2011 19:44:32 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2AE25919-69DA-4226-AB14-301AA7C9446E@vigilsec.com>
References: <20110712143944.20141.23357.idtracker@ietfa.amsl.com> <4E1C7B48.4070000@gmail.com> <4E1CC89E.7010907@gmail.com>
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: Tue, 12 Jul 2011 23:44:35 -0000

+1

I also disagree with some of the statements in the proposed text.  I do =
not think it is worth the effort to come up with consensus text.

Russ


On Jul 12, 2011, at 6:20 PM, Brian E Carpenter wrote:

> Mykyta,
>=20
> I think the draft is fine without this addition, which contains some =
statements
> that I disagree with. I don't think analysis is needed; this all =
ancient history
> anyway.
>=20
> Regards
>   Brian
>=20
> On 2011-07-13 04:50, Mykyta Yevstifeyev wrote:
>> Hello,
>>=20
>> As Russ agreed to sponsor this document on I-D submission cut-off =
date,
>> I did make only some minor changed proposed by him during AD
>> evaluation.  However I thought the document would be incomplete =
without
>> analysis, so after LC I propose to add the following sub-section in =
the
>> draft:
>>=20
>>> 3.4. Analysis and Results
>>>=20
>>>   IONs were intended to serve as a means to document issues related =
to
>>>   procedures used by IETF or other parties, but to be more stable as =
a
>>>   simple web page and to have a more lightweight procedures for
>>>   approval than Best Current Practice (BCP) or other sort of RFC.  =
Even
>>>   though such middle-ground approach might be quite useful, it also
>>>   brings a number of complexities and negative effects, which are
>>>   described below.
>>>=20
>>>   First of all, IONs were mainly scoped to IETF procedural =
questions.
>>>   A number of IONs were published defining procedures used by IETF
>>>   community, such as ion-ad-sponsoring.  However, it should be noted
>>>   that the formal procedure of IONs approval, laid out in RFC 4693
>>>   [RFC4693] did not imply community involvement, unlike one for BCP =
or
>>>   other IETF Stream RFC.  Even though RFC 4693 intended IONs to =
cover
>>>   issues not sufficient for documenting in BCP, this regulation was
>>>   often overlooked.  This might have resulted in community non-
>>>   acceptance of such procedures, partial or full, if IONs were =
adopted
>>>   on the persistent basis.
>>>=20
>>>   Moreover, as IONs were lower in the hierarchy of IETF documents =
that
>>>   RFCs, published RFCs may override what mentioned in a particular =
ION
>>>   (whereas a published RFC may change already established =
procedures),
>>>   which might result in them not being sufficiently followed, =
creating
>>>   documentation conflicts.
>>>=20
>>>   Several IONS were published that describe the procedures used by =
IESG
>>>   or its members internally, such as ion-discuss-criteria or =
ion-tsv-
>>>   alt-cc.  Such material is obviously more appropriate for =
publication
>>>   as IESG Statements, which are also meant to be quite stable when
>>>   published and are approved at IESG's discretion.
>>>=20
>>>   A number of IONs were published covering different IAOC issues.  =
Such
>>>   IONs included ion-execd-tasks and ion-subpoena.  However, even =
though
>>>   IAOC works tightly with IETF, they have an ability to publish such
>>>   material on their site - <http://iaoc.ietf.org/>.
>>>=20
>>>   A one ION - ion-procdocs - was a reference guide to the IWTF =
Process
>>>   documents.  An other ION - ion-2026-practice - provided the =
criticism
>>>      and operational experience on RFC 2026 [RFC2026].  Both this
>>>   documents are fine as web pages, since the material contained in =
it
>>>   might change quickly and often.
>>>=20
>>>   ion-ion-format and ion-ion-store were published for the purpose of
>>>   the IONs series itself and were discarded upon experiment closure.
>>>   They are not analyzed here.
>>>=20
>>>   The aforementioned facts claim that IONs were less useful than the
>>>   equivalent information published in other way, and should be
>>>   abandoned, as proposed by Section 4 of RFC 4693 [RFC4693].
>>=20
>> In order not to request the 2nd LC after this text is included, I'd =
like
>> to seek community feedback on it during this Last Call.
>>=20
>> Thanks,
>> Mykyta Yevstifeyev
>>=20
>> 12.07.2011 17:39, The IESG wrote:
>>> The IESG has received a request from an individual submitter to =
consider
>>> the following document:
>>> - 'Report on the Experiment with IETF Operational Notes (IONs)'
>>>   <draft-yevstifeyev-ion-report-06.txt>  as an Informational RFC
>>>=20
>>> [ . . . ]
>>=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


From touch@isi.edu  Tue Jul 12 17:27:09 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 CB81921F85D9; Tue, 12 Jul 2011 17:27:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.669
X-Spam-Level: 
X-Spam-Status: No, score=-103.669 tagged_above=-999 required=5 tests=[AWL=-1.070, 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 j+phsR9Nj2hh; Tue, 12 Jul 2011 17:27:09 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 3DCA121F85CB; Tue, 12 Jul 2011 17:27:09 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id p6D0QiWp014059 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 12 Jul 2011 17:26:44 -0700 (PDT)
Message-ID: <4E1CE644.9090300@isi.edu>
Date: Tue, 12 Jul 2011 17:26:44 -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: stbryant@cisco.com
Subject: Re: notes from discussion of KARP design guidelines
References: <4E17210A.1070402@joelhalpern.com> <5662A966-70AD-4A63-BA31-8CE1C9635687@cisco.com> <4E1747BB.8080602@cisco.com> <4E19B2DC.4030003@joelhalpern.com> <4E1CC976.9000007@isi.edu> <4E1CCC76.9090409@cisco.com>
In-Reply-To: <4E1CCC76.9090409@cisco.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>, IETF discussion list <ietf@ietf.org>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 00:27:09 -0000

On 7/12/2011 3:36 PM, Stewart Bryant wrote:
> On 12/07/2011 23:23, Joe Touch wrote:
>> Hi, Joel (et al.),
>>
>> On 7/10/2011 7:10 AM, Joel Halpern wrote:
>>> Joe,
>>> THE KARP WG Chairs have reviewed your comments, in order to figure out
>>> what the best way to address them. We would appreciate it if you could
>>> engage in discussion of this proposal on the KARP working group email
>>> list. If you feel we are still not understanding your point, we would be
>>> happy to make some time avaialble for discussion at the WG session in
>>> Quebec City. (Comments from anyone else, particularly WG members, on the
>>> proposals being made by the WG chairs are appreciated as well.)
>>>
>>> Rather than a line by line response, we have tried to find the common
>>> themes and respond to them. If we have missed major issues, please let
>>> us know.
>>>
>>> You raised concern about the use of the term "on-the-wire." Rather than
>>> replace the term, we would prefer to add descriptive text early in the
>>> document. This text would note that it is a widely used term in IETF
>>> documents, including many RFCs. It would also state for clarity that in
>>> this document it is used to refer to the message sent from one routing
>>> process to another.
>>
>> That's a great example of why this term should be removed. The message
>> sent from one BGP to another is sent *inside* a TCP connection, and
>> nobody would ever call the TCP bytestream payload the message "on the
>> wire".
>>
>> This term is simply sloppy, and just as the security community rightly
>> raises issues with similarly poor use of its terms (e.g., "random"
>> where pseudorandom or arbitrary are intended, or "authenticated" where
>> integrity protection is intended), I consider this a *significant*
>> transport issue.
>
> Joe
>
> Please can you suggest a suitable generic term that covers the
> set of cases that we need to deal with in routing - i.e.
> over the MAC, over IP, over UDP and over TCP, so that we can
> discuss inter routing entity message passing as an abstract
> operation.
>
> As Joel says when we get to the detailed design of each routing
> protocol we will discuss the details, but we want a high level
> discussion in this document.
>
> Note BTW that 186 RFCs use the term "on the wire" in this
> sort of situation.

I counted nearly 210, when including "over the wire" too. There are 
similar misuses of, e.g., security terms, though, so let's not let past 
errors suggest continued use.

That said, let's proceed:

First, when you say "on the wire" do you mean:

	(A)- the routing protocol data units (RPDUs)

	(B)- way in which RPDUs are exchanged
		this includes message payloads, meta-info
		(header information), and any other info
		at other layers beyond RPDUs that the routing
		protocol uses or relies upon

I'm presuming the term "on the wire" is intended to differentiate 
between (A) and (B).

There's no good way to describe (B) as a single entity because it's not 
one. You basically are differentiating between the message and the means 
of its communication. The latter is often called a 'channel' in other 
contexts, so maybe that's the term you want - a way to protect the 
'channel'.

Joe






From jdfalk-lists@cybernothing.org  Tue Jul 12 18:33:16 2011
Return-Path: <jdfalk-lists@cybernothing.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 A478C21F8B33 for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 18:33:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zq30--dkPNzX for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 18:33:16 -0700 (PDT)
Received: from ocelope.disgruntled.net (ocelope.disgruntled.net [97.107.131.76]) by ietfa.amsl.com (Postfix) with ESMTP id 09AF321F8606 for <ietf@ietf.org>; Tue, 12 Jul 2011 18:33:15 -0700 (PDT)
Received: from [192.168.11.36] (c-76-126-154-212.hsd1.ca.comcast.net [76.126.154.212]) (authenticated bits=0) by ocelope.disgruntled.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p6D1XDAo011499 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Tue, 12 Jul 2011 18:33:15 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Confidentiality notices on email messages
From: "J.D. Falk" <jdfalk-lists@cybernothing.org>
In-Reply-To: <p0624064fca428419c7be@loud.pensive.org>
Date: Tue, 12 Jul 2011 18:33:12 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <1D49B15C-643F-4D05-92BE-E42A309341CF@cybernothing.org>
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <p0624064fca428419c7be@loud.pensive.org>
To: IETF list <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: Wed, 13 Jul 2011 01:33:16 -0000

On Jul 12, 2011, at 4:12 PM, Randall Gellens wrote:

> Ever since, I've wondered if these notices were set up by someone who =
is a lawyer and does understand the situation, or if they were set up by =
someone who saw others do it, or heard that this sort of thing was =
needed.

The latter seems likely to me as well, but the IETF community is =
unlikely to convince such people to change their minds.  It's certain to =
be far easier, in this case, to gently encourage participants to use a =
different email address for their IETF participation.

(I do that already -- not because of inappropriate footers, but because =
Exchange and Outlook are mind-bogglingly poor tools for discussion =
lists.)

--
J.D. Falk
the leading purveyor of industry counter-rhetoric solutions


From hsantos@isdg.net  Tue Jul 12 19:22:14 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 82DD721F8BF2 for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 19:22:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.53
X-Spam-Level: 
X-Spam-Status: No, score=-4.53 tagged_above=-999 required=5 tests=[AWL=-1.931,  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 8Ohb40eoIlwB for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 19:22:09 -0700 (PDT)
Received: from ntbbs.winserver.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 1E5C421F8BF4 for <ietf@ietf.org>; Tue, 12 Jul 2011 19:22:04 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple; l=2738; t=1310523717; h=Message-ID:Date:From:Organization:To: Subject; bh=OYM6jlONH7CMRjSKKvVHfUdeKiU=; b=d40Q9fgzFhe31SmdcSO5 PN0H7bijmLe5ow7kBftwyTwzvbvBaIuX/I+hmRa42no5ENPaeVgHBprTmemi1FTa gBAoEN/RTnP4vjKrQ+WsyYSlKbIOoJoS/ESHujlQTt1Y3IpfJkiNlJXzb7bc90cO Z3zx7TKwnLFoKTbFPWs5ym0=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Tue, 12 Jul 2011 22:21:57 -0400
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 3274189422.1744.3148; Tue, 12 Jul 2011 22:21:55 -0400
Received: by beta.winserver.com (Wildcat! SMTP Router v6.3.453.2) for ietf@ietf.org; Tue, 12 Jul 2011 22:17:57 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.3.453.2) with ESMTP id 4245483142; Tue, 12 Jul 2011 22:17:56 -0400
Message-ID: <4E1D0142.90504@isdg.net>
Date: Tue, 12 Jul 2011 22:21:54 -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: Randall Gellens <randy@qualcomm.com>
Subject: Re: Confidentiality notices on email messages
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <p0624064fca428419c7be@loud.pensive.org>
In-Reply-To: <p0624064fca428419c7be@loud.pensive.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Barry Leiba <barryleiba@computer.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, 13 Jul 2011 02:22:14 -0000

Randall Gellens wrote:
> Barry,
> 
> I'm not a lawyer and I don't play one on TV or the net, so I likely 
> don't understand the situation.  As a point of possibly interesting 
> information, once upon a time, at a training session held by a lawyer 
> regarding how to protect confidential information, we were admonished 
> not to slap a "confidential" label on anything automatically or without 
> consideration, because, we were warned, doing so can cause the label to 
> lose meaning for everything.  In other words, if we labelled everything 
> "confidential," then we were really saying nothing was confidential.
> 
> Ever since, I've wondered if these notices were set up by someone who is 
> a lawyer and does understand the situation, or if they were set up by 
> someone who saw others do it, or heard that this sort of thing was needed.

Depending on the organization, it may be a legally required especially 
if it is public stock company.  It is also legally required to make an 
explicit statement in order to have stronger enforcement when push 
comes to shove, i.e. ignorance can not be claimed.   There is also a 
difference in PUBLIC vs PRIVATE communications and while it is more 
important to have disclaimers when public, unless an explicit 
statement is also made in private, it can not be assumed.  A good 
example is a private message send to someone and he/she makes it 
public. In tort cases, the receiver has to right to make it public if 
and only if the author did not make an explicit statement that it 
remains private and the guideline is to make it the very first 
statement:  THIS IS A PRIVATE MESSAGE AND THE INTENTION IS THAT IT 
REMAINS PRIVATE. MAKING THIS MESSAGE PUBLIC WILL VIOLATE US EPCA "User 
Privacy Expectation" PROVISIONS.

IMV, the IETF will be opening up a can of worms if they begin to cite 
legal conflicts with the NOTE WELL statement and if its suggested that 
participants use external addresses in order to participate without 
conflict, well, even if people took the advice, it may put the person 
in some legal conflict with his corporate employer. e.g.  just because 
a person moonlights in some other activity, does not necessary mean 
they are free from company employment contracts and if there is any 
kind of relationship of his external activities with his normal work, 
they might want him to use a corporate identity or not. I guess it all 
depends how much of a hard ass is his boss, employer or their chief 
counsel.  You might find if the IETF is making a fuss, they may ask 
the employee to just not participate - lurk, but don't post.

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com




From evnikita2@gmail.com  Tue Jul 12 19:45:49 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 B8CE721F8B21 for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 19:45:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.504
X-Spam-Level: 
X-Spam-Status: No, score=-3.504 tagged_above=-999 required=5 tests=[AWL=0.095,  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 QKVynvgFNNcf for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 19:45:49 -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 F28BB21F89EF for <ietf@ietf.org>; Tue, 12 Jul 2011 19:45:48 -0700 (PDT)
Received: by fxe4 with SMTP id 4so6964005fxe.27 for <ietf@ietf.org>; Tue, 12 Jul 2011 19:45:48 -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=MET2tbbnnE6MPLzhGmRSvwtvpKelfaVaSspbHHz5Dd8=; b=TbLK1K/68O4eVtzkviOjfj8bZTK4XTZCTH+lDque5e53HhcUIXUL32iOi9U5MHkAL6 Jh0S5HGJi74B+zv7zQdgNLS9f5cGPU28PFXfg50r58DJQavytEk2up5SS6fSEOptTPyr EYfgl6iU9lusBDC7vYxGAwK5VEPDe8ZuKL6Ck=
Received: by 10.223.6.198 with SMTP id a6mr884785faa.128.1310525148084; Tue, 12 Jul 2011 19:45:48 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id k26sm10246183fak.0.2011.07.12.19.45.46 (version=SSLv3 cipher=OTHER); Tue, 12 Jul 2011 19:45:47 -0700 (PDT)
Message-ID: <4E1D0708.9090701@gmail.com>
Date: Wed, 13 Jul 2011 05:46:32 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-yevstifeyev-ion-report-06.txt> (Report on the Experiment with IETF Operational Notes (IONs)) to Informational RFC
References: <20110712143944.20141.23357.idtracker@ietfa.amsl.com> <4E1C7B48.4070000@gmail.com> <4E1CC89E.7010907@gmail.com>
In-Reply-To: <4E1CC89E.7010907@gmail.com>
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: Wed, 13 Jul 2011 02:45:49 -0000

13.07.2011 1:20, Brian E Carpenter wrote:
> Mykyta,
>
> I think the draft is fine without this addition, which contains some statements
> that I disagree with. I don't think analysis is needed; this all ancient history
> anyway.
Brian,

Let me explain why I'm planning to include this sub-section.  The 
current draft, after giving background, lists all IONs which were 
published.  Then it notifies the reader about de-facto closure of the 
experiment by IESG and provides information on what was done with IONs.  
Finally, there is a conclusion, which states that IONs were a bad idea.  
Such conclusion needs some basis, and will be unjustified without any 
analysis of why were IONs a bad idea.

If you have some objections/proposals, please feel free to express 
them.  I think we'll be able to find some consensus.

Mykyta Yevstifeyev
>
> Regards
>     Brian
>
> On 2011-07-13 04:50, Mykyta Yevstifeyev wrote:
>> Hello,
>>
>> As Russ agreed to sponsor this document on I-D submission cut-off date,
>> I did make only some minor changed proposed by him during AD
>> evaluation.  However I thought the document would be incomplete without
>> analysis, so after LC I propose to add the following sub-section in the
>> draft:
>>
>>> 3.4. Analysis and Results
>>>
>>> [ . . . ]
>>>
>>>     abandoned, as proposed by Section 4 of RFC 4693 [RFC4693].
>> In order not to request the 2nd LC after this text is included, I'd like
>> to seek community feedback on it during this Last Call.
>>
>> Thanks,
>> Mykyta Yevstifeyev
>>
>> 12.07.2011 17:39, The IESG wrote:
>>> The IESG has received a request from an individual submitter to consider
>>> the following document:
>>> - 'Report on the Experiment with IETF Operational Notes (IONs)'
>>>     <draft-yevstifeyev-ion-report-06.txt>   as an Informational RFC
>>>
>>> [ . . . ]
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>


From samirs.lists@gmail.com  Tue Jul 12 20:21:56 2011
Return-Path: <samirs.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 C530E11E80C2 for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 20:21:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.51
X-Spam-Level: 
X-Spam-Status: No, score=-1.51 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, J_CHICKENPOX_43=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 IVrNgBxyYMUz for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 20:21:52 -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 CFC2211E80EC for <ietf@ietf.org>; Tue, 12 Jul 2011 20:21:51 -0700 (PDT)
Received: by pvh18 with SMTP id 18so6122389pvh.31 for <ietf@ietf.org>; Tue, 12 Jul 2011 20:21:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=NqqUK+CP0vpqK8/3PzEVDsKNKkX+67Ehwvi+0kT/XWk=; b=uKEnY46aLUFvsOlPj0ExaPMZQVjEnlgbwfyoGqQ12OtV1qLE+7H2rP05QWbetKxAem ADLu6xYZnyIhFPURw01iFmBvOGFNQPP0PgfAWRgzzFGqXuEpK0og+pMgf82Jwrbmr7nB IfgxC8ybIsFOdBA+9Y+3cMQwc6T1wXIgHqrKo=
MIME-Version: 1.0
Received: by 10.68.68.98 with SMTP id v2mr743972pbt.487.1310527310966; Tue, 12 Jul 2011 20:21:50 -0700 (PDT)
Received: by 10.68.52.195 with HTTP; Tue, 12 Jul 2011 20:21:50 -0700 (PDT)
Date: Tue, 12 Jul 2011 20:21:50 -0700
Message-ID: <CAK+Spiz3O_b16MZ=BoFyht38DqZsMena6_cZZ5CcaN9mGxpwBA@mail.gmail.com>
Subject: Call for opinion on impact of cashless economy on 'Security Consideration'
From: Samir Srivastava <samirs.lists@gmail.com>
To: ietf@ietf.org, postmaster@nobel.no, vk@khoslaventures.com,  desk@abcnews4.com
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, 13 Jul 2011 03:21:56 -0000

Hi, Readers use information given in this message at thier own risk.
Author cannot be held responsible for damages/consequences caused.
Refer http://samirsrivastava.typepad.com. Search wipo.int for patents
by me. Work has potential to impact security consideration of IETF
docs.  Awarding a prize is in the sole discretion of awarding
organization.Yet nobel peace prize to US President not clear. He was
awarded it for diplomacy within a year after becoming President. I
sent slide set on cashless economy to khosla ventures in 2007. When I
posted on alt.security.terrorism on nov-28-10, president went on
surprise trip to Afganistan. I suspect it is used for someting else
also. Due to various reasons referred work is not able to draw
attention from media and governments. I request parties mentioned on
email to clarify doubts on public forum. I request IETEers to review
it. BTW outstanding work of nobel winners is well known in advance.
Due to unavoidable situations I cannot submit draft.  Regards  Samir
Srivastava

From samirs.lists@gmail.com  Tue Jul 12 20:42:11 2011
Return-Path: <samirs.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 6349121F8553 for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 20:42:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.255
X-Spam-Level: 
X-Spam-Status: No, score=-2.255 tagged_above=-999 required=5 tests=[AWL=0.745,  BAYES_00=-2.599, J_CHICKENPOX_43=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 TL6K2ZITTJ3e for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 20:42:06 -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 A8F4621F854E for <ietf@ietf.org>; Tue, 12 Jul 2011 20:42:06 -0700 (PDT)
Received: by pvh18 with SMTP id 18so6137299pvh.31 for <ietf@ietf.org>; Tue, 12 Jul 2011 20:42:06 -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=kO4ldLhB/eS7kLr5gSACPUesGCBiXumM0KvP1T/Z6hA=; b=ezNILxI8K5ixwa88pAyH0ELaKX6pxCzWjN2S976xDAyIY/0QbidB1qO9rT5YHhk+tA mW+WXAAnUUvz6gEw9ZYvMPOYQ9rZoxbqvkVDa6F4EH/N8hSXp5UsbpoGMev4qfIpsfUf 3+EO8wMmhGryL028Zs/eVZyrm9syb0+27m9zA=
MIME-Version: 1.0
Received: by 10.68.58.103 with SMTP id p7mr830953pbq.219.1310528525659; Tue, 12 Jul 2011 20:42:05 -0700 (PDT)
Received: by 10.68.52.195 with HTTP; Tue, 12 Jul 2011 20:42:05 -0700 (PDT)
In-Reply-To: <CAK+Spiz3O_b16MZ=BoFyht38DqZsMena6_cZZ5CcaN9mGxpwBA@mail.gmail.com>
References: <CAK+Spiz3O_b16MZ=BoFyht38DqZsMena6_cZZ5CcaN9mGxpwBA@mail.gmail.com>
Date: Tue, 12 Jul 2011 20:42:05 -0700
Message-ID: <CAK+SpizC2EaT8rogpeGHTzdua-DhEGd-DC_jqv55Z3Qu4kLd4w@mail.gmail.com>
Subject: Re: Call for opinion on impact of cashless economy on 'Security Consideration'
From: Samir Srivastava <samirs.lists@gmail.com>
To: ietf@ietf.org, postmaster@nobel.no, vk@khoslaventures.com,  desk@abcnews4.com, dw@khoslaventures.com, assignment@aajtak.com
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, 13 Jul 2011 03:42:11 -0000

Added more on the distribution list regards  Samir Srivastava

On 7/12/11, Samir Srivastava <samirs.lists@gmail.com> wrote:
> Hi, Readers use information given in this message at thier own risk.
> Author cannot be held responsible for damages/consequences caused.
> Refer http://samirsrivastava.typepad.com. Search wipo.int for patents
> by me. Work has potential to impact security consideration of IETF
> docs.  Awarding a prize is in the sole discretion of awarding
> organization.Yet nobel peace prize to US President not clear. He was
> awarded it for diplomacy within a year after becoming President. I
> sent slide set on cashless economy to khosla ventures in 2007. When I
> posted on alt.security.terrorism on nov-28-10, president went on
> surprise trip to Afganistan. I suspect it is used for someting else
> also. Due to various reasons referred work is not able to draw
> attention from media and governments. I request parties mentioned on
> email to clarify doubts on public forum. I request IETEers to review
> it. BTW outstanding work of nobel winners is well known in advance.
> Due to unavoidable situations I cannot submit draft.  Regards  Samir
> Srivastava
>

From huubatwork@gmail.com  Tue Jul 12 23:22:15 2011
Return-Path: <huubatwork@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE26C21F8B38 for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 23:22:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.592
X-Spam-Level: 
X-Spam-Status: No, score=-3.592 tagged_above=-999 required=5 tests=[AWL=0.007,  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 ISFNl7eRz4IA for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 23:22:14 -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 9C9DE21F8B34 for <ietf@ietf.org>; Tue, 12 Jul 2011 23:22:14 -0700 (PDT)
Received: by eye13 with SMTP id 13so2305225eye.31 for <ietf@ietf.org>; Tue, 12 Jul 2011 23:22:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:disposition-notification-to:date:from:reply-to :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=XFU2HkwqX02iM5iit7t7OVqjlVQlAmCr7Cr2UA+WB74=; b=p+1ypvPpI93WZjDcA8ClHieTY5g1RMBM8+Fwi4ynO5QWzK2WZood0JYnUYKDbu1EZi PJd9owuLkWRmHnXR026rURYBgOunZaSy1Gx2/7irPcOILCAE5bgfc7yYDMfOJNuj1mOa mi8EKNQPY1H5tsHQBrCGMVeCuvNeerOa8ESqg=
Received: by 10.213.34.143 with SMTP id l15mr1127734ebd.0.1310538133065; Tue, 12 Jul 2011 23:22:13 -0700 (PDT)
Received: from McAsterix.local (dhcp-077-250-051-060.chello.nl [77.250.51.60]) by mx.google.com with ESMTPS id z49sm1762768eef.33.2011.07.12.23.22.11 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Jul 2011 23:22:12 -0700 (PDT)
Message-ID: <4E1D3992.4080206@gmail.com>
Date: Wed, 13 Jul 2011 08:22:10 +0200
From: Huub van Helvoort <huubatwork@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Confidentiality notices on email messages
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com>	<CAP0PwYYmLxPSoPvUqYOO_y=Hdn9vBSTRC5ax4wnjzE1SD1+aLg@mail.gmail.com> <CAC4RtVCwbCsj5vH5UwxWYEpJnAZePRr5HWyLFJ6t1U=_gXfODQ@mail.gmail.com>
In-Reply-To: <CAC4RtVCwbCsj5vH5UwxWYEpJnAZePRr5HWyLFJ6t1U=_gXfODQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: huubatwork@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: Wed, 13 Jul 2011 06:22:15 -0000

Hello Barry,

You wrote:

> Hi, Jorge.
>
>> You may want to refer to Section 5.2 of RFC 5378, which addresses this
>> issue:
>>
>> "Each Contributor agrees that any statement in a Contribution, whether
>> generated automatically or otherwise, that states or implies that the
>> Contribution is confidential or subject to any privilege, can be disregarded
>> for all purposes, and will be of no force or effect."
>
> Yes, I'm aware of that.  My point was exactly that: that the
> confidentiality statement is pointless.  I'm asking people to try to
> get rid of them entirely.

It will also save energy, so it is good for the environment too.

BR, Huub.

From hannes.tschofenig@gmx.net  Wed Jul 13 02:21:13 2011
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DE1111E807B for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 02:21:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level: 
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kmee-uiwn7mC for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 02:21:12 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 6891B21F8B82 for <ietf@ietf.org>; Wed, 13 Jul 2011 02:21:11 -0700 (PDT)
Received: (qmail invoked by alias); 13 Jul 2011 09:21:09 -0000
Received: from letku214.adsl.netsonic.fi (EHLO [10.0.0.6]) [194.29.195.214] by mail.gmx.net (mp022) with SMTP; 13 Jul 2011 11:21:09 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/Sxk9L6DDSjoanm6RVX2j1PxXjT3oF0wV/bDn8Ht fniiqA4W+oCPnW
Subject: Re: Last Call: <draft-polk-local-emergency-rph-namespace-01.txt> (IANA Registering a SIP Resource Priority Header Field Namespace for Local Emergency Communications) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <20110615212629.9737.88852.idtracker@ietfa.amsl.com>
Date: Wed, 13 Jul 2011 12:21:08 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <64D47317-0D25-40FA-8D08-B256096660F1@gmx.net>
References: <20110615212629.9737.88852.idtracker@ietfa.amsl.com>
To: "ietf@ietf.org IETF" <ietf@ietf.org>, ecrit@ietf.org
X-Mailer: Apple Mail (2.1084)
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: Wed, 13 Jul 2011 09:21:13 -0000

Reading through the document I fail to see the clearly stated =
restriction that this is not to be used between the emergency caller's =
UA and the VSP/ASP's network (for VSP/ASP routed calls) or between the =
UA and the PSAP (for directly routed calls).=20
I was in the believe that the scope is restricted only to PSAP-to-first =
Responder, and PSAP-to-PSAP communication.=20

It might also be useful to add that this document did not make it =
through the ECRIT working group. The document type is Standards Track =
and might give the impression that there is wide consensus behind the =
document -- but there isn't. IETF last calls may add a lot of value but =
I do not see that anyone had pointed to the various discussions in the =
ECRIT mailing list on that topic.=20

I was always of the impression that the mechanism does not lead to any =
useful outcome. See previous discussions:=20
Hannes: http://www.ietf.org/mail-archive/web/ecrit/current/msg05940.html
Henning: =
http://www.ietf.org/mail-archive/web/ecrit/current/msg05941.html
JamesW: http://www.ietf.org/mail-archive/web/ecrit/current/msg05945.html

For those who have not followed the work I would like to point out that =
we have an "marking" (or call it indication) of an emergency call =
already, it is called a Service URN - RFC 5031. How many times do we =
need to again identify that a call (or a message) is an emergency call?=20=


The document interestingly talks about closed networks or controlled =
environments where this is supposed to be used. I don't believe it is =
useful to do so because this leaves the door open to use the mechanism =
anywhere. Often, these networks are not as closed as we think.=20

  This new namespace can be included in SIP requests to provide an
   explicit priority indication within controlled environments, such as
   an IMS infrastructure or Emergency Services network (ESInet) where
   misuse can be reduced to a minimum because these types of networks
   have great controls in place.

Btw, what are these >>great<< controls?=20

My comments are addressed if the document (in the introduction) makes it =
clear that UAs' MUST NOT include this  RP namespace in an outgoing =
emergency call because there is already the Service URN marking that =
classifies the call as an emergency call.=20
We had already agreed on this a long time ago, see =
http://www.ietf.org/mail-archive/web/ecrit/current/msg05960.html. Still, =
the text in the introduction and in the security consideration is very =
fuzzy and in my view intentionally does not make the case clear to leave =
it up to interpretation.=20

It is ironic that this document manages to get finished before the major =
work of the ECRIT group, namely PhoneBCP, and ECRIT framework, get =
completed. (Or the SIPCORE SIP location conveyance for that matter as =
well.)=20
Why would someone want to go with their work through a working group =
when they can get a Standards Track document faster and easier?=20

Ciao
Hannes

On Jun 16, 2011, at 12:26 AM, The IESG wrote:

>=20
> The IESG has received a request from an individual submitter to =
consider
> the following document:
> - 'IANA Registering a SIP Resource Priority Header Field Namespace for
>   Local Emergency Communications'
>  <draft-polk-local-emergency-rph-namespace-01.txt> as a Proposed
> Standard
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2011-07-13. Exceptionally, comments may =
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>   This document creates the new Session Initiation Protocol (SIP)
>   Resource Priority header field namespace "esnet" for local emergency
>   usage to a public safety answering point (PSAP), between PSAPs, and
>   between a PSAP and first responders and their organizations, and
>   places this namespace in the IANA registry.
>=20
>=20
>=20
>=20
> The file can be obtained via
> =
http://datatracker.ietf.org/doc/draft-polk-local-emergency-rph-namespace/
>=20
> IESG discussion can be tracked via
> =
http://datatracker.ietf.org/doc/draft-polk-local-emergency-rph-namespace/
>=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


From mnot@mnot.net  Wed Jul 13 04:36:12 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 8EDFC21F8B62 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 04:36:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.82
X-Spam-Level: 
X-Spam-Status: No, score=-105.82 tagged_above=-999 required=5 tests=[AWL=-3.221, 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 eJW5Yg1jAhaM for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 04:36:07 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id A526821F87FA for <ietf@ietf.org>; Wed, 13 Jul 2011 04:36:07 -0700 (PDT)
Received: from chancetrain-lm.mnot.net (unknown [118.209.151.171]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id C008350A56; Wed, 13 Jul 2011 07:36:00 -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: <4E1CA248.7060009@stpeter.im>
Date: Wed, 13 Jul 2011 21:35:57 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <3110098B-5515-4E7A-84A4-522925593FA2@mnot.net>
References: <11CBFBA2-434B-43FC-90C4-DADBACB49226@mnot.net> <4E1CA248.7060009@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1084)
Cc: "ietf@ietf.org IETF" <ietf@ietf.org>, 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, 13 Jul 2011 11:36:12 -0000

Personally, I think Informational is most appropriate (and probably =
easier), but a paragraph or two of context, as well as corresponding =
adjustments, would work as well.=20

Cheers,


On 13/07/2011, at 5:36 AM, Peter Saint-Andre wrote:

> On 6/21/11 11:08 PM, Mark Nottingham wrote:
>> 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
> How about publishing it on the standards track but not as a general
> mechanism (i.e., why not clarify when it is and is not appropriate)?
>=20
> Clearly, both service providers (Google, Yahoo, etc.) and spec authors
> (draft-hardjono-oauth-dynreg-00, draft-hardjono-oauth-umacore-00) have
> found hostmeta somewhat useful in certain contexts.
>=20
> RFC 2026 says:
>=20
>   A Proposed Standard specification is generally stable, has resolved
>   known design choices, is believed to be well-understood, has =
received
>   significant community review, and appears to enjoy enough community
>   interest to be considered valuable.
>=20
> and:
>=20
>   Usually, neither implementation nor operational experience is
>   required for the designation of a specification as a Proposed
>   Standard.  However, such experience is highly desirable, and will
>   usually represent a strong argument in favor of a Proposed Standard
>   designation.
>=20
> The spec seems to be stable at this point, it's received significant
> review, people seem to understand what it does and how it works, it's
> had both implementation and operational experience, and it appears to
> enjoy enough community interest to be considered valuable in certain
> contexts. I also think it has resolved the design choices and solved =
the
> requirements that it set out to solve, although you might be right =
that
> it doesn't solve all of the problems that a more generic metadata
> framework would need to solve.
>=20
> As a result, it seems like a fine candidate for Proposed Standard, =
i.e.,
> an entry-level document on the standards track that might be modified =
or
> even retracted based on further experience.
>=20
>> 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.=20
>=20
> Again, perhaps we need to clarify that it is not necessarily a general
> component of the web architecture, although it can be used to solve =
more
> specific problems.
>=20
>> 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
>>=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
> As discussed in responses to your message, XRD seems to have been an
> appropriate tool for the job in this case. Whether XRD, too, is really =
a
> general component of the web architecture is another question.
>=20
>> * 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
> That could be something to work on if and when folks try to advance =
this
> technology to the next maturity level (currently Draft Standard).
>=20
>> * Scope of hosts -- The document doesn't crisply define what a "host"
>> is.
>=20
> This seems at least somewhat well-defined:
>=20
>   a "host" is not a single resource but the entity
>   controlling the collection of resources identified by Uniform
>   Resource Identifiers (URI) with a common URI host [RFC3986].
>=20
> That is, it references Section 3.2.2 of RFC 3986, which defines "host"
> with some precision (albeit perhaps not "crisply").
>=20
>> * 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
> It would be helpful to hear from folks who have deployed hostmeta to
> hear if they have run into any operational issues of the kind you
> describe here.
>=20
>> * 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.
>>=20
>> 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
> That sounds like good input to a more generic approach. Many discovery
> protocols do seem to have an inherent chattiness about them, but you
> might be right that ideally the round trips could be kept to a =
minimum.
>=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.
>=20
> Again, I think some clarifying language about the applicability of the
> technology is in order.
>=20
>> 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.
>=20
> And my apologies for taking so long to reply.
>=20
> Peter
>=20
> --=20
> Peter Saint-Andre
> https://stpeter.im/
>=20
>=20

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




From mcr@sandelman.ca  Wed Jul 13 06:50:56 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 DD08821F890F for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 06:50:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.375
X-Spam-Level: 
X-Spam-Status: No, score=-0.375 tagged_above=-999 required=5 tests=[AWL=0.090,  BAYES_05=-1.11, 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 RbziOSsnV643 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 06:50:51 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 7F4F621F8789 for <ietf@ietf.org>; Wed, 13 Jul 2011 06:50:51 -0700 (PDT)
Received: from marajade.sandelman.ca (unknown [132.213.238.4]) by relay.sandelman.ca (Postfix) with ESMTPS id C0A28340B2; Wed, 13 Jul 2011 09:50:39 -0400 (EDT)
Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 0DEDC98AC2; Wed, 13 Jul 2011 09:50:58 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Confidentiality notices on email messages
In-Reply-To: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com>
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Wed, 13 Jul 2011 09:50:58 -0400
Message-ID: <29987.1310565058@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 13:50:56 -0000

Barry, I think that we should put a filter on the ietf.org that bounces
all messages with confidentiality notices.

I also think that we should enforce 77 columns max for text/plain when
there is no "format=flowed" option in the Content-Type.

-- 
]       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 barryleiba.mailing.lists@gmail.com  Wed Jul 13 07:48:48 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 2DE6811E80B6 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 07:48:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.148
X-Spam-Level: 
X-Spam-Status: No, score=-103.148 tagged_above=-999 required=5 tests=[AWL=-0.171, 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 MbFharlUs6Ry for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 07:48:47 -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 8F60411E8082 for <ietf@ietf.org>; Wed, 13 Jul 2011 07:48:47 -0700 (PDT)
Received: by ywp31 with SMTP id 31so2112353ywp.31 for <ietf@ietf.org>; Wed, 13 Jul 2011 07:48:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=XoKLSZkQoJ2gcKM7Lg+wPbA31Q+PibLeiZx7e25gCtE=; b=lzoS9lI70X1/eS7nVS5C1k64onmSO/nOd/zcoOzp2eWxTK8ESTDE/sVDb2e5hZV8Ec HLEi1WatlNcv+O3WTNjigSEnqvo/BA2+FXCgGiBxm8FEw6uEXllmi21vl750CMgDjshP 0qvzR4VyR/+B9XWODypPT6mtL3EeSx/z3hd2I=
MIME-Version: 1.0
Received: by 10.236.191.33 with SMTP id f21mr1550350yhn.431.1310568527148; Wed, 13 Jul 2011 07:48:47 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.172.10 with HTTP; Wed, 13 Jul 2011 07:48:47 -0700 (PDT)
In-Reply-To: <4E1D0708.9090701@gmail.com>
References: <20110712143944.20141.23357.idtracker@ietfa.amsl.com> <4E1C7B48.4070000@gmail.com> <4E1CC89E.7010907@gmail.com> <4E1D0708.9090701@gmail.com>
Date: Wed, 13 Jul 2011 10:48:47 -0400
X-Google-Sender-Auth: XoI70utzuKAr7hN-xLTwXICTAbA
Message-ID: <CAC4RtVBvfgmJ3JOB6ZTYrWrQYarwbN7uYTi7XmdVS29BjG7PUw@mail.gmail.com>
Subject: Re: Last Call: <draft-yevstifeyev-ion-report-06.txt> (Report on the Experiment with IETF Operational Notes (IONs)) to Informational RFC
From: Barry Leiba <barryleiba@computer.org>
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 14:48:48 -0000

> Let me explain why I'm planning to include this sub-section.

Why?  Your explanation lacks substance, and further effort here is a
waste of time.

The document as it stands is just fine, except for one sentence that
needs rewording to make sense in English:

OLD
All IONs were republished whether as IESG statements, Web Pages, or
were discarded.

NEW
All IONs were republished as IESG statements, republished as Web Pages,
or discarded.


The document says everything it needs to say.  Let's publish it as it
is, and not spend more time trying to argue or explain anything.

Barry

From stpeter@stpeter.im  Wed Jul 13 07:52:24 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 0A85121F873D for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 07:52:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.71
X-Spam-Level: 
X-Spam-Status: No, score=-102.71 tagged_above=-999 required=5 tests=[AWL=-0.111, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yNRVQj8cae8H for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 07:52:23 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id E07CD21F8761 for <ietf@ietf.org>; Wed, 13 Jul 2011 07:52:12 -0700 (PDT)
Received: from leavealone.cisco.com (unknown [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 628B3410E8; Wed, 13 Jul 2011 08:52:35 -0600 (MDT)
Message-ID: <4E1DB11A.1020607@stpeter.im>
Date: Wed, 13 Jul 2011 08:52:10 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Last Call: <draft-yevstifeyev-ion-report-06.txt> (Report on the Experiment with IETF Operational Notes (IONs)) to Informational RFC
References: <20110712143944.20141.23357.idtracker@ietfa.amsl.com> <4E1C7B48.4070000@gmail.com> <4E1CC89E.7010907@gmail.com> <4E1D0708.9090701@gmail.com> <CAC4RtVBvfgmJ3JOB6ZTYrWrQYarwbN7uYTi7XmdVS29BjG7PUw@mail.gmail.com>
In-Reply-To: <CAC4RtVBvfgmJ3JOB6ZTYrWrQYarwbN7uYTi7XmdVS29BjG7PUw@mail.gmail.com>
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
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: Wed, 13 Jul 2011 14:52:24 -0000

On 7/13/11 8:48 AM, Barry Leiba wrote:

> The document says everything it needs to say.  Let's publish it as it
> is, and not spend more time trying to argue or explain anything.

+1


From ajs@anvilwalrusden.com  Wed Jul 13 07:53:56 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 EBBB711E80C7 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 07: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.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 nXHCP5yEmED3 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 07:53:56 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 66C5E11E808F for <ietf@ietf.org>; Wed, 13 Jul 2011 07:53:56 -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 628631ECB41D for <ietf@ietf.org>; Wed, 13 Jul 2011 14:53:54 +0000 (UTC)
Date: Wed, 13 Jul 2011 10:53:43 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Confidentiality notices on email messages
Message-ID: <20110713145343.GA11135@shinkuro.com>
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <CAP0PwYYmLxPSoPvUqYOO_y=Hdn9vBSTRC5ax4wnjzE1SD1+aLg@mail.gmail.com> <CAC4RtVCwbCsj5vH5UwxWYEpJnAZePRr5HWyLFJ6t1U=_gXfODQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAC4RtVCwbCsj5vH5UwxWYEpJnAZePRr5HWyLFJ6t1U=_gXfODQ@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, 13 Jul 2011 14:53:57 -0000

On Tue, Jul 12, 2011 at 05:39:49PM -0400, Barry Leiba wrote:

> > "Each Contributor agrees that any statement in a Contribution, whether
> > generated automatically or otherwise, that states or implies that the
> > Contribution is confidential or subject to any privilege, can be disregarded
> > for all purposes, and will be of no force or effect."
> 
> Yes, I'm aware of that.  My point was exactly that: that the
> confidentiality statement is pointless.

Actually, given the policy, it's _not_ pointless.  It makes the
message "of no force or effect" and causes the participation by that
individual to be disregarded.  Surely nobody wants their contribution
to be disregarded because of a misguided rule on the part of someone
in their firm who doesn't understand the meaning of the words "public
mailing list".

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From housley@vigilsec.com  Wed Jul 13 07:59:52 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 E6BAB11E80FE for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 07:59:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 XtfQrrE3HDuD for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 07:59:49 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id F35AC11E808F for <ietf@ietf.org>; Wed, 13 Jul 2011 07:59:48 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 26920F2409D; Wed, 13 Jul 2011 11:00:13 -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 zh8fnu5GTAj6; Wed, 13 Jul 2011 10:59:38 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-45-210.washdc.fios.verizon.net [96.255.45.210]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 64B80F24031; Wed, 13 Jul 2011 11:00:12 -0400 (EDT)
Subject: Re: Last Call: <draft-iesg-rfc1150bis-01.txt> (Conclusion of FYI RFC	Sub-series) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4DF22E64.8030401@gmail.com>
Date: Wed, 13 Jul 2011 10:59:46 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F338BE21-F1CA-4712-8B5A-87F95EF79A9B@vigilsec.com>
References: <20110610131840.26851.83855.idtracker@ietfa.amsl.com> <4DF22E64.8030401@gmail.com>
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 14:59:53 -0000

Mykyta:

I don't think this debate has been advanced since the exchange on the =
rfc-interest list, and my response remains the same.

Russ


On Jun 10, 2011, at 10:47 AM, Mykyta Yevstifeyev wrote:

> 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.
>=20
> 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
>>=20
>> [ . . . ]


From petithug@acm.org  Wed Jul 13 09:38:46 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 339D321F8888 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 09:38:46 -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.080, 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 S5WUjqvBw2pt for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 09:38:45 -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 7E22421F887C for <ietf@ietf.org>; Wed, 13 Jul 2011 09:38:45 -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 13D4E2199E; Wed, 13 Jul 2011 18:37:16 +0200 (CEST)
Message-ID: <4E1DCA13.9030301@acm.org>
Date: Wed, 13 Jul 2011 09:38:43 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110626 Iceowl/1.0b2 Icedove/3.1.11
MIME-Version: 1.0
To: Michael Richardson <mcr@sandelman.ca>
Subject: Re: Confidentiality notices on email messages
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <29987.1310565058@marajade.sandelman.ca>
In-Reply-To: <29987.1310565058@marajade.sandelman.ca>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Barry Leiba <barryleiba@computer.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, 13 Jul 2011 16:38:46 -0000

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

On 07/13/2011 06:50 AM, Michael Richardson wrote:
> 
> Barry, I think that we should put a filter on the ietf.org that bounces
> all messages with confidentiality notices.

Yes, and perhaps disclaimers/confidentiality notices should be standardized with
their own MIME type to make automatic processing easier so receivers of this
kind of notice (mailing-list or other) can respect the wishes of the sender.

> 
> I also think that we should enforce 77 columns max for text/plain when
> there is no "format=flowed" option in the Content-Type.
> 


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

iEYEARECAAYFAk4dyhAACgkQ9RoMZyVa61eBugCfZCSPrGvFRzKQnJsfplGxZexp
MCwAoIrKHYpNxpTA85BJL1Oll3JHOF+P
=k4yT
-----END PGP SIGNATURE-----

From vesely@tana.it  Wed Jul 13 09:49:42 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 A3B4911E818B for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 09:49:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.85
X-Spam-Level: 
X-Spam-Status: No, score=-4.85 tagged_above=-999 required=5 tests=[AWL=-0.131,  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 jYvguprhUtUX for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 09:49:41 -0700 (PDT)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 7825D11E8194 for <ietf@ietf.org>; Wed, 13 Jul 2011 09:49:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1310575779; bh=6ln+XFI4udzvplpe69bn0olBhm//l5mnAfJSnYO7IHw=; l=866; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=GvmGR9nFhw07akJMDbdEfjiFhw55hwxO96uagJ6a5P7/3HXFH9rmLA8mNPAySWVQM 8LNHkuqVBDQDZAhCbF2hy85qBpRUWwhEjVUOHr5FhVCD1o+Rr8630UiSdsQ3HpDbO+ Pr1xcBtbsRMq/MiEa4zxSL6wKAtBPMY+ttxEUZfA=
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, 13 Jul 2011 18:49:38 +0200 id 00000000005DC039.000000004E1DCCA2.00003A73
Message-ID: <4E1DCCA2.8040109@tana.it>
Date: Wed, 13 Jul 2011 18:49:38 +0200
From: Alessandro Vesely <vesely@tana.it>
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: ietf@ietf.org
Subject: Re: Confidentiality notices on email messages
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com>	<29987.1310565058@marajade.sandelman.ca> <4E1DCA13.9030301@acm.org>
In-Reply-To: <4E1DCA13.9030301@acm.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 16:49:42 -0000

On 13/Jul/11 18:38, Marc Petit-Huguenin wrote:
> On 07/13/2011 06:50 AM, Michael Richardson wrote:
>> 
>> Barry, I think that we should put a filter on the ietf.org that bounces
>> all messages with confidentiality notices.
> 
> Yes, and perhaps disclaimers/confidentiality notices should be standardized with
> their own MIME type to make automatic processing easier so receivers of this
> kind of notice (mailing-list or other) can respect the wishes of the sender.

+1, I am quite concerned by those unneeded clots of legal wisdom
infesting more and more places.  Couldn't they be concise, at least?
A confidentiality notice shouldn't need to thoroughly explain the
legal meaning of the term "confidential"...  Rather than formulate the
law so as to leverage the Internet, legal systems at times seem to be
hindering it with questionable obligations.

From evnikita2@gmail.com  Wed Jul 13 09:59:38 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 77AC521F88A0 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 09:59:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.507
X-Spam-Level: 
X-Spam-Status: No, score=-3.507 tagged_above=-999 required=5 tests=[AWL=0.092,  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 YBfI2rVRwOvO for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 09:59:38 -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 BD78121F889F for <ietf@ietf.org>; Wed, 13 Jul 2011 09:59:37 -0700 (PDT)
Received: by eye13 with SMTP id 13so2534166eye.31 for <ietf@ietf.org>; Wed, 13 Jul 2011 09:59:36 -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=uVu7WIE2OsqD2ZLkKN/CHoFxazymTPvMPFXD5aqXq1k=; b=BmIAdFCX9GJrLYyOlmef8Cu2yIfFkwreR2woOFLnm6pRWD4eqm+9poYpIXdFOyewbl RxzZxxtxUQ3/9Fc8RtAJwTsTeZnA6lYJ6j6Izg8kUh+AGNbVT4KOyGbiy6+6/TRdBAA2 KSzM2VvnHUK+wQg9LSDPPu1Qq7bcFvi01yyGU=
Received: by 10.14.19.131 with SMTP id n3mr420163een.67.1310576376604; Wed, 13 Jul 2011 09:59:36 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id r39sm9427981eeb.11.2011.07.13.09.59.34 (version=SSLv3 cipher=OTHER); Wed, 13 Jul 2011 09:59:35 -0700 (PDT)
Message-ID: <4E1DCF24.5050601@gmail.com>
Date: Wed, 13 Jul 2011 20:00:20 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Last Call: <draft-yevstifeyev-ion-report-06.txt> (Report on the Experiment with IETF Operational Notes (IONs)) to Informational RFC
References: <20110712143944.20141.23357.idtracker@ietfa.amsl.com> <4E1C7B48.4070000@gmail.com> <4E1CC89E.7010907@gmail.com> <4E1D0708.9090701@gmail.com> <CAC4RtVBvfgmJ3JOB6ZTYrWrQYarwbN7uYTi7XmdVS29BjG7PUw@mail.gmail.com>
In-Reply-To: <CAC4RtVBvfgmJ3JOB6ZTYrWrQYarwbN7uYTi7XmdVS29BjG7PUw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 16:59:38 -0000

13.07.2011 17:48, Barry Leiba wrote:
>> Let me explain why I'm planning to include this sub-section.
> Why?  Your explanation lacks substance, and further effort here is a
> waste of time.
>
> The document as it stands is just fine, except for one sentence that
> needs rewording to make sense in English:
>
> OLD
> All IONs were republished whether as IESG statements, Web Pages, or
> were discarded.
>
> NEW
> All IONs were republished as IESG statements, republished as Web Pages,
> or discarded.
I 'll make this correction.
>
>
> The document says everything it needs to say.  Let's publish it as it
> is, and not spend more time trying to argue or explain anything.
Based on the feedback received, I won't include this subsection in the 
draft.

Mykyta
>
> Barry
>


From petithug@acm.org  Wed Jul 13 10:12:43 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 E4ECF21F88E1 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 10:12:43 -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, 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 nTfgZKOdx+Wq for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 10:12:43 -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 1F09621F8906 for <ietf@ietf.org>; Wed, 13 Jul 2011 10:12:43 -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 83F222199E; Wed, 13 Jul 2011 19:11:14 +0200 (CEST)
Message-ID: <4E1DD208.4040909@acm.org>
Date: Wed, 13 Jul 2011 10:12:40 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110626 Iceowl/1.0b2 Icedove/3.1.11
MIME-Version: 1.0
To: Alessandro Vesely <vesely@tana.it>
Subject: Re: Confidentiality notices on email messages
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com>	<29987.1310565058@marajade.sandelman.ca>	<4E1DCA13.9030301@acm.org> <4E1DCCA2.8040109@tana.it>
In-Reply-To: <4E1DCCA2.8040109@tana.it>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 17:12:44 -0000

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

On 07/13/2011 09:49 AM, Alessandro Vesely wrote:
> On 13/Jul/11 18:38, Marc Petit-Huguenin wrote:
>> On 07/13/2011 06:50 AM, Michael Richardson wrote:
>>>
>>> Barry, I think that we should put a filter on the ietf.org that bounces
>>> all messages with confidentiality notices.
>>
>> Yes, and perhaps disclaimers/confidentiality notices should be standardized with
>> their own MIME type to make automatic processing easier so receivers of this
>> kind of notice (mailing-list or other) can respect the wishes of the sender.
> 
> +1, I am quite concerned by those unneeded clots of legal wisdom
> infesting more and more places.  Couldn't they be concise, at least?
> A confidentiality notice shouldn't need to thoroughly explain the
> legal meaning of the term "confidential"...  Rather than formulate the
> law so as to leverage the Internet, legal systems at times seem to be
> hindering it with questionable obligations.

I do not think that size is really the issue.  It can even make things worse - I
saw some attempts (from Cisco people I think) to use a link instead of a
complete notice, but now I have to click on the link and read the web page,
which takes more time than reading an embedded text.

Using a specific MIME type for the notice text itself permits to not display it
if my mailer is configured this way.  If in addition we have an Header field
that describes the restrictions detailed in the disclaimer text, then we can 1)
configure IETF mailing-lists to bounce emails that clash with IETF's Note Well
and 2) configure our individual mailer to bounce emails with a confidentiality
notice but that are not sent specifically to us.

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

iEUEARECAAYFAk4d0f4ACgkQ9RoMZyVa61eGkQCfXPhQ/yTDEDNiQRbff/eYE+y/
QScAmNGXVlGBQBm9QVx3IegUTo9QJrU=
=X41v
-----END PGP SIGNATURE-----

From gregw@intalio.com  Tue Jul 12 16:03:18 2011
Return-Path: <gregw@intalio.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 965F311E80A2 for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 16:03:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.624
X-Spam-Level: 
X-Spam-Status: No, score=-2.624 tagged_above=-999 required=5 tests=[AWL=0.197,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sGeep-4Jamvo for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 16:03:18 -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 A366C11E80A0 for <ietf@ietf.org>; Tue, 12 Jul 2011 16:03:11 -0700 (PDT)
Received: by vws12 with SMTP id 12so5684470vws.31 for <ietf@ietf.org>; Tue, 12 Jul 2011 16:03:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.174.113 with SMTP id br17mr143059vdc.107.1310511790857; Tue, 12 Jul 2011 16:03:10 -0700 (PDT)
Received: by 10.52.115.103 with HTTP; Tue, 12 Jul 2011 16:03:10 -0700 (PDT)
In-Reply-To: <201107122251.p6CMpJC6002069@fs4113.wdf.sap.corp>
References: <4E1BB856.7040601@gmail.com> <201107122251.p6CMpJC6002069@fs4113.wdf.sap.corp>
Date: Wed, 13 Jul 2011 09:03:10 +1000
Message-ID: <CAH_y2NHt7BP00OXk8b7bvLE=EGS5_YzfRodUxMCme+Skr+dQ_Q@mail.gmail.com>
Subject: Re: Repetitions and consensus
From: Greg Wilkins <gregw@intalio.com>
To: mrex@sap.com
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Wed, 13 Jul 2011 10:22:51 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2011 23:03:18 -0000

On 13 July 2011 08:51, Martin Rex <mrex@sap.com> wrote:
> Trying to gauge "(rough) consensus" by counting voiced opinions when an
> issue has not been reliably determined to be non-technical and
> non-procedural _is_ inappropriate.

Note that the point of the paper is saying that people "feel" that
there is a widely held opinion, even if it comes from few repeated
voices and even if they are intellectually aware of the actual count.
So even if there is no actual conscious opinion counting going on, our
brains are doing it for us and it does influence us.

I think there is an important message there for the IETF, because the
establishment of consensus is not by any objective measure and this
science says that subjective measures can be influenced by repetition
and even if chairs/ADs are aware of this fact.   It shows that
subjective measures are subject to manipulation.

I think there is an important message there for the IETF, because the
establishment of consensus is not by any objective measure and this
science says that subjective measures can be influenced by repetition
and even if chairs/ADs are aware of this fact.   It shows that
subjective measures are subject to manipulation.

I think there is an important message there for the IETF, because the
establishment of consensus is not by any objective measure and this
science says that subjective measures can be influenced by repetition
and even if chairs/ADs are aware of this fact.   It shows that
subjective measures are subject to manipulation.

From david.black@emc.com  Tue Jul 12 17:46:38 2011
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C71711E80CA; Tue, 12 Jul 2011 17:46:38 -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 oytjx0Qq8X0G; Tue, 12 Jul 2011 17:46:36 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 35C7A11E807D; Tue, 12 Jul 2011 17:46:35 -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 p6D0kWGv025793 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Jul 2011 20:46:32 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Tue, 12 Jul 2011 20:46:25 -0400
Received: from mxhub02.corp.emc.com (mxhub02.corp.emc.com [10.254.141.104]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p6D0ix58000649; Tue, 12 Jul 2011 20:45:00 -0400
Received: from mx14a.corp.emc.com ([169.254.1.245]) by mxhub02.corp.emc.com ([10.254.141.104]) with mapi; Tue, 12 Jul 2011 20:45:00 -0400
From: <david.black@emc.com>
To: <jmpolk@cisco.com>, <gen-art@ietf.org>, <ietf@ietf.org>
Date: Tue, 12 Jul 2011 20:44:54 -0400
Subject: Gen-ART review of draft-polk-local-emergency-rph-namespace-01
Thread-Topic: Gen-ART review of draft-polk-local-emergency-rph-namespace-01
Thread-Index: AcxA9hUNwavoqEelQfeUxmCy5d9fyw==
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E058941360C@MX14A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Wed, 13 Jul 2011 10:22:51 -0700
Cc: david.black@emc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 00:46:38 -0000

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-polk-local-emergency-rph-namespace-01
Reviewer: David L. Black
Review Date: July 12, 2011
IETF LC End Date: July 13, 2011

Summary:
This draft is basically ready for publication, but has nits that should be =
fixed before publication.

This draft defines a SIP Resource Priority header namespace, "esnet", for u=
se in
providing preferential treatment to emergency calls (e.g., from on-scene re=
sponders).

This field is an addition to rather than a replacement for existing notions=
 of
priority in the SIP Resource Priority header.  Section 2 explains why this =
was
done, but section 2 is a bit sloppy and imprecise.  Some level of imprecisi=
on is
necessary as this draft deliberately does not specify how this header names=
pace
is used to provide preferential treatment.  Nonetheless, the following two =
items
could be improved in Section 2's discussion:

1) Explain the reason for including the second paragraph, the paragraph
	that references RFC 4412's discouragement of modification of priorities
	within an administrative domain.  That paragraph's not connected to the
	rest of section 2.
2) Explicitly state that one of the anticipated uses of the priorities in t=
he
	esnet namespace is to override the ordinary priorities found elsewhere in
	the Resource Priority header.

Small nit: There's an extraneous "to" in the first line of section 3:

   The "esnet" namespace should not to be considered generic for all
                                    ^^

idnits 2.12.12 found a few formatting problems:

  =3D=3D You're using the IETF Trust Provisions' Section 6.b License Notice=
 from
     12 Sep 2009 rather than the newer Notice from 28 Dec 2009.  (See
     http://trustee.ietf.org/license-info/)

  =3D=3D It seems as if not all pages are separated by form feeds - found 0=
 form
     feeds but 7 pages

  =3D=3D The copyright year in the IETF Trust and authors Copyright Line do=
es not
     match the current year


Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------


From gregw@intalio.com  Tue Jul 12 19:53:54 2011
Return-Path: <gregw@intalio.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3F2A21F8B84; Tue, 12 Jul 2011 19:53:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.726
X-Spam-Level: 
X-Spam-Status: No, score=-2.726 tagged_above=-999 required=5 tests=[AWL=0.251,  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 w3oGWmzNoFfo; Tue, 12 Jul 2011 19:53:54 -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 C8E0721F8B83; Tue, 12 Jul 2011 19:53:53 -0700 (PDT)
Received: by vws12 with SMTP id 12so5820591vws.31 for <multiple recipients>; Tue, 12 Jul 2011 19:53:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.73.234 with SMTP id o10mr742781vdv.174.1310525632902; Tue, 12 Jul 2011 19:53:52 -0700 (PDT)
Received: by 10.52.115.103 with HTTP; Tue, 12 Jul 2011 19:53:52 -0700 (PDT)
In-Reply-To: <1310480036.26452.329.camel@vulcan.aspl.local>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <4E1BD054.7010103@gmail.com> <1310480036.26452.329.camel@vulcan.aspl.local>
Date: Wed, 13 Jul 2011 12:53:52 +1000
Message-ID: <CAH_y2NF3pxbUJctg7P1qGNR+mvzaw80+Axh6kCYwx93HiQocug@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard: request for max frame size
From: Greg Wilkins <gregw@intalio.com>
To: Francis Brosnan Blazquez <francis@aspl.es>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Wed, 13 Jul 2011 10:22:51 -0700
Cc: Hybi <hybi@ietf.org>, ietf@ietf.org, draft-ietf-hybi-thewebsocketprotocol@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, 13 Jul 2011 02:53:55 -0000

Francis et al,

not also that the protocol does support fragmentation and a 1004 frame
too large error.
Even the 1004 error does not carry an indication of what an acceptable
size is, so the client/tool/intermediary that receives a 1004 will
either have to fail or guess a smaller frames size - potentially
binary chopping down to find an acceptable size, which might be sub
optimal.

I simple optional header in the handshake declaring the max frame size
(which intermediaries could adjust) would be very complimentary to the
existing fragmentation and 1004 features and I can't think of any
significant down side.

regards

On 13 July 2011 00:13, Francis Brosnan Blazquez <francis@aspl.es> wrote:
> Hi,
>
> Recently, I posted [1] that websocket protocol should include an
> indication about max frame size that is willing to accept the connecting
> peer.
>
> Many pointed this is not an issue because you could use a stream
> oriented API (like TCP send/recv and others), but that only bypasses the
> problem (in some cases) not solves it.
>
> Websocket protocol is frame based and every frame based protocol
> designed until now has/need such feature or similar. Even TCP, for those
> that proposes to use a stream oriented API as a solution, includes a
> more complex mechanism than a simple max frame size (window based ack),
> so each party can control/inform the sender. This is critical.
>
> A good example for this would be the next. Let suppose you have a
> constrained memory device (either because it is small or because it
> accepts a large amount of connections). On that device you deploy a
> websocket app that only accepts small messages (< 512 bytes, let's
> say).
>
> In this context, you can hard code at your web app (javascript) that
> must not send messages larger than this size (so you control websocket
> payload size) and in the case you need to, you must split them
> properly.
>
> However, even with this mechanism, you have no warranty that the browser
> or an intermediary will join those messages into a single frame, causing
> your device to receive a bigger message/frame than expected.
>
> Assuming this I think we would require either to include a
> Max-Frame-Size indication (or a really poor solution: to explicitly
> state on the draft that frames must not be coalesced by intermediaries
> or browsers).
>
> Regards,
>
> [1] http://www.ietf.org/mail-archive/web/hybi/current/msg07641.html
> --
> Francis Brosnan Bl=E1zquez <francis.brosnan@aspl.es>
> ASPL
> 91 134 14 22 - 91 134 14 45 - 91 116 07 57
>
> AVISO LEGAL
>
> Este mensaje se dirige exclusivamente a su destinatario. Los datos
> incluidos en el presente correo son confidenciales y sometidos a secreto
> profesional, se proh=EDbe divulgarlos, en virtud de las leyes vigentes. S=
i
> usted no lo es y lo ha recibido por error o tiene conocimiento del mismo
> por cualquier motivo, le rogamos que nos lo comunique por este medio y
> proceda a destruirlo o borrarlo.
>
> En virtud de lo dispuesto en la Ley Org=E1nica 15/1999, de 13 de
> diciembre, de Protecci=F3n de Datos de Car=E1cter Personal, le informamos=
 de
> que sus datos de car=E1cter personal, recogidos de fuentes accesibles al
> p=FAblico o datos que usted nos ha facilitado previamente, proceden de
> bases de datos propiedad de Advanced Software Production Line, S.L.
> (ASPL). No obstante, usted puede ejercitar sus derechos de acceso,
> rectificaci=F3n, cancelaci=F3n y oposici=F3n dispuestos en la mencionada =
Ley
> Org=E1nica, notific=E1ndolo por escrito a:
> ASPL - Protecci=F3n Datos, C/Antonio Su=E1rez 10 A-102, 28802, Alcal=E1 d=
e
> Henares (Madrid).
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>

From len.holgate@gmail.com  Wed Jul 13 01:22:09 2011
Return-Path: <len.holgate@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CA0F21F8868; Wed, 13 Jul 2011 01:22:09 -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 9ZmnjdGzlTHT; Wed, 13 Jul 2011 01:22:05 -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 BEEDC21F8872; Wed, 13 Jul 2011 01:22:04 -0700 (PDT)
Received: by wyj26 with SMTP id 26so4383191wyj.31 for <multiple recipients>; Wed, 13 Jul 2011 01:22:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:cc:references:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:in-reply-to :thread-index:x-mimeole; bh=o3Ti2WnO7biG3hLZoMhgKZywgFFWW6yagtm4Hmq5sPs=; b=OH14pUMLfPvhpH3SjL2KQdcVF4K3PUCx4SxUU+kZKvUe9C2QfWNgXssJloQdqjLEqs LWVTlq4Jrbnkq8Hbo596bjFgc5eb8Fe0wN+qx6tphKZE+mr92kLsLOjJ5cnnvHkJHAY9 A4NC+hFuldNv9n7N0C5yQnKkjgnG7vPSKAsL0=
Received: by 10.227.166.9 with SMTP id k9mr725962wby.57.1310545323515; Wed, 13 Jul 2011 01:22:03 -0700 (PDT)
Received: from Venus (cpc7-glfd6-2-0-cust20.6-2.cable.virginmedia.com [86.27.227.21]) by mx.google.com with ESMTPS id o19sm7084193wbh.9.2011.07.13.01.22.01 (version=SSLv3 cipher=OTHER); Wed, 13 Jul 2011 01:22:02 -0700 (PDT)
From: "Len Holgate" <len.holgate@gmail.com>
To: "'Francis Brosnan Blazquez'" <francis@aspl.es>, "'Hybi'" <hybi@ietf.org>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com><4E1BD054.7010103@gmail.com> <1310480036.26452.329.camel@vulcan.aspl.local>
Subject: RE: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard: request for max frame size
Date: Wed, 13 Jul 2011 09:21:57 +0100
Message-ID: <1bc701cc4135$efbf8540$0a00a8c0@Venus>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <1310480036.26452.329.camel@vulcan.aspl.local>
Thread-Index: AcxAngKgFP4EGmhgTeejP3KMKb6S9wAljiJQ
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailman-Approved-At: Wed, 13 Jul 2011 10:22:51 -0700
Cc: ietf@ietf.org, draft-ietf-hybi-thewebsocketprotocol@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, 13 Jul 2011 08:22:09 -0000

Francis,

I agree with your points and would welcome a max frame size negotiation
header.

However, whilst an intermediary might legitimately change the =
fragmentation
of a frame it cannot merge complete messages. If, in your example, your
client limited itself to messages of a certain size then it doesn't =
matter
what intermediaries do to the frames as the maximum frame size would be
limited to the maximum message size that the client sends. The only time
this wouldn't work is if you were using a 'message of infinite =
fragments'
where you start with a fragmented frame and don't know when you'll send =
the
final fragment.

The communication between peers about maximum message sizes supported =
could
just as easily be in the application level protocol that you're running =
over
the websocket connection.

Len
www.lenholgate.com

> -----Original Message-----
> From: hybi-bounces@ietf.org [mailto:hybi-bounces@ietf.org] On=20
> Behalf Of Francis Brosnan Blazquez
> Sent: 12 July 2011 15:14
> To: Hybi
> Cc: ietf@ietf.org; draft-ietf-hybi-thewebsocketprotocol@tools.ietf.org
> Subject: Re: [hybi] Last Call:=20
> <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket=20
> protocol) to Proposed Standard: request for max frame size
>=20
> Hi,
>=20
> Recently, I posted [1] that websocket protocol should include an
> indication about max frame size that is willing to accept the=20
> connecting
> peer.=20
>=20
> Many pointed this is not an issue because you could use a stream
> oriented API (like TCP send/recv and others), but that only=20
> bypasses the
> problem (in some cases) not solves it.
>=20
> Websocket protocol is frame based and every frame based protocol
> designed until now has/need such feature or similar. Even=20
> TCP, for those
> that proposes to use a stream oriented API as a solution, includes a
> more complex mechanism than a simple max frame size (window=20
> based ack),
> so each party can control/inform the sender. This is critical.
>=20
> A good example for this would be the next. Let suppose you have a
> constrained memory device (either because it is small or because it
> accepts a large amount of connections). On that device you deploy a
> websocket app that only accepts small messages (< 512 bytes, let's
> say).=20
>=20
> In this context, you can hard code at your web app (javascript) that
> must not send messages larger than this size (so you control websocket
> payload size) and in the case you need to, you must split them
> properly.=20
>=20
> However, even with this mechanism, you have no warranty that=20
> the browser
> or an intermediary will join those messages into a single=20
> frame, causing
> your device to receive a bigger message/frame than expected.
>=20
> Assuming this I think we would require either to include a
> Max-Frame-Size indication (or a really poor solution: to explicitly
> state on the draft that frames must not be coalesced by intermediaries
> or browsers).=20
>=20
> Regards,
>=20
> [1] http://www.ietf.org/mail-archive/web/hybi/current/msg07641.html
> --=20
> Francis Brosnan Bl=E1zquez <francis.brosnan@aspl.es>
> ASPL
> 91 134 14 22 - 91 134 14 45 - 91 116 07 57
>=20
> AVISO LEGAL
>=20
> Este mensaje se dirige exclusivamente a su destinatario. Los datos
> incluidos en el presente correo son confidenciales y=20
> sometidos a secreto
> profesional, se proh=EDbe divulgarlos, en virtud de las leyes=20
> vigentes. Si
> usted no lo es y lo ha recibido por error o tiene=20
> conocimiento del mismo
> por cualquier motivo, le rogamos que nos lo comunique por este medio y
> proceda a destruirlo o borrarlo.
>=20
> En virtud de lo dispuesto en la Ley Org=E1nica 15/1999, de 13 de
> diciembre, de Protecci=F3n de Datos de Car=E1cter Personal, le=20
> informamos de
> que sus datos de car=E1cter personal, recogidos de fuentes accesibles =
al
> p=FAblico o datos que usted nos ha facilitado previamente, proceden de
> bases de datos propiedad de Advanced Software Production Line, S.L.
> (ASPL). No obstante, usted puede ejercitar sus derechos de acceso,
> rectificaci=F3n, cancelaci=F3n y oposici=F3n dispuestos en la =
mencionada Ley
> Org=E1nica, notific=E1ndolo por escrito a:
> ASPL - Protecci=F3n Datos, C/Antonio Su=E1rez 10 A-102, 28802, =
Alcal=E1 de
> Henares (Madrid).
>=20
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>=20


From len.holgate@gmail.com  Wed Jul 13 01:22:35 2011
Return-Path: <len.holgate@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A647211E807A; Wed, 13 Jul 2011 01:22:35 -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 AopED6x+HuBL; Wed, 13 Jul 2011 01:22:34 -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 CB26911E8072; Wed, 13 Jul 2011 01:22:33 -0700 (PDT)
Received: by mail-wy0-f172.google.com with SMTP id 26so4383191wyj.31 for <multiple recipients>; Wed, 13 Jul 2011 01:22:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:cc:references:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:in-reply-to :thread-index:x-mimeole; bh=3dZIITYVRz7SMDybIKj2CyZwZRbnlXntH31gxQyhmHM=; b=K/eSsML5CWPuMjiwkKidbu/vRRoRPVv1teW4AOEy4Rn+wFs0sUdPPOuPzNHqxofpZy 5wtscuWXm6R766HFB7ozLEBXhI1Gxr1oZusjQpW07tB0D9V9sSOUhc+9JvSrbF6/0Uuq D6pHSQntYlPJyuogmF+48J7+GWgw0/KGyQwpk=
Received: by 10.227.32.136 with SMTP id c8mr766934wbd.7.1310545352315; Wed, 13 Jul 2011 01:22:32 -0700 (PDT)
Received: from Venus (cpc7-glfd6-2-0-cust20.6-2.cable.virginmedia.com [86.27.227.21]) by mx.google.com with ESMTPS id gb1sm11472017wbb.20.2011.07.13.01.22.30 (version=SSLv3 cipher=OTHER); Wed, 13 Jul 2011 01:22:31 -0700 (PDT)
From: "Len Holgate" <len.holgate@gmail.com>
To: "'Greg Wilkins'" <gregw@intalio.com>, "'Francis Brosnan Blazquez'" <francis@aspl.es>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com><4E1BD054.7010103@gmail.com><1310480036.26452.329.camel@vulcan.aspl.local> <CAH_y2NF3pxbUJctg7P1qGNR+mvzaw80+Axh6kCYwx93HiQocug@mail.gmail.com>
Subject: RE: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard: request for max frame size
Date: Wed, 13 Jul 2011 09:22:27 +0100
Message-ID: <1bd101cc4136$01193390$0a00a8c0@Venus>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <CAH_y2NF3pxbUJctg7P1qGNR+mvzaw80+Axh6kCYwx93HiQocug@mail.gmail.com>
Thread-Index: AcxBCCYACdBGKvETT6ymGz9toQUOowAK30Hg
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailman-Approved-At: Wed, 13 Jul 2011 10:22:51 -0700
Cc: 'Hybi' <hybi@ietf.org>, ietf@ietf.org, draft-ietf-hybi-thewebsocketprotocol@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, 13 Jul 2011 08:22:35 -0000

I agree that this would be very useful.=20

Would this be one frame size for both directions, or could it be =
specified
in each direction?=20

I'm a little wary of intermediaries being allowed to adjust this unless
they're only allowed to reduce the amount...

Len
www.lenholgate.com

> -----Original Message-----
> From: hybi-bounces@ietf.org [mailto:hybi-bounces@ietf.org] On=20
> Behalf Of Greg Wilkins
> Sent: 13 July 2011 03:54
> To: Francis Brosnan Blazquez
> Cc: Hybi; ietf@ietf.org;=20
> draft-ietf-hybi-thewebsocketprotocol@tools.ietf.org
> Subject: Re: [hybi] Last Call:=20
> <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket=20
> protocol) to Proposed Standard: request for max frame size
>=20
> Francis et al,
>=20
> not also that the protocol does support fragmentation and a 1004 frame
> too large error.
> Even the 1004 error does not carry an indication of what an acceptable
> size is, so the client/tool/intermediary that receives a 1004 will
> either have to fail or guess a smaller frames size - potentially
> binary chopping down to find an acceptable size, which might be sub
> optimal.
>=20
> I simple optional header in the handshake declaring the max frame size
> (which intermediaries could adjust) would be very complimentary to the
> existing fragmentation and 1004 features and I can't think of any
> significant down side.
>=20
> regards
>=20
> On 13 July 2011 00:13, Francis Brosnan Blazquez=20
> <francis@aspl.es> wrote:
> > Hi,
> >
> > Recently, I posted [1] that websocket protocol should include an
> > indication about max frame size that is willing to accept=20
> the connecting
> > peer.
> >
> > Many pointed this is not an issue because you could use a stream
> > oriented API (like TCP send/recv and others), but that only=20
> bypasses the
> > problem (in some cases) not solves it.
> >
> > Websocket protocol is frame based and every frame based protocol
> > designed until now has/need such feature or similar. Even=20
> TCP, for those
> > that proposes to use a stream oriented API as a solution, includes a
> > more complex mechanism than a simple max frame size (window=20
> based ack),
> > so each party can control/inform the sender. This is critical.
> >
> > A good example for this would be the next. Let suppose you have a
> > constrained memory device (either because it is small or because it
> > accepts a large amount of connections). On that device you deploy a
> > websocket app that only accepts small messages (< 512 bytes, let's
> > say).
> >
> > In this context, you can hard code at your web app (javascript) that
> > must not send messages larger than this size (so you=20
> control websocket
> > payload size) and in the case you need to, you must split them
> > properly.
> >
> > However, even with this mechanism, you have no warranty=20
> that the browser
> > or an intermediary will join those messages into a single=20
> frame, causing
> > your device to receive a bigger message/frame than expected.
> >
> > Assuming this I think we would require either to include a
> > Max-Frame-Size indication (or a really poor solution: to explicitly
> > state on the draft that frames must not be coalesced by=20
> intermediaries
> > or browsers).
> >
> > Regards,
> >
> > [1] http://www.ietf.org/mail-archive/web/hybi/current/msg07641.html
> > --
> > Francis Brosnan Bl=E1zquez <francis.brosnan@aspl.es>
> > ASPL
> > 91 134 14 22 - 91 134 14 45 - 91 116 07 57
> >
> > AVISO LEGAL
> >
> > Este mensaje se dirige exclusivamente a su destinatario. Los datos
> > incluidos en el presente correo son confidenciales y=20
> sometidos a secreto
> > profesional, se proh=EDbe divulgarlos, en virtud de las leyes=20
> vigentes. Si
> > usted no lo es y lo ha recibido por error o tiene=20
> conocimiento del mismo
> > por cualquier motivo, le rogamos que nos lo comunique por=20
> este medio y
> > proceda a destruirlo o borrarlo.
> >
> > En virtud de lo dispuesto en la Ley Org=E1nica 15/1999, de 13 de
> > diciembre, de Protecci=F3n de Datos de Car=E1cter Personal, le=20
> informamos de
> > que sus datos de car=E1cter personal, recogidos de fuentes=20
> accesibles al
> > p=FAblico o datos que usted nos ha facilitado previamente, proceden =
de
> > bases de datos propiedad de Advanced Software Production Line, S.L.
> > (ASPL). No obstante, usted puede ejercitar sus derechos de acceso,
> > rectificaci=F3n, cancelaci=F3n y oposici=F3n dispuestos en la=20
> mencionada Ley
> > Org=E1nica, notific=E1ndolo por escrito a:
> > ASPL - Protecci=F3n Datos, C/Antonio Su=E1rez 10 A-102, 28802, =
Alcal=E1 de
> > Henares (Madrid).
> >
> > _______________________________________________
> > hybi mailing list
> > hybi@ietf.org
> > https://www.ietf.org/mailman/listinfo/hybi
> >
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>=20


From francis@aspl.es  Wed Jul 13 04:39:14 2011
Return-Path: <francis@aspl.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03A6421F86EE; Wed, 13 Jul 2011 04:39:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.713
X-Spam-Level: *
X-Spam-Status: No, score=1.713 tagged_above=-999 required=5 tests=[AWL=-0.571,  BAYES_00=-2.599, FH_HOST_ALMOST_IP=1.889, HOST_EQ_STATIC=1.172,  HOST_EQ_STATICIP=1.511, 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 wwULTg-mAJLw; Wed, 13 Jul 2011 04:39:13 -0700 (PDT)
Received: from mail.aspl.es (196.Red-212-170-101.staticIP.rima-tde.net [212.170.101.196]) by ietfa.amsl.com (Postfix) with ESMTP id 36F0621F85F4; Wed, 13 Jul 2011 04:39:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.aspl.es (Postfix) with ESMTP id 866111170002; Wed, 13 Jul 2011 13:39:10 +0200 (CEST)
X-Virus-Scanned: amavisd-new at aspl.es
Received: from mail.aspl.es ([127.0.0.1]) by localhost (dolphin.aspl.es [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rJYwWvo1rEHq; Wed, 13 Jul 2011 13:39:10 +0200 (CEST)
Received: from [192.168.0.132] (barracuda [10.0.0.4]) by mail.aspl.es (Postfix) with ESMTP id 003AA1170001; Wed, 13 Jul 2011 13:39:09 +0200 (CEST)
Subject: RE: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard: request for max frame size
From: Francis Brosnan Blazquez <francis@aspl.es>
To: Len Holgate <len.holgate@gmail.com>
In-Reply-To: <1bd101cc4136$01193390$0a00a8c0@Venus>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <4E1BD054.7010103@gmail.com><1310480036.26452.329.camel@vulcan.aspl.local> <CAH_y2NF3pxbUJctg7P1qGNR+mvzaw80+Axh6kCYwx93HiQocug@mail.gmail.com> <1bd101cc4136$01193390$0a00a8c0@Venus>
Content-Type: text/plain; charset="ISO-8859-15"
Organization: ASPL
Date: Wed, 13 Jul 2011 13:39:11 +0200
Message-ID: <1310557151.26452.1232.camel@vulcan.aspl.local>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 13 Jul 2011 10:22:51 -0700
Cc: draft-ietf-hybi-thewebsocketprotocol@tools.ietf.org, 'Hybi' <hybi@ietf.org>, ietf@ietf.org, 'Greg Wilkins' <gregw@intalio.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, 13 Jul 2011 11:39:14 -0000

Hi Len,

> I agree that this would be very useful. 
> 
> Would this be one frame size for both directions, or could it be specified
> in each direction? 

It should be done in both directions, assuming each party may have
different requirements..

> I'm a little wary of intermediaries being allowed to adjust this unless
> they're only allowed to reduce the amount...

My impression is that this max frame size value would help
intermediaries, and peers, to know how to fragment or coalesce
application level messages. Without such indication they are blind...


From keith.drage@alcatel-lucent.com  Wed Jul 13 04:59:31 2011
Return-Path: <keith.drage@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 345FC11E8099; Wed, 13 Jul 2011 04:59:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.189
X-Spam-Level: 
X-Spam-Status: No, score=-106.189 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, HELO_EQ_FR=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 ahHYJHQBd39X; Wed, 13 Jul 2011 04:59:30 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by ietfa.amsl.com (Postfix) with ESMTP id 27FC911E8086; Wed, 13 Jul 2011 04:59:30 -0700 (PDT)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail5.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p6DBxH9n007055 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 13 Jul 2011 13:59:25 +0200
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.47]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Wed, 13 Jul 2011 13:59:20 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>, "ietf@ietf.org IETF" <ietf@ietf.org>, "ecrit@ietf.org" <ecrit@ietf.org>
Date: Wed, 13 Jul 2011 13:59:18 +0200
Subject: RE: [Ecrit] Last Call: <draft-polk-local-emergency-rph-namespace-01.txt> (IANA	Registering a SIP Resource Priority Header Field Namespace	for Local Emergency Communications) to Proposed Standard
Thread-Topic: [Ecrit] Last Call: <draft-polk-local-emergency-rph-namespace-01.txt> (IANA	Registering a SIP Resource Priority Header Field Namespace	for Local Emergency Communications) to Proposed Standard
Thread-Index: AcxBPn6uuS0dG300QguqVSnnsBhD8gAFQbTQ
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE21FC9330D@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <20110615212629.9737.88852.idtracker@ietfa.amsl.com> <64D47317-0D25-40FA-8D08-B256096660F1@gmx.net>
In-Reply-To: <64D47317-0D25-40FA-8D08-B256096660F1@gmx.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-Scanned-By: MIMEDefang 2.64 on 155.132.188.13
X-Mailman-Approved-At: Wed, 13 Jul 2011 10:22:51 -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, 13 Jul 2011 11:59:31 -0000

If you insist on that scope

> I was in the believe that the scope is restricted only to PSAP-to-first
> Responder, and PSAP-to-PSAP communication.

Then you can throw it away.

I certainly don't see it being used by an emergency calling UA, but in a 3G=
PP like solution to emergency calling, there is no reason why it cannot be =
used by the first network operator provided entity that identifies an emerg=
ency call. I agree it is not applicable to the IETF solution, but then you =
have no network operator to provide you with priority in the first place.

If a network operator want to provide priority in their equipment after poi=
nt of entry to the network, to an emergency call, then RPH is the sensible =
way of doing it, and not forcing them to recognize multiple different param=
eters to identify that priority is needed.

You seem to be back in cloud cuckoo land where you believe all emergency ca=
lls are handled by the IETF ECRIT solution.

Keith

> -----Original Message-----
> From: ecrit-bounces@ietf.org [mailto:ecrit-bounces@ietf.org] On Behalf Of
> Hannes Tschofenig
> Sent: 13 July 2011 10:21
> To: ietf@ietf.org IETF; ecrit@ietf.org
> Subject: Re: [Ecrit] Last Call: <draft-polk-local-emergency-rph-namespace=
-
> 01.txt> (IANA Registering a SIP Resource Priority Header Field Namespace
> for Local Emergency Communications) to Proposed Standard
>=20
> Reading through the document I fail to see the clearly stated restriction
> that this is not to be used between the emergency caller's UA and the
> VSP/ASP's network (for VSP/ASP routed calls) or between the UA and the
> PSAP (for directly routed calls).
> I was in the believe that the scope is restricted only to PSAP-to-first
> Responder, and PSAP-to-PSAP communication.
>=20
> It might also be useful to add that this document did not make it through
> the ECRIT working group. The document type is Standards Track and might
> give the impression that there is wide consensus behind the document --
> but there isn't. IETF last calls may add a lot of value but I do not see
> that anyone had pointed to the various discussions in the ECRIT mailing
> list on that topic.
>=20
> I was always of the impression that the mechanism does not lead to any
> useful outcome. See previous discussions:
> Hannes: http://www.ietf.org/mail-archive/web/ecrit/current/msg05940.html
> Henning: http://www.ietf.org/mail-archive/web/ecrit/current/msg05941.html
> JamesW: http://www.ietf.org/mail-archive/web/ecrit/current/msg05945.html
>=20
> For those who have not followed the work I would like to point out that w=
e
> have an "marking" (or call it indication) of an emergency call already, i=
t
> is called a Service URN - RFC 5031. How many times do we need to again
> identify that a call (or a message) is an emergency call?
>=20
> The document interestingly talks about closed networks or controlled
> environments where this is supposed to be used. I don't believe it is
> useful to do so because this leaves the door open to use the mechanism
> anywhere. Often, these networks are not as closed as we think.
>=20
>   This new namespace can be included in SIP requests to provide an
>    explicit priority indication within controlled environments, such as
>    an IMS infrastructure or Emergency Services network (ESInet) where
>    misuse can be reduced to a minimum because these types of networks
>    have great controls in place.
>=20
> Btw, what are these >>great<< controls?
>=20
> My comments are addressed if the document (in the introduction) makes it
> clear that UAs' MUST NOT include this  RP namespace in an outgoing
> emergency call because there is already the Service URN marking that
> classifies the call as an emergency call.
> We had already agreed on this a long time ago, see
> http://www.ietf.org/mail-archive/web/ecrit/current/msg05960.html. Still,
> the text in the introduction and in the security consideration is very
> fuzzy and in my view intentionally does not make the case clear to leave
> it up to interpretation.
>=20
> It is ironic that this document manages to get finished before the major
> work of the ECRIT group, namely PhoneBCP, and ECRIT framework, get
> completed. (Or the SIPCORE SIP location conveyance for that matter as
> well.)
> Why would someone want to go with their work through a working group when
> they can get a Standards Track document faster and easier?
>=20
> Ciao
> Hannes
>=20
> On Jun 16, 2011, at 12:26 AM, The IESG wrote:
>=20
> >
> > The IESG has received a request from an individual submitter to conside=
r
> > the following document:
> > - 'IANA Registering a SIP Resource Priority Header Field Namespace for
> >   Local Emergency Communications'
> >  <draft-polk-local-emergency-rph-namespace-01.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-07-13. Exceptionally, comments may
> be
> > sent to iesg@ietf.org instead. In either case, please retain the
> > beginning of the Subject line to allow automated sorting.
> >
> > Abstract
> >
> >
> >   This document creates the new Session Initiation Protocol (SIP)
> >   Resource Priority header field namespace "esnet" for local emergency
> >   usage to a public safety answering point (PSAP), between PSAPs, and
> >   between a PSAP and first responders and their organizations, and
> >   places this namespace in the IANA registry.
> >
> >
> >
> >
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-polk-local-emergency-rph-
> namespace/
> >
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-polk-local-emergency-rph-
> namespace/
> >
> >
> > 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
>=20
> _______________________________________________
> Ecrit mailing list
> Ecrit@ietf.org
> https://www.ietf.org/mailman/listinfo/ecrit

From len.holgate@gmail.com  Wed Jul 13 05:13:22 2011
Return-Path: <len.holgate@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70A6A21F87BA; Wed, 13 Jul 2011 05:13:22 -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 g6cUr328IxxR; Wed, 13 Jul 2011 05:13: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 CE05D21F8B25; Wed, 13 Jul 2011 05:13:17 -0700 (PDT)
Received: by wwe5 with SMTP id 5so3923380wwe.13 for <multiple recipients>; Wed, 13 Jul 2011 05:13:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:cc:references:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:in-reply-to :thread-index:x-mimeole; bh=CSgHtomih3QbYOmqA6/1xHhC0asTuC1mWBftZXUt/TY=; b=hTybVOIxtPnrmo3hyhoITeBc8u+CUAyrFrKdLaNd+gh4IrZNQhx2sLuHHnzm9aM/nF xv77YNhknjbR6YvlFbYXCLXNVpjol2I30KM2Mqk9oIy1BelCcXE77u9T3dStbp6OPj8q n8Yl/xdIC2EWwn1uHSWrIvtnJymUP4xkdXUHc=
Received: by 10.227.137.6 with SMTP id u6mr214050wbt.111.1310559195298; Wed, 13 Jul 2011 05:13:15 -0700 (PDT)
Received: from Venus (cpc7-glfd6-2-0-cust20.6-2.cable.virginmedia.com [86.27.227.21]) by mx.google.com with ESMTPS id ex2sm11618278wbb.31.2011.07.13.05.13.13 (version=SSLv3 cipher=OTHER); Wed, 13 Jul 2011 05:13:14 -0700 (PDT)
From: "Len Holgate" <len.holgate@gmail.com>
To: "'Francis Brosnan Blazquez'" <francis@aspl.es>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <4E1BD054.7010103@gmail.com><1310480036.26452.329.camel@vulcan.aspl.local> <CAH_y2NF3pxbUJctg7P1qGNR+mvzaw80+Axh6kCYwx93HiQocug@mail.gmail.com> <1bd101cc4136$01193390$0a00a8c0@Venus> <1310557151.26452.1232.camel@vulcan.aspl.local>
Subject: RE: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard: request for max frame size
Date: Wed, 13 Jul 2011 13:13:09 +0100
Message-ID: <1c2501cc4156$3ba36a60$0a00a8c0@Venus>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <1310557151.26452.1232.camel@vulcan.aspl.local>
Thread-Index: AcxBUX12KOgYcjXmQlqhBPeazS5MIAABIkjQ
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailman-Approved-At: Wed, 13 Jul 2011 10:22:51 -0700
Cc: draft-ietf-hybi-thewebsocketprotocol@tools.ietf.org, 'Hybi' <hybi@ietf.org>, ietf@ietf.org, 'Greg Wilkins' <gregw@intalio.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, 13 Jul 2011 12:13:22 -0000

> > Would this be one frame size for both directions, or could 
> it be specified
> > in each direction? 
> 
> It should be done in both directions, assuming each party may have
> different requirements..

That was my feeling on it.

> > I'm a little wary of intermediaries being allowed to adjust 
> this unless
> > they're only allowed to reduce the amount...
> 
> My impression is that this max frame size value would help
> intermediaries, and peers, to know how to fragment or coalesce
> application level messages. Without such indication they are blind...

I agree.

Len
www.lenholgate.com


From alessandro.dalessandro@telecomitalia.it  Wed Jul 13 06:07:01 2011
Return-Path: <alessandro.dalessandro@telecomitalia.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 0861921F84F5; Wed, 13 Jul 2011 06:07:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.069
X-Spam-Level: 
X-Spam-Status: No, score=-0.069 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gxvli4Sf+ick; Wed, 13 Jul 2011 06:06:57 -0700 (PDT)
Received: from GRFEDG701RM001.telecomitalia.it (grfedg701rm001.telecomitalia.it [217.169.121.20]) by ietfa.amsl.com (Postfix) with ESMTP id 9DE0021F8564; Wed, 13 Jul 2011 06:02:29 -0700 (PDT)
Received: from grfhub702rm001.griffon.local (10.19.3.9) by GRFEDG701RM001.telecomitalia.it (10.173.88.20) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 13 Jul 2011 15:02:27 +0200
Received: from GRFMBX702RM001.griffon.local ([10.19.3.20]) by grfhub702rm001.griffon.local ([10.19.9.235]) with mapi; Wed, 13 Jul 2011 15:02:26 +0200
From: D'Alessandro Alessandro Gerardo <alessandro.dalessandro@telecomitalia.it>
To: IETF-Announce <ietf-announce@ietf.org>
Date: Wed, 13 Jul 2011 15:02:25 +0200
Subject: R: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive Connectivity Verification, Continuity Check and Remote Defect indication for MPLS	Transport	Profile) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive Connectivity Verification, Continuity Check and Remote Defect indication for MPLS	Transport	Profile) to Proposed Standard
Thread-Index: Acw78+yUyZwkPT7YRSyxVgVnNmWPlAFUhpLQ
Message-ID: <A1F769BC58A8B146B2EEA818EAE052A2096BC61662@GRFMBX702RM001.griffon.local>
References: <20110630134642.1281.3095.idtracker@ietfa.amsl.com> <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B3D5@INOAVREX11.ptin.corpPT.com> <4E1482C8.6020701@pi.nu>
In-Reply-To: <4E1482C8.6020701@pi.nu>
Accept-Language: en-US
Content-Language: it-IT
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, 13 Jul 2011 10:22:51 -0700
Cc: "mpls@ietf.org" <mpls@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, 13 Jul 2011 13:07:01 -0000

Dear all,
I regret to say I have the same concerns expressed by Rui and Erminio about=
 the procedure adopted for this document that has brought so many discussio=
ns. Anyway, probably because of the lack of a reasonable time (in my opinio=
n) for discussions about the previous document version (-04) I have the fol=
lowing comments on this version:

1. it is not clear the BFD's scope
        Sect. 1: PW, LSP, SPME
        Sect. 1: LSP
        Sect 3: LSP
        Sect 3.1:LSP, PW
        Sect 3.3: PW, LSP, SPME, Section
        Sect 3.7: LSP

2. encapsulation
        Sect 1: supported encapsulation GAL/GACh, VCCV, UDP/IP: can be expr=
essed a preference (MUST/MAY) for Transport Profile applications for intero=
perability issues? I would avoid single vendor networks coming from too man=
y options.

3. diagnostic code 5
        Could you clarify what is the BFD state machine behavior receiving/=
transmitting a Diagn Code=3D5

4. detection time
        Sect 3.2: I expect it is that one defined in RFC5884 i.e. detect Mu=
lt x greater (bfd.requiredminrxinterval, last received desired min tx inter=
val). What "interval" means is not clear

5. session periodicity
        Sec 3.3 Should be clarified being not defined in RFC5880

6. detection of loss of continuity
        Sect 3.3 can CV packet  sent on the wire replace CC packet (for LOC=
 purpose on the far end)?

7. CV vs CC packets
        Sect 3.6 Generally speaking, how should the received CV packet's fi=
elds be managed with respect of the BFD state machine/BFD states? (beyond w=
hat is specified in such paragraph limited to P/F and Sta).

8. encoding
        Sect 3.5: could you clarify what " A BFD session will only use one =
encoding of the Source ID TLV" means?

9. editorial
        Source ID TLV, MEP source ID TLV, Source MEP TLV should be aligned

10. terminology
        Wrt sect 3.6 I would ask a clarification about the terminology wher=
e I found
        a- "A BFD session corresponds to a CC and proactive CV OAM instance=
"
        b- " A BFD session is enabled when the CC and proactive CV function=
ality is enabled"
        c- " When the CC and proactive CV functionality is disabled ..., th=
e BFD session transitions to the ADMIN DOWN State and the BFD session ends"
                In the ADMIN DOWN state I understood I can have BFD control=
 packet exchange between the end points. Is it consistent with CC/CV functi=
onality disabled?
11. code points
        Code points are not specified in section 3.1 as stated

12. BFD fixed rate
        Sect 3.7 " This rate is a fixed value common for both directions of=
 MEG for the lifetime of the MEG". Is this statement implying that MEG must=
 be destroyed to be able to change the BFD rate? Should not be limited to t=
he BFD session lifetime (to be clarified what it means... because moving to=
 ADMIN DOWN state both ends could not be enough)

13. two BFD modes
        Sect 3.7 " Two independent BFD sessions are used for independent op=
eration". In my opinion, this approach still remain a big limitation in BFD=
 usage.
        Is it implementation specific the way the two ends distinguish betw=
een the two BFD modes?

14. bfd.RemoteDiscr
        Sect 3.7 " In coordinated mode, an implementation SHOULD NOT reset =
bfd.RemoteDiscr until it is exiting the DOWN state"
        Is it a deviation from BFD as specified in RFC 5880? If it is, coul=
d you clarified the reason for that?

15. bfd.RemoteDiscr
        Sect 3.7 Could you clarify the reasons behind different treatments =
for bfd.RemoteDiscr in coordinated mode and independent mode?

16. overall operation
        Sect 3.7 "Overall operation is as specified in [4] and augmented fo=
r MPLS in[8]"
        Are you sure that it can be generalized in that way? Should not be =
the case to specify more in details what applies and what do not apply?

17. IP-based BFD
        Sect 3.1  IP-based BFD can carry out CV functionality only if IP SA=
 is public

18. CV during transient states
        Sect 3.2 for clarification: at start-up, CC are sent one per second=
. CV are sent in addition to CC (so we have two BFD packets per second)?

19. misconnections
        Sect 3.7.3 sect 3.7.3 states a misconnection bring BFD session to D=
OWN whilst it is not clear if sect 3.7.5 state that misconnection do not im=
pact on BFD state transition

20. encapsulation modes
        Sect 4: if I understood well, there are 4 encapusulations and modes=
 for BFD: UDP/IP/LSP; CC mode in G-ACh; UPD/IP in G-ACh e CC/CV mode in G-A=
Ch.
        Do all of them satisfy transport requirements?
        I understand they are not interoperable (as well as the two BFD mod=
e for the same CC/CV in G-Ach encapsulation). Is it correct?

Best regards,
Alessandro

------------------------------------------------------------------
Telecom Italia
Alessandro D'Alessandro
Transport Innovation
Via Reiss Romoli, 274 - 10148 Torino
phone:  +39 011 228 5887
mobile: +39 335 766 9607
fax: +39 06 418 639 07


-----Messaggio originale-----
Da: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] Per conto di Loa A=
ndersson
Inviato: mercoled=EC 6 luglio 2011 17:44
A: Rui Costa
Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
Oggetto: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proac=
tive Connectivity Verification, Continuity Check and Remote Defect indicati=
on for MPLS Transport Profile) to Proposed Standard

All,

Since someone has commented about the process used for resolving questions =
on draft-ietf-mpls-tp-cc-cv-rdi I am supplying some details below.

The history of draft-ietf-mpls-tp-cc-cv-rdi working group review process is=
:

On February 3rd 2011 the working group last call was issued on version -03

      This was copied to the the Ad Hoc Team List
      and liaised to SG15 also on February 3rd

      This working group last call ended om Feb 28


      On Feb 28 we also received a liaison with comments from SG15


The authors compiled a list of all comments received  as part the MPLS work=
ing group last call; these  comments - and the intended resolution - is inc=
luded in the meeting minutes from the Prague meeting:


      http://www.ietf.org/proceedings/80/slides/mpls-9.pdf


  During the IETF meeting in Prague, we agreed with the BFD working
  group to do a separate working group last callfor the BFD working
  group

The (BFD) working group last call was started on March 30th and ran for 13 =
days. The last call ended on April 11th.

  The authors have since worked hard to resolve comments, some
  issue has been brought to the working group mailing list for
  resolution.

  Version -04 of the document was published June 28th.

  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
  June 29th.

  The AD review resulted in a "New ID needed" due to mostly editorial
  comments. Version -05 was published on June 29 and the IETF last call
  started as soon as the new ID was avaialbe.

  The current list of Last Call Comments resoltion is also avaiable at:
  http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls

  The list of issues that the authors kept very carefully, shows without do=
ubt
  that no comments been ignored.

  Loa
  mpls wg document shepherd

On 2011-07-05 00:02, Rui Costa wrote:
> IMHO and for the record:
>
> ITU-T comments regarding this draft haven't been discussed with ITU-T but=
 were simply ignored. No LS describing these comments' resolution was sent.
>
> Several service providers regarded this draft as not meeting their transp=
ort networks' needs.
>
> [The v03 draft was published in Feb and went to WG LC.
> The v04 draft addressing WG LC comments was published on the 28th June (s=
ame date as the proto write-up).
> When was the WG LC launched, to verify LC comments resolution?]
>
> Regards,
> Rui
>
>
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
> Of The IESG
> Sent: quinta-feira, 30 de Junho de 2011 14:47
> To: IETF-Announce
> Cc: mpls@ietf.org
> Subject: [mpls] Last Call:<draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote
> Defect indication for MPLS Transport Profile) to Proposed Standard
>
>
> The IESG has received a request from the Multiprotocol Label Switching
> WG
> (mpls) to consider the following document:
> - 'Proactive Connectivity Verification, Continuity Check and Remote
>     Defect indication for MPLS Transport Profile'
>    <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally, comments may
> be sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>     Continuity Check, Proactive Connectivity Verification and Remote
>     Defect Indication functionalities are required for MPLS-TP OAM.
>
>     Continuity Check monitors the integrity of the continuity of the
>     label switched path for any loss of continuity defect. Connectivity
>     verification monitors the integrity of the routing of the label
>     switched path between sink and source for any connectivity issues.
>     Remote defect indication enables an End Point to report, to its
>     associated End Point, a fault or defect condition that it detects on
>     a pseudo wire, label switched path or Section.
>
>     This document specifies methods for proactive continuity check,
>     continuity verification, and remote defect indication for MPLS-TP
>     label switched paths, pseudo wires and Sections using Bidirectional
>     Forwarding Detection.
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>
>
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

--


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13 ____________=
___________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, Thanks.


From francis@aspl.es  Wed Jul 13 07:27:53 2011
Return-Path: <francis@aspl.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7991E21F8666; Wed, 13 Jul 2011 07:27:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.903
X-Spam-Level: *
X-Spam-Status: No, score=1.903 tagged_above=-999 required=5 tests=[AWL=-0.380,  BAYES_00=-2.599, FH_HOST_ALMOST_IP=1.889, HOST_EQ_STATIC=1.172,  HOST_EQ_STATICIP=1.511, 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 2bbjbUWtBIQP; Wed, 13 Jul 2011 07:27:49 -0700 (PDT)
Received: from mail.aspl.es (196.Red-212-170-101.staticIP.rima-tde.net [212.170.101.196]) by ietfa.amsl.com (Postfix) with ESMTP id DCEAA21F8745; Wed, 13 Jul 2011 07:27:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.aspl.es (Postfix) with ESMTP id F391E1170003; Wed, 13 Jul 2011 16:27:36 +0200 (CEST)
X-Virus-Scanned: amavisd-new at aspl.es
Received: from mail.aspl.es ([127.0.0.1]) by localhost (dolphin.aspl.es [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m+0i1W3ug7UV; Wed, 13 Jul 2011 16:27:31 +0200 (CEST)
Received: from [192.168.0.132] (barracuda [10.0.0.4]) by mail.aspl.es (Postfix) with ESMTP id 964671170001; Wed, 13 Jul 2011 16:27:31 +0200 (CEST)
Subject: RE: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard: request for max frame size
From: Francis Brosnan Blazquez <francis@aspl.es>
To: Len Holgate <len.holgate@gmail.com>
In-Reply-To: <1bc701cc4135$efbf8540$0a00a8c0@Venus>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <4E1BD054.7010103@gmail.com> <1310480036.26452.329.camel@vulcan.aspl.local> <1bc701cc4135$efbf8540$0a00a8c0@Venus>
Content-Type: text/plain; charset="ISO-8859-15"
Organization: ASPL
Date: Wed, 13 Jul 2011 16:27:32 +0200
Message-ID: <1310567252.26452.1396.camel@vulcan.aspl.local>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Wed, 13 Jul 2011 10:22:51 -0700
Cc: 'Hybi' <hybi@ietf.org>, ietf@ietf.org, draft-ietf-hybi-thewebsocketprotocol@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, 13 Jul 2011 14:27:53 -0000

> Francis,

Hi Len,

> I agree with your points and would welcome a max frame size negotiation
> header.

Ok, It shouldn't be a negotiation but an indication to accommodate
communication to each party.

> However, whilst an intermediary might legitimately change the fragmentation
> of a frame it cannot merge complete messages. If, in your example, your
> client limited itself to messages of a certain size

Ok, it is important to note the peer is limiting max frame size not the
message size which may be still infinite in practical terms (63
bits)....and we have fragmentation support to deal with this.

This way intermediaries can split/coalesce fragments according to
receiving peer expectation.

>  then it doesn't matter
> what intermediaries do to the frames as the maximum frame size would be
> limited to the maximum message size that the client sends. The only time
> this wouldn't work is if you were using a 'message of infinite fragments'
> where you start with a fragmented frame and don't know when you'll send the
> final fragment.

Assuming frame size and message size aren't equal, it does matter. 

> The communication between peers about maximum message sizes supported could
> just as easily be in the application level protocol that you're running over
> the websocket connection.

Ok, I see you point and in part you are right, but there is a risk with
this argument:

1) Protocol problems should be solved on its layer, otherwise it will
   cause next layer (application level in this case) to need to solve
   them. It looks reasonable not forcing people to do so.

     Side note: our intention is to layer BEEP on top of websocket, so,
     in practical terms this is not a problem for us because it will
     provide us with all the protection and flow control required.

     However it looks to me this is not a solution for people using
     websocket in other contexts.

2) In general, it has lot of benefits to fragment bigger messages into
   smaller pieces to avoid sick interactions. 

   For example, if you send a really large frame, you won't be able to
   send a control message in the middle until you finish sending the
   frame in place. 

   Having a max frame size indication will help websocket stacks to
   fragment using the right value for each application.

3) No matter API style provided by a websocket stack (frame indication
or stream oriented), having framing running in the background where the
sending peer and intermediaries can coalesce frames without any
indication of the upper level will cause problems that can't be solved
in practical terms by a receiving side. 

In other words, I think having a framing without a max frame size
mechanism (or other mech like ack confirmation, its the same) is like
pretending having a coin with only one side.

> Len
> www.lenholgate.com
> 
> > -----Original Message-----
> > From: hybi-bounces@ietf.org [mailto:hybi-bounces@ietf.org] On 
> > Behalf Of Francis Brosnan Blazquez
> > Sent: 12 July 2011 15:14
> > To: Hybi
> > Cc: ietf@ietf.org; draft-ietf-hybi-thewebsocketprotocol@tools.ietf.org
> > Subject: Re: [hybi] Last Call: 
> > <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket 
> > protocol) to Proposed Standard: request for max frame size
> > 
> > Hi,
> > 
> > Recently, I posted [1] that websocket protocol should include an
> > indication about max frame size that is willing to accept the 
> > connecting
> > peer. 
> > 
> > Many pointed this is not an issue because you could use a stream
> > oriented API (like TCP send/recv and others), but that only 
> > bypasses the
> > problem (in some cases) not solves it.
> > 
> > Websocket protocol is frame based and every frame based protocol
> > designed until now has/need such feature or similar. Even 
> > TCP, for those
> > that proposes to use a stream oriented API as a solution, includes a
> > more complex mechanism than a simple max frame size (window 
> > based ack),
> > so each party can control/inform the sender. This is critical.
> > 
> > A good example for this would be the next. Let suppose you have a
> > constrained memory device (either because it is small or because it
> > accepts a large amount of connections). On that device you deploy a
> > websocket app that only accepts small messages (< 512 bytes, let's
> > say). 
> > 
> > In this context, you can hard code at your web app (javascript) that
> > must not send messages larger than this size (so you control websocket
> > payload size) and in the case you need to, you must split them
> > properly. 
> > 
> > However, even with this mechanism, you have no warranty that 
> > the browser
> > or an intermediary will join those messages into a single 
> > frame, causing
> > your device to receive a bigger message/frame than expected.
> > 
> > Assuming this I think we would require either to include a
> > Max-Frame-Size indication (or a really poor solution: to explicitly
> > state on the draft that frames must not be coalesced by intermediaries
> > or browsers). 
> > 
> > Regards,
> > 
> > [1] http://www.ietf.org/mail-archive/web/hybi/current/msg07641.html
> > -- 
> > Francis Brosnan Blázquez <francis.brosnan@aspl.es>
> > ASPL
> > 91 134 14 22 - 91 134 14 45 - 91 116 07 57
> > 
> > AVISO LEGAL
> > 
> > Este mensaje se dirige exclusivamente a su destinatario. Los datos
> > incluidos en el presente correo son confidenciales y 
> > sometidos a secreto
> > profesional, se prohíbe divulgarlos, en virtud de las leyes 
> > vigentes. Si
> > usted no lo es y lo ha recibido por error o tiene 
> > conocimiento del mismo
> > por cualquier motivo, le rogamos que nos lo comunique por este medio y
> > proceda a destruirlo o borrarlo.
> > 
> > En virtud de lo dispuesto en la Ley Orgánica 15/1999, de 13 de
> > diciembre, de Protección de Datos de Carácter Personal, le 
> > informamos de
> > que sus datos de carácter personal, recogidos de fuentes accesibles al
> > público o datos que usted nos ha facilitado previamente, proceden de
> > bases de datos propiedad de Advanced Software Production Line, S.L.
> > (ASPL). No obstante, usted puede ejercitar sus derechos de acceso,
> > rectificación, cancelación y oposición dispuestos en la mencionada Ley
> > Orgánica, notificándolo por escrito a:
> > ASPL - Protección Datos, C/Antonio Suárez 10 A-102, 28802, Alcalá de
> > Henares (Madrid).
> > 
> > _______________________________________________
> > hybi mailing list
> > hybi@ietf.org
> > https://www.ietf.org/mailman/listinfo/hybi
> > 
> 

-- 
Francis Brosnan Blázquez <francis.brosnan@aspl.es>
ASPL
91 134 14 22 - 91 134 14 45 - 91 116 07 57

AVISO LEGAL

Este mensaje se dirige exclusivamente a su destinatario. Los datos
incluidos en el presente correo son confidenciales y sometidos a secreto
profesional, se prohíbe divulgarlos, en virtud de las leyes vigentes. Si
usted no lo es y lo ha recibido por error o tiene conocimiento del mismo
por cualquier motivo, le rogamos que nos lo comunique por este medio y
proceda a destruirlo o borrarlo.

En virtud de lo dispuesto en la Ley Orgánica 15/1999, de 13 de
diciembre, de Protección de Datos de Carácter Personal, le informamos de
que sus datos de carácter personal, recogidos de fuentes accesibles al
público o datos que usted nos ha facilitado previamente, proceden de
bases de datos propiedad de Advanced Software Production Line, S.L.
(ASPL). No obstante, usted puede ejercitar sus derechos de acceso,
rectificación, cancelación y oposición dispuestos en la mencionada Ley
Orgánica, notificándolo por escrito a:
ASPL - Protección Datos, C/Antonio Suárez 10 A-102, 28802, Alcalá de
Henares (Madrid).


From bert@secret-wg.org  Wed Jul 13 01:21:24 2011
Return-Path: <bert@secret-wg.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 230B321F8BF6 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 01:21:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eD1gTzNT+RPb for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 01:21:19 -0700 (PDT)
Received: from bert.secret-wg.org (unknown [IPv6:2001:7b8:206:1:0:44bb:77dd:155]) by ietfa.amsl.com (Postfix) with ESMTP id 2BDDC21F8BED for <ietf@ietf.org>; Wed, 13 Jul 2011 01:21:18 -0700 (PDT)
Received: from bert.secret-wg.org (localhost [127.0.0.1]) by bert.secret-wg.org (Postfix) with ESMTP id 28F694AC052; Wed, 13 Jul 2011 10:21:15 +0200 (CEST)
Received: from [IPv6:2001:7b8:206:1:226:b0ff:fee2:a770] (unknown [IPv6:2001:7b8:206:1:226:b0ff:fee2:a770]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by bert.secret-wg.org (Postfix) with ESMTPSA id 0325F4AC00C; Wed, 13 Jul 2011 10:21:15 +0200 (CEST)
Subject: Re: Confidentiality notices on DNS messages
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Bert <bert@secret-wg.org>
In-Reply-To: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com>
Date: Wed, 13 Jul 2011 10:21:13 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <00E4900C-9947-4506-A072-F34B0DDD8DA7@secret-wg.org>
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1084)
X-Virus-Scanned: Bert scanned this mail with ClamAV using ClamSMTP
X-Mailman-Approved-At: Wed, 13 Jul 2011 10:22:51 -0700
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 17:11:22 -0000

On Jul 12, 2011, at 11:28 PM, Barry Leiba wrote:

> I am increasingly seeing IETF participants posting messages to IETF
> mailing lists, sending messages to chairs and ADs, and so on, where
> their messages include confidentiality/security/legal notices at the
> bottom. =20



The first ones have shown up in the DNS !!!!

e.g the BSRPDNSC implementation[*] returns a disclaimer:


dig 10.sin.5.+.rp.secret-wg.org TXT
;; Truncated, retrying in TCP mode.

; <<>> DiG 9.6.0-APPLE-P2 <<>> 10.sin.5.+.rp.secret-wg.org TXT
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14586
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;10.sin.5.+.rp.secret-wg.org. IN	TXT

;; ANSWER SECTION:
10.sin.5.+.rp.secret-wg.org. 10	IN TXT "4.45597888911063"
10.sin.5.+.rp.secret-wg.org. 10	IN TXT "This DNS message (including the =
RR(s) in the additional section) is confidential, proprietary, may be =
subject to copyright and legal privilege and no related rights are =
waived." "If you are not the intended recipient or its agent, any =
review, dissemination, distribution or copying of this DNS message or =
any of its content is strictly prohibited and may be unlawful." "All =
messages may be monitored as permitted by applicable law and regulations =
and our policies to protect our business." "DNS messages are not secure =
and you are deemed to have accepted any risk if you communicate with us =
using DNS." "If received in error, please notify us immediately and =
delete the DNS message (and any of its sections) from any computer or =
any storage medium without printing a copy."

;; Query time: 34 msec
;; SERVER: 213.154.224.155#53(213.154.224.155)
;; WHEN: Wed Jul 13 10:17:21 2011
;; MSG SIZE  rcvd: 851





-- Bert's secretary


[*] BSRPDNSC:  Bert's Secure Reverse Polish DNS Calculator=20
http://bert.secret-wg.org/Tools/index.html#Tool_3=

From psangster@gmail.com  Tue Jul 12 08:25:36 2011
Return-Path: <psangster@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C216821F8B02 for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 08:25:36 -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 J+pomYlggaXN for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2011 08:25:36 -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 08B4E21F8B06 for <ietf@ietf.org>; Tue, 12 Jul 2011 08:25:36 -0700 (PDT)
Received: by pvh18 with SMTP id 18so5488930pvh.31 for <ietf@ietf.org>; Tue, 12 Jul 2011 08:25:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=k/XH+4y2+/1sSgUahkFFzlUH3zs/Ttm5MTh20T40u3U=; b=eYjYCfwzf/o6Y+qmYhKFksMYzgaaQjTdeeMuTBJettvIJsL0OJWqynBvNO1zujaJ8W EYcWdOtx455aIflQ62iVf3UBdW7VKV9WejDtqvvTIRnHaeAM01oPSDgXauoZFEFpc0Sw m9cJtauZeDz6UpMDkbduNZu0lpO0tb3RnyDec=
MIME-Version: 1.0
Received: by 10.68.56.35 with SMTP id x3mr41750pbp.369.1310484335593; Tue, 12 Jul 2011 08:25:35 -0700 (PDT)
Received: by 10.68.56.195 with HTTP; Tue, 12 Jul 2011 08:25:35 -0700 (PDT)
Date: Tue, 12 Jul 2011 08:25:35 -0700
Message-ID: <CADnX8dn8iMZ6YtqotiyyD=L5yHDJUV2Q0ZhtccNCSAj+jM6VUA@mail.gmail.com>
Subject: Looking for room at Hilton
From: Paul Sangster <psangster@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Wed, 13 Jul 2011 10:23:03 -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, 12 Jul 2011 15:25:36 -0000

I'm looking for a room at the Hilton ideally at the IETF rate.  Please
send me a direct e-mail if you have a room that you no longer require.

From tglassey@earthlink.net  Wed Jul 13 10:27:34 2011
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19D3B11E8155 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 10:27:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.443
X-Spam-Level: 
X-Spam-Status: No, score=-2.443 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8kP7wcdrvmDK for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 10:27:33 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by ietfa.amsl.com (Postfix) with ESMTP id 1C25621F886A for <ietf@ietf.org>; Wed, 13 Jul 2011 10:27:33 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=ZY/bZ1Eq2yVVNdQeIZMk5vxoSyoojux7foDFBzC6/SUggtezDfD33k4M66YIjE4S; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [207.111.209.5] (helo=[192.168.1.100]) by elasmtp-banded.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1Qh3Dg-0003q1-5m for ietf@ietf.org; Wed, 13 Jul 2011 13:27:32 -0400
Message-ID: <4E1DD5A6.9010809@earthlink.net>
Date: Wed, 13 Jul 2011 10:28:06 -0700
From: todd glassey <tglassey@earthlink.net>
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.org
Subject: Re: Repetitions and consensus
References: <4E1BB856.7040601@gmail.com>	<201107122251.p6CMpJC6002069@fs4113.wdf.sap.corp> <CAH_y2NHt7BP00OXk8b7bvLE=EGS5_YzfRodUxMCme+Skr+dQ_Q@mail.gmail.com>
In-Reply-To: <CAH_y2NHt7BP00OXk8b7bvLE=EGS5_YzfRodUxMCme+Skr+dQ_Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec7965255099a4010fa742954a566897a579350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 207.111.209.5
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 17:27:34 -0000

On 7/12/2011 4:03 PM, Greg Wilkins wrote:
>   think there is an important message there for the IETF, because the
> establishment of consensus is not by any objective measure and this
> science says that subjective measures can be influe
The real issue is proving the consensus was reasonable after the fact. I 
mean as much as years later there needs to be proof that all IETF 
practices were fair and open - something that they are so far from its 
almost funny.
-- 

Todd S. Glassey
This is from my personal email account and any materials from this account come with personal disclaimers.

Further I OPT OUT of any and all commercial emailings.


From jmh@joelhalpern.com  Wed Jul 13 10:31:06 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 75CFD21F898E; Wed, 13 Jul 2011 10:31:06 -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 vZHhVdkVbARJ; Wed, 13 Jul 2011 10:31:05 -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 6B1AD21F898B; Wed, 13 Jul 2011 10:31:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id CE6883245E54; Wed, 13 Jul 2011 10:31:04 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.154.181.24] (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 A68C032448B8; Wed, 13 Jul 2011 10:31:03 -0700 (PDT)
Message-ID: <4E1DD654.3030603@joelhalpern.com>
Date: Wed, 13 Jul 2011 13:31:00 -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: notes from discussion of KARP design guidelines
References: <4E17210A.1070402@joelhalpern.com> <5662A966-70AD-4A63-BA31-8CE1C9635687@cisco.com> <4E1747BB.8080602@cisco.com> <4E19B2DC.4030003@joelhalpern.com> <4E1CC976.9000007@isi.edu> <4E1CCC76.9090409@cisco.com> <4E1CE644.9090300@isi.edu>
In-Reply-To: <4E1CE644.9090300@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>, "karp@ietf.org" <karp@ietf.org>, IETF discussion list <ietf@ietf.org>, 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: Wed, 13 Jul 2011 17:31:06 -0000

Replacing a widely used term ("on the wire") with term that folks will 
not understand does not seem to me personally to be a benefit.

In terms of this document, I do not see a problem with the usage as it 
is.  This is not a protocol document.  The use of the current term in 
this context seems helpful rather than harmful.

Yours,
Joel

On 7/12/2011 8:26 PM, Joe Touch wrote:
>
>
> On 7/12/2011 3:36 PM, Stewart Bryant wrote:
>> On 12/07/2011 23:23, Joe Touch wrote:
>>> Hi, Joel (et al.),
>>>
>>> On 7/10/2011 7:10 AM, Joel Halpern wrote:
>>>> Joe,
>>>> THE KARP WG Chairs have reviewed your comments, in order to figure out
>>>> what the best way to address them. We would appreciate it if you could
>>>> engage in discussion of this proposal on the KARP working group email
>>>> list. If you feel we are still not understanding your point, we
>>>> would be
>>>> happy to make some time avaialble for discussion at the WG session in
>>>> Quebec City. (Comments from anyone else, particularly WG members, on
>>>> the
>>>> proposals being made by the WG chairs are appreciated as well.)
>>>>
>>>> Rather than a line by line response, we have tried to find the common
>>>> themes and respond to them. If we have missed major issues, please let
>>>> us know.
>>>>
>>>> You raised concern about the use of the term "on-the-wire." Rather than
>>>> replace the term, we would prefer to add descriptive text early in the
>>>> document. This text would note that it is a widely used term in IETF
>>>> documents, including many RFCs. It would also state for clarity that in
>>>> this document it is used to refer to the message sent from one routing
>>>> process to another.
>>>
>>> That's a great example of why this term should be removed. The message
>>> sent from one BGP to another is sent *inside* a TCP connection, and
>>> nobody would ever call the TCP bytestream payload the message "on the
>>> wire".
>>>
>>> This term is simply sloppy, and just as the security community rightly
>>> raises issues with similarly poor use of its terms (e.g., "random"
>>> where pseudorandom or arbitrary are intended, or "authenticated" where
>>> integrity protection is intended), I consider this a *significant*
>>> transport issue.
>>
>> Joe
>>
>> Please can you suggest a suitable generic term that covers the
>> set of cases that we need to deal with in routing - i.e.
>> over the MAC, over IP, over UDP and over TCP, so that we can
>> discuss inter routing entity message passing as an abstract
>> operation.
>>
>> As Joel says when we get to the detailed design of each routing
>> protocol we will discuss the details, but we want a high level
>> discussion in this document.
>>
>> Note BTW that 186 RFCs use the term "on the wire" in this
>> sort of situation.
>
> I counted nearly 210, when including "over the wire" too. There are
> similar misuses of, e.g., security terms, though, so let's not let past
> errors suggest continued use.
>
> That said, let's proceed:
>
> First, when you say "on the wire" do you mean:
>
> (A)- the routing protocol data units (RPDUs)
>
> (B)- way in which RPDUs are exchanged
> this includes message payloads, meta-info
> (header information), and any other info
> at other layers beyond RPDUs that the routing
> protocol uses or relies upon
>
> I'm presuming the term "on the wire" is intended to differentiate
> between (A) and (B).
>
> There's no good way to describe (B) as a single entity because it's not
> one. You basically are differentiating between the message and the means
> of its communication. The latter is often called a 'channel' in other
> contexts, so maybe that's the term you want - a way to protect the
> 'channel'.
>
> Joe
>
>
>
>
>
>

From fred@cisco.com  Wed Jul 13 11:00:24 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 A293F21F8BCD for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 11:00:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.5
X-Spam-Level: 
X-Spam-Status: No, score=-104.5 tagged_above=-999 required=5 tests=[AWL=-2.657, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, SUBJECT_FUZZY_TION=0.156, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6xz1PfSZoT5G for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 11:00:23 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 83DDE21F8BC9 for <ietf@ietf.org>; Wed, 13 Jul 2011 11:00:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=1601; q=dns/txt; s=iport; t=1310580022; x=1311789622; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=ic4Z0DrRspIYwhWYI5H9yZpHAqK/3E5/gaXzcinZSvQ=; b=ddST+y1V6Ddsh6VgSG+5zyBEiw+Qw3YfS7Rmdq8g7qqgTYtWP+0lALnJ xSIaDAlAVk30pNx7E7hM55Z7ZxY4jKWe672lPt2jxu01NWqaj7Rsb2Nyt 8XJTLif7dMYd+uEDcKVgsiID3j3h2VSg9o5Zl7+O2qAx05/yRZXHx4VV9 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAOnbHU6rRDoJ/2dsb2JhbABTpzt3rjmeLoVbXwSSYYR/i2k
X-IronPort-AV: E=Sophos;i="4.65,526,1304294400";  d="scan'208";a="2632379"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by rcdn-iport-5.cisco.com with ESMTP; 13 Jul 2011 18:00:21 +0000
Received: from Freds-Computer.local (sjc-vpn7-1132.cisco.com [10.21.148.108]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p6DI0Ksw023176; Wed, 13 Jul 2011 18:00:21 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Wed, 13 Jul 2011 14:00:21 -0400
X-PGP-Universal: processed; by Freds-Computer.local on Wed, 13 Jul 2011 14:00:21 -0400
Subject: Re: Repetitions and consensus
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4E1BB856.7040601@gmail.com>
Date: Wed, 13 Jul 2011 14:00:09 -0400
Message-Id: <A2D629D7-BF2A-4BF9-BDFB-709B70F7B3A8@cisco.com>
References: <4E1BB856.7040601@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 18:00:24 -0000

On Jul 11, 2011, at 10:58 PM, Brian E Carpenter wrote:
> We quite often discuss here how to judge rough consensus. In a =
completely non-IETF context, I came upon a reference to an article =
published in 2007 with the catchy title "Inferring the Popularity of an =
Opinion =46rom Its Familiarity: A Repetitive Voice Can Sound Like a =
Chorus".=20

We deal with that quite a bit. I can think of discussions in v6ops and =
on this list in which a single person contributed one message in four in =
a 200+ message thread, and although he was the lone speaker with that =
viewpoint, my co-chair told me he thought we lacked consensus.

To my mind, it's not a matter of voting (how many people think A, how =
many people think B, ...) and not a matter of volume (which would accept =
a filibuster as a showstopper). It's a question of the preponderance of =
opinion ("agreement, harmony, concurrence, accord, unity, unanimity, =
solidarity; formal concord") coupled with listening carefully to those =
who disagree and determining whether their arguments actually make sense =
and point up an issue. I will recognize a single person's point at issue =
if it appears that they are not being listened to or their issue dealt =
with. If they are simply hammering a point, and their point is =
incorrect, I will note that they have been hammering an incorrect point =
("even though you are sending one email in four in a long thread and are =
expressing extreme concern about a draft because it does ____, I will =
overlook your objections because it doesn't do that.") and move on.


From touch@isi.edu  Wed Jul 13 11:02:43 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 E198C21F8BC8; Wed, 13 Jul 2011 11:02:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.618
X-Spam-Level: 
X-Spam-Status: No, score=-103.618 tagged_above=-999 required=5 tests=[AWL=-1.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 6TynD7vrKf40; Wed, 13 Jul 2011 11:02:43 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 56C6A21F8BC9; Wed, 13 Jul 2011 11:02:37 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id p6DI2P18014919 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 13 Jul 2011 11:02:27 -0700 (PDT)
Message-ID: <4E1DDDB1.4020902@isi.edu>
Date: Wed, 13 Jul 2011 11:02:25 -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: notes from discussion of KARP design guidelines
References: <4E17210A.1070402@joelhalpern.com> <5662A966-70AD-4A63-BA31-8CE1C9635687@cisco.com> <4E1747BB.8080602@cisco.com> <4E19B2DC.4030003@joelhalpern.com> <4E1CC976.9000007@isi.edu> <4E1CCC76.9090409@cisco.com> <4E1CE644.9090300@isi.edu> <4E1DD654.3030603@joelhalpern.com>
In-Reply-To: <4E1DD654.3030603@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>, "karp@ietf.org" <karp@ietf.org>, IETF discussion list <ietf@ietf.org>, 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: Wed, 13 Jul 2011 18:02:44 -0000

Hi, Joel,

On 7/13/2011 10:31 AM, Joel M. Halpern wrote:
> Replacing a widely used term ("on the wire") with term that folks will
> not understand does not seem to me personally to be a benefit.

The problem is that "on the wire" is ambiguous. Many people think they 
know what it means definitively, but their views vary widely.

> In terms of this document, I do not see a problem with the usage as it
> is. This is not a protocol document. The use of the current term in this
> context seems helpful rather than harmful.

Since the whole point of this doc centers around protecting the way 
messages are exchanged, not the messages themselves (e.g., as would be 
the case with signed BGP routes), this is a crucial issue to make clear 
and precise in this doc.

Joe

> On 7/12/2011 8:26 PM, Joe Touch wrote:
>>
>>
>> On 7/12/2011 3:36 PM, Stewart Bryant wrote:
>>> On 12/07/2011 23:23, Joe Touch wrote:
>>>> Hi, Joel (et al.),
>>>>
>>>> On 7/10/2011 7:10 AM, Joel Halpern wrote:
>>>>> Joe,
>>>>> THE KARP WG Chairs have reviewed your comments, in order to figure out
>>>>> what the best way to address them. We would appreciate it if you could
>>>>> engage in discussion of this proposal on the KARP working group email
>>>>> list. If you feel we are still not understanding your point, we
>>>>> would be
>>>>> happy to make some time avaialble for discussion at the WG session in
>>>>> Quebec City. (Comments from anyone else, particularly WG members, on
>>>>> the
>>>>> proposals being made by the WG chairs are appreciated as well.)
>>>>>
>>>>> Rather than a line by line response, we have tried to find the common
>>>>> themes and respond to them. If we have missed major issues, please let
>>>>> us know.
>>>>>
>>>>> You raised concern about the use of the term "on-the-wire." Rather
>>>>> than
>>>>> replace the term, we would prefer to add descriptive text early in the
>>>>> document. This text would note that it is a widely used term in IETF
>>>>> documents, including many RFCs. It would also state for clarity
>>>>> that in
>>>>> this document it is used to refer to the message sent from one routing
>>>>> process to another.
>>>>
>>>> That's a great example of why this term should be removed. The message
>>>> sent from one BGP to another is sent *inside* a TCP connection, and
>>>> nobody would ever call the TCP bytestream payload the message "on the
>>>> wire".
>>>>
>>>> This term is simply sloppy, and just as the security community rightly
>>>> raises issues with similarly poor use of its terms (e.g., "random"
>>>> where pseudorandom or arbitrary are intended, or "authenticated" where
>>>> integrity protection is intended), I consider this a *significant*
>>>> transport issue.
>>>
>>> Joe
>>>
>>> Please can you suggest a suitable generic term that covers the
>>> set of cases that we need to deal with in routing - i.e.
>>> over the MAC, over IP, over UDP and over TCP, so that we can
>>> discuss inter routing entity message passing as an abstract
>>> operation.
>>>
>>> As Joel says when we get to the detailed design of each routing
>>> protocol we will discuss the details, but we want a high level
>>> discussion in this document.
>>>
>>> Note BTW that 186 RFCs use the term "on the wire" in this
>>> sort of situation.
>>
>> I counted nearly 210, when including "over the wire" too. There are
>> similar misuses of, e.g., security terms, though, so let's not let past
>> errors suggest continued use.
>>
>> That said, let's proceed:
>>
>> First, when you say "on the wire" do you mean:
>>
>> (A)- the routing protocol data units (RPDUs)
>>
>> (B)- way in which RPDUs are exchanged
>> this includes message payloads, meta-info
>> (header information), and any other info
>> at other layers beyond RPDUs that the routing
>> protocol uses or relies upon
>>
>> I'm presuming the term "on the wire" is intended to differentiate
>> between (A) and (B).
>>
>> There's no good way to describe (B) as a single entity because it's not
>> one. You basically are differentiating between the message and the means
>> of its communication. The latter is often called a 'channel' in other
>> contexts, so maybe that's the term you want - a way to protect the
>> 'channel'.
>>
>> Joe
>>
>>
>>
>>
>>
>>

From dougb@dougbarton.us  Wed Jul 13 11:21:10 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 96F5521F8C0F for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 11:21:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.492
X-Spam-Level: 
X-Spam-Status: No, score=-3.492 tagged_above=-999 required=5 tests=[AWL=-0.049, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wtn0yEmdqFXw for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 11:21:09 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 8719621F8C0E for <ietf@ietf.org>; Wed, 13 Jul 2011 11:21:09 -0700 (PDT)
Received: (qmail 8928 invoked by uid 399); 13 Jul 2011 18:21:05 -0000
Received: from unknown (HELO 65-241-43-4.globalsuite.net) (dougb@dougbarton.us@65.241.43.4) by mail2.fluidhosting.com with ESMTPAM; 13 Jul 2011 18:21:05 -0000
X-Originating-IP: 65.241.43.4
X-Sender: dougb@dougbarton.us
Message-ID: <4E1DE20F.709@dougbarton.us>
Date: Wed, 13 Jul 2011 11:21:03 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110706 Thunderbird/5.0
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
Subject: Re: Repetitions and consensus
References: <4E1BB856.7040601@gmail.com> <A2D629D7-BF2A-4BF9-BDFB-709B70F7B3A8@cisco.com>
In-Reply-To: <A2D629D7-BF2A-4BF9-BDFB-709B70F7B3A8@cisco.com>
X-Enigmail-Version: 1.2pre
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 18:21:10 -0000

On 07/13/2011 11:00, Fred Baker wrote:
> To my mind, it's not a matter of voting (how many people think A, how many people think B, ...) and not a matter of volume (which would accept a filibuster as a showstopper). It's a question of the preponderance of opinion ("agreement, harmony, concurrence, accord, unity, unanimity, solidarity; formal concord") coupled with listening carefully to those who disagree and determining whether their arguments actually make sense and point up an issue. I will recognize a single person's point at issue if it appears that they are not being listened to or their issue dealt with. If they are simply hammering a point, and their point is incorrect, I will note that they have been hammering an incorrect point ("even though you are sending one email in four in a long thread and are expressing extreme concern about a draft because it does ____, I will overlook your objections because it doesn't do that.") and move on.

Fred has stated in a much more elegant and complete way what I was
trying to get across the other day when I said "consensus is not the
same as universal agreement."

And I'd also like to, um, repeat support for the concepts discussed in
the article Brian posted. I actually studied social psych. a bit in
college and even way back then these ideas were well understood. Deeply
ingrained human tendencies on both individual and group levels really
militate against what most people would consider to be rational,
objective thought on just about any topic. It gets worse geometrically
when it's something about which you care deeply.

An interesting site that approaches these topics from a fun, although
comparatively rigorous viewpoint is http://youarenotsosmart.com/. Of
particular interest to this group are the articles on confirmation bias,
and the Texas sharpshooter fallacy.


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 wes@mti-systems.com  Wed Jul 13 11:24:11 2011
Return-Path: <wes@mti-systems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6C2F21F8C2C for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 11:24: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 gWWC343ddajX for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 11:24:11 -0700 (PDT)
Received: from omr5.networksolutionsemail.com (omr5.networksolutionsemail.com [205.178.146.55]) by ietfa.amsl.com (Postfix) with ESMTP id A94C921F8C25 for <ietf@ietf.org>; Wed, 13 Jul 2011 11:24:07 -0700 (PDT)
Received: from cm-omr1 (mail.networksolutionsemail.com [205.178.146.50]) by omr5.networksolutionsemail.com (8.13.6/8.13.6) with ESMTP id p6DIO2MU028857 for <ietf@ietf.org>; Wed, 13 Jul 2011 14:24:07 -0400
Authentication-Results: cm-omr1 smtp.user=wes@mti-systems.com; auth=pass (PLAIN)
X-Authenticated-UID: wes@mti-systems.com
Received: from [107.46.81.255] ([107.46.81.255:58078] helo=[192.168.9.2]) by cm-omr1 (envelope-from <wes@mti-systems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id D8/8B-29864-5C2ED1E4; Wed, 13 Jul 2011 14:24:06 -0400
Message-ID: <4E1DE2C2.8090209@mti-systems.com>
Date: Wed, 13 Jul 2011 14:24:02 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
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: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: notes from discussion of KARP design guidelines
References: <4E17210A.1070402@joelhalpern.com>	<5662A966-70AD-4A63-BA31-8CE1C9635687@cisco.com>	<4E1747BB.8080602@cisco.com> <4E19B2DC.4030003@joelhalpern.com>	<4E1CC976.9000007@isi.edu> <4E1CCC76.9090409@cisco.com>	<4E1CE644.9090300@isi.edu> <4E1DD654.3030603@joelhalpern.com>
In-Reply-To: <4E1DD654.3030603@joelhalpern.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: stbryant@cisco.com, "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, "karp@ietf.org" <karp@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, 13 Jul 2011 18:24:11 -0000

On 7/13/2011 1:31 PM, Joel M. Halpern wrote:
> Replacing a widely used term ("on the wire") with term that folks will
> not understand does not seem to me personally to be a benefit.

I think Joe's point is that it's widely used as a concept, but what
it means specifically in this document is not clear.  A sentence to
clarify up-front what the definition is in this document might be
enough.


> In terms of this document, I do not see a problem with the usage as it
> is. This is not a protocol document. The use of the current term in this
> context seems helpful rather than harmful.

It might be reasonable to add a sentence that says, "In this document,
'on the wire' refers to (A) the routing protocol data itself, as well
as (B) the way in which routing protocol data is exchanged using
underlying protocols, including the headers and other meta-data used by
those underlying protocols", or something like that?

To me, that's a lot more useful than saying "this term is commonly
used" without defining in what sense(s) you mean it in the present
document.

I think it's important because the protections possible are
potentially a lot different, and if you want people to think
about only one or both, it should be made explicit.

On a lighter note, I once generated a lot of confusion using this
term with people working on satellite networks, who were wondering
what wires I could possibly be talking about since all of our links
were microwave.  I guess if KARP covered MANET protocols we'd have
to protect them "on the wireless".

-- 
Wes Eddy
MTI Systems

From jmh@joelhalpern.com  Wed Jul 13 11:34:30 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 A13F4228006; Wed, 13 Jul 2011 11:34:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, 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 QGbRLqks5lZY; Wed, 13 Jul 2011 11:34:30 -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 0335422800F; Wed, 13 Jul 2011 11:34:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 3626F3245DBB; Wed, 13 Jul 2011 11:34:29 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.154.181.24] (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 3023F32462B0; Wed, 13 Jul 2011 11:34:28 -0700 (PDT)
Message-ID: <4E1DE530.5060701@joelhalpern.com>
Date: Wed, 13 Jul 2011 14:34:24 -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: Wesley Eddy <wes@mti-systems.com>
Subject: Re: notes from discussion of KARP design guidelines
References: <4E17210A.1070402@joelhalpern.com>	<5662A966-70AD-4A63-BA31-8CE1C9635687@cisco.com>	<4E1747BB.8080602@cisco.com> <4E19B2DC.4030003@joelhalpern.com>	<4E1CC976.9000007@isi.edu> <4E1CCC76.9090409@cisco.com>	<4E1CE644.9090300@isi.edu> <4E1DD654.3030603@joelhalpern.com> <4E1DE2C2.8090209@mti-systems.com>
In-Reply-To: <4E1DE2C2.8090209@mti-systems.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: stbryant@cisco.com, "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, "karp@ietf.org" <karp@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, 13 Jul 2011 18:34:30 -0000

As I said in my earlier note proposing responses to Joe, we would be 
happy to some text in the front clarifying the usage.  Quoting from my 
earlier email:

This text would note that it is a widely used term in IETF documents, 
including many RFCs.  It would also state for clarity that in this 
document it is used to refer to the message sent from one routing 
process to another.

Apparently, this does not address Joe's concern.

Yours,
Joel

On 7/13/2011 2:24 PM, Wesley Eddy wrote:
> On 7/13/2011 1:31 PM, Joel M. Halpern wrote:
>> Replacing a widely used term ("on the wire") with term that folks will
>> not understand does not seem to me personally to be a benefit.
>
> I think Joe's point is that it's widely used as a concept, but what
> it means specifically in this document is not clear. A sentence to
> clarify up-front what the definition is in this document might be
> enough.

...

From wes@mti-systems.com  Wed Jul 13 11:47:07 2011
Return-Path: <wes@mti-systems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E14111E80B2 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 11:47: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 IHxHoR3qqVDJ for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 11:47:07 -0700 (PDT)
Received: from omr10.networksolutionsemail.com (omr10.networksolutionsemail.com [205.178.146.60]) by ietfa.amsl.com (Postfix) with ESMTP id BFDB511E8129 for <ietf@ietf.org>; Wed, 13 Jul 2011 11:47:06 -0700 (PDT)
Received: from cm-omr1 (mail.networksolutionsemail.com [205.178.146.50]) by omr10.networksolutionsemail.com (8.13.6/8.13.6) with ESMTP id p6DIl6AM032537 for <ietf@ietf.org>; Wed, 13 Jul 2011 14:47:06 -0400
Authentication-Results: cm-omr1 smtp.user=wes@mti-systems.com; auth=pass (PLAIN)
X-Authenticated-UID: wes@mti-systems.com
Received: from [107.46.81.255] ([107.46.81.255:59849] helo=[192.168.9.2]) by cm-omr1 (envelope-from <wes@mti-systems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id EF/E1-29864-828ED1E4; Wed, 13 Jul 2011 14:47:06 -0400
Message-ID: <4E1DE827.8000300@mti-systems.com>
Date: Wed, 13 Jul 2011 14:47:03 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
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: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: notes from discussion of KARP design guidelines
References: <4E17210A.1070402@joelhalpern.com>	<5662A966-70AD-4A63-BA31-8CE1C9635687@cisco.com>	<4E1747BB.8080602@cisco.com> <4E19B2DC.4030003@joelhalpern.com>	<4E1CC976.9000007@isi.edu> <4E1CCC76.9090409@cisco.com>	<4E1CE644.9090300@isi.edu> <4E1DD654.3030603@joelhalpern.com> <4E1DE2C2.8090209@mti-systems.com> <4E1DE530.5060701@joelhalpern.com>
In-Reply-To: <4E1DE530.5060701@joelhalpern.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: stbryant@cisco.com, "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, "karp@ietf.org" <karp@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, 13 Jul 2011 18:47:07 -0000

On 7/13/2011 2:34 PM, Joel M. Halpern wrote:
> As I said in my earlier note proposing responses to Joe, we would be
> happy to some text in the front clarifying the usage. Quoting from my
> earlier email:
>
> This text would note that it is a widely used term in IETF documents,
> including many RFCs. It would also state for clarity that in this
> document it is used to refer to the message sent from one routing
> process to another.
>
> Apparently, this does not address Joe's concern.
>

"message sent from one routing process to another" doesn't seem to be
right to me either since it sounds like the first definition that
covers routing protocol data only, and not underlying protocols, so I
wouldn't expect that proposal to address Joe's concern.

-- 
Wes Eddy
MTI Systems

From touch@isi.edu  Wed Jul 13 11:59:25 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 A7CBF11E813F; Wed, 13 Jul 2011 11:59:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.572
X-Spam-Level: 
X-Spam-Status: No, score=-103.572 tagged_above=-999 required=5 tests=[AWL=-0.973, 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 HvmgYJY07lwi; Wed, 13 Jul 2011 11:59:25 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 10DB711E80AF; Wed, 13 Jul 2011 11:59:25 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id p6DIwp3r001226 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 13 Jul 2011 11:58:51 -0700 (PDT)
Message-ID: <4E1DEAEB.9040208@isi.edu>
Date: Wed, 13 Jul 2011 11:58:51 -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: notes from discussion of KARP design guidelines
References: <4E17210A.1070402@joelhalpern.com>	<5662A966-70AD-4A63-BA31-8CE1C9635687@cisco.com>	<4E1747BB.8080602@cisco.com> <4E19B2DC.4030003@joelhalpern.com>	<4E1CC976.9000007@isi.edu> <4E1CCC76.9090409@cisco.com>	<4E1CE644.9090300@isi.edu> <4E1DD654.3030603@joelhalpern.com> <4E1DE2C2.8090209@mti-systems.com> <4E1DE530.5060701@joelhalpern.com>
In-Reply-To: <4E1DE530.5060701@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>, stbryant@cisco.com, IETF discussion list <ietf@ietf.org>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 18:59:25 -0000

On 7/13/2011 11:34 AM, Joel M. Halpern wrote:
> As I said in my earlier note proposing responses to Joe, we would be
> happy to some text in the front clarifying the usage. Quoting from my
> earlier email:
>
> This text would note that it is a widely used term in IETF documents,
> including many RFCs. It would also state for clarity that in this
> document it is used to refer to the message sent from one routing
> process to another.

Here's why this is a problem:

1- does this refer to signing a BGP path?

2- does this refer to protecting the channel over which BGP paths are 
exchanged?

 From the intro:
    Four main steps were identified for that tightening:

       o  More secure mechanisms and practices for operating routers.
    ...

       o  Cleaning up the Internet Routing Registry repository [IRR],
    ...

       o  Specifications for cryptographic validation of routing message
          content.
    ...

       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.

So this document is clearly NOT about "the message from one routing 
process to another (that would be 'routing message content', IMO). I.e., 
this doc focuses on securing the transfer mechanism NOT the message.

Thus this is the key to the entirety of the doc. This doc needs to be 
very clear about what this is, at which point it can certainly also then 
refer back to the original RFC (e.g., "this is referred to in RFC 4948 
as 'on the wire'").

Joe



From hsantos@isdg.net  Wed Jul 13 12:22:22 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 EEF4711E80E5 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 12:22:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.991
X-Spam-Level: 
X-Spam-Status: No, score=-3.991 tagged_above=-999 required=5 tests=[AWL=-2.148, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UpwbRMx1SOpS for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 12:22:22 -0700 (PDT)
Received: from mail.winserver.com (mail.santronics.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id BF69311E80C8 for <ietf@ietf.org>; Wed, 13 Jul 2011 12:22:21 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple; l=2697; t=1310584937; h=Message-ID:Date:From:Organization:To: Subject; bh=pgZ80o51OTak9DEu1FIledSWL/Q=; b=pLHym8hEeRFDcfXjseVJ k1gIpmszqkaNVSAzBdGALynovyaOVmSeSKiVs8vvJLmox5uQp0LbRjtQFDo39p+9 CBAN7LjFb6YZMjbH7qXci6vmkpfY8J2YzRa3/VzApQR3wvGYdhWWiskhlIDQct50 k235XbiGuzZEdTc4B8AlVHw=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Wed, 13 Jul 2011 15:22:17 -0400
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 3335408473.2999.4376; Wed, 13 Jul 2011 15:22:15 -0400
Received: by beta.winserver.com (Wildcat! SMTP Router v6.3.453.2) for ietf@ietf.org; Wed, 13 Jul 2011 15:18:17 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.3.453.2) with ESMTP id 11735315; Wed, 13 Jul 2011 15:18:16 -0400
Message-ID: <4E1DF065.5080305@isdg.net>
Date: Wed, 13 Jul 2011 15:22:13 -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: Fred Baker <fred@cisco.com>
Subject: Re: Repetitions and consensus
References: <4E1BB856.7040601@gmail.com> <A2D629D7-BF2A-4BF9-BDFB-709B70F7B3A8@cisco.com>
In-Reply-To: <A2D629D7-BF2A-4BF9-BDFB-709B70F7B3A8@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 19:22:23 -0000

The process seems to be today what I call "Consensus by Osmosis." 
People get tired of the highly mixed discipline subjective 
philosophies, many times subject to personal agendas, and conflict of 
interest, many get shouted out even to the extent of ignorance at the 
suggestion of key cogs. So even if there was a healthy sampling of 
participants, at some point, its filtered by osmosis and often there 
is already an handicap with editors providing +1s the WG has to 
overcome when a change is in disagreement but doesn't reach the "rough 
consensus."   In my view, the process is outdated. It may sense 20-30 
years ago when there were still a world of unknowns and hard "rough 
consensus" decisions had to made.  But today, to me, a rough consensus 
made - both sides are worthy ideas and compromises need to made rather 
than a cold cutoff of nearly half a WG.  My opinion.

Fred Baker wrote:
> On Jul 11, 2011, at 10:58 PM, Brian E Carpenter wrote:
>> We quite often discuss here how to judge rough consensus. In a completely non-IETF context, I came upon a reference to an article published in 2007 with the catchy title "Inferring the Popularity of an Opinion From Its Familiarity: A Repetitive Voice Can Sound Like a Chorus". 
> 
> We deal with that quite a bit. I can think of discussions in v6ops and on this list in which a single person contributed one message in four in a 200+ message thread, and although he was the lone speaker with that viewpoint, my co-chair told me he thought we lacked consensus.
> 
> To my mind, it's not a matter of voting (how many people think A, how many people think B, ...) and not a matter of volume (which would accept a filibuster as a showstopper). It's a question of the preponderance of opinion ("agreement, harmony, concurrence, accord, unity, unanimity, solidarity; formal concord") coupled with listening carefully to those who disagree and determining whether their arguments actually make sense and point up an issue. I will recognize a single person's point at issue if it appears that they are not being listened to or their issue dealt with. If they are simply hammering a point, and their point is incorrect, I will note that they have been hammering an incorrect point ("even though you are sending one email in four in a long thread and are expressing extreme concern about a draft because it does ____, I will overlook your objections because it doesn't do that.") and move on.
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
> 

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com




From moore@network-heretics.com  Wed Jul 13 12:55: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 2FB4F21F8B20 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 12:55:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.139
X-Spam-Level: 
X-Spam-Status: No, score=-3.139 tagged_above=-999 required=5 tests=[AWL=-0.296, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mp3aCllUvLQC for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 12:55: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 DA26F21F8B1F for <ietf@ietf.org>; Wed, 13 Jul 2011 12:55:39 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id BFEB020814; Wed, 13 Jul 2011 15:55:37 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Wed, 13 Jul 2011 15:55: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=rAZkvrxJPEfTS75FI8E0npQp7w8=; b=sEkPpLf2zVEEB03LwPJekmV9lA/mrJYxIy3AmuD8OSxOFUJNswTDR2rDa+fWFnAr59umid6ZXuVDVN/0U3I0YyH9OyjnAnyb4xQbI6djUlm1LN/cyNDCSP9T9xBifveLsnftysYwlM/nwd3a3B+S2ylYgGtCMe1hv/vQ50AL6Es=
X-Sasl-enc: cu3TkhVtMSfkJuMz6cm6fd/PmpK3W4Xm0xsJYpDEgjIf 1310586937
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 B443C4020F3; Wed, 13 Jul 2011 15:55:36 -0400 (EDT)
Subject: Re: Repetitions and consensus
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: <A2D629D7-BF2A-4BF9-BDFB-709B70F7B3A8@cisco.com>
Date: Wed, 13 Jul 2011 15:55:35 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <BBA147A8-968E-4330-94CA-8BED3CDDA562@network-heretics.com>
References: <4E1BB856.7040601@gmail.com> <A2D629D7-BF2A-4BF9-BDFB-709B70F7B3A8@cisco.com>
To: Fred Baker <fred@cisco.com>
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: Wed, 13 Jul 2011 19:55:44 -0000

On Jul 13, 2011, at 2:00 PM, Fred Baker wrote:

> On Jul 11, 2011, at 10:58 PM, Brian E Carpenter wrote:
>> We quite often discuss here how to judge rough consensus. In a =
completely non-IETF context, I came upon a reference to an article =
published in 2007 with the catchy title "Inferring the Popularity of an =
Opinion =46rom Its Familiarity: A Repetitive Voice Can Sound Like a =
Chorus".=20
>=20
> We deal with that quite a bit. I can think of discussions in v6ops and =
on this list in which a single person contributed one message in four in =
a 200+ message thread, and although he was the lone speaker with that =
viewpoint, my co-chair told me he thought we lacked consensus.

There's also a common tendency of some kinds of groups to categorically =
dismiss the opinions of those that they see as outliers, even to the =
point of diminishing their numbers.   If one of those objecting happens =
to defend his viewpoint vigorously and to respond to numerous attacks on =
not only his viewpoint but also his legitimacy, motivation, character, =
etc., there is a tendency among some to dismiss his opinions even more.

All of these clearly happened in recent discussions in v6ops.

It's certainly true that one lone speaker should not be able to deny =
rough consensus to a group.  That's why the consensus only has to be =
"rough".   But if the group doesn't even try to understand a minority =
view, it cannot be said to have tried to reach consensus of any kind.

> To my mind, it's not a matter of voting (how many people think A, how =
many people think B, ...) and not a matter of volume (which would accept =
a filibuster as a showstopper). It's a question of the preponderance of =
opinion ("agreement, harmony, concurrence, accord, unity, unanimity, =
solidarity; formal concord") coupled with listening carefully to those =
who disagree and determining whether their arguments actually make sense =
and point up an issue. I will recognize a single person's point at issue =
if it appears that they are not being listened to or their issue dealt =
with. If they are simply hammering a point, and their point is =
incorrect, I will note that they have been hammering an incorrect point =
("even though you are sending one email in four in a long thread and are =
expressing extreme concern about a draft because it does ____, I will =
overlook your objections because it doesn't do that.") and move on.

I'd agree with that logic.  Though I note that "incorrect" is sometimes =
subjective.

Keith


From joelja@bogus.com  Wed Jul 13 13:11:25 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 AB3A911E8095 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 13:11:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.888
X-Spam-Level: 
X-Spam-Status: No, score=-102.888 tagged_above=-999 required=5 tests=[AWL=-1.045, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, SUBJECT_FUZZY_TION=0.156, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id obzdLLMJgNba for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 13:11:25 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id E214F11E807D for <ietf@ietf.org>; Wed, 13 Jul 2011 13:11:21 -0700 (PDT)
Received: from [172.16.24.53] (host-64-47-136-190.masergy.com [64.47.136.190]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p6DKBJZ0011572 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 13 Jul 2011 20:11:20 GMT (envelope-from joelja@bogus.com)
Subject: Re: Repetitions and consensus
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <BBA147A8-968E-4330-94CA-8BED3CDDA562@network-heretics.com>
Date: Wed, 13 Jul 2011 13:11:13 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B5F354BC-2AD9-45B4-B8DB-02BF81D5DCE2@bogus.com>
References: <4E1BB856.7040601@gmail.com> <A2D629D7-BF2A-4BF9-BDFB-709B70F7B3A8@cisco.com> <BBA147A8-968E-4330-94CA-8BED3CDDA562@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]); Wed, 13 Jul 2011 20:11:20 +0000 (UTC)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 20:11:25 -0000

On Jul 13, 2011, at 12:55 PM, Keith Moore wrote:

> On Jul 13, 2011, at 2:00 PM, Fred Baker wrote:
>=20
>> On Jul 11, 2011, at 10:58 PM, Brian E Carpenter wrote:
>>> We quite often discuss here how to judge rough consensus. In a =
completely non-IETF context, I came upon a reference to an article =
published in 2007 with the catchy title "Inferring the Popularity of an =
Opinion =46rom Its Familiarity: A Repetitive Voice Can Sound Like a =
Chorus".=20
>>=20
>> We deal with that quite a bit. I can think of discussions in v6ops =
and on this list in which a single person contributed one message in =
four in a 200+ message thread, and although he was the lone speaker with =
that viewpoint, my co-chair told me he thought we lacked consensus.
>=20
> There's also a common tendency of some kinds of groups to =
categorically dismiss the opinions of those that they see as outliers, =
even to the point of diminishing their numbers.   If one of those =
objecting happens to defend his viewpoint vigorously and to respond to =
numerous attacks on not only his viewpoint but also his legitimacy, =
motivation, character, etc., there is a tendency among some to dismiss =
his opinions even more.
>=20
> All of these clearly happened in recent discussions in v6ops.
>=20
> It's certainly true that one lone speaker should not be able to deny =
rough consensus to a group.  That's why the consensus only has to be =
"rough".   But if the group doesn't even try to understand a minority =
view, it cannot be said to have tried to reach consensus of any kind.

Quite contrary imho if you want to speak of 6to4-to-historic in =
specific. The viewpoint most effusively expressed by yourself is quite =
well understood. Lack of reconciliation does not imply that it was =
simply swept under the rug.

>> To my mind, it's not a matter of voting (how many people think A, how =
many people think B, ...) and not a matter of volume (which would accept =
a filibuster as a showstopper). It's a question of the preponderance of =
opinion ("agreement, harmony, concurrence, accord, unity, unanimity, =
solidarity; formal concord") coupled with listening carefully to those =
who disagree and determining whether their arguments actually make sense =
and point up an issue. I will recognize a single person's point at issue =
if it appears that they are not being listened to or their issue dealt =
with. If they are simply hammering a point, and their point is =
incorrect, I will note that they have been hammering an incorrect point =
("even though you are sending one email in four in a long thread and are =
expressing extreme concern about a draft because it does ____, I will =
overlook your objections because it doesn't do that.") and move on.
>=20
> I'd agree with that logic.  Though I note that "incorrect" is =
sometimes subjective.

I'd go a little further. It is trivially possible to establish two =
opposing positions neither of which are "wrong".

> Keith
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From moore@network-heretics.com  Wed Jul 13 13:21: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 1E15411E807D for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 13:21:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[AWL=-0.292, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5iEhhH08-Vsq for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 13:21:32 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 4780911E80AC for <ietf@ietf.org>; Wed, 13 Jul 2011 13:21:29 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id E79AE2040A; Wed, 13 Jul 2011 16:21:28 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Wed, 13 Jul 2011 16:21: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=ZuDZVQ1ShZDCQ+l7nC1ZTBNPybo=; b=ptLjdzIKCq6rRGgnq89Ficp/DeVzDsdSnSeg9f9GbSmaW4BW3DBxoBtIW3SoysI0c/dckMMcY/7UAqEP/XD2/sce/3/XFmyh/+5t6mcfxQ4CyViR/JctugtcN3Arbg4MAX4lYLgQUrUA9kiCFEehNSvFReSXUC9Sn7qE5c/9ebc=
X-Sasl-enc: 5YMHv39IxD5Ranp6k9bW6bvdtaRhgjNkYOesX23LAaXP 1310588488
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 EF31B4055D2; Wed, 13 Jul 2011 16:21:27 -0400 (EDT)
Subject: Re: Repetitions and consensus
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: <B5F354BC-2AD9-45B4-B8DB-02BF81D5DCE2@bogus.com>
Date: Wed, 13 Jul 2011 16:21:27 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <518A3B17-BEC5-48E6-8C4F-28CB0D2F76CE@network-heretics.com>
References: <4E1BB856.7040601@gmail.com> <A2D629D7-BF2A-4BF9-BDFB-709B70F7B3A8@cisco.com> <BBA147A8-968E-4330-94CA-8BED3CDDA562@network-heretics.com> <B5F354BC-2AD9-45B4-B8DB-02BF81D5DCE2@bogus.com>
To: Joel Jaeggli <joelja@bogus.com>
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: Wed, 13 Jul 2011 20:21:38 -0000

On Jul 13, 2011, at 4:11 PM, Joel Jaeggli wrote:

>> There's also a common tendency of some kinds of groups to =
categorically dismiss the opinions of those that they see as outliers, =
even to the point of diminishing their numbers.   If one of those =
objecting happens to defend his viewpoint vigorously and to respond to =
numerous attacks on not only his viewpoint but also his legitimacy, =
motivation, character, etc., there is a tendency among some to dismiss =
his opinions even more.
>>=20
>> All of these clearly happened in recent discussions in v6ops.
>>=20
>> It's certainly true that one lone speaker should not be able to deny =
rough consensus to a group.  That's why the consensus only has to be =
"rough".   But if the group doesn't even try to understand a minority =
view, it cannot be said to have tried to reach consensus of any kind.
>=20
> Quite contrary imho if you want to speak of 6to4-to-historic in =
specific. The viewpoint most effusively expressed by yourself is quite =
well understood. Lack of reconciliation does not imply that it was =
simply swept under the rug.

I have recently received several private emails that indicated that =
particular speakers did not understand it, though we were usually able =
to sort out the differences in private conversation.

I certainly don't claim that my concerns were swept under the rug by the =
WG management.  But in a group is largely composed of individuals with a =
particular point-of-view, it can be difficult for members of that group =
to see the merit in the opinion of a minority, or lone speaker, with a =
different point-of-view.  Those who want to categorically dismiss that =
minority viewpoint will get plenty of support from other members in the =
group.

>>> To my mind, it's not a matter of voting (how many people think A, =
how many people think B, ...) and not a matter of volume (which would =
accept a filibuster as a showstopper). It's a question of the =
preponderance of opinion ("agreement, harmony, concurrence, accord, =
unity, unanimity, solidarity; formal concord") coupled with listening =
carefully to those who disagree and determining whether their arguments =
actually make sense and point up an issue. I will recognize a single =
person's point at issue if it appears that they are not being listened =
to or their issue dealt with. If they are simply hammering a point, and =
their point is incorrect, I will note that they have been hammering an =
incorrect point ("even though you are sending one email in four in a =
long thread and are expressing extreme concern about a draft because it =
does ____, I will overlook your objections because it doesn't do that.") =
and move on.
>>=20
>> I'd agree with that logic.  Though I note that "incorrect" is =
sometimes subjective.
>=20
> I'd go a little further. It is trivially possible to establish two =
opposing positions neither of which are "wrong".

Absolutely.

Keith


From jmh@joelhalpern.com  Wed Jul 13 13:44:40 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 BA5C921F8AB0; Wed, 13 Jul 2011 13:44:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.278
X-Spam-Level: 
X-Spam-Status: No, score=-102.278 tagged_above=-999 required=5 tests=[AWL=-0.279, BAYES_00=-2.599, J_CHICKENPOX_43=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 WYzL+SqDjKNI; Wed, 13 Jul 2011 13:44:40 -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 811EF21F8A7E; Wed, 13 Jul 2011 13:44:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id CB0A432444BF; Wed, 13 Jul 2011 13:44:38 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.154.181.24] (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 C2F453244A7B; Wed, 13 Jul 2011 13:44:37 -0700 (PDT)
Message-ID: <4E1E03B2.3010405@joelhalpern.com>
Date: Wed, 13 Jul 2011 16:44:34 -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: Wesley Eddy <wes@mti-systems.com>
Subject: Re: notes from discussion of KARP design guidelines
References: <4E17210A.1070402@joelhalpern.com>	<5662A966-70AD-4A63-BA31-8CE1C9635687@cisco.com>	<4E1747BB.8080602@cisco.com> <4E19B2DC.4030003@joelhalpern.com>	<4E1CC976.9000007@isi.edu> <4E1CCC76.9090409@cisco.com>	<4E1CE644.9090300@isi.edu> <4E1DD654.3030603@joelhalpern.com> <4E1DE2C2.8090209@mti-systems.com> <4E1DE530.5060701@joelhalpern.com> <4E1DE827.8000300@mti-systems.com>
In-Reply-To: <4E1DE827.8000300@mti-systems.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: stbryant@cisco.com, "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, "karp@ietf.org" <karp@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, 13 Jul 2011 20:44:40 -0000

Sorry, I apparently missed part of your earlier note.
Would text like:
    This document uses the term "on-the-wire" to talk about the 
information used by routing systems.  This term is widely used in IETF 
RFCs,but is used in several different ways.  In this document, it is 
used to refer both to information exchanged between routing protocol 
instances, and to underlying protocols that may also need to be 
protected in specific circumstances.  Individual protocol analysis 
documents will need to be more specific in their usage.

work to address the issue?
Yours,
Joel

On 7/13/2011 2:47 PM, Wesley Eddy wrote:
> On 7/13/2011 2:34 PM, Joel M. Halpern wrote:
>> As I said in my earlier note proposing responses to Joe, we would be
>> happy to some text in the front clarifying the usage. Quoting from my
>> earlier email:
>>
>> This text would note that it is a widely used term in IETF documents,
>> including many RFCs. It would also state for clarity that in this
>> document it is used to refer to the message sent from one routing
>> process to another.
>>
>> Apparently, this does not address Joe's concern.
>>
>
> "message sent from one routing process to another" doesn't seem to be
> right to me either since it sounds like the first definition that
> covers routing protocol data only, and not underlying protocols, so I
> wouldn't expect that proposal to address Joe's concern.
>

From jdrake@juniper.net  Wed Jul 13 13:48:50 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 25B3911E8172; Wed, 13 Jul 2011 13:48:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.798
X-Spam-Level: 
X-Spam-Status: No, score=-5.798 tagged_above=-999 required=5 tests=[AWL=0.801,  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 7KUBDFa6IZ8Q; Wed, 13 Jul 2011 13:48:46 -0700 (PDT)
Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169]) by ietfa.amsl.com (Postfix) with ESMTP id AF7FF11E8171; Wed, 13 Jul 2011 13:48:45 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP ID DSNKTh4EpYgppywL+vECy6KA5u1FPSPomo02@postini.com; Wed, 13 Jul 2011 13:48:45 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB03-HQ.jnpr.net ([::1]) with mapi; Wed, 13 Jul 2011 13:46:28 -0700
From: John E Drake <jdrake@juniper.net>
To: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>, "david.i.allan@ericsson.com" <david.i.allan@ericsson.com>, "RCosta@ptinovacao.pt" <RCosta@ptinovacao.pt>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
Date: Wed, 13 Jul 2011 13:46:27 -0700
Subject: RE: [mpls] R: RE: R: Re:	Last	Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>	(Proactive	Connectivity	Verification, Continuity Check and Remote Defect	indication	for	MPLS	Transport	Profile) to Proposed Standard
Thread-Topic: [mpls] R: RE: R: Re:	Last	Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>	(Proactive	Connectivity	Verification, Continuity Check and Remote Defect	indication	for	MPLS	Transport	Profile) to Proposed Standard
Thread-Index: AcxBmzNJGVqWfL2eQJSfSHict657jgAAmysw
Message-ID: <5E893DB832F57341992548CDBB333163A0A91E90F6@EMBX01-HQ.jnpr.net>
References: <31453662.3306881310588795478.JavaMail.defaultUser@defaultHost>
In-Reply-To: <31453662.3306881310588795478.JavaMail.defaultUser@defaultHost>
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: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 20:48:50 -0000

Italo,

The design team report (http://www.ietf.org/proceedings/75/slides/mpls-17/m=
pls-17_files/frame.htm), with Huub's name as an author, details a plan for =
MPLS-TP OAM which the MPLS WG has followed to this day.  I think the report=
 is compelling evidence that the claim that a packet transport network is a=
n MPLS application that intrinsically requires a different OAM solution is =
simply a lame ex post facto attempt to justify the ITU's abrogation of the =
agreement with the IETF (TD07 (WP3/SG15) from December 2008 sourced by SG15=
):

"The ITU-T accepts these recommendations and states that any extensions to =
MPLS technology will be progressed via the IETF standards process using the=
 procedures defined in RFC 4929 (Change Process for Multiprotocol Label Swi=
tching (MPLS) and Generalized MPLS (GMPLS) Protocols and Procedures).  Expe=
rts from the ITU-T will assist the IETF in the development of RFCs that des=
cribe the transport extensions by providing input to and review of the draf=
ts as they are progressed via the IETF standards process.. The ITU-T will d=
evelop new or revised Recommendations that will allow IETF MPLS-TP to be in=
tegrated into the transport network including integration with the existing=
 equipment, and operations infrastructure.  These Recommendations will make=
 normative references to the base IETF MPLS-TP technology and will be devel=
oped with input from and review by experts from the IETF to ensure consiste=
ncy with MPLS-TP...

The ITU-T has accepted the proposals from the JWT and we look forward to co=
ntinuing the cooperative development of IETF MPLS to address the needs of t=
he transport network. We also believe that this resolution will fulfil the =
mutual goal of improve the functionality of the internet and transport netw=
orks and guaranteeing complete interoperability and architectural soundness=
."

Thanks,

John

Sent from my iPhone

> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> erminio.ottone_69@libero.it
> Sent: Wednesday, July 13, 2011 1:27 PM
> To: david.i.allan@ericsson.com; RCosta@ptinovacao.pt; ietf@ietf.org;
> IETF-Announce
> Cc: mpls@ietf.org
> Subject: [mpls] R: RE: R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
> 05.txt> (Proactive Connectivity Verification, Continuity Check and
> Remote Defect indication for MPLS Transport Profile) to Proposed
> Standard
>=20
> >However this is a consequence of adapting an existing technology to a
> new
> application. I do not see any way around that. And the entire joint
> project was
> based on the premise of engineering re-use not greenfield design. That
> is what
> it said on the tin up front, and IMO why when the IETF started down
> this path
> packet transport transitioned from being a minority sport to
> mainstream, so it
> is a bit late to cry foul....
>=20
> This is not what the IETF has committed to deliver to ITU-T and in fact
> slide
> 44 postpones to the OAM design phase "decide whether LSP-Ping or BFD
> can or
> should be tweaked or not" and slide 46 reckons "many options including
> non IP
> BFD is an option encapsulation of Y.1731 PDU"
>=20
> It seems to me after having read the draft and followed this very long
> thread
> that tweaking BFD is not the right approach to meet ITU-T requirements
> so it
> would be worth evaluating the other alternative considered viable by
> the JWT
> which is encapulating Y.1731 PDUs.
>=20
> >----Messaggio originale----
> >Da: david.i.allan@ericsson.com
> >Data: 6-lug-2011 20.24
> >A: "erminio.ottone_69@libero.it"<erminio.ottone_69@libero.it>,
> "RCosta@ptinovacao.pt"<RCosta@ptinovacao.pt>,
> "ietf@ietf.org"<ietf@ietf.org>,
> "IETF-Announce"<ietf-announce@ietf.org>
> >Cc: "mpls@ietf.org"<mpls@ietf.org>
> >Ogg: RE: [mpls] R: Re: Last	Call:	&lt;draft-ietf-mpls-tp-cc-cv-rdi-
> 05.txt&gt;
> (Proactive	Connectivity	Verification,	Continuity Check and
> Remote Defect
> indication	for	MPLS	Transport	Profile) to Proposed Standard
> >
> >Hi Erminio:
> >
> ><snipped>
> >>Several service providers regarded this draft as not meeting their
> >>transport networks' needs.
> >
> >E> This is a true statement: the solution in this draft is useless for
> many
> MPLS- TP deployments.
> >
> >The two statements do not necessarily follow.
> >
> >What we established during discussions at the SG15 plenary in February
> was
> that the issue some service providers had was that the IETF BFD
> solution
> exceeded their requirements in that there was additional functionality
> they did
> not see a need for, and that they considered any additional
> functionality
> parasitic.
> >
> >However this is a consequence of adapting an existing technology to a
> new
> application. I do not see any way around that. And the entire joint
> project was
> based on the premise of engineering re-use not greenfield design. That
> is what
> it said on the tin up front, and IMO why when the IETF started down
> this path
> packet transport transitioned from being a minority sport to
> mainstream, so it
> is a bit late to cry foul....
> >
> >My 2 cents
> >Dave
> >
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

From jmh@joelhalpern.com  Wed Jul 13 13:59:01 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 3F26111E80C4; Wed, 13 Jul 2011 13:59:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.547
X-Spam-Level: 
X-Spam-Status: No, score=-102.547 tagged_above=-999 required=5 tests=[AWL=0.052, 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 4fWpowwZo9e7; Wed, 13 Jul 2011 13:59:00 -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 98A7511E807D; Wed, 13 Jul 2011 13:59:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 071DB325C159; Wed, 13 Jul 2011 13:59:00 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.154.181.24] (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 01192325C155; Wed, 13 Jul 2011 13:58:58 -0700 (PDT)
Message-ID: <4E1E070F.6000103@joelhalpern.com>
Date: Wed, 13 Jul 2011 16:58:55 -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: notes from discussion of KARP design guidelines
References: <4E17210A.1070402@joelhalpern.com>	<5662A966-70AD-4A63-BA31-8CE1C9635687@cisco.com>	<4E1747BB.8080602@cisco.com> <4E19B2DC.4030003@joelhalpern.com>	<4E1CC976.9000007@isi.edu> <4E1CCC76.9090409@cisco.com>	<4E1CE644.9090300@isi.edu> <4E1DD654.3030603@joelhalpern.com> <4E1DE2C2.8090209@mti-systems.com> <4E1DE530.5060701@joelhalpern.com> <4E1DEAEB.9040208@isi.edu>
In-Reply-To: <4E1DEAEB.9040208@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>, stbryant@cisco.com, IETF discussion list <ietf@ietf.org>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 20:59:01 -0000

I don't understand your description of the problem.
As you quote, the document clearly states its scope.
So, when we then define the term "on-the-wire", I don't think we need to 
restate the scope definition.  It woudl seem coutner-productive.

Yours,
Joel


On 7/13/2011 2:58 PM, Joe Touch wrote:
>
>
> On 7/13/2011 11:34 AM, Joel M. Halpern wrote:
>> As I said in my earlier note proposing responses to Joe, we would be
>> happy to some text in the front clarifying the usage. Quoting from my
>> earlier email:
>>
>> This text would note that it is a widely used term in IETF documents,
>> including many RFCs. It would also state for clarity that in this
>> document it is used to refer to the message sent from one routing
>> process to another.
>
> Here's why this is a problem:
>
> 1- does this refer to signing a BGP path?
>
> 2- does this refer to protecting the channel over which BGP paths are
> exchanged?
>
>  From the intro:
> Four main steps were identified for that tightening:
>
> o More secure mechanisms and practices for operating routers.
> ...
>
> o Cleaning up the Internet Routing Registry repository [IRR],
> ...
>
> o Specifications for cryptographic validation of routing message
> content.
> ...
>
> 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.
>
> So this document is clearly NOT about "the message from one routing
> process to another (that would be 'routing message content', IMO). I.e.,
> this doc focuses on securing the transfer mechanism NOT the message.
>
> Thus this is the key to the entirety of the doc. This doc needs to be
> very clear about what this is, at which point it can certainly also then
> refer back to the original RFC (e.g., "this is referred to in RFC 4948
> as 'on the wire'").
>
> Joe
>
>
>

From touch@isi.edu  Wed Jul 13 14:06:01 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 0597421F8B32; Wed, 13 Jul 2011 14:06:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.191
X-Spam-Level: 
X-Spam-Status: No, score=-103.191 tagged_above=-999 required=5 tests=[AWL=-1.192, BAYES_00=-2.599, J_CHICKENPOX_43=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 qGLIsv5pclkj; Wed, 13 Jul 2011 14:06:00 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 8CF8721F8B2B; Wed, 13 Jul 2011 14:06:00 -0700 (PDT)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id p6DL5fA5006199 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 13 Jul 2011 14:05:42 -0700 (PDT)
Message-ID: <4E1E08A5.4000809@isi.edu>
Date: Wed, 13 Jul 2011 14:05:41 -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: notes from discussion of KARP design guidelines
References: <4E17210A.1070402@joelhalpern.com>	<5662A966-70AD-4A63-BA31-8CE1C9635687@cisco.com>	<4E1747BB.8080602@cisco.com> <4E19B2DC.4030003@joelhalpern.com>	<4E1CC976.9000007@isi.edu> <4E1CCC76.9090409@cisco.com>	<4E1CE644.9090300@isi.edu> <4E1DD654.3030603@joelhalpern.com> <4E1DE2C2.8090209@mti-systems.com> <4E1DE530.5060701@joelhalpern.com> <4E1DE827.8000300@mti-systems.com> <4E1E03B2.3010405@joelhalpern.com>
In-Reply-To: <4E1E03B2.3010405@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>, stbryant@cisco.com, IETF discussion list <ietf@ietf.org>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 21:06:01 -0000

Hi, Joel,

On 7/13/2011 1:44 PM, Joel M. Halpern wrote:
> Sorry, I apparently missed part of your earlier note.
> Would text like:
> This document uses the term "on-the-wire" to talk about the information
> used by routing systems. This term is widely used in IETF RFCs,but is
> used in several different ways. In this document, it is used to refer
> both to information exchanged between routing protocol instances, and to
> underlying protocols that may also need to be protected in specific
> circumstances.

I think that is in direct contrast to the current text in the intro, 
that appears to differentiate between the two and focus on the latter.

Joe

> Individual protocol analysis documents will need to be
> more specific in their usage.
>
> work to address the issue?
> Yours,
> Joel
>
> On 7/13/2011 2:47 PM, Wesley Eddy wrote:
>> On 7/13/2011 2:34 PM, Joel M. Halpern wrote:
>>> As I said in my earlier note proposing responses to Joe, we would be
>>> happy to some text in the front clarifying the usage. Quoting from my
>>> earlier email:
>>>
>>> This text would note that it is a widely used term in IETF documents,
>>> including many RFCs. It would also state for clarity that in this
>>> document it is used to refer to the message sent from one routing
>>> process to another.
>>>
>>> Apparently, this does not address Joe's concern.
>>>
>>
>> "message sent from one routing process to another" doesn't seem to be
>> right to me either since it sounds like the first definition that
>> covers routing protocol data only, and not underlying protocols, so I
>> wouldn't expect that proposal to address Joe's concern.
>>

From touch@isi.edu  Wed Jul 13 14:08:53 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 0F61321F8B2B; Wed, 13 Jul 2011 14:08:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.443
X-Spam-Level: 
X-Spam-Status: No, score=-103.443 tagged_above=-999 required=5 tests=[AWL=-0.844, 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 hW9MkUQNklTX; Wed, 13 Jul 2011 14:08:52 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 87B2C21F8B02; Wed, 13 Jul 2011 14:08:52 -0700 (PDT)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id p6DL8D5O006983 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 13 Jul 2011 14:08:13 -0700 (PDT)
Message-ID: <4E1E093D.9040903@isi.edu>
Date: Wed, 13 Jul 2011 14:08:13 -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: notes from discussion of KARP design guidelines
References: <4E17210A.1070402@joelhalpern.com>	<5662A966-70AD-4A63-BA31-8CE1C9635687@cisco.com>	<4E1747BB.8080602@cisco.com> <4E19B2DC.4030003@joelhalpern.com>	<4E1CC976.9000007@isi.edu> <4E1CCC76.9090409@cisco.com>	<4E1CE644.9090300@isi.edu> <4E1DD654.3030603@joelhalpern.com> <4E1DE2C2.8090209@mti-systems.com> <4E1DE530.5060701@joelhalpern.com> <4E1DEAEB.9040208@isi.edu> <4E1E070F.6000103@joelhalpern.com>
In-Reply-To: <4E1E070F.6000103@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>, stbryant@cisco.com, IETF discussion list <ietf@ietf.org>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 21:08:53 -0000

Hi, Joel,

On 7/13/2011 1:58 PM, Joel M. Halpern wrote:
> I don't understand your description of the problem.
> As you quote, the document clearly states its scope.
> So, when we then define the term "on-the-wire", I don't think we need to
> restate the scope definition. It woudl seem coutner-productive.

The current scope is clear from the bullet list only by the assumption 
that (a) the bullets are mutually exclusive, and (b) since the "routing 
message content" is clear, it cannot be part of "on the wire".

I.e., it requires the reader interpret scope by a matter of deduction 
and exclusion, rather than stating it clearly and explicitly.

Joe

>
> Yours,
> Joel
>
>
> On 7/13/2011 2:58 PM, Joe Touch wrote:
>>
>>
>> On 7/13/2011 11:34 AM, Joel M. Halpern wrote:
>>> As I said in my earlier note proposing responses to Joe, we would be
>>> happy to some text in the front clarifying the usage. Quoting from my
>>> earlier email:
>>>
>>> This text would note that it is a widely used term in IETF documents,
>>> including many RFCs. It would also state for clarity that in this
>>> document it is used to refer to the message sent from one routing
>>> process to another.
>>
>> Here's why this is a problem:
>>
>> 1- does this refer to signing a BGP path?
>>
>> 2- does this refer to protecting the channel over which BGP paths are
>> exchanged?
>>
>> From the intro:
>> Four main steps were identified for that tightening:
>>
>> o More secure mechanisms and practices for operating routers.
>> ...
>>
>> o Cleaning up the Internet Routing Registry repository [IRR],
>> ...
>>
>> o Specifications for cryptographic validation of routing message
>> content.
>> ...
>>
>> 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.
>>
>> So this document is clearly NOT about "the message from one routing
>> process to another (that would be 'routing message content', IMO). I.e.,
>> this doc focuses on securing the transfer mechanism NOT the message.
>>
>> Thus this is the key to the entirety of the doc. This doc needs to be
>> very clear about what this is, at which point it can certainly also then
>> refer back to the original RFC (e.g., "this is referred to in RFC 4948
>> as 'on the wire'").
>>
>> Joe
>>
>>
>>

From jmh@joelhalpern.com  Wed Jul 13 14:26:15 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 225A011E8089; Wed, 13 Jul 2011 14:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.552
X-Spam-Level: 
X-Spam-Status: No, score=-102.552 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cmxVBP3iUV5c; Wed, 13 Jul 2011 14:26: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 3A0C511E8075; Wed, 13 Jul 2011 14:26:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 86DCC32462B0; Wed, 13 Jul 2011 14:26:13 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.154.181.24] (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 5A3E43245E54; Wed, 13 Jul 2011 14:26:12 -0700 (PDT)
Message-ID: <4E1E0D70.7040801@joelhalpern.com>
Date: Wed, 13 Jul 2011 17:26:08 -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: notes from discussion of KARP design guidelines
References: <4E17210A.1070402@joelhalpern.com>	<5662A966-70AD-4A63-BA31-8CE1C9635687@cisco.com>	<4E1747BB.8080602@cisco.com> <4E19B2DC.4030003@joelhalpern.com>	<4E1CC976.9000007@isi.edu> <4E1CCC76.9090409@cisco.com>	<4E1CE644.9090300@isi.edu> <4E1DD654.3030603@joelhalpern.com> <4E1DE2C2.8090209@mti-systems.com> <4E1DE530.5060701@joelhalpern.com> <4E1DEAEB.9040208@isi.edu> <4E1E070F.6000103@joelhalpern.com> <4E1E093D.9040903@isi.edu>
In-Reply-To: <4E1E093D.9040903@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>, stbryant@cisco.com, IETF discussion list <ietf@ietf.org>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 21:26:15 -0000

You wording seems to induce confusion.
Of course the routing message content is part of the message 
on-the-wire.  It is the content of the message.  It is in fact a 
significant part of what is being protected.

What is NOT part of the scope, and which the text says is not part of 
the scope, is the validation of that information.  KARP is not assuring 
that the information is valid.  it is responsible to ensure that the 
message is not modified between the two peers.

Yes, this means that there is an overlap in protection between 
validation information and packet authentication information.  So?  The 
scope is very clear as to whose problem is whose.  (This is merely a 
statement of fact.  If we have path signing and TCP-AO, there are two 
sets of mechanisms preventing modification of some of the BGP 
information.)

The text after the bullet list explicitly says what part is in scope. 
it does not require any assumption or inference.
If there is specific wording you would like to suggest to improve the 
introductory scoping material, I would be happy to look at it.

Yours,
Joel

On 7/13/2011 5:08 PM, Joe Touch wrote:
> Hi, Joel,
>
> On 7/13/2011 1:58 PM, Joel M. Halpern wrote:
>> I don't understand your description of the problem.
>> As you quote, the document clearly states its scope.
>> So, when we then define the term "on-the-wire", I don't think we need to
>> restate the scope definition. It woudl seem coutner-productive.
>
> The current scope is clear from the bullet list only by the assumption
> that (a) the bullets are mutually exclusive, and (b) since the "routing
> message content" is clear, it cannot be part of "on the wire".
>
> I.e., it requires the reader interpret scope by a matter of deduction
> and exclusion, rather than stating it clearly and explicitly.
>
> Joe
>
>>
>> Yours,
>> Joel
>>
>>
>> On 7/13/2011 2:58 PM, Joe Touch wrote:
>>>
>>>
>>> On 7/13/2011 11:34 AM, Joel M. Halpern wrote:
>>>> As I said in my earlier note proposing responses to Joe, we would be
>>>> happy to some text in the front clarifying the usage. Quoting from my
>>>> earlier email:
>>>>
>>>> This text would note that it is a widely used term in IETF documents,
>>>> including many RFCs. It would also state for clarity that in this
>>>> document it is used to refer to the message sent from one routing
>>>> process to another.
>>>
>>> Here's why this is a problem:
>>>
>>> 1- does this refer to signing a BGP path?
>>>
>>> 2- does this refer to protecting the channel over which BGP paths are
>>> exchanged?
>>>
>>> From the intro:
>>> Four main steps were identified for that tightening:
>>>
>>> o More secure mechanisms and practices for operating routers.
>>> ...
>>>
>>> o Cleaning up the Internet Routing Registry repository [IRR],
>>> ...
>>>
>>> o Specifications for cryptographic validation of routing message
>>> content.
>>> ...
>>>
>>> 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.
>>>
>>> So this document is clearly NOT about "the message from one routing
>>> process to another (that would be 'routing message content', IMO). I.e.,
>>> this doc focuses on securing the transfer mechanism NOT the message.
>>>
>>> Thus this is the key to the entirety of the doc. This doc needs to be
>>> very clear about what this is, at which point it can certainly also then
>>> refer back to the original RFC (e.g., "this is referred to in RFC 4948
>>> as 'on the wire'").
>>>
>>> Joe
>>>
>>>
>>>
>

From stpeter@stpeter.im  Wed Jul 13 14:26:50 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 E2EE211E8101 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 14:26:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.694
X-Spam-Level: 
X-Spam-Status: No, score=-102.694 tagged_above=-999 required=5 tests=[AWL=-0.095, 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 N8cdZ6OrR+Xo for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 14:26:50 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 3C3E311E8084 for <ietf@ietf.org>; Wed, 13 Jul 2011 14:26:50 -0700 (PDT)
Received: from leavealone.cisco.com (unknown [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 7EF0B410EE; Wed, 13 Jul 2011 15:27:13 -0600 (MDT)
Message-ID: <4E1E0D97.8060603@stpeter.im>
Date: Wed, 13 Jul 2011 15:26:47 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: Second Last Call: <draft-hammer-hostmeta-16.txt> (Web Host
References: <201107122006.p6CK68YT022236@fs4113.wdf.sap.corp>
In-Reply-To: <201107122006.p6CK68YT022236@fs4113.wdf.sap.corp>
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: mnot@mnot.net, ietf@ietf.org, 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, 13 Jul 2011 21:26:51 -0000

On 7/12/11 2:06 PM, Martin Rex wrote:
> Peter Saint-Andre wrote:
>>
>> On 6/21/11 11:08 PM, Mark Nottingham wrote:
>>> 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.
>>
>> How about publishing it on the standards track but not as a general
>> mechanism (i.e., why not clarify when it is and is not appropriate)?
> 
> How about publishing as Informational?
> 
> RFC 2026 says:
> 
>    4.  THE INTERNET STANDARDS TRACK
> 
>    Specifications that are intended to become Internet Standards evolve
>    through a set of maturity levels known as the "standards track".
>    These maturity levels -- "Proposed Standard", "Draft Standard", and
>    "Standard" -- are defined and discussed in section 4.1.
> 
> If there is no strong consensus and commitment to work the document
> along the standards track up to full standard, then it shouldn't
> be on the standards track at all.

Who said there isn't strong consensus and commitment to work the
document along the standards track? The only statement I've seen is that
it's not a generic solution for all metadata problems.

> For documents where the only purpose of publishing it is only to obtain
> an rfc number for it, but otherwise just describe "this is how others
> have solved a particular problem before" and let vendors and implementors
> wiggle out interop, then Informational is quite appropriate.

I see no reason to make those assumptions here.

Peter

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



From stpeter@stpeter.im  Wed Jul 13 14:30:21 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 D86B211E814C for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 14:30:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.69
X-Spam-Level: 
X-Spam-Status: No, score=-102.69 tagged_above=-999 required=5 tests=[AWL=-0.091, 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 F7rTnmIdFiom for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 14:30:17 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id B314711E8102 for <ietf@ietf.org>; Wed, 13 Jul 2011 14:30:17 -0700 (PDT)
Received: from leavealone.cisco.com (unknown [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 34079410EE; Wed, 13 Jul 2011 15:30:41 -0600 (MDT)
Message-ID: <4E1E0E68.1080809@stpeter.im>
Date: Wed, 13 Jul 2011 15:30:16 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: Second Last Call: <draft-hammer-hostmeta-16.txt> (Web Host Metadata) to Proposed Standard -- feedback
References: <11CBFBA2-434B-43FC-90C4-DADBACB49226@mnot.net> <4E1CA248.7060009@stpeter.im> <3110098B-5515-4E7A-84A4-522925593FA2@mnot.net>
In-Reply-To: <3110098B-5515-4E7A-84A4-522925593FA2@mnot.net>
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Blaine Cook <romeda@gmail.com>, "ietf@ietf.org IETF" <ietf@ietf.org>, 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, 13 Jul 2011 21:30:22 -0000

On 7/13/11 5:35 AM, Mark Nottingham wrote:
> Personally, I think Informational is most appropriate (and probably
> easier), but a paragraph or two of context, as well as corresponding
> adjustments, would work as well.

Personally I'm not wedded to Standards Track for this document, and
neither are the authors. I just want to make sure that there's a good
reason to change it from Standards Track to Informational. IMHO "this
document doesn't solve the problem in the most generic way" would
prevent us from publishing a rather large number of specifications on
the Standards Track. There's nothing evil about scoping a document so
that it solves a more particular problem.

Peter

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



From jdrake@juniper.net  Wed Jul 13 14:52:00 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 B5C1C11E81B1; Wed, 13 Jul 2011 14:52:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.812
X-Spam-Level: 
X-Spam-Status: No, score=-5.812 tagged_above=-999 required=5 tests=[AWL=0.787,  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 oP9fkMX8g7NA; Wed, 13 Jul 2011 14:51:59 -0700 (PDT)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by ietfa.amsl.com (Postfix) with ESMTP id 586EE11E81AE; Wed, 13 Jul 2011 14:51:59 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP ID DSNKTh4TdDoCtWo0fn3CTPbJiemiZctIoI3v@postini.com; Wed, 13 Jul 2011 14:51:59 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB03-HQ.jnpr.net ([::1]) with mapi; Wed, 13 Jul 2011 14:51:01 -0700
From: John E Drake <jdrake@juniper.net>
To: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>, "david.i.allan@ericsson.com" <david.i.allan@ericsson.com>, "RCosta@ptinovacao.pt" <RCosta@ptinovacao.pt>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
Date: Wed, 13 Jul 2011 14:50:59 -0700
Subject: RE: RE: [mpls] R: RE: R: Re:	Last	Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>	(Proactive	Connectivity	Verification, Continuity Check and Remote Defect	indication	for	MPLS	Transport	Profile) to Proposed Standard
Thread-Topic: RE: [mpls] R: RE: R: Re:	Last	Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>	(Proactive	Connectivity	Verification, Continuity Check and Remote Defect	indication	for	MPLS	Transport	Profile) to Proposed Standard
Thread-Index: AcxBoG0OS2ifSLKARaC6iTe+89k3eAABOY5w
Message-ID: <5E893DB832F57341992548CDBB333163A0A92C535B@EMBX01-HQ.jnpr.net>
References: <29155895.3316791310591053994.JavaMail.defaultUser@defaultHost>
In-Reply-To: <29155895.3316791310591053994.JavaMail.defaultUser@defaultHost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 21:52:00 -0000

SXRhbG8sDQoNCkNvbW1lbnRzIGlubGluZS4NCg0KVGhhbmtzLA0KDQpKb2huDQoNClNlbnQgZnJv
bSBteSBpUGhvbmUNCg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IGVy
bWluaW8ub3R0b25lXzY5QGxpYmVyby5pdCBbbWFpbHRvOmVybWluaW8ub3R0b25lXzY5QGxpYmVy
by5pdF0NCj4gU2VudDogV2VkbmVzZGF5LCBKdWx5IDEzLCAyMDExIDI6MDQgUE0NCj4gVG86IEpv
aG4gRSBEcmFrZTsgZGF2aWQuaS5hbGxhbkBlcmljc3Nvbi5jb207IFJDb3N0YUBwdGlub3ZhY2Fv
LnB0Ow0KPiBpZXRmQGlldGYub3JnOyBJRVRGLUFubm91bmNlDQo+IENjOiBtcGxzQGlldGYub3Jn
DQo+IFN1YmplY3Q6IFI6IFJFOiBbbXBsc10gUjogUkU6IFI6IFJlOiBMYXN0IENhbGw6IDxkcmFm
dC1pZXRmLW1wbHMtdHAtY2MtDQo+IGN2LXJkaS0wNS50eHQ+IChQcm9hY3RpdmUgQ29ubmVjdGl2
aXR5IFZlcmlmaWNhdGlvbiwgQ29udGludWl0eSBDaGVjaw0KPiBhbmQgUmVtb3RlIERlZmVjdCBp
bmRpY2F0aW9uIGZvciBNUExTIFRyYW5zcG9ydCBQcm9maWxlKSB0byBQcm9wb3NlZA0KPiBTdGFu
ZGFyZA0KPiANCj4gVGhlIEpXVCByZXBvcnQgaXMgYWxpZ25lZCB3aXRoIG15IHN0YXRlbWVudC4N
Cg0KSkQ6ICBBcyBTRzE1IG1hbmFnZW1lbnQgaXMgZm9uZCBvZiBwb2ludGluZyBvdXQsIHdoZW4g
aXQgc3VpdHMgdGhlbSwgdGhlIEpXVCBvcGVyYXRlZCBvbiBhIHZlcnkgY29tcHJlc3NlZCB0aW1l
IHNjYWxlIGFuZCBkaWRuJ3QgZnVsbHkgZXhwbG9yZSBhbGwgb2YgdGhlIHRlY2huaWNhbCBpc3N1
ZXMNCg0KPiANCj4gVGhlIGRlY2lzaW9uIGF0IElFVEY3NSBoYXMgYmVlbiB0YWtlbiBieSB0aGUg
TVBMUyBXRyBhZnRlciB0aGUgSldUIGFuZA0KPiBoYXMNCj4gbmV2ZXIgYmVlbiBlbmRvcnNlZCBi
eSBJVFUtVCAoSHV1YiBpcyBOT1QgSVRVLVQgYW5kLCBhcyBmYXIgYXMgSQ0KPiB1bmRlcnN0b29k
LCBoZQ0KPiBsYXRlciByZW1vdmVkIGhpcyBuYW1lIGJlY2F1c2UgdGhlIG90aGVyIGVkaXRvcnMg
b2YgdGhlIE9BTSBBbmFseXNpcw0KPiBkcmFmdCB3ZXJlDQo+IG5vdCBjb25zaWRlcmluZyBoaXMg
aW5wdXQgdG8gdGhlIGRvY3VtZW50KS4NCg0KSkQ6ICBJJ20gbm90IHN1cmUgd2hhdCB5b3VyIHBv
aW50IGlzDQoNCj4gDQo+IFRoZSBCRkQtYmFzZWQgc29sdXRpb24gYWNjZXB0ZWQgYnkgSUVURjc1
IGZvciBwcm8tYWN0aXZlIENDL0NWL1JESSB3YXMNCj4gY29tcGxldGVseSBkaWZmZXJlbnQgKGFu
ZCB0ZWNobmljYWxseSBtdWNoIHN1cGVyaW9yKSB0aGFuIHRoZSBvbmUNCj4gZGVzY3JpYmVkIGJ5
DQo+IHRoaXMgZHJhZnQuDQoNCkpEOiAgT2J2aW91c2x5IHdlIGRpc2FncmVlDQoNCj4gDQo+IEFj
Y2VwdGluZyBhIHNvbHV0aW9uIHRoYXQgbWVldHMgdGhlIHJlcXVpcmVtZW50cyBkb2VzIG5vdCBt
ZWFuIHNpZ25pbmcNCj4gYSBibGFuaw0KPiBjaGVxdWUgdGhhdCB3aGljaGV2ZXIgY2hhbmdlcyBp
cyBkb25lIGlzIGFjY2VwdGFibGUgcmVnYXJsZXNzIHdoZXRoZXINCj4gaXQgbWVldHMNCj4gb3Ig
bm90IHRoZSByZXF1aXJlbWVudHMuDQoNCkpEOiAgVGhlIHJlcXVpcmVtZW50cyBhcyBkb2N1bWVu
dGVkIGluIFJGQ3MgNTY1NCwgNTg2MCwgYW5kIDU5NTEsIG9yIHRoZSByZXF1aXJlbWVudHMgdGhh
dCBzZWVtIHRvIGNoYW5nZSBiYXNlZCB1cG9uIHRoZSBwaGFzZXMgb2YgdGhlIG1vb24/DQogDQo+
IA0KPiA+LS0tLU1lc3NhZ2dpbyBvcmlnaW5hbGUtLS0tDQo+ID5EYTogamRyYWtlQGp1bmlwZXIu
bmV0DQo+ID5EYXRhOiAxMy1sdWctMjAxMSAyMi40Ng0KPiA+QTogImVybWluaW8ub3R0b25lXzY5
QGxpYmVyby5pdCI8ZXJtaW5pby5vdHRvbmVfNjlAbGliZXJvLml0PiwNCj4gImRhdmlkLmkuDQo+
IGFsbGFuQGVyaWNzc29uLmNvbSI8ZGF2aWQuaS5hbGxhbkBlcmljc3Nvbi5jb20+LCAiUkNvc3Rh
QHB0aW5vdmFjYW8ucHQiDQo+IDxSQ29zdGFAcHRpbm92YWNhby5wdD4sICJpZXRmQGlldGYub3Jn
IjxpZXRmQGlldGYub3JnPiwgIklFVEYtDQo+IEFubm91bmNlIjxpZXRmLQ0KPiBhbm5vdW5jZUBp
ZXRmLm9yZz4NCj4gPkNjOiAibXBsc0BpZXRmLm9yZyI8bXBsc0BpZXRmLm9yZz4NCj4gPk9nZzog
UkU6IFttcGxzXSBSOiBSRTogUjogUmU6CUxhc3QJQ2FsbDoJJmx0O2RyYWZ0LWlldGYtbXBscy10
cC0NCj4gY2MtY3YtcmRpLTA1Lg0KPiB0eHQmZ3Q7CShQcm9hY3RpdmUJQ29ubmVjdGl2aXR5CVZl
cmlmaWNhdGlvbiwJQ29udGludWl0eQ0KPiBDaGVjayBhbmQgUmVtb3RlDQo+IERlZmVjdAlpbmRp
Y2F0aW9uCWZvcglNUExTCVRyYW5zcG9ydAlQcm9maWxlKSB0byBQcm9wb3NlZA0KPiBTdGFuZGFy
ZA0KPiA+DQo+ID5JdGFsbywNCj4gPg0KPiA+VGhlIGRlc2lnbiB0ZWFtIHJlcG9ydA0KPiAoaHR0
cDovL3d3dy5pZXRmLm9yZy9wcm9jZWVkaW5ncy83NS9zbGlkZXMvbXBscy0NCj4gMTcvbXBscy0x
N19maWxlcy9mcmFtZS5odG0pLCB3aXRoIEh1dWIncyBuYW1lIGFzIGFuIGF1dGhvciwgZGV0YWls
cyBhDQo+IHBsYW4gZm9yDQo+IE1QTFMtVFAgT0FNIHdoaWNoIHRoZSBNUExTIFdHIGhhcyBmb2xs
b3dlZCB0byB0aGlzIGRheS4gIEkgdGhpbmsgdGhlDQo+IHJlcG9ydCBpcw0KPiBjb21wZWxsaW5n
IGV2aWRlbmNlIHRoYXQgdGhlIGNsYWltIHRoYXQgYSBwYWNrZXQgdHJhbnNwb3J0IG5ldHdvcmsg
aXMNCj4gYW4gTVBMUw0KPiBhcHBsaWNhdGlvbiB0aGF0IGludHJpbnNpY2FsbHkgcmVxdWlyZXMg
YSBkaWZmZXJlbnQgT0FNIHNvbHV0aW9uIGlzDQo+IHNpbXBseSBhDQo+IGxhbWUgZXggcG9zdCBm
YWN0byBhdHRlbXB0IHRvIGp1c3RpZnkgdGhlIElUVSdzIGFicm9nYXRpb24gb2YgdGhlDQo+IGFn
cmVlbWVudA0KPiB3aXRoIHRoZSBJRVRGIChURDA3IChXUDMvU0cxNSkgZnJvbSBEZWNlbWJlciAy
MDA4IHNvdXJjZWQgYnkgU0cxNSk6DQo+ID4NCj4gPiJUaGUgSVRVLVQgYWNjZXB0cyB0aGVzZSBy
ZWNvbW1lbmRhdGlvbnMgYW5kIHN0YXRlcyB0aGF0IGFueQ0KPiBleHRlbnNpb25zIHRvDQo+IE1Q
TFMgdGVjaG5vbG9neSB3aWxsIGJlIHByb2dyZXNzZWQgdmlhIHRoZSBJRVRGIHN0YW5kYXJkcyBw
cm9jZXNzIHVzaW5nDQo+IHRoZQ0KPiBwcm9jZWR1cmVzIGRlZmluZWQgaW4gUkZDIDQ5MjkgKENo
YW5nZSBQcm9jZXNzIGZvciBNdWx0aXByb3RvY29sIExhYmVsDQo+IFN3aXRjaGluZyAoTVBMUykg
YW5kIEdlbmVyYWxpemVkIE1QTFMgKEdNUExTKSBQcm90b2NvbHMgYW5kDQo+IFByb2NlZHVyZXMp
Lg0KPiBFeHBlcnRzIGZyb20gdGhlIElUVS1UIHdpbGwgYXNzaXN0IHRoZSBJRVRGIGluIHRoZSBk
ZXZlbG9wbWVudCBvZiBSRkNzDQo+IHRoYXQNCj4gZGVzY3JpYmUgdGhlIHRyYW5zcG9ydCBleHRl
bnNpb25zIGJ5IHByb3ZpZGluZyBpbnB1dCB0byBhbmQgcmV2aWV3IG9mDQo+IHRoZQ0KPiBkcmFm
dHMgYXMgdGhleSBhcmUgcHJvZ3Jlc3NlZCB2aWEgdGhlIElFVEYgc3RhbmRhcmRzIHByb2Nlc3Mu
LiBUaGUgSVRVLQ0KPiBUIHdpbGwNCj4gZGV2ZWxvcCBuZXcgb3IgcmV2aXNlZCBSZWNvbW1lbmRh
dGlvbnMgdGhhdCB3aWxsIGFsbG93IElFVEYgTVBMUy1UUCB0bw0KPiBiZQ0KPiBpbnRlZ3JhdGVk
IGludG8gdGhlIHRyYW5zcG9ydCBuZXR3b3JrIGluY2x1ZGluZyBpbnRlZ3JhdGlvbiB3aXRoIHRo
ZQ0KPiBleGlzdGluZw0KPiBlcXVpcG1lbnQsIGFuZCBvcGVyYXRpb25zIGluZnJhc3RydWN0dXJl
LiAgVGhlc2UgUmVjb21tZW5kYXRpb25zIHdpbGwNCj4gbWFrZQ0KPiBub3JtYXRpdmUgcmVmZXJl
bmNlcyB0byB0aGUgYmFzZSBJRVRGIE1QTFMtVFAgdGVjaG5vbG9neSBhbmQgd2lsbCBiZQ0KPiBk
ZXZlbG9wZWQNCj4gd2l0aCBpbnB1dCBmcm9tIGFuZCByZXZpZXcgYnkgZXhwZXJ0cyBmcm9tIHRo
ZSBJRVRGIHRvIGVuc3VyZQ0KPiBjb25zaXN0ZW5jeSB3aXRoDQo+IE1QTFMtVFAuLi4NCj4gPg0K
PiA+VGhlIElUVS1UIGhhcyBhY2NlcHRlZCB0aGUgcHJvcG9zYWxzIGZyb20gdGhlIEpXVCBhbmQg
d2UgbG9vayBmb3J3YXJkDQo+IHRvDQo+IGNvbnRpbnVpbmcgdGhlIGNvb3BlcmF0aXZlIGRldmVs
b3BtZW50IG9mIElFVEYgTVBMUyB0byBhZGRyZXNzIHRoZQ0KPiBuZWVkcyBvZiB0aGUNCj4gdHJh
bnNwb3J0IG5ldHdvcmsuIFdlIGFsc28gYmVsaWV2ZSB0aGF0IHRoaXMgcmVzb2x1dGlvbiB3aWxs
IGZ1bGZpbCB0aGUNCj4gbXV0dWFsDQo+IGdvYWwgb2YgaW1wcm92ZSB0aGUgZnVuY3Rpb25hbGl0
eSBvZiB0aGUgaW50ZXJuZXQgYW5kIHRyYW5zcG9ydA0KPiBuZXR3b3JrcyBhbmQNCj4gZ3VhcmFu
dGVlaW5nIGNvbXBsZXRlIGludGVyb3BlcmFiaWxpdHkgYW5kIGFyY2hpdGVjdHVyYWwgc291bmRu
ZXNzLiINCj4gPg0KPiA+VGhhbmtzLA0KPiA+DQo+ID5Kb2huDQo+ID4NCj4gPlNlbnQgZnJvbSBt
eSBpUGhvbmUNCj4gPg0KPiA+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+PiBGcm9t
OiBtcGxzLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzptcGxzLWJvdW5jZXNAaWV0Zi5vcmddIE9u
IEJlaGFsZg0KPiBPZg0KPiA+PiBlcm1pbmlvLm90dG9uZV82OUBsaWJlcm8uaXQNCj4gPj4gU2Vu
dDogV2VkbmVzZGF5LCBKdWx5IDEzLCAyMDExIDE6MjcgUE0NCj4gPj4gVG86IGRhdmlkLmkuYWxs
YW5AZXJpY3Nzb24uY29tOyBSQ29zdGFAcHRpbm92YWNhby5wdDsgaWV0ZkBpZXRmLm9yZzsNCj4g
Pj4gSUVURi1Bbm5vdW5jZQ0KPiA+PiBDYzogbXBsc0BpZXRmLm9yZw0KPiA+PiBTdWJqZWN0OiBb
bXBsc10gUjogUkU6IFI6IFJlOiBMYXN0IENhbGw6IDxkcmFmdC1pZXRmLW1wbHMtdHAtY2MtY3Yt
DQo+IHJkaS0NCj4gPj4gMDUudHh0PiAoUHJvYWN0aXZlIENvbm5lY3Rpdml0eSBWZXJpZmljYXRp
b24sIENvbnRpbnVpdHkgQ2hlY2sgYW5kDQo+ID4+IFJlbW90ZSBEZWZlY3QgaW5kaWNhdGlvbiBm
b3IgTVBMUyBUcmFuc3BvcnQgUHJvZmlsZSkgdG8gUHJvcG9zZWQNCj4gPj4gU3RhbmRhcmQNCj4g
Pj4NCj4gPj4gPkhvd2V2ZXIgdGhpcyBpcyBhIGNvbnNlcXVlbmNlIG9mIGFkYXB0aW5nIGFuIGV4
aXN0aW5nIHRlY2hub2xvZ3kgdG8NCj4gYQ0KPiA+PiBuZXcNCj4gPj4gYXBwbGljYXRpb24uIEkg
ZG8gbm90IHNlZSBhbnkgd2F5IGFyb3VuZCB0aGF0LiBBbmQgdGhlIGVudGlyZSBqb2ludA0KPiA+
PiBwcm9qZWN0IHdhcw0KPiA+PiBiYXNlZCBvbiB0aGUgcHJlbWlzZSBvZiBlbmdpbmVlcmluZyBy
ZS11c2Ugbm90IGdyZWVuZmllbGQgZGVzaWduLg0KPiBUaGF0DQo+ID4+IGlzIHdoYXQNCj4gPj4g
aXQgc2FpZCBvbiB0aGUgdGluIHVwIGZyb250LCBhbmQgSU1PIHdoeSB3aGVuIHRoZSBJRVRGIHN0
YXJ0ZWQgZG93bg0KPiA+PiB0aGlzIHBhdGgNCj4gPj4gcGFja2V0IHRyYW5zcG9ydCB0cmFuc2l0
aW9uZWQgZnJvbSBiZWluZyBhIG1pbm9yaXR5IHNwb3J0IHRvDQo+ID4+IG1haW5zdHJlYW0sIHNv
IGl0DQo+ID4+IGlzIGEgYml0IGxhdGUgdG8gY3J5IGZvdWwuLi4uDQo+ID4+DQo+ID4+IFRoaXMg
aXMgbm90IHdoYXQgdGhlIElFVEYgaGFzIGNvbW1pdHRlZCB0byBkZWxpdmVyIHRvIElUVS1UIGFu
ZCBpbg0KPiBmYWN0DQo+ID4+IHNsaWRlDQo+ID4+IDQ0IHBvc3Rwb25lcyB0byB0aGUgT0FNIGRl
c2lnbiBwaGFzZSAiZGVjaWRlIHdoZXRoZXIgTFNQLVBpbmcgb3IgQkZEDQo+ID4+IGNhbiBvcg0K
PiA+PiBzaG91bGQgYmUgdHdlYWtlZCBvciBub3QiIGFuZCBzbGlkZSA0NiByZWNrb25zICJtYW55
IG9wdGlvbnMNCj4gaW5jbHVkaW5nDQo+ID4+IG5vbiBJUA0KPiA+PiBCRkQgaXMgYW4gb3B0aW9u
IGVuY2Fwc3VsYXRpb24gb2YgWS4xNzMxIFBEVSINCj4gPj4NCj4gPj4gSXQgc2VlbXMgdG8gbWUg
YWZ0ZXIgaGF2aW5nIHJlYWQgdGhlIGRyYWZ0IGFuZCBmb2xsb3dlZCB0aGlzIHZlcnkNCj4gbG9u
Zw0KPiA+PiB0aHJlYWQNCj4gPj4gdGhhdCB0d2Vha2luZyBCRkQgaXMgbm90IHRoZSByaWdodCBh
cHByb2FjaCB0byBtZWV0IElUVS1UDQo+IHJlcXVpcmVtZW50cw0KPiA+PiBzbyBpdA0KPiA+PiB3
b3VsZCBiZSB3b3J0aCBldmFsdWF0aW5nIHRoZSBvdGhlciBhbHRlcm5hdGl2ZSBjb25zaWRlcmVk
IHZpYWJsZSBieQ0KPiA+PiB0aGUgSldUDQo+ID4+IHdoaWNoIGlzIGVuY2FwdWxhdGluZyBZLjE3
MzEgUERVcy4NCj4gPj4NCj4gPj4gPi0tLS1NZXNzYWdnaW8gb3JpZ2luYWxlLS0tLQ0KPiA+PiA+
RGE6IGRhdmlkLmkuYWxsYW5AZXJpY3Nzb24uY29tDQo+ID4+ID5EYXRhOiA2LWx1Zy0yMDExIDIw
LjI0DQo+ID4+ID5BOiAiZXJtaW5pby5vdHRvbmVfNjlAbGliZXJvLml0Ijxlcm1pbmlvLm90dG9u
ZV82OUBsaWJlcm8uaXQ+LA0KPiA+PiAiUkNvc3RhQHB0aW5vdmFjYW8ucHQiPFJDb3N0YUBwdGlu
b3ZhY2FvLnB0PiwNCj4gPj4gImlldGZAaWV0Zi5vcmciPGlldGZAaWV0Zi5vcmc+LA0KPiA+PiAi
SUVURi1Bbm5vdW5jZSI8aWV0Zi1hbm5vdW5jZUBpZXRmLm9yZz4NCj4gPj4gPkNjOiAibXBsc0Bp
ZXRmLm9yZyI8bXBsc0BpZXRmLm9yZz4NCj4gPj4gPk9nZzogUkU6IFttcGxzXSBSOiBSZTogTGFz
dAlDYWxsOgkmbHQ7ZHJhZnQtaWV0Zi1tcGxzLXRwLWNjLWN2LQ0KPiByZGktDQo+ID4+IDA1LnR4
dCZndDsNCj4gPj4gKFByb2FjdGl2ZQlDb25uZWN0aXZpdHkJVmVyaWZpY2F0aW9uLAlDb250aW51
aXR5IENoZWNrDQo+IGFuZA0KPiA+PiBSZW1vdGUgRGVmZWN0DQo+ID4+IGluZGljYXRpb24JZm9y
CU1QTFMJVHJhbnNwb3J0CVByb2ZpbGUpIHRvIFByb3Bvc2VkIFN0YW5kYXJkDQo+ID4+ID4NCj4g
Pj4gPkhpIEVybWluaW86DQo+ID4+ID4NCj4gPj4gPjxzbmlwcGVkPg0KPiA+PiA+PlNldmVyYWwg
c2VydmljZSBwcm92aWRlcnMgcmVnYXJkZWQgdGhpcyBkcmFmdCBhcyBub3QgbWVldGluZyB0aGVp
cg0KPiA+PiA+PnRyYW5zcG9ydCBuZXR3b3JrcycgbmVlZHMuDQo+ID4+ID4NCj4gPj4gPkU+IFRo
aXMgaXMgYSB0cnVlIHN0YXRlbWVudDogdGhlIHNvbHV0aW9uIGluIHRoaXMgZHJhZnQgaXMgdXNl
bGVzcw0KPiBmb3INCj4gPj4gbWFueQ0KPiA+PiBNUExTLSBUUCBkZXBsb3ltZW50cy4NCj4gPj4g
Pg0KPiA+PiA+VGhlIHR3byBzdGF0ZW1lbnRzIGRvIG5vdCBuZWNlc3NhcmlseSBmb2xsb3cuDQo+
ID4+ID4NCj4gPj4gPldoYXQgd2UgZXN0YWJsaXNoZWQgZHVyaW5nIGRpc2N1c3Npb25zIGF0IHRo
ZSBTRzE1IHBsZW5hcnkgaW4NCj4gRmVicnVhcnkNCj4gPj4gd2FzDQo+ID4+IHRoYXQgdGhlIGlz
c3VlIHNvbWUgc2VydmljZSBwcm92aWRlcnMgaGFkIHdhcyB0aGF0IHRoZSBJRVRGIEJGRA0KPiA+
PiBzb2x1dGlvbg0KPiA+PiBleGNlZWRlZCB0aGVpciByZXF1aXJlbWVudHMgaW4gdGhhdCB0aGVy
ZSB3YXMgYWRkaXRpb25hbA0KPiBmdW5jdGlvbmFsaXR5DQo+ID4+IHRoZXkgZGlkDQo+ID4+IG5v
dCBzZWUgYSBuZWVkIGZvciwgYW5kIHRoYXQgdGhleSBjb25zaWRlcmVkIGFueSBhZGRpdGlvbmFs
DQo+ID4+IGZ1bmN0aW9uYWxpdHkNCj4gPj4gcGFyYXNpdGljLg0KPiA+PiA+DQo+ID4+ID5Ib3dl
dmVyIHRoaXMgaXMgYSBjb25zZXF1ZW5jZSBvZiBhZGFwdGluZyBhbiBleGlzdGluZyB0ZWNobm9s
b2d5IHRvDQo+IGENCj4gPj4gbmV3DQo+ID4+IGFwcGxpY2F0aW9uLiBJIGRvIG5vdCBzZWUgYW55
IHdheSBhcm91bmQgdGhhdC4gQW5kIHRoZSBlbnRpcmUgam9pbnQNCj4gPj4gcHJvamVjdCB3YXMN
Cj4gPj4gYmFzZWQgb24gdGhlIHByZW1pc2Ugb2YgZW5naW5lZXJpbmcgcmUtdXNlIG5vdCBncmVl
bmZpZWxkIGRlc2lnbi4NCj4gVGhhdA0KPiA+PiBpcyB3aGF0DQo+ID4+IGl0IHNhaWQgb24gdGhl
IHRpbiB1cCBmcm9udCwgYW5kIElNTyB3aHkgd2hlbiB0aGUgSUVURiBzdGFydGVkIGRvd24NCj4g
Pj4gdGhpcyBwYXRoDQo+ID4+IHBhY2tldCB0cmFuc3BvcnQgdHJhbnNpdGlvbmVkIGZyb20gYmVp
bmcgYSBtaW5vcml0eSBzcG9ydCB0bw0KPiA+PiBtYWluc3RyZWFtLCBzbyBpdA0KPiA+PiBpcyBh
IGJpdCBsYXRlIHRvIGNyeSBmb3VsLi4uLg0KPiA+PiA+DQo+ID4+ID5NeSAyIGNlbnRzDQo+ID4+
ID5EYXZlDQo+ID4+ID4NCj4gPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX18NCj4gPj4gbXBscyBtYWlsaW5nIGxpc3QNCj4gPj4gbXBsc0BpZXRmLm9yZw0K
PiA+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21wbHMNCj4gPg0KPiAN
Cg0K

From john-ietf@jck.com  Wed Jul 13 15:19:13 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 27A9811E80A6 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 15:19:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.766
X-Spam-Level: 
X-Spam-Status: No, score=-102.766 tagged_above=-999 required=5 tests=[AWL=-0.167, 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 gddU-214U5zM for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 15:19:02 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 97BCE11E809A for <ietf@ietf.org>; Wed, 13 Jul 2011 15:19:02 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Qh7ll-0000FO-Nm; Wed, 13 Jul 2011 18:19:01 -0400
Date: Wed, 13 Jul 2011 18:19:00 -0400
From: John C Klensin <john-ietf@jck.com>
To: Marc Petit-Huguenin <petithug@acm.org>
Subject: Re: Confidentiality notices on email messages
Message-ID: <04AE56F0C4CE8168D1B38D59@PST.JCK.COM>
In-Reply-To: <4E1DCA13.9030301@acm.org>
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <29987.1310565058@marajade.sandelman.ca> <4E1DCA13.9030301@acm.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 22:19:13 -0000

--On Wednesday, July 13, 2011 09:38 -0700 Marc Petit-Huguenin
<petithug@acm.org> wrote:

>...
> Yes, and perhaps disclaimers/confidentiality notices should be
> standardized with their own MIME type to make automatic
> processing easier so receivers of this kind of notice
> (mailing-list or other) can respect the wishes of the sender.
>...

What did you have in mind?  Something like

  Content-type: text/legal-noise; charset=...

or perhaps

  Content-type: text/noise; noise-type="bogus-legal-disclaimer",
charset=...

:-(

    john




From dave@cridland.net  Wed Jul 13 15:23:16 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 30B9611E8167 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 15:23:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WHWuXBG3ffGZ for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 15:23:10 -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 A0D2F11E809A for <ietf@ietf.org>; Wed, 13 Jul 2011 15:23:10 -0700 (PDT)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id 9AF941168087; Wed, 13 Jul 2011 23:23:00 +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 HLvZ1Ofgz1Cu; Wed, 13 Jul 2011 23:22:53 +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 6514D1168067; Wed, 13 Jul 2011 23:22:53 +0100 (BST)
Subject: Re: Confidentiality notices on email messages
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <29987.1310565058@marajade.sandelman.ca> <4E1DCA13.9030301@acm.org> <04AE56F0C4CE8168D1B38D59@PST.JCK.COM>
In-Reply-To: <04AE56F0C4CE8168D1B38D59@PST.JCK.COM>
MIME-Version: 1.0
Message-Id: <2018.1310595773.421047@puncture>
Date: Wed, 13 Jul 2011 23:22:53 +0100
From: Dave Cridland <dave@cridland.net>
To: John C Klensin <john-ietf@jck.com>, IETF-Discussion <ietf@ietf.org>, Marc Petit-Huguenin <petithug@acm.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, 13 Jul 2011 22:23:16 -0000

On Wed Jul 13 23:19:00 2011, John C Klensin wrote:
> 
> 
> --On Wednesday, July 13, 2011 09:38 -0700 Marc Petit-Huguenin
> <petithug@acm.org> wrote:
> 
> >...
> > Yes, and perhaps disclaimers/confidentiality notices should be
> > standardized with their own MIME type to make automatic
> > processing easier so receivers of this kind of notice
> > (mailing-list or other) can respect the wishes of the sender.
> >...
> 
> What did you have in mind?  Something like
> 
>   Content-type: text/legal-noise; charset=...

text/legal-noise+xml, obviously.

Only XML is sufficiently verbose for lawyers.

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 petithug@acm.org  Wed Jul 13 15:49:09 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 9925A11E81D1 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 15:49:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.529
X-Spam-Level: 
X-Spam-Status: No, score=-103.529 tagged_above=-999 required=5 tests=[AWL=1.071, BAYES_00=-2.599, GB_I_LETTER=-2, 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 qXBP+Bgg+hso for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 15:49:04 -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 950C911E8075 for <ietf@ietf.org>; Wed, 13 Jul 2011 15:49:04 -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 6EFFB2199E; Thu, 14 Jul 2011 00:47:34 +0200 (CEST)
Message-ID: <4E1E20DD.9040103@acm.org>
Date: Wed, 13 Jul 2011 15:49:01 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110626 Iceowl/1.0b2 Icedove/3.1.11
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Confidentiality notices on email messages
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <29987.1310565058@marajade.sandelman.ca> <4E1DCA13.9030301@acm.org> <04AE56F0C4CE8168D1B38D59@PST.JCK.COM>
In-Reply-To: <04AE56F0C4CE8168D1B38D59@PST.JCK.COM>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 22:49:09 -0000

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

On 07/13/2011 03:19 PM, John C Klensin wrote:
> 
> 
> --On Wednesday, July 13, 2011 09:38 -0700 Marc Petit-Huguenin
> <petithug@acm.org> wrote:
> 
>> ...
>> Yes, and perhaps disclaimers/confidentiality notices should be
>> standardized with their own MIME type to make automatic
>> processing easier so receivers of this kind of notice
>> (mailing-list or other) can respect the wishes of the sender.
>> ...
> 
> What did you have in mind?  Something like
> 
>   Content-type: text/legal-noise; charset=...
> 
> or perhaps
> 
>   Content-type: text/noise; noise-type="bogus-legal-disclaimer",
> charset=...
> 
> :-(
> 

No, I was serious.  I think that the best response to this kind of stuff is to
do what they ask to the letter.  If we can convince the senders that annotating
their notice with an header will permit us to obey their request, everybody wins.

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

iEYEARECAAYFAk4eINwACgkQ9RoMZyVa61d2ugCfaPniSosAr3MXqnZQzzFG2PC/
j0MAoJqZ2gYeOHZNBRh0pf0VrJCsvZam
=6Z3z
-----END PGP SIGNATURE-----

From mrex@sap.com  Wed Jul 13 15:51:14 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 9EA9C21F8BB0 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 15:51:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.878
X-Spam-Level: 
X-Spam-Status: No, score=-9.878 tagged_above=-999 required=5 tests=[AWL=0.371,  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 RodlcusTP0om for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 15:51:14 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id E29F421F8BA7 for <ietf@ietf.org>; Wed, 13 Jul 2011 15:51:13 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id p6DMp9Yl028237 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 14 Jul 2011 00:51:09 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201107132251.p6DMp8gK023481@fs4113.wdf.sap.corp>
Subject: Re: Confidentiality notices on email messages
To: randy@qualcomm.com (Randall Gellens)
Date: Thu, 14 Jul 2011 00:51:08 +0200 (MEST)
In-Reply-To: <p0624064fca428419c7be@loud.pensive.org> from "Randall Gellens" at Jul 12, 11 04:12:12 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: barryleiba@computer.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: Wed, 13 Jul 2011 22:51:14 -0000

Randall Gellens wrote:
> 
> I'm not a lawyer and I don't play one on TV or the net, so I likely 
> don't understand the situation.  As a point of possibly interesting 
> information, once upon a time, at a training session held by a lawyer 
> regarding how to protect confidential information, we were admonished 
> not to slap a "confidential" label on anything automatically or 
> without consideration, because, we were warned, doing so can cause 
> the label to lose meaning for everything.  In other words, if we 
> labelled everything "confidential," then we were really saying 
> nothing was confidential.

Congratulation for having met a lawyer with a clue in law.
This assessment is definitely valid for Germany.


> 
> Ever since, I've wondered if these notices were set up by someone who 
> is a lawyer and does understand the situation, or if they were set up 
> by someone who saw others do it, or heard that this sort of thing was 
> needed.

These notices are often suggested by real lawyers.

But it is hard to determine whether they are from the simple
clueless type, or whether they know that this notice is bogus, but
also know that there are many clueless folks, clueless other lawyers
and clueless judges out there that will fall for it, therefore
providing some small value in probabilistic terms. 


-Martin


From touch@isi.edu  Wed Jul 13 16:02:36 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 A141D21F8C0D; Wed, 13 Jul 2011 16:02:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.38
X-Spam-Level: 
X-Spam-Status: No, score=-103.38 tagged_above=-999 required=5 tests=[AWL=-0.781, 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 dMIXt7-KNci6; Wed, 13 Jul 2011 16:02:32 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 5684721F8C07; Wed, 13 Jul 2011 16:02:32 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id p6DN24FG009669 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 13 Jul 2011 16:02:04 -0700 (PDT)
Message-ID: <4E1E23EC.7040502@isi.edu>
Date: Wed, 13 Jul 2011 16:02:04 -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: notes from discussion of KARP design guidelines
References: <4E17210A.1070402@joelhalpern.com>	<5662A966-70AD-4A63-BA31-8CE1C9635687@cisco.com>	<4E1747BB.8080602@cisco.com> <4E19B2DC.4030003@joelhalpern.com>	<4E1CC976.9000007@isi.edu> <4E1CCC76.9090409@cisco.com>	<4E1CE644.9090300@isi.edu> <4E1DD654.3030603@joelhalpern.com> <4E1DE2C2.8090209@mti-systems.com> <4E1DE530.5060701@joelhalpern.com> <4E1DEAEB.9040208@isi.edu> <4E1E070F.6000103@joelhalpern.com> <4E1E093D.9040903@isi.edu> <4E1E0D70.7040801@joelhalpern.com>
In-Reply-To: <4E1E0D70.7040801@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>, stbryant@cisco.com, IETF discussion list <ietf@ietf.org>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 23:02:36 -0000

Hi, Joel,

On 7/13/2011 2:26 PM, Joel M. Halpern wrote:
> You wording seems to induce confusion.
> Of course the routing message content is part of the message
> on-the-wire. It is the content of the message. It is in fact a
> significant part of what is being protected.
>
> What is NOT part of the scope, and which the text says is not part of
> the scope, is the validation of that information. KARP is not assuring
> that the information is valid. it is responsible to ensure that the
> message is not modified between the two peers.
>
> Yes, this means that there is an overlap in protection between
> validation information and packet authentication information.So? The
> scope is very clear as to whose problem is whose.

That makes absolutely no sense. If there's overlap, then it's obviously 
unclear as to whose problem is whose.

> (This is merely a
> statement of fact. If we have path signing and TCP-AO, there are two
> sets of mechanisms preventing modification of some of the BGP information.)

I appreciate that different layers can include redundant protections. 
However, I'm trying to understand what is *expected* from each layer.

> The text after the bullet list explicitly says what part is in scope. it
> does not require any assumption or inference.
> If there is specific wording you would like to suggest to improve the
> introductory scoping material, I would be happy to look at it.

Glad to, with a bit more context.

Can you please define what is being validated in the third bullet that 
is NOT protected by the last one or vice versa? AFAICT, it would be:

#3 is entirely responsible for ensuring that a source has permission to 
advertise a particular route

#3 or #4 could confirm the identity of the source of a piece of 
information (#3 is required if transitive, #4 works only if directly 
communicated).

#3 or #4 could confirm the integrity of such information

#4 is required to protect the properties of lower layers insofar as they 
are used as such information to the routing protocol (e.g., BGP tossing 
out routes because TCP connections fail).

If this is the case, then I understand 4 as protecting the *channel* 
over which routing messages are exchanged (which ends up protecting the 
messages too), and 3 as focusing on the routing layer messages themselves.

Is that the case?

Joe



> On 7/13/2011 5:08 PM, Joe Touch wrote:
>> Hi, Joel,
>>
>> On 7/13/2011 1:58 PM, Joel M. Halpern wrote:
>>> I don't understand your description of the problem.
>>> As you quote, the document clearly states its scope.
>>> So, when we then define the term "on-the-wire", I don't think we need to
>>> restate the scope definition. It woudl seem coutner-productive.
>>
>> The current scope is clear from the bullet list only by the assumption
>> that (a) the bullets are mutually exclusive, and (b) since the "routing
>> message content" is clear, it cannot be part of "on the wire".
>>
>> I.e., it requires the reader interpret scope by a matter of deduction
>> and exclusion, rather than stating it clearly and explicitly.
>>
>> Joe
>>
>>>
>>> Yours,
>>> Joel
>>>
>>>
>>> On 7/13/2011 2:58 PM, Joe Touch wrote:
>>>>
>>>>
>>>> On 7/13/2011 11:34 AM, Joel M. Halpern wrote:
>>>>> As I said in my earlier note proposing responses to Joe, we would be
>>>>> happy to some text in the front clarifying the usage. Quoting from my
>>>>> earlier email:
>>>>>
>>>>> This text would note that it is a widely used term in IETF documents,
>>>>> including many RFCs. It would also state for clarity that in this
>>>>> document it is used to refer to the message sent from one routing
>>>>> process to another.
>>>>
>>>> Here's why this is a problem:
>>>>
>>>> 1- does this refer to signing a BGP path?
>>>>
>>>> 2- does this refer to protecting the channel over which BGP paths are
>>>> exchanged?
>>>>
>>>> From the intro:
>>>> Four main steps were identified for that tightening:
>>>>
>>>> o More secure mechanisms and practices for operating routers.
>>>> ...
>>>>
>>>> o Cleaning up the Internet Routing Registry repository [IRR],
>>>> ...
>>>>
>>>> o Specifications for cryptographic validation of routing message
>>>> content.
>>>> ...
>>>>
>>>> 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.
>>>>
>>>> So this document is clearly NOT about "the message from one routing
>>>> process to another (that would be 'routing message content', IMO).
>>>> I.e.,
>>>> this doc focuses on securing the transfer mechanism NOT the message.
>>>>
>>>> Thus this is the key to the entirety of the doc. This doc needs to be
>>>> very clear about what this is, at which point it can certainly also
>>>> then
>>>> refer back to the original RFC (e.g., "this is referred to in RFC 4948
>>>> as 'on the wire'").
>>>>
>>>> Joe
>>>>
>>>>
>>>>
>>

From jmh@joelhalpern.com  Wed Jul 13 16:25: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 7EA5611E809B; Wed, 13 Jul 2011 16:25:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.557
X-Spam-Level: 
X-Spam-Status: No, score=-102.557 tagged_above=-999 required=5 tests=[AWL=0.042, 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 k6N1ATmqcsSk; Wed, 13 Jul 2011 16:25:03 -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 E232111E8075; Wed, 13 Jul 2011 16:25:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 1632232444BF; Wed, 13 Jul 2011 16:25:02 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.154.181.24] (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 C753132289B4; Wed, 13 Jul 2011 16:25:00 -0700 (PDT)
Message-ID: <4E1E2949.30803@joelhalpern.com>
Date: Wed, 13 Jul 2011 19:24:57 -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: notes from discussion of KARP design guidelines
References: <4E17210A.1070402@joelhalpern.com>	<5662A966-70AD-4A63-BA31-8CE1C9635687@cisco.com>	<4E1747BB.8080602@cisco.com> <4E19B2DC.4030003@joelhalpern.com>	<4E1CC976.9000007@isi.edu> <4E1CCC76.9090409@cisco.com>	<4E1CE644.9090300@isi.edu> <4E1DD654.3030603@joelhalpern.com> <4E1DE2C2.8090209@mti-systems.com> <4E1DE530.5060701@joelhalpern.com> <4E1DEAEB.9040208@isi.edu> <4E1E070F.6000103@joelhalpern.com> <4E1E093D.9040903@isi.edu> <4E1E0D70.7040801@joelhalpern.com> <4E1E23EC.7040502@isi.edu>
In-Reply-To: <4E1E23EC.7040502@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>, stbryant@cisco.com, IETF discussion list <ietf@ietf.org>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 23:25:08 -0000

I am not sure what you are asking.
KARP is never concerned with whether the party is authorized to send the 
information it is sending.
KARP is concerned with assuring that the information received is either 
the information sent, or recognizably NOT the information sent (so it 
can be discarded.)  (I would have said that more simply, but I have been 
beat up by security folks for descriing what authentication does too 
simply.)  It is also concerned that the receiver be able to correctly 
tell who sent the message, or discard the message.

(Which layer those determinations are made at varies across the 
protocols, and is something we were trying not to get detailed about in 
the design guidelines document.)

Sent and received refer to inforamtion being exchanged between directly 
communicating IP routers.  (Of course, directly depends upon the 
protocol and configuration, as both targetted LDP and remote BGP the two 
parties are directly communicating through other routers.)

This document is NOT supposed to be the framework document for the KARP 
work.  The working group did not have enough energy to produce that, and 
I would therefore not want to turn this into a full-blown framework 
document.
With that understanding, if there is an extra paragraph that will help 
the introduction be clear about this, please send text.

Yours,
Joel

On 7/13/2011 7:02 PM, Joe Touch wrote:
> Hi, Joel,
>
> On 7/13/2011 2:26 PM, Joel M. Halpern wrote:
>> You wording seems to induce confusion.
>> Of course the routing message content is part of the message
>> on-the-wire. It is the content of the message. It is in fact a
>> significant part of what is being protected.
>>
>> What is NOT part of the scope, and which the text says is not part of
>> the scope, is the validation of that information. KARP is not assuring
>> that the information is valid. it is responsible to ensure that the
>> message is not modified between the two peers.
>>
>> Yes, this means that there is an overlap in protection between
>> validation information and packet authentication information.So? The
>> scope is very clear as to whose problem is whose.
>
> That makes absolutely no sense. If there's overlap, then it's obviously
> unclear as to whose problem is whose.
>
>> (This is merely a
>> statement of fact. If we have path signing and TCP-AO, there are two
>> sets of mechanisms preventing modification of some of the BGP
>> information.)
>
> I appreciate that different layers can include redundant protections.
> However, I'm trying to understand what is *expected* from each layer.
>
>> The text after the bullet list explicitly says what part is in scope. it
>> does not require any assumption or inference.
>> If there is specific wording you would like to suggest to improve the
>> introductory scoping material, I would be happy to look at it.
>
> Glad to, with a bit more context.
>
> Can you please define what is being validated in the third bullet that
> is NOT protected by the last one or vice versa? AFAICT, it would be:
>
> #3 is entirely responsible for ensuring that a source has permission to
> advertise a particular route
>
> #3 or #4 could confirm the identity of the source of a piece of
> information (#3 is required if transitive, #4 works only if directly
> communicated).
>
> #3 or #4 could confirm the integrity of such information
>
> #4 is required to protect the properties of lower layers insofar as they
> are used as such information to the routing protocol (e.g., BGP tossing
> out routes because TCP connections fail).
>
> If this is the case, then I understand 4 as protecting the *channel*
> over which routing messages are exchanged (which ends up protecting the
> messages too), and 3 as focusing on the routing layer messages themselves.
>
> Is that the case?
>
> Joe
>
>
>
>> On 7/13/2011 5:08 PM, Joe Touch wrote:
>>> Hi, Joel,
>>>
>>> On 7/13/2011 1:58 PM, Joel M. Halpern wrote:
>>>> I don't understand your description of the problem.
>>>> As you quote, the document clearly states its scope.
>>>> So, when we then define the term "on-the-wire", I don't think we
>>>> need to
>>>> restate the scope definition. It woudl seem coutner-productive.
>>>
>>> The current scope is clear from the bullet list only by the assumption
>>> that (a) the bullets are mutually exclusive, and (b) since the "routing
>>> message content" is clear, it cannot be part of "on the wire".
>>>
>>> I.e., it requires the reader interpret scope by a matter of deduction
>>> and exclusion, rather than stating it clearly and explicitly.
>>>
>>> Joe
>>>
>>>>
>>>> Yours,
>>>> Joel
>>>>
>>>>
>>>> On 7/13/2011 2:58 PM, Joe Touch wrote:
>>>>>
>>>>>
>>>>> On 7/13/2011 11:34 AM, Joel M. Halpern wrote:
>>>>>> As I said in my earlier note proposing responses to Joe, we would be
>>>>>> happy to some text in the front clarifying the usage. Quoting from my
>>>>>> earlier email:
>>>>>>
>>>>>> This text would note that it is a widely used term in IETF documents,
>>>>>> including many RFCs. It would also state for clarity that in this
>>>>>> document it is used to refer to the message sent from one routing
>>>>>> process to another.
>>>>>
>>>>> Here's why this is a problem:
>>>>>
>>>>> 1- does this refer to signing a BGP path?
>>>>>
>>>>> 2- does this refer to protecting the channel over which BGP paths are
>>>>> exchanged?
>>>>>
>>>>> From the intro:
>>>>> Four main steps were identified for that tightening:
>>>>>
>>>>> o More secure mechanisms and practices for operating routers.
>>>>> ...
>>>>>
>>>>> o Cleaning up the Internet Routing Registry repository [IRR],
>>>>> ...
>>>>>
>>>>> o Specifications for cryptographic validation of routing message
>>>>> content.
>>>>> ...
>>>>>
>>>>> 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.
>>>>>
>>>>> So this document is clearly NOT about "the message from one routing
>>>>> process to another (that would be 'routing message content', IMO).
>>>>> I.e.,
>>>>> this doc focuses on securing the transfer mechanism NOT the message.
>>>>>
>>>>> Thus this is the key to the entirety of the doc. This doc needs to be
>>>>> very clear about what this is, at which point it can certainly also
>>>>> then
>>>>> refer back to the original RFC (e.g., "this is referred to in RFC 4948
>>>>> as 'on the wire'").
>>>>>
>>>>> Joe
>>>>>
>>>>>
>>>>>
>>>
>

From touch@isi.edu  Wed Jul 13 17:00:17 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 976F121F8B3C; Wed, 13 Jul 2011 17:00:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.353
X-Spam-Level: 
X-Spam-Status: No, score=-103.353 tagged_above=-999 required=5 tests=[AWL=-0.754, 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 5Qepsl+aRKwA; Wed, 13 Jul 2011 17:00:13 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 6516821F8B3B; Wed, 13 Jul 2011 17:00:13 -0700 (PDT)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id p6DNxlff026880 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 13 Jul 2011 16:59:48 -0700 (PDT)
Message-ID: <4E1E3173.2000803@isi.edu>
Date: Wed, 13 Jul 2011 16:59:47 -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: notes from discussion of KARP design guidelines
References: <4E17210A.1070402@joelhalpern.com>	<5662A966-70AD-4A63-BA31-8CE1C9635687@cisco.com>	<4E1747BB.8080602@cisco.com> <4E19B2DC.4030003@joelhalpern.com>	<4E1CC976.9000007@isi.edu> <4E1CCC76.9090409@cisco.com>	<4E1CE644.9090300@isi.edu> <4E1DD654.3030603@joelhalpern.com> <4E1DE2C2.8090209@mti-systems.com> <4E1DE530.5060701@joelhalpern.com> <4E1DEAEB.9040208@isi.edu> <4E1E070F.6000103@joelhalpern.com> <4E1E093D.9040903@isi.edu> <4E1E0D70.7040801@joelhalpern.com> <4E1E23EC.7040502@isi.edu> <4E1E2949.30803@joelhalpern.com>
In-Reply-To: <4E1E2949.30803@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>, stbryant@cisco.com, IETF discussion list <ietf@ietf.org>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jul 2011 00:00:17 -0000

Hi, Joel,

On 7/13/2011 4:24 PM, Joel M. Halpern wrote:
> I am not sure what you are asking.
> KARP is never concerned with whether the party is authorized to send the
> information it is sending.

Right - that's bullet 3.

> KARP is concerned with assuring that the information received is either
> the information sent, or recognizably NOT the information sent (so it
> can be discarded.) (I would have said that more simply, but I have been
> beat up by security folks for describing what authentication does too
> simply.) It is also concerned that the receiver be able to correctly
> tell who sent the message, or discard the message.
>
> (Which layer those determinations are made at varies across the
> protocols, and is something we were trying not to get detailed about in
> the design guidelines document.)
>
> Sent and received refer to inforamtion being exchanged between directly
> communicating IP routers. (Of course, directly depends upon the protocol
> and configuration, as both targetted LDP and remote BGP the two parties
> are directly communicating through other routers.)

OK - so that's protecting the information exchanged between two routers.

I would argue that it also presumes protecting such information whether 
it's explicit at the routing layer (e.g., BGP path messages), other 
headers (e.g., src/dst addrs, TTLs, and the like, if relied upon by the 
routing protocol), and the semantics of other layers of protocols (e.g., 
whether a connection remains "up", as with TCP or PPTP).

> This document is NOT supposed to be the framework document for the KARP
> work. The working group did not have enough energy to produce that, and
> I would therefore not want to turn this into a full-blown framework
> document.
> With that understanding, if there is an extra paragraph that will help
> the introduction be clear about this, please send text.

If we agree on the above, then I can proceed to document suggested 
changes and the paragraph.

Joe

>
> Yours,
> Joel
>
> On 7/13/2011 7:02 PM, Joe Touch wrote:
>> Hi, Joel,
>>
>> On 7/13/2011 2:26 PM, Joel M. Halpern wrote:
>>> You wording seems to induce confusion.
>>> Of course the routing message content is part of the message
>>> on-the-wire. It is the content of the message. It is in fact a
>>> significant part of what is being protected.
>>>
>>> What is NOT part of the scope, and which the text says is not part of
>>> the scope, is the validation of that information. KARP is not assuring
>>> that the information is valid. it is responsible to ensure that the
>>> message is not modified between the two peers.
>>>
>>> Yes, this means that there is an overlap in protection between
>>> validation information and packet authentication information.So? The
>>> scope is very clear as to whose problem is whose.
>>
>> That makes absolutely no sense. If there's overlap, then it's obviously
>> unclear as to whose problem is whose.
>>
>>> (This is merely a
>>> statement of fact. If we have path signing and TCP-AO, there are two
>>> sets of mechanisms preventing modification of some of the BGP
>>> information.)
>>
>> I appreciate that different layers can include redundant protections.
>> However, I'm trying to understand what is *expected* from each layer.
>>
>>> The text after the bullet list explicitly says what part is in scope. it
>>> does not require any assumption or inference.
>>> If there is specific wording you would like to suggest to improve the
>>> introductory scoping material, I would be happy to look at it.
>>
>> Glad to, with a bit more context.
>>
>> Can you please define what is being validated in the third bullet that
>> is NOT protected by the last one or vice versa? AFAICT, it would be:
>>
>> #3 is entirely responsible for ensuring that a source has permission to
>> advertise a particular route
>>
>> #3 or #4 could confirm the identity of the source of a piece of
>> information (#3 is required if transitive, #4 works only if directly
>> communicated).
>>
>> #3 or #4 could confirm the integrity of such information
>>
>> #4 is required to protect the properties of lower layers insofar as they
>> are used as such information to the routing protocol (e.g., BGP tossing
>> out routes because TCP connections fail).
>>
>> If this is the case, then I understand 4 as protecting the *channel*
>> over which routing messages are exchanged (which ends up protecting the
>> messages too), and 3 as focusing on the routing layer messages
>> themselves.
>>
>> Is that the case?
>>
>> Joe
>>
>>
>>
>>> On 7/13/2011 5:08 PM, Joe Touch wrote:
>>>> Hi, Joel,
>>>>
>>>> On 7/13/2011 1:58 PM, Joel M. Halpern wrote:
>>>>> I don't understand your description of the problem.
>>>>> As you quote, the document clearly states its scope.
>>>>> So, when we then define the term "on-the-wire", I don't think we
>>>>> need to
>>>>> restate the scope definition. It woudl seem coutner-productive.
>>>>
>>>> The current scope is clear from the bullet list only by the assumption
>>>> that (a) the bullets are mutually exclusive, and (b) since the "routing
>>>> message content" is clear, it cannot be part of "on the wire".
>>>>
>>>> I.e., it requires the reader interpret scope by a matter of deduction
>>>> and exclusion, rather than stating it clearly and explicitly.
>>>>
>>>> Joe
>>>>
>>>>>
>>>>> Yours,
>>>>> Joel
>>>>>
>>>>>
>>>>> On 7/13/2011 2:58 PM, Joe Touch wrote:
>>>>>>
>>>>>>
>>>>>> On 7/13/2011 11:34 AM, Joel M. Halpern wrote:
>>>>>>> As I said in my earlier note proposing responses to Joe, we would be
>>>>>>> happy to some text in the front clarifying the usage. Quoting
>>>>>>> from my
>>>>>>> earlier email:
>>>>>>>
>>>>>>> This text would note that it is a widely used term in IETF
>>>>>>> documents,
>>>>>>> including many RFCs. It would also state for clarity that in this
>>>>>>> document it is used to refer to the message sent from one routing
>>>>>>> process to another.
>>>>>>
>>>>>> Here's why this is a problem:
>>>>>>
>>>>>> 1- does this refer to signing a BGP path?
>>>>>>
>>>>>> 2- does this refer to protecting the channel over which BGP paths are
>>>>>> exchanged?
>>>>>>
>>>>>> From the intro:
>>>>>> Four main steps were identified for that tightening:
>>>>>>
>>>>>> o More secure mechanisms and practices for operating routers.
>>>>>> ...
>>>>>>
>>>>>> o Cleaning up the Internet Routing Registry repository [IRR],
>>>>>> ...
>>>>>>
>>>>>> o Specifications for cryptographic validation of routing message
>>>>>> content.
>>>>>> ...
>>>>>>
>>>>>> 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.
>>>>>>
>>>>>> So this document is clearly NOT about "the message from one routing
>>>>>> process to another (that would be 'routing message content', IMO).
>>>>>> I.e.,
>>>>>> this doc focuses on securing the transfer mechanism NOT the message.
>>>>>>
>>>>>> Thus this is the key to the entirety of the doc. This doc needs to be
>>>>>> very clear about what this is, at which point it can certainly also
>>>>>> then
>>>>>> refer back to the original RFC (e.g., "this is referred to in RFC
>>>>>> 4948
>>>>>> as 'on the wire'").
>>>>>>
>>>>>> Joe
>>>>>>
>>>>>>
>>>>>>
>>>>
>>

From jmh@joelhalpern.com  Wed Jul 13 17:01:29 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 32A5B11E8089; Wed, 13 Jul 2011 17:01:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.56
X-Spam-Level: 
X-Spam-Status: No, score=-102.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uS0wXRUsasxb; Wed, 13 Jul 2011 17:01:28 -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 8A76411E8075; Wed, 13 Jul 2011 17:01:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id CD686325C161; Wed, 13 Jul 2011 17:01:26 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.154.181.24] (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 C6C85325C15F; Wed, 13 Jul 2011 17:01:25 -0700 (PDT)
Message-ID: <4E1E31D1.7060509@joelhalpern.com>
Date: Wed, 13 Jul 2011 20:01:21 -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: notes from discussion of KARP design guidelines
References: <4E17210A.1070402@joelhalpern.com>	<5662A966-70AD-4A63-BA31-8CE1C9635687@cisco.com>	<4E1747BB.8080602@cisco.com> <4E19B2DC.4030003@joelhalpern.com>	<4E1CC976.9000007@isi.edu> <4E1CCC76.9090409@cisco.com>	<4E1CE644.9090300@isi.edu> <4E1DD654.3030603@joelhalpern.com> <4E1DE2C2.8090209@mti-systems.com> <4E1DE530.5060701@joelhalpern.com> <4E1DEAEB.9040208@isi.edu> <4E1E070F.6000103@joelhalpern.com> <4E1E093D.9040903@isi.edu> <4E1E0D70.7040801@joelhalpern.com> <4E1E23EC.7040502@isi.edu>
In-Reply-To: <4E1E23EC.7040502@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>, stbryant@cisco.com, IETF discussion list <ietf@ietf.org>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jul 2011 00:01:29 -0000

There may be a confusion of objectives.
The WG and chairs do not expect the design guidelines document to 
achieve a degree of thoroughness such taht if one checks every item in 
there, and nothing else, then one will be able to do a complete analysis 
of a routing protocol.
Rather, it is intended to provide assistance and a starting point for 
that analysis.  Folks writing analysis documents are expected to bring 
security and routing protocol skills to the table, and to make sure they 
spot all the issues.

Yours,
Joel

On 7/13/2011 7:02 PM, Joe Touch wrote:
> Hi, Joel,
>
> On 7/13/2011 2:26 PM, Joel M. Halpern wrote:
>> You wording seems to induce confusion.
>> Of course the routing message content is part of the message
>> on-the-wire. It is the content of the message. It is in fact a
>> significant part of what is being protected.
>>
>> What is NOT part of the scope, and which the text says is not part of
>> the scope, is the validation of that information. KARP is not assuring
>> that the information is valid. it is responsible to ensure that the
>> message is not modified between the two peers.
>>
>> Yes, this means that there is an overlap in protection between
>> validation information and packet authentication information.So? The
>> scope is very clear as to whose problem is whose.
>
> That makes absolutely no sense. If there's overlap, then it's obviously
> unclear as to whose problem is whose.
>
>> (This is merely a
>> statement of fact. If we have path signing and TCP-AO, there are two
>> sets of mechanisms preventing modification of some of the BGP
>> information.)
>
> I appreciate that different layers can include redundant protections.
> However, I'm trying to understand what is *expected* from each layer.
>
>> The text after the bullet list explicitly says what part is in scope. it
>> does not require any assumption or inference.
>> If there is specific wording you would like to suggest to improve the
>> introductory scoping material, I would be happy to look at it.
>
> Glad to, with a bit more context.
>
> Can you please define what is being validated in the third bullet that
> is NOT protected by the last one or vice versa? AFAICT, it would be:
>
> #3 is entirely responsible for ensuring that a source has permission to
> advertise a particular route
>
> #3 or #4 could confirm the identity of the source of a piece of
> information (#3 is required if transitive, #4 works only if directly
> communicated).
>
> #3 or #4 could confirm the integrity of such information
>
> #4 is required to protect the properties of lower layers insofar as they
> are used as such information to the routing protocol (e.g., BGP tossing
> out routes because TCP connections fail).
>
> If this is the case, then I understand 4 as protecting the *channel*
> over which routing messages are exchanged (which ends up protecting the
> messages too), and 3 as focusing on the routing layer messages themselves.
>
> Is that the case?
>
> Joe
>
>
>
>> On 7/13/2011 5:08 PM, Joe Touch wrote:
>>> Hi, Joel,
>>>
>>> On 7/13/2011 1:58 PM, Joel M. Halpern wrote:
>>>> I don't understand your description of the problem.
>>>> As you quote, the document clearly states its scope.
>>>> So, when we then define the term "on-the-wire", I don't think we
>>>> need to
>>>> restate the scope definition. It woudl seem coutner-productive.
>>>
>>> The current scope is clear from the bullet list only by the assumption
>>> that (a) the bullets are mutually exclusive, and (b) since the "routing
>>> message content" is clear, it cannot be part of "on the wire".
>>>
>>> I.e., it requires the reader interpret scope by a matter of deduction
>>> and exclusion, rather than stating it clearly and explicitly.
>>>
>>> Joe
>>>
>>>>
>>>> Yours,
>>>> Joel
>>>>
>>>>
>>>> On 7/13/2011 2:58 PM, Joe Touch wrote:
>>>>>
>>>>>
>>>>> On 7/13/2011 11:34 AM, Joel M. Halpern wrote:
>>>>>> As I said in my earlier note proposing responses to Joe, we would be
>>>>>> happy to some text in the front clarifying the usage. Quoting from my
>>>>>> earlier email:
>>>>>>
>>>>>> This text would note that it is a widely used term in IETF documents,
>>>>>> including many RFCs. It would also state for clarity that in this
>>>>>> document it is used to refer to the message sent from one routing
>>>>>> process to another.
>>>>>
>>>>> Here's why this is a problem:
>>>>>
>>>>> 1- does this refer to signing a BGP path?
>>>>>
>>>>> 2- does this refer to protecting the channel over which BGP paths are
>>>>> exchanged?
>>>>>
>>>>> From the intro:
>>>>> Four main steps were identified for that tightening:
>>>>>
>>>>> o More secure mechanisms and practices for operating routers.
>>>>> ...
>>>>>
>>>>> o Cleaning up the Internet Routing Registry repository [IRR],
>>>>> ...
>>>>>
>>>>> o Specifications for cryptographic validation of routing message
>>>>> content.
>>>>> ...
>>>>>
>>>>> 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.
>>>>>
>>>>> So this document is clearly NOT about "the message from one routing
>>>>> process to another (that would be 'routing message content', IMO).
>>>>> I.e.,
>>>>> this doc focuses on securing the transfer mechanism NOT the message.
>>>>>
>>>>> Thus this is the key to the entirety of the doc. This doc needs to be
>>>>> very clear about what this is, at which point it can certainly also
>>>>> then
>>>>> refer back to the original RFC (e.g., "this is referred to in RFC 4948
>>>>> as 'on the wire'").
>>>>>
>>>>> Joe
>>>>>
>>>>>
>>>>>
>>>
>

From jmh@joelhalpern.com  Wed Jul 13 17:02:45 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 3DEA211E8101; Wed, 13 Jul 2011 17:02:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.563
X-Spam-Level: 
X-Spam-Status: No, score=-102.563 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TssLKhSiQfXP; Wed, 13 Jul 2011 17:02:44 -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 1C1E011E8089; Wed, 13 Jul 2011 17:02:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 7C5C1325C15B; Wed, 13 Jul 2011 17:02:43 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.154.181.24] (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 56A05325C15C; Wed, 13 Jul 2011 17:02:42 -0700 (PDT)
Message-ID: <4E1E321E.5010709@joelhalpern.com>
Date: Wed, 13 Jul 2011 20:02:38 -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: notes from discussion of KARP design guidelines
References: <4E17210A.1070402@joelhalpern.com>	<5662A966-70AD-4A63-BA31-8CE1C9635687@cisco.com>	<4E1747BB.8080602@cisco.com> <4E19B2DC.4030003@joelhalpern.com>	<4E1CC976.9000007@isi.edu> <4E1CCC76.9090409@cisco.com>	<4E1CE644.9090300@isi.edu> <4E1DD654.3030603@joelhalpern.com> <4E1DE2C2.8090209@mti-systems.com> <4E1DE530.5060701@joelhalpern.com> <4E1DEAEB.9040208@isi.edu> <4E1E070F.6000103@joelhalpern.com> <4E1E093D.9040903@isi.edu> <4E1E0D70.7040801@joelhalpern.com> <4E1E23EC.7040502@isi.edu> <4E1E2949.30803@joelhalpern.com> <4E1E3173.2000803@isi.edu>
In-Reply-To: <4E1E3173.2000803@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>, stbryant@cisco.com, IETF discussion list <ietf@ietf.org>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jul 2011 00:02:45 -0000

I am not sure we are in sync, but it looks clsoe enough that proposed 
introductory text would be veyr helpful at this point.

Yours,
Joel

On 7/13/2011 7:59 PM, Joe Touch wrote:
> Hi, Joel,
>
> On 7/13/2011 4:24 PM, Joel M. Halpern wrote:
>> I am not sure what you are asking.
>> KARP is never concerned with whether the party is authorized to send the
>> information it is sending.
>
> Right - that's bullet 3.
>
>> KARP is concerned with assuring that the information received is either
>> the information sent, or recognizably NOT the information sent (so it
>> can be discarded.) (I would have said that more simply, but I have been
>> beat up by security folks for describing what authentication does too
>> simply.) It is also concerned that the receiver be able to correctly
>> tell who sent the message, or discard the message.
>>
>> (Which layer those determinations are made at varies across the
>> protocols, and is something we were trying not to get detailed about in
>> the design guidelines document.)
>>
>> Sent and received refer to inforamtion being exchanged between directly
>> communicating IP routers. (Of course, directly depends upon the protocol
>> and configuration, as both targetted LDP and remote BGP the two parties
>> are directly communicating through other routers.)
>
> OK - so that's protecting the information exchanged between two routers.
>
> I would argue that it also presumes protecting such information whether
> it's explicit at the routing layer (e.g., BGP path messages), other
> headers (e.g., src/dst addrs, TTLs, and the like, if relied upon by the
> routing protocol), and the semantics of other layers of protocols (e.g.,
> whether a connection remains "up", as with TCP or PPTP).
>
>> This document is NOT supposed to be the framework document for the KARP
>> work. The working group did not have enough energy to produce that, and
>> I would therefore not want to turn this into a full-blown framework
>> document.
>> With that understanding, if there is an extra paragraph that will help
>> the introduction be clear about this, please send text.
>
> If we agree on the above, then I can proceed to document suggested
> changes and the paragraph.
>
> Joe
>
>>
>> Yours,
>> Joel
>>
>> On 7/13/2011 7:02 PM, Joe Touch wrote:
>>> Hi, Joel,
>>>
>>> On 7/13/2011 2:26 PM, Joel M. Halpern wrote:
>>>> You wording seems to induce confusion.
>>>> Of course the routing message content is part of the message
>>>> on-the-wire. It is the content of the message. It is in fact a
>>>> significant part of what is being protected.
>>>>
>>>> What is NOT part of the scope, and which the text says is not part of
>>>> the scope, is the validation of that information. KARP is not assuring
>>>> that the information is valid. it is responsible to ensure that the
>>>> message is not modified between the two peers.
>>>>
>>>> Yes, this means that there is an overlap in protection between
>>>> validation information and packet authentication information.So? The
>>>> scope is very clear as to whose problem is whose.
>>>
>>> That makes absolutely no sense. If there's overlap, then it's obviously
>>> unclear as to whose problem is whose.
>>>
>>>> (This is merely a
>>>> statement of fact. If we have path signing and TCP-AO, there are two
>>>> sets of mechanisms preventing modification of some of the BGP
>>>> information.)
>>>
>>> I appreciate that different layers can include redundant protections.
>>> However, I'm trying to understand what is *expected* from each layer.
>>>
>>>> The text after the bullet list explicitly says what part is in
>>>> scope. it
>>>> does not require any assumption or inference.
>>>> If there is specific wording you would like to suggest to improve the
>>>> introductory scoping material, I would be happy to look at it.
>>>
>>> Glad to, with a bit more context.
>>>
>>> Can you please define what is being validated in the third bullet that
>>> is NOT protected by the last one or vice versa? AFAICT, it would be:
>>>
>>> #3 is entirely responsible for ensuring that a source has permission to
>>> advertise a particular route
>>>
>>> #3 or #4 could confirm the identity of the source of a piece of
>>> information (#3 is required if transitive, #4 works only if directly
>>> communicated).
>>>
>>> #3 or #4 could confirm the integrity of such information
>>>
>>> #4 is required to protect the properties of lower layers insofar as they
>>> are used as such information to the routing protocol (e.g., BGP tossing
>>> out routes because TCP connections fail).
>>>
>>> If this is the case, then I understand 4 as protecting the *channel*
>>> over which routing messages are exchanged (which ends up protecting the
>>> messages too), and 3 as focusing on the routing layer messages
>>> themselves.
>>>
>>> Is that the case?
>>>
>>> Joe
>>>
>>>
>>>
>>>> On 7/13/2011 5:08 PM, Joe Touch wrote:
>>>>> Hi, Joel,
>>>>>
>>>>> On 7/13/2011 1:58 PM, Joel M. Halpern wrote:
>>>>>> I don't understand your description of the problem.
>>>>>> As you quote, the document clearly states its scope.
>>>>>> So, when we then define the term "on-the-wire", I don't think we
>>>>>> need to
>>>>>> restate the scope definition. It woudl seem coutner-productive.
>>>>>
>>>>> The current scope is clear from the bullet list only by the assumption
>>>>> that (a) the bullets are mutually exclusive, and (b) since the
>>>>> "routing
>>>>> message content" is clear, it cannot be part of "on the wire".
>>>>>
>>>>> I.e., it requires the reader interpret scope by a matter of deduction
>>>>> and exclusion, rather than stating it clearly and explicitly.
>>>>>
>>>>> Joe
>>>>>
>>>>>>
>>>>>> Yours,
>>>>>> Joel
>>>>>>
>>>>>>
>>>>>> On 7/13/2011 2:58 PM, Joe Touch wrote:
>>>>>>>
>>>>>>>
>>>>>>> On 7/13/2011 11:34 AM, Joel M. Halpern wrote:
>>>>>>>> As I said in my earlier note proposing responses to Joe, we
>>>>>>>> would be
>>>>>>>> happy to some text in the front clarifying the usage. Quoting
>>>>>>>> from my
>>>>>>>> earlier email:
>>>>>>>>
>>>>>>>> This text would note that it is a widely used term in IETF
>>>>>>>> documents,
>>>>>>>> including many RFCs. It would also state for clarity that in this
>>>>>>>> document it is used to refer to the message sent from one routing
>>>>>>>> process to another.
>>>>>>>
>>>>>>> Here's why this is a problem:
>>>>>>>
>>>>>>> 1- does this refer to signing a BGP path?
>>>>>>>
>>>>>>> 2- does this refer to protecting the channel over which BGP paths
>>>>>>> are
>>>>>>> exchanged?
>>>>>>>
>>>>>>> From the intro:
>>>>>>> Four main steps were identified for that tightening:
>>>>>>>
>>>>>>> o More secure mechanisms and practices for operating routers.
>>>>>>> ...
>>>>>>>
>>>>>>> o Cleaning up the Internet Routing Registry repository [IRR],
>>>>>>> ...
>>>>>>>
>>>>>>> o Specifications for cryptographic validation of routing message
>>>>>>> content.
>>>>>>> ...
>>>>>>>
>>>>>>> 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.
>>>>>>>
>>>>>>> So this document is clearly NOT about "the message from one routing
>>>>>>> process to another (that would be 'routing message content', IMO).
>>>>>>> I.e.,
>>>>>>> this doc focuses on securing the transfer mechanism NOT the message.
>>>>>>>
>>>>>>> Thus this is the key to the entirety of the doc. This doc needs
>>>>>>> to be
>>>>>>> very clear about what this is, at which point it can certainly also
>>>>>>> then
>>>>>>> refer back to the original RFC (e.g., "this is referred to in RFC
>>>>>>> 4948
>>>>>>> as 'on the wire'").
>>>>>>>
>>>>>>> Joe
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>
>

From johnl@iecc.com  Wed Jul 13 18:46:11 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 59F9221F8743 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 18:46:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.2
X-Spam-Level: 
X-Spam-Status: No, score=-110.2 tagged_above=-999 required=5 tests=[AWL=0.999,  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 tfYNoAvlVY00 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 18:46:07 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id E2E2121F872E for <ietf@ietf.org>; Wed, 13 Jul 2011 18:46:06 -0700 (PDT)
Received: (qmail 50256 invoked from network); 14 Jul 2011 01:46:05 -0000
Received: from gal.iecc.com (64.57.183.53) by mail2.iecc.com with SMTP; 14 Jul 2011 01:46:05 -0000
Received: (qmail 84709 invoked from network); 14 Jul 2011 01:46:05 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 14 Jul 2011 01:46:05 -0000
Date: 14 Jul 2011 01:45:44 -0000
Message-ID: <20110714014544.9252.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Confidentiality notices on email messages
In-Reply-To: <1D49B15C-643F-4D05-92BE-E42A309341CF@cybernothing.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: Thu, 14 Jul 2011 01:46:11 -0000

>Ever since, I've wondered if these notices were set up by someone
>who is a lawyer and does understand the situation, or if they were
>set up by someone who saw others do it, or heard that this sort of
>thing was needed.

It's clueless cargo cult lawyering.  I blogged on it in January:

  http://jl.ly/Internet/confid.html

At least in the US, which is where the IETF has its formal existence,
these notices have no legal merit at all.  They're just stupid.

R's,
John

PS: Anyone who wants to argue they're not stupid should include citations
to case law.

From johnl@iecc.com  Wed Jul 13 18:48:59 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 B306811E8134 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 18:48:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.256
X-Spam-Level: 
X-Spam-Status: No, score=-110.256 tagged_above=-999 required=5 tests=[AWL=0.943, 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 zURylztGmYgU for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 18:48:59 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id D300911E80E6 for <ietf@ietf.org>; Wed, 13 Jul 2011 18:48:58 -0700 (PDT)
Received: (qmail 50270 invoked from network); 14 Jul 2011 01:48:57 -0000
Received: from gal.iecc.com (64.57.183.53) by mail2.iecc.com with SMTP; 14 Jul 2011 01:48:57 -0000
Received: (qmail 85728 invoked from network); 14 Jul 2011 01:48:57 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 14 Jul 2011 01:48:57 -0000
Date: 14 Jul 2011 01:48:35 -0000
Message-ID: <20110714014835.9480.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Confidentiality notices on email messages
In-Reply-To: <4E1DCA13.9030301@acm.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: Thu, 14 Jul 2011 01:48:59 -0000

>Yes, and perhaps disclaimers/confidentiality notices should be
>standardized with their own MIME type to make automatic processing
>easier so receivers of this kind of notice (mailing-list or other)
>can respect the wishes of the sender.

That respect would of course be demonstrated by rejecting or
discarding the mail unread, to avoid any possibility that it could
fall into the wrong hands.

R's,
John

PS: Perhaps I should propose a revised RFC 5617 adding dkim=confidential.

From michel@arneill-py.sacramento.ca.us  Wed Jul 13 20:16:50 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 E93E421F8B20 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 20:16:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.22
X-Spam-Level: 
X-Spam-Status: No, score=-1.22 tagged_above=-999 required=5 tests=[AWL=-0.445,  BAYES_05=-1.11, 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 3l-XdzwZ-9R1 for <ietf@ietfa.amsl.com>; Wed, 13 Jul 2011 20:16:50 -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 17F1321F8B22 for <ietf@ietf.org>; Wed, 13 Jul 2011 20:16:44 -0700 (PDT)
Date: Wed, 13 Jul 2011 20:16:43 -0700
Subject: RE: Confidentiality notices on email messages
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF5EC@newserver.arneill-py.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
In-Reply-To: <20110714014544.9252.qmail@joyce.lan>
Content-Transfer-Encoding: quoted-printable
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Confidentiality notices on email messages
Thread-Index: AcxBx9AtuX4mPtohRnCX3l4HgcWbdAACUgIg
X-MimeOLE: Produced By Microsoft Exchange V6.5
References: <1D49B15C-643F-4D05-92BE-E42A309341CF@cybernothing.org> <20110714014544.9252.qmail@joyce.lan>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "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: Thu, 14 Jul 2011 03:16:51 -0000

> John Levine wrote:
> It's clueless cargo cult lawyering. I blogged on it in January:
> http://jl.ly/Internet/confid.html

That tells me a lot about the competence of some lawyers. A law firm
asked me some time ago to implement a system on their MS Exchange server
to automatically add such disclaimers. Although it's easy to configure
when using Outlook (using a signature), there was no disclaimer sent
when using the HTTP interface or the phones. They're not smart^H^H^H^H^H
technical enough to figure how to edit the "Sent from my Iphone" string,
either.

So, I sold and installed a commercial product:
http://www.exclaimer.com/products/mail-disclaimers/Default.aspx

ROTFL. Thanks John, you made my day. Hey, someone has to make a living
out of this BS, might as well be me.

Michel.


From prvs=0176ad012b=medel@globetel.com.ph  Wed Jul 13 20:28:05 2011
Return-Path: <prvs=0176ad012b=medel@globetel.com.ph>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B10B21F8BE9; Wed, 13 Jul 2011 20:28:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.675
X-Spam-Level: 
X-Spam-Status: No, score=-0.675 tagged_above=-999 required=5 tests=[AWL=0.929,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2KUNsBCbvVob; Wed, 13 Jul 2011 20:28:04 -0700 (PDT)
Received: from smtp02.globetel.com.ph (smtp02.globetel.com.ph [203.177.192.182]) by ietfa.amsl.com (Postfix) with ESMTP id 0A43C21F8BE6; Wed, 13 Jul 2011 20:28:03 -0700 (PDT)
Received: from exgtbh02.globetel.com ([10.225.208.154]) by smtp02.globetel.com.ph (8.14.4/8.14.4) with ESMTP id p6E3M2QU011163;  Thu, 14 Jul 2011 11:22:02 +0800
Received: from EXVSGT02.globetel.com ([10.225.208.145]) by exgtbh02.globetel.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 14 Jul 2011 11:28:00 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CC41D6.083C424B"
Subject: RE: [mpls] R: RE: R: Re: LastCall: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive Connectivity Verification, Continuity Check and Remote Defect indicationfor MPLS Transport Profile) to Proposed Standard
Date: Thu, 14 Jul 2011 11:28:00 +0800
Message-ID: <A5AD67DA1ACB9648831FD753485B2BFE1198DBAB@EXVSGT02.globetel.com>
In-Reply-To: <CA+RyBmX+sb0L9oFvMSUxF7_BgU-5m4MF3Z87F2k1D_Py_AY_8A@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] R: RE: R: Re: LastCall: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive Connectivity Verification, Continuity Check and Remote Defect indicationfor MPLS Transport Profile) to Proposed Standard
Thread-Index: AcxB0NKcS4oTg/PkTlS6nVs+/iJYxQABNEaw
X-Priority: 1
Priority: Urgent
Importance: high
References: <24102355.3308421310589129962.JavaMail.defaultUser@defaultHost> <CA+RyBmX+sb0L9oFvMSUxF7_BgU-5m4MF3Z87F2k1D_Py_AY_8A@mail.gmail.com>
From: "GT RAMIREZ, Medel G." <medel@globetel.com.ph>
To: <erminio.ottone_69@libero.it>
X-OriginalArrivalTime: 14 Jul 2011 03:28:00.0998 (UTC) FILETIME=[08996860:01CC41D6]
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.4.6813, 1.0.211, 0.0.0000 definitions=2011-07-14_02:2011-07-14, 2011-07-14, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=1 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1012030000 definitions=main-1107130233
Cc: Greg Mirsky <gregimirsky@gmail.com>, ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>, mpls@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jul 2011 03:28:05 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CC41D6.083C424B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="ISO-8859-1"

Erminio Hi,

I belong to an Operator, I strongly agree with Greg.

=20

Regards

Medel

________________________________

From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
Greg Mirsky
Sent: Thursday, July 14, 2011 10:50 AM
To: erminio.ottone_69@libero.it
Cc: mpls@ietf.org; IETF-Announce; ietf@ietf.org
Subject: Re: [mpls] R: RE: R: Re: LastCall:
<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive Connectivity
Verification, Continuity Check and Remote Defect indicationfor MPLS
Transport Profile) to Proposed Standard

=20

Dear Erminio,
even though I'm not an operator but I think that you've went bit too far
in your first generalization.
"Every generalization is wrong, including this one"

Regards,
Greg

On Wed, Jul 13, 2011 at 1:32 PM, erminio.ottone_69@libero.it
<erminio.ottone_69@libero.it> wrote:

The technical concern raised during the WG poll has not been resolved so
the
history definetely matters.

Quoting RFC5921:

  There are thus two objectives for MPLS-TP:

  1.  To enable MPLS to be deployed in a transport network and operated
      in a similar manner to existing transport technologies.

  2.  To enable MPLS to support packet transport services with a
      similar degree of predictability to that found in existing
      transport networks.

Based on the extensive comments provided by transport operators and
ITU-T
community, the solution in this draft is useless in case 1.

The fact that the solution in this draft is not backward compatible with
existing IP/MPLS BFD implementations means that this solution is also
uselesee
in case 2.

Are there other undocumented use cases for MPLS-TP deployments?

>----Messaggio originale----
>Da: nurit.sprecher@nsn.com
>Data: 7-lug-2011 11.59
>A: <erminio.ottone_69@libero.it>, <RCosta@ptinovacao.pt>,
<ietf@ietf.org>,

"IETF-Announce"<ietf-announce@ietf.org>

>Cc: <mpls@ietf.org>
>Ogg: RE: [mpls] R: Re: LastCall:
&lt;draft-ietf-mpls-tp-cc-cv-rdi-05.txt&gt;

(Proactive      Connectivity    Verification,Continuity Check and Remote
Defect

indicationfor   MPLS    Transport       Profile) to Proposed Standard

>
>Erminio,
>I do not think the history is relevant for this specific discussion...
>Also I find it inappropriate to give statements with no justifications
>behind.
>You say: "the solution in this draft is useless for many MPLS-TP
>deployments.".  in order to seriously consider your comment, you have
to
>show why it is useless and which requirements are not satisfied.
>Otherwise you cannot expect anyone to refer to your point.
>Best regards,
>Nurit
>
>P.s. did you mean that the document is useless to available
non-standard
>deployments, e.g. T-MPLS?
>
>



_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

=20

This e-mail message (including attachments, if any) is intended for the use=
 of the individual or the entity to whom it is addressed and may contain in=
formation that is privileged, proprietary, confidential and exempt from dis=
closure. If you are not the intended recipient, you are notified that any d=
issemination, distribution or copying of this communication is strictly pro=
hibited. If you have received this communication in error, please notify th=
e sender and delete this E-mail message immediately.

------_=_NextPart_001_01CC41D6.083C424B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="ISO-8859-1"

<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=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 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@Batang";}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Erminio Hi,<o:p></o:p></span></font></=
p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I belong to an Operator, I strongly ag=
ree
with Greg.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Regards<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Medel<o:p></o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font siz=
e=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span style=3D'font-si=
ze:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] <b><span style=3D'font=
-weight:
bold'>On Behalf Of </span></b>Greg Mirsky<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, July 14, 2011
10:50 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> erminio.ottone_69@libero=
.it<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> mpls@ietf.org; IETF-Anno=
unce;
ietf@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [mpls] R: RE: R=
: Re:
LastCall: &lt;draft-ietf-mpls-tp-cc-cv-rdi-05.txt&gt; (Proactive Connectivi=
ty
Verification, Continuity Check and Remote Defect indicationfor MPLS Transpo=
rt
Profile) to Proposed Standard</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>Dear Erminio,<br>
even though I'm not an operator but I think that you've went bit too far in
your first generalization.<br>
&quot;Every generalization is wrong, including this one&quot;<br>
<br>
Regards,<br>
Greg<o:p></o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>On Wed, Jul 13, 2011 at 1:32 PM, <a
href=3D"mailto:erminio.ottone_69@libero.it">erminio.ottone_69@libero.it</a>=
 &lt;<a
href=3D"mailto:erminio.ottone_69@libero.it">erminio.ottone_69@libero.it</a>=
&gt;
wrote:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>The technical concern raised during the WG poll has not been resolv=
ed
so the<br>
history definetely matters.<br>
<br>
Quoting RFC5921:<br>
<br>
&nbsp; There are thus two objectives for MPLS-TP:<br>
<br>
&nbsp; 1. &nbsp;To enable MPLS to be deployed in a transport network and
operated<br>
&nbsp; &nbsp; &nbsp; in a similar manner to existing transport technologies=
.<br>
<br>
&nbsp; 2. &nbsp;To enable MPLS to support packet transport services with a<=
br>
&nbsp; &nbsp; &nbsp; similar degree of predictability to that found in exis=
ting<br>
&nbsp; &nbsp; &nbsp; transport networks.<br>
<br>
Based on the extensive comments provided by transport operators and ITU-T<b=
r>
community, the solution in this draft is useless in case 1.<br>
<br>
The fact that the solution in this draft is not backward compatible with<br>
existing IP/MPLS BFD implementations means that this solution is also usele=
see<br>
in case 2.<br>
<br>
Are there other undocumented use cases for MPLS-TP deployments?<br>
<br>
&gt;----Messaggio originale----<br>
&gt;Da: <a href=3D"mailto:nurit.sprecher@nsn.com">nurit.sprecher@nsn.com</a=
><br>
&gt;Data: 7-lug-2011 11.59<br>
&gt;A: &lt;<a href=3D"mailto:erminio.ottone_69@libero.it">erminio.ottone_69=
@libero.it</a>&gt;,
&lt;<a href=3D"mailto:RCosta@ptinovacao.pt">RCosta@ptinovacao.pt</a>&gt;, &=
lt;<a
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;,<o:p></o:p></span></fon=
t></p>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>&quot;IETF-Announce&quot;&lt;<a href=3D"mailto:ietf-announce@ietf.o=
rg">ietf-announce@ietf.org</a>&gt;<o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>&gt;Cc: &lt;<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>&gt;<=
br>
&gt;Ogg: RE: [mpls] R: Re: LastCall: &nbsp; &nbsp; &nbsp;
&amp;lt;draft-ietf-mpls-tp-cc-cv-rdi-05.txt&amp;gt;<o:p></o:p></span></font=
></p>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>(Proactive &nbsp; &nbsp; &nbsp;Connectivity &nbsp;
&nbsp;Verification,Continuity Check and Remote Defect<o:p></o:p></span></fo=
nt></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>indicationfor &nbsp; MPLS &nbsp; &nbsp;Transport &nbsp; &nbsp; &nbs=
p;
Profile) to Proposed Standard<o:p></o:p></span></font></p>

<div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>&gt;<br>
&gt;Erminio,<br>
&gt;I do not think the history is relevant for this specific discussion...<=
br>
&gt;Also I find it inappropriate to give statements with no justifications<=
br>
&gt;behind.<br>
&gt;You say: &quot;the solution in this draft is useless for many MPLS-TP<b=
r>
&gt;deployments.&quot;. &nbsp;in order to seriously consider your comment, =
you
have to<br>
&gt;show why it is useless and which requirements are not satisfied.<br>
&gt;Otherwise you cannot expect anyone to refer to your point.<br>
&gt;Best regards,<br>
&gt;Nurit<br>
&gt;<br>
&gt;P.s. did you mean that the document is useless to available non-standar=
d<br>
&gt;deployments, e.g. T-MPLS?<br>
&gt;<br>
&gt;<br>
<br>
<o:p></o:p></span></font></p>

</div>

<div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'>_______________________________________________<br>
mpls mailing list<br>
<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/mpls</a><o:p></o:p></span></font></p>

</div>

</div>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>


<DIV>
This e-mail message (including attachments, if any) is intended for the use=
 of the individual or the entity to whom it is addressed and may contain in=
formation that is privileged, proprietary, confidential and exempt from dis=
closure. If you are not the intended recipient, you are notified that any d=
issemination, distribution or copying of this communication is strictly pro=
hibited. If you have received this communication in error, please notify th=
e sender and delete this E-mail message immediately.<BR>
</DIV></body>

</html>

------_=_NextPart_001_01CC41D6.083C424B--

From mcr@sandelman.ca  Thu Jul 14 06:00:52 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 B19D121F85A3 for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 06:00:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.273
X-Spam-Level: 
X-Spam-Status: No, score=-2.273 tagged_above=-999 required=5 tests=[AWL=1.681,  BAYES_00=-2.599, GB_I_LETTER=-2, 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 7FT+J+XaURcG for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 06:00:51 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id C7E9021F8589 for <ietf@ietf.org>; Thu, 14 Jul 2011 06:00:51 -0700 (PDT)
Received: from marajade.sandelman.ca (unknown [132.213.238.4]) by relay.sandelman.ca (Postfix) with ESMTPS id D001B34064; Thu, 14 Jul 2011 09:00:36 -0400 (EDT)
Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 4093598AC2; Thu, 14 Jul 2011 09:00:56 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Marc Petit-Huguenin <petithug@acm.org>
Subject: Re: Confidentiality notices on email messages
In-Reply-To: <4E1E20DD.9040103@acm.org>
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <29987.1310565058@marajade.sandelman.ca> <4E1DCA13.9030301@acm.org> <04AE56F0C4CE8168D1B38D59@PST.JCK.COM> <4E1E20DD.9040103@acm.org>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Thu, 14 Jul 2011 09:00:56 -0400
Message-ID: <5265.1310648456@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
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, 14 Jul 2011 13:00:52 -0000

>>>>> "Marc" == Marc Petit-Huguenin <petithug@acm.org> writes:
    Marc> No, I was serious.  I think that the best response to this
    Marc> kind of stuff is to do what they ask to the letter.  If we can
    Marc> convince the senders that annotating their notice with an
    Marc> header will permit us to obey their request, everybody wins.

+1


From dhc2@dcrocker.net  Thu Jul 14 06:24:54 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 D605621F899D for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 06:24:54 -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 TNwIUBmnXi6s for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 06:24:50 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id BC9AD21F899F for <ietf@ietf.org>; Thu, 14 Jul 2011 06:24:50 -0700 (PDT)
Received: from [192.168.42.123] (mdb2836d0.tmodns.net [208.54.40.219]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p6EDOd2e032401 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Thu, 14 Jul 2011 06:24:46 -0700
Message-ID: <4E1EEE0F.7090209@dcrocker.net>
Date: Thu, 14 Jul 2011 06:24:31 -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: Jorge Contreras <cntreras@gmail.com>
Subject: Re: Confidentiality notices on email messages
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <CAP0PwYYmLxPSoPvUqYOO_y=Hdn9vBSTRC5ax4wnjzE1SD1+aLg@mail.gmail.com>
In-Reply-To: <CAP0PwYYmLxPSoPvUqYOO_y=Hdn9vBSTRC5ax4wnjzE1SD1+aLg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 14 Jul 2011 06:24:47 -0700 (PDT)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jul 2011 13:24:55 -0000

On 7/12/2011 2:36 PM, Jorge Contreras wrote:
> You may want to refer to Section 5.2 of RFC 5378, which addresses this issue:
>
> "Each Contributor agrees that any statement in a Contribution, whether generated
> automatically or otherwise, that states or implies that the Contribution is
> confidential or subject to any privilege, can be disregarded for all purposes,
> and will be of no force or effect."


Jorge,

It's excellent that the issue was covered in the RFC.

My question is how the contents of that RFC can be binding on random IETF 
participants?

I doubt many folk even know about the item, even if they know about the RFC and 
I don't see how they have agreed to those terms.

Has the force of this been tested?  That is, when there is a conflict between 
the conditions imposed by one of these email attachments and the terms in RFC 
5378, is there equivalent legal precedent for the RFC to win?

Thanks.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From mcr@sandelman.ca  Thu Jul 14 06:34:31 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 45F3921F85A3 for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 06:34:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.514
X-Spam-Level: 
X-Spam-Status: No, score=-1.514 tagged_above=-999 required=5 tests=[AWL=0.441,  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 Ci4arCM4APtP for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 06:34:26 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id A9D2B21F86A3 for <ietf@ietf.org>; Thu, 14 Jul 2011 06:34:26 -0700 (PDT)
Received: from marajade.sandelman.ca (unknown [132.213.238.4]) by relay.sandelman.ca (Postfix) with ESMTPS id CED21340C7 for <ietf@ietf.org>; Thu, 14 Jul 2011 09:34:14 -0400 (EDT)
Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 6DAF598AC2 for <ietf@ietf.org>; Thu, 14 Jul 2011 09:34:34 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: IETF discussion list <ietf@ietf.org>
Subject: Re: Confidentiality notices on email messages
In-Reply-To: <4E1EEE0F.7090209@dcrocker.net>
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <CAP0PwYYmLxPSoPvUqYOO_y=Hdn9vBSTRC5ax4wnjzE1SD1+aLg@mail.gmail.com> <4E1EEE0F.7090209@dcrocker.net>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Thu, 14 Jul 2011 09:34:34 -0400
Message-ID: <10119.1310650474@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: Thu, 14 Jul 2011 13:34:31 -0000

>>>>> "Dave" == Dave CROCKER <dhc2@dcrocker.net> writes:
    >> You may want to refer to Section 5.2 of RFC 5378, which addresses
    >> this issue:
    >> 
    >> "Each Contributor agrees that any statement in a Contribution,
    >> whether generated automatically or otherwise, that states or
    >> implies that the Contribution is confidential or subject to any
    >> privilege, can be disregarded for all purposes, and will be of no
    >> force or effect."

    Dave> It's excellent that the issue was covered in the RFC.

    Dave> My question is how the contents of that RFC can be binding on
    Dave> random IETF participants?

It can't, except that they agree to the terms when they sign up at the
web server.   If the IETF deleted posts that were marked confidential
then the IETF would be simply enforcing this.

-- 
]       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 hextic@gmail.com  Thu Jul 14 07:01:08 2011
Return-Path: <hextic@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EF3221F86A7 for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 07:01:08 -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 IUURe6WLknG9 for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 07:01:08 -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 DD89221F86A6 for <ietf@ietf.org>; Thu, 14 Jul 2011 07:01:07 -0700 (PDT)
Received: by gyd5 with SMTP id 5so129238gyd.31 for <ietf@ietf.org>; Thu, 14 Jul 2011 07:01:07 -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=PI03dNB1vhSk3GB+iiejX7qlYJmKsi6OzjMqnI/dr8E=; b=M91vvwpHOmXtQq6D2lDHSlRNxsdBajYKQKBQMPMYV94hccn1MfRnAzV/CnII4Qc1Qa Gla1m7PVAxTGc92oBQSajgXYVRYh6Y1ss8CiKNuryxHZezL4rbHdQFYUxtQ4rQDqQJmJ KxhBxnPc9rJkJbfrfzvplNFYssuKnrO3a1VgM=
MIME-Version: 1.0
Received: by 10.142.55.2 with SMTP id d2mr1032431wfa.276.1310652066577; Thu, 14 Jul 2011 07:01:06 -0700 (PDT)
Received: by 10.142.203.9 with HTTP; Thu, 14 Jul 2011 07:01:06 -0700 (PDT)
In-Reply-To: <10119.1310650474@marajade.sandelman.ca>
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <CAP0PwYYmLxPSoPvUqYOO_y=Hdn9vBSTRC5ax4wnjzE1SD1+aLg@mail.gmail.com> <4E1EEE0F.7090209@dcrocker.net> <10119.1310650474@marajade.sandelman.ca>
Date: Thu, 14 Jul 2011 10:01:06 -0400
Message-ID: <CAC848Nt5CthRQ+nKZvj4Akj36eKPO4EfmuJHms2pJP+RTNb0kQ@mail.gmail.com>
Subject: Re: Confidentiality notices on email messages
From: Will McAfee <hextic@gmail.com>
To: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=0016368e22afda3ba104a807f656
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jul 2011 14:01:08 -0000

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

While these notices have very little to no legal weight whatsoever, I firmly
believe that allowing their presence on our mailing list invites frivolous
lawsuits whose purpose is to cost the IETF money in the case that an
individual does not like what we are doing.  One does not need to look
particularly hard to find examples of ridiculous cases the plaintiff would
never win where the defendant chose to simply buy the privilege of making it
go away without taking on the costs and effort of actually fighting it in
court, no matter how certain the victory.

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

While these notices have very little to no legal weight whatsoever, I firml=
y believe that allowing their presence on our mailing list invites frivolou=
s lawsuits whose purpose is to cost the IETF money in the case that an indi=
vidual does not like what we are doing.=A0 One does not need to look partic=
ularly hard to find examples of ridiculous cases the plaintiff would never =
win where the defendant chose to simply buy the privilege of making it go a=
way without taking on the costs and effort of actually fighting it in court=
, no matter how certain the victory.<br>

--0016368e22afda3ba104a807f656--

From len.holgate@gmail.com  Wed Jul 13 11:36:15 2011
Return-Path: <len.holgate@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B76C722801E; Wed, 13 Jul 2011 11:36:15 -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 vSZVWkfWLknk; Wed, 13 Jul 2011 11:36:11 -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 DD7FA228017; Wed, 13 Jul 2011 11:36:07 -0700 (PDT)
Received: by wyj26 with SMTP id 26so358241wyj.31 for <multiple recipients>; Wed, 13 Jul 2011 11:36:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:cc:references:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:in-reply-to :thread-index:x-mimeole; bh=fBY+uDDFM/RE1yohLQP6nCAuEbVdUmKrFYJvN7gndrg=; b=inzVzIQ9Jn4OqY8ig0Qr8ty1rjrqmN8O+oD4sva5qrt7iJljL+qaLeKkjlMOPMEdV9 sIS3KObx+RZOBGq46/NwA2a6ugCMVRmeDbOFTc0PD7CYk9RC3659Aaetli4FpGFS9CdF ScObPFOeUxXR7QQUe7ul2If6QPMxr/D9fNgJo=
Received: by 10.216.150.150 with SMTP id z22mr5470551wej.32.1310582165518; Wed, 13 Jul 2011 11:36:05 -0700 (PDT)
Received: from Venus (cpc7-glfd6-2-0-cust20.6-2.cable.virginmedia.com [86.27.227.21]) by mx.google.com with ESMTPS id n17sm6885982wed.16.2011.07.13.11.36.03 (version=SSLv3 cipher=OTHER); Wed, 13 Jul 2011 11:36:04 -0700 (PDT)
From: "Len Holgate" <len.holgate@gmail.com>
To: "'Francis Brosnan Blazquez'" <francis@aspl.es>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <4E1BD054.7010103@gmail.com> <1310480036.26452.329.camel@vulcan.aspl.local> <1bc701cc4135$efbf8540$0a00a8c0@Venus> <1310567252.26452.1396.camel@vulcan.aspl.local>
Subject: RE: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard: request for max frame size
Date: Wed, 13 Jul 2011 19:35:53 -0000
Message-ID: <1cc601cc4194$153fcdd0$0a00a8c0@Venus>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <1310567252.26452.1396.camel@vulcan.aspl.local>
Thread-Index: AcxBaQZNU9OGEcHESiCXt+MvxSkd1AAKqeig
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailman-Approved-At: Thu, 14 Jul 2011 08:19:00 -0700
Cc: 'Hybi' <hybi@ietf.org>, ietf@ietf.org, draft-ietf-hybi-thewebsocketprotocol@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, 13 Jul 2011 18:36:15 -0000

Francis,

> Ok, It shouldn't be a negotiation but an indication to accommodate
> communication to each party.

Fair point.

> Ok, it is important to note the peer is limiting max frame 
> size not the
> message size which may be still infinite in practical terms (63
> bits)....and we have fragmentation support to deal with this.

I understand. I was just pointing out that in your example, if the client
instead decided to limit the size of messages that it sent then then nothing
could cause any frames to be larger than that limit when they arrived at the
server.

> 1) Protocol problems should be solved on its layer, otherwise it will
>    cause next layer (application level in this case) to need to solve
>    them. It looks reasonable not forcing people to do so.

Agree.

> 2) In general, it has lot of benefits to fragment bigger messages into
>    smaller pieces to avoid sick interactions. 

Agree.

> 3) No matter API style provided by a websocket stack (frame indication
> or stream oriented), having framing running in the background 
> where the
> sending peer and intermediaries can coalesce frames without any
> indication of the upper level will cause problems that can't be solved
> in practical terms by a receiving side. 

Agree.

Len
www.lenholgate.com


From erminio.ottone_69@libero.it  Wed Jul 13 13:26:41 2011
Return-Path: <erminio.ottone_69@libero.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 6105F11E80F1; Wed, 13 Jul 2011 13:26:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.14
X-Spam-Level: *
X-Spam-Status: No, score=1.14 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MAxwydXa3vjY; Wed, 13 Jul 2011 13:26:40 -0700 (PDT)
Received: from outrelay01.libero.it (outrelay01.libero.it [212.52.84.101]) by ietfa.amsl.com (Postfix) with ESMTP id 80D8F11E807D; Wed, 13 Jul 2011 13:26:40 -0700 (PDT)
X-CTCH-Spam: Unknown
X-CTCH-RefID: str=0001.0A0B0204.4E1DFF7B.00C8,ss=1,re=0.000,fgs=0
X-libjamoibt: 1821
Received: from wmail23 (172.31.0.48) by outrelay01.libero.it (8.5.133) (authenticated as erminio.ottone_69@libero.it) id 4DE4FF25035F586E; Wed, 13 Jul 2011 22:26:35 +0200
Message-ID: <31453662.3306881310588795478.JavaMail.defaultUser@defaultHost>
Date: Wed, 13 Jul 2011 22:26:35 +0200 (CEST)
From: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
To: <david.i.allan@ericsson.com>, "RCosta@ptinovacao.pt" <RCosta@ptinovacao.pt>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
Subject: R: RE: [mpls] R: Re: Last	Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>	(Proactive	Connectivity	Verification, Continuity Check and Remote Defect indication	for	MPLS	Transport	Profile) to Proposed Standard
MIME-Version: 1.0
Content-Type: text/plain;charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-SenderIP: 79.30.163.248
X-Mailman-Approved-At: Thu, 14 Jul 2011 08:19:00 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 20:26:41 -0000

>However this is a consequence of adapting an existing technology to a new 
application. I do not see any way around that. And the entire joint project was 
based on the premise of engineering re-use not greenfield design. That is what 
it said on the tin up front, and IMO why when the IETF started down this path 
packet transport transitioned from being a minority sport to mainstream, so it 
is a bit late to cry foul....

This is not what the IETF has committed to deliver to ITU-T and in fact slide 
44 postpones to the OAM design phase "decide whether LSP-Ping or BFD can or 
should be tweaked or not" and slide 46 reckons "many options including non IP 
BFD is an option encapsulation of Y.1731 PDU"

It seems to me after having read the draft and followed this very long thread 
that tweaking BFD is not the right approach to meet ITU-T requirements so it 
would be worth evaluating the other alternative considered viable by the JWT 
which is encapulating Y.1731 PDUs.

>----Messaggio originale----
>Da: david.i.allan@ericsson.com
>Data: 6-lug-2011 20.24
>A: "erminio.ottone_69@libero.it"<erminio.ottone_69@libero.it>, 
"RCosta@ptinovacao.pt"<RCosta@ptinovacao.pt>, "ietf@ietf.org"<ietf@ietf.org>, 
"IETF-Announce"<ietf-announce@ietf.org>
>Cc: "mpls@ietf.org"<mpls@ietf.org>
>Ogg: RE: [mpls] R: Re: Last	Call:	&lt;draft-ietf-mpls-tp-cc-cv-rdi-05.txt&gt;	
(Proactive	Connectivity	Verification,	Continuity Check and Remote Defect 
indication	for	MPLS	Transport	Profile) to Proposed Standard
>
>Hi Erminio:
>
><snipped>
>>Several service providers regarded this draft as not meeting their 
>>transport networks' needs.	
>
>E> This is a true statement: the solution in this draft is useless for many 
MPLS- TP deployments.
>
>The two statements do not necessarily follow. 
>
>What we established during discussions at the SG15 plenary in February was 
that the issue some service providers had was that the IETF BFD solution 
exceeded their requirements in that there was additional functionality they did 
not see a need for, and that they considered any additional functionality 
parasitic.
>
>However this is a consequence of adapting an existing technology to a new 
application. I do not see any way around that. And the entire joint project was 
based on the premise of engineering re-use not greenfield design. That is what 
it said on the tin up front, and IMO why when the IETF started down this path 
packet transport transitioned from being a minority sport to mainstream, so it 
is a bit late to cry foul....
>
>My 2 cents
>Dave
>

From erminio.ottone_69@libero.it  Wed Jul 13 13:27:59 2011
Return-Path: <erminio.ottone_69@libero.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 7EB7611E810F; Wed, 13 Jul 2011 13:27:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.14
X-Spam-Level: *
X-Spam-Status: No, score=1.14 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jBLbf28wfCN1; Wed, 13 Jul 2011 13:27:59 -0700 (PDT)
Received: from outrelay02.libero.it (outrelay02.libero.it [212.52.84.102]) by ietfa.amsl.com (Postfix) with ESMTP id C9EF811E8114; Wed, 13 Jul 2011 13:27:58 -0700 (PDT)
X-CTCH-Spam: Unknown
X-CTCH-RefID: str=0001.0A0B0207.4E1DFFC9.010E,ss=1,re=0.000,fgs=0
X-libjamoibt: 1821
Received: from wmail23 (172.31.0.48) by outrelay02.libero.it (8.5.133) (authenticated as erminio.ottone_69@libero.it) id 4E09A78E01913BCF; Wed, 13 Jul 2011 22:27:53 +0200
Message-ID: <27773911.3307261310588873729.JavaMail.defaultUser@defaultHost>
Date: Wed, 13 Jul 2011 22:27:53 +0200 (CEST)
From: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
To: <david.i.allan@ericsson.com>, "loa@pi.nu" <loa@pi.nu>,  Rui Costa <RCosta@ptinovacao.pt>
Subject: R: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>	(Proactive Connectivity	Verification,  Continuity Check and Remote Defect indication for	MPLS	Transport	Profile) to Proposed Standard
MIME-Version: 1.0
Content-Type: text/plain;charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-SenderIP: 79.30.163.248
X-Mailman-Approved-At: Thu, 14 Jul 2011 08:19:00 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 20:27:59 -0000

Do you mean that ITU-T comments were discussed and resolution agreed during the 
ITU-T meeting?

If this is the case, why the LS just provides the comments and not the agreed 
resolution?

Why some ITU-T comments have been then rejected?

>----Messaggio originale----
>Da: david.i.allan@ericsson.com
>Data: 6-lug-2011 19.35
>A: "erminio.ottone_69@libero.it"<erminio.ottone_69@libero.it>, "loa@pi.nu"
<loa@pi.nu>, "Rui Costa"<RCosta@ptinovacao.pt>
>Cc: "mpls@ietf.org"<mpls@ietf.org>, "ietf@ietf.org"<ietf@ietf.org>, "IETF-
Announce"<ietf-announce@ietf.org>
>Ogg: RE: [mpls] R: Re: Last Call:	&lt;draft-ietf-mpls-tp-cc-cv-rdi-05.txt&gt;	
(Proactive Connectivity	Verification, Continuity Check and Remote Defect 
indication for	MPLS	Transport	Profile) to Proposed Standard
>
>Hi Erminio:
>
>Two of the three document editors were present at SG15 plenary in February 
where the comments originated. The revised meeting schedule resulted in a day 
spent going through the document with the editors. IMO there were lots of 
discussion and legitimate issues with the document identified and corrected so 
it was a useful session. The liaison of same was in many ways *after the 
fact*.
>
>Cheers
>Dave 
>



From erminio.ottone_69@libero.it  Wed Jul 13 13:32:15 2011
Return-Path: <erminio.ottone_69@libero.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 116F511E80F1; Wed, 13 Jul 2011 13:32:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.418
X-Spam-Level: *
X-Spam-Status: No, score=1.418 tagged_above=-999 required=5 tests=[AWL=-0.277,  BAYES_40=-0.185, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qp9F3f0-IuGe; Wed, 13 Jul 2011 13:32:14 -0700 (PDT)
Received: from outrelay01.libero.it (outrelay01.libero.it [212.52.84.101]) by ietfa.amsl.com (Postfix) with ESMTP id 2B13921F89BA; Wed, 13 Jul 2011 13:32:14 -0700 (PDT)
X-CTCH-Spam: Unknown
X-CTCH-RefID: str=0001.0A0B0201.4E1E00CA.000D,ss=1,re=0.000,fgs=0
X-libjamoibt: 1821
Received: from wmail23 (172.31.0.48) by outrelay01.libero.it (8.5.133) (authenticated as erminio.ottone_69@libero.it) id 4DE4FF25035F7043; Wed, 13 Jul 2011 22:32:09 +0200
Message-ID: <24102355.3308421310589129962.JavaMail.defaultUser@defaultHost>
Date: Wed, 13 Jul 2011 22:32:09 +0200 (CEST)
From: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
To: <nurit.sprecher@nsn.com>,  <RCosta@ptinovacao.pt>,  <ietf@ietf.org>,  IETF-Announce <ietf-announce@ietf.org>
Subject: R: RE: [mpls] R: Re: LastCall: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>	(Proactive	Connectivity Verification,Continuity Check and Remote Defect indicationfor	MPLS Transport	Profile) to Proposed Standard
MIME-Version: 1.0
Content-Type: text/plain;charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-SenderIP: 79.30.163.248
X-Mailman-Approved-At: Thu, 14 Jul 2011 08:19:00 -0700
Cc: mpls@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 20:32:15 -0000

The technical concern raised during the WG poll has not been resolved so the 
history definetely matters.

Quoting RFC5921:

   There are thus two objectives for MPLS-TP:

   1.  To enable MPLS to be deployed in a transport network and operated
       in a similar manner to existing transport technologies.

   2.  To enable MPLS to support packet transport services with a
       similar degree of predictability to that found in existing
       transport networks.

Based on the extensive comments provided by transport operators and ITU-T 
community, the solution in this draft is useless in case 1.

The fact that the solution in this draft is not backward compatible with 
existing IP/MPLS BFD implementations means that this solution is also uselesee 
in case 2.

Are there other undocumented use cases for MPLS-TP deployments?

>----Messaggio originale----
>Da: nurit.sprecher@nsn.com
>Data: 7-lug-2011 11.59
>A: <erminio.ottone_69@libero.it>, <RCosta@ptinovacao.pt>, <ietf@ietf.org>, 
"IETF-Announce"<ietf-announce@ietf.org>
>Cc: <mpls@ietf.org>
>Ogg: RE: [mpls] R: Re: LastCall:	&lt;draft-ietf-mpls-tp-cc-cv-rdi-05.txt&gt;	
(Proactive	Connectivity	Verification,Continuity Check and Remote Defect 
indicationfor	MPLS	Transport	Profile) to Proposed Standard
>
>Erminio,
>I do not think the history is relevant for this specific discussion... 
>Also I find it inappropriate to give statements with no justifications
>behind. 
>You say: "the solution in this draft is useless for many MPLS-TP
>deployments.".  in order to seriously consider your comment, you have to
>show why it is useless and which requirements are not satisfied.
>Otherwise you cannot expect anyone to refer to your point. 
>Best regards,
>Nurit
>
>P.s. did you mean that the document is useless to available non-standard
>deployments, e.g. T-MPLS?
> 
>



From erminio.ottone_69@libero.it  Wed Jul 13 13:38:53 2011
Return-Path: <erminio.ottone_69@libero.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 6C16111E80C3; Wed, 13 Jul 2011 13:38:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.603
X-Spam-Level: 
X-Spam-Status: No, score=0.603 tagged_above=-999 required=5 tests=[AWL=0.722,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, J_CHICKENPOX_31=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 mtiAClvlRKKW; Wed, 13 Jul 2011 13:38:49 -0700 (PDT)
Received: from outrelay03.libero.it (outrelay03.libero.it [212.52.84.103]) by ietfa.amsl.com (Postfix) with ESMTP id 640D821F8A51; Wed, 13 Jul 2011 13:38:47 -0700 (PDT)
X-CTCH-Spam: Unknown
X-CTCH-RefID: str=0001.0A0B0203.4E1E0251.00E3,ss=1,re=0.000,fgs=0
X-libjamoibt: 1821
Received: from wmail23 (172.31.0.48) by outrelay03.libero.it (8.5.133) (authenticated as erminio.ottone_69@libero.it) id 4DE4FF1D03011860; Wed, 13 Jul 2011 22:38:41 +0200
Message-ID: <947166.3310311310589521384.JavaMail.defaultUser@defaultHost>
Date: Wed, 13 Jul 2011 22:38:41 +0200 (CEST)
From: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
To: <david.i.allan@ericsson.com>, Rui Costa <RCosta@ptinovacao.pt>,  Stewart Bryant <stbryant@cisco.com>
Subject: R: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity Verification, Continuity Check and Remote Defect indication for MPLS	Transport	Profile) to Proposed Standard
MIME-Version: 1.0
Content-Type: text/plain;charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-SenderIP: 79.30.163.248
X-Mailman-Approved-At: Thu, 14 Jul 2011 08:19:00 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 20:38:53 -0000

>I would not go so far as to say "similar to 1731", there is actually a lot of 
difference under the hood. As for uni-directional BFD, that is a BFD WG problem 
at the moment.

The fact that the BFD WG has not defined a solution for unidirectional p2p and 
p2mp transport paths does not make BFD a suitable OAM protocol for MPLS-TP nor 
does resolve the technical issue that have been raised.

>----Messaggio originale----
>Da: david.i.allan@ericsson.com
>Data: 8-lug-2011 18.13
>A: "Rui Costa"<RCosta@ptinovacao.pt>, "Stewart Bryant"<stbryant@cisco.com>
>Cc: "erminio.ottone_69@libero.it"<erminio.ottone_69@libero.it>, "mpls@ietf.
org"<mpls@ietf.org>, "ietf@ietf.org"<ietf@ietf.org>, "IETF-Announce"<ietf-
announce@ietf.org>
>Ogg: RE: [mpls] Last Call: &lt;draft-ietf-mpls-tp-cc-cv-rdi-05.txt&gt;	
(Proactive	Connectivity Verification, Continuity Check and Remote Defect	
indication for MPLS	Transport	Profile) to Proposed Standard
>
>Rui:
>
>You wrote:
>
>>Reading something, keeping it on record, without effect in the draft and 
"ignoring comments" have IMHO similar outcomes. As author of the draft you are 
free to do it. These standards have a great impact
>>in our work, so i'm also free to write what i did.
>
>Numerous comments did have effect on the draft and those that didn't were 
either simply not actionable, were rhetorical or not constructive, and a few 
had to be balanced against comments coming from the MPLS & BFD WGs. I would 
translate "ingored" or "without effect" to "did not get one'e way". In the 
standards process it happens.
>
>Meanwhile as an editor of the document, I'll take the liberty of responding 
to some of the points you raise...
>
>>My technical concerns regarding this draft were expressed...
>>...in the (ITU-T -> IETF, Feb/2011) liaison regarding it (LS281, i 
believe);
>>...in operators' meetings' that took place during ITU-T's Feb/2011 plenary 
meeting;
>
>I and the WG don't really have access to private grumblings.
>
>>...in a comparison session that took place during that same ITU-T meeting.
>
>Lots of other opinions were expressed as well, and they did not all agree 
with you.
>
>>Some:
>>CC/CV
>>I don't understand the need for 2 types of packets: a single type allows CC; 
mismatching identifiers in the same CC packets allow CV.
>>Besides adding complexity, we whether always activate both or potentiate 
undetected mismerges.
>
>OK, lets walk through this.
>
>We want CV all the time so that any misconectivity can be detected, but on 
the list it was expressed that the group did not want the overhead of 
processing the source MEP TLV in every packet in order to achieve this. We 
could carry it in every packet and have the receiver simply ignore most of 
them, but then that would make the defect entry criteria compeltely random and 
the exit criteria unreliable as well, not really a good design. Hence they are 
separated using different ACH code points and the receiver is obliged to 
process every source MEP TLV it receives. I hope this is clear.
>
>>(BTW: can't understand how we propose one ACH codepoint to CC, another for 
CV, [counting other drafts, another for frame loss ...] but don't consider 
assigning 1 single ACH protocol identifier codepoint >as requested by ITU-T)
>
>Because that puts you into two protocol ID demultiplexing steps per OAM PDU 
recevied to determine the intended function. Hence COSTS MORE. That is pretty 
basic...
>
>> Uni P2P / P2MP
>> I can't see how BFD will support unidir and hence P2MP other than...
>> ...eliminating the session "state variable" (down, init, up), aiming just 
the state variables we really need, bringing us to something similar to 1731, 
eventually with other bits on the wire or...
>> ...using IP to create the reverse way, which we cannot assume per 
requirements;
>> Will we create a complete different tool for that?
>> (BFD's B="bidirectional")
>
>I would not go so far as to say "similar to 1731", there is actually a lot of 
difference under the hood. As for uni-directional BFD, that is a BFD WG problem 
at the moment.
>
>> Provisioning list
>> This is an MPLS profile/subset (and i heard) achievable through a 
particular configuration. So, i expect each draft-ietf-mpls-TP-* to focus on 
that profile/configuration. However, i keep seeing
>> references f.i. to IP encapsulations unexpected under TP's OAM.
>> I don't thus understand what the aim is: do we expect this in TP, are we 
talking about MPLS in general?... The TP profile is never quite delimited.
>> Does chapter 4 contain ALL the configurable parameters list agreed to 
provide in the comparison session?
>
>It should. As for encapsulations, unless TP is in a complete island not 
connected to anything (which as a network is rather useless) it will be 
expected to interoperate with the rest of the MPLS architecture, and the stated 
intention of tool development was that what resulted was applicable to the 
broader MPLS architecture. Which means backwards compatiblity and procedures 
for interoperation.
>
>> Backwards compatibility
>> This was the main argument risen to ground MPLS-TP OAM on BFD. It's not a 
better argument than grounding MPLS-TP OAM on 1731 due to its ETH deployment 
plus coherence with SDH, OTN, as defended by ITU-T.
>> For reasons like the above, however, MPLS-TP BFD won't be backwards 
compatible with previous BFD (even considering just CC/CV). They don't even 
share the same codepoint.
>
>The issue is not code point, which is the trivial part. It is reuse of the 
majority of the implementation. Again, pretty basic.
>
>>Simplicity
>>Whether we look to PDH, SDH, OTN or ETH, ITU-T's approach to CC is simpler: 
in each flow, a standard defined nr of constant heartbeat signals (with 
standard constant or provisioned period - no
>>auto/negotiated -) means OK. A standard defined number of misses means lost 
Rx connection. An RDI, the only articulation between Rx and Tx flows, 
meaningful in bidirectional applications, allows each
>>pear to identify Tx problems.
>>This OAM simplicity is the key for reliable fail finger pointing, 
performance reports and protection. Also to allow scaling, more implementation 
opportunities/manufacturers, which is valuable for
>>operators.
>
>Well IMO there was not a lot of interest in T-MPLS until the IETF was going 
to re-define it and make it compatible with IP/MPLS. So there was an industry 
wide "design intent" implied here.
>
>> IMHO, between your MPLS-TP view and MPLS/IP, it becomes more and more 
difficult to tell which is which.
>
>That is because MPLS-TP is not a new techology, it is an addition to the 
entire MPLS protocol suite.
>
>Hope this helps
>D
>
>
>
>
>
>
>
>
>
>-----Original Message-----
>From: David Allan I [mailto:david.i.allan@ericsson.com]
>Sent: quarta-feira, 6 de Julho de 2011 19:25
>To: erminio.ottone_69@libero.it; Rui Costa; ietf@ietf.org; IETF-Announce
>Cc: mpls@ietf.org
>Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> 
(Proactive Connectivity Verification, Continuity Check and Remote Defect 
indication for MPLS Transport Profile) to Proposed Standard
>
>Hi Erminio:
>
><snipped>
>>Several service providers regarded this draft as not meeting their
>>transport networks' needs.
>
>E> This is a true statement: the solution in this draft is useless for many 
MPLS- TP deployments.
>
>The two statements do not necessarily follow.
>
>What we established during discussions at the SG15 plenary in February was 
that the issue some service providers had was that the IETF BFD solution 
exceeded their requirements in that there was additional functionality they did 
not see a need for, and that they considered any additional functionality 
parasitic.
>
>However this is a consequence of adapting an existing technology to a new 
application. I do not see any way around that. And the entire joint project was 
based on the premise of engineering re-use not greenfield design. That is what 
it said on the tin up front, and IMO why when the IETF started down this path 
packet transport transitioned from being a minority sport to mainstream, so it 
is a bit late to cry foul....
>
>My 2 cents
>Dave
>
>
>
>
>-----Original Message-----
>From: David Allan I [mailto:david.i.allan@ericsson.com]
>Sent: quarta-feira, 6 de Julho de 2011 18:36
>To: erminio.ottone_69@libero.it; loa@pi.nu; Rui Costa
>Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
>Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> 
(Proactive Connectivity Verification, Continuity Check and Remote Defect 
indication for MPLS Transport Profile) to Proposed Standard
>
>Hi Erminio:
>
>Two of the three document editors were present at SG15 plenary in February 
where the comments originated. The revised meeting schedule resulted in a day 
spent going through the document with the editors. IMO there were lots of 
discussion and legitimate issues with the document identified and corrected so 
it was a useful session. The liaison of same was in many ways *after the 
fact*.
>
>Cheers
>Dave
>
>
>
>
>-----Original Message-----
>From: erminio.ottone_69@libero.it [mailto:erminio.ottone_69@libero.it]
>Sent: quarta-feira, 6 de Julho de 2011 18:34
>To: Rui Costa; ietf@ietf.org; IETF-Announce
>Cc: mpls@ietf.org
>Subject: R: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> 
(Proactive Connectivity Verification, Continuity Check and Remote Defect 
indication for MPLS Transport Profile) to Proposed Standard
>
>The way this draft has been developed is a bit strange.
>
>The poll for its adoption as a WG document was halted by the MPLS WG chair 
because "it is not possible to judge consensus":
>
>http://www.ietf.org/mail-archive/web/mpls/current/msg04502.html
>
>The lack of consensus was motivated by serious technical concerns raised by 
several transport experts during the poll.
>
>Nevertheless the MPLS WG chair decided to adopt the draft as a WG document:
>
>http://www.ietf.org/mail-archive/web/mpls/current/msg04512.html
>
>After several WG revisions and WG LCs, the technical issues have not been 
resolved.
>
>>Several service providers regarded this draft as not meeting their
>>transport
>networks' needs.
>
>This is a true statement: the solution in this draft is useless for many 
MPLS- TP deployments.
>
>
>-----Original Message-----
>From: erminio.ottone_69@libero.it [mailto:erminio.ottone_69@libero.it]
>Sent: quarta-feira, 6 de Julho de 2011 18:26
>To: loa@pi.nu; Rui Costa
>Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
>Subject: R: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> 
(Proactive Connectivity Verification, Continuity Check and Remote Defect 
indication for MPLS Transport Profile) to Proposed Standard
>
>>  Version -04 of the document was published June 28th.
>>
>>  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
>> June 29th.
>>
>
>So when the WG LC to confirm the LC comment resolution has been launched?
>
>The proto write-up says:
>
>            It has also passed a working roup call to verify that LC comments 
were correctly with minor comments.
>
>It also says:
>
>            The comments has been
>            carefully discussed between the authors and people making the 
comments and
>            has been resolved.
>
>But it seems that some comments have not been discussed with the authors of 
the comments. When ITU-T Q10/15 has been involved in discussing its comments?
>
>
>
>
>-----Original Message-----
>From: Loa Andersson [mailto:loa@pi.nu]
>Sent: quarta-feira, 6 de Julho de 2011 16:44
>To: Rui Costa
>Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
>Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> 
(Proactive Connectivity Verification, Continuity Check and Remote Defect 
indication for MPLS Transport Profile) to Proposed Standard
>
>All,
>
>Since someone has commented about the process used for resolving
>questions on
>draft-ietf-mpls-tp-cc-cv-rdi I am supplying some details below.
>
>The history of draft-ietf-mpls-tp-cc-cv-rdi working group review
>process is:
>
>On February 3rd 2011 the working group last call was issued
>on version -03
>
>      This was copied to the the Ad Hoc Team List
>      and liaised to SG15 also on February 3rd
>
>      This working group last call ended om Feb 28
>
>
>      On Feb 28 we also received a liaison with comments from SG15
>
>
>The authors compiled a list of all comments received  as part the MPLS
>working group last call; these  comments - and the intended resolution -
>is included in the meeting minutes from the Prague meeting:
>
>
>      http://www.ietf.org/proceedings/80/slides/mpls-9.pdf
>
>
>  During the IETF meeting in Prague, we agreed with the BFD working
>  group to do a separate working group last callfor the BFD working
>  group
>
>The (BFD) working group last call was started on March 30th and ran
>for 13 days. The last call ended on April 11th.
>
>  The authors have since worked hard to resolve comments, some
>  issue has been brought to the working group mailing list for
>  resolution.
>
>  Version -04 of the document was published June 28th.
>
>  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
>  June 29th.
>
>  The AD review resulted in a "New ID needed" due to mostly editorial
>  comments. Version -05 was published on June 29 and the IETF last call
>  started as soon as the new ID was avaialbe.
>
>  The current list of Last Call Comments resoltion is also avaiable at:
>  http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
>
>  The list of issues that the authors kept very carefully, shows without
>doubt
>  that no comments been ignored.
>
>  Loa
>  mpls wg document shepherd
>
>
>
>
>
>
>
>-----Original Message-----
>From: David Allan I [mailto:david.i.allan@ericsson.com]
>Sent: quarta-feira, 6 de Julho de 2011 14:58
>To: Rui Costa; ietf@ietf.org; IETF-Announce
>Cc: mpls@ietf.org
>Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> 
(Proactive Connectivity Verification, Continuity Check and Remote Defect 
indication for MPLS Transport Profile) to Proposed Standard
>
>Hi Rui:
>
>The comments were not ignored, the resolution of the Q10 comments as well as 
those collected from the MPLS WG was presented at the last IETF. My spreadsheet 
from which that report was generated and has been augmented to include the BFD 
WG comments is available at http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.
xls
>
>So you know...
>Dave
>
>
>-----Original Message-----
>From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Rui 
Costa
>Sent: segunda-feira, 4 de Julho de 2011 23:03
>To: ietf@ietf.org; IETF-Announce
>Cc: mpls@ietf.org
>Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> 
(Proactive Connectivity Verification, Continuity Check and Remote Defect 
indication for MPLS Transport Profile) to Proposed Standard
>
>IMHO and for the record:
>
>ITU-T comments regarding this draft haven't been discussed with ITU-T but 
were simply ignored. No LS describing these comments' resolution was sent.
>
>Several service providers regarded this draft as not meeting their transport 
networks' needs.
>
>[The v03 draft was published in Feb and went to WG LC.
>The v04 draft addressing WG LC comments was published on the 28th June (same 
date as the proto write-up).
>When was the WG LC launched, to verify LC comments resolution?]
>
>Regards,
>Rui
>
>
>-----Original Message-----
>From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of The 
IESG
>Sent: quinta-feira, 30 de Junho de 2011 14:47
>To: IETF-Announce
>Cc: mpls@ietf.org
>Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive 
Connectivity Verification, Continuity Check and Remote Defect indication for 
MPLS Transport Profile) to Proposed Standard
>
>
>The IESG has received a request from the Multiprotocol Label Switching WG
>(mpls) to consider the following document:
>- 'Proactive Connectivity Verification, Continuity Check and Remote
>   Defect indication for MPLS Transport Profile'
>  <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally, comments may be
>sent to iesg@ietf.org instead. In either case, please retain the
>beginning of the Subject line to allow automated sorting.
>
>Abstract
>
>   Continuity Check, Proactive Connectivity Verification and Remote
>   Defect Indication functionalities are required for MPLS-TP OAM.
>
>   Continuity Check monitors the integrity of the continuity of the
>   label switched path for any loss of continuity defect. Connectivity
>   verification monitors the integrity of the routing of the label
>   switched path between sink and source for any connectivity issues.
>   Remote defect indication enables an End Point to report, to its
>   associated End Point, a fault or defect condition that it detects on
>   a pseudo wire, label switched path or Section.
>
>   This document specifies methods for proactive continuity check,
>   continuity verification, and remote defect indication for MPLS-TP
>   label switched paths, pseudo wires and Sections using Bidirectional
>   Forwarding Detection.
>
>
>The file can be obtained via
>http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>
>IESG discussion can be tracked via
>http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>
>
>No IPR declarations have been submitted directly on this I-D.
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls
>
>
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf
>



From erminio.ottone_69@libero.it  Wed Jul 13 13:47:38 2011
Return-Path: <erminio.ottone_69@libero.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 60DE921F8AED; Wed, 13 Jul 2011 13:47:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.422
X-Spam-Level: 
X-Spam-Status: No, score=0.422 tagged_above=-999 required=5 tests=[AWL=0.541,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, J_CHICKENPOX_31=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 O1qca+PdiI8R; Wed, 13 Jul 2011 13:47:37 -0700 (PDT)
Received: from outrelay01.libero.it (outrelay01.libero.it [212.52.84.101]) by ietfa.amsl.com (Postfix) with ESMTP id 2673521F8AEA; Wed, 13 Jul 2011 13:47:37 -0700 (PDT)
X-CTCH-Spam: Unknown
X-CTCH-RefID: str=0001.0A0B0207.4E1E0463.0071,ss=1,re=0.000,fgs=0
X-libjamoibt: 1821
Received: from wmail23 (172.31.0.48) by outrelay01.libero.it (8.5.133) (authenticated as erminio.ottone_69@libero.it) id 4DE4FF25035FB03E; Wed, 13 Jul 2011 22:47:31 +0200
Message-ID: <6036596.3312721310590051192.JavaMail.defaultUser@defaultHost>
Date: Wed, 13 Jul 2011 22:47:31 +0200 (CEST)
From: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
To: <david.i.allan@ericsson.com>, Rui Costa <RCosta@ptinovacao.pt>,  Stewart Bryant <stbryant@cisco.com>
Subject: R: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity Verification, Continuity Check and Remote Defect indication for MPLS	Transport	Profile) to Proposed Standard
MIME-Version: 1.0
Content-Type: text/plain;charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-SenderIP: 79.30.163.248
X-Mailman-Approved-At: Thu, 14 Jul 2011 08:19:00 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 20:47:38 -0000

>> Backwards compatibility
>> This was the main argument risen to ground MPLS-TP OAM on BFD. It's not a 
better argument than grounding MPLS-TP OAM on 1731 due to its ETH deployment 
plus coherence with SDH, OTN, as defended by ITU-T.
>> For reasons like the above, however, MPLS-TP BFD won't be backwards 
compatible with previous BFD (even considering just CC/CV). They don't even 
share the same codepoint.
>
>The issue is not code point, which is the trivial part. It is reuse of the 
majority of the implementation. Again, pretty basic.
>

I disagree. From a backward compatibility perspecting the codepoint is very 
relevant. An existing implementation does not reckon the new encapsulation: the 
only way to deploy this solution in a backward compatible manner is by 
upgrading all the IP/MPLS nodes that have been deployed up to so far.

I think that the "reuse of the majority of the implementation" is actually the 
issue. Those implementations do not have the capabilities required to be 
deployed in a transport network. 

Developing a non-transport capable standard will not make these boxes 
transport capable but it would just make the standard useless for a transport 
environment.

>----Messaggio originale----
>Da: david.i.allan@ericsson.com
>Data: 8-lug-2011 18.13
>A: "Rui Costa"<RCosta@ptinovacao.pt>, "Stewart Bryant"<stbryant@cisco.com>
>Cc: "erminio.ottone_69@libero.it"<erminio.ottone_69@libero.it>, "mpls@ietf.
org"<mpls@ietf.org>, "ietf@ietf.org"<ietf@ietf.org>, "IETF-Announce"<ietf-
announce@ietf.org>
>Ogg: RE: [mpls] Last Call: &lt;draft-ietf-mpls-tp-cc-cv-rdi-05.txt&gt;	
(Proactive	Connectivity Verification, Continuity Check and Remote Defect	
indication for MPLS	Transport	Profile) to Proposed Standard
>
>Rui:
>
>You wrote:
>
>>Reading something, keeping it on record, without effect in the draft and 
"ignoring comments" have IMHO similar outcomes. As author of the draft you are 
free to do it. These standards have a great impact
>>in our work, so i'm also free to write what i did.
>
>Numerous comments did have effect on the draft and those that didn't were 
either simply not actionable, were rhetorical or not constructive, and a few 
had to be balanced against comments coming from the MPLS & BFD WGs. I would 
translate "ingored" or "without effect" to "did not get one'e way". In the 
standards process it happens.
>
>Meanwhile as an editor of the document, I'll take the liberty of responding 
to some of the points you raise...
>
>>My technical concerns regarding this draft were expressed...
>>...in the (ITU-T -> IETF, Feb/2011) liaison regarding it (LS281, i 
believe);
>>...in operators' meetings' that took place during ITU-T's Feb/2011 plenary 
meeting;
>
>I and the WG don't really have access to private grumblings.
>
>>...in a comparison session that took place during that same ITU-T meeting.
>
>Lots of other opinions were expressed as well, and they did not all agree 
with you.
>
>>Some:
>>CC/CV
>>I don't understand the need for 2 types of packets: a single type allows CC; 
mismatching identifiers in the same CC packets allow CV.
>>Besides adding complexity, we whether always activate both or potentiate 
undetected mismerges.
>
>OK, lets walk through this.
>
>We want CV all the time so that any misconectivity can be detected, but on 
the list it was expressed that the group did not want the overhead of 
processing the source MEP TLV in every packet in order to achieve this. We 
could carry it in every packet and have the receiver simply ignore most of 
them, but then that would make the defect entry criteria compeltely random and 
the exit criteria unreliable as well, not really a good design. Hence they are 
separated using different ACH code points and the receiver is obliged to 
process every source MEP TLV it receives. I hope this is clear.
>
>>(BTW: can't understand how we propose one ACH codepoint to CC, another for 
CV, [counting other drafts, another for frame loss ...] but don't consider 
assigning 1 single ACH protocol identifier codepoint >as requested by ITU-T)
>
>Because that puts you into two protocol ID demultiplexing steps per OAM PDU 
recevied to determine the intended function. Hence COSTS MORE. That is pretty 
basic...
>
>> Uni P2P / P2MP
>> I can't see how BFD will support unidir and hence P2MP other than...
>> ...eliminating the session "state variable" (down, init, up), aiming just 
the state variables we really need, bringing us to something similar to 1731, 
eventually with other bits on the wire or...
>> ...using IP to create the reverse way, which we cannot assume per 
requirements;
>> Will we create a complete different tool for that?
>> (BFD's B="bidirectional")
>
>I would not go so far as to say "similar to 1731", there is actually a lot of 
difference under the hood. As for uni-directional BFD, that is a BFD WG problem 
at the moment.
>
>> Provisioning list
>> This is an MPLS profile/subset (and i heard) achievable through a 
particular configuration. So, i expect each draft-ietf-mpls-TP-* to focus on 
that profile/configuration. However, i keep seeing
>> references f.i. to IP encapsulations unexpected under TP's OAM.
>> I don't thus understand what the aim is: do we expect this in TP, are we 
talking about MPLS in general?... The TP profile is never quite delimited.
>> Does chapter 4 contain ALL the configurable parameters list agreed to 
provide in the comparison session?
>
>It should. As for encapsulations, unless TP is in a complete island not 
connected to anything (which as a network is rather useless) it will be 
expected to interoperate with the rest of the MPLS architecture, and the stated 
intention of tool development was that what resulted was applicable to the 
broader MPLS architecture. Which means backwards compatiblity and procedures 
for interoperation.
>
>> Backwards compatibility
>> This was the main argument risen to ground MPLS-TP OAM on BFD. It's not a 
better argument than grounding MPLS-TP OAM on 1731 due to its ETH deployment 
plus coherence with SDH, OTN, as defended by ITU-T.
>> For reasons like the above, however, MPLS-TP BFD won't be backwards 
compatible with previous BFD (even considering just CC/CV). They don't even 
share the same codepoint.
>
>The issue is not code point, which is the trivial part. It is reuse of the 
majority of the implementation. Again, pretty basic.
>
>>Simplicity
>>Whether we look to PDH, SDH, OTN or ETH, ITU-T's approach to CC is simpler: 
in each flow, a standard defined nr of constant heartbeat signals (with 
standard constant or provisioned period - no
>>auto/negotiated -) means OK. A standard defined number of misses means lost 
Rx connection. An RDI, the only articulation between Rx and Tx flows, 
meaningful in bidirectional applications, allows each
>>pear to identify Tx problems.
>>This OAM simplicity is the key for reliable fail finger pointing, 
performance reports and protection. Also to allow scaling, more implementation 
opportunities/manufacturers, which is valuable for
>>operators.
>
>Well IMO there was not a lot of interest in T-MPLS until the IETF was going 
to re-define it and make it compatible with IP/MPLS. So there was an industry 
wide "design intent" implied here.
>
>> IMHO, between your MPLS-TP view and MPLS/IP, it becomes more and more 
difficult to tell which is which.
>
>That is because MPLS-TP is not a new techology, it is an addition to the 
entire MPLS protocol suite.
>
>Hope this helps
>D
>
>
>
>
>
>

From erminio.ottone_69@libero.it  Wed Jul 13 13:51:46 2011
Return-Path: <erminio.ottone_69@libero.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 A2D4021F8B00; Wed, 13 Jul 2011 13:51:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.014
X-Spam-Level: 
X-Spam-Status: No, score=0.014 tagged_above=-999 required=5 tests=[AWL=0.733,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tJUGJ+j1iEQt; Wed, 13 Jul 2011 13:51:42 -0700 (PDT)
Received: from outrelay02.libero.it (outrelay02.libero.it [212.52.84.102]) by ietfa.amsl.com (Postfix) with ESMTP id 60C5321F876B; Wed, 13 Jul 2011 13:51:34 -0700 (PDT)
X-CTCH-Spam: Unknown
X-CTCH-RefID: str=0001.0A0B0207.4E1E0554.011D,ss=1,re=0.000,fgs=0
X-libjamoibt: 1821
Received: from wmail23 (172.31.0.48) by outrelay02.libero.it (8.5.133) (authenticated as erminio.ottone_69@libero.it) id 4E09A78E01919EB2; Wed, 13 Jul 2011 22:51:32 +0200
Message-ID: <3763381.3313701310590292624.JavaMail.defaultUser@defaultHost>
Date: Wed, 13 Jul 2011 22:51:32 +0200 (CEST)
From: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
To: <alessandro.dalessandro@telecomitalia.it>,  IETF-Announce <ietf-announce@ietf.org>
Subject: R: [mpls] R: Last Call:	<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive Connectivity	Verification, Continuity Check and Remote Defect indication for	MPLS	Transport	Profile) to Proposed Standard
MIME-Version: 1.0
Content-Type: text/plain;charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-SenderIP: 79.30.163.248
X-Mailman-Approved-At: Thu, 14 Jul 2011 08:19:00 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 20:51:46 -0000

It looks like this draft does not define a "single" solution for CC, CV and=
 RDI=20
function

>----Messaggio originale----
>Da: alessandro.dalessandro@telecomitalia.it
>Data: 13-lug-2011 15.02
>A: "IETF-Announce"<ietf-announce@ietf.org>
>Cc: "mpls@ietf.org"<mpls@ietf.org>, "ietf@ietf.org"<ietf@ietf.org>
>Ogg: [mpls] R: Last Call:=09&lt;draft-ietf-mpls-tp-cc-cv-rdi-05.txt&gt;=09
(Proactive Connectivity=09Verification, Continuity Check and Remote Defect=
=20
indication for=09MPLS=09Transport=09Profile) to Proposed Standard
>
>Dear all,
>I regret to say I have the same concerns expressed by Rui and Erminio abou=
t=20
the procedure adopted for this document that has brought so many discussion=
s.=20
Anyway, probably because of the lack of a reasonable time (in my opinion) f=
or=20
discussions about the previous document version (-04) I have the following=
=20
comments on this version:
>
>1. it is not clear the BFD's scope
>        Sect. 1: PW, LSP, SPME
>        Sect. 1: LSP
>        Sect 3: LSP
>        Sect 3.1:LSP, PW
>        Sect 3.3: PW, LSP, SPME, Section
>        Sect 3.7: LSP
>
>2. encapsulation
>        Sect 1: supported encapsulation GAL/GACh, VCCV, UDP/IP: can be=20
expressed a preference (MUST/MAY) for Transport Profile applications for=20
interoperability issues? I would avoid single vendor networks coming from t=
oo=20
many options.
>
>3. diagnostic code 5
>        Could you clarify what is the BFD state machine behavior=20
receiving/transmitting a Diagn Code=3D5
>
>4. detection time
>        Sect 3.2: I expect it is that one defined in RFC5884 i.e. detect M=
ult=20
x greater (bfd.requiredminrxinterval, last received desired min tx interval=
).=20
What "interval" means is not clear
>
>5. session periodicity
>        Sec 3.3 Should be clarified being not defined in RFC5880
>
>6. detection of loss of continuity
>        Sect 3.3 can CV packet  sent on the wire replace CC packet (for LO=
C=20
purpose on the far end)?
>
>7. CV vs CC packets
>        Sect 3.6 Generally speaking, how should the received CV packet's=
=20
fields be managed with respect of the BFD state machine/BFD states? (beyond=
=20
what is specified in such paragraph limited to P/F and Sta).
>
>8. encoding
>        Sect 3.5: could you clarify what " A BFD session will only use one=
=20
encoding of the Source ID TLV" means?
>
>9. editorial
>        Source ID TLV, MEP source ID TLV, Source MEP TLV should be aligned
>
>10. terminology
>        Wrt sect 3.6 I would ask a clarification about the terminology whe=
re=20
I found
>        a- "A BFD session corresponds to a CC and proactive CV OAM instanc=
e"
>        b- " A BFD session is enabled when the CC and proactive CV=20
functionality is enabled"
>        c- " When the CC and proactive CV functionality is disabled ..., t=
he=20
BFD session transitions to the ADMIN DOWN State and the BFD session ends"
>                In the ADMIN DOWN state I understood I can have BFD contro=
l=20
packet exchange between the end points. Is it consistent with CC/CV=20
functionality disabled?
>11. code points
>        Code points are not specified in section 3.1 as stated
>
>12. BFD fixed rate
>        Sect 3.7 " This rate is a fixed value common for both directions o=
f=20
MEG for the lifetime of the MEG". Is this statement implying that MEG must =
be=20
destroyed to be able to change the BFD rate? Should not be limited to the B=
FD=20
session lifetime (to be clarified what it means... because moving to ADMIN =
DOWN=20
state both ends could not be enough)
>
>13. two BFD modes
>        Sect 3.7 " Two independent BFD sessions are used for independent=
=20
operation". In my opinion, this approach still remain a big limitation in B=
FD=20
usage.
>        Is it implementation specific the way the two ends distinguish=20
between the two BFD modes?
>
>14. bfd.RemoteDiscr
>        Sect 3.7 " In coordinated mode, an implementation SHOULD NOT reset=
=20
bfd.RemoteDiscr until it is exiting the DOWN state"
>        Is it a deviation from BFD as specified in RFC 5880? If it is, cou=
ld=20
you clarified the reason for that?
>
>15. bfd.RemoteDiscr
>        Sect 3.7 Could you clarify the reasons behind different treatments=
=20
for bfd.RemoteDiscr in coordinated mode and independent mode?
>
>16. overall operation
>        Sect 3.7 "Overall operation is as specified in [4] and augmented f=
or=20
MPLS in[8]"
>        Are you sure that it can be generalized in that way? Should not be=
=20
the case to specify more in details what applies and what do not apply?
>
>17. IP-based BFD
>        Sect 3.1  IP-based BFD can carry out CV functionality only if IP S=
A=20
is public
>
>18. CV during transient states
>        Sect 3.2 for clarification: at start-up, CC are sent one per secon=
d.=20
CV are sent in addition to CC (so we have two BFD packets per second)?
>
>19. misconnections
>        Sect 3.7.3 sect 3.7.3 states a misconnection bring BFD session to=
=20
DOWN whilst it is not clear if sect 3.7.5 state that misconnection do not=
=20
impact on BFD state transition
>
>20. encapsulation modes
>        Sect 4: if I understood well, there are 4 encapusulations and mode=
s=20
for BFD: UDP/IP/LSP; CC mode in G-ACh; UPD/IP in G-ACh e CC/CV mode in G-AC=
h.
>        Do all of them satisfy transport requirements?
>        I understand they are not interoperable (as well as the two BFD mo=
de=20
for the same CC/CV in G-Ach encapsulation). Is it correct?
>
>Best regards,
>Alessandro
>
>------------------------------------------------------------------
>Telecom Italia
>Alessandro D'Alessandro
>Transport Innovation
>Via Reiss Romoli, 274 - 10148 Torino
>phone:  +39 011 228 5887
>mobile: +39 335 766 9607
>fax: +39 06 418 639 07
>
>
>-----Messaggio originale-----
>Da: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] Per conto di Loa=
=20
Andersson
>Inviato: mercoled=C3=AC 6 luglio 2011 17:44
>A: Rui Costa
>Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
>Oggetto: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>=20
(Proactive Connectivity Verification, Continuity Check and Remote Defect=20
indication for MPLS Transport Profile) to Proposed Standard
>
>All,
>
>Since someone has commented about the process used for resolving questions=
 on=20
draft-ietf-mpls-tp-cc-cv-rdi I am supplying some details below.
>
>The history of draft-ietf-mpls-tp-cc-cv-rdi working group review process i=
s:
>
>On February 3rd 2011 the working group last call was issued on version -03
>
>      This was copied to the the Ad Hoc Team List
>      and liaised to SG15 also on February 3rd
>
>      This working group last call ended om Feb 28
>
>
>      On Feb 28 we also received a liaison with comments from SG15
>
>
>The authors compiled a list of all comments received  as part the MPLS=20
working group last call; these  comments - and the intended resolution - is=
=20
included in the meeting minutes from the Prague meeting:
>
>
>      http://www.ietf.org/proceedings/80/slides/mpls-9.pdf
>
>
>  During the IETF meeting in Prague, we agreed with the BFD working
>  group to do a separate working group last callfor the BFD working
>  group
>
>The (BFD) working group last call was started on March 30th and ran for 13=
=20
days. The last call ended on April 11th.
>
>  The authors have since worked hard to resolve comments, some
>  issue has been brought to the working group mailing list for
>  resolution.
>
>  Version -04 of the document was published June 28th.
>
>  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
>  June 29th.
>
>  The AD review resulted in a "New ID needed" due to mostly editorial
>  comments. Version -05 was published on June 29 and the IETF last call
>  started as soon as the new ID was avaialbe.
>
>  The current list of Last Call Comments resoltion is also avaiable at:
>  http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
>
>  The list of issues that the authors kept very carefully, shows without=
=20
doubt
>  that no comments been ignored.
>
>  Loa
>  mpls wg document shepherd
>
>On 2011-07-05 00:02, Rui Costa wrote:
>> IMHO and for the record:
>>
>> ITU-T comments regarding this draft haven't been discussed with ITU-T bu=
t=20
were simply ignored. No LS describing these comments' resolution was sent.
>>
>> Several service providers regarded this draft as not meeting their=20
transport networks' needs.
>>
>> [The v03 draft was published in Feb and went to WG LC.
>> The v04 draft addressing WG LC comments was published on the 28th June=
=20
(same date as the proto write-up).
>> When was the WG LC launched, to verify LC comments resolution?]
>>
>> Regards,
>> Rui
>>
>>
>> -----Original Message-----
>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
>> Of The IESG
>> Sent: quinta-feira, 30 de Junho de 2011 14:47
>> To: IETF-Announce
>> Cc: mpls@ietf.org
>> Subject: [mpls] Last Call:<draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
>> (Proactive Connectivity Verification, Continuity Check and Remote
>> Defect indication for MPLS Transport Profile) to Proposed Standard
>>
>>
>> The IESG has received a request from the Multiprotocol Label Switching
>> WG
>> (mpls) to consider the following document:
>> - 'Proactive Connectivity Verification, Continuity Check and Remote
>>     Defect indication for MPLS Transport Profile'
>>    <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally, comments may
>> be sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>     Continuity Check, Proactive Connectivity Verification and Remote
>>     Defect Indication functionalities are required for MPLS-TP OAM.
>>
>>     Continuity Check monitors the integrity of the continuity of the
>>     label switched path for any loss of continuity defect. Connectivity
>>     verification monitors the integrity of the routing of the label
>>     switched path between sink and source for any connectivity issues.
>>     Remote defect indication enables an End Point to report, to its
>>     associated End Point, a fault or defect condition that it detects on
>>     a pseudo wire, label switched path or Section.
>>
>>     This document specifies methods for proactive continuity check,
>>     continuity verification, and remote defect indication for MPLS-TP
>>     label switched paths, pseudo wires and Sections using Bidirectional
>>     Forwarding Detection.
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>
>>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>
>--
>
>
>Loa Andersson                         email: loa.andersson@ericsson.com
>Sr Strategy and Standards Manager            loa@pi.nu
>Ericsson Inc                          phone: +46 10 717 52 13
>                                              +46 767 72 92 13=20
_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls
>
>Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle=20
persone indicate. La diffusione, copia o qualsiasi altra azione derivante d=
alla=20
conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbia=
te=20
ricevuto questo documento per errore siete cortesemente pregati di darne=20
immediata comunicazione al mittente e di provvedere alla sua distruzione,=
=20
Grazie.
>
>This e-mail and any attachments is confidential and may contain privileged=
=20
information intended for the addressee(s) only. Dissemination, copying,=20
printing or use by anybody else is unauthorised. If you are not the intende=
d=20
recipient, please delete this message and any attachments and advise the se=
nder=20
by return e-mail, Thanks.
>
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls
>



From wwwrun@ietfa.amsl.com  Wed Jul 13 13:59:29 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 379D511E818A; Wed, 13 Jul 2011 13:59:29 -0700 (PDT)
From: RSOC Chair <rsoc-chair@iab.org >
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: RFC Series Editor Search Announcement 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110713205929.379D511E818A@ietfa.amsl.com>
Date: Wed, 13 Jul 2011 13:59:29 -0700 (PDT)
X-Mailman-Approved-At: Thu, 14 Jul 2011 08:19:00 -0700
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: Wed, 13 Jul 2011 20:59:29 -0000

The Internet Engineering Task Force is seeking an RFC Series Editor (RSE).  The RSE has overall responsibility 
for the quality, continuity, and evolution of the Request for Comments (RFC) Series, the Internet's seminal 
technical standards and publications series.  The position has operational and policy development responsibilities.

The overall leadership and supervision of RFC Editor function is the responsibility of the RFC Series Editor. 
The RSE is a senior professional who must be skilled in leading, managing and enhancing a critical, 
multi-vendor, global information service.   

The following qualifications are desired: 

1.	Leadership and management experience.  In particular, demonstrated experience in strategic 
        planning and the management of entire operations.  Experience that can be applied to fulfill 
        the tasks and responsibilities described in RFC Editor Model (version 2) 
        <http://www.ietf.org/id/draft-iab-rfc-editor-model-v2-02.txt>.
2.	Excellent written and verbal communication skills in English and technical terminology related 
        to the Internet a must; additional languages a plus.
3.	Experience with editorial processes. 
4.	Familiar with a wide range of Internet technologies.
5.	An ability to develop a solid understanding of the IETF, its culture and RFC process.
6.	Ability to work independently, via email and teleconf, with strong time management skills.
7.	Willingness and ability to travel as required.
8.	Capable of effectively functioning in a multi-actor and matrixed environment with divided 
        authority and responsibility; ability to work with clarity and flexibility with different constituencies.
9.	Experience as an RFC author desired.

More information about the position can be found at <http://www.rfc-editor.org/rse/RSE-position.html>.

The RSE reports to the RFC Series Oversight Committee (RSOC).

Expressions of interest in the position, CV (including employment history), compensation 
requirements, and references should be sent to the RSOC search committee at rse-search@iab.org  
Applications will be kept confidential.  The application period is open until the position is filled.

Questions are to be addressed to rse-search@iab.org. 

The RSOC will interview interested parties at the IETF meeting in Quebec City that begins 
July 24, 2011.

Fred Baker
Chair
RFC Series Oversight Committee

From erminio.ottone_69@libero.it  Wed Jul 13 14:04:21 2011
Return-Path: <erminio.ottone_69@libero.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 AEC7321F8B02; Wed, 13 Jul 2011 14:04:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.108
X-Spam-Level: 
X-Spam-Status: No, score=-0.108 tagged_above=-999 required=5 tests=[AWL=0.611,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rBckENbBuHPG; Wed, 13 Jul 2011 14:04:21 -0700 (PDT)
Received: from outrelay03.libero.it (outrelay03.libero.it [212.52.84.103]) by ietfa.amsl.com (Postfix) with ESMTP id 885C821F8B00; Wed, 13 Jul 2011 14:04:20 -0700 (PDT)
X-CTCH-Spam: Unknown
X-CTCH-RefID: str=0001.0A0B020C.4E1E084E.003A,ss=1,re=0.000,fgs=0
X-libjamoibt: 1821
Received: from wmail23 (172.31.0.48) by outrelay03.libero.it (8.5.133) (authenticated as erminio.ottone_69@libero.it) id 4DE4FF1D03017E90; Wed, 13 Jul 2011 23:04:13 +0200
Message-ID: <29155895.3316791310591053994.JavaMail.defaultUser@defaultHost>
Date: Wed, 13 Jul 2011 23:04:13 +0200 (CEST)
From: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
To: <jdrake@juniper.net>,  "david.i.allan@ericsson.com" <david.i.allan@ericsson.com>,  "RCosta@ptinovacao.pt" <RCosta@ptinovacao.pt>,  "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
Subject: R: RE: [mpls] R: RE: R: Re:	Last	Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>	(Proactive	Connectivity	Verification, Continuity Check and Remote Defect	indication	for	MPLS	Transport	Profile) to Proposed Standard
MIME-Version: 1.0
Content-Type: text/plain;charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-SenderIP: 79.30.163.248
X-Mailman-Approved-At: Thu, 14 Jul 2011 08:19:00 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 21:04:21 -0000

The JWT report is aligned with my statement.

The decision at IETF75 has been taken by the MPLS WG after the JWT and has 
never been endorsed by ITU-T (Huub is NOT ITU-T and, as far as I understood, he 
later removed his name because the other editors of the OAM Analysis draft were 
not considering his input to the document).

The BFD-based solution accepted by IETF75 for pro-active CC/CV/RDI was 
completely different (and technically much superior) than the one described by 
this draft.

Accepting a solution that meets the requirements does not mean signing a blank 
cheque that whichever changes is done is acceptable regarless whether it meets 
or not the requirements.

>----Messaggio originale----
>Da: jdrake@juniper.net
>Data: 13-lug-2011 22.46
>A: "erminio.ottone_69@libero.it"<erminio.ottone_69@libero.it>, "david.i.
allan@ericsson.com"<david.i.allan@ericsson.com>, "RCosta@ptinovacao.pt"
<RCosta@ptinovacao.pt>, "ietf@ietf.org"<ietf@ietf.org>, "IETF-Announce"<ietf-
announce@ietf.org>
>Cc: "mpls@ietf.org"<mpls@ietf.org>
>Ogg: RE: [mpls] R: RE: R: Re:	Last	Call:	&lt;draft-ietf-mpls-tp-cc-cv-rdi-05.
txt&gt;	(Proactive	Connectivity	Verification,	Continuity Check and Remote 
Defect	indication	for	MPLS	Transport	Profile) to Proposed Standard
>
>Italo,
>
>The design team report (http://www.ietf.org/proceedings/75/slides/mpls-
17/mpls-17_files/frame.htm), with Huub's name as an author, details a plan for 
MPLS-TP OAM which the MPLS WG has followed to this day.  I think the report is 
compelling evidence that the claim that a packet transport network is an MPLS 
application that intrinsically requires a different OAM solution is simply a 
lame ex post facto attempt to justify the ITU's abrogation of the agreement 
with the IETF (TD07 (WP3/SG15) from December 2008 sourced by SG15):
>
>"The ITU-T accepts these recommendations and states that any extensions to 
MPLS technology will be progressed via the IETF standards process using the 
procedures defined in RFC 4929 (Change Process for Multiprotocol Label 
Switching (MPLS) and Generalized MPLS (GMPLS) Protocols and Procedures).  
Experts from the ITU-T will assist the IETF in the development of RFCs that 
describe the transport extensions by providing input to and review of the 
drafts as they are progressed via the IETF standards process.. The ITU-T will 
develop new or revised Recommendations that will allow IETF MPLS-TP to be 
integrated into the transport network including integration with the existing 
equipment, and operations infrastructure.  These Recommendations will make 
normative references to the base IETF MPLS-TP technology and will be developed 
with input from and review by experts from the IETF to ensure consistency with 
MPLS-TP...
>
>The ITU-T has accepted the proposals from the JWT and we look forward to 
continuing the cooperative development of IETF MPLS to address the needs of the 
transport network. We also believe that this resolution will fulfil the mutual 
goal of improve the functionality of the internet and transport networks and 
guaranteeing complete interoperability and architectural soundness."
>
>Thanks,
>
>John
>
>Sent from my iPhone
>
>> -----Original Message-----
>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
>> erminio.ottone_69@libero.it
>> Sent: Wednesday, July 13, 2011 1:27 PM
>> To: david.i.allan@ericsson.com; RCosta@ptinovacao.pt; ietf@ietf.org;
>> IETF-Announce
>> Cc: mpls@ietf.org
>> Subject: [mpls] R: RE: R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-
>> 05.txt> (Proactive Connectivity Verification, Continuity Check and
>> Remote Defect indication for MPLS Transport Profile) to Proposed
>> Standard
>> 
>> >However this is a consequence of adapting an existing technology to a
>> new
>> application. I do not see any way around that. And the entire joint
>> project was
>> based on the premise of engineering re-use not greenfield design. That
>> is what
>> it said on the tin up front, and IMO why when the IETF started down
>> this path
>> packet transport transitioned from being a minority sport to
>> mainstream, so it
>> is a bit late to cry foul....
>> 
>> This is not what the IETF has committed to deliver to ITU-T and in fact
>> slide
>> 44 postpones to the OAM design phase "decide whether LSP-Ping or BFD
>> can or
>> should be tweaked or not" and slide 46 reckons "many options including
>> non IP
>> BFD is an option encapsulation of Y.1731 PDU"
>> 
>> It seems to me after having read the draft and followed this very long
>> thread
>> that tweaking BFD is not the right approach to meet ITU-T requirements
>> so it
>> would be worth evaluating the other alternative considered viable by
>> the JWT
>> which is encapulating Y.1731 PDUs.
>> 
>> >----Messaggio originale----
>> >Da: david.i.allan@ericsson.com
>> >Data: 6-lug-2011 20.24
>> >A: "erminio.ottone_69@libero.it"<erminio.ottone_69@libero.it>,
>> "RCosta@ptinovacao.pt"<RCosta@ptinovacao.pt>,
>> "ietf@ietf.org"<ietf@ietf.org>,
>> "IETF-Announce"<ietf-announce@ietf.org>
>> >Cc: "mpls@ietf.org"<mpls@ietf.org>
>> >Ogg: RE: [mpls] R: Re: Last	Call:	&lt;draft-ietf-mpls-tp-cc-cv-rdi-
>> 05.txt&gt;
>> (Proactive	Connectivity	Verification,	Continuity Check and
>> Remote Defect
>> indication	for	MPLS	Transport	Profile) to Proposed Standard
>> >
>> >Hi Erminio:
>> >
>> ><snipped>
>> >>Several service providers regarded this draft as not meeting their
>> >>transport networks' needs.
>> >
>> >E> This is a true statement: the solution in this draft is useless for
>> many
>> MPLS- TP deployments.
>> >
>> >The two statements do not necessarily follow.
>> >
>> >What we established during discussions at the SG15 plenary in February
>> was
>> that the issue some service providers had was that the IETF BFD
>> solution
>> exceeded their requirements in that there was additional functionality
>> they did
>> not see a need for, and that they considered any additional
>> functionality
>> parasitic.
>> >
>> >However this is a consequence of adapting an existing technology to a
>> new
>> application. I do not see any way around that. And the entire joint
>> project was
>> based on the premise of engineering re-use not greenfield design. That
>> is what
>> it said on the tin up front, and IMO why when the IETF started down
>> this path
>> packet transport transitioned from being a minority sport to
>> mainstream, so it
>> is a bit late to cry foul....
>> >
>> >My 2 cents
>> >Dave
>> >
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>



From david.i.allan@ericsson.com  Wed Jul 13 15:24:08 2011
Return-Path: <david.i.allan@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 3DC3811E809A; Wed, 13 Jul 2011 15:24:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w6KbYltFl5dJ; Wed, 13 Jul 2011 15:24:07 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by ietfa.amsl.com (Postfix) with ESMTP id 426F711E8082; Wed, 13 Jul 2011 15:24:07 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p6DMO3bj022087; Wed, 13 Jul 2011 17:24:06 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.253]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Wed, 13 Jul 2011 18:24:01 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>, "loa@pi.nu" <loa@pi.nu>, Rui Costa <RCosta@ptinovacao.pt>
Date: Wed, 13 Jul 2011 18:24:00 -0400
Subject: RE: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>	(Proactive Connectivity	Verification,  Continuity Check and Remote Defect indication for	MPLS	Transport	Profile) to Proposed Standard
Thread-Topic: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>	(Proactive Connectivity	Verification,  Continuity Check and Remote Defect indication for	MPLS	Transport	Profile) to Proposed Standard
Thread-Index: AcxBm16fxXJVoZpkQjint6SX3SKvxAAC06zg
Message-ID: <60C093A41B5E45409A19D42CF7786DFD5221437821@EUSAACMS0703.eamcs.ericsson.se>
References: <27773911.3307261310588873729.JavaMail.defaultUser@defaultHost>
In-Reply-To: <27773911.3307261310588873729.JavaMail.defaultUser@defaultHost>
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, 14 Jul 2011 08:19:00 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 22:24:08 -0000

HI Erminio:

The comments that were raised during the day long discussion with the edito=
rs at the SG15 plenary resulted in those comments appearing in the liasion =
IMO in an actionable form and resulted in a constructive outcome. I enjoyed=
 that level of cooperation.

The comments that were punted over the wall with no discussion (depsite req=
uests to allocate meeting time to do so) in some cases were sufficiently va=
gue as to have no constructive value or not have a recognizable issue to be=
 addressed.

A request to have the commenters identified in the liaison so that comments=
 that were unclear could be followed up upon by the editors was refused. Ap=
parently that is not done and I would go so far as to suggest that blanket =
of anonymity diminished the quality of the liaison.  The result of this pro=
cess was that the only recourse to go "what does this mean?" was a complete=
 liaison cycle. For some comments, stomaching a multi-month delay to clarif=
y what the actual issue was that resulted in a comment like "describe the s=
tart-up procedure" was not reasonable, especially given SG15s continual com=
plaint on how slow the IETF was. Such comments had to be weighed against th=
e nature of comments from the larger reviewing community that seemed to hav=
e no issue with the completeness of the document content and perhaps had ac=
tually read it and the supporting documents.

I'll call out an example: a comment that appeared more than once in the lia=
ison was "clarify the raising/clearing of defects as well as any consequent=
 actions" which I can only interpret as section 3.7 of the document not hav=
ing been read. E.g. the TOC is:

3.7.1. Session initiation and Modification	13
3.7.2. Defect entry criteria				13
3.7.3. Defect entry consequent action		14
3.7.4. Defect exit criteria				15
3.7.5. State machines					15

...and if there was a deficiency in the descriptions it was not identified,=
 and we're not mind readers.

So that is both the history and why some comments were rejected. If you can=
 suggest a constructive way to proceed that is not simply a waste of everyo=
ne's time, I'll listen..

Cheers
Dave








-----Original Message-----
From: erminio.ottone_69@libero.it [mailto:erminio.ottone_69@libero.it]=20
Sent: Wednesday, July 13, 2011 1:28 PM
To: David Allan I; loa@pi.nu; Rui Costa
Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
Subject: R: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.t=
xt> (Proactive Connectivity Verification, Continuity Check and Remote Defec=
t indication for MPLS Transport Profile) to Proposed Standard

Do you mean that ITU-T comments were discussed and resolution agreed during=
 the ITU-T meeting?

If this is the case, why the LS just provides the comments and not the agre=
ed resolution?

Why some ITU-T comments have been then rejected?

>----Messaggio originale----
>Da: david.i.allan@ericsson.com
>Data: 6-lug-2011 19.35
>A: "erminio.ottone_69@libero.it"<erminio.ottone_69@libero.it>, "loa@pi.nu"
<loa@pi.nu>, "Rui Costa"<RCosta@ptinovacao.pt>
>Cc: "mpls@ietf.org"<mpls@ietf.org>, "ietf@ietf.org"<ietf@ietf.org>,=20
>"IETF-
Announce"<ietf-announce@ietf.org>
>Ogg: RE: [mpls] R: Re: Last Call:	&lt;draft-ietf-mpls-tp-cc-cv-rdi-05.txt&=
gt;=09
(Proactive Connectivity	Verification, Continuity Check and Remote Defect=20
indication for	MPLS	Transport	Profile) to Proposed Standard
>
>Hi Erminio:
>
>Two of the three document editors were present at SG15 plenary in=20
>February
where the comments originated. The revised meeting schedule resulted in a d=
ay spent going through the document with the editors. IMO there were lots o=
f discussion and legitimate issues with the document identified and correct=
ed so it was a useful session. The liaison of same was in many ways *after =
the fact*.
>
>Cheers
>Dave
>



From gregimirsky@gmail.com  Wed Jul 13 19:49:59 2011
Return-Path: <gregimirsky@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCA3811E8092; Wed, 13 Jul 2011 19:49:59 -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 43fKcpoo0o0F; Wed, 13 Jul 2011 19:49:59 -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 A687B21F89AC; Wed, 13 Jul 2011 19:49:58 -0700 (PDT)
Received: by vxi40 with SMTP id 40so6862868vxi.31 for <multiple recipients>; Wed, 13 Jul 2011 19:49:58 -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=udOEXZs9A9tP3UiUcs2Ad3iMWLmcYFR0sGsnJvGrk7E=; b=cwVGA2jhQP2saKnmeZJorvb7bmboUIOfutuvToOlwLWUCG7p2PkqJaBLOtGuZLD8Eh VkVzAhfBzgHflmgURgopDLT0YvfGNbDwAaiCbC+nXuTKbBcCho/EaW5+S4NOk0uiUgrT YURmevCChjeWD8xgfvngE5GUNh4wM/X/lfxIw=
MIME-Version: 1.0
Received: by 10.52.180.201 with SMTP id dq9mr2097040vdc.245.1310611797779; Wed, 13 Jul 2011 19:49:57 -0700 (PDT)
Received: by 10.52.164.68 with HTTP; Wed, 13 Jul 2011 19:49:57 -0700 (PDT)
In-Reply-To: <24102355.3308421310589129962.JavaMail.defaultUser@defaultHost>
References: <24102355.3308421310589129962.JavaMail.defaultUser@defaultHost>
Date: Wed, 13 Jul 2011 19:49:57 -0700
Message-ID: <CA+RyBmX+sb0L9oFvMSUxF7_BgU-5m4MF3Z87F2k1D_Py_AY_8A@mail.gmail.com>
Subject: Re: [mpls] R: RE: R: Re: LastCall: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive Connectivity Verification, Continuity Check and Remote Defect indicationfor MPLS Transport Profile) to Proposed Standard
From: Greg Mirsky <gregimirsky@gmail.com>
To: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
Content-Type: multipart/alternative; boundary=bcaec51a8228a5263904a7fe96d4
X-Mailman-Approved-At: Thu, 14 Jul 2011 08:19:00 -0700
Cc: mpls@ietf.org, IETF-Announce <ietf-announce@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, 14 Jul 2011 02:49:59 -0000

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

Dear Erminio,
even though I'm not an operator but I think that you've went bit too far in
your first generalization.
"Every generalization is wrong, including this one"

Regards,
Greg

On Wed, Jul 13, 2011 at 1:32 PM, erminio.ottone_69@libero.it <
erminio.ottone_69@libero.it> wrote:

> The technical concern raised during the WG poll has not been resolved so
> the
> history definetely matters.
>
> Quoting RFC5921:
>
>   There are thus two objectives for MPLS-TP:
>
>   1.  To enable MPLS to be deployed in a transport network and operated
>       in a similar manner to existing transport technologies.
>
>   2.  To enable MPLS to support packet transport services with a
>       similar degree of predictability to that found in existing
>       transport networks.
>
> Based on the extensive comments provided by transport operators and ITU-T
> community, the solution in this draft is useless in case 1.
>
> The fact that the solution in this draft is not backward compatible with
> existing IP/MPLS BFD implementations means that this solution is also
> uselesee
> in case 2.
>
> Are there other undocumented use cases for MPLS-TP deployments?
>
> >----Messaggio originale----
> >Da: nurit.sprecher@nsn.com
> >Data: 7-lug-2011 11.59
> >A: <erminio.ottone_69@libero.it>, <RCosta@ptinovacao.pt>, <ietf@ietf.org
> >,
> "IETF-Announce"<ietf-announce@ietf.org>
> >Cc: <mpls@ietf.org>
> >Ogg: RE: [mpls] R: Re: LastCall:
> &lt;draft-ietf-mpls-tp-cc-cv-rdi-05.txt&gt;
> (Proactive      Connectivity    Verification,Continuity Check and Remote
> Defect
> indicationfor   MPLS    Transport       Profile) to Proposed Standard
> >
> >Erminio,
> >I do not think the history is relevant for this specific discussion...
> >Also I find it inappropriate to give statements with no justifications
> >behind.
> >You say: "the solution in this draft is useless for many MPLS-TP
> >deployments.".  in order to seriously consider your comment, you have to
> >show why it is useless and which requirements are not satisfied.
> >Otherwise you cannot expect anyone to refer to your point.
> >Best regards,
> >Nurit
> >
> >P.s. did you mean that the document is useless to available non-standard
> >deployments, e.g. T-MPLS?
> >
> >
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>

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

Dear Erminio,<br>even though I&#39;m not an operator but I think that you&#=
39;ve went bit too far in your first generalization.<br>&quot;Every general=
ization is wrong, including this one&quot;<br><br>Regards,<br>Greg<br><br>
<div class=3D"gmail_quote">On Wed, Jul 13, 2011 at 1:32 PM, <a href=3D"mail=
to:erminio.ottone_69@libero.it">erminio.ottone_69@libero.it</a> <span dir=
=3D"ltr">&lt;<a href=3D"mailto:erminio.ottone_69@libero.it">erminio.ottone_=
69@libero.it</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">The technical concern raised during the WG =
poll has not been resolved so the<br>
history definetely matters.<br>
<br>
Quoting RFC5921:<br>
<br>
 =A0 There are thus two objectives for MPLS-TP:<br>
<br>
 =A0 1. =A0To enable MPLS to be deployed in a transport network and operate=
d<br>
 =A0 =A0 =A0 in a similar manner to existing transport technologies.<br>
<br>
 =A0 2. =A0To enable MPLS to support packet transport services with a<br>
 =A0 =A0 =A0 similar degree of predictability to that found in existing<br>
 =A0 =A0 =A0 transport networks.<br>
<br>
Based on the extensive comments provided by transport operators and ITU-T<b=
r>
community, the solution in this draft is useless in case 1.<br>
<br>
The fact that the solution in this draft is not backward compatible with<br=
>
existing IP/MPLS BFD implementations means that this solution is also usele=
see<br>
in case 2.<br>
<br>
Are there other undocumented use cases for MPLS-TP deployments?<br>
<br>
&gt;----Messaggio originale----<br>
&gt;Da: <a href=3D"mailto:nurit.sprecher@nsn.com">nurit.sprecher@nsn.com</a=
><br>
&gt;Data: 7-lug-2011 11.59<br>
&gt;A: &lt;<a href=3D"mailto:erminio.ottone_69@libero.it">erminio.ottone_69=
@libero.it</a>&gt;, &lt;<a href=3D"mailto:RCosta@ptinovacao.pt">RCosta@ptin=
ovacao.pt</a>&gt;, &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&g=
t;,<br>

<div class=3D"im">&quot;IETF-Announce&quot;&lt;<a href=3D"mailto:ietf-annou=
nce@ietf.org">ietf-announce@ietf.org</a>&gt;<br>
</div>&gt;Cc: &lt;<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>&gt;<br=
>
&gt;Ogg: RE: [mpls] R: Re: LastCall: =A0 =A0 =A0 &amp;lt;draft-ietf-mpls-tp=
-cc-cv-rdi-05.txt&amp;gt;<br>
<div class=3D"im">(Proactive =A0 =A0 =A0Connectivity =A0 =A0Verification,Co=
ntinuity Check and Remote Defect<br>
</div>indicationfor =A0 MPLS =A0 =A0Transport =A0 =A0 =A0 Profile) to Propo=
sed Standard<br>
<div class=3D"im">&gt;<br>
&gt;Erminio,<br>
&gt;I do not think the history is relevant for this specific discussion...<=
br>
&gt;Also I find it inappropriate to give statements with no justifications<=
br>
&gt;behind.<br>
&gt;You say: &quot;the solution in this draft is useless for many MPLS-TP<b=
r>
&gt;deployments.&quot;. =A0in order to seriously consider your comment, you=
 have to<br>
&gt;show why it is useless and which requirements are not satisfied.<br>
&gt;Otherwise you cannot expect anyone to refer to your point.<br>
&gt;Best regards,<br>
&gt;Nurit<br>
&gt;<br>
&gt;P.s. did you mean that the document is useless to available non-standar=
d<br>
&gt;deployments, e.g. T-MPLS?<br>
&gt;<br>
&gt;<br>
<br>
<br>
</div><div><div></div><div class=3D"h5">___________________________________=
____________<br>
mpls mailing list<br>
<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/mpls</a><br>
</div></div></blockquote></div><br>

--bcaec51a8228a5263904a7fe96d4--

From gregimirsky@gmail.com  Wed Jul 13 19:57:21 2011
Return-Path: <gregimirsky@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AB4F11E80E2; Wed, 13 Jul 2011 19:57:21 -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=[AWL=-0.600, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, J_CHICKENPOX_31=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cWKCPr7WQxaw; Wed, 13 Jul 2011 19:57:18 -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 4386611E8092; Wed, 13 Jul 2011 19:57:18 -0700 (PDT)
Received: by vws12 with SMTP id 12so6905605vws.31 for <multiple recipients>; Wed, 13 Jul 2011 19:57:17 -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=ovoFsWMB52EZ/fvdjmuQKFiku8RpwxFcu2ISVl/UwrM=; b=bTroztBPqm8RVaBBr9DHCm4ZRSoMJZ+TID9EpJGfPUA6lB2nUav/7o9yMa2pmKTf79 tqP+u/ffC/QCPlmzXYlpdcQHcRLmno81iHooqI0HEC2iWPEQ5sK7ud/CV1gH843udMDU nAMPgIXlaqFNR3HJsmwWso0DOePMYBAnhvoOw=
MIME-Version: 1.0
Received: by 10.52.0.71 with SMTP id 7mr1904362vdc.494.1310612237646; Wed, 13 Jul 2011 19:57:17 -0700 (PDT)
Received: by 10.52.164.68 with HTTP; Wed, 13 Jul 2011 19:57:17 -0700 (PDT)
In-Reply-To: <947166.3310311310589521384.JavaMail.defaultUser@defaultHost>
References: <947166.3310311310589521384.JavaMail.defaultUser@defaultHost>
Date: Wed, 13 Jul 2011 19:57:17 -0700
Message-ID: <CA+RyBmWMVsrx2GTy8zDYoqB7BQaTPcgQoWKyDOrHShCzdYCSwA@mail.gmail.com>
Subject: Re: [mpls] R: RE: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive Connectivity Verification, Continuity Check and Remote Defect indication for MPLS Transport Profile) to Proposed Standard
From: Greg Mirsky <gregimirsky@gmail.com>
To: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
Content-Type: multipart/alternative; boundary=0023547c8c15dcfe0c04a7feb084
X-Mailman-Approved-At: Thu, 14 Jul 2011 08:19:00 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, david.i.allan@ericsson.com, IETF-Announce <ietf-announce@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, 14 Jul 2011 02:57:21 -0000

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

Dear Erminio,
I'd point that the scope of G.8113.1, a.k.a G.tpoam in regard to CCM is even
more narrow then of the document being discussed. The G.8113.1 addresses
only bi-directional co-routed LSP and has no model to handle bi-directional
associated LSP in independent mode. And unidirectional p2p and p2mp LSPs are
not addressed by the current revision of the G.8113.1.
Can all these out-of-scope constructs be used to conclude that G.8113.1 is
not capable to solve these issues? I don't think so. Solutions are not
readily available, that's all.

Regards,
Greg

On Wed, Jul 13, 2011 at 1:38 PM, erminio.ottone_69@libero.it <
erminio.ottone_69@libero.it> wrote:

> >I would not go so far as to say "similar to 1731", there is actually a lot
> of
> difference under the hood. As for uni-directional BFD, that is a BFD WG
> problem
> at the moment.
>
> The fact that the BFD WG has not defined a solution for unidirectional p2p
> and
> p2mp transport paths does not make BFD a suitable OAM protocol for MPLS-TP
> nor
> does resolve the technical issue that have been raised.
>
> >----Messaggio originale----
> >Da: david.i.allan@ericsson.com
> >Data: 8-lug-2011 18.13
> >A: "Rui Costa"<RCosta@ptinovacao.pt>, "Stewart Bryant"<stbryant@cisco.com
> >
> >Cc: "erminio.ottone_69@libero.it"<erminio.ottone_69@libero.it>,
> "mpls@ietf.
> org"<mpls@ietf.org>, "ietf@ietf.org"<ietf@ietf.org>, "IETF-Announce"<ietf-
> announce@ietf.org>
> >Ogg: RE: [mpls] Last Call: &lt;draft-ietf-mpls-tp-cc-cv-rdi-05.txt&gt;
> (Proactive      Connectivity Verification, Continuity Check and Remote
> Defect
> indication for MPLS     Transport       Profile) to Proposed Standard
> >
> >Rui:
> >
> >You wrote:
> >
> >>Reading something, keeping it on record, without effect in the draft and
> "ignoring comments" have IMHO similar outcomes. As author of the draft you
> are
> free to do it. These standards have a great impact
> >>in our work, so i'm also free to write what i did.
> >
> >Numerous comments did have effect on the draft and those that didn't were
> either simply not actionable, were rhetorical or not constructive, and a
> few
> had to be balanced against comments coming from the MPLS & BFD WGs. I would
> translate "ingored" or "without effect" to "did not get one'e way". In the
> standards process it happens.
> >
> >Meanwhile as an editor of the document, I'll take the liberty of
> responding
> to some of the points you raise...
> >
> >>My technical concerns regarding this draft were expressed...
> >>...in the (ITU-T -> IETF, Feb/2011) liaison regarding it (LS281, i
> believe);
> >>...in operators' meetings' that took place during ITU-T's Feb/2011
> plenary
> meeting;
> >
> >I and the WG don't really have access to private grumblings.
> >
> >>...in a comparison session that took place during that same ITU-T
> meeting.
> >
> >Lots of other opinions were expressed as well, and they did not all agree
> with you.
> >
> >>Some:
> >>CC/CV
> >>I don't understand the need for 2 types of packets: a single type allows
> CC;
> mismatching identifiers in the same CC packets allow CV.
> >>Besides adding complexity, we whether always activate both or potentiate
> undetected mismerges.
> >
> >OK, lets walk through this.
> >
> >We want CV all the time so that any misconectivity can be detected, but on
> the list it was expressed that the group did not want the overhead of
> processing the source MEP TLV in every packet in order to achieve this. We
> could carry it in every packet and have the receiver simply ignore most of
> them, but then that would make the defect entry criteria compeltely random
> and
> the exit criteria unreliable as well, not really a good design. Hence they
> are
> separated using different ACH code points and the receiver is obliged to
> process every source MEP TLV it receives. I hope this is clear.
> >
> >>(BTW: can't understand how we propose one ACH codepoint to CC, another
> for
> CV, [counting other drafts, another for frame loss ...] but don't consider
> assigning 1 single ACH protocol identifier codepoint >as requested by
> ITU-T)
> >
> >Because that puts you into two protocol ID demultiplexing steps per OAM
> PDU
> recevied to determine the intended function. Hence COSTS MORE. That is
> pretty
> basic...
> >
> >> Uni P2P / P2MP
> >> I can't see how BFD will support unidir and hence P2MP other than...
> >> ...eliminating the session "state variable" (down, init, up), aiming
> just
> the state variables we really need, bringing us to something similar to
> 1731,
> eventually with other bits on the wire or...
> >> ...using IP to create the reverse way, which we cannot assume per
> requirements;
> >> Will we create a complete different tool for that?
> >> (BFD's B="bidirectional")
> >
> >I would not go so far as to say "similar to 1731", there is actually a lot
> of
> difference under the hood. As for uni-directional BFD, that is a BFD WG
> problem
> at the moment.
> >
> >> Provisioning list
> >> This is an MPLS profile/subset (and i heard) achievable through a
> particular configuration. So, i expect each draft-ietf-mpls-TP-* to focus
> on
> that profile/configuration. However, i keep seeing
> >> references f.i. to IP encapsulations unexpected under TP's OAM.
> >> I don't thus understand what the aim is: do we expect this in TP, are we
> talking about MPLS in general?... The TP profile is never quite delimited.
> >> Does chapter 4 contain ALL the configurable parameters list agreed to
> provide in the comparison session?
> >
> >It should. As for encapsulations, unless TP is in a complete island not
> connected to anything (which as a network is rather useless) it will be
> expected to interoperate with the rest of the MPLS architecture, and the
> stated
> intention of tool development was that what resulted was applicable to the
> broader MPLS architecture. Which means backwards compatiblity and
> procedures
> for interoperation.
> >
> >> Backwards compatibility
> >> This was the main argument risen to ground MPLS-TP OAM on BFD. It's not
> a
> better argument than grounding MPLS-TP OAM on 1731 due to its ETH
> deployment
> plus coherence with SDH, OTN, as defended by ITU-T.
> >> For reasons like the above, however, MPLS-TP BFD won't be backwards
> compatible with previous BFD (even considering just CC/CV). They don't even
> share the same codepoint.
> >
> >The issue is not code point, which is the trivial part. It is reuse of the
> majority of the implementation. Again, pretty basic.
> >
> >>Simplicity
> >>Whether we look to PDH, SDH, OTN or ETH, ITU-T's approach to CC is
> simpler:
> in each flow, a standard defined nr of constant heartbeat signals (with
> standard constant or provisioned period - no
> >>auto/negotiated -) means OK. A standard defined number of misses means
> lost
> Rx connection. An RDI, the only articulation between Rx and Tx flows,
> meaningful in bidirectional applications, allows each
> >>pear to identify Tx problems.
> >>This OAM simplicity is the key for reliable fail finger pointing,
> performance reports and protection. Also to allow scaling, more
> implementation
> opportunities/manufacturers, which is valuable for
> >>operators.
> >
> >Well IMO there was not a lot of interest in T-MPLS until the IETF was
> going
> to re-define it and make it compatible with IP/MPLS. So there was an
> industry
> wide "design intent" implied here.
> >
> >> IMHO, between your MPLS-TP view and MPLS/IP, it becomes more and more
> difficult to tell which is which.
> >
> >That is because MPLS-TP is not a new techology, it is an addition to the
> entire MPLS protocol suite.
> >
> >Hope this helps
> >D
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >-----Original Message-----
> >From: David Allan I [mailto:david.i.allan@ericsson.com]
> >Sent: quarta-feira, 6 de Julho de 2011 19:25
> >To: erminio.ottone_69@libero.it; Rui Costa; ietf@ietf.org; IETF-Announce
> >Cc: mpls@ietf.org
> >Subject: RE: [mpls] R: Re: Last Call:
> <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote Defect
> indication for MPLS Transport Profile) to Proposed Standard
> >
> >Hi Erminio:
> >
> ><snipped>
> >>Several service providers regarded this draft as not meeting their
> >>transport networks' needs.
> >
> >E> This is a true statement: the solution in this draft is useless for
> many
> MPLS- TP deployments.
> >
> >The two statements do not necessarily follow.
> >
> >What we established during discussions at the SG15 plenary in February was
> that the issue some service providers had was that the IETF BFD solution
> exceeded their requirements in that there was additional functionality they
> did
> not see a need for, and that they considered any additional functionality
> parasitic.
> >
> >However this is a consequence of adapting an existing technology to a new
> application. I do not see any way around that. And the entire joint project
> was
> based on the premise of engineering re-use not greenfield design. That is
> what
> it said on the tin up front, and IMO why when the IETF started down this
> path
> packet transport transitioned from being a minority sport to mainstream, so
> it
> is a bit late to cry foul....
> >
> >My 2 cents
> >Dave
> >
> >
> >
> >
> >-----Original Message-----
> >From: David Allan I [mailto:david.i.allan@ericsson.com]
> >Sent: quarta-feira, 6 de Julho de 2011 18:36
> >To: erminio.ottone_69@libero.it; loa@pi.nu; Rui Costa
> >Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
> >Subject: RE: [mpls] R: Re: Last Call:
> <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote Defect
> indication for MPLS Transport Profile) to Proposed Standard
> >
> >Hi Erminio:
> >
> >Two of the three document editors were present at SG15 plenary in February
> where the comments originated. The revised meeting schedule resulted in a
> day
> spent going through the document with the editors. IMO there were lots of
> discussion and legitimate issues with the document identified and corrected
> so
> it was a useful session. The liaison of same was in many ways *after the
> fact*.
> >
> >Cheers
> >Dave
> >
> >
> >
> >
> >-----Original Message-----
> >From: erminio.ottone_69@libero.it [mailto:erminio.ottone_69@libero.it]
> >Sent: quarta-feira, 6 de Julho de 2011 18:34
> >To: Rui Costa; ietf@ietf.org; IETF-Announce
> >Cc: mpls@ietf.org
> >Subject: R: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote Defect
> indication for MPLS Transport Profile) to Proposed Standard
> >
> >The way this draft has been developed is a bit strange.
> >
> >The poll for its adoption as a WG document was halted by the MPLS WG chair
> because "it is not possible to judge consensus":
> >
> >http://www.ietf.org/mail-archive/web/mpls/current/msg04502.html
> >
> >The lack of consensus was motivated by serious technical concerns raised
> by
> several transport experts during the poll.
> >
> >Nevertheless the MPLS WG chair decided to adopt the draft as a WG
> document:
> >
> >http://www.ietf.org/mail-archive/web/mpls/current/msg04512.html
> >
> >After several WG revisions and WG LCs, the technical issues have not been
> resolved.
> >
> >>Several service providers regarded this draft as not meeting their
> >>transport
> >networks' needs.
> >
> >This is a true statement: the solution in this draft is useless for many
> MPLS- TP deployments.
> >
> >
> >-----Original Message-----
> >From: erminio.ottone_69@libero.it [mailto:erminio.ottone_69@libero.it]
> >Sent: quarta-feira, 6 de Julho de 2011 18:26
> >To: loa@pi.nu; Rui Costa
> >Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
> >Subject: R: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote Defect
> indication for MPLS Transport Profile) to Proposed Standard
> >
> >>  Version -04 of the document was published June 28th.
> >>
> >>  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
> >> June 29th.
> >>
> >
> >So when the WG LC to confirm the LC comment resolution has been launched?
> >
> >The proto write-up says:
> >
> >            It has also passed a working roup call to verify that LC
> comments
> were correctly with minor comments.
> >
> >It also says:
> >
> >            The comments has been
> >            carefully discussed between the authors and people making the
> comments and
> >            has been resolved.
> >
> >But it seems that some comments have not been discussed with the authors
> of
> the comments. When ITU-T Q10/15 has been involved in discussing its
> comments?
> >
> >
> >
> >
> >-----Original Message-----
> >From: Loa Andersson [mailto:loa@pi.nu]
> >Sent: quarta-feira, 6 de Julho de 2011 16:44
> >To: Rui Costa
> >Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
> >Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote Defect
> indication for MPLS Transport Profile) to Proposed Standard
> >
> >All,
> >
> >Since someone has commented about the process used for resolving
> >questions on
> >draft-ietf-mpls-tp-cc-cv-rdi I am supplying some details below.
> >
> >The history of draft-ietf-mpls-tp-cc-cv-rdi working group review
> >process is:
> >
> >On February 3rd 2011 the working group last call was issued
> >on version -03
> >
> >      This was copied to the the Ad Hoc Team List
> >      and liaised to SG15 also on February 3rd
> >
> >      This working group last call ended om Feb 28
> >
> >
> >      On Feb 28 we also received a liaison with comments from SG15
> >
> >
> >The authors compiled a list of all comments received  as part the MPLS
> >working group last call; these  comments - and the intended resolution -
> >is included in the meeting minutes from the Prague meeting:
> >
> >
> >      http://www.ietf.org/proceedings/80/slides/mpls-9.pdf
> >
> >
> >  During the IETF meeting in Prague, we agreed with the BFD working
> >  group to do a separate working group last callfor the BFD working
> >  group
> >
> >The (BFD) working group last call was started on March 30th and ran
> >for 13 days. The last call ended on April 11th.
> >
> >  The authors have since worked hard to resolve comments, some
> >  issue has been brought to the working group mailing list for
> >  resolution.
> >
> >  Version -04 of the document was published June 28th.
> >
> >  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
> >  June 29th.
> >
> >  The AD review resulted in a "New ID needed" due to mostly editorial
> >  comments. Version -05 was published on June 29 and the IETF last call
> >  started as soon as the new ID was avaialbe.
> >
> >  The current list of Last Call Comments resoltion is also avaiable at:
> >  http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls
> >
> >  The list of issues that the authors kept very carefully, shows without
> >doubt
> >  that no comments been ignored.
> >
> >  Loa
> >  mpls wg document shepherd
> >
> >
> >
> >
> >
> >
> >
> >-----Original Message-----
> >From: David Allan I [mailto:david.i.allan@ericsson.com]
> >Sent: quarta-feira, 6 de Julho de 2011 14:58
> >To: Rui Costa; ietf@ietf.org; IETF-Announce
> >Cc: mpls@ietf.org
> >Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote Defect
> indication for MPLS Transport Profile) to Proposed Standard
> >
> >Hi Rui:
> >
> >The comments were not ignored, the resolution of the Q10 comments as well
> as
> those collected from the MPLS WG was presented at the last IETF. My
> spreadsheet
> from which that report was generated and has been augmented to include the
> BFD
> WG comments is available at
> http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.
> xls
> >
> >So you know...
> >Dave
> >
> >
> >-----Original Message-----
> >From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Rui
> Costa
> >Sent: segunda-feira, 4 de Julho de 2011 23:03
> >To: ietf@ietf.org; IETF-Announce
> >Cc: mpls@ietf.org
> >Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive Connectivity Verification, Continuity Check and Remote Defect
> indication for MPLS Transport Profile) to Proposed Standard
> >
> >IMHO and for the record:
> >
> >ITU-T comments regarding this draft haven't been discussed with ITU-T but
> were simply ignored. No LS describing these comments' resolution was sent.
> >
> >Several service providers regarded this draft as not meeting their
> transport
> networks' needs.
> >
> >[The v03 draft was published in Feb and went to WG LC.
> >The v04 draft addressing WG LC comments was published on the 28th June
> (same
> date as the proto write-up).
> >When was the WG LC launched, to verify LC comments resolution?]
> >
> >Regards,
> >Rui
> >
> >
> >-----Original Message-----
> >From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> The
> IESG
> >Sent: quinta-feira, 30 de Junho de 2011 14:47
> >To: IETF-Announce
> >Cc: mpls@ietf.org
> >Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
> (Proactive
> Connectivity Verification, Continuity Check and Remote Defect indication
> for
> MPLS Transport Profile) to Proposed Standard
> >
> >
> >The IESG has received a request from the Multiprotocol Label Switching WG
> >(mpls) to consider the following document:
> >- 'Proactive Connectivity Verification, Continuity Check and Remote
> >   Defect indication for MPLS Transport Profile'
> >  <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally, comments may be
> >sent to iesg@ietf.org instead. In either case, please retain the
> >beginning of the Subject line to allow automated sorting.
> >
> >Abstract
> >
> >   Continuity Check, Proactive Connectivity Verification and Remote
> >   Defect Indication functionalities are required for MPLS-TP OAM.
> >
> >   Continuity Check monitors the integrity of the continuity of the
> >   label switched path for any loss of continuity defect. Connectivity
> >   verification monitors the integrity of the routing of the label
> >   switched path between sink and source for any connectivity issues.
> >   Remote defect indication enables an End Point to report, to its
> >   associated End Point, a fault or defect condition that it detects on
> >   a pseudo wire, label switched path or Section.
> >
> >   This document specifies methods for proactive continuity check,
> >   continuity verification, and remote defect indication for MPLS-TP
> >   label switched paths, pseudo wires and Sections using Bidirectional
> >   Forwarding Detection.
> >
> >
> >The file can be obtained via
> >http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
> >
> >IESG discussion can be tracked via
> >http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
> >
> >
> >No IPR declarations have been submitted directly on this I-D.
> >_______________________________________________
> >mpls mailing list
> >mpls@ietf.org
> >https://www.ietf.org/mailman/listinfo/mpls
> >
> >
> >_______________________________________________
> >Ietf mailing list
> >Ietf@ietf.org
> >https://www.ietf.org/mailman/listinfo/ietf
> >
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>

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

Dear Erminio,<br>I&#39;d point that the scope of G.8113.1, a.k.a G.tpoam in=
 regard to CCM is even more narrow then of the document being discussed. Th=
e G.8113.1 addresses only bi-directional co-routed LSP and has no model to =
handle bi-directional associated LSP in independent mode. And unidirectiona=
l p2p and p2mp LSPs are not addressed by the current revision of the G.8113=
.1.<br>
Can all these out-of-scope constructs be used to conclude that G.8113.1 is =
not capable to solve these issues? I don&#39;t think so. Solutions are not =
readily available, that&#39;s all. <br><br>Regards,<br>Greg<br><br><div cla=
ss=3D"gmail_quote">
On Wed, Jul 13, 2011 at 1:38 PM, <a href=3D"mailto:erminio.ottone_69@libero=
.it">erminio.ottone_69@libero.it</a> <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:erminio.ottone_69@libero.it">erminio.ottone_69@libero.it</a>&gt;</span> w=
rote:<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;I would not go so far=
 as to say &quot;similar to 1731&quot;, there is actually a lot of<br>
difference under the hood. As for uni-directional BFD, that is a BFD WG pro=
blem<br>
at the moment.<br>
<br>
</div>The fact that the BFD WG has not defined a solution for unidirectiona=
l p2p and<br>
p2mp transport paths does not make BFD a suitable OAM protocol for MPLS-TP =
nor<br>
does resolve the technical issue that have been raised.<br>
<div class=3D"im"><br>
&gt;----Messaggio originale----<br>
&gt;Da: <a href=3D"mailto:david.i.allan@ericsson.com">david.i.allan@ericsso=
n.com</a><br>
</div>&gt;Data: 8-lug-2011 18.13<br>
&gt;A: &quot;Rui Costa&quot;&lt;<a href=3D"mailto:RCosta@ptinovacao.pt">RCo=
sta@ptinovacao.pt</a>&gt;, &quot;Stewart Bryant&quot;&lt;<a href=3D"mailto:=
stbryant@cisco.com">stbryant@cisco.com</a>&gt;<br>
&gt;Cc: &quot;<a href=3D"mailto:erminio.ottone_69@libero.it">erminio.ottone=
_69@libero.it</a>&quot;&lt;<a href=3D"mailto:erminio.ottone_69@libero.it">e=
rminio.ottone_69@libero.it</a>&gt;, &quot;mpls@ietf.<br>
org&quot;&lt;<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>&gt;, &quot;=
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&quot;&lt;<a href=3D"mail=
to:ietf@ietf.org">ietf@ietf.org</a>&gt;, &quot;IETF-Announce&quot;&lt;ietf-=
<br>

<a href=3D"mailto:announce@ietf.org">announce@ietf.org</a>&gt;<br>
&gt;Ogg: RE: [mpls] Last Call: &amp;lt;draft-ietf-mpls-tp-cc-cv-rdi-05.txt&=
amp;gt;<br>
<div class=3D"im">(Proactive =A0 =A0 =A0Connectivity Verification, Continui=
ty Check and Remote Defect<br>
</div>indication for MPLS =A0 =A0 Transport =A0 =A0 =A0 Profile) to Propose=
d Standard<br>
&gt;<br>
&gt;Rui:<br>
<div class=3D"im">&gt;<br>
&gt;You wrote:<br>
&gt;<br>
&gt;&gt;Reading something, keeping it on record, without effect in the draf=
t and<br>
&quot;ignoring comments&quot; have IMHO similar outcomes. As author of the =
draft you are<br>
free to do it. These standards have a great impact<br>
&gt;&gt;in our work, so i&#39;m also free to write what i did.<br>
&gt;<br>
</div><div class=3D"im">&gt;Numerous comments did have effect on the draft =
and those that didn&#39;t were<br>
either simply not actionable, were rhetorical or not constructive, and a fe=
w<br>
had to be balanced against comments coming from the MPLS &amp; BFD WGs. I w=
ould<br>
translate &quot;ingored&quot; or &quot;without effect&quot; to &quot;did no=
t get one&#39;e way&quot;. In the<br>
standards process it happens.<br>
&gt;<br>
&gt;Meanwhile as an editor of the document, I&#39;ll take the liberty of re=
sponding<br>
to some of the points you raise...<br>
&gt;<br>
</div><div class=3D"im">&gt;&gt;My technical concerns regarding this draft =
were expressed...<br>
&gt;&gt;...in the (ITU-T -&gt; IETF, Feb/2011) liaison regarding it (LS281,=
 i<br>
believe);<br>
&gt;&gt;...in operators&#39; meetings&#39; that took place during ITU-T&#39=
;s Feb/2011 plenary<br>
meeting;<br>
&gt;<br>
</div><div class=3D"im">&gt;I and the WG don&#39;t really have access to pr=
ivate grumblings.<br>
&gt;<br>
</div><div class=3D"im">&gt;&gt;...in a comparison session that took place =
during that same ITU-T meeting.<br>
&gt;<br>
</div><div class=3D"im">&gt;Lots of other opinions were expressed as well, =
and they did not all agree<br>
with you.<br>
&gt;<br>
</div><div class=3D"im">&gt;&gt;Some:<br>
&gt;&gt;CC/CV<br>
&gt;&gt;I don&#39;t understand the need for 2 types of packets: a single ty=
pe allows CC;<br>
mismatching identifiers in the same CC packets allow CV.<br>
&gt;&gt;Besides adding complexity, we whether always activate both or poten=
tiate<br>
undetected mismerges.<br>
&gt;<br>
</div><div class=3D"im">&gt;OK, lets walk through this.<br>
&gt;<br>
&gt;We want CV all the time so that any misconectivity can be detected, but=
 on<br>
the list it was expressed that the group did not want the overhead of<br>
processing the source MEP TLV in every packet in order to achieve this. We<=
br>
could carry it in every packet and have the receiver simply ignore most of<=
br>
them, but then that would make the defect entry criteria compeltely random =
and<br>
the exit criteria unreliable as well, not really a good design. Hence they =
are<br>
separated using different ACH code points and the receiver is obliged to<br=
>
process every source MEP TLV it receives. I hope this is clear.<br>
&gt;<br>
</div><div class=3D"im">&gt;&gt;(BTW: can&#39;t understand how we propose o=
ne ACH codepoint to CC, another for<br>
CV, [counting other drafts, another for frame loss ...] but don&#39;t consi=
der<br>
assigning 1 single ACH protocol identifier codepoint &gt;as requested by IT=
U-T)<br>
&gt;<br>
</div><div class=3D"im">&gt;Because that puts you into two protocol ID demu=
ltiplexing steps per OAM PDU<br>
recevied to determine the intended function. Hence COSTS MORE. That is pret=
ty<br>
basic...<br>
&gt;<br>
</div><div class=3D"im">&gt;&gt; Uni P2P / P2MP<br>
&gt;&gt; I can&#39;t see how BFD will support unidir and hence P2MP other t=
han...<br>
&gt;&gt; ...eliminating the session &quot;state variable&quot; (down, init,=
 up), aiming just<br>
the state variables we really need, bringing us to something similar to 173=
1,<br>
eventually with other bits on the wire or...<br>
&gt;&gt; ...using IP to create the reverse way, which we cannot assume per<=
br>
requirements;<br>
&gt;&gt; Will we create a complete different tool for that?<br>
&gt;&gt; (BFD&#39;s B=3D&quot;bidirectional&quot;)<br>
&gt;<br>
</div><div class=3D"im">&gt;I would not go so far as to say &quot;similar t=
o 1731&quot;, there is actually a lot of<br>
difference under the hood. As for uni-directional BFD, that is a BFD WG pro=
blem<br>
at the moment.<br>
&gt;<br>
</div><div class=3D"im">&gt;&gt; Provisioning list<br>
&gt;&gt; This is an MPLS profile/subset (and i heard) achievable through a<=
br>
particular configuration. So, i expect each draft-ietf-mpls-TP-* to focus o=
n<br>
that profile/configuration. However, i keep seeing<br>
&gt;&gt; references f.i. to IP encapsulations unexpected under TP&#39;s OAM=
.<br>
&gt;&gt; I don&#39;t thus understand what the aim is: do we expect this in =
TP, are we<br>
talking about MPLS in general?... The TP profile is never quite delimited.<=
br>
&gt;&gt; Does chapter 4 contain ALL the configurable parameters list agreed=
 to<br>
provide in the comparison session?<br>
&gt;<br>
</div><div class=3D"im">&gt;It should. As for encapsulations, unless TP is =
in a complete island not<br>
connected to anything (which as a network is rather useless) it will be<br>
expected to interoperate with the rest of the MPLS architecture, and the st=
ated<br>
intention of tool development was that what resulted was applicable to the<=
br>
broader MPLS architecture. Which means backwards compatiblity and procedure=
s<br>
for interoperation.<br>
&gt;<br>
</div><div class=3D"im">&gt;&gt; Backwards compatibility<br>
&gt;&gt; This was the main argument risen to ground MPLS-TP OAM on BFD. It&=
#39;s not a<br>
better argument than grounding MPLS-TP OAM on 1731 due to its ETH deploymen=
t<br>
plus coherence with SDH, OTN, as defended by ITU-T.<br>
&gt;&gt; For reasons like the above, however, MPLS-TP BFD won&#39;t be back=
wards<br>
compatible with previous BFD (even considering just CC/CV). They don&#39;t =
even<br>
share the same codepoint.<br>
&gt;<br>
</div><div class=3D"im">&gt;The issue is not code point, which is the trivi=
al part. It is reuse of the<br>
majority of the implementation. Again, pretty basic.<br>
&gt;<br>
</div><div class=3D"im">&gt;&gt;Simplicity<br>
&gt;&gt;Whether we look to PDH, SDH, OTN or ETH, ITU-T&#39;s approach to CC=
 is simpler:<br>
in each flow, a standard defined nr of constant heartbeat signals (with<br>
standard constant or provisioned period - no<br>
&gt;&gt;auto/negotiated -) means OK. A standard defined number of misses me=
ans lost<br>
Rx connection. An RDI, the only articulation between Rx and Tx flows,<br>
meaningful in bidirectional applications, allows each<br>
&gt;&gt;pear to identify Tx problems.<br>
&gt;&gt;This OAM simplicity is the key for reliable fail finger pointing,<b=
r>
performance reports and protection. Also to allow scaling, more implementat=
ion<br>
opportunities/manufacturers, which is valuable for<br>
&gt;&gt;operators.<br>
&gt;<br>
</div><div class=3D"im">&gt;Well IMO there was not a lot of interest in T-M=
PLS until the IETF was going<br>
to re-define it and make it compatible with IP/MPLS. So there was an indust=
ry<br>
wide &quot;design intent&quot; implied here.<br>
&gt;<br>
</div><div class=3D"im">&gt;&gt; IMHO, between your MPLS-TP view and MPLS/I=
P, it becomes more and more<br>
difficult to tell which is which.<br>
&gt;<br>
</div><div class=3D"im">&gt;That is because MPLS-TP is not a new techology,=
 it is an addition to the<br>
entire MPLS protocol suite.<br>
&gt;<br>
&gt;Hope this helps<br>
&gt;D<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
</div><div class=3D"im">&gt;-----Original Message-----<br>
&gt;From: David Allan I [mailto:<a href=3D"mailto:david.i.allan@ericsson.co=
m">david.i.allan@ericsson.com</a>]<br>
&gt;Sent: quarta-feira, 6 de Julho de 2011 19:25<br>
</div><div class=3D"im">&gt;To: <a href=3D"mailto:erminio.ottone_69@libero.=
it">erminio.ottone_69@libero.it</a>; Rui Costa; <a href=3D"mailto:ietf@ietf=
.org">ietf@ietf.org</a>; IETF-Announce<br>
&gt;Cc: <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br>
</div><div class=3D"im">&gt;Subject: RE: [mpls] R: Re: Last Call: &lt;draft=
-ietf-mpls-tp-cc-cv-rdi-05.txt&gt;<br>
(Proactive Connectivity Verification, Continuity Check and Remote Defect<br=
>
</div>indication for MPLS Transport Profile) to Proposed Standard<br>
<div class=3D"im">&gt;<br>
&gt;Hi Erminio:<br>
&gt;<br>
&gt;&lt;snipped&gt;<br>
&gt;&gt;Several service providers regarded this draft as not meeting their<=
br>
&gt;&gt;transport networks&#39; needs.<br>
&gt;<br>
</div>&gt;E&gt; This is a true statement: the solution in this draft is use=
less for many<br>
MPLS- TP deployments.<br>
&gt;<br>
<div class=3D"im">&gt;The two statements do not necessarily follow.<br>
&gt;<br>
&gt;What we established during discussions at the SG15 plenary in February =
was<br>
that the issue some service providers had was that the IETF BFD solution<br=
>
exceeded their requirements in that there was additional functionality they=
 did<br>
not see a need for, and that they considered any additional functionality<b=
r>
parasitic.<br>
&gt;<br>
&gt;However this is a consequence of adapting an existing technology to a n=
ew<br>
application. I do not see any way around that. And the entire joint project=
 was<br>
based on the premise of engineering re-use not greenfield design. That is w=
hat<br>
it said on the tin up front, and IMO why when the IETF started down this pa=
th<br>
packet transport transitioned from being a minority sport to mainstream, so=
 it<br>
is a bit late to cry foul....<br>
&gt;<br>
&gt;My 2 cents<br>
&gt;Dave<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
</div><div class=3D"im">&gt;-----Original Message-----<br>
&gt;From: David Allan I [mailto:<a href=3D"mailto:david.i.allan@ericsson.co=
m">david.i.allan@ericsson.com</a>]<br>
&gt;Sent: quarta-feira, 6 de Julho de 2011 18:36<br>
</div><div class=3D"im">&gt;To: <a href=3D"mailto:erminio.ottone_69@libero.=
it">erminio.ottone_69@libero.it</a>; <a href=3D"mailto:loa@pi.nu">loa@pi.nu=
</a>; Rui Costa<br>
&gt;Cc: <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>; <a href=3D"mail=
to:ietf@ietf.org">ietf@ietf.org</a>; IETF-Announce<br>
&gt;Subject: RE: [mpls] R: Re: Last Call: &lt;draft-ietf-mpls-tp-cc-cv-rdi-=
05.txt&gt;<br>
(Proactive Connectivity Verification, Continuity Check and Remote Defect<br=
>
</div>indication for MPLS Transport Profile) to Proposed Standard<br>
<div class=3D"im">&gt;<br>
&gt;Hi Erminio:<br>
&gt;<br>
&gt;Two of the three document editors were present at SG15 plenary in Febru=
ary<br>
where the comments originated. The revised meeting schedule resulted in a d=
ay<br>
spent going through the document with the editors. IMO there were lots of<b=
r>
discussion and legitimate issues with the document identified and corrected=
 so<br>
it was a useful session. The liaison of same was in many ways *after the<br=
>
fact*.<br>
&gt;<br>
&gt;Cheers<br>
&gt;Dave<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
</div><div class=3D"im">&gt;-----Original Message-----<br>
&gt;From: <a href=3D"mailto:erminio.ottone_69@libero.it">erminio.ottone_69@=
libero.it</a> [mailto:<a href=3D"mailto:erminio.ottone_69@libero.it">ermini=
o.ottone_69@libero.it</a>]<br>
&gt;Sent: quarta-feira, 6 de Julho de 2011 18:34<br>
</div><div class=3D"im">&gt;To: Rui Costa; <a href=3D"mailto:ietf@ietf.org"=
>ietf@ietf.org</a>; IETF-Announce<br>
&gt;Cc: <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br>
</div><div class=3D"im">&gt;Subject: R: Re: [mpls] Last Call: &lt;draft-iet=
f-mpls-tp-cc-cv-rdi-05.txt&gt;<br>
(Proactive Connectivity Verification, Continuity Check and Remote Defect<br=
>
</div><div class=3D"im">indication for MPLS Transport Profile) to Proposed =
Standard<br>
&gt;<br>
&gt;The way this draft has been developed is a bit strange.<br>
&gt;<br>
&gt;The poll for its adoption as a WG document was halted by the MPLS WG ch=
air<br>
because &quot;it is not possible to judge consensus&quot;:<br>
&gt;<br>
&gt;<a href=3D"http://www.ietf.org/mail-archive/web/mpls/current/msg04502.h=
tml" target=3D"_blank">http://www.ietf.org/mail-archive/web/mpls/current/ms=
g04502.html</a><br>
&gt;<br>
&gt;The lack of consensus was motivated by serious technical concerns raise=
d by<br>
several transport experts during the poll.<br>
&gt;<br>
&gt;Nevertheless the MPLS WG chair decided to adopt the draft as a WG docum=
ent:<br>
&gt;<br>
&gt;<a href=3D"http://www.ietf.org/mail-archive/web/mpls/current/msg04512.h=
tml" target=3D"_blank">http://www.ietf.org/mail-archive/web/mpls/current/ms=
g04512.html</a><br>
&gt;<br>
&gt;After several WG revisions and WG LCs, the technical issues have not be=
en<br>
resolved.<br>
&gt;<br>
</div><div class=3D"im">&gt;&gt;Several service providers regarded this dra=
ft as not meeting their<br>
&gt;&gt;transport<br>
&gt;networks&#39; needs.<br>
&gt;<br>
</div>&gt;This is a true statement: the solution in this draft is useless f=
or many<br>
MPLS- TP deployments.<br>
<div class=3D"im">&gt;<br>
&gt;<br>
&gt;-----Original Message-----<br>
&gt;From: <a href=3D"mailto:erminio.ottone_69@libero.it">erminio.ottone_69@=
libero.it</a> [mailto:<a href=3D"mailto:erminio.ottone_69@libero.it">ermini=
o.ottone_69@libero.it</a>]<br>
&gt;Sent: quarta-feira, 6 de Julho de 2011 18:26<br>
</div><div class=3D"im">&gt;To: <a href=3D"mailto:loa@pi.nu">loa@pi.nu</a>;=
 Rui Costa<br>
&gt;Cc: <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>; <a href=3D"mail=
to:ietf@ietf.org">ietf@ietf.org</a>; IETF-Announce<br>
&gt;Subject: R: Re: [mpls] Last Call: &lt;draft-ietf-mpls-tp-cc-cv-rdi-05.t=
xt&gt;<br>
(Proactive Connectivity Verification, Continuity Check and Remote Defect<br=
>
</div>indication for MPLS Transport Profile) to Proposed Standard<br>
<div class=3D"im">&gt;<br>
&gt;&gt; =A0Version -04 of the document was published June 28th.<br>
&gt;&gt;<br>
</div><div class=3D"im">&gt;&gt; =A0The publication request for draft-ietf-=
mpls-tp-cc-cv-rdi was =A0sent<br>
&gt;&gt; June 29th.<br>
&gt;&gt;<br>
&gt;<br>
&gt;So when the WG LC to confirm the LC comment resolution has been launche=
d?<br>
&gt;<br>
&gt;The proto write-up says:<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0It has also passed a working roup call to verif=
y that LC comments<br>
were correctly with minor comments.<br>
&gt;<br>
&gt;It also says:<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0The comments has been<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0carefully discussed between the authors and peo=
ple making the<br>
comments and<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0has been resolved.<br>
&gt;<br>
&gt;But it seems that some comments have not been discussed with the author=
s of<br>
the comments. When ITU-T Q10/15 has been involved in discussing its comment=
s?<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;-----Original Message-----<br>
&gt;From: Loa Andersson [mailto:<a href=3D"mailto:loa@pi.nu">loa@pi.nu</a>]=
<br>
&gt;Sent: quarta-feira, 6 de Julho de 2011 16:44<br>
&gt;To: Rui Costa<br>
</div><div class=3D"im">&gt;Cc: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.=
org</a>; IETF-Announce; <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><=
br>
</div><div class=3D"im">&gt;Subject: Re: [mpls] Last Call: &lt;draft-ietf-m=
pls-tp-cc-cv-rdi-05.txt&gt;<br>
(Proactive Connectivity Verification, Continuity Check and Remote Defect<br=
>
</div><div><div></div><div class=3D"h5">indication for MPLS Transport Profi=
le) to Proposed Standard<br>
&gt;<br>
&gt;All,<br>
&gt;<br>
&gt;Since someone has commented about the process used for resolving<br>
&gt;questions on<br>
&gt;draft-ietf-mpls-tp-cc-cv-rdi I am supplying some details below.<br>
&gt;<br>
&gt;The history of draft-ietf-mpls-tp-cc-cv-rdi working group review<br>
&gt;process is:<br>
&gt;<br>
&gt;On February 3rd 2011 the working group last call was issued<br>
&gt;on version -03<br>
&gt;<br>
&gt; =A0 =A0 =A0This was copied to the the Ad Hoc Team List<br>
&gt; =A0 =A0 =A0and liaised to SG15 also on February 3rd<br>
&gt;<br>
&gt; =A0 =A0 =A0This working group last call ended om Feb 28<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0On Feb 28 we also received a liaison with comments from SG1=
5<br>
&gt;<br>
&gt;<br>
&gt;The authors compiled a list of all comments received =A0as part the MPL=
S<br>
&gt;working group last call; these =A0comments - and the intended resolutio=
n -<br>
&gt;is included in the meeting minutes from the Prague meeting:<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0<a href=3D"http://www.ietf.org/proceedings/80/slides/mpls-9=
.pdf" target=3D"_blank">http://www.ietf.org/proceedings/80/slides/mpls-9.pd=
f</a><br>
&gt;<br>
&gt;<br>
&gt; =A0During the IETF meeting in Prague, we agreed with the BFD working<b=
r>
&gt; =A0group to do a separate working group last callfor the BFD working<b=
r>
&gt; =A0group<br>
&gt;<br>
&gt;The (BFD) working group last call was started on March 30th and ran<br>
&gt;for 13 days. The last call ended on April 11th.<br>
&gt;<br>
&gt; =A0The authors have since worked hard to resolve comments, some<br>
&gt; =A0issue has been brought to the working group mailing list for<br>
&gt; =A0resolution.<br>
&gt;<br>
&gt; =A0Version -04 of the document was published June 28th.<br>
&gt;<br>
&gt; =A0The publication request for draft-ietf-mpls-tp-cc-cv-rdi was =A0sen=
t<br>
&gt; =A0June 29th.<br>
&gt;<br>
&gt; =A0The AD review resulted in a &quot;New ID needed&quot; due to mostly=
 editorial<br>
&gt; =A0comments. Version -05 was published on June 29 and the IETF last ca=
ll<br>
&gt; =A0started as soon as the new ID was avaialbe.<br>
&gt;<br>
&gt; =A0The current list of Last Call Comments resoltion is also avaiable a=
t:<br>
&gt; =A0<a href=3D"http://www.pi.nu/%7Eloa/cc-cv-rdi-Last-Call-Comments.xls=
" target=3D"_blank">http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls<=
/a><br>
&gt;<br>
&gt; =A0The list of issues that the authors kept very carefully, shows with=
out<br>
&gt;doubt<br>
&gt; =A0that no comments been ignored.<br>
&gt;<br>
&gt; =A0Loa<br>
&gt; =A0mpls wg document shepherd<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
</div></div><div class=3D"im">&gt;-----Original Message-----<br>
&gt;From: David Allan I [mailto:<a href=3D"mailto:david.i.allan@ericsson.co=
m">david.i.allan@ericsson.com</a>]<br>
&gt;Sent: quarta-feira, 6 de Julho de 2011 14:58<br>
</div><div class=3D"im">&gt;To: Rui Costa; <a href=3D"mailto:ietf@ietf.org"=
>ietf@ietf.org</a>; IETF-Announce<br>
&gt;Cc: <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br>
</div><div class=3D"im">&gt;Subject: RE: [mpls] Last Call: &lt;draft-ietf-m=
pls-tp-cc-cv-rdi-05.txt&gt;<br>
(Proactive Connectivity Verification, Continuity Check and Remote Defect<br=
>
</div><div class=3D"im">indication for MPLS Transport Profile) to Proposed =
Standard<br>
&gt;<br>
&gt;Hi Rui:<br>
&gt;<br>
&gt;The comments were not ignored, the resolution of the Q10 comments as we=
ll as<br>
</div>those collected from the MPLS WG was presented at the last IETF. My s=
preadsheet<br>
<div class=3D"im">from which that report was generated and has been augment=
ed to include the BFD<br>
</div>WG comments is available at <a href=3D"http://www.pi.nu/%7Eloa/cc-cv-=
rdi-Last-Call-Comments" target=3D"_blank">http://www.pi.nu/~loa/cc-cv-rdi-L=
ast-Call-Comments</a>.<br>
xls<br>
&gt;<br>
<div class=3D"im">&gt;So you know...<br>
&gt;Dave<br>
&gt;<br>
&gt;<br>
&gt;-----Original Message-----<br>
</div><div class=3D"im">&gt;From: <a href=3D"mailto:ietf-bounces@ietf.org">=
ietf-bounces@ietf.org</a> [mailto:<a href=3D"mailto:ietf-bounces@ietf.org">=
ietf-bounces@ietf.org</a>] On Behalf Of Rui<br>
Costa<br>
&gt;Sent: segunda-feira, 4 de Julho de 2011 23:03<br>
</div>&gt;To: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; IETF-Anno=
unce<br>
&gt;Cc: <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br>
&gt;Subject: RE: [mpls] Last Call: &lt;draft-ietf-mpls-tp-cc-cv-rdi-05.txt&=
gt;<br>
<div class=3D"im">(Proactive Connectivity Verification, Continuity Check an=
d Remote Defect<br>
</div>indication for MPLS Transport Profile) to Proposed Standard<br>
<div class=3D"im">&gt;<br>
&gt;IMHO and for the record:<br>
&gt;<br>
&gt;ITU-T comments regarding this draft haven&#39;t been discussed with ITU=
-T but<br>
were simply ignored. No LS describing these comments&#39; resolution was se=
nt.<br>
&gt;<br>
</div><div class=3D"im">&gt;Several service providers regarded this draft a=
s not meeting their transport<br>
networks&#39; needs.<br>
&gt;<br>
</div><div class=3D"im">&gt;[The v03 draft was published in Feb and went to=
 WG LC.<br>
&gt;The v04 draft addressing WG LC comments was published on the 28th June =
(same<br>
date as the proto write-up).<br>
&gt;When was the WG LC launched, to verify LC comments resolution?]<br>
&gt;<br>
&gt;Regards,<br>
&gt;Rui<br>
&gt;<br>
&gt;<br>
&gt;-----Original Message-----<br>
&gt;From: <a href=3D"mailto:mpls-bounces@ietf.org">mpls-bounces@ietf.org</a=
> [mailto:<a href=3D"mailto:mpls-bounces@ietf.org">mpls-bounces@ietf.org</a=
>] On Behalf Of The<br>
IESG<br>
&gt;Sent: quinta-feira, 30 de Junho de 2011 14:47<br>
&gt;To: IETF-Announce<br>
&gt;Cc: <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br>
</div>&gt;Subject: [mpls] Last Call: &lt;draft-ietf-mpls-tp-cc-cv-rdi-05.tx=
t&gt; (Proactive<br>
<div class=3D"im">Connectivity Verification, Continuity Check and Remote De=
fect indication for<br>
MPLS Transport Profile) to Proposed Standard<br>
&gt;<br>
&gt;<br>
</div><div><div></div><div class=3D"h5">&gt;The IESG has received a request=
 from the Multiprotocol Label Switching WG<br>
&gt;(mpls) to consider the following document:<br>
&gt;- &#39;Proactive Connectivity Verification, Continuity Check and Remote=
<br>
&gt; =A0 Defect indication for MPLS Transport Profile&#39;<br>
&gt; =A0&lt;draft-ietf-mpls-tp-cc-cv-rdi-05.txt&gt; as a Proposed Standard<=
br>
&gt;<br>
&gt;The IESG plans to make a decision in the next few weeks, and solicits<b=
r>
&gt;final comments on this action. Please send substantive comments to the<=
br>
&gt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 201=
1-07-14. Exceptionally, comments may be<br>
&gt;sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In =
either case, please retain the<br>
&gt;beginning of the Subject line to allow automated sorting.<br>
&gt;<br>
&gt;Abstract<br>
&gt;<br>
&gt; =A0 Continuity Check, Proactive Connectivity Verification and Remote<b=
r>
&gt; =A0 Defect Indication functionalities are required for MPLS-TP OAM.<br=
>
&gt;<br>
&gt; =A0 Continuity Check monitors the integrity of the continuity of the<b=
r>
&gt; =A0 label switched path for any loss of continuity defect. Connectivit=
y<br>
&gt; =A0 verification monitors the integrity of the routing of the label<br=
>
&gt; =A0 switched path between sink and source for any connectivity issues.=
<br>
&gt; =A0 Remote defect indication enables an End Point to report, to its<br=
>
&gt; =A0 associated End Point, a fault or defect condition that it detects =
on<br>
&gt; =A0 a pseudo wire, label switched path or Section.<br>
&gt;<br>
&gt; =A0 This document specifies methods for proactive continuity check,<br=
>
&gt; =A0 continuity verification, and remote defect indication for MPLS-TP<=
br>
&gt; =A0 label switched paths, pseudo wires and Sections using Bidirectiona=
l<br>
&gt; =A0 Forwarding Detection.<br>
&gt;<br>
&gt;<br>
&gt;The file can be obtained via<br>
&gt;<a href=3D"http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi=
/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-=
cv-rdi/</a><br>
&gt;<br>
&gt;IESG discussion can be tracked via<br>
&gt;<a href=3D"http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi=
/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-=
cv-rdi/</a><br>
&gt;<br>
&gt;<br>
&gt;No IPR declarations have been submitted directly on this I-D.<br>
&gt;_______________________________________________<br>
</div></div><div class=3D"im">&gt;mpls mailing list<br>
&gt;<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br>
&gt;<a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank=
">https://www.ietf.org/mailman/listinfo/mpls</a><br>
&gt;<br>
&gt;<br>
</div>&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"_blank=
">https://www.ietf.org/mailman/listinfo/ietf</a><br>
<div><div></div><div class=3D"h5">&gt;<br>
<br>
<br>
_______________________________________________<br>
mpls mailing list<br>
<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/mpls</a><br>
</div></div></blockquote></div><br>

--0023547c8c15dcfe0c04a7feb084--

From hideki.endo.es@hitachi.com  Thu Jul 14 04:37:18 2011
Return-Path: <hideki.endo.es@hitachi.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25F5921F86A0 for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 04:37:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.41
X-Spam-Level: 
X-Spam-Status: No, score=0.41 tagged_above=-999 required=5 tests=[AWL=-0.500,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, SUBJ_RE_NUM=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 7a6cw7BAJSo7 for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 04:37:17 -0700 (PDT)
Received: from mail9.hitachi.co.jp (mail9.hitachi.co.jp [133.145.228.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7791121F8652 for <ietf@ietf.org>; Thu, 14 Jul 2011 04:37:17 -0700 (PDT)
Received: from mlsv6.hitachi.co.jp (unknown [133.144.234.166]) by mail9.hitachi.co.jp (Postfix) with ESMTP id 4D38537C85 for <ietf@ietf.org>; Thu, 14 Jul 2011 20:37:15 +0900 (JST)
Received: from mfilter01.hitachi.co.jp by mlsv6.hitachi.co.jp (8.13.1/8.13.1) id p6EBbFQC018049; Thu, 14 Jul 2011 20:37:15 +0900
Received: from vshuts3.hitachi.co.jp (vshuts3.hitachi.co.jp [10.201.6.72]) by mfilter01.hitachi.co.jp (Switch-3.3.4/Switch-3.3.4) with ESMTP id p6EBbE29026226 for <ietf@ietf.org>; Thu, 14 Jul 2011 20:37:15 +0900
X-AuditID: b753bd60-a46c9ba000003bac-d8-4e1ed4ea8967
Received: from gmml25.itg.hitachi.co.jp (unknown [158.213.165.145]) by vshuts3.hitachi.co.jp (Symantec Mail Security) with ESMTP id 458BA77426C for <ietf@ietf.org>; Thu, 14 Jul 2011 20:37:14 +0900 (JST)
Received: from [127.0.0.1] by gmml25.itg.hitachi.co.jp (AIX5.2/8.11.6p2/8.11.0) id p6EBbEx24789168; Thu, 14 Jul 2011 20:37:14 +0900
Message-Type: Multiple Part
MIME-Version: 1.0
Message-ID: <XNM1$7$0$0$$6$1$2$A$5001646U4e1ed4c3@hitachi.com>
Content-Type: text/plain; charset=us-ascii
To: <ietf@ietf.org>
From: <hideki.endo.es@hitachi.com>
Date: Thu, 14 Jul 2011 20:36:51 +0900
References: <20110630134642.1281.3095.idtracker@ietfa.amsl.com> <XNM1$7$0$0$$6$1$2$A$5001645U4e1ed16c@hitachi.com>
Priority: normal
Importance: normal
Subject: Re[2]: [mpls] Last Call:<draft-ietf-mpls-tp-cc-cv-rdi-05.txt>(Proactive Connecti
X400-Content-Identifier: X4E1ED4C300000M
X400-MTS-Identifier: [/C=JP/ADMD=HITNET/PRMD=HITACHI/;gmml2811071420363587G]
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
X-Mailman-Approved-At: Thu, 14 Jul 2011 08:19:00 -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, 14 Jul 2011 11:37:18 -0000

Sorry for resending.

The changes in this version have massive impact for CC/CV/RDI implementation.
We, venders, have kept making efforts on interoperability test again and again.
These changes spoil this effort.

Especially, revival of Poll/Final sequence doesn't make sense.
Originally, in my understanding, Poll/Final sequence was excluded from this draft
to avoid making HW implementation difficult. 

Even though it was difficult to change CC interval arbitrary, 
the problem should be solved by defining how to transit DOWN/INIT state to UP state.

The direction which reached consensus once should NOT be changed easily
in order to respond to the market requirements.

IMO, such major changes should NOT be added right before becoming RFC.

I found at least four major/minor changes as follows;
1)Revival of Poll/Final sequence
2)Change of MEP ID formats
3)Change of Diag. Code
4)Change of CV interleaved definition

BR,
Hideki


>
>>
>>The IESG has received a request from the Multiprotocol Label Switching WG
>>(mpls) to consider the following document:
>>- 'Proactive Connectivity Verification, Continuity Check and Remote
>>   Defect indication for MPLS Transport Profile'
>>  <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally, comments may be
>>sent to iesg@ietf.org instead. In either case, please retain the
>>beginning of the Subject line to allow automated sorting.
>>
>>Abstract
>>
>>   Continuity Check, Proactive Connectivity Verification and Remote
>>   Defect Indication functionalities are required for MPLS-TP OAM.
>>
>>   Continuity Check monitors the integrity of the continuity of the
>>   label switched path for any loss of continuity defect. Connectivity
>>   verification monitors the integrity of the routing of the label
>>   switched path between sink and source for any connectivity issues.
>>   Remote defect indication enables an End Point to report, to its
>>   associated End Point, a fault or defect condition that it detects on
>>   a pseudo wire, label switched path or Section.
>>
>>   This document specifies methods for proactive continuity check,
>>   continuity verification, and remote defect indication for MPLS-TP
>>   label switched paths, pseudo wires and Sections using Bidirectional
>>   Forwarding Detection.
>>
>>
>>The file can be obtained via
>>http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>>
>>IESG discussion can be tracked via
>>http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>>
>>
>>No IPR declarations have been submitted directly on this I-D.
>>_______________________________________________
>>mpls mailing list
>>mpls@ietf.org
>>https://www.ietf.org/mailman/listinfo/mpls
>>
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls
>

From joelja@bogus.com  Thu Jul 14 08:22:33 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 71FF121F8CB7 for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 08:22:33 -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 zL-ky7-iAg5z for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 08:22:29 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1A30721F8CBF for <ietf@ietf.org>; Thu, 14 Jul 2011 08:22:09 -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 p6EFLwvX033212 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 14 Jul 2011 15:21:58 GMT (envelope-from joelja@bogus.com)
Subject: Re: Confidentiality notices on email messages
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <4E1EEE0F.7090209@dcrocker.net>
Date: Thu, 14 Jul 2011 08:21:58 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E69EAC8E-5F41-435E-8CDD-BA71CC6411CB@bogus.com>
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <CAP0PwYYmLxPSoPvUqYOO_y=Hdn9vBSTRC5ax4wnjzE1SD1+aLg@mail.gmail.com> <4E1EEE0F.7090209@dcrocker.net>
To: dcrocker@bbiw.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]); Thu, 14 Jul 2011 15:21:59 +0000 (UTC)
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, 14 Jul 2011 15:22:33 -0000

On Jul 14, 2011, at 6:24 AM, Dave CROCKER wrote:

>=20
>=20
> On 7/12/2011 2:36 PM, Jorge Contreras wrote:
>> You may want to refer to Section 5.2 of RFC 5378, which addresses =
this issue:
>>=20
>> "Each Contributor agrees that any statement in a Contribution, =
whether generated
>> automatically or otherwise, that states or implies that the =
Contribution is
>> confidential or subject to any privilege, can be disregarded for all =
purposes,
>> and will be of no force or effect."
>=20
>=20
> Jorge,
>=20
> It's excellent that the issue was covered in the RFC.
>=20
> My question is how the contents of that RFC can be binding on random =
IETF participants?

Everyone on this list has be asked to and has accepted the note well.

> I doubt many folk even know about the item, even if they know about =
the RFC and I don't see how they have agreed to those terms.

http://www.ietf.org/about/note-well.html

> Has the force of this been tested?  That is, when there is a conflict =
between the conditions imposed by one of these email attachments and the =
terms in RFC 5378, is there equivalent legal precedent for the RFC to =
win?
>=20
> Thanks.
>=20
> d/
>=20
> --=20
>=20
>  Dave Crocker
>  Brandenburg InternetWorking
>  bbiw.net
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From vesely@tana.it  Thu Jul 14 08:28:52 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 002B021F85E3 for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 08:28:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.842
X-Spam-Level: 
X-Spam-Status: No, score=-4.842 tagged_above=-999 required=5 tests=[AWL=-0.123, 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 JqRRIaOa1t5d for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 08:28:47 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 5739021F85E2 for <ietf@ietf.org>; Thu, 14 Jul 2011 08:28:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1310657325; bh=hWb8v6KJmewjdkdZDCUCNTm+k9zBs+/G6Ow0eXZsBYo=; l=1116; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=LrIQayXCjCJscq5K/IWeCsVA1LvqLSax8jJ8hB/HbdF0INY0xQ2HOoBirjpNGOfFf ZwvImEKDpcpTPmIceAtT302sFARDBdnlLVLceSoNZeKW3FwOPf/yoveagKs5SsadLq v8s34e+SsbKYuinh5dy0sQXwj/LC1v8TV97laLdQ=
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; Thu, 14 Jul 2011 17:28:45 +0200 id 00000000005DC035.000000004E1F0B2D.00005C1A
Message-ID: <4E1F0B2C.3070401@tana.it>
Date: Thu, 14 Jul 2011 17:28:44 +0200
From: Alessandro Vesely <vesely@tana.it>
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: ietf@ietf.org
Subject: Re: Confidentiality notices on email messages
References: <20110714014835.9480.qmail@joyce.lan>
In-Reply-To: <20110714014835.9480.qmail@joyce.lan>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jul 2011 15:28:52 -0000

On 14/Jul/11 03:48, John Levine wrote:
>>Yes, and perhaps disclaimers/confidentiality notices should be
>>standardized with their own MIME type to make automatic processing
>>easier so receivers of this kind of notice (mailing-list or other)
>>can respect the wishes of the sender.
> 
> That respect would of course be demonstrated by rejecting or
> discarding the mail unread, to avoid any possibility that it could
> fall into the wrong hands.

Yes, with the possible exception of recipients deploying a Treacherous
Computing environment that includes checks against forwarding or
replying with non fair use quotations of confidential messages.

> PS: Perhaps I should propose a revised RFC 5617 adding dkim=confidential.

One can sign the "Sensitivity" header field defined by RFC 2156.  It
can have the values "Personal" / "Private" / "Company-Confidential".

However, I received some messages bearing a confidentiality notice but
missing this field entirely.  Even the TC system above could hardly
cope with such inconsistent settings.  Do notices still retain any
legal value in such cases?

From hextic@gmail.com  Thu Jul 14 09:38:01 2011
Return-Path: <hextic@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ACDD21F8C8E for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 09:38:01 -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 UBxbHYec3voc for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 09:38:00 -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 C6E5621F899F for <ietf@ietf.org>; Thu, 14 Jul 2011 09:38:00 -0700 (PDT)
Received: by gxk19 with SMTP id 19so204157gxk.31 for <ietf@ietf.org>; Thu, 14 Jul 2011 09:38:00 -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=uY3c24Mj/Y5OR2Lh+2LOGDYl+GkU7j/Dc4g7JLs6gdc=; b=W5891Ir2zTZ+jze2XKsJ+y9FSwN0a5UWGI967SMkz46PN464xe21FGNnpKX5WJZYpN DmBSoafZIBTVsIA6Vs+nag/1mKLJvN6wOxHWis//bEwVZD6u02/wx7LdefLm+3oz4Fnh vZDhbFTUjD4KFx99JF4VQw6FW19s742aRZu1Y=
Received: by 10.150.132.16 with SMTP id f16mr2544354ybd.21.1310661480114; Thu, 14 Jul 2011 09:38:00 -0700 (PDT)
Received: from [10.92.239.92] (mobile-166-137-139-254.mycingular.net [166.137.139.254]) by mx.google.com with ESMTPS id k7sm810826ybm.29.2011.07.14.09.37.57 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 14 Jul 2011 09:37:58 -0700 (PDT)
References: <20110714014835.9480.qmail@joyce.lan> <4E1F0B2C.3070401@tana.it>
In-Reply-To: <4E1F0B2C.3070401@tana.it>
Mime-Version: 1.0 (iPhone Mail 8C148)
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
Message-Id: <2A06ADAE-70E2-4D0C-9809-66E01943B68E@gmail.com>
X-Mailer: iPhone Mail (8C148)
From: Will McAfee <hextic@gmail.com>
Subject: Re: Confidentiality notices on email messages
Date: Thu, 14 Jul 2011 12:37:49 -0400
To: Alessandro Vesely <vesely@tana.it>
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, 14 Jul 2011 16:38:01 -0000

They don't have legal value, period.

Sent from my iPhone

On Jul 14, 2011, at 11:28 AM, Alessandro Vesely <vesely@tana.it> wrote:

> On 14/Jul/11 03:48, John Levine wrote:
>>> Yes, and perhaps disclaimers/confidentiality notices should be
>>> standardized with their own MIME type to make automatic processing
>>> easier so receivers of this kind of notice (mailing-list or other)
>>> can respect the wishes of the sender.
>> 
>> That respect would of course be demonstrated by rejecting or
>> discarding the mail unread, to avoid any possibility that it could
>> fall into the wrong hands.
> 
> Yes, with the possible exception of recipients deploying a Treacherous
> Computing environment that includes checks against forwarding or
> replying with non fair use quotations of confidential messages.
> 
>> PS: Perhaps I should propose a revised RFC 5617 adding dkim=confidential.
> 
> One can sign the "Sensitivity" header field defined by RFC 2156.  It
> can have the values "Personal" / "Private" / "Company-Confidential".
> 
> However, I received some messages bearing a confidentiality notice but
> missing this field entirely.  Even the TC system above could hardly
> cope with such inconsistent settings.  Do notices still retain any
> legal value in such cases?
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From petithug@acm.org  Thu Jul 14 09:44:46 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 8FF5F21F8D1D for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 09:44:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.589
X-Spam-Level: 
X-Spam-Status: No, score=-102.589 tagged_above=-999 required=5 tests=[AWL=0.011, 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 1DaP37naM788 for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 09:44:41 -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 8DAF821F8D1E for <ietf@ietf.org>; Thu, 14 Jul 2011 09:44:41 -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 066802199E; Thu, 14 Jul 2011 18:43:08 +0200 (CEST)
Message-ID: <4E1F1CF7.4050907@acm.org>
Date: Thu, 14 Jul 2011 09:44:39 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110626 Iceowl/1.0b2 Icedove/3.1.11
MIME-Version: 1.0
To: Alessandro Vesely <vesely@tana.it>
Subject: Re: Confidentiality notices on email messages
References: <20110714014835.9480.qmail@joyce.lan> <4E1F0B2C.3070401@tana.it>
In-Reply-To: <4E1F0B2C.3070401@tana.it>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jul 2011 16:44:46 -0000

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

On 07/14/2011 08:28 AM, Alessandro Vesely wrote:
> On 14/Jul/11 03:48, John Levine wrote:
>>> Yes, and perhaps disclaimers/confidentiality notices should be
>>> standardized with their own MIME type to make automatic processing
>>> easier so receivers of this kind of notice (mailing-list or other)
>>> can respect the wishes of the sender.
>>
>> That respect would of course be demonstrated by rejecting or
>> discarding the mail unread, to avoid any possibility that it could
>> fall into the wrong hands.
> 
> Yes, with the possible exception of recipients deploying a Treacherous
> Computing environment that includes checks against forwarding or
> replying with non fair use quotations of confidential messages.
> 
>> PS: Perhaps I should propose a revised RFC 5617 adding dkim=confidential.
> 
> One can sign the "Sensitivity" header field defined by RFC 2156.  It
> can have the values "Personal" / "Private" / "Company-Confidential".
> 
> However, I received some messages bearing a confidentiality notice but
> missing this field entirely.  Even the TC system above could hardly
> cope with such inconsistent settings.

1. If an email received contains a Sensivity header with Confidential, Private
or Personal, the email is rejected.

2. Else, with techniques similar to spam filtering, a process can then test if
the email may contain a legal notice (perhaps Spamassassin can be configured to
do this - I am not a specialist).  If such notice is detected, and there is no
Sensivity header the email is bounced back with a text similar to this:

"We automatically detected that your email may contain a legal notice, but we
have no way to be sure that this notice is compliant with our rules, but we
cannot take the legal risk to accept it against the wishes of your employer.
Please contact your IT department and ask them to add a Sensivity header to the
emails sent by your organization, which should be even easier than adding the
legal notice."

3. Else, if a notice is detected and there is a Sensivity=public header, then
the email is accepted.

4. Else, if no notice is detected, the email is accepted.


> Do notices still retain any
> legal value in such cases?

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

iEYEARECAAYFAk4fHPUACgkQ9RoMZyVa61f1HwCcDCWWIade84CPrOGglYUOS5Jk
UPMAn0eETDcMfjPq6do1Jb92eWGud+ls
=dlvr
-----END PGP SIGNATURE-----

From stpeter@stpeter.im  Thu Jul 14 10:23:03 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 2430321F8DA3 for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 10:23:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.583
X-Spam-Level: 
X-Spam-Status: No, score=-102.583 tagged_above=-999 required=5 tests=[AWL=0.016, 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 oK+ZzK7ltH9A for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 10:22:55 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 21D5621F8DA2 for <ietf@ietf.org>; Thu, 14 Jul 2011 10:22:55 -0700 (PDT)
Received: from dhcp-64-101-72-201.cisco.com (unknown [64.101.72.201]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id B023A410EE; Thu, 14 Jul 2011 11:23:20 -0600 (MDT)
Message-ID: <4E1F25ED.6060500@stpeter.im>
Date: Thu, 14 Jul 2011 11:22:53 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: Second Last Call: <draft-hammer-hostmeta-16.txt> (Web Host Metadata) to Proposed Standard -- feedback
References: <11CBFBA2-434B-43FC-90C4-DADBACB49226@mnot.net> <4E1CA248.7060009@stpeter.im> <3110098B-5515-4E7A-84A4-522925593FA2@mnot.net>
In-Reply-To: <3110098B-5515-4E7A-84A4-522925593FA2@mnot.net>
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org IETF" <ietf@ietf.org>, 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: Thu, 14 Jul 2011 17:23:03 -0000

Mark, I will work with the authors on proposed wording to describe the
context in which this technology is most applicable, and post again once
we've done that.

On 7/13/11 5:35 AM, Mark Nottingham wrote:
> Personally, I think Informational is most appropriate (and probably easier), but a paragraph or two of context, as well as corresponding adjustments, would work as well. 
> 
> Cheers,
> 
> 
> On 13/07/2011, at 5:36 AM, Peter Saint-Andre wrote:
> 
>> On 6/21/11 11:08 PM, Mark Nottingham wrote:
>>> 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.
>>
>> How about publishing it on the standards track but not as a general
>> mechanism (i.e., why not clarify when it is and is not appropriate)?
>>
>> Clearly, both service providers (Google, Yahoo, etc.) and spec authors
>> (draft-hardjono-oauth-dynreg-00, draft-hardjono-oauth-umacore-00) have
>> found hostmeta somewhat useful in certain contexts.
>>
>> RFC 2026 says:
>>
>>   A Proposed Standard specification is generally stable, has resolved
>>   known design choices, is believed to be well-understood, has received
>>   significant community review, and appears to enjoy enough community
>>   interest to be considered valuable.
>>
>> and:
>>
>>   Usually, neither implementation nor operational experience is
>>   required for the designation of a specification as a Proposed
>>   Standard.  However, such experience is highly desirable, and will
>>   usually represent a strong argument in favor of a Proposed Standard
>>   designation.
>>
>> The spec seems to be stable at this point, it's received significant
>> review, people seem to understand what it does and how it works, it's
>> had both implementation and operational experience, and it appears to
>> enjoy enough community interest to be considered valuable in certain
>> contexts. I also think it has resolved the design choices and solved the
>> requirements that it set out to solve, although you might be right that
>> it doesn't solve all of the problems that a more generic metadata
>> framework would need to solve.
>>
>> As a result, it seems like a fine candidate for Proposed Standard, i.e.,
>> an entry-level document on the standards track that might be modified or
>> even retracted based on further experience.
>>
>>> 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. 
>>
>> Again, perhaps we need to clarify that it is not necessarily a general
>> component of the web architecture, although it can be used to solve more
>> specific problems.
>>
>>> 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.
>>
>> As discussed in responses to your message, XRD seems to have been an
>> appropriate tool for the job in this case. Whether XRD, too, is really a
>> general component of the web architecture is another question.
>>
>>> * 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.
>>
>> That could be something to work on if and when folks try to advance this
>> technology to the next maturity level (currently Draft Standard).
>>
>>> * Scope of hosts -- The document doesn't crisply define what a "host"
>>> is.
>>
>> This seems at least somewhat well-defined:
>>
>>   a "host" is not a single resource but the entity
>>   controlling the collection of resources identified by Uniform
>>   Resource Identifiers (URI) with a common URI host [RFC3986].
>>
>> That is, it references Section 3.2.2 of RFC 3986, which defines "host"
>> with some precision (albeit perhaps not "crisply").
>>
>>> * 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.
>>
>> It would be helpful to hear from folks who have deployed hostmeta to
>> hear if they have run into any operational issues of the kind you
>> describe here.
>>
>>> * 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.
>>>
>>> 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.
>>
>> That sounds like good input to a more generic approach. Many discovery
>> protocols do seem to have an inherent chattiness about them, but you
>> might be right that ideally the round trips could be kept to a minimum.
>>
>>> 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.
>>
>> Again, I think some clarifying language about the applicability of the
>> technology is in order.
>>
>>> 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.
>>
>> And my apologies for taking so long to reply.
>>
>> Peter
>>
>> -- 
>> Peter Saint-Andre
>> https://stpeter.im/
>>
>>

From RCosta@ptinovacao.pt  Thu Jul 14 10:32:58 2011
Return-Path: <RCosta@ptinovacao.pt>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9936A21F8BD7; Thu, 14 Jul 2011 10:32:58 -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_31=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 po4UTSxi31XY; Thu, 14 Jul 2011 10:32:54 -0700 (PDT)
Received: from owa.ptinovacao.pt (webmail.ptinovacao.pt [194.65.138.99]) by ietfa.amsl.com (Postfix) with ESMTP id 5C42121F8BCF; Thu, 14 Jul 2011 10:32:53 -0700 (PDT)
Received: from INOAVREX11.ptin.corpPT.com ([10.112.15.121]) by inoavrcas01.ptin.corpPT.com ([10.112.15.99]) with mapi; Thu, 14 Jul 2011 18:32:51 +0100
From: Rui Costa <RCosta@ptinovacao.pt>
To: David Allan I <david.i.allan@ericsson.com>
Date: Thu, 14 Jul 2011 18:32:48 +0100
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity Verification, Continuity Check and Remote Defect indication for MPLS	Transport	Profile) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive	Connectivity Verification, Continuity Check and Remote Defect indication for MPLS	Transport	Profile) to Proposed Standard
Thread-Index: Acw3LJ0GTOqQfPcUQOGUhgK/1kXgjgDPfXWgACJLxEAApIjzAABwiuqg
Message-ID: <52981DB05D3C5247A12D0AEE309F3CC201ED4D53BBBB@INOAVREX11.ptin.corpPT.com>
References: <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B6BC@INOAVREX11.ptin.corpPT.com> <60C093A41B5E45409A19D42CF7786DFD522135449A@EUSAACMS0703.eamcs.ericsson.se>
In-Reply-To: <60C093A41B5E45409A19D42CF7786DFD522135449A@EUSAACMS0703.eamcs.ericsson.se>
Accept-Language: pt-PT
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: pt-PT
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ietf@ietf.org" <ietf@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: Thu, 14 Jul 2011 17:32:58 -0000

David,

T-MPLS rose from MPLS/IP's OAM blanks. Our main interest on it is the simpl=
e/reliable OAM we had in SDH but lost in MPLS/IP. Otherwise, the work in T-=
MPLS or MPLS-TP would be rather pointless.
ITU-T was historically the right place to define such OAM. So, our interest=
 started with ITU-T's work in T-MPLS and not when IETF joined.


We value IETF's work, and in 2008, when the IETF rose doubts about future i=
nteroperability between T-MPLS and MPLS/IP (and the "danger to the internet=
"), even though all T-MPLS Recommendations were approved and the OAM one wa=
s ready for approval, a decision was made to listen carefully to MPLS/IP's =
top experts' input.


IETF's unilateral decision to select BFD was IMHO a surprise: being a prima=
ry goal in T-MPLS, i'd assume OAM definition was ITU-T's responsibility/exp=
ertise or at least a compromise between the 2 SDOs. ITU-T's not just a boil=
erplate stamper.
Hearing that "the decision was expressed in mpls-tp-analysis draft" was ano=
ther surprise: among the possible ways, the document showed, IMHO, 1731 as =
the closest one to requirements.


We don't need a requirement to agree on reusing as most as possible MPLS an=
d PW: it's common sense. However, it can't distract us from primary goals.


"The issue is not code point, which is the trivial part. It is reuse of the=
 majority of the implementation. Again, pretty basic."
In other words, the problem is not backwards compatibility, (ergo the "dang=
er to the internet" problem never really existed) but maintaining particula=
r deployed platforms. If we had to convert cars into planes, we couldn't sa=
y "to reuse the implementation, we can't add wings": they wouldn't fly.
I'm used to FW/HW development and i don't share your cost/simplicity view. =
(Please check other LC responses on this particular point.) I know field ne=
twork support and think you'd change your opinion if you had to work on 24h=
 field network support.



I agree with you that other opinions exist, counting not only manufacturers=
 but also operators. On the operators that don't agree with you are certain=
ly clients of yours. It's none of my business that you view their opinions =
as "grumblings", but that's far from describing the polls' results in the F=
eb2011 WG3 and SG15 plenaries, showing a minority sharing your view, and th=
at, although those not subscribing it tolerate its evolution, you don't the=
irs.
Operators and their clients are the ones that, at the end of the day, pay f=
or networks. From the above, it'll be IMHO impossible to understand if thes=
e Recommendations don't take into account these "grumblers'" view, other th=
an the obsession of those insisting to sell swiss knifes to those who just =
want sharp scalpels. Why don't we call that also "not constructive"?
"[R:] IMHO, between your MPLS-TP view and MPLS/IP, it becomes more and more=
 difficult to tell which is which.
[D:]That is because MPLS-TP is not a new techology, it is an addition to th=
e entire MPLS protocol suite."
Yes, i understand your view, David, but i'm sure you and i don't subscribe =
this one:
"The creatures outside looked from pig to man, and from man to pig, and fro=
m pig to man again; but already it was impossible to say which was which".

Hope this helps. My comrade cents,
Rui



-----Original Message-----
From: David Allan I [mailto:david.i.allan@ericsson.com]
Sent: sexta-feira, 8 de Julho de 2011 17:13
To: Rui Costa; Stewart Bryant
Cc: erminio.ottone_69@libero.it; mpls@ietf.org; ietf@ietf.org; IETF-Announc=
e
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proac=
tive Connectivity Verification, Continuity Check and Remote Defect indicati=
on for MPLS Transport Profile) to Proposed Standard

Rui:

You wrote:

>Reading something, keeping it on record, without effect in the draft and "=
ignoring comments" have IMHO similar outcomes. As author of the draft you a=
re free to do it. These standards have a great impact
>in our work, so i'm also free to write what i did.

Numerous comments did have effect on the draft and those that didn't were e=
ither simply not actionable, were rhetorical or not constructive, and a few=
 had to be balanced against comments coming from the MPLS & BFD WGs. I woul=
d translate "ingored" or "without effect" to "did not get one'e way". In th=
e standards process it happens.

>My technical concerns regarding this draft were expressed...
>...in the (ITU-T -> IETF, Feb/2011) liaison regarding it (LS281, i believe=
);
>...in operators' meetings' that took place during ITU-T's Feb/2011 plenary=
 meeting;

I and the WG don't really have access to private grumblings.

Lots of other opinions were expressed as well, and they did not all agree w=
ith you.

>Some:
>CC/CV
>I don't understand the need for 2 types of packets: a single type allows C=
C; mismatching identifiers in the same CC packets allow CV.
>Besides adding complexity, we whether always activate both or potentiate u=
ndetected mismerges.

OK, lets walk through this.

We want CV all the time so that any misconectivity can be detected, but on =
the list it was expressed that the group did not want the overhead of proce=
ssing the source MEP TLV in every packet in order to achieve this. We could=
 carry it in every packet and have the receiver simply ignore most of them,=
 but then that would make the defect entry criteria compeltely random and t=
he exit criteria unreliable as well, not really a good design. Hence they a=
re separated using different ACH code points and the receiver is obliged to=
 process every source MEP TLV it receives. I hope this is clear.

>(BTW: can't understand how we propose one ACH codepoint to CC, another for=
 CV, [counting other drafts, another for frame loss ...] but don't consider=
 assigning 1 single ACH protocol identifier codepoint >as requested by ITU-=
T)

Because that puts you into two protocol ID demultiplexing steps per OAM PDU=
 recevied to determine the intended function. Hence COSTS MORE. That is pre=
tty basic...

> Uni P2P / P2MP
> I can't see how BFD will support unidir and hence P2MP other than...
> ...eliminating the session "state variable" (down, init, up), aiming just=
 the state variables we really need, bringing us to something similar to 17=
31, eventually with other bits on the wire or...
> ...using IP to create the reverse way, which we cannot assume per require=
ments;
> Will we create a complete different tool for that?
> (BFD's B=3D"bidirectional")

I would not go so far as to say "similar to 1731", there is actually a lot =
of difference under the hood. As for uni-directional BFD, that is a BFD WG =
problem at the moment.

> Provisioning list
> This is an MPLS profile/subset (and i heard) achievable through a particu=
lar configuration. So, i expect each draft-ietf-mpls-TP-* to focus on that =
profile/configuration. However, i keep seeing
> references f.i. to IP encapsulations unexpected under TP's OAM.
> I don't thus understand what the aim is: do we expect this in TP, are we =
talking about MPLS in general?... The TP profile is never quite delimited.
> Does chapter 4 contain ALL the configurable parameters list agreed to pro=
vide in the comparison session?

It should. As for encapsulations, unless TP is in a complete island not con=
nected to anything (which as a network is rather useless) it will be expect=
ed to interoperate with the rest of the MPLS architecture, and the stated i=
ntention of tool development was that what resulted was applicable to the b=
roader MPLS architecture. Which means backwards compatiblity and procedures=
 for interoperation.

> Backwards compatibility
> This was the main argument risen to ground MPLS-TP OAM on BFD. It's not a=
 better argument than grounding MPLS-TP OAM on 1731 due to its ETH deployme=
nt plus coherence with SDH, OTN, as defended by ITU-T.
> For reasons like the above, however, MPLS-TP BFD won't be backwards compa=
tible with previous BFD (even considering just CC/CV). They don't even shar=
e the same codepoint.

The issue is not code point, which is the trivial part. It is reuse of the =
majority of the implementation. Again, pretty basic.

>Simplicity
>Whether we look to PDH, SDH, OTN or ETH, ITU-T's approach to CC is simpler=
: in each flow, a standard defined nr of constant heartbeat signals (with s=
tandard constant or provisioned period - no
>auto/negotiated -) means OK. A standard defined number of misses means los=
t Rx connection. An RDI, the only articulation between Rx and Tx flows, mea=
ningful in bidirectional applications, allows each
>pear to identify Tx problems.
>This OAM simplicity is the key for reliable fail finger pointing, performa=
nce reports and protection. Also to allow scaling, more implementation oppo=
rtunities/manufacturers, which is valuable for
>operators.

Well IMO there was not a lot of interest in T-MPLS until the IETF was going=
 to re-define it and make it compatible with IP/MPLS. So there was an indus=
try wide "design intent" implied here.

> IMHO, between your MPLS-TP view and MPLS/IP, it becomes more and more dif=
ficult to tell which is which.

That is because MPLS-TP is not a new techology, it is an addition to the en=
tire MPLS protocol suite.

Hope this helps
D









-----Original Message-----
From: David Allan I [mailto:david.i.allan@ericsson.com]
Sent: quarta-feira, 6 de Julho de 2011 19:25
To: erminio.ottone_69@libero.it; Rui Costa; ietf@ietf.org; IETF-Announce
Cc: mpls@ietf.org
Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>=
 (Proactive Connectivity Verification, Continuity Check and Remote Defect i=
ndication for MPLS Transport Profile) to Proposed Standard

Hi Erminio:

<snipped>
>Several service providers regarded this draft as not meeting their
>transport networks' needs.

E> This is a true statement: the solution in this draft is useless for many=
 MPLS- TP deployments.

The two statements do not necessarily follow.

What we established during discussions at the SG15 plenary in February was =
that the issue some service providers had was that the IETF BFD solution ex=
ceeded their requirements in that there was additional functionality they d=
id not see a need for, and that they considered any additional functionalit=
y parasitic.

However this is a consequence of adapting an existing technology to a new a=
pplication. I do not see any way around that. And the entire joint project =
was based on the premise of engineering re-use not greenfield design. That =
is what it said on the tin up front, and IMO why when the IETF started down=
 this path packet transport transitioned from being a minority sport to mai=
nstream, so it is a bit late to cry foul....

My 2 cents
Dave




-----Original Message-----
From: David Allan I [mailto:david.i.allan@ericsson.com]
Sent: quarta-feira, 6 de Julho de 2011 18:36
To: erminio.ottone_69@libero.it; loa@pi.nu; Rui Costa
Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
Subject: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>=
 (Proactive Connectivity Verification, Continuity Check and Remote Defect i=
ndication for MPLS Transport Profile) to Proposed Standard

Hi Erminio:

Two of the three document editors were present at SG15 plenary in February =
where the comments originated. The revised meeting schedule resulted in a d=
ay spent going through the document with the editors. IMO there were lots o=
f discussion and legitimate issues with the document identified and correct=
ed so it was a useful session. The liaison of same was in many ways *after =
the fact*.

Cheers
Dave




-----Original Message-----
From: erminio.ottone_69@libero.it [mailto:erminio.ottone_69@libero.it]
Sent: quarta-feira, 6 de Julho de 2011 18:34
To: Rui Costa; ietf@ietf.org; IETF-Announce
Cc: mpls@ietf.org
Subject: R: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Pr=
oactive Connectivity Verification, Continuity Check and Remote Defect indic=
ation for MPLS Transport Profile) to Proposed Standard

The way this draft has been developed is a bit strange.

The poll for its adoption as a WG document was halted by the MPLS WG chair =
because "it is not possible to judge consensus":

http://www.ietf.org/mail-archive/web/mpls/current/msg04502.html

The lack of consensus was motivated by serious technical concerns raised by=
 several transport experts during the poll.

Nevertheless the MPLS WG chair decided to adopt the draft as a WG document:

http://www.ietf.org/mail-archive/web/mpls/current/msg04512.html

After several WG revisions and WG LCs, the technical issues have not been r=
esolved.

>Several service providers regarded this draft as not meeting their
>transport
networks' needs.

This is a true statement: the solution in this draft is useless for many MP=
LS- TP deployments.


-----Original Message-----
From: erminio.ottone_69@libero.it [mailto:erminio.ottone_69@libero.it]
Sent: quarta-feira, 6 de Julho de 2011 18:26
To: loa@pi.nu; Rui Costa
Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
Subject: R: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Pr=
oactive Connectivity Verification, Continuity Check and Remote Defect indic=
ation for MPLS Transport Profile) to Proposed Standard

>  Version -04 of the document was published June 28th.
>
>  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
> June 29th.
>

So when the WG LC to confirm the LC comment resolution has been launched?

The proto write-up says:

            It has also passed a working roup call to verify that LC commen=
ts were correctly with minor comments.

It also says:

            The comments has been
            carefully discussed between the authors and people making the c=
omments and
            has been resolved.

But it seems that some comments have not been discussed with the authors of=
 the comments. When ITU-T Q10/15 has been involved in discussing its commen=
ts?




-----Original Message-----
From: Loa Andersson [mailto:loa@pi.nu]
Sent: quarta-feira, 6 de Julho de 2011 16:44
To: Rui Costa
Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proac=
tive Connectivity Verification, Continuity Check and Remote Defect indicati=
on for MPLS Transport Profile) to Proposed Standard

All,

Since someone has commented about the process used for resolving
questions on
draft-ietf-mpls-tp-cc-cv-rdi I am supplying some details below.

The history of draft-ietf-mpls-tp-cc-cv-rdi working group review
process is:

On February 3rd 2011 the working group last call was issued
on version -03

      This was copied to the the Ad Hoc Team List
      and liaised to SG15 also on February 3rd

      This working group last call ended om Feb 28


      On Feb 28 we also received a liaison with comments from SG15


The authors compiled a list of all comments received  as part the MPLS
working group last call; these  comments - and the intended resolution -
is included in the meeting minutes from the Prague meeting:


      http://www.ietf.org/proceedings/80/slides/mpls-9.pdf


  During the IETF meeting in Prague, we agreed with the BFD working
  group to do a separate working group last callfor the BFD working
  group

The (BFD) working group last call was started on March 30th and ran
for 13 days. The last call ended on April 11th.

  The authors have since worked hard to resolve comments, some
  issue has been brought to the working group mailing list for
  resolution.

  Version -04 of the document was published June 28th.

  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
  June 29th.

  The AD review resulted in a "New ID needed" due to mostly editorial
  comments. Version -05 was published on June 29 and the IETF last call
  started as soon as the new ID was avaialbe.

  The current list of Last Call Comments resoltion is also avaiable at:
  http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls

  The list of issues that the authors kept very carefully, shows without
doubt
  that no comments been ignored.

  Loa
  mpls wg document shepherd







-----Original Message-----
From: David Allan I [mailto:david.i.allan@ericsson.com]
Sent: quarta-feira, 6 de Julho de 2011 14:58
To: Rui Costa; ietf@ietf.org; IETF-Announce
Cc: mpls@ietf.org
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proac=
tive Connectivity Verification, Continuity Check and Remote Defect indicati=
on for MPLS Transport Profile) to Proposed Standard

Hi Rui:

The comments were not ignored, the resolution of the Q10 comments as well a=
s those collected from the MPLS WG was presented at the last IETF. My sprea=
dsheet from which that report was generated and has been augmented to inclu=
de the BFD WG comments is available at http://www.pi.nu/~loa/cc-cv-rdi-Last=
-Call-Comments.xls

So you know...
Dave


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Rui=
 Costa
Sent: segunda-feira, 4 de Julho de 2011 23:03
To: ietf@ietf.org; IETF-Announce
Cc: mpls@ietf.org
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proac=
tive Connectivity Verification, Continuity Check and Remote Defect indicati=
on for MPLS Transport Profile) to Proposed Standard

IMHO and for the record:

ITU-T comments regarding this draft haven't been discussed with ITU-T but w=
ere simply ignored. No LS describing these comments' resolution was sent.

Several service providers regarded this draft as not meeting their transpor=
t networks' needs.

[The v03 draft was published in Feb and went to WG LC.
The v04 draft addressing WG LC comments was published on the 28th June (sam=
e date as the proto write-up).
When was the WG LC launched, to verify LC comments resolution?]

Regards,
Rui


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of The=
 IESG
Sent: quinta-feira, 30 de Junho de 2011 14:47
To: IETF-Announce
Cc: mpls@ietf.org
Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive=
 Connectivity Verification, Continuity Check and Remote Defect indication f=
or MPLS Transport Profile) to Proposed Standard


The IESG has received a request from the Multiprotocol Label Switching WG
(mpls) to consider the following document:
- 'Proactive Connectivity Verification, Continuity Check and Remote
   Defect indication for MPLS Transport Profile'
  <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract

   Continuity Check, Proactive Connectivity Verification and Remote
   Defect Indication functionalities are required for MPLS-TP OAM.

   Continuity Check monitors the integrity of the continuity of the
   label switched path for any loss of continuity defect. Connectivity
   verification monitors the integrity of the routing of the label
   switched path between sink and source for any connectivity issues.
   Remote defect indication enables an End Point to report, to its
   associated End Point, a fault or defect condition that it detects on
   a pseudo wire, label switched path or Section.

   This document specifies methods for proactive continuity check,
   continuity verification, and remote defect indication for MPLS-TP
   label switched paths, pseudo wires and Sections using Bidirectional
   Forwarding Detection.


The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/


No IPR declarations have been submitted directly on this I-D.
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

From nurit.sprecher@nsn.com  Thu Jul 14 10:50:09 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 C631111E809F; Thu, 14 Jul 2011 10:50:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.955
X-Spam-Level: 
X-Spam-Status: No, score=-3.955 tagged_above=-999 required=5 tests=[AWL=2.044,  BAYES_00=-2.599, J_CHICKENPOX_31=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 MgPgPMAiJUXg; Thu, 14 Jul 2011 10:50:05 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 6F1D311E8098; Thu, 14 Jul 2011 10:50:04 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p6EHo1fr016063 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 14 Jul 2011 19:50:01 +0200
Received: from DEMUEXC048.nsn-intra.net ([10.159.32.94]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p6EHnw2M020909; Thu, 14 Jul 2011 19:50:01 +0200
Received: from DEMUEXC014.nsn-intra.net ([10.150.128.25]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 14 Jul 2011 19:50:00 +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: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>(Proactive	Connectivity Verification, Continuity Check and Remote Defectindication for MPLS	Transport	Profile) to Proposed Standard
Date: Thu, 14 Jul 2011 19:49:57 +0200
Message-ID: <077E41CFFD002C4CAB7DFA4386A53264042047D1@DEMUEXC014.nsn-intra.net>
In-Reply-To: <52981DB05D3C5247A12D0AEE309F3CC201ED4D53BBBB@INOAVREX11.ptin.corpPT.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>(Proactive	Connectivity Verification, Continuity Check and Remote Defectindication for MPLS	Transport	Profile) to Proposed Standard
Thread-Index: Acw3LJ0GTOqQfPcUQOGUhgK/1kXgjgDPfXWgACJLxEAApIjzAABwiuqgAMFxdjA=
References: <52981DB05D3C5247A12D0AEE309F3CC201ED4D53B6BC@INOAVREX11.ptin.corpPT.com><60C093A41B5E45409A19D42CF7786DFD522135449A@EUSAACMS0703.eamcs.ericsson.se> <52981DB05D3C5247A12D0AEE309F3CC201ED4D53BBBB@INOAVREX11.ptin.corpPT.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext Rui Costa" <RCosta@ptinovacao.pt>, "David Allan I" <david.i.allan@ericsson.com>
X-OriginalArrivalTime: 14 Jul 2011 17:50:00.0977 (UTC) FILETIME=[741BE810:01CC424E]
Cc: mpls@ietf.org, ietf@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: Thu, 14 Jul 2011 17:50:09 -0000

Rui,
I kindly propose not to refer in this context to the Feb2011 WP3 and
SG15 plenary meetings....
Very unfortunately, it was far away from being a technical
discussion.....or technical poll.=20
Therefore it cannot be a reference to any argument in this context. =20
Regards,
Nurit


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
ext Rui Costa
Sent: Thursday, July 14, 2011 8:33 PM
To: David Allan I
Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
Subject: RE: [mpls] Last Call:
<draft-ietf-mpls-tp-cc-cv-rdi-05.txt>(Proactive Connectivity
Verification, Continuity Check and Remote Defectindication for MPLS
Transport Profile) to Proposed Standard

David,

T-MPLS rose from MPLS/IP's OAM blanks. Our main interest on it is the
simple/reliable OAM we had in SDH but lost in MPLS/IP. Otherwise, the
work in T-MPLS or MPLS-TP would be rather pointless.
ITU-T was historically the right place to define such OAM. So, our
interest started with ITU-T's work in T-MPLS and not when IETF joined.


We value IETF's work, and in 2008, when the IETF rose doubts about
future interoperability between T-MPLS and MPLS/IP (and the "danger to
the internet"), even though all T-MPLS Recommendations were approved and
the OAM one was ready for approval, a decision was made to listen
carefully to MPLS/IP's top experts' input.


IETF's unilateral decision to select BFD was IMHO a surprise: being a
primary goal in T-MPLS, i'd assume OAM definition was ITU-T's
responsibility/expertise or at least a compromise between the 2 SDOs.
ITU-T's not just a boilerplate stamper.
Hearing that "the decision was expressed in mpls-tp-analysis draft" was
another surprise: among the possible ways, the document showed, IMHO,
1731 as the closest one to requirements.


We don't need a requirement to agree on reusing as most as possible MPLS
and PW: it's common sense. However, it can't distract us from primary
goals.


"The issue is not code point, which is the trivial part. It is reuse of
the majority of the implementation. Again, pretty basic."
In other words, the problem is not backwards compatibility, (ergo the
"danger to the internet" problem never really existed) but maintaining
particular deployed platforms. If we had to convert cars into planes, we
couldn't say "to reuse the implementation, we can't add wings": they
wouldn't fly.
I'm used to FW/HW development and i don't share your cost/simplicity
view. (Please check other LC responses on this particular point.) I know
field network support and think you'd change your opinion if you had to
work on 24h field network support.



I agree with you that other opinions exist, counting not only
manufacturers but also operators. On the operators that don't agree with
you are certainly clients of yours. It's none of my business that you
view their opinions as "grumblings", but that's far from describing the
polls' results in the Feb2011 WG3 and SG15 plenaries, showing a minority
sharing your view, and that, although those not subscribing it tolerate
its evolution, you don't theirs.
Operators and their clients are the ones that, at the end of the day,
pay for networks. From the above, it'll be IMHO impossible to understand
if these Recommendations don't take into account these "grumblers'"
view, other than the obsession of those insisting to sell swiss knifes
to those who just want sharp scalpels. Why don't we call that also "not
constructive"?
"[R:] IMHO, between your MPLS-TP view and MPLS/IP, it becomes more and
more difficult to tell which is which.
[D:]That is because MPLS-TP is not a new techology, it is an addition to
the entire MPLS protocol suite."
Yes, i understand your view, David, but i'm sure you and i don't
subscribe this one:
"The creatures outside looked from pig to man, and from man to pig, and
from pig to man again; but already it was impossible to say which was
which".

Hope this helps. My comrade cents,
Rui



-----Original Message-----
From: David Allan I [mailto:david.i.allan@ericsson.com]
Sent: sexta-feira, 8 de Julho de 2011 17:13
To: Rui Costa; Stewart Bryant
Cc: erminio.ottone_69@libero.it; mpls@ietf.org; ietf@ietf.org;
IETF-Announce
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
(Proactive Connectivity Verification, Continuity Check and Remote Defect
indication for MPLS Transport Profile) to Proposed Standard

Rui:

You wrote:

>Reading something, keeping it on record, without effect in the draft
and "ignoring comments" have IMHO similar outcomes. As author of the
draft you are free to do it. These standards have a great impact
>in our work, so i'm also free to write what i did.

Numerous comments did have effect on the draft and those that didn't
were either simply not actionable, were rhetorical or not constructive,
and a few had to be balanced against comments coming from the MPLS & BFD
WGs. I would translate "ingored" or "without effect" to "did not get
one'e way". In the standards process it happens.

>My technical concerns regarding this draft were expressed...
>...in the (ITU-T -> IETF, Feb/2011) liaison regarding it (LS281, i
believe);
>...in operators' meetings' that took place during ITU-T's Feb/2011
plenary meeting;

I and the WG don't really have access to private grumblings.

Lots of other opinions were expressed as well, and they did not all
agree with you.

>Some:
>CC/CV
>I don't understand the need for 2 types of packets: a single type
allows CC; mismatching identifiers in the same CC packets allow CV.
>Besides adding complexity, we whether always activate both or
potentiate undetected mismerges.

OK, lets walk through this.

We want CV all the time so that any misconectivity can be detected, but
on the list it was expressed that the group did not want the overhead of
processing the source MEP TLV in every packet in order to achieve this.
We could carry it in every packet and have the receiver simply ignore
most of them, but then that would make the defect entry criteria
compeltely random and the exit criteria unreliable as well, not really a
good design. Hence they are separated using different ACH code points
and the receiver is obliged to process every source MEP TLV it receives.
I hope this is clear.

>(BTW: can't understand how we propose one ACH codepoint to CC, another
for CV, [counting other drafts, another for frame loss ...] but don't
consider assigning 1 single ACH protocol identifier codepoint >as
requested by ITU-T)

Because that puts you into two protocol ID demultiplexing steps per OAM
PDU recevied to determine the intended function. Hence COSTS MORE. That
is pretty basic...

> Uni P2P / P2MP
> I can't see how BFD will support unidir and hence P2MP other than...
> ...eliminating the session "state variable" (down, init, up), aiming
just the state variables we really need, bringing us to something
similar to 1731, eventually with other bits on the wire or...
> ...using IP to create the reverse way, which we cannot assume per
requirements;
> Will we create a complete different tool for that?
> (BFD's B=3D"bidirectional")

I would not go so far as to say "similar to 1731", there is actually a
lot of difference under the hood. As for uni-directional BFD, that is a
BFD WG problem at the moment.

> Provisioning list
> This is an MPLS profile/subset (and i heard) achievable through a
particular configuration. So, i expect each draft-ietf-mpls-TP-* to
focus on that profile/configuration. However, i keep seeing
> references f.i. to IP encapsulations unexpected under TP's OAM.
> I don't thus understand what the aim is: do we expect this in TP, are
we talking about MPLS in general?... The TP profile is never quite
delimited.
> Does chapter 4 contain ALL the configurable parameters list agreed to
provide in the comparison session?

It should. As for encapsulations, unless TP is in a complete island not
connected to anything (which as a network is rather useless) it will be
expected to interoperate with the rest of the MPLS architecture, and the
stated intention of tool development was that what resulted was
applicable to the broader MPLS architecture. Which means backwards
compatiblity and procedures for interoperation.

> Backwards compatibility
> This was the main argument risen to ground MPLS-TP OAM on BFD. It's
not a better argument than grounding MPLS-TP OAM on 1731 due to its ETH
deployment plus coherence with SDH, OTN, as defended by ITU-T.
> For reasons like the above, however, MPLS-TP BFD won't be backwards
compatible with previous BFD (even considering just CC/CV). They don't
even share the same codepoint.

The issue is not code point, which is the trivial part. It is reuse of
the majority of the implementation. Again, pretty basic.

>Simplicity
>Whether we look to PDH, SDH, OTN or ETH, ITU-T's approach to CC is
simpler: in each flow, a standard defined nr of constant heartbeat
signals (with standard constant or provisioned period - no
>auto/negotiated -) means OK. A standard defined number of misses means
lost Rx connection. An RDI, the only articulation between Rx and Tx
flows, meaningful in bidirectional applications, allows each
>pear to identify Tx problems.
>This OAM simplicity is the key for reliable fail finger pointing,
performance reports and protection. Also to allow scaling, more
implementation opportunities/manufacturers, which is valuable for
>operators.

Well IMO there was not a lot of interest in T-MPLS until the IETF was
going to re-define it and make it compatible with IP/MPLS. So there was
an industry wide "design intent" implied here.

> IMHO, between your MPLS-TP view and MPLS/IP, it becomes more and more
difficult to tell which is which.

That is because MPLS-TP is not a new techology, it is an addition to the
entire MPLS protocol suite.

Hope this helps
D









-----Original Message-----
From: David Allan I [mailto:david.i.allan@ericsson.com]
Sent: quarta-feira, 6 de Julho de 2011 19:25
To: erminio.ottone_69@libero.it; Rui Costa; ietf@ietf.org; IETF-Announce
Cc: mpls@ietf.org
Subject: RE: [mpls] R: Re: Last Call:
<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive Connectivity
Verification, Continuity Check and Remote Defect indication for MPLS
Transport Profile) to Proposed Standard

Hi Erminio:

<snipped>
>Several service providers regarded this draft as not meeting their
>transport networks' needs.

E> This is a true statement: the solution in this draft is useless for
many MPLS- TP deployments.

The two statements do not necessarily follow.

What we established during discussions at the SG15 plenary in February
was that the issue some service providers had was that the IETF BFD
solution exceeded their requirements in that there was additional
functionality they did not see a need for, and that they considered any
additional functionality parasitic.

However this is a consequence of adapting an existing technology to a
new application. I do not see any way around that. And the entire joint
project was based on the premise of engineering re-use not greenfield
design. That is what it said on the tin up front, and IMO why when the
IETF started down this path packet transport transitioned from being a
minority sport to mainstream, so it is a bit late to cry foul....

My 2 cents
Dave




-----Original Message-----
From: David Allan I [mailto:david.i.allan@ericsson.com]
Sent: quarta-feira, 6 de Julho de 2011 18:36
To: erminio.ottone_69@libero.it; loa@pi.nu; Rui Costa
Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
Subject: RE: [mpls] R: Re: Last Call:
<draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive Connectivity
Verification, Continuity Check and Remote Defect indication for MPLS
Transport Profile) to Proposed Standard

Hi Erminio:

Two of the three document editors were present at SG15 plenary in
February where the comments originated. The revised meeting schedule
resulted in a day spent going through the document with the editors. IMO
there were lots of discussion and legitimate issues with the document
identified and corrected so it was a useful session. The liaison of same
was in many ways *after the fact*.

Cheers
Dave




-----Original Message-----
From: erminio.ottone_69@libero.it [mailto:erminio.ottone_69@libero.it]
Sent: quarta-feira, 6 de Julho de 2011 18:34
To: Rui Costa; ietf@ietf.org; IETF-Announce
Cc: mpls@ietf.org
Subject: R: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
(Proactive Connectivity Verification, Continuity Check and Remote Defect
indication for MPLS Transport Profile) to Proposed Standard

The way this draft has been developed is a bit strange.

The poll for its adoption as a WG document was halted by the MPLS WG
chair because "it is not possible to judge consensus":

http://www.ietf.org/mail-archive/web/mpls/current/msg04502.html

The lack of consensus was motivated by serious technical concerns raised
by several transport experts during the poll.

Nevertheless the MPLS WG chair decided to adopt the draft as a WG
document:

http://www.ietf.org/mail-archive/web/mpls/current/msg04512.html

After several WG revisions and WG LCs, the technical issues have not
been resolved.

>Several service providers regarded this draft as not meeting their
>transport
networks' needs.

This is a true statement: the solution in this draft is useless for many
MPLS- TP deployments.


-----Original Message-----
From: erminio.ottone_69@libero.it [mailto:erminio.ottone_69@libero.it]
Sent: quarta-feira, 6 de Julho de 2011 18:26
To: loa@pi.nu; Rui Costa
Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
Subject: R: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
(Proactive Connectivity Verification, Continuity Check and Remote Defect
indication for MPLS Transport Profile) to Proposed Standard

>  Version -04 of the document was published June 28th.
>
>  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
> June 29th.
>

So when the WG LC to confirm the LC comment resolution has been
launched?

The proto write-up says:

            It has also passed a working roup call to verify that LC
comments were correctly with minor comments.

It also says:

            The comments has been
            carefully discussed between the authors and people making
the comments and
            has been resolved.

But it seems that some comments have not been discussed with the authors
of the comments. When ITU-T Q10/15 has been involved in discussing its
comments?




-----Original Message-----
From: Loa Andersson [mailto:loa@pi.nu]
Sent: quarta-feira, 6 de Julho de 2011 16:44
To: Rui Costa
Cc: ietf@ietf.org; IETF-Announce; mpls@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
(Proactive Connectivity Verification, Continuity Check and Remote Defect
indication for MPLS Transport Profile) to Proposed Standard

All,

Since someone has commented about the process used for resolving
questions on
draft-ietf-mpls-tp-cc-cv-rdi I am supplying some details below.

The history of draft-ietf-mpls-tp-cc-cv-rdi working group review
process is:

On February 3rd 2011 the working group last call was issued
on version -03

      This was copied to the the Ad Hoc Team List
      and liaised to SG15 also on February 3rd

      This working group last call ended om Feb 28


      On Feb 28 we also received a liaison with comments from SG15


The authors compiled a list of all comments received  as part the MPLS
working group last call; these  comments - and the intended resolution -
is included in the meeting minutes from the Prague meeting:


      http://www.ietf.org/proceedings/80/slides/mpls-9.pdf


  During the IETF meeting in Prague, we agreed with the BFD working
  group to do a separate working group last callfor the BFD working
  group

The (BFD) working group last call was started on March 30th and ran
for 13 days. The last call ended on April 11th.

  The authors have since worked hard to resolve comments, some
  issue has been brought to the working group mailing list for
  resolution.

  Version -04 of the document was published June 28th.

  The publication request for draft-ietf-mpls-tp-cc-cv-rdi was  sent
  June 29th.

  The AD review resulted in a "New ID needed" due to mostly editorial
  comments. Version -05 was published on June 29 and the IETF last call
  started as soon as the new ID was avaialbe.

  The current list of Last Call Comments resoltion is also avaiable at:
  http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls

  The list of issues that the authors kept very carefully, shows without
doubt
  that no comments been ignored.

  Loa
  mpls wg document shepherd







-----Original Message-----
From: David Allan I [mailto:david.i.allan@ericsson.com]
Sent: quarta-feira, 6 de Julho de 2011 14:58
To: Rui Costa; ietf@ietf.org; IETF-Announce
Cc: mpls@ietf.org
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
(Proactive Connectivity Verification, Continuity Check and Remote Defect
indication for MPLS Transport Profile) to Proposed Standard

Hi Rui:

The comments were not ignored, the resolution of the Q10 comments as
well as those collected from the MPLS WG was presented at the last IETF.
My spreadsheet from which that report was generated and has been
augmented to include the BFD WG comments is available at
http://www.pi.nu/~loa/cc-cv-rdi-Last-Call-Comments.xls

So you know...
Dave


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Rui Costa
Sent: segunda-feira, 4 de Julho de 2011 23:03
To: ietf@ietf.org; IETF-Announce
Cc: mpls@ietf.org
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
(Proactive Connectivity Verification, Continuity Check and Remote Defect
indication for MPLS Transport Profile) to Proposed Standard

IMHO and for the record:

ITU-T comments regarding this draft haven't been discussed with ITU-T
but were simply ignored. No LS describing these comments' resolution was
sent.

Several service providers regarded this draft as not meeting their
transport networks' needs.

[The v03 draft was published in Feb and went to WG LC.
The v04 draft addressing WG LC comments was published on the 28th June
(same date as the proto write-up).
When was the WG LC launched, to verify LC comments resolution?]

Regards,
Rui


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
The IESG
Sent: quinta-feira, 30 de Junho de 2011 14:47
To: IETF-Announce
Cc: mpls@ietf.org
Subject: [mpls] Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>
(Proactive Connectivity Verification, Continuity Check and Remote Defect
indication for MPLS Transport Profile) to Proposed Standard


The IESG has received a request from the Multiprotocol Label Switching
WG
(mpls) to consider the following document:
- 'Proactive Connectivity Verification, Continuity Check and Remote
   Defect indication for MPLS Transport Profile'
  <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally, comments may
be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract

   Continuity Check, Proactive Connectivity Verification and Remote
   Defect Indication functionalities are required for MPLS-TP OAM.

   Continuity Check monitors the integrity of the continuity of the
   label switched path for any loss of continuity defect. Connectivity
   verification monitors the integrity of the routing of the label
   switched path between sink and source for any connectivity issues.
   Remote defect indication enables an End Point to report, to its
   associated End Point, a fault or defect condition that it detects on
   a pseudo wire, label switched path or Section.

   This document specifies methods for proactive continuity check,
   continuity verification, and remote defect indication for MPLS-TP
   label switched paths, pseudo wires and Sections using Bidirectional
   Forwarding Detection.


The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/


No IPR declarations have been submitted directly on this I-D.
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


_______________________________________________
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 randy@qualcomm.com  Thu Jul 14 11:14:01 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 A7FBB21F8B65 for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 11:14:01 -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 jGkEvimANlNs for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 11:13:57 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 7128B21F8B18 for <ietf@ietf.org>; Thu, 14 Jul 2011 11:13:57 -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=1310667237; x=1342203237; 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<p0624066dca44df0ca50f@loud.pensive.org> |In-Reply-To:=20<04AE56F0C4CE8168D1B38D59@PST.JCK.COM> |References:=20<CAC4RtVBGgk74VMEty9u5Yq+DFy=3DoR5tOnbZ3R5 x83Gyee6mRNw@mail.gmail.com>=0D=0A=20<29987.1310565058@ma rajade.sandelman.ca>=20<4E1DCA13.9030301@acm.org>=0D=0A =20<04AE56F0C4CE8168D1B38D59@PST.JCK.COM>|X-Mailer:=20Eud ora=20for=20Mac=20OS=20X|Date:=20Thu,=2014=20Jul=202011 =2011:00:33=20-0700|To:=20John=20C=20Klensin=20<john-ietf @jck.com>,=20Marc=20Petit-Huguenin=20<petithug@acm.org> |From:=20Randall=20Gellens=20<randy@qualcomm.com> |Subject:=20Re:=20Confidentiality=20notices=20on=20email =20messages|CC:=20IETF=20discussion=20list=20<ietf@ietf.o rg>|MIME-Version:=201.0|Content-Type:=20text/plain=3B=20c harset=3D"us-ascii"=3B=20format=3Dflowed |X-Random-Sig-Tag:=201.0b28|X-Originating-IP:=20[172.30.4 8.1]; bh=+jVsAzVNf7CErkhoG4PtaY/jlW+uz2HJb/osinMy1kk=; b=mwi7eMK5D7WA0gndzQlF0p7oJPMO8JItHwtp95JDYeVu4KyVsdxKwfLy IxVEB2636e+R54beOtwqVIjFL7tl35SFOYQ45gn5tVJ7htuy+WtTnHmgc NKjqhf4JBvjW3Y3N+mH9RoGGY0X7DUl0n13g1zXlNso3kBM4J5G8X2DiX 8=;
X-IronPort-AV: E=McAfee;i="5400,1158,6407"; a="103582389"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine02.qualcomm.com with ESMTP; 14 Jul 2011 11:13:55 -0700
X-IronPort-AV: E=Sophos;i="4.65,529,1304319600"; d="scan'208";a="89716428"
Received: from nasanexhc05.na.qualcomm.com ([172.30.48.2]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 14 Jul 2011 11:13:55 -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.323.0; Thu, 14 Jul 2011 11:11:55 -0700
Message-ID: <p0624066dca44df0ca50f@loud.pensive.org>
In-Reply-To: <04AE56F0C4CE8168D1B38D59@PST.JCK.COM>
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <29987.1310565058@marajade.sandelman.ca> <4E1DCA13.9030301@acm.org> <04AE56F0C4CE8168D1B38D59@PST.JCK.COM>
X-Mailer: Eudora for Mac OS X
Date: Thu, 14 Jul 2011 11:00:33 -0700
To: John C Klensin <john-ietf@jck.com>, Marc Petit-Huguenin <petithug@acm.org>
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: Confidentiality notices on email messages
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.48.1]
Cc: 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, 14 Jul 2011 18:14:01 -0000

At 6:19 PM -0400 7/13/11, John C Klensin wrote:

>    Content-type: text/noise; noise-type="bogus-legal-disclaimer",
>  charset=...

Ooh, I like this proposal.  We can also have noise-types for 
exhortations to not print the email.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Note that although IBM 'invented' virtual memory in 1972 it had
been available in a multi-processor multi-tasking environment on
the Burroughs B5000 line since 1963 and the B6000 line since 1968.

From john-ietf@jck.com  Thu Jul 14 11:39:21 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 A2AC821F85C5 for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 11:39:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.753
X-Spam-Level: 
X-Spam-Status: No, score=-102.753 tagged_above=-999 required=5 tests=[AWL=-0.154, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 45LJA19gENkz for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 11:39:21 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 06F2021F85A0 for <ietf@ietf.org>; Thu, 14 Jul 2011 11:39:21 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QhQof-000J0D-Nx; Thu, 14 Jul 2011 14:39:17 -0400
Date: Thu, 14 Jul 2011 14:39:17 -0400
From: John C Klensin <john-ietf@jck.com>
To: Randall Gellens <randy@qualcomm.com>, Marc Petit-Huguenin <petithug@acm.org>
Subject: Re: Confidentiality notices on email messages
Message-ID: <49A68144182BB270C11BC841@PST.JCK.COM>
In-Reply-To: <p0624066dca44df0ca50f@loud.pensive.org>
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <29987.1310565058@marajade.sandelman.ca> <4E1DCA13.9030301@acm.org> <04AE56F0C4CE8168D1B38D59@PST.JCK.COM> <p0624066dca44df0ca50f@loud.pensive.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jul 2011 18:39:21 -0000

--On Thursday, July 14, 2011 11:00 -0700 Randall Gellens
<randy@qualcomm.com> wrote:

> At 6:19 PM -0400 7/13/11, John C Klensin wrote:
> 
>>    Content-type: text/noise;
>>    noise-type="bogus-legal-disclaimer", charset=...
> 
> Ooh, I like this proposal.  We can also have noise-types for
> exhortations to not print the email.

If one starts down that path, there is a real possibility for a
semantically-rich environment.  For example, consider a noise
type for flaming, repetitive, responses to a topic on the IETF
list.  One could also very efficiently reflect what I assume was
the intent of a recent observation on the list with
noise-type="hitler" :-(

   john




From joelja@bogus.com  Thu Jul 14 13:15:02 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 5DD7911E8087; Thu, 14 Jul 2011 13:15:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.923
X-Spam-Level: 
X-Spam-Status: No, score=-102.923 tagged_above=-999 required=5 tests=[AWL=-0.324, 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 IHmGJeYrWyxY; Thu, 14 Jul 2011 13:15:02 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id C0EDE11E8079; Thu, 14 Jul 2011 13:15:01 -0700 (PDT)
Received: from [172.16.24.53] (host-64-47-136-190.masergy.com [64.47.136.190]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p6EKF0Wj039329 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 14 Jul 2011 20:15:00 GMT (envelope-from joelja@bogus.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: [mpls] R: RE: R: Re:	Last	Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>	(Proactive	Connectivity	Verification, Continuity Check and Remote Defect	indication	for	MPLS	Transport	Profile) to Proposed Standard
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <5E893DB832F57341992548CDBB333163A0A92C535B@EMBX01-HQ.jnpr.net>
Date: Thu, 14 Jul 2011 13:14:54 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <4323DAB4-3BCC-434F-98EF-515FCA9381DC@bogus.com>
References: <29155895.3316791310591053994.JavaMail.defaultUser@defaultHost> <5E893DB832F57341992548CDBB333163A0A92C535B@EMBX01-HQ.jnpr.net>
To: IETF discussion list <ietf@ietf.org>, mpls@ietf.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]); Thu, 14 Jul 2011 20:15:00 +0000 (UTC)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jul 2011 20:15:02 -0000

To the extent that this particular debate (that of the nature scope and =
success or failure of the liaison effort) has been going on for some =
time:

* it's not going to be resolved.
* rehashing the history of how we came to this point it advances what =
agenda?

It would seems timely in the IETF last call to focus the line of =
criticism on the merits or lack thereof of the draft as it stands, not =
on how we arrived here.

joel



From barryleiba.mailing.lists@gmail.com  Thu Jul 14 14:02:02 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 9B9D711E80DD for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 14:02:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.115
X-Spam-Level: 
X-Spam-Status: No, score=-103.115 tagged_above=-999 required=5 tests=[AWL=-0.138, 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 x4ggNhBGau8m for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 14:02: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 527D711E80D4 for <ietf@ietf.org>; Thu, 14 Jul 2011 14:01:55 -0700 (PDT)
Received: by yxp4 with SMTP id 4so337834yxp.31 for <ietf@ietf.org>; Thu, 14 Jul 2011 14:01:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=p7DUEeQiozHWwpaT5jZIvfxnpf+PNdBq3WfKhN50JkQ=; b=uE+d+FHM4eh6ggaRB3oAmajSu26t7INyF13+fdJwfZTH9GWN9kVlrcmhV9rgw6jWOU WJQrYlSfgQKmZOp5c6YZeOc5A6DwFqe38t/j5rUhbXhgDuO3Mocwl/uTFDqVdh6wq6Mk KfepbzEUJUJRbZxdp2K41Qg/hG631RUgC7QJo=
MIME-Version: 1.0
Received: by 10.147.13.12 with SMTP id q12mr2700699yai.11.1310677314827; Thu, 14 Jul 2011 14:01:54 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.172.10 with HTTP; Thu, 14 Jul 2011 14:01:54 -0700 (PDT)
In-Reply-To: <49A68144182BB270C11BC841@PST.JCK.COM>
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <29987.1310565058@marajade.sandelman.ca> <4E1DCA13.9030301@acm.org> <04AE56F0C4CE8168D1B38D59@PST.JCK.COM> <p0624066dca44df0ca50f@loud.pensive.org> <49A68144182BB270C11BC841@PST.JCK.COM>
Date: Thu, 14 Jul 2011 17:01:54 -0400
X-Google-Sender-Auth: 92bQpxdb7-ZAucFJ68N7ftaygUo
Message-ID: <CAC4RtVDXG=4uesmnmK7aY_ZxkKdtCfZhd7B+fTxp7uX1NoCvPA@mail.gmail.com>
Subject: Re: Confidentiality notices on email messages
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: Randall Gellens <randy@qualcomm.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: Thu, 14 Jul 2011 21:02:02 -0000

>>> =A0 =A0Content-type: text/noise;
>>> =A0 =A0noise-type=3D"bogus-legal-disclaimer", charset=3D...
>>
>> Ooh, I like this proposal. =A0We can also have noise-types for
>> exhortations to not print the email.
>
> If one starts down that path, there is a real possibility for a
> semantically-rich environment. =A0For example, consider a noise
> type for flaming, repetitive, responses to a topic on the IETF
> list. =A0One could also very efficiently reflect what I assume was
> the intent of a recent observation on the list with
> noise-type=3D"hitler" :-(

I think you guys could develop a nice, crisp spec for this over the
coming 8.5 months.

Barry

From dworley@avaya.com  Thu Jul 14 16:03:07 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 8038321F871B for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 16:03:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.283
X-Spam-Level: 
X-Spam-Status: No, score=-103.283 tagged_above=-999 required=5 tests=[AWL=0.316, 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 sVn5R65nNiUg for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 16:03: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 6B7EE21F8745 for <ietf@ietf.org>; Thu, 14 Jul 2011 16:03:06 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAH91H07GmAcF/2dsb2JhbABUp2B3iHqncQKbMIVbXwSYAYtQ
X-IronPort-AV: E=Sophos;i="4.65,531,1304308800"; d="scan'208";a="256687244"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 14 Jul 2011 19:02:51 -0400
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 14 Jul 2011 19:01:10 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Thu, 14 Jul 2011 19:02:50 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: John C Klensin <john-ietf@jck.com>
Date: Thu, 14 Jul 2011 18:59:16 -0400
Subject: RE: Confidentiality notices on email messages
Thread-Topic: Confidentiality notices on email messages
Thread-Index: AcxCVWLP7dW3BufBRZ+4lDT/JC7b+wAJEW9S
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F5773@DC-US1MBEX4.global.avaya.com>
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <29987.1310565058@marajade.sandelman.ca>	<4E1DCA13.9030301@acm.org> <04AE56F0C4CE8168D1B38D59@PST.JCK.COM> <p0624066dca44df0ca50f@loud.pensive.org>, <49A68144182BB270C11BC841@PST.JCK.COM>
In-Reply-To: <49A68144182BB270C11BC841@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 list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jul 2011 23:03:07 -0000

> From: John C Klensin [john-ietf@jck.com]
>=20
> Randall Gellens <randy@qualcomm.com> wrote:
>=20
> > At 6:19 PM -0400 7/13/11, John C Klensin wrote:
> >
> >>    Content-type: text/noise;
> >>    noise-type=3D"bogus-legal-disclaimer", charset=3D...
> >
> > Ooh, I like this proposal.  We can also have noise-types for
> > exhortations to not print the email.
>=20
> If one starts down that path, there is a real possibility for a
> semantically-rich environment.  For example, consider a noise
> type for flaming, repetitive, responses to a topic on the IETF
> list.  One could also very efficiently reflect what I assume was
> the intent of a recent observation on the list with
> noise-type=3D"hitler" :-(

I, personally, am looking forward to the extended discussion regarding
the proper procedures for deciding upon and registering new values of
the "noise-type" parameter.  I believe that there are a number of
subtle conceptual and syntactic distinctions that need to be clearly
delineated, with due consideration for global cultural differences.

Dale
--
cephalopod9 wrote:
Only on Xkcd can you start a topic involving Hitler and people spend
the better part of half a dozen pages arguing about the quality of
Operating Systems.

From narten@us.ibm.com  Thu Jul 14 21:53:20 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 7A21D21F86BD for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 21:53:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.523
X-Spam-Level: 
X-Spam-Status: No, score=-106.523 tagged_above=-999 required=5 tests=[AWL=0.077, 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 U05NqKlFFlnC for <ietf@ietfa.amsl.com>; Thu, 14 Jul 2011 21:53:19 -0700 (PDT)
Received: from e36.co.us.ibm.com (e36.co.us.ibm.com [32.97.110.154]) by ietfa.amsl.com (Postfix) with ESMTP id 8582C21F867D for <ietf@ietf.org>; Thu, 14 Jul 2011 21:53:19 -0700 (PDT)
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by e36.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p6F4ktwb012925 for <ietf@ietf.org>; Thu, 14 Jul 2011 22:46:55 -0600
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id p6F4r4M5096500 for <ietf@ietf.org>; Thu, 14 Jul 2011 22:53:04 -0600
Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p6F4r35o018189 for <ietf@ietf.org>; Thu, 14 Jul 2011 22:53:03 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.176.22]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p6F4r2ef018106 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 14 Jul 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 p6F4r2uN032189 for <ietf@ietf.org>; Fri, 15 Jul 2011 00:53:02 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p6F4r1ki032152 for ietf@ietf.org; Fri, 15 Jul 2011 00:53:01 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201107150453.p6F4r1ki032152@rotala.raleigh.ibm.com>
Date: Fri, 15 Jul 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, 15 Jul 2011 04:53:20 -0000

Total of 166 messages in the last 7 days.
 
script run at: Fri Jul 15 00:53:01 EDT 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  3.01% |    5 |  8.90% |   127627 | neil.2.harrison@bt.com
  5.42% |    9 |  5.11% |    73305 | jmh@joelhalpern.com
  4.22% |    7 |  5.41% |    77548 | erminio.ottone_69@libero.it
  4.82% |    8 |  4.29% |    61563 | touch@isi.edu
  4.82% |    8 |  3.82% |    54829 | evnikita2@gmail.com
  2.41% |    4 |  5.57% |    79869 | david.i.allan@ericsson.com
  2.41% |    4 |  5.24% |    75130 | jdrake@juniper.net
  4.22% |    7 |  2.50% |    35895 | julian.reschke@gmx.de
  1.20% |    2 |  4.35% |    62421 | gregimirsky@gmail.com
  3.01% |    5 |  2.48% |    35639 | stpeter@stpeter.im
  1.20% |    2 |  3.48% |    49877 | nurit.sprecher@nsn.com
  2.41% |    4 |  2.09% |    30001 | len.holgate@gmail.com
  2.41% |    4 |  1.83% |    26193 | brian.e.carpenter@gmail.com
  2.41% |    4 |  1.59% |    22845 | barryleiba@computer.org
  2.41% |    4 |  1.52% |    21857 | petithug@acm.org
  2.41% |    4 |  1.41% |    20213 | iljitsch@muada.com
  1.81% |    3 |  1.70% |    24326 | francis@aspl.es
  1.81% |    3 |  1.35% |    19401 | moore@network-heretics.com
  1.81% |    3 |  1.31% |    18810 | gregw@intalio.com
  1.81% |    3 |  1.23% |    17654 | randy@qualcomm.com
  1.81% |    3 |  1.16% |    16658 | joelja@bogus.com
  1.81% |    3 |  1.01% |    14419 | mrex@sap.com
  1.81% |    3 |  0.95% |    13630 | mcr@sandelman.ca
  1.20% |    2 |  1.16% |    16620 | turchanyi.geza@gmail.com
  0.60% |    1 |  1.68% |    24073 | rcosta@ptinovacao.pt
  1.20% |    2 |  0.98% |    14087 | hsantos@isdg.net
  0.60% |    1 |  1.56% |    22352 | tnadeau@lucidvision.com
  1.20% |    2 |  0.93% |    13393 | housley@vigilsec.com
  1.20% |    2 |  0.93% |    13349 | nomcom-chair@ietf.org
  1.20% |    2 |  0.85% |    12136 | otroan@employees.org
  1.20% |    2 |  0.80% |    11467 | hextic@gmail.com
  1.20% |    2 |  0.77% |    11097 | wes@mti-systems.com
  1.20% |    2 |  0.77% |    10977 | rogerj@gmail.com
  1.20% |    2 |  0.74% |    10587 | vesely@tana.it
  1.20% |    2 |  0.72% |    10329 | samirs.lists@gmail.com
  1.20% |    2 |  0.67% |     9653 | mohta@necom830.hpcl.titech.ac.jp
  1.20% |    2 |  0.65% |     9355 | ibc@aliax.net
  0.60% |    1 |  1.24% |    17756 | medel@globetel.com.ph
  1.20% |    2 |  0.59% |     8485 | john-ietf@jck.com
  1.20% |    2 |  0.58% |     8268 | johnl@iecc.com
  0.60% |    1 |  1.10% |    15749 | alessandro.dalessandro@telecomitalia.it
  0.60% |    1 |  0.89% |    12769 | cntreras@gmail.com
  0.60% |    1 |  0.76% |    10857 | mnot@mnot.net
  0.60% |    1 |  0.74% |    10606 | keith.drage@alcatel-lucent.com
  0.60% |    1 |  0.66% |     9523 | swallow@cisco.com
  0.60% |    1 |  0.65% |     9388 | narten@us.ibm.com
  0.60% |    1 |  0.64% |     9208 | stbryant@cisco.com
  0.60% |    1 |  0.62% |     8910 | trammell@tik.ee.ethz.ch
  0.60% |    1 |  0.58% |     8258 | hannes.tschofenig@gmx.net
  0.60% |    1 |  0.52% |     7509 | hideki.endo.es@hitachi.com
  0.60% |    1 |  0.52% |     7431 | cb.list6@gmail.com
  0.60% |    1 |  0.51% |     7246 | ben@nostrum.com
  0.60% |    1 |  0.48% |     6828 | david.black@emc.com
  0.60% |    1 |  0.43% |     6179 | quittek@neclab.eu
  0.60% |    1 |  0.43% |     6156 | marka@isc.org
  0.60% |    1 |  0.42% |     6082 | fred@cisco.com
  0.60% |    1 |  0.42% |     5979 | tjc@ecs.soton.ac.uk
  0.60% |    1 |  0.41% |     5871 | bert@secret-wg.org
  0.60% |    1 |  0.41% |     5840 | dougb@dougbarton.us
  0.60% |    1 |  0.40% |     5782 | behcetsarikaya@yahoo.com
  0.60% |    1 |  0.40% |     5701 | dworley@avaya.com
  0.60% |    1 |  0.38% |     5472 | mail@sabahattin-gucukoglu.com
  0.60% |    1 |  0.38% |     5469 | mohacsi@niif.hu
  0.60% |    1 |  0.37% |     5238 | huubatwork@gmail.com
  0.60% |    1 |  0.36% |     5153 | rbarnes@bbn.com
  0.60% |    1 |  0.35% |     5035 | rsoc-chair@iab.org
  0.60% |    1 |  0.35% |     4997 | dhc2@dcrocker.net
  0.60% |    1 |  0.34% |     4944 | dave@cridland.net
  0.60% |    1 |  0.34% |     4890 | tglassey@earthlink.net
  0.60% |    1 |  0.32% |     4620 | ajs@anvilwalrusden.com
  0.60% |    1 |  0.31% |     4481 | jdfalk-lists@cybernothing.org
  0.60% |    1 |  0.30% |     4347 | michel@arneill-py.sacramento.ca.us
  0.60% |    1 |  0.28% |     3985 | psangster@gmail.com
--------+------+--------+----------+------------------------
100.00% |  166 |100.00% |  1434197 | Total

From julian.reschke@gmx.de  Fri Jul 15 00:20:22 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 EFEDF11E8072 for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 00:20:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.084
X-Spam-Level: 
X-Spam-Status: No, score=-104.084 tagged_above=-999 required=5 tests=[AWL=-1.485, 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 iRQqU1vZMnNt for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 00:20:21 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id BDF4211E8071 for <ietf@ietf.org>; Fri, 15 Jul 2011 00:20:20 -0700 (PDT)
Received: (qmail invoked by alias); 15 Jul 2011 07:20:19 -0000
Received: from p508FD5EC.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.213.236] by mail.gmx.net (mp043) with SMTP; 15 Jul 2011 09:20:19 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX195bkA27jF5Llmtw8h6eRTMoQf1gEkS/HdNOTUZmm dGeSIpkQ6Iv2Aw
Message-ID: <4E1FEA30.1000908@gmx.de>
Date: Fri, 15 Jul 2011 09:20:16 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20110711145053.F148121F8CA6@ietfa.amsl.com>
In-Reply-To: <20110711145053.F148121F8CA6@ietfa.amsl.com>
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, 15 Jul 2011 07:20:22 -0000

On 2011-07-11 16:50, Internet-Drafts Administrator wrote:
>
>
> This is a reminder that the Internet Draft Final Submission (version -01
> and up) cut-off is today, July 11, 2011.
>
> All Final Version (-01 and up) submissions are due by 17:00 PT (00:00
> UTC).
> ...

Out of curiosity - why do we still see new drafts coming out, even -00 ones?

Best regards, Julian

From olaf@NLnetLabs.nl  Fri Jul 15 02:45:23 2011
Return-Path: <olaf@NLnetLabs.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C85221F862F for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 02:45:23 -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.020, 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 UCvuYBPgMMrj for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 02:45:18 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id C183821F85CA for <ietf@ietf.org>; Fri, 15 Jul 2011 02:45:17 -0700 (PDT)
Received: from [IPv6:2001:7b8:206:1:226:b0ff:fee2:a770] ([IPv6:2001:7b8:206:1:226:b0ff:fee2:a770]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id p6F9j2Rn062208 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 15 Jul 2011 11:45:03 +0200 (CEST) (envelope-from olaf@NLnetLabs.nl)
Subject: Re: Confidentiality notices on email messages
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <4E1EEE0F.7090209@dcrocker.net>
Date: Fri, 15 Jul 2011 11:45:01 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9BE2752C-2665-48EA-8A5E-28AF17B9A107@NLnetLabs.nl>
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <CAP0PwYYmLxPSoPvUqYOO_y=Hdn9vBSTRC5ax4wnjzE1SD1+aLg@mail.gmail.com> <4E1EEE0F.7090209@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::53]); Fri, 15 Jul 2011 11:45:04 +0200 (CEST)
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, 15 Jul 2011 09:45:23 -0000

On Jul 14, 2011, at 3:24 PM, Dave CROCKER wrote:

> It's excellent that the issue was covered in the RFC.
>=20
> My question is how the contents of that RFC can be binding on random =
IETF participants?

At the risk of answering a rhetorical question: It's being referred to =
in the NOTE WELL.

All of the work we do in the IETF is based on the premisses that =
somebody who participates in the IETF is exposed to the NOTE WELL. =
Personally, I think people are exposed ad nauseoum, whether a court =
would agree, I do not know.

--Olaf


________________________________________________________=20

Olaf M. Kolkman                        NLnet Labs
http://www.nlnetlabs.nl/











    =20


From ynir@checkpoint.com  Fri Jul 15 04:07:44 2011
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05F1921F8547 for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 04:07:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.693
X-Spam-Level: 
X-Spam-Status: No, score=-10.693 tagged_above=-999 required=5 tests=[AWL=-0.094, 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 TgEIx2ddwbsd for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 04:07:43 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 7DB6721F8546 for <ietf@ietf.org>; Fri, 15 Jul 2011 04:07:42 -0700 (PDT)
X-CheckPoint: {4E202D2B-6-1B221DC2-FFFF}
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id p6FB7bEB017851;  Fri, 15 Jul 2011 14:07:37 +0300
Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.2.255.0; Fri, 15 Jul 2011 14:07:37 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Fri, 15 Jul 2011 14:07:37 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 15 Jul 2011 14:07:34 +0300
Subject: Re: Internet Draft Final Submission Cut-Off Today
Thread-Topic: Internet Draft Final Submission Cut-Off Today
Thread-Index: AcxC32cSnafdeuMgTwG65X2AjUmcvw==
Message-ID: <E92A6158-30FF-44FB-95C0-6A2DDBC8DB2B@checkpoint.com>
References: <20110711145053.F148121F8CA6@ietfa.amsl.com> <4E1FEA30.1000908@gmx.de>
In-Reply-To: <4E1FEA30.1000908@gmx.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
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, 15 Jul 2011 11:07:44 -0000

On Jul 15, 2011, at 10:20 AM, Julian Reschke wrote:

> On 2011-07-11 16:50, Internet-Drafts Administrator wrote:
>>=20
>>=20
>> This is a reminder that the Internet Draft Final Submission (version -01
>> and up) cut-off is today, July 11, 2011.
>>=20
>> All Final Version (-01 and up) submissions are due by 17:00 PT (00:00
>> UTC).
>> ...
>=20
> Out of curiosity - why do we still see new drafts coming out, even -00 on=
es?

Some drafts don't get posted immediately because of nits or because the sub=
mitter changed the meta-data. These get handled manually. If the draft was =
submitted in time, it will be posted as soon as the problems are cleared, e=
ven if the cut-off date has passed.




From barryleiba.mailing.lists@gmail.com  Fri Jul 15 07:19:13 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 547A121F86EA for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 07:19:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.11
X-Spam-Level: 
X-Spam-Status: No, score=-103.11 tagged_above=-999 required=5 tests=[AWL=-0.133, 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 HWhxXn7IvQ5K for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 07:19: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 DAACA21F86B9 for <ietf@ietf.org>; Fri, 15 Jul 2011 07:19:12 -0700 (PDT)
Received: by gxk19 with SMTP id 19so614828gxk.31 for <ietf@ietf.org>; Fri, 15 Jul 2011 07:19:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=DDiAy9bfZcMZbTegra8tjtMTJhN66o1DSYhd0fAtF00=; b=hSKiOOac8n5IgvBGAbRSF9OaDL87uUndYM3NOrYGEmEM9KHGmweo1t3NK109sU0EWf kTB3dCPL/pIotInaJXPO9EEPHbsGM9Swz3buqBPtYWY6JScKpSBr/0c/aSZuwtSuy8Q5 k0ADVf5wnd25+un9M3uni/g9K/8CaB5R3Ronw=
MIME-Version: 1.0
Received: by 10.236.179.36 with SMTP id g24mr4593522yhm.297.1310739552255; Fri, 15 Jul 2011 07:19:12 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.172.10 with HTTP; Fri, 15 Jul 2011 07:19:12 -0700 (PDT)
In-Reply-To: <E92A6158-30FF-44FB-95C0-6A2DDBC8DB2B@checkpoint.com>
References: <20110711145053.F148121F8CA6@ietfa.amsl.com> <4E1FEA30.1000908@gmx.de> <E92A6158-30FF-44FB-95C0-6A2DDBC8DB2B@checkpoint.com>
Date: Fri, 15 Jul 2011 10:19:12 -0400
X-Google-Sender-Auth: LgK-fmPeJ7ouCZFOGoWpmvk7hl0
Message-ID: <CAC4RtVBAwygjHc=wUULjAu4Kz_T+0B7QCHVqRrfRq9_TdUc8uw@mail.gmail.com>
Subject: Re: Internet Draft Final Submission Cut-Off Today
From: Barry Leiba <barryleiba@computer.org>
To: IETF Discussion <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jul 2011 14:19:13 -0000

>> Out of curiosity - why do we still see new drafts coming out, even -00 ones?
>
> Some drafts don't get posted immediately

There also appears to be a bug, wherein the tool is not blocking late
submissions.

As we say, "There are still a few bugs in the system."

Barry

From vesely@tana.it  Fri Jul 15 07:55:49 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 B803021F85C6 for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 07:55:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.836
X-Spam-Level: 
X-Spam-Status: No, score=-4.836 tagged_above=-999 required=5 tests=[AWL=-0.117, 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 GN8sQg72+AWE for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 07:55:45 -0700 (PDT)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id C9D0221F85B5 for <ietf@ietf.org>; Fri, 15 Jul 2011 07:55:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1310741743; bh=WFaJJmLTXkycuuRQHgXqXw8SDsC3V3fHb7E/sZ1W9kA=; l=1239; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=ctZF3jU4Rlln35c6IcUnFCvr2ON02OxFPV2nJj5uE9ew3I672CEKaMGkQwPPQLGyL j+jS1SGj7KtwkONzAX+UX7ou6+FcmlTkFB3CQFtG9Tuvx6jCT+rk8ryTRleldQkm/g bduGFsQwHxVNbcF1/rljVNCKXtPLLDw8TsL6tYbI=
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; Fri, 15 Jul 2011 16:55:43 +0200 id 00000000005DC045.000000004E2054EF.00005D93
Message-ID: <4E2054EE.7080108@tana.it>
Date: Fri, 15 Jul 2011 16:55:42 +0200
From: Alessandro Vesely <vesely@tana.it>
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: ietf@ietf.org
Subject: Re: Confidentiality notices on email messages
References: <20110714014835.9480.qmail@joyce.lan> <4E1F0B2C.3070401@tana.it> <2A06ADAE-70E2-4D0C-9809-66E01943B68E@gmail.com>
In-Reply-To: <2A06ADAE-70E2-4D0C-9809-66E01943B68E@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jul 2011 14:55:49 -0000

On 14/Jul/11 18:37, Will McAfee wrote:
> On Jul 14, 2011, at 11:28 AM, Alessandro Vesely <vesely@tana.it> wrote:
>> One can sign the "Sensitivity" header field defined by RFC 2156.  It
>> can have the values "Personal" / "Private" / "Company-Confidential".
>> 
>> However, I received some messages bearing a confidentiality notice but
>> missing this field entirely.  Even the TC system above could hardly
>> cope with such inconsistent settings.  Do notices still retain any
>> legal value in such cases?
>
> They don't have legal value, period.

It is still an argument that one can bring before a court, e.g. when
claiming damage for unauthorized disclosure of confidential data.  We
all know that misaddressing can (and does) happen.  Stating that a
message is confidential might be worth in certain circumstances.
See http://www.out-law.com/page-5536

The point is that the semantic status of a message should be set by
the sender, properly.  It does not scale to leave it up to the
recipients to determine whether any possible notice is harmless,
inapplicable, or out of context.  Laws may allow it, protocols less so.

-- 
*NOTICE*
Access to this text is restricted to people having the right to do so.
-rwxrwxrwx


From joelja@bogus.com  Fri Jul 15 08:05:49 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 2AFF021F84FD for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 08:05:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.869
X-Spam-Level: 
X-Spam-Status: No, score=-102.869 tagged_above=-999 required=5 tests=[AWL=-0.270, 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 jBZBLrh-fn6s for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 08:05:47 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 0CFCE21F856D for <ietf@ietf.org>; Fri, 15 Jul 2011 08:05:46 -0700 (PDT)
Received: from [172.16.24.53] (host-64-47-136-190.masergy.com [64.47.136.190]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p6FF5VQx063056 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 15 Jul 2011 15:05:32 GMT (envelope-from joelja@bogus.com)
Subject: Re: Internet Draft Final Submission Cut-Off Today
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <CAC4RtVBAwygjHc=wUULjAu4Kz_T+0B7QCHVqRrfRq9_TdUc8uw@mail.gmail.com>
Date: Fri, 15 Jul 2011 08:05:26 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <87AC5FC2-328E-4EA7-AD69-C5092430BC32@bogus.com>
References: <20110711145053.F148121F8CA6@ietfa.amsl.com> <4E1FEA30.1000908@gmx.de> <E92A6158-30FF-44FB-95C0-6A2DDBC8DB2B@checkpoint.com> <CAC4RtVBAwygjHc=wUULjAu4Kz_T+0B7QCHVqRrfRq9_TdUc8uw@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.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]); Fri, 15 Jul 2011 15:05:32 +0000 (UTC)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jul 2011 15:05:49 -0000

On Jul 15, 2011, at 7:19 AM, Barry Leiba wrote:

>>> Out of curiosity - why do we still see new drafts coming out, even =
-00 ones?
>>=20
>> Some drafts don't get posted immediately
>=20
> There also appears to be a bug, wherein the tool is not blocking late
> submissions.
>=20
> As we say, "There are still a few bugs in the system."

There are also documents which have become wg documents, and their =
counter resets to zero when they cease being individual submissions.

presumably there were also the usual trickle of manual submissions which =
were probably completed last week.

> Barry
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From wjhns1@hardakers.net  Fri Jul 15 08:07:24 2011
Return-Path: <wjhns1@hardakers.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A35D21F863A for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 08:07:24 -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 DdvQ1XA95Kra for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 08:07:24 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.236.43]) by ietfa.amsl.com (Postfix) with ESMTP id DFD4021F856D for <ietf@ietf.org>; Fri, 15 Jul 2011 08:07:23 -0700 (PDT)
Received: from localhost (wjh.hardakers.net [10.0.0.2]) by mail.hardakers.net (Postfix) with ESMTPSA id 389CF59D; Fri, 15 Jul 2011 08:06:53 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Confidentiality notices on email messages
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <29987.1310565058@marajade.sandelman.ca> <4E1DCA13.9030301@acm.org> <04AE56F0C4CE8168D1B38D59@PST.JCK.COM> <p0624066dca44df0ca50f@loud.pensive.org> <49A68144182BB270C11BC841@PST.JCK.COM>
Date: Fri, 15 Jul 2011 08:06:52 -0700
In-Reply-To: <49A68144182BB270C11BC841@PST.JCK.COM> (John C. Klensin's message of "Thu, 14 Jul 2011 14:39:17 -0400")
Message-ID: <sdlivza8hf.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Cc: Randall Gellens <randy@qualcomm.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jul 2011 15:07:24 -0000

>>>>> On Thu, 14 Jul 2011 14:39:17 -0400, John C Klensin <john-ietf@jck.com> said:

>> Ooh, I like this proposal.  We can also have noise-types for
>> exhortations to not print the email.

JCK> If one starts down that path, there is a real possibility for a
JCK> semantically-rich environment.  For example, consider a noise
JCK> type for flaming, repetitive, responses to a topic on the IETF
JCK> list.  One could also very efficiently reflect what I assume was
JCK> the intent of a recent observation on the list with
JCK> noise-type="hitler" :-(

Obviously we need to take a typical step back first and determine the
scope of the problem.  We need to commission a "requirements for noise"
ID first.
-- 
Wes Hardaker
SPARTA, Inc.

From harald@alvestrand.no  Fri Jul 15 08:18:56 2011
Return-Path: <harald@alvestrand.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 444CF21F8752 for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 08:18:56 -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.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 HFmcDj3vOJFg for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 08:18:55 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id A113921F874A for <ietf@ietf.org>; Fri, 15 Jul 2011 08:18:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 2295039E12B; Fri, 15 Jul 2011 17:17:50 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2V9upbnf31BF; Fri, 15 Jul 2011 17:17:49 +0200 (CEST)
Received: from [192.168.1.53] (162.80-203-220.nextgentel.com [80.203.220.162]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 47FA239E03C; Fri, 15 Jul 2011 17:17:49 +0200 (CEST)
Message-ID: <4E205A5D.1020304@alvestrand.no>
Date: Fri, 15 Jul 2011 17:18:53 +0200
From: Harald Alvestrand <harald@alvestrand.no>
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: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Review of draft-yevstifeyev-ion-report-06
References: <4D91EBDE.5070703@gmail.com>
In-Reply-To: <4D91EBDE.5070703@gmail.com>
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, 15 Jul 2011 15:18:56 -0000

My apologies for the lateness of this review.

I am not happy with this document.

I was unhappy with the IESG's decision to close the ION experiment, 
since I believe the mechanisms that were chosen to replace it failed to 
fulfil several of the requirements that were driving forces in the 
design of the ION mechanism (as an example, try to find out who, if 
anyone, approved http://iaoc.ietf.org/network_requirements.html, what 
the previous version was, and when this version was approved).

The document does not refer back to the aims of the experiment, which I 
tried to make explicit in section 5 of RFC 4693, which include:

- Easy updating
- Explicit approval
- Accessible history

The sum total of analysis in this document is two sentences:
The cited IESG statement

      It is clear that the IESG, IAB, and IAOC need the ability to
      publish documents that do not expire and are easily updated.
      Information published as web pages, including IESG Statements, are
      sufficient for this purpose.

The draft's statement

    Taking everything into account, it was considered that IONs added
    complications to the maintenance of documents but did not give a
    corresponding benefit to the IETF.

I would at least expect those three points to be explicitly addressed by 
analysis, such as:

- The IESG concluded that publication of IONs was more complex than 
publishing Web pages and IESG statements
- The IESG concluded that the IESG statement mechanism, which has no 
formal definition, was enough documentation of the IESG's decisions 
where decision documentation was reasonable, and that Web pages needed 
no explicit approval
- The IESG concluded that there was no need to provide an accessible 
history of versions of the documents for which the ION mechanism was 
intended

The document also needs a language check, but I feel that the lack of 
*any* explicit analysis with respect to the aims of the experiment, even 
an explicit statement that the issues involved were considered not 
important, is the most important shortcoming of the document.

                         Harald







From john-ietf@jck.com  Fri Jul 15 08:55: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 EE7F321F8A4F; Fri, 15 Jul 2011 08:55:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.442
X-Spam-Level: 
X-Spam-Status: No, score=-102.442 tagged_above=-999 required=5 tests=[AWL=-0.443, 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 wmMagDMO204I; Fri, 15 Jul 2011 08:55:21 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id CA4BF21F853A; Fri, 15 Jul 2011 08:55:20 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QhkjX-000DI0-MS; Fri, 15 Jul 2011 11:55:20 -0400
Date: Fri, 15 Jul 2011 11:55:18 -0400
From: John C Klensin <john-ietf@jck.com>
To: IETF Discussion <ietf@ietf.org>
Subject: Another look at 6to4 (and other IPv6 transition issues)
Message-ID: <DB5571A0CF3C3F570576A23F@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: 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, 15 Jul 2011 15:55:22 -0000

Hi.

I've been thinking about this and having a few off-list
conversations and want to make a suggestion that draws together
a few others.  Since many people don't like my long notes with
the conclusion at the end, this one is suggestion-first.  If the
suggestion offends you sufficiently, you can just stop reading
there.

Recommendation:

(1) Abandon the effort to classify the specifications as
Historic.  It is at best a symbolic act that few people outside
the IETF community will even notice, much less act differently
because we have done it.  Instead, let's try to focus on what is
actually important, not classification and name-called ("curse
you, you Historic protocol" :-(  ).

(2) Pull the "-advice" document back from the RFC Editor queue
and fold the actual substantive content of the "-historic"
document into it, preferably as a very clear and very prominent
Applicability Statement.  If this is what v6ops believes, the
statement might reasonably say something like:

	(2a) This protocol, if not used very carefully, leads to
	bad operational situations in which things get lost and
	the problems are hard to diagnose.   We strongly
	recommend that it not ever be a default and that it not
	be used except under special circumstances and with
	great care.
	
	(2b) Even then, we recommend that it not be used unless
	all of those configuring routing information and all the
	systems along the routing path are run by experts who
	both understanding the issues and are willing to accept
	responsibility.
	
	(2c) If you do decide to use the thing, the "advice"
	recommendations in the rest of this document are
	mandatory and MUST be followed to avoid serious
	operational problems.

I haven't included either Randy's colorful language or mine in
the example above, but the intent should be clear.  Depending on
how much detail the community thinks is useful, there is a good
deal of potentially-useful text in draft-moore-6to4-experimental
as well as in the "-historic" draft.

The resulting document should explicitly update RFC3056 and
RFC3068.  Taking that action will send a much stronger "you need
to read that document before doing anything with this one"
message to most of the people who are familiar with how things
work than a reclassification of the base documents.  For those
who aren't familiar with how things work, all of these
approaches, including moving 6to4 to Historic, are pointless.

That is all.  This can and should be made to sound like mature
engineering advice, which it presumably is, and not like small
children throwing mud at each other.


Explanation and Rants:

(ii) I think moving _this_ protocol to Experimental is just
silly.  We use Experimental for things that are
pre-standardization or not sufficiently mature to be
standardized.  Although the bar is higher, there are elements of
"experiment" in every Proposed Standard --that is why we have a
multiple-step standardization process.   If there is really
something to be learned from 6to4 operated in a different way,
then the right action to take would be to propose a 6to4bis that
outlines the characteristics of the protocol, eliminates
anything we have concluded should not be done, and outlines the
desired experiment.  That document might reasonably be listed as
updating RFC3056 and RFC3068 as well.  

(i) <rant> Presumably our goal is to get IPv6 deployed and
provide advice useful to its deployment, independent of any
particular piece of protocol or transition arrangement.  At
least one of the many reasons we haven't seen more deployment is
that we keep sending messages to the broader community that,
however unintentionally, discourage that deployment.  In the
early days of IPv6, we did that by advertising (or letting
others who were presumed to be speaking for us advertise) that
IPv6 was completely ready and that transition was going to be
easy, cheap, and seamless.  For those who had to make decisions
as to when to deploy IPv6, sufficient investigation tp discover
that some of that story was untrue became sufficient motivation
to back away from IPv6 entirely until we got our acts together.
In more recent years, we have continued to deliver the message
that the IETF (and, to a lesser extent the RIRs) are simply
confused about what advice to give and therefore that IPv6 isn't
ready for someone to deploy who suffers from limited resources
and a strong desire to do it only when all of the ducks are
lined up.  Every time we propose a new transition model or
denounce an old one without what seems to be an
externally-convincing analysis of the complete picture, we make
things worse by distributing yet another chapter of "even the
IETF has no real idea how to transition to IPv6".

If we are serious about encouraging deployment of IPv6 -- and I
hope we are -- then it is time to stop the apparent war among
transition strategies.  It seems to me that the document that is
needed is a vastly strengthened (and probably standards-track)
version of RFC 6180 (a rather nice document that I would
encourage those who are engaged in the 6to4 debate on the IETF
list to read), but one that goes beyond such statements as 

	There are several types of tunneling mechanisms,
	including manually configured IPv6-over-IPv4 tunnels
	[RFC4213], 6to4 [RFC3056], automatic host-based tunnels
	[RFC4380], tunnel brokers [RFC3053], running IPv6 over
	MPLS with IPv6 Provider Edge Routers (6PE) [RFC4798],
	the use of Virtual Private Networks (VPNs) or mobility
	tunnels to carry both IPv4 and IPv6 [RFC4301] [RFC5454]
	[RFC5555] [RFC5844], and many others.

(from Section 4.2) and into a serious discussion of the
scenarios that are the best match to different of these
strategies (and others).  If we don't know, then let's say,
explicitly, that we haven't had quite enough experience to
provide a differential chart of when particular techniques can
be used but that they are out their, with their strengths and
weaknesses, for situations to which they seem well-adapted.  It
is almost possible to infer from 6180's conclusions that almost
all transition mechanisms are equivalent, at least within
groups, and those that aren't are best dealt with by public
burning.  Clearly we don't believe the first part of that; we
should get away from the appearance of believing the second.

And, again and most important, if we want to see IPv6 deployed,
we need a clear message that we actually understand what we are
doing, that we have a coherent picture, and that our process is
not one of lurching among solutions, hoping that each one will
be the magic bullet, and then denouncing any that turn out to
not have sufficient magical properties.  The marketplace knows
how to deal with the message we are sending with debates about
recategorization and we have already seen the answer: it isn't
the universal deployment of IPv6 before now or any time soon.
</rant>

    john



From dwm@xpasc.com  Fri Jul 15 09:08:13 2011
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E21921F899D for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 09:08:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.721
X-Spam-Level: 
X-Spam-Status: No, score=-3.721 tagged_above=-999 required=5 tests=[AWL=-1.122, 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 1Uko0RR83MsX for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 09:08:12 -0700 (PDT)
Received: from mail.xpasc.com (mail.xpasc.com [68.164.244.189]) by ietfa.amsl.com (Postfix) with ESMTP id 90B8921F88A0 for <ietf@ietf.org>; Fri, 15 Jul 2011 09:08:12 -0700 (PDT)
Received: from bslepgate.xpasc.com (localhost.localdomain [127.0.0.1]) by bslepgate.xpasc.com (Postfix-out) with ESMTP id A4AFB100091 for <ietf@ietf.org>; Fri, 15 Jul 2011 09:08:12 -0700 (PDT)
X-Propel-Return-Path: <dwm@xpasc.com>
Received: from mail.xpasc.com ([10.1.2.88]) by [127.0.0.1] ([127.0.0.1]) (port 7027) (Abaca EPG outproxy filter 3.1.2.exported $Rev: 9262 $) id iz6Urb7fg8c0; Fri, 15 Jul 2011 09:08:12 -0700
Received: from xpasc.com (egate.xpasc.com [10.1.2.49]) by bslepgate.xpasc.com (Postfix-out) with ESMTP id 7188B10008D for <ietf@ietf.org>; Fri, 15 Jul 2011 09:08:12 -0700 (PDT)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id p6FG8B8S031270 for <ietf@ietf.org>; Fri, 15 Jul 2011 09:08:11 -0700
Date: Fri, 15 Jul 2011 09:08:11 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: IETF discussion list <ietf@ietf.org>
Subject: Re: Confidentiality notices on email messages
In-Reply-To: <sdlivza8hf.fsf@wjh.hardakers.net>
Message-ID: <Pine.LNX.4.64.1107150906590.16878@egate.xpasc.com>
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <29987.1310565058@marajade.sandelman.ca> <4E1DCA13.9030301@acm.org> <04AE56F0C4CE8168D1B38D59@PST.JCK.COM> <p0624066dca44df0ca50f@loud.pensive.org> <49A68144182BB270C11BC841@PST.JCK.COM> <sdlivza8hf.fsf@wjh.hardakers.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Propel-ID: iz6Urb7fg8c0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: IETF discussion list <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jul 2011 16:08:13 -0000

On Fri, 15 Jul 2011, Wes Hardaker wrote:

> >>>>> On Thu, 14 Jul 2011 14:39:17 -0400, John C Klensin <john-ietf@jck.com> said:
> 
> >> Ooh, I like this proposal.  We can also have noise-types for
> >> exhortations to not print the email.
> 
> JCK> If one starts down that path, there is a real possibility for a
> JCK> semantically-rich environment.  For example, consider a noise
> JCK> type for flaming, repetitive, responses to a topic on the IETF
> JCK> list.  One could also very efficiently reflect what I assume was
> JCK> the intent of a recent observation on the list with
> JCK> noise-type="hitler" :-(
> 
> Obviously we need to take a typical step back first and determine the
> scope of the problem.  We need to commission a "requirements for noise"
> ID first.

Can we schedule a BOF? Perhaps a symbolic burning of notices?

Dave Morris

From ned+ietf@mauve.mrochek.com  Fri Jul 15 09:15:32 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 752EE21F8AEA for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 09:15: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 qt8ZDtjbxOzF for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 09:15:28 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 15DED21F8AF0 for <ietf@ietf.org>; Fri, 15 Jul 2011 09:15:28 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O3O60SOY5C00X1AD@mauve.mrochek.com> for ietf@ietf.org; Fri, 15 Jul 2011 09:14:42 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O3O39SAX4W00VHKR@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Fri, 15 Jul 2011 09:14:36 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01O3O60PAEKG00VHKR@mauve.mrochek.com>
Date: Fri, 15 Jul 2011 09:14:03 -0700 (PDT)
Subject: Re: Confidentiality notices on email messages
In-reply-to: "Your message dated Fri, 15 Jul 2011 09:08:11 -0700 (PDT)" <Pine.LNX.4.64.1107150906590.16878@egate.xpasc.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <29987.1310565058@marajade.sandelman.ca> <4E1DCA13.9030301@acm.org> <04AE56F0C4CE8168D1B38D59@PST.JCK.COM> <p0624066dca44df0ca50f@loud.pensive.org> <49A68144182BB270C11BC841@PST.JCK.COM> <sdlivza8hf.fsf@wjh.hardakers.net> <Pine.LNX.4.64.1107150906590.16878@egate.xpasc.com>
To: David Morris <dwm@xpasc.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1310746475; i=@mrochek.com; bh=7ZbWEFD9I/+5G8h9IbqHjEMiz5COVzBk/M1jV4S17kU=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=junA73RM3YwoQJ3s+5+mFYSR53SknI5FDW4Fe8flCX37niodYmUcoBL99bGkKdw4O StgRcJCdTDgPJL/4wxox+UJy0IDesB07a6h7i5wo/yPu+Bv0d9PuiL/gqePf3lvycA hH7Y4sodY12391oPpkS3iebJUYR4Nx7y6L3AMINw=
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, 15 Jul 2011 16:15:32 -0000

> > Obviously we need to take a typical step back first and determine the
> > scope of the problem.  We need to commission a "requirements for noise"
> > ID first.

> Can we schedule a BOF? Perhaps a symbolic burning of notices?

Wouldn't that be a BON rather than BOF?

				Ned

From tfl@psp.co.uk  Thu Jul 14 08:45:02 2011
Return-Path: <tfl@psp.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 3D6CF21F8C19; Thu, 14 Jul 2011 08:45:02 -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 mae8MIibsuAr; Thu, 14 Jul 2011 08:45:01 -0700 (PDT)
Received: from mail140.messagelabs.com (mail140.messagelabs.com [85.158.137.83]) by ietfa.amsl.com (Postfix) with ESMTP id 4A2F421F8C0D; Thu, 14 Jul 2011 08:45:00 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: tfl@psp.co.uk
X-Msg-Ref: server-13.tower-140.messagelabs.com!1310658281!32788904!44
X-StarScan-Version: 6.2.17; banners=psp.co.uk,-,-
X-Originating-IP: [217.28.130.38]
Received: (qmail 17214 invoked from network); 14 Jul 2011 15:44:58 -0000
Received: from hostedexchange.hostedservice.com (HELO outlook.hostedservice2.net) (217.28.130.38) by server-13.tower-140.messagelabs.com with RC4-SHA encrypted SMTP; 14 Jul 2011 15:44:58 -0000
Received: from THHS2E12BE2X.hostedservice2.net ([fe80:0000:0000:0000:e841:4ed5:117.193.90.34]) by thhs2e12ht02.hostedservice2.net ([192.168.16.112]) with mapi; Thu, 14 Jul 2011 16:45:07 +0100
From: Thomas Lee <tfl@psp.co.uk>
To: David Allan I <david.i.allan@ericsson.com>, "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>, "loa@pi.nu" <loa@pi.nu>, Rui Costa <RCosta@ptinovacao.pt>
Date: Thu, 14 Jul 2011 16:44:55 +0100
Subject: RE: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>	 and SPAM
Thread-Topic: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>	 and SPAM
Thread-Index: AcxCPPpOu5rYNxG5SGG+fYF8Fkr+eg==
Message-ID: <F00FA9CEAAB0544CA1F119C69377132B3B9ED35349@THHS2E12BE2X.hostedservice2.net>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 15 Jul 2011 09:21:31 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jul 2011 15:45:02 -0000

guys - does EVERYONE need to see this - I've removed some of the list alia=
ses to bcc - please be careful when you REPLY all

-----Original Message-----
From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.or=
g] On Behalf Of David Allan I
Sent: Wednesday, July 13, 2011 11:24 PM
To: erminio.ottone_69@libero.it; loa@pi.nu; Rui Costa
Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
Subject: RE: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05=
.txt> (Proactive Connectivity Verification, Continuity Check and Remote De=
fect indication for MPLS Transport Profile) to Proposed Standard

HI Erminio:

The comments that were raised during the day long discussion with the edit=
ors at the SG15 plenary resulted in those comments appearing in the liasio=
n IMO in an actionable form and resulted in a constructive outcome. I enjo=
yed that level of cooperation.

The comments that were punted over the wall with no discussion (depsite re=
quests to allocate meeting time to do so) in some cases were sufficiently =
vague as to have no constructive value or not have a recognizable issue to=
 be addressed.

A request to have the commenters identified in the liaison so that comment=
s that were unclear could be followed up upon by the editors was refused. =
Apparently that is not done and I would go so far as to suggest that blank=
et of anonymity diminished the quality of the liaison.  The result of this=
 process was that the only recourse to go "what does this mean?" was a com=
plete liaison cycle. For some comments, stomaching a multi-month delay to =
clarify what the actual issue was that resulted in a comment like "describ=
e the start-up procedure" was not reasonable, especially given SG15s conti=
nual complaint on how slow the IETF was. Such comments had to be weighed a=
gainst the nature of comments from the larger reviewing community that see=
med to have no issue with the completeness of the document content and per=
haps had actually read it and the supporting documents.

I'll call out an example: a comment that appeared more than once in the li=
aison was "clarify the raising/clearing of defects as well as any conseque=
nt actions" which I can only interpret as section 3.7 of the document not =
having been read. E.g. the TOC is:

3.7.1. Session initiation and Modification=0913
3.7.2. Defect entry criteria=09=09=09=0913
3.7.3. Defect entry consequent action=09=0914
3.7.4. Defect exit criteria=09=09=09=0915
3.7.5. State machines=09=09=09=09=0915

...and if there was a deficiency in the descriptions it was not identified=
, and we're not mind readers.

So that is both the history and why some comments were rejected. If you ca=
n suggest a constructive way to proceed that is not simply a waste of ever=
yone's time, I'll listen..

Cheers
Dave








-----Original Message-----
From: erminio.ottone_69@libero.it [mailto:erminio.ottone_69@libero.it]
Sent: Wednesday, July 13, 2011 1:28 PM
To: David Allan I; loa@pi.nu; Rui Costa
Cc: mpls@ietf.org; ietf@ietf.org; IETF-Announce
Subject: R: RE: [mpls] R: Re: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.=
txt> (Proactive Connectivity Verification, Continuity Check and Remote Def=
ect indication for MPLS Transport Profile) to Proposed Standard

Do you mean that ITU-T comments were discussed and resolution agreed durin=
g the ITU-T meeting?

If this is the case, why the LS just provides the comments and not the agr=
eed resolution?

Why some ITU-T comments have been then rejected?

>----Messaggio originale----
>Da: david.i.allan@ericsson.com
>Data: 6-lug-2011 19.35
>A: "erminio.ottone_69@libero.it"<erminio.ottone_69@libero.it>, "loa@pi.nu=
"
<loa@pi.nu>, "Rui Costa"<RCosta@ptinovacao.pt>
>Cc: "mpls@ietf.org"<mpls@ietf.org>, "ietf@ietf.org"<ietf@ietf.org>,
>"IETF-
Announce"<ietf-announce@ietf.org>
>Ogg: RE: [mpls] R: Re: Last Call:=09&lt;draft-ietf-mpls-tp-cc-cv-rdi-05.t=
xt&gt;=09
(Proactive Connectivity=09Verification, Continuity Check and Remote Defect=
=20
indication for=09MPLS=09Transport=09Profile) to Proposed Standard
>
>Hi Erminio:
>
>Two of the three document editors were present at SG15 plenary in=20
>February
where the comments originated. The revised meeting schedule resulted in a =
day spent going through the document with the editors. IMO there were lots=
 of discussion and legitimate issues with the document identified and corr=
ected so it was a useful session. The liaison of same was in many ways *af=
ter the fact*.
>
>Cheers
>Dave
>


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email _______=
_______________________________________________________________

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email=20
______________________________________________________________________

From kpfleming@digium.com  Thu Jul 14 08:50:04 2011
Return-Path: <kpfleming@digium.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8925821F8CA6; Thu, 14 Jul 2011 08:50:04 -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_15=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 44uzHDiCWYtd; Thu, 14 Jul 2011 08:49:59 -0700 (PDT)
Received: from mail.digium.com (mail.digium.com [216.207.245.2]) by ietfa.amsl.com (Postfix) with ESMTP id 80D3921F8C9B; Thu, 14 Jul 2011 08:49:59 -0700 (PDT)
Received: from zimbra.digium.internal ([10.24.55.203] helo=zimbra.hsv.digium.com) by mail.digium.com with esmtp (Exim 4.69) (envelope-from <kpfleming@digium.com>) id 1QhOAm-0000GR-4M; Thu, 14 Jul 2011 10:49:56 -0500
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.hsv.digium.com (Postfix) with ESMTP id 2409CD8024; Thu, 14 Jul 2011 10:49:56 -0500 (CDT)
Received: from zimbra.hsv.digium.com ([127.0.0.1]) by localhost (zimbra.hsv.digium.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id COmIhJibR-Wp; Thu, 14 Jul 2011 10:49:51 -0500 (CDT)
Received: from [10.24.250.46] (unknown [10.24.250.46]) by zimbra.hsv.digium.com (Postfix) with ESMTPSA id 963B9D82A3; Thu, 14 Jul 2011 10:49:51 -0500 (CDT)
Message-ID: <4E1F101E.5070007@digium.com>
Date: Thu, 14 Jul 2011 10:49:50 -0500
From: "Kevin P. Fleming" <kpfleming@digium.com>
Organization: Digium, Inc.
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10
MIME-Version: 1.0
To: Greg Mirsky <gregimirsky@gmail.com>
Subject: Re: [mpls] R: RE: Last Call: <draft-ietf-mpls-tp-cc-cv-rdi-05.txt> (Proactive Connectivity Verification, Continuity Check and Remote Defect indication for MPLS Transport Profile) to Proposed Standard
References: <947166.3310311310589521384.JavaMail.defaultUser@defaultHost> <CA+RyBmWMVsrx2GTy8zDYoqB7BQaTPcgQoWKyDOrHShCzdYCSwA@mail.gmail.com>
In-Reply-To: <CA+RyBmWMVsrx2GTy8zDYoqB7BQaTPcgQoWKyDOrHShCzdYCSwA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 15 Jul 2011 09:21:31 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, david.i.allan@ericsson.com, "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>, IETF-Announce <ietf-announce@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, 14 Jul 2011 15:50:04 -0000

On 07/13/2011 09:57 PM, Greg Mirsky wrote:
> Dear Erminio,
> I'd point that the scope of G.8113.1, a.k.a G.tpoam in regard to CCM is
> even more narrow then of the document being discussed. The G.8113.1
> addresses only bi-directional co-routed LSP and has no model to handle
> bi-directional associated LSP in independent mode. And unidirectional
> p2p and p2mp LSPs are not addressed by the current revision of the G.8113.1.
> Can all these out-of-scope constructs be used to conclude that G.8113.1
> is not capable to solve these issues? I don't think so. Solutions are
> not readily available, that's all.

Can you guys all drop the ietf-announce list from this thread, please? 
This list is not for technical discussions. Thanks.

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: kfleming@digium.com | SIP: kpfleming@digium.com | Skype: kpfleming
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at www.digium.com & www.asterisk.org

From ben@nostrum.com  Thu Jul 14 14:10:13 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 CF67721F8B48; Thu, 14 Jul 2011 14:10:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bOcDN3-Jqp+t; Thu, 14 Jul 2011 14:10:09 -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 039C921F8B65; Thu, 14 Jul 2011 14:10:08 -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 p6EL9a6Q052487 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 14 Jul 2011 16:09:36 -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-shiomoto-ccamp-switch-programming
Date: Thu, 14 Jul 2011 16:09:35 -0500
Message-Id: <F18F3E79-4E0C-4071-B85D-638D3BD0FD6D@nostrum.com>
To: draft-shiomoto-ccamp-switch-programming.all@tools.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: Fri, 15 Jul 2011 09:21:31 -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: Thu, 14 Jul 2011 21:10: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-shiomoto-ccamp-switch-programming-05
Reviewer: Ben Campbell
Review Date: 2011-07-14
IETF LC End Date: 2011-07-18


Summary: Ready for publication as an informational RFC

Major issues:

None

Minor issues:

None

Nits/editorial comments:

-- section 1, paragraph 4: "...with relation to the programming..."

... in relation to...

-- 3.1, last paragraph:

Note that the references say SHOULD rather than MUST. Using "must not" =
here, even non-normatively, seems a bit overstated.=

From hideki.endo.es@hitachi.com  Fri Jul 15 05:17:39 2011
Return-Path: <hideki.endo.es@hitachi.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D96E21F868A; Fri, 15 Jul 2011 05:17:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.66
X-Spam-Level: 
X-Spam-Status: No, score=0.66 tagged_above=-999 required=5 tests=[AWL=-0.250,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, SUBJ_RE_NUM=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 p0h1NAAMESt4; Fri, 15 Jul 2011 05:17:35 -0700 (PDT)
Received: from mail7.hitachi.co.jp (mail7.hitachi.co.jp [133.145.228.42]) by ietfa.amsl.com (Postfix) with ESMTP id 3CB3521F8681; Fri, 15 Jul 2011 05:17:34 -0700 (PDT)
Received: from mlsv4.hitachi.co.jp (unknown [133.144.234.166]) by mail7.hitachi.co.jp (Postfix) with ESMTP id 3EE9C37AC4; Fri, 15 Jul 2011 21:17:33 +0900 (JST)
Received: from mfilter03.hitachi.co.jp by mlsv4.hitachi.co.jp (8.13.1/8.13.1) id p6FCHXSn026561; Fri, 15 Jul 2011 21:17:33 +0900
Received: from vshuts2.hitachi.co.jp (vshuts2.hitachi.co.jp [10.201.6.71]) by mfilter03.hitachi.co.jp (Switch-3.3.4/Switch-3.3.4) with ESMTP id p6FCHW6W029918; Fri, 15 Jul 2011 21:17:32 +0900
X-AuditID: b753bd60-a1e7aba0000050a4-ac-4e202fdc2e3e
Received: from gmml25.itg.hitachi.co.jp (unknown [158.213.165.145]) by vshuts2.hitachi.co.jp (Symantec Mail Security) with ESMTP id 138108B0306; Fri, 15 Jul 2011 21:17:32 +0900 (JST)
Received: from [127.0.0.1] by gmml25.itg.hitachi.co.jp (AIX5.2/8.11.6p2/8.11.0) id p6FCHWc29958168; Fri, 15 Jul 2011 21:17:32 +0900
Message-Type: Multiple Part
MIME-Version: 1.0
Message-ID: <XNM1$7$0$0$$6$1$2$A$5001649U4e202fb7@hitachi.com>
Content-Type: text/plain; charset=us-ascii
To: <Robert.Rennison@ecitele.com>
From: <hideki.endo.es@hitachi.com>
Date: Fri, 15 Jul 2011 21:17:10 +0900
References: <20110630134642.1281.3095.idtracker@ietfa.amsl.com> <XNM1$7$0$0$$6$1$2$A$5001645U4e1ed16c@hitachi.com> <786AD2EC3D80A1428B921CDC9BE9EE546BB7CDB872@USPITMAIL01.ecitele.c>
Priority: normal
Importance: normal
Subject: Re[2]: [mpls] Last Call:<draft-ietf-mpls-tp-cc-cv-rdi-05.txt>(Proactive Connecti
X400-Content-Identifier: X4E202FB700000M
X400-MTS-Identifier: [/C=JP/ADMD=HITNET/PRMD=HITACHI/;gmml28110715211655MD7]
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
X-Mailman-Approved-At: Fri, 15 Jul 2011 09:21:31 -0700
Cc: mpls@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, 15 Jul 2011 12:17:39 -0000

Hi Robert,

Thank you very much for your reply, 
and I am sorry for my late response.

See inline, marked with [HE];

>
>________________________________________
>From: mpls-bounces@ietf.org [mpls-bounces@ietf.org] On Behalf Of hideki.endo.es@hitachi.com [hideki.endo.es@hitachi.com]
>Sent: Thursday, July 14, 2011 7:22 AM
>To: ietf@ietf.or; mpls@ietf.org
>Subject: Re: [mpls] Last Call:  <draft-ietf-mpls-tp-cc-cv-rdi-05.txt>(Proactive Connectivit
>
>>The changes in this version have massive impact for CC/CV/RDI implementation.
>>We, venders, have kept making efforts on interoperability test again and again.
>>These changes spoil this effort.
>
>>Especially, revival of Poll/Final sequence doesn't make sense.
>>Originally, in my understanding, Poll/Final sequence was excluded from this draft
>>to avoid making HW implementation difficult.
>
>[RR] preventing a peer from modifying the rate once the initial target rate was achieved  i.e arbitrary re-negotiation was  and is excluded, that was the "problem"  the group consensus was  to solve. 
>
>
>However P/F is needed to get from the initial 1 per second default rate to the desired rate. This and the rational for an initial P/F were discussed in detail back in March /April.
[HE]My understanding is far from yours.
The cc-cv-rdi-03 said 
"Poll/final discipline can only used for VCCV and UDP/IP encapsulated BFD.".
In my understanding, this meant that Poll/Final Sequence MUST NOT be used for GAL/G-ACh.
In other words, GAL/G-ACh MUST work well without Poll/Final Sequence
in the case of getting from initial state.
I think this was the group consensus.
If the consensus was only for re-negotiation, why was P/F excluded from GAL/G-ACh? 

>
>
>>Even though it was difficult to change CC interval arbitrary,
>>the problem should be solved by defining how to transit DOWN/INIT state to UP state.
>
>[RR] There is no problem in defining how to transit from Down/Init to UP state, it's covered in the existing state machine and is not changed. 
[HE]Sorry for lack of explanation.
I meant the interval change timing should be defined in the case of transition DOWN/INIT to UP state
without P/F sequence for GAL/G-ACh.

BR,
Hideki


>
>Cheers
>
>Rob
>
>
>>The direction which reached consensus once should NOT be changed easily
>>in order to respond to the market requirements.
>
>>IMO, such major changes should NOT be added right before becoming RFC.
>
>>I found at least four major/minor changes as follows;
>>1)Revival of Poll/Final sequence
>>2)Change of MEP ID formats
>>3)Change of Diag. Code
>>4)Change of CV interleaved definition
>
>BR,
>Hideki
>
>
>>
>>The IESG has received a request from the Multiprotocol Label Switching WG
>>(mpls) to consider the following document:
>>- 'Proactive Connectivity Verification, Continuity Check and Remote
>>   Defect indication for MPLS Transport Profile'
>>  <draft-ietf-mpls-tp-cc-cv-rdi-05.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-07-14. Exceptionally, comments may be
>>sent to iesg@ietf.org instead. In either case, please retain the
>>beginning of the Subject line to allow automated sorting.
>>
>>Abstract
>>
>>   Continuity Check, Proactive Connectivity Verification and Remote
>>   Defect Indication functionalities are required for MPLS-TP OAM.
>>
>>   Continuity Check monitors the integrity of the continuity of the
>>   label switched path for any loss of continuity defect. Connectivity
>>   verification monitors the integrity of the routing of the label
>>   switched path between sink and source for any connectivity issues.
>>   Remote defect indication enables an End Point to report, to its
>>   associated End Point, a fault or defect condition that it detects on
>>   a pseudo wire, label switched path or Section.
>>
>>   This document specifies methods for proactive continuity check,
>>   continuity verification, and remote defect indication for MPLS-TP
>>   label switched paths, pseudo wires and Sections using Bidirectional
>>   Forwarding Detection.
>>
>>
>>The file can be obtained via
>>http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>>
>>IESG discussion can be tracked via
>>http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/
>>
>>
>>No IPR declarations have been submitted directly on this I-D.
>>_______________________________________________
>>mpls mailing list
>>mpls@ietf.org
>>https://www.ietf.org/mailman/listinfo/mpls
>>
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls
>
>
>This e-mail message is intended for the recipient only and contains information which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this transmission in error, please inform us by e-mail, phone or fax, and then delete the original and all copies thereof.
>
>

From joelja@bogus.com  Fri Jul 15 09:41: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 E123721F8B4C; Fri, 15 Jul 2011 09:41:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level: 
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[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 uouSgDY02OTc; Fri, 15 Jul 2011 09:41:03 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id AE4F821F8B4B; Fri, 15 Jul 2011 09:40:59 -0700 (PDT)
Received: from [10.179.81.29] (254.sub-166-250-32.myvzw.com [166.250.32.254]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p6FGer8w066061 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 15 Jul 2011 16:40:55 GMT (envelope-from joelja@bogus.com)
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <DB5571A0CF3C3F570576A23F@PST.JCK.COM>
Date: Fri, 15 Jul 2011 09:40:47 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <BBB3AB81-1A20-4022-8687-CD88B000B281@bogus.com>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.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, 15 Jul 2011 16:40:58 +0000 (UTC)
Cc: 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, 15 Jul 2011 16:41:04 -0000

So the rational for the advice document not being combined with the =
standards action in it is that the later has some polarizing impact, the =
advice document does not. the advice document is through and done, =
historic is not.

On Jul 15, 2011, at 8:55 AM, John C Klensin wrote:

> Hi.
>=20
> I've been thinking about this and having a few off-list
> conversations and want to make a suggestion that draws together
> a few others.  Since many people don't like my long notes with
> the conclusion at the end, this one is suggestion-first.  If the
> suggestion offends you sufficiently, you can just stop reading
> there.
>=20
> Recommendation:
>=20
> (1) Abandon the effort to classify the specifications as
> Historic.  It is at best a symbolic act that few people outside
> the IETF community will even notice, much less act differently
> because we have done it.  Instead, let's try to focus on what is
> actually important, not classification and name-called ("curse
> you, you Historic protocol" :-(  ).
>=20
> (2) Pull the "-advice" document back from the RFC Editor queue
> and fold the actual substantive content of the "-historic"
> document into it, preferably as a very clear and very prominent
> Applicability Statement.  If this is what v6ops believes, the
> statement might reasonably say something like:
>=20
> 	(2a) This protocol, if not used very carefully, leads to
> 	bad operational situations in which things get lost and
> 	the problems are hard to diagnose.   We strongly
> 	recommend that it not ever be a default and that it not
> 	be used except under special circumstances and with
> 	great care.
> =09
> 	(2b) Even then, we recommend that it not be used unless
> 	all of those configuring routing information and all the
> 	systems along the routing path are run by experts who
> 	both understanding the issues and are willing to accept
> 	responsibility.
> =09
> 	(2c) If you do decide to use the thing, the "advice"
> 	recommendations in the rest of this document are
> 	mandatory and MUST be followed to avoid serious
> 	operational problems.
>=20
> I haven't included either Randy's colorful language or mine in
> the example above, but the intent should be clear.  Depending on
> how much detail the community thinks is useful, there is a good
> deal of potentially-useful text in draft-moore-6to4-experimental
> as well as in the "-historic" draft.
>=20
> The resulting document should explicitly update RFC3056 and
> RFC3068.  Taking that action will send a much stronger "you need
> to read that document before doing anything with this one"
> message to most of the people who are familiar with how things
> work than a reclassification of the base documents.  For those
> who aren't familiar with how things work, all of these
> approaches, including moving 6to4 to Historic, are pointless.
>=20
> That is all.  This can and should be made to sound like mature
> engineering advice, which it presumably is, and not like small
> children throwing mud at each other.
>=20
>=20
> Explanation and Rants:
>=20
> (ii) I think moving _this_ protocol to Experimental is just
> silly.  We use Experimental for things that are
> pre-standardization or not sufficiently mature to be
> standardized.  Although the bar is higher, there are elements of
> "experiment" in every Proposed Standard --that is why we have a
> multiple-step standardization process.   If there is really
> something to be learned from 6to4 operated in a different way,
> then the right action to take would be to propose a 6to4bis that
> outlines the characteristics of the protocol, eliminates
> anything we have concluded should not be done, and outlines the
> desired experiment.  That document might reasonably be listed as
> updating RFC3056 and RFC3068 as well. =20
>=20
> (i) <rant> Presumably our goal is to get IPv6 deployed and
> provide advice useful to its deployment, independent of any
> particular piece of protocol or transition arrangement.  At
> least one of the many reasons we haven't seen more deployment is
> that we keep sending messages to the broader community that,
> however unintentionally, discourage that deployment.  In the
> early days of IPv6, we did that by advertising (or letting
> others who were presumed to be speaking for us advertise) that
> IPv6 was completely ready and that transition was going to be
> easy, cheap, and seamless.  For those who had to make decisions
> as to when to deploy IPv6, sufficient investigation tp discover
> that some of that story was untrue became sufficient motivation
> to back away from IPv6 entirely until we got our acts together.
> In more recent years, we have continued to deliver the message
> that the IETF (and, to a lesser extent the RIRs) are simply
> confused about what advice to give and therefore that IPv6 isn't
> ready for someone to deploy who suffers from limited resources
> and a strong desire to do it only when all of the ducks are
> lined up.  Every time we propose a new transition model or
> denounce an old one without what seems to be an
> externally-convincing analysis of the complete picture, we make
> things worse by distributing yet another chapter of "even the
> IETF has no real idea how to transition to IPv6".
>=20
> If we are serious about encouraging deployment of IPv6 -- and I
> hope we are -- then it is time to stop the apparent war among
> transition strategies.  It seems to me that the document that is
> needed is a vastly strengthened (and probably standards-track)
> version of RFC 6180 (a rather nice document that I would
> encourage those who are engaged in the 6to4 debate on the IETF
> list to read), but one that goes beyond such statements as=20
>=20
> 	There are several types of tunneling mechanisms,
> 	including manually configured IPv6-over-IPv4 tunnels
> 	[RFC4213], 6to4 [RFC3056], automatic host-based tunnels
> 	[RFC4380], tunnel brokers [RFC3053], running IPv6 over
> 	MPLS with IPv6 Provider Edge Routers (6PE) [RFC4798],
> 	the use of Virtual Private Networks (VPNs) or mobility
> 	tunnels to carry both IPv4 and IPv6 [RFC4301] [RFC5454]
> 	[RFC5555] [RFC5844], and many others.
>=20
> (from Section 4.2) and into a serious discussion of the
> scenarios that are the best match to different of these
> strategies (and others).  If we don't know, then let's say,
> explicitly, that we haven't had quite enough experience to
> provide a differential chart of when particular techniques can
> be used but that they are out their, with their strengths and
> weaknesses, for situations to which they seem well-adapted.  It
> is almost possible to infer from 6180's conclusions that almost
> all transition mechanisms are equivalent, at least within
> groups, and those that aren't are best dealt with by public
> burning.  Clearly we don't believe the first part of that; we
> should get away from the appearance of believing the second.
>=20
> And, again and most important, if we want to see IPv6 deployed,
> we need a clear message that we actually understand what we are
> doing, that we have a coherent picture, and that our process is
> not one of lurching among solutions, hoping that each one will
> be the magic bullet, and then denouncing any that turn out to
> not have sufficient magical properties.  The marketplace knows
> how to deal with the message we are sending with debates about
> recategorization and we have already seen the answer: it isn't
> the universal deployment of IPv6 before now or any time soon.
> </rant>
>=20
>    john
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From sm@resistor.net  Fri Jul 15 10:21: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 3DA1021F8B36 for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 10:21:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IXTLiDh+AC8l for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 10:21:20 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id B776721F8B06 for <ietf@ietf.org>; Fri, 15 Jul 2011 10:21:19 -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 p6FHL3CY020513;  Fri, 15 Jul 2011 10:21:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1310750471; bh=t3hruGDBaSJQyR7ZzTfI4L20FAKk2eTo0KPm3Q6qfKM=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=fbXm/I3PAnJ9EMhXOAjKesxxJWMxFUX0scr6UwuHp+Vf1fspKRJb7D0y6AaquNaIG HXnD310U2wmGTYwHVX4oEHMo4OO2hITFlcRqt1rphE8LneqLdMe/xQuZ7C50Kb3HiZ Xs3tIseAfy/nsIiHlfUQek8osQrjKxXCSyBCO4Ms=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1310750471; bh=t3hruGDBaSJQyR7ZzTfI4L20FAKk2eTo0KPm3Q6qfKM=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=hv9nCPTAVvsMefWvpDTYS3v4albWt0IyeDc1yIZNR8DPgRGagkGkfjQ/BHNXCG0pX R+HJwqngQKUdenU7LRKQBpXqO3yzjHjxNrTrxfsllSP784u7FnGtRRX49ZULFQQz+0 K6fQvn4bx6OJ3HKfYE82opi9NucWwyMOC1dtKdO8=
Message-Id: <6.2.5.6.2.20110715085806.039b2d60@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 15 Jul 2011 10:19:43 -0700
To: Harald Alvestrand <harald@alvestrand.no>
From: SM <sm@resistor.net>
Subject: Re: Review of draft-yevstifeyev-ion-report-06
In-Reply-To: <4E205A5D.1020304@alvestrand.no>
References: <4D91EBDE.5070703@gmail.com> <4E205A5D.1020304@alvestrand.no>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 15 Jul 2011 17:21:27 -0000

Hi Harald,
At 08:18 15-07-2011, Harald Alvestrand wrote:
>The document does not refer back to the aims of the experiment, 
>which I tried to make explicit in section 5 of RFC 4693, which include:
>
>- Easy updating
>- Explicit approval
>- Accessible history
>
>The sum total of analysis in this document is two sentences:
>The cited IESG statement
>
>      It is clear that the IESG, IAB, and IAOC need the ability to
>      publish documents that do not expire and are easily updated.
>      Information published as web pages, including IESG Statements, are
>      sufficient for this purpose.
>
>The draft's statement
>
>    Taking everything into account, it was considered that IONs added
>    complications to the maintenance of documents but did not give a
>    corresponding benefit to the IETF.
>
>I would at least expect those three points to be explicitly 
>addressed by analysis, such as:

I'll quote some text from Section 5 of RFC 4693:

   "The IETF is an open organization, which means (among other things)
    that there are always newcomers coming in to learn how to perform
    work; this places a requirement on the organization to document its
    processes and procedures in an accessible manner."

There is a steep learning curve for newcomers.  One of the ways for 
some people to learn is by reading the RFCs.  Sometimes these 
documents do not reflect current practice.  That is not obvious to 
newcomers who are not aware of the open secrets which seems to be 
common knowledge within the IETF.

There are times when an experiment fails.  When there isn't any 
documentation, one has to rely on those with "institutional" memory 
to pass down the history.

   "The IETF is also a large organization, which means that when
    procedures change, there are a number of people who will like to know
    of the change, to figure out what has changed, and possibly to
    protest or appeal the change if they disagree with it."

It can also be important to understand why it may not be feasible to 
adopt a procedure that has been tried previously.

Commenting on Section 3.2 of draft-yevstifeyev-ion-report-06, "URIs 
don't change: people change them".  The IETF makes an effort to 
preserve old URIs so that its web pages does not expire.  Sometimes a 
document falls through the cracks [1].

The ION experiment is a failure if only because the IETF has yet to 
come to terms with the notion of "lessons learnt".

Regards,
-sm

1. http://www.ietf.org/IESG/STATEMENTS/tsv-alt-cc.txt
    http://www.ietf.org/iesg/STATEMENTS/ad-sponsoring.html
    http://www.ietf.org/iesg/content/agenda-minutes-procedures.html



From d3e3e3@gmail.com  Fri Jul 15 10:26:35 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 71EB121F8B7B for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 10:26:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.349
X-Spam-Level: 
X-Spam-Status: No, score=-104.349 tagged_above=-999 required=5 tests=[AWL=-0.750, 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 ZuHtV6y6P3+0 for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 10:26:35 -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 B87D421F8B60 for <ietf@ietf.org>; Fri, 15 Jul 2011 10:26:32 -0700 (PDT)
Received: by gwb20 with SMTP id 20so700077gwb.31 for <ietf@ietf.org>; Fri, 15 Jul 2011 10:26:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=bHMDhT1yMEOirXP3eU1RwMs0o9HhELrVuMZff7EDsx0=; b=DfkEYSzlk+6Y5kO3edcuamGDKojY3PjRkaFoI/F/blg4P7wTuF2Q2YrzeeWA4Qfykc VsVeQR/zqE+HFMnnvgVp1sQIKws7vF5E9JU8nfTT5Ba4V6AL6QAhXHkW6drOuRtvoyIs kGeFLhaA1oAcBnViesjwkU5QLDCXcWt13JN2k=
Received: by 10.150.160.1 with SMTP id i1mr756968ybe.157.1310750792133; Fri, 15 Jul 2011 10:26:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.151.144.3 with HTTP; Fri, 15 Jul 2011 10:26:12 -0700 (PDT)
In-Reply-To: <01O3O60PAEKG00VHKR@mauve.mrochek.com>
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <29987.1310565058@marajade.sandelman.ca> <4E1DCA13.9030301@acm.org> <04AE56F0C4CE8168D1B38D59@PST.JCK.COM> <p0624066dca44df0ca50f@loud.pensive.org> <49A68144182BB270C11BC841@PST.JCK.COM> <sdlivza8hf.fsf@wjh.hardakers.net> <Pine.LNX.4.64.1107150906590.16878@egate.xpasc.com> <01O3O60PAEKG00VHKR@mauve.mrochek.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 15 Jul 2011 13:26:12 -0400
Message-ID: <CAF4+nEG-n3-otfbfRA4nb0TWvcBfm1juvaXBrR21MCzLv1veKg@mail.gmail.com>
Subject: Re: Confidentiality notices on email messages
To: ned+ietf@mauve.mrochek.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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, 15 Jul 2011 17:26:35 -0000

On Fri, Jul 15, 2011 at 12:14 PM,  <ned+ietf@mauve.mrochek.com> wrote:
>> > Obviously we need to take a typical step back first and determine the
>> > scope of the problem. =A0We need to commission a "requirements for noi=
se"
>> > ID first.
>
>> Can we schedule a BOF? Perhaps a symbolic burning of notices?
>
> Wouldn't that be a BON rather than BOF?

Don't you mean BON-fire...

Donald

> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Ned

From samirs.lists@gmail.com  Fri Jul 15 11:30:24 2011
Return-Path: <samirs.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 3AD3621F8BA2 for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 11:30:24 -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_43=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 boUjn+E33PS0 for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 11:30:23 -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 DA01A21F8BA3 for <ietf@ietf.org>; Fri, 15 Jul 2011 11:30:22 -0700 (PDT)
Received: by vws12 with SMTP id 12so1519372vws.31 for <ietf@ietf.org>; Fri, 15 Jul 2011 11:30:22 -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=I0SUL7UnnIwFcBt2Nw5oCMTND2gY2zHWk8NXKqC83H8=; b=IN3y3FQ5CvgWDoES0wUHTWYt6yxrMTlFzStmlDZxfD7ofOcDbBPx6vVyXILKJflOLL vNJbi4W8xmbR33PvcNNr8PLYtBtQJJ4vO/9Hw8InJ3Vz4RwR7uSiZ1oJcYeJAW0JR5tL fXrUN2DRH4iDopMrEDlSSji1ZqCdaXqWibHSg=
MIME-Version: 1.0
Received: by 10.52.100.98 with SMTP id ex2mr51104vdb.194.1310754622024; Fri, 15 Jul 2011 11:30:22 -0700 (PDT)
Received: by 10.52.181.104 with HTTP; Fri, 15 Jul 2011 11:30:22 -0700 (PDT)
In-Reply-To: <CAK+SpizC2EaT8rogpeGHTzdua-DhEGd-DC_jqv55Z3Qu4kLd4w@mail.gmail.com>
References: <CAK+Spiz3O_b16MZ=BoFyht38DqZsMena6_cZZ5CcaN9mGxpwBA@mail.gmail.com> <CAK+SpizC2EaT8rogpeGHTzdua-DhEGd-DC_jqv55Z3Qu4kLd4w@mail.gmail.com>
Date: Fri, 15 Jul 2011 11:30:22 -0700
Message-ID: <CAK+Spiz_Thu6-PRZ2DV0d7=oE_9RxrPLqfUHmQP76NtBYpnG6w@mail.gmail.com>
Subject: Re: Call for opinion on impact of cashless economy on 'Security Consideration'
From: Samir Srivastava <samirs.lists@gmail.com>
To: ietf@ietf.org, postmaster@nobel.no, vk@khoslaventures.com,  desk@abcnews4.com, dw@khoslaventures.com
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, 15 Jul 2011 18:30:24 -0000

Hi, I am resending. Are the parties mentioned waiting for the email
keeping legal time limit ( if it is 4 years in US) to expire. Can
someone advise me on this time limit? Due to unavoidable situation, I
have limited internet access. I hope parties will reply ASAP. Regards
Samir

On 7/12/11, Samir Srivastava <samirs.lists@gmail.com> wrote:
> Added more on the distribution list regards  Samir Srivastava
>
> On 7/12/11, Samir Srivastava <samirs.lists@gmail.com> wrote:
>> Hi, Readers use information given in this message at thier own risk.
>> Author cannot be held responsible for damages/consequences caused.
>> Refer http://samirsrivastava.typepad.com. Search wipo.int for patents
>> by me. Work has potential to impact security consideration of IETF
>> docs.  Awarding a prize is in the sole discretion of awarding
>> organization.Yet nobel peace prize to US President not clear. He was
>> awarded it for diplomacy within a year after becoming President. I
>> sent slide set on cashless economy to khosla ventures in 2007. When I
>> posted on alt.security.terrorism on nov-28-10, president went on
>> surprise trip to Afganistan. I suspect it is used for someting else
>> also. Due to various reasons referred work is not able to draw
>> attention from media and governments. I request parties mentioned on
>> email to clarify doubts on public forum. I request IETEers to review
>> it. BTW outstanding work of nobel winners is well known in advance.
>> Due to unavoidable situations I cannot submit draft.  Regards  Samir
>> Srivastava
>>
>

From john-ietf@jck.com  Fri Jul 15 11:52:34 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 5F4A221F8BF8; Fri, 15 Jul 2011 11:52:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.377
X-Spam-Level: 
X-Spam-Status: No, score=-102.377 tagged_above=-999 required=5 tests=[AWL=-0.378, 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 isLL5FU6LYyR; Fri, 15 Jul 2011 11:52:33 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 9EF5021F854A; Fri, 15 Jul 2011 11:52:33 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QhnV2-000GNf-UT; Fri, 15 Jul 2011 14:52:33 -0400
Date: Fri, 15 Jul 2011 14:52:32 -0400
From: John C Klensin <john-ietf@jck.com>
To: Joel Jaeggli <joelja@bogus.com>
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
Message-ID: <A6908373951C6911489DF57A@PST.JCK.COM>
In-Reply-To: <BBB3AB81-1A20-4022-8687-CD88B000B281@bogus.com>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <BBB3AB81-1A20-4022-8687-CD88B000B281@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: 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, 15 Jul 2011 18:52:34 -0000

--On Friday, July 15, 2011 09:40 -0700 Joel Jaeggli
<joelja@bogus.com> wrote:

> So the rational for the advice document not being combined
> with the standards action in it is that the later has some
> polarizing impact, the advice document does not. the advice
> document is through and done, historic is not.

Joel (and others),

I understand the rationale.  At the risk of repeating myself, I
simply do not think it works or is appropriate.  Recategorizing
set of documents as "Historic" is an extremely blunt instrument.
If we do it in a consistent and logical fashion, the advice
document would have to go to Historic along with the base
documents because giving advice about a piece of ancient history
is meaningless.  That is not what most people who like the
advice document intended, at least as I understood the consensus
on that Last Call.

Worse, for those who are successfully operating 6to4 and finding
it useful, reclassifying the specifications to Historic sends a
clear message that, from their perspective at least, the IETF is
clueless (since "Historic" essentially says the thing is useless
and/or that no one is using it... and they know better because
they are a counterexample).   The consequence of that, in turn,
is that they either simply ignore the advice or conclude that
they should postpone IPv6 deployment until the IETF gives advice
that is both coherent and believable.

I think there are probably a dozen "right" ways to do this, with
the differences depending on issues that I haven't followed
v6ops or 6to4 deployment closely enough to have opinions about.
What they have in common is a real analysis of issues and some
meaningful recommendations ("-advice" seems to do much of that)
and the used of "updates" to effectively incorporate that advice
and guidance into the base spec.   If that is better done with a
standalone document that references the base spec and the advice
document, updating all of them, I'm fine with it (although,
under that scenario, I'd prefer to have the advice document on
standards track).   

Finally, if we had a wonderful transition model that would work
well in all situations, then it would make sense to recommend it
and depreciate everything else.   We don't.  What we have are a
bunch of mechanisms, each with advantages and disadvantages,
some much better adapted to particular situations than others.
It would be easier if we had a good single solution, but we
don't... that is life, or at least engineering.  Given that, we
serve the community much better with analyses and explanations
of tradeoffs (and RFC 6180 is, IMO, a really good start) than we
do by going through exercises of figuring out what to denounce.
IMO, the _only_ thing we should be categorically denouncing are
tactics and strategies that encourage people to put off getting
serious about IPv6.  Unfortunately, trying to slap a "Historic"
label on one particular transition strategy, or to rank
transition strategies that have proven useful to some actors on
the basis of how much various of us loathe them, are about
denunciation and, however unintentionally, with the risk of
encouraging people to sit and wait, not about progress or
network engineering.

back to lurking...
    john



From joelja@bogus.com  Fri Jul 15 12:17:26 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 5DEB421F8C1E; Fri, 15 Jul 2011 12:17:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yiYqLVGIMwpK; Fri, 15 Jul 2011 12:17:25 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 8069021F8C12; Fri, 15 Jul 2011 12:17:25 -0700 (PDT)
Received: from [10.187.125.226] (254.sub-166-250-32.myvzw.com [166.250.32.254]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p6FJHLFX003131 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 15 Jul 2011 19:17:23 GMT (envelope-from joelja@bogus.com)
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <A6908373951C6911489DF57A@PST.JCK.COM>
Date: Fri, 15 Jul 2011 12:17:08 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <71D5A97D-7119-4082-BC87-6505370CE800@bogus.com>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <BBB3AB81-1A20-4022-8687-CD88B000B281@bogus.com> <A6908373951C6911489DF57A@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.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, 15 Jul 2011 19:17:24 +0000 (UTC)
Cc: 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, 15 Jul 2011 19:17:26 -0000

On Jul 15, 2011, at 11:52 AM, John C Klensin wrote:

>=20
>=20
> --On Friday, July 15, 2011 09:40 -0700 Joel Jaeggli
> <joelja@bogus.com> wrote:
>=20
>> So the rational for the advice document not being combined
>> with the standards action in it is that the later has some
>> polarizing impact, the advice document does not. the advice
>> document is through and done, historic is not.
>=20
> Joel (and others),
>=20
> I understand the rationale.  At the risk of repeating myself, I
> simply do not think it works or is appropriate.

And there are people that disagree with you on that.

>  Recategorizing
> set of documents as "Historic" is an extremely blunt instrument.
> If we do it in a consistent and logical fashion, the advice
> document would have to go to Historic along with the base
> documents because giving advice about a piece of ancient history
> is meaningless.  That is not what most people who like the
> advice document intended, at least as I understood the consensus
> on that Last Call.

<SNIP>

> Finally, if we had a wonderful transition model that would work
> well in all situations, then it would make sense to recommend it
> and depreciate everything else.

You missed the boat about a decade back I guess. Transition technologies =
(none of them) are a substitute for actual deployment. They should =
naturally decline in popularity and in fact in the portions of the =
internet where we can measure them they are. Right now if we try and fit =
a story to the evidence that is happening because of host changes, and  =
not because of deployment. ipv4 is becoming less usable and it's taking =
autotunnels with it, nobody here has a proposal that changes that.

>   We don't.  What we have are a
> bunch of mechanisms, each with advantages and disadvantages,
> some much better adapted to particular situations than others.
> It would be easier if we had a good single solution, but we
> don't... that is life, or at least engineering.  Given that, we
> serve the community much better with analyses and explanations
> of tradeoffs (and RFC 6180 is, IMO, a really good start) than we
> do by going through exercises of figuring out what to denounce.
> IMO, the _only_ thing we should be categorically denouncing are
> tactics and strategies that encourage people to put off getting
> serious about IPv6.  Unfortunately, trying to slap a "Historic"
> label on one particular transition strategy, or to rank
> transition strategies that have proven useful to some actors on
> the basis of how much various of us loathe them, are about
> denunciation and, however unintentionally, with the risk of
> encouraging people to sit and wait, not about progress or
> network engineering.
>=20
> back to lurking...
>    john
>=20
>=20


From Fred.L.Templin@boeing.com  Fri Jul 15 12:37:52 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 B936721F8C35; Fri, 15 Jul 2011 12:37:52 -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 VvUmQs1w+GO9; Fri, 15 Jul 2011 12:37:51 -0700 (PDT)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by ietfa.amsl.com (Postfix) with ESMTP id BB81621F8C32; Fri, 15 Jul 2011 12:37:51 -0700 (PDT)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by stl-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p6FJbcJR022084 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 15 Jul 2011 14:37:41 -0500 (CDT)
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 p6FJbc43017597; Fri, 15 Jul 2011 12:37:38 -0700 (PDT)
Received: from XCH-NWHT-02.nw.nos.boeing.com (xch-nwht-02.nw.nos.boeing.com [130.247.70.248]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p6FJbbUQ017573 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 15 Jul 2011 12:37:38 -0700 (PDT)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-02.nw.nos.boeing.com ([130.247.70.248]) with mapi; Fri, 15 Jul 2011 12:37:37 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joel Jaeggli <joelja@bogus.com>, John C Klensin <john-ietf@jck.com>
Date: Fri, 15 Jul 2011 12:37:36 -0700
Subject: RE: Another look at 6to4 (and other IPv6 transition issues)
Thread-Topic: Another look at 6to4 (and other IPv6 transition issues)
Thread-Index: AcxDI+EB7Z+L/w3xRMqKXIeVwrML3AAAogVw
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65C6B37F80F@XCH-NW-01V.nw.nos.boeing.com>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <BBB3AB81-1A20-4022-8687-CD88B000B281@bogus.com> <A6908373951C6911489DF57A@PST.JCK.COM> <71D5A97D-7119-4082-BC87-6505370CE800@bogus.com>
In-Reply-To: <71D5A97D-7119-4082-BC87-6505370CE800@bogus.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: "v6ops@ietf.org" <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, 15 Jul 2011 19:37:52 -0000

Hi Joel,=20

> ipv4 is becoming less usable and it's=20
> taking autotunnels with it, nobody here has a proposal that=20
> changes that.

As far as I can tell, IPv4 is not becoming less
usable within my organization's network.

Thanks - Fred
fred.l.templin@boeing.com=

From brian.e.carpenter@gmail.com  Fri Jul 15 13:34:45 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 3F6B521F8C47; Fri, 15 Jul 2011 13:34:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.524
X-Spam-Level: 
X-Spam-Status: No, score=-103.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 75J4kUL6F7Rk; Fri, 15 Jul 2011 13:34:44 -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 560C121F8C3D; Fri, 15 Jul 2011 13:34:44 -0700 (PDT)
Received: by fxe4 with SMTP id 4so3954804fxe.27 for <multiple recipients>; Fri, 15 Jul 2011 13:34:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=N/eNqSmoQ9LPsdTgyh5xmvayB6bNBPcd0wxPF3Hh1ls=; b=GJZwfRWfoEgbLG5YE35H1HFkvX2SZg9Y+CSsR77MJfuFvGL/0QhwCS3x2wiiF+G1WR 1eZ5WKXdJXrtyc7CuZXsKvChTs+GC8Sbs9nosdmmozjblnxFNYOFzltUK5zYOJCRIJLf PEFRZ9cInNMZcdolp2wl61iyETPlQVQIyWviA=
Received: by 10.223.1.201 with SMTP id 9mr5880637fag.91.1310762083283; Fri, 15 Jul 2011 13:34:43 -0700 (PDT)
Received: from ?IPv6:2001:388:f000::35? ([2001:388:f000::35]) by mx.google.com with ESMTPS id e10sm995743fak.42.2011.07.15.13.34.39 (version=SSLv3 cipher=OTHER); Fri, 15 Jul 2011 13:34:42 -0700 (PDT)
Message-ID: <4E20A44E.3060203@gmail.com>
Date: Sat, 16 Jul 2011 08:34:22 +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: Another look at 6to4 (and other IPv6 transition issues)
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM>
In-Reply-To: <DB5571A0CF3C3F570576A23F@PST.JCK.COM>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 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, 15 Jul 2011 20:34:45 -0000

On 2011-07-16 03:55, John C Klensin wrote:

> (2) Pull the "-advice" document back from the RFC Editor queue
> and fold the actual substantive content of the "-historic"
> document into it, preferably as a very clear and very prominent
> Applicability Statement.  

I am very strongly against this. The advisory document received extremely
strong support and excellent technical input from a wide cross section
of the IPv-anything operational community and has been fully approved
and is ready to go. I originally hoped it could be published for
World IPv6 Day, but having missed that date, it remains urgent to get
it out there, and to publicise it to operators who are not aware
of the issues.

We can spend another few months debating the exact form of words for
a normative document advising implementors to do what most of them
are now doing; I don't care and it basically doesn't matter except
in the IETF's tiny world. That isn't what's important. What's
important is to get as many operators as possible doing what they
can to ameliorate the situation.

   Brian

From john-ietf@jck.com  Fri Jul 15 14:01: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 E9A0221F8C0E; Fri, 15 Jul 2011 14:01:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.655
X-Spam-Level: 
X-Spam-Status: No, score=-102.655 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 XMkUzicQMmXq; Fri, 15 Jul 2011 14:01:33 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id D603921F8C0A; Fri, 15 Jul 2011 14:01:32 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QhpVr-000ISk-Gy; Fri, 15 Jul 2011 17:01:31 -0400
Date: Fri, 15 Jul 2011 17:01:30 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
Message-ID: <CF9FD8718237FDDA19BE31F8@PST.JCK.COM>
In-Reply-To: <4E20A44E.3060203@gmail.com>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <4E20A44E.3060203@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: 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, 15 Jul 2011 21:01:34 -0000

--On Saturday, July 16, 2011 08:34 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>...
> We can spend another few months debating the exact form of
> words for a normative document advising implementors to do
> what most of them are now doing; I don't care and it basically
> doesn't matter except in the IETF's tiny world. That isn't
> what's important. What's important is to get as many operators
> as possible doing what they can to ameliorate the situation.

Brian,

It seems to me that you can take two positions here, but not
both as the same time.

Position #1: What the IETF does, and how it classifies things,
actually make a difference.  If that is true then the advice
document should look a lot more mandatory and should certainly
be shown as updating the 6to4 base documents (I note that the
latter decision could be made without reopening the document in
any significant way).  Whether it is part of the advice document
or not, an applicability statement that discusses what is really
going on is important and reclassification to Historic would be
stupid.  If nothing else, unless it reclassifies your advice doc
to Historic as well, reclassification to Historic would be
appeal-bait.  And classifying your document as Historic also
would rather dilute the message.

Position #2: How the IETF classifies things makes very little
difference in this space because people will follow advice that
seems sensible and ignore everything else.  If so, it makes
little difference how your document is approved or where it is
published.  For example, it could have come through the
Independent Stream or been pushed into CCR.  No problem.  And
the "Historic" effort is a huge waste of the community's time,
no matter how it comes out.

Just my opinion -- you will probably continue to disagree.

best,
   john




From Ted.Lemon@nominum.com  Fri Jul 15 12:43:19 2011
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 986D521F8C3F; Fri, 15 Jul 2011 12:43:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.576
X-Spam-Level: 
X-Spam-Status: No, score=-106.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dvUX-AyxfPsD; Fri, 15 Jul 2011 12:43:18 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by ietfa.amsl.com (Postfix) with ESMTP id 7067321F8B48; Fri, 15 Jul 2011 12:43:18 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKTiCYVRycy09fVcn7dQVBnxAuAfeOuEeX@postini.com; Fri, 15 Jul 2011 12:43:18 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 4C3251B813B; Fri, 15 Jul 2011 12:43:17 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 22CCD190059; Fri, 15 Jul 2011 12:43:17 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from exchange-01.WIN.NOMINUM.COM (64.89.228.50) by CAS-01.WIN.NOMINUM.COM (64.89.228.131) with Microsoft SMTP Server (TLS) id 14.1.289.1; Fri, 15 Jul 2011 12:43:17 -0700
Received: from vpna-148.vpn.nominum.com (64.89.227.148) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 15 Jul 2011 12:43:16 -0700
Subject: Re: [v6ops] Another look at 6to4 (and other IPv6 transition issues)
MIME-Version: 1.0 (Apple Message framework v1242)
Content-Type: text/plain; charset="us-ascii"
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A65C6B37F80F@XCH-NW-01V.nw.nos.boeing.com>
Date: Fri, 15 Jul 2011 15:43:12 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <6BD654DE-880B-43BD-89A4-1BB065AC2B1B@nominum.com>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <BBB3AB81-1A20-4022-8687-CD88B000B281@bogus.com> <A6908373951C6911489DF57A@PST.JCK.COM> <71D5A97D-7119-4082-BC87-6505370CE800@bogus.com> <E1829B60731D1740BB7A0626B4FAF0A65C6B37F80F@XCH-NW-01V.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1242)
X-Mailman-Approved-At: Fri, 15 Jul 2011 14:04:00 -0700
Cc: "v6ops@ietf.org Operations" <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, 15 Jul 2011 19:43:19 -0000

On Jul 15, 2011, at 3:37 PM, Templin, Fred L wrote:
>> ipv4 is becoming less usable and it's=20
>> taking autotunnels with it, nobody here has a proposal that=20
>> changes that.
>=20
> As far as I can tell, IPv4 is not becoming less
> usable within my organization's network.

You realize that you have not contradicted what Joel said, right?     =
The IETF's business isn't making sure that Boeing's networks are =
functional, much as we might collectively wish you well in that regard.


From nkukich@verilan.com  Fri Jul 15 14:52:52 2011
Return-Path: <nkukich@verilan.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86FF821F8B4C for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 14:52:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.975
X-Spam-Level: 
X-Spam-Status: No, score=-102.975 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=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 SKzEXTjPBXm4 for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 14:52:48 -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 6A56D21F8B2A for <ietf@ietf.org>; Fri, 15 Jul 2011 14:52:48 -0700 (PDT)
Received: by pvh18 with SMTP id 18so2114845pvh.31 for <ietf@ietf.org>; Fri, 15 Jul 2011 14:52:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.41.168 with SMTP id g8mr5048345pbl.512.1310766767686; Fri, 15 Jul 2011 14:52:47 -0700 (PDT)
Received: by 10.68.40.193 with HTTP; Fri, 15 Jul 2011 14:52:47 -0700 (PDT)
Date: Fri, 15 Jul 2011 14:52:47 -0700
Message-ID: <CAHfXyNDr9+vWvn5OZC0wPNkJExOaWcjdsvpV21FYcsj4Qd=BHQ@mail.gmail.com>
Subject: IETF 81 Audio Streaming
From: Nick Kukich <nkukich@verilan.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=bcaec543084c9243d904a822ab0d
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jul 2011 21:52:52 -0000

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

Greetings!

We're two weeks out from the beginning of meeting streaming. For those
interested in monitoring sessions or participating remotely the following
information may prove useful.

- -Audio Streaming-

All 8 parallel tracks at the IETF 81 meeting will be broadcast starting with
the commencement of working group sessions on Monday, July 25, 2011 at 0900
EDT (GMT-4) and continue until Friday, July 29 at 1515 EDT.

Because we have been asked several times in the past, note that if you wish
to use the rooms that are being recorded for impromptu meeting during
unscheduled sessions or lunch breaks that you can invite remote participants
to tune in to the appropriate stream. Recording cannot be guaranteed for
unscheduled sessions. Conversely, it should never be assumed that recording
or observation is not occurring on open microphones, they are after all
connected to the Internet.

The links for streaming sources and the schedule are best retrieved from
the IETF tools agenda, which as per Standard operating procedure will be
located here:

http://tools.ietf.org/agenda/81/ <http://tools.ietf.org/agenda/80/>

- -Jabber/XMPP-

For information on IETF Jabber participation see:

http://www.ietf.org/jabber/index.html

or click on the Jabber links in the tools team agenda once you have a
properly configured jabber/xmpp messaging client.

- -Webex-

Webex screen sharing participation is possible for a limited number of
sessions. Consult with your working-group chair or the secretariat for more
information.

- -Ticketing-

For prompt access to the meeting trouble desk, the email address is:

mtd@ietf.org

For streaming related issues please send email to
ietf-streaming@verilan.com with
info including the current time and affected streaming channel.

Regards,

Nick Kukich

Network Engineer
Verilan Event Services, Inc.
503.710.5115

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

<span class=3D"Apple-style-span" style=3D"border-collapse: collapse; font-f=
amily: arial, sans-serif; font-size: 13px; ">Greetings!<br><br>We&#39;re tw=
o weeks out from the beginning of meeting=A0<span class=3D"il" style=3D"bac=
kground-image: initial; background-attachment: initial; background-origin: =
initial; background-clip: initial; background-color: rgb(255, 255, 136); co=
lor: rgb(34, 34, 34); background-position: initial initial; background-repe=
at: initial initial; ">streaming</span>. For those interested in monitoring=
 sessions or participating remotely the following information may prove use=
ful.<br>
<br>- -Audio=A0<span class=3D"il" style=3D"background-image: initial; backg=
round-attachment: initial; background-origin: initial; background-clip: ini=
tial; background-color: rgb(255, 255, 136); color: rgb(34, 34, 34); backgro=
und-position: initial initial; background-repeat: initial initial; ">Stream=
ing</span>-<br>
<br>All 8 parallel tracks at the=A0<span class=3D"il" style=3D"background-i=
mage: initial; background-attachment: initial; background-origin: initial; =
background-clip: initial; background-color: rgb(255, 255, 136); color: rgb(=
34, 34, 34); background-position: initial initial; background-repeat: initi=
al initial; ">IETF</span>=A081 meeting will be broadcast starting with the =
commencement of working group sessions on Monday, July 25, 2011 at 0900 EDT=
 (GMT-4) and continue until Friday, July 29 at 1515 EDT.<br>
<br>Because we have been asked several times in the past, note that if you =
wish to use the rooms that are being recorded for impromptu meeting during =
unscheduled sessions or lunch breaks that you can invite remote participant=
s to tune in to the appropriate stream. Recording cannot be guaranteed for =
unscheduled sessions. Conversely, it should never be assumed that recording=
 or observation is not occurring on open microphones, they are after all co=
nnected to the Internet.<br>
<br>The links for=A0<span class=3D"il" style=3D"background-image: initial; =
background-attachment: initial; background-origin: initial; background-clip=
: initial; background-color: rgb(255, 255, 136); color: rgb(34, 34, 34); ba=
ckground-position: initial initial; background-repeat: initial initial; ">s=
treaming</span>=A0sources and the schedule are best retrieved from the=A0<s=
pan class=3D"il" style=3D"background-image: initial; background-attachment:=
 initial; background-origin: initial; background-clip: initial; background-=
color: rgb(255, 255, 136); color: rgb(34, 34, 34); background-position: ini=
tial initial; background-repeat: initial initial; ">IETF</span>=A0tools age=
nda, which as per Standard operating procedure will be located here:<br>
<br><a href=3D"http://tools.ietf.org/agenda/80/" target=3D"_blank" style=3D=
"color: rgb(0, 0, 204); ">http://tools.<span class=3D"il" style=3D"backgrou=
nd-image: initial; background-attachment: initial; background-origin: initi=
al; background-clip: initial; background-color: rgb(255, 255, 136); color: =
rgb(34, 34, 34); background-position: initial initial; background-repeat: i=
nitial initial; ">ietf</span>.org/agenda/81/</a><br>
<br>- -Jabber/XMPP-<br><br>For information on=A0<span class=3D"il" style=3D=
"background-image: initial; background-attachment: initial; background-orig=
in: initial; background-clip: initial; background-color: rgb(255, 255, 136)=
; color: rgb(34, 34, 34); background-position: initial initial; background-=
repeat: initial initial; ">IETF</span>=A0Jabber participation see:<br>
<br><a href=3D"http://www.ietf.org/jabber/index.html" target=3D"_blank" sty=
le=3D"color: rgb(0, 0, 204); ">http://www.<span class=3D"il" style=3D"backg=
round-image: initial; background-attachment: initial; background-origin: in=
itial; background-clip: initial; background-color: rgb(255, 255, 136); colo=
r: rgb(34, 34, 34); background-position: initial initial; background-repeat=
: initial initial; ">ietf</span>.org/jabber/index.html</a><br>
<br>or click on the Jabber links in the tools team agenda once you have a p=
roperly configured jabber/xmpp messaging client.<br><br>- -Webex-<br><br>We=
bex screen sharing participation is possible for a limited number of sessio=
ns. Consult with your working-group chair or the secretariat for more infor=
mation.<br>
<br>- -Ticketing-<br><br>For prompt access to the meeting trouble desk, the=
 email address is:<br><br><a href=3D"mailto:mtd@ietf.org" style=3D"color: r=
gb(0, 0, 204); ">mtd@<span class=3D"il" style=3D"background-image: initial;=
 background-attachment: initial; background-origin: initial; background-cli=
p: initial; background-color: rgb(255, 255, 136); color: rgb(34, 34, 34); b=
ackground-position: initial initial; background-repeat: initial initial; ">=
ietf</span>.org</a><br>
<br>For=A0<span class=3D"il" style=3D"background-image: initial; background=
-attachment: initial; background-origin: initial; background-clip: initial;=
 background-color: rgb(255, 255, 136); color: rgb(34, 34, 34); background-p=
osition: initial initial; background-repeat: initial initial; ">streaming</=
span>=A0related issues please send email to=A0<a href=3D"mailto:ietf-stream=
ing@verilan.com" style=3D"color: rgb(0, 0, 204); "><span class=3D"il" style=
=3D"background-image: initial; background-attachment: initial; background-o=
rigin: initial; background-clip: initial; background-color: rgb(255, 255, 1=
36); color: rgb(34, 34, 34); background-position: initial initial; backgrou=
nd-repeat: initial initial; ">ietf</span>-<span class=3D"il" style=3D"backg=
round-image: initial; background-attachment: initial; background-origin: in=
itial; background-clip: initial; background-color: rgb(255, 255, 136); colo=
r: rgb(34, 34, 34); background-position: initial initial; background-repeat=
: initial initial; ">streaming</span>@verilan.com</a>=A0with info including=
 the current time and affected=A0<span class=3D"il" style=3D"background-ima=
ge: initial; background-attachment: initial; background-origin: initial; ba=
ckground-clip: initial; background-color: rgb(255, 255, 136); color: rgb(34=
, 34, 34); background-position: initial initial; background-repeat: initial=
 initial; ">streaming</span>=A0channel.<br>
<br>Regards,</span><br><div><br></div>Nick Kukich<div><br><div>Network Engi=
neer<br>Verilan Event Services, Inc.</div><div><div>503.710.5115</div></div=
></div><br>

--bcaec543084c9243d904a822ab0d--

From dougb@dougbarton.us  Fri Jul 15 15:40:09 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 881E021F8B25 for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 15:40:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.263
X-Spam-Level: 
X-Spam-Status: No, score=-3.263 tagged_above=-999 required=5 tests=[AWL=-0.264, 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 IVFKs2xe9TIL for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 15:40:05 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 2DE4B21F8B23 for <ietf@ietf.org>; Fri, 15 Jul 2011 15:40:04 -0700 (PDT)
Received: (qmail 31109 invoked by uid 399); 15 Jul 2011 22:40:00 -0000
Received: from unknown (HELO 65-241-43-4.globalsuite.net) (dougb@dougbarton.us@65.241.43.4) by mail2.fluidhosting.com with ESMTPAM; 15 Jul 2011 22:40:00 -0000
X-Originating-IP: 65.241.43.4
X-Sender: dougb@dougbarton.us
Message-ID: <4E20C1BF.3040302@dougbarton.us>
Date: Fri, 15 Jul 2011 15:39:59 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110706 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM>
In-Reply-To: <DB5571A0CF3C3F570576A23F@PST.JCK.COM>
X-Enigmail-Version: 1.2pre
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jul 2011 22:40:09 -0000

John,

I think Brian and Joel both made excellent points about why this
suggestion is probably sub-optimal, and I won't presume to add to the
elegance of their arguments on those points other than to say that I
agree with them.

To address your concern about whether or not vendors are paying
attention to this discussion, and why historic status is substantively
different than "off by default, no really, OFF BY DEFAULT," I'll put my
FreeBSD developer hat on for a minute and tell you that we definitely do
pay attention to stuff like this, and whereas we already have it off by
default (and have for some time) moving it to historic gives us the
cover we need to remove the code at some point down the road when that's
appropriate. That's an extremely important distinction, and one of the
reasons that as a "member" of v6ops I ultimately came down in support of
the 2-document strategy.


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 Fred.L.Templin@boeing.com  Fri Jul 15 16:10:22 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 8A28B21F8BDC; Fri, 15 Jul 2011 16:10:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.419
X-Spam-Level: 
X-Spam-Status: No, score=-6.419 tagged_above=-999 required=5 tests=[AWL=0.180,  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 Tytketj4C7Ob; Fri, 15 Jul 2011 16:10:22 -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 0ACB721F8B86; Fri, 15 Jul 2011 16:10:21 -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 p6FNAC5Y029109 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 15 Jul 2011 16:10:15 -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 p6FNA7b9028117; Fri, 15 Jul 2011 16:10:07 -0700 (PDT)
Received: from XCH-NWHT-08.nw.nos.boeing.com (xch-nwht-08.nw.nos.boeing.com [130.247.25.112]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p6FNA409028026 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 15 Jul 2011 16:10:06 -0700 (PDT)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-08.nw.nos.boeing.com ([130.247.25.112]) with mapi; Fri, 15 Jul 2011 16:10:05 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Date: Fri, 15 Jul 2011 16:10:04 -0700
Subject: RE: [v6ops] Another look at 6to4 (and other IPv6 transition issues)
Thread-Topic: [v6ops] Another look at 6to4 (and other IPv6 transition issues)
Thread-Index: AcxDJ3QqjlOP9YhATMa7q2+nrXLFPQAGvlQw
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65C6B37F8F8@XCH-NW-01V.nw.nos.boeing.com>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <BBB3AB81-1A20-4022-8687-CD88B000B281@bogus.com> <A6908373951C6911489DF57A@PST.JCK.COM> <71D5A97D-7119-4082-BC87-6505370CE800@bogus.com> <E1829B60731D1740BB7A0626B4FAF0A65C6B37F80F@XCH-NW-01V.nw.nos.boeing.com> <6BD654DE-880B-43BD-89A4-1BB065AC2B1B@nominum.com>
In-Reply-To: <6BD654DE-880B-43BD-89A4-1BB065AC2B1B@nominum.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: "v6ops@ietf.org Operations" <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, 15 Jul 2011 23:10:22 -0000

=20

> -----Original Message-----
> From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
> Sent: Friday, July 15, 2011 12:43 PM
> To: Templin, Fred L
> Cc: v6ops@ietf.org Operations; IETF Discussion
> Subject: Re: [v6ops] Another look at 6to4 (and other IPv6=20
> transition issues)
>=20
> On Jul 15, 2011, at 3:37 PM, Templin, Fred L wrote:
> >> ipv4 is becoming less usable and it's=20
> >> taking autotunnels with it, nobody here has a proposal that=20
> >> changes that.
> >=20
> > As far as I can tell, IPv4 is not becoming less
> > usable within my organization's network.
>=20
> You realize that you have not contradicted what Joel said,=20
> right?     The IETF's business isn't making sure that=20
> Boeing's networks are functional, much as we might=20
> collectively wish you well in that regard.

If the IETF wishes organizations such as ours well, then
they should be willing to provide operational guidance.
RFCs 4057 and 4852 were a small step in that direction,
while 'draft-templin-v6ops-isops' provides actionable
information.

Fred=

From joelja@bogus.com  Fri Jul 15 16:11: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 1CBCA21F8B8E; Fri, 15 Jul 2011 16:11:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.203
X-Spam-Level: 
X-Spam-Status: No, score=-101.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AfZX4Zv4jmrI; Fri, 15 Jul 2011 16:11:14 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 5997721F8B30; Fri, 15 Jul 2011 16:11:14 -0700 (PDT)
Received: from [192.168.50.12] (24-221-29-56.pools.static.spcsdns.net [24.221.29.56]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p6FNAeSc007915 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 15 Jul 2011 23:10:51 GMT (envelope-from joelja@bogus.com)
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <BBB3AB81-1A20-4022-8687-CD88B000B281@bogus.com> <A6908373951C6911489DF57A@PST.JCK.COM> <71D5A97D-7119-4082-BC87-6505370CE800@bogus.com> <E1829B60731D1740BB7A0626B4FAF0A65C6B37F80F@XCH-NW-01V.nw.nos.boeing.com>
From: Joel Jaeggli <joelja@bogus.com>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A65C6B37F80F@XCH-NW-01V.nw.nos.boeing.com>
Message-Id: <2D86AA95-BC5F-4313-844B-A89485DA7220@bogus.com>
Date: Fri, 15 Jul 2011 13:28:46 -0700
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Mime-Version: 1.0 (iPad Mail 8J2)
X-Mailer: iPad Mail (8J2)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 15 Jul 2011 23:11:11 +0000 (UTC)
Cc: John C Klensin <john-ietf@jck.com>, "v6ops@ietf.org" <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, 15 Jul 2011 23:11:15 -0000

Joel's widget number 2

On Jul 15, 2011, at 12:37, "Templin, Fred L" <Fred.L.Templin@boeing.com> wro=
te:

> Hi Joel,=20
>=20
>> ipv4 is becoming less usable and it's=20
>> taking autotunnels with it, nobody here has a proposal that=20
>> changes that.
>=20
> As far as I can tell, IPv4 is not becoming less
> usable within my organization's network.

Stasis is great if you can get it... There are two drafts proposing the use o=
f shared address space space to be assigned by ARIN for LSN  that will proba=
bly turn up in opsawg.

Whether the get it or not the LSNs will be deployed.

And yeah I think Boeing probably has enough v4 addresses for a while.

Joel

>=20
> Thanks - Fred
> fred.l.templin@boeing.com
>=20

From johnl@iecc.com  Fri Jul 15 16:33:22 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 CCB8A21F8A4E for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 16:33:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.305
X-Spam-Level: 
X-Spam-Status: No, score=-110.305 tagged_above=-999 required=5 tests=[AWL=0.894, 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 KW+2zGTZwGjh for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 16:33:22 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 0BA3B21F8A67 for <ietf@ietf.org>; Fri, 15 Jul 2011 16:33:21 -0700 (PDT)
Received: (qmail 69639 invoked from network); 15 Jul 2011 23:33:19 -0000
Received: from gal.iecc.com (64.57.183.53) by mail2.iecc.com with SMTP; 15 Jul 2011 23:33:19 -0000
Received: (qmail 68136 invoked from network); 15 Jul 2011 23:33:18 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 15 Jul 2011 23:33:18 -0000
Date: 15 Jul 2011 23:32:56 -0000
Message-ID: <20110715233256.23779.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Confidentiality notices on email messages
In-Reply-To: <4E2054EE.7080108@tana.it>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: vesely@tana.it
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jul 2011 23:33:22 -0000

>See http://www.out-law.com/page-5536

It says "There is no legal authority on the effectiveness of these
notices in email messages;" and "There is no legal authority on the
value of these notices in email communications. When the notice is
added automatically to every external communication, there is a risk
that a court would consider that the venom in your warning has been
diluted," then goes on with a couple of pages of advice about how to
write a useless confidentiality threat, advising people to put it at
the top of the message to force them to read it.  Guess I know who I
won't be consulting if I ever need legal advice in the UK.

R's,
John



From msk@cloudmark.com  Fri Jul 15 17:09: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 2E69721F89A7 for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 17:09:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.927
X-Spam-Level: 
X-Spam-Status: No, score=-103.927 tagged_above=-999 required=5 tests=[AWL=-0.328, 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 E98H38ewliK5 for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 17:09: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 CC5A421F8987 for <ietf@ietf.org>; Fri, 15 Jul 2011 17:09: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; Fri, 15 Jul 2011 17:09:09 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: IETF discussion list <ietf@ietf.org>
Date: Fri, 15 Jul 2011 17:09:08 -0700
Subject: RE: Confidentiality notices on email messages
Thread-Topic: Confidentiality notices on email messages
Thread-Index: AcxCVWUsDEn5zdfpRH+NTdnvyS9atQA9w8RA
Message-ID: <F5833273385BB34F99288B3648C4F06F134EBC4D4B@EXCH-C2.corp.cloudmark.com>
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <29987.1310565058@marajade.sandelman.ca>	<4E1DCA13.9030301@acm.org> <04AE56F0C4CE8168D1B38D59@PST.JCK.COM> <p0624066dca44df0ca50f@loud.pensive.org> <49A68144182BB270C11BC841@PST.JCK.COM>
In-Reply-To: <49A68144182BB270C11BC841@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: Sat, 16 Jul 2011 00:09:10 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of J=
ohn C Klensin
> Sent: Thursday, July 14, 2011 11:39 AM
> To: Randall Gellens; Marc Petit-Huguenin
> Cc: IETF discussion list
> Subject: Re: Confidentiality notices on email messages
>=20
> If one starts down that path, there is a real possibility for a
> semantically-rich environment.  For example, consider a noise
> type for flaming, repetitive, responses to a topic on the IETF
> list.  One could also very efficiently reflect what I assume was
> the intent of a recent observation on the list with
> noise-type=3D"hitler" :-(

The trick though, alas, is to get people using such disclaimers to begin us=
ing such a media type.

Maybe we need an attractive acronym for NOISE as a decoy.

From evnikita2@gmail.com  Fri Jul 15 21:11:34 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 662ED21F86E5 for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 21:11:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.503
X-Spam-Level: 
X-Spam-Status: No, score=-3.503 tagged_above=-999 required=5 tests=[AWL=0.096,  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 bi8mWjOlhFBm for <ietf@ietfa.amsl.com>; Fri, 15 Jul 2011 21:11:33 -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 61A2021F86DF for <ietf@ietf.org>; Fri, 15 Jul 2011 21:11:33 -0700 (PDT)
Received: by fxe4 with SMTP id 4so4415326fxe.27 for <ietf@ietf.org>; Fri, 15 Jul 2011 21:11:32 -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=RjXq7NAdtuVXGDTn3+BhBg+s472QFo5q5bJ1MG89V0U=; b=B+4Z7XOpWVT8w6NClEZKfHlZjD9T7LZAwuvxm/zu0Pc4TkmTXY4jkBy0tA50th8qUg McmMvJiuDk6xMJ7lgrG9xGJB0gnFfO5Marzy4kyX3f64Ec2qCoLkXp2HQYvP9x1Vpm8z i9nAWmz38zxEqbFhXb/qxZDyTv03rEt6XggeE=
Received: by 10.223.160.131 with SMTP id n3mr6299503fax.111.1310789490982; Fri, 15 Jul 2011 21:11:30 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id 22sm1196240fas.11.2011.07.15.21.11.26 (version=SSLv3 cipher=OTHER); Fri, 15 Jul 2011 21:11:27 -0700 (PDT)
Message-ID: <4E210F9B.8080305@gmail.com>
Date: Sat, 16 Jul 2011 07:12:11 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Harald Alvestrand <harald@alvestrand.no>
Subject: Re: Review of draft-yevstifeyev-ion-report-06
References: <4D91EBDE.5070703@gmail.com> <4E205A5D.1020304@alvestrand.no>
In-Reply-To: <4E205A5D.1020304@alvestrand.no>
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: Sat, 16 Jul 2011 04:11:34 -0000

Hello Harald,

As you could see in one of my previous messages, I did intend to include 
some analysis in the draft 
(http://www.ietf.org/mail-archive/web/ietf/current/msg67491.html).  
However, numerous responses which discouraged me from doing this were 
received, and including that section will create problems with 
consensus.  However, I share your opinion that the document won't be 
full, so I think the following analysis section, which is different from 
the previous proposed one, can satisfy you and everybody else:

> 3.4. Analysis
>
>    There were a number of reasons which forced IESG to close the IONs
>    experiment.  One of them is a complexity of their approval and
>    publication, compared with ones for IESG Statements and simple Web
>    Pages.  As IONs were intended to represent operational experience,
>    they might have needed to be updated quickly.  Even though these
>    documents were meant to have a very lightweight approval procedure,
>    it could sometimes be inappropriate for that material which was
>    contained therein.
>
>    Secondly, due to the nature of the scope of IONs, there was no need
>    to allow the access to the revision history (which is unavailable in
>    simple Web Pages as well).
>
>    Thirdly, IONs on procedural question could step into the conflict
>    with Best Current Practice (BCP) RFCs; moreover, as IONs approval
>    procedure did not imply any formal community review, unlike BCPs,
>    they could easily fall in the community non-acceptance.
>
>    Correspondingly, it was concluded that the mandate of IONs can fully
>    be fulfilled by RFCs, when documenting IETF procedures, IESG
>    Statements, when clearing up other issues for which RFC publication
>    process is not appropriate, and Web Pages, when dealing with other
>    IETF-related issues. 

Please see other response in-line.

15.07.2011 18:18, Harald Alvestrand wrote:
> My apologies for the lateness of this review.
>
> I am not happy with this document.
>
> I was unhappy with the IESG's decision to close the ION experiment, 
> since I believe the mechanisms that were chosen to replace it failed 
> to fulfil several of the requirements that were driving forces in the 
> design of the ION mechanism (as an example, try to find out who, if 
> anyone, approved http://iaoc.ietf.org/network_requirements.html, what 
> the previous version was, and when this version was approved).
>
> The document does not refer back to the aims of the experiment, which 
> I tried to make explicit in section 5 of RFC 4693, which include:
>
> - Easy updating
> - Explicit approval
> - Accessible history
It's very easy to add.  I think the 2nd paragraph of the Section 2 may 
be changed to:

>    IONs were meant to be easily updated but to have some explicit IESG
>    approval mechanism; IESG might also have granted the approval right
>    to other parties.  The strict format rules for RFCs were not applied
>    to IONs.  Moreover, the history of revisions was intended to be
>    easily accessed.  For more background information on IONs, please see
>    Section 5 of RFC 4693 [RFC4693] .

>
> The sum total of analysis in this document is two sentences:
See above.
> The cited IESG statement
>
> [ . . . ]
>                         Harald
>
>
>
>
>
>
>


From nsb@guppylake.com  Sat Jul 16 00:16:12 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 5AFF821F8506 for <ietf@ietfa.amsl.com>; Sat, 16 Jul 2011 00:16:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0EBTIaaD6+T8 for <ietf@ietfa.amsl.com>; Sat, 16 Jul 2011 00:16:11 -0700 (PDT)
Received: from server1.netnutz.com (server1.netnutz.com [72.233.90.3]) by ietfa.amsl.com (Postfix) with ESMTP id 9BF3A21F84C8 for <ietf@ietf.org>; Sat, 16 Jul 2011 00:16:11 -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=JalI5Dj8fcCqWHioqvzrEM3V/zQCBsjtS2OVY9UMtNjdBuzzmukhzJMnoOaLXkdFRDpV+jDeBJoUO7jQk7/9XO86Ozch2hhaW71m+gFFsV8eNaIigPne86Y/nYACyhYJ;
Received: from host-39-196-68-109.spectrum1.uk.sharedband.net ([109.68.196.39] helo=[10.1.0.211]) by server1.netnutz.com with esmtpa (Exim 4.69) (envelope-from <nsb@guppylake.com>) id 1Qhz6Q-00038x-8z; Sat, 16 Jul 2011 03:16:01 -0400
Subject: Re: Confidentiality notices on email messages
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Nathaniel Borenstein <nsb@guppylake.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F134EBC4D4B@EXCH-C2.corp.cloudmark.com>
Date: Sat, 16 Jul 2011 08:15:48 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <FDD50EB2-B783-49B3-92C2-56A21EFAEF11@guppylake.com>
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <29987.1310565058@marajade.sandelman.ca>	<4E1DCA13.9030301@acm.org> <04AE56F0C4CE8168D1B38D59@PST.JCK.COM> <p0624066dca44df0ca50f@loud.pensive.org> <49A68144182BB270C11BC841@PST.JCK.COM> <F5833273385BB34F99288B3648C4F06F134EBC4D4B@EXCH-C2.corp.cloudmark.com>
To: Murray S. Kucherawy <msk@cloudmark.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 list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2011 07:16:12 -0000

"Notice Of Intentions in Sending Email"?

On Jul 16, 2011, at 1:09 AM, Murray S. Kucherawy wrote:

>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of John C Klensin
>> Sent: Thursday, July 14, 2011 11:39 AM
>> To: Randall Gellens; Marc Petit-Huguenin
>> Cc: IETF discussion list
>> Subject: Re: Confidentiality notices on email messages
>>=20
>> If one starts down that path, there is a real possibility for a
>> semantically-rich environment.  For example, consider a noise
>> type for flaming, repetitive, responses to a topic on the IETF
>> list.  One could also very efficiently reflect what I assume was
>> the intent of a recent observation on the list with
>> noise-type=3D"hitler" :-(
>=20
> The trick though, alas, is to get people using such disclaimers to =
begin using such a media type.
>=20
> Maybe we need an attractive acronym for NOISE as a decoy.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From john-ietf@jck.com  Sat Jul 16 07:21: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 65F2B21F850E for <ietf@ietfa.amsl.com>; Sat, 16 Jul 2011 07:21:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.652
X-Spam-Level: 
X-Spam-Status: No, score=-102.652 tagged_above=-999 required=5 tests=[AWL=-0.053, 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 x8C7xLQSNbaa for <ietf@ietfa.amsl.com>; Sat, 16 Jul 2011 07:21:14 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 58EE121F8509 for <ietf@ietf.org>; Sat, 16 Jul 2011 07:21:10 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Qi5jv-0006zr-03; Sat, 16 Jul 2011 10:21:07 -0400
Date: Sat, 16 Jul 2011 10:21:06 -0400
From: John C Klensin <john-ietf@jck.com>
To: Harald Alvestrand <harald@alvestrand.no>, Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Review of draft-yevstifeyev-ion-report-06
Message-ID: <EF99FBFBD74FE7A969412306@PST.JCK.COM>
In-Reply-To: <4E205A5D.1020304@alvestrand.no>
References: <4D91EBDE.5070703@gmail.com> <4E205A5D.1020304@alvestrand.no>
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: Sat, 16 Jul 2011 14:21:15 -0000

FWIW, +1


--On Friday, July 15, 2011 17:18 +0200 Harald Alvestrand
<harald@alvestrand.no> wrote:

> My apologies for the lateness of this review.
> 
> I am not happy with this document.
> 
> I was unhappy with the IESG's decision to close the ION
> experiment, since I believe the mechanisms that were chosen to
> replace it failed to fulfil several of the requirements that
> were driving forces in the design of the ION mechanism (as an
> example, try to find out who, if anyone, approved
> http://iaoc.ietf.org/network_requirements.html, what the
> previous version was, and when this version was approved).
> 
> The document does not refer back to the aims of the
> experiment, which I tried to make explicit in section 5 of RFC
> 4693, which include:
> 
> - Easy updating
> - Explicit approval
> - Accessible history
> 
> The sum total of analysis in this document is two sentences:
> The cited IESG statement
> 
>       It is clear that the IESG, IAB, and IAOC need the
> ability to
>       publish documents that do not expire and are easily
> updated.
>       Information published as web pages, including IESG
> Statements, are
>       sufficient for this purpose.
> 
> The draft's statement
> 
>     Taking everything into account, it was considered that
> IONs added
>     complications to the maintenance of documents but did not
> give a
>     corresponding benefit to the IETF.
> 
> I would at least expect those three points to be explicitly
> addressed by analysis, such as:
> 
> - The IESG concluded that publication of IONs was more complex
> than publishing Web pages and IESG statements
> - The IESG concluded that the IESG statement mechanism, which
> has no formal definition, was enough documentation of the
> IESG's decisions where decision documentation was reasonable,
> and that Web pages needed no explicit approval
> - The IESG concluded that there was no need to provide an
> accessible history of versions of the documents for which the
> ION mechanism was intended
> 
> The document also needs a language check, but I feel that the
> lack of *any* explicit analysis with respect to the aims of
> the experiment, even an explicit statement that the issues
> involved were considered not important, is the most important
> shortcoming of the document.
> 
>                          Harald
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf





From john-ietf@jck.com  Sat Jul 16 07:39:36 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 82EE921F8561 for <ietf@ietfa.amsl.com>; Sat, 16 Jul 2011 07:39:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.649
X-Spam-Level: 
X-Spam-Status: No, score=-102.649 tagged_above=-999 required=5 tests=[AWL=-0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4PWVw+JwyZPi for <ietf@ietfa.amsl.com>; Sat, 16 Jul 2011 07:39:36 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id D832921F8560 for <ietf@ietf.org>; Sat, 16 Jul 2011 07:39:35 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Qi61c-0007Mk-KE; Sat, 16 Jul 2011 10:39:24 -0400
Date: Sat, 16 Jul 2011 10:39:23 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>, Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Last Call: <draft-yevstifeyev-ion-report-06.txt> (Report on the	Experiment with IETF Operational Notes (IONs)) to Informational RFC
Message-ID: <C56B000FEF3F4C6475ABCE55@PST.JCK.COM>
In-Reply-To: <CAC4RtVBvfgmJ3JOB6ZTYrWrQYarwbN7uYTi7XmdVS29BjG7PUw@mail.gmail.com>
References: <20110712143944.20141.23357.idtracker@ietfa.amsl.com> <4E1C7B48.4070000@gmail.com> <4E1CC89E.7010907@gmail.com>	<4E1D0708.9090701@gmail.com> <CAC4RtVBvfgmJ3JOB6ZTYrWrQYarwbN7uYTi7XmdVS29BjG7PUw@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jul 2011 14:39:36 -0000

--On Wednesday, July 13, 2011 10:48 -0400 Barry Leiba
<barryleiba@computer.org> wrote:

>> Let me explain why I'm planning to include this sub-section.
> 
> Why?  Your explanation lacks substance, and further effort
> here is a waste of time.
> 
> The document as it stands is just fine, except for one
> sentence that needs rewording to make sense in English:
>...

Barry,

I note that we rarely publish analyses of experiments (either
process or technical ones).  I think we should do that a lot
more often but, if there is energy to do so, this wouldn't be my
first priority... or even my 20th.

If IESG statements are adequate as replacements for IONs, then
an IESG statement should be sufficient to terminate that
particular experiment.   And we already have such a statement.
While I could see publishing an RFC that, as Harald suggests,
reflects on the original analysis and explains why either the
problem was inappropriately described or unimportant or why the
solutions weren't worth the trouble, a document that says,
approximately, "we decided to not do that" adds no value to the
IESG Statement and no value to the RFC Series.

Presumably, when the IESG decided to terminate the ION
experiment by an IESG Statement, they made an explicit decision
that an RFC was not needed and that a detailed explanation and
analysis was not worth the trouble.   What do you think has
changed?

So, if only to increase my understanding, why do you think
reviewing this type of document (presumably through multiple
cycles as we quibble about language, etc.) is worth a Last Call
and the community's time?



    john





From john-ietf@jck.com  Sat Jul 16 07:57:59 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 3742721F861A for <ietf@ietfa.amsl.com>; Sat, 16 Jul 2011 07:57:59 -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.047, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CNVryQOXnCge for <ietf@ietfa.amsl.com>; Sat, 16 Jul 2011 07:57:58 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 5171621F863A for <ietf@ietf.org>; Sat, 16 Jul 2011 07:57:58 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Qi6JZ-0007ZS-Dl; Sat, 16 Jul 2011 10:57:57 -0400
Date: Sat, 16 Jul 2011 10:57:56 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Community time as a limited asset (was: Re: Last Call: <draft-yevstifeyev-ion-report-06.txt> (Report on the	Experiment with IETF Operational Notes (IONs)) to Informational RFC)
Message-ID: <C735B1AB6E565283F1806650@PST.JCK.COM>
In-Reply-To: <4E1CC89E.7010907@gmail.com>
References: <20110712143944.20141.23357.idtracker@ietfa.amsl.com> <4E1C7B48.4070000@gmail.com> <4E1CC89E.7010907@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: Sat, 16 Jul 2011 14:57:59 -0000

--On Wednesday, July 13, 2011 10:20 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> Mykyta,
> 
> I think the draft is fine without this addition, which
> contains some statements that I disagree with. I don't think
> analysis is needed; this is all ancient history anyway.

Brian and others,

I think your note, when combined with this document, identifies
a much broader issue that I think we need to start considering
more carefully.

The number of people in the community who actually do work and
who, in particular, feel obligated to review every Last Call
about which they might have knowledge, to make constructive
comments, etc., is not very large.  By definition, they have
finite time.  Relatively few of us have the luxury historically
accorded academics (students and faculty alike) of being able to
set priorities independent of intrusive external complaints
(many academics don't have that luxury any more either).

If we want the specifications and documents that really do need
careful attention, review from different perspectives, etc., to
get that time, then, IMO, we have to start becoming more
disciplined about identifying what is really important...
especially in times when available resources seem to be
shrinking rather than increasing.  Our questions need to include
not only "is this correct" and "does it address an issue that is
either known or that it identifies" but "is it actually
important".

I would hope that much of that discipline could be applied by
authors exercising judgment and maturity.  However, if it is
not, I would hope that IESG members considering whether or not
to sponsor individual contributions would assume that an hour
that goes into reviewing one document (even one that is
unimportant in the grand scheme of things) is an hour that isn't
going to go into reviewing another one, especially one that
might, through the week of the draw, be announced right after
someone has used up all of her available IETF time for a while.  

So, my conclusion about this particular document is ultimately
identical to yours: this is all ancient history anyway (and, by
the way, the IESG has already issued a statement on the
subject).  But that conclusion leads me to disagree with you:
"ancient history" doesn't imply that we should publish the
document, it implies that we should stop wasting time and drop
it.

When I express agreement with Harald's call for more analysis
that might lead us to avoid similar attempts in the future (if,
indeed, IONs were a mistake), it is not because I think that
work would be worth publishing.  I would be much more likely to
still come down on the side of "ancient history; let's not waste
time having a Last Call, discussing it, and publishing".   But
at least in Harald's model we'd be publishing some serious
analysis and new information that would add to the record.  I
don't see this document, freed of all or most analysis, adding a
thing to the existing IESG Statement.  And that makes it a
bigger use of community time, RFC Editing resources, etc.

In case it isn't clear, while this particular document inspired
this comment, the comment applies with equal force to, e.g.,
reclassifying RFCs that are even more ancient history and about
which no one is paying attention any more.  We can do it, the
reclassifications are usually correct technically and
procedurally, but processing them is justified only if we assume
that the community has infinite time and resources and/or that
time spent on something like those efforts isn't time taken away
from other things.

    john



From barryleiba@gmail.com  Sat Jul 16 11:41:57 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 E1E9221F86C1 for <ietf@ietfa.amsl.com>; Sat, 16 Jul 2011 11:41:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.108
X-Spam-Level: 
X-Spam-Status: No, score=-103.108 tagged_above=-999 required=5 tests=[AWL=-0.131, 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 D4zuJXoDbv0q for <ietf@ietfa.amsl.com>; Sat, 16 Jul 2011 11:41:57 -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 6390E21F86B9 for <ietf@ietf.org>; Sat, 16 Jul 2011 11:41:57 -0700 (PDT)
Received: by yie30 with SMTP id 30so1028092yie.31 for <ietf@ietf.org>; Sat, 16 Jul 2011 11:41:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=pnm3ZrHkqbWh8eiWfUv22ZzRXHYYVz6GxT5XB+ze4d0=; b=Y7i6ZvWuRXCQtI6YfHVovtTc1TPYe2m7SyR3ZCLmyEVTbzRdCCxxS/0Z36sn+yrX9l fX6QXp0nHxLz9AYSvvYHe3E1STRL+NwOPGKO7bVijGWFGR2dgOqba5xmBVUGsMWJ3P/9 LGSqNipx4vVJDT3RRwyqdvpnSVjgzFw/HvWIg=
MIME-Version: 1.0
Received: by 10.236.200.234 with SMTP id z70mr6292843yhn.325.1310841716728; Sat, 16 Jul 2011 11:41:56 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.236.199.41 with HTTP; Sat, 16 Jul 2011 11:41:56 -0700 (PDT)
In-Reply-To: <C56B000FEF3F4C6475ABCE55@PST.JCK.COM>
References: <20110712143944.20141.23357.idtracker@ietfa.amsl.com> <4E1C7B48.4070000@gmail.com> <4E1CC89E.7010907@gmail.com> <4E1D0708.9090701@gmail.com> <CAC4RtVBvfgmJ3JOB6ZTYrWrQYarwbN7uYTi7XmdVS29BjG7PUw@mail.gmail.com> <C56B000FEF3F4C6475ABCE55@PST.JCK.COM>
Date: Sat, 16 Jul 2011 14:41:56 -0400
X-Google-Sender-Auth: szrhn1qUsBwBvJOndxh11yDt5js
Message-ID: <CALaySJ+jn0GNmoHOZ2CRFpYGkOVxeUu1xjLx9vppC-uAnf2+DA@mail.gmail.com>
Subject: Re: Last Call: <draft-yevstifeyev-ion-report-06.txt> (Report on the Experiment with IETF Operational Notes (IONs)) to Informational RFC
From: Barry Leiba <barryleiba@computer.org>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jul 2011 18:41:58 -0000

> Barry,
...
> So, if only to increase my understanding, why do you think
> reviewing this type of document (presumably through multiple
> cycles as we quibble about language, etc.) is worth a Last Call
> and the community's time?

John, you've mis-addressed this.  It's Mykyta who wants to do it ,not
I.  I think it's at least as much a waste of time as you do.  The only
reason I reviewed it and commented on the language at all was that
Mykyta said Russ had agreed to shepherd it.  Either it needs to be
published as it is, without further waste of time, or it needs to go
away.

Barry

From rbonica@juniper.net  Sat Jul 16 13:12:02 2011
Return-Path: <rbonica@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21E8A21F881B; Sat, 16 Jul 2011 13:12:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.534
X-Spam-Level: 
X-Spam-Status: No, score=-106.534 tagged_above=-999 required=5 tests=[AWL=0.065, 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 gaa3qAWzYMih; Sat, 16 Jul 2011 13:12:01 -0700 (PDT)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by ietfa.amsl.com (Postfix) with ESMTP id 6CE8D21F859E; Sat, 16 Jul 2011 13:11:42 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKTiHwfpv1w6VyV6I8zrWYsDtPu0mDVHCI@postini.com; Sat, 16 Jul 2011 13:12:01 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; Sat, 16 Jul 2011 13:03:57 -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; Sat, 16 Jul 2011 16:03:57 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Joel Jaeggli <joelja@bogus.com>, John C Klensin <john-ietf@jck.com>
Date: Sat, 16 Jul 2011 16:03:55 -0400
Subject: RE: Another look at 6to4 (and other IPv6 transition issues)
Thread-Topic: Another look at 6to4 (and other IPv6 transition issues)
Thread-Index: AcxDI90BTawX0D64SXGpYpjtR2s/SgAzLLkQ
Message-ID: <13205C286662DE4387D9AF3AC30EF456D3F3DEEA84@EMBX01-WF.jnpr.net>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <BBB3AB81-1A20-4022-8687-CD88B000B281@bogus.com> <A6908373951C6911489DF57A@PST.JCK.COM> <71D5A97D-7119-4082-BC87-6505370CE800@bogus.com>
In-Reply-To: <71D5A97D-7119-4082-BC87-6505370CE800@bogus.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: "v6ops@ietf.org" <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: Sat, 16 Jul 2011 20:12:02 -0000

Hi John,

I think that most of the rancor around RFCs 3056 and 3068 is due to RFC 202=
6's very terse definition of HISTORIC. According to RFC 2026, "A specificat=
ion that has been superseded by a more recent specification or is for any o=
ther reason considered to be obsolete is assigned to the Historic level." T=
hat's the entire definition. Anything more is read into it.

Granted, the phrase "for any other reason considered to be obsolete" is pre=
tty subjective. In this thread, I have seen people interpret that phrase as=
 follows:

"the IETF thinks that there are no longer any valid use cases for this tech=
nology"
"the IETF recommends that you remove this technology from your network"
"the IETF believes that nobody is using this technology"

I doubt if any of these interpretations are valid, because the IETF is not =
in a good position to evaluate what is in use or tell an operator how to ru=
n a network. A more likely interpretation is as follows:

"the IETF is not likely to invest effort in the technology in the future"
"the IETF does not encourage (or discourage) new deployments of this techno=
logy.

                                                   Ron


> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Joel Jaeggli
> Sent: Friday, July 15, 2011 3:17 PM
> To: John C Klensin
> Cc: v6ops@ietf.org; IETF Discussion
> Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
>=20
>=20
> On Jul 15, 2011, at 11:52 AM, John C Klensin wrote:
>=20
> >
> >
> > --On Friday, July 15, 2011 09:40 -0700 Joel Jaeggli
> > <joelja@bogus.com> wrote:
> >
> >> So the rational for the advice document not being combined
> >> with the standards action in it is that the later has some
> >> polarizing impact, the advice document does not. the advice
> >> document is through and done, historic is not.
> >
> > Joel (and others),
> >
> > I understand the rationale.  At the risk of repeating myself, I
> > simply do not think it works or is appropriate.
>=20
> And there are people that disagree with you on that.
>=20
> >  Recategorizing
> > set of documents as "Historic" is an extremely blunt instrument.
> > If we do it in a consistent and logical fashion, the advice
> > document would have to go to Historic along with the base
> > documents because giving advice about a piece of ancient history
> > is meaningless.  That is not what most people who like the
> > advice document intended, at least as I understood the consensus
> > on that Last Call.
>=20
> <SNIP>
>=20
> > Finally, if we had a wonderful transition model that would work
> > well in all situations, then it would make sense to recommend it
> > and depreciate everything else.
>=20
> You missed the boat about a decade back I guess. Transition
> technologies (none of them) are a substitute for actual deployment.
> They should naturally decline in popularity and in fact in the portions
> of the internet where we can measure them they are. Right now if we try
> and fit a story to the evidence that is happening because of host
> changes, and  not because of deployment. ipv4 is becoming less usable
> and it's taking autotunnels with it, nobody here has a proposal that
> changes that.
>=20
> >   We don't.  What we have are a
> > bunch of mechanisms, each with advantages and disadvantages,
> > some much better adapted to particular situations than others.
> > It would be easier if we had a good single solution, but we
> > don't... that is life, or at least engineering.  Given that, we
> > serve the community much better with analyses and explanations
> > of tradeoffs (and RFC 6180 is, IMO, a really good start) than we
> > do by going through exercises of figuring out what to denounce.
> > IMO, the _only_ thing we should be categorically denouncing are
> > tactics and strategies that encourage people to put off getting
> > serious about IPv6.  Unfortunately, trying to slap a "Historic"
> > label on one particular transition strategy, or to rank
> > transition strategies that have proven useful to some actors on
> > the basis of how much various of us loathe them, are about
> > denunciation and, however unintentionally, with the risk of
> > encouraging people to sit and wait, not about progress or
> > network engineering.
> >
> > back to lurking...
> >    john
> >
> >
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From moore@network-heretics.com  Sat Jul 16 13:49: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 AA55821F88A5; Sat, 16 Jul 2011 13:49:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.509
X-Spam-Level: 
X-Spam-Status: No, score=-3.509 tagged_above=-999 required=5 tests=[AWL=0.090,  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 A0XgFrlGt16J; Sat, 16 Jul 2011 13:49: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 BA97321F88A1; Sat, 16 Jul 2011 13:49:38 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id E2917221E4; Sat, 16 Jul 2011 16:49:37 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute3.internal (MEProxy); Sat, 16 Jul 2011 16:49: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=NXIi8yN2nTwEbi1SeyNmVfET6sg=; b=VwQ+mBSYU/QeFJFAzZSZqrGi3xdrlQO0nDBiV0tiHi452sNB2gwlzIzy/EzdY/IQguGzWjBxnS5zE/o5Z1JPSXe8O/5WVYP3iaqL9LeTXuL+HqfznRQANGBTwsp7x4JvZTpVb44rUGqjCHZiq84RLZ7Ymw61heWFbYhJy8Mm++o=
X-Sasl-enc: KoY5m9VTCqjEm4P5W04HLuAijN8T8C5sePl4FCSPCuOv 1310849377
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 804E8440898; Sat, 16 Jul 2011 16:49:36 -0400 (EDT)
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
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: <13205C286662DE4387D9AF3AC30EF456D3F3DEEA84@EMBX01-WF.jnpr.net>
Date: Sat, 16 Jul 2011 16:49:35 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4F5203D0-E4CC-4E52-A953-E90049032C2D@network-heretics.com>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <BBB3AB81-1A20-4022-8687-CD88B000B281@bogus.com> <A6908373951C6911489DF57A@PST.JCK.COM> <71D5A97D-7119-4082-BC87-6505370CE800@bogus.com> <13205C286662DE4387D9AF3AC30EF456D3F3DEEA84@EMBX01-WF.jnpr.net>
To: Ronald Bonica <rbonica@juniper.net>
X-Mailer: Apple Mail (2.1084)
Cc: John C Klensin <john-ietf@jck.com>, "v6ops@ietf.org" <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: Sat, 16 Jul 2011 20:49:39 -0000

On Jul 16, 2011, at 4:03 PM, Ronald Bonica wrote:

> Hi John,
>=20
> I think that most of the rancor around RFCs 3056 and 3068 is due to =
RFC 2026's very terse definition of HISTORIC. According to RFC 2026, "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." That's the entire definition. Anything more is read =
into it.
>=20
> Granted, the phrase "for any other reason considered to be obsolete" =
is pretty subjective. In this thread, I have seen people interpret that =
phrase as follows:
>=20
> "the IETF thinks that there are no longer any valid use cases for this =
technology"
> "the IETF recommends that you remove this technology from your =
network"
> "the IETF believes that nobody is using this technology"
>=20
> I doubt if any of these interpretations are valid, because the IETF is =
not in a good position to evaluate what is in use or tell an operator =
how to run a network.  A more likely interpretation is as follows:

> "the IETF is not likely to invest effort in the technology in the =
future"

Such a determination seems premature.  There are some ideas floating =
around for protocol fixes to deal with some of the operational problems =
associated with 6to4.  It's too early to know whether there are =
significant flaws with them or whether they can get traction.  =
Admittedly, v4 address space exhaustion along with the introduction of =
LSN means that 6to4 has diminishing applicability.  But for those nets =
and hosts that still have access to the public IPv4 internet, it's =
conceivable that the reliability of 6to4 can be considerably improved.  =
(Though of course it will never be as good as be as a well-run native v6 =
service.)   At some point, some evaluation of cost vs. benefit needs to =
be made; and the "cost" of not fixing 6to4 needs to consider the =
consequences of using other tunneled transition mechanisms besides 6to4. =
 =20

Put another way:  Given that there are admittedly several operational =
issues associated with 6to4, there are at least four strategies that =
might be employed:

1. Encourage changes to the operational practices that are causing =
problems that are associated with 6to4.
2. Discourage all use of 6to4 in the strongest possible terms.
3. Discourage use of 6to4 except in the cases where it is believed it =
can work well.
4. Improve the 6to4 protocol to address some of the issues.

IMO, -advisory tries to do #1;  -historic tries to do #2; -experimental =
tries to do #3.  #4 is something I hope can be discussed, informally, in =
Quebec.  We should have a better idea after the meeting how workable =
this is.

Keith


From john-ietf@jck.com  Sat Jul 16 15:52:45 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 7656321F89AC; Sat, 16 Jul 2011 15:52:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.644
X-Spam-Level: 
X-Spam-Status: No, score=-102.644 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 PO+X4+-kfWPM; Sat, 16 Jul 2011 15:52:44 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 0B0C521F89A7; Sat, 16 Jul 2011 15:52:43 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QiDix-000DjH-Sg; Sat, 16 Jul 2011 18:52:40 -0400
X-Vipre-Scanned: 0028B17B00262A0028B2C8-TDI
Date: Sat, 16 Jul 2011 18:52:38 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ronald Bonica <rbonica@juniper.net>, Joel Jaeggli <joelja@bogus.com>
Subject: RE: Another look at 6to4 (and other IPv6 transition issues)
Message-ID: <C2C73F7968F19FEEF11B2C67@[192.168.1.128]>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F3DEEA84@EMBX01-WF.jnpr.net>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <BBB3AB81-1A20-4022-8687-CD88B000B281@bogus.com> <A6908373951C6911489DF57A@PST.JCK.COM> <71D5A97D-7119-4082-BC87-6505370CE800@bogus.com> <13205C286662DE4387D9AF3AC30EF456D3F3DEEA84@EMBX01-WF.jnpr.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: 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: Sat, 16 Jul 2011 22:52:45 -0000

--On Saturday, July 16, 2011 16:03 -0400 Ronald Bonica
<rbonica@juniper.net> wrote:

> Hi John,
> 
> I think that most of the rancor around RFCs 3056 and 3068 is
> due to RFC 2026's very terse definition of HISTORIC. According
> to RFC 2026, "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."
> That's the entire definition. Anything more is read into it.

If you include a certain amount of oral tradition that predates
and surrounds 2026 in "read into it", I agree.  It may be worth
remembering that 2026, like most similar documents, didn't
invent anything but was intended to reflect a community
consensus that existed about what should be done.  Documents
like 2026 never capture that consensus exactly or
comprehensively.  Whether that informal consensus means anything
once we write something down is a question that we rarely ask
ourselves, probably for good reason.

> Granted, the phrase "for any other reason considered to be
> obsolete" is pretty subjective. In this thread, I have seen
> people interpret that phrase as follows:
> 
> "the IETF thinks that there are no longer any valid use cases
> for this technology" "the IETF recommends that you remove this
> technology from your network" "the IETF believes that nobody
> is using this technology"
 
> I doubt if any of these interpretations are valid, because the
> IETF is not in a good position to evaluate what is in use or
> tell an operator how to run a network. 

I think the first interpretation can be valid although it must
be used with great caution.   For example, I think we might all
agree that there are no remaining valid use cases for NCP,
despite the fact that TCP/IP could be argued to have replaced it
rather than precisely superceding it.  Another, perhaps better,
example is that Novell IPX is almost certainly dead
("proprietary protocol abandoned by its owner" is a pretty good
predictor of "no valid use cases").  We wouldn't think using it
for anything in a contemporary network would be useful even if,
e.g., it has better scaling properties.  Interestingly, while
RFC 1234 and 1553 were were moved to Historic, we have one Full
Standard (RFC 1123, STD 49), an Informational document (RFC
1634), a Proposed Standard (RFC 1420), and a some Experimental
documents (RFC 1791, RFC 1792).  That pretty much covers the
whole range of possibilities.    

If I didn't have the view that housekeeping exercises that
require community review and consensus were usually a poor use
of resources (see other note today), getting this whole pack
swept into Historic on the "no valid remaining use cases"
principle would be entirely appropriate.  One could still not
prove that no one is using it: I have every reason to believe
that someone out there is still running Netware and happy about
it.

> A more likely interpretation is as follows:
 
> "the IETF is not likely to invest effort in the technology in
> the future" "the IETF does not encourage (or discourage) new
> deployments of this technology.

Noting in passing that these sorts of statements are quite close
to the uses 2026 prescribes for Applicability Statements (and
for which we have even more precedent and oral tradition), if
the first of those is an adequate reason for identifying
something as historic, I recommend that we immediately move RFC
791 to Historic.  Certainly we are likely to invest more effort
in the development of the technology.  Now, some people would
read such a move as either an indication, as you suggest above,
that the IETF thought no one was using it any more, or that
there were no remaining valid use cases, etc., immediately
turning us into a laughingstock.  But, by logic that suggests
moving 6to4 to Historic on the grounds that the IETF is not
going to invest effort in the technology.

So I think we disagree.

best,
   john

> 
>                                                    Ron
> 
> 
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On
>> Behalf Of Joel Jaeggli
>> Sent: Friday, July 15, 2011 3:17 PM
>> To: John C Klensin
>> Cc: v6ops@ietf.org; IETF Discussion
>> Subject: Re: Another look at 6to4 (and other IPv6 transition
>> issues)
>> 
>> 
>> On Jul 15, 2011, at 11:52 AM, John C Klensin wrote:
>> 
>> > 
>> > 
>> > --On Friday, July 15, 2011 09:40 -0700 Joel Jaeggli
>> > <joelja@bogus.com> wrote:
>> > 
>> >> So the rational for the advice document not being combined
>> >> with the standards action in it is that the later has some
>> >> polarizing impact, the advice document does not. the advice
>> >> document is through and done, historic is not.
>> > 
>> > Joel (and others),
>> > 
>> > I understand the rationale.  At the risk of repeating
>> > myself, I simply do not think it works or is appropriate.
>> 
>> And there are people that disagree with you on that.
>> 
>> >  Recategorizing
>> > set of documents as "Historic" is an extremely blunt
>> > instrument. If we do it in a consistent and logical
>> > fashion, the advice document would have to go to Historic
>> > along with the base documents because giving advice about a
>> > piece of ancient history is meaningless.  That is not what
>> > most people who like the advice document intended, at least
>> > as I understood the consensus on that Last Call.
>> 
>> <SNIP>
>> 
>> > Finally, if we had a wonderful transition model that would
>> > work well in all situations, then it would make sense to
>> > recommend it and depreciate everything else.
>> 
>> You missed the boat about a decade back I guess. Transition
>> technologies (none of them) are a substitute for actual
>> deployment. They should naturally decline in popularity and
>> in fact in the portions of the internet where we can measure
>> them they are. Right now if we try and fit a story to the
>> evidence that is happening because of host changes, and  not
>> because of deployment. ipv4 is becoming less usable and it's
>> taking autotunnels with it, nobody here has a proposal that
>> changes that.
>> 
>> >   We don't.  What we have are a
>> > bunch of mechanisms, each with advantages and disadvantages,
>> > some much better adapted to particular situations than
>> > others. It would be easier if we had a good single
>> > solution, but we don't... that is life, or at least
>> > engineering.  Given that, we serve the community much
>> > better with analyses and explanations of tradeoffs (and RFC
>> > 6180 is, IMO, a really good start) than we do by going
>> > through exercises of figuring out what to denounce. IMO,
>> > the _only_ thing we should be categorically denouncing are
>> > tactics and strategies that encourage people to put off
>> > getting serious about IPv6.  Unfortunately, trying to slap
>> > a "Historic" label on one particular transition strategy,
>> > or to rank transition strategies that have proven useful to
>> > some actors on the basis of how much various of us loathe
>> > them, are about denunciation and, however unintentionally,
>> > with the risk of encouraging people to sit and wait, not
>> > about progress or network engineering.
>> > 
>> > back to lurking...
>> >    john
>> > 
>> > 
>> 
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf





From john-ietf@jck.com  Sat Jul 16 16:19:52 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 97BAF21F88A1 for <ietf@ietfa.amsl.com>; Sat, 16 Jul 2011 16:19:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.642
X-Spam-Level: 
X-Spam-Status: No, score=-102.642 tagged_above=-999 required=5 tests=[AWL=-0.043, 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 ZGP+qXU3hkJs for <ietf@ietfa.amsl.com>; Sat, 16 Jul 2011 16:19:52 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id CCAB621F8893 for <ietf@ietf.org>; Sat, 16 Jul 2011 16:19:51 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QiE9E-000E5G-Qf; Sat, 16 Jul 2011 19:19:49 -0400
X-Vipre-Scanned: 00418C8400269500418DD1-TDI
Date: Sat, 16 Jul 2011 19:19:48 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Last Call: <draft-yevstifeyev-ion-report-06.txt> (Report on the Experiment with IETF Operational Notes (IONs)) to Informational RFC
Message-ID: <59A80C7CC852BE52AF5E4757@[192.168.1.128]>
In-Reply-To: <CALaySJ+jn0GNmoHOZ2CRFpYGkOVxeUu1xjLx9vppC-uAnf2+DA@mail.gmail.com>
References: <20110712143944.20141.23357.idtracker@ietfa.amsl.com> <4E1C7B48.4070000@gmail.com>	<4E1CC89E.7010907@gmail.com> <4E1D0708.9090701@gmail.com> <CAC4RtVBvfgmJ3JOB6ZTYrWrQYarwbN7uYTi7XmdVS29BjG7PUw@mail.gmail.com> <C56B000FEF3F4C6475ABCE55@PST.JCK.COM> <CALaySJ+jn0GNmoHOZ2CRFpYGkOVxeUu1xjLx9vppC-uAnf2+DA@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jul 2011 23:19:52 -0000

--On Saturday, July 16, 2011 14:41 -0400 Barry Leiba
<barryleiba@computer.org> wrote:

>> Barry,
> ...
>> So, if only to increase my understanding, why do you think
>> reviewing this type of document (presumably through multiple
>> cycles as we quibble about language, etc.) is worth a Last
>> Call and the community's time?
> 
> John, you've mis-addressed this.  It's Mykyta who wants to do
> it ,not I.  I think it's at least as much a waste of time as
> you do.  The only reason I reviewed it and commented on the
> language at all was that Mykyta said Russ had agreed to
> shepherd it.  Either it needs to be published as it is,
> without further waste of time, or it needs to go away.

In case it isn't clear, I vote "go away" rather than wasting
even the amount of resources that would be required to publish
it substantially as is.  The community has to be able to say
"this isn't worth the energy" and establish consensus around
that.  

I suspect we agree about that; I'm just surprised and chagrined
that you, Harald, myself, and others are needing to spend energy
reading and understanding this and similar things before we can
reach that conclusion.

   john




From msk@cloudmark.com  Sat Jul 16 20:27:40 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 7178B21F8663; Sat, 16 Jul 2011 20:27:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.916
X-Spam-Level: 
X-Spam-Status: No, score=-103.916 tagged_above=-999 required=5 tests=[AWL=-0.317, 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 QxzzR37quLGZ; Sat, 16 Jul 2011 20:27:40 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id 0E84721F8661; Sat, 16 Jul 2011 20:27:40 -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, 16 Jul 2011 20:27:39 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: John C Klensin <john-ietf@jck.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Sat, 16 Jul 2011 20:27:39 -0700
Subject: RE: Another look at 6to4 (and other IPv6 transition issues)
Thread-Topic: Another look at 6to4 (and other IPv6 transition issues)
Thread-Index: AcxDMm0rkhKxPxQdSnShFXBOOYLS0wA/p8VQ
Message-ID: <F5833273385BB34F99288B3648C4F06F134EBC4D4F@EXCH-C2.corp.cloudmark.com>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <4E20A44E.3060203@gmail.com> <CF9FD8718237FDDA19BE31F8@PST.JCK.COM>
In-Reply-To: <CF9FD8718237FDDA19BE31F8@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: "v6ops@ietf.org" <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: Sun, 17 Jul 2011 03:27:40 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of J=
ohn C Klensin
> Sent: Friday, July 15, 2011 2:02 PM
> To: Brian E Carpenter
> Cc: v6ops@ietf.org; IETF Discussion
> Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
>=20
> Position #2: How the IETF classifies things makes very little
> difference in this space because people will follow advice that
> seems sensible and ignore everything else.  If so, it makes
> little difference how your document is approved or where it is
> published.  For example, it could have come through the
> Independent Stream or been pushed into CCR.  No problem.  And
> the "Historic" effort is a huge waste of the community's time,
> no matter how it comes out.

Well, if this is the prevailing opinion, we can certainly simplify our proc=
edures substantially by eliminating about half of the document states we ma=
intain now, including reducing the standards track down to a single state.

From dougb@dougbarton.us  Sat Jul 16 21:59:37 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 F03B921F8669 for <ietf@ietfa.amsl.com>; Sat, 16 Jul 2011 21:59:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.254
X-Spam-Level: 
X-Spam-Status: No, score=-3.254 tagged_above=-999 required=5 tests=[AWL=-0.255, 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 hMrPGoq-vd7B for <ietf@ietfa.amsl.com>; Sat, 16 Jul 2011 21:59:35 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 8F38021F8663 for <ietf@ietf.org>; Sat, 16 Jul 2011 21:59:35 -0700 (PDT)
Received: (qmail 6579 invoked by uid 399); 17 Jul 2011 04:59:31 -0000
Received: from unknown (HELO 65-241-43-4.globalsuite.net) (dougb@dougbarton.us@65.241.43.4) by mail2.fluidhosting.com with ESMTPAM; 17 Jul 2011 04:59:31 -0000
X-Originating-IP: 65.241.43.4
X-Sender: dougb@dougbarton.us
Message-ID: <4E226C22.1000307@dougbarton.us>
Date: Sat, 16 Jul 2011 21:59:14 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110706 Thunderbird/5.0
MIME-Version: 1.0
To: John C Klensin <john@jck.com>
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <4E20C1BF.3040302@dougbarton.us> <8227832E0BE58765FB9BBFC1@PST.JCK.COM>
In-Reply-To: <8227832E0BE58765FB9BBFC1@PST.JCK.COM>
X-Enigmail-Version: 1.2pre
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Jul 2011 04:59:37 -0000

On 07/16/2011 07:02, John C Klensin wrote:
> 
> 
> --On Friday, July 15, 2011 15:39 -0700 Doug Barton
> <dougb@dougbarton.us> wrote:
> 
>> To address your concern about whether or not vendors are paying
>> attention to this discussion, and why historic status is
>> substantively different than "off by default, no really, OFF
>> BY DEFAULT," I'll put my FreeBSD developer hat on for a minute
>> and tell you that we definitely do pay attention to stuff like
>> this, and whereas we already have it off by default (and have
>> for some time) moving it to historic gives us the cover we
>> need to remove the code at some point down the road when that's
>> appropriate. That's an extremely important distinction, and
>> one of the reasons that as a "member" of v6ops I ultimately
>> came down in support of the 2-document strategy.
> 
> Doug,
> 
> And that is exactly where we agree on the effect and disagree
> about whether it is desirable.

Right.

> I think there is consensus that 6to4 is dangerous unless
> carefully and intelligently configured and that is certainly
> should not be turned on by default.  If anyone has argued
> against that position, they are in a tiny minority.  
> 
> Similarly, I think there is consensus that following the advice
> in the "advice" document makes 6to4 much safer to use, even if
> not entirely risk-free (I contend that there is no "risk-free",
> perhaps as a corollary to the principle that, if we invent
> something idiot-proof, someone will invent a better idiot).  So
> there should be no question about the desirability about
> publishing the content of that document.  

Agreed so far, especially about the idiots. :)

> The question, as far as the "advice" document is concerned, is
> how to get the message out most effectively, most clearly, and
> on as timely a basis as possible.  I think that having it
> "update" the base 6to4 specs is important because that is how
> the RFC Series is threaded.  Without that, there is an increased
> risk of people finding the 6to4 specs and implementing them
> without ever seeing the "advice" piece (just as, even with the
> "updates"/"updated by" pointers, we still hear about new TCP
> implementations based on RFC 793 alone).  For the reasons
> discussed above, I don't think anyone would find that outcome
> desirable. 

You know the subtleties of the various document tracks infinitely better
than I do, so I'm not even going to try and debate you on that.

OTOH, I find the idea of someone implementing 6to4 from scratch at this
point highly unlikely. I also think that declaring it historic would
make the scenario you describe that much more unlikely.

[snip]

> But, while some people have argued that 6to4 has caused so much
> damage by being misconfigured that it should, presumably as
> punishment or to create a public example, be eliminated entirely
> as an option

My perspective, which I've described at length many times now, is not
that 6to4 needs to be punished, but that the widespread deployment of
IPv6 is being harmed as a result of the negative user experience that it
creates for the majority of its users (particularly the unintentional
ones) and therefore the network as a whole is better off if it goes away.

To summarize my main points once again (since you seem determined to
reopen the debate on 6to4's utility):

1. There is next to zero IPv6-only content at this time.
2. Therefore the number of people who actually *need* IPv6 is so close
to zero as to not be a factor.
3. Of the tiny number of people that actually do need IPv6, there are
plenty of other tunnel options.
4. By the time that there *is* IPv6-only content the market will have
sorted out access for the average user.

Thus, 6to4 hurts way more than it helps at this point.

Furthermore you have the huge problem that neither end of the 6to4
equation has *any* motivation to fix it. The ISP side can simply block
tunnels (or even simpler, ignore the problem). The content side can
simply not deploy AAAA records.

I do think that the -advice document is a good thing, and for those that
care I think it's great that the IETF is going to help them out. But all
statements of the form "all we need to do to fix 6to4 is X" are
non-starters because the people with the ability to actually fix it are
not going to.

> -- for FreeBSD users, the exact effect of your removing the code --

To be clear, I didn't say that we *will* remove it, only that making it
historic gives us that opportunity at some point down the road *if* that
becomes appropriate.

> I haven't seen nearly as strong as case, or
> anything even close to consensus, for that position.   If it was
> actually what the community believed, then the "advice" document
> would be a complete waste of time except possibly as a
> retrospective on how 6to4 might have been better specified (a
> retrospective that we would want to publish as (immediately)
> Historic).

Once again repeating myself, but I disagree. The idea of publishing both
documents represents a fine compromise between the 2 extreme positions,
and allows those who want to continue using it to do so in the best way
possible. It's also not the first time the IETF has published a document
that says, effectively, "We don't think you should do this, but if
you're going to do it anyway, here's how to do it right."

> If the thing is still useful, even in limited circumstances and
> used correctly, then the IETF should not provide you with
> "cover" to remove the code because it is not in the best
> interest of the community for you to remove the code.   Might
> both your removing the code and moving 6to4 to Historic in the
> future be appropriate?  Sure.  I also look forward to the day
> when we can move IPv4 to Historic (just as the various
> specifications that make up NCP should have been moved years ago
> if we paid attention to that sort of housekeeping).

So the debate is on the timing. I (and others) think that the time is
now. My opinion is that there is also a pretty strong community
consensus that the time is now, modulo a very vocal group of people who
do not. But fortunately I'm not the one who has to make the decision
about what there is and is not consensus for. :)

[snip]

> FWIW, I note that there are at least a few other things that
> shipped for years with FreeBSD that could cause a lot of damage
> if misconfigured and were hard to configure correctly, but were
> nonetheless included in the code in version after version and
> even were enabled by default.  Getting rid of them would not
> have required any IETF action -- there were other
> implementations of the same protocols that could have been
> included in the base systems instead.  But they weren't removed
> or replaced (the folks who produced them eventually produced
> better versions). 

Putting my FreeBSD hat back on for a second, we're always interested in
improving our code base, and would certainly not want to intentionally
do anything to "cause a lot of damage." If there are concrete concerns
anyone should feel free to file a Problem Report at
http://www.freebsd.org/send-pr.html, or use the 'send-pr' utility in
FreeBSD.

> But I don't recall seeing the sort of venom
> that is directed toward 6to4 being focused on them.  Perhaps
> there weren't enough complaints or you have solid data that 6to4
> has caused even more damage.

Once again repeating myself ... I have no venom towards 6to4. This isn't
a personal attack. And yes, various people and organizations that have
vested interests in seeing IPv6 deployed have posted the data about why
6to4 causes way more problems than it solves, and I believe them.


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 julian.reschke@gmx.de  Sun Jul 17 03:46:53 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 A451721F859F for <ietf@ietfa.amsl.com>; Sun, 17 Jul 2011 03:46:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.939
X-Spam-Level: 
X-Spam-Status: No, score=-103.939 tagged_above=-999 required=5 tests=[AWL=-1.340, 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 oUyJWwkNHA1W for <ietf@ietfa.amsl.com>; Sun, 17 Jul 2011 03:46: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 B922D21F86DC for <ietf@ietf.org>; Sun, 17 Jul 2011 03:46:52 -0700 (PDT)
Received: (qmail invoked by alias); 17 Jul 2011 10:46:48 -0000
Received: from p508FB444.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.180.68] by mail.gmx.net (mp003) with SMTP; 17 Jul 2011 12:46:48 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18HZPFhV9QH/Pl+FeMMK0zy3vLyIj5H3uVGp5WiG6 yHXdgtwRyyP11z
Message-ID: <4E22BD8E.7000703@gmx.de>
Date: Sun, 17 Jul 2011 12:46:38 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: HTTP header field and upgrade token definitions, was: Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com>
In-Reply-To: <20110711140229.17432.23519.idtracker@ietfa.amsl.com>
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: Sun, 17 Jul 2011 10:46:53 -0000

On 2011-07-11 16:02, The IESG wrote:
> ...

This is a set of comments on how the specification defines new HTTP 
header fields and the upgrade token.

1) In the IANA considerations section, please group subsections by 
registrations and new registries.

2) "Specification document(s)" should actually point to the part of the 
spec that *specifies* the thing being registered. Just saying RFC nnnn 
or "this document" wastes the reader's time.

3) That being said, the header field registrations each contain a 
paragraph of prose explaining the header field. *Is* this the 
specification of the header, or does it only summarize more information 
from somewhere else? If so, from where?

4) Each header field definition needs to say what the header means in 
general, and what the syntax is (the latter can be either prose or ABNF, 
but ABNF would be preferred). It's not sufficient to describe it as part 
of a Websocket-specific algorithm - what's needed is a statement about 
what the header means on an HTTP message in general (and yes, saying 
it's only allowed in this or that context, and that it's meaningless 
otherwise would be ok).

Best regards, Julian

From moore@network-heretics.com  Sun Jul 17 08:17: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 65D7621F8793 for <ietf@ietfa.amsl.com>; Sun, 17 Jul 2011 08:17:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.209
X-Spam-Level: 
X-Spam-Status: No, score=-3.209 tagged_above=-999 required=5 tests=[AWL=-0.211, 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 0KPF6j7srNMb for <ietf@ietfa.amsl.com>; Sun, 17 Jul 2011 08:17: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 7ECB021F854D for <ietf@ietf.org>; Sun, 17 Jul 2011 08:17:41 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id AA6B420423; Sun, 17 Jul 2011 11:17:40 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute6.internal (MEProxy); Sun, 17 Jul 2011 11:17: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:message-id:references:to; s=smtpout; bh=1GXxOP4PHEO519Spl0qRWNcq/hg=; b=fWDHFA7o3qDQjfIlgQr+KVPpCiff5zUZaKEmS15hOAr6Q088b7wOswSJzdcBNZtgnrK1NcbA+gFUBSlZzPNMiVWK6oFy0tQ9yGyzhN+KL2tebH04LFd5gv9WHd3QyJ7paLbjUf18iqcHAUcAAKtsplIDmQZyTxsPcRGooUrafl4=
X-Sasl-enc: d0Wg7quKHekkKxHNt3FU4n/IcrqQ90URYbLS7GYa4sCj 1310915858
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 0D578440299; Sun, 17 Jul 2011 11:17:37 -0400 (EDT)
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-4--251308101
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E226C22.1000307@dougbarton.us>
Date: Sun, 17 Jul 2011 11:17:37 -0400
Message-Id: <70A2263A-034C-45E8-B30E-87B2DA64EF9F@network-heretics.com>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <4E20C1BF.3040302@dougbarton.us> <8227832E0BE58765FB9BBFC1@PST.JCK.COM> <4E226C22.1000307@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
X-Mailer: Apple Mail (2.1084)
Cc: John C Klensin <john@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Jul 2011 15:17:45 -0000

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

On Jul 17, 2011, at 12:59 AM, Doug Barton wrote:

>> But, while some people have argued that 6to4 has caused so much
>> damage by being misconfigured that it should, presumably as
>> punishment or to create a public example, be eliminated entirely
>> as an option
>=20
> My perspective, which I've described at length many times now, is not
> that 6to4 needs to be punished, but that the widespread deployment of
> IPv6 is being harmed as a result of the negative user experience that =
it
> creates for the majority of its users (particularly the unintentional
> ones) and therefore the network as a whole is better off if it goes =
away.

It doesn't follow.

Nor would declaring 6to4 Historic (or any other label) have that effect. =
  It could easily make things worse for both users and content =
providers, by giving people the mistaken impression that "remedial" =
actions like filtering protocol 41 or advertisements for 6to4 relay =
routers are good ideas.  =20

The fixes for unintentional users of 6to4 are already in the pipeline.  =
Everybody agrees that the default address selection preferences should =
be changed to prefer native IPv4 over 6to4, and host platforms =
(including FreeBSD I assume) have already changed these preferences or =
are in the process of doing so.    Most platforms have ways of pushing =
urgent updates to their users, and IMO this change in the address =
selection preference list should qualify for such updates.   (As for the =
users who don't make use of that feature and/or turn automatic updating =
off, declaring 6to4 Historic would not make them more likely to use such =
updates.)

> To summarize my main points once again (since you seem determined to
> reopen the debate on 6to4's utility):
>=20
> 1. There is next to zero IPv6-only content at this time.
> 2. Therefore the number of people who actually *need* IPv6 is so close
> to zero as to not be a factor.

#2 does not follow from #1, for various reasons.   One reason is that =
the Internet is highly diverse, and people use it for many other things =
than to download "content" from "content providers".

> 3. Of the tiny number of people that actually do need IPv6, there are
> plenty of other tunnel options.

...which are often worse than 6to4, for some meaning of "worse" (more =
overhead, longer delay, greater likelihood of path congestion, single =
point of failure, reduced probability of getting a connection =
established).

> 4. By the time that there *is* IPv6-only content the market will have
> sorted out access for the average user.

The market hasn't sorted out IPv6 access in the past 15+ years, mostly =
because of the lack of any new v6-only applications or usage scenarios =
that would drive IPv6 deployment.   Under current conditions, there is =
zero incentive to produce IPv6-only content because would block 99.99% =
of the potential market for said content.   HTTP and SMTP will be the =
last protocols to migrate to IPv6, not the first ones.   Prior to =
widespread deployment of IPv6 access, any use of HTTP-over-IPv6 to serve =
content to the public, or SMTP-over-IPv6 to exchange mail between =
arbitrary administrative mail domains, is either a proof-of-concept or a =
publicity stunt. =20

So the idea of waiting until there is IPv6-only content to drive the =
market to provide IPv6 access for the average user, is a nonstarter.

> Thus, 6to4 hurts way more than it helps at this point.

It doesn't follow even if one accepts the premise of #4 (which is not a =
reasonable premise).

And again, nobody disputes that unintentional use of 6to4 is harmful.  =
But that fix is already in the pipeline, via much more effective means =
than any label that could be put on 6to4.

> Furthermore you have the huge problem that neither end of the 6to4
> equation has *any* motivation to fix it. The ISP side can simply block
> tunnels (or even simpler, ignore the problem). The content side can
> simply not deploy AAAA records.

Blocking tunnels makes the situation worse both for users (who will =
experience even more connection failures) and for operators (who will =
experience even more support calls).   We need to get that message out =
as loudly and as clearly as possible.

As for content providers, there are lots of ways for them to provide =
content over HTTP-over-IPv6 without exposing that content to 6to4 users, =
or (better) without exposing that content to users with poor IPv6 =
connections.  =20

One way is this: make the initial connection - the advertised URL - use =
a domain name which only has A records.  This is safe to do because for =
the foreseeable future, everybody will have some kind of IPv4 HTTP =
access.   Have the initial connection provide referrals to the "real" =
content using one of two different domain names, based on whether the =
source address is within 2002::/16: ipv4.example.com only returns A =
records, ipv6.example.com returns both AAAA and A records.  A lot of =
content is using referrals for various reasons anyway, so it might be =
possible to do this without any additional overhead.  Offhand this seems =
a lot more reliable than playing games with DNS.

Another, perhaps better, way:   Again, have the advertised URL use a =
domain name that only has A records.   Have the main page set a cookie, =
the value of which is based on a timestamp.   Also have the initial page =
load a one-pixel image via a URL with a domain that only has IPv6 =
addresses.  This image sets its own cookie, also based on a timestamp.   =
If the server gets a request with the v4 cookie's timestamp much earlier =
than the v6 cookie's timestamp, or if the v6 cookie is missing, make all =
links and referrals use only A records.  If the v4 and v6 cookies are =
both present and have similar timestamps, the links and referrals can =
have AAAA records.

Of course both of the above depend on using different URL domains =
depending on whether the content provider wants to provide v4-only or =
dual-stack service to the client.  The content provider might prefer to =
use the same domain in both cases and play games with DNS based on the =
requester address.  (which causes a different set of issues). =20

But at least with the web, it seems like enough tools are there to let =
content providers serve content via v6 when it works well, and minimize =
use of v6 for those users for whom it doesn't work well, as well as to =
keep track of how often v6 is working for their users.  Admittedly, it's =
a bit more work than just adding AAAA records to existing DNS names and =
enabling v6 on the servers.   =20

> I do think that the -advice document is a good thing, and for those =
that
> care I think it's great that the IETF is going to help them out. But =
all
> statements of the form "all we need to do to fix 6to4 is X" are
> non-starters because the people with the ability to actually fix it =
are
> not going to.

Speculation.   =20

How can we expect people to have "fixed" 6to4 without their being clear =
recommendations for how to do that?   Arguably, a lot of the problems =
that we're seeing with 6to4 are the results of poorly chosen "fixes" =
(like protocol 41 filtering) that actually exacerbate the problem.

(For that matter, how do you know that people aren't slowly discovering =
how to "fix" 6to4, and doing it?   I assure you, 6to4 works better now =
than it did 10 years ago.  It's reasonable to believe that the measures =
in -advisory will also help the situation.)

>> -- for FreeBSD users, the exact effect of your removing the code --
>=20
> To be clear, I didn't say that we *will* remove it, only that making =
it
> historic gives us that opportunity at some point down the road *if* =
that
> becomes appropriate.

The FreeBSD developers can do whatever they like with their code.   They =
don't need for IETF to declare it anything.  If they want to remove 6to4 =
support, they can do so and deal with the criticism and/or praise from =
their users.  =20

Hopefully, "at some point down the road", presumably when native IPv6 is =
widely available, it will make sense to declare 6to4 Historic, and we'll =
all celebrate when that happens. =20

>> If the thing is still useful, even in limited circumstances and
>> used correctly, then the IETF should not provide you with
>> "cover" to remove the code because it is not in the best
>> interest of the community for you to remove the code.   Might
>> both your removing the code and moving 6to4 to Historic in the
>> future be appropriate?  Sure.  I also look forward to the day
>> when we can move IPv4 to Historic (just as the various
>> specifications that make up NCP should have been moved years ago
>> if we paid attention to that sort of housekeeping).
>=20
> So the debate is on the timing. I (and others) think that the time is
> now. My opinion is that there is also a pretty strong community
> consensus that the time is now, modulo a very vocal group of people =
who
> do not. But fortunately I'm not the one who has to make the decision
> about what there is and is not consensus for. :)

=46rom my perspective, the "very vocal group of people" is in v6ops, =
which is heavily biased toward the operator's viewpoint, and against the =
user's and application developer's viewpoint.  They haven't even tried =
to get community consensus on this.

>> But I don't recall seeing the sort of venom
>> that is directed toward 6to4 being focused on them.  Perhaps
>> there weren't enough complaints or you have solid data that 6to4
>> has caused even more damage.
>=20
> Once again repeating myself ... I have no venom towards 6to4. This =
isn't
> a personal attack. And yes, various people and organizations that have
> vested interests in seeing IPv6 deployed have posted the data about =
why
> 6to4 causes way more problems than it solves, and I believe them.


They've posted data about why unintentional use of 6to4 causes more =
problems than it solves.  And that's being fixed.

Keith


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

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jul 17, 2011, at 12:59 AM, Doug Barton =
wrote:</div><br><blockquote type=3D"cite"><div><blockquote =
type=3D"cite">But, while some people have argued that 6to4 has caused so =
much<br></blockquote><blockquote type=3D"cite">damage by being =
misconfigured that it should, presumably as<br></blockquote><blockquote =
type=3D"cite">punishment or to create a public example, be eliminated =
entirely<br></blockquote><blockquote type=3D"cite">as an =
option<br></blockquote><br>My perspective, which I've described at =
length many times now, is not<br>that 6to4 needs to be punished, but =
that the widespread deployment of<br>IPv6 is being harmed as a result of =
the negative user experience that it<br>creates for the majority of its =
users (particularly the unintentional<br>ones) and therefore the network =
as a whole is better off if it goes =
away.<br></div></blockquote><div><br></div><div>It doesn't =
follow.</div><div><br></div><div>Nor would declaring 6to4 Historic (or =
any other label) have that effect. &nbsp; It could easily make things =
worse for both users and content providers, by giving people the =
mistaken impression that "remedial" actions like filtering protocol 41 =
or advertisements for 6to4 relay routers are good ideas. =
&nbsp;&nbsp;</div><div><br></div><div>The fixes for unintentional users =
of 6to4 are already in the pipeline. &nbsp;Everybody agrees that the =
default address selection preferences should be changed to prefer native =
IPv4 over 6to4, and host platforms (including FreeBSD I assume) have =
already changed these preferences or are in the process of doing so. =
&nbsp; &nbsp;Most platforms have ways of pushing urgent updates to their =
users, and IMO this change in the address selection preference list =
should qualify for such updates. &nbsp; (As for the users who don't make =
use of that feature and/or turn automatic updating off, declaring 6to4 =
Historic would not make them more likely to use such =
updates.)</div></div><div><br><blockquote type=3D"cite"><div>To =
summarize my main points once again (since you seem determined =
to<br>reopen the debate on 6to4's utility):<br><br>1. There is next to =
zero IPv6-only content at this time.<br>2. Therefore the number of =
people who actually *need* IPv6 is so close<br>to zero as to not be a =
factor.<br></div></blockquote><div><br></div>#2 does not follow from #1, =
for various reasons. &nbsp; One reason is that the Internet is highly =
diverse, and people use it for many other things than to download =
"content" from "content providers".</div><div><br><blockquote =
type=3D"cite"><div>3. Of the tiny number of people that actually do need =
IPv6, there are<br>plenty of other tunnel =
options.<br></div></blockquote><div><br></div>...which are often worse =
than 6to4, for some meaning of "worse" (more overhead, longer delay, =
greater likelihood of path congestion, single point of failure, reduced =
probability of getting a connection =
established).</div><div><br><blockquote type=3D"cite"><div>4. By the =
time that there *is* IPv6-only content the market will have<br>sorted =
out access for the average =
user.<br></div></blockquote><div><br></div>The market hasn't sorted out =
IPv6 access in the past 15+ years, mostly because of the lack of any new =
v6-only applications or usage scenarios that would drive IPv6 =
deployment. &nbsp; Under current conditions, there is zero incentive to =
produce IPv6-only content because would block 99.99% of the potential =
market for said content. &nbsp; HTTP and SMTP will be the last protocols =
to migrate to IPv6, not the first ones. &nbsp; Prior to widespread =
deployment of IPv6 access, any use of HTTP-over-IPv6 to serve content to =
the public, or SMTP-over-IPv6 to exchange mail between arbitrary =
administrative mail domains, is either a proof-of-concept or a publicity =
stunt. &nbsp;</div><div><br></div><div>So the idea of waiting until =
there is IPv6-only content to drive the market to provide IPv6 access =
for the average user, is a nonstarter.</div><div><br><blockquote =
type=3D"cite"><div>Thus, 6to4 hurts way more than it helps at this =
point.<br></div></blockquote><div><br></div>It doesn't follow even if =
one accepts the premise of #4 (which is not a reasonable =
premise).</div><div><br></div><div>And again, nobody disputes that =
unintentional use of 6to4 is harmful. &nbsp;But that fix is already in =
the pipeline, via much more effective means than any label that could be =
put on 6to4.</div><div><br><blockquote type=3D"cite"><div>Furthermore =
you have the huge problem that neither end of the 6to4<br>equation has =
*any* motivation to fix it. The ISP side can simply block<br>tunnels (or =
even simpler, ignore the problem). The content side can<br>simply not =
deploy AAAA records.<br></div></blockquote><div><br></div><div>Blocking =
tunnels makes the situation worse both for users (who will experience =
even more connection failures) and for operators (who will experience =
even more support calls). &nbsp; We need to get that message out as =
loudly and as clearly as possible.</div><div><br></div><div>As for =
content providers, there are lots of ways for them to provide content =
over HTTP-over-IPv6 without exposing that content to 6to4 users, or =
(better) without exposing that content to users with poor IPv6 =
connections. &nbsp;&nbsp;</div><div><br></div><div>One way is this: make =
the initial connection - the advertised URL - use a domain name which =
only has A records. &nbsp;This is safe to do because for the foreseeable =
future, everybody will have some kind of IPv4 HTTP access. &nbsp; Have =
the initial connection provide referrals to the "real" content using one =
of two different domain names, based on whether the source address is =
within 2002::/16: <a href=3D"http://ipv4.example.com">ipv4.example.com</a>=
 only returns A records, <a =
href=3D"http://ipv6.example.com">ipv6.example.com</a> returns both AAAA =
and A records. &nbsp;A lot of content is using referrals for various =
reasons anyway, so it might be possible to do this without any =
additional overhead. &nbsp;Offhand this seems a lot more reliable than =
playing games with DNS.</div><div><br></div><div>Another, perhaps =
better, way: &nbsp; Again, have the advertised URL use a domain name =
that only has A records. &nbsp; Have the main page set a cookie, the =
value of which is based on a timestamp. &nbsp; Also have the initial =
page load a one-pixel image via a URL with a domain that only has IPv6 =
addresses. &nbsp;This image sets its own cookie, also based on a =
timestamp. &nbsp; If the server gets a request with the v4 cookie's =
timestamp much earlier than the v6 cookie's timestamp, or if the v6 =
cookie is missing, make all links and referrals use only A records. =
&nbsp;If the v4 and v6 cookies are both present and have similar =
timestamps, the links and referrals can have AAAA =
records.</div><div><br></div><div>Of course both of the above depend on =
using different URL domains depending on whether the content provider =
wants to provide v4-only or dual-stack service to the client. &nbsp;The =
content provider might prefer to use the same domain in both cases and =
play games with DNS based on the requester address. &nbsp;(which causes =
a different set of issues). &nbsp;</div><div><br></div><div>But at least =
with the web, it seems like enough tools are there to let content =
providers serve content via v6 when it works well, and minimize use of =
v6 for those users for whom it doesn't work well, as well as to keep =
track of how often v6 is working for their users. &nbsp;Admittedly, it's =
a bit more work than just adding AAAA records to existing DNS names and =
enabling v6 on the servers. &nbsp; =
&nbsp;</div></div><div><br><blockquote type=3D"cite"><div>I do think =
that the -advice document is a good thing, and for those that<br>care I =
think it's great that the IETF is going to help them out. But =
all<br>statements of the form "all we need to do to fix 6to4 is X" =
are<br>non-starters because the people with the ability to actually fix =
it are<br>not going =
to.<br></div></blockquote><div><br></div>Speculation. &nbsp; =
&nbsp;</div><div><br></div><div>How can we expect people to have "fixed" =
6to4 without their being clear recommendations for how to do that? =
&nbsp; Arguably, a lot of the problems that we're seeing with 6to4 are =
the results of poorly chosen "fixes" (like protocol 41 filtering) that =
actually exacerbate the problem.</div><div><br></div><div>(For that =
matter, how do you know that people aren't slowly discovering how to =
"fix" 6to4, and doing it? &nbsp; I assure you, 6to4 works better now =
than it did 10 years ago. &nbsp;It's reasonable to believe that the =
measures in -advisory will also help the =
situation.)</div><div><br><blockquote type=3D"cite"><div><blockquote =
type=3D"cite">-- for FreeBSD users, the exact effect of your removing =
the code --<br></blockquote><br>To be clear, I didn't say that we *will* =
remove it, only that making it<br>historic gives us that opportunity at =
some point down the road *if* that<br>becomes =
appropriate.<br></div></blockquote><div><br></div>The FreeBSD developers =
can do whatever they like with their code. &nbsp; They don't need for =
IETF to declare it anything. &nbsp;If they want to remove 6to4 support, =
they can do so and deal with the criticism and/or praise from their =
users. &nbsp;&nbsp;</div><div><br></div><div>Hopefully, "at some point =
down the road", presumably when native IPv6 is widely available, it will =
make sense to declare 6to4 Historic, and we'll all celebrate when that =
happens. &nbsp;</div><div><br></div><div><blockquote =
type=3D"cite"><div><blockquote type=3D"cite">If the thing is still =
useful, even in limited circumstances and<br></blockquote><blockquote =
type=3D"cite">used correctly, then the IETF should not provide you =
with<br></blockquote><blockquote type=3D"cite">"cover" to remove the =
code because it is not in the best<br></blockquote><blockquote =
type=3D"cite">interest of the community for you to remove the code. =
&nbsp;&nbsp;Might<br></blockquote><blockquote type=3D"cite">both your =
removing the code and moving 6to4 to Historic in =
the<br></blockquote><blockquote type=3D"cite">future be appropriate? =
&nbsp;Sure. &nbsp;I also look forward to the =
day<br></blockquote><blockquote type=3D"cite">when we can move IPv4 to =
Historic (just as the various<br></blockquote><blockquote =
type=3D"cite">specifications that make up NCP should have been moved =
years ago<br></blockquote><blockquote type=3D"cite">if we paid attention =
to that sort of housekeeping).<br></blockquote><br>So the debate is on =
the timing. I (and others) think that the time is<br>now. My opinion is =
that there is also a pretty strong community<br>consensus that the time =
is now, modulo a very vocal group of people who<br>do not. But =
fortunately I'm not the one who has to make the decision<br>about what =
there is and is not consensus for. =
:)<br></div></blockquote><div><br></div><div>=46rom my perspective, the =
"very vocal group of people" is in v6ops, which is heavily biased toward =
the operator's viewpoint, and against the user's and application =
developer's viewpoint. &nbsp;They haven't even tried to get community =
consensus on this.</div><div><br></div></div><div><blockquote =
type=3D"cite"><div><blockquote type=3D"cite">But I don't recall seeing =
the sort of venom<br></blockquote><blockquote type=3D"cite">that is =
directed toward 6to4 being focused on them. =
&nbsp;Perhaps<br></blockquote><blockquote type=3D"cite">there weren't =
enough complaints or you have solid data that =
6to4<br></blockquote><blockquote type=3D"cite">has caused even more =
damage.<br></blockquote><br>Once again repeating myself ... I have no =
venom towards 6to4. This isn't<br>a personal attack. And yes, various =
people and organizations that have<br>vested interests in seeing IPv6 =
deployed have posted the data about why<br>6to4 causes way more problems =
than it solves, and I believe =
them.<br></div></blockquote></div><div><br></div><div>They've posted =
data about why <i>unintentional use</i> of 6to4 causes more problems =
than it solves. &nbsp;And that's being =
fixed.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-4--251308101--

From john-ietf@jck.com  Sun Jul 17 13:32:36 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 7DA3F21F85CE; Sun, 17 Jul 2011 13:32:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.637
X-Spam-Level: 
X-Spam-Status: No, score=-102.637 tagged_above=-999 required=5 tests=[AWL=-0.038, 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 LPLPGWuhH8rM; Sun, 17 Jul 2011 13:32:36 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id B1F2121F85C6; Sun, 17 Jul 2011 13:32:35 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QiY0v-000464-DU; Sun, 17 Jul 2011 16:32:33 -0400
X-Vipre-Scanned: 02D25EC200269D02D2600F-TDI
Date: Sun, 17 Jul 2011 16:32:32 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Murray S. Kucherawy" <msk@cloudmark.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: Another look at 6to4 (and other IPv6 transition issues)
Message-ID: <62EC33D058BC86D3A48291DE@[192.168.1.128]>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F134EBC4D4F@EXCH-C2.corp.cloudmark.com>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <4E20A44E.3060203@gmail.com> <CF9FD8718237FDDA19BE31F8@PST.JCK.COM> <F5833273385BB34F99288B3648C4F06F134EBC4D4F@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
Cc: 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: Sun, 17 Jul 2011 20:32:36 -0000

--On Saturday, July 16, 2011 20:27 -0700 "Murray S. Kucherawy"
<msk@cloudmark.com> wrote:

>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On
>> Behalf Of John C Klensin Sent: Friday, July 15, 2011 2:02 PM
>> To: Brian E Carpenter
>> Cc: v6ops@ietf.org; IETF Discussion
>> Subject: Re: Another look at 6to4 (and other IPv6 transition
>> issues)
>> 
>> Position #2: How the IETF classifies things makes very little
>> difference in this space because people will follow advice
>> that seems sensible and ignore everything else.  If so, it
>> makes little difference how your document is approved or
>> where it is published.  For example, it could have come
>> through the Independent Stream or been pushed into CCR.  No
>> problem.  And the "Historic" effort is a huge waste of the
>> community's time, no matter how it comes out.
> 
> Well, if this is the prevailing opinion, we can certainly
> simplify our procedures substantially by eliminating about
> half of the document states we maintain now, including
> reducing the standards track down to a single state.

I certainly would not claim it is the prevailing opinion.  I
believe it is true and have seen it in action many times but,
beyond that, have no idea.   Also remember that the Standards
Track (including BCP or not), Experimmental, Informational,
Historic breakdown is somewhat orthogonal to the maturity levels
within Standards Track.

That said, I believe, based in part on consensus in at least one
WG that focused on the topic, that, as our standards have become
more complex, with more features, options, and interactions, the
embodiment of the "maturity level" idea as a single set of
category-identifiers has outlived its usefulness.  The reality
is that some features of a particular specification may be
well-tested and very mature while others may still be a bit
questionable and that some specifications may be more
appropriate to some environments and less appropriate to others.
>From that point of view, forcing entire protocols or
specifications into one category or another does both the IETF
community and the users of the specs a disservice: we should be
telling people what we think of a spec, how mature things are,
and what the issues are, if necessary on a
characteristic-by-characteristic basis, not pretending that
assignment of a label communicates significant information.
>From that point of view, reducing the number of categories
increases the odds of classifications being misleading and
communicating little real information, if only from "very
likely" to "near-certain".  But, again, that is just IMO.

    john


From rogerj@gmail.com  Mon Jul 18 00:36:09 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 1974621F8B12 for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 00:36:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.186
X-Spam-Level: 
X-Spam-Status: No, score=-3.186 tagged_above=-999 required=5 tests=[AWL=0.113,  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 MdI7OmArjD7Y for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 00:36:05 -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 A77A421F8B4A for <ietf@ietf.org>; Mon, 18 Jul 2011 00:36:04 -0700 (PDT)
Received: by wyj26 with SMTP id 26so1118871wyj.31 for <ietf@ietf.org>; Mon, 18 Jul 2011 00:36:03 -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:content-transfer-encoding; bh=0n3NB/kO2YFsSoGvNVPGdd+X81gcH1IsxGlleFDw5y8=; b=Fvig11KHsYm2VfWRO9h2o7xmu7RAMtPxKaE4oemrBPyU8NG8lgqW9OmaQF5nH6eLlj JWTFatM6Zbsj4A3wZFZwx9TLKmQ8uKetY1morvP2NvZXkQBBftAJ23VRm/cc1oxipMPq +vLW4zRuZgl/6TfZc8RgVfOyYQMHKDSpaabG0=
MIME-Version: 1.0
Received: by 10.227.42.207 with SMTP id t15mr4948174wbe.98.1310974562183; Mon, 18 Jul 2011 00:36:02 -0700 (PDT)
Received: by 10.227.155.197 with HTTP; Mon, 18 Jul 2011 00:36:02 -0700 (PDT)
In-Reply-To: <4E226C22.1000307@dougbarton.us>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <4E20C1BF.3040302@dougbarton.us> <8227832E0BE58765FB9BBFC1@PST.JCK.COM> <4E226C22.1000307@dougbarton.us>
Date: Mon, 18 Jul 2011 09:36:02 +0200
Message-ID: <CAKFn1SHmTEr3Hg9-Poe1LzVwWsbzY82rcvnp9nQDLQpE0cF7DA@mail.gmail.com>
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Doug Barton <dougb@dougbarton.us>, John C Klensin <john@jck.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: Mon, 18 Jul 2011 07:36:09 -0000

On Sun, Jul 17, 2011 at 6:59 AM, Doug Barton <dougb@dougbarton.us> wrote:
> On 07/16/2011 07:02, John C Klensin wrote:
>> --On Friday, July 15, 2011 15:39 -0700 Doug Barton
>> <dougb@dougbarton.us> wrote:
<snip>
>> But, while some people have argued that 6to4 has caused so much
>> damage by being misconfigured that it should, presumably as
>> punishment or to create a public example, be eliminated entirely
>> as an option
>
> My perspective, which I've described at length many times now, is not
> that 6to4 needs to be punished, but that the widespread deployment of
> IPv6 is being harmed as a result of the negative user experience that it
> creates for the majority of its users (particularly the unintentional
> ones) and therefore the network as a whole is better off if it goes away.

That do sum it up pretty good.


<snip>
> Furthermore you have the huge problem that neither end of the 6to4
> equation has *any* motivation to fix it. The ISP side can simply block
> tunnels (or even simpler, ignore the problem). The content side can
> simply not deploy AAAA records.

My wild guess is that the ISP will sooner or later stop routing the entire
2002::/16 block...  and _yes_ that will hurt bad but it will force a hard e=
rror
on the whole 6to4 issue. It's so much better with one hard error than lots
of possible errors.



<snip>
>> But I don't recall seeing the sort of venom
>> that is directed toward 6to4 being focused on them. =A0Perhaps
>> there weren't enough complaints or you have solid data that 6to4
>> has caused even more damage.
>
> Once again repeating myself ... I have no venom towards 6to4. This isn't
> a personal attack. And yes, various people and organizations that have
> vested interests in seeing IPv6 deployed have posted the data about why
> 6to4 causes way more problems than it solves, and I believe them.

I dare to say the content providers want 6to4 gone because it _can_ be
pointed at as a risk when enabling IPv6.
And I do think the ISP see this as a quite black/white problem _if_ they
have to deal with it. Either 6to4 are on and working all the time without
them doing much, or it's gone.





And this will be my last post on the subject at all, see no point in using =
more
time on it. Lets move on :)



--=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 harald@alvestrand.no  Mon Jul 18 01:30:33 2011
Return-Path: <harald@alvestrand.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7875E21F8B86 for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 01:30: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 2J9HgTTLyyUw for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 01:30:32 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 8C42121F8B85 for <ietf@ietf.org>; Mon, 18 Jul 2011 01:30:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 648E039E123; Mon, 18 Jul 2011 10:29:25 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rhtHi1fXzEdb; Mon, 18 Jul 2011 10:29:21 +0200 (CEST)
Received: from hta-dell.lul.corp.google.com (unknown [62.20.124.50]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 6818D39E0FA; Mon, 18 Jul 2011 10:29:21 +0200 (CEST)
Message-ID: <4E23EF21.5090408@alvestrand.no>
Date: Mon, 18 Jul 2011 10:30:25 +0200
From: Harald Alvestrand <harald@alvestrand.no>
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: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Review of draft-yevstifeyev-ion-report-06
References: <4D91EBDE.5070703@gmail.com> <4E205A5D.1020304@alvestrand.no> <4E210F9B.8080305@gmail.com>
In-Reply-To: <4E210F9B.8080305@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jul 2011 08:30:33 -0000

On 07/16/11 06:12, Mykyta Yevstifeyev wrote:
> Hello Harald,
>
> As you could see in one of my previous messages, I did intend to 
> include some analysis in the draft 
> (http://www.ietf.org/mail-archive/web/ietf/current/msg67491.html).  
> However, numerous responses which discouraged me from doing this were 
> received, and including that section will create problems with consensus. 
I saw the messages. It is very hard to write an analysis on behalf of 
someone else - to my mind, the analysis of why the IESG decided what 
they did has to be based on information from the IESG; it's impossible 
for any outsider, including you and me, to divine what their thought 
processes on this matter were.

There's no IETF consensus to be documented here; the analysis and 
decision was done by the IESG, and the IESG (as it was composed at that 
time) is the body from which the information has to come. All any 
outsider (like you and me) can do is to help with the editing.
> However, I share your opinion that the document won't be full, so I 
> think the following analysis section, which is different from the 
> previous proposed one, can satisfy you and everybody else:
Now, if someone were to speak for the then-present IESG and say the same 
thing, I would make the following comments:
>
>> 3.4. Analysis
>>
>>    There were a number of reasons which forced IESG to close the IONs
>>    experiment. 
Nit: "forced IESG" -> "caused the IESG to decide". There's no forcing 
function.
>> One of them is a complexity of their approval and
>>    publication, compared with ones for IESG Statements and simple Web
>>    Pages.  As IONs were intended to represent operational experience,
>>    they might have needed to be updated quickly.  Even though these
>>    documents were meant to have a very lightweight approval procedure,
>>    it could sometimes be inappropriate for that material which was
>>    contained therein.
In a protocol, I'd ask for a definition of "quickly". Days, weeks or 
months? Examples of documents where "days" is the correct timescale?
>>
>>    Secondly, due to the nature of the scope of IONs, there was no need
>>    to allow the access to the revision history (which is unavailable in
>>    simple Web Pages as well).
I disagree with this statement, obviously. If the IESG thought so, it is 
correct to include it.
>>
>>    Thirdly, IONs on procedural question could step into the conflict
>>    with Best Current Practice (BCP) RFCs; moreover, as IONs approval
>>    procedure did not imply any formal community review, unlike BCPs,
>>    they could easily fall in the community non-acceptance.
I believe this is a red herring. However, I can fully believe that the 
argument was raised, even though I don't believe it, so if the IESG 
indeed thought that, I'm fine with having that documented.
>>
>>    Correspondingly, it was concluded that the mandate of IONs can fully
>>    be fulfilled by RFCs, when documenting IETF procedures, IESG
>>    Statements, when clearing up other issues for which RFC publication
>>    process is not appropriate, and Web Pages, when dealing with other
>>    IETF-related issues. 
Nit: "it was concluded" -> "the IESG concluded".


From harald@alvestrand.no  Mon Jul 18 05:41:41 2011
Return-Path: <harald@alvestrand.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9989221F8BC8 for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 05:41: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 pAkC37-xhagq for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 05:41:41 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id ED63121F8BBB for <ietf@ietf.org>; Mon, 18 Jul 2011 05:41:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id E868139E0FE for <ietf@ietf.org>; Mon, 18 Jul 2011 14:40:34 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bFrk8G5ySuuZ for <ietf@ietf.org>; Mon, 18 Jul 2011 14:40:31 +0200 (CEST)
Received: from hta-dell.lul.corp.google.com (unknown [62.20.124.50]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 01BCE39E0FA for <ietf@ietf.org>; Mon, 18 Jul 2011 14:40:30 +0200 (CEST)
Message-ID: <4E2429FF.9080202@alvestrand.no>
Date: Mon, 18 Jul 2011 14:41:35 +0200
From: Harald Alvestrand <harald@alvestrand.no>
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: Confidentiality notices on email messages
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com>	<29987.1310565058@marajade.sandelman.ca>	<4E1DCA13.9030301@acm.org>	<04AE56F0C4CE8168D1B38D59@PST.JCK.COM>	<p0624066dca44df0ca50f@loud.pensive.org>	<49A68144182BB270C11BC841@PST.JCK.COM>	<F5833273385BB34F99288B3648C4F06F134EBC4D4B@EXCH-C2.corp.cloudmark.com> <FDD50EB2-B783-49B3-92C2-56A21EFAEF11@guppylake.com>
In-Reply-To: <FDD50EB2-B783-49B3-92C2-56A21EFAEF11@guppylake.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: Mon, 18 Jul 2011 12:41:41 -0000

Content-disposition: noise.

On 07/16/11 09:15, Nathaniel Borenstein wrote:
> "Notice Of Intentions in Sending Email"?
>
> On Jul 16, 2011, at 1:09 AM, Murray S. Kucherawy wrote:
>
>>> -----Original Message-----
>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of John C Klensin
>>> Sent: Thursday, July 14, 2011 11:39 AM
>>> To: Randall Gellens; Marc Petit-Huguenin
>>> Cc: IETF discussion list
>>> Subject: Re: Confidentiality notices on email messages
>>>
>>> If one starts down that path, there is a real possibility for a
>>> semantically-rich environment.  For example, consider a noise
>>> type for flaming, repetitive, responses to a topic on the IETF
>>> list.  One could also very efficiently reflect what I assume was
>>> the intent of a recent observation on the list with
>>> noise-type="hitler" :-(
>> The trick though, alas, is to get people using such disclaimers to begin using such a media type.
>>
>> Maybe we need an attractive acronym for NOISE as a decoy.
>> _______________________________________________
>> 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 wjhns1@hardakers.net  Mon Jul 18 06:14:01 2011
Return-Path: <wjhns1@hardakers.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E99F221F8B8C for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 06:14:01 -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 i7pHt+-jqIxC for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 06:14:01 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.236.43]) by ietfa.amsl.com (Postfix) with ESMTP id 68D4621F8B89 for <ietf@ietf.org>; Mon, 18 Jul 2011 06:14:01 -0700 (PDT)
Received: from localhost (75-101-64-22.dsl.dynamic.omsoft.com [75.101.64.22]) by mail.hardakers.net (Postfix) with ESMTPSA id BAD2E3E; Mon, 18 Jul 2011 06:13:28 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Harald Alvestrand <harald@alvestrand.no>
Subject: Re: Confidentiality notices on email messages
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <29987.1310565058@marajade.sandelman.ca> <4E1DCA13.9030301@acm.org> <04AE56F0C4CE8168D1B38D59@PST.JCK.COM> <p0624066dca44df0ca50f@loud.pensive.org> <49A68144182BB270C11BC841@PST.JCK.COM> <F5833273385BB34F99288B3648C4F06F134EBC4D4B@EXCH-C2.corp.cloudmark.com> <FDD50EB2-B783-49B3-92C2-56A21EFAEF11@guppylake.com> <4E2429FF.9080202@alvestrand.no>
Date: Mon, 18 Jul 2011 06:13:27 -0700
In-Reply-To: <4E2429FF.9080202@alvestrand.no> (Harald Alvestrand's message of "Mon, 18 Jul 2011 14:41:35 +0200")
Message-ID: <sdmxgb91fs.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jul 2011 13:14:02 -0000

>>>>> On Mon, 18 Jul 2011 14:41:35 +0200, Harald Alvestrand <harald@alvestrand.no> said:

HA> Content-disposition: noise.

Or: Content-disposition: delete
-- 
Wes Hardaker
SPARTA, Inc.

From john@jck.com  Sat Jul 16 07:02:18 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 EB27C21F8567 for <ietf@ietfa.amsl.com>; Sat, 16 Jul 2011 07:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.632
X-Spam-Level: 
X-Spam-Status: No, score=-102.632 tagged_above=-999 required=5 tests=[AWL=-0.633, 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 e2Wz3tClBD50 for <ietf@ietfa.amsl.com>; Sat, 16 Jul 2011 07:02:18 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 9890221F856B for <ietf@ietf.org>; Sat, 16 Jul 2011 07:02:17 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Qi5Rb-0006pO-9I; Sat, 16 Jul 2011 10:02:11 -0400
Date: Sat, 16 Jul 2011 10:02:10 -0400
From: John C Klensin <john@jck.com>
To: Doug Barton <dougb@dougbarton.us>, ietf@ietf.org
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
Message-ID: <8227832E0BE58765FB9BBFC1@PST.JCK.COM>
In-Reply-To: <4E20C1BF.3040302@dougbarton.us>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <4E20C1BF.3040302@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
X-Mailman-Approved-At: Mon, 18 Jul 2011 07:25:43 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jul 2011 14:02:19 -0000

--On Friday, July 15, 2011 15:39 -0700 Doug Barton
<dougb@dougbarton.us> wrote:

> To address your concern about whether or not vendors are paying
> attention to this discussion, and why historic status is
> substantively different than "off by default, no really, OFF
> BY DEFAULT," I'll put my FreeBSD developer hat on for a minute
> and tell you that we definitely do pay attention to stuff like
> this, and whereas we already have it off by default (and have
> for some time) moving it to historic gives us the cover we
> need to remove the code at some point down the road when that's
> appropriate. That's an extremely important distinction, and
> one of the reasons that as a "member" of v6ops I ultimately
> came down in support of the 2-document strategy.

Doug,

And that is exactly where we agree on the effect and disagree
about whether it is desirable.

I think there is consensus that 6to4 is dangerous unless
carefully and intelligently configured and that is certainly
should not be turned on by default.  If anyone has argued
against that position, they are in a tiny minority.  

Similarly, I think there is consensus that following the advice
in the "advice" document makes 6to4 much safer to use, even if
not entirely risk-free (I contend that there is no "risk-free",
perhaps as a corollary to the principle that, if we invent
something idiot-proof, someone will invent a better idiot).  So
there should be no question about the desirability about
publishing the content of that document.  

The question, as far as the "advice" document is concerned, is
how to get the message out most effectively, most clearly, and
on as timely a basis as possible.  I think that having it
"update" the base 6to4 specs is important because that is how
the RFC Series is threaded.  Without that, there is an increased
risk of people finding the 6to4 specs and implementing them
without ever seeing the "advice" piece (just as, even with the
"updates"/"updated by" pointers, we still hear about new TCP
implementations based on RFC 793 alone).  For the reasons
discussed above, I don't think anyone would find that outcome
desirable.  As to whether there should be a single document or a
separate Applicability Statement that points to both the base
specifications and the "advice" document, I'm really pretty
agnostic even though I don't see many advantages in two
documents.   A separate Applicability Statement that does update
the base documents but points to the "advice" one would
accomplish much the same purpose and eliminate the requirement
that the "advice" document explicitly update the base ones.
While I think publishing a separate document just to avoid that
linkage would waste time, I'm actually pretty agnostic about
that option too.

But, while some people have argued that 6to4 has caused so much
damage by being misconfigured that it should, presumably as
punishment or to create a public example, be eliminated entirely
as an option -- for FreeBSD users, the exact effect of your
removing the code -- I haven't seen nearly as strong as case, or
anything even close to consensus, for that position.   If it was
actually what the community believed, then the "advice" document
would be a complete waste of time except possibly as a
retrospective on how 6to4 might have been better specified (a
retrospective that we would want to publish as (immediately)
Historic).

If the thing is still useful, even in limited circumstances and
used correctly, then the IETF should not provide you with
"cover" to remove the code because it is not in the best
interest of the community for you to remove the code.   Might
both your removing the code and moving 6to4 to Historic in the
future be appropriate?  Sure.  I also look forward to the day
when we can move IPv4 to Historic (just as the various
specifications that make up NCP should have been moved years ago
if we paid attention to that sort of housekeeping).

Summary: we should not move something to Historic that is still
in use, useful, and that can be used correctly.  We explain how
to use it or the circumstances under which is should or should
not be used, narrowing those descriptions as much as needed.
And/or we explain all of the situations in which it should not
be used.  Simply reclassifying it as Historic is problematic to
the use cases that actually do work and doesn't provide nearly
enough information as what people should actually do, especially
people who already have the protocol deployed in some form.
Using Historic, rather than, e.g., NOT RECOMMENDED [any more] as
a sort of super-deprecation mechanism depends too much on our
assumption that people with working deployments will simply
ignore us.  While the assumption is right, it puts the whole
situation into one in which the IETF is publicly operating on
the assumption that its advice won't be followed.   If we do
that very often, we might as well just go home.

FWIW, I note that there are at least a few other things that
shipped for years with FreeBSD that could cause a lot of damage
if misconfigured and were hard to configure correctly, but were
nonetheless included in the code in version after version and
even were enabled by default.  Getting rid of them would not
have required any IETF action -- there were other
implementations of the same protocols that could have been
included in the base systems instead.  But they weren't removed
or replaced (the folks who produced them eventually produced
better versions).  But I don't recall seeing the sort of venom
that is directed toward 6to4 being focused on them.  Perhaps
there weren't enough complaints or you have solid data that 6to4
has caused even more damage.

   best,
     john


From rsk@gsp.org  Mon Jul 18 05:42:38 2011
Return-Path: <rsk@gsp.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 2672221F8BE6 for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 05:42:38 -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 6dbe6YYT9-on for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 05:42:34 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) by ietfa.amsl.com (Postfix) with ESMTP id D4FD321F8BB6 for <ietf@ietf.org>; Mon, 18 Jul 2011 05:42:33 -0700 (PDT)
Received: from squonk.gsp.org (bltmd-207.114.17.237.dsl.charm.net [207.114.17.237]) by taos.firemountain.net (8.14.5/8.14.5) with ESMTP id p6ICgVcq028152 for <ietf@ietf.org>; Mon, 18 Jul 2011 08:42:32 -0400 (EDT)
Received: from vorlon.gsp.org (vorlon.gsp.org [192.168.0.20]) by squonk.gsp.org (8.14.3/8.14.3) with ESMTP id p6IClpI7024907 for <ietf@ietf.org>; Mon, 18 Jul 2011 08:47:51 -0400 (EDT)
Received: from localhost6.localdomain6 (localhost.localdomain [127.0.0.1]) by vorlon.gsp.org (8.14.3/8.14.3/Debian-9.2ubuntu1) with ESMTP id p6ICgO7i029362 for <ietf@ietf.org>; Mon, 18 Jul 2011 08:42:24 -0400
Received: (from rsk@localhost) by localhost6.localdomain6 (8.14.3/8.14.3/Submit) id p6ICgNRa029361 for ietf@ietf.org; Mon, 18 Jul 2011 08:42:23 -0400
Date: Mon, 18 Jul 2011 08:42:23 -0400
From: Richard Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: Confidentiality notices on email messages
Message-ID: <20110718124222.GA29309@gsp.org>
References: <1D49B15C-643F-4D05-92BE-E42A309341CF@cybernothing.org> <20110714014544.9252.qmail@joyce.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110714014544.9252.qmail@joyce.lan>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Mailman-Approved-At: Mon, 18 Jul 2011 07:25:43 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jul 2011 12:42:38 -0000

On Thu, Jul 14, 2011 at 01:45:44AM -0000, John Levine wrote:
> It's clueless cargo cult lawyering.  

+1, and see also:

	http://www.river.com/users/share/etiquette/#legalistic

which reads in part:

	"First, such boilerplate contains useless adhesions, meaning
	the explicit and implied threats they make are particularly
	annoying. If you send something via email, the recipients (are
	you sure you aren't sending to a mailing list?) and anyone else
	who sees your clear text postcard in transit can undetectably and
	with full deniability do whatever they want with the information
	written on it in plain view. Even casual users of email know
	email is not a secure communications medium. Thus the threats in
	typical bogus legalistic boilerplate are naught but an attempt
	at highly improper intimidation. Demands made in this manner
	will be regarded as evidence of a hostile attitude on your
	part by a significant portion of recipients. The threats will
	negatively affect how your recipients perceive the other ideas
	in your message.

	Second, in the case of mailing lists (are you sure the address
	to which you sent isn't one?) or USENET posts, falsely claiming
	a message is "confidential and privileged" is simply too stupid
	for words."


---rsk

From moore@network-heretics.com  Mon Jul 18 07:32:36 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 500A821F8BE9 for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 07:32:36 -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.060, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 7PDlxrKo6+wO for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 07:32:32 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id F396A21F8BD9 for <ietf@ietf.org>; Mon, 18 Jul 2011 07:32:31 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id 8BF1420637; Mon, 18 Jul 2011 10:32:31 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute5.internal (MEProxy); Mon, 18 Jul 2011 10:32: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:message-id:references:to; s=smtpout; bh=C3q5cnS/lr8x8uSz/Z1tEyg9t/E=; b=kMwJxk/MWl06NUFvZOOxBid9c9gD3ObKQJLBrWQxgqZdlIDihS4AhOCRfiBXU4gErBUPmPfeFmRiZfn2Aj26c6nMD1ILz8P+WcyA7VgWVzF4GUcsbMj3eTCaTaGIrL6d+hzEB6i1q7nzRxEU6Q4R1fJ4zU+5TxwjZ9CFU0y4eI4=
X-Sasl-enc: 5s4DMWcNOjUQyLFV3RexWsM8zOxwMb/5+92eafiyRR1Q 1310999550
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 CD5BD442C97; Mon, 18 Jul 2011 10:32:29 -0400 (EDT)
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-4--167617117
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <CAKFn1SHmTEr3Hg9-Poe1LzVwWsbzY82rcvnp9nQDLQpE0cF7DA@mail.gmail.com>
Date: Mon, 18 Jul 2011 10:32:28 -0400
Message-Id: <5C36E42D-6177-49A0-B0F9-6AB128E2D4DD@network-heretics.com>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <4E20C1BF.3040302@dougbarton.us> <8227832E0BE58765FB9BBFC1@PST.JCK.COM> <4E226C22.1000307@dougbarton.us> <CAKFn1SHmTEr3Hg9-Poe1LzVwWsbzY82rcvnp9nQDLQpE0cF7DA@mail.gmail.com>
To: =?iso-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: John C Klensin <john@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: Mon, 18 Jul 2011 14:32:36 -0000

--Apple-Mail-4--167617117
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

On Jul 18, 2011, at 3:36 AM, Roger J=F8rgensen wrote:

> My wild guess is that the ISP will sooner or later stop routing the =
entire
> 2002::/16 block...  and _yes_ that will hurt bad but it will force a =
hard error
> on the whole 6to4 issue. It's so much better with one hard error than =
lots
> of possible errors.

Actually, no.  It will cause a significant increase in the number of =
service calls that will last for years.  And those will be the fault of =
the ISPs blocking the traffic.

It must be re-iterated that the vast majority of problems associated =
with 6to4 appear to be caused by operators, not by 6to4 itself.  6to4 =
does have some real problems, and some of us are looking for ways to fix =
them.   But that's no excuse for operators to deliberately make things =
worse.

> I dare to say the content providers want 6to4 gone because it _can_ be
> pointed at as a risk when enabling IPv6.
> And I do think the ISP see this as a quite black/white problem _if_ =
they
> have to deal with it. Either 6to4 are on and working all the time =
without
> them doing much, or it's gone.

Part of the problem seems to be that operators want a quick solution =
that is under their control, when it appears that no such solution can =
exist.

- Changes to the default address selection rules, already implemented or =
being implemented, should help significantly, but it will take some time =
for hosts to get updated to reflect those changes.  (Asking Microsoft, =
Apple, and Linux vendors to include those changes in incremental updates =
- if they haven't already done so - might help speed that process =
along.)
- The changes in -advisory will help somewhat, but it will take time for =
operators and vendors to learn about them and implement them, and the =
effect will be gradual.
- The changes in -experimental will also help somewhat, if those changes =
are published in some form, but the effect will also be gradual.
- Improvements to the 6to4 protocol (especially where relay routers are =
concerned) might help, but again will require updates to hosts and/or =
routers.   (it's conceivable that fixes could be implemented in hosts =
that don't require the routers to be upgrade in order for those changes =
to be helpful)
- As I said yesterday, there are ways that content providers can use =
IPv6 to distribute content to their customers over HTTP, as well as =
monitor the percentage of their users that are IPv6 capable, though =
they're a tad trickier than simply adding AAAA records to the DNS and =
turning on v6 in their servers.

All of the above can help.   However,

- Yelling "6to4 is Evil" as loudly as possible, e.g. declaring it =
Historic and publishing -historic,
- Filtering protocol 41 packets,
- Blocking 2002::/16 traffic or routing advertisements, or
- Blocking 192.88.99.0/24 traffic or routing advertisements,=20

will all make the situation worse for users, operators, and content =
providers.=20

Keith


--Apple-Mail-4--167617117
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jul 18, 2011, at 3:36 AM, Roger J=F8rgensen =
wrote:</div><br><blockquote type=3D"cite"><div>My wild guess is that the =
ISP will sooner or later stop routing the entire<br>2002::/16 block... =
&nbsp;and _yes_ that will hurt bad but it will force a hard error<br>on =
the whole 6to4 issue. It's so much better with one hard error than =
lots<br>of possible =
errors.<br></div></blockquote><div><br></div>Actually, no. &nbsp;It will =
cause a significant increase in the number of service calls that will =
last for years. &nbsp;And those will be the fault of the ISPs blocking =
the traffic.</div><div><br></div><div>It must be re-iterated that the =
vast majority of problems associated with 6to4 appear to be caused by =
operators, not by 6to4 itself. &nbsp;6to4 does have some real problems, =
and some of us are looking for ways to fix them. &nbsp; But that's no =
excuse for operators to deliberately make things =
worse.</div><div><br></div><div><blockquote type=3D"cite"><div>I dare to =
say the content providers want 6to4 gone because it _can_ be<br>pointed =
at as a risk when enabling IPv6.<br>And I do think the ISP see this as a =
quite black/white problem _if_ they<br>have to deal with it. Either 6to4 =
are on and working all the time without<br>them doing much, or it's =
gone.<br></div></blockquote></div><br><div>Part of the problem seems to =
be that operators want a <i>quick</i> solution that is <i>under their =
control</i>, when it appears that no such solution can =
exist.</div><div><br></div><div>- Changes to the default address =
selection rules, already implemented or being implemented, should help =
significantly, but it will take some time for hosts to get updated to =
reflect those changes. &nbsp;(Asking Microsoft, Apple, and Linux vendors =
to include those changes in incremental updates - if they haven't =
already done so - might help speed that process along.)</div><div>- The =
changes in -advisory will help somewhat, but it will take time for =
operators and vendors to learn about them and implement them, and the =
effect will be gradual.</div><div>- The changes in -experimental will =
also help somewhat, if those changes are published in some form, but the =
effect will also be gradual.</div><div>- Improvements to the 6to4 =
protocol (especially where relay routers are concerned) might help, but =
again will require updates to hosts and/or routers. &nbsp; (it's =
conceivable that fixes could be implemented in hosts that don't require =
the routers to be upgrade in order for those changes to be =
helpful)</div><div>- As I said yesterday, there are ways that content =
providers can use IPv6 to distribute content to their customers over =
HTTP, as well as monitor the percentage of their users that are IPv6 =
capable, though they're a tad trickier than simply adding AAAA records =
to the DNS and turning on v6 in their =
servers.</div><div><br></div><div>All of the above can help. =
&nbsp;&nbsp;However,</div><div><br></div><div>- Yelling "6to4 is Evil" =
as loudly as possible, e.g. declaring it Historic and publishing =
-historic,</div><div>- Filtering protocol 41 packets,</div><div>- =
Blocking 2002::/16 traffic or routing advertisements, or</div><div>- =
Blocking 192.88.99.0/24 traffic or routing =
advertisements,&nbsp;</div><div><br></div><div>will all make the =
situation worse for users, operators, and content =
providers.&nbsp;</div><div><br></div><div>Keith</div><div><br></div></body=
></html>=

--Apple-Mail-4--167617117--

From petithug@acm.org  Mon Jul 18 08:13:36 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 2311821F8B8C for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 08:13:36 -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.008, 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 I0UQXDVQdLTT for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 08:13:31 -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 22B6421F8B88 for <ietf@ietf.org>; Mon, 18 Jul 2011 08:13:30 -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 CCBE42199E for <ietf@ietf.org>; Mon, 18 Jul 2011 17:11:42 +0200 (CEST)
Message-ID: <4E244D98.9010209@acm.org>
Date: Mon, 18 Jul 2011 08:13:28 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110626 Iceowl/1.0b2 Icedove/3.1.11
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Meeting Materials for IETF 81
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: Mon, 18 Jul 2011 15:13:36 -0000

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

Why, one week before the beginning of the IETF meeting, is the "Meeting
Materials" link not enabled on the web site?

There was a discussion on this very mailing-list few months ago ("what is the
problem bis") that discussed about the productivity of WG sessions.  I do
believe that having the slides for the presentations posted ahead of time helps
participants to understand the problem and focus on questions and discussion
during the f2f, which makes for a better use of our time.  Obviously not
everybody agree with me, as it is common to see presentations uploaded few
minutes before the presentation and even in at least one case, few hours after!

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

iEYEARECAAYFAk4kTZYACgkQ9RoMZyVa61eGuACfZvEdmU+FcADkAcJ3TTOZF+xK
KjMAnRRcQw1cmTMyixr2PFPDqbfw0+aB
=J3+E
-----END PGP SIGNATURE-----

From paul.hoffman@vpnc.org  Mon Jul 18 08:19:12 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 3529D21F8C33 for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 08:19:12 -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 DJEX35i5mr-j for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 08:19: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 7214921F8BB7 for <ietf@ietf.org>; Mon, 18 Jul 2011 08:19:11 -0700 (PDT)
Received: from [10.20.30.101] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p6IFIvIL067331 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Mon, 18 Jul 2011 08:18:58 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Meeting Materials for IETF 81
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4E244D98.9010209@acm.org>
Date: Mon, 18 Jul 2011 08:19:09 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <48D8FFAF-3F39-4A51-9F03-7726D0548D54@vpnc.org>
References: <4E244D98.9010209@acm.org>
To: IETF-Discussion list <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: Mon, 18 Jul 2011 15:19:12 -0000

In the meantime: <https://datatracker.ietf.org/meeting/81/materials.html>


From amorris@amsl.com  Mon Jul 18 08:30:05 2011
Return-Path: <amorris@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D23B821F8C6E for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 08:30:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.104
X-Spam-Level: 
X-Spam-Status: No, score=-4.104 tagged_above=-999 required=5 tests=[AWL=-1.504, 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 uBv4V0fMqaMI for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 08:30:02 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:1112:1::14]) by ietfa.amsl.com (Postfix) with ESMTP id E88AA21F8C6D for <ietf@ietf.org>; Mon, 18 Jul 2011 08:30:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id E29271C381E8 for <ietf@ietf.org>; Mon, 18 Jul 2011 08:30:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ampccmHpZkVB for <ietf@ietf.org>; Mon, 18 Jul 2011 08:30:01 -0700 (PDT)
Received: from [192.168.0.194] (c-76-102-55-37.hsd1.ca.comcast.net [76.102.55.37]) by c1a.amsl.com (Postfix) with ESMTPSA id B02A31C381EA for <ietf@ietf.org>; Mon, 18 Jul 2011 08:30:01 -0700 (PDT)
Message-Id: <71C91B01-C209-4CA8-9D0D-B489240EF18F@amsl.com>
From: Alexa Morris <amorris@amsl.com>
To: IETF-Discussion list <ietf@ietf.org>
In-Reply-To: <4E244D98.9010209@acm.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: Meeting Materials for IETF 81
Date: Mon, 18 Jul 2011 08:30:01 -0700
References: <4E244D98.9010209@acm.org>
X-Mailer: Apple Mail (2.936)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jul 2011 15:30:05 -0000

The link is now live.

Alexa

On Jul 18, 2011, at 8:13 AM, Marc Petit-Huguenin wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Why, one week before the beginning of the IETF meeting, is the  
> "Meeting
> Materials" link not enabled on the web site?
>
> There was a discussion on this very mailing-list few months ago  
> ("what is the
> problem bis") that discussed about the productivity of WG sessions.   
> I do
> believe that having the slides for the presentations posted ahead of  
> time helps
> participants to understand the problem and focus on questions and  
> discussion
> during the f2f, which makes for a better use of our time.  Obviously  
> not
> everybody agree with me, as it is common to see presentations  
> uploaded few
> minutes before the presentation and even in at least one case, few  
> hours after!
>
> - --
> 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)
>
> iEYEARECAAYFAk4kTZYACgkQ9RoMZyVa61eGuACfZvEdmU+FcADkAcJ3TTOZF+xK
> KjMAnRRcQw1cmTMyixr2PFPDqbfw0+aB
> =J3+E
> -----END PGP SIGNATURE-----
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

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

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


From jnc@mercury.lcs.mit.edu  Mon Jul 18 08:33: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 E965921F8C66; Mon, 18 Jul 2011 08:33:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.511
X-Spam-Level: 
X-Spam-Status: No, score=-6.511 tagged_above=-999 required=5 tests=[AWL=0.088,  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 P11+R79K22pF; Mon, 18 Jul 2011 08:33:39 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 5882321F8B91; Mon, 18 Jul 2011 08:33:39 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id C849F18C08C; Mon, 18 Jul 2011 11:33:37 -0400 (EDT)
To: ietf@ietf.org
Subject: RE: Another look at 6to4 (and other IPv6 transition issues)
Message-Id: <20110718153337.C849F18C08C@mercury.lcs.mit.edu>
Date: Mon, 18 Jul 2011 11:33:37 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: v6ops@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: Mon, 18 Jul 2011 15:33:40 -0000

    > From: Ronald Bonica <rbonica@juniper.net>

    > RFC 2026's very terse definition of HISTORIC. According to RFC 2026,
    > "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." That's the entire definition.
    > Anything more is read into it.
    > ...
    > A more likely interpretation is as follows:
    > "the IETF is not likely to invest effort in the technology in the
    > 	future"
    > "the IETF does not encourage (or discourage) new deployments of this
    > 	technology.

But in giving other interpretations, are you thereby not comitting the
exact error you call out above: "Anything more is read into it."?

To me, "Historic" has always (including pre-2026) meant just what the
orginal meaning of the word is (caveat - see below) - something that is
now likely only of interest to people who are looking into the history of
networking. (The dictionary definition is "Based on or concerned with
events in history".) I think "obsolete" is probably the best one-word
description (and note that 'obsolete' != 'obsolescent').

(Caveat: technically, it probably should have been 'historical', not
"historic" - "historic" actually means 'in the past, but very noteworthy',
e.g.  'CYCLADES was a historic networking design', so not every historical
protocol is historic.)

	Noel

From jhw@apple.com  Mon Jul 18 12:30:52 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 D641011E8070 for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 12:30:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.69
X-Spam-Level: 
X-Spam-Status: No, score=-106.69 tagged_above=-999 required=5 tests=[AWL=-0.091, 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 GcwzwsCME3Bl for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 12:30:52 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id 315DC228011 for <ietf@ietf.org>; Mon, 18 Jul 2011 12:30:52 -0700 (PDT)
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Received: from relay12.apple.com ([17.128.113.53]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LOJ008M9NIUP841@mail-out.apple.com> for ietf@ietf.org; Mon, 18 Jul 2011 12:30:42 -0700 (PDT)
X-AuditID: 11807135-b7b76ae000001169-5e-4e248a770d61
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 relay12.apple.com (Apple SCV relay) with SMTP id 56.06.04457.77A842E4; Mon, 18 Jul 2011 12:33:11 -0700 (PDT)
Received: from kallisti.apple.com (kallisti.apple.com [17.193.13.64]) by cardamom.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LOJ00AR7NJ54GA0@cardamom.apple.com> for ietf@ietf.org; Mon, 18 Jul 2011 12:30:41 -0700 (PDT)
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
From: james woodyatt <jhw@apple.com>
In-reply-to: <CAKFn1SHmTEr3Hg9-Poe1LzVwWsbzY82rcvnp9nQDLQpE0cF7DA@mail.gmail.com>
Date: Mon, 18 Jul 2011 12:30:00 -0700
Content-transfer-encoding: quoted-printable
Message-id: <170C0171-41D1-4246-B838-2DCF78277D69@apple.com>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <4E20C1BF.3040302@dougbarton.us> <8227832E0BE58765FB9BBFC1@PST.JCK.COM> <4E226C22.1000307@dougbarton.us> <CAKFn1SHmTEr3Hg9-Poe1LzVwWsbzY82rcvnp9nQDLQpE0cF7DA@mail.gmail.com>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1244.3)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprNLMWRmVeSWpSXmKPExsUiON1OVbe8S8XP4G2fnsWzjfNZHBg9liz5 yRTAGMVlk5Kak1mWWqRvl8CV8fDgNdaCxawVb9ffZm5gnMjSxcjJISFgIrFjxTRmCFtM4sK9 9WxdjFwcQgKtTBKz7zazgyR4BQQlfky+B9bALKAj0fv9G1iDkMAKJolzNx1AbGEBF4mJvyHi bAIqEt8u32UCsTkFgiWm3DwNNodFQFXiwKr/rBBztCWevLvACjHfRuLc1PesEIufMUqs/9HC CJIQEVCWeDT1PBvEdfISi1s+M05g5J+F5KZZSG6ahWTuAkbmVYyCRak5iZWGRnqJBQU5qXrJ +bmbGEFB1lBouoPx0UL1Q4wCHIxKPLyCosp+QqyJZcWVuYcYJTiYlUR4lxup+AnxpiRWVqUW 5ccXleakFh9ilOZgURLnLbkn7ickkJ5YkpqdmlqQWgSTZeLglGpgND4nLMB+/G2SitS06jkn VAUCJ/BahdYKe4jLFHNXXvWZclMlO6vsXeSE2CRjp1dFjdE3FhTo27UU7/0b/n1ycE/V3Veq gpylC0w3P2sP8/0zSdWT+6fY8xl+jBWWsyObvp1emLPlwZFVad6MkifjaxWmF2cc3b1xZ/iS HUd8Nn/KPVHxcu4MJZbijERDLeai4kQA+cMlFC4CAAA=
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jul 2011 19:30:53 -0000

On Jul 18, 2011, at 24:36 , Roger J=F8rgensen wrote:
>=20
> My wild guess is that the ISP will sooner or later stop routing the =
entire 2002::/16 block...

You mean, your wild guess is service providers will unilaterally =
implement the phase-out plan I proposed as a standards action.

Why not just sign up for a standard phase-out plan?  Don't we want 6to4 =
users to have any advanced notice that we plan to break their Internet?  =
Or, is the idea that we don't believe we can achieve a tactical victory =
over 6to4 users unless we mount a surprise attack on them?


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From moore@network-heretics.com  Mon Jul 18 12:57: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 9002621F87BD for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 12:57:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.505
X-Spam-Level: 
X-Spam-Status: No, score=-3.505 tagged_above=-999 required=5 tests=[AWL=0.093,  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 Eou0vTRka13G for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 12:57:21 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id A716321F87BC for <ietf@ietf.org>; Mon, 18 Jul 2011 12:57:21 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id 90E4F202D8; Mon, 18 Jul 2011 15:57:19 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute5.internal (MEProxy); Mon, 18 Jul 2011 15:57: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:message-id:references:to; s=smtpout; bh=YtWaKURcA+FSil5erTHTju+o6ug=; b=OJ5m/m1zLGJY0RzQoaJ05reCxmDJAwG4hxJ51V2embhkgzbFwOawpwEiTW+1uK/+NJnucgZ+FEEZP00rs+A6fB2JrYRBVyof7zE0uUFikAH+kPY2A8YjY8buJzvP2iwv3U+qnaMgXDPFJPXGQOqhRaivNhdTLA6ULgjv4awcucc=
X-Sasl-enc: 8C/ub5DWqSTye9mXTusrGqA63vYcI67KZBMszp75a47y 1311019038
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 947B6448130; Mon, 18 Jul 2011 15:57:18 -0400 (EDT)
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-31--148127526
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <170C0171-41D1-4246-B838-2DCF78277D69@apple.com>
Date: Mon, 18 Jul 2011 15:57:17 -0400
Message-Id: <5F7BD2DA-A164-4583-A9CD-A822A373F4F8@network-heretics.com>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <4E20C1BF.3040302@dougbarton.us> <8227832E0BE58765FB9BBFC1@PST.JCK.COM> <4E226C22.1000307@dougbarton.us> <CAKFn1SHmTEr3Hg9-Poe1LzVwWsbzY82rcvnp9nQDLQpE0cF7DA@mail.gmail.com> <170C0171-41D1-4246-B838-2DCF78277D69@apple.com>
To: james woodyatt <jhw@apple.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: Mon, 18 Jul 2011 19:57:22 -0000

--Apple-Mail-31--148127526
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

On Jul 18, 2011, at 3:30 PM, james woodyatt wrote:

> On Jul 18, 2011, at 24:36 , Roger J=F8rgensen wrote:
>>=20
>> My wild guess is that the ISP will sooner or later stop routing the =
entire 2002::/16 block...
>=20
> You mean, your wild guess is service providers will unilaterally =
implement the phase-out plan I proposed as a standards action.
>=20
> Why not just sign up for a standard phase-out plan?  Don't we want =
6to4 users to have any advanced notice that we plan to break their =
Internet?  Or, is the idea that we don't believe we can achieve a =
tactical victory over 6to4 users unless we mount a surprise attack on =
them?

I don't understand the desire for a phase out plan when there's nothing =
better to phase in that's generally available.   =20

Preferring IPv4 to 6to4 makes sense.     But filtering 6to4 traffic or =
its routing advertisements is a denial-of-service attack.

Keith


--Apple-Mail-31--148127526
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jul 18, 2011, at 3:30 PM, james woodyatt wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>On =
Jul 18, 2011, at 24:36 , Roger J=F8rgensen wrote:<br><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">My wild guess =
is that the ISP will sooner or later stop routing the entire 2002::/16 =
block...<br></blockquote><br>You mean, your wild guess is service =
providers will unilaterally implement the phase-out plan I proposed as a =
standards action.<br><br>Why not just sign up for a standard phase-out =
plan? &nbsp;Don't we want 6to4 users to have any advanced notice that we =
plan to break their Internet? &nbsp;Or, is the idea that we don't =
believe we can achieve a tactical victory over 6to4 users unless we =
mount a surprise attack on them?<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 =
don't understand the desire for a phase out plan when there's nothing =
better to phase in that's generally available. &nbsp; =
&nbsp;</div><div><br></div><div>Preferring IPv4 to 6to4 makes sense. =
&nbsp; &nbsp; But filtering 6to4 traffic or its routing advertisements =
is a denial-of-service =
attack.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-31--148127526--

From rbonica@juniper.net  Mon Jul 18 13:21:34 2011
Return-Path: <rbonica@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7ECF21F85E2; Mon, 18 Jul 2011 13:21:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.538
X-Spam-Level: 
X-Spam-Status: No, score=-106.538 tagged_above=-999 required=5 tests=[AWL=0.060, 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 UEXqVz+mv7Xh; Mon, 18 Jul 2011 13:21:33 -0700 (PDT)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id 1360721F85DB; Mon, 18 Jul 2011 13:21:32 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP ID DSNKTiSVyySGmUz1tBhVssk6ei6AodyqLn7i@postini.com; Mon, 18 Jul 2011 13:21:33 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.2.254.0; Mon, 18 Jul 2011 13:20:59 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Mon, 18 Jul 2011 16:20:58 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 18 Jul 2011 16:20:57 -0400
Subject: RE: Another look at 6to4 (and other IPv6 transition issues)
Thread-Topic: Another look at 6to4 (and other IPv6 transition issues)
Thread-Index: AcxFYBJdjQlIlq+EQTO5NLN5FfVsZgAKAEPA
Message-ID: <13205C286662DE4387D9AF3AC30EF456D3F3F4A5F7@EMBX01-WF.jnpr.net>
References: <20110718153337.C849F18C08C@mercury.lcs.mit.edu>
In-Reply-To: <20110718153337.C849F18C08C@mercury.lcs.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
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: Mon, 18 Jul 2011 20:21:34 -0000

Noel,

Given that each of us reads something different into the definition of HIST=
ORIC, is there any hope that this thread will ever converge?

                                                                  Ron


> -----Original Message-----
> From: Noel Chiappa [mailto:jnc@mercury.lcs.mit.edu]
> Sent: Monday, July 18, 2011 11:34 AM
> To: ietf@ietf.org
> Cc: jnc@mercury.lcs.mit.edu; v6ops@ietf.org
> Subject: RE: Another look at 6to4 (and other IPv6 transition issues)
>=20
>     > From: Ronald Bonica <rbonica@juniper.net>
>=20
>     > RFC 2026's very terse definition of HISTORIC. According to RFC
> 2026,
>     > "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." That's the entire definition.
>     > Anything more is read into it.
>     > ...
>     > A more likely interpretation is as follows:
>     > "the IETF is not likely to invest effort in the technology in the
>     > 	future"
>     > "the IETF does not encourage (or discourage) new deployments of
> this
>     > 	technology.
>=20
> But in giving other interpretations, are you thereby not comitting the
> exact error you call out above: "Anything more is read into it."?
>=20
> To me, "Historic" has always (including pre-2026) meant just what the
> orginal meaning of the word is (caveat - see below) - something that is
> now likely only of interest to people who are looking into the history
> of
> networking. (The dictionary definition is "Based on or concerned with
> events in history".) I think "obsolete" is probably the best one-word
> description (and note that 'obsolete' !=3D 'obsolescent').
>=20
> (Caveat: technically, it probably should have been 'historical', not
> "historic" - "historic" actually means 'in the past, but very
> noteworthy',
> e.g.  'CYCLADES was a historic networking design', so not every
> historical
> protocol is historic.)
>=20
> 	Noel

From brian.e.carpenter@gmail.com  Mon Jul 18 16:42:32 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 1241321F8788; Mon, 18 Jul 2011 16:42:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.616
X-Spam-Level: 
X-Spam-Status: No, score=-103.616 tagged_above=-999 required=5 tests=[AWL=-0.017, 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 0RU61tLxi4u5; Mon, 18 Jul 2011 16:42:31 -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 10C0321F8762; Mon, 18 Jul 2011 16:42:30 -0700 (PDT)
Received: by vws12 with SMTP id 12so3462484vws.31 for <multiple recipients>; Mon, 18 Jul 2011 16:42:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=L54OR94jEXM3DUj1En8efj/XBFlApJZE3Jj/iuCSmHs=; b=TyxwcuyeDL56ofu3QFVGjE100mpqcaJoII0BhCTuVrtxoCMqBqim3v3hl1SBFTa0zo yNGiSljF3Siy070f7uC2syWHIOjFynjXQlhImk58BTRfRGAfmiQpCmhCMml6cO1aFLnO 0h1ZHfLvpYryw/BGW1imx0JftJnCaG/s2VSn0=
Received: by 10.52.176.74 with SMTP id cg10mr1275355vdc.242.1311032550565; Mon, 18 Jul 2011 16:42:30 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id y4sm2007156vdv.37.2011.07.18.16.42.27 (version=SSLv3 cipher=OTHER); Mon, 18 Jul 2011 16:42:29 -0700 (PDT)
Message-ID: <4E24C4E1.8050406@gmail.com>
Date: Tue, 19 Jul 2011 11:42:25 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Erik Kline <ek@google.com>
Subject: Re: [v6ops] Another look at 6to4 (and other IPv6 transition issues)
References: <20110718153337.C849F18C08C@mercury.lcs.mit.edu>	<13205C286662DE4387D9AF3AC30EF456D3F3F4A5F7@EMBX01-WF.jnpr.net> <CAAedzxo2U6W-LBUfbe0wby=Kgr57Hcsth_cLzxbTviY_hTAZ8Q@mail.gmail.com>
In-Reply-To: <CAAedzxo2U6W-LBUfbe0wby=Kgr57Hcsth_cLzxbTviY_hTAZ8Q@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, 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: Mon, 18 Jul 2011 23:42:32 -0000

On 2011-07-19 11:26, Erik Kline wrote:
>> Given that each of us reads something different into the definition of HISTORIC, is there any hope that this thread will ever converge?
> 
> I don't see any "progress".
> 
> We may just have to blacklist any resolvers that have 6to4 clients
> behind them and leave it at that.

Why? How would that help anybody?

What would help is following the steps in the -advisory document.

(Discussing how many angels can dance on the head of an RFC certainly
won't help either. Could we all stop now please?)

   Brian

From daedulus@btconnect.com  Tue Jul 19 01:25: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 E104121F89C2 for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 01:25: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 jpyTU+1pzSza for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 01:25:21 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr09.btconnect.com [213.123.26.187]) by ietfa.amsl.com (Postfix) with ESMTP id E8EB221F89C1 for <ietf@ietf.org>; Tue, 19 Jul 2011 01:25:20 -0700 (PDT)
Received: from host217-44-4-189.range217-44.btcentralplus.com (HELO pc6) ([217.44.4.189]) by c2beaomr09.btconnect.com with SMTP id DRX02787; Tue, 19 Jul 2011 09:24:50 +0100 (BST)
Message-ID: <004b01cc45e4$8be36f60$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Ronald Bonica" <rbonica@juniper.net>, "Noel Chiappa" <jnc@mercury.lcs.mit.edu>, <ietf@ietf.org>
References: <20110718153337.C849F18C08C@mercury.lcs.mit.edu> <13205C286662DE4387D9AF3AC30EF456D3F3F4A5F7@EMBX01-WF.jnpr.net>
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
Date: Tue, 19 Jul 2011 09:21:51 +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.4E253F51.00F6, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.7.19.73614:17:7.586, ip=217.44.4.189, 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, 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=c2beaomr09.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0203.4E253F53.00EB,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: Tue, 19 Jul 2011 08:25:22 -0000

----- Original Message -----
From: "Ronald Bonica" <rbonica@juniper.net>
To: "Noel Chiappa" <jnc@mercury.lcs.mit.edu>; <ietf@ietf.org>
Cc: <v6ops@ietf.org>
Sent: Monday, July 18, 2011 10:20 PM
> Noel,
>
> Given that each of us reads something different into the definition of
HISTORIC, is there any hope that this thread will ever converge?
>

No.

What is needed is some lateral thinking, such as the proposal that instead of
trying to shoehorn an RFC into an inappropriate, closed set of maturity levels,
we use a completely different option, namely an Appplicability Statement that
spells out that this magnificent standards track, non-historic piece of
technology now has an extremely limited applicability, and unless you really
know what you are doing, forget it.

Tom Petch.




>                                                                   Ron
>
>
> > -----Original Message-----
> > From: Noel Chiappa [mailto:jnc@mercury.lcs.mit.edu]
> > Sent: Monday, July 18, 2011 11:34 AM
> > To: ietf@ietf.org
> > Cc: jnc@mercury.lcs.mit.edu; v6ops@ietf.org
> > Subject: RE: Another look at 6to4 (and other IPv6 transition issues)
> >
> >     > From: Ronald Bonica <rbonica@juniper.net>
> >
> >     > RFC 2026's very terse definition of HISTORIC. According to RFC
> > 2026,
> >     > "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." That's the entire definition.
> >     > Anything more is read into it.
> >     > ...
> >     > A more likely interpretation is as follows:
> >     > "the IETF is not likely to invest effort in the technology in the
> >     > future"
> >     > "the IETF does not encourage (or discourage) new deployments of
> > this
> >     > technology.
> >
> > But in giving other interpretations, are you thereby not comitting the
> > exact error you call out above: "Anything more is read into it."?
> >
> > To me, "Historic" has always (including pre-2026) meant just what the
> > orginal meaning of the word is (caveat - see below) - something that is
> > now likely only of interest to people who are looking into the history
> > of
> > networking. (The dictionary definition is "Based on or concerned with
> > events in history".) I think "obsolete" is probably the best one-word
> > description (and note that 'obsolete' != 'obsolescent').
> >
> > (Caveat: technically, it probably should have been 'historical', not
> > "historic" - "historic" actually means 'in the past, but very
> > noteworthy',
> > e.g.  'CYCLADES was a historic networking design', so not every
> > historical
> > protocol is historic.)
> >
> > Noel
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From moore@network-heretics.com  Tue Jul 19 05:30: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 B6DDD21F8786 for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 05:30:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.206
X-Spam-Level: 
X-Spam-Status: No, score=-3.206 tagged_above=-999 required=5 tests=[AWL=-0.207, BAYES_00=-2.599, 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 3epI+opzwzNG for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 05:30:55 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 1DAD921F84F7 for <ietf@ietf.org>; Tue, 19 Jul 2011 05:30:55 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id 5F88A20C05; Tue, 19 Jul 2011 08:30:54 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute5.internal (MEProxy); Tue, 19 Jul 2011 08:30: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=YJiH3MX6xQfBwXT8vrDV7i6Wv7w=; b=dsH7ayMTSbqYY/3JZxjzIeH9KjCHeFY4KQyFfMaomQw6gSJKRacM5pqVCh84myQBaKymxIaFyqPmQEMQyrwDc2hpV8+ebCsquO5LwHzxN9CgeYQTbrZx/41uLtDCJZOyzzh/A+b2ARrwVqpIPX5k96kq7qAn1Hm+qgtOyUdLfNo=
X-Sasl-enc: FYm3a/qrV/osk/9h3OYQ9Cf5gvXW04uHMEvBSMbOWh/u 1311078653
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 65AAA44E9C1; Tue, 19 Jul 2011 08:30:52 -0400 (EDT)
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
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: <004b01cc45e4$8be36f60$4001a8c0@gateway.2wire.net>
Date: Tue, 19 Jul 2011 08:29:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4E4FFDA4-8752-4037-BC4C-D12D072F3C0F@network-heretics.com>
References: <20110718153337.C849F18C08C@mercury.lcs.mit.edu> <13205C286662DE4387D9AF3AC30EF456D3F3F4A5F7@EMBX01-WF.jnpr.net> <004b01cc45e4$8be36f60$4001a8c0@gateway.2wire.net>
To: t.petch <daedulus@btconnect.com>
X-Mailer: Apple Mail (2.1084)
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jul 2011 12:30:55 -0000

On Jul 19, 2011, at 3:21 AM, t.petch wrote:

> What is needed is some lateral thinking, such as the proposal that =
instead of
> trying to shoehorn an RFC into an inappropriate, closed set of =
maturity levels,
> we use a completely different option, namely an Appplicability =
Statement that
> spells out that this magnificent standards track, non-historic piece =
of
> technology now has an extremely limited applicability, and unless you =
really
> know what you are doing, forget it.

An Applicability Statement was my first suggestion for how to address =
the problem, and it's still acceptable to me.

Keith


From dave@cridland.net  Tue Jul 19 06:26:54 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 8C0DE21F84E1; Tue, 19 Jul 2011 06:26:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.412
X-Spam-Level: 
X-Spam-Status: No, score=-2.412 tagged_above=-999 required=5 tests=[AWL=-0.113, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SeRUR6ACFNlg; Tue, 19 Jul 2011 06:26:50 -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 EE38921F86D1; Tue, 19 Jul 2011 06:26:49 -0700 (PDT)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id 73A8E1168087; Tue, 19 Jul 2011 14:26:48 +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 MdZBQGoRYsD0; Tue, 19 Jul 2011 14:26:41 +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 A05FC1168067; Tue, 19 Jul 2011 14:26:41 +0100 (BST)
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com>
In-Reply-To: <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com>
MIME-Version: 1.0
Message-Id: <9031.1311082001.631622@puncture>
Date: Tue, 19 Jul 2011 14:26:41 +0100
From: Dave Cridland <dave@cridland.net>
To: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
Content-Type: text/plain; delsp="yes"; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: 8Bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jul 2011 13:26:54 -0000

On Tue Jul 19 12:51:16 2011, Iñaki Baz Castillo wrote:
> 2011/7/11 The IESG <iesg-secretary@ietf.org>:
> > The IESG has received a request from the BiDirectional or
> > Server-Initiated HTTP WG (hybi) to consider the following  
> document:
> > - 'The WebSocket protocol'
> >  <draft-ietf-hybi-thewebsocketprotocol-10.txt> as a Proposed  
> Standard
> 
> Hi, I assume there is no interest in making DNS SRV mechanism  
> exposed
> in http://tools.ietf.org/html/draft-ibc-websocket-dns-srv-02 part of
> the WebSocket core specification, neither referencing it (in the  
> same
> way RFC 3261 "SIP protocol" mandates the usage of RFC 3263 "Locating
> SIP servers").
> 
> As said before, making such DNS SRV specification an extension (so
> present in other document) will mean no success at all, as WebSocket
> client implementors (i.e. webbrowser vendors) will not be mandated  
> to
> implement it and service providers could not rely on the support of
> DNS SRV in web browsers. So nobody will use them (because IE10  
> decided
> not to implement it, for example). IMHO this is sad due the real
> advantages DNS SRV provides for a protocol like WebSocket.
> 
> Yes, in HTTP there is no special DNS stuff, all the load-balancing  
> and
> failover mechanism are done at server side with very complex and
> expensive solutions (www.facebook.com resolves to a single IPv4  
> !!!!).
> The question is: should we also inherit every HTTP limitation in
> WebSocket?

I agree wholeheartedly with this, and strongly recommend that  
mandatory use of SRV is included in the core protocol.

I think with HTTP's very short lived requests, then it's possible to  
work around the lack of SRV support (at a cost), but the benefit is  
markedly higher with the long-lived, stateful sessions we're  
anticipating with WebSocket.

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 ned+ietf@mauve.mrochek.com  Tue Jul 19 08:20:02 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 EB48B21F8A70 for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 08:20: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 LS87M3VB1bpz for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 08:20:02 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 3FF4321F8A71 for <ietf@ietf.org>; Tue, 19 Jul 2011 08:20:02 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O3TP8GHFZ400QSW4@mauve.mrochek.com> for ietf@ietf.org; Tue, 19 Jul 2011 08:19:15 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O3R1W8PRSW00RCTX@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 19 Jul 2011 08:19:10 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01O3TP8DZQF000RCTX@mauve.mrochek.com>
Date: Tue, 19 Jul 2011 08:16:17 -0700 (PDT)
Subject: Re: Confidentiality notices on email messages
In-reply-to: "Your message dated Mon, 18 Jul 2011 14:41:35 +0200" <4E2429FF.9080202@alvestrand.no>
MIME-version: 1.0
Content-type: TEXT/PLAIN; Format=flowed
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <29987.1310565058@marajade.sandelman.ca> <4E1DCA13.9030301@acm.org> <04AE56F0C4CE8168D1B38D59@PST.JCK.COM> <p0624066dca44df0ca50f@loud.pensive.org> <49A68144182BB270C11BC841@PST.JCK.COM> <F5833273385BB34F99288B3648C4F06F134EBC4D4B@EXCH-C2.corp.cloudmark.com> <FDD50EB2-B783-49B3-92C2-56A21EFAEF11@guppylake.com> <4E2429FF.9080202@alvestrand.no>
To: Harald Alvestrand <harald@alvestrand.no>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1311088738; i=@mrochek.com; bh=do5WjkYBTeWlTW5FbCxVyA8/xQJRdD1TT7G0kj+i0HY=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=ArD/OXlFQQO6QbOr5vZvhtIz0uWhZwoNOhAUI0z9hoSUyViVhfSnM9QIADEVF4Ab3 sl98WWCCYayyOb+YpRBM4RYOWQjO/m0NZuuaWHWQa7q5BQvEyJwCTgYQFl1TvGqAp9 uD6y6AnGhGzrodrtdLSWtQcBen7obqM9hAW09DVA=
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jul 2011 15:20:03 -0000

> Content-disposition: noise.

Harald, I was about to say the same thing but you beat me to it. Unless we're
prepared to talk about defining a general format for such notices (and I'm
pretty sure we're not interested in doing that), this doesn't fit as a media
type - I can easily envision using various different types depending on the
sort of notice I want to send.

But a content-disposition value has the right semantics and makes all sorts
of sense.

				Ned

From ek@google.com  Mon Jul 18 16:26:31 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 95D6921F8572 for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 16:26:31 -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 dTqYfeeyvV7q for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2011 16:26:31 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by ietfa.amsl.com (Postfix) with ESMTP id 215B521F8573 for <ietf@ietf.org>; Mon, 18 Jul 2011 16:26:31 -0700 (PDT)
Received: from hpaq14.eem.corp.google.com (hpaq14.eem.corp.google.com [172.25.149.14]) by smtp-out.google.com with ESMTP id p6INQUZF025620 for <ietf@ietf.org>; Mon, 18 Jul 2011 16:26:30 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1311031590; bh=8m+q+Pd5z4UBfDx80H9jBv8pGT0=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=ttNIrNC0HIzKycHTqU+bYPnAO/EnEhXFbPyDMlQYdZcj7faA2c0ScNuYsrCUqKzXO T2CXEAcCHB5moWj388VmA==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:date: message-id:subject:from:to:cc:content-type:x-system-of-record; b=Ye+RdZ9CgayVJI0VADPK03UfoOevajFIlGn9tyR/EdSyYeUbRm44HQ4/skISR/OVB am4JKSfK+lzxRkEKrWj5g==
Received: from pzk32 (pzk32.prod.google.com [10.243.19.160]) by hpaq14.eem.corp.google.com with ESMTP id p6INQRm1003222 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Mon, 18 Jul 2011 16:26:28 -0700
Received: by pzk32 with SMTP id 32so6348961pzk.7 for <ietf@ietf.org>; Mon, 18 Jul 2011 16:26:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wWxTjQR5HtnXHW8wCrxWrGxA/FSgyrlNiA87R2S4IO0=; b=Mvq/ChsxTOIwdJSB3h8Eq0SDy3ci5XnmA+H6GLmOKao8pozOF30EwoGhk13VC0JJiX Ug9DqYAhFCMwcDW2PLuQ==
MIME-Version: 1.0
Received: by 10.142.213.5 with SMTP id l5mr3454655wfg.153.1311031587014; Mon, 18 Jul 2011 16:26:27 -0700 (PDT)
Received: by 10.142.216.21 with HTTP; Mon, 18 Jul 2011 16:26:26 -0700 (PDT)
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F3F4A5F7@EMBX01-WF.jnpr.net>
References: <20110718153337.C849F18C08C@mercury.lcs.mit.edu> <13205C286662DE4387D9AF3AC30EF456D3F3F4A5F7@EMBX01-WF.jnpr.net>
Date: Tue, 19 Jul 2011 08:26:26 +0900
Message-ID: <CAAedzxo2U6W-LBUfbe0wby=Kgr57Hcsth_cLzxbTviY_hTAZ8Q@mail.gmail.com>
Subject: Re: [v6ops] Another look at 6to4 (and other IPv6 transition issues)
From: Erik Kline <ek@google.com>
To: Ronald Bonica <rbonica@juniper.net>
Content-Type: text/plain; charset=UTF-8
X-System-Of-Record: true
X-Mailman-Approved-At: Tue, 19 Jul 2011 08:37:46 -0700
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, 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: Mon, 18 Jul 2011 23:26:31 -0000

> Given that each of us reads something different into the definition of HISTORIC, is there any hope that this thread will ever converge?

I don't see any "progress".

We may just have to blacklist any resolvers that have 6to4 clients
behind them and leave it at that.

From wwwrun@ietfa.amsl.com  Mon Jul 18 20:15:50 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 342F721F8772; Mon, 18 Jul 2011 20:15:50 -0700 (PDT)
From: NomCom Chair <nomcom-chair@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: Nomcom 2011-2012: Results of Random Selection 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110719031550.342F721F8772@ietfa.amsl.com>
Date: Mon, 18 Jul 2011 20:15:50 -0700 (PDT)
X-Mailman-Approved-At: Tue, 19 Jul 2011 08:37:45 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jul 2011 03:15:50 -0000

Hi all,

The following is the list of 10 Nomcom volunteers selected randomly
from this list: https://datatracker.ietf.org/ann/nomcom/2991/

118. Lianshu Zheng, Huawei Technologies;
 35. Stephen Hanna, Juniper Networks;
100. Simo Veikkolainen, Nokia;
 44. Sheng Jiang, Huawei Technologies Co. Ltd.;
 84. Rifaat Shekh-Yusef, Avaya;
 92. Pascal Thubert, Cisco;
  1. Jaap Akkerhuis, NLnet labs;
 99. Olivier Vautrin, Juniper Networks;
108. IJsbrand Wijnands, Cisco;
 58. Dapeng Liu, China Mobile;

Congratulations to everyone who got selected as a voting member.
This begins the one week community review of the selection - please
let me know ASAP if you see any problems with the selections. The
challenge period will close at 23:59 EDT on Monday July 25, 2011.

I am in the process of contacting the individuals to confirm they are
still able to serve on the Nomcom.

Once again, I would like to thank everyone who volunteered for the
Nomcom and I hope you will continue volunteering in the years to come.

Suresh Krishnan
Nomcom Chair 2011-2012
Email: nomcom-chair@ietf.org, suresh.krishnan@ericsson.com

NOTE: 76. Allyn Romanow, Cisco Systems was picked as 10th selection
but had to be skipped due to the "two members per affiliation"
restriction specified in Section 4 Rule 17 of RFC3777.


Selection Details 
=================

Seed Values:
The seed values used in selecting the committee members are follows:

Canadian Lottery Lotto 649
Saturday July 16, 2011 Results:
  http://diffusion.loto-quebec.com/sw3/res/asp/index.asp?l=1&pRequest=2&cProduit=4
  (7 numbers including the bonus number: numbers between 1 and 49)
Value: 02 12 23 35 39 49 44

US National debt ("Debt Held by the Public"), published by the
Treasury department as of Friday, July 15, 2011
  http://www.treasurydirect.gov/NP/BPDLogin?application=np 
  Last 8 digits, ignore the commas and periods
Value: 43838132

US National debt ("Intragovernmental Holdings"), published by the
Treasury department as of Friday, July 15, 2011
  http://www.treasurydirect.gov/NP/BPDLogin?application=np 
  Last 8 digits, ignore the commas and periods
Value: 43531153

Euromillions Lottery
Friday July 15, 2011 Results:
  http://www.europeanlotteryguild.com/lottery_results/euromillions_results/draw_history?results_date=2011-08-01
  (7 numbers including the star balls: 5 numbers between 1 and 50 and 2 star balls between 1 and 11)
Value: 06 26 33 34 39 03 04

With the selection algorithm results are based on RFC 3797 as follows:

[suresh@beeblebrox nomcom11]$./nomcom
Type size of pool:
(or 'exit' to exit) Type number of items to be selected:
(or 'exit' to exit) Approximately 62.1 bits of entropy needed.

Type #1 randomness or 'end' followed by new line.
Up to 16 integers or the word 'float' followed by up
to 16 x.y format reals.
2 12 23 35 39 44 49
Type #2 randomness or 'end' followed by new line.
Up to 16 integers or the word 'float' followed by up
to 16 x.y format reals.
43838132
Type #3 randomness or 'end' followed by new line.
Up to 16 integers or the word 'float' followed by up
to 16 x.y format reals.
43531153
Type #4 randomness or 'end' followed by new line.
Up to 16 integers or the word 'float' followed by up
to 16 x.y format reals.
3 4 6 26 33 34 39
Type #5 randomness or 'end' followed by new line.
Up to 16 integers or the word 'float' followed by up
to 16 x.y format reals.
Key is:
 2.12.23.35.39.44.49./43838132./43531153./3.4.6.26.33.34.39./
index        hex value of MD5        div  selected
 1  0DC9765D111926682972CDB0BE0D2F75  120  -> 118 <-
 2  D6A71A7BA3B379743C7C2E86ED793FB4  119  -> 35 <-
 3  FD440C774ED64A735F817DDB414D69FE  118  -> 100 <-
 4  90DAB0968FC05AA4A3E854F88BE2CBF2  117  -> 44 <-
 5  7CFDC92829037007F178BEA0FB2838C5  116  -> 84 <-
 6  FF1B0A4C427822E41CFD7AA072F87483  115  -> 92 <-
 7  0A2F3DD7A862AD8B7A99323DF747FB36  114  ->  1 <-
 8  8F74E1BF0926172EE4907EDA97E8083A  113  -> 99 <-
 9  50A198675A31BB4225AC3358265C1464  112  -> 108 <-
10  834B1152DF1E7FA6EA7C4C2C3B6AB625  111  -> 76 <-
11  19CF15ADFA7B364A20D498F64A5E1236  110  -> 58 <-
12  A23A41557BC2447A183BFBC32D8EEE92  109  -> 104 <-
13  700AA85DC4CAA77FC303B08E58B2F506  108  -> 54 <-
14  166E56A9AB07A49C4EC77EEBA9F6DE06  107  -> 97 <-
15  9F2F1498FD73BF4FA6C54382E217B5D6  106  -> 90 <-

Done, type any character to exit.
[suresh@beeblebrox nomcom11]$


From kathleen.moriarty@emc.com  Mon Jul 18 21:12:15 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 8A79F21F86E1; Mon, 18 Jul 2011 21:12:15 -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 8cUTgvYvaRhv; Mon, 18 Jul 2011 21:12:15 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id C0A1721F8541; Mon, 18 Jul 2011 21:12:14 -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 p6J4C9YJ022647 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Jul 2011 00:12:09 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Tue, 19 Jul 2011 00:11:58 -0400
Received: from mxhub21.corp.emc.com (mxhub21.corp.emc.com [128.221.56.107]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p6J4BuJ9020274; Tue, 19 Jul 2011 00:11:57 -0400
Received: from mx06a.corp.emc.com ([169.254.1.199]) by mxhub21.corp.emc.com ([128.221.56.107]) with mapi; Tue, 19 Jul 2011 00:11:56 -0400
From: <kathleen.moriarty@emc.com>
To: <draft-ietf-decade-survey.all@tools.ietf.org>, <gen-art@ietf.org>, <ietf@ietf.org>
Date: Tue, 19 Jul 2011 00:11:54 -0400
Subject: Gen-ART review of draft-ietf-decade-survey-04
Thread-Topic: Gen-ART review of draft-ietf-decade-survey-04
Thread-Index: AcxFyf4uQybmHskbTgmnC4Yl9Rt77A==
Message-ID: <AE31510960917D478171C79369B660FA0E052F70A5@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: Tue, 19 Jul 2011 08:37:46 -0700
Cc: ralimi@google.com, Akbar.Rahman@InterDigital.com, yry@cs.yale.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jul 2011 04:12:15 -0000

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/GenArtfaq>.

Please wait for direction from your document shepherd or AD before posting =
a new version of the draft.

Document: draft-ietf-decade-survey-04
Reviewer: Kathleen Moriarty
Review Date: July 18, 2011
IETF LC End Date: July 20, 2011
IESG Telechat date: (if known)

Summary: The document is well written and is ready with the nits listed bel=
ow.

Major issues: None

Minor issues: None

Nits/editorial comments:
Introduction, consider changing from:
"High-capacity and low-cost in-network storage devices introduces
   substantial opportunities."
To: "High-capacity and low-cost in-network storage devices introduce
   substantial opportunities."

Section 2.2 paragraph 3, consider changing the dash in the last sentence to=
 a comma.
From: "In particular, the use of audio and
   video streaming formats has become common for delivery of rich
   information to the public - both residential and business."
To: "In particular, the use of audio and
   video streaming formats has become common for delivery of rich
   information to the public, both residential and business."

Section 2.2: define CDN in the sentence before it is defined where it is fi=
rst used in paragraph 4:
From: "In these edge technologies,
   CDN is a representative technique.  Content Delivery Networks (CDN)
   are based on a large-scale distributed network of servers located
   closer to the edges of the Internet for efficient delivery of digital
   content including various forms of multimedia content."
To: "In these edge technologies,
   Content Delivery Networks (CDN) is a representative technique.  CDNs
   are based on a large-scale distributed network of servers located
   closer to the edges of the Internet for efficient delivery of digital
   content including various forms of multimedia content."

Section 4.2, last paragraph considering changing
From: "Cached content is encrypted, and clients can only decrypt the data
   using keys derived from metadata returned by the content server."
To: "Cached content is encrypted such that only clients can decrypt the dat=
a
   using keys derived from metadata returned by the content server."

Section 4.3.7: Consider removing the first comma as it is not needed since =
only two ideas are connected (not a list).
From: "A query including a location-independent content ID is sent to the
   network, and routed to a Cache-and-forward router, which handles
   retrieval of the data and forwarding to the end host."
To: "A query including a location-independent content ID is sent to the
   network and routed to a Cache-and-forward router, which handles
   retrieval of the data and forwarding to the end host."

Section 4.4: CDN is already defined in the document, at this point you can =
use either the full description or acronym, but do not need to redefine it.
"A Content Delivery Network (CDN) provides services that improve
   network performance by maximizing bandwidth, improving accessibility
   and maintaining correctness through content replication."

Section 4.4.5: Recommend just using one transition at the start of the sent=
ence.
From: "Also as mentioned previously, clients typically cannot write to the
   CDN."
To: "As mentioned previously, clients typically cannot write to the
   CDN."

Section 4.4.7: Add an 's' on last word of sentence:
From: "Clients can locate CDN nodes through DNS or other redirection
   mechanism."
To: "Clients can locate CDN nodes through DNS or other redirection
   mechanisms."

Section 4.10: Consider removing comma (unnecessary):
From: "P2P caches operate similarly to web caches, in that they temporarily
   store frequently-requested content."
To: "P2P caches operate similarly to web caches in that they temporarily
   store frequently-requested content."

Section 4.11.2.6: It is unnecessary to redefine "Deep Packet Inspection (DP=
I)" as it is defined in an earlier section.







From pch-b2B3A6689@u-1.phicoh.com  Tue Jul 19 00:28:22 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 7213521F86DB; Tue, 19 Jul 2011 00:28:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.524
X-Spam-Level: 
X-Spam-Status: No, score=-4.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T4zAPBJ43KIZ; Tue, 19 Jul 2011 00:28:22 -0700 (PDT)
Received: from stereo.hq.phicoh.net (unknown [IPv6:2002:8225:f03:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id 76C7E21F85F2; Tue, 19 Jul 2011 00:28:20 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #66) id m1Qj4j1-0001iTC; Tue, 19 Jul 2011 09:28:15 +0200
Message-Id: <m1Qj4j1-0001iTC@stereo.hq.phicoh.net>
To: Erik Kline <ek@google.com>
Subject: Re: [v6ops] Another look at 6to4 (and other IPv6 transition issues) 
From: Philip Homburg <pch-v6ops@u-1.phicoh.com>
Sender: pch-b2B3A6689@u-1.phicoh.com
References: <20110718153337.C849F18C08C@mercury.lcs.mit.edu> <13205C286662DE4387D9AF3AC30EF456D3F3F4A5F7@EMBX01-WF.jnpr.net> <CAAedzxo2U6W-LBUfbe0wby=Kgr57Hcsth_cLzxbTviY_hTAZ8Q@mail.gmail.com>
In-reply-to: Your message of "Tue, 19 Jul 2011 08:26:26 +0900 ." <CAAedzxo2U6W-LBUfbe0wby=Kgr57Hcsth_cLzxbTviY_hTAZ8Q@mail.gmail.com> 
Date: Tue, 19 Jul 2011 09:28:12 +0200
X-Mailman-Approved-At: Tue, 19 Jul 2011 08:37:46 -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, 19 Jul 2011 07:28:22 -0000

In your letter dated Tue, 19 Jul 2011 08:26:26 +0900 you wrote:
>> Given that each of us reads something different into the definition of HISTO
>RIC, is there any hope that this thread will ever converge?
>
>I don't see any "progress".
>
>We may just have to blacklist any resolvers that have 6to4 clients
>behind them and leave it at that.

I don't think there is any need to be overly dramatic about it.

I firmly belive that 6to4 should be moved to historic. But at the same time,
I was looking for a poorly performing IPv6 connection to test happy eyeballs
and didn't find it. 6to4 can just work.

So a less aggressive approach might be in order.

(If you look at the numbers, there are fewer and fewer 6to4 connections to
dual-stack sites because modern operating system releases will prefer IPv4
over 6to4. Of the users who didn't upgrade, there is about 20% with a
completely broken 6to4 setup. What remains is slightly higher latency due to
non-optimal placement of relays)



From ibc@aliax.net  Tue Jul 19 04:51:18 2011
Return-Path: <ibc@aliax.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0654321F852C; Tue, 19 Jul 2011 04:51:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.667
X-Spam-Level: 
X-Spam-Status: No, score=-2.667 tagged_above=-999 required=5 tests=[AWL=0.010,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 YE25rGLggnlr; Tue, 19 Jul 2011 04:51:17 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id 35D4F21F8512; Tue, 19 Jul 2011 04:51:16 -0700 (PDT)
Received: by qyk29 with SMTP id 29so3066487qyk.10 for <multiple recipients>; Tue, 19 Jul 2011 04:51:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.179.193 with SMTP id br1mr6519477qab.222.1311076276487; Tue, 19 Jul 2011 04:51:16 -0700 (PDT)
Received: by 10.229.185.195 with HTTP; Tue, 19 Jul 2011 04:51:16 -0700 (PDT)
In-Reply-To: <20110711140229.17432.23519.idtracker@ietfa.amsl.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com>
Date: Tue, 19 Jul 2011 13:51:16 +0200
Message-ID: <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: ietf@ietf.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 19 Jul 2011 08:37:45 -0700
Cc: hybi@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jul 2011 11:51:18 -0000

2011/7/11 The IESG <iesg-secretary@ietf.org>:
> The IESG has received a request from the BiDirectional or
> Server-Initiated HTTP WG (hybi) to consider the following document:
> - 'The WebSocket protocol'
> =C2=A0<draft-ietf-hybi-thewebsocketprotocol-10.txt> as a Proposed Standar=
d

Hi, I assume there is no interest in making DNS SRV mechanism exposed
in http://tools.ietf.org/html/draft-ibc-websocket-dns-srv-02 part of
the WebSocket core specification, neither referencing it (in the same
way RFC 3261 "SIP protocol" mandates the usage of RFC 3263 "Locating
SIP servers").

As said before, making such DNS SRV specification an extension (so
present in other document) will mean no success at all, as WebSocket
client implementors (i.e. webbrowser vendors) will not be mandated to
implement it and service providers could not rely on the support of
DNS SRV in web browsers. So nobody will use them (because IE10 decided
not to implement it, for example). IMHO this is sad due the real
advantages DNS SRV provides for a protocol like WebSocket.

Yes, in HTTP there is no special DNS stuff, all the load-balancing and
failover mechanism are done at server side with very complex and
expensive solutions (www.facebook.com resolves to a single IPv4 !!!!).
The question is: should we also inherit every HTTP limitation in
WebSocket?

Thanks.


--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From francis@aspl.es  Tue Jul 19 05:51:42 2011
Return-Path: <francis@aspl.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AD1421F8797; Tue, 19 Jul 2011 05:51:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.149
X-Spam-Level: **
X-Spam-Status: No, score=2.149 tagged_above=-999 required=5 tests=[AWL=-0.435,  BAYES_00=-2.599, FH_HOST_ALMOST_IP=1.889, HOST_EQ_STATIC=1.172,  HOST_EQ_STATICIP=1.511, HOST_MISMATCH_NET=0.311, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XS8QPa7zrCTb; Tue, 19 Jul 2011 05:51:38 -0700 (PDT)
Received: from mail.aspl.es (196.Red-212-170-101.staticIP.rima-tde.net [212.170.101.196]) by ietfa.amsl.com (Postfix) with ESMTP id CA69021F858E; Tue, 19 Jul 2011 05:51:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.aspl.es (Postfix) with ESMTP id BFC541170002; Tue, 19 Jul 2011 14:51:31 +0200 (CEST)
X-Virus-Scanned: amavisd-new at aspl.es
Received: from mail.aspl.es ([127.0.0.1]) by localhost (dolphin.aspl.es [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oORB7JRK8WEU; Tue, 19 Jul 2011 14:51:31 +0200 (CEST)
Received: from [192.168.0.132] (barracuda [10.0.0.4]) by mail.aspl.es (Postfix) with ESMTP id 130FB1170001; Tue, 19 Jul 2011 14:51:31 +0200 (CEST)
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: Francis Brosnan Blazquez <francis@aspl.es>
To: =?ISO-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>
In-Reply-To: <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-15"
Organization: ASPL
Date: Tue, 19 Jul 2011 14:51:32 +0200
Message-ID: <1311079892.23681.475.camel@vulcan.aspl.local>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Tue, 19 Jul 2011 08:37:45 -0700
Cc: hybi@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, 19 Jul 2011 12:51:42 -0000

> As said before, making such DNS SRV specification an extension (so
> present in other document) will mean no success at all, as WebSocket
> client implementors (i.e. webbrowser vendors) will not be mandated to
> implement it and service providers could not rely on the support of
> DNS SRV in web browsers. So nobody will use them (because IE10 decided
> not to implement it, for example). IMHO this is sad due the real
> advantages DNS SRV provides for a protocol like WebSocket.
> 
> Yes, in HTTP there is no special DNS stuff, all the load-balancing and
> failover mechanism are done at server side with very complex and
> expensive solutions (www.facebook.com resolves to a single IPv4 !!!!).
> The question is: should we also inherit every HTTP limitation in
> WebSocket?

+1

It is little the effort for web browser implementors and will provide
lot of benefits to end users and developers which would be able to
provide scalable/configurable services easily. I'm with Iñaki: its usage
must be mandatory to really make it available in all browsers...



From mcr@sandelman.ca  Tue Jul 19 10:00:35 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 8101021F858D for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 10:00:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.824
X-Spam-Level: 
X-Spam-Status: No, score=-0.824 tagged_above=-999 required=5 tests=[AWL=-0.359, BAYES_05=-1.11, 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 gVWYl-f1fRw1 for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 10:00:31 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id E6A9021F8581 for <ietf@ietf.org>; Tue, 19 Jul 2011 10:00:30 -0700 (PDT)
Received: from marajade.sandelman.ca (unknown [132.213.238.4]) by relay.sandelman.ca (Postfix) with ESMTPS id 0AC7B34064; Tue, 19 Jul 2011 13:00:14 -0400 (EDT)
Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 96F6A980EA; Tue, 19 Jul 2011 13:00:39 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Erik Kline <ek@google.com>
Subject: Re: [v6ops] Another look at 6to4 (and other IPv6 transition issues)
In-Reply-To: <CAAedzxo2U6W-LBUfbe0wby=Kgr57Hcsth_cLzxbTviY_hTAZ8Q@mail.gmail.com>
References: <20110718153337.C849F18C08C@mercury.lcs.mit.edu> <13205C286662DE4387D9AF3AC30EF456D3F3F4A5F7@EMBX01-WF.jnpr.net> <CAAedzxo2U6W-LBUfbe0wby=Kgr57Hcsth_cLzxbTviY_hTAZ8Q@mail.gmail.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Tue, 19 Jul 2011 13:00:39 -0400
Message-ID: <804.1311094839@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
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, 19 Jul 2011 17:00:35 -0000

>>>>> "Erik" == Erik Kline <ek@google.com> writes:
    >> Given that each of us reads something different into the
    >> definition of HISTORIC, is there any hope that this thread will
    >> ever converge?

    Erik> I don't see any "progress".

    Erik> We may just have to blacklist any resolvers that have 6to4
    Erik> clients behind them and leave it at that.

I don't see how this can scale or possibly work well given 
that I'm allowed to cache DNS info on my mobile device.

I really wish Google had tried putting a 6to4 relay in your network.

-- 
]       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 mail@sabahattin-gucukoglu.com  Tue Jul 19 14:01:52 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 A4F3D21F8B0D for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 14:01:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.19
X-Spam-Level: 
X-Spam-Status: No, score=0.19 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_EQ_IP_ADDR=1.119, RCVD_IN_PBL=0.905]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2QDtIaPBsy9q for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 14:01:52 -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 A799821F8506 for <ietf@ietf.org>; Tue, 19 Jul 2011 14:01:51 -0700 (PDT)
Received: from Mintaka.sabahattin-gucukoglu.com ([::ffff:127.0.0.1]:40981) by Mintaka.sabahattin-gucukoglu.com with [XMail 1.27 ESMTP Server] id <S3861A> for <ietf@ietf.org> from <mail@sabahattin-gucukoglu.com>; Tue, 19 Jul 2011 22:01:50 +0100
Received: from [172.20.10.2] (178.240.24.22) (using SMTP over TLS) by Mintaka.sabahattin-gucukoglu.com (tmda-ofmipd) with ESMTP; Tue, 19 Jul 2011 22:01:47 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
In-Reply-To: <C2C73F7968F19FEEF11B2C67@[192.168.1.128]>
Date: Wed, 20 Jul 2011 00:01:42 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <E85A5A32-3665-4932-96A7-BADB11DDB2E8@sabahattin-gucukoglu.com>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <BBB3AB81-1A20-4022-8687-CD88B000B281@bogus.com> <A6908373951C6911489DF57A@PST.JCK.COM> <71D5A97D-7119-4082-BC87-6505370CE800@bogus.com> <13205C286662DE4387D9AF3AC30EF456D3F3DEEA84@EMBX01-WF.jnpr.net> <C2C73F7968F19FEEF11B2C67@[192.168.1.128]>
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-1313701310.575d90@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: Tue, 19 Jul 2011 21:01:52 -0000

On 17 Jul 2011, at 01:52, John C Klensin wrote:
> --On Saturday, July 16, 2011 16:03 -0400 Ronald Bonica
> <rbonica@juniper.net> wrote:
> A more likely interpretation is as follows:
>=20
>> "the IETF is not likely to invest effort in the technology in
>> the future" "the IETF does not encourage (or discourage) new
>> deployments of this technology.
>=20
> Noting in passing that these sorts of statements are quite close
> to the uses 2026 prescribes for Applicability Statements (and
> for which we have even more precedent and oral tradition), if
> the first of those is an adequate reason for identifying
> something as historic, I recommend that we immediately move RFC
> 791 to Historic.  Certainly we are likely to invest more effort
> in the development of the technology.  Now, some people would
> read such a move as either an indication, as you suggest above,
> that the IETF thought no one was using it any more, or that
> there were no remaining valid use cases, etc., immediately
> turning us into a laughingstock.  But, by logic that suggests
> moving 6to4 to Historic on the grounds that the IETF is not
> going to invest effort in the technology.

Quite so.  And with that, you've just ruined the best April 1 gag the =
IETF could have hoped for, you. :-)

I stopped to consider, and do again, what exactly would prevent us from =
taking such a radical course of action.  Clearly, the view that making =
something historic when it's in active use is offensive.  No standards =
body could seek to stand behind their specifications, or to give the =
impression of doing so, with such a position.  On the other hand, as =
you've shown, case-by-case analysis is a good thing for document action =
on historic (or any other status), and there are a body of cases where =
the merits of documents have not shown to be sufficient for the IETF to =
consider it worthwhile improving.  I wasn't about in the early days of =
the IETF so I don't know anything about these oral traditions you speak =
of, except to say that this is a case to be made for the force of the =
written word.

BTW, I am among those not exactly thrilled about the idea of moving of =
6to4 to historic.

Cheers,
Sabahattin

From dougb@dougbarton.us  Tue Jul 19 14:34:42 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 C3B6A11E808B for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 14:34:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.802
X-Spam-Level: 
X-Spam-Status: No, score=-2.802 tagged_above=-999 required=5 tests=[AWL=-0.692, BAYES_05=-1.11, 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 oXRHtLbcPBgT for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 14:34:38 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 7A19511E8087 for <ietf@ietf.org>; Tue, 19 Jul 2011 14:34:38 -0700 (PDT)
Received: (qmail 16055 invoked by uid 399); 19 Jul 2011 21:34: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; 19 Jul 2011 21:34:33 -0000
X-Originating-IP: 65.241.43.4
X-Sender: dougb@dougbarton.us
Message-ID: <4E25F868.1000109@dougbarton.us>
Date: Tue, 19 Jul 2011 14:34:32 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110706 Thunderbird/5.0
MIME-Version: 1.0
To: Sabahattin Gucukoglu <mail-dated-1313701310.575d90@sabahattin-gucukoglu.com>
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <BBB3AB81-1A20-4022-8687-CD88B000B281@bogus.com> <A6908373951C6911489DF57A@PST.JCK.COM> <71D5A97D-7119-4082-BC87-6505370CE800@bogus.com> <13205C286662DE4387D9AF3AC30EF456D3F3DEEA84@EMBX01-WF.jnpr.net> <C2C73F7968F19FEEF11B2C67@[192.168.1.128]> <E85A5A32-3665-4932-96A7-BADB11DDB2E8@sabahattin-gucukoglu.com>
In-Reply-To: <E85A5A32-3665-4932-96A7-BADB11DDB2E8@sabahattin-gucukoglu.com>
X-Enigmail-Version: 1.2pre
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jul 2011 21:34:42 -0000

On 07/19/2011 14:01, Sabahattin Gucukoglu wrote:
> Clearly, the view that making something historic when it's in active use is offensive.  No standards body could seek to stand behind their specifications, or to give the impression of doing so, with such a position.

Define "active use."


-- 

	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 mail@sabahattin-gucukoglu.com  Tue Jul 19 15:23:37 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 44E6F11E8098 for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 15:23:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.19
X-Spam-Level: 
X-Spam-Status: No, score=0.19 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_EQ_IP_ADDR=1.119, RCVD_IN_PBL=0.905]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GuP5gx2saTbT for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 15:23:36 -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 5874B11E8092 for <ietf@ietf.org>; Tue, 19 Jul 2011 15:23:36 -0700 (PDT)
Received: from Mintaka.sabahattin-gucukoglu.com ([::ffff:127.0.0.1]:35498) by Mintaka.sabahattin-gucukoglu.com with [XMail 1.27 ESMTP Server] id <S38636> for <ietf@ietf.org> from <mail@sabahattin-gucukoglu.com>; Tue, 19 Jul 2011 23:23:34 +0100
Received: from [172.20.10.2] (178.240.24.22) (using SMTP over TLS) by Mintaka.sabahattin-gucukoglu.com (tmda-ofmipd) with ESMTP; Tue, 19 Jul 2011 23:23:31 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: [v6ops] Another look at 6to4 (and other IPv6 transition issues)
In-Reply-To: <CAAedzxo2U6W-LBUfbe0wby=Kgr57Hcsth_cLzxbTviY_hTAZ8Q@mail.gmail.com>
Date: Wed, 20 Jul 2011 01:23:28 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <03E49CA0-8B60-493A-ADE2-E510CC7F5148@sabahattin-gucukoglu.com>
References: <20110718153337.C849F18C08C@mercury.lcs.mit.edu> <13205C286662DE4387D9AF3AC30EF456D3F3F4A5F7@EMBX01-WF.jnpr.net> <CAAedzxo2U6W-LBUfbe0wby=Kgr57Hcsth_cLzxbTviY_hTAZ8Q@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-1313706214.22da5f@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: Tue, 19 Jul 2011 22:23:37 -0000

On 19 Jul 2011, at 02:26, Erik Kline wrote:
>> Given that each of us reads something different into the definition =
of HISTORIC, is there any hope that this thread will ever converge?
>=20
> I don't see any "progress".
>=20
> We may just have to blacklist any resolvers that have 6to4 clients
> behind them and leave it at that.

Including Google's very own?

Cheers,
Sabahattin

From joelja@bogus.com  Tue Jul 19 15:41:26 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 E600D21F854A for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 15:41:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.746
X-Spam-Level: 
X-Spam-Status: No, score=-102.746 tagged_above=-999 required=5 tests=[AWL=-0.147, 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 oJV6jNs9OKwu for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 15:41:26 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 59A2721F8549 for <ietf@ietf.org>; Tue, 19 Jul 2011 15:41:26 -0700 (PDT)
Received: from [172.16.24.51] (host-64-47-136-190.masergy.com [64.47.136.190]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p6JMfM43073203 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 19 Jul 2011 22:41:22 GMT (envelope-from joelja@bogus.com)
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <4E25F868.1000109@dougbarton.us>
Date: Tue, 19 Jul 2011 15:41:16 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <CF15E17C-2433-48EB-84C8-D78647E22C23@bogus.com>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <BBB3AB81-1A20-4022-8687-CD88B000B281@bogus.com> <A6908373951C6911489DF57A@PST.JCK.COM> <71D5A97D-7119-4082-BC87-6505370CE800@bogus.com> <13205C286662DE4387D9AF3AC30EF456D3F3DEEA84@EMBX01-WF.jnpr.net> <C2C73F7968F19FEEF11B2C67@[192.168.1.128]> <E85A5A32-3665-4932-96A7-BADB11DDB2E8@sabahattin-gucukoglu.com> <4E25F868.1000109@dougbarton.us>
To: Doug Barton <dougb@dougbarton.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]); Tue, 19 Jul 2011 22:41:23 +0000 (UTC)
Cc: ietf@ietf.org, Sabahattin Gucukoglu <mail-dated-1313701310.575d90@sabahattin-gucukoglu.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, 19 Jul 2011 22:41:27 -0000

On Jul 19, 2011, at 2:34 PM, Doug Barton wrote:

> On 07/19/2011 14:01, Sabahattin Gucukoglu wrote:
>> Clearly, the view that making something historic when it's in active =
use is offensive.  No standards body could seek to stand behind their =
specifications, or to give the impression of doing so, with such a =
position.

That's a fairly odd position to take, if we do something which turns out =
to be a bad idea, should we stand behind it regardless of the validity =
of the criticism?

The number of drafts, I've seen over the course of the last decade and a =
half with the title "foo considered harmful" woulkd tend to indicate =
otherwise.=20

> Define "active use."


If in fact no-one were using it there would be little point in engaging =
in the activity.

rfc 5095 and 4966 were not created to address issues that were due to =
protocols being dead to the world...=

From mail@sabahattin-gucukoglu.com  Tue Jul 19 16:24:56 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 A040A228013 for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 16:24:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.19
X-Spam-Level: 
X-Spam-Status: No, score=0.19 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_EQ_IP_ADDR=1.119, RCVD_IN_PBL=0.905]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VZV56eKKFQMr for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 16:24:56 -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 B51A8228012 for <ietf@ietf.org>; Tue, 19 Jul 2011 16:24:55 -0700 (PDT)
Received: from Mintaka.sabahattin-gucukoglu.com ([::ffff:127.0.0.1]:35401) by Mintaka.sabahattin-gucukoglu.com with [XMail 1.27 ESMTP Server] id <S38640> for <ietf@ietf.org> from <mail@sabahattin-gucukoglu.com>; Wed, 20 Jul 2011 00:24:53 +0100
Received: from [172.20.10.2] (178.240.24.22) (using SMTP over TLS) by Mintaka.sabahattin-gucukoglu.com (tmda-ofmipd) with ESMTP; Wed, 20 Jul 2011 00:24:51 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
In-Reply-To: <4E25F868.1000109@dougbarton.us>
Date: Wed, 20 Jul 2011 02:24:49 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <90D829BF-BB51-4B0E-B9A6-4C9CCA1D2840@sabahattin-gucukoglu.com>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <BBB3AB81-1A20-4022-8687-CD88B000B281@bogus.com> <A6908373951C6911489DF57A@PST.JCK.COM> <71D5A97D-7119-4082-BC87-6505370CE800@bogus.com> <13205C286662DE4387D9AF3AC30EF456D3F3DEEA84@EMBX01-WF.jnpr.net> <C2C73F7968F19FEEF11B2C67@[192.168.1.128]> <E85A5A32-3665-4932-96A7-BADB11DDB2E8@sabahattin-gucukoglu.com> <4E25F868.1000109@dougbarton.us>
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-1313709893.f09013@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: Tue, 19 Jul 2011 23:24:56 -0000

On 20 Jul 2011, at 00:34, Doug Barton wrote:
On 07/19/2011 14:01, Sabahattin Gucukoglu wrote:
>> Clearly, the view that making something historic when it's in active =
use is offensive.  No standards body could seek to stand behind their =
specifications, or to give the impression of doing so, with such a =
position.
>=20
> Define "active use."

Actively being used.  In production.  So that taking it away would hurt =
the entity using it, threaten the entity's comfort and convenience, or =
just generally go against the stated goals of making the Internet a =
better place for everybody through the instrumentation and maintenance =
of standards.

But none of us like IPv4 and that's a fact.  Last one to sign the action =
to move it to historic's a yellow-belly.

Cheers,
Sabahattin

From jmh@joelhalpern.com  Tue Jul 19 16:39:09 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 B4EC111E8095 for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 16:39:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.583
X-Spam-Level: 
X-Spam-Status: No, score=-102.583 tagged_above=-999 required=5 tests=[AWL=0.016, 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 Kjg0VHKsRDEI for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 16:39:09 -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 3124311E808B for <ietf@ietf.org>; Tue, 19 Jul 2011 16:39:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 856ED322C1BA; Tue, 19 Jul 2011 16:39:08 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.10.10.102] (pool-71-161-50-210.clppva.btas.verizon.net [71.161.50.210]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id DE7B1322C1AF; Tue, 19 Jul 2011 16:39:07 -0700 (PDT)
Message-ID: <4E261593.2030700@joelhalpern.com>
Date: Tue, 19 Jul 2011 19:38:59 -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: Doug Barton <dougb@dougbarton.us>
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM>	<BBB3AB81-1A20-4022-8687-CD88B000B281@bogus.com>	<A6908373951C6911489DF57A@PST.JCK.COM>	<71D5A97D-7119-4082-BC87-6505370CE800@bogus.com>	<13205C286662DE4387D9AF3AC30EF456D3F3DEEA84@EMBX01-WF.jnpr.net>	<C2C73F7968F19FEEF11B2C67@[192.168.1.128]>	<E85A5A32-3665-4932-96A7-BADB11DDB2E8@sabahattin-gucukoglu.com> <4E25F868.1000109@dougbarton.us>
In-Reply-To: <4E25F868.1000109@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Sabahattin Gucukoglu <mail-dated-1313701310.575d90@sabahattin-gucukoglu.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, 19 Jul 2011 23:39:09 -0000

After all, we moved RIPv1 to Historic when it was still widely 
implemented, and used in many networks.
Yours,
Joel

On 7/19/2011 5:34 PM, Doug Barton wrote:
> On 07/19/2011 14:01, Sabahattin Gucukoglu wrote:
>> Clearly, the view that making something historic when it's in active use is offensive.  No standards body could seek to stand behind their specifications, or to give the impression of doing so, with such a position.
>
> Define "active use."
>
>

From mail@sabahattin-gucukoglu.com  Tue Jul 19 17:19:32 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 D4C5321F8B06 for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 17:19:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.19
X-Spam-Level: 
X-Spam-Status: No, score=0.19 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_EQ_IP_ADDR=1.119, RCVD_IN_PBL=0.905]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vJ7d7ll5xRrc for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 17:19:32 -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 D9BF121F874A for <ietf@ietf.org>; Tue, 19 Jul 2011 17:19:31 -0700 (PDT)
Received: from Mintaka.sabahattin-gucukoglu.com ([::ffff:127.0.0.1]:35714) by Mintaka.sabahattin-gucukoglu.com with [XMail 1.27 ESMTP Server] id <S3864E> for <ietf@ietf.org> from <mail@sabahattin-gucukoglu.com>; Wed, 20 Jul 2011 01:19:30 +0100
Received: from [172.20.10.2] (178.240.24.22) (using SMTP over TLS) by Mintaka.sabahattin-gucukoglu.com (tmda-ofmipd) with ESMTP; Wed, 20 Jul 2011 01:19:26 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
In-Reply-To: <CF15E17C-2433-48EB-84C8-D78647E22C23@bogus.com>
Date: Wed, 20 Jul 2011 03:19:23 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <B446BFB1-AE05-4A88-ADA4-E5FAA9061CFF@sabahattin-gucukoglu.com>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <BBB3AB81-1A20-4022-8687-CD88B000B281@bogus.com> <A6908373951C6911489DF57A@PST.JCK.COM> <71D5A97D-7119-4082-BC87-6505370CE800@bogus.com> <13205C286662DE4387D9AF3AC30EF456D3F3DEEA84@EMBX01-WF.jnpr.net> <C2C73F7968F19FEEF11B2C67@[192.168.1.128]> <E85A5A32-3665-4932-96A7-BADB11DDB2E8@sabahattin-gucukoglu.com> <4E25F868.1000109@dougbarton.us> <CF15E17C-2433-48EB-84C8-D78647E22C23@bogus.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-1313713170.3e13ca@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: Wed, 20 Jul 2011 00:19:32 -0000

On 20 Jul 2011, at 01:41, Joel Jaeggli wrote:
On Jul 19, 2011, at 2:34 PM, Doug Barton wrote:
>> On 07/19/2011 14:01, Sabahattin Gucukoglu wrote:
>>> Clearly, the view that making something historic when it's in active =
use is offensive.  No standards body could seek to stand behind their =
specifications, or to give the impression of doing so, with such a =
position.
>=20
> That's a fairly odd position to take, if we do something which turns =
out to be a bad idea, should we stand behind it regardless of the =
validity of the criticism?

No.  But if it's in active use, we have something of an obligation to =
the users.  The fact that it's in use is a fairly clear indication, =
regardless of technical quality (the review process being meant as an =
aid to identifying the more obvious problems before publication) that it =
is or can be made to be useful.  That's an argument in favour.  I don't =
dispute that protocols can turn out to be harmful, and there's a good vs =
bad benefit analysis to be made for lots of different reasons, but as =
has already been said before, the historic label is an *extremely* blunt =
instrument that is almost always reserved for specifications that have =
actually come to rest, following the logical English definition of =
"Historic" or "Historical".  Better for the community to be informed =
about the good and bad of protocols with troublesome aspects.

> The number of drafts, I've seen over the course of the last decade and =
a half with the title "foo considered harmful" woulkd tend to indicate =
otherwise.=20
>=20
>> Define "active use."
>=20
> If in fact no-one were using it there would be little point in =
engaging in the activity.

Right, precisely.  If the call weren't made, or it were made but happily =
ignored by everyone, I think we can take it as red that nobody minds too =
much.

> rfc 5095 and 4966 were not created to address issues that were due to =
protocols being dead to the world...

Well, FWIW, NAT-PT is still implemented and in use, most recently for =
evil purposes.  But once again, the designation means that the protocol =
has reached the end of its useful service life; there is no further use =
that can't be better served with our newer, shinier standards.  That is =
something we explicitly indicate, so implementers can get on and =
implement the better solution.  And in every case, we have =
"Applicability statements" or "Reasons to move" documents, so the =
community understands.

Cheers,
Sabahattin

From rbarnes@bbn.com  Tue Jul 19 20:02:35 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 7C7EA11E80AF; Tue, 19 Jul 2011 20:02:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.591
X-Spam-Level: 
X-Spam-Status: No, score=-106.591 tagged_above=-999 required=5 tests=[AWL=0.008, 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 OhSqP8XHTrqF; Tue, 19 Jul 2011 20:02:34 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id C123911E80AD; Tue, 19 Jul 2011 20:02:34 -0700 (PDT)
Received: from [128.89.253.17] (port=63728 helo=[172.17.119.227]) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1QjN3M-000Fhn-Jg; Tue, 19 Jul 2011 23:02:34 -0400
From: Richard L. Barnes <rbarnes@bbn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART  last call review of draft-ietf-hybi-thewebsocketprotocol-10
Date: Tue, 19 Jul 2011 23:01:53 -0400
Message-Id: <B9DDE41C-1451-4C97-ACA4-0E4E26B75A07@bbn.com>
To: General Area Review Team <gen-art@ietf.org>, draft-ietf-websec-thewebsocketprotocol@tools.ietf.org, IETF Discussion <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1082)
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: Wed, 20 Jul 2011 03:02:35 -0000

I am the assigned Gen-ART reviewer for this draft. For background on=20
Gen-ART, please see the FAQ at=20
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments=20
you may receive.

Document: draft-ietf-hybi-thewebsocketprotocol-10.txt
Reviewer: Richard Barnes
Review Date: 19 July 2011
IETF LC End Date: 25 July 2011
IESG Telechat date: (if known) -

Summary:
Not ready. =20

Major issues:

[Is GET/Upgrade appropriate?]
It seems like the use of GET here goes beyond the normal "safe" =
semantics for that method.  To quote RFC 2616:
"
   In particular, the convention has been established that the GET and
   HEAD methods SHOULD NOT have the significance of taking an action
   other than retrieval.
"
In addition, alternative protocols specified in Upgrade headers are =
generally optional, whereas in this case, the transaction fails overall =
if the server does not support the websocket protocol.  It doesn't look =
to me like any of the current methods provide much better semantics =
(except possiblyCONNECT or the use of OPTIONS as in RFC 2817), and it =
seems like defining a new method could help get around the Upgrade issue =
as well.

[Huge buffers]
The frame length can be 7, 16, or 64 bits long.  Since the client is =
expected to buffer data until the end of a frame, this is asking clients =
to buffer 128 B, 64 KB, or 16 EB.  If it were 32 bits, the max would be =
4 MB.  Why not just make this a 32-bit fixed length field?

[Why is masking necessary?]
I seriously question the necessity of the masking of data frames.  As I =
understand it, the goal is to prevent proxies that don't understand =
Upgrade from confusing WebSocket data with HTTP data.  This risk seems a =
little dubious to me; has such a poisoning attack been demonstrated?  It =
seems like there are much simpler ways of doing this, like using a =
method other than GET (either CONNECT or something new).  =20

[Why only client-to-server masking?]
Why isn't masking required on server-to-client frames?

[Unlimited buffering with fragmentation]
Much like with the frame length issue above, the fragmentation mechanism =
here seems like it imposes a heavy burden on the receive side.  Since =
the receiving client is supposed to buffer data until the end of a =
frame, it seems like fragmentation could be used to cause a receiving =
client to buffer a frame of indefinite size.=20


Minor issues:

[Setting protocol]
In the NOTE in Section 1.3, the document observes that Sec- headers =
can't be set in XHRs.  But clearly the Sec-WebSocket-Protocol header can =
be set through some API that applications use to get to this protocol.  =
So it seems a little misleading to imply that scripts can't set these =
headers (besides -Version and -Origin).

[Use existing Origin header]
Why is this document creating a separate Sec-WebSocket-Origin header, =
rather than using the Origin header from draft-ietf-websec-origin?  =20

[Need a reference to CORS]
It would be helpful to have a reference to Cross-Origin Resource Sharing =
in the NOTE in this section, since the pre-request check that is =
described is exactly a CORS priming request.

[Key is over-engineered]
What is the need for the hash and GUID in the handshake processing of =
the key?  It seems like it would be sufficient for the server to do =
anything deterministic with the key, even something as simple as =
incrementing it or flipping the bits.



Nits / Editorial comments:

[Why not plain sockets?]
The introduction makes clear why this protocol is needed instead of =
HTTP, but not why this protocol improves over providing a plain socket =
interface.  Presumably this is because the HTTP header provides a space =
where the browser can inject trusted information? =20

[Put the handshake section first]
It would really increase readability to put all the =
negotiation/handshake parts up front, before you get to the data format =
(Section 4).  As it is, when I got to the extension data part, I didn't =
realize that there was an extension mechanism, since it hadn't been =
mentioned yet.

[Stray sections]
It seems like Section 8 (Error Handling) should be moved up to Section =
4.6, and Section 9 (Extensions) should be part of section 4. =20


From ynir@checkpoint.com  Tue Jul 19 23:23:37 2011
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50C5321F8513 for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 23:23:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.681
X-Spam-Level: 
X-Spam-Status: No, score=-10.681 tagged_above=-999 required=5 tests=[AWL=-0.082, 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 fZk51O5NevyI for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2011 23:23:33 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id E116021F8AF4 for <ietf@ietf.org>; Tue, 19 Jul 2011 23:23:32 -0700 (PDT)
X-CheckPoint: {4E268207-3-1B221DC2-FFFF}
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id p6K6NVH5008913 for <ietf@ietf.org>; Wed, 20 Jul 2011 09:23:31 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Wed, 20 Jul 2011 09:23:31 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: IETF discussion list <ietf@ietf.org>
Date: Wed, 20 Jul 2011 09:23:29 +0300
Subject: Standards
Thread-Topic: Standards
Thread-Index: AcxGpYrHfHld6MhRS3aYHJ0b7/O7rA==
Message-ID: <CA4C4F11.3ED2%ynir@checkpoint.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
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, 20 Jul 2011 06:23:37 -0000

Hi

Very appropriate for XKCD to post this just a few days before an IETF
meeting.

http://www.xkcd.com/927/

(For those who are not familiar with XKCD, don't miss the alt-text on the
picture)

Yoav


From bertietf@bwijnen.net  Wed Jul 20 00:17:22 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 9305F21F849F for <ietf@ietfa.amsl.com>; Wed, 20 Jul 2011 00: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=[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 xlkWj4prAB+M for <ietf@ietfa.amsl.com>; Wed, 20 Jul 2011 00:17:18 -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 2968021F8546 for <ietf@ietf.org>; Wed, 20 Jul 2011 00:17:15 -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 1QjR1n-0007N9-Dn; Wed, 20 Jul 2011 09:17:12 +0200
Received: from dog.ripe.net ([193.0.1.217] helo=BWMACBOOK.local) by ayeaye.ripe.net with esmtp (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1QjR1n-0007uP-8e; Wed, 20 Jul 2011 09:17:07 +0200
Message-ID: <4E2680F2.8030901@bwijnen.net>
Date: Wed, 20 Jul 2011 09:17:06 +0200
From: "Bert (IETF) Wijnen" <bertietf@bwijnen.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Standards
References: <CA4C4F11.3ED2%ynir@checkpoint.com>
In-Reply-To: <CA4C4F11.3ED2%ynir@checkpoint.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: 86ab03e524994f79ca2c75a176445dd4354c21bc24eca4ebabcf636d61f4787b
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2011 07:17:22 -0000

I LOVE this one.

Bert

On 7/20/11 8:23 AM, Yoav Nir wrote:
> Hi
>
> Very appropriate for XKCD to post this just a few days before an IETF
> meeting.
>
> http://www.xkcd.com/927/
>
> (For those who are not familiar with XKCD, don't miss the alt-text on the
> picture)
>
> Yoav
>


From nsb@guppylake.com  Wed Jul 20 00:22:30 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 DFACC5E8008 for <ietf@ietfa.amsl.com>; Wed, 20 Jul 2011 00:22:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.189
X-Spam-Level: 
X-Spam-Status: No, score=-2.189 tagged_above=-999 required=5 tests=[AWL=0.410,  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 ZVYXZAQWlMXT for <ietf@ietfa.amsl.com>; Wed, 20 Jul 2011 00:22:27 -0700 (PDT)
Received: from server1.netnutz.com (server1.netnutz.com [72.233.90.3]) by ietfa.amsl.com (Postfix) with ESMTP id 0416311E8073 for <ietf@ietf.org>; Wed, 20 Jul 2011 00:22:27 -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=J9/JBtXiEo2j2ygYjsCo5FT2/8BjJgrXNTA2EPNfzAD9im/xxipacVy4jh/3KvNvM5wbIcPpDBu4EOxkle45dpNIMG+e97NJYjcvTo/VUnzPNwl2uPeTuUNlfxsyQ0Ou;
Received: from host-39-196-68-109.spectrum1.uk.sharedband.net ([109.68.196.39] helo=[10.1.0.227]) by server1.netnutz.com with esmtpa (Exim 4.69) (envelope-from <nsb@guppylake.com>) id 1QjR6t-0001tz-0m; Wed, 20 Jul 2011 03:22:23 -0400
Subject: Re: Confidentiality notices on email messages
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Nathaniel Borenstein <nsb@guppylake.com>
In-Reply-To: <01O3TP8DZQF000RCTX@mauve.mrochek.com>
Date: Wed, 20 Jul 2011 08:22:19 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <9BE3951D-D5AB-42D9-8516-B5C6FE6AE4A2@guppylake.com>
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com> <29987.1310565058@marajade.sandelman.ca> <4E1DCA13.9030301@acm.org> <04AE56F0C4CE8168D1B38D59@PST.JCK.COM> <p0624066dca44df0ca50f@loud.pensive.org> <49A68144182BB270C11BC841@PST.JCK.COM> <F5833273385BB34F99288B3648C4F06F134EBC4D4B@EXCH-C2.corp.cloudmark.com> <FDD50EB2-B783-49B3-92C2-56A21EFAEF11@guppylake.com> <4E2429FF.9080202@alvestrand.no> <01O3TP8DZQF000RCTX@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: Harald Alvestrand <harald@alvestrand.no>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2011 07:22:31 -0000

Except that the other Content-disposition values express the sender's =
intent, whereas this one expresses the receiver's [likely] perception.  =
It might as well be "Content-disposition: discard" -- no sender would =
ever generate it.  In contrast one could make at least a semi-serious =
case that by defining a media type for legal disclaimers, you could have =
UA's that by default hid it but didn't throw it away, so that you could =
see it later if for some inconceivable reason you wanted to.  (And the =
issue of including different media types could be addressed by making it =
multipart/noise.)

On the other hand, if Ned and I disagree that's itself an indication =
that this is not a very serious discussion.  :-)  -- Nathaniel


On Jul 19, 2011, at 4:16 PM, ned+ietf@mauve.mrochek.com wrote:

>> Content-disposition: noise.
>=20
> Harald, I was about to say the same thing but you beat me to it. =
Unless we're
> prepared to talk about defining a general format for such notices (and =
I'm
> pretty sure we're not interested in doing that), this doesn't fit as a =
media
> type - I can easily envision using various different types depending =
on the
> sort of notice I want to send.
>=20
> But a content-disposition value has the right semantics and makes all =
sorts
> of sense.
>=20
> 				Ned
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From harald@alvestrand.no  Wed Jul 20 00:40:13 2011
Return-Path: <harald@alvestrand.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE26A21F8A64 for <ietf@ietfa.amsl.com>; Wed, 20 Jul 2011 00:40:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EynrFYVz1zTP for <ietf@ietfa.amsl.com>; Wed, 20 Jul 2011 00:40:13 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 35AA321F89C1 for <ietf@ietf.org>; Wed, 20 Jul 2011 00:40:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 4065339E0BF for <ietf@ietf.org>; Wed, 20 Jul 2011 09:39:06 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fv65FQOq-wKw for <ietf@ietf.org>; Wed, 20 Jul 2011 09:39:01 +0200 (CEST)
Received: from hta-dell.lul.corp.google.com (62-20-124-50.customer.telia.com [62.20.124.50]) by eikenes.alvestrand.no (Postfix) with ESMTPS id DB21F39E072 for <ietf@ietf.org>; Wed, 20 Jul 2011 09:39:01 +0200 (CEST)
Message-ID: <4E268657.6040005@alvestrand.no>
Date: Wed, 20 Jul 2011 09:40:07 +0200
From: Harald Alvestrand <harald@alvestrand.no>
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: Confidentiality notices on email messages
References: <CAC4RtVBGgk74VMEty9u5Yq+DFy=oR5tOnbZ3R5x83Gyee6mRNw@mail.gmail.com>	<29987.1310565058@marajade.sandelman.ca> <4E1DCA13.9030301@acm.org>	<04AE56F0C4CE8168D1B38D59@PST.JCK.COM>	<p0624066dca44df0ca50f@loud.pensive.org>	<49A68144182BB270C11BC841@PST.JCK.COM>	<F5833273385BB34F99288B3648C4F06F134EBC4D4B@EXCH-C2.corp.cloudmark.com>	<FDD50EB2-B783-49B3-92C2-56A21EFAEF11@guppylake.com>	<4E2429FF.9080202@alvestrand.no>	<01O3TP8DZQF000RCTX@mauve.mrochek.com> <9BE3951D-D5AB-42D9-8516-B5C6FE6AE4A2@guppylake.com>
In-Reply-To: <9BE3951D-D5AB-42D9-8516-B5C6FE6AE4A2@guppylake.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2011 07:40:14 -0000

On 07/20/11 09:22, Nathaniel Borenstein wrote:
> Except that the other Content-disposition values express the sender's intent, whereas this one expresses the receiver's [likely] perception.
In this case, we have to invent a cute backronym for it that expresses 
the sender's intent.... what about Not Optional {Ignorable,Irritating} 
Suit-avoiding Exposition?

>    It might as well be "Content-disposition: discard" -- no sender would ever generate it.  In contrast one could make at least a semi-serious case that by defining a media type for legal disclaimers, you could have UA's that by default hid it but didn't throw it away, so that you could see it later if for some inconceivable reason you wanted to.  (And the issue of including different media types could be addressed by making it multipart/noise.)
>
> On the other hand, if Ned and I disagree that's itself an indication that this is not a very serious discussion.  :-)  -- Nathaniel
We can always find a point of agreement - in this case on the 
seriousness of the discussion!
>
> On Jul 19, 2011, at 4:16 PM, ned+ietf@mauve.mrochek.com wrote:
>
>>> Content-disposition: noise.
>> Harald, I was about to say the same thing but you beat me to it. Unless we're
>> prepared to talk about defining a general format for such notices (and I'm
>> pretty sure we're not interested in doing that), this doesn't fit as a media
>> type - I can easily envision using various different types depending on the
>> sort of notice I want to send.
>>
>> But a content-disposition value has the right semantics and makes all sorts
>> of sense.
>>
>> 				Ned
>> _______________________________________________
>> 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 ynir@checkpoint.com  Wed Jul 20 04:20:41 2011
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 123FA21F8922 for <ietf@ietfa.amsl.com>; Wed, 20 Jul 2011 04:20:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.672
X-Spam-Level: 
X-Spam-Status: No, score=-10.672 tagged_above=-999 required=5 tests=[AWL=-0.073, 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 XKYo+-q0v4kP for <ietf@ietfa.amsl.com>; Wed, 20 Jul 2011 04:20:37 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 6B29721F8777 for <ietf@ietf.org>; Wed, 20 Jul 2011 04:20:35 -0700 (PDT)
X-CheckPoint: {4E26C7A6-7-1B221DC2-FFFF}
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id p6KBJlLp003196;  Wed, 20 Jul 2011 14:19:47 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Wed, 20 Jul 2011 14:19:47 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "Bert (IETF) Wijnen" <bertietf@bwijnen.net>
Date: Wed, 20 Jul 2011 14:19:37 +0300
Subject: Re: Standards
Thread-Topic: Standards
Thread-Index: AcxGzu6KtXy/JjwhRyuhn/OkyRWKgQ==
Message-ID: <CA4C942D.3F35%ynir@checkpoint.com>
In-Reply-To: <4E2680F2.8030901@bwijnen.net>
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
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2011 11:20:41 -0000

[Helmet on]

Maybe they should first move the 14 competing standards to Historic.


On 7/20/11 10:17 AM, "Bert (IETF) Wijnen" <bertietf@bwijnen.net> wrote:

>I LOVE this one.
>
>Bert
>
>On 7/20/11 8:23 AM, Yoav Nir wrote:
>> Hi
>>
>> Very appropriate for XKCD to post this just a few days before an IETF
>> meeting.
>>
>> http://www.xkcd.com/927/
>>
>> (For those who are not familiar with XKCD, don't miss the alt-text on
>>the
>> picture)
>>
>> Yoav


From moore@network-heretics.com  Wed Jul 20 04:47:09 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 C83DE21F8741 for <ietf@ietfa.amsl.com>; Wed, 20 Jul 2011 04:47:09 -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 d0CTa023JMB9 for <ietf@ietfa.amsl.com>; Wed, 20 Jul 2011 04:47:06 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id EAFAB21F8726 for <ietf@ietf.org>; Wed, 20 Jul 2011 04:47:05 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 3FFAC20856; Wed, 20 Jul 2011 07:47:05 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute4.internal (MEProxy); Wed, 20 Jul 2011 07:47: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=GLuD/0iz++eCvdzmB8JUKm9y2Nw=; b=ty aJQ1GGWsnDSOdu4jjg+ZyBQxUe7mI1rHQABRTAnpCKUuc2EaE6oUoQv2/qahobHw jPfjZp1lEOzl4QbCKz/0/4e+0lQ38JX2awPNgiJ6MFrasJcpiZbspnpirCNcD4U8 KcVwsO6h+5oLtYFNQouzB3Sejc4VTZ8YfCQ5QYDKM=
X-Sasl-enc: ejmlpvT/dQaDaZkSLy7nnziMvzQAe+D3VQ4U9X1MOAR4 1311162424
Received: from [10.59.1.76] (static-71-166-174-114.washdc.east.verizon.net [71.166.174.114]) by mail.messagingengine.com (Postfix) with ESMTPA id 51D1944E77D; Wed, 20 Jul 2011 07:47:03 -0400 (EDT)
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
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: <4E261593.2030700@joelhalpern.com>
Date: Wed, 20 Jul 2011 07:47:01 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <1114D1D9-A169-4C70-98CC-93387CAA025E@network-heretics.com>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM>	<BBB3AB81-1A20-4022-8687-CD88B000B281@bogus.com>	<A6908373951C6911489DF57A@PST.JCK.COM>	<71D5A97D-7119-4082-BC87-6505370CE800@bogus.com>	<13205C286662DE4387D9AF3AC30EF456D3F3DEEA84@EMBX01-WF.jnpr.net>	<C2C73F7968F19FEEF11B2C67@[192.168.1.128]>	<E85A5A32-3665-4932-96A7-BADB11DDB2E8@sabahattin-gucukoglu.com> <4E25F868.1000109@dougbarton.us> <4E261593.2030700@joelhalpern.com>
To: Joel M. Halpern <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.1084)
Cc: Sabahattin Gucukoglu <mail-dated-1313701310.575d90@sabahattin-gucukoglu.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, 20 Jul 2011 11:47:09 -0000

yes, but if I'm not mistaken, you already had RIPv2 then.

Keith

On Jul 19, 2011, at 7:38 PM, Joel M. Halpern wrote:

> After all, we moved RIPv1 to Historic when it was still widely =
implemented, and used in many networks.
> Yours,
> Joel
>=20
> On 7/19/2011 5:34 PM, Doug Barton wrote:
>> On 07/19/2011 14:01, Sabahattin Gucukoglu wrote:
>>> Clearly, the view that making something historic when it's in active =
use is offensive.  No standards body could seek to stand behind their =
specifications, or to give the impression of doing so, with such a =
position.
>>=20
>> Define "active use."
>>=20
>>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From dworley@avaya.com  Wed Jul 20 07:54:34 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 702A621F859E for <ietf@ietfa.amsl.com>; Wed, 20 Jul 2011 07:54:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.37
X-Spam-Level: 
X-Spam-Status: No, score=-104.37 tagged_above=-999 required=5 tests=[AWL=1.229, BAYES_00=-2.599, GB_I_LETTER=-2, 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 gF9HgsOJzNpl for <ietf@ietfa.amsl.com>; Wed, 20 Jul 2011 07:54:33 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 94B1521F859C for <ietf@ietf.org>; Wed, 20 Jul 2011 07:54:33 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAMjqJk6HCzI1/2dsb2JhbABTp2N3iHykKgKbVYVeXwSYE4tU
X-IronPort-AV: E=Sophos;i="4.67,235,1309752000"; d="scan'208";a="291852622"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 20 Jul 2011 10:54:32 -0400
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 20 Jul 2011 10:47:15 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Wed, 20 Jul 2011 10:54:32 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Yoav Nir <ynir@checkpoint.com>, IETF discussion list <ietf@ietf.org>
Date: Wed, 20 Jul 2011 10:54:32 -0400
Subject: RE: Standards
Thread-Topic: Standards
Thread-Index: AcxGpYrHfHld6MhRS3aYHJ0b7/O7rAARomzF
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F579B@DC-US1MBEX4.global.avaya.com>
References: <CA4C4F11.3ED2%ynir@checkpoint.com>
In-Reply-To: <CA4C4F11.3ED2%ynir@checkpoint.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2011 14:54:34 -0000

> From: Yoav Nir [ynir@checkpoint.com]
>=20
> Very appropriate for XKCD to post this just a few days before an IETF
> meeting.
>=20
> http://www.xkcd.com/927/

And yet sometimes a standard will sweep away everything that was
before it.

One remarkably successful case is "ASCII" (containing the 26 letter
neo-Latin alphabet used by (only) the English language, ten digits,
and a couple of dozen punctuation marks), which seems to be contained
within every character code in common use.

Another is the "Internet Protocol", a networking scheme that differed
from its many competitors by not being sponsored by any networking
company.

I really do believe that in 1,000 years, a section of any good "history
of computer technology" book will explain why a certain few letter-forms
are segregated into the first 128 locations in the character code.

Dale

From alexey.melnikov@isode.com  Wed Jul 20 09:03:29 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 83DB121F8AAC; Wed, 20 Jul 2011 09:03:29 -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 t7eyeHk9t9N9; Wed, 20 Jul 2011 09:03:28 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 87B4E21F8A62; Wed, 20 Jul 2011 09:03:28 -0700 (PDT)
Received: from [192.168.1.124] ((unknown) [62.3.217.253])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <Tib8TgB=gD=p@rufus.isode.com>; Wed, 20 Jul 2011 17:03:27 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4E26FC3F.1030300@isode.com>
Date: Wed, 20 Jul 2011 17:03:11 +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: "Richard L. Barnes" <rbarnes@bbn.com>
Subject: Re: Gen-ART last call review of draft-ietf-hybi-thewebsocketprotocol-10
References: <B9DDE41C-1451-4C97-ACA4-0E4E26B75A07@bbn.com>
In-Reply-To: <B9DDE41C-1451-4C97-ACA4-0E4E26B75A07@bbn.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-websec-thewebsocketprotocol@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, 20 Jul 2011 16:03:29 -0000

Hi Richard,
Thanks for the review. I will answer to some of your comments and I or 
my co-editor will followup on remaining issues later on.

Richard L. Barnes wrote:

>I am the assigned Gen-ART reviewer for this draft. For background on 
>Gen-ART, please see the FAQ at 
><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
>Please resolve these comments along with any other Last Call comments 
>you may receive.
>
>Document: draft-ietf-hybi-thewebsocketprotocol-10.txt
>Reviewer: Richard Barnes
>Review Date: 19 July 2011
>IETF LC End Date: 25 July 2011
>IESG Telechat date: (if known) -
>
>Summary:
>Not ready.  
>
>Major issues:
>
>[Is GET/Upgrade appropriate?]
>It seems like the use of GET here goes beyond the normal "safe" semantics for that method.  To quote RFC 2616:
>"
>   In particular, the convention has been established that the GET and
>   HEAD methods SHOULD NOT have the significance of taking an action
>   other than retrieval.
>"
>In addition, alternative protocols specified in Upgrade headers are generally optional, whereas in this case, the transaction fails overall if the server does not support the websocket protocol.  It doesn't look to me like any of the current methods provide much better semantics (except possiblyCONNECT or the use of OPTIONS as in RFC 2817), and it seems like defining a new method could help get around the Upgrade issue as well.
>
This issue was discussed extensively in the WG and was reraised during 
IETF LC by others. I will followup with a more detailed answer (or maybe 
the WG agrees with you and this would be changed), but a quick comment 
on one of the points.

The WG discussed defining a new HTTP method, but the idea didn't have 
the support of majority because new HTTP methods are hard to deploy (due 
to old intermediaries which don't handle them as well as they should 
have if they were compliant with RFC 2616).

>[Huge buffers]
>The frame length can be 7, 16, or 64 bits long.  Since the client is expected to buffer data until the end of a frame, this is asking clients to buffer 128 B, 64 KB, or 16 EB.  If it were 32 bits, the max would be 4 MB.  Why not just make this a 32-bit fixed length field?
>
This was discussed in the WG. On one hand the frame length encoding is 
optimized for packet size (the field overhead is small for smaller 
packets) and on another hand there was a desire to support big buffer 
sizes, thus the current proposal. I believe a single 32bit field was 
proposed but was explicitly decided against.

>[Why is masking necessary?]
>I seriously question the necessity of the masking of data frames.  As I understand it, the goal is to prevent proxies that don't understand Upgrade from confusing WebSocket data with HTTP data.  This risk seems a little dubious to me; has such a poisoning attack been demonstrated?  It seems like there are much simpler ways of doing this, like using a method other than GET (either CONNECT or something new).
>
I am not a good person to answer this, but believe me the WG debated 
this very issue for weeks.

>[Why only client-to-server masking?]
>Why isn't masking required on server-to-client frames?
>
As above.

>[Unlimited buffering with fragmentation]
>Much like with the frame length issue above, the fragmentation mechanism here seems like it imposes a heavy burden on the receive side.  Since the receiving client is supposed to buffer data until the end of a frame, it seems like fragmentation could be used to cause a receiving client to buffer a frame of indefinite size. 
>
This is not really different from what other protocols like HTTP and 
SMTP already allow. I think it would be fair to note this in the 
Security Considerations section, but I don't think this feature should 
be removed. Fragmentation does allow senders to start sending data 
before the total size of the object is known (e.g. if data is generated 
on the fly), which was considered as an important feature by the WG.

>Minor issues:
>
>[Setting protocol]
>In the NOTE in Section 1.3, the document observes that Sec- headers can't be set in XHRs.  But clearly the Sec-WebSocket-Protocol header can be set through some API that applications use to get to this protocol.  So it seems a little misleading to imply that scripts can't set these headers (besides -Version and -Origin).
>  
>
But a script can't set the Sec-WebSocket-Protocol header field value 
directly.

 [snip]

I will also look at your editorial proposals.

Best Regards,
Alexey


From john-ietf@jck.com  Wed Jul 20 09:22: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 C80E121F869D for <ietf@ietfa.amsl.com>; Wed, 20 Jul 2011 09:22:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.618
X-Spam-Level: 
X-Spam-Status: No, score=-103.618 tagged_above=-999 required=5 tests=[AWL=0.981, BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4JFvy3zkXs1a for <ietf@ietfa.amsl.com>; Wed, 20 Jul 2011 09:22:13 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 4ADE521F8639 for <ietf@ietf.org>; Wed, 20 Jul 2011 09:22:13 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QjZXE-00069e-Q8; Wed, 20 Jul 2011 12:22:09 -0400
Date: Wed, 20 Jul 2011 12:22:07 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, Yoav Nir <ynir@checkpoint.com>, IETF discussion list <ietf@ietf.org>
Subject: RE: Standards
Message-ID: <D22DB2111653F5BCEF78B602@PST.JCK.COM>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F579B@DC-US1MBEX4.global.avaya.com>
References: <CA4C4F11.3ED2%ynir@checkpoint.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F579B@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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2011 16:22:17 -0000

--On Wednesday, July 20, 2011 10:54 -0400 "Worley, Dale R
(Dale)" <dworley@avaya.com> wrote:

>> From: Yoav Nir [ynir@checkpoint.com]
>> 
>> Very appropriate for XKCD to post this just a few days before
>> an IETF meeting.
>> 
>> http://www.xkcd.com/927/
> 
> And yet sometimes a standard will sweep away everything that
> was before it.

If "sweep away" is something that occurs after many years of
competing standards and a long period of time in which the
outcome was not clear, then sure.   If you believe that either
ASCII or TCP/IP quickly "swept away" its predecessors, you need
to review the actual history.  See below.

> One remarkably successful case is "ASCII" (containing the 26
> letter neo-Latin alphabet used by (only) the English language,
> ten digits, and a couple of dozen punctuation marks), which
> seems to be contained within every character code in common
> use.

Many linguists and orthographers would dispute whether the
letters of ASCII are sufficient to write English as well as your
assertion that there are no other languages that can be written
effectively in that set of characters.  But ASCII, especially if
you mean the encoding typically used today (seven bits right
justified in an eight bit field with a leading zero bit), took a
number of years to win out over several other coded character
sets and encodings.

> Another is the "Internet Protocol", a networking scheme that
> differed from its many competitors by not being sponsored by
> any networking company.

And that appeared to be so much at risk for a while --well
before it was generally established-- that the IETF actually had
an Area dedicated to OSI transition as well as several standards
for how to do it.  
> 
> I really do believe that in 1,000 years, a section of any good
> "history of computer technology" book will explain why a
> certain few letter-forms are segregated into the first 128
> locations in the character code.

I would predict that, if there are three such books, there may
be four different explanations with the largest variations
reflecting whether or not the authors understood 10646 DIS-1 and
what they think of its implications.

    john


From dworley@avaya.com  Wed Jul 20 12:03:51 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 7964921F8AA8 for <ietf@ietfa.amsl.com>; Wed, 20 Jul 2011 12:03:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.402
X-Spam-Level: 
X-Spam-Status: No, score=-103.402 tagged_above=-999 required=5 tests=[AWL=0.197, 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 Ji-SiIWaMEox for <ietf@ietfa.amsl.com>; Wed, 20 Jul 2011 12:03:51 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 950EA21F8B45 for <ietf@ietf.org>; Wed, 20 Jul 2011 12:03:10 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAFMlJ06HCzI1/2dsb2JhbABTp2d3iHyjYgKbVYVeXwSYE4tU
X-IronPort-AV: E=Sophos;i="4.67,236,1309752000"; d="scan'208";a="291915992"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 20 Jul 2011 15:03:09 -0400
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; 20 Jul 2011 14:55:52 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Wed, 20 Jul 2011 15:03:09 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: John C Klensin <john-ietf@jck.com>, Yoav Nir <ynir@checkpoint.com>, IETF discussion list <ietf@ietf.org>
Date: Wed, 20 Jul 2011 14:58:33 -0400
Subject: RE: Standards
Thread-Topic: Standards
Thread-Index: AcxG+S+2hbSE1ZKWSL+ZchoBfnnNjQAFdWas
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F57A0@DC-US1MBEX4.global.avaya.com>
References: <CA4C4F11.3ED2%ynir@checkpoint.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F579B@DC-US1MBEX4.global.avaya.com>, <D22DB2111653F5BCEF78B602@PST.JCK.COM>
In-Reply-To: <D22DB2111653F5BCEF78B602@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: Wed, 20 Jul 2011 19:03:51 -0000

> From: John C Klensin [john-ietf@jck.com]
>=20
> If "sweep away" is something that occurs after many years of
> competing standards and a long period of time in which the
> outcome was not clear, then sure.

Yes.  In the sense that over the long run, the number of "standards"
that are commonly implemented becomes smaller.  As opposed to things
like AC/DC adapters, where the number of connectors on the market seems
to increase without bound.

Dale

From shanna@juniper.net  Wed Jul 20 19:37: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 5328F21F8B06; Wed, 20 Jul 2011 19:37: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 PQbtDk+FeD00; Wed, 20 Jul 2011 19:37:07 -0700 (PDT)
Received: from exprod7og117.obsmtp.com (exprod7og117.obsmtp.com [64.18.2.6]) by ietfa.amsl.com (Postfix) with ESMTP id 704F821F8B05; Wed, 20 Jul 2011 19:37:07 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob117.postini.com ([64.18.6.12]) with SMTP ID DSNKTieQxaRWZvGw0gkGdNJG2xijf/9dLUd9@postini.com; Wed, 20 Jul 2011 19:37:07 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 20 Jul 2011 19:36:02 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Wed, 20 Jul 2011 22:36:02 -0400
From: Stephen Hanna <shanna@juniper.net>
To: "ietf@ietf.org" <ietf@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>, "draft-ietf-dime-priority-avps.all@tools.ietf.org" <draft-ietf-dime-priority-avps.all@tools.ietf.org>
Date: Wed, 20 Jul 2011 22:36:01 -0400
Subject: Secdir review of draft-ietf-dime-priority-avps-04
Thread-Topic: Secdir review of draft-ietf-dime-priority-avps-04
Thread-Index: AcxHTu34hXvg7biARZewSRVBSgbUbw==
Message-ID: <AC6674AB7BC78549BB231821ABF7A9AEB6742734F1@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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2011 02:37:08 -0000

I have reviewed this document as part of the security directorate's=20
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the=20
security area directors.  Document editors and WG chairs should treat
these comments just like any other last call comments.

This standards track document defines Diameter AVPs that can be
used to convey a variety of priority parameters. While the Security
Considerations section of this document properly requires that
implementers review the Security Considerations section in the
Diameter protocol specification and consider the issues described
there, it does not include any analysis of the specific security
issues related to priority systems. The authors should review other
Security Considerations sections relating to priority systems
(e.g. the one in RFC 4412) and add text that describes the
special security issues that arise with priority systems and
the countermeasures that may be employed.

Thanks,

Steve


From evnikita2@gmail.com  Wed Jul 20 20:28:01 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 03BDA21F8757; Wed, 20 Jul 2011 20:28:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.509
X-Spam-Level: 
X-Spam-Status: No, score=-3.509 tagged_above=-999 required=5 tests=[AWL=0.090,  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 aaYNbR+77Vn5; Wed, 20 Jul 2011 20:28:00 -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 0932621F874F; Wed, 20 Jul 2011 20:27:59 -0700 (PDT)
Received: by fxe4 with SMTP id 4so3291209fxe.27 for <multiple recipients>; Wed, 20 Jul 2011 20:27:59 -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=Z5XAGNmz/bWaDK7/NBDl2Q89eIxOOWp//bBzEErppww=; b=gkgRQS/zAQ4njAq+wCTEe2GCEYKiZytddSfe6mUHSd3L6Bohy+GJslh1Q43sTiJRWk O+FVvdjNX7l0h6F1SlqxOIHkd0bza2YT/iylIzlsCQS4EqV+jHeh5QYjlVjAV8fe/rD6 YsqJ7GyaHvZqM/PZtGe6uLJgkP5z7qdswZd2Q=
Received: by 10.223.77.92 with SMTP id f28mr4289492fak.37.1311218879150; Wed, 20 Jul 2011 20:27:59 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id w11sm1107664faj.14.2011.07.20.20.27.56 (version=SSLv3 cipher=OTHER); Wed, 20 Jul 2011 20:27:58 -0700 (PDT)
Message-ID: <4E279CE9.8090800@gmail.com>
Date: Thu, 21 Jul 2011 06:28:41 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture>
In-Reply-To: <9031.1311082001.631622@puncture>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: =?ISO-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>, Server-Initiated HTTP <hybi@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, 21 Jul 2011 03:28:01 -0000

I support the opinion that SRV mechanism for use with WebSocket should 
be incorporated in the core WS specification.  Mykyta

19.07.2011 16:26, Dave Cridland wrote:
> On Tue Jul 19 12:51:16 2011, Iñaki Baz Castillo wrote:
>> 2011/7/11 The IESG <iesg-secretary@ietf.org>:
>> > The IESG has received a request from the BiDirectional or
>> > Server-Initiated HTTP WG (hybi) to consider the following document:
>> > - 'The WebSocket protocol'
>> > <draft-ietf-hybi-thewebsocketprotocol-10.txt> as a Proposed Standard
>>
>> Hi, I assume there is no interest in making DNS SRV mechanism exposed
>> in http://tools.ietf.org/html/draft-ibc-websocket-dns-srv-02 part of
>> the WebSocket core specification, neither referencing it (in the same
>> way RFC 3261 "SIP protocol" mandates the usage of RFC 3263 "Locating
>> SIP servers").
>>
>> As said before, making such DNS SRV specification an extension (so
>> present in other document) will mean no success at all, as WebSocket
>> client implementors (i.e. webbrowser vendors) will not be mandated to
>> implement it and service providers could not rely on the support of
>> DNS SRV in web browsers. So nobody will use them (because IE10 decided
>> not to implement it, for example). IMHO this is sad due the real
>> advantages DNS SRV provides for a protocol like WebSocket.
>>
>> Yes, in HTTP there is no special DNS stuff, all the load-balancing and
>> failover mechanism are done at server side with very complex and
>> expensive solutions (www.facebook.com resolves to a single IPv4 !!!!).
>> The question is: should we also inherit every HTTP limitation in
>> WebSocket?
>
> I agree wholeheartedly with this, and strongly recommend that 
> mandatory use of SRV is included in the core protocol.
>
> I think with HTTP's very short lived requests, then it's possible to 
> work around the lack of SRV support (at a cost), but the benefit is 
> markedly higher with the long-lived, stateful sessions we're 
> anticipating with WebSocket.
>
> Dave.


From harald@alvestrand.no  Thu Jul 21 02:40:26 2011
Return-Path: <harald@alvestrand.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BDFF21F8A71 for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 02:40:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V7XkfMvFoyl8 for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 02:40:25 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 8862921F889F for <ietf@ietf.org>; Thu, 21 Jul 2011 02:40:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id D528B39E0FC for <ietf@ietf.org>; Thu, 21 Jul 2011 11:39:18 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uHnHRg62jidC for <ietf@ietf.org>; Thu, 21 Jul 2011 11:39:17 +0200 (CEST)
Received: from hta-dell.lul.corp.google.com (62-20-124-50.customer.telia.com [62.20.124.50]) by eikenes.alvestrand.no (Postfix) with ESMTPS id D871939E0FA for <ietf@ietf.org>; Thu, 21 Jul 2011 11:39:17 +0200 (CEST)
Message-ID: <4E27F407.8090006@alvestrand.no>
Date: Thu, 21 Jul 2011 11:40:23 +0200
From: Harald Alvestrand <harald@alvestrand.no>
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: Another look at 6to4 (and other IPv6 transition issues)
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM>	<BBB3AB81-1A20-4022-8687-CD88B000B281@bogus.com>	<A6908373951C6911489DF57A@PST.JCK.COM>	<71D5A97D-7119-4082-BC87-6505370CE800@bogus.com>	<13205C286662DE4387D9AF3AC30EF456D3F3DEEA84@EMBX01-WF.jnpr.net>	<C2C73F7968F19FEEF11B2C67@[192.168.1.128]>	<E85A5A32-3665-4932-96A7-BADB11DDB2E8@sabahattin-gucukoglu.com>	<4E25F868.1000109@dougbarton.us> <90D829BF-BB51-4B0E-B9A6-4C9CCA1D2840@sabahattin-gucukoglu.com>
In-Reply-To: <90D829BF-BB51-4B0E-B9A6-4C9CCA1D2840@sabahattin-gucukoglu.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: Thu, 21 Jul 2011 09:40:26 -0000

On 07/20/11 01:24, Sabahattin Gucukoglu wrote:
> On 20 Jul 2011, at 00:34, Doug Barton wrote:
> On 07/19/2011 14:01, Sabahattin Gucukoglu wrote:
>>> Clearly, the view that making something historic when it's in active use is offensive.  No standards body could seek to stand behind their specifications, or to give the impression of doing so, with such a position.
>> Define "active use."
> Actively being used.  In production.  So that taking it away would hurt the entity using it, threaten the entity's comfort and convenience, or just generally go against the stated goals of making the Internet a better place for everybody through the instrumentation and maintenance of standards.
The idea that moving a standard to Historic would take away the ability 
of people to use it reminds me of the story from the Norwegian army, 
approx 1939:

- "If the enemy invades, how will you prevent them from using the train 
network?"
- "Burn all the tickets, sir!"


From harald@alvestrand.no  Thu Jul 21 03:21:08 2011
Return-Path: <harald@alvestrand.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36B1221F84EA for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 03:21:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BZgTAFd0UedA for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 03:21:07 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 8BF9921F86DF for <ietf@ietf.org>; Thu, 21 Jul 2011 03:21:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id D71C939E0FC for <ietf@ietf.org>; Thu, 21 Jul 2011 12:20:00 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4BFYSakt55Tk for <ietf@ietf.org>; Thu, 21 Jul 2011 12:19:59 +0200 (CEST)
Received: from hta-dell.lul.corp.google.com (62-20-124-50.customer.telia.com [62.20.124.50]) by eikenes.alvestrand.no (Postfix) with ESMTPS id CEFA339E0FA for <ietf@ietf.org>; Thu, 21 Jul 2011 12:19:59 +0200 (CEST)
Message-ID: <4E27FD91.9070409@alvestrand.no>
Date: Thu, 21 Jul 2011 12:21:05 +0200
From: Harald Alvestrand <harald@alvestrand.no>
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 discussion list <ietf@ietf.org>
Subject: Review of draft-doria-gen-art-08
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2011 10:21:08 -0000

I support the publication of this document.

In general, the document is clearly written, explains the processes 
followed for gen-Art review, and forms a valuable snapshot of the 
procedures followed at this time.
It makes it very clear that the document does not, in any way, shape or 
form, attempt to modify the rules for IETF work.

One point that I can't see clearly stated (I may have missed it) is that 
both the reviews and the names of the reviewers are public. This may 
seem obvious now, but wasn't obvious when the process got started; I 
think it is important to call this out.

Nits:

- Section 4.3 links to I-D.rfc-editor-rfc2223bis - this draft expired in 
2008. New target needed.
- In the same bulleted list, the last bullet should either be a 
non-bullet or have "As well as" removed from its beginning.
- In section 4.4, a note should be made about groups of I-Ds. I think 
the process is that when a document set is Last Called as a set, one 
reviewer handles it if possible - but I am not sure about this.
- Section 6 claims that the quality of I-Ds has increased, but gives 
only a single data point (2007). Is there a second datapoint that is 
missing somehow?

Thanks for doing this!

                  Harald







From dhc@dcrocker.net  Thu Jul 21 03:40:52 2011
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9AD721F8B12 for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 03:40:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EDJk3D3SKp5F for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 03:40:48 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id AFD7421F8B11 for <ietf@ietf.org>; Thu, 21 Jul 2011 03:40:48 -0700 (PDT)
Received: from [172.17.177.164] (unassigned.matrix-consultants.com [12.180.114.2] (may be forged)) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p6LAefqW031704 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 21 Jul 2011 03:40:48 -0700
Message-ID: <4E280223.8030309@dcrocker.net>
Date: Thu, 21 Jul 2011 06:40:35 -0400
From: Dave CROCKER <dhc@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 Discussion <ietf@ietf.org>
Subject: Review of:   draft-ietf-iab-draft-iab-dns-applications-02
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]); Thu, 21 Jul 2011 03:40: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: Thu, 21 Jul 2011 10:40:52 -0000

  This is a summary of a followup review of the draft, after the one noted in
Ticket #35 of the trac wiki for this draft:

     <http://trac.tools.ietf.org/group/iab/trac/ticket/35>

  The complete version of this second review is at:

    <http://trac.tools.ietf.org/group/iab/trac/ticket/35#comment:2>


  Summary:

       The latest version of the draft contains many substantial changes.
  However it continues to have basic problems with direction, scope, detail,
  writing, and with basic confusion about architecture.

      The draft maintains its claim of being a general considerations
  discussion when, in fact, it continues to focus on fear of inappropriate
  proposals.  It continues to invoke examples of inappropriate proposals
  that lack constituency or even currency.

      In spite of language claiming to distinguish new /uses/ of the DNS
  from /changes/ to the DNS, the draft continues to confuse the two.  The
  problem appears to be a difficulty distinguishing architectural layers.
  This is like saying that TCP changes IP or that HTTP changes TCP.  Hence,
  for example, DDDS is a layer /above/ the DNS.  The only two interesting
  questions about a client layer's use of a provider layer -- such as DDDS's
  use of DNS -- is whether the functional match is acceptable and whether
  it's performance demands cause problems.  When focused on one layer, any
  further discussion of the other likely to confuse things significantly, as
  demonstrated in the draft.

      The paper continues to make broad criticisms that lack foundation and
  sometimes even lack citation.

      Some of the statements and logic sequences were entirely opaque to me.
  I could not decipher what they meant.  In some cases the apparent meaning
  was factually incorrect or confused.

      From all of this, I suspect that the only way to make useful progress
  is to start over, and to begin with a much, much more clear and concrete
  statement of the goal for the draft and then a very diligent effort to
  organize the paper's sequence and carefully document its assertions.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From dave@cridland.net  Thu Jul 21 09:39:01 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 1F34121F87A4; Thu, 21 Jul 2011 09:39:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.408
X-Spam-Level: 
X-Spam-Status: No, score=-2.408 tagged_above=-999 required=5 tests=[AWL=-0.109, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EGJI-5zF9LN3; Thu, 21 Jul 2011 09:39:00 -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 53E7521F876F; Thu, 21 Jul 2011 09:39:00 -0700 (PDT)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id DAC911168087; Thu, 21 Jul 2011 17:38: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 PUpCiRc-VMjP; Thu, 21 Jul 2011 17:38: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 11C3C1168067; Thu, 21 Jul 2011 17:38:49 +0100 (BST)
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com>
In-Reply-To: <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com>
MIME-Version: 1.0
Message-Id: <9031.1311266329.040274@puncture>
Date: Thu, 21 Jul 2011 17:38:49 +0100
From: Dave Cridland <dave@cridland.net>
To: David Endicott <dendicott@gmail.com>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>, =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
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: Thu, 21 Jul 2011 16:39:01 -0000

On Thu Jul 21 17:06:59 2011, David Endicott wrote:
> DNS resolution is not a function of a transport protocol. 

I entirely agree, but the specification already includes DNS  
resolution as part of URI resolution and URI scheme definition, and  
as such, if you want all these things - which are, I concur, not a  
function of a transport protocol - removed from this specification,  
then we'll need a distinct document which adds them back in, as it  
were.

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 john-ietf@jck.com  Thu Jul 21 10:00:04 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 E1D8721F888A for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 10:00:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.64
X-Spam-Level: 
X-Spam-Status: No, score=-102.64 tagged_above=-999 required=5 tests=[AWL=-0.041, 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 tsKa6SD43y4R for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 10:00:04 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 39E5A21F87FA for <ietf@ietf.org>; Thu, 21 Jul 2011 10:00:04 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QjwbT-000OE9-Ia; Thu, 21 Jul 2011 13:00:03 -0400
Date: Thu, 21 Jul 2011 13:00:02 -0400
From: John C Klensin <john-ietf@jck.com>
To: Harald Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
Message-ID: <C125CD63E1264E518A4C7423@PST.JCK.COM>
In-Reply-To: <4E27F407.8090006@alvestrand.no>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <BBB3AB81-1A20-4022-8687-CD88B000B281@bogus.com> <A6908373951C6911489DF57A@PST.JCK.COM> <71D5A97D-7119-4082-BC87-6505370CE800@bogus.com> <13205C286662DE4387D9AF3AC30EF456D3F3DEEA84@EMBX01-WF.jnpr.net> <C2C73F7968F19FEEF11B2C67@[192.168.1.128]> <E85A5A32-3665-4932-96A7-BADB11DDB2E8@sabahattin-gucukoglu.com> <4E25F868.1000109@dougbarton.us> <90D829BF-BB51-4B0E-B9A6-4C9CCA1D2840@sabahattin-gucukoglu.com> <4E27F407.8090006@alvestrand.no>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2011 17:00:05 -0000

--On Thursday, July 21, 2011 11:40 +0200 Harald Alvestrand
<harald@alvestrand.no> wrote:

>...
>> Actively being used.  In production.  So that taking it away
>> would hurt the entity using it, threaten the entity's comfort
>> and convenience, or just generally go against the stated
>> goals of making the Internet a better place for everybody
>> through the instrumentation and maintenance of standards.
> The idea that moving a standard to Historic would take away
> the ability of people to use it reminds me of the story from
> the Norwegian army, approx 1939:
> 
> - "If the enemy invades, how will you prevent them from using
> the train network?"
> - "Burn all the tickets, sir!"

I like this analogy.  The proposed action would have no effect
whatsoever on the behavior that one is trying to discourage.
But the move makes the party recommending the action look
ridiculous, ridiculous enough that the story of the
recommendation is still being told move than 70 years later.

     john






From dave@cridland.net  Thu Jul 21 10:40:06 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 AF9B521F8677; Thu, 21 Jul 2011 10:40:06 -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 Lv9l4TP7idea; Thu, 21 Jul 2011 10:40:06 -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 D2EAB21F850B; Thu, 21 Jul 2011 10:40:05 -0700 (PDT)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id 79DA91168087; Thu, 21 Jul 2011 18:40:03 +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 qNRHjsqhdbKV; Thu, 21 Jul 2011 18:40:00 +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 9780D1168067; Thu, 21 Jul 2011 18:40:00 +0100 (BST)
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com>
In-Reply-To: <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com>
MIME-Version: 1.0
Message-Id: <9031.1311270000.588511@puncture>
Date: Thu, 21 Jul 2011 18:40:00 +0100
From: Dave Cridland <dave@cridland.net>
To: David Endicott <dendicott@gmail.com>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>, Willy Tarreau <w@1wt.eu>
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: Thu, 21 Jul 2011 17:40:06 -0000

On Thu Jul 21 18:18:31 2011, David Endicott wrote:
> It is my opinion that name resolution (however done) is outside the  
> purview
> of WS.   It may be handled in any number of ways by the client, and  
> must
> happen *before* WS establishes it's TCP connection and begins  
> handshaking.

The URI scheme is defined here, and absolutely must explain whether  
it's a host (for direct address lookup), or a domain (for SRV).

It's proven impossible, despite effort, to retrofit SRV onto HTTP;  
there is no way it'll be possible to retrofit onto WS.

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 dave@cridland.net  Thu Jul 21 13:19:16 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 362E121F8A55; Thu, 21 Jul 2011 13:19:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.403
X-Spam-Level: 
X-Spam-Status: No, score=-2.403 tagged_above=-999 required=5 tests=[AWL=-0.104, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u6-w6mgFjOiP; Thu, 21 Jul 2011 13:19:15 -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 F062021F8915; Thu, 21 Jul 2011 13:19:14 -0700 (PDT)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id 83CF01168087; Thu, 21 Jul 2011 21:19:09 +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 GrXk6cjRLl1Z; Thu, 21 Jul 2011 21:19:06 +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 435071168067; Thu, 21 Jul 2011 21:19:06 +0100 (BST)
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <CALiegfnGkypkJYxUGGm3Tddgk3D0Ri=EWtN0WMChhEZN3Xsauw@mail.gmail.com> <CAP992=FrnDrCLgqZGUO9R2WkfgA2D+8TCau=6Xi+xa_u3CXT2w@mail.gmail.com>
In-Reply-To: <CAP992=FrnDrCLgqZGUO9R2WkfgA2D+8TCau=6Xi+xa_u3CXT2w@mail.gmail.com>
MIME-Version: 1.0
Message-Id: <9031.1311279546.247694@puncture>
Date: Thu, 21 Jul 2011 21:19:06 +0100
From: Dave Cridland <dave@cridland.net>
To: David Endicott <dendicott@gmail.com>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>, Willy Tarreau <w@1wt.eu>, =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
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: Thu, 21 Jul 2011 20:19:16 -0000

On Thu Jul 21 19:43:07 2011, David Endicott wrote:
> I do not know SIP or XMPP well enough to comment on why they  
> mandated the
> name resolution mechanisms they did.    However, XMPP is used in a  
> highly
> dynamic host environment, so having flexible & extensible name  
> resolution is
> likely an excellent choice.
> 
> 
I have no idea what you might mean by "highly dynamic host  
environment" in this context, but XMPP servers are normally found at  
the same location consistently. However, it is *not* always (or  
typically) the same location as a simple A record lookup:

;; ANSWER SECTION:
_xmpp-server._tcp.isode.com. 259200 IN	SRV	5 0 5269 xmpp.isode.com.

;; ADDITIONAL SECTION:
xmpp.isode.com.		225364	IN	A	62.3.217.250

;; ANSWER SECTION:
isode.com.		73130	IN	A	87.106.143.99

This property alone is very useful - in a websockets case this would  
mean being able to provide websockets services from a different host  
(or network) to the traditional web services in a simple manner,  
fully compatible with SOP.

The fact that this also allows cheap lightweight load balancing and  
fallback control is also useful in other cases; none of this relates  
to dynamic hosts, but simply richer service location.


> I do not oppose DNS's MX records for SMTP as email addresses are  
> name@domain,
> so obviously the Domain Name System is appropriate.    Also, I fail  
> to see
> why a mail admin should care how the SMTP clients arrive at the  
> server.  DNS
> MX is a reasonable solution, but there may be other methods, any  
> and all of
> which are irrelevant to the SMTP server.    Especially when the  
> SMTP server
> supports multiple email domains....
> 
> 
A mail admin does need to care *that* the service is located, and  
therefore will care *how* it is located.

You can be as theoretical as you like, by all means, but in practical  
terms, your email address (and my XMPP address) work because they use  
a defined, interoperable, service location mechanism, which operates  
via DNS record lookup.

(Also, I have no idea what multiple domains has to do with this.)


> Since WS is intended as a browser supported protocol, WS should  
> follow the
> same URI resolution mechanisms as HTTP (or how URI resolution is  
> done in
> general)  Having URLs that could resolve differently for a HTTP  
> request and
> a WS setup is a problem.
> 
> 
But they do resolve differently anyway. You don't get a page from a  
'ws' scheme URI, you get a transport protocol connection. This is  
good, indeed, it's kind of the point.

Your suggestion of "how URI resolution is done in general" is  
somewhat self-defeating, too, since aside from 'http' and 'https',  
there are 'mailto', which uses MX, 'sip' and 'xmpp', which both use  
SRV.

I think opponents of SRV records need to mount a stronger argument  
than the kind of luddite argument that if it's hard for one protocol  
in use by the browser, it should be hard for them all.

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 david.black@emc.com  Tue Jul 19 14:51:47 2011
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E61121F855B; Tue, 19 Jul 2011 14:51:47 -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 3VpV4FzduTV7; Tue, 19 Jul 2011 14:51:46 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 7579021F8532; Tue, 19 Jul 2011 14:51:46 -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 p6JLpcpF002562 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Jul 2011 17:51:38 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.253]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Tue, 19 Jul 2011 17:51:28 -0400
Received: from mxhub04.corp.emc.com (mxhub04.corp.emc.com [10.254.141.106]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p6JLpROO018677; Tue, 19 Jul 2011 17:51:28 -0400
Received: from mx14a.corp.emc.com ([169.254.1.245]) by mxhub04.corp.emc.com ([10.254.141.106]) with mapi; Tue, 19 Jul 2011 17:51:27 -0400
From: <david.black@emc.com>
To: <c.raiciu@cs.ucl.ac.uk>
Date: Tue, 19 Jul 2011 17:51:25 -0400
Subject: RE: tsv-dir review of draft-ietf-mptcp-congestion-05
Thread-Topic: tsv-dir review of draft-ietf-mptcp-congestion-05
Thread-Index: AcxGMfH1yDA0GmMkRMaHlLDxny9PDQAK3j1w
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E058948B636@MX14A.corp.emc.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E05893924C1@MX14A.corp.emc.com> <7629FCE9-548E-404B-816D-7D04AD65D29D@cs.ucl.ac.uk>
In-Reply-To: <7629FCE9-548E-404B-816D-7D04AD65D29D@cs.ucl.ac.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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Thu, 21 Jul 2011 14:33:03 -0700
Cc: ietf@ietf.org, multipathtcp@ietf.org, david.black@emc.com, tsv-area@ietf.org, m.handley@cs.ucl.ac.uk, d.wischik@cs.ucl.ac.uk, 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, 19 Jul 2011 21:51:47 -0000

Costin,

The proposed -06 version sufficiently clarifies my one open issue.

I agree that the NSDI paper is an important citation and did not intend to
suggest that it be removed.  In addition, your decision to not cite RFC 312=
4
is ok with me.

Thank you for responding to the review.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------

> -----Original Message-----
> From: Costin Raiciu [mailto:c.raiciu@cs.ucl.ac.uk]
> Sent: Tuesday, July 19, 2011 12:35 PM
> To: Black, David
> Cc: tsv-dir; tsv-area; ietf; m.handley; d.wischik; multipathtcp
> Subject: Re: tsv-dir review of draft-ietf-mptcp-congestion-05
>=20
> Hi David,
>=20
> Thank you for your review.
>=20
> > Major:
> >
> > I have one open issue - the first two goals (in the Introduction) are t=
o have multipath
> > TCP connections behave somewhat like single-path connections in terms o=
f effects on
> > (fairness to) other traffic.  The algorithm specified accomplishes this=
 solely by
> > coupling the additive increase functionality across the flows, but allo=
wing each flow
> > to react to drops and congestion separately (no decrease coupling).  Th=
e draft does
> > not explain why increase coupling alone is sufficient to achieve these =
goals or what
> > compromise to the goals results from only coupling increases.
>=20
> Our proposal fully achieves goals 1 and 2 - fairness to single path tcp  =
and improve throughput. It
> does not fully achieve goal three - balancing congestion; fully achieving=
 goal 3 is very difficult,
> and an explanation is attempted in section 5; a reference is given to the=
 NSDI paper for further info.
>=20
> > Section 5 is a good start on this discussion, but it's not clear about =
what compromises
> > to the goals results from increase coupling only.  Section 5 criticizes=
 an alternative
> > that couples both increases and decreases for failing to achieve Goal 1=
, but doesn't
> > say what this approach achieves.  At most a few additional sentences in=
 Section 5 should
> > suffice to address this concern, and Section 2 should be edited to alig=
n with the
> > changes to Section 5.
>=20
> We have updated section 5 to make these points clear - they weren't clear=
 enough before.
>=20
> > Minor:
> >
> > While the [NSDI] paper is a fine place to reference work published in c=
onferences
> > and/or journals, RFC 3124 on the Congestion Manager is related IETF wor=
k and should
> > be cited here as an Informative Reference.
>=20
> The congestion manager is indeed related work and should be cited in a re=
search paper, but does not
> help understanding the congestion controller presented in this draft. We =
chose not to cite it
> explicitly.
>=20
> We chose to cite the NSDI paper because it describes in detail the design=
 choices that shaped the
> algorithm, and it will help an interested reader understand more about th=
e algorithm.
> The discussion section is itself a short high level summary of those deci=
sions.
>=20
> We attach the new version of this draft to this email (we cannot post a n=
ew version online of the
> draft because the IETF submission cutoff date has passed). Could you plea=
se check the draft and see if
> the issues you raised have been clarified?
>=20
> We will post the draft as soon as submissions reopen after the IETF
>=20
> Thanks,
> Costin

From lars.eggert@nokia.com  Tue Jul 19 17:01:37 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 A31B521F85A8; Tue, 19 Jul 2011 17:01:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.756
X-Spam-Level: 
X-Spam-Status: No, score=-102.756 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oTzkBfiZvgpv; Tue, 19 Jul 2011 17:01:33 -0700 (PDT)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by ietfa.amsl.com (Postfix) with ESMTP id AA87A21F85A4; Tue, 19 Jul 2011 17:01:33 -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 p6K01VUv020268 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Jul 2011 03:01:32 +0300
From: Lars Eggert <lars.eggert@nokia.com>
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.97.1 at fit.nokia.com
Content-Type: multipart/signed; boundary=Apple-Mail-14--47083450; protocol="application/pkcs7-signature"; micalg=sha1
Subject: Preliminary Agenda: IRTF Open Meeting at IETF-81
Date: Tue, 19 Jul 2011 20:01:21 -0400
Message-Id: <4B56B390-1EAF-4BAC-A542-DAD360FF4583@nokia.com>
To: irtf-discuss@irtf.org, irtf-announce@irtf.org, irsg@irtf.org, 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); Wed, 20 Jul 2011 03:01:24 +0300 (EEST)
X-Nokia-AV: Clean
X-Mailman-Approved-At: Thu, 21 Jul 2011 14:33:03 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: irtf-discuss@irtf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2011 00:01:37 -0000

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


*PRELIMINARY* Agenda
IRTF Open Meeting
Quebec City, Canada
July 11, 2011, 9:00 - 11:30 (tentative)

Will be uploaded to the datatracker as soon as I have access rights.
Slot lengths below indicate presentation+discussion time.


State of the IRTF
	Lars Eggert
	10+5 min


Applied Networking Prize (ANRP) Awards
	2x 20+10 min

	*** Beichuan Zhang *** for research into =93green=94 traffic =
engineering:
	GreenTE: Power-Aware Traffic Engineering. Mingui Zhang,
	Cheng Yi, Bin Liu and Beichuan Zhang. Proc. IEEE International
	Conference on Network Protocols (ICNP), pp. 21=9630, October =
2010.

	Abstract: Given the high path redundancy and low link
	utilization in today's large networks, one may route traffic
	using fewer number of links so that other links can go sleep
	to conserve energy. In this work we design a traffic engineering
	mechanism that maximizes the number of links to sleep under
	certain performance constraints such as link utilization and =
packet
	delay. Using network topologies and traffic data from several
	wide-area networks, our evaluation demonstrates that GreenTE is
	both feasible and beneficial.

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

	A Technique for Reducing BGP Update Announcements through Path
	Exploration Damping. Geoff Huston, Mattia Rossi and Grenville
	Armitage. IEEE Journal on Selected Areas in Communications =
(JSAC),
	Vol. 28, No. 8, pp. 1271=961286, October 2010.
=20
	Abstract: Path Exploration Damping is intended as a replacement
	for MRAI and RFD, the two main mechanisms used in BGP that aim
	at a reduction of BGP update churn. This talk explains the
	motivation behind PED, outlines the algorithm and provides
	insight into experimental results.


Presentation & discussion of proposals for new IRTF research groups

	Network Complexity
	Michael Beringer
	http://networkcomplexity.org/
	10+10 min
=09
	Information-Centric Networking
	Dirk Kutscher & B=F6rje Ohlman
	http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg
	10+10 min
=09
	Learning-Capable Communication Networks
	Dimitri Papadimitriou =20
	https://sites.google.com/site/lccngroup/
	10+10 min
=09
=09=

--Apple-Mail-14--47083450
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
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDcyMDAwMDEyMlowIwYJKoZIhvcNAQkE
MRYEFFUfsdoZu1wvnb+CB8xnB62oJ9PpMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
ACXaQMpFGn+zfCUbU56kvPb/C0EpACtkB6qBwNJBJJ2phew850CuG6FTpMvchExfMAS0ch2QzzO8
6VgMFeMPvNHep1RIt2gVPlawBcxuUF4IhauOGWmZ0oSPlEnY3So1ITpud+V5XgJKLfC4Dzro4BXE
jHNcEKIXx/i0/+c0n7ZmI70BmS0Cd+9+0EZ7Tp/coEve6b24sd/I7c8E30/jrIfXPiZpV/G6T3TP
DEwdvglkzbRuJ+gmiuEWoOheL0WdsM0Ih2i79F9O/7aW8tt68Xc/CfheXHOrxbyzKMYF06KoGIMp
kcJKWvfAHF4VDfGQV5vPbOnKYQF0DT51lOxhDQUAAAAAAAA=

--Apple-Mail-14--47083450--

From ibc@aliax.net  Wed Jul 20 14:13:04 2011
Return-Path: <ibc@aliax.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C032A21F858D; Wed, 20 Jul 2011 14:13:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.668
X-Spam-Level: 
X-Spam-Status: No, score=-2.668 tagged_above=-999 required=5 tests=[AWL=0.009,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 z9X-Imp+LYnn; Wed, 20 Jul 2011 14:12:53 -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 9ABA321F851A; Wed, 20 Jul 2011 14:12:53 -0700 (PDT)
Received: by qyk9 with SMTP id 9so3790574qyk.10 for <multiple recipients>; Wed, 20 Jul 2011 14:12:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.105.95 with SMTP id s31mr7305586qco.228.1311196373066; Wed, 20 Jul 2011 14:12:53 -0700 (PDT)
Received: by 10.229.185.195 with HTTP; Wed, 20 Jul 2011 14:12:52 -0700 (PDT)
In-Reply-To: <9031.1311082001.631622@puncture>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture>
Date: Wed, 20 Jul 2011 23:12:52 +0200
Message-ID: <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Dave Cridland <dave@cridland.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 21 Jul 2011 14:33:02 -0700
Cc: Server-Initiated HTTP <hybi@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, 20 Jul 2011 21:13:05 -0000

2011/7/19 Dave Cridland <dave@cridland.net>:
>> Hi, I assume there is no interest in making DNS SRV mechanism exposed
>> in http://tools.ietf.org/html/draft-ibc-websocket-dns-srv-02 part of
>> the WebSocket core specification, neither referencing it (in the same
>> way RFC 3261 "SIP protocol" mandates the usage of RFC 3263 "Locating
>> SIP servers").
>>
>> As said before, making such DNS SRV specification an extension (so
>> present in other document) will mean no success at all, as WebSocket
>> client implementors (i.e. webbrowser vendors) will not be mandated to
>> implement it and service providers could not rely on the support of
>> DNS SRV in web browsers. So nobody will use them (because IE10 decided
>> not to implement it, for example). IMHO this is sad due the real
>> advantages DNS SRV provides for a protocol like WebSocket.
>>
>> Yes, in HTTP there is no special DNS stuff, all the load-balancing and
>> failover mechanism are done at server side with very complex and
>> expensive solutions (www.facebook.com resolves to a single IPv4 !!!!).
>> The question is: should we also inherit every HTTP limitation in
>> WebSocket?
>
> I agree wholeheartedly with this, and strongly recommend that mandatory u=
se
> of SRV is included in the core protocol.
>
> I think with HTTP's very short lived requests, then it's possible to work
> around the lack of SRV support (at a cost), but the benefit is markedly
> higher with the long-lived, stateful sessions we're anticipating with
> WebSocket.


Unfortunaltely it seems that the debate about DNS SRV support does not
interest to the core WG authors. I would like, at least, to receive
good arguments not to include/mandate DNS SRV support in the draft. If
not, the proposal is just being ignored with no reason.

Regards.


--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From dendicott@gmail.com  Thu Jul 21 09:07:02 2011
Return-Path: <dendicott@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 155B321F89B8; Thu, 21 Jul 2011 09:07:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.448
X-Spam-Level: 
X-Spam-Status: No, score=-3.448 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 3QllEeBxwjex; Thu, 21 Jul 2011 09:07:01 -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 BC8F321F898F; Thu, 21 Jul 2011 09:07:00 -0700 (PDT)
Received: by wwe5 with SMTP id 5so949103wwe.13 for <multiple recipients>; Thu, 21 Jul 2011 09:06:59 -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=h8z57ttMAhThF8Rtr5IrPUmU/xRh9YunRRIrd61xPEg=; b=jfwb993X5RivII7UnG++fY7iad1GnMqHX5iqknJKS/nkzWRtq7W8aWBfKFZSdOScA0 cZsR2mrCEBpawpyP8WomOD12Zv5F64YebxcukO6xb9PGxT/qTPdlAg9uZYNY/ybc/GYO dl4SR5RY1IUUb9Kgv4mFc+ewiYz6FuvWDVlm8=
MIME-Version: 1.0
Received: by 10.216.63.21 with SMTP id z21mr1029991wec.3.1311264419703; Thu, 21 Jul 2011 09:06:59 -0700 (PDT)
Received: by 10.216.39.197 with HTTP; Thu, 21 Jul 2011 09:06:59 -0700 (PDT)
In-Reply-To: <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com>
Date: Thu, 21 Jul 2011 12:06:59 -0400
Message-ID: <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: David Endicott <dendicott@gmail.com>
To: =?ISO-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
Content-Type: multipart/alternative; boundary=000e0cd3b54ef16b5c04a8968927
X-Mailman-Approved-At: Thu, 21 Jul 2011 14:33:02 -0700
Cc: Server-Initiated HTTP <hybi@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, 21 Jul 2011 16:07:02 -0000

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

I am opposed to inclusion in core specification.  I would accept it as
optional extension.

DNS resolution is not a function of a transport protocol.  DNS SRV has no
special association with WS.    It is my opinion that this would be
additional cruft that is only marginally related to the purpose and functio=
n
of websockets.    It does not address a general use case.   DNS SRV applies
only to a (small?) subset of server-side implementations.    It is a good
and useful mechanism, but I do not believe it should be tied tightly to
websockets, nor included as part of the core spec.


On Wed, Jul 20, 2011 at 5:12 PM, I=F1aki Baz Castillo <ibc@aliax.net> wrote=
:

> 2011/7/19 Dave Cridland <dave@cridland.net>:
> >> Hi, I assume there is no interest in making DNS SRV mechanism exposed
> >> in http://tools.ietf.org/html/draft-ibc-websocket-dns-srv-02 part of
> >> the WebSocket core specification, neither referencing it (in the same
> >> way RFC 3261 "SIP protocol" mandates the usage of RFC 3263 "Locating
> >> SIP servers").
> >>
> >> As said before, making such DNS SRV specification an extension (so
> >> present in other document) will mean no success at all, as WebSocket
> >> client implementors (i.e. webbrowser vendors) will not be mandated to
> >> implement it and service providers could not rely on the support of
> >> DNS SRV in web browsers. So nobody will use them (because IE10 decided
> >> not to implement it, for example). IMHO this is sad due the real
> >> advantages DNS SRV provides for a protocol like WebSocket.
> >>
> >> Yes, in HTTP there is no special DNS stuff, all the load-balancing and
> >> failover mechanism are done at server side with very complex and
> >> expensive solutions (www.facebook.com resolves to a single IPv4 !!!!).
> >> The question is: should we also inherit every HTTP limitation in
> >> WebSocket?
> >
> > I agree wholeheartedly with this, and strongly recommend that mandatory
> use
> > of SRV is included in the core protocol.
> >
> > I think with HTTP's very short lived requests, then it's possible to wo=
rk
> > around the lack of SRV support (at a cost), but the benefit is markedly
> > higher with the long-lived, stateful sessions we're anticipating with
> > WebSocket.
>
>
> Unfortunaltely it seems that the debate about DNS SRV support does not
> interest to the core WG authors. I would like, at least, to receive
> good arguments not to include/mandate DNS SRV support in the draft. If
> not, the proposal is just being ignored with no reason.
>
> Regards.
>
>
> --
> I=F1aki Baz Castillo
> <ibc@aliax.net>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>

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

I am opposed to inclusion in core specification. =A0I would accept it as op=
tional=A0extension.<div><br></div><div>DNS resolution is not a function of =
a transport protocol. =A0DNS SRV has no special association with WS. =A0 =
=A0It is my opinion that this would be additional cruft that is only margin=
ally related to the purpose and function of websockets. =A0 =A0It does not =
address a general use case. =A0 DNS SRV applies only to a (small?) subset o=
f server-side implementations. =A0 =A0It is a good and useful mechanism, bu=
t I do not believe it should be tied tightly to websockets, nor included as=
 part of the core spec.</div>
<div><br><br><div class=3D"gmail_quote">On Wed, Jul 20, 2011 at 5:12 PM, I=
=F1aki Baz Castillo <span dir=3D"ltr">&lt;<a href=3D"mailto:ibc@aliax.net">=
ibc@aliax.net</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;">
2011/7/19 Dave Cridland &lt;<a href=3D"mailto:dave@cridland.net">dave@cridl=
and.net</a>&gt;:<br>
<div class=3D"im">&gt;&gt; Hi, I assume there is no interest in making DNS =
SRV mechanism exposed<br>
&gt;&gt; in <a href=3D"http://tools.ietf.org/html/draft-ibc-websocket-dns-s=
rv-02" target=3D"_blank">http://tools.ietf.org/html/draft-ibc-websocket-dns=
-srv-02</a> part of<br>
&gt;&gt; the WebSocket core specification, neither referencing it (in the s=
ame<br>
&gt;&gt; way RFC 3261 &quot;SIP protocol&quot; mandates the usage of RFC 32=
63 &quot;Locating<br>
&gt;&gt; SIP servers&quot;).<br>
&gt;&gt;<br>
&gt;&gt; As said before, making such DNS SRV specification an extension (so=
<br>
&gt;&gt; present in other document) will mean no success at all, as WebSock=
et<br>
&gt;&gt; client implementors (i.e. webbrowser vendors) will not be mandated=
 to<br>
&gt;&gt; implement it and service providers could not rely on the support o=
f<br>
&gt;&gt; DNS SRV in web browsers. So nobody will use them (because IE10 dec=
ided<br>
&gt;&gt; not to implement it, for example). IMHO this is sad due the real<b=
r>
&gt;&gt; advantages DNS SRV provides for a protocol like WebSocket.<br>
&gt;&gt;<br>
&gt;&gt; Yes, in HTTP there is no special DNS stuff, all the load-balancing=
 and<br>
&gt;&gt; failover mechanism are done at server side with very complex and<b=
r>
&gt;&gt; expensive solutions (<a href=3D"http://www.facebook.com" target=3D=
"_blank">www.facebook.com</a> resolves to a single IPv4 !!!!).<br>
&gt;&gt; The question is: should we also inherit every HTTP limitation in<b=
r>
&gt;&gt; WebSocket?<br>
&gt;<br>
&gt; I agree wholeheartedly with this, and strongly recommend that mandator=
y use<br>
&gt; of SRV is included in the core protocol.<br>
&gt;<br>
&gt; I think with HTTP&#39;s very short lived requests, then it&#39;s possi=
ble to work<br>
&gt; around the lack of SRV support (at a cost), but the benefit is markedl=
y<br>
&gt; higher with the long-lived, stateful sessions we&#39;re anticipating w=
ith<br>
&gt; WebSocket.<br>
<br>
<br>
</div>Unfortunaltely it seems that the debate about DNS SRV support does no=
t<br>
interest to the core WG authors. I would like, at least, to receive<br>
good arguments not to include/mandate DNS SRV support in the draft. If<br>
not, the proposal is just being ignored with no reason.<br>
<br>
Regards.<br>
<div class=3D"im"><br>
<br>
--<br>
I=F1aki Baz Castillo<br>
&lt;<a href=3D"mailto:ibc@aliax.net">ibc@aliax.net</a>&gt;<br>
_______________________________________________<br>
</div><div><div></div><div class=3D"h5">hybi mailing list<br>
<a href=3D"mailto:hybi@ietf.org">hybi@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/hybi" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/hybi</a><br>
</div></div></blockquote></div><br></div>

--000e0cd3b54ef16b5c04a8968927--

From ibc@aliax.net  Thu Jul 21 09:27:51 2011
Return-Path: <ibc@aliax.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0072821F858C; Thu, 21 Jul 2011 09:27:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.668
X-Spam-Level: 
X-Spam-Status: No, score=-2.668 tagged_above=-999 required=5 tests=[AWL=0.009,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 l3X08BxdMVV0; Thu, 21 Jul 2011 09:27:50 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id F178F21F856D; Thu, 21 Jul 2011 09:27:49 -0700 (PDT)
Received: by qyk29 with SMTP id 29so1040769qyk.10 for <multiple recipients>; Thu, 21 Jul 2011 09:27:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.44.36 with SMTP id y36mr390245qce.227.1311265669336; Thu, 21 Jul 2011 09:27:49 -0700 (PDT)
Received: by 10.229.185.195 with HTTP; Thu, 21 Jul 2011 09:27:49 -0700 (PDT)
In-Reply-To: <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com>
Date: Thu, 21 Jul 2011 18:27:49 +0200
Message-ID: <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: David Endicott <dendicott@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 21 Jul 2011 14:33:02 -0700
Cc: Server-Initiated HTTP <hybi@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, 21 Jul 2011 16:27:51 -0000

2011/7/21 David Endicott <dendicott@gmail.com>:
> DNS resolution is not a function of a transport protocol. =C2=A0DNS SRV h=
as no
> special association with WS. =C2=A0 =C2=A0It is my opinion that this woul=
d be
> additional cruft that is only marginally related to the purpose and funct=
ion
> of websockets. =C2=A0 =C2=A0It does not address a general use case. =C2=
=A0 DNS SRV applies
> only to a (small?) subset of server-side implementations. =C2=A0 =C2=A0It=
 is a good
> and useful mechanism, but I do not believe it should be tied tightly to
> websockets, nor included as part of the core spec.

An WebSocket URI is given to a WebSocket client, and the client MUST
locate the corresponding WS server, right? and for locating the server
the client MUST follows a procedures which, for now, involve (if it's
not an IP) DNS A/AAAA resolution, right? So now imagine that the
location mechanism is a bit more powerful and also involves SRV
queries (not always).

If you think that a transport protocol (like WebSocket) must not
resolve a server destination then also remove the WS URI inspection
and resolution from the core spec, don't you agree? or just DNS A/AAA
is valid?

I don't agree with your opinion at all. Regards.



--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From w@1wt.eu  Thu Jul 21 09:39:21 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C094F21F8A55; Thu, 21 Jul 2011 09:39:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.534
X-Spam-Level: 
X-Spam-Status: No, score=-5.534 tagged_above=-999 required=5 tests=[AWL=-3.791, BAYES_00=-2.599, HELO_IS_SMALL6=0.556, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nuqn+XXjkC52; Thu, 21 Jul 2011 09:39:21 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 85A8521F8A30; Thu, 21 Jul 2011 09:39:20 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6LGdAtf016954; Thu, 21 Jul 2011 18:39:10 +0200
Date: Thu, 21 Jul 2011 18:39:10 +0200
From: Willy Tarreau <w@1wt.eu>
To: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110721163910.GA16854@1wt.eu>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Thu, 21 Jul 2011 14:33:03 -0700
Cc: Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>, David Endicott <dendicott@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2011 16:39:21 -0000

On Thu, Jul 21, 2011 at 06:27:49PM +0200, Iñaki Baz Castillo wrote:
> 2011/7/21 David Endicott <dendicott@gmail.com>:
> > DNS resolution is not a function of a transport protocol.  DNS SRV has no
> > special association with WS.    It is my opinion that this would be
> > additional cruft that is only marginally related to the purpose and function
> > of websockets.    It does not address a general use case.   DNS SRV applies
> > only to a (small?) subset of server-side implementations.    It is a good
> > and useful mechanism, but I do not believe it should be tied tightly to
> > websockets, nor included as part of the core spec.
> 
> An WebSocket URI is given to a WebSocket client, and the client MUST
> locate the corresponding WS server, right? and for locating the server
> the client MUST follows a procedures which, for now, involve (if it's
> not an IP) DNS A/AAAA resolution, right? So now imagine that the
> location mechanism is a bit more powerful and also involves SRV
> queries (not always).
> 
> If you think that a transport protocol (like WebSocket) must not
> resolve a server destination then also remove the WS URI inspection
> and resolution from the core spec, don't you agree? or just DNS A/AAA
> is valid?
> 
> I don't agree with your opinion at all. Regards.

Iñaki,

I understand the point David is making. DNS is something independant of
WS and conversely. It is one way of resolving addresses, just like there
will be people using hosts files. At no place the protocol specification
dictates how a client should resolve a name to an IP address. The protocol
specifies the transport part only.

This is the same for other protocols. For instance, neither FTP nor HTTP
explain how a client is supposed to resolve a host name, still the later
explains how to parse a URI. DNS SRV is a DNS extension which only concerns
resolvers. Not all clients will be using resolvers, just a part of them.
Some others will simply forward the request to their HTTP proxy which will
apply whatever DNS resolving method they know, including possibly DNS SRV.

In practice, if there are new elements of DNS SRV that are specific to WS,
they should probably be added to the DNS SRV spec and not the WS spec.
Maybe the WS spec should mention that it addresses transport only and
not address resolving. It may recommend to follow some principles to
perform the resolving but should not specify how to do it.

Hoping it's a bit clearer,
Willy


From ibc@aliax.net  Thu Jul 21 10:15:15 2011
Return-Path: <ibc@aliax.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6A3921F874C; Thu, 21 Jul 2011 10:15:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.669
X-Spam-Level: 
X-Spam-Status: No, score=-2.669 tagged_above=-999 required=5 tests=[AWL=0.008,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 NykDk76jRSDV; Thu, 21 Jul 2011 10:15:15 -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 048D821F84E0; Thu, 21 Jul 2011 10:15:14 -0700 (PDT)
Received: by qyk9 with SMTP id 9so4401456qyk.10 for <multiple recipients>; Thu, 21 Jul 2011 10:15:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.66.25 with SMTP id l25mr440360qci.265.1311268514022; Thu, 21 Jul 2011 10:15:14 -0700 (PDT)
Received: by 10.229.185.195 with HTTP; Thu, 21 Jul 2011 10:15:13 -0700 (PDT)
In-Reply-To: <20110721163910.GA16854@1wt.eu>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu>
Date: Thu, 21 Jul 2011 19:15:13 +0200
Message-ID: <CALiegfkk8G6_KE-KfL_RuF96NUbF6yZgcFfsNGtLoAr2=jcYjg@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Willy Tarreau <w@1wt.eu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 21 Jul 2011 14:33:02 -0700
Cc: Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>, David Endicott <dendicott@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2011 17:15:15 -0000

2011/7/21 Willy Tarreau <w@1wt.eu>:
> I understand the point David is making. DNS is something independant of
> WS and conversely. It is one way of resolving addresses, just like there
> will be people using hosts files. At no place the protocol specification
> dictates how a client should resolve a name to an IP address. The protoco=
l
> specifies the transport part only.

Host files just replace A/AAAA resolution. Still is possible to query
SRV records and later perform hostfiles check for retrieved hostnames
(instead of performing DNS A/AAAA for them).


> This is the same for other protocols. For instance, neither FTP nor HTTP
> explain how a client is supposed to resolve a host name, still the later
> explains how to parse a URI.

Maybe because DNS SRV born later than FTP or HTTP. But now look at SIP
and XMPP protocols which make *extensive* usage of DNS SRV. And SIP is
just a "signaling protocol", you could also consider it a "transport
protocol" which transports sessions and other kind of data. It's at
the very same level than WS, IMHO.



> DNS SRV is a DNS extension which only concerns
> resolvers. Not all clients will be using resolvers, just a part of them.
> Some others will simply forward the request to their HTTP proxy which wil=
l
> apply whatever DNS resolving method they know, including possibly DNS SRV=
.

If WS spec does not mandate DNS SRV resolution in WS clients (so
webbrowsers mainly) then let's forget SRV balancing/failover
capabilities. If the WS core draft does not want to handle this topic,
then refer to another document mandating it (in the same way SIP RFC
3261 mandates the usage of DNS NAPTR/SRV in RFC 3263 for SIP clients).

So you can split WS in:
- transport specification RFC (handshake, frames and so).
- location WS servers (a MUST for WS clients when resolving WS URI's).


> In practice, if there are new elements of DNS SRV that are specific to WS=
,
> they should probably be added to the DNS SRV spec and not the WS spec.

No. DNS SRV spec (RFC 2782) just explains the DNS SRV mechanism. Any
protocol can decide wheter to include/mandate it or not. Each protocol
can register in IANA new "service" values SRV, in the same way SIP and
XMPP RFC's create "sip" and "xmpp-server" values.


> Maybe the WS spec should mention that it addresses transport only and
> not address resolving. It may recommend to follow some principles to
> perform the resolving but should not specify how to do it.

That would be great, so another document/spec would *mandate* how WS
clients MUST resolve WS destinations. But that is not true now as WS
core spec states simple A/AAAA resolution for locating a WS server.


Regards.


--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From dendicott@gmail.com  Thu Jul 21 10:18:34 2011
Return-Path: <dendicott@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F337521F8770; Thu, 21 Jul 2011 10:18:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.586
X-Spam-Level: 
X-Spam-Status: No, score=-3.586 tagged_above=-999 required=5 tests=[AWL=0.012,  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 TB+hTqshj2hr; Thu, 21 Jul 2011 10:18:33 -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 97E7221F876A; Thu, 21 Jul 2011 10:18:32 -0700 (PDT)
Received: by wyj26 with SMTP id 26so1146003wyj.31 for <multiple recipients>; Thu, 21 Jul 2011 10:18:31 -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=JnYrzouHZYlzhVl0Vgf3xfIZaBJjTwbFMjRYY7s4Ots=; b=ZfSqk3IhD2j0wqbkOu5P2VTBh9IUcI4nvxT4T98c69Z1TraGouJZri3XQtPBRf7r93 jncBqB3JgmnJkXjJ6LGyrtmDAZapfPYcnCTJduE9yDar/YeTbNtF5hOemFkoZXpXkCwl qlUF+5hxUsXrcIysZJvUFM9olRAK3HLKjqSJA=
MIME-Version: 1.0
Received: by 10.216.63.21 with SMTP id z21mr1098023wec.3.1311268711646; Thu, 21 Jul 2011 10:18:31 -0700 (PDT)
Received: by 10.216.39.197 with HTTP; Thu, 21 Jul 2011 10:18:31 -0700 (PDT)
In-Reply-To: <20110721163910.GA16854@1wt.eu>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu>
Date: Thu, 21 Jul 2011 13:18:31 -0400
Message-ID: <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: David Endicott <dendicott@gmail.com>
To: Willy Tarreau <w@1wt.eu>
Content-Type: multipart/alternative; boundary=000e0cd3b54ec3487a04a897891d
X-Mailman-Approved-At: Thu, 21 Jul 2011 14:33:03 -0700
Cc: =?ISO-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>, Server-Initiated HTTP <hybi@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, 21 Jul 2011 17:18:34 -0000

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

Thanks Willy, you made my point better than I did.

It is my opinion that name resolution (however done) is outside the purview
of WS.   It may be handled in any number of ways by the client, and must
happen *before* WS establishes it's TCP connection and begins handshaking.

DNS, DNS SRV, etc. are good and useful tools, but are not part of WS.

A document showing how to use DNS SRV with WS would be useful, but it's not
part of the core WS spec.


On Thu, Jul 21, 2011 at 12:39 PM, Willy Tarreau <w@1wt.eu> wrote:

> On Thu, Jul 21, 2011 at 06:27:49PM +0200, I=F1aki Baz Castillo wrote:
> > 2011/7/21 David Endicott <dendicott@gmail.com>:
> > > DNS resolution is not a function of a transport protocol.  DNS SRV ha=
s
> no
> > > special association with WS.    It is my opinion that this would be
> > > additional cruft that is only marginally related to the purpose and
> function
> > > of websockets.    It does not address a general use case.   DNS SRV
> applies
> > > only to a (small?) subset of server-side implementations.    It is a
> good
> > > and useful mechanism, but I do not believe it should be tied tightly =
to
> > > websockets, nor included as part of the core spec.
> >
> > An WebSocket URI is given to a WebSocket client, and the client MUST
> > locate the corresponding WS server, right? and for locating the server
> > the client MUST follows a procedures which, for now, involve (if it's
> > not an IP) DNS A/AAAA resolution, right? So now imagine that the
> > location mechanism is a bit more powerful and also involves SRV
> > queries (not always).
> >
> > If you think that a transport protocol (like WebSocket) must not
> > resolve a server destination then also remove the WS URI inspection
> > and resolution from the core spec, don't you agree? or just DNS A/AAA
> > is valid?
> >
> > I don't agree with your opinion at all. Regards.
>
> I=F1aki,
>
> I understand the point David is making. DNS is something independant of
> WS and conversely. It is one way of resolving addresses, just like there
> will be people using hosts files. At no place the protocol specification
> dictates how a client should resolve a name to an IP address. The protoco=
l
> specifies the transport part only.
>
> This is the same for other protocols. For instance, neither FTP nor HTTP
> explain how a client is supposed to resolve a host name, still the later
> explains how to parse a URI. DNS SRV is a DNS extension which only concer=
ns
> resolvers. Not all clients will be using resolvers, just a part of them.
> Some others will simply forward the request to their HTTP proxy which wil=
l
> apply whatever DNS resolving method they know, including possibly DNS SRV=
.
>
> In practice, if there are new elements of DNS SRV that are specific to WS=
,
> they should probably be added to the DNS SRV spec and not the WS spec.
> Maybe the WS spec should mention that it addresses transport only and
> not address resolving. It may recommend to follow some principles to
> perform the resolving but should not specify how to do it.
>
> Hoping it's a bit clearer,
> Willy
>
>

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

Thanks Willy, you made my point better than I did.<div><br></div><div>It is=
 my opinion that name resolution (however done) is outside the=A0purview of=
 WS. =A0 It may be handled in any number of ways by the client, and must ha=
ppen *before* WS establishes=A0it&#39;s TCP connection and begins handshaki=
ng.</div>
<div><br></div><div>DNS, DNS SRV, etc. are good and useful tools, but are n=
ot part of WS.</div><div><br></div><div>A document showing how to use DNS S=
RV with WS would be useful, but it&#39;s not part of the core WS spec.</div=
>
<div><br><br><div class=3D"gmail_quote">On Thu, Jul 21, 2011 at 12:39 PM, W=
illy Tarreau <span dir=3D"ltr">&lt;<a href=3D"mailto:w@1wt.eu">w@1wt.eu</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><div></div><div class=3D"h5">On Thu, Jul 21, 2011 at 06:27:49PM +0200,=
 I=F1aki Baz Castillo wrote:<br>
&gt; 2011/7/21 David Endicott &lt;<a href=3D"mailto:dendicott@gmail.com">de=
ndicott@gmail.com</a>&gt;:<br>
&gt; &gt; DNS resolution is not a function of a transport protocol. =A0DNS =
SRV has no<br>
&gt; &gt; special association with WS. =A0 =A0It is my opinion that this wo=
uld be<br>
&gt; &gt; additional cruft that is only marginally related to the purpose a=
nd function<br>
&gt; &gt; of websockets. =A0 =A0It does not address a general use case. =A0=
 DNS SRV applies<br>
&gt; &gt; only to a (small?) subset of server-side implementations. =A0 =A0=
It is a good<br>
&gt; &gt; and useful mechanism, but I do not believe it should be tied tigh=
tly to<br>
&gt; &gt; websockets, nor included as part of the core spec.<br>
&gt;<br>
&gt; An WebSocket URI is given to a WebSocket client, and the client MUST<b=
r>
&gt; locate the corresponding WS server, right? and for locating the server=
<br>
&gt; the client MUST follows a procedures which, for now, involve (if it&#3=
9;s<br>
&gt; not an IP) DNS A/AAAA resolution, right? So now imagine that the<br>
&gt; location mechanism is a bit more powerful and also involves SRV<br>
&gt; queries (not always).<br>
&gt;<br>
&gt; If you think that a transport protocol (like WebSocket) must not<br>
&gt; resolve a server destination then also remove the WS URI inspection<br=
>
&gt; and resolution from the core spec, don&#39;t you agree? or just DNS A/=
AAA<br>
&gt; is valid?<br>
&gt;<br>
&gt; I don&#39;t agree with your opinion at all. Regards.<br>
<br>
</div></div>I=F1aki,<br>
<br>
I understand the point David is making. DNS is something independant of<br>
WS and conversely. It is one way of resolving addresses, just like there<br=
>
will be people using hosts files. At no place the protocol specification<br=
>
dictates how a client should resolve a name to an IP address. The protocol<=
br>
specifies the transport part only.<br>
<br>
This is the same for other protocols. For instance, neither FTP nor HTTP<br=
>
explain how a client is supposed to resolve a host name, still the later<br=
>
explains how to parse a URI. DNS SRV is a DNS extension which only concerns=
<br>
resolvers. Not all clients will be using resolvers, just a part of them.<br=
>
Some others will simply forward the request to their HTTP proxy which will<=
br>
apply whatever DNS resolving method they know, including possibly DNS SRV.<=
br>
<br>
In practice, if there are new elements of DNS SRV that are specific to WS,<=
br>
they should probably be added to the DNS SRV spec and not the WS spec.<br>
Maybe the WS spec should mention that it addresses transport only and<br>
not address resolving. It may recommend to follow some principles to<br>
perform the resolving but should not specify how to do it.<br>
<br>
Hoping it&#39;s a bit clearer,<br>
<font color=3D"#888888">Willy<br>
<br>
</font></blockquote></div><br></div>

--000e0cd3b54ec3487a04a897891d--

From ibc@aliax.net  Thu Jul 21 10:23:28 2011
Return-Path: <ibc@aliax.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9303921F8772; Thu, 21 Jul 2011 10:23:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.669
X-Spam-Level: 
X-Spam-Status: No, score=-2.669 tagged_above=-999 required=5 tests=[AWL=0.008,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 8lN3qEB8l1ju; Thu, 21 Jul 2011 10:23:28 -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 CCDE021F8770; Thu, 21 Jul 2011 10:23:27 -0700 (PDT)
Received: by qyk9 with SMTP id 9so4406903qyk.10 for <multiple recipients>; Thu, 21 Jul 2011 10:23:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.173.70 with SMTP id o6mr470664qaz.322.1311269007199; Thu, 21 Jul 2011 10:23:27 -0700 (PDT)
Received: by 10.229.185.195 with HTTP; Thu, 21 Jul 2011 10:23:27 -0700 (PDT)
In-Reply-To: <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com>
Date: Thu, 21 Jul 2011 19:23:27 +0200
Message-ID: <CALiegfmZ6-kQim83oQ6zjVQeHcCnNv2mBpOHXmNRn14sBDmLfg@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: David Endicott <dendicott@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 21 Jul 2011 14:33:02 -0700
Cc: Server-Initiated HTTP <hybi@ietf.org>, Willy Tarreau <w@1wt.eu>, 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, 21 Jul 2011 17:23:28 -0000

2011/7/21 David Endicott <dendicott@gmail.com>:
> It is my opinion that name resolution (however done) is outside the=C2=A0=
purview
> of WS. =C2=A0 It may be handled in any number of ways by the client, and =
must
> happen *before* WS establishes=C2=A0it's TCP connection and begins handsh=
aking.
> DNS, DNS SRV, etc. are good and useful tools, but are not part of WS.
> A document showing how to use DNS SRV with WS would be useful, but it's n=
ot
> part of the core WS spec.

Ok, there you have a proposal:

  http://tools.ietf.org/html/draft-ibc-websocket-dns-srv-02

:)

Of course, the core WS spec should reference and *mandate* it, or
maybe not and instead a W3C specification should mandate it for
webbrowsers.
And in this case, the WS URI resolution section in core WS spec (DNS A
stuff) should be entirely removed.

--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From w@1wt.eu  Thu Jul 21 10:33:46 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1393E21F85AE; Thu, 21 Jul 2011 10:33:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.444
X-Spam-Level: 
X-Spam-Status: No, score=-5.444 tagged_above=-999 required=5 tests=[AWL=-3.701, BAYES_00=-2.599, HELO_IS_SMALL6=0.556, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hxrvjb4r1+uC; Thu, 21 Jul 2011 10:33:45 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 7018A21F85A3; Thu, 21 Jul 2011 10:33:44 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6LHXcjT017171; Thu, 21 Jul 2011 19:33:38 +0200
Date: Thu, 21 Jul 2011 19:33:38 +0200
From: Willy Tarreau <w@1wt.eu>
To: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110721173338.GB16854@1wt.eu>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CALiegfkk8G6_KE-KfL_RuF96NUbF6yZgcFfsNGtLoAr2=jcYjg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CALiegfkk8G6_KE-KfL_RuF96NUbF6yZgcFfsNGtLoAr2=jcYjg@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Thu, 21 Jul 2011 14:33:03 -0700
Cc: Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>, David Endicott <dendicott@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2011 17:33:46 -0000

On Thu, Jul 21, 2011 at 07:15:13PM +0200, Iñaki Baz Castillo wrote:
> If WS spec does not mandate DNS SRV resolution in WS clients (so
> webbrowsers mainly) then let's forget SRV balancing/failover
> capabilities. If the WS core draft does not want to handle this topic,
> then refer to another document mandating it (in the same way SIP RFC
> 3261 mandates the usage of DNS NAPTR/SRV in RFC 3263 for SIP clients).
> 
> So you can split WS in:
> - transport specification RFC (handshake, frames and so).
> - location WS servers (a MUST for WS clients when resolving WS URI's).

But you can't make usage of DNS a MUST. While it generally is acceptable
over the wide Internet, it's almost always anti-pattern on internal
networks. Application developers in particular can never rely on this
because the guy who manages the DNS is not the same who manages servers
and generally doesn't accept to add any input for an application that is
not in production. Similarly, DNS which announce "public" records for
some services will cause trouble to local clients which would always
make use of the DNS first because of the MUST, and would not be able
to connect to the local address:port which is not announced anywhere.

If someone were to develop a backup/restore solution based on WS, it would
be funny to discover that it cannot be used to restore the DNS server when
this one fails...

However in my opinion it could be good to document a recommended DNS
architecture for WS, that is judged optimal and the most interoperable.
This could clearly be a separate RFC suggesting how clients and server
can make use of DNS SRV records for HA and LB.

> > In practice, if there are new elements of DNS SRV that are specific to WS,
> > they should probably be added to the DNS SRV spec and not the WS spec.
> 
> No. DNS SRV spec (RFC 2782) just explains the DNS SRV mechanism. Any
> protocol can decide wheter to include/mandate it or not. Each protocol
> can register in IANA new "service" values SRV, in the same way SIP and
> XMPP RFC's create "sip" and "xmpp-server" values.

Then maybe the name should be reserved as soon as the protocol spec is
released, and the document should refer to it.

> > Maybe the WS spec should mention that it addresses transport only and
> > not address resolving. It may recommend to follow some principles to
> > perform the resolving but should not specify how to do it.
> 
> That would be great, so another document/spec would *mandate* how WS
> clients MUST resolve WS destinations.

MAY

> But that is not true now as WS
> core spec states simple A/AAAA resolution for locating a WS server.

It does not even say that. It only talks about DNS when suggesting how
a client may select a limit on the number of concurrent connections (#5.1).

Regards,
Willy


From ibc@aliax.net  Thu Jul 21 10:52:58 2011
Return-Path: <ibc@aliax.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7233521F8741; Thu, 21 Jul 2011 10:52:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.669
X-Spam-Level: 
X-Spam-Status: No, score=-2.669 tagged_above=-999 required=5 tests=[AWL=0.008,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 i4gcOG3TegqC; Thu, 21 Jul 2011 10:52:58 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id C52FD21F873D; Thu, 21 Jul 2011 10:52:57 -0700 (PDT)
Received: by qyk29 with SMTP id 29so1095914qyk.10 for <multiple recipients>; Thu, 21 Jul 2011 10:52:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.66.25 with SMTP id l25mr480831qci.265.1311270777131; Thu, 21 Jul 2011 10:52:57 -0700 (PDT)
Received: by 10.229.185.195 with HTTP; Thu, 21 Jul 2011 10:52:57 -0700 (PDT)
In-Reply-To: <9031.1311270000.588511@puncture>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture>
Date: Thu, 21 Jul 2011 19:52:57 +0200
Message-ID: <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Dave Cridland <dave@cridland.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 21 Jul 2011 14:33:02 -0700
Cc: Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>, David Endicott <dendicott@gmail.com>, Willy Tarreau <w@1wt.eu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2011 17:52:58 -0000

2011/7/21 Dave Cridland <dave@cridland.net>:
> It's proven impossible, despite effort, to retrofit SRV onto HTTP; there =
is
> no way it'll be possible to retrofit onto WS.

Right. If WS borns with no SRV (as a MUST for WS clients) then just
forget it and let inherit all the ugly limitations from HTTP protocol.

--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From dendicott@gmail.com  Thu Jul 21 11:01:12 2011
Return-Path: <dendicott@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BCDE21F84DD; Thu, 21 Jul 2011 11:01:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.436
X-Spam-Level: 
X-Spam-Status: No, score=-3.436 tagged_above=-999 required=5 tests=[AWL=-0.138, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 STXUuqrIDdrs; Thu, 21 Jul 2011 11:01:11 -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 A713521F8757; Thu, 21 Jul 2011 11:01:06 -0700 (PDT)
Received: by wyj26 with SMTP id 26so1170469wyj.31 for <multiple recipients>; Thu, 21 Jul 2011 11:01:05 -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=RfwIeXJVKS8NcUu/t/Be+3yV3PxQbrUW6QGWlw9agYI=; b=tFuUvCEgs4ej+dFm0b+lvV8z1qRUan6tpAdMGZH7oL9FBZUgqsCvESZE4bGwUsAJjz yLUvJQb6vEDf7VJFQuw9zPhn8swh4NHxYt9cbyDejgplu+39s9kgeKAaArG56pQTRZmQ LrJqjQzFs6ev6s4rn7kc4K/7sVMSCFMId0Zpk=
MIME-Version: 1.0
Received: by 10.217.6.82 with SMTP id x60mr1129305wes.18.1311271265696; Thu, 21 Jul 2011 11:01:05 -0700 (PDT)
Received: by 10.216.39.197 with HTTP; Thu, 21 Jul 2011 11:01:05 -0700 (PDT)
In-Reply-To: <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com>
Date: Thu, 21 Jul 2011 14:01:05 -0400
Message-ID: <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: David Endicott <dendicott@gmail.com>
To: =?ISO-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
Content-Type: multipart/alternative; boundary=20cf301fb94dfefd3504a89821be
X-Mailman-Approved-At: Thu, 21 Jul 2011 14:33:03 -0700
Cc: Server-Initiated HTTP <hybi@ietf.org>, Willy Tarreau <w@1wt.eu>, 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, 21 Jul 2011 18:01:12 -0000

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

I am strongly opposed to any MUST definition for any type of URL resolution=
.


I'm ok with inheriting / mimicking HTTP.    Since it is intended to live in
the same universe as HTTP, I'm ok with it sharing mechanisms / limitations.



On Thu, Jul 21, 2011 at 1:52 PM, I=F1aki Baz Castillo <ibc@aliax.net> wrote=
:

> 2011/7/21 Dave Cridland <dave@cridland.net>:
> > It's proven impossible, despite effort, to retrofit SRV onto HTTP; ther=
e
> is
> > no way it'll be possible to retrofit onto WS.
>
> Right. If WS borns with no SRV (as a MUST for WS clients) then just
> forget it and let inherit all the ugly limitations from HTTP protocol.
>
> --
> I=F1aki Baz Castillo
> <ibc@aliax.net>
>

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

I am strongly opposed to any MUST definition for any type of URL resolution=
. =A0=A0<div><br></div><div>I&#39;m ok with inheriting /=A0mimicking=A0HTTP=
. =A0 =A0Since it is intended to live in the same universe as HTTP, I&#39;m=
 ok with it sharing mechanisms / limitations.</div>
<div><br></div><div><br></div><div><br><div class=3D"gmail_quote">On Thu, J=
ul 21, 2011 at 1:52 PM, I=F1aki Baz Castillo <span dir=3D"ltr">&lt;<a href=
=3D"mailto:ibc@aliax.net">ibc@aliax.net</a>&gt;</span> wrote:<br><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex;">
2011/7/21 Dave Cridland &lt;<a href=3D"mailto:dave@cridland.net">dave@cridl=
and.net</a>&gt;:<br>
<div class=3D"im">&gt; It&#39;s proven impossible, despite effort, to retro=
fit SRV onto HTTP; there is<br>
&gt; no way it&#39;ll be possible to retrofit onto WS.<br>
<br>
</div>Right. If WS borns with no SRV (as a MUST for WS clients) then just<b=
r>
forget it and let inherit all the ugly limitations from HTTP protocol.<br>
<div><div></div><div class=3D"h5"><br>
--<br>
I=F1aki Baz Castillo<br>
&lt;<a href=3D"mailto:ibc@aliax.net">ibc@aliax.net</a>&gt;<br>
</div></div></blockquote></div><br></div>

--20cf301fb94dfefd3504a89821be--

From ibc@aliax.net  Thu Jul 21 11:10:39 2011
Return-Path: <ibc@aliax.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E02E121F86E6; Thu, 21 Jul 2011 11:10:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.669
X-Spam-Level: 
X-Spam-Status: No, score=-2.669 tagged_above=-999 required=5 tests=[AWL=0.008,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 BsEPcJN9cSQ8; Thu, 21 Jul 2011 11:10:38 -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 CC35A21F876F; Thu, 21 Jul 2011 11:10:36 -0700 (PDT)
Received: by qwc23 with SMTP id 23so1254102qwc.31 for <multiple recipients>; Thu, 21 Jul 2011 11:10:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.66.222 with SMTP id o30mr510052qci.189.1311271825000; Thu, 21 Jul 2011 11:10:25 -0700 (PDT)
Received: by 10.229.185.195 with HTTP; Thu, 21 Jul 2011 11:10:24 -0700 (PDT)
In-Reply-To: <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com>
Date: Thu, 21 Jul 2011 20:10:24 +0200
Message-ID: <CALiegfnGkypkJYxUGGm3Tddgk3D0Ri=EWtN0WMChhEZN3Xsauw@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: David Endicott <dendicott@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 21 Jul 2011 14:33:02 -0700
Cc: Server-Initiated HTTP <hybi@ietf.org>, Willy Tarreau <w@1wt.eu>, 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, 21 Jul 2011 18:10:39 -0000

2011/7/21 David Endicott <dendicott@gmail.com>:
> I am strongly opposed to any MUST definition for any type of URL resoluti=
on.

SIP and XMPP mandate (MUST) a resolution mechanism based on NAPTR, SRV
and A/AAAA records. Are they also wrong? do you also oppose to the DNS
MX resolution (as mandatory) for a mailto: URI? Do you imagine that a
mail server admin could not assume that SMTP clients would always use
MX resolution as the first choice? annoying that you say that, sorry.


> I'm ok with inheriting /=C2=A0mimicking=C2=A0HTTP. =C2=A0 =C2=A0Since it =
is intended to live in
> the same universe as HTTP, I'm ok with it sharing mechanisms / limitation=
s.

Yes, I assume many people in the HTTP warden is fine with this. That
is the problem: forcing a *new* protocol to inherit ugly limitations
just because "people is used to them". I don't understand how you can
prefer to ignore cool NEW solutions/mechanisms. This should not be a
valid argument in a new protocol design.



--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From dendicott@gmail.com  Thu Jul 21 11:43:17 2011
Return-Path: <dendicott@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED90A21F87E2; Thu, 21 Jul 2011 11:43:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.427
X-Spam-Level: 
X-Spam-Status: No, score=-3.427 tagged_above=-999 required=5 tests=[AWL=-0.129, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 cUwra0JX8Xbw; Thu, 21 Jul 2011 11:43:17 -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 B14BC21F8786; Thu, 21 Jul 2011 11:43:08 -0700 (PDT)
Received: by wwe5 with SMTP id 5so1041893wwe.13 for <multiple recipients>; Thu, 21 Jul 2011 11:43:07 -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=UohUz9bZaoYlcN1uxhHQWDuv6A0R8kjPZYf9UMaBHzg=; b=q2lOB8/1Dx3S7/nHDu/RQFjd+FRx+4uVPnIS0WE+0S1ng9icv3bxtmzwYlNDuxYihO oDshworcR8/5CRH8sGaPWdggGZPqd+Y1UOKeJx63CAlhHX3xtwIz6zxVQq+LNpfOwO/e xvjBlTzMb8ORv+mfVhdWtOpkJXcj1OCROrGHE=
MIME-Version: 1.0
Received: by 10.216.1.200 with SMTP id 50mr1215331wed.33.1311273787757; Thu, 21 Jul 2011 11:43:07 -0700 (PDT)
Received: by 10.216.39.197 with HTTP; Thu, 21 Jul 2011 11:43:07 -0700 (PDT)
In-Reply-To: <CALiegfnGkypkJYxUGGm3Tddgk3D0Ri=EWtN0WMChhEZN3Xsauw@mail.gmail.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <CALiegfnGkypkJYxUGGm3Tddgk3D0Ri=EWtN0WMChhEZN3Xsauw@mail.gmail.com>
Date: Thu, 21 Jul 2011 14:43:07 -0400
Message-ID: <CAP992=FrnDrCLgqZGUO9R2WkfgA2D+8TCau=6Xi+xa_u3CXT2w@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: David Endicott <dendicott@gmail.com>
To: =?ISO-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
Content-Type: multipart/alternative; boundary=0016364d2c795297c804a898b8e9
X-Mailman-Approved-At: Thu, 21 Jul 2011 14:33:03 -0700
Cc: Server-Initiated HTTP <hybi@ietf.org>, Willy Tarreau <w@1wt.eu>, 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, 21 Jul 2011 18:43:18 -0000

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

I do not know SIP or XMPP well enough to comment on why they mandated the
name resolution mechanisms they did.    However, XMPP is used in a highly
dynamic host environment, so having flexible & extensible name resolution i=
s
likely an excellent choice.

I do not oppose DNS's MX records for SMTP as email addresses are name@domai=
n,
so obviously the Domain Name System is appropriate.    Also, I fail to see
why a mail admin should care how the SMTP clients arrive at the server.  DN=
S
MX is a reasonable solution, but there may be other methods, any and all of
which are irrelevant to the SMTP server.    Especially when the SMTP server
supports multiple email domains....

Since WS is intended as a browser supported protocol, WS should follow the
same URI resolution mechanisms as HTTP (or how URI resolution is done in
general)  Having URLs that could resolve differently for a HTTP request and
a WS setup is a problem.


However....I agree in the sense that I don't think it's been well thought
out what the ramifications are of introducing a new URI *scheme*.  (ie.
ws:// and wss://)    Since everything after the double-slash is "scheme
specific", defining a scheme implies many things (including name resolution
policies, well-known ports, transport protocols, etc.)   But, I don't want
to get side tracked over this.



On Thu, Jul 21, 2011 at 2:10 PM, I=F1aki Baz Castillo <ibc@aliax.net> wrote=
:

> 2011/7/21 David Endicott <dendicott@gmail.com>:
> > I am strongly opposed to any MUST definition for any type of URL
> resolution.
>
> SIP and XMPP mandate (MUST) a resolution mechanism based on NAPTR, SRV
> and A/AAAA records. Are they also wrong? do you also oppose to the DNS
> MX resolution (as mandatory) for a mailto: URI? Do you imagine that a
> mail server admin could not assume that SMTP clients would always use
> MX resolution as the first choice? annoying that you say that, sorry.
>
>
> > I'm ok with inheriting / mimicking HTTP.    Since it is intended to liv=
e
> in
> > the same universe as HTTP, I'm ok with it sharing mechanisms /
> limitations.
>
> Yes, I assume many people in the HTTP warden is fine with this. That
> is the problem: forcing a *new* protocol to inherit ugly limitations
> just because "people is used to them". I don't understand how you can
> prefer to ignore cool NEW solutions/mechanisms. This should not be a
> valid argument in a new protocol design.
>
>
>
> --
> I=F1aki Baz Castillo
> <ibc@aliax.net>
>

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

I do not know SIP or XMPP well enough to comment on why they mandated the n=
ame resolution mechanisms they did. =A0 =A0However, XMPP is used in a highl=
y dynamic host=A0environment, so having flexible &amp; extensible name reso=
lution is likely an excellent choice.<div>
<br></div><div>I do not oppose DNS&#39;s MX records for SMTP as email addre=
sses are name@domain, so obviously the Domain Name System is appropriate. =
=A0 =A0Also, I fail to see why a mail admin should care how the SMTP client=
s arrive at the server. =A0DNS MX is a reasonable solution, but there may b=
e other methods, any and all of which are irrelevant to the SMTP server. =
=A0 =A0Especially when the SMTP server supports multiple email domains....<=
/div>
<div><br></div><div>Since WS is intended as a browser supported protocol, W=
S should follow the same URI resolution mechanisms as HTTP (or how URI reso=
lution is done in general) =A0Having URLs that could resolve differently fo=
r a HTTP request and a WS setup is a problem.</div>
<div><br></div><div><br></div><div>However....I agree in the sense that I d=
on&#39;t think it&#39;s been well thought out what the ramifications are of=
 introducing a new URI *scheme*. =A0(ie. ws:// and wss://) =A0 =A0Since eve=
rything after the double-slash is &quot;scheme specific&quot;, defining a s=
cheme implies many things (including name resolution policies, well-known p=
orts, transport protocols, etc.) =A0 But, I don&#39;t want to get side trac=
ked over this.</div>
<div><br></div><div><br><br><div class=3D"gmail_quote">On Thu, Jul 21, 2011=
 at 2:10 PM, I=F1aki Baz Castillo <span dir=3D"ltr">&lt;<a href=3D"mailto:i=
bc@aliax.net">ibc@aliax.net</a>&gt;</span> wrote:<br><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex;">
<div class=3D"im">2011/7/21 David Endicott &lt;<a href=3D"mailto:dendicott@=
gmail.com">dendicott@gmail.com</a>&gt;:<br>
</div><div class=3D"im">&gt; I am strongly opposed to any MUST definition f=
or any type of URL resolution.<br>
<br>
</div>SIP and XMPP mandate (MUST) a resolution mechanism based on NAPTR, SR=
V<br>
and A/AAAA records. Are they also wrong? do you also oppose to the DNS<br>
MX resolution (as mandatory) for a mailto: URI? Do you imagine that a<br>
mail server admin could not assume that SMTP clients would always use<br>
MX resolution as the first choice? annoying that you say that, sorry.<br>
<div class=3D"im"><br>
<br>
&gt; I&#39;m ok with inheriting /=A0mimicking=A0HTTP. =A0 =A0Since it is in=
tended to live in<br>
&gt; the same universe as HTTP, I&#39;m ok with it sharing mechanisms / lim=
itations.<br>
<br>
</div>Yes, I assume many people in the HTTP warden is fine with this. That<=
br>
is the problem: forcing a *new* protocol to inherit ugly limitations<br>
just because &quot;people is used to them&quot;. I don&#39;t understand how=
 you can<br>
prefer to ignore cool NEW solutions/mechanisms. This should not be a<br>
valid argument in a new protocol design.<br>
<font color=3D"#888888"><br>
<br>
<br>
--<br>
</font><div><div></div><div class=3D"h5">I=F1aki Baz Castillo<br>
&lt;<a href=3D"mailto:ibc@aliax.net">ibc@aliax.net</a>&gt;<br>
</div></div></blockquote></div><br></div>

--0016364d2c795297c804a898b8e9--

From dendicott@gmail.com  Thu Jul 21 13:57:28 2011
Return-Path: <dendicott@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3A1421F86BD; Thu, 21 Jul 2011 13:57:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.568
X-Spam-Level: 
X-Spam-Status: No, score=-3.568 tagged_above=-999 required=5 tests=[AWL=0.030,  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 yMgaAcXLVagu; Thu, 21 Jul 2011 13:57:26 -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 E4F0D21F86A8; Thu, 21 Jul 2011 13:57:25 -0700 (PDT)
Received: by wyj26 with SMTP id 26so1269260wyj.31 for <multiple recipients>; Thu, 21 Jul 2011 13:57:25 -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=LgsmM44IFtoalDLCWx5puGABu3s2MD+CIDZuKt5geWo=; b=kTGvlAZ7EkSJXZrSsWx3SYJiPRWAJ42Ec1ZyAWjoPctZB6i97JBFwRFtljkzdoVPeK 40ns1NpUGUgvRo4laUIkI3uQ79QmmhZbiH18bgxwOIgNRnlr9ZuFZpsmWfJmx4y/r7dY KEu/cRxjHfx1joMsA/qK+bXYrqjP+DR//OYCE=
MIME-Version: 1.0
Received: by 10.216.234.209 with SMTP id s59mr649447weq.18.1311281844964; Thu, 21 Jul 2011 13:57:24 -0700 (PDT)
Received: by 10.216.39.197 with HTTP; Thu, 21 Jul 2011 13:57:23 -0700 (PDT)
In-Reply-To: <9031.1311279546.247694@puncture>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <CALiegfnGkypkJYxUGGm3Tddgk3D0Ri=EWtN0WMChhEZN3Xsauw@mail.gmail.com> <CAP992=FrnDrCLgqZGUO9R2WkfgA2D+8TCau=6Xi+xa_u3CXT2w@mail.gmail.com> <9031.1311279546.247694@puncture>
Date: Thu, 21 Jul 2011 16:57:23 -0400
Message-ID: <CAP992=Ec3KvAerosLNkJCTNzFniRfU-bFg_7=bAiMOJFarb5zA@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: David Endicott <dendicott@gmail.com>
To: Dave Cridland <dave@cridland.net>
Content-Type: multipart/alternative; boundary=001517592bd091cf6f04a89a9883
X-Mailman-Approved-At: Thu, 21 Jul 2011 14:33:03 -0700
Cc: =?ISO-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>, Willy Tarreau <w@1wt.eu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2011 20:57:28 -0000

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

>
> I have no idea what you might mean by "highly dynamic host environment" in
> this context, but XMPP servers are normally found at the same location
> consistently. However, it is *not* always (or typically) the same location
> as a simple A record lookup:
>

That's what I meant.  XMPP systems have hosts that change around (for many
reasons) and having a name resolution that handles that is good.



> This property alone is very useful - in a websockets case this would mean
> being able to provide websockets services from a different host (or network)
> to the traditional web services in a simple manner, fully compatible with
> SOP.   The fact that this also allows cheap lightweight load balancing and
> fallback control is also useful in other cases; none of this relates to
> dynamic hosts, but simply richer service location.


Yes, those are all excellent reasons to use DNS SRV.   None of them are a
reason to mandate that WS require it.   Because something is good for some
(or many) use cases, does not mean it is appropriate for everything and
certainly is not a reason to mandate it as a requirement.
 System implementer should be free to pick and choose tools and mechanisms
appropriate for their tasks.   DNS SRV would likely be an excellent choice
for many people.   But it should not be the one and only choice.   That's
really all I'm saying - don't force people to use something without an
overwhelming reason to make it the only option.



> I do not oppose DNS's MX records for SMTP as email addresses are
>> name@domain,
>> so obviously the Domain Name System is appropriate.    Also, I fail to see
>> why a mail admin should care how the SMTP clients arrive at the server.
>>  DNS
>> MX is a reasonable solution, but there may be other methods, any and all
>> of
>> which are irrelevant to the SMTP server.    Especially when the SMTP
>> server
>> supports multiple email domains...
>>
>>  A mail admin does need to care *that* the service is located, and
> therefore will care *how* it is located.

You can be as theoretical as you like, by all means, but in practical terms,
> your email address (and my XMPP address) work because they use a defined,
> interoperable, service location mechanism, which operates via DNS record
> lookup.
>
> (Also, I have no idea what multiple domains has to do with this.)


Imagine I'm a SMTP server.   People connect to me.   They do SMTP
transactions.    I do not care how they found me.   Perhaps they used DNS to
find the MX server.  Perhaps they had it cached from before.  Perhaps they
guessed.  Perhaps it's in a hosts file.   I don't care.     I answer VRFY
and RCPT TO commands as appropriate.   If the "name" they are trying to
mailwith is one I recognize, I process it.  If I don't, it's an error.
Just because DNS-MX said that @foobar was handled at <addr>, doesn't mean
the dave@foobar is going to work.

Yes, DNS MX is a well known mechanism for determining what SMTP server to
connect with, but like I tried to say above, it's not mandated by the SMTP
protocol.   DNS MX is independent of SMTP and the two mechanisms
operate separately, but with a common goal.  I can use DNS to resolve a name
and never send email/message.  I can send a email/message via SMTP and never
use DNS to resolve a name.    Or I can use one to do the other.

When a SMTP server handles mail for multiple domains, the SMTP server has to
process the @domain part of the RCPT TO request - DNS is not involved at
that point.   This process is unrelated to any DNS MX definitions.    I used
that as an example of how some name resolutions are sometimes done outside
of any DNS framework.



> Since WS is intended as a browser supported protocol, WS should follow the
>> same URI resolution mechanisms as HTTP (or how URI resolution is done in
>> general)  Having URLs that could resolve differently for a HTTP request
>> and
>> a WS setup is a problem.
>>
>>  But they do resolve differently anyway. You don't get a page from a 'ws'
> scheme URI, you get a transport protocol connection. This is good, indeed,
> it's kind of the point.
>

Do they?   A http uri and a ws uri have the same host/path construction.
 It's really only the scheme that differs - and that identifies the
transport protocol to be used.   Resolution of host name/addresses and
mapping of paths "should" be consistent.

WS is a connection that is semantically related to the URI of the request.


e.g. I could ws://host/davesaid  and get live traffic of what Dave is
saying, and then I could ws://host/bobsaid  and get traffic of what Bob
says.  I wouldn't get Bob on /davesaid and I wouldn't get Dave on /bobsaid.
   Dynamic content identified by a URI

And if I http://host/davesaid  I could get a <li> of what Dave said.
Static content of a URI.

It could be problematic if  ws://host/davesaid resolves to a different
address than http://host/davesaid.     (Or it could be advantage - not for
us to decide, however)


> Your suggestion of "how URI resolution is done in general" is somewhat
> self-defeating, too, since aside from 'http' and 'https', there are
> 'mailto', which uses MX, 'sip' and 'xmpp', which both use SRV.
>

As you just said, the universe is bigger than just xmpp, sip, and http.

>
> I think opponents of SRV records need to mount a stronger argument than the
> kind of luddite argument that if it's hard for one protocol in use by the
> browser, it should be hard for them all.


I think you misinterpret my position.  And I resent the luddite slight.   I
think DNS SRV is an awesome tool and would greatly benefit many
implementations.

My position is that it should not be a *requirement*.     It should be an
optional mechanism that can be used if desired.   Further, since WS is a
bastard cousin to HTTP, they should share a similar name resolution
mechanism.



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

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

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I have no idea w=
hat you might mean by &quot;highly dynamic host environment&quot; in this c=
ontext, but XMPP servers are normally found at the same location consistent=
ly. However, it is *not* always (or typically) the same location as a simpl=
e A record lookup:<br>
</blockquote><div><br></div><div>That&#39;s what I meant. =A0XMPP systems h=
ave hosts that change around (for many reasons) and having a name resolutio=
n that handles that is good.</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;">

This property alone is very useful - in a websockets case this would mean b=
eing able to provide websockets services from a different host (or network)=
 to the traditional web services in a simple manner, fully compatible with =
SOP. =A0=A0The fact that this also allows cheap lightweight load balancing =
and fallback control is also useful in other cases; none of this relates to=
 dynamic hosts, but simply richer service location.</blockquote>
<div><br></div><div>Yes, those are all excellent reasons to use DNS SRV. =
=A0 None of them are a reason to mandate that WS require it. =A0 Because so=
mething is good for some (or many) use cases, does not mean it is appropria=
te for everything and certainly is not a reason to mandate it as a requirem=
ent. =A0 =A0System=A0implementer=A0should be free to pick and choose tools =
and mechanisms appropriate for their tasks. =A0 DNS SRV would likely be an =
excellent choice for many people. =A0 But it should not be the one and only=
 choice. =A0 That&#39;s really all I&#39;m saying - don&#39;t force people =
to use something without an overwhelming reason to make it the only option.=
</div>
<div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class=3D"=
im"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">
I do not oppose DNS&#39;s MX records for SMTP as email addresses are name@d=
omain,<br>
so obviously the Domain Name System is appropriate. =A0 =A0Also, I fail to =
see<br>
why a mail admin should care how the SMTP clients arrive at the server. =A0=
DNS<br>
MX is a reasonable solution, but there may be other methods, any and all of=
<br>
which are irrelevant to the SMTP server. =A0 =A0Especially when the SMTP se=
rver<br>
supports multiple email domains...<br>
<br>
</blockquote></div>
A mail admin does need to care *that* the service is located, and therefore=
 will care *how* it is located.</blockquote><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"=
>

You can be as theoretical as you like, by all means, but in practical terms=
, your email address (and my XMPP address) work because they use a defined,=
 interoperable, service location mechanism, which operates via DNS record l=
ookup.<br>

<br>
(Also, I have no idea what multiple domains has to do with this.)</blockquo=
te><div><br></div><meta http-equiv=3D"content-type" content=3D"text/html; c=
harset=3Dutf-8"><div>Imagine I&#39;m a SMTP server. =A0 People connect to m=
e. =A0 They do SMTP transactions. =A0 =A0I do not care how they found me. =
=A0 Perhaps they used DNS to find the MX server. =A0Perhaps they had it cac=
hed from before. =A0Perhaps they guessed. =A0Perhaps it&#39;s in a hosts fi=
le. =A0 I don&#39;t care. =A0 =A0 I answer VRFY and RCPT TO commands as app=
ropriate. =A0 If the &quot;name&quot; they are trying to mailwith is one I =
recognize, I process it. =A0If I don&#39;t, it&#39;s an error. =A0 Just bec=
ause DNS-MX said that @foobar was handled at &lt;addr&gt;, doesn&#39;t mean=
 the dave@foobar is going to work.</div>
<div><br></div><div>Yes, DNS MX is a well known mechanism for determining w=
hat SMTP server to connect with, but like I tried to say above, it&#39;s no=
t mandated by the SMTP protocol. =A0 DNS MX is independent of SMTP and the =
two mechanisms operate=A0separately, but with a common goal. =A0I can use D=
NS to resolve a name and never send email/message. =A0I can send a email/me=
ssage via SMTP and never use DNS to resolve a name. =A0 =A0Or I can use one=
 to do the other.</div>
<div><br></div><div>When a SMTP server handles mail for multiple domains, t=
he SMTP server has to process the @domain part of the RCPT TO request - DNS=
 is not involved at that point. =A0 This process is unrelated to any DNS MX=
 definitions. =A0 =A0I used that as an example of how some name resolutions=
 are sometimes done outside of any DNS framework.</div>
<div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class=3D"=
im"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">
Since WS is intended as a browser supported protocol, WS should follow the<=
br>
same URI resolution mechanisms as HTTP (or how URI resolution is done in<br=
>
general) =A0Having URLs that could resolve differently for a HTTP request a=
nd<br>
a WS setup is a problem.<br>

<br>
</blockquote></div>
But they do resolve differently anyway. You don&#39;t get a page from a &#3=
9;ws&#39; scheme URI, you get a transport protocol connection. This is good=
, indeed, it&#39;s kind of the point.<br></blockquote><div>=A0</div><div>
Do they? =A0 A http uri and a ws uri have the same host/path construction. =
=A0It&#39;s really only the scheme that differs - and that identifies the t=
ransport protocol to be used. =A0 Resolution of host name/addresses and map=
ping of paths &quot;should&quot; be consistent.</div>
<div><br></div><div>WS is a connection that is semantically related to the =
URI of the request. =A0=A0</div><div><br></div><div>e.g. I could ws://host/=
davesaid =A0and get live traffic of what Dave is saying, and then I could w=
s://host/bobsaid =A0and get traffic of what Bob says. =A0I wouldn&#39;t get=
 Bob on /davesaid and I wouldn&#39;t get Dave on /bobsaid. =A0 =A0Dynamic c=
ontent identified by a URI =A0 =A0 =A0</div>
<div><br></div><div>And if I <a href=3D"http://host/davesaid">http://host/d=
avesaid</a> =A0I could get a &lt;li&gt; of what Dave said. =A0 Static conte=
nt of a URI.</div><div><br></div><div>It could be problematic if =A0ws://ho=
st/davesaid resolves to a different address than <a href=3D"http://host/dav=
esaid">http://host/davesaid</a>. =A0 =A0 (Or it could be advantage - not fo=
r us to decide, however)</div>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Your suggestion of &quot;how URI resolution is done in general&quot; is som=
ewhat self-defeating, too, since aside from &#39;http&#39; and &#39;https&#=
39;, there are &#39;mailto&#39;, which uses MX, &#39;sip&#39; and &#39;xmpp=
&#39;, which both use SRV.<br>
</blockquote><div><br></div><div>As you just said, the universe is bigger t=
han just xmpp, sip, and http. =A0=A0</div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
I think opponents of SRV records need to mount a stronger argument than the=
 kind of luddite argument that if it&#39;s hard for one protocol in use by =
the browser, it should be hard for them all.</blockquote><div><br></div>
<div>I think you misinterpret my position. =A0And=A0I resent the luddite sl=
ight. =A0=A0I think DNS SRV is an awesome tool and would greatly benefit ma=
ny implementations.</div><meta http-equiv=3D"content-type" content=3D"text/=
html; charset=3Dutf-8"><div>
<br></div><div>My position is that it should not be a *requirement*. =A0 =
=A0 It should be an optional mechanism that can be used if desired. =A0 Fur=
ther, since WS is a bastard cousin to HTTP, they should share a similar nam=
e resolution mechanism. =A0 =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;"><div><div></di=
v><div class=3D"h5"><br>
<br>
Dave.<br>
-- <br>
Dave Cridland - mailto:<a href=3D"mailto:dave@cridland.net" target=3D"_blan=
k">dave@cridland.net</a> - <a href=3D"mailto:xmpp%3Adwd@dave.cridland.net" =
target=3D"_blank">xmpp:dwd@dave.cridland.net</a><br>
=A0- acap://<a href=3D"http://acap.dave.cridland.net/byowner/user/dwd/bookm=
arks/" target=3D"_blank">acap.dave.cridland.net/<u></u>byowner/user/dwd/boo=
kmarks/</a><br>
=A0- <a href=3D"http://dave.cridland.net/" target=3D"_blank">http://dave.cr=
idland.net/</a><br>
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade<br>
</div></div></blockquote></div><br>

--001517592bd091cf6f04a89a9883--

From dave@cridland.net  Thu Jul 21 14:46:46 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 8F10D21F86A2; Thu, 21 Jul 2011 14:46:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.395
X-Spam-Level: 
X-Spam-Status: No, score=-2.395 tagged_above=-999 required=5 tests=[AWL=-0.096, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FVw+sASwYfhE; Thu, 21 Jul 2011 14:46:45 -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 F325B21F8665; Thu, 21 Jul 2011 14:46:44 -0700 (PDT)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id EFD6D1168087; Thu, 21 Jul 2011 22:46:40 +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 0TK7J2XiP8KI; Thu, 21 Jul 2011 22:46:37 +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 1DC921168067; Thu, 21 Jul 2011 22:46:37 +0100 (BST)
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <CALiegfnGkypkJYxUGGm3Tddgk3D0Ri=EWtN0WMChhEZN3Xsauw@mail.gmail.com> <CAP992=FrnDrCLgqZGUO9R2WkfgA2D+8TCau=6Xi+xa_u3CXT2w@mail.gmail.com> <9031.1311279546.247694@puncture> <CAP992=Ec3KvAerosLNkJCTNzFniRfU-bFg_7=bAiMOJFarb5zA@mail.gmail.com>
In-Reply-To: <CAP992=Ec3KvAerosLNkJCTNzFniRfU-bFg_7=bAiMOJFarb5zA@mail.gmail.com>
MIME-Version: 1.0
Message-Id: <9031.1311284797.122597@puncture>
Date: Thu, 21 Jul 2011 22:46:37 +0100
From: Dave Cridland <dave@cridland.net>
To: David Endicott <dendicott@gmail.com>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>, Willy Tarreau <w@1wt.eu>, =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Content-Type: text/plain; delsp="yes"; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: 8Bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2011 21:46:46 -0000

On Thu Jul 21 21:57:23 2011, David Endicott wrote:
> >
> > I have no idea what you might mean by "highly dynamic host  
> environment" in
> > this context, but XMPP servers are normally found at the same  
> location
> > consistently. However, it is *not* always (or typically) the same  
> location
> > as a simple A record lookup:
> >
> 
> That's what I meant.  XMPP systems have hosts that change around  
> (for many
> reasons) and having a name resolution that handles that is good.
> 
> 
But that statement makes no sense.

Firstly, XMPP servers simply *don't* change around. Really. I don't  
think Google's servers have changed since the service launched:

;; ANSWER SECTION:
_xmpp-server._tcp.gmail.com. 26125 IN	SRV	5 0 5269  
xmpp-server.l.google.com.
_xmpp-server._tcp.gmail.com. 26125 IN	SRV	20 0 5269  
xmpp-server1.l.google.com.
_xmpp-server._tcp.gmail.com. 26125 IN	SRV	20 0 5269  
xmpp-server2.l.google.com.
_xmpp-server._tcp.gmail.com. 26125 IN	SRV	20 0 5269  
xmpp-server3.l.google.com.
_xmpp-server._tcp.gmail.com. 26125 IN	SRV	20 0 5269  
xmpp-server4.l.google.com.

The *clients* move, but they're *doing* SRV resolution, in order to  
locate the servers for their domain.

Secondly, there's nothing dynamic or magical about SRV lookup; the  
records are no more or less static than any other. SRV handles  
roaming hosts as targets no better or worse than A records,  
therefore. All SRV adds is a way of adding indirection, host/port  
discovery, and pushing fallback and load balancing toward the client.

I'm concerned that you may have critically misunderstood what SRV  
records are useful for.

> > This property alone is very useful - in a websockets case this  
> would mean
> > being able to provide websockets services from a different host  
> (or network)
> > to the traditional web services in a simple manner, fully  
> compatible with
> > SOP.   The fact that this also allows cheap lightweight load  
> balancing and
> > fallback control is also useful in other cases; none of this  
> relates to
> > dynamic hosts, but simply richer service location.
> 
> 
> Yes, those are all excellent reasons to use DNS SRV.   None of them  
> are a
> reason to mandate that WS require it.   Because something is good  
> for some
> (or many) use cases, does not mean it is appropriate for everything  
> and
> certainly is not a reason to mandate it as a requirement.
>  System implementer should be free to pick and choose tools and  
> mechanisms
> appropriate for their tasks.   DNS SRV would likely be an excellent  
> choice
> for many people.   But it should not be the one and only choice.    
> That's
> really all I'm saying - don't force people to use something without  
> an
> overwhelming reason to make it the only option.

SRV records simply can't be bolted on afterwards. That's been proven  
with HTTP itself. That's an overwhelming reason, in my opinion.

> Imagine I'm a SMTP server.   People connect to me.   They do SMTP
> transactions.    I do not care how they found me.   Perhaps they  
> used DNS to
> find the MX server.  Perhaps they had it cached from before.   
> Perhaps they
> guessed.  Perhaps it's in a hosts file.   I don't care.     I  
> answer VRFY
> and RCPT TO commands as appropriate.   If the "name" they are  
> trying to
> mailwith is one I recognize, I process it.  If I don't, it's an  
> error.
> Just because DNS-MX said that @foobar was handled at <addr>,  
> doesn't mean
> the dave@foobar is going to work.
> 
> 
Erm. OK...

In the real world, people do care that their mailserver can be found,  
and so they publish MX records, in the confidence that other mail  
servers will use them. This is similar to being a webmaster and  
wanting your website to be found, thus putting A records in. But  
cleverer.

Now, I agree that, in theory, it would be possible to not bother with  
DNS, and simply ask people to put your hostname into their hosts  
files, but you know, I don't think this would work as well, and it's  
certainly not an argument against SRV. (Iñaki's proposal, as I  
recall, even has fallbacks to allow server administrators to avoid  
SRV records in some cases).


> Yes, DNS MX is a well known mechanism for determining what SMTP  
> server to
> connect with, but like I tried to say above, it's not mandated by  
> the SMTP
> protocol.   DNS MX is independent of SMTP and the two mechanisms
> operate separately, but with a common goal.  I can use DNS to  
> resolve a name
> and never send email/message.  I can send a email/message via SMTP  
> and never
> use DNS to resolve a name.    Or I can use one to do the other.
> 
> 
In practical terms, the MX record and SMTP are interlinked. Moreover,  
RFC 5321 says:

   Only resolvable, fully-qualified domain names (FQDNs) are permitted
   when domain names are used in SMTP.  In other words, names that can
   be resolved to MX RRs or address (i.e., A or AAAA) RRs (as  
discussed
   in Section 5) are permitted, as are CNAME RRs whose targets can be
   resolved, in turn, to MX or address RRs.  Local nicknames or
   unqualified names MUST NOT be used.

So there is an argument that it does, indeed, mandate DNS.


> When a SMTP server handles mail for multiple domains, the SMTP  
> server has to
> process the @domain part of the RCPT TO request - DNS is not  
> involved at
> that point.   This process is unrelated to any DNS MX definitions.   
>   I used
> that as an example of how some name resolutions are sometimes done  
> outside
> of any DNS framework.

But the name resolutions are done in exactly the same way, whether  
the mailserver handles one or many domains.

So a mail administrator must ensure that MX records for all the  
domains point to the mailserver host.


> Do they?   A http uri and a ws uri have the same host/path  
> construction.
>  It's really only the scheme that differs - and that identifies the
> transport protocol to be used.   Resolution of host name/addresses  
> and
> mapping of paths "should" be consistent.
> 
> 
So you're expecting xmpp://dave.cridland@isode.com to do what,  
exactly? Because it doesn't do an A record lookup of isode.com, for  
starters.


> WS is a connection that is semantically related to the URI of the  
> request.
> 
> 
> e.g. I could ws://host/davesaid  and get live traffic of what Dave  
> is
> saying, and then I could ws://host/bobsaid  and get traffic of what  
> Bob
> says.  I wouldn't get Bob on /davesaid and I wouldn't get Dave on  
> /bobsaid.
>    Dynamic content identified by a URI
> 
> And if I http://host/davesaid  I could get a <li> of what Dave said.
> Static content of a URI.
> 
> It could be problematic if  ws://host/davesaid resolves to a  
> different
> address than http://host/davesaid.     (Or it could be advantage -  
> not for
> us to decide, however)

I have no idea what any of this means, but it sounds largely  
theoretical, and orthogonal to the point at hand.

Let's put it in practical terms.

'ws' and 'http' URIs have to be treated in different ways.

Therefore, we can treat them in different ways.

> > Your suggestion of "how URI resolution is done in general" is  
> somewhat
> > self-defeating, too, since aside from 'http' and 'https', there  
> are
> > 'mailto', which uses MX, 'sip' and 'xmpp', which both use SRV.
> >
> 
> As you just said, the universe is bigger than just xmpp, sip, and  
> http.
> 
> 
Erm.

Yes.

What this has to do with SRV record usage in websockets is entirely  
beyond me.


> >
> > I think opponents of SRV records need to mount a stronger  
> argument than the
> > kind of luddite argument that if it's hard for one protocol in  
> use by the
> > browser, it should be hard for them all.
> 
> 
> I think you misinterpret my position.  And I resent the luddite  
> slight.   I
> think DNS SRV is an awesome tool and would greatly benefit many
> implementations.
> 
> My position is that it should not be a *requirement*.     It should  
> be an
> optional mechanism that can be used if desired.   Further, since WS  
> is a
> bastard cousin to HTTP, they should share a similar name resolution
> mechanism.

My argument is that it cannot be made optional, so if we want to ever  
take advantage of this "awesome tool", we need to bake it in from the  
start.

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 dave@cridland.net  Thu Jul 21 14:52:12 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 7A10921F898E; Thu, 21 Jul 2011 14:52:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.389
X-Spam-Level: 
X-Spam-Status: No, score=-2.389 tagged_above=-999 required=5 tests=[AWL=-0.090, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HcRkdUJspR84; Thu, 21 Jul 2011 14:52:12 -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 B274A21F8915; Thu, 21 Jul 2011 14:52:11 -0700 (PDT)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id 974021168087; Thu, 21 Jul 2011 22:52:10 +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 6pNx0iFBKWL8; Thu, 21 Jul 2011 22:52:08 +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 ED79C1168067; Thu, 21 Jul 2011 22:52:07 +0100 (BST)
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CALiegfkk8G6_KE-KfL_RuF96NUbF6yZgcFfsNGtLoAr2=jcYjg@mail.gmail.com> <20110721173338.GB16854@1wt.eu>
In-Reply-To: <20110721173338.GB16854@1wt.eu>
MIME-Version: 1.0
Message-Id: <9031.1311285127.963748@puncture>
Date: Thu, 21 Jul 2011 22:52:07 +0100
From: Dave Cridland <dave@cridland.net>
To: Willy Tarreau <w@1wt.eu>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>, David Endicott <dendicott@gmail.com>, =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
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: Thu, 21 Jul 2011 21:52:12 -0000

On Thu Jul 21 18:33:38 2011, Willy Tarreau wrote:
> If someone were to develop a backup/restore solution based on WS,  
> it would
> be funny to discover that it cannot be used to restore the DNS  
> server when
> this one fails...
> 
> 
If SRV (with a fallback) is defined as part of the core spec, this  
usage would use the fallback.


> However in my opinion it could be good to document a recommended DNS
> architecture for WS, that is judged optimal and the most  
> interoperable.
> This could clearly be a separate RFC suggesting how clients and  
> server
> can make use of DNS SRV records for HA and LB.

Okay, a thought experiment for you.

Let's assume we go ahead with dumb A/AAAA lookups.

How will it be possible for a server to later inform browser it  
wishes to use SRV lookups?

If you have an answer for this, we can make it optional, and moreover  
we can deploy SRV for HTTP as well.

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 dave@cridland.net  Thu Jul 21 15:21:29 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 94AC821F8589; Thu, 21 Jul 2011 15:21:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.533
X-Spam-Level: 
X-Spam-Status: No, score=-2.533 tagged_above=-999 required=5 tests=[AWL=0.066,  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 HBTpaYmZMi8R; Thu, 21 Jul 2011 15:21: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 6BD6521F8581; Thu, 21 Jul 2011 15:21:25 -0700 (PDT)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id 4530A1168087; Thu, 21 Jul 2011 23:21:11 +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 xCXy2b3rXpa3; Thu, 21 Jul 2011 23:21:08 +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 EE3041168067; Thu, 21 Jul 2011 23:21:07 +0100 (BST)
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com>
In-Reply-To: <4E28A51F.4020704@callenish.com>
MIME-Version: 1.0
Message-Id: <9031.1311286867.939466@puncture>
Date: Thu, 21 Jul 2011 23:21:07 +0100
From: Dave Cridland <dave@cridland.net>
To: Bruce Atherton <bruce@callenish.com>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>, David Endicott <dendicott@gmail.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: Thu, 21 Jul 2011 22:21:29 -0000

On Thu Jul 21 23:15:59 2011, Bruce Atherton wrote:
> So if you have no control over the DNS, it is not a problem. The  
> host will be resolved exactly the same way as it is now, using a  
> hosts file or A record or whatever. The only change is that the  
> client is required to try to use the more advanced mechanism if it  
> is available.
> 
> 
Right.


> I admit that I find it a little troubling to use MUST for the  
> client to follow this procedure as there is a burden on  
> implementers to understand how to code this since it isn't done by  
> default in the standard libraries the way that ordinary name  
> resolution is. Making it the recognized best practice with a SHOULD  
> would be preferable all else being equal.
> 
> 
SRV lookup is pretty commonplace now in libraries. XMPP and SIP  
clients have no difficulty finding this functionality in a wide  
variety of environments. For the web, where there are substantially  
fewer web browsers than there are XMPP clients, I don't think this  
would pose any kind of problem.


> It can be argued that not using a MUST may well open up  
> interoperability problems because some Websockets clients contact  
> the wrong host. However, keep in mind that in the older SIP RFC2543  
> it provided two resolution mechanisms. It specified that clients  
> SHOULD look up address records, but MAY use the DNS SRV mechanism.  
> SIP survived that without too much of a hassle. And specifying that  
> Websockets clients SHOULD use DNS SRV, but MAY use address records  
> alone looks like an improvement.
> 
> 
SIP survived because it was very small. I don't see WS making a  
transition, in the same way that repeated attempts have failed to  
move HTTP to SRV.

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 dworley@avaya.com  Thu Jul 21 15:29:33 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 64EC911E8071 for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 15:29:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.009
X-Spam-Level: 
X-Spam-Status: No, score=-103.009 tagged_above=-999 required=5 tests=[AWL=-0.209, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lqG-B79SOnY4 for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 15:29:33 -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 B4DF111E8075 for <ietf@ietf.org>; Thu, 21 Jul 2011 15:29:32 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAOGnKE7GmAcF/2dsb2JhbABTp0N3iHyfdwKbSoVgXwSYE4tV
X-IronPort-AV: E=Sophos;i="4.67,244,1309752000"; d="scan'208";a="257967633"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 21 Jul 2011 18:29:30 -0400
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 21 Jul 2011 18:27:24 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Thu, 21 Jul 2011 18:29:28 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "irtf-announce@irtf.org" <irtf-announce@irtf.org>, "irsg@irtf.org" <irsg@irtf.org>, "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 21 Jul 2011 18:27:57 -0400
Subject: RE: Preliminary Agenda: IRTF Open Meeting at IETF-81
Thread-Topic: Preliminary Agenda: IRTF Open Meeting at IETF-81
Thread-Index: AcxH7g8ReGB+qPXJS5SMb4ehzbtM8gAB2K4E
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F57A9@DC-US1MBEX4.global.avaya.com>
References: <4B56B390-1EAF-4BAC-A542-DAD360FF4583@nokia.com>
In-Reply-To: <4B56B390-1EAF-4BAC-A542-DAD360FF4583@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2011 22:29:33 -0000

> From: Lars Eggert [lars.eggert@nokia.com]
>=20
> *PRELIMINARY* Agenda
> IRTF Open Meeting
> Quebec City, Canada
> July 11, 2011, 9:00 - 11:30 (tentative)

You say the meeting was 10 days ago and only the preliminary agenda is
available?

Dale

From marka@isc.org  Thu Jul 21 16:10:20 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 28A4D21F850B for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 16:10:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.607
X-Spam-Level: 
X-Spam-Status: No, score=-2.607 tagged_above=-999 required=5 tests=[AWL=-0.008, 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 R5R84Lc7RcbS for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 16:10:19 -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 5D3BA21F8507 for <ietf@ietf.org>; Thu, 21 Jul 2011 16:10:19 -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 030455F98B6; Thu, 21 Jul 2011 23:09:56 +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 E77DD216C7B; Thu, 21 Jul 2011 23:09: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 B41C2120FCCF; Fri, 22 Jul 2011 09:09:52 +1000 (EST)
To: John C Klensin <john-ietf@jck.com>
From: Mark Andrews <marka@isc.org>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <BBB3AB81-1A20-4022-8687-CD88B000B281@bogus.com> <A6908373951C6911489DF57A@PST.JCK.COM> <71D5A97D-7119-4082-BC87-6505370CE800@bogus.com> <13205C286662DE4387D9AF3AC30EF456D3F3DEEA84@EMBX01-WF.jnpr.net> <C2C73F7968F19FEEF11B2C67@[192.168.1.128]> <E85A5A32-3665-4932-96A7-BADB11DDB2E8@sabahattin-gucukoglu.com> <4E25F868.1000109@dougbarton.us> <90D829BF-BB51-4B0E-B9A6-4C9CCA1D2840@sabahattin-gucukoglu.com> <4E27F407.8090006@alvestrand.no> <C125CD63E1264E518A4C7423@PST.JCK.COM>
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
In-reply-to: Your message of "Thu, 21 Jul 2011 13:00:02 -0400." <C125CD63E1264E518A4C7423@PST.JCK.COM>
Date: Fri, 22 Jul 2011 09:09:52 +1000
Message-Id: <20110721230952.B41C2120FCCF@drugs.dv.isc.org>
Cc: Harald Alvestrand <harald@alvestrand.no>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2011 23:10:20 -0000

In message <C125CD63E1264E518A4C7423@PST.JCK.COM>, John C Klensin writes:
> 
> 
> --On Thursday, July 21, 2011 11:40 +0200 Harald Alvestrand
> <harald@alvestrand.no> wrote:
> 
> >...
> >> Actively being used.  In production.  So that taking it away
> >> would hurt the entity using it, threaten the entity's comfort
> >> and convenience, or just generally go against the stated
> >> goals of making the Internet a better place for everybody
> >> through the instrumentation and maintenance of standards.
> >
> > The idea that moving a standard to Historic would take away
> > the ability of people to use it reminds me of the story from
> > the Norwegian army, approx 1939:
> > 
> > - "If the enemy invades, how will you prevent them from using
> > the train network?"
> > - "Burn all the tickets, sir!"
> 
> I like this analogy.  The proposed action would have no effect
> whatsoever on the behavior that one is trying to discourage.
> But the move makes the party recommending the action look
> ridiculous, ridiculous enough that the story of the
> recommendation is still being told move than 70 years later.
> 
>      john

Except there are vendors who have already threatened to remove the
6to4 code if it is declared historic then you are left between a
rock and a hard place if you need to upgrade the software on the
6to4 router for other reasons and still want to use 6to4.

Not everyone is in the position to just board the train they want
by force to take the analogy a little further.

Mark
-- 
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  Thu Jul 21 17:12:29 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 8F27C21F8686 for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 17:12:29 -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 bNfEKrFw1HoY for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 17:12:29 -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 BD01521F867F for <ietf@ietf.org>; Thu, 21 Jul 2011 17:12:28 -0700 (PDT)
Received: (qmail 18382 invoked from network); 22 Jul 2011 00:30:44 -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; 22 Jul 2011 00:30:44 -0000
Message-ID: <4E28C035.6020009@necom830.hpcl.titech.ac.jp>
Date: Fri, 22 Jul 2011 09:11:33 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture>
In-Reply-To: <9031.1311270000.588511@puncture>
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: Fri, 22 Jul 2011 00:12:29 -0000

Dave Cridland wrote:

> It's proven impossible, despite effort, to retrofit SRV onto HTTP;

Where is a proof?

						Masataka Ohta

From marka@isc.org  Thu Jul 21 19:16:52 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 29D9921F86B3 for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 19:16:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.607
X-Spam-Level: 
X-Spam-Status: No, score=-2.607 tagged_above=-999 required=5 tests=[AWL=-0.008, 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 vV2tve80UrKJ for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 19:16: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 5D0A221F86AE for <ietf@ietf.org>; Thu, 21 Jul 2011 19:16:51 -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 C548F5F98E9; Fri, 22 Jul 2011 02:16:31 +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 BA78B216C7B; Fri, 22 Jul 2011 02:16:29 +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 48D811211E54; Fri, 22 Jul 2011 12:16:27 +1000 (EST)
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
From: Mark Andrews <marka@isc.org>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <4E28C035.6020009@necom830.hpcl.titech.ac.jp>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
In-reply-to: Your message of "Fri, 22 Jul 2011 09:11:33 +0900." <4E28C035.6020009@necom830.hpcl.titech.ac.jp>
Date: Fri, 22 Jul 2011 12:16:27 +1000
Message-Id: <20110722021627.48D811211E54@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, 22 Jul 2011 02:16:52 -0000

In message <4E28C035.6020009@necom830.hpcl.titech.ac.jp>, Masataka Ohta writes:
> Dave Cridland wrote:
> 
> > It's proven impossible, despite effort, to retrofit SRV onto HTTP;
> 
> Where is a proof?
> 
> 						Masataka Ohta

Transitioning HTTP to use SRV is trivial even with proxies.

Transitioning HTTPS to use SRV is complicated because of proxies.
There needs to be changes to how clients talk to proxies for HTTPS
+ SRV to work through proxies.

HTTP and HTTPS's use of the DNS is a abomination.  CNAME is totally
misused.  If you want to host a service on another machine you use
a record that indicates that.  You don't use a alias because aliases
mean so much more.

Getting back to WS and SRV, WS needs to be SRV aware from day one
or it needs its own type in the DNS.  If you don't have SRV records
then you fallback to straight address records.

WS needs to specify what happens when a CNAME, literal or synthesised
from a DNAME, is returned in a DNS lookup.  Is "host.example.net
CNAME host.example.com" equivalent to "host.example.net SRV 100 0
0 host.example.com" or is the CNAME treated as a alias and the URL
gets re-written?

Take the case where one name really is a alias for the other.

	ws.example.net CNAME example.net
	_ws._tcp.example.net SRV 100 0 0 server.hoster.com.

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

From moore@network-heretics.com  Thu Jul 21 20:18: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 9F9DA11E8087 for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 20:18:04 -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 u7uHxoAhJH0N for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 20:18:03 -0700 (PDT)
Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id BA1D411E8086 for <ietf@ietf.org>; Thu, 21 Jul 2011 20:18:03 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 3750E208CE; Thu, 21 Jul 2011 23:18:03 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Thu, 21 Jul 2011 23:18: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=jCwwgOis21Al78c0gyP2gKQBu30=; b=t6 MM9EGeC0c7ZLXRuS7pEBpBqK/wuTXsv4/voDqqQV3iwGmMAa4YevPIlcn48GiiQi qLIZ3JIeE0+Ssd3ZwbzSX+1IS8c2ZH3XHLWLoW2I1lDpAA839G7KBSmnQ7NUoxRL NNkwkp7GkyT6RUbkj1sL6pDGZi508JeLXnvVc2ZwY=
X-Sasl-enc: n4BhG39Map11PyuwWcBCtWYuDXlRv4nLG/yOPY/ipSRT 1311304680
Received: from [10.59.1.76] (static-71-166-174-114.washdc.east.verizon.net [71.166.174.114]) by mail.messagingengine.com (Postfix) with ESMTPA id 2736C4116A1; Thu, 21 Jul 2011 23:17:50 -0400 (EDT)
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
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: <20110722021627.48D811211E54@drugs.dv.isc.org>
Date: Thu, 21 Jul 2011 23:17:39 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0DD53760-9B8A-4569-8C67-81421A8A24B6@network-heretics.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <4E28C035.6020009@necom830.hpcl.titech.ac.jp> <20110722021627.48D811211E54@drugs.dv.isc.org>
To: Mark Andrews <marka@isc.org>
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, 22 Jul 2011 03:18:04 -0000

On Jul 21, 2011, at 10:16 PM, Mark Andrews wrote:

>=20
> In message <4E28C035.6020009@necom830.hpcl.titech.ac.jp>, Masataka =
Ohta writes:
>> Dave Cridland wrote:
>>=20
>>> It's proven impossible, despite effort, to retrofit SRV onto HTTP;
>>=20
>> Where is a proof?
>>=20
>> 						Masataka Ohta
>=20
> Transitioning HTTP to use SRV is trivial even with proxies.
>=20
> Transitioning HTTPS to use SRV is complicated because of proxies.
> There needs to be changes to how clients talk to proxies for HTTPS
> + SRV to work through proxies.
>=20
> HTTP and HTTPS's use of the DNS is a abomination.  CNAME is totally
> misused.  If you want to host a service on another machine you use
> a record that indicates that.  You don't use a alias because aliases
> mean so much more.
>=20
> Getting back to WS and SRV, WS needs to be SRV aware from day one
> or it needs its own type in the DNS.  If you don't have SRV records
> then you fallback to straight address records.

I'm fairly convinced that in the vast majority of cases, SRV is a bad =
idea.  DNS is already too out of sync from hosts in many situations; SRV =
just makes the situation worse.  Or to put it another way, if you want =
to give every DNS admin the ability to impose fine-grained control over =
what all of the hosts named by his DNS zones can do, deploy SRV =
universally.  There are situations where this makes sense, but overall, =
giving that level of control to DNS administrators is an extremely bad =
idea.

That said, if this protocol is going to use SRV, it absolutely needs to =
do it from day one.  There's no way to retro-fit SRV to most protocols =
without breaking compatibility with existing implementations of those =
protocols.

Keith


From michelle.cotton@icann.org  Thu Jul 21 20:26:29 2011
Return-Path: <michelle.cotton@icann.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 C79D921F85F3 for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 20:26:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.404
X-Spam-Level: 
X-Spam-Status: No, score=-106.404 tagged_above=-999 required=5 tests=[AWL=0.194, 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 EtbxpKUGr4qQ for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 20:26:28 -0700 (PDT)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by ietfa.amsl.com (Postfix) with ESMTP id D72C6228011 for <ietf@ietf.org>; Thu, 21 Jul 2011 20:26:28 -0700 (PDT)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Thu, 21 Jul 2011 20:26:28 -0700
From: Michelle Cotton <michelle.cotton@icann.org>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 21 Jul 2011 20:26:24 -0700
Subject: Additional registries converted to XML and announcement of new registry for Service Names and Port Numbers
Thread-Topic: Additional registries converted to XML and announcement of new registry for Service Names and Port Numbers
Thread-Index: AcxIHyIWmRI/T6gv40G3RrdMZb2fUg==
Message-ID: <CA4E3BF0.32F65%michelle.cotton@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.10.0.110428
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CA4E3BF032F65michellecottonicannorg_"
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, 22 Jul 2011 03:26:29 -0000

--_000_CA4E3BF032F65michellecottonicannorg_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

IETF Community:

This is a message for your information.

Last year we archived some legacy text files and notified the IETF communit=
y which ones those were.  This is follow-up message with a new set of regis=
tries that have been both converted and archived.  A total of 78% of the re=
gistries we maintain have been converted to xml.

We will repeat this step again in January 2012 with the registries that we =
convert between July 21, 2011 and December 31, 2011.


Attention:  We recently combined and converted the Service Names and Port N=
umbers registry in accordance with a recently approved document to become a=
n RFC.  The legacy registries will be maintained for 2 more weeks so that a=
nyone running scripts or gathering information can adjust/update what they =
need to.

Legacy URLs:
http://www.iana.org/assignments/service-names/service-names.xml
http://www.iana.org/assignments/port-numbers

NEW URL:
http://www.iana.org/assignments/service-names-port-numbers/service-names-po=
rt-numbers.xml

We are aware that the new registry is very slow to load in some browsers an=
d we are working on resolving the speed issue.

If you have any questions, please do not hesitate to contact me.

Thank you,

Michelle Cotton
Manager, IETF Relations - IANA
ICANN

List of Registries that have been converted to XML between June 30, 2010 an=
d July 20, 2011:


 http://www.iana.org/assignments/bgp-data-collection-communities-std
 http://www.iana.org/assignments/channel-binding-types/
 http://www.iana.org/assignments/enum-services
 http://www.iana.org/assignments/eapsimaka-numbers
 http://www.iana.org/assignments/eappotp-identifiers
 http://www.iana.org/assignments/http-parameters
 http://www.iana.org/assignments/inst-man-values
 http://www.iana.org/assignments/integ-serv
 http://www.iana.org/assignments/icmp-parameters
 http://www.iana.org/assignments/ikev2-parameters
 http://www.iana.org/assignments/ipp-registrations
 http://www.iana.org/assignments/ipv6-address-space
 http://www.iana.org/assignments/ipv6-anycast-addresses
 http://www.iana.org/assignments/iana-ipv6-special-registry
 http://www.iana.org/assignments/ipv6-unicast-address-assignments
http://www.iana.org/assignments/ipv6-parameters
 http://www.iana.org/assignments/ipv6-tla-assignments
 http://www.iana.org/assignments/isns-parameters
 http://www.iana.org/assignments/idxp-options
 http://www.iana.org/assignments/isis-tlv-codepoints
 http://www.iana.org/assignments/language-tags
 http://www.iana.org/assignments/lmp-parameters
 http://www.iana.org/assignments/mtqp-options
 http://www.iana.org/assignments/milnet-parameters
 http://www.iana.org/assignments/mpls-id-type
 http://www.iana.org/assignments/text-directory-registrations
 http://www.iana.org/assignments/pppoe-parameters
 http://www.iana.org/assignments/port-numbers
 http://www.iana.org/assignments/pwe3-parameters
 http://www.iana.org/assignments/public-data-network-numbers
http://www.iana.org/assignments/rmt-fec-parameters
 http://www.iana.org/assignments/rsvp-parameters
 http://www.iana.org/assignments/ssh-parameters
 http://www.iana.org/assignments/svrloc-cryptographic-bsd
 http://www.iana.org/assignments/svrloc-error-numbers
 http://www.iana.org/assignments/service-names
 http://www.iana.org/assignments/sip-table
 http://www.iana.org/assignments/sip-priv-values
 http://www.iana.org/assignments/sieve-extensions
 http://www.iana.org/assignments/sieve-environment-items
 http://www.iana.org/assignments/sasl-mechanisms
 http://www.iana.org/assignments/smtp-enhanced-status-codes
 http://www.iana.org/assignments/snmp-number-spaces
 http://www.iana.org/assignments/sun-rpc-numbers
 http://www.iana.org/assignments/tcp-header-flags
 http://www.iana.org/assignments/sdp-security-descriptions

--_000_CA4E3BF032F65michellecottonicannorg_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Additional registries converted to XML and announcement of new regis=
try for Service Names and Port Numbers</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:=
12pt'>IETF Community:<BR>
<BR>
This is a message for your information.<BR>
<BR>
Last year we archived some legacy text files and notified the IETF communit=
y which ones those were. &nbsp;This is follow-up message with a new set of =
registries that have been both converted and archived. &nbsp;A total of 78%=
 of the registries we maintain have been converted to xml. &nbsp;<BR>
</SPAN></FONT><SPAN STYLE=3D'font-size:12pt'><FONT COLOR=3D"#131313"><FONT =
FACE=3D"Lucida Grande"><BR>
We will repeat this step again in January 2012 with the registries that we =
convert between July 21, 2011 and December 31, 2011.<BR>
<BR>
<BR>
Attention: &nbsp;We recently combined and converted the Service Names and P=
ort Numbers registry in accordance with a recently approved document to bec=
ome an RFC. &nbsp;The legacy registries will be maintained for 2 more weeks=
 so that anyone running scripts or gathering information can adjust/update =
what they need to.<BR>
<BR>
Legacy URLs: <BR>
<a href=3D"http://www.iana.org/assignments/service-names/service-names.xml"=
>http://www.iana.org/assignments/service-names/service-names.xml</a><BR>
<a href=3D"http://www.iana.org/assignments/port-numbers">http://www.iana.or=
g/assignments/port-numbers</a><BR>
<BR>
NEW URL: <BR>
<a href=3D"http://www.iana.org/assignments/service-names-port-numbers/servi=
ce-names-port-numbers.xml">http://www.iana.org/assignments/service-names-po=
rt-numbers/service-names-port-numbers.xml</a><BR>
<BR>
We are aware that the new registry is very slow to load in some browsers an=
d we are working on resolving the speed issue.<BR>
<BR>
If you have any questions, please do not hesitate to contact me.<BR>
<BR>
Thank you,<BR>
<BR>
Michelle Cotton<BR>
Manager, IETF Relations - IANA<BR>
ICANN<BR>
</FONT></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><BR>
List of Registries that have been converted to XML between June 30, 2010 an=
d July 20, 2011:<BR>
&nbsp;&nbsp;<BR>
&nbsp;&nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/bgp-data-collection-communities-std">http://www.iana.=
org/assignments/bgp-data-collection-communities-std</a></FONT><FONT FACE=3D=
"Calibri, Verdana, Helvetica, Arial"> &nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/channel-binding-types/">http://www.iana.org/assignmen=
ts/channel-binding-types/</a></FONT><FONT FACE=3D"Calibri, Verdana, Helveti=
ca, Arial"> &nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/enum-services">http://www.iana.org/assignments/enum-s=
ervices</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> &nbsp;=
<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/eapsimaka-numbers">http://www.iana.org/assignments/ea=
psimaka-numbers</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
> &nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/eappotp-identifiers">http://www.iana.org/assignments/=
eappotp-identifiers</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Ar=
ial"> &nbsp;&nbsp;&nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http=
-parameters</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> &n=
bsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/inst-man-values">http://www.iana.org/assignments/inst=
-man-values</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> &n=
bsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/integ-serv">http://www.iana.org/assignments/integ-ser=
v</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> &nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/icmp-parameters">http://www.iana.org/assignments/icmp=
-parameters</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> &n=
bsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/ikev2-parameters">http://www.iana.org/assignments/ike=
v2-parameters</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> =
&nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/ipp-registrations">http://www.iana.org/assignments/ip=
p-registrations</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
> &nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/ipv6-address-space">http://www.iana.org/assignments/i=
pv6-address-space</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Aria=
l"> &nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/ipv6-anycast-addresses">http://www.iana.org/assignmen=
ts/ipv6-anycast-addresses</a></FONT><FONT FACE=3D"Calibri, Verdana, Helveti=
ca, Arial"> &nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/iana-ipv6-special-registry">http://www.iana.org/assig=
nments/iana-ipv6-special-registry</a></FONT><FONT FACE=3D"Calibri, Verdana,=
 Helvetica, Arial"> &nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/ipv6-unicast-address-assignments">http://www.iana.org=
/assignments/ipv6-unicast-address-assignments</a><BR>
</FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> </FONT><FONT FACE=
=3D"Verdana, Helvetica, Arial"><a href=3D"http://www.iana.org/assignments/i=
pv6-parameters">http://www.iana.org/assignments/ipv6-parameters</a></FONT><=
FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> &nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/ipv6-tla-assignments">http://www.iana.org/assignments=
/ipv6-tla-assignments</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, =
Arial"> &nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/isns-parameters">http://www.iana.org/assignments/isns=
-parameters</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> &n=
bsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/idxp-options">http://www.iana.org/assignments/idxp-op=
tions</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> &nbsp;&n=
bsp;&nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/isis-tlv-codepoints">http://www.iana.org/assignments/=
isis-tlv-codepoints</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Ar=
ial"> &nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/language-tags">http://www.iana.org/assignments/langua=
ge-tags</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> &nbsp;=
<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/lmp-parameters">http://www.iana.org/assignments/lmp-p=
arameters</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> <BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/mtqp-options">http://www.iana.org/assignments/mtqp-op=
tions</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> &nbsp;<B=
R>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/milnet-parameters">http://www.iana.org/assignments/mi=
lnet-parameters</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
> &nbsp;&nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/mpls-id-type">http://www.iana.org/assignments/mpls-id=
-type</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> &nbsp;<B=
R>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/text-directory-registrations">http://www.iana.org/ass=
ignments/text-directory-registrations</a></FONT><FONT FACE=3D"Calibri, Verd=
ana, Helvetica, Arial"> &nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/pppoe-parameters">http://www.iana.org/assignments/ppp=
oe-parameters</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> =
&nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/port-numbers">http://www.iana.org/assignments/port-nu=
mbers</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> &nbsp;<B=
R>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/pwe3-parameters">http://www.iana.org/assignments/pwe3=
-parameters</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> &n=
bsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/public-data-network-numbers">http://www.iana.org/assi=
gnments/public-data-network-numbers</a><BR>
</FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> </FONT><FONT FACE=
=3D"Verdana, Helvetica, Arial"><a href=3D"http://www.iana.org/assignments/r=
mt-fec-parameters">http://www.iana.org/assignments/rmt-fec-parameters</a></=
FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> &nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/rsvp-parameters">http://www.iana.org/assignments/rsvp=
-parameters</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> &n=
bsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/ssh-parameters">http://www.iana.org/assignments/ssh-p=
arameters</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> &nbs=
p;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/svrloc-cryptographic-bsd">http://www.iana.org/assignm=
ents/svrloc-cryptographic-bsd</a></FONT><FONT FACE=3D"Calibri, Verdana, Hel=
vetica, Arial"> &nbsp;&nbsp;&nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/svrloc-error-numbers">http://www.iana.org/assignments=
/svrloc-error-numbers</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, =
Arial"> &nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/service-names">http://www.iana.org/assignments/servic=
e-names</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> &nbsp;=
<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/sip-table">http://www.iana.org/assignments/sip-table<=
/a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> &nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/sip-priv-values">http://www.iana.org/assignments/sip-=
priv-values</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> &n=
bsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/sieve-extensions">http://www.iana.org/assignments/sie=
ve-extensions</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> =
&nbsp;&nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/sieve-environment-items">http://www.iana.org/assignme=
nts/sieve-environment-items</a></FONT><FONT FACE=3D"Calibri, Verdana, Helve=
tica, Arial"> &nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/sasl-mechanisms">http://www.iana.org/assignments/sasl=
-mechanisms</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> <B=
R>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/smtp-enhanced-status-codes">http://www.iana.org/assig=
nments/smtp-enhanced-status-codes</a></FONT><FONT FACE=3D"Calibri, Verdana,=
 Helvetica, Arial"> &nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/snmp-number-spaces">http://www.iana.org/assignments/s=
nmp-number-spaces</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Aria=
l"> &nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/sun-rpc-numbers">http://www.iana.org/assignments/sun-=
rpc-numbers</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> &n=
bsp;&nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/tcp-header-flags">http://www.iana.org/assignments/tcp=
-header-flags</a></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> =
&nbsp;<BR>
&nbsp;</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><a href=3D"http://www=
.iana.org/assignments/sdp-security-descriptions">http://www.iana.org/assign=
ments/sdp-security-descriptions</a></FONT><FONT FACE=3D"Calibri, Verdana, H=
elvetica, Arial"><BR>
</FONT></SPAN>
</BODY>
</HTML>


--_000_CA4E3BF032F65michellecottonicannorg_--

From marka@isc.org  Thu Jul 21 20:43: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 9047711E8079 for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 20:43:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.607
X-Spam-Level: 
X-Spam-Status: No, score=-2.607 tagged_above=-999 required=5 tests=[AWL=-0.008, 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 QoNagKn6ilCB for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 20:43:46 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id B9B7811E808C for <ietf@ietf.org>; Thu, 21 Jul 2011 20:43: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.pao1.isc.org (Postfix) with ESMTPS id 96D30C942B; Fri, 22 Jul 2011 03:43: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 F1C30216C7B; Fri, 22 Jul 2011 03:43: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 8CD841212A79; Fri, 22 Jul 2011 13:43:32 +1000 (EST)
To: Keith Moore <moore@network-heretics.com>
From: Mark Andrews <marka@isc.org>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <4E28C035.6020009@necom830.hpcl.titech.ac.jp> <20110722021627.48D811211E54@drugs.dv.isc.org> <0DD53760-9B8A-4569-8C67-81421A8A24B6@network-heretics.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
In-reply-to: Your message of "Thu, 21 Jul 2011 23:17:39 -0400." <0DD53760-9B8A-4569-8C67-81421A8A24B6@network-heretics.com>
Date: Fri, 22 Jul 2011 13:43:32 +1000
Message-Id: <20110722034332.8CD841212A79@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, 22 Jul 2011 03:43:46 -0000

In message <0DD53760-9B8A-4569-8C67-81421A8A24B6@network-heretics.com>, Keith M
oore writes:
> On Jul 21, 2011, at 10:16 PM, Mark Andrews wrote:
> 
> >=20
> > In message <4E28C035.6020009@necom830.hpcl.titech.ac.jp>, Masataka =
> Ohta writes:
> >> Dave Cridland wrote:
> >>=20
> >>> It's proven impossible, despite effort, to retrofit SRV onto HTTP;
> >>=20
> >> Where is a proof?
> >>=20
> >> 						Masataka Ohta
> >=20
> > Transitioning HTTP to use SRV is trivial even with proxies.
> >=20
> > Transitioning HTTPS to use SRV is complicated because of proxies.
> > There needs to be changes to how clients talk to proxies for HTTPS
> > + SRV to work through proxies.
> >=20
> > HTTP and HTTPS's use of the DNS is a abomination.  CNAME is totally
> > misused.  If you want to host a service on another machine you use
> > a record that indicates that.  You don't use a alias because aliases
> > mean so much more.
> >=20
> > Getting back to WS and SRV, WS needs to be SRV aware from day one
> > or it needs its own type in the DNS.  If you don't have SRV records
> > then you fallback to straight address records.
> 
> I'm fairly convinced that in the vast majority of cases, SRV is a bad =
> idea.  DNS is already too out of sync from hosts in many situations; SRV =
> just makes the situation worse.  Or to put it another way, if you want =
> to give every DNS admin the ability to impose fine-grained control over =
> what all of the hosts named by his DNS zones can do, deploy SRV =
> universally.  There are situations where this makes sense, but overall, =
> giving that level of control to DNS administrators is an extremely bad =
> idea.

What a load of FUD.  SRV records are no differnet to CNAME/MX records
in terms of control.  We don't shy away from adding MX records for
email or CNAME records for HTTP when CNAME is used a SRV equivalent.

Note even with SRV you have fallback to A/AAAA records when no SRV
record is present.

> That said, if this protocol is going to use SRV, it absolutely needs to =
> do it from day one.  There's no way to retro-fit SRV to most protocols =
> without breaking compatibility with existing implementations of those =
> protocols.
> 
> 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 Jul 21 21:32: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 753AC11E8075 for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 21:32: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=[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 uYwHODxzrsK4 for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 21:32:39 -0700 (PDT)
Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id 77F2B21F85C4 for <ietf@ietf.org>; Thu, 21 Jul 2011 21:32:39 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 8BACF209CA; Fri, 22 Jul 2011 00:32:38 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Fri, 22 Jul 2011 00:32: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=1rxuUbC47S9tne1fWrJqi284C+g=; b=a9 73EbBPc3XMr2sAw8r080CoGT0elD7qcR2RCdN6pUdDCqCEBt+rIcuxeuflYhFe4W l8fnw1Mxnc0c7lMFsLkt3P0aDpzfMr3pdn2cOSWk5vHkQXEwbBRK9vdE0v5QTfUH N1lDcPJTfaerusXtQ7aygcBh7jbE+Yay+uNTQefo4=
X-Sasl-enc: RGZoOSD2LAnAGqoxweON25NCOyPIYmRXp4jw1aEXZse+ 1311309156
Received: from [10.59.1.76] (static-71-166-174-114.washdc.east.verizon.net [71.166.174.114]) by mail.messagingengine.com (Postfix) with ESMTPA id E85B74119C7; Fri, 22 Jul 2011 00:32:33 -0400 (EDT)
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
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: <20110722034332.8CD841212A79@drugs.dv.isc.org>
Date: Fri, 22 Jul 2011 00:32:23 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E7507334-3515-4764-A0E7-2DA42C98ECE3@network-heretics.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <4E28C035.6020009@necom830.hpcl.titech.ac.jp> <20110722021627.48D811211E54@drugs.dv.isc.org> <0DD53760-9B8A-4569-8C67-81421A8A24B6@network-heretics.com> <20110722034332.8CD841212A79@drugs.dv.isc.org>
To: Mark Andrews <marka@isc.org>
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, 22 Jul 2011 04:32:40 -0000

On Jul 21, 2011, at 11:43 PM, Mark Andrews wrote:

>> I'm fairly convinced that in the vast majority of cases, SRV is a bad =
=3D
>> idea.  DNS is already too out of sync from hosts in many situations; =
SRV =3D
>> just makes the situation worse.  Or to put it another way, if you =
want =3D
>> to give every DNS admin the ability to impose fine-grained control =
over =3D
>> what all of the hosts named by his DNS zones can do, deploy SRV =3D
>> universally.  There are situations where this makes sense, but =
overall, =3D
>> giving that level of control to DNS administrators is an extremely =
bad =3D
>> idea.
>=20
> What a load of FUD.  SRV records are no differnet to CNAME/MX records
> in terms of control.  We don't shy away from adding MX records for
> email or CNAME records for HTTP when CNAME is used a SRV equivalent.

SRV records at first glance like a straightforward generalization of MX =
records.  But in a sense, that's the problem.  One danger of SRV records =
is that because they are generic, people keep thinking that they should =
be retroactively applied to all protocols, whether it makes sense or =
not.  This is a huge slippery slope.  Not only is there a potential for =
SRV records to be applied to protocols for which they aren't well suited =
(which is to say, most protocols), but there will also be a temptation =
to use SRV to route traffic through NATs that do port mapping, by =
changing the ports on which those protocols operate from their defaults. =
 Combine this with multi-faced DNS, so that the port that a peer uses to =
talk to a service will vary according to from where the DNS query was =
made, and you get a huge mess.

A related problem is due to the tension between DNS names as hostnames, =
and DNS names as names for things besides hosts.   DNS started out =
(quite deliberately) as a system for naming only hosts, and it still =
reflects that heritage in several ways.   But people keep using it, =
understandably, to name services rather than hosts, or sometimes to use =
the same name both.  When a DNS name is exclusively used to associate a =
name with an IP address or set of IP addresses that provide a single =
service, that's not a problem.  But when a DNS name is used in some =
contexts to name a host and in other contexts to name a service, that =
invites problems.  When people take a DNS name that is used to name a =
host and then add SRV records for the same name, unless it's done very =
carefully, that disrupts use of that DNS name to refer to the host and =
protocol servers at that host. =20

For email and MX records, it didn't make such a big difference because =
by the time MX records were in widespread use, workstations were =
replacing larger multiuser machines and it became natural to want to =
associate several hosts with a single email server and map all of them =
to a single email domain.   But that's a very specific use case.  MX =
records, in practice, really don't change the behavior of a protocol or =
host so much as allow domain names to be used for a purpose other than =
to name hosts - namely to associate email addresses from that domain =
with one or more SMTP servers willing to receive mail for them. =20

(Even then, the problem of MX records being out of sync with the SMTP =
servers does exist, and used to be a significant source of mail delivery =
errors.)

CNAMEs are a mess for other reasons.  But at least they don't give DNS =
admins fine-grained control over individual protocols and services.  If =
the CNAME is screwed up, it's screwed up for everything associated with =
that domain.  That tends to call more attention to the problem.

> Note even with SRV you have fallback to A/AAAA records when no SRV
> record is present.

Right, but the DNS admin can blackhole or reroute traffic for your host =
by installing a SRV record that you don't want or that doesn't match =
reality.   Bad architecture.  There's a place for access controls and =
traffic filters, but it's not in DNS.

Keith



From narten@us.ibm.com  Thu Jul 21 21:53:16 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 8E4EE21F85CE for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 21:53:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.561
X-Spam-Level: 
X-Spam-Status: No, score=-106.561 tagged_above=-999 required=5 tests=[AWL=0.038, 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 72vYGJjmHGDC for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 21:53:15 -0700 (PDT)
Received: from e2.ny.us.ibm.com (e2.ny.us.ibm.com [32.97.182.142]) by ietfa.amsl.com (Postfix) with ESMTP id 8453321F85C7 for <ietf@ietf.org>; Thu, 21 Jul 2011 21:53:15 -0700 (PDT)
Received: from d01relay06.pok.ibm.com (d01relay06.pok.ibm.com [9.56.227.116]) by e2.ny.us.ibm.com (8.14.4/8.13.1) with ESMTP id p6M4VqFU010779 for <ietf@ietf.org>; Fri, 22 Jul 2011 00:31:52 -0400
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay06.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p6M4r3WS1507578 for <ietf@ietf.org>; Fri, 22 Jul 2011 00:53:03 -0400
Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p6M4r3iP014906 for <ietf@ietf.org>; Fri, 22 Jul 2011 00:53:03 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p6M4r2m4014899 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 22 Jul 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 p6M4r27r015636 for <ietf@ietf.org>; Fri, 22 Jul 2011 00:53:02 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p6M4r1xx015600 for ietf@ietf.org; Fri, 22 Jul 2011 00:53:01 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201107220453.p6M4r1xx015600@rotala.raleigh.ibm.com>
Date: Fri, 22 Jul 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, 22 Jul 2011 04:53:16 -0000

Total of 125 messages in the last 7 days.
 
script run at: Fri Jul 22 00:53:01 EDT 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  8.80% |   11 |  8.85% |    75151 | john-ietf@jck.com
  5.60% |    7 |  8.49% |    72097 | moore@network-heretics.com
  5.60% |    7 |  6.02% |    51146 | dave@cridland.net
  4.00% |    5 |  7.36% |    62511 | dendicott@gmail.com
  5.60% |    7 |  4.70% |    39891 | ibc@aliax.net
  4.80% |    6 |  4.29% |    36398 | harald@alvestrand.no
  4.00% |    5 |  3.83% |    32540 | joelja@bogus.com
  3.20% |    4 |  2.71% |    23007 | mail@sabahattin-gucukoglu.com
  2.40% |    3 |  2.49% |    21103 | dougb@dougbarton.us
  2.40% |    3 |  2.30% |    19547 | marka@isc.org
  2.40% |    3 |  1.71% |    14536 | dworley@avaya.com
  2.40% |    3 |  1.53% |    13029 | ynir@checkpoint.com
  0.80% |    1 |  2.56% |    21694 | michelle.cotton@icann.org
  1.60% |    2 |  1.74% |    14783 | rbonica@juniper.net
  1.60% |    2 |  1.66% |    14080 | evnikita2@gmail.com
  1.60% |    2 |  1.64% |    13933 | w@1wt.eu
  1.60% |    2 |  1.37% |    11612 | nsb@guppylake.com
  1.60% |    2 |  1.31% |    11165 | fred.l.templin@boeing.com
  1.60% |    2 |  1.22% |    10347 | brian.e.carpenter@gmail.com
  1.60% |    2 |  1.14% |     9703 | ned+ietf@mauve.mrochek.com
  1.60% |    2 |  1.12% |     9521 | msk@cloudmark.com
  1.60% |    2 |  1.12% |     9506 | barryleiba@computer.org
  1.60% |    2 |  1.06% |     9010 | julian.reschke@gmx.de
  1.60% |    2 |  1.02% |     8643 | wjhns1@hardakers.net
  0.80% |    1 |  1.48% |    12581 | lars.eggert@nokia.com
  0.80% |    1 |  1.45% |    12317 | nkukich@verilan.com
  0.80% |    1 |  1.12% |     9475 | hideki.endo.es@hitachi.com
  0.80% |    1 |  1.10% |     9351 | tfl@psp.co.uk
  0.80% |    1 |  1.09% |     9255 | john@jck.com
  0.80% |    1 |  1.06% |     8981 | narten@us.ibm.com
  0.80% |    1 |  1.04% |     8806 | kathleen.moriarty@emc.com
  0.80% |    1 |  0.97% |     8212 | alexey.melnikov@isode.com
  0.80% |    1 |  0.96% |     8120 | david.black@emc.com
  0.80% |    1 |  0.91% |     7693 | rbarnes@bbn.com
  0.80% |    1 |  0.87% |     7427 | daedulus@btconnect.com
  0.80% |    1 |  0.83% |     7039 | sm@resistor.net
  0.80% |    1 |  0.81% |     6900 | nomcom-chair@ietf.org
  0.80% |    1 |  0.79% |     6681 | rogerj@gmail.com
  0.80% |    1 |  0.70% |     5926 | dhc@dcrocker.net
  0.80% |    1 |  0.69% |     5864 | jhw@apple.com
  0.80% |    1 |  0.68% |     5779 | samirs.lists@gmail.com
  0.80% |    1 |  0.67% |     5683 | kpfleming@digium.com
  0.80% |    1 |  0.65% |     5529 | amorris@amsl.com
  0.80% |    1 |  0.65% |     5518 | ek@google.com
  0.80% |    1 |  0.64% |     5450 | ted.lemon@nominum.com
  0.80% |    1 |  0.64% |     5394 | rsk@gsp.org
  0.80% |    1 |  0.63% |     5311 | vesely@tana.it
  0.80% |    1 |  0.63% |     5307 | francis@aspl.es
  0.80% |    1 |  0.61% |     5174 | dwm@xpasc.com
  0.80% |    1 |  0.59% |     5050 | shanna@juniper.net
  0.80% |    1 |  0.58% |     4960 | ben@nostrum.com
  0.80% |    1 |  0.58% |     4938 | d3e3e3@gmail.com
  0.80% |    1 |  0.57% |     4809 | jmh@joelhalpern.com
  0.80% |    1 |  0.57% |     4799 | mcr@sandelman.ca
  0.80% |    1 |  0.55% |     4682 | pch-v6ops@u-1.phicoh.com
  0.80% |    1 |  0.55% |     4673 | olaf@nlnetlabs.nl
  0.80% |    1 |  0.55% |     4643 | jnc@mercury.lcs.mit.edu
  0.80% |    1 |  0.54% |     4566 | petithug@acm.org
  0.80% |    1 |  0.53% |     4473 | bertietf@bwijnen.net
  0.80% |    1 |  0.50% |     4274 | johnl@iecc.com
  0.80% |    1 |  0.50% |     4234 | paul.hoffman@vpnc.org
  0.80% |    1 |  0.50% |     4224 | mohta@necom830.hpcl.titech.ac.jp
--------+------+--------+----------+------------------------
100.00% |  125 |100.00% |   849051 | Total

From mohta@necom830.hpcl.titech.ac.jp  Thu Jul 21 22:02:54 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 BFC9C1F0C37 for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 22:02:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.089
X-Spam-Level: 
X-Spam-Status: No, score=-0.089 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, WEIRD_PORT=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 XcsHwdkMDli9 for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 22:02:54 -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 EE9911F0C36 for <ietf@ietf.org>; Thu, 21 Jul 2011 22:02:53 -0700 (PDT)
Received: (qmail 22079 invoked from network); 22 Jul 2011 05:21:11 -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; 22 Jul 2011 05:21:11 -0000
Message-ID: <4E290442.3010402@necom830.hpcl.titech.ac.jp>
Date: Fri, 22 Jul 2011 14:01:54 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
Subject: SRV and http(s) (was Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard)
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <4E28C035.6020009@necom830.hpcl.titech.ac.jp> <20110722021627.48D811211E54@drugs.dv.isc.org>
In-Reply-To: <20110722021627.48D811211E54@drugs.dv.isc.org>
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: Fri, 22 Jul 2011 05:02:54 -0000

Mark Andrews wrote:

> Transitioning HTTP to use SRV is trivial even with proxies.
> 
> Transitioning HTTPS to use SRV is complicated because of proxies.
> There needs to be changes to how clients talk to proxies for HTTPS
> + SRV to work through proxies.

What's wrong with:

   https://www.example.com
   _https._tcp.www.example.com SRV 0 1 100 server.example.org

   CONNECT server.example.org:100 HTTP/1.1
   Host: www.example.com

?

> HTTP and HTTPS's use of the DNS is a abomination.  CNAME is totally
> misused.  If you want to host a service on another machine you use
> a record that indicates that.  You don't use a alias because aliases
> mean so much more.

What's wrong with:

   https://www.example.com
   _https._tcp.www.example.com SRV 0 1 100 server.example.org
   server.example.org CNAME cname.example.org

   CONNECT server.example.org:100 HTTP/1.1
   Host: www.example.com

?

						Masataka Ohta


From marka@isc.org  Thu Jul 21 22:48:03 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 0C47721F86DC for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 22:48:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.606
X-Spam-Level: 
X-Spam-Status: No, score=-2.606 tagged_above=-999 required=5 tests=[AWL=-0.008, BAYES_00=-2.599, WEIRD_PORT=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 9dPPXSphAlql for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 22:48:02 -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 43F7F21F86D1 for <ietf@ietf.org>; Thu, 21 Jul 2011 22:48:02 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.pao1.isc.org (Postfix) with ESMTPS id CB7ECC9463; Fri, 22 Jul 2011 05:47:51 +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 3456E216C81; Fri, 22 Jul 2011 05:47:49 +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 967CA1213BE5; Fri, 22 Jul 2011 15:47:39 +1000 (EST)
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
From: Mark Andrews <marka@isc.org>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <4E28C035.6020009@necom830.hpcl.titech.ac.jp> <20110722021627.48D811211E54@drugs.dv.isc.org> <4E290442.3010402@necom830.hpcl.titech.ac.jp>
Subject: Re: SRV and http(s) (was Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard)
In-reply-to: Your message of "Fri, 22 Jul 2011 14:01:54 +0900." <4E290442.3010402@necom830.hpcl.titech.ac.jp>
Date: Fri, 22 Jul 2011 15:47:39 +1000
Message-Id: <20110722054739.967CA1213BE5@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, 22 Jul 2011 05:48:03 -0000

In message <4E290442.3010402@necom830.hpcl.titech.ac.jp>, Masataka Ohta writes:
> Mark Andrews wrote:
> 
> > Transitioning HTTP to use SRV is trivial even with proxies.
> > 
> > Transitioning HTTPS to use SRV is complicated because of proxies.
> > There needs to be changes to how clients talk to proxies for HTTPS
> > + SRV to work through proxies.
> 
> What's wrong with:
> 
>    https://www.example.com
>    _https._tcp.www.example.com SRV 0 1 100 server.example.org
> 
>    CONNECT server.example.org:100 HTTP/1.1
>    Host: www.example.com
> 
> ?
> 
> > HTTP and HTTPS's use of the DNS is a abomination.  CNAME is totally
> > misused.  If you want to host a service on another machine you use
> > a record that indicates that.  You don't use a alias because aliases
> > mean so much more.
> 
> What's wrong with:
> 
>    https://www.example.com
>    _https._tcp.www.example.com SRV 0 1 100 server.example.org
>    server.example.org CNAME cname.example.org

Firstly SRV is not (yet) defined for HTTP.
 
>    CONNECT server.example.org:100 HTTP/1.1
>    Host: www.example.com

I was referring to this sort of misuse.

	www.example.com CNAME server.web-hosting-service.com.

www.example.com really isn't a alias for server.web-hosting-service.com
If it was you could replace "www.example.com" with
"server.web-hosting-service.com" and be served the same content.

Or this misuse

	example.com SOA ...
	example.com MX ...
	example.com CNAME server.web-hosting-service.com.

which people try to do and causes all sort of problems.

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

From dave@cridland.net  Fri Jul 22 02:51:14 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 68FC421F8511 for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 02:51:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level: 
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.062,  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 NEFIm2VawS+b for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 02:51:13 -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 7F0A621F84E3 for <ietf@ietf.org>; Fri, 22 Jul 2011 02:51:13 -0700 (PDT)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id 94D351168087; Fri, 22 Jul 2011 10:51:10 +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 MJSOODCLzQSs; Fri, 22 Jul 2011 10:51:08 +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 2D6151168067; Fri, 22 Jul 2011 10:51:08 +0100 (BST)
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <4E28C035.6020009@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4E28C035.6020009@necom830.hpcl.titech.ac.jp>
MIME-Version: 1.0
Message-Id: <9031.1311328268.180517@puncture>
Date: Fri, 22 Jul 2011 10:51:08 +0100
From: Dave Cridland <dave@cridland.net>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>, 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: Fri, 22 Jul 2011 09:51:14 -0000

On Fri Jul 22 01:11:33 2011, Masataka Ohta wrote:
> Dave Cridland wrote:
> 
> > It's proven impossible, despite effort, to retrofit SRV onto HTTP;
> 
> Where is a proof?

Sorry, I've a habit of using the word "proof" in the English (and  
indeed Welsh) sense of "test" or "trial", rather than the  
mathematical sense of the statement backed up by logic.

I should simply say that there have been attempts (I recall more than  
one draft), but the situation is sufficiently entrenched that these  
have gained no traction, in no small part because of the requirement  
for something close to a flag day.

1) There are no SRV records.

2) Therefore browsers do not support them.

3) Therefore you'd need to allow for A-lookup as fallback for the  
forseeable future.

4) Therefore there's no incentive for browsers to support SRV.

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 dave@cridland.net  Fri Jul 22 02:55:23 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 AB9EB21F86C2; Fri, 22 Jul 2011 02:55:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.541
X-Spam-Level: 
X-Spam-Status: No, score=-2.541 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 kr7y30RuRKk7; Fri, 22 Jul 2011 02:55:23 -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 CE2A321F85CB; Fri, 22 Jul 2011 02:55:22 -0700 (PDT)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id B8CAF1168087; Fri, 22 Jul 2011 10:55:21 +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 oCuxDbsSXm6q; Fri, 22 Jul 2011 10:55:19 +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 785201168067; Fri, 22 Jul 2011 10:55:19 +0100 (BST)
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <9031.1311286867.939466@puncture> <4E28BA9D.6010501@callenish.com> <CAP992=GedTEfimykCWwdwm=BsZdwFRJO36EO0a_o7iejURJ+tQ@mail.gmail.com>
In-Reply-To: <CAP992=GedTEfimykCWwdwm=BsZdwFRJO36EO0a_o7iejURJ+tQ@mail.gmail.com>
MIME-Version: 1.0
Message-Id: <9031.1311328519.488604@puncture>
Date: Fri, 22 Jul 2011 10:55:19 +0100
From: Dave Cridland <dave@cridland.net>
To: David Endicott <dendicott@gmail.com>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>, Bruce Atherton <bruce@callenish.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, 22 Jul 2011 09:55:23 -0000

On Fri Jul 22 03:24:41 2011, David Endicott wrote:
> there are added inefficiencies.   Also the name resolution of the  
> HTTP that
> serves the Javascript that opens the WS should remain constant.    
> If WS
> resolves the host/domain to a different address than the HTTP it  
> was spawned
> from, it becomes a method to bypass same-origin / CORS restrictions.

That's an unfortunate misunderstanding.

All protocols that use SRV records maintain the target domain.

So a ws://example.com/xyz would still send a Host header of  
"example.com", whether SRV or not, so there is no impact on same  
origin policy, CORS, etc.

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 evnikita2@gmail.com  Fri Jul 22 03:16: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 171CD21F86E9 for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 03:16:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.512
X-Spam-Level: 
X-Spam-Status: No, score=-3.512 tagged_above=-999 required=5 tests=[AWL=0.087,  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 Ai8EaN26fetZ for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 03:16:03 -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 9097221F86BE for <ietf@ietf.org>; Fri, 22 Jul 2011 03:16:02 -0700 (PDT)
Received: by fxe4 with SMTP id 4so5800186fxe.27 for <ietf@ietf.org>; Fri, 22 Jul 2011 03:16:00 -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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=G0VelP0W+chjOaZJORxHuH3VwMXDWDI5OdwmF0uU8V0=; b=AOpdgUNZ2NLB7ehj8iBzt0/9AdzqTKRb1JV3oQk2tiwXAiKJH36NE0fcKLFC9PVYLf ET2wTGjfSMlsGthrfWZ+1NAemN3sRQuCp8J9c4rnzPziiaX8xUyP+8JrTtBEZg/Jzj/Z VGDTfw03/KDh7GfU8QF/IfEACHytey++plA8Y=
Received: by 10.205.83.2 with SMTP id ae2mr400674bkc.313.1311329760244; Fri, 22 Jul 2011 03:16:00 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id t19sm215912bku.7.2011.07.22.03.15.58 (version=SSLv3 cipher=OTHER); Fri, 22 Jul 2011 03:15:59 -0700 (PDT)
Message-ID: <4E294E09.60507@gmail.com>
Date: Fri, 22 Jul 2011 13:16:41 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Historic status (was Another look at 6to4 (and other IPv6 transition issues))
References: <20110718153337.C849F18C08C@mercury.lcs.mit.edu>
In-Reply-To: <20110718153337.C849F18C08C@mercury.lcs.mit.edu>
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, 22 Jul 2011 10:16:04 -0000

Noel and all,

The meaning of Historic has alway been a bit unclear.  Neither 2026 nor 
its predecessors say enough about this category for RFCs; particularly, 
it fails to describe what are the procedures for moving RFCs to 
Historic, whether one is allowed to publish documents directly to 
Historic, what RFCs may be historicized etc.  The current IESG statement 
clears up one of these issues, ie. how to move IETF Stream RFCs to 
Historic; but what does it actually means was limited to the following 
pieces of text from RFC 2026:

1)
>     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.  (Purists have suggested that the
>     word should be "Historical"; however, at this point the use of
>     "Historic" is historical.)
2)
>     A specification may have been superseded by a more recent
>     Internet Standard, or have otherwise fallen into disuse or disfavor.
(not explicitly stated; may be deduced from the meaning that Historic is 
described)
3)
>     Following each such review, the IESG
>     shall approve termination or continuation of the development effort,
>     at the same time the IESG shall decide to maintain the specification
>     at the same maturity level or to move it to Historic status.
(from Section 6.2)
4)
>     Once the new version has reached the
>     Standard level, it will usually replace the previous version, which
>     will be moved to Historic status.
5)
>     In this case, or when it is felt for some other
>     reason that an existing standards track specification should be
>     retired, the IESG shall approve a change of status of the old
>     specification(s) to Historic.
The cited extracts generally assume that Historic is mostly used to mark 
documents removed from Standards Track in order to denote that they are 
not Internet Standard at any maturity level any more and new 
implementations should not depend on Historic RFCs.  Currently Historic 
is considered in a bit an other way (see below); eg. Experimental and 
Informational documents are also moved to Historic freely (see eg. RFC 
6247), even though they have no relationship to Standards Track and it's 
fully up to the implementor to evaluate the protocol and decide whether 
to implement or not implement it (unlike Standards Track, which was 
intended as "IETF recommends to use this").

RFC 4844 does not mention clearly, but Historic documents may 
occasionally be published by IETF (I also saw 2 Historic RFCs published 
by IRTF and a number - by Independent Submissions Editor) directly.  
Procedures for moving non-IETF-stream RFCs to Historic are still unclear.

There were some proposals regarding Historic; eg. the NEWTRK WG document 
(http://tools.ietf.org/id/draft-ietf-newtrk-cruft-00.txt), which is 
expired but was partly incorporated in IESG Statement on Historic 
(http://www.ietf.org/iesg/statement/designating-rfcs-as-historic.html), 
and my proposal 
(http://tools.ietf.org/html/draft-yevstifeyev-genarea-historic-03).  
None of them progressed further.

Some drafts registered by datatracker as "Internet Standards Process 
Rev. 4" (http://tools.ietf.org/id/draft-lear-ietf-rfc2026bis-00.txt and 
http://tools.ietf.org/id/draft-moonesamy-stds-process-00.txt) also say 
extremely little about Historic status compared with 2026. 
http://tools.ietf.org/id/draft-carpenter-rfc2026-changes-02.txt, Section 
3.12 proposed to change current Historic description to:
>     A specification that has been superseded by a more recent
>     specification or is for any other reason considered to be obsolete
>     may be assigned to the "Historic" level by the IESG.  (Purists have
>     suggested that the word should be "Historical"; however, at this
>     point the use of "Historic" is historical.)
assuming that any RFC may be moved to Historic by IESG, overlooking 
other streams' authorities (this draft was issued in 2008, long after 
RFC 4844).  This draft wasn't ultimately processed, even though it 
entered IESG review.

So what's the meaning of Historic?  As Ronald mentioned, the formulation 
"to be obsolete" in RFC 2026 may be understood differently; one may 
think that it means "nobody uses the protocol", which is impossible to 
determine and then say for sure.  The second person may think that "the 
protocol's possibilities may safely be provided by other protocol", 
which is easier to determine, but applying such definition might create 
problems with interoperability.  The third opinion may be "the protocol 
is known to have technical/security/other omissions and its use should 
be discouraged".   The others may also have other views on Historic, 
which does not facilitate the Internet Standards process.

And what could/should be done?  I think, IESG and the whole community, 
cooperating with IAB, IRSG and ISE, should determine the definition of 
Historic which will be fine enough to cover all existing issues with it, 
and then either publish such approach as BCP or incorporate when 
updating RFC 2026.  This will eliminate the problems with different 
issues with procedures for and understanding of Historic RFCs as well as 
clear up one of "dark places" in IETF process.

Of course, just my opinion.
Mykyta Yevstifeyev

18.07.2011 18:33, Noel Chiappa wrote:
>      >  From: Ronald Bonica<rbonica@juniper.net>
>
>      >  RFC 2026's very terse definition of HISTORIC. According to RFC 2026,
>      >  "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." That's the entire definition.
>      >  Anything more is read into it.
>      >  ...
>      >  A more likely interpretation is as follows:
>      >  "the IETF is not likely to invest effort in the technology in the
>      >  	future"
>      >  "the IETF does not encourage (or discourage) new deployments of this
>      >  	technology.
>
> But in giving other interpretations, are you thereby not comitting the
> exact error you call out above: "Anything more is read into it."?
>
> To me, "Historic" has always (including pre-2026) meant just what the
> orginal meaning of the word is (caveat - see below) - something that is
> now likely only of interest to people who are looking into the history of
> networking. (The dictionary definition is "Based on or concerned with
> events in history".) I think "obsolete" is probably the best one-word
> description (and note that 'obsolete' != 'obsolescent').
>
> (Caveat: technically, it probably should have been 'historical', not
> "historic" - "historic" actually means 'in the past, but very noteworthy',
> e.g.  'CYCLADES was a historic networking design', so not every historical
> protocol is historic.)
>
> 	Noel
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>



From mohta@necom830.hpcl.titech.ac.jp  Fri Jul 22 03:31:32 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 E1BAF21F85C4 for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 03:31:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.211
X-Spam-Level: 
X-Spam-Status: No, score=0.211 tagged_above=-999 required=5 tests=[AWL=-0.300,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_53=0.6, WEIRD_PORT=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 mFKqYpgOLsy1 for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 03:31:32 -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 EB4E621F853B for <ietf@ietf.org>; Fri, 22 Jul 2011 03:31:31 -0700 (PDT)
Received: (qmail 25456 invoked from network); 22 Jul 2011 10:49:52 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 22 Jul 2011 10:49:52 -0000
Message-ID: <4E29514C.8010204@necom830.hpcl.titech.ac.jp>
Date: Fri, 22 Jul 2011 19:30:36 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
Subject: Re: SRV and http(s) (was Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard)
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <4E28C035.6020009@necom830.hpcl.titech.ac.jp> <20110722021627.48D811211E54@drugs.dv.isc.org> <4E290442.3010402@necom830.hpcl.titech.ac.jp> <20110722054739.967CA1213BE5@drugs.dv.isc.org>
In-Reply-To: <20110722054739.967CA1213BE5@drugs.dv.isc.org>
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: Fri, 22 Jul 2011 10:31:33 -0000

Mark Andrews wrote:

>>> Transitioning HTTPS to use SRV is complicated because of proxies.
>>> There needs to be changes to how clients talk to proxies for HTTPS
>>> + SRV to work through proxies.
>>     CONNECT server.example.org:100 HTTP/1.1
>>     Host: www.example.com
> 
> I was referring to this sort of misuse.
> 
> 	www.example.com CNAME server.web-hosting-service.com.
> 
> www.example.com really isn't a alias for server.web-hosting-service.com
> If it was you could replace "www.example.com" with
> "server.web-hosting-service.com" and be served the same content.
>
> Or this misuse
>
> 	example.com SOA ...
> 	example.com MX ...
> 	example.com CNAME server.web-hosting-service.com.

Do you mean there is no complication of HTTPS+SRV by proxies?

> which people try to do and causes all sort of problems.

Your examples just do not work for people, which will drive them
solve their own problems by themselves.

						Masataka Ohta

From mohta@necom830.hpcl.titech.ac.jp  Fri Jul 22 03:35:23 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 F391621F8786 for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 03:35:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.07
X-Spam-Level: 
X-Spam-Status: No, score=-0.07 tagged_above=-999 required=5 tests=[AWL=0.020,  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 V8Xmd7gpu4Jm for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 03:35:22 -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 3B15F21F85F1 for <ietf@ietf.org>; Fri, 22 Jul 2011 03:35:22 -0700 (PDT)
Received: (qmail 25474 invoked from network); 22 Jul 2011 10:54:06 -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; 22 Jul 2011 10:54:06 -0000
Message-ID: <4E295249.5060700@necom830.hpcl.titech.ac.jp>
Date: Fri, 22 Jul 2011 19:34:49 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <4E28C035.6020009@necom830.hpcl.titech.ac.jp> <9031.1311328268.180517@puncture>
In-Reply-To: <9031.1311328268.180517@puncture>
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, 22 Jul 2011 10:35:23 -0000

Dave Cridland wrote:

>> Where is a proof?
> 
> Sorry, I've a habit of using the word "proof" in the English

> 1) There are no SRV records.
> 2) Therefore browsers do not support them.
> 3) Therefore you'd need to allow for A-lookup as fallback for the 
> forseeable future.
> 4) Therefore there's no incentive for browsers to support SRV.

That's a perfect proof against IPv6 deployment. Infrastructure
won't be updated.

However, for application layers issues like SRV ones, thanks to
the end to end argument, only servers and clients need
upgrading without infrastructure changes, which is why major
application of the Internet changed from ftp to http.

							Masataka Ohta

From i.grok@comcast.net  Fri Jul 22 05:31:18 2011
Return-Path: <i.grok@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 0472721F853A for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 05:31:18 -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 AmgGI2bSQler for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 05:31:17 -0700 (PDT)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16]) by ietfa.amsl.com (Postfix) with ESMTP id 623A721F850F for <ietf@ietf.org>; Fri, 22 Jul 2011 05:31:17 -0700 (PDT)
Received: from omta20.westchester.pa.mail.comcast.net ([76.96.62.71]) by qmta01.westchester.pa.mail.comcast.net with comcast id B0Sr1h00B1YDfWL510XHS6; Fri, 22 Jul 2011 12:31:17 +0000
Received: from odin.ulthar.us ([68.33.77.0]) by omta20.westchester.pa.mail.comcast.net with comcast id B0XG1h00p00PQ6U3g0XHhC; Fri, 22 Jul 2011 12:31:17 +0000
Received: from odin.ulthar.us (localhost [127.0.0.1]) by odin.ulthar.us (8.14.4/8.14.3) with ESMTP id p6MCVFBP018831 for <ietf@ietf.org>; Fri, 22 Jul 2011 08:31:15 -0400
Received: (from draco@localhost) by odin.ulthar.us (8.14.4/8.14.4/Submit) id p6MCVELh018829 for ietf@ietf.org; Fri, 22 Jul 2011 08:31:14 -0400
Date: Fri, 22 Jul 2011 08:31:14 -0400
From: Scott Schmit <i.grok@comcast.net>
To: ietf@ietf.org
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110722123114.GA6562@odin.ulthar.us>
Mail-Followup-To: ietf@ietf.org
References: <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <4E28C035.6020009@necom830.hpcl.titech.ac.jp> <9031.1311328268.180517@puncture> <4E295249.5060700@necom830.hpcl.titech.ac.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4E295249.5060700@necom830.hpcl.titech.ac.jp>
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, 22 Jul 2011 12:31:18 -0000

On Fri, Jul 22, 2011 at 07:34:49PM +0900, Masataka Ohta wrote:
> Dave Cridland wrote:
> 
> >> Where is a proof?
> > 
> > Sorry, I've a habit of using the word "proof" in the English
> 
> > 1) There are no SRV records.
> > 2) Therefore browsers do not support them.
> > 3) Therefore you'd need to allow for A-lookup as fallback for the 
> > forseeable future.
> > 4) Therefore there's no incentive for browsers to support SRV.
> 
> That's a perfect proof against IPv6 deployment. Infrastructure
> won't be updated.

Ironic you should mention that, because if more protocols supported SRV,
the content providers could have a lot more control over the IPv6
transition. For example:

_http._tcp.example.com. SRV 0 99 80 www.example.com.
_http._tcp.example.com. SRV 0 1 80 www-ds.example.com.
www.example.com. A 198.0.2.1
www-ds.example.com. A 198.0.2.2
www-ds.example.com. AAAA 2001:db8::2

I.e., content providers could control/measure their probability of
failure. As www-ds.example.com's success rate improves, its weight can
be increased.

-- 
Scott Schmit

From marka@isc.org  Fri Jul 22 05:41: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 4D6F221F856A for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 05:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.606
X-Spam-Level: 
X-Spam-Status: No, score=-2.606 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ntzBhSjo0Ohf for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 05:41:39 -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 7EA6C21F8513 for <ietf@ietf.org>; Fri, 22 Jul 2011 05:41:39 -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 A1FA3C9424; Fri, 22 Jul 2011 12:41:28 +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 36D8F216C7B; Fri, 22 Jul 2011 12:41: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 CF5F31217044; Fri, 22 Jul 2011 22:41:25 +1000 (EST)
To: Dave Cridland <dave@cridland.net>
From: Mark Andrews <marka@isc.org>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <4E28C035.6020009@necom830.hpcl.titech.ac.jp> <9031.1311328268.180517@puncture>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
In-reply-to: Your message of "Fri, 22 Jul 2011 10:51:08 +0100." <9031.1311328268.180517@puncture>
Date: Fri, 22 Jul 2011 22:41:25 +1000
Message-Id: <20110722124125.CF5F31217044@drugs.dv.isc.org>
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, 22 Jul 2011 12:41:40 -0000

In message <9031.1311328268.180517@puncture>, Dave Cridland writes:
> On Fri Jul 22 01:11:33 2011, Masataka Ohta wrote:
> > Dave Cridland wrote:
> > 
> > > It's proven impossible, despite effort, to retrofit SRV onto HTTP;
> > 
> > Where is a proof?
> 
> Sorry, I've a habit of using the word "proof" in the English (and  
> indeed Welsh) sense of "test" or "trial", rather than the  
> mathematical sense of the statement backed up by logic.
> 
> I should simply say that there have been attempts (I recall more than  
> one draft), but the situation is sufficiently entrenched that these  
> have gained no traction, in no small part because of the requirement  
> for something close to a flag day.

There is no need for a flag day.  If SRV support had been added
when first proposed there would be close to 100% by now.  Browsers
get regularly updated so there really is no reason to not add SRV
support.

The main reason to add SRV support is to provide indirection.

> 1) There are no SRV records.
> 
> 2) Therefore browsers do not support them.
> 
> 3) Therefore you'd need to allow for A-lookup as fallback for the  
> forseeable future.
> 
> 4) Therefore there's no incentive for browsers to support SRV.
>
> 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
> _______________________________________________
> 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 Jul 22 07:37:16 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 1382921F8786 for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 07:37:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.071
X-Spam-Level: 
X-Spam-Status: No, score=-0.071 tagged_above=-999 required=5 tests=[AWL=0.019,  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 JDwEedw+S2Dd for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 07:37:15 -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 B477221F86EE for <ietf@ietf.org>; Fri, 22 Jul 2011 07:37:08 -0700 (PDT)
Received: (qmail 27873 invoked from network); 22 Jul 2011 14:55:40 -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; 22 Jul 2011 14:55:40 -0000
Message-ID: <4E298ADA.2060209@necom830.hpcl.titech.ac.jp>
Date: Fri, 22 Jul 2011 23:36:10 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <4E28C035.6020009@necom830.hpcl.titech.ac.jp> <9031.1311328268.180517@puncture> <4E295249.5060700@necom830.hpcl.titech.ac.jp> <20110722123114.GA6562@odin.ulthar.us>
In-Reply-To: <20110722123114.GA6562@odin.ulthar.us>
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: Fri, 22 Jul 2011 14:37:16 -0000

Scott Schmit wrote:

> _http._tcp.example.com. SRV 0 99 80 www.example.com.
> _http._tcp.example.com. SRV 0 1 80 www-ds.example.com.
> www.example.com. A 198.0.2.1
> www-ds.example.com. A 198.0.2.2
> www-ds.example.com. AAAA 2001:db8::2
> 
> I.e., content providers could control/measure their probability of
> failure.

Are you saying content providers will actively control their probability
of failure from 99.99%> to 99% or 99.1% (assuming 10% IPv6 deployment)
only to promote IPv6?

							Masataka Ohta

From randy_presuhn@mindspring.com  Fri Jul 22 08:47:54 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 4EEC321F8AFB for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 08:47:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.74
X-Spam-Level: 
X-Spam-Status: No, score=-100.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lz+pQxhc029b for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 08:47:53 -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 CB51F21F8AE4 for <ietf@ietf.org>; Fri, 22 Jul 2011 08:47:53 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=WsLwKbSqWD+ig/C1nfIMUo+zvqOWroBfZ1LqsqL/euCLe8A7pjiRw5jOlzp5LcYi; 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.35.226.217] (helo=oemcomputer) by elasmtp-junco.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1QkHxB-0001sU-8N for ietf@ietf.org; Fri, 22 Jul 2011 11:47:53 -0400
Message-ID: <001101cc4887$7c390c00$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>
References: <20110718153337.C849F18C08C@mercury.lcs.mit.edu> <4E294E09.60507@gmail.com>
Subject: Re: Historic status (was Another look at 6to4 (and other IPv6 transitionissues))
Date: Fri, 22 Jul 2011 08:53:21 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8887f779e183b2ee2888bd855dff20288b42e66d7d3e36a63bb350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.35.226.217
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jul 2011 15:47:54 -0000

Hi -

> From: "Mykyta Yevstifeyev" <evnikita2@gmail.com>
> To: <ietf@ietf.org>
> Sent: Friday, July 22, 2011 3:16 AM
> Subject: Historic status (was Another look at 6to4 (and other IPv6 transitionissues))
...
> And what could/should be done?  I think, IESG and the whole community, 
> cooperating with IAB, IRSG and ISE, should determine the definition of 
> Historic which will be fine enough to cover all existing issues with it, 
> and then either publish such approach as BCP or incorporate when 
> updating RFC 2026.  This will eliminate the problems with different 
> issues with procedures for and understanding of Historic RFCs as well as 
> clear up one of "dark places" in IETF process.
...

After universal IPv6 deployment has been achieved, after we have
workable standardized configuration management, after all significant
protocols have been properly secured, and after NAT has been
banished from this planet, I *might* be persuaded to support
spending time on this.

Randy


From swallow@cisco.com  Fri Jul 22 10:44:10 2011
Return-Path: <swallow@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 5575B21F8B1C; Fri, 22 Jul 2011 10:44:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.61
X-Spam-Level: 
X-Spam-Status: No, score=-102.61 tagged_above=-999 required=5 tests=[AWL=-1.408, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yi+Fye3A2O6d; Fri, 22 Jul 2011 10:44:09 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 4BD3621F8B1B; Fri, 22 Jul 2011 10:44:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=swallow@cisco.com; l=1660; q=dns/txt; s=iport; t=1311356649; x=1312566249; h=date:subject:from:to:cc:message-id:mime-version; bh=55Twyg/8FXUAfGl+6Hv2f5ptMiSDUelUECdG/Bamy74=; b=hZqr9A/HyMhujVNPE3bg8YZYHIevMzCbEudRee2WSjJqGnERUMy4sR05 ffvQ8nitWOvM5ti8H6Cmdy4Xx5zctnBSI/PL3BeyEQ87lGe4YyOaaiBNY aNasu1cJS1vXrfA4wRnFOOLcGZWYT+mmwe4InW7oFN0Tww0f050f9fUgp M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApIbAAm2KU6tJXG8/2dsb2JhbABTG4I4lWiHBhyGeHJ3iQCcJJ4whj8Egk+EV4tIhRCLaw
X-IronPort-AV: E=Sophos;i="4.67,248,1309737600"; d="scan'208,217";a="5569662"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-2.cisco.com with ESMTP; 22 Jul 2011 17:44:08 +0000
Received: from xbh-rcd-302.cisco.com (xbh-rcd-302.cisco.com [72.163.63.9]) by rcdn-core2-1.cisco.com (8.14.3/8.14.3) with ESMTP id p6MHi8tn028413;  Fri, 22 Jul 2011 17:44:08 GMT
Received: from xmb-rcd-106.cisco.com ([72.163.62.148]) by xbh-rcd-302.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 22 Jul 2011 12:44:08 -0500
Received: from 10.86.250.202 ([10.86.250.202]) by XMB-RCD-106.cisco.com ([72.163.62.148]) with Microsoft Exchange Server HTTP-DAV ;  Fri, 22 Jul 2011 17:44:08 +0000
User-Agent: Microsoft-Entourage/12.29.0.110113
Date: Fri, 22 Jul 2011 13:44:07 -0400
Subject: Last call comments on draft-mpls-tp-identifiers-06.txt
From: George Swallow <swallow@cisco.com>
To: <ietf@ietf.org>
Message-ID: <CA4F2F27.126C3%swallow@cisco.com>
Thread-Topic: Last call comments on draft-mpls-tp-identifiers-06.txt
Thread-Index: AcxIlvRt+K9VKNK6SEijlPUe3r2GTw==
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3394187047_5167292"
X-OriginalArrivalTime: 22 Jul 2011 17:44:08.0048 (UTC) FILETIME=[F50D3700:01CC4896]
Cc: mpls@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jul 2011 17:44:10 -0000

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

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

I=B9ve addressed the last call comments received on the list as well as some
comments on =AD05.txt that were received after the WG LC completed.  The
response to specific comments are in a spreadsheet which can be found at
http://www.pi.nu/~loa/MPLS-TP-Identifiers_IETF_LC_Comments.xls

I=B9ve also addressed some of the discuss issues raised by IESG members.

The new =AD07 version has been posted.

...George

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

<HTML>
<HEAD>
<TITLE>Last call comments on draft-mpls-tp-identifiers-06.txt</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:10pt=
'>I&#8217;ve addressed the last call comments received on the list as well a=
s some comments on &#8211;05.txt that were received after the WG LC complete=
d. &nbsp;The response to specific comments are in a spreadsheet which can be=
 found at <BR>
<FONT COLOR=3D"#0000FF"><U><a href=3D"http://www.pi.nu/~loa/MPLS-TP-Identifiers=
_IETF_LC_Comments.xls">http://www.pi.nu/~loa/MPLS-TP-Identifiers_IETF_LC_Com=
ments.xls</a><BR>
</U></FONT><BR>
I&#8217;ve also addressed some of the discuss issues raised by IESG members=
.<BR>
<BR>
The new &#8211;07 version has been posted.<BR>
<BR>
...George</SPAN></FONT>
</BODY>
</HTML>


--B_3394187047_5167292--


From i.grok@comcast.net  Fri Jul 22 11:26:51 2011
Return-Path: <i.grok@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 B0EFA21F8B27 for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 11:26:51 -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 hJld3UkNpt6n for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 11:26:51 -0700 (PDT)
Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by ietfa.amsl.com (Postfix) with ESMTP id 1A9DB21F84BF for <ietf@ietf.org>; Fri, 22 Jul 2011 11:26:51 -0700 (PDT)
Received: from omta08.westchester.pa.mail.comcast.net ([76.96.62.12]) by qmta02.westchester.pa.mail.comcast.net with comcast id B5xn1h0030Fqzac526Srim; Fri, 22 Jul 2011 18:26:51 +0000
Received: from odin.ulthar.us ([68.33.77.0]) by omta08.westchester.pa.mail.comcast.net with comcast id B6Sa1h01N00PQ6U3U6Sjhz; Fri, 22 Jul 2011 18:26:50 +0000
Received: from odin.ulthar.us (localhost [127.0.0.1]) by odin.ulthar.us (8.14.4/8.14.3) with ESMTP id p6MIQVvA019725 for <ietf@ietf.org>; Fri, 22 Jul 2011 14:26:31 -0400
Received: (from draco@localhost) by odin.ulthar.us (8.14.4/8.14.4/Submit) id p6MIQVqx019724 for ietf@ietf.org; Fri, 22 Jul 2011 14:26:31 -0400
Date: Fri, 22 Jul 2011 14:26:31 -0400
From: Scott Schmit <i.grok@comcast.net>
To: ietf@ietf.org
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110722182631.GB6562@odin.ulthar.us>
Mail-Followup-To: ietf@ietf.org
References: <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <4E28C035.6020009@necom830.hpcl.titech.ac.jp> <9031.1311328268.180517@puncture> <4E295249.5060700@necom830.hpcl.titech.ac.jp> <20110722123114.GA6562@odin.ulthar.us> <4E298ADA.2060209@necom830.hpcl.titech.ac.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4E298ADA.2060209@necom830.hpcl.titech.ac.jp>
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, 22 Jul 2011 18:26:51 -0000

On Fri, Jul 22, 2011 at 11:36:10PM +0900, Masataka Ohta wrote:
> Scott Schmit wrote:
> 
> > _http._tcp.example.com. SRV 0 99 80 www.example.com.
> > _http._tcp.example.com. SRV 0 1 80 www-ds.example.com.
> > www.example.com. A 198.0.2.1
> > www-ds.example.com. A 198.0.2.2
> > www-ds.example.com. AAAA 2001:db8::2
> > 
> > I.e., content providers could control/measure their probability of
> > failure.
> 
> Are you saying content providers will actively control their probability
> of failure from 99.99%> to 99% or 99.1% (assuming 10% IPv6 deployment)
> only to promote IPv6?

I'm saying that they can be IPv6-ready without affecting their bottom
line (at least, as they perceive it). Whether they will or not--as you
point out--is another thing altogether, but at least it takes away an
often-used excuse.

Also, I've seen comments along the lines of "I want to phase in the IPv6
traffic" this allows that to happen.

-- 
Scott Schmit

From fielding@gbiv.com  Fri Jul 22 15:44:15 2011
Return-Path: <fielding@gbiv.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E657C21F8BA6; Fri, 22 Jul 2011 15:44:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.116
X-Spam-Level: 
X-Spam-Status: No, score=-106.116 tagged_above=-999 required=5 tests=[AWL=-3.817, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9BwOxq1mlsU5; Fri, 22 Jul 2011 15:44:15 -0700 (PDT)
Received: from homiemail-a66.g.dreamhost.com (caiajhbdccac.dreamhost.com [208.97.132.202]) by ietfa.amsl.com (Postfix) with ESMTP id 3E80821F8BB3; Fri, 22 Jul 2011 15:44:15 -0700 (PDT)
Received: from homiemail-a66.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a66.g.dreamhost.com (Postfix) with ESMTP id EF21C350078; Fri, 22 Jul 2011 15:44:14 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gbiv.com; h=subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to; q=dns; s=gbiv.com; b=fGWMx/MHZ1YlU5z5 gS5hiZhT+a+RRXacudhlZhoB38H2OYuGGZ4C1v7lXPUWJB6u+De0ZlACajLpUSBX Efh/qazf1o0fHGF9ii+FPRbG77MvVV/7vf5qLkQy5tNo8LPaweYZtnw1jIDDBGXs yZrtDj+fNNyuustcMP60Dzpk3kU=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gbiv.com; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=gbiv.com; bh=TffqHLS29zu3oNU2se+sFK5jPys=; b=hRavpF39+4n2Zm+Ita5EJSnHHdWa BQB8H1KQtTUMhNHZPUpMQvfr8a6Dm93ib2dpmDwEkXK/FSKugquCUhKOhJXwNn/f zgHtQNZWep252J0rnUgTYT4uyJxmeGZK6FvPwdodD3XC4arpjb7cBnKv37rEILuY 20pFIFII9CDOhP4=
Received: from [192.168.1.84] (99-21-208-82.lightspeed.irvnca.sbcglobal.net [99.21.208.82]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: fielding@gbiv.com) by homiemail-a66.g.dreamhost.com (Postfix) with ESMTPSA id AC83B35005B;  Fri, 22 Jul 2011 15:44:14 -0700 (PDT)
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: "Roy T. Fielding" <fielding@gbiv.com>
In-Reply-To: <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com>
Date: Fri, 22 Jul 2011 15:44:19 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com>
To: =?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
X-Mailer: Apple Mail (2.1084)
Cc: Server-Initiated HTTP <hybi@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, 22 Jul 2011 22:44:16 -0000

On Jul 21, 2011, at 10:52 AM, I=F1aki Baz Castillo wrote:

> 2011/7/21 Dave Cridland <dave@cridland.net>:
>> It's proven impossible, despite effort, to retrofit SRV onto HTTP; =
there is
>> no way it'll be possible to retrofit onto WS.
>=20
> Right. If WS borns with no SRV (as a MUST for WS clients) then just
> forget it and let inherit all the ugly limitations from HTTP protocol.

I am tired of this.  SRV is not used for HTTP because SRV adds latency
to the initial request for no useful purpose whatsoever.  SRV records =
for
XMPP and MX records for mail are useful because there is only one such
server expected per domain and it is *very* desirable to maintain =
central
control over that routing.  In contrast, HTTP is deployed in an anarchic
manner in which there are often several HTTP servers per machine
(e.g., tests, staging, production, CUPS, etc,).  AFAICT, WebSockets is
even more anarchic than HTTP -- it will have to be, given that the sane
network admins will block it by default.

In short, SRV is not used by the Web because it is inappropriate for =
HTTP.
I have seen no reason to believe that it would be appropriate for =
WebSockets.
If you want SRV to be part of the proposed standard, then you have to =
convince
the people implementing WS to use SRV.  None have done so, yet, so we =
can't
expect the editor to add it to the spec just because you have an =
opinion.

....Roy=

From dean.willis@softarmor.com  Fri Jul 22 17:18:26 2011
Return-Path: <dean.willis@softarmor.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3467921F8BBE for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 17:18:26 -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 KKrkcOx+eXny for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 17:18:25 -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 9E5F321F8BB8 for <ietf@ietf.org>; Fri, 22 Jul 2011 17:18:25 -0700 (PDT)
Received: by gxk19 with SMTP id 19so1783262gxk.31 for <ietf@ietf.org>; Fri, 22 Jul 2011 17:18:25 -0700 (PDT)
Received: by 10.236.78.232 with SMTP id g68mr3102461yhe.416.1311380305177; Fri, 22 Jul 2011 17:18:25 -0700 (PDT)
Received: from [192.168.2.143] (cpe-66-25-15-110.tx.res.rr.com [66.25.15.110]) by mx.google.com with ESMTPS id j65sm2614338yhm.40.2011.07.22.17.18.22 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 22 Jul 2011 17:18:24 -0700 (PDT)
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <4E28C035.6020009@necom830.hpcl.titech.ac.jp> <9031.1311328268.180517@puncture>
In-Reply-To: <9031.1311328268.180517@puncture>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
Message-Id: <34B72B6B-43EE-43B9-BC0A-2BE87DEAB044@softarmor.com>
Content-Transfer-Encoding: quoted-printable
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Date: Fri, 22 Jul 2011 19:18:21 -0500
To: Dave Cridland <dave@cridland.net>
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: Sat, 23 Jul 2011 00:18:26 -0000

On Jul 22, 2011, at 4:51 AM, Dave Cridland wrote:
>=20
>=20
> 1) There are no SRV records.
>=20
> 2) Therefore browsers do not support them.
>=20
> 3) Therefore you'd need to allow for A-lookup as fallback for the =
forseeable future.
>=20
> 4) Therefore there's no incentive for browsers to support SRV.


That's pretty much where we were when we grafted SRV onto SIP eleven and =
a half years ago, updating earlier SIP drafts (which lacked SRV =
support). There was no incentive for SRV support in SIP user agents at =
the time, either.=20

See:

http://tools.ietf.org/html/draft-ietf-sip-srv-00


The first SIP RFC 2543 used SRV, but didn't work very well. RFC 2782 =
cleaned up the SRV process somewhat, but we required further =
documentation for SIP to make use of it effectively.  It eventually =
worked itself out as RFC 3263, which also involved NAPTR records and a =
slew of other DNS kludges. But barring the limitations of DNS (some =
people still want requester-variant answers), it works pretty well now.

But yes, there's more to effective target resolution than just saying =
"Use SRV records". Especially if you have multiple protocol choices, =
proxies,  aliases, and TLS in the mix.

--
Dean Willis=

From evnikita2@gmail.com  Sat Jul 23 03:12: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 41D4921F86D0 for <ietf@ietfa.amsl.com>; Sat, 23 Jul 2011 03:12:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.068
X-Spam-Level: 
X-Spam-Status: No, score=-3.068 tagged_above=-999 required=5 tests=[AWL=-0.354, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, 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 Z6qPP2HWcGmN for <ietf@ietfa.amsl.com>; Sat, 23 Jul 2011 03:12:42 -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 9F5DB21F86BA for <ietf@ietf.org>; Sat, 23 Jul 2011 03:12:38 -0700 (PDT)
Received: by fxe4 with SMTP id 4so7434440fxe.27 for <ietf@ietf.org>; Sat, 23 Jul 2011 03:12:37 -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:subject:references :in-reply-to:content-type; bh=MPaVCjPGqB6Kidf83KeXPZ4qm9gx16RIGZOXw7hkApM=; b=ueA9srtRrH8B97+gjTxorxhWJw35JhlS5K+WXuy7a2RyKw4JeHB6CU6UgXvodwkJBs xJLQn+wKdKpY9ZAEz7fwxNF4cM6MRJM5tg6OBWFi5Vjf05yQG82XRlLPG50+zOOjPL7Q P97fk3Z2zPSdp9nhYmvoEem62Pbun9Pg8/N4U=
Received: by 10.223.97.131 with SMTP id l3mr3566676fan.43.1311415957769; Sat, 23 Jul 2011 03:12:37 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id n27sm2548546faa.4.2011.07.23.03.12.35 (version=SSLv3 cipher=OTHER); Sat, 23 Jul 2011 03:12:36 -0700 (PDT)
Message-ID: <4E2A9EBE.7090000@gmail.com>
Date: Sat, 23 Jul 2011 13:13:18 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Additional registries converted to XML and announcement of new registry for Service Names and Port Numbers
References: <CA4E3BF0.32F65%michelle.cotton@icann.org>
In-Reply-To: <CA4E3BF0.32F65%michelle.cotton@icann.org>
Content-Type: multipart/alternative; boundary="------------070802080101000208010704"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Jul 2011 10:12:43 -0000

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

Hello,

The new registry says:

>   System Ports are assigned by IETF
>   process for standards-track protocols, as per [RFC1340].  User Ports
>   are assigned by IANA using the "Expert Review" process, as per
>   [RFC5226].  Dynamic Ports are not assigned.

I don't understand referencing RFC 1340 here.  You could better change 
this to "System Ports are assigned per "Standards Action" or "IESG 
Approval" process, as per [RFC5226]".  IESG Approval is assumed by the 
RFC-to-be, Section 8.1:

>     o  Reserved numbers and names are generally only assigned by a
>        Standards Action or an IESG Approval,

Also, the new registry doesn't seem to match the following rule:

>     The new assignment procedure
>     conserves resources by assigning a port number to an application for
>     only those transport protocols (TCP, UDP, SCTP and/or DCCP) it
>     actually uses.  The port number will be marked as Reserved - instead
>     of Assigned - in the port number registries of the other transport
>     protocols.

Such entries as:

> tcpmux               1         tcp    TCP Port Service Multiplexer [Mark_Lottor]                       [Mark_Lottor]
> tcpmux               1         udp    TCP Port Service Multiplexer [Mark_Lottor]                       [Mark_Lottor]

should be:

> tcpmux               1         tcp    TCP Port Service Multiplexer [Mark_Lottor]                       [Mark_Lottor]
> tcpmux               1         udp    TCP Port Service Multiplexer [Mark_Lottor]                       [Mark_Lottor]
>                       1        sctp    Reserved
>                       1        dccp    Reserved

etc.

Mykyta Yevstifeyev

22.07.2011 6:26, Michelle Cotton wrote:
>
> Attention:  We recently combined and converted the Service Names and 
> Port Numbers registry in accordance with a recently approved document 
> to become an RFC.  The legacy registries will be maintained for 2 more 
> weeks so that anyone running scripts or gathering information can 
> adjust/update what they need to.
>
> Legacy URLs:
> http://www.iana.org/assignments/service-names/service-names.xml
> http://www.iana.org/assignments/port-numbers
>
> NEW URL:
> http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xml
>
> We are aware that the new registry is very slow to load in some 
> browsers and we are working on resolving the speed issue.
>
> If you have any questions, please do not hesitate to contact me.
>
> Thank you,
>
> Michelle Cotton


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hello,<br>
    <br>
    The new registry says:<br>
    <br>
    <blockquote type="cite">
      <pre> System Ports are assigned by IETF
 process for standards-track protocols, as per [RFC1340].  User Ports
 are assigned by IANA using the "Expert Review" process, as per
 [RFC5226].  Dynamic Ports are not assigned.</pre>
    </blockquote>
    <br>
    I don't understand referencing RFC 1340 here.&nbsp; You could better
    change this to "System Ports are assigned per "Standards Action" or
    "IESG Approval" process, as per [RFC5226]".&nbsp; IESG Approval is
    assumed by the RFC-to-be, Section 8.1:<br>
    <br>
    <blockquote type="cite">
      <pre class="newpage">   o  Reserved numbers and names are generally only assigned by a
      Standards Action or an IESG Approval,</pre>
    </blockquote>
    <br>
    Also, the new registry doesn't seem to match the following rule:<br>
    <br>
    <blockquote type="cite">
      <pre class="newpage">   The new assignment procedure
   conserves resources by assigning a port number to an application for
   only those transport protocols (TCP, UDP, SCTP and/or DCCP) it
   actually uses.  The port number will be marked as Reserved - instead
   of Assigned - in the port number registries of the other transport
   protocols.  </pre>
    </blockquote>
    <br>
    Such entries as:<br>
    <br>
    <blockquote type="cite">
      <pre>tcpmux               1         tcp    TCP Port Service Multiplexer [Mark_Lottor]                       [Mark_Lottor]
tcpmux               1         udp    TCP Port Service Multiplexer [Mark_Lottor]                       [Mark_Lottor]</pre>
    </blockquote>
    <br>
    should be:<br>
    <br>
    <blockquote type="cite">
      <pre>tcpmux               1         tcp    TCP Port Service Multiplexer [Mark_Lottor]                       [Mark_Lottor]
tcpmux               1         udp    TCP Port Service Multiplexer [Mark_Lottor]                       [Mark_Lottor]
                     1        sctp    Reserved
                     1        dccp    Reserved
</pre>
    </blockquote>
    <br>
    etc.<br>
    <br>
    Mykyta Yevstifeyev<br>
    <br>
    22.07.2011 6:26, Michelle Cotton wrote:
    <blockquote cite="mid:CA4E3BF0.32F65%25michelle.cotton@icann.org"
      type="cite">
      <title>Additional registries converted to XML and announcement of
        new registry for Service Names and Port Numbers</title>
      <font face="Calibri, Verdana, Helvetica, Arial"><span
          style="font-size:12pt"></span></font><span
        style="font-size:12pt"><font color="#131313"><font face="Lucida
            Grande"><br>
            Attention: &nbsp;We recently combined and converted the Service
            Names and Port Numbers registry in accordance with a
            recently approved document to become an RFC. &nbsp;The legacy
            registries will be maintained for 2 more weeks so that
            anyone running scripts or gathering information can
            adjust/update what they need to.<br>
            <br>
            Legacy URLs: <br>
            <a moz-do-not-send="true"
              href="http://www.iana.org/assignments/service-names/service-names.xml">http://www.iana.org/assignments/service-names/service-names.xml</a><br>
            <a moz-do-not-send="true"
              href="http://www.iana.org/assignments/port-numbers">http://www.iana.org/assignments/port-numbers</a><br>
            <br>
            NEW URL: <br>
            <a moz-do-not-send="true"
href="http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xml">http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xml</a><br>
            <br>
            We are aware that the new registry is very slow to load in
            some browsers and we are working on resolving the speed
            issue.<br>
            <br>
            If you have any questions, please do not hesitate to contact
            me.<br>
            <br>
            Thank you,<br>
            <br>
            Michelle Cotton</font></font></span><br>
    </blockquote>
    <br>
  </body>
</html>

--------------070802080101000208010704--

From daedulus@btconnect.com  Sat Jul 23 04:10:08 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 1696321F877B for <ietf@ietfa.amsl.com>; Sat, 23 Jul 2011 04:10:08 -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 2gPVspGMbkJC for <ietf@ietfa.amsl.com>; Sat, 23 Jul 2011 04:10:07 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr14.btconnect.com [213.123.20.132]) by ietfa.amsl.com (Postfix) with ESMTP id 3692521F876F for <ietf@ietf.org>; Sat, 23 Jul 2011 04:10:06 -0700 (PDT)
Received: from host86-174-254-236.range86-174.btcentralplus.com (HELO pc6) ([86.174.254.236]) by c2bthomr14.btconnect.com with SMTP id DSK16122; Sat, 23 Jul 2011 12:09:40 +0100 (BST)
Message-ID: <003401cc4920$38bb93a0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Randy Presuhn" <randy_presuhn@mindspring.com>, <ietf@ietf.org>
References: <20110718153337.C849F18C08C@mercury.lcs.mit.edu><4E294E09.60507@gmail.com> <001101cc4887$7c390c00$6801a8c0@oemcomputer>
Subject: Re: Historic status (was Another look at 6to4 (and other IPv6transitionissues))
Date: Sat, 23 Jul 2011 12:06:38 +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.4E2AABF3.0063, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.7.23.94816:17:7.586, ip=86.174.254.236, 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_1400_1499, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_2000_LESS, __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.0A0B020B.4E2AABF6.007C,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: Sat, 23 Jul 2011 11:10:08 -0000

----- Original Message -----
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>
Sent: Friday, July 22, 2011 5:53 PM

> Hi -
>
> > From: "Mykyta Yevstifeyev" <evnikita2@gmail.com>
> > To: <ietf@ietf.org>
> > Sent: Friday, July 22, 2011 3:16 AM
> > Subject: Historic status (was Another look at 6to4 (and other IPv6
transitionissues))
> ...
> > And what could/should be done?  I think, IESG and the whole community,
> > cooperating with IAB, IRSG and ISE, should determine the definition of
> > Historic which will be fine enough to cover all existing issues with it,
> > and then either publish such approach as BCP or incorporate when
> > updating RFC 2026.  This will eliminate the problems with different
> > issues with procedures for and understanding of Historic RFCs as well as
> > clear up one of "dark places" in IETF process.
> ...
> After universal IPv6 deployment has been achieved, after we have
> workable standardized configuration management, after all significant
> protocols have been properly secured, and after NAT has been
> banished from this planet, I *might* be persuaded to support
> spending time on this.

But Randy, you already have; you have spent time sending an e-mail; I was hoping
that this time there would be no response at all.

Tom Petch

>
> Randy
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From phbernard@gmail.com  Thu Jul 21 14:52:42 2011
Return-Path: <phbernard@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8536721F8ADC; Thu, 21 Jul 2011 14:52:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1QMACVSny1si; Thu, 21 Jul 2011 14:52:41 -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 9127D21F898E; Thu, 21 Jul 2011 14:52:35 -0700 (PDT)
Received: by pvh18 with SMTP id 18so2046036pvh.31 for <multiple recipients>; Thu, 21 Jul 2011 14:52:35 -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:content-transfer-encoding; bh=vyN7eX/XeuNubz6FtZKzzl2CbZWFykNGkZEEKDHGXNU=; b=JDwqhSKmcWvhlwQGa0quutAOUmNtr+sE0v3WxR+DmVXbZTdWbv+qr/D8oEA7MhiTst jmjF9xszQJxG45WSuNXayREIB6fadZak9bTiTd4PWRgs52xhYCTfzxkRORvaZRDu4mS+ uC3ZETyzYCGGOJq5poA0pzAjYeobcI+L2gSXk=
MIME-Version: 1.0
Received: by 10.68.41.3 with SMTP id b3mr1082144pbl.164.1311285155267; Thu, 21 Jul 2011 14:52:35 -0700 (PDT)
Received: by 10.68.49.129 with HTTP; Thu, 21 Jul 2011 14:52:35 -0700 (PDT)
In-Reply-To: <CAP992=Ec3KvAerosLNkJCTNzFniRfU-bFg_7=bAiMOJFarb5zA@mail.gmail.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <CALiegfnGkypkJYxUGGm3Tddgk3D0Ri=EWtN0WMChhEZN3Xsauw@mail.gmail.com> <CAP992=FrnDrCLgqZGUO9R2WkfgA2D+8TCau=6Xi+xa_u3CXT2w@mail.gmail.com> <9031.1311279546.247694@puncture> <CAP992=Ec3KvAerosLNkJCTNzFniRfU-bFg_7=bAiMOJFarb5zA@mail.gmail.com>
Date: Thu, 21 Jul 2011 22:52:35 +0100
Message-ID: <CACXjwhAW2dxN3v+MddCQp9vRGGrtqKz5HigYXWpHAm=yOF2QKA@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: Philippe Bernard <phbernard@gmail.com>
To: David Endicott <dendicott@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Sat, 23 Jul 2011 09:42:33 -0700
Cc: Server-Initiated HTTP <hybi@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, 21 Jul 2011 21:52:42 -0000

On Thu, Jul 21, 2011 at 9:57 PM, David Endicott <dendicott@gmail.com> wrote=
:
>> I have no idea what you might mean by "highly dynamic host environment" =
in
>> this context, but XMPP servers are normally found at the same location
>> consistently. However, it is *not* always (or typically) the same locati=
on
>> as a simple A record lookup:
>
> That's what I meant. =A0XMPP systems have hosts that change around (for m=
any
> reasons) and having a name resolution that handles that is good.
>
>>
>> This property alone is very useful - in a websockets case this would mea=
n
>> being able to provide websockets services from a different host (or netw=
ork)
>> to the traditional web services in a simple manner, fully compatible wit=
h
>> SOP. =A0=A0The fact that this also allows cheap lightweight load balanci=
ng and
>> fallback control is also useful in other cases; none of this relates to
>> dynamic hosts, but simply richer service location.
>
> Yes, those are all excellent reasons to use DNS SRV. =A0 None of them are=
 a
> reason to mandate that WS require it. =A0 Because something is good for s=
ome
> (or many) use cases, does not mean it is appropriate for everything and
> certainly is not a reason to mandate it as a requirement.
> =A0System=A0implementer=A0should be free to pick and choose tools and mec=
hanisms
> appropriate for their tasks. =A0 DNS SRV would likely be an excellent cho=
ice
> for many people. =A0 But it should not be the one and only choice. =A0 Th=
at's
> really all I'm saying - don't force people to use something without an
> overwhelming reason to make it the only option.
>
>>>
>>> I do not oppose DNS's MX records for SMTP as email addresses are
>>> name@domain,
>>> so obviously the Domain Name System is appropriate. =A0 =A0Also, I fail=
 to
>>> see
>>> why a mail admin should care how the SMTP clients arrive at the server.
>>> =A0DNS
>>> MX is a reasonable solution, but there may be other methods, any and al=
l
>>> of
>>> which are irrelevant to the SMTP server. =A0 =A0Especially when the SMT=
P
>>> server
>>> supports multiple email domains...
>>>
>> A mail admin does need to care *that* the service is located, and
>> therefore will care *how* it is located.
>>
>> You can be as theoretical as you like, by all means, but in practical
>> terms, your email address (and my XMPP address) work because they use a
>> defined, interoperable, service location mechanism, which operates via D=
NS
>> record lookup.
>>
>> (Also, I have no idea what multiple domains has to do with this.)
>
> Imagine I'm a SMTP server. =A0 People connect to me. =A0 They do SMTP
> transactions. =A0 =A0I do not care how they found me. =A0 Perhaps they us=
ed DNS to
> find the MX server. =A0Perhaps they had it cached from before. =A0Perhaps=
 they
> guessed. =A0Perhaps it's in a hosts file. =A0 I don't care. =A0 =A0 I ans=
wer VRFY
> and RCPT TO commands as appropriate. =A0 If the "name" they are trying to
> mailwith is one I recognize, I process it. =A0If I don't, it's an error.
> Just because DNS-MX said that @foobar was handled at <addr>, doesn't mean
> the dave@foobar is going to work.
> Yes, DNS MX is a well known mechanism for determining what SMTP server to
> connect with, but like I tried to say above, it's not mandated by the SMT=
P
> protocol. =A0 DNS MX is independent of SMTP and the two mechanisms
> operate=A0separately, but with a common goal. =A0I can use DNS to resolve=
 a name
> and never send email/message. =A0I can send a email/message via SMTP and =
never
> use DNS to resolve a name. =A0 =A0Or I can use one to do the other.
> When a SMTP server handles mail for multiple domains, the SMTP server has=
 to
> process the @domain part of the RCPT TO request - DNS is not involved at
> that point. =A0 This process is unrelated to any DNS MX definitions. =A0 =
=A0I used
> that as an example of how some name resolutions are sometimes done outsid=
e
> of any DNS framework.
>
>>>
>>> Since WS is intended as a browser supported protocol, WS should follow
>>> the
>>> same URI resolution mechanisms as HTTP (or how URI resolution is done i=
n
>>> general) =A0Having URLs that could resolve differently for a HTTP reque=
st
>>> and
>>> a WS setup is a problem.
>>>
>> But they do resolve differently anyway. You don't get a page from a 'ws'
>> scheme URI, you get a transport protocol connection. This is good, indee=
d,
>> it's kind of the point.
>
>
> Do they? =A0 A http uri and a ws uri have the same host/path construction=
.
> =A0It's really only the scheme that differs - and that identifies the
> transport protocol to be used. =A0 Resolution of host name/addresses and
> mapping of paths "should" be consistent.
> WS is a connection that is semantically related to the URI of the request=
.
>
> e.g. I could ws://host/davesaid =A0and get live traffic of what Dave is
> saying, and then I could ws://host/bobsaid =A0and get traffic of what Bob
> says. =A0I wouldn't get Bob on /davesaid and I wouldn't get Dave on /bobs=
aid.
> =A0 =A0Dynamic content identified by a URI
> And if I http://host/davesaid =A0I could get a <li> of what Dave said.
> Static content of a URI.
> It could be problematic if =A0ws://host/davesaid resolves to a different
> address than http://host/davesaid. =A0 =A0 (Or it could be advantage - no=
t for
> us to decide, however)
>>
>> Your suggestion of "how URI resolution is done in general" is somewhat
>> self-defeating, too, since aside from 'http' and 'https', there are
>> 'mailto', which uses MX, 'sip' and 'xmpp', which both use SRV.
>
> As you just said, the universe is bigger than just xmpp, sip, and http.
>>
>> I think opponents of SRV records need to mount a stronger argument than
>> the kind of luddite argument that if it's hard for one protocol in use b=
y
>> the browser, it should be hard for them all.
>
> I think you misinterpret my position. =A0And=A0I resent the luddite sligh=
t. =A0=A0I
> think DNS SRV is an awesome tool and would greatly benefit many
> implementations.
> My position is that it should not be a *requirement*. =A0 =A0 It should b=
e an
> optional mechanism that can be used if desired. =A0 Further, since WS is =
a
> bastard cousin to HTTP, they should share a similar name resolution
> mechanism.

I=F1aki's proposal only imposes a requirement on clients, not on
server-side WS deployments, since clients will fall back to A/AAAA if
no SRV records are available. The mechanism (on the client-side)
cannot be optional though, it would make SRV for WS mostly useless in
practice.

-Philippe.

>
>>
>> Dave.
>> --
>> Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
>> =A0- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
>> =A0- http://dave.cridland.net/
>> Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
>
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>
>

From bruce@callenish.com  Thu Jul 21 15:15:51 2011
Return-Path: <bruce@callenish.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 767DA21F8567; Thu, 21 Jul 2011 15:15:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wB5GhHwlFO4N; Thu, 21 Jul 2011 15:15:50 -0700 (PDT)
Received: from biz82.inmotionhosting.com (biz82.inmotionhosting.com [173.247.251.126]) by ietfa.amsl.com (Postfix) with ESMTP id AD02421F8538; Thu, 21 Jul 2011 15:15:50 -0700 (PDT)
Received: from [24.108.144.160] (helo=[192.168.145.13]) by biz82.inmotionhosting.com with esmtpa (Exim 4.69) (envelope-from <bruce@callenish.com>) id 1Qk1X1-0002J7-Nn; Thu, 21 Jul 2011 15:15:47 -0700
Message-ID: <4E28A51F.4020704@callenish.com>
Date: Thu, 21 Jul 2011 15:15:59 -0700
From: Bruce Atherton <bruce@callenish.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: David Endicott <dendicott@gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com>
In-Reply-To: <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------080201030706020602030101"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz82.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - callenish.com
X-Mailman-Approved-At: Sat, 23 Jul 2011 09:42:33 -0700
Cc: =?ISO-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>, Server-Initiated HTTP <hybi@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, 21 Jul 2011 22:15:51 -0000

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

I think there is some misunderstanding as to what is being proposed, at 
least as I understand it. Iñaki, please correct me if I am wrong.

You are right that it would be impossible to require all environments 
that wanted to add Websockets support, whether client or server, to 
change their DNS to have NAPTR and SRV records. After all, Websockets is 
intended to integrate easily into the already existing HTTP infrastructure.

What is being proposed, though, is to require clients to resolve the 
hostname portion of ws: and wss: URLs by _first_ looking for NAPTR and 
SRV records (unless, of course, the hostname is already an IP address). 
If a NAPTR record is found, use it to look up an SRV record (otherwise 
use a default). If an SRV record is found, use it to look up the A or 
AAAA record. If no SRV record is found, look up the record exactly the 
same as if you were looking up an HTTP host, by using the host name from 
the URL.

So if you have no control over the DNS, it is not a problem. The host 
will be resolved exactly the same way as it is now, using a hosts file 
or A record or whatever. The only change is that the client is required 
to try to use the more advanced mechanism if it is available.

I admit that I find it a little troubling to use MUST for the client to 
follow this procedure as there is a burden on implementers to understand 
how to code this since it isn't done by default in the standard 
libraries the way that ordinary name resolution is. Making it the 
recognized best practice with a SHOULD would be preferable all else 
being equal.

It can be argued that not using a MUST may well open up interoperability 
problems because some Websockets clients contact the wrong host. 
However, keep in mind that in the older SIP RFC2543 it provided two 
resolution mechanisms. It specified that clients SHOULD look up address 
records, but MAY use the DNS SRV mechanism. SIP survived that without 
too much of a hassle. And specifying that Websockets clients SHOULD use 
DNS SRV, but MAY use address records alone looks like an improvement.

As for where the enhanced location definition should live, I think a 
separate document is the best choice. No need to hold up this one.

On 21/07/2011 11:01 AM, David Endicott wrote:
> I am strongly opposed to any MUST definition for any type of URL 
> resolution.
>
> I'm ok with inheriting / mimicking HTTP.    Since it is intended to 
> live in the same universe as HTTP, I'm ok with it sharing mechanisms / 
> limitations.
>
>
>
> On Thu, Jul 21, 2011 at 1:52 PM, Iñaki Baz Castillo <ibc@aliax.net 
> <mailto:ibc@aliax.net>> wrote:
>
>     2011/7/21 Dave Cridland <dave@cridland.net
>     <mailto:dave@cridland.net>>:
>     > It's proven impossible, despite effort, to retrofit SRV onto
>     HTTP; there is
>     > no way it'll be possible to retrofit onto WS.
>
>     Right. If WS borns with no SRV (as a MUST for WS clients) then just
>     forget it and let inherit all the ugly limitations from HTTP protocol.
>
>     --
>     Iñaki Baz Castillo
>     <ibc@aliax.net <mailto:ibc@aliax.net>>
>
>
>
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    I think there is some misunderstanding as to what is being proposed,
    at least as I understand it. I&ntilde;aki, please correct me if I am wrong.<br>
    <br>
    You are right that it would be impossible to require all
    environments that wanted to add Websockets support, whether client
    or server, to change their DNS to have NAPTR and SRV records. After
    all, Websockets is intended to integrate easily into the already
    existing HTTP infrastructure.<br>
    <br>
    What is being proposed, though, is to require clients to resolve the
    hostname portion of ws: and wss: URLs by _first_ looking for NAPTR
    and SRV records (unless, of course, the hostname is already an IP
    address). If a NAPTR record is found, use it to look up an SRV
    record (otherwise use a default). If an SRV record is found, use it
    to look up the A or AAAA record. If no SRV record is found, look up
    the record exactly the same as if you were looking up an HTTP host,
    by using the host name from the URL.<br>
    <br>
    So if you have no control over the DNS, it is not a problem. The
    host will be resolved exactly the same way as it is now, using a
    hosts file or A record or whatever. The only change is that the
    client is required to try to use the more advanced mechanism if it
    is available.<br>
    <br>
    I admit that I find it a little troubling to use MUST for the client
    to follow this procedure as there is a burden on implementers to
    understand how to code this since it isn't done by default in the
    standard libraries the way that ordinary name resolution is. Making
    it the recognized best practice with a SHOULD would be preferable
    all else being equal.<br>
    <br>
    It can be argued that not using a MUST may well open up
    interoperability problems because some Websockets clients contact
    the wrong host. However, keep in mind that in the older SIP RFC2543
    it provided two resolution mechanisms. It specified that clients
    SHOULD look up address records, but MAY use the DNS SRV mechanism.
    SIP survived that without too much of a hassle. And specifying that
    Websockets clients SHOULD use DNS SRV, but MAY use address records
    alone looks like an improvement.<br>
    <br>
    As for where the enhanced location definition should live, I think a
    separate document is the best choice. No need to hold up this one.<br>
    <br>
    On 21/07/2011 11:01 AM, David Endicott wrote:
    <blockquote
cite="mid:CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com"
      type="cite">I am strongly opposed to any MUST definition for any
      type of URL resolution. &nbsp;&nbsp;
      <div><br>
      </div>
      <div>I'm ok with inheriting /&nbsp;mimicking&nbsp;HTTP. &nbsp; &nbsp;Since it is
        intended to live in the same universe as HTTP, I'm ok with it
        sharing mechanisms / limitations.</div>
      <div><br>
      </div>
      <div><br>
      </div>
      <div><br>
        <div class="gmail_quote">On Thu, Jul 21, 2011 at 1:52 PM, I&ntilde;aki
          Baz Castillo <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:ibc@aliax.net">ibc@aliax.net</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex;">
            2011/7/21 Dave Cridland &lt;<a moz-do-not-send="true"
              href="mailto:dave@cridland.net">dave@cridland.net</a>&gt;:<br>
            <div class="im">&gt; It's proven impossible, despite effort,
              to retrofit SRV onto HTTP; there is<br>
              &gt; no way it'll be possible to retrofit onto WS.<br>
              <br>
            </div>
            Right. If WS borns with no SRV (as a MUST for WS clients)
            then just<br>
            forget it and let inherit all the ugly limitations from HTTP
            protocol.<br>
            <div>
              <div class="h5"><br>
                --<br>
                I&ntilde;aki Baz Castillo<br>
                &lt;<a moz-do-not-send="true"
                  href="mailto:ibc@aliax.net">ibc@aliax.net</a>&gt;<br>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
hybi mailing list
<a class="moz-txt-link-abbreviated" href="mailto:hybi@ietf.org">hybi@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/hybi">https://www.ietf.org/mailman/listinfo/hybi</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------080201030706020602030101--

From w@1wt.eu  Thu Jul 21 15:30:01 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3315211E8079; Thu, 21 Jul 2011 15:30:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.508
X-Spam-Level: 
X-Spam-Status: No, score=-5.508 tagged_above=-999 required=5 tests=[AWL=-3.465, BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id egTLucTnM75B; Thu, 21 Jul 2011 15:30:00 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 19D8D11E8075; Thu, 21 Jul 2011 15:29:59 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6LMTqcZ018232; Fri, 22 Jul 2011 00:29:52 +0200
Date: Fri, 22 Jul 2011 00:29:52 +0200
From: Willy Tarreau <w@1wt.eu>
To: Dave Cridland <dave@cridland.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110721222952.GA18126@1wt.eu>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CALiegfkk8G6_KE-KfL_RuF96NUbF6yZgcFfsNGtLoAr2=jcYjg@mail.gmail.com> <20110721173338.GB16854@1wt.eu> <9031.1311285127.963748@puncture>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9031.1311285127.963748@puncture>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Sat, 23 Jul 2011 09:42:33 -0700
Cc: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>, David Endicott <dendicott@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2011 22:30:01 -0000

Hi Dave,

On Thu, Jul 21, 2011 at 10:52:07PM +0100, Dave Cridland wrote:
> On Thu Jul 21 18:33:38 2011, Willy Tarreau wrote:
> >If someone were to develop a backup/restore solution based on WS,  
> >it would
> >be funny to discover that it cannot be used to restore the DNS  
> >server when
> >this one fails...
> >
> >
> If SRV (with a fallback) is defined as part of the core spec, this  
> usage would use the fallback.

Which would be indicated by which component since the DNS is down ?

> >However in my opinion it could be good to document a recommended DNS
> >architecture for WS, that is judged optimal and the most  
> >interoperable.
> >This could clearly be a separate RFC suggesting how clients and  
> >server
> >can make use of DNS SRV records for HA and LB.
> 
> Okay, a thought experiment for you.
> 
> Let's assume we go ahead with dumb A/AAAA lookups.
> 
> How will it be possible for a server to later inform browser it  
> wishes to use SRV lookups?

The same way it has been stated that browsers should use AAAA records
before A records when they exist. At one point it will be possible to
say "if an SRV record exists, then the browser should preferably use
it".

My point is not that DNS is not useful, just that in *some* cases, it
is all but desirable. Have you ever wondered why every cisco router
on the planet has "no ip-domain-lookups" in its config ? Basically
because core infrastructure component must be able to run with very
low dependencies, and DNS certainly is one dependency that is not
desirable for a number of core infrastructure components. And there
is no reason why those components could not be WS clients.

> If you have an answer for this, we can make it optional, and moreover  
> we can deploy SRV for HTTP as well.

It's not that easy either for HTTP. As I said in an earlier mail, HTTP
(as well as WS) has something special called proxies, which exempt
clients from having to deal with DNS. The simple fact that the server
does not know if the client will be able to use the DNS or rely on a
chain of intermediaries that may use it in various ways is a problem
for making use of DNS extensions mandatory.

You couldn't make DNS SRV mandatory for WS when WS starts with a protocol
upgrade from HTTP which does not mandate use of DNS SRV : the DNS resolving
had to be performed by the HTTP chain well before the connection gets
upgraded to WS. If any existing HTTP component in the chain does not make
use of DNS SRV, everything falls apart.

Experience has shown that a spec is not a way to force the world to change
to accomodate its requirements, rather it's a way to tell the world how to
adopt it at a reasonable cost and effort. The higher the expectations, the
lower the adoption. The most important thing is that the spec is designed
to support smooth upgrades so that real world usage drives it forwards.

Best regards,
Willy


From ibc@aliax.net  Thu Jul 21 16:19:43 2011
Return-Path: <ibc@aliax.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF30A21F869E; Thu, 21 Jul 2011 16:19:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.67
X-Spam-Level: 
X-Spam-Status: No, score=-2.67 tagged_above=-999 required=5 tests=[AWL=0.008,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 GtwtQLsgDXk8; Thu, 21 Jul 2011 16:19:42 -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 990BD21F8680; Thu, 21 Jul 2011 16:19:42 -0700 (PDT)
Received: by qyk9 with SMTP id 9so4596219qyk.10 for <multiple recipients>; Thu, 21 Jul 2011 16:19:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.66.25 with SMTP id l25mr725161qci.265.1311290381925; Thu, 21 Jul 2011 16:19:41 -0700 (PDT)
Received: by 10.229.185.195 with HTTP; Thu, 21 Jul 2011 16:19:41 -0700 (PDT)
In-Reply-To: <CAP992=Ec3KvAerosLNkJCTNzFniRfU-bFg_7=bAiMOJFarb5zA@mail.gmail.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <CALiegfnGkypkJYxUGGm3Tddgk3D0Ri=EWtN0WMChhEZN3Xsauw@mail.gmail.com> <CAP992=FrnDrCLgqZGUO9R2WkfgA2D+8TCau=6Xi+xa_u3CXT2w@mail.gmail.com> <9031.1311279546.247694@puncture> <CAP992=Ec3KvAerosLNkJCTNzFniRfU-bFg_7=bAiMOJFarb5zA@mail.gmail.com>
Date: Fri, 22 Jul 2011 01:19:41 +0200
Message-ID: <CALiegfmo2-wGBO+e5E_sdh9wc_G6kpmmmTo1UZCEyLAZ2XFaOw@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: David Endicott <dendicott@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Sat, 23 Jul 2011 09:42:33 -0700
Cc: Server-Initiated HTTP <hybi@ietf.org>, Willy Tarreau <w@1wt.eu>, 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, 21 Jul 2011 23:19:43 -0000

2011/7/21 David Endicott <dendicott@gmail.com>:
> Yes, those are all excellent reasons to use DNS SRV. =C2=A0 None of them =
are a
> reason to mandate that WS require it. =C2=A0 Because something is good fo=
r some
> (or many) use cases, does not mean it is appropriate for everything and
> certainly is not a reason to mandate it as a requirement.

Hi David, I will be away for some days until I can read all the new
mails in this thread (I'll do it and will reply in a few days).
In the meanwhile I strongly ask you to read the draft about DNS SRV in
WebSocket:

  http://tools.ietf.org/html/draft-ibc-websocket-dns-srv-02

Sepecially some sections:


   1. Introducion

   [...]

   DNS SRV mechanism facilitates network applications scalability
   without requiring an intermediary node distributing the traffic in
   load-balancing or failover fashion.  Instead, DNS SRV mechanism just
   requires a proper DNS setup.

   By introducing DNS SRV records into WebSocket protocol
   [I-D.ietf-hybi-thewebsocketprotocol], WebSocket providers can,
   optionally, take same advantages and provide scalable services with a
   minimal infrastructure.

   This specification mandates the usage of DNS SRV resource records by
   WebSocket clients when resolving a "ws:" or "wss:" URI [RFC3986], but
   still leaves the decision of using SRV records up to the service
   administrator.


  3. Implementation

  [...]

   It is up to the system administrator whether to set, or not, DNS SRV
   resource records for the WebSocket protocol within the provided
   service.  This specification allows the system administrator to use
   the DNS SRV [RFC2782] mechanism to improve the service reliability by
   providing load-balancing and failover capabilities, but does not
   mandate it (the system administrator could choose whichever
   scalability strategy).



Section 4 "Client Usage" in which is shown how the WS client should
perform SRV resolution just in case the WS URI is a domain and no port
is present in the URI:

   To clarify it, a WebSocket URI like "ws://example.org/myservice"
   requires the client to perform SRV resolution while
   "ws://example.org:80/myservice" does not (as the port is explicitly
   present in the URI).


   step 3:  If there is no SRV result, attempt the fallback process describ=
ed
       in Section 4.2 and omit next steps.



   4.2.  Fallback Process

   The fallback process SHOULD be a normal A or AAAA address record
   resolution to determine the IPv4 or IPv6 address of the URI host
   component (or URI host value without DNS resolution if it contains an
   IP address).

   The server connection port is obtained as stated in Section 3.1 of
   [I-D.ietf-hybi-thewebsocketprotocol].

NOTE: The section 3.1 has changed in the new WS draft. It pointed to
http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-06#section-=
3.1
(3.1.  Parsing WebSocket URIs)


Also, the section 5 (Examples) should clarify it even more.


Regards.



--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From ibc@aliax.net  Thu Jul 21 16:22:17 2011
Return-Path: <ibc@aliax.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 422B021F86B6; Thu, 21 Jul 2011 16:22:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.67
X-Spam-Level: 
X-Spam-Status: No, score=-2.67 tagged_above=-999 required=5 tests=[AWL=0.007,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 PG1IJL4HqNDr; Thu, 21 Jul 2011 16:22:16 -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 8F3A921F86AF; Thu, 21 Jul 2011 16:22:16 -0700 (PDT)
Received: by qyk9 with SMTP id 9so4597111qyk.10 for <multiple recipients>; Thu, 21 Jul 2011 16:22:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.77.38 with SMTP id e38mr748859qck.151.1311290535964; Thu, 21 Jul 2011 16:22:15 -0700 (PDT)
Received: by 10.229.185.195 with HTTP; Thu, 21 Jul 2011 16:22:15 -0700 (PDT)
In-Reply-To: <4E28A51F.4020704@callenish.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com>
Date: Fri, 22 Jul 2011 01:22:15 +0200
Message-ID: <CALiegf=4K2oWfmZjGMD7J_jyaDtS3i+Mu7R0Wh75Rr+MrQCjtw@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Bruce Atherton <bruce@callenish.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Sat, 23 Jul 2011 09:42:33 -0700
Cc: Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>, David Endicott <dendicott@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2011 23:22:17 -0000

2011/7/22 Bruce Atherton <bruce@callenish.com>:
> You are right that it would be impossible to require all environments tha=
t
> wanted to add Websockets support, whether client or server, to change the=
ir
> DNS to have NAPTR and SRV records. After all, Websockets is intended to
> integrate easily into the already existing HTTP infrastructure.
>
> What is being proposed, though, is to require clients to resolve the
> hostname portion of ws: and wss: URLs by _first_ looking for NAPTR and SR=
V
> records (unless, of course, the hostname is already an IP address). If a
> NAPTR record is found, use it to look up an SRV record (otherwise use a
> default). If an SRV record is found, use it to look up the A or AAAA reco=
rd.
> If no SRV record is found, look up the record exactly the same as if you
> were looking up an HTTP host, by using the host name from the URL.

Well, in SIP there are NAPTR records because SIP can work over
different transports (UDP, TCP, TLS-TCP. SCTP, TLS-SCTP). In case of
WebSocket, it just defined for TCP so NAPTR records don't make sense.

So just SRV is required:

a)  _ws._tcp.DOMAIN.COM    for WS URI
b)  _wss._tcp.DOMAIN.COM   for WSS URI


Regards.

--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From ibc@aliax.net  Thu Jul 21 16:27:21 2011
Return-Path: <ibc@aliax.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA83811E8078; Thu, 21 Jul 2011 16:27:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.67
X-Spam-Level: 
X-Spam-Status: No, score=-2.67 tagged_above=-999 required=5 tests=[AWL=0.007,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 nDVc6EqeA+9o; Thu, 21 Jul 2011 16:27:21 -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 31A4111E8071; Thu, 21 Jul 2011 16:27:21 -0700 (PDT)
Received: by qwc23 with SMTP id 23so1430653qwc.31 for <multiple recipients>; Thu, 21 Jul 2011 16:27:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.77.38 with SMTP id e38mr751382qck.151.1311290840508; Thu, 21 Jul 2011 16:27:20 -0700 (PDT)
Received: by 10.229.185.195 with HTTP; Thu, 21 Jul 2011 16:27:20 -0700 (PDT)
In-Reply-To: <CAP992=Ec3KvAerosLNkJCTNzFniRfU-bFg_7=bAiMOJFarb5zA@mail.gmail.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <CALiegfnGkypkJYxUGGm3Tddgk3D0Ri=EWtN0WMChhEZN3Xsauw@mail.gmail.com> <CAP992=FrnDrCLgqZGUO9R2WkfgA2D+8TCau=6Xi+xa_u3CXT2w@mail.gmail.com> <9031.1311279546.247694@puncture> <CAP992=Ec3KvAerosLNkJCTNzFniRfU-bFg_7=bAiMOJFarb5zA@mail.gmail.com>
Date: Fri, 22 Jul 2011 01:27:20 +0200
Message-ID: <CALiegfktEh3fjd_uHH_uVdo498xUoqxaYvXrzFQkFQbeafw1GQ@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: David Endicott <dendicott@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Sat, 23 Jul 2011 09:42:33 -0700
Cc: Server-Initiated HTTP <hybi@ietf.org>, Willy Tarreau <w@1wt.eu>, 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, 21 Jul 2011 23:27:22 -0000

2011/7/21 David Endicott <dendicott@gmail.com>:
> Do they? =C2=A0 A http uri and a ws uri have the same host/path construct=
ion.
> =C2=A0It's really only the scheme that differs - and that identifies the
> transport protocol to be used. =C2=A0 Resolution of host name/addresses a=
nd
> mapping of paths "should" be consistent.
> WS is a connection that is semantically related to the URI of the request=
.
>
> e.g. I could ws://host/davesaid =C2=A0and get live traffic of what Dave i=
s
> saying, and then I could ws://host/bobsaid =C2=A0and get traffic of what =
Bob
> says. =C2=A0I wouldn't get Bob on /davesaid and I wouldn't get Dave on /b=
obsaid.
> =C2=A0 =C2=A0Dynamic content identified by a URI
> And if I http://host/davesaid =C2=A0I could get a <li> of what Dave said.
> Static content of a URI.
> It could be problematic if =C2=A0ws://host/davesaid resolves to a differe=
nt
> address than http://host/davesaid. =C2=A0 =C2=A0 (Or it could be advantag=
e - not for
> us to decide, however)

David, this does not make sense at all. Let see this case:

a) mailto:alice@google.com
b) xmpp:alice@google.com
c) sip:alice@google,com
d) http://google.com
e) ws://google.com

Do you really expect that all those URI's should point to the same
server??? not, right? then, why e) should behave like d)?

And of course, protocols defining a kind of URI (specific for such
protocol) CAN and probably MUST also define how to locate such URI
destination. In case of http just poor A/AAAA is done, but in other
cases we all do know that other kind of DNS queries are done.

--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From ibc@aliax.net  Thu Jul 21 16:31:34 2011
Return-Path: <ibc@aliax.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3508A21F8574; Thu, 21 Jul 2011 16:31:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.67
X-Spam-Level: 
X-Spam-Status: No, score=-2.67 tagged_above=-999 required=5 tests=[AWL=0.007,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 v9zufBx7Kz+U; Thu, 21 Jul 2011 16:31:33 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id 847E821F856D; Thu, 21 Jul 2011 16:31:33 -0700 (PDT)
Received: by qyk29 with SMTP id 29so1269246qyk.10 for <multiple recipients>; Thu, 21 Jul 2011 16:31:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.66.222 with SMTP id o30mr737740qci.189.1311291092916; Thu, 21 Jul 2011 16:31:32 -0700 (PDT)
Received: by 10.229.185.195 with HTTP; Thu, 21 Jul 2011 16:31:32 -0700 (PDT)
In-Reply-To: <20110721222952.GA18126@1wt.eu>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CALiegfkk8G6_KE-KfL_RuF96NUbF6yZgcFfsNGtLoAr2=jcYjg@mail.gmail.com> <20110721173338.GB16854@1wt.eu> <9031.1311285127.963748@puncture> <20110721222952.GA18126@1wt.eu>
Date: Fri, 22 Jul 2011 01:31:32 +0200
Message-ID: <CALiegfnck+=iV8ttvmdXgsKM938ZhQWkxN_kLkzMCH6vzTMcUw@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Willy Tarreau <w@1wt.eu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Sat, 23 Jul 2011 09:42:33 -0700
Cc: Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>, David Endicott <dendicott@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2011 23:31:34 -0000

2011/7/22 Willy Tarreau <w@1wt.eu>:
> You couldn't make DNS SRV mandatory for WS when WS starts with a protocol
> upgrade from HTTP which does not mandate use of DNS SRV : the DNS resolvi=
ng
> had to be performed by the HTTP chain well before the connection gets
> upgraded to WS. If any existing HTTP component in the chain does not make
> use of DNS SRV, everything falls apart.

I understand that the websocket client is *co-located* within the
webbrowser client, but it's a different entity. Nothing prevents it in
using a different DNS mechanism.

Honestly I'm not reading good arguments against DNS SRV for WebSocket
protocol. Perhaps the topic about the HTTP proxies, but there should
be some way to deal with it without forcing WebSocket to inherit all
the limitations and poor capabilities of HTTP (when referring to
scalability and failover).

--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From bruce@callenish.com  Thu Jul 21 16:47:30 2011
Return-Path: <bruce@callenish.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38CE811E8079; Thu, 21 Jul 2011 16:47:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001,  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 KjddOSxWibxp; Thu, 21 Jul 2011 16:47:29 -0700 (PDT)
Received: from biz82.inmotionhosting.com (biz82.inmotionhosting.com [173.247.251.126]) by ietfa.amsl.com (Postfix) with ESMTP id B08FF11E8075; Thu, 21 Jul 2011 16:47:29 -0700 (PDT)
Received: from [24.108.144.160] (helo=[192.168.145.13]) by biz82.inmotionhosting.com with esmtpa (Exim 4.69) (envelope-from <bruce@callenish.com>) id 1Qk2xk-0000G8-IB; Thu, 21 Jul 2011 16:47:28 -0700
Message-ID: <4E28BA9D.6010501@callenish.com>
Date: Thu, 21 Jul 2011 16:47:41 -0700
From: Bruce Atherton <bruce@callenish.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <9031.1311286867.939466@puncture>
In-Reply-To: <9031.1311286867.939466@puncture>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz82.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - callenish.com
X-Mailman-Approved-At: Sat, 23 Jul 2011 09:42:33 -0700
Cc: Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>, David Endicott <dendicott@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2011 23:47:30 -0000

On 21/07/2011 3:21 PM, Dave Cridland wrote:
>
> SRV lookup is pretty commonplace now in libraries. XMPP and SIP 
> clients have no difficulty finding this functionality in a wide 
> variety of environments. For the web, where there are substantially 
> fewer web browsers than there are XMPP clients, I don't think this 
> would pose any kind of problem.

Oh, it isn't hard, but it violates the principle of least surprise. Most 
people think they know how to code name resolution by using 
gethostbyname() or equivalent. And to do it efficiently, especially when 
we are operating in a world that is predominantly driven by HTTP 
servers, requires complexities like dealing with asynchronous calls to 
fetch the A and SRV records at the same time under the assumption that 
the SRV record probably won't exist.

>
>> It can be argued that not using a MUST may well open up 
>> interoperability problems because some Websockets clients contact the 
>> wrong host. However, keep in mind that in the older SIP RFC2543 it 
>> provided two resolution mechanisms. It specified that clients SHOULD 
>> look up address records, but MAY use the DNS SRV mechanism. SIP 
>> survived that without too much of a hassle. And specifying that 
>> Websockets clients SHOULD use DNS SRV, but MAY use address records 
>> alone looks like an improvement.
>>
>>
> SIP survived because it was very small. I don't see WS making a 
> transition, in the same way that repeated attempts have failed to move 
> HTTP to SRV.
>
> Dave.

As I understand it, the issue that caused the various drafts for HTTP 
SRV to die without getting much traction is one of efficiency. It is 
inefficient to make all these extra DNS calls, especially when it is 
unlikely that many of the records you are blocking on will exist. Other 
than the inefficiency, HTTP SRV is just an incremental technology you 
add to your existing DNS without hurting what already exists. Since 
Websockets uses the same infrastructure the records are unlikely to 
exist for it either, so the inefficiency issues are still present.

Hmm, I seem to be arguing myself out of supporting DNS SRV as the 
preferred location mechanism. That is not the case. I just think that we 
face some of the same challenges migrating Websockets to SRV as are 
faced by HTTP because we share the same environment for the most part. 
Willy's example of a proxy that doesn't know how to resolve host names 
using the SRV method is a good example. But by advocating for the 
deployment of SRV records as a best practice for Websockets, we may 
improve things in the HTTP world as well. It is a shame there is no 
standard defined for HTTP SRV to point to.


From Gabriel.Montenegro@microsoft.com  Thu Jul 21 17:14:28 2011
Return-Path: <Gabriel.Montenegro@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 51CCC21F8782; Thu, 21 Jul 2011 17:14:28 -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 lOM8gJiaAt7g; Thu, 21 Jul 2011 17:14:27 -0700 (PDT)
Received: from smtp.microsoft.com (mail3.microsoft.com [131.107.115.214]) by ietfa.amsl.com (Postfix) with ESMTP id 8B52921F877D; Thu, 21 Jul 2011 17:14:27 -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, 21 Jul 2011 17:14:26 -0700
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) with Microsoft SMTP Server (TLS) id 14.1.323.2; Thu, 21 Jul 2011 17:14:26 -0700
Received: from TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com ([169.254.5.188]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi id 14.01.0289.008; Thu, 21 Jul 2011 17:14:26 -0700
From: Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
To: Bruce Atherton <bruce@callenish.com>, Dave Cridland <dave@cridland.net>
Subject: RE: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Thread-Topic: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Thread-Index: AQHMR8o7lHZOnlMp5E682blrKHSyH5T3gDEAgAADn4CAAAJFgIAARziAgAABb4CAABgwgP//kMyw
Date: Fri, 22 Jul 2011 00:14:25 +0000
Message-ID: <CA566BAEAD6B3F4E8B5C5C4F61710C11403914B3@TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <9031.1311286867.939466@puncture> <4E28BA9D.6010501@callenish.com>
In-Reply-To: <4E28BA9D.6010501@callenish.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.90]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Sat, 23 Jul 2011 09:42:33 -0700
Cc: Server-Initiated HTTP <hybi@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, 22 Jul 2011 00:14:28 -0000

[As an individual]

I think the lack of DNS SRV for HTTP could also be because of the guidance =
in http://wiki.tools.ietf.org/html/draft-iab-dns-applications-02#section-4 =
that argues that DNS might not be the best approach for *all* HTTP applicat=
ions. Perhaps also for WS applications...

It could be a good alternative to have, so I agree with pursuing it as a se=
parate option in a different document.
=09
> -----Original Message-----
> From: hybi-bounces@ietf.org [mailto:hybi-bounces@ietf.org] On Behalf Of
> Bruce Atherton
> Sent: Thursday, July 21, 2011 16:48
> To: Dave Cridland
> Cc: Server-Initiated HTTP; IETF-Discussion
> Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.t=
xt> (The
> WebSocket protocol) to Proposed Standard
>=20
> On 21/07/2011 3:21 PM, Dave Cridland wrote:
> >
> > SRV lookup is pretty commonplace now in libraries. XMPP and SIP
> > clients have no difficulty finding this functionality in a wide
> > variety of environments. For the web, where there are substantially
> > fewer web browsers than there are XMPP clients, I don't think this
> > would pose any kind of problem.
>=20
> Oh, it isn't hard, but it violates the principle of least surprise. Most =
people think
> they know how to code name resolution by using
> gethostbyname() or equivalent. And to do it efficiently, especially when =
we are
> operating in a world that is predominantly driven by HTTP servers, requir=
es
> complexities like dealing with asynchronous calls to fetch the A and SRV =
records
> at the same time under the assumption that the SRV record probably won't =
exist.
>=20
> >
> >> It can be argued that not using a MUST may well open up
> >> interoperability problems because some Websockets clients contact the
> >> wrong host. However, keep in mind that in the older SIP RFC2543 it
> >> provided two resolution mechanisms. It specified that clients SHOULD
> >> look up address records, but MAY use the DNS SRV mechanism. SIP
> >> survived that without too much of a hassle. And specifying that
> >> Websockets clients SHOULD use DNS SRV, but MAY use address records
> >> alone looks like an improvement.
> >>
> >>
> > SIP survived because it was very small. I don't see WS making a
> > transition, in the same way that repeated attempts have failed to move
> > HTTP to SRV.
> >
> > Dave.
>=20
> As I understand it, the issue that caused the various drafts for HTTP SRV=
 to die
> without getting much traction is one of efficiency. It is inefficient to =
make all
> these extra DNS calls, especially when it is unlikely that many of the re=
cords you
> are blocking on will exist. Other than the inefficiency, HTTP SRV is just=
 an
> incremental technology you add to your existing DNS without hurting what
> already exists. Since Websockets uses the same infrastructure the records=
 are
> unlikely to exist for it either, so the inefficiency issues are still pre=
sent.
>=20
> Hmm, I seem to be arguing myself out of supporting DNS SRV as the preferr=
ed
> location mechanism. That is not the case. I just think that we face some =
of the
> same challenges migrating Websockets to SRV as are faced by HTTP because =
we
> share the same environment for the most part.
> Willy's example of a proxy that doesn't know how to resolve host names us=
ing
> the SRV method is a good example. But by advocating for the deployment of
> SRV records as a best practice for Websockets, we may improve things in t=
he
> HTTP world as well. It is a shame there is no standard defined for HTTP S=
RV to
> point to.
>=20
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi


From david.black@emc.com  Thu Jul 21 18:37:09 2011
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3265F21F8581; Thu, 21 Jul 2011 18:37:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.916
X-Spam-Level: 
X-Spam-Status: No, score=-106.916 tagged_above=-999 required=5 tests=[AWL=1.683, BAYES_00=-2.599, GB_I_INVITATION=-2, 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 sXtDPlpFqptV; Thu, 21 Jul 2011 18:37:07 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 6BD0021F86A6; Thu, 21 Jul 2011 18:37:06 -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 p6M1b2QI008164 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Jul 2011 21:37:02 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Thu, 21 Jul 2011 21:36:52 -0400
Received: from mxhub24.corp.emc.com (mxhub24.corp.emc.com [128.221.56.110]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p6M1aoti019022; Thu, 21 Jul 2011 21:36:50 -0400
Received: from mx14a.corp.emc.com ([169.254.1.245]) by mxhub24.corp.emc.com ([128.221.56.110]) with mapi; Thu, 21 Jul 2011 21:36:49 -0400
From: <david.black@emc.com>
To: <asaeda@wide.ad.jp>, <Jinmei_Tatuya@isc.org>, <fenner@fenron.net>, <casner@packetdesign.com>, <gen-art@ietf.org>, <ietf@ietf.org>
Date: Thu, 21 Jul 2011 21:36:32 -0400
Subject: Gen-ART review ofdraft-ietf-mboned-mtrace-v2-08
Thread-Topic: Gen-ART review ofdraft-ietf-mboned-mtrace-v2-08
Thread-Index: AcxID8lgoSOZbIfpQxa7VWnBDQx+TA==
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E058948BB36@MX14A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-cr-puzzleid: {F469AA8A-9402-4E2B-A3C4-7DA70ED8B500}
x-cr-hashedpuzzle: A/w6 OlFm Qkj5 RivN SHCC WqC8 WyxN kGPH rbjK 8LLq ABJYdQ== ACPfjA== AC1i/g== AFPcLg== AFP4ZQ== AG0/kA==; 10; YQBzAGEAZQBkAGEAQAB3AGkAZABlAC4AYQBkAC4AagBwADsAYwBhAHMAbgBlAHIAQABwAGEAYwBrAGUAdABkAGUAcwBpAGcAbgAuAGMAbwBtADsAZgBlAG4AbgBlAHIAQABmAGUAbgByAG8AbgAuAG4AZQB0ADsAZwBlAG4ALQBhAHIAdABAAGkAZQB0AGYALgBvAHIAZwA7AGcAagBzAGgAZQBwAEAAZwBtAGEAaQBsAC4AYwBvAG0AOwBpAGUAdABmAEAAaQBlAHQAZgAuAG8AcgBnADsAagBpAG4AbQBlAGkAXwB0AGEAdAB1AHkAYQBAAGkAcwBjAC4AbwByAGcAOwBsAGUAbgBuAHkAQABqAHUAbgBpAHAAZQByAC4AbgBlAHQAOwBtAGIAbwBuAGUAZABAAGkAZQB0AGYALgBvAHIAZwA7AHIAYgBvAG4AaQBjAGEAQABqAHUAbgBpAHAAZQByAC4AbgBlAHQA; Sosha1_v1; 7; {F469AA8A-9402-4E2B-A3C4-7DA70ED8B500}; ZABhAHYAaQBkAC4AYgBsAGEAYwBrAEAAZQBtAGMALgBjAG8AbQA=; Fri, 22 Jul 2011 01:36:32 GMT; RwBlAG4ALQBBAFIAVAAgAHIAZQB2AGkAZQB3ACAAbwBmAGQAcgBhAGYAdAAtAGkAZQB0AGYALQBtAGIAbwBuAGUAZAAtAG0AdAByAGEAYwBlAC0AdgAyAC0AMAA4AA==
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: Sat, 23 Jul 2011 09:42:33 -0700
Cc: mboned@ietf.org, david.black@emc.com, lenny@juniper.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jul 2011 01:37:09 -0000

I am the assigned Gen-ART reviewer for this draft. For background on=20
Gen-ART, please see the FAQ at=20
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments=20
you may receive.

Document: draft-ietf-mboned-mtrace-v2-08
Reviewer: David L. Black
Review Date: 21 July 2011
IETF LC End Date: 19 July 2011

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

This draft describes version 2 of multicast traceroute.

Major Issues:

This review is late because it took me much longer than expected to work th=
rough this
draft in order to figure out how the protocol works. While I believe that t=
he protocol
does work if correctly implemented, I don't believe that the protocol is ef=
fectively
implementable from this draft, and hence significant work is required.

The open issues fall into two primary areas:

- Message Structure: Sections 4 and 5 are confusing.
- Message Processing: The most important functionality of this protocol is =
the router
	processing of messages in Section 9.  I found numerous problems there, inc=
luding
	significant missing pieces of the specification (e.g., the material on whe=
n and
	how to generate Reply messages is incomplete).

In addition there are some missing security considerations around traffic a=
mplification.

-- Message Structure --

The text in sections 4 and 5 is confusing.  The problem starts with=20
the following sentence in section 4.2:

   An mtrace2 message MUST contain exactly one Mtrace2 Query header.

Because the mtrace2 Query header is not discussed until section 5, this
sentence is easy to misread as a requirement for exactly one Mtrace2
Query TLV. =20

It gets worse, because it turns out that the Mtrace2 Query header is actual=
ly
the value[V] for the Query, Request and Reply TLVs.  Hence, calling that a =
Query
header is an invitation to confusion (e.g., where are the Request and Reply
headers?).

I suggest renaming the Mtrace2 Query header to Mtrace2 Trace header and the=
n
changing the above sentence to:

   An mtrace2 message MUST begin with a Query, Request or Reply TLV. The va=
lue
   for each of these TLVs is an Mtrace2 Trace Header (see section 5).  Thes=
e
   three TLVs MUST NOT be used in any position other than the beginning of
   a message.

That is not easy to figure out from the current text.

5.  Mtrace2 Query Header

What's the maximum size of the UDP packet?  This is important because there=
's
text in Section 9 on that depends on whether another TLV fits into the mess=
age
or not. There needs to be a minimum size, as nothing will work if there isn=
't
room for at least one standard response block after the header.

How does one figure out whether the addresses in the Mtrace2 Query Header
are IPv4 or IPv6?

I suspect that at least one of the multicast address and source address nee=
ds
to be valid (i.e., not all 1's for IPv4, not :: for IPv6).  That should be =
stated,
along with what happens when both addresses are invalid.

State that the client address must be valid (not all 1's for IPv4, not :: f=
or IPv6).

Add the 24 bits of TLV to the packet structure diagrams in sections 5, 6, 7=
 and 8.

Sections 6 and 7 - The IPv4 and IPv6 response blocks use the same TLV code =
(4),
but have different contents and lengths.  How does the receiver determine w=
hich
response block is present for TLV code 4?=20

Section 8 Mtrace2 Augmented Response Block

   The augmented response block is always appended to mtrace2 TLV header
   (0x04).

No, definitely not.  Section 4.2 says that the mtrace2 TLV code for an augm=
ented
response block is 5, not 4.  The following would be better:

  The augmented response block uses TLV code 5 and always comes after a sta=
ndard
  response block TLV (code 4).

-- Message Processing --

Section 9 is confusing and incomplete.  This is the most important function=
ality
in the document, and it needs to be clear to the reader.  I'm having a very=
 hard
time figuring out exactly what the router is supposed to do, and I found a =
number
of things that are clearly wrong.  It is not sufficient to just fix the thi=
ngs=20
noted in this review - Section 9 needs to be clear and cogent about exactly=
 what
the router does for each received message so that code can be written from =
it.

Section 9.1.1 Packet Verification

   If the router determines that it is not the proper last-hop router,
   or it cannot make that determination, it does one of two things
   depending if the Query was received via multicast or unicast.  If the
   Query was received via multicast, then it MUST be silently dropped.
   If it was received via unicast, a forwarding code of WRONG_LAST_HOP
   is noted and processing continues as in Section 9.2.

The last sentence has a number of problems:
- It needs to say that the TLV type in the first TLV is changed from 1 to 2=
,
- Section 9.2 requires that there be a response block, but the Query
	message doesn't have one.
- Section 9.2 will forward the Request towards the multicast source,
	even though the Query was not received by a proper last-hop router.
	That seems wrong.
It would be clearer to describe how to return the WRONG_LAST_HOP error to
the client here instead of referencing Section 9.2.

   Duplicate Query messages as identified by the tuple (Mtrace2 Client
   Address, Query ID) SHOULD be ignored.  This MAY be implemented using
   a simple 1-back cache (i.e. remembering the Mtrace2 Client Address
   and Query ID of the previous Query message that was processed, and
   ignoring future messages with the same Mtrace2 Client Address and
   Query ID).  Duplicate Request messages MUST NOT be ignored in this
   manner.

Is a 1-entry cache really sufficient?  What if 2 clients are trying to quer=
y
concurrently causing their duplicate messages to be interleaved?

9.1.2.  Normal Processing

   When a router receives an mtrace2 Query and it determines that it is
   the proper last-hop router, it changes the TLV type to 0x2 and
   treats it like an mtrace2 Request and performs the steps listed in
   Section 9.2.

That's problematic - Section 9.2 requires that there be a response block,
but there won't be one.  Unlike the error case above, this mismatch can
probably be addressed in Section 9.2.

9.2.2.  Normal Processing

Step 1 in this section is where the Request message needs to have a respons=
e
block.  The problems with the second reference from section 9.1 to section =
9.2
might be correctable by explaining why the "If there was no room" condition
can't occur at the router that converts a Query to a Request.  This case ne=
eds
to be noted in the initial text in Section 9.2.

Also in step 1, how does the router determine whether there is "room in the
current buffer"?

9.2.3.  Mtrace2 Request Received by Non-Supported Router

Describe how the client matches the ICMP message with its original Query.

9.3.1.  Destination Address

   If the Previous-hop router for the mtrace2 Request is known for this
   request and the number of response blocks is less than the number
   requested (i.e., the "# hops" field in the mtrace2 Query header), the
   packet is sent to that router.  If the Incoming Interface is known
   but the Previous-hop router is not known, the packet is sent to an
   appropriate multicast address on the Incoming Interface.  The
   appropriate multicast address may depend on the routing protocol in
   use, MUST be a link-scoped group (i.e. 224/24 for IPv4, FF02::/16 for
   IPv6), MUST NOT be ALL-SYSTEMS.MCAST.NET (224.0.0.1) for IPv4 and All
   Nodes Address (FF02::1) for IPv6, and MAY be ALL-ROUTERS.MCAST.NET
   (224.0.0.2) for IPv4 or All Routers Address (FF02::2) for IPv6 if the
   routing protocol in use does not define a more appropriate group.
   Otherwise, it is sent to the Mtrace2 Client Address in the header.

There are multiple problems with that paragraph:

1) First line: "response blocks" is wrong.  The treatment of the augmented
response block's count of already returned response blocks is missing.

2) There are no instructions on what to do when the number of response
blocks is equal to the number of hops - the Request has to be converted to
a Reply.

3) The last line sends a Request to a Client.  If that's what was intended,
the Request first needs to be converted to a Reply.

9.3.2.  Source Address

   When the NO_SPACE error occurs, the router sends back the mtrace2
   Reply with contained data and the NO_SPACE error code as in
   Section 9.4, and continues the mtrace2 Query by sending an mtrace2
   Request containing the same mtrace2 Query header and its standard and
   augmented response blocks.  The corresponding augmented response
   block type is "# Mtrace2 Response Blocks Returned" described in
   Section 8.

There are a couple of problems with that paragraph:

1) What does "its" mean? If it refers to the header, that would
send all of the response blocks.  I think only this router's
response block is sent.

2) How does the hop count arithmetic work?  I suspect that the value for nu=
mber
of response blocks returned is counted against hop count, but that's not
mentioned in section 9.3.1 .

14.  Security Considerations

There are additional security considerations.  I can see at least two ways
in which this protocol appears to offer opportunities for traffic amplifica=
tion:

1) Suppose the client's address in the Query is a multicast address; the Re=
ply
	will get multicast by the router to a multicast address that the client
	can't reach.  Use of a multicast address as a client address should probab=
ly
	be prohibited.

2) The proxying and NO_SPACE behaviors result in one Query returning multip=
le=20
	Reply messages.  That's necessary for the protocol to work, but needs some
	control to prevent abuse.  Some sort of rate-limiting recommendations shou=
ld
	suffice to prevent this from becoming a problem.

Minor Issues:

Section 1 Introduction

The last 3 paragraphs on p.6 are not clear about how hop count works. The s=
tatement
in the last paragraph on p.6 that a lower hop count can be used is not cons=
istent
with the summary descriptions in the previous two paragraphs that don't dis=
cuss
hop count. That needs to be clearer. One possible approach would be:

- Add a sentence to the third to last paragraph (about generation of
	Request from Query) to say that the hop count in the Query is copied
	to the Request.
- Add a new paragraph following that paragraph to say that when a router
	that is not a first-hop router receives a Request message, the router
	adds a standard response block  If there are fewer standard response
	blocks that the hop count, the Request is forwarded.  If the number
	of response blocks matches the hop count or an error condition
	such as "no route" is encountered, a Reply is generated.

There is significant overlap between sections 1 and 3 - consider whether th=
ey should
be merged.  Of the two sections, the contents of Section 3 would be a bette=
r
Introduction than the current section 1.

Nits:

Add a definition of First-hop router to Section 2.

idnits 2.12.12 found a bunch of problems

  Checking nits according to http://www.ietf.org/id-info/checklist :
  -------------------------------------------------------------------------=
---

  =3D=3D There are 7 instances of lines with non-RFC2606-compliant FQDNs in=
 the
     document.

  =3D=3D There are 1 instance of lines with multicast IPv4 addresses in the
     document.  If these are generic example addresses, they should be chan=
ged
     to use the 233.252.0.x range defined in RFC 5771

The above 2 errors can be ignored - they FQDNs are MCAST.NET addresses that
this draft needs to use, and the multicast IPv4 address is the IPv4 address
for one of those FQDNs.

  Miscellaneous warnings:
  -------------------------------------------------------------------------=
---

  =3D=3D The document seems to lack the recommended RFC 2119 boilerplate, e=
ven if
     it appears to use RFC 2119 keywords -- however, there's a paragraph wi=
th
     a matching beginning. Boilerplate error?

     (The document does seem to have the reference to RFC 2119 which the
     ID-Checklist requires).
  -- The document date (January 7, 2011) is 195 days in the past.  Is this
     intentional?


  Checking references for intended status: Proposed Standard
  -------------------------------------------------------------------------=
---

     (See RFCs 3967 and 4897 for information about using normative referenc=
es
     to lower-maturity documents in RFCs)

  =3D=3D Unused Reference: '2' is defined on line 1413, but no explicit ref=
erence
     was found in the text

  =3D=3D Unused Reference: '5' is defined on line 1422, but no explicit ref=
erence
     was found in the text

  ** Obsolete normative reference: RFC 2373 (ref. '3') (Obsoleted by RFC 35=
13)

  ** Obsolete normative reference: RFC 2434 (ref. '4') (Obsoleted by RFC 52=
26)

  ** Downref: Normative reference to an Unknown state RFC: RFC 1071 (ref. '=
5')

  =3D=3D Outdated reference: A later version (-11) exists of
     draft-ietf-mboned-auto-multicast-08


From dendicott@gmail.com  Thu Jul 21 19:24:44 2011
Return-Path: <dendicott@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B71B811E8084; Thu, 21 Jul 2011 19:24:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.57
X-Spam-Level: 
X-Spam-Status: No, score=-3.57 tagged_above=-999 required=5 tests=[AWL=0.028,  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 TSqy8oGZc4RT; Thu, 21 Jul 2011 19:24:44 -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 69C5411E8086; Thu, 21 Jul 2011 19:24:43 -0700 (PDT)
Received: by wyj26 with SMTP id 26so1390178wyj.31 for <multiple recipients>; Thu, 21 Jul 2011 19:24:42 -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=YosTWudxZhl41afZ8BuiYgAhdogQL1JLIWiYK2WLJU8=; b=vIiUVG+zPlASIvu7VIU3fuN852SHN55IG/3CuoWreNuVnJxJd+oSBvj8r6bCgiciRR Fc8eufT9GI0fjZmQA+/AIzzp72WZNNlBaRmney5Z3Erym+1uQj78ABhzmcS5WXPg+jDS KkAhLI6hlq5jKH1m5BU3GEX7uad3jGz9p1Zq4=
MIME-Version: 1.0
Received: by 10.216.79.18 with SMTP id h18mr861927wee.3.1311301482527; Thu, 21 Jul 2011 19:24:42 -0700 (PDT)
Received: by 10.216.39.197 with HTTP; Thu, 21 Jul 2011 19:24:41 -0700 (PDT)
In-Reply-To: <4E28BA9D.6010501@callenish.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <9031.1311286867.939466@puncture> <4E28BA9D.6010501@callenish.com>
Date: Thu, 21 Jul 2011 22:24:41 -0400
Message-ID: <CAP992=GedTEfimykCWwdwm=BsZdwFRJO36EO0a_o7iejURJ+tQ@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: David Endicott <dendicott@gmail.com>
To: Bruce Atherton <bruce@callenish.com>
Content-Type: multipart/alternative; boundary=000e0ce0b4f00f3d8404a89f2b39
X-Mailman-Approved-At: Sat, 23 Jul 2011 09:42:33 -0700
Cc: Server-Initiated HTTP <hybi@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, 22 Jul 2011 02:24:44 -0000

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

On Thu, Jul 21, 2011 at 7:47 PM, Bruce Atherton <bruce@callenish.com> wrote:

>
> As I understand it, the issue that caused the various drafts for HTTP SRV
> to die without getting much traction is one of efficiency. It is inefficient
> to make all these extra DNS calls, especially when it is unlikely that many
> of the records you are blocking on will exist. Other than the inefficiency,
> HTTP SRV is just an incremental technology you add to your existing DNS
> without hurting what already exists. Since Websockets uses the same
> infrastructure the records are unlikely to exist for it either, so the
> inefficiency issues are still present.
>
> Hmm, I seem to be arguing myself out of supporting DNS SRV as the preferred
> location mechanism. That is not the case. I just think that we face some of
> the same challenges migrating Websockets to SRV as are faced by HTTP because
> we share the same environment for the most part. Willy's example of a proxy
> that doesn't know how to resolve host names using the SRV method is a good
> example. But by advocating for the deployment of SRV records as a best
> practice for Websockets, we may improve things in the HTTP world as well. It
> is a shame there is no standard defined for HTTP SRV to point to.
>

I find myself reminded of my reservations about HTTP Upgrade as the opening
handshake.  It is clever, efficient and reflects some of the shared nature
between HTTP and WS.   However, I felt it should be considered one of
several mechanisms for opening a WS connection, one especially suited for
a co-mingled environment.   But not explicitly the only such method.  (I was
unable to convince many of my position on that, so I could very well be in
the minority about this issue as well)    I think DNS SRV is in a similar
area.   It's a useful technology that if the client uses could be of
benefit.   I'm just not convinced there is overwhelming cause to make it a
mandatory requirement.    Saying that nobody will use it if it's not
legislated does not strike me as a good enough reason.   The technological
advantages are worthy, when it's used, but when it doesn't come into play,
there are added inefficiencies.   Also the name resolution of the HTTP that
serves the Javascript that opens the WS should remain constant.   If WS
resolves the host/domain to a different address than the HTTP it was spawned
from, it becomes a method to bypass same-origin / CORS restrictions.

I favor a minimalist core with extensibility.    Name resolution happens
before the WS opening handshake, so I continue to see this as outside the
domain of the WS protocol.   I would prefer that name resolution be provided
by a selectable method.  That way, in 20 years, when name resolution needs
have again changed, we'll have the ability to adapt.

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

<br><br><div class=3D"gmail_quote">On Thu, Jul 21, 2011 at 7:47 PM, Bruce A=
therton <span dir=3D"ltr">&lt;<a href=3D"mailto:bruce@callenish.com">bruce@=
callenish.com</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"><br></div>
As I understand it, the issue that caused the various drafts for HTTP SRV t=
o die without getting much traction is one of efficiency. It is inefficient=
 to make all these extra DNS calls, especially when it is unlikely that man=
y of the records you are blocking on will exist. Other than the inefficienc=
y, HTTP SRV is just an incremental technology you add to your existing DNS =
without hurting what already exists. Since Websockets uses the same infrast=
ructure the records are unlikely to exist for it either, so the inefficienc=
y issues are still present.<br>

<br>
Hmm, I seem to be arguing myself out of supporting DNS SRV as the preferred=
 location mechanism. That is not the case. I just think that we face some o=
f the same challenges migrating Websockets to SRV as are faced by HTTP beca=
use we share the same environment for the most part. Willy&#39;s example of=
 a proxy that doesn&#39;t know how to resolve host names using the SRV meth=
od is a good example. But by advocating for the deployment of SRV records a=
s a best practice for Websockets, we may improve things in the HTTP world a=
s well. It is a shame there is no standard defined for HTTP SRV to point to=
.<br>
</blockquote><div><br></div><div>I find myself reminded of my reservations =
about HTTP Upgrade as the opening handshake. =A0It is clever, efficient and=
 reflects some of the shared nature between HTTP and WS. =A0 However, I fel=
t it should be considered one of several mechanisms for opening a WS connec=
tion, one especially suited for a=A0co-mingled=A0environment. =A0 But=A0not=
 explicitly the only such method. =A0(I was unable to convince many of my p=
osition on that, so I could very well be in the minority about this issue a=
s well) =A0 =A0I think DNS SRV is in a similar area. =A0 It&#39;s a useful =
technology that if the client uses could be of benefit. =A0 I&#39;m just no=
t convinced there is overwhelming cause to make it a mandatory requirement.=
 =A0 =A0Saying that nobody will use it if it&#39;s not legislated does not =
strike me as a good enough reason. =A0 The technological advantages are wor=
thy, when it&#39;s used, but when it doesn&#39;t come into play, there are =
added inefficiencies. =A0=A0Also the name resolution of the HTTP that serve=
s the Javascript that opens the WS should remain constant. =A0 If WS resolv=
es the host/domain to a different address than the HTTP it was spawned from=
, it becomes a method to bypass same-origin / CORS restrictions. =A0 =A0</d=
iv>
<div><br></div><meta http-equiv=3D"content-type" content=3D"text/html; char=
set=3Dutf-8"><div>I favor a minimalist core with extensibility. =A0 =A0Name=
 resolution happens before the WS opening handshake, so I continue to see t=
his as outside the domain of the WS protocol. =A0 I would prefer that name =
resolution be provided by a selectable method. =A0That way, in 20 years, wh=
en name resolution needs have again changed, we&#39;ll have the ability to =
adapt.</div>
<div><br></div></div>

--000e0ce0b4f00f3d8404a89f2b39--

From jat@google.com  Thu Jul 21 19:45:41 2011
Return-Path: <jat@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 282E511E8075 for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 19:45:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.952
X-Spam-Level: 
X-Spam-Status: No, score=-105.952 tagged_above=-999 required=5 tests=[AWL=0.025, 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 DR6nnmQ4KawR for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 19:45:41 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by ietfa.amsl.com (Postfix) with ESMTP id F11CE11E8080 for <ietf@ietf.org>; Thu, 21 Jul 2011 19:45:40 -0700 (PDT)
Received: from hpaq11.eem.corp.google.com (hpaq11.eem.corp.google.com [172.25.149.11]) by smtp-out.google.com with ESMTP id p6M2jdn7020471 for <ietf@ietf.org>; Thu, 21 Jul 2011 19:45:39 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1311302739; bh=ltAjm2zKw9+y8/AdWc7/vIg9Wxc=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type:Content-Transfer-Encoding; b=uBbEWaW+/WFW4BMnRryau6GmASH/GXOxy/rJ/BSqdFDjL8dVdmDmp7V77kwEQYuij MJB7GQ6/gmDo/jdaxtolA==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type: content-transfer-encoding:x-system-of-record; b=W/QBWN61PGZfe1WAQb7ypnVBVX/S2x+fT2x6cM3J0n+r1P0sd/TT/T/lN1Ud1Zann 0gIf/BzexwUEN0pPhbGGw==
Received: from ywf7 (ywf7.prod.google.com [10.192.6.7]) by hpaq11.eem.corp.google.com with ESMTP id p6M2jQtf025535 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Thu, 21 Jul 2011 19:45:37 -0700
Received: by ywf7 with SMTP id 7so1148905ywf.13 for <ietf@ietf.org>; Thu, 21 Jul 2011 19:45:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=a8PlHfCYyrvGzfaLNG3vTG7r+cS6UBlYIEuVZyvPzDQ=; b=EHlZD57a8yaF8MDsaXdUYdjUuY/Qn0MtfH97MZOYUyX4Fe5i6BgqazlLBzCBK1sWhe pSbKdD1/JoROOX31mS5A==
Received: by 10.151.88.21 with SMTP id q21mr1390171ybl.173.1311302737502; Thu, 21 Jul 2011 19:45:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.49.7 with HTTP; Thu, 21 Jul 2011 19:45:17 -0700 (PDT)
In-Reply-To: <CAP992=GedTEfimykCWwdwm=BsZdwFRJO36EO0a_o7iejURJ+tQ@mail.gmail.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <9031.1311286867.939466@puncture> <4E28BA9D.6010501@callenish.com> <CAP992=GedTEfimykCWwdwm=BsZdwFRJO36EO0a_o7iejURJ+tQ@mail.gmail.com>
From: John Tamplin <jat@google.com>
Date: Thu, 21 Jul 2011 22:45:17 -0400
Message-ID: <CABLsOLA_QiFMVSBL6dhHLkAjfApEe2i_xg7JafA3pxt1oCHt7w@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
To: David Endicott <dendicott@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
X-Mailman-Approved-At: Sat, 23 Jul 2011 09:42:33 -0700
Cc: Server-Initiated HTTP <hybi@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, 22 Jul 2011 02:45:41 -0000

On Thu, Jul 21, 2011 at 10:24 PM, David Endicott <dendicott@gmail.com> wrot=
e:
> I find myself reminded of my reservations about HTTP Upgrade as the openi=
ng
> handshake. =C2=A0It is clever, efficient and reflects some of the shared =
nature
> between HTTP and WS. =C2=A0 However, I felt it should be considered one o=
f
> several mechanisms for opening a WS connection, one especially suited for
> a=C2=A0co-mingled=C2=A0environment. =C2=A0 But=C2=A0not explicitly the on=
ly such method. =C2=A0(I was
> unable to convince many of my position on that, so I could very well be i=
n
> the minority about this issue as well) =C2=A0 =C2=A0I think DNS SRV is in=
 a similar
> area. =C2=A0 It's a useful technology that if the client uses could be of
> benefit. =C2=A0 I'm just not convinced there is overwhelming cause to mak=
e it a
> mandatory requirement. =C2=A0 =C2=A0Saying that nobody will use it if it'=
s not
> legislated does not strike me as a good enough reason. =C2=A0 The technol=
ogical
> advantages are worthy, when it's used, but when it doesn't come into play=
,
> there are added inefficiencies. =C2=A0=C2=A0Also the name resolution of t=
he HTTP that
> serves the Javascript that opens the WS should remain constant. =C2=A0 If=
 WS
> resolves the host/domain to a different address than the HTTP it was spaw=
ned
> from, it becomes a method to bypass same-origin / CORS restrictions.
> I favor a minimalist core with extensibility. =C2=A0 =C2=A0Name resolutio=
n happens
> before the WS opening handshake, so I continue to see this as outside the
> domain of the WS protocol. =C2=A0 I would prefer that name resolution be =
provided
> by a selectable method. =C2=A0That way, in 20 years, when name resolution=
 needs
> have again changed, we'll have the ability to adapt.

How about some language like "SHOULD use SRV records to locate the
host unless specifically configured for an alternate name resolution
method"?  I think that leaves open the possibility for clients that
know better to do so, but strongly encourages most client
implementations to use SRV records.

--=20
John A. Tamplin
Software Engineer (GWT), Google

From gregw@intalio.com  Thu Jul 21 19:51:05 2011
Return-Path: <gregw@intalio.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 113E211E8086; Thu, 21 Jul 2011 19:51:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.843
X-Spam-Level: 
X-Spam-Status: No, score=-2.843 tagged_above=-999 required=5 tests=[AWL=0.134,  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 4wdn9fsGCXhA; Thu, 21 Jul 2011 19:51:04 -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 5585811E8080; Thu, 21 Jul 2011 19:51:04 -0700 (PDT)
Received: by vxi40 with SMTP id 40so1656763vxi.31 for <multiple recipients>; Thu, 21 Jul 2011 19:51:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.76.197 with SMTP id m5mr956820vdw.308.1311303063749; Thu, 21 Jul 2011 19:51:03 -0700 (PDT)
Received: by 10.52.115.103 with HTTP; Thu, 21 Jul 2011 19:51:03 -0700 (PDT)
In-Reply-To: <CAP992=GedTEfimykCWwdwm=BsZdwFRJO36EO0a_o7iejURJ+tQ@mail.gmail.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <9031.1311286867.939466@puncture> <4E28BA9D.6010501@callenish.com> <CAP992=GedTEfimykCWwdwm=BsZdwFRJO36EO0a_o7iejURJ+tQ@mail.gmail.com>
Date: Fri, 22 Jul 2011 12:51:03 +1000
Message-ID: <CAH_y2NEi9PStBQ2pzhswrWnipZR+0J0XSvZe_CwC0trGMEAXEg@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: Greg Wilkins <gregw@intalio.com>
To: David Endicott <dendicott@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Sat, 23 Jul 2011 09:42:33 -0700
Cc: Server-Initiated HTTP <hybi@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, 22 Jul 2011 02:51:05 -0000

I agree that DNS SRV is a matter outside the scope of  websockets,
which (for better or for worse) use a connection that is established
via a HTTP request.   Thus I do not think that the establishment of a
HTTP connection for websockets should differ in any way from the name
resolution handling of other HTTP connections made by a user-agent.
If the advocates of DNS SRV wish for websocket to use it, then they
need to convince HTTPbis (I think that is the right WG?) to adopt it
for all of HTTP and then websockets will inherit that feature.

If in future, there is a proposal to directly establish websocket
connections without a HTTP upgrade (as David Endicott has alluded to),
then I think DNS SRV should definitely be supported.

regards

From w@1wt.eu  Thu Jul 21 22:43:59 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10B1221F869E; Thu, 21 Jul 2011 22:43:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.279
X-Spam-Level: 
X-Spam-Status: No, score=-5.279 tagged_above=-999 required=5 tests=[AWL=-3.536, BAYES_00=-2.599, HELO_IS_SMALL6=0.556, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jS9WjeMI4+2d; Thu, 21 Jul 2011 22:43:58 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 3706721F866A; Thu, 21 Jul 2011 22:43:57 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6M5hjQ1019378; Fri, 22 Jul 2011 07:43:45 +0200
Date: Fri, 22 Jul 2011 07:43:45 +0200
From: Willy Tarreau <w@1wt.eu>
To: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110722054345.GE18126@1wt.eu>
References: <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <CALiegf=4K2oWfmZjGMD7J_jyaDtS3i+Mu7R0Wh75Rr+MrQCjtw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CALiegf=4K2oWfmZjGMD7J_jyaDtS3i+Mu7R0Wh75Rr+MrQCjtw@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Sat, 23 Jul 2011 09:42:33 -0700
Cc: Server-Initiated HTTP <hybi@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, 22 Jul 2011 05:43:59 -0000

On Fri, Jul 22, 2011 at 01:22:15AM +0200, Iñaki Baz Castillo wrote:
> Well, in SIP there are NAPTR records because SIP can work over
> different transports (UDP, TCP, TLS-TCP. SCTP, TLS-SCTP). In case of
> WebSocket, it just defined for TCP so NAPTR records don't make sense.
> 
> So just SRV is required:
> 
> a)  _ws._tcp.DOMAIN.COM    for WS URI
> b)  _wss._tcp.DOMAIN.COM   for WSS URI

Iñaki, what we're saying is that the resolving applies first to HTTP
well before it is WS. For instance, a client could connect to an HTTP
server, fetch a few objects, then decide to upgrade the connection to
switch to WebSocket. DNS resolving for WS would not even be involved
here.

I agree with what others have been saying : if/when a different handshake
is supported, eg. on a specific port without the HTTP upgrade, then it
will make sense. But as of now we're relying on the lower layer. As Greg
said it, without a deep change in HTTP you won't be able to make the rule
a MUST for WS. However, John's suggest of using a SHOULD when the record
exists and the client can see it looks fine. What's the problem if not all
of your clients go to the same hosts ? You can even announce all of your
servers with A/AAAA and with SRV as well as long as they're running on the
same ports. Those who can use SRV just have more information than the other
ones and can be served better.

Regards,
Willy


From dendicott@gmail.com  Fri Jul 22 06:39:56 2011
Return-Path: <dendicott@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68A2521F89A1; Fri, 22 Jul 2011 06:39:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.572
X-Spam-Level: 
X-Spam-Status: No, score=-3.572 tagged_above=-999 required=5 tests=[AWL=0.026,  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 3jWhak6rv5tX; Fri, 22 Jul 2011 06:39:55 -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 7417621F89B8; Fri, 22 Jul 2011 06:39:55 -0700 (PDT)
Received: by wyj26 with SMTP id 26so1734185wyj.31 for <multiple recipients>; Fri, 22 Jul 2011 06:39:54 -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=xYBLA/SIP9nqRan8Hzjo1Um9ANmWy9q5Li7FKqzp1gg=; b=mLlEbIFAOxdN8vRLQhs1O41iMoEw9IuBDvoZhNRh8C3QxzYtPBzqv+Vd2WiByGOTQC 6HQMPTtL9s5uK8EEQR75hoLDQh5QIHOswaILUpeeZ+2G52ZNmmAL1PT+aZ3CP9aGqsz3 dOgr4yYy2ogesHHyo8o5K7nrqIw+m78LbXwNg=
MIME-Version: 1.0
Received: by 10.216.79.74 with SMTP id h52mr1473558wee.33.1311341994460; Fri, 22 Jul 2011 06:39:54 -0700 (PDT)
Received: by 10.216.39.197 with HTTP; Fri, 22 Jul 2011 06:39:53 -0700 (PDT)
In-Reply-To: <9031.1311328519.488604@puncture>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <9031.1311286867.939466@puncture> <4E28BA9D.6010501@callenish.com> <CAP992=GedTEfimykCWwdwm=BsZdwFRJO36EO0a_o7iejURJ+tQ@mail.gmail.com> <9031.1311328519.488604@puncture>
Date: Fri, 22 Jul 2011 09:39:53 -0400
Message-ID: <CAP992=GuGMB7e=skLnW=gjQU0rnbh2BD2A_bRyy3Fkrphmj=VQ@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: David Endicott <dendicott@gmail.com>
To: Dave Cridland <dave@cridland.net>
Content-Type: multipart/alternative; boundary=000e0cd342b6c245a504a8a899d0
X-Mailman-Approved-At: Sat, 23 Jul 2011 09:42:33 -0700
Cc: Server-Initiated HTTP <hybi@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, 22 Jul 2011 13:39:56 -0000

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

Good to know, thank you.

On Fri, Jul 22, 2011 at 5:55 AM, Dave Cridland <dave@cridland.net> wrote:

> On Fri Jul 22 03:24:41 2011, David Endicott wrote:
>
>> there are added inefficiencies.   Also the name resolution of the HTTP
>> that
>> serves the Javascript that opens the WS should remain constant.   If WS
>> resolves the host/domain to a different address than the HTTP it was
>> spawned
>> from, it becomes a method to bypass same-origin / CORS restrictions.
>>
>
> That's an unfortunate misunderstanding.
>
> All protocols that use SRV records maintain the target domain.
>
> So a ws://example.com/xyz would still send a Host header of "example.com",
> whether SRV or not, so there is no impact on same origin policy, CORS, etc.
>
>
> Dave.
> --
> Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
>  - acap://acap.dave.cridland.net/**byowner/user/dwd/bookmarks/<http://acap.dave.cridland.net/byowner/user/dwd/bookmarks/>
>  - http://dave.cridland.net/
> Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
>

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

Good to know, thank you.<br><br><div class=3D"gmail_quote">On Fri, Jul 22, =
2011 at 5:55 AM, Dave Cridland <span dir=3D"ltr">&lt;<a href=3D"mailto:dave=
@cridland.net">dave@cridland.net</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex;">
<div class=3D"im">On Fri Jul 22 03:24:41 2011, David Endicott wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
there are added inefficiencies. =A0 Also the name resolution of the HTTP th=
at<br>
serves the Javascript that opens the WS should remain constant. =A0 If WS<b=
r>
resolves the host/domain to a different address than the HTTP it was spawne=
d<br>
from, it becomes a method to bypass same-origin / CORS restrictions.<br>
</blockquote>
<br></div>
That&#39;s an unfortunate misunderstanding.<br>
<br>
All protocols that use SRV records maintain the target domain.<br>
<br>
So a ws://<a href=3D"http://example.com/xyz" target=3D"_blank">example.com/=
xyz</a> would still send a Host header of &quot;<a href=3D"http://example.c=
om" target=3D"_blank">example.com</a>&quot;, whether SRV or not, so there i=
s no impact on same origin policy, CORS, etc.<div>
<div></div><div class=3D"h5"><br>
<br>
Dave.<br>
-- <br>
Dave Cridland - mailto:<a href=3D"mailto:dave@cridland.net" target=3D"_blan=
k">dave@cridland.net</a> - <a href=3D"mailto:xmpp%3Adwd@dave.cridland.net" =
target=3D"_blank">xmpp:dwd@dave.cridland.net</a><br>
=A0- acap://<a href=3D"http://acap.dave.cridland.net/byowner/user/dwd/bookm=
arks/" target=3D"_blank">acap.dave.cridland.net/<u></u>byowner/user/dwd/boo=
kmarks/</a><br>
=A0- <a href=3D"http://dave.cridland.net/" target=3D"_blank">http://dave.cr=
idland.net/</a><br>
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade<br>
</div></div></blockquote></div><br>

--000e0cd342b6c245a504a8a899d0--

From dendicott@gmail.com  Fri Jul 22 06:47:40 2011
Return-Path: <dendicott@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B94F421F8531; Fri, 22 Jul 2011 06:47:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.573
X-Spam-Level: 
X-Spam-Status: No, score=-3.573 tagged_above=-999 required=5 tests=[AWL=0.025,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Vxt6zZSq9-o; Fri, 22 Jul 2011 06:47:40 -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 1527821F8515; Fri, 22 Jul 2011 06:47:33 -0700 (PDT)
Received: by wwe5 with SMTP id 5so1517549wwe.13 for <multiple recipients>; Fri, 22 Jul 2011 06:47:33 -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=UGfwX4W0mqUSwtSnf/ahEA6EjDJLU+9IqYq4bVewc50=; b=nW5SeYF22y8sZPh0UW7EBLsdmGm8SlYF9c+VwpJyaHcYoQfbGtdNPBI+VMFgd5qKNv e1s5GkY/jVI7Xwnv5cWt3DmyUEhx2WulVYYuSDUVBruBw1I3Jr3azW+VZVZOT8yokSB7 XUdFcvMwHAhV5i8HN+G3MI8+eWl5w/m3wzM+o=
MIME-Version: 1.0
Received: by 10.216.1.200 with SMTP id 50mr2100722wed.33.1311342453158; Fri, 22 Jul 2011 06:47:33 -0700 (PDT)
Received: by 10.216.39.197 with HTTP; Fri, 22 Jul 2011 06:47:31 -0700 (PDT)
In-Reply-To: <CAP992=GuGMB7e=skLnW=gjQU0rnbh2BD2A_bRyy3Fkrphmj=VQ@mail.gmail.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <9031.1311286867.939466@puncture> <4E28BA9D.6010501@callenish.com> <CAP992=GedTEfimykCWwdwm=BsZdwFRJO36EO0a_o7iejURJ+tQ@mail.gmail.com> <9031.1311328519.488604@puncture> <CAP992=GuGMB7e=skLnW=gjQU0rnbh2BD2A_bRyy3Fkrphmj=VQ@mail.gmail.com>
Date: Fri, 22 Jul 2011 09:47:31 -0400
Message-ID: <CAP992=FCQ4uLBw5RWsBjEy-ayZDKkzs4A3j4U37x1n=ZNbwb1A@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: David Endicott <dendicott@gmail.com>
To: Dave Cridland <dave@cridland.net>
Content-Type: multipart/alternative; boundary=0016364d2c791977f404a8a8b552
X-Mailman-Approved-At: Sat, 23 Jul 2011 09:42:33 -0700
Cc: Server-Initiated HTTP <hybi@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, 22 Jul 2011 13:47:40 -0000

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

serves the Javascript that opens the WS should remain constant.   If WS

> resolves the host/domain to a different address than the HTTP it was
>>> spawned
>>> from, it becomes a method to bypass same-origin / CORS restrictions.
>>>
>>
>> That's an unfortunate misunderstanding.
>>
>> All protocols that use SRV records maintain the target domain.
>>
>> So a ws://example.com/xyz would still send a Host header of "example.com",
>> whether SRV or not, so there is no impact on same origin policy, CORS, etc.
>>
>>
> Good to know, thank you.

Actually....I wasn't talking about the Host: header - that is totally
spoofable...I was concerned about:

1. Browser client resolves example.com via old style DNS to x.x.x.x and
fetches HTTP
2. Received HTML starts JS which starts WS connection
3. WS resolves example.com via DNS SRV to y.y.y.y and opens
4. WS now has access outside origin.

Please note, I did not specify why DNS SRV resolved differently than old
style DNS - could be malicious, could be an simple mistake.     I am
assuming the DNS SRV and old DNS might be answered from different servers.

Do browsers restrict origin / cross-site access based on name or on address?

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

<br>serves the Javascript that opens the WS should remain constant. =A0 If =
WS<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div =
class=3D"h5">
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">

resolves the host/domain to a different address than the HTTP it was spawne=
d<br>
from, it becomes a method to bypass same-origin / CORS restrictions.<br>
</blockquote>
<br></div>
That&#39;s an unfortunate misunderstanding.<br>
<br>
All protocols that use SRV records maintain the target domain.<br>
<br>
So a ws://<a href=3D"http://example.com/xyz" target=3D"_blank">example.com/=
xyz</a> would still send a Host header of &quot;<a href=3D"http://example.c=
om" target=3D"_blank">example.com</a>&quot;, whether SRV or not, so there i=
s no impact on same origin policy, CORS, etc.<div>

<div></div><div><br></div></div></blockquote></div></div></div></blockquote=
><meta http-equiv=3D"content-type" content=3D"text/html; charset=3Dutf-8"><=
br class=3D"Apple-interchange-newline">&gt; Good to know, thank you.<div><d=
iv>
</div><div class=3D"h5"><br></div></div><div class=3D"h5">Actually....I was=
n&#39;t talking about the Host: header - that is totally spoofable...I was =
concerned about:</div><div class=3D"h5"><br></div><div class=3D"h5">1. Brow=
ser client resolves <a href=3D"http://example.com">example.com</a> via old =
style DNS to x.x.x.x and fetches HTTP</div>
<div class=3D"h5">2. Received HTML starts JS which starts WS connection</di=
v><div class=3D"h5">3. WS resolves <a href=3D"http://example.com">example.c=
om</a> via DNS SRV to y.y.y.y and opens</div><div class=3D"h5">4. WS now ha=
s access outside origin.</div>
<div class=3D"h5"><br></div><div class=3D"h5">Please note, I did not specif=
y why DNS SRV resolved differently than old style DNS - could be=A0maliciou=
s, could be an simple mistake. =A0 =A0 I am assuming the DNS SRV and old DN=
S might be answered from different servers.</div>
<div class=3D"h5"><br></div><div class=3D"h5">Do browsers restrict origin /=
 cross-site access based on name or on address? =A0=A0</div><div class=3D"h=
5"><br></div><div>=A0</div></div>

--0016364d2c791977f404a8a8b552--

From lars.eggert@nokia.com  Fri Jul 22 07:39:55 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 9605421F8ADE; Fri, 22 Jul 2011 07:39:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.257
X-Spam-Level: 
X-Spam-Status: No, score=-102.257 tagged_above=-999 required=5 tests=[AWL=-0.457, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BDsqpY8BIsNU; Fri, 22 Jul 2011 07:39:55 -0700 (PDT)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by ietfa.amsl.com (Postfix) with ESMTP id EA8DE21F8ABD; Fri, 22 Jul 2011 07:39:54 -0700 (PDT)
Received: from mail.fit.nokia.com (esdhcp030222.research.nokia.com [172.21.30.222]) by mgw-da02.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p6MEdpOG026705 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 22 Jul 2011 17:39:53 +0300
From: Lars Eggert <lars.eggert@nokia.com>
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.97.1 at fit.nokia.com
Content-Type: multipart/signed; boundary=Apple-Mail-4-178418498; protocol="application/pkcs7-signature"; micalg=sha1
Subject: Final Agenda: IRTF Open Meeting at IETF-81
Date: Fri, 22 Jul 2011 10:39:43 -0400
Message-Id: <20EE70D9-061A-47D1-822B-9DB392931520@nokia.com>
To: <irtf-discuss@irtf.org>, <irtf-announce@irtf.org>, <irsg@irtf.org>, <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, 22 Jul 2011 17:39:45 +0300 (EEST)
X-Nokia-AV: Clean
X-Mailman-Approved-At: Sat, 23 Jul 2011 09:42:33 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: irtf-discuss@irtf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jul 2011 14:39:55 -0000

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

Final Agenda
IRTF Open Meeting
Quebec City, Canada
*Wednesday*, July 27, 2011, 9:00 - 11:30 (new time!)

Slot lengths below indicate presentation+discussion time.


State of the IRTF
	Lars Eggert
	10+5 min


Applied Networking Prize (ANRP) Awards
	2x 20+10 min

	*** Beichuan Zhang *** for research into =93green=94 traffic =
engineering:
	GreenTE: Power-Aware Traffic Engineering. Mingui Zhang,
	Cheng Yi, Bin Liu and Beichuan Zhang. Proc. IEEE International
	Conference on Network Protocols (ICNP), pp. 21=9630, October =
2010.

	Abstract: Given the high path redundancy and low link
	utilization in today's large networks, one may route traffic
	using fewer number of links so that other links can go sleep
	to conserve energy. In this work we design a traffic engineering
	mechanism that maximizes the number of links to sleep under
	certain performance constraints such as link utilization and =
packet
	delay. Using network topologies and traffic data from several
	wide-area networks, our evaluation demonstrates that GreenTE is
	both feasible and beneficial.

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

	A Technique for Reducing BGP Update Announcements through Path
	Exploration Damping. Geoff Huston, Mattia Rossi and Grenville
	Armitage. IEEE Journal on Selected Areas in Communications =
(JSAC),
	Vol. 28, No. 8, pp. 1271=961286, October 2010.
=20
	Abstract: Path Exploration Damping is intended as a replacement
	for MRAI and RFD, the two main mechanisms used in BGP that aim
	at a reduction of BGP update churn. This talk explains the
	motivation behind PED, outlines the algorithm and provides
	insight into experimental results.


Presentation & discussion of proposals for new IRTF research groups

	Network Complexity
	Michael Beringer
	http://networkcomplexity.org/
	10+10 min
=09
	Information-Centric Networking
	Dirk Kutscher & B=F6rje Ohlman
	http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg
	10+10 min
=09
	Learning-Capable Communication Networks
	Dimitri Papadimitriou =20
	https://sites.google.com/site/lccngroup/
	10+10 min
=09
	If time permits:
=09
	Energy Efficient Communication
	Rolf Winter & J=FCrgen Quittek
=09=

--Apple-Mail-4-178418498
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
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDcyMjE0Mzk0NFowIwYJKoZIhvcNAQkE
MRYEFLkEgWOIdkVywuZqAWWhIpeN/pI7MIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
ABsWoyidNpB5IJozB1LD0fuDVDWt7FUzALMOf56berb1ls7UVN+t/mIET97g+eOLLDwf986gfBLx
+xKybIuUN0CItpZMfpsLe0aWRtzxnpSFu9u7ToscMVM0V68LPnwd5U6KgxNQ4sxG/HenS/w/4oDL
0RMfGR+PowIw5sA6X2xnYYlvYkAdQZyNKxJwWZ1Y5HFBkwb5aBa5q/7mcKYEGbbTE4SzVdBr3Hz+
9FaHo0CwBvDNjvrpgirntnjVENWgPjeon93Q7av4pjemWmjI22n23VzWrPeodZKyUap9/egRqJTG
2ukLiHllQAxbTDsgahcsXacJWQq70Kmh5TAT7hMAAAAAAAA=

--Apple-Mail-4-178418498--

From ted.ietf@gmail.com  Sat Jul 23 11:41:14 2011
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A19B21F853E; Sat, 23 Jul 2011 11:41:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2CQ8g5mZ6JL9; Sat, 23 Jul 2011 11:41: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 6993221F851F; Sat, 23 Jul 2011 11:41:13 -0700 (PDT)
Received: by gxk19 with SMTP id 19so1990689gxk.31 for <multiple recipients>; Sat, 23 Jul 2011 11:41:13 -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=gKEgMZCQZIIashkFB7RYuxtciCVX5noWnZ2+uFRJBDI=; b=EUGlxKGtxlQTFgaZh93yLPkEFQcgl/VhqgaWKw4SWpcFVUzNZv3MGADBM2zkN97SlB zDmYMlY86/k6Gc67VUPri9/D4uKrjpb1PUoqKKVY2Qsv2J6UxrknFYifJF3Bjn+nFPTK fFs9uFULjqQubuSK25twyDpT+ppeL/pZakeU8=
MIME-Version: 1.0
Received: by 10.236.184.33 with SMTP id r21mr3869625yhm.11.1311446471907; Sat, 23 Jul 2011 11:41:11 -0700 (PDT)
Received: by 10.236.105.133 with HTTP; Sat, 23 Jul 2011 11:41:11 -0700 (PDT)
In-Reply-To: <CAP992=FCQ4uLBw5RWsBjEy-ayZDKkzs4A3j4U37x1n=ZNbwb1A@mail.gmail.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <9031.1311286867.939466@puncture> <4E28BA9D.6010501@callenish.com> <CAP992=GedTEfimykCWwdwm=BsZdwFRJO36EO0a_o7iejURJ+tQ@mail.gmail.com> <9031.1311328519.488604@puncture> <CAP992=GuGMB7e=skLnW=gjQU0rnbh2BD2A_bRyy3Fkrphmj=VQ@mail.gmail.com> <CAP992=FCQ4uLBw5RWsBjEy-ayZDKkzs4A3j4U37x1n=ZNbwb1A@mail.gmail.com>
Date: Sat, 23 Jul 2011 14:41:11 -0400
Message-ID: <CA+9kkMBE9b=K13rJ7wTkk0V6fx5q9z7X5eVoak1_=DYT4JxYKQ@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: Ted Hardie <ted.ietf@gmail.com>
To: David Endicott <dendicott@gmail.com>
Content-Type: multipart/alternative; boundary=20cf305b0a5e1999f804a8c0edb5
Cc: Server-Initiated HTTP <hybi@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: Sat, 23 Jul 2011 18:41:14 -0000

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

On Fri, Jul 22, 2011 at 9:47 AM, David Endicott <dendicott@gmail.com> wrote:

>
> Actually....I wasn't talking about the Host: header - that is totally
> spoofable...I was concerned about:
>
> 1. Browser client resolves example.com via old style DNS to x.x.x.x and
> fetches HTTP
> 2. Received HTML starts JS which starts WS connection
> 3. WS resolves example.com via DNS SRV to y.y.y.y and opens
> 4. WS now has access outside origin.
>
> Please note, I did not specify why DNS SRV resolved differently than old
> style DNS - could be malicious, could be an simple mistake.     I am
> assuming the DNS SRV and old DNS might be answered from different servers.
>
>
You definitely could set it up such that the results from an SRV lookup
points to a different server than that resulting from a lookup of AAAA or A;
that's kind of the point.  The SRV lookup is to a service within the
original domain, but the resulting looking up could have results outside it.
 To go back to Dave Cridland's example, you can see that the result of the
SRV is another name requiring lookup.

;; ANSWER SECTION:
_xmpp-server._tcp.gmail.com. 26125 IN   SRV     5 0 5269
xmpp-server.l.google.com.
_xmpp-server._tcp.gmail.com. 26125 IN   SRV     20 0 5269
xmpp-server1.l.google.com.
_xmpp-server._tcp.gmail.com. 26125 IN   SRV     20 0 5269
xmpp-server2.l.google.com.
_xmpp-server._tcp.gmail.com. 26125 IN   SRV     20 0 5269
xmpp-server3.l.google.com.
_xmpp-server._tcp.gmail.com. 26125 IN   SRV     20 0 5269
xmpp-server4.l.google.com.

You'd have to avoid the results triggering the antibodies to a cross-site
scripting attack in order to deploy this well, in my opinion.

regards,

Ted



Do browsers restrict origin / cross-site access based on name or on address?
>
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
>

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

On Fri, Jul 22, 2011 at 9:47 AM, David Endicott <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:dendicott@gmail.com">dendicott@gmail.com</a>&gt;</span> wrote:=
<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im"><br></div><div class=3D"gmail_quote"><div>Actually....I w=
asn&#39;t talking about the Host: header - that is totally spoofable...I wa=
s concerned about:</div><div><br></div><div>1. Browser client resolves <a h=
ref=3D"http://example.com" target=3D"_blank">example.com</a> via old style =
DNS to x.x.x.x and fetches HTTP</div>

<div>2. Received HTML starts JS which starts WS connection</div><div>3. WS =
resolves <a href=3D"http://example.com" target=3D"_blank">example.com</a> v=
ia DNS SRV to y.y.y.y and opens</div><div>4. WS now has access outside orig=
in.</div>

<div><br></div><div>Please note, I did not specify why DNS SRV resolved dif=
ferently than old style DNS - could be=A0malicious, could be an simple mist=
ake. =A0 =A0 I am assuming the DNS SRV and old DNS might be answered from d=
ifferent servers.</div>

<div><br></div></div></blockquote><div><br></div><div>You definitely could =
set it up such that the results from an SRV lookup points to a different se=
rver than that resulting from a lookup of AAAA or A; that&#39;s kind of the=
 point. =A0The SRV lookup is to a service within the original domain, but t=
he resulting looking up could have results outside it. =A0To go back to Dav=
e Cridland&#39;s example, you can see that the result of the SRV is another=
 name requiring lookup. =A0</div>
<div><font class=3D"Apple-style-span" color=3D"#222222" face=3D"arial, sans=
-serif" size=3D"3"><span class=3D"Apple-style-span" style=3D"border-collaps=
e: collapse; font-size: 11px;"><font class=3D"Apple-style-span" color=3D"#0=
00000" face=3D"arial"><span class=3D"Apple-style-span" style=3D"border-coll=
apse: separate; font-size: small;"><br>
</span></font></span></font></div><div><span class=3D"Apple-style-span" sty=
le=3D"font-family: arial, sans-serif; font-size: 10.8333px; border-collapse=
: collapse; color: rgb(34, 34, 34); ">;; ANSWER SECTION:<br>_xmpp-server._<=
a href=3D"http://tcp.gmail.com/" target=3D"_blank" style=3D"color: rgb(53, =
66, 88); ">tcp.gmail.com</a>. 26125 IN =A0 SRV =A0 =A0 5 0 5269=A0<a href=
=3D"http://xmpp-server.l.google.com/" target=3D"_blank" style=3D"color: rgb=
(53, 66, 88); ">xmpp-server.l.google.com</a>.<br>
_xmpp-server._<a href=3D"http://tcp.gmail.com/" target=3D"_blank" style=3D"=
color: rgb(53, 66, 88); ">tcp.gmail.com</a>. 26125 IN =A0 SRV =A0 =A0 20 0 =
5269=A0<a href=3D"http://xmpp-server1.l.google.com/" target=3D"_blank" styl=
e=3D"color: rgb(53, 66, 88); ">xmpp-server1.l.google.com</a>.<br>
_xmpp-server._<a href=3D"http://tcp.gmail.com/" target=3D"_blank" style=3D"=
color: rgb(53, 66, 88); ">tcp.gmail.com</a>. 26125 IN =A0 SRV =A0 =A0 20 0 =
5269=A0<a href=3D"http://xmpp-server2.l.google.com/" target=3D"_blank" styl=
e=3D"color: rgb(53, 66, 88); ">xmpp-server2.l.google.com</a>.<br>
_xmpp-server._<a href=3D"http://tcp.gmail.com/" target=3D"_blank" style=3D"=
color: rgb(53, 66, 88); ">tcp.gmail.com</a>. 26125 IN =A0 SRV =A0 =A0 20 0 =
5269=A0<a href=3D"http://xmpp-server3.l.google.com/" target=3D"_blank" styl=
e=3D"color: rgb(53, 66, 88); ">xmpp-server3.l.google.com</a>.<br>
_xmpp-server._<a href=3D"http://tcp.gmail.com/" target=3D"_blank" style=3D"=
color: rgb(53, 66, 88); ">tcp.gmail.com</a>. 26125 IN =A0 SRV =A0 =A0 20 0 =
5269=A0<a href=3D"http://xmpp-server4.l.google.com/" target=3D"_blank" styl=
e=3D"color: rgb(53, 66, 88); ">xmpp-server4.l.google.com</a>.<br>
</span></div><div>=A0</div><div>You&#39;d have to avoid the results trigger=
ing the antibodies to a cross-site scripting attack in order to deploy this=
 well, in my opinion.</div><div><br></div><div>regards,</div><div><br></div=
>
<div>Ted</div><div><br></div><div><br></div><div><br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex;"><div class=3D"gmail_quote"><div></div><div>Do browsers rest=
rict origin / cross-site access based on name or on address? =A0=A0</div>
<div><br></div><div>=A0</div></div>
<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>

--20cf305b0a5e1999f804a8c0edb5--

From marka@isc.org  Sat Jul 23 14:23: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 B128A21F8BC0; Sat, 23 Jul 2011 14:23:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.606
X-Spam-Level: 
X-Spam-Status: No, score=-2.606 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z-yyuyD5ikhE; Sat, 23 Jul 2011 14:23: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 1A9D421F8BB0; Sat, 23 Jul 2011 14:23: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 31E545F990E; Sat, 23 Jul 2011 21:23:26 +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 23DCE216C81; Sat, 23 Jul 2011 21:23: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 3A6D1121E068; Sun, 24 Jul 2011 07:23:22 +1000 (EST)
To: Bruce Atherton <bruce@callenish.com>
From: Mark Andrews <marka@isc.org>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
In-reply-to: Your message of "Thu, 21 Jul 2011 15:15:59 MST." <4E28A51F.4020704@callenish.com>
Date: Sun, 24 Jul 2011 07:23:22 +1000
Message-Id: <20110723212322.3A6D1121E068@drugs.dv.isc.org>
Cc: =?ISO-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>, David Endicott <dendicott@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Jul 2011 21:23:46 -0000

In message <4E28A51F.4020704@callenish.com>, Bruce Atherton writes:
>
> I admit that I find it a little troubling to use MUST for the client to 
> follow this procedure as there is a burden on implementers to understand 
> how to code this since it isn't done by default in the standard 
> libraries the way that ordinary name resolution is. Making it the 
> recognized best practice with a SHOULD would be preferable all else 
> being equal.
 
No.  MUST is what is needed.  It's a new protocol.  Do what's best from
day one.

-- 
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  Sat Jul 23 16:25:07 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 117FE21F8ACA; Sat, 23 Jul 2011 16:25:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7UEhchkEJuSb; Sat, 23 Jul 2011 16:25:06 -0700 (PDT)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by ietfa.amsl.com (Postfix) with ESMTP id 7AAC921F874E; Sat, 23 Jul 2011 16:25:06 -0700 (PDT)
Received: from [71.166.174.114] (helo=[10.59.1.76]) by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <moore@network-heretics.com>) id 1QklZ6-0006FO-Bo; Sat, 23 Jul 2011 19:25:00 -0400
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
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: <20110723212322.3A6D1121E068@drugs.dv.isc.org>
Date: Sat, 23 Jul 2011 19:24:58 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4B5A568C-0CEA-4143-8BC5-B9E721B7AB0A@network-heretics.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <20110723212322.3A6D1121E068@drugs.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1084)
X-ELNK-Trace: 867ef52fd101ecb3d6dd28457998182d7e972de0d01da940e151995611c2cbd95dd296b26078a1eb350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 71.166.174.114
Cc: =?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>, David Endicott <dendicott@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Jul 2011 23:25:07 -0000

On Jul 23, 2011, at 5:23 PM, Mark Andrews wrote:

> In message <4E28A51F.4020704@callenish.com>, Bruce Atherton writes:
>>=20
>> I admit that I find it a little troubling to use MUST for the client =
to=20
>> follow this procedure as there is a burden on implementers to =
understand=20
>> how to code this since it isn't done by default in the standard=20
>> libraries the way that ordinary name resolution is. Making it the=20
>> recognized best practice with a SHOULD would be preferable all else=20=

>> being equal.
>=20
> No.  MUST is what is needed.  It's a new protocol.  Do what's best =
from
> day one.


Sort of agree.  If use of SRV for this protocol is really appropriate =
(which I doubt, but I haven't looked at it closely) then the protocol =
specification should say "MUST use SRV".
If use of SRV for this protocol is not appropriate, or if it's not clear =
that it's appropriate, then the specification should probably say "MUST =
NOT use SRV".=20

Either way, provide clear direction to implementors and don't leave the =
decision as to whether to use SRV up to the implementation.  That would =
create different behaviors in different implementations, which is =
clearly not desirable.

Keith


From marka@isc.org  Sun Jul 24 00:34:27 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 9AFEA21F8B66; Sun, 24 Jul 2011 00:34:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.606
X-Spam-Level: 
X-Spam-Status: No, score=-2.606 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9OFYKIrVH22E; Sun, 24 Jul 2011 00:34:26 -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 5B7A821F8AFA; Sun, 24 Jul 2011 00:34:26 -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 E5D635F9919; Sun, 24 Jul 2011 07:34: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 9E5D8216C84; Sun, 24 Jul 2011 07:33:27 +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 EEAAF121E985; Sun, 24 Jul 2011 17:33:23 +1000 (EST)
To: "Roy T. Fielding" <fielding@gbiv.com>
From: Mark Andrews <marka@isc.org>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
In-reply-to: Your message of "Fri, 22 Jul 2011 15:44:19 MST." <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com>
Date: Sun, 24 Jul 2011 17:33:23 +1000
Message-Id: <20110724073323.EEAAF121E985@drugs.dv.isc.org>
Cc: =?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2011 07:34:27 -0000

In message <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com>, "Roy T. Fielding" writes:
> On Jul 21, 2011, at 10:52 AM, I=F1aki Baz Castillo wrote:
> 
> > 2011/7/21 Dave Cridland <dave@cridland.net>:
> >> It's proven impossible, despite effort, to retrofit SRV onto HTTP; there=
>  is
> >> no way it'll be possible to retrofit onto WS.
> > =
> 
> > Right. If WS borns with no SRV (as a MUST for WS clients) then just
> > forget it and let inherit all the ugly limitations from HTTP protocol.
> 
> I am tired of this.  SRV is not used for HTTP because SRV adds latency
> to the initial request for no useful purpose whatsoever.

How do you solve the problem of hosting just "http://example.com/"
on "s1.joes-web-service.com" and not redirect everything else at
example.com?  People have been complaining about this for about as
long as the web has existed.

> SRV records for
> XMPP and MX records for mail are useful because there is only one such
> server expected per domain and it is *very* desirable to maintain central
> control over that routing.  In contrast, HTTP is deployed in an anarchic
> manner in which there are often several HTTP servers per machine
> (e.g., tests, staging, production, CUPS, etc,).  AFAICT, WebSockets is
> even more anarchic than HTTP -- it will have to be, given that the sane
> network admins will block it by default.
> 
> In short, SRV is not used by the Web because it is inappropriate for HTTP.
> I have seen no reason to believe that it would be appropriate for WebSocket=
> s.
> If you want SRV to be part of the proposed standard, then you have to convi=
> nce
> the people implementing WS to use SRV.  None have done so, yet, so we can't
> expect the editor to add it to the spec just because you have an opinion.
> 
> ....Roy
> _______________________________________________
> 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 dave@cridland.net  Sun Jul 24 02:35:54 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 2C88F21F8A1A; Sun, 24 Jul 2011 02:35:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.392
X-Spam-Level: 
X-Spam-Status: No, score=-2.392 tagged_above=-999 required=5 tests=[AWL=-0.093, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FTgogsdeEhLT; Sun, 24 Jul 2011 02:35:53 -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 50F2421F88B6; Sun, 24 Jul 2011 02:35:53 -0700 (PDT)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id 50EDC1168087; Sun, 24 Jul 2011 10:35:48 +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 dDU7BpVS5PZQ; Sun, 24 Jul 2011 10:35:45 +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 AA4DC1168067; Sun, 24 Jul 2011 10:35:45 +0100 (BST)
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <CALiegf=4K2oWfmZjGMD7J_jyaDtS3i+Mu7R0Wh75Rr+MrQCjtw@mail.gmail.com> <20110722054345.GE18126@1wt.eu>
In-Reply-To: <20110722054345.GE18126@1wt.eu>
MIME-Version: 1.0
Message-Id: <9031.1311500145.687172@puncture>
Date: Sun, 24 Jul 2011 10:35:45 +0100
From: Dave Cridland <dave@cridland.net>
To: Willy Tarreau <w@1wt.eu>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>, =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Content-Type: text/plain; delsp="yes"; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: 8Bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2011 09:35:54 -0000

On Fri Jul 22 06:43:45 2011, Willy Tarreau wrote:
> Iñaki, what we're saying is that the resolving applies first to HTTP
> well before it is WS. For instance, a client could connect to an  
> HTTP
> server, fetch a few objects, then decide to upgrade the connection  
> to
> switch to WebSocket. DNS resolving for WS would not even be involved
> here.
> 
> 
I get where you're coming from.

You're saying that you have a nebulous connection thing, that you  
pump HTTP requests down, and you may want to use that for WebSocket  
upgrade requests as well, by taking the ws URI and performing a  
simple transformation on it into an HTTP URI to make the upgrade  
request on.

So, given ws://example.com/foo/bar, you'll make the upgrade request  
on http://example.com/foo/bar

What Iñaki and I are arguing for is that for WS, there is simply one  
additional step prior to finding a suitable connection, which is  
performing an SRV lookup/selection.

And this new step can actually be performed before any of the HTTP  
connection steps. So, roughly, in order to "do" WebSocket for  
ws://example.com/foo/bar you would first do SRV lookup, which would  
give you an equivalent HTTP URI to perform the upgrade request. So  
for example, if you got:

_ws._tcp.example.com SRV 1 0 ws.example.com

You'd make the upgrade request on the HTTP URI of:

http://ws.example.com/foo/bar

Of course, if this failed to connect, you can find another HTTP URI  
to try - something you cannot do without SRV.

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  Sun Jul 24 08:19:25 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 C7ED421F85F7; Sun, 24 Jul 2011 08:19:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8qSnY+OEk6N4; Sun, 24 Jul 2011 08:19:25 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 01A9621F85C0; Sun, 24 Jul 2011 08:19:25 -0700 (PDT)
Received: from [192.168.6.178] ((unknown) [64.134.67.241])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <Tiw3-QB=gD6Y@rufus.isode.com>; Sun, 24 Jul 2011 16:19:22 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4E2C383C.4020108@isode.com>
Date: Sun, 24 Jul 2011 11:20:28 -0400
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.21) Gecko/20090303 SeaMonkey/1.1.15
To: Dave Cridland <dave@cridland.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture>
In-Reply-To: <9031.1311270000.588511@puncture>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>, David Endicott <dendicott@gmail.com>, Willy Tarreau <w@1wt.eu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2011 15:19:25 -0000

Dave Cridland wrote:
> On Thu Jul 21 18:18:31 2011, David Endicott wrote:
>> It is my opinion that name resolution (however done) is outside the 
>> purview
>> of WS.   It may be handled in any number of ways by the client, and must
>> happen *before* WS establishes it's TCP connection and begins 
>> handshaking.
>
> The URI scheme is defined here, and absolutely must explain whether 
> it's a host (for direct address lookup), or a domain (for SRV).
>
> It's proven impossible, despite effort, to retrofit SRV onto HTTP; 
> there is no way it'll be possible to retrofit onto WS.
In my capacity of a WG participant:
+1



From hsantos@isdg.net  Sun Jul 24 09:36:29 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 6709521F84ED for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 09:36:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.204
X-Spam-Level: 
X-Spam-Status: No, score=-4.204 tagged_above=-999 required=5 tests=[AWL=-1.605, 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 4OYVp-jE2YR1 for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 09:36:28 -0700 (PDT)
Received: from winserver.com (mail.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 2F8B121F84EB for <ietf@ietf.org>; Sun, 24 Jul 2011 09:36:27 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1650; t=1311525383; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=M6S8Prp5lpROwQIFBpbHWDyCdLQ=; b=VtXNEp+BVMTiZqTUJUa8 e3PKYh0S0r0QJTDLFB5sjbV2lEjVjjKNn9XrV+aU9f04OhZk9Ekn1pERTkRvcyHc SXsICWIZ2VnLSuAxXrpxIhA+TtULvxIKTJVHuNhIdv1hUp8Fz6OouPtAullQGCzq Cul3QIckmAsX2tLSwScbaq0=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Sun, 24 Jul 2011 12:36:23 -0400
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 4275844885.15152.5028; Sun, 24 Jul 2011 12:36:22 -0400
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Sun, 24 Jul 2011 12:32:06 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 952165112.351.3528; Sun, 24 Jul 2011 12:32:06 -0400
Message-ID: <4E2C4A1C.6010605@isdg.net>
Date: Sun, 24 Jul 2011 12:36:44 -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: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com>	<CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com>	<9031.1311082001.631622@puncture>	<CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com>	<CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com>	<CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com>	<20110721163910.GA16854@1wt.eu>	<CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com>	<9031.1311270000.588511@puncture>	<4E28C035.6020009@necom830.hpcl.titech.ac.jp>	<9031.1311328268.180517@puncture> <4E295249.5060700@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4E295249.5060700@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2011 16:36:29 -0000

Masataka Ohta wrote:
> Dave Cridland wrote:
> 
>>> Where is a proof?
>> Sorry, I've a habit of using the word "proof" in the English
> 
>> 1) There are no SRV records.
>> 2) Therefore browsers do not support them.
>> 3) Therefore you'd need to allow for A-lookup as fallback for the 
>> forseeable future.
>> 4) Therefore there's no incentive for browsers to support SRV.
> 
> That's a perfect proof against IPv6 deployment. Infrastructure
> won't be updated.
> 
> However, for application layers issues like SRV ones, thanks to
> the end to end argument, only servers and clients need
> upgrading without infrastructure changes, which is why major
> application of the Internet changed from ftp to http.

Where is a proof?  :)

A Major Application will offer all services necessary for the customer 
to leverage. They are not going to eliminate ftp just because the 
"developer" likes http better or whats customers to switch to http. 
Even then, where I have seen a history of people using a http link, I 
have also seen many changed back, if only to help balance or spread loads.

My personal technical input on SRV.  It works when particular 
applications needs them or have become dependent on them in order to 
resolve connectivity. i.e. xmpp. But to me, there is an awful lot of 
waste and redundant lookups just to resolve an uri.  It would appear 
to me for web sockets, due to its intended market place of returning 
interactive I/O applications now over the web and specially mobile and 
wireless networks, the less overhead the better.

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com




From sidialimaiga@yahoo.fr  Sun Jul 24 09:46:19 2011
Return-Path: <sidialimaiga@yahoo.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 CD8AB21F84E1 for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 09:46:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level: 
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 c3F+bj+7mNoJ for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 09:46:19 -0700 (PDT)
Received: from nm14-vm0.bullet.mail.ird.yahoo.com (nm14-vm0.bullet.mail.ird.yahoo.com [77.238.189.193]) by ietfa.amsl.com (Postfix) with SMTP id ADD0021F8519 for <ietf@ietf.org>; Sun, 24 Jul 2011 09:46:18 -0700 (PDT)
Received: from [77.238.189.48] by nm14.bullet.mail.ird.yahoo.com with NNFMP; 24 Jul 2011 16:46:17 -0000
Received: from [212.82.108.248] by tm1.bullet.mail.ird.yahoo.com with NNFMP; 24 Jul 2011 16:46:17 -0000
Received: from [127.0.0.1] by omp1013.mail.ird.yahoo.com with NNFMP; 24 Jul 2011 16:46:17 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 938181.411.bm@omp1013.mail.ird.yahoo.com
Received: (qmail 89702 invoked by uid 60001); 24 Jul 2011 16:46:17 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.fr; s=s1024; t=1311525977; bh=cHwlEfJEzr2XDhoq/2LCUdUBHIMFgCh+Lpg9bbcXChw=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=D2731m+C7mIvnISL4+KcSH15Y/85FFh0rnrsJ6C+EhqWymgQtp3Ob4Tt/I33cdBNe51G8ZckA0UKutptSMlAPz8cFoQ87g/h+zpkzuyGTMufK1pFYbDaCQ232GIUONW3COdnTL8igrqAQg52vgGGEHz39Or20H94gSeaR9uzm2s=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.fr; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=cHa+9Aj6MGBYFgvEfOaSShpNow8okff08IMBL/Bqtmt8H+c8HMs8bhqQETfK717l79PD+uwO4ATPAIZopYlBEqEzrNaFPZSLlz0FkaxHbGtaMzDtIHu89cDfQC1/O7xR/B+gvtCZgx/bDH6n3oHaPetLrZ5I0tzvPoCrDDvx19E=;
X-YMail-OSG: XdnSfO4VM1k3gHh4g9o1OKjp6cb4jvAgD4rjhM6qus0d3_u si_vmQqIK8FV7yqxDc16Ns3pJRKGfn0o7XWWFjzDfVJm5LMxY0.C5Uwkcd3x IGvG82anBFJN.ExgAE6ewvX4wmURsz013O5nCvTq4.DdPbj.gDndeJRN1gA6 iR0XIccZf2lmQj.hmp_YNK1KvMByF7DuKerUbEtNSMN64upLgtbAl7QcpCjd syRbOk24NCGVt.QtnQUJJ.wB0svibhUq51EIwFMU9uWZPaCdSnvGTY6zzhkT wGVnRPTmCjnrwy0cdAVYIRbUCl7gSPJUyfZERyl8lG7_jb5J8kyUZb07QZrU bREg3qTnLBb6oK7bP6NiMUXrxuw--
Received: from [41.203.132.22] by web29501.mail.ird.yahoo.com via HTTP; Sun, 24 Jul 2011 17:46:17 BST
X-Mailer: YahooMailWebService/0.8.112.310352
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <9031.1311286867.939466@puncture> <4E28BA9D.6010501@callenish.com> <CAP992=GedTEfimykCWwdwm=BsZdwFRJO36EO0a_o7iejURJ+tQ@mail.gmail.com> <9031.1311328519.488604@puncture> <CAP992=GuGMB7e=skLnW=gjQU0rnbh2BD2A_bRyy3Fkrphmj=VQ@mail.gmail.com> <CAP992=FCQ4uLBw5RWsBjEy-ayZDKkzs4A3j4U37x1n=ZNbwb1A@mail.gmail.com> <CA+9kkMBE9b=K13rJ7wTkk0V6fx5q9z7X5eVoak1_=DYT4JxYKQ@mail.gmail.com>
Message-ID: <1311525977.88268.YahooMailNeo@web29501.mail.ird.yahoo.com>
Date: Sun, 24 Jul 2011 17:46:17 +0100 (BST)
From: amadou ouabanaize sidi ali <sidialimaiga@yahoo.fr>
Subject: DNS, IPV6
To: IETF-Discussion <ietf@ietf.org>
In-Reply-To: <CA+9kkMBE9b=K13rJ7wTkk0V6fx5q9z7X5eVoak1_=DYT4JxYKQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-254748704-1311525977=:88268"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: amadou ouabanaize sidi ali <sidialimaiga@yahoo.fr>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2011 16:46:19 -0000

--0-254748704-1311525977=:88268
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Dear All=0AI nead documentations about DNS et IPv6 architecture and impl=E9=
mentation=0AThanks =0A=0A=A0=0AAMADOU OUABANAIZE Sidi Ali=0AIng=E9nieur d'E=
tat en Informatique=0AEnseignant =E0 l'Universit=E9 de Tahoua=0ABP:256 Taho=
ua (Niger)=0ACel: +22796893540 / +22794025704 / +22790385974=0A=0A=0A______=
__________________________
--0-254748704-1311525977=:88268
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:ti=
mes new roman, new york, times, serif;font-size:18pt"><div><span>Dear All</=
span></div><div><span>I nead documentations about DNS et IPv6 architecture =
and impl=E9mentation</span></div><div><span>Thanks <br></span></div><div>&n=
bsp;</div><div>AMADOU OUABANAIZE Sidi Ali<br>Ing=E9nieur d'Etat en Informat=
ique<br>Enseignant =E0 l'Universit=E9 de Tahoua<br>BP:256 Tahoua (Niger)<br=
>Cel: +22796893540 / +22794025704 / +22790385974<br></div><div style=3D"fon=
t-family: times new roman, new york, times, serif; font-size: 18pt;"><div s=
tyle=3D"font-family: times new roman, new york, times, serif; font-size: 12=
pt;"><font face=3D"Arial" size=3D"2"><hr size=3D"1"><b><span style=3D"font-=
weight:bold;"></span></b></font><br></div></div></div></body></html>
--0-254748704-1311525977=:88268--

From fielding@gbiv.com  Sun Jul 24 10:56:44 2011
Return-Path: <fielding@gbiv.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 315F121F85C7; Sun, 24 Jul 2011 10:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.822
X-Spam-Level: 
X-Spam-Status: No, score=-105.822 tagged_above=-999 required=5 tests=[AWL=-3.523, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MkFcVxv4Vmbd; Sun, 24 Jul 2011 10:56:43 -0700 (PDT)
Received: from homiemail-a73.g.dreamhost.com (caiajhbdccah.dreamhost.com [208.97.132.207]) by ietfa.amsl.com (Postfix) with ESMTP id 6192621F85B2; Sun, 24 Jul 2011 10:56:43 -0700 (PDT)
Received: from homiemail-a73.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a73.g.dreamhost.com (Postfix) with ESMTP id 0C34D1F007C; Sun, 24 Jul 2011 10:56:43 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gbiv.com; h=subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to; q=dns; s=gbiv.com; b=ZRvC29jS4DOhAMQs +Hs8+p4MHqihwn8q9Nwp2rLNHLV2nQhZtvikCjcpRFK+Ynl6p4a7h2WWIWfzO9e6 +OFAJgn+tLM+s15xCdKRn7YM75W1FsSZUwVgU7X/QJeE3NOuPvHci7YW1hNrVG1v bfqx+WwdXB60ayt1SgrYDIsGqbg=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gbiv.com; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=gbiv.com; bh=tFMP/mBbwmvsZgtn7F6q7h+RYN8=; b=QOUExY6ESAVWqtk78QcnSBmbkW+p 70RuF3+7+GjlmZ59IRNbkbBHYFZ7FRAgefyLrZOkjEeq/VirfZP/l32Oa6SW17L+ 2I8GZFUibOboxJ6TakRVKLETg1y1x6zu5nlsor8ZFbpfkV0qy+uNe9SvNJFtGeU/ WlFjF9AO9MbyOIU=
Received: from [192.168.1.84] (99-21-208-82.lightspeed.irvnca.sbcglobal.net [99.21.208.82]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: fielding@gbiv.com) by homiemail-a73.g.dreamhost.com (Postfix) with ESMTPSA id AFBB51F0078;  Sun, 24 Jul 2011 10:56:42 -0700 (PDT)
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: "Roy T. Fielding" <fielding@gbiv.com>
In-Reply-To: <CALiegfkshhJVUHzTD1Kka5+RjGwZ5CS2J=Qk92jfSBg6Z0VfOQ@mail.gmail.com>
Date: Sun, 24 Jul 2011 10:56:41 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C9CD680E-8D68-4380-A76F-70F41F30F877@gbiv.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com> <CALiegfkshhJVUHzTD1Kka5+RjGwZ5CS2J=Qk92jfSBg6Z0VfOQ@mail.gmail.com>
To: =?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
X-Mailer: Apple Mail (2.1084)
Cc: Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2011 17:56:44 -0000

On Jul 24, 2011, at 4:42 AM, I=F1aki Baz Castillo wrote:

> 2011/7/23 Roy T. Fielding <fielding@gbiv.com>:
>>> Right. If WS borns with no SRV (as a MUST for WS clients) then just
>>> forget it and let inherit all the ugly limitations from HTTP =
protocol.
>>=20
>> I am tired of this.  SRV is not used for HTTP because SRV adds =
latency
>> to the initial request for no useful purpose whatsoever.
>=20
> And I'm really tired of hearing the argument of the "latency" which
> nobody demostrates (but just talks about it without replying me how
> the same is not a problem in realtime protocols like SIP and XMPP).

Try using a protocol analyzer.  It is a problem with SIP and XMPP.
Chat and telephony have different user expectations about the initial
connect time, so people just don't notice it as much as they do when
a web page rendering process stalls because embedded resources require
two additional DNS requests.

>> SRV records for
>> XMPP and MX records for mail are useful because there is only one =
such
>> server expected per domain
>=20
> $ host -t srv _xmpp-server._tcp.gmail.com
> _xmpp-server._tcp.gmail.com has SRV record 5 0 5269 =
xmpp-server.l.google.com.
> _xmpp-server._tcp.gmail.com has SRV record 20 0 5269 =
xmpp-server3.l.google.com.
> _xmpp-server._tcp.gmail.com has SRV record 20 0 5269 =
xmpp-server2.l.google.com.
> _xmpp-server._tcp.gmail.com has SRV record 20 0 5269 =
xmpp-server4.l.google.com.
> _xmpp-server._tcp.gmail.com has SRV record 20 0 5269 =
xmpp-server1.l.google.com.
>=20
> No comments.

I meant server as in authority to answer for the domain, of course.

>> and it is *very* desirable to maintain central
>> control over that routing.
>=20
> I don't know what this means.

It means that admins care a great deal about what machines in the =
network
are allowed to receive mail for that network, and likewise for XMPP, =
since
both are store and forward protocols that contain messages with personal
information for individual addresses which are routed on a hop-by-hop =
basis.
HTTP has none of those characteristics.  Hence, Mail and XMPP are =
centralized
services for an entire domain, whereas HTTP services are specific to the
services provided by each individual host.

>>  In contrast, HTTP is deployed in an anarchic
>> manner in which there are often several HTTP servers per machine
>> (e.g., tests, staging, production, CUPS, etc,).
>=20
> Could you explain me why DNS A is good but DNS SRV is bad in such
> "anarchic" deployments?

Because DNS A for a server is deployed as soon as the server is made
available on the network (Intra or Inter).  It is one of the first =
things
done when installing an OS.  SRV, in contrast, requires that the zone
manager reconfigure DNS.

>>  AFAICT, WebSockets is
>> even more anarchic than HTTP -- it will have to be, given that the =
sane
>> network admins will block it by default.
>=20
> ------------------------
>   It is up to the system administrator whether to set, or not, DNS SRV
>   resource records for the WebSocket protocol within the provided
>   service.  This specification allows the system administrator to use
>   the DNS SRV [RFC2782] mechanism to improve the service reliability =
by
>   providing load-balancing and failover capabilities, but does not
>   mandate it (the system administrator could choose whichever
>   scalability strategy).
> ------------------------

*shrug*

>> In short, SRV is not used by the Web because it is inappropriate for =
HTTP.
>> I have seen no reason to believe that it would be appropriate for =
WebSockets.
>> If you want SRV to be part of the proposed standard, then you have to =
convince
>> the people implementing WS to use SRV.  None have done so, yet, so we =
can't
>> expect the editor to add it to the spec just because you have an =
opinion.
>=20
> Ok, so the argument "I don't know SRV but I feel fine with HTTP
> limitations for years" will win. Great design decissions.

No, the argument is that I know SRV, I know a lot more about HTTP, and I =
know
for a fact that SRV is not desirable for HTTP.  So, whenever you suggest =
that
lack of SRV is somehow a failing of HTTP, you should understand that it =
makes
your arguments look clueless.  Please, find some other example.

....Roy=

From fielding@gbiv.com  Sun Jul 24 11:19:07 2011
Return-Path: <fielding@gbiv.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D89F321F8A69; Sun, 24 Jul 2011 11:19:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.72
X-Spam-Level: 
X-Spam-Status: No, score=-105.72 tagged_above=-999 required=5 tests=[AWL=-3.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 JDN9rl66bT9G; Sun, 24 Jul 2011 11:19:07 -0700 (PDT)
Received: from homiemail-a33.g.dreamhost.com (caiajhbdcahe.dreamhost.com [208.97.132.74]) by ietfa.amsl.com (Postfix) with ESMTP id 2949721F8A64; Sun, 24 Jul 2011 11:19:07 -0700 (PDT)
Received: from homiemail-a33.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a33.g.dreamhost.com (Postfix) with ESMTP id F2182594059; Sun, 24 Jul 2011 11:19:06 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gbiv.com; h=subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to; q=dns; s=gbiv.com; b=fYBJ32s0aEK4JoPp Vmdj4nSQaFQaOZP16PV+ZaSmRhaai0BepLmSL2wX2VUP8Onn2W/cfatA5ZKcCdhj C7mHS5BiMJ+EjLfy9nggp0axEoQ02IGjDgURkq+UzpAr6kvjQChehY0NslQoy7pD YFpJ6vJG3ra1v9N+ztLjv0ywIBs=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gbiv.com; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=gbiv.com; bh=Zhc5xVe4U1bC3Z/Eyfw/o3c2gZo=; b=Wtq9KxL3FMeKMy+h6pwVhJjKpOwt hOPRl5ySdNpqE31snE60AG1iwLU4CFu/nMQaLT5QHdKbZf0icys19EooupkReX7j gC+vcSzVuXZWFuWla5XjDEPY/lizGQS/mr0B6WQkBhSLODpvMIa7vEYbvTP5R6Ls uP7OAcj4eSUAXa8=
Received: from [192.168.1.84] (99-21-208-82.lightspeed.irvnca.sbcglobal.net [99.21.208.82]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: fielding@gbiv.com) by homiemail-a33.g.dreamhost.com (Postfix) with ESMTPSA id B62EC594058;  Sun, 24 Jul 2011 11:19:06 -0700 (PDT)
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: "Roy T. Fielding" <fielding@gbiv.com>
In-Reply-To: <20110724073323.EEAAF121E985@drugs.dv.isc.org>
Date: Sun, 24 Jul 2011 11:19:06 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <6B997439-029D-4290-9A4A-308B6D1EA174@gbiv.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com> <20110724073323.EEAAF121E985@drugs.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1084)
Cc: Server-Initiated HTTP <hybi@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: Sun, 24 Jul 2011 18:19:08 -0000

On Jul 24, 2011, at 12:33 AM, Mark Andrews wrote:
> In message <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com>, "Roy T. =
Fielding" writes:
>> On Jul 21, 2011, at 10:52 AM, I=3DF1aki Baz Castillo wrote:
>>=20
>>> 2011/7/21 Dave Cridland <dave@cridland.net>:
>>>> It's proven impossible, despite effort, to retrofit SRV onto HTTP; =
there=3D
>> is
>>>> no way it'll be possible to retrofit onto WS.
>>> =3D
>>=20
>>> Right. If WS borns with no SRV (as a MUST for WS clients) then just
>>> forget it and let inherit all the ugly limitations from HTTP =
protocol.
>>=20
>> I am tired of this.  SRV is not used for HTTP because SRV adds =
latency
>> to the initial request for no useful purpose whatsoever.
>=20
> How do you solve the problem of hosting just "http://example.com/"
> on "s1.joes-web-service.com" and not redirect everything else at
> example.com?  People have been complaining about this for about as
> long as the web has existed.

The Web has existed in usable form since 1991.  Name-based virtual
hosting wasn't even possible until we added Host in 1995.  In any case,
nobody has ever asked me to make the above a priority -- it simply isn't
a relevant problem compared to load balancing in general, and the =
general
problem does not assume that the client is friendly.

I would never try to "solve" load balancing by requiring every browser
to make an additional (failed) DNS SRV request each time it encounters
one of the 357,292,065 individual hostnames that are known to use HTTP,
not to mention the many millions more that are not exposed on the
Internet and don't even use DNS for resolution.  HTTP would not, cannot,
and never will benefit from SRV even if we had a magic wand that could
deploy it on all browsers.  SRV simply doesn't fit the Web architecture.

....Roy=

From derhoermi@gmx.net  Sun Jul 24 11:35:17 2011
Return-Path: <derhoermi@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDC5421F89C1 for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 11:35:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.454
X-Spam-Level: 
X-Spam-Status: No, score=-3.454 tagged_above=-999 required=5 tests=[AWL=-1.155, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XToCGEc+9RM6 for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 11:35:17 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id A763321F889A for <ietf@ietf.org>; Sun, 24 Jul 2011 11:35:16 -0700 (PDT)
Received: (qmail invoked by alias); 24 Jul 2011 18:35:15 -0000
Received: from dslb-094-223-187-169.pools.arcor-ip.net (EHLO HIVE) [94.223.187.169] by mail.gmx.net (mp014) with SMTP; 24 Jul 2011 20:35:15 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX18RC0QIXuURx89p4DThxwfpE+/tN/e3ghxM3OPDCC Yn0/a6FmRPqQ3p
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: =?ISO-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Date: Sun, 24 Jul 2011 20:35:15 +0200
Message-ID: <6epo27t0ktv3b5mtd83r05ro8nq1qoeue1@hive.bjoern.hoehrmann.de>
References: <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <9031.1311286867.939466@puncture> <4E28BA9D.6010501@callenish.com> <CAP992=GedTEfimykCWwdwm=BsZdwFRJO36EO0a_o7iejURJ+tQ@mail.gmail.com> <CALiegfnwNyYDy=SyrqHJXV0ZreADb7F8QySvgdHofW9Hm9miZQ@mail.gmail.com> <CABLsOLCgxDNDs54GUybBzmG8a6rNPzXzFcwf_OU25j5L+AobaQ@mail.gmail.com> <CALiegfnp+kNqnU-_x2ZBZnN8fzP=4+6WO=QPjw1rJzvZmSXEAg@mail.gmail.com>
In-Reply-To: <CALiegfnp+kNqnU-_x2ZBZnN8fzP=4+6WO=QPjw1rJzvZmSXEAg@mail.gmail.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2011 18:35:18 -0000

* Iñaki Baz Castillo wrote:
>Open the fastest web page and tell me how long it takes.

Too long.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From rbarnes@bbn.com  Sun Jul 24 12:11:49 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 C5BC921F89C1; Sun, 24 Jul 2011 12:11:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.591
X-Spam-Level: 
X-Spam-Status: No, score=-106.591 tagged_above=-999 required=5 tests=[AWL=0.008, 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 bsngpTSSnA9z; Sun, 24 Jul 2011 12:11:48 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 4A5AB21F899F; Sun, 24 Jul 2011 12:11:42 -0700 (PDT)
Received: from [128.89.253.15] (port=50534 helo=[130.129.64.148]) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1Ql45V-0006B9-LU; Sun, 24 Jul 2011 15:11:41 -0400
Subject: Re: Gen-ART last call review of draft-ietf-hybi-thewebsocketprotocol-10
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: "Richard L. Barnes" <rbarnes@bbn.com>
In-Reply-To: <4E26FC3F.1030300@isode.com>
Date: Sun, 24 Jul 2011 15:11:10 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <96456EE7-0BE3-444C-BA16-178FE1DF99F8@bbn.com>
References: <B9DDE41C-1451-4C97-ACA4-0E4E26B75A07@bbn.com> <4E26FC3F.1030300@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.1082)
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-websec-thewebsocketprotocol@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: Sun, 24 Jul 2011 19:11:50 -0000

Hey Alexey, =20

Thanks for following up.  A couple of responses inline.

--Richard

>> [Is GET/Upgrade appropriate?]
>> It seems like the use of GET here goes beyond the normal "safe" =
semantics for that method.  To quote RFC 2616:
>> "
>>  In particular, the convention has been established that the GET and
>>  HEAD methods SHOULD NOT have the significance of taking an action
>>  other than retrieval.
>> "
>> In addition, alternative protocols specified in Upgrade headers are =
generally optional, whereas in this case, the transaction fails overall =
if the server does not support the websocket protocol.  It doesn't look =
to me like any of the current methods provide much better semantics =
(except possiblyCONNECT or the use of OPTIONS as in RFC 2817), and it =
seems like defining a new method could help get around the Upgrade issue =
as well.
>>=20
> This issue was discussed extensively in the WG and was reraised during =
IETF LC by others. I will followup with a more detailed answer (or maybe =
the WG agrees with you and this would be changed), but a quick comment =
on one of the points.
>=20
> The WG discussed defining a new HTTP method, but the idea didn't have =
the support of majority because new HTTP methods are hard to deploy (due =
to old intermediaries which don't handle them as well as they should =
have if they were compliant with RFC 2616).

What's the argument against CONNECT?  It seems like that's exactly what =
is desired here -- for proxies to act as tunnels.  RFC 2817 uses an =
upgrade to TLS in all its examples, but the is specified more generally:
"
   Any successful (2xx) response to a CONNECT request indicates that the
   proxy has established a connection to the requested host and port,
   and has switched to tunneling the current connection to that server
   connection.
"

It seems like this gets you around the threat that masking is supposed =
to address -- the proxy won't see anything mid-stream that looks like =
HTTP, since it's just acting as a tunnel at that point.  It's a little =
weird to use CONNECT end-to-end, but that doesn't seem bad enough to be =
a blocking issue.=20


>> [Huge buffers]
>> The frame length can be 7, 16, or 64 bits long.  Since the client is =
expected to buffer data until the end of a frame, this is asking clients =
to buffer 128 B, 64 KB, or 16 EB.  If it were 32 bits, the max would be =
4 MB.  Why not just make this a 32-bit fixed length field?
>>=20
> This was discussed in the WG. On one hand the frame length encoding is =
optimized for packet size (the field overhead is small for smaller =
packets) and on another hand there was a desire to support big buffer =
sizes, thus the current proposal. I believe a single 32bit field was =
proposed but was explicitly decided against.

Actually, now that I think about it, aren't you solving the same problem =
twice, once with frame length and once with fragmentation?  If the goal =
is to have the browser buffer for me until my whole message has arrived, =
isn't that met by either a giant frame or fragmentation?  Given that, it =
seems like having a 16-bit field would even be sufficient.  It seems =
like 64k will probably cover a lot of applications (64k should be enough =
for anyone!), and for large things that use fragmentation, the header =
overhead would only be 8 octets per 64k, way down in the noise.  (3 =
octets if you get rid of masking!)=20


>> [Unlimited buffering with fragmentation]
>> Much like with the frame length issue above, the fragmentation =
mechanism here seems like it imposes a heavy burden on the receive side. =
 Since the receiving client is supposed to buffer data until the end of =
a frame, it seems like fragmentation could be used to cause a receiving =
client to buffer a frame of indefinite size.=20
> This is not really different from what other protocols like HTTP and =
SMTP already allow. I think it would be fair to note this in the =
Security Considerations section, but I don't think this feature should =
be removed. Fragmentation does allow senders to start sending data =
before the total size of the object is known (e.g. if data is generated =
on the fly), which was considered as an important feature by the WG.

A mention in the Security Considerations sounds like a sensible solution =
to me.


>> Minor issues:
>>=20
>> [Setting protocol]
>> In the NOTE in Section 1.3, the document observes that Sec- headers =
can't be set in XHRs.  But clearly the Sec-WebSocket-Protocol header can =
be set through some API that applications use to get to this protocol.  =
So it seems a little misleading to imply that scripts can't set these =
headers (besides -Version and -Origin).
>>=20
> But a script can't set the Sec-WebSocket-Protocol header field value =
directly.

That's not really true: You can't set it *directly*, in the sense that =
the following is not allowed:
   client.setRequestHeader("Sec-WebSocket-Protocol", "kick-puppies");
But you can set it by setting the protocols in the WebSocket API:
   var ws =3D new WebSocket("ws://evil.tld/kick-puppies", =
["kick-puppies"]);









From nweis@verilan.com  Sun Jul 24 12:14:20 2011
Return-Path: <nweis@verilan.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC87221F8A30 for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 12:14:20 -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.001, 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 xI3QIV16kPW9 for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 12:14:19 -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 D46C221F8A69 for <ietf@ietf.org>; Sun, 24 Jul 2011 12:14:17 -0700 (PDT)
Received: by iye7 with SMTP id 7so4739974iye.31 for <ietf@ietf.org>; Sun, 24 Jul 2011 12:14:17 -0700 (PDT)
Received: by 10.142.215.10 with SMTP id n10mr2238351wfg.290.1311534856475; Sun, 24 Jul 2011 12:14:16 -0700 (PDT)
Received: from bender.local ([130.129.0.127]) by mx.google.com with ESMTPS id t20sm2753382wfe.12.2011.07.24.12.14.15 (version=SSLv3 cipher=OTHER); Sun, 24 Jul 2011 12:14:15 -0700 (PDT)
Message-ID: <4E2C6F06.9020807@verilan.com>
Date: Sun, 24 Jul 2011 15:14:14 -0400
From: Noah Weis <nweis@verilan.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: IETF 81 Network is up and operational
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, 24 Jul 2011 19:14:21 -0000

Greetings all,

First off, welcome to Quebec City!

The network here at the Quebec City Convention Center is up and running.

Full network information is available at:

http://noc.meeting.ietf.org/wiki/IETF81network

We were able to extend the IETF network to the Hilton (thanks to a brand 
new fiber from the QCCC) - all of the guest room wired connections are 
funneling through the network here at the QCCC. All rooms are v4 and v6 
capable.

Enjoy! And, as always, please let us know should you have any issues.

-- 

Noah Weis
Verilan, Inc.
m: +1 503 902 2491

From ajs@anvilwalrusden.com  Sun Jul 24 12:54:34 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 2524C21F87D3 for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 12:54: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 hlUJrQROIUVv for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 12:54:33 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 8958F21F86BE for <ietf@ietf.org>; Sun, 24 Jul 2011 12:54:33 -0700 (PDT)
Received: from shinkuro.com (spliair.spotnik.ADSL.akn.ca [66.135.98.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 6E2241ECB41D for <ietf@ietf.org>; Sun, 24 Jul 2011 19:54:32 +0000 (UTC)
Date: Sun, 24 Jul 2011 15:54:26 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Please volunteer to keep minutes for IAOC and IETF Trust
Message-ID: <20110724195357.GA264@shinkuro.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
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: Sun, 24 Jul 2011 19:54:34 -0000

Dear colleagues,

At IETF-80 in Prague, there was a call for volunteers to be an
occasional scribe for the IAOC and IETF Trust.  Until the IETF-81
meeting, I was one of the three people who produce the minutes for the
IAOC and Trust; but I can't continue to do it because of some
conflicting commitments.

I'm writing to encourage you to volunteer.  The IAOC and Trust both
perform an important role in the operation of the IETF.  (You can
learn more at http://iaoc.ietf.org/).

The work isn't terribly onerous -- meetings happen every two weeks,
but with three people on the team you have to take a meeting on
average only once every six weeks.  There is an important commitment
of time immediately around a meeting, however, where you need to get
the minutes into shape to send out fairly quickly.

If you think you might be interested in serving on the IAOC and Trust,
taking minutes would be an excellent way to get prepared to do it.
And if you just like to know secrets (you get to learn what meeting
sites are under consideration, for instance!), it's an excellent way
to learn about the inner workings of the IETF.  On top of that, you
get to work with the clever and IETF-experienced members of the IAOC
and Trust.  If you are not deeply experienced with the IETF, this is a
great way to understand what is going on under the hood.

The meetings are conducted on the phone in English.  You don't need to
be able to do transcription; rather, what you need to be able to do is
summarize the thrust of a conversation and capture conclusions.  If
you were the sort of person who had the notes everyone else wanted
when you were in school, you'll do fine with this.  Note that meetings
are conducted in English, and if fast-paced discussion in English is
hard for you to follow on the phone, you might find this task very
taxing.

I hope you'll consider volunteering.  The other scribes will be nice
to you if you do!  The IAOC members, the IAD (Ray Pelletier), and the
other scribes (Suresh Krishnan and Karen O'Donoghue) have certainly
been nice to me.  They have also been extremely patient with me when
my other obligations caused me not to produce my minutes in a timely
fashion.  I'm grateful.

If you want to do this, and want more information, send me email or
corner me at the meeting this week (I arrive Sunday night well after
the reception, but I'll be around until Friday).  I'll tell you
everything I can.  If you just want to volunteer and don't need any
more information, your best bet is to contact Ray at <iad@ietf.org>.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From dave@cridland.net  Sun Jul 24 13:18:48 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 3A7C521F8749; Sun, 24 Jul 2011 13:18:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.388
X-Spam-Level: 
X-Spam-Status: No, score=-2.388 tagged_above=-999 required=5 tests=[AWL=-0.089, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t5Bn3xI1-uQ8; Sun, 24 Jul 2011 13:18:47 -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 0C49621F8747; Sun, 24 Jul 2011 13:18:47 -0700 (PDT)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id A20FF1168087; Sun, 24 Jul 2011 21:18:44 +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 Bre1gkv-YN4w; Sun, 24 Jul 2011 21:18:40 +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 6785E1168067; Sun, 24 Jul 2011 21:18:40 +0100 (BST)
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <9031.1311286867.939466@puncture> <4E28BA9D.6010501@callenish.com> <CAP992=GedTEfimykCWwdwm=BsZdwFRJO36EO0a_o7iejURJ+tQ@mail.gmail.com> <CALiegfnwNyYDy=SyrqHJXV0ZreADb7F8QySvgdHofW9Hm9miZQ@mail.gmail.com> <CABLsOLCgxDNDs54GUybBzmG8a6rNPzXzFcwf_OU25j5L+AobaQ@mail.gmail.com> <CALiegfnp+kNqnU-_x2ZBZnN8fzP=4+6WO=QPjw1rJzvZmSXEAg@mail.gmail.com> <20110724185949.GB22405@1wt.eu>
In-Reply-To: <20110724185949.GB22405@1wt.eu>
MIME-Version: 1.0
Message-Id: <9031.1311538720.416128@puncture>
Date: Sun, 24 Jul 2011 21:18:40 +0100
From: Dave Cridland <dave@cridland.net>
To: Willy Tarreau <w@1wt.eu>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>, =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Content-Type: text/plain; delsp="yes"; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: 8Bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2011 20:18:48 -0000

On Sun Jul 24 19:59:49 2011, Willy Tarreau wrote:
> On Sun, Jul 24, 2011 at 08:30:11PM +0200, Iñaki Baz Castillo wrote:
> > 2011/7/24 John Tamplin <jat@google.com>:
> > >> ~100 ms (if the DNS server is not local and there is no DNS  
> cache for
> > >> the given domain). And just during the WS connection, no more.  
> Taking
> > >> into account that a WS will be *usually* connected after  
> loading a web
> > >> page, such ~100ms in a non-full-realtime protocol is  
> insignificant.
> > >
> > > Wait, are you really saying that 100ms connect latency is  
> unimportant?
> >
> > Open the fastest web page and tell me how long it takes. Probably  
> you
> > have performed a DNS A query. I don't think that a xtra DNS query
> > would be the bottleneck, never.
> 
> On lossy networks such as 3G, they definitely are. A lost UDP  
> packet is
> not retransmitted nor signaled as lost, so the browser has to  
> retry. However,
> once the connection is established to the server, most losses are  
> more or
> less smoothed by TCP extensions such as SACK. So yes, it can take  
> several
> seconds to just resolve a host and then only a few hundreds of ms  
> to retrieve
> the objects. I've observed it.

I think what might be colouring your opinion regarding DNS resolution  
times on mobile is the difference between the first and subsequent  
RTTs.

3G sessions, in a reasonable area, drop to around 100-150ms, although  
they can go up to 300ms or higher if the network condition  
deteriorates. However, the setup of DCH, the radio state normally  
used for internet traffic (and needed for DNS requests and  
responses), takes a healthy number of round-trips, so that the first  
RTT is about three times longer.

Moreover, it's not clear to me that SRV lookup always (or even  
commonly) adds an additional round-trip. Take an XMPP client SRV  
lookup to my own server:

$ dig _xmpp-client._tcp.dave.cridland.net SRV
;; QUESTION SECTION:
;_xmpp-client._tcp.dave.cridland.net. IN	SRV

;; ANSWER SECTION:
_xmpp-client._tcp.dave.cridland.net. 86400 IN SRV 5 2 5222  
peirce.dave.cridland.net.

;; AUTHORITY SECTION:
dave.cridland.net.	86400	IN	NS	br.cridland.net.

;; ADDITIONAL SECTION:
peirce.dave.cridland.net. 86400	IN	A	217.155.137.61
peirce.dave.cridland.net.  
86400	IN	AAAA	2001:470:1f09:882:2e0:81ff:fe29:d16a

Note that the addresses of the actual server are returned in the  
additional section. My understanding is that in practical terms  
this'd always happen for in-zone cases. (If there's a large number,  
you may not get them all, since they can be discarded without error,  
but it practise you're likely to).

Finally, as I've said before, I think that any overhead involved is  
going to be swallowed up in the noise of general session startup in  
the WebSocket case. I do appreciate things are at the very least  
perceived as different in the HTTP case, although I think SRV would  
help solve issues (like off-site failover) there, too, but I think  
the moment you have long-running stateful sessions, you'll end up  
with the same impact to user experience of a few extra RTTs at  
startup as is seen in XMPP, SIP, and so on - that is, none.

100ms extra on a 100ms request/response would be bad, I agree, but  
that's not what we're talking about.

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 w@1wt.eu  Sun Jul 24 03:52:35 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2097C21F8B45; Sun, 24 Jul 2011 03:52:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.05
X-Spam-Level: 
X-Spam-Status: No, score=-5.05 tagged_above=-999 required=5 tests=[AWL=-3.607,  BAYES_00=-2.599, HELO_IS_SMALL6=0.556, J_CHICKENPOX_44=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lDDR7nei-GMv; Sun, 24 Jul 2011 03:52:34 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 0CF0E21F8B44; Sun, 24 Jul 2011 03:52:33 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6OAqNVe026145; Sun, 24 Jul 2011 12:52:23 +0200
Date: Sun, 24 Jul 2011 12:52:23 +0200
From: Willy Tarreau <w@1wt.eu>
To: Dave Cridland <dave@cridland.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110724105223.GL22405@1wt.eu>
References: <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <CALiegf=4K2oWfmZjGMD7J_jyaDtS3i+Mu7R0Wh75Rr+MrQCjtw@mail.gmail.com> <20110722054345.GE18126@1wt.eu> <9031.1311500145.687172@puncture>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <9031.1311500145.687172@puncture>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Sun, 24 Jul 2011 14:50:43 -0700
Cc: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2011 10:52:35 -0000

[ should we leave ietf@ietf.org in CC or not ? I'm suspecting that people
  who read this address will quickly get bored by hybi traffic ]

On Sun, Jul 24, 2011 at 10:35:45AM +0100, Dave Cridland wrote:
> You're saying that you have a nebulous connection thing, that you  
> pump HTTP requests down, and you may want to use that for WebSocket  
> upgrade requests as well, by taking the ws URI and performing a  
> simple transformation on it into an HTTP URI to make the upgrade  
> request on.
> 
> So, given ws://example.com/foo/bar, you'll make the upgrade request  
> on http://example.com/foo/bar

No I'm not saying that because I don't understand what you mean here.
What I'm saying is that browsers try to reuse existing connections to
host:port. So if you want to connect to ws://example.com/foo/bar and
the browser already has a connection to example.com:80 because of a
previous HTTP request to that host, it's much advantageous for it to
reuse that existing connection.

Making an additional DNS request and a connection come with a cost.
In mobile environments, it's not uncommon to see 300-500 ms RTT. This
means that performing the additional DNS request could cost up to one
extra second.

> What Iñaki and I are arguing for is that for WS, there is simply one  
> additional step prior to finding a suitable connection, which is  
> performing an SRV lookup/selection.

That's clearly what I understood.

> And this new step can actually be performed before any of the HTTP  
> connection steps. So, roughly, in order to "do" WebSocket for  
> ws://example.com/foo/bar you would first do SRV lookup, which would  
> give you an equivalent HTTP URI to perform the upgrade request. So  
> for example, if you got:
> 
> _ws._tcp.example.com SRV 1 0 ws.example.com
> 
> You'd make the upgrade request on the HTTP URI of:
> 
> http://ws.example.com/foo/bar
> 
> Of course, if this failed to connect, you can find another HTTP URI  
> to try - something you cannot do without SRV.

If the connection fails here, HTTP will fail too, and right now, people
don't use SRV records with HTTP. I'm not judging whether it's good or
bad, I'm just saying what I'm seeing. Instead, people are using load
balancers, BGP and DNS mechanisms to ensure their site is available.

So whatever principle they're currently using with HTTP will also
provide the same mechanism for free to WS.

Yes it could be nice to have SRV on both HTTP and WS, but we need to
make it adopted for HTTP first. And if it's not adopted at all in the
case of HTTP, probably that is because it's not perceived as bringing
a lot of benefit *for that specific usage*. Instead it may even add
one DNS round trip which clearly is not desirable with highly interactive
protocols such as HTTP.

Also, the notion of "failure to connect" is hard to qualify in interactive
environments. If my browser tries to connect and waits more than a few
seconds before retrying on another server, I will probably already have
pressed the Esc key. We all do that when clicking links on Google search
results : if you don't get a result in one second, you click another one.
It is not reasonable to use even lower timeouts when using SRV records,
because it happens quite often to lose packets on the net, and sometimes
it's the client side which is slow. If the browser decides to fail within
one second and try another host, it will experience very frequent
difficulties.

Client-based failover (what SRV or MX are) is nice with protocols that
can wait long enough to ensure the server is dead. Some mailers try to
connect for one minute or even more. At that point, the client is
certain that the server is dead. In a browser, nobody waits that long,
so giving such a verdict is quite hard.

Still, I think that SRV might be used for site failover, it will be a
lot cleaner than using very short TTLs as some are doing. Such a usage
is compatible with deployed infrastructures, because nothing prevents
a client from prefering an SRV record over a CNAME record.

Now with that in mind, I don't see how one could suggest a MUST for this.
MUST that don't directly come from absolute requirements are never 100%
respected and cause much more trouble than SHOULD which are recommended
for optimal usage. If we say SHOULD, sites will ensure they have a working
DNS config which always announces valid addresses in A/AAAA or CNAME and
that SRV is used for failover. If we say MUST, sites won't bother emitting
correct addresses in A/AAAA or CNAME, or will even announce different ones,
and we'll get a lot of trouble at many places where the wrong record will
be picked by proxies or by clients which can't use SRV for whatever
reason.

Regards,
Willy


From w@1wt.eu  Sun Jul 24 04:02:55 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62B1421F8997; Sun, 24 Jul 2011 04:02:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.272
X-Spam-Level: 
X-Spam-Status: No, score=-5.272 tagged_above=-999 required=5 tests=[AWL=-3.229, BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zNXtfOoiupMe; Sun, 24 Jul 2011 04:02:55 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 927B521F887C; Sun, 24 Jul 2011 04:02:54 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6OB2mWB026172; Sun, 24 Jul 2011 13:02:48 +0200
Date: Sun, 24 Jul 2011 13:02:48 +0200
From: Willy Tarreau <w@1wt.eu>
To: Mark Andrews <marka@isc.org>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110724110248.GN22405@1wt.eu>
References: <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com> <20110724073323.EEAAF121E985@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110724073323.EEAAF121E985@drugs.dv.isc.org>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Sun, 24 Jul 2011 14:50:43 -0700
Cc: "Roy T. Fielding" <fielding@gbiv.com>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2011 11:02:55 -0000

Hi Mark,

On Sun, Jul 24, 2011 at 05:33:23PM +1000, Mark Andrews wrote:
> 
> In message <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com>, "Roy T. Fielding" writes:
> > On Jul 21, 2011, at 10:52 AM, I=F1aki Baz Castillo wrote:
> > 
> > > 2011/7/21 Dave Cridland <dave@cridland.net>:
> > >> It's proven impossible, despite effort, to retrofit SRV onto HTTP; there=
> >  is
> > >> no way it'll be possible to retrofit onto WS.
> > > =
> > 
> > > Right. If WS borns with no SRV (as a MUST for WS clients) then just
> > > forget it and let inherit all the ugly limitations from HTTP protocol.
> > 
> > I am tired of this.  SRV is not used for HTTP because SRV adds latency
> > to the initial request for no useful purpose whatsoever.
> 
> How do you solve the problem of hosting just "http://example.com/"
> on "s1.joes-web-service.com" and not redirect everything else at
> example.com?  People have been complaining about this for about as
> long as the web has existed.

I would say that people complaining about this are doing the wrong thing
first. We've been using www.domain.tld, ftp.domain.tld, mail.domain.tld,
ns.domain.tld for ages, each indicating the service in their host name,
and suddenly just because www.domain.tld appears in the browser's address
bar, it should be shortened to show only "domain.tld". If people are doing
this, they must assume their choices. Sure, SRV would make that easier for
them, but it's not as if no solution had existed before.

Regards,
Willy


From w@1wt.eu  Sun Jul 24 05:08:01 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8444C21F86C3; Sun, 24 Jul 2011 05:08:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.753
X-Spam-Level: 
X-Spam-Status: No, score=-4.753 tagged_above=-999 required=5 tests=[AWL=-3.610, BAYES_00=-2.599, HELO_IS_SMALL6=0.556, J_CHICKENPOX_24=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kcivGLGb3TQj; Sun, 24 Jul 2011 05:08:01 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 7769121F8663; Sun, 24 Jul 2011 05:08:00 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6OC7pGO026319; Sun, 24 Jul 2011 14:07:51 +0200
Date: Sun, 24 Jul 2011 14:07:51 +0200
From: Willy Tarreau <w@1wt.eu>
To: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110724120751.GQ22405@1wt.eu>
References: <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <CALiegf=4K2oWfmZjGMD7J_jyaDtS3i+Mu7R0Wh75Rr+MrQCjtw@mail.gmail.com> <20110722054345.GE18126@1wt.eu> <CALiegfnYm6g63JDHLiSH__r-or3kzK0XCVa3cC7RMP14KWBOSg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CALiegfnYm6g63JDHLiSH__r-or3kzK0XCVa3cC7RMP14KWBOSg@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Sun, 24 Jul 2011 14:50:43 -0700
Cc: Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2011 12:08:01 -0000

On Sun, Jul 24, 2011 at 01:26:53PM +0200, Iñaki Baz Castillo wrote:
> 2011/7/22 Willy Tarreau <w@1wt.eu>:
> > Iñaki, what we're saying is that the resolving applies first to HTTP
> > well before it is WS. For instance, a client could connect to an HTTP
> > server, fetch a few objects, then decide to upgrade the connection to
> > switch to WebSocket. DNS resolving for WS would not even be involved
> > here.
> 
> Hi. Maybe I'm the only who assumes that, usually, the WS server is not
> colocated within the initial web server.

Web-based infrastructures make that almost mandatory at the frontend,
especially in massive hosting where you don't want to multiply IP addresses.
In general you have one single point which handles the IP:port and which
dispatches that to many servers based on the Host header, URI, file names,
cookies, etc...

> This is, your text below is valid just in the case I browse a web page
> in http://some-domain.org (so port 80) and retrieve a WS URI to
> connect to ws://some-domain.org (so also port 80). In that case you
> say that the http/ws client would decide to upgrade the connection so
> "it must assume that the WS handshake must be sent to the same IP:port
> resolved for the HTTP communication".
> 
> I don't agree with yout point. Doing the "upgrade" does not mean
> reusing an existing TCP connection (in which HTTP took place) for
> other purpose.

Huh ?

> Instead, doing the WS upgrade means opening (or
> reusing) a TCP connection, sending a HTTP GET with special semantics,
> expect 101 and then start a bidirectional frame-based communication.

I still remember how the handshake works, thank you.

> So sending the GET with "upgrade" has nothing to do with any previous
> HTTP communication with the HTTP server.

Yes it has. Either you open a fresh new connection, or you reuse an
idle existing one. But to know that the connection is idle, you must
understand the protocol that was spoken on it and this protocol must
have clearly delimited messages. HTTP supports reuse of connections
(also called "keep-alive") and since the WS handshake is HTTP, it is
possible and I'd add even recommended to reuse an existing connection
to send a WS handshake, if one such connection exists.

> > I agree with what others have been saying : if/when a different handshake
> > is supported, eg. on a specific port without the HTTP upgrade, then it
> > will make sense.
> 
> Do you mean WS as a complete separate protocol running on a specific
> WS port and so? I'd really would like it (rather than the exotic
> pseudo-HTTP mechanism used right now), but I expect it will never
> happen.

I'm sure it will happen. We need applications to be developped using
WS first. But there are places where :
  - HTTP compatibility won't be needed
  - masking will be annoying
  - HTTP overhead will be too much
  - HTTP round trip will be too much

I think that this will happen as soon as a working proposal for TLS NPN
appears, because the same requirements will exist (eg: how to specify
the resource name in a simpler way, etc...). Right now we need WS to be
able to replace long polling mechanisms which already work over HTTP, so
if we want it to be adopted, we need to deploy where previous methods
used to work. You just need to be patient :-)

> > But as of now we're relying on the lower layer. As Greg
> > said it, without a deep change in HTTP you won't be able to make the rule
> > a MUST for WS. However, John's suggest of using a SHOULD when the record
> > exists and the client can see it looks fine. What's the problem if not all
> > of your clients go to the same hosts ? You can even announce all of your
> > servers with A/AAAA and with SRV as well as long as they're running on the
> > same ports. Those who can use SRV just have more information than the other
> > ones and can be served better.
> 
> Having multiple A/AAAA records for a single domain does not provide
> failover (as clients usually take just the first IP). I see your
> point, but I expect no success at all.

That's not what I'm saying. Right now, people are using A/AAAA with short
TTLs and are updating the zones when a site fails (when I mean a site, I
mean a datacenter). This is something which happens rarely enough to be
acceptable. Using fast DNS updates for server failover does not work
because caches are everywhere and experience shows that even after one
month you still receive traffic on a server you've stopped announcing.

However, please read what I've explained in another mail about the
limitations of client-based failover in web environments.

Regards,
Willy


From w@1wt.eu  Sun Jul 24 05:11:53 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEDC621F8779; Sun, 24 Jul 2011 05:11:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.678
X-Spam-Level: 
X-Spam-Status: No, score=-4.678 tagged_above=-999 required=5 tests=[AWL=-3.535, BAYES_00=-2.599, HELO_IS_SMALL6=0.556, J_CHICKENPOX_44=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZgKEp0taDVo3; Sun, 24 Jul 2011 05:11:53 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id E7D3121F8640; Sun, 24 Jul 2011 05:11:52 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6OCBlFo026330; Sun, 24 Jul 2011 14:11:47 +0200
Date: Sun, 24 Jul 2011 14:11:47 +0200
From: Willy Tarreau <w@1wt.eu>
To: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110724121147.GR22405@1wt.eu>
References: <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <CALiegf=4K2oWfmZjGMD7J_jyaDtS3i+Mu7R0Wh75Rr+MrQCjtw@mail.gmail.com> <20110722054345.GE18126@1wt.eu> <9031.1311500145.687172@puncture> <20110724105223.GL22405@1wt.eu> <CALiegfkTVg2=k4d8rxmpqXmaRUihRmhtgfF4QRUTAKic7gBk5w@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CALiegfkTVg2=k4d8rxmpqXmaRUihRmhtgfF4QRUTAKic7gBk5w@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Sun, 24 Jul 2011 14:50:43 -0700
Cc: Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2011 12:11:54 -0000

On Sun, Jul 24, 2011 at 01:47:36PM +0200, Iñaki Baz Castillo wrote:
> 2011/7/24 Willy Tarreau <w@1wt.eu>:
> > No I'm not saying that because I don't understand what you mean here.
> > What I'm saying is that browsers try to reuse existing connections to
> > host:port. So if you want to connect to ws://example.com/foo/bar and
> > the browser already has a connection to example.com:80 because of a
> > previous HTTP request to that host, it's much advantageous for it to
> > reuse that existing connection.
> >
> > Making an additional DNS request and a connection come with a cost.
> 
> http://tools.ietf.org/html/draft-ibc-websocket-dns-srv-02#section-5.2

You still need the DNS request : the client does an A/AAAA request for
the HTTP host, then if you ask it to use an SRV record for the WS connection,
it must perform that request too, even if it's to conclude that it can reuse
the idle connection.

Regards,
Willy


From w@1wt.eu  Sun Jul 24 05:16:29 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC87C21F850E; Sun, 24 Jul 2011 05:16:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.906
X-Spam-Level: 
X-Spam-Status: No, score=-4.906 tagged_above=-999 required=5 tests=[AWL=-3.163, BAYES_00=-2.599, HELO_IS_SMALL6=0.556, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 440A3kq8zflg; Sun, 24 Jul 2011 05:16:29 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 3060F21F8509; Sun, 24 Jul 2011 05:16:29 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6OCGMb8026350; Sun, 24 Jul 2011 14:16:22 +0200
Date: Sun, 24 Jul 2011 14:16:22 +0200
From: Willy Tarreau <w@1wt.eu>
To: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110724121622.GS22405@1wt.eu>
References: <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com> <CALiegfkshhJVUHzTD1Kka5+RjGwZ5CS2J=Qk92jfSBg6Z0VfOQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CALiegfkshhJVUHzTD1Kka5+RjGwZ5CS2J=Qk92jfSBg6Z0VfOQ@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Sun, 24 Jul 2011 14:50:43 -0700
Cc: "Roy T. Fielding" <fielding@gbiv.com>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2011 12:16:30 -0000

On Sun, Jul 24, 2011 at 01:42:26PM +0200, Iñaki Baz Castillo wrote:
> 2011/7/23 Roy T. Fielding <fielding@gbiv.com>:
> >> Right. If WS borns with no SRV (as a MUST for WS clients) then just
> >> forget it and let inherit all the ugly limitations from HTTP protocol.
> >
> > I am tired of this.  SRV is not used for HTTP because SRV adds latency
> > to the initial request for no useful purpose whatsoever.
> 
> And I'm really tired of hearing the argument of the "latency" which
> nobody demostrates (but just talks about it without replying me how
> the same is not a problem in realtime protocols like SIP and XMPP).

Because you have never worked in a mobile phone environment. You'd be
amazed to see what end users are paying for ! Count 300-500 ms on average
for a DNS request.

> > In contrast, HTTP is deployed in an anarchic
> > manner in which there are often several HTTP servers per machine
> > (e.g., tests, staging, production, CUPS, etc,).
> 
> Could you explain me why DNS A is good but DNS SRV is bad in such
> "anarchic" deployments?

DNS is not mandatory for HTTP. It's not "DNS A" which makes it good, but
"no mandatory DNS". This is a huge difference.

Regards,
Willy


From jat@google.com  Sun Jul 24 07:14:15 2011
Return-Path: <jat@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 769D821F8A57 for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 07:14:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.805
X-Spam-Level: 
X-Spam-Status: No, score=-105.805 tagged_above=-999 required=5 tests=[AWL=-0.129, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 XI0k+tByZpjT for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 07:14:15 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id E9EEF21F8557 for <ietf@ietf.org>; Sun, 24 Jul 2011 07:14:14 -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 p6OEEDVl001604 for <ietf@ietf.org>; Sun, 24 Jul 2011 07:14:13 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1311516854; bh=aYVuy2IhGD7wBoGitm+MRXyoZEI=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=n8LqPO2Mu82cNRnfWlXBxVkXrYY5UuUel/fEeTuqcjXtoT4J04JKvXeJljeVsgcA8 BYFQpx5JUoh/Ai2vuYNRw==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type:x-system-of-record; b=c1cUakMRwHxzL1Xxg1heypvr11xVySot5d5NChp9XzW9zpMjmbq6Tu18YI3fLmkC3 IJ/MQdzOKKvKmu+ICamrA==
Received: from gxk23 (gxk23.prod.google.com [10.202.11.23]) by kpbe17.cbf.corp.google.com with ESMTP id p6OEEBej031097 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Sun, 24 Jul 2011 07:14:12 -0700
Received: by gxk23 with SMTP id 23so1864002gxk.28 for <ietf@ietf.org>; Sun, 24 Jul 2011 07:14:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=KIS+Kxe+KPw4OiUjh+QyHlNN7qHwItBr2IKiZw+MGYk=; b=dFESmfm0/xLkEcpduM6+uhFq7wfOQBhH3roMwP2j9AHqpsjh1hqAgNvSGj+FntpmlI I3szMMtAhDr7/09qRt1Q==
Received: by 10.150.74.7 with SMTP id w7mr3400053yba.116.1311516851511; Sun, 24 Jul 2011 07:14:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.49.7 with HTTP; Sun, 24 Jul 2011 07:13:50 -0700 (PDT)
In-Reply-To: <CALiegfnwNyYDy=SyrqHJXV0ZreADb7F8QySvgdHofW9Hm9miZQ@mail.gmail.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <9031.1311286867.939466@puncture> <4E28BA9D.6010501@callenish.com> <CAP992=GedTEfimykCWwdwm=BsZdwFRJO36EO0a_o7iejURJ+tQ@mail.gmail.com> <CALiegfnwNyYDy=SyrqHJXV0ZreADb7F8QySvgdHofW9Hm9miZQ@mail.gmail.com>
From: John Tamplin <jat@google.com>
Date: Sun, 24 Jul 2011 10:13:50 -0400
Message-ID: <CABLsOLCgxDNDs54GUybBzmG8a6rNPzXzFcwf_OU25j5L+AobaQ@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
To: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Content-Type: multipart/alternative; boundary=000e0cd5c4be0d216204a8d150a3
X-System-Of-Record: true
X-Mailman-Approved-At: Sun, 24 Jul 2011 14:50:43 -0700
Cc: Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>, David Endicott <dendicott@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2011 14:14:15 -0000

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

On Sun, Jul 24, 2011 at 7:11 AM, I=C3=B1aki Baz Castillo <ibc@aliax.net> wr=
ote:

> 2011/7/22 David Endicott <dendicott@gmail.com>:
> > The technological advantages are worthy, when it's used, but when it
> doesn't
> > come into play, there are added inefficiencies.
>
> ~100 ms (if the DNS server is not local and there is no DNS cache for
> the given domain). And just during the WS connection, no more. Taking
> into account that a WS will be *usually* connected after loading a web
> page, such ~100ms in a non-full-realtime protocol is insignificant.


Wait, are you really saying that 100ms connect latency is unimportant?

--=20
John A. Tamplin
Software Engineer (GWT), Google

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

<div class=3D"gmail_quote">On Sun, Jul 24, 2011 at 7:11 AM, I=C3=B1aki Baz =
Castillo <span dir=3D"ltr">&lt;<a href=3D"mailto:ibc@aliax.net">ibc@aliax.n=
et</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

2011/7/22 David Endicott &lt;<a href=3D"mailto:dendicott@gmail.com">dendico=
tt@gmail.com</a>&gt;:<br>
<div class=3D"im">&gt; The technological advantages are worthy, when it&#39=
;s used, but when it doesn&#39;t<br>
&gt; come into play, there are added inefficiencies.<br>
<br>
</div>~100 ms (if the DNS server is not local and there is no DNS cache for=
<br>
the given domain). And just during the WS connection, no more. Taking<br>
into account that a WS will be *usually* connected after loading a web<br>
page, such ~100ms in a non-full-realtime protocol is insignificant.</blockq=
uote><div><br></div><div>Wait, are you really saying that 100ms connect lat=
ency is unimportant?</div></div><br>-- <br>John A. Tamplin<br>Software Engi=
neer (GWT), Google<br>



--000e0cd5c4be0d216204a8d150a3--

From w@1wt.eu  Sun Jul 24 11:33:49 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E02A21F89C1; Sun, 24 Jul 2011 11:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.941
X-Spam-Level: 
X-Spam-Status: No, score=-4.941 tagged_above=-999 required=5 tests=[AWL=-3.198, BAYES_00=-2.599, HELO_IS_SMALL6=0.556, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DOLzd0tJo1M6; Sun, 24 Jul 2011 11:33:48 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 1410C21F889A; Sun, 24 Jul 2011 11:33:47 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6OIXh7n027121; Sun, 24 Jul 2011 20:33:43 +0200
Date: Sun, 24 Jul 2011 20:33:43 +0200
From: Willy Tarreau <w@1wt.eu>
To: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110724183343.GY22405@1wt.eu>
References: <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <CALiegf=4K2oWfmZjGMD7J_jyaDtS3i+Mu7R0Wh75Rr+MrQCjtw@mail.gmail.com> <20110722054345.GE18126@1wt.eu> <9031.1311500145.687172@puncture> <20110724105223.GL22405@1wt.eu> <CALiegfkTVg2=k4d8rxmpqXmaRUihRmhtgfF4QRUTAKic7gBk5w@mail.gmail.com> <20110724121147.GR22405@1wt.eu> <CALiegf=GDDKdXOXgz3oognh6=qRDKFUSrRfLOtOoUucAxr4p3w@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CALiegf=GDDKdXOXgz3oognh6=qRDKFUSrRfLOtOoUucAxr4p3w@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Sun, 24 Jul 2011 14:50:43 -0700
Cc: Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2011 18:33:49 -0000

On Sun, Jul 24, 2011 at 08:25:05PM +0200, Iñaki Baz Castillo wrote:
> 2011/7/24 Willy Tarreau <w@1wt.eu>:
> >> > Making an additional DNS request and a connection come with a cost.
> >>
> >> http://tools.ietf.org/html/draft-ibc-websocket-dns-srv-02#section-5.2
> >
> > You still need the DNS request : the client does an A/AAAA request for
> > the HTTP host, then if you ask it to use an SRV record for the WS connection,
> > it must perform that request too, even if it's to conclude that it can reuse
> > the idle connection.
> 
> Ok, but I don't consider a xtra DNS query to be so hard.

I had to perform sites analysis for a customer a few months ago. Many
web pages nowadays have between 100 and 200 objects to fetch, spread
over up to 25-30 host names. If you take even only 100ms for each of
them, you're at 3 additional seconds to display the page. Granted those
requests are not WS and only HTTP, but as I said, SRV for WS won't work
before it works with HTTP, at least due to proxies.

But those 3 extra seconds will always be considered a good reason not
to make SRV mandatory for HTTP. The web is degrading very quickly due
to poor practices, and we should be careful not to suggest to make it
even worse.

Regards,
Willy


From w@1wt.eu  Sun Jul 24 11:45:45 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E01621F889A; Sun, 24 Jul 2011 11:45:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.283
X-Spam-Level: 
X-Spam-Status: No, score=-4.283 tagged_above=-999 required=5 tests=[AWL=-3.740, BAYES_00=-2.599, HELO_IS_SMALL6=0.556, J_CHICKENPOX_24=0.6, J_CHICKENPOX_64=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hc8-X9yYUZQc; Sun, 24 Jul 2011 11:45:45 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 6BE3F21F887C; Sun, 24 Jul 2011 11:45:44 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6OIjbqt027155; Sun, 24 Jul 2011 20:45:37 +0200
Date: Sun, 24 Jul 2011 20:45:37 +0200
From: Willy Tarreau <w@1wt.eu>
To: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110724184537.GZ22405@1wt.eu>
References: <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <CALiegf=4K2oWfmZjGMD7J_jyaDtS3i+Mu7R0Wh75Rr+MrQCjtw@mail.gmail.com> <20110722054345.GE18126@1wt.eu> <CALiegfnYm6g63JDHLiSH__r-or3kzK0XCVa3cC7RMP14KWBOSg@mail.gmail.com> <20110724120751.GQ22405@1wt.eu> <CALiegfncavmoMp4YDCeeJ3rsOfHAYQ99itKX2Q2eHB351T3X5A@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CALiegfncavmoMp4YDCeeJ3rsOfHAYQ99itKX2Q2eHB351T3X5A@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Sun, 24 Jul 2011 14:50:43 -0700
Cc: Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2011 18:45:45 -0000

On Sun, Jul 24, 2011 at 08:24:25PM +0200, Iñaki Baz Castillo wrote:
> > Yes it has. Either you open a fresh new connection, or you reuse an
> > idle existing one.
> 
> If the WS URI points to a different server, it's perfectly possible
> that the WS connection has nothing to do (neither cookies usage) with
> the previous HTTP/HTML traffic. I just meant it.

I agree, and there will certainly be a large number of cases where it
will be different. But that's not enough (in my opinion) to make something
mandatory considering the negative side effects.

> > But to know that the connection is idle, you must
> > understand the protocol that was spoken on it and this protocol must
> > have clearly delimited messages. HTTP supports reuse of connections
> > (also called "keep-alive") and since the WS handshake is HTTP, it is
> > possible and I'd add even recommended to reuse an existing connection
> > to send a WS handshake, if one such connection exists.
> 
> Don't take me wrong, but "keep-alive" mechanism in HTTP is just a hack
> since paralelism is not possible (well, it's but with too many
> constrains, for example the server must send the replies in order).

Pipelining improves things a lot, especially for static objects which
immediately fill the pipe.

> In
> other protocols working on top of TCP (as SIP) each request contains
> an id (in the case of SIP the Via branch) which allows identifying
> which request a response belongs to, so I can send N requests via the
> same TCP connection and receive the responses in any order.

>From what I've read, SPDY typically addresses this point.

> HTTP is poor on this topic, and I wouldn't like WS to inherit it.

But it will since there is no MUX support yet, WS frames will be delivered
in order. The application on top of WS might decide to number each message
though and use its own out-of-order mechanism though.

> >> Do you mean WS as a complete separate protocol running on a specific
> >> WS port and so? I'd really would like it (rather than the exotic
> >> pseudo-HTTP mechanism used right now), but I expect it will never
> >> happen.
> >
> > I'm sure it will happen. We need applications to be developped using
> > WS first. But there are places where :
> >  - HTTP compatibility won't be needed
> >  - masking will be annoying
> >  - HTTP overhead will be too much
> >  - HTTP round trip will be too much
> >
> > I think that this will happen as soon as a working proposal for TLS NPN
> > appears, because the same requirements will exist (eg: how to specify
> > the resource name in a simpler way, etc...). Right now we need WS to be
> > able to replace long polling mechanisms which already work over HTTP, so
> > if we want it to be adopted, we need to deploy where previous methods
> > used to work. You just need to be patient :-)
> 
> ok, I like what you say :)
> However, imagine that in next 2 years there are a lot of WS servers
> speaking HTTP (for the WS handshake, of course). If you suggest that a
> different WS protocol could appear, it would require a new URI schema
> so the client knows wheter to perform a HTTP WS handshake or use the
> new WS protocol.

That's just a minor detail. Likewise it will probably have to support a
fallback to the HTTP handshake because there will be a lot of places where
it will not pass through.

> >> Having multiple A/AAAA records for a single domain does not provide
> >> failover (as clients usually take just the first IP). I see your
> >> point, but I expect no success at all.
> >
> > That's not what I'm saying. Right now, people are using A/AAAA with short
> > TTLs and are updating the zones when a site fails (when I mean a site, I
> > mean a datacenter). This is something which happens rarely enough to be
> > acceptable. Using fast DNS updates for server failover does not work
> > because caches are everywhere and experience shows that even after one
> > month you still receive traffic on a server you've stopped announcing.
> 
> And there is where DNS SRV could help a lot :)

Not that much, because as soon as you fail your DC, you'll stop announcing
it so that visitors don't try to connect there for seconds before they
detect it's down.

> > However, please read what I've explained in another mail about the
> > limitations of client-based failover in web environments.
> 
> Yes, I've read it. But I expect it's even more critical in a phone
> call (my SIP phone performs SRV/A, gets the first IP:port and sends
> the call request there using UDP, but the server is down, so after
> some seconds *without hearing ringing* the phone sends the call to
> another server). If it's not critical in SIP, why should it be so
> critical in WS?

As I said, having it in WS means having it in HTTP too. And having a
browser rely on TCP connection timeouts to decide to use a server vs
another one would make a lot of sites unusable. I've already been used
to mark some advertiser's sites as 255.255.255.255 in my /etc/hosts to
stop waiting for their crap to respond on pages that I'm used to visit.
If a page loads objects from s1,s2,s3,s4.domain.tld and all are hosted
both on a valid and a dead DC, it can take a lot of time before all these
hosts are marked down and ignored. Nobody I know would wait for these to
fail.

> Also, if the user realizes that the connection takes too much time and
> presses F5 to reload the page, why couldn't the webbrowser cache the
> SRV results and mark the previous attemp as failed so next server:port
> woul be tryed when the user presses F5?

Yes but once again, if you have to wait one minute on each new site so
that all dead servers can be ignored, the web will look like a terrible
experience to you.

Regards,
Willy


From w@1wt.eu  Sun Jul 24 11:57:17 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC8D121F8892; Sun, 24 Jul 2011 11:57:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.816
X-Spam-Level: 
X-Spam-Status: No, score=-4.816 tagged_above=-999 required=5 tests=[AWL=-3.073, BAYES_00=-2.599, HELO_IS_SMALL6=0.556, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fMM7rARXSYLa; Sun, 24 Jul 2011 11:57:17 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 19ED721F87C5; Sun, 24 Jul 2011 11:57:13 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6OIv6Hn027193; Sun, 24 Jul 2011 20:57:06 +0200
Date: Sun, 24 Jul 2011 20:57:06 +0200
From: Willy Tarreau <w@1wt.eu>
To: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110724185706.GA22405@1wt.eu>
References: <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com> <CALiegfkshhJVUHzTD1Kka5+RjGwZ5CS2J=Qk92jfSBg6Z0VfOQ@mail.gmail.com> <20110724121622.GS22405@1wt.eu> <CALiegfkzaMOHBz0-Sgj7HWtQX1jadczDu6t=5PoiNPMG69ZyVg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CALiegfkzaMOHBz0-Sgj7HWtQX1jadczDu6t=5PoiNPMG69ZyVg@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Sun, 24 Jul 2011 14:50:43 -0700
Cc: "Roy T. Fielding" <fielding@gbiv.com>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2011 18:57:17 -0000

On Sun, Jul 24, 2011 at 08:28:49PM +0200, Iñaki Baz Castillo wrote:
> 2011/7/24 Willy Tarreau <w@1wt.eu>:
> >> And I'm really tired of hearing the argument of the "latency" which
> >> nobody demostrates (but just talks about it without replying me how
> >> the same is not a problem in realtime protocols like SIP and XMPP).
> >
> > Because you have never worked in a mobile phone environment. You'd be
> > amazed to see what end users are paying for ! Count 300-500 ms on average
> > for a DNS request.
> 
> Well, mobile phone world is a pain due to GPRS/3G internet
> connections. But those networks should be improved rather than
> assuming that all the Internet must change to work on those infernal
> environments (which IMHO are not yet ready for modern internet). All I
> see in mobile networks are workarounds.

Those are infernal but part of the time cannot be compressed much more
due to the fact that you have to share the medium with many other people
and you have to wait for your slot to send packets. And I'm not even
counting the time it can take to forward your data across the country
between the antenna and the datacenter. Sure things will improve, but
I don't expect seeing anything below 40-50ms.

> >> Could you explain me why DNS A is good but DNS SRV is bad in such
> >> "anarchic" deployments?
> >
> > DNS is not mandatory for HTTP. It's not "DNS A" which makes it good, but
> > "no mandatory DNS". This is a huge difference.
> 
> So, do you mean using URI's with IP rather than domain? (take into
> account that TLS connection require the certificate to match the URI
> domain, but anyhow it's also possible to use IP's within the
> certificate).

On internal networks, using IP instead of URIs is not uncommon at all,
especially on developer networks where you need many instances of the
same server in different versions or for different people. Some static
servers also make use of this because it saves one roundtrip. And of
course you have it on your ADSL router's web-based configuration interface
otherwise you wouldn't be able to contact the DNS to reach the router :-)

But that's not what I meant, I meant that DNS is not the only solution
to resolve host names. WINS, NIS and /etc/hosts are usable too. When I
was a student in 94, we had all our passwords and hostnames in NIS and
no DNS was configured. It worked like a charm. DNS is not something
mandatory at all for many protocols. It just happens to be the standard
over the public Internet.

Regards,
Willy


From w@1wt.eu  Sun Jul 24 11:59:55 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B2E121F889D; Sun, 24 Jul 2011 11:59:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.762
X-Spam-Level: 
X-Spam-Status: No, score=-4.762 tagged_above=-999 required=5 tests=[AWL=-3.019, BAYES_00=-2.599, HELO_IS_SMALL6=0.556, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QQ83MbCzw1cx; Sun, 24 Jul 2011 11:59:55 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 7F8C021F87C5; Sun, 24 Jul 2011 11:59:53 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6OIxnQR027207; Sun, 24 Jul 2011 20:59:49 +0200
Date: Sun, 24 Jul 2011 20:59:49 +0200
From: Willy Tarreau <w@1wt.eu>
To: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110724185949.GB22405@1wt.eu>
References: <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <9031.1311286867.939466@puncture> <4E28BA9D.6010501@callenish.com> <CAP992=GedTEfimykCWwdwm=BsZdwFRJO36EO0a_o7iejURJ+tQ@mail.gmail.com> <CALiegfnwNyYDy=SyrqHJXV0ZreADb7F8QySvgdHofW9Hm9miZQ@mail.gmail.com> <CABLsOLCgxDNDs54GUybBzmG8a6rNPzXzFcwf_OU25j5L+AobaQ@mail.gmail.com> <CALiegfnp+kNqnU-_x2ZBZnN8fzP=4+6WO=QPjw1rJzvZmSXEAg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CALiegfnp+kNqnU-_x2ZBZnN8fzP=4+6WO=QPjw1rJzvZmSXEAg@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Sun, 24 Jul 2011 14:50:43 -0700
Cc: Server-Initiated HTTP <hybi@ietf.org>, John Tamplin <jat@google.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: Sun, 24 Jul 2011 18:59:55 -0000

On Sun, Jul 24, 2011 at 08:30:11PM +0200, Iñaki Baz Castillo wrote:
> 2011/7/24 John Tamplin <jat@google.com>:
> >> ~100 ms (if the DNS server is not local and there is no DNS cache for
> >> the given domain). And just during the WS connection, no more. Taking
> >> into account that a WS will be *usually* connected after loading a web
> >> page, such ~100ms in a non-full-realtime protocol is insignificant.
> >
> > Wait, are you really saying that 100ms connect latency is unimportant?
> 
> Open the fastest web page and tell me how long it takes. Probably you
> have performed a DNS A query. I don't think that a xtra DNS query
> would be the bottleneck, never.

On lossy networks such as 3G, they definitely are. A lost UDP packet is
not retransmitted nor signaled as lost, so the browser has to retry. However,
once the connection is established to the server, most losses are more or
less smoothed by TCP extensions such as SACK. So yes, it can take several
seconds to just resolve a host and then only a few hundreds of ms to retrieve
the objects. I've observed it.

Regards,
Willy


From w@1wt.eu  Sun Jul 24 12:16:51 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 531A721F856B; Sun, 24 Jul 2011 12:16:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.71
X-Spam-Level: 
X-Spam-Status: No, score=-4.71 tagged_above=-999 required=5 tests=[AWL=-2.967,  BAYES_00=-2.599, HELO_IS_SMALL6=0.556, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2EPvKQwdGzMo; Sun, 24 Jul 2011 12:16:50 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 3DCBB21F856A; Sun, 24 Jul 2011 12:16:50 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6OJGfBt027251; Sun, 24 Jul 2011 21:16:41 +0200
Date: Sun, 24 Jul 2011 21:16:41 +0200
From: Willy Tarreau <w@1wt.eu>
To: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110724191641.GC22405@1wt.eu>
References: <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com> <CALiegfkshhJVUHzTD1Kka5+RjGwZ5CS2J=Qk92jfSBg6Z0VfOQ@mail.gmail.com> <C9CD680E-8D68-4380-A76F-70F41F30F877@gbiv.com> <CALiegfkFnKjP09Vijo3c_DFYn4=UZm9M-4mVuZUyBk8rzwmDCw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CALiegfkFnKjP09Vijo3c_DFYn4=UZm9M-4mVuZUyBk8rzwmDCw@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Sun, 24 Jul 2011 14:50:43 -0700
Cc: "Roy T. Fielding" <fielding@gbiv.com>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2011 19:16:51 -0000

On Sun, Jul 24, 2011 at 08:52:32PM +0200, Iñaki Baz Castillo wrote:
> Ok. But I don't see the problem. What about Google Apps? My own domain
> uses Gtalk and Gmail by setting Google XMPP SRV and MX records. Now
> imagine that I would host my personal webpage (domain "www.aliax.net")
> in Google, wouldn't be great a SRV entry for HTTP
> (_http._tcp.aliax.net has SRV record 10 0 80
> web-server-01.google.com)? or do we prefer the ugly HTTP 30X
> redirection or ugly CNAME?

Well, you gave the perfect example : here, CNAME is the exact equivalent
of SRV. None is cheaper nor better than the other. You just find it ugly
because it's called CNAME.

> In my opinion SRV is not possible for HTTP since SRV appeared too
> late. That's the main and enough reason IMHO.

I'd see it differently : the balance between its extra costs vs the
expected benefits does not push in the direction to massively deploy
it. You know, it only takes 4-5 browsers to enable it and make the
whole web use it. Pat already explained why he doesn't want it.

> The fact that people is "confortable" enough with HTTP style-of-life
> (a specification of 1999) and does not want to deal with "new
> technologies" other than stuff and more stuff on top of HTTP, is not a
> good argument for me.

It's not a matter of new vs old technologies. We're not trying to
paint HTTP in a shiny color to impress friends. We're dealing with
deployed setups and users with high expectations, which are currently
more or less met and for which your proposal doesn't sensibly improve
experience but can sensibly degrade it for many people.

> HTTP is not the layer number 5 in OSI model.

Like it or not, it has inherited this role a long time ago because it
provides many advantages over plain TCP (such as easy reconnection,
authentication, etc...).

Willy


From w@1wt.eu  Sun Jul 24 12:29:54 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B33D21F8A91; Sun, 24 Jul 2011 12:29:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.36
X-Spam-Level: 
X-Spam-Status: No, score=-4.36 tagged_above=-999 required=5 tests=[AWL=-3.217,  BAYES_00=-2.599, HELO_IS_SMALL6=0.556, J_CHICKENPOX_64=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e0lbL5uoOA1A; Sun, 24 Jul 2011 12:29:53 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 7C73221F8891; Sun, 24 Jul 2011 12:29:53 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6OJTm8F027308; Sun, 24 Jul 2011 21:29:48 +0200
Date: Sun, 24 Jul 2011 21:29:48 +0200
From: Willy Tarreau <w@1wt.eu>
To: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110724192948.GD22405@1wt.eu>
References: <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <CALiegf=4K2oWfmZjGMD7J_jyaDtS3i+Mu7R0Wh75Rr+MrQCjtw@mail.gmail.com> <20110722054345.GE18126@1wt.eu> <CALiegfnYm6g63JDHLiSH__r-or3kzK0XCVa3cC7RMP14KWBOSg@mail.gmail.com> <20110724120751.GQ22405@1wt.eu> <CALiegfncavmoMp4YDCeeJ3rsOfHAYQ99itKX2Q2eHB351T3X5A@mail.gmail.com> <20110724184537.GZ22405@1wt.eu> <CALiegfne620wuDMAp235n3mVcXTAnbhhNm8vpiNCy5F7+VD92A@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CALiegfne620wuDMAp235n3mVcXTAnbhhNm8vpiNCy5F7+VD92A@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Sun, 24 Jul 2011 14:50:43 -0700
Cc: Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2011 19:29:54 -0000

On Sun, Jul 24, 2011 at 08:57:45PM +0200, Iñaki Baz Castillo wrote:
> 2011/7/24 Willy Tarreau <w@1wt.eu>:
> >> Also, if the user realizes that the connection takes too much time and
> >> presses F5 to reload the page, why couldn't the webbrowser cache the
> >> SRV results and mark the previous attemp as failed so next server:port
> >> woul be tryed when the user presses F5?
> >
> > Yes but once again, if you have to wait one minute on each new site so
> > that all dead servers can be ignored, the web will look like a terrible
> > experience to you.
> 
> Ok, but what would be the failover solution then? any failover
> solution can take some time until redirects the client's request to a
> working server, it's not just a client problem.

This is already addressed by existing web architectures. DNS provides
geolocation and proposes you the closest working datacenter. BGP ensures
that this datacenter is always reachable via multiple links and multiple
providers. Load balancers on the site ensure that only valid servers are
used. I know some people who configure their load balancers so that a
server is removed from the pool less than 50ms after a failure or slowdown
has been noticed. You will never be able to offer that quality of service
using DNS only, because those 50ms are less than the time it takes for
most visitors to ping the site.

> Anyhow, don't forget that SRV is not just for failover, but also for
> load-balancing (you can state that a more powerful server-01 receives
> 80% of the traffic and server-02 the remaining 20%).

This is already addressed by DNS round robin and used by a lot of sites.
But keep in mind that DNS is used between *sites* and not *servers*. If
you use it for servers, you'll fail because you won't be able to silently
put them in maintenance without disturbing visitors. Load balancers are
used for servers. And between sites, people are not seeking imbalanced
distribution. If they really do, then it's easy using multiple addresses.

Don't take this as an attack (it is not), but you accused Roy of not
knowing SRV, but I think that you're not much experienced with web
infrastructures and that may be why you think that SRV is the *only*
solution to many problems that have been dealt with for ages.

I think your proposal could make sense with SHOULDs instead of MUSTs,
eventhough it's unlikely that it will be used for the latency reasons
that were suggested.

Regards,
Willy


From w@1wt.eu  Sun Jul 24 12:32:39 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54D2E21F8760; Sun, 24 Jul 2011 12:32:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.606
X-Spam-Level: 
X-Spam-Status: No, score=-4.606 tagged_above=-999 required=5 tests=[AWL=-2.863, BAYES_00=-2.599, HELO_IS_SMALL6=0.556, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vxAgN4pht2NX; Sun, 24 Jul 2011 12:32:38 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id E5AF021F873F; Sun, 24 Jul 2011 12:32:37 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6OJWUMh027319; Sun, 24 Jul 2011 21:32:30 +0200
Date: Sun, 24 Jul 2011 21:32:30 +0200
From: Willy Tarreau <w@1wt.eu>
To: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110724193230.GE22405@1wt.eu>
References: <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com> <CALiegfkshhJVUHzTD1Kka5+RjGwZ5CS2J=Qk92jfSBg6Z0VfOQ@mail.gmail.com> <20110724121622.GS22405@1wt.eu> <CALiegfkzaMOHBz0-Sgj7HWtQX1jadczDu6t=5PoiNPMG69ZyVg@mail.gmail.com> <20110724185706.GA22405@1wt.eu> <CALiegf=smDo6CNQE+cA_2__BLr5wqbmr75unDJSMitavD4ySyA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CALiegf=smDo6CNQE+cA_2__BLr5wqbmr75unDJSMitavD4ySyA@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Sun, 24 Jul 2011 14:50:43 -0700
Cc: "Roy T. Fielding" <fielding@gbiv.com>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2011 19:32:39 -0000

On Sun, Jul 24, 2011 at 09:02:59PM +0200, Iñaki Baz Castillo wrote:
> 2011/7/24 Willy Tarreau <w@1wt.eu>:
> > But that's not what I meant, I meant that DNS is not the only solution
> > to resolve host names. WINS, NIS and /etc/hosts are usable too. When I
> > was a student in 94, we had all our passwords and hostnames in NIS and
> > no DNS was configured. It worked like a charm. DNS is not something
> > mandatory at all for many protocols. It just happens to be the standard
> > over the public Internet.
> 
> Ok, I get your point now :)
> But, do current webbrosers resolve names using anything but DNS A?
> (well, I know that they use /etc/hosts). Anyhow, WINS / NIS /etc/hosts
> and such stuff just maps a hostname into a single IP. It's the
> equivalent of a DNS A resource record. Think about locating a mail
> server (MX is required), you need a DNS server.

... or a static entry (the "Smart Relay host" entry you see in on the DS
line in sendmail.cf). That's the case of any mail client in a campus, they
don't use DNS to send outgoing mail. And even within the mail relays and
servers, it's quite common to have a relaydomains file to map domains to
servers.

Willy


From w@1wt.eu  Sun Jul 24 13:42:41 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56C2421F84F2; Sun, 24 Jul 2011 13:42:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.664
X-Spam-Level: 
X-Spam-Status: No, score=-4.664 tagged_above=-999 required=5 tests=[AWL=-2.621, BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YxbgXEJqUtOL; Sun, 24 Jul 2011 13:42:40 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 514AE21F873D; Sun, 24 Jul 2011 13:42:39 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6OKgaQI027480; Sun, 24 Jul 2011 22:42:36 +0200
Date: Sun, 24 Jul 2011 22:42:36 +0200
From: Willy Tarreau <w@1wt.eu>
To: Dave Cridland <dave@cridland.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110724204236.GG22405@1wt.eu>
References: <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <9031.1311286867.939466@puncture> <4E28BA9D.6010501@callenish.com> <CAP992=GedTEfimykCWwdwm=BsZdwFRJO36EO0a_o7iejURJ+tQ@mail.gmail.com> <CALiegfnwNyYDy=SyrqHJXV0ZreADb7F8QySvgdHofW9Hm9miZQ@mail.gmail.com> <CABLsOLCgxDNDs54GUybBzmG8a6rNPzXzFcwf_OU25j5L+AobaQ@mail.gmail.com> <CALiegfnp+kNqnU-_x2ZBZnN8fzP=4+6WO=QPjw1rJzvZmSXEAg@mail.gmail.com> <20110724185949.GB22405@1wt.eu> <9031.1311538720.416128@puncture>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <9031.1311538720.416128@puncture>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Sun, 24 Jul 2011 14:50:43 -0700
Cc: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2011 20:42:41 -0000

On Sun, Jul 24, 2011 at 09:18:40PM +0100, Dave Cridland wrote:
> >> Open the fastest web page and tell me how long it takes. Probably  
> >you
> >> have performed a DNS A query. I don't think that a xtra DNS query
> >> would be the bottleneck, never.
> >
> >On lossy networks such as 3G, they definitely are. A lost UDP  
> >packet is
> >not retransmitted nor signaled as lost, so the browser has to  
> >retry. However,
> >once the connection is established to the server, most losses are  
> >more or
> >less smoothed by TCP extensions such as SACK. So yes, it can take  
> >several
> >seconds to just resolve a host and then only a few hundreds of ms  
> >to retrieve
> >the objects. I've observed it.
> 
> I think what might be colouring your opinion regarding DNS resolution  
> times on mobile is the difference between the first and subsequent  
> RTTs.

Note that in the point above I was not even talking about RTT but
explaining to Iñaki that sometimes DNS can be slower than the rest
of the transfer due to losses and slow retransmits.

> 3G sessions, in a reasonable area, drop to around 100-150ms, although  
> they can go up to 300ms or higher if the network condition  
> deteriorates.

I agree. However it can get a lot worse as soon as you have even just a
little bit of traffic on your link (eg: objects fetched in parallel).

> However, the setup of DCH, the radio state normally  
> used for internet traffic (and needed for DNS requests and  
> responses), takes a healthy number of round-trips, so that the first  
> RTT is about three times longer.

Yes and depending on the equipments vendor, you may even experience
losses during this phase for several seconds. But I was really not
talking about such issues that add to the bad experience and should
not be considered as the norm.

> Moreover, it's not clear to me that SRV lookup always (or even  
> commonly) adds an additional round-trip. Take an XMPP client SRV  
> lookup to my own server:
> 
> $ dig _xmpp-client._tcp.dave.cridland.net SRV
> ;; QUESTION SECTION:
> ;_xmpp-client._tcp.dave.cridland.net. IN	SRV
> 
> ;; ANSWER SECTION:
> _xmpp-client._tcp.dave.cridland.net. 86400 IN SRV 5 2 5222  
> peirce.dave.cridland.net.
> 
> ;; AUTHORITY SECTION:
> dave.cridland.net.	86400	IN	NS	br.cridland.net.
> 
> ;; ADDITIONAL SECTION:
> peirce.dave.cridland.net. 86400	IN	A	217.155.137.61
> peirce.dave.cridland.net.  
> 86400	IN	AAAA	2001:470:1f09:882:2e0:81ff:fe29:d16a
> 
> Note that the addresses of the actual server are returned in the  
> additional section. My understanding is that in practical terms  
> this'd always happen for in-zone cases. (If there's a large number,  
> you may not get them all, since they can be discarded without error,  
> but it practise you're likely to).

That's very interesting. For an unknown reason, doing the same request
from here using either dig or host only retrieves the answer and not
the authority nor the additional sections.

> Finally, as I've said before, I think that any overhead involved is  
> going to be swallowed up in the noise of general session startup in  
> the WebSocket case. I do appreciate things are at the very least  
> perceived as different in the HTTP case, although I think SRV would  
> help solve issues (like off-site failover) there, too, but I think  
> the moment you have long-running stateful sessions, you'll end up  
> with the same impact to user experience of a few extra RTTs at  
> startup as is seen in XMPP, SIP, and so on - that is, none.
>
> 100ms extra on a 100ms request/response would be bad, I agree, but  
> that's not what we're talking about.

To ensure nobody gets me wrong, I'm certain this can help solve issues
*if this is optional*. If it becomes a MUST, then the negative effects
will override the positive ones. In my opinion, the client should decide
whether to enable it or not. If architectures are built with that in
mind, then it will not be an absolute requirement, and migration to SRV
could happen smoothly just like migration to make the Host header mandatory
happened. What is needed is a way to avoid the extra DNS lookup in most
cases where the SRV record is not there. Coupling it with CNAME as I
proposed could be a reasonable solution. Surely other solutions are better.

But we have to keep in mind that for SRV to work, it cannot be made
mandatory because existing infrastructure simply does not support it.
This point alone is enough to kill the mandatory requirement. And once
optional, we have to promote its adoption with a perceived benefit for
the end user with almost zero cost. Mixing all those points with the
use cases of WS leaves little place for SRV, but maybe someone wants
to work on it and identify the *real* benefits then emit a draft.

Regards,
Willy


From mohta@necom830.hpcl.titech.ac.jp  Sun Jul 24 15:13:08 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 1895521F8747 for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 15:13:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.072
X-Spam-Level: 
X-Spam-Status: No, score=-0.072 tagged_above=-999 required=5 tests=[AWL=0.018,  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 13h4evwd2med for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 15:13:07 -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 DA04E21F86F6 for <ietf@ietf.org>; Sun, 24 Jul 2011 15:12:57 -0700 (PDT)
Received: (qmail 75738 invoked from network); 24 Jul 2011 22:32:07 -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; 24 Jul 2011 22:32:07 -0000
Message-ID: <4E2C98A7.3000204@necom830.hpcl.titech.ac.jp>
Date: Mon, 25 Jul 2011 07:11:51 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Hector Santos <hsantos@isdg.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com>	<CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com>	<9031.1311082001.631622@puncture>	<CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com>	<CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com>	<CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com>	<20110721163910.GA16854@1wt.eu>	<CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com>	<9031.1311270000.588511@puncture>	<4E28C035.6020009@necom830.hpcl.titech.ac.jp>	<9031.1311328268.180517@puncture> <4E295249.5060700@necom830.hpcl.titech.ac.jp> <4E2C4A1C.6010605@isdg.net>
In-Reply-To: <4E2C4A1C.6010605@isdg.net>
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: Sun, 24 Jul 2011 22:13:08 -0000

Hector Santos wrote:

> A Major Application will offer all services necessary for the customer 
> to leverage. They are not going to eliminate ftp just because the 
> "developer" likes http better or whats customers to switch to http. Even 
> then, where I have seen a history of people using a http link, I have 
> also seen many changed back, if only to help balance or spread loads.

I'm afraid you are not distinguishing providers of intermediate
infrastructure and competing developers of various software used
on end systems. The differentiations between them are essential
to understand the Internet.

Roy T. Fielding wrote:

> HTTP would not, cannot,
> and never will benefit from SRV even if we had a magic wand that
> could deploy it on all browsers.  SRV simply doesn't fit the Web
> architecture.

SRV is a tool for port based real/virtual hosting, which is why it
has increased its usefulness with IPv4 address exhaustion.

						Masataka Ohta

From stpeter@stpeter.im  Sun Jul 24 15:48: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 5AC9821F86D8 for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 15:48:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7ky+83f8uSwI for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 15:48:10 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id CE46C21F86C3 for <ietf@ietf.org>; Sun, 24 Jul 2011 15:48:10 -0700 (PDT)
Received: from dhcp-13ac.meeting.ietf.org (unknown [130.129.19.172]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 9D1E6411C7 for <ietf@ietf.org>; Sun, 24 Jul 2011 16:49:04 -0600 (MDT)
Message-ID: <4E2CA129.2090609@stpeter.im>
Date: Sun, 24 Jul 2011 18:48:09 -0400
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: APPSAREA session
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2011 22:48:11 -0000

Folks, please note that the APPSAREA session has been rescheduled to
Monday morning at 09:00 (the slot formerly occupied by the HTTP-AUTH BoF).

Peter

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



From mohta@necom830.hpcl.titech.ac.jp  Sun Jul 24 16:49:44 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 7874221F86DC for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 16:49:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.073
X-Spam-Level: 
X-Spam-Status: No, score=-0.073 tagged_above=-999 required=5 tests=[AWL=0.017,  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 BO8FoDXSjOGy for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 16:49:44 -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 A84E621F86C3 for <ietf@ietf.org>; Sun, 24 Jul 2011 16:49:42 -0700 (PDT)
Received: (qmail 76430 invoked from network); 25 Jul 2011 00:08:50 -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 Jul 2011 00:08:50 -0000
Message-ID: <4E2CAF4C.6010504@necom830.hpcl.titech.ac.jp>
Date: Mon, 25 Jul 2011 08:48:28 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <CALiegf=4K2oWfmZjGMD7J_jyaDtS3i+Mu7R0Wh75Rr+MrQCjtw@mail.gmail.com> <20110722054345.GE18126@1wt.eu> <9031.1311500145.687172@puncture> <20110724105223.GL22405@1wt.eu> <CALiegfkTVg2=k4d8rxmpqXmaRUihRmhtgfF4QRUTAKic7gBk5w@mail.gmail.com> <20110724121147.GR22405@1wt.eu> <CALiegf=GDDKdXOXgz3oognh6=qRDKFUSrRfLOtOoUucAxr4p3w@mail.gmail.com> <20110724183343.GY22405@1wt.eu>
In-Reply-To: <20110724183343.GY22405@1wt.eu>
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: Sun, 24 Jul 2011 23:49:44 -0000

Willy Tarreau wrote:

>> Ok, but I don't consider a xtra DNS query to be so hard.
> 
> I had to perform sites analysis for a customer a few months ago. Many
> web pages nowadays have between 100 and 200 objects to fetch, spread
> over up to 25-30 host names.

How long does it take to fetch all the contents of 100 or 200 objects?

> If you take even only 100ms for each of
> them, you're at 3 additional seconds to display the page. Granted those
> requests are not WS and only HTTP, but as I said, SRV for WS won't work
> before it works with HTTP, at least due to proxies.

It's merely additional 100ms.

							Masataka Ohta

From mohta@necom830.hpcl.titech.ac.jp  Sun Jul 24 16:59:36 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 C3A2821F86DD for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 16:59:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.074
X-Spam-Level: 
X-Spam-Status: No, score=-0.074 tagged_above=-999 required=5 tests=[AWL=0.016,  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 yvtjDJdic3Oz for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 16:59:36 -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 0122D21F86BC for <ietf@ietf.org>; Sun, 24 Jul 2011 16:59:35 -0700 (PDT)
Received: (qmail 76513 invoked from network); 25 Jul 2011 00:19:04 -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 Jul 2011 00:19:04 -0000
Message-ID: <4E2CB1B1.3080309@necom830.hpcl.titech.ac.jp>
Date: Mon, 25 Jul 2011 08:58:41 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <9031.1311286867.939466@puncture> <4E28BA9D.6010501@callenish.com> <CAP992=GedTEfimykCWwdwm=BsZdwFRJO36EO0a_o7iejURJ+tQ@mail.gmail.com> <CALiegfnwNyYDy=SyrqHJXV0ZreADb7F8QySvgdHofW9Hm9miZQ@mail.gmail.com> <CABLsOLCgxDNDs54GUybBzmG8a6rNPzXzFcwf_OU25j5L+AobaQ@mail.gmail.com> <CALiegfnp+kNqnU-_x2ZBZnN8fzP=4+6WO=QPjw1rJzvZmSXEAg@mail.gmail.com> <20110724185949.GB22405@1wt.eu>
In-Reply-To: <20110724185949.GB22405@1wt.eu>
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: Sun, 24 Jul 2011 23:59:36 -0000

Willy Tarreau wrote:

> On lossy networks such as 3G, they definitely are. A lost UDP packet is
> not retransmitted nor signaled as lost, so the browser has to retry. However,
> once the connection is established to the server, most losses are more or
> less smoothed by TCP extensions such as SACK. So yes, it can take several
> seconds to just resolve a host and then only a few hundreds of ms to retrieve
> the objects. I've observed it.

Poor implementation.

If the network between a mobile phone and its name server is known
to be lossy and latency is the issue, send multiple queries to the
name server.

						Masataka Ohta

From mohta@necom830.hpcl.titech.ac.jp  Sun Jul 24 17:05:06 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 26AC921F8748 for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 17:05:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.075
X-Spam-Level: 
X-Spam-Status: No, score=-0.075 tagged_above=-999 required=5 tests=[AWL=0.015,  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 HSXOqq5UKEGN for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 17:05:05 -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 5A25921F86E6 for <ietf@ietf.org>; Sun, 24 Jul 2011 17:05:05 -0700 (PDT)
Received: (qmail 76553 invoked from network); 25 Jul 2011 00:24: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; 25 Jul 2011 00:24:33 -0000
Message-ID: <4E2CB2FB.6060801@necom830.hpcl.titech.ac.jp>
Date: Mon, 25 Jul 2011 09:04:11 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <9031.1311286867.939466@puncture> <4E28BA9D.6010501@callenish.com> <CAP992=GedTEfimykCWwdwm=BsZdwFRJO36EO0a_o7iejURJ+tQ@mail.gmail.com> <CALiegfnwNyYDy=SyrqHJXV0ZreADb7F8QySvgdHofW9Hm9miZQ@mail.gmail.com> <CABLsOLCgxDNDs54GUybBzmG8a6rNPzXzFcwf_OU25j5L+AobaQ@mail.gmail.com> <CALiegfnp+kNqnU-_x2ZBZnN8fzP=4+6WO=QPjw1rJzvZmSXEAg@mail.gmail.com> <20110724185949.GB22405@1wt.eu> <9031.1311538720.416128@puncture> <20110724204236.GG22405@1wt.eu>
In-Reply-To: <20110724204236.GG22405@1wt.eu>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 00:05:06 -0000

Willy Tarreau wrote:

> But we have to keep in mind that for SRV to work, it cannot be made
> mandatory because existing infrastructure simply does not support it.

Such argument is valid at the IP, the infrastructure, layer where
IPv6 is to work but is not applicable at the application layer
where SRV is to work.

						Masataka Ohta

From marka@isc.org  Sun Jul 24 17:47:34 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 2665521F873A; Sun, 24 Jul 2011 17:47:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.605
X-Spam-Level: 
X-Spam-Status: No, score=-2.605 tagged_above=-999 required=5 tests=[AWL=-0.006, 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 2lWJWWcV6MTu; Sun, 24 Jul 2011 17:47:33 -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 7047821F8733; Sun, 24 Jul 2011 17:47:30 -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 4F9C75F9944; Mon, 25 Jul 2011 00:47:09 +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 C55DE216C81; Mon, 25 Jul 2011 00:47: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 A3AE71221C03; Mon, 25 Jul 2011 10:46:58 +1000 (EST)
To: Willy Tarreau <w@1wt.eu>
From: Mark Andrews <marka@isc.org>
References: <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <CALiegf=4K2oWfmZjGMD7J_jyaDtS3i+Mu7R0Wh75Rr+MrQCjtw@mail.gmail.com> <20110722054345.GE18126@1wt.eu> <9031.1311500145.687172@puncture> <20110724105223.GL22405@1wt.eu> <CALiegfkTVg2=k4d8rxmpqXmaRUihRmhtgfF4QRUTAKic7gBk5w@mail.gmail.com> <20110724121147.GR22405@1wt.eu> <CALiegf=GDDKdXOXgz3oognh6=qRDKFUSrRfLOtOoUucAxr4p3w@mail.gmail.com> <20110724183343.GY22405@1wt.eu>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
In-reply-to: Your message of "Sun, 24 Jul 2011 20:33:43 +0200." <20110724183343.GY22405@1wt.eu>
Date: Mon, 25 Jul 2011 10:46:58 +1000
Message-Id: <20110725004658.A3AE71221C03@drugs.dv.isc.org>
Cc: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 00:47:34 -0000

In message <20110724183343.GY22405@1wt.eu>, Willy Tarreau writes:
> On Sun, Jul 24, 2011 at 08:25:05PM +0200, I=F1aki Baz Castillo wrote:
> > 2011/7/24 Willy Tarreau <w@1wt.eu>:
> > >> > Making an additional DNS request and a connection come with a cost.
> > >>
> > >> http://tools.ietf.org/html/draft-ibc-websocket-dns-srv-02#section-5.2
> > >
> > > You still need the DNS request : the client does an A/AAAA request for
> > > the HTTP host, then if you ask it to use an SRV record for the WS conne=
> ction,
> > > it must perform that request too, even if it's to conclude that it can =
> reuse
> > > the idle connection.
> > =
> 
> > Ok, but I don't consider a xtra DNS query to be so hard.
> 
> I had to perform sites analysis for a customer a few months ago. Many
> web pages nowadays have between 100 and 200 objects to fetch, spread
> over up to 25-30 host names. If you take even only 100ms for each of
> them, you're at 3 additional seconds to display the page. Granted those
> requests are not WS and only HTTP, but as I said, SRV for WS won't work
> before it works with HTTP, at least due to proxies.

No. It takes 100ms extra.  Only if you serialise all the lookups
does it take 3 extra seconds.  If you are not doing the DNS lookups
in parallel today you are already doing a dis-service to your
customers.

Adding a SRV lookup should add 0ms if it isn't there as you should be
making A, AAAA and SRV lookups in parallel.  Non-existance is as
cachable as existance is.

> But those 3 extra seconds will always be considered a good reason not
> to make SRV mandatory for HTTP. The web is degrading very quickly due
> to poor practices, and we should be careful not to suggest to make it
> even worse.
> 
> Regards,
> Willy
> 
> _______________________________________________
> 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 marka@isc.org  Sun Jul 24 18:13:38 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 0D7F911E8071; Sun, 24 Jul 2011 18:13:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.605
X-Spam-Level: 
X-Spam-Status: No, score=-2.605 tagged_above=-999 required=5 tests=[AWL=-0.006, 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 3s11Kqz9B6h6; Sun, 24 Jul 2011 18:13: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 BFA2E11E8070; Sun, 24 Jul 2011 18:13:35 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 0117D5F9937; Mon, 25 Jul 2011 01:13:21 +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 E2285216C81; Mon, 25 Jul 2011 01:12:48 +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 AAF761222167; Mon, 25 Jul 2011 11:12:46 +1000 (EST)
To: Willy Tarreau <w@1wt.eu>
From: Mark Andrews <marka@isc.org>
References: <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com> <CALiegfkshhJVUHzTD1Kka5+RjGwZ5CS2J=Qk92jfSBg6Z0VfOQ@mail.gmail.com> <20110724121622.GS22405@1wt.eu> <CALiegfkzaMOHBz0-Sgj7HWtQX1jadczDu6t=5PoiNPMG69ZyVg@mail.gmail.com> <20110724185706.GA22405@1wt.eu> <CALiegf=smDo6CNQE+cA_2__BLr5wqbmr75unDJSMitavD4ySyA@mail.gmail.com> <20110724193230.GE22405@1wt.eu>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
In-reply-to: Your message of "Sun, 24 Jul 2011 21:32:30 +0200." <20110724193230.GE22405@1wt.eu>
Date: Mon, 25 Jul 2011 11:12:46 +1000
Message-Id: <20110725011246.AAF761222167@drugs.dv.isc.org>
Cc: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>, "Roy T. Fielding" <fielding@gbiv.com>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 01:13:38 -0000

In message <20110724193230.GE22405@1wt.eu>, Willy Tarreau writes:
> On Sun, Jul 24, 2011 at 09:02:59PM +0200, I=F1aki Baz Castillo wrote:
> > 2011/7/24 Willy Tarreau <w@1wt.eu>:
> > > But that's not what I meant, I meant that DNS is not the only solution
> > > to resolve host names. WINS, NIS and /etc/hosts are usable too. When I
> > > was a student in 94, we had all our passwords and hostnames in NIS and
> > > no DNS was configured. It worked like a charm. DNS is not something
> > > mandatory at all for many protocols. It just happens to be the standard
> > > over the public Internet.
> > =
> 
> > Ok, I get your point now :)
> > But, do current webbrosers resolve names using anything but DNS A?
> > (well, I know that they use /etc/hosts). Anyhow, WINS / NIS /etc/hosts
> > and such stuff just maps a hostname into a single IP. It's the
> > equivalent of a DNS A resource record. Think about locating a mail
> > server (MX is required), you need a DNS server.
> 
> ... or a static entry (the "Smart Relay host" entry you see in on the DS
> line in sendmail.cf). That's the case of any mail client in a campus, they
> don't use DNS to send outgoing mail. And even within the mail relays and
> servers, it's quite common to have a relaydomains file to map domains to
> servers.
> 
> Willy

But the Smart Relay host uses MX records.  The Smart Relay host should
be seen as the same as a HTTP proxy.
 
> _______________________________________________
> 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 drc@virtualized.org  Sun Jul 24 18:49:37 2011
Return-Path: <drc@virtualized.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5250021F8538 for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 18:49:37 -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 yzTM9okT6fss for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 18:49:36 -0700 (PDT)
Received: from virtualized.org (trantor.virtualized.org [204.152.189.190]) by ietfa.amsl.com (Postfix) with ESMTP id C251021F8532 for <ietf@ietf.org>; Sun, 24 Jul 2011 18:49:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by virtualized.org (Postfix) with ESMTP id 5DB8814C632D; Sun, 24 Jul 2011 18:49:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at virtualized.org
Received: from virtualized.org ([127.0.0.1]) by localhost (trantor.virtualized.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U98267eFluuP; Sun, 24 Jul 2011 18:49:34 -0700 (PDT)
Received: from [10.0.1.10] (cpe-66-91-109-17.hawaii.res.rr.com [66.91.109.17]) by virtualized.org (Postfix) with ESMTP id 58E3E14C6322; Sun, 24 Jul 2011 18:49:34 -0700 (PDT)
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=iso-8859-1
From: David Conrad <drc@virtualized.org>
In-Reply-To: <20110724191641.GC22405@1wt.eu>
Date: Sun, 24 Jul 2011 15:49:33 -1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <644A437E-BB0D-45E9-B6C3-5EF66A811986@virtualized.org>
References: <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com> <CALiegfkshhJVUHzTD1Kka5+RjGwZ5CS2J=Qk92jfSBg6Z0VfOQ@mail.gmail.com> <C9CD680E-8D68-4380-A76F-70F41F30F877@gbiv.com> <CALiegfkFnKjP09Vijo3c_DFYn4=UZm9M-4mVuZUyBk8rzwmDCw@mail.gmail.com> <20110724191641.GC22405@1wt.eu>
To: Willy Tarreau <w@1wt.eu>
X-Mailer: Apple Mail (2.1244.3)
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, 25 Jul 2011 01:49:37 -0000

[I haven't been following hybi and haven't read the draft, but as this =
is posted to the ietf list and there are a bunch of assertions here =
about the DNS I consider ... odd, I thought I'd chime in]

On Jul 24, 2011, at 8:59 AM, Willy Tarreau wrote:
> A lost UDP packet is not retransmitted nor signaled as lost, so the =
browser has to retry.

This sounds like a seriously broken resolver.  All resolvers I'm aware =
of have timeouts and retry if no response is received within the =
timeout. A resolver that gives up after a first time out is equivalent =
to a TCP stack that doesn't retransmit a SYN.  A bug should be filed =
with the vendor.

On Jul 24, 2011, at 9:16 AM, Willy Tarreau wrote:
> CNAME is the exact equivalent of SRV.

No. According to the RFCs and most implementations, you can't have CNAME =
with other data (A, MX, SOA, NS, etc).  With SRV, you can have anything =
at the same label.

> None is cheaper nor better than the other.

CNAME results in the resolver doing additional work, generally resulting =
in no need for an additional query but is not applicable in all =
situations (e.g., putting a CNAME at a zone apex is a gamble). SRV is =
far more general solution with additional benefits (e.g., priority) but =
requires an additional query.  The two RR type solve different problems. =
 CNAME is an alias for a host.  SRV provides information about services =
at a host.

On Jul 24, 2011, at 9:29 AM, Willy Tarreau wrote:
> DNS provides geolocation and proposes you the closest working =
datacenter.

No it doesn't.  The DNS _may_ provide a reasonable facsimile to =
geolocation if and only if the resolver is co-located with the =
requester. In a world of Google DNS, OpenDNS, ISP-wide anycast =
resolvers, etc., the assumption that the location associated with the IP =
of a DNS query correlates to the IP address of the HTTP initiator =
becomes increasingly dangerous.

>> Anyhow, don't forget that SRV is not just for failover, but also for =
load-balancing

> This is already addressed by DNS round robin and used by a lot of =
sites.

Only at the grossest level. What a client get back from a query depends =
on who has queried the same cache and authoritative server and what =
policy the authoritative server has for returning answers.  In reality, =
'round robin' is 'random'.  This is qualitatively different than the =
prioritization offered by SRV.

Regards,
-drc


From moore@network-heretics.com  Sun Jul 24 19:47: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 8150021F8531; Sun, 24 Jul 2011 19:47:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 DqTFQezuUvPk; Sun, 24 Jul 2011 19:47:44 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id AB54A21F8532; Sun, 24 Jul 2011 19:47:43 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id ADCEA21072; Sun, 24 Jul 2011 22:47:42 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Sun, 24 Jul 2011 22:47: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=A2D czvwhzff1lO+chGu9XEEHWP8=; b=EtUJWqb4Btjp7qZ7Z6hrpXEC+t/Yy1DfT+n 6TPmEwDFSMP3jDSi5zsB1lYEYNokbJwwXgn7YB7ziX40Zr6NG4kQQ6V3D1Evo5pF 2M6wMvG7xdyZAdQ9rnKfdKnt8MlXCpNscuTEJM+eZLdsYYEMm//jo9/Ffs2w8Qn8 0hO94iOY=
X-Sasl-enc: gkQJXl+I8idj7FuMj6NM7NEUIYzyuA3Ec1WJCixRf+QD 1311562061
Received: from [192.168.200.118] (modemcable114.145-70-69.static.videotron.ca [69.70.145.114]) by mail.messagingengine.com (Postfix) with ESMTPSA id 03340413373; Sun, 24 Jul 2011 22:47:40 -0400 (EDT)
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-7-394893780
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <20110724073323.EEAAF121E985@drugs.dv.isc.org>
Date: Sun, 24 Jul 2011 22:47:39 -0400
Message-Id: <4B3C19FD-B736-4DA7-9DB5-3D433320DCBC@network-heretics.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com> <20110724073323.EEAAF121E985@drugs.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1084)
Cc: =?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>, "Roy T. Fielding" <fielding@gbiv.com>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 02:47:45 -0000

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

On Jul 24, 2011, at 3:33 AM, Mark Andrews wrote:

> How do you solve the problem of hosting just "http://example.com/"
> on "s1.joes-web-service.com" and not redirect everything else at
> example.com?  People have been complaining about this for about as
> long as the web has existed.

Well, in a way, that's what NAPTR was for.  All of the UR
i resolution mechanisms (equally applicable to DNS-based URIs) that were =
developed and never really used grew out of the original realization in =
the early 1990s that CERN could stop hosting the original web pages if =
it wanted to, and there was no way to keep those links from going stale.

The problem never went away, but the DNS-based solutions were defined a =
long time ago and never used.   By now, I think the market has long =
since decided.  For better or worse, the mechanism the market chose to =
use with the web was HTTP redirects.

Keith


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

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jul 24, 2011, at 3:33 AM, Mark Andrews 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; ">How do you =
solve the problem of hosting just "<a =
href=3D"http://example.com/">http://example.com/</a>"<br>on "<a =
href=3D"http://s1.joes-web-service.com/">s1.joes-web-service.com</a>" =
and not redirect everything else at<br><a =
href=3D"http://example.com/">example.com</a>? &nbsp;People have been =
complaining about this for about as<br>long as the web has =
existed.</span></blockquote></div><br><div>Well, in a way, that's what =
NAPTR was for. &nbsp;All of the UR</div><div>i resolution mechanisms =
(equally applicable to DNS-based URIs) that were developed and never =
really used grew out of the original realization in the early 1990s that =
CERN could stop hosting the original web pages if it wanted to, and =
there was no way to keep those links from going =
stale.</div><div><br></div><div>The problem never went away, but the =
DNS-based solutions were defined a long time ago and never used. &nbsp; =
By now, I think the market has long since decided. &nbsp;For better or =
worse, the mechanism the market chose to use with the web was HTTP =
redirects.</div><div><br></div><div>Keith</div><div><br></div></body></htm=
l>=

--Apple-Mail-7-394893780--

From marka@isc.org  Sun Jul 24 20:00:03 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 0E38921F85CA; Sun, 24 Jul 2011 20:00:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.605
X-Spam-Level: 
X-Spam-Status: No, score=-2.605 tagged_above=-999 required=5 tests=[AWL=-0.006, 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 8WgueCnhwFNs; Sun, 24 Jul 2011 20:00:02 -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 724BC21F8560; Sun, 24 Jul 2011 20:00:02 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 0504E5F9953; Mon, 25 Jul 2011 02:59:50 +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 BC5CA216C83; Mon, 25 Jul 2011 02:59:17 +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 4520F1222A1C; Mon, 25 Jul 2011 12:59:14 +1000 (EST)
To: John Tamplin <jat@google.com>
From: Mark Andrews <marka@isc.org>
References: <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <CALiegf=4K2oWfmZjGMD7J_jyaDtS3i+Mu7R0Wh75Rr+MrQCjtw@mail.gmail.com> <20110722054345.GE18126@1wt.eu> <9031.1311500145.687172@puncture> <20110724105223.GL22405@1wt.eu> <CALiegfkTVg2=k4d8rxmpqXmaRUihRmhtgfF4QRUTAKic7gBk5w@mail.gmail.com> <20110724121147.GR22405@1wt.eu> <CALiegf=GDDKdXOXgz3oognh6=qRDKFUSrRfLOtOoUucAxr4p3w@mail.gmail.com> <20110724183343.GY22405@1wt.eu> <20110725004658.A3AE71221C03@drugs.dv.isc.org> <CABLsOLD-KM6DnR8HvfGH8N1M=1bZ4z8zus0YDczaXSfocBQ+Bw@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
In-reply-to: Your message of "Sun, 24 Jul 2011 21:06:37 -0400." <CABLsOLD-KM6DnR8HvfGH8N1M=1bZ4z8zus0YDczaXSfocBQ+Bw@mail.gmail.com>
Date: Mon, 25 Jul 2011 12:59:14 +1000
Message-Id: <20110725025914.4520F1222A1C@drugs.dv.isc.org>
Cc: Server-Initiated HTTP <hybi@ietf.org>, Willy Tarreau <w@1wt.eu>, 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, 25 Jul 2011 03:00:03 -0000

In message <CABLsOLD-KM6DnR8HvfGH8N1M=1bZ4z8zus0YDczaXSfocBQ+Bw@mail.gmail.com>
, John Tamplin writes:
> 
> On Sun, Jul 24, 2011 at 8:46 PM, Mark Andrews <marka@isc.org> wrote:
> 
> > Adding a SRV lookup should add 0ms if it isn't there as you should be
> > making A, AAAA and SRV lookups in parallel.  Non-existance is as
> > cachable as existance is.
> 
> But you have to wait until the SRV returns even if the A/AAAA response comes
> back first, so there is a non-zero cost even with an optimal implementation.
> I am not arguing whether the cost is worth the benefits, only that there is
> a cost in any case.

In 99.9999% of cases the three answers will come in within 1ms of
each other and you may be waiting on the A or AAAA record.  It
really doesn't take any longer to answer a SRV query compared to a
A or AAAA query.

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  Sun Jul 24 20:21:56 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 D540411E8074; Sun, 24 Jul 2011 20:21:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.605
X-Spam-Level: 
X-Spam-Status: No, score=-2.605 tagged_above=-999 required=5 tests=[AWL=-0.006, 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 KsKN26D-3V1M; Sun, 24 Jul 2011 20:21:56 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id F0AFF11E8072; Sun, 24 Jul 2011 20:21:55 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 0AC5E5F98EF; Mon, 25 Jul 2011 03:21:41 +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 E7C52216C84; Mon, 25 Jul 2011 03:21: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 A36701222CE2; Mon, 25 Jul 2011 13:21:36 +1000 (EST)
To: Keith Moore <moore@network-heretics.com>
From: Mark Andrews <marka@isc.org>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com> <20110724073323.EEAAF121E985@drugs.dv.isc.org> <4B3C19FD-B736-4DA7-9DB5-3D433320DCBC@network-heretics.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
In-reply-to: Your message of "Sun, 24 Jul 2011 22:47:39 -0400." <4B3C19FD-B736-4DA7-9DB5-3D433320DCBC@network-heretics.com>
Date: Mon, 25 Jul 2011 13:21:36 +1000
Message-Id: <20110725032136.A36701222CE2@drugs.dv.isc.org>
Cc: =?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>, "Roy T. Fielding" <fielding@gbiv.com>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 03:21:57 -0000

In message <4B3C19FD-B736-4DA7-9DB5-3D433320DCBC@network-heretics.com>, Keith M
oore writes:
> On Jul 24, 2011, at 3:33 AM, Mark Andrews wrote:
> 
> > How do you solve the problem of hosting just "http://example.com/"
> > on "s1.joes-web-service.com" and not redirect everything else at
> > example.com?  People have been complaining about this for about as
> > long as the web has existed.
> 
> Well, in a way, that's what NAPTR was for.  All of the UR
> i resolution mechanisms (equally applicable to DNS-based URIs) that were =
> developed and never really used grew out of the original realization in =
> the early 1990s that CERN could stop hosting the original web pages if =
> it wanted to, and there was no way to keep those links from going stale.

NAPTR is not defined for HTTP.
SRV is not defined for HTTP.
 
> The problem never went away, but the DNS-based solutions were defined a =
> long time ago and never used.

No.  It was explitly NOT defined.

RFC 2782
Applicability Statement

   In general, it is expected that SRV records will be used by clients
   for applications where the relevant protocol specification indicates
   that clients should use the SRV record. Such specification MUST
   define the symbolic name to be used in the Service field of the SRV
   record as described below. It also MUST include security
   considerations. Service SRV records SHOULD NOT be used in the absence
   of such specification.

> By now, I think the market has long =
> since decided.  For better or worse, the mechanism the market chose to =
> use with the web was HTTP redirects.

If the market hasn't has a really opportunity do decide as only one
mechanism has been specified and coded.  Most people don't know of
the existence of SRV or that it would be useful for HTTP.

If the only tool you have is a hammer then you use a hammer even
if a screwdriver would be better.

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

From moore@network-heretics.com  Sun Jul 24 21:12: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 ECAD721F853E; Sun, 24 Jul 2011 21:12: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=[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 7TqcdDQ3I-4K; Sun, 24 Jul 2011 21:12: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 3C6A121F853A; Sun, 24 Jul 2011 21:12:45 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id BC92720877; Mon, 25 Jul 2011 00:12:43 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Mon, 25 Jul 2011 00:12: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=jJ/T+WiGmKn8sH5US+iMXXpYmDE=; b=Le HmCeoIYqCkNwKg6yZqeS+LT0JquJButSUUYHyyKDtIPDGB3FIhE9JJL7VVKzBEe9 0OUry12SKs6KTFaVWYNt194tkv0r1MXK09LAJIFMzDrSzb6qVGVWbspu8Ba42T8x pZDYrAYL+PEgVV8YtvnLV/wmz66HY58ejiSdrNU3Q=
X-Sasl-enc: Ii8Wzsn3IuLkXIgNvmjld9S9HC43yYSJbqd9dmcoJlT3 1311567163
Received: from [192.168.200.118] (modemcable114.145-70-69.static.videotron.ca [69.70.145.114]) by mail.messagingengine.com (Postfix) with ESMTPSA id 709964540A8; Mon, 25 Jul 2011 00:12:42 -0400 (EDT)
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
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: <20110725032136.A36701222CE2@drugs.dv.isc.org>
Date: Sun, 24 Jul 2011 23:33:04 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3BC48562-6459-4FB9-9806-731AF87FE027@network-heretics.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com> <20110724073323.EEAAF121E985@drugs.dv.isc.org> <4B3C19FD-B736-4DA7-9DB5-3D433320DCBC@network-heretics.com> <20110725032136.A36701222CE2@drugs.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1084)
Cc: =?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>, "Roy T. Fielding" <fielding@gbiv.com>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 04:12:46 -0000

On Jul 24, 2011, at 11:21 PM, Mark Andrews wrote:

>>> How do you solve the problem of hosting just "http://example.com/"
>>> on "s1.joes-web-service.com" and not redirect everything else at
>>> example.com?  People have been complaining about this for about as
>>> long as the web has existed.
>>=20
>> Well, in a way, that's what NAPTR was for.  All of the UR
>> i resolution mechanisms (equally applicable to DNS-based URIs) that =
were =3D
>> developed and never really used grew out of the original realization =
in =3D
>> the early 1990s that CERN could stop hosting the original web pages =
if =3D
>> it wanted to, and there was no way to keep those links from going =
stale.
>=20
> NAPTR is not defined for HTTP.
> SRV is not defined for HTTP.
>=20
>> The problem never went away, but the DNS-based solutions were defined =
a =3D
>> long time ago and never used.
>=20
> No.  It was explitly NOT defined.

Ok, fair enough.   Those of us who were working on the DNS-based URI =
resolution mechanisms realized that they could be applied to http URIs =
in addition to almost anything else (NAPTR is incredibly flexible if you =
don't mind doing lots of DNS lookups).  But they were never formally =
adopted.

But if you really want to use DNS to do redirects for http: URIs (or for =
that matter ws: URIs or almost any other kind of URI), NAPTR was =
tailor-made to do that.  SRV was not.

Keith


From marka@isc.org  Sun Jul 24 21:36:45 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 5DECE21F84ED; Sun, 24 Jul 2011 21:36:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.605
X-Spam-Level: 
X-Spam-Status: No, score=-2.605 tagged_above=-999 required=5 tests=[AWL=-0.006, 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 HVO99dEVd5Cb; Sun, 24 Jul 2011 21:36:44 -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 6192F21F84DC; Sun, 24 Jul 2011 21:36: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.ams1.isc.org (Postfix) with ESMTPS id 886065F98FD; Mon, 25 Jul 2011 04:36:17 +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 75176216C7B; Mon, 25 Jul 2011 04:35:45 +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 0A49C1222F02; Mon, 25 Jul 2011 14:35:43 +1000 (EST)
To: Keith Moore <moore@network-heretics.com>
From: Mark Andrews <marka@isc.org>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com> <20110724073323.EEAAF121E985@drugs.dv.isc.org> <4B3C19FD-B736-4DA7-9DB5-3D433320DCBC@network-heretics.com> <20110725032136.A36701222CE2@drugs.dv.isc.org> <3BC48562-6459-4FB9-9806-731AF87FE027@network-heretics.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
In-reply-to: Your message of "Sun, 24 Jul 2011 23:33:04 -0400." <3BC48562-6459-4FB9-9806-731AF87FE027@network-heretics.com>
Date: Mon, 25 Jul 2011 14:35:42 +1000
Message-Id: <20110725043543.0A49C1222F02@drugs.dv.isc.org>
Cc: =?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>, "Roy T. Fielding" <fielding@gbiv.com>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 04:36:45 -0000

In message <3BC48562-6459-4FB9-9806-731AF87FE027@network-heretics.com>, Keith M
oore writes:
> On Jul 24, 2011, at 11:21 PM, Mark Andrews wrote:
> 
> >>> How do you solve the problem of hosting just "http://example.com/"
> >>> on "s1.joes-web-service.com" and not redirect everything else at
> >>> example.com?  People have been complaining about this for about as
> >>> long as the web has existed.
> >>=20
> >> Well, in a way, that's what NAPTR was for.  All of the UR
> >> i resolution mechanisms (equally applicable to DNS-based URIs) that =
> were =3D
> >> developed and never really used grew out of the original realization =
> in =3D
> >> the early 1990s that CERN could stop hosting the original web pages =
> if =3D
> >> it wanted to, and there was no way to keep those links from going =
> stale.
> >=20
> > NAPTR is not defined for HTTP.
> > SRV is not defined for HTTP.
> >=20
> >> The problem never went away, but the DNS-based solutions were defined =
> a =3D
> >> long time ago and never used.
> >=20
> > No.  It was explitly NOT defined.
> 
> Ok, fair enough.   Those of us who were working on the DNS-based URI =
> resolution mechanisms realized that they could be applied to http URIs =
> in addition to almost anything else (NAPTR is incredibly flexible if you =
> don't mind doing lots of DNS lookups).  But they were never formally =
> adopted.
> 
> But if you really want to use DNS to do redirects for http: URIs (or for =
> that matter ws: URIs or almost any other kind of URI), NAPTR was =
> tailor-made to do that.  SRV was not.

"_http._tcp.example.com SRV 100 0 80 <server>" is not a redirect.
The http client still issues "Host: example.com" not "Host: <server>".
If you want to do DNS level redirect of "www.example.com" to
"example.com" then NAPTR would be the way to do that and the http
client issues "Host: example.com" instead of "Host: www.example.com".

If web browers were using CNAME records correctly, i.e. as aliases,
then they would be treated as a DNS level redirect not as "return
the address of CNAME target but otherwise ignore that this is a
alias".  Doing this has all sorts if implications.  A lot of the
IDN issues are a direct result of HTTP clients/adminstrators abusing
CNAME.

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  Sun Jul 24 21:51: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 B90E121F8581; Sun, 24 Jul 2011 21:51:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.604
X-Spam-Level: 
X-Spam-Status: No, score=-2.604 tagged_above=-999 required=5 tests=[AWL=-0.005, 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 2IzRKSfo5uEi; Sun, 24 Jul 2011 21:51:26 -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 2967921F857E; Sun, 24 Jul 2011 21:51: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.ams1.isc.org (Postfix) with ESMTPS id 1B24F5F98EB; Mon, 25 Jul 2011 04:51: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 55D54216C7B; Mon, 25 Jul 2011 04:50:40 +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 0EDEE122303F; Mon, 25 Jul 2011 14:50:38 +1000 (EST)
To: Willy Tarreau <w@1wt.eu>
From: Mark Andrews <marka@isc.org>
References: <4E28A51F.4020704@callenish.com> <CALiegf=4K2oWfmZjGMD7J_jyaDtS3i+Mu7R0Wh75Rr+MrQCjtw@mail.gmail.com> <20110722054345.GE18126@1wt.eu> <9031.1311500145.687172@puncture> <20110724105223.GL22405@1wt.eu> <CALiegfkTVg2=k4d8rxmpqXmaRUihRmhtgfF4QRUTAKic7gBk5w@mail.gmail.com> <20110724121147.GR22405@1wt.eu> <CALiegf=GDDKdXOXgz3oognh6=qRDKFUSrRfLOtOoUucAxr4p3w@mail.gmail.com> <20110724183343.GY22405@1wt.eu> <20110725004658.A3AE71221C03@drugs.dv.isc.org> <20110725042921.GJ22405@1wt.eu>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
In-reply-to: Your message of "Mon, 25 Jul 2011 06:29:21 +0200." <20110725042921.GJ22405@1wt.eu>
Date: Mon, 25 Jul 2011 14:50:37 +1000
Message-Id: <20110725045038.0EDEE122303F@drugs.dv.isc.org>
Cc: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 04:51:26 -0000

In message <20110725042921.GJ22405@1wt.eu>, Willy Tarreau writes:
> On Mon, Jul 25, 2011 at 10:46:58AM +1000, Mark Andrews wrote:
> > Adding a SRV lookup should add 0ms if it isn't there as you should be
> > making A, AAAA and SRV lookups in parallel.
> 
> This does not work for a simple reason : you have to perform the lookups
> on the SRV response just as you would do with a CNAME :

Please re-read my claim as your comment is not applicable to it.

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  Mon Jul 25 06:10:18 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 A2ECB21F8AAC for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 06:10:18 -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 IY8AfZfDaQpq for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 06:10:16 -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 A6FC021F8A4B for <ietf@ietf.org>; Mon, 25 Jul 2011 06:10:12 -0700 (PDT)
Received: by vws12 with SMTP id 12so3692607vws.31 for <ietf@ietf.org>; Mon, 25 Jul 2011 06:10:12 -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=ySUBIjr7M/+zbSvVor5RUkJtblZEPclieHcF7GKkLO4=; b=qMQA26qsrpScVzYxIFOUXrW/Erz+L143V/LNUwFIEx7NGGJPOPwK0upDxEWF1eSRCZ 6eaxV6SnuYJBW/r9zmL99SCxVBaqokNdPFgYBVT7MZdEcDyFC1w8uWWWeDVShp7FIZU2 kqwbfd9iuifN8bMQ3Q/LYvyqre0N9I9IEZINA=
Received: by 10.52.89.211 with SMTP id bq19mr4611532vdb.22.1311599412055; Mon, 25 Jul 2011 06:10:12 -0700 (PDT)
MIME-Version: 1.0
Sender: shimshamshimmy@gmail.com
Received: by 10.52.158.197 with HTTP; Mon, 25 Jul 2011 06:09:52 -0700 (PDT)
From: Jun Murai <jun@wide.ad.jp>
Date: Mon, 25 Jul 2011 22:09:52 +0900
X-Google-Sender-Auth: -J06QZi6hVlBwxXuUcouyRGTUIU
Message-ID: <CA+k18nV-pEWiTNfAwvU9YiTWuRG0Q_0EFNioELFhJP2JCNx1aA@mail.gmail.com>
Subject: reminder: itojun service award 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: Mon, 25 Jul 2011 13:10:18 -0000

Dear IETFers,

There was one case on the nomination process where we did not receive
a submitted nomination.

Therefore, we decided to extend  nomination time until July 31st.
If you have not received confirmation for the past nomination, please
resubmit it (until you get confirmation!) please!

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

From gregw@intalio.com  Sun Jul 24 17:40:54 2011
Return-Path: <gregw@intalio.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADE7A21F86FF; Sun, 24 Jul 2011 17:40:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.859
X-Spam-Level: 
X-Spam-Status: No, score=-2.859 tagged_above=-999 required=5 tests=[AWL=0.118,  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 6qNM1UP7GiOe; Sun, 24 Jul 2011 17:40:53 -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 0BF8C21F86A4; Sun, 24 Jul 2011 17:40:52 -0700 (PDT)
Received: by vws12 with SMTP id 12so3330420vws.31 for <multiple recipients>; Sun, 24 Jul 2011 17:40:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.174.113 with SMTP id br17mr3781317vdc.107.1311554451856; Sun, 24 Jul 2011 17:40:51 -0700 (PDT)
Received: by 10.52.115.103 with HTTP; Sun, 24 Jul 2011 17:40:51 -0700 (PDT)
In-Reply-To: <96456EE7-0BE3-444C-BA16-178FE1DF99F8@bbn.com>
References: <B9DDE41C-1451-4C97-ACA4-0E4E26B75A07@bbn.com> <4E26FC3F.1030300@isode.com> <96456EE7-0BE3-444C-BA16-178FE1DF99F8@bbn.com>
Date: Mon, 25 Jul 2011 10:40:51 +1000
Message-ID: <CAH_y2NGOsnz9rFtJbAtW0TJK0NiO50UaAY1rRJjA+pZLLmtPSw@mail.gmail.com>
Subject: Re: Gen-ART last call review of draft-ietf-hybi-thewebsocketprotocol-10
From: Greg Wilkins <gregw@intalio.com>
To: draft-ietf-websec-thewebsocketprotocol@tools.ietf.org,  IETF Discussion <ietf@ietf.org>, General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 25 Jul 2011 08:04:51 -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, 25 Jul 2011 00:40:54 -0000

On 25 July 2011 05:11, Richard L. Barnes <rbarnes@bbn.com> wrote:
> It seems like this gets you around the threat that masking is supposed to=
 address -- the proxy won't see anything mid-stream that looks like HTTP, s=
ince it's just acting as a tunnel at that point. =A0It's a little weird to =
use CONNECT end-to-end, but that doesn't seem bad enough to be a blocking i=
ssue.

One concern expressed was that existing infrastructure may have
special handling that triggers on the CONNECT method.   Eg. code that
will look at only the first HTTP request on a connection before
becoming a bit pipe.  Such proxies will work with websockets when GET
is used, but will fail with CONNECT because it will trigger special
handling to look for the destination server, which will not be present
in the handshake.

If the concern with using GET is that we are changing established
semantics, then surely that concern must also apply to changing the
semantics of CONNECT.  If changed semantics is the concern, then using
an entirely new method would be applicable.

However, my reading of the discussion resulting to Roy's objection to
the use of GET, is that he was mostly concerned that the 101 response
not be consider the final response to the GET, and that semantically
there is still a request to be responded to that is related to the
specific URL passed in the GET.    If semantically the WS stream is
considered the response to the GET for the URI, then I think's Roy's
issues are resolved.   (NB. I've misread Roy's concerns a few times...
so confirmation that I've got it right this time would be good).

cheers

From jat@google.com  Sun Jul 24 18:07:00 2011
Return-Path: <jat@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 8C43F21F8678 for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 18:07:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.92
X-Spam-Level: 
X-Spam-Status: No, score=-105.92 tagged_above=-999 required=5 tests=[AWL=0.056, 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 bQBJOzkkBygS for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 18:07:00 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id B983421F8658 for <ietf@ietf.org>; Sun, 24 Jul 2011 18:06:59 -0700 (PDT)
Received: from hpaq14.eem.corp.google.com (hpaq14.eem.corp.google.com [172.25.149.14]) by smtp-out.google.com with ESMTP id p6P16w6r028225 for <ietf@ietf.org>; Sun, 24 Jul 2011 18:06:58 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1311556018; bh=xpgwc7lsKgfWirySk95DsbElaZQ=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=UiyJypoarLpng3D6K3yqF3VpJu4+Ig8RoQvjPlwx1G0rI0lpRDp5ghbf1ezOU0q90 CdzF6A29cQ31FrwmHexRQ==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type:x-system-of-record; b=hyDksnMaWw37edpnzL8Bb71nk/tASom9AT6xRqqW+mi5JAXJ2ghpsLZz9/NPhpUXh s6kwW6ZQVMWLh7EttncWA==
Received: from gxk2 (gxk2.prod.google.com [10.202.11.2]) by hpaq14.eem.corp.google.com with ESMTP id p6P16Vd2027781 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Sun, 24 Jul 2011 18:06:57 -0700
Received: by gxk2 with SMTP id 2so2207733gxk.36 for <ietf@ietf.org>; Sun, 24 Jul 2011 18:06:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=3i9GCBVEyQodIh7ePW/mCiGY5S3odGMHI63/zboROtE=; b=gfKBMu+zXLYKAsueciumOnJaFENDBuwJyPczxSfOTsHhbU0TBwD3aVxlH7zqKCUvnG w+ItynwCXaXESq0H9mhg==
Received: by 10.150.116.12 with SMTP id o12mr3854987ybc.2.1311556017123; Sun, 24 Jul 2011 18:06:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.49.7 with HTTP; Sun, 24 Jul 2011 18:06:37 -0700 (PDT)
In-Reply-To: <20110725004658.A3AE71221C03@drugs.dv.isc.org>
References: <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <CALiegf=4K2oWfmZjGMD7J_jyaDtS3i+Mu7R0Wh75Rr+MrQCjtw@mail.gmail.com> <20110722054345.GE18126@1wt.eu> <9031.1311500145.687172@puncture> <20110724105223.GL22405@1wt.eu> <CALiegfkTVg2=k4d8rxmpqXmaRUihRmhtgfF4QRUTAKic7gBk5w@mail.gmail.com> <20110724121147.GR22405@1wt.eu> <CALiegf=GDDKdXOXgz3oognh6=qRDKFUSrRfLOtOoUucAxr4p3w@mail.gmail.com> <20110724183343.GY22405@1wt.eu> <20110725004658.A3AE71221C03@drugs.dv.isc.org>
From: John Tamplin <jat@google.com>
Date: Sun, 24 Jul 2011 21:06:37 -0400
Message-ID: <CABLsOLD-KM6DnR8HvfGH8N1M=1bZ4z8zus0YDczaXSfocBQ+Bw@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
To: Mark Andrews <marka@isc.org>
Content-Type: multipart/alternative; boundary=000e0cd32b9480f27904a8da6ec3
X-System-Of-Record: true
X-Mailman-Approved-At: Mon, 25 Jul 2011 08:05:19 -0700
Cc: Server-Initiated HTTP <hybi@ietf.org>, Willy Tarreau <w@1wt.eu>, 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, 25 Jul 2011 01:07:00 -0000

--000e0cd32b9480f27904a8da6ec3
Content-Type: text/plain; charset=UTF-8

On Sun, Jul 24, 2011 at 8:46 PM, Mark Andrews <marka@isc.org> wrote:

> Adding a SRV lookup should add 0ms if it isn't there as you should be
> making A, AAAA and SRV lookups in parallel.  Non-existance is as
> cachable as existance is.
>

But you have to wait until the SRV returns even if the A/AAAA response comes
back first, so there is a non-zero cost even with an optimal implementation.
 I am not arguing whether the cost is worth the benefits, only that there is
a cost in any case.

-- 
John A. Tamplin
Software Engineer (GWT), Google

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

<div class=3D"gmail_quote">On Sun, Jul 24, 2011 at 8:46 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;">

Adding a SRV lookup should add 0ms if it isn&#39;t there as you should be<b=
r>
making A, AAAA and SRV lookups in parallel. =C2=A0Non-existance is as<br>
cachable as existance is.<br></blockquote><div><br></div><div>But you have =
to wait until the SRV returns even if the A/AAAA response comes back first,=
 so there is a non-zero cost even with an optimal implementation. =C2=A0I a=
m not arguing whether the cost is worth the benefits, only that there is a =
cost in any case.=C2=A0</div>

</div><br>-- <br>John A. Tamplin<br>Software Engineer (GWT), Google<br>

--000e0cd32b9480f27904a8da6ec3--

From w@1wt.eu  Sun Jul 24 21:29:30 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3375F11E8084; Sun, 24 Jul 2011 21:29:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.58
X-Spam-Level: 
X-Spam-Status: No, score=-4.58 tagged_above=-999 required=5 tests=[AWL=-2.537,  BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m3wUlNuT+J-7; Sun, 24 Jul 2011 21:29:29 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 5C8CA11E807C; Sun, 24 Jul 2011 21:29:28 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6P4TL1o028376; Mon, 25 Jul 2011 06:29:21 +0200
Date: Mon, 25 Jul 2011 06:29:21 +0200
From: Willy Tarreau <w@1wt.eu>
To: Mark Andrews <marka@isc.org>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110725042921.GJ22405@1wt.eu>
References: <4E28A51F.4020704@callenish.com> <CALiegf=4K2oWfmZjGMD7J_jyaDtS3i+Mu7R0Wh75Rr+MrQCjtw@mail.gmail.com> <20110722054345.GE18126@1wt.eu> <9031.1311500145.687172@puncture> <20110724105223.GL22405@1wt.eu> <CALiegfkTVg2=k4d8rxmpqXmaRUihRmhtgfF4QRUTAKic7gBk5w@mail.gmail.com> <20110724121147.GR22405@1wt.eu> <CALiegf=GDDKdXOXgz3oognh6=qRDKFUSrRfLOtOoUucAxr4p3w@mail.gmail.com> <20110724183343.GY22405@1wt.eu> <20110725004658.A3AE71221C03@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110725004658.A3AE71221C03@drugs.dv.isc.org>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Mon, 25 Jul 2011 08:06:07 -0700
Cc: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 04:29:30 -0000

On Mon, Jul 25, 2011 at 10:46:58AM +1000, Mark Andrews wrote:
> Adding a SRV lookup should add 0ms if it isn't there as you should be
> making A, AAAA and SRV lookups in parallel.

This does not work for a simple reason : you have to perform the lookups
on the SRV response just as you would do with a CNAME :

$ host -t srv _xmpp-server._tcp.gmail.com
_xmpp-server._tcp.gmail.com has SRV record 20 0 5269 xmpp-server1.l.google.com.
_xmpp-server._tcp.gmail.com has SRV record 5 0 5269 xmpp-server.l.google.com.
_xmpp-server._tcp.gmail.com has SRV record 20 0 5269 xmpp-server2.l.google.com.
_xmpp-server._tcp.gmail.com has SRV record 20 0 5269 xmpp-server3.l.google.com.
_xmpp-server._tcp.gmail.com has SRV record 20 0 5269 xmpp-server4.l.google.com.

And only now I can resolve xmpp-server.l.google.com and get its real address.
That's why I was saying that SRV and CNAME really are equivalent in terms of
latency, because both of them require an additional round trip.

And that is assuming that all the hosts are referenced on the main page, which
in practice is not true because a number of them are also in additional CSS
and JS.

Now if I want to be really picky, I'd add that at 100 bytes on average per
request, sending 30 additional requests means a total of 3kB of data on the
uplink, which require :
  - 1.5 second of uplink traffic on a 3G HDSPA link with 16kbps uplink
  - 375 ms of uplink traffic on a 3G HDSPA link with 64kbps uplink
  - 187 ms of uplink traffic on an ADSL 512/128

I'm not trying to dismiss the usefulness of the mechanism, I just don't
like to hear that doing something additional comes at absolutely zero cost.

Regards,
Willy


From w@1wt.eu  Sun Jul 24 21:32:09 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1350821F86AA; Sun, 24 Jul 2011 21:32:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.541
X-Spam-Level: 
X-Spam-Status: No, score=-4.541 tagged_above=-999 required=5 tests=[AWL=-2.498, BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8gRnsgC7a3zG; Sun, 24 Jul 2011 21:32:08 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id D6E3D5E8007; Sun, 24 Jul 2011 21:32:07 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6P4W0mF028394; Mon, 25 Jul 2011 06:32:00 +0200
Date: Mon, 25 Jul 2011 06:32:00 +0200
From: Willy Tarreau <w@1wt.eu>
To: Mark Andrews <marka@isc.org>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110725043200.GK22405@1wt.eu>
References: <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com> <CALiegfkshhJVUHzTD1Kka5+RjGwZ5CS2J=Qk92jfSBg6Z0VfOQ@mail.gmail.com> <20110724121622.GS22405@1wt.eu> <CALiegfkzaMOHBz0-Sgj7HWtQX1jadczDu6t=5PoiNPMG69ZyVg@mail.gmail.com> <20110724185706.GA22405@1wt.eu> <CALiegf=smDo6CNQE+cA_2__BLr5wqbmr75unDJSMitavD4ySyA@mail.gmail.com> <20110724193230.GE22405@1wt.eu> <20110725011246.AAF761222167@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110725011246.AAF761222167@drugs.dv.isc.org>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Mon, 25 Jul 2011 08:06:07 -0700
Cc: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>, "Roy T. Fielding" <fielding@gbiv.com>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 04:32:09 -0000

On Mon, Jul 25, 2011 at 11:12:46AM +1000, Mark Andrews wrote:
> > > But, do current webbrosers resolve names using anything but DNS A?
> > > (well, I know that they use /etc/hosts). Anyhow, WINS / NIS /etc/hosts
> > > and such stuff just maps a hostname into a single IP. It's the
> > > equivalent of a DNS A resource record. Think about locating a mail
> > > server (MX is required), you need a DNS server.
> > 
> > ... or a static entry (the "Smart Relay host" entry you see in on the DS
> > line in sendmail.cf). That's the case of any mail client in a campus, they
> > don't use DNS to send outgoing mail. And even within the mail relays and
> > servers, it's quite common to have a relaydomains file to map domains to
> > servers.
> > 
> > Willy
> 
> But the Smart Relay host uses MX records.  The Smart Relay host should
> be seen as the same as a HTTP proxy.

Exactly, which means that the browser can't be required to rely on any
information from the DNS since it does not necessarily have access to it
and other components which are not under our control might behave in a
different manner than what we'd like.

Regards,
Willy


From w@1wt.eu  Sun Jul 24 21:58:29 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D67821F87C5 for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 21:58:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.491
X-Spam-Level: 
X-Spam-Status: No, score=-4.491 tagged_above=-999 required=5 tests=[AWL=-2.448, BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y0tYasWpZxYS for <ietf@ietfa.amsl.com>; Sun, 24 Jul 2011 21:58:29 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 8192221F86FF for <ietf@ietf.org>; Sun, 24 Jul 2011 21:58:28 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6P4wLWT028438; Mon, 25 Jul 2011 06:58:21 +0200
Date: Mon, 25 Jul 2011 06:58:21 +0200
From: Willy Tarreau <w@1wt.eu>
To: David Conrad <drc@virtualized.org>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110725045821.GN22405@1wt.eu>
References: <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com> <CALiegfkshhJVUHzTD1Kka5+RjGwZ5CS2J=Qk92jfSBg6Z0VfOQ@mail.gmail.com> <C9CD680E-8D68-4380-A76F-70F41F30F877@gbiv.com> <CALiegfkFnKjP09Vijo3c_DFYn4=UZm9M-4mVuZUyBk8rzwmDCw@mail.gmail.com> <20110724191641.GC22405@1wt.eu> <644A437E-BB0D-45E9-B6C3-5EF66A811986@virtualized.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <644A437E-BB0D-45E9-B6C3-5EF66A811986@virtualized.org>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Mon, 25 Jul 2011 08:06:07 -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: Mon, 25 Jul 2011 04:58:29 -0000

On Sun, Jul 24, 2011 at 03:49:33PM -1000, David Conrad wrote:
> [I haven't been following hybi and haven't read the draft, but as this is posted to the ietf list and there are a bunch of assertions here about the DNS I consider ... odd, I thought I'd chime in]
> 
> On Jul 24, 2011, at 8:59 AM, Willy Tarreau wrote:
> > A lost UDP packet is not retransmitted nor signaled as lost, so the browser has to retry.
> 
> This sounds like a seriously broken resolver.  All resolvers I'm aware of have timeouts and retry if no response is received within the timeout. A resolver that gives up after a first time out is equivalent to a TCP stack that doesn't retransmit a SYN.  A bug should be filed with the vendor.

What are you saying ? Your browser embeds the resolved as a library, so when
I'm saying that "the browser has to retry", I mean the resolver part of the
browser has to retry.

> On Jul 24, 2011, at 9:16 AM, Willy Tarreau wrote:
> > CNAME is the exact equivalent of SRV.
> 
> No. According to the RFCs and most implementations, you can't have CNAME with other data (A, MX, SOA, NS, etc).  With SRV, you can have anything at the same label.

This does not change anything, because the CNAME is on the hostname while
the SRV is on the service name, so there is nothing wrong with having both.

> On Jul 24, 2011, at 9:29 AM, Willy Tarreau wrote:
> > DNS provides geolocation and proposes you the closest working datacenter.
> 
> >> Anyhow, don't forget that SRV is not just for failover, but also for load-balancing
> 
> > This is already addressed by DNS round robin and used by a lot of sites.
> 
> Only at the grossest level. What a client get back from a query depends on who has queried the same cache and authoritative server and what policy the authoritative server has for returning answers.  In reality, 'round robin' is 'random'.

Yes but in practice, this randomness offers very smooth distribution.

>  This is qualitatively different than the prioritization offered by SRV.

Indeed this is different, but this does not mean there is a huge need for
the minor improvements provided by SRV in this context.

I'm not saying that SRV is useless but that it adds little value to HTTP
and even smaller to WS without HTTP, and comes at a non-zero cost, whatever
people are saying. I'm also certain that if a new record were to be invented
(eg: report the server's load in real time), there would be major proponents
to make it mandatory for everything because it would be what would save the
world from an upcoming disaster.

I'm convinced we can find good use cases for SRV combined with either HTTP
or WS once we admit it is optional and the user controls this option. Try
to imagine what you could do if you knew that 50% of your visitors would
consider your SRV records. Maybe you could use them to progressively test
service updates. You could possibly get a better distribution, or serve
a maintenance page to some of them during maintenance operations instead
of leaving them in the dark. You have to think what the benefit can be
for the user to enable the option, not how to push it down his throat.

Regards,
Willy


From w@1wt.eu  Sun Jul 24 22:01:08 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61B0E21F84CD; Sun, 24 Jul 2011 22:01:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.456
X-Spam-Level: 
X-Spam-Status: No, score=-4.456 tagged_above=-999 required=5 tests=[AWL=-2.413, BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bp7HryQQygv2; Sun, 24 Jul 2011 22:01:08 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 8F8D821F84C9; Sun, 24 Jul 2011 22:01:07 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6P511in028449; Mon, 25 Jul 2011 07:01:01 +0200
Date: Mon, 25 Jul 2011 07:01:01 +0200
From: Willy Tarreau <w@1wt.eu>
To: Mark Andrews <marka@isc.org>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110725050101.GO22405@1wt.eu>
References: <20110722054345.GE18126@1wt.eu> <9031.1311500145.687172@puncture> <20110724105223.GL22405@1wt.eu> <CALiegfkTVg2=k4d8rxmpqXmaRUihRmhtgfF4QRUTAKic7gBk5w@mail.gmail.com> <20110724121147.GR22405@1wt.eu> <CALiegf=GDDKdXOXgz3oognh6=qRDKFUSrRfLOtOoUucAxr4p3w@mail.gmail.com> <20110724183343.GY22405@1wt.eu> <20110725004658.A3AE71221C03@drugs.dv.isc.org> <20110725042921.GJ22405@1wt.eu> <20110725045038.0EDEE122303F@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110725045038.0EDEE122303F@drugs.dv.isc.org>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Mon, 25 Jul 2011 08:06:07 -0700
Cc: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 05:01:08 -0000

On Mon, Jul 25, 2011 at 02:50:37PM +1000, Mark Andrews wrote:
> 
> In message <20110725042921.GJ22405@1wt.eu>, Willy Tarreau writes:
> > On Mon, Jul 25, 2011 at 10:46:58AM +1000, Mark Andrews wrote:
> > > Adding a SRV lookup should add 0ms if it isn't there as you should be
> > > making A, AAAA and SRV lookups in parallel.
> > 
> > This does not work for a simple reason : you have to perform the lookups
> > on the SRV response just as you would do with a CNAME :
> 
> Please re-read my claim as your comment is not applicable to it.

Ah OK : "if it isn't there". Sorry for missing it.

Willy


From rbonica@juniper.net  Mon Jul 25 09:11:14 2011
Return-Path: <rbonica@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C61621F847C for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 09:11:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.546
X-Spam-Level: 
X-Spam-Status: No, score=-106.546 tagged_above=-999 required=5 tests=[AWL=0.053, 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 ptSjM07zBBHv for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 09:11:13 -0700 (PDT)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id 7EFC021F8C19 for <ietf@ietf.org>; Mon, 25 Jul 2011 07:31:47 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKTi1+UrPS9056IvEv8Y2v5qoTwxeuqE7p@postini.com; Mon, 25 Jul 2011 07:31:47 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.2.254.0; Mon, 25 Jul 2011 07:30:48 -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; Mon, 25 Jul 2011 10:30:47 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 25 Jul 2011 10:30:46 -0400
Subject: draft-ietf-v6ops-6to4-to-historic  (yet again)
Thread-Topic: draft-ietf-v6ops-6to4-to-historic  (yet again)
Thread-Index: AcxK13EXQuzfLCzMQFivvvTkow95Tg==
Message-ID: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 16:11:14 -0000

Folks,

After some discussion, the IESG is attempting to determine whether there is=
 IETF consensus to do the following:

- add a new section to draft-ietf-v6ops-6to4-to-historic
- publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL

draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 and conv=
ert their status to HISTORIC. It will also contain a new section describing=
 what it means for RFCs 3056 and 3068 to be classified as HISTORIC. The new=
 section will say that:

- 6-to-4 should not be configured by default on any implementation (hosts, =
cpe routers, other)
- vendors will decide whether/when 6-to-4 will be removed from implementati=
ons. Likewise, operators will decide whether/when 6-to-4 relays will be rem=
oved from their networks. The status of RFCs 3056 and 3068 should not be in=
terpreted as a recommendation to remove 6-to-4 at any particular time.


draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While it clarif=
ies the meaning of "HISTORIC" in this particular case, it does not set a pr=
ecedent for any future case.

Please post your views on this course of action by August 8, 2011.


                                                                   Ron Boni=
ca
                                                                   <speakin=
g as OPS Area AD>

From moore@network-heretics.com  Mon Jul 25 10:14:47 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 1423A21F8B25 for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 10:14:47 -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 RKbQ2SHP7Kqg for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 10:14:46 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 1EB4E21F8B1D for <ietf@ietf.org>; Mon, 25 Jul 2011 10:14:43 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id AFCD220FAE; Mon, 25 Jul 2011 13:14:42 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Mon, 25 Jul 2011 13:14: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:content-transfer-encoding:message-id :references:to; s=smtpout; bh=wEgVt3ZHL2awRD721LDLZCWBy0I=; b=BY L66url8TPnXtdu+kA7omVce5k3t3OKiW0c3V9/6rZL0kpkw/PnmTBQE4slxdaJct I55rOmzF8NvnH1jdMq9J3LW/0GT7EUXMZc+WfH/Dkb6RljLdnVqZzWEdobtejovj uucVwjFxywk4WcQPlqC8WH7sKb6BQMGPxAGDshuNk=
X-Sasl-enc: +xvvhA7QFgRHCNGGC1YEPBt/gN5QWG03sEd12vScbU6E 1311614082
Received: from dhcp-336e.meeting.ietf.org (dhcp-336e.meeting.ietf.org [130.129.51.110]) by mail.messagingengine.com (Postfix) with ESMTPSA id 741254137B7; Mon, 25 Jul 2011 13:14:42 -0400 (EDT)
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
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: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
Date: Mon, 25 Jul 2011 13:14:42 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <AD68A37B-4C1A-423B-AEE9-82CB61E2733C@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
To: Ronald Bonica <rbonica@juniper.net>
X-Mailer: Apple Mail (2.1084)
Cc: Keith Moore <moore@network-heretics.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 17:14:47 -0000

I remain strongly opposed to reclassifying 6to4 as Historic unless/until =
a better alternative appears.  Putting an explanation inside an =
informational document doesn't change that opposition.

I also continue to believe that the -historic draft has too many =
misstatements and misleading statements in it, that the entire =
motivation for the draft is seriously flawed, and that it should not be =
published in anything like its current form.

But I agree that 6to4 should be off by default, mostly because there's =
no good off-the-shelf way to have 6to4 automatically disabled when a =
host or router connects to a network that is using NAT but not using RFC =
1918 addresses.

Keith

On Jul 25, 2011, at 10:30 AM, Ronald Bonica wrote:

> Folks,
>=20
> After some discussion, the IESG is attempting to determine whether =
there is IETF consensus to do the following:
>=20
> - add a new section to draft-ietf-v6ops-6to4-to-historic
> - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL
>=20
> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 and =
convert their status to HISTORIC. It will also contain a new section =
describing what it means for RFCs 3056 and 3068 to be classified as =
HISTORIC. The new section will say that:
>=20
> - 6-to-4 should not be configured by default on any implementation =
(hosts, cpe routers, other)
> - vendors will decide whether/when 6-to-4 will be removed from =
implementations. Likewise, operators will decide whether/when 6-to-4 =
relays will be removed from their networks. The status of RFCs 3056 and =
3068 should not be interpreted as a recommendation to remove 6-to-4 at =
any particular time.
>=20
>=20
> draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While it =
clarifies the meaning of "HISTORIC" in this particular case, it does not =
set a precedent for any future case.
>=20
> Please post your views on this course of action by August 8, 2011.
>=20
>=20
>                                                                   Ron =
Bonica
>                                                                   =
<speaking as OPS Area AD>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From glen@amsl.com  Mon Jul 25 10:17:54 2011
Return-Path: <glen@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C6D121F8B98; Mon, 25 Jul 2011 10:17:54 -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.079, 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 jPNlbzcMbQ33; Mon, 25 Jul 2011 10:17:53 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:1112:1::14]) by ietfa.amsl.com (Postfix) with ESMTP id 921F121F8B35; Mon, 25 Jul 2011 10:17:48 -0700 (PDT)
Received: by c1a.amsl.com (Postfix, from userid 1000) id 87C443A200B; Mon, 25 Jul 2011 10:17:48 -0700 (PDT)
Date: Mon, 25 Jul 2011 10:17:48 -0700
From: Glen <glen@amsl.com>
To: ietf-announce@ietf.org, ietf@ietf.org
Subject: DKIM Signatures now being applied to IETF Email
Message-ID: <20110725171748.GA13506@amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.17 (2007-11-01)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 17:17:54 -0000

All -

I am very pleased to report that the IETF is now applying DKIM signatures
to all outgoing list email from mailman.

Many thanks to Murray Kucherawy, lead author of OpenDKIM, for doing the work
to set up OpenDKIM on the IETF servers and getting it to work.  He made the
process painless, and we express our thanks to him for his service to the IETF.

As always, any questions or issues, please feel free to contact me, or submit
to ietf-action.

Thank you,

Glen
Glen Barney
IT Director
AMS (IETF Secretariat)


From dhc2@dcrocker.net  Mon Jul 25 11:01:12 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 51BED21F891F for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 11:01:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wecGN9PtDrNb for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 11:01:11 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id B7BAB21F86DE for <ietf@ietf.org>; Mon, 25 Jul 2011 11:01:11 -0700 (PDT)
Received: from [130.129.85.251] ([130.129.85.251]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p6PI154J008603 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Mon, 25 Jul 2011 11:01:11 -0700
Message-ID: <4E2DAF60.8030307@dcrocker.net>
Date: Mon, 25 Jul 2011 14:01:04 -0400
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: DKIM Signatures now being applied to IETF Email
References: <20110725171748.GA13506@amsl.com>
In-Reply-To: <20110725171748.GA13506@amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 25 Jul 2011 11:01:11 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 18:01:12 -0000

On 7/25/2011 1:17 PM, Glen wrote:
> I am very pleased to report that the IETF is now applying DKIM signatures
> to all outgoing list email from mailman.


I'll be presumptuous and speak on behalf of the DKIM operations community, 
rather than just myself:

   Cool!  Thanks.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From mcr@sandelman.ca  Mon Jul 25 11:05:20 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 8DE6D21F8B83 for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 11:05:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.207
X-Spam-Level: 
X-Spam-Status: No, score=0.207 tagged_above=-999 required=5 tests=[AWL=0.302,  BAYES_20=-0.74, 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 NM9W6lcAdXF8 for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 11:05:20 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 0166021F8BCC for <ietf@ietf.org>; Mon, 25 Jul 2011 11:05:19 -0700 (PDT)
Received: from marajade.sandelman.ca (unknown [130.129.23.79]) by relay.sandelman.ca (Postfix) with ESMTPS id 7D9B034132; Mon, 25 Jul 2011 14:05:00 -0400 (EDT)
Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 7AAFC980EA; Mon, 25 Jul 2011 14:05:33 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: draft-ietf-v6ops-6to4-to-historic (yet again)
In-Reply-To: <AD68A37B-4C1A-423B-AEE9-82CB61E2733C@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <AD68A37B-4C1A-423B-AEE9-82CB61E2733C@network-heretics.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Mon, 25 Jul 2011 14:05:33 -0400
Message-ID: <3012.1311617133@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
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, 25 Jul 2011 18:05:20 -0000

>>>>> "Keith" == Keith Moore <moore@network-heretics.com> writes:
    Keith> I remain strongly opposed to reclassifying 6to4 as Historic
    Keith> unless/until a better alternative appears.  Putting an
    Keith> explanation inside an informational document doesn't change
    Keith> that opposition.

+1
I note that multicast basically died when the mbone6 got decommissioned
too early.

-- 
]       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 ichiroumakino@gmail.com  Mon Jul 25 11:17:21 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 AE2DE21F8BDD for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 11:17: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 Kvdx30gFMIXo for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 11:17:21 -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 2022721F8BAD for <ietf@ietf.org>; Mon, 25 Jul 2011 11:17:21 -0700 (PDT)
Received: by yie30 with SMTP id 30so2791436yie.31 for <ietf@ietf.org>; Mon, 25 Jul 2011 11:17:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=fALGuSwDN0ht1Q01mJQXFrzqwTDYCa6TUkkD6jNs5dQ=; b=BlY4+TMCPMXmB5DAYt5T+UJrELZA3RDdM2X2th5SpkZ2az+fMIreI0Ux7+9X/H7xR1 EB+9/JgStKMti3fw23wVQURhDcFDVPtyIZoaCWDh5ogvzsD2kqu1DYKrjQLjnbjEJKL3 XyigGHopLjAulv0v+RzkLC4pnlgh+iTTSg2u0=
Received: by 10.68.46.38 with SMTP id s6mr8915521pbm.10.1311617840158; Mon, 25 Jul 2011 11:17:20 -0700 (PDT)
Received: from sjc-vpn6-633.cisco.com (128-107-239-233.cisco.com [128.107.239.233]) by mx.google.com with ESMTPS id m7sm4788628pbk.22.2011.07.25.11.17.17 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 25 Jul 2011 11:17:18 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
Date: Mon, 25 Jul 2011 14:17:14 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9273B4B7-1B8B-45CB-9000-5359BCBC740F@employees.org>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
To: Ronald Bonica <rbonica@juniper.net>
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: Mon, 25 Jul 2011 18:17:21 -0000

I'm in favor of the proposed action and the clarification of historic, =
suggested in the new section.
(I could be in _strong_ favour to nullify Keith's 'vote', although I =
hope we're not counting. ;-)), .

cheers,
Ole

On Jul 25, 2011, at 10:30 , Ronald Bonica wrote:

> Folks,
>=20
> After some discussion, the IESG is attempting to determine whether =
there is IETF consensus to do the following:
>=20
> - add a new section to draft-ietf-v6ops-6to4-to-historic
> - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL
>=20
> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 and =
convert their status to HISTORIC. It will also contain a new section =
describing what it means for RFCs 3056 and 3068 to be classified as =
HISTORIC. The new section will say that:
>=20
> - 6-to-4 should not be configured by default on any implementation =
(hosts, cpe routers, other)
> - vendors will decide whether/when 6-to-4 will be removed from =
implementations. Likewise, operators will decide whether/when 6-to-4 =
relays will be removed from their networks. The status of RFCs 3056 and =
3068 should not be interpreted as a recommendation to remove 6-to-4 at =
any particular time.
>=20
>=20
> draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While it =
clarifies the meaning of "HISTORIC" in this particular case, it does not =
set a precedent for any future case.
>=20
> Please post your views on this course of action by August 8, 2011.
>=20
>=20
>                                                                   Ron =
Bonica
>                                                                   =
<speaking as OPS Area AD>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From michel@arneill-py.sacramento.ca.us  Mon Jul 25 11:23:27 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 C3F1321F8B90 for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 11:23:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.817
X-Spam-Level: 
X-Spam-Status: No, score=-1.817 tagged_above=-999 required=5 tests=[AWL=0.448,  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 KU2KrDiBP3Tt for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 11:23:27 -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 4575A21F8B77 for <ietf@ietf.org>; Mon, 25 Jul 2011 11:23:27 -0700 (PDT)
Subject: RE: draft-ietf-v6ops-6to4-to-historic  (yet again)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 25 Jul 2011 11:23:26 -0700
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF60F@newserver.arneill-py.local>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-v6ops-6to4-to-historic  (yet again)
Thread-Index: AcxK13EXQuzfLCzMQFivvvTkow95TgAIAJog
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Ronald Bonica" <rbonica@juniper.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: Mon, 25 Jul 2011 18:23:27 -0000

> Ronald Bonica wrote:
> After some discussion, the IESG is attempting to determine whether
> there is IETF consensus to do the following:
> - add a new section to draft-ietf-v6ops-6to4-to-historic
> - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL

Opposed. I will pass on details, as I don't think I have any wording to
contribute that has not already been discussed and re-discussed.

Michel.


From amorris@amsl.com  Mon Jul 25 11:39:50 2011
Return-Path: <amorris@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42AD521F8B97 for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 11:39: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 gCFe2Z2gXD-U for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 11:39:49 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:1112:1::14]) by ietfa.amsl.com (Postfix) with ESMTP id CE5FB21F8B81 for <ietf@ietf.org>; Mon, 25 Jul 2011 11:39:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id C7ADF3A200D for <ietf@ietf.org>; Mon, 25 Jul 2011 11:39:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Eo6RWKc6akEn for <ietf@ietf.org>; Mon, 25 Jul 2011 11:39:49 -0700 (PDT)
Received: from dhcp-4795.meeting.ietf.org (unknown [130.129.71.149]) by c1a.amsl.com (Postfix) with ESMTPSA id 817293A200C for <ietf@ietf.org>; Mon, 25 Jul 2011 11:39:49 -0700 (PDT)
Message-Id: <066E00D9-B9E7-4200-AEDA-85A56352DFA0@amsl.com>
From: Alexa Morris <amorris@amsl.com>
To: IETF-Discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Reminder: Remote Participation Support for Plenary by Meetecho
Date: Mon, 25 Jul 2011 11:39:47 -0700
X-Mailer: Apple Mail (2.936)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 18:39:50 -0000

If you are participating in IETF 81 from outside of Quebec City, this  
is a reminder that Meetecho is providing remote participation support  
for both the technical and administrative plenaries. You can find more  
information online at  http://www.ietf.org/meeting/81/remote-participation.html 
  and at http://ietf81.conf.meetecho.com/.

Regards,
Alexa

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

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


From trammell@tik.ee.ethz.ch  Mon Jul 25 14:09:36 2011
Return-Path: <trammell@tik.ee.ethz.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A225D21F899F for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 14:09:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AM0MmZPLGvZr for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 14:09:35 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 7323021F8997 for <ietf@ietf.org>; Mon, 25 Jul 2011 14:09:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id C0428D9325 for <ietf@ietf.org>; Mon, 25 Jul 2011 23:09:34 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id xE6WghR2WLEU for <ietf@ietf.org>; Mon, 25 Jul 2011 23:09:34 +0200 (MEST)
Received: from dhcp-678d.meeting.ietf.org (unknown [130.129.103.141]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id C8CE0D9324 for <ietf@ietf.org>; Mon, 25 Jul 2011 23:09:33 +0200 (MEST)
From: Brian Trammell <trammell@tik.ee.ethz.ch>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: MILE side meeting, IETF81 in Quebec, Monday night July 25th
Date: Mon, 25 Jul 2011 17:08:04 -0400
References: <AE31510960917D478171C79369B660FA0E051CE712@MX06A.corp.emc.com>
To: ietf@ietf.org
Message-Id: <1ECD4FEF-B18A-46D0-BA5B-E9700419316A@tik.ee.ethz.ch>
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: Mon, 25 Jul 2011 21:09:36 -0000

Greetings,

For those interested in the MILE side meeting, it will take place right =
after the plenary, 19:30, in room 301A.

Best regards,

Brian

Begin forwarded message:

> From: <kathleen.moriarty@emc.com>
> Date: July 25, 2011 12:03:01 PM EDT
> To: <trammell@tik.ee.ethz.ch>, <ietf@ietf.org>, <saag@ietf.org>, =
<mile@ietf.org>
> Subject: RE: [mile] MILE side meeting, IETF81 in Quebec, Monday night =
July 25th
>=20
> Hello,
>=20
> Tonight's side meeting for MILE will be held in Room 301A, starting =
right after the plenary at 19:30 EST.  We plan to use the following =
bridge number for those who could not be here in person:
>=20
> Dial-in: 857.207.4204,   1, 60363236#
>=20
> Thank you,
> Kathleen & Brian
>=20
>=20
> ________________________________________

> Managed Incident Lightweight Exchange (mile)
> --------------------------------------------
>=20
> Proposed Working Group Charter
>=20
> Chairs:
>  Kathleen Moriarty <kathleen.moriarty@emc.com>
>  Brian Trammell <trammell@tik.ee.ethz.ch>
>=20
> Security Area Directors:
>  Stephen Farrell =
<stephen.farrell@cs.tcd.ie<mailto:stephen.farrell@cs.tcd.ie>>
>  Sean Turner <turners@ieca.com<mailto:turners@ieca.com>>
>=20
> Security Area Advisor:
>  Sean Turner <turners@ieca.com>
>=20
> Mailing Lists:
>  General Discussion: mile@ietf.org
>  To Subscribe:       http://www.ietf.org/mailman/listinfo/mile
>  Archive:            http://www.ietf.org/mail-archive/web/mile
>=20
> Description:
>=20
> The Managed Incident Lightweight Exchange (MILE) pre-working group =
will develop standards and extensions for the purpose of improving =
incident information sharing and handling capabilities based on the work =
developed in the IETF Extended INCident Handling (INCH) working group.  =
The Incident Object Description Exchange Format (IODEF) in RFC5070 and =
Real-time Inter-network Defense (RID) in RFC6045 were developed in the =
INCH working group by international Computer Security Incident Response =
Teams (CSIRTs) and industry to meet the needs of a global community =
interested in sharing, handling, and exchanging incident information.  =
The extensions and guidance created by the MILE working group assists =
with the daily operations of CSIRTs at an organization, service =
provider, law enforcement, and at the country level.  The application of =
IODEF and RID to interdomain incident information cooperative exchange =
and sharing has recently expanded and the need for extensions has become =
more im
> portant. Efforts continue to deploy IODEF and RID, as well as to =
extend them to support specific use cases covering reporting and =
mitigation of current threats such as anti-phishing extensions.
>=20
> An incident could be a benign configuration issue, IT incident, an =
infraction to a service level agreement (SLA), a system compromise, =
socially engineered phishing attack, or a denial-of-service (DoS) =
attack, etc..  When an incident is detected, the response may include =
simply filing a report, notification to the source of the incident, a =
request to a third party for resolution/mitigation, or a request to =
locate the source.  IODEF defines a data representation that provides a =
standard format for sharing information commonly exchanged about =
computer security incidents.  RID enables the secure exchange of =
incident related information in an IODEF format providing options for =
security, privacy, and policy setting.
>=20
> MILE leverages collaboration and sharing experiences with the work =
developed in the INCH working group which includes the data model =
detailed in the IODEF, 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 contexts. Related work, drafted =
outside of INCH will also be reviewed and includes RFC5941, Sharing =
Transaction Fraud Data.
>=20
> The MILE working group provides coordination for these various =
extension efforts to improve the capabilities for exchanging incident =
information.  MILE has several objectives with the first being a =
description a subset of IODEF focused on ease of deployment and =
applicability to current information security data sharing use cases.  =
MILE also describes a generalization of RID for secure exchange of other =
security-relevant XML formats.  MILE produces additional guidance needed =
for the successful exchange of incident information for new use cases =
according to policy, security, and privacy requirements.  Finally, MILE =
produces a document template with guidance for defining IODEF extensions =
to be followed when producing extensions to IODEF as appropriate, for:
>=20
> * labeling incident reports with data protection, data retention, and =
other 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 =
confirmed 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
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile

From brian.e.carpenter@gmail.com  Mon Jul 25 14:49:38 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 897F521F852C for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 14:49:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.613
X-Spam-Level: 
X-Spam-Status: No, score=-103.613 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 REqZo9XGLSs6 for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 14:49:37 -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 9A0D911E80C0 for <ietf@ietf.org>; Mon, 25 Jul 2011 14:49:37 -0700 (PDT)
Received: by iye7 with SMTP id 7so6263815iye.31 for <ietf@ietf.org>; Mon, 25 Jul 2011 14:49:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=hUWZaXFyv0qMV53G+G7BzHa8oKVLc2nwyM+cApjwoNs=; b=OfG5cLn6bdkY2+YEueF70eqHJrLtV+A3AoISQOOQZ8HWTq1IimjZ7hyI6tt2+ee8U+ tkz3d82+bjP0UO65gqCnSOFMb+m+El0DhzvBkjwdmK981zSZ3JPCoCC+KujSHXNRHu8f OicnSyShJf68+FCPZwhHnnPRUY45nceXPVpEE=
Received: by 10.231.83.20 with SMTP id d20mr4998120ibl.152.1311630576982; Mon, 25 Jul 2011 14:49:36 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id q4sm3381472ibb.32.2011.07.25.14.49.35 (version=SSLv3 cipher=OTHER); Mon, 25 Jul 2011 14:49:36 -0700 (PDT)
Message-ID: <4E2DE4EC.1030109@gmail.com>
Date: Tue, 26 Jul 2011 09:49:32 +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: Ronald Bonica <rbonica@juniper.net>
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 21:49:38 -0000

>  Likewise, operators will decide whether/when 6-to-4 relays will be removed from their networks.

This is, of course, an undeniable statement of fact (as it is for any other feature
of the Internet). However, it needs to be made clear that doing so *prematurely*
would penalise existing successful users of those relays, and therefore it should
only be done when there is no successful traffic through them. Which is when any
operator would remove them anyway.

Therefore, I don't see much value in this statement, and possible harm to users.
The ways to avoid such harm as far as possible are already in the RFC Editor
queue.

Regards
   Brian Carpenter

On 2011-07-26 02:30, Ronald Bonica wrote:
> Folks,
> 
> After some discussion, the IESG is attempting to determine whether there is IETF consensus to do the following:
> 
> - add a new section to draft-ietf-v6ops-6to4-to-historic
> - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL
> 
> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 and convert their status to HISTORIC. It will also contain a new section describing what it means for RFCs 3056 and 3068 to be classified as HISTORIC. The new section will say that:
> 
> - 6-to-4 should not be configured by default on any implementation (hosts, cpe routers, other)
> - vendors will decide whether/when 6-to-4 will be removed from implementations. Likewise, operators will decide whether/when 6-to-4 relays will be removed from their networks. The status of RFCs 3056 and 3068 should not be interpreted as a recommendation to remove 6-to-4 at any particular time.
> 
> 
> draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While it clarifies the meaning of "HISTORIC" in this particular case, it does not set a precedent for any future case.
> 
> Please post your views on this course of action by August 8, 2011.
> 
> 
>                                                                    Ron Bonica
>                                                                    <speaking as OPS Area AD>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 

From jnc@mercury.lcs.mit.edu  Mon Jul 25 15:05:25 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 5BF7111E80CF for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 15:05:25 -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.082,  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 KIMXcBUv4xEL for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 15:05:24 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 0453311E80C7 for <ietf@ietf.org>; Mon, 25 Jul 2011 15:05:12 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 7627518C0E1; Mon, 25 Jul 2011 18:05:12 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
Message-Id: <20110725220512.7627518C0E1@mercury.lcs.mit.edu>
Date: Mon, 25 Jul 2011 18:05:12 -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, 25 Jul 2011 22:05:25 -0000

    > From: Ronald Bonica <rbonica@juniper.net>

    > draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 and
    > convert their status to HISTORIC. 

I think we should only mark things as HISTORIC as a recognition of _what has
already happened_ out in the world, not as an attempt to _make something
happen_.

If we want to tell people to stop using a protocol, we should be direct and
produce a document that says 'this protocol should always be off by default',
or 'stop using this protocol', or 'remove this protocol from your products', or
whatever.

    > While it clarifies the meaning of "HISTORIC" in this particular case, it
    > does not set a precedent for any future case.

In other words, this document is doing something with "HISTORIC" that isn't the
normal, this is a special case. I think this is a bad idea.

	Noel

From john@jlc.net  Mon Jul 25 15:54:17 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 3EE2611E80B1 for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 15:54:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.575
X-Spam-Level: 
X-Spam-Status: No, score=-106.575 tagged_above=-999 required=5 tests=[AWL=0.024, 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 hsDqrv2-d5Fi for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 15:54:16 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 7231711E80CF for <ietf@ietf.org>; Mon, 25 Jul 2011 15:54:16 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 33AF733C25; Mon, 25 Jul 2011 18:54:16 -0400 (EDT)
Date: Mon, 25 Jul 2011 18:54:16 -0400
From: John Leslie <john@jlc.net>
To: Ronald Bonica <rbonica@juniper.net>
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
Message-ID: <20110725225416.GK57285@verdi>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
User-Agent: Mutt/1.4.1i
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, 25 Jul 2011 22:54:17 -0000

Ronald Bonica <rbonica@juniper.net> wrote:
> 
> After some discussion, the IESG is attempting to determine whether
> there is IETF consensus to do the following:
> 
> - add a new section to draft-ietf-v6ops-6to4-to-historic
> - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL

   Clearly, this is an honest effort to make 6to4-to-historic closer to
where you think a consensus might be. I do appreciate the attempt...

   ... but it feels like wandering in the weeds. :^(

   We are suffering from many differing views of what "IETF consensus"
is. IMHO, any useful definition includes that anyone who disagrees with
the "consensus" statement agrees to shut up. They may shut up almost
immediately; they may shut up after some painful appeals process; or
worst, they may only pretend to shut up and keep bringing the issue
to mind again. This last, IMHO, doesn't deserve the name "consensus".

> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 and
> convert their status to HISTORIC. It will also contain a new section
> describing what it means for RFCs 3056 and 3068 to be classified as
> HISTORIC. The new section will say that:
> 
> - 6-to-4 should not be configured by default on any implementation
>   (hosts, cpe routers, other)
> - vendors will decide whether/when 6-to-4 will be removed from
>   implementations. Likewise, operators will decide whether/when
>   6-to-4 relays will be removed from their networks. The status of
>   RFCs 3056 and 3068 should not be interpreted as a recommendation
>   to remove 6-to-4 at any particular time.

   That's a funny definition of "historic"...
> 
> draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While it
> clarifies the meaning of "HISTORIC" in this particular case, it does
> not set a precedent for any future case.

   This _is_ reminiscent of what courts do when faced with a bad law.
But courts _don't_ have the option to not enact the law in the first
place. It _is_ for them the least-worst option.

> Please post your views on this course of action by August 8, 2011.

   Speaking for myself, this proposal accomplishes nothing useful.

   I actually have no particularly strong opinion on whether RFCs
3056 and 3068 deserve to be labeled "historic" at this time. I expect
they will deserve that label within a few years; but the label feels
"optimistic" at this time.

   What I _do_ have a strong opinion on is claiming in a published
RFC that we have IETF consensus to re-classify them. I do not believe
we have such consensus. I do not believe the IESG has followed a process
reasonably aimed at judging such consensus. I don't believe the IESG
even has consensus among themselves -- though if that were what the
boilerplate would claim, I wouldn't interfere.

   At some point, we need to be willing to say, "there is no consensus
at this time," and move on.

   I absolutely do not believe that reclassifying the two RFCs as
"historic" will accomplish what the proponents claim. (Neither do I
believe it would cause world-shattering harm.)

   As a general rule, I think reclassification of _anything_ to
"historic" shouldn't gate on IETF consensus -- it's just too hard.
Instead, I'd recommend some group like the IAB make the call, with
no claim to represent "consensus" of a body so large as the IETF.

   I am probably willing to shut up in any case; but I'd be a whole
lot happier if re-classification were an IAB decision. Barring that,
perhaps the RFC calling for re-classification could follow some path
which doesn't require boilerplate which claims to represent "IETF
Consensus"

   Or, the IESG could just let this document die.

--
John Leslie <john@jlc.net>

From marka@isc.org  Mon Jul 25 17:25:07 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 26A8421F8588 for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 17:25:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.604
X-Spam-Level: 
X-Spam-Status: No, score=-2.604 tagged_above=-999 required=5 tests=[AWL=-0.005, 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 X-7TFoosQki3 for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 17:25:06 -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 7C4DF21F8513 for <ietf@ietf.org>; Mon, 25 Jul 2011 17:25:01 -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 89EE75F9987; Tue, 26 Jul 2011 00:24: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 81134216C87; Tue, 26 Jul 2011 00:24:33 +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 161441228CA2; Tue, 26 Jul 2011 10:24:31 +1000 (EST)
To: Willy Tarreau <w@1wt.eu>
From: Mark Andrews <marka@isc.org>
References: <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com> <CALiegfkshhJVUHzTD1Kka5+RjGwZ5CS2J=Qk92jfSBg6Z0VfOQ@mail.gmail.com> <C9CD680E-8D68-4380-A76F-70F41F30F877@gbiv.com> <CALiegfkFnKjP09Vijo3c_DFYn4=UZm9M-4mVuZUyBk8rzwmDCw@mail.gmail.com> <20110724191641.GC22405@1wt.eu> <644A437E-BB0D-45E9-B6C3-5EF66A811986@virtualized.org> <20110725045821.GN22405@1wt.eu>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
In-reply-to: Your message of "Mon, 25 Jul 2011 06:58:21 +0200." <20110725045821.GN22405@1wt.eu>
Date: Tue, 26 Jul 2011 10:24:31 +1000
Message-Id: <20110726002431.161441228CA2@drugs.dv.isc.org>
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, 26 Jul 2011 00:25:07 -0000

In message <20110725045821.GN22405@1wt.eu>, Willy Tarreau writes:
> On Sun, Jul 24, 2011 at 03:49:33PM -1000, David Conrad wrote:
> > [I haven't been following hybi and haven't read the draft, but as
> > this is posted to the ietf list and there are a bunch of assertions
> > here about the DNS I consider ... odd, I thought I'd chime in]
> > 
> > On Jul 24, 2011, at 8:59 AM, Willy Tarreau wrote:
> > > A lost UDP packet is not retransmitted nor signaled as lost, so the
> > > browser has to retry.
> > 
> > This sounds like a seriously broken resolver.  All resolvers I'm aware of
> > have timeouts and retry if no response is received within the timeout. A
> > resolver that gives up after a first time out is equivalent to a TCP stack
> > that doesn't retransmit a SYN.  A bug should be filed with the vendor.
> 
> What are you saying ? Your browser embeds the resolved as a library, so when
> I'm saying that "the browser has to retry", I mean the resolver part of the
> browser has to retry.
> 
> > On Jul 24, 2011, at 9:16 AM, Willy Tarreau wrote:
> > > CNAME is the exact equivalent of SRV.
> > 
> > No. According to the RFCs and most implementations, you can't have CNAME
> > with other data (A, MX, SOA, NS, etc).  With SRV, you 
> > can have anything at the same label.
> 
> This does not change anything, because the CNAME is on the hostname while
> the SRV is on the service name, so there is nothing wrong with having both.

You are missing the point.   The following is illegal though some nameservers
allow you to load the zone.

	example.com SOA ...
	example.com CNAME ...

This is not illegal

	example.com SOA
_http._tcp.example.com SRV ...

Nor is a fictional HTTP record which adds the same level of
indirection as CNAME.
 
	example.com SOA ...
	example.com HTTP <server>

> > On Jul 24, 2011, at 9:29 AM, Willy Tarreau wrote:
> > > DNS provides geolocation and proposes you the closest working datacenter.
> > 
> > >> Anyhow, don't forget that SRV is not just for failover, but also for load-balancing
> > 
> > > This is already addressed by DNS round robin and used by a lot of sites.
> > 
> > Only at the grossest level. What a client get back from a query depends on who has queried the same cache and authoritative ser
> ver and what policy the authoritative server has for returning answers.  In reality, 'round robin' is 'random'.
> 
> Yes but in practice, this randomness offers very smooth distribution.
> 
> >  This is qualitatively different than the prioritization offered by SRV.
> 
> Indeed this is different, but this does not mean there is a huge need for
> the minor improvements provided by SRV in this context.
> 
> I'm not saying that SRV is useless but that it adds little value to HTTP
> and even smaller to WS without HTTP, and comes at a non-zero cost, whatever
> people are saying. I'm also certain that if a new record were to be invented
> (eg: report the server's load in real time), there would be major proponents
> to make it mandatory for everything because it would be what would save the
> world from an upcoming disaster.

But it adds a lot of value to everyone else using the DNS.  By HTTP
clients and adminitrators abusing CNAME to achieve what SRV achieves
cleanly they cause problems elsewhere.

> I'm convinced we can find good use cases for SRV combined with either HTTP
> or WS once we admit it is optional and the user controls this option. Try
> to imagine what you could do if you knew that 50% of your visitors would
> consider your SRV records. Maybe you could use them to progressively test
> service updates. You could possibly get a better distribution, or serve
> a maintenance page to some of them during maintenance operations instead
> of leaving them in the dark. You have to think what the benefit can be
> for the user to enable the option, not how to push it down his throat.

> Regards,
> Willy
> 
> _______________________________________________
> 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  Mon Jul 25 17:40:14 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 F2BBA11E80DB for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 17:40:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.843
X-Spam-Level: 
X-Spam-Status: No, score=-9.843 tagged_above=-999 required=5 tests=[AWL=0.406,  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 qA+1F5Nn42hd for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 17:40:13 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 3810411E80B1 for <ietf@ietf.org>; Mon, 25 Jul 2011 17:40:13 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id p6Q0eBaW009071 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 26 Jul 2011 02:40:11 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201107260040.p6Q0eAQU009072@fs4113.wdf.sap.corp>
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
To: rbonica@juniper.net (Ronald Bonica)
Date: Tue, 26 Jul 2011 02:40:10 +0200 (MEST)
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> from "Ronald Bonica" at Jul 25, 11 10:30:46 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: Tue, 26 Jul 2011 00:40:14 -0000

Ronald Bonica wrote:
> 
> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 and
> convert their status to HISTORIC. It will also contain a new section
> describing what it means for RFCs 3056 and 3068 to be classified
> as HISTORIC.

I'm strongly opposed.  Discussion is in the archives.

-Martin

From mohta@necom830.hpcl.titech.ac.jp  Mon Jul 25 18:01:25 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 C784921F8B80 for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 18:01:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.076
X-Spam-Level: 
X-Spam-Status: No, score=-0.076 tagged_above=-999 required=5 tests=[AWL=0.014,  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 yqO56ZbJ5Kxg for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 18:01:25 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id EF0A821F8B81 for <ietf@ietf.org>; Mon, 25 Jul 2011 18:01:24 -0700 (PDT)
Received: (qmail 98401 invoked from network); 26 Jul 2011 01:20:49 -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; 26 Jul 2011 01:20:49 -0000
Message-ID: <4E2E11C3.2000603@necom830.hpcl.titech.ac.jp>
Date: Tue, 26 Jul 2011 10:00:51 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com> <CALiegfkshhJVUHzTD1Kka5+RjGwZ5CS2J=Qk92jfSBg6Z0VfOQ@mail.gmail.com> <C9CD680E-8D68-4380-A76F-70F41F30F877@gbiv.com> <CALiegfkFnKjP09Vijo3c_DFYn4=UZm9M-4mVuZUyBk8rzwmDCw@mail.gmail.com> <20110724191641.GC22405@1wt.eu> <644A437E-BB0D-45E9-B6C3-5EF66A811986@virtualized.org> <20110725045821.GN22405@1wt.eu>
In-Reply-To: <20110725045821.GN22405@1wt.eu>
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: Tue, 26 Jul 2011 01:01:25 -0000

Willy Tarreau wrote:

> What are you saying ? Your browser embeds the resolved as a library, so when
> I'm saying that "the browser has to retry", I mean the resolver part of the
> browser has to retry.

You should mean that the browser can control behavior of the
resolver.

If the resolver in the browser retries within a hundred ms:

> So yes, it can take several seconds to just resolve a host and then
> only a few hundreds of ms to retrieve
> the objects. I've observed it.

won't happen.

						Masataka Ohta

From huitema@microsoft.com  Mon Jul 25 18:02:00 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 8103D11E80B0 for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 18:02:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.716
X-Spam-Level: 
X-Spam-Status: No, score=-10.716 tagged_above=-999 required=5 tests=[AWL=-0.117, 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 8dXrvl7uF7Ne for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 18:02:00 -0700 (PDT)
Received: from smtp.microsoft.com (mailb.microsoft.com [131.107.115.215]) by ietfa.amsl.com (Postfix) with ESMTP id 03B3621F8B89 for <ietf@ietf.org>; Mon, 25 Jul 2011 18:01:59 -0700 (PDT)
Received: from TK5EX14MLTC101.redmond.corp.microsoft.com (157.54.79.178) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 25 Jul 2011 18:01:59 -0700
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14MLTC101.redmond.corp.microsoft.com (157.54.79.178) with Microsoft SMTP Server (TLS) id 14.1.323.2; Mon, 25 Jul 2011 18:01:59 -0700
Received: from TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com ([169.254.1.52]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi id 14.01.0289.008; Mon, 25 Jul 2011 18:01:58 -0700
From: Christian Huitema <huitema@microsoft.com>
To: Ronald Bonica <rbonica@juniper.net>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: draft-ietf-v6ops-6to4-to-historic  (yet again)
Thread-Topic: draft-ietf-v6ops-6to4-to-historic  (yet again)
Thread-Index: AcxK13EXQuzfLCzMQFivvvTkow95TgAV+6jA
Date: Tue, 26 Jul 2011 01:01:57 +0000
Message-ID: <22F6318E46E26B498ABC828879B08D4F1D272D@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.90]
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, 26 Jul 2011 01:02:00 -0000

> After some discussion, the IESG is attempting to determine whether there =
is IETF consensus to do the following:
>
> - add a new section to draft-ietf-v6ops-6to4-to-historic
> - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL
>
> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 and co=
nvert their status to HISTORIC. It will also contain > a new section descri=
bing what it means for RFCs 3056 and 3068 to be classified as HISTORIC. The=
 new section will say that:

I do not think this is a good idea, and I am certainly not part of the "con=
sensus."

-- Christian Huitema



From marka@isc.org  Mon Jul 25 18:10:03 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 EACAA21F871E for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 18:10:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.604
X-Spam-Level: 
X-Spam-Status: No, score=-2.604 tagged_above=-999 required=5 tests=[AWL=-0.005, 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 c1I5QkrBqdA4 for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 18:10:03 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 1B65221F847D for <ietf@ietf.org>; Mon, 25 Jul 2011 18:10:03 -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 6D1605F998A; Tue, 26 Jul 2011 01:09: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 AF779216C84; Tue, 26 Jul 2011 01:09: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 B58A812292A8; Tue, 26 Jul 2011 11:09:27 +1000 (EST)
To: Christian Huitema <huitema@microsoft.com>
From: Mark Andrews <marka@isc.org>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <22F6318E46E26B498ABC828879B08D4F1D272D@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
Subject: Re: draft-ietf-v6ops-6to4-to-historic (yet again)
In-reply-to: Your message of "Tue, 26 Jul 2011 01:01:57 GMT." <22F6318E46E26B498ABC828879B08D4F1D272D@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
Date: Tue, 26 Jul 2011 11:09:27 +1000
Message-Id: <20110726010927.B58A812292A8@drugs.dv.isc.org>
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, 26 Jul 2011 01:10:04 -0000

In message <22F6318E46E26B498ABC828879B08D4F1D272D@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>, Christian Huitema writes
:
> > After some discussion, the IESG is attempting to determine whether there is IETF consensus to do the following:
> >
> > - add a new section to draft-ietf-v6ops-6to4-to-historic
> > - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL
> >
> > draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 and convert their status to HISTORIC. It will also contain >
>  a new section describing what it means for RFCs 3056 and 3068 to be classified as HISTORIC. The new section will say that:
> 
> I do not think this is a good idea, and I am certainly not part of the "consensus."

Seconded.
 
> -- Christian Huitema
> 
> 
> _______________________________________________
> 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 cb.list6@gmail.com  Mon Jul 25 18:12:58 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 E6EB021F874E for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 18:12:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.246
X-Spam-Level: 
X-Spam-Status: No, score=-3.246 tagged_above=-999 required=5 tests=[AWL=0.352,  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 HSAIS79AThPy for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 18:12:58 -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 2DFA921F874C for <ietf@ietf.org>; Mon, 25 Jul 2011 18:12:57 -0700 (PDT)
Received: by wwe5 with SMTP id 5so3111075wwe.13 for <ietf@ietf.org>; Mon, 25 Jul 2011 18:12:57 -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=+15dAutLvyJtdCeFUeAeY21BGn21Hp8JLA/D0/Wb0A0=; b=BFJmU4PnT96K8mxJEcfEgTESBVbkB72J3QB94bR2V6aZ8k0IJoFxOTuAnlqTIYoXz0 VsI+wOFdGnHrAlp4pHEWqWndNwjVmjoBMMbTLEhLVIG4uoyhvbXPAtF0kGxtlSOMJzK0 l19TlirUTQEx/TVur1+rZci28vny3dl3DcMnk=
MIME-Version: 1.0
Received: by 10.216.62.3 with SMTP id x3mr1003884wec.77.1311642777296; Mon, 25 Jul 2011 18:12:57 -0700 (PDT)
Received: by 10.216.161.136 with HTTP; Mon, 25 Jul 2011 18:12:57 -0700 (PDT)
Received: by 10.216.161.136 with HTTP; Mon, 25 Jul 2011 18:12:57 -0700 (PDT)
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
Date: Mon, 25 Jul 2011 18:12:57 -0700
Message-ID: <CAD6AjGRcvi9wO6wZvWaaqgv9Xx9WYB_HZ9+QvYCmJk3Eg=Z3Qw@mail.gmail.com>
Subject: Re: draft-ietf-v6ops-6to4-to-historic (yet again)
From: Cameron Byrne <cb.list6@gmail.com>
To: Ronald Bonica <rbonica@juniper.net>
Content-Type: multipart/alternative; boundary=000e0ce00656d01e3e04a8eea158
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, 26 Jul 2011 01:12:59 -0000

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

I approve of this approach.

--000e0ce00656d01e3e04a8eea158
Content-Type: text/html; charset=ISO-8859-1

<p>I approve of this approach. </p>

--000e0ce00656d01e3e04a8eea158--

From faber@isi.edu  Mon Jul 25 19:10:12 2011
Return-Path: <faber@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCA8021F8559 for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 19:10:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wKyaeVPhOqEr for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 19:10:11 -0700 (PDT)
Received: from zod.isi.edu (zod.isi.edu [128.9.168.221]) by ietfa.amsl.com (Postfix) with ESMTP id 6FD6B21F8B39 for <ietf@ietf.org>; Mon, 25 Jul 2011 19:09:44 -0700 (PDT)
Received: from zod.isi.edu (localhost [127.0.0.1]) by zod.isi.edu (8.14.5/8.14.5) with ESMTP id p6Q29RXa086377; Mon, 25 Jul 2011 19:09:28 -0700 (PDT) (envelope-from faber@isi.edu)
Date: Mon, 25 Jul 2011 20:08:43 -0600
From: Ted Faber <faber@isi.edu>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
Message-ID: <20110726020841.GA8802@zod.isi.edu>
References: <20110725220512.7627518C0E1@mercury.lcs.mit.edu>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HlL+5n6rz5pIUxbD"
Content-Disposition: inline
In-Reply-To: <20110725220512.7627518C0E1@mercury.lcs.mit.edu>
X-url: http://www.isi.edu/~faber
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 02:10:12 -0000

--HlL+5n6rz5pIUxbD
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jul 25, 2011 at 06:05:12PM -0400, Noel Chiappa wrote:
>     > From: Ronald Bonica <rbonica@juniper.net>
>=20
>     > draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 =
and
>     > convert their status to HISTORIC.=20
>=20
> I think we should only mark things as HISTORIC as a recognition of _what =
has
> already happened_ out in the world, not as an attempt to _make something
> happen_.

What he said.
--=20
Ted Faber
http://www.isi.edu/~faber           PGP: http://www.isi.edu/~faber/pubkeys.=
asc
Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#=
SIG

--HlL+5n6rz5pIUxbD
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

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

iEYEARECAAYFAk4uIakACgkQaUz3f+Zf+XvNYgCg0TWkrZ/cCHtTvdq6gxWfuGoI
+i8AoPeOBGoTUPExipQz5fc2j8JWsatj
=Je47
-----END PGP SIGNATURE-----

--HlL+5n6rz5pIUxbD--

From brian.e.carpenter@gmail.com  Mon Jul 25 20:08: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 94A6121F865F for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 20:08:47 -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 EIWJlQKJXat9 for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 20:08:47 -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 D524021F8541 for <ietf@ietf.org>; Mon, 25 Jul 2011 20:08:46 -0700 (PDT)
Received: by qwc23 with SMTP id 23so9551qwc.31 for <ietf@ietf.org>; Mon, 25 Jul 2011 20:08:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=TZeaPOWo6uWt5PwsgHWYKI11sAHVX2qYnkgRU3Btwbk=; b=MFvbXMGMJbJZI5Jl9IwfSe4QRHIAVdJjz+YR1ppmzRi9RMseKoLl1y14MrDh5qgD/7 It4CSFxCrP+H9aZedmWMjb7ekeBmUxkdMuy0B/K7mbBRN+JHry8bt517i4kTEsXsLQZm WQkbpVvrEM6ppZFUfjH00Sb+mtxjVzGEcXb/s=
Received: by 10.224.188.210 with SMTP id db18mr3959417qab.317.1311649726221; Mon, 25 Jul 2011 20:08:46 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id d12sm40699qcd.14.2011.07.25.20.08.44 (version=SSLv3 cipher=OTHER); Mon, 25 Jul 2011 20:08:45 -0700 (PDT)
Message-ID: <4E2E2FBA.1030304@gmail.com>
Date: Tue, 26 Jul 2011 15:08:42 +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: Ronald Bonica <rbonica@juniper.net>
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com>
In-Reply-To: <4E2DE4EC.1030109@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 03:08:47 -0000

To be clear, I'd like to see exact proposed text before expressing
support for the proposal. The trick is to get 6to4 disabled by default
at the user end, without disabling it for users who are getting good
service from it.

Regards
   Brian

On 2011-07-26 09:49, Brian E Carpenter wrote:
>>  Likewise, operators will decide whether/when 6-to-4 relays will be removed from their networks.
> 
> This is, of course, an undeniable statement of fact (as it is for any other feature
> of the Internet). However, it needs to be made clear that doing so *prematurely*
> would penalise existing successful users of those relays, and therefore it should
> only be done when there is no successful traffic through them. Which is when any
> operator would remove them anyway.
> 
> Therefore, I don't see much value in this statement, and possible harm to users.
> The ways to avoid such harm as far as possible are already in the RFC Editor
> queue.
> 
> Regards
>    Brian Carpenter
> 
> On 2011-07-26 02:30, Ronald Bonica wrote:
>> Folks,
>>
>> After some discussion, the IESG is attempting to determine whether there is IETF consensus to do the following:
>>
>> - add a new section to draft-ietf-v6ops-6to4-to-historic
>> - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL
>>
>> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 and convert their status to HISTORIC. It will also contain a new section describing what it means for RFCs 3056 and 3068 to be classified as HISTORIC. The new section will say that:
>>
>> - 6-to-4 should not be configured by default on any implementation (hosts, cpe routers, other)
>> - vendors will decide whether/when 6-to-4 will be removed from implementations. Likewise, operators will decide whether/when 6-to-4 relays will be removed from their networks. The status of RFCs 3056 and 3068 should not be interpreted as a recommendation to remove 6-to-4 at any particular time.
>>
>>
>> draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While it clarifies the meaning of "HISTORIC" in this particular case, it does not set a precedent for any future case.
>>
>> Please post your views on this course of action by August 8, 2011.
>>
>>
>>                                                                    Ron Bonica
>>                                                                    <speaking as OPS Area AD>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>
> 

From michel@arneill-py.sacramento.ca.us  Mon Jul 25 20:25:54 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 E421121F85AB for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 20:25:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.929
X-Spam-Level: 
X-Spam-Status: No, score=-1.929 tagged_above=-999 required=5 tests=[AWL=0.336,  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 GhfI1H6BzXx2 for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 20:25:54 -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 68A9721F85AA for <ietf@ietf.org>; Mon, 25 Jul 2011 20:25:54 -0700 (PDT)
Subject: RE: draft-ietf-v6ops-6to4-to-historic  (yet again)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 25 Jul 2011 20:25:53 -0700
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF614@newserver.arneill-py.local>
In-Reply-To: <4E2E2FBA.1030304@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-v6ops-6to4-to-historic  (yet again)
Thread-Index: AcxLQVf4Zgt/kdnmSXe8AxHxiTjR3wAAHXwg
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net><4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>, "Ronald Bonica" <rbonica@juniper.net>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 03:25:55 -0000

Brian,

> Brian E Carpenter wrote:
> To be clear, I'd like to see exact proposed text before
> expressing support for the proposal. The trick is to get
> 6to4 disabled by default at the user end, without disabling
> it for users who are getting good service from it.

Although I commend Ron from trying "something else", I think this
particular approach is doomed to fail. Maybe I'm reading the list wrong,
but I think the sticky point here is the "historic" thing, and nothing
short of removing that part will significantly change the mindset of
people who oppose it.

Have you considered a newer revision of the 6-to-4 RFCs that would
obsolete the current ones and add that 6-to-4 should be disabled by
default? That could reach consensus.

Michel.


From randy_presuhn@mindspring.com  Mon Jul 25 20:45:11 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 75EEB21F865B for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 20:45:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.999
X-Spam-Level: 
X-Spam-Status: No, score=-99.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0ecH7kL8mJ4y for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 20:45:10 -0700 (PDT)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by ietfa.amsl.com (Postfix) with ESMTP id D657D21F863C for <ietf@ietf.org>; Mon, 25 Jul 2011 20:45:10 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=A4vebFVZx8aZVMbY8/MWPTxNFdqEoetBAuxd+Oq75X1iQ/VwuNB23GXSGrpaWr6x; 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.224.236] (helo=oemcomputer) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1QlYZy-000470-5K for ietf@ietf.org; Mon, 25 Jul 2011 23:45:10 -0400
Message-ID: <000e01cc4b47$35f34b80$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>
References: <20110725220512.7627518C0E1@mercury.lcs.mit.edu>
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
Date: Mon, 25 Jul 2011 20:50:48 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8887f779e183b2ee288894aefd439c29b5ea2b15ff422660d09350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.30.224.236
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 03:45:11 -0000

Hi -

> From: "Noel Chiappa" <jnc@mercury.lcs.mit.edu>
> To: <ietf@ietf.org>
> Cc: <jnc@mercury.lcs.mit.edu>
> Sent: Monday, July 25, 2011 3:05 PM
> Subject: Re: draft-ietf-v6ops-6to4-to-historic (yet again)
...
> I think we should only mark things as HISTORIC as a recognition of _what has
> already happened_ out in the world, not as an attempt to _make something
> happen_.
...

Though I think this is a reasonable position, there are examples from
history, such as the "historicization" of RFC 1227, that clearly demonstrate
that the IETF has historically not consistently maintained this position.

Randy


From marka@isc.org  Mon Jul 25 20:51:43 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 B6A2311E8077; Mon, 25 Jul 2011 20:51:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.604
X-Spam-Level: 
X-Spam-Status: No, score=-2.604 tagged_above=-999 required=5 tests=[AWL=-0.005, 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 rOnddGsdtFQ5; Mon, 25 Jul 2011 20:51:43 -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 06AAF11E8072; Mon, 25 Jul 2011 20:51:43 -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 2166C5F98F8; Tue, 26 Jul 2011 03:51:32 +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 5F36D216C89; Tue, 26 Jul 2011 03:51:00 +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 27D9F122A760; Tue, 26 Jul 2011 13:50:57 +1000 (EST)
To: iesg@ietf.org
From: Mark Andrews <marka@isc.org>
Subject: IPv6 Advanced Socket API and POSIX
Date: Tue, 26 Jul 2011 13:50:57 +1000
Message-Id: <20110726035057.27D9F122A760@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, 26 Jul 2011 03:51:43 -0000

Could the IESG please negotiate with Opengroup to get the IPv6
Advanced Socket API included into the next POSIX revision.

RFC 2133 "Basic Socket Interface Extensions for IPv6" (now RFC 2553)
and RFC 2292 "IPv6 Advanced Socket API" (now RFC 3542) were designed
to work together as a single API.  POSIX however only includes the
Basic Socket Interface Extensions for IPv6 in its specification.

This has resulted in operating system vendors being force to hide
the IPv6 Advanced Socket API namespace to achieve POSIX compliance
and multiple methods being independently developed to address issues
addressed by the IPv6 Advanced Socket API.

As a result of this application developers are left in the unenviable
place of having to work out how to expose the IPv6 Advanced Socket
API and also work out what other APIs have been developed to
essentially do what the IPv6 Advanced Socket API does.

I'm aware of 3 different APIs to force IPv6 fragmentation in the
node and multiple different methods to expose the parts of the IPv6
Advanced Socket API that have been implemented.

One can't write a reliable authoritative IPv6 nameserver using just
the Basic Socket Interface Extensions for IPv6.  A nameserver needs
to use some of the functionality in the IPv6 Advanced Socket API
to deal with the way IPv6 fragments packets.

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

From evnikita2@gmail.com  Mon Jul 25 20:53: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 AA93E11E8101 for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 20:53:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.504
X-Spam-Level: 
X-Spam-Status: No, score=-3.504 tagged_above=-999 required=5 tests=[AWL=0.095,  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 Vyu-6+jT0Pk3 for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 20:53:10 -0700 (PDT)
Received: from mail-ey0-f176.google.com (mail-ey0-f176.google.com [209.85.215.176]) by ietfa.amsl.com (Postfix) with ESMTP id ED89D11E8072 for <ietf@ietf.org>; Mon, 25 Jul 2011 20:53:09 -0700 (PDT)
Received: by eya28 with SMTP id 28so60381eya.21 for <ietf@ietf.org>; Mon, 25 Jul 2011 20:53:09 -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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=kNZ7znXR5STFMGUARxmIokBemRirfCbyt1aYDgQTQLo=; b=xiiDAfblSfC5egCtnY2YQhknTREr5v+aXB+GIApyvQLSm6F/mW2yA+JPMoxdCpnDEf 5ExNnhkHLnGO8FQZs/hsfH43xQcIvS2mJPWFrM3RkE2aGYgsnKtU8Apqfu9EY8pT+37I 4JyiKMRYO2udGcHdyAJpc4F9qPJoRoCaMy0Uk=
Received: by 10.205.83.194 with SMTP id ah2mr1635152bkc.49.1311652388168; Mon, 25 Jul 2011 20:53:08 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id i1sm19856bku.21.2011.07.25.20.53.06 (version=SSLv3 cipher=OTHER); Mon, 25 Jul 2011 20:53:07 -0700 (PDT)
Message-ID: <4E2E3A4C.1050803@gmail.com>
Date: Tue, 26 Jul 2011 06:53:48 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
References: <20110725220512.7627518C0E1@mercury.lcs.mit.edu>
In-Reply-To: <20110725220512.7627518C0E1@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 03:53:10 -0000

26.07.2011 1:05, Noel Chiappa wrote:
>      >  From: Ronald Bonica<rbonica@juniper.net>
>      >  While it clarifies the meaning of "HISTORIC" in this particular case, it
>      >  does not set a precedent for any future case.
>
> In other words, this document is doing something with "HISTORIC" that isn't the
> normal, this is a special case. I think this is a bad idea.
+1.  Should Historic status definition be clarified, it should be done 
in a separate document, or in the revision of RFC 2026.  See my previous 
message.

Mykyta
>
> 	Noel
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


From hsantos@isdg.net  Mon Jul 25 21:07:15 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 CC25611E80BB for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 21:07:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.692
X-Spam-Level: 
X-Spam-Status: No, score=-3.692 tagged_above=-999 required=5 tests=[AWL=-1.956, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 kIeLhSNzJpQM for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 21:07:15 -0700 (PDT)
Received: from groups.winserver.com (catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id BFCBB11E8072 for <ietf@ietf.org>; Mon, 25 Jul 2011 21:07:14 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=999; t=1311653231; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=dxA2fclY+kddyXScd3ZD5OR4OZE=; b=uReCHnudT32AVKiWb5Ut TOedK0CiEJSuMU7DpriTJSBB49b8Yb2xrPb8Gkt/ED5f9tKmV7tCD33Y+JpzTeFW qGC8tNsegg+TXmJh2QViwcvzIVcVaJD/i7VVJ18m/LNkz/v7y/P5kip///sPzEwD QBSz8ThfNpiwY+ZBL4yTiKM=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Tue, 26 Jul 2011 00:07:11 -0400
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 108724542.18114.4996; Tue, 26 Jul 2011 00:07:11 -0400
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Tue, 26 Jul 2011 00:02:54 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1080012502.637.7852; Tue, 26 Jul 2011 00:02:53 -0400
Message-ID: <4E2E3D93.6040902@isdg.net>
Date: Tue, 26 Jul 2011 00:07:47 -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: Glen <glen@amsl.com>
Subject: Re: DKIM Signatures now being applied to IETF Email
References: <20110725171748.GA13506@amsl.com>
In-Reply-To: <20110725171748.GA13506@amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 04:07:15 -0000

Cool beans.  Message as verified here.  The good thing is that it 
finally resolved the corruption of distributed original signed mail on 
the ietf list server with its extra line at the top!

Glen wrote:
> All -
> 
> I am very pleased to report that the IETF is now applying DKIM signatures
> to all outgoing list email from mailman.
> 
> Many thanks to Murray Kucherawy, lead author of OpenDKIM, for doing the work
> to set up OpenDKIM on the IETF servers and getting it to work.  He made the
> process painless, and we express our thanks to him for his service to the IETF.
> 
> As always, any questions or issues, please feel free to contact me, or submit
> to ietf-action.
> 
> Thank you,
> 
> Glen
> Glen Barney
> IT Director
> AMS (IETF Secretariat)
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
> 

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com





From evnikita2@gmail.com  Mon Jul 25 21:15: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 B2DD021F8B00 for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 21:15:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.505
X-Spam-Level: 
X-Spam-Status: No, score=-3.505 tagged_above=-999 required=5 tests=[AWL=0.094,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f-6md-P6UwiV for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 21:15:32 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id D7B2021F8AD8 for <ietf@ietf.org>; Mon, 25 Jul 2011 21:15:31 -0700 (PDT)
Received: by ewy19 with SMTP id 19so48265ewy.31 for <ietf@ietf.org>; Mon, 25 Jul 2011 21:15:30 -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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=LfbYDfOZa0zcApdEM+RitsOMA9R3q6HmqjsUhf5u0s8=; b=tOed33UblQUhLnZZMy3BRc9vDkae1dlneJEtDgLaTyU8W8fvgTnpfV0hbmtRaZActS tIS+ympEaIrj9z/3ENVSY1DmaeWkKJROy5URpaIXkiJEYMZWSJoHk/nfRzWEM5NZhh20 VysWfga9DHKxqbmxFa8NLBqeKGvzZmHjEJmfI=
Received: by 10.204.240.144 with SMTP id la16mr1670622bkb.271.1311653730575; Mon, 25 Jul 2011 21:15:30 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id r24sm22192bkr.59.2011.07.25.21.15.29 (version=SSLv3 cipher=OTHER); Mon, 25 Jul 2011 21:15:29 -0700 (PDT)
Message-ID: <4E2E3F8B.6070609@gmail.com>
Date: Tue, 26 Jul 2011 07:16:11 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.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: Tue, 26 Jul 2011 04:15:32 -0000

Hello,

I am not an expert in the questions of 6to4, but unless there are strong 
arguments claiming that this technology is not used any more, 
reclassification isn't appropriate.  Discouraging implementation/use of 
the protocol is not a purpose of Historic, it is to mark what already 
no-one uses.  It is only possible to determine when the obvious absence 
of previous and current interest in the technology is determined by the 
community, such as eg. SiFTP, RFC 913.  I don't see such community's 
vision on 6to4, and therefore the document may not progress further 
unless strong community consensus is built.

Mykyta Yevstifeyev

25.07.2011 17:30, Ronald Bonica wrote:
> Folks,
>
> After some discussion, the IESG is attempting to determine whether there is IETF consensus to do the following:
>
> - add a new section to draft-ietf-v6ops-6to4-to-historic
> - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL
>
> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 and convert their status to HISTORIC. It will also contain a new section describing what it means for RFCs 3056 and 3068 to be classified as HISTORIC. The new section will say that:
>
> - 6-to-4 should not be configured by default on any implementation (hosts, cpe routers, other)
> - vendors will decide whether/when 6-to-4 will be removed from implementations. Likewise, operators will decide whether/when 6-to-4 relays will be removed from their networks. The status of RFCs 3056 and 3068 should not be interpreted as a recommendation to remove 6-to-4 at any particular time.
>
>
> draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While it clarifies the meaning of "HISTORIC" in this particular case, it does not set a precedent for any future case.
>
> Please post your views on this course of action by August 8, 2011.
>
>
>                                                                     Ron Bonica
>                                                                     <speaking as OPS Area AD>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


From hsantos@isdg.net  Mon Jul 25 21:19:09 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 BF6C321F8B36 for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 21:19:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.969
X-Spam-Level: 
X-Spam-Status: No, score=-2.969 tagged_above=-999 required=5 tests=[AWL=-2.434, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, J_CHICKENPOX_44=0.6, J_CHICKENPOX_63=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 dHbwpGrEKIzN for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 21:19:09 -0700 (PDT)
Received: from groups.winserver.com (catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id D477221F8B16 for <ietf@ietf.org>; Mon, 25 Jul 2011 21:19:08 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1879; t=1311653947; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=a8Y2IW5vjsFQao4quzPngOUxZBE=; b=tuzmImjXrAny8Mipoiha 1NIWG4s2/oS47iOPfrD4xiULmvgK0Kp3CfsYF/DHdhraVTqf7/tFZcra+YOuJFZx 3jArz2xSsIWHHzB+5KvKbeeehmiv2ip7sk3W9+93tUpVW9zWonqCiUl0YXeo0/5Y RYxv0VgF74cu7apaNMIYEFI=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Tue, 26 Jul 2011 00:19:07 -0400
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 109439713.18136.444; Tue, 26 Jul 2011 00:19:06 -0400
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Tue, 26 Jul 2011 00:14:46 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1080725112.639.7200; Tue, 26 Jul 2011 00:14:46 -0400
Message-ID: <4E2E405C.9040507@isdg.net>
Date: Tue, 26 Jul 2011 00:19:40 -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@ietf.org
Subject: Re: DKIM Signatures now being applied to IETF Email
References: <20110725171748.GA13506@amsl.com> <4E2E3D93.6040902@isdg.net>
In-Reply-To: <4E2E3D93.6040902@isdg.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 04:19:09 -0000

But the original destroyed signature from the author is not stripped.

Authentication-Results: dkim.winserver.com;
  dkim=pass header.d=ietf.org header.s=ietf1 header.i=ietf.org;
  adsp=fail policy=all author.d=isdg.net asl.d=ietf.org (unauthorized 
signer);
  dkim=fail (DKIM_SIGNATURE_BAD) header.d=isdg.net header.s=tms1 
header.i=isdg.net;
  adsp=pass policy=all author.d=isdg.net signer.d=isdg.net 
(originating signer);

It would be nice for the list server to remove original signatures the 
list will destroy in its resigning process.  That may be an OpenDKIM 
option.

What I need to do now also is authorized IETF.ORG as a valid 3rd party 
signer for the ISDG.NET domain.  This is done by adding ADSP/ATPS 
record using this wizard:
http://www.winserver.com/public/wcadsp/wcadsp.wct



Hector Santos wrote:
> Cool beans.  Message as verified here.  The good thing is that it 
> finally resolved the corruption of distributed original signed mail on 
> the ietf list server with its extra line at the top!
> 
> Glen wrote:
>> All -
>>
>> I am very pleased to report that the IETF is now applying DKIM signatures
>> to all outgoing list email from mailman.
>>
>> Many thanks to Murray Kucherawy, lead author of OpenDKIM, for doing 
>> the work
>> to set up OpenDKIM on the IETF servers and getting it to work.  He 
>> made the
>> process painless, and we express our thanks to him for his service to 
>> the IETF.
>>
>> As always, any questions or issues, please feel free to contact me, or 
>> submit
>> to ietf-action.
>>
>> Thank you,
>>
>> Glen
>> Glen Barney
>> IT Director
>> AMS (IETF Secretariat)
>>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>
>>
> 

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com





From samita.chakrabarti@ericsson.com  Mon Jul 25 22:19:22 2011
Return-Path: <samita.chakrabarti@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 0B33721F8B3C; Mon, 25 Jul 2011 22:19:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.742
X-Spam-Level: 
X-Spam-Status: No, score=-6.742 tagged_above=-999 required=5 tests=[AWL=-0.143, 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 VZa-axisD3g9; Mon, 25 Jul 2011 22:19:21 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by ietfa.amsl.com (Postfix) with ESMTP id 627F221F8B66; Mon, 25 Jul 2011 22:19:21 -0700 (PDT)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p6Q5JJRv017250; Tue, 26 Jul 2011 00:19:20 -0500
Received: from EUSAACMS0715.eamcs.ericsson.se ([169.254.1.121]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Tue, 26 Jul 2011 01:19:13 -0400
From: Samita Chakrabarti <samita.chakrabarti@ericsson.com>
To: Mark Andrews <marka@isc.org>, "iesg@ietf.org" <iesg@ietf.org>
Date: Tue, 26 Jul 2011 01:19:09 -0400
Subject: RE: IPv6 Advanced Socket API and POSIX
Thread-Topic: IPv6 Advanced Socket API and POSIX
Thread-Index: AcxLR1vnPFFUkKsbQWm3YbDqWmgaVgAC16gg
Message-ID: <16D60F43CA0B724F8052D7E9323565D71E6732A226@EUSAACMS0715.eamcs.ericsson.se>
References: <20110726035057.27D9F122A760@drugs.dv.isc.org>
In-Reply-To: <20110726035057.27D9F122A760@drugs.dv.isc.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: "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, 26 Jul 2011 05:19:22 -0000

=20
In addition, RFC 5014 (IPv6 Socket API for source address selection) would =
be useful to include into the next POSIX revision. This document allows app=
lications to choose a source address when default source address selection =
is in place at the IP stack.

Thanks,
-Samita
-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Mar=
k Andrews
Sent: Monday, July 25, 2011 8:51 PM
To: iesg@ietf.org
Cc: ietf@ietf.org
Subject: IPv6 Advanced Socket API and POSIX


Could the IESG please negotiate with Opengroup to get the IPv6 Advanced Soc=
ket API included into the next POSIX revision.

RFC 2133 "Basic Socket Interface Extensions for IPv6" (now RFC 2553) and RF=
C 2292 "IPv6 Advanced Socket API" (now RFC 3542) were designed to work toge=
ther as a single API.  POSIX however only includes the Basic Socket Interfa=
ce Extensions for IPv6 in its specification.

This has resulted in operating system vendors being force to hide the IPv6 =
Advanced Socket API namespace to achieve POSIX compliance and multiple meth=
ods being independently developed to address issues addressed by the IPv6 A=
dvanced Socket API.

As a result of this application developers are left in the unenviable place=
 of having to work out how to expose the IPv6 Advanced Socket API and also =
work out what other APIs have been developed to essentially do what the IPv=
6 Advanced Socket API does.

I'm aware of 3 different APIs to force IPv6 fragmentation in the node and m=
ultiple different methods to expose the parts of the IPv6 Advanced Socket A=
PI that have been implemented.

One can't write a reliable authoritative IPv6 nameserver using just the Bas=
ic Socket Interface Extensions for IPv6.  A nameserver needs to use some of=
 the functionality in the IPv6 Advanced Socket API to deal with the way IPv=
6 fragments packets.

Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE:	+61 2 9871 4742		         INTERNET: marka@isc.org
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

From rogerj@gmail.com  Tue Jul 26 00:53:50 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 83FEC21F8C36 for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 00:53:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.217
X-Spam-Level: 
X-Spam-Status: No, score=-3.217 tagged_above=-999 required=5 tests=[AWL=0.082,  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 WLk7iDTIKnrQ for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 00:53:49 -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 4267021F8C35 for <ietf@ietf.org>; Tue, 26 Jul 2011 00:53:49 -0700 (PDT)
Received: by wwe5 with SMTP id 5so122966wwe.13 for <ietf@ietf.org>; Tue, 26 Jul 2011 00:53:48 -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:content-transfer-encoding; bh=9cd5Xbi54EIubAww1XS97rOYrs/m4msMw66asoJxg8M=; b=uk+othOm8By+JhCAUjD+CSLIQHihetdHXmpRy07PVBzHt2FDRTw6Rsk7TVZTaBd5KA F0MlJJKxk2CdXz/y6uMMfJmhVkHdL8jzgyk6ZJSfi70U04w4fcYJBPra9rRrue+4Sizm 0EZ5d/VZCy0d4I1mkhub/JV0zlNJCUv/GwG5A=
MIME-Version: 1.0
Received: by 10.227.202.14 with SMTP id fc14mr3906wbb.83.1311666828145; Tue, 26 Jul 2011 00:53:48 -0700 (PDT)
Received: by 10.227.155.197 with HTTP; Tue, 26 Jul 2011 00:53:47 -0700 (PDT)
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
Date: Tue, 26 Jul 2011 09:53:47 +0200
Message-ID: <CAKFn1SFep4nptj42jRkuEK6FWB=dkYY3Y-mJhQ0sE7qdC48ZHg@mail.gmail.com>
Subject: Re: draft-ietf-v6ops-6to4-to-historic (yet again)
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Ronald Bonica <rbonica@juniper.net>, "ietf@ietf.org" <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: Tue, 26 Jul 2011 07:53:50 -0000

On Mon, Jul 25, 2011 at 4:30 PM, Ronald Bonica <rbonica@juniper.net> wrote:
> Folks,
>
> After some discussion, the IESG is attempting to determine whether there =
is IETF consensus to do the following:
>
> - add a new section to draft-ietf-v6ops-6to4-to-historic
> - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL
>
> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 and co=
nvert their status to HISTORIC. It will also contain a new section describi=
ng what it means for RFCs 3056 and 3068 to be classified as HISTORIC. The n=
ew section will say that:
>
> - 6-to-4 should not be configured by default on any implementation (hosts=
, cpe routers, other)
> - vendors will decide whether/when 6-to-4 will be removed from implementa=
tions. Likewise, operators will decide whether/when 6-to-4 relays will be r=
emoved from their networks. The status of RFCs 3056 and 3068 should not be =
interpreted as a recommendation to remove 6-to-4 at any particular time.
>
>
> draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While it clar=
ifies the meaning of "HISTORIC" in this particular case, it does not set a =
precedent for any future case.
>
> Please post your views on this course of action by August 8, 2011.

Supported.
Guess there are so many against for whatever reason so the consensus
part will be hard.
The archive have probably all of the arguments.





But whatever happen with this one, can we please move on and focus on
the one and only important thing, native IPv6. All the other are work
around.



--=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 pch-b2B3A6689@u-1.phicoh.com  Tue Jul 26 02:43:21 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 8973A21F8B79 for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 02:43:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5dmEYz3oVTee for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 02:43:21 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo-6to4.hq.phicoh.net [IPv6:2002:8225:f03:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id 7B3A621F8B6B for <ietf@ietf.org>; Tue, 26 Jul 2011 02:43:19 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #66) id m1QleAW-0001g9C; Tue, 26 Jul 2011 11:43:16 +0200
Message-Id: <m1QleAW-0001g9C@stereo.hq.phicoh.net>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
Subject: Re: draft-ietf-v6ops-6to4-to-historic (yet again) 
From: Philip Homburg <pch-ietf@u-1.phicoh.com>
Sender: pch-b2B3A6689@u-1.phicoh.com
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net><4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <392CB277BC2EAE4FB83C1206954BA6CEF614@newserver.arneill-py.local>
In-reply-to: Your message of "Mon, 25 Jul 2011 20:25:53 -0700 ." <392CB277BC2EAE4FB83C1206954BA6CEF614@newserver.arneill-py.local> 
Date: Tue, 26 Jul 2011 11:43:08 +0200
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 09:43:21 -0000

In your letter dated Mon, 25 Jul 2011 20:25:53 -0700 you wrote:
>Maybe I'm reading the list wrong,
>but I think the sticky point here is the "historic" thing, and nothing
>short of removing that part will significantly change the mindset of
>people who oppose it.
>
>Have you considered a newer revision of the 6-to-4 RFCs that would
>obsolete the current ones and add that 6-to-4 should be disabled by
>default? That could reach consensus.

Hmm, I never bothered to really study RFC-2026. But now I found this:

[Section 6.2:]
"When a standards-track specification has not reached the Internet
"Standard level but has remained at the same maturity level for
"twenty-four (24) months, and every twelve (12) months thereafter
"until the status is changed, the IESG shall review the viability of
"the standardization effort responsible for that specification and the
"usefulness of the technology. Following each such review, the IESG
"shall approve termination or continuation of the development effort,
"at the same time the IESG shall decide to maintain the specification
"at the same maturity level or to move it to Historic status.  This
"decision shall be communicated to the IETF by electronic mail to the
"IETF Announce mailing list to allow the Internet community an
"opportunity to comment. This provision is not intended to threaten a
"legitimate and active Working Group effort, but rather to provide an
"administrative mechanism for terminating a moribund effort.

I think it is safe to say that 6to4 is a standard track protocol that is
going nowhere. So why can't the IESG just decide to move 6to4 to historic?



From carlberg@g11.org.uk  Tue Jul 26 03:41:45 2011
Return-Path: <carlberg@g11.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 CC2CD21F875E; Tue, 26 Jul 2011 03:41:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QlhIR3z7fwro; Tue, 26 Jul 2011 03:41:45 -0700 (PDT)
Received: from portland.eukhosting.net (portland.eukhosting.net [92.48.97.5]) by ietfa.amsl.com (Postfix) with ESMTP id 0B0A221F874A; Tue, 26 Jul 2011 03:41:45 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=g11.org.uk; h=Message-ID:Date:From:To:Cc:Subject:MIME-Version:Content-Type:Content-Disposition:Content-Transfer-Encoding:User-Agent:X-Source:X-Source-Args:X-Source-Dir; b=M7WYrH+4la6mylmpqk131Wwp8hkzO1RBhy6oHNKkVc7sTkUqsZwMBU3BiCnqnhokwyF+5L9OTxAy6fwixh6iT1a6vBDxPedyQqFZHOeBmw4fuuW2NuHbYrIQpK/r7zrd;
Received: from localhost ([127.0.0.1]:38387) by portland.eukhosting.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <carlberg@g11.org.uk>) id 1Qlf4x-0003sR-Cj; Tue, 26 Jul 2011 10:41:35 +0000
Received: from 130.129.67.210 ([130.129.67.210]) by portland.eukhosting.net (Horde Framework) with HTTP; Tue, 26 Jul 2011 10:41:35 +0000
Message-ID: <20110726104135.13472eudbij0eaqs@portland.eukhosting.net>
Date: Tue, 26 Jul 2011 10:41:35 +0000
From: carlberg@g11.org.uk
To: shanna@juniper.net
Subject: re: secdir review of draft-ietf-dime-priority-avps-04
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.3.9)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - portland.eukhosting.net
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - g11.org.uk
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: lionel.morand@orange-ftgroup.com, draft-ietf-dime-priority-avps.all@tools.ietf.org, ietf@ietf.org, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 10:41:45 -0000

Hi Steve,

Thanks for the review.

<snip>

> This standards track document defines Diameter AVPs that can be
> used to convey a variety of priority parameters. While the Security
> Considerations section of this document properly requires that
> implementers review the Security Considerations section in the
> Diameter protocol specification and consider the issues described
> there, it does not include any analysis of the specific security
> issues related to priority systems. The authors should review other
> Security Considerations sections relating to priority systems
> (e.g. the one in RFC 4412) and add text that describes the
> special security issues that arise with priority systems and
> the countermeasures that may be employed.

You raise an interesting issue and we actually had a discussion about  
this on the DIME list  
<http://www.ietf.org/mail-archive/web/dime/current/msg04773.html>

And just for the sake of completeness, here is the security  
considerations text of the dime-priority-avps draft in question:

    This document describes the extension of Diameter for conveying Quality
    of Service information.  The security considerations of the Diameter
    protocol itself have been discussed in [I-D.ietf-dime-rfc3588bis].  Use
    of the AVPs defined in this document MUST take into consideration the
    security issues and requirements of the Diameter base protocol.

    The authors also recommend that readers should familiarize themselves
    with the security considerations of the various protocols listed in
    the Normative References listed below.

In a nutshell, the authors and the chair disagreed with the need for  
extending the security considerations to include an analysis with  
other protocols (eg, rfc-4412) because these protocols operate outside  
of the DIAMETER protocol.  The dime-priority-avps draft is an  
extension of I-D.ietf-dime-rfc3588bis, and thus is subject to the same  
security considerations to the bis draft.  And its also important to  
keep in mind that the dime-priority-avps draft does not inject  
prioritization into the exchange of DIAMETER messages.  It simply  
defines AVPs that correlate to some priority fields of other protocols.

If it was the last sentence (above) in the dime-priority-avps security  
considerations that has triggered your comment about further analysis,  
then I'd prefer just removing that text.

cheers,

-ken



From shanna@juniper.net  Tue Jul 26 03:54:48 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 6824B21F8C30; Tue, 26 Jul 2011 03:54: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 wABRONZsfShg; Tue, 26 Jul 2011 03:54:47 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id D70A621F8B67; Tue, 26 Jul 2011 03:54:44 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKTi6c7oRZbl2ZFIIlj9fHyMnaOi758ARl@postini.com; Tue, 26 Jul 2011 03:54:47 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; Tue, 26 Jul 2011 03:52:47 -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; Tue, 26 Jul 2011 06:52:46 -0400
From: Stephen Hanna <shanna@juniper.net>
To: "carlberg@g11.org.uk" <carlberg@g11.org.uk>
Date: Tue, 26 Jul 2011 06:52:45 -0400
Subject: RE: secdir review of draft-ietf-dime-priority-avps-04
Thread-Topic: secdir review of draft-ietf-dime-priority-avps-04
Thread-Index: AcxLgJ6J3gNB8HReTRmZ8+GTygdEGAAALbkA
Message-ID: <AC6674AB7BC78549BB231821ABF7A9AEB674516F2B@EMBX01-WF.jnpr.net>
References: <20110726104135.13472eudbij0eaqs@portland.eukhosting.net>
In-Reply-To: <20110726104135.13472eudbij0eaqs@portland.eukhosting.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: "lionel.morand@orange-ftgroup.com" <lionel.morand@orange-ftgroup.com>, "draft-ietf-dime-priority-avps.all@tools.ietf.org" <draft-ietf-dime-priority-avps.all@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 10:54:48 -0000

Thanks for your response, Ken.

Removing the last sentence that you quoted would make things worse.
Readers of this draft should definitely familiarize themselves with
the security considerations related to priority. We should make that
easier, not harder. The fact that those considerations also apply to
other RFCs does not remove the fact that they apply to this one also.

You cannot publish a document whose security considerations section
says (as this one effectively does today), "There are lots of security
considerations related to this document. To understand them, please
dig through all the referenced documents and figure it out yourself."
Doing that digging and analysis is the job of the document editors.

In order to ease the burden on you, I think a reasonable compromise
would be for YOU to review the documents referenced and decide which
have the most relevant security considerations. Then you could list
those explicitly in the last paragraph of the Security Considerations.

Thanks,

steve

> -----Original Message-----
> From: carlberg@g11.org.uk [mailto:carlberg@g11.org.uk]
> Sent: Tuesday, July 26, 2011 6:42 AM
> To: Stephen Hanna
> Cc: ietf@ietf.org; secdir@ietf.org; draft-ietf-dime-priority-
> avps.all@tools.ietf.org; lionel.morand@orange-ftgroup.com
> Subject: re: secdir review of draft-ietf-dime-priority-avps-04
>=20
> Hi Steve,
>=20
> Thanks for the review.
>=20
> <snip>
>=20
> > This standards track document defines Diameter AVPs that can be
> > used to convey a variety of priority parameters. While the Security
> > Considerations section of this document properly requires that
> > implementers review the Security Considerations section in the
> > Diameter protocol specification and consider the issues described
> > there, it does not include any analysis of the specific security
> > issues related to priority systems. The authors should review other
> > Security Considerations sections relating to priority systems
> > (e.g. the one in RFC 4412) and add text that describes the
> > special security issues that arise with priority systems and
> > the countermeasures that may be employed.
>=20
> You raise an interesting issue and we actually had a discussion about
> this on the DIME list
> <http://www.ietf.org/mail-archive/web/dime/current/msg04773.html>
>=20
> And just for the sake of completeness, here is the security
> considerations text of the dime-priority-avps draft in question:
>=20
>     This document describes the extension of Diameter for conveying
> Quality
>     of Service information.  The security considerations of the
> Diameter
>     protocol itself have been discussed in [I-D.ietf-dime-rfc3588bis].
> Use
>     of the AVPs defined in this document MUST take into consideration
> the
>     security issues and requirements of the Diameter base protocol.
>=20
>     The authors also recommend that readers should familiarize
> themselves
>     with the security considerations of the various protocols listed in
>     the Normative References listed below.
>=20
> In a nutshell, the authors and the chair disagreed with the need for
> extending the security considerations to include an analysis with
> other protocols (eg, rfc-4412) because these protocols operate outside
> of the DIAMETER protocol.  The dime-priority-avps draft is an
> extension of I-D.ietf-dime-rfc3588bis, and thus is subject to the same
> security considerations to the bis draft.  And its also important to
> keep in mind that the dime-priority-avps draft does not inject
> prioritization into the exchange of DIAMETER messages.  It simply
> defines AVPs that correlate to some priority fields of other protocols.
>=20
> If it was the last sentence (above) in the dime-priority-avps security
> considerations that has triggered your comment about further analysis,
> then I'd prefer just removing that text.
>=20
> cheers,
>=20
> -ken
>=20


From carlberg@g11.org.uk  Tue Jul 26 04:23:56 2011
Return-Path: <carlberg@g11.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 04D0F21F8C61; Tue, 26 Jul 2011 04:23:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HZVgQDhQb-PX; Tue, 26 Jul 2011 04:23:55 -0700 (PDT)
Received: from portland.eukhosting.net (portland.eukhosting.net [92.48.97.5]) by ietfa.amsl.com (Postfix) with ESMTP id 1A16A21F8B91; Tue, 26 Jul 2011 04:23:55 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=g11.org.uk; h=Message-ID:Date:From:To:Cc:Subject:References:In-Reply-To:MIME-Version:Content-Type:Content-Disposition:Content-Transfer-Encoding:User-Agent:X-Source:X-Source-Args:X-Source-Dir; b=DQhuqeEDff2sTZfYU5reNpvf+h8QGlQlnABqEBvRIpKxMB/NcthwVHpuE0y0BwlwstCyMaEIuJafVm3FC8uP1X19iWdhuKzo7nqSojPajH6rtuVkizh8mtFZtusRo0RO;
Received: from localhost ([127.0.0.1]:24388) by portland.eukhosting.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <carlberg@g11.org.uk>) id 1Qlfjm-0001ct-KH; Tue, 26 Jul 2011 11:23:46 +0000
Received: from 130.129.67.210 ([130.129.67.210]) by portland.eukhosting.net (Horde Framework) with HTTP; Tue, 26 Jul 2011 11:23:46 +0000
Message-ID: <20110726112346.35893ibie0kwerqc@portland.eukhosting.net>
Date: Tue, 26 Jul 2011 11:23:46 +0000
From: carlberg@g11.org.uk
To: Stephen Hanna <shanna@juniper.net>
Subject: RE: secdir review of draft-ietf-dime-priority-avps-04
References: <20110726104135.13472eudbij0eaqs@portland.eukhosting.net> <AC6674AB7BC78549BB231821ABF7A9AEB674516F2B@EMBX01-WF.jnpr.net>
In-Reply-To: <AC6674AB7BC78549BB231821ABF7A9AEB674516F2B@EMBX01-WF.jnpr.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.3.9)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - portland.eukhosting.net
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - g11.org.uk
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: "lionel.morand@orange-ftgroup.com" <lionel.morand@orange-ftgroup.com>, "draft-ietf-dime-priority-avps.all@tools.ietf.org" <draft-ietf-dime-priority-avps.all@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 11:23:56 -0000

Steve,


Quoting Stephen Hanna <shanna@juniper.net>:

> Thanks for your response, Ken.
>
> Removing the last sentence that you quoted would make things worse.
> Readers of this draft should definitely familiarize themselves with
> the security considerations related to priority. We should make that
> easier, not harder. The fact that those considerations also apply to
> other RFCs does not remove the fact that they apply to this one also.

but those considerations do not directly apply to DIAMETER.

> You cannot publish a document whose security considerations section
> says (as this one effectively does today), "There are lots of security
> considerations related to this document. To understand them, please
> dig through all the referenced documents and figure it out yourself."
> Doing that digging and analysis is the job of the document editors.

agreed, speaking in the general sense.  But again, the security  
considerations of these other protocols do not apply to the operation  
of Diameter.

> In order to ease the burden on you, I think a reasonable compromise
> would be for YOU to review the documents referenced and decide which
> have the most relevant security considerations. Then you could list
> those explicitly in the last paragraph of the Security Considerations.

I'm concerned about the implications of your recommendation.  If we  
extend this position to other work in the IETF, then efforts like  
defining MIBs would mean that each MIB draft would need to perform a  
security considerations analysis of each protocol that an objects  
refers to in the context of SNMP.  And one can extend the argument  
that each protocol operating on top of TCP (and/or UDP) and IP would  
need to perform an analysis on how TCP/UDP and IP may affect the upper  
layer protocol.  We don't do that today.

cheers,

-ken



From olaf@NLnetLabs.nl  Tue Jul 26 05:52:23 2011
Return-Path: <olaf@NLnetLabs.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 048E921F8C4F for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 05:52:23 -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 EeP5ZSEyrL7V for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 05:52:22 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 85C0621F8B81 for <ietf@ietf.org>; Tue, 26 Jul 2011 05:52:21 -0700 (PDT)
Received: from dhcp-2712.meeting.ietf.org (dhcp-2712.meeting.ietf.org [130.129.39.18]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id p6QCqHaQ075496 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Tue, 26 Jul 2011 14:52:19 +0200 (CEST) (envelope-from olaf@NLnetLabs.nl)
From: Olaf Kolkman <olaf@NLnetLabs.nl>
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: multipart/signed; boundary="Apple-Mail=_96087D72-F7E2-4EF4-B705-E5715484061C"; protocol="application/pkcs7-signature"; micalg=sha1
Subject: Re: IAOC: delegating ex-officio responsibility 
Date: Tue, 26 Jul 2011 08:52:16 -0400
In-Reply-To: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>
To: IETF Discussion <ietf@ietf.org>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>
Message-Id: <F31C7D4B-12A5-4520-B0D5-F9CD7FCF3EB5@NLnetLabs.nl>
X-Mailer: Apple Mail (2.1244.3)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [213.154.224.1]); Tue, 26 Jul 2011 14:52:19 +0200 (CEST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 12:52:23 -0000

--Apple-Mail=_96087D72-F7E2-4EF4-B705-E5715484061C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


Dear Colleagues,





Based on the discussion I've updated the draft:
http://tools.ietf.org/html/draft-kolkman-iasa-ex-officio-membership

Essentially I incorporated Dave Crocker's proposal to=20
1) replace the 'chairs' by voting members appointed by the respective =
bodies.
2) allow the chairs to participate in all meetings and provide =
(unsolicited) advice.

I believe that allows chairs to exercise their responsibilities of =
keeping a coherent perspective of the organization an allow them to =
steer outcomes if needed, but doesn't require the day-to-day involvement =
that is required from a diligent voting member.

--Olaf

________________________________________________________=20

Olaf M. Kolkman                        NLnet Labs
http://www.nlnetlabs.nl/











    =20


--Apple-Mail=_96087D72-F7E2-4EF4-B705-E5715484061C
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIFMTCCBS0w
ggMVoAMCAQICAwn66TANBgkqhkiG9w0BAQUFADB5MRAwDgYDVQQKEwdSb290IENBMR4wHAYDVQQL
ExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBBdXRob3Jp
dHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZzAeFw0xMTAzMjMxNTIzNTlaFw0x
MzAzMjIxNTIzNTlaMDkxFTATBgNVBAMTDE9sYWYgS29sa21hbjEgMB4GCSqGSIb3DQEJARYRb2xh
ZkBubG5ldGxhYnMubmwwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCtxtZNngmuLgcf
rto+Uax1WhonECqb5W8US2Z+ZPw/ASKsjKEF8Wa3Nnispys6Gj9Sl7C1X0/2pH//qauLpBqA+lHW
L9mgdGW1T9KU1Fb8Odqw0PBnIIhbLNQzecZL+BchEetcrubplQWzDOpROCJ00IwXksusBiKqhew4
u7X2QoraW+z32Knj5ogajIhdkAeBHUy1pwXsk/mDnV8cIEdz1MhaZWDSn7kJUQtRMVCpFBjVoiXh
ToXMJfiMvn0CKaeFxFm72dcdzvFsw906Ndafd2MOfdP7QSsTVP6sG9am790AOgkzxT5CM77IDPbD
zxZlQ8jTdhcp/WtUrFWIU4QBAgMBAAGjgf0wgfowDAYDVR0TAQH/BAIwADBWBglghkgBhvhCAQ0E
SRZHVG8gZ2V0IHlvdXIgb3duIGNlcnRpZmljYXRlIGZvciBGUkVFIGhlYWQgb3ZlciB0byBodHRw
Oi8vd3d3LkNBY2VydC5vcmcwQAYDVR0lBDkwNwYIKwYBBQUHAwQGCCsGAQUFBwMCBgorBgEEAYI3
CgMEBgorBgEEAYI3CgMDBglghkgBhvhCBAEwMgYIKwYBBQUHAQEEJjAkMCIGCCsGAQUFBzABhhZo
dHRwOi8vb2NzcC5jYWNlcnQub3JnMBwGA1UdEQQVMBOBEW9sYWZAbmxuZXRsYWJzLm5sMA0GCSqG
SIb3DQEBBQUAA4ICAQDKn+TpSrPQr3M8c8F2GGx3BgUnJUN7BBdUI7edGLqLrCBDYLIQSeC/uvLJ
gXt80tfIEGXENNbjb2lrAyrzdounfwTD5GsXqESDXJfCMYiZxVCDmZ71ncXWw9tCW8EmibhmPAeS
fL2yYoGlTOdl48mlZfb0oEB7KeFrjjkP18XbgKsZRhUAmGSBFufJbCxO/LN+F9jCIDOPWM4A6+v3
gjHWc23uW6ZHOqJouviAXkzRJhLSOBSHyOMtgcuGoqoNStzKw3X/FvKXyLF7+Ij5Fss7Gfh0Yiwb
rdP9AcZJL8ZWPw6StTJwSJHuly4co//NIozcFcGQ+qY8iUnDU6Y2YjQZ5iFQ3k7HELCknEJF48Ww
r18NO5l+Wv6Za5UjJJxI2J8l7f1vE7Pa0/Q0o2m5/TeWhbS3Y1U+jfdXmHIwfcxggzqwerNQ9Pm5
uiwRxwElUPfNVDa30rI+UJ4h/tUJsyPCsbQrcVFt3tqL1tyxcPfkebzGuh6oUTG0VVBLM7wNqG+i
nMO1XdqIC1AzNxzq9iOse5YrIK8H++rUdF34vWicvxMMtgzIYGhJwgdRshWs6JL2sRjDCkiUto4b
FWixno9yfESzsQ9LmQ/9A8fQyXsIvSdfZ5Ywh/n8j71Za9E/U43dGrMBstldNoBhvKRHv574PAlU
JwTq0EP4A0X7e7EqgjGCAzMwggMvAgEBMIGAMHkxEDAOBgNVBAoTB1Jvb3QgQ0ExHjAcBgNVBAsT
FWh0dHA6Ly93d3cuY2FjZXJ0Lm9yZzEiMCAGA1UEAxMZQ0EgQ2VydCBTaWduaW5nIEF1dGhvcml0
eTEhMB8GCSqGSIb3DQEJARYSc3VwcG9ydEBjYWNlcnQub3JnAgMJ+ukwCQYFKw4DAhoFAKCCAYcw
GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTEwNzI2MTI1MjE3WjAj
BgkqhkiG9w0BCQQxFgQU8VdQboEP2UyQZ8i2vPSMIk3Sd8IwgZEGCSsGAQQBgjcQBDGBgzCBgDB5
MRAwDgYDVQQKEwdSb290IENBMR4wHAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNV
BAMTGUNBIENlcnQgU2lnbmluZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2Fj
ZXJ0Lm9yZwIDCfrpMIGTBgsqhkiG9w0BCRACCzGBg6CBgDB5MRAwDgYDVQQKEwdSb290IENBMR4w
HAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBB
dXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZwIDCfrpMA0GCSqGSIb3
DQEBAQUABIIBAATIXca/jl+P3op7AR04H87gFM8Es6KkB/OM35cgm92SZryilN/+rVljcM8I/5LL
slW6pdkIO4e28sNKFQtfKYBZ1lMlOZyHDv4Yxm5RzN/Rk6Zz6rSz2ClLC24RvThvgOgc1VdbKv5Z
jRxubySoT1FBYjMwPrFsDuLcdgKMMXgtLsNkIk2iK16IxeSIklWQA9b3gbxaAjoGg5LFlNBrOOii
soZWttum93sYgPvTslznnhyJBcoDiz0b2b4SOM8optgi5jy1tQK/OOUyBTfABFf7fLMxor2LoN/L
7t0XHRfBzmFeNCQwf/R+Z03zoLA28x0iSzrUjAbLWSLu3fvV3doAAAAAAAA=

--Apple-Mail=_96087D72-F7E2-4EF4-B705-E5715484061C--

From rbonica@juniper.net  Tue Jul 26 06:50:07 2011
Return-Path: <rbonica@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C71EF21F855C for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 06:50:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.533
X-Spam-Level: 
X-Spam-Status: No, score=-106.533 tagged_above=-999 required=5 tests=[AWL=0.066, 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 8wPSFCdc8S4w for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 06:50:07 -0700 (PDT)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id 648F421F8C72 for <ietf@ietf.org>; Tue, 26 Jul 2011 06:50:05 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKTi7GCwWREsAFb7pX92YkmRHlX/fnCt+k@postini.com; Tue, 26 Jul 2011 06:50:06 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.2.254.0; Tue, 26 Jul 2011 06:47:34 -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; Tue, 26 Jul 2011 09:47:29 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Tue, 26 Jul 2011 09:47:28 -0400
Subject: RE: draft-ietf-v6ops-6to4-to-historic  (yet again)
Thread-Topic: draft-ietf-v6ops-6to4-to-historic  (yet again)
Thread-Index: AcxLQVmRHd1V19asQbKaMWUW/pae4QAV2j4w
Message-ID: <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com>
In-Reply-To: <4E2E2FBA.1030304@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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 13:50:08 -0000

QnJpYW4sDQoNCkRvZXMgdGhlIGZvbGxvd2luZyB0ZXh0IHdvcmsgZm9yIHlvdT8NCg0KICAgICAg
ICAgICAgICAgICAgICAgICAgIFJvbg0KDQoNCk4uIE1lYW5pbmcgb2YgSElTVE9SSUMNCg0KRm9y
IHRoZSBwdXJwb3NlcyBvZiB0aGlzIGRvY3VtZW50LCB0aGUgdGVybSBISVNUT1JJQyBtZWFuczoN
Cg0KLSA2LXRvLTQgc2hvdWxkIG5vdCBiZSBjb25maWd1cmVkIGJ5IGRlZmF1bHQgb24gYW55IGlt
cGxlbWVudGF0aW9uIChob3N0LCBjcGUgcm91dGVyLCBvdGhlcikNCg0KLSBWZW5kb3JzIHdpbGwg
ZGVjaWRlIHdoaWNoIGZ1dHVyZSB2ZXJzaW9ucyBvZiB0aGVpciBwcm9kdWN0cyB3aWxsIHN1cHBv
cnQgNi10by00LiBJdCBpcyBhc3N1bWVkIHRoYXQgdmVuZG9ycyB3aWxsIGNvbnRpbnVlIHRvIHN1
cHBvcnQgNi10by00IHVudGlsIGEpIHRoZXkgYXJlIG5vIGxvbmdlciBlY29ub21pY2FsbHkgaW5j
ZW50ZWQgdG8gZG8gc28gYW5kIGIpIHRoZXkgYXJlIGVjb25vbWljYWxseSBpbmNlbnRlZCB0byBy
ZW1vdmUgdW51c2VkIGZlYXR1cmVzIGZyb20gdGhlaXIgcHJvZHVjdHMuDQoNCi0gT3BlcmF0b3Jz
IHdpbGwgZGVjaWRlIHdoZW4gdG8gZGVjb21taXNzaW9uIDYtdG8tNCByZWxheXMsIGlmIGV2ZXIu
IEl0IGlzIGFzc3VtZWQgdGhhdCBvcGVyYXRvcnMgd2lsbCBjb250aW51ZSB0byBvcGVyYXRlIDYt
dG8tNCByZWxheXMgYXMgbG9uZyBhcyB0aGV5IGFyZSBlY29ub21pY2FsbHkgaW5jZW50ZWQgdG8g
ZG8gc28uIFdoZW4gNi10by00IHRyYWZmaWMgbGV2ZWxzIHJlYWNoIHplcm8sIG9wZXJhdG9ycyB3
aWxsIHByb2JhYmx5IGJlZ2luIHRvIGNvbnNpZGVyIGRlY29tbWlzc2lvbmluZy4NCg0KVGhlIHN0
YXR1cyBvZiBSRkNzIDMwNTYgYW5kIDMwNjggc2hvdWxkIG5vdCBiZSBpbnRlcnByZXRlZCBhcyBh
IHJlY29tbWVuZGF0aW9uIHRvIHJlbW92ZSA2LXRvLTQgYXQgYW55IHBhcnRpY3VsYXIgdGltZS4N
Cg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IEJyaWFuIEUgQ2FycGVu
dGVyIFttYWlsdG86YnJpYW4uZS5jYXJwZW50ZXJAZ21haWwuY29tXQ0KPiBTZW50OiBNb25kYXks
IEp1bHkgMjUsIDIwMTEgMTE6MDkgUE0NCj4gVG86IFJvbmFsZCBCb25pY2ENCj4gQ2M6IGlldGZA
aWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6IGRyYWZ0LWlldGYtdjZvcHMtNnRvNC10by1oaXN0b3Jp
YyAoeWV0IGFnYWluKQ0KPiANCj4gVG8gYmUgY2xlYXIsIEknZCBsaWtlIHRvIHNlZSBleGFjdCBw
cm9wb3NlZCB0ZXh0IGJlZm9yZSBleHByZXNzaW5nDQo+IHN1cHBvcnQgZm9yIHRoZSBwcm9wb3Nh
bC4gVGhlIHRyaWNrIGlzIHRvIGdldCA2dG80IGRpc2FibGVkIGJ5IGRlZmF1bHQNCj4gYXQgdGhl
IHVzZXIgZW5kLCB3aXRob3V0IGRpc2FibGluZyBpdCBmb3IgdXNlcnMgd2hvIGFyZSBnZXR0aW5n
IGdvb2QNCj4gc2VydmljZSBmcm9tIGl0Lg0KPiANCj4gUmVnYXJkcw0KPiAgICBCcmlhbg0KPiAN
Cj4gT24gMjAxMS0wNy0yNiAwOTo0OSwgQnJpYW4gRSBDYXJwZW50ZXIgd3JvdGU6DQo+ID4+ICBM
aWtld2lzZSwgb3BlcmF0b3JzIHdpbGwgZGVjaWRlIHdoZXRoZXIvd2hlbiA2LXRvLTQgcmVsYXlz
IHdpbGwgYmUNCj4gcmVtb3ZlZCBmcm9tIHRoZWlyIG5ldHdvcmtzLg0KPiA+DQo+ID4gVGhpcyBp
cywgb2YgY291cnNlLCBhbiB1bmRlbmlhYmxlIHN0YXRlbWVudCBvZiBmYWN0IChhcyBpdCBpcyBm
b3IgYW55DQo+IG90aGVyIGZlYXR1cmUNCj4gPiBvZiB0aGUgSW50ZXJuZXQpLiBIb3dldmVyLCBp
dCBuZWVkcyB0byBiZSBtYWRlIGNsZWFyIHRoYXQgZG9pbmcgc28NCj4gKnByZW1hdHVyZWx5Kg0K
PiA+IHdvdWxkIHBlbmFsaXNlIGV4aXN0aW5nIHN1Y2Nlc3NmdWwgdXNlcnMgb2YgdGhvc2UgcmVs
YXlzLCBhbmQNCj4gdGhlcmVmb3JlIGl0IHNob3VsZA0KPiA+IG9ubHkgYmUgZG9uZSB3aGVuIHRo
ZXJlIGlzIG5vIHN1Y2Nlc3NmdWwgdHJhZmZpYyB0aHJvdWdoIHRoZW0uIFdoaWNoDQo+IGlzIHdo
ZW4gYW55DQo+ID4gb3BlcmF0b3Igd291bGQgcmVtb3ZlIHRoZW0gYW55d2F5Lg0KPiA+DQo+ID4g
VGhlcmVmb3JlLCBJIGRvbid0IHNlZSBtdWNoIHZhbHVlIGluIHRoaXMgc3RhdGVtZW50LCBhbmQg
cG9zc2libGUNCj4gaGFybSB0byB1c2Vycy4NCj4gPiBUaGUgd2F5cyB0byBhdm9pZCBzdWNoIGhh
cm0gYXMgZmFyIGFzIHBvc3NpYmxlIGFyZSBhbHJlYWR5IGluIHRoZSBSRkMNCj4gRWRpdG9yDQo+
ID4gcXVldWUuDQo+ID4NCj4gPiBSZWdhcmRzDQo+ID4gICAgQnJpYW4gQ2FycGVudGVyDQo+ID4N
Cj4gPiBPbiAyMDExLTA3LTI2IDAyOjMwLCBSb25hbGQgQm9uaWNhIHdyb3RlOg0KPiA+PiBGb2xr
cywNCj4gPj4NCj4gPj4gQWZ0ZXIgc29tZSBkaXNjdXNzaW9uLCB0aGUgSUVTRyBpcyBhdHRlbXB0
aW5nIHRvIGRldGVybWluZSB3aGV0aGVyDQo+IHRoZXJlIGlzIElFVEYgY29uc2Vuc3VzIHRvIGRv
IHRoZSBmb2xsb3dpbmc6DQo+ID4+DQo+ID4+IC0gYWRkIGEgbmV3IHNlY3Rpb24gdG8gZHJhZnQt
aWV0Zi12Nm9wcy02dG80LXRvLWhpc3RvcmljDQo+ID4+IC0gcHVibGlzaCBkcmFmdC1pZXRmLXY2
b3BzLTZ0bzQtdG8taGlzdG9yaWMgYXMgSU5GT1JNQVRJT05BTA0KPiA+Pg0KPiA+PiBkcmFmdC1p
ZXRmLXY2b3BzLTZ0bzQtdG8taGlzdG9yaWMgd2lsbCBvYnNvbGV0ZSBSRkNzIDMwNTYgYW5kIDMw
NjgNCj4gYW5kIGNvbnZlcnQgdGhlaXIgc3RhdHVzIHRvIEhJU1RPUklDLiBJdCB3aWxsIGFsc28g
Y29udGFpbiBhIG5ldw0KPiBzZWN0aW9uIGRlc2NyaWJpbmcgd2hhdCBpdCBtZWFucyBmb3IgUkZD
cyAzMDU2IGFuZCAzMDY4IHRvIGJlDQo+IGNsYXNzaWZpZWQgYXMgSElTVE9SSUMuIFRoZSBuZXcg
c2VjdGlvbiB3aWxsIHNheSB0aGF0Og0KPiA+Pg0KPiA+PiAtIDYtdG8tNCBzaG91bGQgbm90IGJl
IGNvbmZpZ3VyZWQgYnkgZGVmYXVsdCBvbiBhbnkgaW1wbGVtZW50YXRpb24NCj4gKGhvc3RzLCBj
cGUgcm91dGVycywgb3RoZXIpDQo+ID4+IC0gdmVuZG9ycyB3aWxsIGRlY2lkZSB3aGV0aGVyL3do
ZW4gNi10by00IHdpbGwgYmUgcmVtb3ZlZCBmcm9tDQo+IGltcGxlbWVudGF0aW9ucy4gTGlrZXdp
c2UsIG9wZXJhdG9ycyB3aWxsIGRlY2lkZSB3aGV0aGVyL3doZW4gNi10by00DQo+IHJlbGF5cyB3
aWxsIGJlIHJlbW92ZWQgZnJvbSB0aGVpciBuZXR3b3Jrcy4gVGhlIHN0YXR1cyBvZiBSRkNzIDMw
NTYgYW5kDQo+IDMwNjggc2hvdWxkIG5vdCBiZSBpbnRlcnByZXRlZCBhcyBhIHJlY29tbWVuZGF0
aW9uIHRvIHJlbW92ZSA2LXRvLTQgYXQNCj4gYW55IHBhcnRpY3VsYXIgdGltZS4NCj4gPj4NCj4g
Pj4NCj4gPj4gZHJhZnQtaWV0Zi12Nm9wcy02dG80LXRvLWhpc3RvcmljIHdpbGwgbm90IHVwZGF0
ZSBSRkMgMjAyNi4gV2hpbGUgaXQNCj4gY2xhcmlmaWVzIHRoZSBtZWFuaW5nIG9mICJISVNUT1JJ
QyIgaW4gdGhpcyBwYXJ0aWN1bGFyIGNhc2UsIGl0IGRvZXMNCj4gbm90IHNldCBhIHByZWNlZGVu
dCBmb3IgYW55IGZ1dHVyZSBjYXNlLg0KPiA+Pg0KPiA+PiBQbGVhc2UgcG9zdCB5b3VyIHZpZXdz
IG9uIHRoaXMgY291cnNlIG9mIGFjdGlvbiBieSBBdWd1c3QgOCwgMjAxMS4NCj4gPj4NCj4gPj4N
Cj4gPj4NCj4gUm9uIEJvbmljYQ0KPiA+Pg0KPiA8c3BlYWtpbmcgYXMgT1BTIEFyZWEgQUQ+DQo+
ID4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4+
IElldGYgbWFpbGluZyBsaXN0DQo+ID4+IElldGZAaWV0Zi5vcmcNCj4gPj4gaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZXRmDQo+ID4+DQo+ID4NCg==

From marshall.eubanks@gmail.com  Tue Jul 26 06:57:06 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 6C1E921F8B08 for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 06:57:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.341
X-Spam-Level: 
X-Spam-Status: No, score=-103.341 tagged_above=-999 required=5 tests=[AWL=0.257, 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 cRLL69gBo2QE for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 06:57:05 -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 8E2CB21F884F for <ietf@ietf.org>; Tue, 26 Jul 2011 06:57:05 -0700 (PDT)
Received: by gyd5 with SMTP id 5so324593gyd.31 for <ietf@ietf.org>; Tue, 26 Jul 2011 06:57:05 -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=63M5xh1wT623yXz1+k2TTDT6Zp72/P84SPDZUs0Vxuc=; b=ZTBPWE0kVSua3776Pqv21rc0AnDnHCN3O//w8DLbuKABTrjjGyoDQVj3PllQjkzhsE vd0ffAtmGYM2JVN73s0fQUwy8voNuARtazsFDgDpv6RrB6UWaGcSc5Yt2QzFjeHinSdL Fku3KdYpK8dMKbT3wJNKHRXjTIIvsfk6kiYrQ=
MIME-Version: 1.0
Received: by 10.151.123.18 with SMTP id a18mr5682087ybn.266.1311688623689; Tue, 26 Jul 2011 06:57:03 -0700 (PDT)
Received: by 10.151.10.20 with HTTP; Tue, 26 Jul 2011 06:57:03 -0700 (PDT)
In-Reply-To: <F31C7D4B-12A5-4520-B0D5-F9CD7FCF3EB5@NLnetLabs.nl>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl> <F31C7D4B-12A5-4520-B0D5-F9CD7FCF3EB5@NLnetLabs.nl>
Date: Tue, 26 Jul 2011 09:57:03 -0400
Message-ID: <CAJNg7VLjdaeusb4OTjKYUEGP0uAq9jiBqJaayke0Ya6QNJ2jTQ@mail.gmail.com>
Subject: Re: IAOC: delegating ex-officio responsibility
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Olaf Kolkman <olaf@nlnetlabs.nl>
Content-Type: multipart/alternative; boundary=000e0cd56de278907204a8f94e77
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, 26 Jul 2011 13:57:06 -0000

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

There is one error that must be fixed, and several nits. Otherwise, WFM.

Marshall

There is a big typo in Section 2.1

  The ISOC board of Trustees, the IAB, and the IAOC will appoint two


s/IAOC/IESG/


Nits

Section 1

   an integrated perspective about their bodies work to the IAOC.


s/bodies/body's/


Section 2.2

s/Two member /Two members /

on 3 bulleted lines.

Section 2.3, title

2.3.  IAOC membership


*
*
*
*
*
*
s/IAOC/IETF Trust/

On Tue, Jul 26, 2011 at 8:52 AM, Olaf Kolkman <olaf@nlnetlabs.nl> wrote:

>
> Dear Colleagues,
>
>
>
>
>
> Based on the discussion I've updated the draft:
> http://tools.ietf.org/html/draft-kolkman-iasa-ex-officio-membership
>
> Essentially I incorporated Dave Crocker's proposal to
> 1) replace the 'chairs' by voting members appointed by the respective
> bodies.
> 2) allow the chairs to participate in all meetings and provide
> (unsolicited) advice.
>
> I believe that allows chairs to exercise their responsibilities of keeping
> a coherent perspective of the organization an allow them to steer outcomes
> if needed, but doesn't require the day-to-day involvement that is required
> from a diligent voting member.
>
> --Olaf
>
> ________________________________________________________
>
> Olaf M. Kolkman                        NLnet Labs
> http://www.nlnetlabs.nl/
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
>

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

<div>There is one error that must be fixed, and several nits. Otherwise, WF=
M.</div><div><br></div><div>Marshall</div><div><br></div><div>There is a bi=
g typo in Section 2.1</div><div><br></div><div><span class=3D"Apple-style-s=
pan" style=3D"font-family: Times; font-size: 16px; "><pre class=3D"newpage"=
 style=3D"font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-b=
efore: always; ">
  The ISOC board of Trustees, the IAB, and the IAOC will appoint two
 </pre><pre class=3D"newpage" style=3D"font-size: 1em; margin-top: 0px; mar=
gin-bottom: 0px; page-break-before: always; ">s/IAOC/IESG/</pre></span></di=
v><div><br></div><div>Nits</div><div><br></div><div>Section 1</div><div><br=
>
</div><div><span class=3D"Apple-style-span" style=3D"font-family: Times; fo=
nt-size: 16px; "><pre class=3D"newpage" style=3D"font-size: 1em; margin-top=
: 0px; margin-bottom: 0px; page-break-before: always; ">   an integrated pe=
rspective about their bodies work to the IAOC.</pre>
<pre class=3D"newpage" style=3D"font-size: 1em; margin-top: 0px; margin-bot=
tom: 0px; page-break-before: always; "><br></pre><pre class=3D"newpage" sty=
le=3D"font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-befor=
e: always; ">
s/bodies/body&#39;s/</pre></span><div><br></div><div>Section 2.2</div><div>=
<br></div><div>s/Two member /Two members /</div><div><br></div><div>on 3 bu=
lleted lines.</div><div><br></div><div>Section 2.3, title</div><div><br>
</div><div><span class=3D"Apple-style-span" style=3D"font-family: Times; fo=
nt-size: 16px; "><pre class=3D"newpage" style=3D"font-size: 1em; margin-top=
: 0px; margin-bottom: 0px; page-break-before: always; "><span class=3D"h3" =
style=3D"font-weight: bold; line-height: 0pt; display: inline; white-space:=
 pre; font-family: monospace; font-size: 1em; "><h3 style=3D"font-weight: b=
old; line-height: 0pt; display: inline; white-space: pre; font-family: mono=
space; font-size: 1em; ">
<a name=3D"section-2.3">2.3</a>.  IAOC membership</h3></span>
</pre><div><span class=3D"h3" style=3D"font-weight: bold; line-height: 0pt;=
 display: inline; white-space: pre; font-family: monospace; font-size: 1em;=
 "><h3 style=3D"font-weight: bold; line-height: 0pt; display: inline; white=
-space: pre; font-family: monospace; font-size: 1em; ">
<br></h3></span></div><div><font class=3D"Apple-style-span" face=3D"monospa=
ce"><span class=3D"Apple-style-span" style=3D"line-height: 0px; white-space=
: pre;"><b><br></b></span></font></div><div><font class=3D"Apple-style-span=
" face=3D"monospace"><span class=3D"Apple-style-span" style=3D"line-height:=
 0px; white-space: pre;"><b><br>
</b></span></font></div><div><font class=3D"Apple-style-span" face=3D"monos=
pace"><span class=3D"Apple-style-span" style=3D"line-height: 0px; white-spa=
ce: pre;"><b><br></b></span></font></div></span></div><div>s/IAOC/IETF Trus=
t/</div>
<br><div class=3D"gmail_quote">On Tue, Jul 26, 2011 at 8:52 AM, Olaf Kolkma=
n <span dir=3D"ltr">&lt;<a href=3D"mailto:olaf@nlnetlabs.nl">olaf@nlnetlabs=
.nl</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;">
<br>
Dear Colleagues,<br>
<br>
<br>
<br>
<br>
<br>
Based on the discussion I&#39;ve updated the draft:<br>
<a href=3D"http://tools.ietf.org/html/draft-kolkman-iasa-ex-officio-members=
hip" target=3D"_blank">http://tools.ietf.org/html/draft-kolkman-iasa-ex-off=
icio-membership</a><br>
<br>
Essentially I incorporated Dave Crocker&#39;s proposal to<br>
1) replace the &#39;chairs&#39; by voting members appointed by the respecti=
ve bodies.<br>
2) allow the chairs to participate in all meetings and provide (unsolicited=
) advice.<br>
<br>
I believe that allows chairs to exercise their responsibilities of keeping =
a coherent perspective of the organization an allow them to steer outcomes =
if needed, but doesn&#39;t require the day-to-day involvement that is requi=
red from a diligent voting member.<br>

<br>
--Olaf<br>
<br>
________________________________________________________<br>
<br>
Olaf M. Kolkman =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0NLnet Labs<b=
r>
<a href=3D"http://www.nlnetlabs.nl/" target=3D"_blank">http://www.nlnetlabs=
.nl/</a><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<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></div>

--000e0cd56de278907204a8f94e77--

From tjc@ecs.soton.ac.uk  Tue Jul 26 07:15:07 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 CDAFF21F8CB5 for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 07:15:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.513
X-Spam-Level: 
X-Spam-Status: No, score=-2.513 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 N4HafjcSkV80 for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 07:15:07 -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 4B10421F8AA8 for <ietf@ietf.org>; Tue, 26 Jul 2011 07:15:06 -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 p6QEF2t0029807 for <ietf@ietf.org>; Tue, 26 Jul 2011 15:15:02 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p6QEF2t0029807
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1311689702; bh=uFkxO5fSOwUZ38TAF9gyL526dKI=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=HbqReXUw9cnFuyTAspwpeqEATyzEkREQNVMYMV8+eFZiOW4SSsXI7xmw/557SwoCN fRXqluZjrsMr0IZBkD+WZ+K9etT6h17caJq+3k+WTbZ3Od27oYDLIzQONBl7Q/BPpw DcXhxMMKcTkUhMBUrK4HN0DbWY/SSvCt6OIltI0M=
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 n6PFF20366136564Gl ret-id none; Tue, 26 Jul 2011 15:15:02 +0100
Received: from [IPv6:2001:df8::112:7d1d:53b8:a466:28b4] ([IPv6:2001:df8:0:112:7d1d:53b8:a466:28b4]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p6QEEvVS028391 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Tue, 26 Jul 2011 15:14:57 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1244.3)
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
Date: Tue, 26 Jul 2011 15:14:56 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|038a96b178501de6df9159a9611a0231n6PFF203tjc|ecs.soton.ac.uk|80E059EE-12CD-49D1-8426-2BC74C573108@ecs.soton.ac.uk>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <80E059EE-12CD-49D1-8426-2BC74C573108@ecs.soton.ac.uk>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1244.3)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n6PFF2036613656400; tid=n6PFF20366136564Gl; 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: p6QEF2t0029807
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, 26 Jul 2011 14:15:07 -0000

On 25 Jul 2011, at 15:30, Ronald Bonica wrote:
>=20
> Please post your views on this course of action by August 8, 2011.

Some observations.

Our own users made use of 6to4 maybe 8+ years ago, and at the time it =
was handy to have.  Today though we're not aware of any of our users =
running 6to4 intentionally. We have IPv6 native on site, and anyone who =
wants home IPv6 connectivity either goes to an ISP that provides it, =
e.g. A&A in the UK, or they use a tunnel broker.  Brokers have the =
additional benefit of working through NATs and with dynamic IPv4 =
endpoints.

Our site sees about 1-2% of all inbound traffic being IPv6, and of that =
less than 1% is 6to4, and this is only likely to fall further with =
rfc3484-bis. What 6to4 we do see is probably reasonably robust in that =
our return path uses the JANET-provided 6to4 relay. =20

Most operating systems either already, or before long will, support =
rfc3484-bis, which means hosts should use IPv4 in preference to 6to4 =
where both are available.  To choose to use 6to4, the user would need to =
consciously change their 3484 policy table, assuming their OS supports =
that (Linux and Windows do, MacOS X Lion appears not to).

Geoff Huston has presented data at IETF80 showing 6to4 brokenness and =
performance. We now have 'Happy Eyeballs Lite' implemented in Chrome and =
(I believe, not tested it yet) Firefox, which means the browser can =
adapt to broken IPv6, whether caused by 6to4 or other factors.

The 6to4-advisory draft suggests off-by-default, which I agree with, and =
use of relays to improve user experience. The problem is we can't expect =
every site/ISP to run a relay (or multi-address with 6to4) so there will =
inevitably always be problems with the 3068 mode of 6to4.

We measured rogue RAs over a two year period on our wireless network.  =
About 60% of the time at least one host was emitting a rogue 6to4-based =
RA. While these were mitigated by ramond, it would be good to see =
vendors fix this; it's not just MS ICS.  Happy Eyeballs is a mitigation =
for such rogue RAs also.

So in summary, in practice 3484-bis and the 6to4-advisory off-by-default =
will further reduce what little use there is of 6to4 now, and happy =
eyeballs will mitigate any remaining instances of its use that are bad. =
So whether 6to4 is tagged Historic or not, it should be causing =
significantly less harm. =20

Tim=

From richard@shockey.us  Tue Jul 26 07:18:53 2011
Return-Path: <richard@shockey.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 8D64221F8CC0 for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 07:18:53 -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.208, 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 2hThiv5+KxVM for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 07:18:52 -0700 (PDT)
Received: from oproxy1-pub.bluehost.com (oproxy1-pub.bluehost.com [66.147.249.253]) by ietfa.amsl.com (Postfix) with SMTP id 33E5921F8CC1 for <ietf@ietf.org>; Tue, 26 Jul 2011 07:18:48 -0700 (PDT)
Received: (qmail 31984 invoked by uid 0); 26 Jul 2011 14:18:47 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy1.bluehost.com with SMTP; 26 Jul 2011 14:18:47 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=shockey.us; h=Received:From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language:X-Identified-User; b=T7RcbSq1kDD9/1Jy7RpCdK5YSv7GJcVIenwLdplk5D1K15+Wg3w1jgYIrRali/Pd2ej70kgZDfC72+PuQY5aS0T2+ZS6V2+AhNR7mxe746FimfYaAtwkmrLw/Uq+V5Y4;
Received: from [130.129.20.208] (helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.69) (envelope-from <richard@shockey.us>) id 1QliT9-0004aK-FP for ietf@ietf.org; Tue, 26 Jul 2011 08:18:47 -0600
From: "Richard Shockey" <richard@shockey.us>
To: "'IETF Discussion'" <ietf@ietf.org>
References: <4E280223.8030309@dcrocker.net>
In-Reply-To: <4E280223.8030309@dcrocker.net>
Subject: RE: Review of:   draft-ietf-iab-draft-iab-dns-applications-02
Date: Tue, 26 Jul 2011 10:18:43 -0400
Message-ID: <010301cc4b9e$ee296cf0$ca7c46d0$@us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcxHkqqb6bhdsVniQwWR+k0iku3P4wDgeQxQ
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 130.129.20.208 authed with richard@shockey.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: Tue, 26 Jul 2011 14:18:53 -0000

I would like to add my support here to Dave Crocker's very thoughtful and
IMHO accurate description of this revised draft. I share his views that the
substantive criticisms have not been addressed.

What exactly is the harm that this draft proposes to prevent? I can
certainly understand the natural reluctance to continue to pile on to the
DNS various data attributes but its should be clear that that this cat has
been out of the bag for some time. 

Clearly we do not want the DNS to be used for search like functions where
there may be a indeterminate response but the examples cited do not address
those issues. I am baffled by the ongoing criticism RFC 6116 and the desire
of some members of the community to extend 6116 to values that may not
necessarily be defined as a URI. ENUM works and works quite well in both
e164.arpa and in private instantiations.

Frankly I think this draft needs to be completely withdrawn. 

If there are issues with new uses of the DNS, DNSEXT or DNSOPS are fully
chartered to provide community review and do not need any "fuzzy" guidance
on what is and is not acceptable.  This entire draft could beeasily
simplified byt a one sentence statement.

"If you need to do database look ups in the future we would prefer that you
think of using protocols other than the DNS."

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Dave
CROCKER
Sent: Thursday, July 21, 2011 6:41 AM
To: IETF Discussion
Subject: Review of: draft-ietf-iab-draft-iab-dns-applications-02


  This is a summary of a followup review of the draft, after the one noted
in
Ticket #35 of the trac wiki for this draft:

     <http://trac.tools.ietf.org/group/iab/trac/ticket/35>

  The complete version of this second review is at:

    <http://trac.tools.ietf.org/group/iab/trac/ticket/35#comment:2>


  Summary:

       The latest version of the draft contains many substantial changes.
  However it continues to have basic problems with direction, scope, detail,
  writing, and with basic confusion about architecture.

      The draft maintains its claim of being a general considerations
  discussion when, in fact, it continues to focus on fear of inappropriate
  proposals.  It continues to invoke examples of inappropriate proposals
  that lack constituency or even currency.

      In spite of language claiming to distinguish new /uses/ of the DNS
  from /changes/ to the DNS, the draft continues to confuse the two.  The
  problem appears to be a difficulty distinguishing architectural layers.
  This is like saying that TCP changes IP or that HTTP changes TCP.  Hence,
  for example, DDDS is a layer /above/ the DNS.  The only two interesting
  questions about a client layer's use of a provider layer -- such as DDDS's
  use of DNS -- is whether the functional match is acceptable and whether
  it's performance demands cause problems.  When focused on one layer, any
  further discussion of the other likely to confuse things significantly, as
  demonstrated in the draft.

      The paper continues to make broad criticisms that lack foundation and
  sometimes even lack citation.

      Some of the statements and logic sequences were entirely opaque to me.
  I could not decipher what they meant.  In some cases the apparent meaning
  was factually incorrect or confused.

      From all of this, I suspect that the only way to make useful progress
  is to start over, and to begin with a much, much more clear and concrete
  statement of the goal for the draft and then a very diligent effort to
  organize the paper's sequence and carefully document its assertions.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf


From lorenzo@google.com  Tue Jul 26 07:49: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 DE48B21F8CAC for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 07:49:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.476
X-Spam-Level: 
X-Spam-Status: No, score=-105.476 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 6o8kHazDDtnA for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 07:49: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 B01A821F8CB0 for <ietf@ietf.org>; Tue, 26 Jul 2011 07:49:16 -0700 (PDT)
Received: from wpaz37.hot.corp.google.com (wpaz37.hot.corp.google.com [172.24.198.101]) by smtp-out.google.com with ESMTP id p6QEnG2g018696 for <ietf@ietf.org>; Tue, 26 Jul 2011 07:49:16 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1311691756; bh=W36Yto59zImx7l+st+uKfWEBdJU=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=f7a5WZB4T2HeBLj2zXLEQ2A3qMTxYJL+xqz8ZY3TKBspmQEuaaHmApSZs2YZdN85L jV2CU1XDQ+fKQDCqLzW7g==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type:x-system-of-record; b=Cvu1ipILn5a1jATFbMkXwniieE5puX4dSbfRL1GmcrOqY0oF/TBr1aX5g1zn0+EUm dnqzv4eJs/w6IpiNL2qnA==
Received: from gyd12 (gyd12.prod.google.com [10.243.49.204]) by wpaz37.hot.corp.google.com with ESMTP id p6QElg5H008298 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Tue, 26 Jul 2011 07:49:15 -0700
Received: by gyd12 with SMTP id 12so361319gyd.34 for <ietf@ietf.org>; Tue, 26 Jul 2011 07:49:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=pbomT8Z611lHmjLWbjYBrvk1a6a+vmDJ4FmEidGbbi8=; b=TUa540uSchsvg053eCBWVytU2iaMwrxLHnkcFK67jaAF+S//+UOezN3EU8i2zud316 BwTBykc+A3OAXZiO5YXw==
Received: by 10.231.24.193 with SMTP id w1mr5991651ibb.41.1311691755175; Tue, 26 Jul 2011 07:49:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.12.73 with HTTP; Tue, 26 Jul 2011 07:48:55 -0700 (PDT)
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 26 Jul 2011 10:48:55 -0400
Message-ID: <CAKD1Yr3u6fRF-XtMkHUv312Rsg+PWLtxoqEcww1khNLSyWopyw@mail.gmail.com>
Subject: Re: draft-ietf-v6ops-6to4-to-historic (yet again)
To: Ronald Bonica <rbonica@juniper.net>
Content-Type: multipart/alternative; boundary=001517740cb21f3e4004a8fa09c0
X-System-Of-Record: true
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, 26 Jul 2011 14:49:18 -0000

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

I support this proposal, for the following reasons:

1. Google's public IPv6 adoption data [1] shows that from the perspective of
a website, 6to4 is a tiny and decreasing percentage of IPv6 clients.
2. Geoff Huston's data, presented at v6ops in Prague, shows that 6to4
failure rate when connecting to dual-stack destinations is approximately
20%.
3. Large website operators such as Google, Yahoo, and Facebook have data
that show that 6to4 is an important reason for a large percentage of
dual-stack brokenness, and that dual-stack brokenness is the main reason why
their websites do not have IPv6 records today. Lack of IPv6 content is one
of the reasons most often cited by access networks when explaining the lack
of IPv6 deployment to end users.
4. A number of home gateway manufacturers are still coming out with new
devices that support 6to4 and even enable it by default when IPv6 is
enabled. Declaring 6to4 it to be historic would help ensure that those
manufacturers disable 6to4 in future products.
5. The advent of large-scale NAT will decrease the applicability of 6to4.
6. The advent of ISPs assigning bogon address space to users will
substantially
7. For those who want to do application development using IPv6, there are
alternatives to 6to4, such as manually configured tunnels. These are readily
available, work behind NATs, and in many cases offer lower latency and
higher reliability.

[1] http://www.google.com/intl/en/ipv6/statistics/

On Tue, Jul 26, 2011 at 09:47, Ronald Bonica <rbonica@juniper.net> wrote:

> Brian,
>
> Does the following text work for you?
>
>                         Ron
>
>
> N. Meaning of HISTORIC
>
> For the purposes of this document, the term HISTORIC means:
>
> - 6-to-4 should not be configured by default on any implementation (host,
> cpe router, other)
>
> - Vendors will decide which future versions of their products will support
> 6-to-4. It is assumed that vendors will continue to support 6-to-4 until a)
> they are no longer economically incented to do so and b) they are
> economically incented to remove unused features from their products.
>
> - Operators will decide when to decommission 6-to-4 relays, if ever. It is
> assumed that operators will continue to operate 6-to-4 relays as long as
> they are economically incented to do so. When 6-to-4 traffic levels reach
> zero, operators will probably begin to consider decommissioning.
>
> The status of RFCs 3056 and 3068 should not be interpreted as a
> recommendation to remove 6-to-4 at any particular time.
>
>
> > -----Original Message-----
> > From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
> > Sent: Monday, July 25, 2011 11:09 PM
> > To: Ronald Bonica
> > Cc: ietf@ietf.org
> > Subject: Re: draft-ietf-v6ops-6to4-to-historic (yet again)
> >
> > To be clear, I'd like to see exact proposed text before expressing
> > support for the proposal. The trick is to get 6to4 disabled by default
> > at the user end, without disabling it for users who are getting good
> > service from it.
> >
> > Regards
> >    Brian
> >
> > On 2011-07-26 09:49, Brian E Carpenter wrote:
> > >>  Likewise, operators will decide whether/when 6-to-4 relays will be
> > removed from their networks.
> > >
> > > This is, of course, an undeniable statement of fact (as it is for any
> > other feature
> > > of the Internet). However, it needs to be made clear that doing so
> > *prematurely*
> > > would penalise existing successful users of those relays, and
> > therefore it should
> > > only be done when there is no successful traffic through them. Which
> > is when any
> > > operator would remove them anyway.
> > >
> > > Therefore, I don't see much value in this statement, and possible
> > harm to users.
> > > The ways to avoid such harm as far as possible are already in the RFC
> > Editor
> > > queue.
> > >
> > > Regards
> > >    Brian Carpenter
> > >
> > > On 2011-07-26 02:30, Ronald Bonica wrote:
> > >> Folks,
> > >>
> > >> After some discussion, the IESG is attempting to determine whether
> > there is IETF consensus to do the following:
> > >>
> > >> - add a new section to draft-ietf-v6ops-6to4-to-historic
> > >> - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL
> > >>
> > >> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068
> > and convert their status to HISTORIC. It will also contain a new
> > section describing what it means for RFCs 3056 and 3068 to be
> > classified as HISTORIC. The new section will say that:
> > >>
> > >> - 6-to-4 should not be configured by default on any implementation
> > (hosts, cpe routers, other)
> > >> - vendors will decide whether/when 6-to-4 will be removed from
> > implementations. Likewise, operators will decide whether/when 6-to-4
> > relays will be removed from their networks. The status of RFCs 3056 and
> > 3068 should not be interpreted as a recommendation to remove 6-to-4 at
> > any particular time.
> > >>
> > >>
> > >> draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While it
> > clarifies the meaning of "HISTORIC" in this particular case, it does
> > not set a precedent for any future case.
> > >>
> > >> Please post your views on this course of action by August 8, 2011.
> > >>
> > >>
> > >>
> > Ron Bonica
> > >>
> > <speaking as OPS Area AD>
> > >> _______________________________________________
> > >> 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
>

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

I support this proposal, for the following reasons:<div><br></div><div>1. G=
oogle&#39;s public IPv6 adoption data [1] shows that from the perspective o=
f a website, 6to4 is a tiny and decreasing percentage of IPv6 clients.</div=
>

<div>2. Geoff Huston&#39;s data, presented at v6ops in Prague, shows that 6=
to4 failure rate when connecting to dual-stack destinations is approximatel=
y 20%.</div><div>3. Large website operators such as Google, Yahoo, and Face=
book have data that show that 6to4 is an important reason for a large perce=
ntage of dual-stack brokenness, and that dual-stack brokenness is the main =
reason why their websites do not have IPv6 records today. Lack of IPv6 cont=
ent is one of the reasons most often cited by access networks when explaini=
ng the lack of IPv6 deployment to end users.</div>

<div>4. A number of home gateway manufacturers are still coming out with ne=
w devices that support 6to4 and even enable it by default when IPv6 is enab=
led. Declaring 6to4 it to be historic would help ensure that those manufact=
urers disable 6to4 in future products.</div>

<div>5. The advent of large-scale NAT will decrease the applicability of 6t=
o4.</div><div>6. The advent of=A0ISPs assigning bogon address space to user=
s will substantially</div><div>7. For those who want to do application deve=
lopment using IPv6, there are alternatives to 6to4, such as manually config=
ured tunnels. These are readily available, work behind NATs, and in many ca=
ses offer lower latency and higher reliability.</div>

<div><br></div><div>[1]=A0<a href=3D"http://www.google.com/intl/en/ipv6/sta=
tistics/">http://www.google.com/intl/en/ipv6/statistics/</a><br><br><div cl=
ass=3D"gmail_quote">On Tue, Jul 26, 2011 at 09:47, Ronald Bonica <span dir=
=3D"ltr">&lt;<a href=3D"mailto:rbonica@juniper.net">rbonica@juniper.net</a>=
&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Brian,<br>
<br>
Does the following text work for you?<br>
<br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Ron<br>
<br>
<br>
N. Meaning of HISTORIC<br>
<br>
For the purposes of this document, the term HISTORIC means:<br>
<br>
- 6-to-4 should not be configured by default on any implementation (host, c=
pe router, other)<br>
<br>
- Vendors will decide which future versions of their products will support =
6-to-4. It is assumed that vendors will continue to support 6-to-4 until a)=
 they are no longer economically incented to do so and b) they are economic=
ally incented to remove unused features from their products.<br>


<br>
- Operators will decide when to decommission 6-to-4 relays, if ever. It is =
assumed that operators will continue to operate 6-to-4 relays as long as th=
ey are economically incented to do so. When 6-to-4 traffic levels reach zer=
o, operators will probably begin to consider decommissioning.<br>


<div class=3D"im"><br>
The status of RFCs 3056 and 3068 should not be interpreted as a recommendat=
ion to remove 6-to-4 at any particular time.<br>
<br>
<br>
</div>&gt; -----Original Message-----<br>
&gt; From: Brian E Carpenter [mailto:<a href=3D"mailto:brian.e.carpenter@gm=
ail.com">brian.e.carpenter@gmail.com</a>]<br>
&gt; Sent: Monday, July 25, 2011 11:09 PM<br>
&gt; To: Ronald Bonica<br>
&gt; Cc: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>
&gt; Subject: Re: draft-ietf-v6ops-6to4-to-historic (yet again)<br>
&gt;<br>
&gt; To be clear, I&#39;d like to see exact proposed text before expressing=
<br>
&gt; support for the proposal. The trick is to get 6to4 disabled by default=
<br>
&gt; at the user end, without disabling it for users who are getting good<b=
r>
&gt; service from it.<br>
&gt;<br>
&gt; Regards<br>
&gt; =A0 =A0Brian<br>
<div class=3D"im">&gt;<br>
&gt; On 2011-07-26 09:49, Brian E Carpenter wrote:<br>
&gt; &gt;&gt; =A0Likewise, operators will decide whether/when 6-to-4 relays=
 will be<br>
&gt; removed from their networks.<br>
&gt; &gt;<br>
</div>&gt; &gt; This is, of course, an undeniable statement of fact (as it =
is for any<br>
&gt; other feature<br>
&gt; &gt; of the Internet). However, it needs to be made clear that doing s=
o<br>
&gt; *prematurely*<br>
&gt; &gt; would penalise existing successful users of those relays, and<br>
&gt; therefore it should<br>
&gt; &gt; only be done when there is no successful traffic through them. Wh=
ich<br>
&gt; is when any<br>
&gt; &gt; operator would remove them anyway.<br>
&gt; &gt;<br>
&gt; &gt; Therefore, I don&#39;t see much value in this statement, and poss=
ible<br>
&gt; harm to users.<br>
&gt; &gt; The ways to avoid such harm as far as possible are already in the=
 RFC<br>
&gt; Editor<br>
&gt; &gt; queue.<br>
&gt; &gt;<br>
&gt; &gt; Regards<br>
&gt; &gt; =A0 =A0Brian Carpenter<br>
<div class=3D"im">&gt; &gt;<br>
&gt; &gt; On 2011-07-26 02:30, Ronald Bonica wrote:<br>
&gt; &gt;&gt; Folks,<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; After some discussion, the IESG is attempting to determine wh=
ether<br>
&gt; there is IETF consensus to do the following:<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; - add a new section to draft-ietf-v6ops-6to4-to-historic<br>
&gt; &gt;&gt; - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL<=
br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and=
 3068<br>
&gt; and convert their status to HISTORIC. It will also contain a new<br>
&gt; section describing what it means for RFCs 3056 and 3068 to be<br>
&gt; classified as HISTORIC. The new section will say that:<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; - 6-to-4 should not be configured by default on any implement=
ation<br>
&gt; (hosts, cpe routers, other)<br>
&gt; &gt;&gt; - vendors will decide whether/when 6-to-4 will be removed fro=
m<br>
&gt; implementations. Likewise, operators will decide whether/when 6-to-4<b=
r>
&gt; relays will be removed from their networks. The status of RFCs 3056 an=
d<br>
&gt; 3068 should not be interpreted as a recommendation to remove 6-to-4 at=
<br>
&gt; any particular time.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. W=
hile it<br>
&gt; clarifies the meaning of &quot;HISTORIC&quot; in this particular case,=
 it does<br>
&gt; not set a precedent for any future case.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Please post your views on this course of action by August 8, =
2011.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; Ron Bonica<br>
&gt; &gt;&gt;<br>
&gt; &lt;speaking as OPS Area AD&gt;<br>
&gt; &gt;&gt; _______________________________________________<br>
</div>&gt; &gt;&gt; Ietf mailing list<br>
&gt; &gt;&gt; <a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
&gt; &gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/ietf</a><br>
&gt; &gt;&gt;<br>
&gt; &gt;<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>

--001517740cb21f3e4004a8fa09c0--

From tjc@ecs.soton.ac.uk  Tue Jul 26 08:11:51 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 7085621F8866 for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 08:11:51 -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 i3RZvipHPv2r for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 08:11:50 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 44CC421F8541 for <ietf@ietf.org>; Tue, 26 Jul 2011 08:11:50 -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 p6QFBjkq013988 for <ietf@ietf.org>; Tue, 26 Jul 2011 16:11:45 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p6QFBjkq013988
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1311693106; bh=FpK/IBV7jMVsSrBDVGQA2MFoKm8=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=0fC7KXeODn9yj4pTVGFQRPWC9Ln0td78II2WA2kMu0wxCmGXKYvyieHXaDPabKjgN /RP1xhlFZOwo4IGnMAv3KKOffPOWT7beBj2Z1Q50cdZ3ZiwBaZO2Kff3p/6WEKtAkI Rkkd+7YAV7SZP+nERkeSKAl0AaTF9XYOaV8UtcHY=
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 n6PGBj0366137145kY ret-id none; Tue, 26 Jul 2011 16:11:46 +0100
Received: from [IPv6:2001:df8::112:7d1d:53b8:a466:28b4] ([IPv6:2001:df8:0:112:7d1d:53b8:a466:28b4]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p6QFBcQ5012898 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Tue, 26 Jul 2011 16:11:39 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1244.3)
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|038a96b178501de6df9159a9611a0231n6PFF203tjc|ecs.soton.ac.uk|80E059EE-12CD-49D1-8426-2BC74C573108@ecs.soton.ac.uk>
Date: Tue, 26 Jul 2011 16:11:38 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|9763b88426148cf35a0854b3681c9799n6PGBj03tjc|ecs.soton.ac.uk|79EEDAFB-6F9D-4F5B-B179-E420F97F98EF@ecs.soton.ac.uk>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <80E059EE-12CD-49D1-8426-2BC74C573108@ecs.soton.ac.uk> <EMEW3|038a96b178501de6df9159a9611a0231n6PFF203tjc|ecs.soton.ac.uk|80E059EE-12CD-49D1-8426-2BC74C573108@ecs.soton.ac.uk> <79EEDAFB-6F9D-4F5B-B179-E420F97F98EF@ecs.soton.ac.uk>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1244.3)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n6PGBj036613714500; tid=n6PGBj0366137145kY; 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: p6QFBjkq013988
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, 26 Jul 2011 15:11:51 -0000

On 26 Jul 2011, at 15:14, Tim Chown wrote:
>=20
> So in summary, in practice 3484-bis and the 6to4-advisory =
off-by-default will further reduce what little use there is of 6to4 now, =
and happy eyeballs will mitigate any remaining instances of its use that =
are bad. So whether 6to4 is tagged Historic or not, it should be causing =
significantly less harm. =20

To clarify, I am in favour.

Tim


From gih@apnic.net  Tue Jul 26 08:14:30 2011
Return-Path: <gih@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C66D21F8880 for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 08:14:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.039
X-Spam-Level: 
X-Spam-Status: No, score=-99.039 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_DYNAMIC_DHCP=1.398,  HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ngW6G5652Oyi for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 08:14:29 -0700 (PDT)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id 575F221F867E for <ietf@ietf.org>; Tue, 26 Jul 2011 08:14:29 -0700 (PDT)
Received: from dhcp-53a2.meeting.ietf.org (unknown [130.129.83.162]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id A2393B689A; Wed, 27 Jul 2011 01:14:26 +1000 (EST)
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
Date: Wed, 27 Jul 2011 01:14:16 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <20D2FC69-7C8A-4A01-940A-BEE40E3D47A6@apnic.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
To: Ronald Bonica <rbonica@juniper.net>
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: Tue, 26 Jul 2011 15:14:30 -0000

I'm in favor of the proposed action and the clarification of HISTORIC as =
proposed in the new section.

Geoff


On 26/07/2011, at 12:30 AM, Ronald Bonica wrote:

> Folks,
>=20
> After some discussion, the IESG is attempting to determine whether =
there is IETF consensus to do the following:
>=20
> - add a new section to draft-ietf-v6ops-6to4-to-historic
> - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL
>=20
> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 and =
convert their status to HISTORIC. It will also contain a new section =
describing what it means for RFCs 3056 and 3068 to be classified as =
HISTORIC. The new section will say that:
>=20
> - 6-to-4 should not be configured by default on any implementation =
(hosts, cpe routers, other)
> - vendors will decide whether/when 6-to-4 will be removed from =
implementations. Likewise, operators will decide whether/when 6-to-4 =
relays will be removed from their networks. The status of RFCs 3056 and =
3068 should not be interpreted as a recommendation to remove 6-to-4 at =
any particular time.
>=20
>=20
> draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While it =
clarifies the meaning of "HISTORIC" in this particular case, it does not =
set a precedent for any future case.
>=20
> Please post your views on this course of action by August 8, 2011.
>=20


From ibc@aliax.net  Tue Jul 26 02:47:50 2011
Return-Path: <ibc@aliax.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FDDD21F8B85; Tue, 26 Jul 2011 02:47:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.648
X-Spam-Level: 
X-Spam-Status: No, score=-2.648 tagged_above=-999 required=5 tests=[AWL=0.029,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 a0loMfNDjpZ1; Tue, 26 Jul 2011 02:47:49 -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 7B61021F8B6B; Tue, 26 Jul 2011 02:47:49 -0700 (PDT)
Received: by qyk9 with SMTP id 9so1566559qyk.10 for <multiple recipients>; Tue, 26 Jul 2011 02:47:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.44.36 with SMTP id y36mr474160qce.227.1311673668541; Tue, 26 Jul 2011 02:47:48 -0700 (PDT)
Received: by 10.229.185.195 with HTTP; Tue, 26 Jul 2011 02:47:48 -0700 (PDT)
In-Reply-To: <20110724192948.GD22405@1wt.eu>
References: <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <CALiegf=4K2oWfmZjGMD7J_jyaDtS3i+Mu7R0Wh75Rr+MrQCjtw@mail.gmail.com> <20110722054345.GE18126@1wt.eu> <CALiegfnYm6g63JDHLiSH__r-or3kzK0XCVa3cC7RMP14KWBOSg@mail.gmail.com> <20110724120751.GQ22405@1wt.eu> <CALiegfncavmoMp4YDCeeJ3rsOfHAYQ99itKX2Q2eHB351T3X5A@mail.gmail.com> <20110724184537.GZ22405@1wt.eu> <CALiegfne620wuDMAp235n3mVcXTAnbhhNm8vpiNCy5F7+VD92A@mail.gmail.com> <20110724192948.GD22405@1wt.eu>
Date: Tue, 26 Jul 2011 11:47:48 +0200
Message-ID: <CALiegf=e48kkF+Gky1mY7LippUB-0kZDgSGZrJxk1aZupAGkYw@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Willy Tarreau <w@1wt.eu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 26 Jul 2011 08:21:38 -0700
Cc: Server-Initiated HTTP <hybi@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, 26 Jul 2011 09:47:50 -0000

2011/7/24 Willy Tarreau <w@1wt.eu>:
>> Ok, but what would be the failover solution then? any failover
>> solution can take some time until redirects the client's request to a
>> working server, it's not just a client problem.
>
> This is already addressed by existing web architectures. DNS provides
> geolocation and proposes you the closest working datacenter. BGP ensures
> that this datacenter is always reachable via multiple links and multiple
> providers. Load balancers on the site ensure that only valid servers are
> used. I know some people who configure their load balancers so that a
> server is removed from the pool less than 50ms after a failure or slowdow=
n
> has been noticed. You will never be able to offer that quality of service
> using DNS only, because those 50ms are less than the time it takes for
> most visitors to ping the site.

Yes, but those are expensive server side solutions. I wouldn't like
that a scalable architecture requires so complex solutions (which are
not very suitable in case of usual web hostings). DNS SRV provides a
cheaper way of doing something similar (both ways can live together
thought).



>> Anyhow, don't forget that SRV is not just for failover, but also for
>> load-balancing (you can state that a more powerful server-01 receives
>> 80% of the traffic and server-02 the remaining 20%).
>
> This is already addressed by DNS round robin and used by a lot of sites.

I consider that a hack.


> But keep in mind that DNS is used between *sites* and not *servers*. If
> you use it for servers, you'll fail because you won't be able to silently
> put them in maintenance without disturbing visitors.

SRV provides load-balancing and failover. I never said that SRV is a
solution for temporaly put in maintenance a server.


> Load balancers are
> used for servers. And between sites, people are not seeking imbalanced
> distribution. If they really do, then it's easy using multiple addresses.
>
> Don't take this as an attack (it is not), but you accused Roy of not
> knowing SRV, but I think that you're not much experienced with web
> infrastructures and that may be why you think that SRV is the *only*
> solution to many problems that have been dealt with for ages.

Right, but I'm used to scalable and big SIP infrastructures and DNS
SRV is used for that (along with server side solutions as SIP load
balancers). What I say is that web infraestructures cannot use SRV
mechanism so it's not valid for me that just current HTTP solutions
are valid for any other new protocol.

In contrast it seems that for many people the hacks existing in HTTP
world (www.facebook.com resolves to a single IP) is the only way to go
for a scalable infraestructure "so DNS SRV is not needed". Why so many
efforts in disallowing an *optional* mechanism like SRV? If somebody
does not like it, just don't use it.


Regards.


--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From lars.eggert@nokia.com  Mon Jul 25 09:12:16 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 6400011E8150; Mon, 25 Jul 2011 09:12:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.223
X-Spam-Level: 
X-Spam-Status: No, score=-102.223 tagged_above=-999 required=5 tests=[AWL=-0.423, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ehkPzhZtYeKj; Mon, 25 Jul 2011 09:12:15 -0700 (PDT)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by ietfa.amsl.com (Postfix) with ESMTP id 0CE1321F8559; Mon, 25 Jul 2011 07:48:56 -0700 (PDT)
Received: from mail.fit.nokia.com (esdhcp030222.research.nokia.com [172.21.30.222]) by mgw-da02.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p6PEmqiX002694 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 25 Jul 2011 17:48:54 +0300
From: Lars Eggert <lars.eggert@nokia.com>
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.97.1 at fit.nokia.com
Content-Type: multipart/signed; boundary=Apple-Mail-19-438156695; protocol="application/pkcs7-signature"; micalg=sha1
Subject: [irsg] Final Agenda: IRTF Open Meeting at IETF-81
Date: Mon, 25 Jul 2011 10:48:41 -0400
Message-Id: <DC458255-AE1E-4CEF-8A50-83FE6936397B@nokia.com>
To: <irtf-discuss@irtf.org>, <irtf-announce@irtf.org>, <irsg@irtf.org>, <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); Mon, 25 Jul 2011 17:48:45 +0300 (EEST)
X-Nokia-AV: Clean
X-Mailman-Approved-At: Tue, 26 Jul 2011 08:21:43 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: irtf-discuss@irtf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 16:12:16 -0000

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

Hi,

The final agenda for the IRTF Open Meeting is available at =
http://www.ietf.org/proceedings/81/agenda/IRTF.txt

Please note that the meeting is *Wednesday* at 09:00 and not Thursday, =
as originally scheduled and still listed on the printed agenda.

Lars=

--Apple-Mail-19-438156695
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
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDcyNTE0NDg0MlowIwYJKoZIhvcNAQkE
MRYEFLpJiBCppMxGaaODivH6X7tOqk47MIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
ADwuChrhY5Ia8oeeXHQceo2vRl2fDhf4ExOzIRaYVyFhelBX3RqIbcxOwxgp0jwEXl07weMbAtQo
NmReRZ94iRTjpqIYOOLqlZVHCYqy8H+FS89RwbuX65cPQXIZ4DrVLD2c18y8pKI58Doy7Adp++aD
8RZOZes38hum8icnXxUWeHWrVp4qSL2I8WpVAPfZZvQXxBrGHl14XjDvSLflm2k/ubw7lqWAiGxn
M1Tjow9fbKpf16/nAPuAx1rp3AsX+Ug23jXJsNKRDuHe92d67urF8h3m4trQ1//mqbcs1aISUoTF
aE4TPAzE9uA0JLe30awFrd7xiU1wQcrUTFKdbykAAAAAAAA=

--Apple-Mail-19-438156695--

From kathleen.moriarty@emc.com  Mon Jul 25 09:16:23 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 F02CA21F8C60; Mon, 25 Jul 2011 09:16:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.299
X-Spam-Level: 
X-Spam-Status: No, score=-5.299 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IEcAe+9Hb3nJ; Mon, 25 Jul 2011 09:16:21 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 8533A21F8B2C; Mon, 25 Jul 2011 09:05:14 -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 p6PG5CFt006749 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 25 Jul 2011 12:05:12 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Mon, 25 Jul 2011 12:04:58 -0400
Received: from mxhub05.corp.emc.com (mxhub05.corp.emc.com [128.221.46.113]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p6PG4tS6032529; Mon, 25 Jul 2011 12:04:56 -0400
Received: from mx06a.corp.emc.com ([169.254.1.199]) by mxhub05.corp.emc.com ([128.221.46.113]) with mapi; Mon, 25 Jul 2011 12:04:56 -0400
From: <kathleen.moriarty@emc.com>
To: <trammell@tik.ee.ethz.ch>, <ietf@ietf.org>, <saag@ietf.org>, <mile@ietf.org>
Date: Mon, 25 Jul 2011 12:03:01 -0400
Subject: RE: [mile] MILE side meeting, IETF81 in Quebec, Monday night July 25th
Thread-Topic: [mile] MILE side meeting, IETF81 in Quebec, Monday night July 25th
Thread-Index: Acw/1zHu8XSL9OlJSqS/YBLsoFS60QLDSImh
Message-ID: <AE31510960917D478171C79369B660FA0E051CE712@MX06A.corp.emc.com>
References: <AE31510960917D478171C79369B660FA0E03253CAF@MX06A.corp.emc.com>, <A7CB63B8-DBE2-4862-BA76-9C0BFECBC725@tik.ee.ethz.ch>
In-Reply-To: <A7CB63B8-DBE2-4862-BA76-9C0BFECBC725@tik.ee.ethz.ch>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Tue, 26 Jul 2011 08:21:43 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 16:16:23 -0000

Hello,

Tonight's side meeting for MILE will be held in Room 301A, starting right a=
fter the plenary at 19:30 EST.  We plan to use the following bridge number =
for those who could not be here in person:

Dial-in: 857.207.4204,   1, 60363236#
Global access numbers are listed at the end of this message.

Thank you,
Kathleen & Brian


________________________________________
From: mile-bounces@ietf.org [mile-bounces@ietf.org] On Behalf Of Brian Tram=
mell [trammell@tik.ee.ethz.ch]
Sent: Monday, July 11, 2011 10:30 AM
To: ietf@ietf.org; saag@ietf.org
Cc: mile@ietf.org
Subject: [mile] MILE side meeting, IETF81 in Quebec, Monday night July 25th

Greetings, all,

To help us plan a bit for the (previously-announced) MILE pre-WG side meeti=
ng in Quebec, 19:30 Monday 25 July, after the technical plenary meeting, pl=
ease let us know if you are interested in attending by filling out the dood=
le at:

http://www.doodle.com/e2w494tce6knmq6m

The working proposed charter is attached below for reference. Further detai=
ls will be announced later.

Many thanks, and best regards,

Brian and Kathleen

Managed Incident Lightweight Exchange (mile)
--------------------------------------------

Proposed Working Group Charter

Chairs:
    Kathleen Moriarty <kathleen.moriarty@emc.com>
    Brian Trammell <trammell@tik.ee.ethz.ch>

Security Area Directors:
    Stephen Farrell <stephen.farrell@cs.tcd.ie<mailto:stephen.farrell@cs.tc=
d.ie>>
    Sean Turner <turners@ieca.com<mailto:turners@ieca.com>>

Security Area Advisor:
    Sean Turner <turners@ieca.com>

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

Description:

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 im
portant. Efforts continue to deploy IODEF and RID, as well as to extend the=
m to support specific use cases covering reporting and mitigation of curren=
t 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 othe=
r 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 confi=
rmed 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

_______________________________________________
mile mailing list
mile@ietf.org
https://www.ietf.org/mailman/listinfo/mile



Global Access Numbers
=95	Toll-free number
Freefone number that participants can use to dial in to your call and will =
not be charged.
=95	International toll dial-in number
Toll number available globally. Use when neither toll-free nor local toll i=
s listed for your country.
=95	Local toll dial-in number
Local, in-country numbers that incur a local call charge. Use when no toll-=
free number is listed for your country.
If your country isn't listed below, please use +1 857 207 4204

Note (as of 6/30/11): There are new toll free dial-in numbers for Mexico an=
d Brazil. The new Mexico toll free dial-in number is listed below. For the =
new Brazil toll free dial-in number, please contact the help desk. Please b=
e sure to use these numbers for all future meetings, as the prior numbers (=
not listed) will be disconnected on July 31.
If you are dialing from Ecuador, Egypt, Ghana, Honduras, India, Jordan or T=
urkey, please click here for additional dialing instructions
For Philippines dial-in number, please contact the Help desk
Country	Toll-free #	Local toll dial-in #	Int'l toll dial-in #
Antigua	18009881093	 	=20
Argentina	08006663580	053541170	+54 53541170
Australia	1800107895	 	=20
Australia	1800097161	01280238327	+61 1280238327
Austria	0800293883	01206091042	+43 1206091042
Bahamas	18009887511	 	=20
Bahrain	80004370	 	=20
Belgium	080080799	022006492	+32 22006492
Bolivia	800100617	 	=20
Chile	12300200430	 	=20
China
108007121934 (Netcom only)	 	=20
China
108001201934 (Telecom only)	4008811625 (Netcom, Telecom and all mobile acce=
ss)	+86 4008811625 (Netcom, Telecom and all mobile access)
China
 	4001200029 (Netcom, Telecom and China Mobile)	+86 4001200029 (Netcom, Tel=
ecom and China Mobile)
Colombia	018009440105	 	=20
Costa Rica	08000440080	 	=20
Cyprus	80092424	 	=20
Czech Republic	800142864	239014112	+420 239014112
Denmark	80889478	43682063	+45 43682063
Dominican Republic	18888038749	 	=20
Ecuador	8009887511 (Click here for access code to dial before dialing numbe=
r)
 	=20
Egypt	08000000271	 	=20
Egypt	8885409783 (Click here for access code to dial before dialing number)
 	=20
Estonia	8000044320	 	=20
Finland	0800919478	0972519186	+358 972519186
France	0805540147	0157323313	+33 157323313
Germany	08006646745	06950985552	+49 6950985552
Ghana	 	217013261	+233 217013261
Greece	0080044145248	 	=20
Grenada	18009881111	 	=20
Honduras	8009887511 (Click here for access code to dial before dialing numb=
er)
 	=20
Hong Kong	800930871	30114650	+852 30114650
Hungary	0680016578	0617779141	+36 17779141
Iceland	8008880	 	=20
India	0008004401562	 	=20
India	8006981070 (Click here for access code to dial before dialing number)
 	=20
Indonesia	001803441067	 	=20
Ireland	1800882434	012420715	+353 12420715
Israel	1809440999	 	=20
Italy	800871598	0291483215	+39 0291483215
Jamaica	18009881120	 	=20
Japan	0120925830	0357679520	+81 357679520
Jordan	8009887511 (Click here for access code to dial before dialing number=
)
 	=20
Latvia	80002944	 	=20
Lithuania	880030687	 	=20
Luxembourg	80024059	24871035	+352 24871035
Malaysia	1800814162	0362074117	+60 362074117
Mexico	018005630627	 	=20
Netherlands	08000201642	0202008462	+31 202008462
New Zealand	0800991168	099164905	+64 99164905
Norway	80010740	24159766	+47 24159766
Panama	008000441121	 	=20
Peru	080053571	 	=20
Poland	008004421075	0223060053	+48 223060053
Portugal	800844676	217616089	+351 217616089
Romania	0800894796	 	=20
Russia	81080022381044	84992722055	+7 4992722055
Saudi Arabia	8008444687	 	=20
Singapore	8004481568	66221240	+65 66221240
South Africa	0800166372	 	=20
South Korea	007984420995	0234837092	+82 234837092
Spain	900811826	912754650	+34 912754650
Sweden	020790087	0851761388	+46 851761388
Switzerland	0800562306	0445118108	+41 445118108
Taiwan	00801444395	0221621838	+886 221621838
Thailand	0018004411019	 	=20
Turkey	00800448829160	 	=20
Turkey	8885409783 (Click here for access code to dial before dialing number=
)
 	=20
United Arab Emirates	80004414961	 	=20
United Kingdom	08001214662	02030249140	+44 2030249140
United States	8886433084	18572074204	+1 8572074204
Venezuela	08001766485	 	=20

From ibc@aliax.net  Tue Jul 26 02:58:42 2011
Return-Path: <ibc@aliax.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE70021F8C3B; Tue, 26 Jul 2011 02:58:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[AWL=-0.272, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_24=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 0DCzfhbsPIPk; Tue, 26 Jul 2011 02:58:42 -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 2B71821F8C38; Tue, 26 Jul 2011 02:58:42 -0700 (PDT)
Received: by qwc23 with SMTP id 23so174477qwc.31 for <multiple recipients>; Tue, 26 Jul 2011 02:58:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.44.36 with SMTP id y36mr480884qce.227.1311674321537; Tue, 26 Jul 2011 02:58:41 -0700 (PDT)
Received: by 10.229.185.195 with HTTP; Tue, 26 Jul 2011 02:58:41 -0700 (PDT)
In-Reply-To: <20110724204236.GG22405@1wt.eu>
References: <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <9031.1311286867.939466@puncture> <4E28BA9D.6010501@callenish.com> <CAP992=GedTEfimykCWwdwm=BsZdwFRJO36EO0a_o7iejURJ+tQ@mail.gmail.com> <CALiegfnwNyYDy=SyrqHJXV0ZreADb7F8QySvgdHofW9Hm9miZQ@mail.gmail.com> <CABLsOLCgxDNDs54GUybBzmG8a6rNPzXzFcwf_OU25j5L+AobaQ@mail.gmail.com> <CALiegfnp+kNqnU-_x2ZBZnN8fzP=4+6WO=QPjw1rJzvZmSXEAg@mail.gmail.com> <20110724185949.GB22405@1wt.eu> <9031.1311538720.416128@puncture> <20110724204236.GG22405@1wt.eu>
Date: Tue, 26 Jul 2011 11:58:41 +0200
Message-ID: <CALiegfkgukeaiMR-Yc15qUJYCB-KPcoNoX4G6NrN4+DOiDS+tw@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Willy Tarreau <w@1wt.eu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 26 Jul 2011 08:21:42 -0700
Cc: Server-Initiated HTTP <hybi@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, 26 Jul 2011 09:58:42 -0000

2011/7/24 Willy Tarreau <w@1wt.eu>:
> To ensure nobody gets me wrong, I'm certain this can help solve issues
> *if this is optional*. If it becomes a MUST, then the negative effects
> will override the positive ones. In my opinion, the client should decide
> whether to enable it or not.

But I don't understand how a client is supposed to decide by himself
how to resolve a URI destination. If I give you my vcard containing my
SIP/XMPP/MAILTO URIs, I must expect that you would use *standarized*
mechanisms to locate the server for each service. In fact, in all
these cases (SIP, XMPP; MAILTO) the URI domain can point to several
IP:port (due to NAPTR / SRV / MX DNS records).

BTW: I know that any web browser would first lookup at the /etc/hosts
file when an URI is introduced. This would "replace" a DNS A/AAAA
query. Maybe NIS or whatever could also be used for this. It does not
break SIP/XMPP/MAILTO URI's resolutions: Initially NAPTR / SRV / MX
query would be performed and, if there is no such record (or there is
so we get hostnames for which DNS A must be performed) then the client
can check /etc/hosts for the "A" resolution (domain -> IP).

--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From ibc@aliax.net  Tue Jul 26 03:04:45 2011
Return-Path: <ibc@aliax.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B46921F8A80; Tue, 26 Jul 2011 03:04:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.645
X-Spam-Level: 
X-Spam-Status: No, score=-2.645 tagged_above=-999 required=5 tests=[AWL=0.032,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 H5h4-X4HRqk7; Tue, 26 Jul 2011 03:04:45 -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 02ABE21F8A70; Tue, 26 Jul 2011 03:04:44 -0700 (PDT)
Received: by qwc23 with SMTP id 23so177553qwc.31 for <multiple recipients>; Tue, 26 Jul 2011 03:04:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.179.193 with SMTP id br1mr4419596qab.222.1311674684462; Tue, 26 Jul 2011 03:04:44 -0700 (PDT)
Received: by 10.229.185.195 with HTTP; Tue, 26 Jul 2011 03:04:44 -0700 (PDT)
In-Reply-To: <4B3C19FD-B736-4DA7-9DB5-3D433320DCBC@network-heretics.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com> <20110724073323.EEAAF121E985@drugs.dv.isc.org> <4B3C19FD-B736-4DA7-9DB5-3D433320DCBC@network-heretics.com>
Date: Tue, 26 Jul 2011 12:04:44 +0200
Message-ID: <CALiegfmQOGJ4z6dd0nFnZW=5guNrXRtHHS-iGcXO8Sn=LAmZJg@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Keith Moore <moore@network-heretics.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 26 Jul 2011 08:21:43 -0700
Cc: "Roy T. Fielding" <fielding@gbiv.com>, Server-Initiated HTTP <hybi@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, 26 Jul 2011 10:04:45 -0000

2011/7/25 Keith Moore <moore@network-heretics.com>:
> By now, I think the market has long since decided. =C2=A0For better or wo=
rse, the
> mechanism the market chose to use with the web was HTTP redirects.

That's common in HTTP world: too much "cool" stuff on top of it, and
too much noise and hacks below it.

--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From ibc@aliax.net  Tue Jul 26 03:08:21 2011
Return-Path: <ibc@aliax.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51B3421F8B06; Tue, 26 Jul 2011 03:08:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.645
X-Spam-Level: 
X-Spam-Status: No, score=-2.645 tagged_above=-999 required=5 tests=[AWL=0.032,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 8qklTHMLYs+v; Tue, 26 Jul 2011 03:08:20 -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 AF45C21F8A95; Tue, 26 Jul 2011 03:08:20 -0700 (PDT)
Received: by qwc23 with SMTP id 23so179429qwc.31 for <multiple recipients>; Tue, 26 Jul 2011 03:08:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.105.95 with SMTP id s31mr4088194qco.228.1311674900099; Tue, 26 Jul 2011 03:08:20 -0700 (PDT)
Received: by 10.229.185.195 with HTTP; Tue, 26 Jul 2011 03:08:20 -0700 (PDT)
In-Reply-To: <20110725043543.0A49C1222F02@drugs.dv.isc.org>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com> <20110724073323.EEAAF121E985@drugs.dv.isc.org> <4B3C19FD-B736-4DA7-9DB5-3D433320DCBC@network-heretics.com> <20110725032136.A36701222CE2@drugs.dv.isc.org> <3BC48562-6459-4FB9-9806-731AF87FE027@network-heretics.com> <20110725043543.0A49C1222F02@drugs.dv.isc.org>
Date: Tue, 26 Jul 2011 12:08:20 +0200
Message-ID: <CALiegfnvd4RQ+rtn9deu0_a3cmzVAe_GxBp_v+1pb+EyGh6CWA@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Mark Andrews <marka@isc.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 26 Jul 2011 08:21:43 -0700
Cc: "Roy T. Fielding" <fielding@gbiv.com>, Server-Initiated HTTP <hybi@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: Tue, 26 Jul 2011 10:08:21 -0000

2011/7/25 Mark Andrews <marka@isc.org>:
>> But if you really want to use DNS to do redirects for http: URIs (or for=
 =3D
>> that matter ws: URIs or almost any other kind of URI), NAPTR was =3D
>> tailor-made to do that. =C2=A0SRV was not.
>
> "_http._tcp.example.com SRV 100 0 80 <server>" is not a redirect.
> The http client still issues "Host: example.com" not "Host: <server>".
> If you want to do DNS level redirect of "www.example.com" to
> "example.com" then NAPTR would be the way to do that and the http
> client issues "Host: example.com" instead of "Host: www.example.com".

Great explanation.

--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From lionel.morand@orange-ftgroup.com  Tue Jul 26 08:00:12 2011
Return-Path: <lionel.morand@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 42AD721F8B72; Tue, 26 Jul 2011 08:00:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.249
X-Spam-Level: 
X-Spam-Status: No, score=-103.249 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 7APw9jzvZTr5; Tue, 26 Jul 2011 08:00:11 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by ietfa.amsl.com (Postfix) with ESMTP id 4B91121F855C; Tue, 26 Jul 2011 08:00:11 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id C77688C0001; Tue, 26 Jul 2011 17:00:58 +0200 (CEST)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by p-mail1.rd.francetelecom.com (Postfix) with ESMTP id AC1F78B8009; Tue, 26 Jul 2011 17:00:58 +0200 (CEST)
Received: from ftrdmel1.rd.francetelecom.fr ([10.192.128.40]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 26 Jul 2011 17:00: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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: secdir review of draft-ietf-dime-priority-avps-04
Date: Tue, 26 Jul 2011 17:00:08 +0200
Message-ID: <B11765B89737A7498AF63EA84EC9F577BB642A@ftrdmel1>
In-reply-to: <20110726112346.35893ibie0kwerqc@portland.eukhosting.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-topic: secdir review of draft-ietf-dime-priority-avps-04
Thread-index: AcxLho+V4YXq04I3QKSV0cnCnlyypgAGa8Kw
References: <20110726104135.13472eudbij0eaqs@portland.eukhosting.net> <AC6674AB7BC78549BB231821ABF7A9AEB674516F2B@EMBX01-WF.jnpr.net> <20110726112346.35893ibie0kwerqc@portland.eukhosting.net>
From: <lionel.morand@orange-ftgroup.com>
To: <carlberg@g11.org.uk>, <shanna@juniper.net>
X-OriginalArrivalTime: 26 Jul 2011 15:00:09.0713 (UTC) FILETIME=[B6996E10:01CC4BA4]
X-Mailman-Approved-At: Tue, 26 Jul 2011 08:21:43 -0700
Cc: draft-ietf-dime-priority-avps.all@tools.ietf.org, ietf@ietf.org, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 15:00:12 -0000

Hi Steve,

It should be maybe clarified (if required) that this document does not =
create a new protocol/solution. It only defines extensions to an =
existing protocol (Diameter QoS Application), completing a standard list =
of AVPs in order to support a set of parameters already defined in other =
specifications.

So, to be able to use this set of AVPs, you will have first to comply =
with the Diameter base protocol (RFC3588(bis)), the Diameter QoS =
application (RFC5866), the RFC 5624 defining the list of AVP, and all =
the different specifications defining these priority parameters. This =
document does not introduce new security issue. It just relies on =
existing solutions.

I understand therefore the concerns from Ken.

Regards,

Lionel


-----Message d'origine-----
De=A0: carlberg@g11.org.uk [mailto:carlberg@g11.org.uk]=20
Envoy=E9=A0: mardi 26 juillet 2011 13:24
=C0=A0: Stephen Hanna
Cc=A0: ietf@ietf.org; secdir@ietf.org; =
draft-ietf-dime-priority-avps.all@tools.ietf.org; MORAND Lionel =
RD-CORE-ISS
Objet=A0: RE: secdir review of draft-ietf-dime-priority-avps-04

Steve,


Quoting Stephen Hanna <shanna@juniper.net>:

> Thanks for your response, Ken.
>
> Removing the last sentence that you quoted would make things worse.
> Readers of this draft should definitely familiarize themselves with
> the security considerations related to priority. We should make that
> easier, not harder. The fact that those considerations also apply to
> other RFCs does not remove the fact that they apply to this one also.

but those considerations do not directly apply to DIAMETER.

> You cannot publish a document whose security considerations section
> says (as this one effectively does today), "There are lots of security
> considerations related to this document. To understand them, please
> dig through all the referenced documents and figure it out yourself."
> Doing that digging and analysis is the job of the document editors.

agreed, speaking in the general sense.  But again, the security =20
considerations of these other protocols do not apply to the operation =20
of Diameter.

> In order to ease the burden on you, I think a reasonable compromise
> would be for YOU to review the documents referenced and decide which
> have the most relevant security considerations. Then you could list
> those explicitly in the last paragraph of the Security Considerations.

I'm concerned about the implications of your recommendation.  If we =20
extend this position to other work in the IETF, then efforts like =20
defining MIBs would mean that each MIB draft would need to perform a =20
security considerations analysis of each protocol that an objects =20
refers to in the context of SNMP.  And one can extend the argument =20
that each protocol operating on top of TCP (and/or UDP) and IP would =20
need to perform an analysis on how TCP/UDP and IP may affect the upper =20
layer protocol.  We don't do that today.

cheers,

-ken



From alexandru.petrescu@gmail.com  Tue Jul 26 08:37:15 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 677EE21F8661 for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 08:37:15 -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 hXE7alZup2qa for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 08:37:14 -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 9424D21F8640 for <ietf@ietf.org>; Tue, 26 Jul 2011 08:37:14 -0700 (PDT)
Received: by yie30 with SMTP id 30so421716yie.31 for <ietf@ietf.org>; Tue, 26 Jul 2011 08:37:14 -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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=rTQQCISvjiWXXM11dQ7/ZEGr3i/avIX+xsBesDCCNn4=; b=DpaaXKOaSS2ZLSbYSJO++dfzqWMDlWx/y8b/D5kcrIyrJTJwDTkPk9kj22t5iuxgpU skdBd92OAWe5fzFMNNOSH5QYFtMCRtK452id1lFSVmTJpkF7KTX9ZqMux5Idl2opq1Ge lf5H72WfXc+0LElueifGVgM6BBeacJw2djSOM=
Received: by 10.142.248.12 with SMTP id v12mr3741104wfh.134.1311694632847; Tue, 26 Jul 2011 08:37:12 -0700 (PDT)
Received: from [127.0.0.1] (dhcp-150a.meeting.ietf.org [130.129.21.10]) by mx.google.com with ESMTPS id t20sm395863wff.6.2011.07.26.08.37.10 (version=SSLv3 cipher=OTHER); Tue, 26 Jul 2011 08:37:11 -0700 (PDT)
Message-ID: <4E2EDF23.3060804@gmail.com>
Date: Tue, 26 Jul 2011 17:37:07 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: 6to4v2 (as in ripv2)?  (was: draft-ietf-v6ops-6to4-to-historic (yet again))
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 15:37:15 -0000

I jump in the midle of discussion and lazy to dissect emails:

Is there a replacement for historic 6to4?  What should I now install in 
the lab, without interaction to some admin or web page of some core server?

Thanks,

Alex


Le 26/07/2011 15:47, Ronald Bonica a écrit :
> Brian,
>
> Does the following text work for you?
>
>                           Ron
>
>
> N. Meaning of HISTORIC
>
> For the purposes of this document, the term HISTORIC means:
>
> - 6-to-4 should not be configured by default on any implementation (host, cpe router, other)
>
> - Vendors will decide which future versions of their products will support 6-to-4. It is assumed that vendors will continue to support 6-to-4 until a) they are no longer economically incented to do so and b) they are economically incented to remove unused features from their products.
>
> - Operators will decide when to decommission 6-to-4 relays, if ever. It is assumed that operators will continue to operate 6-to-4 relays as long as they are economically incented to do so. When 6-to-4 traffic levels reach zero, operators will probably begin to consider decommissioning.
>
> The status of RFCs 3056 and 3068 should not be interpreted as a recommendation to remove 6-to-4 at any particular time.
>
>
>> -----Original Message-----
>> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
>> Sent: Monday, July 25, 2011 11:09 PM
>> To: Ronald Bonica
>> Cc: ietf@ietf.org
>> Subject: Re: draft-ietf-v6ops-6to4-to-historic (yet again)
>>
>> To be clear, I'd like to see exact proposed text before expressing
>> support for the proposal. The trick is to get 6to4 disabled by default
>> at the user end, without disabling it for users who are getting good
>> service from it.
>>
>> Regards
>>     Brian
>>
>> On 2011-07-26 09:49, Brian E Carpenter wrote:
>>>>   Likewise, operators will decide whether/when 6-to-4 relays will be
>> removed from their networks.
>>>
>>> This is, of course, an undeniable statement of fact (as it is for any
>> other feature
>>> of the Internet). However, it needs to be made clear that doing so
>> *prematurely*
>>> would penalise existing successful users of those relays, and
>> therefore it should
>>> only be done when there is no successful traffic through them. Which
>> is when any
>>> operator would remove them anyway.
>>>
>>> Therefore, I don't see much value in this statement, and possible
>> harm to users.
>>> The ways to avoid such harm as far as possible are already in the RFC
>> Editor
>>> queue.
>>>
>>> Regards
>>>     Brian Carpenter
>>>
>>> On 2011-07-26 02:30, Ronald Bonica wrote:
>>>> Folks,
>>>>
>>>> After some discussion, the IESG is attempting to determine whether
>> there is IETF consensus to do the following:
>>>>
>>>> - add a new section to draft-ietf-v6ops-6to4-to-historic
>>>> - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL
>>>>
>>>> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068
>> and convert their status to HISTORIC. It will also contain a new
>> section describing what it means for RFCs 3056 and 3068 to be
>> classified as HISTORIC. The new section will say that:
>>>>
>>>> - 6-to-4 should not be configured by default on any implementation
>> (hosts, cpe routers, other)
>>>> - vendors will decide whether/when 6-to-4 will be removed from
>> implementations. Likewise, operators will decide whether/when 6-to-4
>> relays will be removed from their networks. The status of RFCs 3056 and
>> 3068 should not be interpreted as a recommendation to remove 6-to-4 at
>> any particular time.
>>>>
>>>>
>>>> draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While it
>> clarifies the meaning of "HISTORIC" in this particular case, it does
>> not set a precedent for any future case.
>>>>
>>>> Please post your views on this course of action by August 8, 2011.
>>>>
>>>>
>>>>
>> Ron Bonica
>>>>
>> <speaking as OPS Area AD>
>>>> _______________________________________________
>>>> 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 shanna@juniper.net  Tue Jul 26 08:38:11 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 BC22311E8119; Tue, 26 Jul 2011 08:38:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HQI0Aw571ayk; Tue, 26 Jul 2011 08:38:10 -0700 (PDT)
Received: from exprod7og117.obsmtp.com (exprod7og117.obsmtp.com [64.18.2.6]) by ietfa.amsl.com (Postfix) with ESMTP id 91D0D11E80C1; Tue, 26 Jul 2011 08:38:06 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob117.postini.com ([64.18.6.12]) with SMTP ID DSNKTi7fWAplrDKZcwv+XK39HNvdC/SXbGVU@postini.com; Tue, 26 Jul 2011 08:38:10 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.2.254.0; Tue, 26 Jul 2011 08:34:29 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Tue, 26 Jul 2011 11:34:28 -0400
From: Stephen Hanna <shanna@juniper.net>
To: "carlberg@g11.org.uk" <carlberg@g11.org.uk>
Date: Tue, 26 Jul 2011 11:34:27 -0400
Subject: RE: secdir review of draft-ietf-dime-priority-avps-04
Thread-Topic: secdir review of draft-ietf-dime-priority-avps-04
Thread-Index: AcxLhoMMZuNcnDQsSYq5r0pigpKbWQAApa0w
Message-ID: <AC6674AB7BC78549BB231821ABF7A9AEB674517339@EMBX01-WF.jnpr.net>
References: <20110726104135.13472eudbij0eaqs@portland.eukhosting.net> <AC6674AB7BC78549BB231821ABF7A9AEB674516F2B@EMBX01-WF.jnpr.net> <20110726112346.35893ibie0kwerqc@portland.eukhosting.net>
In-Reply-To: <20110726112346.35893ibie0kwerqc@portland.eukhosting.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: "lionel.morand@orange-ftgroup.com" <lionel.morand@orange-ftgroup.com>, "draft-ietf-dime-priority-avps.all@tools.ietf.org" <draft-ietf-dime-priority-avps.all@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 15:38:11 -0000

Every RFC author has an obligation to explain in the Security Consideration=
s
section what security issues are likely to arise when this specification is
used and how those issues may be addressed. You can refer to other RFCs if
you like but you cannot ignore the issues or just give a hand wave.

Let me give a specific example. If a user is able to ensure that their phon=
e
calls always get the highest SIP-Resource-Priority, their calls will always
go through, even during a disaster. This will benefit the user so they have
an incentive to do it. However, it may damage the collective if calls from
emergency responders are overridden. For this reason, protection against
active MITM attacks SHOULD be employed when using Priority AVPs.

If you can find an extant RFC that covers the relevant Security Considerati=
ons
for your document, you can point to it and say that readers should review i=
t
because the security considerations for this draft are contained there. But
you must perform a serious security analysis for your document if you want
it to be accepted as an RFC. If the answer is that there are no security
considerations, that's fine. You can say that. But in this case, that's
clearly not the case.

You raised the concern that documents may need to highlight security issues
with underlying protocols upon which they depend. That is true. If you're
depending on a protocol that has a serious security problem that's relevant
to your document, you should explain that problem or point to a document
that does so. If the problem is not relevant to your document, no problem.
One need not consider every possible security issue, just the ones that
are most relevant to your document. In your case, there are real security
issues particular to conveying priority AVPs over Diameter. You should
explain what those considerations are or point to documents that do so.
As for MIBs, take a look at some recent ones and you will see that they
do contain good Security Considerations sections. For example, see
RFC 5834 and RFC 6240.

If you'd like to learn more about how to write a good Security
Considerations section, read RFC 3552. Or ask a security expert
to help you. If you can't be bothered to think about security,
you might as well withdraw your draft from consideration.

Thanks,

Steve

> -----Original Message-----
> From: carlberg@g11.org.uk [mailto:carlberg@g11.org.uk]
> Sent: Tuesday, July 26, 2011 7:24 AM
> To: Stephen Hanna
> Cc: ietf@ietf.org; secdir@ietf.org; draft-ietf-dime-priority-
> avps.all@tools.ietf.org; lionel.morand@orange-ftgroup.com
> Subject: RE: secdir review of draft-ietf-dime-priority-avps-04
>=20
> Steve,
>=20
>=20
> Quoting Stephen Hanna <shanna@juniper.net>:
>=20
> > Thanks for your response, Ken.
> >
> > Removing the last sentence that you quoted would make things worse.
> > Readers of this draft should definitely familiarize themselves with
> > the security considerations related to priority. We should make that
> > easier, not harder. The fact that those considerations also apply to
> > other RFCs does not remove the fact that they apply to this one also.
>=20
> but those considerations do not directly apply to DIAMETER.
>=20
> > You cannot publish a document whose security considerations section
> > says (as this one effectively does today), "There are lots of
> security
> > considerations related to this document. To understand them, please
> > dig through all the referenced documents and figure it out yourself."
> > Doing that digging and analysis is the job of the document editors.
>=20
> agreed, speaking in the general sense.  But again, the security
> considerations of these other protocols do not apply to the operation
> of Diameter.
>=20
> > In order to ease the burden on you, I think a reasonable compromise
> > would be for YOU to review the documents referenced and decide which
> > have the most relevant security considerations. Then you could list
> > those explicitly in the last paragraph of the Security
> Considerations.
>=20
> I'm concerned about the implications of your recommendation.  If we
> extend this position to other work in the IETF, then efforts like
> defining MIBs would mean that each MIB draft would need to perform a
> security considerations analysis of each protocol that an objects
> refers to in the context of SNMP.  And one can extend the argument
> that each protocol operating on top of TCP (and/or UDP) and IP would
> need to perform an analysis on how TCP/UDP and IP may affect the upper
> layer protocol.  We don't do that today.
>=20
> cheers,
>=20
> -ken
>=20


From daedulus@btconnect.com  Tue Jul 26 12:38:59 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 032EF11E8088 for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 12:38:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kkjMKdqka-j8 for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 12:38:58 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr08.btconnect.com [213.123.26.186]) by ietfa.amsl.com (Postfix) with ESMTP id 29C1111E8082 for <ietf@ietf.org>; Tue, 26 Jul 2011 12:38:57 -0700 (PDT)
Received: from host109-153-78-164.range109-153.btcentralplus.com (HELO pc6) ([109.153.78.164]) by c2beaomr08.btconnect.com with SMTP id DSN97138; Tue, 26 Jul 2011 20:38:53 +0100 (BST)
Message-ID: <015a01cc4bc2$d8cc2d60$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Ronald Bonica" <rbonica@juniper.net>, <ietf@ietf.org>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
Date: Tue, 26 Jul 2011 20:35:47 +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.4E2F17CD.0014, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.7.26.184214:17:7.586, ip=109.153.78.164, 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, 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=c2beaomr08.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020A.4E2F17CD.014F,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: Tue, 26 Jul 2011 19:38:59 -0000

It seems strange that this e-mail is not copied to the v6ops list.

I would have expected this first to have been hammered out on the v6ops list
and, if and only if consensus was reached there, the new text be then brought to
the
IETF list.

I realise that, as you spell out, you are seeking IETF consensus but what is
that if the
WG is dead set against it?

Tom Petch


----- Original Message -----
From: "Ronald Bonica" <rbonica@juniper.net>
To: <ietf@ietf.org>
Sent: Monday, July 25, 2011 4:30 PM

> After some discussion, the IESG is attempting to determine whether there is
IETF consensus to do the following:
>
> - add a new section to draft-ietf-v6ops-6to4-to-historic
> - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL
>
> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 and convert
their status to HISTORIC. It will also contain a new section describing what it
means for RFCs 3056 and 3068 to be classified as HISTORIC. The new section will
say that:
>
> - 6-to-4 should not be configured by default on any implementation (hosts, cpe
routers, other)
> - vendors will decide whether/when 6-to-4 will be removed from
implementations. Likewise, operators will decide whether/when 6-to-4 relays will
be removed from their networks. The status of RFCs 3056 and 3068 should not be
interpreted as a recommendation to remove 6-to-4 at any particular time.
>
>
> draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While it clarifies
the meaning of "HISTORIC" in this particular case, it does not set a precedent
for any future case.
>
> Please post your views on this course of action by August 8, 2011.
>
>
>                                                                    Ron Bonica
>                                                                    <speaking
as OPS Area AD>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From joelja@bogus.com  Tue Jul 26 12:51:46 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 4E56511E8080 for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 12:51:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102
X-Spam-Level: 
X-Spam-Status: No, score=-102 tagged_above=-999 required=5 tests=[AWL=-0.600,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_15=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 9fGMB-tDd37o for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 12:51:45 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 693B621F876F for <ietf@ietf.org>; Tue, 26 Jul 2011 12:51:45 -0700 (PDT)
Received: from [IPv6:2001:df8::80:129a:ddff:feb1:e750] ([IPv6:2001:df8:0:80:129a:ddff:feb1:e750]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p6QJpfBs039500 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 26 Jul 2011 19:51:42 GMT (envelope-from joelja@bogus.com)
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
X-Priority: 3
In-Reply-To: <015a01cc4bc2$d8cc2d60$4001a8c0@gateway.2wire.net>
Date: Tue, 26 Jul 2011 15:51:40 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5548FEDC-23DD-4886-A372-419F3DB42301@bogus.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <015a01cc4bc2$d8cc2d60$4001a8c0@gateway.2wire.net>
To: "t.petch" <daedulus@btconnect.com>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [IPv6:2001:418:1::81]); Tue, 26 Jul 2011 19:51:42 +0000 (UTC)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 19:51:46 -0000

On Jul 26, 2011, at 2:35 PM, t.petch wrote:

> It seems strange that this e-mail is not copied to the v6ops list.
>=20
> I would have expected this first to have been hammered out on the =
v6ops list
> and, if and only if consensus was reached there, the new text be then =
brought to
> the
> IETF list.
>=20
> I realise that, as you spell out, you are seeking IETF consensus but =
what is
> that if the
> WG is dead set against it?

The working group adopted the document without the statement. the IESG =
would presumably provide instruction as to what to do next with the =
draft were they to conclude that the compromise was considered =
acceptable by the community.

> Tom Petch
>=20
>=20
> ----- Original Message -----
> From: "Ronald Bonica" <rbonica@juniper.net>
> To: <ietf@ietf.org>
> Sent: Monday, July 25, 2011 4:30 PM
>=20
>> After some discussion, the IESG is attempting to determine whether =
there is
> IETF consensus to do the following:
>>=20
>> - add a new section to draft-ietf-v6ops-6to4-to-historic
>> - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL
>>=20
>> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 =
and convert
> their status to HISTORIC. It will also contain a new section =
describing what it
> means for RFCs 3056 and 3068 to be classified as HISTORIC. The new =
section will
> say that:
>>=20
>> - 6-to-4 should not be configured by default on any implementation =
(hosts, cpe
> routers, other)
>> - vendors will decide whether/when 6-to-4 will be removed from
> implementations. Likewise, operators will decide whether/when 6-to-4 =
relays will
> be removed from their networks. The status of RFCs 3056 and 3068 =
should not be
> interpreted as a recommendation to remove 6-to-4 at any particular =
time.
>>=20
>>=20
>> draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While it =
clarifies
> the meaning of "HISTORIC" in this particular case, it does not set a =
precedent
> for any future case.
>>=20
>> Please post your views on this course of action by August 8, 2011.
>>=20
>>=20
>>                                                                   Ron =
Bonica
>>                                                                   =
<speaking
> as OPS Area AD>
>> _______________________________________________
>> 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 swmike@swm.pp.se  Tue Jul 26 13:04:31 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 8180821F891F for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 13:04:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.257
X-Spam-Level: 
X-Spam-Status: No, score=-2.257 tagged_above=-999 required=5 tests=[AWL=-0.258, BAYES_00=-2.599, J_CHICKENPOX_15=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 eM64xZW9MDIY for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 13:04:31 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id EA5B621F88DD for <ietf@ietf.org>; Tue, 26 Jul 2011 13:04:30 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 0AA2D9E; Tue, 26 Jul 2011 22:04:30 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 053F29C; Tue, 26 Jul 2011 22:04:30 +0200 (CEST)
Date: Tue, 26 Jul 2011 22:04:30 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "t.petch" <daedulus@btconnect.com>
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
In-Reply-To: <015a01cc4bc2$d8cc2d60$4001a8c0@gateway.2wire.net>
Message-ID: <alpine.DEB.2.00.1107262203130.26694@uplift.swm.pp.se>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <015a01cc4bc2$d8cc2d60$4001a8c0@gateway.2wire.net>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 20:04:31 -0000

On Tue, 26 Jul 2011, t.petch wrote:

> I realise that, as you spell out, you are seeking IETF consensus but 
> what is that if the WG is dead set against it?

Depending on who you ask, there was consensus, rough consensus, or no 
consensus about this document. My opinion is that rough consensus was met 
with a few very vocal people against. I support this document.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

From jnc@mercury.lcs.mit.edu  Tue Jul 26 13:14:21 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 C2A9722800E for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 13:14:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.508
X-Spam-Level: 
X-Spam-Status: No, score=-6.508 tagged_above=-999 required=5 tests=[AWL=0.091,  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 ZN+A7hZwK-gh for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 13:14: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 4AEE022800D for <ietf@ietf.org>; Tue, 26 Jul 2011 13:14:21 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 63A6118C0FA; Tue, 26 Jul 2011 16:14:20 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
Message-Id: <20110726201420.63A6118C0FA@mercury.lcs.mit.edu>
Date: Tue, 26 Jul 2011 16:14:20 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 20:14:21 -0000

    > From: "t.petch" <daedulus@btconnect.com> 

    > I realise that ... you are seeking IETF consensus but what is that
    > if the WG is dead set against it?

If the entire WG is against it, that's enough people to (IMO) prevent IETF
consensus -> no IETF rough consensus for this statement.

	Noel

From sm@resistor.net  Tue Jul 26 13:15:12 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 6F7F422800E for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 13:15:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 sjV6WyhM3lEU for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 13:15:09 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D45E22800D for <ietf@ietf.org>; Tue, 26 Jul 2011 13:15:09 -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 p6QKF2SV015592;  Tue, 26 Jul 2011 13:15:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1311711306; bh=tO3p/ofLIEXCaTu4Fa9fOgJWj3jJiiUgSeoC9bJsiUc=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=dfqLntEQzmdzQVq88JTD+aoo6sl9R/MbsZ37dzrSjlGJBJD/MwcIZUXeOUv89IJFY j/SIWc9OidsLTOoHEwsBs+YaPStMywaohEh0AojD3bBGMRi122WdDRvEQZYhryzHv+ RRp47KLYQXsK2lBzLDBRIDnbX6mbUOOdlwsd2/Uc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1311711306; bh=tO3p/ofLIEXCaTu4Fa9fOgJWj3jJiiUgSeoC9bJsiUc=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=Bij+O0+48zeQzyV/28cv0CW4mblEb1v6bDyAocHAclOFfxZugUeEBsiTUrs5+5pZr B0GH32vAFRxgg/2X7vPDdhuLjjM4jUc70dToyQvAfe6y5tR3k21yjVRBtSJPhNo/86 bshbHoUNb+zTcRfBi2M+sTD7PTaD85NKpGD0YTns=
Message-Id: <6.2.5.6.2.20110726122716.08152830@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 26 Jul 2011 12:58:34 -0700
To: Ronald Bonica <rbonica@juniper.net>
From: SM <sm@resistor.net>
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr. net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.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, 26 Jul 2011 20:15:12 -0000

Hi Ron,
At 07:30 AM 7/25/2011, Ronald Bonica wrote:
>draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 
>and convert their status to HISTORIC. It will also contain a new 
>section describing what it means for RFCs 3056 and 3068 to be 
>classified as HISTORIC. The new section will say that:
>
>- 6-to-4 should not be configured by default on any implementation 
>(hosts, cpe routers, other)
>- vendors will decide whether/when 6-to-4 will be removed from 
>implementations. Likewise, operators will decide whether/when 6-to-4 
>relays will be removed from their networks. The status of RFCs 3056 
>and 3068 should not be interpreted as a recommendation to remove 
>6-to-4 at any particular time.
>
>draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While it 
>clarifies the meaning of "HISTORIC" in this particular case, it does 
>not set a precedent for any future case.

The above conflates document labels, Historic in this case, and 
advice to vendors and operators.  Redefining the meaning of Historic 
in a RFC that is not even a BCP is a bad idea.

I am fine of 6-to-4 not to be configured on by default and obsoleting 
RFCs 3056 and 3068.   I do not support the redefinition of Historic 
or the claim that there is IETF Consensus.

Regards,
-sm 


From dotis@mail-abuse.org  Tue Jul 26 13:38:39 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 7D68F21F889A for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 13:38:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.417
X-Spam-Level: 
X-Spam-Status: No, score=-104.417 tagged_above=-999 required=5 tests=[AWL=-1.818, 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 qXny-BhIY6Y2 for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 13:38:38 -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 AA71C21F8892 for <ietf@ietf.org>; Tue, 26 Jul 2011 13:38:38 -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 79C796E0131 for <ietf@ietf.org>; Tue, 26 Jul 2011 20:38:37 +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 E31C2A9443B for <ietf@ietf.org>; Tue, 26 Jul 2011 20:38:37 +0000 (UTC)
Message-ID: <4E2F25CB.2010502@mail-abuse.org>
Date: Tue, 26 Jul 2011 13:38:35 -0700
From: Douglas Otis <dotis@mail-abuse.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <6.2.5.6.2.20110726122716.08152830@resistor.net>
In-Reply-To: <6.2.5.6.2.20110726122716.08152830@resistor.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: Tue, 26 Jul 2011 20:38:39 -0000

On 7/26/11 12:58 PM, SM wrote:
> Hi Ron,
> At 07:30 AM 7/25/2011, Ronald Bonica wrote:
>> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 
>> and convert their status to HISTORIC. It will also contain a new 
>> section describing what it means for RFCs 3056 and 3068 to be 
>> classified as HISTORIC. The new section will say that:
>>
>> - 6-to-4 should not be configured by default on any implementation 
>> (hosts, cpe routers, other)
>> - vendors will decide whether/when 6-to-4 will be removed from 
>> implementations. Likewise, operators will decide whether/when 6-to-4 
>> relays will be removed from their networks. The status of RFCs 3056 
>> and 3068 should not be interpreted as a recommendation to remove 
>> 6-to-4 at any particular time.
>>
>> draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While it 
>> clarifies the meaning of "HISTORIC" in this particular case, it does 
>> not set a precedent for any future case.
>
> The above conflates document labels, Historic in this case, and advice 
> to vendors and operators.  Redefining the meaning of Historic in a RFC 
> that is not even a BCP is a bad idea.
>
> I am fine of 6-to-4 not to be configured on by default and obsoleting 
> RFCs 3056 and 3068.   I do not support the redefinition of Historic or 
> the claim that there is IETF Consensus.
Agreed.

-Doug

From rbonica@juniper.net  Tue Jul 26 13:53:19 2011
Return-Path: <rbonica@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5DA721F8A4B; Tue, 26 Jul 2011 13:53:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.935
X-Spam-Level: 
X-Spam-Status: No, score=-105.935 tagged_above=-999 required=5 tests=[AWL=-0.536, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_15=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 RpBHzEBnR-dJ; Tue, 26 Jul 2011 13:53:19 -0700 (PDT)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id 9E15E21F880C; Tue, 26 Jul 2011 13:53:17 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKTi8pPHPAnYiDzeHEWPt2hMi9ltc+gjFz@postini.com; Tue, 26 Jul 2011 13:53:18 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.2.254.0; Tue, 26 Jul 2011 13:51:29 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Tue, 26 Jul 2011 16:51:29 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: t.petch <daedulus@btconnect.com>, "ietf@ietf.org" <ietf@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Date: Tue, 26 Jul 2011 16:51:27 -0400
Subject: RE: draft-ietf-v6ops-6to4-to-historic  (yet again)
Thread-Topic: draft-ietf-v6ops-6to4-to-historic  (yet again)
Thread-Index: AcxLy6igndDxYpSyTlCEDzUOzhsoVgACgrMg
Message-ID: <13205C286662DE4387D9AF3AC30EF456D3F455A480@EMBX01-WF.jnpr.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <015a01cc4bc2$d8cc2d60$4001a8c0@gateway.2wire.net>
In-Reply-To: <015a01cc4bc2$d8cc2d60$4001a8c0@gateway.2wire.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, 26 Jul 2011 20:53:19 -0000

Tom,

Sorry. I meant to copy both lists. They are both copied now.

                                Ron


> -----Original Message-----
> From: t.petch [mailto:daedulus@btconnect.com]
> Sent: Tuesday, July 26, 2011 2:36 PM
> To: Ronald Bonica; ietf@ietf.org
> Subject: Re: draft-ietf-v6ops-6to4-to-historic (yet again)
>=20
> It seems strange that this e-mail is not copied to the v6ops list.
>=20
> I would have expected this first to have been hammered out on the v6ops
> list
> and, if and only if consensus was reached there, the new text be then
> brought to
> the
> IETF list.
>=20
> I realise that, as you spell out, you are seeking IETF consensus but
> what is
> that if the
> WG is dead set against it?
>=20
> Tom Petch
>=20
>=20
> ----- Original Message -----
> From: "Ronald Bonica" <rbonica@juniper.net>
> To: <ietf@ietf.org>
> Sent: Monday, July 25, 2011 4:30 PM
>=20
> > After some discussion, the IESG is attempting to determine whether
> there is
> IETF consensus to do the following:
> >
> > - add a new section to draft-ietf-v6ops-6to4-to-historic
> > - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL
> >
> > draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068
> and convert
> their status to HISTORIC. It will also contain a new section describing
> what it
> means for RFCs 3056 and 3068 to be classified as HISTORIC. The new
> section will
> say that:
> >
> > - 6-to-4 should not be configured by default on any implementation
> (hosts, cpe
> routers, other)
> > - vendors will decide whether/when 6-to-4 will be removed from
> implementations. Likewise, operators will decide whether/when 6-to-4
> relays will
> be removed from their networks. The status of RFCs 3056 and 3068 should
> not be
> interpreted as a recommendation to remove 6-to-4 at any particular
> time.
> >
> >
> > draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While it
> clarifies
> the meaning of "HISTORIC" in this particular case, it does not set a
> precedent
> for any future case.
> >
> > Please post your views on this course of action by August 8, 2011.
> >
> >
> >
> Ron Bonica
> >
> <speaking
> as OPS Area AD>
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf


From Fred.L.Templin@boeing.com  Tue Jul 26 14:22:07 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 9D0F921F896E for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 14:22:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.452
X-Spam-Level: 
X-Spam-Status: No, score=-6.452 tagged_above=-999 required=5 tests=[AWL=0.147,  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 T6U3TLUnw0d4 for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 14:22:07 -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 E139321F87ED for <ietf@ietf.org>; Tue, 26 Jul 2011 14:22:06 -0700 (PDT)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by slb-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p6QLM1hQ015706 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 26 Jul 2011 14:22:02 -0700 (PDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id p6QLM0JN003547; Tue, 26 Jul 2011 16:22:00 -0500 (CDT)
Received: from XCH-NWHT-01.nw.nos.boeing.com (xch-nwht-01.nw.nos.boeing.com [130.247.70.222]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p6QLLxe2003475 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 26 Jul 2011 16:22:00 -0500 (CDT)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-01.nw.nos.boeing.com ([130.247.70.222]) with mapi; Tue, 26 Jul 2011 14:22:00 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ronald Bonica <rbonica@juniper.net>, "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 26 Jul 2011 14:21:59 -0700
Subject: RE: draft-ietf-v6ops-6to4-to-historic  (yet again)
Thread-Topic: draft-ietf-v6ops-6to4-to-historic  (yet again)
Thread-Index: AcxK13EXQuzfLCzMQFivvvTkow95TgBAcbxA
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65C76DE4F47@XCH-NW-01V.nw.nos.boeing.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 21:22:07 -0000

Ron,

I believe 'draft-ietf-v6ops-6to4-advisory' is both
necessary and sufficient regardless of whether
"historic" is an appropriate characterization. So,
I don't think we need this document.

Thanks - Fred
fred.l.templin@boeing.com =20

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On=20
> Behalf Of Ronald Bonica
> Sent: Monday, July 25, 2011 7:31 AM
> To: ietf@ietf.org
> Subject: draft-ietf-v6ops-6to4-to-historic (yet again)
>=20
> Folks,
>=20
> After some discussion, the IESG is attempting to determine=20
> whether there is IETF consensus to do the following:
>=20
> - add a new section to draft-ietf-v6ops-6to4-to-historic
> - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL
>=20
> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and=20
> 3068 and convert their status to HISTORIC. It will also=20
> contain a new section describing what it means for RFCs 3056=20
> and 3068 to be classified as HISTORIC. The new section will say that:
>=20
> - 6-to-4 should not be configured by default on any=20
> implementation (hosts, cpe routers, other)
> - vendors will decide whether/when 6-to-4 will be removed=20
> from implementations. Likewise, operators will decide=20
> whether/when 6-to-4 relays will be removed from their=20
> networks. The status of RFCs 3056 and 3068 should not be=20
> interpreted as a recommendation to remove 6-to-4 at any=20
> particular time.
>=20
>=20
> draft-ietf-v6ops-6to4-to-historic will not update RFC 2026.=20
> While it clarifies the meaning of "HISTORIC" in this=20
> particular case, it does not set a precedent for any future case.
>=20
> Please post your views on this course of action by August 8, 2011.
>=20
>=20
>                                                              =20
>      Ron Bonica
>                                                              =20
>      <speaking as OPS Area AD>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> =

From jhw@apple.com  Tue Jul 26 15:11:22 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 930A521F8782 for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 15:11:22 -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 XX9fCVgUQqfI for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 15:11:22 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 1AACA21F877F for <ietf@ietf.org>; Tue, 26 Jul 2011 15:11:22 -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 <0LOY004O1O98B0C0@mail-out.apple.com> for ietf@ietf.org; Tue, 26 Jul 2011 15:11:19 -0700 (PDT)
X-AuditID: 1180711d-b7c5fae000001427-1e-4e2f3b3e3e9f
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 relay13.apple.com (Apple SCV relay) with SMTP id 0D.FA.05159.E3B3F2E4; Tue, 26 Jul 2011 15:10:06 -0700 (PDT)
Received: from [17.153.16.23] (unknown [17.153.16.23]) by kencur.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LOY001P6OATUD50@kencur.apple.com> for ietf@ietf.org; Tue, 26 Jul 2011 15:11:18 -0700 (PDT)
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
From: james woodyatt <jhw@apple.com>
In-reply-to: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
Date: Tue, 26 Jul 2011 18:11:16 -0400
Message-id: <46B9B2CA-3A7A-40F4-9164-5608C48DCF18@apple.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
To: Ronald Bonica <rbonica@juniper.net>
X-Mailer: Apple Mail (2.1244.3)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsUiON1OTdfOWt/PYNpFfYtnG+ezODB6LFny kymAMYrLJiU1J7MstUjfLoEr49DUjewFD/kqvq+cyNrA2MLTxcjJISFgInFs7z8mCFtM4sK9 9WxdjFwcQgLtTBLrG+YzgyR4BQQlfky+x9LFyMHBLCAvcfC8LEiYWUBL4vujVhaI+slMEr0z rrODJIQFrCXezr8ONpRNQEXi2+W7YDangI/EuwWNbCBzWARUJc7sdYCYoyxx9OsNdohVNhJT 3hwBKxcS8JZ4N20x2AkiAuoSj1dNY4O4U15icctnxgmMArOQXDcL4bpZSK5bwMi8ilGwKDUn sdLQWC+xoCAnVS85P3cTIyjsGgpldzDu/8l/iFGAg1GJh5dpsq6fEGtiWXFl7iFGCQ5mJRHe Hf/1/IR4UxIrq1KL8uOLSnNSiw8xSnOwKInzZv1Q9RMSSE8sSc1OTS1ILYLJMnFwSjUwFp84 /dM68k2/jvXsLdnvXOwqf83Rfm79ruHk1N2dSZEeGjm1boL/0oUFLnJtrCtt/Dh71cppsotz ciNVrITc1rdFnF5TfWP76ccS225fusPPeWTas+i7zUWe0wqeWDNMeGy3N2OD80+RmnyOf9m7 OKeVbVnHzLT735LEy5tyjwXM/71z3t/JB5VYijMSDbWYi4oTAQgT7DQ3AgAA
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, 26 Jul 2011 22:11:22 -0000

On Jul 25, 2011, at 10:30 AM, Ronald Bonica wrote:
> 
> Please post your views on this course of action by August 8, 2011.

I remain convinced that this document is unnecessary and publishing it would be silly, at best, and at worst, the simultaneous publication of 6to4-to-historic alongside 6to4-advisory, which implicitly contradict one another-- the latter says that 6to4 has an indefinite future and here's how to keep everything operational in its presence on the Internet; the former says 6to4 has no future, and it should not be used by anyone for any purpose-- may turn out to be an embarrassment for IETF.  IESG should feel very nervous about claiming there is consensus to publish this draft.  It does not appear to me like there is a rough consensus for it.

That said, I won't complain too loudly if this draft is published.  It would give me cover to ask my employers for 6to4 capability to be removed from forthcoming products that I mainly work to support.  I don't like taking features away from users when there isn't a suitable upgrade path for them, but the truth is that fielding problems from the field resulting from 6to4 failure can be pretty tiresome, and I would welcome the cover from IETF to be able to say, "Oh, you're still using 6to4?  You should turn that off.  It's deprecated by IETF now, and accordingly, we no longer support it.  Get native IPv6 service."

In other words, whether IESG means to convey this message or not, publishing 6to4-to-historic alongside the existing 6to4-advisory-- without any clear phase-out plan-- will pretty clearly imply to people like me that the official phase-out plan is to remove 6to4 from the Internet, starting as soon as vendors and operators are independently able to do so.  "Start the engines of destruction."


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From brian.e.carpenter@gmail.com  Tue Jul 26 15:49:59 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 B3A215E800F; Tue, 26 Jul 2011 15:49:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.602
X-Spam-Level: 
X-Spam-Status: No, score=-103.602 tagged_above=-999 required=5 tests=[AWL=-0.003, 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 xnygh4xiYp+p; Tue, 26 Jul 2011 15:49:59 -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 DA0F55E8008; Tue, 26 Jul 2011 15:49:58 -0700 (PDT)
Received: by iye7 with SMTP id 7so1243384iye.31 for <multiple recipients>; Tue, 26 Jul 2011 15:49:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=GxQvPpBwJ09EeJvLhuKOTUJNaWNvRcG9pXNk+gThJOM=; b=SbgzHVXzyPXzf/QNunIDJ5BWQdftIiNqzNaWYvYn4ovM0PFcJzWZ+00t3V9xODJbkS oV2UKJGCH19zvOWCM9IQHkvLUqX5AKDiXOqaOTINammO0Luk35T1pwTHJDgSQ+pEtTFF DDYgPYoYxW/jkOt9BIeEZu6yv/80mNMlgsUlw=
Received: by 10.43.134.74 with SMTP id ib10mr13646icc.485.1311720598099; Tue, 26 Jul 2011 15:49:58 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id a9sm1247351icy.6.2011.07.26.15.49.55 (version=SSLv3 cipher=OTHER); Tue, 26 Jul 2011 15:49:57 -0700 (PDT)
Message-ID: <4E2F4491.30102@gmail.com>
Date: Wed, 27 Jul 2011 10:49:53 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: 6to4v2 (as in ripv2)? 
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com>	<4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com>
In-Reply-To: <4E2EDF23.3060804@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <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, 26 Jul 2011 22:49:59 -0000

Alex,

Since 6to4 is a transition mechanism it has no long term future
*by definition*. Even if someone chooses to design a v2, who is going to
implement it?

If you have a reason to install and enable 6to4, why would the nominal
status of a couple of RFCs make you do anything different?

Of course, if implementors choose to drop the code you might not be
able to upgrade software versions - but hopefully by that time you
will have native IPv6 service anyway.

Regards
   Brian Carpenter

On 2011-07-27 03:37, Alexandru Petrescu wrote:
> I jump in the midle of discussion and lazy to dissect emails:
>=20
> Is there a replacement for historic 6to4?  What should I now install in=

> the lab, without interaction to some admin or web page of some core ser=
ver?
>=20
> Thanks,
>=20
> Alex
>=20
>=20
> Le 26/07/2011 15:47, Ronald Bonica a =C3=A9crit :
>> Brian,
>>
>> Does the following text work for you?
>>
>>                           Ron
>>
>>
>> N. Meaning of HISTORIC
>>
>> For the purposes of this document, the term HISTORIC means:
>>
>> - 6-to-4 should not be configured by default on any implementation
>> (host, cpe router, other)
>>
>> - Vendors will decide which future versions of their products will
>> support 6-to-4. It is assumed that vendors will continue to support
>> 6-to-4 until a) they are no longer economically incented to do so and
>> b) they are economically incented to remove unused features from their=

>> products.
>>
>> - Operators will decide when to decommission 6-to-4 relays, if ever.
>> It is assumed that operators will continue to operate 6-to-4 relays as=

>> long as they are economically incented to do so. When 6-to-4 traffic
>> levels reach zero, operators will probably begin to consider
>> decommissioning.
>>
>> The status of RFCs 3056 and 3068 should not be interpreted as a
>> recommendation to remove 6-to-4 at any particular time.
>>
>>
>>> -----Original Message-----
>>> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
>>> Sent: Monday, July 25, 2011 11:09 PM
>>> To: Ronald Bonica
>>> Cc: ietf@ietf.org
>>> Subject: Re: draft-ietf-v6ops-6to4-to-historic (yet again)
>>>
>>> To be clear, I'd like to see exact proposed text before expressing
>>> support for the proposal. The trick is to get 6to4 disabled by defaul=
t
>>> at the user end, without disabling it for users who are getting good
>>> service from it.
>>>
>>> Regards
>>>     Brian
>>>
>>> On 2011-07-26 09:49, Brian E Carpenter wrote:
>>>>>   Likewise, operators will decide whether/when 6-to-4 relays will b=
e
>>> removed from their networks.
>>>>
>>>> This is, of course, an undeniable statement of fact (as it is for an=
y
>>> other feature
>>>> of the Internet). However, it needs to be made clear that doing so
>>> *prematurely*
>>>> would penalise existing successful users of those relays, and
>>> therefore it should
>>>> only be done when there is no successful traffic through them. Which=

>>> is when any
>>>> operator would remove them anyway.
>>>>
>>>> Therefore, I don't see much value in this statement, and possible
>>> harm to users.
>>>> The ways to avoid such harm as far as possible are already in the RF=
C
>>> Editor
>>>> queue.
>>>>
>>>> Regards
>>>>     Brian Carpenter
>>>>
>>>> On 2011-07-26 02:30, Ronald Bonica wrote:
>>>>> Folks,
>>>>>
>>>>> After some discussion, the IESG is attempting to determine whether
>>> there is IETF consensus to do the following:
>>>>>
>>>>> - add a new section to draft-ietf-v6ops-6to4-to-historic
>>>>> - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL
>>>>>
>>>>> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068
>>> and convert their status to HISTORIC. It will also contain a new
>>> section describing what it means for RFCs 3056 and 3068 to be
>>> classified as HISTORIC. The new section will say that:
>>>>>
>>>>> - 6-to-4 should not be configured by default on any implementation
>>> (hosts, cpe routers, other)
>>>>> - vendors will decide whether/when 6-to-4 will be removed from
>>> implementations. Likewise, operators will decide whether/when 6-to-4
>>> relays will be removed from their networks. The status of RFCs 3056 a=
nd
>>> 3068 should not be interpreted as a recommendation to remove 6-to-4 a=
t
>>> any particular time.
>>>>>
>>>>>
>>>>> draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While i=
t
>>> clarifies the meaning of "HISTORIC" in this particular case, it does
>>> not set a precedent for any future case.
>>>>>
>>>>> Please post your views on this course of action by August 8, 2011.
>>>>>
>>>>>
>>>>>
>>> Ron Bonica
>>>>>
>>> <speaking as OPS Area AD>
>>>>> _______________________________________________
>>>>> 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
>=20


From brian.e.carpenter@gmail.com  Tue Jul 26 15:57: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 8F55121F86D8; Tue, 26 Jul 2011 15:57:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.602
X-Spam-Level: 
X-Spam-Status: No, score=-103.602 tagged_above=-999 required=5 tests=[AWL=-0.003, 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 Q1K+XzdPvBUY; Tue, 26 Jul 2011 15:57:01 -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 B114421F8586; Tue, 26 Jul 2011 15:57:00 -0700 (PDT)
Received: by yie30 with SMTP id 30so803558yie.31 for <multiple recipients>; Tue, 26 Jul 2011 15:57:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=582CK1HOgKZANKFQtTl4FUTHAhtESPdSFcl1iJHPfEY=; b=TJxuGCbcjiXRSGNVaiTxXwQBkMJE/uZQpElwxnzzkPvCvV2OQMARqA0fRwYEiblHY1 SzNi+QOyJcdukkTITVLa+CWoRBvBEEwPA9FWHq1EGd2a6Uf2/G/4IVUZxQPJIK4nTaiW SRFar3zVRl18jZDwvM6ssoSQ72QXZmth/u76g=
Received: by 10.42.155.74 with SMTP id t10mr15500icw.527.1311721019761; Tue, 26 Jul 2011 15:56:59 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id h6sm1261152icy.1.2011.07.26.15.56.57 (version=SSLv3 cipher=OTHER); Tue, 26 Jul 2011 15:56:59 -0700 (PDT)
Message-ID: <4E2F4637.3060409@gmail.com>
Date: Wed, 27 Jul 2011 10:56:55 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <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, 26 Jul 2011 22:57:01 -0000

Ron,

The normal typography is 6to4, not 6-to-4. I assume the draft will
still refer to [I-D.ietf-v6ops-6to4-advisory]. Given that, I believe
the draft should proceed.

I definitely disagree with those who say this would be a misuse of
"Historic"; the words in RFC 2026 certainly cover this case
("for any other reason considered to be obsolete").

Regards
   Brian Carpenter

On 2011-07-27 01:47, Ronald Bonica wrote:
> Brian,
> 
> Does the following text work for you?
> 
>                          Ron
> 
> 
> N. Meaning of HISTORIC
> 
> For the purposes of this document, the term HISTORIC means:
> 
> - 6-to-4 should not be configured by default on any implementation (host, cpe router, other)
> 
> - Vendors will decide which future versions of their products will support 6-to-4. It is assumed that vendors will continue to support 6-to-4 until a) they are no longer economically incented to do so and b) they are economically incented to remove unused features from their products.
> 
> - Operators will decide when to decommission 6-to-4 relays, if ever. It is assumed that operators will continue to operate 6-to-4 relays as long as they are economically incented to do so. When 6-to-4 traffic levels reach zero, operators will probably begin to consider decommissioning.
> 
> The status of RFCs 3056 and 3068 should not be interpreted as a recommendation to remove 6-to-4 at any particular time.
> 
> 
>> -----Original Message-----
>> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
>> Sent: Monday, July 25, 2011 11:09 PM
>> To: Ronald Bonica
>> Cc: ietf@ietf.org
>> Subject: Re: draft-ietf-v6ops-6to4-to-historic (yet again)
>>
>> To be clear, I'd like to see exact proposed text before expressing
>> support for the proposal. The trick is to get 6to4 disabled by default
>> at the user end, without disabling it for users who are getting good
>> service from it.
>>
>> Regards
>>    Brian
>>
>> On 2011-07-26 09:49, Brian E Carpenter wrote:
>>>>  Likewise, operators will decide whether/when 6-to-4 relays will be
>> removed from their networks.
>>> This is, of course, an undeniable statement of fact (as it is for any
>> other feature
>>> of the Internet). However, it needs to be made clear that doing so
>> *prematurely*
>>> would penalise existing successful users of those relays, and
>> therefore it should
>>> only be done when there is no successful traffic through them. Which
>> is when any
>>> operator would remove them anyway.
>>>
>>> Therefore, I don't see much value in this statement, and possible
>> harm to users.
>>> The ways to avoid such harm as far as possible are already in the RFC
>> Editor
>>> queue.
>>>
>>> Regards
>>>    Brian Carpenter
>>>
>>> On 2011-07-26 02:30, Ronald Bonica wrote:
>>>> Folks,
>>>>
>>>> After some discussion, the IESG is attempting to determine whether
>> there is IETF consensus to do the following:
>>>> - add a new section to draft-ietf-v6ops-6to4-to-historic
>>>> - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL
>>>>
>>>> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068
>> and convert their status to HISTORIC. It will also contain a new
>> section describing what it means for RFCs 3056 and 3068 to be
>> classified as HISTORIC. The new section will say that:
>>>> - 6-to-4 should not be configured by default on any implementation
>> (hosts, cpe routers, other)
>>>> - vendors will decide whether/when 6-to-4 will be removed from
>> implementations. Likewise, operators will decide whether/when 6-to-4
>> relays will be removed from their networks. The status of RFCs 3056 and
>> 3068 should not be interpreted as a recommendation to remove 6-to-4 at
>> any particular time.
>>>>
>>>> draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While it
>> clarifies the meaning of "HISTORIC" in this particular case, it does
>> not set a precedent for any future case.
>>>> Please post your views on this course of action by August 8, 2011.
>>>>
>>>>
>>>>
>> Ron Bonica
>> <speaking as OPS Area AD>
>>>> _______________________________________________
>>>> Ietf mailing list
>>>> Ietf@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ietf
>>>>

From randy@psg.com  Tue Jul 26 16:54:56 2011
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A01211E80C0 for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 16:54:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.517
X-Spam-Level: 
X-Spam-Status: No, score=-2.517 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 D1nGI4XwK67A for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 16:54:55 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id BF01C11E809E for <ietf@ietf.org>; Tue, 26 Jul 2011 16:54:55 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76 (FreeBSD)) (envelope-from <randy@psg.com>) id 1QlrSf-000NvL-Kj; Tue, 26 Jul 2011 23:54:53 +0000
Date: Tue, 26 Jul 2011 19:54:53 -0400
Message-ID: <m2zkk0egxe.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ronald Bonica <rbonica@juniper.net>
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F431D13B@EMBX01-WF.jnpr.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D13B@EMBX01-WF.jnpr.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 23:54:56 -0000

i do not care what the draft is called.
i do not care whether it is info, experimental, or an IEN
i do care that is says 6to4 MUST be off by default

randy

From prvs=0189059d72=medel@globetel.com.ph  Tue Jul 26 17:43:40 2011
Return-Path: <prvs=0189059d72=medel@globetel.com.ph>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 110175E8018 for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 17:43:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.295
X-Spam-Level: 
X-Spam-Status: No, score=-1.295 tagged_above=-999 required=5 tests=[AWL=0.310,  BAYES_00=-2.599, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TtZLXqTMVKca for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 17:43:39 -0700 (PDT)
Received: from smtp01.globetel.com.ph (smtp01.globetel.com.ph [203.177.192.181]) by ietfa.amsl.com (Postfix) with ESMTP id 5BE385E8016 for <ietf@ietf.org>; Tue, 26 Jul 2011 17:43:39 -0700 (PDT)
Received: from exgtbh02.globetel.com ([10.225.208.154]) by smtp01.globetel.com.ph (8.14.4/8.14.4) with ESMTP id p6R0hHrF026517;  Wed, 27 Jul 2011 08:43:18 +0800
Received: from EXVSGT02.globetel.com ([10.225.208.145]) by exgtbh02.globetel.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 27 Jul 2011 08:43:36 +0800
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: draft-ietf-v6ops-6to4-to-historic  (yet again)
Date: Wed, 27 Jul 2011 08:43:35 +0800
Message-ID: <A5AD67DA1ACB9648831FD753485B2BFE11D55E7D@EXVSGT02.globetel.com>
In-Reply-To: <20110726201420.63A6118C0FA@mercury.lcs.mit.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-v6ops-6to4-to-historic  (yet again)
Thread-Index: AcxL0KkKZxEbxtogTNOLhXCjqwAZfwAJXmcQ
X-Priority: 1
Priority: Urgent
Importance: high
References: <20110726201420.63A6118C0FA@mercury.lcs.mit.edu>
From: "GT RAMIREZ, Medel G." <medel@globetel.com.ph>
To: <ietf@ietf.org>
X-OriginalArrivalTime: 27 Jul 2011 00:43:36.0962 (UTC) FILETIME=[388BB620:01CC4BF6]
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.4.6813, 1.0.211, 0.0.0000 definitions=2011-07-26_08:2011-07-27, 2011-07-26, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=12 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1012030000 definitions=main-1107260247
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 00:43:40 -0000

I say "Vow"...

Medel
+++++++++++++++++++++++++++++++++
-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Noel Chiappa
Sent: Wednesday, July 27, 2011 4:14 AM
To: ietf@ietf.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: draft-ietf-v6ops-6to4-to-historic (yet again)


    > From: "t.petch" <daedulus@btconnect.com>=20

    > I realise that ... you are seeking IETF consensus but what is that
    > if the WG is dead set against it?

If the entire WG is against it, that's enough people to (IMO) prevent
IETF
consensus -> no IETF rough consensus for this statement.

	Noel
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

This e-mail message (including attachments, if any) is intended for the use=
 of the individual or the entity to whom it is addressed and may contain in=
formation that is privileged, proprietary, confidential and exempt from dis=
closure. If you are not the intended recipient, you are notified that any d=
issemination, distribution or copying of this communication is strictly pro=
hibited. If you have received this communication in error, please notify th=
e sender and delete this E-mail message immediately.

From mail@sabahattin-gucukoglu.com  Tue Jul 26 18:23:56 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 ACD6A21F8A64 for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 18:23:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.19
X-Spam-Level: 
X-Spam-Status: No, score=0.19 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_EQ_IP_ADDR=1.119, RCVD_IN_PBL=0.905]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VFZkltkEpaWu for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 18:23:56 -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 D8F0521F8A62 for <ietf@ietf.org>; Tue, 26 Jul 2011 18:23:55 -0700 (PDT)
Received: from Mintaka.sabahattin-gucukoglu.com ([::ffff:127.0.0.1]:50613) by Mintaka.sabahattin-gucukoglu.com with [XMail 1.27 ESMTP Server] id <S38CD2> for <ietf@ietf.org> from <mail@sabahattin-gucukoglu.com>; Wed, 27 Jul 2011 02:23:54 +0100
Received: from [172.20.10.2] (178.242.87.113) (using SMTP over TLS) by Mintaka.sabahattin-gucukoglu.com (tmda-ofmipd) with ESMTP; Wed, 27 Jul 2011 02:23:52 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
Date: Wed, 27 Jul 2011 04:23:49 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5AEF088-1DAA-4FC9-967D-3F0C6A799F03@sabahattin-gucukoglu.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
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-1314321834.053927@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: Wed, 27 Jul 2011 01:23:56 -0000

On 25 Jul 2011, at 17:30, Ronald Bonica wrote:
> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 and =
convert their status to HISTORIC. It will also contain a new section =
describing what it means for RFCs 3056 and 3068 to be classified as =
HISTORIC. The new section will say that:
>=20
> - 6-to-4 should not be configured by default on any implementation =
(hosts, cpe routers, other)
> - vendors will decide whether/when 6-to-4 will be removed from =
implementations. Likewise, operators will decide whether/when 6-to-4 =
relays will be removed from their networks. The status of RFCs 3056 and =
3068 should not be interpreted as a recommendation to remove 6-to-4 at =
any particular time.
>=20
>=20
> draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While it =
clarifies the meaning of "HISTORIC" in this particular case, it does not =
set a precedent for any future case.

This scares me.  I was on the point of saying, "But none of that stuff =
makes it historic!" but you then change what "Historic" means, so that I =
can no longer be certain ...

I'd like to see the text, but my feeling is that, no, I will not =
approve.  That document is too loaded with dubious claims and 6to4 hate =
for my liking.  And the advisory document is already perfect for =
expressing the _real_ problems, that really _do_ exist, for (current) =
6to4 deployment.  Once again, "Historic" (in whatever sense meant) is =
just too strong an applied label to something which _can_ be used.  I =
have a very hard time seeing the sense in this document.

But let's see the text.  Perhaps you can redefine the word "Historic" in =
a new and interesting way.

Cheers,
Sabahattin

From marka@isc.org  Tue Jul 26 18:29:03 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 5B47C5E800D; Tue, 26 Jul 2011 18:29:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.454
X-Spam-Level: 
X-Spam-Status: No, score=-2.454 tagged_above=-999 required=5 tests=[AWL=-0.155, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id StHUf5z7cwlb; Tue, 26 Jul 2011 18:29:02 -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 1AD595E8003; Tue, 26 Jul 2011 18:29:02 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 8E3C25F9911; Wed, 27 Jul 2011 01:28:41 +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 30050216C88; Wed, 27 Jul 2011 01:28:09 +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 EBB811231907; Wed, 27 Jul 2011 11:28:06 +1000 (EST)
To: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
From: Mark Andrews <marka@isc.org>
References: <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <CALiegf=4K2oWfmZjGMD7J_jyaDtS3i+Mu7R0Wh75Rr+MrQCjtw@mail.gmail.com> <20110722054345.GE18126@1wt.eu> <CALiegfnYm6g63JDHLiSH__r-or3kzK0XCVa3cC7RMP14KWBOSg@mail.gmail.com> <20110724120751.GQ22405@1wt.eu> <CALiegfncavmoMp4YDCeeJ3rsOfHAYQ99itKX2Q2eHB351T3X5A@mail.gmail.com> <20110724184537.GZ22405@1wt.eu> <CALiegfne620wuDMAp235n3mVcXTAnbhhNm8vpiNCy5F7+VD92A@mail.gmail.com> <20110724192948.GD22405@1wt.eu> <CALiegf=e48kkF+Gky1mY7LippUB-0kZDgSGZrJxk1aZupAGkYw@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
In-reply-to: Your message of "Tue, 26 Jul 2011 11:47:48 +0200." <CALiegf=e48kkF+Gky1mY7LippUB-0kZDgSGZrJxk1aZupAGkYw@mail.gmail.com>
Date: Wed, 27 Jul 2011 11:28:06 +1000
Message-Id: <20110727012806.EBB811231907@drugs.dv.isc.org>
Cc: Server-Initiated HTTP <hybi@ietf.org>, Willy Tarreau <w@1wt.eu>, 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, 27 Jul 2011 01:29:03 -0000

In message <CALiegf=e48kkF+Gky1mY7LippUB-0kZDgSGZrJxk1aZupAGkYw@mail.gmail.com>
, =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= writes:
> 2011/7/24 Willy Tarreau <w@1wt.eu>:
> >> Ok, but what would be the failover solution then? any failover
> >> solution can take some time until redirects the client's request to a
> >> working server, it's not just a client problem.
> >
> > This is already addressed by existing web architectures. DNS provides
> > geolocation and proposes you the closest working datacenter. BGP ensures
> > that this datacenter is always reachable via multiple links and multiple
> > providers. Load balancers on the site ensure that only valid servers are
> > used. I know some people who configure their load balancers so that a
> > server is removed from the pool less than 50ms after a failure or 
> slowdown
> > has been noticed. You will never be able to offer that quality of 
> service
> > using DNS only, because those 50ms are less than the time it takes for
> > most visitors to ping the site.
> 
> Yes, but those are expensive server side solutions. I wouldn't like
> that a scalable architecture requires so complex solutions (which are
> not very suitable in case of usual web hostings). DNS SRV provides a
> cheaper way of doing something similar (both ways can live together
> thought).
> 
> 
> 
> >> Anyhow, don't forget that SRV is not just for failover, but also for
> >> load-balancing (you can state that a more powerful server-01 receives
> >> 80% of the traffic and server-02 the remaining 20%).
> >
> > This is already addressed by DNS round robin and used by a lot of sites.
> 
> I consider that a hack.
> 
> 
> > But keep in mind that DNS is used between *sites* and not *servers*. If
> > you use it for servers, you'll fail because you won't be able to 
> silently
> > put them in maintenance without disturbing visitors.
> 
> SRV provides load-balancing and failover. I never said that SRV is a
> solution for temporaly put in maintenance a server.

Happy eyeballs however does allow you to take a server out of production
and not really notice it.  Note webbrowsers have had the ability to do
this for as long as webbrowsers have existed.

Billions of dollars have been wasted globally for the sake of a few hours
work by webbrowser vendors.
 
> > Load balancers are
> > used for servers. And between sites, people are not seeking imbalanced
> > distribution. If they really do, then it's easy using multiple 
> addresses.
> >
> > Don't take this as an attack (it is not), but you accused Roy of not
> > knowing SRV, but I think that you're not much experienced with web
> > infrastructures and that may be why you think that SRV is the *only*
> > solution to many problems that have been dealt with for ages.
> 
> Right, but I'm used to scalable and big SIP infrastructures and DNS
> SRV is used for that (along with server side solutions as SIP load
> balancers). What I say is that web infraestructures cannot use SRV
> mechanism so it's not valid for me that just current HTTP solutions
> are valid for any other new protocol.
> 
> In contrast it seems that for many people the hacks existing in HTTP
> world (www.facebook.com resolves to a single IP) is the only way to go
> for a scalable infraestructure "so DNS SRV is not needed". Why so many
> efforts in disallowing an *optional* mechanism like SRV? If somebody
> does not like it, just don't use it.
> 
> 
> Regards.
> 
> 
> -- 
> IÃ±aki Baz Castillo
> <ibc@aliax.net>
> _______________________________________________
> 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  Tue Jul 26 18:44:38 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 358D711E8086 for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 18:44:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.076
X-Spam-Level: 
X-Spam-Status: No, score=-0.076 tagged_above=-999 required=5 tests=[AWL=0.014,  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 RCUt9o5tqiRL for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 18:44:37 -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 5133121F86BE for <ietf@ietf.org>; Tue, 26 Jul 2011 18:44:37 -0700 (PDT)
Received: (qmail 18678 invoked from network); 27 Jul 2011 02:04:28 -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; 27 Jul 2011 02:04:28 -0000
Message-ID: <4E2F6D24.9090102@necom830.hpcl.titech.ac.jp>
Date: Wed, 27 Jul 2011 10:43:00 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: 6to4v2 (as in ripv2)?
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com>	<4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com>
In-Reply-To: <4E2F4491.30102@gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 01:44:38 -0000

Brian E Carpenter wrote:

> Since 6to4 is a transition mechanism it has no long term future
> *by definition*.

By observation, the transition is continuing for these 16 years
since RFC1883.

						Masataka Ohta

From marka@isc.org  Tue Jul 26 19:39:21 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 BB56D11E80BE; Tue, 26 Jul 2011 19:39:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=-0.001,  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 GDtoA7PccFX9; Tue, 26 Jul 2011 19:39: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 2A99411E80A5; Tue, 26 Jul 2011 19:39: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 BE1265F99DB; Wed, 27 Jul 2011 02:39:08 +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 069F1216C81; Wed, 27 Jul 2011 02:38:37 +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 5C72D1232958; Wed, 27 Jul 2011 12:38:33 +1000 (EST)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com>
Subject: Re: 6to4v2 (as in ripv2)? 
In-reply-to: Your message of "Wed, 27 Jul 2011 10:49:53 +1200." <4E2F4491.30102@gmail.com>
Date: Wed, 27 Jul 2011 12:38:33 +1000
Message-Id: <20110727023833.5C72D1232958@drugs.dv.isc.org>
Cc: IPv6 Operations <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, 27 Jul 2011 02:39:21 -0000

In message <4E2F4491.30102@gmail.com>, Brian E Carpenter writes:
> Alex,
> 
> Since 6to4 is a transition mechanism it has no long term future
> *by definition*. Even if someone chooses to design a v2, who is going to
> implement it?
> 
> If you have a reason to install and enable 6to4, why would the nominal
> status of a couple of RFCs make you do anything different?
> 
> Of course, if implementors choose to drop the code you might not be
> able to upgrade software versions - but hopefully by that time you
> will have native IPv6 service anyway.

Which is exactly why HISTORIC is NOT appropriate. 
 
> Regards
>    Brian Carpenter
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From samirs.lists@gmail.com  Tue Jul 26 23:07:34 2011
Return-Path: <samirs.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 F090C21F8AD3 for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 23:07:34 -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 C4CHqfc863C6 for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 23:07:34 -0700 (PDT)
Received: from mail-pz0-f53.google.com (mail-pz0-f53.google.com [209.85.210.53]) by ietfa.amsl.com (Postfix) with ESMTP id 5790521F8A1A for <ietf@ietf.org>; Tue, 26 Jul 2011 23:07:34 -0700 (PDT)
Received: by pzk6 with SMTP id 6so2006718pzk.26 for <ietf@ietf.org>; Tue, 26 Jul 2011 23:07:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=XLbjXyq6ByDtTEaVeJaqG2EVdhpdZ+Zy0M9X92f9UKs=; b=wq2NV0gzgSt12Ybd3DwMJt13xN31gL34hX3KlRGqev+HxCcJy/sK1ggLGVSg0MjAbn JKA9hbkvUdK+J+esMUaS2eFAnrHz9gWAkvxe3qeQ8Zn/+rRrCmo5C7GuaAw8/xy91XSR GVKxwt78tLilBXFYCL1CyjolPryP0qUNOum6c=
MIME-Version: 1.0
Received: by 10.68.11.232 with SMTP id t8mr7875685pbb.234.1311746853768; Tue, 26 Jul 2011 23:07:33 -0700 (PDT)
Received: by 10.68.43.7 with HTTP; Tue, 26 Jul 2011 23:07:33 -0700 (PDT)
Date: Tue, 26 Jul 2011 23:07:33 -0700
Message-ID: <CAK+SpiyJYKKuWo5bzn_a9+KwW_SFhFXKT34_VTW3b3LKgxa_ag@mail.gmail.com>
Subject: Standards and patents
From: Samir Srivastava <samirs.lists@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, 27 Jul 2011 06:07:35 -0000

Hi, Refer http://samirsrivastava.typepad.com for posting on Standards
And Patents. Copyright of posting on Standards And Patents is free for
personal usage. Arguments were presented in favour of that standards
and their usage should be free from patents. If standards are
patentable then mathematical / scientific theories ( innovation of the
perfection level) should be patentable also. IMHO after the
development of the baseline specifications we lack freedom to
standardize best. Standards are developed by community & for
community. There is no role of patent hunters in that. Comments /
flames on the blog or here are welcome. Regards Samir

From dave@cridland.net  Wed Jul 27 00:38: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 92CC421F8AD1; Wed, 27 Jul 2011 00:38:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.385
X-Spam-Level: 
X-Spam-Status: No, score=-2.385 tagged_above=-999 required=5 tests=[AWL=-0.086, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PujJvoCqUUz7; Wed, 27 Jul 2011 00:38: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 CE7AF21F86A1; Wed, 27 Jul 2011 00:38:02 -0700 (PDT)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id BA9E01168087; Wed, 27 Jul 2011 08:37:57 +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 vGJXQvdsteqp; Wed, 27 Jul 2011 08:37:55 +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 E25D71168067; Wed, 27 Jul 2011 08:37:54 +0100 (BST)
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <CALiegf=4K2oWfmZjGMD7J_jyaDtS3i+Mu7R0Wh75Rr+MrQCjtw@mail.gmail.com> <20110722054345.GE18126@1wt.eu> <CALiegfnYm6g63JDHLiSH__r-or3kzK0XCVa3cC7RMP14KWBOSg@mail.gmail.com> <20110724120751.GQ22405@1wt.eu> <CALiegfncavmoMp4YDCeeJ3rsOfHAYQ99itKX2Q2eHB351T3X5A@mail.gmail.com> <20110724184537.GZ22405@1wt.eu> <CALiegfne620wuDMAp235n3mVcXTAnbhhNm8vpiNCy5F7+VD92A@mail.gmail.com> <20110724192948.GD22405@1wt.eu> <CALiegf=e48kkF+Gky1mY7LippUB-0kZDgSGZrJxk1aZupAGkYw@mail.gmail.com> <20110727012806.EBB811231907@drugs.dv.isc.org>
In-Reply-To: <20110727012806.EBB811231907@drugs.dv.isc.org>
MIME-Version: 1.0
Message-Id: <9031.1311752274.907487@puncture>
Date: Wed, 27 Jul 2011 08:37:54 +0100
From: Dave Cridland <dave@cridland.net>
To: Mark Andrews <marka@isc.org>, Server-Initiated HTTP <hybi@ietf.org>, Willy Tarreau <w@1wt.eu>, IETF-Discussion <ietf@ietf.org>, =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
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, 27 Jul 2011 07:38:03 -0000

On Wed Jul 27 02:28:06 2011, Mark Andrews wrote:
> Billions of dollars have been wasted globally for the sake of a few  
> hours
> work by webbrowser vendors.

Seems to be a recurring theme - browsers could have easily performed  
probe tests to check for vulnerable proxies and disabled WebSockets  
(or negotiated masking), but that was ruled out long ago.

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 despres.remi@laposte.net  Wed Jul 27 00:46:56 2011
Return-Path: <despres.remi@laposte.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20EC521F86E0 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 00:46:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level: 
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[AWL=0.015,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HUx-OQBvKiSK for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 00:46:55 -0700 (PDT)
Received: from smtp22.services.sfr.fr (smtp22.services.sfr.fr [93.17.128.12]) by ietfa.amsl.com (Postfix) with ESMTP id 47DB321F86DD for <ietf@ietf.org>; Wed, 27 Jul 2011 00:46:55 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2213.sfr.fr (SMTP Server) with ESMTP id 70426700008C; Wed, 27 Jul 2011 09:46:54 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2213.sfr.fr (SMTP Server) with ESMTP id 16C387000088; Wed, 27 Jul 2011 09:46:54 +0200 (CEST)
X-SFR-UUID: 20110727074654933.16C387000088@msfrf2213.sfr.fr
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <46B9B2CA-3A7A-40F4-9164-5608C48DCF18@apple.com>
Date: Wed, 27 Jul 2011 09:46:53 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FC48CFAA-4060-4462-827F-CD80C26334C2@laposte.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <46B9B2CA-3A7A-40F4-9164-5608C48DCF18@apple.com>
To: james woodyatt <jhw@apple.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: Wed, 27 Jul 2011 07:46:56 -0000

Le 27 juil. 2011 =E0 00:11, james woodyatt a =E9crit :

> On Jul 25, 2011, at 10:30 AM, Ronald Bonica wrote:
>>=20
>> Please post your views on this course of action by August 8, 2011.
>=20
> I remain convinced that this document is unnecessary and publishing it =
would be silly, at best, and at worst, the simultaneous publication of =
6to4-to-historic alongside 6to4-advisory, which implicitly contradict =
one another-- the latter says that 6to4 has an indefinite future and =
here's how to keep everything operational in its presence on the =
Internet; the former says 6to4 has no future, and it should not be used =
by anyone for any purpose-- may turn out to be an embarrassment for =
IETF.

>  IESG should feel very nervous about claiming there is consensus to =
publish this draft.  It does not appear to me like there is a rough =
consensus for it.

+1


>=20
> That said, I won't complain too loudly if this draft is published.  It =
would give me cover to ask my employers for 6to4 capability to be =
removed from forthcoming products that I mainly work to support.  I =
don't like taking features away from users when there isn't a suitable =
upgrade path for them, but the truth is that fielding problems from the =
field resulting from 6to4 failure can be pretty tiresome, and I would =
welcome the cover from IETF to be able to say, "Oh, you're still using =
6to4?  You should turn that off.  It's deprecated by IETF now, and =
accordingly, we no longer support it.  Get native IPv6 service."
>=20
> In other words, whether IESG means to convey this message or not, =
publishing 6to4-to-historic alongside the existing 6to4-advisory-- =
without any clear phase-out plan-- will pretty clearly imply to people =
like me that the official phase-out plan is to remove 6to4 from the =
Internet, starting as soon as vendors and operators are independently =
able to do so.  "Start the engines of destruction."
>=20
>=20
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, core os networking
>=20
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf



From daedulus@btconnect.com  Wed Jul 27 01:35:36 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 53F6421F8584 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 01:35:36 -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]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jU-sQhkEoNn5 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 01:35:35 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr09.btconnect.com [213.123.26.187]) by ietfa.amsl.com (Postfix) with ESMTP id 5FDBE21F8581 for <ietf@ietf.org>; Wed, 27 Jul 2011 01:35:34 -0700 (PDT)
Received: from host109-153-78-164.range109-153.btcentralplus.com (HELO pc6) ([109.153.78.164]) by c2beaomr09.btconnect.com with SMTP id DUO72267; Wed, 27 Jul 2011 09:35:29 +0100 (BST)
Message-ID: <006d01cc4c2f$55e8dd40$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Ronald Bonica" <rbonica@juniper.net>, <ietf@ietf.org>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
Date: Wed, 27 Jul 2011 09:32:23 +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.4E2FCDD1.0093, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.7.27.73314:17:7.586, ip=109.153.78.164, 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, 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=c2beaomr09.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0201.4E2FCDD2.00A6,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: Wed, 27 Jul 2011 08:35:36 -0000

I oppose this action.

I see clear evidence that 6to4 is damaging the Internet and although there are
those who can use it without causing damage, I believe that the principle is
'First, do no harm'
so the IETF has a responsibility to discourage its use.  For me, classifying it
as 'Historic' is the best way of doing this but I see that there are those dead
set against it.

Redefining 'Historic', as proposed here, can only confuse given the previous and
successful widespread use of this technical term.

Several have suggested that an alternative would be to recast this I-D as an
Applicability Statement and, while I would not see this as good as 'Historic',
since I think that  it carries less weight, I would still see that as strong
enough to get across the message - '6to4 damages the Internet - don't do it'
leaving those who know better to know better.

Tom Petch

----- Original Message -----
From: "Ronald Bonica" <rbonica@juniper.net>
To: <ietf@ietf.org>
Sent: Monday, July 25, 2011 4:30 PM
Subject: draft-ietf-v6ops-6to4-to-historic (yet again)


> Folks,
>
> After some discussion, the IESG is attempting to determine whether there is
IETF consensus to do the following:
>
> - add a new section to draft-ietf-v6ops-6to4-to-historic
> - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL
>
> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 and convert
their status to HISTORIC. It will also contain a new section describing what it
means for RFCs 3056 and 3068 to be classified as HISTORIC. The new section will
say that:
>
> - 6-to-4 should not be configured by default on any implementation (hosts, cpe
routers, other)
> - vendors will decide whether/when 6-to-4 will be removed from
implementations. Likewise, operators will decide whether/when 6-to-4 relays will
be removed from their networks. The status of RFCs 3056 and 3068 should not be
interpreted as a recommendation to remove 6-to-4 at any particular time.
>
>
> draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While it clarifies
the meaning of "HISTORIC" in this particular case, it does not set a precedent
for any future case.
>
> Please post your views on this course of action by August 8, 2011.
>
>
>                                                                    Ron Bonica
>                                                                    <speaking
as OPS Area AD>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From bortzmeyer@nic.fr  Wed Jul 27 01:46:08 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 421D221F8B0B for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 01:46:08 -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 EevfUj23YTfS for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 01:46:07 -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 9387C21F8B09 for <ietf@ietf.org>; Wed, 27 Jul 2011 01:46:07 -0700 (PDT)
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id 3BCA21C0371; Wed, 27 Jul 2011 10:46:06 +0200 (CEST)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx2.nic.fr (Postfix) with ESMTP id 36D4F1C035E; Wed, 27 Jul 2011 10:46:06 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.6.69]) by relay1.nic.fr (Postfix) with ESMTP id 299D7568129; Wed, 27 Jul 2011 10:46:06 +0200 (CEST)
Date: Wed, 27 Jul 2011 10:46:06 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Glen <glen@amsl.com>
Subject: Re: DKIM Signatures now being applied to IETF Email
Message-ID: <20110727084606.GA16280@nic.fr>
References: <20110725171748.GA13506@amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110725171748.GA13506@amsl.com>
X-Operating-System: Debian GNU/Linux 6.0.2
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: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 08:46:08 -0000

On Mon, Jul 25, 2011 at 10:17:48AM -0700,
 Glen <glen@amsl.com> wrote 
 a message of 23 lines which said:

> I am very pleased to report that the IETF is now applying DKIM signatures
> to all outgoing list email from mailman.

What about a RFC 5617 published signing practice?


From despres.remi@laposte.net  Wed Jul 27 02:05:37 2011
Return-Path: <despres.remi@laposte.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4930121F884F for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 02:05:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[AWL=0.014,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fRlaW54NbAVn for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 02:05:36 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.22]) by ietfa.amsl.com (Postfix) with ESMTP id C1BB521F8844 for <ietf@ietf.org>; Wed, 27 Jul 2011 02:05:36 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2314.sfr.fr (SMTP Server) with ESMTP id 229F97000095; Wed, 27 Jul 2011 11:05:36 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2314.sfr.fr (SMTP Server) with ESMTP id A4DE17000094; Wed, 27 Jul 2011 11:05:35 +0200 (CEST)
X-SFR-UUID: 20110727090535675.A4DE17000094@msfrf2314.sfr.fr
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <m2zkk0egxe.wl%randy@psg.com>
Date: Wed, 27 Jul 2011 11:05:35 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D56AC163-F4DF-484F-A249-F15966DFF2BC@laposte.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D13B@EMBX01-WF.jnpr.net> <m2zkk0egxe.wl%randy@psg.com>
To: IETF Discussion <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: Wed, 27 Jul 2011 09:05:37 -0000

Le 27 juil. 2011 =E0 01:54, Randy Bush a =E9crit :

> i do not care what the draft is called.
> i do not care whether it is info, experimental, or an IEN


> i do care that is says 6to4 MUST be off by default

+1
This is really what IETF has to say.

Everything else should better be limited to explanations.

RD

>=20
> randy
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf



From fred@cisco.com  Wed Jul 27 04:10:26 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 6E46921F8548; Wed, 27 Jul 2011 04:10:26 -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 AnhJ1MC4Bq1T; Wed, 27 Jul 2011 04:10:25 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id B6E7521F854C; Wed, 27 Jul 2011 04:10:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=304; q=dns/txt; s=iport; t=1311765025; x=1312974625; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=1hin4uOQkS5g+jSDNnAebBaB/3C6zDOjcxMIYRhoq7E=; b=bpTs4M1fD7dKBfE7do6X9B2GF6H0lU3r3y5Mhjuz7gUdRnJ33KxlWkWf ykQcEQe9iI9ewz2OcAZoTP0EwOdjBtjQsNZnL0jlLY+YNPQRWDaLTAgFi e1kZHW5uHGOwIyr5w5tlk7XgrvEZwYG6Zmly0PSwj08wLfeZSTP96W5rh Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EADzxL06rRDoI/2dsb2JhbAA1AQEBAQIBFAErRQUMDFIUUQc+pxp3iHyieJ5mhWFfBJJ1hQeLdw
X-IronPort-AV: E=Sophos;i="4.67,276,1309737600";  d="scan'208";a="6905634"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by rcdn-iport-4.cisco.com with ESMTP; 27 Jul 2011 11:09:49 +0000
Received: from dhcp-4466.meeting.ietf.org (sjc-vpn6-314.cisco.com [10.21.121.58]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p6RB8MU5020644; Wed, 27 Jul 2011 11:09:47 GMT
Received: from [127.0.0.1] by dhcp-4466.meeting.ietf.org (PGP Universal service); Wed, 27 Jul 2011 07:09:48 -0400
X-PGP-Universal: processed; by dhcp-4466.meeting.ietf.org on Wed, 27 Jul 2011 07:09:48 -0400
Subject: Re: 6to4v2 (as in ripv2)? 
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4E2F4491.30102@gmail.com>
Date: Wed, 27 Jul 2011 07:09:47 -0400
Message-Id: <72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com>	<4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <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, 27 Jul 2011 11:10:26 -0000

On Jul 26, 2011, at 6:49 PM, Brian E Carpenter wrote:

> Since 6to4 is a transition mechanism it has no long term future *by =
definition*. Even if someone chooses to design a v2, who is going to =
implement it?

Actually, I think one could argue pretty effectively that 6rd is =
6to4-bis.=20=

From vesely@tana.it  Wed Jul 27 04:18:41 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 CB60321F8BA1 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 04:18:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.804
X-Spam-Level: 
X-Spam-Status: No, score=-4.804 tagged_above=-999 required=5 tests=[AWL=-0.085, 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 uvLpS3Iar6WR for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 04:18:41 -0700 (PDT)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 0F1E921F8B34 for <ietf@ietf.org>; Wed, 27 Jul 2011 04:18:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1311765519; bh=vpIUzVReZwcDEIVnDt0lUtNU7trM2sBo+/CfLglTPM4=; l=417; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=Rn354/N9rrNll6Zy8AVVPCFQhSxb+U0ssjxkVHMfJyqJb8BZavS9BoR0Ut2CHw9KP XB+zc3RnHDLZrxcjuUbSg1mewQoD/fK8C6SL8xOWEoWuP6j2PzQJJCpn76CglXY/S0 iqGxmBE0HwMSVKpIX+Ue0aP/tAeAN1HOrabO91Uc=
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, 27 Jul 2011 13:18:39 +0200 id 00000000005DC039.000000004E2FF40F.00000301
Message-ID: <4E2FF40F.1050301@tana.it>
Date: Wed, 27 Jul 2011 13:18:39 +0200
From: Alessandro Vesely <vesely@tana.it>
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: ietf@ietf.org
Subject: Re: Standards and patents
References: <CAK+SpiyJYKKuWo5bzn_a9+KwW_SFhFXKT34_VTW3b3LKgxa_ag@mail.gmail.com>
In-Reply-To: <CAK+SpiyJYKKuWo5bzn_a9+KwW_SFhFXKT34_VTW3b3LKgxa_ag@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 11:18:41 -0000

On 27/Jul/11 08:07, Samir Srivastava wrote:
> Standards are developed by community & for community. There is no
> role of patent hunters in that.

I agree, with the exception of "defensive" patents, some of which are
announced with very elegant disclosures.  Let's draw a veil over
incomprehensible and confused disclosures, for now.  For the rest,
what is the purpose of standardizing a private walled garden?



From vesely@tana.it  Wed Jul 27 05:02:45 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 F3D6D21F8A71 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 05:02:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.901
X-Spam-Level: 
X-Spam-Status: No, score=-3.901 tagged_above=-999 required=5 tests=[AWL=-0.982, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, J_CHICKENPOX_34=0.6, J_CHICKENPOX_44=0.6, J_CHICKENPOX_63=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 K-nyYvaqYvBU for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 05:02:44 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 0FC4821F8A70 for <ietf@ietf.org>; Wed, 27 Jul 2011 05:02:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1311768162; bh=2K9gipjgqP9KoN90JsR2HwpL9diPMYBVW8WGDTV/0E8=; l=1349; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=hGi8cF2aBcczGg/tILPZS/OlHfilThXGLvnIuIVRtElxamAW5HZ+T+I0wTrUrFwR4 /5+UxS2O5DiL3ETNbbL2rqdHyJ2RSvJPSca55czaWyMnSDfGHbOOC7m4I7r0VvhfOk uUkHzIR1GEeMpctbVNDJ3cVw1B78fLd35f6C6zWs=
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, 27 Jul 2011 14:02:42 +0200 id 00000000005DC033.000000004E2FFE62.00000DD7
Message-ID: <4E2FFE62.5040006@tana.it>
Date: Wed, 27 Jul 2011 14:02:42 +0200
From: Alessandro Vesely <vesely@tana.it>
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: ietf@ietf.org
Subject: Re: DKIM Signatures now being applied to IETF Email
References: <20110725171748.GA13506@amsl.com> <4E2E3D93.6040902@isdg.net> <4E2E405C.9040507@isdg.net>
In-Reply-To: <4E2E405C.9040507@isdg.net>
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, 27 Jul 2011 12:02:45 -0000

On 26/Jul/11 06:19, Hector Santos wrote:
> But the original destroyed signature from the author is not stripped.

Nor verified, apparently.

> Authentication-Results: dkim.winserver.com;
>  dkim=pass header.d=ietf.org header.s=ietf1 header.i=ietf.org;
>  adsp=fail policy=all author.d=isdg.net asl.d=ietf.org (unauthorized signer);
>  dkim=fail (DKIM_SIGNATURE_BAD) header.d=isdg.net header.s=tms1 header.i=isdg.net;
>  adsp=pass policy=all author.d=isdg.net signer.d=isdg.net (originating signer);

My verifier is somewhat more concise than yours.  For your message it
just reports

Authentication-Results: wmail.tana.it;
  spf=pass smtp.mailfrom=ietf.org;
  dkim=pass header.i=@ietf.org;
  dkim-adsp=fail header.from=hsantos@isdg.net

> It would be nice for the list server to remove original signatures the
> list will destroy in its resigning process.

That implies checking which signatures actually got destroyed.  Was
the author signature destroyed, on this message?  Possibly not, as on
my previous message I got

Authentication-Results: wmail.tana.it;
  spf=pass smtp.mailfrom=ietf.org;
  dkim=pass header.i=@tana.it

(The IETF's signature would probably have passed too, but since the
author signature was good, this concise verifier didn't bother to
report on any other one --a little bit too much concise, perhaps.)

From turners@ieca.com  Wed Jul 27 05:09:09 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 4071921F8B8D for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 05:09:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.89
X-Spam-Level: 
X-Spam-Status: No, score=-100.89 tagged_above=-999 required=5 tests=[AWL=-0.892, BAYES_50=0.001, 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 zazEcrA14P38 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 05:09:08 -0700 (PDT)
Received: from nm19.bullet.mail.sp2.yahoo.com (nm19.bullet.mail.sp2.yahoo.com [98.139.91.89]) by ietfa.amsl.com (Postfix) with SMTP id 3A8F721F8B3C for <ietf@ietf.org>; Wed, 27 Jul 2011 05:09:05 -0700 (PDT)
Received: from [98.139.91.64] by nm19.bullet.mail.sp2.yahoo.com with NNFMP; 27 Jul 2011 12:09:05 -0000
Received: from [98.139.91.13] by tm4.bullet.mail.sp2.yahoo.com with NNFMP; 27 Jul 2011 12:09:05 -0000
Received: from [127.0.0.1] by omp1013.mail.sp2.yahoo.com with NNFMP; 27 Jul 2011 12:09:05 -0000
X-Yahoo-Newman-Id: 156671.37079.bm@omp1013.mail.sp2.yahoo.com
Received: (qmail 9283 invoked from network); 27 Jul 2011 12:09:05 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1311768545; bh=IyXuAJpIY/ZWpnbrXGADwzbxwef2GUeC6/W5SOucCwg=; h=X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=udcOzBu44vH0cXi67IkzjMemGEhMTz0T/ptQJ50i8k3FjlIVOTOoYNDHv+aERZbEE2faMwmgbAsvQu7WiOyH6go7blRLFdNJM3iMTSmV+5lxLVbr94kSv7NpVii4yaF39qyyi3PsK9/hkLl3Uxcr3qwS90T47KpVbWNRY1ZgnO0=
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: _.u5FMwVM1la_k5I._b_PrtCOmsoqgRw5YCGLtPvAssQcdT 7Rjfh_39NYQiEvHWI81Ni4j.AyAmLirGOSebtD2uD3zft.0xQLjhgXCCkwtF IAyhRXmFVAUp7XZ16.2fhXVpteHNSJIjJjWOZ.wOdQKIYbal_cpSEGa2NlfU .Gj7C_3OQJCqjZ58M2FTfk_Ksw_hL1b1gFsdRFwIXBR.2rNt9AMa7o8Nj1r0 _SaHCHSnMQVu3un8gdkaewtq1SjUuVUn9B_3Dqsif9gOhF4dwZyEBQ2Mz1Ia AyZq2OFTa69ygSjoUqLErzEQANAj.doIUlAuELXGsoH7z1y1dBvH9yKBkQOv iZwmdut_MKt1.8lfG7MysM6z7MjieDqOJMCTJ1m1KwAw-
X-Yahoo-SMTP: ZrP3VLSswBDL75pF8ymZHDSu9B.vcMfDPgLJ
Received: from dhcp-40b3.meeting.ietf.org (turners@130.129.64.179 with plain) by smtp114.biz.mail.sp1.yahoo.com with SMTP; 27 Jul 2011 05:09:04 -0700 PDT
Message-ID: <4E2FFFDF.2080601@ieca.com>
Date: Wed, 27 Jul 2011 08:09:03 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DKIM Signatures now being applied to IETF Email
References: <20110725171748.GA13506@amsl.com> <4E2DAF60.8030307@dcrocker.net>
In-Reply-To: <4E2DAF60.8030307@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 12:09:09 -0000

On 7/25/11 2:01 PM, Dave CROCKER wrote:
>
>
> On 7/25/2011 1:17 PM, Glen wrote:
>> I am very pleased to report that the IETF is now applying DKIM signatures
>> to all outgoing list email from mailman.
>
>
> I'll be presumptuous and speak on behalf of the DKIM operations
> community, rather than just myself:
>
> Cool! Thanks.

+1 to that!

Personally, I like it when we eat our own dog food ;)

spt

From moore@network-heretics.com  Wed Jul 27 05:15:35 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 4482821F84FC; Wed, 27 Jul 2011 05:15:35 -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 HzM7Hb9gPlkB; Wed, 27 Jul 2011 05:15:34 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 9F47121F84FB; Wed, 27 Jul 2011 05:15:34 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id D880D20F47; Wed, 27 Jul 2011 08:15:33 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 27 Jul 2011 08:15:33 -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=cSBNGM13VFnp8lqVB1hXedmpbjw=; b=Lt 2JvXEJ49RKmJCg/Bz6l4QZR0rUTSMu5EM++nFzOcPBn7WPy+Jx9ig52Qg6tU4pEN 9bXvXrMivZlgsvU+dtAMN1NDrKn+TGOUIUVoJTpBbavOf0nLLFfK3ygYoweVrSAn CcdnkkulHHc9QITvlLHr5M3TdE1EE9f8Kec6xBx0g=
X-Sasl-enc: l/0kR7TzKstpxO2P2tBGQ9c1SOPMRqhYSbHINIEv8yZO 1311768933
Received: from [192.168.210.100] (modemcable114.145-70-69.static.videotron.ca [69.70.145.114]) by mail.messagingengine.com (Postfix) with ESMTPSA id 57C5D455412; Wed, 27 Jul 2011 08:15:33 -0400 (EDT)
Subject: Re: 6to4v2 (as in ripv2)? 
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: <72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com>
Date: Wed, 27 Jul 2011 08:15:32 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5A600744-8605-46D3-82B2-C3C30E30E4AC@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com>	<4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com>
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.1084)
Cc: IPv6 Operations <v6ops@ietf.org>, ietf@ietf.org, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 12:15:35 -0000

On Jul 27, 2011, at 7:09 AM, Fred Baker wrote:

>=20
> On Jul 26, 2011, at 6:49 PM, Brian E Carpenter wrote:
>=20
>> Since 6to4 is a transition mechanism it has no long term future *by =
definition*. Even if someone chooses to design a v2, who is going to =
implement it?
>=20
> Actually, I think one could argue pretty effectively that 6rd is =
6to4-bis.

only if you're confused about the use cases for each.

Keith


From johnl@iecc.com  Wed Jul 27 06:23:32 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 8659B21F8BA9 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 06:23:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.35
X-Spam-Level: 
X-Spam-Status: No, score=-110.35 tagged_above=-999 required=5 tests=[AWL=0.849, 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 wxLRCo8Ttc9a for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 06:23:32 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 9FF6821F8BA8 for <ietf@ietf.org>; Wed, 27 Jul 2011 06:23:31 -0700 (PDT)
Received: (qmail 96984 invoked from network); 27 Jul 2011 13:23:30 -0000
Received: from gal.iecc.com (64.57.183.53) by mail2.iecc.com with SMTP; 27 Jul 2011 13:23:30 -0000
Received: (qmail 53297 invoked from network); 27 Jul 2011 13:23:30 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 27 Jul 2011 13:23:30 -0000
Date: 27 Jul 2011 13:23:08 -0000
Message-ID: <20110727132308.6972.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: DKIM Signatures now being applied to IETF Email
In-Reply-To: <20110727084606.GA16280@nic.fr>
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, 27 Jul 2011 13:23:32 -0000

>> I am very pleased to report that the IETF is now applying DKIM signatures
>> to all outgoing list email from mailman.
>
>What about a RFC 5617 published signing practice?

That RFC is only useful for a narrow range of heavily phished domains
like Paypal's.  Fabulous though the IETF is, it's not one of them.

R's,
John

From moore@network-heretics.com  Wed Jul 27 06:35: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 4BC3A11E8096; Wed, 27 Jul 2011 06:35:21 -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 3WAIRM19Zo+u; Wed, 27 Jul 2011 06:35:20 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 5C04F11E8085; Wed, 27 Jul 2011 06:35:20 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 1283A20F40; Wed, 27 Jul 2011 09:35:20 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Wed, 27 Jul 2011 09:35:20 -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=rCs j39ZbfoAVzvPfEqAJNrlH4c8=; b=D/ceINFAGorplUwH3pfg9/zo8iuQA0f8ttH efGq5DtYi1LTZ94sfnnkFUrthejYUCU/OvuY2bnVacuaq13CPwTr+fUxNtx0ggbu uGpgQbrJLEJta8/Z0WMEJnkl4LD6NRVyymeKdYHQAP38CvEXooyZeevn4zPpvtgW MJTiUCDc=
X-Sasl-enc: iogXk/Dp105PWrSJa8ojR3bky+dg9Gzr9aYU7P8TZCiX 1311773719
Received: from dhcp-12d1.meeting.ietf.org (dhcp-12d1.meeting.ietf.org [130.129.18.209]) by mail.messagingengine.com (Postfix) with ESMTPSA id A8A0E414428; Wed, 27 Jul 2011 09:35:19 -0400 (EDT)
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-35-606553518
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <CA+OBy1O1ji-ETnAa2oQ8p4OUtd7WjGScyp0xPUTFdm00iaAK=g@mail.gmail.com>
Date: Wed, 27 Jul 2011 09:35:18 -0400
Message-Id: <F30119B7-3400-4685-A929-A85A48ECD51E@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com> <5A600744-8605-46D3-82B2-C3C30E30E4AC@network-heretics.com> <CA+OBy1O1ji-ETnAa2oQ8p4OUtd7WjGScyp0xPUTFdm00iaAK=g@mail.gmail.com>
To: "John Mann (ITS)" <john.mann@monash.edu>
X-Mailer: Apple Mail (2.1084)
Cc: IPv6 Operations <v6ops@ietf.org>, ietf@ietf.org, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 13:35:21 -0000

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


On Jul 27, 2011, at 9:07 AM, John Mann (ITS) wrote:

>=20
> > Actually, I think one could argue pretty effectively that 6rd is =
6to4-bis.
>=20
> only if you're confused about the use cases for each.
>=20
> In my opinion:
>=20
> 6to4 use case
> - D.I.Y setup - no ISP involvement
> - depend upon kindness of strangers to run the anycast relays
> - some users have hard-to-solve reliability problems
> - experimental / historic / not-recommended - should be off by default
> - for users who would prefer "unreliable IPv6" to "no IPv6"

close, but no cigar.

the use case for 6to4 is when
- you have a public IPv4 address
- your ISP doesn't support any kind of IPv6 access
- there's no good native v6 tunnel endpoint near your host, or your host =
is mobile
- you have applications for IPv6 other than to access content that is =
also available via IPv4, OR your hosts are set up to prefer native IPv4 =
over 6to4 addresses

>=20
> 6rd use case
> - configuration parameters set by ISP
> - ISP runs the relays
> - apparently production quality (see free.fr)
> - for users who would prefer "no IPv6" to "unreliable Internet"
>=20
> I agree that 6rd is not a replacement protocol for the 6to4 use case.
>=20
> I will argue that the "6rd use case" is a replacement for the "6to4 =
use case".

If you have 6rd or any kind of native IPv6 available to you, you'll =
almost certainly prefer it to 6to4, except perhaps when needing to =
communicate with other hosts using 6to4.

The problem is that native IPv6 is not widely available, and will not be =
universally available for maybe 10 years. =20

(Or maybe, never, because the deployment model in many people's minds =
assumes that the only reason to use IPv6 is to "access content" that =
will continue to be available via IPv4 indefinitely.)

> We want normal users to move past "experimental IPv6" towards =
"production IPv6".

I want that too.   What I object to is a denial-of-service attack on =
people who find 6to4 useful, just because it doesn't work as well as =
IPv4 for services that support both IPv4 and IPv6.

Keith


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

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jul 27, 2011, at 9:07 AM, John Mann (ITS) =
wrote:</div><br class=3D"Apple-interchange-newline"><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 class=3D"im"><br>
&gt; Actually, I think one could argue pretty effectively that 6rd is =
6to4-bis.<br>
<br>
</div>only if you're confused about the use cases for =
each.</blockquote><div><br></div><div>In my =
opinion:</div><div><br></div><div>6to4 use case</div><div>- D.I.Y setup =
- no ISP involvement</div><div>- depend upon kindness of strangers to =
run the anycast relays</div>

<div>- some users have hard-to-solve reliability problems</div><div>- =
experimental / historic / not-recommended - should be off by =
default</div><div>- for users who would prefer "unreliable IPv6" to "no =
IPv6"</div></div></blockquote><div><br></div>close, but no =
cigar.</div><div><br></div><div>the use case for 6to4 is =
when</div><div>- you have a public IPv4 address</div><div>- your ISP =
doesn't support any kind of IPv6 access</div><div>- there's no good =
native v6 tunnel endpoint near your host, or your host is =
mobile</div><div>- you have applications for IPv6 other than to access =
content that is also available via IPv4, OR your hosts are set up to =
prefer native IPv4 over 6to4 addresses</div><div><br><blockquote =
type=3D"cite"><div class=3D"gmail_quote">

<div><br></div><div>6rd use case</div><div>- configuration parameters =
set by ISP</div><div>- ISP runs the relays</div><div>- apparently =
production quality (see <a =
href=3D"http://free.fr/">free.fr</a>)</div><div>- for users who would =
prefer "no IPv6" to "unreliable Internet"</div>

<div><br></div><div>I agree that 6rd is not a replacement protocol for =
the 6to4 use case.</div><div><br></div><div>I will argue that the "6rd =
use case" is a replacement for the "6to4 use =
case".</div></div></blockquote><div><br></div>If you have 6rd or any =
kind of native IPv6 available to you, you'll almost certainly prefer it =
to 6to4, except perhaps when needing to communicate with other hosts =
using 6to4.</div><div><br></div><div>The problem is that native IPv6 is =
not widely available, and will not be universally available for maybe 10 =
years. &nbsp;</div><div><br></div><div>(Or maybe, never, because the =
deployment model in many people's minds assumes that the only reason to =
use IPv6 is to "access content" that will continue to be available via =
IPv4 indefinitely.)</div><div><br></div><div><blockquote =
type=3D"cite"><div class=3D"gmail_quote"><div>We want normal users to =
move past "experimental IPv6" towards "production =
IPv6".</div></div></blockquote><br></div><div>I want that too. &nbsp; =
What I object to is a denial-of-service attack on people who find 6to4 =
useful, just because it doesn't work as well as IPv4 for services that =
support both IPv4 and =
IPv6.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-35-606553518--

From dhc2@dcrocker.net  Wed Jul 27 06:37:37 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 DFC6321F8A7A for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 06:37:37 -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 s1CqZGRYGi7V for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 06:37:36 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id F421D21F8799 for <ietf@ietf.org>; Wed, 27 Jul 2011 06:37:35 -0700 (PDT)
Received: from [130.129.85.251] (dhcp-55fb.meeting.ietf.org [130.129.85.251]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p6RDbQLu008310 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Jul 2011 06:37:34 -0700
Message-ID: <4E301494.4090309@dcrocker.net>
Date: Wed, 27 Jul 2011 09:37:24 -0400
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Subject: Re: DKIM Signatures now being applied to IETF Email
References: <20110725171748.GA13506@amsl.com> <20110727084606.GA16280@nic.fr>
In-Reply-To: <20110727084606.GA16280@nic.fr>
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, 27 Jul 2011 06:37:34 -0700 (PDT)
Cc: ietf@ietf.org, Glen <glen@amsl.com>
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, 27 Jul 2011 13:37:38 -0000

On 7/27/2011 4:46 AM, Stephane Bortzmeyer wrote:
>> I am very pleased to report that the IETF is now applying DKIM signatures
>> to all outgoing list email from mailman.
>
> What about a RFC 5617 published signing practice?


ADSP only works when the domain in the From: field is the same as the signer's 
domain name.  It really is tailored to use by highly phished sites acting as 
fully-integrated bulk senders.  It cannot work with more diverse environments.

The IETF email environment qualifies as extremely diverse.  Our mailing list 
operation breaks ADSP.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From stpeter@stpeter.im  Wed Jul 27 07:22:47 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 3344111E80B3 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 07:22:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.538
X-Spam-Level: 
X-Spam-Status: No, score=-102.538 tagged_above=-999 required=5 tests=[AWL=0.061, 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 u-AARLtmKuKp for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 07:22:46 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 7AE2E228011 for <ietf@ietf.org>; Wed, 27 Jul 2011 07:22:46 -0700 (PDT)
Received: from dhcp-13ac.meeting.ietf.org (unknown [198.135.0.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 24531411C7 for <ietf@ietf.org>; Wed, 27 Jul 2011 08:23:47 -0600 (MDT)
Message-ID: <4E301F34.3060900@stpeter.im>
Date: Wed, 27 Jul 2011 10:22:44 -0400
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: slide numbers
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
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, 27 Jul 2011 14:22:47 -0000

Dear Presenters,

Please include slide numbers in your presentations. This makes life much
easier for remote participants and jabber scribes.

Thanks!

Peter

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



From ggm+ietf@apnic.net  Wed Jul 27 07:24:12 2011
Return-Path: <ggm+ietf@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB7CD11E807A for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 07:24:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.518
X-Spam-Level: 
X-Spam-Status: No, score=-101.518 tagged_above=-999 required=5 tests=[AWL=1.081, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 52G7QGPBDNQ9 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 07:24:12 -0700 (PDT)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id C4AF911E80CD for <ietf@ietf.org>; Wed, 27 Jul 2011 07:24:10 -0700 (PDT)
Received: from dhcp-53cd.meeting.ietf.org (dhcp-53cd.meeting.ietf.org [130.129.83.205]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id C3CEAB68D8; Thu, 28 Jul 2011 00:24:07 +1000 (EST)
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: George Michaelson <ggm+ietf@apnic.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
Date: Wed, 27 Jul 2011 10:23:59 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4402A0A2-76BD-4043-9B71-78F6A5825DC7@apnic.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
To: Ronald Bonica <rbonica@juniper.net>
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: Wed, 27 Jul 2011 14:24:12 -0000

I have considered the issues I had facing 6to4 deprecation, and in the =
light of what you propose here, and other discussions, I support this =
course of action.

-George

On 25/07/2011, at 10:30 AM, Ronald Bonica wrote:

> Folks,
>=20
> After some discussion, the IESG is attempting to determine whether =
there is IETF consensus to do the following:
>=20
> - add a new section to draft-ietf-v6ops-6to4-to-historic
> - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL
>=20
> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 and =
convert their status to HISTORIC. It will also contain a new section =
describing what it means for RFCs 3056 and 3068 to be classified as =
HISTORIC. The new section will say that:
>=20
> - 6-to-4 should not be configured by default on any implementation =
(hosts, cpe routers, other)
> - vendors will decide whether/when 6-to-4 will be removed from =
implementations. Likewise, operators will decide whether/when 6-to-4 =
relays will be removed from their networks. The status of RFCs 3056 and =
3068 should not be interpreted as a recommendation to remove 6-to-4 at =
any particular time.
>=20
>=20
> draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While it =
clarifies the meaning of "HISTORIC" in this particular case, it does not =
set a precedent for any future case.
>=20
> Please post your views on this course of action by August 8, 2011.
>=20
>=20
>                                                                   Ron =
Bonica
>                                                                   =
<speaking as OPS Area AD>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From cb.list6@gmail.com  Wed Jul 27 07:27:20 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 849FA21F8A30; Wed, 27 Jul 2011 07:27:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.993
X-Spam-Level: 
X-Spam-Status: No, score=-2.993 tagged_above=-999 required=5 tests=[AWL=0.005,  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 rT3Q1du6HVBm; Wed, 27 Jul 2011 07:27: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 9914821F89C1; Wed, 27 Jul 2011 07:27:19 -0700 (PDT)
Received: by wyj26 with SMTP id 26so984462wyj.31 for <multiple recipients>; Wed, 27 Jul 2011 07:27:18 -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=SFMZOTL1Ip0BEnt5jeAOMIGrnWcDWH5bj8N1Hd8ITZE=; b=mAXsv27UUsY6KdsG2FaN4/BfxAu2kEUN5PQripOwJICm3FTKmOSmMIfCy135EP8UEn TcnPzLfJhEy/2BU7U2ZwpnvKsUGENUJSldOz2MyfVDHh+cGb/8echO5cK68yiI2Ir3dU CDXWFmtSLfmvNodXn1e5BpiW+Nr+cTPn/rzB4=
MIME-Version: 1.0
Received: by 10.217.3.17 with SMTP id q17mr2682230wes.107.1311776838109; Wed, 27 Jul 2011 07:27:18 -0700 (PDT)
Received: by 10.216.161.136 with HTTP; Wed, 27 Jul 2011 07:27:17 -0700 (PDT)
Received: by 10.216.161.136 with HTTP; Wed, 27 Jul 2011 07:27:17 -0700 (PDT)
In-Reply-To: <39EEA819-6D8D-4FE7-958D-D7DCEDF893C1@townsley.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com> <39EEA819-6D8D-4FE7-958D-D7DCEDF893C1@townsley.net>
Date: Wed, 27 Jul 2011 07:27:17 -0700
Message-ID: <CAD6AjGTPjhD=yiv5Pe6G4TRGKnPyzn0_nMk9v8bevmGtqu2g3A@mail.gmail.com>
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
From: Cameron Byrne <cb.list6@gmail.com>
To: Mark Townsley <mark@townsley.net>
Content-Type: multipart/alternative; boundary=20cf301e2f2775cb4c04a90dd8d8
Cc: IPv6 Operations <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, 27 Jul 2011 14:27:20 -0000

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

On Jul 27, 2011 4:32 AM, "Mark Townsley" <mark@townsley.net> wrote:
>
>
> On Jul 27, 2011, at 7:09 AM, Fred Baker wrote:
>
> >
> > On Jul 26, 2011, at 6:49 PM, Brian E Carpenter wrote:
> >
> >> Since 6to4 is a transition mechanism it has no long term future *by
definition*. Even if someone chooses to design a v2, who is going to
implement it?
> >
> > Actually, I think one could argue pretty effectively that 6rd is
6to4-bis.
>
> +1
>

+1 as well as 6in4 or native v6.

The full requirements of 6to4 are based on currently unrealistic
requirements for no-nat (apnic is post exhaust ) and service providers to
stand up relays without a reasonable business case

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

--20cf301e2f2775cb4c04a90dd8d8
Content-Type: text/html; charset=ISO-8859-1

<p><br>
On Jul 27, 2011 4:32 AM, &quot;Mark Townsley&quot; &lt;<a href="mailto:mark@townsley.net">mark@townsley.net</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; On Jul 27, 2011, at 7:09 AM, Fred Baker wrote:<br>
&gt;<br>
&gt; &gt;<br>
&gt; &gt; On Jul 26, 2011, at 6:49 PM, Brian E Carpenter wrote:<br>
&gt; &gt;<br>
&gt; &gt;&gt; Since 6to4 is a transition mechanism it has no long term future *by definition*. Even if someone chooses to design a v2, who is going to implement it?<br>
&gt; &gt;<br>
&gt; &gt; Actually, I think one could argue pretty effectively that 6rd is 6to4-bis.<br>
&gt;<br>
&gt; +1<br>
&gt;</p>
<p>+1 as well as 6in4 or native v6.</p>
<p>The full requirements of 6to4 are based on currently unrealistic requirements for no-nat (apnic is post exhaust ) and service providers to stand up relays without a reasonable business case <br></p>
<p>&gt; - Mark<br>
&gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; v6ops mailing list<br>
&gt; &gt; <a href="mailto:v6ops@ietf.org">v6ops@ietf.org</a><br>
&gt; &gt; <a href="https://www.ietf.org/mailman/listinfo/v6ops">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; v6ops mailing list<br>
&gt; <a href="mailto:v6ops@ietf.org">v6ops@ietf.org</a><br>
&gt; <a href="https://www.ietf.org/mailman/listinfo/v6ops">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
</p>

--20cf301e2f2775cb4c04a90dd8d8--

From henk.uijterwaal@gmail.com  Wed Jul 27 07:29:35 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 6403D21F8A4B for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 07:29:35 -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.226,  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 kHC+P-mf6XCv for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 07:29:34 -0700 (PDT)
Received: from mail-ey0-f176.google.com (mail-ey0-f176.google.com [209.85.215.176]) by ietfa.amsl.com (Postfix) with ESMTP id 7F87621F89C1 for <ietf@ietf.org>; Wed, 27 Jul 2011 07:29:34 -0700 (PDT)
Received: by eya28 with SMTP id 28so2341390eya.21 for <ietf@ietf.org>; Wed, 27 Jul 2011 07:29:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=pW+eW1JkK5B2CdEAJ0dS6bmmjVZYvBzhWLVIBCF0wpY=; b=RyzvJEePmaqm4860OaIXtNtIZHcwDv8wm8UQVmbwJsPFpDXt0O/W1X5pmcjGEoCLEN cXxn65N2PhkX66Zr/r/V53xcSjdEv0uqUP1XnFbF0qBCDe3EKMM0/FP7mBDnZrHWv+QM hRuDc0Voh+FrDY+0FZly0WaAY96LJIAqAi33o=
Received: by 10.213.7.220 with SMTP id e28mr365703ebe.82.1311776968017; Wed, 27 Jul 2011 07:29:28 -0700 (PDT)
Received: from geir.local (thuis.uijterwaal.nl [82.95.178.49]) by mx.google.com with ESMTPS id v11sm70552eev.59.2011.07.27.07.29.26 (version=SSLv3 cipher=OTHER); Wed, 27 Jul 2011 07:29:27 -0700 (PDT)
Message-ID: <4E3020C5.1010503@gmail.com>
Date: Wed, 27 Jul 2011 16:29:25 +0200
From: Henk Uijterwaal <henk.uijterwaal@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: slide numbers
References: <4E301F34.3060900@stpeter.im>
In-Reply-To: <4E301F34.3060900@stpeter.im>
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: Wed, 27 Jul 2011 14:29:35 -0000

On 27/07/2011 16:22, Peter Saint-Andre wrote:
> Dear Presenters,
> 
> Please include slide numbers in your presentations. This makes life much
> easier for remote participants and jabber scribes.

And also when you are presenting, please say on which slide you are.

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 cb.list6@gmail.com  Wed Jul 27 07:37: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 5D88721F8639; Wed, 27 Jul 2011 07:37:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.993
X-Spam-Level: 
X-Spam-Status: No, score=-2.993 tagged_above=-999 required=5 tests=[AWL=0.005,  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 zEcDSRbS-atM; Wed, 27 Jul 2011 07:37:25 -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 D519921F861E; Wed, 27 Jul 2011 07:37:24 -0700 (PDT)
Received: by wwe5 with SMTP id 5so978752wwe.13 for <multiple recipients>; Wed, 27 Jul 2011 07:37:24 -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=oPXhWh34+TyOxPVNjseeYUd+oFMs5Eim5DWCp99dHlM=; b=miMFPYHR323W4hy2uYH+4gL/jd62qcfcwe1qDYbV8LP9cHlPr2MI2gJQVE+tGn8CXh bmUyfaML0MpdWAKekm7gS1zuPC4bRZCOuHolCuWHMVWEV1UnfcJf9yyz7oU5v18olXBG 5c5GHj/7BRToKnTUzPu84VabbtfrljbjWQMXs=
MIME-Version: 1.0
Received: by 10.216.8.204 with SMTP id 54mr87991wer.92.1311777443806; Wed, 27 Jul 2011 07:37:23 -0700 (PDT)
Received: by 10.216.161.136 with HTTP; Wed, 27 Jul 2011 07:37:22 -0700 (PDT)
Received: by 10.216.161.136 with HTTP; Wed, 27 Jul 2011 07:37:22 -0700 (PDT)
In-Reply-To: <968F0B1C-D082-4A59-8213-FD58C74AF89D@nominum.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <968F0B1C-D082-4A59-8213-FD58C74AF89D@nominum.com>
Date: Wed, 27 Jul 2011 07:37:22 -0700
Message-ID: <CAD6AjGSGrQTgcFDopdDLkrgXeduqP79sKgC4qtzb8boAjkbLng@mail.gmail.com>
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
From: Cameron Byrne <cb.list6@gmail.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary=0016364c7a7f8ffec104a90dfc22
Cc: IPv6 Operations <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, 27 Jul 2011 14:37:26 -0000

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

On Jul 27, 2011 7:20 AM, "Ted Lemon" <Ted.Lemon@nominum.com> wrote:
>>>
>>> If you have a reason to install and enable 6to4, why would the nominal
>>>
>>> status of a couple of RFCs make you do anything different?
>
>
> This seems like an easy question to answer.   You'd implement and use
6to4v2 because it works better than the historic 6to4 protocol.
>
>

It seems like there is this deep philosophical discussion about historic
status. From what I can tell, ietf sent nat-pt to historic well before nat64
came about. Many people were using nat-pt too ... but going to historic
forced things along. It was a good choice in hindsight.

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

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

<p><br>
On Jul 27, 2011 7:20 AM, &quot;Ted Lemon&quot; &lt;<a href=3D"mailto:Ted.Le=
mon@nominum.com">Ted.Lemon@nominum.com</a>&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; If you have a reason to install and enable 6to4, why would the=
 nominal<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; status of a couple of RFCs make you do anything different?<br>
&gt;<br>
&gt;<br>
&gt; This seems like an easy question to answer. =A0 You&#39;d implement an=
d use 6to4v2 because it works better than the historic 6to4 protocol.<br>
&gt;<br>
&gt;</p>
<p>It seems like there is this deep philosophical discussion about historic=
 status. From what I can tell, ietf sent nat-pt to historic well before nat=
64 came about. Many people were using nat-pt too ... but going to historic =
forced things along. It was a good choice in hindsight. </p>

<p>Cb <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>
&gt;<br>
</p>

--0016364c7a7f8ffec104a90dfc22--

From marka@isc.org  Wed Jul 27 08:09: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 EB5E521F8BC3; Wed, 27 Jul 2011 08:09:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=-0.001,  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 6JB+E2oG3jZF; Wed, 27 Jul 2011 08:09: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 1A03A21F8BC2; Wed, 27 Jul 2011 08:09: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 CE5385F991A; Wed, 27 Jul 2011 15:08:40 +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 C09C0216C86; Wed, 27 Jul 2011 15:08: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 69F5B1235C62; Thu, 28 Jul 2011 01:08:32 +1000 (EST)
To: Cameron Byrne <cb.list6@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com> <39EEA819-6D8D-4FE7-958D-D7DCEDF893C1@townsley.net> <CAD6AjGTPjhD=yiv5Pe6G4TRGKnPyzn0_nMk9v8bevmGtqu2g3A@mail.gmail.com>
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
In-reply-to: Your message of "Wed, 27 Jul 2011 07:27:17 MST." <CAD6AjGTPjhD=yiv5Pe6G4TRGKnPyzn0_nMk9v8bevmGtqu2g3A@mail.gmail.com>
Date: Thu, 28 Jul 2011 01:08:32 +1000
Message-Id: <20110727150832.69F5B1235C62@drugs.dv.isc.org>
Cc: IPv6 Operations <v6ops@ietf.org>, Mark Townsley <mark@townsley.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 15:09:06 -0000

In message <CAD6AjGTPjhD=yiv5Pe6G4TRGKnPyzn0_nMk9v8bevmGtqu2g3A@mail.gmail.com>
, Cameron Byrne writes:
> 
> On Jul 27, 2011 4:32 AM, "Mark Townsley" <mark@townsley.net> wrote:
> >
> >
> > On Jul 27, 2011, at 7:09 AM, Fred Baker wrote:
> >
> > >
> > > On Jul 26, 2011, at 6:49 PM, Brian E Carpenter wrote:
> > >
> > >> Since 6to4 is a transition mechanism it has no long term future *by
> definition*. Even if someone chooses to design a v2, who is going to
> implement it?
> > >
> > > Actually, I think one could argue pretty effectively that 6rd is
> 6to4-bis.
> >
> > +1
> >
> 
> +1 as well as 6in4 or native v6.
> 
> The full requirements of 6to4 are based on currently unrealistic
> requirements for no-nat (apnic is post exhaust ) and service providers to
> stand up relays without a reasonable business case
 
There are lots of things that require no-nat.  6to4 is just one of
them.  ISP will end up providing no-nat for those that need it the
same way as they provide unfiltered port 25 for those that need it
and it also shouldn't cost more.

Yet there are relays out there and there are business cases to run
them.

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  Wed Jul 27 08:16:13 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 F108B21F889A; Wed, 27 Jul 2011 08:16: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=[AWL=-0.001,  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 7OVWx59CBn33; Wed, 27 Jul 2011 08:16:12 -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 6EC6421F885E; Wed, 27 Jul 2011 08:16:12 -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 D674E5F9978; Wed, 27 Jul 2011 15:15:51 +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 19CD9216C86; Wed, 27 Jul 2011 15:15:20 +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 CF9371235D70; Thu, 28 Jul 2011 01:15:17 +1000 (EST)
To: Ted Lemon <Ted.Lemon@nominum.com>
From: Mark Andrews <marka@isc.org>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <968F0B1C-D082-4A59-8213-FD58C74AF89D@nominum.com>
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
In-reply-to: Your message of "Wed, 27 Jul 2011 14:20:11 GMT." <968F0B1C-D082-4A59-8213-FD58C74AF89D@nominum.com>
Date: Thu, 28 Jul 2011 01:15:17 +1000
Message-Id: <20110727151517.CF9371235D70@drugs.dv.isc.org>
Cc: "<ietf@ietf.org>" <ietf@ietf.org>, IPv6 Operations <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, 27 Jul 2011 15:16:13 -0000

In message <968F0B1C-D082-4A59-8213-FD58C74AF89D@nominum.com>, Ted Lemon writes
:
> If you have a reason to install and enable 6to4, why would the nominal
> status of a couple of RFCs make you do anything different?

Because it will come down to "run 6to4 and be exposed to some bug"
or "not run 6to4 but be safe from the bug".  We already have vendors
saying they are thinking about pulling 6to4 from their code bases
if it becomes historic.

> This seems like an easy question to answer.   You'd implement and use 6to4v=
> 2 because it works better than the historic 6to4 protocol.
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From cb.list6@gmail.com  Wed Jul 27 08:27:56 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 7A0B721F8B04; Wed, 27 Jul 2011 08:27:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.994
X-Spam-Level: 
X-Spam-Status: No, score=-2.994 tagged_above=-999 required=5 tests=[AWL=0.004,  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 o74oUzDVFbHN; Wed, 27 Jul 2011 08:27:55 -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 3327A21F8783; Wed, 27 Jul 2011 08:27:54 -0700 (PDT)
Received: by wyj26 with SMTP id 26so1032064wyj.31 for <multiple recipients>; Wed, 27 Jul 2011 08:27:54 -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=YiGuEk+4OEeEBFbClf3M4GzDg3z11MjUn2SutStxkk0=; b=nNJ1pOnG7T7pNJQrOBnwv2XhBzYkCwDWR5sersCojYOaccv9dEAfePpPDMEcMxOLbY VndjI3rzOy9qZykvwjk6ppTb/tT+PKylUFU73lbgyYsxmoeBvlMS+fa8b8q/mNg/3J5G ZH/tUfa9kHwvbET//B5OYqdzn88JodMC0X5o4=
MIME-Version: 1.0
Received: by 10.217.3.17 with SMTP id q17mr906wes.107.1311780474124; Wed, 27 Jul 2011 08:27:54 -0700 (PDT)
Received: by 10.216.161.136 with HTTP; Wed, 27 Jul 2011 08:27:54 -0700 (PDT)
Received: by 10.216.161.136 with HTTP; Wed, 27 Jul 2011 08:27:54 -0700 (PDT)
In-Reply-To: <20110727151517.CF9371235D70@drugs.dv.isc.org>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <968F0B1C-D082-4A59-8213-FD58C74AF89D@nominum.com> <20110727151517.CF9371235D70@drugs.dv.isc.org>
Date: Wed, 27 Jul 2011 08:27:54 -0700
Message-ID: <CAD6AjGThTpvH5HgGc8RbedOcJKZ=_JLR=2t7yAAJWKSS1cKNSg@mail.gmail.com>
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
From: Cameron Byrne <cb.list6@gmail.com>
To: Mark Andrews <marka@isc.org>
Content-Type: multipart/alternative; boundary=20cf301e2f272efb3604a90eb1e5
Cc: "<ietf@ietf.org>" <ietf@ietf.org>, IPv6 Operations <v6ops@ietf.org>, Ted Lemon <Ted.Lemon@nominum.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, 27 Jul 2011 15:27:56 -0000

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

On Jul 27, 2011 8:16 AM, "Mark Andrews" <marka@isc.org> wrote:
>
>
> In message <968F0B1C-D082-4A59-8213-FD58C74AF89D@nominum.com>, Ted Lemon
writes
> :
> > If you have a reason to install and enable 6to4, why would the nominal
> > status of a couple of RFCs make you do anything different?
>
> Because it will come down to "run 6to4 and be exposed to some bug"
> or "not run 6to4 but be safe from the bug".  We already have vendors
> saying they are thinking about pulling 6to4 from their code bases
> if it becomes historic.
>

You also have content owners that say no aaaa while 6to4 is tanking
reliability stats.

Pick your battles.

Cb
> > This seems like an easy question to answer.   You'd implement and use
6to4v=
> > 2 because it works better than the historic 6to4 protocol.
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

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

<p><br>
On Jul 27, 2011 8:16 AM, &quot;Mark Andrews&quot; &lt;<a href=3D"mailto:mar=
ka@isc.org">marka@isc.org</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; In message &lt;<a href=3D"mailto:968F0B1C-D082-4A59-8213-FD58C74AF89D@=
nominum.com">968F0B1C-D082-4A59-8213-FD58C74AF89D@nominum.com</a>&gt;, Ted =
Lemon writes<br>
&gt; :<br>
&gt; &gt; If you have a reason to install and enable 6to4, why would the no=
minal<br>
&gt; &gt; status of a couple of RFCs make you do anything different?<br>
&gt;<br>
&gt; Because it will come down to &quot;run 6to4 and be exposed to some bug=
&quot;<br>
&gt; or &quot;not run 6to4 but be safe from the bug&quot;. =A0We already ha=
ve vendors<br>
&gt; saying they are thinking about pulling 6to4 from their code bases<br>
&gt; if it becomes historic.<br>
&gt;</p>
<p>You also have content owners that say no aaaa while 6to4 is tanking reli=
ability stats.</p>
<p>Pick your battles.</p>
<p>Cb<br>
&gt; &gt; This seems like an easy question to answer. =A0 You&#39;d impleme=
nt and use 6to4v=3D<br>
&gt; &gt; 2 because it works better than the historic 6to4 protocol.<br>
&gt; --<br>
&gt; Mark Andrews, ISC<br>
&gt; 1 Seymour St., Dundas Valley, NSW 2117, Australia<br>
&gt; PHONE: +61 2 9871 4742 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 INTERNET: <a hr=
ef=3D"mailto:marka@isc.org">marka@isc.org</a><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>

--20cf301e2f272efb3604a90eb1e5--

From joelja@bogus.com  Wed Jul 27 08:29: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 6981821F8B04; Wed, 27 Jul 2011 08:29:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102
X-Spam-Level: 
X-Spam-Status: No, score=-102 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=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 PNEg4MeyNXrx; Wed, 27 Jul 2011 08:29:05 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 9315921F8783; Wed, 27 Jul 2011 08:29:04 -0700 (PDT)
Received: from [IPv6:2001:df8::80:129a:ddff:feb1:e750] ([IPv6:2001:df8:0:80:129a:ddff:feb1:e750]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p6RFSwa5025754 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 27 Jul 2011 15:29:00 GMT (envelope-from joelja@bogus.com)
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-24-613313371
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <CAD6AjGSGrQTgcFDopdDLkrgXeduqP79sKgC4qtzb8boAjkbLng@mail.gmail.com>
Date: Wed, 27 Jul 2011 11:27:58 -0400
Message-Id: <9C388DC9-A440-4C78-8798-9FE822AC78BE@bogus.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <968F0B1C-D082-4A59-8213-FD58C74AF89D@nominum.com> <CAD6AjGSGrQTgcFDopdDLkrgXeduqP79sKgC4qtzb8boAjkbLng@mail.gmail.com>
To: Cameron Byrne <cb.list6@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 [IPv6:2001:418:1::81]); Wed, 27 Jul 2011 15:29:00 +0000 (UTC)
Cc: IPv6 Operations <v6ops@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 15:29:05 -0000

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


On Jul 27, 2011, at 10:37 AM, Cameron Byrne wrote:

>=20
> On Jul 27, 2011 7:20 AM, "Ted Lemon" <Ted.Lemon@nominum.com> wrote:
> >>>
> >>> If you have a reason to install and enable 6to4, why would the =
nominal
> >>>
> >>> status of a couple of RFCs make you do anything different?
> >
> >
> > This seems like an easy question to answer.   You'd implement and =
use 6to4v2 because it works better than the historic 6to4 protocol.
> >
> >
>=20
> It seems like there is this deep philosophical discussion about =
historic status. =46rom what I can tell, ietf sent nat-pt to historic =
well before nat64 came about. Many people were using nat-pt too ... but =
going to historic forced things along. It was a good choice in =
hindsight.
>=20

And natpt implementations still exist and are used by consenting adults. =
At a previous employer we were considering the business case for an =
implementation well after it's historic status. better solutions came =
along.

> Cb=20
>=20
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
> >
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


--Apple-Mail-24-613313371
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 Jul 27, 2011, at 10:37 AM, Cameron Byrne wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p><br>
On Jul 27, 2011 7:20 AM, "Ted Lemon" &lt;<a href="mailto:Ted.Lemon@nominum.com">Ted.Lemon@nominum.com</a>&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; If you have a reason to install and enable 6to4, why would the nominal<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; status of a couple of RFCs make you do anything different?<br>
&gt;<br>
&gt;<br>
&gt; This seems like an easy question to answer. &nbsp; You'd implement and use 6to4v2 because it works better than the historic 6to4 protocol.<br>
&gt;<br>
&gt;</p><p>It seems like there is this deep philosophical discussion about historic status. From what I can tell, ietf sent nat-pt to historic well before nat64 came about. Many people were using nat-pt too ... but going to historic forced things along. It was a good choice in hindsight.</p></blockquote><div><br></div><div>And natpt implementations still exist and are used by consenting adults. At a previous employer we were considering the business case for an implementation well after it's historic status. better solutions came along.</div><br><blockquote type="cite"><p>Cb&nbsp;</p><p>
&gt; _______________________________________________<br>
&gt; v6ops mailing list<br>
&gt; <a href="mailto:v6ops@ietf.org">v6ops@ietf.org</a><br>
&gt; <a href="https://www.ietf.org/mailman/listinfo/v6ops">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
&gt;<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-24-613313371--

From michel@arneill-py.sacramento.ca.us  Wed Jul 27 08:29: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 B22DB21F8783 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 08:29:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level: 
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[AWL=0.269,  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 j7vV527RqhPP for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 08:29: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 792CC11E80B3 for <ietf@ietf.org>; Wed, 27 Jul 2011 08:29:37 -0700 (PDT)
Subject: RE: 6to4v2 (as in ripv2)? 
Date: Wed, 27 Jul 2011 08:29:36 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF625@newserver.arneill-py.local>
In-Reply-To: <5A600744-8605-46D3-82B2-C3C30E30E4AC@network-heretics.com>
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: 6to4v2 (as in ripv2)? 
Thread-Index: AcxMVvYKCCAnZeW2QEm38SmwLFnVxQAF8Dcg
X-MimeOLE: Produced By Microsoft Exchange V6.5
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com>	<4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net><4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com><72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com> <5A600744-8605-46D3-82B2-C3C30E30E4AC@network-heretics.com>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Keith Moore" <moore@network-heretics.com>, "Fred Baker" <fred@cisco.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, 27 Jul 2011 15:29:41 -0000

>>> Brian E Carpenter wrote:
>>> Since 6to4 is a transition mechanism it has no long
>>> term future *by definition*. Even if someone chooses
>>> to design a v2, who is going to implement it?

free.fr, which is a third of the worldwide IPv6 traffic.


>> Fred Baker wrote:
>> Actually, I think one could argue pretty
>> effectively that 6rd is 6to4-bis.

Indeed, and it also is a transition mechanism for the very same reasons
that 6to4 is.


> Keith Moore wrote:
> only if you're confused about the use cases for each.

Even if there are different use cases indeed (as you explained it very
well yourself) you can't deny that 6rd is 6to4-bis. The difference is in
who configures/manages it, not how it works; the 6rd code base is a
superset of the 6to4. The difference is more a matter of network design
than core protocol.

Michel.


From cb.list6@gmail.com  Wed Jul 27 08:33:49 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 96E1621F8BCE for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 08:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.294
X-Spam-Level: 
X-Spam-Status: No, score=-3.294 tagged_above=-999 required=5 tests=[AWL=0.304,  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 QqP95RT00jMe for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 08:33:49 -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 27E8321F8BCF for <ietf@ietf.org>; Wed, 27 Jul 2011 08:33:47 -0700 (PDT)
Received: by wwg11 with SMTP id 11so3176238wwg.1 for <ietf@ietf.org>; Wed, 27 Jul 2011 08:33:47 -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=t2rihIGuQcGH1gZOztiTL8B77oJB+w0k7sZZDSrnYow=; b=PRERZBKyp59p5cBYZcGpx/1O4qvvKiQ5OJD6UAgnenU4rYNPwULfBZX1wK5m6J/Keo 6G0uMfFn2A7QwNW8h5roYbjaNLZ/ZtkmQM76Sx6u5LbIo2Zq+ZciRYrFKIHeG+q0+NId TTUTCkTJGyo951gryLnJiMYuEMjfACyPsGdsE=
MIME-Version: 1.0
Received: by 10.216.8.204 with SMTP id 54mr141526wer.92.1311780827166; Wed, 27 Jul 2011 08:33:47 -0700 (PDT)
Received: by 10.216.161.136 with HTTP; Wed, 27 Jul 2011 08:33:47 -0700 (PDT)
Received: by 10.216.161.136 with HTTP; Wed, 27 Jul 2011 08:33:47 -0700 (PDT)
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF625@newserver.arneill-py.local>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com> <5A600744-8605-46D3-82B2-C3C30E30E4AC@network-heretics.com> <392CB277BC2EAE4FB83C1206954BA6CEF625@newserver.arneill-py.local>
Date: Wed, 27 Jul 2011 08:33:47 -0700
Message-ID: <CAD6AjGQ5zuCLP=m8xHmAD_ufW8gYASJx+OGM0==75S1SMawUfw@mail.gmail.com>
Subject: Re: RE: 6to4v2 (as in ripv2)?
From: Cameron Byrne <cb.list6@gmail.com>
To: Michel Py <michel@arneill-py.sacramento.ca.us>
Content-Type: multipart/alternative; boundary=0016364c7a7f39f78004a90ec65e
Cc: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 15:33:49 -0000

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

On Jul 27, 2011 8:30 AM, "Michel Py" <michel@arneill-py.sacramento.ca.us>
wrote:
>
> >>> Brian E Carpenter wrote:
> >>> Since 6to4 is a transition mechanism it has no long
> >>> term future *by definition*. Even if someone chooses
> >>> to design a v2, who is going to implement it?
>
> free.fr, which is a third of the worldwide IPv6 traffic.
>
>
> >> Fred Baker wrote:
> >> Actually, I think one could argue pretty
> >> effectively that 6rd is 6to4-bis.
>
> Indeed, and it also is a transition mechanism for the very same reasons
> that 6to4 is.
>
>
> > Keith Moore wrote:
> > only if you're confused about the use cases for each.
>
> Even if there are different use cases indeed (as you explained it very
> well yourself) you can't deny that 6rd is 6to4-bis. The difference is in
> who configures/manages it, not how it works; the 6rd code base is a
> superset of the 6to4. The difference is more a matter of network design
> than core protocol.
>

6rd also evolves 6to4 with a real and traceable support model.

Cb

> Michel.
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

--0016364c7a7f39f78004a90ec65e
Content-Type: text/html; charset=ISO-8859-1

<p><br>
On Jul 27, 2011 8:30 AM, &quot;Michel Py&quot; &lt;<a href="mailto:michel@arneill-py.sacramento.ca.us">michel@arneill-py.sacramento.ca.us</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt;&gt;&gt; Brian E Carpenter wrote:<br>
&gt; &gt;&gt;&gt; Since 6to4 is a transition mechanism it has no long<br>
&gt; &gt;&gt;&gt; term future *by definition*. Even if someone chooses<br>
&gt; &gt;&gt;&gt; to design a v2, who is going to implement it?<br>
&gt;<br>
&gt; <a href="http://free.fr">free.fr</a>, which is a third of the worldwide IPv6 traffic.<br>
&gt;<br>
&gt;<br>
&gt; &gt;&gt; Fred Baker wrote:<br>
&gt; &gt;&gt; Actually, I think one could argue pretty<br>
&gt; &gt;&gt; effectively that 6rd is 6to4-bis.<br>
&gt;<br>
&gt; Indeed, and it also is a transition mechanism for the very same reasons<br>
&gt; that 6to4 is.<br>
&gt;<br>
&gt;<br>
&gt; &gt; Keith Moore wrote:<br>
&gt; &gt; only if you&#39;re confused about the use cases for each.<br>
&gt;<br>
&gt; Even if there are different use cases indeed (as you explained it very<br>
&gt; well yourself) you can&#39;t deny that 6rd is 6to4-bis. The difference is in<br>
&gt; who configures/manages it, not how it works; the 6rd code base is a<br>
&gt; superset of the 6to4. The difference is more a matter of network design<br>
&gt; than core protocol.<br>
&gt;</p>
<p>6rd also evolves 6to4 with a real and traceable support model.</p>
<p>Cb</p>
<p>&gt; Michel.<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>

--0016364c7a7f39f78004a90ec65e--

From tjc@ecs.soton.ac.uk  Wed Jul 27 08:35:19 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 0D6EE21F8BDB; Wed, 27 Jul 2011 08:35:19 -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 ItQBnxRW1JXU; Wed, 27 Jul 2011 08:35:17 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 7B55621F8BD8; Wed, 27 Jul 2011 08:35:17 -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 p6RFZCao005041; Wed, 27 Jul 2011 16:35:12 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p6RFZCao005041
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1311780912; bh=euyLtAa7+f1ooboyltGPlCkk5DU=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=o8ogwwELSpzNaxbIHLQ+AAPbo+C4/lcrmGUuJLPVhg0AsXKe85RXOW87+hK9eBvWo HL9WUbwlhzJRfR3VgJVnBk9/LcPFHKAXGWtsuKjVYR0RWY02qrKzuwauNEkA77/tag /21jAXwxhxq8/gKjWmwvTn6Vngwha+w0amhX7HIY=
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 n6QGZC0366144739vf ret-id none; Wed, 27 Jul 2011 16:35:12 +0100
Received: from [IPv6:2001:df8::16:704d:e106:4b6a:660a] ([IPv6:2001:df8:0:16:704d:e106:4b6a:660a]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p6RFZ7i7031397 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 27 Jul 2011 16:35:08 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1244.3)
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <20110727151517.CF9371235D70@drugs.dv.isc.org>
Date: Wed, 27 Jul 2011 16:35:07 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|fcf145b5033ff99790b7c34003f47686n6QGZC03tjc|ecs.soton.ac.uk|D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <968F0B1C-D082-4A59-8213-FD58C74AF89D@nominum.com> <20110727151517.CF9371235D70@drugs.dv.isc.org> <D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk>
To: IETF Discussion <ietf@ietf.org>, IPv6 Operations <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1244.3)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n6QGZC036614473900; tid=n6QGZC0366144739vf; 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: p6RFZCao005041
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, 27 Jul 2011 15:35:19 -0000

On 27 Jul 2011, at 16:15, Mark Andrews wrote:
>=20
> Because it will come down to "run 6to4 and be exposed to some bug"
> or "not run 6to4 but be safe from the bug".  We already have vendors
> saying they are thinking about pulling 6to4 from their code bases
> if it becomes historic.

I would note that RIPE-501 does not mention 6to4:
	http://www.ripe.net/ripe/docs/ripe-501
As far as I can see, it only mentions RFC4213.

I would ask what is the alternative if as Mark suggests the vendors =
begin removing 6to4 support?
a) use 6to4 anyway on an open platform like OpenWRT
b) use a tunnel broker - this works much better through NATs and with =
dynamic IPv4 addresses
c) use your $work VPN if it supports IPv6, which it could/should if your =
company values IPv6
d) get IPv6 from your ISP, or move to one that has it if yours does not

I suspect, but have no proof, that the huge majority of 6to4 users don't =
use it intentionally, and the content they are trying to reach is also =
available over IPv4. But for people who want to develop and use new =
IPv6-specific apps, then either a broker or something like OpenWRT ought =
to meet their needs?

Tim=

From lionel.morand@orange-ftgroup.com  Tue Jul 26 11:26:12 2011
Return-Path: <lionel.morand@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 94EFD21F873D; Tue, 26 Jul 2011 11:26:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.249
X-Spam-Level: 
X-Spam-Status: No, score=-103.249 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 3Gqk1aHxmlkJ; Tue, 26 Jul 2011 11:26:11 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by ietfa.amsl.com (Postfix) with ESMTP id 625A721F86BE; Tue, 26 Jul 2011 11:26:11 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 55C598B8007; Tue, 26 Jul 2011 20:26:59 +0200 (CEST)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by p-mail1.rd.francetelecom.com (Postfix) with ESMTP id 49BF48B8003; Tue, 26 Jul 2011 20:26:59 +0200 (CEST)
Received: from ftrdmel1.rd.francetelecom.fr ([10.192.128.40]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 26 Jul 2011 20:26:10 +0200
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: secdir review of draft-ietf-dime-priority-avps-04
Date: Tue, 26 Jul 2011 20:26:08 +0200
Message-ID: <B11765B89737A7498AF63EA84EC9F577BB648C@ftrdmel1>
In-reply-to: <AC6674AB7BC78549BB231821ABF7A9AEB674517339@EMBX01-WF.jnpr.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-topic: secdir review of draft-ietf-dime-priority-avps-04
Thread-index: AcxLhoMMZuNcnDQsSYq5r0pigpKbWQAApa0wAA115aA=
References: <20110726104135.13472eudbij0eaqs@portland.eukhosting.net> <AC6674AB7BC78549BB231821ABF7A9AEB674516F2B@EMBX01-WF.jnpr.net> <20110726112346.35893ibie0kwerqc@portland.eukhosting.net> <AC6674AB7BC78549BB231821ABF7A9AEB674517339@EMBX01-WF.jnpr.net>
From: <lionel.morand@orange-ftgroup.com>
To: <shanna@juniper.net>, <carlberg@g11.org.uk>
X-OriginalArrivalTime: 26 Jul 2011 18:26:10.0449 (UTC) FILETIME=[7E2C1010:01CC4BC1]
X-Mailman-Approved-At: Wed, 27 Jul 2011 08:53:48 -0700
Cc: draft-ietf-dime-priority-avps.all@tools.ietf.org, ietf@ietf.org, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 18:26:12 -0000

Hi Stephen,

The example given below illustrates also what I'm thinking. And please =
forgive me if I miss something below.

IMHO, what you are saying about the SIP-Resource-Priority is true for =
any other QoS parameters carried over the Diameter QoS application. It =
is therefore why I'm assuming that the security considerations =
(http://tools.ietf.org/html/rfc5866#section-11) provided in the RFC 5866 =
is valid for any QoS related AVP, including the new set of AVPs defined =
in this document.

Would it make sense to refer to this section (instead of a copy/paste)? =
Would it solve the current issue?

Regards,

Lionel

-----Message d'origine-----
De=A0: Stephen Hanna [mailto:shanna@juniper.net]=20
Envoy=E9=A0: mardi 26 juillet 2011 17:34
=C0=A0: carlberg@g11.org.uk
Cc=A0: ietf@ietf.org; secdir@ietf.org; =
draft-ietf-dime-priority-avps.all@tools.ietf.org; MORAND Lionel =
RD-CORE-ISS
Objet=A0: RE: secdir review of draft-ietf-dime-priority-avps-04

Every RFC author has an obligation to explain in the Security =
Considerations
section what security issues are likely to arise when this specification =
is
used and how those issues may be addressed. You can refer to other RFCs =
if
you like but you cannot ignore the issues or just give a hand wave.

Let me give a specific example. If a user is able to ensure that their =
phone
calls always get the highest SIP-Resource-Priority, their calls will =
always
go through, even during a disaster. This will benefit the user so they =
have
an incentive to do it. However, it may damage the collective if calls =
from
emergency responders are overridden. For this reason, protection against
active MITM attacks SHOULD be employed when using Priority AVPs.

If you can find an extant RFC that covers the relevant Security =
Considerations
for your document, you can point to it and say that readers should =
review it
because the security considerations for this draft are contained there. =
But
you must perform a serious security analysis for your document if you =
want
it to be accepted as an RFC. If the answer is that there are no security
considerations, that's fine. You can say that. But in this case, that's
clearly not the case.

You raised the concern that documents may need to highlight security =
issues
with underlying protocols upon which they depend. That is true. If =
you're
depending on a protocol that has a serious security problem that's =
relevant
to your document, you should explain that problem or point to a document
that does so. If the problem is not relevant to your document, no =
problem.
One need not consider every possible security issue, just the ones that
are most relevant to your document. In your case, there are real =
security
issues particular to conveying priority AVPs over Diameter. You should
explain what those considerations are or point to documents that do so.
As for MIBs, take a look at some recent ones and you will see that they
do contain good Security Considerations sections. For example, see
RFC 5834 and RFC 6240.

If you'd like to learn more about how to write a good Security
Considerations section, read RFC 3552. Or ask a security expert
to help you. If you can't be bothered to think about security,
you might as well withdraw your draft from consideration.

Thanks,

Steve

> -----Original Message-----
> From: carlberg@g11.org.uk [mailto:carlberg@g11.org.uk]
> Sent: Tuesday, July 26, 2011 7:24 AM
> To: Stephen Hanna
> Cc: ietf@ietf.org; secdir@ietf.org; draft-ietf-dime-priority-
> avps.all@tools.ietf.org; lionel.morand@orange-ftgroup.com
> Subject: RE: secdir review of draft-ietf-dime-priority-avps-04
>=20
> Steve,
>=20
>=20
> Quoting Stephen Hanna <shanna@juniper.net>:
>=20
> > Thanks for your response, Ken.
> >
> > Removing the last sentence that you quoted would make things worse.
> > Readers of this draft should definitely familiarize themselves with
> > the security considerations related to priority. We should make that
> > easier, not harder. The fact that those considerations also apply to
> > other RFCs does not remove the fact that they apply to this one =
also.
>=20
> but those considerations do not directly apply to DIAMETER.
>=20
> > You cannot publish a document whose security considerations section
> > says (as this one effectively does today), "There are lots of
> security
> > considerations related to this document. To understand them, please
> > dig through all the referenced documents and figure it out =
yourself."
> > Doing that digging and analysis is the job of the document editors.
>=20
> agreed, speaking in the general sense.  But again, the security
> considerations of these other protocols do not apply to the operation
> of Diameter.
>=20
> > In order to ease the burden on you, I think a reasonable compromise
> > would be for YOU to review the documents referenced and decide which
> > have the most relevant security considerations. Then you could list
> > those explicitly in the last paragraph of the Security
> Considerations.
>=20
> I'm concerned about the implications of your recommendation.  If we
> extend this position to other work in the IETF, then efforts like
> defining MIBs would mean that each MIB draft would need to perform a
> security considerations analysis of each protocol that an objects
> refers to in the context of SNMP.  And one can extend the argument
> that each protocol operating on top of TCP (and/or UDP) and IP would
> need to perform an analysis on how TCP/UDP and IP may affect the upper
> layer protocol.  We don't do that today.
>=20
> cheers,
>=20
> -ken
>=20


From w@1wt.eu  Tue Jul 26 12:29:04 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB07411E8086; Tue, 26 Jul 2011 12:29:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.024
X-Spam-Level: 
X-Spam-Status: No, score=-4.024 tagged_above=-999 required=5 tests=[AWL=-2.881, BAYES_00=-2.599, HELO_IS_SMALL6=0.556, J_CHICKENPOX_24=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m5FdTmZE2O6w; Tue, 26 Jul 2011 12:29:04 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id CF22A11E8073; Tue, 26 Jul 2011 12:29:02 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6QJSoxB003845; Tue, 26 Jul 2011 21:28:50 +0200
Date: Tue, 26 Jul 2011 21:28:50 +0200
From: Willy Tarreau <w@1wt.eu>
To: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110726192850.GB3692@1wt.eu>
References: <9031.1311286867.939466@puncture> <4E28BA9D.6010501@callenish.com> <CAP992=GedTEfimykCWwdwm=BsZdwFRJO36EO0a_o7iejURJ+tQ@mail.gmail.com> <CALiegfnwNyYDy=SyrqHJXV0ZreADb7F8QySvgdHofW9Hm9miZQ@mail.gmail.com> <CABLsOLCgxDNDs54GUybBzmG8a6rNPzXzFcwf_OU25j5L+AobaQ@mail.gmail.com> <CALiegfnp+kNqnU-_x2ZBZnN8fzP=4+6WO=QPjw1rJzvZmSXEAg@mail.gmail.com> <20110724185949.GB22405@1wt.eu> <9031.1311538720.416128@puncture> <20110724204236.GG22405@1wt.eu> <CALiegfkgukeaiMR-Yc15qUJYCB-KPcoNoX4G6NrN4+DOiDS+tw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CALiegfkgukeaiMR-Yc15qUJYCB-KPcoNoX4G6NrN4+DOiDS+tw@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Wed, 27 Jul 2011 08:53:48 -0700
Cc: Server-Initiated HTTP <hybi@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, 26 Jul 2011 19:29:04 -0000

Hi Iñaki,

On Tue, Jul 26, 2011 at 11:58:41AM +0200, Iñaki Baz Castillo wrote:
> 2011/7/24 Willy Tarreau <w@1wt.eu>:
> > To ensure nobody gets me wrong, I'm certain this can help solve issues
> > *if this is optional*. If it becomes a MUST, then the negative effects
> > will override the positive ones. In my opinion, the client should decide
> > whether to enable it or not.
> 
> But I don't understand how a client is supposed to decide by himself
> how to resolve a URI destination.

This is well explained in RFC3986, #3.2.2. It enumerates a number of
exiting name registration methods and makes it clear that DNS usage is
not mandatory at all, only suggested. Also, it only exposes the fact that
names are resolved to addresses. It obviously does not make any asumption
on the DNS records to use for this either.

> If I give you my vcard containing my
> SIP/XMPP/MAILTO URIs, I must expect that you would use *standarized*
> mechanisms to locate the server for each service. In fact, in all
> these cases (SIP, XMPP; MAILTO) the URI domain can point to several
> IP:port (due to NAPTR / SRV / MX DNS records).

I'd say that the common practice with DNS has always been to use A records
for IPv4, AAAA for IPv6 (or CNAME for any), unless explicitly stated
otherwise for the protocol's usage. Now you could have resolver libraries
which would try SRV before trying A/AAAA and this would be transparent to
the upper application layers.

> BTW: I know that any web browser would first lookup at the /etc/hosts
> file when an URI is introduced.

I'm not a browser developer, but I think they might even simply rely on
the system's resolver. For instance, you might have an /etc/nsswitch.conf
or /etc/hosts.conf which indicates the priorities for the resolvers.

> This would "replace" a DNS A/AAAA
> query. Maybe NIS or whatever could also be used for this. It does not
> break SIP/XMPP/MAILTO URI's resolutions: Initially NAPTR / SRV / MX
> query would be performed and, if there is no such record (or there is
> so we get hostnames for which DNS A must be performed) then the client
> can check /etc/hosts for the "A" resolution (domain -> IP).

I don't know where you want to go with that example, but as I explained
it, if you want to have any chance of making SRV *usable* with WS (or
HTTP), you have to motivate both sides by showing them that :
  - it's better for them to use it than not to use it (both servers and
    browsers)
  - the additional cost of using it is negligible
  - there are no issues with not using it
  - leaving the choices to the intermediaries will not cause disruptions

I'm pretty sure that can be done, but clearly not the way it's been
presented till now.

Willy


From wwwrun@ietfa.amsl.com  Tue Jul 26 20:35:31 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 E266621F858C; Tue, 26 Jul 2011 20:35:31 -0700 (PDT)
From: NomCom Chair <nomcom-chair@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: Nomcom 2011-2012: Final list of Nomcom members 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110727033531.E266621F858C@ietfa.amsl.com>
Date: Tue, 26 Jul 2011 20:35:31 -0700 (PDT)
X-Mailman-Approved-At: Wed, 27 Jul 2011 08:53:48 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 03:35:32 -0000

Hi Folks,

All of the Voting Members chosen by the random selection have been
contacted and have confirmed their willingness and ability to serve on the
2011-2012 Nomcom.  There have been no challenges to the selection of the
voting Members of this Nomcom and the challenge deadline has now passed.

As a result, it is my pleasure to announce the full composition of the
2011-2012 Nomcom as follows:

Nomcom Chair:
Suresh Krishnan

Nomcom Advisor (past year chair):
Tom Walsh

IAB Liaison:
Dave Thaler

IAOC Liaison:
Dave Crocker

IESG Liaison:
Ralph Droms

ISOC Liaison:
TBA

Tools Advisor:
Henrik Levkowetz

Voting members:
Jaap Akkerhuis, NLnet labs;
Stephen Hanna, Juniper Networks;
Sheng Jiang, Huawei Technologies Co. Ltd.;
Dapeng Liu, China Mobile;
Rifaat Shekh-Yusef, Avaya;
Pascal Thubert, Cisco;
Olivier Vautrin, Juniper Networks;
Simo Veikkolainen, Nokia;
IJsbrand Wijnands, Cisco;
Lianshu Zheng, Huawei Technologies;

I appreciate everyone that volunteered and look forward to receiving
input from the community. I will open the call for nominations soon after
IETF81 and I will post a detailed timeline soon.

Suresh Krishnan
Chair, Nomcom 2011-2012
nomcom-chair@ietf.org
suresh.krishnan@ericsson.com


From w@1wt.eu  Tue Jul 26 22:25:58 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 719C821F874B; Tue, 26 Jul 2011 22:25:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.434
X-Spam-Level: 
X-Spam-Status: No, score=-4.434 tagged_above=-999 required=5 tests=[AWL=-2.391, BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zV5JcuoZH8Lh; Tue, 26 Jul 2011 22:25:58 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id B23A621F874A; Tue, 26 Jul 2011 22:25:57 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6R5Pndo005774; Wed, 27 Jul 2011 07:25:49 +0200
Date: Wed, 27 Jul 2011 07:25:49 +0200
From: Willy Tarreau <w@1wt.eu>
To: Mark Andrews <marka@isc.org>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110727052549.GB4086@1wt.eu>
References: <CALiegf=4K2oWfmZjGMD7J_jyaDtS3i+Mu7R0Wh75Rr+MrQCjtw@mail.gmail.com> <20110722054345.GE18126@1wt.eu> <CALiegfnYm6g63JDHLiSH__r-or3kzK0XCVa3cC7RMP14KWBOSg@mail.gmail.com> <20110724120751.GQ22405@1wt.eu> <CALiegfncavmoMp4YDCeeJ3rsOfHAYQ99itKX2Q2eHB351T3X5A@mail.gmail.com> <20110724184537.GZ22405@1wt.eu> <CALiegfne620wuDMAp235n3mVcXTAnbhhNm8vpiNCy5F7+VD92A@mail.gmail.com> <20110724192948.GD22405@1wt.eu> <CALiegf=e48kkF+Gky1mY7LippUB-0kZDgSGZrJxk1aZupAGkYw@mail.gmail.com> <20110727012806.EBB811231907@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110727012806.EBB811231907@drugs.dv.isc.org>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Wed, 27 Jul 2011 08:53:48 -0700
Cc: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>, Server-Initiated HTTP <hybi@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, 27 Jul 2011 05:25:58 -0000

On Wed, Jul 27, 2011 at 11:28:06AM +1000, Mark Andrews wrote:
> > SRV provides load-balancing and failover. I never said that SRV is a
> > solution for temporaly put in maintenance a server.
> 
> Happy eyeballs however does allow you to take a server out of production
> and not really notice it.  Note webbrowsers have had the ability to do
> this for as long as webbrowsers have existed.

Mark, could you elaborate on this point ? Surely you're not talking about
the fact that a browser retries a failed connection, but I'm not not sure
what mechanism you're talking about.

> Billions of dollars have been wasted globally for the sake of a few hours
> work by webbrowser vendors.

This analysis seems a bit simplified in my opinion. Nothing is completely
white or black.

Regards,
Willy


From tore.anderson@redpill-linpro.com  Tue Jul 26 23:10:53 2011
Return-Path: <tore.anderson@redpill-linpro.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A235821F8B25 for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 23:10:53 -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 AS9KLnrRE3RC for <ietf@ietfa.amsl.com>; Tue, 26 Jul 2011 23:10:53 -0700 (PDT)
Received: from mailhub.linpro.no (mailhub.linpro.no [87.238.49.141]) by ietfa.amsl.com (Postfix) with ESMTP id B20D621F84E8 for <ietf@ietf.org>; Tue, 26 Jul 2011 23:10:52 -0700 (PDT)
Received: from localhost (mailhub.linpro.no [87.238.49.141]) by mailhub.linpro.no (Postfix) with ESMTP id 63DCFC4040; Wed, 27 Jul 2011 08:10:51 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at linpro.no
Received: from mailhub.linpro.no ([87.238.49.141]) by localhost (mailhub.linpro.no [87.238.49.141]) (amavisd-new, port 10024) with ESMTP id cNqw-rkFj21i; Wed, 27 Jul 2011 08:10:51 +0200 (CEST)
Received: from zimbra.redpill-linpro.com (claudius.linpro.no [87.238.49.234]) by mailhub.linpro.no (Postfix) with ESMTP; Wed, 27 Jul 2011 08:10:51 +0200 (CEST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.redpill-linpro.com (Postfix) with ESMTP id 3E401103800D; Wed, 27 Jul 2011 08:10:51 +0200 (CEST)
X-Virus-Scanned: amavisd-new at claudius.linpro.no
Received: from zimbra.redpill-linpro.com ([127.0.0.1]) by localhost (zimbra.redpill-linpro.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ux1ivxnZhydb; Wed, 27 Jul 2011 08:10:50 +0200 (CEST)
Received: from echo.linpro.no (v6rprx1-osl2.i.bitbit.net [10.20.126.4]) by zimbra.redpill-linpro.com (Postfix) with ESMTPSA id 9C053103800A; Wed, 27 Jul 2011 08:10:50 +0200 (CEST)
Message-ID: <4E2FABEA.2030905@redpill-linpro.com>
Date: Wed, 27 Jul 2011 08:10:50 +0200
From: Tore Anderson <tore.anderson@redpill-linpro.com>
Organization: Redpill Linpro AS
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20110707 Thunderbird/5.0
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 27 Jul 2011 08:53:48 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 06:10:53 -0000

* Ronald Bonica

> After some discussion, the IESG is attempting to determine whether there is IETF consensus to do the following:
> 
> - add a new section to draft-ietf-v6ops-6to4-to-historic
> - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL
> 
> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 and convert their status to HISTORIC. It will also contain a new section describing what it means for RFCs 3056 and 3068 to be classified as HISTORIC. The new section will say that:
> 
> - 6-to-4 should not be configured by default on any implementation (hosts, cpe routers, other)
> - vendors will decide whether/when 6-to-4 will be removed from implementations. Likewise, operators will decide whether/when 6-to-4 relays will be removed from their networks. The status of RFCs 3056 and 3068 should not be interpreted as a recommendation to remove 6-to-4 at any particular time.
> 
> 
> draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While it clarifies the meaning of "HISTORIC" in this particular case, it does not set a precedent for any future case.

I support this approach.

Best regards,
-- 
Tore Anderson
Redpill Linpro AS - http://www.redpill-linpro.com

From pch-b2B3A6689@u-1.phicoh.com  Wed Jul 27 01:33:00 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 E808E21F8BEA; Wed, 27 Jul 2011 01:33:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.549
X-Spam-Level: 
X-Spam-Status: No, score=-4.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BGCnmAR0mZrV; Wed, 27 Jul 2011 01:33:00 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo-6to4.hq.phicoh.net [IPv6:2002:8225:f03:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id 8368321F8BE9; Wed, 27 Jul 2011 01:32:51 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #66) id m1QlzXt-0001gSC; Wed, 27 Jul 2011 10:32:49 +0200
Message-Id: <m1QlzXt-0001gSC@stereo.hq.phicoh.net>
To: Mark Andrews <marka@isc.org>
Subject: Re: [v6ops] 6to4v2 (as in ripv2)? 
From: Philip Homburg <pch-v6ops@u-1.phicoh.com>
Sender: pch-b2B3A6689@u-1.phicoh.com
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> 
In-reply-to: Your message of "Wed, 27 Jul 2011 12:38:33 +1000 ." <20110727023833.5C72D1232958@drugs.dv.isc.org> 
Date: Wed, 27 Jul 2011 10:32:19 +0200
X-Mailman-Approved-At: Wed, 27 Jul 2011 08:53:48 -0700
Cc: IPv6 Operations <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, 27 Jul 2011 08:33:01 -0000

In your letter dated Wed, 27 Jul 2011 12:38:33 +1000 you wrote:
>In message <4E2F4491.30102@gmail.com>, Brian E Carpenter writes:
>> Of course, if implementors choose to drop the code you might not be
>> able to upgrade software versions - but hopefully by that time you
>> will have native IPv6 service anyway.
>
>Which is exactly why HISTORIC is NOT appropriate. 

With rfc3484-revise and the documented brokenness of 6to4, it doesn't make
any sense for implementors to offer 6to4 anyhow. So I think it would be
quite weird to keep 6to4 at standards track just to prevent some vendors from
dropping 6to4 support. 


From ibc@aliax.net  Wed Jul 27 02:44:00 2011
Return-Path: <ibc@aliax.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B3A321F8BD4; Wed, 27 Jul 2011 02:44:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.646
X-Spam-Level: 
X-Spam-Status: No, score=-2.646 tagged_above=-999 required=5 tests=[AWL=0.031,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 ZideCnpXNrcZ; Wed, 27 Jul 2011 02:43:59 -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 76BC121F8BC3; Wed, 27 Jul 2011 02:43:59 -0700 (PDT)
Received: by qwc23 with SMTP id 23so936158qwc.31 for <multiple recipients>; Wed, 27 Jul 2011 02:43:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.251.6 with SMTP id mq6mr4994651qcb.291.1311759838852; Wed, 27 Jul 2011 02:43:58 -0700 (PDT)
Received: by 10.229.224.212 with HTTP; Wed, 27 Jul 2011 02:43:58 -0700 (PDT)
In-Reply-To: <20110726192850.GB3692@1wt.eu>
References: <9031.1311286867.939466@puncture> <4E28BA9D.6010501@callenish.com> <CAP992=GedTEfimykCWwdwm=BsZdwFRJO36EO0a_o7iejURJ+tQ@mail.gmail.com> <CALiegfnwNyYDy=SyrqHJXV0ZreADb7F8QySvgdHofW9Hm9miZQ@mail.gmail.com> <CABLsOLCgxDNDs54GUybBzmG8a6rNPzXzFcwf_OU25j5L+AobaQ@mail.gmail.com> <CALiegfnp+kNqnU-_x2ZBZnN8fzP=4+6WO=QPjw1rJzvZmSXEAg@mail.gmail.com> <20110724185949.GB22405@1wt.eu> <9031.1311538720.416128@puncture> <20110724204236.GG22405@1wt.eu> <CALiegfkgukeaiMR-Yc15qUJYCB-KPcoNoX4G6NrN4+DOiDS+tw@mail.gmail.com> <20110726192850.GB3692@1wt.eu>
Date: Wed, 27 Jul 2011 11:43:58 +0200
Message-ID: <CALiegfndubt3xgRLFWUikhizsvX60p4+b0DcouX0_m5B8vestg@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Willy Tarreau <w@1wt.eu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Wed, 27 Jul 2011 08:53:46 -0700
Cc: Server-Initiated HTTP <hybi@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, 27 Jul 2011 09:44:00 -0000

2011/7/26 Willy Tarreau <w@1wt.eu>:
> if you want to have any chance of making SRV *usable* with WS (or
> HTTP), you have to motivate both sides by showing them that :
> =C2=A0- it's better for them to use it than not to use it (both servers a=
nd
> =C2=A0 =C2=A0browsers)
> =C2=A0- the additional cost of using it is negligible
> =C2=A0- there are no issues with not using it

These are godd points, but I never wanted to propose SRV for HTTP as I
consider it's just unfeasible at this time (take into account the
ammount of HTTP clients in the world, as browsers, libraries in any
language and so on).


> =C2=A0- leaving the choices to the intermediaries will not cause disrupti=
ons

This last point is hard to accomplish (I'm just talking about SRV for
WS, not for HTTP) because HTTP proxies should be capable of
determining that a GET request is in fact a WS handshake, and *just*
in that case perform SRV procedures over the domain (assuming that
there won't be SRV in the old, anti-fashion and technologically
limited HTTP world).


> I'm pretty sure that can be done, but clearly not the way it's been
> presented till now.

If the requeriment for including SRV in WS is also including it in
HTTP then I surrender. I don't think it will never happen, neither I'm
an expert in HTTP for such kind of proposal.


Thanks a lot.

--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From w@1wt.eu  Wed Jul 27 03:18:06 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C529E21F8B43; Wed, 27 Jul 2011 03:18:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.252
X-Spam-Level: 
X-Spam-Status: No, score=-4.252 tagged_above=-999 required=5 tests=[AWL=-2.509, BAYES_00=-2.599, HELO_IS_SMALL6=0.556, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vuwXgQhv+MpC; Wed, 27 Jul 2011 03:18:06 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id D9F9221F8B36; Wed, 27 Jul 2011 03:18:05 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6RAHvS1006611; Wed, 27 Jul 2011 12:17:57 +0200
Date: Wed, 27 Jul 2011 12:17:57 +0200
From: Willy Tarreau <w@1wt.eu>
To: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110727101757.GA6586@1wt.eu>
References: <CAP992=GedTEfimykCWwdwm=BsZdwFRJO36EO0a_o7iejURJ+tQ@mail.gmail.com> <CALiegfnwNyYDy=SyrqHJXV0ZreADb7F8QySvgdHofW9Hm9miZQ@mail.gmail.com> <CABLsOLCgxDNDs54GUybBzmG8a6rNPzXzFcwf_OU25j5L+AobaQ@mail.gmail.com> <CALiegfnp+kNqnU-_x2ZBZnN8fzP=4+6WO=QPjw1rJzvZmSXEAg@mail.gmail.com> <20110724185949.GB22405@1wt.eu> <9031.1311538720.416128@puncture> <20110724204236.GG22405@1wt.eu> <CALiegfkgukeaiMR-Yc15qUJYCB-KPcoNoX4G6NrN4+DOiDS+tw@mail.gmail.com> <20110726192850.GB3692@1wt.eu> <CALiegfndubt3xgRLFWUikhizsvX60p4+b0DcouX0_m5B8vestg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CALiegfndubt3xgRLFWUikhizsvX60p4+b0DcouX0_m5B8vestg@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Wed, 27 Jul 2011 08:53:48 -0700
Cc: Server-Initiated HTTP <hybi@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, 27 Jul 2011 10:18:06 -0000

On Wed, Jul 27, 2011 at 11:43:58AM +0200, Iñaki Baz Castillo wrote:
> 2011/7/26 Willy Tarreau <w@1wt.eu>:
> > if you want to have any chance of making SRV *usable* with WS (or
> > HTTP), you have to motivate both sides by showing them that :
> >  - it's better for them to use it than not to use it (both servers and
> >    browsers)
> >  - the additional cost of using it is negligible
> >  - there are no issues with not using it
> 
> These are godd points, but I never wanted to propose SRV for HTTP as I
> consider it's just unfeasible at this time (take into account the
> ammount of HTTP clients in the world, as browsers, libraries in any
> language and so on).

That's where I think you're mistaken. As long as you think of it as mandatory
this will not be possible. When you think of it as optional and with an added
value, then you will progressively see clients adopt it and make use of it.
Since the beginning, you're proposing the option as mandatory "just because"
and not for a perceivable added value by both sides. The downsides then
outweigh the benefits. But maybe the benefits do not really exist after all,
otherwise a valid attractive proposal would already have been made by the
time we spent discussing it.

> >  - leaving the choices to the intermediaries will not cause disruptions
> 
> This last point is hard to accomplish (I'm just talking about SRV for
> WS, not for HTTP) because HTTP proxies should be capable of
> determining that a GET request is in fact a WS handshake, and *just*
> in that case perform SRV procedures over the domain (assuming that
> there won't be SRV in the old, anti-fashion and technologically
> limited HTTP world).

Once again, if you expect *all* HTTP proxies to be able to do that, your
proposal fails. If you expect that at least *some* HTTP proxies will be
able to do that with a benefit, then something is possible. Let me repeat
it, technologies are adopted, not forced on users.

> > I'm pretty sure that can be done, but clearly not the way it's been
> > presented till now.
> 
> If the requeriment for including SRV in WS is also including it in
> HTTP then I surrender. I don't think it will never happen, neither I'm
> an expert in HTTP for such kind of proposal.

Probably that starting by enumerating in a draft the benefits it could bring
would be a good start. You seem to be very well convinced that there are
benefits, so you're probably one of the few persons able to start such a
draft.

Regards,
Willy


From ibc@aliax.net  Wed Jul 27 03:46:30 2011
Return-Path: <ibc@aliax.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 318B521F8B11; Wed, 27 Jul 2011 03:46:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.647
X-Spam-Level: 
X-Spam-Status: No, score=-2.647 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 1+6qokdm2qMO; Wed, 27 Jul 2011 03:46:29 -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 31BDB21F8B10; Wed, 27 Jul 2011 03:46:29 -0700 (PDT)
Received: by qwc23 with SMTP id 23so968325qwc.31 for <multiple recipients>; Wed, 27 Jul 2011 03:46:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.1.8 with SMTP id 8mr4190185qcd.215.1311763588455; Wed, 27 Jul 2011 03:46:28 -0700 (PDT)
Received: by 10.229.224.212 with HTTP; Wed, 27 Jul 2011 03:46:28 -0700 (PDT)
In-Reply-To: <20110727101757.GA6586@1wt.eu>
References: <CAP992=GedTEfimykCWwdwm=BsZdwFRJO36EO0a_o7iejURJ+tQ@mail.gmail.com> <CALiegfnwNyYDy=SyrqHJXV0ZreADb7F8QySvgdHofW9Hm9miZQ@mail.gmail.com> <CABLsOLCgxDNDs54GUybBzmG8a6rNPzXzFcwf_OU25j5L+AobaQ@mail.gmail.com> <CALiegfnp+kNqnU-_x2ZBZnN8fzP=4+6WO=QPjw1rJzvZmSXEAg@mail.gmail.com> <20110724185949.GB22405@1wt.eu> <9031.1311538720.416128@puncture> <20110724204236.GG22405@1wt.eu> <CALiegfkgukeaiMR-Yc15qUJYCB-KPcoNoX4G6NrN4+DOiDS+tw@mail.gmail.com> <20110726192850.GB3692@1wt.eu> <CALiegfndubt3xgRLFWUikhizsvX60p4+b0DcouX0_m5B8vestg@mail.gmail.com> <20110727101757.GA6586@1wt.eu>
Date: Wed, 27 Jul 2011 12:46:28 +0200
Message-ID: <CALiegfmMO2Es6P=qy4m=XULVQE9bDp7S0LYXG_9n4Lk9yirGXQ@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Willy Tarreau <w@1wt.eu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Wed, 27 Jul 2011 08:53:48 -0700
Cc: Server-Initiated HTTP <hybi@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, 27 Jul 2011 10:46:30 -0000

2011/7/27 Willy Tarreau <w@1wt.eu>:
> That's where I think you're mistaken. As long as you think of it as manda=
tory
> this will not be possible.

Hi Willy, as I've explained several times in these threads, if a WS
client is not mandated to perform SRV given a WS URI domain, then the
service provider cannot rely on SRV records. This is, let's assume
that a WS service provider offers a WS URI like "ws://mydomain.org",
with these records (simplifying):

- SRV:   1.1.1.1:80, 1.1.1.2:80, 1.1.1.3:90
- A:        1.1.1.1

So assuming that SRV is optional for clients, the provider does not
know how many clients would use SRV or just A. Imagine the service
provider expects millons of concurrent users. He must be ready to
receive all those users in 1.1.1.1 (if they don't use SRV). So the
service provider must build a complex/expensive balancer system in
server side (BGP and all that stuf) just for the case in which most of
the clients would not perform SRV procedures. So 1.1.1.1 would be in
fact a balancer with N hosts providing the WS service behind it.

At the same time, if clients use SRV then load-balancing and failover
would be automatically provided by the SRV capabilities. No need for
like-BGS solutions in server side.

So the question is: which service provider would spend resources, time
and efforts building two different load-balancing/failover systems?.
If a provider can build the "BGP" solution then it will not need SRV.
And another provider which cannot build a "BGP" solution could not
entirely rely on SRV capabilities as maybe most of the clients would
not use it.

In the other side, if service providers must be ready to accept all
the traffic in the IP resolved via single DNS A query, then nobody
would need SRV and webbrowsers would just remove it (the Mozilla
developer has already said in these threads that he won't implement it
"due to latency reasons").

Also the fact that DNS is not mandated by HTTP neither WS makes things
even worse. In contrast, in XMPP and SIP protocols DNS is mandatory
and also SRV procedures. If you are a SIP provider hosting the service
with domain "mydomain.org" you don't ever need to have a working A
record for mydomain.org, but just SRV (and optionally NAPTR). Or you
could just have A record and not use SRV at all. SIP client procedures
for locating servers (RFC 3263) mandate first trying SRV and then
A/AAAA, so things would work in any case.

So correct me if I'm wrong, but making SRV optional for clients (in
*any* protocol) is not something I consider feasible or useful.

Regards.


--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From mark@townsley.net  Wed Jul 27 04:32:02 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 38B8421F8AF1; Wed, 27 Jul 2011 04:32:02 -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 6643XnFsS5W8; Wed, 27 Jul 2011 04:32:01 -0700 (PDT)
Received: from mail-pz0-f53.google.com (mail-pz0-f53.google.com [209.85.210.53]) by ietfa.amsl.com (Postfix) with ESMTP id 9DEBD21F8ACE; Wed, 27 Jul 2011 04:32:01 -0700 (PDT)
Received: by pzk6 with SMTP id 6so2407487pzk.26 for <multiple recipients>; Wed, 27 Jul 2011 04:32:01 -0700 (PDT)
Received: by 10.68.50.67 with SMTP id a3mr12552750pbo.377.1311766321071; Wed, 27 Jul 2011 04:32:01 -0700 (PDT)
Received: from [10.255.254.113] (rtp-isp-nat1.cisco.com [64.102.254.33]) by mx.google.com with ESMTPS id 9sm12505pbx.82.2011.07.27.04.31.54 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 27 Jul 2011 04:31:59 -0700 (PDT)
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com>
Date: Wed, 27 Jul 2011 07:31:51 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <39EEA819-6D8D-4FE7-958D-D7DCEDF893C1@townsley.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com>	<4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com>
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Wed, 27 Jul 2011 08:53:48 -0700
Cc: ietf@ietf.org, IPv6 Operations <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, 27 Jul 2011 11:32:02 -0000

On Jul 27, 2011, at 7:09 AM, Fred Baker wrote:

>=20
> On Jul 26, 2011, at 6:49 PM, Brian E Carpenter wrote:
>=20
>> Since 6to4 is a transition mechanism it has no long term future *by =
definition*. Even if someone chooses to design a v2, who is going to =
implement it?
>=20
> Actually, I think one could argue pretty effectively that 6rd is =
6to4-bis.=20

+1

- Mark

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


From w@1wt.eu  Wed Jul 27 05:45:53 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF9C921F84F1; Wed, 27 Jul 2011 05:45:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[AWL=-2.476, BAYES_00=-2.599, HELO_IS_SMALL6=0.556, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aBNzcz2f6qyV; Wed, 27 Jul 2011 05:45:53 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id EE1A721F84EB; Wed, 27 Jul 2011 05:45:52 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6RCjj97006977; Wed, 27 Jul 2011 14:45:45 +0200
Date: Wed, 27 Jul 2011 14:45:45 +0200
From: Willy Tarreau <w@1wt.eu>
To: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110727124545.GA6931@1wt.eu>
References: <CABLsOLCgxDNDs54GUybBzmG8a6rNPzXzFcwf_OU25j5L+AobaQ@mail.gmail.com> <CALiegfnp+kNqnU-_x2ZBZnN8fzP=4+6WO=QPjw1rJzvZmSXEAg@mail.gmail.com> <20110724185949.GB22405@1wt.eu> <9031.1311538720.416128@puncture> <20110724204236.GG22405@1wt.eu> <CALiegfkgukeaiMR-Yc15qUJYCB-KPcoNoX4G6NrN4+DOiDS+tw@mail.gmail.com> <20110726192850.GB3692@1wt.eu> <CALiegfndubt3xgRLFWUikhizsvX60p4+b0DcouX0_m5B8vestg@mail.gmail.com> <20110727101757.GA6586@1wt.eu> <CALiegfmMO2Es6P=qy4m=XULVQE9bDp7S0LYXG_9n4Lk9yirGXQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CALiegfmMO2Es6P=qy4m=XULVQE9bDp7S0LYXG_9n4Lk9yirGXQ@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Wed, 27 Jul 2011 08:53:48 -0700
Cc: Server-Initiated HTTP <hybi@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, 27 Jul 2011 12:45:54 -0000

On Wed, Jul 27, 2011 at 12:46:28PM +0200, Iñaki Baz Castillo wrote:
> Hi Willy, as I've explained several times in these threads, if a WS
> client is not mandated to perform SRV given a WS URI domain, then the
> service provider cannot rely on SRV records. This is, let's assume
> that a WS service provider offers a WS URI like "ws://mydomain.org",
> with these records (simplifying):
> 
> - SRV:   1.1.1.1:80, 1.1.1.2:80, 1.1.1.3:90
> - A:        1.1.1.1

No, he would have :

 - SRV:   1.1.1.1:80, 1.1.1.2:80, 1.1.1.3:90
 - A:     1.1.1.1, 1.1.1.2, 1.1.1.3

> So assuming that SRV is optional for clients, the provider does not
> know how many clients would use SRV or just A.

That's mainly the point : the provider would offer a service which is
designed to work both ways and which a part of the users would experience
better due to their consideration of the SRV record.

> Imagine the service
> provider expects millons of concurrent users. He must be ready to
> receive all those users in 1.1.1.1 (if they don't use SRV). So the
> service provider must build a complex/expensive balancer system in
> server side (BGP and all that stuf) just for the case in which most of
> the clients would not perform SRV procedures. So 1.1.1.1 would be in
> fact a balancer with N hosts providing the WS service behind it.
> 
> At the same time, if clients use SRV then load-balancing and failover
> would be automatically provided by the SRV capabilities. No need for
> like-BGS solutions in server side.

Once again, the goal to make SRV adopted BY USERS is not to ensure that
it tries to cover all the server-side needs, but that it offers better
quality of service to USERS. That way USERS will massively adopt it and
server will one day be able to safely rely on it. Just like neither
Javascript nor cookies nor flash are mandatory, still all of them are
very common in practice and many service providers happily rely on them.

> So the question is: which service provider would spend resources, time
> and efforts building two different load-balancing/failover systems?.
> If a provider can build the "BGP" solution then it will not need SRV.
> And another provider which cannot build a "BGP" solution could not
> entirely rely on SRV capabilities as maybe most of the clients would
> not use it.

You can't transform the Internet in one day after publishing one draft.
Look at the Set-Cookie2 header. It was a massive failure. It was thought
that the broken Set-Cookie header could be fixed by one new RFC, and
nobody adopted it. The reason is that it was proposed as a replacement.
I think that Opera might be the only browser to parse it. In contrast,
if your proposal is backwards compatible and incites users to enable it
on their side, then in a few years it can become a de-facto standard.

> In the other side, if service providers must be ready to accept all
> the traffic in the IP resolved via single DNS A query, then nobody
> would need SRV and webbrowsers would just remove it (the Mozilla
> developer has already said in these threads that he won't implement it
> "due to latency reasons").

That's why I explained that you have to find what other benefits *for
the end user* can be brought by this. End users are deciding, not site
owners.

> Also the fact that DNS is not mandated by HTTP neither WS makes things
> even worse.

That's why SRV cannot be made mandatory.

> In contrast, in XMPP and SIP protocols DNS is mandatory
> and also SRV procedures. If you are a SIP provider hosting the service
> with domain "mydomain.org" you don't ever need to have a working A
> record for mydomain.org, but just SRV (and optionally NAPTR). Or you
> could just have A record and not use SRV at all. SIP client procedures
> for locating servers (RFC 3263) mandate first trying SRV and then
> A/AAAA, so things would work in any case.
> 
> So correct me if I'm wrong, but making SRV optional for clients (in
> *any* protocol) is not something I consider feasible or useful.

Feasible yes, useful I don't know, and I'm not the one trying to argue
that it can add value. If it can bring value to the user, some users
will enable it despite the possible added latency. If it does not
bring them anything, they won't use it.

Regards,
Willy


From john.mann@monash.edu  Wed Jul 27 06:07:55 2011
Return-Path: <john.mann@monash.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 CE4BA21F8B72; Wed, 27 Jul 2011 06:07:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.676
X-Spam-Level: 
X-Spam-Status: No, score=-5.676 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 B0Dl2u9bBDEh; Wed, 27 Jul 2011 06:07:55 -0700 (PDT)
Received: from na3sys009aog116.obsmtp.com (na3sys009aog116.obsmtp.com [74.125.149.240]) by ietfa.amsl.com (Postfix) with ESMTP id D8CA721F8B71; Wed, 27 Jul 2011 06:07:54 -0700 (PDT)
Received: from mail-vw0-f48.google.com ([209.85.212.48]) (using TLSv1) by na3sys009aob116.postini.com ([74.125.148.12]) with SMTP ID DSNKTjANqmFtk0IWhpuqU8EKGG6L+uRrv8NW@postini.com; Wed, 27 Jul 2011 06:07:55 PDT
Received: by mail-vw0-f48.google.com with SMTP id 7so1208416vws.7 for <multiple recipients>; Wed, 27 Jul 2011 06:07:54 -0700 (PDT)
Received: by 10.52.19.161 with SMTP id g1mr55012vde.11.1311772074107; Wed, 27 Jul 2011 06:07:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.108.193 with HTTP; Wed, 27 Jul 2011 06:07:34 -0700 (PDT)
In-Reply-To: <5A600744-8605-46D3-82B2-C3C30E30E4AC@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com> <5A600744-8605-46D3-82B2-C3C30E30E4AC@network-heretics.com>
From: "John Mann (ITS)" <john.mann@monash.edu>
Date: Wed, 27 Jul 2011 23:07:34 +1000
Message-ID: <CA+OBy1O1ji-ETnAa2oQ8p4OUtd7WjGScyp0xPUTFdm00iaAK=g@mail.gmail.com>
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=20cf307c9c2e80e1b804a90cbce0
X-Mailman-Approved-At: Wed, 27 Jul 2011 08:53:48 -0700
Cc: IPv6 Operations <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, 27 Jul 2011 13:07:55 -0000

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

Hi,

On 27 July 2011 22:15, Keith Moore <moore@network-heretics.com> wrote:

>
> On Jul 27, 2011, at 7:09 AM, Fred Baker wrote:
>
> >
> > On Jul 26, 2011, at 6:49 PM, Brian E Carpenter wrote:
> >
> >> Since 6to4 is a transition mechanism it has no long term future *by
> definition*. Even if someone chooses to design a v2, who is going to
> implement it?
> >
> > Actually, I think one could argue pretty effectively that 6rd is
> 6to4-bis.
>
> only if you're confused about the use cases for each.


In my opinion:

6to4 use case
- D.I.Y setup - no ISP involvement
- depend upon kindness of strangers to run the anycast relays
- some users have hard-to-solve reliability problems
- experimental / historic / not-recommended - should be off by default
- for users who would prefer "unreliable IPv6" to "no IPv6"

6rd use case
- configuration parameters set by ISP
- ISP runs the relays
- apparently production quality (see free.fr)
- for users who would prefer "no IPv6" to "unreliable Internet"

I agree that 6rd is not a replacement protocol for the 6to4 use case.

I will argue that the "6rd use case" is a replacement for the "6to4 use
case".
[ And that native dual-stack is a replacement for both. ]
We want normal users to move past "experimental IPv6" towards "production
IPv6".

Thanks,
    John

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

Hi,<br><br><div class=3D"gmail_quote">On 27 July 2011 22:15, 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 class=3D"im"><br>
On Jul 27, 2011, at 7:09 AM, Fred Baker wrote:<br>
<br>
&gt;<br>
</div><div class=3D"im">&gt; On Jul 26, 2011, at 6:49 PM, Brian E Carpenter=
 wrote:<br>
&gt;<br>
&gt;&gt; Since 6to4 is a transition mechanism it has no long term future *b=
y definition*. Even if someone chooses to design a v2, who is going to impl=
ement it?<br>
&gt;<br>
&gt; Actually, I think one could argue pretty effectively that 6rd is 6to4-=
bis.<br>
<br>
</div>only if you&#39;re confused about the use cases for each.</blockquote=
><div><br></div><div>In my opinion:</div><div><br></div><div>6to4 use case<=
/div><div>- D.I.Y setup - no ISP involvement</div><div>- depend upon kindne=
ss of strangers to run the anycast relays</div>

<div>- some users have hard-to-solve reliability problems</div><div>- exper=
imental / historic / not-recommended - should be off by default</div><div>-=
 for users who would prefer &quot;unreliable IPv6&quot; to &quot;no IPv6&qu=
ot;</div>

<div><br></div><div>6rd use case</div><div>- configuration parameters set b=
y ISP</div><div>- ISP runs the relays</div><div>- apparently production qua=
lity (see <a href=3D"http://free.fr">free.fr</a>)</div><div>- for users who=
 would prefer &quot;no IPv6&quot; to &quot;unreliable Internet&quot;</div>

<div><br></div><div>I agree that 6rd is not a replacement protocol for the =
6to4 use case.</div><div><br></div><div>I will argue that the &quot;6rd use=
 case&quot; is a replacement for the &quot;6to4 use case&quot;.</div><div>

[ And that native dual-stack is a replacement for both. ]</div><div>We want=
 normal users to move past &quot;experimental IPv6&quot; towards &quot;prod=
uction IPv6&quot;.</div><div><br></div><div>Thanks,</div><div>=A0 =A0 John<=
/div>

</div>

--20cf307c9c2e80e1b804a90cbce0--

From ibc@aliax.net  Wed Jul 27 06:45:46 2011
Return-Path: <ibc@aliax.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85FC021F8439; Wed, 27 Jul 2011 06:45:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.647
X-Spam-Level: 
X-Spam-Status: No, score=-2.647 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 8ws575zqUNon; Wed, 27 Jul 2011 06:45:46 -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 780DB21F8581; Wed, 27 Jul 2011 06:45:39 -0700 (PDT)
Received: by qyk9 with SMTP id 9so2422950qyk.10 for <multiple recipients>; Wed, 27 Jul 2011 06:45:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.78.67 with SMTP id j3mr30313qck.253.1311774338829; Wed, 27 Jul 2011 06:45:38 -0700 (PDT)
Received: by 10.229.224.212 with HTTP; Wed, 27 Jul 2011 06:45:38 -0700 (PDT)
In-Reply-To: <20110727124545.GA6931@1wt.eu>
References: <CABLsOLCgxDNDs54GUybBzmG8a6rNPzXzFcwf_OU25j5L+AobaQ@mail.gmail.com> <CALiegfnp+kNqnU-_x2ZBZnN8fzP=4+6WO=QPjw1rJzvZmSXEAg@mail.gmail.com> <20110724185949.GB22405@1wt.eu> <9031.1311538720.416128@puncture> <20110724204236.GG22405@1wt.eu> <CALiegfkgukeaiMR-Yc15qUJYCB-KPcoNoX4G6NrN4+DOiDS+tw@mail.gmail.com> <20110726192850.GB3692@1wt.eu> <CALiegfndubt3xgRLFWUikhizsvX60p4+b0DcouX0_m5B8vestg@mail.gmail.com> <20110727101757.GA6586@1wt.eu> <CALiegfmMO2Es6P=qy4m=XULVQE9bDp7S0LYXG_9n4Lk9yirGXQ@mail.gmail.com> <20110727124545.GA6931@1wt.eu>
Date: Wed, 27 Jul 2011 15:45:38 +0200
Message-ID: <CALiegf=YCCYuoVk1isPOwfB1z8mpSxbJmFHU5vEyQo7xOGH5RA@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Willy Tarreau <w@1wt.eu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Wed, 27 Jul 2011 08:53:48 -0700
Cc: Server-Initiated HTTP <hybi@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, 27 Jul 2011 13:45:46 -0000

2011/7/27 Willy Tarreau <w@1wt.eu>:
> Once again, the goal to make SRV adopted BY USERS is not to ensure that
> it tries to cover all the server-side needs, but that it offers better
> quality of service to USERS. That way USERS will massively adopt it and
> server will one day be able to safely rely on it. Just like neither
> Javascript nor cookies nor flash are mandatory, still all of them are
> very common in practice and many service providers happily rely on them.

Thanks for your useful comments (as always in these threads). Let me
just a question:

What do you mean with "USERS"? Do you mean home users in front of
their web browsers? or webbrowser vendors?
I don't think home users (neither professional users) has nothing to
decide here, they will not "resolve" the WS URI retrieved from a
webpage.
So we are talking about webbrowser vendors, right? and typically there
are no more than.... 10?

Regards.


--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From w@1wt.eu  Wed Jul 27 07:03:08 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EC3621F86C3; Wed, 27 Jul 2011 07:03:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.186
X-Spam-Level: 
X-Spam-Status: No, score=-4.186 tagged_above=-999 required=5 tests=[AWL=-2.443, BAYES_00=-2.599, HELO_IS_SMALL6=0.556, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a1Tm9iQy0g9f; Wed, 27 Jul 2011 07:03:08 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 7CD2F21F86C2; Wed, 27 Jul 2011 07:03:07 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6RE32Ou007260; Wed, 27 Jul 2011 16:03:02 +0200
Date: Wed, 27 Jul 2011 16:03:02 +0200
From: Willy Tarreau <w@1wt.eu>
To: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110727140302.GB7225@1wt.eu>
References: <20110724185949.GB22405@1wt.eu> <9031.1311538720.416128@puncture> <20110724204236.GG22405@1wt.eu> <CALiegfkgukeaiMR-Yc15qUJYCB-KPcoNoX4G6NrN4+DOiDS+tw@mail.gmail.com> <20110726192850.GB3692@1wt.eu> <CALiegfndubt3xgRLFWUikhizsvX60p4+b0DcouX0_m5B8vestg@mail.gmail.com> <20110727101757.GA6586@1wt.eu> <CALiegfmMO2Es6P=qy4m=XULVQE9bDp7S0LYXG_9n4Lk9yirGXQ@mail.gmail.com> <20110727124545.GA6931@1wt.eu> <CALiegf=YCCYuoVk1isPOwfB1z8mpSxbJmFHU5vEyQo7xOGH5RA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CALiegf=YCCYuoVk1isPOwfB1z8mpSxbJmFHU5vEyQo7xOGH5RA@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Wed, 27 Jul 2011 08:53:48 -0700
Cc: Server-Initiated HTTP <hybi@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, 27 Jul 2011 14:03:08 -0000

On Wed, Jul 27, 2011 at 03:45:38PM +0200, Iñaki Baz Castillo wrote:
> 2011/7/27 Willy Tarreau <w@1wt.eu>:
> > Once again, the goal to make SRV adopted BY USERS is not to ensure that
> > it tries to cover all the server-side needs, but that it offers better
> > quality of service to USERS. That way USERS will massively adopt it and
> > server will one day be able to safely rely on it. Just like neither
> > Javascript nor cookies nor flash are mandatory, still all of them are
> > very common in practice and many service providers happily rely on them.
> 
> Thanks for your useful comments (as always in these threads). Let me
> just a question:
> 
> What do you mean with "USERS"? Do you mean home users in front of
> their web browsers? or webbrowser vendors?

Users in front of web browsers.

> I don't think home users (neither professional users) has nothing to
> decide here, they will not "resolve" the WS URI retrieved from a
> webpage.

I think you're wrong. Those are these users which ask for feature XXX or
YYY that they like because it brings them a better experience. If you can
find a real benefit for the end user, there will be an option in the browser
and some of them will enable it. It's just important to find how an end user
may benefit from making use of SRV tags when connecting to his favorite site
instead of using just CNAME or A/AAAA. Maybe being able to always connect to
less loaded servers would be appreciated, because some site maintainers will
start announcing new servers. Maybe there are solutions to provide better
geolocation using SRV than with A (ie: let the web browser decide which field
to use instead of relying on its resolver's IP address). Maybe it will be
possible for mobile users to automatically select a different port which is
not subject to annoying transparent proxies at their provider. I don't know.
You must think in terms of better experience which might be brought via
better quality of service. Surely a DNS record might provide information to
improve QoS based on the browser's decision.

> So we are talking about webbrowser vendors, right? and typically there
> are no more than.... 10?

Browsers implement what their users ask for. They don't want to add features
that are not desired and make experience worse or reduce reliability. But if
users ask for something, they'll certainly implement it.

Regards,
Willy


From Ted.Lemon@nominum.com  Wed Jul 27 07:20:21 2011
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EF9B11E80AE; Wed, 27 Jul 2011 07:20:21 -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=[AWL=-0.000, 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 5vg1QFQDFRMz; Wed, 27 Jul 2011 07:20:20 -0700 (PDT)
Received: from exprod7og117.obsmtp.com (exprod7og117.obsmtp.com [64.18.2.6]) by ietfa.amsl.com (Postfix) with ESMTP id B422711E807A; Wed, 27 Jul 2011 07:20:19 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob117.postini.com ([64.18.6.12]) with SMTP ID DSNKTjAeohXLl8Yw2JWYFnDeV4ss8Nox9s8t@postini.com; Wed, 27 Jul 2011 07:20:19 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id E526E1B81B2; Wed, 27 Jul 2011 07:20:11 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id CA325190058; Wed, 27 Jul 2011 07:20:11 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.01.0289.001; Wed, 27 Jul 2011 07:20:11 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Mark Andrews <marka@isc.org>
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
Thread-Topic: [v6ops] 6to4v2 (as in ripv2)?
Thread-Index: AQHMS+Z/8YBivn23ZUinspFJsOVzppT/dTzEgAE45wA=
Date: Wed, 27 Jul 2011 14:20:11 +0000
Message-ID: <968F0B1C-D082-4A59-8213-FD58C74AF89D@nominum.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org>
In-Reply-To: <20110727023833.5C72D1232958@drugs.dv.isc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.129.66.66]
Content-Type: multipart/alternative; boundary="_000_968F0B1CD0824A598213FD58C74AF89Dnominumcom_"
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 27 Jul 2011 08:53:48 -0700
Cc: "<ietf@ietf.org>" <ietf@ietf.org>, IPv6 Operations <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, 27 Jul 2011 14:20:21 -0000

--_000_968F0B1CD0824A598213FD58C74AF89Dnominumcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

If you have a reason to install and enable 6to4, why would the nominal
status of a couple of RFCs make you do anything different?

This seems like an easy question to answer.   You'd implement and use 6to4v=
2 because it works better than the historic 6to4 protocol.


--_000_968F0B1CD0824A598213FD58C74AF89Dnominumcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <9F2F18C90D0CDB48A580ED2F6A936632@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">
<div>
<blockquote type=3D"cite">If you have a reason to install and enable 6to4, =
why would the nominal<br>
</blockquote>
<blockquote type=3D"cite">status of a couple of RFCs make you do anything d=
ifferent?</blockquote>
</div>
</span></blockquote>
</div>
<br>
<div>This seems like an easy question to answer. &nbsp; You'd implement and=
 use 6to4v2 because it works better than the historic 6to4 protocol.</div>
<div><br>
</div>
</body>
</html>

--_000_968F0B1CD0824A598213FD58C74AF89Dnominumcom_--

From ek@google.com  Wed Jul 27 08:12:34 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 DA44121F85EE for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 08:12:34 -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 bukx9mgsaAHZ for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 08:12:34 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by ietfa.amsl.com (Postfix) with ESMTP id 55DFC21F8556 for <ietf@ietf.org>; Wed, 27 Jul 2011 08:12:34 -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 p6RFCRlU024765 for <ietf@ietf.org>; Wed, 27 Jul 2011 08:12:27 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1311779547; bh=6yNm7yArp9ui6NA18GGCwIasXuw=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=gnjWvAt8mOihHBKcdolYL07jpG8UgeThIMGvxLyEeyuQ2i/h0qQKV74WCIPRCUsPG fxBUpMTKLxzi/G9FJN6oA==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:date: message-id:subject:from:to:cc:content-type:x-system-of-record; b=lSwTkA16yfGbgWdEOlbprJLDDX5nWNUbJisqvVQmxHrOGecflksiC5qSnXKBGJ4ec U8PYPNgKrzwl9Vkbptf2g==
Received: from qwa26 (qwa26.prod.google.com [10.241.193.26]) by wpaz13.hot.corp.google.com with ESMTP id p6RFCJqH028617 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Wed, 27 Jul 2011 08:12:26 -0700
Received: by qwa26 with SMTP id 26so1038490qwa.28 for <ietf@ietf.org>; Wed, 27 Jul 2011 08:12:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=oRl2TDL/DdkCrHjDT4uRwWLTSzAk1dsHqlFNa3ohmt8=; b=PfjyfEEaVm3jGECW1529iC4fuN/QgftR1PH2sh60tejD61VWJuXSI1wrwNmXF89kKz LJ2X2ksLBWiwIB7/vPYQ==
MIME-Version: 1.0
Received: by 10.229.217.72 with SMTP id hl8mr140836qcb.65.1311779546074; Wed, 27 Jul 2011 08:12:26 -0700 (PDT)
Received: by 10.229.136.66 with HTTP; Wed, 27 Jul 2011 08:12:25 -0700 (PDT)
In-Reply-To: <20110727150832.69F5B1235C62@drugs.dv.isc.org>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com> <39EEA819-6D8D-4FE7-958D-D7DCEDF893C1@townsley.net> <CAD6AjGTPjhD=yiv5Pe6G4TRGKnPyzn0_nMk9v8bevmGtqu2g3A@mail.gmail.com> <20110727150832.69F5B1235C62@drugs.dv.isc.org>
Date: Wed, 27 Jul 2011 15:12:25 +0000
Message-ID: <CAAedzxpipYVk-nTQmfg1ecPi-+LTOEEAc8twahDj8UG_AhvSQQ@mail.gmail.com>
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
From: Erik Kline <ek@google.com>
To: Mark Andrews <marka@isc.org>
Content-Type: text/plain; charset=UTF-8
X-System-Of-Record: true
X-Mailman-Approved-At: Wed, 27 Jul 2011 08:53:48 -0700
Cc: IPv6 Operations <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, 27 Jul 2011 15:12:35 -0000

Moving 6to4 to historic does not in any way impact your ability to use
it as you wish.

6to4 support is not part of the IPv6 node requirements, as I
understand it.  Therefore I believe that any vendor (OS, router,
otherwise) could deleted 6to4 support in any release and be in
violation of anything, regardless of historic status.

From ibc@aliax.net  Wed Jul 27 08:19:33 2011
Return-Path: <ibc@aliax.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E266A11E80D7; Wed, 27 Jul 2011 08:19:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.647
X-Spam-Level: 
X-Spam-Status: No, score=-2.647 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 Ba2qKf-4sVNz; Wed, 27 Jul 2011 08:19:33 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id 9A84811E8099; Wed, 27 Jul 2011 08:19:31 -0700 (PDT)
Received: by qyk29 with SMTP id 29so1096803qyk.10 for <multiple recipients>; Wed, 27 Jul 2011 08:19:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.78.67 with SMTP id j3mr114955qck.253.1311779970996; Wed, 27 Jul 2011 08:19:30 -0700 (PDT)
Received: by 10.229.224.212 with HTTP; Wed, 27 Jul 2011 08:19:30 -0700 (PDT)
In-Reply-To: <20110727140302.GB7225@1wt.eu>
References: <20110724185949.GB22405@1wt.eu> <9031.1311538720.416128@puncture> <20110724204236.GG22405@1wt.eu> <CALiegfkgukeaiMR-Yc15qUJYCB-KPcoNoX4G6NrN4+DOiDS+tw@mail.gmail.com> <20110726192850.GB3692@1wt.eu> <CALiegfndubt3xgRLFWUikhizsvX60p4+b0DcouX0_m5B8vestg@mail.gmail.com> <20110727101757.GA6586@1wt.eu> <CALiegfmMO2Es6P=qy4m=XULVQE9bDp7S0LYXG_9n4Lk9yirGXQ@mail.gmail.com> <20110727124545.GA6931@1wt.eu> <CALiegf=YCCYuoVk1isPOwfB1z8mpSxbJmFHU5vEyQo7xOGH5RA@mail.gmail.com> <20110727140302.GB7225@1wt.eu>
Date: Wed, 27 Jul 2011 17:19:30 +0200
Message-ID: <CALiegfmWWL2sxB=4=kD-YmE30rsS3_-DGqePCohv_hv2QQfJUw@mail.gmail.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Willy Tarreau <w@1wt.eu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Wed, 27 Jul 2011 08:53:48 -0700
Cc: Server-Initiated HTTP <hybi@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, 27 Jul 2011 15:19:34 -0000

2011/7/27 Willy Tarreau <w@1wt.eu>:
>> I don't think home users (neither professional users) has nothing to
>> decide here, they will not "resolve" the WS URI retrieved from a
>> webpage.
>
> I think you're wrong. Those are these users which ask for feature XXX or
> YYY that they like because it brings them a better experience. If you can
> find a real benefit for the end user, there will be an option in the brow=
ser
> and some of them will enable it. It's just important to find how an end u=
ser
> may benefit from making use of SRV tags when connecting to his favorite s=
ite
> instead of using just CNAME or A/AAAA. Maybe being able to always connect=
 to
> less loaded servers would be appreciated, because some site maintainers w=
ill
> start announcing new servers. Maybe there are solutions to provide better
> geolocation using SRV than with A (ie: let the web browser decide which f=
ield
> to use instead of relying on its resolver's IP address). Maybe it will be
> possible for mobile users to automatically select a different port which =
is
> not subject to annoying transparent proxies at their provider. I don't kn=
ow.
> You must think in terms of better experience which might be brought via
> better quality of service. Surely a DNS record might provide information =
to
> improve QoS based on the browser's decision.
>
>> So we are talking about webbrowser vendors, right? and typically there
>> are no more than.... 10?
>
> Browsers implement what their users ask for. They don't want to add featu=
res
> that are not desired and make experience worse or reduce reliability. But=
 if
> users ask for something, they'll certainly implement it.


Well, I understand (and agree) most of your text, but I still think
that the URI resolution mechanism is something transparent for an
end-user. This is not like having FlashPlayer for showing annoying and
dancing menus in a web page XD. End-users ask for FlashPlayer (and
Android 2.3 has included it for example) but end-users won't ask for
"SRV procedures".

I would translate your arguments to "web developers", those who want
to provide scalable systems and for which having some kind of QoS
mechanisms (specially for mobile devices) is a great advantage. Of
course, if this happens then end-users would be happier :)

--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From w@1wt.eu  Wed Jul 27 08:37:34 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D52C21F899F; Wed, 27 Jul 2011 08:37:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.205
X-Spam-Level: 
X-Spam-Status: No, score=-4.205 tagged_above=-999 required=5 tests=[AWL=-2.462, BAYES_00=-2.599, HELO_IS_SMALL6=0.556, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Oidh-MKeLdq; Wed, 27 Jul 2011 08:37:34 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 8E7C721F891F; Wed, 27 Jul 2011 08:37:32 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6RFbQ83007587; Wed, 27 Jul 2011 17:37:26 +0200
Date: Wed, 27 Jul 2011 17:37:26 +0200
From: Willy Tarreau <w@1wt.eu>
To: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110727153726.GA7579@1wt.eu>
References: <20110724204236.GG22405@1wt.eu> <CALiegfkgukeaiMR-Yc15qUJYCB-KPcoNoX4G6NrN4+DOiDS+tw@mail.gmail.com> <20110726192850.GB3692@1wt.eu> <CALiegfndubt3xgRLFWUikhizsvX60p4+b0DcouX0_m5B8vestg@mail.gmail.com> <20110727101757.GA6586@1wt.eu> <CALiegfmMO2Es6P=qy4m=XULVQE9bDp7S0LYXG_9n4Lk9yirGXQ@mail.gmail.com> <20110727124545.GA6931@1wt.eu> <CALiegf=YCCYuoVk1isPOwfB1z8mpSxbJmFHU5vEyQo7xOGH5RA@mail.gmail.com> <20110727140302.GB7225@1wt.eu> <CALiegfmWWL2sxB=4=kD-YmE30rsS3_-DGqePCohv_hv2QQfJUw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CALiegfmWWL2sxB=4=kD-YmE30rsS3_-DGqePCohv_hv2QQfJUw@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Wed, 27 Jul 2011 08:53:48 -0700
Cc: Server-Initiated HTTP <hybi@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, 27 Jul 2011 15:37:34 -0000

On Wed, Jul 27, 2011 at 05:19:30PM +0200, Iñaki Baz Castillo wrote:
> Well, I understand (and agree) most of your text, but I still think
> that the URI resolution mechanism is something transparent for an
> end-user. This is not like having FlashPlayer for showing annoying and
> dancing menus in a web page XD. End-users ask for FlashPlayer (and
> Android 2.3 has included it for example) but end-users won't ask for
> "SRV procedures".

They won't "ask for", but when some sites pretend "we work better with",
then they'll ask for the techno to use the site better. It's similar to
the HTTP/1.0 or 1.1, keep-alive and pipelining that you can enable in
your browser. Most users won't play with it, still that's pretty
configurable. Similarly end users can decide to enable/disable IPv6 or
IDN.

> I would translate your arguments to "web developers", those who want
> to provide scalable systems and for which having some kind of QoS
> mechanisms (specially for mobile devices) is a great advantage. Of
> course, if this happens then end-users would be happier :)

I think you got it :-)

Willy


From marka@isc.org  Wed Jul 27 09:04:21 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 A524311E80E8; Wed, 27 Jul 2011 09:04:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.15
X-Spam-Level: 
X-Spam-Status: No, score=-1.15 tagged_above=-999 required=5 tests=[AWL=-1.451,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MANGLED_COMPNY=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 81LifpFrt4xR; Wed, 27 Jul 2011 09:04: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 D8FC611E80F2; Wed, 27 Jul 2011 09:04:20 -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 DB20B5F997F; Wed, 27 Jul 2011 16:04: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 C125C216C87; Wed, 27 Jul 2011 16:03:33 +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 A07C31236670; Thu, 28 Jul 2011 02:03:31 +1000 (EST)
To: Tim Chown <tjc@ecs.soton.ac.uk>
From: Mark Andrews <marka@isc.org>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <968F0B1C-D082-4A59-8213-FD58C74AF89D@nominum.com> <20110727151517.CF9371235D70@drugs.dv.isc.org> <D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk> <EMEW3|fcf145b5033ff99790b7c34003f47686n6QGZC03tjc|ecs.soton.ac.uk|D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk>
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
In-reply-to: Your message of "Wed, 27 Jul 2011 16:35:07 +0100." <EMEW3|fcf145b5033ff99790b7c34003f47686n6QGZC03tjc|ecs.soton.ac.uk|D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk>
Date: Thu, 28 Jul 2011 02:03:31 +1000
Message-Id: <20110727160331.A07C31236670@drugs.dv.isc.org>
Cc: IPv6 Operations <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, 27 Jul 2011 16:04:21 -0000

In message <EMEW3|fcf145b5033ff99790b7c34003f47686n6QGZC03tjc|ecs.soton.ac.uk|D
0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk>, Tim Chown writes:
> 
> On 27 Jul 2011, at 16:15, Mark Andrews wrote:
> > 
> > Because it will come down to "run 6to4 and be exposed to some bug"
> > or "not run 6to4 but be safe from the bug".  We already have vendors
> > saying they are thinking about pulling 6to4 from their code bases
> > if it becomes historic.
> 
> I would note that RIPE-501 does not mention 6to4:
> 	http://www.ripe.net/ripe/docs/ripe-501
> As far as I can see, it only mentions RFC4213.
> 
> I would ask what is the alternative if as Mark suggests the vendors begin rem
> oving 6to4 support?
> a) use 6to4 anyway on an open platform like OpenWRT

Which may or may not still have the code.  OpenWRT could remove
support just the same as another source could.  OpenWRT is also not
widely supported by CPE vendors.  i.e. you are own your own if
something goes wrong in most (not all) cases.

> b) use a tunnel broker - this works much better through NATs and with dynamic
>  IPv4 addresses

For which there is only experimental / ad-hoc code.  Please name
CPE vendors that support tsp?  Please name CPE vendors that support
tunnel re-configuration on re-number.

> c) use your $work VPN if it supports IPv6, which it could/should if your comp
> any values IPv6
> d) get IPv6 from your ISP, or move to one that has it if yours does not

Which is not always a viable option.

> I suspect, but have no proof, that the huge majority of 6to4 users don't use 
> it intentionally, and the content they are trying to reach is also available 
> over IPv4. But for people who want to develop and use new IPv6-specific apps,
> then either a broker or something like OpenWRT ought to meet their needs?
>
> Tim
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From jnc@mercury.lcs.mit.edu  Wed Jul 27 09:14:46 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 CAD7911E8071; Wed, 27 Jul 2011 09:14:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.511
X-Spam-Level: 
X-Spam-Status: No, score=-6.511 tagged_above=-999 required=5 tests=[AWL=0.088,  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 NbYeS1cc4l8s; Wed, 27 Jul 2011 09:14:46 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id E381721F8666; Wed, 27 Jul 2011 09:14:45 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 1C00A18C0CB; Wed, 27 Jul 2011 12:14:45 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
Message-Id: <20110727161445.1C00A18C0CB@mercury.lcs.mit.edu>
Date: Wed, 27 Jul 2011 12:14:45 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: v6ops@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: Wed, 27 Jul 2011 16:14:46 -0000

    > From: Philip Homburg <pch-v6ops@u-1.phicoh.com>

    > I think it would be quite weird to keep 6to4 at standards track just to
    > prevent some vendors from dropping 6to4 support.

There have been suggestions that it might be more appropriate to reclassify
it as Experimental, and I think that makes a lot of sense - as you correctly
(IMO) point out, due to its issues 6to4 is not really appropriate for
standards track (at least, in its current form).

	Noel

From dotis@mail-abuse.org  Wed Jul 27 09:22:39 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 D003311E80E8 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 09:22:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.266
X-Spam-Level: 
X-Spam-Status: No, score=-104.266 tagged_above=-999 required=5 tests=[AWL=-1.667, 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 JRWmlXshkkUN for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 09:22:39 -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 515AD11E80E1 for <ietf@ietf.org>; Wed, 27 Jul 2011 09:22:39 -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 96D076E0144 for <ietf@ietf.org>; Wed, 27 Jul 2011 16:22:38 +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 DE3C0A9443B for <ietf@ietf.org>; Wed, 27 Jul 2011 16:22:38 +0000 (UTC)
Message-ID: <4E303B4D.1020604@mail-abuse.org>
Date: Wed, 27 Jul 2011 09:22:37 -0700
From: Douglas Otis <dotis@mail-abuse.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com>	<4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com> <39EEA819-6D8D-4FE7-958D-D7DCEDF893C1@townsley.net>
In-Reply-To: <39EEA819-6D8D-4FE7-958D-D7DCEDF893C1@townsley.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 16:22:40 -0000

On 7/27/11 4:31 AM, Mark Townsley wrote:
> On Jul 27, 2011, at 7:09 AM, Fred Baker wrote:
>
> On Jul 26, 2011, at 6:49 PM, Brian E Carpenter wrote:
>
>>> Since 6to4 is a transition mechanism it has no long term future *by definition*. Even if someone chooses to design a v2, who is going to implement it?
>> Actually, I think one could argue pretty effectively that 6rd is 6to4-bis.
> +1
+1

-Doug

From marka@isc.org  Wed Jul 27 09:26:27 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 6D3F321F8A4B; Wed, 27 Jul 2011 09:26:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.27
X-Spam-Level: 
X-Spam-Status: No, score=-2.27 tagged_above=-999 required=5 tests=[AWL=-0.271,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8yxAyVuBiWdl; Wed, 27 Jul 2011 09:26:27 -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 D8B8921F899F; Wed, 27 Jul 2011 09:26:26 -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 899D65F996E; Wed, 27 Jul 2011 16:26:08 +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 928C7216C84; Wed, 27 Jul 2011 16:25:36 +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 93E3C1236E8D; Thu, 28 Jul 2011 02:25:34 +1000 (EST)
To: Cameron Byrne <cb.list6@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <968F0B1C-D082-4A59-8213-FD58C74AF89D@nominum.com> <20110727151517.CF9371235D70@drugs.dv.isc.org> <CAD6AjGThTpvH5HgGc8RbedOcJKZ=_JLR=2t7yAAJWKSS1cKNSg@mail.gmail.com>
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
In-reply-to: Your message of "Wed, 27 Jul 2011 08:27:54 MST." <CAD6AjGThTpvH5HgGc8RbedOcJKZ=_JLR=2t7yAAJWKSS1cKNSg@mail.gmail.com>
Date: Thu, 28 Jul 2011 02:25:34 +1000
Message-Id: <20110727162534.93E3C1236E8D@drugs.dv.isc.org>
Cc: "<ietf@ietf.org>" <ietf@ietf.org>, IPv6 Operations <v6ops@ietf.org>, Ted Lemon <Ted.Lemon@nominum.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, 27 Jul 2011 16:26:27 -0000

In message <CAD6AjGThTpvH5HgGc8RbedOcJKZ=_JLR=2t7yAAJWKSS1cKNSg@mail.gmail.com>
, Cameron Byrne writes:
> On Jul 27, 2011 8:16 AM, "Mark Andrews" <marka@isc.org> wrote:
> >
> >
> > In message <968F0B1C-D082-4A59-8213-FD58C74AF89D@nominum.com>, Ted Lemon
> writes
> > :
> > > If you have a reason to install and enable 6to4, why would the nominal
> > > status of a couple of RFCs make you do anything different?
> >
> > Because it will come down to "run 6to4 and be exposed to some bug"
> > or "not run 6to4 but be safe from the bug".  We already have vendors
> > saying they are thinking about pulling 6to4 from their code bases
> > if it becomes historic.
> 
> You also have content owners that say no aaaa while 6to4 is tanking
> reliability stats.

You have Google Chrome and Firefox already implementing HE.  You
have new address selection rules out there.  You have a dramatic
decrease in 6to4 traffic already as a result.  You have improved
throughput for the 80% of machines for which 6to4 does work.

We are yet to see the effects of Mac OS Lion both the 6to4 side
and the HE side.

> Pick your battles.
> 
> Cb
> > > This seems like an easy question to answer.   You'd implement and use
> 6to4v=
> > > 2 because it works better than the historic 6to4 protocol.
> > --
> > Mark Andrews, ISC
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From touch@isi.edu  Wed Jul 27 10:04:53 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 6D07311E8081 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 10:04:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.361
X-Spam-Level: 
X-Spam-Status: No, score=-105.361 tagged_above=-999 required=5 tests=[AWL=1.238, 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 DHVY1JeqH5Sr for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 10:04:53 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id EEFCB11E807B for <ietf@ietf.org>; Wed, 27 Jul 2011 10:04:52 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p6RH4OxA011918 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 27 Jul 2011 10:04:24 -0700 (PDT)
Message-ID: <4E304518.8010905@isi.edu>
Date: Wed, 27 Jul 2011 10:04:24 -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: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Additional registries converted to XML and announcement of new registry for Service Names and Port Numbers
References: <CA4E3BF0.32F65%michelle.cotton@icann.org> <4E2A9EBE.7090000@gmail.com>
In-Reply-To: <4E2A9EBE.7090000@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 17:04:53 -0000

On 7/23/2011 3:13 AM, Mykyta Yevstifeyev wrote:
> Hello,
>
> The new registry says:
>
>>   System Ports are assigned by IETF
>>   process for standards-track protocols, as per [RFC1340].  User Ports
>>   are assigned by IANA using the "Expert Review" process, as per
>>   [RFC5226].  Dynamic Ports are not assigned.
>
> I don't understand referencing RFC 1340 here.

1340 defines system vs. user ports.

You're right; it should refer to RFC 5226 there instead.

 > You could better change
> this to "System Ports are assigned per "Standards Action" or "IESG
> Approval" process, as per [RFC5226]".

That's OK.

> IESG Approval is assumed by the
> RFC-to-be, Section 8.1:
>
>>     o  Reserved numbers and names are generally only assigned by a
>>        Standards Action or an IESG Approval,

The above text isn't needed.

> Also, the new registry doesn't seem to match the following rule:
>
>>     The new assignment procedure
>>     conserves resources by assigning a port number to an application for
>>     only those transport protocols (TCP, UDP, SCTP and/or DCCP) it
>>     actually uses.  The port number will be marked as Reserved - instead
>>     of Assigned - in the port number registries of the other transport
>>     protocols.
 >
> Such entries as:
>
>> tcpmux               1         tcp    TCP Port Service Multiplexer [Mark_Lottor]                       [Mark_Lottor]
>> tcpmux               1         udp    TCP Port Service Multiplexer [Mark_Lottor]                       [Mark_Lottor]
>
> should be:
>
>> tcpmux               1         tcp    TCP Port Service Multiplexer [Mark_Lottor]                       [Mark_Lottor]
>> tcpmux               1         udp    TCP Port Service Multiplexer [Mark_Lottor]                       [Mark_Lottor]
>>                       1        sctp    Reserved
>>                       1        dccp    Reserved

Yes. This is already the case for TCP/UDP entries, but we should be 
consistent with sctp and dccp.

Joe


From dave@cridland.net  Wed Jul 27 10:07:19 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 0DB8421F8C00; Wed, 27 Jul 2011 10:07:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sXW0H941uL0k; Wed, 27 Jul 2011 10:07:18 -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 422E721F8BFF; Wed, 27 Jul 2011 10:07:18 -0700 (PDT)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id D68D41168087; Wed, 27 Jul 2011 18:07:14 +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 qV7+Jj44yN1v; Wed, 27 Jul 2011 18:07:12 +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 5D3491168067; Wed, 27 Jul 2011 18:07:12 +0100 (BST)
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <CALiegf=4K2oWfmZjGMD7J_jyaDtS3i+Mu7R0Wh75Rr+MrQCjtw@mail.gmail.com> <20110722054345.GE18126@1wt.eu> <CALiegfnYm6g63JDHLiSH__r-or3kzK0XCVa3cC7RMP14KWBOSg@mail.gmail.com> <20110724120751.GQ22405@1wt.eu> <CALiegfncavmoMp4YDCeeJ3rsOfHAYQ99itKX2Q2eHB351T3X5A@mail.gmail.com> <20110724184537.GZ22405@1wt.eu> <CALiegfne620wuDMAp235n3mVcXTAnbhhNm8vpiNCy5F7+VD92A@mail.gmail.com> <20110724192948.GD22405@1wt.eu> <CALiegf=e48kkF+Gky1mY7LippUB-0kZDgSGZrJxk1aZupAGkYw@mail.gmail.com> <20110727012806.EBB811231907@drugs.dv.isc.org> <20110727052549.GB4086@1wt.eu>
In-Reply-To: <20110727052549.GB4086@1wt.eu>
MIME-Version: 1.0
Message-Id: <9031.1311786432.357811@puncture>
Date: Wed, 27 Jul 2011 18:07:12 +0100
From: Dave Cridland <dave@cridland.net>
To: Willy Tarreau <w@1wt.eu>, =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>, Mark Andrews <marka@isc.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, 27 Jul 2011 17:07:19 -0000

On Wed Jul 27 06:25:49 2011, Willy Tarreau wrote:
> On Wed, Jul 27, 2011 at 11:28:06AM +1000, Mark Andrews wrote:
> > > SRV provides load-balancing and failover. I never said that SRV  
> is a
> > > solution for temporaly put in maintenance a server.
> >
> > Happy eyeballs however does allow you to take a server out of  
> production
> > and not really notice it.  Note webbrowsers have had the ability  
> to do
> > this for as long as webbrowsers have existed.
> 
> Mark, could you elaborate on this point ? Surely you're not talking  
> about
> the fact that a browser retries a failed connection, but I'm not  
> not sure
> what mechanism you're talking about.

Happy eyeballs - try everything as soon as you can, in parallel. Drop  
everything else when one does.

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 tnadeau@lucidvision.com  Wed Jul 27 10:07:47 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 3314421F8C0A; Wed, 27 Jul 2011 10:07:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.376
X-Spam-Level: 
X-Spam-Status: No, score=-0.376 tagged_above=-999 required=5 tests=[AWL=0.227,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6, 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 DapZ4EfOBSG6; Wed, 27 Jul 2011 10:07:46 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 9007121F8C02; Wed, 27 Jul 2011 10:07:46 -0700 (PDT)
Received: from [130.129.19.44] (dhcp-132c.meeting.ietf.org [130.129.19.44]) by lucidvision.com (Postfix) with ESMTP id 207BB1D2C37C; Wed, 27 Jul 2011 13:07:46 -0400 (EDT)
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com> <39EEA819-6D8D-4FE7-958D-D7DCEDF893C1@townsley.net>
In-Reply-To: <39EEA819-6D8D-4FE7-958D-D7DCEDF893C1@townsley.net>
Mime-Version: 1.0 (iPad Mail 8J2)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <315867B5-EE5F-4440-999D-5E4253A68C2D@lucidvision.com>
X-Mailer: iPad Mail (8J2)
From: Thomas Nadeau <tnadeau@lucidvision.com>
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
Date: Wed, 27 Jul 2011 13:08:09 -0400
To: Mark Townsley <mark@townsley.net>
Cc: IPv6 Operations <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, 27 Jul 2011 17:07:47 -0000

On Jul 27, 2011, at 7:31 AM, Mark Townsley <mark@townsley.net> wrote:

>=20
> On Jul 27, 2011, at 7:09 AM, Fred Baker wrote:
>=20
>>=20
>> On Jul 26, 2011, at 6:49 PM, Brian E Carpenter wrote:
>>=20
>>> Since 6to4 is a transition mechanism it has no long term future *by defi=
nition*. Even if someone chooses to design a v2, who is going to implement i=
t?
>>=20
>> Actually, I think one could argue pretty effectively that 6rd is 6to4-bis=
.=20
>=20
> +1
>=20
> - Mark

+2


>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20

From tjc@ecs.soton.ac.uk  Wed Jul 27 10:25:18 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 D35E821F86CA; Wed, 27 Jul 2011 10:25:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.406
X-Spam-Level: 
X-Spam-Status: No, score=-1.406 tagged_above=-999 required=5 tests=[AWL=-1.107, BAYES_00=-2.599, MANGLED_COMPNY=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 Wk0d1n4yArMM; Wed, 27 Jul 2011 10:25:18 -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 B041721F854E; Wed, 27 Jul 2011 10:25:17 -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 p6RHPF9s032351; Wed, 27 Jul 2011 18:25:15 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p6RHPF9s032351
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1311787516; bh=9ae6gc4yomJzXJMKKl9ywczf524=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=VtTbqVU3qMsXBjmLE7aDtiSc/fSE4Bbi85YiAvy1QRlY1NxOKIfw4PokMnyK8Q8Dn j/kgVags7l03TNdUNgwRAZA18DSPcT5UZI3yWj91HUopf/4Jeu7mXoJ/uSYeannNhs hOou5FFWMygvAt6keJeiUJ3gAzNmju+Z3KCcf0KI=
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 n6QIPF0366145710mB ret-id none; Wed, 27 Jul 2011 18:25:16 +0100
Received: from [IPv6:2001:df8::112:dd15:b32:a2fa:af1f] ([IPv6:2001:df8:0:112:dd15:b32:a2fa:af1f]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p6RHP6X7025232 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 27 Jul 2011 18:25:06 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1244.3)
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <20110727160331.A07C31236670@drugs.dv.isc.org>
Date: Wed, 27 Jul 2011 18:25:06 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|1be1beb1e5d17f8775eb339dfeb479adn6QIPF03tjc|ecs.soton.ac.uk|E8FD4F5B-A87D-4D1D-9A10-9911AAE7A38D@ecs.soton.ac.uk>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <968F0B1C-D082-4A59-8213-FD58C74AF89D@nominum.com> <20110727151517.CF9371235D70@drugs.dv.isc.org> <D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk> <EMEW3|fcf145b5033ff99790b7c34003f47686n6QGZC03tjc|ecs.soton.ac.uk|D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk> <20110727160331.A07C31236670@drugs.dv.isc.org> <E8FD4F5B-A87D-4D1D-9A10-9911AAE7A38D@ecs.soton.ac.uk>
To: IPv6 Operations <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1244.3)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n6QIPF036614571000; tid=n6QIPF0366145710mB; 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: p6RHPF9s032351
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, 27 Jul 2011 17:25:18 -0000

On 27 Jul 2011, at 17:03, Mark Andrews wrote:

> 0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk>, Tim Chown =
writes:
>>=20
>> a) use 6to4 anyway on an open platform like OpenWRT
>=20
> Which may or may not still have the code.  OpenWRT could remove
> support just the same as another source could.  OpenWRT is also not
> widely supported by CPE vendors.  i.e. you are own your own if
> something goes wrong in most (not all) cases.

In the event OpenWRT should remove 6to4 support, just get like-minded =
people together (if there are lots of people that consciously want to =
use 6to4 for application development and testing) and roll your own.

>> b) use a tunnel broker - this works much better through NATs and with =
dynamic
>> IPv4 addresses
>=20
> For which there is only experimental / ad-hoc code.  Please name
> CPE vendors that support tsp?  Please name CPE vendors that support
> tunnel re-configuration on re-number.

Jeroen has answered this, but I would point out, as an example of what =
can be done in short time, that I had a student last year who developed =
a mini-ITX Linux build with tunnel broker support, and IPv6 firewall and =
QoS support, using a web interface driving existing tools like iptables =
and tc.  He chose to use the HE broker, and it's a one-time registration =
after which it just works without further user intervention with HE.

It would be very interesting to see brokenness figures for well-known =
broker prefixes as against 6to4, if anyone is gathering such data.

>> c) use your $work VPN if it supports IPv6, which it could/should if =
your comp
>> any values IPv6
>> d) get IPv6 from your ISP, or move to one that has it if yours does =
not
>=20
> Which is not always a viable option.

It is in the UK, at least.

Tim=

From hannes.tschofenig@gmx.net  Wed Jul 27 10:52:26 2011
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A721E21F8B11 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 10:52:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 BPr58IhzGfuM for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 10:52:26 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id A7DED21F8AFA for <ietf@ietf.org>; Wed, 27 Jul 2011 10:52:24 -0700 (PDT)
Received: (qmail invoked by alias); 27 Jul 2011 17:52:14 -0000
Received: from dhcp-172b.meeting.ietf.org (EHLO dhcp-172b.meeting.ietf.org) [130.129.23.43] by mail.gmx.net (mp059) with SMTP; 27 Jul 2011 19:52:14 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX188XO1VBTc8oDBgYigquZOO9O/ta0c/MEbkQpcO5y Yemwxazxlgvnfs
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: RFC 6302: "Internet-Facing Server Logging": No Word about Privacy?
Date: Wed, 27 Jul 2011 13:52:11 -0400
Message-Id: <A7A1E90D-AE24-401C-8B29-A3DA7252401A@gmx.net>
To: "ietf@ietf.org IETF" <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
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: Wed, 27 Jul 2011 17:52:26 -0000

Hi all,=20

I just noticed this document about "Internet-Facing Server Logging":
http://tools.ietf.org/html/rfc6302

It does not contain any privacy considerations even thought it would be =
a very natural thing to do.=20

Does anyone know the history of this document?=20

Ciao
Hannes


From moore@network-heretics.com  Wed Jul 27 11:18:12 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 481E321F8C12 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 11:18:12 -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_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 ZKI9ZcWBhdYT for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 11:18:11 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 3BA9721F8BB9 for <ietf@ietf.org>; Wed, 27 Jul 2011 11:18:10 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 159F120C86; Wed, 27 Jul 2011 14:18:09 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Wed, 27 Jul 2011 14:18: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=AzV 5HVI1HDT+4/1w+Y+28Utlkro=; b=mW/4K/XmnKotujcMN7ChPScIft14tz8K0fJ soS75a7waEbFZ8dTXldrNWEZTTYtIZQSLytqme3YCl+m4DnDCSeVHNQDIcUi58JQ Qg8o9Npe6OH0oNzEOpCg0trb7mxt3g6uW6BUn+RozXaEm+vu7+eVcJv+t/Tbd9ct f0sBnsas=
X-Sasl-enc: 5bydGy4isbmoKHwD3P1asSUcmXHtEyBmoNJgk/2nV4YS 1311790688
Received: from dhcp-12d1.meeting.ietf.org (dhcp-12d1.meeting.ietf.org [130.129.18.209]) by mail.messagingengine.com (Postfix) with ESMTPSA id AE5884145CF; Wed, 27 Jul 2011 14:18:08 -0400 (EDT)
Subject: "6to4 damages the Internet" (was Re: draft-ietf-v6ops-6to4-to-historic (yet again))
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-36-623522706
From: Keith Moore <moore@network-heretics.com>
X-Priority: 3
In-Reply-To: <006d01cc4c2f$55e8dd40$4001a8c0@gateway.2wire.net>
Date: Wed, 27 Jul 2011 14:18:07 -0400
Message-Id: <A25A544B-DDEA-483B-98B4-8D4C1F8B19A4@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <006d01cc4c2f$55e8dd40$4001a8c0@gateway.2wire.net>
To: t.petch <daedulus@btconnect.com>
X-Mailer: Apple Mail (2.1084)
Cc: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 18:18:12 -0000

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

On Jul 27, 2011, at 3:32 AM, t.petch wrote:

> I oppose this action.
>=20
> I see clear evidence that 6to4 is damaging the Internet and although =
there are
> those who can use it without causing damage, I believe that the =
principle is
> 'First, do no harm'
> so the IETF has a responsibility to discourage its use.  [...]

I'd like to address the point that "6to4 damages the Internet".

I do understand the content providers' argument - if 6to4 is turned on =
at the originator's host or network, the destination is advertising both =
A and AAAA records, and the AAAA record is chosen in preference to the A =
record, the user's experience is degraded.  Sometimes the performance is =
degraded marginally (but the cumulative effect of lots of small delays =
on a web page that loads dozens of images is large).  Sometimes it's =
degraded significantly because the 6to4 address doesn't work at all. =
Both cases matter, and they do provide a disincentive to content =
providers to just slap AAAA records onto their sites and be done with =
it.  (There are other ways of a web site utilizing v6, but they require =
more work.)

A lot of the arguments that I hear about 6to4 being "bad" in a universal =
sense seem to be based on the assumption that it's only access to =
"content" in the public Internet that matters.  But anyone who has =
followed IPv6 development should know better than that.   If access to =
"content" in the public Internet were all that mattered, there would =
have been no interest in ULAs.   It remains the case that many =
enterprise networks have all kinds of "internal" resources that are =
useful to them even if they're not publicly addressable, and are only =
usable from within that network or from other networks with which they =
have made explicit arrangements.

For better or worse, an explicit design "feature" of IPv6 is that hosts =
can have multiple addresses, and that different addresses might be =
needed in different contexts.  A host's public address might be used =
when contacting a public web server, but when communicating within an =
enterprise network or between networks each using ULA space, the host =
might need to use its ULA address as a source address (the other host =
might not have a public address or the ability to send traffic to the =
public IPv6 network). =20

I put the word "feature" in quotes because this can be a pain in the a** =
for applications and users.   The default address selection rules don't =
really handle this case very well, nor can any set of static default =
rules handle this case.  Essentially what having multiple addresses per =
host implies is that hosts or applications need to do routing in the =
absence of routing information.  It shouldn't surprise anybody that the =
use of addresses that only work well (or at all) within a limited scope =
creates situations where a host will try to send traffic down a path =
that will never get it there, even when a different path would have =
worked.

Introducing IPv6 - any kind of IPv6 - into a world of hosts that already =
support IPv4, creates exactly this situation.

Nothing in IPv4 prohibited hosts from having multiple addresses and from =
advertising multiple addresses in DNS.    But this "feature" was rarely =
used, except in cases where all of the addresses were approximately =
equivalent in performance, because it didn't work well if some addresses =
performed better than others.  Then, as now, hosts and applications had =
no good way of reliably choosing which source and destination address to =
use.   But unlike IPv4, IPv6 deliberately chose to not only support the =
ability to have multiple addresses per host, but to actually expect it =
in a number of cases.

One way to look at the content providers' complaint against 6to4, is =
that 6to4 addresses are not "approximately equivalent in performance" to =
IPv4 addresses.  So when hosts or applications happen to choose the 6to4 =
address over an IPv4 address for the same resource, sometimes that =
choice ends up not working, or being suboptimal.  This is nothing new =
with 6to4.  It's inherently the case that having multiple addresses for =
a host that aren't equivalent in performance leads to suboptimal choices =
in some cases.

So essentially, the argument that "6to4 damages the Internet", is =
tantamount to "having multiple addresses for hosts damages the =
Internet".

And this is an explicitly chosen architectural "feature" of IPv6.   =
Blaming 6to4 for the problems caused by this "feature" is like blaming =
the canary carried by a coal miner for ceasing to chirp. =20

(Though as it turns out, in the case of 6to4 the fix is relatively easy =
- just make 6to4 lower preference than either IPv4 or native IPv6 =
addresses except when the source and destination are both 6to4. )

--

People who are entirely engaged in providing content may have a hard =
time seeing any utility in 6to4.   They may ask, "if it doesn't deliver =
content as well as IPv4 does, what good is it?".   My answer to that =
question is, "what good are private networks and ULAs? "

6to4 as defined by RFC 3056 is a bit like a ULA.  It provides a way for =
individual hosts that have a public IPv4 address, and hosts on small =
networks that have a public IPv4 address, to be able to interchange IPv6 =
traffic.   True, it doesn't work through NAT, but it can be used as a =
way to provide IPv6 service within the 6to4 realm.  This lets users =
leverage the IPv6 protocol and IPv6 aware applications to get useful =
things done, that they would not have been able to do using IPv4.  =
Personally, I've found 6to4 useful to let me log into my home machines =
remotely, to remotely access file systems, to print to my home printer =
from work and my work printer from home, and a number of other things - =
all without making any application-specific arrangements.   For years =
I've heard from and read about other people using 6to4 in similar ways.

The mechanism defined in RFC 3068 takes a step down the slippery slope =
of trying to make 6to4 into a means to access the public IPv6 Internet =
(and vice versa).  Because it was designed in an era where managed, =
supported IPv6 service was not widely available, it necessarily relies =
on the good will of people willing to provide relay routers.  And =
relying on the good will of those people comes with, or should come =
with, decreased expectations.  Note, however that we're still in the era =
where managed, supported IPv6 service is not widely available.  As long =
as we're in that era, and as long as native v4 access is available to =
some users, any statements to the effect that 6to4 is evil, obsolete, =
historic, etc., even for the purposes of accessing the public v6 =
internet, are premature.  (But if you want to say that it's not reliable =
for this purpose, that's a defensible statement.)

The problem is that ordinary users don't know that they should have =
decreased expectations.  They might not even be aware that they're using =
6to4, or relying on the good will of others.  =20

Keith


--Apple-Mail-36-623522706
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><div>On Jul 27, 2011, at 3:32 AM, t.petch wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>I =
oppose this action.<br><br>I see clear evidence that 6to4 is damaging =
the Internet and although there are<br>those who can use it without =
causing damage, I believe that the principle is<br>'First, do no =
harm'<br>so the IETF has a responsibility to discourage its use. =
&nbsp;[...]</div></blockquote><br></div></div><div>I'd like to address =
the point that "6to4 damages the Internet".</div><div><br></div><div>I =
do understand the content providers' argument - if 6to4 is turned on at =
the originator's host or network, the destination is advertising both A =
and AAAA records, and the AAAA record is chosen in preference to the A =
record, the user's experience is degraded. &nbsp;Sometimes the =
performance is degraded marginally (but the cumulative effect of lots of =
small delays on a web page that loads dozens of images is large). =
&nbsp;Sometimes it's degraded significantly because the 6to4 address =
doesn't work at all. Both cases matter, and they do provide a =
disincentive to content providers to just slap AAAA records onto their =
sites and be done with it. &nbsp;(There are other ways of a web site =
utilizing v6, but they require more work.)</div><div><br></div><div>A =
lot of the arguments that I hear about 6to4 being "bad" in a universal =
sense seem to be based on the assumption that it's only access to =
"content" in the public Internet that matters. &nbsp;But anyone who has =
followed IPv6 development should know better than that. &nbsp; If access =
to "content" in the public Internet were all that mattered, there would =
have been no interest in ULAs. &nbsp; It remains the case that many =
enterprise networks have all kinds of "internal" resources that are =
useful to them even if they're not publicly addressable, and are only =
usable from within that network or from other networks with which they =
have made explicit arrangements.</div><div><br></div><div>For better or =
worse, an explicit design "feature" of IPv6 is that hosts can have =
multiple addresses, and that different addresses might be needed in =
different contexts. &nbsp;A host's public address might be used when =
contacting a public web server, but when communicating within an =
enterprise network or between networks each using ULA space, the host =
might need to use its ULA address as a source address (the other host =
might not have a public address or the ability to send traffic to the =
public IPv6 network). &nbsp;</div><div><br></div><div>I put the word =
"feature" in quotes because this can be a pain in the a** for =
applications and users. &nbsp; The default address selection rules don't =
really handle this case very well, nor can any set of static default =
rules handle this case. &nbsp;Essentially what having multiple addresses =
per host implies is that hosts or applications need to do routing in the =
absence of routing information. &nbsp;It shouldn't surprise anybody that =
the use of addresses that only work well (or at all) within a limited =
scope creates situations where a host will try to send traffic down a =
path that will never get it there, even when a different path would have =
worked.</div><div><br></div><div>Introducing IPv6 - any kind of IPv6 - =
into a world of hosts that already support IPv4, creates exactly this =
situation.</div><div><br></div><div>Nothing in IPv4 prohibited hosts =
from having multiple addresses and from advertising multiple addresses =
in DNS. &nbsp; &nbsp;But this "feature" was rarely used,<i> except in =
cases where all of the addresses were approximately equivalent in =
performance</i>, because it didn't work well if some addresses performed =
better than others. &nbsp;Then, as now, hosts and applications had no =
good way of reliably choosing which source and destination address to =
use. &nbsp; But unlike IPv4, IPv6 deliberately chose to not only support =
the ability to have multiple addresses per host, but to actually expect =
it in a number of cases.</div><div><br></div><div>One way to look at the =
content providers' complaint against 6to4, is that 6to4 addresses are =
not "approximately equivalent in performance" to IPv4 addresses. =
&nbsp;So when hosts or applications happen to choose the 6to4 address =
over an IPv4 address for the same resource, sometimes that choice ends =
up not working, or being suboptimal. &nbsp;<i>This is nothing new with =
6to4. &nbsp;It's inherently the case that having multiple addresses for =
a host that aren't equivalent in performance leads to suboptimal choices =
in some cases.</i></div><div><i><br></i></div><div>So essentially, the =
argument that "6to4 damages the Internet", is tantamount to "having =
multiple addresses for hosts damages the =
Internet".</div><div><br></div><div><i>And this is an explicitly chosen =
architectural "feature" of IPv6. &nbsp;&nbsp;</i>Blaming 6to4 for the =
problems caused by this "feature" is like blaming the canary carried by =
a coal miner for ceasing to chirp. =
&nbsp;</div><div><br></div><div>(Though as it turns out, in the case of =
6to4 the fix is relatively easy - just make 6to4 lower preference than =
either IPv4 or native IPv6 addresses except when the source and =
destination are both 6to4. =
)</div><div><br></div><div>--</div><div><br></div><div>People who are =
entirely engaged in providing content may have a hard time seeing any =
utility in 6to4. &nbsp; They may ask, "if it doesn't deliver content as =
well as IPv4 does, what good is it?". &nbsp; My answer to that question =
is, "what good are private networks and ULAs? =
"</div><div><br></div><div>6to4 as defined by RFC 3056 is a bit like a =
ULA. &nbsp;It provides a way for individual hosts that have a public =
IPv4 address, and hosts on small networks that have a public IPv4 =
address, to be able to interchange IPv6 traffic. &nbsp; True, it doesn't =
work through NAT, but it can be used as a way to provide IPv6 service =
<i>within the 6to4 realm. &nbsp;</i>This lets users leverage the IPv6 =
protocol and IPv6 aware applications to get useful things done, that =
they would not have been able to do using IPv4. &nbsp;Personally, I've =
found 6to4 useful to let me log into my home machines remotely, to =
remotely access file systems, to print to my home printer from work and =
my work printer from home, and a number of other things - all without =
making any application-specific arrangements. &nbsp; For years I've =
heard from and read about other people using 6to4 in similar =
ways.</div><div><br></div><div>The mechanism defined in RFC 3068 takes a =
step down the slippery slope of trying to make 6to4 into a means to =
access the public IPv6 Internet (and vice versa). &nbsp;Because it was =
designed in an era where managed, supported IPv6 service was not widely =
available, it necessarily relies on the good will of people willing to =
provide relay routers. &nbsp;And relying on the good will of those =
people comes with, or should come with, decreased expectations. =
&nbsp;Note, however that <i>we're still in the era where managed, =
supported IPv6 service is not widely available. &nbsp;<span =
class=3D"Apple-style-span" style=3D"font-style: normal;">As long as =
we're in that era, and as long as native v4 access is available to some =
users, any statements to the effect that 6to4 is evil, obsolete, =
historic, etc., even for the purposes of accessing the public v6 =
internet, are premature. &nbsp;(But if you want to say that it's not =
reliable for this purpose, that's a defensible =
statement.)</span></i></div><div><i><span class=3D"Apple-style-span" =
style=3D"font-style: normal;"><br></span></i></div><div>The problem is =
that ordinary users don't know that they should have decreased =
expectations. &nbsp;They might not even be aware that they're using =
6to4, or relying on the good will of others. =
&nbsp;&nbsp;</div><div><br></div><div><div><div>Keith</div><div><br></div>=
</div></div></body></html>=

--Apple-Mail-36-623522706--

From moore@network-heretics.com  Wed Jul 27 11:21: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 54ED411E8098; Wed, 27 Jul 2011 11:21:56 -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 cEs-K45GiKHC; Wed, 27 Jul 2011 11:21:55 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 07E3711E8084; Wed, 27 Jul 2011 11:21:55 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id AFE052014A; Wed, 27 Jul 2011 14:21:54 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute5.internal (MEProxy); Wed, 27 Jul 2011 14:21: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=FdTyeunTpaEp9WHc/3MTV5Q+fSM=; b=HF p+OzH9QF45AytZtg2fUasoLQZzYceEvLKgiFYNrlxxPDVqKgtirZnpuU2POMIc3O ovrfDNiW98CMOHq6H1DDoii7JL3yd2nib/l+cswYtXoEE7OpxxKGWw2u2RWdQPO/ 6J1TclfFmKNJ3qRg+Mlanuq6OwiFFn4sJsc7/okdA=
X-Sasl-enc: DReTjSDezDBlsELwTh9P78HUWSXvh3WKUPoP7/ibnDia 1311790914
Received: from dhcp-12d1.meeting.ietf.org (dhcp-12d1.meeting.ietf.org [130.129.18.209]) by mail.messagingengine.com (Postfix) with ESMTPSA id 6EEB841443D; Wed, 27 Jul 2011 14:21:54 -0400 (EDT)
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
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|fcf145b5033ff99790b7c34003f47686n6QGZC03tjc|ecs.soton.ac.uk|D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk>
Date: Wed, 27 Jul 2011 14:21:54 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <999C3229-649D-4242-BB0F-2BB494EDF1D9@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <968F0B1C-D082-4A59-8213-FD58C74AF89D@nominum.com> <20110727151517.CF9371235D70@drugs.dv.isc.org> <D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk> <EMEW3|fcf145b5033ff99790b7c34003f47686n6QGZC03tjc|ecs.soton.ac.uk|D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk>
To: Tim Chown <tjc@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.1084)
Cc: IPv6 Operations <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: Wed, 27 Jul 2011 18:21:56 -0000

On Jul 27, 2011, at 11:35 AM, Tim Chown wrote:

> I suspect, but have no proof, that the huge majority of 6to4 users =
don't use it intentionally, and the content they are trying to reach is =
also available over IPv4. But for people who want to develop and use new =
IPv6-specific apps, then either a broker or something like OpenWRT ought =
to meet their needs?

tunnel brokers suck if the tunnel endpoint isn't near your current =
network location.

there are currently no universally applicable, or even widely =
applicable, v6-over-v4 solutions.

Keith


From dwing@cisco.com  Wed Jul 27 11:22:13 2011
Return-Path: <dwing@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 50D5611E80DF for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 11:22:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.961
X-Spam-Level: 
X-Spam-Status: No, score=-103.961 tagged_above=-999 required=5 tests=[AWL=-1.362, 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 HtfZ0wLg0Y6Q for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 11:22:12 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 31A2411E8139 for <ietf@ietf.org>; Wed, 27 Jul 2011 11:22:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=946; q=dns/txt; s=iport; t=1311790930; x=1313000530; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=UUYxpMUbExJSB+7xElGA/9SgR2AqYO3tEQe9FRYOyDs=; b=CRgGOx+6Wbbmg+/m8lCKH1CW5qQYChOVl3T2a2EbNM2GheePxn3+9fcV H+jbW7ABWiZzu+711qDSKgYZnuCBFjb+8TiOd4ZmNIm7U2Gdoe3Oboyzq jlIjAzLkXkxIwiCFAhx+i4EGFUo/T6IRz5LJ7UKtV8OcX+XOY6eF/RYan c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuAAADRWME6rRDoI/2dsb2JhbAA1AQEBAQIBAQEBBQwBGxA6EAcBBAIKDwIEAQE0BxQGEhYNDggBAQUBFg8Yl1uBa41dd4h8BKNenmuGQASjcw
X-IronPort-AV: E=Sophos;i="4.67,277,1309737600";  d="scan'208";a="7090544"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by rcdn-iport-8.cisco.com with ESMTP; 27 Jul 2011 18:22:09 +0000
Received: from dwingWS (sjc-vpn3-1357.cisco.com [10.21.69.77]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p6RIM8bD015262; Wed, 27 Jul 2011 18:22:08 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Hannes Tschofenig'" <hannes.tschofenig@gmx.net>, <ietf@ietf.org>
References: <A7A1E90D-AE24-401C-8B29-A3DA7252401A@gmx.net>
In-Reply-To: <A7A1E90D-AE24-401C-8B29-A3DA7252401A@gmx.net>
Subject: RE: RFC 6302: "Internet-Facing Server Logging": No Word about Privacy?
Date: Wed, 27 Jul 2011 14:22:08 -0400
Message-ID: <069601cc4c8a$18c9d4e0$4a5d7ea0$@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: AcxMhhgRHGxk7GtdSU2wd671kTWPSgAA8pLg
Content-Language: en-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: Wed, 27 Jul 2011 18:22:13 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Hannes Tschofenig
> Sent: Wednesday, July 27, 2011 1:52 PM
> To: ietf@ietf.org IETF
> Subject: RFC 6302: "Internet-Facing Server Logging": No Word about
> Privacy?
> 
> Hi all,
> 
> I just noticed this document about "Internet-Facing Server Logging":
> http://tools.ietf.org/html/rfc6302
> 
> It does not contain any privacy considerations even thought it would be
> a very natural thing to do.
> 
> Does anyone know the history of this document?

It's trying to say that today, servers routinely log:

  * timestamp
  * source IPv4 address
  * resource accessed

and that servers, compliant with RFC6302, need to additionally log:

  * source port

-d

> Ciao
> Hannes
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From moore@network-heretics.com  Wed Jul 27 11:25: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 74AF011E8118; Wed, 27 Jul 2011 11:25:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.539
X-Spam-Level: 
X-Spam-Status: No, score=-4.539 tagged_above=-999 required=5 tests=[AWL=1.060,  BAYES_00=-2.599, GB_I_LETTER=-2, 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 9EptQYWq6bV8; Wed, 27 Jul 2011 11:25: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 E26C711E8101; Wed, 27 Jul 2011 11:25:21 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 90C1A20FFA; Wed, 27 Jul 2011 14:25:21 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Wed, 27 Jul 2011 14:25: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=5BwXqaSaa4uQt1F7EJahX6cP8X8=; b=MG 5hEk/aj50DIc5/gAc5S+lI6Lwy0Ldvs+Tb8MCjfg5R3ni86LosvelrOmWbJDrzuI riLvsFWhlNPsZPTM/ZFTgoz6hdmQlZJdgVF5dq8HOrygefxvwyCxYsjvn5RUSEJK kMJKpzStmnXJv48GjSGqIaRTOt/e7f3NrQQQ9U8i8=
X-Sasl-enc: oqafjX1/v3BikDW+EfMMfRqrRM7dGTrgSRTGEuHECygz 1311791121
Received: from dhcp-12d1.meeting.ietf.org (dhcp-12d1.meeting.ietf.org [130.129.18.209]) by mail.messagingengine.com (Postfix) with ESMTPSA id 3A51A4145D1; Wed, 27 Jul 2011 14:25:21 -0400 (EDT)
Subject: Re: [v6ops] 6to4v2 (as in ripv2)? 
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: <m1QlzXt-0001gSC@stereo.hq.phicoh.net>
Date: Wed, 27 Jul 2011 14:25:20 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <52599079-C6E9-48F9-AFAE-78E7989FB105@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <m1QlzXt-0001gSC@stereo.hq.phicoh.net>
To: Philip Homburg <pch-v6ops@u-1.phicoh.com>
X-Mailer: Apple Mail (2.1084)
Cc: IPv6 Operations <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: Wed, 27 Jul 2011 18:25:22 -0000

On Jul 27, 2011, at 4:32 AM, Philip Homburg wrote:

> In your letter dated Wed, 27 Jul 2011 12:38:33 +1000 you wrote:
>> In message <4E2F4491.30102@gmail.com>, Brian E Carpenter writes:
>>> Of course, if implementors choose to drop the code you might not be
>>> able to upgrade software versions - but hopefully by that time you
>>> will have native IPv6 service anyway.
>>=20
>> Which is exactly why HISTORIC is NOT appropriate.=20
>=20
> With rfc3484-revise and the documented brokenness of 6to4, it doesn't =
make
> any sense for implementors to offer 6to4 anyhow.

False.  It makes even more sense to offer 6to4 because it significantly =
decreases the chance that it will cause a bad experience for users of =
services that provide both v4 and v6 addresses, while increasing the =
chance letting local hosts/users talk to v6-only services/hosts.

> So I think it would be
> quite weird to keep 6to4 at standards track just to prevent some =
vendors from
> dropping 6to4 support.=20


Vendors can drop 6to4 support, or for that matter any other feature, =
anytime they wish.  They don't need permission from IETF to do that.

Keith


From moore@network-heretics.com  Wed Jul 27 11:28: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 095E721F8A71; Wed, 27 Jul 2011 11:28:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.715
X-Spam-Level: 
X-Spam-Status: No, score=-3.715 tagged_above=-999 required=5 tests=[AWL=-0.116, 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 1Os5Pl9CPcE8; Wed, 27 Jul 2011 11:28:49 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id B379D21F8A70; Wed, 27 Jul 2011 11:28:48 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 654D520D6D; Wed, 27 Jul 2011 14:28:48 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Wed, 27 Jul 2011 14:28: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=t3Di7Ii+yuAtmWoN56+lE8FEUcg=; b=Jr f+tACyEBX1M/34Xcmf9swy7NNdHCqneGrnTUypnV8/6NvZLEFZpH1rNpq2uNOflY lJatwy62BZqxXKPjfYSA0GhMahynHIZ+xZ8aG32p9mTqaB4EgTHjpnUSYLHA6dnV tZXRmRQIxEKKxCkkkufvsLA5jcKDBYSFwrssMDQYI=
X-Sasl-enc: uEdfOQ1+uGMBSghRXB9jEUl73kvctsz3rAkxRAEcae76 1311791328
Received: from dhcp-12d1.meeting.ietf.org (dhcp-12d1.meeting.ietf.org [130.129.18.209]) by mail.messagingengine.com (Postfix) with ESMTPSA id 272E240542E; Wed, 27 Jul 2011 14:28:48 -0400 (EDT)
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
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: <CAAedzxpipYVk-nTQmfg1ecPi-+LTOEEAc8twahDj8UG_AhvSQQ@mail.gmail.com>
Date: Wed, 27 Jul 2011 14:28:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5E7CB355-4223-42CC-A621-B1BFD464B57C@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com> <39EEA819-6D8D-4FE7-958D-D7DCEDF893C1@townsley.net> <CAD6AjGTPjhD=yiv5Pe6G4TRGKnPyzn0_nMk9v8bevmGtqu2g3A@mail.gmail.com> <20110727150832.69F5B1235C62@drugs.dv.isc.org> <CAAedzxpipYVk-nTQmfg1ecPi-+LTOEEAc8twahDj8UG_AhvSQQ@mail.gmail.com>
To: Erik Kline <ek@google.com>
X-Mailer: Apple Mail (2.1084)
Cc: IPv6 Operations <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: Wed, 27 Jul 2011 18:28:50 -0000

On Jul 27, 2011, at 11:12 AM, Erik Kline wrote:

> Moving 6to4 to historic does not in any way impact your ability to use
> it as you wish.

False.  Moving 6to4 to Historic is inviting people to mount denial of =
service attacks on things that actually work for people today.  Moving =
6to4 to Historic will also invite vendors to remove 6to4 support from =
future versions or updates of their products, forcing users to make =
difficult choices between using 6to4 on one hand and changing equipment =
or vendors on another.

There's no reason to cause that kind of collateral damage.   Denial of =
service attacks are completely inappropriate.

> 6to4 support is not part of the IPv6 node requirements, as I
> understand it.  Therefore I believe that any vendor (OS, router,
> otherwise) could deleted 6to4 support in any release and be in
> violation of anything, regardless of historic status.

Nothing that IETF specifies requires 6to4.   Vendors can indeed delete =
it if they want to.  But IETF should not recommend that they do so, or =
imply that they should do so.

Keith



From mohta@necom830.hpcl.titech.ac.jp  Wed Jul 27 11:44:07 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 A4A7A11E8146 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 11:44:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.077
X-Spam-Level: 
X-Spam-Status: No, score=-0.077 tagged_above=-999 required=5 tests=[AWL=0.013,  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 IGA3DQiTWc9w for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 11:44:07 -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 A910411E8140 for <ietf@ietf.org>; Wed, 27 Jul 2011 11:44:06 -0700 (PDT)
Received: (qmail 30648 invoked from network); 27 Jul 2011 19:04:01 -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; 27 Jul 2011 19:04:01 -0000
Message-ID: <4E305BFF.7000201@necom830.hpcl.titech.ac.jp>
Date: Thu, 28 Jul 2011 03:42:07 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: "6to4 damages the Internet" (was Re: draft-ietf-v6ops-6to4-to-historic (yet again))
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <006d01cc4c2f$55e8dd40$4001a8c0@gateway.2wire.net> <A25A544B-DDEA-483B-98B4-8D4C1F8B19A4@network-heretics.com>
In-Reply-To: <A25A544B-DDEA-483B-98B4-8D4C1F8B19A4@network-heretics.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: Wed, 27 Jul 2011 18:44:07 -0000

Keith Moore wrote:

>> I see clear evidence that 6to4 is damaging the Internet and although there are
>> those who can use it without causing damage, I believe that the principle is
>> 'First, do no harm'

> I put the word "feature" in quotes because this can be a pain in the a** 

It means it's IPv6 which is damaging the Internet.

> Introducing IPv6 - any kind of IPv6 - into a world of hosts that 

A revised IPv6 and transport which can properly handle multiple
addresses can happily coexist with IPv4.

However, as IPv6 is totally broken, it is better to start with
a clean slate than to revise it. Or, more practically, just stick
to IPv4.

> Nothing in IPv4 prohibited hosts from having multiple addresses

IPv4 with revised transport is far better than the current IPv6
and transport.

> And this is an explicitly chosen architectural "feature" of IPv6.

which is partly why IPv6 is broken and harmful. Proper support
of multihoming can be done only at the transport layer and above.

						Masataka Ohta

From mcr@sandelman.ca  Wed Jul 27 11:44:47 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 C5A7211E8135 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 11:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.033
X-Spam-Level: 
X-Spam-Status: No, score=-1.033 tagged_above=-999 required=5 tests=[AWL=0.921,  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 421qOZcSLktF for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 11:44:46 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id CC98A11E813F for <ietf@ietf.org>; Wed, 27 Jul 2011 11:44:46 -0700 (PDT)
Received: from marajade.sandelman.ca (dhcp-174f.meeting.ietf.org [130.129.23.79]) by relay.sandelman.ca (Postfix) with ESMTPS id 05DC934073; Wed, 27 Jul 2011 14:44:26 -0400 (EDT)
Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 908F2980EA; Wed, 27 Jul 2011 14:45:01 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: ietf@ietf.org
Subject: Re: "6to4 damages the Internet" (was Re: draft-ietf-v6ops-6to4-to-historic (yet again))
In-Reply-To: <A25A544B-DDEA-483B-98B4-8D4C1F8B19A4@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <006d01cc4c2f$55e8dd40$4001a8c0@gateway.2wire.net> <A25A544B-DDEA-483B-98B4-8D4C1F8B19A4@network-heretics.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Wed, 27 Jul 2011 14:45:01 -0400
Message-ID: <26257.1311792301@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
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: Wed, 27 Jul 2011 18:44:47 -0000

Thank you Keith for restating the problem.

>>>>> "Keith" == Keith Moore <moore@network-heretics.com> writes:
    Keith> So essentially, the argument that "6to4 damages the
    Keith> Internet", is tantamount to "having multiple addresses for
    Keith> hosts damages the Internet". 

+1

...

    Keith> People who are entirely engaged in providing content may have
    Keith> a hard time seeing any utility in 6to4.   They may ask, "if
    Keith> it doesn't deliver content as well as IPv4 does, what good is
    Keith> it?".   My answer to that question is, "what good are private
    Keith> networks and ULAs? " 

And, we need to remember that the IETF is the stewart of the IP protocol
suite, not the stewart of the Internet.

Perhaps we actually need Klensin's Internet Standard series, not as a
two-level or something else, but as agreement as to what happens on the
public Internet, vs what might happen behind closed doors.

-- 
]       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 lorenzo@google.com  Wed Jul 27 11:53: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 6A61411E8140 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 11:53:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.876
X-Spam-Level: 
X-Spam-Status: No, score=-105.876 tagged_above=-999 required=5 tests=[AWL=0.100, 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 zz4LlDqdCD6B for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 11:53:23 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id 801C911E8084 for <ietf@ietf.org>; Wed, 27 Jul 2011 11:53:21 -0700 (PDT)
Received: from kpbe19.cbf.corp.google.com (kpbe19.cbf.corp.google.com [172.25.105.83]) by smtp-out.google.com with ESMTP id p6RIrJdc021521 for <ietf@ietf.org>; Wed, 27 Jul 2011 11:53:20 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1311792800; bh=vKS+ffzPdEREMTMaC2zfECHmwvk=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=FiyKZ+72diAM/Z4QtJRjE4PEL7FZx28t3Qsp9spMSUOniLmRQErSBo+F9xZztWweg 4eZ4Y67H7ClyZTjbDhMnA==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type:x-system-of-record; b=JCEiESHgEybbNt3OilfGY3BPu6V/F8thNVRVJdIRolLtOyOivKuLF/XGf1nlq30On pht6ecZDz46fl8AeGmM4A==
Received: from gxk9 (gxk9.prod.google.com [10.202.11.9]) by kpbe19.cbf.corp.google.com with ESMTP id p6RIogd4019259 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Wed, 27 Jul 2011 11:53:18 -0700
Received: by gxk9 with SMTP id 9so1487463gxk.12 for <ietf@ietf.org>; Wed, 27 Jul 2011 11:53:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=lI9FZda+/+uSqmgUQFigZo3IOS4TpdMSW7IrynANvt8=; b=k4YalA/GY0kfReqh3o8zufpWmXZQRcyNIJX4KvVdkn/3mzIXXWcuU/qxY0nmYr/9y3 QFKWL6TbtaWVkKiJsZLQ==
Received: by 10.151.11.10 with SMTP id o10mr143895ybi.171.1311792798220; Wed, 27 Jul 2011 11:53:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.151.156.5 with HTTP; Wed, 27 Jul 2011 11:52:58 -0700 (PDT)
In-Reply-To: <A25A544B-DDEA-483B-98B4-8D4C1F8B19A4@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <006d01cc4c2f$55e8dd40$4001a8c0@gateway.2wire.net> <A25A544B-DDEA-483B-98B4-8D4C1F8B19A4@network-heretics.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 27 Jul 2011 14:52:58 -0400
Message-ID: <CAKD1Yr3eoyi+jeNdPx9-yGRvW1ZDN8rV_-vYQzET6yiWc907aQ@mail.gmail.com>
Subject: Re: "6to4 damages the Internet" (was Re: draft-ietf-v6ops-6to4-to-historic (yet again))
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=000e0cd6aed2c1c31804a9118f79
X-System-Of-Record: true
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 18:53:24 -0000

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

On Wed, Jul 27, 2011 at 14:18, Keith Moore <moore@network-heretics.com>wrote:

> So essentially, the argument that "6to4 damages the Internet", is
> tantamount to "having multiple addresses for hosts damages the Internet".
>
> *And this is an explicitly chosen architectural "feature" of IPv6.*
>

Having multiple addresses for hosts damages the Internet
Multiple addresses for hosts damages the Internet
-> IPv6 damages the Internet

I give up. I wish you a productive discussion from here on.

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

<div class=3D"gmail_quote">On Wed, Jul 27, 2011 at 14:18, Keith Moore <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:moore@network-heretics.com">moore@networ=
k-heretics.com</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;">

<div style=3D"word-wrap:break-word"><div><div><div>So essentially, the argu=
ment that &quot;6to4 damages the Internet&quot;, is tantamount to &quot;hav=
ing multiple addresses for hosts damages the Internet&quot;.</div></div>
</div>
<div><br></div><div><i>And this is an explicitly chosen architectural &quot=
;feature&quot; of IPv6.</i></div></div></blockquote><div><br></div><div>Hav=
ing multiple addresses for hosts damages the Internet</div><div>Multiple ad=
dresses for hosts damages the Internet</div>

<div>-&gt; IPv6 damages the Internet</div><div><br></div><div>I give up. I =
wish you a productive discussion from here on.</div></div>

--000e0cd6aed2c1c31804a9118f79--

From moore@network-heretics.com  Wed Jul 27 12:00: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 3F45C11E8137 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 12:00:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.699
X-Spam-Level: 
X-Spam-Status: No, score=-3.699 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fvNGRpz-oSn0 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 12:00:28 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 4126421F84F3 for <ietf@ietf.org>; Wed, 27 Jul 2011 12:00:28 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 678DA20F8C; Wed, 27 Jul 2011 15:00:20 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Wed, 27 Jul 2011 15:00:20 -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=X0B5j3xT/ftdmhRx2euWt1wPhe4=; b=il 2bpG0flBqThd8j3IjsiMKxxz+k1cFKzUOis95nhmt0269kNOz+Lpx4Tn4Sz1cM97 vm6jOXyZ8ZEM76RWrWbtrbJZkIV4ptziuonnOYExq9/NVkM2iOAIcsGs3af4R3Cq 3HwIm+NZ5FPv0xdR5WP4gyZZ9CejgVcGEfeTHjdP8=
X-Sasl-enc: xL4ZiEnKobH1hpgZlsg+lbze8yPe0IX2aOnMZgO+TIuG 1311793220
Received: from dhcp-12d1.meeting.ietf.org (dhcp-12d1.meeting.ietf.org [130.129.18.209]) by mail.messagingengine.com (Postfix) with ESMTPSA id 3001741404B; Wed, 27 Jul 2011 15:00:20 -0400 (EDT)
Subject: Re: "6to4 damages the Internet" (was Re: draft-ietf-v6ops-6to4-to-historic (yet again))
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: <4E305BFF.7000201@necom830.hpcl.titech.ac.jp>
Date: Wed, 27 Jul 2011 15:00:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <6B2E4316-E56D-497C-91C3-F7A59E1091DC@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <006d01cc4c2f$55e8dd40$4001a8c0@gateway.2wire.net> <A25A544B-DDEA-483B-98B4-8D4C1F8B19A4@network-heretics.com> <4E305BFF.7000201@necom830.hpcl.titech.ac.jp>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
X-Mailer: Apple Mail (2.1084)
Cc: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 19:00:30 -0000

On Jul 27, 2011, at 2:42 PM, Masataka Ohta wrote:

> Keith Moore wrote:
>=20
>>> I see clear evidence that 6to4 is damaging the Internet and although =
there are
>>> those who can use it without causing damage, I believe that the =
principle is
>>> 'First, do no harm'
>=20
>> I put the word "feature" in quotes because this can be a pain in the =
a**=20
>=20
> It means it's IPv6 which is damaging the Internet.

Except that the (v4) Internet is already doing its best to damage =
itself.   So the choice is between a thoroughly brain-damaged v4 =
Internet that is continually getting worse, and a somewhat less =
brain-damaged v6 Internet that has at least some chance of having a few =
things fixed - though all of the existing successful "content" and =
services are optimized for the v4 Internet.

But again, fixing the 6to4 version of this problem is relatively easy, =
and pretty much everybody agrees on mechanisms that will fix the =
problem.  The only disagreement is how to make the message as clear and =
effective as possible, and there are glimmers of hope in that area.

People just shouldn't get lulled into thinking that the problem will go =
away once 6to4 is fixed.

Keith



From rogerj@gmail.com  Wed Jul 27 12:25:05 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 1815121F8BCF; Wed, 27 Jul 2011 12:25:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.224
X-Spam-Level: 
X-Spam-Status: No, score=-3.224 tagged_above=-999 required=5 tests=[AWL=0.075,  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 jwC6qm-OyKxx; Wed, 27 Jul 2011 12:25:03 -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 53B4121F8BD2; Wed, 27 Jul 2011 12:25:03 -0700 (PDT)
Received: by wwe5 with SMTP id 5so1181784wwe.13 for <multiple recipients>; Wed, 27 Jul 2011 12:25:02 -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:content-transfer-encoding; bh=P/7bDl04pRoBQeRZp7YD6rrbbGVQUAOB7E989VcigI8=; b=EcgA0Rv/+n8fBnmVnrhCfNWHA9BdvEnaCA/7vA5AKdFRUo2MAecXc/1buuXqgoWk9s 3tQAshT5qBb3YiVj2wb4vt5YmO30tZ9RyPOBFUuf4QeLg7k0VE79OazUXDxsZOfOOV4H c1NZLpvOh4EGZos2E5v/Gx08pytkWihX3Iwd0=
MIME-Version: 1.0
Received: by 10.227.201.207 with SMTP id fb15mr1237275wbb.113.1311794702049; Wed, 27 Jul 2011 12:25:02 -0700 (PDT)
Received: by 10.227.155.197 with HTTP; Wed, 27 Jul 2011 12:25:01 -0700 (PDT)
In-Reply-To: <CA+OBy1O1ji-ETnAa2oQ8p4OUtd7WjGScyp0xPUTFdm00iaAK=g@mail.gmail.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com> <5A600744-8605-46D3-82B2-C3C30E30E4AC@network-heretics.com> <CA+OBy1O1ji-ETnAa2oQ8p4OUtd7WjGScyp0xPUTFdm00iaAK=g@mail.gmail.com>
Date: Wed, 27 Jul 2011 21:25:01 +0200
Message-ID: <CAKFn1SFSWE2T8u0WC0Vksx1gRkZueU5vrYET=abKMtqOXaMXyQ@mail.gmail.com>
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: "John Mann (ITS)" <john.mann@monash.edu>, Keith Moore <moore@network-heretics.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <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, 27 Jul 2011 19:25:05 -0000

On Wed, Jul 27, 2011 at 3:07 PM, John Mann (ITS) <john.mann@monash.edu> wro=
te:
<snip>
> [ And that native dual-stack is a replacement for both. ]
> We want normal users to move past "experimental IPv6" towards "production
> IPv6".


Exactly, we should focus on doing production IPv6, not wasting our
time on something that run on top of something else, whatever it's
called (are way too many to choice from already and I will recommend
anyone that ask me to never walk down that road, never).




So, can we please stop this never ending SPAMMING with regards to 6to4?

It is a total waste of time, really Keith, please stop. pretty please stop.



--=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 alexandru.petrescu@gmail.com  Wed Jul 27 12:50:31 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 278C811E80F2 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 12:50:31 -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 WWlBCaBJVX0y for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 12:50:30 -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 7390711E8084 for <ietf@ietf.org>; Wed, 27 Jul 2011 12:50:30 -0700 (PDT)
Received: by yxp4 with SMTP id 4so1310752yxp.31 for <ietf@ietf.org>; Wed, 27 Jul 2011 12:50:30 -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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=5yvnBvfy7oi6Edbb5hfPmhLMz2qptR1R+R5Yf4ykejQ=; b=B9WD1tDoORMzJ/eKsJjEmy8QRiacP2elY/VogGFPYRcqmXSBkowkSS++PUwSXT14pc gVTKhrA2+ao/bmhqSoOkghFiC9E8NWzzM2MmRm7joFo+gNUQHzu3U2ULA3bKaRP0ERpY 8M4WUxTsbmHrSyKY7WcMMW8tZG4hDkjuYM9OE=
Received: by 10.142.127.4 with SMTP id z4mr106659wfc.243.1311796229566; Wed, 27 Jul 2011 12:50:29 -0700 (PDT)
Received: from [127.0.0.1] (dhcp-150a.meeting.ietf.org [130.129.21.10]) by mx.google.com with ESMTPS id v17sm110412wfd.5.2011.07.27.12.50.28 (version=SSLv3 cipher=OTHER); Wed, 27 Jul 2011 12:50:29 -0700 (PDT)
Message-ID: <4E306C01.40102@gmail.com>
Date: Wed, 27 Jul 2011 21:50:25 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>	<4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com>	<72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com>	<5A600744-8605-46D3-82B2-C3C30E30E4AC@network-heretics.com>	<CA+OBy1O1ji-ETnAa2oQ8p4OUtd7WjGScyp0xPUTFdm00iaAK=g@mail.gmail.com> <CAKFn1SFSWE2T8u0WC0Vksx1gRkZueU5vrYET=abKMtqOXaMXyQ@mail.gmail.com>
In-Reply-To: <CAKFn1SFSWE2T8u0WC0Vksx1gRkZueU5vrYET=abKMtqOXaMXyQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 19:50:31 -0000

Le 27/07/2011 21:25, Roger Jørgensen a écrit :
> On Wed, Jul 27, 2011 at 3:07 PM, John Mann (ITS)<john.mann@monash.edu>  wrote:
> <snip>
>> [ And that native dual-stack is a replacement for both. ]
>> We want normal users to move past "experimental IPv6" towards "production
>> IPv6".
>
>
> Exactly, we should focus on doing production IPv6, not wasting our
> time on something that run on top of something else, whatever it's
> called (are way too many to choice from already and I will recommend
> anyone that ask me to never walk down that road, never).
>
>
>
>
> So, can we please stop this never ending SPAMMING with regards to 6to4?
>
> It is a total waste of time, really Keith, please stop. pretty please stop.

I believe 6to4 is useful dont make it historic without a clear 
replacement strategy which is backwards compatible with installed base.

open source and no need to fill in forms on web pages.

Alex



From amorris@amsl.com  Wed Jul 27 13:13:00 2011
Return-Path: <amorris@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A15321F8B22 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 13:13:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level: 
X-Spam-Status: No, score=-2.561 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 SSAxwfvdO7sK for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 13:12:59 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:1112:1::14]) by ietfa.amsl.com (Postfix) with ESMTP id BF55F21F8B20 for <ietf@ietf.org>; Wed, 27 Jul 2011 13:12:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id BB0221C381FF for <ietf@ietf.org>; Wed, 27 Jul 2011 13:12:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UOqgzyADAD6j for <ietf@ietf.org>; Wed, 27 Jul 2011 13:12:59 -0700 (PDT)
Received: from dhcp-2311.meeting.ietf.org (dhcp-2311.meeting.ietf.org [130.129.35.17]) by c1a.amsl.com (Postfix) with ESMTPSA id 757781C381FE for <ietf@ietf.org>; Wed, 27 Jul 2011 13:12:59 -0700 (PDT)
Message-Id: <3D658D0E-4958-4AEF-9BD2-447A887EECF1@amsl.com>
From: Alexa Morris <amorris@amsl.com>
To: IETF-Discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Reminder: Remote Participation Support for Admin Plenary Tonight
Date: Wed, 27 Jul 2011 13:12:57 -0700
X-Mailer: Apple Mail (2.936)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 20:13:00 -0000

If you are participating in IETF 81 from outside of Quebec City, this  
is a reminder that Meetecho is providing remote participation support  
for tonight's Administrative Plenary. Starting at 16:20, you can view  
the plenary content here: http://www.meetecho.com/ietf81/adminplenary.

Regards,
Alexa

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

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

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf


From warren@kumari.net  Wed Jul 27 14:17:58 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 25EEB21F8B1B for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 14:17:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wpge6mnQ8ve4 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 14:17:57 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 62C6721F8AFC for <ietf@ietf.org>; Wed, 27 Jul 2011 14:17:57 -0700 (PDT)
Received: from dhcp-227f.meeting.ietf.org (dhcp-227f.meeting.ietf.org [130.129.34.127]) by vimes.kumari.net (Postfix) with ESMTPSA id EEB4E1B416D9; Wed, 27 Jul 2011 17:17:56 -0400 (EDT)
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=windows-1252
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <m2zkk0egxe.wl%randy@psg.com>
Date: Wed, 27 Jul 2011 17:17:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E5FC1E3F-DC1D-41FA-B64B-9BFBFC722E5D@kumari.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D13B@EMBX01-WF.jnpr.net> <m2zkk0egxe.wl%randy@psg.com>
To: Randy Bush <randy@psg.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: Wed, 27 Jul 2011 21:17:58 -0000

Support, A+++, would by from again, etc.

On Jul 26, 2011, at 7:54 PM, Randy Bush wrote:

> i do not care what the draft is called.
> i do not care whether it is info, experimental, or an IEN
> i do care that is says 6to4 MUST be off by default
>=20

Arguing about the label feels like rearranging deckchairs, but if having =
tidy deckchairs is what's needed get 6to4 off by default, so be it=85

W


> randy
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From mohta@necom830.hpcl.titech.ac.jp  Wed Jul 27 14:24:21 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 9AA0A11E8092 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 14:24:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.077
X-Spam-Level: 
X-Spam-Status: No, score=-0.077 tagged_above=-999 required=5 tests=[AWL=0.013,  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 WUEDSg35WEb4 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 14:24:21 -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 C2CF111E8082 for <ietf@ietf.org>; Wed, 27 Jul 2011 14:24:20 -0700 (PDT)
Received: (qmail 32265 invoked from network); 27 Jul 2011 21:44: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; 27 Jul 2011 21:44:18 -0000
Message-ID: <4E308186.9060007@necom830.hpcl.titech.ac.jp>
Date: Thu, 28 Jul 2011 06:22:14 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: "6to4 damages the Internet" (was Re: draft-ietf-v6ops-6to4-to-historic (yet again))
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <006d01cc4c2f$55e8dd40$4001a8c0@gateway.2wire.net> <A25A544B-DDEA-483B-98B4-8D4C1F8B19A4@network-heretics.com> <4E305BFF.7000201@necom830.hpcl.titech.ac.jp> <6B2E4316-E56D-497C-91C3-F7A59E1091DC@network-heretics.com>
In-Reply-To: <6B2E4316-E56D-497C-91C3-F7A59E1091DC@network-heretics.com>
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: Wed, 27 Jul 2011 21:24:21 -0000

Keith Moore wrote:

>> It means it's IPv6 which is damaging the Internet.
> 
> Except that the (v4) Internet is already doing its best to damage
> itself.   So the choice is between a thoroughly brain-damaged
> v4 Internet that is continually getting worse, and a somewhat
> less brain-damaged v6 Internet that has at least some chance
>  of having a few things fixed

You are wrong. While IPv4 is demonstratively usable, IPv6 along
with ND is too bloated that it is totally unusable.

For example, packet too big for multicast PMTUD causes ICMPv6
implosions which may be used for DoS.

While IPv4 guarantees that 516B payload receivable by any host,
IPv6 can't. Because of indefinitely length header options, some
of which (e.g. options for mobility) are inserted without
trasnport/application control, there is no room, not even 1B,
reserved for payload.

And, the worst problem is that 16B address, thanks to poor
estimation of RFC1715, is impossible to remember.

					Masataka Ohta

From brian.e.carpenter@gmail.com  Wed Jul 27 14:43:08 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 BB6DA11E80AB for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 14:43:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.602
X-Spam-Level: 
X-Spam-Status: No, score=-103.602 tagged_above=-999 required=5 tests=[AWL=-0.003, 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 tr25pG3eO1G4 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 14:43:08 -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 0462411E8082 for <ietf@ietf.org>; Wed, 27 Jul 2011 14:43:07 -0700 (PDT)
Received: by iye7 with SMTP id 7so2577195iye.31 for <ietf@ietf.org>; Wed, 27 Jul 2011 14:43:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=3NWDkfmFai9IoHDDzOez0QQpRguuKyIMV8pQyKZRLus=; b=LXQu338WHZPAuUd0Z+wfzUkSJN2SI9nWZu+7NvWucfunxldC/TSd2BDNwwoVzAQxeJ bgDGr2kWEaXDZv53+1c3vcrbW+BsgKoYVbBppm2djzKL6epjrB3e2d1TieHH1I9Hzty2 3p8KxlYAlbMoM6OPtpmGqj0LMELLhDA9I+ZEk=
Received: by 10.43.47.196 with SMTP id ut4mr263462icb.16.1311802987434; Wed, 27 Jul 2011 14:43:07 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id a11sm182531ibg.55.2011.07.27.14.43.05 (version=SSLv3 cipher=OTHER); Wed, 27 Jul 2011 14:43:06 -0700 (PDT)
Message-ID: <4E30865A.2090802@gmail.com>
Date: Thu, 28 Jul 2011 09:42:50 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Alexa Morris <amorris@amsl.com>
Subject: Re: Reminder: Remote Participation Support for Admin Plenary Tonight
References: <3D658D0E-4958-4AEF-9BD2-447A887EECF1@amsl.com>
In-Reply-To: <3D658D0E-4958-4AEF-9BD2-447A887EECF1@amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 21:43:08 -0000

Alexa,

Writing from Auckland NZ, I wish to object to the fact that the regular
audio streaming is not avaialble for the plenaries. It's a signficant
inconvenience.

Meetecho requires login and is picky about browser versions and Java versions,
forced me to blindly accept a security certificate, takes a long time to start
up compared to regular streaming, and the sound quality is definitely worse.

I have no objection to it being run in parallel but please restore the regular
streaming for plenaries.

Regards
   Brian Carpenter

On 2011-07-28 08:12, Alexa Morris wrote:
> If you are participating in IETF 81 from outside of Quebec City, this is
> a reminder that Meetecho is providing remote participation support for
> tonight's Administrative Plenary. Starting at 16:20, you can view the
> plenary content here: http://www.meetecho.com/ietf81/adminplenary.
> 
> Regards,
> Alexa
> 
> -----------
> Alexa Morris / Executive Director / IETF
> 48377 Fremont Blvd., Suite 117, Fremont, CA  94538
> Phone: +1.510.492.4089 / Fax: +1.510.492.4001
> Email: amorris@amsl.com
> 
> Managed by Association Management Solutions (AMS)
> Forum Management, Meeting and Event Planning
> www.amsl.com <http://www.amsl.com/>
> 
> _______________________________________________
> 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 jari.arkko@piuha.net  Wed Jul 27 14:46:28 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 6A34E11E816B for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 14:46:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.442
X-Spam-Level: 
X-Spam-Status: No, score=-102.442 tagged_above=-999 required=5 tests=[AWL=0.157, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zQXbti747RQz for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 14:46:27 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 00D6B11E8160 for <ietf@ietf.org>; Wed, 27 Jul 2011 14:46:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E6F192CEFF for <ietf@ietf.org>; Thu, 28 Jul 2011 00:46:24 +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 Pe2X9ifBqaO2 for <ietf@ietf.org>; Thu, 28 Jul 2011 00:46:24 +0300 (EEST)
Received: from [IPv6:::1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id A053C2CC4B for <ietf@ietf.org>; Thu, 28 Jul 2011 00:46:23 +0300 (EEST)
Message-ID: <4E30872E.1090009@piuha.net>
Date: Wed, 27 Jul 2011 17:46:22 -0400
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: draft-housley-two-maturity-levels
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, 27 Jul 2011 21:46:28 -0000

After extensive discussion on this list and in the IESG Russ has decided 
to make a reduced proposal. I am now initiating a new Last Call to gauge 
consensus on the new version. I believe this version is more focused, 
narrower, and removes many of the parts that people had problems with in 
the previous Last Call. This version certainly does not solve all 
problems in the IETF process, but I at least see this as a small 
positive step.

But this is obviously also a different proposal so discussion is 
required to move forward. I did not think we had consensus to move 
forward with the previous version. I do not yet know if we have 
consensus to move forward with this. But at least the proposal is now 
clearer which should make it possible to get a better view of whether 
the core of Russ' proposal has support to move forward. I certainly hope 
it does.

The proposal still cuts the number of levels to two, and removes the 
yearly review. However, downref changes, motivations related to too much 
scrutiny, discussion of the STD number, etc. are gone. (Many of the 
things taken out of this proposal can be worthwhile topics to pursue, 
but if we take them forward we need to do so separately.)

Here's the link:

  http://tools.ietf.org/html/draft-housley-two-maturity-levels

Diff to the previously last called version:

  
http://tools.ietf.org/rfcdiff?url1=draft-housley-two-maturity-levels-06.txt&url2=draft-housley-two-maturity-levels-08.txt

Jari


From gonzalo.camarillo@ericsson.com  Wed Jul 27 14:48:56 2011
Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8108911E8149 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 14:48:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.605
X-Spam-Level: 
X-Spam-Status: No, score=-106.605 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QexWSAVl0+nW for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 14:48:55 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 5C41D11E80B5 for <ietf@ietf.org>; Wed, 27 Jul 2011 14:48:55 -0700 (PDT)
X-AuditID: c1b4fb39-b7bfdae000005125-36-4e3087c62eda
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 2E.D8.20773.6C7803E4; Wed, 27 Jul 2011 23:48:54 +0200 (CEST)
Received: from [131.160.126.141] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.137.0; Wed, 27 Jul 2011 23:48:53 +0200
Message-ID: <4E3087C4.1000009@ericsson.com>
Date: Wed, 27 Jul 2011 17:48:52 -0400
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Reminder: Remote Participation Support for Admin Plenary Tonight
References: <3D658D0E-4958-4AEF-9BD2-447A887EECF1@amsl.com> <4E30865A.2090802@gmail.com>
In-Reply-To: <4E30865A.2090802@gmail.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 21:48:56 -0000

Hi,

per the discussion in the jabber room, one issue is that the rtsp, sip,
and tel URIs were not available at the ietf page. They should be made
available so that people can use them without accessing the meetecho web
page if they want.

With respect to the audio quality, I have not checked which codecs they use.

Cheers,

Gonzalo


On 27/07/2011 5:42 PM, Brian E Carpenter wrote:
> Alexa,
> 
> Writing from Auckland NZ, I wish to object to the fact that the regular
> audio streaming is not avaialble for the plenaries. It's a signficant
> inconvenience.
> 
> Meetecho requires login and is picky about browser versions and Java versions,
> forced me to blindly accept a security certificate, takes a long time to start
> up compared to regular streaming, and the sound quality is definitely worse.
> 
> I have no objection to it being run in parallel but please restore the regular
> streaming for plenaries.
> 
> Regards
>    Brian Carpenter
> 
> On 2011-07-28 08:12, Alexa Morris wrote:
>> If you are participating in IETF 81 from outside of Quebec City, this is
>> a reminder that Meetecho is providing remote participation support for
>> tonight's Administrative Plenary. Starting at 16:20, you can view the
>> plenary content here: http://www.meetecho.com/ietf81/adminplenary.
>>
>> Regards,
>> Alexa
>>
>> -----------
>> Alexa Morris / Executive Director / IETF
>> 48377 Fremont Blvd., Suite 117, Fremont, CA  94538
>> Phone: +1.510.492.4089 / Fax: +1.510.492.4001
>> Email: amorris@amsl.com
>>
>> Managed by Association Management Solutions (AMS)
>> Forum Management, Meeting and Event Planning
>> www.amsl.com <http://www.amsl.com/>
>>
>> _______________________________________________
>> 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 brian.e.carpenter@gmail.com  Wed Jul 27 14:53:39 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 A7D5D21F8665 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 14:53:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.602
X-Spam-Level: 
X-Spam-Status: No, score=-103.602 tagged_above=-999 required=5 tests=[AWL=-0.003, 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 SNyDWA7P-ny2 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 14:53:39 -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 D5CA621F8661 for <ietf@ietf.org>; Wed, 27 Jul 2011 14:53:38 -0700 (PDT)
Received: by gyd5 with SMTP id 5so1686362gyd.31 for <ietf@ietf.org>; Wed, 27 Jul 2011 14:53:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=Y1so2c12OKUdu7UFyLIISgvIBBnBFiljaebVUW8DAow=; b=SU3/4O9SgPlBVsWaW7Uwc4/8DaHRnEwvt0xQ1VTHvDFy6l0XoG/YeNsBxQTM5U/5va bpnmGiAHRjjaJ9vb5yNkocCHCw01e1VcvPlErcKHqAQU/DwqzYkpiPI1pYO6IYJ5ea7Z ojEgLT9GvI5M4lByT8niHnvbmLlBn48B6KvWA=
Received: by 10.68.46.200 with SMTP id x8mr521611pbm.87.1311803617858; Wed, 27 Jul 2011 14:53:37 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id v2sm49108pbi.35.2011.07.27.14.53.35 (version=SSLv3 cipher=OTHER); Wed, 27 Jul 2011 14:53:37 -0700 (PDT)
Message-ID: <4E3088D0.8080308@gmail.com>
Date: Thu, 28 Jul 2011 09:53:20 +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: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: Reminder: Remote Participation Support for Admin Plenary Tonight
References: <3D658D0E-4958-4AEF-9BD2-447A887EECF1@amsl.com> <4E30865A.2090802@gmail.com> <4E3087C4.1000009@ericsson.com>
In-Reply-To: <4E3087C4.1000009@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 21:53:39 -0000

On 2011-07-28 09:48, Gonzalo Camarillo wrote:
> Hi,
> 
> per the discussion in the jabber room, one issue is that the rtsp, sip,
> and tel URIs were not available at the ietf page. They should be made
> available so that people can use them without accessing the meetecho web
> page if they want.
> 
> With respect to the audio quality, I have not checked which codecs they use.

I don't know about the codecs, but there is a wireless hop. I'm getting
frequent very short drops as well as slightly buzzy sound and less fidelity
than the parallel session streaming. The voices of people I know well are
harder to recognise.

   Brian

> 
> Cheers,
> 
> Gonzalo
> 
> 
> On 27/07/2011 5:42 PM, Brian E Carpenter wrote:
>> Alexa,
>>
>> Writing from Auckland NZ, I wish to object to the fact that the regular
>> audio streaming is not avaialble for the plenaries. It's a signficant
>> inconvenience.
>>
>> Meetecho requires login and is picky about browser versions and Java versions,
>> forced me to blindly accept a security certificate, takes a long time to start
>> up compared to regular streaming, and the sound quality is definitely worse.
>>
>> I have no objection to it being run in parallel but please restore the regular
>> streaming for plenaries.
>>
>> Regards
>>    Brian Carpenter
>>
>> On 2011-07-28 08:12, Alexa Morris wrote:
>>> If you are participating in IETF 81 from outside of Quebec City, this is
>>> a reminder that Meetecho is providing remote participation support for
>>> tonight's Administrative Plenary. Starting at 16:20, you can view the
>>> plenary content here: http://www.meetecho.com/ietf81/adminplenary.
>>>
>>> Regards,
>>> Alexa
>>>
>>> -----------
>>> Alexa Morris / Executive Director / IETF
>>> 48377 Fremont Blvd., Suite 117, Fremont, CA  94538
>>> Phone: +1.510.492.4089 / Fax: +1.510.492.4001
>>> Email: amorris@amsl.com
>>>
>>> Managed by Association Management Solutions (AMS)
>>> Forum Management, Meeting and Event Planning
>>> www.amsl.com <http://www.amsl.com/>
>>>
>>> _______________________________________________
>>> 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 mrex@sap.com  Wed Jul 27 15:00:31 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 73F9611E816D for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 15:00:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.891
X-Spam-Level: 
X-Spam-Status: No, score=-9.891 tagged_above=-999 required=5 tests=[AWL=0.358,  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 S1O88FmIkYOD for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 15:00:31 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id A1E2611E80F5 for <ietf@ietf.org>; Wed, 27 Jul 2011 15:00:30 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p6RM0IkS008497 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 28 Jul 2011 00:00:23 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201107272200.p6RM0GW8013911@fs4113.wdf.sap.corp>
Subject: Re: Reminder: Remote Participation Support for Admin Plenary Tonight
To: brian.e.carpenter@gmail.com (Brian E Carpenter)
Date: Thu, 28 Jul 2011 00:00:16 +0200 (MEST)
In-Reply-To: <4E30865A.2090802@gmail.com> from "Brian E Carpenter" at Jul 28, 11 09:42:50 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: Wed, 27 Jul 2011 22:00:31 -0000

Brian E Carpenter wrote:
> 
> Writing from Auckland NZ, I wish to object to the fact that the regular
> audio streaming is not avaialble for the plenaries. It's a signficant
> inconvenience.

Full ACK.

Although there are rtsp-URLs available for the meetecho audio streams
(which you can only find after logging into Meetecho giving name&EMail),
they're not on the IETF Web site (remote participation), there are
only the Meetecho access URLs listed.

Considering that all regular 8 Audio-Stream _are_still_streaming_
(but they're streaming background noises or after-WG conversations in
the rooms) -- the effort to "fix" the streaming looks like mainly
connecting a cable in the conference hotel.

And the quality of the regular IETF audio streaming is *MUCH* better
than the phone-quality meetecho rtsp stream.

-Martin

From brian.e.carpenter@gmail.com  Wed Jul 27 15:03: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 9C2AD11E80C3 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 15:03:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.602
X-Spam-Level: 
X-Spam-Status: No, score=-103.602 tagged_above=-999 required=5 tests=[AWL=-0.003, 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 AvzZzu9h-1NG for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 15:03:31 -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 E202011E816C for <ietf@ietf.org>; Wed, 27 Jul 2011 15:03:30 -0700 (PDT)
Received: by iye7 with SMTP id 7so2594405iye.31 for <ietf@ietf.org>; Wed, 27 Jul 2011 15:03:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:content-type:content-transfer-encoding; bh=bqobvsF8ra8Y9J4BsZ0wb0/H9HuMALHM2U4eDVNpbbE=; b=npGbvhulXP4kFYVLs0dngzGC6nYNTJfOKzkCJLGI8/DSFlXDfG1z6JDmohWHWsIXip R/IYC8Xa372+hPuRRHRq4lZccxt0RaE/Sbnev0varaKQbCeHrKlrmD4jLA3YHBpp/7Ap sUb2y+DI0s44lKcg7VDUnL2cxPErwhgG8gJqw=
Received: by 10.42.59.144 with SMTP id m16mr244721ich.440.1311804210492; Wed, 27 Jul 2011 15:03:30 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id d8sm388026icy.21.2011.07.27.15.03.28 (version=SSLv3 cipher=OTHER); Wed, 27 Jul 2011 15:03:29 -0700 (PDT)
Message-ID: <4E308B21.1090305@gmail.com>
Date: Thu, 28 Jul 2011 10:03:13 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Kevin's second byte question
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: kfall@cs.Berkeley.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, 27 Jul 2011 22:03:31 -0000

The second byte in an IPv4 header is called the Differentiated Services Field.

Quoting RFC 2474:

2.  Terminology Used in This Document
...
   Differentiated Services Field: the IPv4 header TOS octet or the IPv6
   Traffic Class octet when interpreted in conformance with the
   definition given in this document.  Also DS field.

It's a historical accident that the ECN bits were shoehorned into this octet.

-- 
Regards
   Brian Carpenter



From brian.e.carpenter@gmail.com  Wed Jul 27 15:13: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 2530F11E816F for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 15:13:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.602
X-Spam-Level: 
X-Spam-Status: No, score=-103.602 tagged_above=-999 required=5 tests=[AWL=-0.003, 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 aLZBtM7rV+2C for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 15:13:13 -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 BA66411E816E for <ietf@ietf.org>; Wed, 27 Jul 2011 15:13:12 -0700 (PDT)
Received: by iye7 with SMTP id 7so2602357iye.31 for <ietf@ietf.org>; Wed, 27 Jul 2011 15:13:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=zFsOgXBV0CeFPUuBWHBqXdQydaS14gh9d4klYzLBheM=; b=OzEIGiuFkIAsBcqqaZioiOIVWyaCY9Nd38cgHlq82+eNurnLYQ/qaBY/j3hgE2KRgJ RmYMc1NQGcElCVpdynaWw7kyHrOL8lxiCjnMyeD/0pLVyC0NUbv1qt+8AksFNNuvWk0N pYpiwKS8tPzVPQ9ZJl49r+Z5tQvdmufXvabuE=
Received: by 10.42.152.196 with SMTP id j4mr259568icw.164.1311804790454; Wed, 27 Jul 2011 15:13:10 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id d8sm398208icy.21.2011.07.27.15.13.08 (version=SSLv3 cipher=OTHER); Wed, 27 Jul 2011 15:13:09 -0700 (PDT)
Message-ID: <4E308D64.3030804@gmail.com>
Date: Thu, 28 Jul 2011 10:12:52 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Why the IESG needs to review everything...
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, 27 Jul 2011 22:13:14 -0000

Responding to Glen Zorn's question in plenary:

Firstly, not all ADs review all drafts - that's why you will see
numerous "no objection" or missing ballot responses.

Secondly, the drafts are de facto reviewed by review teams
these days (gen-art, security area, etc.). This serves to alert
the ADs if a draft really needs careful review. The workload is
more reasonable than it used to be.

Thirdly, when I was in the IESG, I was surprised quite often by
*glaring* errors that had not been picked up before. Somebody has
to be responsible for catching these, and today it's the IESG.

Fourthly, because of the exact same discussion that Glen raised in
plenary, the IESG defined and published its criteria for DISCUSS
several years ago. Sometimes there are inappropriate DISCUSSes
and those need to be pointed out when they happen.

I hear the IESG members responding exactly right to this question.

-- 
Regards
   Brian Carpenter



From mcr@sandelman.ca  Wed Jul 27 15:26:30 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 0458E11E8136; Wed, 27 Jul 2011 15:26:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.091
X-Spam-Level: 
X-Spam-Status: No, score=-1.091 tagged_above=-999 required=5 tests=[AWL=0.863,  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 VQlcT6Ejdt3d; Wed, 27 Jul 2011 15:26:29 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 87DA411E8097; Wed, 27 Jul 2011 15:26:29 -0700 (PDT)
Received: from marajade.sandelman.ca (dhcp-174f.meeting.ietf.org [130.129.23.79]) by relay.sandelman.ca (Postfix) with ESMTPS id C6C9934138; Wed, 27 Jul 2011 18:26:07 -0400 (EDT)
Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 8C2AE980EA; Wed, 27 Jul 2011 18:26:43 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: IPv6 Operations <v6ops@ietf.org>, ietf@ietf.org
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
In-Reply-To: <CAKFn1SFSWE2T8u0WC0Vksx1gRkZueU5vrYET=abKMtqOXaMXyQ@mail.gmail.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com> <5A600744-8605-46D3-82B2-C3C30E30E4AC@network-heretics.com> <CA+OBy1O1ji-ETnAa2oQ8p4OUtd7WjGScyp0xPUTFdm00iaAK=g@mail.gmail.com> <CAKFn1SFSWE2T8u0WC0Vksx1gRkZueU5vrYET=abKMtqOXaMXyQ@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: Wed, 27 Jul 2011 18:26:43 -0400
Message-ID: <26682.1311805603@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: Wed, 27 Jul 2011 22:26:30 -0000

>>>>> "Roger" =3D=3D Roger J=F8rgensen <rogerj@gmail.com> writes:
    >> We want normal users to move past "experimental IPv6" towards "produ=
ction
    >> IPv6".


    Roger> Exactly, we should focus on doing production IPv6, not wasting o=
ur
    Roger> time on something that run on top of something else, whatever
    Roger> it's

So, in your opinion, a production host will never have more than
one address?

This is the fundamental problem.  6to4 is just the thing shining the
light on the problem.



From sm@resistor.net  Wed Jul 27 15:28:14 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 9F6ED11E816C for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 15:28:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id naQccJ6Bx1o7 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 15:28:10 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id EBA8411E8097 for <ietf@ietf.org>; Wed, 27 Jul 2011 15:28:09 -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 p6RMS1DW029790;  Wed, 27 Jul 2011 15:28:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1311805683; bh=GFbxJHp3so0H78Eh20d96OuNjxCNK2uC0l2bevLDK6o=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=Z9ZXs4b3cBonFMErLXLi4hTACfkIMTbaCUJSwjg2P4cg5dHx0UPuc/9XiRMvuDq4d q/NgaGRaaPTq5U5IWZrE5cNTFoDs97eZrLlDPZu6wrR6+D1P9+cZeFvc4fWTzYU9ZR GEgLznmpztNs98p6nHb5XNaNzGbAyJ/+YhpGmZ/k=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1311805683; bh=GFbxJHp3so0H78Eh20d96OuNjxCNK2uC0l2bevLDK6o=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=wTVBGJR83uhgUccPsDyTLnGz4lH/6FVAMCSLaRxwDrq1gQ0QGPZKdxhOaL+LujQi1 OADGQzjcISDSsqMntAcAEG083EBP6dd+tD2QbjHGi8FpljzZLwlsN5znh1RJ0os9/G iRu28wsbNsfTXwsk9HGenF2mvsKozn/KSImRlDcs=
Message-Id: <6.2.5.6.2.20110727152126.06e32500@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 27 Jul 2011 15:27:44 -0700
To: Alexa Morris <amorris@amsl.com>
From: SM <sm@resistor.net>
Subject: Re: Reminder: Remote Participation Support for Admin Plenary Tonight
In-Reply-To: <4E30865A.2090802@gmail.com>
References: <3D658D0E-4958-4AEF-9BD2-447A887EECF1@amsl.com> <4E30865A.2090802@gmail.com>
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: Wed, 27 Jul 2011 22:28:14 -0000

Hi Alexa,
At 02:42 PM 7/27/2011, Brian E Carpenter wrote:
>Writing from Auckland NZ, I wish to object to the fact that the regular
>audio streaming is not avaialble for the plenaries. It's a signficant
>inconvenience.

I would like to add my voice to Brian's objection.  Can the usual 
audio stream also be made available for the plenaries?

Regards,
-sm 


From ynir@checkpoint.com  Wed Jul 27 15:30:49 2011
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EB195E8001; Wed, 27 Jul 2011 15:30:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.602
X-Spam-Level: 
X-Spam-Status: No, score=-9.602 tagged_above=-999 required=5 tests=[AWL=-0.806, BAYES_00=-2.599, LONGWORDS=1.803, 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 tQnI8FvuzZ6I; Wed, 27 Jul 2011 15:30:49 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 3B32F5E8004; Wed, 27 Jul 2011 15:30:48 -0700 (PDT)
X-CheckPoint: {4E309F26-2-1B221DC2-FFFF}
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id p6RMUh9w014193;  Thu, 28 Jul 2011 01:30:43 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Thu, 28 Jul 2011 01:30:43 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 28 Jul 2011 01:30:41 +0300
Subject: Re: [IPsec] Last Call: <draft-kivinen-ipsecme-secure-password-framework-01.txt>	(Secure	Password Framework for IKEv2) to Informational RFC
Thread-Topic: [IPsec] Last Call: <draft-kivinen-ipsecme-secure-password-framework-01.txt>	(Secure	Password Framework for IKEv2) to Informational RFC
Thread-Index: AcxMrNHXPdtMuzSzQVqEtsADz3B5Iw==
Message-ID: <7C54FFE2-FFE0-4B4C-BF7E-142A6B10DF6B@checkpoint.com>
References: <20110727164459.29853.48303.idtracker@ietfa.amsl.com>
In-Reply-To: <20110727164459.29853.48303.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IPsecme WG <ipsec@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 22:30:49 -0000

I think this is a terrible idea.=20

IKEv2 has a way for mutual authentication with a shared key.

A concern was raised that this method was vulnerable to guessing if trivial=
 shared keys were configured.

There were several proposals for a better cryptographic method.

The IPsecME working group failed to choose between them. This is not so sur=
prising, because most participants are engineers, not cryptographers. Even =
those with some cryptographic background stayed silent because choosing bet=
ween several cryptographic protocols is hard. IETF last calls and the IESG =
did not help much either.

This draft represents a total shirking of our responsibility. Rather than d=
ecide on one protocol that is "best" or even arbitrarily choosing one that =
is "good enough", it proposes to build a framework so that everyone and the=
ir dog can have their own method. This is a nightmare for developers: since=
 you can't know what method the peer will support, you have to implement al=
l of them.=20

If this had been a hierarchical organization, some manager would decide whi=
ch of the methods gets developed (or published) and the others would be rel=
egated to the recycle bin.

The IETF is not like that and we seek to reach consensus. That's a good thi=
ng, but this time it's leading us to a really bad solution for interoperabi=
lity, and a really bad solution for implementers.=20

I am opposed to this draft.

Yoav

On Jul 27, 2011, at 12:44 PM, The IESG wrote:

>=20
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Secure Password Framework for IKEv2'
>  <draft-kivinen-ipsecme-secure-password-framework-01.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-08-24. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>   This document creates a generic way for Internet Key Exchange (IKEv2)
>   to use any of the symmetric secure password authentication methods.
>   There are multiple methods already specified in other documents and
>   this document does not add new one.  This document specifies a common
>   way so those methods can agree on which method is to be used in
>   current connection.  This document also provides a common way to
>   transmit secure password authentication method specific payloads
>   between peers.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-kivinen-ipsecme-secure-password-fra=
mework/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-kivinen-ipsecme-secure-password-fra=
mework/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.


From dhc2@dcrocker.net  Wed Jul 27 15:35:06 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 4247F11E80A2 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 15:35:06 -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 ov+b05EFJj3K for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 15:35:05 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 33E3D21F865B for <ietf@ietf.org>; Wed, 27 Jul 2011 15:35:05 -0700 (PDT)
Received: from [130.129.85.251] (dhcp-55fb.meeting.ietf.org [130.129.85.251]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p6RMYeEr020445 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Jul 2011 15:34:47 -0700
Message-ID: <4E30927D.50808@dcrocker.net>
Date: Wed, 27 Jul 2011 18:34:37 -0400
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Why the IESG needs to review everything...
References: <4E308D64.3030804@gmail.com>
In-Reply-To: <4E308D64.3030804@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 27 Jul 2011 15:34:47 -0700 (PDT)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 22:35:06 -0000

> Firstly, not all ADs review all drafts - that's why you will see
> numerous "no objection" or missing ballot responses.

Brian,

I've been repeatedly hearing from IESG folk for some year -- and seeing reports 
relating to Nomcom  -- that, in fact, ADs are expected (and maybe required) to 
read every draft.


> Thirdly, when I was in the IESG, I was surprised quite often by
> *glaring* errors that had not been picked up before. Somebody has
> to be responsible for catching these, and today it's the IESG.

Offering no comment on any individuals, but looking at process and structure...

The problem with this sort of datum is that it is entirely out of essential 
context and therefore is not balanced against other factors.

It implies that the considerable cost of the AD review process -- including cost 
to authors, wg chair and shepherds for processing the AD's feedback -- is 
justified by this error-detection benefit.  But it doesn't really try to 
evaluate at relative cost against relative benefit.

Is all of this effort justified if exactly one minor error is found each year? 
Two?  One major?  What is that /actual/ improvement that this process produces? 
  What thresholds should apply?

That is, the presumption in your comment -- and your comment represents a broad 
constituency in the IETF -- is that reviewing only has positive effects of the 
review and it even implies a perfection to the process.

In reality, the current process produces documents with many errors, already. 
The world survives, as does the Internet.

It well might be true that omitting the AD reviews would increase the number. 
By how much?  To what effect?


d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From gonzalo.camarillo@ericsson.com  Wed Jul 27 15:43:14 2011
Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B913C11E80CA for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 15:43:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.605
X-Spam-Level: 
X-Spam-Status: No, score=-106.605 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p5tL+2SR0YWi for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 15:43:14 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id F18E511E8084 for <ietf@ietf.org>; Wed, 27 Jul 2011 15:43:13 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c17ae00000262e-fd-4e30948008f8
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 6E.2A.09774.084903E4; Thu, 28 Jul 2011 00:43:13 +0200 (CEST)
Received: from [131.160.126.141] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.137.0; Thu, 28 Jul 2011 00:43:12 +0200
Message-ID: <4E30947F.1060102@ericsson.com>
Date: Wed, 27 Jul 2011 18:43:11 -0400
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Reminder: Remote Participation Support for Admin Plenary Tonight
References: <3D658D0E-4958-4AEF-9BD2-447A887EECF1@amsl.com> <4E30865A.2090802@gmail.com> <4E3087C4.1000009@ericsson.com> <4E3088D0.8080308@gmail.com>
In-Reply-To: <4E3088D0.8080308@gmail.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 22:43:14 -0000

Hi,

> I don't know about the codecs, but there is a wireless hop. I'm getting
> frequent very short drops as well as slightly buzzy sound and less fidelity
> than the parallel session streaming. The voices of people I know well are
> harder to recognise.

one aspect to consider is that long play-out buffers increase the audio
quality but also increase the delay. Many people have complained about
not being able to effectively participate in the meetings remotely using
the traditional audio streams because of the long delay. On the other
hand, short play-out buffers reduce the delay but can also reduce the
quality under bad network conditions.

As you said, different situations require different services and having
both services available makes sense.

Cheers,

Gonzalo


From marka@isc.org  Wed Jul 27 16:10:36 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 90A4221F8A58; Wed, 27 Jul 2011 16:10:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.564
X-Spam-Level: 
X-Spam-Status: No, score=-2.564 tagged_above=-999 required=5 tests=[AWL=0.035,  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 e1I9Il3rVqBx; Wed, 27 Jul 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 E263A21F8A56; Wed, 27 Jul 2011 16:10:35 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id F3F915F9967; Wed, 27 Jul 2011 23:10: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 E17D4216C85; Wed, 27 Jul 2011 23:09:40 +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 B787612383D5; Thu, 28 Jul 2011 09:09:38 +1000 (EST)
To: Dave Cridland <dave@cridland.net>
From: Mark Andrews <marka@isc.org>
References: <CALiegf=4K2oWfmZjGMD7J_jyaDtS3i+Mu7R0Wh75Rr+MrQCjtw@mail.gmail.com> <20110722054345.GE18126@1wt.eu> <CALiegfnYm6g63JDHLiSH__r-or3kzK0XCVa3cC7RMP14KWBOSg@mail.gmail.com> <20110724120751.GQ22405@1wt.eu> <CALiegfncavmoMp4YDCeeJ3rsOfHAYQ99itKX2Q2eHB351T3X5A@mail.gmail.com> <20110724184537.GZ22405@1wt.eu> <CALiegfne620wuDMAp235n3mVcXTAnbhhNm8vpiNCy5F7+VD92A@mail.gmail.com> <20110724192948.GD22405@1wt.eu> <CALiegf=e48kkF+Gky1mY7LippUB-0kZDgSGZrJxk1aZupAGkYw@mail.gmail.com> <20110727012806.EBB811231907@drugs.dv.isc.org> <20110727052549.GB4086@1wt.eu> <9031.1311786432.357811@puncture>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
In-reply-to: Your message of "Wed, 27 Jul 2011 18:07:12 +0100." <9031.1311786432.357811@puncture>
Date: Thu, 28 Jul 2011 09:09:38 +1000
Message-Id: <20110727230938.B787612383D5@drugs.dv.isc.org>
Cc: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>, Server-Initiated HTTP <hybi@ietf.org>, Willy Tarreau <w@1wt.eu>, 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, 27 Jul 2011 23:10:36 -0000

In message <9031.1311786432.357811@puncture>, Dave Cridland writes:
> On Wed Jul 27 06:25:49 2011, Willy Tarreau wrote:
> > On Wed, Jul 27, 2011 at 11:28:06AM +1000, Mark Andrews wrote:
> > > > SRV provides load-balancing and failover. I never said that SRV  
> > is a
> > > > solution for temporaly put in maintenance a server.
> > >
> > > Happy eyeballs however does allow you to take a server out of  
> > production
> > > and not really notice it.  Note webbrowsers have had the ability  
> > to do
> > > this for as long as webbrowsers have existed.
> > 
> > Mark, could you elaborate on this point ? Surely you're not talking  
> > about
> > the fact that a browser retries a failed connection, but I'm not  
> > not sure
> > what mechanism you're talking about.
> 
> Happy eyeballs - try everything as soon as you can, in parallel. Drop  
> everything else when one does.

More correctly it is try the first address and if that doesn't
connect in a short period (150...250ms) start a second connection
to the next address while continuing with the first.  If you have
more that 2 address you do something similar for the next one (I
use 1/2 the original timeout, but that is a implementation detail).
You continue to use the address that works for that session.  You
drop any other connections to other addresses that complete.

You get fast failover without lots of extra connection attempts
with the advantage that you detect and recover from network failures
that only affect the client.

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  Wed Jul 27 16:13:26 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 33DC621F89B8 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 16:13:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.897
X-Spam-Level: 
X-Spam-Status: No, score=-9.897 tagged_above=-999 required=5 tests=[AWL=0.352,  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 8zjQzDS00w5G for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 16:13:25 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 0238921F87C5 for <ietf@ietf.org>; Wed, 27 Jul 2011 16:13:24 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id p6RNDMkr025137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 28 Jul 2011 01:13:22 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201107272313.p6RNDMX9017678@fs4113.wdf.sap.corp>
Subject: Re: Why the IESG needs to review everything...
To: brian.e.carpenter@gmail.com (Brian E Carpenter)
Date: Thu, 28 Jul 2011 01:13:22 +0200 (MEST)
In-Reply-To: <4E308D64.3030804@gmail.com> from "Brian E Carpenter" at Jul 28, 11 10:12: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: Wed, 27 Jul 2011 23:13:26 -0000

Brian E Carpenter wrote:
> 
> Responding to Glen Zorn's question in plenary:
> 
> Firstly, not all ADs review all drafts - that's why you will see
> numerous "no objection" or missing ballot responses.

I can understand the resource contention when reading drafts
brought to the IESG.  I would not expect that more than 25% of
the IESG members have reviewed a draft (no average) when it is
up for ballot.  But for _standards_action_, I would probably
appreciate if there was a minimum requirement of "yes" ballots
(definitely more than just one) based on independently formed
opinions, which requires some level of review of a document.

According to rfc2026:

   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.  [...]

   4.1.1   Proposed Standard

   [...]
   A Proposed Standard specification is generally stable, has resolved
   known design choices, is believed to be well-understood, has received
   significant community review, and appears to enjoy enough community
   interest to be considered valuable. [...]

While I'm OK seeing just a single "yes" on the IESG ballot for
Informational, I feel quite uncomfortable with a single "yes"
for a standards action.


-Martin

From alexandru.petrescu@gmail.com  Wed Jul 27 16:33:00 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 5DAB811E809C for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 16:33:00 -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 edKhDIN9zRwc for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 16:32:59 -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 931C711E8084 for <ietf@ietf.org>; Wed, 27 Jul 2011 16:32:59 -0700 (PDT)
Received: by qyk9 with SMTP id 9so2768716qyk.10 for <ietf@ietf.org>; Wed, 27 Jul 2011 16:32:59 -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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Ofsei12nwD90KVBr/wfNvrU62KZsLv8PTgyiratVQCM=; b=uOmxZJqqpVRxR47bIxFd89hy0sqXVooWM/b1VN8HnBfL4hKpRytKO6tqq1409p0Gx+ /Sok2QeNXf3x118dvkisZYdsu6+pbO1X44GflQ/GAxta8OTiwAQpRC5PF1I+D/Uu6Tbj Efkgw3KJbhaRAydUzsWvNkpBrYrD/vgWIaX8w=
Received: by 10.224.203.7 with SMTP id fg7mr348092qab.180.1311809577948; Wed, 27 Jul 2011 16:32:57 -0700 (PDT)
Received: from [127.0.0.1] (dhcp-150a.meeting.ietf.org [130.129.21.10]) by mx.google.com with ESMTPS id gx5sm119164qab.7.2011.07.27.16.32.55 (version=SSLv3 cipher=OTHER); Wed, 27 Jul 2011 16:32:56 -0700 (PDT)
Message-ID: <4E30A025.8070209@gmail.com>
Date: Thu, 28 Jul 2011 01:32:53 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<80E059EE-12CD-49D1-8426-2BC74C573108@ecs.soton.ac.uk> <EMEW3|038a96b178501de6df9159a9611a0231n6PFF203tjc|ecs.soton.ac.uk|80E059EE-12CD-49D1-8426-2BC74C573108@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|038a96b178501de6df9159a9611a0231n6PFF203tjc|ecs.soton.ac.uk|80E059EE-12CD-49D1-8426-2BC74C573108@ecs.soton.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 23:33:00 -0000

After reading your text, let me share my experience:

I struggled hard to get a class C w/o NAT.  As hard as that was it was
still easier than obtaining native IPv6.  I wont struggle to get native
ipv6 too.

We use 6to4 on a frontend machine, and we use native IPv6 out of that
6to4 on several subnets behind, hence end machines are native ipv6 if i
can say so.

This is not much for content browsing, but for proudly ping6 an ipv6
node across the globe.

In the past year_s_ we have set up and down several kinds of 6-4 tunnels
manually, brokered, agreed.  We required vendors to include this and
that kind of tunnel in their sw/hw.

We have moved physically and we will move again soon.  We are guaranteed
continuity of this class C no nat, and yet still no IPv6 tunnel up and
downs.  The only thing that was stable during this time was 6to4, and
improved support appeared more and more.

I would also add as information only, that the environment where this
happens, and where i have no control, is where an ethernet seting with
many office-type users, where dhcp is not used, if you can imagine that.
There are many reasons technical and human for that being so.  And
manual assignment (vs dhcp) is not historical - its there in every pc.

Alex

Le 26/07/2011 16:14, Tim Chown a écrit :
>
> On 25 Jul 2011, at 15:30, Ronald Bonica wrote:
>>
>> Please post your views on this course of action by August 8, 2011.
>
> Some observations.
>
> Our own users made use of 6to4 maybe 8+ years ago, and at the time
> it was handy to have.  Today though we're not aware of any of our
> users running 6to4 intentionally. We have IPv6 native on site, and
> anyone who wants home IPv6 connectivity either goes to an ISP that
> provides it, e.g. A&A in the UK, or they use a tunnel broker. Brokers
> have the additional benefit of working through NATs and with dynamic
> IPv4 endpoints.
>
> Our site sees about 1-2% of all inbound traffic being IPv6, and of
> that less than 1% is 6to4, and this is only likely to fall further
> with rfc3484-bis. What 6to4 we do see is probably reasonably robust
> in that our return path uses the JANET-provided 6to4 relay.
>
> Most operating systems either already, or before long will, support
> rfc3484-bis, which means hosts should use IPv4 in preference to 6to4
> where both are available.  To choose to use 6to4, the user would need
> to consciously change their 3484 policy table, assuming their OS
> supports that (Linux and Windows do, MacOS X Lion appears not to).
>
> Geoff Huston has presented data at IETF80 showing 6to4 brokenness
> and performance. We now have 'Happy Eyeballs Lite' implemented in
> Chrome and (I believe, not tested it yet) Firefox, which means the
> browser can adapt to broken IPv6, whether caused by 6to4 or other
> factors.
>
> The 6to4-advisory draft suggests off-by-default, which I agree with,
> and use of relays to improve user experience. The problem is we can't
> expect every site/ISP to run a relay (or multi-address with 6to4) so
> there will inevitably always be problems with the 3068 mode of 6to4.
>
> We measured rogue RAs over a two year period on our wireless
> network. About 60% of the time at least one host was emitting a
> rogue 6to4-based RA. While these were mitigated by ramond, it would
> be good to see vendors fix this; it's not just MS ICS.  Happy
> Eyeballs is a mitigation for such rogue RAs also.
>
> So in summary, in practice 3484-bis and the 6to4-advisory
> off-by-default will further reduce what little use there is of 6to4
> now, and happy eyeballs will mitigate any remaining instances of its
> use that are bad. So whether 6to4 is tagged Historic or not, it
> should be causing significantly less harm.
>
> Tim _______________________________________________ Ietf mailing list
> Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf


From marka@isc.org  Wed Jul 27 16:37:04 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 9ABB711E80D1; Wed, 27 Jul 2011 16:37:04 -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.266, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r9zBQQWuN5Nc; Wed, 27 Jul 2011 16:37:03 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 5546611E8084; Wed, 27 Jul 2011 16:37:02 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id A2A945F995F; Wed, 27 Jul 2011 23:36:38 +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 5FE52216C86; Wed, 27 Jul 2011 23:36:36 +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 406021238970; Thu, 28 Jul 2011 09:36:34 +1000 (EST)
To: Jeroen Massar <jeroen@unfix.org>
From: Mark Andrews <marka@isc.org>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <968F0B1C-D082-4A59-8213-FD58C74AF89D@nominum.com> <20110727151517.CF9371235D70@drugs.dv.isc.org> <D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk> <EMEW3|fcf145b5033ff99790b7c34003f47686n6QGZC03tjc|ecs.soton.ac.uk|D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk> <999C3229-649D-4242-BB0F-2BB494EDF1D9@network-heretics.com> <4E305E3E.2040607@unfix.org>
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
In-reply-to: Your message of "Wed, 27 Jul 2011 20:51:42 +0200." <4E305E3E.2040607@unfix.org>
Date: Thu, 28 Jul 2011 09:36:34 +1000
Message-Id: <20110727233634.406021238970@drugs.dv.isc.org>
Cc: IPv6 Operations <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: Wed, 27 Jul 2011 23:37:04 -0000

In message <4E305E3E.2040607@unfix.org>, Jeroen Massar writes:
> On 2011-07-27 20:21 , Keith Moore wrote:
> > On Jul 27, 2011, at 11:35 AM, Tim Chown wrote:
> > 
> >> I suspect, but have no proof, that the huge majority of 6to4 users don't u
> se it intentionally, and the content they are trying to reach is also availab
> le over IPv4. But for people who want to develop and use new IPv6-specific ap
> ps, then either a broker or something like OpenWRT ought to meet their needs?
> > 
> > tunnel brokers suck if the tunnel endpoint isn't near your current network 
> location.
> 
> Let me rewrite that sentence for you:
> 
>  "transition mechanisms suck if the tunnel endpoint isn't near your
> current network location"
> 
> It does not matter much if that mechanism is static proto-41 (6in4),
> 6to4, AYIYA, TSP, PPTP, HTTP Proxies or whatever, there is going to be a
> bit more latency if they are not directly next to you. Not much you can
> do about except deploy more of them or
> 
> And this will always be the case unless you deploy enough of them in all
> places possible. For SixXS we are at 48 boxes around the world,
> Hurricane has 25 and Gogo6 has 4 of them of their own for Freenet6 and
> then there are 4 others at other organizations and there are a couple of
> other services out there which provide tunnels see:

Is there *one* tunnel management protocol that they all support or
does a cpe vendor have to implement multiple ones to reach them
all?  I'm pretty sure I know the answer to this question but I'd
love to be proved wrong.

One of the advantages of 6to4 anycast is that it is just needs a
check box to turn on and off.  Everybody speaks the same thing.

Another advantage of 6to4 is it doesn't require manual intervention
on renumber events.  Manual tunnel don't pass muster.

Another advantage of 6to4 is you don't have to register.  For most of
the tunnel brokers you have to register.

>  http://en.wikipedia.org/wiki/List_of_IPv6_tunnel_brokers
> 
> > there are currently no universally applicable, or even widely applicable, v
> 6-over-v4 solutions.
> 
> For your set of requirements maybe but especially Tunnel Brokers are
> working very well for a lot of people and if one sees the traffic stats
> on Teredo and 6to4 nodes due to this little thing called NNTP I would
> state that those are doing quite fine too for giving access to what
> people need to get to.
> 
> Your major requirement seems to involve latency though, thus as such,
> there is only one thing to do, get one of those boxes deployed locally
> to your endpoint.
> 
> Do note to yourself that the next issue you will run into that the
> service you are actually contacting will be far away, and you suddenly
> understand that you need that Akamai content box and a Google one and
> various other closeby too ;)
> 
> If you want to solve your problem though, I guess for HE you'll have to
> give them connectivity to their network and space in a rack for a box,
> gogo6 will sell you a box and for SixXS you provide the box+connectivity
> and we'll set up the software for free for you and handle the tunneling
> completely.
> 
> Greets,
>  Jeroen
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
-- 
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 Jul 27 16:51:18 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 044DA21F8A7D; Wed, 27 Jul 2011 16:51:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.902
X-Spam-Level: 
X-Spam-Status: No, score=-9.902 tagged_above=-999 required=5 tests=[AWL=0.347,  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 hwEL2AaTBIoi; Wed, 27 Jul 2011 16:51:17 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 348DD21F8A64; Wed, 27 Jul 2011 16:51:17 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id p6RNoeDx027467 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 28 Jul 2011 01:50:40 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201107272350.p6RNodKa019978@fs4113.wdf.sap.corp>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt>
To: marka@isc.org (Mark Andrews)
Date: Thu, 28 Jul 2011 01:50:39 +0200 (MEST)
In-Reply-To: <20110727230938.B787612383D5@drugs.dv.isc.org> from "Mark Andrews" at Jul 28, 11 09:09:38 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: ibc@aliax.net, hybi@ietf.org, ietf@ietf.org, w@1wt.eu
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, 27 Jul 2011 23:51:18 -0000

Mark Andrews wrote:
> 
> Dave Cridland writes:
> > 
> > Happy eyeballs - try everything as soon as you can, in parallel. Drop  
> > everything else when one does.
> 
> More correctly it is try the first address and if that doesn't
> connect in a short period (150...250ms) start a second connection
> to the next address while continuing with the first.  If you have
> more that 2 address you do something similar for the next one (I
> use 1/2 the original timeout, but that is a implementation detail).
> You continue to use the address that works for that session.  You
> drop any other connections to other addresses that complete.

Happy eyeballs means that a clients reaction to congestion is
to perform an DoS attack, flood the network with additional
connection requests and hammer the server with many additional
half-open connections that will never actually get used.

While this might currently "improve" the end user experience
of clients, it simultaneously adds a deterrant to server operators
to announce IPv6 addresses (even multiple IP addresses -- they're
better of with IPv4 NAT if they have multiple servers at a single
location).

-Martin

From amorris@amsl.com  Wed Jul 27 16:51:25 2011
Return-Path: <amorris@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C63F311E8104 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 16:51:25 -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 QlL6pE0S+WSC for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 16:51:24 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:1112:1::14]) by ietfa.amsl.com (Postfix) with ESMTP id CC88221F8A97 for <ietf@ietf.org>; Wed, 27 Jul 2011 16:51:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 56E0D3A2011; Wed, 27 Jul 2011 16:51:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jGKN5v2lvcsX; Wed, 27 Jul 2011 16:51:23 -0700 (PDT)
Received: from dhcp-4614.meeting.ietf.org (dhcp-4614.meeting.ietf.org [130.129.70.20]) by c1a.amsl.com (Postfix) with ESMTPSA id EBAE63A200E; Wed, 27 Jul 2011 16:51:22 -0700 (PDT)
Message-Id: <0E66E2DF-6381-4014-B1FA-EC33704FA8FF@amsl.com>
From: Alexa Morris <amorris@amsl.com>
To: SM <sm@resistor.net>
In-Reply-To: <6.2.5.6.2.20110727152126.06e32500@resistor.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: Reminder: Remote Participation Support for Admin Plenary Tonight
Date: Wed, 27 Jul 2011 16:51:21 -0700
References: <3D658D0E-4958-4AEF-9BD2-447A887EECF1@amsl.com> <4E30865A.2090802@gmail.com> <6.2.5.6.2.20110727152126.06e32500@resistor.net>
X-Mailer: Apple Mail (2.936)
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 23:51:25 -0000

Brian, SM,

First, I want to reassure you that there is no plan to discontinue the  
regular audio streaming at meetings; indeed, there was every intention  
of providing regular audio streaming for IETF 81, in parallel with the  
support provided by the Meetecho volunteers, but there was some  
miscommunication along the way and, as a result, it was not configured  
as planned. I apologize for that because I now know that I  
inadvertently played a role in that misunderstanding.

Sorry for any inconvenience. Please also understand that the Meetecho  
staff intended to provide additional value, and are in no way  
implicated in this misunderstanding.

Alexa



On Jul 27, 2011, at 3:27 PM, SM wrote:

> Hi Alexa,
> At 02:42 PM 7/27/2011, Brian E Carpenter wrote:
>> Writing from Auckland NZ, I wish to object to the fact that the  
>> regular
>> audio streaming is not avaialble for the plenaries. It's a signficant
>> inconvenience.
>
> I would like to add my voice to Brian's objection.  Can the usual  
> audio stream also be made available for the plenaries?
>
> Regards,
> -sm

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

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


From spromano@unina.it  Wed Jul 27 17:01:14 2011
Return-Path: <spromano@unina.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2988521F8658 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 17:01:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.719
X-Spam-Level: 
X-Spam-Status: No, score=-100.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vLCfmT-BYlRk for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 17:01:13 -0700 (PDT)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by ietfa.amsl.com (Postfix) with ESMTP id 3818621F863E for <ietf@ietf.org>; Wed, 27 Jul 2011 17:01:13 -0700 (PDT)
Received: from [130.129.20.10] (dhcp-140a.meeting.ietf.org [130.129.20.10]) (authenticated bits=0) by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id p6S017a6015833 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 28 Jul 2011 02:01:09 +0200
Message-ID: <4E30A6BE.9000501@unina.it>
Date: Thu, 28 Jul 2011 02:01:02 +0200
From: Simon Pietro Romano <spromano@unina.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; it; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Reminder: Remote Participation Support for Admin Plenary Tonight
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 00:01:14 -0000

Dear all,

as a representative of the Meetecho team, let me jump into this discussion.

First, about the quality of the audio stream. Our system provides two 
different real-time (and when I say "real-time" I mean "real-time") 
streams: the former is a standard VoIP (Asterisk-based) GSM stream; the 
latter is an RTSP G.711 alaw stream. Both of them are not meant for 
high-quality transmission (which, as far as I know, is the objective of 
the classical IETF mp3 streaming based on icecast); they are rather 
meant to provide the participants with a good-enough audio experience. 
With respect to this, I defy anyone who tested Meetecho to demonstrate 
the contrary. The same holds for video, which is a standard H.263 
encoded (and mixed, if needed) stream with either a QCIF or a CIF 
resolution. We do not aim to do HD video or telepresence, or the like.
The point is that Meetecho has been conceived at the outset as a 
real-time collaboration framework; if you ever participated in a virtual 
meeting here at the IETF, you'll have noticed that we provide seamless, 
integrated access to the standard IETF jabber room, to live slide 
presentations (with automated trigger of slide changes on the chat), as 
well as (if needed) to both live video and audio. For this last part 
(access to the audio and video streams) we require people to execute a 
very simple and lightweight applet based on Java Media Framework which 
enables multimedia support. Those who don't want to use the applet  can 
just open they're favourite RTSP player and listen to the available 
audio stream; not to say that those who want to rely on the PSTN, can 
just dial-in through the PSTN bridge. As to the login credentials, the 
only thing we require is that participants insert they're preferred 
username, together with an e-mail address. We create on-the-fly a 
temporary account on our system, which is valid just for the duration of 
the conference and is immediately thereafter destroyed. We do not store 
any information about the users who logged into the system and we are 
not interested at all in using the information they provided for any 
other purpose.

We do believe that the experience we provide (especially to remote 
participants) is an advanced one and does not conflict at all with the 
services that the IETF normally offers to its participants. To have an 
idea of what I'm saying, please have a look at the recordings of the 
sessions we supported, with special regard to today's plenary, available 
at the following site: http://www.meetecho.com/ietf81/recordings. If you 
play it out, you'll also easily acknowledge the fact that the service we 
provide is useful both "during" the sessions and "after" the sessions 
(e.g. for the minutes, or as a reference for those who could not make it 
when the event was scheduled). You'll also recognize that the quality of 
the audio is definitely good. Correct me if I'm wrong.

We are anyhow open to criticisms, especially when they are made with a 
constructive aim.

Best regards,

Simon




> From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
> To: Brian E Carpenter <brian.e.carpenter@gmail.com>
> Reply-to: Gonzalo.Camarillo@ericsson.com
> Subject: Re: Reminder: Remote Participation Support for Admin Plenary 
> Tonight
> X-RSN: 1/0/933/10396/57949
>
> Hi,
>
> > I don't know about the codecs, but there is a wireless hop. I'm getting
> > frequent very short drops as well as slightly buzzy sound and less 
> fidelity
> > than the parallel session streaming. The voices of people I know 
> well are
> > harder to recognise.
>
> one aspect to consider is that long play-out buffers increase the audio
> quality but also increase the delay. Many people have complained about
> not being able to effectively participate in the meetings remotely using
> the traditional audio streams because of the long delay. On the other
> hand, short play-out buffers reduce the delay but can also reduce the
> quality under bad network conditions.
>
> As you said, different situations require different services and having
> both services available makes sense.
>
> Cheers,
>
> Gonzalo
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf 

-- 
                             _\\|//_
                             ( O-O )
    ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                     Simon Pietro Romano
               Universita' di Napoli Federico II
                  Computer Science Department
         Phone: +39 081 7683823 -- Fax: +39 081 7684219
                 e-mail: spromano@unina.it
           http://www.comics.unina.it/simonpietro.romano

     <<Molti mi dicono che lo scoraggiamento è l'alibi degli
    idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
                          oooO
    ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                           \ (    (   )
                            \_)    ) /
                                  (_/



From paul.hoffman@vpnc.org  Wed Jul 27 17:12:54 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 2A73E11E80BF; Wed, 27 Jul 2011 17:12:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.698
X-Spam-Level: 
X-Spam-Status: No, score=-101.698 tagged_above=-999 required=5 tests=[AWL=-0.902, BAYES_00=-2.599, LONGWORDS=1.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 LMdg7fSHOKYO; Wed, 27 Jul 2011 17:12:53 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 3AC7521F8BA1; Wed, 27 Jul 2011 17:12:53 -0700 (PDT)
Received: from dhcp-2121.meeting.ietf.org (dhcp-2121.meeting.ietf.org [130.129.33.33]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p6S0CYeF098610 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 27 Jul 2011 17:12:35 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: [IPsec] Last Call:	<draft-kivinen-ipsecme-secure-password-framework-01.txt>	(Secure	Password Framework for IKEv2) to Informational RFC
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: <7C54FFE2-FFE0-4B4C-BF7E-142A6B10DF6B@checkpoint.com>
Date: Wed, 27 Jul 2011 20:12:49 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <78B594BA-9406-44A2-AB8E-0BF5A425AEC1@vpnc.org>
References: <20110727164459.29853.48303.idtracker@ietfa.amsl.com> <7C54FFE2-FFE0-4B4C-BF7E-142A6B10DF6B@checkpoint.com>
To: IPsecme WG <ipsec@ietf.org>
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, 28 Jul 2011 00:12:54 -0000

<hat location=3D"off">

On Jul 27, 2011, at 6:30 PM, Yoav Nir wrote:

> I think this is a terrible idea.=20

+.5. I think is is a bad idea.

> IKEv2 has a way for mutual authentication with a shared key.
>=20
> A concern was raised that this method was vulnerable to guessing if =
trivial shared keys were configured.
>=20
> There were several proposals for a better cryptographic method.
>=20
> The IPsecME working group failed to choose between them. This is not =
so surprising, because most participants are engineers, not =
cryptographers. Even those with some cryptographic background stayed =
silent because choosing between several cryptographic protocols is hard. =
IETF last calls and the IESG did not help much either.
>=20
> This draft represents a total shirking of our responsibility.

+.5. I think think it represents a shirking of our leadership's =
responsibility. Our leadership said that they would deal with the issue =
if the WG could not come to consensus, and the WG could not come to =
consensus. Adding a layer of indirection that is mostly transparent is =
not dealing with it.

> Rather than decide on one protocol that is "best" or even arbitrarily =
choosing one that is "good enough", it proposes to build a framework so =
that everyone and their dog can have their own method. This is a =
nightmare for developers: since you can't know what method the peer will =
support, you have to implement all of them.=20
>=20
> If this had been a hierarchical organization, some manager would =
decide which of the methods gets developed (or published) and the others =
would be relegated to the recycle bin.
>=20
> The IETF is not like that and we seek to reach consensus. That's a =
good thing, but this time it's leading us to a really bad solution for =
interoperability, and a really bad solution for implementers.=20
>=20
> I am opposed to this draft.

+1


On Jul 27, 2011, at 6:52 PM, Tero Kivinen wrote:

> Yoav Nir writes:
>> This draft represents a total shirking of our responsibility. Rather
>> than decide on one protocol that is "best" or even arbitrarily
>> choosing one that is "good enough", it proposes to build a framework
>> so that everyone and their dog can have their own method. This is a
>> nightmare for developers: since you can't know what method the peer
>> will support, you have to implement all of them. =20
>=20
> Partially yes, but unfortunately all of the authors of those actual
> protocols decided that they wanted to continue publishing those drafts
> as individual RFCs, and each of them used different way to negotiate
> them, so there was no way to even implement multiple of them.

Is this true? Because each has it's own way to negotiate its use, one =
should be able to implement multiple of the competing proposals as-is, =
yes?

> At least this drafts gives you that option to implement multiple of
> them if you want. This draft only provides instructions for those
> other draft authors so they can at least common methods to negotiate
> the feature and use common method to trasmit data between peers.

True, but it is still punting the problem of us having just one.

--Paul Hoffman


From ietf@meetecho.com  Wed Jul 27 17:21:41 2011
Return-Path: <ietf@meetecho.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74ABF21F888A for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 17:21:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.689
X-Spam-Level: 
X-Spam-Status: No, score=-0.689 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ri0GhBjVFaZr for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 17:21:41 -0700 (PDT)
Received: from smtplqs01.aruba.it (smtplqs-out17.aruba.it [62.149.158.57]) by ietfa.amsl.com (Postfix) with SMTP id 33BEA21F8862 for <ietf@ietf.org>; Wed, 27 Jul 2011 17:21:40 -0700 (PDT)
Received: (qmail 4710 invoked by uid 89); 28 Jul 2011 00:21:38 -0000
Received: from unknown (HELO smtpw2.aruba.it) (62.149.128.188) by smtplqs01.aruba.it with SMTP; 28 Jul 2011 00:21:38 -0000
Received: (qmail 31370 invoked by uid 89); 28 Jul 2011 00:21:38 -0000
Received: from unknown (HELO aruba.it) (62.149.158.90) by smtpw2.ad.aruba.it with SMTP; 28 Jul 2011 00:21:38 -0000
Date: Thu, 28 Jul 2011 02:21:38 +0200
Message-Id: <LP0P02$D493780710F49CDD71804B8C8C78FA0C@aruba.it>
Subject: Plenary recordings available
MIME-Version: 1.0
X-Sensitivity: 3
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: "Meetecho IETF support" <ietf@meetecho.com>
To: ietf@ietf.org
X-XaM3-API-Version: V3(R2)
X-SenderIP: 130.129.21.177
X-Spam-Rating: smtpw2.ad.aruba.it 1.6.2 0/1000/N
X-Spam-Rating: smtplqs01.aruba.it 1.6.2 0/1000/N
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 00:21:41 -0000

Dear all,=0A=0Athe full recording (synchronized video, audio, slides and =
jabber room) =0Aof today's Operations and Administration Plenary is avail=
able at the following URL:=0A=0Ahttp://www.meetecho.com/ietf81/recordings=
=0A=0AIn case of problems with the playout, just drop an e-mail to =0Aiet=
f-support@meetecho.com.=0A=0ACheers,=0Athe Meetecho Team


From brian.e.carpenter@gmail.com  Wed Jul 27 17:38:00 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 49BEC11E8120 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 17:38:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.602
X-Spam-Level: 
X-Spam-Status: No, score=-103.602 tagged_above=-999 required=5 tests=[AWL=-0.003, 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 IhXMEY5V6urB for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 17:37:59 -0700 (PDT)
Received: from mail-gw0-f43.google.com (mail-gw0-f43.google.com [74.125.83.43]) by ietfa.amsl.com (Postfix) with ESMTP id BE62A11E807F for <ietf@ietf.org>; Wed, 27 Jul 2011 17:37:59 -0700 (PDT)
Received: by gwm11 with SMTP id 11so2224166gwm.16 for <ietf@ietf.org>; Wed, 27 Jul 2011 17:37:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=fzfp3d4KCeHj6EJWz9pOd+9UsfiOnWOd3e6315ElJoA=; b=f/mesr78KEJO3cYalz6W+1LZmtdr/IlyHWOc7uszMbq/1+hvSl4aQKBheE4Z7T9usW wDbz42LopYTR/nWmJT4pj4rjF5MMSuGbKTEm+AuZxKybnfiRh2X+OYPubxz3ze86A5Nw chyDgWbUSzzvGBdgnb79Tvq7aehZYeYxqsvko=
Received: by 10.42.196.198 with SMTP id eh6mr319137icb.461.1311813479156; Wed, 27 Jul 2011 17:37:59 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id g10sm279374ibe.12.2011.07.27.17.37.56 (version=SSLv3 cipher=OTHER); Wed, 27 Jul 2011 17:37:58 -0700 (PDT)
Message-ID: <4E30AF4E.10407@gmail.com>
Date: Thu, 28 Jul 2011 12:37:34 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: Why the IESG needs to review everything...
References: <201107272313.p6RNDMX9017678@fs4113.wdf.sap.corp>
In-Reply-To: <201107272313.p6RNDMX9017678@fs4113.wdf.sap.corp>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 00:38:00 -0000

On 2011-07-28 11:13, Martin Rex wrote:
> Brian E Carpenter wrote:
>> Responding to Glen Zorn's question in plenary:
>>
>> Firstly, not all ADs review all drafts - that's why you will see
>> numerous "no objection" or missing ballot responses.
> 
> I can understand the resource contention when reading drafts
> brought to the IESG.  I would not expect that more than 25% of
> the IESG members have reviewed a draft (no average) when it is
> up for ballot.  But for _standards_action_, I would probably
> appreciate if there was a minimum requirement of "yes" ballots
> (definitely more than just one) based on independently formed
> opinions, which requires some level of review of a document.

See http://www.ietf.org/iesg/voting-procedures.html

   Brian


From brian.e.carpenter@gmail.com  Wed Jul 27 17:50:49 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 9D82421F874C for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 17:50:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.602
X-Spam-Level: 
X-Spam-Status: No, score=-103.602 tagged_above=-999 required=5 tests=[AWL=-0.003, 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 j0MriY2Qz5o0 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 17:50:49 -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 0414921F86C2 for <ietf@ietf.org>; Wed, 27 Jul 2011 17:50:48 -0700 (PDT)
Received: by iye7 with SMTP id 7so2739542iye.31 for <ietf@ietf.org>; Wed, 27 Jul 2011 17:50:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=vbP6WwuSEw1wFqDG0sCMWfwTA+KZIzjEysWrBt9HQwg=; b=xNkhiIL+Zag9kQCn/5Oodys88EU6V9ABF4wGwMmrxDnY+u40xrEaryf6AGSwWAXl+z nEqivpqSUZwhTwt33p+Ml1SvUOzL3BtQRQLgyezJkQmfCKv26N35xHRqZ1ux9Mu8FvvD MPBAz2G84FXEzRuM1N+kO62RsYEfAEKqzpNI8=
Received: by 10.231.113.17 with SMTP id y17mr300869ibp.108.1311814248636; Wed, 27 Jul 2011 17:50:48 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id 3sm281499ibm.44.2011.07.27.17.50.46 (version=SSLv3 cipher=OTHER); Wed, 27 Jul 2011 17:50:48 -0700 (PDT)
Message-ID: <4E30B250.3030807@gmail.com>
Date: Thu, 28 Jul 2011 12:50:24 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Why the IESG needs to review everything...
References: <4E308D64.3030804@gmail.com> <4E30927D.50808@dcrocker.net>
In-Reply-To: <4E30927D.50808@dcrocker.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 00:50:49 -0000

On 2011-07-28 10:34, Dave CROCKER wrote:
> 
>> Firstly, not all ADs review all drafts - that's why you will see
>> numerous "no objection" or missing ballot responses.
> 
> Brian,
> 
> I've been repeatedly hearing from IESG folk for some year -- and seeing
> reports relating to Nomcom  -- that, in fact, ADs are expected (and
> maybe required) to read every draft.

Expected is one thing; but even the IESG's own rules do not *require* this.
http://www.ietf.org/iesg/voting-procedures.html

I certainly never like ballotting NO OBJECTION unless I had at least
skimmed the draft and read at least one positive review. I'm sure I
never ballotted YES without a careful reading.

...
> 
>> Thirdly, when I was in the IESG, I was surprised quite often by
>> *glaring* errors that had not been picked up before. Somebody has
>> to be responsible for catching these, and today it's the IESG.
> 
...
> Is all of this effort justified if exactly one minor error is found each
> year? Two?  One major?  What is that /actual/ improvement that this
> process produces?  What thresholds should apply?

It depends on what you mean by minor or major, but my experience as an
author is that I get valuable comments from the IESG that definitely
improve the document, even after all the comments one gets from
WGLC and IETF LC and the various review teams.

Why? My guess is that it's because that the buck stops with the IESG - and
that automatically makes people more conscientious. Everybody else can
<shrug>; the final approving body can't.

In other words, if you "fix" this "bug" by moving the final responsibility
elswehere, you will just move the problem to the same place.

> 
> That is, the presumption in your comment -- and your comment represents
> a broad constituency in the IETF -- is that reviewing only has positive
> effects of the review 

Of course, there can be cases where that is not so - in fact, that's
the main reason that the IESG defined the DISCUSS criteria a few years
ago.

> and it even implies a perfection to the process.

Not in my mind.

> In reality, the current process produces documents with many errors,
> already. The world survives, as does the Internet.
> 
> It well might be true that omitting the AD reviews would increase the
> number. By how much?  To what effect?

Hard to tell. But it would amount to giving the IESG secretary a large
rubber stamp *unless* the final responsibility was explicitly moved
elsewhere.

    Brian

From hannes.tschofenig@gmx.net  Wed Jul 27 17:51:15 2011
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00D4D11E80FD for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 17:51:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cCZKY7I9LRhl for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 17:51:14 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id F423011E807F for <ietf@ietf.org>; Wed, 27 Jul 2011 17:51:12 -0700 (PDT)
Received: (qmail invoked by alias); 28 Jul 2011 00:51:11 -0000
Received: from dhcp-172b.meeting.ietf.org (EHLO dhcp-172b.meeting.ietf.org) [130.129.23.43] by mail.gmx.net (mp012) with SMTP; 28 Jul 2011 02:51:11 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+KTo5lqp+KWrh5jnGpNQlJqZ0eohpYxnnL/HvyJa KXX75JcRzbuzW0
Subject: Re: Why the IESG needs to review everything...
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <4E308D64.3030804@gmail.com>
Date: Wed, 27 Jul 2011 20:51:09 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <892B92E8-EC28-44D7-A34F-83299DBC49F8@gmx.net>
References: <4E308D64.3030804@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
X-Y-GMX-Trusted: 0
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 00:51:15 -0000

So, you arguing that all DISCUSSes by ADs are indeed justified and =
necessary.
It is great to hear that our leadership is completely unbiased with =
regard to technology, does not follow their own (or a company) agenda, =
misjudge their expertise in a certain area, showed long delays in =
responding, etc.=20

As a document author I remember a couple of cases where certain ADs =
showed "interesting" behavior.=20

As Jari said at the plenary it is difficult to talk about this topic =
without going into specific cases but on the other hand we don't want to =
upset individuals either.=20
Hence, the story is difficult. =20

My suggestion: Talk to the Nomcom if you think that certain ADs treated =
you in an unfair way.=20

Ciao
Hannes

On Jul 27, 2011, at 6:12 PM, Brian E Carpenter wrote:

> Responding to Glen Zorn's question in plenary:
>=20
> Firstly, not all ADs review all drafts - that's why you will see
> numerous "no objection" or missing ballot responses.
>=20
> Secondly, the drafts are de facto reviewed by review teams
> these days (gen-art, security area, etc.). This serves to alert
> the ADs if a draft really needs careful review. The workload is
> more reasonable than it used to be.
>=20
> Thirdly, when I was in the IESG, I was surprised quite often by
> *glaring* errors that had not been picked up before. Somebody has
> to be responsible for catching these, and today it's the IESG.
>=20
> Fourthly, because of the exact same discussion that Glen raised in
> plenary, the IESG defined and published its criteria for DISCUSS
> several years ago. Sometimes there are inappropriate DISCUSSes
> and those need to be pointed out when they happen.
>=20
> I hear the IESG members responding exactly right to this question.
>=20
> --=20
> Regards
>   Brian Carpenter
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From brian.e.carpenter@gmail.com  Wed Jul 27 17:54:16 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 A76CB11E80DF for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 17:54:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.602
X-Spam-Level: 
X-Spam-Status: No, score=-103.602 tagged_above=-999 required=5 tests=[AWL=-0.003, 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 zdLdcHPSORBN for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 17:54:16 -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 DF8DE11E807F for <ietf@ietf.org>; Wed, 27 Jul 2011 17:54:15 -0700 (PDT)
Received: by iye7 with SMTP id 7so2742490iye.31 for <ietf@ietf.org>; Wed, 27 Jul 2011 17:54:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=7kjdmF0y2WvKkgCGn1NNi8IgdRgeXNNAjlMNPsLSZjA=; b=U1SBTk5tz9s9Fr0Hx+mKFjFn1/Pr0rvg3gdFenuez1H9nkUYOjPQURIdnhsEV7XlDR cRXQkFrNcRNZmW4LySAxrDPFEQkKU4yFPsU42i6mXSHmQT0RLSy8j+8uFD8zVKuIjMqC r0TaTViJ5i4v4DPl2etGh25Xjlm+yuz+/c6zc=
Received: by 10.42.77.3 with SMTP id g3mr338419ick.434.1311814453624; Wed, 27 Jul 2011 17:54:13 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id s2sm582182icw.5.2011.07.27.17.54.11 (version=SSLv3 cipher=OTHER); Wed, 27 Jul 2011 17:54:13 -0700 (PDT)
Message-ID: <4E30B31C.6070701@gmail.com>
Date: Thu, 28 Jul 2011 12:53:48 +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: Alexa Morris <amorris@amsl.com>
Subject: Re: Reminder: Remote Participation Support for Admin Plenary Tonight
References: <3D658D0E-4958-4AEF-9BD2-447A887EECF1@amsl.com>	<4E30865A.2090802@gmail.com>	<6.2.5.6.2.20110727152126.06e32500@resistor.net> <0E66E2DF-6381-4014-B1FA-EC33704FA8FF@amsl.com>
In-Reply-To: <0E66E2DF-6381-4014-B1FA-EC33704FA8FF@amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 00:54:16 -0000

Thanks Alexa!

And certainly the Meetecho service has its value - although those of us
on the end of a very long, thin glass fibre in the South Pacific may
not be able to get the full benefit.

Regards
   Brian Carpenter

On 2011-07-28 11:51, Alexa Morris wrote:
> Brian, SM,
> 
> First, I want to reassure you that there is no plan to discontinue the
> regular audio streaming at meetings; indeed, there was every intention
> of providing regular audio streaming for IETF 81, in parallel with the
> support provided by the Meetecho volunteers, but there was some
> miscommunication along the way and, as a result, it was not configured
> as planned. I apologize for that because I now know that I inadvertently
> played a role in that misunderstanding.
> 
> Sorry for any inconvenience. Please also understand that the Meetecho
> staff intended to provide additional value, and are in no way implicated
> in this misunderstanding.
> 
> Alexa
> 
> 
> 
> On Jul 27, 2011, at 3:27 PM, SM wrote:
> 
>> Hi Alexa,
>> At 02:42 PM 7/27/2011, Brian E Carpenter wrote:
>>> Writing from Auckland NZ, I wish to object to the fact that the regular
>>> audio streaming is not avaialble for the plenaries. It's a signficant
>>> inconvenience.
>>
>> I would like to add my voice to Brian's objection.  Can the usual
>> audio stream also be made available for the plenaries?
>>
>> Regards,
>> -sm
> 
> -----------
> Alexa Morris / Executive Director / IETF
> 48377 Fremont Blvd., Suite 117, Fremont, CA  94538
> Phone: +1.510.492.4089 / Fax: +1.510.492.4001
> Email: amorris@amsl.com
> 
> Managed by Association Management Solutions (AMS)
> Forum Management, Meeting and Event Planning
> www.amsl.com <http://www.amsl.com/>
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 

From brian.e.carpenter@gmail.com  Wed Jul 27 18:14:03 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 415C021F8BEF for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 18:14:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.602
X-Spam-Level: 
X-Spam-Status: No, score=-103.602 tagged_above=-999 required=5 tests=[AWL=-0.003, 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 3rAtKhEJdk18 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 18:14:02 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id 9330F21F8BED for <ietf@ietf.org>; Wed, 27 Jul 2011 18:14:02 -0700 (PDT)
Received: by qyk29 with SMTP id 29so1392245qyk.10 for <ietf@ietf.org>; Wed, 27 Jul 2011 18:14:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=4iIzTLHCx5LA3mArNkV2jpSG7NFt1F0sS4jcTtzMczc=; b=wyGOj6Ag1ZcajCnVLE8bQkH0rBognxzFnKluqiohINQXn2fT+QxmPAX5Q8j/y9vNVh DqZyPs8Ked+W2EOhgWbxLcM06HqWV3J3IYMPLL+Ro2VLkmSYOnVeA0JxCSsvjiXscfss 4+Vvd6BrqaGpFMVsF7p95iJ1ekyiVxkT5RV1E=
Received: by 10.229.237.129 with SMTP id ko1mr403123qcb.16.1311815641932; Wed, 27 Jul 2011 18:14:01 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id q9sm355313qct.20.2011.07.27.18.14.00 (version=SSLv3 cipher=OTHER); Wed, 27 Jul 2011 18:14:01 -0700 (PDT)
Message-ID: <4E30B7C0.5010706@gmail.com>
Date: Thu, 28 Jul 2011 13:13:36 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Subject: Re: Why the IESG needs to review everything...
References: <4E308D64.3030804@gmail.com> <892B92E8-EC28-44D7-A34F-83299DBC49F8@gmx.net>
In-Reply-To: <892B92E8-EC28-44D7-A34F-83299DBC49F8@gmx.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 01:14:03 -0000

On 2011-07-28 12:51, Hannes Tschofenig wrote:
> So, you arguing that all DISCUSSes by ADs are indeed justified and necessary.

No. I said exactly the opposite: "Sometimes there are inappropriate DISCUSSes
and those need to be pointed out when they happen."

> It is great to hear that our leadership 

They are not our leadership; they are members of our community performing
a service role for the rest of us.

> is completely unbiased with regard to technology, 

I didn't say that; they are human.

> does not follow their own (or a company) agenda, 

I didn't say that. In my experience this is pretty rare in IESG discussions,
compared to the blatant company position-pushing I have often seen in
WG discussions. But again, they are human. That's why part of the NomCom's
job is balancing the membership as much as possible.

> misjudge their expertise in a certain area, 

I didn't say that; they are human.

> showed long delays in responding, 

I didn't say that; they are human.

> etc. 
> 
> As a document author I remember a couple of cases where certain ADs showed "interesting" behavior. 

So do I. But your name is on 44 RFCs - a couple of cases is not really surprising.

> As Jari said at the plenary it is difficult to talk about this topic without going into specific cases but on the other hand we don't want to upset individuals either. 
> Hence, the story is difficult.  
> 
> My suggestion: Talk to the Nomcom if you think that certain ADs treated you in an unfair way. 

Absolutely agreed. The NomCom needs an overview of this.

   Brian

> Ciao
> Hannes
> 
> On Jul 27, 2011, at 6:12 PM, Brian E Carpenter wrote:
> 
>> Responding to Glen Zorn's question in plenary:
>>
>> Firstly, not all ADs review all drafts - that's why you will see
>> numerous "no objection" or missing ballot responses.
>>
>> Secondly, the drafts are de facto reviewed by review teams
>> these days (gen-art, security area, etc.). This serves to alert
>> the ADs if a draft really needs careful review. The workload is
>> more reasonable than it used to be.
>>
>> Thirdly, when I was in the IESG, I was surprised quite often by
>> *glaring* errors that had not been picked up before. Somebody has
>> to be responsible for catching these, and today it's the IESG.
>>
>> Fourthly, because of the exact same discussion that Glen raised in
>> plenary, the IESG defined and published its criteria for DISCUSS
>> several years ago. Sometimes there are inappropriate DISCUSSes
>> and those need to be pointed out when they happen.
>>
>> I hear the IESG members responding exactly right to this question.
>>
>> -- 
>> Regards
>>   Brian Carpenter
>>
>>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
> 
> 

From hannes.tschofenig@gmx.net  Wed Jul 27 18:24:52 2011
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5372111E80C2 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 18:24:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 NpKlL5VVKqVy for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 18:24:51 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 6651511E80B9 for <ietf@ietf.org>; Wed, 27 Jul 2011 18:24:51 -0700 (PDT)
Received: (qmail invoked by alias); 28 Jul 2011 01:24:49 -0000
Received: from dhcp-172b.meeting.ietf.org (EHLO dhcp-172b.meeting.ietf.org) [130.129.23.43] by mail.gmx.net (mp067) with SMTP; 28 Jul 2011 03:24:49 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+0YfU4dCq0OTcewH/fed0txBNPaa8WK/mespCgCV 2DHILd+mJxZagT
Subject: Re: Why the IESG needs to review everything...
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <4E30B7C0.5010706@gmail.com>
Date: Wed, 27 Jul 2011 21:24:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2F337A18-1D18-4F8C-8418-3EEB67EFF4AD@gmx.net>
References: <4E308D64.3030804@gmail.com> <892B92E8-EC28-44D7-A34F-83299DBC49F8@gmx.net> <4E30B7C0.5010706@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
X-Y-GMX-Trusted: 0
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 01:24:52 -0000

I believe we agree.=20

On Jul 27, 2011, at 9:13 PM, Brian E Carpenter wrote:

>> My suggestion: Talk to the Nomcom if you think that certain ADs =
treated you in an unfair way.=20
>=20
> Absolutely agreed. The NomCom needs an overview of this.



From mrex@sap.com  Wed Jul 27 18:49:44 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 E0F5111E80B9 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 18:49:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.907
X-Spam-Level: 
X-Spam-Status: No, score=-9.907 tagged_above=-999 required=5 tests=[AWL=0.342,  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 CcABphilgkM8 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 18:49:44 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 272B211E8084 for <ietf@ietf.org>; Wed, 27 Jul 2011 18:49:43 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p6S1ndKT018408 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 28 Jul 2011 03:49:39 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201107280149.p6S1ncAS026882@fs4113.wdf.sap.corp>
Subject: Re: Reminder: Remote Participation Support for Admin Plenary Tonight
To: brian.e.carpenter@gmail.com (Brian E Carpenter)
Date: Thu, 28 Jul 2011 03:49:38 +0200 (MEST)
In-Reply-To: <4E30B31C.6070701@gmail.com> from "Brian E Carpenter" at Jul 28, 11 12:53:48 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, 28 Jul 2011 01:49:45 -0000

Brian E Carpenter wrote:
> 
> And certainly the Meetecho service has its value - although those of us
> on the end of a very long, thin glass fibre in the South Pacific may
> not be able to get the full benefit.

Admittedly there was an improvement to previous IETFs.

Running Meetecho in a virtual machine with a Linux Live CD
(for the visual part) worked OK, and one single solution provided
access to slides of all presentations at the right time.

In all previous IETFs, only a fraction of the presentations were
available on the datatracker just prior or during the plenary,
and there was a significantly annoying lack of standardized format
(like 2007+ PPT, for which _my_ virtualization approach doesn't work).

-Martin

From brian.e.carpenter@gmail.com  Wed Jul 27 18:54:37 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 128B921F8B7E for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 18:54:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.602
X-Spam-Level: 
X-Spam-Status: No, score=-103.602 tagged_above=-999 required=5 tests=[AWL=-0.003, 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 2H3bx2yUPIxZ for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 18:54:36 -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 7C10921F8B7A for <ietf@ietf.org>; Wed, 27 Jul 2011 18:54:36 -0700 (PDT)
Received: by vxi40 with SMTP id 40so2011852vxi.31 for <ietf@ietf.org>; Wed, 27 Jul 2011 18:54:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=LNZ2toSVoqmdnRGHDEOG1T/znloF66VOVz1qeB7JS7s=; b=I4cKP2LYI2/cRSSiGyC06Lg/7zmqZO++wGwbkJ+/sjLjtKmq0Xn8QYcbr87H9W6GXa wjnUD2dzZg6OWTLRns976Flr37Y/DTNlXfYSHWowG+jG0jzl7GX5+hJSJ8pkkHuGC7dN 9goiaAO+Q/ay1LOCch8AAWaqrJLnAmx+vj2Pk=
Received: by 10.52.24.145 with SMTP id u17mr597182vdf.48.1311818075830; Wed, 27 Jul 2011 18:54:35 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id z9sm161733vco.14.2011.07.27.18.54.34 (version=SSLv3 cipher=OTHER); Wed, 27 Jul 2011 18:54:35 -0700 (PDT)
Message-ID: <4E30C158.5000500@gmail.com>
Date: Thu, 28 Jul 2011 13:54:32 +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: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: draft-housley-two-maturity-levels
References: <4E30872E.1090009@piuha.net>
In-Reply-To: <4E30872E.1090009@piuha.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: Thu, 28 Jul 2011 01:54:37 -0000

On 2011-07-28 09:46, Jari Arkko wrote:
> After extensive discussion on this list and in the IESG Russ has decided
> to make a reduced proposal. I am now initiating a new Last Call to gauge
> consensus on the new version. 

Thankyou. I fully support this version.

  Brian Carpenter

From jhw@apple.com  Wed Jul 27 18:57:17 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 6DE0521F8B8A; Wed, 27 Jul 2011 18:57:17 -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 sbJqrt8lUv+V; Wed, 27 Jul 2011 18:57:16 -0700 (PDT)
Received: from mail-out.apple.com (crispin.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 8CFAD21F8B89; Wed, 27 Jul 2011 18:57:16 -0700 (PDT)
MIME-version: 1.0
Content-type: text/plain; charset=windows-1252
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 <0LP000106TF298T1@mail-out.apple.com>; Wed, 27 Jul 2011 18:57:06 -0700 (PDT)
X-AuditID: 11807130-b7c45ae000001381-d1-4e30c1a7b6b6
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 D7.F3.04993.7A1C03E4; Wed, 27 Jul 2011 18:55:51 -0700 (PDT)
Received: from [10.0.1.2] (unknown [207.96.251.20]) by koseret.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LP000M43TEUR440@koseret.apple.com>; Wed, 27 Jul 2011 18:57:06 -0700 (PDT)
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
From: james woodyatt <jhw@apple.com>
In-reply-to: <m1QlzXt-0001gSC@stereo.hq.phicoh.net>
Date: Wed, 27 Jul 2011 21:56:51 -0400
Content-transfer-encoding: quoted-printable
Message-id: <2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <m1QlzXt-0001gSC@stereo.hq.phicoh.net>
To: Philip Homburg <pch-v6ops@u-1.phicoh.com>
X-Mailer: Apple Mail (2.1244.3)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrFLMWRmVeSWpSXmKPExsUiON1OXXf5QQM/gz9z5S2ebZzPYnH62F5m ByaPJUt+MgUwRnHZpKTmZJalFunbJXBlfLn2kbHgOkfFoyV3mRoY/7N1MXJySAiYSDzb1cIC YYtJXLi3HijOxSEk0MkkMelTHztIgldAUOLH5HtARRwczAJ6EvcvakHUNDFJLFs3lxWkRlhA S6Lj/X6wejYBFYlvl+8ygdRzChhLTHkMNp9FQFXi1KspYHuZBQIkbpzczghha0s8eXeBFWKV jcS1W/PZIebfZZLYcv0ZWEJEQFfizc1pzBCHykssbvnMOIFRYBaS82YhnDcLydgFjMyrGAWL UnMSKw0N9RILCnJS9ZLzczcxgkKwodBgB+Pan/yHGAU4GJV4eBfoGPgJsSaWFVfmHmKU4GBW EuG9JAcU4k1JrKxKLcqPLyrNSS0+xCjNwaIkzpv9Q9VPSCA9sSQ1OzW1ILUIJsvEwSnVwHhs v9zPRgvfC1OU/r2YoHtwpq/GcvNI7kdf1wavfPghl1NMJ2Oh/kSLwIaMh1XGS/77ZnYUmL+o 1v51r2ytOvO7wJlh4p7P6sz/bKz+PfPRbXuLJ48eXw/n/Ch0Ifr4bIEXzBeWisarvRXe8u3+ vRns6ysb4pVWTZaWDFCTKcktuPVb7U7F9l1KLMUZiYZazEXFiQBqAYt8PQIAAA==
Cc: IPv6 Operations <v6ops@ietf.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 01:57:17 -0000

On Jul 27, 2011, at 4:32 AM, Philip Homburg wrote:
>=20
> So I think it would be quite weird to keep 6to4 at standards track =
just to prevent some vendors from dropping 6to4 support.=20

As one of those implementers-- as in, it will probably be *my* commit to =
the repository that does "rm $XNU/bsd/net/if_stf.c"=97- I now feel =
compelled to reiterate that I would prefer a more controlled phase-out =
plan than, "equipment vendors and operators are free to commence the =
destruction of 6to4 at their individual convenience and without further =
warning to the user community."

In the absence of a coherent instruction from IETF for a phase-out plan, =
declaring this protocol historic under the current proposed language, =
will do precisely that.  Please please please, if IETF wants 6to4 to =
die, then publish a phase-out plan so that the current users of 6to4 can =
have fair warning before the relays go dark and forthcoming =
hardware/software upgrades rip the feature out from under them.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking



From marka@isc.org  Wed Jul 27 19:02:07 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 608D611E809F; Wed, 27 Jul 2011 19:02:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.56
X-Spam-Level: 
X-Spam-Status: No, score=-2.56 tagged_above=-999 required=5 tests=[AWL=0.039,  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 Yx9PBQWwDkqi; Wed, 27 Jul 2011 19:02:06 -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 71DB511E808E; Wed, 27 Jul 2011 19:02:06 -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 54AFA5F98F1; Thu, 28 Jul 2011 02:01:53 +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 0E9F5216C80; Thu, 28 Jul 2011 02:01:21 +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 647E1123AED8; Thu, 28 Jul 2011 12:01:18 +1000 (EST)
To: mrex@sap.com
From: Mark Andrews <marka@isc.org>
References: <201107272350.p6RNodKa019978@fs4113.wdf.sap.corp>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt>
In-reply-to: Your message of "Thu, 28 Jul 2011 01:50:39 +0200." <201107272350.p6RNodKa019978@fs4113.wdf.sap.corp>
Date: Thu, 28 Jul 2011 12:01:18 +1000
Message-Id: <20110728020118.647E1123AED8@drugs.dv.isc.org>
Cc: ibc@aliax.net, hybi@ietf.org, ietf@ietf.org, w@1wt.eu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 02:02:07 -0000

In message <201107272350.p6RNodKa019978@fs4113.wdf.sap.corp>, Martin Rex writes
:
> Mark Andrews wrote:
> > 
> > Dave Cridland writes:
> > > 
> > > Happy eyeballs - try everything as soon as you can, in parallel. Drop  
> > > everything else when one does.
> > 
> > More correctly it is try the first address and if that doesn't
> > connect in a short period (150...250ms) start a second connection
> > to the next address while continuing with the first.  If you have
> > more that 2 address you do something similar for the next one (I
> > use 1/2 the original timeout, but that is a implementation detail).
> > You continue to use the address that works for that session.  You
> > drop any other connections to other addresses that complete.
> 
> Happy eyeballs means that a clients reaction to congestion is
> to perform an DoS attack, flood the network with additional
> connection requests and hammer the server with many additional
> half-open connections that will never actually get used.

It is not a DoS attack.  The client is almost certainly going to
make those connection attempts anyway if the path is congested
enough to cause the first connection attempt to fail.  The only
difference is the application gives up in 30 seconds rather than
60 or 90 seconds by doing the attempts serially.

> While this might currently "improve" the end user experience
> of clients, it simultaneously adds a deterrant to server operators
> to announce IPv6 addresses (even multiple IP addresses -- they're
> better of with IPv4 NAT if they have multiple servers at a single
> location).
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From mcr@sandelman.ca  Wed Jul 27 19:18:37 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 1A35611E814E for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 19:18:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.142
X-Spam-Level: 
X-Spam-Status: No, score=-1.142 tagged_above=-999 required=5 tests=[AWL=0.812,  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 cc14d4uq-yVJ for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 19:18:36 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 8284D11E8149 for <ietf@ietf.org>; Wed, 27 Jul 2011 19:18:36 -0700 (PDT)
Received: from marajade.sandelman.ca (dhcp-174f.meeting.ietf.org [130.129.23.79]) by relay.sandelman.ca (Postfix) with ESMTPS id 3CEA63412E; Wed, 27 Jul 2011 22:18:15 -0400 (EDT)
Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 0B2EF980EA; Wed, 27 Jul 2011 22:18:51 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: ietf@ietf.org
Subject: Re: draft-ietf-v6ops-6to4-to-historic (yet again)
In-Reply-To: <E5FC1E3F-DC1D-41FA-B64B-9BFBFC722E5D@kumari.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D13B@EMBX01-WF.jnpr.net> <m2zkk0egxe.wl%randy@psg.com> <E5FC1E3F-DC1D-41FA-B64B-9BFBFC722E5D@kumari.net>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Wed, 27 Jul 2011 22:18:51 -0400
Message-ID: <32094.1311819531@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: Thu, 28 Jul 2011 02:18:37 -0000

At dinner today it was suggested that the right course of action is:
   leave rfc3056 (6to4) as it is.
   mark rfc3068-only (anycast) as historic.

It is the availability of anycast that permits 6to4 to be on by default.
Turn off the anycast, and now 6to4 is simply a useful tool for people
who know it's limitations to use. 

-- 
]       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 prvs=0190f2f5dc=medel@globetel.com.ph  Wed Jul 27 19:29:52 2011
Return-Path: <prvs=0190f2f5dc=medel@globetel.com.ph>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2425611E8129 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 19:29:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.372
X-Spam-Level: 
X-Spam-Status: No, score=-1.372 tagged_above=-999 required=5 tests=[AWL=0.233,  BAYES_00=-2.599, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MaKdBm1gcpjV for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 19:29:51 -0700 (PDT)
Received: from smtp01.globetel.com.ph (smtp01.globetel.com.ph [203.177.192.181]) by ietfa.amsl.com (Postfix) with ESMTP id 6F36311E807F for <ietf@ietf.org>; Wed, 27 Jul 2011 19:29:51 -0700 (PDT)
Received: from exgtbh01.globetel.com ([10.225.208.17]) by smtp01.globetel.com.ph (8.14.4/8.14.4) with ESMTP id p6S2T8ck021125;  Thu, 28 Jul 2011 10:29:25 +0800
Received: from EXVSGT02.globetel.com ([10.225.208.145]) by exgtbh01.globetel.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 28 Jul 2011 10:29:40 +0800
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: Why the IESG needs to review everything...
Date: Thu, 28 Jul 2011 10:29:39 +0800
Message-ID: <A5AD67DA1ACB9648831FD753485B2BFE11E5E72C@EXVSGT02.globetel.com>
In-Reply-To: <2F337A18-1D18-4F8C-8418-3EEB67EFF4AD@gmx.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Why the IESG needs to review everything...
Thread-Index: AcxMxTRWUxyJyjxWQkO02NY7w3cdhgACPFZQ
X-Priority: 1
Priority: Urgent
Importance: high
References: <4E308D64.3030804@gmail.com><892B92E8-EC28-44D7-A34F-83299DBC49F8@gmx.net><4E30B7C0.5010706@gmail.com> <2F337A18-1D18-4F8C-8418-3EEB67EFF4AD@gmx.net>
From: "GT RAMIREZ, Medel G." <medel@globetel.com.ph>
To: "Hannes Tschofenig" <hannes.tschofenig@gmx.net>, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
X-OriginalArrivalTime: 28 Jul 2011 02:29:40.0082 (UTC) FILETIME=[33AC8520:01CC4CCE]
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.4.6813, 1.0.211, 0.0.0000 definitions=2011-07-27_06:2011-07-27, 2011-07-27, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1012030000 definitions=main-1107270264
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, 28 Jul 2011 02:29:52 -0000

Likewise...

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Hannes Tschofenig
Sent: Thursday, July 28, 2011 9:25 AM
To: Brian E Carpenter
Cc: IETF discussion list
Subject: Re: Why the IESG needs to review everything...

I believe we agree.=20

On Jul 27, 2011, at 9:13 PM, Brian E Carpenter wrote:

>> My suggestion: Talk to the Nomcom if you think that certain ADs
treated you in an unfair way.=20
>=20
> Absolutely agreed. The NomCom needs an overview of this.


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

This e-mail message (including attachments, if any) is intended for the use=
 of the individual or the entity to whom it is addressed and may contain in=
formation that is privileged, proprietary, confidential and exempt from dis=
closure. If you are not the intended recipient, you are notified that any d=
issemination, distribution or copying of this communication is strictly pro=
hibited. If you have received this communication in error, please notify th=
e sender and delete this E-mail message immediately.

From michel@arneill-py.sacramento.ca.us  Wed Jul 27 20:12:45 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 C6F5D21F8C03 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 20:12:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.041
X-Spam-Level: 
X-Spam-Status: No, score=-2.041 tagged_above=-999 required=5 tests=[AWL=0.224,  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 0AErpdbdT0eC for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 20:12:45 -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 14AB021F8C02 for <ietf@ietf.org>; Wed, 27 Jul 2011 20:12:45 -0700 (PDT)
Subject: IPv6 traffic distribution
Date: Wed, 27 Jul 2011 20:12:43 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local>
Content-class: urn:content-classes:message
In-Reply-To: <2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-MimeOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: IPv6 traffic distribution
Thread-Index: AcxMyb2ObIFMVOKaQjiRxZM0R1OXgQABADaw
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net><4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com><13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net><4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com><20110727023833.5C72D1232958@drugs.dv.isc.org><m1QlzXt-0001gSC@stereo.hq.phicoh.net> <2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "james woodyatt" <jhw@apple.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, 28 Jul 2011 03:12:45 -0000

James,

> james woodyatt wrote:
> I now feel compelled to reiterate that I would prefer a more
> controlled phase-out plan than, "equipment vendors and operators
> are free to commence the destruction of 6to4 at their individual
> convenience and without further warning to the user community."


According to this:
http://www.pam2010.ethz.ch/papers/full-length/15.pdf
Slightly less than 50% of IPv6 traffic comes from a MacOS client (fig
3); about 90% MacOS hits is 6to4, which possibly means (to me) that this
piece of 6to4 MacOS software of yours represents a third of global IPv6
traffic.

Would you care to comment on the numbers?


Also, according to Cisco's blog (that links to the document above):
http://blogs.cisco.com/sp/france-is-famous-for-fine-wine-cheese-and-now-
ipv6/
-or-
http://tinyurl.com/5u3eorn
"France is responsible for more than half of current IPv6 traffic
worldwide"; I can positively confirm that Free (AS12322) that
contributes to most of the French IPv6 native hits is delivering
"native" IPv6 to their eyeballs using 6rd and that they are indeed the
800-pound gorilla of French IPv6 traffic, no contest.

So, a third of IPv6 traffic is James' MacOS 6to4 software, another third
is AS12322's 6rd (which, given recent comments, is indeed 6to4-bis) and
we want to declare 6to4 historic?

Michel.


From john_brzozowski@cable.comcast.com  Wed Jul 27 20:15:34 2011
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 220C8228011 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 20:15:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.28
X-Spam-Level: 
X-Spam-Status: No, score=-105.28 tagged_above=-999 required=5 tests=[AWL=2.583, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o7lhQxz8p54Z for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 20:15:33 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by ietfa.amsl.com (Postfix) with ESMTP id AF95F21F863E for <ietf@ietf.org>; Wed, 27 Jul 2011 20:15:32 -0700 (PDT)
Received: from ([24.40.55.41]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.135401167; Wed, 27 Jul 2011 23:15:25 -0400
Received: from PACDCEXMB02.cable.comcast.com ([fe80::9803:aba4:1ac8:474e]) by PACDCEXHUB02.cable.comcast.com ([fe80::11d4:f530:37a0:9f4e%11]) with mapi id 14.01.0289.001; Wed, 27 Jul 2011 23:15:25 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: Keith Moore <moore@network-heretics.com>, t.petch <daedulus@btconnect.com>
Subject: Re: "6to4 damages the Internet" (was Re: draft-ietf-v6ops-6to4-to-historic (yet again))
Thread-Topic: "6to4 damages the Internet" (was Re: draft-ietf-v6ops-6to4-to-historic (yet again))
Thread-Index: AQHMTNSX7oaIuOgZBkmxJ2sHVc6vEA==
Date: Thu, 28 Jul 2011 03:15:24 +0000
Message-ID: <CA564A99.155733%john_brzozowski@cable.comcast.com>
In-Reply-To: <A25A544B-DDEA-483B-98B4-8D4C1F8B19A4@network-heretics.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
x-originating-ip: [147.191.125.13]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F4FCAF8D09F10741887F7D5DAE18545F@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 03:15:34 -0000

>From an operators point of view, specifically one that has deployed 6to4
relays, use of the same should not be encouraged.

I fully hope and expect the use of 6to4 to systematically decrease over
time so the associated infrastructure can be decommissioned.

While we have seen issues related to 6to4 decrease recently the deployment
of the same over the years, in particular open relays, has grossly
complicated deploying 6to4 in a reliable manner.

I have not been able to keep up with all the emails and threads related to
this topic, I apologize for this.

The bottom line from my point of view is that we (the IETF) should do
something to discourage the use of the same.

John
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D




On 7/27/11 2:18 PM, "Keith Moore" <moore@network-heretics.com> wrote:

>On Jul 27, 2011, at 3:32 AM, t.petch wrote:
>
>
>I oppose this action.
>
>I see clear evidence that 6to4 is damaging the Internet and although
>there are
>those who can use it without causing damage, I believe that the principle
>is
>'First, do no harm'
>so the IETF has a responsibility to discourage its use.  [...]
>
>
>
>
>
>I'd like to address the point that "6to4 damages the Internet".
>
>I do understand the content providers' argument - if 6to4 is turned on at
>the originator's host or network, the destination is advertising both A
>and AAAA records, and the AAAA record is chosen in preference to the A
>record, the user's experience is degraded.  Sometimes the performance is
>degraded marginally (but the cumulative effect of lots of small delays on
>a web page that loads dozens of images is large).  Sometimes it's
>degraded significantly because the 6to4 address doesn't work at all. Both
>cases matter, and they do provide a disincentive to content providers to
>just slap AAAA records onto their sites and be done with it.  (There are
>other ways of a web site utilizing v6, but they require more work.)
>
>A lot of the arguments that I hear about 6to4 being "bad" in a universal
>sense seem to be based on the assumption that it's only access to
>"content" in the public Internet that matters.  But anyone who has
>followed IPv6 development should know better than that.   If access to
>"content" in the public Internet were all that mattered, there would have
>been no interest in ULAs.   It remains the case that many enterprise
>networks have all kinds of "internal" resources that are useful to them
>even if they're not publicly addressable, and are only usable from within
>that network or from other networks with which they have made explicit
>arrangements.
>
>For better or worse, an explicit design "feature" of IPv6 is that hosts
>can have multiple addresses, and that different addresses might be needed
>in different contexts.  A host's public address might be used when
>contacting a public web server, but when communicating within an
>enterprise network or between networks each using ULA space, the host
>might need to use its ULA address as a source address (the other host
>might not have a public address or the ability to send traffic to the
>public IPv6 network).
>
>I put the word "feature" in quotes because this can be a pain in the a**
>for applications and users.   The default address selection rules don't
>really handle this case very well, nor can any set of static default
>rules handle this case.  Essentially what having multiple addresses per
>host implies is that hosts or applications need to do routing in the
>absence of routing information.  It shouldn't surprise anybody that the
>use of addresses that only work well (or at all) within a limited scope
>creates situations where a host will try to send traffic down a path that
>will never get it there, even when a different path would have worked.
>
>Introducing IPv6 - any kind of IPv6 - into a world of hosts that already
>support IPv4, creates exactly this situation.
>
>Nothing in IPv4 prohibited hosts from having multiple addresses and from
>advertising multiple addresses in DNS.    But this "feature" was rarely
>used, except in cases where all of the addresses were approximately
>equivalent in performance, because it didn't work well if some addresses
>performed better than others.  Then, as now, hosts and applications had
>no good way of reliably choosing which source and destination address to
>use.   But unlike IPv4, IPv6 deliberately chose to not only support the
>ability to have multiple addresses per host, but to actually expect it in
>a number of cases.
>
>One way to look at the content providers' complaint against 6to4, is that
>6to4 addresses are not "approximately equivalent in performance" to IPv4
>addresses.  So when hosts or applications happen to choose the 6to4
>address over an IPv4 address for the same resource, sometimes that choice
>ends up not working, or being suboptimal.  This is nothing new with 6to4.
> It's inherently the case that having multiple addresses for a host that
>aren't equivalent in performance leads to suboptimal choices in some
>cases.
>
>So essentially, the argument that "6to4 damages the Internet", is
>tantamount to "having multiple addresses for hosts damages the Internet".
>
>And this is an explicitly chosen architectural "feature" of IPv6.
>Blaming 6to4 for the problems caused by this "feature" is like blaming
>the canary carried by a coal miner for ceasing to chirp.
>
>(Though as it turns out, in the case of 6to4 the fix is relatively easy -
>just make 6to4 lower preference than either IPv4 or native IPv6 addresses
>except when the source and destination are both 6to4. )
>
>--
>
>People who are entirely engaged in providing content may have a hard time
>seeing any utility in 6to4.   They may ask, "if it doesn't deliver
>content as well as IPv4 does, what good is it?".   My answer to that
>question is, "what good are private networks and ULAs? "
>
>6to4 as defined by RFC 3056 is a bit like a ULA.  It provides a way for
>individual hosts that have a public IPv4 address, and hosts on small
>networks that have a public IPv4 address, to be able to interchange IPv6
>traffic.   True, it doesn't work through NAT, but it can be used as a way
>to provide IPv6 service within the 6to4 realm.  This lets users leverage
>the IPv6 protocol and IPv6 aware applications to get useful things done,
>that they would not have been able to do using IPv4.  Personally, I've
>found 6to4 useful to let me log into my home machines remotely, to
>remotely access file systems, to print to my home printer from work and
>my work printer from home, and a number of other things - all without
>making any application-specific arrangements.   For years I've heard from
>and read about other people using 6to4 in similar ways.
>
>The mechanism defined in RFC 3068 takes a step down the slippery slope of
>trying to make 6to4 into a means to access the public IPv6 Internet (and
>vice versa).  Because it was designed in an era where managed, supported
>IPv6 service was not widely available, it necessarily relies on the good
>will of people willing to provide relay routers.  And relying on the good
>will of those people comes with, or should come with, decreased
>expectations.  Note, however that we're still in the era where managed,
>supported IPv6 service is not widely available.  As long as we're in that
>era, and as long as native v4 access is available to some users, any
>statements to the effect that 6to4 is evil, obsolete, historic, etc.,
>even for the purposes of accessing the public v6 internet, are premature.
> (But if you want to say that it's not reliable for this purpose, that's
>a defensible statement.)
>
>The problem is that ordinary users don't know that they should have
>decreased expectations.  They might not even be aware that they're using
>6to4, or relying on the good will of others.
>
>Keith
>
>
>
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf


From trejrco@gmail.com  Wed Jul 27 20:42:01 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 B361311E8179 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 20:42:01 -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_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 7-mYxH12v6jV for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 20:42:00 -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 5E77021F8B3D for <ietf@ietf.org>; Wed, 27 Jul 2011 20:41:59 -0700 (PDT)
Received: by wwe5 with SMTP id 5so1367654wwe.13 for <ietf@ietf.org>; Wed, 27 Jul 2011 20:41:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=Nu0UpTWQfjHhGBimgmSv58Wa5KvSqbzJ+wt6OnludDs=; b=qKCbq/K4GoHB+hD481/06sddEsSgW/jFUfqiS+vmhJaaFJVAmhBLRLcdufOFSdAFEQ VoCQXGlsA5wzuIdROlrnkzwbXH9sBgXqwdQ/nmGvEmEvy0AGea3VvKbRU1T3l9e8vPc2 5vuIxnv98vetJfTI10qGHsRVWyUmMhf00SYIE=
Received: by 10.227.151.196 with SMTP id d4mr7107867wbw.102.1311824518120; Wed, 27 Jul 2011 20:41:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.138.100 with HTTP; Wed, 27 Jul 2011 20:41:38 -0700 (PDT)
In-Reply-To: <CA564A99.155733%john_brzozowski@cable.comcast.com>
References: <A25A544B-DDEA-483B-98B4-8D4C1F8B19A4@network-heretics.com> <CA564A99.155733%john_brzozowski@cable.comcast.com>
From: TJ <trejrco@gmail.com>
Date: Wed, 27 Jul 2011 23:41:38 -0400
Message-ID: <CALOgxGYLn04Sdm_oXfWTDfJAtsTiG+CvVZy6BMTVSwU+88ViPQ@mail.gmail.com>
Subject: Re: "6to4 damages the Internet" (was Re: draft-ietf-v6ops-6to4-to-historic (yet again))
To: "ietf@ietf.org" <ietf@ietf.org>, "Brzozowski, John" <John_Brzozowski@cable.comcast.com>
Content-Type: multipart/alternative; boundary=0016e64c1f7469060c04a918f29a
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, 28 Jul 2011 03:42:01 -0000

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

To be fair - I don't think anyone is saying "We should totally encourage
6to4!", even in the short-term ... or any other auto-tunneling transition
mechanism, really.

In fact, I think the debate here largely stems from a valid desire to
discourage 6to4.
Note: That goal, I am in favor of (recommending that 6to4 be disabled by
default on client platforms).


However, the proposals on the table seek to reclassify 6to4 as historic -
something that has raised a noticeable amount of debate about 1) what
historic really means and/or 2) what impact that re-classification may have
on currently-functional 6to4 usage today.


/TJ ... who wishes to note that 6to4 works *just fine* ... except when it
doesn't.
PS - And in those cases, proper address selection is a much better solution
(IMHO) than hitting this screw with a hammer.


On Wed, Jul 27, 2011 at 23:15, Brzozowski, John <
John_Brzozowski@cable.comcast.com> wrote:

> From an operators point of view, specifically one that has deployed 6to4
> relays, use of the same should not be encouraged.
>
> I fully hope and expect the use of 6to4 to systematically decrease over
> time so the associated infrastructure can be decommissioned.
>
> While we have seen issues related to 6to4 decrease recently the deployment
> of the same over the years, in particular open relays, has grossly
> complicated deploying 6to4 in a reliable manner.
>
> I have not been able to keep up with all the emails and threads related to
> this topic, I apologize for this.
>
> The bottom line from my point of view is that we (the IETF) should do
> something to discourage the use of the same.
>
> John
> =========================================
> John Jason Brzozowski
> Comcast Cable
> e) mailto:john_brzozowski@cable.comcast.com
> o) 609-377-6594
> m) 484-962-0060
> w) http://www.comcast6.net
> =========================================
>
>
>
>
> On 7/27/11 2:18 PM, "Keith Moore" <moore@network-heretics.com> wrote:
>
> >On Jul 27, 2011, at 3:32 AM, t.petch wrote:
> >
> >
> >I oppose this action.
> >
> >I see clear evidence that 6to4 is damaging the Internet and although
> >there are
> >those who can use it without causing damage, I believe that the principle
> >is
> >'First, do no harm'
> >so the IETF has a responsibility to discourage its use.  [...]
> >
> >
> >
> >
> >
> >I'd like to address the point that "6to4 damages the Internet".
> >
> >I do understand the content providers' argument - if 6to4 is turned on at
> >the originator's host or network, the destination is advertising both A
> >and AAAA records, and the AAAA record is chosen in preference to the A
> >record, the user's experience is degraded.  Sometimes the performance is
> >degraded marginally (but the cumulative effect of lots of small delays on
> >a web page that loads dozens of images is large).  Sometimes it's
> >degraded significantly because the 6to4 address doesn't work at all. Both
> >cases matter, and they do provide a disincentive to content providers to
> >just slap AAAA records onto their sites and be done with it.  (There are
> >other ways of a web site utilizing v6, but they require more work.)
> >
> >A lot of the arguments that I hear about 6to4 being "bad" in a universal
> >sense seem to be based on the assumption that it's only access to
> >"content" in the public Internet that matters.  But anyone who has
> >followed IPv6 development should know better than that.   If access to
> >"content" in the public Internet were all that mattered, there would have
> >been no interest in ULAs.   It remains the case that many enterprise
> >networks have all kinds of "internal" resources that are useful to them
> >even if they're not publicly addressable, and are only usable from within
> >that network or from other networks with which they have made explicit
> >arrangements.
> >
> >For better or worse, an explicit design "feature" of IPv6 is that hosts
> >can have multiple addresses, and that different addresses might be needed
> >in different contexts.  A host's public address might be used when
> >contacting a public web server, but when communicating within an
> >enterprise network or between networks each using ULA space, the host
> >might need to use its ULA address as a source address (the other host
> >might not have a public address or the ability to send traffic to the
> >public IPv6 network).
> >
> >I put the word "feature" in quotes because this can be a pain in the a**
> >for applications and users.   The default address selection rules don't
> >really handle this case very well, nor can any set of static default
> >rules handle this case.  Essentially what having multiple addresses per
> >host implies is that hosts or applications need to do routing in the
> >absence of routing information.  It shouldn't surprise anybody that the
> >use of addresses that only work well (or at all) within a limited scope
> >creates situations where a host will try to send traffic down a path that
> >will never get it there, even when a different path would have worked.
> >
> >Introducing IPv6 - any kind of IPv6 - into a world of hosts that already
> >support IPv4, creates exactly this situation.
> >
> >Nothing in IPv4 prohibited hosts from having multiple addresses and from
> >advertising multiple addresses in DNS.    But this "feature" was rarely
> >used, except in cases where all of the addresses were approximately
> >equivalent in performance, because it didn't work well if some addresses
> >performed better than others.  Then, as now, hosts and applications had
> >no good way of reliably choosing which source and destination address to
> >use.   But unlike IPv4, IPv6 deliberately chose to not only support the
> >ability to have multiple addresses per host, but to actually expect it in
> >a number of cases.
> >
> >One way to look at the content providers' complaint against 6to4, is that
> >6to4 addresses are not "approximately equivalent in performance" to IPv4
> >addresses.  So when hosts or applications happen to choose the 6to4
> >address over an IPv4 address for the same resource, sometimes that choice
> >ends up not working, or being suboptimal.  This is nothing new with 6to4.
> > It's inherently the case that having multiple addresses for a host that
> >aren't equivalent in performance leads to suboptimal choices in some
> >cases.
> >
> >So essentially, the argument that "6to4 damages the Internet", is
> >tantamount to "having multiple addresses for hosts damages the Internet".
> >
> >And this is an explicitly chosen architectural "feature" of IPv6.
> >Blaming 6to4 for the problems caused by this "feature" is like blaming
> >the canary carried by a coal miner for ceasing to chirp.
> >
> >(Though as it turns out, in the case of 6to4 the fix is relatively easy -
> >just make 6to4 lower preference than either IPv4 or native IPv6 addresses
> >except when the source and destination are both 6to4. )
> >
> >--
> >
> >People who are entirely engaged in providing content may have a hard time
> >seeing any utility in 6to4.   They may ask, "if it doesn't deliver
> >content as well as IPv4 does, what good is it?".   My answer to that
> >question is, "what good are private networks and ULAs? "
> >
> >6to4 as defined by RFC 3056 is a bit like a ULA.  It provides a way for
> >individual hosts that have a public IPv4 address, and hosts on small
> >networks that have a public IPv4 address, to be able to interchange IPv6
> >traffic.   True, it doesn't work through NAT, but it can be used as a way
> >to provide IPv6 service within the 6to4 realm.  This lets users leverage
> >the IPv6 protocol and IPv6 aware applications to get useful things done,
> >that they would not have been able to do using IPv4.  Personally, I've
> >found 6to4 useful to let me log into my home machines remotely, to
> >remotely access file systems, to print to my home printer from work and
> >my work printer from home, and a number of other things - all without
> >making any application-specific arrangements.   For years I've heard from
> >and read about other people using 6to4 in similar ways.
> >
> >The mechanism defined in RFC 3068 takes a step down the slippery slope of
> >trying to make 6to4 into a means to access the public IPv6 Internet (and
> >vice versa).  Because it was designed in an era where managed, supported
> >IPv6 service was not widely available, it necessarily relies on the good
> >will of people willing to provide relay routers.  And relying on the good
> >will of those people comes with, or should come with, decreased
> >expectations.  Note, however that we're still in the era where managed,
> >supported IPv6 service is not widely available.  As long as we're in that
> >era, and as long as native v4 access is available to some users, any
> >statements to the effect that 6to4 is evil, obsolete, historic, etc.,
> >even for the purposes of accessing the public v6 internet, are premature.
> > (But if you want to say that it's not reliable for this purpose, that's
> >a defensible statement.)
> >
> >The problem is that ordinary users don't know that they should have
> >decreased expectations.  They might not even be aware that they're using
> >6to4, or relying on the good will of others.
> >
> >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
>

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

<div>To be fair - I don&#39;t think anyone is saying &quot;We should totall=
y encourage 6to4!&quot;, even in the short-term ... or any other auto-tunne=
ling transition mechanism, really.<div><br></div><div>In fact, I think the =
debate here largely stems from a valid desire to discourage 6to4.</div>

<div>Note: That goal, I am in favor of (recommending that 6to4 be disabled =
by default on client platforms).</div><div><br></div><div><br></div><div>Ho=
wever, the proposals on the table seek to reclassify 6to4 as historic - som=
ething that has raised a noticeable amount of debate about=A01)=A0what hist=
oric really means and/or 2) what impact that re-classification may have on =
currently-functional 6to4 usage today.</div>

<div><br></div><div><br></div><div>/TJ ... who wishes to note that 6to4 wor=
ks *just fine* ... except when it doesn&#39;t. =A0<br>PS - And in those cas=
es, proper address selection is a much better solution (IMHO) than hitting =
this screw with a hammer.</div>

<div><br></div><div><br><div class=3D"gmail_quote">On Wed, Jul 27, 2011 at =
23:15, Brzozowski, John <span dir=3D"ltr">&lt;<a href=3D"mailto:John_Brzozo=
wski@cable.comcast.com">John_Brzozowski@cable.comcast.com</a>&gt;</span> wr=
ote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">From an operators point of view, specifical=
ly one that has deployed 6to4<br>
relays, use of the same should not be encouraged.<br>
<br>
I fully hope and expect the use of 6to4 to systematically decrease over<br>
time so the associated infrastructure can be decommissioned.<br>
<br>
While we have seen issues related to 6to4 decrease recently the deployment<=
br>
of the same over the years, in particular open relays, has grossly<br>
complicated deploying 6to4 in a reliable manner.<br>
<br>
I have not been able to keep up with all the emails and threads related to<=
br>
this topic, I apologize for this.<br>
<br>
The bottom line from my point of view is that we (the IETF) should do<br>
something to discourage the use of the same.<br>
<br>
John<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
John Jason Brzozowski<br>
Comcast Cable<br>
e) mailto:<a href=3D"mailto:john_brzozowski@cable.comcast.com">john_brzozow=
ski@cable.comcast.com</a><br>
o) <a href=3D"tel:609-377-6594" value=3D"+16093776594">609-377-6594</a><br>
m) <a href=3D"tel:484-962-0060" value=3D"+14849620060">484-962-0060</a><br>
w) <a href=3D"http://www.comcast6.net" target=3D"_blank">http://www.comcast=
6.net</a><br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<div><div></div><div class=3D"h5"><br>
<br>
<br>
<br>
On 7/27/11 2:18 PM, &quot;Keith Moore&quot; &lt;<a href=3D"mailto:moore@net=
work-heretics.com">moore@network-heretics.com</a>&gt; wrote:<br>
<br>
&gt;On Jul 27, 2011, at 3:32 AM, t.petch wrote:<br>
&gt;<br>
&gt;<br>
&gt;I oppose this action.<br>
&gt;<br>
&gt;I see clear evidence that 6to4 is damaging the Internet and although<br=
>
&gt;there are<br>
&gt;those who can use it without causing damage, I believe that the princip=
le<br>
&gt;is<br>
&gt;&#39;First, do no harm&#39;<br>
&gt;so the IETF has a responsibility to discourage its use. =A0[...]<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;I&#39;d like to address the point that &quot;6to4 damages the Internet&=
quot;.<br>
&gt;<br>
&gt;I do understand the content providers&#39; argument - if 6to4 is turned=
 on at<br>
&gt;the originator&#39;s host or network, the destination is advertising bo=
th A<br>
&gt;and AAAA records, and the AAAA record is chosen in preference to the A<=
br>
&gt;record, the user&#39;s experience is degraded. =A0Sometimes the perform=
ance is<br>
&gt;degraded marginally (but the cumulative effect of lots of small delays =
on<br>
&gt;a web page that loads dozens of images is large). =A0Sometimes it&#39;s=
<br>
&gt;degraded significantly because the 6to4 address doesn&#39;t work at all=
. Both<br>
&gt;cases matter, and they do provide a disincentive to content providers t=
o<br>
&gt;just slap AAAA records onto their sites and be done with it. =A0(There =
are<br>
&gt;other ways of a web site utilizing v6, but they require more work.)<br>
&gt;<br>
&gt;A lot of the arguments that I hear about 6to4 being &quot;bad&quot; in =
a universal<br>
&gt;sense seem to be based on the assumption that it&#39;s only access to<b=
r>
&gt;&quot;content&quot; in the public Internet that matters. =A0But anyone =
who has<br>
&gt;followed IPv6 development should know better than that. =A0 If access t=
o<br>
&gt;&quot;content&quot; in the public Internet were all that mattered, ther=
e would have<br>
&gt;been no interest in ULAs. =A0 It remains the case that many enterprise<=
br>
&gt;networks have all kinds of &quot;internal&quot; resources that are usef=
ul to them<br>
&gt;even if they&#39;re not publicly addressable, and are only usable from =
within<br>
&gt;that network or from other networks with which they have made explicit<=
br>
&gt;arrangements.<br>
&gt;<br>
&gt;For better or worse, an explicit design &quot;feature&quot; of IPv6 is =
that hosts<br>
&gt;can have multiple addresses, and that different addresses might be need=
ed<br>
&gt;in different contexts. =A0A host&#39;s public address might be used whe=
n<br>
&gt;contacting a public web server, but when communicating within an<br>
&gt;enterprise network or between networks each using ULA space, the host<b=
r>
&gt;might need to use its ULA address as a source address (the other host<b=
r>
&gt;might not have a public address or the ability to send traffic to the<b=
r>
&gt;public IPv6 network).<br>
&gt;<br>
&gt;I put the word &quot;feature&quot; in quotes because this can be a pain=
 in the a**<br>
&gt;for applications and users. =A0 The default address selection rules don=
&#39;t<br>
&gt;really handle this case very well, nor can any set of static default<br=
>
&gt;rules handle this case. =A0Essentially what having multiple addresses p=
er<br>
&gt;host implies is that hosts or applications need to do routing in the<br=
>
&gt;absence of routing information. =A0It shouldn&#39;t surprise anybody th=
at the<br>
&gt;use of addresses that only work well (or at all) within a limited scope=
<br>
&gt;creates situations where a host will try to send traffic down a path th=
at<br>
&gt;will never get it there, even when a different path would have worked.<=
br>
&gt;<br>
&gt;Introducing IPv6 - any kind of IPv6 - into a world of hosts that alread=
y<br>
&gt;support IPv4, creates exactly this situation.<br>
&gt;<br>
&gt;Nothing in IPv4 prohibited hosts from having multiple addresses and fro=
m<br>
&gt;advertising multiple addresses in DNS. =A0 =A0But this &quot;feature&qu=
ot; was rarely<br>
&gt;used, except in cases where all of the addresses were approximately<br>
&gt;equivalent in performance, because it didn&#39;t work well if some addr=
esses<br>
&gt;performed better than others. =A0Then, as now, hosts and applications h=
ad<br>
&gt;no good way of reliably choosing which source and destination address t=
o<br>
&gt;use. =A0 But unlike IPv4, IPv6 deliberately chose to not only support t=
he<br>
&gt;ability to have multiple addresses per host, but to actually expect it =
in<br>
&gt;a number of cases.<br>
&gt;<br>
&gt;One way to look at the content providers&#39; complaint against 6to4, i=
s that<br>
&gt;6to4 addresses are not &quot;approximately equivalent in performance&qu=
ot; to IPv4<br>
&gt;addresses. =A0So when hosts or applications happen to choose the 6to4<b=
r>
&gt;address over an IPv4 address for the same resource, sometimes that choi=
ce<br>
&gt;ends up not working, or being suboptimal. =A0This is nothing new with 6=
to4.<br>
&gt; It&#39;s inherently the case that having multiple addresses for a host=
 that<br>
&gt;aren&#39;t equivalent in performance leads to suboptimal choices in som=
e<br>
&gt;cases.<br>
&gt;<br>
&gt;So essentially, the argument that &quot;6to4 damages the Internet&quot;=
, is<br>
&gt;tantamount to &quot;having multiple addresses for hosts damages the Int=
ernet&quot;.<br>
&gt;<br>
&gt;And this is an explicitly chosen architectural &quot;feature&quot; of I=
Pv6.<br>
&gt;Blaming 6to4 for the problems caused by this &quot;feature&quot; is lik=
e blaming<br>
&gt;the canary carried by a coal miner for ceasing to chirp.<br>
&gt;<br>
&gt;(Though as it turns out, in the case of 6to4 the fix is relatively easy=
 -<br>
&gt;just make 6to4 lower preference than either IPv4 or native IPv6 address=
es<br>
&gt;except when the source and destination are both 6to4. )<br>
&gt;<br>
&gt;--<br>
&gt;<br>
&gt;People who are entirely engaged in providing content may have a hard ti=
me<br>
&gt;seeing any utility in 6to4. =A0 They may ask, &quot;if it doesn&#39;t d=
eliver<br>
&gt;content as well as IPv4 does, what good is it?&quot;. =A0 My answer to =
that<br>
&gt;question is, &quot;what good are private networks and ULAs? &quot;<br>
&gt;<br>
&gt;6to4 as defined by RFC 3056 is a bit like a ULA. =A0It provides a way f=
or<br>
&gt;individual hosts that have a public IPv4 address, and hosts on small<br=
>
&gt;networks that have a public IPv4 address, to be able to interchange IPv=
6<br>
&gt;traffic. =A0 True, it doesn&#39;t work through NAT, but it can be used =
as a way<br>
&gt;to provide IPv6 service within the 6to4 realm. =A0This lets users lever=
age<br>
&gt;the IPv6 protocol and IPv6 aware applications to get useful things done=
,<br>
&gt;that they would not have been able to do using IPv4. =A0Personally, I&#=
39;ve<br>
&gt;found 6to4 useful to let me log into my home machines remotely, to<br>
&gt;remotely access file systems, to print to my home printer from work and=
<br>
&gt;my work printer from home, and a number of other things - all without<b=
r>
&gt;making any application-specific arrangements. =A0 For years I&#39;ve he=
ard from<br>
&gt;and read about other people using 6to4 in similar ways.<br>
&gt;<br>
&gt;The mechanism defined in RFC 3068 takes a step down the slippery slope =
of<br>
&gt;trying to make 6to4 into a means to access the public IPv6 Internet (an=
d<br>
&gt;vice versa). =A0Because it was designed in an era where managed, suppor=
ted<br>
&gt;IPv6 service was not widely available, it necessarily relies on the goo=
d<br>
&gt;will of people willing to provide relay routers. =A0And relying on the =
good<br>
&gt;will of those people comes with, or should come with, decreased<br>
&gt;expectations. =A0Note, however that we&#39;re still in the era where ma=
naged,<br>
&gt;supported IPv6 service is not widely available. =A0As long as we&#39;re=
 in that<br>
&gt;era, and as long as native v4 access is available to some users, any<br=
>
&gt;statements to the effect that 6to4 is evil, obsolete, historic, etc.,<b=
r>
&gt;even for the purposes of accessing the public v6 internet, are prematur=
e.<br>
&gt; (But if you want to say that it&#39;s not reliable for this purpose, t=
hat&#39;s<br>
&gt;a defensible statement.)<br>
&gt;<br>
&gt;The problem is that ordinary users don&#39;t know that they should have=
<br>
&gt;decreased expectations. =A0They might not even be aware that they&#39;r=
e using<br>
&gt;6to4, or relying on the good will of others.<br>
&gt;<br>
&gt;Keith<br>
&gt;<br>
&gt;<br>
&gt;<br>
</div></div><div><div></div><div class=3D"h5">&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"_blank=
">https://www.ietf.org/mailman/listinfo/ietf</a><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>
</div></div></blockquote></div><br></div></div>

--0016e64c1f7469060c04a918f29a--

From dharkins@lounge.org  Wed Jul 27 22:02:40 2011
Return-Path: <dharkins@lounge.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 693E021F85C4; Wed, 27 Jul 2011 22:02:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.265
X-Spam-Level: 
X-Spam-Status: No, score=-6.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, 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 BaXObg4BzPnT; Wed, 27 Jul 2011 22:02:39 -0700 (PDT)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by ietfa.amsl.com (Postfix) with ESMTP id C049E21F856D; Wed, 27 Jul 2011 22:02:39 -0700 (PDT)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id 723ECA88810C; Wed, 27 Jul 2011 22:02:39 -0700 (PDT)
Received: from 70.25.120.2 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Wed, 27 Jul 2011 22:02:39 -0700 (PDT)
Message-ID: <7828ad8727dd860ccd6c5eb5acd52c19.squirrel@www.trepanning.net>
In-Reply-To: <78B594BA-9406-44A2-AB8E-0BF5A425AEC1@vpnc.org>
References: <20110727164459.29853.48303.idtracker@ietfa.amsl.com> <7C54FFE2-FFE0-4B4C-BF7E-142A6B10DF6B@checkpoint.com> <78B594BA-9406-44A2-AB8E-0BF5A425AEC1@vpnc.org>
Date: Wed, 27 Jul 2011 22:02:39 -0700 (PDT)
Subject: Re: [IPsec] Last  Call:	<draft-kivinen-ipsecme-secure-password-framework-01.txt>	(Secure Password Framework for IKEv2) to Informational RFC
From: "Dan Harkins" <dharkins@lounge.org>
To: "Paul Hoffman" <paul.hoffman@vpnc.org>
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: IPsecme WG <ipsec@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: Thu, 28 Jul 2011 05:02:40 -0000

  Paul,

  The existence of this draft shows a failure of YOUR leadership (and
that of your co-chairman) of the working group. Consensus was achieved
to add an authentication method based on a simple password yet you
seemingly worked to do everything possible to create division in the
working group and then stepped in to declare failure because no
consensus existed.

  We could've had a single standards-track solution to this problem over a
year ago if you had treated the singular draft used to argue for addition
of this work to the charter in the same way that you treated the singular
draft used to argue for addition of "EAP only" authentication to the
charter. The latter (authored by one of the chairmen) was advanced to
standards track after receiving a whopping ZERO comments from the WG and
the former was killed by the chairmen because the only comments on the
list were from authors of competing drafts (after manufacturing the
competition in the first place).

  There was hostility by the IPsecME chairmen to this work item from
the beginning and you worked to ensure its failure in the WG. Now you're
against advancement of Tero's draft to forge the best possible outcome
now? Not a surprise!

  Put that hat back on, along with a sackcloth and ashes, and say "mea
culpa".

  Dan.

On Wed, July 27, 2011 5:12 pm, Paul Hoffman wrote:
> <hat location="off">
>
> On Jul 27, 2011, at 6:30 PM, Yoav Nir wrote:
>
>> I think this is a terrible idea.
>
> +.5. I think is is a bad idea.
>
>> IKEv2 has a way for mutual authentication with a shared key.
>>
>> A concern was raised that this method was vulnerable to guessing if
>> trivial shared keys were configured.
>>
>> There were several proposals for a better cryptographic method.
>>
>> The IPsecME working group failed to choose between them. This is not so
>> surprising, because most participants are engineers, not cryptographers.
>> Even those with some cryptographic background stayed silent because
>> choosing between several cryptographic protocols is hard. IETF last
>> calls and the IESG did not help much either.
>>
>> This draft represents a total shirking of our responsibility.
>
> +.5. I think think it represents a shirking of our leadership's
> responsibility. Our leadership said that they would deal with the issue if
> the WG could not come to consensus, and the WG could not come to
> consensus. Adding a layer of indirection that is mostly transparent is not
> dealing with it.
>
>> Rather than decide on one protocol that is "best" or even arbitrarily
>> choosing one that is "good enough", it proposes to build a framework so
>> that everyone and their dog can have their own method. This is a
>> nightmare for developers: since you can't know what method the peer will
>> support, you have to implement all of them.
>>
>> If this had been a hierarchical organization, some manager would decide
>> which of the methods gets developed (or published) and the others would
>> be relegated to the recycle bin.
>>
>> The IETF is not like that and we seek to reach consensus. That's a good
>> thing, but this time it's leading us to a really bad solution for
>> interoperability, and a really bad solution for implementers.
>>
>> I am opposed to this draft.
>
> +1
>
>
> On Jul 27, 2011, at 6:52 PM, Tero Kivinen wrote:
>
>> Yoav Nir writes:
>>> This draft represents a total shirking of our responsibility. Rather
>>> than decide on one protocol that is "best" or even arbitrarily
>>> choosing one that is "good enough", it proposes to build a framework
>>> so that everyone and their dog can have their own method. This is a
>>> nightmare for developers: since you can't know what method the peer
>>> will support, you have to implement all of them.
>>
>> Partially yes, but unfortunately all of the authors of those actual
>> protocols decided that they wanted to continue publishing those drafts
>> as individual RFCs, and each of them used different way to negotiate
>> them, so there was no way to even implement multiple of them.
>
> Is this true? Because each has it's own way to negotiate its use, one
> should be able to implement multiple of the competing proposals as-is,
> yes?
>
>> At least this drafts gives you that option to implement multiple of
>> them if you want. This draft only provides instructions for those
>> other draft authors so they can at least common methods to negotiate
>> the feature and use common method to trasmit data between peers.
>
> True, but it is still punting the problem of us having just one.
>
> --Paul Hoffman
>
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec
>



From evnikita2@gmail.com  Wed Jul 27 22:05: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 D450C21F8BD5 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 22:05:17 -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 MLRPTzdIisfs for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 22:05: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 245DE21F856D for <ietf@ietf.org>; Wed, 27 Jul 2011 22:05:16 -0700 (PDT)
Received: by fxe6 with SMTP id 6so969329fxe.31 for <ietf@ietf.org>; Wed, 27 Jul 2011 22:05:16 -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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=RqDteFRUrwMnishaSPjdvaKWKaJTFYTplxXTCc9ZKKY=; b=dyD9kPzu8GOGw6Rt2T0H0NCkS1nr7K5olCg+pqAYEyjZwO9pEMOy1AYyETrVxrKnWL 3bXt1yiSkOcx+ttFLSuS1kwFrEqwFatcQZO/PNrTW4EYQlMffVxVJqCm/aLOZoGqHqEf hGBvF8RY36QkovMqEhEoRRi0dYZjUpmQK0jY0=
Received: by 10.223.98.77 with SMTP id p13mr746396fan.72.1311829516117; Wed, 27 Jul 2011 22:05:16 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id 12sm239113faz.32.2011.07.27.22.05.14 (version=SSLv3 cipher=OTHER); Wed, 27 Jul 2011 22:05:14 -0700 (PDT)
Message-ID: <4E30EE32.3020404@gmail.com>
Date: Thu, 28 Jul 2011 08:05:54 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: Last Call: <draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com>
In-Reply-To: <20110728020207.26024.73829.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: Thu, 28 Jul 2011 05:05:17 -0000

Hello,

The new version is obviously shorter, but it omits some points.  With 
eliminating of DS level, RFC 5657 makes no sense more.  It should be 
obsoleted and moved to Historic by your document, if IESG decides to 
eliminate the requirement for interoperability documentation, which I am 
opposed to (see my LC comments to -06).

Another issue is STD numbers.  Mentioning that they are still assigned 
to ISs in Section 2.2 should be fine.

Also, Section 3.3:

>     (2) At any time after two years from the approval of this document as
>         a BCP, the IESG may choose to reclassify any Draft Standard
>         document as Proposed Standard.

Won't such action be allowed after 2 years from approval?

Mykyta Yevstifeyev

28.07.2011 5:02, The IESG wrote:
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Reducing the Standards Track to Two Maturity Levels'
>    <draft-housley-two-maturity-levels-08.txt>  as a BCP
>


From jhw@apple.com  Wed Jul 27 22:32:08 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 2D2BF11E80A3 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 22:32:08 -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_83=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 1kb9W9rOEMur for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 22:32:06 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id EB0C211E8089 for <ietf@ietf.org>; Wed, 27 Jul 2011 22:32:06 -0700 (PDT)
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Received: from relay12.apple.com ([17.128.113.53]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LP1000MX3B4ZAI0@mail-out.apple.com> for ietf@ietf.org; Wed, 27 Jul 2011 22:30:40 -0700 (PDT)
X-AuditID: 11807135-b7b76ae000001169-ca-4e30f4a86d43
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 relay12.apple.com (Apple SCV relay) with SMTP id 0F.34.04457.8A4F03E4; Wed, 27 Jul 2011 22:33:29 -0700 (PDT)
Received: from [10.0.1.2] (unknown [207.96.251.20]) by cardamom.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LP100LNI3B2IP80@cardamom.apple.com> for ietf@ietf.org; Wed, 27 Jul 2011 22:30:40 -0700 (PDT)
Subject: Re: IPv6 traffic distribution
From: james woodyatt <jhw@apple.com>
In-reply-to: <392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local>
Date: Thu, 28 Jul 2011 01:30:38 -0400
Content-transfer-encoding: quoted-printable
Message-id: <10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <m1QlzXt-0001gSC@stereo.hq.phicoh.net> <2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com> <392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local>
To: Michel Py <michel@arneill-py.sacramento.ca.us>
X-Mailer: Apple Mail (2.1244.3)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrKLMWRmVeSWpSXmKPExsUiON1OVXflFwM/g58TWCyebZzP4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujLt7Cgpuilbc7J/L2MA4V7CLkZNDQsBE4uyZ68wQtpjEhXvr 2boYuTiEBFqZJC4u2cUEkuAVEJT4MfkeC4jNLKAj0fv9G1iDkMA0JokZPzNAbGEBNYm7b9aC 1bAJqEh8u3wXrJdTwE/i2Ir3YDaLgKrE33v9jBBzBCUm//0MZWtLPHl3gRVil43EvM0v2CHm X2GWmP9dAMQWETCS2HpxMdSh8hKLWz4zTmAUmIXkvFlIzpuFZOwCRuZVjIJFqTmJlYZGeokF BTmpesn5uZsYQYHXUGi6g/HRQvVDjAIcjEo8vD/1DPyEWBPLiitzDzFKcDArifBekgMK8aYk VlalFuXHF5XmpBYfYpTmYFES5y25J+4nJJCeWJKanZpakFoEk2Xi4JRqYHRM9ky8vLb6zPYv J6bXGzM/V4qa1nTUIO/hT9E19zq81fb/tPWdHM57kLUp2X7lM//nU7PXHrEV/dh9YoKT2Hne dI2osMhz2aapuosanI/d3HrMZKLM3t4558/f6kk5/kxN2+SnfLDiPi77VcFr4mYEbThSM/1x 51y9jRPPiL9ZsGVBjumdD4uVWIozEg21mIuKEwHIg9vdOAIAAA==
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 05:32:08 -0000

On Jul 27, 2011, at 11:12 PM, Michel Py wrote:
>=20
> According to this:
> http://www.pam2010.ethz.ch/papers/full-length/15.pdf
> Slightly less than 50% of IPv6 traffic comes from a MacOS client (fig
> 3); about 90% MacOS hits is 6to4, which possibly means (to me) that =
this
> piece of 6to4 MacOS software of yours represents a third of global =
IPv6
> traffic.
>=20
> Would you care to comment on the numbers?

p1.  Those numbers are badly outdated.

p2.  Hits originating from Mac OS X hosts with their 6to4 tunnels =
disabled probably account for much of that traffic when it was measured. =
 At that time, Apple's operating systems were the most commonly deployed =
implementations with IPv6 stacks enabled and running in the stock =
install.  That isn't true any more.

p3.  Recent measurements of hits originating from Mac OS X hosts on 6to4 =
prefixed networks are dramatically smaller than when those measurements =
were taken, because Apple has updated Mac OS X 10.6 and 10.7 with =
significantly different behavior that will avoid using broken or =
underperforming 6to4 links.

p4.  Yes, older gear remains in the field, and some of it doesn't even =
have a software upgrade path.  That gear, no doubt, accounts for a =
substantial portion of admittedly not very large flows through public =
6to4 relays at present.  I think the measurements we've all seen at the =
technical plenary show that 6to4 is a small percentage of the total =
world IPv6 traffic now, which again is an embarrassingly small fraction =
of global Internet traffic.

p5.  We should all be mindful that we're talking about a very small, and =
as far as I can tell, a not very critical segment of anybody's user =
base.  Which, nevertheless, is still somehow to blame for holding up the =
global roll-out of IPv6 content.  (I'm not sure even the legendary =
Gnomes of Z=FCrich could do that.)

What else is there to say?  Oh, I remember now.  Those of you =
6to4-haters with Lion installed now.  Please open a Terminal.app window =
and type this command:

  $ sudo sysctl -w net.inet6.icmp6.nd6_accept_6to4=3D0

That will make the IPv6 stack treat all Prefix Information Options with =
2002::/16 prefixed addresses in them as if the A bit is always zero.  =
The system will not auto-configure any 6to4 addresses on any interfaces, =
even a stf interface.

Oh, you want that all the time?  Add a line to /etc/sysctl.conf.  Done.  =
No more 6to4 for you.  Anywhere.  Let me know if that changes anything =
noticeably to the better for you.  (On the plus side, it should spare =
you from suffering any indignity at the hands of a 6to4-PMT service.)


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From yaronf.ietf@gmail.com  Wed Jul 27 22:50:10 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 B9BC611E80A4; Wed, 27 Jul 2011 22:50:10 -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 4h35RoRmOZSe; Wed, 27 Jul 2011 22:50:10 -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 588DD11E8089; Wed, 27 Jul 2011 22:50:09 -0700 (PDT)
Received: by wwe5 with SMTP id 5so1403995wwe.13 for <multiple recipients>; Wed, 27 Jul 2011 22:50:08 -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=wFi8IvUotghE83t2Kb6ntbjZ+u8mlcxIh6gaASdcGzM=; b=YiUEVEfVwk4SzbEaEH1+AKB+QjJT3p7FncZGL886G2ebytXFVUNF2CJPmJ9W4WUgNd oGsIrbxzyZGTAGWslkhqR3GixritEQj7n9H26/bYSvSa69F0VatfQMsO8j35FhoTeoV9 6Hnz9CPKOSkd6xS5QLpmpMBU5oU4IO3zrD5HA=
Received: by 10.227.175.139 with SMTP id ba11mr880864wbb.23.1311832208382; Wed, 27 Jul 2011 22:50:08 -0700 (PDT)
Received: from [10.0.0.2] (bzq-79-179-237-205.red.bezeqint.net [79.179.237.205]) by mx.google.com with ESMTPS id fr7sm511121wbb.56.2011.07.27.22.50.05 (version=SSLv3 cipher=OTHER); Wed, 27 Jul 2011 22:50:07 -0700 (PDT)
Message-ID: <4E30F876.70200@gmail.com>
Date: Thu, 28 Jul 2011 08:49:42 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Dan Harkins <dharkins@lounge.org>
Subject: Re: [IPsec] Last Call: <draft-kivinen-ipsecme-secure-password-framework-01.txt> (Secure Password Framework for IKEv2) to Informational RFC
References: <20110727164459.29853.48303.idtracker@ietfa.amsl.com> <7C54FFE2-FFE0-4B4C-BF7E-142A6B10DF6B@checkpoint.com> <78B594BA-9406-44A2-AB8E-0BF5A425AEC1@vpnc.org> <7828ad8727dd860ccd6c5eb5acd52c19.squirrel@www.trepanning.net>
In-Reply-To: <7828ad8727dd860ccd6c5eb5acd52c19.squirrel@www.trepanning.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IPsecme WG <ipsec@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: Thu, 28 Jul 2011 05:50:10 -0000

Unfortunately Dan cannot accept that there may be objective, non 
political reasons for the group not to adopt his work. Which is the 
reason why three alternative proposals were published several months 
after his proposed PAKE solution.

As co-chairmen of ipsecme, Paul and I did our best to get the group to 
agree on a single solution, to the point where we both supported Dan's 
criteria for selecting such a solution. Unfortunately we failed: while 
the group supported a PAKE in IKEv2 "in the abstract", there was not 
enough energy to pick a single protocol for this purpose.

Back to the matter at hand: I am opposed to 
draft-kivinen-ipsecme-secure-password-framework. It has served its 
purpose when two of the proposals were changed to add method 
negotiation, and thus enable IKE peers to implement none, one or more of 
these methods. I believe the other justifications for this draft, 
including the preservation of IANA IKEv2 namespaces, are bogus. Adopting 
the rest of the framework would be a useless exercise.

Personally, given that all three current proposals are being advanced as 
Experimental outside the WG, I would argue that we are wasting far too 
much energy on this grand unified framework. And this includes the 
current mail exchange.

Thanks,
     Yaron

On 28.7.2011 08:02, Dan Harkins wrote:
>    Paul,
>
>    The existence of this draft shows a failure of YOUR leadership (and
> that of your co-chairman) of the working group. Consensus was achieved
> to add an authentication method based on a simple password yet you
> seemingly worked to do everything possible to create division in the
> working group and then stepped in to declare failure because no
> consensus existed.
>
>    We could've had a single standards-track solution to this problem over a
> year ago if you had treated the singular draft used to argue for addition
> of this work to the charter in the same way that you treated the singular
> draft used to argue for addition of "EAP only" authentication to the
> charter. The latter (authored by one of the chairmen) was advanced to
> standards track after receiving a whopping ZERO comments from the WG and
> the former was killed by the chairmen because the only comments on the
> list were from authors of competing drafts (after manufacturing the
> competition in the first place).
>
>    There was hostility by the IPsecME chairmen to this work item from
> the beginning and you worked to ensure its failure in the WG. Now you're
> against advancement of Tero's draft to forge the best possible outcome
> now? Not a surprise!
>
>    Put that hat back on, along with a sackcloth and ashes, and say "mea
> culpa".
>
>    Dan.
>
> On Wed, July 27, 2011 5:12 pm, Paul Hoffman wrote:
>> <hat location="off">
>>
>> On Jul 27, 2011, at 6:30 PM, Yoav Nir wrote:
>>
>>> I think this is a terrible idea.
>> +.5. I think is is a bad idea.
>>
>>> IKEv2 has a way for mutual authentication with a shared key.
>>>
>>> A concern was raised that this method was vulnerable to guessing if
>>> trivial shared keys were configured.
>>>
>>> There were several proposals for a better cryptographic method.
>>>
>>> The IPsecME working group failed to choose between them. This is not so
>>> surprising, because most participants are engineers, not cryptographers.
>>> Even those with some cryptographic background stayed silent because
>>> choosing between several cryptographic protocols is hard. IETF last
>>> calls and the IESG did not help much either.
>>>
>>> This draft represents a total shirking of our responsibility.
>> +.5. I think think it represents a shirking of our leadership's
>> responsibility. Our leadership said that they would deal with the issue if
>> the WG could not come to consensus, and the WG could not come to
>> consensus. Adding a layer of indirection that is mostly transparent is not
>> dealing with it.
>>
>>> Rather than decide on one protocol that is "best" or even arbitrarily
>>> choosing one that is "good enough", it proposes to build a framework so
>>> that everyone and their dog can have their own method. This is a
>>> nightmare for developers: since you can't know what method the peer will
>>> support, you have to implement all of them.
>>>
>>> If this had been a hierarchical organization, some manager would decide
>>> which of the methods gets developed (or published) and the others would
>>> be relegated to the recycle bin.
>>>
>>> The IETF is not like that and we seek to reach consensus. That's a good
>>> thing, but this time it's leading us to a really bad solution for
>>> interoperability, and a really bad solution for implementers.
>>>
>>> I am opposed to this draft.
>> +1
>>
>>
>> On Jul 27, 2011, at 6:52 PM, Tero Kivinen wrote:
>>
>>> Yoav Nir writes:
>>>> This draft represents a total shirking of our responsibility. Rather
>>>> than decide on one protocol that is "best" or even arbitrarily
>>>> choosing one that is "good enough", it proposes to build a framework
>>>> so that everyone and their dog can have their own method. This is a
>>>> nightmare for developers: since you can't know what method the peer
>>>> will support, you have to implement all of them.
>>> Partially yes, but unfortunately all of the authors of those actual
>>> protocols decided that they wanted to continue publishing those drafts
>>> as individual RFCs, and each of them used different way to negotiate
>>> them, so there was no way to even implement multiple of them.
>> Is this true? Because each has it's own way to negotiate its use, one
>> should be able to implement multiple of the competing proposals as-is,
>> yes?
>>
>>> At least this drafts gives you that option to implement multiple of
>>> them if you want. This draft only provides instructions for those
>>> other draft authors so they can at least common methods to negotiate
>>> the feature and use common method to trasmit data between peers.
>> True, but it is still punting the problem of us having just one.
>>
>> --Paul Hoffman
>>
>> _______________________________________________
>> IPsec mailing list
>> IPsec@ietf.org
>> https://www.ietf.org/mailman/listinfo/ipsec
>>
>
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec


From michel@arneill-py.sacramento.ca.us  Wed Jul 27 23:07: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 56E5C21F8AD1 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 23:07:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.073
X-Spam-Level: 
X-Spam-Status: No, score=-2.073 tagged_above=-999 required=5 tests=[AWL=0.192,  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 yP-grm02tNCq for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 23:07:40 -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 CCECD21F8ACA for <ietf@ietf.org>; Wed, 27 Jul 2011 23:07:40 -0700 (PDT)
Subject: RE: IPv6 traffic distribution
Date: Wed, 27 Jul 2011 23:07:40 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF62B@newserver.arneill-py.local>
Content-class: urn:content-classes:message
In-Reply-To: <10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-MimeOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: IPv6 traffic distribution
Thread-Index: AcxM533miNxrce4jQKmT0yuPtdux5gAAVWzg
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <m1QlzXt-0001gSC@stereo.hq.phicoh.net> <2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com> <392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local> <10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "james woodyatt" <jhw@apple.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, 28 Jul 2011 06:07:42 -0000

James,

If I remember correctly, you mentioned a bit ago that your job required
you had native IPv6 at home.=20

Question: Does an ISP providing you IPv6 out of the CPE box (meaning,
without any software other than dual-stack on the hosts) qualify as
native IPv6 if, behind the scenes, they use a tunnel broker, or 6rd?


> james woodyatt wrote:
> p1.  Those numbers are badly outdated.

What is your reading on 6rd numbers? And if these numbers are badly
outdated, where do you place the MacOS IPv6 traffic distribution today?


> p3.  Recent measurements of hits originating from Mac OS X
> hosts on 6to4 prefixed networks are dramatically smaller
> than when those measurements were taken, because Apple has
> updated Mac OS X 10.6 and 10.7 with significantly different
> behavior that will avoid using broken or underperforming
> 6to4 links.

So where does the new behavior switch the traffic to,
from 10.6 to 10.7? Back to IPv4? Or some other method?
Maybe Apple is using Teredo? (ducks) :P


> [..] the total world IPv6 traffic now, which again is an
> embarrassingly small fraction of global Internet traffic.

That is another debate.

Michel.


From sm@resistor.net  Wed Jul 27 23:26:44 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 4C60B21F87C2 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 23:26:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.914
X-Spam-Level: 
X-Spam-Status: No, score=-102.914 tagged_above=-999 required=5 tests=[AWL=-0.179, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, 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 TEl+9pApm7EN for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 23:26:40 -0700 (PDT)
Received: from mx.elandsys.com (ns1.qubic.net [208.69.177.116]) by ietfa.amsl.com (Postfix) with ESMTP id 3B33421F8786 for <ietf@ietf.org>; Wed, 27 Jul 2011 23:26:40 -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 p6S6QFNq009553;  Wed, 27 Jul 2011 23:26:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1311834380; bh=zQV+zmBzofEV9VCI+pZdFDogbtHdPSsgGcfKj3H0hPc=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=eB/qOdm53K3mlRXfVkLUKEAPZXJIxkK2DAvMkwNKkP3QSKG+8IxgT+r/TYO1PXf1n tYSsbzcZWw5P8RMvtM93YhmbmtNJp+IzXjaH3pXYzWXDRe1AmY78lkcsty+PPv7dNt Htca8DDdC2VTTSvgo+1VN8dxqv1xOpyPDz7Y3scU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1311834380; bh=zQV+zmBzofEV9VCI+pZdFDogbtHdPSsgGcfKj3H0hPc=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=FmAULvHDpX0nsO771e0+yLpz3shzbYQnF4/Cw2ZUxCGSwc8dO9qPSWfx8H5a0rNmN S6IG02Bt2jNngTjqz8WoCZZhN7UV4StMJuLANXNEfhcl74+SRh+u1WglpdksI4LBQQ 609mqTAcdMQoNHhqUXN8ztAHHWWHqae+rhqtC/3I=
Message-Id: <6.2.5.6.2.20110727230321.04c60e20@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 27 Jul 2011 23:13:39 -0700
To: Alexa Morris <amorris@amsl.com>
From: SM <sm@resistor.net>
Subject: Re: Reminder: Remote Participation Support for Admin Plenary Tonight
In-Reply-To: <0E66E2DF-6381-4014-B1FA-EC33704FA8FF@amsl.com>
References: <3D658D0E-4958-4AEF-9BD2-447A887EECF1@amsl.com> <4E30865A.2090802@gmail.com> <6.2.5.6.2.20110727152126.06e32500@resistor.net> <0E66E2DF-6381-4014-B1FA-EC33704FA8FF@amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 06:26:44 -0000

Hi Alexa,
At 04:51 PM 7/27/2011, Alexa Morris wrote:
>First, I want to reassure you that there is no plan to discontinue the
>regular audio streaming at meetings; indeed, there was every intention

Thanks.

>Sorry for any inconvenience. Please also understand that the Meetecho
>staff intended to provide additional value, and are in no way

The Meetecho staff were helpful.  They explained how to access the 
Meetecho audio stream.

Regards,
-sm 


From moore@network-heretics.com  Wed Jul 27 23:45: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 1717D21F8BD2 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 23:45:55 -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 DsSJkD207eO4 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 23:45:54 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 6C2F721F8AF3 for <ietf@ietf.org>; Wed, 27 Jul 2011 23:45:54 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 8C78420939; Thu, 28 Jul 2011 02:45:53 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute4.internal (MEProxy); Thu, 28 Jul 2011 02:45:53 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=LuqVV9lbzjLDq3aLOIhRCJtvbno=; b=eU LpvvITO48zrbxEnbMHFri2IzDRUJmI4Vd+sQphIQhBZhf2TCgpL4p98sJQBvKsq+ F+r/5NielfJzT3dSR90QYw3A6NjHQbyRe0DzoRdu/Av/qFfy7JCL2VMmsAnilpMk 2GQEr+P9FB4gOyb8H2W8celaU4SRfCD91IC+dhsjw=
X-Sasl-enc: vd+h81uAetVcAWQSh2uw/0XsvZmgVLKkxrtXGkoNOGbJ 1311835553
Received: from [192.168.210.100] (modemcable114.145-70-69.static.videotron.ca [69.70.145.114]) by mail.messagingengine.com (Postfix) with ESMTPSA id 2FF9E455849; Thu, 28 Jul 2011 02:45:53 -0400 (EDT)
Subject: Re: IPv6 traffic distribution
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: <10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com>
Date: Thu, 28 Jul 2011 02:45:52 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <61FD6550-07F6-4526-81EE-2CF157858236@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <m1QlzXt-0001gSC@stereo.hq.phicoh.net> <2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com> <392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local> <10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com>
To: james woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.1084)
Cc: Michel Py <michel@arneill-py.sacramento.ca.us>, 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, 28 Jul 2011 06:45:55 -0000

On Jul 28, 2011, at 1:30 AM, james woodyatt wrote:

>  I think the measurements we've all seen at the technical plenary show =
that 6to4 is a small percentage of the total world IPv6 traffic now, =
which again is an embarrassingly small fraction of global Internet =
traffic.

What I saw from different presentations seemed to indicate that 6to4 was =
around 30% of total IPv6 traffic. =20

I think it's hard to conclude much from that in terms of future use of =
6to4 vs. native.  As you point out, more and more stacks are disabling =
6to4 by default.  But when the native v6 traffic is dominated by a =
single AS, it's hard to use that as an indication of how much growth =
there will be in use of v6.

Bottom line: we still have our work cut out for us.

Keith


From sm@resistor.net  Thu Jul 28 00:12:14 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 1BE9411E80A6 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 00:12:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HNgGqeBKAQEH for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 00:12:11 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 45E0611E8070 for <ietf@ietf.org>; Thu, 28 Jul 2011 00:12:11 -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 p6S7C2Vv017079;  Thu, 28 Jul 2011 00:12:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1311837127; bh=fhEo88hX84YrSo470jdhSC9etdyFbAMFVScZnxr6T4w=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=R3SDR8RgzBmk5Zt6C+dj8NbnxxPWBt8FdrPP47vtt/RZylSqVEYmvafFgwFS0erEp +xmNhEfE/b/uNxxxNWW6OoECe1Y7o42ATr2ume0QiTYZq8mE34H1l9K1BPdClp3Hn7 gIxtPafLrjW+fi1cJna5FyWqTu1RxJFvo61G3F5c=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1311837127; bh=fhEo88hX84YrSo470jdhSC9etdyFbAMFVScZnxr6T4w=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=Hh0Uy4Z8wr1hlfTy6dLKO9oAhpKnMfBGh8/lRZDfgNJY4hZBbLPdNK/orCO4BgNk0 XnGQXXlDKDBtFBAVd4Sj6cSvnSJmVw1zggLtLh5vGhmAbELbp7FWnCMwKMXjQP/IqZ soVMWntXnlN7U/5sVYTe1FBneIycqzRVul8vPsFA=
Message-Id: <6.2.5.6.2.20110727233441.04c41030@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 27 Jul 2011 23:45:20 -0700
To: mrex@sap.com
From: SM <sm@resistor.net>
Subject: Re: Why the IESG needs to review everything...
In-Reply-To: <201107272313.p6RNDMX9017678@fs4113.wdf.sap.corp>
References: <4E308D64.3030804@gmail.com> <201107272313.p6RNDMX9017678@fs4113.wdf.sap.corp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 07:12:14 -0000

Hi Martin,
At 04:13 PM 7/27/2011, Martin Rex wrote:
>According to rfc2026:
>
>    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.  [...]

The above is incorrect.

Regards,
-sm 


From pch-b2B3A6689@u-1.phicoh.com  Thu Jul 28 00:51:17 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 6E03421F8C06 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 00:51:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 92GkHuaU2EFi for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 00:51:17 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo-6to4.hq.phicoh.net [IPv6:2002:8225:f03:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id 7E44521F8C08 for <ietf@ietf.org>; Thu, 28 Jul 2011 00:51:15 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #66) id m1QmLN6-0001imC; Thu, 28 Jul 2011 09:51:08 +0200
Message-Id: <m1QmLN6-0001imC@stereo.hq.phicoh.net>
To: TJ <trejrco@gmail.com>
Subject: Re: "6to4 damages the Internet" (was Re: draft-ietf-v6ops-6to4-to-historic (yet again)) 
From: Philip Homburg <pch-ietf@u-1.phicoh.com>
Sender: pch-b2B3A6689@u-1.phicoh.com
In-reply-to: Your message of "Wed, 27 Jul 2011 23:41:38 -0400 ." <CALOgxGYLn04Sdm_oXfWTDfJAtsTiG+CvVZy6BMTVSwU+88ViPQ@mail.gmail.com> 
Date: Thu, 28 Jul 2011 09:50:59 +0200
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, 28 Jul 2011 07:51:17 -0000

In your letter dated Wed, 27 Jul 2011 23:41:38 -0400 you wrote:
>PS - And in those cases, proper address selection is a much better solution
>(IMHO) than hitting this screw with a hammer.

I think the problem is that we don't know how to do 'proper' address
selection. It would be nice if 5 or 10 years ago there would have been a good
standard to do address selection. Today, we are just in the stage of doing
more experiments.

There is one thing that works well. And that is, you only assign global
IPv6 addresses to a host if global IPv6 connectivity is at least as good as
IPv4 connectivity.

We want large scale deployment of IPv6 today not some time in the future
when we finally figured out address selection. And that means that today we
have to make sure that users don't end up with unreliable IPv6 connections.



From mohta@necom830.hpcl.titech.ac.jp  Thu Jul 28 01:10:20 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 8CAAF21F8C4B for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 01:10:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.078
X-Spam-Level: 
X-Spam-Status: No, score=-0.078 tagged_above=-999 required=5 tests=[AWL=0.012,  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 bBAZUZtZ0hoD for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 01:10:20 -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 2E52F21F8C47 for <ietf@ietf.org>; Thu, 28 Jul 2011 01:09:41 -0700 (PDT)
Received: (qmail 40664 invoked from network); 28 Jul 2011 08:29:49 -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; 28 Jul 2011 08:29:49 -0000
Message-ID: <4E3118E1.5090107@necom830.hpcl.titech.ac.jp>
Date: Thu, 28 Jul 2011 17:08:01 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: "6to4 damages the Internet" (was Re: draft-ietf-v6ops-6to4-to-historic (yet again))
References: <m1QmLN6-0001imC@stereo.hq.phicoh.net>
In-Reply-To: <m1QmLN6-0001imC@stereo.hq.phicoh.net>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 08:10:20 -0000

Philip Homburg wrote:

> I think the problem is that we don't know how to do 'proper' address
> selection.

I know and it's trivially easy.

> It would be nice if 5 or 10 years ago there would have been a good
> standard to do address selection.

11 years ago in draft-ohta-e2e-multihoming-00.txt, I wrote:

   End systems (hosts) are end systems. To make the end to end principle
   effectively work, the end systems must have all the available
   knowledge to make decisions by the end systems themselves.

   With regard to multihoming, when an end system want to communicate
   with a multihomed end system, the end system must be able to select
   most appropriate (based on the local information) destination address
   of the multihomed end system.

which means an end system should have a full routing table, IGP
metrics in which tell the end system what is the best address of
its multihomed peer. Full routing table should and can, of course,
be small.

The approach is totally against node/router separation of IPv6 to
make routers, the intermediate systems, a lot more intelligent
than nodes, the end systems, which is partly why IPv6 is hopeless.

						Masataka Ohta

From moore@network-heretics.com  Thu Jul 28 04:50: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 AF51621F86A1 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 04:50:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.561
X-Spam-Level: 
X-Spam-Status: No, score=-4.561 tagged_above=-999 required=5 tests=[AWL=1.038,  BAYES_00=-2.599, GB_I_LETTER=-2, 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 szeqpqjFD5b1 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 04:50: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 4760C21F869C for <ietf@ietf.org>; Thu, 28 Jul 2011 04:50:40 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id C782B20DCA; Thu, 28 Jul 2011 07:50:39 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Thu, 28 Jul 2011 07:50: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=blsgqgtsRewStMDYV5eGffPAC+I=; b=X8 rK0MNALBkmhb0f7AR8a0+zfXtbkTQIdwJopUmbPpRIrhTDWGP0xtJ1YgvqpsM7HE iUkzpC5l4FvCrIgerT6DhM9W4TT/04w5CL8glgTmUSEZ4Ox/mfmVXwAOhCqztiAi U47s588MwvCjUM0Y1LpL3Jw34FtUYyPPqT7QZxg3Q=
X-Sasl-enc: 7M5f3wp6VC8IhDW7XMJ3F1CuvR5Rnj2bmT9dl/ZseTIR 1311853839
Received: from [192.168.210.100] (modemcable114.145-70-69.static.videotron.ca [69.70.145.114]) by mail.messagingengine.com (Postfix) with ESMTPSA id 4AC3F414926; Thu, 28 Jul 2011 07:50:39 -0400 (EDT)
Subject: Re: "6to4 damages the Internet" (was Re: draft-ietf-v6ops-6to4-to-historic (yet again)) 
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: <m1QmLN6-0001imC@stereo.hq.phicoh.net>
Date: Thu, 28 Jul 2011 07:50:38 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <51E12FC1-6DE1-479C-AAD4-1877274F96A0@network-heretics.com>
References: <m1QmLN6-0001imC@stereo.hq.phicoh.net>
To: Philip Homburg <pch-ietf@u-1.phicoh.com>
X-Mailer: Apple Mail (2.1084)
Cc: "ietf@ietf.org" <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 11:50:41 -0000

On Jul 28, 2011, at 3:50 AM, Philip Homburg wrote:

> In your letter dated Wed, 27 Jul 2011 23:41:38 -0400 you wrote:
>> PS - And in those cases, proper address selection is a much better =
solution
>> (IMHO) than hitting this screw with a hammer.
>=20
> I think the problem is that we don't know how to do 'proper' address
> selection. It would be nice if 5 or 10 years ago there would have been =
a good
> standard to do address selection. Today, we are just in the stage of =
doing
> more experiments.
>=20
> There is one thing that works well. And that is, you only assign =
global
> IPv6 addresses to a host if global IPv6 connectivity is at least as =
good as
> IPv4 connectivity.

In general, all of a host's addresses (at least, those in the same =
preference class in the address selection algorithm) need to work =
equally well from everywhere.

But even that might not be sufficient.   Fred Baker has recently been =
citing a different example of the same problem:  Imagine a future where =
hosts on a network have both v6 and legacy v4 through stateful NAT.  =
Because the v6 connection works well most of the time, hosts tend to =
choose v6 destinations, and sites reduce the capacity of their NATs over =
time.  Then the v6 connection fails, and suddenly everything falls back =
to v4, and the connections through NAT also fail for lack of sufficient =
capacity to handle the load.

Note that in some sense this is a perceptual problem.   If instead of a =
v4 and a v6 address, each of those hosts had two v6 addresses and two =
different egress paths, the network engineers would be more likely to =
understand that both external connections needed to be of equal capacity =
- just like multihomed v4 networks with a single prefix now.   And in =
some sense there's nothing wrong with having a v6 connection for most =
things and a small v4 NAT for connecting to legacy v4 services, as long =
as you don't think of the v4 path as a fallback - you're willing to =
accept that loss of the v6 connection is for practical purposes loss of =
external connectivity.   The problem is that if you think of the v4 NAT =
as a fallback for the v6 service, AND you don't drastically =
overprovision the NAT.

> We want large scale deployment of IPv6 today not some time in the =
future
> when we finally figured out address selection. And that means that =
today we
> have to make sure that users don't end up with unreliable IPv6 =
connections.

If you make the constraint that nobody can use IPv6 at all until the =
IPv6 connections work as well in all cases as the IPv4 connections, that =
creates a huge barrier to the universal deployment of IPv6 - which =
already has enough barriers as it is. =20

A less onerous constraint is that less reliable IPv6 connections don't =
get used in preference to more reliable IPv4 connections.  We're lucky =
in the case of 6to4 in that it has a well-known prefix that allows the =
traffic to be distinguished from other v6 traffic.   But it's still =
necessary to manage expectations about IPv4 as a fallback path.

Keith


From sob@harvard.edu  Thu Jul 28 05:19:05 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 C614E21F8C2C for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 05:19:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9-q-Ikepghlo for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 05:19:05 -0700 (PDT)
Received: from newdev.eecs.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by ietfa.amsl.com (Postfix) with ESMTP id 4DEDE21F8C29 for <ietf@ietf.org>; Thu, 28 Jul 2011 05:19:05 -0700 (PDT)
Received: by newdev.eecs.harvard.edu (Postfix, from userid 501) id 2D22AD7A76F; Thu, 28 Jul 2011 08:19:04 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: draft-housley-two-maturity-levels
Message-Id: <20110728121904.2D22AD7A76F@newdev.eecs.harvard.edu>
Date: Thu, 28 Jul 2011 08:19:04 -0400 (EDT)
From: sob@harvard.edu (Scott O. Bradner)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 12:19:05 -0000

this is better than the last version but

1/ I still see no reason to think that this change will cause any
significant change in the percent of Proposed Standards that move up the
(shorter) standards track since the proposal does nothing to change the
underlying reasons that people do not expend the effort needed to
advance documents

2/ one of the big issues with the PS->DS step is understanding what
documentation is needed to show that there are the interoperable
implementations and to list the unused features - it would help a lot to
provide some guidance (which I did not do in 2026 - as I have been
reminded a number of times :-) ) as to just what process is to be
followed

could be
	a spread sheet showing features & implementations
	an assertion by the person proposing the advancement that the
requirements have been met
or something in between

Scott

From pch-b2B3A6689@u-1.phicoh.com  Thu Jul 28 05:20:27 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 0B18421F8C79 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 05:20:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aB5fQ0tZoK7H for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 05:20:26 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo-6to4.hq.phicoh.net [IPv6:2002:8225:f03:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id 5695321F8C7A for <ietf@ietf.org>; Thu, 28 Jul 2011 05:20:24 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #66) id m1QmPZd-0001iIC; Thu, 28 Jul 2011 14:20:21 +0200
Message-Id: <m1QmPZd-0001iIC@stereo.hq.phicoh.net>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: "6to4 damages the Internet" (was Re: draft-ietf-v6ops-6to4-to-historic (yet again)) 
From: Philip Homburg <pch-ietf@u-1.phicoh.com>
Sender: pch-b2B3A6689@u-1.phicoh.com
References: <m1QmLN6-0001imC@stereo.hq.phicoh.net> <51E12FC1-6DE1-479C-AAD4-1877274F96A0@network-heretics.com> 
In-reply-to: Your message of "Thu, 28 Jul 2011 07:50:38 -0400 ." <51E12FC1-6DE1-479C-AAD4-1877274F96A0@network-heretics.com> 
Date: Thu, 28 Jul 2011 14:20:07 +0200
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, 28 Jul 2011 12:20:27 -0000

In your letter dated Thu, 28 Jul 2011 07:50:38 -0400 you wrote:
> In general, all of a host's addresses (at least, those in the same
> preference class in the address selection algorithm) need to work
> equally well from everywhere.
> 
> But even that might not be sufficient.   Fred Baker has recently
> been citing a different example of the same problem:  Imagine a
> future where hosts on a network have both v6 and legacy v4 through
> stateful NAT.  Because the v6 connection works well most of the
> time, hosts tend to choose v6 destinations, and sites reduce the
> capacity of their NATs over time.  Then the v6 connection fails,
> and suddenly everything falls back to v4, and the connections
> through NAT also fail for lack of sufficient capacity to handle
> the load.

I'm sure some manager will just require this to work. But I would say that
this is just supposed to fail.

If you had in the past just an IPv4 connection and it went down, there would
be no Internet access. Same thing in the future. If your IPv6 connection goes
down you don't have an Internet conenction.

It would be different if the NAT was there just to connect to a very specific
collection of legacy IPv4 sites. But that can be solved easily but just
routing those IPv4 prefixes to the NAT. 

If you want the NAT to provide full redundancy, then it has to be scaled to
accept full load. Otherwise, no IPv6 just means no Internet. Very simple.

> > We want large scale deployment of IPv6 today not some time in the future
> > when we finally figured out address selection. And that means that today we
> > have to make sure that users don't end up with unreliable IPv6 connections.
> 
> If you make the constraint that nobody can use IPv6 at all until
> the IPv6 connections work as well in all cases as the IPv4 connections,
> that creates a huge barrier to the universal deployment of IPv6 -
> which already has enough barriers as it is.

To some extent that is exactly the way it is. 

Suppose that a significant fraction of popular websites would have IPv6
addresses that don't actually work. Then essentially no ISP would enable IPv6
for their customers because their customers would suffer.

At the moment, most servers that do have IPv6 addresses seem to actually
support IPv6 so this doesn't seem to be a big problem.

But we don't know what the future might bring. If there would be a sudden
rush of servers that have PMTU problems, then we could have a very serious
problem. 

> A less onerous constraint is that less reliable IPv6 connections
> don't get used in preference to more reliable IPv4 connections.
> We're lucky in the case of 6to4 in that it has a well-known prefix
> that allows the traffic to be distinguished from other v6 traffic.
> But it's still necessary to manage expectations about IPv4 as a
> fallback path.

Happy Eyeballs can solve a lot of problems where a connection will fail
completely or have a high latency. But HE support is far from universal and
so far experience is limited to TCP.

But it doesn't do anything for PMTU problems. 

It also doesn't do anything for real-time streaming applications.



From pch-b2B3A6689@u-1.phicoh.com  Thu Jul 28 05:45:29 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 EDC6121F8669 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 05:45:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_00=-2.599, GB_I_LETTER=-2, 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 NOQsdz0WjvGt for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 05:45:23 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id A139021F8C2E for <ietf@ietf.org>; Thu, 28 Jul 2011 05:45:22 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #66) id m1QmPxo-0001iIC; Thu, 28 Jul 2011 14:45:20 +0200
Message-Id: <m1QmPxo-0001iIC@stereo.hq.phicoh.net>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: "6to4 damages the Internet" (was Re: draft-ietf-v6ops-6to4-to-historic (yet again)) 
From: Philip Homburg <pch-ietf@u-1.phicoh.com>
Sender: pch-b2B3A6689@u-1.phicoh.com
In-reply-to: Your message of "Thu, 28 Jul 2011 17:08:01 +0900 ." <4E3118E1.5090107@necom830.hpcl.titech.ac.jp> 
Date: Thu, 28 Jul 2011 14:45:13 +0200
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 12:45:30 -0000

In your letter dated Thu, 28 Jul 2011 17:08:01 +0900 you wrote:
>Philip Homburg wrote:
>> I think the problem is that we don't know how to do 'proper' address
>> selection.
>
>I know and it's trivially easy.
>
>11 years ago in draft-ohta-e2e-multihoming-00.txt, I wrote:
>
>   End systems (hosts) are end systems. To make the end to end principle
>   effectively work, the end systems must have all the available
>   knowledge to make decisions by the end systems themselves.
>
>   With regard to multihoming, when an end system want to communicate
>   with a multihomed end system, the end system must be able to select
>   most appropriate (based on the local information) destination address
>   of the multihomed end system.
>
>which means an end system should have a full routing table, IGP
>metrics in which tell the end system what is the best address of
>its multihomed peer. Full routing table should and can, of course,
>be small.

Even in the unlikely case that it would be feasible to give every host a
complete copy of the DFZ routing table... That still would leave a lot of
issues open...
1) End-to-end latency. Maybe some future generation BGP provides that, but
   that doesn't help now.
2) For 6to4, the use of anycase. You probably need a link-state routing 
   protocol to allow a host to figure out which relays are going to be used on
   a give path.
3) Filters in firewalls. I'd love to see a routing protocol that reports the
   settings of all firewalls in the world :-)
4) Other performance metrics, like jitter, packets loss, etc.

Maybe you can do some experiments and report on how well your draft works for
deciding when to prefer a 6to4 address over IPv4.



From Martin.Thomson@commscope.com  Thu Jul 28 06:10:40 2011
Return-Path: <Martin.Thomson@commscope.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0A1321F8A91 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 06:10:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.573
X-Spam-Level: 
X-Spam-Status: No, score=-2.573 tagged_above=-999 required=5 tests=[AWL=0.026,  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 T8tRJkDp-GyM for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 06:10:37 -0700 (PDT)
Received: from cdcsmgw02.commscope.com (fw.commscope.com [198.135.207.129]) by ietfa.amsl.com (Postfix) with ESMTP id 9290F21F8A6F for <ietf@ietf.org>; Thu, 28 Jul 2011 06:10:37 -0700 (PDT)
X-AuditID: 0a0404e9-b7cc4ae00000074e-d7-4e315fd5f6e5
Received: from ACDCE7HC2.commscope.com ( [10.86.20.103]) by cdcsmgw02.commscope.com (Symantec Brightmail Gateway) with SMTP id E6.F1.01870.5DF513E4; Thu, 28 Jul 2011 08:10:46 -0500 (CDT)
Received: from SISPE7HC1.commscope.com (10.97.4.12) by ACDCE7HC2.commscope.com (10.86.20.103) with Microsoft SMTP Server (TLS) id 8.3.159.2; Thu, 28 Jul 2011 08:10:36 -0500
Received: from SISPE7MB1.commscope.com ([fe80::9d82:a492:85e3:a293]) by SISPE7HC1.commscope.com ([fe80::8a9:4724:f6bb:3cdf%10]) with mapi; Thu, 28 Jul 2011 21:10:33 +0800
From: "Thomson, Martin" <Martin.Thomson@commscope.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF discussion list <ietf@ietf.org>
Date: Thu, 28 Jul 2011 21:10:30 +0800
Subject: RE: Kevin's second byte question
Thread-Topic: Kevin's second byte question
Thread-Index: AcxMqRnHLF1gSYXnQwSHYFARWpwx3AAfl49Q
Message-ID: <8B0A9FCBB9832F43971E38010638454F040D2C3919@SISPE7MB1.commscope.com>
References: <4E308B21.1090305@gmail.com>
In-Reply-To: <4E308B21.1090305@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-Brightmail-Tracker: AAAAAA==
Cc: "kfall@cs.Berkeley.EDU" <kfall@cs.Berkeley.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, 28 Jul 2011 13:10:41 -0000

On 2011-07-27 at 18:03:13, Brian E Carpenter wrote:
> The second byte in an IPv4 header is called the Differentiated=20
> Services Field.

I believe that this has been obsoleted by RFC 5241.

From dhc2@dcrocker.net  Thu Jul 28 06:18:48 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 8953721F8C5D for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 06:18: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 J1dPiuqENYbz for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 06:18:47 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8505621F8C59 for <ietf@ietf.org>; Thu, 28 Jul 2011 06:18:47 -0700 (PDT)
Received: from [172.16.59.36] (modemcable252.155-70-69.static.videotron.ca [69.70.155.252]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p6SDIbJs006650 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Jul 2011 06:18:44 -0700
Message-ID: <4E3161AB.9010007@dcrocker.net>
Date: Thu, 28 Jul 2011 09:18:35 -0400
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Why the IESG needs to review everything...
References: <4E308D64.3030804@gmail.com> <4E30927D.50808@dcrocker.net> <4E30B250.3030807@gmail.com>
In-Reply-To: <4E30B250.3030807@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 28 Jul 2011 06:18:45 -0700 (PDT)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 13:18:48 -0000

Brian,


On 7/27/2011 8:50 PM, Brian E Carpenter wrote:
> Expected is one thing; but even the IESG's own rules do not *require* this.
> http://www.ietf.org/iesg/voting-procedures.html

First, the written rules do not matter much, if actual behavior runs contrary.

Second, expectations constitute a real burden on people, and the discussion was 
about the actual burden.  The claim that ADs are expected to read all 
submissions has been consistent for some years, from many different folk 
including ADs.


> I certainly never like ballotting NO OBJECTION unless I had at least
> skimmed the draft and read at least one positive review. I'm sure I
> never ballotted YES without a careful reading.

On matters of human behavior, one of the continuing challenges in the IETF is 
the pervasive tendency for a sole speaker to cite their own behavior as if it 
were representative of a broader population.  (The formal term is "sampling 
error", I believe.)

There is a basic difference between a single exemplar versus the aggregated 
behavior of a population.  The former is useful to demonstrate an existence 
proof, such as an exception.  It says nothing about the behavior of others in a 
group.

In other words Brian, you are a great guy.  You were diligent, reasonable and 
balanced when you held these positions and asserted your authority.  No one 
should consider criticizing any aspect of how you did the job.

Forgive me, but none of that matters for this discussion.  Your own behavior, 
back then, is irrelevant to this discussion, since no one said that all ADs have 
always behaved a certain way.

What is relevant is the /current/ demands on ADs.


>> Is all of this effort justified if exactly one minor error is found each
>> year? Two?  One major?  What is that /actual/ improvement that this
>> process produces?  What thresholds should apply?
>
> It depends on what you mean by minor or major, but my experience as an
> author is that I get valuable comments from the IESG that definitely
> improve the document, even after all the comments one gets from
> WGLC and IETF LC and the various review teams.

Brian, you missed the point motivating my questions:  I'm suggesting that 
demanding the retention of massive demands on ADs and the imposition of 
significant procedural burden on working groups and authors warrant analysis.

Do the analysis, please.  Make it balanced. Look at pros and cons.  Answer your 
own question, while formulating a serious case for a situation that creates 
chronic problems.  The complaints about the current arrangement are not new or 
isolated.  Unfortunately, the defense of the arrangement is typically in the 
style you are giving.

Besides the skewed perspective -- oh, we caught one error, two years ago, so 
it's worth burdening everyone all the time -- the perspective ignores two key 
points, observed by many folk:

    1.  We have many sources of reviews; the reviewing capabilities of an AD are 
likely to be good, but not better than many others.

    2.  In spite of all the wonderful reviewing done by ADs, errors still get 
through; so the fact that some ADs, sometimes, might catch an important error 
ignores all the others they miss.

Again, Brian:

    Offer a cost/benefit formula and then factor in the known, considerable, 
current costs and demonstrate that we are deriving the requisite benefit.  Try 
to explore real-world behaviors, rather than theoretical hopes.


> Why? My guess is that it's because that the buck stops with the IESG - and

Except that it doesn't stop with the IESG.  (Actually, I don't really know what 
it means to claim it stops with the IESG, and I suspect there are valid claims 
that it stops in a variety of other places.)  Many conditions and actions, over 
a long period of time, are required to make a specification succeed.

It might be interesting for you to document examples of repercussions on the 
IESG for having approved a terrible specification.

At the least, please explain what your assertion means, exactly, and then 
explain what the repercussions are on the IESG when they make the egregious 
error of letting a serious error get published.

This sort of discussion calls for restraint from using comforting, Trumanesque 
catch-phrases.

There is, indeed, a current model that places the personal assessments of ADs on 
a pedestal of power.  It invites mere mortals to work under the myth that they, 
alone, carry the burden of keeping the Internet safe from bogus technologies. 
It's a silly myth, but it's the one that currently in force.

      A more tractable model is that ADs need a manageable workload and a modest 
set of responsibilities, balancing what is demanded of them with the practical 
benefit it provides and the costs to them (and us) that are incurred.

      Further, the model needs to be comfortable with having everyone make lots 
of errors, in spite of their being diligent.


> that automatically makes people more conscientious. Everybody else can
> <shrug>; the final approving body can't.
>
> In other words, if you "fix" this "bug" by moving the final responsibility
> elswehere, you will just move the problem to the same place.

Perhaps you missed the trigger to this thread, which had to do with processing 
bottlenecks and inappropriate Discusses?


>> That is, the presumption in your comment -- and your comment represents
>> a broad constituency in the IETF -- is that reviewing only has positive
>> effects of the review
>
> Of course, there can be cases where that is not so - in fact, that's
> the main reason that the IESG defined the DISCUSS criteria a few years
> ago.

Have you seen a pattern of having a Discuss cite the criterion that justifies 
it?  I haven't.  It might be interesting to attempt an audit of Discusses, 
against the criteria...


>> It well might be true that omitting the AD reviews would increase the
>> number. By how much?  To what effect?
>
> Hard to tell. But it would amount to giving the IESG secretary a large
> rubber stamp *unless* the final responsibility was explicitly moved
> elsewhere.

Herein lies the real problem:  As with many process and structure discussions in 
the IETF, folk often see only a simplistic, binary choice between whatever they 
prefer, versus something akin to chaos.

The world is more nuanced than that, and the choices more rich.

Here is a small counter-example to your sole alternatives of status quo or 
rubber stamp:

      Imagine a process which requires a range of reviews and requires ADs to 
take note of the reviews and the community support-vs-objection.

      Imagine that the job of the ADs is to assess these and to block proposals 
that have had major, unresolved problems uncovered or that lack support, and to 
approve ones that have support and lack known, major deficiencies as documented 
by the reviews.

That ain't a rubber stamp, Brian.

d/


-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From rjsparks@nostrum.com  Thu Jul 28 06:19:50 2011
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A83921F8C93 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 06:19:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000,  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 mOC1AC3C6aI9 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 06:19:49 -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 6B91E21F8C5D for <ietf@ietf.org>; Thu, 28 Jul 2011 06:19:48 -0700 (PDT)
Received: from dhcp-1534.meeting.ietf.org (dhcp-1534.meeting.ietf.org [130.129.21.52]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p6SDJjAD079664 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 28 Jul 2011 08:19:46 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Subject: Re: draft-housley-two-maturity-levels
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <20110728121904.2D22AD7A76F@newdev.eecs.harvard.edu>
Date: Thu, 28 Jul 2011 09:19:45 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <12B69DB8-AFDD-4C40-BC9A-0A8158D9F7C0@nostrum.com>
References: <20110728121904.2D22AD7A76F@newdev.eecs.harvard.edu>
To: "Scott O. Bradner" <sob@harvard.edu>
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass (nostrum.com: 130.129.21.52 is authenticated by a trusted mechanism)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 13:19:50 -0000

Scott -

Didn't RFC 5657 address your point 2?

The current proposal no longer requires this report during advancement, =
but it does not disallow it.
I hope it's obvious that I believe these reports are valuable, but I am =
willing to accept the proposed
structure, with the hope and expectation that  communities that are =
serious about producing and=20
refining protocols will be producing these reports anyhow.

RjS

On Jul 28, 2011, at 8:19 AM, Scott O. Bradner wrote:

>=20
> this is better than the last version but
>=20
> 1/ I still see no reason to think that this change will cause any
> significant change in the percent of Proposed Standards that move up =
the
> (shorter) standards track since the proposal does nothing to change =
the
> underlying reasons that people do not expend the effort needed to
> advance documents
>=20
> 2/ one of the big issues with the PS->DS step is understanding what
> documentation is needed to show that there are the interoperable
> implementations and to list the unused features - it would help a lot =
to
> provide some guidance (which I did not do in 2026 - as I have been
> reminded a number of times :-) ) as to just what process is to be
> followed
>=20
> could be
> 	a spread sheet showing features & implementations
> 	an assertion by the person proposing the advancement that the
> requirements have been met
> or something in between
>=20
> Scott
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From stpeter@stpeter.im  Thu Jul 28 06:52:39 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 3D53121F8BDC for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 06:52:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.55
X-Spam-Level: 
X-Spam-Status: No, score=-102.55 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oXATbeOm7Zy3 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 06:52:36 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 825D721F8BE5 for <ietf@ietf.org>; Thu, 28 Jul 2011 06:52:34 -0700 (PDT)
Received: from dhcp-13ac.meeting.ietf.org (unknown [198.135.0.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 4E0E0410E8; Thu, 28 Jul 2011 07:53:38 -0600 (MDT)
Message-ID: <4E3169A0.1050807@stpeter.im>
Date: Thu, 28 Jul 2011 09:52:32 -0400
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Last Call: <draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <4E30EE32.3020404@gmail.com>
In-Reply-To: <4E30EE32.3020404@gmail.com>
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
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: Thu, 28 Jul 2011 13:52:39 -0000

On 7/28/11 1:05 AM, Mykyta Yevstifeyev wrote:
> Hello,
> 
> The new version is obviously shorter, but it omits some points.  With
> eliminating of DS level, RFC 5657 makes no sense more. 

Wrong. The *title* needs to be adjusted, but mutatis mutandis the
general advice is useful.

> It should be
> obsoleted and moved to Historic by your document, if IESG decides to
> eliminate the requirement for interoperability documentation, which I am
> opposed to (see my LC comments to -06).

I see no reason to move RFC 5657 to Historic.

> Another issue is STD numbers.  Mentioning that they are still assigned
> to ISs in Section 2.2 should be fine.

The STD issue is orthogonal.

> Also, Section 3.3:
> 
>>     (2) At any time after two years from the approval of this document as
>>         a BCP, the IESG may choose to reclassify any Draft Standard
>>         document as Proposed Standard.
> 
> Won't such action be allowed after 2 years from approval?

That's what the text says, no?

Peter

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



From eburger-l@standardstrack.com  Thu Jul 28 07:03:07 2011
Return-Path: <eburger-l@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 1B4AF21F8C52 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 07:03:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=0.113,  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 VSMkeXFnPeuR for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 07:03:06 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 6049521F8C32 for <ietf@ietf.org>; Thu, 28 Jul 2011 07:03:06 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com;  h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=AyAtV9Yq1r5Zj5cxOOF3mvAWmC4eXYtgqRs5DtRBfxj2eqh+DmSWICH6EtfLsUnAdBLz/lUpkCSjuvGYHce0ZDwo7XxfZPDohfsKDmkLF+J8PUVUDglw4EUbrQG02XAa;
Received: from dhcp-63da.meeting.ietf.org ([130.129.99.218]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger-l@standardstrack.com>) id 1QmRB2-00019u-R0; Thu, 28 Jul 2011 07:03:05 -0700
Subject: Re: draft-housley-two-maturity-levels
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <12B69DB8-AFDD-4C40-BC9A-0A8158D9F7C0@nostrum.com>
Date: Thu, 28 Jul 2011 10:03:01 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0D43A851-C57B-484F-ADDD-BBD7A412689C@standardstrack.com>
References: <20110728121904.2D22AD7A76F@newdev.eecs.harvard.edu> <12B69DB8-AFDD-4C40-BC9A-0A8158D9F7C0@nostrum.com>
To: Bradner Scott <sob@harvard.edu>
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: 
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 14:03:07 -0000

And the real question is, are we moving forward? I think that we are not =
moving as far as we originally wanted. However, I offer we are moving a =
baby step forward, and as such is worthwhile doing.

On Jul 28, 2011, at 9:19 AM, Robert Sparks wrote:

> Scott -
>=20
> Didn't RFC 5657 address your point 2?
>=20
> The current proposal no longer requires this report during =
advancement, but it does not disallow it.
> I hope it's obvious that I believe these reports are valuable, but I =
am willing to accept the proposed
> structure, with the hope and expectation that  communities that are =
serious about producing and=20
> refining protocols will be producing these reports anyhow.
>=20
> RjS
>=20
> On Jul 28, 2011, at 8:19 AM, Scott O. Bradner wrote:
>=20
>>=20
>> this is better than the last version but
>>=20
>> 1/ I still see no reason to think that this change will cause any
>> significant change in the percent of Proposed Standards that move up =
the
>> (shorter) standards track since the proposal does nothing to change =
the
>> underlying reasons that people do not expend the effort needed to
>> advance documents
>>=20
>> 2/ one of the big issues with the PS->DS step is understanding what
>> documentation is needed to show that there are the interoperable
>> implementations and to list the unused features - it would help a lot =
to
>> provide some guidance (which I did not do in 2026 - as I have been
>> reminded a number of times :-) ) as to just what process is to be
>> followed
>>=20
>> could be
>> 	a spread sheet showing features & implementations
>> 	an assertion by the person proposing the advancement that the
>> requirements have been met
>> or something in between
>>=20
>> Scott
>> _______________________________________________
>> 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 stpeter@stpeter.im  Thu Jul 28 07:06:58 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 7BAB221F8AD3 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 07:06:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.552
X-Spam-Level: 
X-Spam-Status: No, score=-102.552 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w0ZmLuW1552A for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 07:06:57 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id E46DC21F876F for <ietf@ietf.org>; Thu, 28 Jul 2011 07:06:57 -0700 (PDT)
Received: from dhcp-13ac.meeting.ietf.org (unknown [198.135.0.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id A450D410E8; Thu, 28 Jul 2011 08:08:01 -0600 (MDT)
Message-ID: <4E316D00.6090900@stpeter.im>
Date: Thu, 28 Jul 2011 10:06:56 -0400
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Eric Burger <eburger-l@standardstrack.com>
Subject: Re: draft-housley-two-maturity-levels
References: <20110728121904.2D22AD7A76F@newdev.eecs.harvard.edu> <12B69DB8-AFDD-4C40-BC9A-0A8158D9F7C0@nostrum.com> <0D43A851-C57B-484F-ADDD-BBD7A412689C@standardstrack.com>
In-Reply-To: <0D43A851-C57B-484F-ADDD-BBD7A412689C@standardstrack.com>
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Bradner Scott <sob@harvard.edu>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 14:06:58 -0000

On 7/28/11 10:03 AM, Eric Burger wrote:
> And the real question is, are we moving forward? I think that we are
> not moving as far as we originally wanted. However, I offer we are
> moving a baby step forward, and as such is worthwhile doing.

We are more closely aligning our documentation with our organizational
running code. All other things being equal, that's a good thing. That
doesn't imply that all of our organizatioal running code is bug-free. We
could have a broader conversation about the latter, but IMHO that's
outside the scope of this baby step forward.

Peter

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



From housley@vigilsec.com  Thu Jul 28 07:13:57 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 4901621F8C88 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 07:13:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.511
X-Spam-Level: 
X-Spam-Status: No, score=-102.511 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B2084s2UWv0J for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 07:13:56 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 2B54421F8C9D for <ietf@ietf.org>; Thu, 28 Jul 2011 07:13:56 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id E1A07F24043 for <ietf@ietf.org>; Thu, 28 Jul 2011 10:13:56 -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 IIrlJzir9irX for <ietf@ietf.org>; Thu, 28 Jul 2011 10:13:54 -0400 (EDT)
Received: from dhcp-227d.meeting.ietf.org (dhcp-227d.meeting.ietf.org [130.129.34.125]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id DF782F24037 for <ietf@ietf.org>; Thu, 28 Jul 2011 10:13:55 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Concerns about the recent IPR Statement from Alcatel Lucent Related to RFC 6073
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <E0A4D735-0E49-471F-843E-0314AD69F2C6@vigilsec.com>
Date: Thu, 28 Jul 2011 10:13:54 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DF09DA13-B039-45F8-AF62-99B586C0E7D3@vigilsec.com>
References: <20110531163726.28776.73969.idtracker@ietfa.amsl.com> <EC39C3A2-888B-4A62-952F-39712562D263@ietf.org> <E0A4D735-0E49-471F-843E-0314AD69F2C6@vigilsec.com>
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, 28 Jul 2011 14:13:57 -0000

I want to make the IETF community aware that Alcatel Lucent has =
withdrawn their original IPR disclosure regarding RFC 6073, and Alcatel =
Lucent has submitted a replacement statement: =
https://datatracker.ietf.org/ipr/1589/

I want to highlight one thing that is unique in this particular =
disclosure.  A "non-assert" license to all patents held by Alcatel =
Lucent necessary to implement RFC 6073 is available if requested before =
the end of 2011.  License to these same patents will be available after =
the end of the year with the possibility of a royalty or fee.=20

Russ

On Jun 2, 2011, at 10:06 AM, Russ Housley wrote:

> 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.
>=20
> Yesterday, I wrote to Alcatel Lucent about their recent IPR statement, =
and asked them to consider a revised IPR disclosure to correct this =
situation.
>=20
> 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.
>=20
> Russ
>=20
>=20
> On May 31, 2011, at 12:37 PM, IETF Secretariat wrote:
>=20
>> 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 moore@network-heretics.com  Thu Jul 28 07:20:35 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 659F621F8A96 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 07:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.677
X-Spam-Level: 
X-Spam-Status: No, score=-3.677 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1QvvfId70-GJ for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 07:20:34 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 8C43D21F87D9 for <ietf@ietf.org>; Thu, 28 Jul 2011 07:20:34 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id D299120F29; Thu, 28 Jul 2011 10:20:33 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute6.internal (MEProxy); Thu, 28 Jul 2011 10:20:33 -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=CQVflbaEhGJuBGLEOjftszPJUq0=; b=LN FWF5RkfSR3OtBqNDpMJqyqPb3TVLZzlce0XGpcF0WwvwVsKX9jwbSR2zoXIx38pV 3j4T/nydxfKIuvDGBWgbGB16hrUcWIgdhGb6bAuc7oa5fsUWqf5z1PJo0jg40OnU //trWiKM9z0ba8TaRVuyfpDJo+/oBFuircWvZLFtQ=
X-Sasl-enc: K1PZtaNa0ZhGuUTmXKcPwZ9FJ2aMGjhwnBDuNKvfKwB4 1311862833
Received: from dhcp-3795.meeting.ietf.org (dhcp-3795.meeting.ietf.org [130.129.55.149]) by mail.messagingengine.com (Postfix) with ESMTPSA id 7B03F45541E; Thu, 28 Jul 2011 10:20:33 -0400 (EDT)
Subject: Re: draft-housley-two-maturity-levels
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: <4E316D00.6090900@stpeter.im>
Date: Thu, 28 Jul 2011 10:20:33 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <839F8D5B-B64D-4842-8AC2-72C637942BA8@network-heretics.com>
References: <20110728121904.2D22AD7A76F@newdev.eecs.harvard.edu> <12B69DB8-AFDD-4C40-BC9A-0A8158D9F7C0@nostrum.com> <0D43A851-C57B-484F-ADDD-BBD7A412689C@standardstrack.com> <4E316D00.6090900@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1084)
Cc: IETF <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>, Bradner Scott <sob@harvard.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 14:20:35 -0000

On Jul 28, 2011, at 10:06 AM, Peter Saint-Andre wrote:

> On 7/28/11 10:03 AM, Eric Burger wrote:
>> And the real question is, are we moving forward? I think that we are
>> not moving as far as we originally wanted. However, I offer we are
>> moving a baby step forward, and as such is worthwhile doing.
>=20
> We are more closely aligning our documentation with our organizational
> running code. All other things being equal, that's a good thing.

Hmm.  I've long believed that :

- trying to document existing practice
- trying to document desirable practice

are both worthwhile endeavors, as long as you don't try to do both at =
the same time.  When you try to do both at the same time, there is a =
conflict.

If someone wants to write a document that says we generally follow RFC =
2026, except that:

- drafts hardly ever advance to Draft Standard and even more rarely to =
Full Standard, unless there is significant use of the protocol and there =
are bugs that need to be fixed (in which case the ability to advance can =
sometimes serve as an incentive of sorts)
- we have never been serious about periodic review of standards and we =
don't have enough time/energy to do that
- we've never really nailed down what Historic meant, and when it was =
appropriate to use it

etc.

that would be a fine thing.

And real changes to the process, say to bring in formal cross review =
earlier, to clarify the nature of community consensus and the need for =
it, etc. might also be a fine thing.  Unfortunately, such discussions =
are always contentious and difficult, because they affect the whole =
community, but they also attract a lot of interests from individuals =
with particularly unique axes to grind.  So we keep trying to fix the =
substantive problems with incremental changes.  I forget who it was who =
said yesterday that we can't really do that, but I certainly agree with =
him.

Meanwhile, it's not clear to me that simply changing from one document =
that we don't strictly follow, to another document that we won't follow =
much better, is helpful.  And I don't think IETF's problems with =
standards quality or process can be addressed merely by changes to the =
number of maturity levels.  That strikes me as a bit like rearranging =
deck chairs...it might make people feel better but is of little =
consequence.

In other words, I'm not convinced that this change will do much harm, =
but I'm also not convinced that it will help much.  And yet we keep =
flogging this idea...

Keith





From dworley@avaya.com  Thu Jul 28 07:24:59 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 C014D21F8CAD for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 07:24:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.463
X-Spam-Level: 
X-Spam-Status: No, score=-103.463 tagged_above=-999 required=5 tests=[AWL=0.136, 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 4YzibHDPY2Xs for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 07:24:58 -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 F016221F8CA7 for <ietf@ietf.org>; Thu, 28 Jul 2011 07:24:57 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAN9wMU7GmAcF/2dsb2JhbAA0AQEBAQIBFHEFDAIBCQ0IPRQjLgEBBQEOCAwNDqcxd4h8pk8CnAaFYl8EmB6ER4cU
X-IronPort-AV: E=Sophos;i="4.67,282,1309752000"; d="scan'208";a="259238407"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 28 Jul 2011 10:24:35 -0400
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 28 Jul 2011 10:22:08 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Thu, 28 Jul 2011 10:24:34 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Michel Py <michel@arneill-py.sacramento.ca.us>, james woodyatt <jhw@apple.com>
Date: Thu, 28 Jul 2011 10:20:26 -0400
Subject: RE: IPv6 traffic distribution
Thread-Topic: IPv6 traffic distribution
Thread-Index: AcxMyb2ObIFMVOKaQjiRxZM0R1OXgQABADawABjwGZQ=
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F57CE@DC-US1MBEX4.global.avaya.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net><4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com><13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net><4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com><20110727023833.5C72D1232958@drugs.dv.isc.org><m1QlzXt-0001gSC@stereo.hq.phicoh.net> <2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com>, <392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local>
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 14:25:00 -0000

> From: Michel Py [michel@arneill-py.sacramento.ca.us]
>=20
> http://tinyurl.com/5u3eorn
> "France is responsible for more than half of current IPv6 traffic
> worldwide"; I can positively confirm that Free (AS12322) that
> contributes to most of the French IPv6 native hits is delivering
> "native" IPv6 to their eyeballs using 6rd and that they are indeed the
> 800-pound gorilla of French IPv6 traffic, no contest.

Also:

    One reason that may explain France=92s early adoption of IPv6 is
    that France has formed a multitude of valuable IPv6-based
    associations on the past decade. This activity has greatly
    contributed to the acquisition and dissemination of IPv6
    knowledge. These organizations consist of the G6, whose primary
    task is IPv6 experimentation and information exchange. The G6 was
    founded in 1995 by researchers in academia and industry. G6=92s
    overall goal is the gradual building of a new infrastructure
    required for the Internet to survive. The G6, like Cisco, is
    focused on an effective and seamless transition IPv4 to IPv6. It
    is the primary catalyst for advances in IPv6 networking in France.

In other words, very early (15 years ago), the French Internet
community formed an organization to move IPv6 forward through
coordination and persuasion rather than by preaching from the outside.

In the larger Internet, I've seen a remarkable absence of that sort
of coordination.

Dale

From chair@ietf.org  Thu Jul 28 07:28:36 2011
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D3FA21F8C1D; Thu, 28 Jul 2011 07:28:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.597
X-Spam-Level: 
X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NORMAL_HTTP_TO_IP=0.001, USER_IN_WHITELIST=-100, WEIRD_PORT=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 lyZPGmDZ2TXk; Thu, 28 Jul 2011 07:28:35 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:1112:1::14]) by ietfa.amsl.com (Postfix) with ESMTP id CFFC521F8C5C; Thu, 28 Jul 2011 07:28:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id C8C9E1E2129; Thu, 28 Jul 2011 07:28:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w6U0kXvBIqXf; Thu, 28 Jul 2011 07:28:35 -0700 (PDT)
Received: from [IPv6:2001:df8::32:6233:4bff:fe20:eb18] (unknown [IPv6:2001:df8:0:32:6233:4bff:fe20:eb18]) by c1a.amsl.com (Postfix) with ESMTPSA id 5385C1E2128; Thu, 28 Jul 2011 07:28:35 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-Priority: 1
Subject: Re: IPv6 PCP demo in room 2000 D
Date: Thu, 28 Jul 2011 10:28:33 -0400
To: 81all@ietf.org, IETF <ietf@ietf.org>
Message-Id: <8FECC729-1905-43DB-9364-490C2D3F1A6C@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: Thu, 28 Jul 2011 14:28:36 -0000

There has been a PCP Demo from during the week.  Visitors of the Demo =
have entered their cards and contacts in a raffle box to win a =
Huawei-sponsored iPAD2.  I have agreed to draw the winner during the =
first afternoon break today in the terminal room (2000D).  Two hours =
will be given to the winner to shown up, if the person cannot be =
connected, a runner-up drawn at the same time will get the prize.

Good luck,
Russ


-----Original Message-----
From: 81all-bounces@ietf.org [mailto:81all-bounces@ietf.org] On Behalf =
Of xiaohong.deng@orange-ftgroup.com
Sent: Sunday, July 24, 2011 9:26 PM
To: adurand@juniper.net; 81all@ietf.org
Subject: Re: [81all] IPv6 PCP demo in room 2000 D

It will be a joint demo by ISC (software based), and Huawei -FT (device
based) on Monday and Wednesday morning.

FT-Huawei device based demo will be on site during the whole meeting
week, so you can drop by anytime at your convenience.

Our prize iPad 2, sponsored by Huawei, is ready now. Are you the lucky
winner? ;)

Xiaohong


> Hi folks,
>=20
> During IETF 81, please come and see the Port Control=20
> Protocol (PCP) demonstration in Room 2000 D.=20
>=20
> Leave your name and contact information by the Thursday=20
> afternoon break to be entered into a drawing for an iPad 2.=20
> Russ Housley will draw the winner during the break.
>=20
> Check it out on our website at: http://130.129.48.23:35328/=20
> <http://130.129.48.23:35328/> . The lucky winner will be=20
> announced on our Web site!=20
>=20
> Good Luck!=20
>=20
> Xiaohong Deng
> (xiaohong.deng@orange-ftgroup.com)


From stpeter@stpeter.im  Thu Jul 28 07:32: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 6EADB21F8BC1 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 07:32:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level: 
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DLEKmvLkKgLm for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 07:32:09 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id D5D1621F8B80 for <ietf@ietf.org>; Thu, 28 Jul 2011 07:32:09 -0700 (PDT)
Received: from dhcp-13ac.meeting.ietf.org (unknown [198.135.0.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 08EB9410E8; Thu, 28 Jul 2011 08:33:02 -0600 (MDT)
Message-ID: <4E3172DD.1060005@stpeter.im>
Date: Thu, 28 Jul 2011 10:31:57 -0400
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: draft-housley-two-maturity-levels
References: <20110728121904.2D22AD7A76F@newdev.eecs.harvard.edu> <12B69DB8-AFDD-4C40-BC9A-0A8158D9F7C0@nostrum.com> <0D43A851-C57B-484F-ADDD-BBD7A412689C@standardstrack.com> <4E316D00.6090900@stpeter.im> <839F8D5B-B64D-4842-8AC2-72C637942BA8@network-heretics.com>
In-Reply-To: <839F8D5B-B64D-4842-8AC2-72C637942BA8@network-heretics.com>
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Bradner Scott <sob@harvard.edu>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 14:32:10 -0000

On 7/28/11 10:20 AM, Keith Moore wrote:

> In other words, I'm not convinced that this change will do much harm,
> but I'm also not convinced that it will help much. 

I don't disagree.

> And yet we keep
> flogging this idea...

But we always flog the easy issues, rather than facing the tough ones.

It would be good to start talking about the tough issues, but IMHO there
is some value in settling on two maturity levels as well.

Peter

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



From samirs.lists@gmail.com  Thu Jul 28 07:47:59 2011
Return-Path: <samirs.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 2EA0B21F8CAE for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 07:47:59 -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 n67MWv9S8Q1O for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 07:47:58 -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 140F521F8C78 for <ietf@ietf.org>; Thu, 28 Jul 2011 07:47:54 -0700 (PDT)
Received: by gxk19 with SMTP id 19so2264858gxk.31 for <ietf@ietf.org>; Thu, 28 Jul 2011 07:47:53 -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=atsASzofVK2wW+ApRxPfHBvmK4njjL53Ubwklf9/+xA=; b=kFuj1OuNotFWFeOJCizsLIHaUG8YMP9fTSeGtzAE/keIrbQ5u2zJoXlFROiuhs9iyG wBBCaZIgY2e32Hs0/xPH85BvbzTAZoPiUh5SeK9kqwrklB2haE/LHSrYxm8Ah9DBsKRa 63E5UXdwJgq6vuapSqVnVsZ3EF1gp7VwtQlPo=
MIME-Version: 1.0
Received: by 10.68.2.134 with SMTP id 6mr323648pbu.368.1311864472950; Thu, 28 Jul 2011 07:47:52 -0700 (PDT)
Received: by 10.68.43.7 with HTTP; Thu, 28 Jul 2011 07:47:52 -0700 (PDT)
In-Reply-To: <4E2FF40F.1050301@tana.it>
References: <CAK+SpiyJYKKuWo5bzn_a9+KwW_SFhFXKT34_VTW3b3LKgxa_ag@mail.gmail.com> <4E2FF40F.1050301@tana.it>
Date: Thu, 28 Jul 2011 07:47:52 -0700
Message-ID: <CAK+SpixUkNb0drBmKdP2zT0w0j42byH-+DFpF+-ntWSS4-_Skw@mail.gmail.com>
Subject: Re: Standards and patents
From: Samir Srivastava <samirs.lists@gmail.com>
To: vesely@tana.it, ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 14:47:59 -0000

Hi, Thx for your comments. Private walled garden creates lots of
interoperabilty issues. In the long term with deployments in the
field, even after the expiry of patents we end up for a workable
solution to carry unnecessary burden. e.g. I 'GUESS' pains of htonl
etc are due to patents. IMHO we need to free human brain & cpu for
more important issues. It is not fair for people who work on
unpatented baselines specifications. What would have been situation if
IP header was patented? Thx Samir


On 7/27/11, Alessandro Vesely <vesely@tana.it> wrote:
> On 27/Jul/11 08:07, Samir Srivastava wrote:
>> Standards are developed by community & for community. There is no
>> role of patent hunters in that.
>
> I agree, with the exception of "defensive" patents, some of which are
> announced with very elegant disclosures.  Let's draw a veil over
> incomprehensible and confused disclosures, for now.  For the rest,
> what is the purpose of standardizing a private walled garden?
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

From eburger-l@standardstrack.com  Thu Jul 28 07:56:24 2011
Return-Path: <eburger-l@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 E002E21F8C25 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 07:56:24 -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 WsC6qQNjpqqL for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 07:56:24 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 474B521F8B2C for <ietf@ietf.org>; Thu, 28 Jul 2011 07:56:24 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com;  h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=qloY80I4r/qMQ6Ewp46jpv98moe51m6G3TyDeKrQF2D+CJo665FMjIDBtlgi/bQ0Mtw04u/+dN/7Qh5ghG0i4dowUMb65ih0RYJCqFL3QBiuZIMsXIf1rDpvSmMHHWI/;
Received: from dhcp-63da.meeting.ietf.org ([130.129.99.218]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger-l@standardstrack.com>) id 1QmS0d-00072B-N0; Thu, 28 Jul 2011 07:56:23 -0700
Subject: Re: Standards and patents
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <CAK+SpixUkNb0drBmKdP2zT0w0j42byH-+DFpF+-ntWSS4-_Skw@mail.gmail.com>
Date: Thu, 28 Jul 2011 10:56:20 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <F94D7DF9-4CED-4FE7-AD00-760325A40224@standardstrack.com>
References: <CAK+SpiyJYKKuWo5bzn_a9+KwW_SFhFXKT34_VTW3b3LKgxa_ag@mail.gmail.com> <4E2FF40F.1050301@tana.it> <CAK+SpixUkNb0drBmKdP2zT0w0j42byH-+DFpF+-ntWSS4-_Skw@mail.gmail.com>
To: Samir Srivastava <samirs.lists@gmail.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: 
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 14:56:25 -0000

The patent would have expired by now?

On Jul 28, 2011, at 10:47 AM, Samir Srivastava wrote:

> Hi, Thx for your comments. Private walled garden creates lots of
> interoperabilty issues. In the long term with deployments in the
> field, even after the expiry of patents we end up for a workable
> solution to carry unnecessary burden. e.g. I 'GUESS' pains of htonl
> etc are due to patents. IMHO we need to free human brain & cpu for
> more important issues. It is not fair for people who work on
> unpatented baselines specifications. What would have been situation if
> IP header was patented? Thx Samir
> 
> 
> On 7/27/11, Alessandro Vesely <vesely@tana.it> wrote:
>> On 27/Jul/11 08:07, Samir Srivastava wrote:
>>> Standards are developed by community & for community. There is no
>>> role of patent hunters in that.
>> 
>> I agree, with the exception of "defensive" patents, some of which are
>> announced with very elegant disclosures.  Let's draw a veil over
>> incomprehensible and confused disclosures, for now.  For the rest,
>> what is the purpose of standardizing a private walled garden?
>> 
>> 
>> _______________________________________________
>> 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 cb.list6@gmail.com  Thu Jul 28 08:04:22 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 55E5B21F8CB1; Thu, 28 Jul 2011 08:04:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.024
X-Spam-Level: 
X-Spam-Status: No, score=-4.024 tagged_above=-999 required=5 tests=[AWL=0.974,  BAYES_00=-2.599, GB_I_LETTER=-2, 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 2CR6V7JSQJtR; Thu, 28 Jul 2011 08:04:21 -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 3334521F8C7B; Thu, 28 Jul 2011 08:04:20 -0700 (PDT)
Received: by wyj26 with SMTP id 26so121309wyj.31 for <multiple recipients>; Thu, 28 Jul 2011 08:04:19 -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=MQPOKYjlh9SIim+2JisYfxmU3kQQvZ+R4c8iXkLjihU=; b=FuEuLZlhP7REYC5yYH+EFl1YOARKoBfj0cfxuOJeR/UL+8xTdU2VaYalm6m99Rs0oC FUG8Bmx+XnjiL1WXLy0McTv+s0fu0i35NDvzlDz7fNBjaDpACwmKzhSoXjOzQkI835Pt 2I0rcACNNAJjoRiZECn1ELOGv8fE+HYpgVsfc=
MIME-Version: 1.0
Received: by 10.227.154.6 with SMTP id m6mr125715wbw.73.1311865459356; Thu, 28 Jul 2011 08:04:19 -0700 (PDT)
Received: by 10.216.179.71 with HTTP; Thu, 28 Jul 2011 08:04:17 -0700 (PDT)
Received: by 10.216.179.71 with HTTP; Thu, 28 Jul 2011 08:04:17 -0700 (PDT)
In-Reply-To: <m1QmLdc-0001mlC@stereo.hq.phicoh.net>
References: <2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com> <m1QmLdc-0001mlC@stereo.hq.phicoh.net>
Date: Thu, 28 Jul 2011 08:04:17 -0700
Message-ID: <CAD6AjGRxQqNBE_vg7Pj_Syx6-QmJgu=qhprjOw8=-Ma49au1zQ@mail.gmail.com>
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
From: Cameron Byrne <cb.list6@gmail.com>
To: Philip Homburg <pch-v6ops@u-1.phicoh.com>
Content-Type: multipart/alternative; boundary=0016e64c1a30b2b4e904a9227a65
Cc: IPv6 Operations <v6ops@ietf.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 15:04:22 -0000

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

On Jul 28, 2011 1:08 AM, "Philip Homburg" <pch-v6ops@u-1.phicoh.com> wrote:
>
> In your letter dated Wed, 27 Jul 2011 21:56:51 -0400 you wrote:
> > In the absence of a coherent instruction from IETF for a phase-out
> > plan, declaring this protocol historic under the current proposed
> > language, will do precisely that.  Please please please, if IETF
> > wants 6to4 to die, then publish a phase-out plan so that the
> > current users of 6to4 can have fair warning before the relays go
> > dark and forthcoming hardware/software upgrades rip the feature
> > out from under them.
>
> I would hope that big companies like Apple would actually do an impact
> analysis before removing a feature.
>

Like how Apple does not support Flash in iOS?

Just one example where a visionary drops an inferior solution to force a
better one.

This is also known as cracking some eggs to make an omelet.

Cb

> Big content providers can measure how much 6to4 is enabled, so they can
> probably say something about trends. But that doesn't say much about how
many
> users actually care about 6to4. Vendors seem to be best equiped to analyse
> the users' need for 6to4.
>
> I don't think relay operators have expressed a desire for a specific cut
off
> date. So I guess they just figure out for themselves when to switch off
the
> relays.
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

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

<p><br>
On Jul 28, 2011 1:08 AM, &quot;Philip Homburg&quot; &lt;<a href=3D"mailto:p=
ch-v6ops@u-1.phicoh.com">pch-v6ops@u-1.phicoh.com</a>&gt; wrote:<br>
&gt;<br>
&gt; In your letter dated Wed, 27 Jul 2011 21:56:51 -0400 you wrote:<br>
&gt; &gt; In the absence of a coherent instruction from IETF for a phase-ou=
t<br>
&gt; &gt; plan, declaring this protocol historic under the current proposed=
<br>
&gt; &gt; language, will do precisely that. =A0Please please please, if IET=
F<br>
&gt; &gt; wants 6to4 to die, then publish a phase-out plan so that the<br>
&gt; &gt; current users of 6to4 can have fair warning before the relays go<=
br>
&gt; &gt; dark and forthcoming hardware/software upgrades rip the feature<b=
r>
&gt; &gt; out from under them.<br>
&gt;<br>
&gt; I would hope that big companies like Apple would actually do an impact=
<br>
&gt; analysis before removing a feature.<br>
&gt;</p>
<p>Like how Apple does not support Flash in iOS? </p>
<p>Just one example where a visionary drops an inferior solution to force a=
 better one.</p>
<p>This is also known as cracking some eggs to make an omelet.</p>
<p>Cb</p>
<p>&gt; Big content providers can measure how much 6to4 is enabled, so they=
 can<br>
&gt; probably say something about trends. But that doesn&#39;t say much abo=
ut how many<br>
&gt; users actually care about 6to4. Vendors seem to be best equiped to ana=
lyse<br>
&gt; the users&#39; need for 6to4.<br>
&gt;<br>
&gt; I don&#39;t think relay operators have expressed a desire for a specif=
ic cut off<br>
&gt; date. So I guess they just figure out for themselves when to switch of=
f the<br>
&gt; relays.<br>
&gt;<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>

--0016e64c1a30b2b4e904a9227a65--

From jnc@mercury.lcs.mit.edu  Thu Jul 28 08:20:20 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 BFE2621F8BF2; Thu, 28 Jul 2011 08:20:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.514
X-Spam-Level: 
X-Spam-Status: No, score=-6.514 tagged_above=-999 required=5 tests=[AWL=0.085,  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 n49UkST3jdzU; Thu, 28 Jul 2011 08:20:20 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 2AF5521F8CCC; Thu, 28 Jul 2011 08:20:20 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id A2D8318C0F2; Thu, 28 Jul 2011 11:20:18 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
Message-Id: <20110728152018.A2D8318C0F2@mercury.lcs.mit.edu>
Date: Thu, 28 Jul 2011 11:20:18 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: v6ops@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: Thu, 28 Jul 2011 15:20:20 -0000

    > From: Cameron Byrne <cb.list6@gmail.com>

    > Like how Apple does not support Flash in iOS?
    > Just one example where a visionary drops an inferior solution to force
    > a better one.

Apple has enough market share to get away with that. IPv6 doesn't.

	Noel

From warren@kumari.net  Thu Jul 28 08:22:41 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 4781D21F8B94 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 08:22:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.456
X-Spam-Level: 
X-Spam-Status: No, score=-102.456 tagged_above=-999 required=5 tests=[AWL=0.143, 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 Fy275TCSjuGg for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 08:22:40 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 637DE21F8BF3 for <ietf@ietf.org>; Thu, 28 Jul 2011 08:22:40 -0700 (PDT)
Received: from dhcp-227f.meeting.ietf.org (dhcp-227f.meeting.ietf.org [130.129.34.127]) by vimes.kumari.net (Postfix) with ESMTPSA id 7DFA51B416DC; Thu, 28 Jul 2011 11:22:39 -0400 (EDT)
Subject: Re: Why the IESG needs to review everything...
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=windows-1252
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <4E308D64.3030804@gmail.com>
Date: Thu, 28 Jul 2011 11:22:39 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3D54259C-D229-4FFA-A7E3-0947459A0F14@kumari.net>
References: <4E308D64.3030804@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
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, 28 Jul 2011 15:22:41 -0000

[ Top posting - meta comment ]

Every now and then I get a bee in my bonnet and decide to carefully =
review each and every draft in LC. I hate to break it to y'all, but many =
drafts really poorly written, and, even if you have very broad =
interests, many of them are going to be really boring to you=85

While not all ADs read all drafts, most read a large fraction of them =
(and read them carefully and thoughtfully enough to catch a number of =
large issues (and nits) *that were not caught in LC*) -- I think that =
they deserve recognition for performing a valuable and un-fun =
function...

Climbing off soapbox,
W


On Jul 27, 2011, at 6:12 PM, Brian E Carpenter wrote:

> Responding to Glen Zorn's question in plenary:
>=20
> Firstly, not all ADs review all drafts - that's why you will see
> numerous "no objection" or missing ballot responses.
>=20
> Secondly, the drafts are de facto reviewed by review teams
> these days (gen-art, security area, etc.). This serves to alert
> the ADs if a draft really needs careful review. The workload is
> more reasonable than it used to be.
>=20
> Thirdly, when I was in the IESG, I was surprised quite often by
> *glaring* errors that had not been picked up before. Somebody has
> to be responsible for catching these, and today it's the IESG.
>=20
> Fourthly, because of the exact same discussion that Glen raised in
> plenary, the IESG defined and published its criteria for DISCUSS
> several years ago. Sometimes there are inappropriate DISCUSSes
> and those need to be pointed out when they happen.
>=20
> I hear the IESG members responding exactly right to this question.
>=20
> --=20
> Regards
>   Brian Carpenter
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From mcr@sandelman.ca  Thu Jul 28 08:23:15 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 4986D21F8CD3 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 08:23:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.187
X-Spam-Level: 
X-Spam-Status: No, score=-1.187 tagged_above=-999 required=5 tests=[AWL=0.767,  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 ElnEZ2kMZ4EL for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 08:23:14 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 8F49321F8CCD for <ietf@ietf.org>; Thu, 28 Jul 2011 08:23:13 -0700 (PDT)
Received: from marajade.sandelman.ca (dhcp-174f.meeting.ietf.org [130.129.23.79]) by relay.sandelman.ca (Postfix) with ESMTPS id 98800A0067; Thu, 28 Jul 2011 11:22:51 -0400 (EDT)
Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id E4D8B980EA; Thu, 28 Jul 2011 11:23:24 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: Reminder: Remote Participation Support for Admin Plenary Tonight
In-Reply-To: <4E30947F.1060102@ericsson.com>
References: <3D658D0E-4958-4AEF-9BD2-447A887EECF1@amsl.com> <4E30865A.2090802@gmail.com> <4E3087C4.1000009@ericsson.com> <4E3088D0.8080308@gmail.com> <4E30947F.1060102@ericsson.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Thu, 28 Jul 2011 11:23:24 -0400
Message-ID: <27833.1311866604@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
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, 28 Jul 2011 15:23:15 -0000

>>>>> "Gonzalo" == Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> writes:
    >> I don't know about the codecs, but there is a wireless hop. I'm
    >> getting frequent very short drops as well as slightly buzzy sound
    >> and less fidelity than the parallel session streaming. The voices
    >> of people I know well are harder to recognise.

    Gonzalo> one aspect to consider is that long play-out buffers
    Gonzalo> increase the audio quality but also increase the
    Gonzalo> delay. Many people have complained about not being able to
    Gonzalo> effectively participate in the meetings remotely using the

huh? the major delay is the line up at the microphone, not the TCP
queue.

-- 
]       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 msk@cloudmark.com  Thu Jul 28 08:45:49 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 DFA1D21F8639 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 08:45:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.274
X-Spam-Level: 
X-Spam-Status: No, score=-103.274 tagged_above=-999 required=5 tests=[AWL=-0.675, 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 yxaXWn8Nd76m for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 08:45:49 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by ietfa.amsl.com (Postfix) with ESMTP id 3EE3C21F8BD8 for <ietf@ietf.org>; Thu, 28 Jul 2011 08:45:49 -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, 28 Jul 2011 08:45:42 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: IETF discussion list <ietf@ietf.org>
Date: Thu, 28 Jul 2011 08:45:41 -0700
Subject: RE: Why the IESG needs to review everything...
Thread-Topic: Why the IESG needs to review everything...
Thread-Index: AcxNOjfaKCHn+YmwSRWYvzwg2Bb2bQAAVKYA
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF495@EXCH-C2.corp.cloudmark.com>
References: <4E308D64.3030804@gmail.com> <3D54259C-D229-4FFA-A7E3-0947459A0F14@kumari.net>
In-Reply-To: <3D54259C-D229-4FFA-A7E3-0947459A0F14@kumari.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: Thu, 28 Jul 2011 15:45:50 -0000

I think the IESG, or its various delegates, do need to review everything, e=
specially keeping in mind that "review" doesn't have to be some big heavywe=
ight thing each time.  I share the same view as others that sometimes some =
really broken stuff manages to get up to that level.

And, although it can be annoying, I don't agree that the spurious DISCUSS p=
roblem is all that bad as long as the AD doing so is responsive to being ca=
lled on it (and, as Barry mentioned during plenary, that's improved a lot l=
ately).  There are only 15 people that can DISCUSS a document, but those of=
 us producing broken documents seriously outnumber them.

Part of the problem with spurious DISCUSSes is psychological, and that's fo=
r a different conversation.  My only other remark there is that ADs could s=
ometimes avoid a lot of heartache for themselves and their working groups w=
ith an inquisitive email prior to DISCUSSing something.
=20
I have heard more than once during this meeting some hallway track chatter =
about ADs wishing they had invoked their available review resources (apps-r=
eview, the various directorates, etc.) earlier in the process.  So perhaps =
what's needed is an optional document state prior to Publication Requested =
called Review Requested, which triggers an early, informal review action by=
 the AD and/or her/his review team prior to the formal start of the publica=
tion process.  Working group chairs would have to understand that it's an e=
xpensive request (i.e., not to be used frivolously), but still cheaper than=
 letting a real disaster of a draft get up to the AD or the full IESG.

-MSK

From lberger@labn.net  Thu Jul 28 09:49:03 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 E3C4621F8B22 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 09:49:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.005
X-Spam-Level: 
X-Spam-Status: No, score=-102.005 tagged_above=-999 required=5 tests=[AWL=0.260, 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 v8hQYkxf-s0v for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 09:49:03 -0700 (PDT)
Received: from oproxy7-pub.bluehost.com (oproxy7-pub.bluehost.com [67.222.55.9]) by ietfa.amsl.com (Postfix) with SMTP id 6072921F8AE1 for <ietf@ietf.org>; Thu, 28 Jul 2011 09:48:55 -0700 (PDT)
Received: (qmail 32474 invoked by uid 0); 28 Jul 2011 16:48:55 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy7.bluehost.com with SMTP; 28 Jul 2011 16:48:55 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=dFmqFqicAb1wVPV6T1y8RBCirfGp7aVQL6G/Kb6yZsg=;  b=fa1y/s64ti6Ho7kTRbzF7VuggdA03Lq9VMnWAGVwGFLwaI7uYYiMPWFFX5XfKMlkaEiUBGBU3t3NqigSwtg1D4uYaxmOzectYk+3kA7+9BN2LOvrM7RWJiZq0O4XgepR;
Received: from box313.bluehost.com ([69.89.31.113] helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.76) (envelope-from <lberger@labn.net>) id 1QmTlW-000747-Ua; Thu, 28 Jul 2011 10:48:55 -0600
Message-ID: <4E3192F6.4040808@labn.net>
Date: Thu, 28 Jul 2011 12:48:54 -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: Warren Kumari <warren@kumari.net>
Subject: Re: Why the IESG needs to review everything...
References: <4E308D64.3030804@gmail.com> <3D54259C-D229-4FFA-A7E3-0947459A0F14@kumari.net>
In-Reply-To: <3D54259C-D229-4FFA-A7E3-0947459A0F14@kumari.net>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: IETF 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, 28 Jul 2011 16:49:04 -0000

+1

On 7/28/2011 11:22 AM, Warren Kumari wrote:
>...
> While not all ADs read all drafts, most read a large fraction of them
> (and read them carefully and thoughtfully enough to catch a number of
> large issues (and nits) *that were not caught in LC*) -- I think that
> they deserve recognition for performing a valuable and un-fun
> function...
> ...

From jeroen@unfix.org  Wed Jul 27 09:29:10 2011
Return-Path: <jeroen@unfix.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 96C5511E8133; Wed, 27 Jul 2011 09:29:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, J_CHICKENPOX_16=0.6, J_CHICKENPOX_53=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 aOu4jpsiVidb; Wed, 27 Jul 2011 09:28:59 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [IPv6:2a01:4f8:130:74c1:5054:ff:fec4:f7d4]) by ietfa.amsl.com (Postfix) with ESMTP id 7DC4311E80E8; Wed, 27 Jul 2011 09:28:59 -0700 (PDT)
Received: from yomi.ch.unfix.org (223-95.60-188.cust.bluewin.ch [188.60.95.223]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id 5C835801C2BF; Wed, 27 Jul 2011 18:28:36 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unfix.org; s=DKIM2009; t=1311784136; bh=b0bm6WD1UlGKKVAT39bNA2kaHLj7zibSlQUgGqveif8=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=yEVdQ2RLQT8NgUkSbH4Hq6Sj8gTLLYW/WkXuZ/UFKYWRoU67Lc4v+2d/22w0unBnk UKNQx21EAqMCjgDAEGf8bG3f8oljVHVxGku48g3kTe2KO77GwJmlxZbVP6P3HZfndp 0kjSJ1W+Uv3oHuYFMDuBfcC+t+Icm+o6Acp+LbPxzOplf5vlcH7+wEt4rUTrpCF099 0l2hDMc4GBRyF07QL1GSR4fek5vsSNP90mClBy3mvPysIh2sfHXqZItLDLhwO0ipdv AOlaIXVJvN2FDLefimIRaYpc1JcX+vzCzwx2p0FA6FcXn8B0yYWULabR/+VkwlemUK FLekm5pMjfTOQ==
Message-ID: <4E303CB5.9050606@unfix.org>
Date: Wed, 27 Jul 2011 18:28:37 +0200
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <968F0B1C-D082-4A59-8213-FD58C74AF89D@nominum.com> <20110727151517.CF9371235D70@drugs.dv.isc.org> <D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk> <EMEW3|fcf145b5033ff99790b7c34003f47686n6QGZC03tjc|ecs.soton.ac.uk|D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk> <20110727160331.A07C31236670@drugs.dv.isc.org>
In-Reply-To: <20110727160331.A07C31236670@drugs.dv.isc.org>
X-Enigmail-Version: 1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 28 Jul 2011 09:56:45 -0700
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, IPv6 Operations <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, 27 Jul 2011 16:29:10 -0000

On 2011-07-27 18:03 , Mark Andrews wrote:
[..]
>> b) use a tunnel broker - this works much better through NATs and with dynamic
>>  IPv4 addresses
> 
> For which there is only experimental / ad-hoc code.

You call my code Experimental/ad-hoc? :)

Like a good whiskey it matured over the years and hopefully soon I will
be releasing the next edition of AICCU which solves, at least in that
implementation, a couple of quirks that we have encountered in the
recent years.

> Please name
> CPE vendors that support tsp?  Please name CPE vendors that support
> tunnel re-configuration on re-number.

I don't know about TSP, but for the combination of TIC/heartbeat + AYIYA
in some cases there are a variety of vendors, amongst which AVM
Fritz!Box, Draytek, ZyXel Motorola, and various others I tend to forget
;) I unfortunately do not have an exact list of devices/models as I had
nothing to do with them, we just get users saying that they have a
device which supports it ;)

The fun part though with CPEs is that they tend to sit on the public IP
address, which is also the reason why the Fritz!Box only does TIC/heartbeat.

And of course every self respecting distribtion has support for it too
by just adding AICCU, that includes the various WRTs, pfSense, m0nowall,
Astaro and many many others.

As you said, everybody can decide themselves what options they add ;)

Greets,
 Jeroen

From w@1wt.eu  Wed Jul 27 10:13:43 2011
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFAC022800E; Wed, 27 Jul 2011 10:13:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.349
X-Spam-Level: 
X-Spam-Status: No, score=-4.349 tagged_above=-999 required=5 tests=[AWL=-2.306, BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9AjcXV+vcDfH; Wed, 27 Jul 2011 10:13:41 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 0C28A228006; Wed, 27 Jul 2011 10:13:40 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6RHDYeM008038; Wed, 27 Jul 2011 19:13:34 +0200
Date: Wed, 27 Jul 2011 19:13:34 +0200
From: Willy Tarreau <w@1wt.eu>
To: Dave Cridland <dave@cridland.net>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110727171334.GB7979@1wt.eu>
References: <CALiegfnYm6g63JDHLiSH__r-or3kzK0XCVa3cC7RMP14KWBOSg@mail.gmail.com> <20110724120751.GQ22405@1wt.eu> <CALiegfncavmoMp4YDCeeJ3rsOfHAYQ99itKX2Q2eHB351T3X5A@mail.gmail.com> <20110724184537.GZ22405@1wt.eu> <CALiegfne620wuDMAp235n3mVcXTAnbhhNm8vpiNCy5F7+VD92A@mail.gmail.com> <20110724192948.GD22405@1wt.eu> <CALiegf=e48kkF+Gky1mY7LippUB-0kZDgSGZrJxk1aZupAGkYw@mail.gmail.com> <20110727012806.EBB811231907@drugs.dv.isc.org> <20110727052549.GB4086@1wt.eu> <9031.1311786432.357811@puncture>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9031.1311786432.357811@puncture>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Thu, 28 Jul 2011 09:56:45 -0700
Cc: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>, Server-Initiated HTTP <hybi@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, 27 Jul 2011 17:13:44 -0000

On Wed, Jul 27, 2011 at 06:07:12PM +0100, Dave Cridland wrote:
> On Wed Jul 27 06:25:49 2011, Willy Tarreau wrote:
> >On Wed, Jul 27, 2011 at 11:28:06AM +1000, Mark Andrews wrote:
> >> > SRV provides load-balancing and failover. I never said that SRV  
> >is a
> >> > solution for temporaly put in maintenance a server.
> >>
> >> Happy eyeballs however does allow you to take a server out of  
> >production
> >> and not really notice it.  Note webbrowsers have had the ability  
> >to do
> >> this for as long as webbrowsers have existed.
> >
> >Mark, could you elaborate on this point ? Surely you're not talking  
> >about
> >the fact that a browser retries a failed connection, but I'm not  
> >not sure
> >what mechanism you're talking about.
> 
> Happy eyeballs - try everything as soon as you can, in parallel. Drop  
> everything else when one does.

This sensibly increases load on servers with useless connections, and
is counter-efficient in mobile networks where sending uplink packets
is the limiting factor !

Willy


From jeroen@unfix.org  Wed Jul 27 11:51:47 2011
Return-Path: <jeroen@unfix.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 0379621F8B8B; Wed, 27 Jul 2011 11:51:47 -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 zPst8-rKpwiz; Wed, 27 Jul 2011 11:51:46 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [IPv6:2a01:4f8:130:74c1:5054:ff:fec4:f7d4]) by ietfa.amsl.com (Postfix) with ESMTP id 70C2D21F8B84; Wed, 27 Jul 2011 11:51:45 -0700 (PDT)
Received: from yomi.ch.unfix.org (yomi.ch.unfix.org [IPv6:2001:41e0:ff42:99:ca2a:14ff:fe1f:2b7b]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id 7EEF0801C2BF; Wed, 27 Jul 2011 20:51:42 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unfix.org; s=DKIM2009; t=1311792702; bh=dY6UU4jsNi/bnlZac8EgJN2pD26m5K/elv77P/UQp7I=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=TKlzw1Em/gUT7GNolV4YOtWd/1+P4mYmG2TB7zopbHxyGYRnVvPx6ASQILO7Cepx+ J620jU7do548fNrthpvuXVZrW2xpc8Ycw/d5ZUhZkqbYOw6C/Ah3Jb4sF1k/DkLPHu VhujM70KJdbA6w6Fn9J9eyjMbCr7Ybidl/1MH9E5afjxFZPA/FkZ79QDNQDutBojsa beT1PUoFo8/qAxkr01xsiUphYLbFe083OCeA5IS1A2ykd3erjZ/oPxD+j9dA2Y0Iv3 wIiJ9PGAAn7iLfOSVpo7lCBPfGSpcAP7nn6m0rS5nOIY1JERJ+Cy5WYIPAYbMUhUpB oTEYUHuJjm4AQ==
Message-ID: <4E305E3E.2040607@unfix.org>
Date: Wed, 27 Jul 2011 20:51:42 +0200
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <968F0B1C-D082-4A59-8213-FD58C74AF89D@nominum.com> <20110727151517.CF9371235D70@drugs.dv.isc.org> <D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk> <EMEW3|fcf145b5033ff99790b7c34003f47686n6QGZC03tjc|ecs.soton.ac.uk|D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk> <999C3229-649D-4242-BB0F-2BB494EDF1D9@network-heretics.com>
In-Reply-To: <999C3229-649D-4242-BB0F-2BB494EDF1D9@network-heretics.com>
X-Enigmail-Version: 1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 28 Jul 2011 09:56:45 -0700
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, IPv6 Operations <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, 27 Jul 2011 18:51:47 -0000

On 2011-07-27 20:21 , Keith Moore wrote:
> On Jul 27, 2011, at 11:35 AM, Tim Chown wrote:
> 
>> I suspect, but have no proof, that the huge majority of 6to4 users don't use it intentionally, and the content they are trying to reach is also available over IPv4. But for people who want to develop and use new IPv6-specific apps, then either a broker or something like OpenWRT ought to meet their needs?
> 
> tunnel brokers suck if the tunnel endpoint isn't near your current network location.

Let me rewrite that sentence for you:

 "transition mechanisms suck if the tunnel endpoint isn't near your
current network location"

It does not matter much if that mechanism is static proto-41 (6in4),
6to4, AYIYA, TSP, PPTP, HTTP Proxies or whatever, there is going to be a
bit more latency if they are not directly next to you. Not much you can
do about except deploy more of them or

And this will always be the case unless you deploy enough of them in all
places possible. For SixXS we are at 48 boxes around the world,
Hurricane has 25 and Gogo6 has 4 of them of their own for Freenet6 and
then there are 4 others at other organizations and there are a couple of
other services out there which provide tunnels see:

 http://en.wikipedia.org/wiki/List_of_IPv6_tunnel_brokers

> there are currently no universally applicable, or even widely applicable, v6-over-v4 solutions.

For your set of requirements maybe but especially Tunnel Brokers are
working very well for a lot of people and if one sees the traffic stats
on Teredo and 6to4 nodes due to this little thing called NNTP I would
state that those are doing quite fine too for giving access to what
people need to get to.

Your major requirement seems to involve latency though, thus as such,
there is only one thing to do, get one of those boxes deployed locally
to your endpoint.

Do note to yourself that the next issue you will run into that the
service you are actually contacting will be far away, and you suddenly
understand that you need that Akamai content box and a Google one and
various other closeby too ;)

If you want to solve your problem though, I guess for HE you'll have to
give them connectivity to their network and space in a rack for a box,
gogo6 will sell you a box and for SixXS you provide the box+connectivity
and we'll set up the software for free for you and handle the tunneling
completely.

Greets,
 Jeroen

From kivinen@iki.fi  Wed Jul 27 15:52:37 2011
Return-Path: <kivinen@iki.fi>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9BE011E8092; Wed, 27 Jul 2011 15:52:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4LHmbwWtFc5P; Wed, 27 Jul 2011 15:52:37 -0700 (PDT)
Received: from mail.kivinen.iki.fi (fireball.acr.fi [83.145.195.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01D8611E8084; Wed, 27 Jul 2011 15:52:36 -0700 (PDT)
Received: from fireball.kivinen.iki.fi (localhost [127.0.0.1]) by mail.kivinen.iki.fi (8.14.3/8.14.3) with ESMTP id p6RMqOaf004834 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Jul 2011 01:52:24 +0300 (EEST)
Received: (from kivinen@localhost) by fireball.kivinen.iki.fi (8.14.3/8.12.11) id p6RMqOnp025098; Thu, 28 Jul 2011 01:52:24 +0300 (EEST)
X-Authentication-Warning: fireball.kivinen.iki.fi: kivinen set sender to kivinen@iki.fi using -f
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <20016.38567.974476.933647@fireball.kivinen.iki.fi>
Date: Thu, 28 Jul 2011 01:52:23 +0300
From: Tero Kivinen <kivinen@iki.fi>
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: [IPsec] Last Call:	<draft-kivinen-ipsecme-secure-password-framework-01.txt>	(Secure	Password Framework for IKEv2) to Informational RFC
In-Reply-To: <7C54FFE2-FFE0-4B4C-BF7E-142A6B10DF6B@checkpoint.com>
References: <20110727164459.29853.48303.idtracker@ietfa.amsl.com> <7C54FFE2-FFE0-4B4C-BF7E-142A6B10DF6B@checkpoint.com>
X-Mailer: VM 7.19 under Emacs 21.4.1
X-Edit-Time: 8 min
X-Total-Time: 8 min
X-Mailman-Approved-At: Thu, 28 Jul 2011 09:56:45 -0700
Cc: IPsecme WG <ipsec@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, 27 Jul 2011 22:52:38 -0000

Yoav Nir writes:
> This draft represents a total shirking of our responsibility. Rather
> than decide on one protocol that is "best" or even arbitrarily
> choosing one that is "good enough", it proposes to build a framework
> so that everyone and their dog can have their own method. This is a
> nightmare for developers: since you can't know what method the peer
> will support, you have to implement all of them.  

Partially yes, but unfortunately all of the authors of those actual
protocols decided that they wanted to continue publishing those drafts
as individual RFCs, and each of them used different way to negotiate
them, so there was no way to even implement multiple of them.

At least this drafts gives you that option to implement multiple of
them if you want. This draft only provides instructions for those
other draft authors so they can at least common methods to negotiate
the feature and use common method to trasmit data between peers.
-- 
kivinen@iki.fi

From pch-b2B3A6689@u-1.phicoh.com  Thu Jul 28 01:08:18 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 59FF721F8B9D; Thu, 28 Jul 2011 01:08:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.558
X-Spam-Level: 
X-Spam-Status: No, score=-4.558 tagged_above=-999 required=5 tests=[AWL=0.041,  BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7wIu+WQlDvGu; Thu, 28 Jul 2011 01:08:18 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo-6to4.hq.phicoh.net [IPv6:2002:8225:f03:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id 848C521F8B98; Thu, 28 Jul 2011 01:08:17 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #66) id m1QmLdc-0001mlC; Thu, 28 Jul 2011 10:08:12 +0200
Message-Id: <m1QmLdc-0001mlC@stereo.hq.phicoh.net>
To: james woodyatt <jhw@apple.com>
Subject: Re: [v6ops] 6to4v2 (as in ripv2)? 
From: Philip Homburg <pch-v6ops@u-1.phicoh.com>
Sender: pch-b2B3A6689@u-1.phicoh.com
In-reply-to: Your message of "Wed, 27 Jul 2011 21:56:51 -0400 ." <2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com> 
Date: Thu, 28 Jul 2011 10:08:11 +0200
X-Mailman-Approved-At: Thu, 28 Jul 2011 09:56:45 -0700
Cc: IPv6 Operations <v6ops@ietf.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 08:08:18 -0000

In your letter dated Wed, 27 Jul 2011 21:56:51 -0400 you wrote:
> In the absence of a coherent instruction from IETF for a phase-out
> plan, declaring this protocol historic under the current proposed
> language, will do precisely that.  Please please please, if IETF
> wants 6to4 to die, then publish a phase-out plan so that the
> current users of 6to4 can have fair warning before the relays go
> dark and forthcoming hardware/software upgrades rip the feature
> out from under them.

I would hope that big companies like Apple would actually do an impact
analysis before removing a feature. 

Big content providers can measure how much 6to4 is enabled, so they can
probably say something about trends. But that doesn't say much about how many
users actually care about 6to4. Vendors seem to be best equiped to analyse 
the users' need for 6to4.

I don't think relay operators have expressed a desire for a specific cut off 
date. So I guess they just figure out for themselves when to switch off the
relays.



From jeroen@unfix.org  Thu Jul 28 02:12:43 2011
Return-Path: <jeroen@unfix.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 A47FF21F8C41; Thu, 28 Jul 2011 02:12:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.428
X-Spam-Level: 
X-Spam-Status: No, score=-102.428 tagged_above=-999 required=5 tests=[AWL=0.171, 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 gnK4QTv95XqS; Thu, 28 Jul 2011 02:12:42 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [IPv6:2a01:4f8:130:74c1:5054:ff:fec4:f7d4]) by ietfa.amsl.com (Postfix) with ESMTP id 125EE21F8AE9; Thu, 28 Jul 2011 02:12:41 -0700 (PDT)
Received: from yomi.ch.unfix.org (223-95.60-188.cust.bluewin.ch [188.60.95.223]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id E91F4801C2BF; Thu, 28 Jul 2011 11:12:16 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unfix.org; s=DKIM2009; t=1311844357; bh=JkSTCVhxy50/bL2QgF/S7YbegE+aPMoVd3F1oTnDFEA=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=UzCVdcmVTR6Y2emlvpe0VgUOJCXG44Zyx0mSZyx+cDoWlHvA1uNBr3PQGfG8WG67q w8LmJ9qE3CsbIoX8qmP/4fN7FjaGSArnhYjmhgl9Fk01GN6TdH8z3YiIFNy5yBGjrW 8xmdoq7aL+AHlaYlLb84/1sDxky6UbMjGqx8LwiG/wBmyseqOyvcGB2bkSqPZXIGRm m67pRX18eMAIwtCgiC+nVhwxR+AHspW4luifap0mkHK+TdBX3pq0bhChq0bbV2UpRA 7o8mr7kLUMny0uiE/gU2ppUUJTZbwCFPLaQiryZZHSHZvYTC6m2lmEUdVPVMA01qiR KoVqgHl2GGmtA==
Message-ID: <4E3127F1.2030708@unfix.org>
Date: Thu, 28 Jul 2011 11:12:17 +0200
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <968F0B1C-D082-4A59-8213-FD58C74AF89D@nominum.com> <20110727151517.CF9371235D70@drugs.dv.isc.org> <D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk> <EMEW3|fcf145b5033ff99790b7c34003f47686n6QGZC03tjc|ecs.soton.ac.uk|D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk> <999C3229-649D-4242-BB0F-2BB494EDF1D9@network-heretics.com> <4E305E3E.2040607@unfix.org> <20110727233634.406021238970@drugs.dv.isc.org>
In-Reply-To: <20110727233634.406021238970@drugs.dv.isc.org>
X-Enigmail-Version: 1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 28 Jul 2011 09:56:45 -0700
Cc: IPv6 Operations <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, 28 Jul 2011 09:12:43 -0000

On 2011-07-28 01:36 , Mark Andrews wrote:
[..]
> Is there *one* tunnel management protocol that they all support or
> does a cpe vendor have to implement multiple ones to reach them
> all?  I'm pretty sure I know the answer to this question but I'd
> love to be proved wrong.

There is no 'one' solution to the problems that they are solving.

As such there tend to be a combo of:
 - static proto-41 tunnel
 - 6to4
 - 6rd
 - TSP => dynamic NATted addresses
 - proto-41 + heartbeat + TIC => dynamic public addresses
 - AYIYA + TIC => dynamic NATted addresses

TSP conveys configurartion information inline with the UDP packets.
TIC is solely for configuration information and does not do tunneling
but can be used for all proto-41/heartbeat/AYIYA protocols (and for
instance AVM chose to only do proto-41 + heartbeat as their devices
always have public IPv4 IPs).

Teredo is only for a single host thus is not useful for CPEs and thus
not included in them.

> One of the advantages of 6to4 anycast is that it is just needs a
> check box to turn on and off.  Everybody speaks the same thing.

Except that it does not work behind a NAT and most people do sit behind
a NAT.

Next to that those anycasts are even rarer around the world and on top
of that it is hard to figure out issues when they are there (although
some people have tricks to apparently debug them, the anycast on both
IPv4 and IPv6 requires one to contact a lot of folks).

The big advantage over a known tunnel endpoint is the known behavior of
that endpoint and the simple way of complaining when something is
broken. And people fortunately do complain when stuff is broken,
unfortunately not always with the proper details though, but I am to
blame for not finishing that program up...

> Another advantage of 6to4 is it doesn't require manual intervention
> on renumber events.  Manual tunnel don't pass muster.

I guess you are one of the lucky people to get a public static IPv4
address prefix at home that never renumbers? Guess what, most of the
world does not have that luxury, they get 1 dynamic address and for
instance in Germany they get a disconnect/force-renumber every 24 hours
(according to the ISPs because of 'accounting' reasons...)

Do realize that when you have that public IPv4 address, when it changes
you are renumbering your 2002:<ipv4>::/48 prefix everywhere. Fun...
(I hope you also like asking 6to4.nro.net everytime to change your reverse)

The tunnels above all have ISP-supplied prefixes and tend to be static
(I think TSP anonymous tunnels rotate addresses, but the majority just
keeps on returning the same static allocation, in the case of SixXS you
really get a fixed address, much easier on the PoP side and we can do
whois and store it in the relevant RIR registry)

> Another advantage of 6to4 is you don't have to register.  For most of
> the tunnel brokers you have to register.

I guess you also where able to anonymously sign up to your IPv4 ISP!? :)
Especially that static IPv4 address must be wonderful to get that way.

Note that Freenet6 offers 'anonymous' tunnels, thus that is just a TSP away.

Something with the amounts of abuse made us (SixXS) require that we
require valid address data. Next to that it is a RIPE requirement to
register /48 prefixes. Other Tunnelbrokers just started blocking things
like IRC and NNTP because there was too much abuse or traffic....
We kill off accounts of people when they abuse, google my name and you
will find various people who where caught in the act and are quite mad
that they can't have funny vhosts on IRC anymore and attract 500mbit
DoSses and other such nonsense which are not the goal of providing IPv6.

Also, the registration means that people can just type in their
username/password (and optionally which tunnel they want to use out of
the multiple tunnels they might have) in their CPE and the CPE then uses
TIC or TSP to fetch this configuration and set it all up, and it will
just work(tm).

As a nice example see http://www.sixxs.net/wiki/images/FritzboxHowto.jpg
and
http://www.sixxs.net/wiki/Fritz!Box_7270

Next to that knowing where the user is and more importantly their
endpoint allows one to select a proper PoP for that user close to their
endpoint causing low latency and generally high throughput.

With anycast you are just hoping that that all will work.

Greets,
 Jeroen

From kivinen@iki.fi  Thu Jul 28 07:11:11 2011
Return-Path: <kivinen@iki.fi>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C79F21F8C77; Thu, 28 Jul 2011 07:11:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 2sAEfkjkw80z; Thu, 28 Jul 2011 07:11:10 -0700 (PDT)
Received: from mail.kivinen.iki.fi (fireball.acr.fi [83.145.195.1]) by ietfa.amsl.com (Postfix) with ESMTP id 302B721F8C75; Thu, 28 Jul 2011 07:11:10 -0700 (PDT)
Received: from fireball.kivinen.iki.fi (localhost [127.0.0.1]) by mail.kivinen.iki.fi (8.14.3/8.14.3) with ESMTP id p6SEB0xk008991 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Jul 2011 17:11:00 +0300 (EEST)
Received: (from kivinen@localhost) by fireball.kivinen.iki.fi (8.14.3/8.12.11) id p6SEAxEF000678; Thu, 28 Jul 2011 17:10:59 +0300 (EEST)
X-Authentication-Warning: fireball.kivinen.iki.fi: kivinen set sender to kivinen@iki.fi using -f
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <20017.28147.864891.493584@fireball.kivinen.iki.fi>
Date: Thu, 28 Jul 2011 17:10:59 +0300
From: Tero Kivinen <kivinen@iki.fi>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [IPsec] Last Call:	<draft-kivinen-ipsecme-secure-password-framework-01.txt>	(Secure	Password Framework for IKEv2) to Informational RFC
In-Reply-To: <78B594BA-9406-44A2-AB8E-0BF5A425AEC1@vpnc.org>
References: <20110727164459.29853.48303.idtracker@ietfa.amsl.com> <7C54FFE2-FFE0-4B4C-BF7E-142A6B10DF6B@checkpoint.com> <78B594BA-9406-44A2-AB8E-0BF5A425AEC1@vpnc.org>
X-Mailer: VM 7.19 under Emacs 21.4.1
X-Edit-Time: 17 min
X-Total-Time: 21 min
X-Mailman-Approved-At: Thu, 28 Jul 2011 09:56:45 -0700
Cc: IPsecme WG <ipsec@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: Thu, 28 Jul 2011 14:11:11 -0000

Paul Hoffman writes:
> > Partially yes, but unfortunately all of the authors of those actual
> > protocols decided that they wanted to continue publishing those drafts
> > as individual RFCs, and each of them used different way to negotiate
> > them, so there was no way to even implement multiple of them.
> 
> Is this true? Because each has it's own way to negotiate its use,
> one should be able to implement multiple of the competing proposals
> as-is, yes? 

Before I proposed my common way to negotiate only one of the proposed
protocols included any kind of support for indicating which version is
used. The other two just assumed that initiator selects the method and
responder supports it without any negotiation, meaning there was no
way to make initiator version which supports multiple methods without
trying the first method, if that failed, then starting IKE_SA_INIT
from the beginning and trying second method etc...

This has already been changing as one of the drafts is already changed
to support what I have described in my draft, and another author
has said he will update his. The third one already had negotiation
altough done bit differently to compared what I proposed.

As an implementor I myself I want to keep this problem concentrated in
my code, meaning I do not want to make three completely differently
done implementations for the same thing, when I can instead make
generic changes to common code once, and separate the secure password
method related processing in one module taking care as any methods
needed to be implemented.

> > At least this drafts gives you that option to implement multiple of
> > them if you want. This draft only provides instructions for those
> > other draft authors so they can at least common methods to negotiate
> > the feature and use common method to trasmit data between peers.
> 
> True, but it is still punting the problem of us having just one.

Yes, but there is nothing I can do to that. I cannot fix the problem
that all 3 drafts were sent forward and most likely will be published.
If someone will decided only one of them will go forward (and there
will not be any other ever) then my draft will be mostly unneeded as
all of my draft can be put inside that one protocol draft going
forward just like draft-shin-augmented-pake has already done.

If there is no need to make sure multiple drafts make the negotiation
and common payload things similarly as there is only one draft, then
this draft is not needed.

I am also the IANA expert for the IKEv2 registries, and that was the
main reason I wanted to have common way to do things instead of doing
dozen new allocations to the registries just to support 3 bit
different ways to do same thing (when 3 allocations is enough). I
wanted to point this out to the draft authors as early as possible, so
it will not come as suprise to the authors that I do not support their
way of allocating that many codepoints from the registries.
-- 
kivinen@iki.fi

From kivinen@iki.fi  Thu Jul 28 07:27:43 2011
Return-Path: <kivinen@iki.fi>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FF3B21F8BD9; Thu, 28 Jul 2011 07:27: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 1EqdEGcouVJI; Thu, 28 Jul 2011 07:27:43 -0700 (PDT)
Received: from mail.kivinen.iki.fi (fireball.acr.fi [83.145.195.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9741021F8BDA; Thu, 28 Jul 2011 07:27:42 -0700 (PDT)
Received: from fireball.kivinen.iki.fi (localhost [127.0.0.1]) by mail.kivinen.iki.fi (8.14.3/8.14.3) with ESMTP id p6SERcI4009247 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Jul 2011 17:27:38 +0300 (EEST)
Received: (from kivinen@localhost) by fireball.kivinen.iki.fi (8.14.3/8.12.11) id p6SERbqJ017233; Thu, 28 Jul 2011 17:27:37 +0300 (EEST)
X-Authentication-Warning: fireball.kivinen.iki.fi: kivinen set sender to kivinen@iki.fi using -f
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <20017.29145.171495.225683@fireball.kivinen.iki.fi>
Date: Thu, 28 Jul 2011 17:27:37 +0300
From: Tero Kivinen <kivinen@iki.fi>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Subject: Re: [IPsec] Last Call: <draft-kivinen-ipsecme-secure-password-framework-01.txt> (Secure Password Framework for IKEv2) to Informational RFC
In-Reply-To: <4E30F876.70200@gmail.com>
References: <20110727164459.29853.48303.idtracker@ietfa.amsl.com> <7C54FFE2-FFE0-4B4C-BF7E-142A6B10DF6B@checkpoint.com> <78B594BA-9406-44A2-AB8E-0BF5A425AEC1@vpnc.org> <7828ad8727dd860ccd6c5eb5acd52c19.squirrel@www.trepanning.net> <4E30F876.70200@gmail.com>
X-Mailer: VM 7.19 under Emacs 21.4.1
X-Edit-Time: 12 min
X-Total-Time: 11 min
X-Mailman-Approved-At: Thu, 28 Jul 2011 09:56:45 -0700
Cc: IPsecme WG <ipsec@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: Thu, 28 Jul 2011 14:27:43 -0000

Yaron Sheffer writes:
> Back to the matter at hand: I am opposed to 
> draft-kivinen-ipsecme-secure-password-framework. It has served its 
> purpose when two of the proposals were changed to add method 
> negotiation, and thus enable IKE peers to implement none, one or more of 
> these methods.

Actually there is currently only one draft, draft-shin-augmented-pake,
which follows my negotiation process. The
draft-harkins-ipsecme-spsk-auth author did say he is going to change
his draft, but the draft is not yet there, and then there is
draft-kuegler-ipsecme-pace-ikev2 (which you are co-author) which is
doing negotiation differently and I do not know whether that is going
to change to use same way than others.

> I believe the other justifications for this draft, including the
> preservation of IANA IKEv2 namespaces, are bogus.

As an IANA Expert for the registries in question I strongly disagree.

If you want to delay this fight to the IANA allocation time, that is
fine by me, but I will point it out already now that I will be against
allocating separate code points for each protocol as there is no need
for that.

> Adopting the rest of the framework would be a useless exercise.

Keeping the IANA registries clean is important for me, in addition to
make it easy to implement multiple methods in the same implementation.
I do not consider them as useless resons. Especially as it only causes
very small changes to the actual protocol drafts (I would expect less
than an one hour of work).
-- 
kivinen@iki.fi

From gert@space.net  Thu Jul 28 08:23: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 0C16921F8CD4 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 08:23: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 jGAr9L5GAy+L for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 08:23: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 30A1121F8CDF for <ietf@ietf.org>; Thu, 28 Jul 2011 08:23:43 -0700 (PDT)
Received: from mobil.space.net (localhost [127.0.0.1]) by mobil.space.net (Postfix) with ESMTP id 4CD54F858B for <ietf@ietf.org>; Thu, 28 Jul 2011 17:23:41 +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 38FF3F8576 for <ietf@ietf.org>; Thu, 28 Jul 2011 17:23:41 +0200 (CEST)
Received: (qmail 26801 invoked by uid 1007); 28 Jul 2011 17:23:41 +0200
Date: Thu, 28 Jul 2011 17:23:41 +0200
From: Gert Doering <gert@space.net>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
Message-ID: <20110728152341.GT72014@Space.Net>
References: <20110728152018.A2D8318C0F2@mercury.lcs.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110728152018.A2D8318C0F2@mercury.lcs.mit.edu>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Mailman-Approved-At: Thu, 28 Jul 2011 09:56:45 -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, 28 Jul 2011 15:23:44 -0000

Hi,

On Thu, Jul 28, 2011 at 11:20:18AM -0400, Noel Chiappa wrote:
> Apple has enough market share to get away with that. IPv6 doesn't.

Just how much market share has 6to4, if we exclude those two users?

It's amazing how many human life cycles got wasted on this (and that
I can't refuse to be sucked into this again).

gert
-- 
have you enabled 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 nico@cryptonector.com  Thu Jul 28 08:50:59 2011
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E2EC21F8C42; Thu, 28 Jul 2011 08:50:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.816
X-Spam-Level: 
X-Spam-Status: No, score=-2.816 tagged_above=-999 required=5 tests=[AWL=-0.839, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hjvMXTShJ6y6; Thu, 28 Jul 2011 08:50:58 -0700 (PDT)
Received: from homiemail-a64.g.dreamhost.com (caiajhbdcbef.dreamhost.com [208.97.132.145]) by ietfa.amsl.com (Postfix) with ESMTP id 9E9EE21F8B9E; Thu, 28 Jul 2011 08:50:52 -0700 (PDT)
Received: from homiemail-a64.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a64.g.dreamhost.com (Postfix) with ESMTP id 2D77343807E; Thu, 28 Jul 2011 08:50:52 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=cryptonector.com; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc: content-type; q=dns; s=cryptonector.com; b=eQX10NzzWVjD1SVS0wiBE RQzVaGsK1xZmj7Amme38AQ/oUGrYZ9V9N/ec0uy10r+38wpx/utn8DlVptlPCa0/ lg1uw9Wu9Wcx6SR+MljV3E3/wa9yGdPFMrZYxvLyc6KVld7OYRTI4fBJNqZlvKCZ wtp85vEVJlGoFGdEiPd6mE=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=JlLmT9/6scvxkW+XfA4V 4UIAYgg=; b=erIgtLVD5F4pBut38AVj3aVuNs9HMN77fK6LCldC5t7gzD4AbLX5 k8jfFPOfP5Qcgg4CAhOyZO19SqGb/nisMQxyDSKhDhYilb5+14INDWBZ+CWdp/2f rdO0kKUgSIItcXw2E396vL52hY3Ow88p9nm1wjxUBvez9P0G8rXtU68=
Received: from mail-pz0-f53.google.com (mail-pz0-f53.google.com [209.85.210.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a64.g.dreamhost.com (Postfix) with ESMTPSA id F21DE438072;  Thu, 28 Jul 2011 08:50:51 -0700 (PDT)
Received: by pzk6 with SMTP id 6so4445841pzk.26 for <multiple recipients>; Thu, 28 Jul 2011 08:50:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.21.5 with SMTP id r5mr483043pbe.39.1311868251475; Thu, 28 Jul 2011 08:50:51 -0700 (PDT)
Received: by 10.68.48.74 with HTTP; Thu, 28 Jul 2011 08:50:51 -0700 (PDT)
In-Reply-To: <20110727164459.29853.48303.idtracker@ietfa.amsl.com>
References: <20110727164459.29853.48303.idtracker@ietfa.amsl.com>
Date: Thu, 28 Jul 2011 10:50:51 -0500
Message-ID: <CAK3OfOjE2Nc7=qBAOZXvpRyRdiaTNNdSTmAL4wguLX9t562NQA@mail.gmail.com>
Subject: Re: Last Call: <draft-kivinen-ipsecme-secure-password-framework-01.txt> (Secure Password Framework for IKEv2) to Informational RFC
From: Nico Williams <nico@cryptonector.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=UTF-8
X-Mailman-Approved-At: Thu, 28 Jul 2011 09:56:45 -0700
Cc: ipsec@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: Thu, 28 Jul 2011 15:50:59 -0000

I support an IKEv2 ZKPP method framework.  I don't understand the
controversy -- i.e., I think it's much ado about nothing.

Nico
--

From kfall@cs.Berkeley.EDU  Wed Jul 27 21:49:48 2011
Return-Path: <kfall@cs.Berkeley.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 D018321F8B9F for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 21:49: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 yreo003eotAf for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 21:49:48 -0700 (PDT)
Received: from gateway0.EECS.Berkeley.EDU (gateway0.EECS.Berkeley.EDU [169.229.60.87]) by ietfa.amsl.com (Postfix) with ESMTP id 664D421F8AFD for <ietf@ietf.org>; Wed, 27 Jul 2011 21:49:48 -0700 (PDT)
Received: from [172.16.62.142] (modemcable252.155-70-69.static.videotron.ca [69.70.155.252]) (authenticated bits=0) by gateway0.EECS.Berkeley.EDU (8.14.5/8.13.5) with ESMTP id p6S4nhij005780 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 27 Jul 2011 21:49:46 -0700 (PDT)
Subject: Re: Kevin's second byte question
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Kevin Fall <kfall@cs.Berkeley.EDU>
In-Reply-To: <4E308B21.1090305@gmail.com>
Date: Wed, 27 Jul 2011 21:49:42 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <05599CE4-0BCE-4252-AC83-84B80D8116AA@cs.Berkeley.EDU>
References: <4E308B21.1090305@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Thu, 28 Jul 2011 10:01:03 -0700
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, 28 Jul 2011 04:49:48 -0000

Thanks for the quick response.

Here's what my reading revealed, and you can tell me if I'm in error or =
not...

RFC3260 tells us that the first six bits (not 8) are called the DS Field =
or Differentiated Services Field, and the subsequent
two bits are referred to as ECN ("ECN field" according to RFC 3168).  =
Same applies for what was formerly the IPv6 traffic class byte.

That said, RFC 3260 is Informational, yet claims to update =
standards-track RFCs 2474 and 2597.  I'm not quite sure what sort of =
status that
leaves us with. [?]

(normally this wouldn't really concern me all that much, but I'm writing =
some introductory material and want to ensure the proper current =
terminology is being used.  The thing that caused me to really notice =
this was RFC 6145... esp section 5.1).

thx,
- K


On Jul 27, 2011, at Jul 273:03 PMPDT, Brian E Carpenter wrote:

> The second byte in an IPv4 header is called the Differentiated =
Services Field.
>=20
> Quoting RFC 2474:
>=20
> 2.  Terminology Used in This Document
> ...
>   Differentiated Services Field: the IPv4 header TOS octet or the IPv6
>   Traffic Class octet when interpreted in conformance with the
>   definition given in this document.  Also DS field.
>=20
> It's a historical accident that the ECN bits were shoehorned into this =
octet.
>=20
> --=20
> Regards
>   Brian Carpenter
>=20
>=20


From daedulus@btconnect.com  Thu Jul 28 10:37:28 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 7CA3B21F88E5 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 10:37:28 -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 IxnB-IQOuYD9 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 10:37:27 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr07.btconnect.com [213.123.26.185]) by ietfa.amsl.com (Postfix) with ESMTP id 3E87121F88A5 for <ietf@ietf.org>; Thu, 28 Jul 2011 10:37:26 -0700 (PDT)
Received: from host109-153-78-164.range109-153.btcentralplus.com (HELO pc6) ([109.153.78.164]) by c2beaomr07.btconnect.com with SMTP id DUU81617; Thu, 28 Jul 2011 18:37:21 +0100 (BST)
Message-ID: <005d01cc4d44$3136eda0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Sean Turner" <turners@ieca.com>, <ietf@ietf.org>
References: <20110725171748.GA13506@amsl.com> <4E2DAF60.8030307@dcrocker.net> <4E2FFFDF.2080601@ieca.com>
Subject: Re: DKIM Signatures now being applied to IETF Email
Date: Thu, 28 Jul 2011 18:34:12 +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.4E319E50.006A, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.7.28.165114:17:7.586, ip=109.153.78.164, 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, __STOCK_PHRASE_7, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_1400_1499, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_2000_LESS, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr07.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020C.4E319E53.0067,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: Thu, 28 Jul 2011 17:37:28 -0000

---- Original Message -----
From: "Sean Turner" <turners@ieca.com>
To: <ietf@ietf.org>
Sent: Wednesday, July 27, 2011 2:09 PM

> On 7/25/11 2:01 PM, Dave CROCKER wrote:
> >
> >
> > On 7/25/2011 1:17 PM, Glen wrote:
> >> I am very pleased to report that the IETF is now applying DKIM signatures
> >> to all outgoing list email from mailman.
> >
> >
> > I'll be presumptuous and speak on behalf of the DKIM operations
> > community, rather than just myself:
> >
> > Cool! Thanks.
>
> +1 to that!

-100

The minor point is that e-mails have just got yet bigger.  They are now 100-150%
bigger than when first I started following the IETF and it is not that people
have more to say, but that the junk at the front has expanded out of all
recognition.  This costs, transmission time, processing storage etc.  The
transmission time is significant (I imagine) because of POP3 which seems to take
2n+ messages, n round trips, before starting to download anything out of n
e-mails.

But more importantly we have abolished the end-to-end principle.  If I am going
to benefit from improved security on e-mail, I want to from the originator to
me, not some half-way house giving a spurious impression of accuracy.

Tom Petch

> Personally, I like it when we eat our own dog food ;)
>
> spt
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From evnikita2@gmail.com  Thu Jul 28 10:55:16 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 6D8BE11E80CC for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 10:55:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.497
X-Spam-Level: 
X-Spam-Status: No, score=-3.497 tagged_above=-999 required=5 tests=[AWL=0.102,  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 HQAr5scMqvbB for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 10:55:15 -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 A13ED11E807B for <ietf@ietf.org>; Thu, 28 Jul 2011 10:55:15 -0700 (PDT)
Received: by fxe6 with SMTP id 6so1676834fxe.31 for <ietf@ietf.org>; Thu, 28 Jul 2011 10:55:11 -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=kyomjhVubqa6vntIocF5MwKWWdmft5maCVaF+mV52lQ=; b=yGSMrXCZ6gsIQ4X309+bZqT8GyvjbRJb+5eEVVceY0X+A260b8l7PFlPlE8Nv32Aos ti9WyPlBQrZ+49a97umD+dxu4WrIwJn96gONu98QrlCueOWTDJmMa+L1m+6BJQjc/rLt 1gzjiYJt0ayK8cbiQfTQLuea6Ndd8UCfSgoTw=
Received: by 10.223.7.65 with SMTP id c1mr339398fac.131.1311875711125; Thu, 28 Jul 2011 10:55:11 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id x2sm415877fal.44.2011.07.28.10.55.09 (version=SSLv3 cipher=OTHER); Thu, 28 Jul 2011 10:55:09 -0700 (PDT)
Message-ID: <4E31A2A6.1020402@gmail.com>
Date: Thu, 28 Jul 2011 20:55:50 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: Last Call: <draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <4E30EE32.3020404@gmail.com> <4E3169A0.1050807@stpeter.im>
In-Reply-To: <4E3169A0.1050807@stpeter.im>
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, 28 Jul 2011 17:55:16 -0000

28.07.2011 16:52, Peter Saint-Andre wrote:
> On 7/28/11 1:05 AM, Mykyta Yevstifeyev wrote:
>> Hello,
>>
>> The new version is obviously shorter, but it omits some points.  With
>> eliminating of DS level, RFC 5657 makes no sense more.
> Wrong. The *title* needs to be adjusted, but mutatis mutandis the
> general advice is useful.

The document says:

>     RFC 2026 [1] requires a report
>     that documents interoperability between at least two implementations
>     from different code bases as an interim step ("Draft Standard")
>     before a specification can be advanced further to the third and final
>     maturity level ("Standard") based on widespread deployment and use.
>     In contrast, this document measures interoperability through
>     widespread deployment of multiple implementations from different code
>     bases, thus condensing the two separate metrics into one.

which implies that no requirement for interoperability reports is set.  
RFC 5735 defines what the implementation report is; so I think retaining 
RFC 5735 as BCP will create confusion, as it will define procedures for 
the issue which no longer exists.

>
>> It should be
>> obsoleted and moved to Historic by your document, if IESG decides to
>> eliminate the requirement for interoperability documentation, which I am
>> opposed to (see my LC comments to -06).
> I see no reason to move RFC 5657 to Historic.

See above.

>
>> Another issue is STD numbers.  Mentioning that they are still assigned
>> to ISs in Section 2.2 should be fine.
> The STD issue is orthogonal.
>
>> Also, Section 3.3:
>>
>>>      (2) At any time after two years from the approval of this document as
>>>          a BCP, the IESG may choose to reclassify any Draft Standard
>>>          document as Proposed Standard.
>> Won't such action be allowed after 2 years from approval?
> That's what the text says, no?

Yes, I misunderstood the statement.  I thought that before 2 years come, 
DS->PS may be OK while after these 2 years this won't be OK, while it's 
vice versa.

Mykyta

>
> Peter
>


From msk@cloudmark.com  Thu Jul 28 13:06:04 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 9EA9F11E8110 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 13:06:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.261
X-Spam-Level: 
X-Spam-Status: No, score=-103.261 tagged_above=-999 required=5 tests=[AWL=-0.663, 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 QEtW6qxof8Nl for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 13:06:02 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by ietfa.amsl.com (Postfix) with ESMTP id B713511E8083 for <ietf@ietf.org>; Thu, 28 Jul 2011 13:06:02 -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, 28 Jul 2011 13:06:02 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: IETF discussion list <ietf@ietf.org>
Date: Thu, 28 Jul 2011 13:06:00 -0700
Subject: On attending BoFs
Thread-Topic: On attending BoFs
Thread-Index: AcxNYcVWV+JqIblYS3CZuvd+gHzh0w==
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF4A7@EXCH-C2.corp.cloudmark.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_F5833273385BB34F99288B3648C4F06F13512DF4A7EXCHC2corpclo_"
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, 28 Jul 2011 20:06:04 -0000

--_000_F5833273385BB34F99288B3648C4F06F13512DF4A7EXCHC2corpclo_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I've been encouraged to say this to a wider audience, so here I am.

A BoF is the IETF's tool for gauging interest in a new topic and a potentia=
l working group charter.  This doesn't just mean a showing of people that w=
ould track this work if it were to begin, but really the main purpose is to=
 determine the level of commitment to do the work, which includes things li=
ke counting people willing to review and comment on documents, people willi=
ng to act as editors, potential implementers, and perhaps potential co-chai=
rs.

When we ask for a BoF room, we need to give an indication of estimated atte=
ndance.  Sometimes it's hard to make a good guess and so we underestimate, =
intending to keep larger rooms available for groups that need them.  As a r=
esult, the BoF room is packed.  But when it's packed with what have come to=
 be known as "tourists", those people that could be counted as committed to=
 the work can't even get into the room, which jeopardizes the creation of a=
n otherwise viable working group.  I suspect I can safely say Dave Crocker =
would categorize this as an unintentional denial-of-service attack on the n=
ew work.

And it's certainly not friendly to the work that's trying to get started by=
 filling a seat in a room "because it's warm."

Perhaps in the future this should be mentioned to BoF attendees before the =
meeting really gets going.  I certainly plan to do so for future BoFs that =
I run or at which I present.

Thanks,
-MSK

--_000_F5833273385BB34F99288B3648C4F06F13512DF4A7EXCHC2corpclo_
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=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft 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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	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;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>I&#8217;ve been =
encouraged to say this to a wider audience, so here I am.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>A BoF is the IE=
TF&#8217;s tool for gauging interest in a new topic and a potential working=
 group charter.&nbsp; This doesn&#8217;t just mean a showing of people that=
 would track this work if it were to begin, but really the main purpose is =
to determine the level of commitment to do the work, which includes things =
like counting people willing to review and comment on documents, people wil=
ling to act as editors, potential implementers, and perhaps potential co-ch=
airs.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMs=
oNormal>When we ask for a BoF room, we need to give an indication of estima=
ted attendance.&nbsp; Sometimes it&#8217;s hard to make a good guess and so=
 we underestimate, intending to keep larger rooms available for groups that=
 need them.&nbsp; As a result, the BoF room is packed.&nbsp; But when it&#8=
217;s packed with what have come to be known as &#8220;tourists&#8221;, tho=
se people that could be counted as committed to the work can&#8217;t even g=
et into the room, which jeopardizes the creation of an otherwise viable wor=
king group.&nbsp; I suspect I can safely say Dave Crocker would categorize =
this as an unintentional denial-of-service attack on the new work.<o:p></o:=
p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>And it=
&#8217;s certainly not friendly to the work that&#8217;s trying to get star=
ted by filling a seat in a room &#8220;because it&#8217;s warm.&#8221;<o:p>=
</o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Pe=
rhaps in the future this should be mentioned to BoF attendees before the me=
eting really gets going.&nbsp; I certainly plan to do so for future BoFs th=
at I run or at which I present.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nb=
sp;</o:p></p><p class=3DMsoNormal>Thanks,<o:p></o:p></p><p class=3DMsoNorma=
l>-MSK<o:p></o:p></p></div></body></html>=

--_000_F5833273385BB34F99288B3648C4F06F13512DF4A7EXCHC2corpclo_--

From dwing@cisco.com  Thu Jul 28 13:24:02 2011
Return-Path: <dwing@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 A5EFF11E8163 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 13:24:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.912
X-Spam-Level: 
X-Spam-Status: No, score=-103.912 tagged_above=-999 required=5 tests=[AWL=-1.313, 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 hrYxqKMrRaVM for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 13:24:01 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id ACDE511E814C for <ietf@ietf.org>; Thu, 28 Jul 2011 13:24:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=2233; q=dns/txt; s=iport; t=1311884641; x=1313094241; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=s4vEeS32u8p7SzzClopBHCJAQ5U790fmfIWXyx23KPo=; b=HHghua0cL6YWNpSuggBpcO1uLVN/0tbEECav3okgpM0SI/SaMd9bzA2P BZzCaA2GVlPwpvD4dCIcehirAWlRDcAoD/DOHF6CXwteSxrrL8ctWDGmq CI0QJ/SYehQS4ZxsYwZq03AGUDn3WrnHKlGZbEjBFYgQZKifblLCPSYgp w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AukAAFzEMU6rRDoI/2dsb2JhbAA0AQEBAQMIDAEbEFEBBAIKDwIEAQEXHQcUBigNDggBAQUBFg8Yl2uBa41kd61TnjmDI4MeBKN5
X-IronPort-AV: E=Sophos;i="4.67,284,1309737600";  d="scan'208";a="7529890"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by rcdn-iport-9.cisco.com with ESMTP; 28 Jul 2011 20:24:01 +0000
Received: from dwingWS (sjc-vpn3-89.cisco.com [10.21.64.89]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p6SKO0Eo029420; Thu, 28 Jul 2011 20:24:00 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Murray S. Kucherawy'" <msk@cloudmark.com>, "'IETF discussion list'" <ietf@ietf.org>
References: <F5833273385BB34F99288B3648C4F06F13512DF4A7@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF4A7@EXCH-C2.corp.cloudmark.com>
Subject: RE: On attending BoFs
Date: Thu, 28 Jul 2011 16:23:59 -0400
Message-ID: <051e01cc4d64$493d3c40$dbb7b4c0$@com>
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: AcxNYcVWV+JqIblYS3CZuvd+gHzh0wAASsOQ
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 20:24:02 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Murray S. Kucherawy
> Sent: Thursday, July 28, 2011 4:06 PM
> To: IETF discussion list
> Subject: On attending BoFs
> 
> I've been encouraged to say this to a wider audience, so here I am.
> 
> 
> 
> A BoF is the IETF's tool for gauging interest in a new topic and a
> potential working group charter.  This doesn't just mean a showing of
> people that would track this work if it were to begin, but really the
> main purpose is to determine the level of commitment to do the work,
> which includes things like counting people willing to review and
> comment on documents, people willing to act as editors, potential
> implementers, and perhaps potential co-chairs.
> 
> 
> 
> When we ask for a BoF room, we need to give an indication of estimated
> attendance.  Sometimes it's hard to make a good guess and so we
> underestimate, intending to keep larger rooms available for groups that
> need them.  As a result, the BoF room is packed.  But when it's packed
> with what have come to be known as "tourists", those people that could
> be counted as committed to the work can't even get into the room, which
> jeopardizes the creation of an otherwise viable working group.  I
> suspect I can safely say Dave Crocker would categorize this as an
> unintentional denial-of-service attack on the new work.
> 
> 
> 
> And it's certainly not friendly to the work that's trying to get
> started by filling a seat in a room "because it's warm."
> 
> 
> 
> Perhaps in the future this should be mentioned to BoF attendees before
> the meeting really gets going.  I certainly plan to do so for future
> BoFs that I run or at which I present.

You're going to ask attendees to self-identify as tourists and leave
the room?  Today's tourists may well become tomorrow's document 
editors.

BoFs are IETF's tchotchkes.  People like new things.  As an example,
Homenet is a new WG (not a BoF), and was well attended (every seat
filled, people sitting on the floor, and standing).

Let's just assign large enough rooms to BoFs and newly-formed WGs
so that the work can start in earnest.

-d



From lorenzo@google.com  Thu Jul 28 13:27:46 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 739E311E80FB for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 13:27:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.886
X-Spam-Level: 
X-Spam-Status: No, score=-105.886 tagged_above=-999 required=5 tests=[AWL=0.090, 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 bq5Nu-PEbcLW for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 13:27:45 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id 4957C11E8083 for <ietf@ietf.org>; Thu, 28 Jul 2011 13:27:44 -0700 (PDT)
Received: from hpaq2.eem.corp.google.com (hpaq2.eem.corp.google.com [172.25.149.2]) by smtp-out.google.com with ESMTP id p6SKRhuW016204 for <ietf@ietf.org>; Thu, 28 Jul 2011 13:27:43 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1311884863; bh=5PfjFKvDOP508Tc5on0dVAnm5qI=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=QUSqDyjLFeQ8WU9Sf+tUSF4TtCVdungR+5YHYTmifxYNwONabUiK+NKDk+v1gjYcr BKguTKlUGadeyX35F7Qqw==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type:x-system-of-record; b=Hn7qLWOyrj5mP6ThhREsI94Hbkmh0FhNhWyCuPp8PZmmBvBExKFKwZmUrUI0oidSP DZjPIYfdu6orlVgrfE8Jg==
Received: from gxk28 (gxk28.prod.google.com [10.202.11.28]) by hpaq2.eem.corp.google.com with ESMTP id p6SKRfPl023730 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Thu, 28 Jul 2011 13:27:42 -0700
Received: by gxk28 with SMTP id 28so2791150gxk.41 for <ietf@ietf.org>; Thu, 28 Jul 2011 13:27:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=0ANnYZtKrCmTXJMN0YjbU3rX3F+HhoJY5W8ANm7t+kw=; b=dmSrI2/plyCvgS1R03DYdwZiK08YJ3lvxFd/trG7hereRYaX8+RJlFSkNipH8KHYXA ufhGvpHuERejjx6CrvhQ==
Received: by 10.151.15.12 with SMTP id s12mr168325ybi.0.1311884861288; Thu, 28 Jul 2011 13:27:41 -0700 (PDT)
Received: by 10.151.15.12 with SMTP id s12mr168316ybi.0.1311884861135; Thu, 28 Jul 2011 13:27:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.151.156.5 with HTTP; Thu, 28 Jul 2011 13:27:21 -0700 (PDT)
In-Reply-To: <10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <m1QlzXt-0001gSC@stereo.hq.phicoh.net> <2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com> <392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local> <10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 28 Jul 2011 16:27:21 -0400
Message-ID: <CAKD1Yr3gv=+HfEZMsU0enNh8OQbemQh6iRzpGHsnmr7OJrTcFg@mail.gmail.com>
Subject: Re: IPv6 traffic distribution
To: james woodyatt <jhw@apple.com>
Content-Type: multipart/alternative; boundary=000e0cd6ad3c225d4304a926ffd3
X-System-Of-Record: true
Cc: Michel Py <michel@arneill-py.sacramento.ca.us>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 20:27:46 -0000

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

On Thu, Jul 28, 2011 at 01:30, james woodyatt <jhw@apple.com> wrote:

> > http://www.pam2010.ethz.ch/papers/full-length/15.pdf
> > Slightly less than 50% of IPv6 traffic comes from a MacOS client (fig
> > 3); about 90% MacOS hits is 6to4, which possibly means (to me) that this
> > piece of 6to4 MacOS software of yours represents a third of global IPv6
> > traffic.
> >
> > Would you care to comment on the numbers?
>
> p1.  Those numbers are badly outdated.
>

Speaking as one of the authors of that paper: correct, the numbers are badly
outdated. You can find the more recent numbers resulting from those
measurements at:

http://www.google.com/intl/en/ipv6/statistics/

You will see that 6to4 now accounts for approximately 10% of total IPv6
traffic as measured using that methodology, and is steadily declining
(modulo seasonal variations like the French going on holiday).

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

<div class=3D"gmail_quote">On Thu, Jul 28, 2011 at 01:30, james woodyatt <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:jhw@apple.com">jhw@apple.com</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; <a href=3D"http://www.pam2010.ethz.ch/papers/full-le=
ngth/15.pdf" target=3D"_blank">http://www.pam2010.ethz.ch/papers/full-lengt=
h/15.pdf</a><br>
&gt; Slightly less than 50% of IPv6 traffic comes from a MacOS client (fig<=
br>
&gt; 3); about 90% MacOS hits is 6to4, which possibly means (to me) that th=
is<br>
&gt; piece of 6to4 MacOS software of yours represents a third of global IPv=
6<br>
&gt; traffic.<br>
&gt;<br>
&gt; Would you care to comment on the numbers?<br>
<br>
</div>p1. =A0Those numbers are badly outdated.<br></blockquote><div><br></d=
iv><div>Speaking as one of the authors of that paper: correct, the numbers =
are badly outdated. You can find the more recent numbers resulting from tho=
se measurements at:</div>

<div><br></div><div><a href=3D"http://www.google.com/intl/en/ipv6/statistic=
s/">http://www.google.com/intl/en/ipv6/statistics/</a></div><div><br></div>=
<div>You will see that 6to4 now accounts for approximately 10% of total IPv=
6 traffic as measured using that methodology, and is steadily declining (mo=
dulo seasonal variations like the French going on holiday).</div>

</div>

--000e0cd6ad3c225d4304a926ffd3--

From barryleiba.mailing.lists@gmail.com  Thu Jul 28 13:35:17 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 318C911E80D9 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 13:35:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.057
X-Spam-Level: 
X-Spam-Status: No, score=-103.057 tagged_above=-999 required=5 tests=[AWL=-0.080, 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 zoDVde0l6dqg for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 13:35:16 -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 9DCF311E8081 for <ietf@ietf.org>; Thu, 28 Jul 2011 13:35:16 -0700 (PDT)
Received: by gxk19 with SMTP id 19so2574600gxk.31 for <ietf@ietf.org>; Thu, 28 Jul 2011 13:35:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=aU1P7LeARTc7Gb9NP2j/D6i3WC48KyET+wm5emFiVuM=; b=QXn2AfeQMhYVhwO0n5TcQvpaJRSOveA/OmAq7ah1FkQxomUgbwc0hR3b5/KGwsewdo hfcCAIRSBK6Eby3cEqNOJEW3zNcmTIIWHheEbbtpqTqjo9wHTZ5FlcjQMTaXmV4S5PmY iRH0nhb/TAA+5JL4ikmeG8VC5wTYoIMo5Fk2Q=
MIME-Version: 1.0
Received: by 10.236.189.97 with SMTP id b61mr294418yhn.482.1311885315707; Thu, 28 Jul 2011 13:35:15 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.32.15 with HTTP; Thu, 28 Jul 2011 13:35:15 -0700 (PDT)
In-Reply-To: <051e01cc4d64$493d3c40$dbb7b4c0$@com>
References: <F5833273385BB34F99288B3648C4F06F13512DF4A7@EXCH-C2.corp.cloudmark.com> <051e01cc4d64$493d3c40$dbb7b4c0$@com>
Date: Thu, 28 Jul 2011 16:35:15 -0400
X-Google-Sender-Auth: pOj3_1IuWVGHfJnsN1GW0N2AMwM
Message-ID: <CAC4RtVCLayw1czVKnFG0WPHyL6dUSS0h6zcdSrMqqq9OcNFtrg@mail.gmail.com>
Subject: Re: On attending BoFs
From: Barry Leiba <barryleiba@computer.org>
To: Dan Wing <dwing@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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, 28 Jul 2011 20:35:17 -0000

> You're going to ask attendees to self-identify as tourists and leave
> the room? =A0Today's tourists may well become tomorrow's document
> editors.
...
> Let's just assign large enough rooms to BoFs and newly-formed WGs
> so that the work can start in earnest.

I agree.  If people are there paying attention, I want them there.
Lots of people don't know whether they're going to commit to doing
work until the end of the BoF, after they've heard all the stuff about
problem statement, work scope, and proposed work items.

I'd rather just make sure we have rooms that are big enough, and leave
it at that.  BoFs tend to be artificially busy because people like
those tchotchkes -- people are interested in seeing what the new
proposals are about.  Let's not discourage that, but feed it.

Barry

From stpeter@stpeter.im  Thu Jul 28 13:37:23 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 2BFE111E8137 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 13:37:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.56
X-Spam-Level: 
X-Spam-Status: No, score=-102.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yq2CorCaL9xn for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 13:37:22 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 9AF4611E8114 for <ietf@ietf.org>; Thu, 28 Jul 2011 13:37:20 -0700 (PDT)
Received: from dhcp-13ac.meeting.ietf.org (unknown [198.135.0.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 2644E410E8; Thu, 28 Jul 2011 14:38:25 -0600 (MDT)
Message-ID: <4E31C87E.4090606@stpeter.im>
Date: Thu, 28 Jul 2011 16:37:18 -0400
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Subject: Re: On attending BoFs
References: <F5833273385BB34F99288B3648C4F06F13512DF4A7@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF4A7@EXCH-C2.corp.cloudmark.com>
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
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, 28 Jul 2011 20:37:23 -0000

On 7/28/11 4:06 PM, Murray S. Kucherawy wrote:

> When we ask for a BoF room, we need to give an indication of estimated
> attendance.  Sometimes itâ€™s hard to make a good guess and so we
> underestimate, intending to keep larger rooms available for groups that
> need them.

I think the BoF chairs and responsible ADs need to request larger rooms
for BoFs. After the REPUTE BOF, I talked with the Secretariat
(specifically Wanda Lo, who does an amazing job with the schedule!)
about poking the chairs and ADs when they request BoF rooms to make sure
that we don't assign small rooms to BoFs, at least without careful
consideration.

Peter

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



From michel@arneill-py.sacramento.ca.us  Thu Jul 28 13:51:43 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 D49D321F8B1B for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 13:51:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[AWL=0.168,  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 fzLwpYZKM5Yu for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 13:51:43 -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 469F221F8B29 for <ietf@ietf.org>; Thu, 28 Jul 2011 13:51:43 -0700 (PDT)
Subject: RE: IPv6 traffic distribution
Date: Thu, 28 Jul 2011 13:51:39 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF635@newserver.arneill-py.local>
Content-class: urn:content-classes:message
In-Reply-To: <CAKD1Yr3gv=+HfEZMsU0enNh8OQbemQh6iRzpGHsnmr7OJrTcFg@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-MimeOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: IPv6 traffic distribution
Thread-Index: AcxNZNAOnk0d1f6aRpKLOuBNcOoI/AAAqI8g
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <m1QlzXt-0001gSC@stereo.hq.phicoh.net> <2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com> <392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local> <10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com> <CAKD1Yr3gv=+HfEZMsU0enNh8OQbemQh6iRzpGHsnmr7OJrTcFg@mail.gmail.com>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Lorenzo Colitti" <lorenzo@google.com>, "james woodyatt" <jhw@apple.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, 28 Jul 2011 20:51:44 -0000

Lorenzo,

> Lorenzo Colitti wrote:
> http://www.google.com/intl/en/ipv6/statistics/

Thanks for the update.
Clarification: in your stats, is AS12322's traffic classified as native
or as 6to4/teredo?

Michel.


From brian.e.carpenter@gmail.com  Thu Jul 28 13:57:46 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 0DE515E801D for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 13:57:46 -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 Tg6qjYdJej4i for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 13:57:45 -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 181E95E8014 for <ietf@ietf.org>; Thu, 28 Jul 2011 13:57:44 -0700 (PDT)
Received: by gwb20 with SMTP id 20so2728319gwb.31 for <ietf@ietf.org>; Thu, 28 Jul 2011 13:57:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=ltBCUEC8NUb2juJSHe2q/jicAlc1BiV+uF88hqlXxXc=; b=VRI3aUCIBwu0THwYxB942gVTHqkf0tBVZV+AFLA4RlDvpLGCwfv5yKku/s7yP1oU+2 scKQ2pjl+JUT9xKN+cti37D9Ov//cOLZE/pJUzUhKweTy2Q0bV46xeb9Uk1CCQO8oEF+ zaa4/xiN4tIxIf9sYnf8iJAEPwgTmkFjZuvLI=
Received: by 10.142.238.8 with SMTP id l8mr276292wfh.330.1311886664335; Thu, 28 Jul 2011 13:57:44 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id s6sm795906wff.3.2011.07.28.13.57.41 (version=SSLv3 cipher=OTHER); Thu, 28 Jul 2011 13:57:43 -0700 (PDT)
Message-ID: <4E31CD3D.1020200@gmail.com>
Date: Fri, 29 Jul 2011 08:57: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: Kevin Fall <kfall@cs.Berkeley.EDU>
Subject: Re: Kevin's second byte question
References: <4E308B21.1090305@gmail.com> <05599CE4-0BCE-4252-AC83-84B80D8116AA@cs.Berkeley.EDU>
In-Reply-To: <05599CE4-0BCE-4252-AC83-84B80D8116AA@cs.Berkeley.EDU>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 20:57:46 -0000

On 2011-07-28 16:49, Kevin Fall wrote:
> Thanks for the quick response.
> 
> Here's what my reading revealed, and you can tell me if I'm in error or not...
> 
> RFC3260 tells us that the first six bits (not 8) are called the DS Field or Differentiated Services Field, and the subsequent
> two bits are referred to as ECN ("ECN field" according to RFC 3168).  Same applies for what was formerly the IPv6 traffic class byte.
> 
> That said, RFC 3260 is Informational, yet claims to update standards-track RFCs 2474 and 2597.  I'm not quite sure what sort of status that
> leaves us with. [?]

It can't. That claim shouldn't have been published IMHO. (And yes, I was co-chair
of the diffserv WG at the time). However, it invokes BCP 37 = RFC 2780
which is normative, so probably supersedes RFC 2474. 2780 doesn't answer your
question though, since it refers to the 6-bit DS field and not to the whole
byte or octet except as "superseded".

I think you will need to add a complicated footnote on this.

On 2011-07-29 01:10, Thomson, Martin wrote:

> On 2011-07-27 at 18:03:13, Brian E Carpenter wrote:
>> > The second byte in an IPv4 header is called the Differentiated 
>> > Services Field.
> 
> I believe that this has been obsoleted by RFC 5241.

Good one :-)

    Brian





From lorenzo@google.com  Thu Jul 28 14:09:33 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 7D89C21F855B for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 14:09:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.894
X-Spam-Level: 
X-Spam-Status: No, score=-105.894 tagged_above=-999 required=5 tests=[AWL=0.082, 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 J4Jf6LQCQJ3X for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 14:09:33 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id BBAB021F855A for <ietf@ietf.org>; Thu, 28 Jul 2011 14:09:32 -0700 (PDT)
Received: from wpaz5.hot.corp.google.com (wpaz5.hot.corp.google.com [172.24.198.69]) by smtp-out.google.com with ESMTP id p6SL9VNY010544 for <ietf@ietf.org>; Thu, 28 Jul 2011 14:09:31 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1311887371; bh=VSWPLDIbjrGKKKXvr5ymSqxrHTw=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=a4pYf/k1pFvIm47F1jQDknlGha6U5IgNzZ9Ok0CQw4SMQlW3uSeKlfVob+xOFPPYC v3xAPRw24upQzrqaHb8PQ==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type:x-system-of-record; b=Mc5BNs5p4OdGbLcFd80jBvW9JOvSV80+fg/gyhiaWECzpzZYydWhK3ZsCYi6xH108 emrKz0zrJhsh51KNrCL3A==
Received: from gxk21 (gxk21.prod.google.com [10.202.11.21]) by wpaz5.hot.corp.google.com with ESMTP id p6SL8ZbF016434 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Thu, 28 Jul 2011 14:09:29 -0700
Received: by gxk21 with SMTP id 21so2685252gxk.5 for <ietf@ietf.org>; Thu, 28 Jul 2011 14:09:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=TM5SPve27ovBs6p5dKmON/D9NPmNDMgutMBnRUZYM9g=; b=dracca0X5UP1VTQYT8spww9pB9+h6I+MJdUJ2Cv4h+miI7o+NQMVBIjaBA0UzqaGB1 NyRHJtpRjVj/x167LkOg==
Received: by 10.150.62.6 with SMTP id k6mr32196yba.114.1311887369495; Thu, 28 Jul 2011 14:09:29 -0700 (PDT)
Received: by 10.150.62.6 with SMTP id k6mr32187yba.114.1311887369182; Thu, 28 Jul 2011 14:09:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.151.156.5 with HTTP; Thu, 28 Jul 2011 14:09:09 -0700 (PDT)
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF635@newserver.arneill-py.local>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <m1QlzXt-0001gSC@stereo.hq.phicoh.net> <2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com> <392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local> <10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com> <CAKD1Yr3gv=+HfEZMsU0enNh8OQbemQh6iRzpGHsnmr7OJrTcFg@mail.gmail.com> <392CB277BC2EAE4FB83C1206954BA6CEF635@newserver.arneill-py.local>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 28 Jul 2011 17:09:09 -0400
Message-ID: <CAKD1Yr35ZFYPRknpFUaNK5BK=kGHM2VRKKi29A8FiAVPbLUdnw@mail.gmail.com>
Subject: Re: IPv6 traffic distribution
To: Michel Py <michel@arneill-py.sacramento.ca.us>
Content-Type: multipart/alternative; boundary=000e0cd47baaa01fc904a927941d
X-System-Of-Record: true
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 21:09:33 -0000

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

On Thu, Jul 28, 2011 at 16:51, Michel Py <michel@arneill-py.sacramento.ca.us
> wrote:

> Clarification: in your stats, is AS12322's traffic classified as native
> or as 6to4/teredo?


As the webpage says: "The Total IPv6 graph shows IPv6 users with any type of
connectivity, while the Native IPv6 graph excludes users using 6to4 or
Teredo".

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

<div class=3D"gmail_quote">On Thu, Jul 28, 2011 at 16:51, Michel Py <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:michel@arneill-py.sacramento.ca.us">michel=
@arneill-py.sacramento.ca.us</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">Clarification: in your stats, is AS12322&#39;s traffic cl=
assified as native</div>
or as 6to4/teredo?</blockquote><div><br></div><div>As the webpage says: &qu=
ot;The Total IPv6 graph shows IPv6 users with any type of connectivity, whi=
le the Native IPv6 graph excludes users using 6to4 or Teredo&quot;.=A0</div=
>

</div>

--000e0cd47baaa01fc904a927941d--

From tjc@ecs.soton.ac.uk  Thu Jul 28 14:13:04 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 81D7F11E80FB for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 14:13:04 -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.149,  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 WKimE62FhU8T for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 14:12:49 -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 F12DB11E8099 for <ietf@ietf.org>; Thu, 28 Jul 2011 14:12:47 -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 p6SLChdp016217 for <ietf@ietf.org>; Thu, 28 Jul 2011 22:12:43 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p6SLChdp016217
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1311887564; bh=pEEjLKDjzBo5u1N7ahbdV+l2Jwg=; h=From:Mime-Version:Subject:Date:In-Reply-To:To:References; b=d/UNtGQDMzSqL3GXPN/TQn0NKk6y3HaFQzv2+ROnMsJLz4j/Q8u/qi4c7yv3oi28E K/M+aRjFXGd74vLTiqRROrbpi9xNFYoUAykHT+L2wrBhSYm06qsQcCiBps2ct9z4c+ 2rOCw5zHSlViqsd/VSDHDhEeECH50reYp6P3R6K4=
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 n6RMCh0366153740RA ret-id none; Thu, 28 Jul 2011 22:12:44 +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 p6SLCciT003752 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Thu, 28 Jul 2011 22:12:39 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: multipart/alternative; boundary="Apple-Mail=_D2960829-01E7-433A-9220-89B24C71D2B1"
Subject: Re: IPv6 traffic distribution
Date: Thu, 28 Jul 2011 22:12:37 +0100
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF635@newserver.arneill-py.local>
To: IETF Discussion <ietf@ietf.org>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <m1QlzXt-0001gSC@stereo.hq.phicoh.net> <2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com> <392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local> <10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com> <CAKD1Yr3gv=+HfEZMsU0enNh8OQbemQh6iRzpGHsnmr7OJrTcFg@mail.gmail.com> <392CB277BC2EAE4FB83C1206954BA6CEF635@newserver.arneill-py.local> <3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk>
Message-ID: <EMEW3|fa0511c175232cff9b9cb8310f081538n6RMCh03tjc|ecs.soton.ac.uk|3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.1244.3)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n6RMCh036615374000; tid=n6RMCh0366153740RA; 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: p6SLChdp016217
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, 28 Jul 2011 21:13:04 -0000

--Apple-Mail=_D2960829-01E7-433A-9220-89B24C71D2B1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On 28 Jul 2011, at 21:51, Michel Py wrote:

> Lorenzo,
>=20
>> Lorenzo Colitti wrote:
>> http://www.google.com/intl/en/ipv6/statistics/
>=20
> Thanks for the update.
> Clarification: in your stats, is AS12322's traffic classified as =
native
> or as 6to4/teredo?


Hi,

I just ran a search through our Netflow logs of the most recent flows =
attempting to traverse our enterprise border and this showed:

2002::/16 (6to4):
Summary: total flows: 562468, total bytes: 6.2 G, total packets: 11.0 M=20=


2001::/32 (Teredo):
Summary: total flows: 1363887, total bytes: 4.9 G, total packets: 10.1 M

Other:
Summary: total flows: 23681562, total bytes: 483.1 G, total packets: =
546.9 M

Teredo appears skewed by one host's behaviour which I'll be looking =
into, otherwise it's about what I'd expect with around 1% by volume =
being 6to4.

Tim=

--Apple-Mail=_D2960829-01E7-433A-9220-89B24C71D2B1
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 28 Jul 2011, at 21:51, Michel Py wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>Lorenzo,<br><br><blockquote type=3D"cite">Lorenzo =
Colitti wrote:<br></blockquote><blockquote type=3D"cite"><a =
href=3D"http://www.google.com/intl/en/ipv6/statistics/">http://www.google.=
com/intl/en/ipv6/statistics/</a><br></blockquote><br>Thanks for the =
update.<br>Clarification: in your stats, is AS12322's traffic classified =
as native<br>or as =
6to4/teredo?<br></div></blockquote></div><div><br></div>Hi,<div><br></div>=
<div>I just ran a search through our Netflow logs of the most recent =
flows attempting to traverse our enterprise border and this =
showed:</div><div><br><div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
12px/normal Helvetica; ">2002::/16 (6to4):</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: =
normal normal normal 14px/normal Courier; "><font =
class=3D"Apple-style-span" face=3D"Helvetica" size=3D"3">Summary: total =
flows: 562468, total bytes: 6.2 G, total packets: 11.0 =
M&nbsp;</font></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
14px/normal Courier; min-height: 17px; "><font class=3D"Apple-style-span" =
face=3D"Helvetica" size=3D"3"><br></font></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: =
normal normal normal 14px/normal Courier; "><font =
class=3D"Apple-style-span" face=3D"Helvetica" size=3D"3">2001::/32 =
(Teredo):</font></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
14px/normal Courier; "><font class=3D"Apple-style-span" face=3D"Helvetica"=
 size=3D"3">Summary: total flows: 1363887, total bytes: 4.9 G, total =
packets: 10.1 M</font></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
14px/normal Courier; min-height: 17px; "><font class=3D"Apple-style-span" =
face=3D"Helvetica" size=3D"3"><br></font></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: =
normal normal normal 12px/normal Helvetica; ">Other:</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 14px/normal Courier; =
"><font class=3D"Apple-style-span" face=3D"Helvetica" size=3D"3">Summary: =
total flows: 23681562, total bytes: 483.1 G, total packets: 546.9 =
M</font></div></div></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
14px/normal Courier; "><font class=3D"Apple-style-span" face=3D"Helvetica"=
 size=3D"3"><br></font></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 14px/normal Courier; "><font class=3D"Apple-style-span" =
face=3D"Helvetica" size=3D"3">Teredo appears skewed by one host's =
behaviour which I'll be looking into, otherwise it's about what I'd =
expect with around 1% by volume being 6to4.</font></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 14px/normal Courier; =
"><font class=3D"Apple-style-span" face=3D"Helvetica" =
size=3D"3"><br></font></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
14px/normal Courier; "><font class=3D"Apple-style-span" face=3D"Helvetica"=
 size=3D"3">Tim</font></div></body></html>=

--Apple-Mail=_D2960829-01E7-433A-9220-89B24C71D2B1--

From michel@arneill-py.sacramento.ca.us  Thu Jul 28 14:24:21 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 E2CCC11E812F for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 14:24:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.116
X-Spam-Level: 
X-Spam-Status: No, score=-2.116 tagged_above=-999 required=5 tests=[AWL=0.149,  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 RheCikg2sgam for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 14:24:21 -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 C394B11E810B for <ietf@ietf.org>; Thu, 28 Jul 2011 14:24:19 -0700 (PDT)
Subject: RE: IPv6 traffic distribution
Date: Thu, 28 Jul 2011 14:24:18 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF636@newserver.arneill-py.local>
Content-class: urn:content-classes:message
In-Reply-To: <CAKD1Yr35ZFYPRknpFUaNK5BK=kGHM2VRKKi29A8FiAVPbLUdnw@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-MimeOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: IPv6 traffic distribution
Thread-Index: AcxNaqbnx3UkTn2ERni/V97669pIgAAAPYeA
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <m1QlzXt-0001gSC@stereo.hq.phicoh.net> <2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com> <392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local> <10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com> <CAKD1Yr3gv=+HfEZMsU0enNh8OQbemQh6iRzpGHsnmr7OJrTcFg@mail.gmail.com> <392CB277BC2EAE4FB83C1206954BA6CEF635@newserver.arneill-py.local> <CAKD1Yr35ZFYPRknpFUaNK5BK=kGHM2VRKKi29A8FiAVPbLUdnw@mail.gmail.com>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Lorenzo Colitti" <lorenzo@google.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, 28 Jul 2011 21:24:22 -0000

Bad question, I apologize for the imprecision. Please allow me to
rephrase.

>> Michel Py wrote:
>> Clarification: in your stats, is AS12322's traffic
>> classified as native or as 6to4/teredo?

> Lorenzo Colitti wrote:
> As the webpage says: "The Total IPv6 graph shows IPv6
> users with any type of connectivity, while the Native
> IPv6 graph excludes users using 6to4 or Teredo".

How is 6rd traffic classified? as native or as 6to4/teredo?
I expect that the bulk of traffic from AS12322 is 6rd.

Michel.


From thierry.ernst@inria.fr  Thu Jul 28 15:22:30 2011
Return-Path: <thierry.ernst@inria.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 48E1F5E802F for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 15:22:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.181
X-Spam-Level: 
X-Spam-Status: No, score=-8.181 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P4upZdndVXBu for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 15:22:23 -0700 (PDT)
Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by ietfa.amsl.com (Postfix) with ESMTP id 9F10D5E8029 for <ietf@ietf.org>; Thu, 28 Jul 2011 15:22:18 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.67,284,1309730400";  d="vcf'?scan'208,217";a="114371369"
Received: from 203.125.10.93.rev.sfr.net (HELO [192.168.1.3]) ([93.10.125.203]) by mail1-relais-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-CAMELLIA256-SHA; 29 Jul 2011 00:22:16 +0200
Message-ID: <4E31E118.3020605@inria.fr>
Date: Fri, 29 Jul 2011 00:22:16 +0200
From: Thierry Ernst <thierry.ernst@inria.fr>
Organization: INRIA
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IPv6 traffic distribution
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net><4E2DE4EC.1030109@gmail.com>	<4E2E2FBA.1030304@gmail.com><13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net><4E2EDF23.3060804@gmail.com>	<4E2F4491.30102@gmail.com><20110727023833.5C72D1232958@drugs.dv.isc.org><m1QlzXt-0001gSC@stereo.hq.phicoh.net>	<2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com>, <392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local> <CD5674C3CD99574EBA7432465FC13C1B222B1F57CE@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F57CE@DC-US1MBEX4.global.avaya.com>
Content-Type: multipart/mixed; boundary="------------050205080605050709090809"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 22:22:31 -0000

This is a multi-part message in MIME format.
--------------050205080605050709090809
Content-Type: multipart/alternative;
 boundary="------------020706090000090200010502"


--------------020706090000090200010502
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit


As a member of the G6 (http://g6.asso.fr), I'm very pleased to read this 
message and all the credits given to G6.

Without minimizing the role of the G6 association and its indivual 
members who have individually spread and participated to the deployment 
of IPv6 in their own organization (I would give credits to Renater and 
AFNIC and many others including well-known IETF participants in 
particular Francis Dupont for the first IPv6 implementation and Rémi 
Després for the first large scale deployment of IPv6 (6RD@Free), I would 
just like to mention how much we are indebted to the samurais of the 
WIDE community in Japan for having demonstrated *how to master IPv6 by 
practice.* Without this effort from Japan (KAME, USAGI, ...), IPv6 
wouldn't be where it stands today.

Regards,
Thierry Ernst.


On 28/07/11 16:20, Worley, Dale R (Dale) wrote:
>> From: Michel Py [michel@arneill-py.sacramento.ca.us]
>>
>> http://tinyurl.com/5u3eorn
>> "France is responsible for more than half of current IPv6 traffic
>> worldwide"; I can positively confirm that Free (AS12322) that
>> contributes to most of the French IPv6 native hits is delivering
>> "native" IPv6 to their eyeballs using 6rd and that they are indeed the
>> 800-pound gorilla of French IPv6 traffic, no contest.
> Also:
>
>      One reason that may explain France’s early adoption of IPv6 is
>      that France has formed a multitude of valuable IPv6-based
>      associations on the past decade. This activity has greatly
>      contributed to the acquisition and dissemination of IPv6
>      knowledge. These organizations consist of the G6, whose primary
>      task is IPv6 experimentation and information exchange. The G6 was
>      founded in 1995 by researchers in academia and industry. G6’s
>      overall goal is the gradual building of a new infrastructure
>      required for the Internet to survive. The G6, like Cisco, is
>      focused on an effective and seamless transition IPv4 to IPv6. It
>      is the primary catalyst for advances in IPv6 networking in France.
>
> In other words, very early (15 years ago), the French Internet
> community formed an organization to move IPv6 forward through
> coordination and persuasion rather than by preaching from the outside.
>
> In the larger Internet, I've seen a remarkable absence of that sort
> of coordination.
>
> Dale
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


--------------020706090000090200010502
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    <br>
    As a member of the G6 (<a class="moz-txt-link-freetext" href="http://g6.asso.fr">http://g6.asso.fr</a>), I'm very pleased to read
    this message and all the credits given to G6. <br>
    <br>
    Without minimizing the role of the G6 association and its indivual
    members who have individually spread and participated to the
    deployment of IPv6 in their own organization (I would give credits
    to Renater and AFNIC and many others including well-known IETF
    participants in particular Francis Dupont for the first IPv6
    implementation and Rémi Després for the first large scale deployment
    of IPv6 (6RD@Free), I would just like to mention how much we are
    indebted to the samurais of the WIDE community in Japan for having
    demonstrated <b>how to master IPv6 by practice.</b> Without this
    effort from Japan (KAME, USAGI, ...), IPv6 wouldn't be where it
    stands today. <br>
    <br>
    Regards,<br>
    Thierry Ernst.<br>
    <br>
    <br>
    On 28/07/11 16:20, Worley, Dale R (Dale) wrote:
    <blockquote
cite="mid:CD5674C3CD99574EBA7432465FC13C1B222B1F57CE@DC-US1MBEX4.global.avaya.com"
      type="cite">
      <blockquote type="cite">
        <pre wrap="">From: Michel Py [<a class="moz-txt-link-abbreviated" href="mailto:michel@arneill-py.sacramento.ca.us">michel@arneill-py.sacramento.ca.us</a>]

<a class="moz-txt-link-freetext" href="http://tinyurl.com/5u3eorn">http://tinyurl.com/5u3eorn</a>
"France is responsible for more than half of current IPv6 traffic
worldwide"; I can positively confirm that Free (AS12322) that
contributes to most of the French IPv6 native hits is delivering
"native" IPv6 to their eyeballs using 6rd and that they are indeed the
800-pound gorilla of French IPv6 traffic, no contest.
</pre>
      </blockquote>
      <pre wrap="">
Also:

    One reason that may explain France’s early adoption of IPv6 is
    that France has formed a multitude of valuable IPv6-based
    associations on the past decade. This activity has greatly
    contributed to the acquisition and dissemination of IPv6
    knowledge. These organizations consist of the G6, whose primary
    task is IPv6 experimentation and information exchange. The G6 was
    founded in 1995 by researchers in academia and industry. G6’s
    overall goal is the gradual building of a new infrastructure
    required for the Internet to survive. The G6, like Cisco, is
    focused on an effective and seamless transition IPv4 to IPv6. It
    is the primary catalyst for advances in IPv6 networking in France.

In other words, very early (15 years ago), the French Internet
community formed an organization to move IPv6 forward through
coordination and persuasion rather than by preaching from the outside.

In the larger Internet, I've seen a remarkable absence of that sort
of coordination.

Dale
_______________________________________________
Ietf mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ietf@ietf.org">Ietf@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ietf">https://www.ietf.org/mailman/listinfo/ietf</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------020706090000090200010502--

--------------050205080605050709090809
Content-Type: text/x-vcard; charset=utf-8;
 name="thierry_ernst.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="thierry_ernst.vcf"

begin:vcard
fn:Thierry  Ernst
n:Ernst;Thierry 
org:INRIA - Project Team IMARA - LaRA JRU
tel;work:+33 1 3963 59 30
tel;fax:+33 1 39 63 54 91
tel;cell:+33 6 76 56 25 96
url:http://www.lara.prd.fr
version:2.1
end:vcard


--------------050205080605050709090809--

From mohta@necom830.hpcl.titech.ac.jp  Thu Jul 28 15:25:46 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 0A38E21F85A1 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 15:25:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.078
X-Spam-Level: 
X-Spam-Status: No, score=-0.078 tagged_above=-999 required=5 tests=[AWL=0.012,  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 ObXK90wUTouw for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 15:25:45 -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 DC91521F8588 for <ietf@ietf.org>; Thu, 28 Jul 2011 15:25:44 -0700 (PDT)
Received: (qmail 51062 invoked from network); 28 Jul 2011 22:45:58 -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; 28 Jul 2011 22:45:58 -0000
Message-ID: <4E31E158.1090905@necom830.hpcl.titech.ac.jp>
Date: Fri, 29 Jul 2011 07:23:20 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Philip Homburg <pch-ietf@u-1.phicoh.com>
Subject: Re: "6to4 damages the Internet" (was Re: draft-ietf-v6ops-6to4-to-historic (yet again))
References: <m1QmPxo-0001iIC@stereo.hq.phicoh.net>
In-Reply-To: <m1QmPxo-0001iIC@stereo.hq.phicoh.net>
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, 28 Jul 2011 22:25:46 -0000

Philip Homburg wrote:

>> which means an end system should have a full routing table, IGP
>> metrics in which tell the end system what is the best address of
>> its multihomed peer. Full routing table should and can, of course,
>> be small.
> 
> Even in the unlikely case that it would be feasible to give every host a
> complete copy of the DFZ routing table...

With RFC2374, DFZ of IPv6 has at most 8192 entries.

> That still would leave a lot of issues open...
> 1) End-to-end latency. Maybe some future generation BGP provides that, but
>     that doesn't help now.

Your requirement can be fair, only with a routing protocol
supporting latency based routing for *an* address with
*multiple* paths to its destination.

There is no point to have a latency based selection of
multiple paths to the destination, only if the destination
has multiple addresses.

> 2) For 6to4, the use of anycase. You probably need a link-state routing
>     protocol to allow a host to figure out which relays are going to be used on
>     a give path.

With anycast, you can use only a single relay. Instead, you can
compare metrics between IPv4 and IPv6 addresses of a host.

> 3) Filters in firewalls. I'd love to see a routing protocol that reports the
>     settings of all firewalls in the world :-)

Are you saying filtering of firewalls can be disabled by proper
address selection?

> 4) Other performance metrics, like jitter, packets loss, etc.

See 1).

> Maybe you can do some experiments and report on how well your draft works for
> deciding when to prefer a 6to4 address over IPv4.

A problem is that there is no point to stick to IPv6 broken
so much.

But, it's not my problem.

						Masataka Ohta


From brian.e.carpenter@gmail.com  Thu Jul 28 16:07:45 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 A468D11E8098 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 16:07:45 -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 5hOsND9A4ITL for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 16:07:45 -0700 (PDT)
Received: from mail-pz0-f53.google.com (mail-pz0-f53.google.com [209.85.210.53]) by ietfa.amsl.com (Postfix) with ESMTP id 0CC1F11E8082 for <ietf@ietf.org>; Thu, 28 Jul 2011 16:07:44 -0700 (PDT)
Received: by pzk6 with SMTP id 6so4951015pzk.26 for <ietf@ietf.org>; Thu, 28 Jul 2011 16:07:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=tdgiOBA/uptSE9gyqPWBtLmzsCU1qBKpYOCl+i1HnOQ=; b=SlkoS/tjCRJuJfshQaKfDbDjX+SrZYfzeN1IyxhtQSaFUzu3wpEnRV1uGYhQ6AK0wm Qxj+0aC1GVZ+xivec1VSDwyqEbaF/S+xNf/YIcbGt5DQsLsd0XsMRHtWy+aa0fdvnvER GvLA5KdtMGL8eBc02UsMBGAR0H5ANM/wt28OU=
Received: by 10.68.10.69 with SMTP id g5mr1126011pbb.444.1311894464662; Thu, 28 Jul 2011 16:07:44 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id z6sm1453324pbc.30.2011.07.28.16.07.41 (version=SSLv3 cipher=OTHER); Thu, 28 Jul 2011 16:07:43 -0700 (PDT)
Message-ID: <4E31EBBA.8010302@gmail.com>
Date: Fri, 29 Jul 2011 11:07:38 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: draft-housley-two-maturity-levels
References: <20110728121904.2D22AD7A76F@newdev.eecs.harvard.edu>	<12B69DB8-AFDD-4C40-BC9A-0A8158D9F7C0@nostrum.com>	<0D43A851-C57B-484F-ADDD-BBD7A412689C@standardstrack.com>	<4E316D00.6090900@stpeter.im> <839F8D5B-B64D-4842-8AC2-72C637942BA8@network-heretics.com>
In-Reply-To: <839F8D5B-B64D-4842-8AC2-72C637942BA8@network-heretics.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF <ietf@ietf.org>, Bradner Scott <sob@harvard.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 23:07:45 -0000

Keith,

On 2011-07-29 02:20, Keith Moore wrote:
> On Jul 28, 2011, at 10:06 AM, Peter Saint-Andre wrote:
> 
>> On 7/28/11 10:03 AM, Eric Burger wrote:
>>> And the real question is, are we moving forward? I think that we are
>>> not moving as far as we originally wanted. However, I offer we are
>>> moving a baby step forward, and as such is worthwhile doing.
>> We are more closely aligning our documentation with our organizational
>> running code. All other things being equal, that's a good thing.
> 
> Hmm.  I've long believed that :
> 
> - trying to document existing practice
> - trying to document desirable practice
> 
> are both worthwhile endeavors, as long as you don't try to do both at the same time.  When you try to do both at the same time, there is a conflict.
> 
> If someone wants to write a document that says we generally follow RFC 2026, except that:

Been there, done that, it sank like a stone.

Let's just make this baby step and stop worrying about it.

   Brian

> - drafts hardly ever advance to Draft Standard and even more rarely to Full Standard, unless there is significant use of the protocol and there are bugs that need to be fixed (in which case the ability to advance can sometimes serve as an incentive of sorts)
> - we have never been serious about periodic review of standards and we don't have enough time/energy to do that
> - we've never really nailed down what Historic meant, and when it was appropriate to use it
> 
> etc.
> 
> that would be a fine thing.
> 
> And real changes to the process, say to bring in formal cross review earlier, to clarify the nature of community consensus and the need for it, etc. might also be a fine thing.  Unfortunately, such discussions are always contentious and difficult, because they affect the whole community, but they also attract a lot of interests from individuals with particularly unique axes to grind.  So we keep trying to fix the substantive problems with incremental changes.  I forget who it was who said yesterday that we can't really do that, but I certainly agree with him.
> 
> Meanwhile, it's not clear to me that simply changing from one document that we don't strictly follow, to another document that we won't follow much better, is helpful.  And I don't think IETF's problems with standards quality or process can be addressed merely by changes to the number of maturity levels.  That strikes me as a bit like rearranging deck chairs...it might make people feel better but is of little consequence.
> 
> In other words, I'm not convinced that this change will do much harm, but I'm also not convinced that it will help much.  And yet we keep flogging this idea...
> 
> Keith
> 
> 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 

From eburger-l@standardstrack.com  Thu Jul 28 16:10:24 2011
Return-Path: <eburger-l@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 9FCC121F8AAC for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 16:10:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level: 
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[AWL=0.057,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Voj7TRSoF38p for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 16:10:23 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id B970821F8AB8 for <ietf@ietf.org>; Thu, 28 Jul 2011 16:10:23 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com;  h=Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=KvXtJ7DbS+/YjuZB4s+NUemxCmQTKWJiCtZEOfJmfFSfuKDh4zkjYuwWt5vchn2C+KAmVOkh9j+W95FRHhdx54otV+XfeGQfPTvppqrAlhdNbR7Kpiolkyp5koMxobGP;
Received: from dhcp-63da.meeting.ietf.org ([130.129.99.218]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger-l@standardstrack.com>) id 1QmZiX-0000gt-Ph for ietf@ietf.org; Thu, 28 Jul 2011 16:10:13 -0700
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: On attending BoFs
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <4E31C87E.4090606@stpeter.im>
Date: Thu, 28 Jul 2011 19:10:11 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <BAACE255-C1BA-4511-A367-6A4727ADEAF4@standardstrack.com>
References: <F5833273385BB34F99288B3648C4F06F13512DF4A7@EXCH-C2.corp.cloudmark.com> <4E31C87E.4090606@stpeter.im>
To: IETF <ietf@ietf.org>
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, 28 Jul 2011 23:10:24 -0000

+$1.00

Have we ever had a BOF that looked under-attended? Not me: always =
standing room only!

Big rooms =3D good BOF.

On Jul 28, 2011, at 4:37 PM, Peter Saint-Andre wrote:

> On 7/28/11 4:06 PM, Murray S. Kucherawy wrote:
>=20
>> When we ask for a BoF room, we need to give an indication of =
estimated
>> attendance.  Sometimes it=92s hard to make a good guess and so we
>> underestimate, intending to keep larger rooms available for groups =
that
>> need them.
>=20
> I think the BoF chairs and responsible ADs need to request larger =
rooms
> for BoFs. After the REPUTE BOF, I talked with the Secretariat
> (specifically Wanda Lo, who does an amazing job with the schedule!)
> about poking the chairs and ADs when they request BoF rooms to make =
sure
> that we don't assign small rooms to BoFs, at least without careful
> consideration.
>=20
> Peter
>=20
> --=20
> Peter Saint-Andre
> https://stpeter.im/
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From mnot@mnot.net  Thu Jul 28 16:11:48 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 77C9621F8B05 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 16:11:48 -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=[AWL=-4.000, BAYES_00=-2.599, NO_RDNS_DOTCOM_HELO=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 DIrnSFaOdBzY for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 16:11:48 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id E55E021F8B01 for <ietf@ietf.org>; Thu, 28 Jul 2011 16:11:43 -0700 (PDT)
Received: from unknown-10-101-30-x.yahoo.com (unknown [209.131.62.115]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 07BB850A64; Thu, 28 Jul 2011 19:11:36 -0400 (EDT)
Subject: Re: On attending BoFs
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=windows-1252
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <BAACE255-C1BA-4511-A367-6A4727ADEAF4@standardstrack.com>
Date: Thu, 28 Jul 2011 16:11:34 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <88403E2A-EB94-44AF-B9FC-9B98E3EB5A18@mnot.net>
References: <F5833273385BB34F99288B3648C4F06F13512DF4A7@EXCH-C2.corp.cloudmark.com> <4E31C87E.4090606@stpeter.im> <BAACE255-C1BA-4511-A367-6A4727ADEAF4@standardstrack.com>
To: Eric Burger <eburger-l@standardstrack.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 23:11:48 -0000

... and if the room isn't full, that's interesting information too.


On 28/07/2011, at 4:10 PM, Eric Burger wrote:

> +$1.00
>=20
> Have we ever had a BOF that looked under-attended? Not me: always =
standing room only!
>=20
> Big rooms =3D good BOF.
>=20
> On Jul 28, 2011, at 4:37 PM, Peter Saint-Andre wrote:
>=20
>> On 7/28/11 4:06 PM, Murray S. Kucherawy wrote:
>>=20
>>> When we ask for a BoF room, we need to give an indication of =
estimated
>>> attendance.  Sometimes it=92s hard to make a good guess and so we
>>> underestimate, intending to keep larger rooms available for groups =
that
>>> need them.
>>=20
>> I think the BoF chairs and responsible ADs need to request larger =
rooms
>> for BoFs. After the REPUTE BOF, I talked with the Secretariat
>> (specifically Wanda Lo, who does an amazing job with the schedule!)
>> about poking the chairs and ADs when they request BoF rooms to make =
sure
>> that we don't assign small rooms to BoFs, at least without careful
>> consideration.
>>=20
>> Peter
>>=20
>> --=20
>> Peter Saint-Andre
>> https://stpeter.im/
>>=20
>>=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

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




From HKaplan@acmepacket.com  Thu Jul 28 16:18:05 2011
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AA3421F8B76 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 16:18:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.491
X-Spam-Level: 
X-Spam-Status: No, score=-2.491 tagged_above=-999 required=5 tests=[AWL=0.108,  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 Iv3joT+A1bul for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 16:18:04 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 8A7DE21F8B75 for <ietf@ietf.org>; Thu, 28 Jul 2011 16:18:04 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 28 Jul 2011 19:17:20 -0400
Received: from mailbox1.acmepacket.com ([216.41.24.12]) by mail ([127.0.0.1]) with mapi; Thu, 28 Jul 2011 19:17:20 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Alexa Morris <amorris@amsl.com>
Date: Thu, 28 Jul 2011 19:17:19 -0400
Subject: Re: Reminder: Remote Participation Support for Admin Plenary Tonight
Thread-Topic: Reminder: Remote Participation Support for Admin Plenary Tonight
Thread-Index: AcxNfH+ghda9WQjsSrqo369OYhrdaQ==
Message-ID: <B84E0837-ED64-4C64-927C-2F6948405B20@acmepacket.com>
References: <3D658D0E-4958-4AEF-9BD2-447A887EECF1@amsl.com> <4E30865A.2090802@gmail.com> <6.2.5.6.2.20110727152126.06e32500@resistor.net> <0E66E2DF-6381-4014-B1FA-EC33704FA8FF@amsl.com> <4E30B31C.6070701@gmail.com>
In-Reply-To: <4E30B31C.6070701@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-Brightmail-Tracker: AAAAAgAAAUAAAAFQ
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, 28 Jul 2011 23:18:05 -0000

I don't know about the real-time remote participation aspects because I'm a=
t the IETF in QC, but I did use the meetecho recorded sessions for a couple=
 WGs I didn't attend this week and I have to say it was great - better than=
 the mp3 recordings of previous IETFs.  While the mp3 had better audio qual=
ity, the meetecho HTML5 recordings had the video, audio, presentation slide=
s and jabber all synchronized and I could skip forward forward/back for all=
 of those which was sweet.

Then when I found out they were doing this on their own dime without IETF p=
aying for it, I was shocked.

Kudos to them.

-hadriel


On Jul 27, 2011, at 8:53 PM, Brian E Carpenter wrote:

> Thanks Alexa!
>=20
> And certainly the Meetecho service has its value - although those of us
> on the end of a very long, thin glass fibre in the South Pacific may
> not be able to get the full benefit.
>=20
> Regards
>   Brian Carpenter
>=20


From marshall.eubanks@gmail.com  Thu Jul 28 16:18:19 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 2715D21F8B77 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 16:18:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.44
X-Spam-Level: 
X-Spam-Status: No, score=-103.44 tagged_above=-999 required=5 tests=[AWL=0.158, 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 5kc4n4Z0A6Tc for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 16:18:18 -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 127AB21F8B76 for <ietf@ietf.org>; Thu, 28 Jul 2011 16:18:18 -0700 (PDT)
Received: by yxp4 with SMTP id 4so2429803yxp.31 for <ietf@ietf.org>; Thu, 28 Jul 2011 16:17:34 -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=h0pcTDyI9B2QMrlsSjjoPXWb50PETg51vTEMw+aScYk=; b=Gr5qGZuac4kqrjePHCrpWVdx5gycsihyyFQCjvk89zvNnfGSV9geDEA8CEBIVyiowH oUQvOVl/CVse1bhlFOOrqXmbxUamWRYTNI51G7vz6ch3GjLI3MGuyBY2yNLHWXCjARMM dpH/bb3DC4P6yGyhdhkYHZR9fia6LrpIza1II=
MIME-Version: 1.0
Received: by 10.150.48.28 with SMTP id v28mr116724ybv.38.1311895054665; Thu, 28 Jul 2011 16:17:34 -0700 (PDT)
Received: by 10.151.12.20 with HTTP; Thu, 28 Jul 2011 16:17:34 -0700 (PDT)
In-Reply-To: <BAACE255-C1BA-4511-A367-6A4727ADEAF4@standardstrack.com>
References: <F5833273385BB34F99288B3648C4F06F13512DF4A7@EXCH-C2.corp.cloudmark.com> <4E31C87E.4090606@stpeter.im> <BAACE255-C1BA-4511-A367-6A4727ADEAF4@standardstrack.com>
Date: Thu, 28 Jul 2011 19:17:34 -0400
Message-ID: <CAJNg7VKSwkyoUdSMnHiVuZLor0uvVFsYYe2_CNG9nDqrEWf7mA@mail.gmail.com>
Subject: Re: On attending BoFs
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Eric Burger <eburger-l@standardstrack.com>
Content-Type: multipart/alternative; boundary=000e0cd7055eb747ee04a9295e53
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 23:18:19 -0000

--000e0cd7055eb747ee04a9295e53
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Thu, Jul 28, 2011 at 7:10 PM, Eric Burger
<eburger-l@standardstrack.com>wrote:

> +$1.00
>
> Have we ever had a BOF that looked under-attended? Not me: always standin=
g
> room only!
>
>
I would also argue that you want "BOF tourists." They might turn into
participants. They also might point out
things like overlap with previous work in the IETF or some other SDO.

Regards
Marshall


> Big rooms =3D good BOF.
>
> On Jul 28, 2011, at 4:37 PM, Peter Saint-Andre wrote:
>
> > On 7/28/11 4:06 PM, Murray S. Kucherawy wrote:
> >
> >> When we ask for a BoF room, we need to give an indication of estimated
> >> attendance.  Sometimes it=92s hard to make a good guess and so we
> >> underestimate, intending to keep larger rooms available for groups tha=
t
> >> need them.
> >
> > I think the BoF chairs and responsible ADs need to request larger rooms
> > for BoFs. After the REPUTE BOF, I talked with the Secretariat
> > (specifically Wanda Lo, who does an amazing job with the schedule!)
> > about poking the chairs and ADs when they request BoF rooms to make sur=
e
> > that we don't assign small rooms to BoFs, at least without careful
> > consideration.
> >
> > Peter
> >
> > --
> > Peter Saint-Andre
> > https://stpeter.im/
> >
> >
> > _______________________________________________
> > 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
>

--000e0cd7055eb747ee04a9295e53
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Thu, Jul 28, 2011 at 7:10 PM, Eric Bu=
rger <span dir=3D"ltr">&lt;<a href=3D"mailto:eburger-l@standardstrack.com">=
eburger-l@standardstrack.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;">
+$1.00<br>
<br>
Have we ever had a BOF that looked under-attended? Not me: always standing =
room only!<br>
<br></blockquote><div><br></div><div>I would also argue that you want &quot=
;BOF tourists.&quot; They might turn into participants. They also might poi=
nt out</div><div>things like overlap with previous work in the IETF or some=
 other SDO.</div>
<div><br></div><div>Regards</div><div>Marshall</div><div>=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex;">
Big rooms =3D good BOF.<br>
<div><div></div><div class=3D"h5"><br>
On Jul 28, 2011, at 4:37 PM, Peter Saint-Andre wrote:<br>
<br>
&gt; On 7/28/11 4:06 PM, Murray S. Kucherawy wrote:<br>
&gt;<br>
&gt;&gt; When we ask for a BoF room, we need to give an indication of estim=
ated<br>
&gt;&gt; attendance. =A0Sometimes it=92s hard to make a good guess and so w=
e<br>
&gt;&gt; underestimate, intending to keep larger rooms available for groups=
 that<br>
&gt;&gt; need them.<br>
&gt;<br>
&gt; I think the BoF chairs and responsible ADs need to request larger room=
s<br>
&gt; for BoFs. After the REPUTE BOF, I talked with the Secretariat<br>
&gt; (specifically Wanda Lo, who does an amazing job with the schedule!)<br=
>
&gt; about poking the chairs and ADs when they request BoF rooms to make su=
re<br>
&gt; that we don&#39;t assign small rooms to BoFs, at least without careful=
<br>
&gt; consideration.<br>
&gt;<br>
&gt; Peter<br>
&gt;<br>
&gt; --<br>
&gt; Peter Saint-Andre<br>
&gt; <a href=3D"https://stpeter.im/" target=3D"_blank">https://stpeter.im/<=
/a><br>
&gt;<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>
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>

--000e0cd7055eb747ee04a9295e53--

From brian.e.carpenter@gmail.com  Thu Jul 28 16:22:54 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 56EE411E80A1 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 16:22:54 -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 hnUFvfqpN2Hy for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 16:22:53 -0700 (PDT)
Received: from mail-pz0-f53.google.com (mail-pz0-f53.google.com [209.85.210.53]) by ietfa.amsl.com (Postfix) with ESMTP id BBABB21F85A0 for <ietf@ietf.org>; Thu, 28 Jul 2011 16:22:53 -0700 (PDT)
Received: by pzk6 with SMTP id 6so4967724pzk.26 for <ietf@ietf.org>; Thu, 28 Jul 2011 16:22:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=iSM6KppQM4fraFIByAODhrFiPyCcAr0J9bN1TQYszbY=; b=Ne0Xmgf3dLoYdMDgpAdxFSuPHMaH472HH0VumyQPyBipHrq5EYK3Yq0LRJYjXAmnB2 EBXxkiD9VsPeXWuUJ7gfiNya1ICarnmhhPwbr4qKbmSfmHBH1EjVPRVA76owRYo7rmwO p2JxwhyNh1JEwEmDT9C3dp+LHoIfncQSSuf+8=
Received: by 10.68.8.161 with SMTP id s1mr1102002pba.301.1311895372938; Thu, 28 Jul 2011 16:22:52 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id m7sm1469086pbk.6.2011.07.28.16.22.50 (version=SSLv3 cipher=OTHER); Thu, 28 Jul 2011 16:22:52 -0700 (PDT)
Message-ID: <4E31EF47.5070403@gmail.com>
Date: Fri, 29 Jul 2011 11:22:47 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Why the IESG needs to review everything...
References: <4E308D64.3030804@gmail.com> <4E30927D.50808@dcrocker.net> <4E30B250.3030807@gmail.com> <4E3161AB.9010007@dcrocker.net>
In-Reply-To: <4E3161AB.9010007@dcrocker.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 23:22:54 -0000

Dave, we are shouting past each other so I will not repeat myself
on all points. However,

...
>> Of course, there can be cases where that is not so - in fact, that's
>> the main reason that the IESG defined the DISCUSS criteria a few years
>> ago.
> 
> Have you seen a pattern of having a Discuss cite the criterion that
> justifies it?  I haven't.  It might be interesting to attempt an audit
> of Discusses, against the criteria...

It might, and at the time when the IESG had a large backlog of unresolved
DISCUSSes and the current criteria were being developed (I'm talking
about 2005/2006), the IESG did indeed end up looking at all the old
DISCUSSes against the criteria, and held dedicated conference calls
to talk through many of those DISCUSSes and in many cases persuade the AD
concerned to drop them, or rewrite them in an actionable format. In my
recollection, Allison Mankin was the leader of the charge on this.

But these are all judgment calls, so I don't think there can be an
objective audit. There could be an audit of how many DISCUSSes take
more than N months to clear, or something like that. There were tools
around for that some years ago, but I don't know if they exist for the
modern version of the tracker.

>>> It well might be true that omitting the AD reviews would increase the
>>> number. By how much?  To what effect?
>>
>> Hard to tell. But it would amount to giving the IESG secretary a large
>> rubber stamp *unless* the final responsibility was explicitly moved
>> elsewhere.
> 
> Herein lies the real problem:  As with many process and structure
> discussions in the IETF, folk often see only a simplistic, binary choice
> between whatever they prefer, versus something akin to chaos.
> 
> The world is more nuanced than that, and the choices more rich.
> 
> Here is a small counter-example to your sole alternatives of status quo
> or rubber stamp:
> 
>      Imagine a process which requires a range of reviews and requires
> ADs to take note of the reviews and the community support-vs-objection.
> 
>      Imagine that the job of the ADs is to assess these and to block
> proposals that have had major, unresolved problems uncovered or that
> lack support, and to approve ones that have support and lack known,
> major deficiencies as documented by the reviews.

The only difference between that and what I see happening today is that
the ADs actually verify the reviews by looking at the drafts themselves.
And why do they do that? Because they aren't going to take the
responsibility for approving a document that they haven't read. Nobody
would, I hope.

    Brian

From brian.e.carpenter@gmail.com  Thu Jul 28 16:24:56 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 BEFEC11E8143 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 16:24:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0se8ezxg0lEF for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 16:24:56 -0700 (PDT)
Received: from mail-pz0-f53.google.com (mail-pz0-f53.google.com [209.85.210.53]) by ietfa.amsl.com (Postfix) with ESMTP id 154C011E813D for <ietf@ietf.org>; Thu, 28 Jul 2011 16:24:56 -0700 (PDT)
Received: by pzk6 with SMTP id 6so4970042pzk.26 for <ietf@ietf.org>; Thu, 28 Jul 2011 16:24:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=Cq3uwIfaQl9mx8cQ9N1KCDn6cXFNrEpgMJEEs4xcXNg=; b=PRNaYLjQEH/QAjKVzKGYfoBHH190su7Z5zIRi7z9H6amFhA6h/tdX16J1nKL5u0BAU Sy1dfjSnS0rGNZZbeeMH2K3mYiQD/3uTngzl+eeuMzmjislNtzcOfpLbAIkHuXcma1IC fynukqo+/F79zY62JN/qwcdBcJ1nCTWmfRP+A=
Received: by 10.68.6.101 with SMTP id z5mr1099947pbz.24.1311895495804; Thu, 28 Jul 2011 16:24:55 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id d1sm1462837pbj.56.2011.07.28.16.24.53 (version=SSLv3 cipher=OTHER); Thu, 28 Jul 2011 16:24:55 -0700 (PDT)
Message-ID: <4E31EFC1.8070607@gmail.com>
Date: Fri, 29 Jul 2011 11:24:49 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Why the IESG needs to review everything...
References: <4E308D64.3030804@gmail.com>	<201107272313.p6RNDMX9017678@fs4113.wdf.sap.corp> <6.2.5.6.2.20110727233441.04c41030@resistor.net>
In-Reply-To: <6.2.5.6.2.20110727233441.04c41030@resistor.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 23:24:56 -0000

On 2011-07-28 18:45, SM wrote:
> Hi Martin,
> At 04:13 PM 7/27/2011, Martin Rex wrote:
>> According to rfc2026:
>>
>>    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.  [...]
> 
> The above is incorrect.

Er, no. By definition, it's correct until we update RFC 2026.

    Brian

From brian.e.carpenter@gmail.com  Thu Jul 28 16:42: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 F10895E8007 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 16:42:01 -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 BGOihE6CA3rS for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 16:42:01 -0700 (PDT)
Received: from mail-pz0-f53.google.com (mail-pz0-f53.google.com [209.85.210.53]) by ietfa.amsl.com (Postfix) with ESMTP id 7DF4D5E8004 for <ietf@ietf.org>; Thu, 28 Jul 2011 16:42:01 -0700 (PDT)
Received: by pzk6 with SMTP id 6so4989497pzk.26 for <ietf@ietf.org>; Thu, 28 Jul 2011 16:42:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=we02gVn9Iob1oeTsKgTl1PvdrL5UTEKS2cv41KpVA2M=; b=k8pUipO6pS0KarphftIw5vK6Gi1iRiWDSQhDCRKWynu7QmSjMf1G8+bnjhOelmFXb/ TApJSEsqrHBz86Nc9kcJSgP8Wj1MKh81V9AGboJBdodN34PGArjbpWXs5mW1GT4deG/5 ukWlMmbeP7XxLxcNeHZw+XvBrvjNV4xnNhOLs=
Received: by 10.68.8.72 with SMTP id p8mr1218941pba.0.1311896521184; Thu, 28 Jul 2011 16:42:01 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id m7sm1483889pbk.6.2011.07.28.16.41.58 (version=SSLv3 cipher=OTHER); Thu, 28 Jul 2011 16:42:00 -0700 (PDT)
Message-ID: <4E31F3C2.4000000@gmail.com>
Date: Fri, 29 Jul 2011 11:41:54 +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: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: IPv6 traffic distribution
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>	<4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com>	<20110727023833.5C72D1232958@drugs.dv.isc.org>	<m1QlzXt-0001gSC@stereo.hq.phicoh.net>	<2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com>	<392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local>	<10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com>	<CAKD1Yr3gv=+HfEZMsU0enNh8OQbemQh6iRzpGHsnmr7OJrTcFg@mail.gmail.com>	<392CB277BC2EAE4FB83C1206954BA6CEF635@newserver.arneill-py.local>	<3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk> <EMEW3|fa0511c175232cff9b9cb8310f081538n6RMCh03tjc|ecs.soton.ac.uk|3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|fa0511c175232cff9b9cb8310f081538n6RMCh03tjc|ecs.soton.ac.uk|3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk>
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: Thu, 28 Jul 2011 23:42:02 -0000

Looking at a trace that I got from Geoff Huston a month or two ago,
there are 25486 IPv6 TCP sessions of which 10748 have a 6to4 source
address.

That's surprisingly high, showing that the answer depends greatly on
the point of observation, and explains why operators really need
to try to run a decent 6to4 relay service as long as so many
such clients are observed. Which is why disabling 6to4 in clients
has to be the priority; it's far too soon to decommission the
relays.

Regards
   Brian Carpenter

On 2011-07-29 09:12, Tim Chown wrote:
> On 28 Jul 2011, at 21:51, Michel Py wrote:
> 
>> Lorenzo,
>>
>>> Lorenzo Colitti wrote:
>>> http://www.google.com/intl/en/ipv6/statistics/
>> Thanks for the update.
>> Clarification: in your stats, is AS12322's traffic classified as native
>> or as 6to4/teredo?
> 
> 
> Hi,
> 
> I just ran a search through our Netflow logs of the most recent flows attempting to traverse our enterprise border and this showed:
> 
> 2002::/16 (6to4):
> Summary: total flows: 562468, total bytes: 6.2 G, total packets: 11.0 M 
> 
> 2001::/32 (Teredo):
> Summary: total flows: 1363887, total bytes: 4.9 G, total packets: 10.1 M
> 
> Other:
> Summary: total flows: 23681562, total bytes: 483.1 G, total packets: 546.9 M
> 
> Teredo appears skewed by one host's behaviour which I'll be looking into, otherwise it's about what I'd expect with around 1% by volume being 6to4.
> 
> Tim
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From sm@resistor.net  Thu Jul 28 17:11:39 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 3B64821F8AEC for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 17:11:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 3LR9cUN2xhp0 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 17:11:36 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id EE0A321F8AE6 for <ietf@ietf.org>; Thu, 28 Jul 2011 17:11:35 -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 p6T0BTNG006769;  Thu, 28 Jul 2011 17:11:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1311898290; bh=xu0/lFD2EILgjiU9zFzDmFpKNooT/ZYdu+FKr8ljpCE=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=vmJnibSL0GP0xdhHOm8VacHPqKA8KWP/H3nE5TKk9DgyQHDflTMqjXF7GRKl4RGHl Qp8Zp97DvmJUuJBXacVg0LUEuAObFypAygKf54RO/HSOGDgbwm3VI4lCMxKTpYrxEy fYeq3kxucpSwZ5GiQmCFJM4MhLhWwiTDrU9f6kyQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1311898290; bh=xu0/lFD2EILgjiU9zFzDmFpKNooT/ZYdu+FKr8ljpCE=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=cyUx6RzautYvaWSmgJFmmVAvsE9FKt8hC/BhJcPV2wlAzM+dA7C17w7OvS5fPK2EC e7MNSIF7kdLmnd85mPBUUn9hMHgX51Gva3REjdKPpPWTT9ehXK+JeGxzQiT9OB0kxM Jms8KpX2qFBRz2ALq3Cumu/MR5O/ysHhiJ+Grj7w=
Message-Id: <6.2.5.6.2.20110728163352.0a2bb920@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 28 Jul 2011 16:54:45 -0700
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Why the IESG needs to review everything...
In-Reply-To: <4E31EFC1.8070607@gmail.com>
References: <4E308D64.3030804@gmail.com> <201107272313.p6RNDMX9017678@fs4113.wdf.sap.corp> <6.2.5.6.2.20110727233441.04c41030@resistor.net> <4E31EFC1.8070607@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 00:11:39 -0000

Hi Brian,
At 04:24 PM 7/28/2011, Brian E Carpenter wrote:
>Er, no. By definition, it's correct until we update RFC 2026.

Quoting the Status of this memo section from RFC 6305, RFC 6308, RFC 
6319 and RFC 6331 which are Informational and from the IETF Stream:

   "This document is a product of the Internet Engineering Task Force
    (IETF).  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)."

Although it is, by definition, correct until RFC 2026 is updated, RFC 
5741 is currently being used for the boilerplate in RFCs.

Regards,
-sm 


From mrex@sap.com  Thu Jul 28 17:28:30 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 D00025E8004 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 17:28:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.93
X-Spam-Level: 
X-Spam-Status: No, score=-9.93 tagged_above=-999 required=5 tests=[AWL=0.319,  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 3JE8zQ5V-UxT for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 17:28:30 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 21F315E8001 for <ietf@ietf.org>; Thu, 28 Jul 2011 17:28:29 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id p6T0SQK9024294 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 29 Jul 2011 02:28:26 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201107290028.p6T0SQgQ013589@fs4113.wdf.sap.corp>
Subject: Re: "6to4 damages the Internet" (was Re:
To: mohta@necom830.hpcl.titech.ac.jp (Masataka Ohta)
Date: Fri, 29 Jul 2011 02:28:26 +0200 (MEST)
In-Reply-To: <4E3118E1.5090107@necom830.hpcl.titech.ac.jp> from "Masataka Ohta" at Jul 28, 11 05:08:01 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, 29 Jul 2011 00:28:30 -0000

Masataka Ohta wrote:
> 
> > It would be nice if 5 or 10 years ago there would have been a good
> > standard to do address selection.
> 
> 11 years ago in draft-ohta-e2e-multihoming-00.txt, I wrote:
> 
>    End systems (hosts) are end systems. To make the end to end principle
>    effectively work, the end systems must have all the available
>    knowledge to make decisions by the end systems themselves.
> 
>    With regard to multihoming, when an end system want to communicate
>    with a multihomed end system, the end system must be able to select
>    most appropriate (based on the local information) destination address
>    of the multihomed end system.


The primary reason why the IPv4 -> IPv6 transition is so painful
is that it requires everyone one and everything to become multi-homed
and every software to perform multi-connect, even though most
devices actually just have a single interface.

It would be so much easier if hosts on the public internet could
use one single IPv6 address that contains both, the IPv6 network prefix
and the IPv4 host address, and then let the network figure out whether
the connect goes through as IPv4 or IPv6 (for IPv6 clients).

-Martin

From ggm+ietf@apnic.net  Thu Jul 28 17:28:44 2011
Return-Path: <ggm+ietf@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33B8111E8130 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 17:28:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.31
X-Spam-Level: 
X-Spam-Status: No, score=-101.31 tagged_above=-999 required=5 tests=[AWL=-0.209, BAYES_00=-2.599, HELO_DYNAMIC_DHCP=1.398, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DRcrEtpop6WF for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 17:28:43 -0700 (PDT)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id 45AD511E8104 for <ietf@ietf.org>; Thu, 28 Jul 2011 17:28:43 -0700 (PDT)
Received: from dhcp-44e8.meeting.ietf.org (dhcp-44e8.meeting.ietf.org [130.129.68.232]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id E9245B673D for <ietf@ietf.org>; Fri, 29 Jul 2011 10:28:40 +1000 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: IPv6 traffic distribution
From: George Michaelson <ggm+ietf@apnic.net>
In-Reply-To: <4E31F3C2.4000000@gmail.com>
Date: Thu, 28 Jul 2011 20:28:28 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <76539F38-370D-4106-A633-B99ACE940523@apnic.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>	<4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com>	<20110727023833.5C72D1232958@drugs.dv.isc.org>	<m1QlzXt-0001gSC@stereo.hq.phicoh.net>	<2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com>	<392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local>	<10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com>	<CAKD1Yr3gv=+HfEZMsU0enNh8OQbemQh6iRzpGHsnmr7OJrTcFg@mail.gmail.com>	<392CB277BC2EAE4FB83C1206954BA6CEF635@newserver.arneill-py.local>	<3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk> <EMEW3|fa0511c175232cff9b9cb8310f081538n6RMCh03tjc|ecs.soton.ac.uk|3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk> <4E31F3C2.4000000@gmail.com>
To: IETF Discussion <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, 29 Jul 2011 00:28:44 -0000

you may like to look at

	http://labs.apnic.net/dns-measurement/

From scott.brim@gmail.com  Thu Jul 28 18:51:47 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 7E59011E80C3 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 18:51: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=[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 J2d6njDkHGLl for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 18:51:47 -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 E5B5311E80C2 for <ietf@ietf.org>; Thu, 28 Jul 2011 18:51:46 -0700 (PDT)
Received: by iye7 with SMTP id 7so4191403iye.31 for <ietf@ietf.org>; Thu, 28 Jul 2011 18:51:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:from:date:message-id:subject:to :cc:content-type; bh=PZIMyfPbTuFUtPVaUClPCgCr35RvVRQ6bBF8Q+KOeB4=; b=J8yTWYNo4mF1vcsQ6UHV0+7s1/jI84wlWweo8wRDjRSAADyLEpPLUHlLOo8kk3G0uv I8+o6rj0jzYg3Ty4Q+wAm7S9gDHdcSK7Ba9+Qs5Sq+7bRhKHZftvPdhT8mZvP87Ae8Cb 4/71fKoRf0jW7zIONlovJP9qqIAVK4cBR48UM=
Received: by 10.231.42.21 with SMTP id q21mr482464ibe.24.1311904306481; Thu, 28 Jul 2011 18:51:46 -0700 (PDT)
References: <4E308B21.1090305@gmail.com> <05599CE4-0BCE-4252-AC83-84B80D8116AA@cs.Berkeley.EDU> <4E31CD3D.1020200@gmail.com>
In-Reply-To: <4E31CD3D.1020200@gmail.com>
Mime-Version: 1.0 (iPad Mail 8L1)
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 28 Jul 2011 21:52:17 -0400
Message-ID: <-4274160919487882431@unknownmsgid>
Subject: Re: Kevin's second byte question
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Kevin Fall <kfall@cs.berkeley.edu>, 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, 29 Jul 2011 01:51:47 -0000

Brian, I recall some pretty serious agreement almost at the beginning
that it was a diffserv "field", only 6 bits, and that people who were
saying "diffserv byte" were wrong. I also recall some dithering over
whether the other two bits should be declared reserved, but without
conclusion.



On Jul 28, 2011, at 16:58, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> On 2011-07-28 16:49, Kevin Fall wrote:
>> Thanks for the quick response.
>>
>> Here's what my reading revealed, and you can tell me if I'm in error or not...
>>
>> RFC3260 tells us that the first six bits (not 8) are called the DS Field or Differentiated Services Field, and the subsequent
>> two bits are referred to as ECN ("ECN field" according to RFC 3168).  Same applies for what was formerly the IPv6 traffic class byte.
>>
>> That said, RFC 3260 is Informational, yet claims to update standards-track RFCs 2474 and 2597.  I'm not quite sure what sort of status that
>> leaves us with. [?]
>
> It can't. That claim shouldn't have been published IMHO. (And yes, I was co-chair
> of the diffserv WG at the time). However, it invokes BCP 37 = RFC 2780
> which is normative, so probably supersedes RFC 2474. 2780 doesn't answer your
> question though, since it refers to the 6-bit DS field and not to the whole
> byte or octet except as "superseded".
>
> I think you will need to add a complicated footnote on this.
>
> On 2011-07-29 01:10, Thomson, Martin wrote:
>
>> On 2011-07-27 at 18:03:13, Brian E Carpenter wrote:
>>>> The second byte in an IPv4 header is called the Differentiated
>>>> Services Field.
>>
>> I believe that this has been obsoleted by RFC 5241.
>
> Good one :-)
>
>    Brian
>
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From dhc2@dcrocker.net  Thu Jul 28 18:53:24 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 76B5711E80C3 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 18:53:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OUjE9aprUSYI for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 18:53:23 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id A331C11E8092 for <ietf@ietf.org>; Thu, 28 Jul 2011 18:53:23 -0700 (PDT)
Received: from [172.16.58.236] (modemcable252.155-70-69.static.videotron.ca [69.70.155.252]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p6T1rFMg023224 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 28 Jul 2011 18:53:22 -0700
Message-ID: <4E321288.7000309@dcrocker.net>
Date: Thu, 28 Jul 2011 21:53:12 -0400
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Why the IESG needs to review everything...
References: <4E308D64.3030804@gmail.com> <4E30927D.50808@dcrocker.net> <4E30B250.3030807@gmail.com> <4E3161AB.9010007@dcrocker.net> <4E31EF47.5070403@gmail.com>
In-Reply-To: <4E31EF47.5070403@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 28 Jul 2011 18:53:23 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 01:53:24 -0000

On 7/28/2011 7:22 PM, Brian E Carpenter wrote:
> Dave, we are shouting past each other so I will not repeat myself
> on all points. However,

Brian,

I did not ask you to repeat anything -- and don't want you to.

Rather, I asked you to move beyond cliche's and personal anecdotes into 
consideration of tradeoffs.  That is, I pointedly asked you /not/ to repeat 
yourself.

Please engage in the substance of such balanced analysis comparing benefits 
against costs.  It's not as if that's an unusual approach for evaluating 
expensive activities of questioned value...


>> Have you seen a pattern of having a Discuss cite the criterion that
>> justifies it?  I haven't.  It might be interesting to attempt an audit
>> of Discusses, against the criteria...
>
> It might, and at the time when the IESG had a large backlog of unresolved
> DISCUSSes and the current criteria were being developed (I'm talking
> about 2005/2006), the IESG did indeed end up looking at all the old
> DISCUSSes against the criteria, and held dedicated conference calls

I do not recall seeing this analysis made public.  The point behind my 
suggestion was to prmit transparent consideration of the use of Discuss. So 
whatever was done, it was not transparent to the community.

Further, my suggestion was for /current/ patterns, not in the past.


> to talk through many of those DISCUSSes and in many cases persuade the AD
> concerned to drop them, or rewrite them in an actionable format. In my
> recollection, Allison Mankin was the leader of the charge on this.
>
> But these are all judgment calls, so I don't think there can be an
> objective audit.

I don't recall requiring it to be "objective".  In fact, audits are often 
subjective.  That's ok as long as:

    a) the auditor gives thought to using reasonable criteria

    b) the criteria are made public

    c) they are applied consistently

Let's try to refrain from throwing up artificial barriers, as an excuse not to 
hold the process accountable.


> There could be an audit of how many DISCUSSes take
> more than N months to clear, or something like that. There were tools
> around for that some years ago, but I don't know if they exist for the
> modern version of the tracker.

That's nice, but not all that useful.  In contrast, looking at the substance of 
Discusses against the criteria that are supposed to be used for justifying them 
is directly relevant.

(Note that you replaced a focus on core substance and clear import, with 
something superficial and with a very ambiguous semantic.  In particular, 
longer-vs-shorter holding times have no obvious implication about the 
/appropriateness/ of the Discusses.)


>> Herein lies the real problem:  As with many process and structure
>> discussions in the IETF, folk often see only a simplistic, binary choice
>> between whatever they prefer, versus something akin to chaos.
>>
>> The world is more nuanced than that, and the choices more rich.
>>
>> Here is a small counter-example to your sole alternatives of status quo
>> or rubber stamp:
>>
>>       Imagine a process which requires a range of reviews and requires
>> ADs to take note of the reviews and the community support-vs-objection.
>>
>>       Imagine that the job of the ADs is to assess these and to block
>> proposals that have had major, unresolved problems uncovered or that
>> lack support, and to approve ones that have support and lack known,
>> major deficiencies as documented by the reviews.
>
> The only difference between that and what I see happening today is that
> the ADs actually verify the reviews by looking at the drafts themselves.

You are factually wrong.  AD's do their own reviews.  ADs formulate their own 
lists of issues and requirements.  AD's assert them as the basis for a Discuss.

They often do pay attention to other reviews -- sometimes quite mechanically, 
rather than from an informed basis -- but the exemplar I put forward is a 
fundamentally different model of AD behavior and responsibility.  I can't guess 
how you can misunderstand the difference.


> And why do they do that? Because they aren't going to take the
> responsibility for approving a document that they haven't read. Nobody
> would, I hope.

Therein lies a core problem with the model:  It hinges on personal investment by 
the AD, and a lack of trust in the community process, using the excuse that the 
process is not perfect, as if the AD's own evaluation process is...

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From cb.list6@gmail.com  Thu Jul 28 18:55:06 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 A8BE811E8092 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 18:55:06 -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 5s9cowS7yCBl for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 18:55:06 -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 D2E8311E80DF for <ietf@ietf.org>; Thu, 28 Jul 2011 18:55:05 -0700 (PDT)
Received: by fxe6 with SMTP id 6so2037075fxe.31 for <ietf@ietf.org>; Thu, 28 Jul 2011 18:55:05 -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=ZC9GN48K6UrvpL935qXI9WrGDKYwjzhcRpN8VHoWn+Y=; b=Mokb/mFU+Qy+yuNEZ0kG+Rvkv9fE3RJBDBg8hR2ov4tIzVghMqxqlfwGhhq3lDf7pR DW5hHP8sngmhh3oFDj4pCuS7T2wYsIN3P7Bylur4gKCkKvAngEh2Axqvmz5IDfrd1nSl JRRzuLqkBrOAPrhbv5lfkQP3NJmdgq+gOcdMY=
MIME-Version: 1.0
Received: by 10.223.88.219 with SMTP id b27mr988391fam.21.1311904504999; Thu, 28 Jul 2011 18:55:04 -0700 (PDT)
Received: by 10.223.79.66 with HTTP; Thu, 28 Jul 2011 18:55:04 -0700 (PDT)
Received: by 10.223.79.66 with HTTP; Thu, 28 Jul 2011 18:55:04 -0700 (PDT)
In-Reply-To: <201107290028.p6T0SQgQ013589@fs4113.wdf.sap.corp>
References: <4E3118E1.5090107@necom830.hpcl.titech.ac.jp> <201107290028.p6T0SQgQ013589@fs4113.wdf.sap.corp>
Date: Thu, 28 Jul 2011 18:55:04 -0700
Message-ID: <CAD6AjGRik+N0OObpO=AZE=gowS6bjMJmXF-Oz4w+Yh3-iQ0CVA@mail.gmail.com>
Subject: Re: "6to4 damages the Internet" (was Re:
From: Cameron Byrne <cb.list6@gmail.com>
To: mrex@sap.com
Content-Type: multipart/alternative; boundary=000e0cd4cab4fff0b804a92b919b
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 01:55:06 -0000

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

On Jul 28, 2011 5:28 PM, "Martin Rex" <mrex@sap.com> wrote:
>
> Masataka Ohta wrote:
> >
> > > It would be nice if 5 or 10 years ago there would have been a good
> > > standard to do address selection.
> >
> > 11 years ago in draft-ohta-e2e-multihoming-00.txt, I wrote:
> >
> >    End systems (hosts) are end systems. To make the end to end principle
> >    effectively work, the end systems must have all the available
> >    knowledge to make decisions by the end systems themselves.
> >
> >    With regard to multihoming, when an end system want to communicate
> >    with a multihomed end system, the end system must be able to select
> >    most appropriate (based on the local information) destination address
> >    of the multihomed end system.
>
>
> The primary reason why the IPv4 -> IPv6 transition is so painful
> is that it requires everyone one and everything to become multi-homed
> and every software to perform multi-connect, even though most
> devices actually just have a single interface.
>
> It would be so much easier if hosts on the public internet could
> use one single IPv6 address that contains both, the IPv6 network prefix
> and the IPv4 host address, and then let the network figure out whether
> the connect goes through as IPv4 or IPv6 (for IPv6 clients).
>

This is largely (not entirely)  achieved with nat64 / dns64.

Cb.
> -Martin
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

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

<p><br>
On Jul 28, 2011 5:28 PM, &quot;Martin Rex&quot; &lt;<a href=3D"mailto:mrex@=
sap.com">mrex@sap.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Masataka Ohta wrote:<br>
&gt; &gt;<br>
&gt; &gt; &gt; It would be nice if 5 or 10 years ago there would have been =
a good<br>
&gt; &gt; &gt; standard to do address selection.<br>
&gt; &gt;<br>
&gt; &gt; 11 years ago in draft-ohta-e2e-multihoming-00.txt, I wrote:<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0End systems (hosts) are end systems. To make the end to en=
d principle<br>
&gt; &gt; =A0 =A0effectively work, the end systems must have all the availa=
ble<br>
&gt; &gt; =A0 =A0knowledge to make decisions by the end systems themselves.=
<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0With regard to multihoming, when an end system want to com=
municate<br>
&gt; &gt; =A0 =A0with a multihomed end system, the end system must be able =
to select<br>
&gt; &gt; =A0 =A0most appropriate (based on the local information) destinat=
ion address<br>
&gt; &gt; =A0 =A0of the multihomed end system.<br>
&gt;<br>
&gt;<br>
&gt; The primary reason why the IPv4 -&gt; IPv6 transition is so painful<br=
>
&gt; is that it requires everyone one and everything to become multi-homed<=
br>
&gt; and every software to perform multi-connect, even though most<br>
&gt; devices actually just have a single interface.<br>
&gt;<br>
&gt; It would be so much easier if hosts on the public internet could<br>
&gt; use one single IPv6 address that contains both, the IPv6 network prefi=
x<br>
&gt; and the IPv4 host address, and then let the network figure out whether=
<br>
&gt; the connect goes through as IPv4 or IPv6 (for IPv6 clients).<br>
&gt;</p>
<p>This is largely (not entirely)=A0 achieved with nat64 / dns64.</p>
<p>Cb. <br>
&gt; -Martin<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>

--000e0cd4cab4fff0b804a92b919b--

From scott.brim@gmail.com  Thu Jul 28 19:01:10 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 46BED11E816C for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 19:01:10 -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 27RM5k0NXK+X for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 19:01:09 -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 C137011E80E4 for <ietf@ietf.org>; Thu, 28 Jul 2011 19:01:09 -0700 (PDT)
Received: by iye7 with SMTP id 7so4199975iye.31 for <ietf@ietf.org>; Thu, 28 Jul 2011 19:01:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:from:date:message-id:subject:to :cc:content-type; bh=PHJQck9hDBC1U9fWf70fCnBsJ+n8ZBEc7PkJz6PcrfU=; b=Te3onqFmmemKhRNeKzFeDSu0DNsgtg3QwyxFcrxh3iRSWORdvtLg87eaehWOzBu1U8 ORQ6v8TowbLeq/bbgqSdzimJX0Eg8jJlO784OK0uO9IeE+jwAHuxUWEDq5+pgkyR1bei eW54dDZJdhWbDEe8A5ELg59R/p1GGuv/LIRH4=
Received: by 10.231.12.140 with SMTP id x12mr470868ibx.99.1311904869411; Thu, 28 Jul 2011 19:01:09 -0700 (PDT)
References: <F5833273385BB34F99288B3648C4F06F13512DF4A7@EXCH-C2.corp.cloudmark.com> <051e01cc4d64$493d3c40$dbb7b4c0$@com>
In-Reply-To: <051e01cc4d64$493d3c40$dbb7b4c0$@com>
Mime-Version: 1.0 (iPad Mail 8L1)
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 28 Jul 2011 22:01:39 -0400
Message-ID: <3064576985382880915@unknownmsgid>
Subject: Re: On attending BoFs
To: Dan Wing <dwing@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 02:01:10 -0000

And do you really only want people in the room who already know the
issues and have decided to be for or against it?  If you already have
so many of them, you don't need a BOF at all, just take a hum and be
done. The main purpose of a BOF is to present. Information to the
community so they can decide if the IETF should adopt the work.

From brian.e.carpenter@gmail.com  Thu Jul 28 19:06: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 29F0411E816F for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 19:06: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 qpcDoITc-gAs for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 19:06:46 -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 2870511E80E4 for <ietf@ietf.org>; Thu, 28 Jul 2011 19:06:46 -0700 (PDT)
Received: by iye7 with SMTP id 7so4205093iye.31 for <ietf@ietf.org>; Thu, 28 Jul 2011 19:06:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=sPejQS5fU7w4G6IrVLQSgx2VJptDMhQeVqk3Exen6m0=; b=kvNiMtQ0nD4xroYjAN/FkSiAeduJztEcqsKsWYmFQc3JtnhVNmU7f2LeWZU48fX3BH GuT+mukxJ7MHCtzO4xiGrVSgS0cjiKa3FMYpQXZtlQjiPCi3GBZz/UdiNR45i4IdjRFb F1wFqW3xKETceem9Ow/027Y7Xq++sV6AY9bEM=
Received: by 10.42.23.200 with SMTP id t8mr531606icb.198.1311905205150; Thu, 28 Jul 2011 19:06:45 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id y3sm1019808ibc.54.2011.07.28.19.06.42 (version=SSLv3 cipher=OTHER); Thu, 28 Jul 2011 19:06:44 -0700 (PDT)
Message-ID: <4E3215AE.2060409@gmail.com>
Date: Fri, 29 Jul 2011 14:06:38 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Kevin's second byte question
References: <4E308B21.1090305@gmail.com> <05599CE4-0BCE-4252-AC83-84B80D8116AA@cs.Berkeley.EDU> <4E31CD3D.1020200@gmail.com> <-4274160919487882431@unknownmsgid>
In-Reply-To: <-4274160919487882431@unknownmsgid>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Kevin Fall <kfall@cs.berkeley.edu>, 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, 29 Jul 2011 02:06:47 -0000

On 2011-07-29 13:52, Scott Brim wrote:
> Brian, I recall some pretty serious agreement almost at the beginning
> that it was a diffserv "field", only 6 bits, and that people who were
> saying "diffserv byte" were wrong. I also recall some dithering over
> whether the other two bits should be declared reserved, but without
> conclusion.

Nevertheless, the words in RFC 2474 don't say that. They say that
DS Field refers to the entire octet, including the (then unused)
ECN bits.

We knew ECN was coming when this was published.

    Brian
> 
> 
> 
> On Jul 28, 2011, at 16:58, Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
> 
>> On 2011-07-28 16:49, Kevin Fall wrote:
>>> Thanks for the quick response.
>>>
>>> Here's what my reading revealed, and you can tell me if I'm in error or not...
>>>
>>> RFC3260 tells us that the first six bits (not 8) are called the DS Field or Differentiated Services Field, and the subsequent
>>> two bits are referred to as ECN ("ECN field" according to RFC 3168).  Same applies for what was formerly the IPv6 traffic class byte.
>>>
>>> That said, RFC 3260 is Informational, yet claims to update standards-track RFCs 2474 and 2597.  I'm not quite sure what sort of status that
>>> leaves us with. [?]
>> It can't. That claim shouldn't have been published IMHO. (And yes, I was co-chair
>> of the diffserv WG at the time). However, it invokes BCP 37 = RFC 2780
>> which is normative, so probably supersedes RFC 2474. 2780 doesn't answer your
>> question though, since it refers to the 6-bit DS field and not to the whole
>> byte or octet except as "superseded".
>>
>> I think you will need to add a complicated footnote on this.
>>
>> On 2011-07-29 01:10, Thomson, Martin wrote:
>>
>>> On 2011-07-27 at 18:03:13, Brian E Carpenter wrote:
>>>>> The second byte in an IPv4 header is called the Differentiated
>>>>> Services Field.
>>> I believe that this has been obsoleted by RFC 5241.
>> Good one :-)
>>
>>    Brian
>>
>>
>>
>>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
> 

From moore@network-heretics.com  Thu Jul 28 19:21: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 416755E8007 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 19:21:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.677
X-Spam-Level: 
X-Spam-Status: No, score=-3.677 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JnChcs-QXrQI for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 19:21:13 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 6D8DD21F8867 for <ietf@ietf.org>; Thu, 28 Jul 2011 19:21:13 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 7B39F20861; Thu, 28 Jul 2011 22:21:12 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute4.internal (MEProxy); Thu, 28 Jul 2011 22:21: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:content-transfer-encoding:message-id :references:to; s=smtpout; bh=c6d5jUlfYOc4D1Xyp86hH3jBmXI=; b=VX qBNCo0+QEhI8MGiRSgSSW2tpSfnbRoc9mmI71XIjgH/sZB3VhxpAEndti3hs7wB+ 0+n8AUPTpQbD6qGTavI3QeJE/xlO4pz0T940sPrvL3OGnzkr9el6TgcShLD+uBiR dzsROsbqdUnLcvt/Tb/cHexBvUK29awaaAiioFdE8=
X-Sasl-enc: GIHholjGurTQ9QyO+E+YobSQx311bCg+8LOcgvy7ya23 1311906072
Received: from [192.168.210.105] (modemcable114.145-70-69.static.videotron.ca [69.70.145.114]) by mail.messagingengine.com (Postfix) with ESMTPSA id 05285456334; Thu, 28 Jul 2011 22:21:11 -0400 (EDT)
Subject: Re: IPv6 traffic distribution
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: <4E31F3C2.4000000@gmail.com>
Date: Thu, 28 Jul 2011 22:21:11 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DBB106E0-F6B8-408E-A9EE-75FF005D3AB6@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>	<4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com>	<20110727023833.5C72D1232958@drugs.dv.isc.org>	<m1QlzXt-0001gSC@stereo.hq.phicoh.net>	<2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com>	<392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local>	<10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com>	<CAKD1Yr3gv=+HfEZMsU0enNh8OQbemQh6iRzpGHsnmr7OJrTcFg@mail.gmail.com>	<392CB277BC2EAE4FB83C1206954BA6CEF635@newserver.arneill-py.local>	<3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk> <EMEW3|fa0511c175232cff9b9cb8310f081538n6RMCh03tjc|ecs.soton.ac.uk|3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk> <4E31F3C2.4000000@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 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: Fri, 29 Jul 2011 02:21:14 -0000

On Jul 28, 2011, at 7:41 PM, Brian E Carpenter wrote:

> Looking at a trace that I got from Geoff Huston a month or two ago,
> there are 25486 IPv6 TCP sessions of which 10748 have a 6to4 source
> address.
>=20
> That's surprisingly high, showing that the answer depends greatly on
> the point of observation, and explains why operators really need
> to try to run a decent 6to4 relay service as long as so many
> such clients are observed. Which is why disabling 6to4 in clients
> has to be the priority; it's far too soon to decommission the
> relays.

Actually, it's why making hosts prefer IPv4 over 6to4 is the priority.   =
There's absolutely nothing wrong with using 6to4 if it's the best =
connectivity to the destination that you have.

Also,  this isn't a contest, we're on the same team, and we shouldn't be =
competing against one another.  The entire purpose of 6to4 is to allow =
people to use IPv6 before they have native IPv6 connectivity, because we =
recognize that the latter is in some cases very difficult to achieve =
end-to-end and faces numerous barriers that vary from one situation to =
the next.  That's why we have so many technologies for layering IPv6 =
over IPv4.

IOW, 6to4's purpose is to be a gateway drug for native IPv6.   And it =
can serve that purpose even if at any given time only 1% are using it.  =
The main thing is to make sure that people who do try 6to4 find it =
attractive enough that they want to upgrade to native IPv6.   That means =
not using 6to4 in cases where it will degrade performance compared to =
what people get already with IPv4, but it doesn't mean disabling 6to4 =
entirely.  It also means that DoS attacks on 6to4 are counterproductive.

Keith


From brian.e.carpenter@gmail.com  Thu Jul 28 19:38: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 5DCD121F8AC9 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 19:38: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=[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 9f-bkOcm3P-Q for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 19:38:51 -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 6A23621F8AAC for <ietf@ietf.org>; Thu, 28 Jul 2011 19:38:51 -0700 (PDT)
Received: by iye7 with SMTP id 7so4236344iye.31 for <ietf@ietf.org>; Thu, 28 Jul 2011 19:38:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=RmZsOh+XPXHmjstVE1CnpP3BkVQ4zmZcH4nRSnOxJjU=; b=eYu7CM39AxWqcHhvGfqVO52YfOHzqAREEfBAxAUVowryl/TBexxBzgS29vHO2FqqAx ejlSU+JNyMMRLMEUDY4EP849HjBpRyqGMw+KgYiCRWGMJu+nWFGIyIM6mp3ZDfSXEU80 P1zo3fSqNnBM/6yoMjOuIUhIdQYS9H9n+zbvU=
Received: by 10.42.246.66 with SMTP id lx2mr462413icb.478.1311907130822; Thu, 28 Jul 2011 19:38:50 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id k16sm2091417icc.22.2011.07.28.19.38.47 (version=SSLv3 cipher=OTHER); Thu, 28 Jul 2011 19:38:50 -0700 (PDT)
Message-ID: <4E321D33.80904@gmail.com>
Date: Fri, 29 Jul 2011 14:38: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: dcrocker@bbiw.net
Subject: Re: Why the IESG needs to review everything...
References: <4E308D64.3030804@gmail.com> <4E30927D.50808@dcrocker.net>	<4E30B250.3030807@gmail.com> <4E3161AB.9010007@dcrocker.net>	<4E31EF47.5070403@gmail.com> <4E321288.7000309@dcrocker.net>
In-Reply-To: <4E321288.7000309@dcrocker.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 02:38:52 -0000

Dave,

On 2011-07-29 13:53, Dave CROCKER wrote:
> 
> On 7/28/2011 7:22 PM, Brian E Carpenter wrote:
>> Dave, we are shouting past each other so I will not repeat myself
>> on all points. However,
> 
> Brian,
> 
> I did not ask you to repeat anything -- and don't want you to.
> 
> Rather, I asked you to move beyond cliche's and personal anecdotes into
> consideration of tradeoffs.  That is, I pointedly asked you /not/ to
> repeat yourself.
> 
> Please engage in the substance of such balanced analysis comparing
> benefits against costs.  It's not as if that's an unusual approach for
> evaluating expensive activities of questioned value...

May argument is that if we move the cost (that of final review prior
to committing the text to the RFC Editor), we do not remove the
problem (of the final review being exhaustive and time consuming),
unless we also lower the implied standard of quality.

To my mind it's implicit in RFC 3935 that the present quality standard
is not lowered - especially, that in addition to verifying that
a specification is valid in itself, we verify that it does not damage
other aspects of the Internet. That makes final review by a cross-area
team essential, and today that team is the IESG.

I wouldn't mind moving the responsibility to some other cross-area
team, but it seems like a zero-sum game to me.

> 
>>> Have you seen a pattern of having a Discuss cite the criterion that
>>> justifies it?  I haven't.  It might be interesting to attempt an audit
>>> of Discusses, against the criteria...
>>
>> It might, and at the time when the IESG had a large backlog of unresolved
>> DISCUSSes and the current criteria were being developed (I'm talking
>> about 2005/2006), the IESG did indeed end up looking at all the old
>> DISCUSSes against the criteria, and held dedicated conference calls
> 
> I do not recall seeing this analysis made public.

It was a dynamic process, but I wouldn't be surprised if Allison or
Bill Fenner or somebody did post data at some stage; but that's ancient
history now.

The point behind my
> suggestion was to prmit transparent consideration of the use of Discuss.
> So whatever was done, it was not transparent to the community.
> 
> Further, my suggestion was for /current/ patterns, not in the past.

And all the data is in the tracker these days; it's very easy to
find the DISCUSSes against any draft.

>> to talk through many of those DISCUSSes and in many cases persuade the AD
>> concerned to drop them, or rewrite them in an actionable format. In my
>> recollection, Allison Mankin was the leader of the charge on this.
>>
>> But these are all judgment calls, so I don't think there can be an
>> objective audit.
> 
> I don't recall requiring it to be "objective".  In fact, audits are
> often subjective.  That's ok as long as:
> 
>    a) the auditor gives thought to using reasonable criteria
> 
>    b) the criteria are made public
> 
>    c) they are applied consistently

That is the judgment part.

> 
> Let's try to refrain from throwing up artificial barriers, as an excuse
> not to hold the process accountable.
> 
> 
>> There could be an audit of how many DISCUSSes take
>> more than N months to clear, or something like that. There were tools
>> around for that some years ago, but I don't know if they exist for the
>> modern version of the tracker.
> 
> That's nice, but not all that useful.  In contrast, looking at the
> substance of Discusses against the criteria that are supposed to be used
> for justifying them is directly relevant.
> 
> (Note that you replaced a focus on core substance and clear import, with
> something superficial and with a very ambiguous semantic.  In
> particular, longer-vs-shorter holding times have no obvious implication
> about the /appropriateness/ of the Discusses.)

I think that a long holding time clearly implies one of two causes:

1. A fumble by the shepherd; in fact it was to avoid this sort of problem that
   the shepherding process was carefully defined. Again, credit to Allison.

2. A failed dialogue between the DISCUSSing AD and the authors and/or WG.
   I would assert that most of those are due to non-actionable DISCUSSes.
   There was a lot of analysis of real cases of serious delay behind the
   section on "DISCUSS non-criteria" in
   http://www.ietf.org/iesg/statement/discuss-criteria.html

The fact that we're having this conversation several years later
tells me that human nature hasn't changed much recently. ADs *do*
need to look at those criteria and it's absolutely in order for the
community to complain when they don't.

>>> Herein lies the real problem:  As with many process and structure
>>> discussions in the IETF, folk often see only a simplistic, binary choice
>>> between whatever they prefer, versus something akin to chaos.
>>>
>>> The world is more nuanced than that, and the choices more rich.
>>>
>>> Here is a small counter-example to your sole alternatives of status quo
>>> or rubber stamp:
>>>
>>>       Imagine a process which requires a range of reviews and requires
>>> ADs to take note of the reviews and the community support-vs-objection.
>>>
>>>       Imagine that the job of the ADs is to assess these and to block
>>> proposals that have had major, unresolved problems uncovered or that
>>> lack support, and to approve ones that have support and lack known,
>>> major deficiencies as documented by the reviews.
>>
>> The only difference between that and what I see happening today is that
>> the ADs actually verify the reviews by looking at the drafts themselves.
> 
> You are factually wrong.  AD's do their own reviews.  ADs formulate
> their own lists of issues and requirements.  AD's assert them as the
> basis for a Discuss.

I didn't mean to imply that they (all) don't. But the criteria for
a comment being a DISCUSS are on public record.

> They often do pay attention to other reviews -- sometimes quite
> mechanically, rather than from an informed basis -- but the exemplar I
> put forward is a fundamentally different model of AD behavior and
> responsibility.  I can't guess how you can misunderstand the difference.

I don't think we differ on the responsibility that most ADs feel when
ballotting on a draft. I'm sure there is a significant variety of
"personal algorithms" by which ADs operate.

>> And why do they do that? Because they aren't going to take the
>> responsibility for approving a document that they haven't read. Nobody
>> would, I hope.
> 
> Therein lies a core problem with the model:  It hinges on personal
> investment by the AD, 

 ... by whoever is making the final determination ...

> and a lack of trust in the community process,
> using the excuse that the process is not perfect, as if the AD's own
> evaluation process is...

Nobody, surely, is claiming perfection? What I am claiming is that
knowing one has final responsibility makes a person strive for
something closer to perfection - which means noticing defects in
a draft that nobody else has noticed.

Enough on this thread from me.

Regards

     Brian

From mrex@sap.com  Thu Jul 28 19:38:52 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 9D84521F8AAC; Thu, 28 Jul 2011 19:38:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.935
X-Spam-Level: 
X-Spam-Status: No, score=-9.935 tagged_above=-999 required=5 tests=[AWL=0.314,  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 AQcz8QH+cXFe; Thu, 28 Jul 2011 19:38:51 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id CD29321F886C; Thu, 28 Jul 2011 19:38:50 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p6T2cDxV004245 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 29 Jul 2011 04:38:13 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201107290238.p6T2cCLu021118@fs4113.wdf.sap.corp>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt>
To: marka@isc.org (Mark Andrews)
Date: Fri, 29 Jul 2011 04:38:12 +0200 (MEST)
In-Reply-To: <20110728020118.647E1123AED8@drugs.dv.isc.org> from "Mark Andrews" at Jul 28, 11 12:01:18 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: ibc@aliax.net, hybi@ietf.org, ietf@ietf.org, w@1wt.eu
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, 29 Jul 2011 02:38:52 -0000

Mark Andrews wrote:
> 
> Martin Rex writes:
> >
> > Mark Andrews wrote:
> > > 
> > > More correctly it is try the first address and if that doesn't
> > > connect in a short period (150...250ms) start a second connection
> > > to the next address while continuing with the first.  If you have
> > > more that 2 address you do something similar for the next one
> > 
> > Happy eyeballs means that a clients reaction to congestion is
> > to perform an DoS attack, flood the network with additional
> > connection requests and hammer the server with many additional
> > half-open connections that will never actually get used.
> 
> It is not a DoS attack.  The client is almost certainly going to
> make those connection attempts anyway if the path is congested
> enough to cause the first connection attempt to fail.  The only
> difference is the application gives up in 30 seconds rather than
> 60 or 90 seconds by doing the attempts serially.

150...250ms  ?!

For a satellite link you already have started 3 parallel connects
in non-congested(!) situations. 

just some random IPv4 pings from my office (in germany)
_without_congestion_:

   ping  www.asus.com.tw            300-380ms
   ping  south-america.pool.ntp.org 280-370ms
   ping  oceania.pool.ntp.org       340-420ms
   ping  www.eff.org                160-170ms
   ping  www.ietf79.cn              330-450ms
   ping  www.ietf76.jp              270-370ms

So your approach is already hurting the network without congestion!

-Martin

From mohta@necom830.hpcl.titech.ac.jp  Thu Jul 28 19:45:01 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 637EC21F8B86 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 19:45:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.079
X-Spam-Level: 
X-Spam-Status: No, score=-0.079 tagged_above=-999 required=5 tests=[AWL=0.011,  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 rZvCgBhHPUKj for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 19:45:01 -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 9341211E8076 for <ietf@ietf.org>; Thu, 28 Jul 2011 19:45:00 -0700 (PDT)
Received: (qmail 53759 invoked from network); 29 Jul 2011 03:05:19 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 29 Jul 2011 03:05:19 -0000
Message-ID: <4E321E46.3080104@necom830.hpcl.titech.ac.jp>
Date: Fri, 29 Jul 2011 11:43:18 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Cameron Byrne <cb.list6@gmail.com>
Subject: Re: "6to4 damages the Internet" (was Re:
References: <4E3118E1.5090107@necom830.hpcl.titech.ac.jp> <201107290028.p6T0SQgQ013589@fs4113.wdf.sap.corp> <CAD6AjGRik+N0OObpO=AZE=gowS6bjMJmXF-Oz4w+Yh3-iQ0CVA@mail.gmail.com>
In-Reply-To: <CAD6AjGRik+N0OObpO=AZE=gowS6bjMJmXF-Oz4w+Yh3-iQ0CVA@mail.gmail.com>
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: Fri, 29 Jul 2011 02:45:01 -0000

Cameron Byrne wrote:

>> The primary reason why the IPv4 ->  IPv6 transition is so painful
>> is that it requires everyone one and everything to become multi-homed
>> and every software to perform multi-connect, even though most
>> devices actually just have a single interface.

It was not a problem, because IPv6 was designed to be able to
handle multiple addresses properly with a single interface.

>> It would be so much easier if hosts on the public internet could
>> use one single IPv6 address that contains both, the IPv6 network prefix
>> and the IPv4 host address, and then let the network figure out whether
>> the connect goes through as IPv4 or IPv6 (for IPv6 clients).

> This is largely (not entirely)  achieved with nat64 / dns64.

Assuming NAT, we don't need IPv6.

Moreover, unlike nat64, nat44 can be fully transparent end to end.

So, why do we have to be bothered by 6to4?

						Masataka Ohta

From marka@isc.org  Thu Jul 28 20:05: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 9A21621F8570; Thu, 28 Jul 2011 20:05:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level: 
X-Spam-Status: No, score=-2.561 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 nOqylViRgvUs; Thu, 28 Jul 2011 20:05:48 -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 0D90521F856B; Thu, 28 Jul 2011 20:05:47 -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 322245F98FC; Fri, 29 Jul 2011 03:05:09 +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 269E6216C84; Fri, 29 Jul 2011 03:04:37 +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 52788125120E; Fri, 29 Jul 2011 13:04:33 +1000 (EST)
To: mrex@sap.com
From: Mark Andrews <marka@isc.org>
References: <201107290238.p6T2cCLu021118@fs4113.wdf.sap.corp>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt>
In-reply-to: Your message of "Fri, 29 Jul 2011 04:38:12 +0200." <201107290238.p6T2cCLu021118@fs4113.wdf.sap.corp>
Date: Fri, 29 Jul 2011 13:04:33 +1000
Message-Id: <20110729030433.52788125120E@drugs.dv.isc.org>
Cc: ibc@aliax.net, hybi@ietf.org, ietf@ietf.org, w@1wt.eu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 03:05:49 -0000

In message <201107290238.p6T2cCLu021118@fs4113.wdf.sap.corp>, Martin Rex writes
:
> Mark Andrews wrote:
> > 
> > Martin Rex writes:
> > >
> > > Mark Andrews wrote:
> > > > 
> > > > More correctly it is try the first address and if that doesn't
> > > > connect in a short period (150...250ms) start a second connection
> > > > to the next address while continuing with the first.  If you have
> > > > more that 2 address you do something similar for the next one
> > > 
> > > Happy eyeballs means that a clients reaction to congestion is
> > > to perform an DoS attack, flood the network with additional
> > > connection requests and hammer the server with many additional
> > > half-open connections that will never actually get used.
> > 
> > It is not a DoS attack.  The client is almost certainly going to
> > make those connection attempts anyway if the path is congested
> > enough to cause the first connection attempt to fail.  The only
> > difference is the application gives up in 30 seconds rather than
> > 60 or 90 seconds by doing the attempts serially.
> 
> 150...250ms  ?!

Yes, that small.  For most people, most connections are "in country"
or "in continent" however there are always exceptions to this.
The times are driven by human delay tolerances.

> For a satellite link you already have started 3 parallel connects
> in non-congested(!) situations. 

Indeed.  However only one will have data sent over it.  The three
way handshake won't even complete for two of them in many cases.
For those that do complete the server won't be woken up in many
cases as no data gets sent.

> just some random IPv4 pings from my office (in germany)
> _without_congestion_:
> 
>    ping  www.asus.com.tw            300-380ms
>    ping  south-america.pool.ntp.org 280-370ms
>    ping  oceania.pool.ntp.org       340-420ms
>    ping  www.eff.org                160-170ms
>    ping  www.ietf79.cn              330-450ms
>    ping  www.ietf76.jp              270-370ms
> 
> So your approach is already hurting the network without congestion!

Only if you think a could of extra TCP connection attemps to servers
on the other side of the world is hurting the network. 
 
B.T.W. I'm well aware of speed of light issues.  Look at my signature.

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

From michel@arneill-py.sacramento.ca.us  Thu Jul 28 20:41: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 45DBB11E8076 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 20:41:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.131
X-Spam-Level: 
X-Spam-Status: No, score=-2.131 tagged_above=-999 required=5 tests=[AWL=0.134,  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 gBDvQifkNslX for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 20:41:32 -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 927B111E8075 for <ietf@ietf.org>; Thu, 28 Jul 2011 20:41:32 -0700 (PDT)
Subject: RE: IPv6 traffic distribution
Date: Thu, 28 Jul 2011 20:41:32 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF637@newserver.arneill-py.local>
Content-class: urn:content-classes:message
In-Reply-To: <4E31F3C2.4000000@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-MimeOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: IPv6 traffic distribution
Thread-Index: AcxNf/PW6bvRPQPCTQe1ItUb0nCYqgAHlKAg
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com><4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>	<4E2EDF23.3060804@gmail.com><4E2F4491.30102@gmail.com>	<20110727023833.5C72D1232958@drugs.dv.isc.org>	<m1QlzXt-0001gSC@stereo.hq.phicoh.net>	<2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com>	<392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local>	<10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com>	<CAKD1Yr3gv=+HfEZMsU0enNh8OQbemQh6iRzpGHsnmr7OJrTcFg@mail.gmail.com>	<392CB277BC2EAE4FB83C1206954BA6CEF635@newserver.arneill-py.local>	<3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk><EMEW3|fa0511c175232cff9b9cb8310f081538n6RMCh03tjc|ecs.soton.ac.uk|3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk> <4E31F3C2.4000000@gmail.com>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>, "Tim Chown" <tjc@ecs.soton.ac.uk>
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, 29 Jul 2011 03:41:33 -0000

> Brian E Carpenter wrote:
> Looking at a trace that I got from Geoff Huston a month or
> two ago, there are 25486 IPv6 TCP sessions of which 10748
> have a 6to4 source address. That's surprisingly high,

Not to me.

> showing that the answer depends greatly on the
> point of observation

Indeed this is the key. Validate the sample (the trace). To be
meaningful, that is. Collecting IPv6 stats somewhere close to someone
heavily involved in IPv6 deployment is meaningless. Among other things,
Tim's numbers. Tim, we have met a few times; as I recall, you are the
one who convinced me of the inevitability of IPv6 NAT. Your numbers are
meaningless; not because you don't collect them right or anything
involving your skills or competence, but because you're too close to the
problem. That's the geek syndrome.

IMHO, the only valid stats we can gather are either from a large content
provider (which is why Lorenzo's numbers are so interesting) or from a
large eyeball ISP. Cisco, Juniper, Apple, the academia, the IETF, etc
are NOT valid places to collect data.


> George Michaelson wrote:
> you may like to look at
> http://labs.apnic.net/dns-measurement/

Same remarks as above, plus I don't see there anything that separates
6rd.

Michel.


From ajs@anvilwalrusden.com  Thu Jul 28 20:49:39 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 9B1F611E8076 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 20:49:39 -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 PuWYW1NOZ1sK for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 20:49:39 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 1F38411E8075 for <ietf@ietf.org>; Thu, 28 Jul 2011 20:49:39 -0700 (PDT)
Received: from shinkuro.com (dhcp-464e.meeting.ietf.org [130.129.70.78]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 3BA101ECB41D for <ietf@ietf.org>; Fri, 29 Jul 2011 03:49:38 +0000 (UTC)
Date: Thu, 28 Jul 2011 23:49:36 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Why the IESG needs to review everything...
Message-ID: <20110729034936.GB8787@shinkuro.com>
References: <4E308D64.3030804@gmail.com> <3D54259C-D229-4FFA-A7E3-0947459A0F14@kumari.net> <F5833273385BB34F99288B3648C4F06F13512DF495@EXCH-C2.corp.cloudmark.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF495@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, 29 Jul 2011 03:49:39 -0000

Dear colleagues,

This is not to pick on Murray, who was not making the point I am
trying to draw out of his remarks.  Sorry, Murray.

On Thu, Jul 28, 2011 at 08:45:41AM -0700, Murray S. Kucherawy wrote:
  
> the process.  So perhaps what's needed is an optional document state
> prior to Publication Requested called Review Requested,

I hereby propose that every single I-D adopted by every working group
go into Review Requested state.  Oh.  Right.

In my opinion, this thread would be a lot better motivated if we (and
I emphatically include myself) did a lot more review, and did it a lot
more carefully.  As a WG chair, I have faced a number of occasions in
which plain embarrassing flaws in documents made it past my own review
(which means "through WGLC") and up to the IESG.  As a participant, I
have noticed more than once that my failure to review something I
should have made it all the way to the IESG before someone said, "Uh,
hey, there's an issue."

Once frivolous DISCUSSes way outnumber serious ones, I'll feel like
there's a problem.  We're all busy, and by the grace of some power who
doesn't explain itself to me some employers are willing to subsidize
the Bulwark Panel of Final Review.  Given my own experience of what I
regard as mistaken or frivolous DISCUSSes, when every document has 5
or 6 really high quality reviews both in WGLC and IETF LC, I'll feel
that we can start throwing stones.  But today, not so much: most
DISCUSSes are in fact attempts to discuss unclear or -- sometimes --
seriously mistaken parts of drafts.  Maybe in others' corner of the
IETF it's different, but I feel that I need to pick up my end of the
log before telling other people to haul their end.

Best,

A
-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From jmh@joelhalpern.com  Thu Jul 28 20:54:05 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 1E21911E8075 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 20:54:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.557
X-Spam-Level: 
X-Spam-Status: No, score=-102.557 tagged_above=-999 required=5 tests=[AWL=0.042, 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 AMdZQ69XaL50 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 20:54:04 -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 15D5F11E8076 for <ietf@ietf.org>; Thu, 28 Jul 2011 20:54:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 5A98E3244FB4; Thu, 28 Jul 2011 20:54:03 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [130.129.67.226] (dhcp-43e2.meeting.ietf.org [130.129.67.226]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id E94623228BEB; Thu, 28 Jul 2011 20:54:02 -0700 (PDT)
Message-ID: <4E322EDB.7030306@joelhalpern.com>
Date: Thu, 28 Jul 2011 23:54:03 -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: dcrocker@bbiw.net
Subject: Re: Why the IESG needs to review everything...
References: <4E308D64.3030804@gmail.com> <4E30927D.50808@dcrocker.net>	<4E30B250.3030807@gmail.com> <4E3161AB.9010007@dcrocker.net>	<4E31EF47.5070403@gmail.com> <4E321288.7000309@dcrocker.net>
In-Reply-To: <4E321288.7000309@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Dave CROCKER <dhc2@dcrocker.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 03:54:05 -0000

I think I understand your request taht we move beyond personal 
anecdotes.  In principle, I even agree with you.

However, when I try to act on that, I am stumped.  I do not see any way 
to evaluate say the last 2 years discusses to determine whether they 
were more harmful or more helpful.
Any such evaluation would have to icnlude the various area reviews which 
occur during last call, but which are supported by the possibility of a 
discuss if they are ignored and the AD decides they matter.
Yes, I have a gut feel on the matter.  So does everyone in the discussion.

But you asked that we go beyond that.  How?

Yours,
Joel

On 7/28/2011 9:53 PM, Dave CROCKER wrote:
>
> On 7/28/2011 7:22 PM, Brian E Carpenter wrote:
>> Dave, we are shouting past each other so I will not repeat myself
>> on all points. However,
>
> Brian,
>
> I did not ask you to repeat anything -- and don't want you to.
>
> Rather, I asked you to move beyond cliche's and personal anecdotes into
> consideration of tradeoffs. That is, I pointedly asked you /not/ to
> repeat yourself.
>
> Please engage in the substance of such balanced analysis comparing
> benefits against costs. It's not as if that's an unusual approach for
> evaluating expensive activities of questioned value...
>
>
>>> Have you seen a pattern of having a Discuss cite the criterion that
>>> justifies it? I haven't. It might be interesting to attempt an audit
>>> of Discusses, against the criteria...
>>
>> It might, and at the time when the IESG had a large backlog of unresolved
>> DISCUSSes and the current criteria were being developed (I'm talking
>> about 2005/2006), the IESG did indeed end up looking at all the old
>> DISCUSSes against the criteria, and held dedicated conference calls
>
> I do not recall seeing this analysis made public. The point behind my
> suggestion was to prmit transparent consideration of the use of Discuss.
> So whatever was done, it was not transparent to the community.
>
> Further, my suggestion was for /current/ patterns, not in the past.
>
>
>> to talk through many of those DISCUSSes and in many cases persuade the AD
>> concerned to drop them, or rewrite them in an actionable format. In my
>> recollection, Allison Mankin was the leader of the charge on this.
>>
>> But these are all judgment calls, so I don't think there can be an
>> objective audit.
>
> I don't recall requiring it to be "objective". In fact, audits are often
> subjective. That's ok as long as:
>
> a) the auditor gives thought to using reasonable criteria
>
> b) the criteria are made public
>
> c) they are applied consistently
>
> Let's try to refrain from throwing up artificial barriers, as an excuse
> not to hold the process accountable.
>
>
>> There could be an audit of how many DISCUSSes take
>> more than N months to clear, or something like that. There were tools
>> around for that some years ago, but I don't know if they exist for the
>> modern version of the tracker.
>
> That's nice, but not all that useful. In contrast, looking at the
> substance of Discusses against the criteria that are supposed to be used
> for justifying them is directly relevant.
>
> (Note that you replaced a focus on core substance and clear import, with
> something superficial and with a very ambiguous semantic. In particular,
> longer-vs-shorter holding times have no obvious implication about the
> /appropriateness/ of the Discusses.)
>
>
>>> Herein lies the real problem: As with many process and structure
>>> discussions in the IETF, folk often see only a simplistic, binary choice
>>> between whatever they prefer, versus something akin to chaos.
>>>
>>> The world is more nuanced than that, and the choices more rich.
>>>
>>> Here is a small counter-example to your sole alternatives of status quo
>>> or rubber stamp:
>>>
>>> Imagine a process which requires a range of reviews and requires
>>> ADs to take note of the reviews and the community support-vs-objection.
>>>
>>> Imagine that the job of the ADs is to assess these and to block
>>> proposals that have had major, unresolved problems uncovered or that
>>> lack support, and to approve ones that have support and lack known,
>>> major deficiencies as documented by the reviews.
>>
>> The only difference between that and what I see happening today is that
>> the ADs actually verify the reviews by looking at the drafts themselves.
>
> You are factually wrong. AD's do their own reviews. ADs formulate their
> own lists of issues and requirements. AD's assert them as the basis for
> a Discuss.
>
> They often do pay attention to other reviews -- sometimes quite
> mechanically, rather than from an informed basis -- but the exemplar I
> put forward is a fundamentally different model of AD behavior and
> responsibility. I can't guess how you can misunderstand the difference.
>
>
>> And why do they do that? Because they aren't going to take the
>> responsibility for approving a document that they haven't read. Nobody
>> would, I hope.
>
> Therein lies a core problem with the model: It hinges on personal
> investment by the AD, and a lack of trust in the community process,
> using the excuse that the process is not perfect, as if the AD's own
> evaluation process is...
>
> d/

From eburger-l@standardstrack.com  Thu Jul 28 21:12:55 2011
Return-Path: <eburger-l@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 0531A21F86DC; Thu, 28 Jul 2011 21:12:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.554
X-Spam-Level: 
X-Spam-Status: No, score=-2.554 tagged_above=-999 required=5 tests=[AWL=0.045,  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 OfgXKMvW6dpD; Thu, 28 Jul 2011 21:12:54 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 6AAB821F86D7; Thu, 28 Jul 2011 21:12:54 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com;  h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=Lqb0kw3pYWg2G8Gdxoy5jwKbJAIlRjSDvBxbt1CnO8bQ+wjdwFQvpNXX3+V3ZuDr/QgheuPGtJk28QWUuNBoOWVPXLiYeCXIzMRMn8tbiPlTZSmuVD+D2wXp0R0bvlcO;
Received: from dhcp-42f9.meeting.ietf.org ([130.129.66.249]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger-l@standardstrack.com>) id 1QmeRQ-0001mX-7m; Thu, 28 Jul 2011 21:12:53 -0700
Subject: Re: On attending BoFs
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <3064576985382880915@unknownmsgid>
Date: Fri, 29 Jul 2011 00:12:49 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <F9EC5BB4-F51C-47E9-AE84-BBC440715D31@standardstrack.com>
References: <F5833273385BB34F99288B3648C4F06F13512DF4A7@EXCH-C2.corp.cloudmark.com> <051e01cc4d64$493d3c40$dbb7b4c0$@com> <3064576985382880915@unknownmsgid>
To: IETF <ietf@ietf.org>
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: 
Cc: IAOC <iaoc@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 04:12:55 -0000

Just for the record: we want big rooms!

On Jul 28, 2011, at 10:01 PM, Scott Brim wrote:

> And do you really only want people in the room who already know the
> issues and have decided to be for or against it?  If you already have
> so many of them, you don't need a BOF at all, just take a hum and be
> done. The main purpose of a BOF is to present. Information to the
> community so they can decide if the IETF should adopt the work.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From joelja@bogus.com  Thu Jul 28 21:24: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 D2B5621F8760 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 21:24:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.34
X-Spam-Level: 
X-Spam-Status: No, score=-102.34 tagged_above=-999 required=5 tests=[AWL=0.259, 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 965pWlrCx8Bi for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 21:24:45 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id EE46521F875E for <ietf@ietf.org>; Thu, 28 Jul 2011 21:24:44 -0700 (PDT)
Received: from dhcp-47c2.meeting.ietf.org (dhcp-47c2.meeting.ietf.org [130.129.71.194]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p6T4O2Bd077976 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 29 Jul 2011 04:24:03 GMT (envelope-from joelja@bogus.com)
Subject: Re: IPv6 traffic distribution
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF637@newserver.arneill-py.local>
Date: Fri, 29 Jul 2011 00:24:00 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <6E140BC3-0C38-453B-A557-A929EDC33A09@bogus.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com><4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>	<4E2EDF23.3060804@gmail.com><4E2F4491.30102@gmail.com>	<20110727023833.5C72D1232958@drugs.dv.isc.org>	<m1QlzXt-0001gSC@stereo.hq.phicoh.net>	<2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com>	<392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local>	<10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com>	<CAKD1Yr3gv=+HfEZMsU0enNh8OQbemQh6iRzpGHsnmr7OJrTcFg@mail.gmail.com>	<392CB277BC2EAE4FB83C1206954BA6CEF635@newserver.arneill-py.local>	<3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk><EMEW3|fa0511c175232cff9b9cb8310f081538n6RMCh03tjc|ecs.soton.ac.uk|3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk> <4E31F3C2.4000000@gmail.com> <392CB277BC2EAE4FB83C1206954BA6CEF637@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]); Fri, 29 Jul 2011 04:24:04 +0000 (UTC)
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 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, 29 Jul 2011 04:24:45 -0000

On Jul 28, 2011, at 11:41 PM, Michel Py wrote:
>>=20
>=20
> Same remarks as above, plus I don't see there anything that separates
> 6rd.

6rd is global unicast... there's nothing to discriminate it from any =
other native range.

> Michel.
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From narten@us.ibm.com  Thu Jul 28 21:53:10 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 2026621F87BC for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 21:53:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.568
X-Spam-Level: 
X-Spam-Status: No, score=-106.568 tagged_above=-999 required=5 tests=[AWL=0.031, 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 BZEHH-eD3xEA for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 21:53:09 -0700 (PDT)
Received: from e38.co.us.ibm.com (e38.co.us.ibm.com [32.97.110.159]) by ietfa.amsl.com (Postfix) with ESMTP id 2695F21F8799 for <ietf@ietf.org>; Thu, 28 Jul 2011 21:53:09 -0700 (PDT)
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e38.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p6SLG5GS015944 for <ietf@ietf.org>; Thu, 28 Jul 2011 15:16:05 -0600
Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p6T4r8lN130346 for <ietf@ietf.org>; Thu, 28 Jul 2011 22:53:08 -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 p6T4r8L4023297 for <ietf@ietf.org>; Thu, 28 Jul 2011 22:53:08 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p6T4r8l1023293 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 28 Jul 2011 22:53:08 -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 p6T4r7qC000778 for <ietf@ietf.org>; Fri, 29 Jul 2011 00:53:07 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p6T4r3m2000669 for ietf@ietf.org; Fri, 29 Jul 2011 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201107290453.p6T4r3m2000669@rotala.raleigh.ibm.com>
Date: Fri, 29 Jul 2011 00:53:03 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 04:53:10 -0000

Total of 337 messages in the last 7 days.
 
script run at: Fri Jul 29 00:53:02 EDT 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  7.72% |   26 |  7.40% |   171189 | w@1wt.eu
  6.82% |   23 |  6.76% |   156358 | marka@isc.org
  5.93% |   20 |  6.21% |   143702 | brian.e.carpenter@gmail.com
  4.75% |   16 |  5.58% |   129160 | moore@network-heretics.com
  4.45% |   15 |  3.32% |    76837 | mohta@necom830.hpcl.titech.ac.jp
  3.56% |   12 |  3.38% |    78258 | ibc@aliax.net
  2.08% |    7 |  2.34% |    54169 | cb.list6@gmail.com
  2.37% |    8 |  1.83% |    42401 | michel@arneill-py.sacramento.ca.us
  1.78% |    6 |  2.09% |    48459 | evnikita2@gmail.com
  2.08% |    7 |  1.55% |    35786 | mrex@sap.com
  1.78% |    6 |  1.65% |    38072 | dave@cridland.net
  1.48% |    5 |  1.74% |    40327 | tjc@ecs.soton.ac.uk
  1.19% |    4 |  1.88% |    43505 | lorenzo@google.com
  1.48% |    5 |  1.57% |    36246 | dhc2@dcrocker.net
  1.78% |    6 |  1.21% |    27925 | stpeter@stpeter.im
  1.48% |    5 |  1.21% |    27913 | sm@resistor.net
  1.48% |    5 |  1.14% |    26454 | mcr@sandelman.ca
  1.19% |    4 |  1.22% |    28162 | daedulus@btconnect.com
  1.19% |    4 |  1.02% |    23714 | pch-ietf@u-1.phicoh.com
  0.89% |    3 |  1.26% |    29124 | dendicott@gmail.com
  0.89% |    3 |  1.08% |    24873 | jeroen@unfix.org
  0.89% |    3 |  1.05% |    24378 | alexandru.petrescu@gmail.com
  0.89% |    3 |  1.05% |    24357 | jat@google.com
  1.19% |    4 |  0.73% |    16876 | jnc@mercury.lcs.mit.edu
  0.89% |    3 |  1.02% |    23588 | fielding@gbiv.com
  0.89% |    3 |  0.99% |    22885 | jhw@apple.com
  0.89% |    3 |  0.92% |    21192 | rbonica@juniper.net
  0.89% |    3 |  0.86% |    19823 | kivinen@iki.fi
  0.89% |    3 |  0.83% |    19211 | hsantos@isdg.net
  0.89% |    3 |  0.83% |    19188 | eburger-l@standardstrack.com
  0.59% |    2 |  1.02% |    23704 | lars.eggert@nokia.com
  0.89% |    3 |  0.69% |    15954 | amorris@amsl.com
  0.89% |    3 |  0.65% |    15017 | hannes.tschofenig@gmx.net
  0.59% |    2 |  0.92% |    21294 | bruce@callenish.com
  0.59% |    2 |  0.89% |    20564 | marshall.eubanks@gmail.com
  0.30% |    1 |  1.16% |    26786 | trejrco@gmail.com
  0.59% |    2 |  0.80% |    18532 | lionel.morand@orange-ftgroup.com
  0.59% |    2 |  0.79% |    18196 | shanna@juniper.net
  0.59% |    2 |  0.68% |    15710 | msk@cloudmark.com
  0.59% |    2 |  0.67% |    15446 | joelja@bogus.com
  0.59% |    2 |  0.62% |    14328 | carlberg@g11.org.uk
  0.59% |    2 |  0.56% |    13019 | dwing@cisco.com
  0.59% |    2 |  0.54% |    12493 | medel@globetel.com.ph
  0.59% |    2 |  0.53% |    12288 | rogerj@gmail.com
  0.59% |    2 |  0.52% |    12019 | ajs@anvilwalrusden.com
  0.59% |    2 |  0.52% |    11944 | gonzalo.camarillo@ericsson.com
  0.59% |    2 |  0.50% |    11502 | despres.remi@laposte.net
  0.59% |    2 |  0.49% |    11451 | vesely@tana.it
  0.30% |    1 |  0.79% |    18300 | david.black@emc.com
  0.59% |    2 |  0.49% |    11251 | dotis@mail-abuse.org
  0.59% |    2 |  0.48% |    11215 | scott.brim@gmail.com
  0.59% |    2 |  0.48% |    11106 | i.grok@comcast.net
  0.59% |    2 |  0.47% |    10921 | ggm+ietf@apnic.net
  0.59% |    2 |  0.47% |    10805 | gregw@intalio.com
  0.59% |    2 |  0.46% |    10649 | warren@kumari.net
  0.59% |    2 |  0.46% |    10555 | samirs.lists@gmail.com
  0.59% |    2 |  0.45% |    10465 | pch-v6ops@u-1.phicoh.com
  0.59% |    2 |  0.45% |    10402 | randy_presuhn@mindspring.com
  0.30% |    1 |  0.66% |    15374 | kathleen.moriarty@emc.com
  0.30% |    1 |  0.56% |    12865 | john_brzozowski@cable.comcast.com
  0.30% |    1 |  0.52% |    12030 | ted.ietf@gmail.com
  0.30% |    1 |  0.51% |    11825 | phbernard@gmail.com
  0.30% |    1 |  0.50% |    11648 | thierry.ernst@inria.fr
  0.30% |    1 |  0.49% |    11371 | yaronf.ietf@gmail.com
  0.30% |    1 |  0.43% |    10027 | trammell@tik.ee.ethz.ch
  0.30% |    1 |  0.40% |     9213 | spromano@unina.it
  0.30% |    1 |  0.39% |     9121 | dharkins@lounge.org
  0.30% |    1 |  0.38% |     8902 | olaf@nlnetlabs.nl
  0.30% |    1 |  0.38% |     8808 | gabriel.montenegro@microsoft.com
  0.30% |    1 |  0.38% |     8766 | narten@us.ibm.com
  0.30% |    1 |  0.37% |     8668 | rbarnes@bbn.com
  0.30% |    1 |  0.37% |     8647 | john.mann@monash.edu
  0.30% |    1 |  0.37% |     8640 | richard@shockey.us
  0.30% |    1 |  0.35% |     7994 | sidialimaiga@yahoo.fr
  0.30% |    1 |  0.33% |     7697 | john@jlc.net
  0.30% |    1 |  0.33% |     7677 | ted.lemon@nominum.com
  0.30% |    1 |  0.32% |     7451 | ynir@checkpoint.com
  0.30% |    1 |  0.32% |     7416 | paul.hoffman@vpnc.org
  0.30% |    1 |  0.32% |     7336 | jun@wide.ad.jp
  0.30% |    1 |  0.30% |     7039 | fred.l.templin@boeing.com
  0.30% |    1 |  0.30% |     6905 | drc@virtualized.org
  0.30% |    1 |  0.30% |     6828 | dworley@avaya.com
  0.30% |    1 |  0.29% |     6769 | housley@vigilsec.com
  0.30% |    1 |  0.29% |     6754 | mail@sabahattin-gucukoglu.com
  0.30% |    1 |  0.29% |     6702 | swallow@cisco.com
  0.30% |    1 |  0.28% |     6564 | otroan@employees.org
  0.30% |    1 |  0.28% |     6430 | samita.chakrabarti@ericsson.com
  0.30% |    1 |  0.28% |     6409 | tore.anderson@redpill-linpro.com
  0.30% |    1 |  0.27% |     6343 | ek@google.com
  0.30% |    1 |  0.27% |     6295 | touch@isi.edu
  0.30% |    1 |  0.26% |     5915 | turners@ieca.com
  0.30% |    1 |  0.25% |     5846 | rjsparks@nostrum.com
  0.30% |    1 |  0.25% |     5777 | chair@ietf.org
  0.30% |    1 |  0.25% |     5731 | jari.arkko@piuha.net
  0.30% |    1 |  0.25% |     5725 | mnot@mnot.net
  0.30% |    1 |  0.24% |     5645 | barryleiba@computer.org
  0.30% |    1 |  0.24% |     5641 | dean.willis@softarmor.com
  0.30% |    1 |  0.24% |     5630 | nico@cryptonector.com
  0.30% |    1 |  0.24% |     5594 | gih@apnic.net
  0.30% |    1 |  0.24% |     5537 | kfall@cs.berkeley.edu
  0.30% |    1 |  0.24% |     5508 | fred@cisco.com
  0.30% |    1 |  0.24% |     5483 | henk.uijterwaal@gmail.com
  0.30% |    1 |  0.24% |     5471 | faber@isi.edu
  0.30% |    1 |  0.24% |     5449 | hkaplan@acmepacket.com
  0.30% |    1 |  0.23% |     5434 | huitema@microsoft.com
  0.30% |    1 |  0.23% |     5284 | lberger@labn.net
  0.30% |    1 |  0.22% |     5073 | mark@townsley.net
  0.30% |    1 |  0.22% |     5046 | tnadeau@lucidvision.com
  0.30% |    1 |  0.22% |     5008 | gert@space.net
  0.30% |    1 |  0.21% |     4891 | martin.thomson@commscope.com
  0.30% |    1 |  0.21% |     4792 | alexey.melnikov@isode.com
  0.30% |    1 |  0.20% |     4707 | bortzmeyer@nic.fr
  0.30% |    1 |  0.20% |     4667 | derhoermi@gmx.net
  0.30% |    1 |  0.20% |     4663 | swmike@swm.pp.se
  0.30% |    1 |  0.20% |     4607 | sob@harvard.edu
  0.30% |    1 |  0.20% |     4516 | ietf@meetecho.com
  0.30% |    1 |  0.19% |     4435 | johnl@iecc.com
  0.30% |    1 |  0.18% |     4266 | nomcom-chair@ietf.org
  0.30% |    1 |  0.18% |     4252 | randy@psg.com
  0.30% |    1 |  0.18% |     4251 | glen@amsl.com
  0.30% |    1 |  0.18% |     4233 | nweis@verilan.com
--------+------+--------+----------+------------------------
100.00% |  337 |100.00% |  2313639 | Total

From johnl@iecc.com  Thu Jul 28 22:12:14 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 7B88C21F881C for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 22:12:14 -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.032, 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 TpafNawxEZO0 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 22:12:13 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 6948121F87BC for <ietf@ietf.org>; Thu, 28 Jul 2011 22:12:13 -0700 (PDT)
Received: (qmail 37251 invoked from network); 29 Jul 2011 05:12:11 -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=9182.4e32412b.k1107; bh=vpBj9QCyjddJdSqZGH3iIqZUOBGa3Y2A5zbF25gnQIg=; b=SzUZdCP3EmyDbdyvVjleJFpti8ENfmvSyDVzZHF2Au63cqbQd+i7OsDq/oVf0jAmqXaS73BghU9JZREX4BrXMXroUmLnoC7J3ZboQlDmE9kn4tjfcKq3ls4EfP1YpbHNM7upxqKCdkLGKBPa+4FQnr6X81nbX806FqnPhzZxxa4=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1) with (DHE-RSA-AES256-SHA encrypted) SMTP; 29 Jul 2011 05:11:49 -0000
Date: 29 Jul 2011 01:12:08 -0400
Message-ID: <alpine.BSF.2.00.1107290109250.20876@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "t.petch" <daedulus@btconnect.com>
Subject: Re: DKIM Signatures now being applied to IETF Email
In-Reply-To: <005d01cc4d44$3136eda0$4001a8c0@gateway.2wire.net>
References: <20110725171748.GA13506@amsl.com> <4E2FFFDF.2080601@ieca.com> <4E2DAF60.8030307@dcrocker.net> <005d01cc4d44$3136eda0$4001a8c0@gateway.2wire.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/signed; protocol="application/pkcs7-signature"; micalg=sha1; BOUNDARY="3825401791-1445651086-1311916331=:20876"
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 05:12:14 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3825401791-1445651086-1311916331=:20876
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

> But more importantly we have abolished the end-to-end principle.  If I am going
> to benefit from improved security on e-mail, I want to from the originator to
> me, not some half-way house giving a spurious impression of accuracy.

I can't help but be baffled at the lack of a PGP or S/MIME signature on 
your message.

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
--3825401791-1445651086-1311916331=:20876
Content-Type: APPLICATION/pkcs7-signature; name=smime.p7s
Content-Transfer-Encoding: BASE64
Content-Description: S/MIME Cryptographic Signature
Content-Disposition: attachment; filename=smime.p7s

MIIJIwYJKoZIhvcNAQcCoIIJFDCCCRACAQExCzAJBgUrDgMCGgUAMAsGCSqG
SIb3DQEHAaCCBiUwggYhMIIFCaADAgECAhA+xR7I39n15XT4ZYPptoVlMA0G
CSqGSIb3DQEBBQUAMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMCVVQxFzAV
BgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNU
IE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2
MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24g
YW5kIEVtYWlsMB4XDTEwMDgyMDAwMDAwMFoXDTExMDgyMDIzNTk1OVowgdUx
NTAzBgNVBAsTLENvbW9kbyBUcnVzdCBOZXR3b3JrIC0gUEVSU09OQSBOT1Qg
VkFMSURBVEVEMUYwRAYDVQQLEz1UZXJtcyBhbmQgQ29uZGl0aW9ucyBvZiB1
c2U6IGh0dHA6Ly93d3cuY29tb2RvLm5ldC9yZXBvc2l0b3J5MR8wHQYDVQQL
ExYoYykyMDAzIENvbW9kbyBMaW1pdGVkMRQwEgYDVQQDEwtKb2huIExldmlu
ZTEdMBsGCSqGSIb3DQEJARYOam9obmxAaWVjYy5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDDjT8poyoXt8e5ZgIbnypzSdHYr34wuQzt
2Yr/CZMo61F2tBBA9MbwWm94JDm0aVw/iSrTKzUVtRLH3vfiegbHiRgKk4FR
ecV2MxGGVijjdzjrgt74q4BVhzZ+NrFoPzp36wmWGSy6XMLmTRoLrUNRsffo
H5aSDxrxb3HysdLAtStGrWtjUxw0t1Mlfc5c78M5nOUtFOhpMrZ6Yh83+oxc
8aBhWyCgvmAOjFf8mO1xXgHK78mQUYKctXhEf4CZOhiQ4eowpswpxqalDOQC
FT/knkdUbjvJx/gGb6XHWHL7eLNNEHsMn88MOBR6Jxn3v/lOLNsycbNTYTa8
O8zjJMejAgMBAAGjggIQMIICDDAfBgNVHSMEGDAWgBSJgmd9xJ0mcABLtFBI
fN49rgRufTAdBgNVHQ4EFgQU/uQJi/hstmW7oeI6utA38NKgcRgwDgYDVR0P
AQH/BAQDAgWgMAwGA1UdEwEB/wQCMAAwIAYDVR0lBBkwFwYIKwYBBQUHAwQG
CysGAQQBsjEBAwUCMBEGCWCGSAGG+EIBAQQEAwIFIDBGBgNVHSAEPzA9MDsG
DCsGAQQBsjEBAgEBATArMCkGCCsGAQUFBwIBFh1odHRwczovL3NlY3VyZS5j
b21vZG8ubmV0L0NQUzCBpQYDVR0fBIGdMIGaMEygSqBIhkZodHRwOi8vY3Js
LmNvbW9kb2NhLmNvbS9VVE4tVVNFUkZpcnN0LUNsaWVudEF1dGhlbnRpY2F0
aW9uYW5kRW1haWwuY3JsMEqgSKBGhkRodHRwOi8vY3JsLmNvbW9kby5uZXQv
VVROLVVTRVJGaXJzdC1DbGllbnRBdXRoZW50aWNhdGlvbmFuZEVtYWlsLmNy
bDBsBggrBgEFBQcBAQRgMF4wNgYIKwYBBQUHMAKGKmh0dHA6Ly9jcnQuY29t
b2RvY2EuY29tL1VUTkFBQUNsaWVudENBLmNydDAkBggrBgEFBQcwAYYYaHR0
cDovL29jc3AuY29tb2RvY2EuY29tMBkGA1UdEQQSMBCBDmpvaG5sQGllY2Mu
Y29tMA0GCSqGSIb3DQEBBQUAA4IBAQBF+DKfxPqBmDs7hsQz7l9HEs1vHP9a
QeaKltcgGgRd8LV04m+ukjflWLVIyWgKq0X4uDypwN+Bdre6TO5OnFT2QWo7
5PoOGyVSAnegvkhKX4ENftYuWo5NiRcjMjlMcwymA8Dc3fYZEqYCuIyArVUC
Y5FAibthpZ/5Q39GoDJK7NbogOTGQIA9pkSYuDcnpsh5v6rUXtEnpvExC9q1
VBIk2acUI6q4eLtD+jVFuQwqS1D4UbAQ407m55/5Qprzolmmkvi7fOGDQhXS
6XXwmHh0TaplzEi2JcQtKA4TUaEkOWVgPjmNO6xOn1lZ1f5Skk5FLm/sA7v/
Jay3ey8HN2BjMYICxjCCAsICAQEwgcMwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRo
ZSBVU0VSVFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2Vy
dHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRo
ZW50aWNhdGlvbiBhbmQgRW1haWwCED7FHsjf2fXldPhlg+m2hWUwCQYFKw4D
AhoFAKCB2DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJ
BTEPFw0xMTA3MjkwNTEyMDhaMCMGCSqGSIb3DQEJBDEWBBSd9z1VMsSRisjT
73CPx92LOTjbMTB5BgkqhkiG9w0BCQ8xbDBqMAsGCWCGSAFlAwQBKjALBglg
hkgBZQMEARYwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMC
AgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDAN
BgkqhkiG9w0BAQEFAASCAQAkFKI9us+YUIpf5ZkXvS5fv5ODALKPg6e10wPq
G/l4y17ekRPR8kjSs5eIr9mwyl789ay49tIi57L1H4TWVyhqs3Lm0rf0nso3
3oeRgiV1f0srv0Lgn4UulxNyk9dMW/x7V/vw8F0p5k/TfjfdGsrQ8nob2FU7
25YYAnRPF4g2454x50uu6V3qiiM6F+ZaZqvE/YawVTt8wV+A2xkyrgB/TTWw
D9Go4cNlaVcS60kUTa0J48zUxKBMARPCtGkzXNCeeZd4YIKXPGEzfb2as1l/
xCxru2XgNk++1rpnUGYVJrqq3G7+Ii2B7Tv0usbvTRjtWvrz+kJiJGO13zlx
qItg

--3825401791-1445651086-1311916331=:20876--

From michel@arneill-py.sacramento.ca.us  Thu Jul 28 22:14:17 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 3298D21F8B06 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 22:14:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.143
X-Spam-Level: 
X-Spam-Status: No, score=-2.143 tagged_above=-999 required=5 tests=[AWL=0.122,  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 FJWvkttd0+07 for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 22:14:16 -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 4D76621F87D3 for <ietf@ietf.org>; Thu, 28 Jul 2011 22:14:16 -0700 (PDT)
Subject: RE: IPv6 traffic distribution
MIME-Version: 1.0
Date: Thu, 28 Jul 2011 22:14:15 -0700
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF638@newserver.arneill-py.local>
Content-class: urn:content-classes:message
In-Reply-To: <6E140BC3-0C38-453B-A557-A929EDC33A09@bogus.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-MimeOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: IPv6 traffic distribution
Thread-Index: AcxNp1qocgJOe6QASKyufSHVS74M5gABkxcg
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com><4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>	<4E2EDF23.3060804@gmail.com><4E2F4491.30102@gmail.com>	<20110727023833.5C72D1232958@drugs.dv.isc.org>	<m1QlzXt-0001gSC@stereo.hq.phicoh.net>	<2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com>	<392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local>	<10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com>	<CAKD1Yr3gv=+HfEZMsU0enNh8OQbemQh6iRzpGHsnmr7OJrTcFg@mail.gmail.com>	<392CB277BC2EAE4FB83C1206954BA6CEF635@newserver.arneill-py.local>	<3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk><EMEW3|fa0511c175232cff9b9cb8310f081538n6RMCh03tjc|ecs.soton.ac.uk|3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk> <4E31F3C2.4000000@gmail.com> <392CB277BC2EAE4FB83C1206954BA6CEF637@newserver.arneill-py.local> <6E140BC3-0C38-453B-A557-A929EDC33A09@bogus.com>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Joel Jaeggli" <joelja@bogus.com>
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 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, 29 Jul 2011 05:14:17 -0000

> Joel Jaeggli wrote:
> 6rd is global unicast... there's nothing to discriminate
> it from any other native range.

No. there is nothing in the current classification algorithm to
discriminate from any other native range. But it's not native, as it
has, among other things, the same reliance on IPv4 and the same MTU
issues than 6to4 as the core mechanism is based on 6to4 tunneling, or
encapsulation, or whatever else you want to call it.

Michel.


From pch-b2B3A6689@u-1.phicoh.com  Fri Jul 29 00:56:46 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 1E0F221F8799; Fri, 29 Jul 2011 00:56:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.799
X-Spam-Level: 
X-Spam-Status: No, score=-6.799 tagged_above=-999 required=5 tests=[AWL=1.200,  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 ieKG+cBJdQ3r; Fri, 29 Jul 2011 00:56: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 0BE4121F87C5; Fri, 29 Jul 2011 00:56:44 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #66) id m1QmhvM-0001gVC; Fri, 29 Jul 2011 09:56:00 +0200
Message-Id: <m1QmhvM-0001gVC@stereo.hq.phicoh.net>
To: Martin Rex <mrex@sap.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> 
From: Philip Homburg <pch-ietf@u-1.phicoh.com>
Sender: pch-b2B3A6689@u-1.phicoh.com
In-reply-to: Your message of "Fri, 29 Jul 2011 04:38:12 +0200 (MEST) ." <201107290238.p6T2cCLu021118@fs4113.wdf.sap.corp> 
Date: Fri, 29 Jul 2011 09:55:16 +0200
Cc: ibc@aliax.net, hybi@ietf.org, ietf@ietf.org, w@1wt.eu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 07:56:46 -0000

In your letter dated Fri, 29 Jul 2011 04:38:12 +0200 (MEST) you wrote:
>Mark Andrews wrote:
>> Martin Rex writes:
>> > Mark Andrews wrote:
>> > > 
>> > > More correctly it is try the first address and if that doesn't
>> > > connect in a short period (150...250ms) start a second connection
>> > > to the next address while continuing with the first.  If you have
>> > > more that 2 address you do something similar for the next one
>> > 
>> > Happy eyeballs means that a clients reaction to congestion is
>> > to perform an DoS attack, flood the network with additional
>> > connection requests and hammer the server with many additional
>> > half-open connections that will never actually get used.
>> 
>> It is not a DoS attack.  The client is almost certainly going to
>> make those connection attempts anyway if the path is congested
>> enough to cause the first connection attempt to fail.  The only
>> difference is the application gives up in 30 seconds rather than
>> 60 or 90 seconds by doing the attempts serially.
>
>150...250ms  ?!
>
>For a satellite link you already have started 3 parallel connects
>in non-congested(!) situations. 
>
>just some random IPv4 pings from my office (in germany)
>_without_congestion_:
>
>   ping  www.asus.com.tw            300-380ms
>   ping  south-america.pool.ntp.org 280-370ms
>   ping  oceania.pool.ntp.org       340-420ms
>   ping  www.eff.org                160-170ms
>   ping  www.ietf79.cn              330-450ms
>   ping  www.ietf76.jp              270-370ms
>
>So your approach is already hurting the network without congestion!

There are two ways to do Happy Eyeballs. A simple immediate solution that
works in most cases to use a fixed timeout value. In your case, you would
have to increase that value to a bit higher than 400ms. If HE was invented
a long time ago, then by now there could have been a parameter in DHCP
to let the network control this parameter.

The other way of doing HE is make it react to observed connect time. In that
case if you are regularly connecting to sites that are more than 400ms away
then the parameter will automatically increase to that value.

The proposal is currently discussed in v6ops and everybody seems to be happy 
with it. So a critical voice may help shape the proposal a bit.



From framefritti@gmail.com  Fri Jul 29 01:11:17 2011
Return-Path: <framefritti@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A77121F8ACE for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 01:11:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.467
X-Spam-Level: 
X-Spam-Status: No, score=-3.467 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_UNSUB18=0.131]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h6wKSXca4NgV for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 01:11:17 -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 D51B521F8ACC for <ietf@ietf.org>; Fri, 29 Jul 2011 01:11:16 -0700 (PDT)
Received: by qyk9 with SMTP id 9so3595398qyk.10 for <ietf@ietf.org>; Fri, 29 Jul 2011 01:10:48 -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=0ljVN3dWffCajgnwz7sunO5LyIerkZwlqoK5+kR+tio=; b=GbpWTBBHUj1QeeiXxoX68XXTAEf8ea2XQixuQIiewL7hucDvbTG2teAzbRDGdEKxck aYU3A1Saj6M5aQpDapnvG+F6GVaF6zAXxiSCzibBMmDt96hOICuZiPSRo2/usGTKhcna vPygVRcYPBhYm0ZV9wXdojPZi4pBsMuuvSSUQ=
MIME-Version: 1.0
Received: by 10.229.253.138 with SMTP id na10mr698596qcb.273.1311927048330; Fri, 29 Jul 2011 01:10:48 -0700 (PDT)
Received: by 10.229.31.11 with HTTP; Fri, 29 Jul 2011 01:10:48 -0700 (PDT)
In-Reply-To: <CAC4RtVCLayw1czVKnFG0WPHyL6dUSS0h6zcdSrMqqq9OcNFtrg@mail.gmail.com>
References: <F5833273385BB34F99288B3648C4F06F13512DF4A7@EXCH-C2.corp.cloudmark.com> <051e01cc4d64$493d3c40$dbb7b4c0$@com> <CAC4RtVCLayw1czVKnFG0WPHyL6dUSS0h6zcdSrMqqq9OcNFtrg@mail.gmail.com>
Date: Fri, 29 Jul 2011 10:10:48 +0200
Message-ID: <CABSMSPXU82RdN2gpoT9er6vQVBO3=w2akfZMRmsByhctcV355Q@mail.gmail.com>
Subject: Re: On attending BoFs
From: Riccardo Bernardini <framefritti@gmail.com>
To: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=90e6ba5bba03afdcf804a930d198
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 08:11:17 -0000

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

2011/7/28 Barry Leiba <barryleiba@computer.org>

> > You're going to ask attendees to self-identify as tourists and leave
> > the room?  Today's tourists may well become tomorrow's document
> > editors.
> ...
> > Let's just assign large enough rooms to BoFs and newly-formed WGs
> > so that the work can start in earnest.
>
> I agree.  If people are there paying attention, I want them there.
> Lots of people don't know whether they're going to commit to doing
> work until the end of the BoF, after they've heard all the stuff about
> problem statement, work scope, and proposed work items.
>

+1.  So far I came only to one IETF meeting.  At that time I attended (as a
"tourist," as you would call it) to a couple of BoF.  My motivation for
attending was that the BoF title sounded close enough to my interests and I
wanted to know something more about it. I could not say if I was willing to
be committed in contributing in the next-to-be WG by the title (and maybe a
brief abstract) only.  Keep also in mind that, although I participate as an
individual, I have an employer and I am not entirely free to decide if
contributing in some WG or not.  (If you are curious: it turned out that one
BoF was fairly orthogonal to my interests, while the other one was
sufficiently close so that I subscribed to the WG ML and spread the word
with few of my colleagues that are more interested in the matter).

Riccardo

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

<br><br><div class=3D"gmail_quote">2011/7/28 Barry Leiba <span dir=3D"ltr">=
&lt;<a href=3D"mailto:barryleiba@computer.org">barryleiba@computer.org</a>&=
gt;</span><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; You&#39;re going to ask attendees to self-identify a=
s tourists and leave<br>
&gt; the room? =A0Today&#39;s tourists may well become tomorrow&#39;s docum=
ent<br>
&gt; editors.<br>
</div>...<br>
<div class=3D"im">&gt; Let&#39;s just assign large enough rooms to BoFs and=
 newly-formed WGs<br>
&gt; so that the work can start in earnest.<br>
<br>
</div>I agree. =A0If people are there paying attention, I want them there.<=
br>
Lots of people don&#39;t know whether they&#39;re going to commit to doing<=
br>
work until the end of the BoF, after they&#39;ve heard all the stuff about<=
br>
problem statement, work scope, and proposed work items.<br></blockquote><di=
v><br></div><div>+1. =A0So far I came only to one IETF meeting. =A0At that =
time I attended (as a &quot;tourist,&quot; as you would call it) to a coupl=
e of BoF. =A0My motivation for attending was that the BoF title sounded clo=
se enough to my interests and I wanted to know something more about it. I c=
ould not say if I was willing to be committed in contributing in the next-t=
o-be WG by the title (and maybe a brief abstract) only. =A0Keep also in min=
d that, although I=A0participate as an individual, I have an employer and I=
 am not entirely free to decide if contributing in some WG or not. =A0(If y=
ou are curious: it turned out that one BoF was fairly orthogonal to my inte=
rests, while the other one was sufficiently close so that I subscribed to t=
he WG ML and spread the word with few of my=A0colleagues=A0that are more in=
terested in the matter).</div>
<div><br></div><div>Riccardo=A0</div></div>

--90e6ba5bba03afdcf804a930d198--

From pch-b2B3A6689@u-1.phicoh.com  Fri Jul 29 01:16:20 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 CE11F21F8828 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 01:16:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.339
X-Spam-Level: 
X-Spam-Status: No, score=-7.339 tagged_above=-999 required=5 tests=[AWL=1.260,  BAYES_00=-2.599, GB_I_LETTER=-2, 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 wM+cNEQLLXCy for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 01:16:20 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id 15AFE21F87E2 for <ietf@ietf.org>; Fri, 29 Jul 2011 01:16:20 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #66) id m1QmiEz-0001idC; Fri, 29 Jul 2011 10:16:17 +0200
Message-Id: <m1QmiEz-0001idC@stereo.hq.phicoh.net>
To: Cameron Byrne <cb.list6@gmail.com>
Subject: Re: "6to4 damages the Internet" (was Re: 
From: Philip Homburg <pch-ietf@u-1.phicoh.com>
Sender: pch-b2B3A6689@u-1.phicoh.com
In-reply-to: Your message of "Thu, 28 Jul 2011 18:55:04 -0700 ." <CAD6AjGRik+N0OObpO=AZE=gowS6bjMJmXF-Oz4w+Yh3-iQ0CVA@mail.gmail.com> 
Date: Fri, 29 Jul 2011 10:16:16 +0200
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 08:16:20 -0000

In your letter dated Thu, 28 Jul 2011 18:55:04 -0700 you wrote:
>On Jul 28, 2011 5:28 PM, "Martin Rex" <mrex@sap.com> wrote:
>> It would be so much easier if hosts on the public internet could
>> use one single IPv6 address that contains both, the IPv6 network prefix
>> and the IPv4 host address, and then let the network figure out whether
>> the connect goes through as IPv4 or IPv6 (for IPv6 clients).

In particular, if the remote address is encoded this way. If the host has
to chose between an IPv6 or IPv4 destination address then the protocol is
fixed.

I think that would have been a much better use of thse bits then simply
storing the ethernet address there.

But anyhow, it should be possible to do that with a destination option with is
then inspected by some middle box that makes a routing decision. But
that would require a lot of changes to retrofit it in todays operating
systems.

>This is largely (not entirely)  achieved with nat64 / dns64.

That would require the dns64 box to do destination selection. Possible, but
maybe also tricky to keep a dns resolver informed about the current state of
the network.



From lear@cisco.com  Fri Jul 29 01:46:10 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 B160421F8ACC for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 01:46:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.595
X-Spam-Level: 
X-Spam-Status: No, score=-110.595 tagged_above=-999 required=5 tests=[AWL=0.004, 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 iD0OG9MUgsWb for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 01:46:10 -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 CAB3C21F8515 for <ietf@ietf.org>; Fri, 29 Jul 2011 01:46:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=1116; q=dns/txt; s=iport; t=1311929169; x=1313138769; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=V8WwNAOluB20ZdOLskLcv/cdvjVv2SfMFq79y1dJ4go=; b=j1VtRfQa12ugkRF57Y0lsvlzK/qVKL0pxOZaIZ4uUdFoKgpb4Ub87SN/ whBH3toRqGLgYzmxjup1q6Fx2LPqtTyCY66z7KJjxV6HNXHDFnHxAfNa7 xqQJZlWaHOiMMBSxkVyDQ5jdL3eTP/mMx5HjapakHUUuSGlgquxVXuUj7 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqgHAAJyMk6Q/khL/2dsb2JhbAA1AQEBAQMUARRODQERDBoCBSACCwICCQMCAQIBAlEVAQ4BAR+EMJQBjxB3qmiNJJEkgSuEBoEQBJJ6kH8
X-IronPort-AV: E=Sophos;i="4.67,286,1309737600"; d="scan'208";a="45459386"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 29 Jul 2011 08:46:07 +0000
Received: from dhcp-10-61-101-196.cisco.com (dhcp-10-61-101-196.cisco.com [10.61.101.196]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p6T8k7KX030618; Fri, 29 Jul 2011 08:46:07 GMT
Message-ID: <4E327356.9090605@cisco.com>
Date: Fri, 29 Jul 2011 04:46:14 -0400
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Why the IESG needs to review everything...
References: <4E308D64.3030804@gmail.com> <4E30927D.50808@dcrocker.net>
In-Reply-To: <4E30927D.50808@dcrocker.net>
X-Enigmail-Version: 1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Dave CROCKER <dhc2@dcrocker.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: Fri, 29 Jul 2011 08:46:10 -0000

I don't have too much to say on whether the IESG is effective.  Our
standards production rate and the market uptake of same seems to speak
for itself.  I also don't have the numbers Dave is looking for either.

However, I would like to contribute my own anecdotal experience,
involving at least one draft from the person who kicked off this debate
(not you Dave or Brian).  I reviewed on behalf of the apps-area one of
the drafts he wrote and found a serious concern, and reported it.  He
ignored my review at his peril, and then complained when he got slapped
with a DISCUSS.  I don't know whether the AD based his DISCUSS on my
review or not, but clearly there was, at the very least, a substantial
disagreement.  What's particular egregious is that here we had a
cross-area expert review process that identified a problem that could
have been resolved without him wasting IESG time.  Instead, we are all
incompetent, and don't know what we're talking about, and the process is
broken.  It has not occurred to this guy that he might have made an
error in judgment.  In fact he made many.

Eliot

From vesely@tana.it  Fri Jul 29 02:09:32 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 52C2021F8ACC for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 02:09:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.451
X-Spam-Level: 
X-Spam-Status: No, score=-4.451 tagged_above=-999 required=5 tests=[AWL=-0.332, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, J_CHICKENPOX_15=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 R2QUDMptGuaq for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 02:09:31 -0700 (PDT)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 5AB4621F8867 for <ietf@ietf.org>; Fri, 29 Jul 2011 02:09:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1311930569; bh=gNp9l7X9ZLC4oaZ87HnNgiW2k0BOhRvIs8oL+aiBUhg=; l=926; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=BAmMv5zoVWIyWDWvdMpJrkoL8wGlWiNzklcXWUm1LRLEKA+ATJ4raKFdZboPNiRZ6 dBQmLVG9LV6r0t5A2gqAQWyzMtIDj+EWQv5bBHtR6W0h/EcWs4IWf2JHqW69LMxyMx iZsiNeDX5w53uroNCnhT/qDfztUziTNovnRVZcrs=
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; Fri, 29 Jul 2011 11:09:29 +0200 id 00000000005DC039.000000004E3278C9.00002485
Message-ID: <4E3278C9.1090104@tana.it>
Date: Fri, 29 Jul 2011 11:09:29 +0200
From: Alessandro Vesely <vesely@tana.it>
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: ietf@ietf.org
Subject: Re: DKIM Signatures now being applied to IETF Email
References: <20110725171748.GA13506@amsl.com> <4E2DAF60.8030307@dcrocker.net>	<4E2FFFDF.2080601@ieca.com> <005d01cc4d44$3136eda0$4001a8c0@gateway.2wire.net>
In-Reply-To: <005d01cc4d44$3136eda0$4001a8c0@gateway.2wire.net>
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, 29 Jul 2011 09:09:32 -0000

On 28/Jul/11 18:34, t.petch wrote:
> The minor point is that e-mails have just got yet bigger.  They are now 100-150%
> bigger than when first I started following the IETF

According to Nielsen's Law, network connection speeds double every 21
months.  DKIM is apparently using a quite reasonable fraction of that.

> But more importantly we have abolished the end-to-end principle.  If I am going
> to benefit from improved security on e-mail, I want to from the originator to
> me, not some half-way house giving a spurious impression of accuracy.

Most users don't want perfect accuracy into the mail system.  Not only
because of the burden of maintaining keys, but also for concerns about
freedom of speech, right to anonymity, possibility to play jokes, and
the like.  MSA endorsement allows all that, and still delivers some
responsibility by leveraging the trust between authors and their
mailbox providers.

From moore@network-heretics.com  Fri Jul 29 03:01: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 4314221F8788 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 03:01:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.669
X-Spam-Level: 
X-Spam-Status: No, score=-3.669 tagged_above=-999 required=5 tests=[AWL=-0.070, 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 hxr2tPyEDhZx for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 03:01: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 97DB621F8786 for <ietf@ietf.org>; Fri, 29 Jul 2011 03:01:01 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 6000420A67; Fri, 29 Jul 2011 06:01:00 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Fri, 29 Jul 2011 06:01: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=cI+t8cQrt5otWWyRyIZeSlkNU1A=; b=Sr KPlZvA61dpxCQlm0O4HYnqd7WiMvCzCpvYY460Hm8ERehhK7FAZfBaUvTgUDMsIw npBCRDHlklu0j5S4YWBd7OoaNkzXCCtcOF+1omC3nuXYfpiih5dPWWcfr4ZuhT21 JvktTNeFB9tAing9W6SRas1zOReSpC9BK2yE6qliY=
X-Sasl-enc: o7+ao8ytfRA+apQwZUUURs8mQSJAMiyOXwSFL5++Q27b 1311933660
Received: from [192.168.210.105] (modemcable114.145-70-69.static.videotron.ca [69.70.145.114]) by mail.messagingengine.com (Postfix) with ESMTPSA id CE75241525E; Fri, 29 Jul 2011 06:00:59 -0400 (EDT)
Subject: Re: IPv6 traffic distribution
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: <392CB277BC2EAE4FB83C1206954BA6CEF637@newserver.arneill-py.local>
Date: Fri, 29 Jul 2011 06:00:59 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <155C5C09-D85A-4106-BEEC-FE51E55C80E3@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com><4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>	<4E2EDF23.3060804@gmail.com><4E2F4491.30102@gmail.com>	<20110727023833.5C72D1232958@drugs.dv.isc.org>	<m1QlzXt-0001gSC@stereo.hq.phicoh.net>	<2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com>	<392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local>	<10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com>	<CAKD1Yr3gv=+HfEZMsU0enNh8OQbemQh6iRzpGHsnmr7OJrTcFg@mail.gmail.com>	<392CB277BC2EAE4FB83C1206954BA6CEF635@newserver.arneill-py.local>	<3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk><EMEW3|fa0511c175232cff9b9cb8310f081538n6RMCh03tjc|ecs.soton.ac.uk|3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk> <4E31F3C2.4000000@gmail.com> <392CB277BC2EAE4FB83C1206954BA6CEF637@newserver.arneill-py.local>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
X-Mailer: Apple Mail (2.1084)
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 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, 29 Jul 2011 10:01:02 -0000

On Jul 28, 2011, at 11:41 PM, Michel Py wrote:

> IMHO, the only valid stats we can gather are either from a large =
content
> provider (which is why Lorenzo's numbers are so interesting) or from a
> large eyeball ISP. Cisco, Juniper, Apple, the academia, the IETF, etc
> are NOT valid places to collect data.

I think all of the numbers are interesting, but the numbers shouldn't be =
separated from the conditions under which they were collected.  =20

It's reasonable to say "Google is now seeing X% 6to4 traffic" or "My =
native v6 enterprise network is seeing Y% 6to4 traffic."   What's not =
reasonable is to say that observations under one set of conditions are =
indicative of the whole network.   Even observations made at several =
points by a large transit carrier might not be indicative of conditions =
on the other side of the world.

It's also dubious to extrapolate from a few data points and call it a =
long term trend, because we're in a very early phase of v6 deployment =
(and v4 exhaustion), and there are many factors which could have a large =
but unpredictable influence on future use of IPv4 vs IPv6.

Keith


From moore@network-heretics.com  Fri Jul 29 03:07:34 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 C383021F8B15 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 03:07:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.663
X-Spam-Level: 
X-Spam-Status: No, score=-3.663 tagged_above=-999 required=5 tests=[AWL=-0.064, 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 gvjZqJ5c8yyf for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 03:07:34 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 23D2321F8AF6 for <ietf@ietf.org>; Fri, 29 Jul 2011 03:07:34 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 53FDB20E20; Fri, 29 Jul 2011 06:07:33 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Fri, 29 Jul 2011 06:07:33 -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=pUcwsx30q/7mUXNFc8W80mZamFQ=; b=Ws m3Qqg4uoAlguQZoI7Il5xz0n0lYepL7adbqAQ1kTpRx+uLiPUl+LkEx8+HNTSZyg jhfX4+V6+FfAwc3A9Kti0g4WFhSGa7ua451fVChHCCbHMbxU61/Y7FrD7QHpL6ln bJyxeUuhhWmgepRQt+gBvOhublIgE/mPHElK7oYMA=
X-Sasl-enc: wqFsOmr+PmpGl+aeACCXOg32C0ecgIqdsOXKFcxsbv+2 1311934053
Received: from [192.168.210.105] (modemcable114.145-70-69.static.videotron.ca [69.70.145.114]) by mail.messagingengine.com (Postfix) with ESMTPSA id CA2CF4153A8; Fri, 29 Jul 2011 06:07:32 -0400 (EDT)
Subject: Re: IPv6 traffic distribution
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: <392CB277BC2EAE4FB83C1206954BA6CEF638@newserver.arneill-py.local>
Date: Fri, 29 Jul 2011 06:07:32 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C027AD9D-E2AA-4E2A-92F1-2665A54C9A55@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com><4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>	<4E2EDF23.3060804@gmail.com><4E2F4491.30102@gmail.com>	<20110727023833.5C72D1232958@drugs.dv.isc.org>	<m1QlzXt-0001gSC@stereo.hq.phicoh.net>	<2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com>	<392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local>	<10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com>	<CAKD1Yr3gv=+HfEZMsU0enNh8OQbemQh6iRzpGHsnmr7OJrTcFg@mail.gmail.com>	<392CB277BC2EAE4FB83C1206954BA6CEF635@newserver.arneill-py.local>	<3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk><EMEW3|fa0511c175232cff9b9cb8310f081538n6RMCh03tjc|ecs.soton.ac.uk|3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk> <4E31F3C2.4000000@gmail.com> <392CB277BC2EAE4FB83C1206954BA6CEF637@newserver.arneill-py.local> <6E140BC3-0C38-453B-A557-A929EDC33A09@bogus.com> <392CB277BC2EAE4FB83C1206954BA6CEF 638@newserver.arneill-py.local>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
X-Mailer: Apple Mail (2.1084)
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 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: Fri, 29 Jul 2011 10:07:34 -0000

On Jul 29, 2011, at 1:14 AM, Michel Py wrote:

>> Joel Jaeggli wrote:
>> 6rd is global unicast... there's nothing to discriminate
>> it from any other native range.
>=20
> No. there is nothing in the current classification algorithm to
> discriminate from any other native range. But it's not native, as it
> has, among other things, the same reliance on IPv4 and the same MTU
> issues than 6to4 as the core mechanism is based on 6to4 tunneling, or
> encapsulation, or whatever else you want to call it.

Well, maybe.   One hopes that if an ISP chooses 6rd as a means to roll =
out v6 service to its customers, they've considered MTU issues and dealt =
with them as much as is feasible.   It's much easier to do that for TCP =
traffic than for say UDP.

All of these transition mechanisms introduce unpleasant  and undesirable =
corner cases.   =20

Keith


From dhc2@dcrocker.net  Fri Jul 29 03:18: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 6609021F8B7C for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 03:18:34 -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_15=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 YpXi+xkjBB7N for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 03:18:33 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id BC16921F8876 for <ietf@ietf.org>; Fri, 29 Jul 2011 03:18:33 -0700 (PDT)
Received: from [172.16.58.236] (modemcable252.155-70-69.static.videotron.ca [69.70.155.252]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p6TAIQCm001614 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 29 Jul 2011 03:18:33 -0700
Message-ID: <4E3288EE.9050201@dcrocker.net>
Date: Fri, 29 Jul 2011 06:18:22 -0400
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DKIM Signatures now being applied to IETF Email
References: <20110725171748.GA13506@amsl.com> <4E2DAF60.8030307@dcrocker.net> <4E2FFFDF.2080601@ieca.com> <005d01cc4d44$3136eda0$4001a8c0@gateway.2wire.net>
In-Reply-To: <005d01cc4d44$3136eda0$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 29 Jul 2011 03:18:33 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 10:18:34 -0000

On 7/28/2011 12:34 PM, t.petch wrote:
> But more importantly we have abolished the end-to-end principle.  If I am going
> to benefit from improved security on e-mail, I want to from the originator to
> me, not some half-way house giving a spurious impression of accuracy.


The end-to-end principle is often cited as an argument for any mechanism that is 
not the end-nodes.  I'm waiting for the day it is applied to a demand that every 
user's computer, tablet and smartphone be directly connected to every other one, 
so that we no longer suffer IP relaying by routers, since their presence 
violates the end-to-end principle.

With respect to DKIM, the problem with your concern is that you appear to 
misunderstand the function DKIM is performing.  Since that's well-documented, I 
suggest you review how it works and what it means.  In case that's too much 
effort, I suggest you take a look at:

    The Truth About DKIM
    <http://bbiw.net/presentations/DKIM%20Truth.pdf>

specifically slide 4.  The left hand side includes a short list of common 
mis-assumptions about DKIM's meaning, along with the one correct one.  See 
whether you know which is the right one.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From moore@network-heretics.com  Fri Jul 29 03:36: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 A9EBA21F86A5 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 03:36:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.357
X-Spam-Level: 
X-Spam-Status: No, score=-3.357 tagged_above=-999 required=5 tests=[AWL=-0.358, BAYES_00=-2.599, 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 pXmCgjVdR28I for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 03:36:24 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 0E92C21F861E for <ietf@ietf.org>; Fri, 29 Jul 2011 03:36:24 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 50D6C20B31; Fri, 29 Jul 2011 06:36:23 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute3.internal (MEProxy); Fri, 29 Jul 2011 06: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=Fp1e/32XbJ66L9JcWVIBuHwKrpw=; b=X3 JLv8iGkshlXQdjMib+k4qgUu5/h3xRmrWlndRNUzM6wdaAOPqw/hLvEaNoJvl5a+ Kqphk89tjkVLdAHq+f3RIOW/wiEa5mrUjtJCgko3Up5qGznbQWhn62Pa3UuFLmGn OOLM8fgqMzDW0WsLJIWwsmK+UQKASwTBn+Nr5bq74=
X-Sasl-enc: +WhCJmJz1fOIrDq3sWAH2g5bHjahkuDtBECvmSOr8TxW 1311935783
Received: from [192.168.210.105] (modemcable114.145-70-69.static.videotron.ca [69.70.145.114]) by mail.messagingengine.com (Postfix) with ESMTPSA id DE74A45642B; Fri, 29 Jul 2011 06:36:22 -0400 (EDT)
Subject: Re: DKIM Signatures now being applied to IETF Email
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: <4E3288EE.9050201@dcrocker.net>
Date: Fri, 29 Jul 2011 06:36:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F82A56EA-A44D-4587-952D-2B95B72885B1@network-heretics.com>
References: <20110725171748.GA13506@amsl.com> <4E2DAF60.8030307@dcrocker.net> <4E2FFFDF.2080601@ieca.com> <005d01cc4d44$3136eda0$4001a8c0@gateway.2wire.net> <4E3288EE.9050201@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1084)
Cc: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 10:36:24 -0000

On Jul 29, 2011, at 6:18 AM, Dave CROCKER wrote:

>=20
> On 7/28/2011 12:34 PM, t.petch wrote:
>> But more importantly we have abolished the end-to-end principle.  If =
I am going
>> to benefit from improved security on e-mail, I want to from the =
originator to
>> me, not some half-way house giving a spurious impression of accuracy.
>=20
>=20
> The end-to-end principle is often cited as an argument for any =
mechanism that is not the end-nodes.  I'm waiting for the day it is =
applied to a demand that every user's computer, tablet and smartphone be =
directly connected to every other one, so that we no longer suffer IP =
relaying by routers, since their presence violates the end-to-end =
principle.
>=20
> With respect to DKIM, the problem with your concern is that you appear =
to misunderstand the function DKIM is performing.  Since that's =
well-documented, I suggest you review how it works and what it means.  =
In case that's too much effort, I suggest you take a look at:
>=20
>   The Truth About DKIM
>   <http://bbiw.net/presentations/DKIM%20Truth.pdf>
>=20
> specifically slide 4.  The left hand side includes a short list of =
common mis-assumptions about DKIM's meaning, along with the one correct =
one.  See whether you know which is the right one.

DKIM is not my favorite protocol.  But it's not like there haven't been =
several efforts to define e2e authentication for email, including PEM, =
S/MIME, PGPMIME, and several others whose acronyms I'm too lazy to look =
up at the moment.    Implementations of email clients that support e2e =
authentication are not hard to find, and some people do use them.   But =
they've never been widely used.  I don't blame the DKIM proponents for =
wanting to try a different deployment model, for a different use case.

Keith


From ichiroumakino@gmail.com  Fri Jul 29 04:11:57 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 5BDF421F863A for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 04:11:57 -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 MEe+bhtFj7iG for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 04:11:56 -0700 (PDT)
Received: from mail-pz0-f53.google.com (mail-pz0-f53.google.com [209.85.210.53]) by ietfa.amsl.com (Postfix) with ESMTP id CC23421F85B8 for <ietf@ietf.org>; Fri, 29 Jul 2011 04:11:56 -0700 (PDT)
Received: by pzk6 with SMTP id 6so5818740pzk.26 for <ietf@ietf.org>; Fri, 29 Jul 2011 04:11:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=r3KLyHtTmN7wHCRTkU2K2zr2pmB43ehsZKeeGuXcIW0=; b=GTIHRpTPKU0J7EJpbXjtHl9iCguTW2TDdGMM/kcqVY141xboZTT3oepfNrjaIjbAAj zfyOKB/EuFGLNKswdfsyj9GQkfOpDZ3XcwXHOwtA3FcU/Gn7jZuoK4j42B/Lr9KFBucx uZwN7auw4GorKrf61fOYkEehBzo3jRklUMz7s=
Received: by 10.68.33.195 with SMTP id t3mr2037064pbi.458.1311937916527; Fri, 29 Jul 2011 04:11:56 -0700 (PDT)
Received: from sjc-vpn4-1289.cisco.com (128-107-239-233.cisco.com [128.107.239.233]) by mx.google.com with ESMTPS id e6sm2053340pbm.55.2011.07.29.04.11.54 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 29 Jul 2011 04:11:55 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Subject: Re: IPv6 traffic distribution
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF638@newserver.arneill-py.local>
Date: Fri, 29 Jul 2011 07:11:52 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <38D0CD11-F193-4D1B-951A-332C24AFBC7E@employees.org>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com><4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>	<4E2EDF23.3060804@gmail.com><4E2F4491.30102@gmail.com>	<20110727023833.5C72D1232958@drugs.dv.isc.org>	<m1QlzXt-0001gSC@stereo.hq.phicoh.net>	<2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com>	<392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local>	<10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com>	<CAKD1Yr3gv=+HfEZMsU0enNh8OQbemQh6iRzpGHsnmr7OJrTcFg@mail.gmail.com>	<392CB277BC2EAE4FB83C1206954BA6CEF635@newserver.arneill-py.local>	<3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk><EMEW3|fa0511c175232cff9b9cb8310f081538n6RMCh03tjc|ecs.soton.ac.uk|3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk> <4E31F3C2.4000000@gmail.com> <392CB277BC2EAE4FB83C1206954BA6CEF637@newserver.arneill-py.local> <6E140BC3-0C38-453B-A557-A929EDC33A09@bogus.com> <392CB277BC2EAE4FB83C1206954BA6CEF 638@newserver.arneill-py.local>
To: Michel Py <michel@arneill-py.sacramento.ca.us>
X-Mailer: Apple Mail (2.1084)
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 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, 29 Jul 2011 11:11:57 -0000

Michel,

>> Joel Jaeggli wrote:
>> 6rd is global unicast... there's nothing to discriminate
>> it from any other native range.
>=20
> No. there is nothing in the current classification algorithm to
> discriminate from any other native range. But it's not native, as it
> has, among other things, the same reliance on IPv4 and the same MTU
> issues than 6to4 as the core mechanism is based on 6to4 tunneling, or
> encapsulation, or whatever else you want to call it.

the 6rd MTU is under control of a single provider. the transport layer =
MTU can be set large enough to provide a 1500 byte MTU for IPv6.
I presume you are arguing that MPLS (6PE) is not native either?

cheers,
Ole



From joelja@bogus.com  Fri Jul 29 05:06:20 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 ACE7D21F8747 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 05:06:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.358
X-Spam-Level: 
X-Spam-Status: No, score=-102.358 tagged_above=-999 required=5 tests=[AWL=0.241, 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 IWoIUcDhVeAc for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 05:06:20 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id E123D21F8511 for <ietf@ietf.org>; Fri, 29 Jul 2011 05:06:19 -0700 (PDT)
Received: from dhcp-47c2.meeting.ietf.org (dhcp-47c2.meeting.ietf.org [130.129.71.194]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p6TC3bpx008612 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 29 Jul 2011 12:03:38 GMT (envelope-from joelja@bogus.com)
Subject: Re: IPv6 traffic distribution
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF638@newserver.arneill-py.local>
Date: Fri, 29 Jul 2011 08:03:36 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <D55ACDFC-4667-446E-871C-B480D7A93A1A@bogus.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com><4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>	<4E2EDF23.3060804@gmail.com><4E2F4491.30102@gmail.com>	<20110727023833.5C72D1232958@drugs.dv.isc.org>	<m1QlzXt-0001gSC@stereo.hq.phicoh.net>	<2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com>	<392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local>	<10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com>	<CAKD1Yr3gv=+HfEZMsU0enNh8OQbemQh6iRzpGHsnmr7OJrTcFg@mail.gmail.com>	<392CB277BC2EAE4FB83C1206954BA6CEF635@newserver.arneill-py.local>	<3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk><EMEW3|fa0511c175232cff9b9cb8310f081538n6RMCh03tjc|ecs.soton.ac.uk|3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk> <4E31F3C2.4000000@gmail.com> <392CB277BC2EAE4FB83C1206954BA6CEF637@newserver.arneill-py.local> <6E140BC3-0C38-453B-A557-A929EDC33A09@bogus.com> <392CB277BC2EAE4FB83C1206954BA6CE! F638@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]); Fri, 29 Jul 2011 12:03:39 +0000 (UTC)
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 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, 29 Jul 2011 12:06:20 -0000

agree but if you're trying to discriminate it by:

"This graph shows the daily unique queried reverse addresses by type."

you can't.

On Jul 29, 2011, at 1:14 AM, Michel Py wrote:

>> Joel Jaeggli wrote:
>> 6rd is global unicast... there's nothing to discriminate
>> it from any other native range.
> 
> No. there is nothing in the current classification algorithm to
> discriminate from any other native range. But it's not native, as it
> has, among other things, the same reliance on IPv4 and the same MTU
> issues than 6to4 as the core mechanism is based on 6to4 tunneling, or
> encapsulation, or whatever else you want to call it.
> 
> Michel.
> 
> 


From dhc2@dcrocker.net  Fri Jul 29 05:10:15 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 9047721F8B31 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 05:10:15 -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 MBSkdtKUt0Fy for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 05:10:14 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id B976021F8B0F for <ietf@ietf.org>; Fri, 29 Jul 2011 05:09:59 -0700 (PDT)
Received: from [130.129.85.251] (dhcp-55fb.meeting.ietf.org [130.129.85.251]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p6TC9Wf3005001 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Jul 2011 05:09:39 -0700
Message-ID: <4E32A2F8.4020400@dcrocker.net>
Date: Fri, 29 Jul 2011 08:09:28 -0400
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: DKIM Signatures now being applied to IETF Email
References: <20110725171748.GA13506@amsl.com> <4E2DAF60.8030307@dcrocker.net> <4E2FFFDF.2080601@ieca.com> <005d01cc4d44$3136eda0$4001a8c0@gateway.2wire.net> <4E3288EE.9050201@dcrocker.net> <F82A56EA-A44D-4587-952D-2B95B72885B1@network-heretics.com>
In-Reply-To: <F82A56EA-A44D-4587-952D-2B95B72885B1@network-heretics.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 29 Jul 2011 05:09: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: Fri, 29 Jul 2011 12:10:15 -0000

oh boy...

On 7/29/2011 6:36 AM, Keith Moore wrote:
>> The Truth About DKIM <http://bbiw.net/presentations/DKIM%20Truth.pdf>
>>
>> specifically slide 4.  The left hand side includes a short list of common
>> mis-assumptions about DKIM's meaning, along with the one correct one.  See
>> whether you know which is the right one.
>
> DKIM is not my favorite protocol.  But it's not like there haven't been
> several efforts to define e2e authentication for email, including PEM,
> S/MIME, PGPMIME, and several others whose acronyms I'm too lazy to look up at

Since DKIM's semantic is fundamentally different from PEM, S/MIME and OpenPGP, I 
don't know why you cited them.

For the typically uses of 'authentication' with respect to email, DKIM does not 
do authentication.  Please re-read the preceding sentence 10 times.

I really do suggest folks who have comments about DKIM first put some effort 
understanding what it does and does not do.

We've made it easy.  There are multiple documents discussion what it is and how 
to use it.


>  I don't blame the DKIM proponents for
> wanting to try a different deployment model, for a different use case.

DKIM is a different semantic, not just a different implementation.

d/


-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From ggm+ietf@apnic.net  Fri Jul 29 05:16:21 2011
Return-Path: <ggm+ietf@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD06621F8AFC for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 05:16:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.24
X-Spam-Level: 
X-Spam-Status: No, score=-101.24 tagged_above=-999 required=5 tests=[AWL=-0.139, BAYES_00=-2.599, HELO_DYNAMIC_DHCP=1.398, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BiVu8WQdRfkz for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 05:16:21 -0700 (PDT)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id 1A75821F8AF9 for <ietf@ietf.org>; Fri, 29 Jul 2011 05:16:21 -0700 (PDT)
Received: from dhcp-44e8.meeting.ietf.org (dhcp-44e8.meeting.ietf.org [130.129.68.232]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 25ADBB673D; Fri, 29 Jul 2011 22:16:17 +1000 (EST)
Subject: Re: IPv6 traffic distribution
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: George Michaelson <ggm+ietf@apnic.net>
In-Reply-To: <D55ACDFC-4667-446E-871C-B480D7A93A1A@bogus.com>
Date: Fri, 29 Jul 2011 08:16:09 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <91527B3C-A687-4750-A8AA-A5E9C0F3FDDC@apnic.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com><4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>	<4E2EDF23.3060804@gmail.com><4E2F4491.30102@gmail.com>	<20110727023833.5C72D1232958@drugs.dv.isc.org>	<m1QlzXt-0001gSC@stereo.hq.phicoh.net>	<2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com>	<392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local>	<10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com>	<CAKD1Yr3gv=+HfEZMsU0enNh8OQbemQh6iRzpGHsnmr7OJrTcFg@mail.gmail.com>	<392CB277BC2EAE4FB83C1206954BA6CEF635@newserver.arneill-py.local>	<3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk><EMEW3|fa0511c175232cff9b9cb8310f081538n6RMCh03tjc|ecs.soton.ac.uk|3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk> <4E31F3C2.4000000@gmail.com> <392CB277BC2EAE4FB83C1206954BA6CEF637@newserver.arneill-py.local> <6E140BC3-0C38-453B-A557-A929EDC33A09@bogus.com> <392CB277BC2EAE4FB83C1206954BA6CE! F638@newserver.arneill-py.local> <D55ACDFC-4667-446E-871C-B480D7A93A1A@bogus.com>
To: Joel Jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1084)
Cc: Michel Py <michel@arneill-py.sacramento.ca.us>, Tim Chown <tjc@ecs.soton.ac.uk>, 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, 29 Jul 2011 12:16:21 -0000

On 29/07/2011, at 8:03 AM, Joel Jaeggli wrote:

> agree but if you're trying to discriminate it by:
>=20
> "This graph shows the daily unique queried reverse addresses by type."
>=20
> you can't.
>=20


Very true Joel. I did, for a while, pattern match the 6rd prefix from =
Free.FR's declared ranges in RIPE whois but it was pointed out to me =
that dealing with one ISP like this skews things.

After all, other ISps also deploy 6rd, and Comcast do some kind of =
related work.

I can put in a 6rd line, if thats what people *want*

-G=

From dhc2@dcrocker.net  Fri Jul 29 05:19:54 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 693C521F8AFC for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 05:19:54 -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 PkgL4HHDXLzR for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 05:19:54 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0869921F8AF9 for <ietf@ietf.org>; Fri, 29 Jul 2011 05:19:54 -0700 (PDT)
Received: from [130.129.85.251] (dhcp-55fb.meeting.ietf.org [130.129.85.251]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p6TCJjeq005318 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Jul 2011 05:19:52 -0700
Message-ID: <4E32A55E.9070900@dcrocker.net>
Date: Fri, 29 Jul 2011 08:19:42 -0400
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Why the IESG needs to review everything...
References: <4E308D64.3030804@gmail.com> <201107272313.p6RNDMX9017678@fs4113.wdf.sap.corp> <6.2.5.6.2.20110727233441.04c41030@resistor.net> <4E31EFC1.8070607@gmail.com> <6.2.5.6.2.20110728163352.0a2bb920@resistor.net>
In-Reply-To: <6.2.5.6.2.20110728163352.0a2bb920@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 29 Jul 2011 05:19:53 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 12:19:54 -0000

On 7/28/2011 7:54 PM, SM wrote:
> At 04:24 PM 7/28/2011, Brian E Carpenter wrote:
>> Er, no. By definition, it's correct until we update RFC 2026.
>
> Quoting the Status of this memo section from RFC 6305, RFC 6308, RFC 6319 and
> RFC 6331 which are Informational and from the IETF Stream:
>
> "This document is a product of the Internet Engineering Task Force
> (IETF). It represents the consensus of the IETF community.


SM is correctly detecting some problematic inconsistencies in our language.

We do not use adequately clear and distinctive language to distinguish between:

    *  IETF consensus used to approve standards/bcp,

    *  IETF consensus used to approve other documents through the IETF

    *  Independent Informational and Experimental submissions that are published 
/without/ IETF approval.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From mohta@necom830.hpcl.titech.ac.jp  Fri Jul 29 05:21:32 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 023BD21F8ADC for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 05:21:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.079
X-Spam-Level: 
X-Spam-Status: No, score=-0.079 tagged_above=-999 required=5 tests=[AWL=0.011,  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 HnEAchC9SsDk for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 05:21:31 -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 394C821F8A6C for <ietf@ietf.org>; Fri, 29 Jul 2011 05:21:31 -0700 (PDT)
Received: (qmail 61946 invoked from network); 29 Jul 2011 12:42:04 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 29 Jul 2011 12:42:04 -0000
Message-ID: <4E32A568.5040000@necom830.hpcl.titech.ac.jp>
Date: Fri, 29 Jul 2011 21:19:52 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: "6to4 damages the Internet" (was Re:
References: <m1QmiEz-0001idC@stereo.hq.phicoh.net>
In-Reply-To: <m1QmiEz-0001idC@stereo.hq.phicoh.net>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 12:21:32 -0000

Philip Homburg wrote:

> I think that would have been a much better use of thse bits then simply
> storing the ethernet address there.

IPv6 address was (when it was SIP) and should be 8B, but extended
to be 16B to store ethernet address with wrong reasoning of RFC1715
only to make IPv6 inoperational.

At that time, it was 10B+6B, but as I pointed it out that IEEE1394
MAC is 8B long, it became 8B+8B.

> But anyhow, it should be possible to do that with a destination option with is
> then inspected by some middle box that makes a routing decision. But
> that would require a lot of changes to retrofit it in todays operating
> systems.

That's no different from legacy NAT to violate the end to end
principle. For example, just as legacy NAT, transport check sum depends
on actually used address family and address. Thus, transport
check sum must be recalculated by the middle box which changes
address family.

> That would require the dns64 box to do destination selection. Possible, but
> maybe also tricky to keep a dns resolver informed about the current state of
> the network.

That's guaranteed to be impossible by the end to end argument:

   The function in question can completely and correctly be
   implemented only with the knowledge and help of the
   application standing at the end points of the communication
   system. Therefore, providing that questioned function as a
   feature of the communication system itself is not possible.

Destination address selection is the function in question and
complete and correct implementation by middle boxes is just
impossible.

The only approach for the address selection function is to do
it at the end systems using "knowledge and help" of the end
systems, which requires end systems have "knowledge" on
default free global routing tables.

						Masataka Ohta

From john@jlc.net  Fri Jul 29 05:22:08 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 3AD4121F8B75 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 05:22:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.578
X-Spam-Level: 
X-Spam-Status: No, score=-106.578 tagged_above=-999 required=5 tests=[AWL=0.021, 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 jR9Nw5iDXzjq for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 05:22:07 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 9D8BE21F8B6D for <ietf@ietf.org>; Fri, 29 Jul 2011 05:22:07 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 39A2633C25; Fri, 29 Jul 2011 08:22:07 -0400 (EDT)
Date: Fri, 29 Jul 2011 08:22:07 -0400
From: John Leslie <john@jlc.net>
To: SM <sm@resistor.net>
Subject: Re: Why the IESG needs to review everything...
Message-ID: <20110729122207.GT57285@verdi>
References: <4E308D64.3030804@gmail.com> <201107272313.p6RNDMX9017678@fs4113.wdf.sap.corp> <6.2.5.6.2.20110727233441.04c41030@resistor.net> <4E31EFC1.8070607@gmail.com> <6.2.5.6.2.20110728163352.0a2bb920@resistor.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6.2.5.6.2.20110728163352.0a2bb920@resistor.net>
User-Agent: Mutt/1.4.1i
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 12:22:08 -0000

SM <sm@resistor.net> wrote:
> At 04:24 PM 7/28/2011, Brian E Carpenter wrote:
>> On 2011-07-28 18:45, SM wrote:
>>> At 04:13 PM 7/27/2011, Martin Rex wrote:
>>> 
>>>> According to rfc2026:
>>>>
>>>>    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.  [...]
>>>  
>>> The above is incorrect.
>>   
>> Er, no. By definition, it's correct until we update RFC 2026.
> 
> Quoting the Status of this memo section from RFC 6305, RFC 6308, RFC 
> 6319 and RFC 6331 which are Informational and from the IETF Stream:
> 
>   "This document is a product of the Internet Engineering Task Force
>    (IETF).  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)."
> 
> Although it is, by definition, correct until RFC 2026 is updated, RFC 
> 5741 is currently being used for the boilerplate in RFCs.

   This actually caught me by surprise, but it is accurate.

   RFC 5741, status Informational, specifies boilerplate for
Informational RFCs. The operative text is in Section 3.2.2:
" 
" The text that follows is stream dependent -- these are suggested
" initial values and may be updated by stream definition document
" updates.
" 
" IETF Stream:
"    "This document is a product of the Internet Engineering Task Force
"    (IETF)."
" 
"    If there has been an IETF consensus call per IETF process, an
"    additional sentence should be added:
" 
"       "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)."
" 
"    If there has not been such a consensus call, then this simply
"    reads:
" 
"       "It has been approved for publication by the Internet
"       Engineering Steering Group (IESG)."

   Frankly, I am not happy with this. An Informational track document
has effectively over-ruled RFC 2026, a BCP status document -- and
gone on to say that RFC 2026 may be further overruled by "stream
definition document updates" (whatever that may mean).

   I _much_ prefer the RFC 2026 definition of Informational (and I
don't believe they should require extensive IESG scrutiny).

   (BTW, I wonder to what extent our current repetition of the
argument about the IESG filing too many DISCUSSes is in reaction to
their scrutiny of Informational track documents.)

   I don't have time today to research to what extent Informational
track RFCs have actually received "an IETF consensus call per IETF
process". Perhaps somebody else would like to respond on that...

--
John Leslie <john@jlc.net>

From despres.remi@laposte.net  Fri Jul 29 05:52:29 2011
Return-Path: <despres.remi@laposte.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18E8421F8BB5 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 05:52:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.882
X-Spam-Level: 
X-Spam-Status: No, score=-1.882 tagged_above=-999 required=5 tests=[AWL=0.067,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sVvjJrqn0Bqe for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 05:52:27 -0700 (PDT)
Received: from smtp22.services.sfr.fr (smtp22.services.sfr.fr [93.17.128.10]) by ietfa.amsl.com (Postfix) with ESMTP id 193A521F8B99 for <ietf@ietf.org>; Fri, 29 Jul 2011 05:52:26 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2221.sfr.fr (SMTP Server) with ESMTP id 45194700008D; Fri, 29 Jul 2011 14:52:26 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2221.sfr.fr (SMTP Server) with ESMTP id 7A51E7000081; Fri, 29 Jul 2011 14:52:25 +0200 (CEST)
X-SFR-UUID: 20110729125225501.7A51E7000081@msfrf2221.sfr.fr
Subject: Re: 6to4v2 (as in ripv2)? 
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF625@newserver.arneill-py.local>
Date: Fri, 29 Jul 2011 14:52:24 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <4E656E6D-EA61-48E7-BF06-6F038777FA70@laposte.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com>	<4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net><4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com><72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com> <5A600744-8605-46D3-82B2-C3C30E30E4AC@network-heretics.com> <392CB277BC2EAE4FB83C1206954BA6CEF625@newserver.arneill-py.local>
To: Michel Py <michel@arneill-py.sacramento.ca.us>
X-Mailer: Apple Mail (2.1084)
Cc: 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, 29 Jul 2011 12:52:29 -0000

Le 27 juil. 2011 =E0 17:29, Michel Py a =E9crit :
> ...
>>> Fred Baker wrote:
>>> Actually, I think one could argue pretty
>>> effectively that 6rd is 6to4-bis.
>=20
> Indeed, and it also is a transition mechanism for the very same =
reasons
> that 6to4 is.
>=20
>=20
>> Keith Moore wrote:
>> only if you're confused about the use cases for each.
>=20
> Even if there are different use cases indeed (as you explained it very
> well yourself)

> you can't deny that 6rd is 6to4-bis.

Oh, yes indeed, on can!
(Depending, of course on what you mean with 6to4-bis, but no one can be =
sure what you mean).

- 6to4 delivers native IPv6 prefixes to customer sites, which 6to4 =
doesn't.
- 6to4 has known operational problems, not 6rd.

> The difference is in
> who configures/manages it,

> not how it works;

See above.

> the 6rd code base is a
> superset of the 6to4.

Although it has been convenient to deploy 6rd starting with existing =
6to4 code, one can write 6rd code that doesn't work for 6to4.

> The difference is more a matter of network design
> than core protocol.

It is a matter of clean IPv6 service, transparent to users, vs service =
for experts who know what they are doing.

RD



>=20
> Michel.
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf



From despres.remi@laposte.net  Fri Jul 29 05:57:45 2011
Return-Path: <despres.remi@laposte.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1940821F8A6C for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 05:57:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.883
X-Spam-Level: 
X-Spam-Status: No, score=-1.883 tagged_above=-999 required=5 tests=[AWL=0.066,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m9sTchThVQMj for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 05:57:44 -0700 (PDT)
Received: from smtp22.services.sfr.fr (smtp22.services.sfr.fr [93.17.128.10]) by ietfa.amsl.com (Postfix) with ESMTP id 5C67E21F88DD for <ietf@ietf.org>; Fri, 29 Jul 2011 05:57:44 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2221.sfr.fr (SMTP Server) with ESMTP id B66907000088; Fri, 29 Jul 2011 14:57:43 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2221.sfr.fr (SMTP Server) with ESMTP id 5F0A17000083; Fri, 29 Jul 2011 14:57:43 +0200 (CEST)
X-SFR-UUID: 20110729125743389.5F0A17000083@msfrf2221.sfr.fr
Subject: Re: draft-ietf-v6ops-6to4-to-historic  (yet again)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <4E2FABEA.2030905@redpill-linpro.com>
Date: Fri, 29 Jul 2011 14:57:42 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E3733F79-40CB-4DCD-A05D-E48777A0898B@laposte.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2FABEA.2030905@redpill-linpro.com>
To: Tore Anderson <tore.anderson@redpill-linpro.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: Fri, 29 Jul 2011 12:57:45 -0000

Le 27 juil. 2011 =E0 08:10, Tore Anderson a =E9crit :

> * Ronald Bonica
>=20
>> After some discussion, the IESG is attempting to determine whether =
there is IETF consensus to do the following:
>>=20
>> - add a new section to draft-ietf-v6ops-6to4-to-historic
>> - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL
>>=20
>> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 =
and convert their status to HISTORIC. It will also contain a new section =
describing what it means for RFCs 3056 and 3068 to be classified as =
HISTORIC. The new section will say that:
>>=20
>> - 6-to-4 should not be configured by default on any implementation =
(hosts, cpe routers, other)
>> - vendors will decide whether/when 6-to-4 will be removed from =
implementations. Likewise, operators will decide whether/when 6-to-4 =
relays will be removed from their networks. The status of RFCs 3056 and =
3068 should not be interpreted as a recommendation to remove 6-to-4 at =
any particular time.
>>=20
>>=20
>> draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While it =
clarifies the meaning of "HISTORIC" in this particular case, it does not =
set a precedent for any future case.
>=20
> I support this approach.

Suggestion to make the two RFC Experimental has been made, and received =
some support.
I haven't seen objections tho this compromise approach.
Are there some?

RD

>=20
> Best regards,
> --=20
> Tore Anderson
> Redpill Linpro AS - http://www.redpill-linpro.com
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf



From alexandru.petrescu@gmail.com  Fri Jul 29 06:03:04 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 1AB5421F8B82 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 06:03:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.569
X-Spam-Level: 
X-Spam-Status: No, score=-3.569 tagged_above=-999 required=5 tests=[AWL=0.030,  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 OYdDqEVXoB2E for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 06:03:03 -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 58C2021F8AFE for <ietf@ietf.org>; Fri, 29 Jul 2011 06:03:03 -0700 (PDT)
Received: by qyk9 with SMTP id 9so3728133qyk.10 for <ietf@ietf.org>; Fri, 29 Jul 2011 06:03:02 -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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=OKpOhobdOvYiRYYgawgbZQNEJVQOdIEWAWRahK7X7c0=; b=S54rmMenqxTqZ0pkN8kbh36nVBqFUVK7F69XxorBRjA60c9PTXLaRQ8UhiwX+1Prke MDZDxaM9xeYhWFTi2TdP+aWDuU7JSnBHPU/LR3ENjE9zdlmTWT/p4fTydzX/R4ADnmRr l+6S80gWApRW4IJw+BATneYtMuyukMj3YH1lI=
Received: by 10.224.209.73 with SMTP id gf9mr954221qab.362.1311944582796; Fri, 29 Jul 2011 06:03:02 -0700 (PDT)
Received: from [127.0.0.1] (dhcp-150a.meeting.ietf.org [130.129.21.10]) by mx.google.com with ESMTPS id bh11sm1038411qab.10.2011.07.29.06.02.45 (version=SSLv3 cipher=OTHER); Fri, 29 Jul 2011 06:02:45 -0700 (PDT)
Message-ID: <4E32AF70.3080901@gmail.com>
Date: Fri, 29 Jul 2011 15:02:40 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-gundavelli-v6ops-pmipv6-address-reservations-00.txt> (Reserved IPv6 Interface Identifier for Proxy Mobile IPv6) to Informational RFC
References: <20110729121436.14048.14658.idtracker@ietfa.amsl.com>
In-Reply-To: <20110729121436.14048.14658.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 13:03:04 -0000

I do think that pmipv6 has some issues about how it does mag-mn
interface.  One solution to one issue may be this reserved iid.

Is this updating the stds track rfc5453 "reserved iids"?

Does this mean that pmipv6 spec is to be updated? (eg say that its RAs
are src'ed with an address formed from this iid?)

I think that even though an iid is reserved for mag, the mn must still
resolve (ns/na) the addresses ip-mac hence the utility of the uniqueness
of a fe80::iid throughout the pmip domain may be questionable.

I think it should be stated whether this is for shared links (wifi) or
ptp links (3g) this latter doesn't have many problems w/ pmip.

Other solutions for this mn-mag pmip problem are possible and
implementation exists.

Alex

Le 29/07/2011 14:14, The IESG a écrit :
>
> The IESG has received a request from an individual submitter to
> consider the following document: - 'Reserved IPv6 Interface
> Identifier for Proxy Mobile IPv6'
> <draft-gundavelli-v6ops-pmipv6-address-reservations-00.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-08-26.
> 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
>
>
> Proxy Mobile IPv6 [RFC5213] requires all the mobile access gateways
> to use a fixed link-local and link-layer addresses on any of its
> access links that it shares with the mobile nodes.  This was
> intended to ensure a mobile node does not detect any change with
> respect to its layer-3 attachment even after it roams from one mobile
> access gateway to another.  In the absence of any reserved addresses
> for this use, it requires coordination across vendors and the manual
> configuration of these addresses on all the mobility elements in a
> Proxy Mobile IPv6 domain.  This document attempts to simplify this
> operational requirement by making reservation for special addresses
> that can be used for this purpose.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-gundavelli-v6ops-pmipv6-address-reservations/
>
>  IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-gundavelli-v6ops-pmipv6-address-reservations/
>
>
>
> 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


From chris.newman@oracle.com  Fri Jul 29 06:14:41 2011
Return-Path: <chris.newman@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9FF221F8BCF for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 06:14:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.466
X-Spam-Level: 
X-Spam-Status: No, score=-105.466 tagged_above=-999 required=5 tests=[AWL=-0.489, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, HELO_MISMATCH_COM=0.553, 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 kVBzrnUdu4Kd for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 06:14:41 -0700 (PDT)
Received: from sca-ea-mail-1.sun.com (sca-ea-mail-1.Sun.COM [192.18.43.24]) by ietfa.amsl.com (Postfix) with ESMTP id 7B81421F8BCE for <ietf@ietf.org>; Fri, 29 Jul 2011 06:14:41 -0700 (PDT)
Received: from brmsunmail1-sfbay.uk.sun.com ([10.79.11.100]) by sca-ea-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id p6TDEZOs010173; Fri, 29 Jul 2011 13:14:36 GMT
Received: from gotmail.us.oracle.com (gotmail.us.oracle.com [10.133.152.174]) by brmsunmail1-sfbay.uk.sun.com (8.14.4+Sun/8.14.4/ENSMAIL,v2.4) with ESMTP id p6TDEYj0016716; Fri, 29 Jul 2011 13:14:35 GMT
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-disposition: inline
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Received: from [10.159.49.225] (dhcp-rmdc-twvpn-2-vpnpool-10-159-49-225.vpn.oracle.com [10.159.49.225]) by gotmail.us.oracle.com (Oracle Communications Messaging Exchange Server 7u5-4.01 64bit (built May 4 2011)) with ESMTPA id <0LP30071NJG52H00@gotmail.us.oracle.com>; Fri, 29 Jul 2011 06:14:34 -0700 (PDT)
Date: Thu, 28 Jul 2011 22:28:06 -0400
From: Chris Newman <chris.newman@oracle.com>
To: Jari Arkko <jari.arkko@piuha.net>, IETF Discussion <ietf@ietf.org>
Subject: Re: draft-housley-two-maturity-levels
Message-id: <2715CFEEA3358D18DDA30559@96B2F16665FF96BAE59E9B90>
In-reply-to: <4E30872E.1090009@piuha.net>
References: <4E30872E.1090009@piuha.net>
X-Mailer: Mulberry/4.0.8 (Mac OS X)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 13:14:41 -0000

I have read version 08 and support this proposal.

		- Chris

--On July 27, 2011 17:46:22 -0400 Jari Arkko <jari.arkko@piuha.net> wrote:
> Here's the link:
>
>   http://tools.ietf.org/html/draft-housley-two-maturity-levels


From despres.remi@laposte.net  Fri Jul 29 06:19:47 2011
Return-Path: <despres.remi@laposte.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A66E21F8AD9; Fri, 29 Jul 2011 06:19:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.885
X-Spam-Level: 
X-Spam-Status: No, score=-1.885 tagged_above=-999 required=5 tests=[AWL=0.064,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1gzBchC3or9Q; Fri, 29 Jul 2011 06:19:47 -0700 (PDT)
Received: from smtp22.services.sfr.fr (smtp22.services.sfr.fr [93.17.128.10]) by ietfa.amsl.com (Postfix) with ESMTP id DD14D21F8B29; Fri, 29 Jul 2011 06:19:46 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2221.sfr.fr (SMTP Server) with ESMTP id 43212700008E; Fri, 29 Jul 2011 15:19:46 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2221.sfr.fr (SMTP Server) with ESMTP id DD0277000083; Fri, 29 Jul 2011 15:19:43 +0200 (CEST)
X-SFR-UUID: 20110729131943905.DD0277000083@msfrf2221.sfr.fr
Subject: Re: [v6ops] Make 6to4 Experimental (was6to4v2 (as in ripv2)?)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <20110727161445.1C00A18C0CB@mercury.lcs.mit.edu>
Date: Fri, 29 Jul 2011 15:19:43 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <65EB9DA2-255C-47F5-B6BB-EBE2B8BC219D@laposte.net>
References: <20110727161445.1C00A18C0CB@mercury.lcs.mit.edu>
To: IETF discussion list <ietf@ietf.org>, v6ops v6ops WG <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 13:19:47 -0000

+1

IMHO, it does make a lot of sense.
(I made a similar comment before reading this one)-.

Regards,
RD

Le 27 juil. 2011 =E0 18:14, Noel Chiappa a =E9crit :

>> From: Philip Homburg <pch-v6ops@u-1.phicoh.com>
>=20
>> I think it would be quite weird to keep 6to4 at standards track just =
to
>> prevent some vendors from dropping 6to4 support.
>=20
> There have been suggestions that it might be more appropriate to =
reclassify
> it as Experimental, and I think that makes a lot of sense - as you =
correctly
> (IMO) point out, due to its issues 6to4 is not really appropriate for
> standards track (at least, in its current form).
>=20
> 	Noel
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf



From daedulus@btconnect.com  Fri Jul 29 06:25:41 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 C216821F8507 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 06:25:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level: 
X-Spam-Status: No, score=-2.199 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_15=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 z1iUdV-raIB6 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 06:25:41 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr06.btconnect.com [213.123.26.184]) by ietfa.amsl.com (Postfix) with ESMTP id CE4BC21F8506 for <ietf@ietf.org>; Fri, 29 Jul 2011 06:25:40 -0700 (PDT)
Received: from host109-153-78-164.range109-153.btcentralplus.com (HELO pc6) ([109.153.78.164]) by c2beaomr06.btconnect.com with SMTP id EAC02866; Fri, 29 Jul 2011 14:25:30 +0100 (BST)
Message-ID: <006101cc4dea$2c9bdd40$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: <dcrocker@bbiw.net>, "ietf" <ietf@ietf.org>
References: <20110725171748.GA13506@amsl.com> <4E2DAF60.8030307@dcrocker.net><4E2FFFDF.2080601@ieca.com><005d01cc4d44$3136eda0$4001a8c0@gateway.2wire.net> <4E3288EE.9050201@dcrocker.net>
Subject: Re: DKIM Signatures now being applied to IETF Email
Date: Fri, 29 Jul 2011 14:22:15 +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.0A0B0303.4E32B4CA.0029, actions=TAG
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.7.29.122715:17:7.586, ip=109.153.78.164, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __TO_NO_NAME, __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, __CP_URI_IN_BODY, __STOCK_PHRASE_7, __INT_PROD_COMP, 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=c2beaomr06.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0206.4E32B4CB.014B,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: Fri, 29 Jul 2011 13:25:41 -0000

---- Original Message -----
From: "Dave CROCKER" <dhc2@dcrocker.net>
To: <ietf@ietf.org>
Sent: Friday, July 29, 2011 12:18 PM
>
> On 7/28/2011 12:34 PM, t.petch wrote:
> > But more importantly we have abolished the end-to-end principle.  If I am
going
> > to benefit from improved security on e-mail, I want to from the originator
to
> > me, not some half-way house giving a spurious impression of accuracy.
>
> The end-to-end principle is often cited as an argument for any mechanism that
is
> not the end-nodes.  I'm waiting for the day it is applied to a demand that
every
> user's computer, tablet and smartphone be directly connected to every other
one,
> so that we no longer suffer IP relaying by routers, since their presence
> violates the end-to-end principle.
>
> With respect to DKIM, the problem with your concern is that you appear to
> misunderstand the function DKIM is performing.  Since that's well-documented,
I
> suggest you review how it works and what it means.  In case that's too much
> effort, I suggest you take a look at:
>
>     The Truth About DKIM
>     <http://bbiw.net/presentations/DKIM%20Truth.pdf>
>
> specifically slide 4.  The left hand side includes a short list of common
> mis-assumptions about DKIM's meaning, along with the one correct one.  See
> whether you know which is the right one.

Yes, I know enough about DKIM to identify the right one.

I think that it is an error for the IETF to add DKIM signatures.  They do indeed
tell me
which intermediary has sent me the mail, but does nothing for the 'spam' that
the
intermediary accepted in the first place (albeit there being little of that on
the IETF
managed lists).  And has already been pointed out, the mailing list damages any
DKIM signature that is already there.  I find it interesting that John Levine
lists
'DKIM doesn't work with mailing lists'
as one of this three myths.  I think that that depends on the interpretation of
the word 'work'.  I would say that DKIM in this context, of a mailing list,
gives
a spurious impression of increased security that we would be better off without.
It functions, but does not work, in that it tells me nothing about the true
origin of the communication.

Tom Petch
>
> d/
>
> --
>
>    Dave Crocker
>    Brandenburg InternetWorking
>    bbiw.net
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From despres.remi@laposte.net  Fri Jul 29 06:39:26 2011
Return-Path: <despres.remi@laposte.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6603521F8A30 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 06:39:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level: 
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[AWL=0.062,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 65jnMA3rnUSE for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 06:39:26 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.20]) by ietfa.amsl.com (Postfix) with ESMTP id D5AA321F8B7E for <ietf@ietf.org>; Fri, 29 Jul 2011 06:39:25 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2309.sfr.fr (SMTP Server) with ESMTP id 83BE9700008C; Fri, 29 Jul 2011 15:39:24 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2309.sfr.fr (SMTP Server) with ESMTP id 1D39F7000089; Fri, 29 Jul 2011 15:39:23 +0200 (CEST)
X-SFR-UUID: 20110729133924119.1D39F7000089@msfrf2309.sfr.fr
Subject: Re: IPv6 traffic distribution
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF62B@newserver.arneill-py.local>
Date: Fri, 29 Jul 2011 15:39:23 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F4F2FCD3-8961-44A8-A1EA-D26643BDD9EC@laposte.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <m1QlzXt-0001gSC@stereo.hq.phicoh.net> <2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com> <392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local> <10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com> <392CB277BC2EAE4FB83C1206954BA6CEF62B@newserver.arneill-py.local>
To: Michel Py <michel@arneill-py.sacramento.ca.us>
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, 29 Jul 2011 13:39:26 -0000

Le 28 juil. 2011 =E0 08:07, Michel Py a =E9crit :

> James,
>=20
> If I remember correctly, you mentioned a bit ago that your job =
required
> you had native IPv6 at home.=20
>=20
> Question: Does an ISP providing you IPv6 out of the CPE box (meaning,
> without any software other than dual-stack on the hosts) qualify as
> native IPv6 if, behind the scenes, they use a tunnel broker, or 6rd?

Facts are AFAIK that:
- Tunnel brokers need host cooperation. They can't be used behind the =
scene by ISP's.
- 6rd can indeed be used behind the scene by ISP's, without users making =
the difference with native IPv6 routing in ISP networks. This has been =
proven on a large scale over 3.5 years.=20

Regards,
RD




From msk@cloudmark.com  Fri Jul 29 06:43:55 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 392C821F8BE8 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 06:43:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.954
X-Spam-Level: 
X-Spam-Status: No, score=-102.954 tagged_above=-999 required=5 tests=[AWL=-0.955, BAYES_00=-2.599, J_CHICKENPOX_15=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 9NQcS2B11m7C for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 06:43:54 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by ietfa.amsl.com (Postfix) with ESMTP id D56B221F8BC6 for <ietf@ietf.org>; Fri, 29 Jul 2011 06:43:54 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Fri, 29 Jul 2011 06:43:54 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: ietf <ietf@ietf.org>
Date: Fri, 29 Jul 2011 06:43:53 -0700
Subject: RE: DKIM Signatures now being applied to IETF Email
Thread-Topic: DKIM Signatures now being applied to IETF Email
Thread-Index: AcxN8wmg9bdhIH8vQOKkY/C/obxNKAAAmxwA
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF4B2@EXCH-C2.corp.cloudmark.com>
References: <20110725171748.GA13506@amsl.com> <4E2DAF60.8030307@dcrocker.net><4E2FFFDF.2080601@ieca.com><005d01cc4d44$3136eda0$4001a8c0@gateway.2wire.net> <4E3288EE.9050201@dcrocker.net> <006101cc4dea$2c9bdd40$4001a8c0@gateway.2wire.net>
In-Reply-To: <006101cc4dea$2c9bdd40$4001a8c0@gateway.2wire.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: Fri, 29 Jul 2011 13:43:55 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of t=
.petch
> Sent: Friday, July 29, 2011 5:22 AM
> To: dcrocker@bbiw.net; ietf
> Subject: Re: DKIM Signatures now being applied to IETF Email
>=20
> It functions, but does not work, in that it tells me nothing about the tr=
ue
> origin of the communication.

...but that's not what it's supposed to tell you.

From joelja@bogus.com  Fri Jul 29 06:51: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 793BA21F8745 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 06:51:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.095
X-Spam-Level: 
X-Spam-Status: No, score=-102.095 tagged_above=-999 required=5 tests=[AWL=0.205, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 JToKYLl3S9Ue for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 06:51:17 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id C1FA621F8748 for <ietf@ietf.org>; Fri, 29 Jul 2011 06:51:16 -0700 (PDT)
Received: from [IPv6:2001:df8::80:129a:ddff:feb1:e750] ([IPv6:2001:df8:0:80:129a:ddff:feb1:e750]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p6TDpBQS016157 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 29 Jul 2011 13:51:13 GMT (envelope-from joelja@bogus.com)
Subject: Re: IPv6 traffic distribution
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <F4F2FCD3-8961-44A8-A1EA-D26643BDD9EC@laposte.net>
Date: Fri, 29 Jul 2011 09:51:11 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B330A141-120A-4775-947A-2EAE28E10351@bogus.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <m1QlzXt-0001gSC@stereo.hq.phicoh.net> <2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com> <392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local> <10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com> <392CB277BC2EAE4FB83C1206954BA6CEF62B@newserver.arneill-py.local> <F4F2FCD3-8961-44A8-A1EA-D26643BDD9EC@laposte.net>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [IPv6:2001:418:1::81]); Fri, 29 Jul 2011 13:51:14 +0000 (UTC)
Cc: Michel Py <michel@arneill-py.sacramento.ca.us>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 13:51:17 -0000

On Jul 29, 2011, at 9:39 AM, R=E9mi Despr=E9s wrote:

>=20
> Le 28 juil. 2011 =E0 08:07, Michel Py a =E9crit :
>=20
>> James,
>>=20
>> If I remember correctly, you mentioned a bit ago that your job =
required
>> you had native IPv6 at home.=20
>>=20
>> Question: Does an ISP providing you IPv6 out of the CPE box (meaning,
>> without any software other than dual-stack on the hosts) qualify as
>> native IPv6 if, behind the scenes, they use a tunnel broker, or 6rd?
>=20
> Facts are AFAIK that:
> - Tunnel brokers need host cooperation. They can't be used behind the =
scene by ISP's.
> - 6rd can indeed be used behind the scene by ISP's, without users =
making the difference with native IPv6 routing in ISP networks. This has =
been proven on a large scale over 3.5 years.=20

I would suspect that there's nothing that prevents an isp running it's =
own tunnel broker and a compliant cpe from automating that process in =
much the same way that 6rd in free required control over the firmware. =
the business case for doing so seems like an exercise for the reader.

> Regards,
> RD
>=20
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From despres.remi@laposte.net  Fri Jul 29 07:12:53 2011
Return-Path: <despres.remi@laposte.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0A0921F8BE1 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 07:12:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J-hwXtOrMDwa for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 07:12:53 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.20]) by ietfa.amsl.com (Postfix) with ESMTP id E30F021F8C1E for <ietf@ietf.org>; Fri, 29 Jul 2011 07:12:51 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2309.sfr.fr (SMTP Server) with ESMTP id 460CB700008A; Fri, 29 Jul 2011 16:12:51 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2309.sfr.fr (SMTP Server) with ESMTP id AD2E17000087; Fri, 29 Jul 2011 16:12:50 +0200 (CEST)
X-SFR-UUID: 20110729141250709.AD2E17000087@msfrf2309.sfr.fr
Subject: Re: IPv6 traffic distribution
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <B330A141-120A-4775-947A-2EAE28E10351@bogus.com>
Date: Fri, 29 Jul 2011 16:12:49 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <2FB9FC27-C26F-4B9F-A79B-ED5E221724E1@laposte.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <m1QlzXt-0001gSC@stereo.hq.phicoh.net> <2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com> <392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local> <10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com> <392CB277BC2EAE4FB83C1206954BA6CEF62B@newserver.arneill-py.local> <F4F2FCD3-8961-44A8-A1EA-D26643BDD9EC@laposte.net> <B330A141-120A-4775-947A-2EAE28E10351@bogus.com>
To: Joel Jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1084)
Cc: Michel Py <michel@arneill-py.sacramento.ca.us>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 14:12:54 -0000

Le 29 juil. 2011 =E0 15:51, Joel Jaeggli a =E9crit :

>=20
> On Jul 29, 2011, at 9:39 AM, R=E9mi Despr=E9s wrote:
>=20
>>=20
>> Le 28 juil. 2011 =E0 08:07, Michel Py a =E9crit :
>>=20
>>> James,
>>>=20
>>> If I remember correctly, you mentioned a bit ago that your job =
required
>>> you had native IPv6 at home.=20
>>>=20
>>> Question: Does an ISP providing you IPv6 out of the CPE box =
(meaning,
>>> without any software other than dual-stack on the hosts) qualify as
>>> native IPv6 if, behind the scenes, they use a tunnel broker, or 6rd?
>>=20
>> Facts are AFAIK that:
>> - Tunnel brokers need host cooperation. They can't be used behind the =
scene by ISP's.
>> - 6rd can indeed be used behind the scene by ISP's, without users =
making the difference with native IPv6 routing in ISP networks. This has =
been proven on a large scale over 3.5 years.=20
>=20
> I would suspect that there's nothing that prevents an isp running it's =
own tunnel broker and a compliant cpe from automating that process in =
much the same way that 6rd in free required control over the firmware.

Fair enough, that's a technical possibility.

> the business case for doing so seems like an exercise for the reader.

Exactly, I doubt any ISP would do that, in view of the compared =
simplicity of 6rd.
If that would be used, customers would have native prefixes for which =
they ignore that ISP-network traversal has bee tunneled.

Regards,
RD=


From moore@network-heretics.com  Fri Jul 29 07:33: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 7E6DC21F8563 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 07:33:48 -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=[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 1nTINcfHWT92 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 07:33:47 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id C12AF21F8BF3 for <ietf@ietf.org>; Fri, 29 Jul 2011 07:33:47 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id E263C20953; Fri, 29 Jul 2011 10:33:46 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute5.internal (MEProxy); Fri, 29 Jul 2011 10:33:46 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=references:in-reply-to:mime-version :content-type:content-transfer-encoding:subject:from:date:to:cc :message-id; s=smtpout; bh=br5lmQIYX3/HWTOgMTwjEB6Ck10=; b=jXS4N mz0dzMbgF5CpAul/3Guf+lSpM2p3lbmq9R808ERhKikJSY+Os1IZxZdDC0AUXBwL BrwZyHwqZJw28M9VwSzSI+LfSeTstdNEw+MsaukxqlRsphQj2f+wGu9f/+fCx+ji bjOGLe1CC5mC+PgRNMwi0j11gA4zFOlneEJlls=
X-Sasl-enc: ycSvwqnPLHbtAiLFGrTuPfx4ajxm6BbUE0T7MuEp77Kq 1311950026
Received: from [192.168.1.63] (unknown [206.172.18.93]) by mail.messagingengine.com (Postfix) with ESMTPSA id 3DB8F41544F; Fri, 29 Jul 2011 10:33:46 -0400 (EDT)
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net><4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com><72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com> <5A600744-8605-46D3-82B2-C3C30E30E4AC@network-heretics.com> <392CB277BC2EAE4FB83C1206954BA6CEF625@newserver.arneill-py.local> <4E656E6D-EA61-48E7-BF06-6F038777FA70@laposte.net>
User-Agent: K-9 Mail for Android
In-Reply-To: <4E656E6D-EA61-48E7-BF06-6F038777FA70@laposte.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: 6to4v2 (as in ripv2)?
From: Keith Moore <moore@network-heretics.com>
Date: Fri, 29 Jul 2011 10:33:42 -0400
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>, Michel Py <michel@arneill-py.sacramento.ca.us>
Message-ID: <cabc1e23-efbb-4ccc-ae93-82a8a38478a6@email.android.com>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 14:33:48 -0000

"RÃ©mi DesprÃ©s" <despres.remi@laposte.net> wrote:

>
>Le 27 juil. 2011 Ã  17:29, Michel Py a Ã©crit :
>> ...
>>>> Fred Baker wrote:
>>>> Actually, I think one could argue pretty
>>>> effectively that 6rd is 6to4-bis.
>> 
>> Indeed, and it also is a transition mechanism for the very same reasons
>> that 6to4 is.
>> 
>> 
>>> Keith Moore wrote:
>>> only if you're confused about the use cases for each.
>> 
>> Even if there are different use cases indeed (as you explained it very
>> well yourself)
>
>> you can't deny that 6rd is 6to4-bis.
>
>Oh, yes indeed, on can!
>(Depending, of course on what you mean with 6to4-bis, but no one can be
>sure what you mean).
>
>- 6to4 delivers native IPv6 prefixes to customer sites, which 6to4 doesn't.
>- 6to4 has known operational problems, not 6rd.

In a sense, 6rd has all of the problems that 6to4 does.  The difference is that 6to4 is deployed independent of network operators and often without their involvement, and 6rd (when deployed) is deployed by network operators on their own networks.  So 6to4 tries to work over networks that might or might not be unsuitable for it, or even hostile to it.  By contrast, if an operator's network isn't a good fit for 6rd, they simply don't use it.   And presumably an operator choosing to use 6rd won't try to DoS it...

Again: there are valid use cases for 6to4. But almost any kind of provider managed service (except one that NATs traffic) is almost certainly better.

Keith
-- 
Sent from my Android tablet with K-9 Mail. 

From bob.hinden@gmail.com  Fri Jul 29 07:39:31 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 29E0321F8C05 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 07:39:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.57
X-Spam-Level: 
X-Spam-Status: No, score=-103.57 tagged_above=-999 required=5 tests=[AWL=0.029, 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 U6vMfreLcJyZ for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 07:39:30 -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 9100F21F8BF6 for <ietf@ietf.org>; Fri, 29 Jul 2011 07:39:30 -0700 (PDT)
Received: by yxp4 with SMTP id 4so2876809yxp.31 for <ietf@ietf.org>; Fri, 29 Jul 2011 07:39:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=kQmel97Fby5LZy/ZtfmI4qz6vtj/A8lpiFTEZjIaCjM=; b=vdeeYTbPG3gxxFCj3YvXRa6Gbn7XmhTS7pd2E5G8M6mJE549Ra0RFgI5QJYV8vifeh WuCVT3C357I37LaE5Y7isJn6M48li48105FAGhQCXhJuvv7JJjq76qOxMD+SEhVXzHM+ H7JjC83eAe8UglEx0KIGF8wJh7NfLvm+OcRO0=
Received: by 10.68.24.228 with SMTP id x4mr2263940pbf.261.1311950369125; Fri, 29 Jul 2011 07:39:29 -0700 (PDT)
Received: from dhcp-445b.meeting.ietf.org (dhcp-445b.meeting.ietf.org [130.129.68.91]) by mx.google.com with ESMTPS id p7sm673055pbn.81.2011.07.29.07.39.27 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 29 Jul 2011 07:39:28 -0700 (PDT)
Subject: Re: Last Call: <draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
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: <20110728020207.26024.73829.idtracker@ietfa.amsl.com>
Date: Fri, 29 Jul 2011 10:39:25 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A78EB07C-8D05-4EC1-9800-AC07502FCB6B@gmail.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1084)
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 14:39:31 -0000

Hi,

I generally support this proposal, but have some questions on Section =
2.3, "Transition to a Standards Track with Two Maturity Levels".  I am =
both an author of several Draft Standards and have chaired working =
groups that have produced them.

>    Any protocol or service that is currently at the abandoned Draft
>    Standard maturity level will retain that classification, absent
>    explicit actions.  Two possible actions are available:
>=20
>    (1) A Draft Standard may be reclassified as an Internet Standard as
>        soon as the criteria in Section 2.2 are satisfied.


What is the process for this?  Is the IESG going to review all Draft =
Standards.  Should authors and/or working groups propose a change of =
status as defined in the document?  Something else?  Most draft =
standards very likely meet most of the requirements listed in the =
document for Internet Standard.


>=20
>    (2) At any time after two years from the approval of this document =
as
>        a BCP, the IESG may choose to reclassify any Draft Standard
>        document as Proposed Standard.


I think this is unfair to the people who have done considerable work to =
get a document to Draft Standard.  I hope that the IESG would only do =
this after giving a lot of notice to the authors, appropriate working =
groups, and the IETF community to give them the opportunity to request =
advancement to Internet Standard.=20

I think this Section of the document needs to provide additional detail =
on how this should work.

Regards,
Bob







From despres.remi@laposte.net  Fri Jul 29 07:54:51 2011
Return-Path: <despres.remi@laposte.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9B6321F8C51 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 07:54:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.892
X-Spam-Level: 
X-Spam-Status: No, score=-1.892 tagged_above=-999 required=5 tests=[AWL=0.057,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CTcMHK6o95eR for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 07:54:51 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.20]) by ietfa.amsl.com (Postfix) with ESMTP id A0B5A21F8C48 for <ietf@ietf.org>; Fri, 29 Jul 2011 07:54:45 -0700 (PDT)
Received: by msfrf2309.sfr.fr (SMTP Server, from userid 1004) id D50B6700009E; Fri, 29 Jul 2011 16:54:44 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2309.sfr.fr (SMTP Server) with ESMTP id 3801E7000096; Fri, 29 Jul 2011 16:54:44 +0200 (CEST)
X-SFR-UUID: 20110729145444229.3801E7000096@msfrf2309.sfr.fr
Subject: Re: IPv6 traffic distribution
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <91527B3C-A687-4750-A8AA-A5E9C0F3FDDC@apnic.net>
Date: Fri, 29 Jul 2011 16:54:43 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5EB3E61-BEEA-4441-A346-A0361AF00CDD@laposte.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com><4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>	<4E2EDF23.3060804@gmail.com><4E2F4491.30102@gmail.com>	<20110727023833.5C72D1232958@drugs.dv.isc.org>	<m1QlzXt-0001gSC@stereo.hq.phicoh.net>	<2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com>	<392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local>	<10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com>	<CAKD1Yr3gv=+HfEZMsU0enNh8OQbemQh6iRzpGHsnmr7OJrTcFg@mail.gmail.com>	<392CB277BC2EAE4FB83C1206954BA6CEF635@newserver.arneill-py.local>	<3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk><EMEW3|fa0511c175232cff9b9cb8310f081538n6RMCh03tjc|ecs.soton.ac.uk|3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk> <4E31F3C2.4000000@gmail.com> <392CB277BC2EAE4FB83C1206954BA6CEF637@newserver.arneill-py.local> <6E140BC3-0C38-453B-A557-A929EDC33A09@bogus.com> <392CB277BC2EAE4FB83C1206954BA6CE! F638@newserver.arneill-py.local> <D55ACDFC-4667-446E-871C-B480D7A93A1A@bogus.com> <91527B3C-A687-4750-A8AA-A5E9C0F3FDDC@apnic.net>
To: George Michaelson <ggm+ietf@apnic.net>
X-Mailer: Apple Mail (2.1084)
X-sfr-spamlevel: not-spam
Cc: Michel Py <michel@arneill-py.sacramento.ca.us>, Tim Chown <tjc@ecs.soton.ac.uk>, 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, 29 Jul 2011 14:54:51 -0000

Le 29 juil. 2011 =E0 14:16, George Michaelson a =E9crit :

>=20
> On 29/07/2011, at 8:03 AM, Joel Jaeggli wrote:
>=20
>> agree but if you're trying to discriminate it by:
>>=20
>> "This graph shows the daily unique queried reverse addresses by =
type."
>>=20
>> you can't.
>>=20
>=20
>=20
> Very true Joel. I did, for a while, pattern match the 6rd prefix from =
Free.FR's declared ranges in RIPE whois but it was pointed out to me =
that dealing with one ISP like this skews things.
>=20
> After all, other ISps also deploy 6rd, and Comcast do some kind of =
related work.
>=20
> I can put in a 6rd line, if thats what people *want*

I suppose that te proportion of native IPv6 traffic due to Free will =
quickly decrease as IPv6 gets really deployed by others.
(This proportion was reported to still be slightly above 50% a few =
months ago, but this was before the World IPv6 day and various other =
events.)

Yes, that would be nice to have this proportion for some time.

Thanks,
RD


>=20
> -G
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From barryleiba.mailing.lists@gmail.com  Fri Jul 29 08:02:22 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 7BF2711E8072 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 08:02:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.054
X-Spam-Level: 
X-Spam-Status: No, score=-103.054 tagged_above=-999 required=5 tests=[AWL=-0.077, 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 eGysDywU6Vc8 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 08:02: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 EE54921F8BA5 for <ietf@ietf.org>; Fri, 29 Jul 2011 08:02:21 -0700 (PDT)
Received: by yie30 with SMTP id 30so3124915yie.31 for <ietf@ietf.org>; Fri, 29 Jul 2011 08:02:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=PIpUWS5r4LvvnMNyidVy89jVSoqWztNhKjMmHDOVhfo=; b=aOYY+m1TqBKbu0ZTkyWXnOQ374fGrNpzrQgs94q3vzHuK/HixdpaUxJzSMw2feo9Cn rYkX+0MdH/OpNyQZSEUSLfBOxhvFEEevC7K2hyd6/oAAhBgZCBdfuKFvU+AIViOJlvWA hk5N6qR0YpwFymyfhjJrBDD2aX1iwobpi6k1M=
MIME-Version: 1.0
Received: by 10.146.134.18 with SMTP id h18mr1177300yad.8.1311951741505; Fri, 29 Jul 2011 08:02:21 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.32.15 with HTTP; Fri, 29 Jul 2011 08:02:21 -0700 (PDT)
In-Reply-To: <006101cc4dea$2c9bdd40$4001a8c0@gateway.2wire.net>
References: <20110725171748.GA13506@amsl.com> <4E2DAF60.8030307@dcrocker.net> <4E2FFFDF.2080601@ieca.com> <005d01cc4d44$3136eda0$4001a8c0@gateway.2wire.net> <4E3288EE.9050201@dcrocker.net> <006101cc4dea$2c9bdd40$4001a8c0@gateway.2wire.net>
Date: Fri, 29 Jul 2011 11:02:21 -0400
X-Google-Sender-Auth: 4JU2el_I_xpMd_ICfsqkc0UeMpc
Message-ID: <CAC4RtVDSHEhcffUx=+Y2vORb1TBmgs=XmGrvJgAc1upo-5SbEQ@mail.gmail.com>
Subject: Re: DKIM Signatures now being applied to IETF Email
From: Barry Leiba <barryleiba@computer.org>
To: "t.petch" <daedulus@btconnect.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 15:02:22 -0000

> I think that it is an error for the IETF to add DKIM signatures. =A0They =
do indeed
> tell me
> which intermediary has sent me the mail, but does nothing for the 'spam' =
that
> the
> intermediary accepted in the first place (albeit there being little of th=
at on
> the IETF
> managed lists).
...
> It functions, but does not work, in that it tells me nothing about the tr=
ue
> origin of the communication.

What it does is allow you to assure yourself that the message was,
indeed, from an IETF mailing list (well, from an IETF email server),
and that it wasn't that someone tried to spoof that.  That, in turn,
allows you to confidently increase your trust that the message is not
spam in proportion to your confidence in the IETF's spam-filtering
capabilities.

Some of us, at least, find that useful.  Some of us might even
completely white-list IETF-signed messages.  You can make your own
choice on that.

Barry, DKIM WG chair

From housley@vigilsec.com  Fri Jul 29 08:14:01 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 2604921F8C6A for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 08:14:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.519
X-Spam-Level: 
X-Spam-Status: No, score=-102.519 tagged_above=-999 required=5 tests=[AWL=0.080, 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 4EGm1wJObpsv for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 08:14:00 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 2A72021F8BF3 for <ietf@ietf.org>; Fri, 29 Jul 2011 08:14:00 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 9FA4AF240C4; Fri, 29 Jul 2011 11:13:54 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id ZU2KiyUiyu0H; Fri, 29 Jul 2011 11:13:48 -0400 (EDT)
Received: from dhcp-227d.meeting.ietf.org (dhcp-227d.meeting.ietf.org [130.129.34.125]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id C296FF24048; Fri, 29 Jul 2011 11:13:52 -0400 (EDT)
Subject: Re: Last Call: <draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <A78EB07C-8D05-4EC1-9800-AC07502FCB6B@gmail.com>
Date: Fri, 29 Jul 2011 11:13:50 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <573CDFAC-1C01-43F1-9878-EF6EB57F6710@vigilsec.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <A78EB07C-8D05-4EC1-9800-AC07502FCB6B@gmail.com>
To: Bob Hinden <bob.hinden@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, 29 Jul 2011 15:14:01 -0000

Bob:

> I generally support this proposal, but have some questions on Section =
2.3, "Transition to a Standards Track with Two Maturity Levels".  I am =
both an author of several Draft Standards and have chaired working =
groups that have produced them.
>=20
>>   Any protocol or service that is currently at the abandoned Draft
>>   Standard maturity level will retain that classification, absent
>>   explicit actions.  Two possible actions are available:
>>=20
>>   (1) A Draft Standard may be reclassified as an Internet Standard as
>>       soon as the criteria in Section 2.2 are satisfied.
>=20
>=20
> What is the process for this?  Is the IESG going to review all Draft =
Standards.  Should authors and/or working groups propose a change of =
status as defined in the document?  Something else?  Most draft =
standards very likely meet most of the requirements listed in the =
document for Internet Standard.

Section 2.2 is pretty clear I think.  A request to reclassification must =
be sent to the IESG.

   ... The request for reclassification is sent to the
   IESG along with an explanation of how the criteria have been met.
   The criteria are:

   (1) There are at least two independent interoperating implementations
       with widespread deployment and successful operational experience.

   (2) There are no errata against the specification that would cause a
       new implementation to fail to interoperate with deployed ones.

   (3) There are no unused features in the specification that greatly
       increase implementation complexity.

   (4) If patented or otherwise controlled technology is required for
       implementation, the implementations demonstrate at least two
       separate and successful uses of the licensing process.


>>   (2) At any time after two years from the approval of this document =
as
>>       a BCP, the IESG may choose to reclassify any Draft Standard
>>       document as Proposed Standard.
>=20
> I think this is unfair to the people who have done considerable work =
to get a document to Draft Standard.  I hope that the IESG would only do =
this after giving a lot of notice to the authors, appropriate working =
groups, and the IETF community to give them the opportunity to request =
advancement to Internet Standard.=20

This was added after the discussion that Draft Standards could linger =
for a very long time.  Some people said that would not be a problem, and =
other people said it would be harmful.  I conclude that no one knows, so =
we should include the powers necessary to resolve the problems if they =
emerge.  If they do not emerge, there is no requirement that the IESG do =
anything.

> I think this Section of the document needs to provide additional =
detail on how this should work.

I do not think we should add speculation about the potential problems to =
this document.

Russ


From michel@arneill-py.sacramento.ca.us  Fri Jul 29 09:21:01 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 5B50F21F8B15 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 09:21:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.003
X-Spam-Level: 
X-Spam-Status: No, score=-2.003 tagged_above=-999 required=5 tests=[AWL=-0.038, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cbq4heZS8699 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 09:21:00 -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 CC10221F884E for <ietf@ietf.org>; Fri, 29 Jul 2011 09:21:00 -0700 (PDT)
Subject: RE: 6to4v2 (as in ripv2)? 
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Date: Fri, 29 Jul 2011 09:21:00 -0700
Content-Transfer-Encoding: quoted-printable
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF639@newserver.arneill-py.local>
Content-class: urn:content-classes:message
In-Reply-To: <4E656E6D-EA61-48E7-BF06-6F038777FA70@laposte.net>
X-MS-Has-Attach: 
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-MS-TNEF-Correlator: 
Thread-Topic: 6to4v2 (as in ripv2)? 
Thread-Index: AcxN7l9R63Cbl9RzQAuywBVQs3ZKxAAHHXOw
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com>	<4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net><4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com><72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com> <5A600744-8605-46D3-82B2-C3C30E30E4AC@network-heretics.com> <392CB277BC2EAE4FB83C1206954BA6CEF625@newserver.arneill-py.local> <4E656E6D-EA61-48E7-BF06-6F038777FA70@laposte.net>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
Cc: 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, 29 Jul 2011 16:21:01 -0000

> R=E9mi Despr=E9s wrote:
> - 6to4 delivers native IPv6 prefixes to customer sites, which 6to4 =
doesn't.

That is playing with words. In that case, any router that delivers =
native IPv6 to the hosts (by having the tunnel software on the router, =
not on the hosts) can be called a native solution.

This is just flat out WRONG. ANY solution that needs IPv4 to transport =
IPv6 is NOT native IPv6, and regardless of who states it and their great =
contributions, it will remain the same.

Some please stop calling things what they are not; a native IPv6 =
solution is one that works when IPv4 has been removed, anything else is =
called a transition mechanism.

Michel.


From dcrocker@gmail.com  Fri Jul 29 03:04:19 2011
Return-Path: <dcrocker@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03E1B21F8B6F for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 03:04: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 Dq9I-CVSe4Xy for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 03:04:18 -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 47D1F21F8B67 for <ietf@ietf.org>; Fri, 29 Jul 2011 03:04:18 -0700 (PDT)
Received: by qwc23 with SMTP id 23so2321652qwc.31 for <ietf@ietf.org>; Fri, 29 Jul 2011 03:04:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=rOaBWgd8MKy7hGWCE2+362xqYk3fnhNJ9EmVc1Ucjwg=; b=RgGmlMAAh42nMK1HUePoYrkJN1jD6i2bS/3NxhWWiI8UsIWOybNwH/4z2FPgDQ5T9S ppnAFAYP4lTaZfyOWPldV7001XUOHd38FKARdUgJN16luTfXf3priZNRNHSd/wSDX5Ur ZLSnz16D/EW+5Guf3YRd20LRohwAQOOXAH9Pg=
Received: by 10.224.209.73 with SMTP id gf9mr815499qab.362.1311933857619; Fri, 29 Jul 2011 03:04:17 -0700 (PDT)
Received: from [172.16.58.236] (modemcable252.155-70-69.static.videotron.ca [69.70.155.252]) by mx.google.com with ESMTPS id d12sm1283965qcd.14.2011.07.29.03.04.15 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 29 Jul 2011 03:04:16 -0700 (PDT)
Message-ID: <4E328599.3080803@gmail.com>
Date: Fri, 29 Jul 2011 06:04:09 -0400
From: Dave Crocker <dcrocker@gmail.com>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: On attending BoFs
References: <F5833273385BB34F99288B3648C4F06F13512DF4A7@EXCH-C2.corp.cloudmark.com> <051e01cc4d64$493d3c40$dbb7b4c0$@com> <3064576985382880915@unknownmsgid> <F9EC5BB4-F51C-47E9-AE84-BBC440715D31@standardstrack.com>
In-Reply-To: <F9EC5BB4-F51C-47E9-AE84-BBC440715D31@standardstrack.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 29 Jul 2011 09:25:36 -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, 29 Jul 2011 10:04:19 -0000

I seem to recall having sometimes seen the chair reserve the front of the 
seating for people who claim to have read the drafts.

d/

On 7/29/2011 12:12 AM, Eric Burger wrote:
> Just for the record: we want big rooms!
>
> On Jul 28, 2011, at 10:01 PM, Scott Brim wrote:
>
>> And do you really only want people in the room who already know the
>> issues and have decided to be for or against it?  If you already have
>> so many of them, you don't need a BOF at all, just take a hum and be
>> done. The main purpose of a BOF is to present. Information to the
>> community so they can decide if the IETF should adopt the work.
>> _______________________________________________
>> 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 ggm+ietf@apnic.net  Fri Jul 29 09:28:18 2011
Return-Path: <ggm+ietf@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F53021F8A70 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 09:28:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.804
X-Spam-Level: 
X-Spam-Status: No, score=-101.804 tagged_above=-999 required=5 tests=[AWL=0.495, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xy5TRA2XUlOE for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 09:28:17 -0700 (PDT)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id 3C76021F8A6F for <ietf@ietf.org>; Fri, 29 Jul 2011 09:28:17 -0700 (PDT)
Received: from dhcp-53cd.meeting.ietf.org (dhcp-53cd.meeting.ietf.org [130.129.83.205]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id D17B9B673D; Sat, 30 Jul 2011 02:28:12 +1000 (EST)
Subject: Re: IPv6 traffic distribution
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: George Michaelson <ggm+ietf@apnic.net>
In-Reply-To: <C5EB3E61-BEEA-4441-A346-A0361AF00CDD@laposte.net>
Date: Fri, 29 Jul 2011 12:28:03 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2DB496E2-740A-445E-88FE-2C3250F95664@apnic.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com><4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>	<4E2EDF23.3060804@gmail.com><4E2F4491.30102@gmail.com>	<20110727023833.5C72D1232958@drugs.dv.isc.org>	<m1QlzXt-0001gSC@stereo.hq.phicoh.net>	<2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com>	<392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local>	<10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com>	<CAKD1Yr3gv=+HfEZMsU0enNh8OQbemQh6iRzpGHsnmr7OJrTcFg@mail.gmail.com>	<392CB277BC2EAE4FB83C1206954BA6CEF635@newserver.arneill-py.local>	<3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk><EMEW3|fa0511c175232cff9b9cb8310f081538n6RMCh03tjc|ecs.soton.ac.uk|3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk> <4E31F3C2.4000000@gmail.com> <392CB277BC2EAE4FB83C1206954BA6CEF637@newserver.arneill-py.local> <6E140BC3-0C38-453B-A557-A929EDC33A09@bogus.com> <392CB277BC2EAE4FB83C1206954BA6CE! F638@newserver.arneill-py.local> <D55ACDFC-4667-446E-871C-B480D7A93A1A@bogus.com> <91527B3C-A687-4750-A8AA-A5E9C0F3FDDC@apnic.net> <C5EB3E61-BEEA-4441-A346-A0361AF00CDD@laposte.net>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
X-Mailer: Apple Mail (2.1084)
Cc: Michel Py <michel@arneill-py.sacramento.ca.us>, Tim Chown <tjc@ecs.soton.ac.uk>, 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, 29 Jul 2011 16:28:18 -0000

I have updated the graph to include 6rd, based on my understanding that =
the prefixes of the form 2a01:e3xx: are your 6rd space.

There is *other* FreeNet space, which appears to do things, but I sense =
its not part of the 6rd deployment since the numberforms in the lower =
/64 appear to be infrastructure assignment, not classic customer space =
forms.

Please let me know if I have this wrong.

You will notice that this count places Free/6rd at a far lower relative =
% of unique DNS than the measures of traffic and sources people =
discussing here. I think this bears thinking about.

http://labs.apnic.net/dns-measurement/

-George


From despres.remi@laposte.net  Fri Jul 29 09:50:28 2011
Return-Path: <despres.remi@laposte.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85BAC21F8B02 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 09:50:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level: 
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[AWL=0.055,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ai8XQTeSAWkq for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 09:50:28 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA6C521F8AFF for <ietf@ietf.org>; Fri, 29 Jul 2011 09:50:27 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2118.sfr.fr (SMTP Server) with ESMTP id 0AC2B700009B; Fri, 29 Jul 2011 18:50:27 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2118.sfr.fr (SMTP Server) with ESMTP id 6DF93700009C; Fri, 29 Jul 2011 18:50:22 +0200 (CEST)
X-SFR-UUID: 20110729165022450.6DF93700009C@msfrf2118.sfr.fr
Subject: Re: 6to4v2 (as in ripv2)? 
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF639@newserver.arneill-py.local>
Date: Fri, 29 Jul 2011 18:50:21 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <AF449E25-057F-4856-AB92-1D6D19027A98@laposte.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com>	<4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net><4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com><72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com> <5A600744-8605-46D3-82B2-C3C30E30E4AC@network-heretics.com> <392CB277BC2EAE4FB83C1206954BA6CEF625@newserver.arneill-py.local> <4E656E6D-EA61-48E7-BF06-6F038777FA70@laposte.net> <392CB277BC2EAE4FB83C1206954BA6CEF639@newserver.arneill-py.local>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
X-Mailer: Apple Mail (2.1084)
Cc: 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, 29 Jul 2011 16:50:28 -0000

Le 29 juil. 2011 =E0 18:21, Michel Py a =E9crit :

>> R=E9mi Despr=E9s wrote:
>> - 6to4 delivers native IPv6 prefixes to customer sites, which 6to4 =
doesn't.
>=20
> That is playing with words. In that case, any router that delivers =
native IPv6 to the hosts (by having the tunnel software on the router, =
not on the hosts) can be called a native solution.
>=20
> This is just flat out WRONG. ANY solution that needs IPv4 to transport =
IPv6 is NOT native IPv6, and regardless of who states it and their great =
contributions, it will remain the same.
>=20
> Some please stop calling things what they are not; a native IPv6 =
solution is one that works when IPv4 has been removed, anything else is =
called a transition mechanism.

We have, it seems, a different understanding of the situation.

The distinction to be made, and which I make, is between
- native addresses vs well-known-prefix addresses (the former start with =
an ISP allocated prefix, the latter, e.g. those of 6to4 and Teredo, have =
a routing problem in the Internet backbone)
- native IPv6 routing (IPv6-only or dual stack) vs IPv4-only routing=20

6rd is designed to offer native IPv6 prefixes across IPv4-only routing =
domains.

Regards,
RD




From dhc2@dcrocker.net  Fri Jul 29 09:53:19 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 654F35E800E for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 09:53:19 -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 ZsfAnaFh-+nM for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 09:53:18 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C214B5E800A for <ietf@ietf.org>; Fri, 29 Jul 2011 09:53:18 -0700 (PDT)
Received: from [130.129.85.251] (dhcp-55fb.meeting.ietf.org [130.129.85.251]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p6TGr8TH011742 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Jul 2011 09:53:15 -0700
Message-ID: <4E32E571.4050108@dcrocker.net>
Date: Fri, 29 Jul 2011 12:53:05 -0400
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Last Call: <draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <A78EB07C-8D05-4EC1-9800-AC07502FCB6B@gmail.com> <573CDFAC-1C01-43F1-9878-EF6EB57F6710@vigilsec.com>
In-Reply-To: <573CDFAC-1C01-43F1-9878-EF6EB57F6710@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 29 Jul 2011 09:53:16 -0700 (PDT)
Cc: Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 16:53:19 -0000

On 7/29/2011 11:13 AM, Russ Housley wrote:
>>> (2) At any time after two years from the approval of this document as a
>>> BCP, the IESG may choose to reclassify any Draft Standard document as
>>> Proposed Standard.
>>
>> I think this is unfair to the people who have done considerable work to get
>> a document to Draft Standard.  I hope that the IESG would only do this
>> after giving a lot of notice to the authors, appropriate working groups,
>> and the IETF community to give them the opportunity to request advancement
>> to Internet Standard.
>
> This was added after the discussion that Draft Standards could linger for a
> very long time.  Some people said that would not be a problem, and other
> people said it would be harmful.  I conclude that no one knows, so we should
> include the powers necessary to resolve the problems if they emerge.  If they
> do not emerge, there is no requirement that the IESG do anything.

If a document no longer has anyone watching it, there's a reasonable concern
that it no longer has much constituency.  In that case, it's better to treat it 
as immature rather than mature.


>> I think this Section of the document needs to provide additional detail on
>> how this should work.
>
> I do not think we should add speculation about the potential problems to this
> document.

+1

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From dhc2@dcrocker.net  Fri Jul 29 09:55:58 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 D1B6B21F8686 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 09:55:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4rTtLHuWdGf8 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 09:55:58 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5916821F8672 for <ietf@ietf.org>; Fri, 29 Jul 2011 09:55:58 -0700 (PDT)
Received: from [130.129.85.251] (dhcp-55fb.meeting.ietf.org [130.129.85.251]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p6TGtpRf011806 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 29 Jul 2011 09:55:57 -0700
Message-ID: <4E32E614.8040308@dcrocker.net>
Date: Fri, 29 Jul 2011 12:55:48 -0400
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DKIM Signatures now being applied to IETF Email
References: <20110725171748.GA13506@amsl.com> <4E2DAF60.8030307@dcrocker.net> <4E2FFFDF.2080601@ieca.com> <005d01cc4d44$3136eda0$4001a8c0@gateway.2wire.net> <4E3288EE.9050201@dcrocker.net> <006101cc4dea$2c9bdd40$4001a8c0@gateway.2wire.net> <CAC4RtVDSHEhcffUx=+Y2vORb1TBmgs=XmGrvJgAc1upo-5SbEQ@mail.gmail.com>
In-Reply-To: <CAC4RtVDSHEhcffUx=+Y2vORb1TBmgs=XmGrvJgAc1upo-5SbEQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 29 Jul 2011 09:55:58 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 16:55:58 -0000

On 7/29/2011 11:02 AM, Barry Leiba wrote:
> What it does is allow you to assure yourself that the message was,
> indeed, from an IETF mailing list (well, from an IETF email server),
> and that it wasn't that someone tried to spoof that.  That, in turn,
> allows you to confidently increase your trust that the message is not
> spam in proportion to your confidence in the IETF's spam-filtering
> capabilities.
>
> Some of us, at least, find that useful.  Some of us might even
> completely white-list IETF-signed messages.  You can make your own
> choice on that.


An intermediary that signs messages and has a reputation for carrying spam in 
its stream will have an appropriate reputation.  One that signs messages and has 
a clean message stream will also have an appropriate reputation.

The differences between the two will produce very different disposition at the 
delivery site.

All of which is cleaner and safer than is possible today, except with 
constrained uses of previous-hop IP(v4) addresses.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From michel@arneill-py.sacramento.ca.us  Fri Jul 29 11:38:17 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 95FE25E8011 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 11:38:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[AWL=-0.035, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M4cwulEVDODK for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 11:38:17 -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 20CD75E800F for <ietf@ietf.org>; Fri, 29 Jul 2011 11:38:17 -0700 (PDT)
Subject: RE: 6to4v2 (as in ripv2)? 
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Date: Fri, 29 Jul 2011 11:38:16 -0700
Content-Transfer-Encoding: quoted-printable
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF63A@newserver.arneill-py.local>
Content-class: urn:content-classes:message
In-Reply-To: <AF449E25-057F-4856-AB92-1D6D19027A98@laposte.net>
X-MS-Has-Attach: 
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-MS-TNEF-Correlator: 
Thread-Topic: 6to4v2 (as in ripv2)? 
Thread-Index: AcxOD58+04/oCfU1QZSH3jYavJW7dgADsVIg
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com>	<4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net><4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com><72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com> <5A600744-8605-46D3-82B2-C3C30E30E4AC@network-heretics.com> <392CB277BC2EAE4FB83C1206954BA6CEF625@newserver.arneill-py.local> <4E656E6D-EA61-48E7-BF06-6F038777FA70@laposte.net> <392CB277BC2EAE4FB83C1206954BA6CEF639@newserver.arneill-py.local> <AF449E25-057F-4856-AB92-1D6D19027A98@laposte.net>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
Cc: 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, 29 Jul 2011 18:38:17 -0000

> R=E9mi Despr=E9s wrote:
> 6rd is designed to offer native IPv6 prefixes
> across IPv4-only routing domains.

There is a word for that: oxymoron. In French: oxymore.
If it stops working when IPv4 is broken, it is not native.

Michel.


From huitema@microsoft.com  Fri Jul 29 12:16:35 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 C7CB821F8B38 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 12:16:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.549
X-Spam-Level: 
X-Spam-Status: No, score=-10.549 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 Ui5zMWBQpP-G for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 12:16:35 -0700 (PDT)
Received: from smtp.microsoft.com (mail3.microsoft.com [131.107.115.214]) by ietfa.amsl.com (Postfix) with ESMTP id 3C8DA21F8B35 for <ietf@ietf.org>; Fri, 29 Jul 2011 12:16:35 -0700 (PDT)
Received: from TK5EX14HUBC104.redmond.corp.microsoft.com (157.54.80.25) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 29 Jul 2011 12:16:35 -0700
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14HUBC104.redmond.corp.microsoft.com (157.54.80.25) with Microsoft SMTP Server (TLS) id 14.1.323.2; Fri, 29 Jul 2011 12:16:34 -0700
Received: from TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com ([169.254.1.52]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi id 14.01.0289.008; Fri, 29 Jul 2011 12:16:34 -0700
From: Christian Huitema <huitema@microsoft.com>
To: Michel Py <michel@arneill-py.sacramento.ca.us>, =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
Subject: RE: 6to4v2 (as in ripv2)? 
Thread-Topic: 6to4v2 (as in ripv2)? 
Thread-Index: AQHMS+ZmwMuKugepKkyXRofd8XRLBJUAePCAgAASXgCAADY5AIAC+L4AgAA6SACAAAgzgIAAHicA//+RA3A=
Date: Fri, 29 Jul 2011 19:16:31 +0000
Message-ID: <22F6318E46E26B498ABC828879B08D4F1DAF89@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com>	<4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net><4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com><72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com> <5A600744-8605-46D3-82B2-C3C30E30E4AC@network-heretics.com> <392CB277BC2EAE4FB83C1206954BA6CEF625@newserver.arneill-py.local> <4E656E6D-EA61-48E7-BF06-6F038777FA70@laposte.net> <392CB277BC2EAE4FB83C1206954BA6CEF639@newserver.arneill-py.local> <AF449E25-057F-4856-AB92-1D6D19027A98@laposte.net> <392CB277BC2EAE4FB83C1206954BA6CEF63A@newserver.arneill-py.local>
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF63A@newserver.arneill-py.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.90]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 19:16:35 -0000

6rd addresses a different problem than 6to4.

6to4 is a global solution, that relies on pretty much every native IPv6 pro=
vider deploying 6to4 relays. If these relays were really well deployed and =
reliable, 6to4 would allow any router with a native IPv4 address to provide=
 IPv6 connectivity to its local users. That is, 6to4 relies on the kindness=
 of strangers and allows uncoordinated deployments by end-users.

6rd is a local solution, that can be used by providers to easily deploy IPv=
6 tunnels over their existing IPv4 infrastructure. The provider controls th=
e IPv6 prefix, which effectively defines a specific 6rd "subnet." The provi=
der also controls the deployment of relays between the 6rd subnet and the n=
ative Internet. There is no need to rely on the kindness of strangers.

In a sense, 6rd is very similar to a tunnel broker deployment, with a key i=
mprovement and an important limitation. The key improvement is the ability =
for 6rd routers in the same domain to send traffic directly at each other. =
Local traffic stays local, does not need to be relayed by the tunnel server=
s or the 6rd relays. The key limitation is that 6rd assumes direct IPv4 con=
nectivity between the participating 6rd routers, i.e. no NAT.=20

6rd is a very good solution for its intended usage, rapid deployment of IPv=
6 by IPv4 providers. But 6rd is not a replacement for the "global, uncoordi=
nated" 6to4 deployment. Hosts that really need this kind of uncoordinated g=
lobal solution will have to rely on Teredo if they cannot use 6to4. Whether=
 that's a good thing is clearly a matter of debate.


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Mic=
hel Py
Sent: Friday, July 29, 2011 11:38 AM
To: R=E9mi Despr=E9s
Cc: ietf@ietf.org; Keith Moore
Subject: RE: 6to4v2 (as in ripv2)?=20

> R=E9mi Despr=E9s wrote:
> 6rd is designed to offer native IPv6 prefixes across IPv4-only routing=20
> domains.

There is a word for that: oxymoron. In French: oxymore.
If it stops working when IPv4 is broken, it is not native.

Michel.

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf


From sm@resistor.net  Fri Jul 29 13:10:45 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 EFA6421F8B0A for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 13:10:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.905
X-Spam-Level: 
X-Spam-Status: No, score=-102.905 tagged_above=-999 required=5 tests=[AWL=-0.170, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, 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 3bi2ESzBQZ9b for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 13:10:43 -0700 (PDT)
Received: from mx.elandsys.com (ns1.qubic.net [208.69.177.116]) by ietfa.amsl.com (Postfix) with ESMTP id C310121F8B01 for <ietf@ietf.org>; Fri, 29 Jul 2011 13:10:43 -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 p6TK9O3a018201 for <ietf@ietf.org>; Fri, 29 Jul 2011 13:09:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1311970167; bh=HrfLWBiA8ATrVyj2xlFOxEMG/+kfB5UDqR6t0DuROEM=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=xacZMh9Ht1b+FgVg+e4qTCy+0Y1QgHj7fGhlJvqEbci2YQva8oTnSqH8xpVt4Hw/F 9TIDpp2ahhWMw9sIm+6z0ZKh0tSaPHkWB0YY239J7QGlMurjt+WwqM9lpA3Qruv7NZ xz1SeWRA6GSygBQKXWu0RaoTXpWt6KX46ltXJTqk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1311970167; bh=HrfLWBiA8ATrVyj2xlFOxEMG/+kfB5UDqR6t0DuROEM=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=MaJX6kympaoS2lXGCULc4r3q/dEY+bDL2xUbO6Ms6vo5Ns2G/4s8aZhMF6yQKQp0/ +r5AaPcE9K7nJILzV2gizFvt5r1jdkGpuBXPYVSWlRGspT6yxGuqzBOXU2EzgVOxyk W0PXqTcdyWsvYBlz2YhkzB/TJ9bfpUpUjsWlkrd8=
Message-Id: <6.2.5.6.2.20110728234859.075cb888@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 29 Jul 2011 12:43:43 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
In-Reply-To: <20110728020207.26024.73829.idtracker@ietfa.amsl.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 20:10:46 -0000

At 07:02 PM 7/27/2011, The IESG wrote:

>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'Reducing the Standards Track to Two Maturity Levels'
>   <draft-housley-two-maturity-levels-08.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-08-24. Exceptionally, comments may be

 From Section 2.1:

  "no existing published requirements are relaxed".

Are these published requirements BCPs?

 From Section 2.2:

   'This maturity level is a merger of Draft Standard and Standard as
    specified in RFC 2026 [1].  The chosen name avoids confusion between
    "Draft Standard" and "Internet-Draft".'

Shouldn't that be "Internet Standard" instead of "Standard"?

    "The request for reclassification is sent to the IESG along with an
     explanation of how the criteria have been met.
     The criteria are:

    (1) There are at least two independent interoperating implementations
        with widespread deployment and successful operational experience.

    (2) There are no errata against the specification that would cause a
        new implementation to fail to interoperate with deployed ones.

    (3) There are no unused features in the specification that greatly
        increase implementation complexity."

The document that has been the subject of innumerable messages 
highlights how difficult it can be to reclassify a RFC.  Moreover, it 
amplified the divide between application folks and operators.  The 
IESG could have used the review clause from RFC 2026 and:

   (i)  requested an implementation report from the people in favor of the
        proposed standard; and

   (ii) a statement about deployment to determine whether there are operational
        issues that have to be addressed.

I don't know whether application folks and operators agree that 
cross-area requires mutual understanding.

The creation of interoperable protocol implementations requires clear 
specifications.  Interoperability does not mean that the protocol 
would not have unintended effects on the network.  That is where 
operational experience comes in.  It can serve as valuable input to 
improve a specification.  For what it is worth, there approximately 
75 implementation reports have been submitted since 1996.

A two-step maturity level folds the two different classes of issues 
into one.  Quoting RFC 5657, which this draft unfortunately does not reference:

   "Moving documents along the standards track can be an important signal
    to the user and implementor communities, and the process of
    submitting a standard for advancement can help improve that standard
    or the quality of implementations that participate."

During a discussion on another mailing list, it has been mentioned 
that such an effort has a cost.  Lumping all the issues together can 
only increase that cost.

Strangely, this draft argues for measuring "interoperability through 
widespread deployment of multiple implementations from different code 
bases".  It will be more difficult to remove features once 
implementations are widely deployed.  Keeping the feature fight 
within the Draft Standard  discussion can reduce the level of 
controversy at the last step.  As a side note, it would be less 
costly if feature evaluation was based on implementations instead of 
what people would like to keep (only one implementation of a feature).

Once a Proposed Standard is published, it is expected that people 
will go and write code, if they have not done so yet, and evaluate 
whether their implementation can interoperate with other 
implementations.  I don't see anything in this draft that encourages that.

In the RFC 5000 range, there are 7 Internet Standards, 13 Draft 
Standards and 537 Proposed Standards.  One of the arguments for this 
draft is that it reduces the number of IESG evaluations, and other 
review cycles, from three to two.  Basically, this draft is to adjust 
the environment so that the IESG can review everything.  It does not 
reduce the barrier of "intended proposed standards" to the RFC 2026 
level.  It does not offer any incentive to advance document along the 
Standards Track.

I unfortunately cannot support this draft.

Regards,
-sm  


From pch-b2B3A6689@u-1.phicoh.com  Fri Jul 29 13:35:05 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 A6CCA21F8B69 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 13:35:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.949
X-Spam-Level: 
X-Spam-Status: No, score=-6.949 tagged_above=-999 required=5 tests=[AWL=0.450,  BAYES_00=-2.599, GB_I_LETTER=-2, J_CHICKENPOX_12=0.6, J_CHICKENPOX_51=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 rnhxzLO6fwLT for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 13:35:04 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id 678A021F8A4D for <ietf@ietf.org>; Fri, 29 Jul 2011 13:35:04 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #66) id m1Qmswy-0001iFC; Fri, 29 Jul 2011 21:42:24 +0200
Message-Id: <m1Qmswy-0001iFC@stereo.hq.phicoh.net>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
Subject: Re: 6to4v2 (as in ripv2)? 
From: Philip Homburg <pch-ietf@u-1.phicoh.com>
Sender: pch-b2B3A6689@u-1.phicoh.com
In-reply-to: Your message of "Fri, 29 Jul 2011 11:38:16 -0700 ." <392CB277BC2EAE4FB83C1206954BA6CEF63A@newserver.arneill-py.local> 
Date: Fri, 29 Jul 2011 21:42:07 +0200
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 20:35:05 -0000

In your letter dated Fri, 29 Jul 2011 11:38:16 -0700 you wrote:
>> R?mi Despr?s wrote:
>> 6rd is designed to offer native IPv6 prefixes
>> across IPv4-only routing domains.
>
>There is a word for that: oxymoron. In French: oxymore.
>If it stops working when IPv4 is broken, it is not native.

Could you please elaborate why expect the internal IPv4 network of an ISP
to break while they are using it for 6rd?

It there some sort of built-in self-destruct mechanism somewhere?



From Fred.L.Templin@boeing.com  Fri Jul 29 14:31:23 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 E84235E8025 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 14:31:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.302
X-Spam-Level: 
X-Spam-Status: No, score=-6.302 tagged_above=-999 required=5 tests=[AWL=-0.003, BAYES_00=-2.599, MIME_8BIT_HEADER=0.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 nYj8G4m3CZGt for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 14:31:23 -0700 (PDT)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by ietfa.amsl.com (Postfix) with ESMTP id 5003E5E8027 for <ietf@ietf.org>; Fri, 29 Jul 2011 14:31:23 -0700 (PDT)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by blv-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p6TLVBBx001445 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 29 Jul 2011 14:31:12 -0700 (PDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id p6TLVBfa028333; Fri, 29 Jul 2011 16:31:11 -0500 (CDT)
Received: from XCH-NWHT-05.nw.nos.boeing.com (xch-nwht-05.nw.nos.boeing.com [130.247.25.109]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p6TLVApM028305 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 29 Jul 2011 16:31:11 -0500 (CDT)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-05.nw.nos.boeing.com ([130.247.25.109]) with mapi; Fri, 29 Jul 2011 14:31:10 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Christian Huitema <huitema@microsoft.com>, Michel Py <michel@arneill-py.sacramento.ca.us>, =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
Date: Fri, 29 Jul 2011 14:31:10 -0700
Subject: RE: 6to4v2 (as in ripv2)? 
Thread-Topic: 6to4v2 (as in ripv2)? 
Thread-Index: AQHMS+ZmwMuKugepKkyXRofd8XRLBJUAePCAgAASXgCAADY5AIAC+L4AgAA6SACAAAgzgIAAHicA//+RA3CAACbSUA==
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65C76FB9A71@XCH-NW-01V.nw.nos.boeing.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com>	<4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net><4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com><72A76FC2-CA5F-4DD5-91FF-280B6A42268B@cisco.com> <5A600744-8605-46D3-82B2-C3C30E30E4AC@network-heretics.com> <392CB277BC2EAE4FB83C1206954BA6CEF625@newserver.arneill-py.local> <4E656E6D-EA61-48E7-BF06-6F038777FA70@laposte.net> <392CB277BC2EAE4FB83C1206954BA6CEF639@newserver.arneill-py.local> <AF449E25-057F-4856-AB92-1D6D19027A98@laposte.net> <392CB277BC2EAE4FB83C1206954BA6CEF63A@newserver.arneill-py.local> <22F6318E46E26B498ABC828879B08D4F1DAF89@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <22F6318E46E26B498ABC828879B08D4F1DAF89@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.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
Cc: "ietf@ietf.org" <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 21:31:24 -0000

Christian,

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On=20
> Behalf Of Christian Huitema
> Sent: Friday, July 29, 2011 12:17 PM
> To: Michel Py; R=E9mi Despr=E9s
> Cc: ietf@ietf.org; Keith Moore
> Subject: RE: 6to4v2 (as in ripv2)?=20
>=20
> 6rd addresses a different problem than 6to4.
>=20
> 6to4 is a global solution, that relies on pretty much every=20
> native IPv6 provider deploying 6to4 relays. If these relays=20
> were really well deployed and reliable, 6to4 would allow any=20
> router with a native IPv4 address to provide IPv6=20
> connectivity to its local users. That is, 6to4 relies on the=20
> kindness of strangers and allows uncoordinated deployments by=20
> end-users.
>=20
> 6rd is a local solution, that can be used by providers to=20
> easily deploy IPv6 tunnels over their existing IPv4=20
> infrastructure. The provider controls the IPv6 prefix, which=20
> effectively defines a specific 6rd "subnet." The provider=20
> also controls the deployment of relays between the 6rd subnet=20
> and the native Internet. There is no need to rely on the=20
> kindness of strangers.

I think this is well said. Another way of saying the
same thing is that 6to4 is an inter-site solution while
6rd is an intra-site solution when considering the
provider network as a "site". With extensions, ISATAP
can also satisfy this provider network intra-site
requirement (see draft-templin-isupdate) while enabling
the desired IPv6 services for end-user sites.

Thanks - Fred
fred.l.templin@boeing.com

> In a sense, 6rd is very similar to a tunnel broker=20
> deployment, with a key improvement and an important=20
> limitation. The key improvement is the ability for 6rd=20
> routers in the same domain to send traffic directly at each=20
> other. Local traffic stays local, does not need to be relayed=20
> by the tunnel servers or the 6rd relays. The key limitation=20
> is that 6rd assumes direct IPv4 connectivity between the=20
> participating 6rd routers, i.e. no NAT.=20
>=20
> 6rd is a very good solution for its intended usage, rapid=20
> deployment of IPv6 by IPv4 providers. But 6rd is not a=20
> replacement for the "global, uncoordinated" 6to4 deployment.=20
> Hosts that really need this kind of uncoordinated global=20
> solution will have to rely on Teredo if they cannot use 6to4.=20
> Whether that's a good thing is clearly a matter of debate.
>=20
>=20
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On=20
> Behalf Of Michel Py
> Sent: Friday, July 29, 2011 11:38 AM
> To: R=E9mi Despr=E9s
> Cc: ietf@ietf.org; Keith Moore
> Subject: RE: 6to4v2 (as in ripv2)?=20
>=20
> > R=E9mi Despr=E9s wrote:
> > 6rd is designed to offer native IPv6 prefixes across=20
> IPv4-only routing=20
> > domains.
>=20
> There is a word for that: oxymoron. In French: oxymore.
> If it stops working when IPv4 is broken, it is not native.
>=20
> Michel.
>=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
> =

From marka@isc.org  Fri Jul 29 18:16:44 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 4432B21F8BF6; Fri, 29 Jul 2011 18:16:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.561
X-Spam-Level: 
X-Spam-Status: No, score=-6.561 tagged_above=-999 required=5 tests=[AWL=4.038,  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 tVlXJCDWlsUy; Fri, 29 Jul 2011 18:16:34 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) by ietfa.amsl.com (Postfix) with ESMTP id 2937D21F8BF3; Fri, 29 Jul 2011 18:16:33 -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 997965F98E9; Sat, 30 Jul 2011 01:14:53 +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 EC7C2216C84; Sat, 30 Jul 2011 01:14:50 +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 05D3212542D0; Sat, 30 Jul 2011 11:06:25 +1000 (EST)
To: Jeroen Massar <jeroen@unfix.org>
From: Mark Andrews <marka@isc.org>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <968F0B1C-D082-4A59-8213-FD58C74AF89D@nominum.com> <20110727151517.CF9371235D70@drugs.dv.isc.org> <D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk> <EMEW3|fcf145b5033ff99790b7c34003f47686n6QGZC03tjc|ecs.soton.ac.uk|D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk> <999C3229-649D-4242-BB0F-2BB494EDF1D9@network-heretics.com> <4E305E3E.2040607@unfix.org> <20110727233634.406021238970@drugs.dv.isc.org> <4E3127F1.2030708@unfix.org>
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
In-reply-to: Your message of "Thu, 28 Jul 2011 11:12:17 +0200." <4E3127F1.2030708@unfix.org>
Date: Sat, 30 Jul 2011 11:06:25 +1000
Message-Id: <20110730010626.05D3212542D0@drugs.dv.isc.org>
Cc: IPv6 Operations <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: Sat, 30 Jul 2011 01:16:44 -0000

In message <4E3127F1.2030708@unfix.org>, Jeroen Massar writes:
> On 2011-07-28 01:36 , Mark Andrews wrote:
> [..]
> > Is there *one* tunnel management protocol that they all support or
> > does a cpe vendor have to implement multiple ones to reach them
> > all?  I'm pretty sure I know the answer to this question but I'd
> > love to be proved wrong.
> 
> There is no 'one' solution to the problems that they are solving.
> 
> As such there tend to be a combo of:
>  - static proto-41 tunnel
>  - 6to4
>  - 6rd
>  - TSP => dynamic NATted addresses
>  - proto-41 + heartbeat + TIC => dynamic public addresses
>  - AYIYA + TIC => dynamic NATted addresses

I was more thinking about commonality with tunnel brokers.

6rd is not a replacement for 6to4 as it requires ISP involment or
someone to create a registry of 3rd party 6rd providers along with
associated parameters sets similar non anycast 6to4.  static proto-41
tunnel is also not a viable replacement as it doesn't handle address
reassignment at the CPE end.

> TSP conveys configurartion information inline with the UDP packets.
> TIC is solely for configuration information and does not do tunneling
> but can be used for all proto-41/heartbeat/AYIYA protocols (and for
> instance AVM chose to only do proto-41 + heartbeat as their devices
> always have public IPv4 IPs).
> 
> Teredo is only for a single host thus is not useful for CPEs and thus
> not included in them.
> 
> > One of the advantages of 6to4 anycast is that it is just needs a
> > check box to turn on and off.  Everybody speaks the same thing.
> 
> Except that it does not work behind a NAT and most people do sit behind
> a NAT.
> 
> Next to that those anycasts are even rarer around the world and on top
> of that it is hard to figure out issues when they are there (although
> some people have tricks to apparently debug them, the anycast on both
> IPv4 and IPv6 requires one to contact a lot of folks).
> 
> The big advantage over a known tunnel endpoint is the known behavior of
> that endpoint and the simple way of complaining when something is
> broken. And people fortunately do complain when stuff is broken,
> unfortunately not always with the proper details though, but I am to
> blame for not finishing that program up...
> 
> > Another advantage of 6to4 is it doesn't require manual intervention
> > on renumber events.  Manual tunnel don't pass muster.
> 
> I guess you are one of the lucky people to get a public static IPv4
> address prefix at home that never renumbers? Guess what, most of the
> world does not have that luxury, they get 1 dynamic address and for
> instance in Germany they get a disconnect/force-renumber every 24 hours
> (according to the ISPs because of 'accounting' reasons...)
> 
> Do realize that when you have that public IPv4 address, when it changes
> you are renumbering your 2002:<ipv4>::/48 prefix everywhere. Fun...
> (I hope you also like asking 6to4.nro.net everytime to change your reverse)
> 
> The tunnels above all have ISP-supplied prefixes and tend to be static
> (I think TSP anonymous tunnels rotate addresses, but the majority just
> keeps on returning the same static allocation, in the case of SixXS you
> really get a fixed address, much easier on the PoP side and we can do
> whois and store it in the relevant RIR registry)
> 
> > Another advantage of 6to4 is you don't have to register.  For most of
> > the tunnel brokers you have to register.
> 
> I guess you also where able to anonymously sign up to your IPv4 ISP!? :)
> Especially that static IPv4 address must be wonderful to get that way.
> 
> Note that Freenet6 offers 'anonymous' tunnels, thus that is just a TSP away.
> 
> Something with the amounts of abuse made us (SixXS) require that we
> require valid address data. Next to that it is a RIPE requirement to
> register /48 prefixes. Other Tunnelbrokers just started blocking things
> like IRC and NNTP because there was too much abuse or traffic....
> We kill off accounts of people when they abuse, google my name and you
> will find various people who where caught in the act and are quite mad
> that they can't have funny vhosts on IRC anymore and attract 500mbit
> DoSses and other such nonsense which are not the goal of providing IPv6.
> 
> Also, the registration means that people can just type in their
> username/password (and optionally which tunnel they want to use out of
> the multiple tunnels they might have) in their CPE and the CPE then uses
> TIC or TSP to fetch this configuration and set it all up, and it will
> just work(tm).
> 
> As a nice example see http://www.sixxs.net/wiki/images/FritzboxHowto.jpg
> and
> http://www.sixxs.net/wiki/Fritz!Box_7270
> 
> Next to that knowing where the user is and more importantly their
> endpoint allows one to select a proper PoP for that user close to their
> endpoint causing low latency and generally high throughput.
> 
> With anycast you are just hoping that that all will work.
> 
> Greets,
>  Jeroen
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From michel@arneill-py.sacramento.ca.us  Fri Jul 29 19:31:14 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 5006F21F8BBA for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 19:31:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.148
X-Spam-Level: 
X-Spam-Status: No, score=-2.148 tagged_above=-999 required=5 tests=[AWL=0.117,  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 Fkdbb2aVYXaG for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 19:31:13 -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 BAEB921F8BB8 for <ietf@ietf.org>; Fri, 29 Jul 2011 19:31:13 -0700 (PDT)
Subject: What is Native IPv6
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 29 Jul 2011 19:31:13 -0700
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF63B@newserver.arneill-py.local>
Content-class: urn:content-classes:message
In-Reply-To: <38D0CD11-F193-4D1B-951A-332C24AFBC7E@employees.org>
X-MS-Has-Attach: 
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-MS-TNEF-Correlator: 
Thread-Topic: What is Native IPv6
Thread-Index: AcxN4FUQnZKWM6AwS46IyZPF6nDHaQAd3ywg
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com><4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>	<4E2EDF23.3060804@gmail.com><4E2F4491.30102@gmail.com>	<20110727023833.5C72D1232958@drugs.dv.isc.org>	<m1QlzXt-0001gSC@stereo.hq.phicoh.net>	<2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com>	<392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local>	<10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com>	<CAKD1Yr3gv=+HfEZMsU0enNh8OQbemQh6iRzpGHsnmr7OJrTcFg@mail.gmail.com>	<392CB277BC2EAE4FB83C1206954BA6CEF635@newserver.arneill-py.local>	<3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk><EMEW3|fa0511c175232cff9b9cb8310f081538n6RMCh03tjc|ecs.soton.ac.uk|3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk> <4E31F3C2.4000000@gmail.com> <392CB277BC2EAE4FB83C1206954BA6CEF637@newserver.arneill-py.local> <6E140BC3-0C38-453B-A557-A929EDC33A09@bogus.com> <392CB277BC2EAE4FB83C1206954BA6CEF 638@news erver.arneil l-py.local> <38D0CD11-F193-4D1B-951A-332C24AFBC7E@employees.org>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Ole Troan" <otroan@employees.org>
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 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, 30 Jul 2011 02:31:14 -0000

Ole,

> Ole Troan wrote:
> I presume you are arguing that MPLS (6PE) is not native either?

That's a tough one.

What would make me say it is native is: MPLS is a L2/switching animal,
not a L3/routing one. In theory you can bind any L3 protocol such as
IPv4, IPv6, IPX, Appletalk, etc to it. So the MPLS interface is very
similar in some aspects to a real physical interface such as Ethernet or
HSSI. It reminds me of a frame-relay sub-interface in a past life.

What would make me say it is not native is: you can't remove IPv4 out of
the equation. Frame relay does not even know about which L3 protocols it
transports, while MPLS is kinda going the reverse way in the stack: it
uses L3 packets/datagrams to encapsulate and transport "L2 frames".


Here's my take:
- You can have native IPv6 over Ethernet or HDLC or Sonet or any other
L2 technology.

- Saying you have native IPv6 over fiber or copper is incorrect; you
have native IPv6 over GigE over {singlemode|multimode} (*) fiber or you
have IPv6 over Ethernet over GigE over (*) copper (or other examples)
(*) insert the appropriate 802.x standard

- I like the idea of being native requiring the IPv6 to be bound to a L2
interface. The gray area with 6PE is that the interface is logical, not
physical.

- Native IPv6 over a 6to4 or a 6RD or any kind of L3-L3 tunnel is an
oxymoron.



In other words: native IPv6 means:
a) IPv6 has to be bound to a L2 interface.
b) That interface can NOT be a tunnel interface using another L3
protocol such as IPv4.

Up for grabs:

- c1) Is it acceptable to have a structural requirement to use IPv4
(which would mean 6PE is native) or c2) is it a requirement that the
entire infrastructure (in the case of 6RD, the ISP's infrastructure)
supports IPv6 (which would mean that 6PE is not native).

Food for thought:=20

- If c2) is chosen, I would consider rephrasing a) so it becomes "IPv6
has to be bound to a PHYSICAL L2 interface". Rationale: besides 6PE, are
there any other gray area candidates?

- If one is in the business of writing an draft about "what is native
IPv6", and if one of the draft's goals is to reach -cough- consensus
-cough-, one may consider "forgetting" the 6PE classification
altogether. The one part that is not open for grabs with me is
classifying 6RD as native.


Michel.


From john_brzozowski@cable.comcast.com  Fri Jul 29 21:33:50 2011
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF1A521F8C9D for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 21:33:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.538
X-Spam-Level: 
X-Spam-Status: No, score=-102.538 tagged_above=-999 required=5 tests=[AWL=-0.804, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t2rbV90Owqdd for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 21:33:44 -0700 (PDT)
Received: from cable.comcast.com (copdcimo01.potomac.co.ndcwest.comcast.net [76.96.32.251]) by ietfa.amsl.com (Postfix) with ESMTP id 80BE621F8CA2 for <ietf@ietf.org>; Fri, 29 Jul 2011 21:33:44 -0700 (PDT)
Received: from ([24.40.55.42]) by copdcimo01.cable.comcast.com with ESMTP with TLS id 5503630.46805489; Fri, 29 Jul 2011 22:38:23 -0600
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by PACDCEXHUB01.cable.comcast.com ([fe80::d1e7:20b5:9b63:21a6%11]) with mapi id 14.01.0289.001; Sat, 30 Jul 2011 00:33:31 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: George Michaelson <ggm+ietf@apnic.net>, Joel Jaeggli <joelja@bogus.com>
Subject: Re: IPv6 traffic distribution
Thread-Topic: IPv6 traffic distribution
Thread-Index: AQHMTWTAiNxrce4jQKmT0yuPtdux5pUCeI+AgAAF3ICAACm2AIAAQvQAgAAL3QCAAA4KgIAAcl8AgAADgoCAAHN/AA==
Date: Sat, 30 Jul 2011 04:33:30 +0000
Message-ID: <CA58B5CC.156099%john_brzozowski@cable.comcast.com>
In-Reply-To: <91527B3C-A687-4750-A8AA-A5E9C0F3FDDC@apnic.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.12.0.110505
x-originating-ip: [147.191.125.11]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <EEEFD3245E0BE24DBFC59FFE559F91B7@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Michel Py <michel@arneill-py.sacramento.ca.us>, Tim Chown <tjc@ecs.soton.ac.uk>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jul 2011 04:33:51 -0000

The Comcast 6rd trial will conclude very soon, so I do not recommend doing
anything specific for Comcast 6rd.

John
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D




On 7/29/11 8:16 AM, "George Michaelson" <ggm+ietf@apnic.net> wrote:

>
>On 29/07/2011, at 8:03 AM, Joel Jaeggli wrote:
>
>> agree but if you're trying to discriminate it by:
>>=20
>> "This graph shows the daily unique queried reverse addresses by type."
>>=20
>> you can't.
>>=20
>
>
>Very true Joel. I did, for a while, pattern match the 6rd prefix from
>Free.FR's declared ranges in RIPE whois but it was pointed out to me that
>dealing with one ISP like this skews things.
>
>After all, other ISps also deploy 6rd, and Comcast do some kind of
>related work.
>
>I can put in a 6rd line, if thats what people *want*
>
>-G
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf


From hsantos@isdg.net  Fri Jul 29 22:41:38 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 B330F21F8CC5 for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 22:41:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.936
X-Spam-Level: 
X-Spam-Status: No, score=-3.936 tagged_above=-999 required=5 tests=[AWL=-1.337, 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 LHCFzk+0Nfrk for <ietf@ietfa.amsl.com>; Fri, 29 Jul 2011 22:41:37 -0700 (PDT)
Received: from secure.winserver.com (listserv.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 86C6B21F8CBB for <ietf@ietf.org>; Fri, 29 Jul 2011 22:41:36 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1698; t=1312004493; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=/PPa4b2S6DO3StYKBgG7PJ5k5mc=; b=fBknzBQMfM1basYf/J3t zGKOUbXkqbfT8wCqUVjuU4D3GqUHvHArEuq/wiBqr6X7P0S2w6XhwIzkJsrT9soq jqmmTFt0JumF2afBarP708O3i5a7pRDfyTRk2Tk8thVqdzCyRSfHiFqFsfKxODfN mgjJmVbv7eSHjJKkP6R5VKY=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Sat, 30 Jul 2011 01:41:33 -0400
Authentication-Results: dkim.winserver.com; dkim=fail (DKIM_SELECTOR_DNS_PERM_FAILURE) header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=fail policy=all author.d=isdg.net asl.d=beta.winserver.com (unauthorized signer); 
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 459981198.26252.3764; Sat, 30 Jul 2011 01:41:31 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; t=1312004228; h=Received:Received:Message-ID: Date:From:Organization:To:Subject:List-ID; bh=XsiuiyhJChhBBhpHEh G0qsnW2W2Kx2Nal/slCiXVkSo=; b=SPwlFzBoo08F9OGHSbdgWtAB/+yIuLlgyz T2Gv0/7NWIN1FpemRzaO8KexECDkDArOXZPg5uwfgSWnmxwQOsol0Ze0GhamywKq 14Uw6zr/l18JUDpHoSC5lOOPEE9ENd3ts5NVsNeWo0szzRuLA7hmX2AA3XKp1zwY co95pNkEo=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Sat, 30 Jul 2011 01:37:08 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1431265705.2963.3844; Sat, 30 Jul 2011 01:37:06 -0400
Message-ID: <4E3399AB.5080801@isdg.net>
Date: Sat, 30 Jul 2011 01:42:03 -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: "t.petch" <daedulus@btconnect.com>
Subject: Re: DKIM Signatures now being applied to IETF Email
References: <20110725171748.GA13506@amsl.com>	<4E2DAF60.8030307@dcrocker.net><4E2FFFDF.2080601@ieca.com><005d01cc4d44$3136eda0$4001a8c0@gateway.2wire.net>	<4E3288EE.9050201@dcrocker.net> <006101cc4dea$2c9bdd40$4001a8c0@gateway.2wire.net>
In-Reply-To: <006101cc4dea$2c9bdd40$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: dcrocker@bbiw.net, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jul 2011 05:41:38 -0000

t.petch wrote:

> It functions, but does not work, in that it tells me nothing about the true
> origin of the communication.

Yes and No and that the main problem with DKIM, which I see is the 
lack of 3rd party signal controls or put another way - anyone, middle 
ware and especially list servers can blindly DKIM resign mail without 
restrictions.  That lack of control has cause originating authoring 
domains, copyright holders of mail, all benefits of supporting DKIM.

The current approach is that original domains no longer have any 
rights whatsoever to declare they are the only signers allowed to sign 
mail and any deviation from that expectation should be indication of 
protocol failure - "Reject it!"

Unfortunately, in order to allow a list server or any 3rd party 
middleware to exist with DKIM (re)signing features, it needs to ignore 
any original DKIM domain signing practice or expectations.

No domain that wishes exclusive signing operations should be sending 
their signed mail to a public service forum.   We know this, but we 
don't have the controls to disallow faults or bad guys attempting to 
create a facsimile of your domain signed mail in public areas or 
directly to others.

Finally, as DKIM was revamped from secured Author-Domain signing 
protocol to a "anyone can signed" 3rd party Trust vendor protocol, the 
problem we face is we don't have consistency with 3rd party trust 
tables.   For DKIM to work, every validators needs a copy of the same 
trust tables.  DKIM is a protocol that requires Batteries in order to 
work and everyone must use the same batteries.


-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com





From prvs=119257c7bb=jordi.palet@consulintel.es  Sat Jul 30 02:45:52 2011
Return-Path: <prvs=119257c7bb=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56D0921F8A51 for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 02:45:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.462
X-Spam-Level: 
X-Spam-Status: No, score=-104.462 tagged_above=-999 required=5 tests=[AWL=-2.137, BAYES_00=-2.599, DATE_IN_FUTURE_03_06=0.274, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vbxHDnujvRsb for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 02:45:51 -0700 (PDT)
Received: from consulintel.es (gr2000.consulintel.es [213.172.48.138]) by ietfa.amsl.com (Postfix) with ESMTP id BB33A21F886E for <ietf@ietf.org>; Sat, 30 Jul 2011 02:45:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1312018642; x=1312623442; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: In-Reply-To:Mime-version:Content-type:Content-transfer-encoding: Reply-To; bh=DyVUbKUxYrxNBsYD5SY9FYGvb7HICZVf4yMEgvpdcZM=; b=nKN GE46aubmml8mz8+TTcvfqxJRtGriouqKZ2RBuRqOqVfm9aKwuWeXY4V0U43TN8wy v9W8DoSXdx33Tms6F8V1SyjaZlLaw9CGjRILINoQoZb7QG97nVIwHMW+FXoseZ3i SNppZv0sRrsLvxb9OGW+l4GXs41nFW/fizLMixoI=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=qsdYmGYF9QwdGocJ6TWOjaxDmqtd56P0uT+iaKOuZvoLobb1dh4fIIDhTRdX bEn6GZO4DvW/MRWcjZTsD9a4OAhJaD1iYx4TK7Nxtt05Y02tp2xpvOMDe w8Z38nB/onT+wPGOr4jch8eusLJnz6eTqk8Gzb1DjZ0SnbPihdl9UQ=;
X-MDAV-Processed: consulintel.es, Sat, 30 Jul 2011 11:37:22 +0200
Received: from [10.1.0.16] by consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50003954828.msg for <ietf@ietf.org>; Sat, 30 Jul 2011 11:37:22 +0200
X-Spam-Processed: consulintel.es, Sat, 30 Jul 2011 11:37:22 +0200 (not processed: message from trusted or authenticated source)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:110730:md50003954828::qaoYVmsfQ1FvnDQc:00005Wwd
X-MDRemoteIP: 94.175.239.226
X-Return-Path: prvs=119257c7bb=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/14.12.0.110505
Date: Sat, 30 Jul 2011 10:45:27 -0400
Subject: Re: What is Native IPv6
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IETF Discussion <ietf@ietf.org>
Message-ID: <CA599052.495A5%jordi.palet@consulintel.es>
Thread-Topic: What is Native IPv6
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF63B@newserver.arneill-py.local>
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
Reply-To: jordi.palet@consulintel.es
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2011 09:45:52 -0000

However, for what it matters here, 6rd is native after exiting from the
ISP, same as 6to4 is native after exiting from the 6to4 relay.

As we may not be able to know how "much" of the "native" IPv6 traffic is
6rd in the last mile, I think we should consider all 6rd traffic as native
for those measurements, otherwise, we will be biasing the data. Even it
may be the case of an ISP using 6rd for some part of its network, and
native for the other.

We may need to state "IPv6 native as measured, may be encapsulated in the
last mile".

Regards,
Jordi






-----Mensaje original-----
De: Michel Py <michel@arneill-py.sacramento.ca.us>
Responder a: <michel@arneill-py.sacramento.ca.us>
Fecha: Fri, 29 Jul 2011 19:31:13 -0700
Para: Ole Troan <otroan@employees.org>
CC: Tim Chown <tjc@ecs.soton.ac.uk>, IETF Discussion <ietf@ietf.org>
Asunto: What is Native IPv6

>Ole,
>
>> Ole Troan wrote:
>> I presume you are arguing that MPLS (6PE) is not native either?
>
>That's a tough one.
>
>What would make me say it is native is: MPLS is a L2/switching animal,
>not a L3/routing one. In theory you can bind any L3 protocol such as
>IPv4, IPv6, IPX, Appletalk, etc to it. So the MPLS interface is very
>similar in some aspects to a real physical interface such as Ethernet or
>HSSI. It reminds me of a frame-relay sub-interface in a past life.
>
>What would make me say it is not native is: you can't remove IPv4 out of
>the equation. Frame relay does not even know about which L3 protocols it
>transports, while MPLS is kinda going the reverse way in the stack: it
>uses L3 packets/datagrams to encapsulate and transport "L2 frames".
>
>
>Here's my take:
>- You can have native IPv6 over Ethernet or HDLC or Sonet or any other
>L2 technology.
>
>- Saying you have native IPv6 over fiber or copper is incorrect; you
>have native IPv6 over GigE over {singlemode|multimode} (*) fiber or you
>have IPv6 over Ethernet over GigE over (*) copper (or other examples)
>(*) insert the appropriate 802.x standard
>
>- I like the idea of being native requiring the IPv6 to be bound to a L2
>interface. The gray area with 6PE is that the interface is logical, not
>physical.
>
>- Native IPv6 over a 6to4 or a 6RD or any kind of L3-L3 tunnel is an
>oxymoron.
>
>
>
>In other words: native IPv6 means:
>a) IPv6 has to be bound to a L2 interface.
>b) That interface can NOT be a tunnel interface using another L3
>protocol such as IPv4.
>
>Up for grabs:
>
>- c1) Is it acceptable to have a structural requirement to use IPv4
>(which would mean 6PE is native) or c2) is it a requirement that the
>entire infrastructure (in the case of 6RD, the ISP's infrastructure)
>supports IPv6 (which would mean that 6PE is not native).
>
>Food for thought: 
>
>- If c2) is chosen, I would consider rephrasing a) so it becomes "IPv6
>has to be bound to a PHYSICAL L2 interface". Rationale: besides 6PE, are
>there any other gray area candidates?
>
>- If one is in the business of writing an draft about "what is native
>IPv6", and if one of the draft's goals is to reach -cough- consensus
>-cough-, one may consider "forgetting" the 6PE classification
>altogether. The one part that is not open for grabs with me is
>classifying 6RD as native.
>
>
>Michel.
>
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




From rogerj@gmail.com  Sat Jul 30 04:01:22 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 BD22521F898E for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 04:01:22 -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.069,  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 FvQHnHF8SukM for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 04:01:21 -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 DEA5D21F8867 for <ietf@ietf.org>; Sat, 30 Jul 2011 04:01:20 -0700 (PDT)
Received: by wyj26 with SMTP id 26so335378wyj.31 for <ietf@ietf.org>; Sat, 30 Jul 2011 04:01: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 :cc:content-type:content-transfer-encoding; bh=92RE1/gnIYi0mWHSEHyxGQ4u+PDB3I8rZimrbz0c86M=; b=Qa0gUtrrGUcxywfZhX1Qe7JVZePHBbi0UY+S5wVh05XoiOQBHTidWXRs0IV32c7uzR ndX3plIKd+r2G2gjFVpSPIDBCvyficlNaGh07OVlHntrLY3OVcqNOQBmymrL7UqjdrEV Ej9T+27r0bedhAZd0ZQ1eBYz6SlJFXOkXsIzI=
MIME-Version: 1.0
Received: by 10.227.60.201 with SMTP id q9mr3329919wbh.52.1312023680462; Sat, 30 Jul 2011 04:01:20 -0700 (PDT)
Received: by 10.227.141.74 with HTTP; Sat, 30 Jul 2011 04:01:20 -0700 (PDT)
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF63B@newserver.arneill-py.local>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <m1QlzXt-0001gSC@stereo.hq.phicoh.net> <2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com> <392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local> <10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com> <CAKD1Yr3gv=+HfEZMsU0enNh8OQbemQh6iRzpGHsnmr7OJrTcFg@mail.gmail.com> <392CB277BC2EAE4FB83C1206954BA6CEF635@newserver.arneill-py.local> <3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk> <EMEW3|fa0511c175232cff9b9cb8310f081538n6RMCh03tjc|ecs.soton.ac.uk|3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk> <4E31F3C2.4000000@gmail.com> <392CB277BC2EAE4FB83C1206954BA6CEF637@newserver.arneill-py.local> <6E140BC3-0C38-453B-A557-A929EDC33A09@bogus.com> <38D0CD11-F193-4D1B-951A-332C24AFBC7E@employees.org> <392CB277BC2EAE4FB83C1206954BA6CEF63B@newserver.arneill-py.local>
Date: Sat, 30 Jul 2011 13:01:20 +0200
Message-ID: <CAKFn1SFKqQZp_pQQyJtRYqSwi1=iYEL=rvsXy0rOmb-tU6oFVA@mail.gmail.com>
Subject: Re: What is Native IPv6
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Michel Py <michel@arneill-py.sacramento.ca.us>, jordi.palet@consulintel.es
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: Sat, 30 Jul 2011 11:01:22 -0000

On Sat, Jul 30, 2011 at 4:31 AM, Michel Py
<michel@arneill-py.sacramento.ca.us> wrote:
> Ole,
>> Ole Troan wrote:
>> I presume you are arguing that MPLS (6PE) is not native either?
> That's a tough one.
>
> What would make me say it is native is: MPLS is a L2/switching animal,
> not a L3/routing one. In theory you can bind any L3 protocol such as
> IPv4, IPv6, IPX, Appletalk, etc to it. So the MPLS interface is very
> similar in some aspects to a real physical interface such as Ethernet or
> HSSI. It reminds me of a frame-relay sub-interface in a past life.
>
> What would make me say it is not native is: you can't remove IPv4 out of
> the equation. Frame relay does not even know about which L3 protocols it
> transports, while MPLS is kinda going the reverse way in the stack: it
> uses L3 packets/datagrams to encapsulate and transport "L2 frames".
>
> Here's my take:
> - You can have native IPv6 over Ethernet or HDLC or Sonet or any other
> L2 technology.
>
> - Saying you have native IPv6 over fiber or copper is incorrect; you
> have native IPv6 over GigE over {singlemode|multimode} (*) fiber or you
> have IPv6 over Ethernet over GigE over (*) copper (or other examples)
> (*) insert the appropriate 802.x standard
>
> - I like the idea of being native requiring the IPv6 to be bound to a L2
> interface. The gray area with 6PE is that the interface is logical, not
> physical.
>
> - Native IPv6 over a 6to4 or a 6RD or any kind of L3-L3 tunnel is an
> oxymoron.
>
>
>
> In other words: native IPv6 means:
> a) IPv6 has to be bound to a L2 interface.
> b) That interface can NOT be a tunnel interface using another L3
> protocol such as IPv4.
>
> Up for grabs:
>
> - c1) Is it acceptable to have a structural requirement to use IPv4
> (which would mean 6PE is native) or c2) is it a requirement that the
> entire infrastructure (in the case of 6RD, the ISP's infrastructure)
> supports IPv6 (which would mean that 6PE is not native).
>
> Food for thought:
>
> - If c2) is chosen, I would consider rephrasing a) so it becomes "IPv6
> has to be bound to a PHYSICAL L2 interface". Rationale: besides 6PE, are
> there any other gray area candidates?
>
> - If one is in the business of writing an draft about "what is native
> IPv6", and if one of the draft's goals is to reach -cough- consensus
> -cough-, one may consider "forgetting" the 6PE classification
> altogether. The one part that is not open for grabs with me is
> classifying 6RD as native.

let me try to write all of the above in my own wording to see if I
understand what you mean...

Anything doing translation L3 <> L3 is not native, that's an easy one.
It mean IPv4 running on top of IPv6, IPv6 running on top of IPv4 is
not native.  But this easy way of seeing it only affect IPv4 and IPv6,
not all of the others.

As you said somewhere in there, anything attached to a L2 interface is
L3 and in that respect native as long as the transport from that L2
interface do not require other L3 protocols to work?
(of course it gets hairy when you involve MPLS according to Michel's
text above....)



When Jordi says:
"However, for what it matters here, 6rd is native after exiting from the
ISP, same as 6to4 is native after exiting from the 6to4 relay."

That fails the first one, it is _translated_ on L3 and is because of
that not native, even if the transportation of the packet after the
translation is 100% native as in not require another L3 protocol to
work.



I guess it all boils down to, are we talking about end to end native,
or the transportation of the L3 protocol being native?

--=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 daedulus@btconnect.com  Sat Jul 30 04:29:27 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 B4AFC21F885C for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 04:29:27 -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 7b-jfAMibktl for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 04:29:27 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr08.btconnect.com [213.123.26.186]) by ietfa.amsl.com (Postfix) with ESMTP id CF57021F8853 for <ietf@ietf.org>; Sat, 30 Jul 2011 04:29:26 -0700 (PDT)
Received: from host109-153-78-164.range109-153.btcentralplus.com (HELO pc6) ([109.153.78.164]) by c2beaomr08.btconnect.com with SMTP id DTV39908; Sat, 30 Jul 2011 12:29:23 +0100 (BST)
Message-ID: <00ad01cc4ea3$1e06ce20$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Barry Leiba" <barryleiba@computer.org>
References: <20110725171748.GA13506@amsl.com><4E2DAF60.8030307@dcrocker.net><4E2FFFDF.2080601@ieca.com><005d01cc4d44$3136eda0$4001a8c0@gateway.2wire.net><4E3288EE.9050201@dcrocker.net><006101cc4dea$2c9bdd40$4001a8c0@gateway.2wire.net> <CAC4RtVDSHEhcffUx=+Y2vORb1TBmgs=XmGrvJgAc1upo-5SbEQ@mail.gmail.com>
Subject: Re: DKIM Signatures now being applied to IETF Email
Date: Sat, 30 Jul 2011 12:26:13 +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.4E33EB13.0055, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.7.30.110614:17:7.586, ip=109.153.78.164, 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_WWW, __URI_NO_PATH, __FRAUD_TRUST, __INT_PROD_COMP, BODY_SIZE_1700_1799, BODYTEXTP_SIZE_3000_LESS, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_2000_LESS, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr08.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0202.4E33EB13.0140,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@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2011 11:29:27 -0000

----- Original Message -----
From: "Barry Leiba" <barryleiba@computer.org>
To: "t.petch" <daedulus@btconnect.com>
Cc: "ietf" <ietf@ietf.org>
Sent: Friday, July 29, 2011 5:02 PM

> I think that it is an error for the IETF to add DKIM signatures. They do
indeed
> tell me
> which intermediary has sent me the mail, but does nothing for the 'spam' that
> the
> intermediary accepted in the first place (albeit there being little of that on
> the IETF
> managed lists).
...
> It functions, but does not work, in that it tells me nothing about the true
> origin of the communication.

What it does is allow you to assure yourself that the message was,
indeed, from an IETF mailing list (well, from an IETF email server),
and that it wasn't that someone tried to spoof that.  That, in turn,
allows you to confidently increase your trust that the message is not
spam in proportion to your confidence in the IETF's spam-filtering
capabilities.

Some of us, at least, find that useful.  Some of us might even
completely white-list IETF-signed messages.  You can make your own
choice on that.

<tp>
Yes, I do understand that - having read the first round of DKIM RFC
when they came out all those years ago - and do see it as a useful
tool for improving the security of e-mail and I should have made
that clearer in my first e-mail.

Sadly, I do not see it being used in the mailing lists where an
organisation is sending me directly data I would like to be able to rely on
- which I think fits the applicability well - and instead, I see it
being used on a mailing list such as those in the IETF where I
believe that the costs outweigh the benefits - and I have no choice
about that:-(.

Tom Petch

Barry, DKIM WG chair


From dhc2@dcrocker.net  Sat Jul 30 04:45:30 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 E465A21F89BE for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 04:45:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.224
X-Spam-Level: 
X-Spam-Status: No, score=-6.224 tagged_above=-999 required=5 tests=[AWL=-0.225, BAYES_00=-2.599, J_CHICKENPOX_15=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 o48jI6fcYh+c for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 04:45:30 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4C0AF21F89A1 for <ietf@ietf.org>; Sat, 30 Jul 2011 04:45:30 -0700 (PDT)
Received: from [172.16.59.36] (modemcable252.155-70-69.static.videotron.ca [69.70.155.252]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p6UBjNUQ027930 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Sat, 30 Jul 2011 04:45:30 -0700
Message-ID: <4E33EECF.5020708@dcrocker.net>
Date: Sat, 30 Jul 2011 07:45:19 -0400
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DKIM Signatures now being applied to IETF Email
References: <20110725171748.GA13506@amsl.com><4E2DAF60.8030307@dcrocker.net><4E2FFFDF.2080601@ieca.com><005d01cc4d44$3136eda0$4001a8c0@gateway.2wire.net><4E3288EE.9050201@dcrocker.net><006101cc4dea$2c9bdd40$4001a8c0@gateway.2wire.net> <CAC4RtVDSHEhcffUx=+Y2vORb1TBmgs=XmGrvJgAc1upo-5SbEQ@mail.gmail.com> <00ad01cc4ea3$1e06ce20$4001a8c0@gateway.2wire.net>
In-Reply-To: <00ad01cc4ea3$1e06ce20$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sat, 30 Jul 2011 04:45:30 -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: Sat, 30 Jul 2011 11:45:31 -0000

On 7/30/2011 6:26 AM, t.petch wrote:
> Sadly, I do not see it being used in the mailing lists where an
> organisation is sending me directly data I would like to be able to rely on
> - which I think fits the applicability well - and instead, I see it
> being used on a mailing list such as those in the IETF where I
> believe that the costs outweigh the benefits - and I have no choice
> about that:-(.


Costs?

1. The only place that DKIM information appears in a message is in a special 
header-field.

2. If your system does not process DKIM and you don't display the full header, 
you don't even see that it is there; unlike OpenPGP and S/MIME, there is no 
evidence of DKIM in the body.

3. The increase in size in message size is felt by the industry to be a minor 
"cost", especially given all the other functions that already increase message size.

4. If the extra bytes are such a terrible burden for you, strip the field off.

It does seem odd to complain about a mechanism that (finally) provides a 
certifiably valid identifier on messages, in an environment where 90% of the 
traffic across the Internet exploits the fact that there hasn't been one...

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From moore@network-heretics.com  Sat Jul 30 04:45: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 1034521F8A4F for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 04:45:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.504
X-Spam-Level: 
X-Spam-Status: No, score=-3.504 tagged_above=-999 required=5 tests=[AWL=0.095,  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 Z4owCvCEAGbU for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 04:45:55 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 2E47621F89BA for <ietf@ietf.org>; Sat, 30 Jul 2011 04:45:55 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 0CB272042B; Sat, 30 Jul 2011 07:45:54 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute6.internal (MEProxy); Sat, 30 Jul 2011 07:45: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=uzjS1wICzB+e0WPSehqCVILOQwU=; b=TS a5yK0VNTjJZ9hLJ+if10xul+D11gJwqP/tMVZXWUvFV5bZVC900mAnBPbp+R7U9m aOHrkqTrqxBsbUc8Xgo3dRLjYu5Vi4gBs7mMuARHtkdL418rKv051IGz7Qt62Mr0 w5+sTD0IcWR7g64oZQtvvs7lfpZ8Q0Yc9U0pWg9dc=
X-Sasl-enc: 8sFg45a7OuLFZO+UraIxHZxuOaxn2Vzn1fqc71IaOtWX 1312026353
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPSA id 521E745622C; Sat, 30 Jul 2011 07:45:53 -0400 (EDT)
Subject: Re: What is Native IPv6
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: <CA599052.495A5%jordi.palet@consulintel.es>
Date: Sat, 30 Jul 2011 07:45:51 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <78340747-5B8E-4748-9531-50303476534F@network-heretics.com>
References: <CA599052.495A5%jordi.palet@consulintel.es>
To: jordi.palet@consulintel.es
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: Sat, 30 Jul 2011 11:45:56 -0000

On Jul 30, 2011, at 10:45 AM, JORDI PALET MARTINEZ wrote:

> However, for what it matters here, 6rd is native after exiting from =
the
> ISP, same as 6to4 is native after exiting from the 6to4 relay.
>=20
> As we may not be able to know how "much" of the "native" IPv6 traffic =
is
> 6rd in the last mile, I think we should consider all 6rd traffic as =
native
> for those measurements, otherwise, we will be biasing the data. Even =
it
> may be the case of an ISP using 6rd for some part of its network, and
> native for the other.

good points.

I suspect that what many people are interested in is not whether the v6 =
traffic is "native" end-to-end, but rather, something like:

a) How much of this traffic is _managed_ end-to-end vs. how much relies =
on ad-hoc "kindness of strangers" e.g. RFC 3068 which we know is less =
reliable.
b) If certain transition mechanisms happen to be very effective/useful =
at getting people onto IPv6 (or not), which ones are those? =20

Of course, some of these things are easier to measure than others.

Then again, others really are interested in whether the traffic is =
"native", since perhaps they care about applications (media streaming?) =
that are significantly impacted by tunneling.

Keith



From pch-b2B3A6689@u-1.phicoh.com  Sat Jul 30 05:17:14 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 CB56321F874A for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 05:17:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.613
X-Spam-Level: 
X-Spam-Status: No, score=-7.613 tagged_above=-999 required=5 tests=[AWL=0.986,  BAYES_00=-2.599, GB_I_LETTER=-2, 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 D519on1hvsWn for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 05:17:09 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id 5C92C21F8888 for <ietf@ietf.org>; Sat, 30 Jul 2011 05:17:09 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #66) id m1Qn8CT-0001gNC; Sat, 30 Jul 2011 13:59:25 +0200
Message-Id: <m1Qn8CT-0001gNC@stereo.hq.phicoh.net>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
Subject: Re: What is Native IPv6 
From: Philip Homburg <pch-ietf@u-1.phicoh.com>
Sender: pch-b2B3A6689@u-1.phicoh.com
In-reply-to: Your message of "Fri, 29 Jul 2011 19:31:13 -0700 ." <392CB277BC2EAE4FB83C1206954BA6CEF63B@newserver.arneill-py.local> 
Date: Sat, 30 Jul 2011 13:58:57 +0200
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 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, 30 Jul 2011 12:17:14 -0000

In your letter dated Fri, 29 Jul 2011 19:31:13 -0700 you wrote:
>- If one is in the business of writing an draft about "what is native
>IPv6", and if one of the draft's goals is to reach -cough- consensus
>-cough-, one may consider "forgetting" the 6PE classification
>altogether. The one part that is not open for grabs with me is
>classifying 6RD as native.

Why do you care so much about 'native'?

At the moment, I have 5 IPv6 connections:
1) native
2) tunnel to my ISP
3) tunnel to HE
4) tunnel to SixXS
5) 6to4

Obviously, the first one is native and the others aren't, But as user of those
links, it seems a completely arbitrary and useless distinction.
Number 5, 6to4 is obviously a problem. So that's in the 'avoid' category.
Number 3 and 4, require good access to the IPv4 Internet. At the moment
they work perfectly, but they are not future proof.
Numbers 1 and 2. In first case, ppp frames go over atm/ethernet to my ISP.
In the second case, IPv4 packets go over ppp frames over atm/ethernet to my
ISP. Yes, compared to native, the tunnel has an extra IPv4 header, but
otherwise, there is no difference. (At my ISP, native and tunneled are
terminated differently, but so far that difference is almost impossible to
notice)

So my classification would be
1) IPv6 provided by the user's ISP. (native, 6rd, tunnel by ISP)
2) IPv6 provided by a third party (tunnels by other parties)
3) IPv6 provided by unknown third parties (6to4, teredo)

1) can be made to work very well, 2) has problems, 3) is to be avoided.



From hsantos@isdg.net  Sat Jul 30 05:17:16 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 9D60B21F898E for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 05:17:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.936
X-Spam-Level: 
X-Spam-Status: No, score=-3.936 tagged_above=-999 required=5 tests=[AWL=-1.337, 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 lrhWn8VI5M8W for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 05:17:15 -0700 (PDT)
Received: from secure.winserver.com (news.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 79BE621F8749 for <ietf@ietf.org>; Sat, 30 Jul 2011 05:17:14 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1196; t=1312028137; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=Ce6qG2bEISLC6719cNCyU4Y9TXc=; b=u9ANpGgtHTvE3QlbpV0c ux9hPiw5gR4H7e30Klg9+maFIUpFIuFlle+IyUC7ymXhM3/AV20NPVWxL8O2As1n QXaclAZUsAy4zQSyRdq5VJttzq0uPVIphVHG/1BGfL/Lj7lcmEKwLrhawXG71+di ZxrHUw81dg/YNqk/ZkJoj5o=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Sat, 30 Jul 2011 08:15:37 -0400
Authentication-Results: dkim.winserver.com; dkim=fail (DKIM_SIGNATURE_BAD) header.d=isdg.net header.s=tms1 header.i=isdg.net;  adsp=pass policy=all author.d=isdg.net signer.d=isdg.net (originating signer); 
Received: from beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 483627393.26882.4868; Sat, 30 Jul 2011 08:15:36 -0400
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha256; c=simple/relaxed; t=1312027873; h=Received:Received:Message-ID: Date:From:Organization:To:Subject:List-ID; bh=ZRvFqQpZwrxTKVjpXe h8MILGY64McYHJHCdmW9l86IE=; b=Fo/gNo7mzdIVFMk433WWArig2ems7mN6Bn iIpABMDA9SfMb55e/f2LxoRIWP6jvfpZZSk1H8zvze256Qp34zZkQPob6U6j2qki jOqBMNCKeY4/yKXubVVZPdFwS9YZs+OqvsFyXg4/4J/pJiThYX5SRu4++OHrvkfA MgTQ700pE=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Sat, 30 Jul 2011 08:11:13 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1454911815.3064.7116; Sat, 30 Jul 2011 08:11:12 -0400
Message-ID: <4E33F60F.90805@isdg.net>
Date: Sat, 30 Jul 2011 08:16:15 -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@ietf.org
Subject: Re: DKIM Signatures now being applied to IETF Email
References: <20110725171748.GA13506@amsl.com><4E2DAF60.8030307@dcrocker.net><4E2FFFDF.2080601@ieca.com><005d01cc4d44$3136eda0$4001a8c0@gateway.2wire.net><4E3288EE.9050201@dcrocker.net><006101cc4dea$2c9bdd40$4001a8c0@gateway.2wire.net>	<CAC4RtVDSHEhcffUx=+Y2vORb1TBmgs=XmGrvJgAc1upo-5SbEQ@mail.gmail.com>	<00ad01cc4ea3$1e06ce20$4001a8c0@gateway.2wire.net> <4E33EECF.5020708@dcrocker.net>
In-Reply-To: <4E33EECF.5020708@dcrocker.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jul 2011 12:17:16 -0000

Dave CROCKER wrote:

> It does seem odd to complain about a mechanism that (finally) provides a 
> certifiably valid identifier on messages, in an environment where 90% of 
> the traffic across the Internet exploits the fact that there hasn't been 
> one...

How it is certified?  I haven't seen any DKIM message that comes with 
a certified identifier. Is there consistency in the certification 
across all DKIM verifiers? What do you when it isn't certified which 
is 99% of the DKIM signed mail coming in?   And how does one leverage 
or mitigate this 90% asserted exploitation with DKIM?  Should we begin 
to reject mail that do not have valid signatures?

Without a domain policy based security wrapper, DKIM remains an 
unsecured protocol and currently it is just wasted processing 
bandwidth with a huge cost in implementation and management, or just 
plain old getting it right, and even then, most people in our market 
don't understand what utility it offers them.  At present, they 
believe the "new badge" will help them look better, but there is no 
real evidence that it does anything for them.

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com





From dhc2@dcrocker.net  Sat Jul 30 05:20:14 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 6253321F874A for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 05:20:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.479
X-Spam-Level: 
X-Spam-Status: No, score=-6.479 tagged_above=-999 required=5 tests=[AWL=0.120,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U0knaWHE1k8b for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 05:20:13 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8621321F88A1 for <ietf@ietf.org>; Sat, 30 Jul 2011 05:20:13 -0700 (PDT)
Received: from [172.16.59.36] (modemcable252.155-70-69.static.videotron.ca [69.70.155.252]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p6UCHlgC028445 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 30 Jul 2011 05:17:54 -0700
Message-ID: <4E33F668.7050900@dcrocker.net>
Date: Sat, 30 Jul 2011 08:17:44 -0400
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: Why the IESG needs to review everything...
References: <4E308D64.3030804@gmail.com> <4E30927D.50808@dcrocker.net>	<4E30B250.3030807@gmail.com> <4E3161AB.9010007@dcrocker.net>	<4E31EF47.5070403@gmail.com> <4E321288.7000309@dcrocker.net> <4E322EDB.7030306@joelhalpern.com>
In-Reply-To: <4E322EDB.7030306@joelhalpern.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sat, 30 Jul 2011 05:17:55 -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: Sat, 30 Jul 2011 12:20:14 -0000

Joel, et al,

On 7/28/2011 11:54 PM, Joel M. Halpern wrote:
> I think I understand your request taht we move beyond personal anecdotes. In
> principle, I even agree with you.
>
> However, when I try to act on that, I am stumped. I do not see any way to
> evaluate say the last 2 years discusses to determine whether they were more
> harmful or more helpful.

1. Pursue serious discussions that consider criteria for determining that.  A 
variety of obvious candidates for this list come to mind readily; for example:

    *  Does a review of the Discuss now produce a sense of its worth?  That is, 
do the rest of us, looking at the Discuss generally feel that it was clear and 
substantive and even important?

    *  Does the Discuss obviously align with the criteria for a Discuss?

    *  Does the AD who held the Discuss now feel that it was productive, and why?

    *  Do the authors and chairs now feel that it was productive, and why?

    *  How much delay did the Discuss introduce?  Was it timely?

    *  How much effort did it take to resolve the discuss?

    *  Did the Discuss produce a change in normative text?

    *  Does a review of the change in text, now, produce a sense of its worth?
    ...

It could well be worth trying to classify typical types of Discusses, such as:

    *  Curiosity questions.  "I'd like to understand..." where no actual problem 
is cited

    *  Review enforcement.  Ensuring that particular points from other reviews 
are resolved

    *  Personal preference.  AD dislike of a working group choice, without a 
clear basis the makes clear why the wg choice won't work or is otherwise impractical

    *  Fundamental problem.  Assertion of a basic limitation to the 
specification that renders it inherently problematic

    *  Scope.  The Discuss appears to be out of scope for the document.  For 
example, a document intended for Draft is being challenged on basic issues that 
were approved when it went to Proposed.

    *  Unclear.  The meaning of the Discuss is unclear and/or the path towards 
resolution cannot be understood because the Discuss offers no clear criteria for 
resolution.

       To illustrate this last item with examples that almost certainly have 
never happened:

       o  If a Discuss said "needs to be written in an active voice rather than 
passive", it would be clear what would resolve it.

       o  If a Discuss said "needs to be shorter", there's a clear direction for 
resolution, but no criteria for for knowing when it is short enough.

       o  If a Discuss said "Algorithm X in the specification will not work for 
the following reasons...; Algorithm Y is better for the following reasons" then 
it is clear what the problem is, why it is a problem and exactly what will 
satisfy the AD to resolve it.

    ...

It can also be worth looking at meta-issues.  For example, do documents 
typically get a Discuss?  That is, is it typical to block progress for a 
document?  Does it make sense to have working groups proceed for many months and 
then have presumably basic issues raised at the very last moment?


2. Review the datatracker histories over the last <x> years, sampling enough of 
the documents to get a sense of the overall pattern.  (The new datatracker now 
supports provides a complete history for the handling of drafts; massive kudos 
to the tools team!)


3. Talk with authors, chairs and ADs about previous Discusses.


> But you asked that we go beyond that. How?

The above is meant to prime a serious discussion, but the first requirement is a 
willingness to engage in that discussion and to pursue it seriously.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From presnick@qualcomm.com  Sat Jul 30 09:55:53 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 B2CDA21F8892 for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 09:55:53 -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 AX7FU9oHXqXy for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 09:55:53 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 30D1921F874E for <ietf@ietf.org>; Sat, 30 Jul 2011 09:55:52 -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=1312044954; x=1343580954; 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<4E343791.7040401@qualcomm.com>|Date:=20Sa t,=2030=20Jul=202011=2011:55:45=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:=20Eric=20Burger=20<eburger-l@sta ndardstrack.com>|CC:=20Bradner=20Scott=20<sob@harvard.edu >,=20IETF=20<ietf@ietf.org>|Subject:=20Re:=20draft-housle y-two-maturity-levels|References:=20<20110728121904.2D22A D7A76F@newdev.eecs.harvard.edu>=09<12B69DB8-AFDD-4C40-BC9 A-0A8158D9F7C0@nostrum.com>=20<0D43A851-C57B-484F-ADDD-BB D7A412689C@standardstrack.com>|In-Reply-To:=20<0D43A851-C 57B-484F-ADDD-BBD7A412689C@standardstrack.com> |Content-Type:=20text/plain=3B=20charset=3D"ISO-8859-1" =3B=20format=3Dflowed|Content-Transfer-Encoding:=207bit |X-Originating-IP:=20[172.30.48.1]; bh=7Rak34oXsXN+4qDspjgkOqYT/oFGuN1NXRgTO/4KreE=; b=wfN+1zi+bLp1I/AjrEbJFe9ttXKDoFfCuUxW2wuENg0AWmr5vMMKDZpc 6EIlf0E3u1Rv8e8QL+8fbdy6i1c8cIjCHehbrGx0l3duk/0hRTmtfllJc Bh5lcPzxsskf/HYumPh0eJQtTCDdXGy5Y48qKKtIq4KD5qf1dvEvbCxhm s=;
X-IronPort-AV: E=McAfee;i="5400,1158,6423"; a="107053557"
Received: from ironmsg02-r.qualcomm.com ([172.30.46.16]) by wolverine01.qualcomm.com with ESMTP; 30 Jul 2011 09:55:47 -0700
X-IronPort-AV: E=Sophos;i="4.67,291,1309762800"; d="scan'208";a="155247540"
Received: from nasanexhc05.na.qualcomm.com ([172.30.48.2]) by ironmsg02-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 30 Jul 2011 09:55:47 -0700
Received: from Macintosh-4.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.1.323.0; Sat, 30 Jul 2011 09:55:46 -0700
Message-ID: <4E343791.7040401@qualcomm.com>
Date: Sat, 30 Jul 2011 11:55:45 -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: Eric Burger <eburger-l@standardstrack.com>
Subject: Re: draft-housley-two-maturity-levels
References: <20110728121904.2D22AD7A76F@newdev.eecs.harvard.edu>	<12B69DB8-AFDD-4C40-BC9A-0A8158D9F7C0@nostrum.com> <0D43A851-C57B-484F-ADDD-BBD7A412689C@standardstrack.com>
In-Reply-To: <0D43A851-C57B-484F-ADDD-BBD7A412689C@standardstrack.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: Bradner Scott <sob@harvard.edu>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jul 2011 16:55:53 -0000

On 7/28/11 9:03 AM, Eric Burger wrote:

>> On Jul 28, 2011, at 8:19 AM, Scott O. Bradner wrote:
>>> 1/ I still see no reason to think that this change will cause any
>>> significant change in the percent of Proposed Standards that move up the
>>> (shorter) standards track since the proposal does nothing to change the
>>> underlying reasons that people do not expend the effort needed to
>>> advance documents
>
> And the real question is, are we moving forward? I think that we are not moving as far as we originally wanted. However, I offer we are moving a baby step forward, and as such is worthwhile doing.
>    

On 7/28/11 6:07 PM, Brian E Carpenter wrote:
> Let's just make this baby step and stop worrying about it.
>    

Not to pick on Eric and Brian alone; I put this to everyone.

I *really* want an answer to the issue that Scott raises. Eric and Brian 
each refer to a "baby step". A baby step toward what exactly?

If the answer is simply, "to align documentation with current 
procedure", that's fine, but then I want to know: a) Why is it useful 
and positive to line up documentation with current procedure? That is, 
what are we gaining by publishing this? and b) This document is 
identical to neither 2026 *nor* current procedure, so how is it 
accomplishing the goal of aligning with current procedure anyway?

If the answer is, "Yes, this document will cause a change in the percent 
of Proposed Standards that move up", then I want to know "How?", because 
like Scott, I haven't heard the answer stated in this dicussion.

If you think I've missed an obvious alternative reason to go ahead with 
this document, I'm open to hear it, but it sounds like the only two 
alternatives expressed so far are, "Document current practice" and 
"Improve number of documents moving along standards track", and I 
haven't heard how this document does either of those things.

I consider this an open, unaddressed, issue.

pr

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


From jmh@joelhalpern.com  Sat Jul 30 10:05:51 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 C639A21F8B0F for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 10:05:51 -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 xW3vMd9T05ZA for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 10:05:51 -0700 (PDT)
Received: from hgblob.out.tigertech.net (hgblob.out.tigertech.net [74.114.88.71]) by ietfa.amsl.com (Postfix) with ESMTP id 469AE21F86C4 for <ietf@ietf.org>; Sat, 30 Jul 2011 10:05:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 726723246443; Sat, 30 Jul 2011 10:05:20 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [130.129.67.226] (dhcp-43e2.meeting.ietf.org [130.129.67.226]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id 6FEE4324615D; Sat, 30 Jul 2011 10:05:19 -0700 (PDT)
Message-ID: <4E3439CE.4030509@joelhalpern.com>
Date: Sat, 30 Jul 2011 13:05:18 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: draft-housley-two-maturity-levels
References: <20110728121904.2D22AD7A76F@newdev.eecs.harvard.edu>	<12B69DB8-AFDD-4C40-BC9A-0A8158D9F7C0@nostrum.com> <0D43A851-C57B-484F-ADDD-BBD7A412689C@standardstrack.com> <4E343791.7040401@qualcomm.com>
In-Reply-To: <4E343791.7040401@qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Bradner Scott <sob@harvard.edu>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jul 2011 17:05:51 -0000

It seems to me that this does two things, both small but useful.
1) It makes a minor change in the advancement procedures so that they 
are more reasonable.  They may still not be sufficiently reasonable to 
be used, but it improves them, and thereby improves the odds.
2) It is coupled to an intent to actually behave according to what the 
document says.  Such an intent is obviously not feasible without some 
change.  It is useful to have our behavior and our documented 
description of how we work match because the mismatch causes confusion, 
at least for new participants, and sometimes even for experienced 
participants.

It might be the case that it will improve the advancement percentage. 
It might not.  I can not imagine that it will make that even worse.

So, it seems to me that this matches the description that Eric, Brian, 
and others have used of a baby step that is not harmful and may be helpful.

Yours,
Joel

On 7/30/2011 12:55 PM, Pete Resnick wrote:
> On 7/28/11 9:03 AM, Eric Burger wrote:
>
>>> On Jul 28, 2011, at 8:19 AM, Scott O. Bradner wrote:
>>>> 1/ I still see no reason to think that this change will cause any
>>>> significant change in the percent of Proposed Standards that move up
>>>> the
>>>> (shorter) standards track since the proposal does nothing to change the
>>>> underlying reasons that people do not expend the effort needed to
>>>> advance documents
>>
>> And the real question is, are we moving forward? I think that we are
>> not moving as far as we originally wanted. However, I offer we are
>> moving a baby step forward, and as such is worthwhile doing.
>
> On 7/28/11 6:07 PM, Brian E Carpenter wrote:
>> Let's just make this baby step and stop worrying about it.
>
> Not to pick on Eric and Brian alone; I put this to everyone.
>
> I *really* want an answer to the issue that Scott raises. Eric and Brian
> each refer to a "baby step". A baby step toward what exactly?
>
> If the answer is simply, "to align documentation with current
> procedure", that's fine, but then I want to know: a) Why is it useful
> and positive to line up documentation with current procedure? That is,
> what are we gaining by publishing this? and b) This document is
> identical to neither 2026 *nor* current procedure, so how is it
> accomplishing the goal of aligning with current procedure anyway?
>
> If the answer is, "Yes, this document will cause a change in the percent
> of Proposed Standards that move up", then I want to know "How?", because
> like Scott, I haven't heard the answer stated in this dicussion.
>
> If you think I've missed an obvious alternative reason to go ahead with
> this document, I'm open to hear it, but it sounds like the only two
> alternatives expressed so far are, "Document current practice" and
> "Improve number of documents moving along standards track", and I
> haven't heard how this document does either of those things.
>
> I consider this an open, unaddressed, issue.
>
> pr
>

From michel@arneill-py.sacramento.ca.us  Sat Jul 30 11:39:55 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 2526721F873D for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 11:39:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.005
X-Spam-Level: 
X-Spam-Status: No, score=-2.005 tagged_above=-999 required=5 tests=[AWL=-0.040, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sq7LXhUhsPlA for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 11:39:54 -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 7FA8E21F873A for <ietf@ietf.org>; Sat, 30 Jul 2011 11:39:54 -0700 (PDT)
Subject: RE: What is Native IPv6
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 30 Jul 2011 11:39:53 -0700
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF63E@newserver.arneill-py.local>
Content-class: urn:content-classes:message
In-Reply-To: <CAKFn1SFKqQZp_pQQyJtRYqSwi1=iYEL=rvsXy0rOmb-tU6oFVA@mail.gmail.com>
X-MS-Has-Attach: 
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-MS-TNEF-Correlator: 
Thread-Topic: What is Native IPv6
Thread-Index: AcxOqAWdZRba1onjQMetz9BReJfZ4wANhqsg
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net><4E2DE4EC.1030109@gmail.com><4E2E2FBA.1030304@gmail.com><13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net><4E2EDF23.3060804@gmail.com><4E2F4491.30102@gmail.com><20110727023833.5C72D1232958@drugs.dv.isc.org><m1QlzXt-0001gSC@stereo.hq.phicoh.net><2D290C0C-E845-42EF-9690-D92D3D86641C@apple.com><392CB277BC2EAE4FB83C1206954BA6CEF627@newserver.arneill-py.local><10E841AF-01FC-4AAF-B9A1-78FD521C87E9@apple.com><CAKD1Yr3gv=+HfEZMsU0enNh8OQbemQh6iRzpGHsnmr7OJrTcFg@mail.gmail.com><392CB277BC2EAE4FB83C1206954BA6CEF635@newserver.arneill-py.local><3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk><EMEW3|fa0511c175232cff9b9cb8310f081538n6RMCh03tjc|ecs.soton.ac.uk|3428AA6F-334F-43F0-906A-13828378999C@ecs.soton.ac.uk><4E31F3C2.4000000@gmail.com><392CB277BC2EAE4FB83C1206954BA6CEF637@newserver.arneill-py.local><6E140BC3-0C38-453B-A557-A929EDC33A09@bogus.com><38D0CD11-F193-4D1B-951A-332C24AFBC7E@employees.o rg><392C B277BC2EAE4F B83C1206954BA6CEF63B@newserver.arneill-py.local> <CAKFn1SFKqQZp_pQQyJtRYqSwi1=iYEL=rvsXy0rOmb-tU6oFVA@mail.gmail.com>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: =?iso-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>, <jordi.palet@consulintel.es>
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, 30 Jul 2011 18:39:55 -0000

> JORDI PALET MARTINEZ wrote:
> However, for what it matters here, 6rd is native after
> exiting from the ISP, same as 6to4 is native after
> exiting from the 6to4 relay. As we may not be able to
> know how "much" of the "native" IPv6 traffic is 6rd in
> the last mile, I think we should consider all 6rd traffic
> as native for those measurements, otherwise, we will be
> biasing the data. Even it may be the case of an ISP using
> 6rd for some part of its network, and native for the other.
> We may need to state "IPv6 native as measured, may be
> encapsulated in the last mile".

I disagree.

6RD is not a last mile solution. With the existing levels of IPv6 =
traffic, an ISP would deploy a couple of 6RD relays at their main IX. In =
a country such as France, it means that a 6RD customer in Nice would see =
their IPv6 traffic being encapsulated all the way to Paris over IPv4 =
crossing the entire ISP's network for some 400 miles. In Spain, the =
really native part of the traffic would possibly start in Madrid.

Imagine 2 customers in Barcelona, who are with two different ISPs using =
6RD. The 6RD relays are in Madrid for both, likely not much more than a =
few miles away or even possibly in the same IX (I don't know the details =
of IXes in Madrid). The 6RD traffic from one goes over IPv4 all the way =
to Madrid, then goes native for a few miles to the other ISP's 6RD =
relay, then back over IPv4 to Barcelona. This is not native.

On top of it, like any other tunnel solution, it stinks because the IPv6 =
traffic goes back all the way to Madrid while, if it was IPv4, there is =
a good possibility that the two ISPs are peering in Barcelona in a small =
colo and the traffic never leaves the town.

The obvious: the solution is, duh, native IPv6 in Barcelona and the =
reason ISPs are deploying 6RD is, duh, because they don't have it.

As mentioned before by Christian and other, 6RD is very similar to a =
tunnel broker deployment, and the number and location of relays change =
everything.


> Philip Homburg wrote:
> At the moment, I have 5 IPv6 connections:
> 1) native
> 2) tunnel to my ISP
> 3) tunnel to HE
> 4) tunnel to SixXS
> 5) 6to4
> Obviously, the first one is native and the others aren't,

Then we agree.


> Roger J=F8rgensen wrote:
> It mean IPv4 running on top of IPv6, IPv6 running on top
> of IPv4 is not native.  But this easy way of seeing it
> only affect IPv4 and IPv6, not all of the others.

I could go for that; native IPv6 mostly means "no IPv4" for the agreed =
scope. But I was trying to be more generic, the idea being to prevent a =
clever marketing droid finding a way to tunnel IPv6 over avian carriers =
and calling it native.

> I guess it all boils down to, are we talking about end
> to end native, or the transportation of the L3 protocol
> being native?

If I understand you correctly (I think I do) I would say it ends up =
being the same thing. What we want is no reliance on IPv4, what we don't =
want is limit implementation options.

How good is a native IPv6 network if it has to be redone when =
decommissioning IPv4? That's where the oxymoron is. I think a good way =
to see it would be: remove all IPv4 end-to-end.  If it still works, it's =
native IPv6. If not, it's not native.

Michel.


From john@jlc.net  Sat Jul 30 12:31:38 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 596C321F8834 for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 12:31:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.579
X-Spam-Level: 
X-Spam-Status: No, score=-106.579 tagged_above=-999 required=5 tests=[AWL=0.020, 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 KCi0R-2qienz for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 12:31:37 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id B308421F8696 for <ietf@ietf.org>; Sat, 30 Jul 2011 12:31:37 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 95F1A33C26; Sat, 30 Jul 2011 15:31:38 -0400 (EDT)
Date: Sat, 30 Jul 2011 15:31:38 -0400
From: John Leslie <john@jlc.net>
To: IETF <ietf@ietf.org>
Subject: Re: draft-housley-two-maturity-levels
Message-ID: <20110730193138.GA26631@verdi>
References: <20110728121904.2D22AD7A76F@newdev.eecs.harvard.edu> <12B69DB8-AFDD-4C40-BC9A-0A8158D9F7C0@nostrum.com> <0D43A851-C57B-484F-ADDD-BBD7A412689C@standardstrack.com> <4E343791.7040401@qualcomm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4E343791.7040401@qualcomm.com>
User-Agent: Mutt/1.4.1i
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2011 19:31:38 -0000

Pete Resnick <presnick@qualcomm.com> wrote:
> 
> I *really* want an answer to the issue that Scott raises. Eric and Brian 
> each refer to a "baby step". A baby step toward what exactly?
> 
> If the answer is simply, "to align documentation with current 
> procedure", that's fine, but then I want to know:
> a) Why is it useful and positive to line up documentation with current
>    procedure? That is, what are we gaining by publishing this? and
> b) This document is identical to neither 2026 *nor* current procedure,
>    so how is it accomplishing the goal of aligning with current
>    procedure anyway?

   Although, to tell truth, I don't care very much whether this I-D
becomes an RFC, I am _very_ glad that Pete is raising these questions.

   We have been wandering in the weeds for years now over "how many
steps should there be?" IMHO, the last serious WG effort (newtrk)
reached something very like consensus that that was the wrong question.

   I _seriously_ hope the IESG will either decide to enact this I-D or
stop beating this horse.

   I suggest that we accept the principle that "consensus" process
means it will be hard to change something in the future; and admit
that "adjust to current practice" isn't a sufficient shibboleth to
gain consensus for a change from a previous consensus.

   It _is_ appropriate for anyone sufficiently bothered by failure to
follow current documented rules to appeal actions which don't follow
the "rules". That _will_ make you unpopular with the folks that must
process the appeal, but it is less harmful than asking the entire IETF
to wander in the weeds in seek of consensus to change the "rules".

   If I may make a suggestion, actual practice could be documented on
ietf.org web pages (with some explanation of how it differs from the
RFC "rules" and why) -- without all this wandering in the weeds. It
is _really_ unlikely that would invoke the full appeal process more
than once, and it would save a lot of bandwidth on this list.

   BTW, while I do intend to be silent if the IESG adopts this I-D
for publication, that does _not_ mean I will be silent when the next
"adjust to current practice" I-D comes up.

--
John Leslie <john@jlc.net>

From pch-b2B3A6689@u-1.phicoh.com  Sat Jul 30 12:54:54 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 2A1A721F87BC for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 12:54:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.736
X-Spam-Level: 
X-Spam-Status: No, score=-7.736 tagged_above=-999 required=5 tests=[AWL=0.863,  BAYES_00=-2.599, GB_I_LETTER=-2, 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 o-1Fk1lf-Wsg for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 12:54:53 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id 458D121F87AF for <ietf@ietf.org>; Sat, 30 Jul 2011 12:54:52 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #66) id m1QnFNs-0001iVC; Sat, 30 Jul 2011 21:39:40 +0200
Message-Id: <m1QnFNs-0001iVC@stereo.hq.phicoh.net>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
Subject: Re: What is Native IPv6 
From: Philip Homburg <pch-ietf@u-1.phicoh.com>
Sender: pch-b2B3A6689@u-1.phicoh.com
In-reply-to: Your message of "Sat, 30 Jul 2011 11:39:53 -0700 ." <392CB277BC2EAE4FB83C1206954BA6CEF63E@newserver.arneill-py.local> 
Date: Sat, 30 Jul 2011 21:39:22 +0200
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, 30 Jul 2011 19:54:54 -0000

In your letter dated Sat, 30 Jul 2011 11:39:53 -0700 you wrote:
>6RD is not a last mile solution. With the existing levels of IPv6 traffic, an 
>ISP would deploy a couple of 6RD relays at their main IX. In a country such as
> France, it means that a 6RD customer in Nice would see their IPv6 traffic bei
>ng encapsulated all the way to Paris over IPv4 crossing the entire ISP's netwo
>rk for some 400 miles. In Spain, the really native part of the traffic would p
>ossibly start in Madrid.
>
>Imagine 2 customers in Barcelona, who are with two different ISPs using 6RD. T
>he 6RD relays are in Madrid for both, likely not much more than a few miles aw
>ay or even possibly in the same IX (I don't know the details of IXes in Madrid
>). The 6RD traffic from one goes over IPv4 all the way to Madrid, then goes na
>tive for a few miles to the other ISP's 6RD relay, then back over IPv4 to Barc
>elona. This is not native.

So, 6rd is bad because it allows an ISP to deploy it in a sub-optimal way.
Wow, if that how we are going to judge protocols then we can just as well go
home.

If the existing levels of IPv6 traffic were a reason to install just one 6rd
box for an entire country then expecting that ISP to deploy native IPv6 would
be extremely unrealistic.

And even if an ISP would do that. The round trip latency between Barcelona and
Madrid is likely to be in the order of 5ms. There are DSL error correcting
settings that have much impact than that.

From brian.e.carpenter@gmail.com  Sat Jul 30 13:40:46 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 CFB8D21F8782 for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 13:40:46 -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 kAeSHlBxvhvJ for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 13:40: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 DB7C321F8779 for <ietf@ietf.org>; Sat, 30 Jul 2011 13:40:45 -0700 (PDT)
Received: by fxe6 with SMTP id 6so3840130fxe.31 for <ietf@ietf.org>; Sat, 30 Jul 2011 13:40:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=f97t7iNzTZ0WEE7ggnqeyaxGKW9WAa7xltRfQZrsHJ8=; b=TTqn9Le9geY+n1Vgy2cjj7drFmvowWK5aL5gtUKRPw9i7V3Sw4WUu1KPQ8NtHYwMP5 JaRyWrxFpIIh0C3ccinFvfiyxwcVZcFQtbvJpycKnqMVI7XKxYNqnFONmGsqGgy75o9y QAWmKcIJaTDpI51rwNW9pRq5VYwH4iFnqlBnc=
Received: by 10.223.58.75 with SMTP id f11mr2251127fah.70.1312058446887; Sat, 30 Jul 2011 13:40:46 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id j18sm1068453faa.46.2011.07.30.13.40.42 (version=SSLv3 cipher=OTHER); Sat, 30 Jul 2011 13:40:45 -0700 (PDT)
Message-ID: <4E346C3E.4060509@gmail.com>
Date: Sun, 31 Jul 2011 08:40:30 +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: Pete Resnick <presnick@qualcomm.com>
Subject: Re: draft-housley-two-maturity-levels
References: <20110728121904.2D22AD7A76F@newdev.eecs.harvard.edu>	<12B69DB8-AFDD-4C40-BC9A-0A8158D9F7C0@nostrum.com>	<0D43A851-C57B-484F-ADDD-BBD7A412689C@standardstrack.com> <4E343791.7040401@qualcomm.com>
In-Reply-To: <4E343791.7040401@qualcomm.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Bradner Scott <sob@harvard.edu>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jul 2011 20:40:46 -0000

Hi Pete,

On 2011-07-31 04:55, Pete Resnick wrote:
...
> I *really* want an answer to the issue that Scott raises. Eric and Brian
> each refer to a "baby step". A baby step toward what exactly?
> 
> If the answer is simply, "to align documentation with current
> procedure", that's fine, but then I want to know: a) Why is it useful
> and positive to line up documentation with current procedure? That is,
> what are we gaining by publishing this? 

I believe that the present situation is confusing both to IETF newcomers
(who may falsely believe that the IETF actually follows the 3 stage process)
and, worse, confusing to users of IETF standards (who may falsely believe
that a document isn't useful until it's advanced). We, and those users,
gain by reducing the confusion. (Note: I did not write "eliminating the
confusion".)

> and b) This document is
> identical to neither 2026 *nor* current procedure, so how is it
> accomplishing the goal of aligning with current procedure anyway?

It defines a practice which is *very* close to present practice,
apart from a minor name change. I think that's the best we can do,
but that's why it's a baby step, not a no-op.

> 
> If the answer is, "Yes, this document will cause a change in the percent
> of Proposed Standards that move up", then I want to know "How?", because
> like Scott, I haven't heard the answer stated in this dicussion.

It might cause a change, simply because the effort of making the single
move PS->IS will get you to the end state, whereas previously you had
to make two efforts, PS->DS->STD. But only time will tell if this changes
our collective behaviour.

   Brian

From ron.even.tlv@gmail.com  Sat Jul 30 17:03:59 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 C548221F8669; Sat, 30 Jul 2011 17:03:59 -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 s7i+mx9ZiEpE; Sat, 30 Jul 2011 17:03:58 -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 44A8021F8663; Sat, 30 Jul 2011 17:03:55 -0700 (PDT)
Received: by iye7 with SMTP id 7so6525899iye.31 for <multiple recipients>; Sat, 30 Jul 2011 17:03:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=UIEVkQEj2Kcqg4YqARYJQrF38yXlYGukA6ofhVarozw=; b=uZIaV3/fr4QN4pk2OAU8zRsR+mhayxPAi60pOSUtq+ElDtmJEU5T1KnpvSCdX08Ei9 i9hkVYpPtgUkaAmqwFNin1Uc3jocx8qNoSLc1nDSBdBwHPhFXWvP0cLgD9iYh35zvL+L JglAvxd9PGL1ELyMP9ztSuvakk8YnGLwkW/hU=
Received: by 10.231.209.71 with SMTP id gf7mr1881909ibb.181.1312070635817; Sat, 30 Jul 2011 17:03:55 -0700 (PDT)
Received: from windows8d787f9 (69-196-160-60.dsl.teksavvy.com [69.196.160.60]) by mx.google.com with ESMTPS id v3sm2352147ibh.16.2011.07.30.17.03.53 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 30 Jul 2011 17:03:55 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-yevstifeyev-ion-report.all@tools.ietf.org>
Subject: Gen-ART last call review of draft-yevstifeyev-ion-report-06
Date: Sun, 31 Jul 2011 03:01:10 +0300
Message-ID: <4e349beb.033ee70a.79c4.567f@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00A0_01CC4F2E.1A78DC40"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcxPFJdbNYgVDDFZQDefVL95JHyQ3g==
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: Sun, 31 Jul 2011 00:03:59 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_00A0_01CC4F2E.1A78DC40
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-yevstifeyev-ion-report-06

Reviewer: Roni Even

Review Date:2011-7-31

IETF LC End Date: 2011-8-9

IESG Telechat date: 

 

Summary: This draft is ready for publication as an informational RFC.  

 

Major issues:

 

Minor issues:

 

I read in section 3.2 

"The IESG has determined that IONs will not be used in the future.    It is
clear that the IESG, IAB, and IAOC need the ability to   publish documents
that do not expire and are easily updated.     Information published as web
pages, including IESG Statements, are  sufficient for this purpose."

 

I was wondering that since the ION process required approval for the
document to be published, what will be the approval process when using web
pages. It is probably not part of this document but it is just a question
and I see no problem with publishing this document.

 

 

Nits/editorial comments:  

 

 


------=_NextPart_000_00A0_01CC4F2E.1A78DC40
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: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.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>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"'>Document: =
draft-yevstifeyev-ion-report-06<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;7&#8211;31<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;8&#8211;9<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as an informational RFC.&nbsp; =
<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"'>I read in =
section 3.2 <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&#8220;The =
IESG has determined that IONs will not be used in the =
future.&nbsp;&nbsp;&nbsp; It is clear that the IESG, IAB, and IAOC need =
the ability to&nbsp;&nbsp; publish documents that do not expire and are =
easily updated.&nbsp; &nbsp;&nbsp;&nbsp;Information published as web =
pages, including IESG Statements, are&nbsp; sufficient for this =
purpose.&#8221;<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"'>I was =
wondering that since the ION process required approval for the document =
to be published, what will be the approval process when using web pages. =
It is probably not part of this document but it is just a question and I =
see no problem with publishing this document.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editor=
ial comments:&nbsp; <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_00A0_01CC4F2E.1A78DC40--


From msk@cloudmark.com  Sat Jul 30 22:00:08 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 0F42621F8639 for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 22:00:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.936
X-Spam-Level: 
X-Spam-Status: No, score=-102.936 tagged_above=-999 required=5 tests=[AWL=-0.937, BAYES_00=-2.599, J_CHICKENPOX_15=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 2n3lykl9Etd3 for <ietf@ietfa.amsl.com>; Sat, 30 Jul 2011 22:00:07 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by ietfa.amsl.com (Postfix) with ESMTP id 85C1F21F861E for <ietf@ietf.org>; Sat, 30 Jul 2011 22:00:07 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Sat, 30 Jul 2011 22:00:09 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: t.petch <daedulus@btconnect.com>, Barry Leiba <barryleiba@computer.org>
Date: Sat, 30 Jul 2011 22:00:08 -0700
Subject: RE: DKIM Signatures now being applied to IETF Email
Thread-Topic: DKIM Signatures now being applied to IETF Email
Thread-Index: AcxOq/s+FtxqqqrET3yJXr0sjWvx9wAkkHww
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF4CE@EXCH-C2.corp.cloudmark.com>
References: <20110725171748.GA13506@amsl.com><4E2DAF60.8030307@dcrocker.net><4E2FFFDF.2080601@ieca.com><005d01cc4d44$3136eda0$4001a8c0@gateway.2wire.net><4E3288EE.9050201@dcrocker.net><006101cc4dea$2c9bdd40$4001a8c0@gateway.2wire.net> <CAC4RtVDSHEhcffUx=+Y2vORb1TBmgs=XmGrvJgAc1upo-5SbEQ@mail.gmail.com> <00ad01cc4ea3$1e06ce20$4001a8c0@gateway.2wire.net>
In-Reply-To: <00ad01cc4ea3$1e06ce20$4001a8c0@gateway.2wire.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@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2011 05:00:08 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of t=
.petch
> Sent: Saturday, July 30, 2011 3:26 AM
> To: Barry Leiba
> Cc: ietf
> Subject: Re: DKIM Signatures now being applied to IETF Email
>=20
> Sadly, I do not see it being used in the mailing lists where an
> organisation is sending me directly data I would like to be able to rely =
on
> - which I think fits the applicability well - and instead, I see it
> being used on a mailing list such as those in the IETF where I
> believe that the costs outweigh the benefits - and I have no choice
> about that:-(.

There has been some post-DKIM talk recently about the idea of "transient tr=
ust", wherein (to use this example) ietf.org would verify the signature on =
an arriving list submission, attach an RFC5451 header field that indicates =
the results of that verification, then send the message out to the list wit=
h that added field and a new ietf.org signature that "covered" it.  Then, i=
f you decide to believe ietf.org's claims about the original signature, you=
 know more than you would otherwise.

This hasn't been widely deployed yet, but some big email providers are curr=
ently playing with the idea.


From hsantos@isdg.net  Sun Jul 31 03:12:18 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 5D6F821F8834 for <ietf@ietfa.amsl.com>; Sun, 31 Jul 2011 03:12:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.116
X-Spam-Level: 
X-Spam-Status: No, score=-3.116 tagged_above=-999 required=5 tests=[AWL=-2.039, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_15=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 RmJAY0cHGHc8 for <ietf@ietfa.amsl.com>; Sun, 31 Jul 2011 03:12:17 -0700 (PDT)
Received: from catinthebox.net (groups.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 534F621F8804 for <ietf@ietf.org>; Sun, 31 Jul 2011 03:12:16 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2651; t=1312107135; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=2lPEHzbghtgrEigsXmxvITA8GDU=; b=On6G8YvZc4OTfj7j/QaT HONxSDW3tVauSPoMJIT3Ut7rUroH1IKM7taRDd8udbP1YAtlsBJt/fAG7cEVZ2Jl 1eKuthXam64W2a5uVibNwqNQiLtxx4gHgZvEhrVAX3ADtymqf95yYQWZZR8HTRbK ebcEmLE9kYPpasX10fLmlCE=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Sun, 31 Jul 2011 06:12:15 -0400
Authentication-Results: dkim.winserver.com; dkim=fail (DKIM_SIGNATURE_BAD) header.d=isdg.net header.s=tms1 header.i=isdg.net;  adsp=pass policy=all author.d=isdg.net signer.d=isdg.net (originating signer); 
Received: from beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 562623039.28476.5496; Sun, 31 Jul 2011 06:12:14 -0400
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; t=1312106865; h=Received:Received:Message-ID: Date:From:Organization:To:Subject:List-ID; bh=2lPEHzbghtgrEigsXm xvITA8GDU=; b=oG5H9y8v+s2nUyB8lWBfD9CMIC1jo/Kqdtdck5VPkZ0OwGyTDa JCAuWctFbID22ZwpZ7iLqgqIp0T1h6eYqm2+JdQ180Hy6hHOHfadyXTY3VttvoRM 3ZxZTuf7jAuqsylRppVQIAtP1SHdAssi/Rv+xLTZkNebRWgp409sZPRbk=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Sun, 31 Jul 2011 06:07:45 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1533903518.3365.5716; Sun, 31 Jul 2011 06:07:44 -0400
Message-ID: <4E352A74.6080703@isdg.net>
Date: Sun, 31 Jul 2011 06:12:04 -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 <ietf@ietf.org>
Subject: Re: DKIM Signatures now being applied to IETF Email
References: <20110725171748.GA13506@amsl.com><4E2DAF60.8030307@dcrocker.net><4E2FFFDF.2080601@ieca.com><005d01cc4d44$3136eda0$4001a8c0@gateway.2wire.net><4E3288EE.9050201@dcrocker.net><006101cc4dea$2c9bdd40$4001a8c0@gateway.2wire.net>	<CAC4RtVDSHEhcffUx=+Y2vORb1TBmgs=XmGrvJgAc1upo-5SbEQ@mail.gmail.com>	<00ad01cc4ea3$1e06ce20$4001a8c0@gateway.2wire.net> <F5833273385BB34F99288B3648C4F06F13512DF4CE@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF4CE@EXCH-C2.corp.cloudmark.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Jul 2011 10:12:18 -0000

You continue to not comprehend (or rather ignore) what continues to 
plaque DKIM - the lack of fault detection. Its why it continues to 
have a hard time and have people who actually believe in this 
promising protocol "bitch" about it.  If these "big email" providers 
(or anyone for that matter) begin to make assertions about what is 
good about their mail then they better be ready for the violations of 
such assertions to be rejected.  You can't have it just one way and 
mandate this is the only way to process this overhead - looking for 
good mail only and ignoring all the violations and illogically 
treating it like it was never signed or compromised or attempted to be 
compromised.

The overall difficulty is that originality is lost - the original 
author or dkim signer has lost or lacks any protocol guidance to tell 
resigners that the mail they are about the process might be bad - 
according to the original author domain.

If the resigner is going to intentionally and neglectfully ignore all 
original claims about the original domain signing practice, then how 
do you expect the anonymous "copy-cat" abuse to be controlled?


Murray S. Kucherawy wrote:
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of t.petch
>> Sent: Saturday, July 30, 2011 3:26 AM
>> To: Barry Leiba
>> Cc: ietf
>> Subject: Re: DKIM Signatures now being applied to IETF Email
>>
>> Sadly, I do not see it being used in the mailing lists where an
>> organisation is sending me directly data I would like to be able to rely on
>> - which I think fits the applicability well - and instead, I see it
>> being used on a mailing list such as those in the IETF where I
>> believe that the costs outweigh the benefits - and I have no choice
>> about that:-(.
> 
> There has been some post-DKIM talk recently about the idea of "transient trust", wherein (to use this example) ietf.org would verify the signature on an arriving list submission, attach an RFC5451 header field that indicates the results of that verification, then send the message out to the list with that added field and a new ietf.org signature that "covered" it.  Then, if you decide to believe ietf.org's claims about the original signature, you know more than you would otherwise.
> 
> This hasn't been widely deployed yet, but some big email providers are currently playing with the idea.
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
> 

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com





From HKaplan@acmepacket.com  Sun Jul 31 08:39:58 2011
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12C0E21F8770 for <ietf@ietfa.amsl.com>; Sun, 31 Jul 2011 08:39:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.569
X-Spam-Level: 
X-Spam-Status: No, score=-1.569 tagged_above=-999 required=5 tests=[AWL=-0.829, BAYES_20=-0.74]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1nTK+0SgyoaZ for <ietf@ietfa.amsl.com>; Sun, 31 Jul 2011 08:39:57 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 755DA21F876A for <ietf@ietf.org>; Sun, 31 Jul 2011 08:39:57 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Sun, 31 Jul 2011 11:39:58 -0400
Received: from mailbox1.acmepacket.com ([216.41.24.12]) by mail ([127.0.0.1]) with mapi; Sun, 31 Jul 2011 11:39:58 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: IETF-Discussion list <ietf@ietf.org>
Date: Sun, 31 Jul 2011 11:40:00 -0400
Subject: A modest proposal for Friday meeting schedule
Thread-Topic: A modest proposal for Friday meeting schedule
Thread-Index: AcxPmBpixpbwtezNTTGCAyx7fK66Jg==
Message-ID: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.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-Brightmail-Tracker: AAAAAgAAAUAAAAFT
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2011 15:39:58 -0000

Howdy,
First I'd like to thank the organizers for IETF-81 for another well-run mee=
ting.  The logistics and coordination for such an event must be daunting, a=
nd I know we (the attendees) tend to focus on the negatives rather than the=
 positives... but we really are thankful for all the time and effort put in=
to it.  Thank you!

I would also like to propose a small change for future meetings.  On Friday=
, instead of having a 2.5 hour WG meeting, followed by a 1.5 hour lunch bre=
ak, followed by 2 hours of WG meetings... perhaps we could just have 4.5 ho=
urs of WG meetings straight and also start a bit earlier? =20

Something like this:
8:30-11:00 Session I
11:15-12:15 Session II
12:30-13:30 Session III
End

That way the people who need to get to an airport get more time, or fewer o=
f them have to miss WG meetings, etc.  And it would help reduce costs for a=
ttendees if they can avoid staying Friday night at the hotel.  And lunch at=
 13:30 doesn't seem unreasonable (to me).

I apologize if this has been brought up before.  I tried to find it from an=
 old email thread for the "Experiment" at IETF-73 which added the Friday af=
ternoon sessions, but did not see this proposal being suggested.

-hadriel


From eburger-l@standardstrack.com  Sun Jul 31 08:48:12 2011
Return-Path: <eburger-l@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 DC11821F8784 for <ietf@ietfa.amsl.com>; Sun, 31 Jul 2011 08:48:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level: 
X-Spam-Status: No, score=-2.561 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 1l2vttlKEYIZ for <ietf@ietfa.amsl.com>; Sun, 31 Jul 2011 08:48:12 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 3590021F8733 for <ietf@ietf.org>; Sun, 31 Jul 2011 08:48:12 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com;  h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=fYaw5bETmea9l7d73hQ08KzdjikEmtawYszFEM3OuDo3CxkyM9XPe31J+pyK6ffGZjlUU8/Lrlii0vk7hE+k+82muPZBa0VCT1QlCeFrOyziwvzF89wsU1hBbE3skHWk;
Received: from dhcp-63da.meeting.ietf.org ([130.129.99.218]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger-l@standardstrack.com>) id 1QnYFS-000295-DB; Sun, 31 Jul 2011 08:48:14 -0700
Subject: Re: A modest proposal for Friday meeting schedule
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com>
Date: Sun, 31 Jul 2011 11:48:11 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B8E48539-BB03-41AB-8484-769624453E91@standardstrack.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com>
To: Hadriel Kaplan <HKaplan@acmepacket.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: 
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: Sun, 31 Jul 2011 15:48:13 -0000

I don't think I have seen a proposal like this before.  I really like =
it, as there are a bunch of post-IETF stuff, some of which starts in the =
afternoon and thus conflicts with the IETF. This fixes that problem, =
enables us to have the same amount of meeting time, and potentially lets =
people get home a day early.

On Jul 31, 2011, at 11:40 AM, Hadriel Kaplan wrote:

> Howdy,
> First I'd like to thank the organizers for IETF-81 for another =
well-run meeting.  The logistics and coordination for such an event must =
be daunting, and I know we (the attendees) tend to focus on the =
negatives rather than the positives... but we really are thankful for =
all the time and effort put into it.  Thank you!
>=20
> I would also like to propose a small change for future meetings.  On =
Friday, instead of having a 2.5 hour WG meeting, followed by a 1.5 hour =
lunch break, followed by 2 hours of WG meetings... perhaps we could just =
have 4.5 hours of WG meetings straight and also start a bit earlier? =20
>=20
> Something like this:
> 8:30-11:00 Session I
> 11:15-12:15 Session II
> 12:30-13:30 Session III
> End
>=20
> That way the people who need to get to an airport get more time, or =
fewer of them have to miss WG meetings, etc.  And it would help reduce =
costs for attendees if they can avoid staying Friday night at the hotel. =
 And lunch at 13:30 doesn't seem unreasonable (to me).
>=20
> I apologize if this has been brought up before.  I tried to find it =
from an old email thread for the "Experiment" at IETF-73 which added the =
Friday afternoon sessions, but did not see this proposal being =
suggested.
>=20
> -hadriel
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From rja.lists@gmail.com  Sun Jul 31 08:55:21 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 18CBF21F87BD for <ietf@ietfa.amsl.com>; Sun, 31 Jul 2011 08:55:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.586
X-Spam-Level: 
X-Spam-Status: No, score=-3.586 tagged_above=-999 required=5 tests=[AWL=0.013,  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 KLioqJt4PmZj for <ietf@ietfa.amsl.com>; Sun, 31 Jul 2011 08:55:20 -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 7EAE521F8760 for <ietf@ietf.org>; Sun, 31 Jul 2011 08:55:20 -0700 (PDT)
Received: by qyk9 with SMTP id 9so663782qyk.10 for <ietf@ietf.org>; Sun, 31 Jul 2011 08:55:23 -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 :to:mime-version:x-mailer; bh=8y9BEY/vl/a65vZKzDWF/XndBzvS4SJjCkzikm+47o8=; b=G6TR15LdRPa/sTAdYom4on7t33y/GjV5LREuoyGTsU4yR2XaZfcpdSzJylgfmmXaLw lWyQmwc31yKOh7mnXji/VNZfT36XwTVLq1eJ7v19QWmt3hfx22XdES/ZSgBoA4UoFVYh GVNLIPS/j8oSia9MdI+UMzIxLOnn51VOtSpbI=
Received: by 10.229.7.141 with SMTP id d13mr311335qcd.21.1312127723746; Sun, 31 Jul 2011 08:55:23 -0700 (PDT)
Received: from [10.30.20.5] (pool-96-225-170-25.nrflva.fios.verizon.net [96.225.170.25]) by mx.google.com with ESMTPS id p15sm2592679qct.46.2011.07.31.08.55.21 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 31 Jul 2011 08:55:22 -0700 (PDT)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: draft-housley-two-maturity-levels
Date: Sun, 31 Jul 2011 11:55:20 -0400
Message-Id: <B9333E33-0756-42B3-9A7C-357B4BF6250D@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: Sun, 31 Jul 2011 15:55:21 -0000

On 31st July 2011, Brian Carpenter wrote, in part:
> I believe that the present situation is confusing both to IETF =
newcomers
> (who may falsely believe that the IETF actually follows the 3 stage =
process)
> and, worse, confusing to users of IETF standards (who may falsely =
believe
> that a document isn't useful until it's advanced). We, and those =
users,
> gain by reducing the confusion. (Note: I did not write "eliminating =
the
> confusion".)

I agree totally with Brian's assessment.

> It defines a practice which is *very* close to present practice,
> apart from a minor name change. I think that's the best we can do,
> but that's why it's a baby step, not a no-op.

Also agreed.

> It might cause a change, simply because the effort of making the =
single
> move PS->IS will get you to the end state, whereas previously you had
> to make two efforts, PS->DS->STD. But only time will tell if this =
changes
> our collective behaviour.

Making this process change definitely will change my attitude=20
towards trying to advance standards-track RFCs that I am directly=20
involved with. =20

Until now, the process overhead to move from PS to STD was far too great=20=

to justify the time spent.  My perception is that this change reduces=20
the process work substantially -- and a change in perception (i.e.=20
"perception" by itself) is sufficient to increase my own motivation=20
to make the attempt. =20

While perception normally varies widely between individuals,=20
on virtually all topics, I am not alone in in the view
I've expressed just above.

Yours,

Ran


From eburger-l@standardstrack.com  Sun Jul 31 08:57:55 2011
Return-Path: <eburger-l@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 0AB3621F81D7 for <ietf@ietfa.amsl.com>; Sun, 31 Jul 2011 08:57:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.567
X-Spam-Level: 
X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[AWL=0.032,  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 KDvq5u0pRO59 for <ietf@ietfa.amsl.com>; Sun, 31 Jul 2011 08:57:54 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 65FD321F84E2 for <ietf@ietf.org>; Sun, 31 Jul 2011 08:57:48 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com;  h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=My2hjm4FEewseHFLZG+NF6al1Dq0iFpdRC8dI2six3LMpVsz7z6yjzDXumpnoATTqY/Hd/RhWzzbkDHq0dYA/5TDI0Bit2aYDpnX7rwBirP3cJijBWnT/dmpIB2Cgp0e;
Received: from dhcp-63da.meeting.ietf.org ([130.129.99.218]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger-l@standardstrack.com>) id 1QnYOl-0001Q4-5Q; Sun, 31 Jul 2011 08:57:51 -0700
Subject: Re: draft-housley-two-maturity-levels
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <B9333E33-0756-42B3-9A7C-357B4BF6250D@gmail.com>
Date: Sun, 31 Jul 2011 11:57:48 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <50B3F6F6-4364-446F-820B-350CFB359C9B@standardstrack.com>
References: <B9333E33-0756-42B3-9A7C-357B4BF6250D@gmail.com>
To: RJ Atkinson <rja.lists@gmail.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: 
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2011 15:57:55 -0000

On Jul 31, 2011, at 11:55 AM, RJ Atkinson wrote:
> On 31st July 2011, Brian Carpenter wrote, in part:

[snip]

>> It might cause a change, simply because the effort of making the single
>> move PS->IS will get you to the end state, whereas previously you had
>> to make two efforts, PS->DS->STD. But only time will tell if this changes
>> our collective behaviour.
> 
> Making this process change definitely will change my attitude 
> towards trying to advance standards-track RFCs that I am directly 
> involved with.  
> 
> Until now, the process overhead to move from PS to STD was far too great 
> to justify the time spent.  My perception is that this change reduces 
> the process work substantially -- and a change in perception (i.e. 
> "perception" by itself) is sufficient to increase my own motivation 
> to make the attempt.  
> 
> While perception normally varies widely between individuals, 
> on virtually all topics, I am not alone in in the view
> I've expressed just above.
> 
> Yours,
> 
> Ran

This is the intent.


From richard@shockey.us  Sun Jul 31 09:46:17 2011
Return-Path: <richard@shockey.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 C999821F8828 for <ietf@ietfa.amsl.com>; Sun, 31 Jul 2011 09:46:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.648
X-Spam-Level: 
X-Spam-Status: No, score=-101.648 tagged_above=-999 required=5 tests=[AWL=0.617, 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 AmghWSUQzYh5 for <ietf@ietfa.amsl.com>; Sun, 31 Jul 2011 09:46:17 -0700 (PDT)
Received: from oproxy8-pub.bluehost.com (oproxy8-pub.bluehost.com [69.89.22.20]) by ietfa.amsl.com (Postfix) with SMTP id 0530D21F8794 for <ietf@ietf.org>; Sun, 31 Jul 2011 09:46:16 -0700 (PDT)
Received: (qmail 4745 invoked by uid 0); 31 Jul 2011 16:46:20 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy8.bluehost.com with SMTP; 31 Jul 2011 16:46:20 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us; s=default;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:Cc:To:From; bh=pyWoquc87PpRMcxmf8c3pYJ73fG066yltZruAQLytsc=;  b=i8Vp/T7JUoASx94VroaTxj4qcS1I7WbQo8/uj0mINHBnPNuH1his1u6hxPsDUr8vvBc9NpjoeW5kcHoa2NPk4l9OaAD7UWHcD8aLt8ZUWvbiqbHnb0wcvQvaBQ0pCU7a;
Received: from pool-71-178-24-118.washdc.fios.verizon.net ([71.178.24.118] helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.76) (envelope-from <richard@shockey.us>) id 1QnZ9f-0004Zd-R2; Sun, 31 Jul 2011 10:46:20 -0600
From: "Richard Shockey" <richard@shockey.us>
To: "'Hadriel Kaplan'" <HKaplan@acmepacket.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <B8E48539-BB03-41AB-8484-769624453E91@standardstrack.com>
In-Reply-To: <B8E48539-BB03-41AB-8484-769624453E91@standardstrack.com>
Subject: RE: A modest proposal for Friday meeting schedule
Date: Sun, 31 Jul 2011 12:46:16 -0400
Message-ID: <007301cc4fa1$5eb34e40$1c19eac0$@us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcxPmUQ3/BAAq5pWS8+EmdNDFx0sLAACAm5Q
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 71.178.24.118 authed with richard@shockey.us}
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: Sun, 31 Jul 2011 16:46:17 -0000

+1 to that as well ..an excellent proposal. 

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Eric
Burger
Sent: Sunday, July 31, 2011 11:48 AM
To: Hadriel Kaplan
Cc: IETF-Discussion list
Subject: Re: A modest proposal for Friday meeting schedule

I don't think I have seen a proposal like this before.  I really like it, as
there are a bunch of post-IETF stuff, some of which starts in the afternoon
and thus conflicts with the IETF. This fixes that problem, enables us to
have the same amount of meeting time, and potentially lets people get home a
day early.

On Jul 31, 2011, at 11:40 AM, Hadriel Kaplan wrote:

> Howdy,
> First I'd like to thank the organizers for IETF-81 for another well-run
meeting.  The logistics and coordination for such an event must be daunting,
and I know we (the attendees) tend to focus on the negatives rather than the
positives... but we really are thankful for all the time and effort put into
it.  Thank you!
> 
> I would also like to propose a small change for future meetings.  On
Friday, instead of having a 2.5 hour WG meeting, followed by a 1.5 hour
lunch break, followed by 2 hours of WG meetings... perhaps we could just
have 4.5 hours of WG meetings straight and also start a bit earlier?  
> 
> Something like this:
> 8:30-11:00 Session I
> 11:15-12:15 Session II
> 12:30-13:30 Session III
> End
> 
> That way the people who need to get to an airport get more time, or fewer
of them have to miss WG meetings, etc.  And it would help reduce costs for
attendees if they can avoid staying Friday night at the hotel.  And lunch at
13:30 doesn't seem unreasonable (to me).
> 
> I apologize if this has been brought up before.  I tried to find it from
an old email thread for the "Experiment" at IETF-73 which added the Friday
afternoon sessions, but did not see this proposal being suggested.
> 
> -hadriel
> 
> _______________________________________________
> 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 mra@pobox.com  Sun Jul 31 13:42:04 2011
Return-Path: <mra@pobox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDC6421F889D for <ietf@ietfa.amsl.com>; Sun, 31 Jul 2011 13:42:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZKs74utFkI3g for <ietf@ietfa.amsl.com>; Sun, 31 Jul 2011 13:42:04 -0700 (PDT)
Received: from smtp.pobox.com (b-pb-sasl-quonix.pobox.com [208.72.237.35]) by ietfa.amsl.com (Postfix) with ESMTP id 4B96D21F8839 for <ietf@ietf.org>; Sun, 31 Jul 2011 13:42:04 -0700 (PDT)
Received: from smtp.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id 861DD468C for <ietf@ietf.org>; Sun, 31 Jul 2011 16:42:07 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=mime-version :in-reply-to:references:from:date:message-id:subject:to :content-type; s=sasl; bh=VjZAPHw5fCr9DQZ1Z1Lxh4i4PIw=; b=p9HYQH 0uFli3nlqMZe9Seg82JfZAAuOFDDchPyMEt7VVUMK38bY1jAhL1zsEfmnFarczLf IHpq+fpEs1NhjKswtX5k0wAWvoEi7ajG33nKCxrsevrkdrNUR2zScpkYc01SSIr2 e1Q1M2LsP5lM0um0SQ4ByzRBBH7ddiO4Y5uxY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=mime-version :in-reply-to:references:from:date:message-id:subject:to :content-type; q=dns; s=sasl; b=MrNxKyiCr8vbkE7RQAZ4KZy3Yel4uQkx m7mb3yl2ehJ9YwT5Nru5Q49FebXqzx1QUyiNK9vbotaJ1RvlWtH9ebQ/+M1PjuaT wnBHB5y5j76AqTSrv4tifnmZsz5cblg2ruek36QfQjGgJMI8rFA1Fb8cyMZyzSy6 BTCxwYQ4Ans=
Received: from b-pb-sasl-quonix.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id 7D679468B for <ietf@ietf.org>; Sun, 31 Jul 2011 16:42:07 -0400 (EDT)
Received: from mail-qw0-f44.google.com (unknown [209.85.216.44]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by b-sasl-quonix.pobox.com (Postfix) with ESMTPSA id 45388468A for <ietf@ietf.org>; Sun, 31 Jul 2011 16:42:07 -0400 (EDT)
Received: by qwc23 with SMTP id 23so3311647qwc.31 for <ietf@ietf.org>; Sun, 31 Jul 2011 13:42:07 -0700 (PDT)
Received: by 10.224.198.194 with SMTP id ep2mr2942087qab.117.1312144927066; Sun, 31 Jul 2011 13:42:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.45.67 with HTTP; Sun, 31 Jul 2011 13:41:47 -0700 (PDT)
In-Reply-To: <4E321E46.3080104@necom830.hpcl.titech.ac.jp>
References: <4E3118E1.5090107@necom830.hpcl.titech.ac.jp> <201107290028.p6T0SQgQ013589@fs4113.wdf.sap.corp> <CAD6AjGRik+N0OObpO=AZE=gowS6bjMJmXF-Oz4w+Yh3-iQ0CVA@mail.gmail.com> <4E321E46.3080104@necom830.hpcl.titech.ac.jp>
From: Mark Atwood <mra@pobox.com>
Date: Sun, 31 Jul 2011 13:41:47 -0700
Message-ID: <CANW5CYV37JBvFyJk-GjwONrtK=cDigPjjJcenbVgNsnRw+6SrQ@mail.gmail.com>
Subject: Re: "6to4 damages the Internet" (was Re:
To: ietf@ietf.org
Content-Type: text/plain; charset=UTF-8
X-Pobox-Relay-ID: 8E5D3784-BBB5-11E0-900F-1DC62E706CDE-82717895!b-pb-sasl-quonix.pobox.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Jul 2011 20:42:05 -0000

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>:
> Moreover, unlike nat64, nat44 can be fully transparent end to end.

Some people may consider it a feature that only incumbents with power
and money can usefully call listen(), and that useful user to user
activities requires the cooperation of an intrusive 3rd party, while
mere users and upstarts can only call connect().

Some people consider that a feature.  I do not.

It is, in fact, getting really hard to avoid assuming malice on the
part of people who want to nail the world to the nat44 cross.

.. Mark Atwood

From sob@harvard.edu  Sun Jul 31 17:55:51 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 01AE521F8794 for <ietf@ietfa.amsl.com>; Sun, 31 Jul 2011 17:55:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LFViPDiUuqp7 for <ietf@ietfa.amsl.com>; Sun, 31 Jul 2011 17:55:50 -0700 (PDT)
Received: from barracuda.ethostream.com (gleek.ethostream.com [66.195.129.15]) by ietfa.amsl.com (Postfix) with ESMTP id DC0B921F86D8 for <ietf@ietf.org>; Sun, 31 Jul 2011 17:55:49 -0700 (PDT)
X-ASG-Debug-ID: 1312159617-5c4b00050000-h9jmKw
X-Barracuda-URL: http://66.195.129.15:8000/cgi-bin/mark.cgi
Received: from relay.ethostream.com (www1.ethostream.com [66.195.129.11]) by barracuda.ethostream.com (Spam & Virus Firewall) with ESMTP id 353D311D1115 for <ietf@ietf.org>; Sun, 31 Jul 2011 19:46:57 -0500 (CDT)
Received: from relay.ethostream.com (www1.ethostream.com [66.195.129.11]) by barracuda.ethostream.com with ESMTP id A4K9DAGDbCQ3wSdG for <ietf@ietf.org>; Sun, 31 Jul 2011 19:46:57 -0500 (CDT)
Received: from ethoserver.ezone.net (173-167-136-97-illinois.hfc.comcastbusiness.net [173.167.136.97]) by relay.ethostream.com (Postfix) with ESMTPA id 153DD89032E for <ietf@ietf.org>; Sun, 31 Jul 2011 19:46:54 -0500 (CDT)
Received: from soblap3.sobco.com (unknown [172.16.1.172]) by ethoserver.ezone.net (Postfix) with ESMTP id 29EA4A1F6B8 for <ietf@ietf.org>; Sun, 31 Jul 2011 19:46:43 -0500 (CDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by soblap3.sobco.com (Postfix) with ESMTP id 21FB33B965F; Thu, 28 Jul 2011 14:39:25 -0400 (EDT)
X-ASG-Orig-Subj: Re: draft-housley-two-maturity-levels
Subject: Re: draft-housley-two-maturity-levels
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-5-711199685
From: Scott O Bradner <sob@harvard.edu>
In-Reply-To: <12B69DB8-AFDD-4C40-BC9A-0A8158D9F7C0@nostrum.com>
Date: Thu, 28 Jul 2011 14:39:24 -0400
Message-Id: <72BFC611-FAC0-4C82-A96E-24DCEFA7639A@harvard.edu>
References: <20110728121904.2D22AD7A76F@newdev.eecs.harvard.edu> <12B69DB8-AFDD-4C40-BC9A-0A8158D9F7C0@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.1084)
X-Barracuda-Connect: www1.ethostream.com[66.195.129.11]
X-Barracuda-Start-Time: 1312159617
X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at ethostream.com
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=1.4 tests=HTML_MESSAGE
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.70548 Rule breakdown below pts rule name              description ---- ---------------------- -------------------------------------------------- 0.00 HTML_MESSAGE           BODY: HTML included in message
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 00:55:51 -0000

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

it looks so - maybe it would be good to have a pointer in this doc

Scott

On Jul 28, 2011, at 9:19 AM, Robert Sparks wrote:

> Scott -
>=20
> Didn't RFC 5657 address your point 2?
>=20
> The current proposal no longer requires this report during =
advancement, but it does not disallow it.
> I hope it's obvious that I believe these reports are valuable, but I =
am willing to accept the proposed
> structure, with the hope and expectation that  communities that are =
serious about producing and=20
> refining protocols will be producing these reports anyhow.
>=20
> RjS
>=20
> On Jul 28, 2011, at 8:19 AM, Scott O. Bradner wrote:
>=20
>>=20
>> this is better than the last version but
>>=20
>> 1/ I still see no reason to think that this change will cause any
>> significant change in the percent of Proposed Standards that move up =
the
>> (shorter) standards track since the proposal does nothing to change =
the
>> underlying reasons that people do not expend the effort needed to
>> advance documents
>>=20
>> 2/ one of the big issues with the PS->DS step is understanding what
>> documentation is needed to show that there are the interoperable
>> implementations and to list the unused features - it would help a lot =
to
>> provide some guidance (which I did not do in 2026 - as I have been
>> reminded a number of times :-) ) as to just what process is to be
>> followed
>>=20
>> could be
>> 	a spread sheet showing features & implementations
>> 	an assertion by the person proposing the advancement that the
>> requirements have been met
>> or something in between
>>=20
>> Scott
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>=20

Scott Bradner

Harvard University Information Technology
Security | Policy, Risk & Compliance
+1 617 495 3864
29 Oxford St., Room 407
Cambridge, MA 02138
www.harvard.edu/huit





--Apple-Mail-5-711199685
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; ">it =
looks so - maybe it would be good to have a pointer in this =
doc<div><br></div><div>Scott</div><div><br><div><div>On Jul 28, 2011, at =
9:19 AM, Robert Sparks wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>Scott =
-<br><br>Didn't RFC 5657 address your point 2?<br><br>The current =
proposal no longer requires this report during advancement, but it does =
not disallow it.<br>I hope it's obvious that I believe these reports are =
valuable, but I am willing to accept the proposed<br>structure, with the =
hope and expectation that &nbsp;communities that are serious about =
producing and <br>refining protocols will be producing these reports =
anyhow.<br><br>RjS<br><br>On Jul 28, 2011, at 8:19 AM, Scott O. Bradner =
wrote:<br><br><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">this is better than the last version =
but<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">1/ I still see no reason to think that this change will =
cause any<br></blockquote><blockquote type=3D"cite">significant change =
in the percent of Proposed Standards that move up =
the<br></blockquote><blockquote type=3D"cite">(shorter) standards track =
since the proposal does nothing to change =
the<br></blockquote><blockquote type=3D"cite">underlying reasons that =
people do not expend the effort needed to<br></blockquote><blockquote =
type=3D"cite">advance documents<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">2/ one of the =
big issues with the PS-&gt;DS step is understanding =
what<br></blockquote><blockquote type=3D"cite">documentation is needed =
to show that there are the interoperable<br></blockquote><blockquote =
type=3D"cite">implementations and to list the unused features - it would =
help a lot to<br></blockquote><blockquote type=3D"cite">provide some =
guidance (which I did not do in 2026 - as I have =
been<br></blockquote><blockquote type=3D"cite">reminded a number of =
times :-) ) as to just what process is to be<br></blockquote><blockquote =
type=3D"cite">followed<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">could =
be<br></blockquote><blockquote type=3D"cite"><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>a spread =
sheet showing features &amp; implementations<br></blockquote><blockquote =
type=3D"cite"><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>an assertion by the person proposing the advancement that =
the<br></blockquote><blockquote type=3D"cite">requirements have been =
met<br></blockquote><blockquote type=3D"cite">or something in =
between<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Scott<br></blockquote><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote><blockquote type=3D"cite">Ietf mailing =
list<br></blockquote><blockquote type=3D"cite"><a =
href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br></blockquote><blockquot=
e type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/ietf">https://www.ietf.org/m=
ailman/listinfo/ietf</a><br></blockquote><br></div></blockquote></div><br>=
<div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: =
0px; -webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div>Scott =
Bradner</div><div><br></div><div>Harvard University Information =
Technology</div><div>Security |&nbsp;Policy, Risk &amp; =
Compliance</div><div>+1 617 495 3864</div><div>29 Oxford St., Room =
407</div><div>Cambridge, MA 02138</div><div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: =
normal normal normal 11px/normal Arial; color: rgb(59, 0, 255); "><a =
href=3D"http://www.harvard.edu/huit">www.harvard.edu/huit</a></div></div><=
div><br></div></div></span><br =
class=3D"Apple-interchange-newline"></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></div></body></html>=

--Apple-Mail-5-711199685--

From brian.e.carpenter@gmail.com  Sun Jul 31 18:15:51 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 B632321F85EC for <ietf@ietfa.amsl.com>; Sun, 31 Jul 2011 18:15:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.601
X-Spam-Level: 
X-Spam-Status: No, score=-103.601 tagged_above=-999 required=5 tests=[AWL=-0.002, 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 X64J0ZcV7FgK for <ietf@ietfa.amsl.com>; Sun, 31 Jul 2011 18:15:51 -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 331A021F8593 for <ietf@ietf.org>; Sun, 31 Jul 2011 18:15:51 -0700 (PDT)
Received: by iye7 with SMTP id 7so7500644iye.31 for <ietf@ietf.org>; Sun, 31 Jul 2011 18:15:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=JQF4Q+cx3p9dSMregXdorCSKe1BqXBFEk8ImVXT44vA=; b=pDg2jCEbn5A80zeqrka6W57dDtdh2nl0l0Eki4hsR3GfnrBzQ78JBgEXSIRviXNIxk K09v3QjEzD/rIwSACSJLboD9xKVwN3l9tQVBBxW2GCvvGPCynSYbPh4RhUKYemWARy52 kQqgohnoeG3tlIIuxccT//YNR4wnLz+hzxBlc=
Received: by 10.231.211.199 with SMTP id gp7mr2046766ibb.188.1312161355955; Sun, 31 Jul 2011 18:15:55 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id uz2sm2941948icb.12.2011.07.31.18.15.53 (version=SSLv3 cipher=OTHER); Sun, 31 Jul 2011 18:15:55 -0700 (PDT)
Message-ID: <4E35FE44.6050702@gmail.com>
Date: Mon, 01 Aug 2011 13:15:48 +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: Olaf Kolkman <olaf@NLnetLabs.nl>
Subject: Re: IAOC: delegating ex-officio responsibility
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl> <F31C7D4B-12A5-4520-B0D5-F9CD7FCF3EB5@NLnetLabs.nl>
In-Reply-To: <F31C7D4B-12A5-4520-B0D5-F9CD7FCF3EB5@NLnetLabs.nl>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 01:15:51 -0000

On 2011-07-27 00:52, Olaf Kolkman wrote:
> Dear Colleagues,
> 
> 
> 
> 
> 
> Based on the discussion I've updated the draft:
> http://tools.ietf.org/html/draft-kolkman-iasa-ex-officio-membership
> 
> Essentially I incorporated Dave Crocker's proposal to 
> 1) replace the 'chairs' by voting members appointed by the respective bodies.
> 2) allow the chairs to participate in all meetings and provide (unsolicited) advice.
> 
> I believe that allows chairs to exercise their responsibilities of keeping a coherent perspective of the organization an allow them to steer outcomes if needed, but doesn't require the day-to-day involvement that is required from a diligent voting member.

And it therefore removes the two Chairs' shared responsibility for decisions of
the IAOC and the IETF Trust. I am still far from convinced that this is a good
thing.

Also, the new section 2.3, which is incorrectly titled but presumably
is intended to be "IETF Trust membership" seems to me to be inconsistent
with the Trust Agreement. The Trust Agreement states that the Eligible Persons
(to become Trustees) are each "a then-current member of the IAOC, duly appointed
and in good standing in accordance with the procedures of the IAOC established
pursuant to IETF document BCP 101 [as amended]". That doesn't exclude the
non-voting members of the IAOC, which is why the IAD is already a Trustee.
To change this, the Trust would have to change the Trust Agreement. To be clear,
I'm not saying this can't be done, but it can't be ignored either.

    Brian

From yoshifumi.nishida@gmail.com  Sun Jul 31 21:58:47 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 4455D21F85DA; Sun, 31 Jul 2011 21:58:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.805
X-Spam-Level: 
X-Spam-Status: No, score=-102.805 tagged_above=-999 required=5 tests=[AWL=-0.055, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ed8diq-TVvOJ; Sun, 31 Jul 2011 21:58:46 -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 8319021F85A1; Sun, 31 Jul 2011 21:58:43 -0700 (PDT)
Received: by iye7 with SMTP id 7so7712823iye.31 for <multiple recipients>; Sun, 31 Jul 2011 21:58:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=YJ76QgGtXESITksLwOUihTJoJoWlNI7agKE5J/tgoXI=; b=XSGPCenYM4NkMrb3uALuQPPDy/muCVUlYLOAaVfVQU/soRQZFZWO8e8Lqpu1xPYRAM 9ROGWPvjeyZInvIOa2H+rF0/ChYv+FjLIk1gCBYOHkBKEryJxlrLkh1dm8A0CLxv4Yf+ X/RY7UEkRiniCGrhsU8Rwg0BqGiT1VDM5NP0c=
MIME-Version: 1.0
Received: by 10.231.119.216 with SMTP id a24mr2803258ibr.58.1312174726387; Sun, 31 Jul 2011 21:58:46 -0700 (PDT)
Sender: yoshifumi.nishida@gmail.com
Received: by 10.231.199.12 with HTTP; Sun, 31 Jul 2011 21:58:46 -0700 (PDT)
Date: Sun, 31 Jul 2011 21:58:46 -0700
X-Google-Sender-Auth: xol0NoegZ0PyF4j4dld_uf4u2YY
Message-ID: <CABxaRLEkhoNuTr=rE2r4C2D6spj3bb0X0r3czttJky6cgNK2KQ@mail.gmail.com>
Subject: tsv-dir review of draft-ietf-karp-threats-reqs-03
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: karp@ietf.org, ietf@ietf.org, draft-ietf-karp-threats-reqs@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: 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, 01 Aug 2011 04:58:47 -0000

Hello folks,

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.

Transport Issues:

I had some difficulties to grasp the objective of the document,
however, I believe it's

   This document does not contain protocol specifications.  Instead, it
   defines the areas where protocol specification work is needed and
   sets a direction, a set of requirements, and a relative priority for
   addressing that specification work.

as it is stated in Section 1.3.
Along with this context, I can understand section 2 and 3 are written
for this purpose. Also, I think there is no specific transport layer
concern in this document since there's no detailed discussion for
protocol specs.
However, if my presumption on the objective of the document is right,
I think the title of this draft might not be appropriate. It would be
something like "The Goal and Requirements for Cryptographic Authentication
of Routing Protocols' Transports" or "The Requirements for Cryptographic
Authentication of Routing Protocols' Transports". Because there is not
threat analysis in the document. Also, abstract will need to be updated.


Other minor comments:

As stated above, I have some difficulties to read this document. I think
this is likely because I'm not an expected audience for the document.
However, if you think some of the following points are also reasonable
for some expected audience, please consider updating.

1: I prefer that the objective of the draft is articulated at the beginning
   of the document. It will be very helpful to read the rest of the document.

2: I think it would be better to separate the introduction of this draft
   and KARP project. For example, it is a bit confusing for me to understand
   the focus of this draft since it is mixed with the focus of the KARP
   in Section 1.3.
   I think Section 1.1, 1.2 and 1.7 can be put in the introduction of
   this draft and 1.3, 1.4, 1.5, 1.6 can be put in another section which
   describes the overview of KARP.

3: I think it depends on the objective of the draft, but I feel some texts
   in Section 1 is not necessary for this draft. For example, I'm not very
   sure the audience of this doc need to read Section 1.4.
   Also, Section 1.5 seems to be too long.

   There are also many mentions about roadmap in this draft, but I'm not
   very sure these are necessary since this is not a roadmap document.
   (Hence, I don't understand the meaning of "this roadmap document". )

4: Section 3 only describes the requirement for Phase 1.
   Will be there another document for Phase 2 or we don't need it?

5: 24 requirements seems to be too many to check easily.
   I think it would be better to categorize them in some ways.
   (priority? protocols? approach?)


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

From mohta@necom830.hpcl.titech.ac.jp  Sun Jul 31 22:29:31 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 A00DC21F8561 for <ietf@ietfa.amsl.com>; Sun, 31 Jul 2011 22:29:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.08
X-Spam-Level: 
X-Spam-Status: No, score=-0.08 tagged_above=-999 required=5 tests=[AWL=0.010,  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 eLJQ-+RR3O6c for <ietf@ietfa.amsl.com>; Sun, 31 Jul 2011 22:29:30 -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 3367C21F8559 for <ietf@ietf.org>; Sun, 31 Jul 2011 22:29:29 -0700 (PDT)
Received: (qmail 6035 invoked from network); 1 Aug 2011 05:50:46 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 1 Aug 2011 05:50:46 -0000
Message-ID: <4E363947.80002@necom830.hpcl.titech.ac.jp>
Date: Mon, 01 Aug 2011 14:27:35 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: "6to4 damages the Internet" (was Re:
References: <4E3118E1.5090107@necom830.hpcl.titech.ac.jp> <201107290028.p6T0SQgQ013589@fs4113.wdf.sap.corp> <CAD6AjGRik+N0OObpO=AZE=gowS6bjMJmXF-Oz4w+Yh3-iQ0CVA@mail.gmail.com> <4E321E46.3080104@necom830.hpcl.titech.ac.jp> <CANW5CYV37JBvFyJk-GjwONrtK=cDigPjjJcenbVgNsnRw+6SrQ@mail.gmail.com>
In-Reply-To: <CANW5CYV37JBvFyJk-GjwONrtK=cDigPjjJcenbVgNsnRw+6SrQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 05:29:31 -0000

Mark Atwood wrote:

>> Moreover, unlike nat64, nat44 can be fully transparent end to end.

> Some people may consider it a feature that only incumbents with power
> and money can usefully call listen(), and that useful user to user
> activities requires the cooperation of an intrusive 3rd party, while
> mere users and upstarts can only call connect().

> It is, in fact, getting really hard to avoid assuming malice on the
> part of people who want to nail the world to the nat44 cross.

Isn't port forwarding over legacy nat44 enough for you?

For me, port forwarding is not enough because it lacks
end to end transparency.

For example, you can't use PORT command of your ftp
client behind legacy nat.

See draft-ohta-e2e-nat-00.txt for how nat44 can be
transparent end to end.

OTOH, nat64 can not have end to end transparency.

						Masataka Ohta
