
From paul.hoffman@vpnc.org  Wed Aug  1 06:56:41 2012
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 E50A411E8116 for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 06:56:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r1DtuOjmnAAU for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 06:56:41 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 51DCF11E8113 for <ietf@ietf.org>; Wed,  1 Aug 2012 06:56:41 -0700 (PDT)
Received: from [192.168.0.22] (S01060026f3e16488.vc.shawcable.net [24.84.235.32]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q71D5QLB057323 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 1 Aug 2012 06:05:27 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com>
Date: Wed, 1 Aug 2012 06:56:37 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B7C8BE95-ADAF-4670-9C6B-7AA26D50FC7C@vpnc.org>
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1278)
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 13:56:42 -0000

On Jul 31, 2012, at 11:48 PM, Abdussalam Baryun wrote:

> I written this draft starting a RFC2119 update for the reasons of
> discussion threads in [1] and [2]. Please check draft and feedback,
> thanking you.

This is a useless change to a very stable document. No one reading RFCs =
misunderstands what "if" and "else" mean.

--Paul Hoffman=

From abdussalambaryun@gmail.com  Wed Aug  1 07:39:39 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 499B411E8106 for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 07:39:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.469
X-Spam-Level: 
X-Spam-Status: No, score=-4.469 tagged_above=-999 required=5 tests=[AWL=1.130,  BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lFewroHjJBNm for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 07:39:38 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id AC36C11E8100 for <ietf@ietf.org>; Wed,  1 Aug 2012 07:39:38 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so7625127vcb.31 for <ietf@ietf.org>; Wed, 01 Aug 2012 07:39:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=P02b5mbkk6x5H2DPbCEbpJNyp9i/iE1aGdjKOPLCR6c=; b=CMRYh4K5MXhBNAgtlEXvwaoYCC0xfuw0UZrmrWlvN5DZqZuHR/eK5jPbw91uZIAgXe e5dSeMGakoEo9hQZQ0rjzc3RSlsv2SO+XBqhrlKiqZR9ACr+fe27nluftsHUnkO54l6D wFkg671bZ8+jxk74rgXc2x9jw8BaI3QN6FrPJnyvIxciyNX2ljiyOcvqSU7sVFONANFn 3f+VMSJZ/1XQdIZ1MdZaOkagMa2RSGGovZLOxvoCw+y43CkYwfoKbP6LVU2YVUXOgY6P jl1fYyGTIeqJp4j+38xBuDQCDdjZL6JKwJAHUgw82C+4P9cJ7plEEOUSOo5NO5sAhstJ 8qLw==
MIME-Version: 1.0
Received: by 10.52.98.3 with SMTP id ee3mr9925586vdb.127.1343831978092; Wed, 01 Aug 2012 07:39:38 -0700 (PDT)
Received: by 10.220.141.200 with HTTP; Wed, 1 Aug 2012 07:39:37 -0700 (PDT)
In-Reply-To: <B7C8BE95-ADAF-4670-9C6B-7AA26D50FC7C@vpnc.org>
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com> <B7C8BE95-ADAF-4670-9C6B-7AA26D50FC7C@vpnc.org>
Date: Wed, 1 Aug 2012 16:39:37 +0200
Message-ID: <CADnDZ89gg8OYQCuaLHLCKt4BitXB-aC-d0dYGC+e05vTnr6O8A@mail.gmail.com>
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 14:39:39 -0000

> This is a useless change to a very stable document. No one reading RFCs
> misunderstands what "if" and "else" mean.

We don't change the RFC2119 (IETF RFCs never can be changed) its only
update, no one before ever misunderstood "may" and "should" either but
capital letters made difference. However, thanks for your comments,

AB

From daedulus@btconnect.com  Wed Aug  1 08:46:44 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C32921F8B4C for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 08:46:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.817
X-Spam-Level: 
X-Spam-Status: No, score=-2.817 tagged_above=-999 required=5 tests=[AWL=-1.632, BAYES_40=-0.185, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DN5T7842Gxln for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 08:46:43 -0700 (PDT)
Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe001.messaging.microsoft.com [213.199.154.204]) by ietfa.amsl.com (Postfix) with ESMTP id 7063C21F8B45 for <ietf@ietf.org>; Wed,  1 Aug 2012 08:46:42 -0700 (PDT)
Received: from mail14-am1-R.bigfish.com (10.3.201.249) by AM1EHSOBE008.bigfish.com (10.3.204.28) with Microsoft SMTP Server id 14.1.225.23; Wed, 1 Aug 2012 15:46:41 +0000
Received: from mail14-am1 (localhost [127.0.0.1])	by mail14-am1-R.bigfish.com (Postfix) with ESMTP id 88C48402F3; Wed,  1 Aug 2012 15:46:41 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.224.141; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0702HT008.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: PS-23(zz9371I542M1432Izz1202hzz1033IL8275bh8275dhz2dh2a8h5a9h668h839hd24hf0ah107ah304l)
Received: from mail14-am1 (localhost.localdomain [127.0.0.1]) by mail14-am1 (MessageSwitch) id 1343835999403191_23750; Wed,  1 Aug 2012 15:46:39 +0000 (UTC)
Received: from AM1EHSMHS008.bigfish.com (unknown [10.3.201.230])	by mail14-am1.bigfish.com (Postfix) with ESMTP id 56E1D1E004F; Wed,  1 Aug 2012 15:46:39 +0000 (UTC)
Received: from DB3PRD0702HT008.eurprd07.prod.outlook.com (157.55.224.141) by AM1EHSMHS008.bigfish.com (10.3.207.108) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 1 Aug 2012 15:46:35 +0000
Received: from SN2PRD0310HT005.namprd03.prod.outlook.com (157.56.234.5) by pod51017.outlook.com (10.3.4.173) with Microsoft SMTP Server (TLS) id 14.15.86.1; Wed, 1 Aug 2012 15:46:30 +0000
Message-ID: <008801cd6ffc$37ba2440$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: <ietf@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
References: <20120731214755.6CF4118C10A@mercury.lcs.mit.edu>
Subject: Re: RFC and I-D Citation Tool
Date: Wed, 1 Aug 2012 16:42:01 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.234.5]
X-OriginatorOrg: btconnect.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 15:46:44 -0000

----- Original Message -----
From: "Noel Chiappa" <jnc@mercury.lcs.mit.edu>
To: <ietf@ietf.org>
Cc: <rsoc@iab.org>; <jnc@mercury.lcs.mit.edu>; <rsag@rfc-editor.org>
Sent: Tuesday, July 31, 2012 10:47 PM
>     > From: Ole Jacobsen <ole@cisco.com>
>
>     > using the American "quotation outside punctuation rule."
>
> Ugh. There may be uglier typographic conventions, but off the top of
my head,
> I can't come up with one.

Ugh indeed, but I find the "space before every comma" rule even uggier.

Tom Petch

>
> Noel
>



From melinda.shore@gmail.com  Wed Aug  1 08:46:58 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E80021F8B52 for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 08:46:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 52FyVW4iwbk3 for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 08:46:57 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id B6CEB21F8B4D for <ietf@ietf.org>; Wed,  1 Aug 2012 08:46:57 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so8013743ghb.31 for <ietf@ietf.org>; Wed, 01 Aug 2012 08:46:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ceuspzMW6RPK4QBSHgc3vEPbxLFe98U2eLzf7NSSJ3Y=; b=t/loSqvs/tt6GLWya9u+KdCva1O93Yna0WME9tFBJqeCz46YlCaKXi9x5Wf8pGgNYY AijUPwNXhmYJ1lwNXZ8xMjDOR3TFl0VPm9j/erZMbFDuKXGtLglw9o4R/uePdHlCJ/uI WubvVxaYUKOy6mxbiZTFCuZf/j9ZX1POklmBgt/Eoq05FNA8uEnTbVxr9tBu/TeJ4LXW F9c4dWSM5nU81QnSWKGUUmPuaf1zFVhtrkrvgs/MOp7Yv7zHC2DxREfDUCZg2Z7naYcc bWId4P9iAFO6H2cVPXeNTaUUnuixcZYPf0L4urO6Qv99RkicVwXSOsdYyBTc5E+JSqTx Yp4Q==
Received: by 10.66.84.229 with SMTP id c5mr3975884paz.12.1343836016960; Wed, 01 Aug 2012 08:46:56 -0700 (PDT)
Received: from ?IPv6:2001:df8:0:16:2c86:4d38:4ced:b2b3? ([2001:df8:0:16:2c86:4d38:4ced:b2b3]) by mx.google.com with ESMTPS id qc5sm2822937pbb.6.2012.08.01.08.46.55 (version=SSLv3 cipher=OTHER); Wed, 01 Aug 2012 08:46:56 -0700 (PDT)
Message-ID: <50194FA8.9000205@gmail.com>
Date: Wed, 01 Aug 2012 07:47:52 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com> <B7C8BE95-ADAF-4670-9C6B-7AA26D50FC7C@vpnc.org> <CADnDZ89gg8OYQCuaLHLCKt4BitXB-aC-d0dYGC+e05vTnr6O8A@mail.gmail.com>
In-Reply-To: <CADnDZ89gg8OYQCuaLHLCKt4BitXB-aC-d0dYGC+e05vTnr6O8A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 15:46:58 -0000

On 8/1/2012 6:39 AM, Abdussalam Baryun wrote:
> We don't change the RFC2119 (IETF RFCs never can be changed) its only
> update, no one before ever misunderstood "may" and "should" either but
> capital letters made difference. However, thanks for your comments,

To the contrary - people confuse MAY and SHOULD all the time.
Regardless, you're not solving anything resembling an actual
problem.

Melinda


From barryleiba.mailing.lists@gmail.com  Wed Aug  1 09:04:14 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1B0821F8869 for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 09:04:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.958
X-Spam-Level: 
X-Spam-Status: No, score=-102.958 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jtPhrfMxctbL for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 09:04:00 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 91CDD21F8861 for <ietf@ietf.org>; Wed,  1 Aug 2012 09:03:59 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id go11so481817lbb.31 for <ietf@ietf.org>; Wed, 01 Aug 2012 09:03:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=BWwLYs0/Ga2IRnvPR9i8snDrdhZ9O9ccxjBQ/dgU23I=; b=EL7dPR90Mx8DHFubkZIowhEOXeLfdb6KGVJGaokahxrumn79xKEn8ZJTBmIbFTJoCh pSdW7DKa/TVDpEPXi1+btjKa8j4w8V+cMJzbllLu+Vxec9lQPK3RcRXUsO40Sh70n+B2 PUtGZAdnZqk7KNnKsrJLuV0pRllo90pqwZDS28Fe23bs8Vzln9pIqcT556XM5HmhVZql 92DDkuY05EpeMKdQbodIHvp0KP5O0kc+aWk0MhUqUIrTIA5fFGUmASgYAkQ/1oTukNBF ACz/GpOygBiUu20Q1bDOllFYWRtAqS1iAQsJhrPNEWRnQuVceieCTlhCs/B9n/veBp4f JiMA==
MIME-Version: 1.0
Received: by 10.112.44.163 with SMTP id f3mr8267800lbm.59.1343837039209; Wed, 01 Aug 2012 09:03:59 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.17.133 with HTTP; Wed, 1 Aug 2012 09:03:59 -0700 (PDT)
In-Reply-To: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com>
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com>
Date: Wed, 1 Aug 2012 12:03:59 -0400
X-Google-Sender-Auth: pMNCvZBkAYhAVi821SdcW5kZc0Y
Message-ID: <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com>
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
From: Barry Leiba <barryleiba@computer.org>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec554d23e5bae1f04c63671b9
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 16:04:14 -0000

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

>
> I written this draft starting a RFC2119 update for the reasons of
> discussion threads in [1] and [2]. Please check draft and feedback,
> thanking you.
>

I agree with what Paul and Melinda have said.  This document is pointless,
as there is no actual problem that it's solving and no misunderstanding
that it's clarifying.  Further, it's actively *harmful*.  It's arguable
that 2119 already reserves too many words by giving them specific,
normative meanings (SHALL *and* MUST; SHOULD *and* RECOMMENDED).  Adding
IF, THEN, and ELSE would not only be unnecessary, but downright *bad*.

Barry

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

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I written this draft starting a RFC2119 upda=
te for the reasons of<br>
discussion threads in [1] and [2]. Please check draft and feedback,<br>
thanking you.<br>
</blockquote><div><br></div><div>I agree with what Paul and Melinda have sa=
id. =A0This document is pointless, as there is no actual problem that it&#3=
9;s solving and no misunderstanding that it&#39;s clarifying. =A0Further, i=
t&#39;s actively *harmful*. =A0It&#39;s arguable that 2119 already reserves=
 too many words by giving them specific, normative meanings (SHALL *and* MU=
ST; SHOULD *and* RECOMMENDED). =A0Adding IF, THEN, and ELSE would not only =
be unnecessary, but downright *bad*.</div>
<div><br></div><div>Barry=A0<span></span></div>

--bcaec554d23e5bae1f04c63671b9--

From paul.hoffman@vpnc.org  Wed Aug  1 09:08:11 2012
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 DB90911E810B for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 09:08:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.299
X-Spam-Level: 
X-Spam-Status: No, score=-103.299 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6GXKP-hTAfrw for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 09:08: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 557A511E80FD for <ietf@ietf.org>; Wed,  1 Aug 2012 09:08:11 -0700 (PDT)
Received: from dhcp-2066.meeting.ietf.org (dhcp-2066.meeting.ietf.org [130.129.32.102]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q71FGu7G010694 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 1 Aug 2012 08:16:56 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CADnDZ89gg8OYQCuaLHLCKt4BitXB-aC-d0dYGC+e05vTnr6O8A@mail.gmail.com>
Date: Wed, 1 Aug 2012 09:08:07 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <4F6A64BE-7944-4FEE-9AAF-704EE465438F@vpnc.org>
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com> <B7C8BE95-ADAF-4670-9C6B-7AA26D50FC7C@vpnc.org> <CADnDZ89gg8OYQCuaLHLCKt4BitXB-aC-d0dYGC+e05vTnr6O8A@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1278)
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 16:08:12 -0000

On Aug 1, 2012, at 7:39 AM, Abdussalam Baryun wrote:

>> This is a useless change to a very stable document. No one reading =
RFCs
>> misunderstands what "if" and "else" mean.
>=20
> We don't change the RFC2119 (IETF RFCs never can be changed) its only
> update,

An update is a change.

> no one before ever misunderstood "may" and "should" either but
> capital letters made difference.

Both clauses in that sentence are incorrect. People very much =
misunderstood "should", which was one of the primary purposes for =
nailing it down in RFC 2119. The capital letters don't actually make the =
difference, the definition of the words make the difference.

> However, thanks for your comments,

No problem.

--Paul Hoffman=

From mnot@mnot.net  Wed Aug  1 09:28:06 2012
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B18311E8180 for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 09:28:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.863
X-Spam-Level: 
X-Spam-Status: No, score=-105.863 tagged_above=-999 required=5 tests=[AWL=-3.264, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 43CrKnmYOQ-Q for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 09:28:05 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id A0FD411E817D for <ietf@ietf.org>; Wed,  1 Aug 2012 09:28:05 -0700 (PDT)
Received: from dhcp-40be.meeting.ietf.org (unknown [130.129.64.190]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 7E77422E1F4; Wed,  1 Aug 2012 12:27:56 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com>
Date: Wed, 1 Aug 2012 09:27:56 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E07E0004-8BE7-4897-8980-16DA41F75464@mnot.net>
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com> <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1485)
Cc: ietf <ietf@ietf.org>, Abdussalam Baryun <abdussalambaryun@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 16:28:06 -0000

+1 to Barry, well said.

On 01/08/2012, at 9:03 AM, Barry Leiba <barryleiba@computer.org> wrote:

> I written this draft starting a RFC2119 update for the reasons of
> discussion threads in [1] and [2]. Please check draft and feedback,
> thanking you.
>=20
> I agree with what Paul and Melinda have said.  This document is =
pointless, as there is no actual problem that it's solving and no =
misunderstanding that it's clarifying.  Further, it's actively =
*harmful*.  It's arguable that 2119 already reserves too many words by =
giving them specific, normative meanings (SHALL *and* MUST; SHOULD *and* =
RECOMMENDED).  Adding IF, THEN, and ELSE would not only be unnecessary, =
but downright *bad*.
>=20
> Barry=20

--
Mark Nottingham
http://www.mnot.net/





From adrian@olddog.co.uk  Wed Aug  1 09:39:58 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A52A11E80E3 for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 09:39:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.578
X-Spam-Level: 
X-Spam-Status: No, score=-2.578 tagged_above=-999 required=5 tests=[AWL=0.020,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uLyp5+jqWTFK for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 09:39:57 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id B88DC11E8156 for <ietf@ietf.org>; Wed,  1 Aug 2012 09:39:56 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id q71GdoFQ031211;  Wed, 1 Aug 2012 17:39:50 +0100
Received: from 950129200 (dhcp-11f1.meeting.ietf.org [130.129.17.241]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id q71GdgeR031167 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 1 Aug 2012 17:39:45 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Barry Leiba'" <barryleiba@computer.org>, "'Abdussalam Baryun'" <abdussalambaryun@gmail.com>
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com> <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com>
In-Reply-To: <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com>
Subject: RE: New Version Notification for: draft-baryun-rfc2119-update-00.txt
Date: Wed, 1 Aug 2012 17:39:39 +0100
Message-ID: <034101cd7004$43758dd0$ca60a970$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0342_01CD700C.A53EB0C0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLw+3MjyVCsgx/3v7ilGpHvBIxheAJ4IDYAlOpQM9A=
Content-Language: en-gb
Cc: 'ietf' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 16:39:58 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0342_01CD700C.A53EB0C0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Barry,
 
Did you mean "bad" or "BAD"?
 
A
 
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Barry
Leiba
Sent: 01 August 2012 17:04
To: Abdussalam Baryun
Cc: ietf
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
 
I written this draft starting a RFC2119 update for the reasons of
discussion threads in [1] and [2]. Please check draft and feedback,
thanking you.
 
I agree with what Paul and Melinda have said.  This document is pointless, as
there is no actual problem that it's solving and no misunderstanding that it's
clarifying.  Further, it's actively *harmful*.  It's arguable that 2119 already
reserves too many words by giving them specific, normative meanings (SHALL *and*
MUST; SHOULD *and* RECOMMENDED).  Adding IF, THEN, and ELSE would not only be
unnecessary, but downright *bad*.
 
Barry 

------=_NextPart_000_0342_01CD700C.A53EB0C0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DProgId content=3DWord.Document><meta =
name=3DGenerator content=3D"Microsoft Word 14"><meta name=3DOriginator =
content=3D"Microsoft Word 14"><link rel=3DFile-List =
href=3D"cid:filelist.xml@01CD700C.770A88F0"><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:EnvelopeVis/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-GB</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:DoNotExpandShiftReturn/>
<w:BreakWrappedTables/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520092929 1073786111 9 0 415 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520081665 -1073717157 41 0 66047 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	mso-fareast-font-family:Calibri;}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue =
vlink=3Dpurple style=3D'tab-interval:36.0pt'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Barry,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Did you mean &quot;bad&quot; =
or &quot;BAD&quot;?<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>A<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New =
Roman";mso-ansi-language:EN-US'>From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New Roman";mso-ansi-language:EN-US'> =
ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] <b>On Behalf Of =
</b>Barry Leiba<br><b>Sent:</b> 01 August 2012 17:04<br><b>To:</b> =
Abdussalam Baryun<br><b>Cc:</b> ietf<br><b>Subject:</b> Re: New Version =
Notification for: =
draft-baryun-rfc2119-update-00.txt<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><blockquote =
style=3D'border:none;border-left:solid #CCCCCC =
1.0pt;mso-border-left-alt:solid #CCCCCC .75pt;padding:0cm 0cm 0cm =
6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=3DMsoNormal>I written =
this draft starting a RFC2119 update for the reasons of<br>discussion =
threads in [1] and [2]. Please check draft and feedback,<br>thanking =
you.<o:p></o:p></p></blockquote><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
agree with what Paul and Melinda have said. &nbsp;This document is =
pointless, as there is no actual problem that it's solving and no =
misunderstanding that it's clarifying. &nbsp;Further, it's actively =
*harmful*. &nbsp;It's arguable that 2119 already reserves too many words =
by giving them specific, normative meanings (SHALL *and* MUST; SHOULD =
*and* RECOMMENDED). &nbsp;Adding IF, THEN, and ELSE would not only be =
unnecessary, but downright *bad*.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Barry&nbsp;<o:p></o:p></p></div></div></div></body></ht=
ml>
------=_NextPart_000_0342_01CD700C.A53EB0C0--


From abdussalambaryun@gmail.com  Wed Aug  1 10:05:45 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A67E21F8810 for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 10:05:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.478
X-Spam-Level: 
X-Spam-Status: No, score=-3.478 tagged_above=-999 required=5 tests=[AWL=0.121,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ev003qzpKp-J for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 10:05:44 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3D12711E80E1 for <ietf@ietf.org>; Wed,  1 Aug 2012 10:05:44 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so7871577vbb.31 for <ietf@ietf.org>; Wed, 01 Aug 2012 10:05:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BjFMV9er+KtHjuMpjfrj2UIPFRdjB40Um+SDURIb0L8=; b=ztLyDsEi4TwMf2qiVID1s9UDdO+WcTEwOp8PEuWiC/kfvaukdcpheTJnBHcE0TPXYh YedvCc7f0BdJYpbDk/qiOYmC4MU0oK4CWBkjU1ehOSQXaHazsfmDLNeQrFhpyg4YeTF9 ZbpbAg99KUWGESlGl48UnTZZgyIG8t9iqdquL+Xz/5+uEcC60cA/3Rb/r3T3Re3xisjR qZHmVkiZCju6tVkhjE5rst9CUZYc/DiBIKgDA/KnXZwZKOF88/BFB2fp8nVigGsYlO0a 8M5RH79RrBJtiJZC9TXGgt1uAnN2BvwXuDLob8hd3RNOCDaWFmPalh2P2bzREaEW4iq3 f6sA==
MIME-Version: 1.0
Received: by 10.220.150.138 with SMTP id y10mr17427079vcv.73.1343840743664; Wed, 01 Aug 2012 10:05:43 -0700 (PDT)
Received: by 10.220.141.200 with HTTP; Wed, 1 Aug 2012 10:05:43 -0700 (PDT)
In-Reply-To: <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com>
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com> <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com>
Date: Wed, 1 Aug 2012 19:05:43 +0200
Message-ID: <CADnDZ8-6iTjav+utqDOXriKc3FUVesHAy0CD5FtFQjrWDMvuWA@mail.gmail.com>
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 17:05:45 -0000

> I agree with what Paul and Melinda have said.  This document is pointless,
> as there is no actual problem that it's solving and no misunderstanding
> that it's clarifying.

It is solving the problem of specifications that don't specify
conditions in a easy manner that implementers/users need. Please note
that "IF THEN" is reducing the number of words in the draft as well
(more efficient). Please tell me what specification can specify a
conditional situation in less words than "IF, THEN". Many RFC don't
follow the easy way properly,

> Further, it's actively *harmful*.

I implemented some RFC that don't specify "if, then", and it was
harmful for me. I don't know what kind of harmful that the update will
make, please explain by an example. Do you mean harmful to the
reviewers or to the draft authors. Please note that we should make the
internet a better place for ALL not only for authors.

> It's arguable
> that 2119 already reserves too many words by giving them specific,
> normative meanings (SHALL *and* MUST; SHOULD *and* RECOMMENDED).  Adding
> IF, THEN, and ELSE would not only be unnecessary, but downright *bad*.
>

It is necessary, and the words in RFC2119 are not many if we compare
with our RFCs pages.

I thank you for your comments,

AB

From melinda.shore@gmail.com  Wed Aug  1 10:11:27 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9313D11E81BB for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 10:11:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.799
X-Spam-Level: 
X-Spam-Status: No, score=-3.799 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8fxELNEdHtKw for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 10:11:27 -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 0B9C811E8176 for <ietf@ietf.org>; Wed,  1 Aug 2012 10:11:26 -0700 (PDT)
Received: by yhq56 with SMTP id 56so8154846yhq.31 for <ietf@ietf.org>; Wed, 01 Aug 2012 10:11:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=1mhzMa1vlUruXK81k6lEb2NsKrwYyVi6fT4nAZs+JpQ=; b=rVkmm1W+5pP+5gFxAQqp2sUwc63XxFJ7DUWbO7Q52dxkRadc2F+90NeU3o/VS+wSd7 KLjoMsOkT/uJFeeQ0enJXtY4O4jpbGjIJKZZ51oDZZfy2ASPwdlFfxyxwPj8o62fiyIo cpDbRcVuQdBbopw8ZoFCgHP4EiVQHPw98jIhOMvVldyWDe4kN62eYH7wfbaBAP0CIMcz ynaGwB3nG99SLqRwzEeAf2ElEwRQaBFkNB+ACkqQnpyt6THHpEf1J5qHzBnPGrwR3Z6X W8XMpPdVcXY6uD28QB6h0sqYJdzXQjjwNHBg0YsxA1Z1dSR1ahel4G88C3M1Mqlk01+r z+Ww==
Received: by 10.66.78.42 with SMTP id y10mr41321659paw.31.1343841086315; Wed, 01 Aug 2012 10:11:26 -0700 (PDT)
Received: from ?IPv6:2001:df8:0:16:2c86:4d38:4ced:b2b3? ([2001:df8:0:16:2c86:4d38:4ced:b2b3]) by mx.google.com with ESMTPS id gf3sm2929595pbc.74.2012.08.01.10.11.22 (version=SSLv3 cipher=OTHER); Wed, 01 Aug 2012 10:11:23 -0700 (PDT)
Message-ID: <50196374.40306@gmail.com>
Date: Wed, 01 Aug 2012 09:12:20 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com> <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com> <CADnDZ8-6iTjav+utqDOXriKc3FUVesHAy0CD5FtFQjrWDMvuWA@mail.gmail.com>
In-Reply-To: <CADnDZ8-6iTjav+utqDOXriKc3FUVesHAy0CD5FtFQjrWDMvuWA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 17:11:27 -0000

On 8/1/2012 9:05 AM, Abdussalam Baryun wrote:
> It is solving the problem of specifications that don't specify
> conditions in a easy manner that implementers/users need.

It's pretty clear that you'd like to be involved with the work
of the IETF in some way.  Allow me to suggest that a more productive
approach might be to identify a working group in your area of
expertise, review their documents, provide feedback on those
documents, and write text or new documents to address any gaps.
There is work to be done and there are problems to solve.  What
you are doing now is not helpful.

Melinda


From ynir@checkpoint.com  Wed Aug  1 10:15:31 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C52011E825E for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 10:15:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.3
X-Spam-Level: 
X-Spam-Status: No, score=-10.3 tagged_above=-999 required=5 tests=[AWL=0.298,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DbvQ-QLwbXfQ for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 10:15:30 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 6FA6111E8250 for <ietf@ietf.org>; Wed,  1 Aug 2012 10:15:29 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id q71HFLN3014123; Wed, 1 Aug 2012 20:15:22 +0300
X-CheckPoint: {5019619E-4-1B221DC2-4FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Wed, 1 Aug 2012 20:15:21 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Date: Wed, 1 Aug 2012 20:15:19 +0300
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
Thread-Topic: New Version Notification for: draft-baryun-rfc2119-update-00.txt
Thread-Index: Ac1wCTqNDI2IoTyuT9iBB4fG4VBZUg==
Message-ID: <D872E3E4-7DE6-4691-B76F-A70B4E5E1613@checkpoint.com>
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com> <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com> <034101cd7004$43758dd0$ca60a970$@olddog.co.uk>
In-Reply-To: <034101cd7004$43758dd0$ca60a970$@olddog.co.uk>
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: multipart/alternative; boundary="_000_D872E3E47DE64691B76FA70B4E5E1613checkpointcom_"
MIME-Version: 1.0
Cc: Barry Leiba <barryleiba@computer.org>, ietf <ietf@ietf.org>, Abdussalam Baryun <abdussalambaryun@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 17:15:31 -0000

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

He meant "PILLAR OF SALT"

On Aug 1, 2012, at 9:39 AM, Adrian Farrel wrote:

Barry,

Did you mean "bad" or "BAD"?

A

From: ietf-bounces@ietf.org<mailto:ietf-bounces@ietf.org> [mailto:ietf-boun=
ces@ietf.org] On Behalf Of Barry Leiba
Sent: 01 August 2012 17:04
To: Abdussalam Baryun
Cc: ietf
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.t=
xt

I written this draft starting a RFC2119 update for the reasons of
discussion threads in [1] and [2]. Please check draft and feedback,
thanking you.

I agree with what Paul and Melinda have said.  This document is pointless, =
as there is no actual problem that it's solving and no misunderstanding tha=
t it's clarifying.  Further, it's actively *harmful*.  It's arguable that 2=
119 already reserves too many words by giving them specific, normative mean=
ings (SHALL *and* MUST; SHOULD *and* RECOMMENDED).  Adding IF, THEN, and EL=
SE would not only be unnecessary, but downright *bad*.

Barry


Scanned by Check Point Total Security Gateway.



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

<html><head><base href=3D"x-msg://411/"></head><body style=3D"word-wrap: br=
eak-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">He meant "PILLAR OF SALT"<div><br><div><div>On Aug 1, 2012, at 9:39 AM, A=
drian Farrel wrote:</div><br class=3D"Apple-interchange-newline"><blockquot=
e type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Tahoma; font-style: normal; font-variant: normal; fo=
nt-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2;=
 text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-sp=
ace: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacin=
g: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-e=
ffect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px=
; font-size: medium; "><div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple"><=
div class=3D"WordSection1" style=3D"page: WordSection1; "><div style=3D"mar=
gin-top: 0cm; margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt;=
 font-size: 12pt; font-family: 'Times New Roman', serif; "><span style=3D"f=
ont-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
">Barry,<o:p></o:p></span></div><div style=3D"margin-top: 0cm; margin-right=
: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; font-size: 12pt; font-fam=
ily: 'Times New Roman', serif; "><span style=3D"font-size: 11pt; font-famil=
y: Calibri, sans-serif; color: rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span>=
</div><div style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; m=
argin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', se=
rif; "><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; co=
lor: rgb(31, 73, 125); ">Did you mean "bad" or "BAD"?<o:p></o:p></span></di=
v><div style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; margi=
n-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;=
 "><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color:=
 rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top=
: 0cm; margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; font-s=
ize: 12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-siz=
e: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">A<o:p=
></o:p></span></div><div style=3D"margin-top: 0cm; margin-right: 0cm; margi=
n-left: 0cm; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></div><div s=
tyle=3D"border-top-style: none; border-right-style: none; border-bottom-sty=
le: none; border-width: initial; border-color: initial; border-left-style: =
solid; border-left-color: blue; border-left-width: 1.5pt; padding-top: 0cm;=
 padding-right: 0cm; padding-bottom: 0cm; padding-left: 4pt; "><div><div st=
yle=3D"border-right-style: none; border-bottom-style: none; border-left-sty=
le: none; border-width: initial; border-color: initial; border-top-style: s=
olid; border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding-=
top: 3pt; padding-right: 0cm; padding-bottom: 0cm; padding-left: 0cm; "><di=
v style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; margin-bot=
tom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><b=
><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Tahoma, sans-s=
erif; ">From:</span></b><span lang=3D"EN-US" style=3D"font-size: 10pt; font=
-family: Tahoma, sans-serif; "><span class=3D"Apple-converted-space">&nbsp;=
</span><a href=3D"mailto:ietf-bounces@ietf.org" style=3D"color: blue; text-=
decoration: underline; ">ietf-bounces@ietf.org</a><span class=3D"Apple-conv=
erted-space">&nbsp;</span>[mailto:ietf-bounces@ietf.org]<span class=3D"Appl=
e-converted-space">&nbsp;</span><b>On Behalf Of<span class=3D"Apple-convert=
ed-space">&nbsp;</span></b>Barry Leiba<br><b>Sent:</b><span class=3D"Apple-=
converted-space">&nbsp;</span>01 August 2012 17:04<br><b>To:</b><span class=
=3D"Apple-converted-space">&nbsp;</span>Abdussalam Baryun<br><b>Cc:</b><spa=
n class=3D"Apple-converted-space">&nbsp;</span>ietf<br><b>Subject:</b><span=
 class=3D"Apple-converted-space">&nbsp;</span>Re: New Version Notification =
for: draft-baryun-rfc2119-update-00.txt<o:p></o:p></span></div></div></div>=
<div style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
><o:p>&nbsp;</o:p></div><blockquote style=3D"border-top-style: none; border=
-right-style: none; border-bottom-style: none; border-width: initial; borde=
r-color: initial; border-left-style: solid; border-left-color: rgb(204, 204=
, 204); border-left-width: 1pt; padding-top: 0cm; padding-right: 0cm; paddi=
ng-bottom: 0cm; padding-left: 6pt; margin-left: 4.8pt; margin-right: 0cm; "=
><div style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; margin=
-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
">I written this draft starting a RFC2119 update for the reasons of<br>disc=
ussion threads in [1] and [2]. Please check draft and feedback,<br>thanking=
 you.<o:p></o:p></div></blockquote><div><div style=3D"margin-top: 0cm; marg=
in-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><o:p>&nbsp;</o:p></div></div><div>=
<div style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>I agree with what Paul and Melinda have said. &nbsp;This document is point=
less, as there is no actual problem that it's solving and no misunderstandi=
ng that it's clarifying. &nbsp;Further, it's actively *harmful*. &nbsp;It's=
 arguable that 2119 already reserves too many words by giving them specific=
, normative meanings (SHALL *and* MUST; SHOULD *and* RECOMMENDED). &nbsp;Ad=
ding IF, THEN, and ELSE would not only be unnecessary, but downright *bad*.=
<o:p></o:p></div></div><div><div style=3D"margin-top: 0cm; margin-right: 0c=
m; margin-left: 0cm; margin-bottom: 0.0001pt; font-size: 12pt; font-family:=
 'Times New Roman', serif; "><o:p>&nbsp;</o:p></div></div><div><div style=
=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.=
0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">Barry&nbs=
p;<o:p></o:p></div></div></div></div><br><br>Scanned by Check Point Total S=
ecurity Gateway.<span class=3D"Apple-converted-space">&nbsp;</span><br><br>=
</div></span></blockquote></div><br></div></body></html>=

--_000_D872E3E47DE64691B76FA70B4E5E1613checkpointcom_--

From lars@netapp.com  Wed Aug  1 10:21:48 2012
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77A6211E831C for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 10:21:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.441
X-Spam-Level: 
X-Spam-Status: No, score=-10.441 tagged_above=-999 required=5 tests=[AWL=0.158, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T9eM97bxyd2V for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 10:21:47 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 6003811E831B for <ietf@ietf.org>; Wed,  1 Aug 2012 10:21:47 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.77,695,1336374000";  d="p7s'?scan'208";a="671535213"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 01 Aug 2012 10:21:47 -0700
Received: from vmwexceht01-prd.hq.netapp.com (vmwexceht01-prd.hq.netapp.com [10.106.76.239]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q71HLlf2016735; Wed, 1 Aug 2012 10:21:47 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.13]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.02.0298.004; Wed, 1 Aug 2012 10:21:46 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
Thread-Topic: New Version Notification for: draft-baryun-rfc2119-update-00.txt
Thread-Index: AQHNb7G+F2Pdt2PrS0GwGq2xcUHdtZdFlHqAgAAVtQA=
Date: Wed, 1 Aug 2012 17:21:45 +0000
Message-ID: <17DCE4C6-66DA-4E4A-8792-856E3B4A78A2@netapp.com>
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com> <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com>
In-Reply-To: <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.116]
Content-Type: multipart/signed; boundary="Apple-Mail=_EBD82A89-5DF6-4FE7-93DF-945C2F41A007"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: ietf <ietf@ietf.org>, Abdussalam Baryun <abdussalambaryun@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 17:21:48 -0000

--Apple-Mail=_EBD82A89-5DF6-4FE7-93DF-945C2F41A007
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=iso-8859-1

Agreed. I suggest we stop discussing this proposal.

On Aug 1, 2012, at 9:03, Barry Leiba <barryleiba@computer.org> wrote:

>> 
>> I written this draft starting a RFC2119 update for the reasons of
>> discussion threads in [1] and [2]. Please check draft and feedback,
>> thanking you.
>> 
> 
> I agree with what Paul and Melinda have said.  This document is pointless,
> as there is no actual problem that it's solving and no misunderstanding
> that it's clarifying.  Further, it's actively *harmful*.  It's arguable
> that 2119 already reserves too many words by giving them specific,
> normative meanings (SHALL *and* MUST; SHOULD *and* RECOMMENDED).  Adding
> IF, THEN, and ELSE would not only be unnecessary, but downright *bad*.
> 
> Barry


--Apple-Mail=_EBD82A89-5DF6-4FE7-93DF-945C2F41A007
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMQDCCBUow
ggQyoAMCAQICEFcfSRTG0jNknqb9LV9GuFkwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTEyMTAwMDAwMDBaFw0x
MjEyMDkyMzU5NTlaMIIBDTEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEeMBwGCSqGSIb3DQEJARYPbGFyc0BuZXRhcHAuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokrhJTcXt6J/VEpZOicLoguBlYTjXP9v
Ze4HuuhXnURUS8YouAfgaqA0zYbt5yd6fh4PBMdAaEWr5yJyHuFykXlrCumjUWSpLuqTS2A+pt4q
cZaAQk9iLDN/UVd3SpkUuvWbxXlqzG7/BSqa3VNObBzCmyh+V7aXxri+30CT//DSsNRC4VFy6sn6
dMgSaFenXLwe/FBwY0qTMfICT1PrrX6Sw1S8OfH9rykLlZXbmfkFExxQngp1DJH9xMHeODHGbCv/
ty5gdxMOrLe+vENxFEcy1YQWBZd1kNL4UObugF8A/jE/s+Oa3H1VFH8ghqZTdqGDysVxmtKHuNFx
6jIBSQIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgG
CCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNV
HSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDovL2luZGMx
ZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqG
SIb3DQEBBQUAA4IBAQBA7q6tR92qpd7xo7VBsrOfGCWzoxIVfTc7t0RhB/Oz/+c3lnhYnNScIuKN
JmyZvznmVxqB9BJ72+NkvmdB/hnILSBTRawL2tyLo9PkBtN0nRt4gS6wjpWnD8G83hlJLE7r25jk
7HkRev61dTIXsANFpJKF02C4XSoDfEzNV6MpuEvHvcgHCqMrlwWwfKc7+NoDnE8PBuRzwSXvlD5L
mswCY2iiOsd7ImNO4OzTCxETvKTDu92+FTIbRJJpYjVNv1UF7e3w9Kq65BkZJErUH19beUeQl0Wh
2BJQE6/15rQyCnP0iJ/Nmx2/kI6M0PWunEsI6FMs0MbosreaWGHlQmomMIIG7jCCBdagAwIBAgIQ
cRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQL
EzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYD
VQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y
aXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAo
YykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBD
bGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6ZvgSU6Lb9UB
0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHsEnMhjfXc
MM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO4YM/d/mZ
//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSyriMGZSal
J1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYI
KwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0T
AQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVy
aXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9w
Y2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1h
Z2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28u
dmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRl
TGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHp
MIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWduLCBJ
bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENsYXNzIDEg
UHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+v
OEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlMJBq6WaSH
O3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKvYLMVirOV
nDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDRyxTWcVib
vtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy+kgOZY5J
yNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/wYIxggSL
MIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDgwMTE3MjE0MFowIwYJKoZIhvcNAQkEMRYEFMKH
6VFQ8NkKbkJDQaeZtkMUBCt+MIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBADCkwrTC
jJbr7a/ejfGCFokh5WmKHt5ffpsLx2al//h/6whH3m3uNXZ+SrlaneKZ0RXlOoMGM5ALcPF2gPrC
Ca/ssLXZvKkrTf19C2db3a4M4UkXUnBrZvVNQNci1f+ZXnRudQUOqYJyXcDEKAj9wf7y1v5e/RfR
KSzaBZSA0HZybY0CDT6HMZlsmVS+HTIupoqpHfEZl7ldQEby8FdSpo7xGPSHgMByjekokrZJEfDh
vBf+SrIbXDvsP3i3xSoUs8TWGEgC2vuy2DdW79HUBjFOoZ1GwRhf+nmEUUG/g7BZGDRgEZypxmRC
PBu70JalsypSAUiszkFeJ7OQCwrtUToAAAAAAAA=

--Apple-Mail=_EBD82A89-5DF6-4FE7-93DF-945C2F41A007--

From adrian@olddog.co.uk  Wed Aug  1 10:23:06 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AADFB11E836B for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 10:23:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.58
X-Spam-Level: 
X-Spam-Status: No, score=-2.58 tagged_above=-999 required=5 tests=[AWL=0.018,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p6B0m+RCyXM1 for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 10:23:05 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 0574A11E8169 for <ietf@ietf.org>; Wed,  1 Aug 2012 10:23:04 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q71HMrZh011252;  Wed, 1 Aug 2012 18:22:53 +0100
Received: from 950129200 (dhcp-11f1.meeting.ietf.org [130.129.17.241]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q71HMj3t011196 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 1 Aug 2012 18:22:49 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Yoav Nir'" <ynir@checkpoint.com>
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com> <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com> <034101cd7004$43758dd0$ca60a970$@olddog.co.uk> <D872E3E4-7DE6-4691-B76F-A70B4E5E1613@checkpoint.com>
In-Reply-To: <D872E3E4-7DE6-4691-B76F-A70B4E5E1613@checkpoint.com>
Subject: RE: New Version Notification for: draft-baryun-rfc2119-update-00.txt
Date: Wed, 1 Aug 2012 18:22:44 +0100
Message-ID: <039801cd700a$46cc2420$d4646c60$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0399_01CD7012.A8954710"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLw+3MjyVCsgx/3v7ilGpHvBIxheAJ4IDYAAS9o544CPzf9nZTO523w
Content-Language: en-gb
Cc: 'Barry Leiba' <barryleiba@computer.org>, 'ietf' <ietf@ietf.org>, 'Abdussalam Baryun' <abdussalambaryun@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 17:23:06 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0399_01CD7012.A8954710
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Thanks Yoav,
 
I don't get a lot of citations for that one :-)
 
From: Yoav Nir [mailto:ynir@checkpoint.com] 
Sent: 01 August 2012 18:15
To: adrian@olddog.co.uk
Cc: Barry Leiba; Abdussalam Baryun; ietf
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
 
He meant "PILLAR OF SALT"
 
On Aug 1, 2012, at 9:39 AM, Adrian Farrel wrote:



Barry,
 
Did you mean "bad" or "BAD"?
 
A
 
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Barry
Leiba
Sent: 01 August 2012 17:04
To: Abdussalam Baryun
Cc: ietf
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
 
I written this draft starting a RFC2119 update for the reasons of
discussion threads in [1] and [2]. Please check draft and feedback,
thanking you.
 
I agree with what Paul and Melinda have said.  This document is pointless, as
there is no actual problem that it's solving and no misunderstanding that it's
clarifying.  Further, it's actively *harmful*.  It's arguable that 2119 already
reserves too many words by giving them specific, normative meanings (SHALL *and*
MUST; SHOULD *and* RECOMMENDED).  Adding IF, THEN, and ELSE would not only be
unnecessary, but downright *bad*.
 
Barry 


Scanned by Check Point Total Security Gateway. 
 

------=_NextPart_000_0399_01CD7012.A8954710
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DProgId content=3DWord.Document><meta =
name=3DGenerator content=3D"Microsoft Word 14"><meta name=3DOriginator =
content=3D"Microsoft Word 14"><base href=3D"x-msg://411/"><link =
rel=3DFile-List href=3D"cid:filelist.xml@01CD7012.9E2B4310"><!--[if gte =
mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:EnvelopeVis/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-GB</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:DoNotExpandShiftReturn/>
<w:BreakWrappedTables/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520092929 1073786111 9 0 415 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520081665 -1073717157 41 0 66047 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	mso-fareast-font-family:Calibri;}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
span.apple-style-span
	{mso-style-name:apple-style-span;
	mso-style-unhide:no;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;
	mso-style-unhide:no;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-size:10.0pt;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue =
vlink=3Dpurple style=3D'tab-interval:36.0pt'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Thanks =
Yoav,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>I don't get a lot of citations =
for that one :-)<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New =
Roman";mso-ansi-language:EN-US'>From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New Roman";mso-ansi-language:EN-US'> Yoav Nir =
[mailto:ynir@checkpoint.com] <br><b>Sent:</b> 01 August 2012 =
18:15<br><b>To:</b> adrian@olddog.co.uk<br><b>Cc:</b> Barry Leiba; =
Abdussalam Baryun; ietf<br><b>Subject:</b> Re: New Version Notification =
for: =
draft-baryun-rfc2119-update-00.txt<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'mso-fareast-font-family:"Times New Roman"'>He meant =
&quot;PILLAR OF SALT&quot;<o:p></o:p></span></p><div><p =
class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></p><div><div><p class=3DMsoNormal><span =
style=3D'mso-fareast-font-family:"Times New Roman"'>On Aug 1, 2012, at =
9:39 AM, Adrian Farrel wrote:<o:p></o:p></span></p></div><p =
class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman"'><br style=3D'mso-special-character:line-break'><![if =
!supportLineBreakNewLine]><br =
style=3D'mso-special-character:line-break'><![endif]><o:p></o:p></span></=
p><div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:"Times New Roman";color:#1F497D'>Barry,</span><span =
style=3D'mso-fareast-font-family:"Times New =
Roman"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:"Times New Roman";color:#1F497D'>&nbsp;</span><span =
style=3D'mso-fareast-font-family:"Times New =
Roman"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:"Times New Roman";color:#1F497D'>Did you mean =
&quot;bad&quot; or &quot;BAD&quot;?</span><span =
style=3D'mso-fareast-font-family:"Times New =
Roman"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:"Times New Roman";color:#1F497D'>&nbsp;</span><span =
style=3D'mso-fareast-font-family:"Times New =
Roman"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:"Times New Roman";color:#1F497D'>A</span><span =
style=3D'mso-fareast-font-family:"Times New =
Roman"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:"Times New Roman";color:#1F497D'>&nbsp;</span><span =
style=3D'mso-fareast-font-family:"Times New =
Roman"'><o:p></o:p></span></p></div><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt;border-width:initial;border-color:initial'><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm;border-width:initial;border-color:initial'><div><p =
class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New =
Roman";mso-ansi-language:EN-US'>From:</span></b><span =
class=3Dapple-converted-space><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New =
Roman";mso-ansi-language:EN-US'>&nbsp;</span></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New Roman";mso-ansi-language:EN-US'><a =
href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a><span =
class=3Dapple-converted-space>&nbsp;</span>[mailto:ietf-bounces@ietf.org]=
<span class=3Dapple-converted-space>&nbsp;</span><b>On Behalf Of<span =
class=3Dapple-converted-space>&nbsp;</span></b>Barry =
Leiba<br><b>Sent:</b><span class=3Dapple-converted-space>&nbsp;</span>01 =
August 2012 17:04<br><b>To:</b><span =
class=3Dapple-converted-space>&nbsp;</span>Abdussalam =
Baryun<br><b>Cc:</b><span =
class=3Dapple-converted-space>&nbsp;</span>ietf<br><b>Subject:</b><span =
class=3Dapple-converted-space>&nbsp;</span>Re: New Version Notification =
for: draft-baryun-rfc2119-update-00.txt</span><span =
style=3D'mso-fareast-font-family:"Times New =
Roman"'><o:p></o:p></span></p></div></div></div><div><p =
class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman"'>&nbsp;<o:p></o:p></span></p></div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm =
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5=
.0pt;border-width:initial;border-color:initial'><div><p =
class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman"'>I written this draft starting a RFC2119 update for the reasons =
of<br>discussion threads in [1] and [2]. Please check draft and =
feedback,<br>thanking =
you.<o:p></o:p></span></p></div></blockquote><div><div><p =
class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman"'>&nbsp;<o:p></o:p></span></p></div></div><div><div><p =
class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman"'>I agree with what Paul and Melinda have said. &nbsp;This =
document is pointless, as there is no actual problem that it's solving =
and no misunderstanding that it's clarifying. &nbsp;Further, it's =
actively *harmful*. &nbsp;It's arguable that 2119 already reserves too =
many words by giving them specific, normative meanings (SHALL *and* =
MUST; SHOULD *and* RECOMMENDED). &nbsp;Adding IF, THEN, and ELSE would =
not only be unnecessary, but downright =
*bad*.<o:p></o:p></span></p></div></div><div><div><p =
class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman"'>&nbsp;<o:p></o:p></span></p></div></div><div><div><p =
class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman"'>Barry&nbsp;<o:p></o:p></span></p></div></div></div><p =
class=3DMsoNormal style=3D'margin-bottom:13.5pt'><span =
style=3D'font-size:13.5pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New Roman"'><br><br>Scanned by Check Point Total =
Security Gateway.<span =
class=3Dapple-converted-space>&nbsp;</span><o:p></o:p></span></p></div></=
div><p class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times =
New Roman"'><o:p>&nbsp;</o:p></span></p></div></div></div></body></html>
------=_NextPart_000_0399_01CD7012.A8954710--


From jmpolk@cisco.com  Wed Aug  1 10:33:27 2012
Return-Path: <jmpolk@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C424611E8297 for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 10:33:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.506
X-Spam-Level: 
X-Spam-Status: No, score=-110.506 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id khXb8d2jyAYG for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 10:33:27 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id DF07F11E8295 for <ietf@ietf.org>; Wed,  1 Aug 2012 10:33:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=1778; q=dns/txt; s=iport; t=1343842407; x=1345052007; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=F7ORSH/KPipRBgtKqMQ3AsUa5aL8vDafslDAzSb5RH4=; b=Cs72f2IRK2OIDdSAebKb4sB+xjF9M8s/gA/mBvrLXCPgKooxn0b0xOq7 yQGUlOv8NQZYNilzaLIRYk0rmLm2J18tDUnHyJfCOqdsstKq8z3Yu08In PeXm7Fd1IcFXm8/Mi5om3N7MTXhxa43anHo2/ECKrG0Vko5bJaGmsJcgm U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAA1oGVCrRDoJ/2dsb2JhbABFuRCBB4IgAQEBBBIBJQI9AhAHBBgeEBk+BgEoDIdqnHCgT4tJhwkDiE2bIYFmgn0
X-IronPort-AV: E=Sophos;i="4.77,695,1336348800"; d="scan'208";a="51212149"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 01 Aug 2012 17:33:26 +0000
Received: from jmpolk-WS.cisco.com ([10.21.169.169]) (authenticated bits=0) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q71HXPXG021973 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Aug 2012 17:33:26 GMT
Message-Id: <201208011733.q71HXPXG021973@mtv-core-4.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 01 Aug 2012 12:33:25 -0500
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, Barry Leiba <barryleiba@computer.org>
From: James Polk <jmpolk@cisco.com>
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
In-Reply-To: <CADnDZ8-6iTjav+utqDOXriKc3FUVesHAy0CD5FtFQjrWDMvuWA@mail.g mail.com>
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com> <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com> <CADnDZ8-6iTjav+utqDOXriKc3FUVesHAy0CD5FtFQjrWDMvuWA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 17:33:27 -0000

At 12:05 PM 8/1/2012, Abdussalam Baryun wrote:
> > I agree with what Paul and Melinda have said.  This document is pointless,
> > as there is no actual problem that it's solving and no misunderstanding
> > that it's clarifying.
>
>It is solving the problem of specifications that don't specify
>conditions in a easy manner that implementers/users need.

normative language is for implementers, not education for users - at 
least as its primary goal. Implementations can be configured to 
comply and not comply with one or more RFCs, based on the needs of 
the customer and the desire of the implementer (i.e., vendor) to want 
the sale of their equipment to that customer. This fact is commonly 
misunderstood. Melinda has wise words

>Please note
>that "IF THEN" is reducing the number of words in the draft as well
>(more efficient). Please tell me what specification can specify a
>conditional situation in less words than "IF, THEN". Many RFC don't
>follow the easy way properly,
>
> > Further, it's actively *harmful*.
>
>I implemented some RFC that don't specify "if, then", and it was
>harmful for me. I don't know what kind of harmful that the update will
>make, please explain by an example. Do you mean harmful to the
>reviewers or to the draft authors. Please note that we should make the
>internet a better place for ALL not only for authors.
>
> > It's arguable
> > that 2119 already reserves too many words by giving them specific,
> > normative meanings (SHALL *and* MUST; SHOULD *and* RECOMMENDED).  Adding
> > IF, THEN, and ELSE would not only be unnecessary, but downright *bad*.
> >
>
>It is necessary, and the words in RFC2119 are not many if we compare
>with our RFCs pages.
>
>I thank you for your comments,
>
>AB


From abdussalambaryun@gmail.com  Wed Aug  1 10:44:23 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E66A811E82C5 for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 10:44:22 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C9p+5qsSwLmJ for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 10:44:21 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3DAAA11E82FE for <ietf@ietf.org>; Wed,  1 Aug 2012 10:44:21 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so7846852vcb.31 for <ietf@ietf.org>; Wed, 01 Aug 2012 10:44:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0tJC40uuVpcT8L6BOQ4nMvCplH+GOkGvT9frQekxing=; b=VHzMbfjd7EBjTGQfEdBUWZF8xMGIhpd8J8paEHz/JBQIxcYnV2IMUTUxxcRYjYPUzz P2PsDU9X+iukBFre879xlszBCCqphOo5GzOkBCAffzE6G0wc5QbE3eXPp75NSUu0Uwfn n2K0ANAF+UAqNRKcpQHOEAk/lR1Tj+Fy9mQ0Tan7k8r3PzFQiN19LTeakqrfLumo5rg4 qubizBMfoe+dXDlBXfrS4TomJYwg54nryvr9mY1ZjD5LHtdp8eCDvf755+dfguuVXMwX QnptCdRBObsiPp6yRUVBUQRMSY5WdxrOlKfBoHbdGvU486EJnyFO6Fkv6sNtSI/6Jakj ieeA==
MIME-Version: 1.0
Received: by 10.220.150.138 with SMTP id y10mr17524207vcv.73.1343843050331; Wed, 01 Aug 2012 10:44:10 -0700 (PDT)
Received: by 10.220.141.200 with HTTP; Wed, 1 Aug 2012 10:44:10 -0700 (PDT)
In-Reply-To: <201208011733.q71HXPXG021973@mtv-core-4.cisco.com>
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com> <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com> <CADnDZ8-6iTjav+utqDOXriKc3FUVesHAy0CD5FtFQjrWDMvuWA@mail.gmail.com> <201208011733.q71HXPXG021973@mtv-core-4.cisco.com>
Date: Wed, 1 Aug 2012 19:44:10 +0200
Message-ID: <CADnDZ89hp9FNoPyx2ms-4+aURLM=_Mk6whoC5NLTm06D_wHJCA@mail.gmail.com>
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: melinda.shore@gmail.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 17:44:23 -0000

Hi Melinda,

I am already involved, and volunteering work, I done many reviews and
comments in two WGs, and will hopfuly continue if people are
welcoming. However, I thank you for your comments,

AB
======
The mission of the Internet Engineering Task Force is to make the
Internet work better by producing high-quality and relevant technical
documents that influence the way people design, use, and manage the
Internet
-----------------------------------------------------------------------------------------------------------

It's pretty clear that you'd like to be involved with the work
of the IETF in some way.  Allow me to suggest that a more productive
approach might be to identify a working group in your area of
expertise, review their documents, provide feedback on those
documents, and write text or new documents to address any gaps.
There is work to be done and there are problems to solve.  What
you are doing now is not helpful.

Melinda

From scott.brim@gmail.com  Wed Aug  1 10:48:32 2012
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 1463F11E835C for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 10:48:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.588
X-Spam-Level: 
X-Spam-Status: No, score=-103.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VXe9TwxPKdwb for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 10:48:31 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7C8AC11E8370 for <ietf@ietf.org>; Wed,  1 Aug 2012 10:48:31 -0700 (PDT)
Received: by pbbjt11 with SMTP id jt11so1461051pbb.31 for <ietf@ietf.org>; Wed, 01 Aug 2012 10:48:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=KDm73dkEGsBeTQKD9P1h3rVKhULFF4aLs/spCFEaYSw=; b=HifGEZU23xqipUwKGuZn+VLqc51CgJNbp4ACSHF8YinefTTbjJtkKUiyvJQuFjq003 pi8FzSivzhEfJQonLyt43xzLSW32dEkbkUbNuJXwpWOx/vj/Weoj2Ga6i3e83RetryS+ UmganO0arzli4BRiFP0cWjyDEx+RzruSZWPDLE+/XHmOmiabqnEKXKmK+m8OXxxdzW5A VqKJgJCq5NEOa3POg561xBs7A2x4abAGrjl9vtiL4L2N6pn1oPFPcgn7OAn9y3chxYkq emxM0BCTXblK4zhKx50aGrIqCkmojABI4N894pBuTpYSzeDRgN0yVfNMtjMU+GAa/HxV hqNw==
Received: by 10.68.233.103 with SMTP id tv7mr54394262pbc.124.1343843311097; Wed, 01 Aug 2012 10:48:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.48.231 with HTTP; Wed, 1 Aug 2012 10:48:10 -0700 (PDT)
In-Reply-To: <CADnDZ8-6iTjav+utqDOXriKc3FUVesHAy0CD5FtFQjrWDMvuWA@mail.gmail.com>
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com> <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com> <CADnDZ8-6iTjav+utqDOXriKc3FUVesHAy0CD5FtFQjrWDMvuWA@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Wed, 1 Aug 2012 10:48:10 -0700
Message-ID: <CAPv4CP-LBGVPn9O5N1HmbUqw8H7dpK66q7JEcrYA_Sd395giCA@mail.gmail.com>
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Barry Leiba <barryleiba@computer.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 17:48:32 -0000

On Wed, Aug 1, 2012 at 10:05 AM, Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:
> It is solving the problem of specifications that don't specify
> conditions in a easy manner that implementers/users need. Please note
> that "IF THEN" is reducing the number of words in the draft as well
> (more efficient). Please tell me what specification can specify a
> conditional situation in less words than "IF, THEN". Many RFC don't
> follow the easy way properly,

Yes but that's an editing issue.  Go look at how process documentation
and state machines are handled in serious protocol RFCs.  Some do use
if/then in a formal way, but some are just informative.  The purpose
of 2119 is clarity of terminology.  Everyone knows what "if" and
"then" mean - your concern is how they are used.  The way to fix that
is in the particular drafts you have an issue with.

From sob@sobco.com  Tue Jul 31 13:03:48 2012
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8828C21F8883 for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 13:03:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.346
X-Spam-Level: 
X-Spam-Status: No, score=-0.346 tagged_above=-999 required=5 tests=[AWL=0.149,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NrE+J9FysvFy for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 13:03:47 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 8988D21F887E for <ietf@ietf.org>; Tue, 31 Jul 2012 13:03:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 301853572464; Tue, 31 Jul 2012 16:03:46 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WRGYKwtCXMDE; Tue, 31 Jul 2012 16:03:43 -0400 (EDT)
Received: from [136.248.127.173] (unknown [136.248.127.173]) by sobco.sobco.com (Postfix) with ESMTPSA id 7930A357243A; Tue, 31 Jul 2012 16:03:42 -0400 (EDT)
Subject: Re: I-D Action:	draft-balaji-mpls-lawful-intercept-thru-label-dis-00.txt
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Scott O Bradner <sob@sobco.com>
In-Reply-To: <m2ipd5w3um.wl%randy@psg.com>
Date: Tue, 31 Jul 2012 16:01:02 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <50B0354C-D870-483B-AC16-87E0B6B11CE7@sobco.com>
References: <20120730082620.18701.51607.idtracker@ietfa.amsl.com> <50164E21.2040904@gmail.com> <225158E4-78BC-42BC-8339-EB9E0DE75AA7@sobco.com> <m2ipd5w3um.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1278)
X-Mailman-Approved-At: Wed, 01 Aug 2012 11:07:26 -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: Tue, 31 Jul 2012 20:03:48 -0000

:-)

its a label not a process (in this case)

i.e., according to 2804 the label on the rfc should not be standards =
track

Scott

On Jul 30, 2012, at 1:33 PM, Randy Bush wrote:

>> 2804 does not say not to talk about such things - or that such =
documents should
>> not be published as RFCs  - 2804 says that the IETF will not do =
standards work
>> in this area
>=20
> for those of us who are easily confused, could you differentiate =
between
> working on douments and publishing them as rfcs from doing standards
> work?
>=20
> randy


From abdussalambaryun@gmail.com  Wed Aug  1 11:20:02 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F93021F8821 for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 11:20:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.481
X-Spam-Level: 
X-Spam-Status: No, score=-3.481 tagged_above=-999 required=5 tests=[AWL=0.118,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tm4ATGWbH784 for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 11:20:00 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 737D211E82CA for <ietf@ietf.org>; Wed,  1 Aug 2012 11:19:59 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so7955931vbb.31 for <ietf@ietf.org>; Wed, 01 Aug 2012 11:19:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WsM+kkhpOQMc/AmwnSo8StF8PZkZGrpdN7Ejo8Xn/wM=; b=j8AfD2ibbKIblH+s385txSfeTaKNOiuoOqa8xmQm95dOltGQw7vG4zM90cOZiK5/GE 5OuN3FjLlWZLNV9cnO4EvtdAK3BheMNcpEktbwe7FaOhf5LaAnA53mQqEHImaRZnKYAy NEB5rZSiP98+DWfpTs0FMl9K3+WNb+qUK9q5lEfxvQhIsXAylEbm7gBAuaXDv7KHZvY5 u+baKxrCy1kUXRZcf+LNiruL8JXxe7N1MsALI3LMeYZj5gANc/A+qqluANy0ExhZnoG2 tQaSveI/arzE03Yum6Ih/KMJQE8lLbsA19cDMI2E40nWcDH7yByqwTiHE3wdHQEhJQ5X 6O3g==
MIME-Version: 1.0
Received: by 10.52.94.36 with SMTP id cz4mr15799915vdb.10.1343845190581; Wed, 01 Aug 2012 11:19:50 -0700 (PDT)
Received: by 10.220.141.200 with HTTP; Wed, 1 Aug 2012 11:19:50 -0700 (PDT)
In-Reply-To: <CAPv4CP-LBGVPn9O5N1HmbUqw8H7dpK66q7JEcrYA_Sd395giCA@mail.gmail.com>
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com> <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com> <CADnDZ8-6iTjav+utqDOXriKc3FUVesHAy0CD5FtFQjrWDMvuWA@mail.gmail.com> <CAPv4CP-LBGVPn9O5N1HmbUqw8H7dpK66q7JEcrYA_Sd395giCA@mail.gmail.com>
Date: Wed, 1 Aug 2012 20:19:50 +0200
Message-ID: <CADnDZ892BCo7Vb87eTKGNmpHGxQi5RK6khT8curBL8iFkUjqcw@mail.gmail.com>
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Scott Brim <scott.brim@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Barry Leiba <barryleiba@computer.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 18:20:03 -0000

> Yes but that's an editing issue.  Go look at how process documentation
> and state machines are handled in serious protocol RFCs.  Some do use
> if/then in a formal way, but some are just informative.  The purpose
> of 2119 is clarity of terminology.

That is good when they use, I seen thoes, but how can we use
terminology so that don't collide, some people use 2119 terms that are
not condition, to describe conditions.

>  Everyone knows what "if" and
> "then" mean - your concern is how they are used.

Yes my concern is how/when use terms not meaning of terms. Ok,  What
about "MUST" (every one know it), wasn't it clear as "if then", please
explain why capital?

> The way to fix that
> is in the particular drafts you have an issue with.
>

 I did put that in one draft already as you say and one participant
before suggest. but I am thinking for the future works and to make the
authors document the specification they implemented more efficiently
without using 2119 terms in conditional and

I thank you for your comments, your email will be more concsidered,

AB

From sm@resistor.net  Wed Aug  1 13:23:24 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB52B11E8235 for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 13:23:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N5qCNHYtIPNQ for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 13:23: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 DA72B11E820D for <ietf@ietf.org>; Wed,  1 Aug 2012 13:23:20 -0700 (PDT)
Received: from sm-THINK.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q71KN93I001882; Wed, 1 Aug 2012 13:23:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1343852597; bh=43L2W7PlvjQb+tGtS/SSsiYM6ffw5hgwzcMmDIi6WGY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=WM/+4rxPUyczoUN8kOAdnIeSVw80FBrZAq//NNGMniMMZ37BVOQGdbfBFAU2M9Z+m BdZ7fmi8Wds3HmcvMWme4v1DqmMmdDbwBmpJpnca9XisRPdLXmezmYLeP7WEUyWsO6 aG1CrLx+IDQadHiKc7V5a/2MBaW/UZpLT7dMpZYY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1343852597; i=@resistor.net; bh=43L2W7PlvjQb+tGtS/SSsiYM6ffw5hgwzcMmDIi6WGY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=zTzF7q12rdej7wKcvV00zt6XE8mnJ1Oc8oLuuI9LFm0h3ZkDFwrMYa+IJ7WExrzGG Sgl/fLFjqRoFnaH/voZANK/qwJmmm0SQcDMER6CSQ8zzQ5XfMZabJF3/F0wWN0ORyG akV2/T32LFaOWa6xoPtuRfxs5hVfXX4Vc54Ws2ZI=
Message-Id: <6.2.5.6.2.20120801125000.04c23488@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 01 Aug 2012 13:21:38 -0700
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
In-Reply-To: <CADnDZ892BCo7Vb87eTKGNmpHGxQi5RK6khT8curBL8iFkUjqcw@mail.g mail.com>
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com> <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com> <CADnDZ8-6iTjav+utqDOXriKc3FUVesHAy0CD5FtFQjrWDMvuWA@mail.gmail.com> <CAPv4CP-LBGVPn9O5N1HmbUqw8H7dpK66q7JEcrYA_Sd395giCA@mail.gmail.com> <CADnDZ892BCo7Vb87eTKGNmpHGxQi5RK6khT8curBL8iFkUjqcw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 20:23:25 -0000

At 11:19 AM 8/1/2012, Abdussalam Baryun wrote:
>Yes my concern is how/when use terms not meaning of terms. Ok,  What
>about "MUST" (every one know it), wasn't it clear as "if then", please
>explain why capital?

You are probably receiving feedback on your draft because the WG 
sessions this week are boring. :-)  The is a thread about "all caps" 
at http://www.ietf.org/mail-archive/web/ietf/current/msg73338.html  I 
suggest reading RFC 1122 and RFC 1123 to get a view of how some 
specifications were written and why they were written in such a way.

Melinda Shore provided some good advice ( 
http://www.ietf.org/mail-archive/web/ietf/current/msg74191.html ).  I 
would not say that your draft is not helpful.  It is up to you to 
assess whether draft-baryun-rfc2119-update-00 can gain IETF Consensus.

Regards,
-sm  


From weiler@watson.org  Wed Aug  1 15:59:32 2012
Return-Path: <weiler@watson.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 9202511E817E for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 15:59:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level: 
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u0ayTOrdqJTP for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 15:59:31 -0700 (PDT)
Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by ietfa.amsl.com (Postfix) with ESMTP id 71B1911E8179 for <ietf@ietf.org>; Wed,  1 Aug 2012 15:59:31 -0700 (PDT)
Received: from fledge.watson.org (localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.14.5/8.14.5) with ESMTP id q71MxU00095325 for <ietf@ietf.org>; Wed, 1 Aug 2012 18:59:30 -0400 (EDT) (envelope-from weiler@watson.org)
Received: from localhost (weiler@localhost) by fledge.watson.org (8.14.5/8.14.5/Submit) with ESMTP id q71MxUh7095322 for <ietf@ietf.org>; Wed, 1 Aug 2012 18:59:30 -0400 (EDT) (envelope-from weiler@watson.org)
X-Authentication-Warning: fledge.watson.org: weiler owned process doing -bs
Date: Wed, 1 Aug 2012 18:59:30 -0400 (EDT)
From: Samuel Weiler <weiler@watson.org>
To: ietf@ietf.org
Subject: Re: NomCom 2012-2013: Third Call for Volunteers
In-Reply-To: <20120731044425.12307.52108.idtracker@ietfa.amsl.com>
Message-ID: <alpine.BSF.2.00.1208011848500.88006@fledge.watson.org>
References: <20120731044425.12307.52108.idtracker@ietfa.amsl.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (fledge.watson.org [127.0.0.1]); Wed, 01 Aug 2012 18:59:30 -0400 (EDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 22:59:33 -0000

On Mon, 30 Jul 2012, NomCom Chair wrote:

> I am pleased to report at this time we have 98 qualified individuals 
> who have generously volunteer their time to serve on this year's 
> NomCom.

Sorting that list by affiliation and counting the number of names from 
each affiliation, the volunteer list as of Monday included:

16 Huawai
15 Cisco
13 Ericsson
9 Juniper
5 ZTE
4 Nokia/Siemens (debatable; see details)
3 Alcatel-Lucent
3 BBN
3 China Mobile
3 CNNIC
2 Time Warner Cable
1 (22)
Total: 98

Observations: the top four companies on this list have contributed 
more than half of the NomCom volunteers.  The top three have 
contributed twice as many (44) as all of the entities that 
contributed only one (22).

Opinion: the NomCom would benefit from having many "independent" 
members.  While that could happen (yay, randomness), the odds here 
don't look great.

-- Sam


Footnote: I wasn't entirely sure which of the Nokia and Seimens 
entries (below) to combine.  I erred on the side of combining all of 
them, knowing that there's likely a strong argument to be made for 
some other treatment.  In any case, I don't think it will make much of 
a difference to the analysis.
Teemu Savolainen, Nokia
Jouni Korhonen, Nokia Siemens Networks
Mehmet Ersue, Nokia Siemens Networks
Andrew Hutton, Siemens Enterprise Communications


From d3e3e3@gmail.com  Wed Aug  1 16:07:25 2012
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7D0A11E81D0 for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 16:07:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.519
X-Spam-Level: 
X-Spam-Status: No, score=-103.519 tagged_above=-999 required=5 tests=[AWL=0.080, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id it13b2Y1GPgG for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 16:07:25 -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 0CFDC11E8159 for <ietf@ietf.org>; Wed,  1 Aug 2012 16:07:24 -0700 (PDT)
Received: by yhq56 with SMTP id 56so8553336yhq.31 for <ietf@ietf.org>; Wed, 01 Aug 2012 16:07:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=jEjXPW8a4zt0lLs8zU9FTqzoiPY3s0e3BbYVV9OnvIk=; b=pMZg2lsmMcse7JhkpHcQSlhfXUlHWP61mIx5ajolDZ5UbsIXnaoojGRJ8Tj+06NzOy Ced/OQgo7ecgHWg4yGwM8VnHuARdpCtLLUF4RgYrvusUnmWW5/48ttgNpzYajXkv4IYK 0KZufGMdtR8+tGcOKZyBHp7sKOYeFoIK9UJdh0DQJLin7JLN6IDV4Rh2noubGI5LRkwH c58MPgj5QUPqJvCfW+a7+NfCLECRuE0FlcH04vp2RH38RXD3g+hZWbSz7BRChgEJ6UFk 2nDcU7kbdfunAolnp9riYIOU4iCm/EihrVUptsS8CDCrRx1IjGUj5s5TbBJA952Fap58 5zPA==
Received: by 10.50.196.232 with SMTP id ip8mr6919860igc.50.1343862444424; Wed, 01 Aug 2012 16:07:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.70.227 with HTTP; Wed, 1 Aug 2012 16:07:03 -0700 (PDT)
In-Reply-To: <alpine.BSF.2.00.1208011848500.88006@fledge.watson.org>
References: <20120731044425.12307.52108.idtracker@ietfa.amsl.com> <alpine.BSF.2.00.1208011848500.88006@fledge.watson.org>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 1 Aug 2012 19:07:03 -0400
Message-ID: <CAF4+nEE_y0YZ6H4AyM-CwvDBfDJ3P+x68zfZ6EEofXh7efDGTA@mail.gmail.com>
Subject: Re: NomCom 2012-2013: Third Call for Volunteers
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 23:07:25 -0000

(1) Your figures show that it is more likely that a noncom member will
be selected from an affiliation listed by only one volunteer then that
they are to be selected from any specific affiliation listed by more
than one volunteer.

(2) Because of appearances of biased voting membership in some early
noncoms, the rules were changes to prohibit more than two voting
members with the same affiliation.

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

On Wed, Aug 1, 2012 at 6:59 PM, Samuel Weiler <weiler@watson.org> wrote:
> On Mon, 30 Jul 2012, NomCom Chair wrote:
>
>> I am pleased to report at this time we have 98 qualified individuals who
>> have generously volunteer their time to serve on this year's NomCom.
>
> Sorting that list by affiliation and counting the number of names from each
> affiliation, the volunteer list as of Monday included:
>
> 16 Huawai
> 15 Cisco
> 13 Ericsson
> 9 Juniper
> 5 ZTE
> 4 Nokia/Siemens (debatable; see details)
> 3 Alcatel-Lucent
> 3 BBN
> 3 China Mobile
> 3 CNNIC
> 2 Time Warner Cable
> 1 (22)
> Total: 98
>
> Observations: the top four companies on this list have contributed more than
> half of the NomCom volunteers.  The top three have contributed twice as many
> (44) as all of the entities that contributed only one (22).
>
> Opinion: the NomCom would benefit from having many "independent" members.
> While that could happen (yay, randomness), the odds here don't look great.
>
> -- Sam
>
>
> Footnote: I wasn't entirely sure which of the Nokia and Seimens entries
> (below) to combine.  I erred on the side of combining all of them, knowing
> that there's likely a strong argument to be made for some other treatment.
> In any case, I don't think it will make much of a difference to the
> analysis.
> Teemu Savolainen, Nokia
>
> Jouni Korhonen, Nokia Siemens Networks
> Mehmet Ersue, Nokia Siemens Networks
> Andrew Hutton, Siemens Enterprise Communications

From timo.perala@nsn.com  Wed Aug  1 16:25:01 2012
Return-Path: <timo.perala@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 D7A1B11E83D5 for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 16:25:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jrYiQp0yhjng for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 16:25:01 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id DE4B911E83D3 for <ietf@ietf.org>; Wed,  1 Aug 2012 16:25:00 -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 q71NOvox024258 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <ietf@ietf.org>; Thu, 2 Aug 2012 01:24:57 +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 q71NOvv3018860 for <ietf@ietf.org>; Thu, 2 Aug 2012 01:24:57 +0200
Received: from FIESEXC016.nsn-intra.net ([10.159.0.24]) by DEMUEXC047.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 2 Aug 2012 01:24:57 +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: NomCom 2012-2013: Third Call for Volunteers
Date: Thu, 2 Aug 2012 02:24:54 +0300
Message-ID: <4AF3E8170315EC458F9110B8F9DEDAA801AB7B45@FIESEXC016.nsn-intra.net>
In-Reply-To: <CAF4+nEE_y0YZ6H4AyM-CwvDBfDJ3P+x68zfZ6EEofXh7efDGTA@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: NomCom 2012-2013: Third Call for Volunteers
Thread-Index: Ac1wOnPJcnmKMiqCQhGo5i71fG3bGgAAeitg
References: <20120731044425.12307.52108.idtracker@ietfa.amsl.com><alpine.BSF.2.00.1208011848500.88006@fledge.watson.org> <CAF4+nEE_y0YZ6H4AyM-CwvDBfDJ3P+x68zfZ6EEofXh7efDGTA@mail.gmail.com>
From: "Perala, Timo (NSN - FI/Espoo)" <timo.perala@nsn.com>
To: <ietf@ietf.org>
X-OriginalArrivalTime: 01 Aug 2012 23:24:57.0066 (UTC) FILETIME=[DCEFBCA0:01CD703C]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 2631
X-purgate-ID: 151667::1343863497-00002E58-775E19B1/0-0/0-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, 01 Aug 2012 23:25:02 -0000

Sam,

Related to your footnote: Nokia is different from Nokia Siemens Networks
is different from Siemens. So, rather than grouping them all together
more appropriate (and correct) would be to treat them separately.


cheers
Timo

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
ext Donald Eastlake
Sent: Thursday, August 02, 2012 2:07 AM
To: ietf@ietf.org
Subject: Re: NomCom 2012-2013: Third Call for Volunteers

(1) Your figures show that it is more likely that a noncom member will
be selected from an affiliation listed by only one volunteer then that
they are to be selected from any specific affiliation listed by more
than one volunteer.

(2) Because of appearances of biased voting membership in some early
noncoms, the rules were changes to prohibit more than two voting
members with the same affiliation.

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

On Wed, Aug 1, 2012 at 6:59 PM, Samuel Weiler <weiler@watson.org> wrote:
> On Mon, 30 Jul 2012, NomCom Chair wrote:
>
>> I am pleased to report at this time we have 98 qualified individuals
who
>> have generously volunteer their time to serve on this year's NomCom.
>
> Sorting that list by affiliation and counting the number of names from
each
> affiliation, the volunteer list as of Monday included:
>
> 16 Huawai
> 15 Cisco
> 13 Ericsson
> 9 Juniper
> 5 ZTE
> 4 Nokia/Siemens (debatable; see details)
> 3 Alcatel-Lucent
> 3 BBN
> 3 China Mobile
> 3 CNNIC
> 2 Time Warner Cable
> 1 (22)
> Total: 98
>
> Observations: the top four companies on this list have contributed
more than
> half of the NomCom volunteers.  The top three have contributed twice
as many
> (44) as all of the entities that contributed only one (22).
>
> Opinion: the NomCom would benefit from having many "independent"
members.
> While that could happen (yay, randomness), the odds here don't look
great.
>
> -- Sam
>
>
> Footnote: I wasn't entirely sure which of the Nokia and Seimens
entries
> (below) to combine.  I erred on the side of combining all of them,
knowing
> that there's likely a strong argument to be made for some other
treatment.
> In any case, I don't think it will make much of a difference to the
> analysis.
> Teemu Savolainen, Nokia
>
> Jouni Korhonen, Nokia Siemens Networks
> Mehmet Ersue, Nokia Siemens Networks
> Andrew Hutton, Siemens Enterprise Communications

From sm@resistor.net  Wed Aug  1 17:20:22 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADAAC21F89EB for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 17:20:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nP5Uz1lz3x4X for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 17:20:17 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B39A21F889B for <ietf@ietf.org>; Wed,  1 Aug 2012 17:20:11 -0700 (PDT)
Received: from sm-THINK.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q720K3CX028678; Wed, 1 Aug 2012 17:20:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1343866808; bh=sDFJqyzfoQgTn0Om4/ncrRg7AOykM/7UdgWtxKPJ254=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=GFCVtIP2C8dHKLOjRLt8q+H0+7DbrS84OzuSZbJ5syt4s3Mm8OQgV+E9XiEDChJTA DdigqRyQuGWzGdW7glJ1i5Jfqi34dpCS9y4ynjmrZR5zpKP44dGmd4rjxrPcKWVKXo bDS2d9lXxG6b8G4E4FQfvEAltTLQKTtdBUEsZPD4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1343866808; i=@resistor.net; bh=sDFJqyzfoQgTn0Om4/ncrRg7AOykM/7UdgWtxKPJ254=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=WIpgHpyh8uXgfa/pt1TJVsnPfl9S2FgVyPAvWQgktjLK48fb1k7wgAOTD2PXxDOm8 KrpYf2OQOxih7DWlQYx875FIwDq8ogz/seDFUq8JUVXmR3YXGBmk9IxsFaCifOnOBM PcLPGlbA/H78GKb7RyywnBGqTp3wQNdxS4uUhD+8=
Message-Id: <6.2.5.6.2.20120801163619.0978b1a0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 01 Aug 2012 17:17:36 -0700
To: Samuel Weiler <weiler@watson.org>
From: SM <sm@resistor.net>
Subject: Re: NomCom 2012-2013: Third Call for Volunteers
In-Reply-To: <alpine.BSF.2.00.1208011848500.88006@fledge.watson.org>
References: <20120731044425.12307.52108.idtracker@ietfa.amsl.com> <alpine.BSF.2.00.1208011848500.88006@fledge.watson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 00:20:22 -0000

Hi Sam,
At 03:59 PM 8/1/2012, Samuel Weiler wrote:
>Sorting that list by affiliation and counting the number of names 
>from each affiliation, the volunteer list as of Monday included:
>
>16 Huawai
>15 Cisco
>13 Ericsson
>9 Juniper
>5 ZTE
>4 Nokia/Siemens (debatable; see details)
>3 Alcatel-Lucent
>3 BBN
>3 China Mobile
>3 CNNIC
>2 Time Warner Cable
>1 (22)
>Total: 98
>
>Observations: the top four companies on this list have contributed 
>more than half of the NomCom volunteers.  The top three have 
>contributed twice as many (44) as all of the entities that 
>contributed only one (22).
>
>Opinion: the NomCom would benefit from having many "independent" 
>members.  While that could happen (yay, randomness), the odds here 
>don't look great.

Cisco has more authors than Huawei.  It's interesting to see four 
companies making up more than 44% of the volunteer list.  It was 
pointed out that there cannot be more than two NomCom members with 
the same affiliation.  There isn't anyone with a Google or Microsoft 
affiliation.  There is a person with an ICANN affiliation and one 
with an Internet Society affiliation (see discussion about 
draft-leiba-3777upd-eligibility).

The odds of volunteers from companies at the top of the list being 
selected as a NomCom member is not that low.  One could look at 
NomCom as an exercise in randomness or one could look at it as an 
exercise in "let the market decide".

Regards,
-sm 


From hsantos@isdg.net  Wed Aug  1 18:52:29 2012
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2124B21F8A86 for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 18:52:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.586
X-Spam-Level: 
X-Spam-Status: No, score=-102.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CMrFXjY6mi1F for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 18:52:28 -0700 (PDT)
Received: from catinthebox.net (ftp.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id EEE4C21F8A85 for <ietf@ietf.org>; Wed,  1 Aug 2012 18:52:27 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1418; t=1343872340; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=nfKYZGMdpL/yK0EWT7G53Nvj6HU=; b=Mx+AAmi95rdUxXXlonNl ZJuJKFb1PwvF+0VAob4fby2tVYhP6l1uANDQzkgyZt8NdG5PsVE2oeMhija+sL1g DDHfgvsROaLR/tnthjcCzBfCUybjEuA0XfWK6/FzI3XVq0lbsS+H+gVFeeXDLNZs FyiXPs+3cFe2WrvpbaWjdVQ=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 01 Aug 2012 21:52:20 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 4189125151.5475.4420; Wed, 01 Aug 2012 21:52:19 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1418; t=1343872183; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=mofk/Np MijvunIRzJA9CJJ2odfSOZQ5176T631iGN4o=; b=Mi+m8LnwRU+6Xmo6g7HX47L fbwm2MWM7YkCrcG03OESDFm9FxGu+1wU63L6u13ITPWSRs7Vc/c3wAjF+HxUQlag 2rqWhkClD0PwC6WA/YtALxzr21YhJDZheT4RC5CBhSUHyh1MKCQg2NdU//N0xrxb ZwoIr9XEu/SufIRcRjTo=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 01 Aug 2012 21:49:43 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 492981614.9.6568; Wed, 01 Aug 2012 21:49:42 -0400
Message-ID: <5019DD76.7070402@isdg.net>
Date: Wed, 01 Aug 2012 21:52: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: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com>	<CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com>	<CADnDZ8-6iTjav+utqDOXriKc3FUVesHAy0CD5FtFQjrWDMvuWA@mail.gmail.com>	<201208011733.q71HXPXG021973@mtv-core-4.cisco.com> <CADnDZ89hp9FNoPyx2ms-4+aURLM=_Mk6whoC5NLTm06D_wHJCA@mail.gmail.com>
In-Reply-To: <CADnDZ89hp9FNoPyx2ms-4+aURLM=_Mk6whoC5NLTm06D_wHJCA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 01:52:29 -0000

Mr Baryun, the world was once flat! I commend your efforts.  Who 
knows? Maybe you have the seeds here for the development of a protocol 
expert system, AI based protocol design-configuration systems using 
SBPT "Structured Block Protocol Technology" as a language and tool to 
make the world jump!

Go West! or is that Go East! these days.

-- 
HLS


Abdussalam Baryun wrote:
> Hi Melinda,
> 
> I am already involved, and volunteering work, I done many reviews and
> comments in two WGs, and will hopfuly continue if people are
> welcoming. However, I thank you for your comments,
> 
> AB
> ======
> The mission of the Internet Engineering Task Force is to make the
> Internet work better by producing high-quality and relevant technical
> documents that influence the way people design, use, and manage the
> Internet
> -----------------------------------------------------------------------------------------------------------
> 
> It's pretty clear that you'd like to be involved with the work
> of the IETF in some way.  Allow me to suggest that a more productive
> approach might be to identify a working group in your area of
> expertise, review their documents, provide feedback on those
> documents, and write text or new documents to address any gaps.
> There is work to be done and there are problems to solve.  What
> you are doing now is not helpful.
> 
> Melinda
> 
> 

-- 
HLS



From paf@frobbit.se  Wed Aug  1 19:13:48 2012
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E324111E8164 for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 19:13:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ID0WUdRJL0Fi for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 19:13:48 -0700 (PDT)
Received: from srv01.frobbit.se (srv01.frobbit.se [IPv6:2a02:80:3ffe::39]) by ietfa.amsl.com (Postfix) with ESMTP id 3190F11E80EF for <ietf@ietf.org>; Wed,  1 Aug 2012 19:13:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by srv01.frobbit.se (Postfix) with ESMTP id C4287144ADA59; Thu,  2 Aug 2012 04:13:46 +0200 (CEST)
X-Virus-Scanned: amavisd-new at frobbit.se
Received: from srv01.frobbit.se ([127.0.0.1]) by localhost (srv01.frobbit.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gtsYCYjhOoGy; Thu,  2 Aug 2012 04:13:45 +0200 (CEST)
Received: from [192.168.1.53] (frobbit.cust.teleservice.net [85.30.128.225]) (Authenticated sender: paf01) by srv01.frobbit.se (Postfix) with ESMTP id 31FC1144ADA52; Thu,  2 Aug 2012 04:13:44 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: NomCom 2012-2013: Third Call for Volunteers
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <alpine.BSF.2.00.1208011848500.88006@fledge.watson.org>
Date: Thu, 2 Aug 2012 04:13:43 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3B46F876-010A-4C9D-9CC4-704211939459@frobbit.se>
References: <20120731044425.12307.52108.idtracker@ietfa.amsl.com> <alpine.BSF.2.00.1208011848500.88006@fledge.watson.org>
To: Samuel Weiler <weiler@watson.org>
X-Mailer: Apple Mail (2.1485)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 02:13:49 -0000

2 aug 2012 kl. 00:59 skrev Samuel Weiler <weiler@watson.org>:

> Sorting that list by affiliation and counting the number of names from =
each affiliation, the volunteer list as of Monday included:
>=20
> 16 Huawai
> 15 Cisco
> 13 Ericsson
> 9 Juniper
> 5 ZTE
> 4 Nokia/Siemens (debatable; see details)
> 3 Alcatel-Lucent
> 3 BBN
> 3 China Mobile
> 3 CNNIC
> 2 Time Warner Cable
> 1 (22)
> Total: 98
>=20
> Observations: the top four companies on this list have contributed =
more than half of the NomCom volunteers.  The top three have contributed =
twice as many (44) as all of the entities that contributed only one =
(22).

A good thing is that the "one" category is still the largest.

Without arguing against you regarding this being something one should =
keep an eye on.

   Patrik


From yoshihiro.ohba@toshiba.co.jp  Wed Aug  1 22:11:03 2012
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B050121F8AD9 for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 22:11:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.089
X-Spam-Level: 
X-Spam-Status: No, score=-8.089 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_HI=-8, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h8jEfg1PuifS for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 22:11:03 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by ietfa.amsl.com (Postfix) with ESMTP id 2FCC821F8B4C for <ietf@ietf.org>; Wed,  1 Aug 2012 22:10:57 -0700 (PDT)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp  with ESMTP id q725AvQJ024785 for <ietf@ietf.org>; Thu, 2 Aug 2012 14:10:57 +0900 (JST)
Received: (from root@localhost) by arc11.toshiba.co.jp  id q725Au23013079 for ietf@ietf.org; Thu, 2 Aug 2012 14:10:56 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148]  by arc11.toshiba.co.jp with ESMTP id QAA13078; Thu, 2 Aug 2012 14:10:56 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp  with ESMTP id q725AuDi005476 for <ietf@ietf.org>; Thu, 2 Aug 2012 14:10:56 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id q725Aud8008568; Thu, 2 Aug 2012 14:10:56 +0900 (JST)
Received: from [133.199.17.4] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0M84006VC3Q5YHM0@mail.po.toshiba.co.jp> for ietf@ietf.org; Thu, 02 Aug 2012 14:10:56 +0900 (JST)
Date: Thu, 02 Aug 2012 14:10:51 +0900
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
Subject: Re: NomCom 2012-2013: Third Call for Volunteers
In-reply-to: <3B46F876-010A-4C9D-9CC4-704211939459@frobbit.se>
To: ietf@ietf.org
Message-id: <501A0BDB.2040501@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8; format=flowed
Content-transfer-encoding: 8BIT
References: <20120731044425.12307.52108.idtracker@ietfa.amsl.com> <alpine.BSF.2.00.1208011848500.88006@fledge.watson.org> <3B46F876-010A-4C9D-9CC4-704211939459@frobbit.se>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 05:11:03 -0000

What is the exact definition of "affiliation" in IETF?

If a consultant who runs his/her own consulting company X is paid by 
his/her customer company Y for his/her IETF activities including 
NOMCOM activity, then what is his/her affiliation?

Yoshihiro Ohba

(2012/08/02 11:13), Patrik FÃ¤ltstrÃ¶m wrote:
> 2 aug 2012 kl. 00:59 skrev Samuel Weiler <weiler@watson.org>:
>
>> Sorting that list by affiliation and counting the number of names from each affiliation, the volunteer list as of Monday included:
>>
>> 16 Huawai
>> 15 Cisco
>> 13 Ericsson
>> 9 Juniper
>> 5 ZTE
>> 4 Nokia/Siemens (debatable; see details)
>> 3 Alcatel-Lucent
>> 3 BBN
>> 3 China Mobile
>> 3 CNNIC
>> 2 Time Warner Cable
>> 1 (22)
>> Total: 98
>>
>> Observations: the top four companies on this list have contributed more than half of the NomCom volunteers.  The top three have contributed twice as many (44) as all of the entities that contributed only one (22).
>
> A good thing is that the "one" category is still the largest.
>
> Without arguing against you regarding this being something one should keep an eye on.
>
>     Patrik
>
>


From mstjohns@comcast.net  Wed Aug  1 22:24:27 2012
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C29A311E809A for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 22:24:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.157
X-Spam-Level: 
X-Spam-Status: No, score=-101.157 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U65o5wNI3YS6 for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 22:24:27 -0700 (PDT)
Received: from qmta13.emeryville.ca.mail.comcast.net (qmta13.emeryville.ca.mail.comcast.net [76.96.27.243]) by ietfa.amsl.com (Postfix) with ESMTP id 56FBD11E80D9 for <ietf@ietf.org>; Wed,  1 Aug 2012 22:24:26 -0700 (PDT)
Received: from omta07.emeryville.ca.mail.comcast.net ([76.96.30.59]) by qmta13.emeryville.ca.mail.comcast.net with comcast id hhKW1j0051GXsucADhQSCT; Thu, 02 Aug 2012 05:24:26 +0000
Received: from [10.0.1.3] ([130.129.69.209]) by omta07.emeryville.ca.mail.comcast.net with comcast id hhQF1j00C4Wubui8UhQJd7; Thu, 02 Aug 2012 05:24:24 +0000
References: <20120731044425.12307.52108.idtracker@ietfa.amsl.com> <alpine.BSF.2.00.1208011848500.88006@fledge.watson.org> <3B46F876-010A-4C9D-9CC4-704211939459@frobbit.se> <501A0BDB.2040501@toshiba.co.jp>
In-Reply-To: <501A0BDB.2040501@toshiba.co.jp>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=utf-8
Message-Id: <B7C97596-8D01-4705-A0F8-657401C84093@comcast.net>
X-Mailer: iPad Mail (9B206)
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: NomCom 2012-2013: Third Call for Volunteers
Date: Wed, 1 Aug 2012 22:24:17 -0700
To: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 05:24:27 -0000

I reported both when I volunteered. =20

Sent from my iPad

On Aug 1, 2012, at 22:10, Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp> wrot=
e:

> What is the exact definition of "affiliation" in IETF?
>=20
> If a consultant who runs his/her own consulting company X is paid by his/h=
er customer company Y for his/her IETF activities including NOMCOM activity,=
 then what is his/her affiliation?
>=20
> Yoshihiro Ohba
>=20
> (2012/08/02 11:13), Patrik F=C3=A4ltstr=C3=B6m wrote:
>> 2 aug 2012 kl. 00:59 skrev Samuel Weiler <weiler@watson.org>:
>>=20
>>> Sorting that list by affiliation and counting the number of names from e=
ach affiliation, the volunteer list as of Monday included:
>>>=20
>>> 16 Huawai
>>> 15 Cisco
>>> 13 Ericsson
>>> 9 Juniper
>>> 5 ZTE
>>> 4 Nokia/Siemens (debatable; see details)
>>> 3 Alcatel-Lucent
>>> 3 BBN
>>> 3 China Mobile
>>> 3 CNNIC
>>> 2 Time Warner Cable
>>> 1 (22)
>>> Total: 98
>>>=20
>>> Observations: the top four companies on this list have contributed more t=
han half of the NomCom volunteers.  The top three have contributed twice as m=
any (44) as all of the entities that contributed only one (22).
>>=20
>> A good thing is that the "one" category is still the largest.
>>=20
>> Without arguing against you regarding this being something one should kee=
p an eye on.
>>=20
>>    Patrik
>>=20
>>=20
>=20

From weiler@watson.org  Wed Aug  1 22:37:46 2012
Return-Path: <weiler@watson.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 BB66011E809A for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 22:37:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.429
X-Spam-Level: 
X-Spam-Status: No, score=-2.429 tagged_above=-999 required=5 tests=[AWL=0.170,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EXjowxOQVpkZ for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 22:37:45 -0700 (PDT)
Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by ietfa.amsl.com (Postfix) with ESMTP id AE77311E80D9 for <ietf@ietf.org>; Wed,  1 Aug 2012 22:37:44 -0700 (PDT)
Received: from fledge.watson.org (localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.14.5/8.14.5) with ESMTP id q725bhSm099108; Thu, 2 Aug 2012 01:37:43 -0400 (EDT) (envelope-from weiler@watson.org)
Received: from localhost (weiler@localhost) by fledge.watson.org (8.14.5/8.14.5/Submit) with ESMTP id q725bhqI099102; Thu, 2 Aug 2012 01:37:43 -0400 (EDT) (envelope-from weiler@watson.org)
X-Authentication-Warning: fledge.watson.org: weiler owned process doing -bs
Date: Thu, 2 Aug 2012 01:37:43 -0400 (EDT)
From: Samuel Weiler <weiler@watson.org>
To: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
Subject: Re: NomCom 2012-2013: Third Call for Volunteers
In-Reply-To: <501A0BDB.2040501@toshiba.co.jp>
Message-ID: <alpine.BSF.2.00.1208020132140.96564@fledge.watson.org>
References: <20120731044425.12307.52108.idtracker@ietfa.amsl.com> <alpine.BSF.2.00.1208011848500.88006@fledge.watson.org> <3B46F876-010A-4C9D-9CC4-704211939459@frobbit.se> <501A0BDB.2040501@toshiba.co.jp>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (fledge.watson.org [127.0.0.1]); Thu, 02 Aug 2012 01:37:44 -0400 (EDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 05:37:46 -0000

On Thu, 2 Aug 2012, Yoshihiro Ohba wrote:

> What is the exact definition of "affiliation" in IETF?

Quoting from RFC3777:

"Rather than defining precise rules for how to define "affiliation", 
the IETF community depends on the honor and integrity of the 
participants to make the process work."

As a community, we recognize that this could easily be gamed, and we 
expect each other to behave reasonably.

> If a consultant who runs his/her own consulting company X is paid by 
> his/her customer company Y for his/her IETF activities including 
> NOMCOM activity, then what is his/her affiliation?

As a first pass answer, it's whatever the consultant would normally 
show on a meeting registration badge.  Typically, I'd expect X.  But 
the degree of funding is as extreme as you describe, it might still be 
appropriate to step aside if two persons from Y are also chosen (or 
ask one of them to step aside).

-- Sam

From mrex@sap.com  Wed Aug  1 22:52:55 2012
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 DC6EA11E812A for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 22:52:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.196
X-Spam-Level: 
X-Spam-Status: No, score=-10.196 tagged_above=-999 required=5 tests=[AWL=0.053, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6SXUvtc8e8V3 for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 22:52:55 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id B2FCA11E8122 for <ietf@ietf.org>; Wed,  1 Aug 2012 22:52:54 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q725qlqt007571 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 2 Aug 2012 07:52:52 +0200 (MEST)
Subject: Re: I-D Action: draft-balaji-mpls-lawful-intercept-thru-label-dis-00.txt
In-Reply-To: <m2ipd5w3um.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
Date: Thu, 2 Aug 2012 07:52:47 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20120802055247.66F7F1A10A@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: IETF discussion list <ietf@ietf.org>, Scott O Bradner <sob@sobco.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: Thu, 02 Aug 2012 05:52:56 -0000

Randy Bush wrote:
> 
> Scott O Bradner wrote:
>>
>> 2804 does not say not to talk about such things - or that such
>> documents should not be published as RFCs  - 2804 says that the
>> IETF will not do standards work in this area
> 
> for those of us who are easily confused, could you differentiate between
> working on douments and publishing them as rfcs from doing standards
> work?

I can not answer this on Scott's behalf, but my interpretation of
this paragraph of 2804:

   - The IETF, an international standards body, believes itself to be
     the wrong forum for designing protocol or equipment features that
     address needs arising from the laws of individual countries,
     because these laws vary widely across the areas that IETF standards
     are deployed in.  Bodies whose scope of authority correspond to a
     single regime of jurisdiction are more appropriate for this task.

means that while publishing information as independent submission
as RFCs would be OK, and talking about the technology or its consequences
for IETF protocols and standardization work is OK
(that is primarily a matter of free speech).

Discussion within the IETF on wiretapping technology, with the purpose
of changing either the wiretapping technology prior to publishing
it as RFC, or with the purpose of changing IETF protocols to facilitate
wiretapping technology is _not_ OK, independent of whether the document
is published on standards track or informational / experimental.


But it is really difficult to stay out of that rathole.

There is a wiretapping technology in use that is completely subverting
the security of "TLS" (Transport Layer Security), in form of transparent
intercepting SSL/TLS proxies, that impersonate the real communication
peers by forging themselves certificates on the fly, and by coercing
TLS clients, such as Web-Browsers through organizational authority,
to blindly trust and silently accept the certs that are forged by the
intercepting SSL/TLS proxies.

Such technology kills other protocol features of TLS besides integrity
and confidentiality protection along with it, such as client certificate
support and channel bindings.


It is not easy to decide what kind of discussion about such gear and
possible TLS extensions to facilitate such gear are OK, and which are
in conflict with rfc2804.


With DANE (DNSSEC-protected DNS "TLSA" records) conveying additional
information for verification the correctness of a TLS Server's
presented certificate (chain), silently intercepting TLS-protected
traffic will become _much_ harder for those intercepting SSL/TLS proxies.


-Martin

From barryleiba@gmail.com  Wed Aug  1 23:01:04 2012
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D496421F8B76 for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 23:01:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.98
X-Spam-Level: 
X-Spam-Status: No, score=-102.98 tagged_above=-999 required=5 tests=[AWL=-0.003, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VX8hNHfItheX for <ietf@ietfa.amsl.com>; Wed,  1 Aug 2012 23:01:04 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1915D21F8B74 for <ietf@ietf.org>; Wed,  1 Aug 2012 23:01:03 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so8462919vcb.31 for <ietf@ietf.org>; Wed, 01 Aug 2012 23:01:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=Jpd0bGCrSRJUvVyo22tRZ7vzRLjzBezZ9UKVgeWgiiM=; b=Hj8rFUKwHH0vSOZkaM8VrbY5C/Y2Ta04Sf/5bqvSftowdHl7N9bMIoQbr4lZqsUWbe Awh/0gIDXv7PPF01B9AXRY/DkbbJWDxS/JEv6+aJ/dSXsR4Er0EWITGI0wXJBFl0IPDJ 1rdC7kXiWdAvcKXx29WLCWrqUEBHKbvM6ByqPQXGIpRlmA6HSQtpV2mhUNW99XYGIPL7 ZCqlxj6iUATTzPZqL6WhyGOlbRUKkuZeF44iCGasArhsobA6JmoS7UMkcayhecw8CSoO 53IGQ4m32r7VGmbby1UwpR3TvfSWsr89S5e7dc66DHTgsEpt25VqNHhXSGBDRAiH+U+I XWzw==
MIME-Version: 1.0
Received: by 10.52.71.137 with SMTP id v9mr16771927vdu.63.1343887263513; Wed, 01 Aug 2012 23:01:03 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.220.29.8 with HTTP; Wed, 1 Aug 2012 23:01:03 -0700 (PDT)
In-Reply-To: <20120802055556.1356.17133.idtracker@ietfa.amsl.com>
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com>
Date: Thu, 2 Aug 2012 02:01:03 -0400
X-Google-Sender-Auth: bdF-AriH_eUc0Cw2KV8xtkGpMbo
Message-ID: <CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com>
Subject: Re: New Version Notification for draft-leiba-extended-doc-shepherd-00.txt
From: Barry Leiba <barryleiba@computer.org>
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: Thu, 02 Aug 2012 06:01:04 -0000

I've posted my thoughts on starting document shepherding at the time a
document first starts its life in a working group, and on the tasks a
shepherd might perform at each stage in the document's life.  I intend
to pursue having this published as an Informational document, not a
BCP, reflecting my personal opinion.  That said, I'm interested in
comments, and might make changes accordingly.

Barry

> Filename:        draft-leiba-extended-doc-shepherd
> Revision:        00
> Title:           Document Shepherding Throughout a Document's Lifecycle
> Creation date:   2012-08-02
> WG ID:           Individual Submission
> Number of pages: 24
> URL:
> http://www.ietf.org/internet-drafts/draft-leiba-extended-doc-shepherd-00.txt
> Status:
> http://datatracker.ietf.org/doc/draft-leiba-extended-doc-shepherd
> Htmlized:
> http://tools.ietf.org/html/draft-leiba-extended-doc-shepherd-00
>
>
> Abstract:
>    RFC 4858 talks about "Document Shepherding from Working Group Last
>    Call to Publication".  There's a significant part of a document's
>    life that happens before working group last call, starting, really,
>    at the time a working group begins discussing a version of the idea
>    that's been posted as an individual draft.  It seems reasonable and
>    helpful to begin shepherding when there's a call for adoption as a
>    working group document, and this document gives one Area Director's
>    view of how that extended shepherding function might work, and what
>    tasks might be involved throughout the document's lifecycle.

From abdussalambaryun@gmail.com  Thu Aug  2 01:19:02 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF6F421F8DA9 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 01:19:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.483
X-Spam-Level: 
X-Spam-Status: No, score=-3.483 tagged_above=-999 required=5 tests=[AWL=0.116,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FKqdYo3dk6hw for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 01:19:01 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 269E221F8DA7 for <ietf@ietf.org>; Thu,  2 Aug 2012 01:19:01 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so8573737vcb.31 for <ietf@ietf.org>; Thu, 02 Aug 2012 01:19:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=V52Bz8zUXZuwQf92j8o5TNfKCVB7YfrVuTEyLmyIJx4=; b=vlz5QfHEMuZe2k18RkLUzaHjIGhtjRuvQ4DBYB2NgLMTbFsH6pWIubHAJGGLLSLHgd t0kNLgntsKx67y0UuEctUV+V/mZTBTHx26V6EvBYE7sU8njcVrI1SrHJranUQ85sN56Z Z/gCXQFZXv+6uE4UD3S4tBvA3GPUBcIMO+vImNE9bLcdqfR1Kb60mGt3/fOnSFml/WI1 oZmZS8jAija/eF6IDe4/P9fHtEhPtlsoAqCWeQXxGVjghiXAwVqwJGOKmEvF2addSHqY 8qtC+Wf63KbclgmzxjFYBCXN/te0s7B1e5kb1SuSmZ8xBR2zXulSFUEhS6thYyhTymYu mz1g==
MIME-Version: 1.0
Received: by 10.52.94.36 with SMTP id cz4mr17104674vdb.10.1343895540660; Thu, 02 Aug 2012 01:19:00 -0700 (PDT)
Received: by 10.220.141.200 with HTTP; Thu, 2 Aug 2012 01:19:00 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20120801125000.04c23488@resistor.net>
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com> <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com> <CADnDZ8-6iTjav+utqDOXriKc3FUVesHAy0CD5FtFQjrWDMvuWA@mail.gmail.com> <CAPv4CP-LBGVPn9O5N1HmbUqw8H7dpK66q7JEcrYA_Sd395giCA@mail.gmail.com> <CADnDZ892BCo7Vb87eTKGNmpHGxQi5RK6khT8curBL8iFkUjqcw@mail.gmail.com> <6.2.5.6.2.20120801125000.04c23488@resistor.net>
Date: Thu, 2 Aug 2012 10:19:00 +0200
Message-ID: <CADnDZ89qzeHSfEZ9BdkTMOX7bsDwk3Rj05OxEr+07+MfnXBqew@mail.gmail.com>
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 08:19:03 -0000

Hi SM,

Thanks for your comments, I will note your feedback and follow to read
into these issues as you advise, thanking you,

Best Regards
AB
======

On 8/1/12, SM <sm@resistor.net> wrote:
> At 11:19 AM 8/1/2012, Abdussalam Baryun wrote:
>>Yes my concern is how/when use terms not meaning of terms. Ok,  What
>>about "MUST" (every one know it), wasn't it clear as "if then", please
>>explain why capital?
>
> You are probably receiving feedback on your draft because the WG
> sessions this week are boring. :-)  The is a thread about "all caps"
> at http://www.ietf.org/mail-archive/web/ietf/current/msg73338.html  I
> suggest reading RFC 1122 and RFC 1123 to get a view of how some
> specifications were written and why they were written in such a way.
>
> Melinda Shore provided some good advice (
> http://www.ietf.org/mail-archive/web/ietf/current/msg74191.html ).  I
> would not say that your draft is not helpful.  It is up to you to
> assess whether draft-baryun-rfc2119-update-00 can gain IETF Consensus.
>
> Regards,
> -sm
>
>

From daedulus@btconnect.com  Thu Aug  2 01:36:54 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4872521F8DFB for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 01:36:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.698
X-Spam-Level: 
X-Spam-Status: No, score=-3.698 tagged_above=-999 required=5 tests=[AWL=-0.099, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EcFWFsPKtO41 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 01:36:53 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe005.messaging.microsoft.com [216.32.180.188]) by ietfa.amsl.com (Postfix) with ESMTP id 1A94A21F8DFA for <ietf@ietf.org>; Thu,  2 Aug 2012 01:36:52 -0700 (PDT)
Received: from mail7-co1-R.bigfish.com (10.243.78.248) by CO1EHSOBE005.bigfish.com (10.243.66.68) with Microsoft SMTP Server id 14.1.225.23; Thu, 2 Aug 2012 08:36:52 +0000
Received: from mail7-co1 (localhost [127.0.0.1])	by mail7-co1-R.bigfish.com (Postfix) with ESMTP id 160DBD002C4; Thu,  2 Aug 2012 08:36:52 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.224.141; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0702HT004.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -24
X-BigFish: PS-24(zz9371I98bI542M1432Izz1202hzz1033IL8275dhz2dh2a8h5a9h668h839hd24hf0ah107ah304l)
Received: from mail7-co1 (localhost.localdomain [127.0.0.1]) by mail7-co1 (MessageSwitch) id 1343896610863082_8911; Thu,  2 Aug 2012 08:36:50 +0000 (UTC)
Received: from CO1EHSMHS014.bigfish.com (unknown [10.243.78.249])	by mail7-co1.bigfish.com (Postfix) with ESMTP id CF2F3660096; Thu,  2 Aug 2012 08:36:50 +0000 (UTC)
Received: from DB3PRD0702HT004.eurprd07.prod.outlook.com (157.55.224.141) by CO1EHSMHS014.bigfish.com (10.243.66.24) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 2 Aug 2012 08:36:50 +0000
Received: from AMXPRD0410HT003.eurprd04.prod.outlook.com (157.56.248.165) by pod51017.outlook.com (10.3.4.154) with Microsoft SMTP Server (TLS) id 14.15.86.1; Thu, 2 Aug 2012 08:36:40 +0000
Message-ID: <008c01cd7089$55631640$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Samuel Weiler <weiler@watson.org>, <ietf@ietf.org>
References: <20120731044425.12307.52108.idtracker@ietfa.amsl.com> <alpine.BSF.2.00.1208011848500.88006@fledge.watson.org>
Subject: Re: NomCom 2012-2013: Third Call for Volunteers
Date: Thu, 2 Aug 2012 09:32:13 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.248.165]
X-OriginatorOrg: btconnect.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 08:36:54 -0000

----- Original Message -----
From: "Samuel Weiler" <weiler@watson.org>
To: <ietf@ietf.org>
Sent: Wednesday, August 01, 2012 11:59 PM
>
> Sorting that list by affiliation and counting the number of names from
> each affiliation, the volunteer list as of Monday included:
>
> 16 Huawai
> 15 Cisco
> 13 Ericsson
> 9 Juniper
> 5 ZTE
> 4 Nokia/Siemens (debatable; see details)
> 3 Alcatel-Lucent
> 3 BBN
> 3 China Mobile
> 3 CNNIC
> 2 Time Warner Cable
> 1 (22)
> Total: 98
>
> Observations: the top four companies on this list have contributed
> more than half of the NomCom volunteers.  The top three have
> contributed twice as many (44) as all of the entities that
> contributed only one (22).

Looks like a fairly accurate reflection of the driving force behind most
of the I-Ds I see, in Areas such as Routing and Ops.

Whether NomCom should reflect the forces behind those I-Ds I am less
clear about.

Tom Petch

> Opinion: the NomCom would benefit from having many "independent"
> members.  While that could happen (yay, randomness), the odds here
> don't look great.
>
> -- Sam
>
> Footnote: I wasn't entirely sure which of the Nokia and Seimens
> entries (below) to combine.  I erred on the side of combining all of
> them, knowing that there's likely a strong argument to be made for
> some other treatment.  In any case, I don't think it will make much of
> a difference to the analysis.
> Teemu Savolainen, Nokia
> Jouni Korhonen, Nokia Siemens Networks
> Mehmet Ersue, Nokia Siemens Networks
> Andrew Hutton, Siemens Enterprise Communications



From abdussalambaryun@gmail.com  Thu Aug  2 01:50:21 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C44CC21F881D for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 01:50:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.483
X-Spam-Level: 
X-Spam-Status: No, score=-3.483 tagged_above=-999 required=5 tests=[AWL=0.116,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i9LX82o4Icc1 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 01:50:21 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id F01E721F885D for <ietf@ietf.org>; Thu,  2 Aug 2012 01:50:10 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so131730vbb.31 for <ietf@ietf.org>; Thu, 02 Aug 2012 01:50:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=mXSC/HujAWODbGcPU14BQEmOWDGo5HSfVEL3rWA9Swg=; b=fVQBQSpGlHPptaLaR0bfOv5JSQeMxmhL20AH/f/ktmFzVWQ/lxKez9SPPbOBXXuNas ej6GNy12CC2HLoO16g2HGLFerSJV8vH7kUcfqjgDWs7zq8xMAQbnuG2Z7W98sVc1YH+G pm+4pGQ57FVDybJpYCoTGgSnx4aC1mMpeRZ1pT1DD4gqJ5BTS64i4PJB/aLIh66vzxah QiRg2lZRgd6ME7bJXpuFjduWU36J925xQCO4i000JuUZqpdL4WNzdpduY1oR1wRohg9V ZNCqTNxC967dcWtFlZYjw/UuWDXVDP90eoYPbGWOIOWJe3Y1DmFSQI8XO20ZFOUPxdoS 92EQ==
MIME-Version: 1.0
Received: by 10.52.90.144 with SMTP id bw16mr16799131vdb.129.1343897410444; Thu, 02 Aug 2012 01:50:10 -0700 (PDT)
Received: by 10.220.141.200 with HTTP; Thu, 2 Aug 2012 01:50:10 -0700 (PDT)
In-Reply-To: <CADnDZ88fJXk6RprXNSs1HhrLJ-MHVf-R_S2GnbeGFcsCVB36LA@mail.gmail.com>
References: <CADnDZ88fJXk6RprXNSs1HhrLJ-MHVf-R_S2GnbeGFcsCVB36LA@mail.gmail.com>
Date: Thu, 2 Aug 2012 10:50:10 +0200
Message-ID: <CADnDZ8_ZqbvA2CRL0F9+gfGuPWdT9E4Grp-bRaz=aFgkBtDdyA@mail.gmail.com>
Subject: Re: RFC Errata: when to file, and when not to
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: barryleiba@computer.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 08:50:21 -0000

Hi Barry,

Could you refer to a RFC that states your below information or
procedure, if there is not, I recommend some one doing procedure
drafts to take it over. Please note that ALL reports from any
participant should be useful for IETF community and system. Even if
he/she misunderstood, this does not mean that he/she is not useful,
that means the IETF system/community needs to adjust to help
participants to understand and follow.

For me I will note your procedure so that I will not report wrongly,
but I will continue reporting my comments/views, and hope if some
thing is wrong I get a reply like your, thanking you,

AB
IETF Particpant
==================================================
The mission of the Internet Engineering Task Force is to make the
Internet work better by producing high-quality and relevant technical
documents that influence the way people design, use, and manage the
Internet.
==================================================

> We've been seeing a lot of inappropriate errata reports, made by
> well-meaning people who, surely, think their reports are useful, even
> important.  These aren't free: they take time to process, and they
> form clutter in the errata system, obscuring the ones that do fit into
> what errata are meant to be.
>
>
> So I wanted to clarify what's meant to be reported, and what's not.
>
>
> A valid erratum, one that the IESG will mark as "Verified", mets two
> criteria:
>
>
> 1. It is truly an *error* in the original document.  That is, it would
> have been considered an error *at the time the document was
> published*, had it been noticed at the time.
>
>
> 2. It is important, an error that would cause someone to misread the
> document in a significant way, causing implementation or deployment
> problems, or other serious issues.
>
>
> Criterion 1 means that anything that is "wrong" because of situations
> or discussions that have come up since publication are not appropriate
> errata.  Consider the differences among these:
>
>
> - (a) Someone realizes that the document forgot to specify the valid
> range of a value.
>
>
> - (b) Someone realizes that the range specified did not correctly
> reflect the result of the discussion at the time (the change got
> missed and no one noticed).
>
>
> - (c) Someone realizes that the range specified causes problems in
> practice, but we didn't know that would happen when we published the
> document.
>
>
> (a) and (b) are valid errata, and should get marked as "Verified".
> (c) is NOT valid for the errata system, and really ought to be marked
> as "Rejected".
>
>
> Criterion 2 means that minor typos are NOT appropriate errata.  The
> IESG will mark these as "Held for Document Update", but, really, there
> is no need to say that "an" should be "and", that a comma is missing
> (unless it seriously affects the meaning and is likely to be
> mis-read), or that "concensus" is misspelled (as here).  Again,
> consider the differences:
>
>
> - (a) "The server will now respond with an error code," where "now"
> should have been "not".
>
>
> - (b) "The server will not repond with an error code," where "repond"
> should have been "respond".
>
>
> - (c) "The server will not respond with and error code," where "and"
> should have been "an".
>
>
> (a) is the only valid one here.  There's no real value in recording
> the others as errata.
>
>
> In particular, the errata system is NOT meant to be used as an issue
> tracker; please do not submit errata reports with the *intent* that
> they be marked as "Held for Document Update", to be used as an issue
> list later.  We have mailing lists, issue trackers, and wikis for this
> purpose.
>
>
> Barry, Applications AD
>

From brian.e.carpenter@gmail.com  Thu Aug  2 01:58:29 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26E3D21F8E56 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 01:58:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.44
X-Spam-Level: 
X-Spam-Status: No, score=-101.44 tagged_above=-999 required=5 tests=[AWL=0.251, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gv7AIl0qluTw for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 01:58:28 -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 4D22E21F8DAC for <ietf@ietf.org>; Thu,  2 Aug 2012 01:58:28 -0700 (PDT)
Received: by eaai11 with SMTP id i11so64693eaa.31 for <ietf@ietf.org>; Thu, 02 Aug 2012 01:58:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=jJQqq5DpCsNaR5lY5/cvgaC8dOSn5mwuW0QXmu+a4yk=; b=YdNFkqj61Io8tWwLsUm7ayLpNyTxKXyWZg2Vc8emZ3lEGLQKLTUgg/oX/UHFJ/3ztV 3vnV/Tpm59eflJafqIEcDvbiil/53UMRtyY8t80HR+eXiVRD1IoW/oXdcUamuVLVgZZC I/r4GynnMoge1NcQdIQ9glggxQSZaVuZHGuuJBW7aaWfq38wDNWWAY47vWb4CY/yBOjr UkKglKmx21wKqOffetpO5Fto99eDWo2hPUCp6dIe/95W/t4/0A2+CN9qV1K+37//t+8y xlejwF67GgWV+qk8pLcQYmaXXLbFA9DJGk/j5JOOwgXICo/UChBtuHmEgpU8qY+1YUOh pSDg==
Received: by 10.14.202.69 with SMTP id c45mr26101318eeo.4.1343897907461; Thu, 02 Aug 2012 01:58:27 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-219-46.as13285.net. [2.102.219.46]) by mx.google.com with ESMTPS id v5sm15527695eel.6.2012.08.02.01.58.25 (version=SSLv3 cipher=OTHER); Thu, 02 Aug 2012 01:58:26 -0700 (PDT)
Message-ID: <501A4139.7050108@gmail.com>
Date: Thu, 02 Aug 2012 09:58:33 +0100
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: iab@iab.org
Subject: Re: Affirmation of the Modern Global Standards Paradigm
References: <04e401cd7055$416aecf0$c440c6d0$@iab.org>
In-Reply-To: <04e401cd7055$416aecf0$c440c6d0$@iab.org>
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, 02 Aug 2012 08:58:29 -0000

Hi,

In general this seem like a Good Thing. However, I have a slight confusion
caused by these two extracts:

> Openness. Standards processes are open to all interested and informed
> parties.

...

> 4. Availability. Standards are made accessible to all for implementation and
> deployment under fair terms. Given market diversity, fair terms may vary from
> royalty-free (especially where open source is commonplace) to fair, reasonable,
> and non-discriminatory terms (FRAND).

"Open" in standards parlance is used in (at least) two ways - open process,
as in the first extract, and open publication.

I'd like to see the "Availability" clause changed to "Open Availability".
But then I'm confused - the text seems to mix up dependency on patents
with the question of access to the text of the standard. I think these two
aspects need to be separated. Then we'd get something like:

4. Open Availablity. The text of standards is made accessible to all,
free of charge or at low cost.

5. Implementability. Standards may be implemented and deployed under fair terms.
Given market diversity, fair terms may vary from royalty-free (especially where
open source is commonplace) to fair, reasonable, and non-discriminatory terms (FRAND).

Regards
   Brian Carpenter

On 02/08/2012 03:19, IAB Chair wrote:
> The IAB, IESG, IEEE-SA and W3C have been developing an
> <http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-4.pdf>
> "Affirmation of the Modern Global Standards Paradigm".  Comments may be sent
> to iab@iab.org.
> 
> 

From duerst@it.aoyama.ac.jp  Thu Aug  2 03:28:55 2012
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CE8F21F8E31 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 03:28:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.41
X-Spam-Level: 
X-Spam-Status: No, score=-100.41 tagged_above=-999 required=5 tests=[AWL=-0.620, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b7ChP86yZvgJ for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 03:28:54 -0700 (PDT)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id A40B921F8E2F for <ietf@ietf.org>; Thu,  2 Aug 2012 03:28:52 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id q72AShDS029049 for <ietf@ietf.org>; Thu, 2 Aug 2012 19:28:43 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 3de1_096e_d5827d6a_dc8c_11e1_8faa_001d096c5782; Thu, 02 Aug 2012 19:28:42 +0900
Received: from [IPv6:::1] ([133.2.210.1]:41530) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15EB14F> for <ietf@ietf.org> from <duerst@it.aoyama.ac.jp>; Thu, 2 Aug 2012 19:28:46 +0900
Message-ID: <501A5656.2050407@it.aoyama.ac.jp>
Date: Thu, 02 Aug 2012 19:28:38 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: RFC Errata: when to file, and when not to
References: <CALaySJKV96tdXhzfPD1e1Mro_+gp5aDarF7Z06QrA+iQtnHkLw@mail.gmail.com>
In-Reply-To: <CALaySJKV96tdXhzfPD1e1Mro_+gp5aDarF7Z06QrA+iQtnHkLw@mail.gmail.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: Thu, 02 Aug 2012 10:28:55 -0000

Hello Barry,

Thanks for explanation about errata, which must have been caused at 
least in part by an erratum that I submitted recently.

Just for the record, I want to mention that the errata report form at 
http://www.rfc-editor.org/errata_report.php has a "type" field with two 
categories, "Technical" and "Editorial", where "Editorial" is defined in 
the help popup as: "spelling, grammar, punctuation, or syntax error that 
does not affect the technical meaning". This would directly contradict 
your "Criterion 2 means that minor typos are NOT appropriate errata."


However, my main point is a different one. At the end of your mail, you 
wrote:

 > In particular, the errata system is NOT meant to be used as an issue
 > tracker; please do not submit errata reports with the *intent* that 
they be
 > marked as "Held for Document Update", to be used as an issue list later.
 >   We have mailing lists, issue trackers, and wikis for this purpose.

Of course we have mailing lists, issue trackers, and wikis, but the 
problem is that none of them are for RFCs. And if there's a tracker for 
a bis version, it's not necessarily easy to find from the RFC.

Actually, even if somebody finds the -bis draft, in many (if not most) 
cases, these drafts don't contain pointers to issue trackers, wikis, or 
the like (a pointer to a mailing list, at least indirectly via the 
mention of a WG, should be there in most cases, I guess).

The question then comes up on whether we can do better. And my guess is 
that in this day and age of linked information, we should be able to do 
better. With the tools version of an RFC, which is quickly becoming the 
preferred version of many, it's already easy to find errata.

There are certainly many open questions when moving to better linking of 
the relevant information, such as "who approves it", "what's 'official' 
(wiki, issue tracker,...) and what not", and so on.


On 2012/08/01 8:27, Barry Leiba wrote:
> We've been seeing a lot of inappropriate errata reports, made by
> well-meaning people who, surely, think their reports are useful, even
> important.  These aren't free: they take time to process, and they form
> clutter in the errata system, obscuring the ones that do fit into what
> errata are meant to be.

These are certainly problems, and we have to work on improving the 
situation. Sending all the errata to the IESG without triage (which 
seems to be done for the "Technical" ones; not sure it's also true for 
the "Editorial" ones) definitely may not be the best for the busy people 
on the IESG to spend their time.

Regards,   Martin.

From paul.hoffman@vpnc.org  Thu Aug  2 07:04:48 2012
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 1E5CE21F85E6; Thu,  2 Aug 2012 07:04:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PVAX+G2yBAaZ; Thu,  2 Aug 2012 07:04:47 -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 6D93A21F8674; Thu,  2 Aug 2012 07:04:47 -0700 (PDT)
Received: from [192.168.0.22] (S01060026f3e16488.vc.shawcable.net [24.84.235.32]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q72DDWZ0014378 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 2 Aug 2012 06:13:33 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: Affirmation of the Modern Global Standards Paradigm
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <501A4139.7050108@gmail.com>
Date: Thu, 2 Aug 2012 07:04:44 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C9D687F1-92C3-40A7-B3C1-7E64A1BE290C@vpnc.org>
References: <04e401cd7055$416aecf0$c440c6d0$@iab.org> <501A4139.7050108@gmail.com>
To: iab@iab.org
X-Mailer: Apple Mail (2.1278)
Cc: ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 14:04:48 -0000

Greetings again. At the plenary last night, Russ said that the expected =
signatories are those three organizations and hopefully other SDOs. =
People active in SDOs other than those three were encouraged to try to =
get those additional SDOs to sign the final wording.

However, it seems like many other organizations could strongly support =
the document and possibly want to do so publicly by becoming =
signatories. There is nothing at the bottom that says "The following =
SDOs are signatories". Is there any intention of letting organizations =
that are not SDOs become signatories? For example, the VPN Consortium =
(which explicitly does no standards development, but tests systems that =
are based on the standards from the IETF) strongly supports what is in =
this document and would want to be a signatory if that was available. I =
imagine other consortia, and probably even vendors, would also want to =
be signatories. It would be useful to hear what non-SDOs who support =
these principles can do to either become signatories or to support the =
document when it is signed by SDOs.

--Paul Hoffman, Director
--VPN Consortium


From barryleiba@gmail.com  Thu Aug  2 07:05:20 2012
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE11321F84EE for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 07:05:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.83
X-Spam-Level: 
X-Spam-Status: No, score=-102.83 tagged_above=-999 required=5 tests=[AWL=-0.153, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BJIAxhtFIQsp for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 07:05:20 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id E1AD621F845B for <ietf@ietf.org>; Thu,  2 Aug 2012 07:05:19 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so8921972vcb.31 for <ietf@ietf.org>; Thu, 02 Aug 2012 07:05:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=4TgASHtsu1wJXrNq9S9wQDKFZfVKELlNonH8Iz5qEwo=; b=Nn6Tw4p1faiLoP0kWAEpm+aCvVeed4+OTjoiHLr1mnJZMGHVxXpMEzpJlAyU1do9s0 prwmUJb6kgF4wmIPY66kswkvzWL23NQpjDPxw/RgwMrWlZdTBcv0+yjAYbJbkXSchGAq RDROBs185TfonYwMOUDsfgWavYjDOmQ0wS2ZbZtx2ZLiurt78mYWUz/D/3C2LodDiU6U hBRxgg5Sc3BbtiSxHTKtbGc2WIrc/vaqheaLL/isXiFJ4Z/q9Kp624kAt00wLJItiffC WN7IjJtvSshoTbSLgQb3RFjO+1F19BLkrqKNfIqMbpTRHvCmOo9TJkVjzHqVf5OVqZ3Y pKDA==
MIME-Version: 1.0
Received: by 10.58.68.163 with SMTP id x3mr9300812vet.41.1343916319353; Thu, 02 Aug 2012 07:05:19 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.220.29.8 with HTTP; Thu, 2 Aug 2012 07:05:19 -0700 (PDT)
In-Reply-To: <501A5656.2050407@it.aoyama.ac.jp>
References: <CALaySJKV96tdXhzfPD1e1Mro_+gp5aDarF7Z06QrA+iQtnHkLw@mail.gmail.com> <501A5656.2050407@it.aoyama.ac.jp>
Date: Thu, 2 Aug 2012 10:05:19 -0400
X-Google-Sender-Auth: 9NGW7Rg1xHp8SUWdgXxpKlalGLw
Message-ID: <CALaySJJUufTeKSoRoqgiBqm0MzDM_h+YQ30hVKVNA0hg--74Sg@mail.gmail.com>
Subject: Re: RFC Errata: when to file, and when not to
From: Barry Leiba <barryleiba@computer.org>
To: =?ISO-8859-1?Q?Martin_J=2E_D=FCrst?= <duerst@it.aoyama.ac.jp>
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: Thu, 02 Aug 2012 14:05:20 -0000

> Thanks for explanation about errata, which must have been caused at least in
> part by an erratum that I submitted recently.

Yours was one of many.  Yours was actually one that I'd like to find a
way to fix -- a URL that needs to be updated.

>> In particular, the errata system is NOT meant to be used as an issue
>> tracker; please do not submit errata reports with the *intent* that they
>> be marked as "Held for Document Update", to be used as an issue
>> list later.  We have mailing lists, issue trackers, and wikis for this purpose.
>
> Of course we have mailing lists, issue trackers, and wikis, but the problem
> is that none of them are for RFCs. And if there's a tracker for a bis
> version, it's not necessarily easy to find from the RFC.

Yes, and we're working on that.  We're looking into ways of handling
this, to provide some sort of issue tracking for RFCs.  Not sure yet
what the right way to do it is.

Barry

From joelja@bogus.com  Thu Aug  2 07:14:58 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4152521F8683 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 07:14:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.487
X-Spam-Level: 
X-Spam-Status: No, score=-102.487 tagged_above=-999 required=5 tests=[AWL=0.113, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JHMG8GKY1pzz for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 07:14:57 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 2CB8421F8682 for <ietf@ietf.org>; Thu,  2 Aug 2012 07:14:56 -0700 (PDT)
Received: from dhcp-4475.meeting.ietf.org (dhcp-4475.meeting.ietf.org [130.129.68.117]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q72EEoor068826 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 2 Aug 2012 14:14:51 GMT (envelope-from joelja@bogus.com)
Message-ID: <501A8B5B.2070609@bogus.com>
Date: Thu, 02 Aug 2012 07:14:51 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120717 Thunderbird/15.0
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com> <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com> <CADnDZ8-6iTjav+utqDOXriKc3FUVesHAy0CD5FtFQjrWDMvuWA@mail.gmail.com> <CAPv4CP-LBGVPn9O5N1HmbUqw8H7dpK66q7JEcrYA_Sd395giCA@mail.gmail.com>
In-Reply-To: <CAPv4CP-LBGVPn9O5N1HmbUqw8H7dpK66q7JEcrYA_Sd395giCA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 02 Aug 2012 14:14:51 +0000 (UTC)
Cc: Barry Leiba <barryleiba@computer.org>, ietf <ietf@ietf.org>, Abdussalam Baryun <abdussalambaryun@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 14:14:58 -0000

On 8/1/12 10:48 AM, Scott Brim wrote:
> On Wed, Aug 1, 2012 at 10:05 AM, Abdussalam Baryun
> <abdussalambaryun@gmail.com> wrote:
>> It is solving the problem of specifications that don't specify
>> conditions in a easy manner that implementers/users need. Please note
>> that "IF THEN" is reducing the number of words in the draft as well
>> (more efficient). Please tell me what specification can specify a
>> conditional situation in less words than "IF, THEN". Many RFC don't
>> follow the easy way properly,
A Change to the interpretation of normative language does not 
retroactively apply to existing documents.
>> Yes but that's an editing issue.  Go look at how process documentation
>> and state machines are handled in serious protocol RFCs.  Some do use
>> if/then in a formal way, but some are just informative.  The purpose
>> of 2119 is clarity of terminology.  Everyone knows what "if" and
>> "then" mean - your concern is how they are used.  The way to fix that
>> is in the particular drafts you have an issue with.
>>


From daedulus@btconnect.com  Thu Aug  2 07:31:25 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D23B21F86B7 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 07:31:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.681
X-Spam-Level: 
X-Spam-Status: No, score=-3.681 tagged_above=-999 required=5 tests=[AWL=-0.082, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EFomhJlQmddU for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 07:31:24 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe006.messaging.microsoft.com [216.32.181.186]) by ietfa.amsl.com (Postfix) with ESMTP id 7F1AC21F86B8 for <ietf@ietf.org>; Thu,  2 Aug 2012 07:31:24 -0700 (PDT)
Received: from mail139-ch1-R.bigfish.com (10.43.68.249) by CH1EHSOBE013.bigfish.com (10.43.70.63) with Microsoft SMTP Server id 14.1.225.23; Thu, 2 Aug 2012 14:31:23 +0000
Received: from mail139-ch1 (localhost [127.0.0.1])	by mail139-ch1-R.bigfish.com (Postfix) with ESMTP id 1DDF82002B6; Thu,  2 Aug 2012 14:31:23 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.224.141; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0702HT010.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -24
X-BigFish: PS-24(zz98dI9371I542M1432Izz1202hzz1033IL8275bh8275dhz2dh2a8h5a9h668h839hd24hf0ah107ah304l)
Received: from mail139-ch1 (localhost.localdomain [127.0.0.1]) by mail139-ch1 (MessageSwitch) id 1343917880378434_13650; Thu,  2 Aug 2012 14:31:20 +0000 (UTC)
Received: from CH1EHSMHS011.bigfish.com (snatpool3.int.messaging.microsoft.com [10.43.68.226])	by mail139-ch1.bigfish.com (Postfix) with ESMTP id 588D23400C8;	Thu,  2 Aug 2012 14:31:20 +0000 (UTC)
Received: from DB3PRD0702HT010.eurprd07.prod.outlook.com (157.55.224.141) by CH1EHSMHS011.bigfish.com (10.43.70.11) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 2 Aug 2012 14:31:19 +0000
Received: from BL2PRD0310HT005.namprd03.prod.outlook.com (157.56.240.21) by pod51017.outlook.com (10.3.4.178) with Microsoft SMTP Server (TLS) id 14.15.86.1; Thu, 2 Aug 2012 14:31:14 +0000
Message-ID: <00f201cd70ba$ddaf65e0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Russ Housley <housley@vigilsec.com>
References: <CDF73C59-A8E8-43B4-B67D-34CFAF541DB6@ietf.org><EDC652A26FB23C4EB6384A4584434A0407E24097@307622ANEX5.global.avaya.com> <6E526B78-44AD-44F3-A5FB-F42D3DBEE4B0@vigilsec.com>
Subject: Re: Draft IESG Statement Regarding Ethertype Requests
Date: Thu, 2 Aug 2012 15:26:47 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.240.21]
X-OriginatorOrg: btconnect.com
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 14:31:25 -0000

What is the position of the IRTF on this?

Tom Petch


----- Original Message -----
From: "Russ Housley" <housley@vigilsec.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Cc: "IETF" <ietf@ietf.org>
Sent: Monday, July 30, 2012 11:53 PM

Dan:

Only protocol specifications make use of Ethertypes.  The statement is
intended to apply to any protocol specification on the IETF Stream
(Standards Track RFC, Informational RFC, or Experimental RFC) that needs
to allocate a new Ethertype.

Russ


On Jul 30, 2012, at 5:20 PM, Romascanu, Dan (Dan) wrote:

>
>
> (I hope not to open some Pandora box or a long thread - my goal is to
> make sure there is clarity in the language of the statement)
>
> What 'IETF protocol specification' means here?
>
> Pretty clear it covers protocols defined in IETF standards-track
> documents.
>
> Does it also cover protocols defined (described) in Informational RFCs
> which are part of the IETF stream?
>
> Dan
>
>
>> -----Original Message-----
>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>> bounces@ietf.org] On Behalf Of IETF Chair
>> Sent: Monday, July 30, 2012 7:40 PM
>> To: IETF Announce
>> Cc: IETF
>> Subject: Draft IESG Statement Regarding Ethertype Requests
>>
>> Last week the IAB and the IESG met with the leadership of IEEE 802.
> One
>> of the things that was discussed was the IEEE policies for allocating
>> EtherTypes, and the IESG is considering the attached IESG Statement
to
>> implement an IETF policy that aligns with the IEEE policy.
>>
>> If you have an comments on this proposed policy, please raise them on
>> ietf@ietf.org.
>>
>> Russ
>>
>> = = = = = =
>>
>> The IEEE Registration Authority Committee (RAC) assigns Ethertypes.
>> (See http://standards.ieee.org/develop/regauth/ethertype/.)  Some
IETF
>> protocol specification make use of Ethertypes.  Since Ethertypes are
a
>> fairly scarce resource, the IEEE RAC will not assign an Ethertype to
a
>> new IETF protocol specification that needs a new Ethertype until the
>> IESG has approved the specification for publication as an RFC.
>>
>> To let the IEEE RAC know that the IESG has approved an IETF protocol
>> specification for publication, all future requests for assignment of
>> Ethertypes for IETF protocol specifications will be made by the IESG.
>>
>> Note that playpen Ethertypes have been assigned in IEEE 802 [1] for
> use
>> during development and experimentation.
>>
>>
>> [1] IEEE Std 802a-2003 (Amendment to IEEE Std 802-2001).
>>    IEEE standard for Local and Metropolitan Area Networks:
>>    Overview and Architecture -- Amendment 1: Ethertypes for
>>    Prototype and Vendor-Specific Protocol Development.




From randy@psg.com  Thu Aug  2 07:32:58 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E596911E80B8 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 07:32:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.519
X-Spam-Level: 
X-Spam-Status: No, score=-2.519 tagged_above=-999 required=5 tests=[AWL=0.080,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L4RI+0mMkOM4 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 07:32:58 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 8514F11E80A5 for <ietf@ietf.org>; Thu,  2 Aug 2012 07:32:58 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SwwSQ-0006DB-3A; Thu, 02 Aug 2012 14:32:58 +0000
Date: Thu, 02 Aug 2012 07:32:58 -0700
Message-ID: <m28vdxwehx.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: joel jaeggli <joelja@bogus.com>
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
In-Reply-To: <501A8B5B.2070609@bogus.com>
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com> <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com> <CADnDZ8-6iTjav+utqDOXriKc3FUVesHAy0CD5FtFQjrWDMvuWA@mail.gmail.com> <CAPv4CP-LBGVPn9O5N1HmbUqw8H7dpK66q7JEcrYA_Sd395giCA@mail.gmail.com> <501A8B5B.2070609@bogus.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 14:32:59 -0000

> A Change to the interpretation of normative language does not
> retroactively apply to existing documents.

welcome to the 21st century.  the ietf has become a shiny thing (thanks
jc) which attracts.  many do not understand the technology, computer
science, engineering, ...  but they do understand process politics.
[politely] ignore their fumblings, focus on real work, and endure.

randy

From yoshihiro.ohba@toshiba.co.jp  Thu Aug  2 07:36:41 2012
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15E6E11E80C5 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 07:36:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.089
X-Spam-Level: 
X-Spam-Status: No, score=-8.089 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_HI=-8, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0ieX4aRuasoZ for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 07:36:40 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by ietfa.amsl.com (Postfix) with ESMTP id 292E811E80BF for <ietf@ietf.org>; Thu,  2 Aug 2012 07:36:40 -0700 (PDT)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp  with ESMTP id q72EaciJ007959; Thu, 2 Aug 2012 23:36:38 +0900 (JST)
Received: (from root@localhost) by arc11.toshiba.co.jp  id q72EablD021456; Thu, 2 Aug 2012 23:36:37 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148]  by arc11.toshiba.co.jp with ESMTP id ZAA21455; Thu, 2 Aug 2012 23:36:37 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp  with ESMTP id q72Eabha009073; Thu, 2 Aug 2012 23:36:37 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id q72EabjO025157; Thu, 2 Aug 2012 23:36:37 +0900 (JST)
Received: from [133.199.16.155] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0M8400C66TWZN090@mail.po.toshiba.co.jp>; Thu, 02 Aug 2012 23:36:37 +0900 (JST)
Date: Thu, 02 Aug 2012 23:36:39 +0900
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
Subject: Re: NomCom 2012-2013: Third Call for Volunteers
In-reply-to: <alpine.BSF.2.00.1208020132140.96564@fledge.watson.org>
To: Samuel Weiler <weiler@watson.org>
Message-id: <501A9077.5020501@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-2022-JP
Content-transfer-encoding: 7bit
References: <20120731044425.12307.52108.idtracker@ietfa.amsl.com> <alpine.BSF.2.00.1208011848500.88006@fledge.watson.org> <3B46F876-010A-4C9D-9CC4-704211939459@frobbit.se> <501A0BDB.2040501@toshiba.co.jp> <alpine.BSF.2.00.1208020132140.96564@fledge.watson.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 14:36:41 -0000

Probably nothing can be perfect when defining "affiliation", but I
think some definition can help reducing hidden conflict of interests.

Here is an example in other standards body:
http://standards.ieee.org/faqs/affiliation.html

Yoshihiro Ohba

(2012/08/02 14:37), Samuel Weiler wrote:
> On Thu, 2 Aug 2012, Yoshihiro Ohba wrote:
> 
>> What is the exact definition of "affiliation" in IETF?
> 
> Quoting from RFC3777:
> 
> "Rather than defining precise rules for how to define "affiliation", 
> the IETF community depends on the honor and integrity of the 
> participants to make the process work."
> 
> As a community, we recognize that this could easily be gamed, and we 
> expect each other to behave reasonably.
> 
>> If a consultant who runs his/her own consulting company X is paid by 
>> his/her customer company Y for his/her IETF activities including 
>> NOMCOM activity, then what is his/her affiliation?
> 
> As a first pass answer, it's whatever the consultant would normally 
> show on a meeting registration badge.  Typically, I'd expect X.  But 
> the degree of funding is as extreme as you describe, it might still be 
> appropriate to step aside if two persons from Y are also chosen (or 
> ask one of them to step aside).
> 
> -- Sam
> 


From randy@psg.com  Thu Aug  2 07:50:57 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDC2121F8680 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 07:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.523
X-Spam-Level: 
X-Spam-Status: No, score=-2.523 tagged_above=-999 required=5 tests=[AWL=0.076,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3HNU1kXcpmZo for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 07:50:56 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 2E06521F867F for <ietf@ietf.org>; Thu,  2 Aug 2012 07:50:56 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Swwjn-0006FN-71; Thu, 02 Aug 2012 14:50:55 +0000
Date: Thu, 02 Aug 2012 07:50:55 -0700
Message-ID: <m26291wdo0.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
Subject: Re: NomCom 2012-2013: Third Call for Volunteers
In-Reply-To: <501A9077.5020501@toshiba.co.jp>
References: <20120731044425.12307.52108.idtracker@ietfa.amsl.com> <alpine.BSF.2.00.1208011848500.88006@fledge.watson.org> <3B46F876-010A-4C9D-9CC4-704211939459@frobbit.se> <501A0BDB.2040501@toshiba.co.jp> <alpine.BSF.2.00.1208020132140.96564@fledge.watson.org> <501A9077.5020501@toshiba.co.jp>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 14:50:57 -0000

> Here is an example in other standards body:
> http://standards.ieee.org/faqs/affiliation.html

thank you for reminding me of where i do not want to go.

the ietf culture presumes the players are adults.  yes, this has
occasional failures, perhaps i am one.  but better that than massive
rules which do not actually stop the really egregious abuses.

a 40 page contract drawn up by the lawyers does not ensure a meeting
of the minds, let alone the hearts.

randy

From superuser@gmail.com  Thu Aug  2 08:47:56 2012
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B416D21F8622 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 08:47:56 -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.065, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wlSd+lcpFrV2 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 08:47:56 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id D6A7E21F8620 for <ietf@ietf.org>; Thu,  2 Aug 2012 08:47:55 -0700 (PDT)
Received: by lagv3 with SMTP id v3so5650488lag.31 for <ietf@ietf.org>; Thu, 02 Aug 2012 08:47:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=R3PSyb+WicVaD6aaplr8nGyFmUOonhfARZvqsVsa0OE=; b=TMXQV0NkPBWXbBpEzM39DZZQmx+EIfr0lz11M+/P/RCODBoYWA+8bWSiHbrhsi7rpX M/HKYKnoAkdKyQa4bPGthEohP3cUEl6BUL2BEmWGdOPqlg7fNalCE0Nh9vGa5E0L/ppc TecFocuJ3kIT4s3Jn1otmuC2PN0Wm7KBSt6It2+YRdmv/aNFog2xrqwxfGSvwwIH772g LGUwZhJSnN+Ow/nUk2sez0mDM1T/WVDLW3hyVv6pfZSsAKPPGMkKyRZ0DLyhC0BD8g7s C/LhTJEi+4WuTkhW226smr3yuZRZXVVMDL6UdNilM6QsZgehlIe01P5EC/PKtMNUECzq GuPg==
MIME-Version: 1.0
Received: by 10.152.112.138 with SMTP id iq10mr22099063lab.13.1343922474701; Thu, 02 Aug 2012 08:47:54 -0700 (PDT)
Received: by 10.112.89.3 with HTTP; Thu, 2 Aug 2012 08:47:54 -0700 (PDT)
In-Reply-To: <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com>
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com> <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com>
Date: Thu, 2 Aug 2012 08:47:54 -0700
Message-ID: <CAL0qLwbgbtBWGWpV2DL9H2ac94S6cZor_dp77c_Z7YV_eAm+aw@mail.gmail.com>
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary=f46d0408da07b5d4b604c64a5523
Cc: ietf <ietf@ietf.org>, Abdussalam Baryun <abdussalambaryun@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 15:47:56 -0000

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

On Wed, Aug 1, 2012 at 9:03 AM, Barry Leiba <barryleiba@computer.org> wrote:

> I written this draft starting a RFC2119 update for the reasons of
>> discussion threads in [1] and [2]. Please check draft and feedback,
>> thanking you.
>>
>
> I agree with what Paul and Melinda have said.  This document is pointless,
> as there is no actual problem that it's solving and no misunderstanding
> that it's clarifying.  Further, it's actively *harmful*.  It's arguable
> that 2119 already reserves too many words by giving them specific,
> normative meanings (SHALL *and* MUST; SHOULD *and* RECOMMENDED).  Adding
> IF, THEN, and ELSE would not only be unnecessary, but downright *bad*.
>
>
>
If I may quote Blazing Saddles:

Reverend!

("+1", for those unfamiliar.)

-MSK

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

On Wed, Aug 1, 2012 at 9:03 AM, Barry Leiba <span dir=3D"ltr">&lt;<a href=
=3D"mailto:barryleiba@computer.org" target=3D"_blank">barryleiba@computer.o=
rg</a>&gt;</span> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">
<div class=3D"im"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">I written this draft start=
ing a RFC2119 update for the reasons of<br>
discussion threads in [1] and [2]. Please check draft and feedback,<br>
thanking you.<br>
</blockquote><div><br></div></div><div>I agree with what Paul and Melinda h=
ave said. =A0This document is pointless, as there is no actual problem that=
 it&#39;s solving and no misunderstanding that it&#39;s clarifying. =A0Furt=
her, it&#39;s actively *harmful*. =A0It&#39;s arguable that 2119 already re=
serves too many words by giving them specific, normative meanings (SHALL *a=
nd* MUST; SHOULD *and* RECOMMENDED). =A0Adding IF, THEN, and ELSE would not=
 only be unnecessary, but downright *bad*.</div>
<span class=3D"HOEnZb"><font color=3D"#888888">
<div><br><br></div></font></span></blockquote><div><br>If I may quote Blazi=
ng Saddles:<br><br>Reverend!<br><br>(&quot;+1&quot;, for those unfamiliar.)=
<br><br>-MSK <br></div></div><br>

--f46d0408da07b5d4b604c64a5523--

From superuser@gmail.com  Thu Aug  2 09:02:44 2012
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85C3721E803D for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 09:02:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.662
X-Spam-Level: 
X-Spam-Status: No, score=-3.662 tagged_above=-999 required=5 tests=[AWL=-0.064, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JuBl7mZ-4Orr for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 09:02:44 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id B05D821E803C for <ietf@ietf.org>; Thu,  2 Aug 2012 09:02:43 -0700 (PDT)
Received: by lagv3 with SMTP id v3so5659297lag.31 for <ietf@ietf.org>; Thu, 02 Aug 2012 09:02:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YuZ00eU8XUr0TBwa38h682FDQAwh5BViLTeX6oON/eY=; b=hhEJHnAjMMgxqb7LVSoew70GeQLFC67eq0sq1K4wC14uP/d3GZb+XdUU/n6weA0YbW 3qNtzN2Rh2fWIwNnrl8/udCzRAW2ZlYD+1sB0vpy76M+4YSVLMRD6JmtjpcwQueJR4gt OxLishLH1dOziKjg0XdCehSdVEl9YaMGqPuklUd1CDMM7n9k1Pos442VCy/0AFBOhIvH 5aRxVXGOIF2M8hMifDWyRtN6tPdUxP+I+yQbg1vkj+n9uNBTflatP9WmUd+2iM9wMT6B IVIol8vcdx6c6inlzAic+h0uboZXUqgxwq9qORXVuQOB/nPMz/WjVMEYTvgrCHki+cDF 65nA==
MIME-Version: 1.0
Received: by 10.112.49.100 with SMTP id t4mr9758087lbn.10.1343923362664; Thu, 02 Aug 2012 09:02:42 -0700 (PDT)
Received: by 10.112.89.3 with HTTP; Thu, 2 Aug 2012 09:02:42 -0700 (PDT)
In-Reply-To: <CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com>
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com> <CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com>
Date: Thu, 2 Aug 2012 09:02:42 -0700
Message-ID: <CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com>
Subject: Re: New Version Notification for draft-leiba-extended-doc-shepherd-00.txt
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary=bcaec554d63ca311ae04c64a8a87
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 16:02:44 -0000

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

On Wed, Aug 1, 2012 at 11:01 PM, Barry Leiba <barryleiba@computer.org>wrote:

> I've posted my thoughts on starting document shepherding at the time a
> document first starts its life in a working group, and on the tasks a
> shepherd might perform at each stage in the document's life.  I intend
> to pursue having this published as an Informational document, not a
> BCP, reflecting my personal opinion.  That said, I'm interested in
> comments, and might make changes accordingly.
>
>
If this piques anyone's interest, we will be trying what Barry's suggesting
in APPSAWG.  Ask us in a few months how well it's working.

-MSK

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

On Wed, Aug 1, 2012 at 11:01 PM, Barry Leiba <span dir=3D"ltr">&lt;<a href=
=3D"mailto:barryleiba@computer.org" target=3D"_blank">barryleiba@computer.o=
rg</a>&gt;</span> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">
I&#39;ve posted my thoughts on starting document shepherding at the time a<=
br>
document first starts its life in a working group, and on the tasks a<br>
shepherd might perform at each stage in the document&#39;s life. =A0I inten=
d<br>
to pursue having this published as an Informational document, not a<br>
BCP, reflecting my personal opinion. =A0That said, I&#39;m interested in<br=
>
comments, and might make changes accordingly.<br>
<br></blockquote><div><br>If this piques anyone&#39;s interest, we will be =
trying what Barry&#39;s suggesting in APPSAWG.=A0 Ask us in a few months ho=
w well it&#39;s working.<br><br>-MSK <br></div></div><br>

--bcaec554d63ca311ae04c64a8a87--

From superuser@gmail.com  Thu Aug  2 09:05:15 2012
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92B7821F8602 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 09:05:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.662
X-Spam-Level: 
X-Spam-Status: No, score=-3.662 tagged_above=-999 required=5 tests=[AWL=-0.064, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5LUqsfEiSmjo for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 09:05:15 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id C37A821F85EF for <ietf@ietf.org>; Thu,  2 Aug 2012 09:05:14 -0700 (PDT)
Received: by lagv3 with SMTP id v3so5660776lag.31 for <ietf@ietf.org>; Thu, 02 Aug 2012 09:05:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=RQv6KOQDZgkdE5HFZiLHaWktza3crNVS7oULGFGivkY=; b=LyLDMjohHlmL+otMEEHevTjvV4o0p/y50/4nuGO/tmLuz3T0Q3N8gZ12dZtygW49yQ RlLSUpAm1H2enYg1ZJz/W8DVdJcS/NgESN4m0YEz5dDK9uGorfsOHRIw5dNjmuf1t/fl +6x77+12kxOkB4IyW5vOe8kqT+NQfVzXa0Ggs3nxt+n66O5r0dOhhQq7FpNfBrTGMkQl CC2TUTeaajStfF3NgeZpNFuX0jf3kC4ZYO11zBX+z4aDbxo4CL3EtUrvtiWbKCjcughi 31kzFgBuXyUIpkoCUsT/6eamVav7XieJ6eW2vQZZ9lFON3D2WVgUhQA2O5U9HOAbITyg Ev7Q==
MIME-Version: 1.0
Received: by 10.152.112.233 with SMTP id it9mr21840129lab.40.1343923513729; Thu, 02 Aug 2012 09:05:13 -0700 (PDT)
Received: by 10.112.89.3 with HTTP; Thu, 2 Aug 2012 09:05:13 -0700 (PDT)
In-Reply-To: <1343593068.9245.0.camel@gwz-laptop>
References: <501531F7.5040404@gmail.com> <6.2.5.6.2.20120729073422.06d8fe10@resistor.net> <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net> <1343593068.9245.0.camel@gwz-laptop>
Date: Thu, 2 Aug 2012 09:05:13 -0700
Message-ID: <CAL0qLwbEquWAxFGmLq+xpRApsOMURgNvsetQzpcj_BxEnBMMFQ@mail.gmail.com>
Subject: Re: Oauth blog post
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Glen Zorn <glenzorn@gmail.com>
Content-Type: multipart/alternative; boundary=f46d040838d3a4223804c64a9366
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 16:05:15 -0000

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

On Sun, Jul 29, 2012 at 1:17 PM, Glen Zorn <glenzorn@gmail.com> wrote:

> **
>
> Do you think that corporate domination of "open" standards development is
> OK?
>
>
Do you think that's actually what we do around here?  I can think of
counterexamples if you need some.

-MSK

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

On Sun, Jul 29, 2012 at 1:17 PM, Glen Zorn <span dir=3D"ltr">&lt;<a href=3D=
"mailto:glenzorn@gmail.com" target=3D"_blank">glenzorn@gmail.com</a>&gt;</s=
pan> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<u></u>


 =20
 =20

<div><div><div class=3D"h5">
<br></div></div>
Do you think that corporate domination of &quot;open&quot; standards develo=
pment is OK?<br>
<br>
</div>

</blockquote></div><br>Do you think that&#39;s actually what we do around h=
ere?=A0 I can think of counterexamples if you need some.<br><br>-MSK<br>

--f46d040838d3a4223804c64a9366--

From superuser@gmail.com  Thu Aug  2 09:13:10 2012
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBB9D21F8669 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 09:13:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.661
X-Spam-Level: 
X-Spam-Status: No, score=-3.661 tagged_above=-999 required=5 tests=[AWL=-0.063, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 35TlGZIzh8xq for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 09:13:10 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id DC5D621F85F3 for <ietf@ietf.org>; Thu,  2 Aug 2012 09:13:09 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so1155938lbb.31 for <ietf@ietf.org>; Thu, 02 Aug 2012 09:13:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Pz0w0c+tqVD4crKrkPOSPeTyhaD3upxIAqjxrzqzQGU=; b=noojYMmfW47XH+YlH/Y9+cdkokUV4tmKCntQnAklWcti8qXVK/dNP1/Zo+N423BYS9 liNWeL4NCz/+dcvCTCIsXpXznEksbP1FH6OkEEYAgatqyKd34Sl3Y+p+bmxDwGaY7c4f h7BEEs+f2CZY7YrHo9fH9XNkUTE+7ytXFDFDE1FbJei+atlS8a6sSaCPcOBUesI1DkCv P23g3icJiMCnEfK95tAVpAEx52Ndnf8agzr6TjjTqyrJo96kKTdI5jYB7oFPOVYwYrJO PZIQOrHrg8ZrFsAIgNZdd8fTWNTRsndr5J8HF2Qhv0cmbbNg94nTWzf09pC7pcjR5CjG 3Cgg==
MIME-Version: 1.0
Received: by 10.112.40.231 with SMTP id a7mr503007lbl.67.1343923988700; Thu, 02 Aug 2012 09:13:08 -0700 (PDT)
Received: by 10.112.89.3 with HTTP; Thu, 2 Aug 2012 09:13:08 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20120730101231.047f2550@resistor.net>
References: <501531F7.5040404@gmail.com> <6.2.5.6.2.20120729073422.06d8fe10@resistor.net> <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net> <6.2.5.6.2.20120730101231.047f2550@resistor.net>
Date: Thu, 2 Aug 2012 09:13:08 -0700
Message-ID: <CAL0qLwYNRW6FSC4kMQkn81+4HgKdv591D43Z31rLAg3ArRsSZg@mail.gmail.com>
Subject: Re: Oauth blog post
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=485b390f7cfef39d5204c64aaf10
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 16:13:11 -0000

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

On Mon, Jul 30, 2012 at 10:21 AM, SM <sm@resistor.net> wrote:

> Hi Hannes,
>
> At 12:19 PM 7/29/2012, Hannes Tschofenig wrote:
>
>> The IETF allows open participation and, as such, everyone, including
>> companies that develop enterprise software, are free to participate in the
>> discussions.
>>
>> Do you think open participation is wrong?
>>
>
> It depends on what open participation means in the above.  If it is open
> participation by companies, I don't have any problem with it as long as the
> relevant BCPs are updated to reflect that.


I think it's impossible to determine with certainty whether someone
standing at the mic and asserting a position is doing so based on what an
employer is insisting on doing, or that person's opinion.

We purport to participate as individuals.  It's entirely possible that a
person's opinion happens to concur with her employer's opinion rather than
being told what to say.  Does that mean the corporation is the participant
and not the person?

So when I hear these sorts of allegations of corporate domination of the
standards process, I have to wonder how true they are.  I have a pretty big
corporate name on my badge this time, but I'm not here pushing any specific
agenda I was given.

-MSK

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

On Mon, Jul 30, 2012 at 10:21 AM, SM <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:sm@resistor.net" target=3D"_blank">sm@resistor.net</a>&gt;</span> wrote:<=
br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Hannes,<div class=3D"im"><br>
At 12:19 PM 7/29/2012, Hannes Tschofenig wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The IETF allows open participation and, as such, everyone, including compan=
ies that develop enterprise software, are free to participate in the discus=
sions.<br>
<br>
Do you think open participation is wrong?<br>
</blockquote>
<br></div>
It depends on what open participation means in the above. =A0If it is open =
participation by companies, I don&#39;t have any problem with it as long as=
 the relevant BCPs are updated to reflect that.</blockquote><div><br>I thin=
k it&#39;s impossible to determine with certainty whether someone standing =
at the mic and asserting a position is doing so based on what an employer i=
s insisting on doing, or that person&#39;s opinion.<br>
<br>We purport to participate as individuals.=A0 It&#39;s entirely possible=
 that a person&#39;s opinion happens to concur with her employer&#39;s opin=
ion rather than being told what to say.=A0 Does that mean the corporation i=
s the participant and not the person?<br>
<br>So when I hear these sorts of allegations of corporate domination of th=
e standards process, I have to wonder how true they are.=A0 I have a pretty=
 big corporate name on my badge this time, but I&#39;m not here pushing any=
 specific agenda I was given.<br>
<br>-MSK</div></div><br>

--485b390f7cfef39d5204c64aaf10--

From robert@raszuk.net  Thu Aug  2 09:25:06 2012
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 9AD3121F85CD for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 09:25:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.534
X-Spam-Level: 
X-Spam-Status: No, score=-1.534 tagged_above=-999 required=5 tests=[AWL=-0.227, BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aCIG2B6BGUFt for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 09:25:06 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id BE04321F84F6 for <ietf@ietf.org>; Thu,  2 Aug 2012 09:25:05 -0700 (PDT)
Received: (qmail 25561 invoked by uid 399); 2 Aug 2012 16:25:04 -0000
Received: from unknown (HELO ?130.129.17.10?) (pbs:robert@raszuk.net@130.129.17.10) by mail1310.opentransfer.com with ESMTPM; 2 Aug 2012 16:25:04 -0000
X-Originating-IP: 130.129.17.10
Message-ID: <501AA9DF.6010208@raszuk.net>
Date: Thu, 02 Aug 2012 18:25:03 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Basic ietf process question ...
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com> <CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com> <CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com>
In-Reply-To: <CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Thu, 02 Aug 2012 16:25:06 -0000

All,

IETF documents have number of mandatory sections .. IANA Actions, 
Security Considerations, Refs, etc ...

Does anyone have a good reason why any new protocol definition or 
enhancement does not have a build in mandatory "XML schema" section 
which would allow to actually use such standards based enhancement in 
vendor agnostic way ?

There is a lot of talk about reinventing APIs, building network wide OS 
platform, delivering SDNs (whatever it means at any point of time for 
one) ... but how about we start with something very basic yet IMHO 
necessary to slowly begin thinking of network as one plane.

I understand that historically we had/still have SNMP however I have 
never seen this being mandatory section of any standards track document. 
Usually SNMP comes 5 years behind (if at all) making it obsolete by design.

NETCONF is great and very flexible communication channel for 
provisioning. However it is sufficient to just look at number of ops 
lists to see that those who tried to use it quickly abandoned their 
efforts due to complete lack of XML schema from each vendor they happen 
to use or complete mismatch of vendor to vendor XML interpretation.

And while perhaps this is obvious I do not think that any new single 
effort will address this. This has to be an atomic and integral part of 
each WG's document.

Looking forward for insightful comments ...

Best,
R.



From randy@psg.com  Thu Aug  2 09:31:34 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFFAF21F842E for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 09:31:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.526
X-Spam-Level: 
X-Spam-Status: No, score=-2.526 tagged_above=-999 required=5 tests=[AWL=0.073,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FJZj3SHD6rCw for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 09:31:34 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 646A921F842B for <ietf@ietf.org>; Thu,  2 Aug 2012 09:31:34 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SwyJB-0006Vs-S7; Thu, 02 Aug 2012 16:31:33 +0000
Date: Thu, 02 Aug 2012 09:31:33 -0700
Message-ID: <m2k3xhuufu.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Robert Raszuk <robert@raszuk.net>
Subject: Re: Basic ietf process question ...
In-Reply-To: <501AA9DF.6010208@raszuk.net>
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com> <CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com> <CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com> <501AA9DF.6010208@raszuk.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: Thu, 02 Aug 2012 16:31:35 -0000

hi robert

> Does anyone have a good reason why any new protocol definition or 
> enhancement does not have a build in mandatory "XML schema" section 
> which would allow to actually use such standards based enhancement in 
> vendor agnostic way ?

xml is just a way to package the incompatibilities.  just as mime is a
way to codify incompatibility.

randy

From iad@ietf.org  Thu Aug  2 09:45:51 2012
Return-Path: <iad@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 862A221E804B; Thu,  2 Aug 2012 09:45:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e1RWPWkfDC8d; Thu,  2 Aug 2012 09:45:51 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E2E221E8040; Thu,  2 Aug 2012 09:45:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Proposed IETF 95 Date Change
X-Test-IDTracker: no
X-IETF-IDTracker: 4.33
Message-ID: <20120802164551.20569.2082.idtracker@ietfa.amsl.com>
Date: Thu, 02 Aug 2012 09:45:51 -0700
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 16:45:51 -0000

A reminder of the 6 August deadline for input.
Thanks

The IAOC is seeking community feedback on a proposed date change for IETF 95
scheduled for March 2016.

Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27 March is E=
aster.

The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 and wou=
ld like =

feedback on those dates before making a decision.  Comments appreciated to =
ietf@ietf.org =

by 6 August 2012.

Ray Pelletier
IETF Administrative Director

From iad@ietf.org  Thu Aug  2 09:47:18 2012
Return-Path: <iad@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B17BF11E814D; Thu,  2 Aug 2012 09:47:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QAZv15CfnrUe; Thu,  2 Aug 2012 09:47:17 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C611311E812E; Thu,  2 Aug 2012 09:47:17 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Draft Fees for Processing Legal Requests Policy
X-Test-IDTracker: no
X-IETF-IDTracker: 4.33
Message-ID: <20120802164717.20616.13622.idtracker@ietfa.amsl.com>
Date: Thu, 02 Aug 2012 09:47:17 -0700
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 16:47:19 -0000

A reminder of the deadline of 6 August for input.
Thanks

The IAOC is seeking community feedback on a proposed policy by the IAOC to =
impose =

fees to produce information and authenticate documents in response to subpo=
enas and =

other legal requests.

The IETF receives requests for information, documentation, authentication o=
r other =

matters through subpoenas and less formal means that require manpower and m=
aterials =

to be expended.  These requests are on the rise. During the period 2005 to =
2010 the IETF =

responded to nine subpoenas.  Since 2011 the IETF has received five subpoen=
as and three =

other legal requests for authenticated documents.  =


Each such request is time sensitive and involves the IETF Counsel, the IAD,=
 and members =

of the IAOC, who together form the Legal Management Committee, to rapidly a=
nalyze and =

identify the means for satisfying the request.  Often there is a need to re=
tain outside counsel, =

especially in cases that might lead to depositions or court testimony. =


The IAOC believes a Schedule of Fees is an appropriate and reasonable means=
 to recover =

costs associated with such efforts.

The draft policy entitled Draft Fee Policy for Legal Requests can be found =

at: <http://iaoc.ietf.org/policyandprocedures.html>

Before adopting a policy the IAOC would like feedback on this before making=
 a =

decision.  Comments appreciated to ietf@ietf.org by 6 August 2012.

Ray Pelletier
IETF Administrative Director

From olaf@NLnetLabs.nl  Thu Aug  2 09:50:51 2012
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 59AA221E80A9 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 09:50:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZmvyU1EQ4L3l for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 09:50:50 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id CE07111E8151 for <ietf@ietf.org>; Thu,  2 Aug 2012 09:50:49 -0700 (PDT)
Received: from [IPv6:2001:df8::96:c4e3:36f1:5927:3f07] ([IPv6:2001:df8:0:96:c4e3:36f1:5927:3f07]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.5/8.14.4) with ESMTP id q72GocBH097949 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Thu, 2 Aug 2012 18:50:42 +0200 (CEST) (envelope-from olaf@NLnetLabs.nl)
X-DKIM: OpenDKIM Filter v2.5.2 open.nlnetlabs.nl q72GocBH097949
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1343926244; bh=fP0XoSk8gkKfDSgOjpNDu2uiEFQ8Wjfj0DbmagfuEnI=; h=From:Subject:Date:References:To:In-Reply-To; b=dHQWmrJF5E9QDDdSSlMGJTS2jJ7cKhys47nmqkI2bUT0ZOYNf5I/bfE8Y5ePTjDaa P2wxWkOpISbELS02MaCN3c4zYWDV4RGJyhQzXMVvY7fFFN28TvtYzZtnopF0RfeQ68 jureWwm9wMDPfdwU8cX17A2h+fEb9X4EhideqUh0=
From: Olaf Kolkman <olaf@NLnetLabs.nl>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3AA6B8C8-73C0-402F-97D5-75C19070294F"
Message-Id: <8A32C4E1-6585-4708-8A1B-46F615265E13@NLnetLabs.nl>
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: Proposed IETF 95 Date Change
Date: Thu, 2 Aug 2012 09:50:39 -0700
References: <20120802164551.20569.2082.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
In-Reply-To: <20120802164551.20569.2082.idtracker@ietfa.amsl.com>
X-Mailer: Apple Mail (2.1485)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::53]); Thu, 02 Aug 2012 18:50:43 +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: Thu, 02 Aug 2012 16:50:51 -0000

--Apple-Mail=_3AA6B8C8-73C0-402F-97D5-75C19070294F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Aug 2, 2012, at 9:45 AM, IETF Administrative Director <iad@ietf.org> =
wrote:

> The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 =
and would like=20
> feedback on those dates before making a decision. =20


Support.


--Olaf



--Apple-Mail=_3AA6B8C8-73C0-402F-97D5-75C19070294F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Aug 2, 2012, at 9:45 AM, IETF Administrative Director =
&lt;<a href=3D"mailto:iad@ietf.org">iad@ietf.org</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
style=3D"font-family: Monaco; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
display: inline !important; float: none; ">The IAOC is proposing IETF 95 =
be rescheduled for 20 - 25 March 2016 and would like<span =
class=3D"Apple-converted-space">&nbsp;</span></span><br =
style=3D"font-family: Monaco; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
"><span style=3D"font-family: Monaco; font-size: medium; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; display: inline !important; float: none; =
">feedback on those dates before making a decision. =
&nbsp;</span></blockquote><br></div><div><br></div><div>Support.</div><div=
><br></div><div><br></div><div>--Olaf</div><div =
apple-content-edited=3D"true"><br class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Apple-Mail=_3AA6B8C8-73C0-402F-97D5-75C19070294F--

From dromasca@avaya.com  Thu Aug  2 09:59:09 2012
Return-Path: <dromasca@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3527221E80D2; Thu,  2 Aug 2012 09:59:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.425
X-Spam-Level: 
X-Spam-Status: No, score=-103.425 tagged_above=-999 required=5 tests=[AWL=0.174, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xdczt0Xyr5V8; Thu,  2 Aug 2012 09:59:08 -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 1646121E80D1; Thu,  2 Aug 2012 09:59:07 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAFKvGlDGmAcF/2dsb2JhbABFuRiBB4IgAQEBAQMSHgo/DAQCAQgNBAEDAQELBgwLAQYBRQMGCAEBBBMIGodrn2edWItKg2iCPGADm0SKEIJh
X-IronPort-AV: E=Sophos;i="4.77,702,1336363200"; d="scan'208";a="318305461"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 02 Aug 2012 12:54:29 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 02 Aug 2012 12:54:33 -0400
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: Basic ietf process question ...
Date: Thu, 2 Aug 2012 18:59:03 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com>
In-Reply-To: <501AA9DF.6010208@raszuk.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Basic ietf process question ...
Thread-Index: Ac1wy2hzPoZv2TgCQzeKkLeHbDP4+QAAOQGw
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com><CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com><CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com> <501AA9DF.6010208@raszuk.net>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <robert@raszuk.net>
Cc: opsawg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 16:59:09 -0000

Hi,

The OPSAWG/OPSAREA open meeting this afternoon has an item on the agenda
concerning the revision of RFC1052 and discussing a new architecture for
management protocols.=20


My personal take is that no one protocol, or one data modeling language
can match the operational requirements to configure and manage the wide
and wider range of hosts, routers and other network devices that are
used to implement IP networks and protocols. We should be talking
nowadays about a toolset rather than one tool that fits all. However,
this is a discussion that just starts.=20

Regards,

Dan




> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
Of
> Robert Raszuk
> Sent: Thursday, August 02, 2012 7:25 PM
> Cc: ietf@ietf.org
> Subject: Basic ietf process question ...
>=20
> All,
>=20
> IETF documents have number of mandatory sections .. IANA Actions,
> Security Considerations, Refs, etc ...
>=20
> Does anyone have a good reason why any new protocol definition or
> enhancement does not have a build in mandatory "XML schema" section
> which would allow to actually use such standards based enhancement in
> vendor agnostic way ?
>=20
> There is a lot of talk about reinventing APIs, building network wide
OS
> platform, delivering SDNs (whatever it means at any point of time for
> one) ... but how about we start with something very basic yet IMHO
> necessary to slowly begin thinking of network as one plane.
>=20
> I understand that historically we had/still have SNMP however I have
> never seen this being mandatory section of any standards track
document.
> Usually SNMP comes 5 years behind (if at all) making it obsolete by
> design.
>=20
> NETCONF is great and very flexible communication channel for
> provisioning. However it is sufficient to just look at number of ops
> lists to see that those who tried to use it quickly abandoned their
> efforts due to complete lack of XML schema from each vendor they
happen
> to use or complete mismatch of vendor to vendor XML interpretation.
>=20
> And while perhaps this is obvious I do not think that any new single
> effort will address this. This has to be an atomic and integral part
of
> each WG's document.
>=20
> Looking forward for insightful comments ...
>=20
> Best,
> R.
>=20


From robert@raszuk.net  Thu Aug  2 10:12:34 2012
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 5C49721E8045 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 10:12:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.16
X-Spam-Level: 
X-Spam-Status: No, score=-2.16 tagged_above=-999 required=5 tests=[AWL=0.439,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FiYal+v+pMsY for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 10:12:32 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 6BBBB11E8133 for <ietf@ietf.org>; Thu,  2 Aug 2012 10:12:25 -0700 (PDT)
Received: (qmail 24306 invoked by uid 399); 2 Aug 2012 17:12:22 -0000
Received: from unknown (HELO ?130.129.17.10?) (pbs:robert@raszuk.net@130.129.17.10) by mail1310.opentransfer.com with ESMTPM; 2 Aug 2012 17:12:22 -0000
X-Originating-IP: 130.129.17.10
Message-ID: <501AB4F5.7030205@raszuk.net>
Date: Thu, 02 Aug 2012 19:12:21 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Subject: Re: Basic ietf process question ...
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com><CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com><CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com> <501AA9DF.6010208@raszuk.net> <EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: opsawg@ietf.org, 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: Thu, 02 Aug 2012 17:12:35 -0000

Hi Dan,

 > We should be talking
 > nowadays about a toolset rather than one tool that fits all.

Just to clarify what I asked about .. I am not looking for a single tool 
or single protocol to be used to configure everything.

I am asking for small building block like xml schema (or something 
similar) to be part of each new IETF proposal or protocol change. IMHO 
only that can allow any further more fancy abstractions and tools to be 
build and used in practice.

Best regards,
R.



> Hi,
>
> The OPSAWG/OPSAREA open meeting this afternoon has an item on the agenda
> concerning the revision of RFC1052 and discussing a new architecture for
> management protocols.
>
>
> My personal take is that no one protocol, or one data modeling language
> can match the operational requirements to configure and manage the wide
> and wider range of hosts, routers and other network devices that are
> used to implement IP networks and protocols. We should be talking
> nowadays about a toolset rather than one tool that fits all. However,
> this is a discussion that just starts.
>
> Regards,
>
> Dan
>
>
>
>
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
> Of
>> Robert Raszuk
>> Sent: Thursday, August 02, 2012 7:25 PM
>> Cc: ietf@ietf.org
>> Subject: Basic ietf process question ...
>>
>> All,
>>
>> IETF documents have number of mandatory sections .. IANA Actions,
>> Security Considerations, Refs, etc ...
>>
>> Does anyone have a good reason why any new protocol definition or
>> enhancement does not have a build in mandatory "XML schema" section
>> which would allow to actually use such standards based enhancement in
>> vendor agnostic way ?
>>
>> There is a lot of talk about reinventing APIs, building network wide
> OS
>> platform, delivering SDNs (whatever it means at any point of time for
>> one) ... but how about we start with something very basic yet IMHO
>> necessary to slowly begin thinking of network as one plane.
>>
>> I understand that historically we had/still have SNMP however I have
>> never seen this being mandatory section of any standards track
> document.
>> Usually SNMP comes 5 years behind (if at all) making it obsolete by
>> design.
>>
>> NETCONF is great and very flexible communication channel for
>> provisioning. However it is sufficient to just look at number of ops
>> lists to see that those who tried to use it quickly abandoned their
>> efforts due to complete lack of XML schema from each vendor they
> happen
>> to use or complete mismatch of vendor to vendor XML interpretation.
>>
>> And while perhaps this is obvious I do not think that any new single
>> effort will address this. This has to be an atomic and integral part
> of
>> each WG's document.
>>
>> Looking forward for insightful comments ...
>>
>> Best,
>> R.
>>
>
>
>


From jnc@mercury.lcs.mit.edu  Thu Aug  2 10:14:25 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2D7211E8163 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 10:14:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.223
X-Spam-Level: 
X-Spam-Status: No, score=-6.223 tagged_above=-999 required=5 tests=[AWL=0.376,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s0-wLGrmWERa for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 10:14:25 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id E973E11E8133 for <ietf@ietf.org>; Thu,  2 Aug 2012 10:14:24 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 0898618C124; Thu,  2 Aug 2012 13:14:24 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: NomCom 2012-2013: Third Call for Volunteers
Message-Id: <20120802171424.0898618C124@mercury.lcs.mit.edu>
Date: Thu,  2 Aug 2012 13:14:24 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 17:14:25 -0000

    > From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>

    > Probably nothing can be perfect when defining "affiliation", but I
    > think some definition can help reducing hidden conflict of interests.

I suspect that unless it is done very carefully, any more extensive definition
is simply going to open additional potential loopholes, in the additional
text. Just say something very non-specific "affiliation (interpreted as
broadly as possible)", and leave it at that.

	Noel

From dromasca@avaya.com  Thu Aug  2 10:16:25 2012
Return-Path: <dromasca@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0408821F8652; Thu,  2 Aug 2012 10:16:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.426
X-Spam-Level: 
X-Spam-Status: No, score=-103.426 tagged_above=-999 required=5 tests=[AWL=0.173, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ni9ZI9zSsKi9; Thu,  2 Aug 2012 10:16:24 -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 29B1721F8622; Thu,  2 Aug 2012 10:16:24 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAJG0GlDGmAcF/2dsb2JhbABFhXuyK3OBB4IgAQEBAQMBAQEPEQ0EOgsMBAIBCA0EAQMBAQECAgYGDAsBAgICAQElHwMGCAEBBBMIGodrC59eih6TOQSBIYophXIyYAObRIoQgmE
X-IronPort-AV: E=Sophos;i="4.77,702,1336363200"; d="scan'208";a="360156194"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 02 Aug 2012 13:12:23 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 02 Aug 2012 13:11:50 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Subject: RE: [OPSAWG] Basic ietf process question ...
Date: Thu, 2 Aug 2012 19:16:20 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0407E24718@307622ANEX5.global.avaya.com>
In-Reply-To: <CABCOCHQwi7-Bi8itu5fZDpmEZDAufXwpS=zx68Xyq1xLzwOLng@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPSAWG] Basic ietf process question ...
Thread-Index: Ac1w0jSaA+9gSCWUS0eENw3bix/ixQAABTow
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com><CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com><CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com><501AA9DF.6010208@raszuk.net><EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com> <CABCOCHQwi7-Bi8itu5fZDpmEZDAufXwpS=zx68Xyq1xLzwOLng@mail.gmail.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Andy Bierman" <andy@yumaworks.com>
Cc: opsawg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 17:16:25 -0000

WWVzLiBUaGUgcXVlc3Rpb24gaXMgd2hldGhlciBhIGJhc2ljIGluZm9ybWF0aW9uIG1vZGVsIHdy
aXR0ZW4gaW4gWE1MIGNhbiBiZSBhIHVzZWZ1bCBzdGFydGluZyBwb2ludCAodHJ5aW5nIHRvIGlu
dGVycHJldCB0aGUgcHJvcG9zYWwgbWFkZSBieSBSb2JlcnQpLiANCg0KRGFuDQoNCj4gLS0tLS1P
cmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogQW5keSBCaWVybWFuIFttYWlsdG86YW5keUB5
dW1hd29ya3MuY29tXQ0KPiBTZW50OiBUaHVyc2RheSwgQXVndXN0IDAyLCAyMDEyIDg6MTQgUE0N
Cj4gVG86IFJvbWFzY2FudSwgRGFuIChEYW4pDQo+IENjOiByb2JlcnRAcmFzenVrLm5ldDsgb3Bz
YXdnQGlldGYub3JnOyBpZXRmQGlldGYub3JnDQo+IFN1YmplY3Q6IFJlOiBbT1BTQVdHXSBCYXNp
YyBpZXRmIHByb2Nlc3MgcXVlc3Rpb24gLi4uDQo+IA0KPiBPbiBUaHUsIEF1ZyAyLCAyMDEyIGF0
IDk6NTkgQU0sIFJvbWFzY2FudSwgRGFuIChEYW4pDQo+IDxkcm9tYXNjYUBhdmF5YS5jb20+IHdy
b3RlOg0KPiA+IEhpLA0KPiA+DQo+ID4gVGhlIE9QU0FXRy9PUFNBUkVBIG9wZW4gbWVldGluZyB0
aGlzIGFmdGVybm9vbiBoYXMgYW4gaXRlbSBvbiB0aGUNCj4gPiBhZ2VuZGEgY29uY2VybmluZyB0
aGUgcmV2aXNpb24gb2YgUkZDMTA1MiBhbmQgZGlzY3Vzc2luZyBhIG5ldw0KPiA+IGFyY2hpdGVj
dHVyZSBmb3IgbWFuYWdlbWVudCBwcm90b2NvbHMuDQo+ID4NCj4gPg0KPiA+IE15IHBlcnNvbmFs
IHRha2UgaXMgdGhhdCBubyBvbmUgcHJvdG9jb2wsIG9yIG9uZSBkYXRhIG1vZGVsaW5nDQo+ID4g
bGFuZ3VhZ2UgY2FuIG1hdGNoIHRoZSBvcGVyYXRpb25hbCByZXF1aXJlbWVudHMgdG8gY29uZmln
dXJlIGFuZA0KPiA+IG1hbmFnZSB0aGUgd2lkZSBhbmQgd2lkZXIgcmFuZ2Ugb2YgaG9zdHMsIHJv
dXRlcnMgYW5kIG90aGVyIG5ldHdvcmsNCj4gPiBkZXZpY2VzIHRoYXQgYXJlIHVzZWQgdG8gaW1w
bGVtZW50IElQIG5ldHdvcmtzIGFuZCBwcm90b2NvbHMuIFdlDQo+ID4gc2hvdWxkIGJlIHRhbGtp
bmcgbm93YWRheXMgYWJvdXQgYSB0b29sc2V0IHJhdGhlciB0aGFuIG9uZSB0b29sIHRoYXQNCj4g
PiBmaXRzIGFsbC4gSG93ZXZlciwgdGhpcyBpcyBhIGRpc2N1c3Npb24gdGhhdCBqdXN0IHN0YXJ0
cy4NCj4gDQo+IE5NUyBkZXZlbG9wZXJzIG5lZWQgdG8gc3BlbmQgdG9vIG1hbnkgcmVzb3VyY2Vz
IG9uIHRyYW5zbGF0aW5nIG5hbWluZw0KPiBhbmQgb3RoZXIgZGF0YS1tb2RlbGluZyBzcGVjaWZp
YyBkZXRhaWxzIHNvIHRoZXkgY2FuIGJlIHVzYWJsZSB3aXRoaW4NCj4gdGhlIGFwcGxpY2F0aW9u
LiAgU28gaWYgMSBkYXRhIG1vZGVsaW5nIGxhbmd1YWdlIGlzIG5vdCB1c2VkLCB0aGVuDQo+IGRl
dGVybWluaXN0aWMsIGxvc3MtbGVzcywgcm91bmQtdHJpcCB0cmFuc2xhdGlvbiBiZXR3ZWVuIGRh
dGEgbW9kZWxpbmcNCj4gbGFuZ3VhZ2VzIGlzIG5lZWRlZC4gIE11bHRpcGxlIHByb3RvY29scyBh
cmUgbm90IHRoZSBwcm9ibGVtIC0tDQo+IGluY29tcGF0aWJsZSBkYXRhIGZyb20gbXVsdGlwbGUg
cHJvdG9jb2xzIGlzIHRoZSBwcm9ibGVtLg0KPiANCj4gPg0KPiA+IFJlZ2FyZHMsDQo+ID4NCj4g
PiBEYW4NCj4gPg0KPiANCj4gQW5keQ0KPiANCj4gPg0KPiA+DQo+ID4NCj4gPj4gLS0tLS1Pcmln
aW5hbCBNZXNzYWdlLS0tLS0NCj4gPj4gRnJvbTogaWV0Zi1ib3VuY2VzQGlldGYub3JnIFttYWls
dG86aWV0Zi1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYNCj4gPiBPZg0KPiA+PiBSb2JlcnQg
UmFzenVrDQo+ID4+IFNlbnQ6IFRodXJzZGF5LCBBdWd1c3QgMDIsIDIwMTIgNzoyNSBQTQ0KPiA+
PiBDYzogaWV0ZkBpZXRmLm9yZw0KPiA+PiBTdWJqZWN0OiBCYXNpYyBpZXRmIHByb2Nlc3MgcXVl
c3Rpb24gLi4uDQo+ID4+DQo+ID4+IEFsbCwNCj4gPj4NCj4gPj4gSUVURiBkb2N1bWVudHMgaGF2
ZSBudW1iZXIgb2YgbWFuZGF0b3J5IHNlY3Rpb25zIC4uIElBTkEgQWN0aW9ucywNCj4gPj4gU2Vj
dXJpdHkgQ29uc2lkZXJhdGlvbnMsIFJlZnMsIGV0YyAuLi4NCj4gPj4NCj4gPj4gRG9lcyBhbnlv
bmUgaGF2ZSBhIGdvb2QgcmVhc29uIHdoeSBhbnkgbmV3IHByb3RvY29sIGRlZmluaXRpb24gb3IN
Cj4gPj4gZW5oYW5jZW1lbnQgZG9lcyBub3QgaGF2ZSBhIGJ1aWxkIGluIG1hbmRhdG9yeSAiWE1M
IHNjaGVtYSIgc2VjdGlvbg0KPiA+PiB3aGljaCB3b3VsZCBhbGxvdyB0byBhY3R1YWxseSB1c2Ug
c3VjaCBzdGFuZGFyZHMgYmFzZWQgZW5oYW5jZW1lbnQgaW4NCj4gPj4gdmVuZG9yIGFnbm9zdGlj
IHdheSA/DQo+ID4+DQo+ID4+IFRoZXJlIGlzIGEgbG90IG9mIHRhbGsgYWJvdXQgcmVpbnZlbnRp
bmcgQVBJcywgYnVpbGRpbmcgbmV0d29yayB3aWRlDQo+ID4gT1MNCj4gPj4gcGxhdGZvcm0sIGRl
bGl2ZXJpbmcgU0ROcyAod2hhdGV2ZXIgaXQgbWVhbnMgYXQgYW55IHBvaW50IG9mIHRpbWUgZm9y
DQo+ID4+IG9uZSkgLi4uIGJ1dCBob3cgYWJvdXQgd2Ugc3RhcnQgd2l0aCBzb21ldGhpbmcgdmVy
eSBiYXNpYyB5ZXQgSU1ITw0KPiA+PiBuZWNlc3NhcnkgdG8gc2xvd2x5IGJlZ2luIHRoaW5raW5n
IG9mIG5ldHdvcmsgYXMgb25lIHBsYW5lLg0KPiA+Pg0KPiA+PiBJIHVuZGVyc3RhbmQgdGhhdCBo
aXN0b3JpY2FsbHkgd2UgaGFkL3N0aWxsIGhhdmUgU05NUCBob3dldmVyIEkgaGF2ZQ0KPiA+PiBu
ZXZlciBzZWVuIHRoaXMgYmVpbmcgbWFuZGF0b3J5IHNlY3Rpb24gb2YgYW55IHN0YW5kYXJkcyB0
cmFjaw0KPiA+IGRvY3VtZW50Lg0KPiA+PiBVc3VhbGx5IFNOTVAgY29tZXMgNSB5ZWFycyBiZWhp
bmQgKGlmIGF0IGFsbCkgbWFraW5nIGl0IG9ic29sZXRlIGJ5DQo+ID4+IGRlc2lnbi4NCj4gPj4N
Cj4gPj4gTkVUQ09ORiBpcyBncmVhdCBhbmQgdmVyeSBmbGV4aWJsZSBjb21tdW5pY2F0aW9uIGNo
YW5uZWwgZm9yDQo+ID4+IHByb3Zpc2lvbmluZy4gSG93ZXZlciBpdCBpcyBzdWZmaWNpZW50IHRv
IGp1c3QgbG9vayBhdCBudW1iZXIgb2Ygb3BzDQo+ID4+IGxpc3RzIHRvIHNlZSB0aGF0IHRob3Nl
IHdobyB0cmllZCB0byB1c2UgaXQgcXVpY2tseSBhYmFuZG9uZWQgdGhlaXINCj4gPj4gZWZmb3J0
cyBkdWUgdG8gY29tcGxldGUgbGFjayBvZiBYTUwgc2NoZW1hIGZyb20gZWFjaCB2ZW5kb3IgdGhl
eQ0KPiA+IGhhcHBlbg0KPiA+PiB0byB1c2Ugb3IgY29tcGxldGUgbWlzbWF0Y2ggb2YgdmVuZG9y
IHRvIHZlbmRvciBYTUwgaW50ZXJwcmV0YXRpb24uDQo+ID4+DQo+ID4+IEFuZCB3aGlsZSBwZXJo
YXBzIHRoaXMgaXMgb2J2aW91cyBJIGRvIG5vdCB0aGluayB0aGF0IGFueSBuZXcgc2luZ2xlDQo+
ID4+IGVmZm9ydCB3aWxsIGFkZHJlc3MgdGhpcy4gVGhpcyBoYXMgdG8gYmUgYW4gYXRvbWljIGFu
ZCBpbnRlZ3JhbCBwYXJ0DQo+ID4gb2YNCj4gPj4gZWFjaCBXRydzIGRvY3VtZW50Lg0KPiA+Pg0K
PiA+PiBMb29raW5nIGZvcndhcmQgZm9yIGluc2lnaHRmdWwgY29tbWVudHMgLi4uDQo+ID4+DQo+
ID4+IEJlc3QsDQo+ID4+IFIuDQo+ID4+DQo+ID4NCj4gPiBfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+IE9QU0FXRyBtYWlsaW5nIGxpc3QNCj4gPiBP
UFNBV0dAaWV0Zi5vcmcNCj4gPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv
L29wc2F3Zw0K

From tnadeau@lucidvision.com  Thu Aug  2 10:18:40 2012
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 A972021E80DE for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 10:18:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eGjvLqRJCzla for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 10:18:40 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id CA4D821E803F for <ietf@ietf.org>; Thu,  2 Aug 2012 10:18:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by lucidvision.com (Postfix) with ESMTP id 5AF1B220DB17; Thu,  2 Aug 2012 13:18:39 -0400 (EDT)
X-Virus-Scanned: amavisd-new at www.lucidvision.com
Received: from lucidvision.com ([127.0.0.1]) by localhost (static-72-71-250-34.cncdnh.fios.verizon.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U2GeS6eyv-kq; Thu,  2 Aug 2012 13:18:39 -0400 (EDT)
Received: from tnadeau-sslvpn-nc.jnpr.net (natint3.juniper.net [66.129.224.36]) by lucidvision.com (Postfix) with ESMTP id A03EB220DB14; Thu,  2 Aug 2012 13:18:38 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: Basic ietf process question ...
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <501AA9DF.6010208@raszuk.net>
Date: Thu, 2 Aug 2012 10:18:36 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <F18D336A-1E60-4E17-8638-2583D7F54170@lucidvision.com>
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com> <CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com> <CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com> <501AA9DF.6010208@raszuk.net>
To: robert@raszuk.net
X-Mailer: Apple Mail (2.1485)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 17:18:40 -0000

	I am discussing this very topic in the Ops meeting today at 3. =
Please come by to discuss.

	--Tom


On Aug 2, 2012:9:25 AM, at 9:25 AM, Robert Raszuk <robert@raszuk.net> =
wrote:

> All,
>=20
> IETF documents have number of mandatory sections .. IANA Actions, =
Security Considerations, Refs, etc ...
>=20
> Does anyone have a good reason why any new protocol definition or =
enhancement does not have a build in mandatory "XML schema" section =
which would allow to actually use such standards based enhancement in =
vendor agnostic way ?
>=20
> There is a lot of talk about reinventing APIs, building network wide =
OS platform, delivering SDNs (whatever it means at any point of time for =
one) ... but how about we start with something very basic yet IMHO =
necessary to slowly begin thinking of network as one plane.
>=20
> I understand that historically we had/still have SNMP however I have =
never seen this being mandatory section of any standards track document. =
Usually SNMP comes 5 years behind (if at all) making it obsolete by =
design.
>=20
> NETCONF is great and very flexible communication channel for =
provisioning. However it is sufficient to just look at number of ops =
lists to see that those who tried to use it quickly abandoned their =
efforts due to complete lack of XML schema from each vendor they happen =
to use or complete mismatch of vendor to vendor XML interpretation.
>=20
> And while perhaps this is obvious I do not think that any new single =
effort will address this. This has to be an atomic and integral part of =
each WG's document.
>=20
> Looking forward for insightful comments ...
>=20
> Best,
> R.
>=20
>=20
>=20


From sm@resistor.net  Thu Aug  2 10:20:47 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D56711E8148 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 10:20:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JhhHjZhRQngk for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 10:20:44 -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 AF20C11E8129 for <ietf@ietf.org>; Thu,  2 Aug 2012 10:20:44 -0700 (PDT)
Received: from sm-THINK.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q72HKOKH026263; Thu, 2 Aug 2012 10:20:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1343928037; bh=CnN1OhqAvjKSm/rkqQALs4W2o0AVVoRzJhVHa/6hFoI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=PzgZesIc4g8xXD5+aJFr35Z4XPFI3+Alo2LiRTmNQ8flZ21sDljvyFgR+LFp5NZWu GkgFJrppoEcPdDQGHsU2vjnj9PhGAgD86erS2DIx3ogOCS9QAUTRj6d8M/PZQpv6cC o/ogn0vxfOJ/FswsUJ7whdQEh2cPshFUI601FWBU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1343928037; i=@resistor.net; bh=CnN1OhqAvjKSm/rkqQALs4W2o0AVVoRzJhVHa/6hFoI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=34x7lfTPZpgbwnAbENBr87weOp4AZFBnBzAfQkrBlWifqKWX5LyFJF7LAUra1WdG7 KJzbGG9Ib+N0nSc/1qwSuhjl2MC9fSdli9IZgR6htWWtzZbqTDZTzJ5n/B5RD11MpZ zIIUZI+u8MAJTlLhjssH4kE6bgehF0z7BVqWS1N8=
Message-Id: <6.2.5.6.2.20120802092955.09500ea0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 02 Aug 2012 10:15:35 -0700
To: "Murray S. Kucherawy" <superuser@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Oauth blog post
In-Reply-To: <CAL0qLwYNRW6FSC4kMQkn81+4HgKdv591D43Z31rLAg3ArRsSZg@mail.g mail.com>
References: <501531F7.5040404@gmail.com> <6.2.5.6.2.20120729073422.06d8fe10@resistor.net> <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net> <6.2.5.6.2.20120730101231.047f2550@resistor.net> <CAL0qLwYNRW6FSC4kMQkn81+4HgKdv591D43Z31rLAg3ArRsSZg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 17:20:47 -0000

Hi Murray,
At 09:13 AM 8/2/2012, Murray S. Kucherawy wrote:
>I think it's impossible to determine with certainty whether someone 
>standing at the mic and asserting a position is doing so based on 
>what an employer is insisting on doing, or that person's opinion.

Yes.

>We purport to participate as individuals.  It's entirely possible 
>that a person's opinion happens to concur with her employer's 
>opinion rather than being told what to say.  Does that mean the 
>corporation is the participant and not the person?

As the participation is as an individual the participant is the 
person.  In practice the person usually acts as a proxy for their 
employee.  A hum can be taken for some decisions so that the 
individual can express his or her opinion without any external pressure.

>So when I hear these sorts of allegations of corporate domination of 
>the standards process, I have to wonder how true they are.  I have a 
>pretty big corporate name on my badge this time, but I'm not here 
>pushing any specific agenda I was given.

I have not seen your badge.  I can find out what pretty corporate 
name is on it by looking  up the information on the relevant web page. :-)

These comments about corporate domination generally comes down to 
perception.  The problem in my humble opinion is mistrust.  It can be 
caused by miscommunication.

Regards,
-sm 


From ben@nostrum.com  Thu Aug  2 10:46:17 2012
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6EB611E81BC; Thu,  2 Aug 2012 10:46:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NVtHBLOq8qXu; Thu,  2 Aug 2012 10:46:16 -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 4B07811E81AD; Thu,  2 Aug 2012 10:46:16 -0700 (PDT)
Received: from dhcp-625b.meeting.ietf.org (dhcp-625b.meeting.ietf.org [130.129.98.91]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q72Hk62W012780 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 2 Aug 2012 12:46:11 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: Gen-ART LC Review of draft-ietf-websec-strict-transport-sec-11
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <50161BD5.7040901@KingsMountain.com>
Date: Thu, 2 Aug 2012 10:46:01 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <344AB802-6D45-4399-A628-6852A4732C16@nostrum.com>
References: <50161BD5.7040901@KingsMountain.com>
To: =JeffH <Jeff.Hodges@kingsmountain.com>
X-Mailer: Apple Mail (2.1485)
Received-SPF: pass (nostrum.com: 130.129.98.91 is authenticated by a trusted mechanism)
Cc: General Area Review Team <gen-art@ietf.org>, IETF WebSec WG <websec@ietf.org>, draft-ietf-websec-strict-transport-sec.all@tools.ietf.org, IETF Discussion List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 17:46:18 -0000

Hi, thanks for the response.  Comments inline:

On Jul 29, 2012, at 10:29 PM, =3DJeffH <Jeff.Hodges@kingsmountain.com> =
wrote:
>=20
> > -- Does this draft update any other RFCs (e.g. 2616 or 2818)? If so, =
that
> > should be explicitly flagged and mentioned in the abstract.
>=20
> Good question, I don't believe we've discussed this possibility =
directly in the websec wg. In looking at the RFCs that do update =
RFC2616, it doesn't look like draft-ietf-websec-strict-transport-sec =
(HSTS) is of that ilk.
>=20
> However, it nominally appears that an argument could be made that it'd =
be appropriate to update RFC2818 via =
draft-ietf-websec-strict-transport-sec, specifically with regards to =
Section 2.1.  Connection Initiation.
>=20
> Though, RFC2818 is Informational, which may be an issue (?). Also, =
perhaps this is something to more appropriately do via a standards-track =
rfc2818bis, i.e., have the latter reference the HSTS spec.
>=20
> this is something to discuss this coming week @IETF-84 Vancouver it =
seems.
>=20
>=20

I will comment on this in response to your post-meeting email.


> > -- I did not find any guidance on how to handle UAs that do not =
understand
> > this extension. I don't know if this needs to be normative, but the =
draft
> > should at least mention the possibility and implications.
>=20
> Agreed. My -12 working copy now contains these new subsections..
>=20
> ###
> 10.  Server Implementation and Deployment Advice
>=20
>   This section is non-normative.
>=20
> 10.1.  Non-Conformant User Agent Considerations
>=20
>   Non-conformant UAs ignore the Strict-Transport-Security header =
field,
>   thus non-conformant user agents do not address the threats described
>   in Section 2.3.1 "Threats Addressed".  Please refer to Section 14.1
>   "Non-Conformant User Agent Implications" for further discussion.
>=20
>                       .
>                       .
>=20
> 14.  Security Considerations
>                       .
>                       .
> 14.1.  Non-Conformant User Agent Implications
>=20
>   Non-conformant UAs ignore the Strict-Transport-Security header =
field,
>   thus non-conformant user agents do not address the threats described
>   in Section 2.3.1 "Threats Addressed".
>=20
>   This means that the web application and its users wielding non-
>   conformant user agents will be vulnerable to both:
>=20
>      Passive network attacks due to web site development and =
deployment
>      bugs: For example, if the web application contains any insecure,
>      non-"https", references to the web application server, and if not
>      all of its cookies are flagged as "Secure", then its cookies will
>      be vulnerable to passive network sniffing, and potentially
>      subsequent misuse of user credentials.
>=20
>      Active network attacks: If an attacker is able to place a man-in-
>      the-middle, secure transport connection attempts will likely =
yield
>      warnings to the user, but without HSTS Policy being enforced, the
>      present common practice is to allow the user to "click-through"
>      and proceed.  This renders the user and possibly the web
>      application open to abuse by such an attacker.
>=20
>   This is essentially the status-quo for all web applications and =
their
>   users in the absence of HSTS Policy.
> ###

That's all good text, but I'm not sure it actually captures my concern.

=46rom the server's perspective, the fact that non-conformant UAs may =
exist, the server cannot assume that UAs will honor the extension. This =
means that a UA might attempt unprotected access to some resource =
assumed to be protected by this extension. That is, the server can't =
merely select the extension and forget about things--it still needs to =
to take the same care to avoid leaking resources over unprotected =
connections that it would need to do if this extension did not exist in =
the first place.

I think this is implied by your last sentence above, but it would be =
better to say it explicitly.


>=20
> >
> > -- How should a UA handle potential conflicts between a the policy =
record
> > that includes the includeSubdomain, and any records for subdomains =
that might
> > have different parameters?
>=20
> this is in the draft. the short answer is that at policy enforcement =
time, "superdomain matches win".
>=20
> At "noting an HSTS Host" time, the HSTS host's policy (if expressed) =
is noted regardless of whether there are superdomain HSTS hosts =
asserting "includeSubDomains".
>=20
> perhaps this needs to be made more clear?

Maybe I'm missing something, but I'm not getting that answer from the =
text. Can you point out the specific language?

>=20
>=20
> >
> > -- section 6.1:
> >
> > The draft mentions that directives may be extended, but defers =
creation of an
> > IANA registry to the time of first extension. IANA registries are =
not
> > expensive; I suggest it be created now. If there's a good reason not =
to, then
> > the draft should still address the specification policy for =
extensions.
> >
> > Also, do you expect that some future directive might need to have a
> > "required-to-understand" status? Given that this is a =
security-affecting
> > extension, it seems likely. If so, then the mechanism for expressing =
that
> > needs to be defined in this draft.
>=20
>=20
> These are good questions, and they beg the overall question of how =
complex this simple solution really needs to be and whether we really =
think we'll need any extensions. Something for us to discuss in the =
working group meeting on Tue morning I think.

I will comment on this in the post-meeting mail.

>=20
> >
> > -- section 7.2:
> >
> > Am I correct to assume that the server must never just serve the =
content over
> > a non-secure connection? If so, it would be helpful to mention that, =
maybe
> > even normatively.
>=20
> It's a SHOULD, see the Note in that section, so it's already =
effectively stated normatively, though one needs to understand HTTP =
workings to realize it in the way you stated it above.  Perhaps could =
add a simple statement as you suggest to the intro para for section 7 =
Server Processing Model, to address this concern?
>=20

I think something of the form SHOULD redirect to HTTPS, but MUST NOT =
under any circumstances send the content unprotected would improve the =
text. That's probably already implied, and a reasonable implementor =
wouldn't due it anyway. But my experience is that some readers will find =
strange interpretations whenever you give them the wiggle room to do so, =
so it's better to be explicit.

>=20
> >
> > -- section 8.4:
> >
> > Does this imply a duty for compliant UAs to check for revocation one =
way or
> > another?
>=20
> yes. though, per other relevant specifications, as duly cited. AFAIK =
the HSTS spec doesn't need to get into the details because the =
underlying security transport specs, namely TLS, already do this.

If that duty already exists, then I see no reason to add it here. But do =
the cited specs unambiguously _require_ revocation checks? I admit to =
not being an expert here, but on a quick scan it seems more like they =
say how you can do it, but do they say you have to?=20

[...]

>=20
> > -- section 1.2:
> >
> > The description of indented notes is almost precisely the opposite =
of how
> > they are described in the RFC editor's style guide. It describes =
them as
> > "parenthetical" notes, which is how experienced RFC readers are =
likely to
> > perceive them. While it doesn't say so explicitly, I think putting =
normative
> > text in parenthetical notes should be avoided. If these are intended =
to be
> > taken more strongly than that (and by the description, I take it =
they should
> > be taken more strongly than the surrounding text), then I suggest =
choosing a
> > stronger prefix than "NOTE:"
>=20
> As it turns out, almost all the Notes are parenthetical.
>=20
> I'll render the one(s) that are normative as a regular paragraph(s) =
and leave the others as-is. Will that address your concern?
>=20

Yes, thanks.

>=20
> >
> > -- section 7:
> >
> > Does the reference to I-D.ietf-tls-ssl-version3 indicate a =
requirement for
> > SSL3?
>=20
> no, it's just that SSLv3 remains a fact of life and is referenced for =
completeness' sake.
>=20
>=20

Okay.

>=20
> >
> > -- section 8.2, paragraph 5 (first non-numbered paragraph after =
numbered
> > list)
> >
> > To be pedantic, this could be taken to mean a congruent match only =
applies if
> > the includeSubdomains flag is not present. I assume it's intended to =
apply
> > whether or not the flag is present.
>=20
> [ I am assuming you actually are referring to section 8.3, as section =
8.2 doesn't mention the includeSubdomains flag and does not contain a =
numbered list. ]
>=20
> yes, a congruent match is intended to apply whether or not the flag is =
present.
>=20
>=20

yes, I meant 8.3. And on re-reading, I think the text is fine.

>=20
> > -- section 12 and subsections:
> >
> > I was surprised to see more apparently normative material after the
> > non-normative guidance sections. I think it would improve the =
organization to
> > put this closer to the normative rules for UAs.
>=20
> We can move section 12 up ahead of the non-normative guidance =
sections.

I think that would help, thanks.

>=20
>=20
> >
> > -- section 14.1, 4th paragraph (first non-bulleted paragraph =
following bullet
> > list)
> >
> > This issue is only true for proxies that act as a TLS MiTM, right?
>=20
> yes.
>=20
>=20
> > Would
> > proxies that tunnel TLS via the CONNECT method have this issue?
>=20
> I don't think so in the general case.
>=20
> I'm not sure what terminology to use to differentiate such proxies if =
this is a detail worth addressing.
>=20

Okay

>=20
> thanks again,
>=20
> =3DJeffH
>=20
>=20
>=20
>=20
>=20
>=20


From lars@netapp.com  Thu Aug  2 11:07:08 2012
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23B7E11E8197; Thu,  2 Aug 2012 11:07:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.447
X-Spam-Level: 
X-Spam-Status: No, score=-10.447 tagged_above=-999 required=5 tests=[AWL=0.152, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m+9F8uuVAtZt; Thu,  2 Aug 2012 11:07:07 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 862CF11E80F5; Thu,  2 Aug 2012 11:07:07 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.77,702,1336374000";  d="p7s'?scan'208";a="672285146"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 02 Aug 2012 11:07:07 -0700
Received: from vmwexceht02-prd.hq.netapp.com (vmwexceht02-prd.hq.netapp.com [10.106.76.240]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q72I77ZQ001168; Thu, 2 Aug 2012 11:07:07 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.13]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.02.0298.004; Thu, 2 Aug 2012 11:07:06 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: IETF Administrative Director <iad@ietf.org>
Subject: Re: [IAB] Draft Fees for Processing Legal Requests Policy
Thread-Topic: [IAB] Draft Fees for Processing Legal Requests Policy
Thread-Index: AQHNcM6F4lt8DZmzr0CanT4RQaDhJ5dHRvkA
Date: Thu, 2 Aug 2012 18:07:06 +0000
Message-ID: <23C09D95-E873-40C1-9BF5-3378290C9FD0@netapp.com>
References: <20120802164717.20616.13622.idtracker@ietfa.amsl.com>
In-Reply-To: <20120802164717.20616.13622.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.115]
Content-Type: multipart/signed; boundary="Apple-Mail=_019FCBF4-0AEB-43B1-91EE-DADB522F7EF3"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: "<wgchairs@ietf.org>" <wgchairs@ietf.org>, "<ietf@ietf.org>" <ietf@ietf.org>, "<iaoc@ietf.org>" <iaoc@ietf.org>, "<iab@iab.org>" <iab@iab.org>, "<iesg@ietf.org>" <iesg@ietf.org>, IETF Announcement List <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, 02 Aug 2012 18:07:08 -0000

--Apple-Mail=_019FCBF4-0AEB-43B1-91EE-DADB522F7EF3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Looks good to me, but I agree with whoever suggested to increase the =
fees. I think you could easily double or triple them.

On Aug 2, 2012, at 9:47, IETF Administrative Director <iad@ietf.org> =
wrote:

> A reminder of the deadline of 6 August for input.
> Thanks
>=20
> The IAOC is seeking community feedback on a proposed policy by the =
IAOC to impose=20
> fees to produce information and authenticate documents in response to =
subpoenas and=20
> other legal requests.
>=20
> The IETF receives requests for information, documentation, =
authentication or other=20
> matters through subpoenas and less formal means that require manpower =
and materials=20
> to be expended.  These requests are on the rise. During the period =
2005 to 2010 the IETF=20
> responded to nine subpoenas.  Since 2011 the IETF has received five =
subpoenas and three=20
> other legal requests for authenticated documents. =20
>=20
> Each such request is time sensitive and involves the IETF Counsel, the =
IAD, and members=20
> of the IAOC, who together form the Legal Management Committee, to =
rapidly analyze and=20
> identify the means for satisfying the request.  Often there is a need =
to retain outside counsel,=20
> especially in cases that might lead to depositions or court testimony.=20=

>=20
> The IAOC believes a Schedule of Fees is an appropriate and reasonable =
means to recover=20
> costs associated with such efforts.
>=20
> The draft policy entitled Draft Fee Policy for Legal Requests can be =
found=20
> at: <http://iaoc.ietf.org/policyandprocedures.html>
>=20
> Before adopting a policy the IAOC would like feedback on this before =
making a=20
> decision.  Comments appreciated to ietf@ietf.org by 6 August 2012.
>=20
> Ray Pelletier
> IETF Administrative Director


--Apple-Mail=_019FCBF4-0AEB-43B1-91EE-DADB522F7EF3
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMQDCCBUow
ggQyoAMCAQICEFcfSRTG0jNknqb9LV9GuFkwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTEyMTAwMDAwMDBaFw0x
MjEyMDkyMzU5NTlaMIIBDTEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEeMBwGCSqGSIb3DQEJARYPbGFyc0BuZXRhcHAuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokrhJTcXt6J/VEpZOicLoguBlYTjXP9v
Ze4HuuhXnURUS8YouAfgaqA0zYbt5yd6fh4PBMdAaEWr5yJyHuFykXlrCumjUWSpLuqTS2A+pt4q
cZaAQk9iLDN/UVd3SpkUuvWbxXlqzG7/BSqa3VNObBzCmyh+V7aXxri+30CT//DSsNRC4VFy6sn6
dMgSaFenXLwe/FBwY0qTMfICT1PrrX6Sw1S8OfH9rykLlZXbmfkFExxQngp1DJH9xMHeODHGbCv/
ty5gdxMOrLe+vENxFEcy1YQWBZd1kNL4UObugF8A/jE/s+Oa3H1VFH8ghqZTdqGDysVxmtKHuNFx
6jIBSQIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgG
CCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNV
HSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDovL2luZGMx
ZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqG
SIb3DQEBBQUAA4IBAQBA7q6tR92qpd7xo7VBsrOfGCWzoxIVfTc7t0RhB/Oz/+c3lnhYnNScIuKN
JmyZvznmVxqB9BJ72+NkvmdB/hnILSBTRawL2tyLo9PkBtN0nRt4gS6wjpWnD8G83hlJLE7r25jk
7HkRev61dTIXsANFpJKF02C4XSoDfEzNV6MpuEvHvcgHCqMrlwWwfKc7+NoDnE8PBuRzwSXvlD5L
mswCY2iiOsd7ImNO4OzTCxETvKTDu92+FTIbRJJpYjVNv1UF7e3w9Kq65BkZJErUH19beUeQl0Wh
2BJQE6/15rQyCnP0iJ/Nmx2/kI6M0PWunEsI6FMs0MbosreaWGHlQmomMIIG7jCCBdagAwIBAgIQ
cRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQL
EzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYD
VQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y
aXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAo
YykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBD
bGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6ZvgSU6Lb9UB
0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHsEnMhjfXc
MM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO4YM/d/mZ
//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSyriMGZSal
J1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYI
KwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0T
AQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVy
aXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9w
Y2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1h
Z2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28u
dmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRl
TGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHp
MIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWduLCBJ
bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENsYXNzIDEg
UHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+v
OEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlMJBq6WaSH
O3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKvYLMVirOV
nDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDRyxTWcVib
vtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy+kgOZY5J
yNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/wYIxggSL
MIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDgwMjE4MDcwNVowIwYJKoZIhvcNAQkEMRYEFHLi
OfcmFJd934nV+PNUBol3vwOTMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBAEDg9+Xh
JIxSH1mzZxqu7pw956N6EMctzTtBNVfsh8qQ35UMbdxgJxddoTOfYTbU528H879BPP1jwcL/GKr+
FqOyylM6E6WeicTcVI4Pi9WcpqvWNI+dtKAc08UISrg11qDVymhnQH85LgqVDbOpfWDifde4BAGq
cMa0x1B+bEqd+vPM902eM0Q3M205tsKV0ojARWIn6S5yI9pEvmFKFBq0d70+NNrLFc2dQcmNPFGu
XIDoHQZwUa9sN35LHUJNrGUn09wv2mUeb4p4Pm3cVcZuGPk3mg3sbnqOKKJqZv/cBIurH+EqYjag
hNRzdqrRJ2liC7dBF48IyxIgKh/bcsMAAAAAAAA=

--Apple-Mail=_019FCBF4-0AEB-43B1-91EE-DADB522F7EF3--

From brian.e.carpenter@gmail.com  Thu Aug  2 11:11:19 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F63C21F8592; Thu,  2 Aug 2012 11:11:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.46
X-Spam-Level: 
X-Spam-Status: No, score=-101.46 tagged_above=-999 required=5 tests=[AWL=0.231, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C21BF+CaE2UM; Thu,  2 Aug 2012 11:11:13 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id B2D9B11E8200; Thu,  2 Aug 2012 11:11:12 -0700 (PDT)
Received: by weyu54 with SMTP id u54so6888972wey.31 for <multiple recipients>; Thu, 02 Aug 2012 11:11:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=15LcXXzM72CCqEbZLP5PBiUzAiuj14e5H9nyrnaPvAE=; b=Emg8+eOMknZ8acozJpcMknPOk7a24Q/Uv+7g0kWHH+zkEuBh+WmoaIjm55POWov5WL S+6c6eUxGHxT/RfT3voFU7ZOXbn6teUVZfioUACy7v4xFIVlCQOxRBo+fYYIK0VqmJ81 U+s4bFa5u3R+uK1N/b82fux1cLKelpwFy0oVPtG+f1bCcKgkI3k0FPfqMmd4Mi8pAdgB ohILsuIRWS99NrZeg1w3MMQ9UdvZPXPZinY9WLqqx0DGZM1FJSbNTuECXH26lZFqKFAf fot0XL/JXXPsE8sg/gY9ZzYjPWRoDamdUnXOf9yPcfXPmd3tc94gojGFemLKXpEpEWh8 lpdg==
Received: by 10.180.104.197 with SMTP id gg5mr6700774wib.9.1343931071890; Thu, 02 Aug 2012 11:11:11 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-219-46.as13285.net. [2.102.219.46]) by mx.google.com with ESMTPS id fb20sm18993230wid.1.2012.08.02.11.11.10 (version=SSLv3 cipher=OTHER); Thu, 02 Aug 2012 11:11:11 -0700 (PDT)
Message-ID: <501AC2C7.6040707@gmail.com>
Date: Thu, 02 Aug 2012 19:11:19 +0100
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: robert@raszuk.net
Subject: Re: Basic ietf process question ...
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com><CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com><CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com>	<501AA9DF.6010208@raszuk.net>	<EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com> <501AB4F5.7030205@raszuk.net>
In-Reply-To: <501AB4F5.7030205@raszuk.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>, opsawg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 18:11:19 -0000

I think anyone with intimate experience of the Web Services standards
experiment (trying to use XML as if it was a Turing machine) would have
extreme doubts about any proposal to impose such a requirement.

It was not for no reason that many people came to refer to the Web
Services family of standards as "WS-splat". The words "small" and
"xml schema" don't really belong together,

Regards
   Brian Carpenter

On 02/08/2012 18:12, Robert Raszuk wrote:
> Hi Dan,
> 
>> We should be talking
>> nowadays about a toolset rather than one tool that fits all.
> 
> Just to clarify what I asked about .. I am not looking for a single tool
> or single protocol to be used to configure everything.
> 
> I am asking for small building block like xml schema (or something
> similar) to be part of each new IETF proposal or protocol change. IMHO
> only that can allow any further more fancy abstractions and tools to be
> build and used in practice.
> 
> Best regards,
> R.
> 
> 
> 
>> Hi,
>>
>> The OPSAWG/OPSAREA open meeting this afternoon has an item on the agenda
>> concerning the revision of RFC1052 and discussing a new architecture for
>> management protocols.
>>
>>
>> My personal take is that no one protocol, or one data modeling language
>> can match the operational requirements to configure and manage the wide
>> and wider range of hosts, routers and other network devices that are
>> used to implement IP networks and protocols. We should be talking
>> nowadays about a toolset rather than one tool that fits all. However,
>> this is a discussion that just starts.
>>
>> Regards,
>>
>> Dan
>>
>>
>>
>>
>>> -----Original Message-----
>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
>> Of
>>> Robert Raszuk
>>> Sent: Thursday, August 02, 2012 7:25 PM
>>> Cc: ietf@ietf.org
>>> Subject: Basic ietf process question ...
>>>
>>> All,
>>>
>>> IETF documents have number of mandatory sections .. IANA Actions,
>>> Security Considerations, Refs, etc ...
>>>
>>> Does anyone have a good reason why any new protocol definition or
>>> enhancement does not have a build in mandatory "XML schema" section
>>> which would allow to actually use such standards based enhancement in
>>> vendor agnostic way ?
>>>
>>> There is a lot of talk about reinventing APIs, building network wide
>> OS
>>> platform, delivering SDNs (whatever it means at any point of time for
>>> one) ... but how about we start with something very basic yet IMHO
>>> necessary to slowly begin thinking of network as one plane.
>>>
>>> I understand that historically we had/still have SNMP however I have
>>> never seen this being mandatory section of any standards track
>> document.
>>> Usually SNMP comes 5 years behind (if at all) making it obsolete by
>>> design.
>>>
>>> NETCONF is great and very flexible communication channel for
>>> provisioning. However it is sufficient to just look at number of ops
>>> lists to see that those who tried to use it quickly abandoned their
>>> efforts due to complete lack of XML schema from each vendor they
>> happen
>>> to use or complete mismatch of vendor to vendor XML interpretation.
>>>
>>> And while perhaps this is obvious I do not think that any new single
>>> effort will address this. This has to be an atomic and integral part
>> of
>>> each WG's document.
>>>
>>> Looking forward for insightful comments ...
>>>
>>> Best,
>>> R.
>>>
>>
>>
>>
> 
> 

From hallam@gmail.com  Thu Aug  2 11:16:09 2012
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BF1F11E81F5 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 11:16:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.674
X-Spam-Level: 
X-Spam-Status: No, score=-4.674 tagged_above=-999 required=5 tests=[AWL=-2.934, BAYES_20=-0.74, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2tjhssM4MiCE for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 11:16:05 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7FBA011E81B7 for <ietf@ietf.org>; Thu,  2 Aug 2012 11:16:05 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so9736633ghb.31 for <ietf@ietf.org>; Thu, 02 Aug 2012 11:16:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=gmNvtios9+y0B6uEY1BBNZLK5/JexOWoPji5vkQ6l08=; b=MoQ7CTkcsXnQenMxkETQn/Bsql5SRgyLveDQUfhr7R3/Q/PidGjkSCmcta3zU7hQpK gO4zAe6W0g/qykQzzpEIF7XG7oQk6Tw1BxSP7SZWxG5r3nLrz2/mR6+ktEbJHjh8lr5O ldBXUcyY2+NcZjl7EewG8AUZLnYjPMKp+cgBOr85KuxamuU6qMv8R68W3G1lUWyTWymA TCKoSJMEfFqQPtMPjB7zdLl1i1z9Dr5jDJxLJMKTrO9kWH5ZPxjfs/YNiB59FiWjVzu2 J42pOJv2dl37jEqsYztUp3qCetx+H0cbaD9xW4n/h4SIWKAGrl4Jk2mhxJ+x7WBpVzzR wqUw==
MIME-Version: 1.0
Received: by 10.60.20.197 with SMTP id p5mr38623263oee.32.1343931364858; Thu, 02 Aug 2012 11:16:04 -0700 (PDT)
Received: by 10.76.133.104 with HTTP; Thu, 2 Aug 2012 11:16:04 -0700 (PDT)
Date: Thu, 2 Aug 2012 11:16:04 -0700
Message-ID: <CAMm+LwhKUZK9RGSmrntB6ZZVfnXRsaZfUcpWvVhWnxWRgdBjbw@mail.gmail.com>
Subject: ITU-T Dubai Meeting
From: Phillip Hallam-Baker <hallam@gmail.com>
To: IETF Discussion Mailing 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: Thu, 02 Aug 2012 18:16:09 -0000

Those of us who went through the crypto-wars will see a lot of
similarities between the situation we faced then and now. The main
difference being that in the mid 1990s very few people understood what
the net was really capable of, it was seen as merely a way to make
money. Those who were paying attention knew that it was rather more
important.

The 1979 revolution in Iran spread through the then new medium of the
compact cassette. The 1989 collapse of communism in Eastern Europe was
in large measure driven by Western television signals leaking over the
border. Long before that, the development of the printing press led to
the Reformation, nor is it coincidental that Benjamin Franklin and
many other revolutionaries were in the business of print.

The Web is not the first media technology to give the masses
unrestricted access to information. The unprecedented feature of the
Web is that it gave everyone a voice.

Many if not most of the people involved in the development of the
Internet and the Web have understood this from the start. And the
potential political consequences of the Web have been rather better
understood in government circles than many imagine. What has changed
in the years since the last ITU rechartering event is not the
understanding of the potential consequences of the net but the fact
that the Iranian election protests of 2009 and the Arab Spring have
made them imposible to ignore.

Russia and China have been pushing for government regulation of the
net for years. They even agreed a treaty under the Shanghai
Cooperation Organization (SCO) which commits the parties to work
together to stop such things as 'Information terrorism' which is their
term for freedom of speech. There is nothing new in their ambitions.
Russia has made plain that it will make no effort to control Internet
crime originating in Russia unless the US and European powers agree to
censor publications critical of Putin.

But there is also another side to the complaints made by Russia, China
and others, a complaint that US dominated organizations like ICANN and
the IETF do not allow sufficient credit for in my view. The current
governance structure of the Internet does more than merely prevent
other governments from gaining control of the Internet, it grants the
US an extraordinary degree of control. Or at least they give the
appearance of doing so on paper if the checks and balances on that
control are not sufficiently understood.


As with the crypto-wars there is a very real risk of the governments
getting together to make a 'grand bargain' and as with the crypto-wars
the grand bargain will almost certainly mean absolutely nothing.

Legislation through treaty making has in recent years become a major
threat to the concept of democracy. Rather than present a
controversial proposal to their legislature, various governments will
propose it in closed session of an international treaty making process
which the legislature 'must' then ratify as a fait accompli.

Unlike in the crypto-wars, there is no risk that the US government
delegation will engage in this type of back-stab operation. But there
is a very real risk that other governments will. There are many
governments would prefer a police-friendly state to an open Internet
and there is a very real risk that they will accept treaty clauses
that 'require' them to bring the net under direct government control.

It may be that these governments will succeed in such a move, but it
is also possible if not rather likely that the attempt would provoke
the civil unrest that they are attempting to suppress. Mubarak's
government hoped that shutting down the Internet would shut down the
protests. Instead it had the opposite effect as the keyboard warriors
were forced to leave their homes and go into the streets to find out
what was happening.

Contrary to the view expressed to me by one IESG member, there is no
outcome here that is 'unthinkable'. Diplomats will almost invariably
tell you that their has no choice but to sign whatever treaty they are
working on. Looking at recent treaty actions in the US Senate it seems
highly unlikely that any treaty agreed in Dubai will make it out of
committee, let alone receive the super-majority required for
ratification regardless of what the treaty actually states. Moreover,
the diplomats are not the policy makers. If the WCIT process results
in an over-reach, governments can and will leave the ITU.

If people believe such outcomes are unthinkable, they have not been
paying attention. What should be unthinkable is the idea of sending
planes over a country to drop bombs on cities. Such actions are rather
commonplace in our world. The reason that institutions such as the ITU
persist is not that it is unthinkable that any government would leave
but that the people who lead such organizations dare not commit to any
act that might provoke such an action.

The most likely outcome from Dubai therefore is an ambiguous document
that the reader can interpret as maintaining or overturning the status
quo as they choose. The only real area of concern being the extent to
which that document gives a pretext for government network takeovers.
My personal view is that it does not make a difference whether the
document does or not since the governments who are attempting to
control the net in their country will do so irregardless of what the
treaty says, nor is the text going to dissuade anyone from protesting.


Rather than being overly concerned about the diplomatic situation, we
should instead focus on the ways that the technical architecture of
the Internet creates control points that are vulnerable to capture and
consider ways in which those control points can be made capture-proof.

The Internet has three separate potential control points: The IP
Address registry, the DNS name registry and the various registries for
protocol features. All three are an example of a Tinkerbell ontology:
They exist for no other reason than that people believe in their
existence. ICANN DNS names have relevance because there is a consensus
that they are so, new.net DNS names are irrelevant because there is
consensus that they are so.

Rather than attempting to maintain the status quo, we should instead
identify what are the necessary concerns. We need to protect the
openness of the Internet. We do not need to perpetuate the existence
of ICANN, IANA or the RIRs as institutions. Maintaining the
institutions may be a means of protecting the open internet but we
should be prepared to walk away from them if necessary and in
particular we should not defend their monopoly status at all costs.

Consider for example the maintenance of IPv6 address space. Why does
this have to be an IANA monopoly? The only necessary requirements for
IPv6 address space is that the same space is not assigned to two
different parties and we do not run out. If the ITU-T wants to also be
in the business of handing out IPv6 address names then give then a /21
or a /16 and tell them to go party. No really, choose your battles.
Having a duopoly in address assignment is better than a monopoly. If
Russia, China et. al. decide that they want to do that and tell IANA
what prefix they are going to be using, they can make it a fait
accompli in any case.

The DNS is a rather more complex consideration. In that case I see a
fracture as all but inevitable. But that should not be a cause for
panic. The fracture that I anticipate is at the root rather than the
leaves. There will be only one example.com but people who live in
different countries will arrive at it in rather different ways.
New.net was a quixotic proposition when advanced by a private
corporation, when advanced by a large nation state it is not. Rather
than try to defend ICANN at all possible costs, I will be investing my
energies in working out ways to mitigate the effects of the split.


In conclusion, there is an issue here but not a cause for the panic
that many seem to suggest. The situation is certainly complex, but not
one that is too complex for mortal understanding. What I am certain of
is that we do not need to rely on the counsels of those who tell us
that the situation is so complex that we need not worry our little
heads about it. In fact I believe the exact opposite: The openness of
the net will only be secured through frank and open discussion of all
the issues.


[1] http://www.senate.gov/pagelayout/legislative/one_item_and_teasers/trty_act.htm
-- 
Website: http://hallambaker.com/

From robert@raszuk.net  Thu Aug  2 11:17:33 2012
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 1193111E8221 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 11:17:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.254
X-Spam-Level: 
X-Spam-Status: No, score=-2.254 tagged_above=-999 required=5 tests=[AWL=0.345,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r7a31dfmCyBa for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 11:17:32 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 201EE11E821C for <ietf@ietf.org>; Thu,  2 Aug 2012 11:17:32 -0700 (PDT)
Received: (qmail 8399 invoked by uid 399); 2 Aug 2012 18:17:31 -0000
Received: from unknown (HELO ?130.129.17.10?) (pbs:robert@raszuk.net@130.129.17.10) by mail1310.opentransfer.com with ESMTPM; 2 Aug 2012 18:17:31 -0000
X-Originating-IP: 130.129.17.10
Message-ID: <501AC43A.3020307@raszuk.net>
Date: Thu, 02 Aug 2012 20:17:30 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Basic ietf process question ...
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com><CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com><CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com>	<501AA9DF.6010208@raszuk.net>	<EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com> <501AB4F5.7030205@raszuk.net> <501AC2C7.6040707@gmail.com>
In-Reply-To: <501AC2C7.6040707@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>, opsawg@ietf.org, 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: Thu, 02 Aug 2012 18:17:33 -0000

Hi Brian,

Perhaps we understand a different thing by "xml schema" As example what 
I had in mind when asking this question was the example from "Appendix 
A" of http://tools.ietf.org/html/draft-marques-l3vpn-schema-00 where 
while perhaps not yet complete it does provide decent representation of 
one of the popular service today.

That's what I had mind asking why such appendix isn't a mandatory part 
of each new protocol extension.

It has very little to do with Web Services you may be referring to.

Many thx,
R.

> I think anyone with intimate experience of the Web Services standards
> experiment (trying to use XML as if it was a Turing machine) would have
> extreme doubts about any proposal to impose such a requirement.
>
> It was not for no reason that many people came to refer to the Web
> Services family of standards as "WS-splat". The words "small" and
> "xml schema" don't really belong together,
>
> Regards
>     Brian Carpenter
>
> On 02/08/2012 18:12, Robert Raszuk wrote:
>> Hi Dan,
>>
>>> We should be talking
>>> nowadays about a toolset rather than one tool that fits all.
>>
>> Just to clarify what I asked about .. I am not looking for a single tool
>> or single protocol to be used to configure everything.
>>
>> I am asking for small building block like xml schema (or something
>> similar) to be part of each new IETF proposal or protocol change. IMHO
>> only that can allow any further more fancy abstractions and tools to be
>> build and used in practice.
>>
>> Best regards,
>> R.
>>
>>
>>
>>> Hi,
>>>
>>> The OPSAWG/OPSAREA open meeting this afternoon has an item on the agenda
>>> concerning the revision of RFC1052 and discussing a new architecture for
>>> management protocols.
>>>
>>>
>>> My personal take is that no one protocol, or one data modeling language
>>> can match the operational requirements to configure and manage the wide
>>> and wider range of hosts, routers and other network devices that are
>>> used to implement IP networks and protocols. We should be talking
>>> nowadays about a toolset rather than one tool that fits all. However,
>>> this is a discussion that just starts.
>>>
>>> Regards,
>>>
>>> Dan
>>>
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
>>> Of
>>>> Robert Raszuk
>>>> Sent: Thursday, August 02, 2012 7:25 PM
>>>> Cc: ietf@ietf.org
>>>> Subject: Basic ietf process question ...
>>>>
>>>> All,
>>>>
>>>> IETF documents have number of mandatory sections .. IANA Actions,
>>>> Security Considerations, Refs, etc ...
>>>>
>>>> Does anyone have a good reason why any new protocol definition or
>>>> enhancement does not have a build in mandatory "XML schema" section
>>>> which would allow to actually use such standards based enhancement in
>>>> vendor agnostic way ?
>>>>
>>>> There is a lot of talk about reinventing APIs, building network wide
>>> OS
>>>> platform, delivering SDNs (whatever it means at any point of time for
>>>> one) ... but how about we start with something very basic yet IMHO
>>>> necessary to slowly begin thinking of network as one plane.
>>>>
>>>> I understand that historically we had/still have SNMP however I have
>>>> never seen this being mandatory section of any standards track
>>> document.
>>>> Usually SNMP comes 5 years behind (if at all) making it obsolete by
>>>> design.
>>>>
>>>> NETCONF is great and very flexible communication channel for
>>>> provisioning. However it is sufficient to just look at number of ops
>>>> lists to see that those who tried to use it quickly abandoned their
>>>> efforts due to complete lack of XML schema from each vendor they
>>> happen
>>>> to use or complete mismatch of vendor to vendor XML interpretation.
>>>>
>>>> And while perhaps this is obvious I do not think that any new single
>>>> effort will address this. This has to be an atomic and integral part
>>> of
>>>> each WG's document.
>>>>
>>>> Looking forward for insightful comments ...
>>>>
>>>> Best,
>>>> R.
>>>>
>>>
>>>
>>>
>>
>>
>
>


From ynir@checkpoint.com  Thu Aug  2 11:18:14 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF84421E80C4; Thu,  2 Aug 2012 11:18:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.326
X-Spam-Level: 
X-Spam-Status: No, score=-10.326 tagged_above=-999 required=5 tests=[AWL=0.273, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oVZqVKvkAJt4; Thu,  2 Aug 2012 11:18:14 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id A486D21E80DF; Thu,  2 Aug 2012 11:18:13 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id q72IIB04011132; Thu, 2 Aug 2012 21:18:11 +0300
X-CheckPoint: {501AC1CA-1-1B221DC2-4FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Thu, 2 Aug 2012 21:18:10 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Ben Campbell <ben@nostrum.com>
Date: Thu, 2 Aug 2012 21:18:09 +0300
Subject: Re: Gen-ART LC Review of draft-ietf-websec-strict-transport-sec-11
Thread-Topic: Gen-ART LC Review of draft-ietf-websec-strict-transport-sec-11
Thread-Index: Ac1w2yvprMHoxvR2RzOTiJG6heTTcA==
Message-ID: <C0912D8D-4DA8-4E0A-9C72-0AF917EE0F9E@checkpoint.com>
References: <50161BD5.7040901@KingsMountain.com> <344AB802-6D45-4399-A628-6852A4732C16@nostrum.com>
In-Reply-To: <344AB802-6D45-4399-A628-6852A4732C16@nostrum.com>
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: General Area Review Team <gen-art@ietf.org>, IETF WebSec WG <websec@ietf.org>, "draft-ietf-websec-strict-transport-sec.all@tools.ietf.org" <draft-ietf-websec-strict-transport-sec.all@tools.ietf.org>, IETF Discussion List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 18:18:15 -0000

On Aug 2, 2012, at 10:46 AM, Ben Campbell wrote:

> Hi, thanks for the response.  Comments inline:
>=20
> On Jul 29, 2012, at 10:29 PM, =3DJeffH <Jeff.Hodges@kingsmountain.com> wr=
ote:
>=20
>>> -- I did not find any guidance on how to handle UAs that do not underst=
and
>>> this extension. I don't know if this needs to be normative, but the dra=
ft
>>> should at least mention the possibility and implications.
>>=20
>> Agreed. My -12 working copy now contains these new subsections..
>>=20
>> ###
>> 10.  Server Implementation and Deployment Advice
>>=20
>>  This section is non-normative.
>>=20
>> 10.1.  Non-Conformant User Agent Considerations
>>=20
>>  Non-conformant UAs ignore the Strict-Transport-Security header field,
>>  thus non-conformant user agents do not address the threats described
>>  in Section 2.3.1 "Threats Addressed".  Please refer to Section 14.1
>>  "Non-Conformant User Agent Implications" for further discussion.
>>=20
>>                      .
>>                      .
>>=20
>> 14.  Security Considerations
>>                      .
>>                      .
>> 14.1.  Non-Conformant User Agent Implications
>>=20
>>  Non-conformant UAs ignore the Strict-Transport-Security header field,
>>  thus non-conformant user agents do not address the threats described
>>  in Section 2.3.1 "Threats Addressed".
>>=20
>>  This means that the web application and its users wielding non-
>>  conformant user agents will be vulnerable to both:
>>=20
>>     Passive network attacks due to web site development and deployment
>>     bugs: For example, if the web application contains any insecure,
>>     non-"https", references to the web application server, and if not
>>     all of its cookies are flagged as "Secure", then its cookies will
>>     be vulnerable to passive network sniffing, and potentially
>>     subsequent misuse of user credentials.
>>=20
>>     Active network attacks: If an attacker is able to place a man-in-
>>     the-middle, secure transport connection attempts will likely yield
>>     warnings to the user, but without HSTS Policy being enforced, the
>>     present common practice is to allow the user to "click-through"
>>     and proceed.  This renders the user and possibly the web
>>     application open to abuse by such an attacker.
>>=20
>>  This is essentially the status-quo for all web applications and their
>>  users in the absence of HSTS Policy.
>> ###
>=20
> That's all good text, but I'm not sure it actually captures my concern.
>=20
> From the server's perspective, the fact that non-conformant UAs may exist=
, the server cannot assume that UAs will honor the extension. This means th=
at a UA might attempt unprotected access to some resource assumed to be pro=
tected by this extension. That is, the server can't merely select the exten=
sion and forget about things--it still needs to to take the same care to av=
oid leaking resources over unprotected connections that it would need to do=
 if this extension did not exist in the first place.
>=20
> I think this is implied by your last sentence above, but it would be bett=
er to say it explicitly.

Hi Ben

On this issue, it should be noted that there is never a guarantee that a UA=
 will respect this extension:
 - Older UAs and the latest and greatest Internet Explorer do not support t=
his
 - Any UA that has not visited this website yet may try to access insecurel=
y
 - Any UA that has visited this website, but has not done so within the tim=
e period may try to access insecurely

A server can use HSTS to reflect a "no HTTP" policy, but it cannot be used =
to enforce a "only clients that know I'm STS" policy. That is outside the s=
cope of the draft.

A DNS-based approach could solve the TOFU issue, but older clients (or thos=
e without access to the secure DNS) could always try to get things over HTT=
P

Yoav


From jnc@mercury.lcs.mit.edu  Thu Aug  2 11:44:37 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E61DF21E8136 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 11:44:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.24
X-Spam-Level: 
X-Spam-Status: No, score=-6.24 tagged_above=-999 required=5 tests=[AWL=0.359,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lga1MhqpAzEa for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 11:44:37 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 435CC21E8128 for <ietf@ietf.org>; Thu,  2 Aug 2012 11:44:37 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 87A0318C11F; Thu,  2 Aug 2012 14:44:36 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: ITU-T Dubai Meeting
Message-Id: <20120802184436.87A0318C11F@mercury.lcs.mit.edu>
Date: Thu,  2 Aug 2012 14:44:36 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 18:44:38 -0000

    > From: Phillip Hallam-Baker <hallam@gmail.com>

    > to stop such things as 'Information terrorism' which is their term for
    > freedom of speech.

:-)

    > The current governance structure of the Internet does more than merely
    > prevent other governments from gaining control of the Internet, it
    > grants the US an extraordinary degree of control. Or at least they give
    > the appearance of doing so on paper if the checks and balances on that
    > control are not sufficiently understood.

Correct; and so it might be worth changing the structure to lessen that
_appearance_ of USG control. But if such changes increase the Internet's
vulnerabiilty to hostile, authoritarian governments, maybe that would not (in
the end) be such a good idea.

    > as with the crypto-wars the grand bargain will almost certainly mean
    > absolutely nothing.

Not necessarily - see below.

    > If the WCIT process results in an over-reach, governments can and will
    > leave the ITU.

The latter is unlikely, IMO.

    > we should instead focus on the ways that the technical architecture of
    > the Internet creates control points that are vulnerable to capture and
    > consider ways in which those control points can be made capture-proof.

Agreed.

    > The Internet has three separate potential control points: The IP Address
    > registry, the DNS name registry and the various registries for protocol
    > features.

And it is these that in my perception are really what is at risk in Dubai,
which is why I disagreed (above) that the output of Dubai will necessarily be
a NOOP.

    > We need to protect the openness of the Internet. We do not need to
    > perpetuate the existence of ICANN, IANA or the RIRs as
    > institutions. Maintaining the institutions may be a means of protecting
    > the open internet but we should be prepared to walk away from them if
    > necessary

I concur that they may be expendable, but others may differ. In particular,
will not whatever replaces them be equally targets? Yes, a shell game may
produce temporary relief, but in the end won't the replacements be equally
targeted for takeover/control?

    > If the ITU-T wants to also be in the business of handing out IPv6
    > address names then give then a /21 or a /16 and tell them to go
    > party. No really, choose your battles.

I basically agree. It could have negative impacts on the routing, by impacting
route aggregatability, but it can hardly be worse that those bletcherous PI
addresses, so if it makes them happy to be in charge of a large /N, why not?

    > What I am certain of is that we do not need to rely on the counsels of
    > those who tell us that the situation is so complex that we need not
    > worry our little heads about it.

Indeed.

	Noel

From sm@resistor.net  Thu Aug  2 13:13:54 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A5B921E80BC for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 13:13:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level: 
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V8LeaB0aHgi8 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 13:13:48 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id B9DA311E8072 for <ietf@ietf.org>; Thu,  2 Aug 2012 13:13:48 -0700 (PDT)
Received: from sm-THINK.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q72KDa4d028839; Thu, 2 Aug 2012 13:13:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1343938425; bh=KcEtzmMi5ZTlQ9qS8fUlA9e5PRjHELfKtD41Qw58+u0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=cmi6HyUC3KaC2IBcjKhzNXmauru8yfDAl6jtbEnpWqJamgfA5KhnIOHERwcyHUwYg pKhLdql9avoC0TbTkE04tbJbTZ+TQgfjBy30HrQKZ47TyHk/1hBREBnZGt6WqkaJrg 1RY1KLfzf2voZ9SGa1pSYsEu7NHIW4nxukqm6iEo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1343938425; i=@resistor.net; bh=KcEtzmMi5ZTlQ9qS8fUlA9e5PRjHELfKtD41Qw58+u0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=HijASoU6KtQScMbFfhw0b9TdxxfiBFHRHIsmGJznrJBYZLHY2YyXVgEYjRtJIeoO7 9cuREinsWDVn2amnu9XqQmWj0Bu5YZEofnVBs8BxvGyDAgE8TC8m0uXBdkDwT4ERL1 oI67TSVOZlfMUqNTeIGMC5uGwohA3Pnw0Mv7tGHU=
Message-Id: <6.2.5.6.2.20120802115334.04b486b8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 02 Aug 2012 12:55:03 -0700
To: Phillip Hallam-Baker <hallam@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: ITU-T Dubai Meeting
In-Reply-To: <CAMm+LwhKUZK9RGSmrntB6ZZVfnXRsaZfUcpWvVhWnxWRgdBjbw@mail.g mail.com>
References: <CAMm+LwhKUZK9RGSmrntB6ZZVfnXRsaZfUcpWvVhWnxWRgdBjbw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 20:13:54 -0000

Hi Phillip,
At 11:16 AM 8/2/2012, Phillip Hallam-Baker wrote:
>But there is also another side to the complaints made by Russia, China
>and others, a complaint that US dominated organizations like ICANN and
>the IETF do not allow sufficient credit for in my view. The current

Is the above about the US having a prominent say in organizations 
such as ICANN and the IETF?

>governance structure of the Internet does more than merely prevent
>other governments from gaining control of the Internet, it grants the
>US an extraordinary degree of control. Or at least they give the
>appearance of doing so on paper if the checks and balances on that
>control are not sufficiently understood.

Is there even a governance structure (see draft-bollow-ectf-02)?

>Contrary to the view expressed to me by one IESG member, there is no
>outcome here that is 'unthinkable'. Diplomats will almost invariably

What is unthinkable today may be possible tomorrow.

>The Internet has three separate potential control points: The IP
>Address registry, the DNS name registry and the various registries for
>protocol features. All three are an example of a Tinkerbell ontology:
>They exist for no other reason than that people believe in their
>existence. ICANN DNS names have relevance because there is a consensus
>that they are so, new.net DNS names are irrelevant because there is
>consensus that they are so.

Yes.

>Rather than attempting to maintain the status quo, we should instead
>identify what are the necessary concerns. We need to protect the
>openness of the Internet. We do not need to perpetuate the existence
>of ICANN, IANA or the RIRs as institutions. Maintaining the

The IETF took money from ICANN for some hors d'oeuvres and nobody objected.

>institutions may be a means of protecting the open internet but we
>should be prepared to walk away from them if necessary and in
>particular we should not defend their monopoly status at all costs.

During the last plenary it was mentioned that the IETF should not be 
self-perpetuating.

For some people the open internet is the web.  Other people see it as 
Google, Facebook and Twitter.  Would anyone on this mailing list walk 
away from these free services to protect the open internet?

>Consider for example the maintenance of IPv6 address space. Why does
>this have to be an IANA monopoly? The only necessary requirements for
>IPv6 address space is that the same space is not assigned to two
>different parties and we do not run out. If the ITU-T wants to also be
>in the business of handing out IPv6 address names then give then a /21
>or a /16 and tell them to go party. No really, choose your battles.

If the ITU-T wants a /16 it is simply a matter of asking the IETF for it.

>In conclusion, there is an issue here but not a cause for the panic
>that many seem to suggest. The situation is certainly complex, but not
>one that is too complex for mortal understanding. What I am certain of
>is that we do not need to rely on the counsels of those who tell us
>that the situation is so complex that we need not worry our little
>heads about it. In fact I believe the exact opposite: The openness of

Yes.

Regards,
-sm 


From drc@virtualized.org  Thu Aug  2 13:24:13 2012
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 C2AC511E8125 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 13:24:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MiMyPVzc8QT7 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 13:24:12 -0700 (PDT)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id AF92811E8072 for <ietf@ietf.org>; Thu,  2 Aug 2012 13:24:12 -0700 (PDT)
Received: from [10.0.1.8] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: drc) by trantor.virtualized.org (Postfix) with ESMTPSA id 6901F1705A; Thu,  2 Aug 2012 20:24:05 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: ITU-T Dubai Meeting
From: David Conrad <drc@virtualized.org>
In-Reply-To: <20120802184436.87A0318C11F@mercury.lcs.mit.edu>
Date: Thu, 2 Aug 2012 13:24:04 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B6033EB2-3B90-4524-A123-38852C5E2698@virtualized.org>
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu>
To: jnc@mercury.lcs.mit.edu (Noel Chiappa)
X-Mailer: Apple Mail (2.1485)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 20:24:13 -0000

On Aug 2, 2012, at 11:44 AM, jnc@mercury.lcs.mit.edu (Noel Chiappa) =
wrote:
>> we should instead focus on the ways that the technical architecture =
of
>> the Internet creates control points that are vulnerable to capture =
and
>> consider ways in which those control points can be made =
capture-proof.
>=20
> Agreed.

The challenge of course is that one of the simple/efficient mechanisms =
to implement desirable features (e.g., security, scalability, =
manageability) is to create hierarchies, but those very hierarchies =
provide control points that can (at least in theory) be captured.  The =
DNS root is one such, the proposed RPKI root is another.  Perhaps a =
variation of the Software Engineering Dilemma ("fast, good, cheap: pick =
two") applies to Internet architecture: secure, scalable, manageable: =
pick two?

>> If the ITU-T wants to also be in the business of handing out IPv6
>> address names then give then a /21 or a /16 and tell them to go
>> party.

I don't think this is what the ITU is after.  My impression is that the =
ITU is arguing that member states should get the /<whatever> directly.

> I basically agree. It could have negative impacts on the routing, by =
impacting
> route aggregatability, but it can hardly be worse that those =
bletcherous PI
> addresses, so if it makes them happy to be in charge of a large /N, =
why not?

I believe the routing scalability risk lies not in the allocation body, =
but rather the policies imposed around the allocations.  That is, =
imagine a world of 200+ National Internet Registries instead of 5 =
Regional Internet registries.  If the government behind an NIR then =
decides that to use the Internet in their country, you must use =
addresses allocated by the NIR of that country, you then run the risk of =
having 200+ prefixes for each entity that operates globally.  This risk =
could be addressed if it didn't matter where you get your addresses, =
however that isn't true with the existing model and there are political =
pressures that would likely ensure that it would not be true in the NIR =
model.

There are also risks associated with upkeep of registration data, which =
is already a challenge with the existing limited set of registries.  I =
imagine this would get worse with more registries.

Regards,
-drc




From housley@vigilsec.com  Thu Aug  2 13:28:02 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11E5A21F8978 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 13:28:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.62
X-Spam-Level: 
X-Spam-Status: No, score=-102.62 tagged_above=-999 required=5 tests=[AWL=-0.021, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GyqGqARhWnJH for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 13:28:01 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 8EF1E21F8976 for <ietf@ietf.org>; Thu,  2 Aug 2012 13:28:01 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 8B8B0F2403B; Thu,  2 Aug 2012 16:28:06 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id vyCGDCq3w9ZV; Thu,  2 Aug 2012 16:27:57 -0400 (EDT)
Received: from dhcp-55b9.meeting.ietf.org (dhcp-55b9.meeting.ietf.org [130.129.85.185]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 54033F2403F; Thu,  2 Aug 2012 16:28:05 -0400 (EDT)
Subject: Progress with Open Internet endowment
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <019d01cd70e6$fe6dcc50$fb4964f0$@olddog.co.uk>
Date: Thu, 2 Aug 2012 16:27:58 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <42A8E91A-9802-4BFA-B245-B67F1B9E1ACE@vigilsec.com>
References: <019d01cd70e6$fe6dcc50$fb4964f0$@olddog.co.uk>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: oie@internetsociety.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 20:28:02 -0000

Our current totals as of noon today, the Open Internet Endowment has =
received $19,245 from 54 donors.  Thanks to all.

It would be great to reach $25,000 (or more) from 75 donors (or more) by =
lunch tomorrow.  Please help if you can.

There will be a table at the Bits-N-Bites tonight.  People will be at =
the table to answer any questions you might have.

Thanks,
  Russ


From smb@cs.columbia.edu  Thu Aug  2 13:30:15 2012
Return-Path: <smb@cs.columbia.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB4FA11E808E for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 13:30:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h7ZR6vWBJ74x for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 13:30:13 -0700 (PDT)
Received: from salak.cc.columbia.edu (salak.cc.columbia.edu [128.59.29.6]) by ietfa.amsl.com (Postfix) with ESMTP id 6EF5411E8087 for <ietf@ietf.org>; Thu,  2 Aug 2012 13:30:04 -0700 (PDT)
Received: from [10.9.0.82] (fireball.cs.columbia.edu [128.59.13.10]) (user=smb2132 mech=PLAIN bits=0) by salak.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id q72KU1H6012340 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 2 Aug 2012 16:30:02 -0400 (EDT)
Subject: Re: ITU-T Dubai Meeting
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <B6033EB2-3B90-4524-A123-38852C5E2698@virtualized.org>
Date: Thu, 2 Aug 2012 13:30:01 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <4401D68C-F9BB-4777-845A-A7011C50F1EA@cs.columbia.edu>
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu> <B6033EB2-3B90-4524-A123-38852C5E2698@virtualized.org>
To: David Conrad <drc@virtualized.org>
X-Mailer: Apple Mail (2.1278)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.6
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 20:30:15 -0000

On Aug 2, 2012, at 1:24 PM, David Conrad wrote:

> On Aug 2, 2012, at 11:44 AM, jnc@mercury.lcs.mit.edu (Noel Chiappa) =
wrote:
>>> we should instead focus on the ways that the technical architecture =
of
>>> the Internet creates control points that are vulnerable to capture =
and
>>> consider ways in which those control points can be made =
capture-proof.
>>=20
>> Agreed.
>=20
> The challenge of course is that one of the simple/efficient mechanisms =
to implement desirable features (e.g., security, scalability, =
manageability) is to create hierarchies, but those very hierarchies =
provide control points that can (at least in theory) be captured.  The =
DNS root is one such, the proposed RPKI root is another.  Perhaps a =
variation of the Software Engineering Dilemma ("fast, good, cheap: pick =
two") applies to Internet architecture: secure, scalable, manageable: =
pick two?
>=20
>>> If the ITU-T wants to also be in the business of handing out IPv6
>>> address names then give then a /21 or a /16 and tell them to go
>>> party.
>=20
> I don't think this is what the ITU is after.  My impression is that =
the ITU is arguing that member states should get the /<whatever> =
directly.
>=20
>> I basically agree. It could have negative impacts on the routing, by =
impacting
>> route aggregatability, but it can hardly be worse that those =
bletcherous PI
>> addresses, so if it makes them happy to be in charge of a large /N, =
why not?
>=20
> I believe the routing scalability risk lies not in the allocation =
body, but rather the policies imposed around the allocations.  That is, =
imagine a world of 200+ National Internet Registries instead of 5 =
Regional Internet registries.  If the government behind an NIR then =
decides that to use the Internet in their country, you must use =
addresses allocated by the NIR of that country, you then run the risk of =
having 200+ prefixes for each entity that operates globally.  This risk =
could be addressed if it didn't matter where you get your addresses, =
however that isn't true with the existing model and there are political =
pressures that would likely ensure that it would not be true in the NIR =
model.


It also implies entry into a country through a few official =
gateways/exchange points -- that way, there are only ~200 entries plus =
your own country's that you need in your RIB...  (Telecom used to be =
that way -- PTTs and other monopolies (e.g., AT&T) loved it.)

		--Steve Bellovin, https://www.cs.columbia.edu/~smb






From hallam@gmail.com  Thu Aug  2 13:41:18 2012
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31A6E21F8976 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 13:41:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.578
X-Spam-Level: 
X-Spam-Status: No, score=-5.578 tagged_above=-999 required=5 tests=[AWL=-1.979, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H8JKnYjElehp for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 13:41:17 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0523921F8620 for <ietf@ietf.org>; Thu,  2 Aug 2012 13:41:16 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so16288817obb.31 for <ietf@ietf.org>; Thu, 02 Aug 2012 13:41:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=d/E+4eb+KX1mmneRj1Cv64wDyUh9MpFe4v0KIEVfrfA=; b=id14HnBylSl84N9y4JvkfsF3RC3GjKNkJVHwRBxKVOizRrKXJ+9KOiXbEFVpfA97KI LavOwNzaYcsKYBcY9nGWgGB5I9rQ8YSYA/jrStfLy8r4784/K6+xxKl1onuChcSysQK3 QIbQn+IGg4jUfkAicBu4R7CsB+wVsyZds7I7DZj4h1OLvpuesb8gMbpy7sQNvpySLpYi ZPqWS7CVpCevwTSFvH+G8YoS0F9UZX2XAdu9JgLux0tDppMH58he6qFwsM+tHqQJss7U O7s2MgqUnImBSaoL89/Yu1QpHjm440T/VhIwf4gW/I4R3GkYPQBGZQ+l2uxAIGOAProv /w+g==
MIME-Version: 1.0
Received: by 10.182.136.2 with SMTP id pw2mr39652231obb.54.1343940076524; Thu, 02 Aug 2012 13:41:16 -0700 (PDT)
Received: by 10.76.133.104 with HTTP; Thu, 2 Aug 2012 13:41:16 -0700 (PDT)
In-Reply-To: <20120802184436.87A0318C11F@mercury.lcs.mit.edu>
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu>
Date: Thu, 2 Aug 2012 13:41:16 -0700
Message-ID: <CAMm+Lwg2HgO-=9ED4vbmO+Vf9r6bYPcLDgfyMAyPdEPVgRm4LQ@mail.gmail.com>
Subject: Re: ITU-T Dubai Meeting
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 20:41:18 -0000

On Thu, Aug 2, 2012 at 11:44 AM, Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
>     > From: Phillip Hallam-Baker <hallam@gmail.com>
>
>     > to stop such things as 'Information terrorism' which is their term for
>     > freedom of speech.
>
> :-)

The term comes up in their treaty.

>     > If the WCIT process results in an over-reach, governments can and will
>     > leave the ITU.
>
> The latter is unlikely, IMO.

If the ITU were to over-reach and get away with it then it will not
have over-reached by definition.

One of the factors here is that a lot of the diplomats working on
'cyber' (aka information engagement, cyber security, etc. etc.) began
by working on arms limitation treaties. This turns out to be self
reinforcing as once the US has a person from that world in their
delegation the Russians will add someone who was part of earlier
negotiations with her and vice versa.

Nuclear deterrence is a viable strategy because nuclear weapons are
difficult to make which makes the attribution problem tractable and
thus enables a credible threat of consequences. Techies know that
Cyber deterrence is obviously unworkable because attribution is not
possible. We can track an IP packet to Iran but we cannot state with
certainty who controlled the computer who sent it. The diplomats know
that this is the case but really can't accept that it is the case
because they are trying to cram cyber into their 'deterrence'
framework.

Cyber-attacks should be considered a form of terrorism. The barrier to
entry is low, the consequences are disproportionate to the effort but
fall far short of a conventional attack. At this point we are at the
same stage of understanding of cyber as the diplomatic community was
with terrorism in the mid 1960s when the terrorist movements began to
become active in Europe. The US government is doing damn stupid things
like attacking civil nuclear facilities and the Russians are doing
stuff that is equally stupid.

The challenge we face is how to define the border between a cyber
attack (i.e. an act of war) and cyber-espionage (which is not
considered warfare in law). I do not take offense at the Chinese
government enacting a DIY reparations program for the 'open door'
policy and the opium wars. I am going to do my best to help my
customers stop them, but they are acting within their rights.


>     > The Internet has three separate potential control points: The IP Address
>     > registry, the DNS name registry and the various registries for protocol
>     > features.
>
> And it is these that in my perception are really what is at risk in Dubai,
> which is why I disagreed (above) that the output of Dubai will necessarily be
> a NOOP.

Yes, it is all about the registries.

>     > We need to protect the openness of the Internet. We do not need to
>     > perpetuate the existence of ICANN, IANA or the RIRs as
>     > institutions. Maintaining the institutions may be a means of protecting
>     > the open internet but we should be prepared to walk away from them if
>     > necessary
>
> I concur that they may be expendable, but others may differ. In particular,
> will not whatever replaces them be equally targets? Yes, a shell game may
> produce temporary relief, but in the end won't the replacements be equally
> targeted for takeover/control?

That depends on whether the registry in question is dealing with a
scarce resource or a plentiful one. Having two registries handing out
IPv4 addresses at this point would be very very bad. Having more than
one place you can get an IPv6 from would not worry me at all.


>     > If the ITU-T wants to also be in the business of handing out IPv6
>     > address names then give then a /21 or a /16 and tell them to go
>     > party. No really, choose your battles.
>
> I basically agree. It could have negative impacts on the routing, by impacting
> route aggregatability, but it can hardly be worse that those bletcherous PI
> addresses, so if it makes them happy to be in charge of a large /N, why not?

SM also commented on this:

> If the ITU-T wants a /16 it is simply a matter of asking the IETF for it.

No, if the ITU-T really wants to do this it is just a matter of them
taking it. This happens repeatedly in registry schemes. They could ask
the IETF for a /16 or they could simply send a message informing us
that they will be allocating out of (say) 2F00::/16 from now on and
that it would be 'inadvisable' for IANA, ICANN, IETF or whoever to
grant competing allocations.

If people choose to route packets for the corresponding BGP adverts
then they get away with it. If they can't do that then we don't need
to worry about them anyway.


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

From dworley@avaya.com  Thu Aug  2 13:59:03 2012
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 A2D9121E808B for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 13:59:03 -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.157, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D+uBszIn3iGb for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 13:59:02 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id AA1F221E803A for <ietf@ietf.org>; Thu,  2 Aug 2012 13:59:02 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAL7pGlDGmAcF/2dsb2JhbABFuRuBB4IgAQEBAQIBEig/BQsCAQgNCCEQIRElAQEEAQ0FCBMHh1wDBgafe5NyDYlOimOHC2ADk3MBh1CFDYUDgns
X-IronPort-AV: E=Sophos;i="4.77,703,1336363200"; d="scan'208";a="20871723"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 02 Aug 2012 16:52:56 -0400
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by co300216-co-erhwest-out.avaya.com with ESMTP; 02 Aug 2012 16:53:47 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Thu, 2 Aug 2012 16:58:14 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>, SM <sm@resistor.net>
Date: Thu, 2 Aug 2012 16:58:14 -0400
Subject: RE: Oauth blog post
Thread-Topic: Oauth blog post
Thread-Index: Ac1wycZZlGFeBPaQS4aZei/RSpLG3wAJuobm
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0BED@DC-US1MBEX4.global.avaya.com>
References: <501531F7.5040404@gmail.com> <6.2.5.6.2.20120729073422.06d8fe10@resistor.net> <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net> <6.2.5.6.2.20120730101231.047f2550@resistor.net>, <CAL0qLwYNRW6FSC4kMQkn81+4HgKdv591D43Z31rLAg3ArRsSZg@mail.gmail.com>
In-Reply-To: <CAL0qLwYNRW6FSC4kMQkn81+4HgKdv591D43Z31rLAg3ArRsSZg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 20:59:03 -0000

> From: Murray S. Kucherawy [superuser@gmail.com]
>=20
> I think it's impossible to determine with certainty whether someone
> standing at the mic and asserting a position is doing so based on what
> an employer is insisting on doing, or that person's opinion.

But it is possible, over a period of time, to get a good estimate of
whether someone promotes technically poor solutions that are
commercially advantageous for their employers.

Indeed, relative to our fundamental principle of openness, "All may
speak; not all are listened to.", in order to be listened to, someone
has to spend some time to establish a reputation for technical quality
of their contributions, and not being a shill for poor ideas advanced
by their employers.

Dale

From glenzorn@gmail.com  Thu Aug  2 14:17:26 2012
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A150A11E8180 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 14:17:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.368
X-Spam-Level: 
X-Spam-Status: No, score=-3.368 tagged_above=-999 required=5 tests=[AWL=0.230,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id anio89Nv6+gH for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 14:17:26 -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 EDCDF11E8186 for <ietf@ietf.org>; Thu,  2 Aug 2012 14:17:25 -0700 (PDT)
Received: by yenq13 with SMTP id q13so10003173yen.31 for <ietf@ietf.org>; Thu, 02 Aug 2012 14:17:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer; bh=9xOwqbH/E0VJCrSh282AO1dpU8JieisL0Uns8t0q3kg=; b=uTek8WjY8bhJeOiIcHT8v5Wn+Os1R/dApIBxEgDNw5SSq6PKQicChtpPfmUWjXRrNp 2jrjdwS1VpsLHPJuwU4kSPhg454waTb7ZuXkErbUIXxw2xLFSHbNK/c5Nzuq73jEfxN+ Z6C8QJOL7IRmHd+0Ttc/3tfOG2tg2FbuuOWJ/gR3yPo1JqWY8y2CIPbtXoQ9ooR0cLmY SNoz4wcFajH/hvdTmoJWlmSpyQuNH0xnlY8am+M3cMAxaAso0PjM8fxNXEB3t8GI+Rt4 NnMS3SziuMdpo4A9M8d9krg1NG6qHhsLCcAqEgGGURoEB1jy76T7sCFJXLUT97+3HHnb c8Mw==
Received: by 10.60.1.69 with SMTP id 5mr39850728oek.66.1343942245501; Thu, 02 Aug 2012 14:17:25 -0700 (PDT)
Received: from [10.0.1.195] (216-19-185-109.dyn.novuscom.net. [216.19.185.109]) by mx.google.com with ESMTPS id k3sm534773obw.4.2012.08.02.14.17.23 (version=SSLv3 cipher=OTHER); Thu, 02 Aug 2012 14:17:24 -0700 (PDT)
Subject: RE: Oauth blog post
From: Glen Zorn <glenzorn@gmail.com>
To: ietf@ietf.org
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A0BED@DC-US1MBEX4.global.avaya.com>
References: <501531F7.5040404@gmail.com> <6.2.5.6.2.20120729073422.06d8fe10@resistor.net> <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net> <6.2.5.6.2.20120730101231.047f2550@resistor.net> , <CAL0qLwYNRW6FSC4kMQkn81+4HgKdv591D43Z31rLAg3ArRsSZg@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22726A0BED@DC-US1MBEX4.global.avaya.com>
Content-Type: multipart/alternative; boundary="=-beTYoOek7X/Fqh6d9PrW"
Organization: Network Zen
Date: Thu, 02 Aug 2012 14:17:21 -0700
Message-ID: <1343942242.17758.26.camel@gwz-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 21:17:26 -0000

--=-beTYoOek7X/Fqh6d9PrW
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

On Thu, 2012-08-02 at 16:58 -0400, Worley, Dale R (Dale) wrote:

> > From: Murray S. Kucherawy [superuser@gmail.com]
> > 
> > I think it's impossible to determine with certainty whether someone
> > standing at the mic and asserting a position is doing so based on what
> > an employer is insisting on doing, or that person's opinion.
> 
> But it is possible, over a period of time, to get a good estimate of
> whether someone promotes technically poor solutions that are
> commercially advantageous for their employers.


Yes; those people generally (but not always) have fairly poor success
rates; OTOH, a lot of nonsense can be accomplished 
with sufficient manpower.


> 
> Indeed, relative to our fundamental principle of openness, "All may
> speak; not all are listened to.", in order to be listened to, someone
> has to spend some time to establish a reputation for technical quality
> of their contributions, and not being a shill for poor ideas advanced
> by their employers.


I suppose that that may be one reason why my experiences with corporate
manipulation (or domination, if you prefer) of the IETF have been of 
people with those very reputations blocking good ideas that threatened
the interests of their  employer.  It's pretty hard to get things done
in the IETF,
but quite easy to stop things, especially if one is in a position of
power.


> 
> Dale



--=-beTYoOek7X/Fqh6d9PrW
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
On Thu, 2012-08-02 at 16:58 -0400, Worley, Dale R (Dale) wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
&gt; From: Murray S. Kucherawy [<A HREF="mailto:superuser@gmail.com">superuser@gmail.com</A>]
&gt; 
&gt; I think it's impossible to determine with certainty whether someone
&gt; standing at the mic and asserting a position is doing so based on what
&gt; an employer is insisting on doing, or that person's opinion.

But it is possible, over a period of time, to get a good estimate of
whether someone promotes technically poor solutions that are
commercially advantageous for their employers.
</PRE>
</BLOCKQUOTE>
<BR>
Yes; those people generally (but not always) have fairly poor success rates; OTOH, a lot of nonsense can be accomplished <BR>
with sufficient manpower.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>

Indeed, relative to our fundamental principle of openness, &quot;All may
speak; not all are listened to.&quot;, in order to be listened to, someone
has to spend some time to establish a reputation for technical quality
of their contributions, and not being a shill for poor ideas advanced
by their employers.
</PRE>
</BLOCKQUOTE>
<BR>
I suppose that that may be one reason why my experiences with corporate manipulation (or domination, if you prefer) of the IETF have been of <BR>
people with those very reputations blocking good ideas that threatened the interests of their&nbsp; employer.&nbsp; It's pretty hard to get things done in the IETF,<BR>
but quite easy to stop things, especially if one is in a position of power.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>

Dale
</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>

--=-beTYoOek7X/Fqh6d9PrW--


From dougb@dougbarton.us  Thu Aug  2 14:30:56 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E45E021F896D for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 14:30:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mdkBuY+v+Ttp for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 14:30:56 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 9116021F89DD for <ietf@ietf.org>; Thu,  2 Aug 2012 14:30:49 -0700 (PDT)
Received: (qmail 25039 invoked by uid 399); 2 Aug 2012 21:30:40 -0000
Received: from unknown (HELO ?172.17.127.241?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 2 Aug 2012 21:30:40 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <501AF187.3020408@dougbarton.us>
Date: Thu, 02 Aug 2012 14:30:47 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: ITU-T Dubai Meeting
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu> <B6033EB2-3B90-4524-A123-38852C5E2698@virtualized.org>
In-Reply-To: <B6033EB2-3B90-4524-A123-38852C5E2698@virtualized.org>
X-Enigmail-Version: 1.4.3
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: Thu, 02 Aug 2012 21:30:57 -0000

On 8/2/2012 1:24 PM, David Conrad wrote:
> On Aug 2, 2012, at 11:44 AM, jnc@mercury.lcs.mit.edu (Noel Chiappa) wrote:
>>> we should instead focus on the ways that the technical architecture of
>>> the Internet creates control points that are vulnerable to capture and
>>> consider ways in which those control points can be made capture-proof.
>>
>> Agreed.
> 
> The challenge of course is that one of the simple/efficient mechanisms to implement desirable features (e.g., security, scalability, manageability) is to create hierarchies, but those very hierarchies provide control points that can (at least in theory) be captured.  The DNS root is one such, the proposed RPKI root is another.  Perhaps a variation of the Software Engineering Dilemma ("fast, good, cheap: pick two") applies to Internet architecture: secure, scalable, manageable: pick two?
> 
>>> If the ITU-T wants to also be in the business of handing out IPv6
>>> address names then give then a /21 or a /16 and tell them to go
>>> party.
> 
> I don't think this is what the ITU is after.  My impression is that the ITU is arguing that member states should get the /<whatever> directly.
> 
>> I basically agree. It could have negative impacts on the routing, by impacting
>> route aggregatability, but it can hardly be worse that those bletcherous PI
>> addresses, so if it makes them happy to be in charge of a large /N, why not?
> 
> I believe the routing scalability risk lies not in the allocation body, but rather the policies imposed around the allocations.  That is, imagine a world of 200+ National Internet Registries instead of 5 Regional Internet registries.  If the government behind an NIR then decides that to use the Internet in their country, you must use addresses allocated by the NIR of that country, you then run the risk of having 200+ prefixes for each entity that operates globally.  This risk could be addressed if it didn't matter where you get your addresses, however that isn't true with the existing model and there are political pressures that would likely ensure that it would not be true in the NIR model.
> 
> There are also risks associated with upkeep of registration data, which is already a challenge with the existing limited set of registries.  I imagine this would get worse with more registries.

In addition to the very valid points that David made, there are also
other risks. Such as, if the national government is the only source of
IP addresses then they have much greater control over who can get on the
network in-country. And if all of the traffic from a given country is
coming into my country via the same prefix it makes it that much easier
to apply censorship, tariffs, etc.

The whole concept of a global network, with no centralized control, that
permits (nay, encourages) the free flow of information is anathema to
many national governments. They are desperate to choke that off, by any
means necessary.

Doug

-- 

    I am only one, but I am one.  I cannot do everything, but I can do
    something.  And I will not let what I cannot do interfere with what
    I can do.
			-- Edward Everett Hale, (1822 - 1909)

From hannes.tschofenig@gmx.net  Thu Aug  2 14:35:14 2012
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB4DA21F88E5 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 14:35:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f2BjenCQtDy4 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 14:35: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 D7A8C21F85AD for <ietf@ietf.org>; Thu,  2 Aug 2012 14:35:13 -0700 (PDT)
Received: (qmail invoked by alias); 02 Aug 2012 21:35:11 -0000
Received: from dhcp-172b.meeting.ietf.org (EHLO dhcp-172b.meeting.ietf.org) [130.129.23.43] by mail.gmx.net (mp029) with SMTP; 02 Aug 2012 23:35:11 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX18FRLUv+qoFBJ4dBLoD038ppwq9YSNCNsvpRBF8yq yemwHDK6AjLN5T
Subject: Re: Oauth blog post
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: <CD5674C3CD99574EBA7432465FC13C1B22726A0BED@DC-US1MBEX4.global.avaya.com>
Date: Thu, 2 Aug 2012 14:35:08 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <CABC742E-0DD2-412D-B60E-879C30D01769@gmx.net>
References: <501531F7.5040404@gmail.com> <6.2.5.6.2.20120729073422.06d8fe10@resistor.net> <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net> <6.2.5.6.2.20120730101231.047f2550@resistor.net>, <CAL0qLwYNRW6FSC4kMQkn81+4HgKdv591D43Z31rLAg3ArRsSZg@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22726A0BED@DC-US1MBEX4.global.avaya.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
X-Mailer: Apple Mail (2.1084)
X-Y-GMX-Trusted: 0
Cc: SM <sm@resistor.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 21:35:15 -0000

In the identity management case we are not necessarily talking about =
solutions that are "good" or "bad". The issue is that certain people =
care about one use case and other people care about other use cases.  I =
use the term "use case" in a generic sense to also include certain =
deployment assumptions (e.g., has to work with existing programming =
languages, deployment environments), or design themes (e.g., XML vs. =
JSON).=20

So, for example, in the OAuth case there are people who care a lot about =
different Websites sharing data between each other (the photo sharing / =
photo printing use case). Again others think that the smart phone use =
case is more important. The solutions for these two cases are slightly =
different (because they can rely on different assumptions).=20

Initially, people start with a single use case they care about. The work =
gets attention and other people start to use the protocol as well and =
notice that it does not meet their use cases. So, they add =
functionality. Over time the set of specification becomes more complex =
and a beginner does not see through the specification jungle anymore. =
Then, these newcomers start from scratch to fix all these "complex =
protocols". Typically, these persons like to reject any idea that was =
done in the past (such as learning from the experience the previous =
generation had made). The cycle starts from the beginning. We went =
through these cycles several times already in the identity management =
world.=20

We had seen this with the transition from Kerberos to SAML, from SAML to =
OpenID, from OpenID to OAuth.=20

At some point we should ask ourselves whether the problem that is being =
solved is multi-faceted and the resulting solution will just not be a 10 =
page document (unless it is incomplete).=20

I believe that application developers shouldn't even worry about the =
details of the protocol suite. They should be using a library instead. =
We use libraries all the time and particularly with security protocols. =
Take TLS as an example. No application developer would come up with the =
idea to write their own TLS stack either. They let security =
professionals write those libraries.=20


On Aug 2, 2012, at 1:58 PM, Worley, Dale R (Dale) wrote:

>> From: Murray S. Kucherawy [superuser@gmail.com]
>>=20
>> I think it's impossible to determine with certainty whether someone
>> standing at the mic and asserting a position is doing so based on =
what
>> an employer is insisting on doing, or that person's opinion.
>=20
> But it is possible, over a period of time, to get a good estimate of
> whether someone promotes technically poor solutions that are
> commercially advantageous for their employers.
>=20
> Indeed, relative to our fundamental principle of openness, "All may
> speak; not all are listened to.", in order to be listened to, someone
> has to spend some time to establish a reputation for technical quality
> of their contributions, and not being a shill for poor ideas advanced
> by their employers.
>=20
> Dale


From agmalis@gmail.com  Thu Aug  2 14:42:39 2012
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C87F21F8AA9 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 14:42:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.192
X-Spam-Level: 
X-Spam-Status: No, score=-3.192 tagged_above=-999 required=5 tests=[AWL=0.407,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VD+d9F4RVa2l; Thu,  2 Aug 2012 14:42:39 -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 D35D621F8860; Thu,  2 Aug 2012 14:42:38 -0700 (PDT)
Received: by yhq56 with SMTP id 56so9156yhq.31 for <multiple recipients>; Thu, 02 Aug 2012 14:42:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=SBtYLImKhnSrmuljdOBlKtsBl7z68RibPrsG5kZ7apI=; b=it+RXDsRmwxGXXRJJmkMDGxPskXSrV/7+y7OW7kLPm0UKKTcDqnbq1dNIbYHQfxgb7 sb2SlBobtyUXv4g2PGWUEplsrpM9T89TB3F+Xs5hnY+EeEYtNppRT+hFwjAVpw45Bqr8 N/IpmN7/ubuQeUxkWJbC5cv549RTcr/gO5DgDVa5T/20R/eeY6jZBvnC4g1Aaju/43NO XRyNw3wbgNXJ04B3Yv2rG6mAjDs7TsMqliaAetWFqNOOZF61mSjv9xw1A/BGaruRARTl H0WPFAJCbaGmN6sOBhnJz1BXWDoT6ygisKKcF/R8AJA6VVx/BgBsqnBC7Do0G/luhjY4 k+OQ==
Received: by 10.43.126.1 with SMTP id gu1mr6033214icc.6.1343943758150; Thu, 02 Aug 2012 14:42:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.90.229 with HTTP; Thu, 2 Aug 2012 14:42:17 -0700 (PDT)
In-Reply-To: <20120802164551.20569.2082.idtracker@ietfa.amsl.com>
References: <20120802164551.20569.2082.idtracker@ietfa.amsl.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Thu, 2 Aug 2012 14:42:17 -0700
Message-ID: <CAA=duU0sByW_tkMupo-Ae8+9f3_-YN9yYT_g57tkbys7CwVjyQ@mail.gmail.com>
Subject: Re: Proposed IETF 95 Date Change
To: IETF Administrative Director <iad@ietf.org>
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: Thu, 02 Aug 2012 21:42:39 -0000

Both the original and the proposed new dates are fine with me. Note
that anyone planning on traveling on 26 March (the day before Easter)
should probably make their reservations well ahead of time. On the
other hand, travel on 27 March should be relatively easy.

Cheers,
Andy

On Thu, Aug 2, 2012 at 9:45 AM, IETF Administrative Director
<iad@ietf.org> wrote:
> A reminder of the 6 August deadline for input.
> Thanks
>
> The IAOC is seeking community feedback on a proposed date change for IETF 95
> scheduled for March 2016.
>
> Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27 March is Easter.
>
> The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 and would like
> feedback on those dates before making a decision.  Comments appreciated to ietf@ietf.org
> by 6 August 2012.
>
> Ray Pelletier
> IETF Administrative Director

From robert@raszuk.net  Thu Aug  2 14:50:25 2012
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 82E7A11E8144 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 14:50:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.297
X-Spam-Level: 
X-Spam-Status: No, score=-2.297 tagged_above=-999 required=5 tests=[AWL=0.302,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tmZ1MJT559pj for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 14:50:23 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 1453C11E8118 for <ietf@ietf.org>; Thu,  2 Aug 2012 14:50:13 -0700 (PDT)
Received: (qmail 14416 invoked by uid 399); 2 Aug 2012 21:50:06 -0000
Received: from unknown (HELO ?130.129.17.10?) (pbs:m42@mojaklasa.info@130.129.17.10) by mail1310.opentransfer.com with ESMTPM; 2 Aug 2012 21:50:06 -0000
X-Originating-IP: 130.129.17.10
Message-ID: <501AF60E.5080707@raszuk.net>
Date: Thu, 02 Aug 2012 23:50:06 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
Subject: Re: Basic ietf process question ...
References: <CC403A23.1BE60%jhildebr@cisco.com>
In-Reply-To: <CC403A23.1BE60%jhildebr@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Thu, 02 Aug 2012 21:50:26 -0000

Hi Joe,

Many thx for your comments.

Perhaps my intentions were not very well described. Personally I am not 
that much stuck on plain XML schema .. it could be expressed in any 
language IETF would choose to use. The point is not how to do it .. but 
to do it at the moment of bringing new protocol extension.

However for years the same functionality is completely different to 
configure using one vendor from other vendor (leave alone that even 
within single vendor there are complete different UIs to provision the 
same knob).

If anyone is even remotely serious about some form of common network OS 
IMHO the first step is to create unified configuration abstraction. The 
xml schema for each proto extension would be just a standard based API 
for configuration input.

Keep in mind that today routers are configured by scripts from central 
management clusters where there are tons of templates which in fact 
completely differ from vendor to vendor and their maintenance and 
keeping them up to date is a real pain.

Regards,
R.


> On 8/2/12 9:25 AM, "Robert Raszuk" <robert@raszuk.net> wrote:
>
>> Does anyone have a good reason why any new protocol definition or
>> enhancement does not have a build in mandatory "XML schema" section
>> which would allow to actually use such standards based enhancement in
>> vendor agnostic way ?
>
> For docs that use XML, requiring some form of schema makes sense.
> However, what we're finding at the application layer is that often times
> using JSON (see RFC 4627) ends up with better interoperability more
> quickly than using XML, except in the case of human-readable content like
> marked-up text.  See RFC 6120, Appendix A (http://goo.gl/CBv8G) for
> another example.
>
> For those that insist on XML, RelaxNG (http://goo.gl/MYnB1) is another
> language you can use to describe your XML, which is a little easier to
> learn than XSD.
>
> However, for implementors, if you start with the schema and blindly use it
> for conformance checking of real-world traffic, you are likely to have
> both performance and extensibility issues in practice.
>
> If folks at other layers in the stack would like input from Apps folks,
> I'm sure that we would be happy to share our lessons learned.  Join
> apps-discuss (http://goo.gl/0Otjv) and ask for help.
>


From hannes.tschofenig@gmx.net  Thu Aug  2 14:50:30 2012
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9170511E814B for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 14:50:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fa2T3ngPTYyA for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 14:50:29 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 276AA11E8127 for <ietf@ietf.org>; Thu,  2 Aug 2012 14:50:28 -0700 (PDT)
Received: (qmail invoked by alias); 02 Aug 2012 21:50:27 -0000
Received: from dhcp-172b.meeting.ietf.org (EHLO dhcp-172b.meeting.ietf.org) [130.129.23.43] by mail.gmx.net (mp016) with SMTP; 02 Aug 2012 23:50:27 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/sibxInuLsxaGAHFhuA4CsMiOVIEqBp5um8BcJit v88oN3PibS3Y2w
Subject: Re: Oauth blog post
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: <6.2.5.6.2.20120730101231.047f2550@resistor.net>
Date: Thu, 2 Aug 2012 14:50:24 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <899D5D51-BA0D-49C0-9F30-D94BB40E4EC2@gmx.net>
References: <501531F7.5040404@gmail.com> <6.2.5.6.2.20120729073422.06d8fe10@resistor.net> <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net> <6.2.5.6.2.20120730101231.047f2550@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1084)
X-Y-GMX-Trusted: 0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 21:50:31 -0000

Hi SM,=20

On Jul 30, 2012, at 10:21 AM, SM wrote:

> Hi Hannes,
> At 12:19 PM 7/29/2012, Hannes Tschofenig wrote:
>> The IETF allows open participation and, as such, everyone, including =
companies that develop enterprise software, are free to participate in =
the discussions.
>>=20
>> Do you think open participation is wrong?
>=20
> It depends on what open participation means in the above.  If it is =
open participation by companies, I don't have any problem with it as =
long as the relevant BCPs are updated to reflect that.
>=20

I believe you know what open participation in the IETF means.=20

In fact, for the IETF openness means more than for many other SDOs where =
"open" means you can join if you pay a substantial amount of money every =
year.=20

> At 11:14 AM 7/29/2012, Tschofenig, Hannes (NSN - FI/Espoo) wrote:
>> I would find it useful if anyone of you who likes to agree or =
disagree to have at least read the OAuth specification. I had noticed =
that many of those who share their valuable thoughts have not even spent =
the time to look at the document.
>=20
> I wonder whether I read the OAuth2 specifications. :-)

I hope you did. I had also given various tutorials during IETF =
meetings...

Ciao
Hannes

>=20
> Regards,
> -sm =20


From smb@cs.columbia.edu  Thu Aug  2 14:53:07 2012
Return-Path: <smb@cs.columbia.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF0BE11E8118 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 14:53: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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UKuyLZIc+ful for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 14:53:05 -0700 (PDT)
Received: from salak.cc.columbia.edu (salak.cc.columbia.edu [128.59.29.6]) by ietfa.amsl.com (Postfix) with ESMTP id 7C75011E8144 for <ietf@ietf.org>; Thu,  2 Aug 2012 14:53:05 -0700 (PDT)
Received: from [10.9.0.82] (fireball.cs.columbia.edu [128.59.13.10]) (user=smb2132 mech=PLAIN bits=0) by salak.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id q72Lr2j4028559 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 2 Aug 2012 17:53:02 -0400 (EDT)
Subject: Re: ITU-T Dubai Meeting
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <501AF187.3020408@dougbarton.us>
Date: Thu, 2 Aug 2012 14:53:01 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <97FDD5BF-21F8-4538-9966-87C6380BAEB2@cs.columbia.edu>
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu> <B6033EB2-3B90-4524-A123-38852C5E2698@virtualized.org> <501AF187.3020408@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
X-Mailer: Apple Mail (2.1278)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.6
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 21:53:07 -0000

On Aug 2, 2012, at 2:30 PM, Doug Barton wrote:
>=20
> The whole concept of a global network, with no centralized control, =
that
> permits (nay, encourages) the free flow of information is anathema to
> many national governments. They are desperate to choke that off, by =
any
> means necessary.


=46rom =
http://www.nextgov.com/cybersecurity/2012/07/nsa-head-calls-more-visibilit=
y-over-computer-networks/57073/ :

"The decentralized nature of the Internet and the confusing thicket of =
independent public and private networks are limiting efforts to protect =
against attacks, Alexander signaled Friday at the Def Con hacker =
conference in Las Vegas."

This is Gen. Alexander, head of the NSA...

		--Steve Bellovin, https://www.cs.columbia.edu/~smb






From dougb@dougbarton.us  Thu Aug  2 15:00:42 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB25311E8105 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 15:00:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MqGFX741w42u for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 15:00:42 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id B433011E80F0 for <ietf@ietf.org>; Thu,  2 Aug 2012 15:00:41 -0700 (PDT)
Received: (qmail 28274 invoked by uid 399); 2 Aug 2012 22:00:34 -0000
Received: from unknown (HELO ?172.17.127.241?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 2 Aug 2012 22:00:34 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <501AF889.9000607@dougbarton.us>
Date: Thu, 02 Aug 2012 15:00:41 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Steven Bellovin <smb@cs.columbia.edu>
Subject: Re: ITU-T Dubai Meeting
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu> <B6033EB2-3B90-4524-A123-38852C5E2698@virtualized.org> <501AF187.3020408@dougbarton.us> <97FDD5BF-21F8-4538-9966-87C6380BAEB2@cs.columbia.edu>
In-Reply-To: <97FDD5BF-21F8-4538-9966-87C6380BAEB2@cs.columbia.edu>
X-Enigmail-Version: 1.4.3
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: Thu, 02 Aug 2012 22:00:42 -0000

On 8/2/2012 2:53 PM, Steven Bellovin wrote:
> On Aug 2, 2012, at 2:30 PM, Doug Barton wrote:
>>
>> The whole concept of a global network, with no centralized control, that
>> permits (nay, encourages) the free flow of information is anathema to
>> many national governments. They are desperate to choke that off, by any
>> means necessary.
> 
> 
> From http://www.nextgov.com/cybersecurity/2012/07/nsa-head-calls-more-visibility-over-computer-networks/57073/ :
> 
> "The decentralized nature of the Internet and the confusing thicket of independent public and private networks are limiting efforts to protect against attacks, Alexander signaled Friday at the Def Con hacker conference in Las Vegas."
> 
> This is Gen. Alexander, head of the NSA...

I'm not discounting the fact that some elements of the USG want to clamp
down on this troublesome "freedom" thing. :)  But look at the next
sentence below what you quoted:

Alexander used the speech to lobby for laws to make it easier for
companies under attack to share information with the government and each
other ...

There are currently many DIS-incentives in place regarding companies
sharing information about attacks, hacks, etc.


-- 

    I am only one, but I am one.  I cannot do everything, but I can do
    something.  And I will not let what I cannot do interfere with what
    I can do.
			-- Edward Everett Hale, (1822 - 1909)

From dworley@avaya.com  Thu Aug  2 15:35:57 2012
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 4964421F8B69 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 15:35:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.751
X-Spam-Level: 
X-Spam-Status: No, score=-102.751 tagged_above=-999 required=5 tests=[AWL=-0.152, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B3OUP+kpeyrk for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 15:35:56 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id AB05921F8B66 for <ietf@ietf.org>; Thu,  2 Aug 2012 15:35:56 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAAMAG1DGmAcF/2dsb2JhbABFuRuBB4IgAQEBAQIBEigyCggLAgEIDQghECERJQEBBAESCBqHXAMGBp9/k3ANiU6KY4EChglgA5NzAYdQhQ2FA4J7
X-IronPort-AV: E=Sophos;i="4.77,703,1336363200"; d="scan'208";a="20888852"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 02 Aug 2012 18:30:20 -0400
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by co300216-co-erhwest-out.avaya.com with ESMTP; 02 Aug 2012 18:31:22 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Thu, 2 Aug 2012 18:35:55 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Glen Zorn <glenzorn@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 2 Aug 2012 18:32:41 -0400
Subject: RE: Oauth blog post
Thread-Topic: Oauth blog post
Thread-Index: Ac1w9EaHz/5tT4RoRb6IkdzeSVZq2wACnMiJ
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0BF2@DC-US1MBEX4.global.avaya.com>
References: <501531F7.5040404@gmail.com> <6.2.5.6.2.20120729073422.06d8fe10@resistor.net> <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net> <6.2.5.6.2.20120730101231.047f2550@resistor.net>	, <CAL0qLwYNRW6FSC4kMQkn81+4HgKdv591D43Z31rLAg3ArRsSZg@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22726A0BED@DC-US1MBEX4.global.avaya.com>, <1343942242.17758.26.camel@gwz-laptop>
In-Reply-To: <1343942242.17758.26.camel@gwz-laptop>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 22:35:57 -0000

> From: Glen Zorn [glenzorn@gmail.com]
>=20
> I suppose that that may be one reason why my experiences with
> corporate manipulation (or domination, if you prefer) of the IETF have
> been of people with those very reputations blocking good ideas that
> threatened the interests of their employer.  It's pretty hard to get
> things done in the IETF, but quite easy to stop things, especially if
> one is in a position of power.

If we're doing things right, people who do that should pay a price in
reputation, which will cause them to be excluded from power.

My observation is that the place where an employer can gain leverage
is by being willing to allow employees to spend time as WG chairs,
etc.  We need a lot of chairs, and there seems to be a shortage of
people who are allowed to spend the time to be good chairs.  That
makes it harder to exclude people who excessively promote their
employer's parochial interests.

Dale

From ben@nostrum.com  Thu Aug  2 15:54:12 2012
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DCF811E8087; Thu,  2 Aug 2012 15:54:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9BLtIgOAPNJW; Thu,  2 Aug 2012 15:54:11 -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 D23A711E8125; Thu,  2 Aug 2012 15:54:10 -0700 (PDT)
Received: from dhcp-4516.meeting.ietf.org (dhcp-4516.meeting.ietf.org [130.129.69.22]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q72Ms8Gd041594 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 2 Aug 2012 17:54:09 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: Gen-ART LC Review of draft-ietf-websec-strict-transport-sec-11
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <344AB802-6D45-4399-A628-6852A4732C16@nostrum.com>
Date: Thu, 2 Aug 2012 15:54:08 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <FCCDE600-F790-4804-A860-27CF62493ADA@nostrum.com>
References: <50161BD5.7040901@KingsMountain.com> <344AB802-6D45-4399-A628-6852A4732C16@nostrum.com>
To: =JeffH <Jeff.Hodges@kingsmountain.com>
X-Mailer: Apple Mail (2.1485)
Received-SPF: pass (nostrum.com: 130.129.69.22 is authenticated by a trusted mechanism)
Cc: General Area Review Team <gen-art@ietf.org>, IETF WebSec WG <websec@ietf.org>, draft-ietf-websec-strict-transport-sec.all@tools.ietf.org, IETF Discussion List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 22:54:12 -0000

Jeff and I spoke f2f. Pending actual text, I believe we have resolutions =
to all of my comments save those about an extension registry, which Jeff =
will discuss with other interested parties.

Thanks!

Ben.

On Aug 2, 2012, at 10:46 AM, Ben Campbell <ben@nostrum.com> wrote:

> Hi, thanks for the response.  Comments inline:
>=20
> On Jul 29, 2012, at 10:29 PM, =3DJeffH <Jeff.Hodges@kingsmountain.com> =
wrote:
>>=20
>>> -- Does this draft update any other RFCs (e.g. 2616 or 2818)? If so, =
that
>>> should be explicitly flagged and mentioned in the abstract.
>>=20
>> Good question, I don't believe we've discussed this possibility =
directly in the websec wg. In looking at the RFCs that do update =
RFC2616, it doesn't look like draft-ietf-websec-strict-transport-sec =
(HSTS) is of that ilk.
>>=20
>> However, it nominally appears that an argument could be made that =
it'd be appropriate to update RFC2818 via =
draft-ietf-websec-strict-transport-sec, specifically with regards to =
Section 2.1.  Connection Initiation.
>>=20
>> Though, RFC2818 is Informational, which may be an issue (?). Also, =
perhaps this is something to more appropriately do via a standards-track =
rfc2818bis, i.e., have the latter reference the HSTS spec.
>>=20
>> this is something to discuss this coming week @IETF-84 Vancouver it =
seems.
>>=20
>>=20
>=20
> I will comment on this in response to your post-meeting email.
>=20
>=20
>>> -- I did not find any guidance on how to handle UAs that do not =
understand
>>> this extension. I don't know if this needs to be normative, but the =
draft
>>> should at least mention the possibility and implications.
>>=20
>> Agreed. My -12 working copy now contains these new subsections..
>>=20
>> ###
>> 10.  Server Implementation and Deployment Advice
>>=20
>>  This section is non-normative.
>>=20
>> 10.1.  Non-Conformant User Agent Considerations
>>=20
>>  Non-conformant UAs ignore the Strict-Transport-Security header =
field,
>>  thus non-conformant user agents do not address the threats described
>>  in Section 2.3.1 "Threats Addressed".  Please refer to Section 14.1
>>  "Non-Conformant User Agent Implications" for further discussion.
>>=20
>>                      .
>>                      .
>>=20
>> 14.  Security Considerations
>>                      .
>>                      .
>> 14.1.  Non-Conformant User Agent Implications
>>=20
>>  Non-conformant UAs ignore the Strict-Transport-Security header =
field,
>>  thus non-conformant user agents do not address the threats described
>>  in Section 2.3.1 "Threats Addressed".
>>=20
>>  This means that the web application and its users wielding non-
>>  conformant user agents will be vulnerable to both:
>>=20
>>     Passive network attacks due to web site development and =
deployment
>>     bugs: For example, if the web application contains any insecure,
>>     non-"https", references to the web application server, and if not
>>     all of its cookies are flagged as "Secure", then its cookies will
>>     be vulnerable to passive network sniffing, and potentially
>>     subsequent misuse of user credentials.
>>=20
>>     Active network attacks: If an attacker is able to place a man-in-
>>     the-middle, secure transport connection attempts will likely =
yield
>>     warnings to the user, but without HSTS Policy being enforced, the
>>     present common practice is to allow the user to "click-through"
>>     and proceed.  This renders the user and possibly the web
>>     application open to abuse by such an attacker.
>>=20
>>  This is essentially the status-quo for all web applications and =
their
>>  users in the absence of HSTS Policy.
>> ###
>=20
> That's all good text, but I'm not sure it actually captures my =
concern.
>=20
> =46rom the server's perspective, the fact that non-conformant UAs may =
exist, the server cannot assume that UAs will honor the extension. This =
means that a UA might attempt unprotected access to some resource =
assumed to be protected by this extension. That is, the server can't =
merely select the extension and forget about things--it still needs to =
to take the same care to avoid leaking resources over unprotected =
connections that it would need to do if this extension did not exist in =
the first place.
>=20
> I think this is implied by your last sentence above, but it would be =
better to say it explicitly.
>=20
>=20
>>=20
>>>=20
>>> -- How should a UA handle potential conflicts between a the policy =
record
>>> that includes the includeSubdomain, and any records for subdomains =
that might
>>> have different parameters?
>>=20
>> this is in the draft. the short answer is that at policy enforcement =
time, "superdomain matches win".
>>=20
>> At "noting an HSTS Host" time, the HSTS host's policy (if expressed) =
is noted regardless of whether there are superdomain HSTS hosts =
asserting "includeSubDomains".
>>=20
>> perhaps this needs to be made more clear?
>=20
> Maybe I'm missing something, but I'm not getting that answer from the =
text. Can you point out the specific language?
>=20
>>=20
>>=20
>>>=20
>>> -- section 6.1:
>>>=20
>>> The draft mentions that directives may be extended, but defers =
creation of an
>>> IANA registry to the time of first extension. IANA registries are =
not
>>> expensive; I suggest it be created now. If there's a good reason not =
to, then
>>> the draft should still address the specification policy for =
extensions.
>>>=20
>>> Also, do you expect that some future directive might need to have a
>>> "required-to-understand" status? Given that this is a =
security-affecting
>>> extension, it seems likely. If so, then the mechanism for expressing =
that
>>> needs to be defined in this draft.
>>=20
>>=20
>> These are good questions, and they beg the overall question of how =
complex this simple solution really needs to be and whether we really =
think we'll need any extensions. Something for us to discuss in the =
working group meeting on Tue morning I think.
>=20
> I will comment on this in the post-meeting mail.
>=20
>>=20
>>>=20
>>> -- section 7.2:
>>>=20
>>> Am I correct to assume that the server must never just serve the =
content over
>>> a non-secure connection? If so, it would be helpful to mention that, =
maybe
>>> even normatively.
>>=20
>> It's a SHOULD, see the Note in that section, so it's already =
effectively stated normatively, though one needs to understand HTTP =
workings to realize it in the way you stated it above.  Perhaps could =
add a simple statement as you suggest to the intro para for section 7 =
Server Processing Model, to address this concern?
>>=20
>=20
> I think something of the form SHOULD redirect to HTTPS, but MUST NOT =
under any circumstances send the content unprotected would improve the =
text. That's probably already implied, and a reasonable implementor =
wouldn't due it anyway. But my experience is that some readers will find =
strange interpretations whenever you give them the wiggle room to do so, =
so it's better to be explicit.
>=20
>>=20
>>>=20
>>> -- section 8.4:
>>>=20
>>> Does this imply a duty for compliant UAs to check for revocation one =
way or
>>> another?
>>=20
>> yes. though, per other relevant specifications, as duly cited. AFAIK =
the HSTS spec doesn't need to get into the details because the =
underlying security transport specs, namely TLS, already do this.
>=20
> If that duty already exists, then I see no reason to add it here. But =
do the cited specs unambiguously _require_ revocation checks? I admit to =
not being an expert here, but on a quick scan it seems more like they =
say how you can do it, but do they say you have to?=20
>=20
> [...]
>=20
>>=20
>>> -- section 1.2:
>>>=20
>>> The description of indented notes is almost precisely the opposite =
of how
>>> they are described in the RFC editor's style guide. It describes =
them as
>>> "parenthetical" notes, which is how experienced RFC readers are =
likely to
>>> perceive them. While it doesn't say so explicitly, I think putting =
normative
>>> text in parenthetical notes should be avoided. If these are intended =
to be
>>> taken more strongly than that (and by the description, I take it =
they should
>>> be taken more strongly than the surrounding text), then I suggest =
choosing a
>>> stronger prefix than "NOTE:"
>>=20
>> As it turns out, almost all the Notes are parenthetical.
>>=20
>> I'll render the one(s) that are normative as a regular paragraph(s) =
and leave the others as-is. Will that address your concern?
>>=20
>=20
> Yes, thanks.
>=20
>>=20
>>>=20
>>> -- section 7:
>>>=20
>>> Does the reference to I-D.ietf-tls-ssl-version3 indicate a =
requirement for
>>> SSL3?
>>=20
>> no, it's just that SSLv3 remains a fact of life and is referenced for =
completeness' sake.
>>=20
>>=20
>=20
> Okay.
>=20
>>=20
>>>=20
>>> -- section 8.2, paragraph 5 (first non-numbered paragraph after =
numbered
>>> list)
>>>=20
>>> To be pedantic, this could be taken to mean a congruent match only =
applies if
>>> the includeSubdomains flag is not present. I assume it's intended to =
apply
>>> whether or not the flag is present.
>>=20
>> [ I am assuming you actually are referring to section 8.3, as section =
8.2 doesn't mention the includeSubdomains flag and does not contain a =
numbered list. ]
>>=20
>> yes, a congruent match is intended to apply whether or not the flag =
is present.
>>=20
>>=20
>=20
> yes, I meant 8.3. And on re-reading, I think the text is fine.
>=20
>>=20
>>> -- section 12 and subsections:
>>>=20
>>> I was surprised to see more apparently normative material after the
>>> non-normative guidance sections. I think it would improve the =
organization to
>>> put this closer to the normative rules for UAs.
>>=20
>> We can move section 12 up ahead of the non-normative guidance =
sections.
>=20
> I think that would help, thanks.
>=20
>>=20
>>=20
>>>=20
>>> -- section 14.1, 4th paragraph (first non-bulleted paragraph =
following bullet
>>> list)
>>>=20
>>> This issue is only true for proxies that act as a TLS MiTM, right?
>>=20
>> yes.
>>=20
>>=20
>>> Would
>>> proxies that tunnel TLS via the CONNECT method have this issue?
>>=20
>> I don't think so in the general case.
>>=20
>> I'm not sure what terminology to use to differentiate such proxies if =
this is a detail worth addressing.
>>=20
>=20
> Okay
>=20
>>=20
>> thanks again,
>>=20
>> =3DJeffH
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>=20


From rdroms.ietf@gmail.com  Thu Aug  2 16:09:46 2012
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F4A011E81A3; Thu,  2 Aug 2012 16:09:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.69
X-Spam-Level: 
X-Spam-Status: No, score=-103.69 tagged_above=-999 required=5 tests=[AWL=-0.091, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NQ+gvgw96cQt; Thu,  2 Aug 2012 16:09:45 -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 C416411E81A0; Thu,  2 Aug 2012 16:09:43 -0700 (PDT)
Received: by yhq56 with SMTP id 56so90823yhq.31 for <multiple recipients>; Thu, 02 Aug 2012 16:09:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=J/RQCTMHPF/S/TafyBP61vvjnzcsFaE7vG9xQ6fJC0Q=; b=cov/nU7szS6lZiQTeuYfx6NpMWLLvL/V7hcXqsOODF4+jiceAVxJ+fUHf7+Ts4cP3G xQpVMSVXsbgH2ZOo0jKKGXr+jnNBSIhV2ghZ/Alxyv5FI8qMcDtHjxDgOCUCbOBXnyDK 4yAy0beRKXGVaU0g4GJLG6OXY+cPwgxTzB2NggjjkwbRU3aEw4yRCCn2Ae7Q6OVKwCIM fXzdNTjNZQXc/kc7tafvWmDq6WjUgzUEVLPQGVdXJnFStevH0fkCPbtzAMVUWCIwo/pr iYGw5fS4MWfvTpSPH5butjXPQ6iBYwFu6PsCmfeMg8Mqe+S4YB0GiqttVP2jl34bE80h ojow==
Received: by 10.50.46.232 with SMTP id y8mr6494330igm.57.1343948983230; Thu, 02 Aug 2012 16:09:43 -0700 (PDT)
Received: from [10.21.119.96] (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPS id uq6sm12313211igb.14.2012.08.02.16.09.40 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 02 Aug 2012 16:09:42 -0700 (PDT)
Subject: Re: [IAB] Draft Fees for Processing Legal Requests Policy
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <23C09D95-E873-40C1-9BF5-3378290C9FD0@netapp.com>
Date: Thu, 2 Aug 2012 16:09:38 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <59260491-B8D8-4825-BD9A-0106AC0092F0@gmail.com>
References: <20120802164717.20616.13622.idtracker@ietfa.amsl.com> <23C09D95-E873-40C1-9BF5-3378290C9FD0@netapp.com>
To: IETF Administrative Director <iad@ietf.org>
X-Mailer: Apple Mail (2.1278)
Cc: Working Chairs Group <wgchairs@ietf.org>, IETF discussion list <ietf@ietf.org>, IAOC <iaoc@ietf.org>, IAB IAB <iab@iab.org>, IETF Announcement List <ietf-announce@ietf.org>, IESG IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 23:09:47 -0000

On Aug 2, 2012, at 11:07 AM 8/2/12, Eggert, Lars wrote:

> Looks good to me, but I agree with whoever suggested to increase the =
fees. I think you could easily double or triple them.

I agree with Lars and the suggestion that the fees could be higher.

- Ralph

>=20
> On Aug 2, 2012, at 9:47, IETF Administrative Director <iad@ietf.org> =
wrote:
>=20
>> A reminder of the deadline of 6 August for input.
>> Thanks
>>=20
>> The IAOC is seeking community feedback on a proposed policy by the =
IAOC to impose=20
>> fees to produce information and authenticate documents in response to =
subpoenas and=20
>> other legal requests.
>>=20
>> The IETF receives requests for information, documentation, =
authentication or other=20
>> matters through subpoenas and less formal means that require manpower =
and materials=20
>> to be expended.  These requests are on the rise. During the period =
2005 to 2010 the IETF=20
>> responded to nine subpoenas.  Since 2011 the IETF has received five =
subpoenas and three=20
>> other legal requests for authenticated documents. =20
>>=20
>> Each such request is time sensitive and involves the IETF Counsel, =
the IAD, and members=20
>> of the IAOC, who together form the Legal Management Committee, to =
rapidly analyze and=20
>> identify the means for satisfying the request.  Often there is a need =
to retain outside counsel,=20
>> especially in cases that might lead to depositions or court =
testimony.=20
>>=20
>> The IAOC believes a Schedule of Fees is an appropriate and reasonable =
means to recover=20
>> costs associated with such efforts.
>>=20
>> The draft policy entitled Draft Fee Policy for Legal Requests can be =
found=20
>> at: <http://iaoc.ietf.org/policyandprocedures.html>
>>=20
>> Before adopting a policy the IAOC would like feedback on this before =
making a=20
>> decision.  Comments appreciated to ietf@ietf.org by 6 August 2012.
>>=20
>> Ray Pelletier
>> IETF Administrative Director
>=20


From smb@cs.columbia.edu  Thu Aug  2 16:29:27 2012
Return-Path: <smb@cs.columbia.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7856A11E81CE; Thu,  2 Aug 2012 16:29:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nfe7J-0uvpXM; Thu,  2 Aug 2012 16:29:26 -0700 (PDT)
Received: from salak.cc.columbia.edu (salak.cc.columbia.edu [128.59.29.6]) by ietfa.amsl.com (Postfix) with ESMTP id 8C36F11E81CB; Thu,  2 Aug 2012 16:29:26 -0700 (PDT)
Received: from [10.9.0.98] (fireball.cs.columbia.edu [128.59.13.10]) (user=smb2132 mech=PLAIN bits=0) by salak.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id q72NTNlh011670 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 2 Aug 2012 19:29:24 -0400 (EDT)
Subject: Re: [IAB] Draft Fees for Processing Legal Requests Policy
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <59260491-B8D8-4825-BD9A-0106AC0092F0@gmail.com>
Date: Thu, 2 Aug 2012 16:29:22 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A745E18-820B-4470-A46A-5D7ADFAFA57B@cs.columbia.edu>
References: <20120802164717.20616.13622.idtracker@ietfa.amsl.com> <23C09D95-E873-40C1-9BF5-3378290C9FD0@netapp.com> <59260491-B8D8-4825-BD9A-0106AC0092F0@gmail.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
X-Mailer: Apple Mail (2.1278)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.6
Cc: Working Chairs Group <wgchairs@ietf.org>, IETF discussion list <ietf@ietf.org>, IAOC <iaoc@ietf.org>, IAB IAB <iab@iab.org>, IESG IESG <iesg@ietf.org>, IETF Announcement List <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, 02 Aug 2012 23:29:27 -0000

On Aug 2, 2012, at 4:09 PM, Ralph Droms wrote:

>=20
> On Aug 2, 2012, at 11:07 AM 8/2/12, Eggert, Lars wrote:
>=20
>> Looks good to me, but I agree with whoever suggested to increase the =
fees. I think you could easily double or triple them.
>=20
> I agree with Lars and the suggestion that the fees could be higher.
>=20

I don't think this can be a profit center; as I understand it, the judge =
in any case will rule on the reasonableness of any fees.  Here's text =
from Rule 45 of the (U.S.) Federal Rules of Civil Procedure:

"A non-party required to produce documents or materials is protected =
against significant expense resulting from involuntary assistance to the =
court. This provision applies, for example, to a non-party required to  =
provide a list of class members. The court is not required to fix the =
costs in advance of production, although this will often be the most =
satisfactory accommodation to protect the party seeking discovery from =
excessive costs. In some instances, it may be preferable to leave =
uncertain costs to be determined after the materials have been produced, =
provided that the risk of uncertainty is fully disclosed to the =
discovering party. See, e.g., United States v. Columbia Broadcasting =
Systems, Inc., 666 F.2d 364 (9th Cir. 1982)."

Note: as I read it, "the court" fixes the fees.  I'm not a lawyer, but =
given that Jorge wrote the text in the draft procedure I assume that the =
fee he specified is considered reasonable in today's courts.  I don't =
know that a higher one would be accepted; I'll defer to Jorge to answer. =
 (He doesn't tell me how much crypto to put in; I won't tell him how to =
deal with courts...)

I'm more concerned about "This procedure assumes that the procedure and =
technology experts will volunteer their time as IETF participants."  A =
lot of us give a lot of time on technical matters, because we think it's =
good for the Internet and -- to be honest -- because our employers think =
it benefits them.  It's quite unclear that spending many hours on =
something that benefits a third party is in the interests of the =
Internet, and I could easily see some employers objecting to their =
employees getting dragged into a legal matter.  (Only slightly =
hypothetical scenario: Party A sues Party B on patent matters, and wants =
IETF data.  Party C, for whom an AD works, is probably in the same =
position on those patents as is B, but A sued only B for tactical =
reasons.  Can/should that AD work on the subpoena?  Would that AD even =
know B's and C's positions?)  Also, I wonder -- is there any potential =
liability accruing to such procedure and technology experts?  Does the =
IETF's liability policy cover them, if they're not currently among the =
covered leadership?


		--Steve Bellovin, https://www.cs.columbia.edu/~smb






From lars@netapp.com  Thu Aug  2 16:46:28 2012
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BE3711E814E; Thu,  2 Aug 2012 16:46:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.45
X-Spam-Level: 
X-Spam-Status: No, score=-10.45 tagged_above=-999 required=5 tests=[AWL=0.149,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GVBbUCtY2PKV; Thu,  2 Aug 2012 16:46:28 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 1701C11E8131; Thu,  2 Aug 2012 16:46:28 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.77,704,1336374000";  d="p7s'?scan'208";a="672429185"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 02 Aug 2012 16:46:12 -0700
Received: from vmwexceht01-prd.hq.netapp.com (vmwexceht01-prd.hq.netapp.com [10.106.76.239]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q72NkCPd010253; Thu, 2 Aug 2012 16:46:12 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.13]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.02.0298.004; Thu, 2 Aug 2012 16:46:12 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Steven Bellovin <smb@cs.columbia.edu>
Subject: Re: [IAB] Draft Fees for Processing Legal Requests Policy
Thread-Topic: [IAB] Draft Fees for Processing Legal Requests Policy
Thread-Index: AQHNcM6F4lt8DZmzr0CanT4RQaDhJ5dHRvkAgABUiQCAAAWEAIAABLCA
Date: Thu, 2 Aug 2012 23:46:11 +0000
Message-ID: <FBB9DA49-C1D8-4B30-9268-3BC693DD081E@netapp.com>
References: <20120802164717.20616.13622.idtracker@ietfa.amsl.com> <23C09D95-E873-40C1-9BF5-3378290C9FD0@netapp.com> <59260491-B8D8-4825-BD9A-0106AC0092F0@gmail.com> <7A745E18-820B-4470-A46A-5D7ADFAFA57B@cs.columbia.edu>
In-Reply-To: <7A745E18-820B-4470-A46A-5D7ADFAFA57B@cs.columbia.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.116]
Content-Type: multipart/signed; boundary="Apple-Mail=_4D9D095E-C6F9-441C-BD77-AC0FE388ECA4"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: Working Chairs Group <wgchairs@ietf.org>, IETF discussion list <ietf@ietf.org>, IAOC <iaoc@ietf.org>, IAB IAB <iab@iab.org>, IETF Announcement List <ietf-announce@ietf.org>, IESG IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 23:46:28 -0000

--Apple-Mail=_4D9D095E-C6F9-441C-BD77-AC0FE388ECA4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Aug 2, 2012, at 16:29, Steven Bellovin <smb@cs.columbia.edu> wrote:
> I don't think this can be a profit center; as I understand it, the =
judge in any case will rule on the reasonableness of any fees.

Agreed. My intent is not to create a profit center. But I do also avoid =
this remaining a loss center for us.

But I guess we don't need to discuss this here further. I'm sure the =
IAOC has taken note and will look into this.

Lars=

--Apple-Mail=_4D9D095E-C6F9-441C-BD77-AC0FE388ECA4
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMQDCCBUow
ggQyoAMCAQICEFcfSRTG0jNknqb9LV9GuFkwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTEyMTAwMDAwMDBaFw0x
MjEyMDkyMzU5NTlaMIIBDTEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEeMBwGCSqGSIb3DQEJARYPbGFyc0BuZXRhcHAuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokrhJTcXt6J/VEpZOicLoguBlYTjXP9v
Ze4HuuhXnURUS8YouAfgaqA0zYbt5yd6fh4PBMdAaEWr5yJyHuFykXlrCumjUWSpLuqTS2A+pt4q
cZaAQk9iLDN/UVd3SpkUuvWbxXlqzG7/BSqa3VNObBzCmyh+V7aXxri+30CT//DSsNRC4VFy6sn6
dMgSaFenXLwe/FBwY0qTMfICT1PrrX6Sw1S8OfH9rykLlZXbmfkFExxQngp1DJH9xMHeODHGbCv/
ty5gdxMOrLe+vENxFEcy1YQWBZd1kNL4UObugF8A/jE/s+Oa3H1VFH8ghqZTdqGDysVxmtKHuNFx
6jIBSQIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgG
CCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNV
HSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDovL2luZGMx
ZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqG
SIb3DQEBBQUAA4IBAQBA7q6tR92qpd7xo7VBsrOfGCWzoxIVfTc7t0RhB/Oz/+c3lnhYnNScIuKN
JmyZvznmVxqB9BJ72+NkvmdB/hnILSBTRawL2tyLo9PkBtN0nRt4gS6wjpWnD8G83hlJLE7r25jk
7HkRev61dTIXsANFpJKF02C4XSoDfEzNV6MpuEvHvcgHCqMrlwWwfKc7+NoDnE8PBuRzwSXvlD5L
mswCY2iiOsd7ImNO4OzTCxETvKTDu92+FTIbRJJpYjVNv1UF7e3w9Kq65BkZJErUH19beUeQl0Wh
2BJQE6/15rQyCnP0iJ/Nmx2/kI6M0PWunEsI6FMs0MbosreaWGHlQmomMIIG7jCCBdagAwIBAgIQ
cRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQL
EzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYD
VQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y
aXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAo
YykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBD
bGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6ZvgSU6Lb9UB
0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHsEnMhjfXc
MM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO4YM/d/mZ
//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSyriMGZSal
J1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYI
KwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0T
AQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVy
aXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9w
Y2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1h
Z2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28u
dmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRl
TGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHp
MIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWduLCBJ
bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENsYXNzIDEg
UHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+v
OEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlMJBq6WaSH
O3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKvYLMVirOV
nDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDRyxTWcVib
vtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy+kgOZY5J
yNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/wYIxggSL
MIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDgwMjIzNDYwOVowIwYJKoZIhvcNAQkEMRYEFPm7
Bd/MMWm1dSyfL1iYFaJA510gMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBACMFYNmi
jKyglyuoCTm5pjv/AHxfFhkkkXS+L84qvttZwN4+W3OH/44bJ3VGduVgSRpzNFS/KRX0sswTJsos
snJsRk2bMuOxYuWUPyIsKVbSTB735OCs/qu7lWwBnqgkpdIzFeLWXaaEi+DXY8DDPyPrnmY3dttN
w9lyCLLl/vA60NukxSfAqcXKX14JD3gpNlOoGxoPiiL9EzK3U0BdwcD65a1qbEKrKnVpOOFbh1M3
j0xSjFRh6+j//143KGRndrjYxmqMXj1cFw9IkZKdLSv/Xf1WMbL4yfLFieuUVcqkMnxpvN8+xZMT
OEOnjBhcmRZudGLzrzZq7ufSXJaKGv8AAAAAAAA=

--Apple-Mail=_4D9D095E-C6F9-441C-BD77-AC0FE388ECA4--

From hsantos@isdg.net  Thu Aug  2 21:07:22 2012
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 876FC11E809B for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 21:07:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.586
X-Spam-Level: 
X-Spam-Status: No, score=-102.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CugoJUVO0djx for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 21:07:21 -0700 (PDT)
Received: from pop3.winserver.com (news.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 50FFD11E80AE for <ietf@ietf.org>; Thu,  2 Aug 2012 21:07:20 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=5870; t=1343966838; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=nHgxf2mN8tLLJU2P/JXReTNM+V8=; b=pd2z/5+E4ykTzukHohT9 OAEsX9iE6wQvSWWLvzHhyAumQEcEdKUfxJe4o16iiWFiDfWYJRGeSGFjtL5r9CdY f7XjwcLccy89HkWavynPffFh49AyKiby9eQNuguNNX3XIMd+4E3p3yH0mrkxAxho ASnFzo7hCk2tHm21wNu5Ff0=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 03 Aug 2012 00:07:18 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from hector.wildcatblog.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 4283621415.6563.4072; Fri, 03 Aug 2012 00:07:16 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=5870; t=1343966678; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=GpFOH3f kNY7ZoIf78SumpZauZad66W5bIboP7K/rZ08=; b=d+FBL9EX4dkQZejR/ClyALp Xrgav4vF2hl2fhzFUpRbEM2G/YJg0LDubbcKcPiZv7pGFJ6e9PUbuzMtphF24WC0 HoDGF5/hGtKev8QkzAlXUnY+Bs/XEfZQAZN2VMAKoYks5+9NGQa5itNZujcwcui2 IbSicCcFZ0cmxa3EnIcg=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 03 Aug 2012 00:04:38 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 587476286.9.6528; Fri, 03 Aug 2012 00:04:37 -0400
Message-ID: <501B4E68.2030402@isdg.net>
Date: Fri, 03 Aug 2012 00:07: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: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Subject: Re: Oauth blog post
References: <501531F7.5040404@gmail.com>	<6.2.5.6.2.20120729073422.06d8fe10@resistor.net>	<39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net>	<6.2.5.6.2.20120730101231.047f2550@resistor.net>, <CAL0qLwYNRW6FSC4kMQkn81+4HgKdv591D43Z31rLAg3ArRsSZg@mail.gmail.com>	<CD5674C3CD99574EBA7432465FC13C1B22726A0BED@DC-US1MBEX4.global.avaya.com> <CABC742E-0DD2-412D-B60E-879C30D01769@gmx.net>
In-Reply-To: <CABC742E-0DD2-412D-B60E-879C30D01769@gmx.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 04:07:22 -0000

Whose library? (rhetorical question).

In my experience, the issue is pretty straight forward and its what 
this OAUTH fellow exemplified - technology leaders taking control of a 
standard for their strategic benefit. This is not a phenomenon, its 
par for the course and its a principle reason why I have mandated 
since the 80s that we (SSI) do not get locked in on any standard 
protocol, with PPP, RADIUS, TELNET, FTP, SMTP, POP3, HTTP and others 
our product are strategically based on.  This is not odd and 
product/project managers who don't recognized protocol(s) apply to the 
benefit of their company and product lines is well, not doing their 
company any great service. The IETF is suppose to be the watchdog for 
protocol standards changing on the community and more often you are 
seeing the mantra of "Who's Who" or basically the old GM theory - 
"Whats good for GM, is good for ...." changing standards or pseudo 
developed standard protocols.

Overall, we have a conflict of interest and if anyone who does not 
have any particular interest in a protocol, makes you wonder why one 
would be involved or are even carrying a corporate badge.  I for one 
will not appreciate an employee doing work that may have a direct or 
indirect conflict of interest and would be pissed if he didn't 
recognized it.  Thats not odd or evil. Thats par for the course.

Which brings us to the "Whose Library?" question.  If one is to follow 
market and technology leaders, does that mean you are using their 
library as well?  I'm sure that does not always fit with all corporate 
IP policies, and more controlled so in the past with in-house 
developed source code, than it does today with all the globalization 
and participation going on.  Look at the mess that (open source) 
created!  It all fun when you're young, but one day you have to bring 
home the bacon.

I think it is a mistake to assume that using a Library is the answer 
or rather is something that defines a protocol direction and the 
people that define it. One question might be what language is this in? 
  Would it be C/C++? or some perl scripting language? Some other? 
What if the organization has its own strategic "added value" language 
for its customers?  You don't have to go far than just use an example 
of .NET? What if the OAUTH Library was offered only in .NET. I'm sure 
the *nix world would not be jumping with joy there.  All this and I've 
hardly touch based with many more reasons to be careful of these 
protocol definition/direction issues, why one has be very careful and 
also if they can, be active, if only just vocal and watchful when need 
be of people, in particular those who are very active with the IETF 
process taking control and advocating a method in a direction that can 
have a major/negative impact on you.   Its a tough issue because 
decisions do need to be made but its getting harder to swallow the 
"Rough Consensus" stick being especially when its a highly subjective 
issue involved.

In any case, I believe the IETF should take heed of what has occured 
with the OAUTH incident. I don't believe it is an isolated issue which 
I am sure many here believe. I am not sure what all can be learned 
other than possibly the IETF needs to be more watchful of standards 
moving away from a network wide community open standard to one that 
only feasibly benefits a much smaller set, abeit larger entities.

At the end of the day, its all about cost, yet, while a library may 
help address that, that is not always the best solution unless we do 
want to have specific market and technology leaders in control of a 
particular protocol w/o a library.  In my view, the community MUST 
have an IETF around to be watchful of the standards from being 
strategically changed on people. It assume a level of equal capability 
by all to stay on par or get out of the way and that presents conflict 
of interest and possible anti-trust.  The GM theory does not always apply.

-- 
HLS

Hannes Tschofenig wrote:
> In the identity management case we are not necessarily talking about solutions that are "good" or "bad". The issue is that certain people care about one use case and other people care about other use cases.  I use the term "use case" in a generic sense to also include certain deployment assumptions (e.g., has to work with existing programming languages, deployment environments), or design themes (e.g., XML vs. JSON). 
> 
> So, for example, in the OAuth case there are people who care a lot about different Websites sharing data between each other (the photo sharing / photo printing use case). Again others think that the smart phone use case is more important. The solutions for these two cases are slightly different (because they can rely on different assumptions). 
> 
> Initially, people start with a single use case they care about. The work gets attention and other people start to use the protocol as well and notice that it does not meet their use cases. So, they add functionality. Over time the set of specification becomes more complex and a beginner does not see through the specification jungle anymore. Then, these newcomers start from scratch to fix all these "complex protocols". Typically, these persons like to reject any idea that was done in the past (such as learning from the experience the previous generation had made). The cycle starts from the beginning. We went through these cycles several times already in the identity management world. 

> I believe that application developers shouldn't even worry about the details of the protocol suite. They should be using a library instead. We use libraries all the time and particularly with security protocols. Take TLS as an example. No application developer would come up with the idea to write their own TLS stack either. They let security professionals write those libraries. 





From narten@us.ibm.com  Thu Aug  2 21:53:12 2012
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68C7811E80E8 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 21:53:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.249
X-Spam-Level: 
X-Spam-Status: No, score=-110.249 tagged_above=-999 required=5 tests=[AWL=0.350, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jj-RKvUSM-ja for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 21:53:11 -0700 (PDT)
Received: from e4.ny.us.ibm.com (e4.ny.us.ibm.com [32.97.182.144]) by ietfa.amsl.com (Postfix) with ESMTP id 2BF8311E80E5 for <ietf@ietf.org>; Thu,  2 Aug 2012 21:53:10 -0700 (PDT)
Received: from /spool/local by e4.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 3 Aug 2012 00:53:09 -0400
Received: from d01dlp02.pok.ibm.com (9.56.250.167) by e4.ny.us.ibm.com (192.168.1.104) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 3 Aug 2012 00:53:08 -0400
Received: from d01relay03.pok.ibm.com (d01relay03.pok.ibm.com [9.56.227.235]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 43AB26E803A for <ietf@ietf.org>; Fri,  3 Aug 2012 00:53:06 -0400 (EDT)
Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay03.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q734r5uv367554 for <ietf@ietf.org>; Fri, 3 Aug 2012 00:53:05 -0400
Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q734r4E8026654 for <ietf@ietf.org>; Fri, 3 Aug 2012 01:53:05 -0300
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q734r4Of026641 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 3 Aug 2012 01:53:04 -0300
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q734r3Zt007837 for <ietf@ietf.org>; Fri, 3 Aug 2012 00:53:04 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q734r3OW007813 for ietf@ietf.org; Fri, 3 Aug 2012 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201208030453.q734r3OW007813@rotala.raleigh.ibm.com>
Date: Fri, 03 Aug 2012 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-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12080304-3534-0000-0000-00000B11C654
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 04:53:12 -0000

Total of 160 messages in the last 7 days.
 
script run at: Fri Aug  3 00:53:03 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  5.00% |    8 |  4.27% |    52331 | abdussalambaryun@gmail.com
  5.00% |    8 |  4.05% |    49608 | hannes.tschofenig@gmx.net
  4.38% |    7 |  4.28% |    52421 | barryleiba@computer.org
  4.38% |    7 |  3.85% |    47178 | sm@resistor.net
  5.00% |    8 |  3.18% |    38920 | randy@psg.com
  1.88% |    3 |  5.93% |    72615 | adrian@olddog.co.uk
  3.12% |    5 |  3.93% |    48062 | glenzorn@gmail.com
  2.50% |    4 |  4.18% |    51112 | lars@netapp.com
  3.12% |    5 |  3.53% |    43171 | brian.e.carpenter@gmail.com
  3.12% |    5 |  3.12% |    38254 | smb@cs.columbia.edu
  2.50% |    4 |  3.36% |    41093 | hallam@gmail.com
  3.12% |    5 |  2.58% |    31625 | dworley@avaya.com
  2.50% |    4 |  2.42% |    29662 | robert@raszuk.net
  2.50% |    4 |  2.40% |    29438 | superuser@gmail.com
  2.50% |    4 |  1.83% |    22358 | paul.hoffman@vpnc.org
  1.88% |    3 |  2.34% |    28631 | ynir@checkpoint.com
  1.88% |    3 |  1.94% |    23770 | dromasca@avaya.com
  1.88% |    3 |  1.93% |    23630 | henrik@levkowetz.com
  1.88% |    3 |  1.80% |    22013 | daedulus@btconnect.com
  1.25% |    2 |  2.41% |    29444 | ben@nostrum.com
  1.88% |    3 |  1.71% |    20940 | ole@cisco.com
  1.88% |    3 |  1.52% |    18587 | joelja@bogus.com
  1.88% |    3 |  1.46% |    17823 | chair@ietf.org
  1.88% |    3 |  1.27% |    15599 | jnc@mercury.lcs.mit.edu
  1.25% |    2 |  1.19% |    14600 | d3e3e3@gmail.com
  1.25% |    2 |  1.14% |    13952 | dougb@dougbarton.us
  1.25% |    2 |  1.13% |    13866 | sob@sobco.com
  1.25% |    2 |  1.08% |    13175 | yoshihiro.ohba@toshiba.co.jp
  1.25% |    2 |  1.06% |    12995 | housley@vigilsec.com
  1.25% |    2 |  1.00% |    12187 | john-ietf@jck.com
  1.25% |    2 |  0.99% |    12069 | melinda.shore@gmail.com
  1.25% |    2 |  0.98% |    11995 | weiler@watson.org
  1.25% |    2 |  0.96% |    11709 | yaronf.ietf@gmail.com
  1.25% |    2 |  0.93% |    11351 | paf@frobbit.se
  1.25% |    2 |  0.85% |    10388 | iad@ietf.org
  0.62% |    1 |  1.12% |    13771 | jeff.hodges@kingsmountain.com
  0.62% |    1 |  0.91% |    11131 | hannes.tschofenig@nsn.com
  0.62% |    1 |  0.83% |    10147 | rbarnes@bbn.com
  0.62% |    1 |  0.83% |    10120 | peer2peer@gmail.com
  0.62% |    1 |  0.83% |    10105 | narten@us.ibm.com
  0.62% |    1 |  0.76% |     9325 | stephen.farrell@cs.tcd.ie
  0.62% |    1 |  0.70% |     8566 | aservin@lacnic.net
  0.62% |    1 |  0.68% |     8361 | eburger-l@standardstrack.com
  0.62% |    1 |  0.68% |     8330 | loa@pi.nu
  0.62% |    1 |  0.67% |     8192 | timo.perala@nsn.com
  0.62% |    1 |  0.64% |     7828 | olaf@nlnetlabs.nl
  0.62% |    1 |  0.63% |     7722 | mehmet.ersue@nsn.com
  0.62% |    1 |  0.63% |     7701 | duerst@it.aoyama.ac.jp
  0.62% |    1 |  0.62% |     7623 | hsantos@isdg.net
  0.62% |    1 |  0.62% |     7590 | rdroms.ietf@gmail.com
  0.62% |    1 |  0.62% |     7550 | davidb@verisign.com
  0.62% |    1 |  0.61% |     7436 | tbray@textuality.com
  0.62% |    1 |  0.60% |     7331 | jmpolk@cisco.com
  0.62% |    1 |  0.58% |     7093 | mrex@sap.com
  0.62% |    1 |  0.56% |     6912 | drc@virtualized.org
  0.62% |    1 |  0.55% |     6674 | tnadeau@lucidvision.com
  0.62% |    1 |  0.52% |     6364 | marc.blanchet@viagenie.ca
  0.62% |    1 |  0.51% |     6216 | mstjohns@comcast.net
  0.62% |    1 |  0.51% |     6193 | scott.brim@gmail.com
  0.62% |    1 |  0.49% |     6038 | alexandru.petrescu@gmail.com
  0.62% |    1 |  0.49% |     5995 | craemer@isoc.org
  0.62% |    1 |  0.48% |     5922 | agmalis@gmail.com
  0.62% |    1 |  0.45% |     5559 | mnot@mnot.net
  0.62% |    1 |  0.43% |     5299 | cabo@tzi.org
  0.62% |    1 |  0.43% |     5292 | ned+ietf@mauve.mrochek.com
  0.62% |    1 |  0.43% |     5269 | hartmans-ietf@mit.edu
--------+------+--------+----------+------------------------
100.00% |  160 |100.00% |  1224227 | Total


From daniel.karrenberg@ripe.net  Thu Aug  2 22:42:22 2012
Return-Path: <daniel.karrenberg@ripe.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F02E911E80D7 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 22:42:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LSUWbZm6iCZr for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 22:42:21 -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 F255911E80D5 for <ietf@ietf.org>; Thu,  2 Aug 2012 22:42:20 -0700 (PDT)
Received: from dodo.ripe.net ([193.0.23.4]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <daniel.karrenberg@ripe.net>) id 1SxAeP-0003PS-Bl; Fri, 03 Aug 2012 07:42:18 +0200
Received: from baboon.ripe.net ([193.0.1.208] helo=[127.0.0.1]) by dodo.ripe.net with esmtps (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <daniel.karrenberg@ripe.net>) id 1SxAeO-0005OS-Ua; Fri, 03 Aug 2012 07:42:17 +0200
Subject: Re: ITU-T Dubai Meeting
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Daniel Karrenberg <daniel.karrenberg@ripe.net>
In-Reply-To: <CAMm+Lwg2HgO-=9ED4vbmO+Vf9r6bYPcLDgfyMAyPdEPVgRm4LQ@mail.gmail.com>
Date: Fri, 3 Aug 2012 07:42:16 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FB949BEA-5BDB-401A-8A75-E9A9BDAA72A6@ripe.net>
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu> <CAMm+Lwg2HgO-=9ED4vbmO+Vf9r6bYPcLDgfyMAyPdEPVgRm4LQ@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1278)
X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.48/RELEASE, bases: 20120425 #7816575, check: 20120803 clean
X-RIPE-Spam-Level: --
X-RIPE-Spam-Report: Spam Total Points:   -2.9 points pts rule name              description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 2cd422cf40ef1bab352b066641112beb1045897546985d142337c3082ad6dd5c
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: Fri, 03 Aug 2012 05:42:22 -0000

On 02.08.2012, at 22:41, Phillip Hallam-Baker wrote:

> ... That depends on whether the registry in question is dealing with a
> scarce resource or a plentiful one. Having two registries handing out
> IPv4 addresses at this point would be very very bad. Having more than
> one place you can get an IPv6 from would not worry me at all. ...

IPv4 addresses used to be regarded as non-scarce not so long ago.

It is not about distributing the address space but about keeping a=20
correct, comprehensive and current registry of address space users.

As others have pointed out the ITU argument is about choice only in =
name.
It is quite likely that nation states will quickly restrict that choice=20=

once they control one of the 'choices'.

Full disclosure: I helped invent and implement the RIR system. I am =
employed by the RIPE NCC.

Daniel




From brian.e.carpenter@gmail.com  Thu Aug  2 23:58:05 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 959C021E8034; Thu,  2 Aug 2012 23:58:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.462
X-Spam-Level: 
X-Spam-Status: No, score=-101.462 tagged_above=-999 required=5 tests=[AWL=0.229, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cDg7TH6zMSrw; Thu,  2 Aug 2012 23:58:04 -0700 (PDT)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4D33821E8039; Thu,  2 Aug 2012 23:58:04 -0700 (PDT)
Received: by wibhm11 with SMTP id hm11so4597115wib.13 for <multiple recipients>; Thu, 02 Aug 2012 23:58:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=dbONaZKbFwOe0wVPYbEInwlodLIqmdwLE3wCA43X8vc=; b=C50MhQYZAsxht85VVXdVtTaKmvvcxdBL8Xh/NPu5/sB35iB7J/RTNLgt6AS3CGPy1j t3J8HRwEXur62kvW7HhG8Uehk+pLAfUjzHZGG+T4SKDUDRAGLMZUGci8Xnwyi1VEe/sX SwAfvEgPsGau1VgghlrAreoiruIQ0h/id6CvfTE07R2qTh4RWATjtWx8v4IBb316ZCKp low46WnwLpZ5BgFQtWRVV6dO9XJKXHpCmSaW1WuOc6fiY0sEAnYa4Ezn+YuJDR/mDikW K42xGLXqNwGlLOItbxwJxMx+VvfcAxUCrjzomQwqmG7Az8+c6laWp+qt2aZozon/1tno 76wA==
Received: by 10.216.101.68 with SMTP id a46mr335171weg.120.1343977082767; Thu, 02 Aug 2012 23:58:02 -0700 (PDT)
Received: from [192.168.1.64] (host-2-102-217-126.as13285.net. [2.102.217.126]) by mx.google.com with ESMTPS id cu1sm37903317wib.6.2012.08.02.23.58.00 (version=SSLv3 cipher=OTHER); Thu, 02 Aug 2012 23:58:01 -0700 (PDT)
Message-ID: <501B767B.6030501@gmail.com>
Date: Fri, 03 Aug 2012 07:58:03 +0100
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: robert@raszuk.net
Subject: Re: Basic ietf process question ...
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com><CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com><CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com>	<501AA9DF.6010208@raszuk.net>	<EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com> <501AB4F5.7030205@raszuk.net> <501AC2C7.6040707@gmail.com> <501AC43A.3020307@raszuk.net>
In-Reply-To: <501AC43A.3020307@raszuk.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>, opsawg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 06:58:06 -0000

On 02/08/2012 19:17, Robert Raszuk wrote:
> Hi Brian,
> 
> Perhaps we understand a different thing by "xml schema" As example what
> I had in mind when asking this question was the example from "Appendix
> A" of http://tools.ietf.org/html/draft-marques-l3vpn-schema-00 where
> while perhaps not yet complete it does provide decent representation of
> one of the popular service today.

There are certainly cases where systematic metadata are useful; I can't judge
whether VPN configuration is one of them, but I can easily believe it. In such
a case, I suppose XML is as good a tool as ASN.1, ABNF or whatever else
you might choose.

> That's what I had mind asking why such appendix isn't a mandatory part
> of each new protocol extension.

That's an enormous leap that I just don't understand. Most protocols don't
need that sort of configuration complexity.

> It has very little to do with Web Services you may be referring to.

Yes it does. It's exactly because of a doctrinaire approach that whatever
it is, it should be represented by an XML schema, that WS-splat became
such a horribly complex matter.

Again: no problem with creating XML schemata where they are useful. But
making them mandatory would be just as bad as making MIB modules mandatory,
IMHO.

    Brian

> 
> Many thx,
> R.
> 
>> I think anyone with intimate experience of the Web Services standards
>> experiment (trying to use XML as if it was a Turing machine) would have
>> extreme doubts about any proposal to impose such a requirement.
>>
>> It was not for no reason that many people came to refer to the Web
>> Services family of standards as "WS-splat". The words "small" and
>> "xml schema" don't really belong together,
>>
>> Regards
>>     Brian Carpenter
>>
>> On 02/08/2012 18:12, Robert Raszuk wrote:
>>> Hi Dan,
>>>
>>>> We should be talking
>>>> nowadays about a toolset rather than one tool that fits all.
>>>
>>> Just to clarify what I asked about .. I am not looking for a single tool
>>> or single protocol to be used to configure everything.
>>>
>>> I am asking for small building block like xml schema (or something
>>> similar) to be part of each new IETF proposal or protocol change. IMHO
>>> only that can allow any further more fancy abstractions and tools to be
>>> build and used in practice.
>>>
>>> Best regards,
>>> R.
>>>
>>>
>>>
>>>> Hi,
>>>>
>>>> The OPSAWG/OPSAREA open meeting this afternoon has an item on the
>>>> agenda
>>>> concerning the revision of RFC1052 and discussing a new architecture
>>>> for
>>>> management protocols.
>>>>
>>>>
>>>> My personal take is that no one protocol, or one data modeling language
>>>> can match the operational requirements to configure and manage the wide
>>>> and wider range of hosts, routers and other network devices that are
>>>> used to implement IP networks and protocols. We should be talking
>>>> nowadays about a toolset rather than one tool that fits all. However,
>>>> this is a discussion that just starts.
>>>>
>>>> Regards,
>>>>
>>>> Dan
>>>>
>>>>
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
>>>> Of
>>>>> Robert Raszuk
>>>>> Sent: Thursday, August 02, 2012 7:25 PM
>>>>> Cc: ietf@ietf.org
>>>>> Subject: Basic ietf process question ...
>>>>>
>>>>> All,
>>>>>
>>>>> IETF documents have number of mandatory sections .. IANA Actions,
>>>>> Security Considerations, Refs, etc ...
>>>>>
>>>>> Does anyone have a good reason why any new protocol definition or
>>>>> enhancement does not have a build in mandatory "XML schema" section
>>>>> which would allow to actually use such standards based enhancement in
>>>>> vendor agnostic way ?
>>>>>
>>>>> There is a lot of talk about reinventing APIs, building network wide
>>>> OS
>>>>> platform, delivering SDNs (whatever it means at any point of time for
>>>>> one) ... but how about we start with something very basic yet IMHO
>>>>> necessary to slowly begin thinking of network as one plane.
>>>>>
>>>>> I understand that historically we had/still have SNMP however I have
>>>>> never seen this being mandatory section of any standards track
>>>> document.
>>>>> Usually SNMP comes 5 years behind (if at all) making it obsolete by
>>>>> design.
>>>>>
>>>>> NETCONF is great and very flexible communication channel for
>>>>> provisioning. However it is sufficient to just look at number of ops
>>>>> lists to see that those who tried to use it quickly abandoned their
>>>>> efforts due to complete lack of XML schema from each vendor they
>>>> happen
>>>>> to use or complete mismatch of vendor to vendor XML interpretation.
>>>>>
>>>>> And while perhaps this is obvious I do not think that any new single
>>>>> effort will address this. This has to be an atomic and integral part
>>>> of
>>>>> each WG's document.
>>>>>
>>>>> Looking forward for insightful comments ...
>>>>>
>>>>> Best,
>>>>> R.
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
> 
> 

From brian.e.carpenter@gmail.com  Fri Aug  3 00:18:21 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17BF221F8C7B for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 00:18:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.465
X-Spam-Level: 
X-Spam-Status: No, score=-101.465 tagged_above=-999 required=5 tests=[AWL=0.226, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9VnEarWQPURg for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 00:18:20 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 370CE21F8C03 for <ietf@ietf.org>; Fri,  3 Aug 2012 00:18:20 -0700 (PDT)
Received: by wgbdr13 with SMTP id dr13so200306wgb.13 for <ietf@ietf.org>; Fri, 03 Aug 2012 00:18:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=2dKtozmg8mCWPInUW7vaVZCmpxz4xHosZOv6Cus3oCY=; b=uqEN9NsC+2u1rdb6XM74wFV5eRTY6ZDnRjASC5uRtFZn3GUMEe20znS5oy/uCVcJss 0fQYm6IGFvMEc+bHyfPDgIT0SAuGjK9ndnq/3RICSRcQZWBYdmfGyEnUUpzD1geo2RLw b0ZBnpS3cpMPMMIVUaFQ+wJ7n2JkgF9d+uF/oGhvRSDj7r7BFQvWDk4e9JrX1hhrhG0/ QIpijc3GQvgevEm0tjmlF8LBQPL0B/KMhoSss982FXzkUUxg3XhRBkuAqOgmJt5CuW/f KJF5SLZ/QLo0Wz0yrRFw3TGZfs2c6niBrPXRoLRZNjGN7LYQ2KEMfY8u572uLtdhc9t9 TCFg==
Received: by 10.216.208.104 with SMTP id p82mr385275weo.119.1343978299161; Fri, 03 Aug 2012 00:18:19 -0700 (PDT)
Received: from [192.168.1.64] (host-2-102-217-126.as13285.net. [2.102.217.126]) by mx.google.com with ESMTPS id k20sm38060606wiv.11.2012.08.03.00.18.16 (version=SSLv3 cipher=OTHER); Fri, 03 Aug 2012 00:18:17 -0700 (PDT)
Message-ID: <501B7B43.70202@gmail.com>
Date: Fri, 03 Aug 2012 08:18:27 +0100
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: Steven Bellovin <smb@cs.columbia.edu>
Subject: Re: ITU-T Dubai Meeting
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu>	<B6033EB2-3B90-4524-A123-38852C5E2698@virtualized.org> <4401D68C-F9BB-4777-845A-A7011C50F1EA@cs.columbia.edu>
In-Reply-To: <4401D68C-F9BB-4777-845A-A7011C50F1EA@cs.columbia.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, 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, 03 Aug 2012 07:18:21 -0000

On 02/08/2012 21:30, Steven Bellovin wrote:
> On Aug 2, 2012, at 1:24 PM, David Conrad wrote:
> 
>> On Aug 2, 2012, at 11:44 AM, jnc@mercury.lcs.mit.edu (Noel Chiappa) wrote:
>>>> we should instead focus on the ways that the technical architecture of
>>>> the Internet creates control points that are vulnerable to capture and
>>>> consider ways in which those control points can be made capture-proof.
>>> Agreed.
>> The challenge of course is that one of the simple/efficient mechanisms to implement desirable features (e.g., security, scalability, manageability) is to create hierarchies, but those very hierarchies provide control points that can (at least in theory) be captured.  The DNS root is one such, the proposed RPKI root is another.  Perhaps a variation of the Software Engineering Dilemma ("fast, good, cheap: pick two") applies to Internet architecture: secure, scalable, manageable: pick two?
>>
>>>> If the ITU-T wants to also be in the business of handing out IPv6
>>>> address names then give then a /21 or a /16 and tell them to go
>>>> party.
>> I don't think this is what the ITU is after.  My impression is that the ITU is arguing that member states should get the /<whatever> directly.
>>
>>> I basically agree. It could have negative impacts on the routing, by impacting
>>> route aggregatability, but it can hardly be worse that those bletcherous PI
>>> addresses, so if it makes them happy to be in charge of a large /N, why not?
>> I believe the routing scalability risk lies not in the allocation body, but rather the policies imposed around the allocations.  That is, imagine a world of 200+ National Internet Registries instead of 5 Regional Internet registries.  If the government behind an NIR then decides that to use the Internet in their country, you must use addresses allocated by the NIR of that country, you then run the risk of having 200+ prefixes for each entity that operates globally.  This risk could be addressed if it didn't matter where you get your addresses, however that isn't true with the existing model and there are political pressures that would likely ensure that it would not be true in the NIR model.
> 
> 
> It also implies entry into a country through a few official gateways/exchange points -- that way, there are only ~200 entries plus your own country's that you need in your RIB...  (Telecom used to be that way -- PTTs and other monopolies (e.g., AT&T) loved it.)

Exactly. It is intended to defeat the Internet's historical growth model
of independence from national administrations and monopolies, by imposing
a geographical addressing scheme. Since the Internet actually works with
a topological addressing scheme, the effect is to force the topology
to be congruent with the geography. If you want central control, that's
a desirable result.

It isn't a harmless concession. We've been playing whack-a-mole against
this for a number of years now.

   Brian Carpenter

From robert@raszuk.net  Fri Aug  3 00:22:15 2012
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 D5A2F21E804E for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 00:22:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lZbTruV6usxN for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 00:22:15 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id C810F21E8041 for <ietf@ietf.org>; Fri,  3 Aug 2012 00:22:14 -0700 (PDT)
Received: (qmail 31317 invoked by uid 399); 3 Aug 2012 07:22:13 -0000
Received: from unknown (HELO ?10.0.1.2?) (pbs:robert@raszuk.net@64.114.198.24) by mail1310.opentransfer.com with ESMTPM; 3 Aug 2012 07:22:13 -0000
X-Originating-IP: 64.114.198.24
Message-ID: <501B7C22.3030706@raszuk.net>
Date: Fri, 03 Aug 2012 09:22:10 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Basic ietf process question ...
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com><CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com><CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com>	<501AA9DF.6010208@raszuk.net>	<EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com> <501AB4F5.7030205@raszuk.net> <501AC2C7.6040707@gmail.com> <501AC43A.3020307@raszuk.net> <501B767B.6030501@gmail.com>
In-Reply-To: <501B767B.6030501@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>, opsawg@ietf.org, 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: Fri, 03 Aug 2012 07:22:16 -0000

Hello Brian,

> That's an enormous leap that I just don't understand. Most protocols don't
> need that sort of configuration complexity.

Hmmmm I am of the opinion that most protocols requires configuration. I 
am also of the opinion that each vendor chooses an original way to 
configure their network elements.

Therefor if you do not define up front a standard based of configuring 
given routing protocol you will end up with exactly what we have today 
.. zoo of various different CLI commands to enable the exact same 
protocol across more then one vendor box.

Are you saying that this is ok ?

Or are you saying that there is simpler way to enable netconf based 
unified way to configure protocols and services on your network other 
then providing per component "xml schema" with subsequent schema 
extensions as part of IETF standardization process ?

To make it a bit more explicit ... do you really need to study 5 user 
manuals or google 5 times to enable IGP or BGP or even configure NTP 
across 5 different router OS running in your network ???

 > Again: no problem with creating XML schemata where they are useful.
 > But making them mandatory would be just as bad as making MIB modules
 > mandatory, IMHO.

Aha .. so you are saying that MIBs are not mandatory .... Very 
interesting. So I guess SSH to the routers and box by box cli 
provisioning is here to stay for a while I think :(

Best regards,
R.



From paf@frobbit.se  Fri Aug  3 00:25:46 2012
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34F9A21E8041 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 00:25:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jlIv-KL6IuTa for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 00:25:45 -0700 (PDT)
Received: from srv01.frobbit.se (srv01.frobbit.se [IPv6:2a02:80:3ffe::39]) by ietfa.amsl.com (Postfix) with ESMTP id 7F98721E8034 for <ietf@ietf.org>; Fri,  3 Aug 2012 00:25:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by srv01.frobbit.se (Postfix) with ESMTP id A6C29144C88C6; Fri,  3 Aug 2012 09:25:36 +0200 (CEST)
X-Virus-Scanned: amavisd-new at frobbit.se
Received: from srv01.frobbit.se ([127.0.0.1]) by localhost (srv01.frobbit.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lU+kldU+Ki0k; Fri,  3 Aug 2012 09:25:36 +0200 (CEST)
Received: from [IPv6:2a02:80:3ffc::14] (unknown [IPv6:2a02:80:3ffc::14]) (Authenticated sender: paf01) by srv01.frobbit.se (Postfix) with ESMTP id 06EDC144C88C3; Fri,  3 Aug 2012 09:25:36 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: ITU-T Dubai Meeting
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <501B7B43.70202@gmail.com>
Date: Fri, 3 Aug 2012 09:25:35 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <BF8D9FB8-E584-45C2-9CD6-4289F2DF303F@frobbit.se>
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu>	<B6033EB2-3B90-4524-A123-38852C5E2698@virtualized.org> <4401D68C-F9BB-4777-845A-A7011C50F1EA@cs.columbia.edu> <501B7B43.70202@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1485)
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: Fri, 03 Aug 2012 07:25:46 -0000

3 aug 2012 kl. 09:18 skrev Brian E Carpenter <brian.e.carpenter@gmail.com>:

> Exactly. It is intended to defeat the Internet's historical growth model
> of independence from national administrations and monopolies, by imposing
> a geographical addressing scheme. Since the Internet actually works with
> a topological addressing scheme, the effect is to force the topology
> to be congruent with the geography. If you want central control, that's
> a desirable result.

The key here is control.

Innovation in the core, or at the edge.

License/politically based or need based allocation.

The rest is implementation.

   Patrik


From daedulus@btconnect.com  Fri Aug  3 01:10:32 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 436F521F8B25 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 01:10:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.67
X-Spam-Level: 
X-Spam-Status: No, score=-3.67 tagged_above=-999 required=5 tests=[AWL=-0.070,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gsF0cmDIwU9D; Fri,  3 Aug 2012 01:10:30 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe005.messaging.microsoft.com [216.32.180.188]) by ietfa.amsl.com (Postfix) with ESMTP id 54B3021F8D3F; Fri,  3 Aug 2012 01:10:29 -0700 (PDT)
Received: from mail193-co1-R.bigfish.com (10.243.78.245) by CO1EHSOBE005.bigfish.com (10.243.66.68) with Microsoft SMTP Server id 14.1.225.23; Fri, 3 Aug 2012 08:10:26 +0000
Received: from mail193-co1 (localhost [127.0.0.1])	by mail193-co1-R.bigfish.com (Postfix) with ESMTP id 7D653DC034D; Fri,  3 Aug 2012 08:10:26 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.224.141; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0702HT006.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -24
X-BigFish: PS-24(zz98dI9371I542M1432Izz1202hzz1033IL8275bh8275dhz2dh2a8h5a9h668h839hd24hf0ah107ah304l)
Received: from mail193-co1 (localhost.localdomain [127.0.0.1]) by mail193-co1 (MessageSwitch) id 1343981423780254_10866; Fri,  3 Aug 2012 08:10:23 +0000 (UTC)
Received: from CO1EHSMHS015.bigfish.com (unknown [10.243.78.242])	by mail193-co1.bigfish.com (Postfix) with ESMTP id BCB04A00044; Fri,  3 Aug 2012 08:10:23 +0000 (UTC)
Received: from DB3PRD0702HT006.eurprd07.prod.outlook.com (157.55.224.141) by CO1EHSMHS015.bigfish.com (10.243.66.25) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 3 Aug 2012 08:10:23 +0000
Received: from SN2PRD0510HT001.namprd05.prod.outlook.com (157.56.234.117) by pod51017.outlook.com (10.3.4.165) with Microsoft SMTP Server (TLS) id 14.15.108.4; Fri, 3 Aug 2012 08:10:12 +0000
Message-ID: <007701cd714e$ccf1d140$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: "Andrew G. Malis" <agmalis@gmail.com>, IETF Administrative Director <iad@ietf.org>
References: <20120802164551.20569.2082.idtracker@ietfa.amsl.com> <CAA=duU0sByW_tkMupo-Ae8+9f3_-YN9yYT_g57tkbys7CwVjyQ@mail.gmail.com>
Subject: Re: Proposed IETF 95 Date Change
Date: Fri, 3 Aug 2012 09:01:39 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.234.117]
X-OriginatorOrg: btconnect.com
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 08:10:32 -0000

----- Original Message -----
From: "Andrew G. Malis" <agmalis@gmail.com>
To: "IETF Administrative Director" <iad@ietf.org>
Cc: "IETF Discussion" <ietf@ietf.org>
Sent: Thursday, August 02, 2012 10:42 PM
Subject: Re: Proposed IETF 95 Date Change
<snip>
>
On the
> other hand, travel on 27 March should be relatively easy.

Precisely, which makes the original dates better for travel than the
proposed alteration.  This is a relatively early (Easter) holiday, which
makes the run up to it frantic, so trying to get home on the
24th/25th/26th
I would expect to be a nightmare, whereas the following week will be
relatively quiet.

Stay with the original dates.

Tom Petch

>
> Cheers,
> Andy
>
> On Thu, Aug 2, 2012 at 9:45 AM, IETF Administrative Director
> <iad@ietf.org> wrote:
> > A reminder of the 6 August deadline for input.
> > Thanks
> >
> > The IAOC is seeking community feedback on a proposed date change for
IETF 95
> > scheduled for March 2016.
> >
> > Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27
March is Easter.
> >
> > The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016
and would like
> > feedback on those dates before making a decision.  Comments
appreciated to ietf@ietf.org
> > by 6 August 2012.
> >
> > Ray Pelletier
> > IETF Administrative Director
>



From ole@cisco.com  Fri Aug  3 02:30:30 2012
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC5BA21F8D55 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 02:30:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.449
X-Spam-Level: 
X-Spam-Status: No, score=-110.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rf5uSgN1QgP5 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 02:30:30 -0700 (PDT)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id C7F2B21F8D53 for <ietf@ietf.org>; Fri,  3 Aug 2012 02:30:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=391; q=dns/txt; s=iport; t=1343986229; x=1345195829; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=/wClWiXCla+l3JsqTHivyGpZ3D+CHKadnLKQ2PF3SnY=; b=IahtmSfceVRh3Ppe1TTTL6LEgp1IXjk81jKY0J0rhXpJLWtGnYw5q7X5 exmQsRAtwgb6xyDhTK3ZjeIVaAJIZ/GFKoP16xHOi48rILRk99i5MSKtU TSVBNjVGaRGj60ltkwQiQbHsXWUrZyDk6TDmqL5pNug9OlktsxDNYJ7Xa k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFAHiZG1CQ/khR/2dsb2JhbABCA4U0s3KBB4IhAQECAhIBAiU/EAtGVwYTIodrC5w/g0gQnFaLYYNJgyEDiE2SVoUygxqBBGKCf4E/
X-IronPort-AV: E=Sophos;i="4.77,706,1336348800";  d="scan'208";a="7102607"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-4.cisco.com with ESMTP; 03 Aug 2012 09:30:26 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q739UO3x014936; Fri, 3 Aug 2012 09:30:24 GMT
Date: Fri, 3 Aug 2012 02:30:23 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: =?ISO-8859-15?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
Subject: Re: ITU-T Dubai Meeting
In-Reply-To: <BF8D9FB8-E584-45C2-9CD6-4289F2DF303F@frobbit.se>
Message-ID: <alpine.OSX.2.01.1208030229470.13211@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu> <B6033EB2-3B90-4524-A123-38852C5E2698@virtualized.org> <4401D68C-F9BB-4777-845A-A7011C50F1EA@cs.columbia.edu> <501B7B43.70202@gmail.com> <BF8D9FB8-E584-45C2-9CD6-4289F2DF303F@frobbit.se>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org, Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 09:30:31 -0000

Plug:

http://www.cisco.com/web/about/ac123/ac147/archived_issues/ipj_15-2/ipj_15-2.pdf

Read the article "December in Dubai," I think you will find it 
interesting.

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo



From robert@raszuk.net  Fri Aug  3 07:31:45 2012
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 28E1A21F8D99 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 07:31:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qjo87hSVQDsA for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 07:31:44 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 5651921F8D6C for <ietf@ietf.org>; Fri,  3 Aug 2012 07:31:44 -0700 (PDT)
Received: (qmail 30588 invoked by uid 399); 3 Aug 2012 14:31:43 -0000
Received: from unknown (HELO ?10.0.1.2?) (pbs:robert@raszuk.net@64.114.198.24) by mail1310.opentransfer.com with ESMTPM; 3 Aug 2012 14:31:43 -0000
X-Originating-IP: 64.114.198.24
Message-ID: <501BE0CE.90605@raszuk.net>
Date: Fri, 03 Aug 2012 16:31:42 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: j.schoenwaelder@jacobs-university.de
Subject: Re: [OPSAWG] Basic ietf process question ...
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com> <CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com> <CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com> <501AA9DF.6010208@raszuk.net> <EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com> <501AB4F5.7030205@raszuk.net> <501AC2C7.6040707@gmail.com> <501AC43A.3020307@raszuk.net> <501B767B.6030501@gmail.com> <501B7C22.3030706@raszuk.net> <20120803132945.GD88437@elstar.local>
In-Reply-To: <20120803132945.GD88437@elstar.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: opsawg@ietf.org, 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: Fri, 03 Aug 2012 14:31:45 -0000

Hi Juergen,

Many thx for the great suggestion !

However perhaps you are much more knowledgeable in that area and could 
recommend which model fit the best the requirement to standardize 
configuration of any new protocol or protocol extension at least in the 
space of routing and routing protocols or services being based on them ?

As you know the current IRS framework driven by junisco is trying to 
come with common API to the routing system agreed across vendors. This 
is great as attempts never happened in the past.

But if we are at this phase I think creating a network elements 
abstraction layer and be able to configure/monitor any protocol and 
service at the unified way is one of the building blocks we should start 
with. And of course I think this is very clear to everyone if it is not 
made mandatory in each draft as new section or appendix it is just not 
going to happen in practice.

Best regards,
R.

> On Fri, Aug 03, 2012 at 09:22:10AM +0200, Robert Raszuk wrote:
>>
>> Aha .. so you are saying that MIBs are not mandatory .... Very
>> interesting. So I guess SSH to the routers and box by box cli
>> provisioning is here to stay for a while I think :(
>>
>
> Robert,
>
> you may want to take a closer look at the data models currently being
> defined in the NETMOD working group. Please review them and send any
> comments.
>
> /js
>


From vesely@tana.it  Fri Aug  3 08:19:58 2012
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C241F21F8DE9 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 08:19:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.719
X-Spam-Level: 
X-Spam-Status: No, score=-4.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V9CFs42TQ4vW for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 08:19:56 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id A140921F8DE8 for <ietf@ietf.org>; Fri,  3 Aug 2012 08:19:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1344007194; bh=L6MOheLECERarDcHP5PyVPWGhonlUBqGVZyNCMdo4Rc=; l=916; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=B0+Eag8d1bLM+jPfEXLpzsuyuUD+/n8rn6+7DWl91vEvgWcsvWVBvCtWZ0r8Dsb8Y jegTgBNj0RoczQMtbgham9CztvVvpZNX2xMb3i8iCq1ayROKgd7e8h3C3KLWPT260x qft+TZyVJKJpZg11unrhDq2uts5TGzDhokpX8+4c=
Received: from [208.181.206.141] (softdnserr [208.181.206.141]) (AUTH: PLAIN 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Fri, 03 Aug 2012 17:19:52 +0200 id 00000000005DC049.00000000501BEC1A.00004F83
Message-ID: <501BEC0D.1060404@tana.it>
Date: Fri, 03 Aug 2012 08:19:41 -0700
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: RFC Errata: when to file, and when not to
References: <CALaySJKV96tdXhzfPD1e1Mro_+gp5aDarF7Z06QrA+iQtnHkLw@mail.gmail.com> <501A5656.2050407@it.aoyama.ac.jp>
In-Reply-To: <501A5656.2050407@it.aoyama.ac.jp>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 15:19:58 -0000

On Thu 02/Aug/2012 03:28:38 -0700 Martin J. DÃ¼rst wrote:
> 
>> In particular, the errata system is NOT meant to be used as an issue
>> tracker;
> 
> Of course we have mailing lists, issue trackers, and wikis, but the
> problem is that none of them are for RFCs.

In addition, those tools seem to be intended rather for IETF internal
use than for general public.

> The question then comes up on whether we can do better. And my guess
> is that in this day and age of linked information, we should be able
> to do better. With the tools version of an RFC, which is quickly
> becoming the preferred version of many, it's already easy to find errata.

It is /not difficult/ to find errata.  "Easy" would mean that people
usually find them even if they're not purposely looking for them.  For
example, the existence of an approved errata could be signaled by
coloring the margin near the relevant text.


From drc@virtualized.org  Fri Aug  3 08:37:42 2012
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 F3BFC21F8DD7 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 08:37:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VraIUpomzqIn for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 08:37:41 -0700 (PDT)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id 1CF5921F8DCF for <ietf@ietf.org>; Fri,  3 Aug 2012 08:37:41 -0700 (PDT)
Received: from [10.0.1.8] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: drc) by trantor.virtualized.org (Postfix) with ESMTPSA id 020A61705A; Fri,  3 Aug 2012 15:37:39 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: ITU-T Dubai Meeting
From: David Conrad <drc@virtualized.org>
In-Reply-To: <6.2.5.6.2.20120802115334.04b486b8@resistor.net>
Date: Fri, 3 Aug 2012 08:37:39 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7557FA6E-827D-431F-B434-ACA619E1ACB2@virtualized.org>
References: <CAMm+LwhKUZK9RGSmrntB6ZZVfnXRsaZfUcpWvVhWnxWRgdBjbw@mail.gmail.com> <6.2.5.6.2.20120802115334.04b486b8@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1485)
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 15:37:42 -0000

On Aug 2, 2012, at 12:55 PM, SM <sm@resistor.net> wrote:
> If the ITU-T wants a /16 it is simply a matter of asking the IETF for =
it.

And, unless the reason the ITU-T was requesting the /16 was for some =
protocol that came up with that has global applicability that needed a =
/16 of IPv6 space, they'd be redirected to an RIR.

Regards,
-drc


From barryleiba.mailing.lists@gmail.com  Fri Aug  3 08:38:46 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D54E21F8DC6 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 08:38:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hHfZuBa5IDg6 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 08:38:46 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6BA6621F8DDD for <ietf@ietf.org>; Fri,  3 Aug 2012 08:38:45 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so1801201lbb.31 for <ietf@ietf.org>; Fri, 03 Aug 2012 08:38:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=0OyNPCK6daLW5F6Xy3zNxe87qbbvX0aUq5wOLFQo+u0=; b=qAq+SbfoIBY7L7E9q3BK1hvbPkaK9orweIzeaN3nGzPjExZMeec9NYjK+jv4QDhqMA oYkqzT35vXgzhzt+XmuCiRyMNbAzznFwc6TbDh8QhG1QKYXilhAeyKYiRJD/f+u4tnwk wW4OWVRi+TbyN67xGSbGWUDhyh/GL46qsWQE4PVNk+HXyl/KPs/YIVPrp5bspPJFYTbe Yd2pdo/E7hTqfVnztb7NmgathNzoLVn0hiAiFUM7V9zAxeJk5fHzcrGKp+QEKWoreD3e Ph/lI6UnU5PvoYNCAoWBZpnp4h5OhZ0GvBcICDA9IT9lzjmxLmQH6f6lXLtbXz5/T74h aIjg==
MIME-Version: 1.0
Received: by 10.152.136.18 with SMTP id pw18mr1964442lab.17.1344008324393; Fri, 03 Aug 2012 08:38:44 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.17.133 with HTTP; Fri, 3 Aug 2012 08:38:44 -0700 (PDT)
In-Reply-To: <501BEC0D.1060404@tana.it>
References: <CALaySJKV96tdXhzfPD1e1Mro_+gp5aDarF7Z06QrA+iQtnHkLw@mail.gmail.com> <501A5656.2050407@it.aoyama.ac.jp> <501BEC0D.1060404@tana.it>
Date: Fri, 3 Aug 2012 11:38:44 -0400
X-Google-Sender-Auth: -HcShVwL6jI-iLVVIe-Lc2Km4JI
Message-ID: <CAC4RtVCM17j0O-=LO5Mcgm64mg6C1XPw+y4a1giAU4oX7UxN3g@mail.gmail.com>
Subject: Re: RFC Errata: when to file, and when not to
From: Barry Leiba <barryleiba@computer.org>
To: Alessandro Vesely <vesely@tana.it>
Content-Type: multipart/alternative; boundary=f46d042f927ac029e404c65e528f
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 15:38:46 -0000

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

>
> > Of course we have mailing lists, issue trackers, and wikis, but the
> > problem is that none of them are for RFCs.
>
> In addition, those tools seem to be intended rather for IETF internal
> use than for general public.


I would say that "IETF internal use" would refer to chairs, ADs, the RFC
Editor (which is not a function that's part of the IETF, by the way), and
so on.  It's very easy for anyone, including my mother, should she want to,
to get a login to the IETF tools system.  We could perhaps make it more
obvious that one is needed, and how to do it, but I don't know that it's
any more of a hurdle than any of the 17,000 other web things that require a
"free one-time signup".

Anyway, as I said, we haven't sorted out how we would do this, and it might
be that something even easier than what we have now would be in order.


> It is /not difficult/ to find errata.  "Easy" would mean that people
> usually find them even if they're not purposely looking for them.  For
> example, the existence of an approved errata could be signaled by
> coloring the margin near the relevant text.
>

I like this idea.  Not colour, maybe -- despite the errata tool's format,
not all errata nicely fit into OLD/NEW text, and one often needs the
explanation even for those that do -- but perhaps an "errata" icon in the
margin next to the relevant text.  One could click the icon and be sent
straight to that erratum.

The trouble is that I can't see how we could do that automatically, so it
would require significant extra manual processing.  I don't have stats on
how many errata are "Verified" (and we'd only do this sort of thing for
those, I imagine), nor any real idea of how much extra work it would be for
someone to add the erratum links.  But no argument at all about how useful
it would likely be.

Barry

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

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">&gt; Of course we have mailing lists, issue =
trackers, and wikis, but the<br>
&gt; problem is that none of them are for RFCs.<br>
<br>
In addition, those tools seem to be intended rather for IETF internal<br>
use than for general public.</blockquote><div><br></div><div>I would say th=
at &quot;IETF internal use&quot; would refer to chairs, ADs, the RFC Editor=
 (which is not a function that&#39;s part of the IETF, by the way), and so =
on. =A0It&#39;s very easy for anyone, including my mother, should she want =
to, to get a login to the IETF tools system. =A0We could perhaps make it mo=
re obvious that one is needed, and how to do it, but I don&#39;t know that =
it&#39;s any more of a hurdle than any of the 17,000 other web things that =
require a &quot;free one-time signup&quot;.</div>
<div><br></div><div>Anyway, as I said, we haven&#39;t sorted out how we wou=
ld do this, and it might be that something even easier than what we have no=
w would be in order.</div><div>=A0</div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

It is /not difficult/ to find errata. =A0&quot;Easy&quot; would mean that p=
eople<br>
usually find them even if they&#39;re not purposely looking for them. =A0Fo=
r<br>
example, the existence of an approved errata could be signaled by<br>
coloring the margin near the relevant text.<br>
</blockquote><div><br></div><div>I like this idea. =A0Not colour, maybe -- =
despite the errata tool&#39;s format, not all errata nicely fit into OLD/NE=
W text, and one often needs the explanation even for those that do -- but p=
erhaps an &quot;errata&quot; icon in the margin next to the relevant text. =
=A0One could click the icon and be sent straight to that erratum.</div>
<div><br></div><div>The trouble is that I can&#39;t see how we could do tha=
t automatically, so it would require significant extra manual processing. =
=A0I don&#39;t have stats on how many errata are &quot;Verified&quot; (and =
we&#39;d only do this sort of thing for those, I imagine), nor any real ide=
a of how much extra work it would be for someone to add the erratum links. =
=A0But no argument at all about how useful it would likely be.</div>
<div><br></div><div>Barry<span></span></div>

--f46d042f927ac029e404c65e528f--

From afarrel@juniper.net  Thu Aug  2 08:38:57 2012
Return-Path: <afarrel@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 3809521F869F for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 08:38:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1wv5XkiE1nHk for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 08:38:56 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 7704621F869E for <ietf@ietf.org>; Thu,  2 Aug 2012 08:38:56 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q72Fcnrv031773;  Thu, 2 Aug 2012 16:38:49 +0100
Received: from 950129200 (dhcp-3167.meeting.ietf.org [130.129.49.103]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q72Fcgfb031696 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 2 Aug 2012 16:38:45 +0100
From: "Adrian Farrel" <afarrel@juniper.net>
To: "'joel jaeggli'" <joelja@bogus.com>, "'Scott Brim'" <scott.brim@gmail.com>
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com>	<CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com>	<CADnDZ8-6iTjav+utqDOXriKc3FUVesHAy0CD5FtFQjrWDMvuWA@mail.gmail.com>	<CAPv4CP-LBGVPn9O5N1HmbUqw8H7dpK66q7JEcrYA_Sd395giCA@mail.gmail.com> <501A8B5B.2070609@bogus.com>
In-Reply-To: <501A8B5B.2070609@bogus.com>
Subject: RE: New Version Notification for: draft-baryun-rfc2119-update-00.txt
Date: Thu, 2 Aug 2012 16:38:40 +0100
Message-ID: <011201cd70c4$e81abde0$b85039a0$@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLw+3MjyVCsgx/3v7ilGpHvBIxheAJ4IDYAAngh6QwBuKimbQKXHalqlLWRm9A=
Content-Language: en-gb
X-Mailman-Approved-At: Fri, 03 Aug 2012 08:48:43 -0700
Cc: 'Barry Leiba' <barryleiba@computer.org>, 'ietf' <ietf@ietf.org>, 'Abdussalam Baryun' <abdussalambaryun@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: afarrel@juniper.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 15:38:57 -0000

> A Change to the interpretation of normative language does not
> retroactively apply to existing documents.

Shucks! Really?

I was hoping I could automatically change the behavior of deployed routers by
updating the meaning of some words in published RFCs. You mean I can't do that?

A


From andy@yumaworks.com  Thu Aug  2 10:13:46 2012
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2366311E815E for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 10:13:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.697
X-Spam-Level: 
X-Spam-Status: No, score=-2.697 tagged_above=-999 required=5 tests=[AWL=0.280,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E81wybJJzXGC for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 10:13:45 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 562B811E813D for <ietf@ietf.org>; Thu,  2 Aug 2012 10:13:45 -0700 (PDT)
Received: by qcac10 with SMTP id c10so6031567qca.31 for <ietf@ietf.org>; Thu, 02 Aug 2012 10:13:44 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=se17rDsSnqDvp5SP2U+hl1dRTCXSbLwJKVpTRp9m1vc=; b=oums6ARSr2LU3RX5DIn/3cV/c0bIQBPAuwMvAm4614Vvb1inhuE2hGjSfd5pwrR+5H z4kri+JIrb+BXvN+yN/CHa1h7Ekn0QtzhOOIPxBkJhEbjZ+/9tiBMnO4EpbvOydCMI61 6PvMWqURDbJ7Iby1DaNjtFSHs2PP8j528iZS8UxLLmb0vEt/aeNBy4TWuKtx39f3A/9q B++ulzFZmcxK9e4/SBnk+zvvhmvG58PZiuz7rR9IkjO3oGPekT6AMp3Crj8cEB27hbH2 fZLqIV8KiFJfBYO6sZT0RSUUbXyic4rrTsbZuNJW7VeRQXpUnS05ppI6AJPqNkR9mHYH Ju5g==
MIME-Version: 1.0
Received: by 10.224.35.130 with SMTP id p2mr42909924qad.21.1343927624851; Thu, 02 Aug 2012 10:13:44 -0700 (PDT)
Received: by 10.49.26.168 with HTTP; Thu, 2 Aug 2012 10:13:44 -0700 (PDT)
X-Originating-IP: [2001:df8:0:64:e55b:8747:ab19:155b]
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com>
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com> <CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com> <CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com> <501AA9DF.6010208@raszuk.net> <EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com>
Date: Thu, 2 Aug 2012 10:13:44 -0700
Message-ID: <CABCOCHQwi7-Bi8itu5fZDpmEZDAufXwpS=zx68Xyq1xLzwOLng@mail.gmail.com>
Subject: Re: [OPSAWG] Basic ietf process question ...
From: Andy Bierman <andy@yumaworks.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Content-Type: text/plain; charset=UTF-8
X-Gm-Message-State: ALoCoQlTWc0jNmc1+ETx2j7DsLrWM1fPfCx2Dw9tY64XglYPcH941wDEjTZAWBlHSdlH7u7VuK1g
X-Mailman-Approved-At: Fri, 03 Aug 2012 08:50:06 -0700
Cc: opsawg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 17:13:46 -0000

On Thu, Aug 2, 2012 at 9:59 AM, Romascanu, Dan (Dan) <dromasca@avaya.com> wrote:
> Hi,
>
> The OPSAWG/OPSAREA open meeting this afternoon has an item on the agenda
> concerning the revision of RFC1052 and discussing a new architecture for
> management protocols.
>
>
> My personal take is that no one protocol, or one data modeling language
> can match the operational requirements to configure and manage the wide
> and wider range of hosts, routers and other network devices that are
> used to implement IP networks and protocols. We should be talking
> nowadays about a toolset rather than one tool that fits all. However,
> this is a discussion that just starts.

NMS developers need to spend too many resources on translating
naming and other data-modeling specific details so they can be
usable within the application.  So if 1 data modeling language
is not used, then deterministic, loss-less, round-trip translation
between data modeling languages is needed.  Multiple
protocols are not the problem -- incompatible data from multiple
protocols is the problem.

>
> Regards,
>
> Dan
>

Andy

>
>
>
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
> Of
>> Robert Raszuk
>> Sent: Thursday, August 02, 2012 7:25 PM
>> Cc: ietf@ietf.org
>> Subject: Basic ietf process question ...
>>
>> All,
>>
>> IETF documents have number of mandatory sections .. IANA Actions,
>> Security Considerations, Refs, etc ...
>>
>> Does anyone have a good reason why any new protocol definition or
>> enhancement does not have a build in mandatory "XML schema" section
>> which would allow to actually use such standards based enhancement in
>> vendor agnostic way ?
>>
>> There is a lot of talk about reinventing APIs, building network wide
> OS
>> platform, delivering SDNs (whatever it means at any point of time for
>> one) ... but how about we start with something very basic yet IMHO
>> necessary to slowly begin thinking of network as one plane.
>>
>> I understand that historically we had/still have SNMP however I have
>> never seen this being mandatory section of any standards track
> document.
>> Usually SNMP comes 5 years behind (if at all) making it obsolete by
>> design.
>>
>> NETCONF is great and very flexible communication channel for
>> provisioning. However it is sufficient to just look at number of ops
>> lists to see that those who tried to use it quickly abandoned their
>> efforts due to complete lack of XML schema from each vendor they
> happen
>> to use or complete mismatch of vendor to vendor XML interpretation.
>>
>> And while perhaps this is obvious I do not think that any new single
>> effort will address this. This has to be an atomic and integral part
> of
>> each WG's document.
>>
>> Looking forward for insightful comments ...
>>
>> Best,
>> R.
>>
>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg

From ietfdbh@comcast.net  Thu Aug  2 10:20:02 2012
Return-Path: <ietfdbh@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE5D911E8158 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 10:20:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.35
X-Spam-Level: 
X-Spam-Status: No, score=-102.35 tagged_above=-999 required=5 tests=[AWL=0.249, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id heet89Tgd6o3 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 10:20:01 -0700 (PDT)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [76.96.62.32]) by ietfa.amsl.com (Postfix) with ESMTP id DCB0B11E8148 for <ietf@ietf.org>; Thu,  2 Aug 2012 10:20:00 -0700 (PDT)
Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by qmta03.westchester.pa.mail.comcast.net with comcast id hmfd1j0051wpRvQ53tL3E0; Thu, 02 Aug 2012 17:20:03 +0000
Received: from [10.59.1.23] ([71.233.85.150]) by omta18.westchester.pa.mail.comcast.net with comcast id htRS1j00S3Ecudz3etRTAe; Thu, 02 Aug 2012 17:25:30 +0000
User-Agent: Microsoft-MacOutlook/14.2.3.120616
Date: Thu, 02 Aug 2012 13:19:55 -0400
Subject: Re: [OPSAWG] Basic ietf process question ...
From: David Harrington <ietfdbh@comcast.net>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, <robert@raszuk.net>
Message-ID: <CC402EF0.24386%ietfdbh@comcast.net>
Thread-Topic: [OPSAWG] Basic ietf process question ...
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Mailman-Approved-At: Fri, 03 Aug 2012 08:52:14 -0700
Cc: opsawg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 17:20:03 -0000

+1

--
David Harrington
Ietfdbh@comcast.net
+1-603-828-1401





On 8/2/12 12:59 PM, "Romascanu, Dan (Dan)" <dromasca@avaya.com> wrote:

>Hi,
>
>The OPSAWG/OPSAREA open meeting this afternoon has an item on the agenda
>concerning the revision of RFC1052 and discussing a new architecture for
>management protocols.
>
>
>My personal take is that no one protocol, or one data modeling language
>can match the operational requirements to configure and manage the wide
>and wider range of hosts, routers and other network devices that are
>used to implement IP networks and protocols. We should be talking
>nowadays about a toolset rather than one tool that fits all. However,
>this is a discussion that just starts.
>
>Regards,
>
>Dan
>
>
>
>
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
>Of
>> Robert Raszuk
>> Sent: Thursday, August 02, 2012 7:25 PM
>> Cc: ietf@ietf.org
>> Subject: Basic ietf process question ...
>> 
>> All,
>> 
>> IETF documents have number of mandatory sections .. IANA Actions,
>> Security Considerations, Refs, etc ...
>> 
>> Does anyone have a good reason why any new protocol definition or
>> enhancement does not have a build in mandatory "XML schema" section
>> which would allow to actually use such standards based enhancement in
>> vendor agnostic way ?
>> 
>> There is a lot of talk about reinventing APIs, building network wide
>OS
>> platform, delivering SDNs (whatever it means at any point of time for
>> one) ... but how about we start with something very basic yet IMHO
>> necessary to slowly begin thinking of network as one plane.
>> 
>> I understand that historically we had/still have SNMP however I have
>> never seen this being mandatory section of any standards track
>document.
>> Usually SNMP comes 5 years behind (if at all) making it obsolete by
>> design.
>> 
>> NETCONF is great and very flexible communication channel for
>> provisioning. However it is sufficient to just look at number of ops
>> lists to see that those who tried to use it quickly abandoned their
>> efforts due to complete lack of XML schema from each vendor they
>happen
>> to use or complete mismatch of vendor to vendor XML interpretation.
>> 
>> And while perhaps this is obvious I do not think that any new single
>> effort will address this. This has to be an atomic and integral part
>of
>> each WG's document.
>> 
>> Looking forward for insightful comments ...
>> 
>> Best,
>> R.
>> 
>
>_______________________________________________
>OPSAWG mailing list
>OPSAWG@ietf.org
>https://www.ietf.org/mailman/listinfo/opsawg



From william.atwood@concordia.ca  Thu Aug  2 11:19:23 2012
Return-Path: <william.atwood@concordia.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C8B021E810F for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 11:19:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.182
X-Spam-Level: 
X-Spam-Status: No, score=-6.182 tagged_above=-999 required=5 tests=[AWL=0.417,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TQ0M9xlpw3ze for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 11:19:22 -0700 (PDT)
Received: from oldperseverance.encs.concordia.ca (oldperseverance.encs.concordia.ca [132.205.96.94]) by ietfa.amsl.com (Postfix) with ESMTP id B255521E80CF for <ietf@ietf.org>; Thu,  2 Aug 2012 11:19:22 -0700 (PDT)
Received: from [IPv6:::1] (bill@poise.encs.concordia.ca [132.205.2.209]) by oldperseverance.encs.concordia.ca (envelope-from william.atwood@concordia.ca) (8.13.7/8.13.7) with ESMTP id q72IJJfT012075 for <ietf@ietf.org>; Thu, 2 Aug 2012 14:19:20 -0400
Message-ID: <501AC4A8.9050203@concordia.ca>
Date: Thu, 02 Aug 2012 14:19:20 -0400
From: John William Atwood <william.atwood@concordia.ca>
Organization: Concordia University, Montreal
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Proposed IETF 95 date change
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.58 on oldperseverance.encs.concordia.ca at 2012/08/02 14:19:21 EDT
X-Mailman-Approved-At: Fri, 03 Aug 2012 08:52:14 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 18:19:23 -0000

It's not clear to me which is less desirable, starting on Easter day, or
finishing on Good Friday.  Both are important from the Christian
perspective.  However, for a significant part of the IETF membership,
neither Easter nor Good Friday is important.  My vote would be to leave
it where it is.

  Bill Atwood

-- 
Dr. J.W. Atwood, Eng.             tel:   +1 (514) 848-2424 x3046
Distinguished Professor Emeritus  fax:   +1 (514) 848-2830
Department of Computer Science
   and Software Engineering
Concordia University EV 3.185     email:william.atwood@concordia.ca
1455 de Maisonneuve Blvd. West    http://users.encs.concordia.ca/~bill
Montreal, Quebec Canada H3G 1M8


From jhildebr@cisco.com  Thu Aug  2 14:17:42 2012
Return-Path: <jhildebr@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 7A26C11E81C5 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 14:17:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rd8rc9dUBGW6 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 14:17:41 -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 9B33211E81B3 for <ietf@ietf.org>; Thu,  2 Aug 2012 14:17:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jhildebr@cisco.com; l=1265; q=dns/txt; s=iport; t=1343942261; x=1345151861; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=HzoEA7JTuBatVAFRUn3qUUgAe97uV3w2HS8lz8vawDg=; b=YTFOK2bbwfHqEr+uDdx4fSCfT/s8TFgujkPVm2J6D6v8Qy5uXMWVmsgC kGo+1C+Sf83QQLUARQopC3cWx/HAQZjLAv55mye/+Jqu2m0cRKvnjdOJf pq3Ws+yLjxnRYJ1VwAWP3LwZfODpgWU5H5BGiRMlZuJt9tXkT94hhPFm7 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAFHtGlCtJV2Y/2dsb2JhbABFuRuBB4InEgEnPxIBCDZCJQIEDgUih2ucfaBGkk4DlUeLDQGDGYFmgl8
X-IronPort-AV: E=Sophos;i="4.77,703,1336348800"; d="scan'208";a="108002247"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-8.cisco.com with ESMTP; 02 Aug 2012 21:17:41 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q72LHf1I021569 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 2 Aug 2012 21:17:41 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.184]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.02.0298.004; Thu, 2 Aug 2012 16:17:40 -0500
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: "robert@raszuk.net" <robert@raszuk.net>
Subject: Re: Basic ietf process question ...
Thread-Topic: Basic ietf process question ...
Thread-Index: AQHNcPQ/BZi3xKSMb02eb5YX2IuheA==
Date: Thu, 2 Aug 2012 21:17:39 +0000
Message-ID: <CC403A23.1BE60%jhildebr@cisco.com>
In-Reply-To: <501AA9DF.6010208@raszuk.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.21.73.213]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19082.000
x-tm-as-result: No--36.795500-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8B808C9C9F6D9C479E4ADD9EBE4A3AE7@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 03 Aug 2012 08:52:14 -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: Thu, 02 Aug 2012 21:17:42 -0000

On 8/2/12 9:25 AM, "Robert Raszuk" <robert@raszuk.net> wrote:

>Does anyone have a good reason why any new protocol definition or
>enhancement does not have a build in mandatory "XML schema" section
>which would allow to actually use such standards based enhancement in
>vendor agnostic way ?

For docs that use XML, requiring some form of schema makes sense.
However, what we're finding at the application layer is that often times
using JSON (see RFC 4627) ends up with better interoperability more
quickly than using XML, except in the case of human-readable content like
marked-up text.  See RFC 6120, Appendix A (http://goo.gl/CBv8G) for
another example.

For those that insist on XML, RelaxNG (http://goo.gl/MYnB1) is another
language you can use to describe your XML, which is a little easier to
learn than XSD.

However, for implementors, if you start with the schema and blindly use it
for conformance checking of real-world traffic, you are likely to have
both performance and extensibility issues in practice.

If folks at other layers in the stack would like input from Apps folks,
I'm sure that we would be happy to share our lessons learned.  Join
apps-discuss (http://goo.gl/0Otjv) and ask for help.

--=20
Joe Hildebrand




From Kuor-Hsin.Chang@us.elster.com  Thu Aug  2 14:38:57 2012
Return-Path: <Kuor-Hsin.Chang@us.elster.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 050F221E80AF for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 14:38:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dDm1uI2mMdy3 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 14:38:56 -0700 (PDT)
Received: from mail136.messagelabs.com (mail136.messagelabs.com [216.82.249.3]) by ietfa.amsl.com (Postfix) with SMTP id 2932821E80A5 for <ietf@ietf.org>; Thu,  2 Aug 2012 14:38:56 -0700 (PDT)
X-Env-Sender: Kuor-Hsin.Chang@us.elster.com
X-Msg-Ref: server-5.tower-136.messagelabs.com!1343943530!7574887!2
X-Originating-IP: [129.179.1.27]
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.2; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31279 invoked from network); 2 Aug 2012 21:38:54 -0000
Received: from ip27.net129179-1.block1.us.syntegra.com (HELO us-smtp01.smtp.elster.com) (129.179.1.27) by server-5.tower-136.messagelabs.com with SMTP; 2 Aug 2012 21:38:54 -0000
In-Reply-To: <20120802164551.20569.2082.idtracker@ietfa.amsl.com>
References: <20120802164551.20569.2082.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
MIME-Version: 1.0
Subject: Re: Proposed IETF 95 Date Change
X-KeepSent: 659A2183:906666C4-88257A4E:00766B9B; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.3 September 15, 2011
From: Kuor-Hsin.Chang@us.elster.com
Message-ID: <OF659A2183.906666C4-ON88257A4E.00766B9B-88257A4E.0076CC60@gb.elster.com>
Date: Thu, 2 Aug 2012 14:37:47 -0700
X-MIMETrack: Serialize by Router on US-SMTP01.domino.elster-group.com/RIM-TEMP(Release 8.5.2FP3|July 10, 2011) at 08/02/2012 05:32:05 PM, Serialize complete at 08/02/2012 05:32:05 PM
Content-Type: multipart/alternative; boundary="=_alternative 007690E588257A4E_="
X-Mailman-Approved-At: Fri, 03 Aug 2012 08:52:14 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 21:38:57 -0000

This is a multipart message in MIME format.
--=_alternative 007690E588257A4E_=
Content-Type: text/plain; charset="US-ASCII"

I am fine with the date change but please coordinate with IEEE802 to make 
sure there is no conflict.

Best,

Kuor Hsin Chang



From:
IETF Administrative Director <iad@ietf.org>
To:
IETF Announcement List <ietf-announce@ietf.org>, 
Cc:
iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org, 
iesg@ietf.org
Date:
08/02/2012 09:48 AM
Subject:
Proposed IETF 95 Date Change
Sent by:
ietf-announce-bounces@ietf.org



A reminder of the 6 August deadline for input.
Thanks

The IAOC is seeking community feedback on a proposed date change for IETF 
95
scheduled for March 2016.

Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27 March is 
Easter.

The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 and 
would like 
feedback on those dates before making a decision.  Comments appreciated to 
ietf@ietf.org 
by 6 August 2012.

Ray Pelletier
IETF Administrative Director

______________________________________________________________________
This email has been spam and virus checked by Elster IT Services.


--=_alternative 007690E588257A4E_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif">I am fine with the date change but please
coordinate with IEEE802 to make sure there is no conflict.</font>
<br>
<br><font size=2 face="sans-serif">Best,</font>
<br>
<br><font size=2 face="sans-serif">Kuor Hsin Chang</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">From:</font>
<td><font size=1 face="sans-serif">IETF Administrative Director &lt;iad@ietf.org&gt;</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">To:</font>
<td><font size=1 face="sans-serif">IETF Announcement List &lt;ietf-announce@ietf.org&gt;,
</font>
<tr>
<td valign=top><font size=1 color=#5f5f5f face="sans-serif">Cc:</font>
<td><font size=1 face="sans-serif">iaoc@ietf.org, iab@iab.org, ietf@ietf.org,
wgchairs@ietf.org, iesg@ietf.org</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font>
<td><font size=1 face="sans-serif">08/02/2012 09:48 AM</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Subject:</font>
<td><font size=1 face="sans-serif">Proposed IETF 95 Date Change</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Sent by:</font>
<td><font size=1 face="sans-serif">ietf-announce-bounces@ietf.org</font></table>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>A reminder of the 6 August deadline for input.<br>
Thanks<br>
<br>
The IAOC is seeking community feedback on a proposed date change for IETF
95<br>
scheduled for March 2016.<br>
<br>
Currently IETF 95 is scheduled for 27 March to 1 April 2016. &nbsp;27 March
is Easter.<br>
<br>
The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 and
would like <br>
feedback on those dates before making a decision. &nbsp;Comments appreciated
to ietf@ietf.org <br>
by 6 August 2012.<br>
<br>
Ray Pelletier<br>
IETF Administrative Director<br>
<br>
______________________________________________________________________<br>
This email has been spam and virus checked by Elster IT Services.<br>
</font></tt>
<br>
--=_alternative 007690E588257A4E_=--

From philip_matthews@magma.ca  Thu Aug  2 10:09:37 2012
Return-Path: <philip_matthews@magma.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 971B021E80F8 for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 10:09:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.803
X-Spam-Level: 
X-Spam-Status: No, score=-1.803 tagged_above=-999 required=5 tests=[AWL=0.796,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qoDTKEy1ttOC for <ietf@ietfa.amsl.com>; Thu,  2 Aug 2012 10:09:36 -0700 (PDT)
Received: from mail-08.primus.ca (mail16.primus.ca [216.254.141.183]) by ietfa.amsl.com (Postfix) with ESMTP id A202821E8090 for <ietf@ietf.org>; Thu,  2 Aug 2012 10:09:36 -0700 (PDT)
Received: from dhcp-1483.meeting.ietf.org ([130.129.20.131]) by mail-08.primus.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <philip_matthews@magma.ca>) id 1Swytx-0005u9-1p for ietf@ietf.org; Thu, 02 Aug 2012 13:09:33 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Proposed IETF 95 Date Change
From: Philip Matthews <philip_matthews@magma.ca>
In-Reply-To: <20120802164551.20569.2082.idtracker@ietfa.amsl.com>
Date: Thu, 2 Aug 2012 10:09:31 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <FEF37558-FA51-4D8E-A6E9-654716CC3484@magma.ca>
References: <20120802164551.20569.2082.idtracker@ietfa.amsl.com>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-Authenticated: philip_matthews - dhcp-1483.meeting.ietf.org [130.129.20.131]
X-Mailman-Approved-At: Fri, 03 Aug 2012 08:52:14 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 17:09:37 -0000

I would personally prefer if the meeting was rescheduled for the week of =
April 3 - 8.
- Philip

On 2012-08-02, at 9:45 , IETF Administrative Director wrote:

> The IAOC is seeking community feedback on a proposed date change for =
IETF 95
> scheduled for March 2016.
>=20
> Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27 March =
is Easter.
>=20
> The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 =
and would like=20
> feedback on those dates before making a decision.  Comments =
appreciated to ietf@ietf.org=20
> by 6 August 2012.


From j.schoenwaelder@jacobs-university.de  Fri Aug  3 06:29:49 2012
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A02821F8D9D; Fri,  3 Aug 2012 06:29:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.205
X-Spam-Level: 
X-Spam-Status: No, score=-103.205 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t5zvJrKsF3Ct; Fri,  3 Aug 2012 06:29:47 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id BABA721F8D8E; Fri,  3 Aug 2012 06:29:47 -0700 (PDT)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id E1D2A20C0A; Fri,  3 Aug 2012 15:29:46 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id GKCI3dLssajV; Fri,  3 Aug 2012 15:29:46 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 0584820BFB; Fri,  3 Aug 2012 15:29:46 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id A306A2103BA8; Fri,  3 Aug 2012 15:29:45 +0200 (CEST)
Date: Fri, 3 Aug 2012 15:29:45 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Robert Raszuk <robert@raszuk.net>
Subject: Re: [OPSAWG] Basic ietf process question ...
Message-ID: <20120803132945.GD88437@elstar.local>
Mail-Followup-To: Robert Raszuk <robert@raszuk.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>, opsawg@ietf.org, ietf@ietf.org
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com> <CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com> <CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com> <501AA9DF.6010208@raszuk.net> <EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com> <501AB4F5.7030205@raszuk.net> <501AC2C7.6040707@gmail.com> <501AC43A.3020307@raszuk.net> <501B767B.6030501@gmail.com> <501B7C22.3030706@raszuk.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <501B7C22.3030706@raszuk.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Mailman-Approved-At: Fri, 03 Aug 2012 08:52:14 -0700
Cc: opsawg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 13:29:49 -0000

On Fri, Aug 03, 2012 at 09:22:10AM +0200, Robert Raszuk wrote:
> 
> Aha .. so you are saying that MIBs are not mandatory .... Very
> interesting. So I guess SSH to the routers and box by box cli
> provisioning is here to stay for a while I think :(
> 

Robert,

you may want to take a closer look at the data models currently being
defined in the NETMOD working group. Please review them and send any
comments.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

From j.schoenwaelder@jacobs-university.de  Fri Aug  3 08:31:05 2012
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3038221F8DCF; Fri,  3 Aug 2012 08:31:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.205
X-Spam-Level: 
X-Spam-Status: No, score=-103.205 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hJUGjspP3hmX; Fri,  3 Aug 2012 08:31:04 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 7540921F8DC3; Fri,  3 Aug 2012 08:31:04 -0700 (PDT)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id 5278420C0A; Fri,  3 Aug 2012 17:31:03 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id tOL92Xs9F__U; Fri,  3 Aug 2012 17:31:03 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id E23E120BED; Fri,  3 Aug 2012 17:31:02 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id C46142103DAB; Fri,  3 Aug 2012 17:31:00 +0200 (CEST)
Date: Fri, 3 Aug 2012 17:31:00 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Robert Raszuk <robert@raszuk.net>
Subject: Re: [OPSAWG] Basic ietf process question ...
Message-ID: <20120803153100.GA88678@elstar.local>
Mail-Followup-To: Robert Raszuk <robert@raszuk.net>, opsawg@ietf.org, ietf@ietf.org
References: <CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com> <501AA9DF.6010208@raszuk.net> <EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com> <501AB4F5.7030205@raszuk.net> <501AC2C7.6040707@gmail.com> <501AC43A.3020307@raszuk.net> <501B767B.6030501@gmail.com> <501B7C22.3030706@raszuk.net> <20120803132945.GD88437@elstar.local> <501BE0CE.90605@raszuk.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <501BE0CE.90605@raszuk.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Mailman-Approved-At: Fri, 03 Aug 2012 08:52:14 -0700
Cc: opsawg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 15:31:05 -0000

On Fri, Aug 03, 2012 at 04:31:42PM +0200, Robert Raszuk wrote:
> 
> But if we are at this phase I think creating a network elements
> abstraction layer and be able to configure/monitor any protocol and
> service at the unified way is one of the building blocks we should
> start with. And of course I think this is very clear to everyone if
> it is not made mandatory in each draft as new section or appendix it
> is just not going to happen in practice.
> 

Writing data models that are implementable on multiple platforms is
non trivial. We started working on your "building block" but it will
take time. And after all, a data model is only worth something if it
gets implemented.  A mandatory section does not help much with all of
this. What helps is people who commit time to work on it, who review
stuff, producing good and hopefully widely implementable models.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

From dburk@burkov.aha.ru  Fri Aug  3 08:54:18 2012
Return-Path: <dburk@burkov.aha.ru>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CEB621F8E37 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 08:54:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.902
X-Spam-Level: *
X-Spam-Status: No, score=1.902 tagged_above=-999 required=5 tests=[AWL=0.460,  BAYES_00=-2.599, HELO_EQ_RU=0.595, HELO_IS_SMALL6=0.556, HOST_EQ_RU=0.875, MIME_QP_LONG_LINE=1.396, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tMYOVTdcuuzV for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 08:54:17 -0700 (PDT)
Received: from aha.ru (backend13.aha.ru [62.113.86.202]) by ietfa.amsl.com (Postfix) with ESMTP id 0834821F8E30 for <ietf@ietf.org>; Fri,  3 Aug 2012 08:54:16 -0700 (PDT)
Received: from [83.149.9.12] (account dburk@burkov.aha.ru HELO [10.106.132.133]) by backend13.aha.ru (CommuniGate Pro SMTP 4.3.11) with ESMTPSA id 310670393; Fri, 03 Aug 2012 19:54:14 +0400
References: <CAMm+LwhKUZK9RGSmrntB6ZZVfnXRsaZfUcpWvVhWnxWRgdBjbw@mail.gmail.com> <6.2.5.6.2.20120802115334.04b486b8@resistor.net> <7557FA6E-827D-431F-B434-ACA619E1ACB2@virtualized.org>
In-Reply-To: <7557FA6E-827D-431F-B434-ACA619E1ACB2@virtualized.org>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <C9A6D67B-C4EE-4411-A4A8-69C27D66C577@burkov.aha.ru>
X-Mailer: iPhone Mail (9B206)
From: Dmitry Burkov <dburk@burkov.aha.ru>
Subject: Re: ITU-T Dubai Meeting
Date: Fri, 3 Aug 2012 19:52:03 +0400
To: David Conrad <drc@virtualized.org>
Cc: SM <sm@resistor.net>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 15:54:18 -0000

I hope too as they still ignore the procedures

Sent from my iPhone

On 03.08.2012, at 19:37, David Conrad <drc@virtualized.org> wrote:

> On Aug 2, 2012, at 12:55 PM, SM <sm@resistor.net> wrote:
>> If the ITU-T wants a /16 it is simply a matter of asking the IETF for it.=

>=20
> And, unless the reason the ITU-T was requesting the /16 was for some proto=
col that came up with that has global applicability that needed a /16 of IPv=
6 space, they'd be redirected to an RIR.
>=20
> Regards,
> -drc
>=20

From randy_presuhn@mindspring.com  Fri Aug  3 09:18:41 2012
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 8A8AF21F8E57; Fri,  3 Aug 2012 09:18:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xLNBRRvOissx; Fri,  3 Aug 2012 09:18:41 -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 E6A9D21F8E54; Fri,  3 Aug 2012 09:18:40 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=ehI2/7sAO48DEMr7AsdlCx+SWeFXZfdBkcDtBh0HerkfURte7xXbZzV5Q/el5WyJ; h=Received:Message-ID:From:To:Cc:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [76.254.55.169] (helo=oemcomputer) by elasmtp-junco.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1SxKaG-0002vX-FK; Fri, 03 Aug 2012 12:18:40 -0400
Message-ID: <006601cd7194$6681e620$6b01a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <opsawg@ietf.org>
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com><CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com><CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com><501AA9DF.6010208@raszuk.net><EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com> <CABCOCHQwi7-Bi8itu5fZDpmEZDAufXwpS=zx68Xyq1xLzwOLng@mail.gmail.com>
Subject: Re: [OPSAWG] Basic ietf process question ...
Date: Fri, 3 Aug 2012 09:24:03 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888b7f3a87d4e9c50f11d75e9d171ba3468f40dcd775cc11f38350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 76.254.55.169
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 16:18:41 -0000

Hi -

> From: "Andy Bierman" <andy@yumaworks.com>
> To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
> Cc: <opsawg@ietf.org>; <ietf@ietf.org>
> Sent: Thursday, August 02, 2012 10:13 AM
> Subject: Re: [OPSAWG] Basic ietf process question ...
...
> NMS developers need to spend too many resources on translating
> naming and other data-modeling specific details so they can be
> usable within the application.  So if 1 data modeling language
> is not used, then deterministic, loss-less, round-trip translation
> between data modeling languages is needed.  Multiple
> protocols are not the problem -- incompatible data from multiple
> protocols is the problem.
...

Picking a single language or set of round-trip translatable languages
also isn't enough.  Its a fact of life that vendors will produce
models and implementations that are slightly, or even radically different.
The differences aren't necessarily even intentional, but nonetheless
introduce the need to talk about "similar" models and "operationally
equivalent" configurations, where the transformations needed to go
from what will do the job on one piece of equipment to what will
work on another may be substantial.  (From an implementation perspective
it might be better to think in terms of transformations necessary to go
from a common model of desired operational characteristics to the
dial tweaks and button pokes necessary to get a device to do the right
thing.)  Since great minds often think alike, even in the absence
of standards, there is not necessarily a formal "derived from" or
"subclass" or "common aspect" relationship between the definitions.
This may be an obvious use case for XSLT, but as far as I know nothing
has been done about *standardizing* such usage, other than discussions at the
IAB workshop oh-so-many years ago, and some ISO/ITU discussions in
the 1990s about eventual applications of the General Relationship
Model and the management domain/policy stuff in GDMO land.

Randy


From housley@vigilsec.com  Fri Aug  3 09:59:25 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FEB721F8E03 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 09:59:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.619
X-Spam-Level: 
X-Spam-Status: No, score=-102.619 tagged_above=-999 required=5 tests=[AWL=-0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id akN4R+EnHpQU for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 09:59:25 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id D1DFA21F8DF7 for <ietf@ietf.org>; Fri,  3 Aug 2012 09:59:24 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 939EEF2403F; Fri,  3 Aug 2012 12:59:42 -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 I1TnxJx2nnjz; Fri,  3 Aug 2012 12:59:09 -0400 (EDT)
Received: from dhcp-55b9.meeting.ietf.org (dhcp-55b9.meeting.ietf.org [130.129.85.185]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id A2A05F2403B; Fri,  3 Aug 2012 12:59:41 -0400 (EDT)
Subject: Re: Progress with Open Internet endowment
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <42A8E91A-9802-4BFA-B245-B67F1B9E1ACE@vigilsec.com>
Date: Fri, 3 Aug 2012 12:59:21 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9051A6BB-B1C4-4A3A-B340-FFC940ACA9C9@vigilsec.com>
References: <019d01cd70e6$fe6dcc50$fb4964f0$@olddog.co.uk> <42A8E91A-9802-4BFA-B245-B67F1B9E1ACE@vigilsec.com>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: oie@internetsociety.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 16:59:25 -0000

As of Friday morning, we are very close to the goal.  As of 9:00 AM this =
morning, we have $24,905 from 80 donors.  Please help if you can.

Thanks,
  Russ


On Aug 2, 2012, at 4:27 PM, Russ Housley wrote:

> Our current totals as of noon today, the Open Internet Endowment has =
received $19,245 from 54 donors.  Thanks to all.
>=20
> It would be great to reach $25,000 (or more) from 75 donors (or more) =
by lunch tomorrow.  Please help if you can.
>=20
> There will be a table at the Bits-N-Bites tonight.  People will be at =
the table to answer any questions you might have.
>=20
> Thanks,
>  Russ
>=20


From paul.hoffman@vpnc.org  Fri Aug  3 10:18:55 2012
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 880CD21F8E24 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 10:18:55 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L3gKqMrBr5ju for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 10:18:55 -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 094FE21F8E20 for <ietf@ietf.org>; Fri,  3 Aug 2012 10:18:54 -0700 (PDT)
Received: from dhcp-2066.meeting.ietf.org (dhcp-2066.meeting.ietf.org [130.129.32.102]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q73GRfjb030164 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Fri, 3 Aug 2012 09:27:41 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Meeting "lounges" at IETF meetings
Date: Fri, 3 Aug 2012 10:18:50 -0700
Message-Id: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org>
To: ietf list <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 17:18:55 -0000

Greetings again. Some meeting venues have had insufficient places where =
five or so people could comfortably gather for informal meetings, while =
other venues did this just fine. One proposal has been that the =
Secretariat reserve large rooms for this. Unfortunately, that adds =
significant cost to the meetings.

Instead, I propose that we simply designate the terminal room (which is =
already reserved for future meetings) be designated as meeting areas =
where talking is allowed / encouraged. Earplugs could be provided for =
people who really want a quiet Ethernet connection; the cost of those =
for the Secretariat will be about $25/meeting.

--Paul Hoffman=

From scott.brim@gmail.com  Fri Aug  3 10:20:58 2012
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 2511421F8DDC for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 10:20:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.591
X-Spam-Level: 
X-Spam-Status: No, score=-103.591 tagged_above=-999 required=5 tests=[AWL=0.008, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IEt9pP9M4No0 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 10:20:57 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 816CE21F8DDB for <ietf@ietf.org>; Fri,  3 Aug 2012 10:20:57 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so1071075vbb.31 for <ietf@ietf.org>; Fri, 03 Aug 2012 10:20:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=GyMBg59z16MeqdtlcTXRo0FL/GOVaDiynP+Tx0iGe8c=; b=UT9JxYiJ8qNvR5FIYXJ0BZjKwCXn86SJ3i2dBFpjtJDT2hL2HDcg7u1Bna4MkuNYvj 4lb7XjPi/AjeUwwXRfeFOOHyJGJiZ9ZBP1OgSaeOxEI6mFLS/yBu/Ly7o8t5zwhDarTh KcTx6vMrOMMn4wnxNFt9N3gnYba09VPCAIeEGSTe0Ac1jAgzwmV6CWAuDRpeLKJBb5PE NwplJYYFVVzyfKN33M5ssk7+V2wjk0lDX5ozK8+RVjA7e0LX6+N0qnLO1AGWM3d0hTqF 0GfMxJl272CXbCAcx3Tb6cXYRzzv6EXtPClV1i3oeSOJ8ZOoItqu9bnOogy2UCiJp6g0 W6JA==
Received: by 10.220.214.8 with SMTP id gy8mr1914639vcb.45.1344014457026; Fri, 03 Aug 2012 10:20:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.100.199 with HTTP; Fri, 3 Aug 2012 10:20:36 -0700 (PDT)
In-Reply-To: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org>
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org>
From: Scott Brim <scott.brim@gmail.com>
Date: Fri, 3 Aug 2012 10:20:36 -0700
Message-ID: <CAPv4CP_qu_s_O4FWXmMvdkoWhMBcFWhG6c0MxQZ2qN8WBCh-LA@mail.gmail.com>
Subject: Re: Meeting "lounges" at IETF meetings
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 17:20:58 -0000

On Fri, Aug 3, 2012 at 10:18 AM, Paul Hoffman <paul.hoffman@vpnc.org> wrote=
:
> Greetings again. Some meeting venues have had insufficient places where f=
ive or so people could comfortably gather for informal meetings, while othe=
r venues did this just fine. One proposal has been that the Secretariat res=
erve large rooms for this. Unfortunately, that adds significant cost to the=
 meetings.
>
> Instead, I propose that we simply designate the terminal room (which is a=
lready reserved for future meetings) be designated as meeting areas where t=
alking is allowed / encouraged. Earplugs could be provided for people who r=
eally want a quiet Ethernet connection; the cost of those for the Secretari=
at will be about $25/meeting.

Sounds good.

I volunteer to collect free headsets from airplanes and put them out
for people to take.

From mnot@mnot.net  Fri Aug  3 10:47:54 2012
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E0D021F8DEC; Fri,  3 Aug 2012 10:47:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ykWwkwTETqYM; Fri,  3 Aug 2012 10:47:53 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 1457821F8D60; Fri,  3 Aug 2012 10:47:52 -0700 (PDT)
Received: from [10.6.130.84] (unknown [50.56.228.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id D197822E253; Fri,  3 Aug 2012 13:47:45 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: Basic ietf process question ...
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <501AC2C7.6040707@gmail.com>
Date: Fri, 3 Aug 2012 12:47:44 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <270DDF46-AA04-49C0-B54C-35FD0AE0350F@mnot.net>
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com><CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com><CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com>	<501AA9DF.6010208@raszuk.net>	<EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com> <501AB4F5.7030205@raszuk.net> <501AC2C7.6040707@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1485)
Cc: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>, opsawg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 17:47:54 -0000

On 02/08/2012, at 1:11 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> I think anyone with intimate experience of the Web Services standards

I do, unfortunately.

Specifically: contributor to SOAP, WS-Addressing, WS-Policy, MTOM, lead =
editor of the WS-I Basic Profile, etc. (ad nauseum).


> experiment (trying to use XML as if it was a Turing machine) would =
have
> extreme doubts about any proposal to impose such a requirement.
>=20
> It was not for no reason that many people came to refer to the Web
> Services family of standards as "WS-splat". The words "small" and
> "xml schema" don't really belong together,

+1

XML Schema is grossly over-engineered for its purpose; being the subject =
of requirements from not only the document markup field, but also =
databases and object models, it's a twisted monstrosity that tries to do =
many things, and fails at most.

Specifically, it's very common for people to try to use schema to inform =
"binding" tools into specific languages. However, the underlying =
metamodel of XML, the Infoset, is both complex and a poor fit for most =
languages, so bindings take "shortcuts" and expose a profile of XML's =
range of expression, encouraging some patterns of use, while =
discouraging (or disallowing) others. Since the bindings often make =
different decisions (based upon the language of use), interoperability =
is difficult (sometimes, impossible).

Furthermore, designing a schema that is extensible is incredibly =
convoluted in XML Schema 1.0. Schema 1.1 was designed to address this =
failure, but it hasn't been broadly adopted; most people I know in the =
field consider it a failure.=20

What surprises me and many others is that people are still using it and =
promoting it, when it's well-understood by almost EVERYONE who was =
involved in using XML for protocols in the past ten years agrees that =
it's a mistake.

Cheers,


>=20
> Regards
>   Brian Carpenter
>=20
> On 02/08/2012 18:12, Robert Raszuk wrote:
>> Hi Dan,
>>=20
>>> We should be talking
>>> nowadays about a toolset rather than one tool that fits all.
>>=20
>> Just to clarify what I asked about .. I am not looking for a single =
tool
>> or single protocol to be used to configure everything.
>>=20
>> I am asking for small building block like xml schema (or something
>> similar) to be part of each new IETF proposal or protocol change. =
IMHO
>> only that can allow any further more fancy abstractions and tools to =
be
>> build and used in practice.
>>=20
>> Best regards,
>> R.
>>=20
>>=20
>>=20
>>> Hi,
>>>=20
>>> The OPSAWG/OPSAREA open meeting this afternoon has an item on the =
agenda
>>> concerning the revision of RFC1052 and discussing a new architecture =
for
>>> management protocols.
>>>=20
>>>=20
>>> My personal take is that no one protocol, or one data modeling =
language
>>> can match the operational requirements to configure and manage the =
wide
>>> and wider range of hosts, routers and other network devices that are
>>> used to implement IP networks and protocols. We should be talking
>>> nowadays about a toolset rather than one tool that fits all. =
However,
>>> this is a discussion that just starts.
>>>=20
>>> Regards,
>>>=20
>>> Dan
>>>=20
>>>=20
>>>=20
>>>=20
>>>> -----Original Message-----
>>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On =
Behalf
>>> Of
>>>> Robert Raszuk
>>>> Sent: Thursday, August 02, 2012 7:25 PM
>>>> Cc: ietf@ietf.org
>>>> Subject: Basic ietf process question ...
>>>>=20
>>>> All,
>>>>=20
>>>> IETF documents have number of mandatory sections .. IANA Actions,
>>>> Security Considerations, Refs, etc ...
>>>>=20
>>>> Does anyone have a good reason why any new protocol definition or
>>>> enhancement does not have a build in mandatory "XML schema" section
>>>> which would allow to actually use such standards based enhancement =
in
>>>> vendor agnostic way ?
>>>>=20
>>>> There is a lot of talk about reinventing APIs, building network =
wide
>>> OS
>>>> platform, delivering SDNs (whatever it means at any point of time =
for
>>>> one) ... but how about we start with something very basic yet IMHO
>>>> necessary to slowly begin thinking of network as one plane.
>>>>=20
>>>> I understand that historically we had/still have SNMP however I =
have
>>>> never seen this being mandatory section of any standards track
>>> document.
>>>> Usually SNMP comes 5 years behind (if at all) making it obsolete by
>>>> design.
>>>>=20
>>>> NETCONF is great and very flexible communication channel for
>>>> provisioning. However it is sufficient to just look at number of =
ops
>>>> lists to see that those who tried to use it quickly abandoned their
>>>> efforts due to complete lack of XML schema from each vendor they
>>> happen
>>>> to use or complete mismatch of vendor to vendor XML interpretation.
>>>>=20
>>>> And while perhaps this is obvious I do not think that any new =
single
>>>> effort will address this. This has to be an atomic and integral =
part
>>> of
>>>> each WG's document.
>>>>=20
>>>> Looking forward for insightful comments ...
>>>>=20
>>>> Best,
>>>> R.
>>>>=20
>>>=20
>>>=20
>>>=20
>>=20
>>=20

--
Mark Nottingham
http://www.mnot.net/





From mary.ietf.barnes@gmail.com  Fri Aug  3 11:22:13 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26AC621F8E25 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 11:22:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.523
X-Spam-Level: 
X-Spam-Status: No, score=-103.523 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BbrWWbz1dGAR for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 11:22:11 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4B45C21F8D80 for <ietf@ietf.org>; Fri,  3 Aug 2012 11:22:05 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so1893692lbb.31 for <ietf@ietf.org>; Fri, 03 Aug 2012 11:22:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=kSXd4JnBO0eh2Ds4YWl+MA6Wq/KW7OXFlZ3cwjZ1tpU=; b=JYVEc7mwsR+nc+/PnGadGqjyMwMsRMknU4GyNOkECnCb4DE5lEoeEn5JkNEhkWWTwQ OOZ5UUZo/G3r8CWqUlHapCcmGLh8GpqIAy3vfcGuE35msdYf2XYANsK15bTkjLcTuCH/ LyxhY1gZWgnYQIkr3fanHpP8a/RFdOOZ1JDw1v68KgAucFngZv3KoiKpEfqld7ev+qNz RRWdOpFNcHEM0LbJBCeZj/yYV+GtDdYxlxMjVxHvDPyYvCn/6AzUjGP3jX8o4yYefON5 bMy6w83ewJfn2oLgiu4o+LIfTKp6sr7wPHkzjASlDxLXhEIwYee5rPsyjOFkj6dUB3cQ onPA==
MIME-Version: 1.0
Received: by 10.152.131.37 with SMTP id oj5mr2373888lab.14.1344018124283; Fri, 03 Aug 2012 11:22:04 -0700 (PDT)
Received: by 10.112.85.196 with HTTP; Fri, 3 Aug 2012 11:22:04 -0700 (PDT)
In-Reply-To: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org>
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org>
Date: Fri, 3 Aug 2012 13:22:04 -0500
Message-ID: <CAHBDyN6VaL3fgYe+C+o9d93VZ1bR_EDmrPN7-Sv+7BiJ9+Q9AA@mail.gmail.com>
Subject: Re: Meeting "lounges" at IETF meetings
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: multipart/alternative; boundary=f46d042c6b8dde9e0b04c6609a4e
Cc: ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 18:22:13 -0000

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

I don't like this idea at all.  For people that aren't staying at the
meeting hotel, the terminal room is often the only place where it is quiet.
 Ear plugs only partially address the problem for those of us with really
sensitive hearing and some folks cannot use those ear plugs (e.g., when you
have an ear infection, which I often get from the air conditioning in these
venues).

Instead, I think we should ensure that future venues have adequate space
for both circulating between meeting rooms and for side conversations.
 This hotel was really bad in that respect.  The corridor outside the
Regency rooms was always packed between sessions and getting from B to E
was impossible without bumping into people.  One problem was that people
stopped in the corridor for discussions, which is a normal thing to do at
IETF meetings, but it totally clogged up the hallways and often blocked the
access to the coffee.  This makes me wonder if the folks that choose the
venue discuss the nature of our meetings - i.e., almost everyone is moving
between meeting rooms multiple times a day.  Also, at least half the people
have backpacks and the majority are men.  Thus, the footprint for each of
us is larger than the average conference attendee.   I would suggest for
this next meeting at this hotel to put the refreshments in the open space
on the 3rd floor and put some chairs or tables in the alcoves and along the
wall where they put the refreshments.  Or better yet, reserve one of the
rooms for the refreshments and/or meeting space.  We had that at one of the
recent meetings and it worked extremely well.    I suggest that you could
cut the cookie budget if funds really are the only reason this wouldn't be
done.

Mary.


On Fri, Aug 3, 2012 at 12:18 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> Greetings again. Some meeting venues have had insufficient places where
> five or so people could comfortably gather for informal meetings, while
> other venues did this just fine. One proposal has been that the Secretariat
> reserve large rooms for this. Unfortunately, that adds significant cost to
> the meetings.
>
> Instead, I propose that we simply designate the terminal room (which is
> already reserved for future meetings) be designated as meeting areas where
> talking is allowed / encouraged. Earplugs could be provided for people who
> really want a quiet Ethernet connection; the cost of those for the
> Secretariat will be about $25/meeting.
>
> --Paul Hoffman

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

I don&#39;t like this idea at all. =A0For people that aren&#39;t staying at=
 the meeting hotel, the terminal room is often the only place where it is q=
uiet. =A0Ear plugs only partially address the problem for those of us with =
really sensitive hearing and some folks cannot use those ear plugs (e.g., w=
hen you have an ear infection, which I often get from the air conditioning =
in these venues).=A0<div>
<br></div><div>Instead, I think we should ensure that future venues have ad=
equate space for both circulating between meeting rooms and for side conver=
sations. =A0This hotel was really bad in that respect. =A0The corridor outs=
ide the Regency rooms was always packed between sessions and getting from B=
 to E was impossible without bumping into people. =A0One problem was that p=
eople stopped in the corridor for discussions, which is a normal thing to d=
o at IETF meetings, but it totally clogged up the hallways and often blocke=
d the access to the coffee. =A0This makes me wonder if the folks that choos=
e the venue discuss the nature of our meetings - i.e., almost everyone is m=
oving between meeting rooms multiple times a day. =A0Also, at least half th=
e people have backpacks and the majority are men. =A0Thus, the footprint fo=
r each of us is larger than the average conference attendee. =A0 I would su=
ggest for this next meeting at this hotel to put the refreshments in the op=
en space on the 3rd floor and put some chairs or tables in the alcoves and =
along the wall where they put the refreshments. =A0Or better yet, reserve o=
ne of the rooms for the refreshments and/or meeting space. =A0We had that a=
t one of the recent meetings and it worked extremely well. =A0 =A0I suggest=
 that you could cut the cookie budget if funds really are the only reason t=
his wouldn&#39;t be done.=A0</div>
<div><br></div><div>Mary.=A0</div><div><br></div><div><br><div class=3D"gma=
il_quote">On Fri, Aug 3, 2012 at 12:18 PM, Paul Hoffman <span dir=3D"ltr">&=
lt;<a href=3D"mailto:paul.hoffman@vpnc.org" target=3D"_blank">paul.hoffman@=
vpnc.org</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Greetings again. Some meeting venues have ha=
d insufficient places where five or so people could comfortably gather for =
informal meetings, while other venues did this just fine. One proposal has =
been that the Secretariat reserve large rooms for this. Unfortunately, that=
 adds significant cost to the meetings.<br>

<br>
Instead, I propose that we simply designate the terminal room (which is alr=
eady reserved for future meetings) be designated as meeting areas where tal=
king is allowed / encouraged. Earplugs could be provided for people who rea=
lly want a quiet Ethernet connection; the cost of those for the Secretariat=
 will be about $25/meeting.<br>

<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--Paul Hoffman</font></span></blockquote></div><br></div>

--f46d042c6b8dde9e0b04c6609a4e--

From marka@isc.org  Fri Aug  3 11:25:15 2012
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 30ECC21F8D65 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 11:25:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.58
X-Spam-Level: 
X-Spam-Status: No, score=-2.58 tagged_above=-999 required=5 tests=[AWL=0.019,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zsnhx2cCd9lb for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 11:25:14 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id B530721F8C0A for <ietf@ietf.org>; Fri,  3 Aug 2012 11:25:14 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS id 83D66C9572; Fri,  3 Aug 2012 18:25:01 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:df8:0:64:9184:45d4:f7ad:eb5d]) (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 69300216C33; Fri,  3 Aug 2012 18:25:01 +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 1F9512344DBF; Sat,  4 Aug 2012 04:25:00 +1000 (EST)
To: Daniel Karrenberg <daniel.karrenberg@ripe.net>
From: Mark Andrews <marka@isc.org>
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu> <CAMm+Lwg2HgO-=9ED4vbmO+Vf9r6bYPcLDgfyMAyPdEPVgRm4LQ@mail.gmail.com> <FB949BEA-5BDB-401A-8A75-E9A9BDAA72A6@ripe.net>
Subject: Re: ITU-T Dubai Meeting
In-reply-to: Your message of "Fri, 03 Aug 2012 07:42:16 +0200." <FB949BEA-5BDB-401A-8A75-E9A9BDAA72A6@ripe.net>
Date: Sat, 04 Aug 2012 04:25:00 +1000
Message-Id: <20120803182500.1F9512344DBF@drugs.dv.isc.org>
Cc: Phillip Hallam-Baker <hallam@gmail.com>, Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 18:25:15 -0000

In message <FB949BEA-5BDB-401A-8A75-E9A9BDAA72A6@ripe.net>, Daniel Karrenberg w
rites:
> 
> On 02.08.2012, at 22:41, Phillip Hallam-Baker wrote:
> 
> > ... That depends on whether the registry in question is dealing with a
> > scarce resource or a plentiful one. Having two registries handing out
> > IPv4 addresses at this point would be very very bad. Having more than
> > one place you can get an IPv6 from would not worry me at all. ...
> 
> IPv4 addresses used to be regarded as non-scarce not so long ago.

I don't know what planet you have been living on but it was clear
IPv4 addresses were a scarce resource 2+ decades ago longer than
some IETF attendees have been alive.  IPv6 was started because they
were a scarce resource that would run out in the foreseeable future.

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

From paul.hoffman@vpnc.org  Fri Aug  3 11:42:58 2012
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 5985421E8051 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 11:42:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.739
X-Spam-Level: 
X-Spam-Status: No, score=-102.739 tagged_above=-999 required=5 tests=[AWL=-0.140, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D3xGEn-trgpn for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 11:42:58 -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 D72A321E8049 for <ietf@ietf.org>; Fri,  3 Aug 2012 11:42:57 -0700 (PDT)
Received: from dhcp-2066.meeting.ietf.org (dhcp-2066.meeting.ietf.org [130.129.32.102]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q73HphdP095318 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 3 Aug 2012 10:51:44 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: Meeting "lounges" at IETF meetings
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CAHBDyN6VaL3fgYe+C+o9d93VZ1bR_EDmrPN7-Sv+7BiJ9+Q9AA@mail.gmail.com>
Date: Fri, 3 Aug 2012 11:42:53 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <345BE467-B3CA-41EE-9577-6985E3555C8A@vpnc.org>
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org> <CAHBDyN6VaL3fgYe+C+o9d93VZ1bR_EDmrPN7-Sv+7BiJ9+Q9AA@mail.gmail.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
X-Mailer: Apple Mail (2.1278)
Cc: ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 18:42:58 -0000

On Aug 3, 2012, at 11:22 AM, Mary Barnes wrote:

> Instead, I think we should ensure that future venues have adequate =
space for both circulating between meeting rooms and for side =
conversations.

Just to be clear: you would rather that we pay higher meeting fees in =
exchange for that adequate space?

> I suggest that you could cut the cookie budget if funds really are the =
only reason this wouldn't be done.=20

That is one way to pay for the extra space; it might not be so popular =
in this particular crowd.

--Paul Hoffman=

From dburk@burkov.aha.ru  Fri Aug  3 11:46:13 2012
Return-Path: <dburk@burkov.aha.ru>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33E3321F8DA0 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 11:46:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.273
X-Spam-Level: 
X-Spam-Status: No, score=-0.273 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, HELO_EQ_RU=0.595, HELO_IS_SMALL6=0.556, HOST_EQ_RU=0.875]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id umTJL3UXWAqp for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 11:46:12 -0700 (PDT)
Received: from aha.ru (backend13.aha.ru [62.113.86.202]) by ietfa.amsl.com (Postfix) with ESMTP id 749B521F8DEB for <ietf@ietf.org>; Fri,  3 Aug 2012 11:46:09 -0700 (PDT)
Received: from [91.76.219.195] (account dburk@burkov.aha.ru HELO [192.168.1.5]) by backend13.aha.ru (CommuniGate Pro SMTP 4.3.11) with ESMTPSA id 310680893; Fri, 03 Aug 2012 22:46:08 +0400
Subject: Re: ITU-T Dubai Meeting
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Dmitry Burkov <dburk@burkov.aha.ru>
In-Reply-To: <20120803182500.1F9512344DBF@drugs.dv.isc.org>
Date: Fri, 3 Aug 2012 22:46:07 +0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <1938E5FD-57DE-4172-834A-55CA1FDAF29A@burkov.aha.ru>
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu> <CAMm+Lwg2HgO-=9ED4vbmO+Vf9r6bYPcLDgfyMAyPdEPVgRm4LQ@mail.gmail.com> <FB949BEA-5BDB-401A-8A75-E9A9BDAA72A6@ripe.net> <20120803182500.1F9512344DBF@drugs.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1278)
Cc: Phillip Hallam-Baker <hallam@gmail.com>, Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 18:46:13 -0000

Mark,
I really enjoyed your professional remarks for the years and your deep =
and intrinsic mind,
but it seems that now it is not a time to discuss the issue that ipv4 is =
scarce resource :)


My opinion that IPv6 was done in the worst manner and we should simply =
recognize that we have no other way to satisfy industry needs in such =
short time.=20

Nothing personal - as a lot of my friends spent significant part of =
their life on it.

Dima

On Aug 3, 2012, at 10:25 PM, Mark Andrews wrote:

>=20
> In message <FB949BEA-5BDB-401A-8A75-E9A9BDAA72A6@ripe.net>, Daniel =
Karrenberg w
> rites:
>>=20
>> On 02.08.2012, at 22:41, Phillip Hallam-Baker wrote:
>>=20
>>> ... That depends on whether the registry in question is dealing with =
a
>>> scarce resource or a plentiful one. Having two registries handing =
out
>>> IPv4 addresses at this point would be very very bad. Having more =
than
>>> one place you can get an IPv6 from would not worry me at all. ...
>>=20
>> IPv4 addresses used to be regarded as non-scarce not so long ago.
>=20
> I don't know what planet you have been living on but it was clear
> IPv4 addresses were a scarce resource 2+ decades ago longer than
> some IETF attendees have been alive.  IPv6 was started because they
> were a scarce resource that would run out in the foreseeable future.
>=20
> Mark
> --=20
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From housley@vigilsec.com  Fri Aug  3 11:47:37 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70CE121E805E for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 11:47:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.619
X-Spam-Level: 
X-Spam-Status: No, score=-102.619 tagged_above=-999 required=5 tests=[AWL=-0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AScQc2rkSlmm for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 11:47:37 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id EB8EE21E8044 for <ietf@ietf.org>; Fri,  3 Aug 2012 11:47:36 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id D4011F24040; Fri,  3 Aug 2012 14:47:51 -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 52UcePPOVqN6; Fri,  3 Aug 2012 14:47:28 -0400 (EDT)
Received: from dhcp-55b9.meeting.ietf.org (dhcp-55b9.meeting.ietf.org [130.129.85.185]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id D40A9F2403B; Fri,  3 Aug 2012 14:47:50 -0400 (EDT)
Subject: Re: Progress with Open Internet endowment
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <9051A6BB-B1C4-4A3A-B340-FFC940ACA9C9@vigilsec.com>
Date: Fri, 3 Aug 2012 14:47:33 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <73F4A247-BF55-42E2-814D-CC6DF87F3E0D@vigilsec.com>
References: <019d01cd70e6$fe6dcc50$fb4964f0$@olddog.co.uk> <42A8E91A-9802-4BFA-B245-B67F1B9E1ACE@vigilsec.com> <9051A6BB-B1C4-4A3A-B340-FFC940ACA9C9@vigilsec.com>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: oie@internetsociety.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 18:47:37 -0000

Thank you!   We made it.  We received $26,255 from 90 donors.

Thanks agin,
  Russ

On Aug 3, 2012, at 12:59 PM, Russ Housley wrote:

> As of Friday morning, we are very close to the goal.  As of 9:00 AM =
this morning, we have $24,905 from 80 donors.  Please help if you can.
>=20
> Thanks,
>  Russ
>=20
>=20
> On Aug 2, 2012, at 4:27 PM, Russ Housley wrote:
>=20
>> Our current totals as of noon today, the Open Internet Endowment has =
received $19,245 from 54 donors.  Thanks to all.
>>=20
>> It would be great to reach $25,000 (or more) from 75 donors (or more) =
by lunch tomorrow.  Please help if you can.
>>=20
>> There will be a table at the Bits-N-Bites tonight.  People will be at =
the table to answer any questions you might have.
>>=20
>> Thanks,
>> Russ
>>=20
>=20


From mary.ietf.barnes@gmail.com  Fri Aug  3 12:13:30 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E985121F8E10 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 12:13:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.523
X-Spam-Level: 
X-Spam-Status: No, score=-103.523 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wORfZu8Kn6a7 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 12:13:30 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id EA09021F8E0D for <ietf@ietf.org>; Fri,  3 Aug 2012 12:13:29 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so1918355lbb.31 for <ietf@ietf.org>; Fri, 03 Aug 2012 12:13:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=lWiv+maJv/IcqlFvzwwj/SDL921wlI3nTTHx2IkOvz0=; b=TGik5bCYHl7+JR84oeu6hu3kDvUeocyDcXfw5J6ad6aG/9cyDC6ujjBaXIBpmclvpq wPNflD2F5ai1+05uUvXub05hEmh3zSI/xXksGqtAG092mCeuHXi2feJQxfo9KYjAF32P bCenojuXfce01dNUG7PyT4m21qjAnMh3VzlNlamZIDuuflm4jtU0SBksPARlBNQ1yt2J FxFD847Dq/OsefAVGEmZZOqdM0dT5lPf9SsOuPKvYoBdHEDUc29j7ei+5qZUAMUpW9Be aj2dIPFHxcfeQnUlMeJEq+QOnyWz3SjVQFyU60F+/sq589ED7G+6StpWbVukl1sW4y0j RGbA==
MIME-Version: 1.0
Received: by 10.112.46.135 with SMTP id v7mr1086023lbm.3.1344021208944; Fri, 03 Aug 2012 12:13:28 -0700 (PDT)
Received: by 10.112.85.196 with HTTP; Fri, 3 Aug 2012 12:13:28 -0700 (PDT)
In-Reply-To: <345BE467-B3CA-41EE-9577-6985E3555C8A@vpnc.org>
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org> <CAHBDyN6VaL3fgYe+C+o9d93VZ1bR_EDmrPN7-Sv+7BiJ9+Q9AA@mail.gmail.com> <345BE467-B3CA-41EE-9577-6985E3555C8A@vpnc.org>
Date: Fri, 3 Aug 2012 14:13:28 -0500
Message-ID: <CAHBDyN45juuW65z0ErSxPTB98_J2ZfZ9H9ah4JA6VaVe=uHVmw@mail.gmail.com>
Subject: Re: Meeting "lounges" at IETF meetings
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: multipart/alternative; boundary=bcaec55240bebacfe604c661521a
Cc: ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 19:13:31 -0000

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

On Fri, Aug 3, 2012 at 1:42 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> On Aug 3, 2012, at 11:22 AM, Mary Barnes wrote:
>
> > Instead, I think we should ensure that future venues have adequate space
> for both circulating between meeting rooms and for side conversations.
>
> Just to be clear: you would rather that we pay higher meeting fees in
> exchange for that adequate space?
>
[MB] Yes. [/MB]

>
> > I suggest that you could cut the cookie budget if funds really are the
> only reason this wouldn't be done.
>
> That is one way to pay for the extra space; it might not be so popular in
> this particular crowd.
>
[MB]  Yes, I know it's not at all a popular idea (to reduce cookies), BUT
we have had adequate space at previous meetings for which we paid the same
meeting fee, so it seems possible to get space without increasing meeting
fees (and I thought Vancouver was selected as it was deemed a very
moderately priced venue for meetings).   Note, that we did get additional
space on the 34th floor during the week (which I assumed we paid for).
Also, there was a block of rooms on the 2nd floor that we did not use for
our meetings.  [/MB]



>
> --Paul Hoffman

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

<br><br><div class=3D"gmail_quote">On Fri, Aug 3, 2012 at 1:42 PM, Paul Hof=
fman <span dir=3D"ltr">&lt;<a href=3D"mailto:paul.hoffman@vpnc.org" target=
=3D"_blank">paul.hoffman@vpnc.org</a>&gt;</span> wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">
<div class=3D"im">On Aug 3, 2012, at 11:22 AM, Mary Barnes wrote:<br>
<br>
&gt; Instead, I think we should ensure that future venues have adequate spa=
ce for both circulating between meeting rooms and for side conversations.<b=
r>
<br>
</div>Just to be clear: you would rather that we pay higher meeting fees in=
 exchange for that adequate space?<br></blockquote><div>[MB] Yes. [/MB]=A0<=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">

<div class=3D"im"><br>
&gt; I suggest that you could cut the cookie budget if funds really are the=
 only reason this wouldn&#39;t be done.<br>
<br>
</div>That is one way to pay for the extra space; it might not be so popula=
r in this particular crowd.<br></blockquote><div>[MB] =A0Yes, I know it&#39=
;s not at all a popular idea (to reduce cookies), BUT we have had adequate =
space at previous meetings for which we paid the same meeting fee, so it se=
ems possible to get space without increasing meeting fees (and I thought Va=
ncouver was selected as it was deemed a very moderately priced venue for me=
etings). =A0 Note, that we did get additional space on the 34th floor durin=
g the week (which I assumed we paid for). Also, there was a block of rooms =
on the 2nd floor that we did not use for our meetings. =A0[/MB]</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">
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--Paul Hoffman</font></span></blockquote></div><br>

--bcaec55240bebacfe604c661521a--

From mrex@sap.com  Fri Aug  3 12:29:59 2012
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 E416F21E8043 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 12:29:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.2
X-Spam-Level: 
X-Spam-Status: No, score=-10.2 tagged_above=-999 required=5 tests=[AWL=0.049,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 60tHPV9oHlcT for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 12:29:59 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 36F2921E8042 for <ietf@ietf.org>; Fri,  3 Aug 2012 12:29:33 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id q73JTR1D029117 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 3 Aug 2012 21:29:32 +0200 (MEST)
Subject: Re: Basic ietf process question ...
In-Reply-To: <501AA9DF.6010208@raszuk.net>
To: robert@raszuk.net
Date: Fri, 3 Aug 2012 21:29:27 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20120803192927.14BCC1A117@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
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, 03 Aug 2012 19:30:00 -0000

Robert Raszuk wrote:
> 
> I understand that historically we had/still have SNMP however I have 
> never seen this being mandatory section of any standards track document. 
> Usually SNMP comes 5 years behind (if at all) making it obsolete by design.
> 
> NETCONF is great and very flexible communication channel for 
> provisioning. However it is sufficient to just look at number of ops 
> lists to see that those who tried to use it quickly abandoned their 
> efforts due to complete lack of XML schema from each vendor they happen 
> to use or complete mismatch of vendor to vendor XML interpretation.

There seems to be a network management protocol in active use
for CPE networking gear:

  http://en.wikipedia.org/wiki/TR-069

that is based on SOAP (ie WebService using XML).

-Martin

From randy@psg.com  Fri Aug  3 12:39:39 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27B0911E80DB for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 12:39:39 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PLgmqPad0ZQ5 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 12:39:38 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id CEEF311E80D7 for <ietf@ietf.org>; Fri,  3 Aug 2012 12:39:38 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SxNik-000ACn-Ej for ietf@ietf.org; Fri, 03 Aug 2012 19:39:38 +0000
Date: Fri, 03 Aug 2012 12:39:37 -0700
Message-ID: <m2ipczu5mu.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: ietf list <ietf@ietf.org>
Subject: Re: Meeting "lounges" at IETF meetings
In-Reply-To: <CAHBDyN6VaL3fgYe+C+o9d93VZ1bR_EDmrPN7-Sv+7BiJ9+Q9AA@mail.gmail.com>
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org> <CAHBDyN6VaL3fgYe+C+o9d93VZ1bR_EDmrPN7-Sv+7BiJ9+Q9AA@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-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 19:39:39 -0000

i have no need to micro-manage the secretariat.  and i greatly
appreciate the meeting space the secretariat provided on 34f.
and i think they got the message and will sort it out.

randy

From timo.perala@nsn.com  Fri Aug  3 13:05:27 2012
Return-Path: <timo.perala@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 3D6FB21F8D45 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 13:05:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QUpiEfa7-J1m for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 13:05:26 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 80C6321F899C for <ietf@ietf.org>; Fri,  3 Aug 2012 13:05:25 -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 q73K5Okj028563 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <ietf@ietf.org>; Fri, 3 Aug 2012 22:05:24 +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 q73K5OIt024793 for <ietf@ietf.org>; Fri, 3 Aug 2012 22:05:24 +0200
Received: from FIESEXC016.nsn-intra.net ([10.159.0.24]) by DEMUEXC047.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 3 Aug 2012 22:05:23 +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: Proposed IETF 95 Date Change
Date: Fri, 3 Aug 2012 23:05:21 +0300
Message-ID: <4AF3E8170315EC458F9110B8F9DEDAA801AF275C@FIESEXC016.nsn-intra.net>
In-Reply-To: <FEF37558-FA51-4D8E-A6E9-654716CC3484@magma.ca>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Proposed IETF 95 Date Change
Thread-Index: Ac1xj/voWkczdU64TbyobebL9zrOywAIyhWw
References: <20120802164551.20569.2082.idtracker@ietfa.amsl.com> <FEF37558-FA51-4D8E-A6E9-654716CC3484@magma.ca>
From: "Perala, Timo (NSN - FI/Espoo)" <timo.perala@nsn.com>
To: "IETF Discussion" <ietf@ietf.org>
X-OriginalArrivalTime: 03 Aug 2012 20:05:23.0588 (UTC) FILETIME=[51037C40:01CD71B3]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 760
X-purgate-ID: 151667::1344024324-00002E58-5474EDB9/0-0/0-0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 20:05:27 -0000

+1

Timo

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
ext Philip Matthews
Sent: Thursday, August 02, 2012 8:10 PM

I would personally prefer if the meeting was rescheduled for the week of
April 3 - 8.
- Philip

On 2012-08-02, at 9:45 , IETF Administrative Director wrote:

> The IAOC is seeking community feedback on a proposed date change for
IETF 95
> scheduled for March 2016.
>=20
> Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27 March
is Easter.
>=20
> The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016
and would like=20
> feedback on those dates before making a decision.  Comments
appreciated to ietf@ietf.org=20
> by 6 August 2012.


From mnot@mnot.net  Fri Aug  3 13:06:55 2012
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2EA921F8D52 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 13:06:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.166
X-Spam-Level: 
X-Spam-Status: No, score=-105.166 tagged_above=-999 required=5 tests=[AWL=-2.567, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q-L-F44eUi5d for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 13:06:55 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 84D3E21F8DC6 for <ietf@ietf.org>; Fri,  3 Aug 2012 13:06:53 -0700 (PDT)
Received: from [10.6.130.84] (unknown [50.56.228.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id DF41222E25F; Fri,  3 Aug 2012 16:06:46 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: Meeting "lounges" at IETF meetings
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <m2ipczu5mu.wl%randy@psg.com>
Date: Fri, 3 Aug 2012 15:06:46 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <42D7895B-8949-41FF-AE5B-0C9B813CEE8C@mnot.net>
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org> <CAHBDyN6VaL3fgYe+C+o9d93VZ1bR_EDmrPN7-Sv+7BiJ9+Q9AA@mail.gmail.com> <m2ipczu5mu.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1485)
Cc: ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 20:06:56 -0000

On 03/08/2012, at 2:39 PM, Randy Bush <randy@psg.com> wrote:

> i have no need to micro-manage the secretariat.

+1

seems to happen a lot around here...


--
Mark Nottingham
http://www.mnot.net/





From glenzorn@gmail.com  Fri Aug  3 13:17:15 2012
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C115B21E8034 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 13:17:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.406
X-Spam-Level: 
X-Spam-Status: No, score=-3.406 tagged_above=-999 required=5 tests=[AWL=0.192,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wnl+5VSwMnXc for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 13:17:15 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5076D21F8D69 for <ietf@ietf.org>; Fri,  3 Aug 2012 13:17:15 -0700 (PDT)
Received: by pbbrr4 with SMTP id rr4so65576pbb.31 for <ietf@ietf.org>; Fri, 03 Aug 2012 13:17:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer; bh=UyZl825GXQadURXGnwO3+QcttchYRhuZjReaW9ml7DM=; b=NI0EKG146NYFvCupxsJLZrBuZoPsitq/L18wxisQuI0niyVQUdZ9VMdAS3nNB3+b0f JXF7b1ahJ86H+GI6LDTu5TfQ1xbWDq00EGr+GY7Ngf+tJcdyNkY7M5tA6wzx2s9PNHKn jj8hJpJqnsQpmmZkwIISwRhpqFoFi2fWlA2J0kgRz5q9/jIWpZ/c3CegNQpdwdGQOwei ORjWSN//1+LK7fT06pcGijzQrQUWh4f/8v5E9G78a6F7RWEiZUWK0CEJyaBHKe+bmCB/ Wvr0Hfc3CQMpnZmCIjGFZP11qZukoKSQPmsZvoJLaPgz5gpIQPKwBLM9w8wHk/29cq4/ tGJQ==
Received: by 10.68.232.103 with SMTP id tn7mr188652pbc.86.1344025035145; Fri, 03 Aug 2012 13:17:15 -0700 (PDT)
Received: from [10.0.1.195] (216-19-185-109.dyn.novuscom.net. [216.19.185.109]) by mx.google.com with ESMTPS id pi7sm3525136pbb.56.2012.08.03.13.17.13 (version=SSLv3 cipher=OTHER); Fri, 03 Aug 2012 13:17:14 -0700 (PDT)
Subject: RE: Proposed IETF 95 Date Change
From: Glen Zorn <glenzorn@gmail.com>
To: ietf@ietf.org
In-Reply-To: <4AF3E8170315EC458F9110B8F9DEDAA801AF275C@FIESEXC016.nsn-intra.net>
References: <20120802164551.20569.2082.idtracker@ietfa.amsl.com> <FEF37558-FA51-4D8E-A6E9-654716CC3484@magma.ca> <4AF3E8170315EC458F9110B8F9DEDAA801AF275C@FIESEXC016.nsn-intra.net>
Content-Type: multipart/alternative; boundary="=-Qm8xfucN5ZIAQp6SKSwL"
Organization: Network Zen
Date: Fri, 03 Aug 2012 13:17:12 -0700
Message-ID: <1344025032.14865.6.camel@gwz-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 20:17:15 -0000

--=-Qm8xfucN5ZIAQp6SKSwL
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit



> I would personally prefer if the meeting was rescheduled for the week of
> April 3 - 8.


Strongly opposed.

...

--=-Qm8xfucN5ZIAQp6SKSwL
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
I would personally prefer if the meeting was rescheduled for the week of
April 3 - 8.
</PRE>
</BLOCKQUOTE>
<BR>
Strongly opposed.<BR>
<BR>
...
</BODY>
</HTML>

--=-Qm8xfucN5ZIAQp6SKSwL--


From glenzorn@gmail.com  Fri Aug  3 13:20:31 2012
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C9CD21F8D8E for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 13:20:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.434
X-Spam-Level: 
X-Spam-Status: No, score=-3.434 tagged_above=-999 required=5 tests=[AWL=0.164,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aZYcz2pnG5ge for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 13:20:29 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4166521F8BD6 for <ietf@ietf.org>; Fri,  3 Aug 2012 13:20:19 -0700 (PDT)
Received: by pbbrr4 with SMTP id rr4so69235pbb.31 for <ietf@ietf.org>; Fri, 03 Aug 2012 13:20:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer; bh=bpCCPw1Q8dRT+2paEamnrD9XOb3jV9Jm0c7GQM3y11o=; b=H15UhGZHQDArdZrmxsRGT4d1y+jCUGTfCvlNmjCGecctQHckXaFQSeUIjJxq8ydFOj RuqxKgf0m3IX2EguRWdW63hBehEBWY8/8MXkLTRp/KHvJlsBMrxNb6eJxUs9F2pRW5eh zoKiaUT/j9l6noKcVoyScORQh2jByPqXP4LXdqxxIuuYKfLUz8fDxX8NRWxcW1q96iMv O7pxO+LvSFYpYWlajfPV2ZeZZY+gAdkchxhS9pELyJ8G+6Yt6GyV0d5WP/8nwdTGjQlj QW/xGNkAqy6+cvjoluA8fCc8xesDrIsNxGItBSJMMdLj78lh1oTxVHssm5yVJrKVZW02 KBIw==
Received: by 10.68.138.170 with SMTP id qr10mr205527pbb.120.1344025219000; Fri, 03 Aug 2012 13:20:19 -0700 (PDT)
Received: from [10.0.1.195] (216-19-185-109.dyn.novuscom.net. [216.19.185.109]) by mx.google.com with ESMTPS id pj10sm3531400pbb.46.2012.08.03.13.20.17 (version=SSLv3 cipher=OTHER); Fri, 03 Aug 2012 13:20:18 -0700 (PDT)
Subject: Re: Meeting "lounges" at IETF meetings
From: Glen Zorn <glenzorn@gmail.com>
To: ietf@ietf.org
In-Reply-To: <CAHBDyN45juuW65z0ErSxPTB98_J2ZfZ9H9ah4JA6VaVe=uHVmw@mail.gmail.com>
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org> <CAHBDyN6VaL3fgYe+C+o9d93VZ1bR_EDmrPN7-Sv+7BiJ9+Q9AA@mail.gmail.com> <345BE467-B3CA-41EE-9577-6985E3555C8A@vpnc.org> <CAHBDyN45juuW65z0ErSxPTB98_J2ZfZ9H9ah4JA6VaVe=uHVmw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="=-JLk+fS/s76mxrWMeUI/z"
Organization: Network Zen
Date: Fri, 03 Aug 2012 13:20:17 -0700
Message-ID: <1344025217.14865.9.camel@gwz-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 20:20:31 -0000

--=-JLk+fS/s76mxrWMeUI/z
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

On Fri, 2012-08-03 at 14:13 -0500, Mary Barnes wrote:

> 
> 
> 
> On Fri, Aug 3, 2012 at 1:42 PM, Paul Hoffman <paul.hoffman@vpnc.org>
> wrote:
> 
>         On Aug 3, 2012, at 11:22 AM, Mary Barnes wrote:
>         
>         > Instead, I think we should ensure that future venues have
>         adequate space for both circulating between meeting rooms and
>         for side conversations.
>         
>         
>         
>         Just to be clear: you would rather that we pay higher meeting
>         fees in exchange for that adequate space?
>         
> [MB] Yes. [/MB] 


Just to be even clearer, are you offering to pay those higher fees out
of your own pocket or just to type a larger number into your expense
report?

>         
>         > I suggest that you could cut the cookie budget if funds
>         really are the only reason this wouldn't be done.
>         
>         
>         
>         That is one way to pay for the extra space; it might not be so
>         popular in this particular crowd.
>         
> [MB]  Yes, I know it's not at all a popular idea (to reduce cookies),
> BUT we have had adequate space at previous meetings for which we paid
> the same meeting fee, so it seems possible to get space without
> increasing meeting fees (and I thought Vancouver was selected as it
> was deemed a very moderately priced venue for meetings).   Note, that
> we did get additional space on the 34th floor during the week (which I
> assumed we paid for). Also, there was a block of rooms on the 2nd
> floor that we did not use for our meetings.  [/MB]
> 
> 
>  
>         
>         
>         --Paul Hoffman
> 
> 



--=-JLk+fS/s76mxrWMeUI/z
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
On Fri, 2012-08-03 at 14:13 -0500, Mary Barnes wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
    <BR>
    <BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    On Fri, Aug 3, 2012 at 1:42 PM, Paul Hoffman &lt;<A HREF="mailto:paul.hoffman@vpnc.org">paul.hoffman@vpnc.org</A>&gt; wrote:
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE>
        On Aug 3, 2012, at 11:22 AM, Mary Barnes wrote:<BR>
        <BR>
        &gt; Instead, I think we should ensure that future venues have adequate space for both circulating between meeting rooms and for side conversations.<BR>
        <BR>
        <BR>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE>
        Just to be clear: you would rather that we pay higher meeting fees in exchange for that adequate space?
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    [MB] Yes. [/MB] <BR>
</BLOCKQUOTE>
<BR>
Just to be even clearer, are you offering to pay those higher fees out of your own pocket or just to type a larger number into your expense report?<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE>
        <BR>
        &gt; I suggest that you could cut the cookie budget if funds really are the only reason this wouldn't be done.<BR>
        <BR>
        <BR>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE>
        That is one way to pay for the extra space; it might not be so popular in this particular crowd.
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    [MB] &nbsp;Yes, I know it's not at all a popular idea (to reduce cookies), BUT we have had adequate space at previous meetings for which we paid the same meeting fee, so it seems possible to get space without increasing meeting fees (and I thought Vancouver was selected as it was deemed a very moderately priced venue for meetings). &nbsp; Note, that we did get additional space on the 34th floor during the week (which I assumed we paid for). Also, there was a block of rooms on the 2nd floor that we did not use for our meetings. &nbsp;[/MB]
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BR>
    <BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    &nbsp;
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE>
        <BR>
        <FONT COLOR="#888888">--Paul Hoffman</FONT>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BR>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>

--=-JLk+fS/s76mxrWMeUI/z--


From randy@psg.com  Fri Aug  3 13:27:21 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82FAA21F8D33 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 13:27:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.543
X-Spam-Level: 
X-Spam-Status: No, score=-2.543 tagged_above=-999 required=5 tests=[AWL=0.056,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h06L5J5QG3+a for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 13:27:21 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 2F57F21F8D27 for <ietf@ietf.org>; Fri,  3 Aug 2012 13:27:21 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SxOSu-000AJn-4R; Fri, 03 Aug 2012 20:27:20 +0000
Date: Fri, 03 Aug 2012 13:27:19 -0700
Message-ID: <m2d337u3fc.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: Meeting "lounges" at IETF meetings
In-Reply-To: <42D7895B-8949-41FF-AE5B-0C9B813CEE8C@mnot.net>
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org> <CAHBDyN6VaL3fgYe+C+o9d93VZ1bR_EDmrPN7-Sv+7BiJ9+Q9AA@mail.gmail.com> <m2ipczu5mu.wl%randy@psg.com> <42D7895B-8949-41FF-AE5B-0C9B813CEE8C@mnot.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 list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 20:27:21 -0000

>> i have no need to micro-manage the secretariat.
> seems to happen a lot around here...

symptom of too much free time on hands

randy

From mary.ietf.barnes@gmail.com  Fri Aug  3 13:29:17 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEDE821F8E2B for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 13:29:16 -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.074, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zyehH+lC3AA1 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 13:29:16 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id D83A921F8D27 for <ietf@ietf.org>; Fri,  3 Aug 2012 13:29:15 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so1952449lbb.31 for <ietf@ietf.org>; Fri, 03 Aug 2012 13:29:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=FedJctaskZu5jj104G4ks/POKv4cJrdOPYPguP7N07Y=; b=lyZGP+V/2GtP7KdIrEso0JogHG8UJTVePV7TeHmm1HxOB0RRsmDctvcBfO8ST8+7ut ojhXxFO3CxrUM7WL21D+R7A+OSCGh58cCF+Fhz28jHN0q9ty5zWdBWmvhNd1Uf+WwXSE xPZNJwkdTaKb28Hu5xmBCmeAjqPiqvj/m8Oy0Zs4bchFL8QwjlLhsxcMHlHsUdLxMgU4 S9/al+rJcEMRcTPjsD5OTXRnv02GUQCqPhfAQU7jv+qKPz5VR2BCsQVPlsrM7GZCEva0 iNhebR50TXg3bx+9pYleRkqadXR92vNWLVXfZzDqUxUa2h78zdcuREIg2fGZtPUzc2Nl EKtQ==
MIME-Version: 1.0
Received: by 10.152.104.44 with SMTP id gb12mr2698662lab.29.1344025754889; Fri, 03 Aug 2012 13:29:14 -0700 (PDT)
Received: by 10.112.85.196 with HTTP; Fri, 3 Aug 2012 13:29:14 -0700 (PDT)
In-Reply-To: <1344025217.14865.9.camel@gwz-laptop>
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org> <CAHBDyN6VaL3fgYe+C+o9d93VZ1bR_EDmrPN7-Sv+7BiJ9+Q9AA@mail.gmail.com> <345BE467-B3CA-41EE-9577-6985E3555C8A@vpnc.org> <CAHBDyN45juuW65z0ErSxPTB98_J2ZfZ9H9ah4JA6VaVe=uHVmw@mail.gmail.com> <1344025217.14865.9.camel@gwz-laptop>
Date: Fri, 3 Aug 2012 15:29:14 -0500
Message-ID: <CAHBDyN56SOLq2QUm5oaZeSCR9KXfgyj7wO2e2LTJP1z+1t6n8A@mail.gmail.com>
Subject: Re: Meeting "lounges" at IETF meetings
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Glen Zorn <glenzorn@gmail.com>
Content-Type: multipart/alternative; boundary=f46d04088ef5b06c4d04c66261fa
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 20:29:17 -0000

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

Either one - I'll direct a donation to the Open Internet Endowment for
meeting rooms.  Or, we can increase the fees for legal requests as others
have been suggesting.

If you read the thread, I was responding to the takeover of the terminal
room as a meeting place.  I was trying to be constructive with my
suggestions.  You can interpret them however you want.

Mary.

On Fri, Aug 3, 2012 at 3:20 PM, Glen Zorn <glenzorn@gmail.com> wrote:

> **
> On Fri, 2012-08-03 at 14:13 -0500, Mary Barnes wrote:
>
>
>
>  On Fri, Aug 3, 2012 at 1:42 PM, Paul Hoffman <paul.hoffman@vpnc.org>
> wrote:
>
>  On Aug 3, 2012, at 11:22 AM, Mary Barnes wrote:
>
> > Instead, I think we should ensure that future venues have adequate space
> for both circulating between meeting rooms and for side conversations.
>
>
>   Just to be clear: you would rather that we pay higher meeting fees in
> exchange for that adequate space?
>
>  [MB] Yes. [/MB]
>
>
> Just to be even clearer, are you offering to pay those higher fees out of
> your own pocket or just to type a larger number into your expense report?
>
>
>
> > I suggest that you could cut the cookie budget if funds really are the
> only reason this wouldn't be done.
>
>
>   That is one way to pay for the extra space; it might not be so popular
> in this particular crowd.
>
>  [MB]  Yes, I know it's not at all a popular idea (to reduce cookies),
> BUT we have had adequate space at previous meetings for which we paid the
> same meeting fee, so it seems possible to get space without increasing
> meeting fees (and I thought Vancouver was selected as it was deemed a very
> moderately priced venue for meetings).   Note, that we did get additional
> space on the 34th floor during the week (which I assumed we paid for).
> Also, there was a block of rooms on the 2nd floor that we did not use for
> our meetings.  [/MB]
>
>
>
>
>
>
> --Paul Hoffman
>
>
>
>

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

Either one - I&#39;ll direct a donation to the Open Internet Endowment for =
meeting rooms. =A0Or, we can increase the fees for legal requests as others=
 have been suggesting.=A0<div><br></div><div>If you read the thread, I was =
responding to the takeover of the terminal room as a meeting place. =A0I wa=
s trying to be constructive with my suggestions. =A0You can interpret them =
however you want.=A0</div>
<div><div><br></div><div>Mary.=A0<br><br><div class=3D"gmail_quote">On Fri,=
 Aug 3, 2012 at 3:20 PM, Glen Zorn <span dir=3D"ltr">&lt;<a href=3D"mailto:=
glenzorn@gmail.com" target=3D"_blank">glenzorn@gmail.com</a>&gt;</span> wro=
te:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><u></u>


 =20
 =20

<div><div class=3D"im">
On Fri, 2012-08-03 at 14:13 -0500, Mary Barnes wrote:<br>
<blockquote type=3D"CITE">
    <br>
    <br>
</blockquote>
<blockquote type=3D"CITE">
    On Fri, Aug 3, 2012 at 1:42 PM, Paul Hoffman &lt;<a href=3D"mailto:paul=
.hoffman@vpnc.org" target=3D"_blank">paul.hoffman@vpnc.org</a>&gt; wrote:
</blockquote>
<blockquote type=3D"CITE">
    <blockquote>
        On Aug 3, 2012, at 11:22 AM, Mary Barnes wrote:<br>
        <br>
        &gt; Instead, I think we should ensure that future venues have adeq=
uate space for both circulating between meeting rooms and for side conversa=
tions.<br>
        <br>
        <br>
    </blockquote>
</blockquote>
<blockquote type=3D"CITE">
    <blockquote>
        Just to be clear: you would rather that we pay higher meeting fees =
in exchange for that adequate space?
    </blockquote>
</blockquote>
<blockquote type=3D"CITE">
    [MB] Yes. [/MB] <br>
</blockquote>
<br></div>
Just to be even clearer, are you offering to pay those higher fees out of y=
our own pocket or just to type a larger number into your expense report?<di=
v class=3D"im"><br>
<br>
<blockquote type=3D"CITE">
    <blockquote>
        <br>
        &gt; I suggest that you could cut the cookie budget if funds really=
 are the only reason this wouldn&#39;t be done.<br>
        <br>
        <br>
    </blockquote>
</blockquote>
<blockquote type=3D"CITE">
    <blockquote>
        That is one way to pay for the extra space; it might not be so popu=
lar in this particular crowd.
    </blockquote>
</blockquote>
<blockquote type=3D"CITE">
    [MB] =A0Yes, I know it&#39;s not at all a popular idea (to reduce cooki=
es), BUT we have had adequate space at previous meetings for which we paid =
the same meeting fee, so it seems possible to get space without increasing =
meeting fees (and I thought Vancouver was selected as it was deemed a very =
moderately priced venue for meetings). =A0 Note, that we did get additional=
 space on the 34th floor during the week (which I assumed we paid for). Als=
o, there was a block of rooms on the 2nd floor that we did not use for our =
meetings. =A0[/MB]
</blockquote>
<blockquote type=3D"CITE">
    <br>
    <br>
</blockquote>
<blockquote type=3D"CITE">
    =A0
</blockquote>
<blockquote type=3D"CITE">
    <blockquote>
        <br>
        <font color=3D"#888888">--Paul Hoffman</font>
    </blockquote>
</blockquote>
<blockquote type=3D"CITE">
    <br>
</blockquote>
<br>
</div></div>

</blockquote></div><br></div></div>

--f46d04088ef5b06c4d04c66261fa--

From mary.ietf.barnes@gmail.com  Fri Aug  3 13:30:36 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1144821F8DA2 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 13:30:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.525
X-Spam-Level: 
X-Spam-Status: No, score=-103.525 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1H7G322akeKC for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 13:30:35 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 29B8321F8D9B for <ietf@ietf.org>; Fri,  3 Aug 2012 13:30:34 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so1952975lbb.31 for <ietf@ietf.org>; Fri, 03 Aug 2012 13:30:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JxPliJX0UBvfRI1T4qncpr0mCnq/ccjPNy5Ou/fMT1o=; b=XXlVfYkaW5dzokdzX6mwccU2ZEj6RrxeNkzxDAr5Pz2Gkz/mF4Nx6cTEh/3WBx7wke 0Brvdi+ZSIKCXerLKr051LPltxSbZKv1390NUBDHrTLwdQXN72MwKpEVQsdfkBsYW4vb B6c0hMMCNPmiEjYHdm7OS9w1uwukq957dZrgdcs6087YCag9IEPRkDOY9t7UfJLR2kpc tjkuGk/yXxPV+oyciNH6hJHwpH916Gv4XMFMwr5YWmz9dtSgp7EiqsQTA47ziZ/EuKmQ Ub9T5hbTdBNQum4Mqx80d5ZO6LJZ7v4QLY8cCp9wv7zmLytUbinZBPTg8duY9xd1puSX xwvA==
MIME-Version: 1.0
Received: by 10.112.37.67 with SMTP id w3mr1095939lbj.93.1344025834053; Fri, 03 Aug 2012 13:30:34 -0700 (PDT)
Received: by 10.112.85.196 with HTTP; Fri, 3 Aug 2012 13:30:34 -0700 (PDT)
In-Reply-To: <m2d337u3fc.wl%randy@psg.com>
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org> <CAHBDyN6VaL3fgYe+C+o9d93VZ1bR_EDmrPN7-Sv+7BiJ9+Q9AA@mail.gmail.com> <m2ipczu5mu.wl%randy@psg.com> <42D7895B-8949-41FF-AE5B-0C9B813CEE8C@mnot.net> <m2d337u3fc.wl%randy@psg.com>
Date: Fri, 3 Aug 2012 15:30:34 -0500
Message-ID: <CAHBDyN49-31-O77Dmpun30A6SmnJKYoOZnEwdWOkCP255eQ3Wg@mail.gmail.com>
Subject: Re: Meeting "lounges" at IETF meetings
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Randy Bush <randy@psg.com>
Content-Type: multipart/alternative; boundary=e0cb4efe2c8e68626b04c6626654
Cc: Mark Nottingham <mnot@mnot.net>, ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 20:30:36 -0000

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

Yeah, I have tons of free time at these meetings.    And, my response was
absolutely an attempt to micro-manage rather than provide suggestions on
how the situation could be better handled (as I don't think taking over the
terminal room is a good idea).

Mary.

On Fri, Aug 3, 2012 at 3:27 PM, Randy Bush <randy@psg.com> wrote:

> >> i have no need to micro-manage the secretariat.
> > seems to happen a lot around here...
>
> symptom of too much free time on hands
>
> randy
>

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

Yeah, I have tons of free time at these meetings. =A0 =A0And, my response w=
as absolutely an attempt to micro-manage rather than provide suggestions on=
 how the situation could be better handled (as I don&#39;t think taking ove=
r the terminal room is a good idea).<div>
<br></div><div>Mary.=A0<br><br><div class=3D"gmail_quote">On Fri, Aug 3, 20=
12 at 3:27 PM, Randy Bush <span dir=3D"ltr">&lt;<a href=3D"mailto:randy@psg=
.com" target=3D"_blank">randy@psg.com</a>&gt;</span> wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">
<div class=3D"im">&gt;&gt; i have no need to micro-manage the secretariat.<=
br>
</div><div class=3D"im">&gt; seems to happen a lot around here...<br>
<br>
</div>symptom of too much free time on hands<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
randy<br>
</font></span></blockquote></div><br></div>

--e0cb4efe2c8e68626b04c6626654--

From sm@resistor.net  Fri Aug  3 13:39:11 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B84EA21E804E for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 13:39:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.42
X-Spam-Level: 
X-Spam-Status: No, score=-102.42 tagged_above=-999 required=5 tests=[AWL=-0.121, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g63d7mq6RKk4 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 13:39:07 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A480721F8E05 for <ietf@ietf.org>; Fri,  3 Aug 2012 13:39:07 -0700 (PDT)
Received: from sm-THINK.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q73Kcmv3010640; Fri, 3 Aug 2012 13:38:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1344026335; bh=EWU4TrWGBFWqbGtXq/FA7D/ZTBA1cu5dQbxTF8/KK58=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=0sE1SngQqRgZ0ty9U81mfzXMjXwJjlbHEJxzyAKmSml7DkIb/pdpgGp+DLGaaMwX3 AkCXYHXVyhSQ7rkxQfssxy81DnAmiux1WkwMLLDIvgYjtzGt8GPomp53viVzeZoq8P ZwX0KtKEaeI+azOSKH9vHv4pSAz8mDS/XEYaRauA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1344026335; i=@resistor.net; bh=EWU4TrWGBFWqbGtXq/FA7D/ZTBA1cu5dQbxTF8/KK58=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=JeNZVFt1N/37qXfLSi6BRInR3lVImXtE3ZEW/ysg4pdIUuxbFuF6DUclvaeYHivIY YymVqjZjbuHY09lonsVE53rLRhjgkbKnxM7Va82A0VK7Lu9f7a4w//o24vZETHb/cw u5tB5oR9SpM0Cb355+INApIYdqNYYCPOn1JHxU/E=
Message-Id: <6.2.5.6.2.20120803091255.09587b30@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 03 Aug 2012 13:27:01 -0700
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Patrik  =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@frobbit.se>
From: SM <sm@resistor.net>
Subject: Re: ITU-T Dubai Meeting
In-Reply-To: <501B7B43.70202@gmail.com>
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu> <B6033EB2-3B90-4524-A123-38852C5E2698@virtualized.org> <4401D68C-F9BB-4777-845A-A7011C50F1EA@cs.columbia.edu> <501B7B43.70202@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 20:39:11 -0000

At 12:18 AM 8/3/2012, Brian E Carpenter wrote:
>Exactly. It is intended to defeat the Internet's historical growth model
>of independence from national administrations and monopolies, by imposing
>a geographical addressing scheme. Since the Internet actually works with
>a topological addressing scheme, the effect is to force the topology
>to be congruent with the geography. If you want central control, that's

Yes.  However that message is not reaching the=20
people who are part of national administrations.

At 12:25 AM 8/3/2012, Patrik F=E4ltstr=F6m wrote:
>The key here is control.

SAAG [1] might consider working on that Worst=20
Common Practice document to explain to countries=20
how they should "cut off" the Internet (=20
http://www.ietf.org/proceedings/84/slides/slides-84-irtfopen-1.pdf ). :-)

If I am not mistaken the control points are=20
already in place in one or more countries.  The=20
key may be control.  It may also be a desire to=20
address a problem which people consider as important.

Regards,
-sm

1. There is generally one of more interesting=20
presentations at SAAG.  I don't know how the Security ADs make that happen.=
=20


From rbonica@juniper.net  Fri Aug  3 13:47:47 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 956D321F8E4C for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 13:47:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.573
X-Spam-Level: 
X-Spam-Status: No, score=-106.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n4tQ33vLWPXt for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 13:47:47 -0700 (PDT)
Received: from exprod7og117.obsmtp.com (exprod7og117.obsmtp.com [64.18.2.6]) by ietfa.amsl.com (Postfix) with ESMTP id CF2FF21F8E49 for <ietf@ietf.org>; Fri,  3 Aug 2012 13:47:43 -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 DSNKUBw47+nVHael0wHDfPeyU3xDTyIxFuL6@postini.com; Fri, 03 Aug 2012 13:47:45 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 3 Aug 2012 13:46:18 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Fri, 3 Aug 2012 16:44:24 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "Perala, Timo (NSN - FI/Espoo)" <timo.perala@nsn.com>, IETF Discussion <ietf@ietf.org>
Date: Fri, 3 Aug 2012 16:44:22 -0400
Subject: RE: Proposed IETF 95 Date Change
Thread-Topic: Proposed IETF 95 Date Change
Thread-Index: Ac1xj/voWkczdU64TbyobebL9zrOywAIyhWwAAFmafA=
Message-ID: <13205C286662DE4387D9AF3AC30EF456D771652E13@EMBX01-WF.jnpr.net>
References: <20120802164551.20569.2082.idtracker@ietfa.amsl.com> <FEF37558-FA51-4D8E-A6E9-654716CC3484@magma.ca> <4AF3E8170315EC458F9110B8F9DEDAA801AF275C@FIESEXC016.nsn-intra.net>
In-Reply-To: <4AF3E8170315EC458F9110B8F9DEDAA801AF275C@FIESEXC016.nsn-intra.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, 03 Aug 2012 20:47:47 -0000

+1

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Perala, Timo (NSN - FI/Espoo)
> Sent: Friday, August 03, 2012 4:05 PM
> To: IETF Discussion
> Subject: RE: Proposed IETF 95 Date Change
>=20
> +1
>=20
> Timo
>=20
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> ext Philip Matthews
> Sent: Thursday, August 02, 2012 8:10 PM
>=20
> I would personally prefer if the meeting was rescheduled for the week
> of April 3 - 8.
> - Philip
>=20
> On 2012-08-02, at 9:45 , IETF Administrative Director wrote:
>=20
> > The IAOC is seeking community feedback on a proposed date change for
> IETF 95
> > scheduled for March 2016.
> >
> > Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27
> March
> is Easter.
> >
> > The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016
> and would like
> > feedback on those dates before making a decision.  Comments
> appreciated to ietf@ietf.org
> > by 6 August 2012.


From tnadeau@lucidvision.com  Fri Aug  3 14:14:43 2012
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 6962711E80C5 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 14:14:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level: 
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hpv0we76FSwL for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 14:14:43 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id D87B711E8091 for <ietf@ietf.org>; Fri,  3 Aug 2012 14:14:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by lucidvision.com (Postfix) with ESMTP id 2A5DB2210E7A; Fri,  3 Aug 2012 17:14:42 -0400 (EDT)
X-Virus-Scanned: amavisd-new at www.lucidvision.com
Received: from lucidvision.com ([127.0.0.1]) by localhost (static-72-71-250-34.cncdnh.fios.verizon.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sN7nziBknYR0; Fri,  3 Aug 2012 17:14:42 -0400 (EDT)
Received: from [10.203.110.177] (mobile-166-147-102-020.mycingular.net [166.147.102.20]) by lucidvision.com (Postfix) with ESMTP id CF1442210E77; Fri,  3 Aug 2012 17:14:41 -0400 (EDT)
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org> <CAHBDyN6VaL3fgYe+C+o9d93VZ1bR_EDmrPN7-Sv+7BiJ9+Q9AA@mail.gmail.com> <m2ipczu5mu.wl%randy@psg.com> <42D7895B-8949-41FF-AE5B-0C9B813CEE8C@mnot.net> <m2d337u3fc.wl%randy@psg.com>
In-Reply-To: <m2d337u3fc.wl%randy@psg.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <20104150-FCF4-4914-8656-72FFC9BA94AA@lucidvision.com>
X-Mailer: iPhone Mail (9B206)
From: Thomas Nadeau <tnadeau@lucidvision.com>
Subject: Re: Meeting "lounges" at IETF meetings
Date: Fri, 3 Aug 2012 16:14:29 -0500
To: Randy Bush <randy@psg.com>
Cc: Mark Nottingham <mnot@mnot.net>, ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 21:14:43 -0000

I agree with randy. I've never had an issue finding a place to huddle/meet w=
hen necessary at an ietf meeting venue. between the hallways, bar, etc I'm n=
ot sure what the fuss is all about.

Tom=20



On Aug 3, 2012, at 3:27 PM, Randy Bush <randy@psg.com> wrote:

>>> i have no need to micro-manage the secretariat.
>> seems to happen a lot around here...
>=20
> symptom of too much free time on hands
>=20
> randy
>=20

From mary.ietf.barnes@gmail.com  Fri Aug  3 14:56:47 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4E9C21F8DD6 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 14:56:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.525
X-Spam-Level: 
X-Spam-Status: No, score=-103.525 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FGh9XT3zwCDZ for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 14:56:47 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9E1A721F8DDF for <ietf@ietf.org>; Fri,  3 Aug 2012 14:56:46 -0700 (PDT)
Received: by lahm15 with SMTP id m15so663297lah.31 for <ietf@ietf.org>; Fri, 03 Aug 2012 14:56:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8IMAKPn/KosUFn6T520takszSat0f3j237QJ1aYb+ko=; b=brjTgleA0+6I5rG05aO36ayhuHtfPvFqI5JQ+7M802FA5dPFPRJuHYZ3gFv+Ihvm0b 3XRuywXaolu/2cPYFzfnr5PlWcvI2JnBNvgfRKLEig2rBq7RlK238a2OGTmb7E5D6Aqo rHRAOJx9Y/TS1rxQTyoxElpjRp5u9jqocltI7i3E6Gy7+Ma2HpiBoRDdhWVuNKyUTInr B60ZCI9VqpVc5gR9nbf35Be6ivXjmyWKwcX8CQR4LSKBaiohI/jWjB25yArdIMfItuqf 157fItA0CNAk2ykkqWdZiIfl9DHH8t8omLw21WWB7bzbGO83Fk7nv0BryGM5b1h43/qA HobA==
MIME-Version: 1.0
Received: by 10.112.40.33 with SMTP id u1mr1245172lbk.28.1344031005520; Fri, 03 Aug 2012 14:56:45 -0700 (PDT)
Received: by 10.112.85.196 with HTTP; Fri, 3 Aug 2012 14:56:45 -0700 (PDT)
In-Reply-To: <20104150-FCF4-4914-8656-72FFC9BA94AA@lucidvision.com>
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org> <CAHBDyN6VaL3fgYe+C+o9d93VZ1bR_EDmrPN7-Sv+7BiJ9+Q9AA@mail.gmail.com> <m2ipczu5mu.wl%randy@psg.com> <42D7895B-8949-41FF-AE5B-0C9B813CEE8C@mnot.net> <m2d337u3fc.wl%randy@psg.com> <20104150-FCF4-4914-8656-72FFC9BA94AA@lucidvision.com>
Date: Fri, 3 Aug 2012 16:56:45 -0500
Message-ID: <CAHBDyN63_r2TEf7h81r9NYnQbdriC9Ztr-cT7vapO0uyRYB5_w@mail.gmail.com>
Subject: Re: Meeting "lounges" at IETF meetings
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Thomas Nadeau <tnadeau@lucidvision.com>
Content-Type: multipart/alternative; boundary=e0cb4efe3060a6b46d04c6639ab2
Cc: Mark Nottingham <mnot@mnot.net>, ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 21:56:48 -0000

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

The issue that I experienced (and why I'm fussing)  is that if you were
attending many sessions in the Regency rooms (and moving rooms between
sessions), it was extremely difficult to weave your way through the
corridor as many people were having their discussion directly in the middle
of the corridor.  There just was not room in that corridor for side
conversations.  The situation was made worse as that corridor was where
they served the refreshments.   And trying to ask people politely to move
generally had no impact in my experience as people were too engaged in
their conversations.

Mary.

On Fri, Aug 3, 2012 at 4:14 PM, Thomas Nadeau <tnadeau@lucidvision.com>wrote:

> I agree with randy. I've never had an issue finding a place to huddle/meet
> when necessary at an ietf meeting venue. between the hallways, bar, etc I'm
> not sure what the fuss is all about.
>
> Tom
>
>
>
> On Aug 3, 2012, at 3:27 PM, Randy Bush <randy@psg.com> wrote:
>
> >>> i have no need to micro-manage the secretariat.
> >> seems to happen a lot around here...
> >
> > symptom of too much free time on hands
> >
> > randy
> >
>

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

The issue that I experienced (and why I&#39;m fussing) =A0is that if you we=
re attending many sessions in the Regency rooms (and moving rooms between s=
essions), it was extremely difficult to weave your way through the corridor=
 as many people were having their discussion directly in the middle of the =
corridor. =A0There just was not room in that corridor for side conversation=
s. =A0The situation was made worse as that corridor was where they served t=
he refreshments. =A0 And trying to ask people politely to move generally ha=
d no impact in my experience as people were too engaged in their conversati=
ons. =A0<div>
<br></div><div>Mary.=A0<br><br><div class=3D"gmail_quote">On Fri, Aug 3, 20=
12 at 4:14 PM, Thomas Nadeau <span dir=3D"ltr">&lt;<a href=3D"mailto:tnadea=
u@lucidvision.com" target=3D"_blank">tnadeau@lucidvision.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">I agree with randy. I&#39;ve never had an is=
sue finding a place to huddle/meet when necessary at an ietf meeting venue.=
 between the hallways, bar, etc I&#39;m not sure what the fuss is all about=
.<br>

<br>
Tom<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
<br>
On Aug 3, 2012, at 3:27 PM, Randy Bush &lt;<a href=3D"mailto:randy@psg.com"=
>randy@psg.com</a>&gt; wrote:<br>
<br>
&gt;&gt;&gt; i have no need to micro-manage the secretariat.<br>
&gt;&gt; seems to happen a lot around here...<br>
&gt;<br>
&gt; symptom of too much free time on hands<br>
&gt;<br>
&gt; randy<br>
&gt;<br>
</div></div></blockquote></div><br></div>

--e0cb4efe3060a6b46d04c6639ab2--

From amorris@amsl.com  Fri Aug  3 15:08:36 2012
Return-Path: <amorris@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B1A511E808A for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 15:08:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ebrqfXv8d7xg for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 15:08:35 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id A62A021F8D80 for <ietf@ietf.org>; Fri,  3 Aug 2012 15:08:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 1071F12BB70; Fri,  3 Aug 2012 15:08:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NAEG4T0OLJFa; Fri,  3 Aug 2012 15:08:10 -0700 (PDT)
Received: from dhcp-624e.meeting.ietf.org (dhcp-624e.meeting.ietf.org [130.129.98.78]) by c8a.amsl.com (Postfix) with ESMTPSA id A764212BB6E; Fri,  3 Aug 2012 15:08:10 -0700 (PDT)
Subject: Re: Meeting "lounges" at IETF meetings
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-3-652269238
From: Alexa Morris <amorris@amsl.com>
In-Reply-To: <CAHBDyN63_r2TEf7h81r9NYnQbdriC9Ztr-cT7vapO0uyRYB5_w@mail.gmail.com>
Date: Fri, 3 Aug 2012 15:08:09 -0700
Message-Id: <252B8F1B-C899-4834-8BE9-E25FC8218469@amsl.com>
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org> <CAHBDyN6VaL3fgYe+C+o9d93VZ1bR_EDmrPN7-Sv+7BiJ9+Q9AA@mail.gmail.com> <m2ipczu5mu.wl%randy@psg.com> <42D7895B-8949-41FF-AE5B-0C9B813CEE8C@mnot.net> <m2d337u3fc.wl%randy@psg.com> <20104150-FCF4-4914-8656-72FFC9BA94AA@lucidvision.com> <CAHBDyN63_r2TEf7h81r9NYnQbdriC9Ztr-cT7vapO0uyRYB5_w@mail.gmail.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Mark Nottingham <mnot@mnot.net>, ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 22:08:36 -0000

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

Yes, the hallway congestion was a real issue at this meeting, and we are =
already working on ways to make sure that we manage it differently when =
we return next year. The refreshments will not be served in those same =
corridors, as a start.=20

We are also working to address the desire for additional lounge areas. =
It is not always possible, given that our space varies considerably from =
meeting to meeting, but we are hoping to make it a more permanent =
fixture moving forward.

Alexa


On Aug 3, 2012, at 2:56 PM, Mary Barnes wrote:

> The issue that I experienced (and why I'm fussing)  is that if you =
were attending many sessions in the Regency rooms (and moving rooms =
between sessions), it was extremely difficult to weave your way through =
the corridor as many people were having their discussion directly in the =
middle of the corridor.  There just was not room in that corridor for =
side conversations.  The situation was made worse as that corridor was =
where they served the refreshments.   And trying to ask people politely =
to move generally had no impact in my experience as people were too =
engaged in their conversations. =20
>=20
> Mary.=20
>=20
> On Fri, Aug 3, 2012 at 4:14 PM, Thomas Nadeau =
<tnadeau@lucidvision.com> wrote:
> I agree with randy. I've never had an issue finding a place to =
huddle/meet when necessary at an ietf meeting venue. between the =
hallways, bar, etc I'm not sure what the fuss is all about.
>=20
> Tom
>=20
>=20
>=20
> On Aug 3, 2012, at 3:27 PM, Randy Bush <randy@psg.com> wrote:
>=20
> >>> i have no need to micro-manage the secretariat.
> >> seems to happen a lot around here...
> >
> > symptom of too much free time on hands
> >
> > randy
> >
>=20

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

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


--Apple-Mail-3-652269238
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; ">Yes, =
the hallway congestion was a real issue at this meeting, and we are =
already working on ways to make sure that we manage it differently when =
we return next year. The refreshments will not be served in those same =
corridors, as a start.&nbsp;<div><br></div><div>We are also working to =
address the desire for additional lounge areas. It is not always =
possible, given that our space varies considerably from meeting to =
meeting, but we are hoping to make it a more permanent fixture moving =
forward.</div><div><br></div><div>Alexa</div><div><br><div><br><div><div>O=
n Aug 3, 2012, at 2:56 PM, Mary Barnes wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite">The issue =
that I experienced (and why I'm fussing) &nbsp;is that if you were =
attending many sessions in the Regency rooms (and moving rooms between =
sessions), it was extremely difficult to weave your way through the =
corridor as many people were having their discussion directly in the =
middle of the corridor. &nbsp;There just was not room in that corridor =
for side conversations. &nbsp;The situation was made worse as that =
corridor was where they served the refreshments. &nbsp; And trying to =
ask people politely to move generally had no impact in my experience as =
people were too engaged in their conversations. &nbsp;<div>
<br></div><div>Mary.&nbsp;<br><br><div class=3D"gmail_quote">On Fri, Aug =
3, 2012 at 4:14 PM, Thomas Nadeau <span dir=3D"ltr">&lt;<a =
href=3D"mailto:tnadeau@lucidvision.com" =
target=3D"_blank">tnadeau@lucidvision.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">I agree with randy. =
I've never had an issue finding a place to huddle/meet when necessary at =
an ietf meeting venue. between the hallways, bar, etc I'm not sure what =
the fuss is all about.<br>

<br>
Tom<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
<br>
On Aug 3, 2012, at 3:27 PM, Randy Bush &lt;<a =
href=3D"mailto:randy@psg.com">randy@psg.com</a>&gt; wrote:<br>
<br>
&gt;&gt;&gt; i have no need to micro-manage the secretariat.<br>
&gt;&gt; seems to happen a lot around here...<br>
&gt;<br>
&gt; symptom of too much free time on hands<br>
&gt;<br>
&gt; randy<br>
&gt;<br>
</div></div></blockquote></div><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: -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>----------<br>Alexa Morris / Executive Director / IETF<br>48377 =
Fremont Blvd., Suite 117, Fremont, CA &nbsp;94538<br>Phone: =
+1.510.492.4089 / Fax: +1.510.492.4001<br>Email:&nbsp;<a =
href=3D"mailto:amorris@amsl.com">amorris@amsl.com</a><br><br>Managed by =
Association Management Solutions (AMS)<br>Forum Management, Meeting and =
Event Planning<br><a =
href=3D"http://www.amsl.com/">www.amsl.com</a>&nbsp;&lt;<a =
href=3D"http://www.amsl.com/">http://www.amsl.com/</a>&gt;</div></span>
</div>
<br></div></div></body></html>=

--Apple-Mail-3-652269238--

From ole@cisco.com  Fri Aug  3 15:10:34 2012
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 769AE21F8DA2 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 15:10:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.556
X-Spam-Level: 
X-Spam-Status: No, score=-110.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bj-LEvE+uAAS for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 15:10:33 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id C198021F8D96 for <ietf@ietf.org>; Fri,  3 Aug 2012 15:10:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=1823; q=dns/txt; s=iport; t=1344031824; x=1345241424; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=2MRCPDU+csb31VqMOig4mCUZ35RsrEAO55vm6nLUYmM=; b=YbM7DAoTS4O1XVReLNn3Hi4lyTWSqRkwX6KRDz2ysdPhzOIUvXehA23L V7AibNSckCrJvqwdqYqs5ocZ3iThSHsQEUDXOWIQm0IlMJ0pkAZPpUAjx Hal3qeMb6bCAFAgZQ+/3WiJY0L8ZwY87pzn4ZXubLVCB2C42DGoMZopdB U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EABRMHFCrRDoG/2dsb2JhbABBA7k4gQeCIAEBAQMBEgECJT8FCwsYLlcGEyKHZQWcXoNIEJxBi0gag0mDIQOITZJYhTKDGoEEYoJ/gT8
X-IronPort-AV: E=Sophos;i="4.77,709,1336348800"; d="scan'208";a="50910780"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 03 Aug 2012 22:10:10 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q73MA9ta025590; Fri, 3 Aug 2012 22:10:09 GMT
Date: Fri, 3 Aug 2012 15:10:09 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: Meeting "lounges" at IETF meetings
In-Reply-To: <CAHBDyN63_r2TEf7h81r9NYnQbdriC9Ztr-cT7vapO0uyRYB5_w@mail.gmail.com>
Message-ID: <alpine.OSX.2.01.1208031505550.16675@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org> <CAHBDyN6VaL3fgYe+C+o9d93VZ1bR_EDmrPN7-Sv+7BiJ9+Q9AA@mail.gmail.com> <m2ipczu5mu.wl%randy@psg.com> <42D7895B-8949-41FF-AE5B-0C9B813CEE8C@mnot.net> <m2d337u3fc.wl%randy@psg.com> <20104150-FCF4-4914-8656-72FFC9BA94AA@lucidvision.com> <CAHBDyN63_r2TEf7h81r9NYnQbdriC9Ztr-cT7vapO0uyRYB5_w@mail.gmail.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: Mark Nottingham <mnot@mnot.net>, ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 22:10:34 -0000

The narrowness of the corridoors, placement of food/drink and all that 
was discussed in our wrap-up meeting this morning, and indeed the 
issues you have raised were indentified as areas for improvement. 
Since we are coming back to THIS hotel, there are certainly things 
that can be done better, and will be done better, next time. 

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Fri, 3 Aug 2012, Mary Barnes wrote:

> The issue that I experienced (and why I'm fussing)  is that if you were
> attending many sessions in the Regency rooms (and moving rooms between
> sessions), it was extremely difficult to weave your way through the
> corridor as many people were having their discussion directly in the middle
> of the corridor.  There just was not room in that corridor for side
> conversations.  The situation was made worse as that corridor was where
> they served the refreshments.   And trying to ask people politely to move
> generally had no impact in my experience as people were too engaged in
> their conversations.
> 
> Mary.
> 
> On Fri, Aug 3, 2012 at 4:14 PM, Thomas Nadeau <tnadeau@lucidvision.com>wrote:
> 
> > I agree with randy. I've never had an issue finding a place to huddle/meet
> > when necessary at an ietf meeting venue. between the hallways, bar, etc I'm
> > not sure what the fuss is all about.
> >
> > Tom
> >
> >
> >
> > On Aug 3, 2012, at 3:27 PM, Randy Bush <randy@psg.com> wrote:
> >
> > >>> i have no need to micro-manage the secretariat.
> > >> seems to happen a lot around here...
> > >
> > > symptom of too much free time on hands
> > >
> > > randy
> > >
> >
> 

From mary.ietf.barnes@gmail.com  Fri Aug  3 15:20:07 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DEE721E8049 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 15:20:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.526
X-Spam-Level: 
X-Spam-Status: No, score=-103.526 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nq1a+-kbjZtC for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 15:20:06 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id E34E821E8034 for <ietf@ietf.org>; Fri,  3 Aug 2012 15:20:05 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so1992673lbb.31 for <ietf@ietf.org>; Fri, 03 Aug 2012 15:20:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=lmSRDAISGTGVw5/auHBQiTs5HqrD2YY+VXbx0chebMg=; b=ci0+Tseb1gpIzbj38KtsVuGf8sY/nk3Wc0CulJIocD0ka2C9mm9GOter15GdVvO7GS +sAmQk7iPtRNkY/mWR5cfrcNgtjwa1WHe6+6+deZ1vgtmwwk7CuGhuX5TNHI/RfeeqbU BEYaVRK2TV2oAjIwR/8kQ/bO7nRov8wOyAuCxmw1ylRj6GlZF6GIYCnlzwbF6pxZABLZ /zmWPHAhP1MoC5yjDKWLoiI/3Kr0rvIzmtDFejZdNlCgKCjjRiT+BpK/TgUeCzhkRLmg 5GFyop49HNCIuvSa5/Ud1DOj84MXgGChExNMW2EVNXWQrLNXgd32wMZnKLl2xUwBdUkT mBrA==
MIME-Version: 1.0
Received: by 10.112.86.132 with SMTP id p4mr1231827lbz.22.1344032404864; Fri, 03 Aug 2012 15:20:04 -0700 (PDT)
Received: by 10.112.85.196 with HTTP; Fri, 3 Aug 2012 15:20:04 -0700 (PDT)
In-Reply-To: <alpine.OSX.2.01.1208031505550.16675@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org> <CAHBDyN6VaL3fgYe+C+o9d93VZ1bR_EDmrPN7-Sv+7BiJ9+Q9AA@mail.gmail.com> <m2ipczu5mu.wl%randy@psg.com> <42D7895B-8949-41FF-AE5B-0C9B813CEE8C@mnot.net> <m2d337u3fc.wl%randy@psg.com> <20104150-FCF4-4914-8656-72FFC9BA94AA@lucidvision.com> <CAHBDyN63_r2TEf7h81r9NYnQbdriC9Ztr-cT7vapO0uyRYB5_w@mail.gmail.com> <alpine.OSX.2.01.1208031505550.16675@173-11-110-132-sfba.hfc.comcastbusiness.net>
Date: Fri, 3 Aug 2012 17:20:04 -0500
Message-ID: <CAHBDyN5E9PZYb+e6p5excaeOAe-YUmLyG2=KAfGGg4XN9R=XPw@mail.gmail.com>
Subject: Re: Meeting "lounges" at IETF meetings
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Ole Jacobsen <ole@cisco.com>, Alexa Morris <amorris@amsl.com>
Content-Type: multipart/alternative; boundary=bcaec554d5220efefa04c663ee86
Cc: Mark Nottingham <mnot@mnot.net>, ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 22:20:07 -0000

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

Thanks!

On Fri, Aug 3, 2012 at 5:10 PM, Ole Jacobsen <ole@cisco.com> wrote:

>
> The narrowness of the corridoors, placement of food/drink and all that
> was discussed in our wrap-up meeting this morning, and indeed the
> issues you have raised were indentified as areas for improvement.
> Since we are coming back to THIS hotel, there are certainly things
> that can be done better, and will be done better, next time.
>
> Ole
>
>
> Ole J. Jacobsen
> Editor and Publisher,  The Internet Protocol Journal
> Cisco Systems
> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> Skype: organdemo
>
>
> On Fri, 3 Aug 2012, Mary Barnes wrote:
>
> > The issue that I experienced (and why I'm fussing)  is that if you were
> > attending many sessions in the Regency rooms (and moving rooms between
> > sessions), it was extremely difficult to weave your way through the
> > corridor as many people were having their discussion directly in the
> middle
> > of the corridor.  There just was not room in that corridor for side
> > conversations.  The situation was made worse as that corridor was where
> > they served the refreshments.   And trying to ask people politely to move
> > generally had no impact in my experience as people were too engaged in
> > their conversations.
> >
> > Mary.
> >
> > On Fri, Aug 3, 2012 at 4:14 PM, Thomas Nadeau <tnadeau@lucidvision.com
> >wrote:
> >
> > > I agree with randy. I've never had an issue finding a place to
> huddle/meet
> > > when necessary at an ietf meeting venue. between the hallways, bar,
> etc I'm
> > > not sure what the fuss is all about.
> > >
> > > Tom
> > >
> > >
> > >
> > > On Aug 3, 2012, at 3:27 PM, Randy Bush <randy@psg.com> wrote:
> > >
> > > >>> i have no need to micro-manage the secretariat.
> > > >> seems to happen a lot around here...
> > > >
> > > > symptom of too much free time on hands
> > > >
> > > > randy
> > > >
> > >
> >
>

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

Thanks!<br><br><div class=3D"gmail_quote">On Fri, Aug 3, 2012 at 5:10 PM, O=
le Jacobsen <span dir=3D"ltr">&lt;<a href=3D"mailto:ole@cisco.com" target=
=3D"_blank">ole@cisco.com</a>&gt;</span> wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">
<br>
The narrowness of the corridoors, placement of food/drink and all that<br>
was discussed in our wrap-up meeting this morning, and indeed the<br>
issues you have raised were indentified as areas for improvement.<br>
Since we are coming back to THIS hotel, there are certainly things<br>
that can be done better, and will be done better, next time.<br>
<br>
Ole<br>
<br>
<br>
Ole J. Jacobsen<br>
Editor and Publisher, =A0The Internet Protocol Journal<br>
Cisco Systems<br>
Tel: <a href=3D"tel:%2B1%20408-527-8972" value=3D"+14085278972">+1 408-527-=
8972</a> =A0 Mobile: <a href=3D"tel:%2B1%20415-370-4628" value=3D"+14153704=
628">+1 415-370-4628</a><br>
E-mail: <a href=3D"mailto:ole@cisco.com">ole@cisco.com</a> =A0URL: <a href=
=3D"http://www.cisco.com/ipj" target=3D"_blank">http://www.cisco.com/ipj</a=
><br>
Skype: organdemo<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
On Fri, 3 Aug 2012, Mary Barnes wrote:<br>
<br>
&gt; The issue that I experienced (and why I&#39;m fussing) =A0is that if y=
ou were<br>
&gt; attending many sessions in the Regency rooms (and moving rooms between=
<br>
&gt; sessions), it was extremely difficult to weave your way through the<br=
>
&gt; corridor as many people were having their discussion directly in the m=
iddle<br>
&gt; of the corridor. =A0There just was not room in that corridor for side<=
br>
&gt; conversations. =A0The situation was made worse as that corridor was wh=
ere<br>
&gt; they served the refreshments. =A0 And trying to ask people politely to=
 move<br>
&gt; generally had no impact in my experience as people were too engaged in=
<br>
&gt; their conversations.<br>
&gt;<br>
&gt; Mary.<br>
&gt;<br>
&gt; On Fri, Aug 3, 2012 at 4:14 PM, Thomas Nadeau &lt;<a href=3D"mailto:tn=
adeau@lucidvision.com">tnadeau@lucidvision.com</a>&gt;wrote:<br>
&gt;<br>
&gt; &gt; I agree with randy. I&#39;ve never had an issue finding a place t=
o huddle/meet<br>
&gt; &gt; when necessary at an ietf meeting venue. between the hallways, ba=
r, etc I&#39;m<br>
&gt; &gt; not sure what the fuss is all about.<br>
&gt; &gt;<br>
&gt; &gt; Tom<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; On Aug 3, 2012, at 3:27 PM, Randy Bush &lt;<a href=3D"mailto:rand=
y@psg.com">randy@psg.com</a>&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt; &gt;&gt;&gt; i have no need to micro-manage the secretariat.<br>
&gt; &gt; &gt;&gt; seems to happen a lot around here...<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; symptom of too much free time on hands<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; randy<br>
&gt; &gt; &gt;<br>
&gt; &gt;<br>
&gt;<br>
</div></div></blockquote></div><br>

--bcaec554d5220efefa04c663ee86--

From stephen.farrell@cs.tcd.ie  Fri Aug  3 15:37:39 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 411D011E80A6 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 15:37:39 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r6tdt2ROW5Rn for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 15:37:38 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 29E3B11E80D9 for <ietf@ietf.org>; Fri,  3 Aug 2012 15:37:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 18774171475; Fri,  3 Aug 2012 23:37:37 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1344033456; bh=BINAtUb4O1icc/ A9EbjFqD+2zdXVnyDNGOgt0W4wOM4=; b=KenHqMlEATPG2bo2IZ2qm5WmPawW/A 2Qat60jqconl31smbr+f5fi7xiz9bR8kMqBqWVuuuT+hLm3V7ryuEeVJaH5igzqr d/yiwZc7FQ9Q+vdWH5C2U7m1LSkpfMcYhNXt0A2iCHi2z6l0Ufksm6ATxwWGHKtQ TyeAvfVt86euwq+SmY19OnYI19kFbtupjkRlIyZ4AI2Hv6ftO4ClTchHnAqxs3oA R7QWa7apprJE/DlwZAsmB2gHTmlzkzIJAEORoV1LHlar3r002IHfda+pbM9xVJIW MCQQqTjUvlvSivowbbF0j8+ycWkqbJMSegFGfb+8/Bz7gnmYk6t5LZcw==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id nmj3ayyr4RVj; Fri,  3 Aug 2012 23:37:36 +0100 (IST)
Received: from [IPv6:2001:df8:0:64:8853:ef9b:1b62:6a9b] (unknown [IPv6:2001:df8:0:64:8853:ef9b:1b62:6a9b]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 0F73C171472; Fri,  3 Aug 2012 23:37:34 +0100 (IST)
Message-ID: <501C52AC.1010106@cs.tcd.ie>
Date: Fri, 03 Aug 2012 23:37:32 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: Ole Jacobsen <ole@cisco.com>
Subject: Re: Meeting "lounges" at IETF meetings
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org> <CAHBDyN6VaL3fgYe+C+o9d93VZ1bR_EDmrPN7-Sv+7BiJ9+Q9AA@mail.gmail.com> <m2ipczu5mu.wl%randy@psg.com> <42D7895B-8949-41FF-AE5B-0C9B813CEE8C@mnot.net> <m2d337u3fc.wl%randy@psg.com> <20104150-FCF4-4914-8656-72FFC9BA94AA@lucidvision.com> <CAHBDyN63_r2TEf7h81r9NYnQbdriC9Ztr-cT7vapO0uyRYB5_w@mail.gmail.com> <alpine.OSX.2.01.1208031505550.16675@173-11-110-132-sfba.hfc.comcastbusiness.net>
In-Reply-To: <alpine.OSX.2.01.1208031505550.16675@173-11-110-132-sfba.hfc.comcastbusiness.net>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 22:37:39 -0000

On 08/03/2012 11:10 PM, Ole Jacobsen wrote:
> 
> The narrowness of the corridoors, placement of food/drink and all that 
> was discussed in our wrap-up meeting this morning, and indeed the 
> issues you have raised were indentified as areas for improvement. 
> Since we are coming back to THIS hotel, there are certainly things 
> that can be done better, and will be done better, next time. 

That gives the NOC folks time to figure out how to take
over the elevator system for next time too:-)

S

> 
> Ole
> 
> 
> Ole J. Jacobsen
> Editor and Publisher,  The Internet Protocol Journal
> Cisco Systems
> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> Skype: organdemo
> 
> 
> On Fri, 3 Aug 2012, Mary Barnes wrote:
> 
>> The issue that I experienced (and why I'm fussing)  is that if you were
>> attending many sessions in the Regency rooms (and moving rooms between
>> sessions), it was extremely difficult to weave your way through the
>> corridor as many people were having their discussion directly in the middle
>> of the corridor.  There just was not room in that corridor for side
>> conversations.  The situation was made worse as that corridor was where
>> they served the refreshments.   And trying to ask people politely to move
>> generally had no impact in my experience as people were too engaged in
>> their conversations.
>>
>> Mary.
>>
>> On Fri, Aug 3, 2012 at 4:14 PM, Thomas Nadeau <tnadeau@lucidvision.com>wrote:
>>
>>> I agree with randy. I've never had an issue finding a place to huddle/meet
>>> when necessary at an ietf meeting venue. between the hallways, bar, etc I'm
>>> not sure what the fuss is all about.
>>>
>>> Tom
>>>
>>>
>>>
>>> On Aug 3, 2012, at 3:27 PM, Randy Bush <randy@psg.com> wrote:
>>>
>>>>>> i have no need to micro-manage the secretariat.
>>>>> seems to happen a lot around here...
>>>>
>>>> symptom of too much free time on hands
>>>>
>>>> randy
>>>>
>>>
>>

From jmpolk@cisco.com  Fri Aug  3 15:40:50 2012
Return-Path: <jmpolk@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD47B21F8CB2 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 15:40:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.517
X-Spam-Level: 
X-Spam-Status: No, score=-110.517 tagged_above=-999 required=5 tests=[AWL=0.082, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A90yFMDESyy6 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 15:40:49 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id C976121F8C9F for <ietf@ietf.org>; Fri,  3 Aug 2012 15:40:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=2852; q=dns/txt; s=iport; t=1344033648; x=1345243248; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=jK59vaZnhTRLLk5m+SCWzudRke++tFUobQxnAcAC+0M=; b=B6WKVhWqluXjQBSdr6TE9UzRnZghklNJcLg6LlU+f6iSmXPO9vE7u2fL ARphhusmW+JibTo78LZrRh9iwu9sUg9sufwU/8BnRdGW/Wq2r22xCvhzf huWBY5tVQBsE9JpKGo6VdZUx2sGGnmSXEd+39glWlKnOOlZjIvWR4RhC1 o=;
X-IronPort-AV: E=Sophos;i="4.77,709,1336348800"; d="scan'208";a="54024161"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 03 Aug 2012 22:40:45 +0000
Received: from jmpolk-WS.cisco.com ([10.21.167.61]) (authenticated bits=0) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q73Mc6OY008678 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Aug 2012 22:40:44 GMT
Message-Id: <201208032240.q73Mc6OY008678@mtv-core-1.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 03 Aug 2012 17:38:06 -0500
To: Ole Jacobsen <ole@cisco.com>, Mary Barnes <mary.ietf.barnes@gmail.com>
From: James Polk <jmpolk@cisco.com>
Subject: Re: Meeting "lounges" at IETF meetings
In-Reply-To: <alpine.OSX.2.01.1208031505550.16675@173-11-110-132-sfba.hf c.comcastbusiness.net>
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org> <CAHBDyN6VaL3fgYe+C+o9d93VZ1bR_EDmrPN7-Sv+7BiJ9+Q9AA@mail.gmail.com> <m2ipczu5mu.wl%randy@psg.com> <42D7895B-8949-41FF-AE5B-0C9B813CEE8C@mnot.net> <m2d337u3fc.wl%randy@psg.com> <20104150-FCF4-4914-8656-72FFC9BA94AA@lucidvision.com> <CAHBDyN63_r2TEf7h81r9NYnQbdriC9Ztr-cT7vapO0uyRYB5_w@mail.gmail.com> <alpine.OSX.2.01.1208031505550.16675@173-11-110-132-sfba.hfc.comcastbusiness.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
Cc: Mark Nottingham <mnot@mnot.net>, ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 22:40:50 -0000

Having missed only 2 meetings in 13 years, I can say that no venue 
was perfect, but some were very good. It becomes a case of which 
venues have the fewest "bad" things. I believe this venue was 
exceptional at many things, very good at nearly all others, with the 
bad things being food/snacks served in the crowded hallway and that 
sucky elevator algorithm (which was by far the worst think here).

The crowded hallway we can't change.

We can change where the snacks are served, and I have read that will 
happen for our next meeting in Vancouver here in 15 months.

To me the exceptional aspects far outweighed the bad things - so I'm 
chalking this venue up as one of the best in 13 years of attending 
IETFs, and a *serious* contrast to the Paris venue (which I believe 
was one of the worst - each time we were there, though the city was nice).

However, YMMV

James

At 05:10 PM 8/3/2012, Ole Jacobsen wrote:

>The narrowness of the corridoors, placement of food/drink and all that
>was discussed in our wrap-up meeting this morning, and indeed the
>issues you have raised were indentified as areas for improvement.
>Since we are coming back to THIS hotel, there are certainly things
>that can be done better, and will be done better, next time.
>
>Ole
>
>
>Ole J. Jacobsen
>Editor and Publisher,  The Internet Protocol Journal
>Cisco Systems
>Tel: +1 408-527-8972   Mobile: +1 415-370-4628
>E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
>Skype: organdemo
>
>
>On Fri, 3 Aug 2012, Mary Barnes wrote:
>
> > The issue that I experienced (and why I'm fussing)  is that if you were
> > attending many sessions in the Regency rooms (and moving rooms between
> > sessions), it was extremely difficult to weave your way through the
> > corridor as many people were having their discussion directly in the middle
> > of the corridor.  There just was not room in that corridor for side
> > conversations.  The situation was made worse as that corridor was where
> > they served the refreshments.   And trying to ask people politely to move
> > generally had no impact in my experience as people were too engaged in
> > their conversations.
> >
> > Mary.
> >
> > On Fri, Aug 3, 2012 at 4:14 PM, Thomas Nadeau 
> <tnadeau@lucidvision.com>wrote:
> >
> > > I agree with randy. I've never had an issue finding a place to 
> huddle/meet
> > > when necessary at an ietf meeting venue. between the hallways, 
> bar, etc I'm
> > > not sure what the fuss is all about.
> > >
> > > Tom
> > >
> > >
> > >
> > > On Aug 3, 2012, at 3:27 PM, Randy Bush <randy@psg.com> wrote:
> > >
> > > >>> i have no need to micro-manage the secretariat.
> > > >> seems to happen a lot around here...
> > > >
> > > > symptom of too much free time on hands
> > > >
> > > > randy
> > > >
> > >
> >


From mohta@necom830.hpcl.titech.ac.jp  Fri Aug  3 16:19:45 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F73521F8DCA for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 16:19:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.04
X-Spam-Level: 
X-Spam-Status: No, score=-0.04 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fVDSQVFJCmX3 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 16:19: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 E112721F8DC9 for <ietf@ietf.org>; Fri,  3 Aug 2012 16:19:43 -0700 (PDT)
Received: (qmail 12828 invoked from network); 3 Aug 2012 23:28: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; 3 Aug 2012 23:28:28 -0000
Message-ID: <501C5C75.9040209@necom830.hpcl.titech.ac.jp>
Date: Sat, 04 Aug 2012 08:19:17 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FE2715C.2090601@necom830.hpcl.titech.ac.jp> <4FF20DE7.2080208@isi.edu> <500654AB.7060500@necom830.hpcl.titech.ac.jp> <8F5CBE79-4540-4519-9F51-62B36686EE8C@isi.edu>
In-Reply-To: <8F5CBE79-4540-4519-9F51-62B36686EE8C@isi.edu>
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, 03 Aug 2012 23:19:45 -0000

Joe Touch wrote:

> Translators violate RFC791. They cannot merely copy the
> low-order bits of the field, since that is insufficiently
> unique, and isn't specified as being generated at the
> IPv6 source in compliance with IPv4 requirements.

RFC2765 specifies that translators can merely copy the
low-order bits of the field.

Moreover, RFC2460 specifies:

   In that case, the IPv6 node
   is not required to reduce the size of subsequent packets to less than
   1280, but must include a Fragment header in those packets so that the
   IPv6-to-IPv4 translating router can obtain a suitable Identification
   value to use in resulting IPv4 fragments.

That is, RFC2460 guarantees that translators can obtain "a
suitable Identification value" from IPv6 "Fragment header".

Or, are you saying RFC2460 and RFC2765 violate RFC791?

I'm afraid you must say so, if you insist on "existing systems
violate the current specification" (quote from abstract of your
draft).

> It quotes IPv6 examples, but does not propose to change
> IPv6 processing. That may be needed, but that would be
> outside the scope of this doc.

It is inside the scope because RFC2765 specifies how IPv4
ID is generated from RFC2460 fragment header, which is,
according to your draft, a violation of RFC791.

>>    Finally, the IPv6 ID field is
>>    32 bits, but lower 16 bits are required unique per
>>    source/destination address pair for
>>    IPv6,
> 
> That's incorrect as per RFC2460. Other RFCs may violate that
> original spec, but that needs to be cleaned up separately.

As I stated above, RFC2460 gurantees "a suitable Identification
value" for IPv4 ID is there in IPv6 fragmentation ID.

Or, if you think RFC2460 does not mind ID uniqueness (of IPv4,
at least) so much, RFC791 should not either.

						Masataka Ohta

From tjc@ecs.soton.ac.uk  Fri Aug  3 16:43:55 2012
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEF1921F8DAC for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 16:43:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.668
X-Spam-Level: 
X-Spam-Status: No, score=-1.668 tagged_above=-999 required=5 tests=[AWL=-0.465, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zs7HuWNGss0S for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 16:43:55 -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 1A61E21E8039 for <ietf@ietf.org>; Fri,  3 Aug 2012 16:43:53 -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 q73NhpBb031714 for <ietf@ietf.org>; Sat, 4 Aug 2012 00:43:51 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk q73NhpBb031714
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1344037431; bh=eDR19xHK1JP5VgzvUUitFs/7r1g=; h=Subject:References:From:In-Reply-To:Date:To:Mime-Version; b=KIS19sz7J0rSuPqbGp1axdPTTfVjMFlqlDKmlkgWfl5kVtx+YmHj5vf73tLLM8Sz4 vh7ZtniEYGQ12pbJW0ZCvECJrWK06c6tctcJ7CN+8dgZc4TuxUwzyedZUmnUHaS44p O3EokBUytX4K6cXLDry6k32ekDOcqhCxRzh6j62g=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id o730hp0430612371SA ret-id none; Sat, 04 Aug 2012 00:43:51 +0100
Received: from [130.129.11.5] (dhcp-9305.meeting.ietf.org [130.129.11.5]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id q73NhkjB024688 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Sat, 4 Aug 2012 00:43:47 +0100
Subject: Re: Meeting "lounges" at IETF meetings
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org> <CAHBDyN6VaL3fgYe+C+o9d93VZ1bR_EDmrPN7-Sv+7BiJ9+Q9AA@mail.gmail.com> <m2ipczu5mu.wl%randy@psg.com> <42D7895B-8949-41FF-AE5B-0C9B813CEE8C@mnot.net> <m2d337u3fc.wl%randy@psg.com> <20104150-FCF4-4914-8656-72FFC9BA94AA@lucidvision.com> <CAHBDyN63_r2TEf7h81r9NYnQbdriC9Ztr-cT7vapO0uyRYB5_w@mail.gmail.com> <F56E239C-E790-4D4A-9239-BE20F3B41362@ecs.soton.ac.uk>
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: text/plain; charset=us-ascii
X-Mailer: iPad Mail (9B206)
In-Reply-To: <CAHBDyN63_r2TEf7h81r9NYnQbdriC9Ztr-cT7vapO0uyRYB5_w@mail.gmail.com>
Message-ID: <EMEW3|39c1fd589ec0aacfc22ff15d64d4f777o730hp03tjc|ecs.soton.ac.uk|F56E239C-E790-4D4A-9239-BE20F3B41362@ecs.soton.ac.uk>
Date: Sat, 4 Aug 2012 00:43:48 +0100
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=o730hp043061237100; tid=o730hp0430612371SA; 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: q73NhpBb031714
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, 03 Aug 2012 23:43:56 -0000

On 3 Aug 2012, at 22:56, Mary Barnes <mary.ietf.barnes@gmail.com> wrote:

> The issue that I experienced (and why I'm fussing)  is that if you were at=
tending many sessions in the Regency rooms (and moving rooms between session=
s), it was extremely difficult to weave your way through the corridor as man=
y people were having their discussion directly in the middle of the corridor=
.  There just was not room in that corridor for side conversations.  The sit=
uation was made worse as that corridor was where they served the refreshment=
s.   And trying to ask people politely to move generally had no impact in my=
 experience as people were too engaged in their conversations. =20

The corridor congestion when food was served was the only minor nit in an ot=
herwise excellent meeting.  The wireless, the facilities etc were all top no=
tch.

Tim=

From tjc@ecs.soton.ac.uk  Fri Aug  3 16:46:36 2012
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4B5821F8DC9 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 16:46:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.601
X-Spam-Level: 
X-Spam-Status: No, score=-1.601 tagged_above=-999 required=5 tests=[AWL=-0.399, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yo5NlGfHvkD5 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 16:46:36 -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 F2FD521F8DC3 for <ietf@ietf.org>; Fri,  3 Aug 2012 16:46:35 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id q73NkUXt032431 for <ietf@ietf.org>; Sat, 4 Aug 2012 00:46:30 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk q73NkUXt032431
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1344037590; bh=5uIV9EKixA7y21CpsUL9BlGPn00=; h=Subject:References:From:In-Reply-To:Date:To:Mime-Version; b=r7KrCA7tsX55D9M6ANBG4hIbSZhcxhTBTfmwV8JrpbIlCkBl1Z8ns0/dW0vSKjbSC AuG0Jya7r/1UPwXHcVOz3fILLvQOPPgtHGIrKOW9+7R+XYTF0+gqg+5cNb6pNgStJW ZMAMd2ExiMNGYgFGUrPWWWRoT8/fbC8FfiEFQ1Vs=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id o730kU0430612389Lc ret-id none; Sat, 04 Aug 2012 00:46:30 +0100
Received: from [130.129.11.5] (dhcp-9305.meeting.ietf.org [130.129.11.5]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id q73NkPjo025454 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Sat, 4 Aug 2012 00:46:27 +0100
Subject: Re: Meeting "lounges" at IETF meetings
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org> <CAHBDyN6VaL3fgYe+C+o9d93VZ1bR_EDmrPN7-Sv+7BiJ9+Q9AA@mail.gmail.com> <m2ipczu5mu.wl%randy@psg.com> <42D7895B-8949-41FF-AE5B-0C9B813CEE8C@mnot.net> <m2d337u3fc.wl%randy@psg.com> <20104150-FCF4-4914-8656-72FFC9BA94AA@lucidvision.com> <CAHBDyN63_r2TEf7h81r9NYnQbdriC9Ztr-cT7vapO0uyRYB5_w@mail.gmail.com> <alpine.OSX.2.01.1208031505550.16675@173-11-110-132-sfba.hfc.comcastbusiness.net> <201208032240.q73Mc6OY008678@mtv-core-1.cisco.com> <48A2DE16-BC2B-4F37-9866-21B869B831B2@ecs.soton.ac.uk>
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary=Apple-Mail-9363729D-3854-4262-9BAE-75A98955BFC4
X-Mailer: iPad Mail (9B206)
In-Reply-To: <201208032240.q73Mc6OY008678@mtv-core-1.cisco.com>
Message-ID: <EMEW3|ac0294addafd52131b524a451da3ac66o730kU03tjc|ecs.soton.ac.uk|48A2DE16-BC2B-4F37-9866-21B869B831B2@ecs.soton.ac.uk>
Date: Sat, 4 Aug 2012 00:46:28 +0100
To: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=o730kU043061238900; tid=o730kU0430612389Lc; 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: q73NkUXt032431
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, 03 Aug 2012 23:46:36 -0000

--Apple-Mail-9363729D-3854-4262-9BAE-75A98955BFC4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 3 Aug 2012, at 23:38, James Polk <jmpolk@cisco.com> wrote:
>=20
> To me the exceptional aspects far outweighed the bad things - so I'm chalk=
ing this venue up as one of the best in 13 years of attending IETFs, and a *=
serious* contrast to the Paris venue (which I believe was one of the worst -=
 each time we were there, though the city was nice).

+1

Would be fun to get access to an API for the lifts for next time ;)

Tim=

--Apple-Mail-9363729D-3854-4262-9BAE-75A98955BFC4
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=utf-8

<html><head></head><body bgcolor="#FFFFFF"><div><span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">On 3 Aug 2012, at 23:38, James Polk &lt;<a href="mailto:jmpolk@cisco.com">jmpolk@cisco.com</a>&gt; wrote:</span></div><blockquote type="cite"><div><span></span><br><span>To me the exceptional aspects far outweighed the bad things - so I'm chalking this venue up as one of the best in 13 years of attending IETFs, and a *serious* contrast to the Paris venue (which I believe was one of the worst - each time we were there, though the city was nice).</span><font class="Apple-style-span" color="#005001"><br></font></div></blockquote><br><div>+1</div><div><br></div><div>Would be fun to get access to an API for the lifts for next time ;)</div><div><br></div><div>Tim</div></body></html>
--Apple-Mail-9363729D-3854-4262-9BAE-75A98955BFC4--

From touch@isi.edu  Fri Aug  3 16:53:03 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C46B021E8082 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 16:53:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.47
X-Spam-Level: 
X-Spam-Status: No, score=-105.47 tagged_above=-999 required=5 tests=[AWL=1.129, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fCc2KEdtqAWI for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 16:53:03 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id E9C5621E8055 for <ietf@ietf.org>; Fri,  3 Aug 2012 16:53:02 -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 q73NqXHS017277 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 3 Aug 2012 16:52:33 -0700 (PDT)
Message-ID: <501C6441.4000302@isi.edu>
Date: Fri, 03 Aug 2012 16:52:33 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FE2715C.2090601@necom830.hpcl.titech.ac.jp> <4FF20DE7.2080208@isi.edu> <500654AB.7060500@necom830.hpcl.titech.ac.jp> <8F5CBE79-4540-4519-9F51-62B36686EE8C@isi.edu> <501C5C75.9040209@necom830.hpcl.titech.ac.jp>
In-Reply-To: <501C5C75.9040209@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=ISO-2022-JP
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: Fri, 03 Aug 2012 23:53:03 -0000

On 8/3/2012 4:19 PM, Masataka Ohta wrote:
> Joe Touch wrote:
> 
>> Translators violate RFC791. They cannot merely copy the
>> low-order bits of the field, since that is insufficiently
>> unique, and isn't specified as being generated at the
>> IPv6 source in compliance with IPv4 requirements.
> 
> RFC2765 specifies that translators can merely copy the
> low-order bits of the field.

Yes, but this is not compatible with RFC791.

> Moreover, RFC2460 specifies:
> 
>     In that case, the IPv6 node
>     is not required to reduce the size of subsequent packets to less than
>     1280, but must include a Fragment header in those packets so that the
>     IPv6-to-IPv4 translating router can obtain a suitable Identification
>     value to use in resulting IPv4 fragments.
> 
> That is, RFC2460 guarantees that translators can obtain "a
> suitable Identification value" from IPv6 "Fragment header".

The case above occurs only when the source gets back a "packet too big"
message with a desired MTU less than 1280. Note that this might never
happen, in which case there would never be any Fragment header.

However, even when it does happen, there is no instruction above about
how to construct the header that is compliant with RFC791.

Further, the source might already be inserting the fragmentation header
(e.g., on a 2KB packet). There's no instruction in how fragment headers
are constructed in general that complies with RFC791.

Simply using the low 16 bits is not correct. In particular, RFC2460
suggests that its 32-bit counter can wrap once a minute, and that only
one such counter might be needed for an endpoint for all connections. In
that case, the entire number space wraps twice as fast as RFC791/RFC1122
require for IPv4, and it's half the bit-width, so the low-order bits
alone wrap 120,000x faster.

> Or, are you saying RFC2460 and RFC2765 violate RFC791?

Yes.

> I'm afraid you must say so, if you insist on "existing systems
> violate the current specification" (quote from abstract of your
> draft).
> 
>> It quotes IPv6 examples, but does not propose to change
>> IPv6 processing. That may be needed, but that would be
>> outside the scope of this doc.
> 
> It is inside the scope because RFC2765 specifies how IPv4
> ID is generated from RFC2460 fragment header, which is,
> according to your draft, a violation of RFC791.

This document updates RFC791, but does not fix either RFC2460 or
RFC2765. This document does not make any statements about how IPv6
generates its IDs.

>>>     Finally, the IPv6 ID field is
>>>     32 bits, but lower 16 bits are required unique per
>>>     source/destination address pair for
>>>     IPv6,
>>
>> That's incorrect as per RFC2460. Other RFCs may violate that
>> original spec, but that needs to be cleaned up separately.
> 
> As I stated above, RFC2460 guarantees "a suitable Identification
> value" for IPv4 ID is there in IPv6 fragmentation ID.

Not the way I interpret the text, especially because there are other
ways to generate IDs in RFC2460 that could be translated to IPv4 that
might not result from ICMP errors, or that might never have
Fragmentation headers anyway.

> Or, if you think RFC2460 does not mind ID uniqueness (of IPv4,
> at least) so much, RFC791 should not either.

I think there are a lot of IETF documents that are not reviewed in the
correct context of existing standards. I don't think that applies to
this draft, though.

Joe

From ned+ietf@mauve.mrochek.com  Fri Aug  3 17:48:20 2012
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 8F8D321F8D5F for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 17:48:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.493
X-Spam-Level: 
X-Spam-Status: No, score=-2.493 tagged_above=-999 required=5 tests=[AWL=0.106,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id euwPCQC6f-N8 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 17:48:20 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 60D1F21F8DE0 for <ietf@ietf.org>; Fri,  3 Aug 2012 17:48:20 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OIMHYAZYXS0064WP@mauve.mrochek.com> for ietf@ietf.org; Fri, 3 Aug 2012 17:43:15 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OIGH28IS2O0006TF@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Fri, 3 Aug 2012 17:43:08 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OIMHY7BVKK0006TF@mauve.mrochek.com>
Date: Fri, 03 Aug 2012 15:59:04 -0700 (PDT)
Subject: Re: Basic ietf process question ...
In-reply-to: "Your message dated Fri, 03 Aug 2012 12:47:44 -0500" <270DDF46-AA04-49C0-B54C-35FD0AE0350F@mnot.net>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com> <CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com> <CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com> <501AA9DF.6010208@raszuk.net> <EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com> <501AB4F5.7030205@raszuk.net> <501AC2C7.6040707@gmail.com> <270DDF46-AA04-49C0-B54C-35FD0AE0350F@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
Cc: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>, opsawg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Aug 2012 00:48:20 -0000

> XML Schema is grossly over-engineered for its purpose; being the subject of
> requirements from not only the document markup field, but also databases and
> object models, it's a twisted monstrosity that tries to do many things, and
> fails at most.

Agreed, and I would add that it is seriously lacking in flexibility. (I would
like to have words with whoever thought the "unique particle attribution rule"
was a good idea.)

That said, there's a timing issue in play here. A variety of tools supporting
other validation systems, e.g., RelaxNG or Schematron are available now, but a
few years back alternatives to XML Schema were much more limited. Despite our
dislike we've used XML Schema in a couple of places for precisely this reason.

> Specifically, it's very common for people to try to use schema to inform
> "binding" tools into specific languages. However, the underlying metamodel of
> XML, the Infoset, is both complex and a poor fit for most languages, so
> bindings take "shortcuts" and expose a profile of XML's range of expression,
> encouraging some patterns of use, while discouraging (or disallowing) others.
> Since the bindings often make different decisions (based upon the language of
> use), interoperability is difficult (sometimes, impossible).

It very much depends on what you're doing and how you're doing it. If what
you want is for your data to manifest directly as a data structure, XML is
a lousy fit for that for a bunch of different reasons. Json is the clear choice
in such cases. But there are other uses where the more complex Infoset of
XML can be an asset.

Really, it's all about how you use the available tools.

> Furthermore, designing a schema that is extensible is incredibly convoluted
> in XML Schema 1.0. Schema 1.1 was designed to address this failure, but it
> hasn't been broadly adopted; most people I know in the field consider it a
> failure.

Yes, XML Schema makes this a lot harder to do than it should be, but in a lot
of designs I've seen it also has to do with how XML is actually used. A bad
design is a bad design, regardless of what schema language you use.

> What surprises me and many others is that people are still using it and
> promoting it, when it's well-understood by almost EVERYONE who was involved in
> using XML for protocols in the past ten years agrees that it's a mistake.

See above. I certainly wouldn't use XML Schema for anything new, but there's
a lot of legacy stuff out there.

				Ned

From mnot@mnot.net  Fri Aug  3 17:50:30 2012
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B452921F8D38; Fri,  3 Aug 2012 17:50:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vucsTlAyQS+n; Fri,  3 Aug 2012 17:50:30 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 01D2E21F8D05; Fri,  3 Aug 2012 17:50:29 -0700 (PDT)
Received: from [10.10.5.63] (unknown [67.79.29.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 4BD6250A64; Fri,  3 Aug 2012 20:50:22 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: Basic ietf process question ...
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <01OIMHY7BVKK0006TF@mauve.mrochek.com>
Date: Fri, 3 Aug 2012 19:50:21 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <8D242074-DA5B-4C31-807D-79116517A64D@mnot.net>
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com> <CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com> <CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com> <501AA9DF.6010208@raszuk.net> <EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com> <501AB4F5.7030205@raszuk.net> <501AC2C7.6040707@gmail.com> <270DDF46-AA04-49C0-B54C-35FD0AE0350F@mnot.net> <01OIMHY7BVKK0006TF@mauve.mrochek.com>
To: Ned Freed <ned.freed@mrochek.com>
X-Mailer: Apple Mail (2.1485)
Cc: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>, opsawg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Aug 2012 00:50:30 -0000

On 03/08/2012, at 5:59 PM, Ned Freed <ned.freed@mrochek.com> wrote:

>> Specifically, it's very common for people to try to use schema to =
inform
>> "binding" tools into specific languages. However, the underlying =
metamodel of
>> XML, the Infoset, is both complex and a poor fit for most languages, =
so
>> bindings take "shortcuts" and expose a profile of XML's range of =
expression,
>> encouraging some patterns of use, while discouraging (or disallowing) =
others.
>> Since the bindings often make different decisions (based upon the =
language of
>> use), interoperability is difficult (sometimes, impossible).
>=20
> It very much depends on what you're doing and how you're doing it. If =
what
> you want is for your data to manifest directly as a data structure, =
XML is
> a lousy fit for that for a bunch of different reasons. Json is the =
clear choice
> in such cases. But there are other uses where the more complex Infoset =
of
> XML can be an asset.

Very much; when it becomes a "document" (e.g., mixed markup), XML is a =
much better choice.

>=20
> Really, it's all about how you use the available tools.
>=20
>> Furthermore, designing a schema that is extensible is incredibly =
convoluted
>> in XML Schema 1.0. Schema 1.1 was designed to address this failure, =
but it
>> hasn't been broadly adopted; most people I know in the field consider =
it a
>> failure.
>=20
> Yes, XML Schema makes this a lot harder to do than it should be, but =
in a lot
> of designs I've seen it also has to do with how XML is actually used. =
A bad
> design is a bad design, regardless of what schema language you use.
>=20
>> What surprises me and many others is that people are still using it =
and
>> promoting it, when it's well-understood by almost EVERYONE who was =
involved in
>> using XML for protocols in the past ten years agrees that it's a =
mistake.
>=20
> See above. I certainly wouldn't use XML Schema for anything new, but =
there's
> a lot of legacy stuff out there.

That's the rub, isn't it?

--
Mark Nottingham
http://www.mnot.net/





From ned+ietf@mauve.mrochek.com  Fri Aug  3 18:19:21 2012
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 AB03521F8BFA for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 18:19:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.496
X-Spam-Level: 
X-Spam-Status: No, score=-2.496 tagged_above=-999 required=5 tests=[AWL=0.103,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UPEk-OFwkAqt for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 18:19:21 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 74AEA21F8DB4 for <ietf@ietf.org>; Fri,  3 Aug 2012 18:19:21 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OIMJ1REFU8005V09@mauve.mrochek.com> for ietf@ietf.org; Fri, 3 Aug 2012 18:14:16 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OIGH28IS2O0006TF@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Fri, 3 Aug 2012 18:14:09 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OIMJ1NAB5W0006TF@mauve.mrochek.com>
Date: Fri, 03 Aug 2012 18:09:47 -0700 (PDT)
Subject: Re: Basic ietf process question ...
In-reply-to: "Your message dated Fri, 03 Aug 2012 19:50:21 -0500" <8D242074-DA5B-4C31-807D-79116517A64D@mnot.net>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com> <CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com> <CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com> <501AA9DF.6010208@raszuk.net> <EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com> <501AB4F5.7030205@raszuk.net> <501AC2C7.6040707@gmail.com> <270DDF46-AA04-49C0-B54C-35FD0AE0350F@mnot.net> <01OIMHY7BVKK0006TF@mauve.mrochek.com> <8D242074-DA5B-4C31-807D-79116517A64D@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
Cc: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>, opsawg@ietf.org, Ned Freed <ned.freed@mrochek.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Aug 2012 01:19:21 -0000

> On 03/08/2012, at 5:59 PM, Ned Freed <ned.freed@mrochek.com> wrote:

> >> Specifically, it's very common for people to try to use schema to inform
> >> "binding" tools into specific languages. However, the underlying metamodel of
> >> XML, the Infoset, is both complex and a poor fit for most languages, so
> >> bindings take "shortcuts" and expose a profile of XML's range of expression,
> >> encouraging some patterns of use, while discouraging (or disallowing) others.
> >> Since the bindings often make different decisions (based upon the language of
> >> use), interoperability is difficult (sometimes, impossible).
> >
> > It very much depends on what you're doing and how you're doing it. If what
> > you want is for your data to manifest directly as a data structure, XML is
> > a lousy fit for that for a bunch of different reasons. Json is the clear choice
> > in such cases. But there are other uses where the more complex Infoset of
> > XML can be an asset.

> Very much; when it becomes a "document" (e.g., mixed markup), XML is a much
> better choice.

The other interesting case is where large amounts of data arrive in a stream.
SAX and SAX-like libraries makes this easy to implement with XML. I hope
there's an equivalent for Json; if not there needs to be.

> >
> > Really, it's all about how you use the available tools.
> >
> >> Furthermore, designing a schema that is extensible is incredibly convoluted
> >> in XML Schema 1.0. Schema 1.1 was designed to address this failure, but it
> >> hasn't been broadly adopted; most people I know in the field consider it a
> >> failure.
> >
> > Yes, XML Schema makes this a lot harder to do than it should be, but in a lot
> > of designs I've seen it also has to do with how XML is actually used. A bad
> > design is a bad design, regardless of what schema language you use.
> >
> >> What surprises me and many others is that people are still using it and
> >> promoting it, when it's well-understood by almost EVERYONE who was involved in
> >> using XML for protocols in the past ten years agrees that it's a mistake.
> >
> > See above. I certainly wouldn't use XML Schema for anything new, but there's
> > a lot of legacy stuff out there.

> That's the rub, isn't it?

Yeah, and it sure is rubbing me the wrong way every time I look at our usage.
I know it was the right choice at the time, and now that it's done it's not
cost effective to change unless we need additional capabilities, but that
all so ... unsatisfying.

				Ned

From mnot@mnot.net  Sat Aug  4 08:52:44 2012
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EC3721F87EE; Sat,  4 Aug 2012 08:52:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KQguquHvzw3M; Sat,  4 Aug 2012 08:52:43 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id A541521F869C; Sat,  4 Aug 2012 08:52:43 -0700 (PDT)
Received: from [10.10.5.63] (unknown [67.79.29.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id EFC2450A64; Sat,  4 Aug 2012 11:52:36 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: Basic ietf process question ...
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <01OIMJ1NAB5W0006TF@mauve.mrochek.com>
Date: Sat, 4 Aug 2012 10:52:37 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <1D580354-3D3D-424B-8DE8-C5C436E8B14D@mnot.net>
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com> <CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com> <CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com> <501AA9DF.6010208@raszuk.net> <EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com> <501AB4F5.7030205@raszuk.net> <501AC2C7.6040707@gmail.com> <270DDF46-AA04-49C0-B54C-35FD0AE0350F@mnot.net> <01OIMHY7BVKK0006TF@mauve.mrochek.com> <8D242074-DA5B-4C31-807D-79116517A64D@mnot.net> <01OIMJ1NAB5W0006TF@mauve.mrochek.com>
To: ned+ietf@mauve.mrochek.com
X-Mailer: Apple Mail (2.1485)
Cc: opsawg@ietf.org, Ned Freed <ned.freed@mrochek.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Aug 2012 15:52:44 -0000

On 03/08/2012, at 8:09 PM, ned+ietf@mauve.mrochek.com wrote:

>> Very much; when it becomes a "document" (e.g., mixed markup), XML is =
a much
>> better choice.
>=20
> The other interesting case is where large amounts of data arrive in a =
stream.
> SAX and SAX-like libraries makes this easy to implement with XML. I =
hope
> there's an equivalent for Json; if not there needs to be.

Funny you mention that, I was just looking into that yesterday.

This seems to be in the front running:
  http://lloyd.github.com/yajl/

Cheers,

--
Mark Nottingham
http://www.mnot.net/





From martin.thomson@gmail.com  Sat Aug  4 09:26:57 2012
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4073521F87BC; Sat,  4 Aug 2012 09:26:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.002
X-Spam-Level: 
X-Spam-Status: No, score=-4.002 tagged_above=-999 required=5 tests=[AWL=-0.403, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F17FUSqwTIQp; Sat,  4 Aug 2012 09:26:56 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1DB3921F87B9; Sat,  4 Aug 2012 09:26:55 -0700 (PDT)
Received: by lahm15 with SMTP id m15so929434lah.31 for <multiple recipients>; Sat, 04 Aug 2012 09:26:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YQ2I2fGHW2cH+OlRBBsMBrVAMQ1c/070NY6eQBpOpc4=; b=bCmPhNAzEqXorExqIF538VHvsdlx6weu09HD2R778tbQO9ajHtO4b+ZPzh7rxlyA9Y LXqGMZWWg39RKfR6049ToeQk8w685E/I/4BmYgKvAKUKGjpHIB4YcZ5uq2nX37kXXbhQ VQZE4PrOfFD6lp4uRW/Gm+CJhXK7CXFU++XJPc0lycyDa8ij1wngGasC0xgsKxhMvTP9 LB0Oe/ffr2eHRcAK/jTvkpt4YCufnHM6cggewvmWK47f5pZXiFfBySw656utv2gSY/a1 35dYFaQ1vWq0+LqT+HdczVH6slORudq6/GKXQF3Jjh1lbI0s3ITnD1Ww5A/mhH4UyWKD ks0w==
MIME-Version: 1.0
Received: by 10.152.109.198 with SMTP id hu6mr5167125lab.21.1344097614848; Sat, 04 Aug 2012 09:26:54 -0700 (PDT)
Received: by 10.112.82.1 with HTTP; Sat, 4 Aug 2012 09:26:54 -0700 (PDT)
In-Reply-To: <1D580354-3D3D-424B-8DE8-C5C436E8B14D@mnot.net>
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com> <CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com> <CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com> <501AA9DF.6010208@raszuk.net> <EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com> <501AB4F5.7030205@raszuk.net> <501AC2C7.6040707@gmail.com> <270DDF46-AA04-49C0-B54C-35FD0AE0350F@mnot.net> <01OIMHY7BVKK0006TF@mauve.mrochek.com> <8D242074-DA5B-4C31-807D-79116517A64D@mnot.net> <01OIMJ1NAB5W0006TF@mauve.mrochek.com> <1D580354-3D3D-424B-8DE8-C5C436E8B14D@mnot.net>
Date: Sat, 4 Aug 2012 09:26:54 -0700
Message-ID: <CABkgnnXRu6c7RpJQoMEL8zW_=6ySM_-1Uato2GubnWtgEd=H8A@mail.gmail.com>
Subject: Re: Basic ietf process question ...
From: Martin Thomson <martin.thomson@gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=UTF-8
Cc: ned+ietf@mauve.mrochek.com, opsawg@ietf.org, Ned Freed <ned.freed@mrochek.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Aug 2012 16:26:57 -0000

On 4 August 2012 08:52, Mark Nottingham <mnot@mnot.net> wrote:
>> The other interesting case is where large amounts of data arrive in a stream.
>> SAX and SAX-like libraries makes this easy to implement with XML. I hope
>> there's an equivalent for Json; if not there needs to be.
>
> Funny you mention that, I was just looking into that yesterday.
>
> This seems to be in the front running:
>   http://lloyd.github.com/yajl/

The conclusion that I reached on this subject was that both XML and
JSON are poorly suited to streaming use cases for large datasets.  Try
implementing XMPP "framing" some time and tell me afterwards how much
you love SAX.

I prefer CSV or lots of small objects.

From mnot@mnot.net  Sat Aug  4 10:01:49 2012
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9D5A21F87AD; Sat,  4 Aug 2012 10:01:49 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ssg+UBU6fHyL; Sat,  4 Aug 2012 10:01:49 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 2D8C321F8535; Sat,  4 Aug 2012 10:01:49 -0700 (PDT)
Received: from [10.130.10.92] (unknown [166.147.79.205]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id A554C22DD6D; Sat,  4 Aug 2012 13:01:42 -0400 (EDT)
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com> <CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com> <CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com> <501AA9DF.6010208@raszuk.net> <EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com> <501AB4F5.7030205@raszuk.net> <501AC2C7.6040707@gmail.com> <270DDF46-AA04-49C0-B54C-35FD0AE0350F@mnot.net> <01OIMHY7BVKK0006TF@mauve.mrochek.com> <8D242074-DA5B-4C31-807D-79116517A64D@mnot.net> <01OIMJ1NAB5W0006TF@mauve.mrochek.com> <1D580354-3D3D-424B-8DE8-C5C436E8B14D@mnot.net> <CABkgnnXRu6c7RpJQoMEL8zW_=6ySM_-1Uato2GubnWtgEd=H8A@mail.gmail.com>
In-Reply-To: <CABkgnnXRu6c7RpJQoMEL8zW_=6ySM_-1Uato2GubnWtgEd=H8A@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <620454C2-9023-4364-9C04-97B2058D2D36@mnot.net>
X-Mailer: iPhone Mail (9B206)
From: Mark Nottingham <mnot@mnot.net>
Subject: Re: Basic ietf process question ...
Date: Sat, 4 Aug 2012 12:01:41 -0500
To: Martin Thomson <martin.thomson@gmail.com>
Cc: "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>, "opsawg@ietf.org" <opsawg@ietf.org>, Ned Freed <ned.freed@mrochek.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Aug 2012 17:01:50 -0000

Probably digressing here (from our previous digression), but I find a hybrid=
 API best. E.g., the python pulldom API, which is event driven until you fin=
d a node you're interested in, whereupon it can give you an object.=20

Should be even easier with json, since it can just give back a data structur=
e.=20

Sent from my iPhone

On 04/08/2012, at 11:26 AM, Martin Thomson <martin.thomson@gmail.com> wrote:=


> On 4 August 2012 08:52, Mark Nottingham <mnot@mnot.net> wrote:
>>> The other interesting case is where large amounts of data arrive in a st=
ream.
>>> SAX and SAX-like libraries makes this easy to implement with XML. I hope=

>>> there's an equivalent for Json; if not there needs to be.
>>=20
>> Funny you mention that, I was just looking into that yesterday.
>>=20
>> This seems to be in the front running:
>>  http://lloyd.github.com/yajl/
>=20
> The conclusion that I reached on this subject was that both XML and
> JSON are poorly suited to streaming use cases for large datasets.  Try
> implementing XMPP "framing" some time and tell me afterwards how much
> you love SAX.
>=20
> I prefer CSV or lots of small objects.

From hsantos@isdg.net  Sat Aug  4 10:04:26 2012
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EB3921F87F1 for <ietf@ietfa.amsl.com>; Sat,  4 Aug 2012 10:04:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.586
X-Spam-Level: 
X-Spam-Status: No, score=-102.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 47r3BGOo4ePx for <ietf@ietfa.amsl.com>; Sat,  4 Aug 2012 10:04:25 -0700 (PDT)
Received: from dkim.winserver.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id EDC4421F8535 for <ietf@ietf.org>; Sat,  4 Aug 2012 10:04:24 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=3054; t=1344099855; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:Subject:To: List-ID; bh=oSl+YetAikfdYKrhZAXLYC0tJtU=; b=SJPitUvXLgamAT1+3oZe 00noLgqTzFUtMkevm7aFxKhfwQjCe1Ftdo8qXphBQ9xcs7GmGkXZ3vAvnuIo9LPI rATQTptC4C7AX+NgzavxYXktJm3firyJpY5ni+sTlMnlGhUs0dMIiAIGQAvLJ7hN 2SRZJjT21wOeLm9TbKXyMhg=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 04 Aug 2012 13:04:15 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 121670524.8257.968; Sat, 04 Aug 2012 13:04:14 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=3054; t=1344099696; h=Received:Received: Message-ID:Date:From:Organization:Subject:To:List-ID; bh=2Gm2Aay /3X/arQfTGwHErTqgKc0pVIHKmXMBY13lnH8=; b=OuGY7jYCQ77jFkoz1X6Em8e X5Z/ultgl35S4rKmaxsFnSPm39oG/n0mh5fvA5vPCsE1DUdh0m8ukPRBG0L7sbt8 PwNnUwGJcWmnoifbyZ29f97xSsKYaPuUZGyzTsUQyuj2CBOCfXAtTPm2vWi1hXyI DfVhYZKyjZ9yNd/K6Lfw=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 04 Aug 2012 13:01:36 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 720493911.9.3332; Sat, 04 Aug 2012 13:01:35 -0400
Message-ID: <501D560F.7030206@isdg.net>
Date: Sat, 04 Aug 2012 13:04: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
CC: "ietf@ietf.org list" <ietf@ietf.org>
Subject: Re: Basic ietf process question ...
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com>	<CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com>	<CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com>	<501AA9DF.6010208@raszuk.net>	<EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com>	<501AB4F5.7030205@raszuk.net> <501AC2C7.6040707@gmail.com>	<270DDF46-AA04-49C0-B54C-35FD0AE0350F@mnot.net>	<01OIMHY7BVKK0006TF@mauve.mrochek.com>	<8D242074-DA5B-4C31-807D-79116517A64D@mnot.net>	<01OIMJ1NAB5W0006TF@mauve.mrochek.com>	<1D580354-3D3D-424B-8DE8-C5C436E8B14D@mnot.net> <CABkgnnXRu6c7RpJQoMEL8zW_=6ySM_-1Uato2GubnWtgEd=H8A@mail.gmail.com>
In-Reply-To: <CABkgnnXRu6c7RpJQoMEL8zW_=6ySM_-1Uato2GubnWtgEd=H8A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Comment: Missing recipient address appended by wcSMTP router.
To: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Aug 2012 17:04:26 -0000

Martin Thomson wrote:
> On 4 August 2012 08:52, Mark Nottingham <mnot@mnot.net> wrote:
>>> The other interesting case is where large amounts of data arrive in a stream.
>>> SAX and SAX-like libraries makes this easy to implement with XML. I hope
>>> there's an equivalent for Json; if not there needs to be.
>> Funny you mention that, I was just looking into that yesterday.
>>
>> This seems to be in the front running:
>>   http://lloyd.github.com/yajl/
> 
> The conclusion that I reached on this subject was that both XML and
> JSON are poorly suited to streaming use cases for large datasets.  Try
> implementing XMPP "framing" some time and tell me afterwards how much
> you love SAX.
> 
> I prefer CSV or lots of small objects.

+1, too much overhead, cries/needs for compiling and p-coding it comes 
in.  But it depends much on how much dynamic vs static data is 
involved in the application.  For on the fly dynamic processing, too 
much overhead and relaxing on strong syntaxing (i.e. allow for 
errors). Of course, thats getting cheaper these day.  One other issue, 
at least for us, to make it more useful, more layers will be needed. 
So this library may be great, but not for the layman to use. It will 
good for the systems level people to write the high layers tools (for 
application developers) perhaps.  That has been the dearth for many 
vendors who have to interface with different flavored APIs.  Single 
sourcing it is a strategic benefit for many which means having to 
write/port/convert the libraries into other languages.

Regarding the XML related question for IETF processing, well, the way 
I look at it is document writing should not involved requiring XML 
knowledge. Its already complex and it gets even more complex with XML 
Schemas, so its the last thing I want to spend time learning, 
relearning or refreshing on on.   But for usage as a tools to help 
IETF processors, management, perhaps, in what is essentially a static 
application it probably ok and keeps up with a direction in using XML 
for all things static (and even dynamic, not always the best result). 
It can help with I/O Communications, perhaps decentralization areas, a 
bunch of things once a common format is used.  But lets not require 
document writers having to know XML and XML schema just to be involved 
and productive with the IETF.

PS: For XML processing, we use the super light weight PUGXML C/C++ 
code in many areas

http://www.codeproject.com/Articles/3502/PugXML-A-Small-Pugnacious-XML-Parser

For JSON, well, thus far, we only needed it for web clients and 
javascript applets, and javascript is naturally JSON.  For the server 
side, I am probably going to relook at V8 again (googles stuff) which 
is also used for Chrome.

http://en.wikipedia.org/wiki/V8_(JavaScript_engine)

The nice thing I felt was the ability to built on top of it, new 
layers, language independent imports and more importantly, JIT "Just 
in time" pcode compiling/processing which is how Chrome gets its 
Javascripting speed from.

-- 
HLS



From ned+ietf@mauve.mrochek.com  Sat Aug  4 11:57:34 2012
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 4677121F86C9 for <ietf@ietfa.amsl.com>; Sat,  4 Aug 2012 11:57:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.505
X-Spam-Level: 
X-Spam-Status: No, score=-2.505 tagged_above=-999 required=5 tests=[AWL=0.094,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EPlcN6UqR91a for <ietf@ietfa.amsl.com>; Sat,  4 Aug 2012 11:57:34 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id D24EA21F86C6 for <ietf@ietf.org>; Sat,  4 Aug 2012 11:57:33 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OINK3SF7JK006G56@mauve.mrochek.com> for ietf@ietf.org; Sat, 4 Aug 2012 11:54:56 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OIGH28IS2O0006TF@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sat, 4 Aug 2012 11:54:53 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OINK3QSJXO0006TF@mauve.mrochek.com>
Date: Sat, 04 Aug 2012 11:54:39 -0700 (PDT)
Subject: Re: Basic ietf process question ...
In-reply-to: "Your message dated Sat, 04 Aug 2012 10:52:37 -0500" <1D580354-3D3D-424B-8DE8-C5C436E8B14D@mnot.net>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com> <CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com> <CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com> <501AA9DF.6010208@raszuk.net> <EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com> <501AB4F5.7030205@raszuk.net> <501AC2C7.6040707@gmail.com> <270DDF46-AA04-49C0-B54C-35FD0AE0350F@mnot.net> <01OIMHY7BVKK0006TF@mauve.mrochek.com> <8D242074-DA5B-4C31-807D-79116517A64D@mnot.net> <01OIMJ1NAB5W0006TF@mauve.mrochek.com> <1D580354-3D3D-424B-8DE8-C5C436E8B14D@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
Cc: ned+ietf@mauve.mrochek.com, opsawg@ietf.org, Ned Freed <ned.freed@mrochek.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Aug 2012 18:57:34 -0000

> On 03/08/2012, at 8:09 PM, ned+ietf@mauve.mrochek.com wrote:

> >> Very much; when it becomes a "document" (e.g., mixed markup), XML is a much
> >> better choice.
> >
> > The other interesting case is where large amounts of data arrive in a stream.
> > SAX and SAX-like libraries makes this easy to implement with XML. I hope
> > there's an equivalent for Json; if not there needs to be.

> Funny you mention that, I was just looking into that yesterday.

> This seems to be in the front running:
>   http://lloyd.github.com/yajl/

This looks promising. Thanks for the pointer.

				Ned




From mcr+ietf@sandelman.ca  Sat Aug  4 13:06:20 2012
Return-Path: <mcr+ietf@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 DB0CC21F87CC for <ietf@ietfa.amsl.com>; Sat,  4 Aug 2012 13:06:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.111
X-Spam-Level: 
X-Spam-Status: No, score=-1.111 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Itha31m2JZ7a for <ietf@ietfa.amsl.com>; Sat,  4 Aug 2012 13:06:18 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 62B7021F877E for <ietf@ietf.org>; Sat,  4 Aug 2012 13:06:14 -0700 (PDT)
Received: from obiwan.sandelman.ca (unknown [IPv6:2607:f0b0:f:2:3a60:77ff:fe38:e647]) by tuna.sandelman.ca (Postfix) with ESMTP id 689C42016C for <ietf@ietf.org>; Sat,  4 Aug 2012 16:18:47 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf list <ietf@ietf.org>
Subject: Re: Meeting "lounges" at IETF meetings
In-Reply-To: <CAHBDyN45juuW65z0ErSxPTB98_J2ZfZ9H9ah4JA6VaVe=uHVmw@mail.gmail.com>
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org> <CAHBDyN6VaL3fgYe+C+o9d93VZ1bR_EDmrPN7-Sv+7BiJ9+Q9AA@mail.gmail.com> <345BE467-B3CA-41EE-9577-6985E3555C8A@vpnc.org> <CAHBDyN45juuW65z0ErSxPTB98_J2ZfZ9H9ah4JA6VaVe=uHVmw@mail.gmail.com>
X-Mailer: MH-E 8.3; nmh 1.5; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Sat, 04 Aug 2012 16:06:08 -0400
Message-ID: <13849.1344110768@obiwan.sandelman.ca>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Aug 2012 20:06:20 -0000

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


>>>>> "Mary" =3D=3D Mary Barnes <mary.ietf.barnes@gmail.com> writes:
    Mary> [MB] Yes, I know it's not at all a popular idea (to reduce
    Mary> cookies), BUT we have had adequate space at previous meetings
    Mary> for which we paid the same meeting fee, so it seems possible
    Mary> to get space without increasing meeting fees (and I thought

Actually, we were over supplied with cookies, as there were always some
left over, I observed.  Perhaps it was the inability to move around
meant that people couldn't find the cookies.=20

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


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

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

iQCVAwUAUB2Ar4qHRg3pndX9AQIbaAP/Shbw2lcHc60n+WmD0dsFn8ss5Y1X7Y5w
MAr0hOR0VJ2vxOjT4jScGOy39tNxQtqUUXyCPLg8XpEyX5dAtUq/4H4jyBeLeVhp
18Txe8PMcw4NU8iMFkm0YXhgOOhr00U4HdU+C7kl2g8pA4KSguspvaoEWTL7ntD5
roLWZfUFRAc=
=mVhS
-----END PGP SIGNATURE-----
--=-=-=--

From dhc@dcrocker.net  Sat Aug  4 13:32:04 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C21B721F87E0 for <ietf@ietfa.amsl.com>; Sat,  4 Aug 2012 13:32:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KthNeZcZAR9r for <ietf@ietfa.amsl.com>; Sat,  4 Aug 2012 13:32:03 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id CC46921F87BD for <ietf@ietf.org>; Sat,  4 Aug 2012 13:32:03 -0700 (PDT)
Received: from [10.71.8.181] ([67.21.202.20]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q74KVwhn024965 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 4 Aug 2012 13:31:59 -0700
Message-ID: <501D86B5.9060404@dcrocker.net>
Date: Sat, 04 Aug 2012 13:31:49 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: James Polk <jmpolk@cisco.com>
Subject: management granularity  (Re: Meeting "lounges" at IETF meetings)
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org> <CAHBDyN6VaL3fgYe+C+o9d93VZ1bR_EDmrPN7-Sv+7BiJ9+Q9AA@mail.gmail.com> <m2ipczu5mu.wl%randy@psg.com> <42D7895B-8949-41FF-AE5B-0C9B813CEE8C@mnot.net> <m2d337u3fc.wl%randy@psg.com> <20104150-FCF4-4914-8656-72FFC9BA94AA@lucidvision.com> <CAHBDyN63_r2TEf7h81r9NYnQbdriC9Ztr-cT7vapO0uyRYB5_w@mail.gmail.com> <alpine.OSX.2.01.1208031505550.16675@173-11-110-132-sfba.hfc.comcastbusiness.net> <201208032240.q73Mc6OY008678@mtv-core-1.cisco.com>
In-Reply-To: <201208032240.q73Mc6OY008678@mtv-core-1.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]); Sat, 04 Aug 2012 13:32:01 -0700 (PDT)
Cc: Mark Nottingham <mnot@mnot.net>, Ole Jacobsen <ole@cisco.com>, ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Aug 2012 20:32:04 -0000

Folks,


On 8/3/2012 3:38 PM, James Polk wrote:
> Having missed only 2 meetings in 13 years, I can say that no venue was
> perfect, but some were very good. It becomes a case of which venues have
> the fewest "bad" things.
...
> The crowded hallway we can't change.
>
> We can change where the snacks are served, and I have read that will
> happen for our next meeting in Vancouver here in 15 months.


Long before I started serving on the IAOC (last year) it was clear to me 
that the Secretariat & related staff knew/knows how to do their job, 
both in terms of planning and in terms of fixing problems.  My opinion 
hasn't changed in the last year.  Well actually that's not quite true. 
They seem to be a bit better than I thought...

It's not that a occasional suggestions are sure to be entirely 
unnecessary, it's that most of them are... (So, was it wrong that I felt 
a tiny glow of satisfaction at seeing a sign appear about a half-hour 
after suggesting it to them, at the beginning of the week?)


On the other hand, there's a macro-management point that /does/ need to 
fall within the community purview:

      Should we constantly seek new venues or should we prefer returning 
to a small set of them?


The tendency for the last 20 years has been to seek new venues quite 
often.  Our rate of returning has been relatively low.  That means that 
most meeting venues are unfamiliar and run the risk of some serious, 
unforseen problem.  And my own observation was that we have tended to 
suffer roughly one major venue problem a year.

Visiting familiar places means that a) we know the tradeoffs at a place, 
and b) we can tune our use of it.  Visiting new places means we can find 
/better/ places to return to, albeit while also finding worse.  Locking 
down on on a fixed set of venues means we miss these improvements. 
(It's also been noted that returning regularly often tends to get 
degraded performance over time.)

However the tendency of the community has been to express preference for 
the tourism of going to new places.

If we really want venues to function towards some ideal, we need the 
benefit of a multi-visit learning curve.

And it means we stop being tourists.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From jason_livingood@cable.comcast.com  Sat Aug  4 16:24:09 2012
Return-Path: <jason_livingood@cable.comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA5BB21F86C5 for <ietf@ietfa.amsl.com>; Sat,  4 Aug 2012 16:24:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.908
X-Spam-Level: 
X-Spam-Status: No, score=-101.908 tagged_above=-999 required=5 tests=[AWL=-1.011, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qs8A+afT43ZF for <ietf@ietfa.amsl.com>; Sat,  4 Aug 2012 16:24:09 -0700 (PDT)
Received: from cable.comcast.com (pacdcavout01.cable.comcast.com [69.241.43.119]) by ietfa.amsl.com (Postfix) with ESMTP id 4F9E421F86CB for <ietf@ietf.org>; Sat,  4 Aug 2012 16:24:09 -0700 (PDT)
Received: from ([24.40.56.116]) by pacdcavout01.cable.comcast.com with ESMTP  id 97wm3m1.21863219; Sat, 04 Aug 2012 19:19:59 -0400
Received: from PACDCEXMB06.cable.comcast.com ([169.254.8.184]) by pacdcexhub03.cable.comcast.com ([fe80::5527:6d6b:29a7:f414%13]) with mapi id 14.02.0309.002; Sat, 4 Aug 2012 19:24:01 -0400
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>, James Polk <jmpolk@cisco.com>
Subject: Re: management granularity  (Re: Meeting "lounges" at IETF meetings)
Thread-Topic: management granularity  (Re: Meeting "lounges" at IETF meetings)
Thread-Index: AQHNcoBVDVEnWSFMrEu+WcHSn0GARJdKGSeA
Date: Sat, 4 Aug 2012 23:24:00 +0000
Message-ID: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com>
In-Reply-To: <501D86B5.9060404@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.2.120421
x-originating-ip: [24.40.55.72]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8A9B5FF1E3DB9947805586BA7A3A46E2@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Mark Nottingham <mnot@mnot.net>, Ole Jacobsen <ole@cisco.com>, ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Aug 2012 23:24:10 -0000

On 8/4/12 1:31 PM, "Dave Crocker" <dhc@dcrocker.net> wrote:

>However the tendency of the community has been to express preference for
>the tourism of going to new places.
>
>If we really want venues to function towards some ideal, we need the
>benefit of a multi-visit learning curve.
>
>And it means we stop being tourists.

Of course holding meetings in a range of locations, some new, also
provides the opportunity to attract new meeting hosts rather than relying
on a small pool of regular hosts. Ultimately, there are pros and cons to
either model and the current model does not seem especially bad (quite the
contrary I think).

And, as they say, 'variety is the spice of life'. ;-)

Perhaps when we the Internet is less dynamic (I hope it is never so) we
could meet in just one city all the time, as I understand some other
standards development group does. ;-)

Jason


From mnot@mnot.net  Sat Aug  4 16:32:08 2012
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE00021F876A; Sat,  4 Aug 2012 16:32: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=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WnwXmKWcz1Lt; Sat,  4 Aug 2012 16:32:07 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id BD1CB21F8670; Sat,  4 Aug 2012 16:32:07 -0700 (PDT)
Received: from [172.16.42.7] (unknown [72.177.241.155]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 1470322E1EB; Sat,  4 Aug 2012 19:32:00 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: Basic ietf process question ...
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <01OINK3QSJXO0006TF@mauve.mrochek.com>
Date: Sat, 4 Aug 2012 18:32:01 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <E18F8A22-25FC-4044-B5CA-C99EAA7BDF97@mnot.net>
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com> <CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com> <CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com> <501AA9DF.6010208@raszuk.net> <EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com> <501AB4F5.7030205@raszuk.net> <501AC2C7.6040707@gmail.com> <270DDF46-AA04-49C0-B54C-35FD0AE0350F@mnot.net> <01OIMHY7BVKK0006TF@mauve.mrochek.com> <8D242074-DA5B-4C31-807D-79116517A64D@mnot.net> <01OIMJ1NAB5W0006TF@mauve.mrochek.com> <1D580354-3D3D-424B-8DE8-C5C436E8B14D@mnot.net> <01OINK3QSJXO0006TF@mauve.mrochek.com>
To: Ned Freed <ned.freed@mrochek.com>
X-Mailer: Apple Mail (2.1485)
Cc: ned+ietf@mauve.mrochek.com, opsawg@ietf.org, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Aug 2012 23:32:08 -0000

Forwarding a couple more:
  http://wiki.fasterxml.com/JacksonHome
  http://argo.sourceforge.net/

Cheers,


On 04/08/2012, at 1:54 PM, Ned Freed <ned.freed@mrochek.com> wrote:

>=20
>> On 03/08/2012, at 8:09 PM, ned+ietf@mauve.mrochek.com wrote:
>=20
>>>> Very much; when it becomes a "document" (e.g., mixed markup), XML =
is a much
>>>> better choice.
>>>=20
>>> The other interesting case is where large amounts of data arrive in =
a stream.
>>> SAX and SAX-like libraries makes this easy to implement with XML. I =
hope
>>> there's an equivalent for Json; if not there needs to be.
>=20
>> Funny you mention that, I was just looking into that yesterday.
>=20
>> This seems to be in the front running:
>>  http://lloyd.github.com/yajl/
>=20
> This looks promising. Thanks for the pointer.
>=20
> 				Ned
>=20
>=20
>=20

--
Mark Nottingham
http://www.mnot.net/





From mcr@sandelman.ca  Fri Aug  3 11:49:49 2012
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 0C56E21F8E23 for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 11:49:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7GEIm8oHUODs for <ietf@ietfa.amsl.com>; Fri,  3 Aug 2012 11:49:48 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 2D4CE21F8E2B for <ietf@ietf.org>; Fri,  3 Aug 2012 11:49:41 -0700 (PDT)
Received: from [IPV6:2001:df8:0:16:5487:487d:3852:4fce] (unknown [IPv6:2001:df8:0:16:5487:487d:3852:4fce]) by tuna.sandelman.ca (Postfix) with ESMTPSA id 9F0422016C; Fri,  3 Aug 2012 15:02:09 -0400 (EDT)
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org>
User-Agent: K-9 Mail for Android
In-Reply-To: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----2TFF49ST8CR2X26PTLWF7DPQDGRMXM"
Subject: Re: Meeting "lounges" at IETF meetings
From: Michael Richardson {quigon} <mcr@sandelman.ca>
Date: Fri, 03 Aug 2012 11:49:35 -0700
To: Paul Hoffman <paul.hoffman@vpnc.org>,ietf list <ietf@ietf.org>
Message-ID: <342151eb-28c7-43ae-b4dc-f9bd69be37cd@email.android.com>
X-Mailman-Approved-At: Sat, 04 Aug 2012 17:44:50 -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, 03 Aug 2012 18:49:49 -0000

------2TFF49ST8CR2X26PTLWF7DPQDGRMXM
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 8bit

I agree with having the terminal room... let's get some signs on the stairs to the fourth floor when we return.
When we return fall 2013, can we move all the break food into the space at the top of the escalator, away from the doors in/out of Regency.
Let's also get a few more couches around the place... the Quebec 2011 big room was awesome, in hindsight.

-- 
Sent from my Android tablet.

Paul Hoffman <paul.hoffman@vpnc.org> wrote:

Greetings again. Some meeting venues have had insufficient places where five or so people could comfortably gather for informal meetings, while other venues did this just fine. One proposal has been that the Secretariat reserve large rooms for this. Unfortunately, that adds significant cost to the meetings.

Instead, I propose that we simply designate the terminal room (which is already reserved for future meetings) be designated as meeting areas where talking is allowed / encouraged. Earplugs could be provided for people who really want a quiet Ethernet connection; the cost of those for the Secretariat will be about $25/meeting.

--Paul Hoffman


------2TFF49ST8CR2X26PTLWF7DPQDGRMXM
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: 8bit

<html><head></head><body>I agree with having the terminal room... let&#39;s get some signs on the stairs to the fourth floor when we return.<br>
When we return fall 2013, can we move all the break food into the space at the top of the escalator, away from the doors in/out of Regency.<br>
Let&#39;s also get a few more couches around the place... the Quebec 2011 big room was awesome, in hindsight.<br>
<br>
-- <br>
Sent from my Android tablet.<br><br><div class="gmail_quote">Paul Hoffman &lt;paul.hoffman@vpnc.org&gt; wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre style="white-space: pre-wrap; word-wrap:break-word; font-family: sans-serif">Greetings again. Some meeting venues have had insufficient places where five or so people could comfortably gather for informal meetings, while other venues did this just fine. One proposal has been that the Secretariat reserve large rooms for this. Unfortunately, that adds significant cost to the meetings.<br /><br />Instead, I propose that we simply designate the terminal room (which is already reserved for future meetings) be designated as meeting areas where talking is allowed / encouraged. Earplugs could be provided for people who really want a quiet Ethernet connection; the cost of those for the Secretariat will be about $25/meeting.<br /><br />--Paul Hoffman</pre></blockquote></div></body></html>
------2TFF49ST8CR2X26PTLWF7DPQDGRMXM--


From dworley@avaya.com  Sat Aug  4 18:28:53 2012
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 BBAF121F8817 for <ietf@ietfa.amsl.com>; Sat,  4 Aug 2012 18:28:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.248
X-Spam-Level: 
X-Spam-Status: No, score=-103.248 tagged_above=-999 required=5 tests=[AWL=0.351, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZNJG4a6xLtnO for <ietf@ietfa.amsl.com>; Sat,  4 Aug 2012 18:28:53 -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 ECEBC21F87EE for <ietf@ietf.org>; Sat,  4 Aug 2012 18:28:52 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAETLHVDGmAcF/2dsb2JhbABFuT2BB4IgAQEBAQIBEigyCggLAgEIDQghEDIlAQEEARIIGodlBp1ynCuRbmADm0aKD4J7
X-IronPort-AV: E=Sophos;i="4.77,714,1336363200"; d="scan'208";a="318556276"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 04 Aug 2012 21:24:05 -0400
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by co300216-co-erhwest-out.avaya.com with ESMTP; 04 Aug 2012 21:24:10 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Sat, 4 Aug 2012 21:28:49 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, ietf list <ietf@ietf.org>
Date: Sat, 4 Aug 2012 21:25:38 -0400
Subject: RE: Meeting "lounges" at IETF meetings
Thread-Topic: Meeting "lounges" at IETF meetings
Thread-Index: Ac1xnBVo47+XzpduTrir5/r7eBwimwBDSKmy
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0BF6@DC-US1MBEX4.global.avaya.com>
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org>
In-Reply-To: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Aug 2012 01:28:53 -0000

> From: Paul Hoffman [paul.hoffman@vpnc.org]
>=20
> Instead, I propose that we simply designate the terminal room (which
> is already reserved for future meetings) be designated as meeting
> areas where talking is allowed / encouraged. Earplugs could be
> provided for people who really want a quiet Ethernet connection; the
> cost of those for the Secretariat will be about $25/meeting.

I agree with Mary here, we really don't want to turn the terminal room
into a talking room.

The problem with the earplug idea is that earplugs don't dampen human
voices to the point where they don't cause your brain to try to track
conversations, because earplugs uniformly cut the volume of both
voices and background noise.  Since your brain's audio processing
system has an excellent AGC (automatic gain control), the recognition
of voices is unimpaired.

Dale

From dworley@avaya.com  Sat Aug  4 18:37:09 2012
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 7D07821F882E for <ietf@ietfa.amsl.com>; Sat,  4 Aug 2012 18:37:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.256
X-Spam-Level: 
X-Spam-Status: No, score=-103.256 tagged_above=-999 required=5 tests=[AWL=0.343, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bsW63eQzLLRg for <ietf@ietfa.amsl.com>; Sat,  4 Aug 2012 18:37:09 -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 90A5C21F8828 for <ietf@ietf.org>; Sat,  4 Aug 2012 18:37:08 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAG/MHVDGmAcF/2dsb2JhbABFuT2BB4IgAQEBAQIBEigxDgULAgEIDQEHIRAyJQEBBA4FCBqHZQadcpwrkW5gA5tGig+Cew
X-IronPort-AV: E=Sophos;i="4.77,714,1336363200"; d="scan'208";a="318556692"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 04 Aug 2012 21:32:21 -0400
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by co300216-co-erhwest-out.avaya.com with ESMTP; 04 Aug 2012 21:32:26 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Sat, 4 Aug 2012 21:37:06 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Mark Nottingham <mnot@mnot.net>
Date: Sat, 4 Aug 2012 21:34:59 -0400
Subject: RE: Basic ietf process question ...
Thread-Topic: Basic ietf process question ...
Thread-Index: Ac1xoCIzv7OzK/YgQZOyNFu+lgjY1ABCmR5l
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0BF7@DC-US1MBEX4.global.avaya.com>
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com><CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com><CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com> <501AA9DF.6010208@raszuk.net> <EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com> <501AB4F5.7030205@raszuk.net> <501AC2C7.6040707@gmail.com>, <270DDF46-AA04-49C0-B54C-35FD0AE0350F@mnot.net>
In-Reply-To: <270DDF46-AA04-49C0-B54C-35FD0AE0350F@mnot.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Aug 2012 01:37:09 -0000

> From: Mark Nottingham [mnot@mnot.net]
>=20
> What surprises me and many others is that people are still using it
> and promoting it, when it's well-understood by almost EVERYONE who was
> involved in using XML for protocols in the past ten years agrees that
> it's a mistake.

It sounds to me like what is needed is some sort of "best common
practices" document regarding data aggregation and encoding, or even
perhaps an IETF Sunday tutorial.  Lots of people who are never going
to become experts in the field need to make good choices when
designing protocols...

Dale

From tbray@textuality.com  Sat Aug  4 20:06:07 2012
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F64121F8827 for <ietf@ietfa.amsl.com>; Sat,  4 Aug 2012 20:06:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.999
X-Spam-Level: 
X-Spam-Status: No, score=-4.999 tagged_above=-999 required=5 tests=[AWL=-2.022, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cZVeg2Rtrrwd for <ietf@ietfa.amsl.com>; Sat,  4 Aug 2012 20:06:06 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0111A21F8810 for <ietf@ietf.org>; Sat,  4 Aug 2012 20:06:05 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so2059326vcb.31 for <ietf@ietf.org>; Sat, 04 Aug 2012 20:06:05 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding:x-gm-message-state; bh=3sqD9PjPfa2mLH80JyJCiqsQEzCxOHtlTAHhsajXQBQ=; b=MXaBE3WXRGyh2tMhd9orMsIFvgoiQiFIwW1BXnxZFV0g8o8hS5aaLNXRjuv0Pd2exv C5M0hEHKgQIJo7WObPXo7QDUrSUJoRT+lmgVCVT7GT7Y9twkh+Al9oHrJDWkO5k2bFQS x9H6AFGfJDLQAaotVd5Ic2wjTdx8h3C1NwOX6VmB4lArc65V1jJh6eVvoxRYmAatNaW2 Qq1RJ8r/gr9f43rTGEEp4nFyXUZ/zVaD8eVrAxZoknug9l9M4FoubnAnXB0U5qJGMngr g3om2Q/g/mRVRobMpPXddfJEdvW4/Il63qDmNqwGh+LL/Ax+tOJmu4NwfDS/tDWnjAKW cR/w==
MIME-Version: 1.0
Received: by 10.220.219.129 with SMTP id hu1mr4994576vcb.72.1344135965267; Sat, 04 Aug 2012 20:06:05 -0700 (PDT)
Received: by 10.52.113.162 with HTTP; Sat, 4 Aug 2012 20:06:05 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A0BF7@DC-US1MBEX4.global.avaya.com>
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com> <CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com> <CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com> <501AA9DF.6010208@raszuk.net> <EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com> <501AB4F5.7030205@raszuk.net> <501AC2C7.6040707@gmail.com> <270DDF46-AA04-49C0-B54C-35FD0AE0350F@mnot.net> <CD5674C3CD99574EBA7432465FC13C1B22726A0BF7@DC-US1MBEX4.global.avaya.com>
Date: Sat, 4 Aug 2012 20:06:05 -0700
Message-ID: <CAHBU6ivbzi7UGovxAH2WmbbajY7rmah2Gt5coX+HVLL+KFL7YA@mail.gmail.com>
Subject: Re: Basic ietf process question ...
From: Tim Bray <tbray@textuality.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQknxMWQXwTnMPViVaA+rAbwTEquK9EGwuIYuz9j34DV80/3jYM4tZa0lP/OoixAT2j8G+7P
Cc: Mark Nottingham <mnot@mnot.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Aug 2012 03:06:07 -0000

I gave such a Sunday tutorial at IETF70.  The slides are here
(somewhat dated, but still useful I=92d say):
http://www.tbray.org/tmp/IETF70.pdf

 -Tim

On Sat, Aug 4, 2012 at 6:34 PM, Worley, Dale R (Dale) <dworley@avaya.com> w=
rote:
>> From: Mark Nottingham [mnot@mnot.net]
>>
>> What surprises me and many others is that people are still using it
>> and promoting it, when it's well-understood by almost EVERYONE who was
>> involved in using XML for protocols in the past ten years agrees that
>> it's a mistake.
>
> It sounds to me like what is needed is some sort of "best common
> practices" document regarding data aggregation and encoding, or even
> perhaps an IETF Sunday tutorial.  Lots of people who are never going
> to become experts in the field need to make good choices when
> designing protocols...
>
> Dale

From johnl@iecc.com  Sat Aug  4 20:55:27 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 596C921F86DC for <ietf@ietfa.amsl.com>; Sat,  4 Aug 2012 20:55:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.125
X-Spam-Level: 
X-Spam-Status: No, score=-111.125 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vmHN4jsZjzYh for <ietf@ietfa.amsl.com>; Sat,  4 Aug 2012 20:55:26 -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 7DACC21F85F9 for <ietf@ietf.org>; Sat,  4 Aug 2012 20:55:26 -0700 (PDT)
Received: (qmail 43975 invoked from network); 5 Aug 2012 03:55:25 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 5 Aug 2012 03:55:25 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=501deead.xn--hew.k1208; i=johnl@user.iecc.com; bh=B88YyiBx9u5crVhlVEsmNTgKUPVvaqiTmfpGdMGav38=; b=L4n5I7Hw3sXbu1ZWVyasjyT2PljRCv7lWxPFPsONKfeaZaMYgcxUY3B6QASbLeB8TInqmbhINPxH3ALADuse9amNN0ORTKBiTG0eiG+Cvd/hEMfMy/SxCx6hu12ejZxySS6A7u8i4f4YQF3PP3nTpSRzGV6AOWEQHL6hJW//Gvk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=501deead.xn--hew.k1208; olt=johnl@user.iecc.com; bh=B88YyiBx9u5crVhlVEsmNTgKUPVvaqiTmfpGdMGav38=; b=kUkQw2twh2GaD5jfvoBYNHRNSnnjlnzV2ezU+hwbVPACiPuv71wEatllTePVxuOBC55V7aPjhbusCIdzSyqemwu0Q70pTmd7yX749xtGb8mdD/1L/tnRChDExq8aqhJgHcVauRT0+tZKWBK/VCZBGEldP4jgSLbUGyQJ61IcELU=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 5 Aug 2012 03:55:03 -0000
Message-ID: <20120805035503.14051.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: management granularity  (Re: Meeting "lounges" at IETF meetings)
In-Reply-To: <501D86B5.9060404@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: Sun, 05 Aug 2012 03:55:27 -0000

>And it means we stop being tourists.

Depends where.  I would be happy to be a tourist in Vancouver, Quebec,
Paris (assuming we can sort out the Hotel Klepto issue), and/or Berlin
every year.

R's,
John

PS: But not Orlando.

From daniel.karrenberg@ripe.net  Sun Aug  5 06:29:28 2012
Return-Path: <daniel.karrenberg@ripe.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E27421F84DD for <ietf@ietfa.amsl.com>; Sun,  5 Aug 2012 06:29:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lJVnLVL01oHY for <ietf@ietfa.amsl.com>; Sun,  5 Aug 2012 06:29:27 -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 B894A21F84A7 for <ietf@ietf.org>; Sun,  5 Aug 2012 06:29:27 -0700 (PDT)
Received: from dodo.ripe.net ([193.0.23.4]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <daniel.karrenberg@ripe.net>) id 1Sy0tV-0001WN-Nr; Sun, 05 Aug 2012 15:29:23 +0200
Received: from baboon.ripe.net ([193.0.1.208] helo=[127.0.0.1]) by dodo.ripe.net with esmtps (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <daniel.karrenberg@ripe.net>) id 1Sy0tV-0004fx-Ga; Sun, 05 Aug 2012 15:29:21 +0200
Subject: Re: ITU-T Dubai Meeting
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Daniel Karrenberg <daniel.karrenberg@ripe.net>
In-Reply-To: <20120803182500.1F9512344DBF@drugs.dv.isc.org>
Date: Sun, 5 Aug 2012 15:29:21 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DF913BB3-90FD-4FFC-8B72-39E969009788@ripe.net>
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu> <CAMm+Lwg2HgO-=9ED4vbmO+Vf9r6bYPcLDgfyMAyPdEPVgRm4LQ@mail.gmail.com> <FB949BEA-5BDB-401A-8A75-E9A9BDAA72A6@ripe.net> <20120803182500.1F9512344DBF@drugs.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1278)
X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.48/RELEASE, bases: 20120425 #7816575, check: 20120805 clean
X-RIPE-Spam-Level: --
X-RIPE-Spam-Report: Spam Total Points:   -2.9 points pts rule name              description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 2cd422cf40ef1bab352b066641112beb2f114dcc787d6a4a757176f7111183b0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Aug 2012 13:29:28 -0000

On 03.08.2012, at 20:25, Mark Andrews wrote:

>>=20
>> IPv4 addresses used to be regarded as non-scarce not so long ago.
>=20
> I don't know what planet you have been living on but it was clear
> IPv4 addresses were a scarce resource 2+ decades ago longer than
> some IETF attendees have been alive.  IPv6 was started because they
> were a scarce resource that would run out in the foreseeable future.

I may have been too terse for some readers.  What I intended to point =
out is that the life time of address spaces has been underestimated more =
often than not, especially early on in their deployment. This is =
particularly true for network level addressing.  Arguments that =
"addresses are not scarce" in any finite address space should be judged =
in the light of this historic experience.

In other words: I expect that it will be not more than 20 years from now =
that we will hear cries of "Why were we so wasteful with IPv6 addresses =
in the beginning?" This is why I disagree with Phillip Hallam-Baker's =
opinion.

Daniel

PS: I have been living on Earth, the densest and fifth-largest of the =
eight planets in the Solar System. Personally I have been aware of the =
general state of the IPv4 address space since the 1980s and I have =
contributed towards making it last as long as it did; refer to RFC1597 =
(now RFC1918) of the year 1994 as an example.=

From randy@psg.com  Sun Aug  5 07:34:22 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8724121F84F1 for <ietf@ietfa.amsl.com>; Sun,  5 Aug 2012 07:34:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.547
X-Spam-Level: 
X-Spam-Status: No, score=-2.547 tagged_above=-999 required=5 tests=[AWL=0.052,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iAX+7KcrNHFg for <ietf@ietfa.amsl.com>; Sun,  5 Aug 2012 07:34:22 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 2F48421F84DD for <ietf@ietf.org>; Sun,  5 Aug 2012 07:34:22 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Sy1uK-000GXM-Rb; Sun, 05 Aug 2012 14:34:17 +0000
Date: Sun, 05 Aug 2012 07:34:16 -0700
Message-ID: <m2obmp9zmf.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Daniel Karrenberg <daniel.karrenberg@ripe.net>
Subject: Re: ITU-T Dubai Meeting
In-Reply-To: <DF913BB3-90FD-4FFC-8B72-39E969009788@ripe.net>
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu> <CAMm+Lwg2HgO-=9ED4vbmO+Vf9r6bYPcLDgfyMAyPdEPVgRm4LQ@mail.gmail.com> <FB949BEA-5BDB-401A-8A75-E9A9BDAA72A6@ripe.net> <20120803182500.1F9512344DBF@drugs.dv.isc.org> <DF913BB3-90FD-4FFC-8B72-39E969009788@ripe.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: Sun, 05 Aug 2012 14:34:22 -0000

> In other words: I expect that it will be not more than 20 years from
> now that we will hear cries of "Why were we so wasteful with IPv6
> addresses in the beginning?" This is why I disagree with Phillip
> Hallam-Baker's opinion.

<aol>

whatever the number of address bits, if it is fixed, we always run out.
memory addressing has been a cliff many times.  ip addressing.  ...

randy

From dcrocker@bbiw.net  Sun Aug  5 11:58:23 2012
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D33F21F8599 for <ietf@ietfa.amsl.com>; Sun,  5 Aug 2012 11:58:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.544
X-Spam-Level: 
X-Spam-Status: No, score=-6.544 tagged_above=-999 required=5 tests=[AWL=0.055,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OnU5H7dKYKy4 for <ietf@ietfa.amsl.com>; Sun,  5 Aug 2012 11:58:22 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id CCA6021F8559 for <ietf@ietf.org>; Sun,  5 Aug 2012 11:58:22 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q75IwIOL017441 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 5 Aug 2012 11:58:19 -0700
Message-ID: <501EC24B.4080709@bbiw.net>
Date: Sun, 05 Aug 2012 11:58:19 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
Subject: Re: management granularity  (Re: Meeting "lounges" at IETF meetings)
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com>
In-Reply-To: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sun, 05 Aug 2012 11:58:19 -0700 (PDT)
Cc: Mark Nottingham <mnot@mnot.net>, ietf list <ietf@ietf.org>, Ole Jacobsen <ole@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, 05 Aug 2012 18:58:23 -0000

On 8/4/2012 4:24 PM, Livingood, Jason wrote:
> On 8/4/12 1:31 PM, "Dave Crocker" <dhc@dcrocker.net> wrote:
>> If we really want venues to function towards some ideal, we need the
>> benefit of a multi-visit learning curve.
...
> Of course holding meetings in a range of locations, some new, also
> provides the opportunity to attract new meeting hosts rather than relying
> on a small pool of regular hosts. Ultimately, there are pros and cons to
> either model and the current model does not seem especially bad (quite the
> contrary I think).

My note highlighted some tradeoffs, and your note adds to that.  The 
main point is that choices among tradeoffs have very different effects, 
both desirable an not.

If the community wants venues to be reliably excellent, it's not enough 
merely to have excellent staff.  We need to go back to the better places 
and benefit from the learning curve.  This doesn't mean "no new venues" 
but it means fewer.

The influence of choosing sites based on hosts has, in my view, tended 
to work against these functional benefits.[1]  The counter, of course, 
is the benefit having a host can bring, most notably funds.


> Perhaps when we the Internet is less dynamic (I hope it is never so) we
> could meet in just one city all the time, as I understand some other
> standards development group does. ;-)

It's been amusing (not) to hear claims that the IETF needs to wander 
around the world for its meetings, for what is really a marketing 
campaign, to counter some of those other groups... who do indeed sit in 
one city for all of their formal meetings.

Moving around in order to spread the pain of travel among folks who 
actually do the work is one thing.  Moving around to improve public 
relations is quite another.



On 8/4/2012 8:55 PM, John Levine wrote:>> And it means we stop being 
tourists.
 >
 > Depends where.  I would be happy to be a tourist in Vancouver, Quebec,
 > Paris (assuming we can sort out the Hotel Klepto issue), and/or Berlin
 > every year.

Given the context and content of my note, I suspect that I was not 
referring to attendees' taking advantage of a venue's sightseeing 
opportunities, but rather to a possibly strategic orientation to choose 
different venues in order to /create/ tourism opportunities.  I might 
even have thought that I made the latter focus clear enough, but alas 
didn't word things to bullet-proof against creative misinterpretation.

Sorry.

d/


[1] Shortly before I joined the IAOC, an important paradigm change was 
instituted.  In the past, venues were primarily chosen /after/ getting a 
host, so the host could largely decide where to have the meeting. With 
some regularity, this produced extremely limited choices in sites. More 
recently, the model is to choose the venue and then seek a host.  This 
permits us to get a venue much sooner than we used to, which greatly 
improves our choice of meeting site.  While sometimes creating a greater 
challenge for finding a host, I think the newer paradigm is a vast 
improvement.

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From mnot@mnot.net  Sun Aug  5 12:26:24 2012
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0496521F851B for <ietf@ietfa.amsl.com>; Sun,  5 Aug 2012 12:26:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.932
X-Spam-Level: 
X-Spam-Status: No, score=-103.932 tagged_above=-999 required=5 tests=[AWL=-1.333, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sTDHRizlOFRm for <ietf@ietfa.amsl.com>; Sun,  5 Aug 2012 12:26:23 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 4D4B721F8512 for <ietf@ietf.org>; Sun,  5 Aug 2012 12:26:23 -0700 (PDT)
Received: from [10.10.1.125] (unknown [67.79.29.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id C29C6509EB; Sun,  5 Aug 2012 15:26:16 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: management granularity  (Re: Meeting "lounges" at IETF meetings)
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <501EC24B.4080709@bbiw.net>
Date: Sun, 5 Aug 2012 14:26:16 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <E4DA6495-E02F-4A47-9AA2-E47F260CF3C5@mnot.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net>
To: Dave Crocker <dcrocker@bbiw.net>
X-Mailer: Apple Mail (2.1485)
Cc: ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Aug 2012 19:26:24 -0000

On 05/08/2012, at 1:58 PM, Dave Crocker <dcrocker@bbiw.net> wrote:

> It's been amusing (not) to hear claims that the IETF needs to wander =
around the world for its meetings, for what is really a marketing =
campaign, to counter some of those other groups... who do indeed sit in =
one city for all of their formal meetings.
>=20
> Moving around in order to spread the pain of travel among folks who =
actually do the work is one thing. =20

So, let's talk about that.=20

I live in Melbourne, and thus must travel for more than 24 hours each =
way to just about every IETF meeting there is (the "asian" meetings are =
at best 16 hours away, but often more due to routing). Sometimes, much =
more.

Three or so locations doesn't spread the pain equitably.

> Moving around to improve public relations is quite another.


You say "public relations", I say it's to encourage participation from a =
wider range of people, so this doesn't become a self-selecting set of =
blowhards*. This is a primary condition for an organisation that aspires =
to set standards, not just a "marketing campaign".

Again, choosing three or so locations ignores large parts of not only =
the developing world (e.g., Africa, India), but also substantial =
portions of the developed world with a reasonable track record of =
participation (e.g., Australia, New Zealand, Brazil).

As much as I fear unleashing a mob of cookie-eating, hotel-complaining, =
detail-fixated, t-shirt wearing, difference-from-America-fearing, =
beard-wielding, restaurant-bill-splitting nerd-ninjas on my adopted =
country, I think there are very good selfish *and* unselfish reasons for =
the IETF returning to Australia, or appearing nearby. And going to =
Brazil or thereabouts, and India, and (eventually) Africa. Doesn't have =
to be every year, but once a decade+ is not often enough.

Regards,


* Well, more of one.

--
Mark Nottingham
http://www.mnot.net/





From agmalis@gmail.com  Sun Aug  5 12:36:22 2012
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3A9721F8518 for <ietf@ietfa.amsl.com>; Sun,  5 Aug 2012 12:36:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.26
X-Spam-Level: 
X-Spam-Status: No, score=-3.26 tagged_above=-999 required=5 tests=[AWL=0.339,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ogc3P76gN8mR for <ietf@ietfa.amsl.com>; Sun,  5 Aug 2012 12:36:21 -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 4BEE521F8517 for <ietf@ietf.org>; Sun,  5 Aug 2012 12:36:21 -0700 (PDT)
Received: by yhq56 with SMTP id 56so2122214yhq.31 for <ietf@ietf.org>; Sun, 05 Aug 2012 12:36:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Rd8CZqnoi0DS3v3l5MRtke8Kbm0xKXd4SL7end9B8KA=; b=ery/8kZm0zs5d5/x+I1QookOrEggTipJZw6JCmkzGxq38hSs37tfJxb0/8R3XuuQT2 K/l9iUl2zajI9se+6LCLIovWXpHdOXLuYtLty07R2BCkArrT9SmA67y311szFuKfvOhG KdDgDHeh5aigmzXoWVzYja0pLO7kMC8KcVz4E23GoR0n99QR1L2iuD+VGsiaPLxznlx8 lkuxJ6oQnzVnBmN9yl361a2y8ruRe8Z2cVBLAPWPVxHHp6i8a0GecHzB+rVzxRTOaI62 bLJWPg42Pfr382xP5F4hY3FhDWqr4qHUVmFJn6sNJrChlFHvxDdMaaspwqzrlHmmFRe+ 7SUw==
Received: by 10.50.161.131 with SMTP id xs3mr3590834igb.46.1344195380505; Sun, 05 Aug 2012 12:36:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.90.229 with HTTP; Sun, 5 Aug 2012 12:36:00 -0700 (PDT)
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A0BF6@DC-US1MBEX4.global.avaya.com>
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org> <CD5674C3CD99574EBA7432465FC13C1B22726A0BF6@DC-US1MBEX4.global.avaya.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Sun, 5 Aug 2012 15:36:00 -0400
Message-ID: <CAA=duU2MQK6sFoqHgH93uvj8DK_cE+eNzeYg8vm3f55isTzuqA@mail.gmail.com>
Subject: Re: Meeting "lounges" at IETF meetings
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Aug 2012 19:36:22 -0000

+1 on keeping the terminal room a (mostly) quiet work area.

Rather, let's replicate the Quebec large lounge space if possible (at
all upcoming meetings).

Cheers,
Andy

On Sat, Aug 4, 2012 at 9:25 PM, Worley, Dale R (Dale) <dworley@avaya.com> wrote:
>> From: Paul Hoffman [paul.hoffman@vpnc.org]
>>
>> Instead, I propose that we simply designate the terminal room (which
>> is already reserved for future meetings) be designated as meeting
>> areas where talking is allowed / encouraged. Earplugs could be
>> provided for people who really want a quiet Ethernet connection; the
>> cost of those for the Secretariat will be about $25/meeting.
>
> I agree with Mary here, we really don't want to turn the terminal room
> into a talking room.
>
> The problem with the earplug idea is that earplugs don't dampen human
> voices to the point where they don't cause your brain to try to track
> conversations, because earplugs uniformly cut the volume of both
> voices and background noise.  Since your brain's audio processing
> system has an excellent AGC (automatic gain control), the recognition
> of voices is unimpaired.
>
> Dale

From sm@resistor.net  Sun Aug  5 19:02:01 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB98221F8532 for <ietf@ietfa.amsl.com>; Sun,  5 Aug 2012 19:02:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TIZJL8caLbyh for <ietf@ietfa.amsl.com>; Sun,  5 Aug 2012 19:01:59 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id B1B6421F853F for <ietf@ietf.org>; Sun,  5 Aug 2012 19:01:59 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q7621qgG008810; Sun, 5 Aug 2012 19:01:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1344218518; bh=S7AbIV62pnlLtUG5hcTBfHn/MEsFR2U+CWIgPDCaNis=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=VFBhlUu+xogJ9KZPvZ6xjM2S4/pdLMrOWhKVTv73lUAOzDhLWHcnAxitOysisjOdr 3V9SDn+s+ytNG0uWtN05pS8IqHpvPqquHiINJUzVqYRjfdVMo/0Fo2mfycxa6lbDoM /FMiXd+PVdSVK8vlB4fyx4nyOlNtz/e9huZE5uFs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1344218518; i=@resistor.net; bh=S7AbIV62pnlLtUG5hcTBfHn/MEsFR2U+CWIgPDCaNis=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=cUW2psrAQye/s38lMzaAMLJRhJI5aqf4F/+lmyd67rOcytw+7qHuneGa1YrORaDd6 7DLMHRf29buInP5QYOpANjI3pLiq6gKsmU4X8Mr3B+TGBGIv/nmIhym0d3YrP2/LOH J3cHutpCKgw7VmuL5YTKqqW6aM76JozSQ0LCZShg=
Message-Id: <6.2.5.6.2.20120805165716.07820120@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 05 Aug 2012 18:54:49 -0700
To: Mark Nottingham <mnot@mnot.net>
From: SM <sm@resistor.net>
Subject: Re: management granularity  (Re: Meeting "lounges" at IETF meetings)
In-Reply-To: <E4DA6495-E02F-4A47-9AA2-E47F260CF3C5@mnot.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <E4DA6495-E02F-4A47-9AA2-E47F260CF3C5@mnot.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Aug 2012 02:02:02 -0000

Hi Mark,
At 12:26 05-08-2012, Mark Nottingham wrote:
>I live in Melbourne, and thus must travel for more than 24 hours 
>each way to just about every IETF meeting there is (the "asian" 
>meetings are at best 16 hours away, but often more due to routing). 
>Sometimes, much more.

And yet I don't see you complaining about that. :-)  The good news is 
that the IAOC decided to have a meeting in the Southern 
Hemisphere.  The bad news is that it may not be in Melbourne.

>You say "public relations", I say it's to encourage participation 
>from a wider range of people, so this doesn't become a 
>self-selecting set of blowhards*. This is a primary condition for an 
>organisation that aspires to set standards, not just a "marketing campaign".

Yes.

>Again, choosing three or so locations ignores large parts of not 
>only the developing world (e.g., Africa, India), but also 
>substantial portions of the developed world with a reasonable track 
>record of participation (e.g., Australia, New Zealand, Brazil).

There were 10 participants from Australia and 4 participants from New 
Zealand at the last IETF meeting.  There was interest to have the 
IETF in New Zealand.  I guess that it was considered as difficult to 
convince the cookie-eating mob that it was a good location.

>As much as I fear unleashing a mob of cookie-eating, 
>hotel-complaining, detail-fixated, t-shirt wearing, 
>difference-from-America-fearing, beard-wielding, 
>restaurant-bill-splitting nerd-ninjas on my adopted country, I think 
>there are very good selfish *and* unselfish

:-)

>  reasons for the IETF returning to Australia, or appearing nearby. 
> And going to Brazil or thereabouts, and India, and (eventually) 
> Africa. Doesn't have to be every year, but once a decade+ is not often enough.

The IETF will likely go to Latin America first.  My guess is that it 
might eventually go to India.  If it ever goes to Africa it will be 
more of a political statement than anything else.

Regards,
-sm 


From smb@cs.columbia.edu  Sun Aug  5 20:30:44 2012
Return-Path: <smb@cs.columbia.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5533821F8514 for <ietf@ietfa.amsl.com>; Sun,  5 Aug 2012 20:30:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KuasNzzXCEB9 for <ietf@ietfa.amsl.com>; Sun,  5 Aug 2012 20:30:43 -0700 (PDT)
Received: from tarap.cc.columbia.edu (tarap.cc.columbia.edu [128.59.29.7]) by ietfa.amsl.com (Postfix) with ESMTP id 4131D21F84A6 for <ietf@ietf.org>; Sun,  5 Aug 2012 20:30:43 -0700 (PDT)
Received: from [10.9.0.14] (fireball.cs.columbia.edu [128.59.13.10]) (user=smb2132 mech=PLAIN bits=0) by tarap.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id q763UcA3013217 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 5 Aug 2012 23:30:39 -0400 (EDT)
Subject: Re: ITU-T Dubai Meeting
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <m2obmp9zmf.wl%randy@psg.com>
Date: Sun, 5 Aug 2012 20:30:39 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <DBC678C7-7C9C-4B47-A396-317D62AF82F5@cs.columbia.edu>
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu> <CAMm+Lwg2HgO-=9ED4vbmO+Vf9r6bYPcLDgfyMAyPdEPVgRm4LQ@mail.gmail.com> <FB949BEA-5BDB-401A-8A75-E9A9BDAA72A6@ripe.net> <20120803182500.1F9512344DBF@drugs.dv.isc.org> <DF913BB3-90FD-4FFC-8B72-39E969009788@ripe.net> <m2obmp9zmf.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1278)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.7
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Aug 2012 03:30:44 -0000

On Aug 5, 2012, at 7:34 AM, Randy Bush wrote:

>> In other words: I expect that it will be not more than 20 years from
>> now that we will hear cries of "Why were we so wasteful with IPv6
>> addresses in the beginning?" This is why I disagree with Phillip
>> Hallam-Baker's opinion.
> 
> <aol>
> 
> whatever the number of address bits, if it is fixed, we always run out.
> memory addressing has been a cliff many times.  ip addressing.  ...
> 
Yup.  To quote Fred Brooks on memory address space: "Every successful
computer architecture eventually runs out of address space" -- and I heard
him say that in 1973.


		--Steve Bellovin, https://www.cs.columbia.edu/~smb






From ajs@anvilwalrusden.com  Mon Aug  6 05:06:27 2012
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 91FAE21F866C for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 05:06:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.053
X-Spam-Level: 
X-Spam-Status: No, score=0.053 tagged_above=-999 required=5 tests=[AWL=-1.707,  BAYES_50=0.001, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L2jKePJSXEE0 for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 05:06:27 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 071D221F8669 for <ietf@ietf.org>; Mon,  6 Aug 2012 05:06:26 -0700 (PDT)
Received: from crankycanuck.ca (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id B87528A031 for <ietf@ietf.org>; Mon,  6 Aug 2012 12:06:25 +0000 (UTC)
Date: Mon, 6 Aug 2012 08:06:12 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: So, where to repeat?  (was:Re: management granularity)
Message-ID: <20120806120547.GA20379@crankycanuck.ca>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <501EC24B.4080709@bbiw.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Aug 2012 12:06:27 -0000

On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:
> enough merely to have excellent staff.  We need to go back to the
> better places and benefit from the learning curve.  This doesn't
> mean "no new venues" but it means fewer.

As a practical matter, may I ask about which venues you want to return
to?  I get your argument in principle, but it seems to me that there
has been quite a lot of complaining in the past.  The one factor that
seems to me most likely to reduce complaints -- weather -- is
evidently beyond the Secretariat's or IAOC's control.

People seem inclined to return to the Hyatt in Vancouver, elevators
notwithstanding.  We're going to do that.  (I don't understand why the
previous Vencouver venue was less desirable -- to me, these venues
were very similar, and not very far apart.  I note, however, that the
previous two Vancouver visits were near the end of the year, when it
rains all the time in Vancouver.)

People complained at length about the venue in Paris, so I presume
it's out.

Some people complained about the hotel room prices and travel expense
in Taipei, though I heard remarks that it was a good venue.
Should we try to return there?

People complained in advance about getting to QuÃ©bec, although
afterwards I heard lots of good noises about that venue.  I note that
the weather was great.  Should we try to return?

I don't recall much complaining about the Prague venue in 2011, which
was striking to me because very little seemed different to me compared
to our first visit there.  Perhaps this is evidence of the "tuning"
you suggest (ensuring the water bottles were plastic, for instance).
But I note the weather was excellent.

Beijing?  I guess Maastricht is out. Anaheim (FWIW, I thought that was
an example of a terrible location, but many people seemed happy with
it)?  Hiroshima?  Stockholm?  San Francisco (we thought the crime at
Paris was bad, yet didn't complain about being smack up against the
Tenderloin)?  Or there's the old standby, Minneapolis; perhaps we
could do it in March.  The Dublin venue was panned by large numbers of
people.  Philadelphia, people complained about expense.  Chicago, too
(combined with hotel renovations).  

That gets us back through 2007.  Which of the venues do you think we
should return to, to which we already haven't returned or planned to
return?  And why? 

For what it's worth, I would not complain about returning to any of
those venues; I personally had good meetings at all of them except
Hiroshima, which I missed due to other commitments.  That includes
both Maastricht and Dublin, which were both apparently trials for
large numbers of others.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From daniele.ceccarelli@ericsson.com  Mon Aug  6 05:24:00 2012
Return-Path: <daniele.ceccarelli@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 E008421F8669 for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 05:24:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.077
X-Spam-Level: 
X-Spam-Status: No, score=-3.077 tagged_above=-999 required=5 tests=[AWL=3.172,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x25tMdyrZmD9 for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 05:24:00 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id C601F21F8634 for <ietf@ietf.org>; Mon,  6 Aug 2012 05:23:59 -0700 (PDT)
X-AuditID: c1b4fb25-b7f236d000005cde-36-501fb75e54e7
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id AF.49.23774.E57BF105; Mon,  6 Aug 2012 14:23:58 +0200 (CEST)
Received: from ESESSCMS0360.eemea.ericsson.se ([169.254.1.63]) by esessmw0191.eemea.ericsson.se ([153.88.115.84]) with mapi; Mon, 6 Aug 2012 14:23:58 +0200
From: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 6 Aug 2012 14:23:56 +0200
Subject: RE: So, where to repeat?  (was:Re: management granularity)
Thread-Topic: So, where to repeat?  (was:Re: management granularity)
Thread-Index: Ac1zy/SJGMBkkgr9RtquGul1sS7ttQAANDow
Message-ID: <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca>
In-Reply-To: <20120806120547.GA20379@crankycanuck.ca>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: it-IT, en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrFLMWRmVeSWpSXmKPExsUyM+JvrW7cdvkAg43XTSwOfL7GZPFs43wW ByaPZydfsXssWfKTKYApissmJTUnsyy1SN8ugStjWmNtwSmZikPzjzA2MPaLdzFycEgImEhs /1PXxcgJZIpJXLi3nq2LkYtDSOAUo8S69fvZIZz5jBLvFq5iAmlgE7CSeHLIB6RBRMBX4uu1 PawgNouAisSvFxfAbGEBZ4nV0zeyQ9S4SPSdWc4C0ioiYCSxZnMeSJhXIFyifd5MZojxsxkl Jl56zwaS4BQwlThx7ysjiM0oICsxYfciMJtZQFzi1pP5TBCHCkgs2XOeGcIWlXj5+B8rRL2M xK9N31gh6vUkbkydwgZha0ssW/iaGWKxoMTJmU9YJjCKzkIydhaSlllIWmYhaVnAyLKKUTg3 MTMnvdxIL7UoM7m4OD9Przh1EyMwPg5u+a26g/HOOZFDjNIcLErivNZb9/gLCaQnlqRmp6YW pBbFF5XmpBYfYmTi4JRqYNypfDjR7a3xpGPOh/Nez06S6HlQlqFZsSjIbe6vpeFH7Lh0Dr2r KH/abiZ0+cO06Jq9HotU722YujvyVfgX5lUL5d5dkP5soZ99683/E4UPv925e1Ds9uUHsQuO mz/XUb1vuPNN74SqE0athdPnbK9m5N9yvGX5HI4o74TZ7ceF9zb/Tq2Iui6uxFKckWioxVxU nAgAN1d3G10CAAA=
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Aug 2012 12:24:01 -0000

Dublin panned? I thought it was one of the best venues and locations of the=
 last meetings.

What about Italy or Spain? I've never heard about an IETF in Italy. I'm ok =
with meetings outside Italy since i like traveling very much, but i was won=
dering why it has never been taken into account in the past meetings. Is it=
 expensive? I think Italy and Spain are much cheaper than France, UK or Swe=
den, aren't they?

BR
Daniele

>-----Original Message-----
>From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On=20
>Behalf Of Andrew Sullivan
>Sent: luned=EC 6 agosto 2012 14.06
>To: ietf@ietf.org
>Subject: So, where to repeat? (was:Re: management granularity)
>
>On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:
>> enough merely to have excellent staff.  We need to go back to the=20
>> better places and benefit from the learning curve.  This=20
>doesn't mean=20
>> "no new venues" but it means fewer.
>
>As a practical matter, may I ask about which venues you want=20
>to return to?  I get your argument in principle, but it seems=20
>to me that there has been quite a lot of complaining in the=20
>past.  The one factor that seems to me most likely to reduce=20
>complaints -- weather -- is evidently beyond the Secretariat's=20
>or IAOC's control.
>
>People seem inclined to return to the Hyatt in Vancouver,=20
>elevators notwithstanding.  We're going to do that.  (I don't=20
>understand why the previous Vencouver venue was less desirable=20
>-- to me, these venues were very similar, and not very far=20
>apart.  I note, however, that the previous two Vancouver=20
>visits were near the end of the year, when it rains all the=20
>time in Vancouver.)
>
>People complained at length about the venue in Paris, so I=20
>presume it's out.
>
>Some people complained about the hotel room prices and travel=20
>expense in Taipei, though I heard remarks that it was a good venue.
>Should we try to return there?
>
>People complained in advance about getting to Qu=E9bec, although=20
>afterwards I heard lots of good noises about that venue.  I=20
>note that the weather was great.  Should we try to return?
>
>I don't recall much complaining about the Prague venue in=20
>2011, which was striking to me because very little seemed=20
>different to me compared to our first visit there.  Perhaps=20
>this is evidence of the "tuning"
>you suggest (ensuring the water bottles were plastic, for instance).
>But I note the weather was excellent.
>
>Beijing?  I guess Maastricht is out. Anaheim (FWIW, I thought=20
>that was an example of a terrible location, but many people=20
>seemed happy with it)?  Hiroshima?  Stockholm?  San Francisco=20
>(we thought the crime at Paris was bad, yet didn't complain=20
>about being smack up against the Tenderloin)?  Or there's the=20
>old standby, Minneapolis; perhaps we could do it in March. =20
>The Dublin venue was panned by large numbers of people. =20
>Philadelphia, people complained about expense.  Chicago, too=20
>(combined with hotel renovations). =20
>
>That gets us back through 2007.  Which of the venues do you=20
>think we should return to, to which we already haven't=20
>returned or planned to return?  And why?=20
>
>For what it's worth, I would not complain about returning to=20
>any of those venues; I personally had good meetings at all of=20
>them except Hiroshima, which I missed due to other=20
>commitments.  That includes both Maastricht and Dublin, which=20
>were both apparently trials for large numbers of others.
>
>Best,
>
>A
>
>--
>Andrew Sullivan
>ajs@anvilwalrusden.com
>
>=

From nurit.sprecher@nsn.com  Mon Aug  6 06:09:20 2012
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 970B221F8698 for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 06:09:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.413
X-Spam-Level: 
X-Spam-Status: No, score=-6.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SQ-NdWEe4rgC for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 06:09:20 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 9FFD721F8671 for <ietf@ietf.org>; Mon,  6 Aug 2012 06:09:19 -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 q76D91YC012974 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 6 Aug 2012 15:09:02 +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 q76D8vLq009302; Mon, 6 Aug 2012 15:09:01 +0200
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 6 Aug 2012 15:08:58 +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: So, where to repeat?  (was:Re: management granularity)
Date: Mon, 6 Aug 2012 15:08:57 +0200
Message-ID: <E4873516F3FC7547BCFE792C7D94039C02314BDB@DEMUEXC013.nsn-intra.net>
In-Reply-To: <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: So, where to repeat?  (was:Re: management granularity)
Thread-Index: Ac1zy/SJGMBkkgr9RtquGul1sS7ttQAANDowAAH1j8A=
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com><501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext Daniele Ceccarelli" <daniele.ceccarelli@ericsson.com>, "Andrew Sullivan" <ajs@anvilwalrusden.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 06 Aug 2012 13:08:58.0373 (UTC) FILETIME=[A3E77B50:01CD73D4]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 3938
X-purgate-ID: 151667::1344258542-000055D8-E00A5045/0-0/0-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, 06 Aug 2012 13:09:20 -0000

Oslo?

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of =
ext Daniele Ceccarelli
Sent: Monday, August 06, 2012 3:24 PM
To: Andrew Sullivan; ietf@ietf.org
Subject: RE: So, where to repeat? (was:Re: management granularity)

Dublin panned? I thought it was one of the best venues and locations of =
the last meetings.

What about Italy or Spain? I've never heard about an IETF in Italy. I'm =
ok with meetings outside Italy since i like traveling very much, but i =
was wondering why it has never been taken into account in the past =
meetings. Is it expensive? I think Italy and Spain are much cheaper than =
France, UK or Sweden, aren't they?

BR
Daniele

>-----Original Message-----
>From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On=20
>Behalf Of Andrew Sullivan
>Sent: luned=EC 6 agosto 2012 14.06
>To: ietf@ietf.org
>Subject: So, where to repeat? (was:Re: management granularity)
>
>On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:
>> enough merely to have excellent staff.  We need to go back to the=20
>> better places and benefit from the learning curve.  This=20
>doesn't mean=20
>> "no new venues" but it means fewer.
>
>As a practical matter, may I ask about which venues you want=20
>to return to?  I get your argument in principle, but it seems=20
>to me that there has been quite a lot of complaining in the=20
>past.  The one factor that seems to me most likely to reduce=20
>complaints -- weather -- is evidently beyond the Secretariat's=20
>or IAOC's control.
>
>People seem inclined to return to the Hyatt in Vancouver,=20
>elevators notwithstanding.  We're going to do that.  (I don't=20
>understand why the previous Vencouver venue was less desirable=20
>-- to me, these venues were very similar, and not very far=20
>apart.  I note, however, that the previous two Vancouver=20
>visits were near the end of the year, when it rains all the=20
>time in Vancouver.)
>
>People complained at length about the venue in Paris, so I=20
>presume it's out.
>
>Some people complained about the hotel room prices and travel=20
>expense in Taipei, though I heard remarks that it was a good venue.
>Should we try to return there?
>
>People complained in advance about getting to Qu=E9bec, although=20
>afterwards I heard lots of good noises about that venue.  I=20
>note that the weather was great.  Should we try to return?
>
>I don't recall much complaining about the Prague venue in=20
>2011, which was striking to me because very little seemed=20
>different to me compared to our first visit there.  Perhaps=20
>this is evidence of the "tuning"
>you suggest (ensuring the water bottles were plastic, for instance).
>But I note the weather was excellent.
>
>Beijing?  I guess Maastricht is out. Anaheim (FWIW, I thought=20
>that was an example of a terrible location, but many people=20
>seemed happy with it)?  Hiroshima?  Stockholm?  San Francisco=20
>(we thought the crime at Paris was bad, yet didn't complain=20
>about being smack up against the Tenderloin)?  Or there's the=20
>old standby, Minneapolis; perhaps we could do it in March. =20
>The Dublin venue was panned by large numbers of people. =20
>Philadelphia, people complained about expense.  Chicago, too=20
>(combined with hotel renovations). =20
>
>That gets us back through 2007.  Which of the venues do you=20
>think we should return to, to which we already haven't=20
>returned or planned to return?  And why?=20
>
>For what it's worth, I would not complain about returning to=20
>any of those venues; I personally had good meetings at all of=20
>them except Hiroshima, which I missed due to other=20
>commitments.  That includes both Maastricht and Dublin, which=20
>were both apparently trials for large numbers of others.
>
>Best,
>
>A
>
>--
>Andrew Sullivan
>ajs@anvilwalrusden.com
>
>

From Chris.Dearlove@baesystems.com  Mon Aug  6 06:56:05 2012
Return-Path: <Chris.Dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4AB321F861D for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 06:56:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.287
X-Spam-Level: 
X-Spam-Status: No, score=-10.287 tagged_above=-999 required=5 tests=[AWL=0.312, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jku0WBFpzOXj for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 06:56:05 -0700 (PDT)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) by ietfa.amsl.com (Postfix) with ESMTP id 726BE21F8617 for <ietf@ietf.org>; Mon,  6 Aug 2012 06:56:04 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.77,718,1336345200"; d="scan'208";a="261582612"
Received: from unknown (HELO baemasmds009.greenlnk.net) ([141.245.68.246]) by baemasmds003ir.sharelnk.net with ESMTP; 06 Aug 2012 14:56:01 +0100
Received: from GLKXH0003V.GREENLNK.net ([10.109.2.34]) by baemasmds009.greenlnk.net (Switch-3.4.4/Switch-3.4.4) with ESMTP id q76Du0cY022707 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 6 Aug 2012 14:56:00 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.170]) by GLKXH0003V.GREENLNK.net ([10.109.2.34]) with mapi id 14.02.0309.002; Mon, 6 Aug 2012 14:56:00 +0100
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>, Andrew Sullivan <ajs@anvilwalrusden.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: So, where to repeat?  (was:Re: management granularity)
Thread-Topic: So, where to repeat?  (was:Re: management granularity)
Thread-Index: AQHNc8vwANZh9JcPEUekUkB0CVEkipdMpFYAgAAnVfA=
Date: Mon, 6 Aug 2012 13:55:59 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se>
In-Reply-To: <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset=iso-8859-1
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, 06 Aug 2012 13:56:06 -0000

Dublin's problem was that the venue was isolated from the city. This has al=
so been the case with e.g. San Diego. (I'm assuming no personal car.) Contr=
ast with Minneapolis (and several other places) where you were right in the=
 city. Being in a city is better for lunch and dinner options, taking a bre=
ak to go to a bookshop (or to buy something you forgot to bring) and so on.=
 (I'm deliberately not including tourism here.)

However at the moment my priorities to make being able to attend possible w=
ould be time (so the closer to me the better - I realise that's impossible =
globally), cost (hotel first, flight second, rest is noise) and the ability=
 to plan ahead to only attend part of the week. This is the current economi=
c reality. Dublin actually scores quite well on those for me.

--=20
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Dan=
iele Ceccarelli
Sent: 06 August 2012 13:24
To: Andrew Sullivan; ietf@ietf.org
Subject: RE: So, where to repeat? (was:Re: management granularity)

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

Dublin panned? I thought it was one of the best venues and locations of the=
 last meetings.

What about Italy or Spain? I've never heard about an IETF in Italy. I'm ok =
with meetings outside Italy since i like traveling very much, but i was won=
dering why it has never been taken into account in the past meetings. Is it=
 expensive? I think Italy and Spain are much cheaper than France, UK or Swe=
den, aren't they?

BR
Daniele

>-----Original Message-----
>From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On=20
>Behalf Of Andrew Sullivan
>Sent: luned=EC 6 agosto 2012 14.06
>To: ietf@ietf.org
>Subject: So, where to repeat? (was:Re: management granularity)
>
>On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:
>> enough merely to have excellent staff.  We need to go back to the=20
>> better places and benefit from the learning curve.  This=20
>doesn't mean=20
>> "no new venues" but it means fewer.
>
>As a practical matter, may I ask about which venues you want=20
>to return to?  I get your argument in principle, but it seems=20
>to me that there has been quite a lot of complaining in the=20
>past.  The one factor that seems to me most likely to reduce=20
>complaints -- weather -- is evidently beyond the Secretariat's=20
>or IAOC's control.
>
>People seem inclined to return to the Hyatt in Vancouver,=20
>elevators notwithstanding.  We're going to do that.  (I don't=20
>understand why the previous Vencouver venue was less desirable=20
>-- to me, these venues were very similar, and not very far=20
>apart.  I note, however, that the previous two Vancouver=20
>visits were near the end of the year, when it rains all the=20
>time in Vancouver.)
>
>People complained at length about the venue in Paris, so I=20
>presume it's out.
>
>Some people complained about the hotel room prices and travel=20
>expense in Taipei, though I heard remarks that it was a good venue.
>Should we try to return there?
>
>People complained in advance about getting to Qu=E9bec, although=20
>afterwards I heard lots of good noises about that venue.  I=20
>note that the weather was great.  Should we try to return?
>
>I don't recall much complaining about the Prague venue in=20
>2011, which was striking to me because very little seemed=20
>different to me compared to our first visit there.  Perhaps=20
>this is evidence of the "tuning"
>you suggest (ensuring the water bottles were plastic, for instance).
>But I note the weather was excellent.
>
>Beijing?  I guess Maastricht is out. Anaheim (FWIW, I thought=20
>that was an example of a terrible location, but many people=20
>seemed happy with it)?  Hiroshima?  Stockholm?  San Francisco=20
>(we thought the crime at Paris was bad, yet didn't complain=20
>about being smack up against the Tenderloin)?  Or there's the=20
>old standby, Minneapolis; perhaps we could do it in March. =20
>The Dublin venue was panned by large numbers of people. =20
>Philadelphia, people complained about expense.  Chicago, too=20
>(combined with hotel renovations). =20
>
>That gets us back through 2007.  Which of the venues do you=20
>think we should return to, to which we already haven't=20
>returned or planned to return?  And why?=20
>
>For what it's worth, I would not complain about returning to=20
>any of those venues; I personally had good meetings at all of=20
>them except Hiroshima, which I missed due to other=20
>commitments.  That includes both Maastricht and Dublin, which=20
>were both apparently trials for large numbers of others.
>
>Best,
>
>A
>
>--
>Andrew Sullivan
>ajs@anvilwalrusden.com
>
>

********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From nurit.sprecher@nsn.com  Mon Aug  6 07:06:44 2012
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 6968421F869A for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 07:06:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.423
X-Spam-Level: 
X-Spam-Status: No, score=-6.423 tagged_above=-999 required=5 tests=[AWL=0.176,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KBVL4VKRtitj for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 07:06:43 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 31E0F21F85EA for <ietf@ietf.org>; Mon,  6 Aug 2012 07:06:43 -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 q76E6bCg017698 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 6 Aug 2012 16:06:38 +0200
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q76E6b9a027324; Mon, 6 Aug 2012 16:06:37 +0200
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 6 Aug 2012 16:06:37 +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: So, where to repeat?  (was:Re: management granularity)
Date: Mon, 6 Aug 2012 16:06:35 +0200
Message-ID: <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: So, where to repeat?  (was:Re: management granularity)
Thread-Index: AQHNc8vwANZh9JcPEUekUkB0CVEkipdMpFYAgAAnVfCAAAV5EA==
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com><501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca><B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>, "Daniele Ceccarelli" <daniele.ceccarelli@ericsson.com>, "Andrew Sullivan" <ajs@anvilwalrusden.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 06 Aug 2012 14:06:37.0603 (UTC) FILETIME=[B1C41730:01CD73DC]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 6658
X-purgate-ID: 151667::1344261998-000055D8-68477399/0-0/0-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, 06 Aug 2012 14:06:44 -0000

When you are not close (time), flight cost may become higher in the =
priority (over hotem)....
Flying to Vancouver for me for example is the most expensive =
trip....even though the city is amazing and the host was wonderful!

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of =
ext Dearlove, Christopher (UK)
Sent: Monday, August 06, 2012 4:56 PM
To: Daniele Ceccarelli; Andrew Sullivan; ietf@ietf.org
Subject: RE: So, where to repeat? (was:Re: management granularity)

Dublin's problem was that the venue was isolated from the city. This has =
also been the case with e.g. San Diego. (I'm assuming no personal car.) =
Contrast with Minneapolis (and several other places) where you were =
right in the city. Being in a city is better for lunch and dinner =
options, taking a break to go to a bookshop (or to buy something you =
forgot to bring) and so on. (I'm deliberately not including tourism =
here.)

However at the moment my priorities to make being able to attend =
possible would be time (so the closer to me the better - I realise =
that's impossible globally), cost (hotel first, flight second, rest is =
noise) and the ability to plan ahead to only attend part of the week. =
This is the current economic reality. Dublin actually scores quite well =
on those for me.

--=20
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace =
Centre, Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of =
Daniele Ceccarelli
Sent: 06 August 2012 13:24
To: Andrew Sullivan; ietf@ietf.org
Subject: RE: So, where to repeat? (was:Re: management granularity)

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

Dublin panned? I thought it was one of the best venues and locations of =
the last meetings.

What about Italy or Spain? I've never heard about an IETF in Italy. I'm =
ok with meetings outside Italy since i like traveling very much, but i =
was wondering why it has never been taken into account in the past =
meetings. Is it expensive? I think Italy and Spain are much cheaper than =
France, UK or Sweden, aren't they?

BR
Daniele

>-----Original Message-----
>From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On=20
>Behalf Of Andrew Sullivan
>Sent: luned=EC 6 agosto 2012 14.06
>To: ietf@ietf.org
>Subject: So, where to repeat? (was:Re: management granularity)
>
>On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:
>> enough merely to have excellent staff.  We need to go back to the=20
>> better places and benefit from the learning curve.  This=20
>doesn't mean=20
>> "no new venues" but it means fewer.
>
>As a practical matter, may I ask about which venues you want=20
>to return to?  I get your argument in principle, but it seems=20
>to me that there has been quite a lot of complaining in the=20
>past.  The one factor that seems to me most likely to reduce=20
>complaints -- weather -- is evidently beyond the Secretariat's=20
>or IAOC's control.
>
>People seem inclined to return to the Hyatt in Vancouver,=20
>elevators notwithstanding.  We're going to do that.  (I don't=20
>understand why the previous Vencouver venue was less desirable=20
>-- to me, these venues were very similar, and not very far=20
>apart.  I note, however, that the previous two Vancouver=20
>visits were near the end of the year, when it rains all the=20
>time in Vancouver.)
>
>People complained at length about the venue in Paris, so I=20
>presume it's out.
>
>Some people complained about the hotel room prices and travel=20
>expense in Taipei, though I heard remarks that it was a good venue.
>Should we try to return there?
>
>People complained in advance about getting to Qu=E9bec, although=20
>afterwards I heard lots of good noises about that venue.  I=20
>note that the weather was great.  Should we try to return?
>
>I don't recall much complaining about the Prague venue in=20
>2011, which was striking to me because very little seemed=20
>different to me compared to our first visit there.  Perhaps=20
>this is evidence of the "tuning"
>you suggest (ensuring the water bottles were plastic, for instance).
>But I note the weather was excellent.
>
>Beijing?  I guess Maastricht is out. Anaheim (FWIW, I thought=20
>that was an example of a terrible location, but many people=20
>seemed happy with it)?  Hiroshima?  Stockholm?  San Francisco=20
>(we thought the crime at Paris was bad, yet didn't complain=20
>about being smack up against the Tenderloin)?  Or there's the=20
>old standby, Minneapolis; perhaps we could do it in March. =20
>The Dublin venue was panned by large numbers of people. =20
>Philadelphia, people complained about expense.  Chicago, too=20
>(combined with hotel renovations). =20
>
>That gets us back through 2007.  Which of the venues do you=20
>think we should return to, to which we already haven't=20
>returned or planned to return?  And why?=20
>
>For what it's worth, I would not complain about returning to=20
>any of those venues; I personally had good meetings at all of=20
>them except Hiroshima, which I missed due to other=20
>commitments.  That includes both Maastricht and Dublin, which=20
>were both apparently trials for large numbers of others.
>
>Best,
>
>A
>
>--
>Andrew Sullivan
>ajs@anvilwalrusden.com
>
>

********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From joelja@bogus.com  Mon Aug  6 07:08:19 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 201D021F8771 for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 07:08:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4pIbt1eKkbAk for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 07:08:18 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 616B321F869A for <ietf@ietf.org>; Mon,  6 Aug 2012 07:08:18 -0700 (PDT)
Received: from joels-MacBook-Air.local (64-66-20-219.cipherkey.net [64.66.20.219]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q76E7uw4051566 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 6 Aug 2012 14:07:56 GMT (envelope-from joelja@bogus.com)
Message-ID: <501FCFBD.1010702@bogus.com>
Date: Mon, 06 Aug 2012 07:07:57 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120717 Thunderbird/15.0
MIME-Version: 1.0
To: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
Subject: Re: So, where to repeat?
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se>
In-Reply-To: <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 06 Aug 2012 14:07:57 +0000 (UTC)
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Aug 2012 14:08:19 -0000

On 8/6/12 5:23 AM, Daniele Ceccarelli wrote:
> Dublin panned? I thought it was one of the best venues and locations of the last meetings.
The meeting wasn't "in" Dublin. There are no venues  attached to or 
adjacent to suitable hotels large enough to do a plenary in Dublin.

Regarding the venue itself. Next to no attenuation between floors. I am 
still surprised that building had enough steel in it to not come down 
around our ears.

I'd just as soon do wifi for 1200 in a tent.
> What about Italy or Spain? I've never heard about an IETF in Italy. I'm ok with meetings outside Italy since i like traveling very much, but i was wondering why it has never been taken into account in the past meetings. Is it expensive? I think Italy and Spain are much cheaper than France, UK or Sweden, aren't they?
>
> BR
> Daniele
>
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On
>> Behalf Of Andrew Sullivan
>> Sent: lunedì 6 agosto 2012 14.06
>> To: ietf@ietf.org
>> Subject: So, where to repeat? (was:Re: management granularity)
>>
>> On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:
>>> enough merely to have excellent staff.  We need to go back to the
>>> better places and benefit from the learning curve.  This
>> doesn't mean
>>> "no new venues" but it means fewer.
>> As a practical matter, may I ask about which venues you want
>> to return to?  I get your argument in principle, but it seems
>> to me that there has been quite a lot of complaining in the
>> past.  The one factor that seems to me most likely to reduce
>> complaints -- weather -- is evidently beyond the Secretariat's
>> or IAOC's control.
>>
>> People seem inclined to return to the Hyatt in Vancouver,
>> elevators notwithstanding.  We're going to do that.  (I don't
>> understand why the previous Vencouver venue was less desirable
>> -- to me, these venues were very similar, and not very far
>> apart.  I note, however, that the previous two Vancouver
>> visits were near the end of the year, when it rains all the
>> time in Vancouver.)
>>
>> People complained at length about the venue in Paris, so I
>> presume it's out.
>>
>> Some people complained about the hotel room prices and travel
>> expense in Taipei, though I heard remarks that it was a good venue.
>> Should we try to return there?
>>
>> People complained in advance about getting to Québec, although
>> afterwards I heard lots of good noises about that venue.  I
>> note that the weather was great.  Should we try to return?
>>
>> I don't recall much complaining about the Prague venue in
>> 2011, which was striking to me because very little seemed
>> different to me compared to our first visit there.  Perhaps
>> this is evidence of the "tuning"
>> you suggest (ensuring the water bottles were plastic, for instance).
>> But I note the weather was excellent.
>>
>> Beijing?  I guess Maastricht is out. Anaheim (FWIW, I thought
>> that was an example of a terrible location, but many people
>> seemed happy with it)?  Hiroshima?  Stockholm?  San Francisco
>> (we thought the crime at Paris was bad, yet didn't complain
>> about being smack up against the Tenderloin)?  Or there's the
>> old standby, Minneapolis; perhaps we could do it in March.
>> The Dublin venue was panned by large numbers of people.
>> Philadelphia, people complained about expense.  Chicago, too
>> (combined with hotel renovations).
>>
>> That gets us back through 2007.  Which of the venues do you
>> think we should return to, to which we already haven't
>> returned or planned to return?  And why?
>>
>> For what it's worth, I would not complain about returning to
>> any of those venues; I personally had good meetings at all of
>> them except Hiroshima, which I missed due to other
>> commitments.  That includes both Maastricht and Dublin, which
>> were both apparently trials for large numbers of others.
>>
>> Best,
>>
>> A
>>
>> --
>> Andrew Sullivan
>> ajs@anvilwalrusden.com
>>
>>


From ole@cisco.com  Mon Aug  6 07:11:09 2012
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 444C021F8644 for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 07:11:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.56
X-Spam-Level: 
X-Spam-Status: No, score=-110.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4jrdjxD3AgOz for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 07:11:08 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 7FB9021F8617 for <ietf@ietf.org>; Mon,  6 Aug 2012 07:10:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=929; q=dns/txt; s=iport; t=1344262265; x=1345471865; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=Hmo71FXLwVzxmhw53/i1YaBU4fIifANe+X73igMbXLk=; b=WdvOpRpOkfuKXznIDMDS7HL1PcNOtoYKMtaT4geanEZ9FyQO0lFpcrG2 uym1IuOGqqsRGtWWMdTnH5MXOqLAafWXg08xC1VpqjczneNbZKPN9IlGu NLiN50NV4zDwsfOdhwYTQt7LFZhbgDVTzmh8HIVJeI2LHP3RtXai+se1u A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4FACfPH1CrRDoG/2dsb2JhbABCA4U0tBGBB4IgAQEBAwESAQIlPwULCy0ZVwYTIodlBZtUg0gQnByLShqDQgeDIQOITZJXhTGDGoEEYoJ/gT8
X-IronPort-AV: E=Sophos;i="4.77,720,1336348800"; d="scan'208";a="51110045"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 06 Aug 2012 14:10:56 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q76EAtVn012190 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Aug 2012 14:10:55 GMT
Date: Mon, 6 Aug 2012 07:10:55 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
Subject: RE: So, where to repeat?  (was:Re: management granularity)
In-Reply-To: <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se>
Message-ID: <alpine.OSX.2.01.1208060708530.11247@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Aug 2012 14:11:09 -0000

Daniele,

I can almost guarantee that if you help us find a suitable venue and 
host we'll be coming to Italy. So far we haven't found either, but 
that can be said about a lot of places...

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Mon, 6 Aug 2012, Daniele Ceccarelli wrote:

> Dublin panned? I thought it was one of the best venues and locations 
> of the last meetings.
> 
> What about Italy or Spain? I've never heard about an IETF in Italy. 
> I'm ok with meetings outside Italy since i like traveling very much, 
> but i was wondering why it has never been taken into account in the 
> past meetings. Is it expensive? I think Italy and Spain are much 
> cheaper than France, UK or Sweden, aren't they?
> 
> BR
> Daniele
> 

From Chris.Dearlove@baesystems.com  Mon Aug  6 07:18:42 2012
Return-Path: <Chris.Dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CE5521F86A0 for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 07:18:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level: 
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eDZ74EUcYg1K for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 07:18:40 -0700 (PDT)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) by ietfa.amsl.com (Postfix) with ESMTP id 5261721F868A for <ietf@ietf.org>; Mon,  6 Aug 2012 07:18:40 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.77,720,1336345200"; d="scan'208";a="261590936"
Received: from unknown (HELO baemasmds009.greenlnk.net) ([141.245.68.246]) by baemasmds003ir.sharelnk.net with ESMTP; 06 Aug 2012 15:18:39 +0100
Received: from GLKXH0002V.GREENLNK.net ([10.109.2.33]) by baemasmds009.greenlnk.net (Switch-3.4.4/Switch-3.4.4) with ESMTP id q76EIdj4005798 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 6 Aug 2012 15:18:39 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.170]) by GLKXH0002V.GREENLNK.net ([10.109.2.33]) with mapi id 14.02.0309.002; Mon, 6 Aug 2012 15:18:38 +0100
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>, Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>, Andrew Sullivan <ajs@anvilwalrusden.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: So, where to repeat?  (was:Re: management granularity)
Thread-Topic: So, where to repeat?  (was:Re: management granularity)
Thread-Index: AQHNc8vwANZh9JcPEUekUkB0CVEkipdMpFYAgAAnVfCAAAV5EIAAAOGA
Date: Mon, 6 Aug 2012 14:18:38 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com><501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca><B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net>
In-Reply-To: <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="iso-8859-1"
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, 06 Aug 2012 14:18:42 -0000

I've never been to an IETF meeting where the plane fare has exceeded the ho=
tel cost for a week. Caveats to that are that I have mostly gone for IETF r=
ecommended hotels, so may have missed particularly cheap hotels, and that I=
 have only been to North American and Europe (but that statistic includes V=
ancouver and the even further away western US cities down to San Diego). An=
d of course I fly economy, and it's much cheaper including a Saturday night=
 in your trip, even at the cost of an extra night in a hotel (at least it i=
s from here). An almost exception was Paris this year where I was staying f=
airly cheaply, but that was a cost-shared trip between me and my employer, =
and I didn't fly (I went by train - though that's not cheaper, just better)=
. Paris has cheap(er) hotels and a metro I understand, so I felt less locat=
ion constrained.

--=20
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: Sprecher, Nurit (NSN - IL/Hod HaSharon) [mailto:nurit.sprecher@nsn.co=
m]=20
Sent: 06 August 2012 15:07
To: Dearlove, Christopher (UK); Daniele Ceccarelli; Andrew Sullivan; ietf@i=
etf.org
Subject: RE: So, where to repeat? (was:Re: management granularity)

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

When you are not close (time), flight cost may become higher in the priorit=
y (over hotem)....
Flying to Vancouver for me for example is the most expensive trip....even t=
hough the city is amazing and the host was wonderful!

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of ext=
 Dearlove, Christopher (UK)
Sent: Monday, August 06, 2012 4:56 PM
To: Daniele Ceccarelli; Andrew Sullivan; ietf@ietf.org
Subject: RE: So, where to repeat? (was:Re: management granularity)

Dublin's problem was that the venue was isolated from the city. This has al=
so been the case with e.g. San Diego. (I'm assuming no personal car.) Contr=
ast with Minneapolis (and several other places) where you were right in the=
 city. Being in a city is better for lunch and dinner options, taking a bre=
ak to go to a bookshop (or to buy something you forgot to bring) and so on.=
 (I'm deliberately not including tourism here.)

However at the moment my priorities to make being able to attend possible w=
ould be time (so the closer to me the better - I realise that's impossible =
globally), cost (hotel first, flight second, rest is noise) and the ability=
 to plan ahead to only attend part of the week. This is the current economi=
c reality. Dublin actually scores quite well on those for me.

--=20
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Dan=
iele Ceccarelli
Sent: 06 August 2012 13:24
To: Andrew Sullivan; ietf@ietf.org
Subject: RE: So, where to repeat? (was:Re: management granularity)

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

Dublin panned? I thought it was one of the best venues and locations of the=
 last meetings.

What about Italy or Spain? I've never heard about an IETF in Italy. I'm ok =
with meetings outside Italy since i like traveling very much, but i was won=
dering why it has never been taken into account in the past meetings. Is it=
 expensive? I think Italy and Spain are much cheaper than France, UK or Swe=
den, aren't they?

BR
Daniele

>-----Original Message-----
>From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On=20
>Behalf Of Andrew Sullivan
>Sent: luned=EC 6 agosto 2012 14.06
>To: ietf@ietf.org
>Subject: So, where to repeat? (was:Re: management granularity)
>
>On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:
>> enough merely to have excellent staff.  We need to go back to the=20
>> better places and benefit from the learning curve.  This=20
>doesn't mean=20
>> "no new venues" but it means fewer.
>
>As a practical matter, may I ask about which venues you want=20
>to return to?  I get your argument in principle, but it seems=20
>to me that there has been quite a lot of complaining in the=20
>past.  The one factor that seems to me most likely to reduce=20
>complaints -- weather -- is evidently beyond the Secretariat's=20
>or IAOC's control.
>
>People seem inclined to return to the Hyatt in Vancouver,=20
>elevators notwithstanding.  We're going to do that.  (I don't=20
>understand why the previous Vencouver venue was less desirable=20
>-- to me, these venues were very similar, and not very far=20
>apart.  I note, however, that the previous two Vancouver=20
>visits were near the end of the year, when it rains all the=20
>time in Vancouver.)
>
>People complained at length about the venue in Paris, so I=20
>presume it's out.
>
>Some people complained about the hotel room prices and travel=20
>expense in Taipei, though I heard remarks that it was a good venue.
>Should we try to return there?
>
>People complained in advance about getting to Qu=E9bec, although=20
>afterwards I heard lots of good noises about that venue.  I=20
>note that the weather was great.  Should we try to return?
>
>I don't recall much complaining about the Prague venue in=20
>2011, which was striking to me because very little seemed=20
>different to me compared to our first visit there.  Perhaps=20
>this is evidence of the "tuning"
>you suggest (ensuring the water bottles were plastic, for instance).
>But I note the weather was excellent.
>
>Beijing?  I guess Maastricht is out. Anaheim (FWIW, I thought=20
>that was an example of a terrible location, but many people=20
>seemed happy with it)?  Hiroshima?  Stockholm?  San Francisco=20
>(we thought the crime at Paris was bad, yet didn't complain=20
>about being smack up against the Tenderloin)?  Or there's the=20
>old standby, Minneapolis; perhaps we could do it in March. =20
>The Dublin venue was panned by large numbers of people. =20
>Philadelphia, people complained about expense.  Chicago, too=20
>(combined with hotel renovations). =20
>
>That gets us back through 2007.  Which of the venues do you=20
>think we should return to, to which we already haven't=20
>returned or planned to return?  And why?=20
>
>For what it's worth, I would not complain about returning to=20
>any of those venues; I personally had good meetings at all of=20
>them except Hiroshima, which I missed due to other=20
>commitments.  That includes both Maastricht and Dublin, which=20
>were both apparently trials for large numbers of others.
>
>Best,
>
>A
>
>--
>Andrew Sullivan
>ajs@anvilwalrusden.com
>
>

********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************



From ajs@anvilwalrusden.com  Mon Aug  6 07:30:29 2012
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 675A221F8600 for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 07:30:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.221
X-Spam-Level: 
X-Spam-Status: No, score=-1.221 tagged_above=-999 required=5 tests=[AWL=-0.381, BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RkF4tGG+J-bW for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 07:30:29 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id ECEF821F85FF for <ietf@ietf.org>; Mon,  6 Aug 2012 07:30:28 -0700 (PDT)
Received: from mail.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 3694B8A031 for <ietf@ietf.org>; Mon,  6 Aug 2012 14:30:28 +0000 (UTC)
Date: Mon, 6 Aug 2012 10:30:26 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: So, where to repeat?  (was:Re: management granularity)
Message-ID: <20120806143025.GB53917@mail.yitter.info>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Aug 2012 14:30:29 -0000

On Mon, Aug 06, 2012 at 01:55:59PM +0000, Dearlove, Christopher (UK) wrote:
 
> is noise) and the ability to plan ahead to only attend part of the
> week.

That topic imports a completely new one to this discussion: advance
scheduling of the meetings. If there is any principle for repeating a
venue to be found (I'm a sceptic, but let's see), then advance
scheduling can't enter into it because the lack of advance scheduling
is the same at every meeting. So, for the purposes of this discussion,
you have two options: plan well in advance to be there for the entire
week, or plan to buy plane tickets after the agenda is finalized.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From Chris.Dearlove@baesystems.com  Mon Aug  6 07:39:53 2012
Return-Path: <Chris.Dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C914C21F8617 for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 07:39:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.31
X-Spam-Level: 
X-Spam-Status: No, score=-10.31 tagged_above=-999 required=5 tests=[AWL=0.289,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HWQcJ2EdCGLS for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 07:39:52 -0700 (PDT)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) by ietfa.amsl.com (Postfix) with ESMTP id A62AF21F858F for <ietf@ietf.org>; Mon,  6 Aug 2012 07:39:52 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.77,720,1336345200"; d="scan'208";a="261598806"
Received: from unknown (HELO baemasmds009.greenlnk.net) ([141.245.68.246]) by baemasmds003ir.sharelnk.net with ESMTP; 06 Aug 2012 15:39:51 +0100
Received: from GLKXH0001V.GREENLNK.net ([10.109.2.32]) by baemasmds009.greenlnk.net (Switch-3.4.4/Switch-3.4.4) with ESMTP id q76EdpkA020525 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 6 Aug 2012 15:39:51 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.170]) by GLKXH0001V.GREENLNK.net ([10.109.2.32]) with mapi id 14.02.0309.002; Mon, 6 Aug 2012 15:39:51 +0100
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: So, where to repeat?  (was:Re: management granularity)
Thread-Topic: So, where to repeat?  (was:Re: management granularity)
Thread-Index: AQHNc8vwANZh9JcPEUekUkB0CVEkipdMpFYAgAAnVfD///wDAIAAEklQ
Date: Mon, 6 Aug 2012 14:39:50 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBAA19@GLKXM0002V.GREENLNK.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net>	<20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <20120806143025.GB53917@mail.yitter.info>
In-Reply-To: <20120806143025.GB53917@mail.yitter.info>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset=iso-8859-1
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, 06 Aug 2012 14:39:53 -0000

Three options. The two you mention and not going. Yes, advance scheduling i=
s new to this discussion this time, and yes it's not done. But it does have=
 a real impact once time/cost becomes sufficiently critical that days count=
.

--=20
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of And=
rew Sullivan
Sent: 06 August 2012 15:30
To: ietf@ietf.org
Subject: Re: So, where to repeat? (was:Re: management granularity)

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

On Mon, Aug 06, 2012 at 01:55:59PM +0000, Dearlove, Christopher (UK) wrote:
=20
> is noise) and the ability to plan ahead to only attend part of the
> week.

That topic imports a completely new one to this discussion: advance
scheduling of the meetings. If there is any principle for repeating a
venue to be found (I'm a sceptic, but let's see), then advance
scheduling can't enter into it because the lack of advance scheduling
is the same at every meeting. So, for the purposes of this discussion,
you have two options: plan well in advance to be there for the entire
week, or plan to buy plane tickets after the agenda is finalized.

Best,

A

--=20
Andrew Sullivan
ajs@anvilwalrusden.com


********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From mary.ietf.barnes@gmail.com  Mon Aug  6 07:41:45 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE3EB21F863B for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 07:41:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.528
X-Spam-Level: 
X-Spam-Status: No, score=-103.528 tagged_above=-999 required=5 tests=[AWL=0.070, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q5jbijy2J736 for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 07:41:41 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7B7B021F84CD for <ietf@ietf.org>; Mon,  6 Aug 2012 07:41:38 -0700 (PDT)
Received: by lahm15 with SMTP id m15so1682505lah.31 for <ietf@ietf.org>; Mon, 06 Aug 2012 07:41:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=s3YKOAoPhI/0N60NnOzgtZ0NE+uGZzmLBWX7tbY8XVQ=; b=0wgzBwZRHkPhu2Ak1goBFov7EWHXA/DRPnheWak1QAENsRY8mCCrqs7w578W/R+HUW GaVBDGTFUuNR6/pC6thb6iF/37zqx9/d6rJCK1Ca508jsshFw/ij8WjddxAtbrHKqopw YJeDcM8EiK0UrxyHjHr3N5i0AL3nJkOng0y5wL9HeWtEVwKODQlvgHAS4/2EHZ4sJZTf uiVhAVoCMQXmOXi824lqBZsyCjmF9cSJ25bvbg73//oqH7LHnTcFP3VkL80AxO0wJaPq +dmK0UblvU+KfOzIE59bPWKvSr7O7x5cmSXg/J4dT9Zw471JhQB3LQs//MkJsYeEOFql cnnA==
MIME-Version: 1.0
Received: by 10.152.104.77 with SMTP id gc13mr10914573lab.31.1344264095731; Mon, 06 Aug 2012 07:41:35 -0700 (PDT)
Received: by 10.112.85.196 with HTTP; Mon, 6 Aug 2012 07:41:35 -0700 (PDT)
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net>
Date: Mon, 6 Aug 2012 09:41:35 -0500
Message-ID: <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com>
Subject: Re: So, where to repeat? (was:Re: management granularity)
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
Content-Type: multipart/alternative; boundary=f46d04083adbe9109304c699dfbe
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, 06 Aug 2012 14:41:46 -0000

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

Flights to Vancouver from some cities were extremely expensive.  It would
have cost me more than twice as much as it did to fly to Beijing, for
example, if I had taken a direct flight from DFW - it would have been by
far my most expensive IETF airfare ever. I didn't because I was trying to
be cost conscious.  However, I could have flown to London in the same time
it took me to get to/from Vancouver and for about the same price.  This is
a typical problem when we go somewhere when tourists go (for some reason,
flying to cities in Canada is very popular when the temp in Texas is 110
degrees F).     Orlando will most likely be just as bad since it is
scheduled during a time where many schools in DFW area have Spring Break -
flight costs right now are over $500 ($560).  I can usually fly anywhere in
the U.S. for around $300 when I book early.  And, of course, I can't book
early as my company won't re-imburse unless I use their travel company and
have approval (which I won't get for at least another 5-6 months).
Hopefully, the IETF negotiated hotel rate won't reflect that it is Spring
Break.

If we were to choose one place in the U.S. to meet, Minneapolis is the best
choice IMHO.  It's very reasonably priced, easy for many to get to and the
hotel has adequate space for us (even back when we had many more
attendees).  Personally, the weather is not critical to me, since I spend
the vast majority of my time in the hotel meeting rooms, so I'm very happy
if we meet there in March and November.

Mary

On Mon, Aug 6, 2012 at 9:18 AM, Dearlove, Christopher (UK) <
Chris.Dearlove@baesystems.com> wrote:

> I've never been to an IETF meeting where the plane fare has exceeded the
> hotel cost for a week. Caveats to that are that I have mostly gone for IE=
TF
> recommended hotels, so may have missed particularly cheap hotels, and tha=
t
> I have only been to North American and Europe (but that statistic include=
s
> Vancouver and the even further away western US cities down to San Diego).
> And of course I fly economy, and it's much cheaper including a Saturday
> night in your trip, even at the cost of an extra night in a hotel (at lea=
st
> it is from here). An almost exception was Paris this year where I was
> staying fairly cheaply, but that was a cost-shared trip between me and my
> employer, and I didn't fly (I went by train - though that's not cheaper,
> just better). Paris has cheap(er) hotels and a metro I understand, so I
> felt less location constrained.
>
> --
> Christopher Dearlove
> Senior Principal Engineer, Communications Group
> Communications, Networks and Image Analysis Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194 |  Fax: +44 1245 242124
> chris.dearlove@baesystems.com | http://www.baesystems.com
>
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre=
,
> Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687
>
>
> -----Original Message-----
> From: Sprecher, Nurit (NSN - IL/Hod HaSharon) [mailto:
> nurit.sprecher@nsn.com]
> Sent: 06 August 2012 15:07
> To: Dearlove, Christopher (UK); Daniele Ceccarelli; Andrew Sullivan;
> ietf@ietf.org
> Subject: RE: So, where to repeat? (was:Re: management granularity)
>
> ----------------------! WARNING ! ----------------------
> This message originates from outside our organisation,
> either from an external partner or from the internet.
> Keep this in mind if you answer this message.
> Follow the 'Report Suspicious Emails' link on IT matters
> for instructions on reporting suspicious email messages.
> --------------------------------------------------------
>
> When you are not close (time), flight cost may become higher in the
> priority (over hotem)....
> Flying to Vancouver for me for example is the most expensive trip....even
> though the city is amazing and the host was wonderful!
>
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> ext Dearlove, Christopher (UK)
> Sent: Monday, August 06, 2012 4:56 PM
> To: Daniele Ceccarelli; Andrew Sullivan; ietf@ietf.org
> Subject: RE: So, where to repeat? (was:Re: management granularity)
>
> Dublin's problem was that the venue was isolated from the city. This has
> also been the case with e.g. San Diego. (I'm assuming no personal car.)
> Contrast with Minneapolis (and several other places) where you were right
> in the city. Being in a city is better for lunch and dinner options, taki=
ng
> a break to go to a bookshop (or to buy something you forgot to bring) and
> so on. (I'm deliberately not including tourism here.)
>
> However at the moment my priorities to make being able to attend possible
> would be time (so the closer to me the better - I realise that's impossib=
le
> globally), cost (hotel first, flight second, rest is noise) and the abili=
ty
> to plan ahead to only attend part of the week. This is the current econom=
ic
> reality. Dublin actually scores quite well on those for me.
>
> --
> Christopher Dearlove
> Senior Principal Engineer, Communications Group
> Communications, Networks and Image Analysis Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194 |  Fax: +44 1245 242124
> chris.dearlove@baesystems.com | http://www.baesystems.com
>
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre=
,
> Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687
>
>
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Daniele Ceccarelli
> Sent: 06 August 2012 13:24
> To: Andrew Sullivan; ietf@ietf.org
> Subject: RE: So, where to repeat? (was:Re: management granularity)
>
> ----------------------! WARNING ! ----------------------
> This message originates from outside our organisation,
> either from an external partner or from the internet.
> Keep this in mind if you answer this message.
> Follow the 'Report Suspicious Emails' link on IT matters
> for instructions on reporting suspicious email messages.
> --------------------------------------------------------
>
> Dublin panned? I thought it was one of the best venues and locations of
> the last meetings.
>
> What about Italy or Spain? I've never heard about an IETF in Italy. I'm o=
k
> with meetings outside Italy since i like traveling very much, but i was
> wondering why it has never been taken into account in the past meetings. =
Is
> it expensive? I think Italy and Spain are much cheaper than France, UK or
> Sweden, aren't they?
>
> BR
> Daniele
>
> >-----Original Message-----
> >From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On
> >Behalf Of Andrew Sullivan
> >Sent: luned=EC 6 agosto 2012 14.06
> >To: ietf@ietf.org
> >Subject: So, where to repeat? (was:Re: management granularity)
> >
> >On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:
> >> enough merely to have excellent staff.  We need to go back to the
> >> better places and benefit from the learning curve.  This
> >doesn't mean
> >> "no new venues" but it means fewer.
> >
> >As a practical matter, may I ask about which venues you want
> >to return to?  I get your argument in principle, but it seems
> >to me that there has been quite a lot of complaining in the
> >past.  The one factor that seems to me most likely to reduce
> >complaints -- weather -- is evidently beyond the Secretariat's
> >or IAOC's control.
> >
> >People seem inclined to return to the Hyatt in Vancouver,
> >elevators notwithstanding.  We're going to do that.  (I don't
> >understand why the previous Vencouver venue was less desirable
> >-- to me, these venues were very similar, and not very far
> >apart.  I note, however, that the previous two Vancouver
> >visits were near the end of the year, when it rains all the
> >time in Vancouver.)
> >
> >People complained at length about the venue in Paris, so I
> >presume it's out.
> >
> >Some people complained about the hotel room prices and travel
> >expense in Taipei, though I heard remarks that it was a good venue.
> >Should we try to return there?
> >
> >People complained in advance about getting to Qu=E9bec, although
> >afterwards I heard lots of good noises about that venue.  I
> >note that the weather was great.  Should we try to return?
> >
> >I don't recall much complaining about the Prague venue in
> >2011, which was striking to me because very little seemed
> >different to me compared to our first visit there.  Perhaps
> >this is evidence of the "tuning"
> >you suggest (ensuring the water bottles were plastic, for instance).
> >But I note the weather was excellent.
> >
> >Beijing?  I guess Maastricht is out. Anaheim (FWIW, I thought
> >that was an example of a terrible location, but many people
> >seemed happy with it)?  Hiroshima?  Stockholm?  San Francisco
> >(we thought the crime at Paris was bad, yet didn't complain
> >about being smack up against the Tenderloin)?  Or there's the
> >old standby, Minneapolis; perhaps we could do it in March.
> >The Dublin venue was panned by large numbers of people.
> >Philadelphia, people complained about expense.  Chicago, too
> >(combined with hotel renovations).
> >
> >That gets us back through 2007.  Which of the venues do you
> >think we should return to, to which we already haven't
> >returned or planned to return?  And why?
> >
> >For what it's worth, I would not complain about returning to
> >any of those venues; I personally had good meetings at all of
> >them except Hiroshima, which I missed due to other
> >commitments.  That includes both Maastricht and Dublin, which
> >were both apparently trials for large numbers of others.
> >
> >Best,
> >
> >A
> >
> >--
> >Andrew Sullivan
> >ajs@anvilwalrusden.com
> >
> >
>
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************
>
>
>

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

Flights to Vancouver from some cities were extremely expensive. =A0It would=
 have cost me more than twice as much as it did to fly to Beijing, for exam=
ple, if I had taken a direct flight from DFW - it would have been by far my=
 most expensive IETF airfare ever. I didn&#39;t because I was trying to be =
cost conscious. =A0However, I could have flown to London in the same time i=
t took me to get to/from Vancouver and for about the same price. =A0This is=
 a typical problem when we go somewhere when tourists go (for some reason, =
flying to cities in Canada is very popular when the temp in Texas is 110 de=
grees F). =A0 =A0 Orlando will most likely be just as bad since it is sched=
uled during a time where many schools in DFW area have Spring Break - fligh=
t costs right now are over $500 ($560). =A0I can usually fly anywhere in th=
e U.S. for around $300 when I book early. =A0And, of course, I can&#39;t bo=
ok early as my company won&#39;t re-imburse unless I use their travel compa=
ny and have approval (which I won&#39;t get for at least another 5-6 months=
). =A0 Hopefully, the IETF negotiated hotel rate won&#39;t reflect that it =
is Spring Break. =A0=A0<div>
<br></div><div>If we were to choose one place in the U.S. to meet, Minneapo=
lis is the best choice IMHO. =A0It&#39;s very reasonably priced, easy for m=
any to get to and the hotel has adequate space for us (even back when we ha=
d many more attendees). =A0Personally, the weather is not critical to me, s=
ince I spend the vast majority of my time in the hotel meeting rooms, so I&=
#39;m very happy if we meet there in March and November. =A0=A0</div>
<div><br></div><div>Mary<div><br><div class=3D"gmail_quote">On Mon, Aug 6, =
2012 at 9:18 AM, Dearlove, Christopher (UK) <span dir=3D"ltr">&lt;<a href=
=3D"mailto:Chris.Dearlove@baesystems.com" target=3D"_blank">Chris.Dearlove@=
baesystems.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">I&#39;ve never been to an IETF meeting where=
 the plane fare has exceeded the hotel cost for a week. Caveats to that are=
 that I have mostly gone for IETF recommended hotels, so may have missed pa=
rticularly cheap hotels, and that I have only been to North American and Eu=
rope (but that statistic includes Vancouver and the even further away weste=
rn US cities down to San Diego). And of course I fly economy, and it&#39;s =
much cheaper including a Saturday night in your trip, even at the cost of a=
n extra night in a hotel (at least it is from here). An almost exception wa=
s Paris this year where I was staying fairly cheaply, but that was a cost-s=
hared trip between me and my employer, and I didn&#39;t fly (I went by trai=
n - though that&#39;s not cheaper, just better). Paris has cheap(er) hotels=
 and a metro I understand, so I felt less location constrained.<br>

<div class=3D"im HOEnZb"><br>
--<br>
Christopher Dearlove<br>
Senior Principal Engineer, Communications Group<br>
Communications, Networks and Image Analysis Capability<br>
BAE Systems Advanced Technology Centre<br>
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<br>
Tel: <a href=3D"tel:%2B44%201245%20242194" value=3D"+441245242194">+44 1245=
 242194</a>=A0| =A0Fax: <a href=3D"tel:%2B44%201245%20242124" value=3D"+441=
245242124">+44 1245 242124</a><br>
<a href=3D"mailto:chris.dearlove@baesystems.com">chris.dearlove@baesystems.=
com</a> | <a href=3D"http://www.baesystems.com" target=3D"_blank">http://ww=
w.baesystems.com</a><br>
<br>
BAE Systems (Operations) Limited<br>
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK<br>
Registered in England &amp; Wales No: 1996687<br>
<br>
<br>
-----Original Message-----<br>
</div><div class=3D"im HOEnZb">From: Sprecher, Nurit (NSN - IL/Hod HaSharon=
) [mailto:<a href=3D"mailto:nurit.sprecher@nsn.com">nurit.sprecher@nsn.com<=
/a>]<br>
Sent: 06 August 2012 15:07<br>
To: Dearlove, Christopher (UK); Daniele Ceccarelli; Andrew Sullivan; <a hre=
f=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>
Subject: RE: So, where to repeat? (was:Re: management granularity)<br>
<br>
</div><div class=3D"HOEnZb"><div class=3D"h5">----------------------! WARNI=
NG ! ----------------------<br>
This message originates from outside our organisation,<br>
either from an external partner or from the internet.<br>
Keep this in mind if you answer this message.<br>
Follow the &#39;Report Suspicious Emails&#39; link on IT matters<br>
for instructions on reporting suspicious email messages.<br>
--------------------------------------------------------<br>
<br>
When you are not close (time), flight cost may become higher in the priorit=
y (over hotem)....<br>
Flying to Vancouver for me for example is the most expensive trip....even t=
hough the city is amazing and the host was wonderful!<br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a> [m=
ailto:<a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a>] O=
n Behalf Of ext Dearlove, Christopher (UK)<br>
Sent: Monday, August 06, 2012 4:56 PM<br>
To: Daniele Ceccarelli; Andrew Sullivan; <a href=3D"mailto:ietf@ietf.org">i=
etf@ietf.org</a><br>
Subject: RE: So, where to repeat? (was:Re: management granularity)<br>
<br>
Dublin&#39;s problem was that the venue was isolated from the city. This ha=
s also been the case with e.g. San Diego. (I&#39;m assuming no personal car=
.) Contrast with Minneapolis (and several other places) where you were righ=
t in the city. Being in a city is better for lunch and dinner options, taki=
ng a break to go to a bookshop (or to buy something you forgot to bring) an=
d so on. (I&#39;m deliberately not including tourism here.)<br>

<br>
However at the moment my priorities to make being able to attend possible w=
ould be time (so the closer to me the better - I realise that&#39;s impossi=
ble globally), cost (hotel first, flight second, rest is noise) and the abi=
lity to plan ahead to only attend part of the week. This is the current eco=
nomic reality. Dublin actually scores quite well on those for me.<br>

<br>
--<br>
Christopher Dearlove<br>
Senior Principal Engineer, Communications Group<br>
Communications, Networks and Image Analysis Capability<br>
BAE Systems Advanced Technology Centre<br>
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<br>
Tel: <a href=3D"tel:%2B44%201245%20242194" value=3D"+441245242194">+44 1245=
 242194</a>=A0| =A0Fax: <a href=3D"tel:%2B44%201245%20242124" value=3D"+441=
245242124">+44 1245 242124</a><br>
<a href=3D"mailto:chris.dearlove@baesystems.com">chris.dearlove@baesystems.=
com</a> | <a href=3D"http://www.baesystems.com" target=3D"_blank">http://ww=
w.baesystems.com</a><br>
<br>
BAE Systems (Operations) Limited<br>
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK<br>
Registered in England &amp; Wales No: 1996687<br>
<br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a> [m=
ailto:<a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a>] O=
n Behalf Of Daniele Ceccarelli<br>
Sent: 06 August 2012 13:24<br>
To: Andrew Sullivan; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>
Subject: RE: So, where to repeat? (was:Re: management granularity)<br>
<br>
----------------------! WARNING ! ----------------------<br>
This message originates from outside our organisation,<br>
either from an external partner or from the internet.<br>
Keep this in mind if you answer this message.<br>
Follow the &#39;Report Suspicious Emails&#39; link on IT matters<br>
for instructions on reporting suspicious email messages.<br>
--------------------------------------------------------<br>
<br>
Dublin panned? I thought it was one of the best venues and locations of the=
 last meetings.<br>
<br>
What about Italy or Spain? I&#39;ve never heard about an IETF in Italy. I&#=
39;m ok with meetings outside Italy since i like traveling very much, but i=
 was wondering why it has never been taken into account in the past meeting=
s. Is it expensive? I think Italy and Spain are much cheaper than France, U=
K or Sweden, aren&#39;t they?<br>

<br>
BR<br>
Daniele<br>
<br>
&gt;-----Original Message-----<br>
&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<br>
&gt;Behalf Of Andrew Sullivan<br>
&gt;Sent: luned=EC 6 agosto 2012 14.06<br>
&gt;To: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>
&gt;Subject: So, where to repeat? (was:Re: management granularity)<br>
&gt;<br>
&gt;On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:<br>
&gt;&gt; enough merely to have excellent staff. =A0We need to go back to th=
e<br>
&gt;&gt; better places and benefit from the learning curve. =A0This<br>
&gt;doesn&#39;t mean<br>
&gt;&gt; &quot;no new venues&quot; but it means fewer.<br>
&gt;<br>
&gt;As a practical matter, may I ask about which venues you want<br>
&gt;to return to? =A0I get your argument in principle, but it seems<br>
&gt;to me that there has been quite a lot of complaining in the<br>
&gt;past. =A0The one factor that seems to me most likely to reduce<br>
&gt;complaints -- weather -- is evidently beyond the Secretariat&#39;s<br>
&gt;or IAOC&#39;s control.<br>
&gt;<br>
&gt;People seem inclined to return to the Hyatt in Vancouver,<br>
&gt;elevators notwithstanding. =A0We&#39;re going to do that. =A0(I don&#39=
;t<br>
&gt;understand why the previous Vencouver venue was less desirable<br>
&gt;-- to me, these venues were very similar, and not very far<br>
&gt;apart. =A0I note, however, that the previous two Vancouver<br>
&gt;visits were near the end of the year, when it rains all the<br>
&gt;time in Vancouver.)<br>
&gt;<br>
&gt;People complained at length about the venue in Paris, so I<br>
&gt;presume it&#39;s out.<br>
&gt;<br>
&gt;Some people complained about the hotel room prices and travel<br>
&gt;expense in Taipei, though I heard remarks that it was a good venue.<br>
&gt;Should we try to return there?<br>
&gt;<br>
&gt;People complained in advance about getting to Qu=E9bec, although<br>
&gt;afterwards I heard lots of good noises about that venue. =A0I<br>
&gt;note that the weather was great. =A0Should we try to return?<br>
&gt;<br>
&gt;I don&#39;t recall much complaining about the Prague venue in<br>
&gt;2011, which was striking to me because very little seemed<br>
&gt;different to me compared to our first visit there. =A0Perhaps<br>
&gt;this is evidence of the &quot;tuning&quot;<br>
&gt;you suggest (ensuring the water bottles were plastic, for instance).<br=
>
&gt;But I note the weather was excellent.<br>
&gt;<br>
&gt;Beijing? =A0I guess Maastricht is out. Anaheim (FWIW, I thought<br>
&gt;that was an example of a terrible location, but many people<br>
&gt;seemed happy with it)? =A0Hiroshima? =A0Stockholm? =A0San Francisco<br>
&gt;(we thought the crime at Paris was bad, yet didn&#39;t complain<br>
&gt;about being smack up against the Tenderloin)? =A0Or there&#39;s the<br>
&gt;old standby, Minneapolis; perhaps we could do it in March.<br>
&gt;The Dublin venue was panned by large numbers of people.<br>
&gt;Philadelphia, people complained about expense. =A0Chicago, too<br>
&gt;(combined with hotel renovations).<br>
&gt;<br>
&gt;That gets us back through 2007. =A0Which of the venues do you<br>
&gt;think we should return to, to which we already haven&#39;t<br>
&gt;returned or planned to return? =A0And why?<br>
&gt;<br>
&gt;For what it&#39;s worth, I would not complain about returning to<br>
&gt;any of those venues; I personally had good meetings at all of<br>
&gt;them except Hiroshima, which I missed due to other<br>
&gt;commitments. =A0That includes both Maastricht and Dublin, which<br>
&gt;were both apparently trials for large numbers of others.<br>
&gt;<br>
&gt;Best,<br>
&gt;<br>
&gt;A<br>
&gt;<br>
&gt;--<br>
&gt;Andrew Sullivan<br>
&gt;<a href=3D"mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><br=
>
&gt;<br>
&gt;<br>
<br>
********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************<br>
<br>
<br>
</div></div></blockquote></div><br></div></div>

--f46d04083adbe9109304c699dfbe--

From Chris.Dearlove@baesystems.com  Mon Aug  6 07:53:19 2012
Return-Path: <Chris.Dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3669D21F865F for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 07:53:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.319
X-Spam-Level: 
X-Spam-Status: No, score=-10.319 tagged_above=-999 required=5 tests=[AWL=0.279, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Yg0YXXGSpmB for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 07:53:16 -0700 (PDT)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) by ietfa.amsl.com (Postfix) with ESMTP id 19DA921F8634 for <ietf@ietf.org>; Mon,  6 Aug 2012 07:53:13 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.77,720,1336345200";  d="scan'208,217";a="261603556"
Received: from unknown (HELO baemasmds009.greenlnk.net) ([141.245.68.246]) by baemasmds003ir.sharelnk.net with ESMTP; 06 Aug 2012 15:53:13 +0100
Received: from GLKXH0002V.GREENLNK.net ([10.109.2.33]) by baemasmds009.greenlnk.net (Switch-3.4.4/Switch-3.4.4) with ESMTP id q76ErCxm030032 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 6 Aug 2012 15:53:12 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.170]) by GLKXH0002V.GREENLNK.net ([10.109.2.33]) with mapi id 14.02.0309.002; Mon, 6 Aug 2012 15:53:12 +0100
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: RE: So, where to repeat? (was:Re: management granularity)
Thread-Topic: So, where to repeat? (was:Re: management granularity)
Thread-Index: AQHNc+GWEX7RpVScC0qWyg0VTbeN8pdM3Dzw
Date: Mon, 6 Aug 2012 14:53:11 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBAA3F@GLKXM0002V.GREENLNK.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net>	<20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com>
In-Reply-To: <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: multipart/alternative; boundary="_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBAA3FGLKXM0002VGREEN_"
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Aug 2012 14:53:19 -0000

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBAA3FGLKXM0002VGREEN_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Those prices still sound like a week's hotel costs would exceed them. And I=
 would expect the cost of your time to your employer to exceed even that. I=
'm not suggesting airfare prices don't matter, not by any stretch of the im=
agination, just that they are third if you stay a whole week. Or maybe four=
th, there's also the IETF charge to consider, but that's less flexible (wee=
k or day) and not highly location dependent. Of course if you go for just a=
 day the airfare is quite likely to be number one on the list, unless the l=
ocation is relatively local.

--
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194 |  Fax: +44 1245 242124
chris.dearlove@baesystems.com<mailto:chris.dearlove@baesystems.com> | http:=
//www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687

From: Mary Barnes [mailto:mary.ietf.barnes@gmail.com]
Sent: 06 August 2012 15:42
To: Dearlove, Christopher (UK)
Cc: Sprecher, Nurit (NSN - IL/Hod HaSharon); Daniele Ceccarelli; Andrew Sul=
livan; ietf@ietf.org
Subject: Re: So, where to repeat? (was:Re: management granularity)


*** WARNING ***
This message originates from outside our organisation, either from an exter=
nal partner or the internet.
Keep this in mind if you answer this message.
Please see this process<http://intranet.ent.baesystems.com/howwework/securi=
ty/spotlights/Documents/Dealing%20With%20Suspicious%20Emails.pdf> on how to=
 deal with suspicious emails.
Flights to Vancouver from some cities were extremely expensive.  It would h=
ave cost me more than twice as much as it did to fly to Beijing, for exampl=
e, if I had taken a direct flight from DFW - it would have been by far my m=
ost expensive IETF airfare ever. I didn't because I was trying to be cost c=
onscious.  However, I could have flown to London in the same time it took m=
e to get to/from Vancouver and for about the same price.  This is a typical=
 problem when we go somewhere when tourists go (for some reason, flying to =
cities in Canada is very popular when the temp in Texas is 110 degrees F). =
    Orlando will most likely be just as bad since it is scheduled during a =
time where many schools in DFW area have Spring Break - flight costs right =
now are over $500 ($560).  I can usually fly anywhere in the U.S. for aroun=
d $300 when I book early.  And, of course, I can't book early as my company=
 won't re-imburse unless I use their travel company and have approval (whic=
h I won't get for at least another 5-6 months).   Hopefully, the IETF negot=
iated hotel rate won't reflect that it is Spring Break.

If we were to choose one place in the U.S. to meet, Minneapolis is the best=
 choice IMHO.  It's very reasonably priced, easy for many to get to and the=
 hotel has adequate space for us (even back when we had many more attendees=
).  Personally, the weather is not critical to me, since I spend the vast m=
ajority of my time in the hotel meeting rooms, so I'm very happy if we meet=
 there in March and November.

Mary

On Mon, Aug 6, 2012 at 9:18 AM, Dearlove, Christopher (UK) <Chris.Dearlove@=
baesystems.com<mailto:Chris.Dearlove@baesystems.com>> wrote:
I've never been to an IETF meeting where the plane fare has exceeded the ho=
tel cost for a week. Caveats to that are that I have mostly gone for IETF r=
ecommended hotels, so may have missed particularly cheap hotels, and that I=
 have only been to North American and Europe (but that statistic includes V=
ancouver and the even further away western US cities down to San Diego). An=
d of course I fly economy, and it's much cheaper including a Saturday night=
 in your trip, even at the cost of an extra night in a hotel (at least it i=
s from here). An almost exception was Paris this year where I was staying f=
airly cheaply, but that was a cost-shared trip between me and my employer, =
and I didn't fly (I went by train - though that's not cheaper, just better)=
. Paris has cheap(er) hotels and a metro I understand, so I felt less locat=
ion constrained.

--
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194<tel:%2B44%201245%20242194> |  Fax: +44 1245 242124<tel=
:%2B44%201245%20242124>
chris.dearlove@baesystems.com<mailto:chris.dearlove@baesystems.com> | http:=
//www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: Sprecher, Nurit (NSN - IL/Hod HaSharon) [mailto:nurit.sprecher@nsn.co=
m<mailto:nurit.sprecher@nsn.com>]
Sent: 06 August 2012 15:07
To: Dearlove, Christopher (UK); Daniele Ceccarelli; Andrew Sullivan; ietf@i=
etf.org<mailto:ietf@ietf.org>
Subject: RE: So, where to repeat? (was:Re: management granularity)
----------------------! WARNING ! ----------------------
This message originates from outside our organisation,
either from an external partner or from the internet.
Keep this in mind if you answer this message.
Follow the 'Report Suspicious Emails' link on IT matters
for instructions on reporting suspicious email messages.
--------------------------------------------------------

When you are not close (time), flight cost may become higher in the priorit=
y (over hotem)....
Flying to Vancouver for me for example is the most expensive trip....even t=
hough the city is amazing and the host was wonderful!

-----Original Message-----
From: ietf-bounces@ietf.org<mailto:ietf-bounces@ietf.org> [mailto:ietf-boun=
ces@ietf.org<mailto:ietf-bounces@ietf.org>] On Behalf Of ext Dearlove, Chri=
stopher (UK)
Sent: Monday, August 06, 2012 4:56 PM
To: Daniele Ceccarelli; Andrew Sullivan; ietf@ietf.org<mailto:ietf@ietf.org=
>
Subject: RE: So, where to repeat? (was:Re: management granularity)

Dublin's problem was that the venue was isolated from the city. This has al=
so been the case with e.g. San Diego. (I'm assuming no personal car.) Contr=
ast with Minneapolis (and several other places) where you were right in the=
 city. Being in a city is better for lunch and dinner options, taking a bre=
ak to go to a bookshop (or to buy something you forgot to bring) and so on.=
 (I'm deliberately not including tourism here.)

However at the moment my priorities to make being able to attend possible w=
ould be time (so the closer to me the better - I realise that's impossible =
globally), cost (hotel first, flight second, rest is noise) and the ability=
 to plan ahead to only attend part of the week. This is the current economi=
c reality. Dublin actually scores quite well on those for me.

--
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194<tel:%2B44%201245%20242194> |  Fax: +44 1245 242124<tel=
:%2B44%201245%20242124>
chris.dearlove@baesystems.com<mailto:chris.dearlove@baesystems.com> | http:=
//www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: ietf-bounces@ietf.org<mailto:ietf-bounces@ietf.org> [mailto:ietf-boun=
ces@ietf.org<mailto:ietf-bounces@ietf.org>] On Behalf Of Daniele Ceccarelli
Sent: 06 August 2012 13:24
To: Andrew Sullivan; ietf@ietf.org<mailto:ietf@ietf.org>
Subject: RE: So, where to repeat? (was:Re: management granularity)

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

Dublin panned? I thought it was one of the best venues and locations of the=
 last meetings.

What about Italy or Spain? I've never heard about an IETF in Italy. I'm ok =
with meetings outside Italy since i like traveling very much, but i was won=
dering why it has never been taken into account in the past meetings. Is it=
 expensive? I think Italy and Spain are much cheaper than France, UK or Swe=
den, aren't they?

BR
Daniele

>-----Original Message-----
>From: ietf-bounces@ietf.org<mailto:ietf-bounces@ietf.org> [mailto:ietf-bou=
nces@ietf.org<mailto:ietf-bounces@ietf.org>] On
>Behalf Of Andrew Sullivan
>Sent: luned=EC 6 agosto 2012 14.06
>To: ietf@ietf.org<mailto:ietf@ietf.org>
>Subject: So, where to repeat? (was:Re: management granularity)
>
>On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:
>> enough merely to have excellent staff.  We need to go back to the
>> better places and benefit from the learning curve.  This
>doesn't mean
>> "no new venues" but it means fewer.
>
>As a practical matter, may I ask about which venues you want
>to return to?  I get your argument in principle, but it seems
>to me that there has been quite a lot of complaining in the
>past.  The one factor that seems to me most likely to reduce
>complaints -- weather -- is evidently beyond the Secretariat's
>or IAOC's control.
>
>People seem inclined to return to the Hyatt in Vancouver,
>elevators notwithstanding.  We're going to do that.  (I don't
>understand why the previous Vencouver venue was less desirable
>-- to me, these venues were very similar, and not very far
>apart.  I note, however, that the previous two Vancouver
>visits were near the end of the year, when it rains all the
>time in Vancouver.)
>
>People complained at length about the venue in Paris, so I
>presume it's out.
>
>Some people complained about the hotel room prices and travel
>expense in Taipei, though I heard remarks that it was a good venue.
>Should we try to return there?
>
>People complained in advance about getting to Qu=E9bec, although
>afterwards I heard lots of good noises about that venue.  I
>note that the weather was great.  Should we try to return?
>
>I don't recall much complaining about the Prague venue in
>2011, which was striking to me because very little seemed
>different to me compared to our first visit there.  Perhaps
>this is evidence of the "tuning"
>you suggest (ensuring the water bottles were plastic, for instance).
>But I note the weather was excellent.
>
>Beijing?  I guess Maastricht is out. Anaheim (FWIW, I thought
>that was an example of a terrible location, but many people
>seemed happy with it)?  Hiroshima?  Stockholm?  San Francisco
>(we thought the crime at Paris was bad, yet didn't complain
>about being smack up against the Tenderloin)?  Or there's the
>old standby, Minneapolis; perhaps we could do it in March.
>The Dublin venue was panned by large numbers of people.
>Philadelphia, people complained about expense.  Chicago, too
>(combined with hotel renovations).
>
>That gets us back through 2007.  Which of the venues do you
>think we should return to, to which we already haven't
>returned or planned to return?  And why?
>
>For what it's worth, I would not complain about returning to
>any of those venues; I personally had good meetings at all of
>them except Hiroshima, which I missed due to other
>commitments.  That includes both Maastricht and Dublin, which
>were both apparently trials for large numbers of others.
>
>Best,
>
>A
>
>--
>Andrew Sullivan
>ajs@anvilwalrusden.com<mailto:ajs@anvilwalrusden.com>
>
>

********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************



--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBAA3FGLKXM0002VGREEN_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Those prices still sound =
like a week's hotel costs would exceed them. And I would expect the cost of=
 your time to your employer to exceed even that. I'm not
 suggesting airfare prices don't matter, not by any stretch of the imaginat=
ion, just that they are third if you stay a whole week. Or maybe fourth, th=
ere's also the IETF charge to consider, but that's less flexible (week or d=
ay) and not highly location dependent.
 Of course if you go for just a day the airfare is quite likely to be numbe=
r one on the list, unless the location is relatively local.<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
">--
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
">Christopher Dearlove<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
">Senior Principal Engineer, Communications Group<br>
Communications, Networks and Image Analysis Capability<br>
BAE Systems Advanced Technology Centre<br>
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<br>
Tel: &#43;44 1245 242194&nbsp;|&nbsp; Fax: &#43;44 1245 242124<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
"><a href=3D"mailto:chris.dearlove@baesystems.com"><span style=3D"color:#1F=
497D;text-decoration:none">chris.dearlove@baesystems.com</span></a>
 | http://www.baesystems.com<br>
<br>
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US">BAE Systems (O=
perations) Limited<br>
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK<br>
Registered in England &amp; Wales No: 1996687<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> Mary Barnes [mailto:mary.ietf.barnes@gmail.com]
<br>
<b>Sent:</b> 06 August 2012 15:42<br>
<b>To:</b> Dearlove, Christopher (UK)<br>
<b>Cc:</b> Sprecher, Nurit (NSN - IL/Hod HaSharon); Daniele Ceccarelli; And=
rew Sullivan; ietf@ietf.org<br>
<b>Subject:</b> Re: So, where to repeat? (was:Re: management granularity)<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div style=3D"border:solid black 1.0pt;padding:2.0pt 2.0pt 2.0pt 2.0pt">
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center;backgrou=
nd:white"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quo=
t;;color:black"><o:p>&nbsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center;backgrou=
nd:white"><b><span style=3D"font-size:15.0pt;font-family:&quot;Arial&quot;,=
&quot;sans-serif&quot;;color:#333972">*** WARNING ***<o:p></o:p></span></b>=
</p>
</div>
<div>
<p class=3D"MsoNormal" align=3D"center" style=3D"margin-bottom:12.0pt;text-=
align:center;background:white">
<em><span style=3D"font-size:10.5pt;font-family:&quot;Arial&quot;,&quot;san=
s-serif&quot;;color:#333972">This message originates from outside our organ=
isation, either from an external partner or the internet.</span></em><i><sp=
an style=3D"font-size:10.5pt;font-family:&quot;Arial&quot;,&quot;sans-serif=
&quot;;color:#333972"><br>
<em><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">Ke=
ep this in mind if you answer this message.</span></em><br>
<em><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">Pl=
ease see <a href=3D"http://intranet.ent.baesystems.com/howwework/security/s=
potlights/Documents/Dealing%20With%20Suspicious%20Emails.pdf">
this process</a> on how to deal with suspicious emails.</span></em></span><=
/i><span style=3D"font-size:10.5pt;font-family:&quot;Arial&quot;,&quot;sans=
-serif&quot;;color:#333972"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal">Flights to Vancouver from some cities were extremely=
 expensive. &nbsp;It would have cost me more than twice as much as it did t=
o fly to Beijing, for example, if I had taken a direct flight from DFW - it=
 would have been by far my most expensive
 IETF airfare ever. I didn't because I was trying to be cost conscious. &nb=
sp;However, I could have flown to London in the same time it took me to get=
 to/from Vancouver and for about the same price. &nbsp;This is a typical pr=
oblem when we go somewhere when tourists go
 (for some reason, flying to cities in Canada is very popular when the temp=
 in Texas is 110 degrees F). &nbsp; &nbsp; Orlando will most likely be just=
 as bad since it is scheduled during a time where many schools in DFW area =
have Spring Break - flight costs right now
 are over $500 ($560). &nbsp;I can usually fly anywhere in the U.S. for aro=
und $300 when I book early. &nbsp;And, of course, I can't book early as my =
company won't re-imburse unless I use their travel company and have approva=
l (which I won't get for at least another
 5-6 months). &nbsp; Hopefully, the IETF negotiated hotel rate won't reflec=
t that it is Spring Break. &nbsp;&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">If we were to choose one place in the U.S. to meet, =
Minneapolis is the best choice IMHO. &nbsp;It's very reasonably priced, eas=
y for many to get to and the hotel has adequate space for us (even back whe=
n we had many more attendees). &nbsp;Personally,
 the weather is not critical to me, since I spend the vast majority of my t=
ime in the hotel meeting rooms, so I'm very happy if we meet there in March=
 and November. &nbsp;&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Mary<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Mon, Aug 6, 2012 at 9:18 AM, Dearlove, Christophe=
r (UK) &lt;<a href=3D"mailto:Chris.Dearlove@baesystems.com" target=3D"_blan=
k">Chris.Dearlove@baesystems.com</a>&gt; wrote:<o:p></o:p></p>
<p class=3D"MsoNormal">I've never been to an IETF meeting where the plane f=
are has exceeded the hotel cost for a week. Caveats to that are that I have=
 mostly gone for IETF recommended hotels, so may have missed particularly c=
heap hotels, and that I have only
 been to North American and Europe (but that statistic includes Vancouver a=
nd the even further away western US cities down to San Diego). And of cours=
e I fly economy, and it's much cheaper including a Saturday night in your t=
rip, even at the cost of an extra
 night in a hotel (at least it is from here). An almost exception was Paris=
 this year where I was staying fairly cheaply, but that was a cost-shared t=
rip between me and my employer, and I didn't fly (I went by train - though =
that's not cheaper, just better).
 Paris has cheap(er) hotels and a metro I understand, so I felt less locati=
on constrained.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><br>
--<br>
Christopher Dearlove<br>
Senior Principal Engineer, Communications Group<br>
Communications, Networks and Image Analysis Capability<br>
BAE Systems Advanced Technology Centre<br>
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<br>
Tel: <a href=3D"tel:%2B44%201245%20242194">&#43;44 1245 242194</a>&nbsp;| &=
nbsp;Fax: <a href=3D"tel:%2B44%201245%20242124">
&#43;44 1245 242124</a><br>
<a href=3D"mailto:chris.dearlove@baesystems.com">chris.dearlove@baesystems.=
com</a> |
<a href=3D"http://www.baesystems.com" target=3D"_blank">http://www.baesyste=
ms.com</a><br>
<br>
BAE Systems (Operations) Limited<br>
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK<br>
Registered in England &amp; Wales No: 1996687<br>
<br>
<br>
-----Original Message-----<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">From: Sprecher, Nurit=
 (NSN - IL/Hod HaSharon) [mailto:<a href=3D"mailto:nurit.sprecher@nsn.com">=
nurit.sprecher@nsn.com</a>]<br>
Sent: 06 August 2012 15:07<br>
To: Dearlove, Christopher (UK); Daniele Ceccarelli; Andrew Sullivan; <a hre=
f=3D"mailto:ietf@ietf.org">
ietf@ietf.org</a><br>
Subject: RE: So, where to repeat? (was:Re: management granularity)<o:p></o:=
p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">---------------------=
-! WARNING ! ----------------------<br>
This message originates from outside our organisation,<br>
either from an external partner or from the internet.<br>
Keep this in mind if you answer this message.<br>
Follow the 'Report Suspicious Emails' link on IT matters<br>
for instructions on reporting suspicious email messages.<br>
--------------------------------------------------------<br>
<br>
When you are not close (time), flight cost may become higher in the priorit=
y (over hotem)....<br>
Flying to Vancouver for me for example is the most expensive trip....even t=
hough the city is amazing and the host was wonderful!<br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a> [m=
ailto:<a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a>] O=
n Behalf Of ext Dearlove, Christopher (UK)<br>
Sent: Monday, August 06, 2012 4:56 PM<br>
To: Daniele Ceccarelli; Andrew Sullivan; <a href=3D"mailto:ietf@ietf.org">i=
etf@ietf.org</a><br>
Subject: RE: So, where to repeat? (was:Re: management granularity)<br>
<br>
Dublin's problem was that the venue was isolated from the city. This has al=
so been the case with e.g. San Diego. (I'm assuming no personal car.) Contr=
ast with Minneapolis (and several other places) where you were right in the=
 city. Being in a city is better
 for lunch and dinner options, taking a break to go to a bookshop (or to bu=
y something you forgot to bring) and so on. (I'm deliberately not including=
 tourism here.)<br>
<br>
However at the moment my priorities to make being able to attend possible w=
ould be time (so the closer to me the better - I realise that's impossible =
globally), cost (hotel first, flight second, rest is noise) and the ability=
 to plan ahead to only attend part
 of the week. This is the current economic reality. Dublin actually scores =
quite well on those for me.<br>
<br>
--<br>
Christopher Dearlove<br>
Senior Principal Engineer, Communications Group<br>
Communications, Networks and Image Analysis Capability<br>
BAE Systems Advanced Technology Centre<br>
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<br>
Tel: <a href=3D"tel:%2B44%201245%20242194">&#43;44 1245 242194</a>&nbsp;| &=
nbsp;Fax: <a href=3D"tel:%2B44%201245%20242124">
&#43;44 1245 242124</a><br>
<a href=3D"mailto:chris.dearlove@baesystems.com">chris.dearlove@baesystems.=
com</a> |
<a href=3D"http://www.baesystems.com" target=3D"_blank">http://www.baesyste=
ms.com</a><br>
<br>
BAE Systems (Operations) Limited<br>
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK<br>
Registered in England &amp; Wales No: 1996687<br>
<br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a> [m=
ailto:<a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a>] O=
n Behalf Of Daniele Ceccarelli<br>
Sent: 06 August 2012 13:24<br>
To: Andrew Sullivan; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>
Subject: RE: So, where to repeat? (was:Re: management granularity)<br>
<br>
----------------------! WARNING ! ----------------------<br>
This message originates from outside our organisation,<br>
either from an external partner or from the internet.<br>
Keep this in mind if you answer this message.<br>
Follow the 'Report Suspicious Emails' link on IT matters<br>
for instructions on reporting suspicious email messages.<br>
--------------------------------------------------------<br>
<br>
Dublin panned? I thought it was one of the best venues and locations of the=
 last meetings.<br>
<br>
What about Italy or Spain? I've never heard about an IETF in Italy. I'm ok =
with meetings outside Italy since i like traveling very much, but i was won=
dering why it has never been taken into account in the past meetings. Is it=
 expensive? I think Italy and Spain
 are much cheaper than France, UK or Sweden, aren't they?<br>
<br>
BR<br>
Daniele<br>
<br>
&gt;-----Original Message-----<br>
&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<br>
&gt;Behalf Of Andrew Sullivan<br>
&gt;Sent: luned=EC 6 agosto 2012 14.06<br>
&gt;To: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>
&gt;Subject: So, where to repeat? (was:Re: management granularity)<br>
&gt;<br>
&gt;On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:<br>
&gt;&gt; enough merely to have excellent staff. &nbsp;We need to go back to=
 the<br>
&gt;&gt; better places and benefit from the learning curve. &nbsp;This<br>
&gt;doesn't mean<br>
&gt;&gt; &quot;no new venues&quot; but it means fewer.<br>
&gt;<br>
&gt;As a practical matter, may I ask about which venues you want<br>
&gt;to return to? &nbsp;I get your argument in principle, but it seems<br>
&gt;to me that there has been quite a lot of complaining in the<br>
&gt;past. &nbsp;The one factor that seems to me most likely to reduce<br>
&gt;complaints -- weather -- is evidently beyond the Secretariat's<br>
&gt;or IAOC's control.<br>
&gt;<br>
&gt;People seem inclined to return to the Hyatt in Vancouver,<br>
&gt;elevators notwithstanding. &nbsp;We're going to do that. &nbsp;(I don't=
<br>
&gt;understand why the previous Vencouver venue was less desirable<br>
&gt;-- to me, these venues were very similar, and not very far<br>
&gt;apart. &nbsp;I note, however, that the previous two Vancouver<br>
&gt;visits were near the end of the year, when it rains all the<br>
&gt;time in Vancouver.)<br>
&gt;<br>
&gt;People complained at length about the venue in Paris, so I<br>
&gt;presume it's out.<br>
&gt;<br>
&gt;Some people complained about the hotel room prices and travel<br>
&gt;expense in Taipei, though I heard remarks that it was a good venue.<br>
&gt;Should we try to return there?<br>
&gt;<br>
&gt;People complained in advance about getting to Qu=E9bec, although<br>
&gt;afterwards I heard lots of good noises about that venue. &nbsp;I<br>
&gt;note that the weather was great. &nbsp;Should we try to return?<br>
&gt;<br>
&gt;I don't recall much complaining about the Prague venue in<br>
&gt;2011, which was striking to me because very little seemed<br>
&gt;different to me compared to our first visit there. &nbsp;Perhaps<br>
&gt;this is evidence of the &quot;tuning&quot;<br>
&gt;you suggest (ensuring the water bottles were plastic, for instance).<br=
>
&gt;But I note the weather was excellent.<br>
&gt;<br>
&gt;Beijing? &nbsp;I guess Maastricht is out. Anaheim (FWIW, I thought<br>
&gt;that was an example of a terrible location, but many people<br>
&gt;seemed happy with it)? &nbsp;Hiroshima? &nbsp;Stockholm? &nbsp;San Fran=
cisco<br>
&gt;(we thought the crime at Paris was bad, yet didn't complain<br>
&gt;about being smack up against the Tenderloin)? &nbsp;Or there's the<br>
&gt;old standby, Minneapolis; perhaps we could do it in March.<br>
&gt;The Dublin venue was panned by large numbers of people.<br>
&gt;Philadelphia, people complained about expense. &nbsp;Chicago, too<br>
&gt;(combined with hotel renovations).<br>
&gt;<br>
&gt;That gets us back through 2007. &nbsp;Which of the venues do you<br>
&gt;think we should return to, to which we already haven't<br>
&gt;returned or planned to return? &nbsp;And why?<br>
&gt;<br>
&gt;For what it's worth, I would not complain about returning to<br>
&gt;any of those venues; I personally had good meetings at all of<br>
&gt;them except Hiroshima, which I missed due to other<br>
&gt;commitments. &nbsp;That includes both Maastricht and Dublin, which<br>
&gt;were both apparently trials for large numbers of others.<br>
&gt;<br>
&gt;Best,<br>
&gt;<br>
&gt;A<br>
&gt;<br>
&gt;--<br>
&gt;Andrew Sullivan<br>
&gt;<a href=3D"mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><br=
>
&gt;<br>
&gt;<br>
<br>
********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************<br>
<br>
<o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBAA3FGLKXM0002VGREEN_--

From mary.ietf.barnes@gmail.com  Mon Aug  6 07:55:15 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1D3621F8672 for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 07:55:15 -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=0.069, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eOGs57OX0+bw for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 07:55:12 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id CA3D521F865F for <ietf@ietf.org>; Mon,  6 Aug 2012 07:55:11 -0700 (PDT)
Received: by lahm15 with SMTP id m15so1690764lah.31 for <ietf@ietf.org>; Mon, 06 Aug 2012 07:55:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=B+FaJRJUdyK0fL28vXkYNCg93hx2Xmha7VPF7ZpmSc0=; b=znhOtvSYXQkiIW3rCaNub10VlOLWqrKN+WYIRHXLNs1DjQ/EdlWTn0NUf4M/+PJoiz d2W6loPctP5g9lviIcvhK48X7+SnT+t8S+y5kS+ZaGE44j2VzkYOJgn7rVfcaT+fUviw JEpI/TtQwQTClsbe4U34OhdZ+ZtdCj1PJgl8iT+WI4MSWqjoMGvk7M+F1jyVj9RZpaMp lpdenXWg4YisdUs+HNQVEeFBnmpEfTElCu9/2WT+ti6mpnSWfOInH0i7Wfog1ytZ+mWH H1fali1dS30zWEcNTlrhL48J+fsCV/EwGUNpMAhH0DI+vEL3Dn9MXe2TXGZea02ybIwb zjfQ==
MIME-Version: 1.0
Received: by 10.112.40.33 with SMTP id u1mr4778980lbk.28.1344264908439; Mon, 06 Aug 2012 07:55:08 -0700 (PDT)
Received: by 10.112.85.196 with HTTP; Mon, 6 Aug 2012 07:55:08 -0700 (PDT)
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBAA3F@GLKXM0002V.GREENLNK.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBAA3F@GLKXM0002V.GREENLNK.net>
Date: Mon, 6 Aug 2012 09:55:08 -0500
Message-ID: <CAHBDyN705BHK7NGUQMZfBRZ2VssMUjVrLZs9HrW0qQXgqz+Npg@mail.gmail.com>
Subject: Re: So, where to repeat? (was:Re: management granularity)
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
Content-Type: multipart/alternative; boundary=e0cb4efe30605a017e04c69a106f
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, 06 Aug 2012 14:55:16 -0000

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

The only reason why a RT direct airfare would not have exceeded hotel costs
was because I came early as I attended another meeting in San JOse just
prior to IETF and I was attending a workshop on Saturday. If I had arrived
on Saturday the direct RT airfare would have exceeded hotel costs.

Mary.

On Mon, Aug 6, 2012 at 9:53 AM, Dearlove, Christopher (UK) <
Chris.Dearlove@baesystems.com> wrote:

>  Those prices still sound like a week's hotel costs would exceed them.
> And I would expect the cost of your time to your employer to exceed even
> that. I'm not suggesting airfare prices don't matter, not by any stretch =
of
> the imagination, just that they are third if you stay a whole week. Or
> maybe fourth, there's also the IETF charge to consider, but that's less
> flexible (week or day) and not highly location dependent. Of course if yo=
u
> go for just a day the airfare is quite likely to be number one on the lis=
t,
> unless the location is relatively local.****
>
> ** **
>
> -- ****
>
> Christopher Dearlove****
>
> Senior Principal Engineer, Communications Group
> Communications, Networks and Image Analysis Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194 |  Fax: +44 1245 242124****
>
> chris.dearlove@baesystems.com | http://www.baesystems.com
>
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre=
,
> Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687****
>
> ** **
>
> *From:* Mary Barnes [mailto:mary.ietf.barnes@gmail.com]
> *Sent:* 06 August 2012 15:42
> *To:* Dearlove, Christopher (UK)
> *Cc:* Sprecher, Nurit (NSN - IL/Hod HaSharon); Daniele Ceccarelli; Andrew
> Sullivan; ietf@ietf.org
> *Subject:* Re: So, where to repeat? (was:Re: management granularity)****
>
> ** **
>
> ** **
>
> **** WARNING ****
>
> *This message originates from outside our organisation, either from an
> external partner or the internet.***
> *
> Keep this in mind if you answer this message.
> *
> *Please see this process<http://intranet.ent.baesystems.com/howwework/sec=
urity/spotlights/Documents/Dealing%20With%20Suspicious%20Emails.pdf>on how =
to deal with suspicious emails.
> *****
>
>  Flights to Vancouver from some cities were extremely expensive.  It
> would have cost me more than twice as much as it did to fly to Beijing, f=
or
> example, if I had taken a direct flight from DFW - it would have been by
> far my most expensive IETF airfare ever. I didn't because I was trying to
> be cost conscious.  However, I could have flown to London in the same tim=
e
> it took me to get to/from Vancouver and for about the same price.  This i=
s
> a typical problem when we go somewhere when tourists go (for some reason,
> flying to cities in Canada is very popular when the temp in Texas is 110
> degrees F).     Orlando will most likely be just as bad since it is
> scheduled during a time where many schools in DFW area have Spring Break =
-
> flight costs right now are over $500 ($560).  I can usually fly anywhere =
in
> the U.S. for around $300 when I book early.  And, of course, I can't book
> early as my company won't re-imburse unless I use their travel company an=
d
> have approval (which I won't get for at least another 5-6 months).
> Hopefully, the IETF negotiated hotel rate won't reflect that it is Spring
> Break.   ****
>
> ** **
>
> If we were to choose one place in the U.S. to meet, Minneapolis is the
> best choice IMHO.  It's very reasonably priced, easy for many to get to a=
nd
> the hotel has adequate space for us (even back when we had many more
> attendees).  Personally, the weather is not critical to me, since I spend
> the vast majority of my time in the hotel meeting rooms, so I'm very happ=
y
> if we meet there in March and November.   ****
>
> ** **
>
> Mary****
>
> ** **
>
> On Mon, Aug 6, 2012 at 9:18 AM, Dearlove, Christopher (UK) <
> Chris.Dearlove@baesystems.com> wrote:****
>
> I've never been to an IETF meeting where the plane fare has exceeded the
> hotel cost for a week. Caveats to that are that I have mostly gone for IE=
TF
> recommended hotels, so may have missed particularly cheap hotels, and tha=
t
> I have only been to North American and Europe (but that statistic include=
s
> Vancouver and the even further away western US cities down to San Diego).
> And of course I fly economy, and it's much cheaper including a Saturday
> night in your trip, even at the cost of an extra night in a hotel (at lea=
st
> it is from here). An almost exception was Paris this year where I was
> staying fairly cheaply, but that was a cost-shared trip between me and my
> employer, and I didn't fly (I went by train - though that's not cheaper,
> just better). Paris has cheap(er) hotels and a metro I understand, so I
> felt less location constrained.****
>
>
> --
> Christopher Dearlove
> Senior Principal Engineer, Communications Group
> Communications, Networks and Image Analysis Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194 |  Fax: +44 1245 242124
> chris.dearlove@baesystems.com | http://www.baesystems.com
>
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre=
,
> Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687
>
>
> -----Original Message-----****
>
> From: Sprecher, Nurit (NSN - IL/Hod HaSharon) [mailto:
> nurit.sprecher@nsn.com]
> Sent: 06 August 2012 15:07
> To: Dearlove, Christopher (UK); Daniele Ceccarelli; Andrew Sullivan;
> ietf@ietf.org
> Subject: RE: So, where to repeat? (was:Re: management granularity)****
>
> ----------------------! WARNING ! ----------------------
> This message originates from outside our organisation,
> either from an external partner or from the internet.
> Keep this in mind if you answer this message.
> Follow the 'Report Suspicious Emails' link on IT matters
> for instructions on reporting suspicious email messages.
> --------------------------------------------------------
>
> When you are not close (time), flight cost may become higher in the
> priority (over hotem)....
> Flying to Vancouver for me for example is the most expensive trip....even
> though the city is amazing and the host was wonderful!
>
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> ext Dearlove, Christopher (UK)
> Sent: Monday, August 06, 2012 4:56 PM
> To: Daniele Ceccarelli; Andrew Sullivan; ietf@ietf.org
> Subject: RE: So, where to repeat? (was:Re: management granularity)
>
> Dublin's problem was that the venue was isolated from the city. This has
> also been the case with e.g. San Diego. (I'm assuming no personal car.)
> Contrast with Minneapolis (and several other places) where you were right
> in the city. Being in a city is better for lunch and dinner options, taki=
ng
> a break to go to a bookshop (or to buy something you forgot to bring) and
> so on. (I'm deliberately not including tourism here.)
>
> However at the moment my priorities to make being able to attend possible
> would be time (so the closer to me the better - I realise that's impossib=
le
> globally), cost (hotel first, flight second, rest is noise) and the abili=
ty
> to plan ahead to only attend part of the week. This is the current econom=
ic
> reality. Dublin actually scores quite well on those for me.
>
> --
> Christopher Dearlove
> Senior Principal Engineer, Communications Group
> Communications, Networks and Image Analysis Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194 |  Fax: +44 1245 242124
> chris.dearlove@baesystems.com | http://www.baesystems.com
>
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre=
,
> Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687
>
>
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Daniele Ceccarelli
> Sent: 06 August 2012 13:24
> To: Andrew Sullivan; ietf@ietf.org
> Subject: RE: So, where to repeat? (was:Re: management granularity)
>
> ----------------------! WARNING ! ----------------------
> This message originates from outside our organisation,
> either from an external partner or from the internet.
> Keep this in mind if you answer this message.
> Follow the 'Report Suspicious Emails' link on IT matters
> for instructions on reporting suspicious email messages.
> --------------------------------------------------------
>
> Dublin panned? I thought it was one of the best venues and locations of
> the last meetings.
>
> What about Italy or Spain? I've never heard about an IETF in Italy. I'm o=
k
> with meetings outside Italy since i like traveling very much, but i was
> wondering why it has never been taken into account in the past meetings. =
Is
> it expensive? I think Italy and Spain are much cheaper than France, UK or
> Sweden, aren't they?
>
> BR
> Daniele
>
> >-----Original Message-----
> >From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On
> >Behalf Of Andrew Sullivan
> >Sent: luned=EC 6 agosto 2012 14.06
> >To: ietf@ietf.org
> >Subject: So, where to repeat? (was:Re: management granularity)
> >
> >On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:
> >> enough merely to have excellent staff.  We need to go back to the
> >> better places and benefit from the learning curve.  This
> >doesn't mean
> >> "no new venues" but it means fewer.
> >
> >As a practical matter, may I ask about which venues you want
> >to return to?  I get your argument in principle, but it seems
> >to me that there has been quite a lot of complaining in the
> >past.  The one factor that seems to me most likely to reduce
> >complaints -- weather -- is evidently beyond the Secretariat's
> >or IAOC's control.
> >
> >People seem inclined to return to the Hyatt in Vancouver,
> >elevators notwithstanding.  We're going to do that.  (I don't
> >understand why the previous Vencouver venue was less desirable
> >-- to me, these venues were very similar, and not very far
> >apart.  I note, however, that the previous two Vancouver
> >visits were near the end of the year, when it rains all the
> >time in Vancouver.)
> >
> >People complained at length about the venue in Paris, so I
> >presume it's out.
> >
> >Some people complained about the hotel room prices and travel
> >expense in Taipei, though I heard remarks that it was a good venue.
> >Should we try to return there?
> >
> >People complained in advance about getting to Qu=E9bec, although
> >afterwards I heard lots of good noises about that venue.  I
> >note that the weather was great.  Should we try to return?
> >
> >I don't recall much complaining about the Prague venue in
> >2011, which was striking to me because very little seemed
> >different to me compared to our first visit there.  Perhaps
> >this is evidence of the "tuning"
> >you suggest (ensuring the water bottles were plastic, for instance).
> >But I note the weather was excellent.
> >
> >Beijing?  I guess Maastricht is out. Anaheim (FWIW, I thought
> >that was an example of a terrible location, but many people
> >seemed happy with it)?  Hiroshima?  Stockholm?  San Francisco
> >(we thought the crime at Paris was bad, yet didn't complain
> >about being smack up against the Tenderloin)?  Or there's the
> >old standby, Minneapolis; perhaps we could do it in March.
> >The Dublin venue was panned by large numbers of people.
> >Philadelphia, people complained about expense.  Chicago, too
> >(combined with hotel renovations).
> >
> >That gets us back through 2007.  Which of the venues do you
> >think we should return to, to which we already haven't
> >returned or planned to return?  And why?
> >
> >For what it's worth, I would not complain about returning to
> >any of those venues; I personally had good meetings at all of
> >them except Hiroshima, which I missed due to other
> >commitments.  That includes both Maastricht and Dublin, which
> >were both apparently trials for large numbers of others.
> >
> >Best,
> >
> >A
> >
> >--
> >Andrew Sullivan
> >ajs@anvilwalrusden.com
> >
> >
>
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************
>
> ****
>
> ** **
>

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

The only reason why a RT direct airfare would not have exceeded hotel costs=
 was because I came early as I attended another meeting in San JOse just pr=
ior to IETF and I was attending a workshop on Saturday. If I had arrived on=
 Saturday the direct RT airfare would have exceeded hotel costs.<div>
<br></div><div>Mary.=A0<br><br><div class=3D"gmail_quote">On Mon, Aug 6, 20=
12 at 9:53 AM, Dearlove, Christopher (UK) <span dir=3D"ltr">&lt;<a href=3D"=
mailto:Chris.Dearlove@baesystems.com" target=3D"_blank">Chris.Dearlove@baes=
ystems.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Those prices still sound =
like a week&#39;s hotel costs would exceed them. And I would expect the cos=
t of your time to your employer to exceed even that. I&#39;m not
 suggesting airfare prices don&#39;t matter, not by any stretch of the imag=
ination, just that they are third if you stay a whole week. Or maybe fourth=
, there&#39;s also the IETF charge to consider, but that&#39;s less flexibl=
e (week or day) and not highly location dependent.
 Of course if you go for just a day the airfare is quite likely to be numbe=
r one on the list, unless the location is relatively local.<u></u><u></u></=
span></p><div class=3D"im">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">--
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Christopher Dearlove<u></=
u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Senior Principal Engineer=
, Communications Group<br>
Communications, Networks and Image Analysis Capability<br>
BAE Systems Advanced Technology Centre<br>
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<br>
Tel: <a href=3D"tel:%2B44%201245%20242194" value=3D"+441245242194" target=
=3D"_blank">+44 1245 242194</a>=A0|=A0 Fax: <a href=3D"tel:%2B44%201245%202=
42124" value=3D"+441245242124" target=3D"_blank">+44 1245 242124</a><u></u>=
<u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><a href=3D"mailto:chris.d=
earlove@baesystems.com" target=3D"_blank"><span style=3D"color:#1f497d;text=
-decoration:none">chris.dearlove@baesystems.com</span></a>
 | <a href=3D"http://www.baesystems.com" target=3D"_blank">http://www.baesy=
stems.com</a><br>
<br>
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1f497d">BAE Systems (Operations) Limited<br>
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK<br>
Registered in England &amp; Wales No: 1996687<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
</div><p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.=
0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b>=
<span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quo=
t;,&quot;sans-serif&quot;"> Mary Barnes [mailto:<a href=3D"mailto:mary.ietf=
.barnes@gmail.com" target=3D"_blank">mary.ietf.barnes@gmail.com</a>]
<br>
<b>Sent:</b> 06 August 2012 15:42<br>
<b>To:</b> Dearlove, Christopher (UK)<br>
<b>Cc:</b> Sprecher, Nurit (NSN - IL/Hod HaSharon); Daniele Ceccarelli; And=
rew Sullivan; <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.=
org</a><br>
<b>Subject:</b> Re: So, where to repeat? (was:Re: management granularity)<u=
></u><u></u></span></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div style=3D"border:solid black 1.0pt;padding:2.0pt 2.0pt 2.0pt 2.0pt">
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center;backgrou=
nd:white"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quo=
t;"><u></u>=A0<u></u></span></p>
<div>
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center;backgrou=
nd:white"><b><span style=3D"font-size:15.0pt;font-family:&quot;Arial&quot;,=
&quot;sans-serif&quot;;color:#333972">*** WARNING ***<u></u><u></u></span><=
/b></p>

</div>
<div>
<p class=3D"MsoNormal" align=3D"center" style=3D"margin-bottom:12.0pt;text-=
align:center;background:white">
<em><span style=3D"font-size:10.5pt;font-family:&quot;Arial&quot;,&quot;san=
s-serif&quot;;color:#333972">This message originates from outside our organ=
isation, either from an external partner or the internet.</span></em><i><sp=
an style=3D"font-size:10.5pt;font-family:&quot;Arial&quot;,&quot;sans-serif=
&quot;;color:#333972"></span></i></p>
<div class=3D"im"><i><br>
<em><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">Ke=
ep this in mind if you answer this message.</span></em><br>
</i></div><i><em><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;">Please see <a href=3D"http://intranet.ent.baesystems.com/howwewo=
rk/security/spotlights/Documents/Dealing%20With%20Suspicious%20Emails.pdf" =
target=3D"_blank">
this process</a> on how to deal with suspicious emails.</span></em></i><spa=
n style=3D"font-size:10.5pt;font-family:&quot;Arial&quot;,&quot;sans-serif&=
quot;;color:#333972"><u></u><u></u></span><p></p>
</div>
</div><div><div class=3D"h5">
<p class=3D"MsoNormal">Flights to Vancouver from some cities were extremely=
 expensive. =A0It would have cost me more than twice as much as it did to f=
ly to Beijing, for example, if I had taken a direct flight from DFW - it wo=
uld have been by far my most expensive
 IETF airfare ever. I didn&#39;t because I was trying to be cost conscious.=
 =A0However, I could have flown to London in the same time it took me to ge=
t to/from Vancouver and for about the same price. =A0This is a typical prob=
lem when we go somewhere when tourists go
 (for some reason, flying to cities in Canada is very popular when the temp=
 in Texas is 110 degrees F). =A0 =A0 Orlando will most likely be just as ba=
d since it is scheduled during a time where many schools in DFW area have S=
pring Break - flight costs right now
 are over $500 ($560). =A0I can usually fly anywhere in the U.S. for around=
 $300 when I book early. =A0And, of course, I can&#39;t book early as my co=
mpany won&#39;t re-imburse unless I use their travel company and have appro=
val (which I won&#39;t get for at least another
 5-6 months). =A0 Hopefully, the IETF negotiated hotel rate won&#39;t refle=
ct that it is Spring Break. =A0=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">If we were to choose one place in the U.S. to meet, =
Minneapolis is the best choice IMHO. =A0It&#39;s very reasonably priced, ea=
sy for many to get to and the hotel has adequate space for us (even back wh=
en we had many more attendees). =A0Personally,
 the weather is not critical to me, since I spend the vast majority of my t=
ime in the hotel meeting rooms, so I&#39;m very happy if we meet there in M=
arch and November. =A0=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Mary<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Mon, Aug 6, 2012 at 9:18 AM, Dearlove, Christophe=
r (UK) &lt;<a href=3D"mailto:Chris.Dearlove@baesystems.com" target=3D"_blan=
k">Chris.Dearlove@baesystems.com</a>&gt; wrote:<u></u><u></u></p>
<p class=3D"MsoNormal">I&#39;ve never been to an IETF meeting where the pla=
ne fare has exceeded the hotel cost for a week. Caveats to that are that I =
have mostly gone for IETF recommended hotels, so may have missed particular=
ly cheap hotels, and that I have only
 been to North American and Europe (but that statistic includes Vancouver a=
nd the even further away western US cities down to San Diego). And of cours=
e I fly economy, and it&#39;s much cheaper including a Saturday night in yo=
ur trip, even at the cost of an extra
 night in a hotel (at least it is from here). An almost exception was Paris=
 this year where I was staying fairly cheaply, but that was a cost-shared t=
rip between me and my employer, and I didn&#39;t fly (I went by train - tho=
ugh that&#39;s not cheaper, just better).
 Paris has cheap(er) hotels and a metro I understand, so I felt less locati=
on constrained.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><br>
--<br>
Christopher Dearlove<br>
Senior Principal Engineer, Communications Group<br>
Communications, Networks and Image Analysis Capability<br>
BAE Systems Advanced Technology Centre<br>
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<br>
Tel: <a href=3D"tel:%2B44%201245%20242194" target=3D"_blank">+44 1245 24219=
4</a>=A0| =A0Fax: <a href=3D"tel:%2B44%201245%20242124" target=3D"_blank">
+44 1245 242124</a><br>
<a href=3D"mailto:chris.dearlove@baesystems.com" target=3D"_blank">chris.de=
arlove@baesystems.com</a> |
<a href=3D"http://www.baesystems.com" target=3D"_blank">http://www.baesyste=
ms.com</a><br>
<br>
BAE Systems (Operations) Limited<br>
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK<br>
Registered in England &amp; Wales No: 1996687<br>
<br>
<br>
-----Original Message-----<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">From: Sprecher, Nurit=
 (NSN - IL/Hod HaSharon) [mailto:<a href=3D"mailto:nurit.sprecher@nsn.com" =
target=3D"_blank">nurit.sprecher@nsn.com</a>]<br>
Sent: 06 August 2012 15:07<br>
To: Dearlove, Christopher (UK); Daniele Ceccarelli; Andrew Sullivan; <a hre=
f=3D"mailto:ietf@ietf.org" target=3D"_blank">
ietf@ietf.org</a><br>
Subject: RE: So, where to repeat? (was:Re: management granularity)<u></u><u=
></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">---------------------=
-! WARNING ! ----------------------<br>
This message originates from outside our organisation,<br>
either from an external partner or from the internet.<br>
Keep this in mind if you answer this message.<br>
Follow the &#39;Report Suspicious Emails&#39; link on IT matters<br>
for instructions on reporting suspicious email messages.<br>
--------------------------------------------------------<br>
<br>
When you are not close (time), flight cost may become higher in the priorit=
y (over hotem)....<br>
Flying to Vancouver for me for example is the most expensive trip....even t=
hough the city is amazing and the host was wonderful!<br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:ietf-bounces@ietf.org" target=3D"_blank">ietf-bounc=
es@ietf.org</a> [mailto:<a href=3D"mailto:ietf-bounces@ietf.org" target=3D"=
_blank">ietf-bounces@ietf.org</a>] On Behalf Of ext Dearlove, Christopher (=
UK)<br>

Sent: Monday, August 06, 2012 4:56 PM<br>
To: Daniele Ceccarelli; Andrew Sullivan; <a href=3D"mailto:ietf@ietf.org" t=
arget=3D"_blank">ietf@ietf.org</a><br>
Subject: RE: So, where to repeat? (was:Re: management granularity)<br>
<br>
Dublin&#39;s problem was that the venue was isolated from the city. This ha=
s also been the case with e.g. San Diego. (I&#39;m assuming no personal car=
.) Contrast with Minneapolis (and several other places) where you were righ=
t in the city. Being in a city is better
 for lunch and dinner options, taking a break to go to a bookshop (or to bu=
y something you forgot to bring) and so on. (I&#39;m deliberately not inclu=
ding tourism here.)<br>
<br>
However at the moment my priorities to make being able to attend possible w=
ould be time (so the closer to me the better - I realise that&#39;s impossi=
ble globally), cost (hotel first, flight second, rest is noise) and the abi=
lity to plan ahead to only attend part
 of the week. This is the current economic reality. Dublin actually scores =
quite well on those for me.<br>
<br>
--<br>
Christopher Dearlove<br>
Senior Principal Engineer, Communications Group<br>
Communications, Networks and Image Analysis Capability<br>
BAE Systems Advanced Technology Centre<br>
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<br>
Tel: <a href=3D"tel:%2B44%201245%20242194" target=3D"_blank">+44 1245 24219=
4</a>=A0| =A0Fax: <a href=3D"tel:%2B44%201245%20242124" target=3D"_blank">
+44 1245 242124</a><br>
<a href=3D"mailto:chris.dearlove@baesystems.com" target=3D"_blank">chris.de=
arlove@baesystems.com</a> |
<a href=3D"http://www.baesystems.com" target=3D"_blank">http://www.baesyste=
ms.com</a><br>
<br>
BAE Systems (Operations) Limited<br>
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK<br>
Registered in England &amp; Wales No: 1996687<br>
<br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:ietf-bounces@ietf.org" target=3D"_blank">ietf-bounc=
es@ietf.org</a> [mailto:<a href=3D"mailto:ietf-bounces@ietf.org" target=3D"=
_blank">ietf-bounces@ietf.org</a>] On Behalf Of Daniele Ceccarelli<br>
Sent: 06 August 2012 13:24<br>
To: Andrew Sullivan; <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">iet=
f@ietf.org</a><br>
Subject: RE: So, where to repeat? (was:Re: management granularity)<br>
<br>
----------------------! WARNING ! ----------------------<br>
This message originates from outside our organisation,<br>
either from an external partner or from the internet.<br>
Keep this in mind if you answer this message.<br>
Follow the &#39;Report Suspicious Emails&#39; link on IT matters<br>
for instructions on reporting suspicious email messages.<br>
--------------------------------------------------------<br>
<br>
Dublin panned? I thought it was one of the best venues and locations of the=
 last meetings.<br>
<br>
What about Italy or Spain? I&#39;ve never heard about an IETF in Italy. I&#=
39;m ok with meetings outside Italy since i like traveling very much, but i=
 was wondering why it has never been taken into account in the past meeting=
s. Is it expensive? I think Italy and Spain
 are much cheaper than France, UK or Sweden, aren&#39;t they?<br>
<br>
BR<br>
Daniele<br>
<br>
&gt;-----Original Message-----<br>
&gt;From: <a href=3D"mailto:ietf-bounces@ietf.org" target=3D"_blank">ietf-b=
ounces@ietf.org</a> [mailto:<a href=3D"mailto:ietf-bounces@ietf.org" target=
=3D"_blank">ietf-bounces@ietf.org</a>] On<br>
&gt;Behalf Of Andrew Sullivan<br>
&gt;Sent: luned=EC 6 agosto 2012 14.06<br>
&gt;To: <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a=
><br>
&gt;Subject: So, where to repeat? (was:Re: management granularity)<br>
&gt;<br>
&gt;On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:<br>
&gt;&gt; enough merely to have excellent staff. =A0We need to go back to th=
e<br>
&gt;&gt; better places and benefit from the learning curve. =A0This<br>
&gt;doesn&#39;t mean<br>
&gt;&gt; &quot;no new venues&quot; but it means fewer.<br>
&gt;<br>
&gt;As a practical matter, may I ask about which venues you want<br>
&gt;to return to? =A0I get your argument in principle, but it seems<br>
&gt;to me that there has been quite a lot of complaining in the<br>
&gt;past. =A0The one factor that seems to me most likely to reduce<br>
&gt;complaints -- weather -- is evidently beyond the Secretariat&#39;s<br>
&gt;or IAOC&#39;s control.<br>
&gt;<br>
&gt;People seem inclined to return to the Hyatt in Vancouver,<br>
&gt;elevators notwithstanding. =A0We&#39;re going to do that. =A0(I don&#39=
;t<br>
&gt;understand why the previous Vencouver venue was less desirable<br>
&gt;-- to me, these venues were very similar, and not very far<br>
&gt;apart. =A0I note, however, that the previous two Vancouver<br>
&gt;visits were near the end of the year, when it rains all the<br>
&gt;time in Vancouver.)<br>
&gt;<br>
&gt;People complained at length about the venue in Paris, so I<br>
&gt;presume it&#39;s out.<br>
&gt;<br>
&gt;Some people complained about the hotel room prices and travel<br>
&gt;expense in Taipei, though I heard remarks that it was a good venue.<br>
&gt;Should we try to return there?<br>
&gt;<br>
&gt;People complained in advance about getting to Qu=E9bec, although<br>
&gt;afterwards I heard lots of good noises about that venue. =A0I<br>
&gt;note that the weather was great. =A0Should we try to return?<br>
&gt;<br>
&gt;I don&#39;t recall much complaining about the Prague venue in<br>
&gt;2011, which was striking to me because very little seemed<br>
&gt;different to me compared to our first visit there. =A0Perhaps<br>
&gt;this is evidence of the &quot;tuning&quot;<br>
&gt;you suggest (ensuring the water bottles were plastic, for instance).<br=
>
&gt;But I note the weather was excellent.<br>
&gt;<br>
&gt;Beijing? =A0I guess Maastricht is out. Anaheim (FWIW, I thought<br>
&gt;that was an example of a terrible location, but many people<br>
&gt;seemed happy with it)? =A0Hiroshima? =A0Stockholm? =A0San Francisco<br>
&gt;(we thought the crime at Paris was bad, yet didn&#39;t complain<br>
&gt;about being smack up against the Tenderloin)? =A0Or there&#39;s the<br>
&gt;old standby, Minneapolis; perhaps we could do it in March.<br>
&gt;The Dublin venue was panned by large numbers of people.<br>
&gt;Philadelphia, people complained about expense. =A0Chicago, too<br>
&gt;(combined with hotel renovations).<br>
&gt;<br>
&gt;That gets us back through 2007. =A0Which of the venues do you<br>
&gt;think we should return to, to which we already haven&#39;t<br>
&gt;returned or planned to return? =A0And why?<br>
&gt;<br>
&gt;For what it&#39;s worth, I would not complain about returning to<br>
&gt;any of those venues; I personally had good meetings at all of<br>
&gt;them except Hiroshima, which I missed due to other<br>
&gt;commitments. =A0That includes both Maastricht and Dublin, which<br>
&gt;were both apparently trials for large numbers of others.<br>
&gt;<br>
&gt;Best,<br>
&gt;<br>
&gt;A<br>
&gt;<br>
&gt;--<br>
&gt;Andrew Sullivan<br>
&gt;<a href=3D"mailto:ajs@anvilwalrusden.com" target=3D"_blank">ajs@anvilwa=
lrusden.com</a><br>
&gt;<br>
&gt;<br>
<br>
********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************<br>
<br>
<u></u><u></u></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div>
</div></div></div>
</div>

</blockquote></div><br></div>

--e0cb4efe30605a017e04c69a106f--

From nurit.sprecher@nsn.com  Mon Aug  6 07:58:57 2012
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 B940C21F84DE for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 07:58:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.431
X-Spam-Level: 
X-Spam-Status: No, score=-6.431 tagged_above=-999 required=5 tests=[AWL=0.167,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IJYMnHcg1Jqq for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 07:58:49 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id A2E1721F865F for <ietf@ietf.org>; Mon,  6 Aug 2012 07:58:48 -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 q76EwdE4027416 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 6 Aug 2012 16:58:39 +0200
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q76Ewdrb004735; Mon, 6 Aug 2012 16:58:39 +0200
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 6 Aug 2012 16:58:39 +0200
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_01CD73E3.F66ADD7A"
Subject: RE: So, where to repeat? (was:Re: management granularity)
Date: Mon, 6 Aug 2012 16:58:38 +0200
Message-ID: <E4873516F3FC7547BCFE792C7D94039C02314CA0@DEMUEXC013.nsn-intra.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBAA3F@GLKXM0002V.GREENLNK.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: So, where to repeat? (was:Re: management granularity)
Thread-Index: AQHNc+GWEX7RpVScC0qWyg0VTbeN8pdM3DzwgAACpfA=
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com><501EC24B.4080709@bbiw.net>	<20120806120547.GA20379@crankycanuck.ca><B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se><B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net><E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net><B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBAA3F@GLKXM0002V.GREENLNK.net>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>, "Mary Barnes" <mary.ietf.barnes@gmail.com>
X-OriginalArrivalTime: 06 Aug 2012 14:58:39.0741 (UTC) FILETIME=[F6B48AD0:01CD73E3]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 59185
X-purgate-ID: 151667::1344265120-000055D8-322A9045/0-0/0-0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Aug 2012 14:58:57 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CD73E3.F66ADD7A
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

To some people it may be "third if <they> stay a whole week"....but for =
others not!
Going to Vancouver is definitely one the most expensive flights....and =
takes a lot of time to get there....
Now that I have seen one saying it took him 27 hours to get back....I =
feel lucky....it took me "only" 24 hours....I left Wednesday late =
evening and got home Friday morning....
And no, even if I stayed two more nights....the cost of the flight was =
still much higher than the price of the hotel...
-          Nurit
From: ext Dearlove, Christopher (UK) =
[mailto:Chris.Dearlove@baesystems.com]=20
Sent: Monday, August 06, 2012 5:53 PM
To: Mary Barnes
Cc: Sprecher, Nurit (NSN - IL/Hod HaSharon); Daniele Ceccarelli; Andrew =
Sullivan; ietf@ietf.org
Subject: RE: So, where to repeat? (was:Re: management granularity)
=20
Those prices still sound like a week's hotel costs would exceed them. =
And I would expect the cost of your time to your employer to exceed even =
that. I'm not suggesting airfare prices don't matter, not by any stretch =
of the imagination, just that they are third if you stay a whole week. =
Or maybe fourth, there's also the IETF charge to consider, but that's =
less flexible (week or day) and not highly location dependent. Of course =
if you go for just a day the airfare is quite likely to be number one on =
the list, unless the location is relatively local.
=20
--=20
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194 |  Fax: +44 1245 242124
chris.dearlove@baesystems.com <mailto:chris.dearlove@baesystems.com>  | =
http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace =
Centre, Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687
=20
From: Mary Barnes [mailto:mary.ietf.barnes@gmail.com]=20
Sent: 06 August 2012 15:42
To: Dearlove, Christopher (UK)
Cc: Sprecher, Nurit (NSN - IL/Hod HaSharon); Daniele Ceccarelli; Andrew =
Sullivan; ietf@ietf.org
Subject: Re: So, where to repeat? (was:Re: management granularity)
=20
=20
*** WARNING ***
This message originates from outside our organisation, either from an =
external partner or the internet.
Keep this in mind if you answer this message.
Please see this process =
<http://intranet.ent.baesystems.com/howwework/security/spotlights/Documen=
ts/Dealing%20With%20Suspicious%20Emails.pdf>  on how to deal with =
suspicious emails.
Flights to Vancouver from some cities were extremely expensive.  It =
would have cost me more than twice as much as it did to fly to Beijing, =
for example, if I had taken a direct flight from DFW - it would have =
been by far my most expensive IETF airfare ever. I didn't because I was =
trying to be cost conscious.  However, I could have flown to London in =
the same time it took me to get to/from Vancouver and for about the same =
price.  This is a typical problem when we go somewhere when tourists go =
(for some reason, flying to cities in Canada is very popular when the =
temp in Texas is 110 degrees F).     Orlando will most likely be just as =
bad since it is scheduled during a time where many schools in DFW area =
have Spring Break - flight costs right now are over $500 ($560).  I can =
usually fly anywhere in the U.S. for around $300 when I book early.  =
And, of course, I can't book early as my company won't re-imburse unless =
I use their travel company and have approval (which I won't get for at =
least another 5-6 months).   Hopefully, the IETF negotiated hotel rate =
won't reflect that it is Spring Break.  =20
=20
If we were to choose one place in the U.S. to meet, Minneapolis is the =
best choice IMHO.  It's very reasonably priced, easy for many to get to =
and the hotel has adequate space for us (even back when we had many more =
attendees).  Personally, the weather is not critical to me, since I =
spend the vast majority of my time in the hotel meeting rooms, so I'm =
very happy if we meet there in March and November.  =20
=20
Mary
=20
On Mon, Aug 6, 2012 at 9:18 AM, Dearlove, Christopher (UK) =
<Chris.Dearlove@baesystems.com> wrote:
I've never been to an IETF meeting where the plane fare has exceeded the =
hotel cost for a week. Caveats to that are that I have mostly gone for =
IETF recommended hotels, so may have missed particularly cheap hotels, =
and that I have only been to North American and Europe (but that =
statistic includes Vancouver and the even further away western US cities =
down to San Diego). And of course I fly economy, and it's much cheaper =
including a Saturday night in your trip, even at the cost of an extra =
night in a hotel (at least it is from here). An almost exception was =
Paris this year where I was staying fairly cheaply, but that was a =
cost-shared trip between me and my employer, and I didn't fly (I went by =
train - though that's not cheaper, just better). Paris has cheap(er) =
hotels and a metro I understand, so I felt less location constrained.

--
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194 <tel:%2B44%201245%20242194>  |  Fax: +44 1245 =
242124 <tel:%2B44%201245%20242124>=20
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace =
Centre, Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: Sprecher, Nurit (NSN - IL/Hod HaSharon) =
[mailto:nurit.sprecher@nsn.com]
Sent: 06 August 2012 15:07
To: Dearlove, Christopher (UK); Daniele Ceccarelli; Andrew Sullivan; =
ietf@ietf.org
Subject: RE: So, where to repeat? (was:Re: management granularity)
----------------------! WARNING ! ----------------------
This message originates from outside our organisation,
either from an external partner or from the internet.
Keep this in mind if you answer this message.
Follow the 'Report Suspicious Emails' link on IT matters
for instructions on reporting suspicious email messages.
--------------------------------------------------------

When you are not close (time), flight cost may become higher in the =
priority (over hotem)....
Flying to Vancouver for me for example is the most expensive =
trip....even though the city is amazing and the host was wonderful!

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of =
ext Dearlove, Christopher (UK)
Sent: Monday, August 06, 2012 4:56 PM
To: Daniele Ceccarelli; Andrew Sullivan; ietf@ietf.org
Subject: RE: So, where to repeat? (was:Re: management granularity)

Dublin's problem was that the venue was isolated from the city. This has =
also been the case with e.g. San Diego. (I'm assuming no personal car.) =
Contrast with Minneapolis (and several other places) where you were =
right in the city. Being in a city is better for lunch and dinner =
options, taking a break to go to a bookshop (or to buy something you =
forgot to bring) and so on. (I'm deliberately not including tourism =
here.)

However at the moment my priorities to make being able to attend =
possible would be time (so the closer to me the better - I realise =
that's impossible globally), cost (hotel first, flight second, rest is =
noise) and the ability to plan ahead to only attend part of the week. =
This is the current economic reality. Dublin actually scores quite well =
on those for me.

--
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194 <tel:%2B44%201245%20242194>  |  Fax: +44 1245 =
242124 <tel:%2B44%201245%20242124>=20
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace =
Centre, Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of =
Daniele Ceccarelli
Sent: 06 August 2012 13:24
To: Andrew Sullivan; ietf@ietf.org
Subject: RE: So, where to repeat? (was:Re: management granularity)

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

Dublin panned? I thought it was one of the best venues and locations of =
the last meetings.

What about Italy or Spain? I've never heard about an IETF in Italy. I'm =
ok with meetings outside Italy since i like traveling very much, but i =
was wondering why it has never been taken into account in the past =
meetings. Is it expensive? I think Italy and Spain are much cheaper than =
France, UK or Sweden, aren't they?

BR
Daniele

>-----Original Message-----
>From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On
>Behalf Of Andrew Sullivan
>Sent: luned=EC 6 agosto 2012 14.06
>To: ietf@ietf.org
>Subject: So, where to repeat? (was:Re: management granularity)
>
>On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:
>> enough merely to have excellent staff.  We need to go back to the
>> better places and benefit from the learning curve.  This
>doesn't mean
>> "no new venues" but it means fewer.
>
>As a practical matter, may I ask about which venues you want
>to return to?  I get your argument in principle, but it seems
>to me that there has been quite a lot of complaining in the
>past.  The one factor that seems to me most likely to reduce
>complaints -- weather -- is evidently beyond the Secretariat's
>or IAOC's control.
>
>People seem inclined to return to the Hyatt in Vancouver,
>elevators notwithstanding.  We're going to do that.  (I don't
>understand why the previous Vencouver venue was less desirable
>-- to me, these venues were very similar, and not very far
>apart.  I note, however, that the previous two Vancouver
>visits were near the end of the year, when it rains all the
>time in Vancouver.)
>
>People complained at length about the venue in Paris, so I
>presume it's out.
>
>Some people complained about the hotel room prices and travel
>expense in Taipei, though I heard remarks that it was a good venue.
>Should we try to return there?
>
>People complained in advance about getting to Qu=E9bec, although
>afterwards I heard lots of good noises about that venue.  I
>note that the weather was great.  Should we try to return?
>
>I don't recall much complaining about the Prague venue in
>2011, which was striking to me because very little seemed
>different to me compared to our first visit there.  Perhaps
>this is evidence of the "tuning"
>you suggest (ensuring the water bottles were plastic, for instance).
>But I note the weather was excellent.
>
>Beijing?  I guess Maastricht is out. Anaheim (FWIW, I thought
>that was an example of a terrible location, but many people
>seemed happy with it)?  Hiroshima?  Stockholm?  San Francisco
>(we thought the crime at Paris was bad, yet didn't complain
>about being smack up against the Tenderloin)?  Or there's the
>old standby, Minneapolis; perhaps we could do it in March.
>The Dublin venue was panned by large numbers of people.
>Philadelphia, people complained about expense.  Chicago, too
>(combined with hotel renovations).
>
>That gets us back through 2007.  Which of the venues do you
>think we should return to, to which we already haven't
>returned or planned to return?  And why?
>
>For what it's worth, I would not complain about returning to
>any of those venues; I personally had good meetings at all of
>them except Hiroshima, which I missed due to other
>commitments.  That includes both Maastricht and Dublin, which
>were both apparently trials for large numbers of others.
>
>Best,
>
>A
>
>--
>Andrew Sullivan
>ajs@anvilwalrusden.com
>
>

********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************
=20

------_=_NextPart_001_01CD73E3.F66ADD7A
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-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=3Diso-8859-1"><meta name=3DProgId content=3DWord.Document><meta =
name=3DGenerator content=3D"Microsoft Word 12"><meta name=3DOriginator =
content=3D"Microsoft Word 12"><link rel=3DFile-List =
href=3D"cid:filelist.xml@01CD73FD.1AF7CCE0"><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
<o:TargetScreenSize>1024x768</o:TargetScreenSize>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:Zoom>120</w:Zoom>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:EnvelopeVis/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-US</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>HE</w:LidThemeComplexScript>
<w:Compatibility>
<w:DoNotExpandShiftReturn/>
<w:BreakWrappedTables/>
<w:SplitPgBreakAndParaMark/>
<w:DontVertAlignCellWithSp/>
<w:DontBreakConstrainedForcedTables/>
<w:DontVertAlignInTxbx/>
<w:Word11KerningPairs/>
<w:CachedColBalance/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;
	mso-font-alt:Wingdings;
	mso-font-charset:2;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:0 268435456 0 0 -2147483648 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;
	mso-font-alt:"Calisto MT";
	mso-font-charset:0;
	mso-generic-font-family:roman;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1107305727 0 0 415 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-alt:"Times New Roman";
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520092929 1073786111 9 0 415 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-alt:Verdana;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520081665 -1073717157 41 0 66047 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	mso-fareast-font-family:Calibri;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	mso-fareast-font-family:Calibri;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	mso-style-unhide:no;
	mso-style-qformat:yes;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	mso-fareast-font-family:Calibri;}
span.EmailStyle17
	{mso-style-type:personal;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:Calibri;
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Balloon Text";
	mso-ansi-font-size:8.0pt;
	mso-bidi-font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	mso-ascii-font-family:Tahoma;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Tahoma;
	mso-bidi-font-family:Tahoma;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:Arial;
	color:#993366;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-size:10.0pt;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:853693678;
	mso-list-type:hybrid;
	mso-list-template-ids:23464676 841284434 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:16;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-qformat:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple style=3D'tab-interval:.5in'><div class=3DWordSection1><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:Arial;color:#993366'>To some people it may be =
&#8220;</span><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-GB'>third if &lt;they&gt; stay a whole =
week&#8221;&#8230;.but for others not!<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-GB'>Going to Vancouver is definitely one the most =
expensive flights&#8230;.and takes a lot of time to get =
there&#8230;.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-GB'>Now that I have seen one saying it took him =
27 hours to get back&#8230;.I feel lucky&#8230;.it took me =
&#8220;only&#8221; 24 hours&#8230;.I left Wednesday late evening and got =
home Friday morning&#8230;.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-GB'>And no, even if I stayed two more =
nights&#8230;.the cost of the flight was still much higher than the =
price of the hotel&#8230;<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";mso-fareast-=
font-family:Calibri;color:#993366'><span =
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:Arial;color:#993366'>Nurit<o:p></o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New Roman"'>From:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New Roman"'> ext Dearlove, Christopher (UK) =
[mailto:Chris.Dearlove@baesystems.com] <br><b>Sent:</b> Monday, August =
06, 2012 5:53 PM<br><b>To:</b> Mary Barnes<br><b>Cc:</b> Sprecher, Nurit =
(NSN - IL/Hod HaSharon); Daniele Ceccarelli; Andrew Sullivan; =
ietf@ietf.org<br><b>Subject:</b> RE: So, where to repeat? (was:Re: =
management granularity)<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-GB'>Those prices still sound like a week's hotel =
costs would exceed them. And I would expect the cost of your time to =
your employer to exceed even that. I'm not suggesting airfare prices =
don't matter, not by any stretch of the imagination, just that they are =
third if you stay a whole week. Or maybe fourth, there's also the IETF =
charge to consider, but that's less flexible (week or day) and not =
highly location dependent. Of course if you go for just a day the =
airfare is quite likely to be number one on the list, unless the =
location is relatively local.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-GB'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-GB'>-- <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-GB'>Christopher Dearlove<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-GB'>Senior Principal Engineer, Communications =
Group<br>Communications, Networks and Image Analysis Capability<br>BAE =
Systems Advanced Technology Centre<br>West Hanningfield Road, Great =
Baddow, Chelmsford, CM2 8HN, UK<br>Tel: +44 1245 242194&nbsp;|&nbsp; =
Fax: +44 1245 242124<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-GB'><a =
href=3D"mailto:chris.dearlove@baesystems.com"><span =
style=3D'color:#1F497D;text-decoration:none;text-underline:none'>chris.de=
arlove@baesystems.com</span></a> | <a =
href=3D"http://www.baesystems.com">http://www.baesystems.com</a><br><br>B=
AE Systems (Operations) Limited<br>Registered Office: Warwick House, PO =
Box 87, Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, =
UK<br>Registered in England &amp; Wales No: =
1996687<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-GB'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal style=3D'mso-outline-level:1'><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Mary Barnes [<a =
href=3D"mailto:mary.ietf.barnes@gmail.com">mailto:mary.ietf.barnes@gmail.=
com</a>] <br><b>Sent:</b> 06 August 2012 15:42<br><b>To:</b> Dearlove, =
Christopher (UK)<br><b>Cc:</b> Sprecher, Nurit (NSN - IL/Hod HaSharon); =
Daniele Ceccarelli; Andrew Sullivan; <a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br><b>Subject:</b> Re: =
So, where to repeat? (was:Re: management =
granularity)<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-GB =
style=3D'mso-ansi-language:EN-GB'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:solid black 1.0pt;padding:2.0pt 2.0pt 2.0pt 2.0pt'><p =
class=3DMsoNormal align=3Dcenter =
style=3D'text-align:center;background:white'><span lang=3DEN-GB =
style=3D'font-family:"Arial","sans-serif";color:black;mso-ansi-language:E=
N-GB'><o:p>&nbsp;</o:p></span></p><div><p class=3DMsoNormal =
align=3Dcenter style=3D'text-align:center;background:white'><b><span =
lang=3DEN-GB =
style=3D'font-size:15.0pt;font-family:"Arial","sans-serif";color:#333972;=
mso-ansi-language:EN-GB'>*** WARNING =
***<o:p></o:p></span></b></p></div><div><p class=3DMsoNormal =
align=3Dcenter =
style=3D'margin-bottom:12.0pt;text-align:center;background:white'><em><sp=
an lang=3DEN-GB =
style=3D'font-size:10.5pt;font-family:"Arial","sans-serif";color:#333972;=
mso-ansi-language:EN-GB'>This message originates from outside our =
organisation, either from an external partner or the =
internet.</span></em><i><span lang=3DEN-GB =
style=3D'font-size:10.5pt;font-family:"Arial","sans-serif";color:#333972;=
mso-ansi-language:EN-GB'><br><em><span =
style=3D'font-family:"Arial","sans-serif"'>Keep this in mind if you =
answer this message.</span></em><br><em><span =
style=3D'font-family:"Arial","sans-serif"'>Please see <a =
href=3D"http://intranet.ent.baesystems.com/howwework/security/spotlights/=
Documents/Dealing%20With%20Suspicious%20Emails.pdf">this process</a> on =
how to deal with suspicious emails.</span></em></span></i><span =
lang=3DEN-GB =
style=3D'font-size:10.5pt;font-family:"Arial","sans-serif";color:#333972;=
mso-ansi-language:EN-GB'><o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'mso-ansi-language:EN-GB'>Flights to Vancouver from some cities =
were extremely expensive. &nbsp;It would have cost me more than twice as =
much as it did to fly to Beijing, for example, if I had taken a direct =
flight from DFW - it would have been by far my most expensive IETF =
airfare ever. I didn't because I was trying to be cost conscious. =
&nbsp;However, I could have flown to London in the same time it took me =
to get to/from Vancouver and for about the same price. &nbsp;This is a =
typical problem when we go somewhere when tourists go (for some reason, =
flying to cities in Canada is very popular when the temp in Texas is 110 =
degrees F). &nbsp; &nbsp; Orlando will most likely be just as bad since =
it is scheduled during a time where many schools in DFW area have Spring =
Break - flight costs right now are over $500 ($560). &nbsp;I can usually =
fly anywhere in the U.S. for around $300 when I book early. &nbsp;And, =
of course, I can't book early as my company won't re-imburse unless I =
use their travel company and have approval (which I won't get for at =
least another 5-6 months). &nbsp; Hopefully, the IETF negotiated hotel =
rate won't reflect that it is Spring Break. =
&nbsp;&nbsp;<o:p></o:p></span></p><div><p class=3DMsoNormal><span =
lang=3DEN-GB =
style=3D'mso-ansi-language:EN-GB'><o:p>&nbsp;</o:p></span></p></div><div>=
<p class=3DMsoNormal><span lang=3DEN-GB =
style=3D'mso-ansi-language:EN-GB'>If we were to choose one place in the =
U.S. to meet, Minneapolis is the best choice IMHO. &nbsp;It's very =
reasonably priced, easy for many to get to and the hotel has adequate =
space for us (even back when we had many more attendees). =
&nbsp;Personally, the weather is not critical to me, since I spend the =
vast majority of my time in the hotel meeting rooms, so I'm very happy =
if we meet there in March and November. =
&nbsp;&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-GB =
style=3D'mso-ansi-language:EN-GB'><o:p>&nbsp;</o:p></span></p></div><div>=
<p class=3DMsoNormal><span lang=3DEN-GB =
style=3D'mso-ansi-language:EN-GB'>Mary<o:p></o:p></span></p><div><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'mso-ansi-language:EN-GB'><o:p>&nbsp;</o:p></span></p><div><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'mso-ansi-language:EN-GB'>On Mon, Aug 6, 2012 at 9:18 AM, =
Dearlove, Christopher (UK) &lt;<a =
href=3D"mailto:Chris.Dearlove@baesystems.com" =
target=3D"_blank">Chris.Dearlove@baesystems.com</a>&gt; =
wrote:<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-GB =
style=3D'mso-ansi-language:EN-GB'>I've never been to an IETF meeting =
where the plane fare has exceeded the hotel cost for a week. Caveats to =
that are that I have mostly gone for IETF recommended hotels, so may =
have missed particularly cheap hotels, and that I have only been to =
North American and Europe (but that statistic includes Vancouver and the =
even further away western US cities down to San Diego). And of course I =
fly economy, and it's much cheaper including a Saturday night in your =
trip, even at the cost of an extra night in a hotel (at least it is from =
here). An almost exception was Paris this year where I was staying =
fairly cheaply, but that was a cost-shared trip between me and my =
employer, and I didn't fly (I went by train - though that's not cheaper, =
just better). Paris has cheap(er) hotels and a metro I understand, so I =
felt less location constrained.<o:p></o:p></span></p><div><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'mso-ansi-language:EN-GB'><br>--<br>Christopher =
Dearlove<br>Senior Principal Engineer, Communications =
Group<br>Communications, Networks and Image Analysis Capability<br>BAE =
Systems Advanced Technology Centre<br>West Hanningfield Road, Great =
Baddow, Chelmsford, CM2 8HN, UK<br>Tel: <a =
href=3D"tel:%2B44%201245%20242194">+44 1245 242194</a>&nbsp;| &nbsp;Fax: =
<a href=3D"tel:%2B44%201245%20242124">+44 1245 242124</a><br><a =
href=3D"mailto:chris.dearlove@baesystems.com">chris.dearlove@baesystems.c=
om</a> | <a href=3D"http://www.baesystems.com" =
target=3D"_blank">http://www.baesystems.com</a><br><br>BAE Systems =
(Operations) Limited<br>Registered Office: Warwick House, PO Box 87, =
Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, =
UK<br>Registered in England &amp; Wales No: =
1996687<br><br><br>-----Original =
Message-----<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt;mso-outline-level:1'><span lang=3DEN-GB =
style=3D'mso-ansi-language:EN-GB'>From: Sprecher, Nurit (NSN - IL/Hod =
HaSharon) [mailto:<a =
href=3D"mailto:nurit.sprecher@nsn.com">nurit.sprecher@nsn.com</a>]<br>Sen=
t: 06 August 2012 15:07<br>To: Dearlove, Christopher (UK); Daniele =
Ceccarelli; Andrew Sullivan; <a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>Subject: RE: So, =
where to repeat? (was:Re: management =
granularity)<o:p></o:p></span></p></div><div><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt;mso-outline-level:1'><span lang=3DEN-GB =
style=3D'mso-ansi-language:EN-GB'>----------------------! WARNING ! =
----------------------<br>This message originates from outside our =
organisation,<br>either from an external partner or from the =
internet.<br>Keep this in mind if you answer this message.<br>Follow the =
'Report Suspicious Emails' link on IT matters<br>for instructions on =
reporting suspicious email =
messages.<br>--------------------------------------------------------<br>=
<br>When you are not close (time), flight cost may become higher in the =
priority (over hotem)....<br>Flying to Vancouver for me for example is =
the most expensive trip....even though the city is amazing and the host =
was wonderful!<br><br>-----Original Message-----<br>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 ext Dearlove, Christopher (UK)<br>Sent: Monday, August 06, =
2012 4:56 PM<br>To: Daniele Ceccarelli; Andrew Sullivan; <a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>Subject: RE: So, =
where to repeat? (was:Re: management granularity)<br><br>Dublin's =
problem was that the venue was isolated from the city. This has also =
been the case with e.g. San Diego. (I'm assuming no personal car.) =
Contrast with Minneapolis (and several other places) where you were =
right in the city. Being in a city is better for lunch and dinner =
options, taking a break to go to a bookshop (or to buy something you =
forgot to bring) and so on. (I'm deliberately not including tourism =
here.)<br><br>However at the moment my priorities to make being able to =
attend possible would be time (so the closer to me the better - I =
realise that's impossible globally), cost (hotel first, flight second, =
rest is noise) and the ability to plan ahead to only attend part of the =
week. This is the current economic reality. Dublin actually scores quite =
well on those for me.<br><br>--<br>Christopher Dearlove<br>Senior =
Principal Engineer, Communications Group<br>Communications, Networks and =
Image Analysis Capability<br>BAE Systems Advanced Technology =
Centre<br>West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, =
UK<br>Tel: <a href=3D"tel:%2B44%201245%20242194">+44 1245 =
242194</a>&nbsp;| &nbsp;Fax: <a href=3D"tel:%2B44%201245%20242124">+44 =
1245 242124</a><br><a =
href=3D"mailto:chris.dearlove@baesystems.com">chris.dearlove@baesystems.c=
om</a> | <a href=3D"http://www.baesystems.com" =
target=3D"_blank">http://www.baesystems.com</a><br><br>BAE Systems =
(Operations) Limited<br>Registered Office: Warwick House, PO Box 87, =
Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, =
UK<br>Registered in England &amp; Wales No: =
1996687<br><br><br>-----Original Message-----<br>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 Daniele Ceccarelli<br>Sent: 06 August 2012 13:24<br>To: Andrew =
Sullivan; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>Subject: =
RE: So, where to repeat? (was:Re: management =
granularity)<br><br>----------------------! WARNING ! =
----------------------<br>This message originates from outside our =
organisation,<br>either from an external partner or from the =
internet.<br>Keep this in mind if you answer this message.<br>Follow the =
'Report Suspicious Emails' link on IT matters<br>for instructions on =
reporting suspicious email =
messages.<br>--------------------------------------------------------<br>=
<br>Dublin panned? I thought it was one of the best venues and locations =
of the last meetings.<br><br>What about Italy or Spain? I've never heard =
about an IETF in Italy. I'm ok with meetings outside Italy since i like =
traveling very much, but i was wondering why it has never been taken =
into account in the past meetings. Is it expensive? I think Italy and =
Spain are much cheaper than France, UK or Sweden, aren't =
they?<br><br>BR<br>Daniele<br><br>&gt;-----Original =
Message-----<br>&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<br>&gt;Behalf Of Andrew Sullivan<br>&gt;Sent: luned=EC 6 agosto 2012 =
14.06<br>&gt;To: <a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>&gt;Subject: So, =
where to repeat? (was:Re: management granularity)<br>&gt;<br>&gt;On Sun, =
Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:<br>&gt;&gt; enough =
merely to have excellent staff. &nbsp;We need to go back to =
the<br>&gt;&gt; better places and benefit from the learning curve. =
&nbsp;This<br>&gt;doesn't mean<br>&gt;&gt; &quot;no new venues&quot; but =
it means fewer.<br>&gt;<br>&gt;As a practical matter, may I ask about =
which venues you want<br>&gt;to return to? &nbsp;I get your argument in =
principle, but it seems<br>&gt;to me that there has been quite a lot of =
complaining in the<br>&gt;past. &nbsp;The one factor that seems to me =
most likely to reduce<br>&gt;complaints -- weather -- is evidently =
beyond the Secretariat's<br>&gt;or IAOC's control.<br>&gt;<br>&gt;People =
seem inclined to return to the Hyatt in Vancouver,<br>&gt;elevators =
notwithstanding. &nbsp;We're going to do that. &nbsp;(I =
don't<br>&gt;understand why the previous Vencouver venue was less =
desirable<br>&gt;-- to me, these venues were very similar, and not very =
far<br>&gt;apart. &nbsp;I note, however, that the previous two =
Vancouver<br>&gt;visits were near the end of the year, when it rains all =
the<br>&gt;time in Vancouver.)<br>&gt;<br>&gt;People complained at =
length about the venue in Paris, so I<br>&gt;presume it's =
out.<br>&gt;<br>&gt;Some people complained about the hotel room prices =
and travel<br>&gt;expense in Taipei, though I heard remarks that it was =
a good venue.<br>&gt;Should we try to return =
there?<br>&gt;<br>&gt;People complained in advance about getting to =
Qu=E9bec, although<br>&gt;afterwards I heard lots of good noises about =
that venue. &nbsp;I<br>&gt;note that the weather was great. &nbsp;Should =
we try to return?<br>&gt;<br>&gt;I don't recall much complaining about =
the Prague venue in<br>&gt;2011, which was striking to me because very =
little seemed<br>&gt;different to me compared to our first visit there. =
&nbsp;Perhaps<br>&gt;this is evidence of the =
&quot;tuning&quot;<br>&gt;you suggest (ensuring the water bottles were =
plastic, for instance).<br>&gt;But I note the weather was =
excellent.<br>&gt;<br>&gt;Beijing? &nbsp;I guess Maastricht is out. =
Anaheim (FWIW, I thought<br>&gt;that was an example of a terrible =
location, but many people<br>&gt;seemed happy with it)? &nbsp;Hiroshima? =
&nbsp;Stockholm? &nbsp;San Francisco<br>&gt;(we thought the crime at =
Paris was bad, yet didn't complain<br>&gt;about being smack up against =
the Tenderloin)? &nbsp;Or there's the<br>&gt;old standby, Minneapolis; =
perhaps we could do it in March.<br>&gt;The Dublin venue was panned by =
large numbers of people.<br>&gt;Philadelphia, people complained about =
expense. &nbsp;Chicago, too<br>&gt;(combined with hotel =
renovations).<br>&gt;<br>&gt;That gets us back through 2007. &nbsp;Which =
of the venues do you<br>&gt;think we should return to, to which we =
already haven't<br>&gt;returned or planned to return? &nbsp;And =
why?<br>&gt;<br>&gt;For what it's worth, I would not complain about =
returning to<br>&gt;any of those venues; I personally had good meetings =
at all of<br>&gt;them except Hiroshima, which I missed due to =
other<br>&gt;commitments. &nbsp;That includes both Maastricht and =
Dublin, which<br>&gt;were both apparently trials for large numbers of =
others.<br>&gt;<br>&gt;Best,<br>&gt;<br>&gt;A<br>&gt;<br>&gt;--<br>&gt;An=
drew Sullivan<br>&gt;<a =
href=3D"mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><br>&gt;=
<br>&gt;<br><br>*********************************************************=
***********<br>This email and any attachments are confidential to the =
intended<br>recipient and may also be privileged. If you are not the =
intended<br>recipient please delete it from your system and notify the =
sender.<br>You should not copy it or use it for any purpose nor disclose =
or<br>distribute its contents to any other =
person.<br>**************************************************************=
******<o:p></o:p></span></p></div></div></div><p class=3DMsoNormal><span =
lang=3DEN-GB =
style=3D'mso-ansi-language:EN-GB'><o:p>&nbsp;</o:p></span></p></div></div=
></div></body></html>
------_=_NextPart_001_01CD73E3.F66ADD7A--

From Chris.Dearlove@baesystems.com  Mon Aug  6 08:02:25 2012
Return-Path: <Chris.Dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE94721F85BB for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 08:02:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.328
X-Spam-Level: 
X-Spam-Status: No, score=-10.328 tagged_above=-999 required=5 tests=[AWL=0.270, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0KXizSgqeHeL for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 08:02:16 -0700 (PDT)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) by ietfa.amsl.com (Postfix) with ESMTP id 9104921F859A for <ietf@ietf.org>; Mon,  6 Aug 2012 08:02:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.77,720,1336345200";  d="scan'208,217";a="261606579"
Received: from unknown (HELO baemasmds009.greenlnk.net) ([141.245.68.246]) by baemasmds003ir.sharelnk.net with ESMTP; 06 Aug 2012 16:02:14 +0100
Received: from GLKXH0004V.GREENLNK.net ([10.109.2.35]) by baemasmds009.greenlnk.net (Switch-3.4.4/Switch-3.4.4) with ESMTP id q76F2Ec4004094 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 6 Aug 2012 16:02:14 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.170]) by GLKXH0004V.GREENLNK.net ([10.109.2.35]) with mapi id 14.02.0309.002; Mon, 6 Aug 2012 16:02:13 +0100
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>, "Mary Barnes" <mary.ietf.barnes@gmail.com>
Subject: RE: So, where to repeat? (was:Re: management granularity)
Thread-Topic: So, where to repeat? (was:Re: management granularity)
Thread-Index: AQHNc+GWEX7RpVScC0qWyg0VTbeN8pdM3DzwgAACpfCAAAGH0A==
Date: Mon, 6 Aug 2012 15:02:13 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBAA75@GLKXM0002V.GREENLNK.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com><501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca><B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se><B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net><E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net><B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBAA3F@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314CA0@DEMUEXC013.nsn-intra.net>
In-Reply-To: <E4873516F3FC7547BCFE792C7D94039C02314CA0@DEMUEXC013.nsn-intra.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: multipart/alternative; boundary="_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBAA75GLKXM0002VGREEN_"
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Aug 2012 15:02:25 -0000

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBAA75GLKXM0002VGREEN_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

My experience is no doubt biased by that one can get directly to most place=
s, including Vancouver the last time I went (not this year), from London, a=
nd I can get to Heathrow in well under two hours.

--
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194 |  Fax: +44 1245 242124
chris.dearlove@baesystems.com<mailto:chris.dearlove@baesystems.com> | http:=
//www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687

From: Sprecher, Nurit (NSN - IL/Hod HaSharon) [mailto:nurit.sprecher@nsn.co=
m]
Sent: 06 August 2012 15:59
To: Dearlove, Christopher (UK); Mary Barnes
Cc: Daniele Ceccarelli; Andrew Sullivan; ietf@ietf.org
Subject: RE: So, where to repeat? (was:Re: management granularity)


*** WARNING ***
This message originates from outside our organisation, either from an exter=
nal partner or the internet.
Keep this in mind if you answer this message.
Please see this process<http://intranet.ent.baesystems.com/howwework/securi=
ty/spotlights/Documents/Dealing%20With%20Suspicious%20Emails.pdf> on how to=
 deal with suspicious emails.
To some people it may be "third if <they> stay a whole week"....but for oth=
ers not!
Going to Vancouver is definitely one the most expensive flights....and take=
s a lot of time to get there....
Now that I have seen one saying it took him 27 hours to get back....I feel =
lucky....it took me "only" 24 hours....I left Wednesday late evening and go=
t home Friday morning....
And no, even if I stayed two more nights....the cost of the flight was stil=
l much higher than the price of the hotel...

-          Nurit
From: ext Dearlove, Christopher (UK) [mailto:Chris.Dearlove@baesystems.com]
Sent: Monday, August 06, 2012 5:53 PM
To: Mary Barnes
Cc: Sprecher, Nurit (NSN - IL/Hod HaSharon); Daniele Ceccarelli; Andrew Sul=
livan; ietf@ietf.org
Subject: RE: So, where to repeat? (was:Re: management granularity)

Those prices still sound like a week's hotel costs would exceed them. And I=
 would expect the cost of your time to your employer to exceed even that. I=
'm not suggesting airfare prices don't matter, not by any stretch of the im=
agination, just that they are third if you stay a whole week. Or maybe four=
th, there's also the IETF charge to consider, but that's less flexible (wee=
k or day) and not highly location dependent. Of course if you go for just a=
 day the airfare is quite likely to be number one on the list, unless the l=
ocation is relatively local.

--
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194 |  Fax: +44 1245 242124
chris.dearlove@baesystems.com<mailto:chris.dearlove@baesystems.com> | http:=
//www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687

From: Mary Barnes [mailto:mary.ietf.barnes@gmail.com]
Sent: 06 August 2012 15:42
To: Dearlove, Christopher (UK)
Cc: Sprecher, Nurit (NSN - IL/Hod HaSharon); Daniele Ceccarelli; Andrew Sul=
livan; ietf@ietf.org<mailto:ietf@ietf.org>
Subject: Re: So, where to repeat? (was:Re: management granularity)


*** WARNING ***
This message originates from outside our organisation, either from an exter=
nal partner or the internet.
Keep this in mind if you answer this message.
Please see this process<http://intranet.ent.baesystems.com/howwework/securi=
ty/spotlights/Documents/Dealing%20With%20Suspicious%20Emails.pdf> on how to=
 deal with suspicious emails.
Flights to Vancouver from some cities were extremely expensive.  It would h=
ave cost me more than twice as much as it did to fly to Beijing, for exampl=
e, if I had taken a direct flight from DFW - it would have been by far my m=
ost expensive IETF airfare ever. I didn't because I was trying to be cost c=
onscious.  However, I could have flown to London in the same time it took m=
e to get to/from Vancouver and for about the same price.  This is a typical=
 problem when we go somewhere when tourists go (for some reason, flying to =
cities in Canada is very popular when the temp in Texas is 110 degrees F). =
    Orlando will most likely be just as bad since it is scheduled during a =
time where many schools in DFW area have Spring Break - flight costs right =
now are over $500 ($560).  I can usually fly anywhere in the U.S. for aroun=
d $300 when I book early.  And, of course, I can't book early as my company=
 won't re-imburse unless I use their travel company and have approval (whic=
h I won't get for at least another 5-6 months).   Hopefully, the IETF negot=
iated hotel rate won't reflect that it is Spring Break.

If we were to choose one place in the U.S. to meet, Minneapolis is the best=
 choice IMHO.  It's very reasonably priced, easy for many to get to and the=
 hotel has adequate space for us (even back when we had many more attendees=
).  Personally, the weather is not critical to me, since I spend the vast m=
ajority of my time in the hotel meeting rooms, so I'm very happy if we meet=
 there in March and November.

Mary

On Mon, Aug 6, 2012 at 9:18 AM, Dearlove, Christopher (UK) <Chris.Dearlove@=
baesystems.com<mailto:Chris.Dearlove@baesystems.com>> wrote:
I've never been to an IETF meeting where the plane fare has exceeded the ho=
tel cost for a week. Caveats to that are that I have mostly gone for IETF r=
ecommended hotels, so may have missed particularly cheap hotels, and that I=
 have only been to North American and Europe (but that statistic includes V=
ancouver and the even further away western US cities down to San Diego). An=
d of course I fly economy, and it's much cheaper including a Saturday night=
 in your trip, even at the cost of an extra night in a hotel (at least it i=
s from here). An almost exception was Paris this year where I was staying f=
airly cheaply, but that was a cost-shared trip between me and my employer, =
and I didn't fly (I went by train - though that's not cheaper, just better)=
. Paris has cheap(er) hotels and a metro I understand, so I felt less locat=
ion constrained.

--
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194<tel:%2B44%201245%20242194> |  Fax: +44 1245 242124<tel=
:%2B44%201245%20242124>
chris.dearlove@baesystems.com<mailto:chris.dearlove@baesystems.com> | http:=
//www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: Sprecher, Nurit (NSN - IL/Hod HaSharon) [mailto:nurit.sprecher@nsn.co=
m<mailto:nurit.sprecher@nsn.com>]
Sent: 06 August 2012 15:07
To: Dearlove, Christopher (UK); Daniele Ceccarelli; Andrew Sullivan; ietf@i=
etf.org<mailto:ietf@ietf.org>
Subject: RE: So, where to repeat? (was:Re: management granularity)
----------------------! WARNING ! ----------------------
This message originates from outside our organisation,
either from an external partner or from the internet.
Keep this in mind if you answer this message.
Follow the 'Report Suspicious Emails' link on IT matters
for instructions on reporting suspicious email messages.
--------------------------------------------------------

When you are not close (time), flight cost may become higher in the priorit=
y (over hotem)....
Flying to Vancouver for me for example is the most expensive trip....even t=
hough the city is amazing and the host was wonderful!

-----Original Message-----
From: ietf-bounces@ietf.org<mailto:ietf-bounces@ietf.org> [mailto:ietf-boun=
ces@ietf.org<mailto:ietf-bounces@ietf.org>] On Behalf Of ext Dearlove, Chri=
stopher (UK)
Sent: Monday, August 06, 2012 4:56 PM
To: Daniele Ceccarelli; Andrew Sullivan; ietf@ietf.org<mailto:ietf@ietf.org=
>
Subject: RE: So, where to repeat? (was:Re: management granularity)

Dublin's problem was that the venue was isolated from the city. This has al=
so been the case with e.g. San Diego. (I'm assuming no personal car.) Contr=
ast with Minneapolis (and several other places) where you were right in the=
 city. Being in a city is better for lunch and dinner options, taking a bre=
ak to go to a bookshop (or to buy something you forgot to bring) and so on.=
 (I'm deliberately not including tourism here.)

However at the moment my priorities to make being able to attend possible w=
ould be time (so the closer to me the better - I realise that's impossible =
globally), cost (hotel first, flight second, rest is noise) and the ability=
 to plan ahead to only attend part of the week. This is the current economi=
c reality. Dublin actually scores quite well on those for me.

--
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194<tel:%2B44%201245%20242194> |  Fax: +44 1245 242124<tel=
:%2B44%201245%20242124>
chris.dearlove@baesystems.com<mailto:chris.dearlove@baesystems.com> | http:=
//www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: ietf-bounces@ietf.org<mailto:ietf-bounces@ietf.org> [mailto:ietf-boun=
ces@ietf.org<mailto:ietf-bounces@ietf.org>] On Behalf Of Daniele Ceccarelli
Sent: 06 August 2012 13:24
To: Andrew Sullivan; ietf@ietf.org<mailto:ietf@ietf.org>
Subject: RE: So, where to repeat? (was:Re: management granularity)

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

Dublin panned? I thought it was one of the best venues and locations of the=
 last meetings.

What about Italy or Spain? I've never heard about an IETF in Italy. I'm ok =
with meetings outside Italy since i like traveling very much, but i was won=
dering why it has never been taken into account in the past meetings. Is it=
 expensive? I think Italy and Spain are much cheaper than France, UK or Swe=
den, aren't they?

BR
Daniele

>-----Original Message-----
>From: ietf-bounces@ietf.org<mailto:ietf-bounces@ietf.org> [mailto:ietf-bou=
nces@ietf.org<mailto:ietf-bounces@ietf.org>] On
>Behalf Of Andrew Sullivan
>Sent: luned=EC 6 agosto 2012 14.06
>To: ietf@ietf.org<mailto:ietf@ietf.org>
>Subject: So, where to repeat? (was:Re: management granularity)
>
>On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:
>> enough merely to have excellent staff.  We need to go back to the
>> better places and benefit from the learning curve.  This
>doesn't mean
>> "no new venues" but it means fewer.
>
>As a practical matter, may I ask about which venues you want
>to return to?  I get your argument in principle, but it seems
>to me that there has been quite a lot of complaining in the
>past.  The one factor that seems to me most likely to reduce
>complaints -- weather -- is evidently beyond the Secretariat's
>or IAOC's control.
>
>People seem inclined to return to the Hyatt in Vancouver,
>elevators notwithstanding.  We're going to do that.  (I don't
>understand why the previous Vencouver venue was less desirable
>-- to me, these venues were very similar, and not very far
>apart.  I note, however, that the previous two Vancouver
>visits were near the end of the year, when it rains all the
>time in Vancouver.)
>
>People complained at length about the venue in Paris, so I
>presume it's out.
>
>Some people complained about the hotel room prices and travel
>expense in Taipei, though I heard remarks that it was a good venue.
>Should we try to return there?
>
>People complained in advance about getting to Qu=E9bec, although
>afterwards I heard lots of good noises about that venue.  I
>note that the weather was great.  Should we try to return?
>
>I don't recall much complaining about the Prague venue in
>2011, which was striking to me because very little seemed
>different to me compared to our first visit there.  Perhaps
>this is evidence of the "tuning"
>you suggest (ensuring the water bottles were plastic, for instance).
>But I note the weather was excellent.
>
>Beijing?  I guess Maastricht is out. Anaheim (FWIW, I thought
>that was an example of a terrible location, but many people
>seemed happy with it)?  Hiroshima?  Stockholm?  San Francisco
>(we thought the crime at Paris was bad, yet didn't complain
>about being smack up against the Tenderloin)?  Or there's the
>old standby, Minneapolis; perhaps we could do it in March.
>The Dublin venue was panned by large numbers of people.
>Philadelphia, people complained about expense.  Chicago, too
>(combined with hotel renovations).
>
>That gets us back through 2007.  Which of the venues do you
>think we should return to, to which we already haven't
>returned or planned to return?  And why?
>
>For what it's worth, I would not complain about returning to
>any of those venues; I personally had good meetings at all of
>them except Hiroshima, which I missed due to other
>commitments.  That includes both Maastricht and Dublin, which
>were both apparently trials for large numbers of others.
>
>Best,
>
>A
>
>--
>Andrew Sullivan
>ajs@anvilwalrusden.com<mailto:ajs@anvilwalrusden.com>
>
>

********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBAA75GLKXM0002VGREEN_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#993366;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:853693678;
	mso-list-type:hybrid;
	mso-list-template-ids:23464676 841284434 67698691 67698693 67698689 676986=
91 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:16;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;}
@list l0:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">My experience is no doubt=
 biased by that one can get directly to most places, including Vancouver th=
e last time I went (not this year), from London, and I can
 get to Heathrow in well under two hours.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
">--
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
">Christopher Dearlove<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
">Senior Principal Engineer, Communications Group<br>
Communications, Networks and Image Analysis Capability<br>
BAE Systems Advanced Technology Centre<br>
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<br>
Tel: &#43;44 1245 242194&nbsp;|&nbsp; Fax: &#43;44 1245 242124<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
"><a href=3D"mailto:chris.dearlove@baesystems.com"><span style=3D"color:#1F=
497D;text-decoration:none">chris.dearlove@baesystems.com</span></a>
 | http://www.baesystems.com<br>
<br>
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US">BAE Systems (O=
perations) Limited<br>
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK<br>
Registered in England &amp; Wales No: 1996687<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> Sprecher, Nurit (NSN - IL/Hod HaSharon) [mailto:nurit=
.sprecher@nsn.com]
<br>
<b>Sent:</b> 06 August 2012 15:59<br>
<b>To:</b> Dearlove, Christopher (UK); Mary Barnes<br>
<b>Cc:</b> Daniele Ceccarelli; Andrew Sullivan; ietf@ietf.org<br>
<b>Subject:</b> RE: So, where to repeat? (was:Re: management granularity)<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div style=3D"border:solid black 1.0pt;padding:2.0pt 2.0pt 2.0pt 2.0pt">
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center;backgrou=
nd:white"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quo=
t;;color:black"><o:p>&nbsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center;backgrou=
nd:white"><b><span style=3D"font-size:15.0pt;font-family:&quot;Arial&quot;,=
&quot;sans-serif&quot;;color:#333972">*** WARNING ***<o:p></o:p></span></b>=
</p>
</div>
<div>
<p class=3D"MsoNormal" align=3D"center" style=3D"margin-bottom:12.0pt;text-=
align:center;background:white">
<em><span style=3D"font-size:10.5pt;font-family:&quot;Arial&quot;,&quot;san=
s-serif&quot;;color:#333972">This message originates from outside our organ=
isation, either from an external partner or the internet.</span></em><i><sp=
an style=3D"font-size:10.5pt;font-family:&quot;Arial&quot;,&quot;sans-serif=
&quot;;color:#333972"><br>
<em><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">Ke=
ep this in mind if you answer this message.</span></em><br>
<em><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">Pl=
ease see <a href=3D"http://intranet.ent.baesystems.com/howwework/security/s=
potlights/Documents/Dealing%20With%20Suspicious%20Emails.pdf">
this process</a> on how to deal with suspicious emails.</span></em></span><=
/i><span style=3D"font-size:10.5pt;font-family:&quot;Arial&quot;,&quot;sans=
-serif&quot;;color:#333972"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#993366">To some pe=
ople it may be &#8220;</span><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">third if &lt;they&g=
t; stay a whole week&#8221;&#8230;.but
 for others not!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Going to Vancouver is def=
initely one the most expensive flights&#8230;.and takes a lot of time to ge=
t there&#8230;.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Now that I have seen one =
saying it took him 27 hours to get back&#8230;.I feel lucky&#8230;.it took =
me &#8220;only&#8221; 24 hours&#8230;.I left Wednesday late evening and got=
 home Friday
 morning&#8230;.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">And no, even if I stayed =
two more nights&#8230;.the cost of the flight was still much higher than th=
e price of the hotel&#8230;<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo2"><![if !supportLists]><span lang=3D"EN-US" style=3D"font-size:11.0p=
t;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#993366"><sp=
an style=3D"mso-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Rom=
an&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US" style=3D"font-size:11.0=
pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#993366">Nu=
rit<o:p></o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> ext Dearlove, Christopher (UK) [mailto:Chris.Dearlove=
@baesystems.com]
<br>
<b>Sent:</b> Monday, August 06, 2012 5:53 PM<br>
<b>To:</b> Mary Barnes<br>
<b>Cc:</b> Sprecher, Nurit (NSN - IL/Hod HaSharon); Daniele Ceccarelli; And=
rew Sullivan; ietf@ietf.org<br>
<b>Subject:</b> RE: So, where to repeat? (was:Re: management granularity)<o=
:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Those prices still sound =
like a week's hotel costs would exceed them. And I would expect the cost of=
 your time to your employer to exceed even that. I'm not
 suggesting airfare prices don't matter, not by any stretch of the imaginat=
ion, just that they are third if you stay a whole week. Or maybe fourth, th=
ere's also the IETF charge to consider, but that's less flexible (week or d=
ay) and not highly location dependent.
 Of course if you go for just a day the airfare is quite likely to be numbe=
r one on the list, unless the location is relatively local.<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">--
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Christopher Dearlove<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Senior Principal Engineer=
, Communications Group<br>
Communications, Networks and Image Analysis Capability<br>
BAE Systems Advanced Technology Centre<br>
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<br>
Tel: &#43;44 1245 242194&nbsp;|&nbsp; Fax: &#43;44 1245 242124<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><a href=3D"mailto:chris.d=
earlove@baesystems.com"><span style=3D"color:#1F497D;text-decoration:none">=
chris.dearlove@baesystems.com</span></a> |
<a href=3D"http://www.baesystems.com">http://www.baesystems.com</a><br>
<br>
BAE Systems (Operations) Limited<br>
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK<br>
Registered in England &amp; Wales No: 1996687<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> Mary Barnes [<a href=3D"mailto:mary.ietf.barnes@gmail=
.com">mailto:mary.ietf.barnes@gmail.com</a>]
<br>
<b>Sent:</b> 06 August 2012 15:42<br>
<b>To:</b> Dearlove, Christopher (UK)<br>
<b>Cc:</b> Sprecher, Nurit (NSN - IL/Hod HaSharon); Daniele Ceccarelli; And=
rew Sullivan;
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>
<b>Subject:</b> Re: So, where to repeat? (was:Re: management granularity)<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div style=3D"border:solid black 1.0pt;padding:2.0pt 2.0pt 2.0pt 2.0pt">
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center;backgrou=
nd:white"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quo=
t;;color:black"><o:p>&nbsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center;backgrou=
nd:white"><b><span style=3D"font-size:15.0pt;font-family:&quot;Arial&quot;,=
&quot;sans-serif&quot;;color:#333972">*** WARNING ***<o:p></o:p></span></b>=
</p>
</div>
<div>
<p class=3D"MsoNormal" align=3D"center" style=3D"margin-bottom:12.0pt;text-=
align:center;background:white">
<em><span style=3D"font-size:10.5pt;font-family:&quot;Arial&quot;,&quot;san=
s-serif&quot;;color:#333972">This message originates from outside our organ=
isation, either from an external partner or the internet.</span></em><i><sp=
an style=3D"font-size:10.5pt;font-family:&quot;Arial&quot;,&quot;sans-serif=
&quot;;color:#333972"><br>
<em><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">Ke=
ep this in mind if you answer this message.</span></em><br>
<em><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">Pl=
ease see <a href=3D"http://intranet.ent.baesystems.com/howwework/security/s=
potlights/Documents/Dealing%20With%20Suspicious%20Emails.pdf">
this process</a> on how to deal with suspicious emails.</span></em></span><=
/i><span style=3D"font-size:10.5pt;font-family:&quot;Arial&quot;,&quot;sans=
-serif&quot;;color:#333972"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal">Flights to Vancouver from some cities were extremely=
 expensive. &nbsp;It would have cost me more than twice as much as it did t=
o fly to Beijing, for example, if I had taken a direct flight from DFW - it=
 would have been by far my most expensive
 IETF airfare ever. I didn't because I was trying to be cost conscious. &nb=
sp;However, I could have flown to London in the same time it took me to get=
 to/from Vancouver and for about the same price. &nbsp;This is a typical pr=
oblem when we go somewhere when tourists go
 (for some reason, flying to cities in Canada is very popular when the temp=
 in Texas is 110 degrees F). &nbsp; &nbsp; Orlando will most likely be just=
 as bad since it is scheduled during a time where many schools in DFW area =
have Spring Break - flight costs right now
 are over $500 ($560). &nbsp;I can usually fly anywhere in the U.S. for aro=
und $300 when I book early. &nbsp;And, of course, I can't book early as my =
company won't re-imburse unless I use their travel company and have approva=
l (which I won't get for at least another
 5-6 months). &nbsp; Hopefully, the IETF negotiated hotel rate won't reflec=
t that it is Spring Break. &nbsp;&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">If we were to choose one place in the U.S. to meet, =
Minneapolis is the best choice IMHO. &nbsp;It's very reasonably priced, eas=
y for many to get to and the hotel has adequate space for us (even back whe=
n we had many more attendees). &nbsp;Personally,
 the weather is not critical to me, since I spend the vast majority of my t=
ime in the hotel meeting rooms, so I'm very happy if we meet there in March=
 and November. &nbsp;&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Mary<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Mon, Aug 6, 2012 at 9:18 AM, Dearlove, Christophe=
r (UK) &lt;<a href=3D"mailto:Chris.Dearlove@baesystems.com" target=3D"_blan=
k">Chris.Dearlove@baesystems.com</a>&gt; wrote:<o:p></o:p></p>
<p class=3D"MsoNormal">I've never been to an IETF meeting where the plane f=
are has exceeded the hotel cost for a week. Caveats to that are that I have=
 mostly gone for IETF recommended hotels, so may have missed particularly c=
heap hotels, and that I have only
 been to North American and Europe (but that statistic includes Vancouver a=
nd the even further away western US cities down to San Diego). And of cours=
e I fly economy, and it's much cheaper including a Saturday night in your t=
rip, even at the cost of an extra
 night in a hotel (at least it is from here). An almost exception was Paris=
 this year where I was staying fairly cheaply, but that was a cost-shared t=
rip between me and my employer, and I didn't fly (I went by train - though =
that's not cheaper, just better).
 Paris has cheap(er) hotels and a metro I understand, so I felt less locati=
on constrained.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><br>
--<br>
Christopher Dearlove<br>
Senior Principal Engineer, Communications Group<br>
Communications, Networks and Image Analysis Capability<br>
BAE Systems Advanced Technology Centre<br>
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<br>
Tel: <a href=3D"tel:%2B44%201245%20242194">&#43;44 1245 242194</a>&nbsp;| &=
nbsp;Fax: <a href=3D"tel:%2B44%201245%20242124">
&#43;44 1245 242124</a><br>
<a href=3D"mailto:chris.dearlove@baesystems.com">chris.dearlove@baesystems.=
com</a> |
<a href=3D"http://www.baesystems.com" target=3D"_blank">http://www.baesyste=
ms.com</a><br>
<br>
BAE Systems (Operations) Limited<br>
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK<br>
Registered in England &amp; Wales No: 1996687<br>
<br>
<br>
-----Original Message-----<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">From: Sprecher, Nurit=
 (NSN - IL/Hod HaSharon) [mailto:<a href=3D"mailto:nurit.sprecher@nsn.com">=
nurit.sprecher@nsn.com</a>]<br>
Sent: 06 August 2012 15:07<br>
To: Dearlove, Christopher (UK); Daniele Ceccarelli; Andrew Sullivan; <a hre=
f=3D"mailto:ietf@ietf.org">
ietf@ietf.org</a><br>
Subject: RE: So, where to repeat? (was:Re: management granularity)<o:p></o:=
p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">---------------------=
-! WARNING ! ----------------------<br>
This message originates from outside our organisation,<br>
either from an external partner or from the internet.<br>
Keep this in mind if you answer this message.<br>
Follow the 'Report Suspicious Emails' link on IT matters<br>
for instructions on reporting suspicious email messages.<br>
--------------------------------------------------------<br>
<br>
When you are not close (time), flight cost may become higher in the priorit=
y (over hotem)....<br>
Flying to Vancouver for me for example is the most expensive trip....even t=
hough the city is amazing and the host was wonderful!<br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a> [m=
ailto:<a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a>] O=
n Behalf Of ext Dearlove, Christopher (UK)<br>
Sent: Monday, August 06, 2012 4:56 PM<br>
To: Daniele Ceccarelli; Andrew Sullivan; <a href=3D"mailto:ietf@ietf.org">i=
etf@ietf.org</a><br>
Subject: RE: So, where to repeat? (was:Re: management granularity)<br>
<br>
Dublin's problem was that the venue was isolated from the city. This has al=
so been the case with e.g. San Diego. (I'm assuming no personal car.) Contr=
ast with Minneapolis (and several other places) where you were right in the=
 city. Being in a city is better
 for lunch and dinner options, taking a break to go to a bookshop (or to bu=
y something you forgot to bring) and so on. (I'm deliberately not including=
 tourism here.)<br>
<br>
However at the moment my priorities to make being able to attend possible w=
ould be time (so the closer to me the better - I realise that's impossible =
globally), cost (hotel first, flight second, rest is noise) and the ability=
 to plan ahead to only attend part
 of the week. This is the current economic reality. Dublin actually scores =
quite well on those for me.<br>
<br>
--<br>
Christopher Dearlove<br>
Senior Principal Engineer, Communications Group<br>
Communications, Networks and Image Analysis Capability<br>
BAE Systems Advanced Technology Centre<br>
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<br>
Tel: <a href=3D"tel:%2B44%201245%20242194">&#43;44 1245 242194</a>&nbsp;| &=
nbsp;Fax: <a href=3D"tel:%2B44%201245%20242124">
&#43;44 1245 242124</a><br>
<a href=3D"mailto:chris.dearlove@baesystems.com">chris.dearlove@baesystems.=
com</a> |
<a href=3D"http://www.baesystems.com" target=3D"_blank">http://www.baesyste=
ms.com</a><br>
<br>
BAE Systems (Operations) Limited<br>
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK<br>
Registered in England &amp; Wales No: 1996687<br>
<br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a> [m=
ailto:<a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a>] O=
n Behalf Of Daniele Ceccarelli<br>
Sent: 06 August 2012 13:24<br>
To: Andrew Sullivan; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>
Subject: RE: So, where to repeat? (was:Re: management granularity)<br>
<br>
----------------------! WARNING ! ----------------------<br>
This message originates from outside our organisation,<br>
either from an external partner or from the internet.<br>
Keep this in mind if you answer this message.<br>
Follow the 'Report Suspicious Emails' link on IT matters<br>
for instructions on reporting suspicious email messages.<br>
--------------------------------------------------------<br>
<br>
Dublin panned? I thought it was one of the best venues and locations of the=
 last meetings.<br>
<br>
What about Italy or Spain? I've never heard about an IETF in Italy. I'm ok =
with meetings outside Italy since i like traveling very much, but i was won=
dering why it has never been taken into account in the past meetings. Is it=
 expensive? I think Italy and Spain
 are much cheaper than France, UK or Sweden, aren't they?<br>
<br>
BR<br>
Daniele<br>
<br>
&gt;-----Original Message-----<br>
&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<br>
&gt;Behalf Of Andrew Sullivan<br>
&gt;Sent: luned=EC 6 agosto 2012 14.06<br>
&gt;To: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>
&gt;Subject: So, where to repeat? (was:Re: management granularity)<br>
&gt;<br>
&gt;On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:<br>
&gt;&gt; enough merely to have excellent staff. &nbsp;We need to go back to=
 the<br>
&gt;&gt; better places and benefit from the learning curve. &nbsp;This<br>
&gt;doesn't mean<br>
&gt;&gt; &quot;no new venues&quot; but it means fewer.<br>
&gt;<br>
&gt;As a practical matter, may I ask about which venues you want<br>
&gt;to return to? &nbsp;I get your argument in principle, but it seems<br>
&gt;to me that there has been quite a lot of complaining in the<br>
&gt;past. &nbsp;The one factor that seems to me most likely to reduce<br>
&gt;complaints -- weather -- is evidently beyond the Secretariat's<br>
&gt;or IAOC's control.<br>
&gt;<br>
&gt;People seem inclined to return to the Hyatt in Vancouver,<br>
&gt;elevators notwithstanding. &nbsp;We're going to do that. &nbsp;(I don't=
<br>
&gt;understand why the previous Vencouver venue was less desirable<br>
&gt;-- to me, these venues were very similar, and not very far<br>
&gt;apart. &nbsp;I note, however, that the previous two Vancouver<br>
&gt;visits were near the end of the year, when it rains all the<br>
&gt;time in Vancouver.)<br>
&gt;<br>
&gt;People complained at length about the venue in Paris, so I<br>
&gt;presume it's out.<br>
&gt;<br>
&gt;Some people complained about the hotel room prices and travel<br>
&gt;expense in Taipei, though I heard remarks that it was a good venue.<br>
&gt;Should we try to return there?<br>
&gt;<br>
&gt;People complained in advance about getting to Qu=E9bec, although<br>
&gt;afterwards I heard lots of good noises about that venue. &nbsp;I<br>
&gt;note that the weather was great. &nbsp;Should we try to return?<br>
&gt;<br>
&gt;I don't recall much complaining about the Prague venue in<br>
&gt;2011, which was striking to me because very little seemed<br>
&gt;different to me compared to our first visit there. &nbsp;Perhaps<br>
&gt;this is evidence of the &quot;tuning&quot;<br>
&gt;you suggest (ensuring the water bottles were plastic, for instance).<br=
>
&gt;But I note the weather was excellent.<br>
&gt;<br>
&gt;Beijing? &nbsp;I guess Maastricht is out. Anaheim (FWIW, I thought<br>
&gt;that was an example of a terrible location, but many people<br>
&gt;seemed happy with it)? &nbsp;Hiroshima? &nbsp;Stockholm? &nbsp;San Fran=
cisco<br>
&gt;(we thought the crime at Paris was bad, yet didn't complain<br>
&gt;about being smack up against the Tenderloin)? &nbsp;Or there's the<br>
&gt;old standby, Minneapolis; perhaps we could do it in March.<br>
&gt;The Dublin venue was panned by large numbers of people.<br>
&gt;Philadelphia, people complained about expense. &nbsp;Chicago, too<br>
&gt;(combined with hotel renovations).<br>
&gt;<br>
&gt;That gets us back through 2007. &nbsp;Which of the venues do you<br>
&gt;think we should return to, to which we already haven't<br>
&gt;returned or planned to return? &nbsp;And why?<br>
&gt;<br>
&gt;For what it's worth, I would not complain about returning to<br>
&gt;any of those venues; I personally had good meetings at all of<br>
&gt;them except Hiroshima, which I missed due to other<br>
&gt;commitments. &nbsp;That includes both Maastricht and Dublin, which<br>
&gt;were both apparently trials for large numbers of others.<br>
&gt;<br>
&gt;Best,<br>
&gt;<br>
&gt;A<br>
&gt;<br>
&gt;--<br>
&gt;Andrew Sullivan<br>
&gt;<a href=3D"mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><br=
>
&gt;<br>
&gt;<br>
<br>
********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************<o:p></=
o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBAA75GLKXM0002VGREEN_--

From barryleiba.mailing.lists@gmail.com  Mon Aug  6 09:12:36 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38CB521E8049 for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 09:12:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.302
X-Spam-Level: 
X-Spam-Status: No, score=-102.302 tagged_above=-999 required=5 tests=[AWL=-0.815, BAYES_05=-1.11, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sb6844+RDPuC for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 09:12:35 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3D7CE21F84D2 for <ietf@ietf.org>; Mon,  6 Aug 2012 09:12:34 -0700 (PDT)
Received: by lahm15 with SMTP id m15so1737656lah.31 for <ietf@ietf.org>; Mon, 06 Aug 2012 09:12:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=qsosBYYkbP+dvyeSdSvs39ZBuWNRevN3HpmtA+psdpU=; b=sYza7sFnJMvnLxOauRmx3Cp8/TmFEpN1Pc33nX/SrwC2nvSFd/WfrU3Ng0IdogW0UX 2R0BA/c9dltk+5o6fWqSjFAVRY6qzPZ3boyz4NbaxrrOiDWu+Lr/YMKdG+4g1NwRi8dq vGa5kENhV/U7V9NAWR6yT5IOZxBKL18L2kg5F/nndthVybsp7mo0AtIjFcF6jdUYCKiX c/fPdFcgkDHirg4fsEPt3zS8MHRG15nB9RHwZiqPn5I+oQvgcPWW5rkx8UvBra/UIFEB YNvpfqVQjoZEEm7Z6bQaF3LRDUvTBews8p1+LpiDPJ+PuwaHjOPYQ4bGuyD2KOFSJr03 DFjw==
MIME-Version: 1.0
Received: by 10.152.136.18 with SMTP id pw18mr11187748lab.17.1344269553708; Mon, 06 Aug 2012 09:12:33 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.17.133 with HTTP; Mon, 6 Aug 2012 09:12:33 -0700 (PDT)
Date: Mon, 6 Aug 2012 12:12:33 -0400
X-Google-Sender-Auth: xPFf7xOM70lLIZ0XISqck_p5ies
Message-ID: <CAC4RtVAFPLdOHmJ=YO1XRXTv9E+Sy8sZi-ppVLgurChcqFZvnQ@mail.gmail.com>
Subject: Flighhts: "direct" vs "non-stop"
From: Barry Leiba <barryleiba@computer.org>
To: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=f46d042f927a3b2fbd04c69b25eb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Aug 2012 16:12:36 -0000

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

I've discussed this with many people, including many who fly a lot, and I
find it's often misunderstood.  I've seen it again in the current travel
threads on this list.  So:

A "direct flight" is not the same as a "non-stop flight".  If you're
talking about a flight that goes from airport ABC to airport QRS, making no
stops along the way, it's a non-stop flight from ABC to QRS.

A "direct flight" from ABC to QRS, is a flight that has one flight
number... but that flight might make stops, and could even involve a change
of planes.  It's possible for flight ZX 1042 to be "direct from Podunk to
Shanghai", and to have it be a puddle-jumper from Podunk to Chicago, have
you change to a 757 there, go on to SFO to pick up more passengers, and
then continue to Shanghai.  As long as it's ZX 1042 all the way, that
flight with two stops is "direct".

All non-stop flights are direct flights.
Not all direct flights are non-stop.

And, yes, even travel agents and airline booking personnel sometimes use
these terms interchangably.  If you're offered a direct flight, make sure
to confirm whether it's "non-stop".

Barry

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

I&#39;ve discussed this with many people, including many who fly a lot, and=
 I find it&#39;s often misunderstood. =A0I&#39;ve seen it again in the curr=
ent travel threads on this list. =A0So:<div><br></div><div>A &quot;direct f=
light&quot; is not the same as a &quot;non-stop flight&quot;. =A0If you&#39=
;re talking about a flight that goes from airport ABC to airport QRS, makin=
g no stops along the way, it&#39;s a non-stop flight from ABC to QRS.</div>
<div><br></div><div>A &quot;direct flight&quot; from ABC to QRS, is a fligh=
t that has one flight number... but that flight might make stops, and could=
 even involve a change of planes. =A0It&#39;s possible for flight ZX 1042 t=
o be &quot;direct from Podunk to Shanghai&quot;, and to have it be a puddle=
-jumper from Podunk to Chicago, have you change to a 757 there, go on to SF=
O to pick up more passengers, and then continue to Shanghai. =A0As long as =
it&#39;s ZX 1042 all the way, that flight with two stops is &quot;direct&qu=
ot;.</div>
<div><br></div><div>All non-stop flights are direct flights.</div><div>Not =
all direct flights are non-stop.</div><div><br></div><div>And, yes, even tr=
avel agents and airline booking personnel sometimes use these terms interch=
angably. =A0If you&#39;re offered a direct flight, make sure to confirm whe=
ther it&#39;s &quot;non-stop&quot;.<span></span></div>
<div><br></div><div>Barry</div>

--f46d042f927a3b2fbd04c69b25eb--

From mary.ietf.barnes@gmail.com  Mon Aug  6 09:24:28 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C63F21F860B for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 09:24:28 -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=0.069, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Aikd3OezqKy for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 09:24:27 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 63FAE21F848B for <ietf@ietf.org>; Mon,  6 Aug 2012 09:24:27 -0700 (PDT)
Received: by lbbgg6 with SMTP id gg6so558481lbb.31 for <ietf@ietf.org>; Mon, 06 Aug 2012 09:24:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7Qeb3hPYSg8t9iU9RbW47TCF87ZmFApfcZmqrYIbMJU=; b=CdAA3b0eO/brlHxCYq5tEfVVwA7xbUN0igs+T4ym96ASimZb1uPh9rx606ciax9ELT JSP1HTuYNFHBNybgxE0QIupi0+LRpsfqUJ2oMhkxTc5+iE23HIKOGTypU/xVViROcwdf Q1ms6BmdRwIWljYLpVwoZAQVEc1saIz/ITo7BNF46rHkhADd4IOHHq4UGB8exNRA1Urj 2DwNN60v/CxnCZ26XGwWH/UrNyz0Cqzvqgmw7iiasK4Ga3oEIStBjOEwfCMT+Q2kHawK HMVxFWN0+HDdY6ScNWvWYpIwcjwtHPprinUY/lQsFJCDHrqMAQX2zunE7X39AZTPCDl8 kiGQ==
MIME-Version: 1.0
Received: by 10.112.40.33 with SMTP id u1mr4894964lbk.28.1344270266371; Mon, 06 Aug 2012 09:24:26 -0700 (PDT)
Received: by 10.112.85.196 with HTTP; Mon, 6 Aug 2012 09:24:26 -0700 (PDT)
In-Reply-To: <CAC4RtVAFPLdOHmJ=YO1XRXTv9E+Sy8sZi-ppVLgurChcqFZvnQ@mail.gmail.com>
References: <CAC4RtVAFPLdOHmJ=YO1XRXTv9E+Sy8sZi-ppVLgurChcqFZvnQ@mail.gmail.com>
Date: Mon, 6 Aug 2012 11:24:26 -0500
Message-ID: <CAHBDyN4WrF+dcGSey5TgigwQcns0QPSHx5fpp2NwD2YnRN7g1w@mail.gmail.com>
Subject: Re: Flighhts: "direct" vs "non-stop"
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary=e0cb4efe3060b5902704c69b4fef
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Aug 2012 16:24:28 -0000

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

For me a direct flight is always a non-stop flight, so yes I do use the
terms interchangeably.

On Mon, Aug 6, 2012 at 11:12 AM, Barry Leiba <barryleiba@computer.org>wrote:

> I've discussed this with many people, including many who fly a lot, and I
> find it's often misunderstood.  I've seen it again in the current travel
> threads on this list.  So:
>
> A "direct flight" is not the same as a "non-stop flight".  If you're
> talking about a flight that goes from airport ABC to airport QRS, making no
> stops along the way, it's a non-stop flight from ABC to QRS.
>
> A "direct flight" from ABC to QRS, is a flight that has one flight
> number... but that flight might make stops, and could even involve a change
> of planes.  It's possible for flight ZX 1042 to be "direct from Podunk to
> Shanghai", and to have it be a puddle-jumper from Podunk to Chicago, have
> you change to a 757 there, go on to SFO to pick up more passengers, and
> then continue to Shanghai.  As long as it's ZX 1042 all the way, that
> flight with two stops is "direct".
>
> All non-stop flights are direct flights.
> Not all direct flights are non-stop.
>
> And, yes, even travel agents and airline booking personnel sometimes use
> these terms interchangably.  If you're offered a direct flight, make sure
> to confirm whether it's "non-stop".
>
> Barry
>

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

For me a direct flight is always a non-stop flight, so yes I do use the ter=
ms interchangeably.=A0<br><br><div class=3D"gmail_quote">On Mon, Aug 6, 201=
2 at 11:12 AM, Barry Leiba <span dir=3D"ltr">&lt;<a href=3D"mailto:barrylei=
ba@computer.org" target=3D"_blank">barryleiba@computer.org</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">I&#39;ve discussed this with many people, in=
cluding many who fly a lot, and I find it&#39;s often misunderstood. =A0I&#=
39;ve seen it again in the current travel threads on this list. =A0So:<div>
<br></div><div>A &quot;direct flight&quot; is not the same as a &quot;non-s=
top flight&quot;. =A0If you&#39;re talking about a flight that goes from ai=
rport ABC to airport QRS, making no stops along the way, it&#39;s a non-sto=
p flight from ABC to QRS.</div>

<div><br></div><div>A &quot;direct flight&quot; from ABC to QRS, is a fligh=
t that has one flight number... but that flight might make stops, and could=
 even involve a change of planes. =A0It&#39;s possible for flight ZX 1042 t=
o be &quot;direct from Podunk to Shanghai&quot;, and to have it be a puddle=
-jumper from Podunk to Chicago, have you change to a 757 there, go on to SF=
O to pick up more passengers, and then continue to Shanghai. =A0As long as =
it&#39;s ZX 1042 all the way, that flight with two stops is &quot;direct&qu=
ot;.</div>

<div><br></div><div>All non-stop flights are direct flights.</div><div>Not =
all direct flights are non-stop.</div><div><br></div><div>And, yes, even tr=
avel agents and airline booking personnel sometimes use these terms interch=
angably. =A0If you&#39;re offered a direct flight, make sure to confirm whe=
ther it&#39;s &quot;non-stop&quot;.<span class=3D"HOEnZb"><font color=3D"#8=
88888"><span></span></font></span></div>
<span class=3D"HOEnZb"><font color=3D"#888888">
<div><br></div><div>Barry</div>
</font></span></blockquote></div><br>

--e0cb4efe3060b5902704c69b4fef--

From randy@psg.com  Mon Aug  6 09:37:06 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F73E21F85F4 for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 09:37:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[AWL=0.051,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xzzDfFdhRkPU for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 09:37:05 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id D33B821F85EF for <ietf@ietf.org>; Mon,  6 Aug 2012 09:37:05 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SyQIj-000JZM-0H; Mon, 06 Aug 2012 16:37:05 +0000
Date: Mon, 06 Aug 2012 09:37:04 -0700
Message-ID: <m24nog7z9r.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Flighhts: "direct" vs "non-stop"
In-Reply-To: <CAC4RtVAFPLdOHmJ=YO1XRXTv9E+Sy8sZi-ppVLgurChcqFZvnQ@mail.gmail.com>
References: <CAC4RtVAFPLdOHmJ=YO1XRXTv9E+Sy8sZi-ppVLgurChcqFZvnQ@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
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Aug 2012 16:37:06 -0000

> A "direct flight" is not the same as a "non-stop flight".  If you're
> talking about a flight that goes from airport ABC to airport QRS, making no
> stops along the way, it's a non-stop flight from ABC to QRS.
> 
> A "direct flight" from ABC to QRS, is a flight that has one flight
> number... but that flight might make stops, and could even involve a change
> of planes.

while i agree with you completely, and the misuse annoys me.  i fear it
may be like routers and switches.  we have lost the distinction.

my fave used to be ua flight 3, ord-ogg-koa-ord, direct ord-ord :)

randy

From melinda.shore@gmail.com  Mon Aug  6 10:33:11 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A0B321E804A for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 10:33:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.551
X-Spam-Level: 
X-Spam-Status: No, score=-3.551 tagged_above=-999 required=5 tests=[AWL=0.048,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v-eUZCuURrIZ for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 10:33:11 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0F48F21E8039 for <ietf@ietf.org>; Mon,  6 Aug 2012 10:33:11 -0700 (PDT)
Received: by pbbrr4 with SMTP id rr4so4135158pbb.31 for <ietf@ietf.org>; Mon, 06 Aug 2012 10:33:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=5cj/93DgaAFzH57LpiC3BoqFxXFqvmrS7vEnrnFkMW0=; b=iZeNL2W7xeQ0OrroJXJSCDwVAW1tlftedwPi1hLGtiftPMOPtAAULNikh0zyGZk4eC tkWscovLL5qLPy07k9etjhZnFUnOBHKB19mv+A3IsPg/qQ9soRaBBA0+6HjaM9FcsgdM vQfLbzAw//Kr8+zDtYbohDNpavihNyupen5hYXIoUGzm3isb/7nf7liqoO9NB5mP4lcK 5zghAq3iXbhBZu4PUaWCjxzHvxQdYiWGzcXfc4gj3E6m09+HIGcokpEg4sHR7B3CjjdY Y4hfF1YMVwRr/2oA2eoAJMqW2Eu0K96YlcM9V6U0MI1xci1SfTqLBO1Znu42J7EC0BU9 0dDA==
Received: by 10.68.134.161 with SMTP id pl1mr20528862pbb.29.1344274390793; Mon, 06 Aug 2012 10:33:10 -0700 (PDT)
Received: from spandex.local (66-230-81-165-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.81.165]) by mx.google.com with ESMTPS id pe8sm5913192pbc.76.2012.08.06.10.33.08 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 06 Aug 2012 10:33:09 -0700 (PDT)
Message-ID: <501FFFD3.6060501@gmail.com>
Date: Mon, 06 Aug 2012 09:33:07 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: So, where to repeat?
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Aug 2012 17:33:11 -0000

This appears to be turning into a survey.  My views are no doubt colored
by it being difficult, expensive, and slow to get anywhere (I live near
Fairbanks, AK) so travel doesn't figure very prominently into how I
feel about various venues.  But even if it did ...  I go to IETF
meetings to get work done, and it's been easier some places than others.
Minneapolis has consistently had outstanding meeting facilities, and
I thought the facilities in Vancouver last week were excellent, too
(and the network team did an outstanding job - many thanks!).
Inexpensive, edible food is a huge plus, and there again, Minneapolis
and Vancouver have stood out.  But still, the only really serious
consideration for me is whether or not the facilities make it easier
to get done the things that need to get done.

Melinda

From scott.brim@gmail.com  Mon Aug  6 10:44:53 2012
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 DA3BC21F84EF for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 10:44:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.592
X-Spam-Level: 
X-Spam-Status: No, score=-103.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mu0PbIr547Kq for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 10:44:53 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5219121F84EA for <ietf@ietf.org>; Mon,  6 Aug 2012 10:44:53 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so3053447ggn.31 for <ietf@ietf.org>; Mon, 06 Aug 2012 10:44:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ASGZ/J4Djjl1nyhI3d/YexyjENACnSzMWX087TDj96g=; b=vS95kL9rTfJAAT3pG6FlMUtDOx+aqqhYVyIU/Mg7Up+EFFXs+I63shF0DlDCD/yFJf xo3uR693tgbRJtZz9WcVP/zohTyTz12LXRms2QDhnRCnhjysuf+wdDlJn3YUpTuTXE09 JZtI3aaOwS3KIzOzAw17P9sQnma9Qt42W0o7hD1VtfYRmWINpuVu4LEQuXghHP7CmcB3 +PAFpv8XDGTwrmQcDL0echq009lrjABlVuT3huoNXaGeggbqTefyzDLeo9Sg4M8+K5Mx CwFrU3fPsGkvL5DpBvp/jX5/B1DmIR9JKhUjwknZh1cq05S8mEOgDp9TVD7/pU9f7UVt Dn6w==
Received: by 10.66.77.229 with SMTP id v5mr2629175paw.60.1344275092454; Mon, 06 Aug 2012 10:44:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.48.231 with HTTP; Mon, 6 Aug 2012 10:44:32 -0700 (PDT)
In-Reply-To: <501FFFD3.6060501@gmail.com>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <501FFFD3.6060501@gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Mon, 6 Aug 2012 13:44:32 -0400
Message-ID: <CAPv4CP99Xdo_kWeGhmKEdg+PLuC0RNvcESZ5cVL7HdG4rVE6Aw@mail.gmail.com>
Subject: Re: So, where to repeat?
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Aug 2012 17:44:54 -0000

On Mon, Aug 6, 2012 at 1:33 PM, Melinda Shore <melinda.shore@gmail.com> wrote:
> feel about various venues.  But even if it did ...  I go to IETF
> meetings to get work done, and it's been easier some places than others.
> Minneapolis has consistently had outstanding meeting facilities, and
> I thought the facilities in Vancouver last week were excellent, too
> (and the network team did an outstanding job - many thanks!).
> Inexpensive, edible food is a huge plus, and there again, Minneapolis
> and Vancouver have stood out.  But still, the only really serious
> consideration for me is whether or not the facilities make it easier
> to get done the things that need to get done.

Using those criteria, I would rate Prague and Beijing as good as or
better than Minneapolis, and cheaper if you avoid the big hotels.

From michal@krsek.cz  Mon Aug  6 10:51:33 2012
Return-Path: <michal@krsek.cz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24FBF21F856D for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 10:51:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.146
X-Spam-Level: 
X-Spam-Status: No, score=0.146 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_CZ=0.445, HOST_EQ_CZ=0.904, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qOzdmUzqaMmt for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 10:51:32 -0700 (PDT)
Received: from io.pinknet.cz (io.pinknet.cz [217.31.57.96]) by ietfa.amsl.com (Postfix) with ESMTP id 7C50221F854A for <ietf@ietf.org>; Mon,  6 Aug 2012 10:51:32 -0700 (PDT)
Received: from [192.168.100.100] (ip-78-45-177-68.net.upcbroadband.cz [78.45.177.68]) by io.pinknet.cz (Postfix) with ESMTP id 33A2C23B042; Mon,  6 Aug 2012 20:09:44 +0200 (CEST)
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <501FFFD3.6060501@gmail.com> <CAPv4CP99Xdo_kWeGhmKEdg+PLuC0RNvcESZ5cVL7HdG4rVE6Aw@mail.gmail.com>
In-Reply-To: <CAPv4CP99Xdo_kWeGhmKEdg+PLuC0RNvcESZ5cVL7HdG4rVE6Aw@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <7542AF25-1990-42A9-98C2-1984C35343F7@krsek.cz>
X-Mailer: iPad Mail (9B206)
From: Michal Krsek <michal@krsek.cz>
Subject: Re: So, where to repeat?
Date: Mon, 6 Aug 2012 19:51:31 +0200
To: Scott Brim <scott.brim@gmail.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Aug 2012 17:51:33 -0000

=46rom central Europe perspective - price for airline ticket to Vancouver in=
 summer is rocket expensive. I can fly to united states for half price.

So "cheap food" cant beat more than $1.000 extra fee paid to airline.

It does not mean YVR is a bad place, but I'd recommend to be carefull when t=
alking about expensiveness.

MK

6. 8. 2012 v 19:44, Scott Brim <scott.brim@gmail.com>:

> On Mon, Aug 6, 2012 at 1:33 PM, Melinda Shore <melinda.shore@gmail.com> wr=
ote:
>> feel about various venues.  But even if it did ...  I go to IETF
>> meetings to get work done, and it's been easier some places than others.
>> Minneapolis has consistently had outstanding meeting facilities, and
>> I thought the facilities in Vancouver last week were excellent, too
>> (and the network team did an outstanding job - many thanks!).
>> Inexpensive, edible food is a huge plus, and there again, Minneapolis
>> and Vancouver have stood out.  But still, the only really serious
>> consideration for me is whether or not the facilities make it easier
>> to get done the things that need to get done.
>=20
> Using those criteria, I would rate Prague and Beijing as good as or
> better than Minneapolis, and cheaper if you avoid the big hotels.

From ajs@anvilwalrusden.com  Mon Aug  6 11:18:39 2012
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 EAEA211E80E0 for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 11:18:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.211
X-Spam-Level: 
X-Spam-Status: No, score=-1.211 tagged_above=-999 required=5 tests=[AWL=-0.371, BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sjA1yUd4s6cA for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 11:18:38 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 340BF11E80DF for <ietf@ietf.org>; Mon,  6 Aug 2012 11:18:38 -0700 (PDT)
Received: from mail.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 8597F8A031 for <ietf@ietf.org>; Mon,  6 Aug 2012 18:18:37 +0000 (UTC)
Date: Mon, 6 Aug 2012 14:18:35 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: So, where to repeat?
Message-ID: <20120806181835.GJ53917@mail.yitter.info>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <501FFFD3.6060501@gmail.com> <CAPv4CP99Xdo_kWeGhmKEdg+PLuC0RNvcESZ5cVL7HdG4rVE6Aw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAPv4CP99Xdo_kWeGhmKEdg+PLuC0RNvcESZ5cVL7HdG4rVE6Aw@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Aug 2012 18:18:39 -0000

On Mon, Aug 06, 2012 at 01:44:32PM -0400, Scott Brim wrote:
> On Mon, Aug 6, 2012 at 1:33 PM, Melinda Shore <melinda.shore@gmail.com> wrote:

> > and Vancouver have stood out.  But still, the only really serious
> > consideration for me is whether or not the facilities make it easier
> > to get done the things that need to get done.
> 
> Using those criteria, I would rate Prague and Beijing as good as or
> better than Minneapolis, and cheaper if you avoid the big hotels.

Thanks to Scott and Melinda for demonstrating the problem I saw in the
original position.  Dave's original argument was that by going back to
places instead of finding new ones, we win by being able to tune.  But
I am unable to see from the evidence the kind of agreement on a site
that results in mere tuning.  For _every_ meeting, I can think of some
set of people who will have reservations about the venue for some
reason.  That is not the basis for simple tuning.  Some people (many
of whom are the squeakiest wheels) appear to have internally
inconsistent sets of demands.

I think the people selecting venues -- return or otherwise -- have a
thankless job, and I think that we should stop trying to manage that
job on a list of a thousand people.  "This worked, that didn't" is,
we've heard, useful feedback.  Aside from that, I don't see what more
we have to say.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From mcr@sandelman.ca  Mon Aug  6 12:15:50 2012
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 24EAF11E80EE for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 12:15:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.135
X-Spam-Level: 
X-Spam-Status: No, score=-1.135 tagged_above=-999 required=5 tests=[AWL=-0.670, BAYES_05=-1.11, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p5uHyg0kmfs7 for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 12:15:49 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 2CA1111E80ED for <ietf@ietf.org>; Mon,  6 Aug 2012 12:15:49 -0700 (PDT)
Received: from sandelman.ca (wlan196.sandelman.ca [209.87.252.196]) by relay.sandelman.ca (Postfix) with ESMTPS id 189A3829B for <ietf@ietf.org>; Mon,  6 Aug 2012 15:11:18 -0400 (EDT)
Received: from sandelman.ca (quigon.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 36923CA952 for <ietf@ietf.org>; Fri,  3 Aug 2012 20:43:47 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: Re: Proposed IETF 95 date change
In-reply-to: <501AC4A8.9050203@concordia.ca>
References: <501AC4A8.9050203@concordia.ca>
Comments: In-reply-to John William Atwood <william.atwood@concordia.ca> message dated "Thu, 02 Aug 2012 14:19:20 -0400."
X-Mailer: MH-E 8.3; nmh 1.3; XEmacs 21.4 (patch 22)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 03 Aug 2012 20:43:47 -0400
Message-ID: <27150.1344041027@sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Aug 2012 19:15:50 -0000

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


>>>>> "John" =3D=3D John William Atwood <william.atwood@concordia.ca> write=
s:
    John> It's not clear to me which is less desirable, starting on
    John> Easter day, or finishing on Good Friday.  Both are important
    John> from the Christian perspective.  However, for a significant
    John> part of the IETF membership, neither Easter nor Good Friday is
    John> important.  My vote would be to leave it where it is.

It's not the "holiday" that is important, it's the congestion at the
airport that concerns me.  Either week accomodates travelling on the
Saturday of easter weekend, as being the possible "out".

I am not clear if we even know where it will be.

=2D-=20
Michael Richardson
=2Don the airplane-

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

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

iQEcBAABAgAGBQJQHHBCAAoJEKD0KQ7Gj3P2NJ0IALm75xBG47drefKYx5QVsBgD
u1++mWrtAOmdSiAdVX69i2rVtO7jMfmbNrAbE/IqPpv10mVnt1FEwVcBgnJBMPsY
x8K1TKD5JCr1n356Eu9Gzc/9ehpYG1zPK4aZRFvGiqqXYrRGc27mtZU4v8pJIAFN
dtZgOTjT698zLVvO0W3/7p3wtJ1ueXnPZFFS7AwK3rFMHIAsdnlrtsfpQVGZ+obR
QXUJZZ20b/xhWa5qW5nugzJExNjH2w7Cd1I7i/SvYjIz2GkCB/G05BDGJ0e2+ZBd
4UH6g3MjwWmfno3FxydsumPGbuyHU5M1aiuNDd4Y3XXay6fvthDfr6Yxb3n27dg=
=PSYT
-----END PGP SIGNATURE-----
--=-=-=--

From mehmet.ersue@nsn.com  Mon Aug  6 12:38:23 2012
Return-Path: <mehmet.ersue@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 D1B2721E80A1 for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 12:38:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.576
X-Spam-Level: 
X-Spam-Status: No, score=-106.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MZSnfdfN3+BI for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 12:38:23 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 7DAB721E809E for <ietf@ietf.org>; Mon,  6 Aug 2012 12:38:22 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q76Jc8Yb005563 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 6 Aug 2012 21:38:08 +0200
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q76Jc8T2031036; Mon, 6 Aug 2012 21:38:08 +0200
Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 6 Aug 2012 21:38:08 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Subject: RE: So, where to repeat?  (was:Re: management granularity)
Date: Mon, 6 Aug 2012 21:38:05 +0200
Message-ID: <80A0822C5E9A4440A5117C2F4CD36A6404183C73@DEMUEXC006.nsn-intra.net>
In-Reply-To: <20120806120547.GA20379@crankycanuck.ca>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: So, where to repeat?  (was:Re: management granularity)
Thread-Index: Ac1zy/YWdQBIwqnQSKmmk5fgy6kOUQAPU36A
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com><501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca>
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: "ext Andrew Sullivan" <ajs@anvilwalrusden.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 06 Aug 2012 19:38:08.0064 (UTC) FILETIME=[01679400:01CD740B]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 5248
X-purgate-ID: 151667::1344281888-00002E58-468AE1EF/0-0/0-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, 06 Aug 2012 19:38:24 -0000

SSBtYWRlIGFsd2F5cyBnb29kIGV4cGVyaWVuY2VzIHdpdGggbWVldGluZyB2ZW51ZXMgaW4gdGhl
IGRvd250b3duIG9mIGh1YiBjaXRpZXMgd2l0aCBnb29kIGZsaWdodCBjb25uZWN0aW9ucy4NCkFz
IGEgRXVyb3BlYW4gZm9yIG1lIHRoZSBlYXN0IGNvYXN0IG9mIE5vcnRoIEFtZXJpY2EgaXMgYmV0
dGVyIHRoYW4gdGhlIHdlc3QgY29hc3QuDQoNClNvIGZhciBteSBleHBlcmllbmNlIHdhcyB2ZXJ5
IGdvb2Qgd2l0aCBmb2xsb3dpbmcgbWVldGluZyBsb2NhdGlvbnMgYW5kIHdvdWxkIGFncmVlIGZv
ciBhIHJlcGV0aXRpb246IA0KVmFuY291dmVyLCBDaGljYWdvLCBTYW4gRnJhbmNpc2NvLCBQaGls
YWRlbHBoaWEsIFBhcmlzLCBMb25kb24sIFN0b2NraG9sbSBhbmQgZXZlbiBNaW5uZWFwb2xpcyAo
YnJycikuDQoNCkJhZCBleHBlcmllbmNlcyB3ZXJlOiBEdWJsaW4gKDYwIG1pbi4gYXMgYSBzdW0g
dG8gZHJpdmUgZm9yIGEgZGlubmVyKSwgTWFhc3RyaWNodCAoNjAgbWluLiBhcyBhIHN1bSB0byB3
YWxrIGZvciBhIGRpbm5lciksIEFuYWhlaW0gKGZhciBhd2F5IGZyb20gdGhlIExBIGFpcnBvcnQp
DQoNCldoeSBkb24ndCB3ZSBhY3R1YWxseSBwbGFuIGEgbWVldGluZyBpbiBCb3N0b24sIE5ldyBZ
b3JrLCBNYWRyaWQsIG9yIExpc2Jvbj8NCg0KQ2hlZXJzLCANCk1laG1ldCANCg0KDQo+IC0tLS0t
T3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IGlldGYtYm91bmNlc0BpZXRmLm9yZyBbbWFp
bHRvOmlldGYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIGV4dCBBbmRyZXcNCj4gU3Vs
bGl2YW4NCj4gU2VudDogTW9uZGF5LCBBdWd1c3QgMDYsIDIwMTIgNTowNiBBTQ0KPiBUbzogaWV0
ZkBpZXRmLm9yZw0KPiBTdWJqZWN0OiBTbywgd2hlcmUgdG8gcmVwZWF0PyAod2FzOlJlOiBtYW5h
Z2VtZW50IGdyYW51bGFyaXR5KQ0KPiANCj4gT24gU3VuLCBBdWcgMDUsIDIwMTIgYXQgMTE6NTg6
MTlBTSAtMDcwMCwgRGF2ZSBDcm9ja2VyIHdyb3RlOg0KPiA+IGVub3VnaCBtZXJlbHkgdG8gaGF2
ZSBleGNlbGxlbnQgc3RhZmYuICBXZSBuZWVkIHRvIGdvIGJhY2sgdG8gdGhlDQo+ID4gYmV0dGVy
IHBsYWNlcyBhbmQgYmVuZWZpdCBmcm9tIHRoZSBsZWFybmluZyBjdXJ2ZS4gIFRoaXMgZG9lc24n
dA0KPiA+IG1lYW4gIm5vIG5ldyB2ZW51ZXMiIGJ1dCBpdCBtZWFucyBmZXdlci4NCj4gDQo+IEFz
IGEgcHJhY3RpY2FsIG1hdHRlciwgbWF5IEkgYXNrIGFib3V0IHdoaWNoIHZlbnVlcyB5b3Ugd2Fu
dCB0byByZXR1cm4NCj4gdG8/ICBJIGdldCB5b3VyIGFyZ3VtZW50IGluIHByaW5jaXBsZSwgYnV0
IGl0IHNlZW1zIHRvIG1lIHRoYXQgdGhlcmUNCj4gaGFzIGJlZW4gcXVpdGUgYSBsb3Qgb2YgY29t
cGxhaW5pbmcgaW4gdGhlIHBhc3QuICBUaGUgb25lIGZhY3RvciB0aGF0DQo+IHNlZW1zIHRvIG1l
IG1vc3QgbGlrZWx5IHRvIHJlZHVjZSBjb21wbGFpbnRzIC0tIHdlYXRoZXIgLS0gaXMNCj4gZXZp
ZGVudGx5IGJleW9uZCB0aGUgU2VjcmV0YXJpYXQncyBvciBJQU9DJ3MgY29udHJvbC4NCj4gDQo+
IFBlb3BsZSBzZWVtIGluY2xpbmVkIHRvIHJldHVybiB0byB0aGUgSHlhdHQgaW4gVmFuY291dmVy
LCBlbGV2YXRvcnMNCj4gbm90d2l0aHN0YW5kaW5nLiAgV2UncmUgZ29pbmcgdG8gZG8gdGhhdC4g
IChJIGRvbid0IHVuZGVyc3RhbmQgd2h5IHRoZQ0KPiBwcmV2aW91cyBWZW5jb3V2ZXIgdmVudWUg
d2FzIGxlc3MgZGVzaXJhYmxlIC0tIHRvIG1lLCB0aGVzZSB2ZW51ZXMNCj4gd2VyZSB2ZXJ5IHNp
bWlsYXIsIGFuZCBub3QgdmVyeSBmYXIgYXBhcnQuICBJIG5vdGUsIGhvd2V2ZXIsIHRoYXQgdGhl
DQo+IHByZXZpb3VzIHR3byBWYW5jb3V2ZXIgdmlzaXRzIHdlcmUgbmVhciB0aGUgZW5kIG9mIHRo
ZSB5ZWFyLCB3aGVuIGl0DQo+IHJhaW5zIGFsbCB0aGUgdGltZSBpbiBWYW5jb3V2ZXIuKQ0KPiAN
Cj4gUGVvcGxlIGNvbXBsYWluZWQgYXQgbGVuZ3RoIGFib3V0IHRoZSB2ZW51ZSBpbiBQYXJpcywg
c28gSSBwcmVzdW1lDQo+IGl0J3Mgb3V0Lg0KPiANCj4gU29tZSBwZW9wbGUgY29tcGxhaW5lZCBh
Ym91dCB0aGUgaG90ZWwgcm9vbSBwcmljZXMgYW5kIHRyYXZlbCBleHBlbnNlDQo+IGluIFRhaXBl
aSwgdGhvdWdoIEkgaGVhcmQgcmVtYXJrcyB0aGF0IGl0IHdhcyBhIGdvb2QgdmVudWUuDQo+IFNo
b3VsZCB3ZSB0cnkgdG8gcmV0dXJuIHRoZXJlPw0KPiANCj4gUGVvcGxlIGNvbXBsYWluZWQgaW4g
YWR2YW5jZSBhYm91dCBnZXR0aW5nIHRvIFF1w6liZWMsIGFsdGhvdWdoDQo+IGFmdGVyd2FyZHMg
SSBoZWFyZCBsb3RzIG9mIGdvb2Qgbm9pc2VzIGFib3V0IHRoYXQgdmVudWUuICBJIG5vdGUgdGhh
dA0KPiB0aGUgd2VhdGhlciB3YXMgZ3JlYXQuICBTaG91bGQgd2UgdHJ5IHRvIHJldHVybj8NCj4g
DQo+IEkgZG9uJ3QgcmVjYWxsIG11Y2ggY29tcGxhaW5pbmcgYWJvdXQgdGhlIFByYWd1ZSB2ZW51
ZSBpbiAyMDExLCB3aGljaA0KPiB3YXMgc3RyaWtpbmcgdG8gbWUgYmVjYXVzZSB2ZXJ5IGxpdHRs
ZSBzZWVtZWQgZGlmZmVyZW50IHRvIG1lIGNvbXBhcmVkDQo+IHRvIG91ciBmaXJzdCB2aXNpdCB0
aGVyZS4gIFBlcmhhcHMgdGhpcyBpcyBldmlkZW5jZSBvZiB0aGUgInR1bmluZyINCj4geW91IHN1
Z2dlc3QgKGVuc3VyaW5nIHRoZSB3YXRlciBib3R0bGVzIHdlcmUgcGxhc3RpYywgZm9yIGluc3Rh
bmNlKS4NCj4gQnV0IEkgbm90ZSB0aGUgd2VhdGhlciB3YXMgZXhjZWxsZW50Lg0KPiANCj4gQmVp
amluZz8gIEkgZ3Vlc3MgTWFhc3RyaWNodCBpcyBvdXQuIEFuYWhlaW0gKEZXSVcsIEkgdGhvdWdo
dCB0aGF0IHdhcw0KPiBhbiBleGFtcGxlIG9mIGEgdGVycmlibGUgbG9jYXRpb24sIGJ1dCBtYW55
IHBlb3BsZSBzZWVtZWQgaGFwcHkgd2l0aA0KPiBpdCk/ICBIaXJvc2hpbWE/ICBTdG9ja2hvbG0/
ICBTYW4gRnJhbmNpc2NvICh3ZSB0aG91Z2h0IHRoZSBjcmltZSBhdA0KPiBQYXJpcyB3YXMgYmFk
LCB5ZXQgZGlkbid0IGNvbXBsYWluIGFib3V0IGJlaW5nIHNtYWNrIHVwIGFnYWluc3QgdGhlDQo+
IFRlbmRlcmxvaW4pPyAgT3IgdGhlcmUncyB0aGUgb2xkIHN0YW5kYnksIE1pbm5lYXBvbGlzOyBw
ZXJoYXBzIHdlDQo+IGNvdWxkIGRvIGl0IGluIE1hcmNoLiAgVGhlIER1YmxpbiB2ZW51ZSB3YXMg
cGFubmVkIGJ5IGxhcmdlIG51bWJlcnMgb2YNCj4gcGVvcGxlLiAgUGhpbGFkZWxwaGlhLCBwZW9w
bGUgY29tcGxhaW5lZCBhYm91dCBleHBlbnNlLiAgQ2hpY2FnbywgdG9vDQo+IChjb21iaW5lZCB3
aXRoIGhvdGVsIHJlbm92YXRpb25zKS4NCj4gDQo+IFRoYXQgZ2V0cyB1cyBiYWNrIHRocm91Z2gg
MjAwNy4gIFdoaWNoIG9mIHRoZSB2ZW51ZXMgZG8geW91IHRoaW5rIHdlDQo+IHNob3VsZCByZXR1
cm4gdG8sIHRvIHdoaWNoIHdlIGFscmVhZHkgaGF2ZW4ndCByZXR1cm5lZCBvciBwbGFubmVkIHRv
DQo+IHJldHVybj8gIEFuZCB3aHk/DQo+IA0KPiBGb3Igd2hhdCBpdCdzIHdvcnRoLCBJIHdvdWxk
IG5vdCBjb21wbGFpbiBhYm91dCByZXR1cm5pbmcgdG8gYW55IG9mDQo+IHRob3NlIHZlbnVlczsg
SSBwZXJzb25hbGx5IGhhZCBnb29kIG1lZXRpbmdzIGF0IGFsbCBvZiB0aGVtIGV4Y2VwdA0KPiBI
aXJvc2hpbWEsIHdoaWNoIEkgbWlzc2VkIGR1ZSB0byBvdGhlciBjb21taXRtZW50cy4gIFRoYXQg
aW5jbHVkZXMNCj4gYm90aCBNYWFzdHJpY2h0IGFuZCBEdWJsaW4sIHdoaWNoIHdlcmUgYm90aCBh
cHBhcmVudGx5IHRyaWFscyBmb3INCj4gbGFyZ2UgbnVtYmVycyBvZiBvdGhlcnMuDQo+IA0KPiBC
ZXN0LA0KPiANCj4gQQ0KPiANCj4gLS0NCj4gQW5kcmV3IFN1bGxpdmFuDQo+IGFqc0BhbnZpbHdh
bHJ1c2Rlbi5jb20NCg0K

From mrex@sap.com  Mon Aug  6 15:02:22 2012
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 415A811E80DC for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 15:02:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.15
X-Spam-Level: 
X-Spam-Status: No, score=-10.15 tagged_above=-999 required=5 tests=[AWL=0.099,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Cd4kdlimh-k for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 15:02:17 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 6BF6F11E80BF for <ietf@ietf.org>; Mon,  6 Aug 2012 15:02:17 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id q76M29XZ007982 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Aug 2012 00:02:09 +0200 (MEST)
Subject: Re: ITU-T Dubai Meeting
In-Reply-To: <DBC678C7-7C9C-4B47-A396-317D62AF82F5@cs.columbia.edu>
To: Steven Bellovin <smb@cs.columbia.edu>
Date: Tue, 7 Aug 2012 00:02:08 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20120806220208.D443E1A126@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
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, 06 Aug 2012 22:02:22 -0000

Steven Bellovin wrote:
> 
> Randy Bush wrote:
>> 
>> whatever the number of address bits, if it is fixed, we always run out.
>> memory addressing has been a cliff many times.  ip addressing.  ...
> 
> Yup.  To quote Fred Brooks on memory address space: "Every successful
> computer architecture eventually runs out of address space" -- and I heard
> him say that in 1973.

I'm wondering what resource shortage would have happened if IPv6
had been massively adopted 10 years earlier, and whether we would have
seen the internet backbone routers suffer severely from the size
of the routing tables, if every single home customer (DSL subscriber)
would have required a provider-independent IPv6 network prefix rather
than a single, provider-dependent IPv4 IP Address.

-Martin

From richard@shockey.us  Mon Aug  6 16:20:36 2012
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 6483B11E80BF for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 16:20:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.908
X-Spam-Level: 
X-Spam-Status: No, score=-99.908 tagged_above=-999 required=5 tests=[AWL=0.586, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pzp+vNNqBPp6 for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 16:20:30 -0700 (PDT)
Received: from oproxy12-pub.bluehost.com (unknown [IPv6:2605:dc00:100:2::a4]) by ietfa.amsl.com (Postfix) with SMTP id 47E1B11E80A5 for <ietf@ietf.org>; Mon,  6 Aug 2012 16:20:30 -0700 (PDT)
Received: (qmail 20385 invoked by uid 0); 6 Aug 2012 20:33:02 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy12.bluehost.com with SMTP; 6 Aug 2012 20:33:02 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us; s=default;  h=Content-Type:MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:To:From; bh=gtdGjCe9hfemPpfC7I5xQgnHTxMXdDY+GBdITXnX8/8=;  b=mM356XF+vrhGDLpi2BwGk7MNWU4ExEEq9+N+ciPybj2pKQHr/uMXfHp/DLhQLUTFFEZZ0ObF3e/Z6W4hzhGsOjdgifSOHaKgg4NJg1bh7SvaQ/MXrx4k3qL6Wcq89oRu;
Received: from [71.191.243.130] (port=64537 helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.76) (envelope-from <richard@shockey.us>) id 1SyTz3-0005gU-3W for ietf@ietf.org; Mon, 06 Aug 2012 14:33:01 -0600
From: "Richard Shockey" <richard@shockey.us>
To: <ietf@ietf.org>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com>	<501EC24B.4080709@bbiw.net>	<20120806120547.GA20379@crankycanuck.ca>	<B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se>	<B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net>	<E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net>	<B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com>
In-Reply-To: <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com>
Subject: RE: So, where to repeat? (was:Re: management granularity)
Date: Mon, 6 Aug 2012 16:32:59 -0400
Message-ID: <01ae01cd7412$abe83e50$03b8baf0$@us>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01AF_01CD73F1.24D69E50"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac1z4ZxBQgc7eB0wQHiDupL5PDQ4fgAFvRvw
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 71.191.243.130 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: Mon, 06 Aug 2012 23:20:36 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_01AF_01CD73F1.24D69E50
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

=20

=20

[RS> ] +1 and no employer ever argued that going to Minneapolis was a
boondoggle.  The Hilton in Minneapolis  of all the IETF meetings I=92ve
attended has the most optimal layout of meeting rooms etc.=20

=20

=20

If we were to choose one place in the U.S. to meet, Minneapolis is the =
best
choice IMHO.  It's very reasonably priced, easy for many to get to and =
the
hotel has adequate space for us (even back when we had many more =
attendees).
Personally, the weather is not critical to me, since I spend the vast
majority of my time in the hotel meeting rooms, so I'm very happy if we =
meet
there in March and November.  =20

=20

Mary

=20

On Mon, Aug 6, 2012 at 9:18 AM, Dearlove, Christopher (UK)
<Chris.Dearlove@baesystems.com> wrote:

I've never been to an IETF meeting where the plane fare has exceeded the
hotel cost for a week. Caveats to that are that I have mostly gone for =
IETF
recommended hotels, so may have missed particularly cheap hotels, and =
that I
have only been to North American and Europe (but that statistic includes
Vancouver and the even further away western US cities down to San =
Diego).
And of course I fly economy, and it's much cheaper including a Saturday
night in your trip, even at the cost of an extra night in a hotel (at =
least
it is from here). An almost exception was Paris this year where I was
staying fairly cheaply, but that was a cost-shared trip between me and =
my
employer, and I didn't fly (I went by train - though that's not cheaper,
just better). Paris has cheap(er) hotels and a metro I understand, so I =
felt
less location constrained.


--
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194 <tel:%2B44%201245%20242194>  |  Fax: +44 1245 =
242124
<tel:%2B44%201245%20242124>=20
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace =
Centre,
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----

From: Sprecher, Nurit (NSN - IL/Hod HaSharon)
[mailto:nurit.sprecher@nsn.com]
Sent: 06 August 2012 15:07
To: Dearlove, Christopher (UK); Daniele Ceccarelli; Andrew Sullivan;
ietf@ietf.org
Subject: RE: So, where to repeat? (was:Re: management granularity)

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

When you are not close (time), flight cost may become higher in the =
priority
(over hotem)....
Flying to Vancouver for me for example is the most expensive =
trip....even
though the city is amazing and the host was wonderful!

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of =
ext
Dearlove, Christopher (UK)
Sent: Monday, August 06, 2012 4:56 PM
To: Daniele Ceccarelli; Andrew Sullivan; ietf@ietf.org
Subject: RE: So, where to repeat? (was:Re: management granularity)

Dublin's problem was that the venue was isolated from the city. This has
also been the case with e.g. San Diego. (I'm assuming no personal car.)
Contrast with Minneapolis (and several other places) where you were =
right in
the city. Being in a city is better for lunch and dinner options, taking =
a
break to go to a bookshop (or to buy something you forgot to bring) and =
so
on. (I'm deliberately not including tourism here.)

However at the moment my priorities to make being able to attend =
possible
would be time (so the closer to me the better - I realise that's =
impossible
globally), cost (hotel first, flight second, rest is noise) and the =
ability
to plan ahead to only attend part of the week. This is the current =
economic
reality. Dublin actually scores quite well on those for me.

--
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194 <tel:%2B44%201245%20242194>  |  Fax: +44 1245 =
242124
<tel:%2B44%201245%20242124>=20
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace =
Centre,
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Daniele Ceccarelli
Sent: 06 August 2012 13:24
To: Andrew Sullivan; ietf@ietf.org
Subject: RE: So, where to repeat? (was:Re: management granularity)

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

Dublin panned? I thought it was one of the best venues and locations of =
the
last meetings.

What about Italy or Spain? I've never heard about an IETF in Italy. I'm =
ok
with meetings outside Italy since i like traveling very much, but i was
wondering why it has never been taken into account in the past meetings. =
Is
it expensive? I think Italy and Spain are much cheaper than France, UK =
or
Sweden, aren't they?

BR
Daniele

>-----Original Message-----
>From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On
>Behalf Of Andrew Sullivan
>Sent: luned=EC 6 agosto 2012 14.06
>To: ietf@ietf.org
>Subject: So, where to repeat? (was:Re: management granularity)
>
>On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:
>> enough merely to have excellent staff.  We need to go back to the
>> better places and benefit from the learning curve.  This
>doesn't mean
>> "no new venues" but it means fewer.
>
>As a practical matter, may I ask about which venues you want
>to return to?  I get your argument in principle, but it seems
>to me that there has been quite a lot of complaining in the
>past.  The one factor that seems to me most likely to reduce
>complaints -- weather -- is evidently beyond the Secretariat's
>or IAOC's control.
>
>People seem inclined to return to the Hyatt in Vancouver,
>elevators notwithstanding.  We're going to do that.  (I don't
>understand why the previous Vencouver venue was less desirable
>-- to me, these venues were very similar, and not very far
>apart.  I note, however, that the previous two Vancouver
>visits were near the end of the year, when it rains all the
>time in Vancouver.)
>
>People complained at length about the venue in Paris, so I
>presume it's out.
>
>Some people complained about the hotel room prices and travel
>expense in Taipei, though I heard remarks that it was a good venue.
>Should we try to return there?
>
>People complained in advance about getting to Qu=E9bec, although
>afterwards I heard lots of good noises about that venue.  I
>note that the weather was great.  Should we try to return?
>
>I don't recall much complaining about the Prague venue in
>2011, which was striking to me because very little seemed
>different to me compared to our first visit there.  Perhaps
>this is evidence of the "tuning"
>you suggest (ensuring the water bottles were plastic, for instance).
>But I note the weather was excellent.
>
>Beijing?  I guess Maastricht is out. Anaheim (FWIW, I thought
>that was an example of a terrible location, but many people
>seemed happy with it)?  Hiroshima?  Stockholm?  San Francisco
>(we thought the crime at Paris was bad, yet didn't complain
>about being smack up against the Tenderloin)?  Or there's the
>old standby, Minneapolis; perhaps we could do it in March.
>The Dublin venue was panned by large numbers of people.
>Philadelphia, people complained about expense.  Chicago, too
>(combined with hotel renovations).
>
>That gets us back through 2007.  Which of the venues do you
>think we should return to, to which we already haven't
>returned or planned to return?  And why?
>
>For what it's worth, I would not complain about returning to
>any of those venues; I personally had good meetings at all of
>them except Hiroshima, which I missed due to other
>commitments.  That includes both Maastricht and Dublin, which
>were both apparently trials for large numbers of others.
>
>Best,
>
>A
>
>--
>Andrew Sullivan
>ajs@anvilwalrusden.com
>
>

********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************

=20


------=_NextPart_000_01AF_01CD73F1.24D69E50
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-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=3Diso-8859-1"><meta name=3DGenerator content=3D"Microsoft Word =
12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[RS&gt; ] +1 and no employer ever argued that going to Minneapolis =
was a boondoggle.&nbsp; The Hilton in Minneapolis &nbsp;of all the IETF =
meetings I&#8217;ve attended has the most optimal layout of meeting =
rooms etc. <o:p></o:p></span></i></b></p><p =
class=3DMsoNormal><b><i><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></i></b></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p></div><div><p class=3DMsoNormal>If we =
were to choose one place in the U.S. to meet, Minneapolis is the best =
choice IMHO. &nbsp;It's very reasonably priced, easy for many to get to =
and the hotel has adequate space for us (even back when we had many more =
attendees). &nbsp;Personally, the weather is not critical to me, since I =
spend the vast majority of my time in the hotel meeting rooms, so I'm =
very happy if we meet there in March and November. =
&nbsp;&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Mary<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On Mon, =
Aug 6, 2012 at 9:18 AM, Dearlove, Christopher (UK) &lt;<a =
href=3D"mailto:Chris.Dearlove@baesystems.com" =
target=3D"_blank">Chris.Dearlove@baesystems.com</a>&gt; =
wrote:<o:p></o:p></p><p class=3DMsoNormal>I've never been to an IETF =
meeting where the plane fare has exceeded the hotel cost for a week. =
Caveats to that are that I have mostly gone for IETF recommended hotels, =
so may have missed particularly cheap hotels, and that I have only been =
to North American and Europe (but that statistic includes Vancouver and =
the even further away western US cities down to San Diego). And of =
course I fly economy, and it's much cheaper including a Saturday night =
in your trip, even at the cost of an extra night in a hotel (at least it =
is from here). An almost exception was Paris this year where I was =
staying fairly cheaply, but that was a cost-shared trip between me and =
my employer, and I didn't fly (I went by train - though that's not =
cheaper, just better). Paris has cheap(er) hotels and a metro I =
understand, so I felt less location constrained.<o:p></o:p></p><div><p =
class=3DMsoNormal><br>--<br>Christopher Dearlove<br>Senior Principal =
Engineer, Communications Group<br>Communications, Networks and Image =
Analysis Capability<br>BAE Systems Advanced Technology Centre<br>West =
Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<br>Tel: <a =
href=3D"tel:%2B44%201245%20242194">+44 1245 242194</a>&nbsp;| &nbsp;Fax: =
<a href=3D"tel:%2B44%201245%20242124">+44 1245 242124</a><br><a =
href=3D"mailto:chris.dearlove@baesystems.com">chris.dearlove@baesystems.c=
om</a> | <a href=3D"http://www.baesystems.com" =
target=3D"_blank">http://www.baesystems.com</a><br><br>BAE Systems =
(Operations) Limited<br>Registered Office: Warwick House, PO Box 87, =
Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, =
UK<br>Registered in England &amp; Wales No: =
1996687<br><br><br>-----Original =
Message-----<o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>From: Sprecher, Nurit (NSN - IL/Hod =
HaSharon) [mailto:<a =
href=3D"mailto:nurit.sprecher@nsn.com">nurit.sprecher@nsn.com</a>]<br>Sen=
t: 06 August 2012 15:07<br>To: Dearlove, Christopher (UK); Daniele =
Ceccarelli; Andrew Sullivan; <a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>Subject: RE: So, =
where to repeat? (was:Re: management =
granularity)<o:p></o:p></p></div><div><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>----------------------! WARNING ! =
----------------------<br>This message originates from outside our =
organisation,<br>either from an external partner or from the =
internet.<br>Keep this in mind if you answer this message.<br>Follow the =
'Report Suspicious Emails' link on IT matters<br>for instructions on =
reporting suspicious email =
messages.<br>--------------------------------------------------------<br>=
<br>When you are not close (time), flight cost may become higher in the =
priority (over hotem)....<br>Flying to Vancouver for me for example is =
the most expensive trip....even though the city is amazing and the host =
was wonderful!<br><br>-----Original Message-----<br>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 ext Dearlove, Christopher (UK)<br>Sent: Monday, August 06, =
2012 4:56 PM<br>To: Daniele Ceccarelli; Andrew Sullivan; <a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>Subject: RE: So, =
where to repeat? (was:Re: management granularity)<br><br>Dublin's =
problem was that the venue was isolated from the city. This has also =
been the case with e.g. San Diego. (I'm assuming no personal car.) =
Contrast with Minneapolis (and several other places) where you were =
right in the city. Being in a city is better for lunch and dinner =
options, taking a break to go to a bookshop (or to buy something you =
forgot to bring) and so on. (I'm deliberately not including tourism =
here.)<br><br>However at the moment my priorities to make being able to =
attend possible would be time (so the closer to me the better - I =
realise that's impossible globally), cost (hotel first, flight second, =
rest is noise) and the ability to plan ahead to only attend part of the =
week. This is the current economic reality. Dublin actually scores quite =
well on those for me.<br><br>--<br>Christopher Dearlove<br>Senior =
Principal Engineer, Communications Group<br>Communications, Networks and =
Image Analysis Capability<br>BAE Systems Advanced Technology =
Centre<br>West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, =
UK<br>Tel: <a href=3D"tel:%2B44%201245%20242194">+44 1245 =
242194</a>&nbsp;| &nbsp;Fax: <a href=3D"tel:%2B44%201245%20242124">+44 =
1245 242124</a><br><a =
href=3D"mailto:chris.dearlove@baesystems.com">chris.dearlove@baesystems.c=
om</a> | <a href=3D"http://www.baesystems.com" =
target=3D"_blank">http://www.baesystems.com</a><br><br>BAE Systems =
(Operations) Limited<br>Registered Office: Warwick House, PO Box 87, =
Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, =
UK<br>Registered in England &amp; Wales No: =
1996687<br><br><br>-----Original Message-----<br>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 Daniele Ceccarelli<br>Sent: 06 August 2012 13:24<br>To: Andrew =
Sullivan; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>Subject: =
RE: So, where to repeat? (was:Re: management =
granularity)<br><br>----------------------! WARNING ! =
----------------------<br>This message originates from outside our =
organisation,<br>either from an external partner or from the =
internet.<br>Keep this in mind if you answer this message.<br>Follow the =
'Report Suspicious Emails' link on IT matters<br>for instructions on =
reporting suspicious email =
messages.<br>--------------------------------------------------------<br>=
<br>Dublin panned? I thought it was one of the best venues and locations =
of the last meetings.<br><br>What about Italy or Spain? I've never heard =
about an IETF in Italy. I'm ok with meetings outside Italy since i like =
traveling very much, but i was wondering why it has never been taken =
into account in the past meetings. Is it expensive? I think Italy and =
Spain are much cheaper than France, UK or Sweden, aren't =
they?<br><br>BR<br>Daniele<br><br>&gt;-----Original =
Message-----<br>&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<br>&gt;Behalf Of Andrew Sullivan<br>&gt;Sent: luned=EC 6 agosto 2012 =
14.06<br>&gt;To: <a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>&gt;Subject: So, =
where to repeat? (was:Re: management granularity)<br>&gt;<br>&gt;On Sun, =
Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:<br>&gt;&gt; enough =
merely to have excellent staff. &nbsp;We need to go back to =
the<br>&gt;&gt; better places and benefit from the learning curve. =
&nbsp;This<br>&gt;doesn't mean<br>&gt;&gt; &quot;no new venues&quot; but =
it means fewer.<br>&gt;<br>&gt;As a practical matter, may I ask about =
which venues you want<br>&gt;to return to? &nbsp;I get your argument in =
principle, but it seems<br>&gt;to me that there has been quite a lot of =
complaining in the<br>&gt;past. &nbsp;The one factor that seems to me =
most likely to reduce<br>&gt;complaints -- weather -- is evidently =
beyond the Secretariat's<br>&gt;or IAOC's control.<br>&gt;<br>&gt;People =
seem inclined to return to the Hyatt in Vancouver,<br>&gt;elevators =
notwithstanding. &nbsp;We're going to do that. &nbsp;(I =
don't<br>&gt;understand why the previous Vencouver venue was less =
desirable<br>&gt;-- to me, these venues were very similar, and not very =
far<br>&gt;apart. &nbsp;I note, however, that the previous two =
Vancouver<br>&gt;visits were near the end of the year, when it rains all =
the<br>&gt;time in Vancouver.)<br>&gt;<br>&gt;People complained at =
length about the venue in Paris, so I<br>&gt;presume it's =
out.<br>&gt;<br>&gt;Some people complained about the hotel room prices =
and travel<br>&gt;expense in Taipei, though I heard remarks that it was =
a good venue.<br>&gt;Should we try to return =
there?<br>&gt;<br>&gt;People complained in advance about getting to =
Qu=E9bec, although<br>&gt;afterwards I heard lots of good noises about =
that venue. &nbsp;I<br>&gt;note that the weather was great. &nbsp;Should =
we try to return?<br>&gt;<br>&gt;I don't recall much complaining about =
the Prague venue in<br>&gt;2011, which was striking to me because very =
little seemed<br>&gt;different to me compared to our first visit there. =
&nbsp;Perhaps<br>&gt;this is evidence of the =
&quot;tuning&quot;<br>&gt;you suggest (ensuring the water bottles were =
plastic, for instance).<br>&gt;But I note the weather was =
excellent.<br>&gt;<br>&gt;Beijing? &nbsp;I guess Maastricht is out. =
Anaheim (FWIW, I thought<br>&gt;that was an example of a terrible =
location, but many people<br>&gt;seemed happy with it)? &nbsp;Hiroshima? =
&nbsp;Stockholm? &nbsp;San Francisco<br>&gt;(we thought the crime at =
Paris was bad, yet didn't complain<br>&gt;about being smack up against =
the Tenderloin)? &nbsp;Or there's the<br>&gt;old standby, Minneapolis; =
perhaps we could do it in March.<br>&gt;The Dublin venue was panned by =
large numbers of people.<br>&gt;Philadelphia, people complained about =
expense. &nbsp;Chicago, too<br>&gt;(combined with hotel =
renovations).<br>&gt;<br>&gt;That gets us back through 2007. &nbsp;Which =
of the venues do you<br>&gt;think we should return to, to which we =
already haven't<br>&gt;returned or planned to return? &nbsp;And =
why?<br>&gt;<br>&gt;For what it's worth, I would not complain about =
returning to<br>&gt;any of those venues; I personally had good meetings =
at all of<br>&gt;them except Hiroshima, which I missed due to =
other<br>&gt;commitments. &nbsp;That includes both Maastricht and =
Dublin, which<br>&gt;were both apparently trials for large numbers of =
others.<br>&gt;<br>&gt;Best,<br>&gt;<br>&gt;A<br>&gt;<br>&gt;--<br>&gt;An=
drew Sullivan<br>&gt;<a =
href=3D"mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><br>&gt;=
<br>&gt;<br><br>*********************************************************=
***********<br>This email and any attachments are confidential to the =
intended<br>recipient and may also be privileged. If you are not the =
intended<br>recipient please delete it from your system and notify the =
sender.<br>You should not copy it or use it for any purpose nor disclose =
or<br>distribute its contents to any other =
person.<br>**************************************************************=
******<o:p></o:p></p></div></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_01AF_01CD73F1.24D69E50--


From mcr+ietf@sandelman.ca  Mon Aug  6 17:14:47 2012
Return-Path: <mcr+ietf@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 0E10811E80A5 for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 17:14:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.768
X-Spam-Level: 
X-Spam-Status: No, score=-0.768 tagged_above=-999 required=5 tests=[AWL=-0.468, BAYES_00=-2.599, MANGLED_BEST=2.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l7PdWDL2b-xM for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 17:14:46 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 96DB011E8087 for <ietf@ietf.org>; Mon,  6 Aug 2012 17:14:41 -0700 (PDT)
Received: from obiwan.sandelman.ca (unknown [IPv6:2607:f0b0:f:2:3a60:77ff:fe38:e647]) by tuna.sandelman.ca (Postfix) with ESMTP id F371D20168 for <ietf@ietf.org>; Mon,  6 Aug 2012 20:27:22 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: Re: So, where to repeat? (was:Re: management granularity)
In-Reply-To: <01ae01cd7412$abe83e50$03b8baf0$@us>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <01ae01cd7412$abe83e50$03b8baf0$@us>
X-Mailer: MH-E 8.3; nmh 1.5; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Mon, 06 Aug 2012 20:14:35 -0400
Message-ID: <3983.1344298475@obiwan.sandelman.ca>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 00:14:47 -0000

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


> I've never been to an IETF meeting where the plane fare has exceeded the
> hotel cost for a week.=20

note: I pay my own way, and make all my own arrangements.

The only meetings where my hotel costs exceeded my transporation costs
were the Montreal IETFs (I live in Ottawa).  When I've flown I have
seldom ever been on direct flights.

I *do* avoid the main hotel if the price is poor.  I did get the
Sheraton Wall (backup hotel IETF84), via hotwire.com, which surprised me.

I find staying over saturday night no longer has any affect on my travel
costs.=20

I do prefer returning to the same places, and I do like Minneapolis.
(Yes, even in March and November)

I am more concerned that we have three north-american IETFs in a row
(Vancouver, Atlanta, Orlando), and 4 of the next 6 are in North America.
(Not counting Hawaii as North America for the purposes of travel
budgets, or it's be 5/7)

I'm also concerned about going popular places (Quebec, Orlando) during
peak tourist season.=20

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


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

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

iQCVAwUAUCBd64qHRg3pndX9AQLTFQP/VT6oFxAz4bKiLb4khWYP0es3aLmAkwgy
X33Pr3CVrQLfbYAnjCXQk/vdvdF0oYSJk687xcZRWyBBy8zPLePOUMK38pdlN7sI
pvRiP52bmGoQy9GQLcN2CqvqehVB1FpaY6+NP71jkMb/9GQQumYVRS1k5jYInaT2
CbT2rtnuwkQ=
=jw/o
-----END PGP SIGNATURE-----
--=-=-=--

From mrw@lilacglade.org  Mon Aug  6 17:19:50 2012
Return-Path: <mrw@lilacglade.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 CE72411E80ED for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 17:19:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.707
X-Spam-Level: 
X-Spam-Status: No, score=-95.707 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HTML_MESSAGE=0.001, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vMFlYvJ2nrYv for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 17:19:49 -0700 (PDT)
Received: from ec2-23-21-76-251.compute-1.amazonaws.com (ec2-23-21-76-251.compute-1.amazonaws.com [23.21.76.251]) by ietfa.amsl.com (Postfix) with ESMTP id 167BC11E8087 for <ietf@ietf.org>; Mon,  6 Aug 2012 17:19:36 -0700 (PDT)
Received: from lilac-too.home (permutation-city.suchdamage.org [69.25.196.28]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mail.suchdamage.org (Postfix) with ESMTPSA id EB6EB2002D; Mon,  6 Aug 2012 20:18:34 -0400 (EDT)
Subject: Re: So, where to repeat? (was:Re: management granularity)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-6-919354687
From: Margaret Wasserman <mrw@lilacglade.org>
In-Reply-To: <01ae01cd7412$abe83e50$03b8baf0$@us>
Date: Mon, 6 Aug 2012 20:19:34 -0400
Message-Id: <841C1C01-5581-4535-8B13-3201E3199821@lilacglade.org>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com>	<501EC24B.4080709@bbiw.net>	<20120806120547.GA20379@crankycanuck.ca>	<B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se>	<B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net>	<E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net>	<B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <01ae01cd7412$abe83e50$03b8baf0$@us>
To: Richard Shockey <richard@shockey.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: Tue, 07 Aug 2012 00:19:51 -0000

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


+1

On Aug 6, 2012, at 4:32 PM, Richard Shockey wrote:
> [RS> ] +1 and no employer ever argued that going to Minneapolis was a =
boondoggle.  The Hilton in Minneapolis  of all the IETF meetings I=92ve =
attended has the most optimal layout of meeting rooms etc.
> =20
> If we were to choose one place in the U.S. to meet, Minneapolis is the =
best choice IMHO.  It's very reasonably priced, easy for many to get to =
and the hotel has adequate space for us (even back when we had many more =
attendees).  Personally, the weather is not critical to me, since I =
spend the vast majority of my time in the hotel meeting rooms, so I'm =
very happy if we meet there in March and November.  =20
> =20

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

<html><head><base href=3D"x-msg://132/"></head><body style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div><br></div>+1<div><br><div><div>On Aug 6, 2012, =
at 4:32 PM, Richard Shockey wrote:</div><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
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; "><div lang=3D"EN-US" link=3D"blue" =
vlink=3D"purple"><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: =
'Times New Roman', serif; "><b><i><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">[RS&gt; ] =
+1 and no employer ever argued that going to Minneapolis was a =
boondoggle.&nbsp; The Hilton in Minneapolis &nbsp;of all the IETF =
meetings I=92ve attended has the most optimal layout of meeting rooms =
etc.<o:p></o:p></span></i></b></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><b><i><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></i></b></div></div><div =
style=3D"font-family: Helvetica; font-size: medium; "><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; ">If we were to choose one place in the U.S. to meet, =
Minneapolis is the best choice IMHO. &nbsp;It's very reasonably priced, =
easy for many to get to and the hotel has adequate space for us (even =
back when we had many more attendees). &nbsp;Personally, the weather is =
not critical to me, since I spend the vast majority of my time in the =
hotel meeting rooms, so I'm very happy if we meet there in March and =
November. &nbsp;&nbsp;<o:p></o:p></div></div><div style=3D"font-family: =
Helvetica; font-size: medium; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div></div></div></span></blockquote></div></div=
></body></html>=

--Apple-Mail-6-919354687--

From cabo@tzi.org  Mon Aug  6 17:22:21 2012
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE36B11E80F4 for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 17:22:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.353
X-Spam-Level: 
X-Spam-Status: No, score=-106.353 tagged_above=-999 required=5 tests=[AWL=-0.104, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HzZjXiypfwWx for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 17:22:20 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id E99B011E80A5 for <ietf@ietf.org>; Mon,  6 Aug 2012 17:22:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q770MC1v008447 for <ietf@ietf.org>; Tue, 7 Aug 2012 02:22:12 +0200 (CEST)
Received: from [192.168.217.105] (p54892F18.dip.t-dialin.net [84.137.47.24]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 24964BE2; Tue,  7 Aug 2012 02:22:12 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: So, where to repeat? (was:Re: management granularity)
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com>
Date: Tue, 7 Aug 2012 02:22:04 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <29F2EDD3-71B8-4762-8753-5C7AF369001B@tzi.org>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1485)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 00:22:21 -0000

On Aug 6, 2012, at 16:41, Mary Barnes <mary.ietf.barnes@gmail.com> =
wrote:

> If we were to choose one place in the U.S. to meet, Minneapolis is the =
best choice IMHO. =20

+1 a lot.
(If we indeed have to choose the US.)
Great facility to get work done, good food, reasonable flights.

And add Prague as the staple for Europe.

Gr=FC=DFe, Carsten


From aservin@lacnic.net  Mon Aug  6 17:38:18 2012
Return-Path: <aservin@lacnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 452B221F85E7 for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 17:38:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.91
X-Spam-Level: 
X-Spam-Status: No, score=0.91 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HOST_EQ_DIALUP=0.862, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vs5eblD7aSWq for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 17:38:17 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 5C33021F85E6 for <ietf@ietf.org>; Mon,  6 Aug 2012 17:38:16 -0700 (PDT)
Received: from [192.168.1.133] (r186-48-254-36.dialup.adsl.anteldata.net.uy [186.48.254.36]) by mail.lacnic.net.uy (Postfix) with ESMTP id F331E308427; Mon,  6 Aug 2012 21:38:12 -0300 (UYT)
Subject: Re: So, where to repeat?  (was:Re: management granularity)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Arturo Servin <aservin@lacnic.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net>
Date: Mon, 6 Aug 2012 21:38:12 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <F75FF431-E9E6-4191-A292-8748BE262864@lacnic.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com><501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca><B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net>
To: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
X-Mailer: Apple Mail (2.1278)
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 00:38:18 -0000

	I do. May be you do not leave far enough from IETF venues.


Regards
as

On 6 Aug 2012, at 11:18, Dearlove, Christopher (UK) wrote:

> I've never been to an IETF meeting where the plane fare has exceeded =
the hotel cost for a week. Caveats to that are that I have mostly gone =
for IETF recommended hotels, so may have missed particularly cheap =
hotels, and that I have only been to North American and Europe (but that =
statistic includes Vancouver and the even further away western US cities =
down to San Diego). And of course I fly economy, and it's much cheaper =
including a Saturday night in your trip, even at the cost of an extra =
night in a hotel (at least it is from here). An almost exception was =
Paris this year where I was staying fairly cheaply, but that was a =
cost-shared trip between me and my employer, and I didn't fly (I went by =
train - though that's not cheaper, just better). Paris has cheap(er) =
hotels and a metro I understand, so I felt less location constrained.
>=20
> --=20
> Christopher Dearlove
> Senior Principal Engineer, Communications Group
> Communications, Networks and Image Analysis Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194 |  Fax: +44 1245 242124
> chris.dearlove@baesystems.com | http://www.baesystems.com
>=20
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace =
Centre, Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687
>=20
>=20
> -----Original Message-----
> From: Sprecher, Nurit (NSN - IL/Hod HaSharon) =
[mailto:nurit.sprecher@nsn.com]=20
> Sent: 06 August 2012 15:07
> To: Dearlove, Christopher (UK); Daniele Ceccarelli; Andrew Sullivan; =
ietf@ietf.org
> Subject: RE: So, where to repeat? (was:Re: management granularity)
>=20
> ----------------------! WARNING ! ----------------------
> This message originates from outside our organisation,
> either from an external partner or from the internet.
> Keep this in mind if you answer this message.
> Follow the 'Report Suspicious Emails' link on IT matters
> for instructions on reporting suspicious email messages.
> --------------------------------------------------------
>=20
> When you are not close (time), flight cost may become higher in the =
priority (over hotem)....
> Flying to Vancouver for me for example is the most expensive =
trip....even though the city is amazing and the host was wonderful!
>=20
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of ext Dearlove, Christopher (UK)
> Sent: Monday, August 06, 2012 4:56 PM
> To: Daniele Ceccarelli; Andrew Sullivan; ietf@ietf.org
> Subject: RE: So, where to repeat? (was:Re: management granularity)
>=20
> Dublin's problem was that the venue was isolated from the city. This =
has also been the case with e.g. San Diego. (I'm assuming no personal =
car.) Contrast with Minneapolis (and several other places) where you =
were right in the city. Being in a city is better for lunch and dinner =
options, taking a break to go to a bookshop (or to buy something you =
forgot to bring) and so on. (I'm deliberately not including tourism =
here.)
>=20
> However at the moment my priorities to make being able to attend =
possible would be time (so the closer to me the better - I realise =
that's impossible globally), cost (hotel first, flight second, rest is =
noise) and the ability to plan ahead to only attend part of the week. =
This is the current economic reality. Dublin actually scores quite well =
on those for me.
>=20
> --=20
> Christopher Dearlove
> Senior Principal Engineer, Communications Group
> Communications, Networks and Image Analysis Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194 |  Fax: +44 1245 242124
> chris.dearlove@baesystems.com | http://www.baesystems.com
>=20
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace =
Centre, Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687
>=20
>=20
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of Daniele Ceccarelli
> Sent: 06 August 2012 13:24
> To: Andrew Sullivan; ietf@ietf.org
> Subject: RE: So, where to repeat? (was:Re: management granularity)
>=20
> ----------------------! WARNING ! ----------------------
> This message originates from outside our organisation,
> either from an external partner or from the internet.
> Keep this in mind if you answer this message.
> Follow the 'Report Suspicious Emails' link on IT matters
> for instructions on reporting suspicious email messages.
> --------------------------------------------------------
>=20
> Dublin panned? I thought it was one of the best venues and locations =
of the last meetings.
>=20
> What about Italy or Spain? I've never heard about an IETF in Italy. =
I'm ok with meetings outside Italy since i like traveling very much, but =
i was wondering why it has never been taken into account in the past =
meetings. Is it expensive? I think Italy and Spain are much cheaper than =
France, UK or Sweden, aren't they?
>=20
> BR
> Daniele
>=20
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On=20
>> Behalf Of Andrew Sullivan
>> Sent: luned=EC 6 agosto 2012 14.06
>> To: ietf@ietf.org
>> Subject: So, where to repeat? (was:Re: management granularity)
>>=20
>> On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:
>>> enough merely to have excellent staff.  We need to go back to the=20
>>> better places and benefit from the learning curve.  This=20
>> doesn't mean=20
>>> "no new venues" but it means fewer.
>>=20
>> As a practical matter, may I ask about which venues you want=20
>> to return to?  I get your argument in principle, but it seems=20
>> to me that there has been quite a lot of complaining in the=20
>> past.  The one factor that seems to me most likely to reduce=20
>> complaints -- weather -- is evidently beyond the Secretariat's=20
>> or IAOC's control.
>>=20
>> People seem inclined to return to the Hyatt in Vancouver,=20
>> elevators notwithstanding.  We're going to do that.  (I don't=20
>> understand why the previous Vencouver venue was less desirable=20
>> -- to me, these venues were very similar, and not very far=20
>> apart.  I note, however, that the previous two Vancouver=20
>> visits were near the end of the year, when it rains all the=20
>> time in Vancouver.)
>>=20
>> People complained at length about the venue in Paris, so I=20
>> presume it's out.
>>=20
>> Some people complained about the hotel room prices and travel=20
>> expense in Taipei, though I heard remarks that it was a good venue.
>> Should we try to return there?
>>=20
>> People complained in advance about getting to Qu=E9bec, although=20
>> afterwards I heard lots of good noises about that venue.  I=20
>> note that the weather was great.  Should we try to return?
>>=20
>> I don't recall much complaining about the Prague venue in=20
>> 2011, which was striking to me because very little seemed=20
>> different to me compared to our first visit there.  Perhaps=20
>> this is evidence of the "tuning"
>> you suggest (ensuring the water bottles were plastic, for instance).
>> But I note the weather was excellent.
>>=20
>> Beijing?  I guess Maastricht is out. Anaheim (FWIW, I thought=20
>> that was an example of a terrible location, but many people=20
>> seemed happy with it)?  Hiroshima?  Stockholm?  San Francisco=20
>> (we thought the crime at Paris was bad, yet didn't complain=20
>> about being smack up against the Tenderloin)?  Or there's the=20
>> old standby, Minneapolis; perhaps we could do it in March. =20
>> The Dublin venue was panned by large numbers of people. =20
>> Philadelphia, people complained about expense.  Chicago, too=20
>> (combined with hotel renovations). =20
>>=20
>> That gets us back through 2007.  Which of the venues do you=20
>> think we should return to, to which we already haven't=20
>> returned or planned to return?  And why?=20
>>=20
>> For what it's worth, I would not complain about returning to=20
>> any of those venues; I personally had good meetings at all of=20
>> them except Hiroshima, which I missed due to other=20
>> commitments.  That includes both Maastricht and Dublin, which=20
>> were both apparently trials for large numbers of others.
>>=20
>> Best,
>>=20
>> A
>>=20
>> --
>> Andrew Sullivan
>> ajs@anvilwalrusden.com
>>=20
>>=20
>=20
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************
>=20


From aservin@lacnic.net  Mon Aug  6 17:42:53 2012
Return-Path: <aservin@lacnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4118221F8674 for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 17:42:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.91
X-Spam-Level: 
X-Spam-Status: No, score=0.91 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HOST_EQ_DIALUP=0.862, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ySWHPYrl7wiY for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 17:42:51 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 1CBE721F8672 for <ietf@ietf.org>; Mon,  6 Aug 2012 17:42:51 -0700 (PDT)
Received: from [192.168.1.133] (r186-48-254-36.dialup.adsl.anteldata.net.uy [186.48.254.36]) by mail.lacnic.net.uy (Postfix) with ESMTP id BBE7A308427; Mon,  6 Aug 2012 21:42:33 -0300 (UYT)
Subject: Re: So, where to repeat?  (was:Re: management granularity)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Arturo Servin <aservin@lacnic.net>
In-Reply-To: <F75FF431-E9E6-4191-A292-8748BE262864@lacnic.net>
Date: Mon, 6 Aug 2012 21:42:33 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <82E1DFF1-EE96-431F-BFE1-21A6858FCAB9@lacnic.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com><501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca><B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <F75FF431-E9E6-4191-A292-8748BE262864@lacnic.net>
To: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
X-Mailer: Apple Mail (2.1278)
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 00:42:53 -0000

	Live, not "leave".

	I have some jetlag from my almost 30 hours from Vancouver to =
Montevideo.

=3DD
as

On 6 Aug 2012, at 21:38, Arturo Servin wrote:

>=20
> 	I do. May be you do not leave far enough from IETF venues.
>=20
>=20
> Regards
> as
>=20
> On 6 Aug 2012, at 11:18, Dearlove, Christopher (UK) wrote:
>=20
>> I've never been to an IETF meeting where the plane fare has exceeded =
the hotel cost for a week. Caveats to that are that I have mostly gone =
for IETF recommended hotels, so may have missed particularly cheap =
hotels, and that I have only been to North American and Europe (but that =
statistic includes Vancouver and the even further away western US cities =
down to San Diego). And of course I fly economy, and it's much cheaper =
including a Saturday night in your trip, even at the cost of an extra =
night in a hotel (at least it is from here). An almost exception was =
Paris this year where I was staying fairly cheaply, but that was a =
cost-shared trip between me and my employer, and I didn't fly (I went by =
train - though that's not cheaper, just better). Paris has cheap(er) =
hotels and a metro I understand, so I felt less location constrained.
>>=20
>> --=20
>> Christopher Dearlove
>> Senior Principal Engineer, Communications Group
>> Communications, Networks and Image Analysis Capability
>> BAE Systems Advanced Technology Centre
>> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
>> Tel: +44 1245 242194 |  Fax: +44 1245 242124
>> chris.dearlove@baesystems.com | http://www.baesystems.com
>>=20
>> BAE Systems (Operations) Limited
>> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace =
Centre, Farnborough, Hants, GU14 6YU, UK
>> Registered in England & Wales No: 1996687
>>=20
>>=20
>> -----Original Message-----
>> From: Sprecher, Nurit (NSN - IL/Hod HaSharon) =
[mailto:nurit.sprecher@nsn.com]=20
>> Sent: 06 August 2012 15:07
>> To: Dearlove, Christopher (UK); Daniele Ceccarelli; Andrew Sullivan; =
ietf@ietf.org
>> Subject: RE: So, where to repeat? (was:Re: management granularity)
>>=20
>> ----------------------! WARNING ! ----------------------
>> This message originates from outside our organisation,
>> either from an external partner or from the internet.
>> Keep this in mind if you answer this message.
>> Follow the 'Report Suspicious Emails' link on IT matters
>> for instructions on reporting suspicious email messages.
>> --------------------------------------------------------
>>=20
>> When you are not close (time), flight cost may become higher in the =
priority (over hotem)....
>> Flying to Vancouver for me for example is the most expensive =
trip....even though the city is amazing and the host was wonderful!
>>=20
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of ext Dearlove, Christopher (UK)
>> Sent: Monday, August 06, 2012 4:56 PM
>> To: Daniele Ceccarelli; Andrew Sullivan; ietf@ietf.org
>> Subject: RE: So, where to repeat? (was:Re: management granularity)
>>=20
>> Dublin's problem was that the venue was isolated from the city. This =
has also been the case with e.g. San Diego. (I'm assuming no personal =
car.) Contrast with Minneapolis (and several other places) where you =
were right in the city. Being in a city is better for lunch and dinner =
options, taking a break to go to a bookshop (or to buy something you =
forgot to bring) and so on. (I'm deliberately not including tourism =
here.)
>>=20
>> However at the moment my priorities to make being able to attend =
possible would be time (so the closer to me the better - I realise =
that's impossible globally), cost (hotel first, flight second, rest is =
noise) and the ability to plan ahead to only attend part of the week. =
This is the current economic reality. Dublin actually scores quite well =
on those for me.
>>=20
>> --=20
>> Christopher Dearlove
>> Senior Principal Engineer, Communications Group
>> Communications, Networks and Image Analysis Capability
>> BAE Systems Advanced Technology Centre
>> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
>> Tel: +44 1245 242194 |  Fax: +44 1245 242124
>> chris.dearlove@baesystems.com | http://www.baesystems.com
>>=20
>> BAE Systems (Operations) Limited
>> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace =
Centre, Farnborough, Hants, GU14 6YU, UK
>> Registered in England & Wales No: 1996687
>>=20
>>=20
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of Daniele Ceccarelli
>> Sent: 06 August 2012 13:24
>> To: Andrew Sullivan; ietf@ietf.org
>> Subject: RE: So, where to repeat? (was:Re: management granularity)
>>=20
>> ----------------------! WARNING ! ----------------------
>> This message originates from outside our organisation,
>> either from an external partner or from the internet.
>> Keep this in mind if you answer this message.
>> Follow the 'Report Suspicious Emails' link on IT matters
>> for instructions on reporting suspicious email messages.
>> --------------------------------------------------------
>>=20
>> Dublin panned? I thought it was one of the best venues and locations =
of the last meetings.
>>=20
>> What about Italy or Spain? I've never heard about an IETF in Italy. =
I'm ok with meetings outside Italy since i like traveling very much, but =
i was wondering why it has never been taken into account in the past =
meetings. Is it expensive? I think Italy and Spain are much cheaper than =
France, UK or Sweden, aren't they?
>>=20
>> BR
>> Daniele
>>=20
>>> -----Original Message-----
>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On=20
>>> Behalf Of Andrew Sullivan
>>> Sent: luned=EC 6 agosto 2012 14.06
>>> To: ietf@ietf.org
>>> Subject: So, where to repeat? (was:Re: management granularity)
>>>=20
>>> On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:
>>>> enough merely to have excellent staff.  We need to go back to the=20=

>>>> better places and benefit from the learning curve.  This=20
>>> doesn't mean=20
>>>> "no new venues" but it means fewer.
>>>=20
>>> As a practical matter, may I ask about which venues you want=20
>>> to return to?  I get your argument in principle, but it seems=20
>>> to me that there has been quite a lot of complaining in the=20
>>> past.  The one factor that seems to me most likely to reduce=20
>>> complaints -- weather -- is evidently beyond the Secretariat's=20
>>> or IAOC's control.
>>>=20
>>> People seem inclined to return to the Hyatt in Vancouver,=20
>>> elevators notwithstanding.  We're going to do that.  (I don't=20
>>> understand why the previous Vencouver venue was less desirable=20
>>> -- to me, these venues were very similar, and not very far=20
>>> apart.  I note, however, that the previous two Vancouver=20
>>> visits were near the end of the year, when it rains all the=20
>>> time in Vancouver.)
>>>=20
>>> People complained at length about the venue in Paris, so I=20
>>> presume it's out.
>>>=20
>>> Some people complained about the hotel room prices and travel=20
>>> expense in Taipei, though I heard remarks that it was a good venue.
>>> Should we try to return there?
>>>=20
>>> People complained in advance about getting to Qu=E9bec, although=20
>>> afterwards I heard lots of good noises about that venue.  I=20
>>> note that the weather was great.  Should we try to return?
>>>=20
>>> I don't recall much complaining about the Prague venue in=20
>>> 2011, which was striking to me because very little seemed=20
>>> different to me compared to our first visit there.  Perhaps=20
>>> this is evidence of the "tuning"
>>> you suggest (ensuring the water bottles were plastic, for instance).
>>> But I note the weather was excellent.
>>>=20
>>> Beijing?  I guess Maastricht is out. Anaheim (FWIW, I thought=20
>>> that was an example of a terrible location, but many people=20
>>> seemed happy with it)?  Hiroshima?  Stockholm?  San Francisco=20
>>> (we thought the crime at Paris was bad, yet didn't complain=20
>>> about being smack up against the Tenderloin)?  Or there's the=20
>>> old standby, Minneapolis; perhaps we could do it in March. =20
>>> The Dublin venue was panned by large numbers of people. =20
>>> Philadelphia, people complained about expense.  Chicago, too=20
>>> (combined with hotel renovations). =20
>>>=20
>>> That gets us back through 2007.  Which of the venues do you=20
>>> think we should return to, to which we already haven't=20
>>> returned or planned to return?  And why?=20
>>>=20
>>> For what it's worth, I would not complain about returning to=20
>>> any of those venues; I personally had good meetings at all of=20
>>> them except Hiroshima, which I missed due to other=20
>>> commitments.  That includes both Maastricht and Dublin, which=20
>>> were both apparently trials for large numbers of others.
>>>=20
>>> Best,
>>>=20
>>> A
>>>=20
>>> --
>>> Andrew Sullivan
>>> ajs@anvilwalrusden.com
>>>=20
>>>=20
>>=20
>> ********************************************************************
>> This email and any attachments are confidential to the intended
>> recipient and may also be privileged. If you are not the intended
>> recipient please delete it from your system and notify the sender.
>> You should not copy it or use it for any purpose nor disclose or
>> distribute its contents to any other person.
>> ********************************************************************
>>=20


From johnl@iecc.com  Mon Aug  6 18:10:10 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC64A21F86BD for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 18:10:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.156
X-Spam-Level: 
X-Spam-Status: No, score=-111.156 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HJCN70YZXhXe for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 18:10:10 -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 BDF8221F8565 for <ietf@ietf.org>; Mon,  6 Aug 2012 18:10:09 -0700 (PDT)
Received: (qmail 49062 invoked from network); 7 Aug 2012 01:10:07 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 7 Aug 2012 01:10:07 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50206aef.xn--yuvv84g.k1208; i=johnl@user.iecc.com; bh=FEz5avuCvMhRp7ghB5NT7gI7F1ajw1aVHdJNeitAM74=; b=goD8SwAU7GAKJ3VXSwX6drCrh39O0EKG3URVL3vZGlDNU9gUrf7EA8+T+reOA8wmzEBHm/TTjjhFv0lmtQtIgl8KQQZgXZpPWOf2YW8/WX7B5iccXvZZBcbiIRKQ+CF6eotCU/KJu+PDOO8Of0oduEsFCfVkSRvd+d3IdFVnEUs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50206aef.xn--yuvv84g.k1208; olt=johnl@user.iecc.com; bh=FEz5avuCvMhRp7ghB5NT7gI7F1ajw1aVHdJNeitAM74=; b=IyepihfAfEMkZtDMblVQDN/XUgooMlHveHnAxm6nKUHykfE5W/+x/Pos6uChNdLd1VWMbIUqQLexwnM/eG90LRCgcUhCsPc/eBB1/+3A2wExER3w+1Y4iwJLFpj1wwkVQ3Q8s/WhtJprdrQLpoHUtsfW56RX/FeTvAcFrcdW4dw=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 7 Aug 2012 01:09:45 -0000
Message-ID: <20120807010945.51851.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: So, where to repeat? (was: Re: management granularity)
In-Reply-To: <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 01:10:11 -0000

>Flights to Vancouver from some cities were extremely expensive.  It would
>have cost me more than twice as much as it did to fly to Beijing, for
>example, if I had taken a direct flight from DFW - it would have been by
>far my most expensive IETF airfare ever.

That's very odd.  I see lots of fares from DFW to YVR from Saturday to
Saturday via Houston or Denver for in upcoming weeks for under $550,
and nonstops for $678.  (If you can get to Beijing for that price, I'd
sure like to hear about it.)

Did you perhaps wait until the last minute to buy your tickets, or have
company rules that require flying on airlines without competitive prices
to Canada?

Flying to Canada is certainly more expensive than flying within the
US, but it's not that much more expensive.  I thought the hotel and
food were all quite reasonable, but it does help that I get the HST
back.

R's,
John

From mary.ietf.barnes@gmail.com  Mon Aug  6 21:34:01 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF78121F86AB for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 21:34:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.528
X-Spam-Level: 
X-Spam-Status: No, score=-103.528 tagged_above=-999 required=5 tests=[AWL=0.070, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UNp5vBW+SwnX for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 21:33:59 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9B5F921F86A7 for <ietf@ietf.org>; Mon,  6 Aug 2012 21:33:58 -0700 (PDT)
Received: by lahm15 with SMTP id m15so2030394lah.31 for <ietf@ietf.org>; Mon, 06 Aug 2012 21:33:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=q1O7WK1d1+O31Ov6W0KQKrFcBFaecl9tY16TezwwpbI=; b=r32sDhkYu39cSrXzs2l+AkIUIjjMNH5cMxwg5pBj/U1KnQOEOVun+MZAtTcGYleJx4 /9q5sgGPbSAS0Zyd4MsLigBnLUZbd1+znZQapHjUtLbGDgL0+KBkn/d8qj9jhWDhev1d B9pi85toydWYULh5CRca+A4vc0gmvXeJGym3akhn8NsG/eId2aN2eYVFsRBcDGkG315x SVJiPqpZx284uVjdqou79EIoEVh6g704r7F/z1Lj7m4m/Dw5p4vFHhwwgfsdSLxh/Qgo qTzAl2MfSkszFk9ijGQ2fIa9TVWwxfIEXzUE67WDCUnw04w3b2WtYa3D1fD60kHkpM9p NiRA==
MIME-Version: 1.0
Received: by 10.112.99.98 with SMTP id ep2mr5790104lbb.45.1344314034718; Mon, 06 Aug 2012 21:33:54 -0700 (PDT)
Received: by 10.112.85.196 with HTTP; Mon, 6 Aug 2012 21:33:54 -0700 (PDT)
In-Reply-To: <20120807010945.51851.qmail@joyce.lan>
References: <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <20120807010945.51851.qmail@joyce.lan>
Date: Mon, 6 Aug 2012 23:33:54 -0500
Message-ID: <CAHBDyN4R7sMBM+tmUcmaYYRV-PQC7eTgomWN=G-PYShkO4N6Aw@mail.gmail.com>
Subject: Re: So, where to repeat? (was: Re: management granularity)
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: John Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary=f46d0401fde1818a2c04c6a580e5
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 04:34:01 -0000

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

The thing is that I don't need a flight to DFW to YVR for this coming week
and I don't see the prices you do either.  I did not buy my tickets at the
last minute and believe it or not, I'm actually not lying about what I paid
for my tickets to YVR nor to Beijing.   I made a very simple statement of
fact based on my own experiences.  I can't fathom why you felt obligated to
spend time trying to show that I was lying.

Mary.

On Mon, Aug 6, 2012 at 8:09 PM, John Levine <johnl@taugh.com> wrote:

> >Flights to Vancouver from some cities were extremely expensive.  It would
> >have cost me more than twice as much as it did to fly to Beijing, for
> >example, if I had taken a direct flight from DFW - it would have been by
> >far my most expensive IETF airfare ever.
>
> That's very odd.  I see lots of fares from DFW to YVR from Saturday to
> Saturday via Houston or Denver for in upcoming weeks for under $550,
> and nonstops for $678.  (If you can get to Beijing for that price, I'd
> sure like to hear about it.)
>
> Did you perhaps wait until the last minute to buy your tickets, or have
> company rules that require flying on airlines without competitive prices
> to Canada?
>
> Flying to Canada is certainly more expensive than flying within the
> US, but it's not that much more expensive.  I thought the hotel and
> food were all quite reasonable, but it does help that I get the HST
> back.
>
> R's,
> John
>

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

The thing is that I don&#39;t need a flight to DFW to YVR for this coming w=
eek and I don&#39;t see the prices you do either. =A0I did not buy my ticke=
ts at the last minute and believe it or not, I&#39;m actually not lying abo=
ut what I paid for my tickets to YVR nor to Beijing. =A0 I made a very simp=
le statement of fact based on my own experiences. =A0I can&#39;t fathom why=
 you felt obligated to spend time trying to show that I was lying. =A0=A0<d=
iv>
<br></div><div>Mary.=A0<br><br><div class=3D"gmail_quote">On Mon, Aug 6, 20=
12 at 8:09 PM, John Levine <span dir=3D"ltr">&lt;<a href=3D"mailto:johnl@ta=
ugh.com" target=3D"_blank">johnl@taugh.com</a>&gt;</span> wrote:<br><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">

&gt;Flights to Vancouver from some cities were extremely expensive. =A0It w=
ould<br>
&gt;have cost me more than twice as much as it did to fly to Beijing, for<b=
r>
&gt;example, if I had taken a direct flight from DFW - it would have been b=
y<br>
&gt;far my most expensive IETF airfare ever.<br>
<br>
That&#39;s very odd. =A0I see lots of fares from DFW to YVR from Saturday t=
o<br>
Saturday via Houston or Denver for in upcoming weeks for under $550,<br>
and nonstops for $678. =A0(If you can get to Beijing for that price, I&#39;=
d<br>
sure like to hear about it.)<br>
<br>
Did you perhaps wait until the last minute to buy your tickets, or have<br>
company rules that require flying on airlines without competitive prices<br=
>
to Canada?<br>
<br>
Flying to Canada is certainly more expensive than flying within the<br>
US, but it&#39;s not that much more expensive. =A0I thought the hotel and<b=
r>
food were all quite reasonable, but it does help that I get the HST<br>
back.<br>
<br>
R&#39;s,<br>
John<br>
</blockquote></div><br>
</div>

--f46d0401fde1818a2c04c6a580e5--

From johnl@taugh.com  Mon Aug  6 21:41:48 2012
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34A4311E8087 for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 21:41:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.591
X-Spam-Level: 
X-Spam-Status: No, score=-2.591 tagged_above=-999 required=5 tests=[AWL=0.009,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0V528Sn5tzm9 for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 21:41:46 -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 2199C11E80E8 for <ietf@ietf.org>; Mon,  6 Aug 2012 21:41:38 -0700 (PDT)
Received: (qmail 85072 invoked from network); 7 Aug 2012 04:41:38 -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=14c4f.50209c82.k1208; bh=QzTqyyHHeWg9mtoUKc4ikbBfwsWGavObhJivTwcKw/M=; b=ozaT+WPBPiNMbQRKzlKKaKvTFD6t7taMOoTMQ4FN8Z7xPvqG62esvZYw+7CXCtH68jHEh5IG9QgbyLdae2h2WwQjmMHnd65mg2h9XBDu9MPMedCxF5eoleu2HbtgEEJx3nfCk3aHXfll7iWpR+vJOeItlxmZHc4C3IB4WfT2d/s=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=14c4f.50209c82.k1208; bh=QzTqyyHHeWg9mtoUKc4ikbBfwsWGavObhJivTwcKw/M=; b=oaID4fkOfrFIeGt7NLo+w9jc4V9GpFGm+QfplTserH1gbvnnBGWt7O70vZOjjiJNchfCqwEuFi9zKVhhvN5pxSPOF4S7OYFoEYtnLIXH1X79Llrv1csK3M9haOAvVpJDjg29dSkPga7Qxm4JbWOJmmQXppg9o13KmChqTWNIko8=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 7 Aug 2012 04:41:15 -0000
Date: 7 Aug 2012 00:41:37 -0400
Message-ID: <alpine.BSF.2.00.1208070038400.99336@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Mary Barnes" <mary.ietf.barnes@gmail.com>
Subject: Re: So, where to repeat? (was: Re: management granularity)
In-Reply-To: <CAHBDyN4R7sMBM+tmUcmaYYRV-PQC7eTgomWN=G-PYShkO4N6Aw@mail.gmail.com>
References: <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <20120807010945.51851.qmail@joyce.lan> <CAHBDyN4R7sMBM+tmUcmaYYRV-PQC7eTgomWN=G-PYShkO4N6Aw@mail.gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 04:41:48 -0000

> The thing is that I don't need a flight to DFW to YVR for this coming week
> and I don't see the prices you do either.  I did not buy my tickets at the
> last minute and believe it or not, I'm actually not lying about what I paid
> for my tickets to YVR nor to Beijing.   I made a very simple statement of
> fact based on my own experiences.  I can't fathom why you felt obligated to
> spend time trying to show that I was lying.

Sigh.  If you'll review my previous messages, you'll note that I never 
said you were lying.  Is there some reason that it's important to put 
words in people's mouths?

But since non-stop tickets from Dallas to Vancouver are easily available
for prices far below any plausible price for a ticket to China via aa.com
and the usual travel agents, something peculiar was evidently going on
when you bought yours.

R's,
John

From mary.ietf.barnes@gmail.com  Mon Aug  6 22:00:39 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FA9821F860B for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 22:00:39 -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=0.069, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3IK6hFE1TAFv for <ietf@ietfa.amsl.com>; Mon,  6 Aug 2012 22:00:38 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id EF5AD21F8609 for <ietf@ietf.org>; Mon,  6 Aug 2012 22:00:37 -0700 (PDT)
Received: by lbbgg6 with SMTP id gg6so851529lbb.31 for <ietf@ietf.org>; Mon, 06 Aug 2012 22:00:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=m/X6cAZK6Q1fSZfk2kCELH54UWAvqiyW/7TNyyuBQlc=; b=l22UI/81AlDrIPavbkCMkfPC8IwcRTk0dMRXn4jDkDck33HhDNdEWiCFZXpODopNiw g04GzgHyscfLHnyGRKFtLFvkA3Y/zJCYHaz/aqlt0JmmbkB4knfhhpbtkpeSIkltP+/9 IlK6nvef66x1td0epccpi4WM+bhiNLc5KdGD2vHJbKn8OO+5e0wLKlxRcK1m2bjPKPuX kH6ehS2ZgskG0f/MMoK+NmxU34VXwu9yGP5XWlEbUUn8u6zoX6l8iToktWIydHa33ONM ubPnULch1Wbz/4cVWlcZ1uiwJRt4/BAh1MLLNulzRCF3vZXf68h/ugskD5xaueR2m1F8 Uelg==
MIME-Version: 1.0
Received: by 10.152.103.109 with SMTP id fv13mr13046033lab.33.1344315636783; Mon, 06 Aug 2012 22:00:36 -0700 (PDT)
Received: by 10.112.85.196 with HTTP; Mon, 6 Aug 2012 22:00:36 -0700 (PDT)
In-Reply-To: <alpine.BSF.2.00.1208070038400.99336@joyce.lan>
References: <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <20120807010945.51851.qmail@joyce.lan> <CAHBDyN4R7sMBM+tmUcmaYYRV-PQC7eTgomWN=G-PYShkO4N6Aw@mail.gmail.com> <alpine.BSF.2.00.1208070038400.99336@joyce.lan>
Date: Tue, 7 Aug 2012 00:00:36 -0500
Message-ID: <CAHBDyN6r-BV1vNP2J3gGAfHcynsirt366H2V+_2zktE_PpfCiw@mail.gmail.com>
Subject: Re: So, where to repeat? (was: Re: management granularity)
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: John R Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary=f46d040890c7ff189d04c6a5df3c
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 05:00:40 -0000

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

On Mon, Aug 6, 2012 at 11:41 PM, John R Levine <johnl@taugh.com> wrote:

> The thing is that I don't need a flight to DFW to YVR for this coming week
>> and I don't see the prices you do either.  I did not buy my tickets at the
>> last minute and believe it or not, I'm actually not lying about what I
>> paid
>> for my tickets to YVR nor to Beijing.   I made a very simple statement of
>> fact based on my own experiences.  I can't fathom why you felt obligated
>> to
>> spend time trying to show that I was lying.
>>
>
> Sigh.  If you'll review my previous messages, you'll note that I never
> said you were lying.  Is there some reason that it's important to put words
> in people's mouths?
>
> But since non-stop tickets from Dallas to Vancouver are easily available
> for prices far below any plausible price for a ticket to China via aa.com
> and the usual travel agents, something peculiar was evidently going on
> when you bought yours.
>
> [MB] I paid around $962.10 for my ticket to Beijing when we had the IETF
there in Nov 2010.   So, no, there was nothing peculiar except that a
direct flight from DFW to YVR was over $2000 when I was making
reservations.  My indirect flight was $1156.23.   Certainly, if you look
for flights to YVR in a couple weeks, the prices less.  That's because kids
are back in school.  [/MB]

[MB] No - you did not use the noun "liar" or the verb "lying", but when you
tell someone that what they are saying can't possibly be true, that has the
same implication. [/MB]


> R's,
> John
>

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

<br><br><div class=3D"gmail_quote">On Mon, Aug 6, 2012 at 11:41 PM, John R =
Levine <span dir=3D"ltr">&lt;<a href=3D"mailto:johnl@taugh.com" target=3D"_=
blank">johnl@taugh.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The thing is that I don&#39;t need a flight to DFW to YVR for this coming w=
eek<br>
and I don&#39;t see the prices you do either. =A0I did not buy my tickets a=
t the<br>
last minute and believe it or not, I&#39;m actually not lying about what I =
paid<br>
for my tickets to YVR nor to Beijing. =A0 I made a very simple statement of=
<br>
fact based on my own experiences. =A0I can&#39;t fathom why you felt obliga=
ted to<br>
spend time trying to show that I was lying.<br>
</blockquote>
<br>
Sigh. =A0If you&#39;ll review my previous messages, you&#39;ll note that I =
never said you were lying. =A0Is there some reason that it&#39;s important =
to put words in people&#39;s mouths?<br>
<br>
But since non-stop tickets from Dallas to Vancouver are easily available<br=
>
for prices far below any plausible price for a ticket to China via <a href=
=3D"http://aa.com" target=3D"_blank">aa.com</a><br>
and the usual travel agents, something peculiar was evidently going on<br>
when you bought yours.<br>
<br></blockquote><div>[MB] I paid around $962.10 for my ticket to Beijing w=
hen we had the IETF there in Nov 2010. =A0 So, no, there was nothing peculi=
ar except that a direct flight from DFW to YVR was over $2000 when I was ma=
king reservations. =A0My indirect flight was $1156.23. =A0 Certainly, if yo=
u look for flights to YVR in a couple weeks, the prices less. =A0That&#39;s=
 because kids are back in school. =A0[/MB]</div>
<div><br></div><div>[MB] No - you did not use the noun &quot;liar&quot; or =
the verb &quot;lying&quot;, but when you tell someone that what they are sa=
ying can&#39;t possibly be true, that has the same implication. [/MB] =A0</=
div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
R&#39;s,<br>
John<br>
</blockquote></div><br>

--f46d040890c7ff189d04c6a5df3c--

From brian.e.carpenter@gmail.com  Tue Aug  7 00:09:48 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FA0121F8567 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 00:09:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.474
X-Spam-Level: 
X-Spam-Status: No, score=-101.474 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nhsLuV3b5raG for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 00:09:47 -0700 (PDT)
Received: from mail-wg0-f42.google.com (mail-wg0-f42.google.com [74.125.82.42]) by ietfa.amsl.com (Postfix) with ESMTP id 3F7E221F8565 for <ietf@ietf.org>; Tue,  7 Aug 2012 00:09:47 -0700 (PDT)
Received: by wgbfm10 with SMTP id fm10so2136256wgb.1 for <ietf@ietf.org>; Tue, 07 Aug 2012 00:09:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=8Qbt2jJoWtktOtWhyrpCVCLEVbyeNZ4EmzfD0HJQUYc=; b=1A+JOB5bfG1Zw6OhHy3hDJqESBnrwMLXH1XYvjo3gwLWvJgX2qdH9WNiW2yx41Pjjx p9IHYSdik1D7WbGxTKQEOeDdheAkQmWBhnRASoRH/Xmctpa3IsqYiri0kUNHGQgZy2DD YGAp++YHu9nKTxSMRpOsfNyGzNxGFBmqHfo8YvYiGPpTJmn97if10vUsZY0Ils280OzV /t3JEvvWb/a1B5cPjzgFtPKXjimhUFAKNG66UX3ntHzM2mLUmIG9XkujMZivjg6FxfwV D3XTzTs0W4DI8Z6Duepu5OwNOHPu1bn2EJXie1d1N+E2fxcMsoJSjrqRsJ6QBuKS9RM9 lm8w==
Received: by 10.217.2.197 with SMTP id p47mr6590903wes.55.1344323386299; Tue, 07 Aug 2012 00:09:46 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-145.as13285.net. [2.102.216.145]) by mx.google.com with ESMTPS id l6sm19846194wiz.4.2012.08.07.00.09.44 (version=SSLv3 cipher=OTHER); Tue, 07 Aug 2012 00:09:45 -0700 (PDT)
Message-ID: <5020BF3A.2080903@gmail.com>
Date: Tue, 07 Aug 2012 08:09:46 +0100
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: ITU-T Dubai Meeting
References: <20120806220208.D443E1A126@ld9781.wdf.sap.corp>
In-Reply-To: <20120806220208.D443E1A126@ld9781.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: Tue, 07 Aug 2012 07:09:48 -0000

On 06/08/2012 23:02, Martin Rex wrote:
> Steven Bellovin wrote:
>> Randy Bush wrote:
>>> whatever the number of address bits, if it is fixed, we always run out.
>>> memory addressing has been a cliff many times.  ip addressing.  ...
>> Yup.  To quote Fred Brooks on memory address space: "Every successful
>> computer architecture eventually runs out of address space" -- and I heard
>> him say that in 1973.
> 
> I'm wondering what resource shortage would have happened if IPv6
> had been massively adopted 10 years earlier, and whether we would have
> seen the internet backbone routers suffer severely from the size
> of the routing tables, if every single home customer (DSL subscriber)
> would have required a provider-independent IPv6 network prefix rather
> than a single, provider-dependent IPv4 IP Address.

That was never a likely scenario (and still isn't). PA prefixes are still
the norm for mass-market IP, regardless of version number.

     Brian

From mohta@necom830.hpcl.titech.ac.jp  Tue Aug  7 00:27:24 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5732321F85F3 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 00:27:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.043
X-Spam-Level: 
X-Spam-Status: No, score=-0.043 tagged_above=-999 required=5 tests=[AWL=0.047,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C-Ll3l1nakzl for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 00:27:23 -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 396D821F85D8 for <ietf@ietf.org>; Tue,  7 Aug 2012 00:27:20 -0700 (PDT)
Received: (qmail 72827 invoked from network); 7 Aug 2012 07:36: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; 7 Aug 2012 07:36:52 -0000
Message-ID: <5020C32A.4060907@necom830.hpcl.titech.ac.jp>
Date: Tue, 07 Aug 2012 16:26:34 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FE2715C.2090601@necom830.hpcl.titech.ac.jp> <4FF20DE7.2080208@isi.edu> <500654AB.7060500@necom830.hpcl.titech.ac.jp> <8F5CBE79-4540-4519-9F51-62B36686EE8C@isi.edu> <501C5C75.9040209@necom830.hpcl.titech.ac.jp> <501C6441.4000302@isi.edu>
In-Reply-To: <501C6441.4000302@isi.edu>
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: Tue, 07 Aug 2012 07:27:24 -0000

Joe Touch wrote:

>> RFC2765 specifies that translators can merely copy the
>> low-order bits of the field.
> 
> Yes, but this is not compatible with RFC791.

Then, which should we revice? RFC791, RFC2765 or both?

Without such a decision, there is no point to publish something
based on RFC791 and is not compatible with RFC2765.

> The case above occurs only when the source gets back a "packet too big"
> message with a desired MTU less than 1280.

which means RFC2460 expects it.

> Note that this might never
> happen, in which case there would never be any Fragment header.

If you can assume so, let's better assume that accidental ID
match never happen and we all can be very happy.

> However, even when it does happen, there is no instruction above about
> how to construct the header that is compliant with RFC791.

That is the problem. That is, if you insist on RFC791 as is, not
enough is specified on how to generate IPv6 ID.

> Further, the source might already be inserting the fragmentation header
> (e.g., on a 2KB packet).

Thus, there can be only one way (the one in RFC2765) to map IPv6
ID to IPv4 ID

Or, if multiple IPv6 fragments with same ID use different IPv4
translators with different mapping algorithm, each IPv6
fragments will have different IPv4 IDs.

> There's no instruction in how fragment headers
> are constructed in general that complies with RFC791.

Is it a problem of RFC791 or RFC2460/2765?

> Simply using the low 16 bits is not correct. In particular, RFC2460
> suggests that its 32-bit counter can wrap once a minute, and that only
> one such counter might be needed for an endpoint for all connections.

Never mind.

IPv6 specification is not self consistent at all.

>> Or, are you saying RFC2460 and RFC2765 violate RFC791?
> 
> Yes.

Then, as fixing RFC2460 is politically impossible, we must
abandone IPv6 and live with IPv4 forever.

> This document updates RFC791, but does not fix either RFC2460 or
> RFC2765. This document does not make any statements about how IPv6
> generates its IDs.

You draft says:

   This document updates the specification of the IPv4 ID field to more
   closely reflect current practice, and to include considerations taken
   into account during the specification of the similar field in IPv6.

but, "the specification of the similar field in IPv6" is, in
your opinion, incomplete, let's finish it first, only after
which you can revise your draft "to include considerations
taken into account during the specification of the similar
field in IPv6."

More specifically, for example, the following statement in your draft:

   The latter case is relevant only for
   IPv6 datagrams sent to IPv4 destinations to support subsequent
   fragmentation after translation to IPv4.

is incorrect because NAT646 refer RFC2765.

For another example,

   Finally, the IPv6 ID field is
   32 bits, and required unique per source/destination address pair for
   IPv6,

is, in your opinion, violation of RFC791.

>> As I stated above, RFC2460 guarantees "a suitable Identification
>> value" for IPv4 ID is there in IPv6 fragmentation ID.
> 
> Not the way I interpret the text, especially because there are other
> ways to generate IDs in RFC2460 that could be translated to IPv4

As I stated above, there can be only one way common to all the
6->4 translators. Or, different fragments with an IPv6 ID will
have different IPv4 IDs.

>> Or, if you think RFC2460 does not mind ID uniqueness (of IPv4,
>> at least) so much, RFC791 should not either.
> 
> I think there are a lot of IETF documents that are not reviewed in the
> correct context of existing standards. I don't think that applies to
> this draft, though.

So, you are lucky that I have noticed the problem at the last call.

						Masataka Ohta


From mrex@sap.com  Tue Aug  7 00:46:11 2012
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 6ACC121F8549 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 00:46:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.146
X-Spam-Level: 
X-Spam-Status: No, score=-10.146 tagged_above=-999 required=5 tests=[AWL=0.103, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PmrnhRocl0A1 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 00:46:10 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 7663A21F853F for <ietf@ietf.org>; Tue,  7 Aug 2012 00:46:10 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q777k16N009426 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Aug 2012 09:46:01 +0200 (MEST)
Subject: Re: ITU-T Dubai Meeting
In-Reply-To: <5020BF3A.2080903@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Tue, 7 Aug 2012 09:46:01 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20120807074601.23F871A125@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
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, 07 Aug 2012 07:46:11 -0000

Brian E Carpenter wrote:
[ Charset UTF-8 unsupported, converting... ]
> On 06/08/2012 23:02, Martin Rex wrote:
> > Steven Bellovin wrote:
> >> Randy Bush wrote:
> >>> whatever the number of address bits, if it is fixed, we always run out.
> >>> memory addressing has been a cliff many times.  ip addressing.  ...
> >> Yup.  To quote Fred Brooks on memory address space: "Every successful
> >> computer architecture eventually runs out of address space" -- and I heard
> >> him say that in 1973.
> > 
> > I'm wondering what resource shortage would have happened if IPv6
> > had been massively adopted 10 years earlier, and whether we would have
> > seen the internet backbone routers suffer severely from the size
> > of the routing tables, if every single home customer (DSL subscriber)
> > would have required a provider-independent IPv6 network prefix rather
> > than a single, provider-dependent IPv4 IP Address.
> 
> That was never a likely scenario (and still isn't). PA prefixes are still
> the norm for mass-market IP, regardless of version number.


IPv6 PA prefixes result in that awkward renumbering.
Avoiding the renumbering implies provider independent
network prefix.

With IPv4, you would have typically keept your IPv4 network address
(the old class A, B & C from early 199x) even when changing network
providers.


To me, IPv6 PA prefixes look like a pretty useless feature
(from the customer perspective).  Either you want an provider-independent
prefix to avoid the renumbering when changing providers,
or you want some level of privacy protection and therefore
a fully dynamic temporary DHCP-assigned IPv6 address
(same network prefix for 10000+ customers of the ISP)
and for use with NAT (again to avoid the renumbering).

IPv6 renumbering creates huge complexity without value (for the customer).

-Martin

From brian.e.carpenter@gmail.com  Tue Aug  7 01:20:12 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CCC121F8587 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 01:20:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.476
X-Spam-Level: 
X-Spam-Status: No, score=-101.476 tagged_above=-999 required=5 tests=[AWL=0.215, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LohelqqloI3o for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 01:20:11 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 012E821F866A for <ietf@ietf.org>; Tue,  7 Aug 2012 01:20:10 -0700 (PDT)
Received: by eekb45 with SMTP id b45so1011376eek.31 for <ietf@ietf.org>; Tue, 07 Aug 2012 01:20:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Bq5Y8h72GHCMAAUACDVXi4dcMWhAnyzBeyh9TC5rB0Y=; b=P7mARCUOKhXIGNZ8y/+UvcD9+iOyHGc3yyLi3j+/R83j192KCMH8mrvuu595YCWJ4y 8U0xJoVj6DvUi6RGJvYvd4oA5BrvPIuJkCvVZfgN0WZ2vAyMo5asGKPlpMOWs01FeUC6 3+CEGc4CVQhTdYZ3qcx3WjpVTwJpnkkNNe9sllHlzCr7htiCv1lo4JfdjVVNcucfFFtz JEZf530ZrTLoEFgVmhXiQwA0OkFZGYsqlUO6PCl79gtedvQm7yrJsDaEvwzbWR54dFfW CacXIil5C8j3360+CF0tGX/izdn4/O1eW9nHQi1m+XmL0ZcMIpQrTvrlFM/UqxQOQ8YG HyYg==
Received: by 10.14.214.196 with SMTP id c44mr16774472eep.7.1344327610151; Tue, 07 Aug 2012 01:20:10 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-145.as13285.net. [2.102.216.145]) by mx.google.com with ESMTPS id j4sm53930127eeo.11.2012.08.07.01.20.08 (version=SSLv3 cipher=OTHER); Tue, 07 Aug 2012 01:20:09 -0700 (PDT)
Message-ID: <5020CFB9.7090402@gmail.com>
Date: Tue, 07 Aug 2012 09:20:09 +0100
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: ITU-T Dubai Meeting
References: <20120807074601.23F871A125@ld9781.wdf.sap.corp>
In-Reply-To: <20120807074601.23F871A125@ld9781.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: Tue, 07 Aug 2012 08:20:12 -0000

Martin,

As far as the mass market goes, multiple prefixes and renumbering are a fact of life.
See the MIF and HOMENET WGs for more.

As far as enterprise networks go, renumbering is rather undesirable but sometimes
inevitable, see 6RENUM.

Regards
   Brian

On 07/08/2012 08:46, Martin Rex wrote:
> Brian E Carpenter wrote:
> [ Charset UTF-8 unsupported, converting... ]
>> On 06/08/2012 23:02, Martin Rex wrote:
>>> Steven Bellovin wrote:
>>>> Randy Bush wrote:
>>>>> whatever the number of address bits, if it is fixed, we always run out.
>>>>> memory addressing has been a cliff many times.  ip addressing.  ...
>>>> Yup.  To quote Fred Brooks on memory address space: "Every successful
>>>> computer architecture eventually runs out of address space" -- and I heard
>>>> him say that in 1973.
>>> I'm wondering what resource shortage would have happened if IPv6
>>> had been massively adopted 10 years earlier, and whether we would have
>>> seen the internet backbone routers suffer severely from the size
>>> of the routing tables, if every single home customer (DSL subscriber)
>>> would have required a provider-independent IPv6 network prefix rather
>>> than a single, provider-dependent IPv4 IP Address.
>> That was never a likely scenario (and still isn't). PA prefixes are still
>> the norm for mass-market IP, regardless of version number.
> 
> 
> IPv6 PA prefixes result in that awkward renumbering.
> Avoiding the renumbering implies provider independent
> network prefix.
> 
> With IPv4, you would have typically keept your IPv4 network address
> (the old class A, B & C from early 199x) even when changing network
> providers.
> 
> 
> To me, IPv6 PA prefixes look like a pretty useless feature
> (from the customer perspective).  Either you want an provider-independent
> prefix to avoid the renumbering when changing providers,
> or you want some level of privacy protection and therefore
> a fully dynamic temporary DHCP-assigned IPv6 address
> (same network prefix for 10000+ customers of the ISP)
> and for use with NAT (again to avoid the renumbering).
> 
> IPv6 renumbering creates huge complexity without value (for the customer).
> 
> -Martin
> 

From daedulus@btconnect.com  Tue Aug  7 01:33:46 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E031E21F85C5 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 01:33:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.916
X-Spam-Level: 
X-Spam-Status: No, score=-2.916 tagged_above=-999 required=5 tests=[AWL=-0.806, BAYES_05=-1.11, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vnmbanymH7uD for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 01:33:46 -0700 (PDT)
Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe004.messaging.microsoft.com [213.199.154.142]) by ietfa.amsl.com (Postfix) with ESMTP id 9608721F85A5 for <ietf@ietf.org>; Tue,  7 Aug 2012 01:33:44 -0700 (PDT)
Received: from mail114-db3-R.bigfish.com (10.3.81.227) by DB3EHSOBE006.bigfish.com (10.3.84.26) with Microsoft SMTP Server id 14.1.225.23; Tue, 7 Aug 2012 08:33:43 +0000
Received: from mail114-db3 (localhost [127.0.0.1])	by mail114-db3-R.bigfish.com (Postfix) with ESMTP id BDF734E009D; Tue,  7 Aug 2012 08:33:43 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.224.141; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0702HT005.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -24
X-BigFish: PS-24(zz98dI9371Ic89bh542M1432Izz1202hzz1033IL8275dhz2dh2a8h5a9h668h839h93fhd24hf0ah107ah304l)
Received: from mail114-db3 (localhost.localdomain [127.0.0.1]) by mail114-db3 (MessageSwitch) id 1344328422595082_3451; Tue,  7 Aug 2012 08:33:42 +0000 (UTC)
Received: from DB3EHSMHS007.bigfish.com (unknown [10.3.81.240])	by mail114-db3.bigfish.com (Postfix) with ESMTP id 8D8902E00A5; Tue,  7 Aug 2012 08:33:42 +0000 (UTC)
Received: from DB3PRD0702HT005.eurprd07.prod.outlook.com (157.55.224.141) by DB3EHSMHS007.bigfish.com (10.3.87.107) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 7 Aug 2012 08:33:41 +0000
Received: from DBXPRD0510HT004.eurprd05.prod.outlook.com (157.56.252.165) by pod51017.outlook.com (10.3.4.160) with Microsoft SMTP Server (TLS) id 14.15.108.4; Tue, 7 Aug 2012 08:33:41 +0000
Message-ID: <009101cd7476$bb522c20$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Alessandro Vesely <vesely@tana.it>, <ietf@ietf.org>
References: <CALaySJKV96tdXhzfPD1e1Mro_+gp5aDarF7Z06QrA+iQtnHkLw@mail.gmail.com><501A5656.2050407@it.aoyama.ac.jp> <501BEC0D.1060404@tana.it>
Subject: Re: RFC Errata: when to file, and when not to
Date: Tue, 7 Aug 2012 09:29:00 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.252.165]
Content-Transfer-Encoding: quoted-printable
X-OriginatorOrg: btconnect.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 08:33:47 -0000

---- Original Message -----
From: "Alessandro Vesely" <vesely@tana.it>
To: <ietf@ietf.org>
Sent: Friday, August 03, 2012 4:19 PM
On Thu 02/Aug/2012 03:28:38 -0700 Martin J. D=C3=BCrst wrote:
>
>> In particular, the errata system is NOT meant to be used as an issue
>> tracker;
>
> Of course we have mailing lists, issue trackers, and wikis, but the
> problem is that none of them are for RFCs.

In addition, those tools seem to be intended rather for IETF internal
use than for general public.

> The question then comes up on whether we can do better. And my guess
> is that in this day and age of linked information, we should be able
> to do better. With the tools version of an RFC, which is quickly
> becoming the preferred version of many, it's already easy to find
errata.

It is /not difficult/ to find errata.  "Easy" would mean that people
usually find them even if they're not purposely looking for them.  For
example, the existence of an approved errata could be signaled by
coloring the margin near the relevant text.

<tp>
When I Google RFCnnnn, I am sometimes directed to www.ietf.org, which is
not much help here. Other times, I am directed to tools.ietf.org, whose
format I find less friendly but which does have 'errata exist' in the
top right hand corner.  However, I cannot click on that, unlike the
Obsoletes and Updates fields; but, more importantly, would your average
not-involved-in-standards audience know what errata are?  For me, the
word comes from a classical education, before ever I got involved with
standards, and so is a commonplace, but is it used in the world at
large?  I suspect not.

Tom Petch
</tp>



From ynir@checkpoint.com  Tue Aug  7 03:58:27 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 119F221F84F4 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 03:58:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.361
X-Spam-Level: 
X-Spam-Status: No, score=-10.361 tagged_above=-999 required=5 tests=[AWL=0.238, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gAMcTBjSJPEA for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 03:58:26 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id DE72121F8510 for <ietf@ietf.org>; Tue,  7 Aug 2012 03:58:25 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id q77AwKV3016559; Tue, 7 Aug 2012 13:58:20 +0300
X-CheckPoint: {5020F1F7-2-1B221DC2-4FFFF}
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.3.213.0; Tue, 7 Aug 2012 13:58:19 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Tue, 7 Aug 2012 13:58:16 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "t.p." <daedulus@btconnect.com>
Date: Tue, 7 Aug 2012 13:58:13 +0300
Subject: Re: RFC Errata: when to file, and when not to
Thread-Topic: RFC Errata: when to file, and when not to
Thread-Index: Ac10i4uM9P23SNmfRyiDc0GLmk8jsA==
Message-ID: <599B1629-543A-49BC-A0E7-FA2096C538AD@checkpoint.com>
References: <CALaySJKV96tdXhzfPD1e1Mro_+gp5aDarF7Z06QrA+iQtnHkLw@mail.gmail.com><501A5656.2050407@it.aoyama.ac.jp> <501BEC0D.1060404@tana.it> <009101cd7476$bb522c20$4001a8c0@gateway.2wire.net>
In-Reply-To: <009101cd7476$bb522c20$4001a8c0@gateway.2wire.net>
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
x-cpdlp: 1109f01b72ce00a01452cadedb01ff106deb176e36
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
Cc: "ietf@ietf.org" <ietf@ietf.org>, Alessandro Vesely <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 10:58:27 -0000

On Aug 7, 2012, at 11:29 AM, t.p. wrote:
> When I Google RFCnnnn, I am sometimes directed to www.ietf.org, which is
> not much help here. Other times, I am directed to tools.ietf.org, whose
> format I find less friendly but which does have 'errata exist' in the
> top right hand corner.  However, I cannot click on that,

No, but two lines above it, there's an "Errata" link, which you can click.

> unlike the
> Obsoletes and Updates fields; but, more importantly, would your average
> not-involved-in-standards audience know what errata are?  For me, the
> word comes from a classical education, before ever I got involved with
> standards, and so is a commonplace, but is it used in the world at
> large?  I suspect not.

Probably not, and neither is "bis". But what can you do about this?  It's e=
ither allow updating of RFCs after publication, or have a list or correctio=
ns. Would it make it easier to find if they were called "notes" or "correct=
ions" instead of "errata"?

Yoav=

From vesely@tana.it  Tue Aug  7 04:12:52 2012
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BD7F21F861D for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 04:12:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.611
X-Spam-Level: 
X-Spam-Status: No, score=-4.611 tagged_above=-999 required=5 tests=[AWL=0.108,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7N-c8ghmIZRE for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 04:12:51 -0700 (PDT)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 6918D21F8607 for <ietf@ietf.org>; Tue,  7 Aug 2012 04:12:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1344337969; bh=wU87iIe45Yyh7v4Ls4alDx7IgiqiPoFB9lVDhp4gaps=; l=978; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=MRhpsTV55BCk/Kzr5/zfxqV2olcChcfGZ3H4wffgTnHcqKr+zh08iR4iuANKg2Wb4 OzDM/8obzUOJZC06OlpzKcSCwexKY1sRjH5vbbFoc1UXh60MQq2Z+o/zzIZHj39chy NS1otrmtOdAxgs5JNsZfH1WMHPyOENOw+A+ZhiSs=
Received: from [172.25.197.80] (minivista.tana [172.25.197.80]) (AUTH: PLAIN 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Tue, 07 Aug 2012 13:12:49 +0200 id 00000000005DC035.000000005020F831.00001352
Message-ID: <5020F824.7040907@tana.it>
Date: Tue, 07 Aug 2012 04:12:36 -0700
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: RFC Errata: when to file, and when not to
References: <CALaySJKV96tdXhzfPD1e1Mro_+gp5aDarF7Z06QrA+iQtnHkLw@mail.gmail.com> <501A5656.2050407@it.aoyama.ac.jp> <501BEC0D.1060404@tana.it> <CAC4RtVCM17j0O-=LO5Mcgm64mg6C1XPw+y4a1giAU4oX7UxN3g@mail.gmail.com>
In-Reply-To: <CAC4RtVCM17j0O-=LO5Mcgm64mg6C1XPw+y4a1giAU4oX7UxN3g@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 11:12:52 -0000

On Fri 03/Aug/2012 08:38:44 -0700 Barry Leiba wrote:
> 
>> "Easy" would mean that people usually find them even if they're
>> not purposely looking for them.  For example, the existence of an
>> approved errata could be signaled by coloring the margin near the
>> relevant text.
> 
> I like this idea.  Not colour, maybe -- despite the errata tool's
> format, not all errata nicely fit into OLD/NEW text, and one often
> needs the explanation even for those that do -- but perhaps an
> "errata" icon in the margin next to the relevant text.  One could
> click the icon and be sent straight to that erratum.
> 
> The trouble is that I can't see how we could do that automatically, so
> it would require significant extra manual processing.

Yes, it would be part of a verifier's job.  E.g. an additional field
in the verification form.  Empty field, no icon.  Otherwise, the field
contains an anchor, a section number, or whatever pointer the form
handler may accept.


From arturo.servin@gmail.com  Tue Aug  7 04:48:27 2012
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FEE921F86DE for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 04:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WjiZJ3p+TYFy for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 04:48:27 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 868E021F870A for <ietf@ietf.org>; Tue,  7 Aug 2012 04:48:26 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so1496830ghb.31 for <ietf@ietf.org>; Tue, 07 Aug 2012 04:48:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=h3oVFgpV2f5s7+/yqssmMXel74ks+Mge2V8UKU+xepk=; b=rTLD/JWHU4lnWDWZjUe6BPP/BPMX6YkTPsf/fZG1uOX+qzOs6PSZMWv+QXBuisoMyE QYWjRrmOz3ewkVE6ZTYzqpSq1QMc2RbL92mZkbwi9l5K5nvVACGNgxLpkhsmf/qZQdMk C5b3GhnJrWBaZu810+b3rI3bHJSkF2x4Kf8rVoDV3cmxVaZekmkzcxGCVfeqfG02Bfwt 9ikS48s6D8TECrjAxb/3ibj9XdXoKFTbhtnJVdrQt19psoPI05GUrww8j2/w438HCFWZ J2TRfR5+3mOMKBK8Nbiy6eU4th/fAT40H+p0hJeOc4+9SRWg07c01frEPICB82JWCzKt lnww==
Received: by 10.236.9.40 with SMTP id 28mr12764217yhs.128.1344340106099; Tue, 07 Aug 2012 04:48:26 -0700 (PDT)
Received: from [192.168.1.133] (r186-48-255-169.dialup.adsl.anteldata.net.uy. [186.48.255.169]) by mx.google.com with ESMTPS id l10sm357293ang.12.2012.08.07.04.48.23 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 07 Aug 2012 04:48:25 -0700 (PDT)
Subject: Re: ITU-T Dubai Meeting
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Arturo Servin <arturo.servin@gmail.com>
In-Reply-To: <5020CFB9.7090402@gmail.com>
Date: Tue, 7 Aug 2012 08:48:19 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <9C549EE0-2584-4AE1-A35A-FA69D85EF909@gmail.com>
References: <20120807074601.23F871A125@ld9781.wdf.sap.corp> <5020CFB9.7090402@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1278)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 11:48:27 -0000

Brian,

	Yes, that is true, renumbering is a fact and we may be doing it =
eventually but hopefully not frequently.

	Needing to renumbering every time that a large enterprise =
changes internet provider (frequently, every 2 or 3 years perhaps) it is =
simply not practical today and possibly it will never be.

Regards,
as

On 7 Aug 2012, at 05:20, Brian E Carpenter wrote:

> Martin,
>=20
> As far as the mass market goes, multiple prefixes and renumbering are =
a fact of life.
> See the MIF and HOMENET WGs for more.
>=20
> As far as enterprise networks go, renumbering is rather undesirable =
but sometimes
> inevitable, see 6RENUM.
>=20
> Regards
>   Brian
>=20
> On 07/08/2012 08:46, Martin Rex wrote:
>> Brian E Carpenter wrote:
>> [ Charset UTF-8 unsupported, converting... ]
>>> On 06/08/2012 23:02, Martin Rex wrote:
>>>> Steven Bellovin wrote:
>>>>> Randy Bush wrote:
>>>>>> whatever the number of address bits, if it is fixed, we always =
run out.
>>>>>> memory addressing has been a cliff many times.  ip addressing.  =
...
>>>>> Yup.  To quote Fred Brooks on memory address space: "Every =
successful
>>>>> computer architecture eventually runs out of address space" -- and =
I heard
>>>>> him say that in 1973.
>>>> I'm wondering what resource shortage would have happened if IPv6
>>>> had been massively adopted 10 years earlier, and whether we would =
have
>>>> seen the internet backbone routers suffer severely from the size
>>>> of the routing tables, if every single home customer (DSL =
subscriber)
>>>> would have required a provider-independent IPv6 network prefix =
rather
>>>> than a single, provider-dependent IPv4 IP Address.
>>> That was never a likely scenario (and still isn't). PA prefixes are =
still
>>> the norm for mass-market IP, regardless of version number.
>>=20
>>=20
>> IPv6 PA prefixes result in that awkward renumbering.
>> Avoiding the renumbering implies provider independent
>> network prefix.
>>=20
>> With IPv4, you would have typically keept your IPv4 network address
>> (the old class A, B & C from early 199x) even when changing network
>> providers.
>>=20
>>=20
>> To me, IPv6 PA prefixes look like a pretty useless feature
>> (from the customer perspective).  Either you want an =
provider-independent
>> prefix to avoid the renumbering when changing providers,
>> or you want some level of privacy protection and therefore
>> a fully dynamic temporary DHCP-assigned IPv6 address
>> (same network prefix for 10000+ customers of the ISP)
>> and for use with NAT (again to avoid the renumbering).
>>=20
>> IPv6 renumbering creates huge complexity without value (for the =
customer).
>>=20
>> -Martin
>>=20


From agmalis@gmail.com  Tue Aug  7 05:14:10 2012
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D04321F862B for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 05:14:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.286
X-Spam-Level: 
X-Spam-Status: No, score=-3.286 tagged_above=-999 required=5 tests=[AWL=0.313,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id btiiT69jelsL for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 05:14:10 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id C69C921F865C for <ietf@ietf.org>; Tue,  7 Aug 2012 05:14:09 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so1524749ghb.31 for <ietf@ietf.org>; Tue, 07 Aug 2012 05:14:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=uX321wqpAi1F0Tn3JT7R4drzWg11LFAamZ2v6UcjIcI=; b=q1GmApZr8U48UGkcX0tKHQc7EHLePsmCy0723tl2gDkFTZbrx8X8TqEQr30MdP2GCm ZlMaqqXzK5CjWKxN2pqkRDgg4CfYuTbfBR6vG9o3xIkkN0fzYgmBzsWW+aa/55VHZE3D Ko1KmulJe7HY3zsJ+i75HnQfNrV3UeKmLK3AfFsdplBRlKEZ3nqoZA4+rKBWr+5KP1Jf Fxm4RtiJQ9bYGYk7vK6/dmzOd5QQgBCiHl0xciNPzkR9pZZEVWWm4o6qJzfKmVzfZdHv Mf4TRsJUvDSkRk2VejJ9JcPvqAHwMGuRGdC2ahXX+cMdKysw9b7fjz3F31jNv9AIYPzd pUqg==
Received: by 10.50.181.136 with SMTP id dw8mr8435220igc.31.1344341649124; Tue, 07 Aug 2012 05:14:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.102.10 with HTTP; Tue, 7 Aug 2012 05:13:48 -0700 (PDT)
In-Reply-To: <29F2EDD3-71B8-4762-8753-5C7AF369001B@tzi.org>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <29F2EDD3-71B8-4762-8753-5C7AF369001B@tzi.org>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Tue, 7 Aug 2012 08:13:48 -0400
Message-ID: <CAA=duU0D1OuTKhBn=EzGqsvezVdV=E+Jj78h+rf+vbXfWtZyJA@mail.gmail.com>
Subject: Re: So, where to repeat? (was:Re: management granularity)
To: Carsten Bormann <cabo@tzi.org>
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: Tue, 07 Aug 2012 12:14:10 -0000

+1 to both of Carsten's suggestions.

On Mon, Aug 6, 2012 at 8:22 PM, Carsten Bormann <cabo@tzi.org> wrote:
> On Aug 6, 2012, at 16:41, Mary Barnes <mary.ietf.barnes@gmail.com> wrote:
>
>> If we were to choose one place in the U.S. to meet, Minneapolis is the b=
est choice IMHO.
>
> +1 a lot.
> (If we indeed have to choose the US.)
> Great facility to get work done, good food, reasonable flights.
>
> And add Prague as the staple for Europe.
>
> Gr=FC=DFe, Carsten
>

From daedulus@btconnect.com  Tue Aug  7 06:25:25 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FA4021F85C7 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 06:25:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.571
X-Spam-Level: 
X-Spam-Status: No, score=-3.571 tagged_above=-999 required=5 tests=[AWL=0.028,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PUxXVJAesWlI for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 06:25:24 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe003.messaging.microsoft.com [216.32.181.183]) by ietfa.amsl.com (Postfix) with ESMTP id 80F3821F85A5 for <ietf@ietf.org>; Tue,  7 Aug 2012 06:25:24 -0700 (PDT)
Received: from mail244-ch1-R.bigfish.com (10.43.68.236) by CH1EHSOBE009.bigfish.com (10.43.70.59) with Microsoft SMTP Server id 14.1.225.23; Tue, 7 Aug 2012 13:25:23 +0000
Received: from mail244-ch1 (localhost [127.0.0.1])	by mail244-ch1-R.bigfish.com (Postfix) with ESMTP id A0C378002C0; Tue,  7 Aug 2012 13:25:23 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.224.141; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0702HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: PS-23(zz98dI9371I542Mzz1202hzz1033IL8275bh8275dhz2dh2a8h5a9h668h839hd24hf0ah107ah304l)
Received: from mail244-ch1 (localhost.localdomain [127.0.0.1]) by mail244-ch1 (MessageSwitch) id 134434592296458_32050; Tue,  7 Aug 2012 13:25:22 +0000 (UTC)
Received: from CH1EHSMHS003.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.240])	by mail244-ch1.bigfish.com (Postfix) with ESMTP id 15B361BC004A;	Tue,  7 Aug 2012 13:25:22 +0000 (UTC)
Received: from DB3PRD0702HT001.eurprd07.prod.outlook.com (157.55.224.141) by CH1EHSMHS003.bigfish.com (10.43.70.3) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 7 Aug 2012 13:25:19 +0000
Received: from DBXPRD0510HT004.eurprd05.prod.outlook.com (157.56.252.165) by pod51017.outlook.com (10.3.4.141) with Microsoft SMTP Server (TLS) id 14.15.108.4; Tue, 7 Aug 2012 13:25:10 +0000
Message-ID: <03e701cd749f$73891c40$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Yoav Nir <ynir@checkpoint.com>
References: <CALaySJKV96tdXhzfPD1e1Mro_+gp5aDarF7Z06QrA+iQtnHkLw@mail.gmail.com><501A5656.2050407@it.aoyama.ac.jp> <501BEC0D.1060404@tana.it> <009101cd7476$bb522c20$4001a8c0@gateway.2wire.net> <599B1629-543A-49BC-A0E7-FA2096C538AD@checkpoint.com>
Subject: Re: RFC Errata: when to file, and when not to
Date: Tue, 7 Aug 2012 14:20:35 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.252.165]
X-OriginatorOrg: btconnect.com
Cc: ietf@ietf.org, Alessandro Vesely <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 13:25:25 -0000

----- Original Message -----
From: "Yoav Nir" <ynir@checkpoint.com>
To: "t.p." <daedulus@btconnect.com>
Cc: "Alessandro Vesely" <vesely@tana.it>; <ietf@ietf.org>
Sent: Tuesday, August 07, 2012 11:58 AM
On Aug 7, 2012, at 11:29 AM, t.p. wrote:
> When I Google RFCnnnn, I am sometimes directed to www.ietf.org, which
is
> not much help here. Other times, I am directed to tools.ietf.org,
whose
> format I find less friendly but which does have 'errata exist' in the
> top right hand corner.  However, I cannot click on that,

No, but two lines above it, there's an "Errata" link, which you can
click.

> unlike the
> Obsoletes and Updates fields; but, more importantly, would your
average
> not-involved-in-standards audience know what errata are?  For me, the
> word comes from a classical education, before ever I got involved with
> standards, and so is a commonplace, but is it used in the world at
> large?  I suspect not.

Probably not, and neither is "bis". But what can you do about this?
It's either allow updating of RFCs after publication, or have a list or
corrections. Would it make it easier to find if they were called "notes"
or "corrections" instead of "errata"?

<tp>
Yes, corrections is what I see published in a newspaper to correct
errata in previous editions.  So far, it is the best word I can think of
(but there might be a better one:-).

In the html version of an RFC, it would be easy to provide old and new
in an easy to compare format (as some editors do for I-D), not perhaps
on permanent display but shown when 'errata' (or whatever name we
choose) is toggled.

Tom Petch
</tp>

Yoav



From jnc@mercury.lcs.mit.edu  Tue Aug  7 07:32:42 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D434E21F85D0 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 07:32:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.256
X-Spam-Level: 
X-Spam-Status: No, score=-6.256 tagged_above=-999 required=5 tests=[AWL=0.343,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1G6lK4I6Jmgh for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 07:32:42 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 3661021F84DF for <ietf@ietf.org>; Tue,  7 Aug 2012 07:32:42 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 44D2118C0B5; Tue,  7 Aug 2012 10:32:41 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: ITU-T Dubai Meeting
Message-Id: <20120807143241.44D2118C0B5@mercury.lcs.mit.edu>
Date: Tue,  7 Aug 2012 10:32:41 -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, 07 Aug 2012 14:32:43 -0000

    > From: mrex@sap.com (Martin Rex)

    > To me, IPv6 PA prefixes look like a pretty useless feature (from the
    > customer perspective). 

Far be it from me to defend IPv6, but... I don't see the case here.

Our house is pretty typical of the _average_ consumer - we have a provider
suppplied PA address (IPv4, but the principles are the same), which they seem
to change on a fairly regular basis as they renumber/reorganize their
network. However, as we don't run any servers/services, we don't care. Thanks
to the magic of DHCP, etc, everything 'just works'. So for the _average_
customer (who are 99.9...% of their customers), PA is just fine.

    > you want some level of privacy protection and therefore a fully dynamic
    > temporary DHCP-assigned IPv6 address

This turns out to be a chimera. Such addresses don't really provide any real
privacy - it turns out to be easy to track people through their access
patterns, etc.

	Noel

From dworley@avaya.com  Tue Aug  7 07:42:18 2012
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 C973221F8599 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 07:42:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.265
X-Spam-Level: 
X-Spam-Status: No, score=-103.265 tagged_above=-999 required=5 tests=[AWL=0.334, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TudtBza4Fy4F for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 07:42:18 -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 218B621F8568 for <ietf@ietf.org>; Tue,  7 Aug 2012 07:42:18 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EANwoIVCHCzI1/2dsb2JhbABFuUaBB4IgAQEBAQIBEihECwIBCA0IIRAyJQEBBAESCBqHZQaeWZ1aizOFaWADm0WKD4J7
X-IronPort-AV: E=Sophos;i="4.77,727,1336363200"; d="scan'208";a="360728479"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 07 Aug 2012 10:38:04 -0400
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 07 Aug 2012 10:22:13 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Tue, 7 Aug 2012 10:42:10 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 7 Aug 2012 10:42:10 -0400
Subject: RE: So, where to repeat? (was: Re: management granularity)
Thread-Topic: So, where to repeat? (was: Re: management granularity)
Thread-Index: Ac10OWtm6awxDaQ2RV6olqa/n7yI9QAbuuz1
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0BFE@DC-US1MBEX4.global.avaya.com>
References: <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com>, <20120807010945.51851.qmail@joyce.lan>
In-Reply-To: <20120807010945.51851.qmail@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 14:42:19 -0000

> From: John Levine [johnl@taugh.com]
>=20
> >It would have cost me more than twice as much as it did to fly to
> >Beijing, for example, if I had taken a direct flight from DFW
>=20
> That's very odd.  I see lots of fares from DFW to YVR from Saturday to
> Saturday via Houston or Denver for in upcoming weeks for under $550,
> and nonstops for $678.

I expect that a chunk of the variance hinges on the qualifier
"direct", which Mary included and Jon did not.  Mary uses a major hub
(DFW) and can plausibly take direct flights to many locations.  I
don't, and I never even consider searching for direct flights.  But
the market for direct flights is likely to be much thinner than the
market for connecting flights, and to be more subject to spot
shortages and the vagaries of how airles have laid out their route
systems.

More disturbing is Mary's later "My indirect flight was $1156.23."
It'd be useful to get information from someone who really knows
airfares as to why that might happen.  But I can see from ITA Software
that even indirect flights DFW-YVR in the near future can easily reach
$650, and higher within the next two weeks.  Tickets BOS-YVR (my
route) have about the same prices.

Dale

From dworley@avaya.com  Tue Aug  7 08:02:19 2012
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 C951D21F8618 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 08:02:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.269
X-Spam-Level: 
X-Spam-Status: No, score=-103.269 tagged_above=-999 required=5 tests=[AWL=0.330, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8yoZhHrA1dAg for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 08:02:14 -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 EBF9D11E808E for <ietf@ietf.org>; Tue,  7 Aug 2012 08:02:12 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAKQtIVDGmAcF/2dsb2JhbABFuUaBB4IgAQEBAQIBEig/BQsCAQgNCCEQMiUBAQQBDQUIGodlBp5inVyRHGADm0WKD4J7
X-IronPort-AV: E=Sophos;i="4.77,727,1336363200"; d="scan'208";a="360732321"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 07 Aug 2012 10:57:39 -0400
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by co300216-co-erhwest-out.avaya.com with ESMTP; 07 Aug 2012 10:56:57 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Tue, 7 Aug 2012 11:01:44 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "mrex@sap.com" <mrex@sap.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Tue, 7 Aug 2012 10:58:48 -0400
Subject: RE: ITU-T Dubai Meeting
Thread-Topic: ITU-T Dubai Meeting
Thread-Index: Ac10cL8CGWYk7x7UQ6KhU+HuV40WbwAPGd32
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0C01@DC-US1MBEX4.global.avaya.com>
References: <5020BF3A.2080903@gmail.com>, <20120807074601.23F871A125@ld9781.wdf.sap.corp>
In-Reply-To: <20120807074601.23F871A125@ld9781.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: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 15:02:20 -0000

> From: Martin Rex [mrex@sap.com]
>=20
> IPv6 PA prefixes result in that awkward renumbering.  Avoiding the
> renumbering implies provider independent network prefix.
>=20
> With IPv4, you would have typically keept your IPv4 network address
> (the old class A, B & C from early 199x) even when changing network
> providers.

I've been told that ISPs don't like routing to their customers using
routing-independent prefixes (in IPv4), and that the result is that
small organizations (in practice) use provider address space.
Certainly there would be a problem with routing table size if all
organizations used provider-independent prefixes.

Dale

From ynir@checkpoint.com  Tue Aug  7 08:05:43 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCEF221F84F8 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 08:05:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.374
X-Spam-Level: 
X-Spam-Status: No, score=-10.374 tagged_above=-999 required=5 tests=[AWL=0.225, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vugPk+3YpC1J for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 08:05:43 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 87C9721F84E7 for <ietf@ietf.org>; Tue,  7 Aug 2012 08:05:42 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id q77F5eNm015486; Tue, 7 Aug 2012 18:05:40 +0300
X-CheckPoint: {50212BED-0-1B221DC2-4FFFF}
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.3.213.0; Tue, 7 Aug 2012 18:05:39 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Tue, 7 Aug 2012 18:05:36 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Date: Tue, 7 Aug 2012 18:05:35 +0300
Subject: Re: ITU-T Dubai Meeting
Thread-Topic: ITU-T Dubai Meeting
Thread-Index: Ac10rhk02reezI+XSIiv+nMH8R+rzQ==
Message-ID: <74BA9587-13DB-4228-BB84-46D4C33EBAF3@checkpoint.com>
References: <20120807143241.44D2118C0B5@mercury.lcs.mit.edu>
In-Reply-To: <20120807143241.44D2118C0B5@mercury.lcs.mit.edu>
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
x-cpdlp: 114e7206f0ebf4a05fdae437315c6a7e955c2b0ca3
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
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, 07 Aug 2012 15:05:44 -0000

On Aug 7, 2012, at 5:32 PM, Noel Chiappa wrote:

>> From: mrex@sap.com (Martin Rex)
>=20
>> To me, IPv6 PA prefixes look like a pretty useless feature (from the
>> customer perspective).=20
>=20
> Far be it from me to defend IPv6, but... I don't see the case here.
>=20
> Our house is pretty typical of the _average_ consumer - we have a provide=
r
> suppplied PA address (IPv4, but the principles are the same), which they =
seem
> to change on a fairly regular basis as they renumber/reorganize their
> network. However, as we don't run any servers/services, we don't care. Th=
anks
> to the magic of DHCP, etc, everything 'just works'. So for the _average_
> customer (who are 99.9...% of their customers), PA is just fine.

If home automation systems become more commonplace, having a "server" at ho=
me may also become more commonplace. What's the point of having an IPv6-ena=
bled lightbulb if you can't turn it off from half-way around the world? =20

But as long as DNS updates dynamically, this shouldn't be a problem.=20

For organizations renumbering is more painful, but as long as there's plent=
y of time to prepare - it should be manageable. If it's too painful, there =
are provider independent addresses, but how many really need them?

Yoav=

From ajs@anvilwalrusden.com  Tue Aug  7 08:11:08 2012
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 AB17021F875D for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 08:11:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.194
X-Spam-Level: 
X-Spam-Status: No, score=-1.194 tagged_above=-999 required=5 tests=[AWL=-0.354, BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wGnAZthIfFBj for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 08:11:07 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 5DF2221F8665 for <ietf@ietf.org>; Tue,  7 Aug 2012 08:11:07 -0700 (PDT)
Received: from mail.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 496918A031 for <ietf@ietf.org>; Tue,  7 Aug 2012 15:11:06 +0000 (UTC)
Date: Tue, 7 Aug 2012 11:11:04 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: So, where to repeat? (was: Re: management granularity)
Message-ID: <20120807151103.GT53917@mail.yitter.info>
References: <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <20120807010945.51851.qmail@joyce.lan> <CD5674C3CD99574EBA7432465FC13C1B22726A0BFE@DC-US1MBEX4.global.avaya.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A0BFE@DC-US1MBEX4.global.avaya.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 15:11:08 -0000

Dear colleagues,

On Tue, Aug 07, 2012 at 10:42:10AM -0400, Worley, Dale R (Dale) wrote:

> I expect that a chunk of the variance hinges on the qualifier

While the vagaries of air transport costs fascinate me, I'm not sure
how the question of the cost of one route at one time for one person
is broadly relevant.  The basic fact of having meetings in multiple
places (which is a direct consequence of trying to spread the pain of
travel) is that sometimes each of us will have an expensive flight.
(This is the same reason that I think confusing the
scheduling-in-advance question with the venue question is a bad idea.)

Dave Crocker's original point was that some venues are "good enough"
that you can tune them to be better.  I was sceptical, but upthread we
had two proposals: Minneapolis and Prague.  Nobody seems to have
argued against.

Any others?  At the plenary in Vancouver we heard "go here again", and
we've already decided to run that trial in any case.  That makes
three.  Also, many people expressed satisfaction in QuÃ©bec.

Vancouver's Pacific location notwithstanding, this appears to me to
suggest that we have one "repeat" location in Europe and two in North
America.  This leaves us rather thin in Asia-Pacific.  I recall people
saying good things about Taipei.  

The point of all this, in case it isn't clear, is to ask to add a
question to the post-meeting survey about specific venues and whether
future meetings should try to return to them.  Given Arrow paradoxes
and so on, I think a short list with "yes/no" for each is much more
likely to yield useful aggregate results than a big list or a rank
order.  So, I'd like to suggest the following survey item be added to
the post-Vancouver survey:

    Do you support the IETF returning to the very same venue (hotel
    and meeting facilities) as the last time in the following
    meetings:

    - IETF 84, Vancouver (Hyatt) [Y|N]
    - IETF 82, Taipei (Hyatt and TICC) [Y|N]
    - IETF 81, QuÃ©bec (Hilton) [Y|N]
    - IETF 80, Prague (Hilton) [Y|N]
    - IETF 73, Minneapolis (Hilton) [Y|N]

I suppose we could just add every venue from the last _n_ years, but
I'm reluctant to do that because I think it will give too many
options. 

I seem to recall at least some of the previous post-meeting surveys
asking this question about the venue we were just in.  I think it
would be interesting, however, to pick a few popular venues and track
their ratings over time.

This is merely a suggestion for the IAOC, and I hope they feel free to
treat it as a bad idea.  (It's also the last I have to say on this
topic, since I've used up my bit quota.)

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From jnc@mercury.lcs.mit.edu  Tue Aug  7 08:19:31 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9BF121F86F6 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 08:19:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.283
X-Spam-Level: 
X-Spam-Status: No, score=-6.283 tagged_above=-999 required=5 tests=[AWL=0.316,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PdGVJkJFdZRB for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 08:19:30 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id CF7D921F855B for <ietf@ietf.org>; Tue,  7 Aug 2012 08:19:30 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 804E518C0B2; Tue,  7 Aug 2012 11:19:30 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: ITU-T Dubai Meeting
Message-Id: <20120807151930.804E518C0B2@mercury.lcs.mit.edu>
Date: Tue,  7 Aug 2012 11:19:30 -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, 07 Aug 2012 15:19:32 -0000

    > From: Yoav Nir <ynir@checkpoint.com>

    > For organizations renumbering is more painful, but as long as there's
    > plenty of time to prepare - it should be manageable. If it's too
    > painful, there are provider independent addresses, but how many really
    > need them?

Or we could separate location and identity. Just a thought. Oh, wait...

(Just channeling my inner Randy... :-)

	Noel

From ynir@checkpoint.com  Tue Aug  7 08:23:06 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3818021F86B8 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 08:23:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.378
X-Spam-Level: 
X-Spam-Status: No, score=-10.378 tagged_above=-999 required=5 tests=[AWL=0.221, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qTsDP7NLMWOm for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 08:23:05 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 8E3A621F8608 for <ietf@ietf.org>; Tue,  7 Aug 2012 08:23:04 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id q77FN1no019394; Tue, 7 Aug 2012 18:23:01 +0300
X-CheckPoint: {50212FFE-2-1B221DC2-4FFFF}
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.3.213.0; Tue, 7 Aug 2012 18:23:01 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Tue, 7 Aug 2012 18:22:59 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Date: Tue, 7 Aug 2012 18:22:58 +0300
Subject: Re: ITU-T Dubai Meeting
Thread-Topic: ITU-T Dubai Meeting
Thread-Index: Ac10sIZz1GVkR8LHQkWXu751XGIUGQ==
Message-ID: <48BB64DC-B10D-458B-B108-B0AD5E61F99D@checkpoint.com>
References: <20120807151930.804E518C0B2@mercury.lcs.mit.edu>
In-Reply-To: <20120807151930.804E518C0B2@mercury.lcs.mit.edu>
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
x-cpdlp: 1152b4763592a1f4c019825139dc68eb09d1c55ff2
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
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, 07 Aug 2012 15:23:06 -0000

On Aug 7, 2012, at 6:19 PM, Noel Chiappa wrote:

>> From: Yoav Nir <ynir@checkpoint.com>
>=20
>> For organizations renumbering is more painful, but as long as there's
>> plenty of time to prepare - it should be manageable. If it's too
>> painful, there are provider independent addresses, but how many really
>> need them?
>=20
> Or we could separate location and identity. Just a thought. Oh, wait...

I'm the same person, I live in the same house. My computer is connected to =
the same socket in the wall. All I changed was the ISP. Why do we call the =
thing that's changed "location"?=

From nurit.sprecher@nsn.com  Tue Aug  7 08:29:15 2012
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 7C17721F8766 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 08:29:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.44
X-Spam-Level: 
X-Spam-Status: No, score=-6.44 tagged_above=-999 required=5 tests=[AWL=0.159,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y+dGRoXf++iJ for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 08:29:14 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 1BC9E21F8763 for <ietf@ietf.org>; Tue,  7 Aug 2012 08:29:13 -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 q77FT9iw024884 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Aug 2012 17:29:09 +0200
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q77FT8VI031057; Tue, 7 Aug 2012 17:29:09 +0200
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 7 Aug 2012 17:28:26 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Subject: RE: So, where to repeat? (was: Re: management granularity)
Date: Tue, 7 Aug 2012 17:28:33 +0200
Message-ID: <E4873516F3FC7547BCFE792C7D94039C023151B7@DEMUEXC013.nsn-intra.net>
In-Reply-To: <20120807151103.GT53917@mail.yitter.info>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: So, where to repeat? (was: Re: management granularity)
Thread-Index: Ac10rvI5QJlRspEjSpy8Ml/sRIfn/QAAhiUg
References: <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com><20120807010945.51851.qmail@joyce.lan><CD5674C3CD99574EBA7432465FC13C1B22726A0BFE@DC-US1MBEX4.global.avaya.com> <20120807151103.GT53917@mail.yitter.info>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext Andrew Sullivan" <ajs@anvilwalrusden.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 07 Aug 2012 15:28:26.0507 (UTC) FILETIME=[4A1D25B0:01CD74B1]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 4484
X-purgate-ID: 151667::1344353350-00002E58-13F12378/0-0/0-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, 07 Aug 2012 15:29:15 -0000

V2h5IHRoZSBzdXJ2ZXkgc2hvdWxkIGxpbWl0IGl0IHRvIHRoZSBsYXN0IGZpdmUgbWVldGluZ3Mu
Li4NCkluIHRoZSBsb25nIGhpc3Rvcnkgd2UgZXhwZXJpZW5jZWQgYWRkaXRpb25hbCBnb29kIHBs
YWNlcy4uLi4NClNvIG1heWJlIHRoZSBzdXJ2ZXkgc2hvdWxkIGJlIG1vcmUgb3BlbiBhbmQgbGV0
IGVhY2ggbGlzdCBoaXMgMy01IGZhdm9yYWJsZSBwbGFjZXMgYmFzZWQgb24gdGhlIGV4cGVyaWVu
Y2UgZnJvbSBlYXJsaWVyIG1lZXRpbmdzPw0KQmVzdCByZWdhcmRzLA0KTnVyaXQNCg0KLS0tLS1P
cmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGlldGYtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRv
OmlldGYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIGV4dCBBbmRyZXcgU3VsbGl2YW4N
ClNlbnQ6IFR1ZXNkYXksIEF1Z3VzdCAwNywgMjAxMiA2OjExIFBNDQpUbzogaWV0ZkBpZXRmLm9y
Zw0KU3ViamVjdDogUmU6IFNvLCB3aGVyZSB0byByZXBlYXQ/ICh3YXM6IFJlOiBtYW5hZ2VtZW50
IGdyYW51bGFyaXR5KQ0KDQpEZWFyIGNvbGxlYWd1ZXMsDQoNCk9uIFR1ZSwgQXVnIDA3LCAyMDEy
IGF0IDEwOjQyOjEwQU0gLTA0MDAsIFdvcmxleSwgRGFsZSBSIChEYWxlKSB3cm90ZToNCg0KPiBJ
IGV4cGVjdCB0aGF0IGEgY2h1bmsgb2YgdGhlIHZhcmlhbmNlIGhpbmdlcyBvbiB0aGUgcXVhbGlm
aWVyDQoNCldoaWxlIHRoZSB2YWdhcmllcyBvZiBhaXIgdHJhbnNwb3J0IGNvc3RzIGZhc2NpbmF0
ZSBtZSwgSSdtIG5vdCBzdXJlDQpob3cgdGhlIHF1ZXN0aW9uIG9mIHRoZSBjb3N0IG9mIG9uZSBy
b3V0ZSBhdCBvbmUgdGltZSBmb3Igb25lIHBlcnNvbg0KaXMgYnJvYWRseSByZWxldmFudC4gIFRo
ZSBiYXNpYyBmYWN0IG9mIGhhdmluZyBtZWV0aW5ncyBpbiBtdWx0aXBsZQ0KcGxhY2VzICh3aGlj
aCBpcyBhIGRpcmVjdCBjb25zZXF1ZW5jZSBvZiB0cnlpbmcgdG8gc3ByZWFkIHRoZSBwYWluIG9m
DQp0cmF2ZWwpIGlzIHRoYXQgc29tZXRpbWVzIGVhY2ggb2YgdXMgd2lsbCBoYXZlIGFuIGV4cGVu
c2l2ZSBmbGlnaHQuDQooVGhpcyBpcyB0aGUgc2FtZSByZWFzb24gdGhhdCBJIHRoaW5rIGNvbmZ1
c2luZyB0aGUNCnNjaGVkdWxpbmctaW4tYWR2YW5jZSBxdWVzdGlvbiB3aXRoIHRoZSB2ZW51ZSBx
dWVzdGlvbiBpcyBhIGJhZCBpZGVhLikNCg0KRGF2ZSBDcm9ja2VyJ3Mgb3JpZ2luYWwgcG9pbnQg
d2FzIHRoYXQgc29tZSB2ZW51ZXMgYXJlICJnb29kIGVub3VnaCINCnRoYXQgeW91IGNhbiB0dW5l
IHRoZW0gdG8gYmUgYmV0dGVyLiAgSSB3YXMgc2NlcHRpY2FsLCBidXQgdXB0aHJlYWQgd2UNCmhh
ZCB0d28gcHJvcG9zYWxzOiBNaW5uZWFwb2xpcyBhbmQgUHJhZ3VlLiAgTm9ib2R5IHNlZW1zIHRv
IGhhdmUNCmFyZ3VlZCBhZ2FpbnN0Lg0KDQpBbnkgb3RoZXJzPyAgQXQgdGhlIHBsZW5hcnkgaW4g
VmFuY291dmVyIHdlIGhlYXJkICJnbyBoZXJlIGFnYWluIiwgYW5kDQp3ZSd2ZSBhbHJlYWR5IGRl
Y2lkZWQgdG8gcnVuIHRoYXQgdHJpYWwgaW4gYW55IGNhc2UuICBUaGF0IG1ha2VzDQp0aHJlZS4g
IEFsc28sIG1hbnkgcGVvcGxlIGV4cHJlc3NlZCBzYXRpc2ZhY3Rpb24gaW4gUXXDqWJlYy4NCg0K
VmFuY291dmVyJ3MgUGFjaWZpYyBsb2NhdGlvbiBub3R3aXRoc3RhbmRpbmcsIHRoaXMgYXBwZWFy
cyB0byBtZSB0bw0Kc3VnZ2VzdCB0aGF0IHdlIGhhdmUgb25lICJyZXBlYXQiIGxvY2F0aW9uIGlu
IEV1cm9wZSBhbmQgdHdvIGluIE5vcnRoDQpBbWVyaWNhLiAgVGhpcyBsZWF2ZXMgdXMgcmF0aGVy
IHRoaW4gaW4gQXNpYS1QYWNpZmljLiAgSSByZWNhbGwgcGVvcGxlDQpzYXlpbmcgZ29vZCB0aGlu
Z3MgYWJvdXQgVGFpcGVpLiAgDQoNClRoZSBwb2ludCBvZiBhbGwgdGhpcywgaW4gY2FzZSBpdCBp
c24ndCBjbGVhciwgaXMgdG8gYXNrIHRvIGFkZCBhDQpxdWVzdGlvbiB0byB0aGUgcG9zdC1tZWV0
aW5nIHN1cnZleSBhYm91dCBzcGVjaWZpYyB2ZW51ZXMgYW5kIHdoZXRoZXINCmZ1dHVyZSBtZWV0
aW5ncyBzaG91bGQgdHJ5IHRvIHJldHVybiB0byB0aGVtLiAgR2l2ZW4gQXJyb3cgcGFyYWRveGVz
DQphbmQgc28gb24sIEkgdGhpbmsgYSBzaG9ydCBsaXN0IHdpdGggInllcy9ubyIgZm9yIGVhY2gg
aXMgbXVjaCBtb3JlDQpsaWtlbHkgdG8geWllbGQgdXNlZnVsIGFnZ3JlZ2F0ZSByZXN1bHRzIHRo
YW4gYSBiaWcgbGlzdCBvciBhIHJhbmsNCm9yZGVyLiAgU28sIEknZCBsaWtlIHRvIHN1Z2dlc3Qg
dGhlIGZvbGxvd2luZyBzdXJ2ZXkgaXRlbSBiZSBhZGRlZCB0bw0KdGhlIHBvc3QtVmFuY291dmVy
IHN1cnZleToNCg0KICAgIERvIHlvdSBzdXBwb3J0IHRoZSBJRVRGIHJldHVybmluZyB0byB0aGUg
dmVyeSBzYW1lIHZlbnVlIChob3RlbA0KICAgIGFuZCBtZWV0aW5nIGZhY2lsaXRpZXMpIGFzIHRo
ZSBsYXN0IHRpbWUgaW4gdGhlIGZvbGxvd2luZw0KICAgIG1lZXRpbmdzOg0KDQogICAgLSBJRVRG
IDg0LCBWYW5jb3V2ZXIgKEh5YXR0KSBbWXxOXQ0KICAgIC0gSUVURiA4MiwgVGFpcGVpIChIeWF0
dCBhbmQgVElDQykgW1l8Tl0NCiAgICAtIElFVEYgODEsIFF1w6liZWMgKEhpbHRvbikgW1l8Tl0N
CiAgICAtIElFVEYgODAsIFByYWd1ZSAoSGlsdG9uKSBbWXxOXQ0KICAgIC0gSUVURiA3MywgTWlu
bmVhcG9saXMgKEhpbHRvbikgW1l8Tl0NCg0KSSBzdXBwb3NlIHdlIGNvdWxkIGp1c3QgYWRkIGV2
ZXJ5IHZlbnVlIGZyb20gdGhlIGxhc3QgX25fIHllYXJzLCBidXQNCkknbSByZWx1Y3RhbnQgdG8g
ZG8gdGhhdCBiZWNhdXNlIEkgdGhpbmsgaXQgd2lsbCBnaXZlIHRvbyBtYW55DQpvcHRpb25zLiAN
Cg0KSSBzZWVtIHRvIHJlY2FsbCBhdCBsZWFzdCBzb21lIG9mIHRoZSBwcmV2aW91cyBwb3N0LW1l
ZXRpbmcgc3VydmV5cw0KYXNraW5nIHRoaXMgcXVlc3Rpb24gYWJvdXQgdGhlIHZlbnVlIHdlIHdl
cmUganVzdCBpbi4gIEkgdGhpbmsgaXQNCndvdWxkIGJlIGludGVyZXN0aW5nLCBob3dldmVyLCB0
byBwaWNrIGEgZmV3IHBvcHVsYXIgdmVudWVzIGFuZCB0cmFjaw0KdGhlaXIgcmF0aW5ncyBvdmVy
IHRpbWUuDQoNClRoaXMgaXMgbWVyZWx5IGEgc3VnZ2VzdGlvbiBmb3IgdGhlIElBT0MsIGFuZCBJ
IGhvcGUgdGhleSBmZWVsIGZyZWUgdG8NCnRyZWF0IGl0IGFzIGEgYmFkIGlkZWEuICAoSXQncyBh
bHNvIHRoZSBsYXN0IEkgaGF2ZSB0byBzYXkgb24gdGhpcw0KdG9waWMsIHNpbmNlIEkndmUgdXNl
ZCB1cCBteSBiaXQgcXVvdGEuKQ0KDQpCZXN0LA0KDQpBDQoNCi0tIA0KQW5kcmV3IFN1bGxpdmFu
DQphanNAYW52aWx3YWxydXNkZW4uY29tDQo=

From jnc@mercury.lcs.mit.edu  Tue Aug  7 08:35:47 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83B1421F8682 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 08:35:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.295
X-Spam-Level: 
X-Spam-Status: No, score=-6.295 tagged_above=-999 required=5 tests=[AWL=0.304,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d7NEqlD5V8VR for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 08:35:47 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 9305821F867F for <ietf@ietf.org>; Tue,  7 Aug 2012 08:35:46 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 46C8D18C0B3; Tue,  7 Aug 2012 11:35:46 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: ITU-T Dubai Meeting
Message-Id: <20120807153546.46C8D18C0B3@mercury.lcs.mit.edu>
Date: Tue,  7 Aug 2012 11:35:46 -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, 07 Aug 2012 15:35:47 -0000

    > From: Yoav Nir <ynir@checkpoint.com>

    > I live in the same house. My computer is connected to the same socket
    > in the wall.

That's your physical location. Irrelevant (basically) ato the network.

    > All I changed was the ISP. Why do we call the = thing that's changed
    > "location"?

'Location' in the network-centric sense (i.e. 'where in the overall network's
connectivity map you are').

Is there a better term? (Not that we're likely to be able to switch to it
now, 'location' is too engrained, going back to RFC-1498, if not before.)

	Noel

From ynir@checkpoint.com  Tue Aug  7 08:53:54 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AE5721F87C9 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 08:53:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.381
X-Spam-Level: 
X-Spam-Status: No, score=-10.381 tagged_above=-999 required=5 tests=[AWL=0.218, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T+c1VxDFwwwm for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 08:53:53 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 03E7121F87C1 for <ietf@ietf.org>; Tue,  7 Aug 2012 08:53:51 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id q77FrnqN026093; Tue, 7 Aug 2012 18:53:49 +0300
X-CheckPoint: {50213736-0-1B221DC2-4FFFF}
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.3.213.0; Tue, 7 Aug 2012 18:53:49 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Tue, 7 Aug 2012 18:53:47 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Date: Tue, 7 Aug 2012 18:53:47 +0300
Subject: Re: ITU-T Dubai Meeting
Thread-Topic: ITU-T Dubai Meeting
Thread-Index: Ac10tNR4stgOaLmJQ/SXOAS8G8kUxw==
Message-ID: <99E96486-74D0-40B2-9CC2-7C3B514639C5@checkpoint.com>
References: <20120807153546.46C8D18C0B3@mercury.lcs.mit.edu>
In-Reply-To: <20120807153546.46C8D18C0B3@mercury.lcs.mit.edu>
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
x-cpdlp: 11a43a8caf187284aa7558742be9c7a88ba44eb852
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
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, 07 Aug 2012 15:53:54 -0000

On Aug 7, 2012, at 6:35 PM, Noel Chiappa wrote:

>> All I changed was the ISP. Why do we call the =3D thing that's changed
>> "location"?
>=20
> 'Location' in the network-centric sense (i.e. 'where in the overall netwo=
rk's
> connectivity map you are').

Right.

The location is pretty much irrelevant to the user. Too bad changing it inv=
olves pain for the user rather than just pain for the core (ISPs and such)=

From ajs@anvilwalrusden.com  Tue Aug  7 09:01:46 2012
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 9A21F21F8690 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 09:01:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.19
X-Spam-Level: 
X-Spam-Status: No, score=-1.19 tagged_above=-999 required=5 tests=[AWL=-0.350,  BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UslYPLFV7vA3 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 09:01:46 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 0C1F621F8733 for <ietf@ietf.org>; Tue,  7 Aug 2012 09:01:45 -0700 (PDT)
Received: from mail.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 27A438A031 for <ietf@ietf.org>; Tue,  7 Aug 2012 16:01:45 +0000 (UTC)
Date: Tue, 7 Aug 2012 12:01:43 -0400
From: ext Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: the methodology (was: So, where to repeat? (was: Re: management granularity))
Message-ID: <20120807160143.GW53917@mail.yitter.info>
References: <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <20120807010945.51851.qmail@joyce.lan> <CD5674C3CD99574EBA7432465FC13C1B22726A0BFE@DC-US1MBEX4.global.avaya.com> <20120807151103.GT53917@mail.yitter.info> <E4873516F3FC7547BCFE792C7D94039C023151B7@DEMUEXC013.nsn-intra.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E4873516F3FC7547BCFE792C7D94039C023151B7@DEMUEXC013.nsn-intra.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 16:01:46 -0000

Ok, I know I said that I'd shut up, but this is a clarifying question,
so I'll answer.

On Tue, Aug 07, 2012 at 05:28:33PM +0200, Sprecher, Nurit (NSN - IL/Hod HaSharon) wrote:
> Why the survey should limit it to the last five meetings...

That's what the oblique reference to Arrow-and-other-issues was about.
It turns out that if you give groups of people choices, the
preferences in a set are not necessarily transitive in the aggregate
even if they are in the individual cases.  (This is why preferential
ballot systems and so on have paradoxical effects.)  Similarly, if you
give people too many options, you overwhelm their ability to answer
and you get answers that are not consistent with the answers under
more narrowly constrained choices.

Survey methodology is one of my hobby horses.  The approach I
suggested is far from perfect, but given the lousy sample (our sample
is always self-selected) it seemed likely to me to produce better data
than other approaches.  I can justify this at greater length off list
if you really want.

> In the long history we experienced additional good places....

I picked recent ones where I heard people say good things and I didn't
hear very many complaints; also, I included only things people have
quite recently praised (that's why Minneapolis is on there even though
the last visit was some years ago).  I should note that I haven't
really found anything too bad about _any_ meeting I've been to, so I
don't have a horse in this race.  Anaheim was my least favourite, but
I still had a useful meeting, which is my real measure.  (Once again,
I note, people complained rather little and the weather was good.  I'm
pretty convinced about the weather-to-complaints correlation.  Maybe
we need a COLDNWET WG.)

> So maybe the survey should be more open and let each list his 3-5 favorable places based on the experience from earlier meetings?

No, that will produce totally useless data.  There will be no way to
reconcile it.  And anyway, because of the transitivity problem, we
could end up picking everyone's last choice out of that list to go to.

Now I really will shut up,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From hartmans@mit.edu  Tue Aug  7 10:22:32 2012
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33D0D21F866B for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 10:22:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.425
X-Spam-Level: 
X-Spam-Status: No, score=-99.425 tagged_above=-999 required=5 tests=[AWL=-3.757, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vA275YJ1988z for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 10:22:31 -0700 (PDT)
Received: from ec2-23-21-76-251.compute-1.amazonaws.com (ec2-23-21-227-93.compute-1.amazonaws.com [23.21.227.93]) by ietfa.amsl.com (Postfix) with ESMTP id A01F521F865D for <ietf@ietf.org>; Tue,  7 Aug 2012 10:22:30 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 9A213202A8; Tue,  7 Aug 2012 13:13:54 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 64A5C4350; Tue,  7 Aug 2012 09:36:14 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Margaret Wasserman <mrw@lilacglade.org>
Subject: Re: So, where to repeat?
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <01ae01cd7412$abe83e50$03b8baf0$@us> <841C1C01-5581-4535-8B13-3201E3199821@lilacglade.org>
Date: Tue, 07 Aug 2012 09:36:14 -0400
In-Reply-To: <841C1C01-5581-4535-8B13-3201E3199821@lilacglade.org> (Margaret Wasserman's message of "Mon, 6 Aug 2012 20:19:34 -0400")
Message-ID: <tslehnisu29.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: ietf@ietf.org, Richard Shockey <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, 07 Aug 2012 17:22:32 -0000

I'd strongly prefer the IETF to focus on going to places where we get
work done and where costs can be controlled.
I'd prefer to avoid tourist destinations to some extent even if they are
not more expensive, but definitely if they are.
I want to present a professional image to my clients and I want to go to
IETf meetings with people who are there to get work done, not to tour.

So, for US meetings I agree with the following:


>    [RS> ] +1 and no employer ever argued that going to Minneapolis was a
>    boondoggle.  The Hilton in Minneapolis  of all the IETF meetings I ve
>    attended has the most optimal layout of meeting rooms etc.
     
>    If we were to choose one place in the U.S. to meet, Minneapolis is the best
>    choice IMHO.  It's very reasonably priced, easy for many to get to and the
>    hotel has adequate space for us (even back when we had many more
>    attendees).  Personally, the weather is not critical to me, since I spend
>    the vast majority of my time in the hotel meeting rooms, so I'm very happy
>    if we meet there in March and November.   

From touch@isi.edu  Tue Aug  7 10:28:53 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3630421F86D1 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 10:28:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.489
X-Spam-Level: 
X-Spam-Status: No, score=-105.489 tagged_above=-999 required=5 tests=[AWL=1.110, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fECWlZLqYT5Z for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 10:28:52 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 5558E21F86D0 for <ietf@ietf.org>; Tue,  7 Aug 2012 10:28: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 q77HSIYw010963 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 7 Aug 2012 10:28:18 -0700 (PDT)
Message-ID: <50215032.7090800@isi.edu>
Date: Tue, 07 Aug 2012 10:28:18 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FE2715C.2090601@necom830.hpcl.titech.ac.jp> <4FF20DE7.2080208@isi.edu> <500654AB.7060500@necom830.hpcl.titech.ac.jp> <8F5CBE79-4540-4519-9F51-62B36686EE8C@isi.edu> <501C5C75.9040209@necom830.hpcl.titech.ac.jp> <501C6441.4000302@isi.edu> <5020C32A.4060907@necom830.hpcl.titech.ac.jp>
In-Reply-To: <5020C32A.4060907@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 17:28:53 -0000

Hi,

On 8/7/2012 12:26 AM, Masataka Ohta wrote:
> Joe Touch wrote:
> 
>>> RFC2765 specifies that translators can merely copy the
>>> low-order bits of the field.
>>
>> Yes, but this is not compatible with RFC791.
> 
> Then, which should we revice? RFC791, RFC2765 or both?

2765.

There is no useful way to revise 791 to make the text in 2765 correct.

> Without such a decision, there is no point to publish something
> based on RFC791 and is not compatible with RFC2765.

Sure there is - when IPv6 is not involved. That is the case for
ipv4-id-update. At best it makes things a little better for some cases
of IPv6-IPv4 translation - which can be noted - but it does not correct
for the failings of 2765, which are out of scope.

>> The case above occurs only when the source gets back a "packet too big"
>> message with a desired MTU less than 1280.
> 
> which means RFC2460 expects it.
> 
>> Note that this might never
>> happen, in which case there would never be any Fragment header.
> 
> If you can assume so, let's better assume that accidental ID
> match never happen and we all can be very happy.

My words were ambiguous; permit me to clarify:

An IPv6 source might never send packets larger than IPv4 can natively
handle - i.e., it could send packets 576 bytes or smaller. In that case,
the IPv6 source would never get an ICMP "too big" because they're not as
far as IPv4 is concerned. In that case, the IPv6 source would never
insert the Fragmentation Header.

That is the fundamental flaw in these IPv6 RFCs, but it is behavior that
is out of scope for an IPv4 source. My doc focuses on the behavior of
IPv4 sources.

>> However, even when it does happen, there is no instruction above about
>> how to construct the header that is compliant with RFC791.
> 
> That is the problem. That is, if you insist on RFC791 as is, not
> enough is specified on how to generate IPv6 ID.

Yes, but that does not affect an IPv4 source; it remains a problem, but
out of scope for this doc.

>> Further, the source might already be inserting the fragmentation header
>> (e.g., on a 2KB packet).
> 
> Thus, there can be only one way (the one in RFC2765) to map IPv6
> ID to IPv4 ID

I have no idea why the fantasy exists that IPv6 packets MUST be
translatable into IPv4 based on the existing specs. As specified in
RFC2460, this simply isn't the case.

Yes, this is a nice goal, but it would have required IPv6 hosts insert
16-bit IDs into *every* packet and make them just as unique as IPv4 does.

...
>> There's no instruction in how fragment headers
>> are constructed in general that complies with RFC791.
> 
> Is it a problem of RFC791 or RFC2460/2765?

RFC2460/2765.

>> Simply using the low 16 bits is not correct. In particular, RFC2460
>> suggests that its 32-bit counter can wrap once a minute, and that only
>> one such counter might be needed for an endpoint for all connections.
> 
> Never mind.
> 
> IPv6 specification is not self consistent at all.

Correct - not regarding translation to IPv4. That's what I've been
trying to say ;-)

>>> Or, are you saying RFC2460 and RFC2765 violate RFC791?
>>
>> Yes.
> 
> Then, as fixing RFC2460 is politically impossible, we must
> abandone IPv6 and live with IPv4 forever.

I didn't say we couldn't fix - or at least try to fix - this situation.
But it remains out of scope for this doc.

>> This document updates RFC791, but does not fix either RFC2460 or
>> RFC2765. This document does not make any statements about how IPv6
>> generates its IDs.
> 
> You draft says:
> 
>     This document updates the specification of the IPv4 ID field to more
>     closely reflect current practice, and to include considerations taken
>     into account during the specification of the similar field in IPv6.
> 
> but, "the specification of the similar field in IPv6" is, in
> your opinion, incomplete, let's finish it first, 

IPv6 is fine when it talks to IPv6 only. The goal is to make IPv4 work
in a similar way.

The goal is NOT to deal with translation. IPv6-IPv4 translation has two
directions - IPv4->IPv6 (which might be in scope for this doc, but isn't
really affected by the changes - we can add a statement on that) and
IP6->IPv4 (this doc similarly doesn't break that; if anything, it makes
it easier. it doesn't make it completely correct, though - there remain
problems that have nothing to do with the changes in this doc that need
to be addressed separately.

> only after
> which you can revise your draft "to include considerations
> taken into account during the specification of the similar
> field in IPv6."
> 
> More specifically, for example, the following statement in your draft:
> 
>     The latter case is relevant only for
>     IPv6 datagrams sent to IPv4 destinations to support subsequent
>     fragmentation after translation to IPv4.
> 
> is incorrect because NAT646 refer RFC2765.

That will be fixed, yes.

> For another example,
> 
>     Finally, the IPv6 ID field is
>     32 bits, and required unique per source/destination address pair for
>     IPv6,
> 
> is, in your opinion, violation of RFC791.

No; the violation occurs only when the lower 16 bits are masked off and
used by themselves by on-path translators. That has nothing to do with
the quoted text above.

>>> As I stated above, RFC2460 guarantees "a suitable Identification
>>> value" for IPv4 ID is there in IPv6 fragmentation ID.
>>
>> Not the way I interpret the text, especially because there are other
>> ways to generate IDs in RFC2460 that could be translated to IPv4
> 
> As I stated above, there can be only one way common to all the
> 6->4 translators. 

That's true.

> Or, different fragments with an IPv6 ID will
> have different IPv4 IDs.

Also true.

But neither of the above requires that IPv6 IDs must be easily
translatable into valid IPv4 addresses using the existing mechanism.

>>> Or, if you think RFC2460 does not mind ID uniqueness (of IPv4,
>>> at least) so much, RFC791 should not either.
>>
>> I think there are a lot of IETF documents that are not reviewed in the
>> correct context of existing standards. I don't think that applies to
>> this draft, though.
> 
> So, you are lucky that I have noticed the problem at the last call.

I am lucky that you are raising these issues for two reasons:

1) it provides an opportunity to explain some of the related issues in
this doc, as noted above

2) it provides a motivation to address ID issues for IPv6-IPv4
translation in a separate document, since they're out of scope for this one.

So yes, this has been helpful.

Joe

From anshumanpratap@gmail.com  Tue Aug  7 10:52:20 2012
Return-Path: <anshumanpratap@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CC3621F8709; Tue,  7 Aug 2012 10:52:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jX64Prgv0TC5; Tue,  7 Aug 2012 10:52:19 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7601821F8736; Tue,  7 Aug 2012 10:52:18 -0700 (PDT)
Received: by eekb45 with SMTP id b45so1219276eek.31 for <multiple recipients>; Tue, 07 Aug 2012 10:52:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-rim-org-msg-ref-id:return-receipt-to:disposition-notification-to :message-id:content-transfer-encoding:reply-to:x-priority:references :in-reply-to:sensitivity:importance:subject:to:from:date :content-type:mime-version; bh=/iHghwwvLwDFyxfRmQ24OdpAhn+0ukXDYza/+Gog3aE=; b=DY8JRI+OC9yEiXqfXDoL/x/nfEBC0oLhjzE+Zbibb+3QbwGAaVkqqs1clceowft3CD AkwJNmlV0Pv7hXzupRsRddKBG5GWdfHMHql6Sq8kJXrZasHNXNCoTkFZ8verbqGccIO4 UY1R9SuTQrALrWk/2BnDcRopUeDkmc8b+9KfxTZdhTVy0Ly+LjBjijMnIlM4Xu0WdNzo LlmR82OlDbhxEjT6KknXpfe4ns5x198s6h29rtQetLRvZzpqbgVAfOE8TKmhL+xg2zj3 d07qo7ghdW/yHNwGKJ9fpbcMI0O7vxgGekxc6p9W3HebLgfhlIxkNJ7+Phx5kiW7HEUD Tpeg==
Received: by 10.14.211.196 with SMTP id w44mr18562999eeo.19.1344361937664; Tue, 07 Aug 2012 10:52:17 -0700 (PDT)
Received: from 172.18.196.179 (bda-178-239-83-217.bis7.eu.blackberry.com. [178.239.83.217]) by mx.google.com with ESMTPS id a48sm18567151eeo.1.2012.08.07.10.52.16 (version=SSLv3 cipher=OTHER); Tue, 07 Aug 2012 10:52:17 -0700 (PDT)
X-rim-org-msg-ref-id: 1945895955
Message-ID: <1945895955-1344361933-cardhu_decombobulator_blackberry.rim.net-52336685-@b18.c3.bise7.blackberry>
Content-Transfer-Encoding: base64
X-Priority: Normal
References: <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <20120807010945.51851.qmail@joyce.lan> <CD5674C3CD99574EBA7432465FC13C1B22726A0BFE@DC-US1MBEX4.global.avaya.com> <20120807151103.GT53917@mail.yitter.info> <E4873516F3FC7547BCFE792C7D94039C023151B7@DEMUEXC013.nsn-intra.net>
In-Reply-To: <E4873516F3FC7547BCFE792C7D94039C023151B7@DEMUEXC013.nsn-intra.net>
Sensitivity: Normal
Importance: Normal
Subject: Re: So, where to repeat? (was: Re: management granularity)
To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>, ietf-bounces@ietf.org, "ext Andrew Sullivan" <ajs@anvilwalrusden.com>, ietf@ietf.org
From: "Anshuman Pratap Chaudhary" <anshumanpratap@gmail.com>
Date: Tue, 7 Aug 2012 17:52:14 +0000
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: anshumanpratap@gmail.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 17:52:20 -0000

V2h5IG5vdCBpbiBiZXJtdWRhIHRyaWFuZ2xlLSBpbm5vdmF0aW9uIGNvdXBsZWQgd2l0aCBhZHZl
bnR1cmUhISEgDQoNCg0KV2FybSBSZWdhcmRzLCANCg0KQW5zaHVtYW4gDQoNCg0KU2VudCBmcm9t
IG15IEJsYWNrQmVycnnCriBTbWFydHBob25lLCByZWdyZXQgdHlwbydzIQ0KDQoNCi0tLS0tT3Jp
Z2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiAiU3ByZWNoZXIsIE51cml0IChOU04gLSBJTC9Ib2Qg
SGFTaGFyb24pIiA8bnVyaXQuc3ByZWNoZXJAbnNuLmNvbT4NClNlbmRlcjogaWV0Zi1ib3VuY2Vz
QGlldGYub3JnDQpEYXRlOiBUdWUsIDcgQXVnIDIwMTIgMTc6Mjg6MzMgDQpUbzogZXh0IEFuZHJl
dyBTdWxsaXZhbjxhanNAYW52aWx3YWxydXNkZW4uY29tPjsgPGlldGZAaWV0Zi5vcmc+DQpTdWJq
ZWN0OiBSRTogU28sIHdoZXJlIHRvIHJlcGVhdD8gKHdhczogUmU6IG1hbmFnZW1lbnQgZ3JhbnVs
YXJpdHkpDQoNCldoeSB0aGUgc3VydmV5IHNob3VsZCBsaW1pdCBpdCB0byB0aGUgbGFzdCBmaXZl
IG1lZXRpbmdzLi4uDQpJbiB0aGUgbG9uZyBoaXN0b3J5IHdlIGV4cGVyaWVuY2VkIGFkZGl0aW9u
YWwgZ29vZCBwbGFjZXMuLi4uDQpTbyBtYXliZSB0aGUgc3VydmV5IHNob3VsZCBiZSBtb3JlIG9w
ZW4gYW5kIGxldCBlYWNoIGxpc3QgaGlzIDMtNSBmYXZvcmFibGUgcGxhY2VzIGJhc2VkIG9uIHRo
ZSBleHBlcmllbmNlIGZyb20gZWFybGllciBtZWV0aW5ncz8NCkJlc3QgcmVnYXJkcywNCk51cml0
DQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBpZXRmLWJvdW5jZXNAaWV0Zi5v
cmcgW21haWx0bzppZXRmLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBleHQgQW5kcmV3
IFN1bGxpdmFuDQpTZW50OiBUdWVzZGF5LCBBdWd1c3QgMDcsIDIwMTIgNjoxMSBQTQ0KVG86IGll
dGZAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBTbywgd2hlcmUgdG8gcmVwZWF0PyAod2FzOiBSZTog
bWFuYWdlbWVudCBncmFudWxhcml0eSkNCg0KRGVhciBjb2xsZWFndWVzLA0KDQpPbiBUdWUsIEF1
ZyAwNywgMjAxMiBhdCAxMDo0MjoxMEFNIC0wNDAwLCBXb3JsZXksIERhbGUgUiAoRGFsZSkgd3Jv
dGU6DQoNCj4gSSBleHBlY3QgdGhhdCBhIGNodW5rIG9mIHRoZSB2YXJpYW5jZSBoaW5nZXMgb24g
dGhlIHF1YWxpZmllcg0KDQpXaGlsZSB0aGUgdmFnYXJpZXMgb2YgYWlyIHRyYW5zcG9ydCBjb3N0
cyBmYXNjaW5hdGUgbWUsIEknbSBub3Qgc3VyZQ0KaG93IHRoZSBxdWVzdGlvbiBvZiB0aGUgY29z
dCBvZiBvbmUgcm91dGUgYXQgb25lIHRpbWUgZm9yIG9uZSBwZXJzb24NCmlzIGJyb2FkbHkgcmVs
ZXZhbnQuICBUaGUgYmFzaWMgZmFjdCBvZiBoYXZpbmcgbWVldGluZ3MgaW4gbXVsdGlwbGUNCnBs
YWNlcyAod2hpY2ggaXMgYSBkaXJlY3QgY29uc2VxdWVuY2Ugb2YgdHJ5aW5nIHRvIHNwcmVhZCB0
aGUgcGFpbiBvZg0KdHJhdmVsKSBpcyB0aGF0IHNvbWV0aW1lcyBlYWNoIG9mIHVzIHdpbGwgaGF2
ZSBhbiBleHBlbnNpdmUgZmxpZ2h0Lg0KKFRoaXMgaXMgdGhlIHNhbWUgcmVhc29uIHRoYXQgSSB0
aGluayBjb25mdXNpbmcgdGhlDQpzY2hlZHVsaW5nLWluLWFkdmFuY2UgcXVlc3Rpb24gd2l0aCB0
aGUgdmVudWUgcXVlc3Rpb24gaXMgYSBiYWQgaWRlYS4pDQoNCkRhdmUgQ3JvY2tlcidzIG9yaWdp
bmFsIHBvaW50IHdhcyB0aGF0IHNvbWUgdmVudWVzIGFyZSAiZ29vZCBlbm91Z2giDQp0aGF0IHlv
dSBjYW4gdHVuZSB0aGVtIHRvIGJlIGJldHRlci4gIEkgd2FzIHNjZXB0aWNhbCwgYnV0IHVwdGhy
ZWFkIHdlDQpoYWQgdHdvIHByb3Bvc2FsczogTWlubmVhcG9saXMgYW5kIFByYWd1ZS4gIE5vYm9k
eSBzZWVtcyB0byBoYXZlDQphcmd1ZWQgYWdhaW5zdC4NCg0KQW55IG90aGVycz8gIEF0IHRoZSBw
bGVuYXJ5IGluIFZhbmNvdXZlciB3ZSBoZWFyZCAiZ28gaGVyZSBhZ2FpbiIsIGFuZA0Kd2UndmUg
YWxyZWFkeSBkZWNpZGVkIHRvIHJ1biB0aGF0IHRyaWFsIGluIGFueSBjYXNlLiAgVGhhdCBtYWtl
cw0KdGhyZWUuICBBbHNvLCBtYW55IHBlb3BsZSBleHByZXNzZWQgc2F0aXNmYWN0aW9uIGluIFF1
w6liZWMuDQoNClZhbmNvdXZlcidzIFBhY2lmaWMgbG9jYXRpb24gbm90d2l0aHN0YW5kaW5nLCB0
aGlzIGFwcGVhcnMgdG8gbWUgdG8NCnN1Z2dlc3QgdGhhdCB3ZSBoYXZlIG9uZSAicmVwZWF0IiBs
b2NhdGlvbiBpbiBFdXJvcGUgYW5kIHR3byBpbiBOb3J0aA0KQW1lcmljYS4gIFRoaXMgbGVhdmVz
IHVzIHJhdGhlciB0aGluIGluIEFzaWEtUGFjaWZpYy4gIEkgcmVjYWxsIHBlb3BsZQ0Kc2F5aW5n
IGdvb2QgdGhpbmdzIGFib3V0IFRhaXBlaS4gIA0KDQpUaGUgcG9pbnQgb2YgYWxsIHRoaXMsIGlu
IGNhc2UgaXQgaXNuJ3QgY2xlYXIsIGlzIHRvIGFzayB0byBhZGQgYQ0KcXVlc3Rpb24gdG8gdGhl
IHBvc3QtbWVldGluZyBzdXJ2ZXkgYWJvdXQgc3BlY2lmaWMgdmVudWVzIGFuZCB3aGV0aGVyDQpm
dXR1cmUgbWVldGluZ3Mgc2hvdWxkIHRyeSB0byByZXR1cm4gdG8gdGhlbS4gIEdpdmVuIEFycm93
IHBhcmFkb3hlcw0KYW5kIHNvIG9uLCBJIHRoaW5rIGEgc2hvcnQgbGlzdCB3aXRoICJ5ZXMvbm8i
IGZvciBlYWNoIGlzIG11Y2ggbW9yZQ0KbGlrZWx5IHRvIHlpZWxkIHVzZWZ1bCBhZ2dyZWdhdGUg
cmVzdWx0cyB0aGFuIGEgYmlnIGxpc3Qgb3IgYSByYW5rDQpvcmRlci4gIFNvLCBJJ2QgbGlrZSB0
byBzdWdnZXN0IHRoZSBmb2xsb3dpbmcgc3VydmV5IGl0ZW0gYmUgYWRkZWQgdG8NCnRoZSBwb3N0
LVZhbmNvdXZlciBzdXJ2ZXk6DQoNCiAgICBEbyB5b3Ugc3VwcG9ydCB0aGUgSUVURiByZXR1cm5p
bmcgdG8gdGhlIHZlcnkgc2FtZSB2ZW51ZSAoaG90ZWwNCiAgICBhbmQgbWVldGluZyBmYWNpbGl0
aWVzKSBhcyB0aGUgbGFzdCB0aW1lIGluIHRoZSBmb2xsb3dpbmcNCiAgICBtZWV0aW5nczoNCg0K
ICAgIC0gSUVURiA4NCwgVmFuY291dmVyIChIeWF0dCkgW1l8Tl0NCiAgICAtIElFVEYgODIsIFRh
aXBlaSAoSHlhdHQgYW5kIFRJQ0MpIFtZfE5dDQogICAgLSBJRVRGIDgxLCBRdcOpYmVjIChIaWx0
b24pIFtZfE5dDQogICAgLSBJRVRGIDgwLCBQcmFndWUgKEhpbHRvbikgW1l8Tl0NCiAgICAtIElF
VEYgNzMsIE1pbm5lYXBvbGlzIChIaWx0b24pIFtZfE5dDQoNCkkgc3VwcG9zZSB3ZSBjb3VsZCBq
dXN0IGFkZCBldmVyeSB2ZW51ZSBmcm9tIHRoZSBsYXN0IF9uXyB5ZWFycywgYnV0DQpJJ20gcmVs
dWN0YW50IHRvIGRvIHRoYXQgYmVjYXVzZSBJIHRoaW5rIGl0IHdpbGwgZ2l2ZSB0b28gbWFueQ0K
b3B0aW9ucy4gDQoNCkkgc2VlbSB0byByZWNhbGwgYXQgbGVhc3Qgc29tZSBvZiB0aGUgcHJldmlv
dXMgcG9zdC1tZWV0aW5nIHN1cnZleXMNCmFza2luZyB0aGlzIHF1ZXN0aW9uIGFib3V0IHRoZSB2
ZW51ZSB3ZSB3ZXJlIGp1c3QgaW4uICBJIHRoaW5rIGl0DQp3b3VsZCBiZSBpbnRlcmVzdGluZywg
aG93ZXZlciwgdG8gcGljayBhIGZldyBwb3B1bGFyIHZlbnVlcyBhbmQgdHJhY2sNCnRoZWlyIHJh
dGluZ3Mgb3ZlciB0aW1lLg0KDQpUaGlzIGlzIG1lcmVseSBhIHN1Z2dlc3Rpb24gZm9yIHRoZSBJ
QU9DLCBhbmQgSSBob3BlIHRoZXkgZmVlbCBmcmVlIHRvDQp0cmVhdCBpdCBhcyBhIGJhZCBpZGVh
LiAgKEl0J3MgYWxzbyB0aGUgbGFzdCBJIGhhdmUgdG8gc2F5IG9uIHRoaXMNCnRvcGljLCBzaW5j
ZSBJJ3ZlIHVzZWQgdXAgbXkgYml0IHF1b3RhLikNCg0KQmVzdCwNCg0KQQ0KDQotLSANCkFuZHJl
dyBTdWxsaXZhbg0KYWpzQGFudmlsd2FscnVzZGVuLmNvbQ0K


From jason_livingood@cable.comcast.com  Tue Aug  7 12:00:57 2012
Return-Path: <jason_livingood@cable.comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79E8D21F8720; Tue,  7 Aug 2012 12:00:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.671
X-Spam-Level: 
X-Spam-Status: No, score=-103.671 tagged_above=-999 required=5 tests=[AWL=1.560, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1tue8sJQxvVy; Tue,  7 Aug 2012 12:00:56 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id 28CD611E80FC; Tue,  7 Aug 2012 12:00:31 -0700 (PDT)
Received: from ([24.40.56.115]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.28395548; Tue, 07 Aug 2012 12:40:53 -0600
Received: from PACDCEXMB01.cable.comcast.com ([169.254.1.168]) by PACDCEXHUB02.cable.comcast.com ([fe80::492e:3fa1:c2ad:e04e%13]) with mapi id 14.02.0309.002; Tue, 7 Aug 2012 15:00:25 -0400
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: "anshumanpratap@gmail.com" <anshumanpratap@gmail.com>, "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>, "ietf-bounces@ietf.org" <ietf-bounces@ietf.org>, ext Andrew Sullivan <ajs@anvilwalrusden.com>,  "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: So, where to repeat? (was: Re: management granularity)
Thread-Topic: So, where to repeat? (was: Re: management granularity)
Thread-Index: AQHNdDlsH4mPHmQ940SebPH4CPOMHZdOsEEAgAAIEwCAAATjgIAAKCUA///QAYA=
Date: Tue, 7 Aug 2012 19:00:25 +0000
Message-ID: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com>
In-Reply-To: <1945895955-1344361933-cardhu_decombobulator_blackberry.rim.net-52336685-@b18.c3.bise7.blackberry>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.2.120421
x-originating-ip: [24.40.56.165]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <CB2F980E21F55E448FF811993901AAA5@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 19:00:58 -0000

BTW, if anyone finds the venue question extremely compelling / interesting
-- consider seeking a spot on the IAOC during the next nominating period.

- Jason


From dhc@dcrocker.net  Tue Aug  7 12:18:06 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76F2721F8705 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 12:18:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.589
X-Spam-Level: 
X-Spam-Status: No, score=-6.589 tagged_above=-999 required=5 tests=[AWL=0.010,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zqSowjj6d7nU for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 12:18:05 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D491F21F8703 for <ietf@ietf.org>; Tue,  7 Aug 2012 12:18:05 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q77JI5xd014599 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Tue, 7 Aug 2012 12:18:05 -0700
Message-ID: <502169E9.9020009@dcrocker.net>
Date: Tue, 07 Aug 2012 12:18:01 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: So, where to repeat? (was: Re: management granularity)
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com>
In-Reply-To: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 07 Aug 2012 12:18:05 -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, 07 Aug 2012 19:18:06 -0000

> BTW, if anyone finds the venue question extremely compelling / interesting
> -- consider seeking a spot on the IAOC during the next nominating period.


Yes, please do.  Frankly, I'd prefer there be competition; it creates 
healthy debate within nomcom and might even improve community awareness 
of IAOC functions.

The one caveat that I'll offer is that the IAOC has a range of topics 
beyond meeting venue -- budget, tools development, IT ops, legal, IPR, etc.:

    http://iaoc.ietf.org/

They all need to be covered by all the IAOC members.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From dougb@dougbarton.us  Tue Aug  7 13:01:57 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A229121F86C8 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 13:01: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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TtqgnqzFZ8oa for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 13:01:57 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 6011B21F854D for <ietf@ietf.org>; Tue,  7 Aug 2012 13:01:52 -0700 (PDT)
Received: (qmail 31285 invoked by uid 399); 7 Aug 2012 20:01:41 -0000
Received: from unknown (HELO opti.dougb.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 7 Aug 2012 20:01:41 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <5021742A.70804@dougbarton.us>
Date: Tue, 07 Aug 2012 13:01:46 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120728 Thunderbird/14.0
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: ITU-T Dubai Meeting
References: <20120807074601.23F871A125@ld9781.wdf.sap.corp>
In-Reply-To: <20120807074601.23F871A125@ld9781.wdf.sap.corp>
X-Enigmail-Version: 1.4.2
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, 07 Aug 2012 20:01:57 -0000

On 08/07/2012 00:46, Martin Rex wrote:
> IPv6 PA prefixes result in that awkward renumbering.
> Avoiding the renumbering implies provider independent
> network prefix.

ULA on the inside + https://tools.ietf.org/html/rfc6296

-- 

    I am only one, but I am one.  I cannot do everything, but I can do
    something.  And I will not let what I cannot do interfere with what
    I can do.
			-- Edward Everett Hale, (1822 - 1909)

From tjc@ecs.soton.ac.uk  Tue Aug  7 14:56:36 2012
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 727DC11E80F0 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 14:56:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.735
X-Spam-Level: 
X-Spam-Status: No, score=-1.735 tagged_above=-999 required=5 tests=[AWL=-0.532, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Iko1e5kUEvEx for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 14:56:36 -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 A196211E80D2 for <ietf@ietf.org>; Tue,  7 Aug 2012 14:56:35 -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 q77LuXIE016397 for <ietf@ietf.org>; Tue, 7 Aug 2012 22:56:33 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk q77LuXIE016397
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1344376593; bh=Hx90psmDcP/5xa3BuarHsVEUExU=; h=Subject:References:From:In-Reply-To:Date:To:Mime-Version; b=rAU7yoMFpB4loVzZINDLe5gNcnJZWFuMzlp5kc3Pp8XFSYFQ7mmzmu98dCHbcWHbv pdgKQ9jUosfVa8dhYdnuWH86g7XAWSxc9UyAB4YpVCCFetghIOGeW4L83Bc1UyqtKC qxLAQ1hYRnOIBOv0b0NCk/Qazx4q24DI3B+9jIzM=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id o76MuX0430609196s0 ret-id none; Tue, 07 Aug 2012 22:56:33 +0100
Received: from [192.168.1.101] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id q77LtBC6028976 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Tue, 7 Aug 2012 22:55:12 +0100
Subject: Re: So, where to repeat? (was: Re: management granularity)
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk>
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: text/plain; charset=us-ascii
X-Mailer: iPad Mail (9B206)
In-Reply-To: <502169E9.9020009@dcrocker.net>
Message-ID: <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk>
Date: Tue, 7 Aug 2012 22:55:20 +0100
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=o76MuX043060919600; tid=o76MuX0430609196s0; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: q77LuXIE016397
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 21:56:36 -0000

Hi,

My top three repeat venues would be Prague, Minneapolis and Vancouver.  Grea=
t meeting venues, with everything you need nearby.

My least favoured venues have been Dublin, Vienna and Maastricht.

Of course, you have to experiment to find good repeat venues...

Tim=

From steve@shinkuro.com  Tue Aug  7 15:01:31 2012
Return-Path: <steve@shinkuro.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5527C11E80F2 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 15:01:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.47
X-Spam-Level: 
X-Spam-Status: No, score=-1.47 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HELO_EQ_DSL=1.129]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4+0Za+XOQsv6 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 15:01:30 -0700 (PDT)
Received: from execdsl.com (remote.shinkuro.com [50.56.68.178]) by ietfa.amsl.com (Postfix) with ESMTP id A4BD411E80F1 for <ietf@ietf.org>; Tue,  7 Aug 2012 15:01:30 -0700 (PDT)
Received: from [70.88.139.89] (account steve@shinkuro.com HELO [192.168.168.160]) by execdsl.com (CommuniGate Pro SMTP 5.1.16) with ESMTPSA id 20735609; Tue, 07 Aug 2012 22:02:42 +0000
Subject: Re: So, where to repeat? (was: Re: management granularity)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Steve Crocker <steve@shinkuro.com>
In-Reply-To: <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk>
Date: Tue, 7 Aug 2012 18:01:28 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk>
To: Tim Chown <tjc@ecs.soton.ac.uk>
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, 07 Aug 2012 22:01:31 -0000

I'll bet Dublin would be rated higher if the meetings had been downtown. =
 Same for Vienna.

Steve
=20
On Aug 7, 2012, at 5:55 PM, Tim Chown wrote:

> Hi,
>=20
> My top three repeat venues would be Prague, Minneapolis and Vancouver. =
 Great meeting venues, with everything you need nearby.
>=20
> My least favoured venues have been Dublin, Vienna and Maastricht.
>=20
> Of course, you have to experiment to find good repeat venues...
>=20
> Tim


From ietf@meetecho.com  Tue Aug  7 15:37:15 2012
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 1E39D21F85DB for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 15:37:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.241
X-Spam-Level: *
X-Spam-Status: No, score=1.241 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_BL_SPAMCOP_NET=1.96]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zqFQECFPYP4s for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 15:37:14 -0700 (PDT)
Received: from smtplq04.aruba.it (smtplqs-out18.aruba.it [62.149.158.58]) by ietfa.amsl.com (Postfix) with SMTP id F370521F85C6 for <ietf@ietf.org>; Tue,  7 Aug 2012 15:37:13 -0700 (PDT)
Received: (qmail 8650 invoked by uid 89); 7 Aug 2012 22:37:11 -0000
Received: from unknown (HELO smtp2.aruba.it) (62.149.158.222) by smtplq04.aruba.it with SMTP; 7 Aug 2012 22:37:11 -0000
Received: (qmail 29980 invoked by uid 89); 7 Aug 2012 22:37:11 -0000
Received: from unknown (HELO ?192.168.1.154?) (alex@meetecho.com@87.11.150.210) by smtp2.ad.aruba.it with ESMTPA; 7 Aug 2012 22:37:11 -0000
Message-ID: <50219888.9000004@meetecho.com>
Date: Wed, 08 Aug 2012 00:36:56 +0200
From: Meetecho IETF support <ietf@meetecho.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Meetecho session recording available
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: smtplq04.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: Tue, 07 Aug 2012 22:37:15 -0000

Dear all,

the full recording (synchronized video, audio, slides and jabber room)
of the Administration and Operations Plenary session at IETF-84 is 
available.

You can watch it by accessing the following URL:
http://ietf84.conf.meetecho.com/index.php/Recorded_Sessions#IETF84_ADMIN_PLENARY

For the chair(s): please feel free to put the link to the recording in 
the minutes, if you think this might be useful.

In case of problems with the playout, just drop an e-mail to 
team@meetecho.com.

Cheers,
the Meetecho team

-- 
Meetecho s.r.l.
Web Conferencing and Collaboration Tools
www.meetecho.com

From tjc@ecs.soton.ac.uk  Tue Aug  7 16:18:34 2012
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12FBC21F861D for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 16:18:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level: 
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[AWL=-0.456, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F1K1I6PNwFYu for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 16:18: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 6BC2A21F855E for <ietf@ietf.org>; Tue,  7 Aug 2012 16:18:32 -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 q77NITeP029330 for <ietf@ietf.org>; Wed, 8 Aug 2012 00:18:29 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk q77NITeP029330
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1344381509; bh=UML/1DpaGc9fdM4PcPSEy/oSabg=; h=Subject:References:From:In-Reply-To:Date:To:Mime-Version; b=oP5U3wykBaCKECLMpafAfeNXvnWfZ4IsTM8Ei0SbrhM9/9MhY2kBoMqlZJOx5KGXy o9CwFCxBdiweIhVYfhZk5mpY0nOtJ29jZO9HhTslV3QMRI8bE7cI2ChfG/BP5s3oMt u8BsfmR+jLP506dnq/K/bjDIORJlr7mw5Z1q+K14=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id o770IY0430609415XJ ret-id none; Wed, 08 Aug 2012 00:18:29 +0100
Received: from [192.168.1.101] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id q77NH9Yn011552 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Wed, 8 Aug 2012 00:17:10 +0100
Subject: Re: So, where to repeat? (was: Re: management granularity)
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <D48A7250-2C4D-479B-A53C-B075F0318497@ecs.soton.ac.uk>
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: text/plain; charset=us-ascii
X-Mailer: iPad Mail (9B206)
In-Reply-To: <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com>
Message-ID: <EMEW3|259b87edcd936ca1e1490039dd285e00o770IY03tjc|ecs.soton.ac.uk|D48A7250-2C4D-479B-A53C-B075F0318497@ecs.soton.ac.uk>
Date: Wed, 8 Aug 2012 00:17:18 +0100
To: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=o770IY043060941500; tid=o770IY0430609415XJ; 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: q77NITeP029330
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 23:18:34 -0000

On 7 Aug 2012, at 23:01, Steve Crocker <steve@shinkuro.com> wrote:

> I'll bet Dublin would be rated higher if the meetings had been downtown.  S=
ame for Vienna.

Quite possibly, but a rating is based on a venue, not a city.  Dublin is a g=
reat city.  An out of town golf resort is not a great venue.

Tim

> On Aug 7, 2012, at 5:55 PM, Tim Chown wrote:
>=20
>> Hi,
>>=20
>> My top three repeat venues would be Prague, Minneapolis and Vancouver.  G=
reat meeting venues, with everything you need nearby.
>>=20
>> My least favoured venues have been Dublin, Vienna and Maastricht.
>>=20
>> Of course, you have to experiment to find good repeat venues...
>>=20
>> Tim
>=20

From ole@cisco.com  Tue Aug  7 16:30:35 2012
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37C8321F84F6 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 16:30:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.562
X-Spam-Level: 
X-Spam-Status: No, score=-110.562 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EoFlMIgD2--F for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 16:30:34 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 45EB221F84EE for <ietf@ietf.org>; Tue,  7 Aug 2012 16:30:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=537; q=dns/txt; s=iport; t=1344382234; x=1345591834; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=WdMWGEYgXHI3s0t8mxHad4EWSpyAJIgl2V0UEnevK9U=; b=T/UpEYV8I4DAWOCklICicB8Umdkw+1bun7wkMTA4ncrH12DcdWc4x4g5 x6jwegspiiTgGONjHn0anF+VgmHsaoVz1mbbUUzj8cy2jSbPpzRIzTayb g2i6okZqSzgczpuNtgETjozZRbPrRbm3VabipYZIZKXSdGpjl/6ahyu8q Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgwFAGWkIVCrRDoJ/2dsb2JhbABFDoUntDGBB4IgAQEBAwESAQIlPwULCw4KLlcGExoIh2UFDJpfg0gQnQaLD4ZgA4hNklaIS4EEYoImWQ
X-IronPort-AV: E=Sophos;i="4.77,729,1336348800"; d="scan'208";a="54377000"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-2.cisco.com with ESMTP; 07 Aug 2012 23:30:33 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q77NUXUK022584 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Aug 2012 23:30:33 GMT
Date: Tue, 7 Aug 2012 16:30:33 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: So, where to repeat? (was: Re: management granularity)
In-Reply-To: <EMEW3|259b87edcd936ca1e1490039dd285e00o770IY03tjc|ecs.soton.ac.uk|D48A7250-2C4D-479B-A53C-B075F0318497@ecs.soton.ac.uk>
Message-ID: <alpine.OSX.2.01.1208071629480.18204@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <D48A7250-2C4D-479B-A53C-B075F0318497@ecs.soton.ac.uk> <EMEW3|259b87edcd936ca1e1490039dd285e00o770IY03tjc|ecs.soton.ac.uk|D48A7250-2C4D-479B-A53C-B075F0318497@ecs.soton.ac.uk>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 23:30:35 -0000

On Tue, 7 Aug 2012, Tim Chown wrote:

> On 7 Aug 2012, at 23:01, Steve Crocker <steve@shinkuro.com> wrote:
> 
> > I'll bet Dublin would be rated higher if the meetings had been 
> > downtown.  Same for Vienna.
> 
> Quite possibly, but a rating is based on a venue, not a city.  
> Dublin is a great city.  An out of town golf resort is not a great 
> venue.
> 
> Tim

Right, and I don't think we will be going back to CityWest ever:

http://www.herald.ie/news/creditors-fury-at-citywest-showdown-2489018.html

Ole
 

From richard@shockey.us  Tue Aug  7 16:34:11 2012
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 A569411E8104 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 16:34:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.973
X-Spam-Level: 
X-Spam-Status: No, score=-99.973 tagged_above=-999 required=5 tests=[AWL=0.522, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9SWma7Eip0Hs for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 16:34:11 -0700 (PDT)
Received: from oproxy8-pub.bluehost.com (oproxy8.bluehost.com [IPv6:2605:dc00:100:2::a8]) by ietfa.amsl.com (Postfix) with SMTP id 03AE011E8103 for <ietf@ietf.org>; Tue,  7 Aug 2012 16:34:10 -0700 (PDT)
Received: (qmail 20327 invoked by uid 0); 7 Aug 2012 23:34:05 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy8.bluehost.com with SMTP; 7 Aug 2012 23:34:05 -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:To:From; bh=XrAv3K4Ajwmo5okqt8gGLc1HjyIkz85vLo9J5P87+FI=;  b=AK2WxzvA3LVZ2+bYNVnWEYQQjmOAQfy+Wko4neATt+OcutrV6W0dmrTyiZWUG2xp70dN6UsGfNas+4aSLgwAwo/8ssy1uSHBKBxyLuRMJY2w9Z62tIsJPfhrmuj4vs7p;
Received: from [71.191.243.130] (port=55464 helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.76) (envelope-from <richard@shockey.us>) id 1SytHo-0005n5-Df; Tue, 07 Aug 2012 17:34:04 -0600
From: "Richard Shockey" <richard@shockey.us>
To: "'Steve Crocker'" <steve@shinkuro.com>, <ietf@ietf.org>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com>	<502169E9.9020009@dcrocker.net>	<AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk>	<EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com>
In-Reply-To: <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com>
Subject: RE: So, where to repeat? (was: Re: management granularity)
Date: Tue, 7 Aug 2012 19:34:02 -0400
Message-ID: <01af01cd74f5$217e5770$647b0650$@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: Ac106DQp2r0tsdIiRxCG3+4lQPsX1wAC8QhA
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 71.191.243.130 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, 07 Aug 2012 23:34:12 -0000

+1  Prague was excellent .. I actually liked Quebec City but connections
were awful.  

So where in Asia?  You have to have the 3.  

Is this discussion is really about are we the Internet Entertainment and
Travel Facility??   Some of us have employers some of us do not.  Is this
about "diversity" or getting the work done. 

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Steve Crocker
Sent: Tuesday, August 07, 2012 6:01 PM
To: Tim Chown
Cc: ietf@ietf.org
Subject: Re: So, where to repeat? (was: Re: management granularity)

I'll bet Dublin would be rated higher if the meetings had been downtown.
Same for Vienna.

Steve
 
On Aug 7, 2012, at 5:55 PM, Tim Chown wrote:

> Hi,
> 
> My top three repeat venues would be Prague, Minneapolis and Vancouver.
Great meeting venues, with everything you need nearby.
> 
> My least favoured venues have been Dublin, Vienna and Maastricht.
> 
> Of course, you have to experiment to find good repeat venues...
> 
> Tim


From stephen.farrell@cs.tcd.ie  Tue Aug  7 16:34:39 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 935C111E8109 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 16:34:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IpuxmWdFE4Ky for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 16:34:32 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 7D1E711E810C for <ietf@ietf.org>; Tue,  7 Aug 2012 16:34:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 7291B17150A; Wed,  8 Aug 2012 00:34:29 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1344382469; bh=O82EtavcvcU4o7 BtJ4/BizT49RGTI0EOOPZrH0Oc6rI=; b=VtPhgSVAmt3hxsIY4/sGIRaQdmLwOv naOs2w3t5TVkuHSqpZANNsHQ5N4uf2EBPi5d3bQ3FI5SLIP1kOl2bGuCntTgwyq/ odLJzE5z9xuYQlrXCAdsevzXsA0EvJbFm0sl2AZMGjOwFhFEpCtaAPw8zAbj5+q2 b62LcG6EvsyWVyrqJ0xWfmN3JOvywTZQfuGea8IOm22O4clZ28dSB1msYHm8J9Qp e4eaIRuOcp0e3o5o8LFsgH61Di2QPMkPrAImxsVzknHXSeTKa3ly9eWgEMBFbyCi XKiMzwqgijDxfSZSKhd4PfBQocoj8bOTe0V2PDjWN8pFtpmmzbcz0/dw==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id m-5xDKdF+jqZ; Wed,  8 Aug 2012 00:34:29 +0100 (IST)
Received: from [10.87.48.8] (unknown [86.42.30.15]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id C0CD8171509; Wed,  8 Aug 2012 00:34:27 +0100 (IST)
Message-ID: <5021A603.4050409@cs.tcd.ie>
Date: Wed, 08 Aug 2012 00:34:27 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: Ole Jacobsen <ole@cisco.com>
Subject: Re: So, where to repeat? (was: Re: management granularity)
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <D48A7250-2C4D-479B-A53C-B075F0318497@ecs.soton.ac.uk> <EMEW3|259b87edcd936ca1e1490039dd285e00o770IY03tjc|ecs.soton.ac.uk|D48A7250-2C4D-479B-A53C-B075F0318497@ecs.soton.ac.uk> <alpine.OSX.2.01.1208071629480.18204@173-11-110-132-sfba.hfc.comcastbusiness.net>
In-Reply-To: <alpine.OSX.2.01.1208071629480.18204@173-11-110-132-sfba.hfc.comcastbusiness.net>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 23:34:39 -0000

On 08/08/2012 12:30 AM, Ole Jacobsen wrote:
> 
> On Tue, 7 Aug 2012, Tim Chown wrote:
> 
>> On 7 Aug 2012, at 23:01, Steve Crocker <steve@shinkuro.com> wrote:
>>
>>> I'll bet Dublin would be rated higher if the meetings had been 
>>> downtown.  Same for Vienna.
>>
>> Quite possibly, but a rating is based on a venue, not a city.  
>> Dublin is a great city.  An out of town golf resort is not a great 
>> venue.
>>
>> Tim
> 
> Right, and I don't think we will be going back to CityWest ever:

So I agree with that. If a feasible venue actually in Dublin
turns up I'll be sure to let Ray/IAOC/site-visit folks know.

> http://www.herald.ie/news/creditors-fury-at-citywest-showdown-2489018.html

However the place is still open. Wonders of business I guess;-)

S.




> 
> Ole
>  
> 
> 

From johnl@iecc.com  Tue Aug  7 17:29:57 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDBE021F8610 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 17:29:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.157
X-Spam-Level: 
X-Spam-Status: No, score=-111.157 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8zdS65LP3zp1 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 17:29:57 -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 1388521F860B for <ietf@ietf.org>; Tue,  7 Aug 2012 17:29:56 -0700 (PDT)
Received: (qmail 22560 invoked from network); 8 Aug 2012 00:29:56 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 8 Aug 2012 00:29:56 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5021b304.xn--i8sz2z.k1208; i=johnl@user.iecc.com; bh=kk2OkWt4COxdufjBo1WEeWDM9xIwLRkfZXDkwi0dfAs=; b=bAx6KXBtPFlA/tZ0O68knoxhkTkcqYzYbn92rc9HvLlDbCIm8c1yOUGVBKK0q0Whgr+9BXyGHG3obpOg2D86cqDsD3zWaQtN5mC5No8sm0Jwhu5OTiNbX3nujpBpmuvAgMFrn2WDM+3UZBdkmVd936a1ZesO81WZ4EPaYjQ33Uc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5021b304.xn--i8sz2z.k1208; olt=johnl@user.iecc.com; bh=kk2OkWt4COxdufjBo1WEeWDM9xIwLRkfZXDkwi0dfAs=; b=pPzwVpZMaHmWfu3JM0W3zg5PyjMd4ez2ZnCJHXycYd6RCsFwcJG2QLrD7brlkyMsU1mzdAK+Q2SkqfUwDc1RugzxIeTQwKpSqEO+YsZ5znkGWRmF9WPoX8y8uc/PBECkYCZRxxC0xHXx4uwt6MhdYu0opgYYM/ybThaJOMYHTwU=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 8 Aug 2012 00:29:34 -0000
Message-ID: <20120808002934.12325.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: So, where to repeat? (was: Re: management granularity)
In-Reply-To: <5021A603.4050409@cs.tcd.ie>
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, 08 Aug 2012 00:29:58 -0000

>So I agree with that. If a feasible venue actually in Dublin
>turns up I'll be sure to let Ray/IAOC/site-visit folks know.

The Burlington hotel claims that they can host a 1500 person meeting.

MAAWG met there in 2007 and it worked well for us, although that was
a somewhat smaller meeting.

R's,
John

From dhc@dcrocker.net  Tue Aug  7 19:20:32 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0527E21F84F1 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 19:20:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.59
X-Spam-Level: 
X-Spam-Status: No, score=-6.59 tagged_above=-999 required=5 tests=[AWL=0.009,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cEHDQKMcBNq3 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 19:20:31 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 008B421F84EC for <ietf@ietf.org>; Tue,  7 Aug 2012 19:20:30 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q782KTYM019913 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 7 Aug 2012 19:20:30 -0700
Message-ID: <5021CCE8.6020106@dcrocker.net>
Date: Tue, 07 Aug 2012 19:20:24 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: So, where to repeat? (was: Re: management granularity)
References: <20120808002934.12325.qmail@joyce.lan>
In-Reply-To: <20120808002934.12325.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 07 Aug 2012 19:20:30 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 02:20:32 -0000

On 8/7/2012 5:29 PM, John Levine wrote:
>> So I agree with that. If a feasible venue actually in Dublin
>> turns up I'll be sure to let Ray/IAOC/site-visit folks know.
>
> The Burlington hotel claims that they can host a 1500 person meeting.


Yeah, it's exactly that easy to choose a venue.  A single number does it.[1]

not.

Folks, the IETF actually has a rather constraining set of requirements 
and the secretariat has to put in quite a bit of effort to qualify 
venues.  Many places that are otherwise just dandy can't deal with these 
complexities.  For example, we run quite a few parallel meetings that 
are large.

Take a careful look at the range of serious complaints that get lodged 
about venues and you can start to glean the requirements list.  (I said 
serious.  That is, complaints that get significant traction from the 
community.)

Perhaps the Burlington really can accommodate us, but given the rate at 
which places get rejected, the expectation ain't great.  That doesn't 
mean reject it out of hand, of course.


d/


[1] For the places that we do go to and that we like, I've no idea what 
single capacity number they typically cite, but I predict it's more like 
double our actual size, if not triple.

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From dhc@dcrocker.net  Tue Aug  7 19:24:37 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C98011E8113 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 19:24:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.59
X-Spam-Level: 
X-Spam-Status: No, score=-6.59 tagged_above=-999 required=5 tests=[AWL=0.009,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oP-8nCAGmpwX for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 19:24:36 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 73BAA11E80E9 for <ietf@ietf.org>; Tue,  7 Aug 2012 19:24:36 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q782OZZl019961 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 7 Aug 2012 19:24:36 -0700
Message-ID: <5021CDDE.8060207@dcrocker.net>
Date: Tue, 07 Aug 2012 19:24:30 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Richard Shockey <richard@shockey.us>
Subject: Re: So, where to repeat? (was: Re: management granularity)
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com>	<502169E9.9020009@dcrocker.net>	<AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk>	<EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us>
In-Reply-To: <01af01cd74f5$217e5770$647b0650$@us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 07 Aug 2012 19:24:36 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 02:24:37 -0000

On 8/7/2012 4:34 PM, Richard Shockey wrote:
> +1  Prague was excellent .. I actually liked Quebec City but connections
> were awful.

I haven't seen anyone post negative comments about Prague in this 
thread.  By way of probing, I'll ask for them.  For example, do folks 
who live outside of that region not care about the additional hop of 
travel to get to it?


> So where in Asia?  You have to have the 3.

Asia is east of Prague.

sigh.  sorry.

As Bob has noted from the IAOC presentation, Asia is actually proving a 
challenge.  Due to language and culture challenges, we seem to really 
need a host.  And there there are price problems we keep hitting.


> Is this discussion is really about are we the Internet Entertainment and
> Travel Facility??   Some of us have employers some of us do not.  Is this
> about "diversity" or getting the work done.

While it's not automatic that these are mutually exclusive, I sometimes 
find it confusing to discern the criteria that participants apply.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From melinda.shore@gmail.com  Tue Aug  7 19:42:13 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A082411E80F1 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 19:42:13 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VyFql14OJiGQ for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 19:42:12 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id A0F3811E80EE for <ietf@ietf.org>; Tue,  7 Aug 2012 19:42:12 -0700 (PDT)
Received: by pbbrr4 with SMTP id rr4so639709pbb.31 for <ietf@ietf.org>; Tue, 07 Aug 2012 19:42:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=MYOaUL5XPv41gc0tx/9k3Jg81oUfa38ErrbFvyqhEec=; b=xEdCueuJTKWzHtKq9oq3KI+IUiNVjfI7BG0+ETTG6JKo9SINdzwemnknAZvlivzOZa H72mJKFBUCoJBL57ITE6fWFzxwMe7E+H+TWqGyjU3Ko2reJrdmO8eetTn8wUezw9WPnf GJ8QPjf1q/I2Cq1QhljGyEqkArBAM6S2Ay+u0Th53kuZ89q2w/hEBYPji2H0E/1ToVfB OxdOMIULggrmXB0txdw2TYbKsCt7E9VhW3iwbKMJFnxHyq2b2mAXIaxdRHUKJ1JTRKIv L5r7HVBwx3ZPx20Cpir+ZKbLzoQtvUdxQEagWQBW5O4xUa1q3NyyJhEeanZjx9Rb+Zda 6d3A==
Received: by 10.68.200.138 with SMTP id js10mr33020717pbc.23.1344393732439; Tue, 07 Aug 2012 19:42:12 -0700 (PDT)
Received: from spandex.local (66-230-81-165-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.81.165]) by mx.google.com with ESMTPS id oj8sm8925680pbb.54.2012.08.07.19.42.10 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 07 Aug 2012 19:42:11 -0700 (PDT)
Message-ID: <5021D201.5040900@gmail.com>
Date: Tue, 07 Aug 2012 18:42:09 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: So, where to repeat?
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com>	<502169E9.9020009@dcrocker.net>	<AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk>	<EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net>
In-Reply-To: <5021CDDE.8060207@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, 08 Aug 2012 02:42:13 -0000

On 8/7/12 6:24 PM, Dave Crocker wrote:
> I haven't seen anyone post negative comments about Prague in this
> thread.  By way of probing, I'll ask for them.  For example, do folks
> who live outside of that region not care about the additional hop of
> travel to get to it?

It was over 24 hours of travel to get to Prague and over 24
hours of travel to get to Taipei - it's a wash.

It's looking like given the constraints we can't meet in Alaska.
Kidding - there aren't any facilities large enough, even in
Anchorage.

Melinda

From ole@cisco.com  Tue Aug  7 19:55:25 2012
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4357D21F84FE for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 19:55:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.563
X-Spam-Level: 
X-Spam-Status: No, score=-110.563 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FxBxfoYL27Ih for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 19:55:24 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 8CFA921F84EE for <ietf@ietf.org>; Tue,  7 Aug 2012 19:55:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=2128; q=dns/txt; s=iport; t=1344394524; x=1345604124; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=ZM+Iymub4ps9u7cvOc3Fj32Ee0GpKI2f8DUN54zDi18=; b=HUHzLHgcI/c0gVM4F/TToUp8HjdzUIAYY7SlNi95ukLfVqde08PXIIDr 7nhiinKK0yzRLmF39rDP/R8Bae4YeMlwHPDSCHxlgKFPS1FcLWswq4Rip jCmCWMraXd+K+0N4WlZmWl0XDQzPYNrtxOhgFASGwyd9EJuvXTY5J3PWX I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAA/UIVCrRDoH/2dsb2JhbABCA7lngQeCIQEBBBIBAiUtEhALRlcZGQmHappZg0gQnH6LJwIKgxsFgxwDiE2SVoUxgxqBBGKCf4E/
X-IronPort-AV: E=Sophos;i="4.77,730,1336348800"; d="scan'208";a="54389937"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-2.cisco.com with ESMTP; 08 Aug 2012 02:55:24 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q782tN3o017547 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Aug 2012 02:55:24 GMT
Date: Tue, 7 Aug 2012 19:55:23 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: dcrocker@bbiw.net
Subject: Re: So, where to repeat? (was: Re: management granularity)
In-Reply-To: <5021CDDE.8060207@dcrocker.net>
Message-ID: <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org, Richard Shockey <richard@shockey.us>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 02:55:25 -0000

You said about Prague:

"...[do] folks who live outside of that region not care about the 
additional hop of travel to get to it?"

This gets cited often, and I don't really understand why. There are 
VERY few European cities that are reachable directly from the US (or 
Asia for that matter). Most require transiting some kind of major hub 
(London, Paris, Frankfurt, Amsterdam to name a few). There will always 
be exceptions, I am sure you can get to Stockholm directly from the US 
East Coast, but not from the West Coast. I am sure a very large 
percentage of the IETF attendees from the US went through London or 
Frankfurt (or a small number of alternatives) to get to Stockholm on 
the two occasions when we met there.

Since I travel to Norway on a more or less regular basis, I am used to 
(and quite happy to) go through Frankfurt or London, it's just a fact 
of life especially if you factor in the "preferred carrier" (personal 
or corporate). Prague may be an "extra hop," but depending on 
schedules you might well get to your destination (hotel) just as 
quickly as you would for getting from CDG to central Paris or LHR to 
central London.

If we restrict European cities to the ones with direct flight 
connections from other continents, we're really limiting the choices. 
Let's be a little more realistic and consider actual travel "pain" 
from the top hubs in Europe, assuming we can't (always) meet in those 
places.

I do understand that the extra hop does add some cost, which is why
I always consider trains as a reasonable alternative, albeit not a
particularly fast one. For example, the cost for a First Class train
ticket from Frankfurt to Prague was 98 Euros. I am not suggesting
that this is always going to be a reasonable alternative, and I am
worried that the mere mention of "train" on this list may result in
a flame war, but still...

Ole



Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo



From dcrocker@bbiw.net  Tue Aug  7 20:01:40 2012
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 352BC11E80EC for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 20:01:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.546
X-Spam-Level: 
X-Spam-Status: No, score=-6.546 tagged_above=-999 required=5 tests=[AWL=0.053,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oQuWumc4duIN for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 20:01:39 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2B97711E8101 for <ietf@ietf.org>; Tue,  7 Aug 2012 20:01:39 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q7831JPb020604 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 7 Aug 2012 20:01:28 -0700
Message-ID: <5021D678.9060002@bbiw.net>
Date: Tue, 07 Aug 2012 20:01:12 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Ole Jacobsen <ole@cisco.com>
Subject: Re: So, where to repeat? (was: Re: management granularity)
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net>
In-Reply-To: <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.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]); Tue, 07 Aug 2012 20:01:33 -0700 (PDT)
Cc: ietf@ietf.org, Richard Shockey <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: Wed, 08 Aug 2012 03:01:40 -0000

On 8/7/2012 7:55 PM, Ole Jacobsen wrote:
>
> You said about Prague:
>
> "...[do] folks who live outside of that region not care about the
> additional hop of travel to get to it?"
>
> This gets cited often, and I don't really understand why. There are
> VERY few European cities that are reachable directly from the US (or
> Asia for that matter). Most require transiting some kind of major hub
> (London, Paris, Frankfurt, Amsterdam to name a few).

So, those hubs are reachable directly from the US and Asia, aren't they?


> If we restrict European cities to the ones with direct flight
> connections from other continents, we're really limiting the choices.

Yup.


> I do understand that the extra hop does add some cost,

Something like an extra US$200 or so, if I remember my research of a 
couple of years ago.  And a round-trip extra cost in time of 1/2-1 day...


d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From ole@cisco.com  Tue Aug  7 20:12:25 2012
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F32211E8110 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 20:12:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.564
X-Spam-Level: 
X-Spam-Status: No, score=-110.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mwbcdf5cQj1Q for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 20:12:24 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 9F72D11E80F3 for <ietf@ietf.org>; Tue,  7 Aug 2012 20:12:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=1644; q=dns/txt; s=iport; t=1344395544; x=1345605144; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=D5IZ/ecauJk8IAuiw3TaRCRkv0RhbQ/6Dl/jswqQ3aY=; b=LOw6pDWgx8Ab8o7TAZIsTjIOybWgyp6oQNOj9B9XfGqZlJl3QiLlcprx k6LFYtgHhJZT0/Cceye9yEVhVY+kcDxlVbIECvvIWHtZvNBQu9FZdSIyl LGLVQek9HGZ9Pno1HZVOSLlYdTZ5zreOV0v0f7JNOU3CeKrxYe7NthUR5 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAHbXIVCrRDoJ/2dsb2JhbABCA7lqgQeCIAEBAQMBEgECJT8QCw44VwYTIodlBZpdg0gQnH6LDxgCgyWDIQOITY4PhEeFMYMagQRign+BPw
X-IronPort-AV: E=Sophos;i="4.77,730,1336348800"; d="scan'208";a="54391184"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-2.cisco.com with ESMTP; 08 Aug 2012 03:12:24 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q783CN5o027684 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Aug 2012 03:12:24 GMT
Date: Tue, 7 Aug 2012 20:12:19 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Dave Crocker <dcrocker@bbiw.net>
Subject: Re: So, where to repeat? (was: Re: management granularity)
In-Reply-To: <5021D678.9060002@bbiw.net>
Message-ID: <alpine.OSX.2.01.1208072003250.20339@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <5021D678.9060002@bbiw.net>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org, Richard Shockey <richard@shockey.us>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 03:12:25 -0000

On Tue, 7 Aug 2012, Dave Crocker wrote:

> > Most require transiting some kind of major hub (London, Paris, 
> > Frankfurt, Amsterdam to name a few).
> 
> So, those hubs are reachable directly from the US and Asia, aren't they?

Yes, they are, and we have met in Paris twice and London once, will 
meet there again in 2014. Amsterdam, well, we've met there once too,
but that was a long time ago and the group was MUCH smaller. London
and Paris also happen to be among the most expensive places in the
world, and also very "popular" in terms of locating a suitable and
available venue.

> > I do understand that the extra hop does add some cost,
> 
> Something like an extra US$200 or so, if I remember my research of a couple of
> years ago.  And a round-trip extra cost in time of 1/2-1 day...

See my previous message. Short answer: it depends. Frankfurt to Prague 
is a really short flight.

Tradeoffs include significantly lower venue and hotel costs, more
availability of said venue etc. I think you'd generally get your
$200 back, but this is certainly not something one can ever be
particularly scientific about given all the variables. And with
specific reference to Prague, well, it certainly fits the "we know
this venue, we like this venue" mantra, hence it gets the "should
repeat" checkmark.

> 
> 
> d/
> -- 
>  Dave Crocker
>  Brandenburg InternetWorking
>  bbiw.net
> 
> 

Ole

Ole J. Jacobsen 
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


From vinayakh@gmail.com  Tue Aug  7 20:49:04 2012
Return-Path: <vinayakh@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 937A611E811E for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 20:49:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level: 
X-Spam-Status: No, score=-2.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KI9f8g+-P6PC for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 20:49:04 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id B17BF11E811D for <ietf@ietf.org>; Tue,  7 Aug 2012 20:49:03 -0700 (PDT)
Received: by pbbrr4 with SMTP id rr4so725353pbb.31 for <ietf@ietf.org>; Tue, 07 Aug 2012 20:49:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=EFTRr+D5kq4+oQRW2uSp11O1tWO5AaixmLUnopqbYxU=; b=z07oL/dNuBKdEDsdrMfDDiGSg8WYjKpo4XMQ/o3gtt1bo5jN5h1lWt6vyS+mELH/lO J87xcDFQBdXFhjy/6R7EuXg0dr7zDuBmWdGyMnBGRV7IWk+faY++YRsD25VbH+g1XLNd Utfni0kHA6n7Q0B5WIHcjHyraLGwBkm7a1a3gNrnwvB5gy/Sq4SRnmyuctF5JztAqJcW Vd+UxPYPfTjTGCDIdIv6xPpdWlPiYh0GMAgwzW9qKdWPEVEJNaeS90GTt/tCCAcPJkmo vrs9WvugtmDQgG3Qhy3Eat3d46AWecucABED/S9AuVPF9xxCHgxzJriLdgSlFhjw5CN7 L+MQ==
MIME-Version: 1.0
Received: by 10.66.81.232 with SMTP id d8mr30710345pay.66.1344397741420; Tue, 07 Aug 2012 20:49:01 -0700 (PDT)
Received: by 10.142.49.1 with HTTP; Tue, 7 Aug 2012 20:49:01 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20120805165716.07820120@resistor.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <E4DA6495-E02F-4A47-9AA2-E47F260CF3C5@mnot.net> <6.2.5.6.2.20120805165716.07820120@resistor.net>
Date: Wed, 8 Aug 2012 09:19:01 +0530
Message-ID: <CAKe6YvP46bssjsJCiAu+1LfUD8DAZB1ivqYLtBMdYS3k3Rn54w@mail.gmail.com>
Subject: Re: management granularity (Re: Meeting "lounges" at IETF meetings)
From: Vinayak Hegde <vinayakh@gmail.com>
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Mark Nottingham <mnot@mnot.net>, ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 03:49:04 -0000

On Mon, Aug 6, 2012 at 7:24 AM, SM <sm@resistor.net> wrote:
> Hi Mark,
> Again, choosing three or so locations ignores large parts of not only the
>> developing world (e.g., Africa, India), but also substantial portions of the
>> developed world with a reasonable track record of participation (e.g.,
>> Australia, New Zealand, Brazil).

@Mark : There has been a steady stream of participation from India for
atleast the last 4 years. By India, I mean Indians living in India and
not those living abroad (there have been quite a few of them around in
IETF for longer than 4+ years).

> There were 10 participants from Australia and 4 participants from New
> Zealand at the last IETF meeting.  There was interest to have the IETF in
> New Zealand.  I guess that it was considered as difficult to convince the
> cookie-eating mob that it was a good location.

@SM : Where do you get this data. It will be interesting to chart the
data for IETF participants over the years by country / affliation. If
we have the base location of participants then it will be interesting
to see the average distance over the years and participation based on
city.

>>  reasons for the IETF returning to Australia, or appearing nearby. And
>> going to Brazil or thereabouts, and India, and (eventually) Africa. Doesn't
>> have to be every year, but once a decade+ is not often enough.

+1

> The IETF will likely go to Latin America first.  My guess is that it might
> eventually go to India.  If it ever goes to Africa it will be more of a
> political statement than anything else.
>
> Regards,
> -sm

From johnl@iecc.com  Tue Aug  7 20:59:12 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6129411E8123 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 20:59:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.158
X-Spam-Level: 
X-Spam-Status: No, score=-111.158 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LM2tjksH4R7y for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 20:59:11 -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 7FF2611E8122 for <ietf@ietf.org>; Tue,  7 Aug 2012 20:59:11 -0700 (PDT)
Received: (qmail 66201 invoked from network); 8 Aug 2012 03:59:10 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 8 Aug 2012 03:59:10 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5021e40e.xn--btvx9d.k1208; i=johnl@user.iecc.com; bh=0QsdUvmURNCSsIap2OMtAZaH5WqMCMMQGS9D00oH22U=; b=HxAO8ZPeqyPrpWeaMrja3eypzXZe7Zm/ZsDtTEQSHzhFgqbwqxsXBrY5wEDtaP2OOXnV8vK2lRMtO/Ic+r3x5g9ODB3vLQ3BSzfa6DaNKt1KbJAP6fux28DiTh6OLAhrbUKV2CUF9Gb1xOEPrPV5Q3wBQzCL9BNJ0tlCKYjKJB0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5021e40e.xn--btvx9d.k1208; olt=johnl@user.iecc.com; bh=0QsdUvmURNCSsIap2OMtAZaH5WqMCMMQGS9D00oH22U=; b=EW+OcG9MqSdPzoMgoqRA6oqYFgHXUkn8klYTB95TpbOnC5n/aMywyyBS6DrN1pu/UdJQvmL09qbps7C6LwaPR+LItlrV1triLlKdap0D0u1Z1uvmqU0RhViyfJ6dfqCNi7E/+Ff+WoixLItymvZIDKwvoVuQyyYJgKM7evSMMzk=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 8 Aug 2012 03:58:48 -0000
Message-ID: <20120808035848.63251.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: So, where to repeat? (was: Re: management granularity)
In-Reply-To: <5021CCE8.6020106@dcrocker.net>
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, 08 Aug 2012 03:59:12 -0000

>> The Burlington hotel claims that they can host a 1500 person meeting.
>
>
>Yeah, it's exactly that easy to choose a venue.  A single number does it.[1]
>
>not.

Of course.  MAAWG has been there so we know it's not a dump, it's
downtown, they can deal with nerds with lots of computers who demand
coffee and cookies, the prices are not totally absurd, etc.  MAAWG is
smaller than the IETF so there may well be problems that make it
unsuitable, but if people are looking for a downtown Dublin hotel,
that's the most likely one.

R's,
John

PS: Weren't you at that meeting?  The day we arrived there was a
benefit women's road race in the morning so when we got there in the
afternoon, the pubs were all full of the racers, who ranged from
athletic teens to good natured grannies, and their friends.

From johnl@iecc.com  Tue Aug  7 21:05:10 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EED8221F85F0 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 21:05:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.158
X-Spam-Level: 
X-Spam-Status: No, score=-111.158 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bmzr1M1F19HY for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 21:05:10 -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 B402E21F85EF for <ietf@ietf.org>; Tue,  7 Aug 2012 21:05:09 -0700 (PDT)
Received: (qmail 67151 invoked from network); 8 Aug 2012 04:05:09 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 8 Aug 2012 04:05:09 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5021e575.xn--9vv.k1208; i=johnl@user.iecc.com; bh=Rjdlb/wzt2oMFc3LUim9KNJSNPrmkHieTRpeCm+t8XI=; b=hr6B05ZFzlv/TwX/cVigjnwXweFmyZIa/Oz6nSRuTcyGirzZiLExWG2L2niRt0pAPk2P7MwhIyVeLNVAaaYuGGicj1CO6VVADBW3yoipjBhSm/32qfOCnAoEoOpPl2RplwvMxpiztfNYu6EYyCdryGpNScbG6HAZyZkvAZH0Ce4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5021e575.xn--9vv.k1208; olt=johnl@user.iecc.com; bh=Rjdlb/wzt2oMFc3LUim9KNJSNPrmkHieTRpeCm+t8XI=; b=TW5EEJ6qC59gMp3JPS2aJi+U75A6lH19j6frFVZDLKC6YJ8NTZUgm17pQ4QTAE2rR8Hi/amEb6c3sIoZxn/QLdvdncPA/EwTnNP4HVakUjyuGqgNma7IrKz2O1mYwhAA+5Zz0Zq5EjnQ60b5xOCfqlQdT0hWeW14LpoVyGJEFK0=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 8 Aug 2012 04:04:47 -0000
Message-ID: <20120808040447.64729.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: So, where to repeat? (was: Re: management granularity)
In-Reply-To: <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: ole@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, 08 Aug 2012 04:05:11 -0000

>If we restrict European cities to the ones with direct flight 
>connections from other continents, we're really limiting the choices. 

For some of us, if we limit our choices to places with direct flights,
that means Newark, Philadelphia, or Detroit.  Count your blessings.

We can argue about whether Quebec was unduly hard to get to (I didn't
have any problem when I got tickets a month ahead, even though I was
redeeming points), but it seems to me that so long as most people can
get to or from the venue in less than a day for a reasonable amount of
money, it's OK.

R's,
John

From marka@isc.org  Tue Aug  7 21:52:22 2012
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 7903D21F855E for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 21:52:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.582
X-Spam-Level: 
X-Spam-Status: No, score=-2.582 tagged_above=-999 required=5 tests=[AWL=0.017,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Guz3tFZKN0xG for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 21:52:05 -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 4734721F854F for <ietf@ietf.org>; Tue,  7 Aug 2012 21:52: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 "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS id 75222C942B; Wed,  8 Aug 2012 04:51:51 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (173-11-96-181-SFBA.hfc.comcastbusiness.net [173.11.96.181]) (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 5838B216C33; Wed,  8 Aug 2012 04:51:51 +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 41A60235AA9A; Wed,  8 Aug 2012 14:51:49 +1000 (EST)
To: Doug Barton <dougb@dougbarton.us>
From: Mark Andrews <marka@isc.org>
References: <20120807074601.23F871A125@ld9781.wdf.sap.corp> <5021742A.70804@dougbarton.us>
Subject: Re: ITU-T Dubai Meeting
In-reply-to: Your message of "Tue, 07 Aug 2012 13:01:46 MST." <5021742A.70804@dougbarton.us>
Date: Wed, 08 Aug 2012 14:51:49 +1000
Message-Id: <20120808045149.41A60235AA9A@drugs.dv.isc.org>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 04:52:22 -0000

In message <5021742A.70804@dougbarton.us>, Doug Barton writes:
> On 08/07/2012 00:46, Martin Rex wrote:
> > IPv6 PA prefixes result in that awkward renumbering.
> > Avoiding the renumbering implies provider independent
> > network prefix.
> 
> ULA on the inside + https://tools.ietf.org/html/rfc6296

If you are changing your external connection you may as well just use
ULA + PA.  The DNS needs to be updated in either case, the firewall needs
to be updated in either case.
 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From sm@resistor.net  Tue Aug  7 21:52:22 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC4C821F854F for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 21:52:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level: 
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JWgz25Ac5xox for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 21:52:04 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E55921F8552 for <ietf@ietf.org>; Tue,  7 Aug 2012 21:52:04 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q784pqpG022791; Tue, 7 Aug 2012 21:51:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1344401519; bh=A+OqLm77jlADQXpVdOhrnrUobuduoKdjlRyAd1+lngg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=iieE/PRFvE4N07HLrU/aUisIMPhjwPL2rXtwMxGv7R8M2K8BiukfDtZMe+0QVlx9y n4O1tB7BpRmSER0LwxUBhCckHDtLXT3hUlkpVc8G+Z/tiBMv36xh70vzQhNCzCVVFy lWuLeDTImB8vcATDiAK+mbLOqU6glfUSynAecvPc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1344401519; i=@resistor.net; bh=A+OqLm77jlADQXpVdOhrnrUobuduoKdjlRyAd1+lngg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=DrQgALT1TP5zwyts1MA0tqUEmYsGnelitCwZLFNYoHxcNJLf7lSWg00brif7yU72n oMT8PhOy3XKTOELfce+3CD6Lq8bNHoXI8SrPKvfjhIv+TSB5d8r8IT5d5vsAsE2p71 Rr2N5bIS7RVU+gvLycvh6cxz2/SHzYpYqA0sPkdI=
Message-Id: <6.2.5.6.2.20120807211829.0a0b4718@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 07 Aug 2012 21:47:34 -0700
To: Vinayak Hegde <vinayakh@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: management granularity (Re: Meeting "lounges" at IETF meetings)
In-Reply-To: <CAKe6YvP46bssjsJCiAu+1LfUD8DAZB1ivqYLtBMdYS3k3Rn54w@mail.g mail.com>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <E4DA6495-E02F-4A47-9AA2-E47F260CF3C5@mnot.net> <6.2.5.6.2.20120805165716.07820120@resistor.net> <CAKe6YvP46bssjsJCiAu+1LfUD8DAZB1ivqYLtBMdYS3k3Rn54w@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 04:52:23 -0000

Hi Vinayak,
At 20:49 07-08-2012, Vinayak Hegde wrote:
>@SM : Where do you get this data. It will be interesting to chart the
>data for IETF participants over the years by country / affliation. If

The list of participants for the last meeting is at 
https://www.ietf.org/registration/ietf84/attendance.py

Regards,
-sm 


From mrex@sap.com  Tue Aug  7 22:19:35 2012
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 C571A11E811D for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 22:19:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.168
X-Spam-Level: 
X-Spam-Status: No, score=-10.168 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B6ZbmYl4JLTf for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 22:19:35 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id E65DD11E80E2 for <ietf@ietf.org>; Tue,  7 Aug 2012 22:19:34 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q785JTQT028250 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 8 Aug 2012 07:19:29 +0200 (MEST)
Subject: Re: ITU-T Dubai Meeting
In-Reply-To: <20120808045149.41A60235AA9A@drugs.dv.isc.org>
To: Mark Andrews <marka@isc.org>
Date: Wed, 8 Aug 2012 07:19:29 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20120808051929.717981A12D@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
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, 08 Aug 2012 05:19:35 -0000

Mark Andrews wrote:
> 
> In message <5021742A.70804@dougbarton.us>, Doug Barton writes:
> > On 08/07/2012 00:46, Martin Rex wrote:
> > > IPv6 PA prefixes result in that awkward renumbering.
> > > Avoiding the renumbering implies provider independent
> > > network prefix.
> > 
> > ULA on the inside + https://tools.ietf.org/html/rfc6296
> 
> If you are changing your external connection you may as well just use
> ULA + PA.  The DNS needs to be updated in either case, the firewall needs
> to be updated in either case.

And what about running apps and network connections in the connected state?

I'm also wondering about sockets in listen() on less-than-any
interface(s), bind() seems to work on IP-Addresses, not interfaces.

I have a copy Steven's Unix Network Programming
(a Volume 1 second edition that I purchase while at the
 Pittsburgh IETF in Aug 2000)

I don't see (IPv6) "renumbering" in the Index or Table of Contents,
is it somewhere describe for apps programmers how to deal with
renumbering events?  Or is it a "Reboot for changes to take effect"
type of activity?

-Martin

From dougb@dougbarton.us  Tue Aug  7 22:28:38 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EE7111E812F for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 22:28:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Wo1MW65BAnz for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 22:28:37 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 48A2211E812C for <ietf@ietf.org>; Tue,  7 Aug 2012 22:28:36 -0700 (PDT)
Received: (qmail 2207 invoked by uid 399); 8 Aug 2012 05:28:29 -0000
Received: from unknown (HELO ?192.168.0.100?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 8 Aug 2012 05:28:29 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <5021F902.4090808@dougbarton.us>
Date: Tue, 07 Aug 2012 22:28:34 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
Subject: Re: ITU-T Dubai Meeting
References: <20120807074601.23F871A125@ld9781.wdf.sap.corp> <5021742A.70804@dougbarton.us> <20120808045149.41A60235AA9A@drugs.dv.isc.org>
In-Reply-To: <20120808045149.41A60235AA9A@drugs.dv.isc.org>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 05:28:38 -0000

On 08/07/2012 09:51 PM, Mark Andrews wrote:
> In message <5021742A.70804@dougbarton.us>, Doug Barton writes:
>> On 08/07/2012 00:46, Martin Rex wrote:
>>> IPv6 PA prefixes result in that awkward renumbering.
>>> Avoiding the renumbering implies provider independent
>>> network prefix.
>>
>> ULA on the inside + https://tools.ietf.org/html/rfc6296
> 
> If you are changing your external connection you may as well just use
> ULA + PA.

That was what Martin was discussing, unless I missed something.


From dougb@dougbarton.us  Tue Aug  7 22:30:54 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14A6121E8034 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 22:30:54 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ucs6rCC3FJjr for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 22:30:53 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 0C7C311E812D for <ietf@ietf.org>; Tue,  7 Aug 2012 22:30:53 -0700 (PDT)
Received: (qmail 3838 invoked by uid 399); 8 Aug 2012 05:30:46 -0000
Received: from unknown (HELO ?192.168.0.100?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 8 Aug 2012 05:30:46 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <5021F98A.9000509@dougbarton.us>
Date: Tue, 07 Aug 2012 22:30:50 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: ITU-T Dubai Meeting
References: <20120808051929.717981A12D@ld9781.wdf.sap.corp>
In-Reply-To: <20120808051929.717981A12D@ld9781.wdf.sap.corp>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 05:30:54 -0000

On 08/07/2012 10:19 PM, Martin Rex wrote:
> Mark Andrews wrote:
>>
>> In message <5021742A.70804@dougbarton.us>, Doug Barton writes:
>>> On 08/07/2012 00:46, Martin Rex wrote:
>>>> IPv6 PA prefixes result in that awkward renumbering.
>>>> Avoiding the renumbering implies provider independent
>>>> network prefix.
>>>
>>> ULA on the inside + https://tools.ietf.org/html/rfc6296
>>
>> If you are changing your external connection you may as well just use
>> ULA + PA.  The DNS needs to be updated in either case, the firewall needs
>> to be updated in either case.
> 
> And what about running apps and network connections in the connected state?

If they are connected external to your network then obviously they would
have to be restarted ... but then you know that already. :)

If "PI everywhere" were a feasible strategy at this time, I'd be first
in line. But it isn't, so I think it's worthwhile discussing how we can
do what we _can_ do, best.


From mrex@sap.com  Tue Aug  7 23:47:03 2012
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 214E311E8138 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 23:47:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.169
X-Spam-Level: 
X-Spam-Status: No, score=-10.169 tagged_above=-999 required=5 tests=[AWL=0.080, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kRMVp4Dvzny5 for <ietf@ietfa.amsl.com>; Tue,  7 Aug 2012 23:47:02 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 006D011E808E for <ietf@ietf.org>; Tue,  7 Aug 2012 23:47:01 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q786l0TJ023308 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 8 Aug 2012 08:47:00 +0200 (MEST)
Subject: Re: ITU-T Dubai Meeting
In-Reply-To: <20120807143241.44D2118C0B5@mercury.lcs.mit.edu>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Date: Wed, 8 Aug 2012 08:47:00 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20120808064700.11B7B1A12D@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
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, 08 Aug 2012 06:47:03 -0000

Noel Chiappa wrote:
>
>     > you want some level of privacy protection and therefore a fully dynamic
>     > temporary DHCP-assigned IPv6 address
> 
> This turns out to be a chimera. Such addresses don't really provide any real
> privacy - it turns out to be easy to track people through their access
> patterns, etc.

It _can_ be used in in a privacy-protecting fashion,
when used properly (potentially with other than a web browser).

If one is using one single web browser for *everything*; with
cookies, active content, flash and all other crap enabled,
then an occasional change in the outside address of your
DSL router is not going to make much of a difference, of course.

The map that tools/plugins like these draw after a few mouseclicks
in a fully-featured FireFox are impressive (or depressing, depending
on how you feel about privacy):

   http://www.mozilla.org/en-US/collusion/
   http://www.ghostery.com/


-Martin

From brian.e.carpenter@gmail.com  Wed Aug  8 00:52:28 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F182321F86C9 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 00:52:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.481
X-Spam-Level: 
X-Spam-Status: No, score=-101.481 tagged_above=-999 required=5 tests=[AWL=0.210, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vlxkWf8fJg0N for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 00:52:28 -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 4C70521F86B7 for <ietf@ietf.org>; Wed,  8 Aug 2012 00:52:28 -0700 (PDT)
Received: by eaai11 with SMTP id i11so106607eaa.31 for <ietf@ietf.org>; Wed, 08 Aug 2012 00:52:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=oJMDfvgVBQLXKMThugbvIcXpqDle9a76nPnN2mtWRDA=; b=DsdjbwdrTk+U06CeX6xSeZ7RZ786cox8H51q5os0gK3N+hl9kFbw2XCCXKtMOc4BHv lQhlwF/BlySUS32ToXNNthNXK1yirOuXa+NGahp1gYeTtdwaImJopBPKb695YnLUd+Ym lDM8o9nmza4lwvvldu0ZsxNzCHUOQl8A0WSSOpdTmMtP3ikU41rw3lPuzxF9pg/JEQUd nhKPAUZgZ276zxgPhphQPgYVBMN2bnpABwMvo+eMRCCX2h03NvkYd3i2PAWCrDdNXEiv JCyUk+bEt8uB47A7r2W97UdJm2c0KIlO95ERN0lekQPpzZejjx41NRb00sjGTPCFJjsf mOuw==
Received: by 10.14.204.72 with SMTP id g48mr21105828eeo.45.1344412347468; Wed, 08 Aug 2012 00:52:27 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-169.as13285.net. [2.102.217.169]) by mx.google.com with ESMTPS id k41sm62282642eep.13.2012.08.08.00.52.25 (version=SSLv3 cipher=OTHER); Wed, 08 Aug 2012 00:52:26 -0700 (PDT)
Message-ID: <50221ABA.4020306@gmail.com>
Date: Wed, 08 Aug 2012 08:52:26 +0100
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: Doug Barton <dougb@dougbarton.us>
Subject: Re: ITU-T Dubai Meeting
References: <20120808051929.717981A12D@ld9781.wdf.sap.corp> <5021F98A.9000509@dougbarton.us>
In-Reply-To: <5021F98A.9000509@dougbarton.us>
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, 08 Aug 2012 07:52:29 -0000

On 08/08/2012 06:30, Doug Barton wrote:
> On 08/07/2012 10:19 PM, Martin Rex wrote:
>> Mark Andrews wrote:
>>> In message <5021742A.70804@dougbarton.us>, Doug Barton writes:
>>>> On 08/07/2012 00:46, Martin Rex wrote:
>>>>> IPv6 PA prefixes result in that awkward renumbering.
>>>>> Avoiding the renumbering implies provider independent
>>>>> network prefix.
>>>> ULA on the inside + https://tools.ietf.org/html/rfc6296
>>> If you are changing your external connection you may as well just use
>>> ULA + PA.  The DNS needs to be updated in either case, the firewall needs
>>> to be updated in either case.
>> And what about running apps and network connections in the connected state?
> 
> If they are connected external to your network then obviously they would
> have to be restarted ... but then you know that already. :)

And any mission-critical application that can't survive a disconnect and
reconnect is badly broken anyway. I've never understood why session survival
was so highly rated; this has vastly complicated every discussion of
multihoming for many years.

    Brian

> 
> If "PI everywhere" were a feasible strategy at this time, I'd be first
> in line. But it isn't, so I think it's worthwhile discussing how we can
> do what we _can_ do, best.
> 
> 

From mehmet.ersue@nsn.com  Wed Aug  8 01:04:27 2012
Return-Path: <mehmet.ersue@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 1EC4221F85B4 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 01:04:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.577
X-Spam-Level: 
X-Spam-Status: No, score=-106.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z7rPjx4FrNti for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 01:04:26 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id D0A8D21F84F3 for <ietf@ietf.org>; Wed,  8 Aug 2012 01:04:25 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q7883teY020146 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 8 Aug 2012 10:03:57 +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 q7883nnh003180; Wed, 8 Aug 2012 10:03:50 +0200
Received: from DEMUEXC006.nsn-intra.net ([10.150.128.17]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 8 Aug 2012 10:03:42 +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: So, where to repeat? (was: Re: management granularity)
Date: Wed, 8 Aug 2012 10:03:41 +0200
Message-ID: <80A0822C5E9A4440A5117C2F4CD36A6404184034@DEMUEXC006.nsn-intra.net>
In-Reply-To: <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: So, where to repeat? (was: Re: management granularity)
Thread-Index: Ac106DvOpW6CHOT9SX+HRmJKOOOpQAAVAeTA
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com><502169E9.9020009@dcrocker.net><AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk><EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com>
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: "ext Steve Crocker" <steve@shinkuro.com>, "Tim Chown" <tjc@ecs.soton.ac.uk>
X-OriginalArrivalTime: 08 Aug 2012 08:03:42.0867 (UTC) FILETIME=[53D68E30:01CD753C]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 883
X-purgate-ID: 151667::1344413037-00002E58-9952E6EB/0-0/0-0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 08:04:27 -0000

> I'll bet Dublin would be rated higher if the meetings had been
downtown. =20

Indeed.

Mehmet=20

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
Of ext Steve
> Crocker
> Sent: Wednesday, August 08, 2012 12:01 AM
> To: Tim Chown
> Cc: ietf@ietf.org
> Subject: Re: So, where to repeat? (was: Re: management granularity)
>=20
> I'll bet Dublin would be rated higher if the meetings had been
downtown.  Same for
> Vienna.
>=20
> Steve
>=20
> On Aug 7, 2012, at 5:55 PM, Tim Chown wrote:
>=20
> > Hi,
> >
> > My top three repeat venues would be Prague, Minneapolis and
Vancouver.  Great
> meeting venues, with everything you need nearby.
> >
> > My least favoured venues have been Dublin, Vienna and Maastricht.
> >
> > Of course, you have to experiment to find good repeat venues...
> >
> > Tim


From daniel.karrenberg@ripe.net  Wed Aug  8 02:04:28 2012
Return-Path: <daniel.karrenberg@ripe.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C102C21F8699 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 02:04:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dLKwhveHRiX2 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 02:04:27 -0700 (PDT)
Received: from postlady.ripe.net (postlady.ipv6.ripe.net [IPv6:2001:67c:2e8:11::c100:1341]) by ietfa.amsl.com (Postfix) with ESMTP id E470F21F8679 for <ietf@ietf.org>; Wed,  8 Aug 2012 02:04:26 -0700 (PDT)
Received: from dodo.ripe.net ([193.0.23.4]) by postlady.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <daniel.karrenberg@ripe.net>) id 1Sz2Bk-0007q3-7W; Wed, 08 Aug 2012 11:04:25 +0200
Received: from baboon.ripe.net ([193.0.1.208] helo=[127.0.0.1]) by dodo.ripe.net with esmtps (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <daniel.karrenberg@ripe.net>) id 1Sz2Bk-0000lW-2Q; Wed, 08 Aug 2012 11:04:24 +0200
Subject: Re: ITU-T Dubai Meeting
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Daniel Karrenberg <daniel.karrenberg@ripe.net>
In-Reply-To: <20120806220208.D443E1A126@ld9781.wdf.sap.corp>
Date: Wed, 8 Aug 2012 11:04:23 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7C6F6C7E-DAC8-41A8-B55B-BFBED4454F37@ripe.net>
References: <20120806220208.D443E1A126@ld9781.wdf.sap.corp>
To: mrex@sap.com
X-Mailer: Apple Mail (2.1278)
X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.48/RELEASE, bases: 20120425 #7816066, check: 20120808 clean
X-RIPE-Spam-Level: --
X-RIPE-Spam-Report: Spam Total Points:   -2.9 points pts rule name              description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 2cd422cf40ef1bab352b066641112beb425a9275acfa5a0a1753580c41602d72
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 09:04:28 -0000

On 07.08.2012, at 00:02, Martin Rex wrote:

> Steven Bellovin wrote:
>>=20
>> Randy Bush wrote:
>>>=20
>>> whatever the number of address bits, if it is fixed, we always run =
out.
>>> memory addressing has been a cliff many times.  ip addressing.  ...
>>=20
>> Yup.  To quote Fred Brooks on memory address space: "Every successful
>> computer architecture eventually runs out of address space" -- and I =
heard
>> him say that in 1973.
>=20
> I'm wondering what resource shortage would have happened if IPv6
> had been massively adopted 10 years earlier, and whether we would have
> seen the internet backbone routers suffer severely from the size
> of the routing tables, if every single home customer (DSL subscriber)
> would have required a provider-independent IPv6 network prefix rather
> than a single, provider-dependent IPv4 IP Address.


... add to that: what would have happened if the IETF had not =
underestimated
the life expectancy of IPv4 address space so drastically and  =
consequently had=20
taken the time to design  a better IPv6  with things like wire =
compatibility=20
with IPv4, better routing and other features that make ISPs want to =
deploy it.=20
Ah - what if ....... . Amusing musings but not more than that.

Daniel=

From drc@virtualized.org  Wed Aug  8 06:40:35 2012
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 37CAA21F853D for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 06:40:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ih10FMJGRafd for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 06:40:34 -0700 (PDT)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id 67FE121F85BB for <ietf@ietf.org>; Wed,  8 Aug 2012 06:40:34 -0700 (PDT)
Received: from [10.0.1.8] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: drc) by trantor.virtualized.org (Postfix) with ESMTPSA id 4A2A41705A; Wed,  8 Aug 2012 13:40:32 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: ITU-T Dubai Meeting
From: David Conrad <drc@virtualized.org>
In-Reply-To: <50221ABA.4020306@gmail.com>
Date: Wed, 8 Aug 2012 06:40:32 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <4C14946B-97C8-40C6-BACF-668DF4E5B4D9@virtualized.org>
References: <20120808051929.717981A12D@ld9781.wdf.sap.corp> <5021F98A.9000509@dougbarton.us> <50221ABA.4020306@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1485)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 13:40:35 -0000

Brian,

On Aug 8, 2012, at 12:52 AM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>> If they are connected external to your network then obviously they =
would
>> have to be restarted ... but then you know that already. :)
> And any mission-critical application that can't survive a disconnect =
and
> reconnect is badly broken anyway. I've never understood why session =
survival
> was so highly rated; this has vastly complicated every discussion of
> multihoming for many years.

The Law of Conservation of Complexity[1]?  Forcing applications to deal =
with disconnect/reconnect means they're much more complicated than if =
they can assume the session is always there and there are many more =
applications (and application developers, particular those that do it =
poorly) than networks.

Regards,
-drc

[1] I thought I was being snarky. Imagine my surprise when I just =
discovered this actually exists: =
http://en.wikipedia.org/wiki/Law_of_conservation_of_complexity=

From arturo.servin@gmail.com  Wed Aug  8 07:51:33 2012
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD28721F865C for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 07:51:33 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kO53Ta4eSv0h for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 07:51:33 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1E54D21F8565 for <ietf@ietf.org>; Wed,  8 Aug 2012 07:51:32 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so954897ggn.31 for <ietf@ietf.org>; Wed, 08 Aug 2012 07:51:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=XHQGw13JQRsdffeX4873nZEqYbVyvWigXOxrMFclyr8=; b=x10GBdOmkKGUsHKSGMRH//Ty+LFd9AryKQfWgnmVQSoRAgwHsv2xJv/e8pyaaV58+z LfjZHqcoUxEb2/4kEh6+o6Tym4J8Xhswyh1jlWUAtFbcyzTMmKm8urJ1k06LihPmwb2G hA4ASnKgAHxqnMhp2lm+OmWp41XRUEL0CC1q+szXGpE3QP1wgJBmCFrcIm6AvV9VmVQU C93iAL/rrN3xBQbcmd81JB19s79C7XVJb3fZEzh+TNjcq1LzfxK46vxTe+I5axQJb1pn vYOYGYEj2zS/bpnrMbpZUd+q+P3MsXlyJIXHGf39TN29aOMgF518vr8LPaYbTYjVsvWl nS7g==
Received: by 10.236.154.165 with SMTP id h25mr16878279yhk.38.1344437492704; Wed, 08 Aug 2012 07:51:32 -0700 (PDT)
Received: from 85-7-200.lacnic.net.uy ([200.7.85.140]) by mx.google.com with ESMTPS id s12sm13961106anh.2.2012.08.08.07.51.29 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 08 Aug 2012 07:51:31 -0700 (PDT)
Subject: Re: ITU-T Dubai Meeting
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Arturo Servin <arturo.servin@gmail.com>
In-Reply-To: <5021742A.70804@dougbarton.us>
Date: Wed, 8 Aug 2012 11:51:26 -0300
Content-Transfer-Encoding: 7bit
Message-Id: <FD58F405-5FBE-4533-8241-7294CAEE9DE1@gmail.com>
References: <20120807074601.23F871A125@ld9781.wdf.sap.corp> <5021742A.70804@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
X-Mailer: Apple Mail (2.1278)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 14:51:33 -0000

	If I refuse to use NAT (or NPTv6 for the sensible)?

	Any other option besides PI?

/as

On 7 Aug 2012, at 17:01, Doug Barton wrote:

> On 08/07/2012 00:46, Martin Rex wrote:
>> IPv6 PA prefixes result in that awkward renumbering.
>> Avoiding the renumbering implies provider independent
>> network prefix.
> 
> ULA on the inside + https://tools.ietf.org/html/rfc6296
> 
> -- 
> 
>    I am only one, but I am one.  I cannot do everything, but I can do
>    something.  And I will not let what I cannot do interfere with what
>    I can do.
> 			-- Edward Everett Hale, (1822 - 1909)


From Tom.Haynes@netapp.com  Tue Aug  7 13:03:25 2012
Return-Path: <Tom.Haynes@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65F5421F86EA; Tue,  7 Aug 2012 13:03:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.542
X-Spam-Level: 
X-Spam-Status: No, score=-10.542 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V1F2dljB4a9m; Tue,  7 Aug 2012 13:03:23 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id CCEE221F86D5; Tue,  7 Aug 2012 13:03:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.77,728,1336374000"; d="scan'208";a="674310059"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 07 Aug 2012 13:03:00 -0700
Received: from vmwexceht05-prd.hq.netapp.com (vmwexceht05-prd.hq.netapp.com [10.106.77.35]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q77K2xvT016107; Tue, 7 Aug 2012 13:02:59 -0700 (PDT)
Received: from SACEXCMBX04-PRD.hq.netapp.com ([169.254.6.188]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.02.0309.002; Tue, 7 Aug 2012 13:02:53 -0700
From: "Haynes, Tom" <Tom.Haynes@netapp.com>
To: "rbarnes@bbn.com" <rbarnes@bbn.com>
Subject: Re: [nfsv4] Gen-ART LC review of draft-ietf-nfsv4-federated-fs-admin-11 (fwd)
Thread-Topic: [nfsv4] Gen-ART LC review of draft-ietf-nfsv4-federated-fs-admin-11 (fwd)
Thread-Index: AQHNUIiR3/6yfq+JwEWuYsxcwIlj9ZdPg48A
Date: Tue, 7 Aug 2012 20:02:58 +0000
Message-ID: <800EE113-E8B8-4C7A-97B6-182C01CA7149@netapp.com>
References: <CC08E06F.1AFEC%tom.haynes@netapp.com>
In-Reply-To: <CC08E06F.1AFEC%tom.haynes@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7F0B98AFBF824349B55FCCD4B78DDEDE@tahoe.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 08 Aug 2012 09:50:55 -0700
Cc: nfsv4 list <nfsv4@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-nfsv4-federated-fs-admin@tools.ietf.org" <draft-ietf-nfsv4-federated-fs-admin@tools.ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 20:03:25 -0000

Hi Richard,

Here is the proposed text for the remaining issues you raised:

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

1. Section 4 does not adequately specify how the certificate in the
FedFsNsdbParams should be used in the verification process.  Is it to be
used as a trust anchor, so that any subordinate certificate is considered
valid?  Or perhaps it is to be matched against the end-entitycertificate.
In either case, it seems like it would be sufficient to
provision a certificate fingerprint (or even a public key fingerprint)inste=
ad
of the whole certificate.

Original:
------------
A value of FEDFS_SEC_TLS indicates that the StartTLS security
    mechanism [RFC4513] MUST be used to protect all connections to the
    NSDB.  In this case, the secData array will contain an X.509v3
    certificate in binary DER format [RFC5280].  The certificate
    SHOULD be used by the fileserver to authenticate the identity of

Lentini, et al.         Expires December 16, 2012              [Page 17]
Internet-Draft  Admin Protocol for Federated Filesystems       June 2012

    the NSDB.  In particular, this certificate SHOULD be used to
    validate the NSDB's TLS certificate list chain (see 7.4.2 of
    [RFC5246]).  The certificate could be that of a certificate
    authority or a self-signed certificate.


New:
-------
A value of FEDFS_SEC_TLS indicates that the StartTLS security
mechanism [RFC4513] MUST be used to protect all connections to the
NSDB.  In this case, the secData array will contain an X.509v3
root certificate in binary DER format [RFC5280] fulfilling the TLS
requirement that root keys be distributed independently from the TLS
protocol. The certificate MUST be used by the fileserver
as a Trust Anchor to validate the NSDB's TLS server certificate list
chain (see section 7.4.2 of [RFC5246]) and thus authenticate the identitiy
of the NSDB. The certificate could be that of a certificate authority or
a self-signed cert.

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

2. In the security considerations, the document should discuss the
implications of provisioning trust information in this way (depending on
how it is used), and any requirements for security mechanisms to be used
in these cases.

Original
---------
6.  Security Considerations

 The ONC RPC protocol supports authentication, integrity and privacy
 via the RPCSEC_GSS framework [RFC2203].  Fileservers which support
 the FedFS administration protocol described above MUST support
 RPCSEC_GSS.

 FEDFS_GET_LIMITED_NSDB_PARAMS's interaction with the NSDB's
 connection parameters is discussed in Section 5.10.2.


New
---

6.  Security Considerations

 The ONC RPC protocol supports authentication, integrity and privacy
 via the RPCSEC_GSS framework [RFC2203].  Fileservers which support
 the FedFS administration protocol described above MUST support
 RPCSEC_GSS. When RPCSEC_GSS is employed, RPCSEC_GSS data integrity
 SHOULD be used.

 It is strongly RECOMMENDED that an Access Control Service be employed
 to restrict access to a fileserver's FedFS administration configuration
 data via the FedFS administrative protocol to prevent FedFS namespace
 corruption, and protect NSDB communication parameters.

 For example, when the FedFsNsdbParams secData field value FEDFS_SEC_TLS
 is chosen, the payload is used to provision the trust anchor root
 certificate for TLS secure communication between the fileserver and the NS=
DB.
 In this case, RPCSEC_GSS with data integrity SHOULD be employed along with
 an Access Control Service to restrict access to domain adminstrators.

 FEDFS_GET_LIMITED_NSDB_PARAMS's interaction with the NSDB's
 connection parameters is discussed in Section 5.10.2.

Please let us know if these address the points you raised.

Thanks,
Tom

On Jul 27, 2012, at 12:29 PM, Chuck Lever wrote:

> ..returning FEDFS_ERR_ACCESS... =20
>=20
> That should also go in the body of the Implementation discussion in the A=
DMIN draft, I think.
>=20
> Sent from my iPhone
>=20
> On Jul 27, 2012, at 11:48 AM, "Adamson, Andy" <William.Adamson@netapp.com=
> wrote:
>=20
>> Here is a stab at updating the Security Considerations section to addres=
s the second Gen-ART review comment.
>>=20
>> -->Andy
>>=20
>> ------- second Gen-ART review comment -------------
>> 2. In the security considerations, the document should discuss the
>> implications of provisioning trust information in this way (depending on
>> how it is used), and any requirements for security mechanisms to be used
>> in these cases.
>> ----------------------
>>=20
>> Original
>> ---------
>> 6.  Security Considerations
>>=20
>> The ONC RPC protocol supports authentication, integrity and privacy
>> via the RPCSEC_GSS framework [RFC2203].  Fileservers which support
>> the FedFS administration protocol described above MUST support
>> RPCSEC_GSS.
>>=20
>> FEDFS_GET_LIMITED_NSDB_PARAMS's interaction with the NSDB's
>> connection parameters is discussed in Section 5.10.2.
>>=20
>>=20
>> New
>> ---
>>=20
>> 6.  Security Considerations
>>=20
>> The ONC RPC protocol supports authentication, integrity and privacy
>> via the RPCSEC_GSS framework [RFC2203].  Fileservers which support
>> the FedFS administration protocol described above MUST support
>> RPCSEC_GSS. When RPCSEC_GSS is employed, RPCSEC_GSS data integrity=20
>> SHOULD be used.
>>=20
>> An Access Control Service SHOULD be employed to restrict access to a
>> fileserver's FedFS administration configuration data via the FedFS
>> administrative protocol, returning FEDFS_ERR_ACCESS when the caller
>> does not have the correct permission to perform the requested operation.
>>=20
>> When NSDB connection paramters contains security mechanism sensitive
>> information, RPCSEC_GSS with data integrity SHOULD be used.
>>=20
>> For example, when the FedFsNsdbParams secData field value FEDFS_SEC_TLS
>> is chosen, the payload is used to provision the trust anchor root=20
>> certificate for TLS secure communication between the fileserver and the =
NSDB.
>> In this case, RPCSEC_GSS with data integrity SHOULD be employed along wi=
th
>> an Access Control Service.
>>=20
>> FEDFS_GET_LIMITED_NSDB_PARAMS's interaction with the NSDB's
>> connection parameters is discussed in Section 5.10.2.
>>=20
>>=20
>> On Jul 27, 2012, at 10:30 AM, Nico Williams wrote:
>>=20
>>> Security implementation mandates are fine.  Security use mandates are
>>> at least controversial, and probably impractical.


On Jun 22, 2012, at 8:06 AM, "Haynes, Tom" <Tom.Haynes@netapp.com> wrote:

> <comments inline>
>=20
> On 6/20/12 11:53 AM, "James Lentini" <jlentini@netapp.com> wrote:
>=20
>>=20
>> Below is the Gen-ART review comments for the FedFS admin protocol.
>>=20
>> -james
>>=20
>> ---------- Forwarded message ----------
>> Date: Tue, 19 Jun 2012 11:31:42 -0400
>> From: Richard L. Barnes <rbarnes@bbn.com>
>> To: ietf@ietf.org, The IESG <iesg@ietf.org>,
>>   draft-ietf-nfsv4-federated-fs-admin@tools.ietf.org, gen-art@ietf.org
>> Subject: Gen-ART LC review of draft-ietf-nfsv4-federated-fs-admin-11
>>=20
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>=20
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>=20
>> Document: draft-ietf-nfsv4-federated-fs-admin-11
>> Reviewer: Richard Barnes
>> Review Date: Jun-19-2012
>> IETF LC End Date: Not known
>> IESG Telechat date: Jun-28-2012
>>=20
>> Summary: Almost ready, couple of issues
>>=20
>> MAJOR:=20
>>=20
>> 4. / 7.
>> This protocol allows for the provisioning of security information as par=
t
>> of the FedFsNsdbParams, in the form of a certificate to be used in
>> verifying a TLS server certificate.  There are two notable issues with
>> how the document does this now:
>> 1. Section 4 does not adequately specify how the certificate in the
>> FedFsNsdbParams should be used in the verification process.  Is it to be
>> used as a trust anchor, so that any subordinate certificate is considere=
d
>> valid?  Or perhaps it is to be matched against the end-entity
>> certificate.  In either case, it seems like it would be sufficient to
>> provision a certificate fingerprint (or even a public key fingerprint)
>> instead of the whole certificate.
>> 2. In the security considerations, the document should discuss the
>> implications of provisioning trust information in this way (depending on
>> how it is used), and any requirements for security mechanisms to be used
>> in these cases.
>>=20
>=20
>=20
> I'm going to have to work with the rest of the group to answer this one.
>=20
>=20
>>=20
>> MINOR:
>>=20
>> 2.=20
>> It's not clear what the difference is between utf8string_cs and
>> utf8string_cis.  Should you mention at some point that these MUST be
>> UTF-8, even though the XDR won't enforce that?  (Say, at the beginning o=
f
>> Section 4?)
>=20
>=20
> Argh, we did away with utf8string_cs and utf8string_cis in 3530bis.
>=20
>=20
> utf8string_cis should be utf8val_REQUIRED4
> utf8string_cs should be ascii_REQUIRED4
>=20
> In 3530bis, these are defined as:
>=20
> typedef :opaque  :utf8string<>:UTF-8 encoding for strings.
> typedef :utf8string:utf8_expected:String expected to be UTF-8 but no
> validation
> typedef :utf8string:utf8val_RECOMMENDED4:String SHOULD be sent UTF-8 and
> SHOULD be validated
> typedef :utf8string:utf8val_REQUIRED4:String MUST be sent UTF-8 and MUST
> be validated
> typedef :utf8string:ascii_REQUIRED4:String MUST be sent as ASCII and thus
> is automatically UTF-8
>=20
>=20
> I'll change the types and there is already some text pointing the reader
> to Chapter 12 of 3530bis.
>=20
>=20
>>=20
>> 3.
>> It's not clear to me how FEDFS_ERR_PERM differs from FEDFS_ERR_ACCESS.  =
I
>> don't see it called out for use anywhere in the procedure calls.  Perhap=
s
>> this is a legacy of prior versions that should be deleted?
>=20
>=20
> This is inherited from the base NFSv4.0 documentation and also NFSv3. It
> is also the difference between EPERM and EACCES. (see
> http://www.wlug.org.nz/EACCES)
>=20
>=20
> 13.1.6.1.  NFS4ERR_ACCESS (Error Code 13)
>=20
>   Indicates permission denied.  The caller does not have the correct
>   permission to perform the requested operation.  Contrast this with
>   NFS4ERR_PERM (Section 13.1.6.2), which restricts itself to owner or
>   privileged user permission failures.
>=20
> 13.1.6.2.  NFS4ERR_PERM (Error Code 1)
>=20
>   Indicates requester is not the owner.  The operation was not allowed
>   because the caller is neither a privileged user (root) nor the owner
>   of the target of the operation.
>=20
>=20
>=20
>=20
>=20
>=20
>>=20
>>=20
>> EDITORIAL:=20
>>=20
>> 3.=20
>> The definition of FEDFS_ERR_LOOP isn't actually related to looping.  It
>> seems like this should either detect a loop (e.g., via a repeated name),
>> or be renamed something like FEDFS_ERR_TOOMANYREFERS.
>=20
>=20
> This has its roots in a Linux error code:
>=20
>>> As I recall this error is supposed to be returned when fedfsd is passed
>>> a pathname that contains too many symlinks.  The equivalent errno on
>>> Linux is called ELOOP.
>=20
> We are striving to maintain parity.
>=20
>=20
>=20
>=20
>=20
>>=20
>> 4. "The port is the NSDB transport port for the LDAP interface"
>> Suggest rewording to clarify that this is an LDAP/TCP port (I initially
>> wondered if other transports could be used), e.g.:
>> "The port value in the FedFsNsdbName indicates the LDAP port on the NSDB=
"
>=20
>=20
> Thanks, we've been struggling with this issue, I'll take your suggested
> change here.
>=20
>>=20
>> _______________________________________________
>> nfsv4 mailing list
>> nfsv4@ietf.org
>> https://www.ietf.org/mailman/listinfo/nfsv4
>=20
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4


From geoff@proto6.com  Wed Aug  8 09:34:35 2012
Return-Path: <geoff@proto6.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A4BF21F875A for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 09:34:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.202
X-Spam-Level: 
X-Spam-Status: No, score=-101.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tb0jiOkZR1Sf for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 09:34:33 -0700 (PDT)
Received: from mail.coslabs.com (mail.coslabs.com [199.233.92.34]) by ietfa.amsl.com (Postfix) with ESMTP id 67C9821F8759 for <ietf@ietf.org>; Wed,  8 Aug 2012 09:34:33 -0700 (PDT)
Received: from [192.168.0.36] (unknown [184.99.9.112]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.coslabs.com (Postfix) with ESMTPSA id 2BC1B5F75F; Wed,  8 Aug 2012 10:34:30 -0600 (MDT)
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <01ae01cd7412$abe83e50$03b8baf0$@us>
In-Reply-To: <01ae01cd7412$abe83e50$03b8baf0$@us>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary=Apple-Mail-A1DB5909-CF28-4F4A-8999-99B9BE9992C6
Message-Id: <6BC80C42-9921-4141-B918-4101E873945E@proto6.com>
X-Mailer: iPad Mail (9B206)
From: Geoff Mulligan <geoff@proto6.com>
Subject: Re: So, where to repeat? (was:Re: management granularity)
Date: Wed, 8 Aug 2012 10:34:33 -0600
To: Richard Shockey <richard@shockey.us>
X-Mailman-Approved-At: Wed, 08 Aug 2012 09:50:55 -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, 08 Aug 2012 16:34:35 -0000

--Apple-Mail-A1DB5909-CF28-4F4A-8999-99B9BE9992C6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I also would vote to return to Minneapolis again and again even permanently.=


Geoff




On Aug 6, 2012, at 2:32 PM, "Richard Shockey" <richard@shockey.us> wrote:

> =20
> =20
> [RS> ] +1 and no employer ever argued that going to Minneapolis was a boon=
doggle.  The Hilton in Minneapolis  of all the IETF meetings I=E2=80=99ve at=
tended has the most optimal layout of meeting rooms etc.=20
> =20
> =20
> If we were to choose one place in the U.S. to meet, Minneapolis is the bes=
t choice IMHO.  It's very reasonably priced, easy for many to get to and the=
 hotel has adequate space for us (even back when we had many more attendees)=
.  Personally, the weather is not critical to me, since I spend the vast maj=
ority of my time in the hotel meeting rooms, so I'm very happy if we meet th=
ere in March and November.  =20
> =20
> Mary
> =20
> On Mon, Aug 6, 2012 at 9:18 AM, Dearlove, Christopher (UK) <Chris.Dearlove=
@baesystems.com> wrote:
> I've never been to an IETF meeting where the plane fare has exceeded the h=
otel cost for a week. Caveats to that are that I have mostly gone for IETF r=
ecommended hotels, so may have missed particularly cheap hotels, and that I h=
ave only been to North American and Europe (but that statistic includes Vanc=
ouver and the even further away western US cities down to San Diego). And of=
 course I fly economy, and it's much cheaper including a Saturday night in y=
our trip, even at the cost of an extra night in a hotel (at least it is from=
 here). An almost exception was Paris this year where I was staying fairly c=
heaply, but that was a cost-shared trip between me and my employer, and I di=
dn't fly (I went by train - though that's not cheaper, just better). Paris h=
as cheap(er) hotels and a metro I understand, so I felt less location constr=
ained.
>=20
> --
> Christopher Dearlove
> Senior Principal Engineer, Communications Group
> Communications, Networks and Image Analysis Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194 |  Fax: +44 1245 242124
> chris.dearlove@baesystems.com | http://www.baesystems.com
>=20
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre,=
 Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687
>=20
>=20
> -----Original Message-----
> From: Sprecher, Nurit (NSN - IL/Hod HaSharon) [mailto:nurit.sprecher@nsn.c=
om]
> Sent: 06 August 2012 15:07
> To: Dearlove, Christopher (UK); Daniele Ceccarelli; Andrew Sullivan; ietf@=
ietf.org
> Subject: RE: So, where to repeat? (was:Re: management granularity)
>=20
> ----------------------! WARNING ! ----------------------
> This message originates from outside our organisation,
> either from an external partner or from the internet.
> Keep this in mind if you answer this message.
> Follow the 'Report Suspicious Emails' link on IT matters
> for instructions on reporting suspicious email messages.
> --------------------------------------------------------
>=20
> When you are not close (time), flight cost may become higher in the priori=
ty (over hotem)....
> Flying to Vancouver for me for example is the most expensive trip....even t=
hough the city is amazing and the host was wonderful!
>=20
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of ex=
t Dearlove, Christopher (UK)
> Sent: Monday, August 06, 2012 4:56 PM
> To: Daniele Ceccarelli; Andrew Sullivan; ietf@ietf.org
> Subject: RE: So, where to repeat? (was:Re: management granularity)
>=20
> Dublin's problem was that the venue was isolated from the city. This has a=
lso been the case with e.g. San Diego. (I'm assuming no personal car.) Contr=
ast with Minneapolis (and several other places) where you were right in the c=
ity. Being in a city is better for lunch and dinner options, taking a break t=
o go to a bookshop (or to buy something you forgot to bring) and so on. (I'm=
 deliberately not including tourism here.)
>=20
> However at the moment my priorities to make being able to attend possible w=
ould be time (so the closer to me the better - I realise that's impossible g=
lobally), cost (hotel first, flight second, rest is noise) and the ability t=
o plan ahead to only attend part of the week. This is the current economic r=
eality. Dublin actually scores quite well on those for me.
>=20
> --
> Christopher Dearlove
> Senior Principal Engineer, Communications Group
> Communications, Networks and Image Analysis Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194 |  Fax: +44 1245 242124
> chris.dearlove@baesystems.com | http://www.baesystems.com
>=20
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre,=
 Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687
>=20
>=20
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Da=
niele Ceccarelli
> Sent: 06 August 2012 13:24
> To: Andrew Sullivan; ietf@ietf.org
> Subject: RE: So, where to repeat? (was:Re: management granularity)
>=20
> ----------------------! WARNING ! ----------------------
> This message originates from outside our organisation,
> either from an external partner or from the internet.
> Keep this in mind if you answer this message.
> Follow the 'Report Suspicious Emails' link on IT matters
> for instructions on reporting suspicious email messages.
> --------------------------------------------------------
>=20
> Dublin panned? I thought it was one of the best venues and locations of th=
e last meetings.
>=20
> What about Italy or Spain? I've never heard about an IETF in Italy. I'm ok=
 with meetings outside Italy since i like traveling very much, but i was won=
dering why it has never been taken into account in the past meetings. Is it e=
xpensive? I think Italy and Spain are much cheaper than France, UK or Sweden=
, aren't they?
>=20
> BR
> Daniele
>=20
> >-----Original Message-----
> >From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On
> >Behalf Of Andrew Sullivan
> >Sent: luned=C3=AC 6 agosto 2012 14.06
> >To: ietf@ietf.org
> >Subject: So, where to repeat? (was:Re: management granularity)
> >
> >On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:
> >> enough merely to have excellent staff.  We need to go back to the
> >> better places and benefit from the learning curve.  This
> >doesn't mean
> >> "no new venues" but it means fewer.
> >
> >As a practical matter, may I ask about which venues you want
> >to return to?  I get your argument in principle, but it seems
> >to me that there has been quite a lot of complaining in the
> >past.  The one factor that seems to me most likely to reduce
> >complaints -- weather -- is evidently beyond the Secretariat's
> >or IAOC's control.
> >
> >People seem inclined to return to the Hyatt in Vancouver,
> >elevators notwithstanding.  We're going to do that.  (I don't
> >understand why the previous Vencouver venue was less desirable
> >-- to me, these venues were very similar, and not very far
> >apart.  I note, however, that the previous two Vancouver
> >visits were near the end of the year, when it rains all the
> >time in Vancouver.)
> >
> >People complained at length about the venue in Paris, so I
> >presume it's out.
> >
> >Some people complained about the hotel room prices and travel
> >expense in Taipei, though I heard remarks that it was a good venue.
> >Should we try to return there?
> >
> >People complained in advance about getting to Qu=C3=A9bec, although
> >afterwards I heard lots of good noises about that venue.  I
> >note that the weather was great.  Should we try to return?
> >
> >I don't recall much complaining about the Prague venue in
> >2011, which was striking to me because very little seemed
> >different to me compared to our first visit there.  Perhaps
> >this is evidence of the "tuning"
> >you suggest (ensuring the water bottles were plastic, for instance).
> >But I note the weather was excellent.
> >
> >Beijing?  I guess Maastricht is out. Anaheim (FWIW, I thought
> >that was an example of a terrible location, but many people
> >seemed happy with it)?  Hiroshima?  Stockholm?  San Francisco
> >(we thought the crime at Paris was bad, yet didn't complain
> >about being smack up against the Tenderloin)?  Or there's the
> >old standby, Minneapolis; perhaps we could do it in March.
> >The Dublin venue was panned by large numbers of people.
> >Philadelphia, people complained about expense.  Chicago, too
> >(combined with hotel renovations).
> >
> >That gets us back through 2007.  Which of the venues do you
> >think we should return to, to which we already haven't
> >returned or planned to return?  And why?
> >
> >For what it's worth, I would not complain about returning to
> >any of those venues; I personally had good meetings at all of
> >them except Hiroshima, which I missed due to other
> >commitments.  That includes both Maastricht and Dublin, which
> >were both apparently trials for large numbers of others.
> >
> >Best,
> >
> >A
> >
> >--
> >Andrew Sullivan
> >ajs@anvilwalrusden.com
> >
> >
>=20
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************
>=20
> =20

--Apple-Mail-A1DB5909-CF28-4F4A-8999-99B9BE9992C6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head></head><body bgcolor=3D"#FFFFFF"><div>I also would vote to retur=
n to Minneapolis again and again even permanently.</div><div><br></div><div>=
Geoff</div><div><br><br><br></div><div><br>On Aug 6, 2012, at 2:32 PM, "Rich=
ard Shockey" &lt;<a href=3D"mailto:richard@shockey.us">richard@shockey.us</a=
>&gt; wrote:<br><br></div><div></div><blockquote type=3D"cite"><div><meta ht=
tp-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-1"><meta n=
ame=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)"><style><!-=
-
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{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]--><div class=3D"WordSection1"><p class=3D"Ms=
oNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p><div><p class=
=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></span></p><p c=
lass=3D"MsoNormal"><b><i><span style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">[RS&gt; ] +1 and no emplo=
yer ever argued that going to Minneapolis was a boondoggle.&nbsp; The Hilton=
 in Minneapolis &nbsp;of all the IETF meetings I=E2=80=99ve attended has the=
 most optimal layout of meeting rooms etc. <o:p></o:p></span></i></b></p><p c=
lass=3D"MsoNormal"><b><i><span style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/i></b></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p=
></span></p></div><div><p class=3D"MsoNormal">If we were to choose one place=
 in the U.S. to meet, Minneapolis is the best choice IMHO. &nbsp;It's very r=
easonably priced, easy for many to get to and the hotel has adequate space f=
or us (even back when we had many more attendees). &nbsp;Personally, the wea=
ther is not critical to me, since I spend the vast majority of my time in th=
e hotel meeting rooms, so I'm very happy if we meet there in March and Novem=
ber. &nbsp;&nbsp;<o:p></o:p></p></div><div><p class=3D"MsoNormal"><o:p>&nbsp=
;</o:p></p></div><div><p class=3D"MsoNormal">Mary<o:p></o:p></p><div><p clas=
s=3D"MsoNormal"><o:p>&nbsp;</o:p></p><div><p class=3D"MsoNormal">On Mon, Aug=
 6, 2012 at 9:18 AM, Dearlove, Christopher (UK) &lt;<a href=3D"mailto:Chris.=
Dearlove@baesystems.com" target=3D"_blank">Chris.Dearlove@baesystems.com</a>=
&gt; wrote:<o:p></o:p></p><p class=3D"MsoNormal">I've never been to an IETF m=
eeting where the plane fare has exceeded the hotel cost for a week. Caveats t=
o that are that I have mostly gone for IETF recommended hotels, so may have m=
issed particularly cheap hotels, and that I have only been to North American=
 and Europe (but that statistic includes Vancouver and the even further away=
 western US cities down to San Diego). And of course I fly economy, and it's=
 much cheaper including a Saturday night in your trip, even at the cost of a=
n extra night in a hotel (at least it is from here). An almost exception was=
 Paris this year where I was staying fairly cheaply, but that was a cost-sha=
red trip between me and my employer, and I didn't fly (I went by train - tho=
ugh that's not cheaper, just better). Paris has cheap(er) hotels and a metro=
 I understand, so I felt less location constrained.<o:p></o:p></p><div><p cl=
ass=3D"MsoNormal"><br>--<br>Christopher Dearlove<br>Senior Principal Enginee=
r, Communications Group<br>Communications, Networks and Image Analysis Capab=
ility<br>BAE Systems Advanced Technology Centre<br>West Hanningfield Road, G=
reat Baddow, Chelmsford, CM2 8HN, UK<br>Tel: <a href=3D"tel:%2B44%201245%202=
42194">+44 1245 242194</a>&nbsp;| &nbsp;Fax: <a href=3D"tel:%2B44%201245%202=
42124">+44 1245 242124</a><br><a href=3D"mailto:chris.dearlove@baesystems.co=
m">chris.dearlove@baesystems.com</a> | <a href=3D"http://www.baesystems.com"=
 target=3D"_blank">http://www.baesystems.com</a><br><br>BAE Systems (Operati=
ons) Limited<br>Registered Office: Warwick House, PO Box 87, Farnborough Aer=
ospace Centre, Farnborough, Hants, GU14 6YU, UK<br>Registered in England &am=
p; Wales No: 1996687<br><br><br>-----Original Message-----<o:p></o:p></p></d=
iv><div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">From: Sprecher=
, Nurit (NSN - IL/Hod HaSharon) [mailto:<a href=3D"mailto:nurit.sprecher@nsn=
.com">nurit.sprecher@nsn.com</a>]<br>Sent: 06 August 2012 15:07<br>To: Dearl=
ove, Christopher (UK); Daniele Ceccarelli; Andrew Sullivan; <a href=3D"mailt=
o:ietf@ietf.org">ietf@ietf.org</a><br>Subject: RE: So, where to repeat? (was=
:Re: management granularity)<o:p></o:p></p></div><div><div><p class=3D"MsoNo=
rmal" style=3D"margin-bottom:12.0pt">----------------------! WARNING ! -----=
-----------------<br>This message originates from outside our organisation,<=
br>either from an external partner or from the internet.<br>Keep this in min=
d if you answer this message.<br>Follow the 'Report Suspicious Emails' link o=
n IT matters<br>for instructions on reporting suspicious email messages.<br>=
--------------------------------------------------------<br><br>When you are=
 not close (time), flight cost may become higher in the priority (over hotem=
)....<br>Flying to Vancouver for me for example is the most expensive trip..=
..even though the city is amazing and the host was wonderful!<br><br>-----Or=
iginal Message-----<br>From: <a href=3D"mailto:ietf-bounces@ietf.org">ietf-b=
ounces@ietf.org</a> [mailto:<a href=3D"mailto:ietf-bounces@ietf.org">ietf-bo=
unces@ietf.org</a>] On Behalf Of ext Dearlove, Christopher (UK)<br>Sent: Mon=
day, August 06, 2012 4:56 PM<br>To: Daniele Ceccarelli; Andrew Sullivan; <a h=
ref=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>Subject: RE: So, where to r=
epeat? (was:Re: management granularity)<br><br>Dublin's problem was that the=
 venue was isolated from the city. This has also been the case with e.g. San=
 Diego. (I'm assuming no personal car.) Contrast with Minneapolis (and sever=
al other places) where you were right in the city. Being in a city is better=
 for lunch and dinner options, taking a break to go to a bookshop (or to buy=
 something you forgot to bring) and so on. (I'm deliberately not including t=
ourism here.)<br><br>However at the moment my priorities to make being able t=
o attend possible would be time (so the closer to me the better - I realise t=
hat's impossible globally), cost (hotel first, flight second, rest is noise)=
 and the ability to plan ahead to only attend part of the week. This is the c=
urrent economic reality. Dublin actually scores quite well on those for me.<=
br><br>--<br>Christopher Dearlove<br>Senior Principal Engineer, Communicatio=
ns Group<br>Communications, Networks and Image Analysis Capability<br>BAE Sy=
stems Advanced Technology Centre<br>West Hanningfield Road, Great Baddow, Ch=
elmsford, CM2 8HN, UK<br>Tel: <a href=3D"tel:%2B44%201245%20242194">+44 1245=
 242194</a>&nbsp;| &nbsp;Fax: <a href=3D"tel:%2B44%201245%20242124">+44 1245=
 242124</a><br><a href=3D"mailto:chris.dearlove@baesystems.com">chris.dearlo=
ve@baesystems.com</a> | <a href=3D"http://www.baesystems.com" target=3D"_bla=
nk">http://www.baesystems.com</a><br><br>BAE Systems (Operations) Limited<br=
>Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK<br>Registered in England &amp; Wales No: 19=
96687<br><br><br>-----Original Message-----<br>From: <a href=3D"mailto:ietf-=
bounces@ietf.org">ietf-bounces@ietf.org</a> [mailto:<a href=3D"mailto:ietf-b=
ounces@ietf.org">ietf-bounces@ietf.org</a>] On Behalf Of Daniele Ceccarelli<=
br>Sent: 06 August 2012 13:24<br>To: Andrew Sullivan; <a href=3D"mailto:ietf=
@ietf.org">ietf@ietf.org</a><br>Subject: RE: So, where to repeat? (was:Re: m=
anagement granularity)<br><br>----------------------! WARNING ! ------------=
----------<br>This message originates from outside our organisation,<br>eith=
er from an external partner or from the internet.<br>Keep this in mind if yo=
u answer this message.<br>Follow the 'Report Suspicious Emails' link on IT m=
atters<br>for instructions on reporting suspicious email messages.<br>------=
--------------------------------------------------<br><br>Dublin panned? I t=
hought it was one of the best venues and locations of the last meetings.<br>=
<br>What about Italy or Spain? I've never heard about an IETF in Italy. I'm o=
k with meetings outside Italy since i like traveling very much, but i was wo=
ndering why it has never been taken into account in the past meetings. Is it=
 expensive? I think Italy and Spain are much cheaper than France, UK or Swed=
en, aren't they?<br><br>BR<br>Daniele<br><br>&gt;-----Original Message-----<=
br>&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<br>&gt;Behalf Of Andrew Sullivan<br>&gt;Sent: luned=C3=AC 6 agosto 20=
12 14.06<br>&gt;To: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>&g=
t;Subject: So, where to repeat? (was:Re: management granularity)<br>&gt;<br>=
&gt;On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:<br>&gt;&gt=
; enough merely to have excellent staff. &nbsp;We need to go back to the<br>=
&gt;&gt; better places and benefit from the learning curve. &nbsp;This<br>&g=
t;doesn't mean<br>&gt;&gt; "no new venues" but it means fewer.<br>&gt;<br>&g=
t;As a practical matter, may I ask about which venues you want<br>&gt;to ret=
urn to? &nbsp;I get your argument in principle, but it seems<br>&gt;to me th=
at there has been quite a lot of complaining in the<br>&gt;past. &nbsp;The o=
ne factor that seems to me most likely to reduce<br>&gt;complaints -- weathe=
r -- is evidently beyond the Secretariat's<br>&gt;or IAOC's control.<br>&gt;=
<br>&gt;People seem inclined to return to the Hyatt in Vancouver,<br>&gt;ele=
vators notwithstanding. &nbsp;We're going to do that. &nbsp;(I don't<br>&gt;=
understand why the previous Vencouver venue was less desirable<br>&gt;-- to m=
e, these venues were very similar, and not very far<br>&gt;apart. &nbsp;I no=
te, however, that the previous two Vancouver<br>&gt;visits were near the end=
 of the year, when it rains all the<br>&gt;time in Vancouver.)<br>&gt;<br>&g=
t;People complained at length about the venue in Paris, so I<br>&gt;presume i=
t's out.<br>&gt;<br>&gt;Some people complained about the hotel room prices a=
nd travel<br>&gt;expense in Taipei, though I heard remarks that it was a goo=
d venue.<br>&gt;Should we try to return there?<br>&gt;<br>&gt;People complai=
ned in advance about getting to Qu=C3=A9bec, although<br>&gt;afterwards I he=
ard lots of good noises about that venue. &nbsp;I<br>&gt;note that the weath=
er was great. &nbsp;Should we try to return?<br>&gt;<br>&gt;I don't recall m=
uch complaining about the Prague venue in<br>&gt;2011, which was striking to=
 me because very little seemed<br>&gt;different to me compared to our first v=
isit there. &nbsp;Perhaps<br>&gt;this is evidence of the "tuning"<br>&gt;you=
 suggest (ensuring the water bottles were plastic, for instance).<br>&gt;But=
 I note the weather was excellent.<br>&gt;<br>&gt;Beijing? &nbsp;I guess Maa=
stricht is out. Anaheim (FWIW, I thought<br>&gt;that was an example of a ter=
rible location, but many people<br>&gt;seemed happy with it)? &nbsp;Hiroshim=
a? &nbsp;Stockholm? &nbsp;San Francisco<br>&gt;(we thought the crime at Pari=
s was bad, yet didn't complain<br>&gt;about being smack up against the Tende=
rloin)? &nbsp;Or there's the<br>&gt;old standby, Minneapolis; perhaps we cou=
ld do it in March.<br>&gt;The Dublin venue was panned by large numbers of pe=
ople.<br>&gt;Philadelphia, people complained about expense. &nbsp;Chicago, t=
oo<br>&gt;(combined with hotel renovations).<br>&gt;<br>&gt;That gets us bac=
k through 2007. &nbsp;Which of the venues do you<br>&gt;think we should retu=
rn to, to which we already haven't<br>&gt;returned or planned to return? &nb=
sp;And why?<br>&gt;<br>&gt;For what it's worth, I would not complain about r=
eturning to<br>&gt;any of those venues; I personally had good meetings at al=
l of<br>&gt;them except Hiroshima, which I missed due to other<br>&gt;commit=
ments. &nbsp;That includes both Maastricht and Dublin, which<br>&gt;were bot=
h apparently trials for large numbers of others.<br>&gt;<br>&gt;Best,<br>&gt=
;<br>&gt;A<br>&gt;<br>&gt;--<br>&gt;Andrew Sullivan<br>&gt;<a href=3D"mailto=
:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><br>&gt;<br>&gt;<br><br>*=
*******************************************************************<br>This e=
mail and any attachments are confidential to the intended<br>recipient and m=
ay also be privileged. If you are not the intended<br>recipient please delet=
e it from your system and notify the sender.<br>You should not copy it or us=
e it for any purpose nor disclose or<br>distribute its contents to any other=
 person.<br>****************************************************************=
****<o:p></o:p></p></div></div></div><p class=3D"MsoNormal"><o:p>&nbsp;</o:p=
></p></div></div></div></div></blockquote></body></html>=

--Apple-Mail-A1DB5909-CF28-4F4A-8999-99B9BE9992C6--

From geoff@proto6.com  Wed Aug  8 09:39:10 2012
Return-Path: <geoff@proto6.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 763EC11E8107 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 09:39:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.053
X-Spam-Level: 
X-Spam-Status: No, score=-100.053 tagged_above=-999 required=5 tests=[AWL=-1.149, BAYES_00=-2.599, MANGLED_BEST=2.3, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fZ8bfe1CjKTN for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 09:39:09 -0700 (PDT)
Received: from mail.coslabs.com (mail.coslabs.com [199.233.92.34]) by ietfa.amsl.com (Postfix) with ESMTP id CA20311E80D5 for <ietf@ietf.org>; Wed,  8 Aug 2012 09:39:09 -0700 (PDT)
Received: from [192.168.0.36] (unknown [184.99.9.112]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.coslabs.com (Postfix) with ESMTPSA id 284B15F75F; Wed,  8 Aug 2012 10:39:07 -0600 (MDT)
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <01ae01cd7412$abe83e50$03b8baf0$@us> <3983.1344298475@obiwan.sandelman.ca>
In-Reply-To: <3983.1344298475@obiwan.sandelman.ca>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <DDA0D4A0-4D9D-44A3-A200-CF807D41919F@proto6.com>
X-Mailer: iPad Mail (9B206)
From: Geoff Mulligan <geoff@proto6.com>
Subject: Re: So, where to repeat? (was:Re: management granularity)
Date: Wed, 8 Aug 2012 10:39:10 -0600
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailman-Approved-At: Wed, 08 Aug 2012 09:50:55 -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, 08 Aug 2012 16:39:10 -0000

The Orlando airport is a nightmare almost any time and will be even worse du=
ring this upcoming IETF.  When I had my FlyClear card it was the only airpor=
t where I ever felt that it was necessary.

Avoiding Orlando during the many weeks a spring break would have been good.

Geoff




On Aug 6, 2012, at 6:14 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote=
:

>=20
>> I've never been to an IETF meeting where the plane fare has exceeded the
>> hotel cost for a week.=20
>=20
> note: I pay my own way, and make all my own arrangements.
>=20
> The only meetings where my hotel costs exceeded my transporation costs
> were the Montreal IETFs (I live in Ottawa).  When I've flown I have
> seldom ever been on direct flights.
>=20
> I *do* avoid the main hotel if the price is poor.  I did get the
> Sheraton Wall (backup hotel IETF84), via hotwire.com, which surprised me.
>=20
> I find staying over saturday night no longer has any affect on my travel
> costs.=20
>=20
> I do prefer returning to the same places, and I do like Minneapolis.
> (Yes, even in March and November)
>=20
> I am more concerned that we have three north-american IETFs in a row
> (Vancouver, Atlanta, Orlando), and 4 of the next 6 are in North America.
> (Not counting Hawaii as North America for the purposes of travel
> budgets, or it's be 5/7)
>=20
> I'm also concerned about going popular places (Quebec, Orlando) during
> peak tourist season.=20
>=20
> --=20
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works=20
>=20

From geoff@proto6.com  Wed Aug  8 09:41:24 2012
Return-Path: <geoff@proto6.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3613E21F86FE for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 09:41:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.628
X-Spam-Level: 
X-Spam-Status: No, score=-100.628 tagged_above=-999 required=5 tests=[AWL=0.575, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zt2UhBTgHQ05 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 09:41:23 -0700 (PDT)
Received: from mail.coslabs.com (mail.coslabs.com [199.233.92.34]) by ietfa.amsl.com (Postfix) with ESMTP id C712821F86FD for <ietf@ietf.org>; Wed,  8 Aug 2012 09:41:23 -0700 (PDT)
Received: from [192.168.0.36] (unknown [184.99.9.112]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.coslabs.com (Postfix) with ESMTPSA id 2A16F5F75F; Wed,  8 Aug 2012 10:41:21 -0600 (MDT)
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <29F2EDD3-71B8-4762-8753-5C7AF369001B@tzi.org>
In-Reply-To: <29F2EDD3-71B8-4762-8753-5C7AF369001B@tzi.org>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=utf-8
Message-Id: <15DAC57C-82D5-4261-B0FA-4B700138DA2A@proto6.com>
X-Mailer: iPad Mail (9B206)
From: Geoff Mulligan <geoff@proto6.com>
Subject: Re: So, where to repeat? (was:Re: management granularity)
Date: Wed, 8 Aug 2012 10:41:24 -0600
To: Carsten Bormann <cabo@tzi.org>
X-Mailman-Approved-At: Wed, 08 Aug 2012 09:50:55 -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, 08 Aug 2012 16:41:24 -0000

I liked the hotel and prague was wonderful, but it didn't seem easy to get t=
o cheaply from the US.

Geoff



On Aug 6, 2012, at 6:22 PM, Carsten Bormann <cabo@tzi.org> wrote:

> On Aug 6, 2012, at 16:41, Mary Barnes <mary.ietf.barnes@gmail.com> wrote:
>=20
>> If we were to choose one place in the U.S. to meet, Minneapolis is the be=
st choice IMHO. =20
>=20
> +1 a lot.
> (If we indeed have to choose the US.)
> Great facility to get work done, good food, reasonable flights.
>=20
> And add Prague as the staple for Europe.
>=20
> Gr=C3=BC=C3=9Fe, Carsten
>=20

From dougb@dougbarton.us  Wed Aug  8 09:55:43 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6D8F21F8532 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 09:55:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DgRgGFU1-8Jk for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 09:55:42 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 1DA5F21E8045 for <ietf@ietf.org>; Wed,  8 Aug 2012 09:55:42 -0700 (PDT)
Received: (qmail 9838 invoked by uid 399); 8 Aug 2012 16:55:30 -0000
Received: from unknown (HELO ?192.168.0.101?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 8 Aug 2012 16:55:30 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <50229A06.6020601@dougbarton.us>
Date: Wed, 08 Aug 2012 09:55:34 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: David Conrad <drc@virtualized.org>
Subject: Re: ITU-T Dubai Meeting
References: <20120808051929.717981A12D@ld9781.wdf.sap.corp> <5021F98A.9000509@dougbarton.us> <50221ABA.4020306@gmail.com> <4C14946B-97C8-40C6-BACF-668DF4E5B4D9@virtualized.org>
In-Reply-To: <4C14946B-97C8-40C6-BACF-668DF4E5B4D9@virtualized.org>
X-Enigmail-Version: 1.4.3
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: Wed, 08 Aug 2012 16:55:43 -0000

On 8/8/2012 6:40 AM, David Conrad wrote:
> Imagine my surprise when I just discovered this actually exists

To the extent that anything on wikipedia actually exists ... :)

-- 

    I am only one, but I am one.  I cannot do everything, but I can do
    something.  And I will not let what I cannot do interfere with what
    I can do.
			-- Edward Everett Hale, (1822 - 1909)

From simon.perreault@viagenie.ca  Wed Aug  8 10:08:12 2012
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7F7D21E8047 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 10:08:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level: 
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CgfNY08kDuBD for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 10:08:12 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 2FD0421E8042 for <ietf@ietf.org>; Wed,  8 Aug 2012 10:08:12 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:9ab:7147:49ff:11fa]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 8CCD5400C8 for <ietf@ietf.org>; Wed,  8 Aug 2012 13:08:11 -0400 (EDT)
Message-ID: <50229CFA.8080408@viagenie.ca>
Date: Wed, 08 Aug 2012 13:08:10 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120717 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: So, where to repeat?
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <01ae01cd7412$abe83e50$03b8baf0$@us> <6BC80C42-9921-4141-B918-4101E873945E@proto6.com>
In-Reply-To: <6BC80C42-9921-4141-B918-4101E873945E@proto6.com>
Content-Type: text/plain; charset=UTF-8; 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, 08 Aug 2012 17:08:12 -0000

Le 2012-08-08 12:34, Geoff Mulligan a Ã©crit :
> I also would vote to return to Minneapolis again and again even permanently.

Does nobody care about going to new places so that new people are 
exposed to the IETF and may start getting involved?

We've seen this positive effect many times when we went outside our 
comfort zone...

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From vesely@tana.it  Wed Aug  8 10:09:09 2012
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BBCE21E804C for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 10:09:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.589
X-Spam-Level: 
X-Spam-Status: No, score=-4.589 tagged_above=-999 required=5 tests=[AWL=0.130,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fkHOPV3sgehQ for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 10:09:08 -0700 (PDT)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 8242A21E8048 for <ietf@ietf.org>; Wed,  8 Aug 2012 10:09:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1344445747; bh=4Gmz5BPOcB3Ixs4mLFjn4MAQyrf8SfcYTDjzRUZjWGo=; l=1106; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=T9ubi5bMvbig+P8HPV+xdg/84zTmii8ZU5K5VkwdK7DjHVWURNNT/UbNSIQzyIZox /2k7dyGBP91RhgNYEcByeZJa2lNWo3IkEkAdm7OMONTdu/w5HPckeYixkns69GqRBF EThwcaxuamrdGf0Pu1914ooJaaMtKzrfY50DvzTs=
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, 08 Aug 2012 19:09:07 +0200 id 00000000005DC03F.0000000050229D33.00003A73
Message-ID: <50229D32.8000605@tana.it>
Date: Wed, 08 Aug 2012 19:09:06 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: RFC Errata: when to file, and when not to
References: <CALaySJKV96tdXhzfPD1e1Mro_+gp5aDarF7Z06QrA+iQtnHkLw@mail.gmail.com><501A5656.2050407@it.aoyama.ac.jp> <501BEC0D.1060404@tana.it> <009101cd7476$bb522c20$4001a8c0@gateway.2wire.net> <599B1629-543A-49BC-A0E7-FA2096C538AD@checkpoint.com> <03e701cd749f$73891c40$4001a8c0@gateway.2wire.net>
In-Reply-To: <03e701cd749f$73891c40$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: Wed, 08 Aug 2012 17:09:09 -0000

On Tue 07/Aug/2012 15:20:35 +0200 t.p. wrote:
> From: "Yoav Nir" <ynir@checkpoint.com>
> 
>> Would it make it easier to find if they were called "notes" or
>> "corrections" instead of "errata"?
>
> Yes, corrections is what I see published in a newspaper to correct 
> errata in previous editions.  So far, it is the best word I can
> think of (but there might be a better one:-).

Errata is an abbreviation of "errata corrige", the Latin for "error
correction".  Switching to the English translation would seem to be
consistent with English being the official publication language for RFCs.

> In the html version of an RFC, it would be easy to provide old and new
> in an easy to compare format (as some editors do for I-D), not perhaps
> on permanent display but shown when 'errata' (or whatever name we
> choose) is toggled.

Although easy, doing that would require a noticeable amount of
editorial work.  In addition, notes, reasons, and explanations don't
have an obvious graphical rendition.  IMHO, knowing when and why an
errata was proposed and verified is an integral part of it.


From ynir@checkpoint.com  Wed Aug  8 11:06:58 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E335C21F85CD for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 11:06:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.385
X-Spam-Level: 
X-Spam-Status: No, score=-10.385 tagged_above=-999 required=5 tests=[AWL=0.214, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T6bf4oaXbPBc for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 11:06:58 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 1772921F85C7 for <ietf@ietf.org>; Wed,  8 Aug 2012 11:06:54 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id q78I6q3Z018734; Wed, 8 Aug 2012 21:06:53 +0300
X-CheckPoint: {5022A7D7-0-1B221DC2-4FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Wed, 8 Aug 2012 21:06:52 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Geoff Mulligan <geoff@proto6.com>
Date: Wed, 8 Aug 2012 21:06:56 +0300
Subject: Re: So, where to repeat? (was:Re: management granularity)
Thread-Topic: So, where to repeat? (was:Re: management granularity)
Thread-Index: Ac11kJY38wMhT5bOSr+YYKLt4ERMaQ==
Message-ID: <79811B0A-FA21-456A-8016-BF20DF3FBD95@checkpoint.com>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net>	<20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <29F2EDD3-71B8-4762-8753-5C7AF369001B@tzi.org> <15DAC57C-82D5-4261-B0FA-4B700138DA2A@proto6.com>
In-Reply-To: <15DAC57C-82D5-4261-B0FA-4B700138DA2A@proto6.com>
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Carsten Bormann <cabo@tzi.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 18:06:59 -0000

Mileage varies.=20

For me it was the shortest and cheapest flight of any IETF meeting I have a=
ttended.

Yoav

On Aug 8, 2012, at 7:41 PM, Geoff Mulligan wrote:

> I liked the hotel and prague was wonderful, but it didn't seem easy to ge=
t to cheaply from the US.
>=20
> Geoff
>=20
>=20
>=20
> On Aug 6, 2012, at 6:22 PM, Carsten Bormann <cabo@tzi.org> wrote:
>=20
>> On Aug 6, 2012, at 16:41, Mary Barnes <mary.ietf.barnes@gmail.com> wrote=
:
>>=20
>>> If we were to choose one place in the U.S. to meet, Minneapolis is the =
best choice IMHO. =20
>>=20
>> +1 a lot.
>> (If we indeed have to choose the US.)
>> Great facility to get work done, good food, reasonable flights.
>>=20
>> And add Prague as the staple for Europe.
>>=20
>> Gr=FC=DFe, Carsten


From nurit.sprecher@nsn.com  Wed Aug  8 11:14:15 2012
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 EB0D821F8647 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 11:14:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.447
X-Spam-Level: 
X-Spam-Status: No, score=-6.447 tagged_above=-999 required=5 tests=[AWL=0.152,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M28apuE4nR0w for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 11:14:15 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 00B9F21F84F8 for <ietf@ietf.org>; Wed,  8 Aug 2012 11:14:14 -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 q78IE4F7029717 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 8 Aug 2012 20:14:04 +0200
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q78IE4bt009286; Wed, 8 Aug 2012 20:14:04 +0200
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 8 Aug 2012 20:13:16 +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: So, where to repeat? (was:Re: management granularity)
Date: Wed, 8 Aug 2012 20:13:23 +0200
Message-ID: <E4873516F3FC7547BCFE792C7D94039C0236B100@DEMUEXC013.nsn-intra.net>
In-Reply-To: <79811B0A-FA21-456A-8016-BF20DF3FBD95@checkpoint.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: So, where to repeat? (was:Re: management granularity)
Thread-Index: Ac11kJY38wMhT5bOSr+YYKLt4ERMaQAAOcaA
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com><501EC24B.4080709@bbiw.net>	<20120806120547.GA20379@crankycanuck.ca><B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se><B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net><E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net><B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net><CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com><29F2EDD3-71B8-4762-8753-5C7AF369001B@tzi.org><15DAC57C-82D5-4261-B0FA-4B700138DA2A@proto6.com> <79811B0A-FA21-456A-8016-BF20DF3FBD95@checkpoint.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext Yoav Nir" <ynir@checkpoint.com>, "Geoff Mulligan" <geoff@proto6.com>
X-OriginalArrivalTime: 08 Aug 2012 18:13:16.0743 (UTC) FILETIME=[7B912570:01CD7591]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 1081
X-purgate-ID: 151667::1344449644-000055D8-E7636283/0-0/0-0
Cc: Carsten Bormann <cabo@tzi.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 18:14:16 -0000

+1

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of =
ext Yoav Nir
Sent: Wednesday, August 08, 2012 9:07 PM
To: Geoff Mulligan
Cc: Carsten Bormann; ietf@ietf.org
Subject: Re: So, where to repeat? (was:Re: management granularity)

Mileage varies.=20

For me it was the shortest and cheapest flight of any IETF meeting I =
have attended.

Yoav

On Aug 8, 2012, at 7:41 PM, Geoff Mulligan wrote:

> I liked the hotel and prague was wonderful, but it didn't seem easy to =
get to cheaply from the US.
>=20
> Geoff
>=20
>=20
>=20
> On Aug 6, 2012, at 6:22 PM, Carsten Bormann <cabo@tzi.org> wrote:
>=20
>> On Aug 6, 2012, at 16:41, Mary Barnes <mary.ietf.barnes@gmail.com> =
wrote:
>>=20
>>> If we were to choose one place in the U.S. to meet, Minneapolis is =
the best choice IMHO. =20
>>=20
>> +1 a lot.
>> (If we indeed have to choose the US.)
>> Great facility to get work done, good food, reasonable flights.
>>=20
>> And add Prague as the staple for Europe.
>>=20
>> Gr=FC=DFe, Carsten


From stpeter@stpeter.im  Wed Aug  8 11:18:55 2012
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 A97D921F86DA for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 11:18:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eEkFVg7LjGWu for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 11:18:55 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 0F4E521F869C for <ietf@ietf.org>; Wed,  8 Aug 2012 11:18:55 -0700 (PDT)
Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 7E54F4013D; Wed,  8 Aug 2012 12:18:59 -0600 (MDT)
Message-ID: <5022AD8C.4020205@stpeter.im>
Date: Wed, 08 Aug 2012 12:18:52 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: So, where to repeat?
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net>	<20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <29F2EDD3-71B8-4762-8753-5C7AF369001B@tzi.org> <15DAC57C-82D5-4261-B0FA-4B700138DA2A@proto6.com> <79811B0A-FA21-456A-8016-BF20DF3FBD95@checkpoint.com>
In-Reply-To: <79811B0A-FA21-456A-8016-BF20DF3FBD95@checkpoint.com>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Geoff Mulligan <geoff@proto6.com>, Carsten Bormann <cabo@tzi.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 18:18:55 -0000

On 8/8/12 12:06 PM, Yoav Nir wrote:
> Mileage varies. 
> 
> For me it was the shortest and cheapest flight of any IETF meeting I have attended.

If we discussed protocols the way we discuss venue sites, all would be
lost. "Oh, this feature works great for me, therefore let's include it
in the spec."

Perhaps we might consider ending these interminable venue discussions
and just complain three times a year when we visit a place that the IAOC
has selected?

Peter

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



From dhc@dcrocker.net  Wed Aug  8 11:30:40 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C49321F851B for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 11:30:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.59
X-Spam-Level: 
X-Spam-Status: No, score=-6.59 tagged_above=-999 required=5 tests=[AWL=0.009,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0xgYh-XXVRE8 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 11:30:39 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id E493C21F850B for <ietf@ietf.org>; Wed,  8 Aug 2012 11:30:38 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q78IUU1F007565 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 8 Aug 2012 11:30:30 -0700
Message-ID: <5022B03F.5000904@dcrocker.net>
Date: Wed, 08 Aug 2012 11:30:23 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: So, where to repeat?
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net>	<20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <29F2EDD3-71B8-4762-8753-5C7AF369001B@tzi.org> <15DAC57C-82D5-4261-B0FA-4B700138DA2A@proto6.com> <79811B0A-FA21-456A-8016-BF20DF3FBD95@checkpoint.com> <5022AD8C.4020205@stpeter.im>
In-Reply-To: <5022AD8C.4020205@stpeter.im>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 08 Aug 2012 11:30:31 -0700 (PDT)
Cc: Geoff Mulligan <geoff@proto6.com>, Carsten Bormann <cabo@tzi.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 18:30:40 -0000

On 8/8/2012 11:18 AM, Peter Saint-Andre wrote:
> Perhaps we might consider ending these interminable venue discussions
> and just complain three times a year when we visit a place that the IAOC
> has selected?


now i'm completely confused.

i thought that that was/is exactly what's being done...

d/

ps. btw, what is it that you think is different about this from the way 
we /do/ discuss protocol specs?

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From dcrocker@bbiw.net  Wed Aug  8 11:49:32 2012
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99BA221F8624 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 11:49:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.547
X-Spam-Level: 
X-Spam-Status: No, score=-6.547 tagged_above=-999 required=5 tests=[AWL=0.052,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rg-cD4DUYY4Y for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 11:49:31 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id B31F921F84EC for <ietf@ietf.org>; Wed,  8 Aug 2012 11:49:31 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q78InSEc008016 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 8 Aug 2012 11:49:29 -0700
Message-ID: <5022B4B2.8040904@bbiw.net>
Date: Wed, 08 Aug 2012 11:49:22 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Geoff Mulligan <geoff@proto6.com>
Subject: Re: So, where to repeat? (was: Re: management granularity)
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com>
In-Reply-To: <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.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, 08 Aug 2012 11:49:29 -0700 (PDT)
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, 08 Aug 2012 18:49:32 -0000

On 8/8/2012 11:46 AM, Geoff Mulligan wrote:
> So then why not consider, London, Paris (not the Concorde Lafayette), Frankfurt, Amsterdam?


shockingly, amsterdam can't handle the ietf.  wrong mix of resources. 
really.

paris appears to have broad crime and work-ethic patterns that also are 
problematic, not just at the concorde.

to be clear: i'm speaking for myself.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From ole@cisco.com  Wed Aug  8 12:07:00 2012
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22DE421F867A for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 12:07:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.565
X-Spam-Level: 
X-Spam-Status: No, score=-110.565 tagged_above=-999 required=5 tests=[AWL=0.034, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TIegHgJrR3Dy for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 12:06:59 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id E869C21F8671 for <ietf@ietf.org>; Wed,  8 Aug 2012 12:06:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=752; q=dns/txt; s=iport; t=1344452819; x=1345662419; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=ZKBjN6igY0EtfIAT/rpqfol6lA2xzfaYYRparjbuh2Y=; b=jd9OP1GoXsa8IC/igmt1x8slhHS2kHPqOKTPE3081aa7cxLkkel/t8Cs ToaiwT0IT2FMyxrIUEOQQSVcORku8VJiCcDyexHdb3XP9JOBA8spoKmCl BFgiQ4YsP5JBH/f3MxvYuKVp554GcRr2lO+X3SvwZgmLp+QXdBsp/qu/4 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgkFAK64IlCrRDoJ/2dsb2JhbABCA4U6tCaBB4IgAQEBAwESAQIlPwULC0ZXBhMih2UFmxqDSBCca4sSGAKDJYMhA4hOkleFMYMcgQRign+BPw
X-IronPort-AV: E=Sophos;i="4.77,734,1336348800"; d="scan'208";a="54460718"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-2.cisco.com with ESMTP; 08 Aug 2012 19:06:51 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q78J6oLj017230 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Aug 2012 19:06:50 GMT
Date: Wed, 8 Aug 2012 12:06:50 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Geoff Mulligan <geoff@proto6.com>
Subject: Re: So, where to repeat? (was: Re: management granularity)
In-Reply-To: <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com>
Message-ID: <alpine.OSX.2.01.1208081204190.24762@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: Richard Shockey <richard@shockey.us>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 19:07:00 -0000

Geoff,

What are you talking about? Of course we are "considering" all of 
those places. We are going to London in 2014 for example, we went to 
Paris this year. But, like with all popular places, finding venues 
available for OUR dates is not easy. Add to that the costs and you 
will understand why we don't meet in London or Paris or Frankfurt or 
Amsterdam more often.

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Wed, 8 Aug 2012, Geoff Mulligan wrote:

> So then why not consider, London, Paris (not the Concorde 
> Lafayette), Frankfurt, Amsterdam?
> 

From sm@resistor.net  Wed Aug  8 12:57:10 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A592321F8639 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 12:57:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level: 
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lS3PgN5IKSPv for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 12:57:06 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9470B21F861C for <ietf@ietf.org>; Wed,  8 Aug 2012 12:57:06 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q78Jv0h4019843; Wed, 8 Aug 2012 12:57:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1344455825; bh=jmBaSrtKdhzBA4gaNm5RYuhg+gy5CTlHV1B94Zgxt30=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=a17dNc/kxeU6go8NFyemMvYzzykolC/MOCHQJdt3XZBsP44Zn8WzF/3vUaYOyRBGG JAW4MegfY0h7BroqNiSpIg0fi0fR7b5HqH9v6tWJ6qtoBJJA48Po3LSgrAKmCEEv1t uEnxCkgJPD6yDJVrZyOt5Y8Ken17JjiQUJqBnYu8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1344455825; i=@resistor.net; bh=jmBaSrtKdhzBA4gaNm5RYuhg+gy5CTlHV1B94Zgxt30=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=oOnbQhoFDPu/IcjEgopLWr6VzDVYThSmnbifn29i1GEHph1q2uTA/RqI2R4SAK973 7Y7MEEPRTcL3H6lYhxQwo2CvYjUwhIFumsVsnyDF2DGQqzNu5j68n5M5+qeT/UEmzH hkl0hI6FCL9B+KMc/1Evc0vl/ysLNh9fOQ+1kCrk=
Message-Id: <6.2.5.6.2.20120808114731.0d7d2440@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 08 Aug 2012 12:38:44 -0700
To: Peter Saint-Andre <stpeter@stpeter.im>
From: SM <sm@resistor.net>
Subject: Re: So, where to repeat?
In-Reply-To: <5022AD8C.4020205@stpeter.im>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <29F2EDD3-71B8-4762-8753-5C7AF369001B@tzi.org> <15DAC57C-82D5-4261-B0FA-4B700138DA2A@proto6.com> <79811B0A-FA21-456A-8016-BF20DF3FBD95@checkpoint.com> <5022AD8C.4020205@stpeter.im>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 19:57:10 -0000

Hi Peter,
At 11:18 08-08-2012, Peter Saint-Andre wrote:
>If we discussed protocols the way we discuss venue sites, all would be
>lost. "Oh, this feature works great for me, therefore let's include it
>in the spec."

That's how protocols are discussed. :-)

>Perhaps we might consider ending these interminable venue discussions
>and just complain three times a year when we visit a place that the IAOC
>has selected?

Here's a quick snapshot.

  Quebec has been in the exact same location for over 400 years.  The city
  has historic monuments which are insulting to the Americans who failed
  to capture the city in 1775. [1]

  Brand-new conference centre, canonical hotel is a Hilton, and
  boy can I show you some bars... [2]

  Nothing is "a reasonable walk" when the average temperature is 32 C.
  At least not for the "average" IETF attendee. [3]

  You'd be eligible to vote if you'd attended an IETF anytime within the past,
  say, 2 years - or if you were willing to commit to attending the one you vote
  on if it wins. [4]

  There are a host of reasons that voting is a stupid decision making 
process. I
  thought we knew that. [5]

  Now, we should maybe calibrate that in something other than USD (maybe in
  milligrams of gold, or the Economist's Bic Mac index) and also find an
  independent source on hotel price inflation. [6]

  According to the stats, since IETF-1, there have been 6 IETF meetings in
  Minneapolis.  Every one of them had significantly lower number of 
participants
  than the meeting before  and after them... except IETF-44 which was 
lower than
  IETF-43 but about the same as IETF-45, but IETF-45 was in Oslo, Norway, and
  IETF-46 went back up to higher levels again. [7]

  Maastricht Bans Cannabis Coffee-Shop Tourists [8]

  The social was held at an abbey that had wonderful dark beer in 1 
litre steins.
  I discovered that it's best to drink only one, if flying home at 
30,000 feet the
  next day. [9]

  Obviously, not enough Canadians from outside Toronto were asked.
  Everyone in the country loves to hate Toronto. [10]

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/ietf/current/msg66962.html
2. http://www.ietf.org/mail-archive/web/ietf/current/msg68326.html
3. http://www.ietf.org/mail-archive/web/ietf/current/msg68330.html
4. http://www.ietf.org/mail-archive/web/ietf/current/msg68655.html
5. http://www.ietf.org/mail-archive/web/ietf/current/msg68681.html
6. http://www.ietf.org/mail-archive/web/ietf/current/msg68682.html
7. http://www.ietf.org/mail-archive/web/ietf/current/msg68729.html
8. http://www.ietf.org/mail-archive/web/ietf/current/msg69714.html
9. http://www.ietf.org/mail-archive/web/ietf/current/msg70647.html
10. http://www.ietf.org/mail-archive/web/ietf/current/msg70653.html 


From mary.ietf.barnes@gmail.com  Wed Aug  8 13:38:34 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40B0121F8648 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 13:38:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.697
X-Spam-Level: 
X-Spam-Status: No, score=-102.697 tagged_above=-999 required=5 tests=[AWL=-0.765, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UDBjyVO1VbrH for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 13:38:33 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0E70E21F8639 for <ietf@ietf.org>; Wed,  8 Aug 2012 13:38:32 -0700 (PDT)
Received: by lbbgg6 with SMTP id gg6so750569lbb.31 for <ietf@ietf.org>; Wed, 08 Aug 2012 13:38:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=z92yXjiax3txR6qz1Hi5qa5G12ety9JAkI4oCsidUBc=; b=ls5weRHnDitdpMEOqA0qBE6LMHR3+kDdRkWulUA0Po0sTiACvSApKikWgKoTQF5DGT Li9X5ZoMsPsFMNYtqcvJ//BJ6gR8xoN7ApgTmQ75yaRdwxbpem7iTx1Z7c/HtixgN1FD o5u4y0+asx59NLdubSaxaarYaCpSV2AuhQo6q62pzCLzldaWCzZo5rqXoFNDHmzAg3Ur MbMGXsgBacUAYylFXa5MC6srv7c5QmMkLipHsfqB2PNtVwnAoBqk6yjuj1bM1MCYUvNp Dwt9vq4xzOSjnVJNPMlZan3J0zeUk27M2VooTdmEESQbeOlpXsGn4Jzfi03IeZiiffIO FSQQ==
MIME-Version: 1.0
Received: by 10.112.86.132 with SMTP id p4mr8240844lbz.22.1344458311854; Wed, 08 Aug 2012 13:38:31 -0700 (PDT)
Received: by 10.112.85.196 with HTTP; Wed, 8 Aug 2012 13:38:31 -0700 (PDT)
Date: Wed, 8 Aug 2012 15:38:31 -0500
Message-ID: <CAHBDyN70JABA4SrQGjJGTZTZyeA611tdRJB_+QL7VBJTaCRAVQ@mail.gmail.com>
Subject: Meetecho session recording for IETF-84 Telepresence (CLUE) Tutorial
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: IETF-Discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=bcaec554d52217ecf804c6c7188d
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 20:38:34 -0000

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

Hi all,

Many of you were aware that we held a Telepresence (CLUE) tutorial Monday
lunchtime.  We had about 60 attendees.  A Meetecho recording of the session
is available.   The link is below.  If you've never had the time to watch a
Meetecho session recording, this would be a good opportunity. The audio,
video, slides and jabber session are all synched.

Regards,
Mary
CLUE WG co-chair

---------- Forwarded message ----------
From: Meetecho IETF support <ietf@meetecho.com>
Date: Thu, Aug 2, 2012 at 4:50 PM
Subject: [clue] Meetecho session recordings available
To: clue@ietf.org


Dear all,

the full recording (synchronized video, audio, slides and jabber room)
of the three CLUE sessions at IETF-84 are available.

You can watch them by accessing the following URLs:

CLUE I:
http://ietf84.conf.meetecho.**com/index.php/Recorded_**Sessions#IETF84_CLUE<http://ietf84.conf.meetecho.com/index.php/Recorded_Sessions#IETF84_CLUE>

CLUE II:
http://ietf84.conf.meetecho.**com/index.php/Recorded_**
Sessions#IETF84_CLUE_II<http://ietf84.conf.meetecho.com/index.php/Recorded_Sessions#IETF84_CLUE_II>

CLUE Tutorial:
http://ietf84.conf.meetecho.**com/index.php/Recorded_**
Sessions#IETF84_CLUE_TUTORIAL<http://ietf84.conf.meetecho.com/index.php/Recorded_Sessions#IETF84_CLUE_TUTORIAL>

For the chair(s): please feel free to put the link to the recording in the
minutes, if you think this might be useful.

In case of problems with the playout, just drop an e-mail to
team@meetecho.com.

Cheers,
the Meetecho team

-- 
Meetecho s.r.l.
Web Conferencing and Collaboration Tools
www.meetecho.com

______________________________**_________________
clue mailing list
clue@ietf.org
https://www.ietf.org/mailman/**listinfo/clue<https://www.ietf.org/mailman/listinfo/clue>

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

Hi all,<div><br></div><div>Many of you were aware that we held a Telepresen=
ce (CLUE) tutorial Monday lunchtime. =A0We had about 60 attendees. =A0A Mee=
techo recording of the session is available. =A0 The link is below. =A0If y=
ou&#39;ve never had the time to watch a Meetecho session recording, this wo=
uld be a good opportunity. The audio, video, slides and jabber session are =
all synched.</div>
<div><br></div><div>Regards,</div><div>Mary</div><div>CLUE WG co-chair<br><=
br><div class=3D"gmail_quote">---------- Forwarded message ----------<br>Fr=
om: <b class=3D"gmail_sendername">Meetecho IETF support</b> <span dir=3D"lt=
r">&lt;<a href=3D"mailto:ietf@meetecho.com">ietf@meetecho.com</a>&gt;</span=
><br>
Date: Thu, Aug 2, 2012 at 4:50 PM<br>Subject: [clue] Meetecho session recor=
dings available<br>To: <a href=3D"mailto:clue@ietf.org">clue@ietf.org</a><b=
r><br><br>Dear all,<br>
<br>
the full recording (synchronized video, audio, slides and jabber room)<br>
of the three CLUE sessions at IETF-84 are available.<br>
<br>
You can watch them by accessing the following URLs:<br>
<br>
CLUE I:<br>
<a href=3D"http://ietf84.conf.meetecho.com/index.php/Recorded_Sessions#IETF=
84_CLUE" target=3D"_blank">http://ietf84.conf.meetecho.<u></u>com/index.php=
/Recorded_<u></u>Sessions#IETF84_CLUE</a><br>
<br>
CLUE II:<br>
<a href=3D"http://ietf84.conf.meetecho.com/index.php/Recorded_Sessions#IETF=
84_CLUE_II" target=3D"_blank">http://ietf84.conf.meetecho.<u></u>com/index.=
php/Recorded_<u></u>Sessions#IETF84_CLUE_II</a><br>
<br>
CLUE Tutorial:<br>
<a href=3D"http://ietf84.conf.meetecho.com/index.php/Recorded_Sessions#IETF=
84_CLUE_TUTORIAL" target=3D"_blank">http://ietf84.conf.meetecho.<u></u>com/=
index.php/Recorded_<u></u>Sessions#IETF84_CLUE_TUTORIAL</a><br>
<br>
For the chair(s): please feel free to put the link to the recording in the =
minutes, if you think this might be useful.<br>
<br>
In case of problems with the playout, just drop an e-mail to <a href=3D"mai=
lto:team@meetecho.com" target=3D"_blank">team@meetecho.com</a>.<br>
<br>
Cheers,<br>
the Meetecho team<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
-- <br>
Meetecho s.r.l.<br>
Web Conferencing and Collaboration Tools<br>
<a href=3D"http://www.meetecho.com" target=3D"_blank">www.meetecho.com</a><=
br>
<br>
______________________________<u></u>_________________<br>
clue mailing list<br>
<a href=3D"mailto:clue@ietf.org" target=3D"_blank">clue@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/clue" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/clue</a><br>
</font></span></div><br></div>

--bcaec554d52217ecf804c6c7188d--

From johnl@iecc.com  Wed Aug  8 13:52:56 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B83A921F860B for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 13:52:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.159
X-Spam-Level: 
X-Spam-Status: No, score=-111.159 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mM9kVmf1DSn6 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 13:52:55 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 4522021F8605 for <ietf@ietf.org>; Wed,  8 Aug 2012 13:52:43 -0700 (PDT)
Received: (qmail 77274 invoked from network); 8 Aug 2012 20:52:42 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 8 Aug 2012 20:52:42 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5022d19a.xn--hew.k1208; i=johnl@user.iecc.com; bh=3Kro8GXUwH8LNDHJVleLtoGTQdeku/bitsMSJitD2Wc=; b=SUmXcHJnmfb52x8pNQWAQDkyE73rTEryWrbd5vrnA3xd5a21BWlfcdWJGriI2GFh0agDnHflZqLw+z61nOrUEYdnMABrYSjORPiZqwZWmK3CkcqkMfm5Siw3Mke4gvlcSGzIApf1VsBi1tmgJQ6SZGpgSLNgBCTu1KLT7by/wI4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5022d19a.xn--hew.k1208; olt=johnl@user.iecc.com; bh=3Kro8GXUwH8LNDHJVleLtoGTQdeku/bitsMSJitD2Wc=; b=YMm2Uj06cB49omJWDaLECXWLJwkHfmefAkTpkEKlB1PZciZ7oqMsPjfCriaaencLZgruMse9jiwgyx92d+/QfJbmswJvX4E2poBea3J22gUt+ww7VozuyACjmcKe13V2YshEUsJvoqj/V+nP7+QPz6JaCIxvX7k94U/Sf672OOk=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 8 Aug 2012 20:52:20 -0000
Message-ID: <20120808205220.11419.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: So, where to repeat?
In-Reply-To: <5022B03F.5000904@dcrocker.net>
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, 08 Aug 2012 20:52:56 -0000

>ps. btw, what is it that you think is different about this from the way 
>we /do/ discuss protocol specs?

People discussing venues are less willing to believe that anyone
else's experience or issues differ from their own.

R's,
John

From cabo@tzi.org  Wed Aug  8 15:33:44 2012
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24B6921F84EB for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 15:33:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.35
X-Spam-Level: 
X-Spam-Status: No, score=-106.35 tagged_above=-999 required=5 tests=[AWL=-0.101, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PlGzlZvJBHw5 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 15:33:43 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 5ABC221F84F1 for <ietf@ietf.org>; Wed,  8 Aug 2012 15:33:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q78MXZID021501; Thu, 9 Aug 2012 00:33:35 +0200 (CEST)
Received: from [192.168.217.117] (p548945C1.dip.t-dialin.net [84.137.69.193]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 2DE623A2; Thu,  9 Aug 2012 00:33:34 +0200 (CEST)
Subject: Re: Meetecho session recording for IETF-84 Telepresence (CLUE) Tutorial
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAHBDyN70JABA4SrQGjJGTZTZyeA611tdRJB_+QL7VBJTaCRAVQ@mail.gmail.com>
Date: Thu, 9 Aug 2012 00:33:27 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <8FEE254D-9256-4DDF-894F-6F046B4D6E2E@tzi.org>
References: <CAHBDyN70JABA4SrQGjJGTZTZyeA611tdRJB_+QL7VBJTaCRAVQ@mail.gmail.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
X-Mailer: Apple Mail (2.1485)
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, 08 Aug 2012 22:33:44 -0000

On Aug 8, 2012, at 22:38, Mary Barnes <mary.ietf.barnes@gmail.com> =
wrote:

>  If you've never had the time to watch a Meetecho session recording,

OMG, was the audio recovered from air bubbling up from a submarine or =
what happened?

Oh, and maybe somebody can explain the value of the audio spectrum above =
4 kHz to the meetecho guys.

With this audio quality, this is very close to useless (except maybe for =
historians digging it up 5000 years in the future and painstakingly =
reconstructing what was maybe said).

Gr=FC=DFe, Carsten


From mary.ietf.barnes@gmail.com  Wed Aug  8 15:37:37 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF61A11E8104 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 15:37:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.523
X-Spam-Level: 
X-Spam-Status: No, score=-103.523 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6ij7JQapgWt8 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 15:37:37 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id D14D411E80FE for <ietf@ietf.org>; Wed,  8 Aug 2012 15:37:36 -0700 (PDT)
Received: by lbbgg6 with SMTP id gg6so799303lbb.31 for <ietf@ietf.org>; Wed, 08 Aug 2012 15:37:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ZPfhryYXHU9co3X50gXmOdp8RadCSCF3DTqrT1jPBo0=; b=PM/3y6i5rod9yiHLcJWnccltFmkSxsU5jYTRBJGZpQnPmrThRhsEGUwdlOgZMf1yUS Hx+ZhvgG4h40zbbftjNv/ZPUL5UeFH9AQWDv7lMPbxTpBWg5xMLgnALLXTkSdpvgvJoa jcasBt9orBALu9BmIpHaUBE7XF0s00icjmXSDq1UgixfwQMYT95iPel00sWy9Lnu9wMO /JeYFbSAqTBA4FDfjLJEO8ROHcbxzL3HYqAhDgb7kwKzP8Ld4cy3wJwVTQkocHe954G1 ZyKqK1nSwv+2Nt0q577C+YEQ4eeXxa0iEtwrtXffC36KXP0LhfGPIX6lrJluFSBa4dBQ sJOg==
MIME-Version: 1.0
Received: by 10.152.112.234 with SMTP id it10mr16737071lab.36.1344465455835; Wed, 08 Aug 2012 15:37:35 -0700 (PDT)
Received: by 10.112.85.196 with HTTP; Wed, 8 Aug 2012 15:37:35 -0700 (PDT)
In-Reply-To: <8FEE254D-9256-4DDF-894F-6F046B4D6E2E@tzi.org>
References: <CAHBDyN70JABA4SrQGjJGTZTZyeA611tdRJB_+QL7VBJTaCRAVQ@mail.gmail.com> <8FEE254D-9256-4DDF-894F-6F046B4D6E2E@tzi.org>
Date: Wed, 8 Aug 2012 17:37:35 -0500
Message-ID: <CAHBDyN4J8Eyr59S9O0XPYW8aORuYXrTTVafs20sqWm=kMA7zoA@mail.gmail.com>
Subject: Re: Meetecho session recording for IETF-84 Telepresence (CLUE) Tutorial
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary=f46d04083919e8690204c6c8c16c
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, 08 Aug 2012 22:37:37 -0000

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

It's surely not perfect, but given the technology being used, it's
certainly good enough and I find having the video and presentations synched
is far superior to just listening to the regular audio stream.  You can
turn off audio on Meetecho and use the regular audio stream, but the audio
will be delayed.

As a chair, I find it very useful to use the recorded session to double
check my notes or sometimes clarify notes by the notetakers.

It's also extremely important to consider that these guys are providing the
service at no cost to IETF.  I can't fathom what the cost would be if IETF
were paying for something that might meet your quality standards.

Regards,
Mary.

On Wed, Aug 8, 2012 at 5:33 PM, Carsten Bormann <cabo@tzi.org> wrote:

> On Aug 8, 2012, at 22:38, Mary Barnes <mary.ietf.barnes@gmail.com> wrote:
>
> >  If you've never had the time to watch a Meetecho session recording,
>
> OMG, was the audio recovered from air bubbling up from a submarine or wha=
t
> happened?
>
> Oh, and maybe somebody can explain the value of the audio spectrum above =
4
> kHz to the meetecho guys.
>
> With this audio quality, this is very close to useless (except maybe for
> historians digging it up 5000 years in the future and painstakingly
> reconstructing what was maybe said).
>
> Gr=FC=DFe, Carsten
>
>

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

It&#39;s surely not perfect, but given the technology being used, it&#39;s =
certainly good enough and I find having the video and presentations synched=
 is far superior to just listening to the regular audio stream. =A0You can =
turn off audio on Meetecho and use the regular audio stream, but the audio =
will be delayed.=A0<div>
<br></div><div>As a chair, I find it very useful to use the recorded sessio=
n to double check my notes or sometimes clarify notes by the notetakers.=A0=
</div><div><br></div><div>It&#39;s also extremely important to consider tha=
t these guys are providing the service at no cost to IETF. =A0I can&#39;t f=
athom what the cost would be if IETF were paying for something that might m=
eet your quality standards.</div>
<div><br></div><div>Regards,</div><div>Mary.=A0<br><div><br><div class=3D"g=
mail_quote">On Wed, Aug 8, 2012 at 5:33 PM, Carsten Bormann <span dir=3D"lt=
r">&lt;<a href=3D"mailto:cabo@tzi.org" target=3D"_blank">cabo@tzi.org</a>&g=
t;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Aug 8, 2012, at 22:38, =
Mary Barnes &lt;<a href=3D"mailto:mary.ietf.barnes@gmail.com">mary.ietf.bar=
nes@gmail.com</a>&gt; wrote:<br>

<br>
&gt; =A0If you&#39;ve never had the time to watch a Meetecho session record=
ing,<br>
<br>
</div>OMG, was the audio recovered from air bubbling up from a submarine or=
 what happened?<br>
<br>
Oh, and maybe somebody can explain the value of the audio spectrum above 4 =
kHz to the meetecho guys.<br>
<br>
With this audio quality, this is very close to useless (except maybe for hi=
storians digging it up 5000 years in the future and painstakingly reconstru=
cting what was maybe said).<br>
<br>
Gr=FC=DFe, Carsten<br>
<br>
</blockquote></div><br></div></div>

--f46d04083919e8690204c6c8c16c--

From joelja@bogus.com  Wed Aug  8 16:01:31 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AF9311E80A6 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 16:01:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.45
X-Spam-Level: 
X-Spam-Status: No, score=-102.45 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PCNEhMlWLyDS for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 16:01:31 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 024D111E8098 for <ietf@ietf.org>; Wed,  8 Aug 2012 16:01:30 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q78N1SlQ073181 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 8 Aug 2012 23:01:28 GMT (envelope-from joelja@bogus.com)
Message-ID: <5022EFC3.5030308@bogus.com>
Date: Wed, 08 Aug 2012 16:01:23 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120731 Thunderbird/15.0
MIME-Version: 1.0
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: Meetecho session recording for IETF-84 Telepresence (CLUE) Tutorial
References: <CAHBDyN70JABA4SrQGjJGTZTZyeA611tdRJB_+QL7VBJTaCRAVQ@mail.gmail.com> <8FEE254D-9256-4DDF-894F-6F046B4D6E2E@tzi.org> <CAHBDyN4J8Eyr59S9O0XPYW8aORuYXrTTVafs20sqWm=kMA7zoA@mail.gmail.com>
In-Reply-To: <CAHBDyN4J8Eyr59S9O0XPYW8aORuYXrTTVafs20sqWm=kMA7zoA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 08 Aug 2012 23:01:28 +0000 (UTC)
Cc: Carsten Bormann <cabo@tzi.org>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 23:01:31 -0000

On 8/8/12 3:37 PM, Mary Barnes wrote:
> It's surely not perfect, but given the technology being used, it's 
> certainly good enough and I find having the video and presentations 
> synched is far superior to just listening to the regular audio stream. 
>  You can turn off audio on Meetecho and use the regular audio stream, 
> but the audio will be delayed.
>
> As a chair, I find it very useful to use the recorded session to 
> double check my notes or sometimes clarify notes by the notetakers.
>
> It's also extremely important to consider that these guys are 
> providing the service at no cost to IETF.  I can't fathom what the 
> cost would be if IETF were paying for something that might meet your 
> quality standards.

Too clarify something. The various experimental and ongoing volunteer 
efforts and well as contractor provided services has non-trivial trivial 
support costs even when they are delivered by volunteers paying their 
own way. We can and should (and do) evaluate how we can do better, 
whether they're appropiate or not and what else we should be doing.
> Regards,
> Mary.
>
> On Wed, Aug 8, 2012 at 5:33 PM, Carsten Bormann <cabo@tzi.org 
> <mailto:cabo@tzi.org>> wrote:
>
>     On Aug 8, 2012, at 22:38, Mary Barnes <mary.ietf.barnes@gmail.com
>     <mailto:mary.ietf.barnes@gmail.com>> wrote:
>
>     >  If you've never had the time to watch a Meetecho session recording,
>
>     OMG, was the audio recovered from air bubbling up from a submarine
>     or what happened?
>
>     Oh, and maybe somebody can explain the value of the audio spectrum
>     above 4 kHz to the meetecho guys.
>
>     With this audio quality, this is very close to useless (except
>     maybe for historians digging it up 5000 years in the future and
>     painstakingly reconstructing what was maybe said).
>
>     Grüße, Carsten
>
>


From cabo@tzi.org  Wed Aug  8 16:07:22 2012
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BC9721F8503 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 16:07:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.348
X-Spam-Level: 
X-Spam-Status: No, score=-106.348 tagged_above=-999 required=5 tests=[AWL=-0.099, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ns-4S8okg7og for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 16:07:21 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 8907E21F84FE for <ietf@ietf.org>; Wed,  8 Aug 2012 16:07:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q78N7D7I001958; Thu, 9 Aug 2012 01:07:13 +0200 (CEST)
Received: from [192.168.217.117] (p548945C1.dip.t-dialin.net [84.137.69.193]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 7BD953A5; Thu,  9 Aug 2012 01:07:13 +0200 (CEST)
Subject: Re: Meetecho session recording for IETF-84 Telepresence (CLUE) Tutorial
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAHBDyN4J8Eyr59S9O0XPYW8aORuYXrTTVafs20sqWm=kMA7zoA@mail.gmail.com>
Date: Thu, 9 Aug 2012 01:07:12 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E9CE0F6F-464E-48A1-A378-5CCCE9354D93@tzi.org>
References: <CAHBDyN70JABA4SrQGjJGTZTZyeA611tdRJB_+QL7VBJTaCRAVQ@mail.gmail.com> <8FEE254D-9256-4DDF-894F-6F046B4D6E2E@tzi.org> <CAHBDyN4J8Eyr59S9O0XPYW8aORuYXrTTVafs20sqWm=kMA7zoA@mail.gmail.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
X-Mailer: Apple Mail (2.1485)
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, 08 Aug 2012 23:07:22 -0000

On Aug 9, 2012, at 00:37, Mary Barnes <mary.ietf.barnes@gmail.com> =
wrote:

> It's surely not perfect, but given the technology being used, it's =
certainly good enough

I'm sorry, I'm not a native English speaker, and the audio simply needs =
to be better to be legible for my ears.
With Audio Hijack and a couple of appropriately tuned AudioUnits, this =
recording indeed becomes barely understandable.
But what's lost is gone, and I'd rather focus on the content instead of =
on making out the words.
Actually, I'd rather listen to VHF AM 8.3 kHz cockpit communications =
than this...

> and I find having the video and presentations synched is far superior =
to just listening to the regular audio stream. =20

That is certainly a great feature.  But the regular audio stream mostly =
is legible, and the meetecho one apparently isn't.

> You can turn off audio on Meetecho and use the regular audio stream, =
but the audio will be delayed.=20
>=20
> As a chair, I find it very useful to use the recorded session to =
double check my notes or sometimes clarify notes by the notetakers.=20

Certainly.  And many kudos to Joel and friends.

> It's also extremely important to consider that these guys are =
providing the service at no cost to IETF.  I can't fathom what the cost =
would be if IETF were paying for something that might meet your quality =
standards.

Recording at a sampling rate of 8 kHz in 2012?  That's incomprehensible =
(in both senses).  And then applying some inferior compression scheme =
that inserts heavy artifacts.  They can do better.  Much better.  For =
exactly the same cost.

If the meetecho guys use the IETF as a pilot customer, they need honest =
feedback.  Honest and candid.  Like the one I'm providing here.  They =
don't want to be remembered by 1000 people as the guys who can't get =
audio right.

The fact that the tutorial is about telepresence adds a measure of =
irony...
(Which gets to the point of hilarious when the SDP example actually uses =
PCMU/8000 :-)

Gr=FC=DFe, Carsten


From glenzorn@gmail.com  Wed Aug  8 17:59:36 2012
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D35C911E8108 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 17:59:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.536
X-Spam-Level: 
X-Spam-Status: No, score=-3.536 tagged_above=-999 required=5 tests=[AWL=0.062,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0n7MNv-WrTui for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 17:59:30 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 421AC11E80FF for <ietf@ietf.org>; Wed,  8 Aug 2012 17:59:30 -0700 (PDT)
Received: by ggnh4 with SMTP id h4so438549ggn.31 for <ietf@ietf.org>; Wed, 08 Aug 2012 17:59:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer; bh=vXmm1U3LRdSKi3rudQ1WQTZXZp4+ehfTMSaI7li85zE=; b=GvVfZ60CCnKNdny9pydNJ+pgKLX9/Rb8NRno6nCCGoJ2sdnLo3D29YhgG8AUHy9Iee NhlKXYMNXMxbFuJUvygQ0NxDfl79J4RB97d1dxAO8xGcl/yR5JVV9cQaao1zd1e0EKtw Sjz8K2/WL3IKvMt8zOiy0B9OWSSZWU2X/AZhjo6WZDVnAIN/hPr7CJPUhkYOpKj39ItW b/6ff+yur4TSXLGPL0eUqPOGkGiACKJKRoOMUbO5C1g1E4Qe3xN0IqvXtYo23Bb+xVFj wqjxZ1nZEj5KdmFGdxqR+Dfd75tawKB79EIjsMxk5FUT0ZQwxr54rlNHZgCLo9kSGjCk kgig==
Received: by 10.50.187.233 with SMTP id fv9mr627943igc.59.1344473969061; Wed, 08 Aug 2012 17:59:29 -0700 (PDT)
Received: from [192.168.0.102] (ppp-115-87-121-149.revip4.asianet.co.th. [115.87.121.149]) by mx.google.com with ESMTPS id iw1sm3950602igc.13.2012.08.08.17.59.26 (version=SSLv3 cipher=OTHER); Wed, 08 Aug 2012 17:59:28 -0700 (PDT)
Subject: Re: So, where to repeat? (was:Re: management granularity)
From: Glen Zorn <glenzorn@gmail.com>
To: ietf@ietf.org
In-Reply-To: <6BC80C42-9921-4141-B918-4101E873945E@proto6.com>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <01ae01cd7412$abe83e50$03b8baf0$@us> <6BC80C42-9921-4141-B918-4101E873945E@proto6.com>
Content-Type: multipart/alternative; boundary="=-dszQ66DGg9320hN1I3e8"
Organization: Network Zen
Date: Thu, 09 Aug 2012 07:59:24 +0700
Message-ID: <1344473964.5897.15.camel@gwz-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 00:59:36 -0000

--=-dszQ66DGg9320hN1I3e8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit

On Wed, 2012-08-08 at 10:34 -0600, Geoff Mulligan wrote:
> I also would vote to return to Minneapolis again and again even
> permanently.
> 
> 
> Geoff
> 
> 
> 
> 
> 
> On Aug 6, 2012, at 2:32 PM, "Richard Shockey" <richard@shockey.us>
> wrote:
> 
> 
> 
> >  
> > 
> > 
> >  
> > 
> > [RS> ] +1 and no employer ever argued that going to Minneapolis was
> > a boondoggle.  


I imagine that few employers would ever argue that a trip to Hell would
be a boondoggle, either,
but that doesn't make it a good idea...


> > The Hilton in Minneapolis  of all the IETF meetings Iâ€™ve attended
> > has the most optimal layout of meeting rooms etc. 
> > 
> >  
> > 
> >  
> > 
> > 
> > If we were to choose one place in the U.S. to meet, Minneapolis is
> > the best choice IMHO.  It's very reasonably priced, easy for many to
> > get to and the hotel has adequate space for us (even back when we
> > had many more attendees).  Personally, the weather is not critical
> > to me, since I spend the vast majority of my time in the hotel
> > meeting rooms, so I'm very happy if we meet there in March and
> > November.   
> > 
> > 
> >  
> > 
> > 
> > Mary
> > 
> > 
> >  
> > 
> > 
> > On Mon, Aug 6, 2012 at 9:18 AM, Dearlove, Christopher (UK)
> > <Chris.Dearlove@baesystems.com> wrote:
> > 
> > I've never been to an IETF meeting where the plane fare has exceeded
> > the hotel cost for a week. Caveats to that are that I have mostly
> > gone for IETF recommended hotels, so may have missed particularly
> > cheap hotels, and that I have only been to North American and Europe
> > (but that statistic includes Vancouver and the even further away
> > western US cities down to San Diego). And of course I fly economy,
> > and it's much cheaper including a Saturday night in your trip, even
> > at the cost of an extra night in a hotel (at least it is from here).
> > An almost exception was Paris this year where I was staying fairly
> > cheaply, but that was a cost-shared trip between me and my employer,
> > and I didn't fly (I went by train - though that's not cheaper, just
> > better). Paris has cheap(er) hotels and a metro I understand, so I
> > felt less location constrained.
> > 
> > 
> > 
> > --
> > Christopher Dearlove
> > Senior Principal Engineer, Communications Group
> > Communications, Networks and Image Analysis Capability
> > BAE Systems Advanced Technology Centre
> > West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> > Tel: +44 1245 242194 |  Fax: +44 1245 242124
> > chris.dearlove@baesystems.com | http://www.baesystems.com
> > 
> > BAE Systems (Operations) Limited
> > Registered Office: Warwick House, PO Box 87, Farnborough Aerospace
> > Centre, Farnborough, Hants, GU14 6YU, UK
> > Registered in England & Wales No: 1996687
> > 
> > 
> > -----Original Message-----
> > 
> > 
> > From: Sprecher, Nurit (NSN - IL/Hod HaSharon)
> > [mailto:nurit.sprecher@nsn.com]
> > Sent: 06 August 2012 15:07
> > To: Dearlove, Christopher (UK); Daniele Ceccarelli; Andrew Sullivan;
> > ietf@ietf.org
> > Subject: RE: So, where to repeat? (was:Re: management granularity)
> > 
> > 
> > ----------------------! WARNING ! ----------------------
> > This message originates from outside our organisation,
> > either from an external partner or from the internet.
> > Keep this in mind if you answer this message.
> > Follow the 'Report Suspicious Emails' link on IT matters
> > for instructions on reporting suspicious email messages.
> > --------------------------------------------------------
> > 
> > When you are not close (time), flight cost may become higher in the
> > priority (over hotem)....
> > Flying to Vancouver for me for example is the most expensive
> > trip....even though the city is amazing and the host was wonderful!
> > 
> > -----Original Message-----
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
> > Of ext Dearlove, Christopher (UK)
> > Sent: Monday, August 06, 2012 4:56 PM
> > To: Daniele Ceccarelli; Andrew Sullivan; ietf@ietf.org
> > Subject: RE: So, where to repeat? (was:Re: management granularity)
> > 
> > Dublin's problem was that the venue was isolated from the city. This
> > has also been the case with e.g. San Diego. (I'm assuming no
> > personal car.) Contrast with Minneapolis (and several other places)
> > where you were right in the city. Being in a city is better for
> > lunch and dinner options, taking a break to go to a bookshop (or to
> > buy something you forgot to bring) and so on. (I'm deliberately not
> > including tourism here.)
> > 
> > However at the moment my priorities to make being able to attend
> > possible would be time (so the closer to me the better - I realise
> > that's impossible globally), cost (hotel first, flight second, rest
> > is noise) and the ability to plan ahead to only attend part of the
> > week. This is the current economic reality. Dublin actually scores
> > quite well on those for me.
> > 
> > --
> > Christopher Dearlove
> > Senior Principal Engineer, Communications Group
> > Communications, Networks and Image Analysis Capability
> > BAE Systems Advanced Technology Centre
> > West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> > Tel: +44 1245 242194 |  Fax: +44 1245 242124
> > chris.dearlove@baesystems.com | http://www.baesystems.com
> > 
> > BAE Systems (Operations) Limited
> > Registered Office: Warwick House, PO Box 87, Farnborough Aerospace
> > Centre, Farnborough, Hants, GU14 6YU, UK
> > Registered in England & Wales No: 1996687
> > 
> > 
> > -----Original Message-----
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
> > Of Daniele Ceccarelli
> > Sent: 06 August 2012 13:24
> > To: Andrew Sullivan; ietf@ietf.org
> > Subject: RE: So, where to repeat? (was:Re: management granularity)
> > 
> > ----------------------! WARNING ! ----------------------
> > This message originates from outside our organisation,
> > either from an external partner or from the internet.
> > Keep this in mind if you answer this message.
> > Follow the 'Report Suspicious Emails' link on IT matters
> > for instructions on reporting suspicious email messages.
> > --------------------------------------------------------
> > 
> > Dublin panned? I thought it was one of the best venues and locations
> > of the last meetings.
> > 
> > What about Italy or Spain? I've never heard about an IETF in Italy.
> > I'm ok with meetings outside Italy since i like traveling very much,
> > but i was wondering why it has never been taken into account in the
> > past meetings. Is it expensive? I think Italy and Spain are much
> > cheaper than France, UK or Sweden, aren't they?
> > 
> > BR
> > Daniele
> > 
> > >-----Original Message-----
> > >From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On
> > >Behalf Of Andrew Sullivan
> > >Sent: lunedÃ¬ 6 agosto 2012 14.06
> > >To: ietf@ietf.org
> > >Subject: So, where to repeat? (was:Re: management granularity)
> > >
> > >On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:
> > >> enough merely to have excellent staff.  We need to go back to the
> > >> better places and benefit from the learning curve.  This
> > >doesn't mean
> > >> "no new venues" but it means fewer.
> > >
> > >As a practical matter, may I ask about which venues you want
> > >to return to?  I get your argument in principle, but it seems
> > >to me that there has been quite a lot of complaining in the
> > >past.  The one factor that seems to me most likely to reduce
> > >complaints -- weather -- is evidently beyond the Secretariat's
> > >or IAOC's control.
> > >
> > >People seem inclined to return to the Hyatt in Vancouver,
> > >elevators notwithstanding.  We're going to do that.  (I don't
> > >understand why the previous Vencouver venue was less desirable
> > >-- to me, these venues were very similar, and not very far
> > >apart.  I note, however, that the previous two Vancouver
> > >visits were near the end of the year, when it rains all the
> > >time in Vancouver.)
> > >
> > >People complained at length about the venue in Paris, so I
> > >presume it's out.
> > >
> > >Some people complained about the hotel room prices and travel
> > >expense in Taipei, though I heard remarks that it was a good venue.
> > >Should we try to return there?
> > >
> > >People complained in advance about getting to QuÃ©bec, although
> > >afterwards I heard lots of good noises about that venue.  I
> > >note that the weather was great.  Should we try to return?
> > >
> > >I don't recall much complaining about the Prague venue in
> > >2011, which was striking to me because very little seemed
> > >different to me compared to our first visit there.  Perhaps
> > >this is evidence of the "tuning"
> > >you suggest (ensuring the water bottles were plastic, for
> > instance).
> > >But I note the weather was excellent.
> > >
> > >Beijing?  I guess Maastricht is out. Anaheim (FWIW, I thought
> > >that was an example of a terrible location, but many people
> > >seemed happy with it)?  Hiroshima?  Stockholm?  San Francisco
> > >(we thought the crime at Paris was bad, yet didn't complain
> > >about being smack up against the Tenderloin)?  Or there's the
> > >old standby, Minneapolis; perhaps we could do it in March.
> > >The Dublin venue was panned by large numbers of people.
> > >Philadelphia, people complained about expense.  Chicago, too
> > >(combined with hotel renovations).
> > >
> > >That gets us back through 2007.  Which of the venues do you
> > >think we should return to, to which we already haven't
> > >returned or planned to return?  And why?
> > >
> > >For what it's worth, I would not complain about returning to
> > >any of those venues; I personally had good meetings at all of
> > >them except Hiroshima, which I missed due to other
> > >commitments.  That includes both Maastricht and Dublin, which
> > >were both apparently trials for large numbers of others.
> > >
> > >Best,
> > >
> > >A
> > >
> > >--
> > >Andrew Sullivan
> > >ajs@anvilwalrusden.com
> > >
> > >
> > 
> > ********************************************************************
> > This email and any attachments are confidential to the intended
> > recipient and may also be privileged. If you are not the intended
> > recipient please delete it from your system and notify the sender.
> > You should not copy it or use it for any purpose nor disclose or
> > distribute its contents to any other person.
> > ********************************************************************
> > 
> > 
> > 
> >  
> > 
> > 


--=-dszQ66DGg9320hN1I3e8
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY BGCOLOR="#ffffff">
On Wed, 2012-08-08 at 10:34 -0600, Geoff Mulligan wrote:
<BLOCKQUOTE TYPE=CITE>
    I also would vote to return to Minneapolis again and again even permanently.
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BR>
    <BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    Geoff
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BR>
    <BR>
    <BR>
    <BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BR>
    On Aug 6, 2012, at 2:32 PM, &quot;Richard Shockey&quot; &lt;<A HREF="mailto:richard@shockey.us">richard@shockey.us</A>&gt; wrote:<BR>
    <BR>
    <BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE TYPE=CITE>
        &nbsp;<BR>
        <BR>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE TYPE=CITE>
        &nbsp;<BR>
        <BR>
        <B><I>[RS&gt; ] +1 and no employer ever argued that going to Minneapolis was a boondoggle.&nbsp; </I></B><BR>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BR>
I imagine that few employers would ever argue that a trip to Hell would be a boondoggle, either,<BR>
but that doesn't make it a good idea...<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE TYPE=CITE>
        <B><I>The Hilton in Minneapolis&nbsp; of all the IETF meetings I&#8217;ve attended has the most optimal layout of meeting rooms etc. </I></B><BR>
        <BR>
        <B><I>&nbsp;</I></B><BR>
        <BR>
        &nbsp;<BR>
        <BR>
        <BR>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE TYPE=CITE>
        If we were to choose one place in the U.S. to meet, Minneapolis is the best choice IMHO. &nbsp;It's very reasonably priced, easy for many to get to and the hotel has adequate space for us (even back when we had many more attendees). &nbsp;Personally, the weather is not critical to me, since I spend the vast majority of my time in the hotel meeting rooms, so I'm very happy if we meet there in March and November. &nbsp;&nbsp;<BR>
        <BR>
        <BR>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE TYPE=CITE>
        &nbsp;<BR>
        <BR>
        <BR>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE TYPE=CITE>
        Mary<BR>
        <BR>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE TYPE=CITE>
        &nbsp;<BR>
        <BR>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE TYPE=CITE>
        On Mon, Aug 6, 2012 at 9:18 AM, Dearlove, Christopher (UK) &lt;<A HREF="mailto:Chris.Dearlove@baesystems.com">Chris.Dearlove@baesystems.com</A>&gt; wrote:<BR>
        <BR>
        I've never been to an IETF meeting where the plane fare has exceeded the hotel cost for a week. Caveats to that are that I have mostly gone for IETF recommended hotels, so may have missed particularly cheap hotels, and that I have only been to North American and Europe (but that statistic includes Vancouver and the even further away western US cities down to San Diego). And of course I fly economy, and it's much cheaper including a Saturday night in your trip, even at the cost of an extra night in a hotel (at least it is from here). An almost exception was Paris this year where I was staying fairly cheaply, but that was a cost-shared trip between me and my employer, and I didn't fly (I went by train - though that's not cheaper, just better). Paris has cheap(er) hotels and a metro I understand, so I felt less location constrained.<BR>
        <BR>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE TYPE=CITE>
        <BR>
        --<BR>
        Christopher Dearlove<BR>
        Senior Principal Engineer, Communications Group<BR>
        Communications, Networks and Image Analysis Capability<BR>
        BAE Systems Advanced Technology Centre<BR>
        West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<BR>
        Tel: <A HREF="tel:%2B44%201245%20242194">+44 1245 242194</A>&nbsp;| &nbsp;Fax: <A HREF="tel:%2B44%201245%20242124">+44 1245 242124</A><BR>
        <A HREF="mailto:chris.dearlove@baesystems.com">chris.dearlove@baesystems.com</A> | <A HREF="http://www.baesystems.com">http://www.baesystems.com</A><BR>
        <BR>
        BAE Systems (Operations) Limited<BR>
        Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, UK<BR>
        Registered in England &amp; Wales No: 1996687<BR>
        <BR>
        <BR>
        -----Original Message-----<BR>
        <BR>
        <BR>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE TYPE=CITE>
        From: Sprecher, Nurit (NSN - IL/Hod HaSharon) [mailto:<A HREF="mailto:nurit.sprecher@nsn.com">nurit.sprecher@nsn.com</A>]<BR>
        Sent: 06 August 2012 15:07<BR>
        To: Dearlove, Christopher (UK); Daniele Ceccarelli; Andrew Sullivan; <A HREF="mailto:ietf@ietf.org">ietf@ietf.org</A><BR>
        Subject: RE: So, where to repeat? (was:Re: management granularity)<BR>
        <BR>
        <BR>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE TYPE=CITE>
        ----------------------! WARNING ! ----------------------<BR>
        This message originates from outside our organisation,<BR>
        either from an external partner or from the internet.<BR>
        Keep this in mind if you answer this message.<BR>
        Follow the 'Report Suspicious Emails' link on IT matters<BR>
        for instructions on reporting suspicious email messages.<BR>
        --------------------------------------------------------<BR>
        <BR>
        When you are not close (time), flight cost may become higher in the priority (over hotem)....<BR>
        Flying to Vancouver for me for example is the most expensive trip....even though the city is amazing and the host was wonderful!<BR>
        <BR>
        -----Original Message-----<BR>
        From: <A HREF="mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</A> [mailto:<A HREF="mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</A>] On Behalf Of ext Dearlove, Christopher (UK)<BR>
        Sent: Monday, August 06, 2012 4:56 PM<BR>
        To: Daniele Ceccarelli; Andrew Sullivan; <A HREF="mailto:ietf@ietf.org">ietf@ietf.org</A><BR>
        Subject: RE: So, where to repeat? (was:Re: management granularity)<BR>
        <BR>
        Dublin's problem was that the venue was isolated from the city. This has also been the case with e.g. San Diego. (I'm assuming no personal car.) Contrast with Minneapolis (and several other places) where you were right in the city. Being in a city is better for lunch and dinner options, taking a break to go to a bookshop (or to buy something you forgot to bring) and so on. (I'm deliberately not including tourism here.)<BR>
        <BR>
        However at the moment my priorities to make being able to attend possible would be time (so the closer to me the better - I realise that's impossible globally), cost (hotel first, flight second, rest is noise) and the ability to plan ahead to only attend part of the week. This is the current economic reality. Dublin actually scores quite well on those for me.<BR>
        <BR>
        --<BR>
        Christopher Dearlove<BR>
        Senior Principal Engineer, Communications Group<BR>
        Communications, Networks and Image Analysis Capability<BR>
        BAE Systems Advanced Technology Centre<BR>
        West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<BR>
        Tel: <A HREF="tel:%2B44%201245%20242194">+44 1245 242194</A>&nbsp;| &nbsp;Fax: <A HREF="tel:%2B44%201245%20242124">+44 1245 242124</A><BR>
        <A HREF="mailto:chris.dearlove@baesystems.com">chris.dearlove@baesystems.com</A> | <A HREF="http://www.baesystems.com">http://www.baesystems.com</A><BR>
        <BR>
        BAE Systems (Operations) Limited<BR>
        Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, UK<BR>
        Registered in England &amp; Wales No: 1996687<BR>
        <BR>
        <BR>
        -----Original Message-----<BR>
        From: <A HREF="mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</A> [mailto:<A HREF="mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</A>] On Behalf Of Daniele Ceccarelli<BR>
        Sent: 06 August 2012 13:24<BR>
        To: Andrew Sullivan; <A HREF="mailto:ietf@ietf.org">ietf@ietf.org</A><BR>
        Subject: RE: So, where to repeat? (was:Re: management granularity)<BR>
        <BR>
        ----------------------! WARNING ! ----------------------<BR>
        This message originates from outside our organisation,<BR>
        either from an external partner or from the internet.<BR>
        Keep this in mind if you answer this message.<BR>
        Follow the 'Report Suspicious Emails' link on IT matters<BR>
        for instructions on reporting suspicious email messages.<BR>
        --------------------------------------------------------<BR>
        <BR>
        Dublin panned? I thought it was one of the best venues and locations of the last meetings.<BR>
        <BR>
        What about Italy or Spain? I've never heard about an IETF in Italy. I'm ok with meetings outside Italy since i like traveling very much, but i was wondering why it has never been taken into account in the past meetings. Is it expensive? I think Italy and Spain are much cheaper than France, UK or Sweden, aren't they?<BR>
        <BR>
        BR<BR>
        Daniele<BR>
        <BR>
        &gt;-----Original Message-----<BR>
        &gt;From: <A HREF="mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</A> [mailto:<A HREF="mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</A>] On<BR>
        &gt;Behalf Of Andrew Sullivan<BR>
        &gt;Sent: luned&#236; 6 agosto 2012 14.06<BR>
        &gt;To: <A HREF="mailto:ietf@ietf.org">ietf@ietf.org</A><BR>
        &gt;Subject: So, where to repeat? (was:Re: management granularity)<BR>
        &gt;<BR>
        &gt;On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:<BR>
        &gt;&gt; enough merely to have excellent staff. &nbsp;We need to go back to the<BR>
        &gt;&gt; better places and benefit from the learning curve. &nbsp;This<BR>
        &gt;doesn't mean<BR>
        &gt;&gt; &quot;no new venues&quot; but it means fewer.<BR>
        &gt;<BR>
        &gt;As a practical matter, may I ask about which venues you want<BR>
        &gt;to return to? &nbsp;I get your argument in principle, but it seems<BR>
        &gt;to me that there has been quite a lot of complaining in the<BR>
        &gt;past. &nbsp;The one factor that seems to me most likely to reduce<BR>
        &gt;complaints -- weather -- is evidently beyond the Secretariat's<BR>
        &gt;or IAOC's control.<BR>
        &gt;<BR>
        &gt;People seem inclined to return to the Hyatt in Vancouver,<BR>
        &gt;elevators notwithstanding. &nbsp;We're going to do that. &nbsp;(I don't<BR>
        &gt;understand why the previous Vencouver venue was less desirable<BR>
        &gt;-- to me, these venues were very similar, and not very far<BR>
        &gt;apart. &nbsp;I note, however, that the previous two Vancouver<BR>
        &gt;visits were near the end of the year, when it rains all the<BR>
        &gt;time in Vancouver.)<BR>
        &gt;<BR>
        &gt;People complained at length about the venue in Paris, so I<BR>
        &gt;presume it's out.<BR>
        &gt;<BR>
        &gt;Some people complained about the hotel room prices and travel<BR>
        &gt;expense in Taipei, though I heard remarks that it was a good venue.<BR>
        &gt;Should we try to return there?<BR>
        &gt;<BR>
        &gt;People complained in advance about getting to Qu&#233;bec, although<BR>
        &gt;afterwards I heard lots of good noises about that venue. &nbsp;I<BR>
        &gt;note that the weather was great. &nbsp;Should we try to return?<BR>
        &gt;<BR>
        &gt;I don't recall much complaining about the Prague venue in<BR>
        &gt;2011, which was striking to me because very little seemed<BR>
        &gt;different to me compared to our first visit there. &nbsp;Perhaps<BR>
        &gt;this is evidence of the &quot;tuning&quot;<BR>
        &gt;you suggest (ensuring the water bottles were plastic, for instance).<BR>
        &gt;But I note the weather was excellent.<BR>
        &gt;<BR>
        &gt;Beijing? &nbsp;I guess Maastricht is out. Anaheim (FWIW, I thought<BR>
        &gt;that was an example of a terrible location, but many people<BR>
        &gt;seemed happy with it)? &nbsp;Hiroshima? &nbsp;Stockholm? &nbsp;San Francisco<BR>
        &gt;(we thought the crime at Paris was bad, yet didn't complain<BR>
        &gt;about being smack up against the Tenderloin)? &nbsp;Or there's the<BR>
        &gt;old standby, Minneapolis; perhaps we could do it in March.<BR>
        &gt;The Dublin venue was panned by large numbers of people.<BR>
        &gt;Philadelphia, people complained about expense. &nbsp;Chicago, too<BR>
        &gt;(combined with hotel renovations).<BR>
        &gt;<BR>
        &gt;That gets us back through 2007. &nbsp;Which of the venues do you<BR>
        &gt;think we should return to, to which we already haven't<BR>
        &gt;returned or planned to return? &nbsp;And why?<BR>
        &gt;<BR>
        &gt;For what it's worth, I would not complain about returning to<BR>
        &gt;any of those venues; I personally had good meetings at all of<BR>
        &gt;them except Hiroshima, which I missed due to other<BR>
        &gt;commitments. &nbsp;That includes both Maastricht and Dublin, which<BR>
        &gt;were both apparently trials for large numbers of others.<BR>
        &gt;<BR>
        &gt;Best,<BR>
        &gt;<BR>
        &gt;A<BR>
        &gt;<BR>
        &gt;--<BR>
        &gt;Andrew Sullivan<BR>
        &gt;<A HREF="mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</A><BR>
        &gt;<BR>
        &gt;<BR>
        <BR>
        ********************************************************************<BR>
        This email and any attachments are confidential to the intended<BR>
        recipient and may also be privileged. If you are not the intended<BR>
        recipient please delete it from your system and notify the sender.<BR>
        You should not copy it or use it for any purpose nor disclose or<BR>
        distribute its contents to any other person.<BR>
        ********************************************************************<BR>
        <BR>
        <BR>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE TYPE=CITE>
        &nbsp;<BR>
        <BR>
        <BR>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>

--=-dszQ66DGg9320hN1I3e8--


From glenzorn@gmail.com  Wed Aug  8 18:08:33 2012
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DC1A11E811A for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 18:08:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.542
X-Spam-Level: 
X-Spam-Status: No, score=-3.542 tagged_above=-999 required=5 tests=[AWL=0.056,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W4z1AA1IOLuh for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 18:08:32 -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 38C0F11E80FF for <ietf@ietf.org>; Wed,  8 Aug 2012 18:08:32 -0700 (PDT)
Received: by yhq56 with SMTP id 56so1596109yhq.31 for <ietf@ietf.org>; Wed, 08 Aug 2012 18:08:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer; bh=fBcQABflVHDzWpk8GFnlHYMx0ziJNfKpj6sf5MbfhhA=; b=WKbLy5ydQTFwJP7vB6N6puPxjvL9lUp2VuI8/con5dSPLNuBB7+xU3dcCtJtpFy0tB /DDuWoe/k57KIl2C2RbUd7/jcWLmw+RnRiI0K6DJRbj53haBRW2l2MVKMSTN/cIoHzzL 2DEpNZSZu8qOQBz7dLFPXOgFkBdMU47Lxgga8Nxq/bgtxSSRCSZyyljfjBmd7M9jMepZ qWxbTjXaNSFYM85+JHf5W1WHH7n7qxTrcJf1SLCfi8kQnf5i91H9mAWBC9avw5QxA8uw oZdcWrrTaif/zOOGC0EQNs9TXH5bXvsJBlhqjAD41i1yVezom7iuUgjE9i2Ye28kgOB6 U5LQ==
Received: by 10.50.6.229 with SMTP id e5mr766135iga.9.1344474511526; Wed, 08 Aug 2012 18:08:31 -0700 (PDT)
Received: from [192.168.0.102] (ppp-115-87-121-149.revip4.asianet.co.th. [115.87.121.149]) by mx.google.com with ESMTPS id a10sm7710948igd.1.2012.08.08.18.08.29 (version=SSLv3 cipher=OTHER); Wed, 08 Aug 2012 18:08:30 -0700 (PDT)
Subject: RE: So, where to repeat? (was:Re: management granularity)
From: Glen Zorn <glenzorn@gmail.com>
To: ietf@ietf.org
In-Reply-To: <E4873516F3FC7547BCFE792C7D94039C0236B100@DEMUEXC013.nsn-intra.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net>	<20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <29F2EDD3-71B8-4762-8753-5C7AF369001B@tzi.org> <15DAC57C-82D5-4261-B0FA-4B700138DA2A@proto6.com> <79811B0A-FA21-456A-8016-BF20DF3FBD95@checkpoint.com> <E4873516F3FC7547BCFE792C7D94039C0236B100@DEMUEXC013.nsn-intra.net>
Content-Type: multipart/alternative; boundary="=-ZcO3gYuTK0gchKER9dTr"
Organization: Network Zen
Date: Thu, 09 Aug 2012 08:08:27 +0700
Message-ID: <1344474507.5897.17.camel@gwz-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 01:08:33 -0000

--=-ZcO3gYuTK0gchKER9dTr
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit

On Wed, 2012-08-08 at 20:13 +0200, Sprecher, Nurit (NSN - IL/Hod
HaSharon) wrote:


> +1


Indeed, almost any place in Europe is easier & cheaper for me (not to
mention less hassle from immigration and customs!) than any place in the
US.


> 
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of ext Yoav Nir
> Sent: Wednesday, August 08, 2012 9:07 PM
> To: Geoff Mulligan
> Cc: Carsten Bormann; ietf@ietf.org
> Subject: Re: So, where to repeat? (was:Re: management granularity)
> 
> Mileage varies. 
> 
> For me it was the shortest and cheapest flight of any IETF meeting I have attended.
> 
> Yoav
> 
> On Aug 8, 2012, at 7:41 PM, Geoff Mulligan wrote:
> 
> > I liked the hotel and prague was wonderful, but it didn't seem easy to get to cheaply from the US.
> > 
> > Geoff
> > 
> > 
> > 
> > On Aug 6, 2012, at 6:22 PM, Carsten Bormann <cabo@tzi.org> wrote:
> > 
> >> On Aug 6, 2012, at 16:41, Mary Barnes <mary.ietf.barnes@gmail.com> wrote:
> >> 
> >>> If we were to choose one place in the U.S. to meet, Minneapolis is the best choice IMHO.  
> >> 
> >> +1 a lot.
> >> (If we indeed have to choose the US.)
> >> Great facility to get work done, good food, reasonable flights.
> >> 
> >> And add Prague as the staple for Europe.
> >> 
> >> GrÃ¼ÃŸe, Carsten
> 



--=-ZcO3gYuTK0gchKER9dTr
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
On Wed, 2012-08-08 at 20:13 +0200, Sprecher, Nurit (NSN - IL/Hod HaSharon) wrote:<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
+1
</PRE>
</BLOCKQUOTE>
<BR>
Indeed, almost any place in Europe is easier &amp; cheaper for me (not to mention less hassle from immigration and customs!) than any place in the US.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>

-----Original Message-----
From: <A HREF="mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</A> [<A HREF="mailto:ietf-bounces@ietf.org">mailto:ietf-bounces@ietf.org</A>] On Behalf Of ext Yoav Nir
Sent: Wednesday, August 08, 2012 9:07 PM
To: Geoff Mulligan
Cc: Carsten Bormann; <A HREF="mailto:ietf@ietf.org">ietf@ietf.org</A>
Subject: Re: So, where to repeat? (was:Re: management granularity)

Mileage varies. 

For me it was the shortest and cheapest flight of any IETF meeting I have attended.

Yoav

On Aug 8, 2012, at 7:41 PM, Geoff Mulligan wrote:

&gt; I liked the hotel and prague was wonderful, but it didn't seem easy to get to cheaply from the US.
&gt; 
&gt; Geoff
&gt; 
&gt; 
&gt; 
&gt; On Aug 6, 2012, at 6:22 PM, Carsten Bormann &lt;<A HREF="mailto:cabo@tzi.org">cabo@tzi.org</A>&gt; wrote:
&gt; 
&gt;&gt; On Aug 6, 2012, at 16:41, Mary Barnes &lt;<A HREF="mailto:mary.ietf.barnes@gmail.com">mary.ietf.barnes@gmail.com</A>&gt; wrote:
&gt;&gt; 
&gt;&gt;&gt; If we were to choose one place in the U.S. to meet, Minneapolis is the best choice IMHO.  
&gt;&gt; 
&gt;&gt; +1 a lot.
&gt;&gt; (If we indeed have to choose the US.)
&gt;&gt; Great facility to get work done, good food, reasonable flights.
&gt;&gt; 
&gt;&gt; And add Prague as the staple for Europe.
&gt;&gt; 
&gt;&gt; Gr&#252;&#223;e, Carsten

</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>

--=-ZcO3gYuTK0gchKER9dTr--


From glenzorn@gmail.com  Wed Aug  8 18:13:48 2012
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C229111E8087 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 18:13:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.818
X-Spam-Level: 
X-Spam-Status: No, score=-1.818 tagged_above=-999 required=5 tests=[AWL=-1.680, BAYES_00=-2.599, EXTRA_MPART_TYPE=1, HTML_IMAGE_ONLY_12=2.46, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zaNnxcIjfp13 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 18:13:48 -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 D9B0711E811A for <ietf@ietf.org>; Wed,  8 Aug 2012 18:13:47 -0700 (PDT)
Received: by yhq56 with SMTP id 56so1599593yhq.31 for <ietf@ietf.org>; Wed, 08 Aug 2012 18:13:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer; bh=at7azovtFakUgo2jaGmRfjmZR0W4xrx+QYnrVBoNlRw=; b=SAeo79h/2nKDtG/MflQYZY3Bv5nB0aYEkOXLR62yETl2Sl0wPbAHBQ/sUgKi6jzxSC /kbNFKIjSj2dQr1lGSoqPJxbvEWA+csB+3jlarX1knKkKWm5i3jdb16aE001hRSoPHAK E9fv0q/SmpFqnqH4peW2yFwbvqQy4xD28qMPYcDmyugD/cB/HtG7tA1MREZz6bsTEW7r VWNTI96Fbf5Ar453+aKVFw/3csnwpjQFj0/R4+4dSFS/Say+GR9Qvn4pkS6yzkvtzQc5 s36JPMbaPNNQ/s8tO12gV75IK+186sGYSfLeTRLFLY7m3tP22kqr9ih5SnZfl7OtUgJe mn4Q==
Received: by 10.50.209.41 with SMTP id mj9mr705796igc.23.1344474827270; Wed, 08 Aug 2012 18:13:47 -0700 (PDT)
Received: from [192.168.0.102] (ppp-115-87-121-149.revip4.asianet.co.th. [115.87.121.149]) by mx.google.com with ESMTPS id ai6sm7736169igc.0.2012.08.08.18.13.44 (version=SSLv3 cipher=OTHER); Wed, 08 Aug 2012 18:13:46 -0700 (PDT)
Subject: Re: So, where to repeat?
From: Glen Zorn <glenzorn@gmail.com>
To: ietf@ietf.org
In-Reply-To: <5022AD8C.4020205@stpeter.im>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net>	<20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <29F2EDD3-71B8-4762-8753-5C7AF369001B@tzi.org> <15DAC57C-82D5-4261-B0FA-4B700138DA2A@proto6.com> <79811B0A-FA21-456A-8016-BF20DF3FBD95@checkpoint.com> <5022AD8C.4020205@stpeter.im>
Content-Type: multipart/related; type="multipart/alternative"; boundary="=-LFN8R9oxk2mahbxCDwoq"
Organization: Network Zen
Date: Thu, 09 Aug 2012 08:13:42 +0700
Message-ID: <1344474822.5897.20.camel@gwz-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 01:13:48 -0000

--=-LFN8R9oxk2mahbxCDwoq
Content-Type: multipart/alternative; boundary="=-pb+YnYmLE6MxwIDamA9f"


--=-pb+YnYmLE6MxwIDamA9f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

On Wed, 2012-08-08 at 12:18 -0600, Peter Saint-Andre wrote:

> On 8/8/12 12:06 PM, Yoav Nir wrote:
> > Mileage varies. 
> > 
> > For me it was the shortest and cheapest flight of any IETF meeting I have attended.
> 
> If we discussed protocols the way we discuss venue sites, all would be
> lost. "Oh, this feature works great for me, therefore let's include it
> in the spec."
> 
> Perhaps we might consider ending these interminable venue discussions
> and just complain three times a year when we visit a place that the IAOC
> has selected?


I though we already did that ;-).  

> 
> Peter
> 



--=-pb+YnYmLE6MxwIDamA9f
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
On Wed, 2012-08-08 at 12:18 -0600, Peter Saint-Andre wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
On 8/8/12 12:06 PM, Yoav Nir wrote:
&gt; Mileage varies. 
&gt; 
&gt; For me it was the shortest and cheapest flight of any IETF meeting I have attended.

If we discussed protocols the way we discuss venue sites, all would be
lost. &quot;Oh, this feature works great for me, therefore let's include it
in the spec.&quot;

Perhaps we might consider ending these interminable venue discussions
and just complain three times a year when we visit a place that the IAOC
has selected?
</PRE>
</BLOCKQUOTE>
<BR>
I though we already did that <IMG SRC="cid:1344474590.5897.18.camel@gwz-laptop" ALIGN="middle" ALT=";-)" BORDER="0">.&nbsp; 
<BLOCKQUOTE TYPE=CITE>
<PRE>

Peter

</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>

--=-pb+YnYmLE6MxwIDamA9f--

--=-LFN8R9oxk2mahbxCDwoq
Content-ID: <1344474590.5897.18.camel@gwz-laptop>
Content-Disposition: attachment; filename="face-wink.png"
Content-Type: image/png; name="face-wink.png"
Content-Transfer-Encoding: base64

iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAABHNCSVQICAgIfAhkiAAAAAlwSFlz
AAAN1wAADdcBQiibeAAAABl0RVh0U29mdHdhcmUAd3d3Lmlua3NjYXBlLm9yZ5vuPBoAAAAXdEVY
dEF1dGhvcgBMYXBvIENhbGFtYW5kcmVp35EaKgAAACl0RVh0RGVzY3JpcHRpb24AQmFzZWQgb2Yg
SmFrdWIgU3RlaW5lciBkZXNpZ26ghAVzAAADQUlEQVQ4jWWTW2jVdQCAv//t3HbqzF3cOluL1kWi
3DTP3NAt3bAeokKCXoISFHUEhQ9d3grxKWh0gYxJSAwSKQh8KAkqtcZWtqXTww562NnZpq6dTbdz
ds75337/36/Xhd/zx/f2aUopNnL6g96koRmvhw21F13bAYBUk26gXQxUcObgx6N3NvraxsDI+30H
o/EHvnhmZ0+4ofUhs6ahEZSislJgeWFRXB0fcyvl8juHPx07fV/g2/d2/dT65Pb+1MDzEc39By1U
gJAAFLgW+M0EViejP//o5DNTFwa//PtFAB3gm3d7B1se39rf1bs7EuROId1JVAL0xnq0xnpIKALn
L2T+a/YM7Iu0tD+1d+hIahBAP3Wsr80IRYd27Hoh4lwfRgZL6PEa9FgcFY5COMZKRefDr+ZQ/iJO
+iTP7XspaljhoeMHUm26L/xD27Z1h+X8BWRplttrNQyfLXH46BgyCNCUIp1eZvxKCQWIUh5u/c7u
nr5wEIhDZiC8/vqmh43VqfMIKUi2hnjjlU7erH8Uw7sBKKLYCLcKnocmJd7tyzQ9dsAIhNdvesro
iNc2UVnPk1mFijlLe9jFMDJIz0JDo6PJ58j+NpRTQXkCsT5LYmcST+gdpi800ykuIT2X7W11nL/h
8ev1LD3P1tH5dC0AIdvltZTEKThU130iro/vVPECZZq2XU3nb17tbjUTyHKJl7u3UrQ288v4FX77
M4eUCuFJasOSjmbYUiPA3MTM9GVc10mbTsClTPZmV0MsplvOPcrzacxNLewf2IMWq0Pay8jiHHpl
CYoFgqKLG4szlclIR3DJFIEauTZTeDvZbkS3BBIdB8dboFy4hdINLBNiBigRgO0iXUVOWYxdy7ue
0EeM8enC8rmRz0Nzd+2uemvNSiiBqRS6UoS0gJAUaI4PtotX8cnZOt9P69WSLT85ezH3nQ7QVEme
KHpW9tydZHVy1WRl3Yeyjbluo63ZuEWbf4uCiXsGZ7J11ZUq2WVj/sT/XjiaSlmVB+8eV0odeyRe
irREXa056gKwWA2xUA2rmWLcUWifNTibPxqemPDvuxHg1b72Th3/LQ2tN5DaEwCGrrIKNSqxTv7w
R25qo/8f4VCvV0QXv9gAAAAASUVORK5CYII=


--=-LFN8R9oxk2mahbxCDwoq--


From hsantos@isdg.net  Wed Aug  8 19:44:42 2012
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48B9821E803F for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 19:44:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.578
X-Spam-Level: 
X-Spam-Status: No, score=-102.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZJmdEIXYewgU for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 19:44:41 -0700 (PDT)
Received: from groups.winserver.com (groups.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 440BD21E8039 for <ietf@ietf.org>; Wed,  8 Aug 2012 19:44:40 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=423; t=1344480275; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=kIbuYZitwOY66a22mw4BDLdfKuI=; b=GCq3xu9uUwCZFWK5gdhP D628OT0ZbM00sB3q83rjVg5chtucTefVMUdjklLma5Kf9jYTzmM69s8RXSa8EiX/ GTX8WQi9ddzc37zFJm9VZCmQi7DOi2TDIuvHg3nVHWfgwrtzEz79xxR3yFtxsifD BeEQYNtg0lKZwDYfqr2mYFY=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 08 Aug 2012 22:44:35 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 502086200.14909.4532; Wed, 08 Aug 2012 22:44:34 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=423; t=1344480105; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=eeF0pOb I3nwyLj/fGuKg6uf6jBRMCHWlPY2AimMyo9w=; b=REiqHqxXCk52h/LwXYwB5BH iAhxTktjLm1j/R+Fmb4p4y/NVib5pKZEqrUWq6LjOBacvFht29xU+PHqm7FUahmA zFptS5l1JU0TkQmBu5WfhC2jWPCVPRg3rg2mBTpxd+6h1RV5/RAeEVFBzHFnk7Lk pW0H/y+CyMsm4EOKNRTw=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 08 Aug 2012 22:41:45 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1100903927.9.3284; Wed, 08 Aug 2012 22:41:45 -0400
Message-ID: <50232431.1010308@isdg.net>
Date: Wed, 08 Aug 2012 22:45:05 -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: So, where to repeat?
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com>	<501EC24B.4080709@bbiw.net>	<20120806120547.GA20379@crankycanuck.ca>	<B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se>	<B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net>	<E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net>	<B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net>	<CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com>	<01ae01cd7412$abe83e50$03b8baf0$@us>	<6BC80C42-9921-4141-B918-4101E873945E@proto6.com> <50229CFA.8080408@viagenie.ca>
In-Reply-To: <50229CFA.8080408@viagenie.ca>
Content-Type: text/plain; charset=UTF-8; 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, 09 Aug 2012 02:44:42 -0000

Simon Perreault wrote:
> Le 2012-08-08 12:34, Geoff Mulligan a Ã©crit :
>> I also would vote to return to Minneapolis again and again even 
>> permanently.
> 
> Does nobody care about going to new places so that new people are 
> exposed to the IETF and may start getting involved?
> 
> We've seen this positive effect many times when we went outside our 
> comfort zone...

Is Miami out of the question?

-- 
HLS



From ole@cisco.com  Wed Aug  8 19:50:07 2012
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8A9821E8039 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 19:50:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.565
X-Spam-Level: 
X-Spam-Status: No, score=-110.565 tagged_above=-999 required=5 tests=[AWL=0.034, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D2Q6xMsSkWXQ for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 19:50:05 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id BBF6811E80D2 for <ietf@ietf.org>; Wed,  8 Aug 2012 19:50:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=1363; q=dns/txt; s=iport; t=1344480605; x=1345690205; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=WExHrE4OQL9EvJvo+kikwABlQZL3UTJl5Ge7rs70hZQ=; b=DYk7ECnyXvTbKz2pIpe5vlvxjKY+vpmpLLLlbYE7r031CUvcntPNZVOJ CaTBO528ZszRLRk5lXQO87SKp25dY8mKqTi3Jm2DVTxi49r/INje37YDV /FuE8SffslBSA9AYfSyKD/HQu4HF3N0VlnbaaOi2fAQvESrxeEkdgjoy5 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAE8kI1CrRDoI/2dsb2JhbABCA4YBs2KBB4IgAQEBAwESAQIOVgULCw4KKgICVwYTIodlBZtUg0gQiUGTGYsSGoMlgg+BEgOITpJXhTGDHIEEYoJ/gT8
X-IronPort-AV: E=Sophos;i="4.77,736,1336348800"; d="scan'208";a="54414578"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 09 Aug 2012 02:50:05 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q792o4cu031598 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Aug 2012 02:50:05 GMT
Date: Wed, 8 Aug 2012 19:50:04 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Hector Santos <hsantos@isdg.net>
Subject: Re: So, where to repeat?
In-Reply-To: <50232431.1010308@isdg.net>
Message-ID: <alpine.OSX.2.01.1208081947270.26915@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <01ae01cd7412$abe83e50$03b8baf0$@us> <6BC80C42-9921-4141-B918-4101E873945E@proto6.com> <50229CFA.8080408@viagenie.ca> <50232431.1010308@isdg.net>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="0-397911640-1344480605=:26915"
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 02:50:08 -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.

--0-397911640-1344480605=:26915
Content-Type: TEXT/PLAIN; charset=UTF-8
Content-Transfer-Encoding: 8BIT


No more so than Orlando where we are going after Atlanta, in my 
opinion. There exists a whole set of requirements ranging from
travel considerations, costs, suitable venue, hotels, and nearby 
environment to host and sponsorship availability. I see no reason
why Miami would be automatically excluded from consideration.

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Wed, 8 Aug 2012, Hector Santos wrote:

> Simon Perreault wrote:
> > Le 2012-08-08 12:34, Geoff Mulligan a Ã©crit :
> > > I also would vote to return to Minneapolis again and again even
> > > permanently.
> > 
> > Does nobody care about going to new places so that new people are exposed to
> > the IETF and may start getting involved?
> > 
> > We've seen this positive effect many times when we went outside our comfort
> > zone...
> 
> Is Miami out of the question?
> 
> -- 
> HLS
> 
> 
> 
--0-397911640-1344480605=:26915--

From daedulus@btconnect.com  Thu Aug  9 01:12:33 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25CA521F86E4 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 01:12:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.54
X-Spam-Level: 
X-Spam-Status: No, score=-3.54 tagged_above=-999 required=5 tests=[AWL=0.059,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8ljT0gHOuxwy for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 01:12:32 -0700 (PDT)
Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe002.messaging.microsoft.com [213.199.154.140]) by ietfa.amsl.com (Postfix) with ESMTP id 03EEE21F873B for <ietf@ietf.org>; Thu,  9 Aug 2012 01:12:31 -0700 (PDT)
Received: from mail17-db3-R.bigfish.com (10.3.81.233) by DB3EHSOBE010.bigfish.com (10.3.84.30) with Microsoft SMTP Server id 14.1.225.23; Thu, 9 Aug 2012 08:12:30 +0000
Received: from mail17-db3 (localhost [127.0.0.1])	by mail17-db3-R.bigfish.com (Postfix) with ESMTP id CAD5A1C0076; Thu,  9 Aug 2012 08:12:30 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.224.141; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0702HT007.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -24
X-BigFish: PS-24(zz98dI9371I542M1432Izz1202hzz1033IL8275bh8275dhz2dh2a8h5a9h668h839hd24hf0ah107ah304l)
Received: from mail17-db3 (localhost.localdomain [127.0.0.1]) by mail17-db3 (MessageSwitch) id 1344499949609367_26182; Thu,  9 Aug 2012 08:12:29 +0000 (UTC)
Received: from DB3EHSMHS013.bigfish.com (unknown [10.3.81.238])	by mail17-db3.bigfish.com (Postfix) with ESMTP id 88BEC1800B4; Thu,  9 Aug 2012 08:12:29 +0000 (UTC)
Received: from DB3PRD0702HT007.eurprd07.prod.outlook.com (157.55.224.141) by DB3EHSMHS013.bigfish.com (10.3.87.113) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 9 Aug 2012 08:12:29 +0000
Received: from AMSPRD0510HT001.eurprd05.prod.outlook.com (157.56.248.53) by pod51017.outlook.com (10.3.4.168) with Microsoft SMTP Server (TLS) id 14.15.108.4; Thu, 9 Aug 2012 08:12:28 +0000
Message-ID: <006701cd7606$17ff48a0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Alessandro Vesely <vesely@tana.it>, <ietf@ietf.org>
References: <CALaySJKV96tdXhzfPD1e1Mro_+gp5aDarF7Z06QrA+iQtnHkLw@mail.gmail.com><501A5656.2050407@it.aoyama.ac.jp><501BEC0D.1060404@tana.it><009101cd7476$bb522c20$4001a8c0@gateway.2wire.net><599B1629-543A-49BC-A0E7-FA2096C538AD@checkpoint.com><03e701cd749f$73891c40$4001a8c0@gateway.2wire.net> <50229D32.8000605@tana.it>
Subject: Re: RFC Errata: when to file, and when not to
Date: Thu, 9 Aug 2012 09:07:54 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.248.53]
X-OriginatorOrg: btconnect.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 08:12:33 -0000

----- Original Message -----
From: "Alessandro Vesely" <vesely@tana.it>
To: <ietf@ietf.org>
Sent: Wednesday, August 08, 2012 6:09 PM
> On Tue 07/Aug/2012 15:20:35 +0200 t.p. wrote:
> > From: "Yoav Nir" <ynir@checkpoint.com>
> >
> >> Would it make it easier to find if they were called "notes" or
> >> "corrections" instead of "errata"?
> >
> > Yes, corrections is what I see published in a newspaper to correct
> > errata in previous editions.  So far, it is the best word I can
> > think of (but there might be a better one:-).
>
> Errata is an abbreviation of "errata corrige", the Latin for "error
> correction".  Switching to the English translation would seem to be
> consistent with English being the official publication language for
RFCs.
>
> > In the html version of an RFC, it would be easy to provide old and
new
> > in an easy to compare format (as some editors do for I-D), not
perhaps
> > on permanent display but shown when 'errata' (or whatever name we
> > choose) is toggled.
>
> Although easy, doing that would require a noticeable amount of
> editorial work.  In addition, notes, reasons, and explanations don't
> have an obvious graphical rendition.  IMHO, knowing when and why an
> errata was proposed and verified is an integral part of it.

Well, start simple and build on it, something the tools team have a
history of doing:-)

First, have only the one highlighted 'corrections made' field on the
html page.

Second, add a new link to a 'corrections help' page telling the viewer
that once issued, a RFC is never changed, that any changes require a
fresh RFC that updates or supersedes the original one (pointing to the
highlighted fields in the top right hand example, perhaps with a worked
example - but not SMTP:-( but that there is an 'erratum' mechanism for
correcting editorial errors or places where the text is or may not be
clear about the intentions of the editors; and that such errata can be
viewed by clicking on the 'corrections made' field.

Finally, change the 'corrections made' to a 'hide corrections/view
corrections' toggle, default the first setting, the second setting
showing OLD/NEW text, old recognisably different eg struck through, with
a link to the RFC Editor page for the erratum; this is only done for
errata that are accepted.  Yes, there would be some intricate errata
that this would not cover, but the screens you get currently by
following the link to the RFC Editor page are so arcane as to switch off
all but those intimately involved in this standards process.

Tom Petch



From daedulus@btconnect.com  Thu Aug  9 01:17:10 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EB7121F86FC for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 01:17:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.545
X-Spam-Level: 
X-Spam-Status: No, score=-3.545 tagged_above=-999 required=5 tests=[AWL=0.054,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gaPJh1akpyTt for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 01:17:08 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe004.messaging.microsoft.com [216.32.181.184]) by ietfa.amsl.com (Postfix) with ESMTP id 4ECCF21F859A for <ietf@ietf.org>; Thu,  9 Aug 2012 01:17:08 -0700 (PDT)
Received: from mail70-ch1-R.bigfish.com (10.43.68.238) by CH1EHSOBE014.bigfish.com (10.43.70.64) with Microsoft SMTP Server id 14.1.225.23; Thu, 9 Aug 2012 08:17:07 +0000
Received: from mail70-ch1 (localhost [127.0.0.1])	by mail70-ch1-R.bigfish.com (Postfix) with ESMTP id 8C8A32031B; Thu,  9 Aug 2012 08:17:07 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.224.141; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0702HT005.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -24
X-BigFish: PS-24(zz98dI9371Ic89bh542M1432Izz1202hzz1033IL8275bh8275dhz2dh2a8h5a9h668h839h93fhd24hf0ah107ah304l)
Received: from mail70-ch1 (localhost.localdomain [127.0.0.1]) by mail70-ch1 (MessageSwitch) id 1344500206959948_17558; Thu,  9 Aug 2012 08:16:46 +0000 (UTC)
Received: from CH1EHSMHS023.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.242])	by mail70-ch1.bigfish.com (Postfix) with ESMTP id 52FACA022C; Thu,  9 Aug 2012 08:16:39 +0000 (UTC)
Received: from DB3PRD0702HT005.eurprd07.prod.outlook.com (157.55.224.141) by CH1EHSMHS023.bigfish.com (10.43.70.23) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 9 Aug 2012 08:16:38 +0000
Received: from AMSPRD0510HT001.eurprd05.prod.outlook.com (157.56.248.53) by pod51017.outlook.com (10.3.4.160) with Microsoft SMTP Server (TLS) id 14.15.108.4; Thu, 9 Aug 2012 08:16:26 +0000
Message-ID: <008601cd7606$a5c8e420$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Geoff Mulligan <geoff@proto6.com>, Richard Shockey <richard@shockey.us>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com><501EC24B.4080709@bbiw.net><20120806120547.GA20379@crankycanuck.ca><B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se><B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net><E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net><B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net><CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com><01ae01cd7412$abe83e50$03b8baf0$@us> <6BC80C42-9921-4141-B918-4101E873945E@proto6.com>
Subject: Re: So, where to repeat? (was:Re: management granularity)
Date: Thu, 9 Aug 2012 09:11:52 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.248.53]
Content-Transfer-Encoding: quoted-printable
X-OriginatorOrg: btconnect.com
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 08:17:10 -0000

---- Original Message -----
From: "Geoff Mulligan" <geoff@proto6.com>
To: "Richard Shockey" <richard@shockey.us>
Cc: <ietf@ietf.org>
Sent: Wednesday, August 08, 2012 5:34 PM

I also would vote to return to Minneapolis again and again even
permanently.

<tp>
So, would I despite London 2014 being only a train ride away.
Minneapolis has the flights, and flights across the Atlantic are so much
cheaper than those across Europe,  has the range of hotels (and has the
possibility of extra-mural interests, although it is travel and hotel
costs that dominate my decision-making)


Tom Petch
</tp>

Geoff




On Aug 6, 2012, at 2:32 PM, "Richard Shockey" <richard@shockey.us>
wrote:

>
>
> [RS> ] +1 and no employer ever argued that going to Minneapolis was a
boondoggle.  The Hilton in Minneapolis  of all the IETF meetings I=E2=80=99=
ve
attended has the most optimal layout of meeting rooms etc.
>
>
> If we were to choose one place in the U.S. to meet, Minneapolis is the
best choice IMHO.  It's very reasonably priced, easy for many to get to
and the hotel has adequate space for us (even back when we had many more
attendees).  Personally, the weather is not critical to me, since I
spend the vast majority of my time in the hotel meeting rooms, so I'm
very happy if we meet there in March and November.
>
> Mary
>
> On Mon, Aug 6, 2012 at 9:18 AM, Dearlove, Christopher (UK)
<Chris.Dearlove@baesystems.com> wrote:
> I've never been to an IETF meeting where the plane fare has exceeded
the hotel cost for a week. Caveats to that are that I have mostly gone
for IETF recommended hotels, so may have missed particularly cheap
hotels, and that I have only been to North American and Europe (but that
statistic includes Vancouver and the even further away western US cities
down to San Diego). And of course I fly economy, and it's much cheaper
including a Saturday night in your trip, even at the cost of an extra
night in a hotel (at least it is from here). An almost exception was
Paris this year where I was staying fairly cheaply, but that was a
cost-shared trip between me and my employer, and I didn't fly (I went by
train - though that's not cheaper, just better). Paris has cheap(er)
hotels and a metro I understand, so I felt less location constrained.
>
> --
> Christopher Dearlove
> Senior Principal Engineer, Communications Group
> Communications, Networks and Image Analysis Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194 |  Fax: +44 1245 242124
> chris.dearlove@baesystems.com | http://www.baesystems.com
>
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace
Centre, Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687
>
>
> -----Original Message-----
> From: Sprecher, Nurit (NSN - IL/Hod HaSharon)
[mailto:nurit.sprecher@nsn.com]
> Sent: 06 August 2012 15:07
> To: Dearlove, Christopher (UK); Daniele Ceccarelli; Andrew Sullivan;
ietf@ietf.org
> Subject: RE: So, where to repeat? (was:Re: management granularity)
>
> ----------------------! WARNING ! ----------------------
> This message originates from outside our organisation,
> either from an external partner or from the internet.
> Keep this in mind if you answer this message.
> Follow the 'Report Suspicious Emails' link on IT matters
> for instructions on reporting suspicious email messages.
> --------------------------------------------------------
>
> When you are not close (time), flight cost may become higher in the
priority (over hotem)....
> Flying to Vancouver for me for example is the most expensive
trip....even though the city is amazing and the host was wonderful!
>
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
Of ext Dearlove, Christopher (UK)
> Sent: Monday, August 06, 2012 4:56 PM
> To: Daniele Ceccarelli; Andrew Sullivan; ietf@ietf.org
> Subject: RE: So, where to repeat? (was:Re: management granularity)
>
> Dublin's problem was that the venue was isolated from the city. This
has also been the case with e.g. San Diego. (I'm assuming no personal
car.) Contrast with Minneapolis (and several other places) where you
were right in the city. Being in a city is better for lunch and dinner
options, taking a break to go to a bookshop (or to buy something you
forgot to bring) and so on. (I'm deliberately not including tourism
here.)
>
> However at the moment my priorities to make being able to attend
possible would be time (so the closer to me the better - I realise
that's impossible globally), cost (hotel first, flight second, rest is
noise) and the ability to plan ahead to only attend part of the week.
This is the current economic reality. Dublin actually scores quite well
on those for me.
>
> --
> Christopher Dearlove
> Senior Principal Engineer, Communications Group
> Communications, Networks and Image Analysis Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194 |  Fax: +44 1245 242124
> chris.dearlove@baesystems.com | http://www.baesystems.com
>
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace
Centre, Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687
>
>
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
Of Daniele Ceccarelli
> Sent: 06 August 2012 13:24
> To: Andrew Sullivan; ietf@ietf.org
> Subject: RE: So, where to repeat? (was:Re: management granularity)
>
> ----------------------! WARNING ! ----------------------
> This message originates from outside our organisation,
> either from an external partner or from the internet.
> Keep this in mind if you answer this message.
> Follow the 'Report Suspicious Emails' link on IT matters
> for instructions on reporting suspicious email messages.
> --------------------------------------------------------
>
> Dublin panned? I thought it was one of the best venues and locations
of the last meetings.
>
> What about Italy or Spain? I've never heard about an IETF in Italy.
I'm ok with meetings outside Italy since i like traveling very much, but
i was wondering why it has never been taken into account in the past
meetings. Is it expensive? I think Italy and Spain are much cheaper than
France, UK or Sweden, aren't they?
>
> BR
> Daniele
>
> >-----Original Message-----
> >From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On
> >Behalf Of Andrew Sullivan
> >Sent: luned=C3=AC 6 agosto 2012 14.06
> >To: ietf@ietf.org
> >Subject: So, where to repeat? (was:Re: management granularity)
> >
> >On Sun, Aug 05, 2012 at 11:58:19AM -0700, Dave Crocker wrote:
> >> enough merely to have excellent staff.  We need to go back to the
> >> better places and benefit from the learning curve.  This
> >doesn't mean
> >> "no new venues" but it means fewer.
> >
> >As a practical matter, may I ask about which venues you want
> >to return to?  I get your argument in principle, but it seems
> >to me that there has been quite a lot of complaining in the
> >past.  The one factor that seems to me most likely to reduce
> >complaints -- weather -- is evidently beyond the Secretariat's
> >or IAOC's control.
> >
> >People seem inclined to return to the Hyatt in Vancouver,
> >elevators notwithstanding.  We're going to do that.  (I don't
> >understand why the previous Vencouver venue was less desirable
> >-- to me, these venues were very similar, and not very far
> >apart.  I note, however, that the previous two Vancouver
> >visits were near the end of the year, when it rains all the
> >time in Vancouver.)
> >
> >People complained at length about the venue in Paris, so I
> >presume it's out.
> >
> >Some people complained about the hotel room prices and travel
> >expense in Taipei, though I heard remarks that it was a good venue.
> >Should we try to return there?
> >
> >People complained in advance about getting to Qu=C3=A9bec, although
> >afterwards I heard lots of good noises about that venue.  I
> >note that the weather was great.  Should we try to return?
> >
> >I don't recall much complaining about the Prague venue in
> >2011, which was striking to me because very little seemed
> >different to me compared to our first visit there.  Perhaps
> >this is evidence of the "tuning"
> >you suggest (ensuring the water bottles were plastic, for instance).
> >But I note the weather was excellent.
> >
> >Beijing?  I guess Maastricht is out. Anaheim (FWIW, I thought
> >that was an example of a terrible location, but many people
> >seemed happy with it)?  Hiroshima?  Stockholm?  San Francisco
> >(we thought the crime at Paris was bad, yet didn't complain
> >about being smack up against the Tenderloin)?  Or there's the
> >old standby, Minneapolis; perhaps we could do it in March.
> >The Dublin venue was panned by large numbers of people.
> >Philadelphia, people complained about expense.  Chicago, too
> >(combined with hotel renovations).
> >
> >That gets us back through 2007.  Which of the venues do you
> >think we should return to, to which we already haven't
> >returned or planned to return?  And why?
> >
> >For what it's worth, I would not complain about returning to
> >any of those venues; I personally had good meetings at all of
> >them except Hiroshima, which I missed due to other
> >commitments.  That includes both Maastricht and Dublin, which
> >were both apparently trials for large numbers of others.
> >
> >Best,
> >
> >A
> >
> >--
> >Andrew Sullivan
> >ajs@anvilwalrusden.com
> >
> >
>
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************
>
>



From dave@cridland.net  Thu Aug  9 01:27:52 2012
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 1D62E21F875E for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 01:27:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SSx5SzGduskU for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 01:27:51 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 13A5821F8759 for <ietf@ietf.org>; Thu,  9 Aug 2012 01:27:50 -0700 (PDT)
Received: by wgbdr13 with SMTP id dr13so112596wgb.13 for <ietf@ietf.org>; Thu, 09 Aug 2012 01:27:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=88KCLUG/6W3PSAhp4k9+6wBKR8Z8X5gkmNcCYZH8Ab0=; b=FUzc0MbK0/PidnN1e6i5CMicWQLgqZdgIL5KCtNtxekqpg9uKppOzh7ByesSzAKtVr ZQS16jsCNlJqjO+do+qzc/9g9vGRp90Cj8/FOtUHyhW2aSpgfDJWVRlvnmiAZJba7Ajx gpqb5TQPuPTw7PynwcRzJxmNqSPPpWYnVgDgg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=88KCLUG/6W3PSAhp4k9+6wBKR8Z8X5gkmNcCYZH8Ab0=; b=jbE5+7WKHhBA/136UdR+hN2pvAM27BD6Av3Ap9jagK68LQB7RF4rewZgFvo2bZB6WI fs4QHSk5uPn4uR653GVUvCWxcOqRO1ghAvW2bVPIaKlZbFM2Wo1pn5CXt2FE082oKI7h JxCxKVcFYQZjjoa5s6c9zw/TVL7LDbwbfE25ftPwVDvJJm3S6dWED6c0o25ubf+OBZNh tMJggyECsbecbjEIDX5hA2EBQT6Qe4RvlewiIrDg79xeXZUAE3y10vAwVMIpuIUZuhpW iPxsCNZCF/TI87jSSkp2cdNP1qRg0jQ0eUbaaz+pJlg0BS3wXs9ca0fS6qmV8EHwMyrC ES8g==
MIME-Version: 1.0
Received: by 10.180.106.97 with SMTP id gt1mr903023wib.5.1344500870208; Thu, 09 Aug 2012 01:27:50 -0700 (PDT)
Received: by 10.194.33.66 with HTTP; Thu, 9 Aug 2012 01:27:50 -0700 (PDT)
Received: by 10.194.33.66 with HTTP; Thu, 9 Aug 2012 01:27:50 -0700 (PDT)
In-Reply-To: <006701cd7606$17ff48a0$4001a8c0@gateway.2wire.net>
References: <CALaySJKV96tdXhzfPD1e1Mro_+gp5aDarF7Z06QrA+iQtnHkLw@mail.gmail.com> <501A5656.2050407@it.aoyama.ac.jp> <501BEC0D.1060404@tana.it> <009101cd7476$bb522c20$4001a8c0@gateway.2wire.net> <599B1629-543A-49BC-A0E7-FA2096C538AD@checkpoint.com> <03e701cd749f$73891c40$4001a8c0@gateway.2wire.net> <50229D32.8000605@tana.it> <006701cd7606$17ff48a0$4001a8c0@gateway.2wire.net>
Date: Thu, 9 Aug 2012 09:27:50 +0100
Message-ID: <CAKHUCzzsf6veDR+uwxnMw4Koh0Kj7FqoQpsUbENMb_r3v0G89A@mail.gmail.com>
Subject: Re: RFC Errata: when to file, and when not to
From: Dave Cridland <dave@cridland.net>
To: "t.p." <daedulus@btconnect.com>
Content-Type: multipart/alternative; boundary=f46d04428066c4dd9304c6d1003a
X-Gm-Message-State: ALoCoQmrz3cD+0KF0CJkEv4+dERhysdQbGgjIuBikYWxwEyE4k7AR7jC2LAXe+bkBUeDHOXK0fLI
Cc: ietf@ietf.org, Alessandro Vesely <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 08:27:52 -0000

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

Does anyone other than historians honestly care what the original was? I
mean, really?

Dave.

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

<p>Does anyone other than historians honestly care what the original was? I mean, really?</p>
<p>Dave.</p>

--f46d04428066c4dd9304c6d1003a--

From spromano@unina.it  Thu Aug  9 01:48:34 2012
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 2EE9B21F8715 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 01:48:34 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 35KItBkSlW0F for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 01:48:33 -0700 (PDT)
Received: from smtp1.unina.it (smtp1.unina.it [192.132.34.61]) by ietfa.amsl.com (Postfix) with ESMTP id 2A94A21F86C8 for <ietf@ietf.org>; Thu,  9 Aug 2012 01:48:32 -0700 (PDT)
Received: from [192.168.1.180] (host95-146-dynamic.10-87-r.retail.telecomitalia.it [87.10.146.95]) (authenticated bits=0) by smtp1.unina.it (8.14.4/8.14.4) with ESMTP id q798mRCU016693 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 9 Aug 2012 10:48:29 +0200
Message-ID: <50237958.20008@unina.it>
Date: Thu, 09 Aug 2012 10:48:24 +0200
From: Simon Pietro Romano <spromano@unina.it>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: Meetecho session recording for IETF-84 Telepresence (CLUE) Tutorial
References: <CAHBDyN70JABA4SrQGjJGTZTZyeA611tdRJB_+QL7VBJTaCRAVQ@mail.gmail.com> <8FEE254D-9256-4DDF-894F-6F046B4D6E2E@tzi.org>
In-Reply-To: <8FEE254D-9256-4DDF-894F-6F046B4D6E2E@tzi.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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, 09 Aug 2012 08:48:34 -0000

Wow,

your comment is a bit harsh, but it definitely makes some sense :-). 
Even though I personally don't find recorded audio as useless as you 
claim, audio quality might undoubtedly be better than it currently is. 
What we are using now is one of the standard VoIP options provided by 
Asterisk. You have to keep in mind that the recordings we provide do 
represent an exact reproduction of the real-time conference we streamed 
live. This said, we'll certainly improve audio quality in the upcoming 
releases of our platform.

Thank you for your precious feedback,

Simon

Il 09/08/2012 00:33, Carsten Bormann ha scritto:
> On Aug 8, 2012, at 22:38, Mary Barnes <mary.ietf.barnes@gmail.com> wrote:
>
>>   If you've never had the time to watch a Meetecho session recording,
> OMG, was the audio recovered from air bubbling up from a submarine or what happened?
>
> Oh, and maybe somebody can explain the value of the audio spectrum above 4 kHz to the meetecho guys.
>
> With this audio quality, this is very close to useless (except maybe for historians digging it up 5000 years in the future and painstakingly reconstructing what was maybe said).
>
> Grüße, Carsten
>
>

-- 
                             _\\|//_
                             ( 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 spromano@unina.it  Thu Aug  9 01:55:52 2012
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 6646921F86CF for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 01:55:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.718
X-Spam-Level: 
X-Spam-Status: No, score=-100.718 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5yl2WBWGPCQa for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 01:55:51 -0700 (PDT)
Received: from smtp1.unina.it (smtp1.unina.it [192.132.34.61]) by ietfa.amsl.com (Postfix) with ESMTP id 5958721F869D for <ietf@ietf.org>; Thu,  9 Aug 2012 01:55:51 -0700 (PDT)
Received: from [192.168.1.180] (host95-146-dynamic.10-87-r.retail.telecomitalia.it [87.10.146.95]) (authenticated bits=0) by smtp1.unina.it (8.14.4/8.14.4) with ESMTP id q798tb90017218 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 9 Aug 2012 10:55:48 +0200
Message-ID: <50237B05.4070408@unina.it>
Date: Thu, 09 Aug 2012 10:55:33 +0200
From: Simon Pietro Romano <spromano@unina.it>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: Meetecho session recording for IETF-84 Telepresence (CLUE) Tutorial
References: <CAHBDyN70JABA4SrQGjJGTZTZyeA611tdRJB_+QL7VBJTaCRAVQ@mail.gmail.com> <8FEE254D-9256-4DDF-894F-6F046B4D6E2E@tzi.org> <CAHBDyN4J8Eyr59S9O0XPYW8aORuYXrTTVafs20sqWm=kMA7zoA@mail.gmail.com>
In-Reply-To: <CAHBDyN4J8Eyr59S9O0XPYW8aORuYXrTTVafs20sqWm=kMA7zoA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------020001030101070207040809"
Cc: Carsten Bormann <cabo@tzi.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, 09 Aug 2012 08:55:52 -0000

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


> It's also extremely important to consider that these guys are 
> providing the service at no cost to IETF.  I can't fathom what the 
> cost would be if IETF were paying for something that might meet your 
> quality standards.

Thank you Mary for your support. Anyhow, I think the discussion on the 
quality of the remote participation tools should be conducted 
independently from the fact that people involved in the service get paid 
or not. If something can be improved, we just have to try and improve 
it! Meetecho has learned a lot from ietffers' comments and has also got 
used to their extreme frankness...

Cheers,

Simo

>
> Regards,
> Mary.
>
> On Wed, Aug 8, 2012 at 5:33 PM, Carsten Bormann <cabo@tzi.org 
> <mailto:cabo@tzi.org>> wrote:
>
>     On Aug 8, 2012, at 22:38, Mary Barnes <mary.ietf.barnes@gmail.com
>     <mailto:mary.ietf.barnes@gmail.com>> wrote:
>
>     >  If you've never had the time to watch a Meetecho session recording,
>
>     OMG, was the audio recovered from air bubbling up from a submarine
>     or what happened?
>
>     Oh, and maybe somebody can explain the value of the audio spectrum
>     above 4 kHz to the meetecho guys.
>
>     With this audio quality, this is very close to useless (except
>     maybe for historians digging it up 5000 years in the future and
>     painstakingly reconstructing what was maybe said).
>
>     Grüße, Carsten
>
>

-- 
                             _\\|//_
                             ( 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~~~~~~~~~~~~~~~~~~~~~~~~~
                           \ (    (   )
                            \_)    ) /
                                  (_/


--------------020001030101070207040809
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">
    <br>
    <blockquote
cite="mid:CAHBDyN4J8Eyr59S9O0XPYW8aORuYXrTTVafs20sqWm=kMA7zoA@mail.gmail.com"
      type="cite">
      <div>It's also extremely important to consider that these guys are
        providing the service at no cost to IETF. &nbsp;I can't fathom what
        the cost would be if IETF were paying for something that might
        meet your quality standards.</div>
    </blockquote>
    <br>
    Thank you Mary for your support. Anyhow, I think the discussion on
    the quality of the remote participation tools should be conducted
    independently from the fact that people involved in the service get
    paid or not. If something can be improved, we just have to try and
    improve it! Meetecho has learned a lot from ietffers' comments and
    has also got used to their extreme frankness...<br>
    <br>
    Cheers,<br>
    <br>
    Simo<br>
    <br>
    <blockquote
cite="mid:CAHBDyN4J8Eyr59S9O0XPYW8aORuYXrTTVafs20sqWm=kMA7zoA@mail.gmail.com"
      type="cite">
      <div><br>
      </div>
      <div>Regards,</div>
      <div>Mary.&nbsp;<br>
        <div><br>
          <div class="gmail_quote">On Wed, Aug 8, 2012 at 5:33 PM,
            Carsten Bormann <span dir="ltr">&lt;<a
                moz-do-not-send="true" href="mailto:cabo@tzi.org"
                target="_blank">cabo@tzi.org</a>&gt;</span> wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div class="im">On Aug 8, 2012, at 22:38, Mary Barnes &lt;<a
                  moz-do-not-send="true"
                  href="mailto:mary.ietf.barnes@gmail.com">mary.ietf.barnes@gmail.com</a>&gt;
                wrote:<br>
                <br>
                &gt; &nbsp;If you've never had the time to watch a Meetecho
                session recording,<br>
                <br>
              </div>
              OMG, was the audio recovered from air bubbling up from a
              submarine or what happened?<br>
              <br>
              Oh, and maybe somebody can explain the value of the audio
              spectrum above 4 kHz to the meetecho guys.<br>
              <br>
              With this audio quality, this is very close to useless
              (except maybe for historians digging it up 5000 years in
              the future and painstakingly reconstructing what was maybe
              said).<br>
              <br>
              Gr&uuml;&szlig;e, Carsten<br>
              <br>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
                            _\\|//_
                            ( 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: <a class="moz-txt-link-abbreviated" href="mailto:spromano@unina.it">spromano@unina.it</a>
          <a class="moz-txt-link-freetext" href="http://www.comics.unina.it/simonpietro.romano">http://www.comics.unina.it/simonpietro.romano</a>

    &lt;&lt;Molti mi dicono che lo scoraggiamento &egrave; l'alibi degli 
   idioti. Ci rifletto un istante; e mi scoraggio&gt;&gt;. Magritte.
                         oooO
   ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                          \ (    (   )
                           \_)    ) /
                                 (_/

</pre>
  </body>
</html>

--------------020001030101070207040809--

From spromano@unina.it  Thu Aug  9 01:58:20 2012
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 BDCEB21F8740 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 01:58:20 -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=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P4PpVEpP6HvG for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 01:58:20 -0700 (PDT)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by ietfa.amsl.com (Postfix) with ESMTP id B520B21F873E for <ietf@ietf.org>; Thu,  9 Aug 2012 01:58:19 -0700 (PDT)
Received: from [192.168.1.180] (host95-146-dynamic.10-87-r.retail.telecomitalia.it [87.10.146.95]) (authenticated bits=0) by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id q798w9UO001216 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 9 Aug 2012 10:58:10 +0200
Message-ID: <50237B9E.6070002@unina.it>
Date: Thu, 09 Aug 2012 10:58:06 +0200
From: Simon Pietro Romano <spromano@unina.it>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: joel jaeggli <joelja@bogus.com>
Subject: Re: Meetecho session recording for IETF-84 Telepresence (CLUE) Tutorial
References: <CAHBDyN70JABA4SrQGjJGTZTZyeA611tdRJB_+QL7VBJTaCRAVQ@mail.gmail.com> <8FEE254D-9256-4DDF-894F-6F046B4D6E2E@tzi.org> <CAHBDyN4J8Eyr59S9O0XPYW8aORuYXrTTVafs20sqWm=kMA7zoA@mail.gmail.com> <5022EFC3.5030308@bogus.com>
In-Reply-To: <5022EFC3.5030308@bogus.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Carsten Bormann <cabo@tzi.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, 09 Aug 2012 08:58:20 -0000

>
> Too clarify something. The various experimental and ongoing volunteer 
> efforts and well as contractor provided services has non-trivial 
> trivial support costs even when they are delivered by volunteers 
> paying their own way. We can and should (and do) evaluate how we can 
> do better, whether they're appropiate or not and what else we should 
> be doing.

+1

Simon

>> Regards,
>> Mary.
>>
>> On Wed, Aug 8, 2012 at 5:33 PM, Carsten Bormann <cabo@tzi.org 
>> <mailto:cabo@tzi.org>> wrote:
>>
>>     On Aug 8, 2012, at 22:38, Mary Barnes <mary.ietf.barnes@gmail.com
>>     <mailto:mary.ietf.barnes@gmail.com>> wrote:
>>
>>     >  If you've never had the time to watch a Meetecho session 
>> recording,
>>
>>     OMG, was the audio recovered from air bubbling up from a submarine
>>     or what happened?
>>
>>     Oh, and maybe somebody can explain the value of the audio spectrum
>>     above 4 kHz to the meetecho guys.
>>
>>     With this audio quality, this is very close to useless (except
>>     maybe for historians digging it up 5000 years in the future and
>>     painstakingly reconstructing what was maybe said).
>>
>>     Grüße, Carsten
>>
>>
>
>

-- 
                             _\\|//_
                             ( 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 spromano@unina.it  Thu Aug  9 02:50:55 2012
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 8306C21F869F for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 02:50:55 -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=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IaigBtxoQTmT for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 02:50:54 -0700 (PDT)
Received: from smtp1.unina.it (smtp1.unina.it [192.132.34.61]) by ietfa.amsl.com (Postfix) with ESMTP id 50BB621F85DD for <ietf@ietf.org>; Thu,  9 Aug 2012 02:50:54 -0700 (PDT)
Received: from [192.168.1.180] (host95-146-dynamic.10-87-r.retail.telecomitalia.it [87.10.146.95]) (authenticated bits=0) by smtp1.unina.it (8.14.4/8.14.4) with ESMTP id q799og6w020773 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 9 Aug 2012 11:50:51 +0200
Message-ID: <502387EE.3070900@unina.it>
Date: Thu, 09 Aug 2012 11:50:38 +0200
From: Simon Pietro Romano <spromano@unina.it>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: Meetecho session recording for IETF-84 Telepresence (CLUE) Tutorial
References: <CAHBDyN70JABA4SrQGjJGTZTZyeA611tdRJB_+QL7VBJTaCRAVQ@mail.gmail.com> <8FEE254D-9256-4DDF-894F-6F046B4D6E2E@tzi.org> <CAHBDyN4J8Eyr59S9O0XPYW8aORuYXrTTVafs20sqWm=kMA7zoA@mail.gmail.com> <E9CE0F6F-464E-48A1-A378-5CCCE9354D93@tzi.org>
In-Reply-To: <E9CE0F6F-464E-48A1-A378-5CCCE9354D93@tzi.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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, 09 Aug 2012 09:50:56 -0000

> Recording at a sampling rate of 8 kHz in 2012?  That's incomprehensible (in both senses).  And then applying some inferior compression scheme that inserts heavy artifacts.  They can do better.  Much better.  For exactly the same cost.
Again, we can do better, independently from the cost. Indeed, people can 
always do better. One of Meetecho's mottos, though, is "better is the 
enemy of good". If we wanted to have the 'perfect' platform available, 
we'd still be working on fine-tuning the bits of its architecture. What 
we wanted, instead, was an operational tool that people could use in 
real-world scenarios like the IETF meetings (which in my view do 
represent the perfect playground for remote participation support tools).

> If the meetecho guys use the IETF as a pilot customer, they need honest feedback. Honest and candid.  Like the one I'm providing here.  They don't want to be remembered by 1000 people as the guys who can't get audio right.
Definitely not!
> The fact that the tutorial is about telepresence adds a measure of irony...
> (Which gets to the point of hilarious when the SDP example actually uses PCMU/8000 :-)
You're too "candid" now :-). Meetecho is not a telepresence platform, 
but rather a real-time web-enabled collaboration framework.

Simon
> Grüße, Carsten
>
>

-- 
                             _\\|//_
                             ( 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 john-ietf@jck.com  Thu Aug  9 04:01:01 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC6CA21F8665 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 04:01:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level: 
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CZpWE3G7wmjJ for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 04:01:01 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id DABFF21F8661 for <ietf@ietf.org>; Thu,  9 Aug 2012 04:01:00 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SzQO7-000OQB-EA; Thu, 09 Aug 2012 06:54:47 -0400
Date: Thu, 09 Aug 2012 07:00:44 -0400
From: John C Klensin <john-ietf@jck.com>
To: Dave Cridland <dave@cridland.net>, "t.p." <daedulus@btconnect.com>
Subject: Re: RFC Errata: when to file, and when not to
Message-ID: <5256BF9BC9AE13013F066C4E@JcK-HP8200.jck.com>
In-Reply-To: <CAKHUCzzsf6veDR+uwxnMw4Koh0Kj7FqoQpsUbENMb_r3v0G89A@mail.gmail.com>
References: <CALaySJKV96tdXhzfPD1e1Mro_+gp5aDarF7Z06QrA+iQtnHkLw@mail.gmail.com> <501A5656.2050407@it.aoyama.ac.jp> <501BEC0D.1060404@tana.it> <009101cd7476$bb522c20$4001a8c0@gateway.2wire.net> <599B1629-543A-49BC-A0E7-FA2096C538AD@checkpoint.com> <03e701cd749f$73891c40$4001a8c0@gateway.2wire.net> <50229D32.8000605@tana.it> <006701cd7606$17ff48a0$4001a8c0@gateway.2wire.net> <CAKHUCzzsf6veDR+uwxnMw4Koh0Kj7FqoQpsUbENMb_r3v0G89A@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org, Alessandro Vesely <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 11:01:01 -0000

--On Thursday, August 09, 2012 09:27 +0100 Dave Cridland
<dave@cridland.net> wrote:

> Does anyone other than historians honestly care what the
> original was? I mean, really?

Dave,

RFCs are often incorporated by reference in procurement
documents and conformity requirements.  If one were trying to
interpret or enforce such a requirement, it would almost
certainly be useful to know _exactly_ what version of an RFC and
its interpretations was agreed to.

   john




From dave@cridland.net  Thu Aug  9 04:35:43 2012
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 BBF9C21F85F7 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 04:35:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xWxgNBmDZ6yl for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 04:35:43 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id B1C2621F85C5 for <ietf@ietf.org>; Thu,  9 Aug 2012 04:35:42 -0700 (PDT)
Received: by weyu54 with SMTP id u54so268060wey.31 for <ietf@ietf.org>; Thu, 09 Aug 2012 04:35:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0KUgZNA5rhf6ap7th+1JPQZUEs39DT1HDxDC7opohKE=; b=i6l0Go7QAPnPQ7lQMhJRtgWgDbuJHFgfk1MpFxY/uO/k15JB4hhumoMDNj2iA+/P4g Ljjs0xZ5loL8wsPgH+AzE5WYwzne87tQOBIhPov/D22fE7hOLZKV+mcTWDn77OLKsZzQ BFLmLssFO3Fg9a4xpIuEp1JftiJm9wUn7ASXg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=0KUgZNA5rhf6ap7th+1JPQZUEs39DT1HDxDC7opohKE=; b=Xj1D33M/fgCGA4n/CVyaSekqkXibGXQYqaNkQoATnEgzB925HDTP5KikCuloOHBm2t crYmRNB4MQ2FvIejW2mmayXDq4/4g7ieiO0sD8L5ABduM41YESWAj3Pl1Ep6gToDhkI7 yOjiOxPiNPIMJ4wr4ut+gooyF55DIsfKNks0kXVc4XfT3+t4B/I4K0Q7Atjxs5eYOylP QDuORrVYdtLL0PKTR4RWjUAoI7fUtBwQmaAxgKKlBGaNcYBLmAB39oq0JSdZKvOK3xwp oBrZH5mD1/0Jg9LaK1PWkclyLxyTZ+w+JiPQCiVqu6OxBsamhebVxtaZ0IZSRu7NioSz KbNw==
MIME-Version: 1.0
Received: by 10.216.133.153 with SMTP id q25mr914999wei.11.1344512141426; Thu, 09 Aug 2012 04:35:41 -0700 (PDT)
Received: by 10.194.33.66 with HTTP; Thu, 9 Aug 2012 04:35:41 -0700 (PDT)
Received: by 10.194.33.66 with HTTP; Thu, 9 Aug 2012 04:35:41 -0700 (PDT)
In-Reply-To: <5256BF9BC9AE13013F066C4E@JcK-HP8200.jck.com>
References: <CALaySJKV96tdXhzfPD1e1Mro_+gp5aDarF7Z06QrA+iQtnHkLw@mail.gmail.com> <501A5656.2050407@it.aoyama.ac.jp> <501BEC0D.1060404@tana.it> <009101cd7476$bb522c20$4001a8c0@gateway.2wire.net> <599B1629-543A-49BC-A0E7-FA2096C538AD@checkpoint.com> <03e701cd749f$73891c40$4001a8c0@gateway.2wire.net> <50229D32.8000605@tana.it> <006701cd7606$17ff48a0$4001a8c0@gateway.2wire.net> <CAKHUCzzsf6veDR+uwxnMw4Koh0Kj7FqoQpsUbENMb_r3v0G89A@mail.gmail.com> <5256BF9BC9AE13013F066C4E@JcK-HP8200.jck.com>
Date: Thu, 9 Aug 2012 12:35:41 +0100
Message-ID: <CAKHUCzza0ba9eDsEHF+y_icmeWTB8Y=3vb3zw83dGi+4-uh77Q@mail.gmail.com>
Subject: Re: RFC Errata: when to file, and when not to
From: Dave Cridland <dave@cridland.net>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=0016e6de002296006004c6d3a0f9
X-Gm-Message-State: ALoCoQnE7I/5Oua2VAyflb1qxgf0hjv1tabFG90ZhyCNFp9NI3eU48TOHfUM05Um5WTaRGR2xWpt
Cc: ietf@ietf.org, Alessandro Vesely <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 11:35:43 -0000

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

It seems entirely reasonable that there needs to be a version available
that's precisely as-published, for legal (and quasi-legal) reasons, as you
say - however, that's the version produced by the RFC Editor, and not the
tools version (which is already non-normative, technically, due to the
markup).

What I'm driving at is whether the right way to handle errata is by
changing the document on tools (perhaps by diff submission). This should
reduce the mechanical workload of errata handling to near-zero, and leave
the judgement calls of whether to accept them as the cost.

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

<p>It seems entirely reasonable that there needs to be a version available =
that&#39;s precisely as-published, for legal (and quasi-legal) reasons, as =
you say - however, that&#39;s the version produced by the RFC Editor, and n=
ot the tools version (which is already non-normative, technically, due to t=
he markup).</p>

<p>What I&#39;m driving at is whether the right way to handle errata is by =
changing the document on tools (perhaps by diff submission). This should re=
duce the mechanical workload of errata handling to near-zero, and leave the=
 judgement calls of whether to accept them as the cost.</p>


--0016e6de002296006004c6d3a0f9--

From ynir@checkpoint.com  Thu Aug  9 04:53:19 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02FAB21F8670 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 04:53:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.388
X-Spam-Level: 
X-Spam-Status: No, score=-10.388 tagged_above=-999 required=5 tests=[AWL=0.210, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rwtH66DNZA4y for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 04:53:18 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id DC99221F86A7 for <ietf@ietf.org>; Thu,  9 Aug 2012 04:53:17 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id q79BrDFG016541; Thu, 9 Aug 2012 14:53:13 +0300
X-CheckPoint: {5023A1BA-0-1B221DC2-4FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Thu, 9 Aug 2012 14:53:12 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Dave Cridland <dave@cridland.net>
Date: Thu, 9 Aug 2012 14:53:12 +0300
Subject: Re: RFC Errata: when to file, and when not to
Thread-Topic: RFC Errata: when to file, and when not to
Thread-Index: Ac12JY1x18in8MdwQF+5uPrMkD9yhg==
Message-ID: <EA2F8447-D700-4E22-85A6-30BAD12DF3E6@checkpoint.com>
References: <CALaySJKV96tdXhzfPD1e1Mro_+gp5aDarF7Z06QrA+iQtnHkLw@mail.gmail.com> <501A5656.2050407@it.aoyama.ac.jp> <501BEC0D.1060404@tana.it> <009101cd7476$bb522c20$4001a8c0@gateway.2wire.net> <599B1629-543A-49BC-A0E7-FA2096C538AD@checkpoint.com> <03e701cd749f$73891c40$4001a8c0@gateway.2wire.net> <50229D32.8000605@tana.it> <006701cd7606$17ff48a0$4001a8c0@gateway.2wire.net> <CAKHUCzzsf6veDR+uwxnMw4Koh0Kj7FqoQpsUbENMb_r3v0G89A@mail.gmail.com> <5256BF9BC9AE13013F066C4E@JcK-HP8200.jck.com> <CAKHUCzza0ba9eDsEHF+y_icmeWTB8Y=3vb3zw83dGi+4-uh77Q@mail.gmail.com>
In-Reply-To: <CAKHUCzza0ba9eDsEHF+y_icmeWTB8Y=3vb3zw83dGi+4-uh77Q@mail.gmail.com>
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: multipart/alternative; boundary="_000_EA2F8447D7004E2285A630BAD12DF3E6checkpointcom_"
MIME-Version: 1.0
Cc: John C Klensin <john-ietf@jck.com>, "ietf@ietf.org" <ietf@ietf.org>, Alessandro Vesely <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 11:53:19 -0000

--_000_EA2F8447D7004E2285A630BAD12DF3E6checkpointcom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


On Aug 9, 2012, at 2:35 PM, Dave Cridland wrote:


It seems entirely reasonable that there needs to be a version available tha=
t's precisely as-published, for legal (and quasi-legal) reasons, as you say=
 - however, that's the version produced by the RFC Editor, and not the tool=
s version (which is already non-normative, technically, due to the markup).

What I'm driving at is whether the right way to handle errata is by changin=
g the document on tools (perhaps by diff submission). This should reduce th=
e mechanical workload of errata handling to near-zero, and leave the judgem=
ent calls of whether to accept them as the cost.

This means that there would be two documents with the same RFC number. The =
quasi-leagal "as published" one, and the one of the tools site. Which shoul=
d I follow when I go to implement?

If the errors amount to something that would really make a difference in im=
plementation, you really need a new RFC, and can't handle this in an erratu=
m.

See for example RFC 4753. The erratum changed bits on the wire, so a replac=
ement RFC (5903) had to be published.

RFC 5903 also has two errata, which were rejected. But they are editorial, =
so even had they been accepted, they would not require a new RFC.

--_000_EA2F8447D7004E2285A630BAD12DF3E6checkpointcom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode:=
 space; -webkit-line-break: after-white-space; "><br><div><div>On Aug 9, 20=
12, at 2:35 PM, Dave Cridland wrote:</div><br class=3D"Apple-interchange-ne=
wline"><blockquote type=3D"cite"><p>It seems entirely reasonable that there=
 needs to be a version available that's precisely as-published, for legal (=
and quasi-legal) reasons, as you say - however, that's the version produced=
 by the RFC Editor, and not the tools version (which is already non-normati=
ve, technically, due to the markup).</p><p>What I'm driving at is whether t=
he right way to handle errata is by changing the document on tools (perhaps=
 by diff submission). This should reduce the mechanical workload of errata =
handling to near-zero, and leave the judgement calls of whether to accept t=
hem as the cost.</p>


</blockquote></div>This means that there would be two documents with the sa=
me RFC number. The quasi-leagal "as published" one, and the one of the tool=
s site. Which should I follow when I go to implement?<div><br></div><div>If=
 the errors amount to something that would really make a difference in impl=
ementation, you really need a new RFC, and can't handle this in an erratum.=
</div><div><br></div><div>See for example RFC 4753. The erratum changed bit=
s on the wire, so a replacement RFC (5903) had to be published.</div><div><=
br></div><div>RFC 5903 also has two errata, which were rejected. But they a=
re editorial, so even had they been accepted, they would not require a new =
RFC.</div></body></html>=

--_000_EA2F8447D7004E2285A630BAD12DF3E6checkpointcom_--

From john-ietf@jck.com  Thu Aug  9 05:34:29 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D54CF21F8617 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 05:34:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level: 
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 361LctoDuK5B for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 05:34:29 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 44DAA21F85E4 for <ietf@ietf.org>; Thu,  9 Aug 2012 05:34:29 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SzRqZ-000OaV-2T; Thu, 09 Aug 2012 08:28:15 -0400
Date: Thu, 09 Aug 2012 08:34:12 -0400
From: John C Klensin <john-ietf@jck.com>
To: Yoav Nir <ynir@checkpoint.com>, Dave Cridland <dave@cridland.net>
Subject: Re: RFC Errata: when to file, and when not to
Message-ID: <E3A4486529AAE3D8CD2A0098@JcK-HP8200.jck.com>
In-Reply-To: <EA2F8447-D700-4E22-85A6-30BAD12DF3E6@checkpoint.com>
References: <CALaySJKV96tdXhzfPD1e1Mro_+gp5aDarF7Z06QrA+iQtnHkLw@mail.gmail.com> <501A5656.2050407@it.aoyama.ac.jp> <501BEC0D.1060404@tana.it> <009101cd7476$bb522c20$4001a8c0@gateway.2wire.net> <599B1629-543A-49BC-A0E7-FA2096C538AD@checkpoint.com> <03e701cd749f$73891c40$4001a8c0@gateway.2wire.net> <50229D32.8000605@tana.it> <006701cd7606$17ff48a0$4001a8c0@gateway.2wire.net> <CAKHUCzzsf6veDR+uwxnMw4Koh0Kj7FqoQpsUbENMb_r3v0G89A@mail.gmail.com> <5256BF9BC9AE13013F066C4E@JcK-HP8200.jck.com> <CAKHUCzza0ba9eDsEHF+y_icmeWTB8Y=3vb3zw83dGi+4-uh77Q@mail.gmail.com> <EA2F8447-D700-4E22-85A6-30BAD12DF3E6@checkpoint.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org, Alessandro Vesely <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 12:34:30 -0000

--On Thursday, August 09, 2012 14:53 +0300 Yoav Nir
<ynir@checkpoint.com> wrote:

> 
> This means that there would be two documents with the same RFC
> number. The quasi-leagal "as published" one, and the one of
> the tools site. Which should I follow when I go to implement?

Exactly

> If the errors amount to something that would really make a
> difference in implementation, you really need a new RFC, and
> can't handle this in an erratum.
> 
> See for example RFC 4753. The erratum changed bits on the
> wire, so a replacement RFC (5903) had to be published.

And, if I correctly understood it at the time, that is exactly
why the RFC Editor opposed the idea of formal errata for years.
If there were real, substantive, errors, a replacement RFC
should be published as soon as practical.  For anything else,
the most that was desirable would be a collected list of
comments and suggestions that could be considered if/when the
document was revised.

   john


From ynir@checkpoint.com  Thu Aug  9 07:12:28 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D60D321F866E for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 07:12:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.392
X-Spam-Level: 
X-Spam-Status: No, score=-10.392 tagged_above=-999 required=5 tests=[AWL=0.207, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q3Vcec44N4iX for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 07:12:28 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 9F89D21F8669 for <ietf@ietf.org>; Thu,  9 Aug 2012 07:12:27 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id q79ECF16015973; Thu, 9 Aug 2012 17:12:24 +0300
X-CheckPoint: {5023C24F-1-1B221DC2-4FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Thu, 9 Aug 2012 17:11:59 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: John C Klensin <john-ietf@jck.com>
Date: Thu, 9 Aug 2012 17:11:58 +0300
Subject: Re: RFC Errata: when to file, and when not to
Thread-Topic: RFC Errata: when to file, and when not to
Thread-Index: Ac12OPApVuHT5Xo+SauxF2rTXSGDrg==
Message-ID: <4F18A4B6-3D63-4135-A367-F3CAAF4132CF@checkpoint.com>
References: <CALaySJKV96tdXhzfPD1e1Mro_+gp5aDarF7Z06QrA+iQtnHkLw@mail.gmail.com> <501A5656.2050407@it.aoyama.ac.jp> <501BEC0D.1060404@tana.it> <009101cd7476$bb522c20$4001a8c0@gateway.2wire.net> <599B1629-543A-49BC-A0E7-FA2096C538AD@checkpoint.com> <03e701cd749f$73891c40$4001a8c0@gateway.2wire.net> <50229D32.8000605@tana.it> <006701cd7606$17ff48a0$4001a8c0@gateway.2wire.net> <CAKHUCzzsf6veDR+uwxnMw4Koh0Kj7FqoQpsUbENMb_r3v0G89A@mail.gmail.com> <5256BF9BC9AE13013F066C4E@JcK-HP8200.jck.com> <CAKHUCzza0ba9eDsEHF+y_icmeWTB8Y=3vb3zw83dGi+4-uh77Q@mail.gmail.com> <EA2F8447-D700-4E22-85A6-30BAD12DF3E6@checkpoint.com> <E3A4486529AAE3D8CD2A0098@JcK-HP8200.jck.com>
In-Reply-To: <E3A4486529AAE3D8CD2A0098@JcK-HP8200.jck.com>
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: Alessandro Vesely <vesely@tana.it>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 14:12:29 -0000

On Aug 9, 2012, at 3:34 PM, John C Klensin wrote:

>=20
>=20
> --On Thursday, August 09, 2012 14:53 +0300 Yoav Nir
> <ynir@checkpoint.com> wrote:
>=20
>>=20
>> This means that there would be two documents with the same RFC
>> number. The quasi-leagal "as published" one, and the one of
>> the tools site. Which should I follow when I go to implement?
>=20
> Exactly
>=20
>> If the errors amount to something that would really make a
>> difference in implementation, you really need a new RFC, and
>> can't handle this in an erratum.
>>=20
>> See for example RFC 4753. The erratum changed bits on the
>> wire, so a replacement RFC (5903) had to be published.
>=20
> And, if I correctly understood it at the time, that is exactly
> why the RFC Editor opposed the idea of formal errata for years.
> If there were real, substantive, errors, a replacement RFC
> should be published as soon as practical.  For anything else,
> the most that was desirable would be a collected list of
> comments and suggestions that could be considered if/when the
> document was revised.

There are still the spelling mistakes and obvious errors. Take for example =
this one from RFC 5296:

   The EMSKname is in the username part of the NAI and is encoded in
   hexadecimal values.  The EMSKname is 64 bits in length and so the=20
   username portion takes up 128 octets.

Encoding 64 bits in hex requires 16 octets, not 128. I think anyone impleme=
nting this would figure this out, but it is substantive. The RFC was being =
revised anyway, but do you think a replacement RFC would need to be publish=
ed if that were not the case?

Yoav=

From henrik@levkowetz.com  Thu Aug  9 07:49:46 2012
Return-Path: <henrik@levkowetz.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1510821F8661; Thu,  9 Aug 2012 07:49:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fETzx4c7XFT6; Thu,  9 Aug 2012 07:49:45 -0700 (PDT)
Received: from grenache.tools.ietf.org (unknown [IPv6:2a01:3f0:1:2:225:90ff:fe34:720e]) by ietfa.amsl.com (Postfix) with ESMTP id E167D21F865E; Thu,  9 Aug 2012 07:49:44 -0700 (PDT)
Received: from [2a01:3f0:1:0:6d55:bd05:4cb4:b42] (port=52414 helo=brunello.netnod.se) by grenache.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.77) (envelope-from <henrik@levkowetz.com>) id 1SzU37-0005Jb-OD; Thu, 09 Aug 2012 16:49:22 +0200
Message-ID: <5023CDE2.5050104@levkowetz.com>
Date: Thu, 09 Aug 2012 16:49:06 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.6esrpre) Gecko/20120713 Thunderbird/10.0.6
MIME-Version: 1.0
To: Ole Jacobsen <ole@cisco.com>
References: <alpine.OSX.2.01.1207311102470.86865@173-11-110-132-sfba.hfc.comcastbusiness.net> <80A0822C5E9A4440A5117C2F4CD36A6404136619@DEMUEXC006.nsn-intra.net> <alpine.OSX.2.01.1207311421270.87763@173-11-110-132-sfba.hfc.comcastbusiness.net> <C18E588A-541E-43C7-AF41-F301E3A6AE5B@cs.columbia.edu> <50186301.9030506@levkowetz.com> <alpine.OSX.2.01.1207311615310.88195@173-11-110-132-sfba.hfc.comcastbusiness.net>
In-Reply-To: <alpine.OSX.2.01.1207311615310.88195@173-11-110-132-sfba.hfc.comcastbusiness.net>
X-Enigmail-Version: 1.4
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig21A79B135F5D57E66DB36B73"
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:6d55:bd05:4cb4:b42
X-SA-Exim-Rcpt-To: ole@cisco.com, smb@cs.columbia.edu, mehmet.ersue@nsn.com, rsag@rfc-editor.org, rsoc@iab.org, ietf@ietf.org, hlflanagan@gmail.com, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Re: RFC and I-D Citation Tool
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on grenache.tools.ietf.org)
Cc: The IETF <ietf@ietf.org>, RSOC <rsoc@iab.org>, Heather Flanagan <hlflanagan@gmail.com>, rsag@rfc-editor.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 14:49:46 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig21A79B135F5D57E66DB36B73
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

On 2012-08-01 01:17 Ole Jacobsen said:
>=20
> One feature request that I discussed with Henrik was to either
> "auto-detect" I-D file names and handle them slightly differently
> from RFC numbers (by putting the file name as the final entry)
> OR just having two tools. With the kind of feedback Henrik is
> getting I am sure the tool will be improved/enhanced over time.

I've now set up the tool to use different templates, depending on
whether the document is an RFC or a draft (actually, it's decided
on whether or not I find an RFC number in the metadata I have for
a document).

Let me know if this works for you, or if further tweaks are needed
to provide what is desired.


Best regards,

	Henrik


--------------enig21A79B135F5D57E66DB36B73
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAlAjzfAACgkQeVhrtTJkXCOBUgCgpxrR7rbJo8R+COPVP8Gj8R5X
TD4AoOtXQ2rFHeLOM9d87wyZxcmzsjLV
=fH8b
-----END PGP SIGNATURE-----

--------------enig21A79B135F5D57E66DB36B73--

From hallam@gmail.com  Thu Aug  9 07:52:36 2012
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C22F21F86FD for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 07:52:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.613
X-Spam-Level: 
X-Spam-Status: No, score=-5.613 tagged_above=-999 required=5 tests=[AWL=-2.014, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jSe7TIs-9gp7 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 07:52:35 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 06FA121F86D8 for <ietf@ietf.org>; Thu,  9 Aug 2012 07:52:34 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so938532obb.31 for <ietf@ietf.org>; Thu, 09 Aug 2012 07:52:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yzH0R4qd1aRFOTgIVwZnzgqhelfYD2Kld2bnOUzsYHc=; b=dwrXNv30Z8EhTryaYq5Hr23MgXM9m+UPM6l27qbc4Chmh9FoGM4lfmag8pxJ2wX8Rp 3TcE+koYrCydxOKwY5gk0qR+oQWx/7Ll6pX4TAEJ8lycLXtcuJtHL6GOwU3yqNFewnjd W+l9ygqIcmk0W15Z1EdH2V7aSppPydcDubrsoUdZ63SxfkFiJ4pBTfBmk6M/wzXjyDAT 2+7LDNErodFYoS0nWv5qgvPHNsvuAqIlXKsK2hmHk0diCIUTzo+s7tdQLOVvPh/qN98A KAxHRilQeu00+kQ+L7lb1dwXZjlFYB+rENlVJO1G4Y7b4O7Qq6ctTgqFgmP7YKTgDfAX IM2g==
MIME-Version: 1.0
Received: by 10.182.167.41 with SMTP id zl9mr35924166obb.43.1344523954541; Thu, 09 Aug 2012 07:52:34 -0700 (PDT)
Received: by 10.76.80.10 with HTTP; Thu, 9 Aug 2012 07:52:34 -0700 (PDT)
In-Reply-To: <1938E5FD-57DE-4172-834A-55CA1FDAF29A@burkov.aha.ru>
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu> <CAMm+Lwg2HgO-=9ED4vbmO+Vf9r6bYPcLDgfyMAyPdEPVgRm4LQ@mail.gmail.com> <FB949BEA-5BDB-401A-8A75-E9A9BDAA72A6@ripe.net> <20120803182500.1F9512344DBF@drugs.dv.isc.org> <1938E5FD-57DE-4172-834A-55CA1FDAF29A@burkov.aha.ru>
Date: Thu, 9 Aug 2012 10:52:34 -0400
Message-ID: <CAMm+Lwhw=XUPKgAJaVeXcQ5mG++hNL9PkmAfqOPyVZo9oi=suQ@mail.gmail.com>
Subject: Re: ITU-T Dubai Meeting
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Dmitry Burkov <dburk@burkov.aha.ru>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 14:52:36 -0000

The fact that people plan badly does not mean that all planning must fail.

As Tom Knight pointed out when the IPv4 address size was chosen, there
aren't enough for one for each person living on the planet.

IPv6 has enough addresses to assign a subnet to every grain of sand on
the planet.


Allocating a /16 for national RIRs independent of IANA and the US
government gives other countries the ability to protect their national
interests. The specific concern is that the US government can pass a
law that prevents

Remember that we are trying to build a network that is going to last
for hundreds if not thousands of years. I don't think it likely that
the RIRs or ICANN or even the IETF lasts that long. If it does it will
be in a very different form. What we might think about Steve Crocker
or Vint Cerf or whoever is irrelevant, we do not know who their
successors will be let alone whether we can trust whoever is in charge
in 2040.

I do not believe the national allocations are ever likely to be used
unless the RIRs screw up or get above their post but their existence
provides an exit option in case they ever do.

What I am proposing here is the network equivalent of a crumple zone
on a car body. Cars are designed to break in very specific ways so as
to avoid damage. There is quite a large potential for collateral
damage if an event occurs and people start inventing solutions on the
fly and there are multiple competing solutions fighting it out.


There are privacy implications to this approach but only for battles
that have already been lost. Packets are not routed by the IP address
in any case, they are aggregated by the ASN number and all that is
needed to map those to identify national origin in practice is a
lookup table. [Yes there are networks that span national borders but
not in countries with ugly types of government where this capability
is a concern].




On Fri, Aug 3, 2012 at 2:46 PM, Dmitry Burkov <dburk@burkov.aha.ru> wrote:
> Mark,
> I really enjoyed your professional remarks for the years and your deep and intrinsic mind,
> but it seems that now it is not a time to discuss the issue that ipv4 is scarce resource :)
>
>
> My opinion that IPv6 was done in the worst manner and we should simply recognize that we have no other way to satisfy industry needs in such short time.
>
> Nothing personal - as a lot of my friends spent significant part of their life on it.
>
> Dima
>
> On Aug 3, 2012, at 10:25 PM, Mark Andrews wrote:
>
>>
>> In message <FB949BEA-5BDB-401A-8A75-E9A9BDAA72A6@ripe.net>, Daniel Karrenberg w
>> rites:
>>>
>>> On 02.08.2012, at 22:41, Phillip Hallam-Baker wrote:
>>>
>>>> ... That depends on whether the registry in question is dealing with a
>>>> scarce resource or a plentiful one. Having two registries handing out
>>>> IPv4 addresses at this point would be very very bad. Having more than
>>>> one place you can get an IPv6 from would not worry me at all. ...
>>>
>>> IPv4 addresses used to be regarded as non-scarce not so long ago.
>>
>> I don't know what planet you have been living on but it was clear
>> IPv4 addresses were a scarce resource 2+ decades ago longer than
>> some IETF attendees have been alive.  IPv6 was started because they
>> were a scarce resource that would run out in the foreseeable future.
>>
>> Mark
>> --
>> Mark Andrews, ISC
>> 1 Seymour St., Dundas Valley, NSW 2117, Australia
>> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>



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

From john-ietf@jck.com  Thu Aug  9 07:59:49 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B87B21F8720 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 07:59:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level: 
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mT2Zz3Mf3t+G for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 07:59:48 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 43AEA21F8743 for <ietf@ietf.org>; Thu,  9 Aug 2012 07:59:43 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SzU77-000Ors-U9; Thu, 09 Aug 2012 10:53:29 -0400
Date: Thu, 09 Aug 2012 10:59:27 -0400
From: John C Klensin <john-ietf@jck.com>
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: RFC Errata: when to file, and when not to
Message-ID: <03F0AB7F579E78F38CB37092@JcK-HP8200.jck.com>
In-Reply-To: <4F18A4B6-3D63-4135-A367-F3CAAF4132CF@checkpoint.com>
References: <CALaySJKV96tdXhzfPD1e1Mro_+gp5aDarF7Z06QrA+iQtnHkLw@mail.gmail.com> <501A5656.2050407@it.aoyama.ac.jp> <501BEC0D.1060404@tana.it> <009101cd7476$bb522c20$4001a8c0@gateway.2wire.net> <599B1629-543A-49BC-A0E7-FA2096C538AD@checkpoint.com> <03e701cd749f$73891c40$4001a8c0@gateway.2wire.net> <50229D32.8000605@tana.it> <006701cd7606$17ff48a0$4001a8c0@gateway.2wire.net> <CAKHUCzzsf6veDR+uwxnMw4Koh0Kj7FqoQpsUbENMb_r3v0G89A@mail.gmail.com> <5256BF9BC9AE13013F066C4E@JcK-HP8200.jck.com> <CAKHUCzza0ba9eDsEHF+y_icmeWTB8Y=3vb3zw83dGi+4-uh77Q@mail.gmail.com> <EA2F8447-D700-4E22-85A6-30BAD12DF3E6@checkpoint.com> <E3A4486529AAE3D8CD2A0098@JcK-HP8200.jck.com> <4F18A4B6-3D63-4135-A367-F3CAAF4132CF@checkpoint.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: Alessandro Vesely <vesely@tana.it>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 14:59:49 -0000

--On Thursday, August 09, 2012 17:11 +0300 Yoav Nir
<ynir@checkpoint.com> wrote:

>> And, if I correctly understood it at the time, that is exactly
>> why the RFC Editor opposed the idea of formal errata for
>> years. If there were real, substantive, errors, a replacement
>> RFC should be published as soon as practical.  For anything
>> else, the most that was desirable would be a collected list of
>> comments and suggestions that could be considered if/when the
>> document was revised.
> 
> There are still the spelling mistakes and obvious errors. Take
> for example this one from RFC 5296:
> 
>    The EMSKname is in the username part of the NAI and is
> encoded in    hexadecimal values.  The EMSKname is 64 bits in
> length and so the     username portion takes up 128 octets.
> 
> Encoding 64 bits in hex requires 16 octets, not 128. I think
> anyone implementing this would figure this out, but it is
> substantive. The RFC was being revised anyway, but do you
> think a replacement RFC would need to be published if that
> were not the case?

Personal opinion:  I don't know about "need to be", but
replacing an RFC with an error of that type would be desirable
to avoid any possible misunderstanding, however unlikely.  IMO,
it would also be desirable to have some self-examination in the
community about why that error slipped past IETF Last Call, AD
reviews, and AUTH48).

   john
 





From randy@psg.com  Thu Aug  9 08:06:18 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9A3B21F876D for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 08:06:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.555
X-Spam-Level: 
X-Spam-Status: No, score=-2.555 tagged_above=-999 required=5 tests=[AWL=0.044,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fdgYwiSg6vfj for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 08:06:18 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 20E7221F8687 for <ietf@ietf.org>; Thu,  9 Aug 2012 08:06:18 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SzUJU-0003ZG-TJ; Thu, 09 Aug 2012 15:06:17 +0000
Date: Thu, 09 Aug 2012 11:06:24 -0400
Message-ID: <m2vcgs85qn.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: ITU-T Dubai Meeting
In-Reply-To: <CAMm+Lwhw=XUPKgAJaVeXcQ5mG++hNL9PkmAfqOPyVZo9oi=suQ@mail.gmail.com>
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu> <CAMm+Lwg2HgO-=9ED4vbmO+Vf9r6bYPcLDgfyMAyPdEPVgRm4LQ@mail.gmail.com> <FB949BEA-5BDB-401A-8A75-E9A9BDAA72A6@ripe.net> <20120803182500.1F9512344DBF@drugs.dv.isc.org> <1938E5FD-57DE-4172-834A-55CA1FDAF29A@burkov.aha.ru> <CAMm+Lwhw=XUPKgAJaVeXcQ5mG++hNL9PkmAfqOPyVZo9oi=suQ@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
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 15:06:18 -0000

> Remember that we are trying to build a network that is going to last
> for hundreds if not thousands of years.

some of us do not have such hubris.  

> I don't think it likely that the RIRs or ICANN or even the IETF lasts
> that long. If it does it will be in a very different form.

i suspect the same is true for the internet.  i bet it will be quite
different in much less than a hundred years.

so can we please stick to engineering, not omnipotence.

randy

From dcrocker@bbiw.net  Thu Aug  9 08:07:20 2012
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8023021F8776 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 08:07:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.549
X-Spam-Level: 
X-Spam-Status: No, score=-6.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g9SPR51dxqX6 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 08:07:19 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8043821F86EC for <ietf@ietf.org>; Thu,  9 Aug 2012 08:07:19 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q79F7I7i026438 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 9 Aug 2012 08:07:19 -0700
Message-ID: <5023D21D.7030408@bbiw.net>
Date: Thu, 09 Aug 2012 08:07:09 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Geoff Mulligan <geoff@proto6.com>
Subject: Re: So, where to repeat? (was: Re: management granularity)
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <5022B4B2.8040904@bbiw.net> <79607D9B-40A1-4EE7-9C1A-B93B492D2802@proto6.com>
In-Reply-To: <79607D9B-40A1-4EE7-9C1A-B93B492D2802@proto6.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, 09 Aug 2012 08:07:19 -0700 (PDT)
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, 09 Aug 2012 15:07:20 -0000

offlist.


Geoff,

Frankfurt is a city in Germany.  I believe the IETF has never been there.

Other than those two tidbits about it, I've no idea what is to be 
accomplished by someone's randomly throwing out the names of cities for 
a discussion like this, especially when threads like these always have a 
great deal of trouble staying focused on the /principle/ rather than 
haggling the details.

d/

On 8/8/2012 12:24 PM, Geoff Mulligan wrote:
> Frankfurt?
>
>
>
> On Aug 8, 2012, at 12:49 PM, Dave Crocker <dcrocker@bbiw.net> wrote:
>
>>
>>
>> On 8/8/2012 11:46 AM, Geoff Mulligan wrote:
>>> So then why not consider, London, Paris (not the Concorde Lafayette), Frankfurt, Amsterdam?
>>
>>
>> shockingly, amsterdam can't handle the ietf.  wrong mix of resources. really.
>>
>> paris appears to have broad crime and work-ethic patterns that also are problematic, not just at the concorde.
>>
>> to be clear: i'm speaking for myself.
>>
>> d/
>>
>> --
>> Dave Crocker
>> Brandenburg InternetWorking
>> bbiw.net
>
>

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From dhc@dcrocker.net  Thu Aug  9 08:11:19 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B0D321F8732 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 08:11:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.591
X-Spam-Level: 
X-Spam-Status: No, score=-6.591 tagged_above=-999 required=5 tests=[AWL=0.008,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c8xGjQ34AMaj for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 08:11:14 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id B3C8E21F872D for <ietf@ietf.org>; Thu,  9 Aug 2012 08:11:14 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q79FBDk6026495 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 9 Aug 2012 08:11:14 -0700
Message-ID: <5023D308.3030708@dcrocker.net>
Date: Thu, 09 Aug 2012 08:11:04 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: So, where to repeat?
References: <20120808205220.11419.qmail@joyce.lan>
In-Reply-To: <20120808205220.11419.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 09 Aug 2012 08:11:14 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 15:11:19 -0000

On 8/8/2012 1:52 PM, John Levine wrote:
>> ps. btw, what is it that you think is different about this from the way
>> we /do/ discuss protocol specs?
>
> People discussing venues are less willing to believe that anyone
> else's experience or issues differ from their own.


A common problem in /any/ IETF discussion, technical or otherwise, is 
the tendency of speakers to live within two views:

1.  If it is good enough for me, it must be good enough for everyone

2.  If it is unacceptable to me, it must be unacceptable for everyone.

We are not a very empathetic crowd.

I can't say that I see the 'less' that you assert.

d/


-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From dcrocker@bbiw.net  Thu Aug  9 08:12:58 2012
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A7F821F87B6 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 08:12:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.55
X-Spam-Level: 
X-Spam-Status: No, score=-6.55 tagged_above=-999 required=5 tests=[AWL=0.049,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hzEvdn5RCCaJ for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 08:12:57 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 044E321F87B2 for <ietf@ietf.org>; Thu,  9 Aug 2012 08:12:56 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q79FCq1e026551 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 9 Aug 2012 08:12:53 -0700
Message-ID: <5023D36B.8000805@bbiw.net>
Date: Thu, 09 Aug 2012 08:12:43 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Dave Crocker <dcrocker@bbiw.net>
Subject: Re: So, where to repeat?
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <5022B4B2.8040904@bbiw.net> <79607D9B-40A1-4EE7-9C1A-B93B492D2802@proto6.com> <5023D21D.7030408@bbiw.net>
In-Reply-To: <5023D21D.7030408@bbiw.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]); Thu, 09 Aug 2012 08:12:53 -0700 (PDT)
Cc: Geoff Mulligan <geoff@proto6.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 15:12:58 -0000

On 8/9/2012 8:07 AM, Dave Crocker wrote:
> offlist.


weird.  i really did prune the list.  sorry.

but then, it's not as if my concern applies only to Geoff's note...

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From ynir@checkpoint.com  Thu Aug  9 08:17:46 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7758121F874A for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 08:17:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.395
X-Spam-Level: 
X-Spam-Status: No, score=-10.395 tagged_above=-999 required=5 tests=[AWL=0.204, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Eqh48XQDSJkD for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 08:17:45 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 56AAC21F8738 for <ietf@ietf.org>; Thu,  9 Aug 2012 08:17:45 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id q79FHXg5030347; Thu, 9 Aug 2012 18:17:33 +0300
X-CheckPoint: {5023D19D-0-1B221DC2-4FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Thu, 9 Aug 2012 18:17:33 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Dave Crocker <dcrocker@bbiw.net>
Date: Thu, 9 Aug 2012 18:17:34 +0300
Subject: Re: So, where to repeat? (was: Re: management granularity)
Thread-Topic: So, where to repeat? (was: Re: management granularity)
Thread-Index: Ac12QhlgCKrfnXiUSM2DKkLsx6hyyw==
Message-ID: <6F255DD8-325B-4FA1-AD65-2A75555260FA@checkpoint.com>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us>	<5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <5022B4B2.8040904@bbiw.net> <79607D9B-40A1-4EE7-9C1A-B93B492D2802@proto6.com> <5023D21D.7030408@bbiw.net>
In-Reply-To: <5023D21D.7030408@bbiw.net>
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Geoff Mulligan <geoff@proto6.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 15:17:46 -0000

On Aug 9, 2012, at 6:07 PM, Dave Crocker wrote:

> offlist.

Not so much

> Geoff,
>=20
> Frankfurt is a city in Germany.  I believe the IETF has never been there.

Two more tidbits:
 - It's a huge aviation hub. There are direct flights from everywhere, simi=
lar to CDG, Heathrow, or Schiphol
 - Unlike Paris, London and Amsterdam, it's not a great tourist attraction,=
 so conceivably it would be cheaper.

> Other than those two tidbits about it, I've no idea what is to be=20
> accomplished by someone's randomly throwing out the names of cities for=20
> a discussion like this, especially when threads like these always have a=
=20
> great deal of trouble staying focused on the /principle/ rather than=20
> haggling the details.

The principle would be to go to aviation hubs so as to minimize the collect=
ive pain. Most people from the US going to Prague, would have a connection =
in Frankfurt, so a meeting in Frankfurt would reduce the amount of flights.

Yoav

> On 8/8/2012 12:24 PM, Geoff Mulligan wrote:
>> Frankfurt?
>>=20
>>=20
>>=20
>> On Aug 8, 2012, at 12:49 PM, Dave Crocker <dcrocker@bbiw.net> wrote:
>>=20
>>>=20
>>>=20
>>> On 8/8/2012 11:46 AM, Geoff Mulligan wrote:
>>>> So then why not consider, London, Paris (not the Concorde Lafayette), =
Frankfurt, Amsterdam?
>>>=20
>>>=20
>>> shockingly, amsterdam can't handle the ietf.  wrong mix of resources. r=
eally.
>>>=20
>>> paris appears to have broad crime and work-ethic patterns that also are=
 problematic, not just at the concorde.
>>>=20
>>> to be clear: i'm speaking for myself.
>>>=20
>>> d/
>>>=20
>>> --
>>> Dave Crocker
>>> Brandenburg InternetWorking
>>> bbiw.net
>>=20
>>=20
>=20
> --=20
>  Dave Crocker
>  Brandenburg InternetWorking
>  bbiw.net
>=20
> Scanned by Check Point Total Security Gateway.


From ole@cisco.com  Thu Aug  9 08:20:17 2012
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FD7221F8764 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 08:20:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.574
X-Spam-Level: 
X-Spam-Status: No, score=-110.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nn8hNPEWFL+H for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 08:20:16 -0700 (PDT)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id 4E4D021F8738 for <ietf@ietf.org>; Thu,  9 Aug 2012 08:20:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=468; q=dns/txt; s=iport; t=1344525616; x=1345735216; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=dj64efp6Ny9EEavFJo03vKzJTV6VWMtjovGYFQt3ZF4=; b=kh8CVD6LSc/ZqZzaS8Y1hZPfWjcursOykGkh2/t3zGMycD2FLfogNc73 kVaAA0tPj2Fd9QyOmuMbFENE4rczkMPx2Qrvt3NanGmBR1Qs1+NsSXF2T u34yVlzIe16YxzrIhyhAq4Nr2PgoQWy9EFeOfJdjOgXaKukP0WeYoJ5Lc o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAPXTI1CQ/khM/2dsb2JhbABFuWKBB4IgAQEBAwESAQIlPwULC0ZXBjWHZQabQINIEJ0Wiw+GZAOITpJXiE2BBGKCfw
X-IronPort-AV: E=Sophos;i="4.77,740,1336348800";  d="scan'208";a="7235356"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-4.cisco.com with ESMTP; 09 Aug 2012 15:20:15 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q79FKCUE009436 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Aug 2012 15:20:14 GMT
Date: Thu, 9 Aug 2012 08:20:07 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Geoff Mulligan <geoff@proto6.com>
Subject: Re: So, where to repeat? (was: Re: management granularity)
In-Reply-To: <15ECE2E3-1086-413D-A7AD-C42AA2D4D020@proto6.com>
Message-ID: <alpine.OSX.2.01.1208090818130.31054@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <alpine.OSX.2.01.1208081204190.24762@173-11-110-132-sfba.hfc.comcastbusiness.net> <15ECE2E3-1086-413D-A7AD-C42AA2D4D020@proto6.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: Richard Shockey <richard@shockey.us>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 15:20:17 -0000

On Wed, 8 Aug 2012, Geoff Mulligan wrote:

> So I'm confused...  We're we talking about the possibility of 
> sticking to one European city, one north American city and one Asian 
> city and not picking various cities throughout the world.

Oh, I see. My reading was that we would focus on small number of 
cities in each region, especially since we cannot depend on ONE
being always available for our dates, host and sponsorship 
notwithstanding.

Ole 

From ole@cisco.com  Thu Aug  9 08:23:05 2012
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1245621F86D9 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 08:23:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.578
X-Spam-Level: 
X-Spam-Status: No, score=-110.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3qcW6GJ2EgUi for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 08:23:04 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 90D6821F86D8 for <ietf@ietf.org>; Thu,  9 Aug 2012 08:23:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=546; q=dns/txt; s=iport; t=1344525783; x=1345735383; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=G9nMiQCqOXQrZnYFFTecKEd6sqUIZrADfeKgq3+0y9c=; b=e1D2CzAfYLK29EMQ1Vj4ME0qgYhKnq15fHc4lEfGIUKOo5k+2pZv/sze C+6M+EEYaZHiuukCzQRXKiZCE+86cL3UISCoEdgRUbFBE3fcPBAU5t12b v0wCeL4KtifnJi1xPfenpUEckhUbqYKB7Om3ed3pB1C1A9Hs11+TsNjmJ g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4FAFnVI1CQ/khL/2dsb2JhbABCA4U6tCiBB4IhAQEEEgECJS4REAsOOFcGEyKHa5s+g0gQnRSLKYMpgyEDJgKIJpJXhTGDHIEEYoJ/gT8K
X-IronPort-AV: E=Sophos;i="4.77,740,1336348800";  d="scan'208";a="7230370"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-3.cisco.com with ESMTP; 09 Aug 2012 15:23:02 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q79FMxn8017102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Aug 2012 15:23:01 GMT
Date: Thu, 9 Aug 2012 08:22:58 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: So, where to repeat? (was: Re: management granularity)
In-Reply-To: <6F255DD8-325B-4FA1-AD65-2A75555260FA@checkpoint.com>
Message-ID: <alpine.OSX.2.01.1208090821080.31054@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <5022B4B2.8040904@bbiw.net> <79607D9B-40A1-4EE7-9C1A-B93B492D2802@proto6.com> <5023D21D.7030408@bbiw.net> <6F255DD8-325B-4FA1-AD65-2A75555260FA@checkpoint.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: Geoff Mulligan <geoff@proto6.com>, Dave Crocker <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 15:23:05 -0000

Frankfurt has been considered. Turns out that it is one of the most
expensive cities in all of Europe to have a conference. It is also
geared mostly towards large tradeshows. The Frankfurt Messe is about
the size of your average Olympic Park, just walking from the nearest 
hotel to your venue Hall could take 15 minutes.

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo



From lars@netapp.com  Thu Aug  9 08:53:43 2012
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9F0521F87D1 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 08:53:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.453
X-Spam-Level: 
X-Spam-Status: No, score=-10.453 tagged_above=-999 required=5 tests=[AWL=0.146, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7jSsNWOH2B4U for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 08:53:43 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 4EE7D21F87C5 for <ietf@ietf.org>; Thu,  9 Aug 2012 08:53:43 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.77,740,1336374000";  d="p7s'?scan'208";a="675033696"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 09 Aug 2012 08:53:13 -0700
Received: from vmwexceht05-prd.hq.netapp.com (vmwexceht05-prd.hq.netapp.com [10.106.77.35]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q79FrBRB016239; Thu, 9 Aug 2012 08:53:12 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.211]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.02.0309.002; Thu, 9 Aug 2012 08:52:57 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: RFC and I-D Citation Tool
Thread-Topic: RFC and I-D Citation Tool
Thread-Index: AQHNb0igNg5IgJ3khUOcrqwfWeNK7pdETJSAgAAPh4CAAANygIAAFyKAgAAFeoCADZbeAIAAEeWA
Date: Thu, 9 Aug 2012 15:53:10 +0000
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E906744E87@SACEXCMBX01-PRD.hq.netapp.com>
References: <alpine.OSX.2.01.1207311102470.86865@173-11-110-132-sfba.hfc.comcastbusiness.net> <80A0822C5E9A4440A5117C2F4CD36A6404136619@DEMUEXC006.nsn-intra.net> <alpine.OSX.2.01.1207311421270.87763@173-11-110-132-sfba.hfc.comcastbusiness.net> <C18E588A-541E-43C7-AF41-F301E3A6AE5B@cs.columbia.edu> <50186301.9030506@levkowetz.com> <alpine.OSX.2.01.1207311615310.88195@173-11-110-132-sfba.hfc.comcastbusiness.net> <5023CDE2.5050104@levkowetz.com>
In-Reply-To: <5023CDE2.5050104@levkowetz.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.116]
Content-Type: multipart/signed; boundary="Apple-Mail=_DA6C9EC5-AAFD-4475-A8D0-097B4CB69D38"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: RSOC <rsoc@iab.org>, Ole Jacobsen <ole@cisco.com>, The IETF <ietf@ietf.org>, "<rsag@rfc-editor.org>" <rsag@rfc-editor.org>, Heather Flanagan <hlflanagan@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, 09 Aug 2012 15:53:44 -0000

--Apple-Mail=_DA6C9EC5-AAFD-4475-A8D0-097B4CB69D38
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi,

one suggestion: I-Ds must be cited as "Work in Progress" only. =46rom =
the boilerplate text:

   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."
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

I typically do it like this. Instead of:

Alia Atlas, Cisco Systems, Dave Ward, Juniper Networks, and Thomas =
Nadeau, "Interface to the Routing System Framework," July 2012, =
draft-ward-irs-framework-00.

I use:

Alia Atlas, Cisco Systems, Dave Ward, Juniper Networks, and Thomas =
Nadeau, "Interface to the Routing System Framework," Internet-Draft =
draft-ward-irs-framework-00, Work in Progress, July 2012.

Lars=

--Apple-Mail=_DA6C9EC5-AAFD-4475-A8D0-097B4CB69D38
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMQDCCBUow
ggQyoAMCAQICEFcfSRTG0jNknqb9LV9GuFkwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTEyMTAwMDAwMDBaFw0x
MjEyMDkyMzU5NTlaMIIBDTEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEeMBwGCSqGSIb3DQEJARYPbGFyc0BuZXRhcHAuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokrhJTcXt6J/VEpZOicLoguBlYTjXP9v
Ze4HuuhXnURUS8YouAfgaqA0zYbt5yd6fh4PBMdAaEWr5yJyHuFykXlrCumjUWSpLuqTS2A+pt4q
cZaAQk9iLDN/UVd3SpkUuvWbxXlqzG7/BSqa3VNObBzCmyh+V7aXxri+30CT//DSsNRC4VFy6sn6
dMgSaFenXLwe/FBwY0qTMfICT1PrrX6Sw1S8OfH9rykLlZXbmfkFExxQngp1DJH9xMHeODHGbCv/
ty5gdxMOrLe+vENxFEcy1YQWBZd1kNL4UObugF8A/jE/s+Oa3H1VFH8ghqZTdqGDysVxmtKHuNFx
6jIBSQIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgG
CCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNV
HSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDovL2luZGMx
ZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqG
SIb3DQEBBQUAA4IBAQBA7q6tR92qpd7xo7VBsrOfGCWzoxIVfTc7t0RhB/Oz/+c3lnhYnNScIuKN
JmyZvznmVxqB9BJ72+NkvmdB/hnILSBTRawL2tyLo9PkBtN0nRt4gS6wjpWnD8G83hlJLE7r25jk
7HkRev61dTIXsANFpJKF02C4XSoDfEzNV6MpuEvHvcgHCqMrlwWwfKc7+NoDnE8PBuRzwSXvlD5L
mswCY2iiOsd7ImNO4OzTCxETvKTDu92+FTIbRJJpYjVNv1UF7e3w9Kq65BkZJErUH19beUeQl0Wh
2BJQE6/15rQyCnP0iJ/Nmx2/kI6M0PWunEsI6FMs0MbosreaWGHlQmomMIIG7jCCBdagAwIBAgIQ
cRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQL
EzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYD
VQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y
aXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAo
YykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBD
bGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6ZvgSU6Lb9UB
0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHsEnMhjfXc
MM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO4YM/d/mZ
//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSyriMGZSal
J1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYI
KwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0T
AQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVy
aXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9w
Y2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1h
Z2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28u
dmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRl
TGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHp
MIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWduLCBJ
bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENsYXNzIDEg
UHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+v
OEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlMJBq6WaSH
O3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKvYLMVirOV
nDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDRyxTWcVib
vtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy+kgOZY5J
yNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/wYIxggSL
MIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDgwOTE1NTMxMFowIwYJKoZIhvcNAQkEMRYEFBpQ
ZgNx25kjrz/8x7p95J71h3rgMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBAHOAfKY9
OuZBi0NlAiopFr5G4uvieTvEq+Yfp2ri6HeypNU9N1B1DI9ETm7GCH1THHCpmZk2weZHvjRHogyQ
slOLxLCtW4lIBsySk017DgVBr0QnOLREZHzufpneYrcijRWrhcZD0VIm8wxG/xguM2HpBqfjXRH7
xXoUqMtiDV78G+6KoqlgCHOTB5QBQSdmSuHLArfkrIgaAbsnVx80efbP3iB3bxHtegfUvIQY/oeE
f00xMguynDFdgZ2jtNu7ZfhO8sgRzxqjuoK+rjSCvaDDmMx/NtmuKg0G7B9GReT6uNFKxTWhYArL
Qx/IYqazNTHrmewWGpH+57YcxyURraIAAAAAAAA=

--Apple-Mail=_DA6C9EC5-AAFD-4475-A8D0-097B4CB69D38--

From aservin@lacnic.net  Thu Aug  9 09:11:32 2012
Return-Path: <aservin@lacnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F00BF21F87F1 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 09:11:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bWgDPVYYhRj3 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 09:11:32 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 16BE721F87EA for <ietf@ietf.org>; Thu,  9 Aug 2012 09:11:31 -0700 (PDT)
Received: from [IPv6:2001:13c7:7001:5128:5861:56d1:636b:b89f] (unknown [IPv6:2001:13c7:7001:5128:5861:56d1:636b:b89f]) by mail.lacnic.net.uy (Postfix) with ESMTP id 3B755308444; Thu,  9 Aug 2012 13:11:26 -0300 (UYT)
Subject: Re: So, where to repeat? (was: Re: management granularity)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Arturo Servin <aservin@lacnic.net>
In-Reply-To: <alpine.OSX.2.01.1208090821080.31054@173-11-110-132-sfba.hfc.comcastbusiness.net>
Date: Thu, 9 Aug 2012 13:11:25 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <830EBC63-F1C4-4575-9EBD-D6E29B4F792F@lacnic.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <5022B4B2.8040904@bbiw.net> <79607D9B-40A1-4EE7-9C1A-B93B492D2802@proto6.com> <5023D21D.7030408@bbiw.net> <6F255DD8-325B-4FA1-AD65-2A75555260FA@checkpoint.com> <alpine.OSX.2.01.1208090821080.31054@173-11-110-132-sfba.hfc.comcastbusiness.net>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1278)
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: Geoff Mulligan <geoff@proto6.com>, Ole Jacobsen <ole@cisco.com>, Dave Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 16:11:33 -0000

	Besides where to to repeat, some new places to go that are =
cheaper and closer to me (and possible to others, and perhaps not so bad =
to many).

	Sao Paolo, Mexico City, Miami, Madrid, Cancun, Santiago, Panama, =
San Juan

Regards,
as

On 9 Aug 2012, at 12:22, Ole Jacobsen wrote:

>=20
> Frankfurt has been considered. Turns out that it is one of the most
> expensive cities in all of Europe to have a conference. It is also
> geared mostly towards large tradeshows. The Frankfurt Messe is about
> the size of your average Olympic Park, just walking from the nearest=20=

> hotel to your venue Hall could take 15 minutes.
>=20
> Ole
>=20
>=20
> Ole J. Jacobsen
> Editor and Publisher,  The Internet Protocol Journal
> Cisco Systems
> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> Skype: organdemo
>=20


From hallam@gmail.com  Thu Aug  9 09:17:48 2012
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27E7F21F8772 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 09:17:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.596
X-Spam-Level: 
X-Spam-Status: No, score=-5.596 tagged_above=-999 required=5 tests=[AWL=-1.997, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dPR3Kn4WglUf for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 09:17:47 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6941021F876F for <ietf@ietf.org>; Thu,  9 Aug 2012 09:17:47 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so1041646obb.31 for <ietf@ietf.org>; Thu, 09 Aug 2012 09:17:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3YKPv56hTDQjkP9xfc8RlZ4RI9SDJ5r1h90log/xBdc=; b=xlAXYp6V0015j79tPFGzXI+/VhrEWDmO2xTTSoSjJB4bEVN8KRWXdUOQ1bxvpaCujO MZXk2EavtR9Wt5iVdR1x6g+5Fo/iZuSvxZgA9yeyzhkvkBLZ40WaziGhih4SpG93ZX+o dJkUGipFd+Wx8FAL+TQbDKFyTjThNi85X9C6YL0gtiABYZ6f2wyERadOtY0YtomUzA3B CBv21mJ4VuWMKhvRZP8YurWKFUc+/oF8DWh95myWpM3oxaPPLQPZSRkL1RAGxwFRy82I di7m3mcu1S4D83r2dHhH/+Ib2ZxA+n/hbirkDqYqHuBCK7YRhE9CkKpWYafD0Z+/c3ow bHKg==
MIME-Version: 1.0
Received: by 10.182.86.225 with SMTP id s1mr36427585obz.73.1344529066951; Thu, 09 Aug 2012 09:17:46 -0700 (PDT)
Received: by 10.76.80.10 with HTTP; Thu, 9 Aug 2012 09:17:46 -0700 (PDT)
In-Reply-To: <m2vcgs85qn.wl%randy@psg.com>
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu> <CAMm+Lwg2HgO-=9ED4vbmO+Vf9r6bYPcLDgfyMAyPdEPVgRm4LQ@mail.gmail.com> <FB949BEA-5BDB-401A-8A75-E9A9BDAA72A6@ripe.net> <20120803182500.1F9512344DBF@drugs.dv.isc.org> <1938E5FD-57DE-4172-834A-55CA1FDAF29A@burkov.aha.ru> <CAMm+Lwhw=XUPKgAJaVeXcQ5mG++hNL9PkmAfqOPyVZo9oi=suQ@mail.gmail.com> <m2vcgs85qn.wl%randy@psg.com>
Date: Thu, 9 Aug 2012 12:17:46 -0400
Message-ID: <CAMm+LwjEara+=_BKu7JFsf4Fhbyxr8b6R-hL-QNX0qfXvZLztg@mail.gmail.com>
Subject: Re: ITU-T Dubai Meeting
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Randy Bush <randy@psg.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 16:17:48 -0000

Hubris? it has already lasted 40.

Hubris was proposing that the Clinton-Gore campaign deploy a Web
server in the White House when we had 100 people using it.


I can understand why people might not want to worry about long term
issues but not why you would want to insult people who do think about
them. Particularly in your particular case. You botched DNSSEC
deployment because you were incapable of considering such issues and
if we accept your argument now we will get another botch job.

The fact that outcomes cannot be predicted with 100% certainty does
not mean that all outcomes are equally likely or that we have
absolutely no control over them or that there is no point in
discussing them.


In context the statement was that we should not design infrastructure
on the basis that we can trust the individuals we put in charge of
them now. One of the fundamental reasons ICANN governance is a
disaster is that people who could and should have known better had
assumed we could trust Jon Postel.

More importantly for this issue, the fact that we might trust them
does not mean we should expect others to do so.



On Thu, Aug 9, 2012 at 11:06 AM, Randy Bush <randy@psg.com> wrote:
>> Remember that we are trying to build a network that is going to last
>> for hundreds if not thousands of years.
>
> some of us do not have such hubris.
>
>> I don't think it likely that the RIRs or ICANN or even the IETF lasts
>> that long. If it does it will be in a very different form.
>
> i suspect the same is true for the internet.  i bet it will be quite
> different in much less than a hundred years.
>
> so can we please stick to engineering, not omnipotence.
>
> randy



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

From dhruv.ietf@gmail.com  Thu Aug  9 09:26:43 2012
Return-Path: <dhruv.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 531DA21F866B for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 09:26:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M3s8cTt6zA86 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 09:26:39 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id F25FF21F8659 for <ietf@ietf.org>; Thu,  9 Aug 2012 09:26:38 -0700 (PDT)
Received: by weyu54 with SMTP id u54so487091wey.31 for <ietf@ietf.org>; Thu, 09 Aug 2012 09:26:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:x-google-sender-delegation:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=9bTbgygCKR7svw/4N8ywnGcITfbQ7by98z8D7DRvJ4M=; b=CzUtNlo5RoNJLsGpTIOkLVxni5NjTjsul1zMsQ2Aiv2xoNAsIXoKAHmKQwA0mED6+M hGKUQXZ8jKZef5kWxk7UkTgBqnjEmRDTSWTyyQewdSVWjki3W84ccP8/vs9nW5trgtoj 9izQdfEp/hXzuUE3bKXcE1zWuxFzlptzxtSTSvf2Qc5MNx3MCvjixvJWLEHFkFpucvDJ owAqLTfyoiqfVAErymWfH4BXaUf5eigHBfL+rKoeQbd1igLOc/BNNmgsPwo7zXOgh8I5 fNWK7AbwNT69wJJs0W7Yj/u15AA7xhGEjAEJ0A/7a2Pkjkg3UaAZ2y72oApWmnXzqSq4 I8ZA==
MIME-Version: 1.0
Received: by 10.216.138.220 with SMTP id a70mr12052325wej.170.1344529598016; Thu, 09 Aug 2012 09:26:38 -0700 (PDT)
Sender: dhruvdhody@gmail.com
X-Google-Sender-Delegation: dhruvdhody@gmail.com
Received: by 10.223.182.70 with HTTP; Thu, 9 Aug 2012 09:26:37 -0700 (PDT)
In-Reply-To: <830EBC63-F1C4-4575-9EBD-D6E29B4F792F@lacnic.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <5022B4B2.8040904@bbiw.net> <79607D9B-40A1-4EE7-9C1A-B93B492D2802@proto6.com> <5023D21D.7030408@bbiw.net> <6F255DD8-325B-4FA1-AD65-2A75555260FA@checkpoint.com> <alpine.OSX.2.01.1208090821080.31054@173-11-110-132-sfba.hfc.comcastbusiness.net> <830EBC63-F1C4-4575-9EBD-D6E29B4F792F@lacnic.net>
Date: Thu, 9 Aug 2012 21:56:37 +0530
X-Google-Sender-Auth: CUepHDrTkKu34_zDRupj-PpjFrg
Message-ID: <CAB75xn70KUrPq35ruc-hqq4wbrbY+v3-vEQ5HTdAix3prcKmOQ@mail.gmail.com>
Subject: Re: So, where to repeat? (was: Re: management granularity)
From: Dhruv Dhody <dhruv.ietf@gmail.com>
To: Arturo Servin <aservin@lacnic.net>
Content-Type: multipart/alternative; boundary=0016e6d99b45146d5004c6d7b1f1
Cc: Geoff Mulligan <geoff@proto6.com>, Ole Jacobsen <ole@cisco.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>, Dave Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 16:26:43 -0000

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

Hi,

For new how is Dubai or Barcelona?

Repeat: I would like Prague, Vancouver, Quebec!

Regards,
D

On Thu, Aug 9, 2012 at 9:41 PM, Arturo Servin <aservin@lacnic.net> wrote:

>
>         Besides where to to repeat, some new places to go that are cheaper
> and closer to me (and possible to others, and perhaps not so bad to many).
>
>         Sao Paolo, Mexico City, Miami, Madrid, Cancun, Santiago, Panama,
> San Juan
>
> Regards,
> as
>
> On 9 Aug 2012, at 12:22, Ole Jacobsen wrote:
>
> >
> > Frankfurt has been considered. Turns out that it is one of the most
> > expensive cities in all of Europe to have a conference. It is also
> > geared mostly towards large tradeshows. The Frankfurt Messe is about
> > the size of your average Olympic Park, just walking from the nearest
> > hotel to your venue Hall could take 15 minutes.
> >
> > Ole
> >
> >
> > Ole J. Jacobsen
> > Editor and Publisher,  The Internet Protocol Journal
> > Cisco Systems
> > Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> > E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> > Skype: organdemo
> >
>
>

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

Hi,<div><br></div><div>For new how is Dubai or Barcelona?=A0</div><div><br>=
</div><div>Repeat: I would like Prague, Vancouver, Quebec!=A0</div><div><br=
></div><div>Regards,</div><div>D=A0<br><br><div class=3D"gmail_quote">On Th=
u, Aug 9, 2012 at 9:41 PM, Arturo Servin <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:aservin@lacnic.net" target=3D"_blank">aservin@lacnic.net</a>&gt;</spa=
n> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
=A0 =A0 =A0 =A0 Besides where to to repeat, some new places to go that are =
cheaper and closer to me (and possible to others, and perhaps not so bad to=
 many).<br>
<br>
=A0 =A0 =A0 =A0 Sao Paolo, Mexico City, Miami, Madrid, Cancun, Santiago, Pa=
nama, San Juan<br>
<br>
Regards,<br>
as<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On 9 Aug 2012, at 12:22, Ole Jacobsen wrote:<br>
<br>
&gt;<br>
&gt; Frankfurt has been considered. Turns out that it is one of the most<br=
>
&gt; expensive cities in all of Europe to have a conference. It is also<br>
&gt; geared mostly towards large tradeshows. The Frankfurt Messe is about<b=
r>
&gt; the size of your average Olympic Park, just walking from the nearest<b=
r>
&gt; hotel to your venue Hall could take 15 minutes.<br>
&gt;<br>
&gt; Ole<br>
&gt;<br>
&gt;<br>
&gt; Ole J. Jacobsen<br>
&gt; Editor and Publisher, =A0The Internet Protocol Journal<br>
&gt; Cisco Systems<br>
&gt; Tel: +1 408-527-8972 =A0 Mobile: +1 415-370-4628<br>
&gt; E-mail: <a href=3D"mailto:ole@cisco.com">ole@cisco.com</a> =A0URL: <a =
href=3D"http://www.cisco.com/ipj" target=3D"_blank">http://www.cisco.com/ip=
j</a><br>
&gt; Skype: organdemo<br>
&gt;<br>
<br>
</div></div></blockquote></div><br></div>

--0016e6d99b45146d5004c6d7b1f1--

From dworley@avaya.com  Thu Aug  9 09:45:09 2012
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 57C0921F8688 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 09:45:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.276
X-Spam-Level: 
X-Spam-Status: No, score=-103.276 tagged_above=-999 required=5 tests=[AWL=0.323, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GMmHQR9GcnIz for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 09:45:08 -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 2CB1421F867B for <ietf@ietf.org>; Thu,  9 Aug 2012 09:45:07 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAIzgI1DGmAcF/2dsb2JhbABFuWKBB4IgAQEBAQIBEihEDQEIDQghMREnBBMIEQmHXAMGBplehCOUFw2JTooqZRuFaWADk3UBh1GFDIUFgns
X-IronPort-AV: E=Sophos;i="4.77,741,1336363200"; d="scan'208";a="319119155"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 09 Aug 2012 12:40:03 -0400
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by co300216-co-erhwest-out.avaya.com with ESMTP; 09 Aug 2012 12:40:09 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Thu, 9 Aug 2012 12:45:05 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Date: Thu, 9 Aug 2012 12:45:05 -0400
Subject: RE: ITU-T Dubai Meeting and IPv15
Thread-Topic: ITU-T Dubai Meeting and IPv15
Thread-Index: AQHNdk5Td0YYar+nVUCf27oq/dhOTQ==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0C08@DC-US1MBEX4.global.avaya.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, 09 Aug 2012 16:45:09 -0000

> From: Phillip Hallam-Baker [hallam@gmail.com]
>=20
> As Tom Knight pointed out when the IPv4 address size was chosen, there
> aren't enough for one for each person living on the planet.
>=20
> Remember that we are trying to build a network that is going to last
> for hundreds if not thousands of years.

Technology changes over time, and so the optimal design tradeoffs
change over time.  When IPv4 was designed, memory, processing power,
and transmission capacity were far more expensive than now.  Moore's
Law suggests a factor of 2^15 between 1982 and 2012.  Before that was
the ARPAnet, with 8 bit addresses, which lasted for around 15 years.
Presumably IPv6 will suffice for at least another 30 years.

The real issue regarding longevity is that total network overhauls
should be infrequent enough that their amortized costs are well less
than ongoing operational costs.  Once that has been achieved, the cost
savings of designing a protocol with a longer usable lifetime is
probably not worth the effort of trying to predict the future well
enough to achieve longer lifetime.

Extrapolating a 30-year lifetime for each IP version suggests that in
300 years we will reach the end of the usable life of IPv15 and will have
to allocate more bits to the "version" field at the beginning of
packets.  That'll be a mess...

Dale

From dworley@avaya.com  Thu Aug  9 09:46:38 2012
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 DF78521F8726 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 09:46:38 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yaRqdnBQznzr for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 09:46:38 -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 4665321F8688 for <ietf@ietf.org>; Thu,  9 Aug 2012 09:46:38 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAIzgI1DGmAcF/2dsb2JhbABFuWKBB4IgAQEBAQIBEihECwIBCA0IIRAyJQEBBBMIGodlBp4BnXKRE2ADm0eKEYJ7
X-IronPort-AV: E=Sophos;i="4.77,741,1336363200"; d="scan'208";a="319119440"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 09 Aug 2012 12:41:34 -0400
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by co300216-co-erhwest-out.avaya.com with ESMTP; 09 Aug 2012 12:41:40 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Thu, 9 Aug 2012 12:46:36 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Date: Thu, 9 Aug 2012 12:45:21 -0400
Subject: RE: RFC Errata: when to file, and when not to
Thread-Topic: RFC Errata: when to file, and when not to
Thread-Index: Ac12COJI7LkDVSSjT0SRozIa0grMcgARXs76
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0C09@DC-US1MBEX4.global.avaya.com>
References: <CALaySJKV96tdXhzfPD1e1Mro_+gp5aDarF7Z06QrA+iQtnHkLw@mail.gmail.com> <501A5656.2050407@it.aoyama.ac.jp> <501BEC0D.1060404@tana.it> <009101cd7476$bb522c20$4001a8c0@gateway.2wire.net> <599B1629-543A-49BC-A0E7-FA2096C538AD@checkpoint.com> <03e701cd749f$73891c40$4001a8c0@gateway.2wire.net> <50229D32.8000605@tana.it> <006701cd7606$17ff48a0$4001a8c0@gateway.2wire.net>, <CAKHUCzzsf6veDR+uwxnMw4Koh0Kj7FqoQpsUbENMb_r3v0G89A@mail.gmail.com>
In-Reply-To: <CAKHUCzzsf6veDR+uwxnMw4Koh0Kj7FqoQpsUbENMb_r3v0G89A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 16:46:39 -0000

> From: Dave Cridland [dave@cridland.net]
>=20
> Does anyone other than historians honestly care what the original was?

Does anyone honestly care what last month's version of the source code was?

Dale

From stewe@stewe.org  Thu Aug  9 10:21:00 2012
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E76AE21F86D8 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 10:20:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.634
X-Spam-Level: 
X-Spam-Status: No, score=-3.634 tagged_above=-999 required=5 tests=[AWL=-0.035, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xIkPcrFkjdHq for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 10:20:59 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe003.messaging.microsoft.com [216.32.180.186]) by ietfa.amsl.com (Postfix) with ESMTP id 463AC21F8690 for <ietf@ietf.org>; Thu,  9 Aug 2012 10:20:59 -0700 (PDT)
Received: from mail45-co1-R.bigfish.com (10.243.78.246) by CO1EHSOBE005.bigfish.com (10.243.66.68) with Microsoft SMTP Server id 14.1.225.23; Thu, 9 Aug 2012 17:20:55 +0000
Received: from mail45-co1 (localhost [127.0.0.1])	by mail45-co1-R.bigfish.com (Postfix) with ESMTP id 211649002C7; Thu,  9 Aug 2012 17:20:55 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.236.133; KIP:(null); UIP:(null); IPV:NLI; H:BY2PRD0710HT005.namprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 1
X-BigFish: PS1(zz98dI1432Izz1202h1082kzz8275bhz2fh2a8h668h839h944he5bhf0ah107ah)
Received-SPF: pass (mail45-co1: domain of stewe.org designates 157.56.236.133 as permitted sender) client-ip=157.56.236.133; envelope-from=stewe@stewe.org; helo=BY2PRD0710HT005.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail45-co1 (localhost.localdomain [127.0.0.1]) by mail45-co1 (MessageSwitch) id 1344532853312707_5192; Thu,  9 Aug 2012 17:20:53 +0000 (UTC)
Received: from CO1EHSMHS001.bigfish.com (unknown [10.243.78.250])	by mail45-co1.bigfish.com (Postfix) with ESMTP id 4100E54004D; Thu,  9 Aug 2012 17:20:53 +0000 (UTC)
Received: from BY2PRD0710HT005.namprd07.prod.outlook.com (157.56.236.133) by CO1EHSMHS001.bigfish.com (10.243.66.11) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 9 Aug 2012 17:20:52 +0000
Received: from BY2PRD0710MB354.namprd07.prod.outlook.com ([169.254.10.231]) by BY2PRD0710HT005.namprd07.prod.outlook.com ([10.255.86.40]) with mapi id 14.16.0175.005; Thu, 9 Aug 2012 17:20:52 +0000
From: Stephan Wenger <stewe@stewe.org>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: RFC Errata: when to file, and when not to
Thread-Topic: RFC Errata: when to file, and when not to
Thread-Index: AQHNdgYTijpQ9GLKr0yzz5jOlfP895dRJa0AgACLAYD//5SLgA==
Date: Thu, 9 Aug 2012 17:20:51 +0000
Message-ID: <CC493F71.8A3D2%stewe@stewe.org>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A0C09@DC-US1MBEX4.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.102.5]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4BD45E10A9891549BE32CF44B5F39B5E@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 17:21:00 -0000

Lawyers may, in both cases.
Stephan

On 8.9.2012 09:45 , "Worley, Dale R (Dale)" <dworley@avaya.com> wrote:

>> From: Dave Cridland [dave@cridland.net]
>>=20
>> Does anyone other than historians honestly care what the original was?
>
>Does anyone honestly care what last month's version of the source code
>was?
>
>Dale
>



From mcr@sandelman.ca  Wed Aug  8 12:40:59 2012
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 44E6911E8072 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 12:40:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.855
X-Spam-Level: 
X-Spam-Status: No, score=-1.855 tagged_above=-999 required=5 tests=[AWL=-0.744, BAYES_05=-1.11, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HkBStkNzffs4 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 12:40:58 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 8B87311E80AD for <ietf@ietf.org>; Wed,  8 Aug 2012 12:40:58 -0700 (PDT)
Received: from obiwan.sandelman.ca (unknown [IPv6:2607:f0b0:f:2:3a60:77ff:fe38:e647]) by tuna.sandelman.ca (Postfix) with ESMTP id EFDA52024D for <ietf@ietf.org>; Wed,  8 Aug 2012 15:53:44 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: ietf@ietf.org
Subject: Re: So, where to repeat?
In-Reply-To: <50229CFA.8080408@viagenie.ca>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <01ae01cd7412$abe83e50$03b8baf0$@us> <6BC80C42-9921-4141-B918-4101E873945E@proto6.com> <50229CFA.8080408@viagenie.ca>
X-Mailer: MH-E 8.3; nmh 1.5; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Date: Wed, 08 Aug 2012 15:40:50 -0400
Message-ID: <17661.1344454850@obiwan.sandelman.ca>
X-Mailman-Approved-At: Thu, 09 Aug 2012 10:38:01 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 19:40:59 -0000

>>>>> "Simon" =3D=3D Simon Perreault <simon.perreault@viagenie.ca> writes:
    Simon> Le 2012-08-08 12:34, Geoff Mulligan a =C3=A9crit :
    >> I also would vote to return to Minneapolis again and again even
    >> permanently.

    Simon> Does nobody care about going to new places so that new people
    Simon> are exposed to the IETF and may start getting involved?

    Simon> We've seen this positive effect many times when we went
    Simon> outside our comfort zone...

Simon, it *is* important.
But, we don't have to go to a new place every meeting.

If 1/3 meetings are in North America, I see no reason why we can't
return to places that work.  I think the same mostly applies to Europe
as well.  (We don't have to go back to the *same* place every year,
although there are advantages of that.  So a Paris/Prague would be fine,
but please, not Paris in the summer... nor Orlando on spring break)

Let's innovate for that third meeting, realizing that we do not yet
have a preferred place in Asia, or any place in Africa or South America,
but maybe we should.=20

--=20
]       He who is tired of Weird Al is tired of life!           |  firewall=
s  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net archit=
ect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device dri=
ver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=3Dkzx1ycLXQS=
E>
	               then sign the petition.=20





From geoff@proto6.com  Wed Aug  8 21:51:07 2012
Return-Path: <geoff@proto6.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06BA121E8049 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 21:51:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.82
X-Spam-Level: 
X-Spam-Status: No, score=-100.82 tagged_above=-999 required=5 tests=[AWL=0.384, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZwavMX7PY+1D for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 21:51:06 -0700 (PDT)
Received: from mail.coslabs.com (mail.coslabs.com [199.233.92.34]) by ietfa.amsl.com (Postfix) with ESMTP id 06FEB11E812F for <ietf@ietf.org>; Wed,  8 Aug 2012 21:51:05 -0700 (PDT)
Received: from [192.168.0.36] (unknown [184.99.9.112]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.coslabs.com (Postfix) with ESMTPSA id 2DE855FBC4; Wed,  8 Aug 2012 13:24:13 -0600 (MDT)
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <5022B4B2.8040904@bbiw.net>
In-Reply-To: <5022B4B2.8040904@bbiw.net>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <79607D9B-40A1-4EE7-9C1A-B93B492D2802@proto6.com>
X-Mailer: iPad Mail (9B206)
From: Geoff Mulligan <geoff@proto6.com>
Subject: Re: So, where to repeat? (was: Re: management granularity)
Date: Wed, 8 Aug 2012 13:24:18 -0600
To: Dave Crocker <dcrocker@bbiw.net>
X-Mailman-Approved-At: Thu, 09 Aug 2012 10:38:01 -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: Thu, 09 Aug 2012 04:51:07 -0000

Frankfurt?



On Aug 8, 2012, at 12:49 PM, Dave Crocker <dcrocker@bbiw.net> wrote:

>=20
>=20
> On 8/8/2012 11:46 AM, Geoff Mulligan wrote:
>> So then why not consider, London, Paris (not the Concorde Lafayette), Fra=
nkfurt, Amsterdam?
>=20
>=20
> shockingly, amsterdam can't handle the ietf.  wrong mix of resources. real=
ly.
>=20
> paris appears to have broad crime and work-ethic patterns that also are pr=
oblematic, not just at the concorde.
>=20
> to be clear: i'm speaking for myself.
>=20
> d/
>=20
> --=20
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net

From geoff@proto6.com  Wed Aug  8 22:01:06 2012
Return-Path: <geoff@proto6.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B8CD21E8054 for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 22:01:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.915
X-Spam-Level: 
X-Spam-Status: No, score=-100.915 tagged_above=-999 required=5 tests=[AWL=0.288, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NuAEdNPsbkge for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 22:01:05 -0700 (PDT)
Received: from mail.coslabs.com (mail.coslabs.com [199.233.92.34]) by ietfa.amsl.com (Postfix) with ESMTP id 7F56321E8053 for <ietf@ietf.org>; Wed,  8 Aug 2012 22:01:05 -0700 (PDT)
Received: from [192.168.0.36] (unknown [184.99.9.112]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.coslabs.com (Postfix) with ESMTPSA id 603215FD78; Wed,  8 Aug 2012 13:33:32 -0600 (MDT)
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <alpine.OSX.2.01.1208081204190.24762@173-11-110-132-sfba.hfc.comcastbusiness.net>
In-Reply-To: <alpine.OSX.2.01.1208081204190.24762@173-11-110-132-sfba.hfc.comcastbusiness.net>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <15ECE2E3-1086-413D-A7AD-C42AA2D4D020@proto6.com>
X-Mailer: iPad Mail (9B206)
From: Geoff Mulligan <geoff@proto6.com>
Subject: Re: So, where to repeat? (was: Re: management granularity)
Date: Wed, 8 Aug 2012 13:33:38 -0600
To: Ole Jacobsen <ole@cisco.com>
X-Mailman-Approved-At: Thu, 09 Aug 2012 10:38:01 -0700
Cc: Richard Shockey <richard@shockey.us>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 05:01:06 -0000

So I'm confused...  We're we talking about the possibility of sticking to on=
e European city, one north American city and one Asian city and not picking v=
arious cities throughout the world.

I was just suggesting picking -a- city in Europe that was not multiple hops f=
rom most US hubs.  Prague, while a nice city, isn't one hop and as Dave poin=
ted out this adds costs and time, just as would choosing a US city that is m=
ultiple hops from major European hubs.

I loved Vancouver and would go back there over and over again.  I like Minne=
apolis for convenience and venue and would go there every time.

I liked Prague, both times, but had trouble getting there both times and it d=
id add time and cost.

Geoff



On Aug 8, 2012, at 1:06 PM, Ole Jacobsen <ole@cisco.com> wrote:

>=20
> Geoff,
>=20
> What are you talking about? Of course we are "considering" all of=20
> those places. We are going to London in 2014 for example, we went to=20
> Paris this year. But, like with all popular places, finding venues=20
> available for OUR dates is not easy. Add to that the costs and you=20
> will understand why we don't meet in London or Paris or Frankfurt or=20
> Amsterdam more often.
>=20
> Ole
>=20
>=20
> Ole J. Jacobsen
> Editor and Publisher,  The Internet Protocol Journal
> Cisco Systems
> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> Skype: organdemo
>=20
>=20
> On Wed, 8 Aug 2012, Geoff Mulligan wrote:
>=20
>> So then why not consider, London, Paris (not the Concorde=20
>> Lafayette), Frankfurt, Amsterdam?
>>=20

From geoff@proto6.com  Wed Aug  8 22:26:06 2012
Return-Path: <geoff@proto6.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8142F11E811E for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 22:26:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.973
X-Spam-Level: 
X-Spam-Status: No, score=-100.973 tagged_above=-999 required=5 tests=[AWL=0.230, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Rx+7lkeJyAw for <ietf@ietfa.amsl.com>; Wed,  8 Aug 2012 22:26:06 -0700 (PDT)
Received: from mail.coslabs.com (mail.coslabs.com [199.233.92.34]) by ietfa.amsl.com (Postfix) with ESMTP id 05AB911E80F7 for <ietf@ietf.org>; Wed,  8 Aug 2012 22:26:05 -0700 (PDT)
Received: from [192.168.0.36] (unknown [184.99.9.112]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.coslabs.com (Postfix) with ESMTPSA id 3BBBE5F76C; Wed,  8 Aug 2012 12:46:50 -0600 (MDT)
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net>
In-Reply-To: <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com>
X-Mailer: iPad Mail (9B206)
From: Geoff Mulligan <geoff@proto6.com>
Subject: Re: So, where to repeat? (was: Re: management granularity)
Date: Wed, 8 Aug 2012 12:46:55 -0600
To: Ole Jacobsen <ole@cisco.com>
X-Mailman-Approved-At: Thu, 09 Aug 2012 10:38:01 -0700
Cc: Richard Shockey <richard@shockey.us>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 05:26:06 -0000

So then why not consider, London, Paris (not the Concorde Lafayette), Frankf=
urt, Amsterdam?





On Aug 7, 2012, at 8:55 PM, Ole Jacobsen <ole@cisco.com> wrote:

>=20
> You said about Prague:
>=20
> "...[do] folks who live outside of that region not care about the=20
> additional hop of travel to get to it?"
>=20
> This gets cited often, and I don't really understand why. There are=20
> VERY few European cities that are reachable directly from the US (or=20
> Asia for that matter). Most require transiting some kind of major hub=20
> (London, Paris, Frankfurt, Amsterdam to name a few). There will always=20
> be exceptions, I am sure you can get to Stockholm directly from the US=20
> East Coast, but not from the West Coast. I am sure a very large=20
> percentage of the IETF attendees from the US went through London or=20
> Frankfurt (or a small number of alternatives) to get to Stockholm on=20
> the two occasions when we met there.
>=20
> Since I travel to Norway on a more or less regular basis, I am used to=20
> (and quite happy to) go through Frankfurt or London, it's just a fact=20
> of life especially if you factor in the "preferred carrier" (personal=20
> or corporate). Prague may be an "extra hop," but depending on=20
> schedules you might well get to your destination (hotel) just as=20
> quickly as you would for getting from CDG to central Paris or LHR to=20
> central London.
>=20
> If we restrict European cities to the ones with direct flight=20
> connections from other continents, we're really limiting the choices.=20
> Let's be a little more realistic and consider actual travel "pain"=20
> from the top hubs in Europe, assuming we can't (always) meet in those=20
> places.
>=20
> I do understand that the extra hop does add some cost, which is why
> I always consider trains as a reasonable alternative, albeit not a
> particularly fast one. For example, the cost for a First Class train
> ticket from Frankfurt to Prague was 98 Euros. I am not suggesting
> that this is always going to be a reasonable alternative, and I am
> worried that the mere mention of "train" on this list may result in
> a flame war, but still...
>=20
> Ole
>=20
>=20
>=20
> Ole J. Jacobsen
> Editor and Publisher,  The Internet Protocol Journal
> Cisco Systems
> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> Skype: organdemo
>=20
>=20

From aservin@lacnic.net  Thu Aug  9 10:55:52 2012
Return-Path: <aservin@lacnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 412E821F85AC for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 10:55: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=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 98MCTBOSmG+E for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 10:55:51 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id AF34D21F851E for <ietf@ietf.org>; Thu,  9 Aug 2012 10:55:51 -0700 (PDT)
Received: from [IPv6:2001:13c7:7001:5128:5861:56d1:636b:b89f] (unknown [IPv6:2001:13c7:7001:5128:5861:56d1:636b:b89f]) by mail.lacnic.net.uy (Postfix) with ESMTP id 8DD8C308427; Thu,  9 Aug 2012 14:55:49 -0300 (UYT)
Subject: Re: So, where to repeat?
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/alternative; boundary="Apple-Mail=_7F686773-A295-49A0-83D3-CC1B796006CA"
From: Arturo Servin <aservin@lacnic.net>
In-Reply-To: <17661.1344454850@obiwan.sandelman.ca>
Date: Thu, 9 Aug 2012 14:55:49 -0300
Message-Id: <6F8DA856-014A-45EA-9285-DB716045A5A0@lacnic.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <01ae01cd7412$abe83e50$03b8baf0$@us> <6BC80C42-9921-4141-B918-4101E873945E@proto6.com> <50229CFA.8080408@viagenie.ca> <17661.1344454850@obiwan.sandelman.ca>
To: Michael Richardson <mcr@sandelman.ca>
X-Mailer: Apple Mail (2.1278)
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 17:55:52 -0000

--Apple-Mail=_7F686773-A295-49A0-83D3-CC1B796006CA
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=iso-8859-1


	+1

Regards,
as

On 8 Aug 2012, at 16:40, Michael Richardson wrote:

> Let's innovate for that third meeting, realizing that we do not yet
> have a preferred place in Asia, or any place in Africa or South America,
> but maybe we should. 


--Apple-Mail=_7F686773-A295-49A0-83D3-CC1B796006CA
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><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	=
</span>+1</div><div><br></div><div>Regards,</div><div>as</div><br><div><di=
v>On 8 Aug 2012, at 16:40, Michael Richardson wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Let's =
innovate for that third meeting, realizing that we do not yet<br>have a =
preferred place in Asia, or any place in Africa or South America,<br>but =
maybe we should.<span =
class=3D"Apple-converted-space">&nbsp;</span></span></blockquote></div><br=
></body></html>=

--Apple-Mail=_7F686773-A295-49A0-83D3-CC1B796006CA--

From andy@hxr.us  Thu Aug  9 10:58:26 2012
Return-Path: <andy@hxr.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08E0621F871E for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 10:58:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5ccnaiR757e3 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 10:58:25 -0700 (PDT)
Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 75DC521F86F7 for <ietf@ietf.org>; Thu,  9 Aug 2012 10:58:25 -0700 (PDT)
Received: by qadz3 with SMTP id z3so447760qad.10 for <ietf@ietf.org>; Thu, 09 Aug 2012 10:58:25 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=P7WzLwg4UMOW62r9BVT9CatqmLyJQBP3ZNmVfECb7do=; b=JuZ6cr81I3zYePo+CHGd7Uu6trh+3nX87QyP4mEHPejENKjjMK5WS51OfMi0vEJXHE Ky14742wPeZ78lAMObujRq3FYgpC4TsETQSL0P5IwH20/1umvkhsctsMDQ/zDDuKooTL hssLp8Golfh4Ly8GMki0o7OwsgOa7lnHbdnfN6RtDmMrV/MgiJ8zfHTO8x6ro1LDn/Y/ zsIFqxfIJBvVyLFCzL3h53SiNCq3Jhz0O8Rxjsb79XLx+1pOq2RfZWxOqjvxmgHxiFPS NWYZPNPqpZlW1nW/FUeRpFYAtglHQm0bs7aDdKj0qjS9KotDLO924JP8uIr/hzGZOuYX cxgg==
Received: by 10.229.136.17 with SMTP id p17mr64132qct.86.1344535104998; Thu, 09 Aug 2012 10:58:24 -0700 (PDT)
Received: from [10.71.2.77] ([67.201.120.8]) by mx.google.com with ESMTPS id cg7sm1602501qab.19.2012.08.09.10.58.22 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 09 Aug 2012 10:58:24 -0700 (PDT)
Subject: Re: So, where to repeat?
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=windows-1252
From: Andy Newton <andy@hxr.us>
In-Reply-To: <17661.1344454850@obiwan.sandelman.ca>
Date: Thu, 9 Aug 2012 13:58:24 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <90594EE7-FA36-4C8A-B08D-C1AFAFCB4BF7@hxr.us>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <01ae01cd7412$abe83e50$03b8baf0$@us> <6BC80C42-9921-4141-B918-4101E873945E@proto6.com> <50229CFA.8080408@viagenie.ca> <17661.1344454850@obiwan.sandelman.ca>
To: Michael Richardson <mcr@sandelman.ca>
X-Mailer: Apple Mail (2.1278)
X-Gm-Message-State: ALoCoQkmAo7d17xlobLkrVW7R3dc8yngxBfkm4UPxv7GTRQaXdOIqLkiME5vT4OlcOkRlcFMkVWA
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 17:58:26 -0000

On Aug 8, 2012, at 3:40 PM, Michael Richardson wrote:

>    Simon> Does nobody care about going to new places so that new =
people
>    Simon> are exposed to the IETF and may start getting involved?
>=20
>    Simon> We've seen this positive effect many times when we went
>    Simon> outside our comfort zone...
>=20
> Simon, it *is* important.
> But, we don't have to go to a new place every meeting.
>=20
> If 1/3 meetings are in North America, I see no reason why we can't
> return to places that work.  I think the same mostly applies to Europe
> as well.  (We don't have to go back to the *same* place every year,
> although there are advantages of that.  So a Paris/Prague would be =
fine,
> but please, not Paris in the summer... nor Orlando on spring break)
>=20
> Let's innovate for that third meeting, realizing that we do not yet
> have a preferred place in Asia, or any place in Africa or South =
America,
> but maybe we should.=20

I think this is a fine idea.

And while some see value in going to new places so as to expose new =
people to the IETF, there is one benefit to revisiting venues that has =
not been given. By revisiting well trodden venues, attendees have the =
opportunity to learn what works for them as far as hotel, travel, etc=85 =
and can learn to optimize based on their needs and hopefully that will =
enable them to reduce costs in both money, time, and mental energy.

-andy=

From dcrocker@bbiw.net  Thu Aug  9 11:55:13 2012
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4755C21F872A for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 11:55:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.553
X-Spam-Level: 
X-Spam-Status: No, score=-6.553 tagged_above=-999 required=5 tests=[AWL=0.046,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cNwZdNLx18-e for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 11:55:12 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7CA2A21F8723 for <ietf@ietf.org>; Thu,  9 Aug 2012 11:55:12 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q79ItBkp030563 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 9 Aug 2012 11:55:11 -0700
Message-ID: <50240786.8050903@bbiw.net>
Date: Thu, 09 Aug 2012 11:55:02 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Geoff Mulligan <geoff@proto6.com>
Subject: Re: So, where to repeat?
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us>	<5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <5022B4B2.8040904@bbiw.net> <79607D9B-40A1-4EE7-9C1A-B93B492D2802@proto6.com> <5023D21D.7030408@bbiw.net> <6F255DD8-325B-4FA1-AD65-2A75555260FA@checkpoint.com> <50240374.50608@proto6.com>
In-Reply-To: <50240374.50608@proto6.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, 09 Aug 2012 11:55:12 -0700 (PDT)
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, 09 Aug 2012 18:55:13 -0000

On 8/9/2012 11:37 AM, Geoff Mulligan wrote:
>>> Frankfurt is a city in Germany.  I believe the IETF has never been
...
> I've found it relatively inexpensive, clean and very easy to get to.

Ole's comment was reflecting secretariat and IAOC research.

Individual experience can be very misleading here.  Sometimes, yes, it 
can point to approaches that haven't been considered.  But the 
'sometimes' is meant as a polite way of saying 'almost never'.

As someone who has challenged the IETF's venue selection process 
vigorously for 20 years, I am forced to admit that any possible problems 
in the process seem to be strategic, not tactical.  I haven't seen any 
evidence that the current process obtains distorted data or makes silly 
decisions in the /details/ of researching or arranging a given city.

Anyone thinking otherwise needs to employ the full set of requirements 
for an IETF meeting, not merely a stray, isolated item, such as 
discounted hotel price.


>>> Other than those two tidbits about it, I've no idea what is to be
>>> accomplished by someone's randomly throwing out the names of cities for
>>> a discussion like this, especially when threads like these always have a
>>> great deal of trouble staying focused on the /principle/ rather than
>>> haggling the details.
>> The principle would be to go to aviation hubs so as to minimize the
>> collective pain. Most people from the US going to Prague, would have a
>> connection in Frankfurt, so a meeting in Frankfurt would reduce the
>> amount of flights.
> This is why I threw out a "not so random" city name - Frankfurt.

Indeed, random was the wrong word.  That word is often used incorrectly. 
  The correct word is "arbitrary".

It is frankly entirely arbitrary to suggest a particular city, in terms 
of the a directed discussion about the /approach/ of choosing cities.

It presumes that the existing processes haven't researched most choices 
for Europe, Asia, or North America.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From rja.lists@gmail.com  Thu Aug  9 12:48:35 2012
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 5A27821F8748 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 12:48:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.333
X-Spam-Level: 
X-Spam-Status: No, score=-3.333 tagged_above=-999 required=5 tests=[AWL=0.266,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bSX4o7lVShBJ for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 12:48:34 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 65B5421F8740 for <ietf@ietf.org>; Thu,  9 Aug 2012 12:48:34 -0700 (PDT)
Received: by qcac10 with SMTP id c10so615886qca.31 for <ietf@ietf.org>; Thu, 09 Aug 2012 12:48:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=7b/DFZ80ctUCRvEjdF9FYtZOpBo1+y0UVCf0S4xqctc=; b=McV6rdhQI7Ss9+weGNlwv31wPP1JL6DJQk8AywQ0ujz60JDEPxncdLW6C9GmGDFdvB F52hmWlQuWO5iHLAOqw0bnCYLu0BntYmJfSYuG7UDBlcMknCTBESqzIFP3oboO5bBVrO uhp+WpwDpBIo7ZeFy8Ustoo7NFSu3gW/GFANkmkONCW1sXv+XOAmeYLdGNOIx+xtkA0H KbfSfoB5OtLqM0HMYqibggUmbHF3cb7t4xBm9gtIcRUweBNSUsBz35bP5gFEOtuZYpc6 VP32flZFBgMq+XeJp3lpKt0q4k2NVk8q6fSTFe2gjVfqxmVqsqBjpbIzdO8Rw7B+XXHf qVOw==
Received: by 10.224.32.205 with SMTP id e13mr4717613qad.69.1344541713842; Thu, 09 Aug 2012 12:48:33 -0700 (PDT)
Received: from [10.30.20.13] (pool-74-110-100-136.nrflva.fios.verizon.net. [74.110.100.136]) by mx.google.com with ESMTPS id cg7sm1825078qab.19.2012.08.09.12.48.32 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 09 Aug 2012 12:48:33 -0700 (PDT)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: RE: So, where to repeat?
Date: Thu, 9 Aug 2012 15:48:30 -0400
Message-Id: <A7315D15-50CD-403B-B340-C0F3A8D02B1F@gmail.com>
To: ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 19:48:35 -0000

I haven't been at any IETF recently, but from my previous
experience, I agree with several commenters about these
cities:

* MINNEAPOLIS consistently works well for IETF meetings.


* VANCOUVER consistently works well for IETF meetings.


* DUBLIN has good air transport links, and would have 
  rated MUCH higher in many folks' views if only the 
  meeting either had been downtown (or in another part 
  of town with a range of hotel and restaurant options 
  to choose from). 

  I very much hope the IAOC will look into Dublin again, 
  but a meeting downtown or otherwise with a range of
  hotel and restaurant options.


* WASHINGTON DC worked well for several meetings in the
  1990s and would be worth re-examining.  It has very
  good air transport links, and the Metro Rail (subway)
  is being extended out west to Dulles International
  Airport.  [MetroRail to Reston/Wiehle Ave opens in 2013; 
  extending the last few miles from there to Dulles Airport
  is expected circa 2016.]


I also agree with several commenters about these 
more general meeting aspects:

* When I attend an IETF, I'm working, not playing tourist.  
  So I'm quite happy to meet someplace cold in winter or 
  someplace wet during rainy season -- provided one can 
  get around in a reasonable way.

* Tourist-oriented venues often ring alarm bells in the
  management approval processes for many organisations.
  As examples, meetings in Hawaii or Las Vegas (any time)
  likely will raise more management-approval questions 
  than meeting in Minneapolis during the local winter.

* Locations convenient (using public transport) to a major
  airline hub are preferable, given our global scope.


Separately, despite the best efforts of the IAOC (and 
their predecessors), it has been disappointing that most 
A/P region locations have been relatively expensive.


Yours,

Ran


From john-ietf@jck.com  Thu Aug  9 13:06:06 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D29A21F872E for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 13:06:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.585
X-Spam-Level: 
X-Spam-Status: No, score=-102.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jxna6b7yXkaX for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 13:06:05 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8CBDB21F869D for <ietf@ietf.org>; Thu,  9 Aug 2012 13:06:05 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SzYtc-000PmP-F9; Thu, 09 Aug 2012 15:59:52 -0400
Date: Thu, 09 Aug 2012 16:05:50 -0400
From: John C Klensin <john-ietf@jck.com>
To: Dave Crocker <dcrocker@bbiw.net>, Geoff Mulligan <geoff@proto6.com>
Subject: Re: So, where to repeat?
Message-ID: <FEC981B8DEB702AC01C7AADF@JcK-HP8200.jck.com>
In-Reply-To: <50240786.8050903@bbiw.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <5022B4B2.8040904@bbiw.net> <79607D9B-40A1-4EE7-9C1A-B93B492D2802@proto6.com> <5023D21D.7030408@bbiw.net> <6F255DD8-325B-4FA1-AD65-2A75555260FA@checkpoint.com> <50240374.50608@proto6.com> <50240786.8050903@bbiw.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 20:06:06 -0000

--On Thursday, August 09, 2012 11:55 -0700 Dave Crocker
<dcrocker@bbiw.net> wrote:

>> This is why I threw out a "not so random" city name -
>> Frankfurt.
>=20
> Indeed, random was the wrong word.  That word is often used
> incorrectly.   The correct word is "arbitrary".
>=20
> It is frankly entirely arbitrary to suggest a particular city,
> in terms of the a directed discussion about the /approach/ of
> choosing cities.
>=20
> It presumes that the existing processes haven't researched
> most choices for Europe, Asia, or North America.

Dave,

Without suggesting that Frankfurt has not been carefully
researched (I gather it has and have some personal experience
with meeting arrangements, not just individual visits that leads
me to agree with the conclusion, whether you approve of such
personal experiences or not), I don't think you can dismiss it
as either "random" or even "arbitrary". =20

One of the major criteria that has often been suggested --I
think even by you-- is "major airline hub".   As far as I know,
there are four such hubs in Europe: London (where we have met
and are planning to meet again), Paris (where we have met),
Amsterdam (where we have met), and Frankfurt.  I would consider
Copenhagen, Munich (where we have met), and a few other places
as secondary hubs; YMMD. =20

I think its being the only place on that first list where we
have not met makes "why not Frankfurt" an entirely reasonable
and actually highly focused and predictable question.  If he had
said "why not K=C3=B6ln-Bonn" or "why not Nice" or any of dozens =
of
other smaller, non-hub airports, "arbitrary" would have been in
order.  But "Frankfurt" is no more arbitrary than Chicago,
Dallas, or New York -- there may be perfectly good reasons to
avoid all three (although we have met in Chicago and Dallas),
but it seems to me that asking about _any_ airline hub city that
significant can certainly not be dismissed as "arbitrary".

    john





From mehmet.ersue@nsn.com  Thu Aug  9 13:20:35 2012
Return-Path: <mehmet.ersue@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 69AE521F8593 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 13:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.577
X-Spam-Level: 
X-Spam-Status: No, score=-106.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k2hNNGgx5K7W for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 13:20:34 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 54B8A21F842E for <ietf@ietf.org>; Thu,  9 Aug 2012 13:20:34 -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 q79KKOqP006133 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 9 Aug 2012 22:20:24 +0200
Received: from DEMUEXC047.nsn-intra.net ([10.159.32.93]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q79KKL9H014709; Thu, 9 Aug 2012 22:20:23 +0200
Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by DEMUEXC047.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 9 Aug 2012 22:20:15 +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: So, where to repeat? (was: Re: management granularity)
Date: Thu, 9 Aug 2012 22:20:14 +0200
Message-ID: <80A0822C5E9A4440A5117C2F4CD36A64041CD5E4@DEMUEXC006.nsn-intra.net>
In-Reply-To: <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: So, where to repeat? (was: Re: management granularity)
Thread-Index: Ac12VgUMwIXfPfLIQUmsmeJS8rt9KQAFD8zg
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com><502169E9.9020009@dcrocker.net><AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk><EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk><39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com><01af01cd74f5$217e5770$647b0650$@us><5021CDDE.8060207@dcrocker.net><alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com>
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: "ext Geoff Mulligan" <geoff@proto6.com>, "Ole Jacobsen" <ole@cisco.com>
X-OriginalArrivalTime: 09 Aug 2012 20:20:15.0629 (UTC) FILETIME=[6330A3D0:01CD766C]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 3073
X-purgate-ID: 151667::1344543624-00006F5F-C7D6352E/0-0/0-0
Cc: ietf@ietf.org, dcrocker@bbiw.net, Richard Shockey <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: Thu, 09 Aug 2012 20:20:35 -0000

Why not consider Istanbul? It's another nice harbor city.

Has a series of world class hotels like Grand Hyatt, Hilton,
InterContinental, Radisson Blu but also less expensive hotels, close to
each other.

Cheers,=20
Mehmet=20

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
Of ext Geoff
> Mulligan
> Sent: Wednesday, August 08, 2012 8:47 PM
> To: Ole Jacobsen
> Cc: Richard Shockey; dcrocker@bbiw.net; ietf@ietf.org
> Subject: Re: So, where to repeat? (was: Re: management granularity)
>=20
> So then why not consider, London, Paris (not the Concorde Lafayette),
Frankfurt,
> Amsterdam?
>=20
>=20
>=20
>=20
>=20
> On Aug 7, 2012, at 8:55 PM, Ole Jacobsen <ole@cisco.com> wrote:
>=20
> >
> > You said about Prague:
> >
> > "...[do] folks who live outside of that region not care about the
> > additional hop of travel to get to it?"
> >
> > This gets cited often, and I don't really understand why. There are
> > VERY few European cities that are reachable directly from the US (or
> > Asia for that matter). Most require transiting some kind of major
hub
> > (London, Paris, Frankfurt, Amsterdam to name a few). There will
always
> > be exceptions, I am sure you can get to Stockholm directly from the
US
> > East Coast, but not from the West Coast. I am sure a very large
> > percentage of the IETF attendees from the US went through London or
> > Frankfurt (or a small number of alternatives) to get to Stockholm on
> > the two occasions when we met there.
> >
> > Since I travel to Norway on a more or less regular basis, I am used
to
> > (and quite happy to) go through Frankfurt or London, it's just a
fact
> > of life especially if you factor in the "preferred carrier"
(personal
> > or corporate). Prague may be an "extra hop," but depending on
> > schedules you might well get to your destination (hotel) just as
> > quickly as you would for getting from CDG to central Paris or LHR to
> > central London.
> >
> > If we restrict European cities to the ones with direct flight
> > connections from other continents, we're really limiting the
choices.
> > Let's be a little more realistic and consider actual travel "pain"
> > from the top hubs in Europe, assuming we can't (always) meet in
those
> > places.
> >
> > I do understand that the extra hop does add some cost, which is why
> > I always consider trains as a reasonable alternative, albeit not a
> > particularly fast one. For example, the cost for a First Class train
> > ticket from Frankfurt to Prague was 98 Euros. I am not suggesting
> > that this is always going to be a reasonable alternative, and I am
> > worried that the mere mention of "train" on this list may result in
> > a flame war, but still...
> >
> > Ole
> >
> >
> >
> > Ole J. Jacobsen
> > Editor and Publisher,  The Internet Protocol Journal
> > Cisco Systems
> > Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> > E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> > Skype: organdemo
> >
> >

From nurit.sprecher@nsn.com  Thu Aug  9 13:24:20 2012
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 C862721F86F9 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 13:24:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level: 
X-Spam-Status: No, score=-6.454 tagged_above=-999 required=5 tests=[AWL=0.145,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OuigqymqKSSo for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 13:24:20 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id B3B2F21F86EB for <ietf@ietf.org>; Thu,  9 Aug 2012 13:24:19 -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 q79KO94E001212 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 9 Aug 2012 22:24:10 +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 q79KO9hh028680; Thu, 9 Aug 2012 22:24:09 +0200
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by DEMUEXC047.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 9 Aug 2012 22:22:59 +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: So, where to repeat? (was: Re: management granularity)
Date: Thu, 9 Aug 2012 22:22:57 +0200
Message-ID: <E4873516F3FC7547BCFE792C7D94039C0236B662@DEMUEXC013.nsn-intra.net>
In-Reply-To: <80A0822C5E9A4440A5117C2F4CD36A64041CD5E4@DEMUEXC006.nsn-intra.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: So, where to repeat? (was: Re: management granularity)
Thread-Index: Ac12VgUMwIXfPfLIQUmsmeJS8rt9KQAFD8zgAACWVbA=
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com><502169E9.9020009@dcrocker.net><AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk><EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk><39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com><01af01cd74f5$217e5770$647b0650$@us><5021CDDE.8060207@dcrocker.net><alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net><B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <80A0822C5E9A4440A5117C2F4CD36A64041CD5E4@DEMUEXC006.nsn-intra.net>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>, "ext Geoff Mulligan" <geoff@proto6.com>, "Ole Jacobsen" <ole@cisco.com>
X-OriginalArrivalTime: 09 Aug 2012 20:22:59.0064 (UTC) FILETIME=[C49AD780:01CD766C]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 3535
X-purgate-ID: 151667::1344543850-00003184-F3BB5721/0-0/0-0
Cc: Richard Shockey <richard@shockey.us>, ietf@ietf.org, dcrocker@bbiw.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 20:24:21 -0000

Istanbul, Dubai, and similar places will not allow all of us in the
community to participate in the meetings....=20


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Ersue, Mehmet (NSN - DE/Munich)
Sent: Thursday, August 09, 2012 11:20 PM
To: ext Geoff Mulligan; Ole Jacobsen
Cc: ietf@ietf.org; dcrocker@bbiw.net; Richard Shockey
Subject: RE: So, where to repeat? (was: Re: management granularity)

Why not consider Istanbul? It's another nice harbor city.

Has a series of world class hotels like Grand Hyatt, Hilton,
InterContinental, Radisson Blu but also less expensive hotels, close to
each other.

Cheers,=20
Mehmet=20

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
Of ext Geoff
> Mulligan
> Sent: Wednesday, August 08, 2012 8:47 PM
> To: Ole Jacobsen
> Cc: Richard Shockey; dcrocker@bbiw.net; ietf@ietf.org
> Subject: Re: So, where to repeat? (was: Re: management granularity)
>=20
> So then why not consider, London, Paris (not the Concorde Lafayette),
Frankfurt,
> Amsterdam?
>=20
>=20
>=20
>=20
>=20
> On Aug 7, 2012, at 8:55 PM, Ole Jacobsen <ole@cisco.com> wrote:
>=20
> >
> > You said about Prague:
> >
> > "...[do] folks who live outside of that region not care about the
> > additional hop of travel to get to it?"
> >
> > This gets cited often, and I don't really understand why. There are
> > VERY few European cities that are reachable directly from the US (or
> > Asia for that matter). Most require transiting some kind of major
hub
> > (London, Paris, Frankfurt, Amsterdam to name a few). There will
always
> > be exceptions, I am sure you can get to Stockholm directly from the
US
> > East Coast, but not from the West Coast. I am sure a very large
> > percentage of the IETF attendees from the US went through London or
> > Frankfurt (or a small number of alternatives) to get to Stockholm on
> > the two occasions when we met there.
> >
> > Since I travel to Norway on a more or less regular basis, I am used
to
> > (and quite happy to) go through Frankfurt or London, it's just a
fact
> > of life especially if you factor in the "preferred carrier"
(personal
> > or corporate). Prague may be an "extra hop," but depending on
> > schedules you might well get to your destination (hotel) just as
> > quickly as you would for getting from CDG to central Paris or LHR to
> > central London.
> >
> > If we restrict European cities to the ones with direct flight
> > connections from other continents, we're really limiting the
choices.
> > Let's be a little more realistic and consider actual travel "pain"
> > from the top hubs in Europe, assuming we can't (always) meet in
those
> > places.
> >
> > I do understand that the extra hop does add some cost, which is why
> > I always consider trains as a reasonable alternative, albeit not a
> > particularly fast one. For example, the cost for a First Class train
> > ticket from Frankfurt to Prague was 98 Euros. I am not suggesting
> > that this is always going to be a reasonable alternative, and I am
> > worried that the mere mention of "train" on this list may result in
> > a flame war, but still...
> >
> > Ole
> >
> >
> >
> > Ole J. Jacobsen
> > Editor and Publisher,  The Internet Protocol Journal
> > Cisco Systems
> > Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> > E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> > Skype: organdemo
> >
> >

From john-ietf@jck.com  Thu Aug  9 13:42:56 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1F7021F8617 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 13:42:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.585
X-Spam-Level: 
X-Spam-Status: No, score=-102.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zGfxVDVOQnV1 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 13:42:56 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id EE50F21F8611 for <ietf@ietf.org>; Thu,  9 Aug 2012 13:42:55 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SzZTC-000Ps2-38; Thu, 09 Aug 2012 16:36:38 -0400
Date: Thu, 09 Aug 2012 16:42:36 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>, "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>, ext Geoff Mulligan <geoff@proto6.com>, Ole Jacobsen <ole@cisco.com>
Subject: RE: So, where to repeat? (was: Re: management granularity)
Message-ID: <359C3335DECB3764A8BC37B3@JcK-HP8200.jck.com>
In-Reply-To: <E4873516F3FC7547BCFE792C7D94039C0236B662@DEMUEXC013.nsn-intra.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <80A0822C5E9A4440A5117C2F4CD36A64041CD5E4@DEMUEXC006.nsn-intra.net> <E4873516F3FC7547BCFE792C7D94039C0236B662@DEMUEXC013.nsn-intra.ne t>
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: dcrocker@bbiw.net, ietf@ietf.org, Richard Shockey <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: Thu, 09 Aug 2012 20:42:56 -0000

Let me say that a different way.  We sometimes have to tolerate
countries, like the US, who a fussy about visas or immigration
procedures for people coming from specific other countries.  I
wish we didn't.  But, as soon as a country says "if you have a
passport from X, you aren't getting in, don't even bother to
apply for a visa", they should be off our list of possibilities.

   john


--On Thursday, August 09, 2012 22:22 +0200 "Sprecher, Nurit (NSN
- IL/Hod HaSharon)" <nurit.sprecher@nsn.com> wrote:

> Istanbul, Dubai, and similar places will not allow all of us
> in the community to participate in the meetings.... 
> 
> 
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On
> Behalf Of Ersue, Mehmet (NSN - DE/Munich)
> Sent: Thursday, August 09, 2012 11:20 PM
> To: ext Geoff Mulligan; Ole Jacobsen
> Cc: ietf@ietf.org; dcrocker@bbiw.net; Richard Shockey
> Subject: RE: So, where to repeat? (was: Re: management
> granularity)
> 
> Why not consider Istanbul? It's another nice harbor city.
> 
> Has a series of world class hotels like Grand Hyatt, Hilton,
> InterContinental, Radisson Blu but also less expensive hotels,
> close to each other.





From ole@cisco.com  Thu Aug  9 13:47:47 2012
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51C4621F86F3 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 13:47:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18equAit9vG8 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 13:47:46 -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 A1ACE21F86D8 for <ietf@ietf.org>; Thu,  9 Aug 2012 13:47:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=1620; q=dns/txt; s=iport; t=1344545266; x=1345754866; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Nrqq+/cOfwKumFNmszzTO2vBe5RJLLluWryR7VJRMJY=; b=Dn4EcZwasUt48e5VB2QVoG+VrqOKslO+dmY4gaJrtugGJ7O4IGn6uaCY W6PKSGkRA+8X404h41tinU/hqmwC7/7uNcbcwafv8R0+b09fW0jt+IrbK OV4FJO3vhLoxB+3jUKAgU6h/xnz+8zpbDlH2wxvl89c3kCgMIbJZMznML g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAIzgI1CtJXHA/2dsb2JhbABFuWKBB4IgAQEBAwESASc7BAUHBAIBCBEEAQEBHgkHMhQJCAIEDgUUDodlBpsGjxaRV4sPhgRgA5VJgRSJeYMcgWaCXw
X-IronPort-AV: E=Sophos;i="4.77,742,1336348800"; d="scan'208";a="110097833"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-5.cisco.com with ESMTP; 09 Aug 2012 20:47:46 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id q79Kljb7030754 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 9 Aug 2012 20:47:45 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.98]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.02.0298.004; Thu, 9 Aug 2012 15:47:44 -0500
From: "Ole Jacobsen (ole)" <ole@cisco.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: So, where to repeat? (was: Re: management granularity)
Thread-Topic: So, where to repeat? (was: Re: management granularity)
Thread-Index: AQHNdm+CPY9STExk+0qjcr7YA02QG5dR85T4
Date: Thu, 9 Aug 2012 20:47:44 +0000
Message-ID: <629A968E-8104-4E6D-B393-CEBEDEC5FFDD@cisco.com>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <80A0822C5E9A4440A5117C2F4CD36A64041CD5E4@DEMUEXC006.nsn-intra.net> <E4873516F3FC7547BCFE792C7D94039C0236B662@DEMUEXC013.nsn-intra.ne t>,<359C3335DECB3764A8BC37B3@JcK-HP8200.jck.com>
In-Reply-To: <359C3335DECB3764A8BC37B3@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19098.001
x-tm-as-result: No--40.083400-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>, Richard Shockey <richard@shockey.us>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, ext Geoff Mulligan <geoff@proto6.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 20:47:47 -0000

Yes, and sadly that rules out really good venues such as Kuala Lumpur, quit=
e possibly the least expensive (hotel wise) suitable location in Asia.

Ole J. Jacobsen
Editor & Publisher
http://cisco.com/ipj

Sent from my iPhone

On 9 Aug 2012, at 13:42, "John C Klensin" <john-ietf@jck.com> wrote:

> Let me say that a different way.  We sometimes have to tolerate
> countries, like the US, who a fussy about visas or immigration
> procedures for people coming from specific other countries.  I
> wish we didn't.  But, as soon as a country says "if you have a
> passport from X, you aren't getting in, don't even bother to
> apply for a visa", they should be off our list of possibilities.
>=20
>   john
>=20
>=20
> --On Thursday, August 09, 2012 22:22 +0200 "Sprecher, Nurit (NSN
> - IL/Hod HaSharon)" <nurit.sprecher@nsn.com> wrote:
>=20
>> Istanbul, Dubai, and similar places will not allow all of us
>> in the community to participate in the meetings....=20
>>=20
>>=20
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On
>> Behalf Of Ersue, Mehmet (NSN - DE/Munich)
>> Sent: Thursday, August 09, 2012 11:20 PM
>> To: ext Geoff Mulligan; Ole Jacobsen
>> Cc: ietf@ietf.org; dcrocker@bbiw.net; Richard Shockey
>> Subject: RE: So, where to repeat? (was: Re: management
>> granularity)
>>=20
>> Why not consider Istanbul? It's another nice harbor city.
>>=20
>> Has a series of world class hotels like Grand Hyatt, Hilton,
>> InterContinental, Radisson Blu but also less expensive hotels,
>> close to each other.
>=20
>=20
>=20
>=20

From stpeter@stpeter.im  Thu Aug  9 13:50:22 2012
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 907D321F8764 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 13:50:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.763
X-Spam-Level: 
X-Spam-Status: No, score=-102.763 tagged_above=-999 required=5 tests=[AWL=-0.164, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GrokE5EwR5Zf for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 13:50:22 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id ED7C821F86FC for <ietf@ietf.org>; Thu,  9 Aug 2012 13:50:21 -0700 (PDT)
Received: from [192.168.0.4] (unknown [67.177.192.224]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 409F0404EA; Thu,  9 Aug 2012 14:50:28 -0600 (MDT)
Message-ID: <50242289.2040108@stpeter.im>
Date: Thu, 09 Aug 2012 14:50:17 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: So, where to repeat? (was: Re: management granularity)
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <80A0822C5E9A4440A5117C2F4CD36A64041CD5E4@DEMUEXC006.nsn-intra.net> <E4873516F3FC7547BCFE792C7D94039C0236B662@DEMUEXC013.nsn-intra.ne t> <359C3335DECB3764A8BC37B3@JcK-HP8200.jck.com>
In-Reply-To: <359C3335DECB3764A8BC37B3@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Ole Jacobsen <ole@cisco.com>, ietf@ietf.org, Richard Shockey <richard@shockey.us>, dcrocker@bbiw.net, ext Geoff Mulligan <geoff@proto6.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 20:50:22 -0000

On 8/9/12 2:42 PM, John C Klensin wrote:
> Let me say that a different way.  We sometimes have to tolerate
> countries, like the US, who a fussy about visas or immigration
> procedures for people coming from specific other countries.  I
> wish we didn't.  But, as soon as a country says "if you have a
> passport from X, you aren't getting in, don't even bother to
> apply for a visa", they should be off our list of possibilities.

Agreed.

Dare I say that we need a requirements document? ;-)

Peter

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



From dhc@dcrocker.net  Thu Aug  9 13:57:10 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9155721F86EF for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 13:57:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.592
X-Spam-Level: 
X-Spam-Status: No, score=-6.592 tagged_above=-999 required=5 tests=[AWL=0.007,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GjkA251YbGLE for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 13:57:10 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id E6AB421F8621 for <ietf@ietf.org>; Thu,  9 Aug 2012 13:57:09 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q79Kv7uF000379 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 9 Aug 2012 13:57:07 -0700
Message-ID: <5024241A.8040804@dcrocker.net>
Date: Thu, 09 Aug 2012 13:56:58 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: "Ole Jacobsen (ole)" <ole@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: So, where to repeat? (was: Re: management granularity)
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <80A0822C5E9A4440A5117C2F4CD36A64041CD5E4@DEMUEXC006.nsn-intra.net> <E4873516F3FC7547BCFE792C7D94039C0236B662@DEMUEXC013.nsn-intra.ne t>, <359C3335DECB3764A8BC37B3@JcK-HP8200.jck.com> <629A968E-8104-4E6D-B393-CEBEDEC5FFDD@cisco.com>
In-Reply-To: <629A968E-8104-4E6D-B393-CEBEDEC5FFDD@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]); Thu, 09 Aug 2012 13:57:07 -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, 09 Aug 2012 20:57:10 -0000

> Yes, and sadly that rules out really good venues such as Kuala
> Lumpur, quite possibly the least expensive (hotel wise) suitable
> location in Asia.


The IAOC researched this recently, quite thoroughly; Ole and I are both
biased towards wanting it.  (I lived there for a year.)

This is worth mentioning because the MY formal rule is not strict
prohibition but a formal visa process that is so onerous as to equate to
a prohibition.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From mehmet.ersue@nsn.com  Thu Aug  9 14:15:43 2012
Return-Path: <mehmet.ersue@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 43B7221F85B8 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 14:15:43 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BIWwiYYp9oI0 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 14:15:42 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 3DF9221F85AC for <ietf@ietf.org>; Thu,  9 Aug 2012 14:15:42 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q79LFSX7027934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 9 Aug 2012 23:15:29 +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 q79LFRT1029979; Thu, 9 Aug 2012 23:15:27 +0200
Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 9 Aug 2012 23:15:27 +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: So, where to repeat? (was: Re: management granularity)
Date: Thu, 9 Aug 2012 23:15:25 +0200
Message-ID: <80A0822C5E9A4440A5117C2F4CD36A64041CD5E7@DEMUEXC006.nsn-intra.net>
In-Reply-To: <629A968E-8104-4E6D-B393-CEBEDEC5FFDD@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: So, where to repeat? (was: Re: management granularity)
Thread-Index: AQHNdm+CPY9STExk+0qjcr7YA02QG5dR85T4gAAAUqA=
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <80A0822C5E9A4440A5117C2F4CD36A64041CD5E4@DEMUEXC006.nsn-intra.net> <E4873516F3FC7547BCFE792C7D94039C0236B662@DEMUEXC013.nsn-intra.ne t>, <359C3335DECB3764A8BC37B3@JcK-HP8200.jck.com> <629A968E-8104-4E6D-B393-CEBEDEC5FFDD@cisco.com>
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>, "John C Klensin" <john-ietf@jck.com>
X-OriginalArrivalTime: 09 Aug 2012 21:15:27.0533 (UTC) FILETIME=[193D15D0:01CD7674]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 2690
X-purgate-ID: 151667::1344546931-00003184-E96A513D/0-0/0-0
Cc: ext Geoff Mulligan <geoff@proto6.com>, "ext Ole Jacobsen \(ole\)" <ole@cisco.com>, dcrocker@bbiw.net, ietf@ietf.org, Richard Shockey <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: Thu, 09 Aug 2012 21:15:43 -0000

> > But, as soon as a country says "if you have a
> > passport from X, you aren't getting in, don't even bother to
> > apply for a visa", they should be off our list of possibilities.

It is sad to hear this. I actually never heard such restrictions for
people travelling to Turkey.

BTW: A lot of countries, including Israel, don't need a visa for Turkey.
For others it is technically a non-issue to get it at the border.

Beside many European cities there are direct flights to Istanbul from:
Los Angeles, Washington, Chicago, New York, Beijing, Tokyo, Seoul,
Bangkok, and Tel Aviv.

Cheers,=20
Mehmet=20


> -----Original Message-----
> From: ext Ole Jacobsen (ole) [mailto:ole@cisco.com]
> Sent: Thursday, August 09, 2012 10:48 PM
> To: John C Klensin
> Cc: Sprecher, Nurit (NSN - IL/Hod HaSharon); Ersue, Mehmet (NSN -
DE/Munich); ext
> Geoff Mulligan; Richard Shockey; ietf@ietf.org; dcrocker@bbiw.net
> Subject: Re: So, where to repeat? (was: Re: management granularity)
>=20
> Yes, and sadly that rules out really good venues such as Kuala Lumpur,
quite possibly
> the least expensive (hotel wise) suitable location in Asia.
>=20
> Ole J. Jacobsen
> Editor & Publisher
> http://cisco.com/ipj
>=20
> Sent from my iPhone
>=20
> On 9 Aug 2012, at 13:42, "John C Klensin" <john-ietf@jck.com> wrote:
>=20
> > Let me say that a different way.  We sometimes have to tolerate
> > countries, like the US, who a fussy about visas or immigration
> > procedures for people coming from specific other countries.  I
> > wish we didn't.  But, as soon as a country says "if you have a
> > passport from X, you aren't getting in, don't even bother to
> > apply for a visa", they should be off our list of possibilities.
> >
> >   john
> >
> >
> > --On Thursday, August 09, 2012 22:22 +0200 "Sprecher, Nurit (NSN
> > - IL/Hod HaSharon)" <nurit.sprecher@nsn.com> wrote:
> >
> >> Istanbul, Dubai, and similar places will not allow all of us
> >> in the community to participate in the meetings....
> >>
> >>
> >> -----Original Message-----
> >> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On
> >> Behalf Of Ersue, Mehmet (NSN - DE/Munich)
> >> Sent: Thursday, August 09, 2012 11:20 PM
> >> To: ext Geoff Mulligan; Ole Jacobsen
> >> Cc: ietf@ietf.org; dcrocker@bbiw.net; Richard Shockey
> >> Subject: RE: So, where to repeat? (was: Re: management
> >> granularity)
> >>
> >> Why not consider Istanbul? It's another nice harbor city.
> >>
> >> Has a series of world class hotels like Grand Hyatt, Hilton,
> >> InterContinental, Radisson Blu but also less expensive hotels,
> >> close to each other.
> >
> >
> >
> >

From ole@cisco.com  Thu Aug  9 14:31:27 2012
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60C7421F86D4 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 14:31:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.566
X-Spam-Level: 
X-Spam-Status: No, score=-110.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W9vaKe2fliae for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 14:31:26 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id DF08521F86B4 for <ietf@ietf.org>; Thu,  9 Aug 2012 14:31:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=241; q=dns/txt; s=iport; t=1344547886; x=1345757486; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=i4Obd3sp1cUO/jsNuMkvsaQABzlZTd05h68OVrjPGfI=; b=TiJBtTPS1jdmu/Qicd13gDjNc1b4j4tCwscHz2qwiOB8NTfNkHxKHfBg O6PPJhjNPjT4cXq76QSg0xvSXiOfEMWxHJoD+jAoQ89AA2a5Osn3CswSg rMEYs2bm+SLU1KpfGKvDG+OQOqjGluFAM5GRrcJIYt+K7nYxAuD95vwXr A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FAIzgI1CrRDoH/2dsb2JhbABFhTq0KIEHgiABAQEDARIBAiU/EAtGVwY1h2UFmweDSBCdEQSLD4ZkA4hOkleITYEEYoJ/
X-IronPort-AV: E=Sophos;i="4.77,742,1336348800"; d="scan'208";a="51468667"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-1.cisco.com with ESMTP; 09 Aug 2012 21:31:26 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q79LVP96012810 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Aug 2012 21:31:26 GMT
Date: Thu, 9 Aug 2012 14:31:25 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: So, where to repeat? (was: Re: management granularity)
In-Reply-To: <50242289.2040108@stpeter.im>
Message-ID: <alpine.OSX.2.01.1208091430540.37089@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <80A0822C5E9A4440A5117C2F4CD36A64041CD5E4@DEMUEXC006.nsn-intra.net> <E4873516F3FC7547BCFE792C7D94039C0236B662@DEMUEXC013.nsn-intra.ne t> <359C3335DECB3764A8BC37B3@JcK-HP8200.jck.com> <50242289.2040108@stpeter.im>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org, Richard Shockey <richard@shockey.us>, ext Geoff Mulligan <geoff@proto6.com>, dcrocker@bbiw.net, John C Klensin <john-ietf@jck.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 21:31:27 -0000

We HAVE a requirements document.

Ole

On Thu, 9 Aug 2012, Peter Saint-Andre wrote:

> 
> Agreed.
> 
> Dare I say that we need a requirements document? ;-)
> 
> Peter
> 
> Peter Saint-Andre
> https://stpeter.im/
> 
> 
> 

From stpeter@stpeter.im  Thu Aug  9 14:44:57 2012
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 21E4921F860F for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 14:44:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.752
X-Spam-Level: 
X-Spam-Status: No, score=-102.752 tagged_above=-999 required=5 tests=[AWL=-0.153, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cgb+dUBWalso for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 14:44:56 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 86D2521F8604 for <ietf@ietf.org>; Thu,  9 Aug 2012 14:44:56 -0700 (PDT)
Received: from [192.168.0.4] (unknown [67.177.192.224]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id B7925404EA; Thu,  9 Aug 2012 15:45:04 -0600 (MDT)
Message-ID: <50242F55.8060301@stpeter.im>
Date: Thu, 09 Aug 2012 15:44:53 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Ole Jacobsen <ole@cisco.com>
Subject: Re: So, where to repeat?
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <80A0822C5E9A4440A5117C2F4CD36A64041CD5E4@DEMUEXC006.nsn-intra.net> <E4873516F3FC7547BCFE792C7D94039C0236B662@DEMUEXC013.nsn-intra.ne t> <359C3335DECB3764A8BC37B3@JcK-HP8200.jck.com> <50242289.2040108@stpeter.im> <alpine.OSX.2.01.1208091430540.37089@173-11-110-132-sfba.hfc.comcastbusiness.net>
In-Reply-To: <alpine.OSX.2.01.1208091430540.37089@173-11-110-132-sfba.hfc.comcastbusiness.net>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Richard Shockey <richard@shockey.us>, ext Geoff Mulligan <geoff@proto6.com>, dcrocker@bbiw.net, John C Klensin <john-ietf@jck.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 21:44:57 -0000

On 8/9/12 3:31 PM, Ole Jacobsen wrote:
> 
> We HAVE a requirements document.

Aha, so it's just that people at the mic haven't read the draft. That
never happens at one of our meetings, does it? ;-)

Unfortunately, I can't seem to find this requirements document in the
datatracker...

Peter

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



From johnl@iecc.com  Thu Aug  9 15:04:58 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8213921F86D4 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 15:04:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.16
X-Spam-Level: 
X-Spam-Status: No, score=-111.16 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HLaIdk5a-qlC for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 15:04:57 -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 BCC0421F86D3 for <ietf@ietf.org>; Thu,  9 Aug 2012 15:04:56 -0700 (PDT)
Received: (qmail 45061 invoked from network); 9 Aug 2012 22:04:54 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 9 Aug 2012 22:04:54 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50243406.xn--btvx9d.k1208; i=johnl@user.iecc.com; bh=N0qWir5MudlzYSDOn1CpPR/xO/x2zMrWB2EFhcIsoQA=; b=ogNZS7W4xMg9MZMmT1w/BtKxK2EJKSbamJOVvOM0P/yLPPg7FnB86t8X+bpHMgRKbi2AW/J+qRRYn7HPr10N4WqI8O8JMzxarGUhBmnH4XfAVSvZwV1vRtTTNrLPUXGLVb/I/PO2qmmvgrTnOKG0NU6IJ9EKROYoBMDFFNJG7zk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50243406.xn--btvx9d.k1208; olt=johnl@user.iecc.com; bh=N0qWir5MudlzYSDOn1CpPR/xO/x2zMrWB2EFhcIsoQA=; b=E/yAv87McAY80RxSxxdpeOCDirQ3uCFoOSDQfHlAq3CAIXetYDttAm8KVQ/Yr+un9sEaZipFpRyNYyMVG8aKqVy4BtM4hWPmeyPgF+98ftBWQnvSuLM0BKNXeEu2KoQnu+9YMEQyom3yusqbq1x9f7ct7sCf5z+wEKwqTDJXFFw=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 9 Aug 2012 22:04:32 -0000
Message-ID: <20120809220432.83061.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: So, where to repeat? (was: Re: management granularity)
In-Reply-To: <5024241A.8040804@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: Thu, 09 Aug 2012 22:04:58 -0000

>This is worth mentioning because the MY formal rule is not strict
>prohibition but a formal visa process that is so onerous as to equate to
>a prohibition.

Wouldn't that rule out the United States?  It is my impression that
getting a US visa for someone with a Cuban or Iranian passport is
effectively impossible.

R's,
John

From rbonica@juniper.net  Thu Aug  9 16:48:46 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D215621F8694 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 16:48:46 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cxgmvd9aZWWv for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 16:48:46 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id 1DA5E21F8690 for <ietf@ietf.org>; Thu,  9 Aug 2012 16:48:45 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUCRMXY8P0XB8Id7+RbHJfj29ePZzkGnG@postini.com; Thu, 09 Aug 2012 16:48:46 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.3.213.0; Thu, 9 Aug 2012 16:47:15 -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; Thu, 9 Aug 2012 19:47:14 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: IETF Discussion <ietf@ietf.org>
Date: Thu, 9 Aug 2012 19:47:12 -0400
Subject: Liaison Statement from the Broadband Forum
Thread-Topic: Liaison Statement from the Broadband Forum
Thread-Index: Ac12iUxanGB/fuvuSKermmvvwbOu4Q==
Message-ID: <13205C286662DE4387D9AF3AC30EF456D771989330@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, 09 Aug 2012 23:48:46 -0000

Folks,

The Broadband Forum has sent a liaison statement to the IETF regarding a "N=
ew Project - Broadband Access Service Attributes and Performance Measures".=
=20

Click on the following link for details: https://datatracker.ietf.org/liais=
on/1179/.

Please review and send comments to this list.

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


From randy@psg.com  Thu Aug  9 20:12:31 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97E4321F8446 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 20:12:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level: 
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1CYclIYBiFt3 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 20:12:31 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 0E32F21F8443 for <ietf@ietf.org>; Thu,  9 Aug 2012 20:12:31 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SzfeH-0005QT-OL; Fri, 10 Aug 2012 03:12:30 +0000
Date: Thu, 09 Aug 2012 23:12:40 -0400
Message-ID: <m2sjbvxwwn.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: ITU-T Dubai Meeting
In-Reply-To: <CAMm+LwjEara+=_BKu7JFsf4Fhbyxr8b6R-hL-QNX0qfXvZLztg@mail.gmail.com>
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu> <CAMm+Lwg2HgO-=9ED4vbmO+Vf9r6bYPcLDgfyMAyPdEPVgRm4LQ@mail.gmail.com> <FB949BEA-5BDB-401A-8A75-E9A9BDAA72A6@ripe.net> <20120803182500.1F9512344DBF@drugs.dv.isc.org> <1938E5FD-57DE-4172-834A-55CA1FDAF29A@burkov.aha.ru> <CAMm+Lwhw=XUPKgAJaVeXcQ5mG++hNL9PkmAfqOPyVZo9oi=suQ@mail.gmail.com> <m2vcgs85qn.wl%randy@psg.com> <CAMm+LwjEara+=_BKu7JFsf4Fhbyxr8b6R-hL-QNX0qfXvZLztg@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
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 03:12:31 -0000

> Hubris? it has already lasted 40.

and it's such a short way from 40 to "hundreds or thousands."  i get it.

> I can understand why people might not want to worry about long term
> issues but not why you would want to insult people who do think about
> them.

first, i did not insult anyone.  if you took it as an insult, take it up
with your shaman, rabi, priest, or shrink.

secondly, 

> You botched DNSSEC deployment because you were incapable of
> considering such issues

damn!  and i missed where i had anything to do with dnssec deployment.
but i am glad we all now understand why it has fared so badly.

> if we accept your argument now we will get another botch job.

an i am guilty of ad homina?

> The fact that outcomes cannot be predicted with 100% certainty does
> not mean that all outcomes are equally likely or that we have
> absolutely no control over them or that there is no point in
> discussing them.

my point was predicting technology outcomes "hundreds if not thousands"
of years in the future is beyond hyperbolic.

randy

From hartmans@mit.edu  Thu Aug  9 21:36:11 2012
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E694821F8523 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 21:36:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.624
X-Spam-Level: 
X-Spam-Status: No, score=-98.624 tagged_above=-999 required=5 tests=[AWL=-4.401, BAYES_05=-1.11, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f0E5yZyP1+0A; Thu,  9 Aug 2012 21:36:10 -0700 (PDT)
Received: from ec2-23-21-76-251.compute-1.amazonaws.com (ec2-23-21-227-93.compute-1.amazonaws.com [23.21.227.93]) by ietfa.amsl.com (Postfix) with ESMTP id 3DA4121F84F6; Thu,  9 Aug 2012 21:36:08 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id A58E62029E; Fri, 10 Aug 2012 00:36:06 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 79478420F; Fri, 10 Aug 2012 00:35:59 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: NomCom Chair <nomcom-chair@ietf.org>
Subject: Re: Final List of NomCom 2012-13 Volunteers
References: <20120806040148.27923.65936.idtracker@ietfa.amsl.com>
Date: Fri, 10 Aug 2012 00:35:59 -0400
In-Reply-To: <20120806040148.27923.65936.idtracker@ietfa.amsl.com> (NomCom Chair's message of "Sun, 05 Aug 2012 21:01:48 -0700")
Message-ID: <tslfw7ve53k.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 04:36:11 -0000

hi.  I regret having to do this. I realize the nomcom is important, and
it's a valuable way to contribute to the community. Unfortunately, I've
taken on some responsibilities since the nomcom call for volunteers.
I'm no longer sure that I will have the time to do as good of a job on
the nomcom as I'd like.  For that reason I'd like to ask you to
disqualify me if I'm selected.


--Sam

From narten@us.ibm.com  Thu Aug  9 21:53:11 2012
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8F2D11E80E1 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 21:53:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.293
X-Spam-Level: 
X-Spam-Status: No, score=-110.293 tagged_above=-999 required=5 tests=[AWL=0.306, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EgvwM-r-3ycY for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 21:53:10 -0700 (PDT)
Received: from e36.co.us.ibm.com (e36.co.us.ibm.com [32.97.110.154]) by ietfa.amsl.com (Postfix) with ESMTP id 9E78C11E80E0 for <ietf@ietf.org>; Thu,  9 Aug 2012 21:53:10 -0700 (PDT)
Received: from /spool/local by e36.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 9 Aug 2012 22:53:09 -0600
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e36.co.us.ibm.com (192.168.1.136) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 9 Aug 2012 22:53:08 -0600
Received: from d03relay03.boulder.ibm.com (d03relay03.boulder.ibm.com [9.17.195.228]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id E8FEB3E40039 for <ietf@ietf.org>; Fri, 10 Aug 2012 04:53:05 +0000 (WET)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay03.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q7A4r7UD161306 for <ietf@ietf.org>; Thu, 9 Aug 2012 22:53:07 -0600
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q7A4r60W013704 for <ietf@ietf.org>; Thu, 9 Aug 2012 22:53:06 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q7A4r6sG013692 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 9 Aug 2012 22:53:06 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q7A4r5OJ011664 for <ietf@ietf.org>; Fri, 10 Aug 2012 00:53:05 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q7A4r4W6011650 for ietf@ietf.org; Fri, 10 Aug 2012 00:53:04 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201208100453.q7A4r4W6011650@rotala.raleigh.ibm.com>
Date: Fri, 10 Aug 2012 00:53:04 -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-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12081004-7606-0000-0000-000002B0BB52
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 04:53:11 -0000

Total of 245 messages in the last 7 days.
 
script run at: Fri Aug 10 00:53:03 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  5.31% |   13 |  8.41% |   168471 | mary.ietf.barnes@gmail.com
  4.90% |   12 |  4.16% |    83408 | ole@cisco.com
  2.45% |    6 |  5.60% |   112211 | nurit.sprecher@nsn.com
  2.04% |    5 |  6.00% |   120224 | chris.dearlove@baesystems.com
  3.27% |    8 |  2.69% |    53888 | ynir@checkpoint.com
  3.27% |    8 |  2.34% |    46944 | johnl@taugh.com
  2.45% |    6 |  3.12% |    62539 | geoff@proto6.com
  2.04% |    5 |  3.31% |    66313 | glenzorn@gmail.com
  2.86% |    7 |  2.31% |    46253 | mnot@mnot.net
  2.86% |    7 |  2.14% |    42785 | dhc@dcrocker.net
  2.45% |    6 |  1.97% |    39500 | dcrocker@bbiw.net
  2.04% |    5 |  2.35% |    47137 | daedulus@btconnect.com
  2.45% |    6 |  1.87% |    37523 | dworley@avaya.com
  2.04% |    5 |  1.98% |    39752 | brian.e.carpenter@gmail.com
  2.45% |    6 |  1.53% |    30556 | randy@psg.com
  1.63% |    4 |  2.11% |    42341 | aservin@lacnic.net
  2.04% |    5 |  1.66% |    33296 | ajs@anvilwalrusden.com
  2.04% |    5 |  1.59% |    31783 | john-ietf@jck.com
  2.04% |    5 |  1.37% |    27425 | mrex@sap.com
  1.63% |    4 |  1.73% |    34585 | mehmet.ersue@nsn.com
  1.63% |    4 |  1.57% |    31541 | spromano@unina.it
  1.63% |    4 |  1.43% |    28593 | tjc@ecs.soton.ac.uk
  1.63% |    4 |  1.41% |    28299 | sm@resistor.net
  1.63% |    4 |  1.04% |    20868 | dougb@dougbarton.us
  1.22% |    3 |  1.42% |    28443 | hsantos@isdg.net
  0.82% |    2 |  1.82% |    36521 | richard@shockey.us
  1.22% |    3 |  1.04% |    20831 | ned+ietf@mauve.mrochek.com
  1.22% |    3 |  0.99% |    19863 | daniel.karrenberg@ripe.net
  1.22% |    3 |  0.93% |    18630 | cabo@tzi.org
  1.22% |    3 |  0.92% |    18414 | mcr+ietf@sandelman.ca
  1.22% |    3 |  0.90% |    18089 | vesely@tana.it
  1.22% |    3 |  0.87% |    17367 | stpeter@stpeter.im
  1.22% |    3 |  0.69% |    13910 | jnc@mercury.lcs.mit.edu
  0.82% |    2 |  1.01% |    20137 | touch@isi.edu
  0.82% |    2 |  0.88% |    17558 | barryleiba@computer.org
  0.82% |    2 |  0.79% |    15886 | hallam@gmail.com
  0.82% |    2 |  0.79% |    15790 | joelja@bogus.com
  0.82% |    2 |  0.77% |    15482 | mohta@necom830.hpcl.titech.ac.jp
  0.82% |    2 |  0.74% |    14859 | stephen.farrell@cs.tcd.ie
  0.82% |    2 |  0.70% |    14070 | dave@cridland.net
  0.82% |    2 |  0.70% |    14009 | arturo.servin@gmail.com
  0.82% |    2 |  0.70% |    14004 | mcr@sandelman.ca
  0.82% |    2 |  0.64% |    12865 | j.schoenwaelder@jacobs-university.de
  0.82% |    2 |  0.64% |    12769 | robert@raszuk.net
  0.82% |    2 |  0.63% |    12645 | melinda.shore@gmail.com
  0.82% |    2 |  0.63% |    12579 | agmalis@gmail.com
  0.82% |    2 |  0.61% |    12221 | scott.brim@gmail.com
  0.82% |    2 |  0.58% |    11652 | rbonica@juniper.net
  0.82% |    2 |  0.58% |    11583 | housley@vigilsec.com
  0.82% |    2 |  0.58% |    11533 | dburk@burkov.aha.ru
  0.82% |    2 |  0.57% |    11515 | jason_livingood@cable.comcast.com
  0.82% |    2 |  0.57% |    11505 | marka@isc.org
  0.82% |    2 |  0.54% |    10739 | drc@virtualized.org
  0.82% |    2 |  0.53% |    10528 | paul.hoffman@vpnc.org
  0.41% |    1 |  0.85% |    17054 | tom.haynes@netapp.com
  0.41% |    1 |  0.64% |    12873 | lars@netapp.com
  0.41% |    1 |  0.55% |    11015 | amorris@amsl.com
  0.41% |    1 |  0.49% |     9854 | narten@us.ibm.com
  0.41% |    1 |  0.48% |     9656 | anshumanpratap@gmail.com
  0.41% |    1 |  0.47% |     9422 | daniele.ceccarelli@ericsson.com
  0.41% |    1 |  0.46% |     9234 | dhruv.ietf@gmail.com
  0.41% |    1 |  0.44% |     8860 | mrw@lilacglade.org
  0.41% |    1 |  0.43% |     8576 | andy@yumaworks.com
  0.41% |    1 |  0.42% |     8464 | jmpolk@cisco.com
  0.41% |    1 |  0.42% |     8373 | kuor-hsin.chang@us.elster.com
  0.41% |    1 |  0.37% |     7446 | andy@hxr.us
  0.41% |    1 |  0.37% |     7351 | ietfdbh@comcast.net
  0.41% |    1 |  0.36% |     7205 | randy_presuhn@mindspring.com
  0.41% |    1 |  0.35% |     7076 | jhildebr@cisco.com
  0.41% |    1 |  0.35% |     6972 | rja.lists@gmail.com
  0.41% |    1 |  0.34% |     6841 | vinayakh@gmail.com
  0.41% |    1 |  0.34% |     6779 | tbray@textuality.com
  0.41% |    1 |  0.34% |     6762 | henrik@levkowetz.com
  0.41% |    1 |  0.33% |     6566 | hartmans-ietf@mit.edu
  0.41% |    1 |  0.33% |     6554 | stewe@stewe.org
  0.41% |    1 |  0.32% |     6316 | martin.thomson@gmail.com
  0.41% |    1 |  0.31% |     6303 | timo.perala@nsn.com
  0.41% |    1 |  0.31% |     6137 | michal@krsek.cz
  0.41% |    1 |  0.28% |     5655 | paf@frobbit.se
  0.41% |    1 |  0.28% |     5537 | afarrel@juniper.net
  0.41% |    1 |  0.28% |     5532 | simon.perreault@viagenie.ca
  0.41% |    1 |  0.28% |     5531 | tnadeau@lucidvision.com
  0.41% |    1 |  0.27% |     5497 | smb@cs.columbia.edu
  0.41% |    1 |  0.27% |     5316 | steve@shinkuro.com
  0.41% |    1 |  0.26% |     5272 | philip_matthews@magma.ca
  0.41% |    1 |  0.26% |     5251 | william.atwood@concordia.ca
  0.41% |    1 |  0.26% |     5171 | ietf@meetecho.com
--------+------+--------+----------+------------------------
100.00% |  245 |100.00% |  2002683 | Total


From alexey.melnikov@isode.com  Fri Aug 10 01:55:37 2012
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 8DA4F21F841B; Fri, 10 Aug 2012 01:55:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.375
X-Spam-Level: 
X-Spam-Status: No, score=-102.375 tagged_above=-999 required=5 tests=[AWL=-0.845, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ROKsW45Fovmy; Fri, 10 Aug 2012 01:55:37 -0700 (PDT)
Received: from waldorf.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id D4A7821F852C; Fri, 10 Aug 2012 01:55:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1344588934; d=isode.com; s=selector; i=@isode.com; bh=00/1+9E+AM7GqxYBAXVF+YQh/LQlEXBj8s3wxQ/OuJ8=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=ncGxuHp0wlue+qJqcRblnzyg4u4o351jL53HTSWq/NtO8sShNNfZnWRsqPQ2bQ1McIQWEA 9APIDlfHgo0XzhOs14XgV9ih2FtGFZDayBHPJZN9suNB8H3W7CBwqepyG03zutOipZpDgy Z4NyOgT5p1jF5tGZHBKnVxHiXIw0dwI=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <UCTMfgBvaBmt@waldorf.isode.com>; Fri, 10 Aug 2012 09:55:33 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <502441B7.8020001@isode.com>
Date: Fri, 10 Aug 2012 00:03:19 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
To: Ben Campbell <ben@nostrum.com>, =JeffH <Jeff.Hodges@kingsmountain.com>
Subject: Re: Gen-ART LC Review of draft-ietf-websec-strict-transport-sec-11
References: <50161BD5.7040901@KingsMountain.com> <344AB802-6D45-4399-A628-6852A4732C16@nostrum.com>
In-Reply-To: <344AB802-6D45-4399-A628-6852A4732C16@nostrum.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>, IETF WebSec WG <websec@ietf.org>, draft-ietf-websec-strict-transport-sec.all@tools.ietf.org, IETF Discussion List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 08:55:37 -0000

On 02/08/2012 10:46, Ben Campbell wrote:
> Hi, thanks for the response.  Comments inline:
>
> On Jul 29, 2012, at 10:29 PM, =JeffH <Jeff.Hodges@kingsmountain.com> wrote:
  [...]
>>> -- section 7.2:
>>>
>>> Am I correct to assume that the server must never just serve the content over
>>> a non-secure connection? If so, it would be helpful to mention that, maybe
>>> even normatively.
>> It's a SHOULD, see the Note in that section, so it's already effectively stated normatively, though one needs to understand HTTP workings to realize it in the way you stated it above.  Perhaps could add a simple statement as you suggest to the intro para for section 7 Server Processing Model, to address this concern?
>>
> I think something of the form SHOULD redirect to HTTPS, but MUST NOT under any circumstances send the content unprotected would improve the text.

Sounds good to me. (And yes, this is implied, but it doesn't hurt to 
state explicitly.)

> That's probably already implied, and a reasonable implementor wouldn't due it anyway. But my experience is that some readers will find strange interpretations whenever you give them the wiggle room to do so, so it's better to be explicit.



From tobias.gondrom@gondrom.org  Fri Aug 10 03:03:18 2012
Return-Path: <tobias.gondrom@gondrom.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A098A21F8646 for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 03:03:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.711
X-Spam-Level: 
X-Spam-Status: No, score=-97.711 tagged_above=-999 required=5 tests=[AWL=-2.350, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NXf6B2cLmEgV for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 03:03:18 -0700 (PDT)
Received: from lvps176-28-13-69.dedicated.hosteurope.de (lvps176-28-13-69.dedicated.hosteurope.de [176.28.13.69]) by ietfa.amsl.com (Postfix) with ESMTP id A050621F8577 for <ietf@ietf.org>; Fri, 10 Aug 2012 03:03:17 -0700 (PDT)
Received: (qmail 20391 invoked from network); 10 Aug 2012 12:03:11 +0200
Received: from 94-194-102-93.zone8.bethere.co.uk (HELO ?192.168.1.65?) (94.194.102.93) by lvps176-28-13-69.dedicated.hosteurope.de with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 10 Aug 2012 12:03:11 +0200
Message-ID: <5024DC5E.60404@gondrom.org>
Date: Fri, 10 Aug 2012 11:03:10 +0100
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: alexey.melnikov@isode.com
Subject: Re: Gen-ART LC Review of draft-ietf-websec-strict-transport-sec-11
References: <50161BD5.7040901@KingsMountain.com> <344AB802-6D45-4399-A628-6852A4732C16@nostrum.com> <502441B7.8020001@isode.com>
In-Reply-To: <502441B7.8020001@isode.com>
Content-Type: multipart/alternative; boundary="------------080205060203060004010107"
Cc: ben@nostrum.com, ietf@ietf.org, gen-art@ietf.org, websec@ietf.org, draft-ietf-websec-strict-transport-sec.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 10:03:18 -0000

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

On 10/08/12 00:03, Alexey Melnikov wrote:
> On 02/08/2012 10:46, Ben Campbell wrote:
>> Hi, thanks for the response.  Comments inline:
>>
>> On Jul 29, 2012, at 10:29 PM, =JeffH <Jeff.Hodges@kingsmountain.com> 
>> wrote:
>  [...]
>>>> -- section 7.2:
>>>>
>>>> Am I correct to assume that the server must never just serve the 
>>>> content over
>>>> a non-secure connection? If so, it would be helpful to mention 
>>>> that, maybe
>>>> even normatively.
>>> It's a SHOULD, see the Note in that section, so it's already 
>>> effectively stated normatively, though one needs to understand HTTP 
>>> workings to realize it in the way you stated it above. Perhaps could 
>>> add a simple statement as you suggest to the intro para for section 
>>> 7 Server Processing Model, to address this concern?
>>>
>> I think something of the form SHOULD redirect to HTTPS, but MUST NOT 
>> under any circumstances send the content unprotected would improve 
>> the text.
>
> Sounds good to me. (And yes, this is implied, but it doesn't hurt to 
> state explicitly.)
>
>> That's probably already implied, and a reasonable implementor 
>> wouldn't due it anyway. But my experience is that some readers will 
>> find strange interpretations whenever you give them the wiggle room 
>> to do so, so it's better to be explicit.
>
>
<hat="individual">
Agree with Alexey and Ben. Tobias



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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 10/08/12 00:03, Alexey Melnikov
      wrote:<br>
    </div>
    <blockquote cite="mid:502441B7.8020001@isode.com" type="cite">On
      02/08/2012 10:46, Ben Campbell wrote:
      <br>
      <blockquote type="cite">Hi, thanks for the response.&nbsp; Comments
        inline:
        <br>
        <br>
        On Jul 29, 2012, at 10:29 PM, =JeffH
        <a class="moz-txt-link-rfc2396E" href="mailto:Jeff.Hodges@kingsmountain.com">&lt;Jeff.Hodges@kingsmountain.com&gt;</a> wrote:
        <br>
      </blockquote>
      &nbsp;[...]
      <br>
      <blockquote type="cite">
        <blockquote type="cite">
          <blockquote type="cite">-- section 7.2:
            <br>
            <br>
            Am I correct to assume that the server must never just serve
            the content over
            <br>
            a non-secure connection? If so, it would be helpful to
            mention that, maybe
            <br>
            even normatively.
            <br>
          </blockquote>
          It's a SHOULD, see the Note in that section, so it's already
          effectively stated normatively, though one needs to understand
          HTTP workings to realize it in the way you stated it above.&nbsp;
          Perhaps could add a simple statement as you suggest to the
          intro para for section 7 Server Processing Model, to address
          this concern?
          <br>
          <br>
        </blockquote>
        I think something of the form SHOULD redirect to HTTPS, but MUST
        NOT under any circumstances send the content unprotected would
        improve the text.
        <br>
      </blockquote>
      <br>
      Sounds good to me. (And yes, this is implied, but it doesn't hurt
      to state explicitly.)
      <br>
      <br>
      <blockquote type="cite">That's probably already implied, and a
        reasonable implementor wouldn't due it anyway. But my experience
        is that some readers will find strange interpretations whenever
        you give them the wiggle room to do so, so it's better to be
        explicit.
        <br>
      </blockquote>
      <br>
      <br>
    </blockquote>
    &lt;hat="individual"&gt;
    <br>
    <font face="Arial">Agree with Alexey and Ben. Tobias<br>
      <br>
    </font><br>
  </body>
</html>

--------------080205060203060004010107--

From hallam@gmail.com  Fri Aug 10 05:31:13 2012
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72E3D21F85C3 for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 05:31:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.579
X-Spam-Level: 
X-Spam-Status: No, score=-5.579 tagged_above=-999 required=5 tests=[AWL=-1.980, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RNlovggFgO9x for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 05:31:12 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id A636221F8491 for <ietf@ietf.org>; Fri, 10 Aug 2012 05:31:12 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so2581828obb.31 for <ietf@ietf.org>; Fri, 10 Aug 2012 05:31:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4qbaQcQLVzch/Mg0Ku+fxQV/YF1FIoo9BeIK0pS4HsE=; b=JMIaiDCwFOnze1VfFnLNO1yVWV6f2uOLfELBeMkSaZBrBk8noy//PRFYEe6DOLRs1e FP/4Xq+Si5v34xHGEkkRwSNuJk4C1Xy/QdXivoO7JvwF4nLiB0/abqkuZh+qljxIEzDu QZ5+5T1WAc7lJF2dMbmEJmy+dXzxe4Ix9Jxk6ROjZOpOM8f3/QxFzVZKNp/WQ0FULdEF 23MfgWcNnkrYoEHP+gulYelB/gOoLeaWEZEi9/eqVSdVJiKhuaZIZuEsjQ+oDsrN5aGn Bs84yuv1FR9zStJasF+A+y0xei89QDNRcg49bEPM45TNCXBhzFB+KZiWWrw7UR/f2Aoe XS/A==
MIME-Version: 1.0
Received: by 10.60.29.228 with SMTP id n4mr3936974oeh.27.1344601872105; Fri, 10 Aug 2012 05:31:12 -0700 (PDT)
Received: by 10.76.80.10 with HTTP; Fri, 10 Aug 2012 05:31:11 -0700 (PDT)
In-Reply-To: <m2sjbvxwwn.wl%randy@psg.com>
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu> <CAMm+Lwg2HgO-=9ED4vbmO+Vf9r6bYPcLDgfyMAyPdEPVgRm4LQ@mail.gmail.com> <FB949BEA-5BDB-401A-8A75-E9A9BDAA72A6@ripe.net> <20120803182500.1F9512344DBF@drugs.dv.isc.org> <1938E5FD-57DE-4172-834A-55CA1FDAF29A@burkov.aha.ru> <CAMm+Lwhw=XUPKgAJaVeXcQ5mG++hNL9PkmAfqOPyVZo9oi=suQ@mail.gmail.com> <m2vcgs85qn.wl%randy@psg.com> <CAMm+LwjEara+=_BKu7JFsf4Fhbyxr8b6R-hL-QNX0qfXvZLztg@mail.gmail.com> <m2sjbvxwwn.wl%randy@psg.com>
Date: Fri, 10 Aug 2012 08:31:11 -0400
Message-ID: <CAMm+Lwi6EBavRdUqsS1YRwr01m31LfZW=LPtMERRwb8NmqbuyQ@mail.gmail.com>
Subject: Re: ITU-T Dubai Meeting
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Randy Bush <randy@psg.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 12:31:13 -0000

On Thu, Aug 9, 2012 at 11:12 PM, Randy Bush <randy@psg.com> wrote:
>> Hubris? it has already lasted 40.
>
> and it's such a short way from 40 to "hundreds or thousands."  i get it.

40 is not very short of 100 at all.

And creating a legacy that other people have to work round is rather
too easy in this industry. The place is littered with them. COBOL will
probably last another century. QWERTY will. Lasting has little to
being good.


>> I can understand why people might not want to worry about long term
>> issues but not why you would want to insult people who do think about
>> them.
>
> first, i did not insult anyone.  if you took it as an insult, take it up
> with your shaman, rabi, priest, or shrink.

You pulled the 'I don't understand this so nobody else can' move. That
is pretty insulting.


>> You botched DNSSEC deployment because you were incapable of
>> considering such issues
>
> damn!  and i missed where i had anything to do with dnssec deployment.
> but i am glad we all now understand why it has fared so badly.

You are the reason that DNSSEC did not deploy in 2002. There was a
clear WG consensus to change the spec to make it deployable and you
used your position as WG chair to block it.

The code was written and would have deployed with the ATLAS upgrade.
You are the only reason it did not.

You thought that changing the specification to meet a deployment issue
was unreasonable. I told you repeatedly that there would be no
deployment unless the change was made. The result was that you 'won'
and DNSSEC was on hold for six years while the WG undid the mess you
made. Congratulations.

And now deployment of DNSSEC is much harder because the Internet is
now a cabinet level concern and there is an actual Russia-China treaty
that requires them to block it (amongst other things).


>> if we accept your argument now we will get another botch job.
>
> an i am guilty of ad homina?

Ad homniem is actually a valid argument against an unsubstantiated
personal opinion. 'Randy Bush made a botch of DNSSEC' is a perfectly
valid argument for rejecting Randy Bush's opinion on the value of long
term planning.


>> The fact that outcomes cannot be predicted with 100% certainty does
>> not mean that all outcomes are equally likely or that we have
>> absolutely no control over them or that there is no point in
>> discussing them.
>
> my point was predicting technology outcomes "hundreds if not thousands"
> of years in the future is beyond hyperbolic.

The point related to the institutions, not the technology.

Predicting that institutions will become corrupt over long periods of
time is hardly hyperbolic.


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

From randy@psg.com  Fri Aug 10 06:41:38 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACA6521F85D9 for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 06:41:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.558
X-Spam-Level: 
X-Spam-Status: No, score=-2.558 tagged_above=-999 required=5 tests=[AWL=0.041,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mMXygTrg-GGp for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 06:41:38 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 34C2B21F84EA for <ietf@ietf.org>; Fri, 10 Aug 2012 06:41:38 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SzpT6-0006QK-Qf; Fri, 10 Aug 2012 13:41:37 +0000
Date: Fri, 10 Aug 2012 09:41:47 -0400
Message-ID: <m2hasayick.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: ITU-T Dubai Meeting
In-Reply-To: <CAMm+Lwi6EBavRdUqsS1YRwr01m31LfZW=LPtMERRwb8NmqbuyQ@mail.gmail.com>
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu> <CAMm+Lwg2HgO-=9ED4vbmO+Vf9r6bYPcLDgfyMAyPdEPVgRm4LQ@mail.gmail.com> <FB949BEA-5BDB-401A-8A75-E9A9BDAA72A6@ripe.net> <20120803182500.1F9512344DBF@drugs.dv.isc.org> <1938E5FD-57DE-4172-834A-55CA1FDAF29A@burkov.aha.ru> <CAMm+Lwhw=XUPKgAJaVeXcQ5mG++hNL9PkmAfqOPyVZo9oi=suQ@mail.gmail.com> <m2vcgs85qn.wl%randy@psg.com> <CAMm+LwjEara+=_BKu7JFsf4Fhbyxr8b6R-hL-QNX0qfXvZLztg@mail.gmail.com> <m2sjbvxwwn.wl%randy@psg.com> <CAMm+Lwi6EBavRdUqsS1YRwr01m31LfZW=LPtMERRwb8NmqbuyQ@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
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 13:41:38 -0000

hundreds or thousands is perceptually much larger than 100.

> Predicting that institutions will become corrupt over long periods of
> time is hardly hyperbolic.

the institutions are corrupt now.

as to dnssec, opinions seem to vary widely, and yours is a few sigma
out.  some think you/verisign stalled it for five years becuase you
could not commercialize it.  but i really do not care.

randy

From mcr+ietf@sandelman.ca  Fri Aug 10 07:17:00 2012
Return-Path: <mcr+ietf@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 8CBAD21F85C5 for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 07:17:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.181
X-Spam-Level: 
X-Spam-Status: No, score=-2.181 tagged_above=-999 required=5 tests=[AWL=0.419,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qLGilSFnSKI0 for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 07:17:00 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id E66EF21F85C3 for <ietf@ietf.org>; Fri, 10 Aug 2012 07:16:59 -0700 (PDT)
Received: from obiwan.sandelman.ca (unknown [IPv6:2607:f0b0:f:2:3a60:77ff:fe38:e647]) by tuna.sandelman.ca (Postfix) with ESMTP id ED34120289 for <ietf@ietf.org>; Fri, 10 Aug 2012 10:29:49 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
to: ietf@ietf.org
Subject: Re: So, where to repeat?
In-Reply-To: <17661.1344454850@obiwan.sandelman.ca>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net> <20120806120547.GA20379@crankycanuck.ca> <B5630A95D803744A81C51AD4040A6DAA234677B967@ESESSCMS0360.eemea.ericsson.se> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9B1@GLKXM0002V.GREENLNK.net> <E4873516F3FC7547BCFE792C7D94039C02314C5E@DEMUEXC013.nsn-intra.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EBA9E4@GLKXM0002V.GREENLNK.net> <CAHBDyN5NLoJWMXEa8EdEVWxtUxm5XsuCjmqD4xn_N=2=7vKGXg@mail.gmail.com> <01ae01cd7412$abe83e50$03b8baf0$@us> <6BC80C42-9921-4141-B918-4101E873945E@proto6.com> <50229CFA.8080408@viagenie.ca> <17661.1344454850@obiwan.sandelman.ca>
X-Mailer: MH-E 8.3; nmh 1.5; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 10 Aug 2012 10:16:48 -0400
Message-ID: <4224.1344608208@obiwan.sandelman.ca>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 14:17:00 -0000

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


>>>>> "Michael" =3D=3D Michael Richardson <mcr@sandelman.ca> writes:
    Michael> but please, not Paris in the summer... nor Orlando on
    Michael> spring break)

ps: I'm really upset about Orlando in March.  We did that in back in
December 1998, and it seemed a failure to me.  Maybe this will be a
remote meeting for me. (go rps WG, go!!)

The hallways were WAY WAY too small for the people, thank god they
didn't serve the cookies there, and the social event... nice band, but
so loud, one couldn't talk to each other.

I understand that perhaps we won't be in the same conference centre, and
maybe NBC Universal will do a better job... but.

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


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

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

iQCVAwUAUCUX0IqHRg3pndX9AQJVjgQAzdPKG27zwanQrMsm2PAElGHGbsGBwAxM
FXY2dJtiyFscnuHBg790JGXH4kLEOwcRo3luCVAcvaWaMAk5xijjmzxEKBpRs5PI
RAvqViJrDPLgrTwGEiUTcV0JipF6chnR5hg4HYsY7Zk7Sr7BD3m9gPcm1JkjODFj
6EdrRZCNAVk=
=cHSP
-----END PGP SIGNATURE-----
--=-=-=--

From ben@estacado.net  Fri Aug 10 07:19:17 2012
Return-Path: <ben@estacado.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 622DB21F8604; Fri, 10 Aug 2012 07:19:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IqPgMkHDslNP; Fri, 10 Aug 2012 07:19:16 -0700 (PDT)
Received: from estacado.net (vicuna.estacado.net [4.30.77.35]) by ietfa.amsl.com (Postfix) with ESMTP id 9771121F85C3; Fri, 10 Aug 2012 07:19:16 -0700 (PDT)
Received: from [10.0.1.30] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by estacado.net (8.14.3/8.14.3) with ESMTP id q7AEGWUQ049872 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 10 Aug 2012 09:16:38 -0500 (CDT) (envelope-from ben@estacado.net)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-websec-strict-transport-sec-11
From: Ben Campbell <ben@estacado.net>
In-Reply-To: <502441B7.8020001@isode.com>
Date: Fri, 10 Aug 2012 09:16:32 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C11651CD-3713-4F2E-9026-E4D7AFF44B31@estacado.net>
References: <50161BD5.7040901@KingsMountain.com> <344AB802-6D45-4399-A628-6852A4732C16@nostrum.com> <502441B7.8020001@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.1485)
Cc: Ben Campbell <ben@nostrum.com>, IETF Discussion List <ietf@ietf.org>, General Area Review Team <gen-art@ietf.org>, IETF WebSec WG <websec@ietf.org>, draft-ietf-websec-strict-transport-sec.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 14:19:17 -0000

Jeff and I had a f2f discussion about this point in Vancouver. To =
paraphrase (and I assume he will correct me if if I mischaracterize =
anything), Jeff indicated that this really wasn't a MUST level =
requirement due to the variation and vagaries in application behavior =
and abilities. Rather, it's more of a "do the best you can" sort of =
thing. Specifically, he indicated that an implementation that chose to =
go ahead and serve unprotected content due to the listed caveats on =
redirecting to HTTPS would necessarily be out-of-compliance.

If the requirement really that you SHOULD NOT (rather than MUST NOT) =
serve unprotected content, then I think the original language is okay.

Thanks!

Ben.

On Aug 9, 2012, at 6:03 PM, Alexey Melnikov <alexey.melnikov@isode.com> =
wrote:

> On 02/08/2012 10:46, Ben Campbell wrote:
>> Hi, thanks for the response.  Comments inline:
>>=20
>> On Jul 29, 2012, at 10:29 PM, =3DJeffH =
<Jeff.Hodges@kingsmountain.com> wrote:
> [...]
>>>> -- section 7.2:
>>>>=20
>>>> Am I correct to assume that the server must never just serve the =
content over
>>>> a non-secure connection? If so, it would be helpful to mention =
that, maybe
>>>> even normatively.
>>> It's a SHOULD, see the Note in that section, so it's already =
effectively stated normatively, though one needs to understand HTTP =
workings to realize it in the way you stated it above.  Perhaps could =
add a simple statement as you suggest to the intro para for section 7 =
Server Processing Model, to address this concern?
>>>=20
>> I think something of the form SHOULD redirect to HTTPS, but MUST NOT =
under any circumstances send the content unprotected would improve the =
text.
>=20
> Sounds good to me. (And yes, this is implied, but it doesn't hurt to =
state explicitly.)
>=20
>> That's probably already implied, and a reasonable implementor =
wouldn't due it anyway. But my experience is that some readers will find =
strange interpretations whenever you give them the wiggle room to do so, =
so it's better to be explicit.
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From hallam@gmail.com  Fri Aug 10 07:26:33 2012
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7278021F8646 for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 07:26:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.562
X-Spam-Level: 
X-Spam-Status: No, score=-5.562 tagged_above=-999 required=5 tests=[AWL=-1.963, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9uBI6h9ZkXLA for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 07:26:32 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8745721F8618 for <ietf@ietf.org>; Fri, 10 Aug 2012 07:26:32 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so2728549obb.31 for <ietf@ietf.org>; Fri, 10 Aug 2012 07:26:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=NEycDPNcDXsus/9OQLvCOwYsBmIBEhiE7172lfEkl9A=; b=XT+FFhxo7WLZleqrbvbAmN5tLTP9r+aebZJrmXq3PzWvjZfeWs3UaztjGlxZwQ3d/J gq9Ayj7PXpY/PM0UtCRKortU9KIr/XB8WTCGHawkKrvrSwRE3aAyyrtR+8BxYQPL2A1n vDtAvtlClVUqvO+Mhb3Bw6d9x4Q+ntHsteSFdYLnHTx0l3h9q2FshXZW2IiK5jPhCf1P sgRFvesWHcKE66DRJc/U1ciKU5gdKybP0UGt2Emk4ujNTJEOlmwTARPTj6QqpzrWzCE5 qN6nNc0RRbjKYdGSTeGfWmKGcDIzvy0+PVKRT0ybGQZJNqCcDSFGuK+gM5QqimhD/pCa sUUw==
MIME-Version: 1.0
Received: by 10.182.207.6 with SMTP id ls6mr4411960obc.36.1344608792001; Fri, 10 Aug 2012 07:26:32 -0700 (PDT)
Received: by 10.76.80.10 with HTTP; Fri, 10 Aug 2012 07:26:31 -0700 (PDT)
In-Reply-To: <m2hasayick.wl%randy@psg.com>
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu> <CAMm+Lwg2HgO-=9ED4vbmO+Vf9r6bYPcLDgfyMAyPdEPVgRm4LQ@mail.gmail.com> <FB949BEA-5BDB-401A-8A75-E9A9BDAA72A6@ripe.net> <20120803182500.1F9512344DBF@drugs.dv.isc.org> <1938E5FD-57DE-4172-834A-55CA1FDAF29A@burkov.aha.ru> <CAMm+Lwhw=XUPKgAJaVeXcQ5mG++hNL9PkmAfqOPyVZo9oi=suQ@mail.gmail.com> <m2vcgs85qn.wl%randy@psg.com> <CAMm+LwjEara+=_BKu7JFsf4Fhbyxr8b6R-hL-QNX0qfXvZLztg@mail.gmail.com> <m2sjbvxwwn.wl%randy@psg.com> <CAMm+Lwi6EBavRdUqsS1YRwr01m31LfZW=LPtMERRwb8NmqbuyQ@mail.gmail.com> <m2hasayick.wl%randy@psg.com>
Date: Fri, 10 Aug 2012 10:26:31 -0400
Message-ID: <CAMm+LwhViaKxRkVapXHiovEQaTkn4e2GVf4eWViBcm9nj-PsuA@mail.gmail.com>
Subject: Re: ITU-T Dubai Meeting
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Randy Bush <randy@psg.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 14:26:33 -0000

On Fri, Aug 10, 2012 at 9:41 AM, Randy Bush <randy@psg.com> wrote:
> hundreds or thousands is perceptually much larger than 100.
>
>> Predicting that institutions will become corrupt over long periods of
>> time is hardly hyperbolic.
>
> the institutions are corrupt now.

Pointing that out right now hardly helps the cause of stopping the
ITU-T getting control of their function.


> as to dnssec, opinions seem to vary widely, and yours is a few sigma
> out.  some think you/verisign stalled it for five years becuase you
> could not commercialize it.  but i really do not care.

I stated the conditions under which deployment would take place in
.net and .com. Had you genuinely believed that I did not intend to
deploy in any case and was merely stalling you should have given me
what I had asked for and put me on the spot.

The reason you pulled the procedural manipulations with the bogus DNS
Directorate review etc. was that you were convinced that VeriSign had
no choice but to deploy.

If it had been my product I would have brought the lawyers in at that
point. A working group chair is not entitled to re-litigate arguments
that they have already lost by referring them to a directorate and
directorates are not permitted to re-litigate working group
discussions.


The fact that you made such a personal intervention on an issue that
you really don't care about speaks volumes.

I find it amazing how often the members of the elder generation pull
the following sililoquy:

1) I do not understand the issues here, therefore nobody can understand them
2) We must be careful not to make mistakes by making decisions we do
not understand
3) Therefore everyone must do it my way as it makes no difference


Difference between you and me is that when I know I don't know
something I either go talk to people who do and find out or I don't
get involved with that issue. You pronounce that nobody understands it
and then demand to be the decision maker.




Website: http://hallambaker.com/

From chair@ietf.org  Fri Aug 10 08:19:38 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60D1821F86A2; Fri, 10 Aug 2012 08:19:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HmwqaznsvAIS; Fri, 10 Aug 2012 08:19:37 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id BD18121F8699; Fri, 10 Aug 2012 08:19:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 9660112CB4C; Fri, 10 Aug 2012 08:19:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8AJyPA6ed+0Z; Fri, 10 Aug 2012 08:19:37 -0700 (PDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) by c8a.amsl.com (Postfix) with ESMTPSA id 27E3812CB58; Fri, 10 Aug 2012 08:19:37 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Subject: Last Call: Modern Global Standards Paradigm
Mime-Version: 1.0 (Apple Message framework v1084)
From: IETF Chair <chair@ietf.org>
Date: Fri, 10 Aug 2012 11:19:34 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: IETF <ietf@ietf.org>, IAB <iab@iab.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 15:19:38 -0000

The IETF Chair and the IAB Chair intend to sign the Affirmation
of the Modern Global Standards Paradigm, which can be found
here:

http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf

An earlier version was discussed in plenary, and the IAB Chair called
for comments on the IETF mail list.  This version includes changes
that address those comments.

Th IETF 84 Administrative plenary minutes have been posted, so that
discussion can be reviewed if desired.  The minutes are here:

http://www.ietf.org/proceedings/84/minutes/minutes-84-iesg-opsplenary

On 8 August 2012, the IEEE Standards Association Board of Governors
approved this version of the document.  The approval process is
underway at the W3C as well.

The IETF Chair and the IAB Chair intend to sign the Affirmation in the
next few weeks. Please send strong objections to the iab@iab.org
and the ietf@ietf.org mailing lists by 2012-08-24.

Thank you,
  Russ Housley
  IETF Chair

From geoff@proto6.com  Thu Aug  9 11:37:43 2012
Return-Path: <geoff@proto6.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F7AF21F8750 for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 11:37:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.45
X-Spam-Level: 
X-Spam-Status: No, score=-102.45 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Odd6OZdBCFRY for <ietf@ietfa.amsl.com>; Thu,  9 Aug 2012 11:37:42 -0700 (PDT)
Received: from mail.coslabs.com (mail.coslabs.com [199.233.92.34]) by ietfa.amsl.com (Postfix) with ESMTP id 927AC21F874F for <ietf@ietf.org>; Thu,  9 Aug 2012 11:37:42 -0700 (PDT)
Received: from [199.233.92.4] (unknown [199.233.92.4]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.coslabs.com (Postfix) with ESMTPSA id E4A0D5F717; Thu,  9 Aug 2012 12:37:37 -0600 (MDT)
Message-ID: <50240374.50608@proto6.com>
Date: Thu, 09 Aug 2012 12:37:40 -0600
From: Geoff Mulligan <geoff@proto6.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: So, where to repeat?
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us>	<5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <5022B4B2.8040904@bbiw.net> <79607D9B-40A1-4EE7-9C1A-B93B492D2802@proto6.com> <5023D21D.7030408@bbiw.net> <6F255DD8-325B-4FA1-AD65-2A75555260FA@checkpoint.com>
In-Reply-To: <6F255DD8-325B-4FA1-AD65-2A75555260FA@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 10 Aug 2012 09:18:58 -0700
Cc: Dave Crocker <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 18:37:43 -0000

On 08/09/2012 09:17 AM, Yoav Nir wrote:
> On Aug 9, 2012, at 6:07 PM, Dave Crocker wrote:
>
>> offlist.
> Not so much
>
>> Geoff,
>>
>> Frankfurt is a city in Germany.  I believe the IETF has never been there.
> Two more tidbits:
>   - It's a huge aviation hub. There are direct flights from everywhere, similar to CDG, Heathrow, or Schiphol
>   - Unlike Paris, London and Amsterdam, it's not a great tourist attraction, so conceivably it would be cheaper.
I've found it relatively inexpensive, clean and very easy to get to.
>
>> Other than those two tidbits about it, I've no idea what is to be
>> accomplished by someone's randomly throwing out the names of cities for
>> a discussion like this, especially when threads like these always have a
>> great deal of trouble staying focused on the /principle/ rather than
>> haggling the details.
> The principle would be to go to aviation hubs so as to minimize the collective pain. Most people from the US going to Prague, would have a connection in Frankfurt, so a meeting in Frankfurt would reduce the amount of flights.
This is why I threw out a "not so random" city name - Frankfurt.
>
> Yoav
>
>> On 8/8/2012 12:24 PM, Geoff Mulligan wrote:
>>> Frankfurt?
>>>
>>>
>>>
>>> On Aug 8, 2012, at 12:49 PM, Dave Crocker <dcrocker@bbiw.net> wrote:
>>>
>>>>
>>>> On 8/8/2012 11:46 AM, Geoff Mulligan wrote:
>>>>> So then why not consider, London, Paris (not the Concorde Lafayette), Frankfurt, Amsterdam?
>>>>
>>>> shockingly, amsterdam can't handle the ietf.  wrong mix of resources. really.
>>>>
>>>> paris appears to have broad crime and work-ethic patterns that also are problematic, not just at the concorde.
>>>>
>>>> to be clear: i'm speaking for myself.
>>>>
>>>> d/
>>>>
>>>> --
>>>> Dave Crocker
>>>> Brandenburg InternetWorking
>>>> bbiw.net
>>>
>> -- 
>>   Dave Crocker
>>   Brandenburg InternetWorking
>>   bbiw.net
>>
>> Scanned by Check Point Total Security Gateway.


From david.black@emc.com  Thu Aug  9 16:05:16 2012
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 432D321F85C7; Thu,  9 Aug 2012 16:05:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.404
X-Spam-Level: 
X-Spam-Status: No, score=-102.404 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qO-dHgqP9ret; Thu,  9 Aug 2012 16:05:15 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 8670521F85C5; Thu,  9 Aug 2012 16:05:15 -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 q79N4nAn028185 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Aug 2012 19:04:50 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Thu, 9 Aug 2012 19:04:40 -0400
Received: from mxhub13.corp.emc.com (mxhub13.corp.emc.com [128.222.70.234]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q79N4eAR021633; Thu, 9 Aug 2012 19:04:40 -0400
Received: from mxhub39.corp.emc.com (128.222.70.106) by mxhub13.corp.emc.com (128.222.70.234) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 9 Aug 2012 19:04:40 -0400
Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub39.corp.emc.com ([128.222.70.106]) with mapi; Thu, 9 Aug 2012 19:04:40 -0400
From: "Black, David" <david.black@emc.com>
To: "michelle.cotton@icann.org" <michelle.cotton@icann.org>, "leo.vegoda@icann.org" <leo.vegoda@icann.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Thu, 9 Aug 2012 19:04:38 -0400
Subject: Gen-ART review of draft-vegoda-cotton-rfc5735bis-02
Thread-Topic: Gen-ART review of draft-vegoda-cotton-rfc5735bis-02
Thread-Index: Ac12g1nlR2o6ek4yS0CffYeN22Tw+A==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71208F1240F@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Fri, 10 Aug 2012 09:18:58 -0700
Cc: "Black, David" <david.black@emc.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 23:05:16 -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 resolve these comments along with any other Last Call comments you m=
ay receive.

Document: draft-vegoda-cotton-rfc5735bis-02
Reviewer: David L. Black
Review Date: August 9, 2012
IETF LC End Date: August 9, 2012

Summary:
This draft is basically ready for publication, but has nits that
should be fixed before publication.

This draft provides an updated list of the special use IPv4 address blocks
that have been allocated by IANA along with explanations of their special
uses.

I found one nit and idnits found another one.

Section 5 - the first sentence in the second paragraph is:

   The domain name and IP address spaces involve policy issues (in
   addition to technical issues) so that the requirements of [RFC2860]
   do not apply generally to those spaces.

I'm surprised by "do not apply generally".  I would have expected that
the policy issues create requirements and constraints above and beyond
the requirements in RFC 2860 as opposed to replacing those requirements.

idnits 2.12.13 complained about a lot of IP addresses that aren't in
the address ranges used for examples.  These complaints can be ignored,
but idnits did find one actual nit:

  =3D=3D Unused Reference: 'RFC6441' is defined on line 346, but no explici=
t
     reference was found in the text

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 david.black@emc.com  Thu Aug  9 16:08:45 2012
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEBD921F85F0; Thu,  9 Aug 2012 16:08:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.482
X-Spam-Level: 
X-Spam-Status: No, score=-102.482 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5rrgaodBTzVD; Thu,  9 Aug 2012 16:08:44 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id BDE6921F85DD; Thu,  9 Aug 2012 16:08:44 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q79N8fCO015783 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Aug 2012 19:08:42 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.226]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Thu, 9 Aug 2012 19:08:21 -0400
Received: from mxhub11.corp.emc.com (mxhub11.corp.emc.com [10.254.92.106]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q79N8Iec010299; Thu, 9 Aug 2012 19:08:18 -0400
Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub11.corp.emc.com ([10.254.92.106]) with mapi; Thu, 9 Aug 2012 19:08:18 -0400
From: "Black, David" <david.black@emc.com>
To: "alan.b.johnston@gmail.com" <alan.b.johnston@gmail.com>, "mohsen.soroush@sylantro.com" <mohsen.soroush@sylantro.com>, "vvenkatar@gmail.com" <vvenkatar@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Thu, 9 Aug 2012 19:08:17 -0400
Subject: Gen-ART review of draft-ietf-bliss-shared-appearances-13
Thread-Topic: Gen-ART review of draft-ietf-bliss-shared-appearances-13
Thread-Index: Ac1Vb8Dn5IHpqMlJQDmiZm9plrtFJQL1mcsgBU9mF9A=
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71208F12410@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71208D3A7FD@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE71208DD8672@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71208DD8672@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Fri, 10 Aug 2012 09:18:58 -0700
Cc: "bliss@ietf.org" <bliss@ietf.org>, "Black, David" <david.black@emc.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 23:08:46 -0000

These resolutions have been carried forward to the -13 version of the draft=
.

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Friday, July 13, 2012 6:25 PM
> To: Black, David; alan.b.johnston@gmail.com; mohsen.soroush@sylantro.com;
> vvenkatar@gmail.com; gen-art@ietf.org
> Cc: Shida Schubert; bliss@ietf.org; IETF Discussion; Robert Sparks
> Subject: Gen-ART review of draft-ietf-bliss-shared-appearances-12
>=20
> The -12 version of this draft resolves all of the comments in the
> Gen-ART review of the -11 version.
>=20
> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: Black, David
> > Sent: Thursday, June 28, 2012 4:51 PM
> > To: alan.b.johnston@gmail.com; mohsen.soroush@sylantro.com;
> > vvenkatar@gmail.com; gen-art@ietf.org
> > Cc: Black, David; Shida Schubert; bliss@ietf.org; IETF Discussion; Robe=
rt
> > Sparks
> > Subject: Gen-ART review of draft-ietf-bliss-shared-appearances-11
> >
> > I am the assigned Gen-ART reviewer for this draft. For background on
> > Gen-ART, please see the FAQ at
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Please resolve these comments along with any other Last Call comments
> > you may receive.
> >
> > Document: draft-ietf-bliss-shared-appearances-11
> > Reviewer: David L. Black
> > Review Date: June 28, 2012
> > IETF LC End Date: June 28, 2012
> > IESG Telechat date: (if known)
> >
> > Summary:
> >
> > This draft is on the right track but has open issues, described in the
> review.
> >
> > This draft describes support for shared appearances in support of multi=
-line
> > and shared-line telephone often found in businesses.  All of the open i=
ssues
> > are minor.  The draft is well-written and reasonably clear for the most
> part,
> > although significant SIP expertise is required to completely understand=
 it.
> >
> > Major issues:  None.
> >
> > Minor issues:
> >
> > 4.1 - REQ-16:
> >
> >    in this case, seizing the line is the same thing as dialing.
> >
> > That seems wrong - I would have thought it was a "prerequisite" as
> > opposed to "the same thing" because seizing the line is immediately
> > followed by a dialing request.
> >
> > 5.3.
> >
> >    A user may select an appearance number but then abandon placing a
> >    call (go back on hook).  In this case, the UA MUST free up the
> >    appearance number by removing the event state with a PUBLISH as
> >    described in [RFC3903].
> >
> > What happens when that can't be done due to UA or network failure?
> >
> > 5.4.
> >
> >    A 400 response is returned if the chosen appearance number is invali=
d,
> >
> > Is that always a 400 (Bad Request) or is any 4xx response allowed?  If
> > it's always 400, add the words "Bad Request" after "400".
> >
> >    If the Appearance Agent policy does not allow this, a 400 response
> >    is returned.
> >
> > Same question.  In addition, is 403 Forbidden allowed here?
> >
> >    If an INVITE is sent by a member of the group to the shared AOR (i.e=
.
> >    they call their own AOR), the Appearance Agent MUST assign two
> >    appearance numbers.  The first appearance number will be the one
> >    selected or assigned to the outgoing INVITE.  The second appearance
> >    number will be another one assigned by the Appearance Agent for the
> >    INVITE as it is forked back to the members of the group.
> >
> > How does that interact with the single appearance UAs in 8.1.1 that won=
't
> > understand the second appearance number?  A warning that such a UA can'=
t
> > pick up its call to its own AOR would suffice, either here or in 8.1.1.
> >
> > 9.1
> >
> >    A UA that has no knowledge of appearances must will only have
> >    appearance numbers for outgoing calls if assigned by the Appearance
> >    Agent.  If the non-shared appearance UA does not support Join or
> >    Replaces, all dialogs could be marked "exclusive" to indicate that
> >    these options are not available.
> >
> > Should that "could be marked" be changed to "SHOULD be marked" ?
> > Also, analogous questions for "could" in 9.2 and "can" in 9.3.
> >
> > All three of these affect interoperability.
> >
> > 12. Security Considerations
> >
> > In general, this section is weak on rationale - the second, third and
> > fourth paragraphs should all explain more about the purpose of and/or
> > rationale for their security requirements (e.g., what does the security
> > mechanism protect against and when/why might that protection be desired
> > and/or required?).
> >
> >    NOTIFY or PUBLISH message bodies that provide the dialog state
> >    information and the dialog identifiers MAY be encrypted end-to-end
> >    using the standard mechanisms.
> >
> > What are "the standard mechanisms"?  List them, and provide references,
> > please.
> >
> > Please ensure that the section 6 XML and Section 7 ABNF are
> > syntax-checked with actual tools.
> >
> > Nits/editorial comments:
> >
> > p.10:
> >
> >    The next section discusses the operations used to implement parts of
> >    the shared appearance feature.
> >
> > "The following list describes the operations ..." would be better.
> >
> > 5.3.1.
> >
> >    A UA wanting to place a call but not have an appearance number
> >    assigned publishes before sending the INVITE without an 'appearance'
> >    element but with the 'shared' event package parameter present.
> >
> > I think I understand what was intended here, but this would be clearer
> > if "publishes" was replaced with language about sending a PUBLISH.
> > It's also not completely clear whether "without" applies to the
> > INVITE or the PUBLISH, so this sentence probably needs to be reworded.
> >
> > 5.4. - Expand B2BUA acronym on first use.
> >
> > idnits 2.12.13 ran clean.
> >
> > Thanks,
> > --David
> > ----------------------------------------------------
> > David L. Black, Distinguished Engineer
> > EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> > +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293=
-7786
> > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> > ----------------------------------------------------


From david.black@emc.com  Thu Aug  9 16:17:09 2012
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D7CB21F8618; Thu,  9 Aug 2012 16:17:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.482
X-Spam-Level: 
X-Spam-Status: No, score=-102.482 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OlD9v+UKxFbo; Thu,  9 Aug 2012 16:17:08 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 6404321F8617; Thu,  9 Aug 2012 16:17:08 -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 q79NH6xJ022805 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Aug 2012 19:17:07 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Thu, 9 Aug 2012 19:16:55 -0400
Received: from mxhub29.corp.emc.com (mxhub29.corp.emc.com [128.222.70.169]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q79NGsAE030948; Thu, 9 Aug 2012 19:16:54 -0400
Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub29.corp.emc.com ([128.222.70.169]) with mapi; Thu, 9 Aug 2012 19:16:54 -0400
From: "Black, David" <david.black@emc.com>
To: "James M. Polk" <jmpolk@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 9 Aug 2012 19:16:53 -0400
Subject: Gen-ART review of draft-polk-local-emergency-rph-namespace-02
Thread-Topic: Gen-ART review of draft-polk-local-emergency-rph-namespace-02
Thread-Index: AcxA9hUNwavoqEelQfeUxmCy5d9fy01jouJA
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71208F12412@MX15A.corp.emc.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E058941360C@MX14A.corp.emc.com>
In-Reply-To: <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: Fri, 10 Aug 2012 09:18:58 -0700
Cc: "Black, David" <david.black@emc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 23:17:09 -0000

The nits in the Gen-ART review of the -01 version of this draft
have not been addressed in the -02 version.

idnits found one existing nit and one new one:

  =3D=3D It seems as if not all pages are separated by form feeds - found 0=
 form
     feeds but 8 pages

  =3D=3D Line 156 has weird spacing: '...n, this  is a ...'

Thanks,
--David


> -----Original Message-----
> From: Black, David
> Sent: Tuesday, July 12, 2011 8:45 PM
> To: James M. Polk; gen-art@ietf.org; ietf@ietf.org
> Cc: Black, David; Robert Sparks
> Subject: Gen-ART review of draft-polk-local-emergency-rph-namespace-01
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on Gen-=
ART,
> please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments you=
 may
> receive.
>=20
> Document: draft-polk-local-emergency-rph-namespace-01
> Reviewer: David L. Black
> Review Date: July 12, 2011
> IETF LC End Date: July 13, 2011
>=20
> Summary:
> This draft is basically ready for publication, but has nits that should b=
e
> fixed before publication.
>=20
> This draft defines a SIP Resource Priority header namespace, "esnet", for=
 use
> in
> providing preferential treatment to emergency calls (e.g., from on-scene
> responders).
>=20
> This field is an addition to rather than a replacement for existing notio=
ns of
> priority in the SIP Resource Priority header.  Section 2 explains why thi=
s was
> done, but section 2 is a bit sloppy and imprecise.  Some level of impreci=
sion
> is
> necessary as this draft deliberately does not specify how this header
> namespace
> is used to provide preferential treatment.  Nonetheless, the following tw=
o
> items
> could be improved in Section 2's discussion:
>=20
> 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=
 the
> 	esnet namespace is to override the ordinary priorities found elsewhere
> in
> 	the Resource Priority header.
>=20
> Small nit: There's an extraneous "to" in the first line of section 3:
>=20
>    The "esnet" namespace should not to be considered generic for all
>                                     ^^
>=20
> idnits 2.12.12 found a few formatting problems:
>=20
>   =3D=3D You're using the IETF Trust Provisions' Section 6.b License Noti=
ce from
>      12 Sep 2009 rather than the newer Notice from 28 Dec 2009.  (See
>      http://trustee.ietf.org/license-info/)
>=20
>   =3D=3D It seems as if not all pages are separated by form feeds - found=
 0 form
>      feeds but 7 pages
>=20
>   =3D=3D The copyright year in the IETF Trust and authors Copyright Line =
does not
>      match the current year
>=20
>=20
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------


From Ruediger.Geib@telekom.de  Thu Aug  9 23:33:47 2012
Return-Path: <Ruediger.Geib@telekom.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 49E0221F8628; Thu,  9 Aug 2012 23:33:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FemgKRFRRT7N; Thu,  9 Aug 2012 23:33:46 -0700 (PDT)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [194.25.30.7]) by ietfa.amsl.com (Postfix) with ESMTP id 953A921F8621; Thu,  9 Aug 2012 23:33:42 -0700 (PDT)
Received: from he113656.emea1.cds.t-internal.com ([10.134.99.16]) by tcmail31.telekom.de with ESMTP/TLS/AES128-SHA; 10 Aug 2012 08:33:40 +0200
Received: from HE111648.emea1.cds.t-internal.com ([10.134.93.17]) by HE113656.emea1.cds.t-internal.com ([::1]) with mapi; Fri, 10 Aug 2012 08:33:40 +0200
From: <Ruediger.Geib@telekom.de>
To: <matt@internet2.edu>
Date: Fri, 10 Aug 2012 08:33:39 +0200
Subject: RE: [ippm] Fwd: Liaison Statement from the Broadband Forum
Thread-Topic: [ippm] Fwd: Liaison Statement from the Broadband Forum
Thread-Index: Ac12ivfeUwStqsPCSreOgERWfwQNCAANZygg
Message-ID: <580BEA5E3B99744AB1F5BFF5E9A3C67D14DD77A228@HE111648.emea1.cds.t-internal.com>
References: <13205C286662DE4387D9AF3AC30EF456D771989330@EMBX01-WF.jnpr.net> <50244EBF.7010709@internet2.edu>
In-Reply-To: <50244EBF.7010709@internet2.edu>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 10 Aug 2012 09:18:58 -0700
Cc: ietf@ietf.org, ippm@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 06:33:47 -0000

Matt,

I've read the liaision statement. The BBF informs us, that
they plan to "create a standard set of Broadband performance metrics
to address on-going regulatory, and consumer performance information
needs."

BBF asks for guidance and support. From the document I couldn't
identify the architecture. I personally think IPPM members may
volunteer to suggest IETF metrics to BBF. But to me that requires
that the architecture is clearly defined (by BBF).

Regards,

Ruediger


-----Original Message-----
From: ippm-bounces@ietf.org [mailto:ippm-bounces@ietf.org] On Behalf Of Mat=
thew J Zekauskas
Sent: Friday, August 10, 2012 1:59 AM
To: IETF IPPM WG
Subject: [ippm] Fwd: Liaison Statement from the Broadband Forum

FYI, if folks here want to review.  Ron wants comments to ietf@ietf.org.

--Matt

-------------------

Folks,

The Broadband Forum has sent a liaison statement to the IETF regarding a "N=
ew Project - Broadband Access Service Attributes and Performance Measures".

Click on the following link for details: https://datatracker.ietf.org/liais=
on/1179/.

Please review and send comments to this list.

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

From mcr@sandelman.ca  Fri Aug 10 06:57:47 2012
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 AA70921F85DB for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 06:57:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.352
X-Spam-Level: 
X-Spam-Status: No, score=-2.352 tagged_above=-999 required=5 tests=[AWL=0.248,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SjMBU89awDdU for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 06:57:47 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 37DFE21F85D9 for <ietf@ietf.org>; Fri, 10 Aug 2012 06:57:47 -0700 (PDT)
Received: from obiwan.sandelman.ca (unknown [IPv6:2607:f0b0:f:2:3a60:77ff:fe38:e647]) by tuna.sandelman.ca (Postfix) with ESMTP id F1C6F20289 for <ietf@ietf.org>; Fri, 10 Aug 2012 10:10:40 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: ietf@ietf.org
Subject: Re: ITU-T Dubai Meeting
In-Reply-To: <CAMm+Lwhw=XUPKgAJaVeXcQ5mG++hNL9PkmAfqOPyVZo9oi=suQ@mail.gmail.com>
References: <20120802184436.87A0318C11F@mercury.lcs.mit.edu> <CAMm+Lwg2HgO-=9ED4vbmO+Vf9r6bYPcLDgfyMAyPdEPVgRm4LQ@mail.gmail.com> <FB949BEA-5BDB-401A-8A75-E9A9BDAA72A6@ripe.net> <20120803182500.1F9512344DBF@drugs.dv.isc.org> <1938E5FD-57DE-4172-834A-55CA1FDAF29A@burkov.aha.ru> <CAMm+Lwhw=XUPKgAJaVeXcQ5mG++hNL9PkmAfqOPyVZo9oi=suQ@mail.gmail.com>
X-Mailer: MH-E 8.3; nmh 1.5; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
Date: Fri, 10 Aug 2012 09:57:39 -0400
Message-ID: <640.1344607059@obiwan.sandelman.ca>
X-Mailman-Approved-At: Fri, 10 Aug 2012 09:18:58 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 13:57:47 -0000

>>>>> "Phillip" == Phillip Hallam-Baker <hallam@gmail.com> writes:
    Phillip> Allocating a /16 for national RIRs independent of IANA and
    Phillip> the US

Can we give them ULA-C space? ;-)

From mcr@sandelman.ca  Fri Aug 10 08:36:40 2012
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 8D38721F8789 for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 08:36:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.414
X-Spam-Level: 
X-Spam-Status: No, score=-2.414 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UVd3LoQdCD5J for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 08:36:37 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 75BF021F8625 for <ietf@ietf.org>; Fri, 10 Aug 2012 08:36:33 -0700 (PDT)
Received: from obiwan.sandelman.ca (unknown [IPv6:2607:f0b0:f:2:3a60:77ff:fe38:e647]) by tuna.sandelman.ca (Postfix) with ESMTP id 0C4AB2028E for <ietf@ietf.org>; Fri, 10 Aug 2012 11:49:27 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: So, where to repeat? (was: Re: management granularity)
In-Reply-To: <alpine.OSX.2.01.1208090818130.31054@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <alpine.OSX.2.01.1208081204190.24762@173-11-110-132-sfba.hfc.comcastbusiness.net> <15ECE2E3-1086-413D-A7AD-C42AA2D4D020@proto6.com> <alpine.OSX.2.01.1208090818130.31054@173-11-110-132-sfba.hfc.comcastbusiness.net>
X-Mailer: MH-E 8.3; nmh 1.5; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
Date: Fri, 10 Aug 2012 11:36:25 -0400
Message-ID: <18214.1344612985@obiwan.sandelman.ca>
X-Mailman-Approved-At: Fri, 10 Aug 2012 09:18:58 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 15:36:40 -0000

>>>>> "Ole" == Ole Jacobsen <ole@cisco.com> writes:
    Ole> On Wed, 8 Aug 2012, Geoff Mulligan wrote:

    >> So I'm confused...  We're we talking about the possibility of 
    >> sticking to one European city, one north American city and one Asian 
    >> city and not picking various cities throughout the world.

    Ole> Oh, I see. My reading was that we would focus on small number of 
    Ole> cities in each region, especially since we cannot depend on ONE
    Ole> being always available for our dates, host and sponsorship 
    Ole> notwithstanding.

I understood what Ole did.
I think that over a decade, the small number would go from ~7 to perhaps
2 in each region.  That's because we'd wind up signing multi-year
contracts with hotels that we liked. (which is, I understand, why we
repeated in Minneapolis)



From tbray@textuality.com  Fri Aug 10 09:30:03 2012
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4914C21F8569 for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 09:30:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.982
X-Spam-Level: 
X-Spam-Status: No, score=-4.982 tagged_above=-999 required=5 tests=[AWL=-2.005, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id szalT2xccSTs for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 09:30:02 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 71ECD21F8568 for <ietf@ietf.org>; Fri, 10 Aug 2012 09:30:02 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so1846099vbb.31 for <ietf@ietf.org>; Fri, 10 Aug 2012 09:30:02 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=rj/8HsrDzxWxftIzyxG+SHoUZoDH5/aXkx3cg6W5ViQ=; b=CrtHPn4uh7dBcSDGnfw+VPdu2s16gTKOtOUSvkz8REDV8n3f+yvMXlmtJK/CJM0B/w BrEvJt7sBZqa3nCM2C9XLnp81hEXMrIu9o8sWg+EiTS2zn7qfrqJpr7praxUc3nviOLY ecRPZ0SRPnCthiq5ejl6PGjX2ADDE/kVNtOvaVyS7L1ndxNbquyyp/FP9TjYbYV97mGi orlOHWG+mTcE5BNy3GyWUvWnBZfdKedbbY2k1nWMe2+BAUEgy9AxTsieM2rvHcSZ/3k1 lkjrnyRY23oyoEgEHJUlEgLCReCq5j0XSll7NiqL5OKMj3tG/l+IWA64hp4v4v/gAGce gPSg==
MIME-Version: 1.0
Received: by 10.220.142.79 with SMTP id p15mr117943vcu.24.1344616201918; Fri, 10 Aug 2012 09:30:01 -0700 (PDT)
Received: by 10.52.113.162 with HTTP; Fri, 10 Aug 2012 09:30:01 -0700 (PDT)
X-Originating-IP: [24.84.208.217]
In-Reply-To: <50240374.50608@proto6.com>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <5022B4B2.8040904@bbiw.net> <79607D9B-40A1-4EE7-9C1A-B93B492D2802@proto6.com> <5023D21D.7030408@bbiw.net> <6F255DD8-325B-4FA1-AD65-2A75555260FA@checkpoint.com> <50240374.50608@proto6.com>
Date: Fri, 10 Aug 2012 09:30:01 -0700
Message-ID: <CAHBU6ivSPYhetW4nj7gb3gZN3yTZxeomYM9-Ffr2C5zs7rZVAg@mail.gmail.com>
Subject: Re: So, where to repeat?
From: Tim Bray <tbray@textuality.com>
To: Geoff Mulligan <geoff@proto6.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQkhOmbHUXdQ8MBqO1Ov/Hynt2hR8+sbvWY67IcWghlLpp12F60v86A2Lk86d3Ahy430k4JB
Cc: Dave Crocker <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 16:30:03 -0000

Frankfurt as the Minneapolis of Europe: central, well-connected, cold,
unglamorous.  -T

On Thu, Aug 9, 2012 at 11:37 AM, Geoff Mulligan <geoff@proto6.com> wrote:
>
> On 08/09/2012 09:17 AM, Yoav Nir wrote:
>>
>> On Aug 9, 2012, at 6:07 PM, Dave Crocker wrote:
>>
>>> offlist.
>>
>> Not so much
>>
>>> Geoff,
>>>
>>> Frankfurt is a city in Germany.  I believe the IETF has never been there.
>>
>> Two more tidbits:
>>   - It's a huge aviation hub. There are direct flights from everywhere,
>> similar to CDG, Heathrow, or Schiphol
>>   - Unlike Paris, London and Amsterdam, it's not a great tourist
>> attraction, so conceivably it would be cheaper.
>
> I've found it relatively inexpensive, clean and very easy to get to.
>>
>>
>>> Other than those two tidbits about it, I've no idea what is to be
>>> accomplished by someone's randomly throwing out the names of cities for
>>> a discussion like this, especially when threads like these always have a
>>> great deal of trouble staying focused on the /principle/ rather than
>>> haggling the details.
>>
>> The principle would be to go to aviation hubs so as to minimize the
>> collective pain. Most people from the US going to Prague, would have a
>> connection in Frankfurt, so a meeting in Frankfurt would reduce the amount
>> of flights.
>
> This is why I threw out a "not so random" city name - Frankfurt.
>>
>>
>> Yoav
>>
>>> On 8/8/2012 12:24 PM, Geoff Mulligan wrote:
>>>>
>>>> Frankfurt?
>>>>
>>>>
>>>>
>>>> On Aug 8, 2012, at 12:49 PM, Dave Crocker <dcrocker@bbiw.net> wrote:
>>>>
>>>>>
>>>>> On 8/8/2012 11:46 AM, Geoff Mulligan wrote:
>>>>>>
>>>>>> So then why not consider, London, Paris (not the Concorde Lafayette),
>>>>>> Frankfurt, Amsterdam?
>>>>>
>>>>>
>>>>> shockingly, amsterdam can't handle the ietf.  wrong mix of resources.
>>>>> really.
>>>>>
>>>>> paris appears to have broad crime and work-ethic patterns that also are
>>>>> problematic, not just at the concorde.
>>>>>
>>>>> to be clear: i'm speaking for myself.
>>>>>
>>>>> d/
>>>>>
>>>>> --
>>>>> Dave Crocker
>>>>> Brandenburg InternetWorking
>>>>> bbiw.net
>>>>
>>>>
>>> --
>>>   Dave Crocker
>>>   Brandenburg InternetWorking
>>>   bbiw.net
>>>
>>> Scanned by Check Point Total Security Gateway.
>
>

From sm@resistor.net  Fri Aug 10 09:33:15 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A133621F86C5; Fri, 10 Aug 2012 09:33:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level: 
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UKMn9kCV6NtH; Fri, 10 Aug 2012 09:33: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 A5D8821F869A; Fri, 10 Aug 2012 09:33:11 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q7AGX6pT025456; Fri, 10 Aug 2012 09:33:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1344616390; bh=XE2k/qlrLBnIewDnj6Yow2Sd9UsBOGZ2HskM8eALlWQ=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=Bfe7RBYXblcAdOYl74Qx+E/MyRk3Dcoe6qwpJEOVI5FF2j0Vq6f4XL/Db5F5C64IP TFcBX8UNxRPLBRPs8MB9udKsUjtPEvcxm8TTAE26xdv7+gGLEnZYOprDeNWnyRin3z kJjnJ5mXJIxPbIYeEYWJkG1r7hp3qVzVmNxOTvw4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1344616390; i=@resistor.net; bh=XE2k/qlrLBnIewDnj6Yow2Sd9UsBOGZ2HskM8eALlWQ=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=pC1c73TzeFygpDmZ2hEKMWixOtP6JmekMwBzKTModSBIyfONZ0WGdAqetcJ5uQ1Ex txfhpcJ6vqVQIWQL+3TGdwOghWN2hss/yHIfLRPA8/SEMJ9x3oI+iP2/+Ny9Fi9wbp PItowUCjdL0F3SvijAGfuYxXkLfoWMe+FtvyXD6k=
Message-Id: <6.2.5.6.2.20120810084356.088ef9c0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 10 Aug 2012 09:31:33 -0700
To: IETF <ietf@ietf.org>, IAB <iab@iab.org>
From: SM <sm@resistor.net>
Subject: Re: Last Call: Modern Global Standards Paradigm
In-Reply-To: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 16:33:15 -0000

At 08:19 10-08-2012, IETF Chair wrote:
>The IETF Chair and the IAB Chair intend to sign the Affirmation
>of the Modern Global Standards Paradigm, which can be found
>here:
>
>http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf

[snip]

>The IETF Chair and the IAB Chair intend to sign the Affirmation in the
>next few weeks. Please send strong objections to the iab@iab.org
>and the ietf@ietf.org mailing lists by 2012-08-24.

"Collective empowerment" sounds like a marketing term.  "contribute 
to the creation of global communities, benefiting humanity" does not 
sound like something the IETF would say as it comes out as hollow words.

Regards,
-sm



From ole@cisco.com  Fri Aug 10 09:33:45 2012
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E490221F86D0 for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 09:33:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.58
X-Spam-Level: 
X-Spam-Status: No, score=-110.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mhR+a7ugCuAq for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 09:33:45 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 2B58921F86C9 for <ietf@ietf.org>; Fri, 10 Aug 2012 09:33:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=489; q=dns/txt; s=iport; t=1344616425; x=1345826025; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=6WoXvB687T/XQy4UgiwUVd3PwafmbwGWx5yPAq0YJxM=; b=YeHsCVQYTkJFhSZOomwfHcuKiIOHz6R7YXPCHjbWUY2Ri3I3N7rGXajH wCnD4BxLdfm0456ECfzvO7CevOS7ufoVS8zMuxvcQGwUElj040mxDpet+ fXs4NQ4D6otPIt7LVWQnj0LSvqhhD4QNoHt6Ar7JUoNDkR3Wr3eEHIGZ8 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAIzgI1CQ/khL/2dsb2JhbABFuWKBB4IgAQEBAwESAQIlPwULCw44VwY1h2UGmwaDSBCdFYsPhmQDiE6SV4hNgQRign8
X-IronPort-AV: E=Sophos;i="4.77,745,1336348800";  d="scan'208";a="7255211"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-3.cisco.com with ESMTP; 10 Aug 2012 16:33:44 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q7AGXfk1003388 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Aug 2012 16:33:43 GMT
Date: Fri, 10 Aug 2012 09:33:40 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Tim Bray <tbray@textuality.com>
Subject: Re: So, where to repeat?
In-Reply-To: <CAHBU6ivSPYhetW4nj7gb3gZN3yTZxeomYM9-Ffr2C5zs7rZVAg@mail.gmail.com>
Message-ID: <alpine.OSX.2.01.1208100930520.58056@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <5022B4B2.8040904@bbiw.net> <79607D9B-40A1-4EE7-9C1A-B93B492D2802@proto6.com> <5023D21D.7030408@bbiw.net> <6F255DD8-325B-4FA1-AD65-2A75555260FA@checkpoint.com> <50240374.50608@proto6.com> <CAHBU6ivSPYhetW4nj7gb3gZN3yTZxeomYM9-Ffr2C5zs7rZVAg@mail.gmail.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: Geoff Mulligan <geoff@proto6.com>, Dave Crocker <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 16:33:46 -0000

On Fri, 10 Aug 2012, Tim Bray wrote:

> Frankfurt as the Minneapolis of Europe: central, well-connected, cold,
> unglamorous.  -T

Plus expensive and generally unsuitable for a meeting such as ours, 
until the day Bit's and Bites turns into a 200,000 square foot 
tradeshow, just kidding! :-)

I agree with the well-connected, it's my "main gateway" to Europe
these days, especially because of the great train service, getting
to Amsterdam for example is very easy.


Ole



From hallam@gmail.com  Fri Aug 10 09:49:18 2012
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EECF21F87A9; Fri, 10 Aug 2012 09:49:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.546
X-Spam-Level: 
X-Spam-Status: No, score=-5.546 tagged_above=-999 required=5 tests=[AWL=-1.947, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Szq-ZQoJXLj2; Fri, 10 Aug 2012 09:49:17 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 78FA421F873E; Fri, 10 Aug 2012 09:49:17 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so2898387obb.31 for <multiple recipients>; Fri, 10 Aug 2012 09:49:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Xqe3MDPILtmqMapSeSIG3YWqFiUhd9MJvQXQGE1jXvM=; b=GDMrJClnMT4yhkXJk585Ja4u5rQ+Z2AoMLu0V05P5w+fxWihvUoRiVMcuIqR7zAlOt Yu23RWda9Gr29VW0q8O+/4iYtzMPKDFK+mICGufKzdWQ6vfix9N3rxTVIR7gH93gdkEu fkdz/R7B86ulgjgGmrcGPZCLRPoQfokExYLplPmlJaS9Q8Iq28qQt0YlmnyYmF4cWGsx hU31pT3ZQ/JxKS++qDyAB6gG57r/Wpi0BtvTjpb0qFRNV15COyZAyHv0h5+B4mCpjV+J keQqqnylHl2XoeHBaXvtMog1WlzHFinZshwg1srdmddzUV3pbTKhnJNhBNcDntCoSRCb /hGQ==
MIME-Version: 1.0
Received: by 10.182.89.102 with SMTP id bn6mr5106923obb.7.1344617357097; Fri, 10 Aug 2012 09:49:17 -0700 (PDT)
Received: by 10.76.80.10 with HTTP; Fri, 10 Aug 2012 09:49:17 -0700 (PDT)
In-Reply-To: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org>
Date: Fri, 10 Aug 2012 12:49:17 -0400
Message-ID: <CAMm+Lwio8=EyW-=LZE8BA4=6N=H4f7a1Nycg25LxB920ceZ6JA@mail.gmail.com>
Subject: Re: Last Call: Modern Global Standards Paradigm
From: Phillip Hallam-Baker <hallam@gmail.com>
To: IETF <ietf@ietf.org>, IAB <iab@iab.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 16:49:18 -0000

I think the point needs to be made that standards organizations can
only advise and not dictate.

There is really no risk that ITU-T is going to end up in control of
the technical standards that are implemented by the likes of
Microsoft, Cisco or Google, let alone Apache, Mozilla and the folk on
SourceForge and Github.

The key defect in the ITU-T view of the world is that it is populated
by people who think that they are making decisions that matter. In
practice deciding telephone system standards right now is about as
important as the next revision of the FORTRAN standard, it is not
completely irrelevant but matters a lot more to the people in the
meetings than anyone else.

The strength of the IETF negotiating position comes from the fact that
we cannot dictate terms to anyone. The consensus that matters is not
just consensus among the people developing the specification document
but consensus among the people who are expected to act on it.

ITU-T can certainly set themselves up a Friendship Games if they like
[1]. But they can't force people to show up, let alone implement their
'requirements'.

>From a censorship busting point of view, the best thing that can
happen for us is for the states attempting to gain control of the net
in their country to attempt to standardize their approach. Much easier
to circumvent fixed blocks than the current moving target.


[1] http://en.wikipedia.org/wiki/Friendship_Games


On Fri, Aug 10, 2012 at 11:19 AM, IETF Chair <chair@ietf.org> wrote:
>
> The IETF Chair and the IAB Chair intend to sign the Affirmation
> of the Modern Global Standards Paradigm, which can be found
> here:
>
> http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf
>
> An earlier version was discussed in plenary, and the IAB Chair called
> for comments on the IETF mail list.  This version includes changes
> that address those comments.
>
> Th IETF 84 Administrative plenary minutes have been posted, so that
> discussion can be reviewed if desired.  The minutes are here:
>
> http://www.ietf.org/proceedings/84/minutes/minutes-84-iesg-opsplenary
>
> On 8 August 2012, the IEEE Standards Association Board of Governors
> approved this version of the document.  The approval process is
> underway at the W3C as well.
>
> The IETF Chair and the IAB Chair intend to sign the Affirmation in the
> next few weeks. Please send strong objections to the iab@iab.org
> and the ietf@ietf.org mailing lists by 2012-08-24.
>
> Thank you,
>   Russ Housley
>   IETF Chair



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

From agmalis@gmail.com  Fri Aug 10 10:23:13 2012
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A38A21F8746 for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 10:23:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.308
X-Spam-Level: 
X-Spam-Status: No, score=-3.308 tagged_above=-999 required=5 tests=[AWL=0.291,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wuliS4oYG-gu for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 10:23:13 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id D3A9921F8723 for <ietf@ietf.org>; Fri, 10 Aug 2012 10:23:12 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so1991736ghb.31 for <ietf@ietf.org>; Fri, 10 Aug 2012 10:23:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=X5dYUUqI4Hbv3/wzw1CacIp8wQITetJV+c0LgtMgZE0=; b=ZM/vv/pvoNmJ5b6gk3t3bKxh+FHHwNhyAujqINkzl0e/Lj/w+zaJO2xU4GmrgZlNOc oEfJc+xBJIJuZYR+bfMOwPoQyHrdYDWp6O9WfymQniI1z9WF54RI6uoMj+t9jUsPZ84d CGCdWAhVpQfD+wFa1Q5VrMmqBeKQXMNJY42KB1P/0mNWg2ROrQmnh2pQ/z1fWObS6N/C RYZ+xONAnHqKDUmWYtHI17LJUR6ylUwJj9bJZvfPjq244wbh4hKSUxRSsU1F3elZSXv1 1if5KP3OJxKMpLF1uJQbOU0B92dTLjReQL6L9j3tYy0WvBkws3Qh0W9mE87i6EWuIvJf S7EA==
Received: by 10.50.184.227 with SMTP id ex3mr2501223igc.26.1344619392158; Fri, 10 Aug 2012 10:23:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.124.70 with HTTP; Fri, 10 Aug 2012 10:22:51 -0700 (PDT)
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A0C08@DC-US1MBEX4.global.avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B22726A0C08@DC-US1MBEX4.global.avaya.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Fri, 10 Aug 2012 13:22:51 -0400
Message-ID: <CAA=duU0_L9PUdJdFYzmQgpKSpCxcpiBfYE8Tj50+UQpyuLF6vA@mail.gmail.com>
Subject: Re: ITU-T Dubai Meeting and IPv15
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 17:23:13 -0000

A 260-bit address should be sufficient to address every atom in the
universe, according to current estimates (10^78 atoms). We go there
next (plus some extra to add hierarchy), and we'll never have to worry
about addressing again.

Another alternative is self-describing variable-length addresses,
again do it once and we'll never have to worry about it again.

Cheers,
Andy

On Thu, Aug 9, 2012 at 12:45 PM, Worley, Dale R (Dale)
<dworley@avaya.com> wrote:
>> From: Phillip Hallam-Baker [hallam@gmail.com]
>>
>> As Tom Knight pointed out when the IPv4 address size was chosen, there
>> aren't enough for one for each person living on the planet.
>>
>> Remember that we are trying to build a network that is going to last
>> for hundreds if not thousands of years.
>
> Technology changes over time, and so the optimal design tradeoffs
> change over time.  When IPv4 was designed, memory, processing power,
> and transmission capacity were far more expensive than now.  Moore's
> Law suggests a factor of 2^15 between 1982 and 2012.  Before that was
> the ARPAnet, with 8 bit addresses, which lasted for around 15 years.
> Presumably IPv6 will suffice for at least another 30 years.
>
> The real issue regarding longevity is that total network overhauls
> should be infrequent enough that their amortized costs are well less
> than ongoing operational costs.  Once that has been achieved, the cost
> savings of designing a protocol with a longer usable lifetime is
> probably not worth the effort of trying to predict the future well
> enough to achieve longer lifetime.
>
> Extrapolating a 30-year lifetime for each IP version suggests that in
> 300 years we will reach the end of the usable life of IPv15 and will have
> to allocate more bits to the "version" field at the beginning of
> packets.  That'll be a mess...
>
> Dale

From jnc@mercury.lcs.mit.edu  Fri Aug 10 10:30:47 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33C1421F85F0 for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 10:30:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.317
X-Spam-Level: 
X-Spam-Status: No, score=-6.317 tagged_above=-999 required=5 tests=[AWL=0.282,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3aXKRY3reqnf for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 10:30: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 8977221F85E6 for <ietf@ietf.org>; Fri, 10 Aug 2012 10:30:46 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 8D9FE18C127; Fri, 10 Aug 2012 13:30:45 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: ITU-T Dubai Meeting and IPv15
Message-Id: <20120810173045.8D9FE18C127@mercury.lcs.mit.edu>
Date: Fri, 10 Aug 2012 13:30:45 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 17:30:47 -0000

    > From: "Andrew G. Malis" <agmalis@gmail.com>

    > 260-bit address should be sufficient to [s]address[/s] _name_ every
    > atom in the universe

YPIF.

	Noel
h

From drc@virtualized.org  Fri Aug 10 10:35:56 2012
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 33F8421F8508 for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 10:35:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ggOX6ONlW49A for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 10:35:55 -0700 (PDT)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id BF83321F8507 for <ietf@ietf.org>; Fri, 10 Aug 2012 10:35:55 -0700 (PDT)
Received: from [10.0.1.8] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: drc) by trantor.virtualized.org (Postfix) with ESMTPSA id 1BA8B1705A; Fri, 10 Aug 2012 17:35:54 +0000 (UTC)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: ITU-T Dubai Meeting and IPv15
From: David Conrad <drc@virtualized.org>
In-Reply-To: <CAA=duU0_L9PUdJdFYzmQgpKSpCxcpiBfYE8Tj50+UQpyuLF6vA@mail.gmail.com>
Date: Fri, 10 Aug 2012 10:35:53 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C2796AD0-6361-4EE0-B97B-5443D685215F@virtualized.org>
References: <CD5674C3CD99574EBA7432465FC13C1B22726A0C08@DC-US1MBEX4.global.avaya.com> <CAA=duU0_L9PUdJdFYzmQgpKSpCxcpiBfYE8Tj50+UQpyuLF6vA@mail.gmail.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
X-Mailer: Apple Mail (2.1485)
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 17:35:56 -0000

On Aug 10, 2012, at 10:22 AM, "Andrew G. Malis" <agmalis@gmail.com> =
wrote:
> Another alternative is self-describing variable-length addresses,
> again do it once and we'll never have to worry about it again.

Heretic!  That's OSI speak!  Why do you hate the Internet you ISO/ITU =
lackey?!?

</flashback>

Yeah, variable-length addresses would have been nice. There was even =
working code. Maybe next IPng.

Regards,
-drc


From richard@shockey.us  Fri Aug 10 12:01:36 2012
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 7ACD611E8072 for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 12:01:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.91
X-Spam-Level: 
X-Spam-Status: No, score=-100.91 tagged_above=-999 required=5 tests=[AWL=1.355, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MF30q8+k1cl7 for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 12:01:35 -0700 (PDT)
Received: from oproxy7-pub.bluehost.com (oproxy7-pub.bluehost.com [67.222.55.9]) by ietfa.amsl.com (Postfix) with SMTP id CB19521F841E for <ietf@ietf.org>; Fri, 10 Aug 2012 12:01:35 -0700 (PDT)
Received: (qmail 2638 invoked by uid 0); 10 Aug 2012 19:01:12 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy7.bluehost.com with SMTP; 10 Aug 2012 19:01:12 -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:To:From; bh=GjM7yhnLzh+gWB0AY+xIKAO8BuzD3dS1YBOm32RB0RQ=;  b=eB2Viet0D4uY+8vme5UqfKCVAewVkw2bSTztfgLoihJLc8W5Qt3Hbb6sdr1HSTNs1DeK2zIkQ1s/eeimL2ygI3hwaPCf6e4tXTeSPb/wrsgfamjb4rMTkjCV1sHmaDeQ;
Received: from [71.191.243.130] (port=62399 helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.76) (envelope-from <richard@shockey.us>) id 1SzuSO-0006zD-BS for ietf@ietf.org; Fri, 10 Aug 2012 13:01:12 -0600
From: "Richard Shockey" <richard@shockey.us>
To: <ietf@ietf.org>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com>	<502169E9.9020009@dcrocker.net>	<AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk>	<EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk>	<39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com>	<01af01cd74f5$217e5770$647b0650$@us>	<5021CDDE.8060207@dcrocker.net>	<alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net>	<B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com>	<5022B4B2.8040904@bbiw.net>	<79607D9B-40A1-4EE7-9C1A-B93B492D2802@proto6.com>	<5023D21D.7030408@bbiw.net>	<6F255DD8-325B-4FA1-AD65-2A75555260FA@checkpoint.com>	<50240374.50608@proto6.com> <CAHBU6ivSPYhetW4nj7gb3gZN3yTZxeomYM9-Ffr2C5zs7rZVAg@mail.gmail.com>
In-Reply-To: <CAHBU6ivSPYhetW4nj7gb3gZN3yTZxeomYM9-Ffr2C5zs7rZVAg@mail.gmail.com>
Subject: RE: So, where to repeat?
Date: Fri, 10 Aug 2012 15:01:09 -0400
Message-ID: <00a801cd772a$818c26b0$84a47410$@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: Ac13FWXT64yIWvY3R1SFcT/NcDhDrwAE/XDA
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 71.191.243.130 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: Fri, 10 Aug 2012 19:01:36 -0000

Minneapolis is infinitely more glamorous Frankfurt .. 

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Tim
Bray
Sent: Friday, August 10, 2012 12:30 PM
To: Geoff Mulligan
Cc: Dave Crocker; ietf@ietf.org
Subject: Re: So, where to repeat?

Frankfurt as the Minneapolis of Europe: central, well-connected, cold,
unglamorous.  -T

On Thu, Aug 9, 2012 at 11:37 AM, Geoff Mulligan <geoff@proto6.com> wrote:
>
> On 08/09/2012 09:17 AM, Yoav Nir wrote:
>>
>> On Aug 9, 2012, at 6:07 PM, Dave Crocker wrote:
>>
>>> offlist.
>>
>> Not so much
>>
>>> Geoff,
>>>
>>> Frankfurt is a city in Germany.  I believe the IETF has never been
there.
>>
>> Two more tidbits:
>>   - It's a huge aviation hub. There are direct flights from 
>> everywhere, similar to CDG, Heathrow, or Schiphol
>>   - Unlike Paris, London and Amsterdam, it's not a great tourist 
>> attraction, so conceivably it would be cheaper.
>
> I've found it relatively inexpensive, clean and very easy to get to.
>>
>>
>>> Other than those two tidbits about it, I've no idea what is to be 
>>> accomplished by someone's randomly throwing out the names of cities 
>>> for a discussion like this, especially when threads like these 
>>> always have a great deal of trouble staying focused on the 
>>> /principle/ rather than haggling the details.
>>
>> The principle would be to go to aviation hubs so as to minimize the 
>> collective pain. Most people from the US going to Prague, would have 
>> a connection in Frankfurt, so a meeting in Frankfurt would reduce the 
>> amount of flights.
>
> This is why I threw out a "not so random" city name - Frankfurt.
>>
>>
>> Yoav
>>
>>> On 8/8/2012 12:24 PM, Geoff Mulligan wrote:
>>>>
>>>> Frankfurt?
>>>>
>>>>
>>>>
>>>> On Aug 8, 2012, at 12:49 PM, Dave Crocker <dcrocker@bbiw.net> wrote:
>>>>
>>>>>
>>>>> On 8/8/2012 11:46 AM, Geoff Mulligan wrote:
>>>>>>
>>>>>> So then why not consider, London, Paris (not the Concorde 
>>>>>> Lafayette), Frankfurt, Amsterdam?
>>>>>
>>>>>
>>>>> shockingly, amsterdam can't handle the ietf.  wrong mix of resources.
>>>>> really.
>>>>>
>>>>> paris appears to have broad crime and work-ethic patterns that 
>>>>> also are problematic, not just at the concorde.
>>>>>
>>>>> to be clear: i'm speaking for myself.
>>>>>
>>>>> d/
>>>>>
>>>>> --
>>>>> Dave Crocker
>>>>> Brandenburg InternetWorking
>>>>> bbiw.net
>>>>
>>>>
>>> --
>>>   Dave Crocker
>>>   Brandenburg InternetWorking
>>>   bbiw.net
>>>
>>> Scanned by Check Point Total Security Gateway.
>
>


From ben@nostrum.com  Fri Aug 10 12:31:17 2012
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2264121F8666; Fri, 10 Aug 2012 12:31:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.45
X-Spam-Level: 
X-Spam-Status: No, score=-101.45 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_LIST=2.3, SPF_PASS=-0.001,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id boZ-YnG8a-Mp; Fri, 10 Aug 2012 12:31:16 -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 D346C21F865E; Fri, 10 Aug 2012 12:31:15 -0700 (PDT)
Received: from [10.12.11.64] ([4.30.77.1]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q7AJVD13036521 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 10 Aug 2012 14:31:15 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART LC Review of draft-ietf-mptcp-api-05
Date: Fri, 10 Aug 2012 14:31:11 -0500
Message-Id: <CCBAA297-B839-4AEA-BB24-F4D320200415@nostrum.com>
To: draft-ietf-mptcp-api.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
X-Mailer: Apple Mail (2.1485)
Received-SPF: pass (nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Cc: General Area Review Team <gen-art@ietf.org>, IETF Discussion List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 19:31:17 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq> .

Please resolve these comments along with any other Last Call comments
you may receive.

Document:  draft-ietf-mptcp-api-05

Reviewer: Ben Campbell
Review Date: 2012-08-10
IETF LC End Date: 2012-08-14

Summary: This draft is almost ready for publication, but I have =
questions about its intended informational status.

Major issues: None

Minor issues:

-- Section 5 specifies an abstract "basic" API for MPTCP. The draft =
characterizes this as an extension to the sockets API. On it's face, =
this sounds like it's creating a standard, or will at least have the =
effect of creating a standard. Is that the intent? If so, I wonder why =
the intended status is informational rather than standards track? If =
not, it would be useful to explicitly state the intent. (For example, is =
this intended as an input to inform a standardization effort?)

I realize that the sockets API is not an IETF standard. I don't know if =
that is part of the reason for making this draft informational, nor am I =
familiar with precedent for extending non-IETF-native standards. But at =
the risk of attacking a straw man, I am concerned that putting something =
that could be interpreted as a "standard" in an informational RFC might =
not be the best practice for solving that sort of process issue.


-- It seems like at least passing knowledge of the sockets API is needed =
to understand this document. I'm curious why the POSIX reference is =
informational rather than normative?

Nits/editorial comments:

-- 3.3.1, 1st paragraph: "This will provide greater bandwidth for an =
application. "

I assume this means "as great or greater", given the previous statements =
that MPTCP should be at worst no worse than normal TCP?

-- 3.2.1, 1st paragraph: "...while having TCP SYN/ACK ready to reply =
to..."

I had to think about this a while to figure out the meaning. Perhaps it =
could be rephrased?=

From ynir@checkpoint.com  Fri Aug 10 13:19:45 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3652121F869F for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 13:19:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.398
X-Spam-Level: 
X-Spam-Status: No, score=-10.398 tagged_above=-999 required=5 tests=[AWL=0.201, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hkjBxds7Q7XT for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 13:19:44 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 21F7E21F868A for <ietf@ietf.org>; Fri, 10 Aug 2012 13:19:43 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id q7AKJe1N027562; Fri, 10 Aug 2012 23:19:41 +0300
X-CheckPoint: {502569DC-0-1B221DC2-4FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Fri, 10 Aug 2012 23:19:40 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Richard Shockey <richard@shockey.us>
Date: Fri, 10 Aug 2012 23:19:39 +0300
Subject: Re: So, where to repeat?
Thread-Topic: So, where to repeat?
Thread-Index: Ac13NXg7XINKZ9GbQQShoNUojAiCbg==
Message-ID: <E252936B-074A-4B13-B2B2-D12329D2F8AE@checkpoint.com>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us>	<5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <5022B4B2.8040904@bbiw.net> <79607D9B-40A1-4EE7-9C1A-B93B492D2802@proto6.com> <5023D21D.7030408@bbiw.net> <6F255DD8-325B-4FA1-AD65-2A75555260FA@checkpoint.com> <50240374.50608@proto6.com> <CAHBU6ivSPYhetW4nj7gb3gZN3yTZxeomYM9-Ffr2C5zs7rZVAg@mail.gmail.com> <00a801cd772a$818c26b0$84a47410$@us>
In-Reply-To: <00a801cd772a$818c26b0$84a47410$@us>
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@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 20:19:45 -0000

The tourist website www.minneapolis.org uses the slogan "City by Nature".=20

I think "An infinitely more glamorous Frankfurt" would be an improvement.
.

On Aug 10, 2012, at 10:01 PM, Richard Shockey wrote:

> Minneapolis is infinitely more glamorous Frankfurt ..=20
>=20
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of T=
im
> Bray
> Sent: Friday, August 10, 2012 12:30 PM
> To: Geoff Mulligan
> Cc: Dave Crocker; ietf@ietf.org
> Subject: Re: So, where to repeat?
>=20
> Frankfurt as the Minneapolis of Europe: central, well-connected, cold,
> unglamorous.  -T


From joelja@bogus.com  Fri Aug 10 13:58:25 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24ADD21F85C0 for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 13:58:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.45
X-Spam-Level: 
X-Spam-Status: No, score=-102.45 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EAE4GueIwdnx for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 13:58:24 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 749FE21F85BB for <ietf@ietf.org>; Fri, 10 Aug 2012 13:58:24 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q7AKwJ82093037 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 10 Aug 2012 20:58:20 GMT (envelope-from joelja@bogus.com)
Message-ID: <502575E6.5010802@bogus.com>
Date: Fri, 10 Aug 2012 13:58:14 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120731 Thunderbird/15.0
MIME-Version: 1.0
To: Tim Bray <tbray@textuality.com>
Subject: Re: So, where to repeat?
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com> <502169E9.9020009@dcrocker.net> <AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk> <39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com> <01af01cd74f5$217e5770$647b0650$@us> <5021CDDE.8060207@dcrocker.net> <alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net> <B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com> <5022B4B2.8040904@bbiw.net> <79607D9B-40A1-4EE7-9C1A-B93B492D2802@proto6.com> <5023D21D.7030408@bbiw.net> <6F255DD8-325B-4FA1-AD65-2A75555260FA@checkpoint.com> <50240374.50608@proto6.com> <CAHBU6ivSPYhetW4nj7gb3gZN3yTZxeomYM9-Ffr2C5zs7rZVAg@mail.gmail.com>
In-Reply-To: <CAHBU6ivSPYhetW4nj7gb3gZN3yTZxeomYM9-Ffr2C5zs7rZVAg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 10 Aug 2012 20:58:20 +0000 (UTC)
Cc: Geoff Mulligan <geoff@proto6.com>, Dave Crocker <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 20:58:25 -0000

On 8/10/12 9:30 AM, Tim Bray wrote:
> Frankfurt as the Minneapolis of Europe: central, well-connected, cold,
> unglamorous.  -T
Also home of the ECB and the Bundesbank which shows when you try to book 
a large event into the big hotels near the hauptbahnhof.

"The why have we not met in this large city which I think is more 
appropriate then some of our others choices" aspect of this thrice 
annual discussion seems a bit played out.
> On Thu, Aug 9, 2012 at 11:37 AM, Geoff Mulligan <geoff@proto6.com> wrote:
>> On 08/09/2012 09:17 AM, Yoav Nir wrote:
>>> On Aug 9, 2012, at 6:07 PM, Dave Crocker wrote:
>>>
>>>> offlist.
>>> Not so much
>>>
>>>> Geoff,
>>>>
>>>> Frankfurt is a city in Germany.  I believe the IETF has never been there.
>>> Two more tidbits:
>>>    - It's a huge aviation hub. There are direct flights from everywhere,
>>> similar to CDG, Heathrow, or Schiphol
>>>    - Unlike Paris, London and Amsterdam, it's not a great tourist
>>> attraction, so conceivably it would be cheaper.
>> I've found it relatively inexpensive, clean and very easy to get to.
>>>
>>>> Other than those two tidbits about it, I've no idea what is to be
>>>> accomplished by someone's randomly throwing out the names of cities for
>>>> a discussion like this, especially when threads like these always have a
>>>> great deal of trouble staying focused on the /principle/ rather than
>>>> haggling the details.
>>> The principle would be to go to aviation hubs so as to minimize the
>>> collective pain. Most people from the US going to Prague, would have a
>>> connection in Frankfurt, so a meeting in Frankfurt would reduce the amount
>>> of flights.
>> This is why I threw out a "not so random" city name - Frankfurt.
>>>
>>> Yoav
>>>
>>>> On 8/8/2012 12:24 PM, Geoff Mulligan wrote:
>>>>> Frankfurt?
>>>>>
>>>>>
>>>>>
>>>>> On Aug 8, 2012, at 12:49 PM, Dave Crocker <dcrocker@bbiw.net> wrote:
>>>>>
>>>>>> On 8/8/2012 11:46 AM, Geoff Mulligan wrote:
>>>>>>> So then why not consider, London, Paris (not the Concorde Lafayette),
>>>>>>> Frankfurt, Amsterdam?
>>>>>>
>>>>>> shockingly, amsterdam can't handle the ietf.  wrong mix of resources.
>>>>>> really.
>>>>>>
>>>>>> paris appears to have broad crime and work-ethic patterns that also are
>>>>>> problematic, not just at the concorde.
>>>>>>
>>>>>> to be clear: i'm speaking for myself.
>>>>>>
>>>>>> d/
>>>>>>
>>>>>> --
>>>>>> Dave Crocker
>>>>>> Brandenburg InternetWorking
>>>>>> bbiw.net
>>>>>
>>>> --
>>>>    Dave Crocker
>>>>    Brandenburg InternetWorking
>>>>    bbiw.net
>>>>
>>>> Scanned by Check Point Total Security Gateway.
>>


From Jeff.Hodges@KingsMountain.com  Fri Aug 10 14:34:20 2012
Return-Path: <Jeff.Hodges@KingsMountain.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B0C121F8625 for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 14:34:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.633
X-Spam-Level: 
X-Spam-Status: No, score=-100.633 tagged_above=-999 required=5 tests=[AWL=1.632, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qOADO9LZ4oMz for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 14:34:20 -0700 (PDT)
Received: from oproxy6-pub.bluehost.com (oproxy6-pub.bluehost.com [67.222.54.6]) by ietfa.amsl.com (Postfix) with SMTP id F09F721F8564 for <ietf@ietf.org>; Fri, 10 Aug 2012 14:34:19 -0700 (PDT)
Received: (qmail 23990 invoked by uid 0); 10 Aug 2012 21:33:58 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by cpoproxy3.bluehost.com with SMTP; 10 Aug 2012 21:33:58 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kingsmountain.com; s=default;  h=Content-Transfer-Encoding:Content-Type:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=zQ42lv4nJ35pqAeoI1DBK7QuzkWuO0maehLqEdWcNw4=;  b=nP7T9HTdfxO9PV1OTuC7BwjLaByYiMHmmqcpWPoSCFT+jwlIiE5BqcKI9hkfVMcVRuPJ3wEKYorwfWULZSHCIfKDfdtB7Ypex/bymket+MziQjEpFNwgTfP/43MTahNx;
Received: from [24.4.122.173] (port=41385 helo=[192.168.11.12]) by box514.bluehost.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1SzwqC-0001Ci-He; Fri, 10 Aug 2012 15:33:56 -0600
Message-ID: <50257E43.8010005@KingsMountain.com>
Date: Fri, 10 Aug 2012 14:33:55 -0700
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>,  Tobias Gondrom <tobias.gondrom@gondrom.org>, Ben Campbell <ben@nostrum.com>
Subject: Re: Gen-ART LC Review of draft-ietf-websec-strict-transport-sec-11
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 24.4.122.173 authed with jeff.hodges+kingsmountain.com}
Cc: General Area Review Team <gen-art@ietf.org>, IETF WebSec WG <websec@ietf.org>, draft-ietf-websec-strict-transport-sec.all@tools.ietf.org, IETF Discussion List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 21:34:20 -0000

Thanks Ben.

 > Jeff and I had a f2f discussion about this point in Vancouver. To paraphrase
 > (and I assume he will correct me if if I mischaracterize anything), Jeff
 > indicated that this really wasn't a MUST level requirement due to the
 > variation and vagaries in application behavior and abilities.

Yes, see the NOTE in section 7.2.

 > Rather, it's
 > more of a "do the best you can" sort of thing. Specifically, he indicated
 > that an implementation that chose to go ahead and serve unprotected content
 > due to the listed caveats on redirecting to HTTPS would necessarily be
 > out-of-compliance.

I presume you actually mean "not necessarily", which would then be correct, 
unless I'm misunderstanding something.


 > If the requirement really that you SHOULD NOT (rather than MUST NOT) serve
 > unprotected content, then I think the original language is okay.

agreed.

thanks,

=JeffH



From adrian@olddog.co.uk  Fri Aug 10 14:38:15 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF3CC21F8648; Fri, 10 Aug 2012 14:38:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.484
X-Spam-Level: 
X-Spam-Status: No, score=-2.484 tagged_above=-999 required=5 tests=[AWL=0.115,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tC8twUBjEV2p; Fri, 10 Aug 2012 14:38:14 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id EDC1721F8646; Fri, 10 Aug 2012 14:38:13 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7ALcCfb017052;  Fri, 10 Aug 2012 22:38:12 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7ALcAEl017044 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 10 Aug 2012 22:38:11 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'IETF'" <ietf@ietf.org>, "'IAB'" <iab@iab.org>, "'IETF-Announce'" <ietf-announce@ietf.org>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org>
In-Reply-To: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org>
Subject: RE: Last Call: Modern Global Standards Paradigm
Date: Fri, 10 Aug 2012 22:38:08 +0100
Message-ID: <06a601cd7740$6fb704d0$4f250e70$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKADG0ZlSPzGQd8wC2Lw99G+a7b45XuZvoA
Content-Language: en-gb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 21:38:15 -0000

Hi Russ,

I am conscious that this text needs to have the consensus of the three groups
planning to co-sign, and we also need consensus of the IETF community that you
sign it.

Given the first of these, I think the question you ask is "Are there strong
objections?" not "Could we wordsmith this so we would be happier with it?"

Had you asked the second question, I would have been first in line (actually, I
already sent my thoughts a couple of weeks ago). But I agree there is no scope
for that at this stage.

Since you asked the other question: No, I have no strong objection, and I
support this statement being signed by you and the IAB chair.

Thanks,
Adrian

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of IETF Chair
> Sent: 10 August 2012 16:20
> To: IETF-Announce
> Cc: IAB; IETF
> Subject: Last Call: Modern Global Standards Paradigm
> 
> 
> The IETF Chair and the IAB Chair intend to sign the Affirmation
> of the Modern Global Standards Paradigm, which can be found
> here:
> 
> http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf
> 
> An earlier version was discussed in plenary, and the IAB Chair called
> for comments on the IETF mail list.  This version includes changes
> that address those comments.
> 
> Th IETF 84 Administrative plenary minutes have been posted, so that
> discussion can be reviewed if desired.  The minutes are here:
> 
> http://www.ietf.org/proceedings/84/minutes/minutes-84-iesg-opsplenary
> 
> On 8 August 2012, the IEEE Standards Association Board of Governors
> approved this version of the document.  The approval process is
> underway at the W3C as well.
> 
> The IETF Chair and the IAB Chair intend to sign the Affirmation in the
> next few weeks. Please send strong objections to the iab@iab.org
> and the ietf@ietf.org mailing lists by 2012-08-24.
> 
> Thank you,
>   Russ Housley
>   IETF Chair


From ben@estacado.net  Fri Aug 10 14:58:38 2012
Return-Path: <ben@estacado.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E60221F865E; Fri, 10 Aug 2012 14:58:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v1bz59dq3Dy9; Fri, 10 Aug 2012 14:58:37 -0700 (PDT)
Received: from estacado.net (vicuna.estacado.net [4.30.77.35]) by ietfa.amsl.com (Postfix) with ESMTP id 69D6221F865C; Fri, 10 Aug 2012 14:58:36 -0700 (PDT)
Received: from [10.12.11.64] ([10.12.11.64]) (authenticated bits=0) by estacado.net (8.14.3/8.14.3) with ESMTP id q7ALttiU010516 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 10 Aug 2012 16:55:55 -0500 (CDT) (envelope-from ben@estacado.net)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-websec-strict-transport-sec-11
From: Ben Campbell <ben@estacado.net>
In-Reply-To: <50257E43.8010005@KingsMountain.com>
Date: Fri, 10 Aug 2012 16:55:47 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <570BD336-2C91-4C7E-AC03-9FD5423AEB35@estacado.net>
References: <50257E43.8010005@KingsMountain.com>
To: =JeffH <Jeff.Hodges@kingsmountain.com>
X-Mailer: Apple Mail (2.1485)
Cc: Ben Campbell <ben@nostrum.com>, IETF Discussion List <ietf@ietf.org>, General Area Review Team <gen-art@ietf.org>, IETF WebSec WG <websec@ietf.org>, Alexey Melnikov <alexey.melnikov@isode.com>, draft-ietf-websec-strict-transport-sec.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 21:58:38 -0000

On Aug 10, 2012, at 4:33 PM, =3DJeffH <Jeff.Hodges@kingsmountain.com> =
wrote:

> Thanks Ben.
>=20
> > Jeff and I had a f2f discussion about this point in Vancouver. To =
paraphrase
> > (and I assume he will correct me if if I mischaracterize anything), =
Jeff
> > indicated that this really wasn't a MUST level requirement due to =
the
> > variation and vagaries in application behavior and abilities.
>=20
> Yes, see the NOTE in section 7.2.
>=20
> > Rather, it's
> > more of a "do the best you can" sort of thing. Specifically, he =
indicated
> > that an implementation that chose to go ahead and serve unprotected =
content
> > due to the listed caveats on redirecting to HTTPS would necessarily =
be
> > out-of-compliance.
>=20
> I presume you actually mean "not necessarily", which would then be =
correct, unless I'm misunderstanding something.

Oops, you are correct, that's a typo.

>=20
>=20
> > If the requirement really that you SHOULD NOT (rather than MUST NOT) =
serve
> > unprotected content, then I think the original language is okay.
>=20
> agreed.
>=20
> thanks,
>=20
> =3DJeffH
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From richard@shockey.us  Fri Aug 10 15:32:43 2012
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 0AE2B11E80CC for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 15:32:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.201
X-Spam-Level: 
X-Spam-Status: No, score=-101.201 tagged_above=-999 required=5 tests=[AWL=1.398, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8VKo1VLxIegQ for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 15:32:41 -0700 (PDT)
Received: from oproxy12-pub.bluehost.com (oproxy12-pub.bluehost.com [50.87.16.10]) by ietfa.amsl.com (Postfix) with SMTP id 5F35911E80AD for <ietf@ietf.org>; Fri, 10 Aug 2012 15:32:41 -0700 (PDT)
Received: (qmail 11240 invoked by uid 0); 10 Aug 2012 22:32:20 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy12.bluehost.com with SMTP; 10 Aug 2012 22:32:19 -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=zc6wY1tormgDN9iudMchOs86eylZtJanS/dqq8fusdo=;  b=aPpk6H+rxT8sYt216cn1dBZSyy69wOdBZhGl9/kxU4B7GEL/d/a7/oDS5++id7kvk66VtxBdROcLQQxaILc6JsPRK5815EJuhGJMhHNaaFqJ2/hY7Kau9GmtbinKhLeJ;
Received: from [71.191.243.130] (port=51889 helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.76) (envelope-from <richard@shockey.us>) id 1Szxkh-0007Ef-Af; Fri, 10 Aug 2012 16:32:19 -0600
From: "Richard Shockey" <richard@shockey.us>
To: "'Yoav Nir'" <ynir@checkpoint.com>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF2834A0516@PACDCEXMB01.cable.comcast.com>	<502169E9.9020009@dcrocker.net>	<AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk>	<EMEW3|0ebd669a4eccc2cca00daf1beb84ed50o76MuX03tjc|ecs.soton.ac.uk|AC30AAA7-8634-4851-86CC-6F64095BB600@ecs.soton.ac.uk>	<39C56E09-72AD-4C99-9A62-3992DEF04D70@shinkuro.com>	<01af01cd74f5$217e5770$647b0650$@us>	<5021CDDE.8060207@dcrocker.net>	<alpine.OSX.2.01.1208071937500.20339@173-11-110-132-sfba.hfc.comcastbusiness.net>	<B33DB90A-5819-4CEE-AE99-DAEC5CC5425C@proto6.com>	<5022B4B2.8040904@bbiw.net>	<79607D9B-40A1-4EE7-9C1A-B93B492D2802@proto6.com>	<5023D21D.7030408@bbiw.net>	<6F255DD8-325B-4FA1-AD65-2A75555260FA@checkpoint.com>	<50240374.50608@proto6.com>	<CAHBU6ivSPYhetW4nj7gb3gZN3yTZxeomYM9-Ffr2C5zs7rZVAg@mail.gmail.com>	<00a801cd772a$818c26b0$84a47410$@us> <E252936B-074A-4B13-B2B2-D12329D2F8AE@checkpoint.com>
In-Reply-To: <E252936B-074A-4B13-B2B2-D12329D2F8AE@checkpoint.com>
Subject: RE: So, where to repeat?
Date: Fri, 10 Aug 2012 18:32:16 -0400
Message-ID: <00d901cd7747$ff9ec130$fedc4390$@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: Ac13NXg7XINKZ9GbQQShoNUojAiCbgAESTBg
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 71.191.243.130 authed with richard@shockey.us}
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 22:32:43 -0000

The tourist website www.minneapolis.org uses the slogan "City by Nature". 

I think "An infinitely more glamorous Frankfurt" would be an improvement.

[RS> ] If you prefer a globally dysfunctional airport and a city run by
bankers ..then yes its potentially more 'glamorous'.  Granted they do have a
world class Christmas Market in season.  If you want the center of Europe ..
Munchen. You could think about Berlin but then you have a totally non
existent disfunctional airport.  Wait a few years out and you can rethink
Washington DC. A totally functional 5 runway international airport .. a full
metro rail from the airport to the city and all of Washington's many
nonexistent charms. 

.

On Aug 10, 2012, at 10:01 PM, Richard Shockey wrote:

> Minneapolis is infinitely more glamorous Frankfurt .. 
> 
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf 
> Of Tim Bray
> Sent: Friday, August 10, 2012 12:30 PM
> To: Geoff Mulligan
> Cc: Dave Crocker; ietf@ietf.org
> Subject: Re: So, where to repeat?
> 
> Frankfurt as the Minneapolis of Europe: central, well-connected, cold, 
> unglamorous.  -T


From bob.hinden@gmail.com  Fri Aug 10 15:55:51 2012
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A649911E80A6 for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 15:55:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.518
X-Spam-Level: 
X-Spam-Status: No, score=-103.518 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JGISDAyXpums for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 15:55:51 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1EFE211E8087 for <ietf@ietf.org>; Fri, 10 Aug 2012 15:55:51 -0700 (PDT)
Received: by pbbrr4 with SMTP id rr4so3411957pbb.31 for <ietf@ietf.org>; Fri, 10 Aug 2012 15:55:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=5L+5CfimMN0ID3G/MRnRpf6ElvdFF+vMxZv0WB3IBjY=; b=gWNO2seYpGQyaB+ob9vflcmr8oQD58uOuIcfPOtF75+BYoX3teiX7TKEtJkcnzJCT9 zN5zNVOsgyK2/0hUPlNsqg/HopMHmVl4UCJpg2x05k5t7cDNrNFV1GCybtxyzMVlHv9X z3KNgSv8isdiSQ26lwKAHs0umb1vdswx5erAHUQY73ggy2nmH6vckWsy1MlL+85DiWYV eam3+3iU1WreiwEjM5+YCbH84e/xwCyIY8I7BsDfdC3qz+ITMsnOGO/C8IalrZ2eAuVj x47BZfiw7DqV44FtcDc00FP7pssxwsXtoj+JTt2/w3aGD4mq3c6g/F7aNpBWg3/CtHHX bhlw==
Received: by 10.68.213.137 with SMTP id ns9mr400046pbc.88.1344639350929; Fri, 10 Aug 2012 15:55:50 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPS id hx9sm110998pbc.68.2012.08.10.15.55.46 (version=SSLv3 cipher=OTHER); Fri, 10 Aug 2012 15:55:50 -0700 (PDT)
Subject: Re: Last Call: Modern Global Standards Paradigm
Mime-Version: 1.0 (Apple Message framework v1280)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org>
Date: Fri, 10 Aug 2012 15:55:45 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <8393C34B-3BD4-4453-A315-74D93E971260@gmail.com>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org>
To: IETF <ietf@ietf.org>, IAB <iab@iab.org>
X-Mailer: Apple Mail (2.1280)
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, 10 Aug 2012 22:55:51 -0000

I support the IETF and IAB chairs signing document.

Bob

On Aug 10, 2012, at 8:19 AM, IETF Chair wrote:

> 
> The IETF Chair and the IAB Chair intend to sign the Affirmation
> of the Modern Global Standards Paradigm, which can be found
> here:
> 
> http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf
> 
> An earlier version was discussed in plenary, and the IAB Chair called
> for comments on the IETF mail list.  This version includes changes
> that address those comments.
> 
> Th IETF 84 Administrative plenary minutes have been posted, so that
> discussion can be reviewed if desired.  The minutes are here:
> 
> http://www.ietf.org/proceedings/84/minutes/minutes-84-iesg-opsplenary
> 
> On 8 August 2012, the IEEE Standards Association Board of Governors
> approved this version of the document.  The approval process is
> underway at the W3C as well.
> 
> The IETF Chair and the IAB Chair intend to sign the Affirmation in the
> next few weeks. Please send strong objections to the iab@iab.org
> and the ietf@ietf.org mailing lists by 2012-08-24.
> 
> Thank you,
>  Russ Housley
>  IETF Chair


From eburger@standardstrack.com  Fri Aug 10 18:19:59 2012
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E80211E809B for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 18:19:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gh+Xh6Q-cpSH for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 18:19:58 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.215.15]) by ietfa.amsl.com (Postfix) with ESMTP id 2208821F851B for <ietf@ietf.org>; Fri, 10 Aug 2012 18:19:58 -0700 (PDT)
Received: from [206.191.100.2] (port=53754 helo=[172.17.114.11]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1T00Mt-00017L-Jl; Fri, 10 Aug 2012 18:19:55 -0700
Subject: Re: Last Call: Modern Global Standards Paradigm
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-88--887724103"
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <CAMm+Lwio8=EyW-=LZE8BA4=6N=H4f7a1Nycg25LxB920ceZ6JA@mail.gmail.com>
Date: Fri, 10 Aug 2012 15:52:59 -0700
Message-Id: <1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.com>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <CAMm+Lwio8=EyW-=LZE8BA4=6N=H4f7a1Nycg25LxB920ceZ6JA@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Transfer-Encoding: 7bit
X-Pgp-Agent: GPGMail 1.3.3
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: IAB <iab@iab.org>, IETF list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 01:19:59 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--Apple-Mail-88--887724103
Content-Type: multipart/signed; boundary=Apple-Mail-87--887724113; protocol="application/pkcs7-signature"; micalg=sha1


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

PLEASE, PLEASE, PLEASE read what the proposal is. The proposal being put =
forth is not that the ITU-T wants to write Internet standards. The =
proposal being put forth is that ONLY ITU-T standards will be the =
*legal* standards accepted by signatory nations.

At best, this would be a repeat of GOSIP in the U.S., where the law was =
the U.S. government could only buy OSI products. The issue there was the =
private sector was still free to buy what it wanted and DoD did not =
really follow the rules and bought TCP/IP instead. TCP/IP in the market =
killed OSI.

The difference here is some countries may take their ITR obligations =
literally and ban products that use non-ITU protocols. Could one go to =
jail for using TCP/IP or HTTP? That has an admittedly small, but not =
insignificant possibility of happening. Worse yet, having treaties that =
obligates countries to ban non-ITU protocols does virtually guarantee a =
balkanization of the Internet into open and free networking and =
controlled and censored networking.

Just as it is not fair to say that if the ITU-T gets its way the world =
will end, it is also not fair to say there is no risk to allowing the =
ITU-T to get a privileged, NON-VOLUNTARY, position in the communications =
world.

On Aug 10, 2012, at 9:49 AM, Phillip Hallam-Baker wrote:

> I think the point needs to be made that standards organizations can
> only advise and not dictate.
>=20
> There is really no risk that ITU-T is going to end up in control of
> the technical standards that are implemented by the likes of
> Microsoft, Cisco or Google, let alone Apache, Mozilla and the folk on
> SourceForge and Github.
>=20
> The key defect in the ITU-T view of the world is that it is populated
> by people who think that they are making decisions that matter. In
> practice deciding telephone system standards right now is about as
> important as the next revision of the FORTRAN standard, it is not
> completely irrelevant but matters a lot more to the people in the
> meetings than anyone else.
>=20
> The strength of the IETF negotiating position comes from the fact that
> we cannot dictate terms to anyone. The consensus that matters is not
> just consensus among the people developing the specification document
> but consensus among the people who are expected to act on it.
>=20
> ITU-T can certainly set themselves up a Friendship Games if they like
> [1]. But they can't force people to show up, let alone implement their
> 'requirements'.
>=20
> =46rom a censorship busting point of view, the best thing that can
> happen for us is for the states attempting to gain control of the net
> in their country to attempt to standardize their approach. Much easier
> to circumvent fixed blocks than the current moving target.
>=20
>=20
> [1] http://en.wikipedia.org/wiki/Friendship_Games
>=20
>=20
> On Fri, Aug 10, 2012 at 11:19 AM, IETF Chair <chair@ietf.org> wrote:
>>=20
>> The IETF Chair and the IAB Chair intend to sign the Affirmation
>> of the Modern Global Standards Paradigm, which can be found
>> here:
>>=20
>> =
http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf=

>>=20
>> An earlier version was discussed in plenary, and the IAB Chair called
>> for comments on the IETF mail list.  This version includes changes
>> that address those comments.
>>=20
>> Th IETF 84 Administrative plenary minutes have been posted, so that
>> discussion can be reviewed if desired.  The minutes are here:
>>=20
>> http://www.ietf.org/proceedings/84/minutes/minutes-84-iesg-opsplenary
>>=20
>> On 8 August 2012, the IEEE Standards Association Board of Governors
>> approved this version of the document.  The approval process is
>> underway at the W3C as well.
>>=20
>> The IETF Chair and the IAB Chair intend to sign the Affirmation in =
the
>> next few weeks. Please send strong objections to the iab@iab.org
>> and the ietf@ietf.org mailing lists by 2012-08-24.
>>=20
>> Thank you,
>>  Russ Housley
>>  IETF Chair
>=20
>=20
>=20
> --=20
> Website: http://hallambaker.com/


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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIPODCCBN0w
ggPFoAMCAQICEHGS++YZX6xNEoV0cTSiGKcwDQYJKoZIhvcNAQEFBQAwezELMAkGA1UEBhMCR0Ix
GzAZBgNVBAgMEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBwwHU2FsZm9yZDEaMBgGA1UECgwR
Q29tb2RvIENBIExpbWl0ZWQxITAfBgNVBAMMGEFBQSBDZXJ0aWZpY2F0ZSBTZXJ2aWNlczAeFw0w
NDAxMDEwMDAwMDBaFw0yODEyMzEyMzU5NTlaMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMCVVQx
FzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsx
ITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVROLVVTRVJGaXJz
dC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAsjmFpPJ9q0E7YkY3rs3BYHW8OWX5ShpHornMSMxqmNVNNRm5pELlzkniii8efNIx
B8dOtINknS4p1aJkxIW9hVE1eaROaJB7HHqkkqgX8pgV8pPMyaQylbsMTzC9mKALi+VuG6JG+ni8
om+rWV6lL8/K2m2qL+usobNqqrcuZzWLeeEeaYji5kbNoKXqvgvOdjp6Dpvq/NonWz1zHyLmSGHG
TPNpsaguG7bUMSAsvIKKjqQOpdeJQ/wWWq8dcdcRWdq6hw2v+vPhwvCkxWeM1tZUOt4KpLoDd7Nl
yP0e03RiqhjKaJMeoYV+9Udly/hNVyh00jT/MLbu9mIwFIws6wIDAQABo4IBJzCCASMwHwYDVR0j
BBgwFoAUoBEKIz6W8Qfs4q8p74Klf9AwpLQwHQYDVR0OBBYEFImCZ33EnSZwAEu0UEh83j2uBG59
MA4GA1UdDwEB/wQEAwIBBjAPBgNVHRMBAf8EBTADAQH/MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggr
BgEFBQcDBDARBgNVHSAECjAIMAYGBFUdIAAwewYDVR0fBHQwcjA4oDagNIYyaHR0cDovL2NybC5j
b21vZG9jYS5jb20vQUFBQ2VydGlmaWNhdGVTZXJ2aWNlcy5jcmwwNqA0oDKGMGh0dHA6Ly9jcmwu
Y29tb2RvLm5ldC9BQUFDZXJ0aWZpY2F0ZVNlcnZpY2VzLmNybDARBglghkgBhvhCAQEEBAMCAQYw
DQYJKoZIhvcNAQEFBQADggEBAJ2Vyzy4fqUJxB6/C8LHdo45PJTGEKpPDMngq4RdiVTgZTvzbRx8
NywlVF+WIfw3hJGdFdwUT4HPVB1rbEVgxy35l1FM+WbKPKCCjKbI8OLp1Er57D9Wyd12jMOCAU9s
APMeGmF0BEcDqcZAV5G8ZSLFJ2dPV9tkWtmNH7qGL/QGrpxp7en0zykX2OBKnxogL5dMUbtGB8SK
N04g4wkxaMeexIud6H4RvDJoEJYRmETYKlFgTYjrdDrfQwYyyDlWjDoRUtNBpEMD9O3vMyfbOeAU
TibJ2PU54om4k123KSZB6rObroP8d3XK6Mq1/uJlSmM+RMTQw16Hc6mYHK9/FX8wggUaMIIEAqAD
AgECAhBtGeqnGU9qMyLmIjJ6qnHeMA0GCSqGSIb3DQEBBQUAMIGuMQswCQYDVQQGEwJVUzELMAkG
A1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNU
IE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVRO
LVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMB4XDTExMDQyODAwMDAw
MFoXDTIwMDUzMDEwNDgzOFowgZMxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNo
ZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkwNwYD
VQQDEzBDT01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0EwggEi
MA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCShIRbS1eY1F4vi6ThQMijU1hfZmXxMk73nzJ9
VdB4TFW3QpTg+SdxB8XGaaS5MsTxQBqQzCdWYn8XtXFpruUgG+TLY15gyqJB9mrho/+43x9IbWVD
jCouK2M4d9+xF6zC2oIC1tQyatRnbyATj1w1+uVUgK/YcQodNwoCUFNslR2pEBS0mZVZEjH/CaLS
TNxS297iQAFbSGjdxUq04O0kHzqvcV8H46y/FDuwJXFoPfQP1hdYRhWBPGiLi4MPbXohV+Y0sNsy
fuNK4aVScmQmkU6lkg//4LFg/RpvaFGZY40ai6XMQpubfSJj06mg/M6ekN9EGfRcWzW6FvOnm//B
AgMBAAGjggFLMIIBRzAfBgNVHSMEGDAWgBSJgmd9xJ0mcABLtFBIfN49rgRufTAdBgNVHQ4EFgQU
ehNOAHRbxnhjZCfBL+KgW7x5xXswDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8CAQAw
EQYDVR0gBAowCDAGBgRVHSAAMFgGA1UdHwRRME8wTaBLoEmGR2h0dHA6Ly9jcmwudXNlcnRydXN0
LmNvbS9VVE4tVVNFUkZpcnN0LUNsaWVudEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMHQGCCsG
AQUFBwEBBGgwZjA9BggrBgEFBQcwAoYxaHR0cDovL2NydC51c2VydHJ1c3QuY29tL1VUTkFkZFRy
dXN0Q2xpZW50X0NBLmNydDAlBggrBgEFBQcwAYYZaHR0cDovL29jc3AudXNlcnRydXN0LmNvbTAN
BgkqhkiG9w0BAQUFAAOCAQEAhda+eFdVbTN/RFL+QtUGqAEDgIr7DbL9Sr/2r0FJ9RtaxdKtG3Nu
PukmfOZMmMEwKN/L+0I8oSU+CnXW0D05hmbRoZu1TZtvryhsHa/l6nRaqNqxwPF1ei+eupN5yv7i
kR5WdLL4jdPgQ3Ib7Y/9YDkgR/uLrzplSDyYPaUlv73vYOBJ5RbI6z9Dg/Dg7g3B080zX5vQvWBq
szv++tTJOjwf7Zv/m0kzvkIpOYPuM2kugp1FTahp2oAbHj3SGl18R5mlmwhtEpmG1l1XBxunML5L
SUS4kH7K0Xk467Qz+qA6XSZYnmFVGLQh1ZnV4ENAQjC+6qXnlNKw/vN1+X9u5zCCBTUwggQdoAMC
AQICEDWub7CYfsGXUhthgY5vuwcwDQYJKoZIhvcNAQEFBQAwgZMxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9E
TyBDQSBMaW1pdGVkMTkwNwYDVQQDEzBDT01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBT
ZWN1cmUgRW1haWwgQ0EwHhcNMTEwOTA5MDAwMDAwWhcNMTIwOTA4MjM1OTU5WjArMSkwJwYJKoZI
hvcNAQkBFhplYnVyZ2VyQHN0YW5kYXJkc3RyYWNrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEP
ADCCAQoCggEBAML1VN+kPTw2iXeq1Yag6nChmCSmvCGACE3X9APNsUP2GvbYNFj6qdkayJJdhy0T
aIzCiMW01sD5mSV4mi0w8EfXKn/cwqi1Brw06fwaI4T2iGXA/0zb272GR57uoH1VjMd0/Qc1h2CJ
9ueUwsxP9ufXm7Kb9+DkLGDAU+6jQQv9rTiNz8sSyjOTSmtrsVpk5MTRn0np6fybkyxcjNy2cLTX
56+gfF4SxgukWt0XAWI49y+PAp2AyG9RxX/1kTZPCEPLzitGpDTGPN7HH9sdvXyyhNT73i20BtZ0
FHRfhLIo1bRqnl3W06JjVOkNbUxFbE4p01FrF7O/kRk+WZ+FMVcCAwEAAaOCAeowggHmMB8GA1Ud
IwQYMBaAFHoTTgB0W8Z4Y2QnwS/ioFu8ecV7MB0GA1UdDgQWBBSMC0QogJ7C8csD5XuRaGotm7qC
mDAOBgNVHQ8BAf8EBAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYB
BAGyMQEDBQIwEQYJYIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCsw
KQYIKwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMFcGA1UdHwRQME4wTKBK
oEiGRmh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9ET0NsaWVudEF1dGhlbnRpY2F0aW9uYW5k
U2VjdXJlRW1haWxDQS5jcmwwgYgGCCsGAQUFBwEBBHwwejBSBggrBgEFBQcwAoZGaHR0cDovL2Ny
dC5jb21vZG9jYS5jb20vQ09NT0RPQ2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENB
LmNydDAkBggrBgEFBQcwAYYYaHR0cDovL29jc3AuY29tb2RvY2EuY29tMCUGA1UdEQQeMByBGmVi
dXJnZXJAc3RhbmRhcmRzdHJhY2suY29tMA0GCSqGSIb3DQEBBQUAA4IBAQATedFpXp5JcVGrEipp
KirfegdjPe823Noihn8K6Em01BbEuUsPgHVY/a/6v0UNICBEAuQCwF4aJxuxSBN2GZ6XasVvlg+R
nMnJP6ZZLkd8QmRSmt/AyzxCXkDQdPEJ41+ioNUmVpnGHtHliaT8yEF9EwmMDsy+efbjWomPIx5P
e6MWJX/W2qQ60WhPQxD1U+3VbqWYtn6j9M89JpgQyjYku8C+oOuFUnZskIjbnWMsB3ahHEUympe0
okQT0frCohstkscVkhk63zLmHaUmhKGrJvVwFK+RBBAzuVJcwmEvQqsrczwtlO5E/Qr729Kbch6A
JfmJZ7fJIL1+RbB7ORZNMYIDqzCCA6cCAQEwgagwgZMxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJH
cmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBM
aW1pdGVkMTkwNwYDVQQDEzBDT01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUg
RW1haWwgQ0ECEDWub7CYfsGXUhthgY5vuwcwCQYFKw4DAhoFAKCCAdcwGAYJKoZIhvcNAQkDMQsG
CSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTIwODEwMjI1MjU5WjAjBgkqhkiG9w0BCQQxFgQU
ikktvGfLF51NQTR/AXzKkuS8sN8wgbkGCSsGAQQBgjcQBDGBqzCBqDCBkzELMAkGA1UEBhMCR0Ix
GzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMR
Q09NT0RPIENBIExpbWl0ZWQxOTA3BgNVBAMTMENPTU9ETyBDbGllbnQgQXV0aGVudGljYXRpb24g
YW5kIFNlY3VyZSBFbWFpbCBDQQIQNa5vsJh+wZdSG2GBjm+7BzCBuwYLKoZIhvcNAQkQAgsxgaug
gagwgZMxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcT
B1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkwNwYDVQQDEzBDT01PRE8gQ2xp
ZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEDWub7CYfsGXUhthgY5vuwcw
DQYJKoZIhvcNAQEBBQAEggEAbwju+2YksGKJR5JtxnLptsMpt4WxwD4fMqXdsapxhj86YF8JOnwK
756Cc5hqAAtAUGekMMxtGuIHETgRyF3vuHAFNc6YxTMW36t/W0Vhl/8xDnz1r9YZToI3D62ElDh8
LKu1B8W49AQVdknHTNCieaMbYr9H3SNfi5bCs4nwl4OebdEMauvfCqQI/X1jGA0xNyjDGWgD4iUp
ac5KZAAnzfXLVbpUeO5FCqxPaBenhIBuTuIkRAiiG0Wy3kc+UJk9xTSQt0t4LP7E9E0wB2TC+zij
Gm6yBhuzZ7rYXpF/zxNLo55kygklUCTq/5l7HEADM6CJoayvn/AAcSOVI2qZygAAAAAAAA==

--Apple-Mail-87--887724113--

--Apple-Mail-88--887724103
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
content-transfer-encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJQJZDMAAoJEDY/T2tCIPW38KMP/0ySmoSyuCGYoM7/r5m5BX5l
ObbBILEm/18IAjyp+NPJe34+n2aXqQt8tPumIWCNcXEbs3ZKVuvBho15kmNTRHFX
lqpspsq9alrhkhijME7vTnmKH+d+Gw95ZL2+cTjDPmCZqIJz0UrpmWobNjpnW1ce
pSTADY09w5cyH5R3gIzfzFW8mvxDIUr4lLc80V1q6HEVy2qinOe321tzTZ6vfCe2
3NdRzhG83N2rBeIu/VW+nnTQ4bvjSHue9snLuTSHv0mldK4wDD8/u+cVBtptRbqP
tRDgbK3/QVPe9iQzta8c6wIUX+RfMwEYJxFZJUTvNwLzIu5S+G+nrbN7pV0fut2s
KvubynVjTXW7j3Xo5FBiyfyhR07yg38IOnZO3t+TP9mefEJF9NiXHkVjdn+Efezi
I4OVOss+bGvmiPvlBH5KsFvAWudv1ATS2W5bc9Z/6H2dlNVrAmVbY8twTfDgE+C9
Q8U9GtKG7FuI+noPn0I+szhjl1GoTGC3JGMDtICk8a6X25VF5M3MMpc2e8L+rA3e
TsUMM2yaVM5J047K6ZYU40kZ8KNE13iy5sI0NgDq7hXkpk79VOdiVE044Els8YoP
0F/5krZ3xLRXUBsZjdUuARCPbrghtg1bG5XxpLDuSKXVrAQ6pNZxW3dVDoroZvbx
+WEtRoUTlkuLbsSZk7Rq
=lP82
-----END PGP SIGNATURE-----

--Apple-Mail-88--887724103--

From hallam@gmail.com  Fri Aug 10 20:09:14 2012
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EE0811E80DC for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 20:09:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.515
X-Spam-Level: 
X-Spam-Status: No, score=-5.515 tagged_above=-999 required=5 tests=[AWL=-1.916, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0v1vwyT7HGtB for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 20:09:13 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id EA52211E8087 for <ietf@ietf.org>; Fri, 10 Aug 2012 20:09:12 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so3633678obb.31 for <ietf@ietf.org>; Fri, 10 Aug 2012 20:09:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=5betldK8TFXHAmD/4XHpD9GNtwdpn9vIILTyAhyNceE=; b=cn8Tt6AEqPFOc/jeL+qBXi+1Vl5HNmZeZsDh2LJ6TFOKSuRwZfe4Jpc7z2lzwXZdU+ Uu7TClq1xHrZmTA8Pr2fDaksMjQ6RLdyXHbJcdWg7GEh+raakUiteZtp6Vv13I39py71 rsbf/HV2Uf6I1VjmWZAdoemVoG7eYR8Hwhivj/z8nQbNhbhuBDWD5lIqzBFhPijsIliy MgAI5CFoGY2Rg6Oqwqqfmwg7dWa8Yt5ROwLHLGRxLA9AXEz7HhI7q/XEoj2czd8fozny DQxVt+jBR8myVKrvaPwQ1kPeQjVImWCMrlMmd1ev6+gyG56HU1ZnwnqRVmGzcSJPvVfb wDiw==
MIME-Version: 1.0
Received: by 10.60.2.42 with SMTP id 10mr1748255oer.9.1344654552472; Fri, 10 Aug 2012 20:09:12 -0700 (PDT)
Received: by 10.76.80.10 with HTTP; Fri, 10 Aug 2012 20:09:12 -0700 (PDT)
In-Reply-To: <1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.com>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <CAMm+Lwio8=EyW-=LZE8BA4=6N=H4f7a1Nycg25LxB920ceZ6JA@mail.gmail.com> <1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.com>
Date: Fri, 10 Aug 2012 23:09:12 -0400
Message-ID: <CAMm+LwgBhpJhacVLrAYiUJHzEuHifonXNvCz5v5W3MDCaCRwDQ@mail.gmail.com>
Subject: Re: Last Call: Modern Global Standards Paradigm
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Eric Burger <eburger@standardstrack.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IAB <iab@iab.org>, IETF list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 03:09:14 -0000

This has been going on for quite a few years now and I had read many
iterations before the ITU-T Dubai meeting emerged as the venue of
choice for the latest push on this idea.

The real problem is that many of the smaller countries have lost tax
revenue that used to be collected on international telephone calls and
Russia and China are offering them the fiction that they will be able
to recoup that if they bring the net under control. That idea is even
more attractive to the telecommunications ministers who were getting a
cut of that revenue.

I think the idea that the ITU-T is going to write a treaty that
western governments feel obliged to sign is rather silly. The US has
had no problem refusing to sign treaties and withdrawing from UN
charter bodies, none. Europe isn't a pushover either. Does anyone
really imagine that the Senate is going to ratify any treaty that
comes out regardless of what it says?

There is a big difference between aspirational and necessary goals.
The SCO countries aspirational goal is control of the net. Their
necessary goal is to ensure that undue US influence over Internet
governance might lead policy makers to believe that they could impose
a digital blockade. Now I am pretty sure that the technology does not
allow them to do that but what really matters is what the policy
makers believe and there are some individuals who could well be in
very senior policy making positions who clearly think it does.

The necessary goal for the US is to maintain the openness of the
Internet. At least that is what the State dept considers the primary
goal at the moment. The big liability in the US position is the
aspirational goal of maintaining control. Take that off the table and
there would be remarkably little support for the SCO scheme.


On Fri, Aug 10, 2012 at 6:52 PM, Eric Burger <eburger@standardstrack.com> w=
rote:
> PLEASE, PLEASE, PLEASE read what the proposal is. The proposal being put =
forth is not that the ITU-T wants to write Internet standards. The proposal=
 being put forth is that ONLY ITU-T standards will be the *legal* standards=
 accepted by signatory nations.
>
> At best, this would be a repeat of GOSIP in the U.S., where the law was t=
he U.S. government could only buy OSI products. The issue there was the pri=
vate sector was still free to buy what it wanted and DoD did not really fol=
low the rules and bought TCP/IP instead. TCP/IP in the market killed OSI.
>
> The difference here is some countries may take their ITR obligations lite=
rally and ban products that use non-ITU protocols. Could one go to jail for=
 using TCP/IP or HTTP? That has an admittedly small, but not insignificant =
possibility of happening. Worse yet, having treaties that obligates countri=
es to ban non-ITU protocols does virtually guarantee a balkanization of the=
 Internet into open and free networking and controlled and censored network=
ing.
>
> Just as it is not fair to say that if the ITU-T gets its way the world wi=
ll end, it is also not fair to say there is no risk to allowing the ITU-T t=
o get a privileged, NON-VOLUNTARY, position in the communications world.
>
> On Aug 10, 2012, at 9:49 AM, Phillip Hallam-Baker wrote:
>
>> I think the point needs to be made that standards organizations can
>> only advise and not dictate.
>>
>> There is really no risk that ITU-T is going to end up in control of
>> the technical standards that are implemented by the likes of
>> Microsoft, Cisco or Google, let alone Apache, Mozilla and the folk on
>> SourceForge and Github.
>>
>> The key defect in the ITU-T view of the world is that it is populated
>> by people who think that they are making decisions that matter. In
>> practice deciding telephone system standards right now is about as
>> important as the next revision of the FORTRAN standard, it is not
>> completely irrelevant but matters a lot more to the people in the
>> meetings than anyone else.
>>
>> The strength of the IETF negotiating position comes from the fact that
>> we cannot dictate terms to anyone. The consensus that matters is not
>> just consensus among the people developing the specification document
>> but consensus among the people who are expected to act on it.
>>
>> ITU-T can certainly set themselves up a Friendship Games if they like
>> [1]. But they can't force people to show up, let alone implement their
>> 'requirements'.
>>
>> From a censorship busting point of view, the best thing that can
>> happen for us is for the states attempting to gain control of the net
>> in their country to attempt to standardize their approach. Much easier
>> to circumvent fixed blocks than the current moving target.
>>
>>
>> [1] http://en.wikipedia.org/wiki/Friendship_Games
>>
>>
>> On Fri, Aug 10, 2012 at 11:19 AM, IETF Chair <chair@ietf.org> wrote:
>>>
>>> The IETF Chair and the IAB Chair intend to sign the Affirmation
>>> of the Modern Global Standards Paradigm, which can be found
>>> here:
>>>
>>> http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.=
pdf
>>>
>>> An earlier version was discussed in plenary, and the IAB Chair called
>>> for comments on the IETF mail list.  This version includes changes
>>> that address those comments.
>>>
>>> Th IETF 84 Administrative plenary minutes have been posted, so that
>>> discussion can be reviewed if desired.  The minutes are here:
>>>
>>> http://www.ietf.org/proceedings/84/minutes/minutes-84-iesg-opsplenary
>>>
>>> On 8 August 2012, the IEEE Standards Association Board of Governors
>>> approved this version of the document.  The approval process is
>>> underway at the W3C as well.
>>>
>>> The IETF Chair and the IAB Chair intend to sign the Affirmation in the
>>> next few weeks. Please send strong objections to the iab@iab.org
>>> and the ietf@ietf.org mailing lists by 2012-08-24.
>>>
>>> Thank you,
>>>  Russ Housley
>>>  IETF Chair
>>
>>
>>
>> --
>> Website: http://hallambaker.com/
>



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

From Jeff.Hodges@KingsMountain.com  Fri Aug 10 21:41:20 2012
Return-Path: <Jeff.Hodges@KingsMountain.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1417621F851C for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 21:41:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.377
X-Spam-Level: 
X-Spam-Status: No, score=-101.377 tagged_above=-999 required=5 tests=[AWL=0.888, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H8dFgx2wah-W for <ietf@ietfa.amsl.com>; Fri, 10 Aug 2012 21:41:19 -0700 (PDT)
Received: from oproxy7-pub.bluehost.com (oproxy7-pub.bluehost.com [67.222.55.9]) by ietfa.amsl.com (Postfix) with SMTP id 8E8DC21F8508 for <ietf@ietf.org>; Fri, 10 Aug 2012 21:41:18 -0700 (PDT)
Received: (qmail 1457 invoked by uid 0); 11 Aug 2012 04:40:53 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by oproxy7.bluehost.com with SMTP; 11 Aug 2012 04:40:53 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kingsmountain.com; s=default;  h=Content-Transfer-Encoding:Content-Type:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=pAUvay1+OwfsdgXlsoXr/7NnBbFxf3AmRbW1zQy4gVY=;  b=2JCYYopKE5hWt5Dw40q4+QK9rfVYp5cy9gFeYYUfHvOmPlvmXnpiNztH2QgqqV4BHksahsz5o4n29WYkPHuzReCP/hzaT4KTHDRICE4juqTotMrD9ZmyokkLG14pjE4X;
Received: from [24.4.122.173] (port=43149 helo=[192.168.11.12]) by box514.bluehost.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1T03VN-0007RE-Lo; Fri, 10 Aug 2012 22:40:53 -0600
Message-ID: <5025E253.7070907@KingsMountain.com>
Date: Fri, 10 Aug 2012 21:40:51 -0700
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: Ben Campbell <ben@nostrum.com>
Subject: Re: Gen-ART LC Review of draft-ietf-websec-strict-transport-sec-11
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 24.4.122.173 authed with jeff.hodges+kingsmountain.com}
Cc: General Area Review Team <gen-art@ietf.org>, IETF WebSec WG <websec@ietf.org>, draft-ietf-websec-strict-transport-sec.all@tools.ietf.org, IETF Discussion List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 04:41:20 -0000

Hi,

I believe I've made requite changes to draft-ietf-websec-strict-transport-sec
per this thread as well as the WG f2f discussion @IETF-84 Vancouver and also my
f2f discussion with Ben after the websec wg meeting.

In the below I'm just going to try to identify the individual issues from Ben's
review without quoting all the thread discussion, but also highlight the changes
I have queued in my -12 working copy of draft-ietf-websec-strict-transport-sec.

If the below looks nominally OK I can submit my -12 working copy, please let me 
know (Alexey/Barry). (note: I'm going to be mostly offline for the next several 
days)

thanks,

=JeffH
------

Ben's "minor items":

M1) update 2818 ?

 >> -- Does this draft update any other RFCs (e.g. 2616 or 2818)?

Maybe 2818, but based on the informational status of 2818, websec wg 
discussions, and discussions with Ben and EKR, there's no statement of updating 
2818 in my -12 working copy.


M2) non-conformant UAs ?

 >>> -- I did not find any guidance on how to handle UAs that do not
 >>> understand this extension. I don't know if this needs to be normative,
 >>> but the draft should at least mention the possibility and implications.
 >>
 >> Agreed. My -12 working copy now contains these new subsections..
 >>
 >> <snip/>
 >>
 > That's all good text, but I'm not sure it actually captures my concern.
 >
 > <snip/> That is, the server can't merely select the extension and forget
 > about things--it still needs to to take the same care to avoid leaking
 > resources over unprotected connections that it would need to do if this
 > extension did not exist in the first place.
 >
 > I think this is implied by your last sentence above, but it would be better
 > to say it explicitly.

I've added text to my -12 working copy, it now states...

###
14.1.  Non-Conformant User Agent Implications

    Non-conformant user agents ignore the Strict-Transport-Security
    header field, thus non-conformant user agents do not address the
    threats described in Section 2.3.1 "Threats Addressed".

    This means that the web application and its users wielding non-
    conformant UAs will be vulnerable to both:

    o  Passive network attacks due to web site development and deployment
       bugs:

          For example, if the web application contains any insecure,
          non-"https", references to the web application server, and if
          not all of its cookies are flagged as "Secure", then its
          cookies will be vulnerable to passive network sniffing, and
          potentially subsequent misuse of user credentials.

    o  Active network attacks:

          For example, if an attacker is able to place a man-in-the-
          middle, secure transport connection attempts will likely yield
          warnings to the user, but without HSTS Policy being enforced,
          the present common practice is to allow the user to "click-
          through" and proceed.  This renders the user and possibly the
          web application open to abuse by such an attacker.

    This is essentially the status-quo for all web applications and their
    users in the absence of HSTS Policy.  Since web application providers
    typically do not control the type or version of UAs their web
    applications interact with, the implication is that HSTS Host
    deployers must generally exercise the same level of care to avoid web
    site development and deployment bugs (see Section 2.3.1.3) as they
    would if they were not asserting HSTS Policy.
###


M3) the superdomain match wins (?) question  (section 8.x generally)

 >>> -- How should a UA handle potential conflicts between a the policy
 >>> record that includes the includeSubdomain, and any records for subdomains
 >>> that might have different parameters?
 >>
 >> this is in the draft. the short answer is that at policy enforcement time,
 >> "superdomain matches win".
 >>
 >> At "noting an HSTS Host" time, the HSTS host's policy (if expressed) is
 >> noted regardless of whether there are superdomain HSTS hosts asserting
 >> "includeSubDomains".
 >>
 >> perhaps this needs to be made more clear?
 >
 > Maybe I'm missing something, but I'm not getting that answer from the text.

In our f2f discussion, Ben and I agreed that we need to clear that we stop on 
first match when doing policy enforcement -- but it turns out to be not quite 
that simple, due to the includeSubDomains semantics. Here's the relvant text now 
in my -12 working copy, the alterations are in step 5...

###
8.3.  URI Loading and Port Mapping

    Whenever the UA prepares to "load", also known as "dereference", any
    "http" URI [RFC3986] (including when following HTTP redirects
    [RFC2616]), the UA MUST first determine whether a domain name is
    given in the URI and whether it matches a Known HSTS Host, using
    these steps:
                         .
                         .
    4.  Otherwise, the substring is a given domain name, which MUST be
        matched against the UA's Known HSTS Hosts using the procedure in
        Section 8.2 "Known HSTS Host Domain Name Matching".

    5.  If when performing doman name matching, any superdomain match
        with an asserted includeSubDomains flag is found, or, if no
        superdomain matches with asserted includeSubDomains flags are
        found and a congruent match is found (with or without an asserted
        includeSubDomains flag), then before proceeding with the load:
                         .
                         .
###


M4) section 6.1: handling header field extensibility

[ see separate message entitled "handling STS header field extendability" ]
section 7.2 must not serve insecure content?



M5) section 7.2: state explicitly must not serve insecure content?

no changes necessary, see relevant discussion in this thread.



M6) section 8.4:formal duty for revocation checking ?

Based on f2f discussions with Ben and EKR, I now have the following text in my 
-12 working copy, and have moved the references to RFC2560 & RFC5280 to 
Informational. The rationale is that revocation checking is not required by the 
TLS and PKIX specs, they just say "here's how you can do it", and there's not 
really an appropriate spec to point at (which would have any chance at all to be 
actually adhered to by UAs due to the rapidly evolving nature of our 
understanding of the efficacy and performance and utility of "classical" 
revocation checking).

###
8.4.  Errors in Secure Transport Establishment

    When connecting to a Known HSTS Host, the UA MUST terminate the
    connection (see also Section 12 "User Agent Implementation Advice")
    if there are any errors, whether "warning" or "fatal" or any other
    error level, with the underlying secure transport.  For example, this
    includes any errors found in certificate validity checking UAs employ
    such as via Certificate Revocation Lists (CRL) [RFC5280], or via the
    Online Certificate Status Protocol (OCSP) [RFC2560].
###





Ben's editorial items:


E1) Unused Reference: 'RFC6376'                       -- done in -12

E2) fixup indented "Note:" such that one(s) that are normative as a regular 
paragraph(s) and leave the others as-is              -- done in -12

E3) reference to SSLv3, ref 6101 informatively       -- done in -12

E4) section 8.3 congruent match -- text is fine, no changes necessary

E5) move section 12 up ahead of the non-normative guidance sections
                                                      -- done in -12

E6) proxy sec cons apply to CONNECT proxy ?            -- done in -12
( noted that the type of proxy of concern is a "MITM non-transparent proxy",
   which ought to clarify that it's not a transparent HTTP CONNECT-based
   proxy. (I couldn't find any dominating terminology describing these
   beasts, it is all over the map, but maybe I'm missing something) )


---
end












From lars@netapp.com  Sat Aug 11 00:27:33 2012
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FD1821F84D2 for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 00:27:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.451
X-Spam-Level: 
X-Spam-Status: No, score=-10.451 tagged_above=-999 required=5 tests=[AWL=0.148, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jX69WdhOQn7V for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 00:27:32 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id B3E1321F84CF for <ietf@ietf.org>; Sat, 11 Aug 2012 00:27:32 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.77,749,1336374000";  d="p7s'?scan'208";a="675637665"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 11 Aug 2012 00:26:53 -0700
Received: from vmwexceht01-prd.hq.netapp.com (vmwexceht01-prd.hq.netapp.com [10.106.76.239]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q7B7QqoD022664; Sat, 11 Aug 2012 00:26:53 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.211]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.02.0309.002; Sat, 11 Aug 2012 00:26:52 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: [IAB] Last Call: Modern Global Standards Paradigm
Thread-Topic: [IAB] Last Call: Modern Global Standards Paradigm
Thread-Index: AQHNdwuHIJ6bgXoI70y/JI0eEC/nmJdUHc6AgACOywA=
Date: Sat, 11 Aug 2012 07:26:51 +0000
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E90675A1BB@SACEXCMBX01-PRD.hq.netapp.com>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <8393C34B-3BD4-4453-A315-74D93E971260@gmail.com>
In-Reply-To: <8393C34B-3BD4-4453-A315-74D93E971260@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.115]
Content-Type: multipart/signed; boundary="Apple-Mail=_2B61C393-597E-49D1-B8A6-21ECCBCEAA5F"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 07:27:33 -0000

--Apple-Mail=_2B61C393-597E-49D1-B8A6-21ECCBCEAA5F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Aug 11, 2012, at 1:55, Bob Hinden <bob.hinden@gmail.com> wrote:
> I support the IETF and IAB chairs signing document.

+1

(I'd even co-sign for the IRTF, but I think that isn't really =
appropriate in this case.)

Lars=

--Apple-Mail=_2B61C393-597E-49D1-B8A6-21ECCBCEAA5F
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMQDCCBUow
ggQyoAMCAQICEFcfSRTG0jNknqb9LV9GuFkwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTEyMTAwMDAwMDBaFw0x
MjEyMDkyMzU5NTlaMIIBDTEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEeMBwGCSqGSIb3DQEJARYPbGFyc0BuZXRhcHAuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokrhJTcXt6J/VEpZOicLoguBlYTjXP9v
Ze4HuuhXnURUS8YouAfgaqA0zYbt5yd6fh4PBMdAaEWr5yJyHuFykXlrCumjUWSpLuqTS2A+pt4q
cZaAQk9iLDN/UVd3SpkUuvWbxXlqzG7/BSqa3VNObBzCmyh+V7aXxri+30CT//DSsNRC4VFy6sn6
dMgSaFenXLwe/FBwY0qTMfICT1PrrX6Sw1S8OfH9rykLlZXbmfkFExxQngp1DJH9xMHeODHGbCv/
ty5gdxMOrLe+vENxFEcy1YQWBZd1kNL4UObugF8A/jE/s+Oa3H1VFH8ghqZTdqGDysVxmtKHuNFx
6jIBSQIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgG
CCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNV
HSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDovL2luZGMx
ZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqG
SIb3DQEBBQUAA4IBAQBA7q6tR92qpd7xo7VBsrOfGCWzoxIVfTc7t0RhB/Oz/+c3lnhYnNScIuKN
JmyZvznmVxqB9BJ72+NkvmdB/hnILSBTRawL2tyLo9PkBtN0nRt4gS6wjpWnD8G83hlJLE7r25jk
7HkRev61dTIXsANFpJKF02C4XSoDfEzNV6MpuEvHvcgHCqMrlwWwfKc7+NoDnE8PBuRzwSXvlD5L
mswCY2iiOsd7ImNO4OzTCxETvKTDu92+FTIbRJJpYjVNv1UF7e3w9Kq65BkZJErUH19beUeQl0Wh
2BJQE6/15rQyCnP0iJ/Nmx2/kI6M0PWunEsI6FMs0MbosreaWGHlQmomMIIG7jCCBdagAwIBAgIQ
cRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQL
EzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYD
VQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y
aXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAo
YykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBD
bGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6ZvgSU6Lb9UB
0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHsEnMhjfXc
MM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO4YM/d/mZ
//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSyriMGZSal
J1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYI
KwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0T
AQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVy
aXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9w
Y2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1h
Z2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28u
dmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRl
TGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHp
MIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWduLCBJ
bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENsYXNzIDEg
UHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+v
OEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlMJBq6WaSH
O3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKvYLMVirOV
nDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDRyxTWcVib
vtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy+kgOZY5J
yNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/wYIxggSL
MIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDgxMTA3MjY1MVowIwYJKoZIhvcNAQkEMRYEFEC7
hL6vPJFLP5KrouTTRgjCkn0NMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBAGVeazbu
BiuC3wJdUKWI5fofvvmF8pZ01DvsuDkaIyEc3WBsv9eIQPZbL2Ad/JOHblC5SL9SZsKQxtD+5Svu
ghAmOezjBAlkrGBN+/chlKcUQV5nnJGQjzty0PrGOhCqoYqlJ1fh/k6XvfL/EbkFlXKQvFY3RqDB
eZnU+Ogx2RyYi515mhwjCVmbKZ7gYy7EjJGN8XfeNUYFKq47o7xcYg1WGh/V/Mh8maco+bDyEOT+
60NZoaQDRRDfvj6fdljDfZogh4IExnAewmaTW3ECt9vHS36aNMqUvx3T38pIIjhOu6RpqvV5D/4/
yLvoOTGmIuA6FqMves3xf+KBHPR5pXIAAAAAAAA=

--Apple-Mail=_2B61C393-597E-49D1-B8A6-21ECCBCEAA5F--

From brian.e.carpenter@gmail.com  Sat Aug 11 00:44:18 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8029621F8594 for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 00:44:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.486
X-Spam-Level: 
X-Spam-Status: No, score=-101.486 tagged_above=-999 required=5 tests=[AWL=0.205, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mYGHTJThR4gk for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 00:44:18 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id C60D221F858A for <ietf@ietf.org>; Sat, 11 Aug 2012 00:44:17 -0700 (PDT)
Received: by weyu54 with SMTP id u54so1648989wey.31 for <ietf@ietf.org>; Sat, 11 Aug 2012 00:44:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Eq2W3DH7l61X0IMF+WVXfyDSaaUwdQyRqiNLFy4LsFE=; b=qoFIKUFkn/51GwHYKsT//bKI3Qx9Zf0n5rBqDDWMAwX9BVwGWDDOq3fwK8dGt+GVm6 QqPSoG4CHaUXfwwce9MtRoaog3j+zZoD/rLdjfoKAoTgMdgPfDqOdy/PkJhpNcpp3H7+ ssJijcrVq9tRKE12KnCtvbA1R+QKGrSV8GHit0EWVyFj13Uby5smdhHFjDfQoEvSCZU8 2wg/xl7pn4xc5qJn6J+YYYYtTNVgOHsZ8QME9scbQWFmb5vPCh0S7tKnSTFthWpqyBnR xqutSpIfalyfry58py6Pm8w0IevByG1ztG/oGvFbRZyKkOZzvY85N3TFYrBS5rXXYQcV 0rIw==
Received: by 10.180.78.4 with SMTP id x4mr2197737wiw.19.1344671056855; Sat, 11 Aug 2012 00:44:16 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-38.as13285.net. [2.102.217.38]) by mx.google.com with ESMTPS id b7sm3490118wiz.9.2012.08.11.00.44.15 (version=SSLv3 cipher=OTHER); Sat, 11 Aug 2012 00:44:16 -0700 (PDT)
Message-ID: <50260D5C.1050504@gmail.com>
Date: Sat, 11 Aug 2012 08:44:28 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF <ietf@ietf.org>
Subject: Re: Last Call: Modern Global Standards Paradigm
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <8393C34B-3BD4-4453-A315-74D93E971260@gmail.com>
In-Reply-To: <8393C34B-3BD4-4453-A315-74D93E971260@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IAB <iab@iab.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 07:44:18 -0000

I support this too.

Regards
   Brian Carpenter

On 10/08/2012 23:55, Bob Hinden wrote:
> I support the IETF and IAB chairs signing document.
> 
> Bob
> 
> On Aug 10, 2012, at 8:19 AM, IETF Chair wrote:
> 
>> The IETF Chair and the IAB Chair intend to sign the Affirmation
>> of the Modern Global Standards Paradigm, which can be found
>> here:
>>
>> http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf
>>
>> An earlier version was discussed in plenary, and the IAB Chair called
>> for comments on the IETF mail list.  This version includes changes
>> that address those comments.
>>
>> Th IETF 84 Administrative plenary minutes have been posted, so that
>> discussion can be reviewed if desired.  The minutes are here:
>>
>> http://www.ietf.org/proceedings/84/minutes/minutes-84-iesg-opsplenary
>>
>> On 8 August 2012, the IEEE Standards Association Board of Governors
>> approved this version of the document.  The approval process is
>> underway at the W3C as well.
>>
>> The IETF Chair and the IAB Chair intend to sign the Affirmation in the
>> next few weeks. Please send strong objections to the iab@iab.org
>> and the ietf@ietf.org mailing lists by 2012-08-24.
>>
>> Thank you,
>>  Russ Housley
>>  IETF Chair
> 
> .
> 

From vesely@tana.it  Sat Aug 11 02:39:16 2012
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B84A721F85D5 for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 02:39:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.6
X-Spam-Level: 
X-Spam-Status: No, score=-4.6 tagged_above=-999 required=5 tests=[AWL=0.119, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JRlSxDGt6nOc for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 02:39:15 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 356F421F859B for <ietf@ietf.org>; Sat, 11 Aug 2012 02:39:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1344677953; bh=MrQ6anUXDRZdYff0c/4ryNxFLk9diKtRL15NnlYHgeI=; l=7355; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=fziy6YHt/HdmI6N/Ghfgc9znVJuQCScYkZvI/UcMiqZ9oQe6OExKxufBw2S+BgykE ZuzNW03W+pOs9TRPJU8Pe2ZPqAlCdIquzxAXpM/rKDw1CMbsaD36rFvsG3yUf+KJ6R 5kF/Q9NgrBNdFH+o1tMhbV/DM1YCZaulNJkkL4IE=
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; Sat, 11 Aug 2012 11:39:13 +0200 id 00000000005DC035.0000000050262841.00001FC9
Message-ID: <50262840.6050305@tana.it>
Date: Sat, 11 Aug 2012 11:39:12 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: Modern Global Standards Paradigm
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <CAMm+Lwio8=EyW-=LZE8BA4=6N=H4f7a1Nycg25LxB920ceZ6JA@mail.gmail.com> <1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.com> <CAMm+LwgBhpJhacVLrAYiUJHzEuHifonXNvCz5v5W3MDCaCRwDQ@mail.gmail.com>
In-Reply-To: <CAMm+LwgBhpJhacVLrAYiUJHzEuHifonXNvCz5v5W3MDCaCRwDQ@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: Sat, 11 Aug 2012 09:39:16 -0000

I wish to thank Phillip and Eric for their illuminating comments.

However, I'm still not clear on the role that great powers may play in
the standards development and deployment, compared to that of vested
interests.  Stranger to economics, I may be conflating the concept of
open standard with that of open source, and their relationships with
markets.  I'd be grateful if someone can explain the IETF's position
in this game.

At a first glance, many traits of the IETF look similar to those of
open source organizations:  Voluntary, unpaid participation, free
products, meritocracy, even hairstyle.  However, the hype that the
Modern Global Standards Paradigm poses on industrial and commercial
competition dwarfs the aim at benefiting humanity --"hollow words"
someone said.

With different purposes and techniques, networking giants, closed
countries, and SDOs, all aim at controlling the Internet.  The IETF
has historically been different, AFAIK.  But looking at it going to
sit around a table with the sort of players mentioned in the messages
quoted below, as in a remake of the Congress of Vienna, makes me feel
doubtful.

On Sat 11/Aug/2012 05:09:12 +0200 Phillip Hallam-Baker wrote:
> This has been going on for quite a few years now and I had read many
> iterations before the ITU-T Dubai meeting emerged as the venue of
> choice for the latest push on this idea.
> 
> The real problem is that many of the smaller countries have lost tax
> revenue that used to be collected on international telephone calls and
> Russia and China are offering them the fiction that they will be able
> to recoup that if they bring the net under control. That idea is even
> more attractive to the telecommunications ministers who were getting a
> cut of that revenue.
> 
> I think the idea that the ITU-T is going to write a treaty that
> western governments feel obliged to sign is rather silly. The US has
> had no problem refusing to sign treaties and withdrawing from UN
> charter bodies, none. Europe isn't a pushover either. Does anyone
> really imagine that the Senate is going to ratify any treaty that
> comes out regardless of what it says?
> 
> There is a big difference between aspirational and necessary goals.
> The SCO countries aspirational goal is control of the net. Their
> necessary goal is to ensure that undue US influence over Internet
> governance might lead policy makers to believe that they could impose
> a digital blockade. Now I am pretty sure that the technology does not
> allow them to do that but what really matters is what the policy
> makers believe and there are some individuals who could well be in
> very senior policy making positions who clearly think it does.
> 
> The necessary goal for the US is to maintain the openness of the
> Internet. At least that is what the State dept considers the primary
> goal at the moment. The big liability in the US position is the
> aspirational goal of maintaining control. Take that off the table and
> there would be remarkably little support for the SCO scheme.
> 
> 
> On Fri, Aug 10, 2012 at 6:52 PM, Eric Burger <eburger@standardstrack.com> wrote:
>> PLEASE, PLEASE, PLEASE read what the proposal is. The proposal being put forth is not that the ITU-T wants to write Internet standards. The proposal being put forth is that ONLY ITU-T standards will be the *legal* standards accepted by signatory nations.
>>
>> At best, this would be a repeat of GOSIP in the U.S., where the law was the U.S. government could only buy OSI products. The issue there was the private sector was still free to buy what it wanted and DoD did not really follow the rules and bought TCP/IP instead. TCP/IP in the market killed OSI.
>>
>> The difference here is some countries may take their ITR obligations literally and ban products that use non-ITU protocols. Could one go to jail for using TCP/IP or HTTP? That has an admittedly small, but not insignificant possibility of happening. Worse yet, having treaties that obligates countries to ban non-ITU protocols does virtually guarantee a balkanization of the Internet into open and free networking and controlled and censored networking.
>>
>> Just as it is not fair to say that if the ITU-T gets its way the world will end, it is also not fair to say there is no risk to allowing the ITU-T to get a privileged, NON-VOLUNTARY, position in the communications world.
>>
>> On Aug 10, 2012, at 9:49 AM, Phillip Hallam-Baker wrote:
>>
>>> I think the point needs to be made that standards organizations can
>>> only advise and not dictate.
>>>
>>> There is really no risk that ITU-T is going to end up in control of
>>> the technical standards that are implemented by the likes of
>>> Microsoft, Cisco or Google, let alone Apache, Mozilla and the folk on
>>> SourceForge and Github.
>>>
>>> The key defect in the ITU-T view of the world is that it is populated
>>> by people who think that they are making decisions that matter. In
>>> practice deciding telephone system standards right now is about as
>>> important as the next revision of the FORTRAN standard, it is not
>>> completely irrelevant but matters a lot more to the people in the
>>> meetings than anyone else.
>>>
>>> The strength of the IETF negotiating position comes from the fact that
>>> we cannot dictate terms to anyone. The consensus that matters is not
>>> just consensus among the people developing the specification document
>>> but consensus among the people who are expected to act on it.
>>>
>>> ITU-T can certainly set themselves up a Friendship Games if they like
>>> [1]. But they can't force people to show up, let alone implement their
>>> 'requirements'.
>>>
>>> From a censorship busting point of view, the best thing that can
>>> happen for us is for the states attempting to gain control of the net
>>> in their country to attempt to standardize their approach. Much easier
>>> to circumvent fixed blocks than the current moving target.
>>>
>>>
>>> [1] http://en.wikipedia.org/wiki/Friendship_Games
>>>
>>>
>>> On Fri, Aug 10, 2012 at 11:19 AM, IETF Chair <chair@ietf.org> wrote:
>>>>
>>>> The IETF Chair and the IAB Chair intend to sign the Affirmation
>>>> of the Modern Global Standards Paradigm, which can be found
>>>> here:
>>>>
>>>> http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf
>>>>
>>>> An earlier version was discussed in plenary, and the IAB Chair called
>>>> for comments on the IETF mail list.  This version includes changes
>>>> that address those comments.
>>>>
>>>> Th IETF 84 Administrative plenary minutes have been posted, so that
>>>> discussion can be reviewed if desired.  The minutes are here:
>>>>
>>>> http://www.ietf.org/proceedings/84/minutes/minutes-84-iesg-opsplenary
>>>>
>>>> On 8 August 2012, the IEEE Standards Association Board of Governors
>>>> approved this version of the document.  The approval process is
>>>> underway at the W3C as well.
>>>>
>>>> The IETF Chair and the IAB Chair intend to sign the Affirmation in the
>>>> next few weeks. Please send strong objections to the iab@iab.org
>>>> and the ietf@ietf.org mailing lists by 2012-08-24.
>>>>
>>>> Thank you,
>>>>  Russ Housley
>>>>  IETF Chair
>>>
>>>
>>>
>>> --
>>> Website: http://hallambaker.com/
>>
> 
> 
> 


From sm@resistor.net  Sat Aug 11 03:04:34 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFA4621F85D7; Sat, 11 Aug 2012 03:04:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level: 
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4eidYkauR97f; Sat, 11 Aug 2012 03:04:30 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4109921F85C7; Sat, 11 Aug 2012 03:04:30 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q7BA4IE7004602; Sat, 11 Aug 2012 03:04:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1344679464; bh=mi0tg/8CP/ldKONV6VPBF3nX4HU6apPpQANk27QQ2wc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Y2lcgTgKVG422fYu15cUD9dk9Wb9Yh6xNBMSoV1PJmMLDeFzYVH9pwWQBCvKlytYM iDymx84XSw1uV16rEHcO/d5HtqHrLRffh0n6Sp/BWgG//7mhoWD7YbMETQOPBejLGd jVmVw0/hllDqNV52MIZoaNPoqonmpQPvg4QIz8I8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1344679464; i=@resistor.net; bh=mi0tg/8CP/ldKONV6VPBF3nX4HU6apPpQANk27QQ2wc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=BiDaXaogE5nOaTHDtq8YifheQnE1mgyKD6x2eGWMrnvM6riSEhFtmz4sl9+odfDXG y/4xga3upuPnfQyFBSL6Z4M6vcHnWq3RY/mhtBseNIYm7RUROp/x+GtC9rK5Z//PBQ cBHVGLPF++bFoB1/4BcJ54W7NOpfHSabnt1JDhQw=
Message-Id: <6.2.5.6.2.20120810231115.09ef5ee0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 11 Aug 2012 02:35:34 -0700
To: Eric Burger <eburger@standardstrack.com>, Phillip Hallam-Baker <hallam@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: Modern Global Standards Paradigm
In-Reply-To: <1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.com>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <CAMm+Lwio8=EyW-=LZE8BA4=6N=H4f7a1Nycg25LxB920ceZ6JA@mail.gmail.com> <1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: IAB <iab@iab.org>, IETF list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 10:04:34 -0000

At 15:52 10-08-2012, Eric Burger wrote:
>that the ITU-T wants to write Internet standards. The proposal being 
>put forth is that ONLY ITU-T standards will be the *legal* standards 
>accepted by signatory nations.

Phillip posted the following comment previously:

   "The strength of the IETF negotiating position comes from the fact that
    we cannot dictate terms to anyone. The consensus that matters is not
    just consensus among the people developing the specification document
    but consensus among the people who are expected to act on it."

If one accepts the above principle signatory nations would still use 
some IETF standards for systems and equipment and push back on 
competing standards proposed within another organization.  The 
sweetener in what was proposed is that developing nations would be 
provided with assistance to evaluate product compliance.

A significant number of these nations do not understand what is the 
IETF and how it works.  This does not affect the IETF as long as 
there isn't an alternative standard developed within an organization 
which these nations consider as reputable.

>The difference here is some countries may take their ITR obligations 
>literally and ban products that use non-ITU protocols. Could one go 
>to jail for using TCP/IP or HTTP? That has an admittedly small, but 
>not insignificant possibility of happening. Worse yet,

It is highly unlikely that someone would be sent to jail for using 
the protocols mentioned above.

>  having treaties that obligates countries to ban non-ITU protocols 
> does virtually guarantee a balkanization of the Internet into open 
> and free networking and controlled and censored networking.

Some of issues which the organization seeks to address are:

  - cybercrime

  - spam

It has been mentioned within the IETF that the walled garden service 
model simplifies a number of issues.  I don't think that some nations 
would consider network control to solve these issues as censored 
networking.  Whether these issues could be solved without a strong 
regulatory regime is another question.

At 20:09 10-08-2012, Phillip Hallam-Baker wrote:
>The real problem is that many of the smaller countries have lost tax
>revenue that used to be collected on international telephone calls and

I would describe it as a motivation to support a change which might 
bring in more revenue for these countries.  The end user will get 
fleeced but that's just a matter of detail.

>There is a big difference between aspirational and necessary goals.
>The SCO countries aspirational goal is control of the net. Their
>necessary goal is to ensure that undue US influence over Internet
>governance might lead policy makers to believe that they could impose
>a digital blockade. Now I am pretty sure that the technology does not

That debate has been going on for years.

>allow them to do that but what really matters is what the policy
>makers believe and there are some individuals who could well be in
>very senior policy making positions who clearly think it does.

Yes.

Regards,
-sm 


From randy@psg.com  Sat Aug 11 05:05:05 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CEAD21F85D4; Sat, 11 Aug 2012 05:05:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.559
X-Spam-Level: 
X-Spam-Status: No, score=-2.559 tagged_above=-999 required=5 tests=[AWL=0.040,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7b1Nclgt517N; Sat, 11 Aug 2012 05:05:04 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id CEA7F21F8565; Sat, 11 Aug 2012 05:05:00 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1T0AR9-000AGH-Ob; Sat, 11 Aug 2012 12:05:00 +0000
Date: Sat, 11 Aug 2012 08:05:13 -0400
Message-ID: <m27gt5y6py.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Chair <chair@ietf.org>
Subject: Re: Last Call: Modern Global Standards Paradigm
In-Reply-To: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 12:05:05 -0000

> The IETF Chair and the IAB Chair intend to sign the Affirmation
> of the Modern Global Standards Paradigm, which can be found
> here:
> 
> http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf

no brainer.

randy

From jari.arkko@piuha.net  Sat Aug 11 05:48:11 2012
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84D0221F85D6 for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 05: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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mGlhggQglNT4 for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 05:48:03 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id C16BE21F84A0 for <ietf@ietf.org>; Sat, 11 Aug 2012 05:48:02 -0700 (PDT)
Received: from localhost (unknown [200.115.1.152]) by p130.piuha.net (Postfix) with ESMTPSA id A7B682D7D7; Sat, 11 Aug 2012 15:47:44 +0300 (EEST)
Date: Sat, 11 Aug 2012 09:47:38 -0300
Subject: VS:  Re: [IAB] Last Call: Modern Global Standards Paradigm
Message-ID: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com>
From: Jari Arkko <jari.arkko@piuha.net>
To: "Eggert, Lars" <lars@netapp.com>, Bob Hinden <bob.hinden@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 12:48:11 -0000

KzEKCi0tLS0tLS0tIEFsa3VwZXLDpGluZW4gdmllc3RpIC0tLS0tLS0tCkFpaGU6IFJlOiBbSUFC
XSBMYXN0IENhbGw6IE1vZGVybiBHbG9iYWwgU3RhbmRhcmRzIFBhcmFkaWdtCkzDpGhldHTDpGrD
pDogIkVnZ2VydCwgTGFycyIgPGxhcnNAbmV0YXBwLmNvbT4KVmFzdGFhbm90dGFqYTogQm9iIEhp
bmRlbiA8Ym9iLmhpbmRlbkBnbWFpbC5jb20+CktvcGlvOiBJQUIgPGlhYkBpYWIub3JnPixJRVRG
IDxpZXRmQGlldGYub3JnPgoKT24gQXVnIDExLCAyMDEyLCBhdCAxOjU1LCBCb2IgSGluZGVuIDxi
b2IuaGluZGVuQGdtYWlsLmNvbT4gd3JvdGU6Cj4gSSBzdXBwb3J0IHRoZSBJRVRGIGFuZCBJQUIg
Y2hhaXJzIHNpZ25pbmcgZG9jdW1lbnQuCgorMQoKKEknZCBldmVuIGNvLXNpZ24gZm9yIHRoZSBJ
UlRGLCBidXQgSSB0aGluayB0aGF0IGlzbid0IHJlYWxseSBhcHByb3ByaWF0ZSBpbiB0aGlzIGNh
c2UuKQoKTGFycw==


From alastair.johnson@alcatel-lucent.com  Sat Aug 11 06:07:27 2012
Return-Path: <alastair.johnson@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 8B10421F85DA for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 06:07:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.451
X-Spam-Level: 
X-Spam-Status: No, score=-9.451 tagged_above=-999 required=5 tests=[AWL=0.798,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zWemiVVOYikA for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 06:07:26 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by ietfa.amsl.com (Postfix) with ESMTP id 8940B21F85D5 for <ietf@ietf.org>; Sat, 11 Aug 2012 06:07:25 -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 q7BD7Hok007503 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sat, 11 Aug 2012 15:07:18 +0200
Received: from FRMRSSXCHMBSA1X.dc-m.alcatel-lucent.com ([135.120.45.66]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Sat, 11 Aug 2012 15:07:17 +0200
From: "JOHNSON, ALASTAIR (ALASTAIR)" <alastair.johnson@alcatel-lucent.com>
To: SM <sm@resistor.net>, Mark Nottingham <mnot@mnot.net>
Date: Sat, 11 Aug 2012 15:07:16 +0200
Subject: RE: management granularity  (Re: Meeting "lounges" at IETF meetings)
Thread-Topic: management granularity  (Re: Meeting "lounges" at IETF meetings)
Thread-Index: Ac1zd4Dg5schIjKYTfKM1CHJ2PJ2OQDrfz6A
Message-ID: <E156544669B02841A2C7AF1B1A96360560783CA7AC@FRMRSSXCHMBSA1X.dc-m.alcatel-lucent.com>
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com> <501EC24B.4080709@bbiw.net>	<E4DA6495-E02F-4A47-9AA2-E47F260CF3C5@mnot.net> <6.2.5.6.2.20120805165716.07820120@resistor.net>
In-Reply-To: <6.2.5.6.2.20120805165716.07820120@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.13
Cc: ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 13:07:27 -0000

> There were 10 participants from Australia and 4 participants from New
> Zealand at the last IETF meeting.  There was interest to have the IETF in
> New Zealand.  I guess that it was considered as difficult to convince the
> cookie-eating mob that it was a good location.=20

I understand that New Zealand was felt to be too expensive[1] and the trave=
l was too far for many[2]. NZ also suffers from a lack of conference facili=
ties that are functional *and* have suitable accommodation near them to fit=
 the IETF size.=20

As much as I'd like to have NZ as a venue, since I could visit my family...

aj
A New Zealander, but not living in NZ. Vaguely affiliated with people who l=
ooked into hosting IETF in NZ.
[1] NZ is surprisingly expensive for hotel accommodation in the major citie=
s, and transport can be expensive or difficult. Flights can also be difficu=
lt since there isn't mass competition into the country unless you're trying=
 to jump the Tasman.
[2] 3 hours to East Cost AU, 10+ hours to Asia[3], 13+ hours to US, 24+ hou=
rs to Europe. Travel times would really hurt here.
[3] For the bits of Asia that are directly connected (JP, SG, HK, CN, KR). =
If you need to connect (e.g. India) you could be looking at 20+ hours too.

From brian.e.carpenter@gmail.com  Sat Aug 11 06:49:22 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41BFB21F85F9 for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 06:49:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.487
X-Spam-Level: 
X-Spam-Status: No, score=-101.487 tagged_above=-999 required=5 tests=[AWL=0.204, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ePw5eg1YZ38x for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 06:49:21 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9276521F85ED for <ietf@ietf.org>; Sat, 11 Aug 2012 06:49:21 -0700 (PDT)
Received: by weyu54 with SMTP id u54so1791007wey.31 for <ietf@ietf.org>; Sat, 11 Aug 2012 06:49:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=XkC2Jluyhrzw2NBWHk4guv8Q2jJLG952Aiy+FxVZHDA=; b=W4jryh4RXoXGL002L2BB6iDmChP8C8wjx5wGODF8pATUDX6INoNNaDB1WRHiKKJKHY jEtw8DUL7PmSOEChonyYyBQ3fk3ANTz9Kw0hJEzTLzE9kvtTk4OYI6JanV4A49boo9El GVpWD3UkwsOpaiAVrvpQMwkmAv3W7HmFgs0SMZlqmSrKdVefWY/dP4j4h0+4kU2JQ73A rMENFE6vO168hcBv5SnZHPDJUMYCRf7DzMkwap8EcBXfcAxKQGi9LSJYbfoy1ZSehsQ8 RU4i5UrSFN8gQPwFz0cWmyKqQQlTfrvIO/esbl4KAvPw9KglFbD9nSvKvS3XDiD5PQBl niTA==
Received: by 10.180.104.197 with SMTP id gg5mr3979871wib.9.1344692960703; Sat, 11 Aug 2012 06:49:20 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-38.as13285.net. [2.102.217.38]) by mx.google.com with ESMTPS id t8sm4218910wiy.3.2012.08.11.06.49.19 (version=SSLv3 cipher=OTHER); Sat, 11 Aug 2012 06:49:19 -0700 (PDT)
Message-ID: <502662ED.2000500@gmail.com>
Date: Sat, 11 Aug 2012 14:49:33 +0100
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: "JOHNSON, ALASTAIR (ALASTAIR)" <alastair.johnson@alcatel-lucent.com>
Subject: Re: management granularity  (Re: Meeting "lounges" at IETF meetings)
References: <31BCE4DE825B3F4D9E452EFBBD3F1EF280CE839F@PACDCEXMB06.cable.comcast.com>	<501EC24B.4080709@bbiw.net>	<E4DA6495-E02F-4A47-9AA2-E47F260CF3C5@mnot.net>	<6.2.5.6.2.20120805165716.07820120@resistor.net> <E156544669B02841A2C7AF1B1A96360560783CA7AC@FRMRSSXCHMBSA1X.dc-m.alcatel-lucent.com>
In-Reply-To: <E156544669B02841A2C7AF1B1A96360560783CA7AC@FRMRSSXCHMBSA1X.dc-m.alcatel-lucent.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, Mark Nottingham <mnot@mnot.net>, ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 13:49:22 -0000

On 11/08/2012 14:07, JOHNSON, ALASTAIR (ALASTAIR) wrote:
>> There were 10 participants from Australia and 4 participants from New
>> Zealand at the last IETF meeting.  There was interest to have the IETF in
>> New Zealand.  I guess that it was considered as difficult to convince the
>> cookie-eating mob that it was a good location. 
> 
> I understand that New Zealand was felt to be too expensive[1] and the travel was too far for many[2]. NZ also suffers from a lack of conference facilities that are functional *and* have suitable accommodation near them to fit the IETF size. 

The venue that was actually proposed was big enough (I did the maths)
and surrounded by hotels. Travel cost and duration was an issue, for
sure.

   Brian

> As much as I'd like to have NZ as a venue, since I could visit my family...
> 
> aj
> A New Zealander, but not living in NZ. Vaguely affiliated with people who looked into hosting IETF in NZ.
> [1] NZ is surprisingly expensive for hotel accommodation in the major cities, and transport can be expensive or difficult. Flights can also be difficult since there isn't mass competition into the country unless you're trying to jump the Tasman.
> [2] 3 hours to East Cost AU, 10+ hours to Asia[3], 13+ hours to US, 24+ hours to Europe. Travel times would really hurt here.
> [3] For the bits of Asia that are directly connected (JP, SG, HK, CN, KR). If you need to connect (e.g. India) you could be looking at 20+ hours too.
> 

From brian.e.carpenter@gmail.com  Sat Aug 11 06:58:13 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2788721F85F9 for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 06:58:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.489
X-Spam-Level: 
X-Spam-Status: No, score=-101.489 tagged_above=-999 required=5 tests=[AWL=0.202, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8OllGau3Md3s for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 06:58:12 -0700 (PDT)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7FE1521F85ED for <ietf@ietf.org>; Sat, 11 Aug 2012 06:58:12 -0700 (PDT)
Received: by wicr5 with SMTP id r5so963770wic.13 for <ietf@ietf.org>; Sat, 11 Aug 2012 06:58:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=JRNBXQW/twIIJ6eFpTdO0IAkrYQ4mt1FESo8qqv9W3k=; b=aUsdiFrPCGctuftGrF4IcwEiVNAjZg1H3cjIQ/0ax4K5OclwgVjSyCNKAJGFrQWj8z Lgm8Gx/Ly/whRwTMI1njbf5C6NMbvcF1regMhHBsxZQr7m57tpHvpZcYM1EcrB35QnEg hlcTEEHulZM+IGbEPnbbhrYmNyO70bvEqjQ6TzpMIY2UVEsGi88c60LJ7LQasHsIaEeV QPPVFEUqQMCA2+CRRt5urcndvTPeyRudGP3ieUhTX+Vuyf1gNrRN9lM0MpZb4P/zbzpD x3ep5t3yGOHTeZ++t84A1pZpFkc02LJ++YkIJae14OEIebYfby+LcHCj3nr/vwQqNUXf n7dg==
Received: by 10.180.74.33 with SMTP id q1mr4053125wiv.4.1344693491518; Sat, 11 Aug 2012 06:58:11 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-38.as13285.net. [2.102.217.38]) by mx.google.com with ESMTPS id ep14sm4742102wid.0.2012.08.11.06.58.09 (version=SSLv3 cipher=OTHER); Sat, 11 Aug 2012 06:58:10 -0700 (PDT)
Message-ID: <50266500.6000507@gmail.com>
Date: Sat, 11 Aug 2012 14:58:24 +0100
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: Alessandro Vesely <vesely@tana.it>
Subject: Re: Last Call: Modern Global Standards Paradigm
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org>	<CAMm+Lwio8=EyW-=LZE8BA4=6N=H4f7a1Nycg25LxB920ceZ6JA@mail.gmail.com>	<1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.com>	<CAMm+LwgBhpJhacVLrAYiUJHzEuHifonXNvCz5v5W3MDCaCRwDQ@mail.gmail.com> <50262840.6050305@tana.it>
In-Reply-To: <50262840.6050305@tana.it>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 13:58:13 -0000

On 11/08/2012 10:39, Alessandro Vesely wrote:
> I wish to thank Phillip and Eric for their illuminating comments.
> 
> However, I'm still not clear on the role that great powers may play in
> the standards development and deployment, compared to that of vested
> interests.  

Traditionally, and still in some countries, the telecommunications
monopolist *is* the government, so defending the monopoly is directly
in the government's financial interest. In other countries, where
there's still a de facto monopoly, that monopolist is very good at
political lobbying. So in both those types of country, the vested
interest drives the government position. Add that to the governments
that want central control and/or monitoring of information, and you
get a strong bloc of political support for standards and regulations
that support monopoly, control, and eavesdropping.

    Brian

From stephen.farrell@cs.tcd.ie  Sat Aug 11 07:17:31 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3250721F8567; Sat, 11 Aug 2012 07:17:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BjKh2K36rhFE; Sat, 11 Aug 2012 07:17:25 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 88B7421F8540; Sat, 11 Aug 2012 07:17:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 0996E171486; Sat, 11 Aug 2012 15:17:22 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1344694640; bh=DygUJ2D0nnCryO Zr0Y9LrR4gAyu5JsssV3DOSTa+rGY=; b=UT3geke+vydmrsyOs3Q/yV87iQfTeO T8F5Bg3S8DVqfs2t3Jff9nDDL9aqeATV9fp2niQ+EDf3mG8AyAasbzhHlLV+WVwI vPVzZJjjac9/D4y8CwRQl9H/6EJZCOO+XVtIzt1Oa3t8HJ1Hq+FbZrhhL+Nr0nNu 4OPD1zny/I9Ra5iOMUALszibBuJftmwOaUZL11RzYUQUxbpl6ZgCLY1IHAq4YyF4 TjzWvWhUyuvUU0VCB0EAaxLjKMm0mphoHNfKks4Y/x7LDEdJdGZ80PLL7L5ITdQk trJmE8+lQuDgF7VAF/L7k5qKf0xSvEEr39DVMx0do+AFQ3Hi7hyYw+YA==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id FyWnV13G7Veh; Sat, 11 Aug 2012 15:17:20 +0100 (IST)
Received: from [10.87.48.8] (unknown [86.46.25.40]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 7D15C17147F; Sat, 11 Aug 2012 15:17:20 +0100 (IST)
Message-ID: <50266970.3050909@cs.tcd.ie>
Date: Sat, 11 Aug 2012 15:17:20 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: IETF <ietf@ietf.org>, IAB <iab@iab.org>
Subject: Re: Last Call: Modern Global Standards Paradigm
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org>
In-Reply-To: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF Chair <chair@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 14:17:31 -0000

This is the kind of thing to which I'd normally pay
no attention at all, but I don't get away with that
these days;-)

Anyway, I do reckon this is an important issue and,
stilted language and all, this is very much worth
supporting. So, I'd encourage everyone to try find
out more about it and to support Russ and Bernard in
signing this, and to spread the message locally that
the IETF way of doing this stuff is, while not near
perfect, the best we've seen to date.

S.

On 08/10/2012 04:19 PM, IETF Chair wrote:
> 
> The IETF Chair and the IAB Chair intend to sign the Affirmation
> of the Modern Global Standards Paradigm, which can be found
> here:
> 
> http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf
> 
> An earlier version was discussed in plenary, and the IAB Chair called
> for comments on the IETF mail list.  This version includes changes
> that address those comments.
> 
> Th IETF 84 Administrative plenary minutes have been posted, so that
> discussion can be reviewed if desired.  The minutes are here:
> 
> http://www.ietf.org/proceedings/84/minutes/minutes-84-iesg-opsplenary
> 
> On 8 August 2012, the IEEE Standards Association Board of Governors
> approved this version of the document.  The approval process is
> underway at the W3C as well.
> 
> The IETF Chair and the IAB Chair intend to sign the Affirmation in the
> next few weeks. Please send strong objections to the iab@iab.org
> and the ietf@ietf.org mailing lists by 2012-08-24.
> 
> Thank you,
>   Russ Housley
>   IETF Chair
> 
> 

From dhc@dcrocker.net  Sat Aug 11 07:41:23 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 852B921F857D; Sat, 11 Aug 2012 07:41:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.592
X-Spam-Level: 
X-Spam-Status: No, score=-6.592 tagged_above=-999 required=5 tests=[AWL=0.007,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JzN0LbwLK7mp; Sat, 11 Aug 2012 07:41:22 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8561F21F850B; Sat, 11 Aug 2012 07:41:22 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q7BEfL5I013358 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 11 Aug 2012 07:41:22 -0700
Message-ID: <50266F05.5050601@dcrocker.net>
Date: Sat, 11 Aug 2012 07:41:09 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>
Subject: Re: VS:  Re: [IAB] Last Call: Modern Global Standards Paradigm
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com>
In-Reply-To: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sat, 11 Aug 2012 07:41:22 -0700 (PDT)
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 14:41:23 -0000

> Aihe: Re: [IAB] Last Call: Modern Global Standards Paradigm
> LÃ¤hettÃ¤jÃ¤: "Eggert, Lars" <lars@netapp.com>
...
> (I'd even co-sign for the IRTF, but I think that isn't really appropriate in this case.)


The "for the IRTF" underscores a possible concern in the current 
situation.

The perception will certainly be that the IAB and IETF chairs' signature 
do represent the support of the IETF.

But we are a consensus-oriented group and we have not had anything that 
even hints at a consensus-oriented process to authorize that representation.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From gtw@gtwassociates.com  Sat Aug 11 07:45:46 2012
Return-Path: <gtw@gtwassociates.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6BF121F848A; Sat, 11 Aug 2012 07:45:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.739
X-Spam-Level: 
X-Spam-Status: No, score=-0.739 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28a6hWOk546q; Sat, 11 Aug 2012 07:45:45 -0700 (PDT)
Received: from mail3.primary.net (mail3.primary.net [216.87.38.220]) by ietfa.amsl.com (Postfix) with ESMTP id 8DAA921F8472; Sat, 11 Aug 2012 07:45:45 -0700 (PDT)
Received: from pool-71-191-174-95.washdc.fios.verizon.net ([71.191.174.95]:1206 helo=gtw8608f024389) by mail3.primary.net with esmtpa (Exim 4.63) (envelope-from <gtw@gtwassociates.com>) id 1T0Cwe-00057V-TV; Sat, 11 Aug 2012 09:45:44 -0500
Message-ID: <CB9994EDE13F4C42B859C4F6637183F3@gtw8608f024389>
From: "GTW" <gtw@gtwassociates.com>
To: "IETF" <ietf@ietf.org>, "IAB" <iab@iab.org>, "IETF-Announce" <ietf-announce@ietf.org>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org>
Subject: Re: Last Call: Modern Global Standards Paradigm
Date: Sat, 11 Aug 2012 10:45:41 -0400
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
X-ACL-Warn: X-The email account used to send this email was: gtw@gtwassociates.com
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: GTW <gtw@gtwassociates.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, 11 Aug 2012 14:45:46 -0000

I support the thrust of the "Modern Global Standards Paradigm"  It is 
particularly timely  as the US formally prepares for meetings of the ITU and 
CITEL and there are some aspirations from some members and staff at ITU 
inconsistent with the market based approach to standards setting the 
document embraces.  I support IETF Chair and the IAB Chair signing such a 
document.

While I am content with the wording of the section on IP  this text  is 
nevertheless imprecise.

clip from 
http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf

4. Availability. Standards specifications are made accessible to all for

implementation and deployment. Affirming standards organizations have 
defined

procedures to develop specifications that can be implemented under fair 
terms.

Given market diversity, fair terms may vary from royalty-free (especially 
where

open source is commonplace) to fair, reasonable, and non-discriminatory 
terms

(FRAND).



end clip

 If there were time for tweaking it would be helpful.  What are time 
constraints?   The first sentence  seems to be describing the availability 
of specifications to users ... this is the issue of copyrights and fees 
charged for copies of standards.  Specifications have to be available to 
users under reasonable terms but not necessarily for free.  But the words 
are not clear that is what is being addressed. The second sentence seems to 
describe that   licenses to practice essential patent claims related to a 
standards  are available under "fair terms"  However the global patent 
policy concept generally is  that such licenses should be available under 
"reasonable and non discriminatory" terms.   The single  term   "reasonable 
and non discriminatory" covers  the situation where there may be a "fee" 
involved or not.  There may be  non fee based terms in what other wise be 
called "royalty free" licenses It is not that RAND and FRAND are different 
from "royalty free" It is that "royalty free"  falls under the overall 
condition of  fair, reasonable, and non-discriminatory term when there may 
be non royalty terms involved.  Sometimes the "royalty free" situation is 
described as  "RAND(0)"   I   am also curious about the IETF experience with 
its patent policy.  What is further background  to the statement that "often 
our IPR terms at  IETF end up being much worse than that."  The comments 
below that the paragraph does not  accurately describe the IETF experience 
are worrisome.

clip from 
http://www.ietf.org/proceedings/84/minutes/minutes-84-iesg-opsplenary

 Cullen Jennings: I was just noting that the IPR terms vary from RF to
FRAND. I wish that was true. But I think that often our IPR terms at
IETF end up being much worse than that.

Russ: Understand.

Leslie Daigle: I wanted just to help you out a bit by popping up a
level and giving the broader context of this whole statement. You have
alluded to the fact that it was born from discussions with a number of
organizations. Everyone should appreciate that Russ is presenting today
something that he thinks is viable for the IETF. The challenge has been
that indeed the words have been discussed extensively for a period of
time and there was fairly wide divergence exactly on the point that
Cullen just mentioned. Have been seeking terminology that says something
positive about how to do things, and also encompasses a broad range of
ways that different organizations do things. We are very different from
the WC3, which is very different from the IEEE. But we are trying to
capture things that are positive, constructive, new -- as compared to
the establishment, if you will, of the SDO world. So that has been the
challenge. Having input from people in terms of support or not is
probably quite useful. The document -- and I will personally take
responsibility for some of this -- is not in the best English ever. So,
some of the comments on it would be better if it were written this way,
you'll get a polite smile and a nod, and we will take that into
consideration in the next iteration. So, just by way of context, it is
a joint effort, and I hope we are capturing something useful that
expresses something the community believes in. Because personally, I
think the really novel thing is to stand up and say, there are formal
standards development organization in the world, and there are other
organizations that get together and are doing something that is
slightly different, being driven by different motivations. We are
seeking technical excellence, are dedicated to being open, are
dedicated to providing standards that will be built by industry. And
that isn't an immature form. We are hoping not to grow up into the
more traditional form. We are trying to make a statement so that more
people understand that this is a real thing, and that it is valuable.

Scott Bradner: I made some comments on this document to the authors. I
think it is a very important thing to say, for the reasons that Leslie
just described. But I do worry that it has to be accurate. And I do
believe that the specific text of the IPR section is not accurate, when
it comes to the IETF. And could be used against us because it is not
what we do.

Russ: Thank you, and I can tell you that those words are still under
discussion. The concerns that Cullen any you raised are representative
of a comment that I have already shared with the people trying to put
this to together

end clip

George T. Willingmyre, P.E.
www.gtwassociates.com
301 421 4138
----- Original Message ----- 
From: "IETF Chair" <chair@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: "IAB" <iab@iab.org>; "IETF" <ietf@ietf.org>
Sent: Friday, August 10, 2012 11:19 AM
Subject: Last Call: Modern Global Standards Paradigm


>
> The IETF Chair and the IAB Chair intend to sign the Affirmation
> of the Modern Global Standards Paradigm, which can be found
> here:
>
> http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf
>
> An earlier version was discussed in plenary, and the IAB Chair called
> for comments on the IETF mail list.  This version includes changes
> that address those comments.
>
> Th IETF 84 Administrative plenary minutes have been posted, so that
> discussion can be reviewed if desired.  The minutes are here:
>
> http://www.ietf.org/proceedings/84/minutes/minutes-84-iesg-opsplenary
>
> On 8 August 2012, the IEEE Standards Association Board of Governors
> approved this version of the document.  The approval process is
> underway at the W3C as well.
>
> The IETF Chair and the IAB Chair intend to sign the Affirmation in the
> next few weeks. Please send strong objections to the iab@iab.org
> and the ietf@ietf.org mailing lists by 2012-08-24.
>
> Thank you,
>  Russ Housley
>  IETF Chair
> 


From dhc@dcrocker.net  Sat Aug 11 07:47:56 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 619CE21F84A1; Sat, 11 Aug 2012 07:47:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.592
X-Spam-Level: 
X-Spam-Status: No, score=-6.592 tagged_above=-999 required=5 tests=[AWL=0.007,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zCgWd6xa8Exe; Sat, 11 Aug 2012 07:47:55 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id E0B4821F8496; Sat, 11 Aug 2012 07:47:55 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q7BElsGT013457 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 11 Aug 2012 07:47:55 -0700
Message-ID: <5026708E.8080708@dcrocker.net>
Date: Sat, 11 Aug 2012 07:47:42 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Eric Burger <eburger@standardstrack.com>
Subject: Re: Last Call: Modern Global Standards Paradigm
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <CAMm+Lwio8=EyW-=LZE8BA4=6N=H4f7a1Nycg25LxB920ceZ6JA@mail.gmail.com> <1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.com>
In-Reply-To: <1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.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, 11 Aug 2012 07:47:55 -0700 (PDT)
Cc: IAB <iab@iab.org>, IETF list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 14:47:56 -0000

On 8/10/2012 3:52 PM, Eric Burger wrote:
> Just as it is not fair to say that if the ITU-T gets its way the
> world will end, it is also not fair to say there is no risk to
> allowing the ITU-T to get a privileged, NON-VOLUNTARY, position in
> the communications world.


Given the historical example of GOSIP, and its ilk, that you cited, we 
actually do have a basis for believing that a similar arrangement now 
will do quite a bit of damage.

The difference in timeliness and pragmatics between a voluntary, 
industry-collaborative effort like the IETF's, versus a legally-enforced 
position like the ITU's work, has already been demonstrated.

The latter never got their system running at scale.

Occasionally in an email presentation, I'll ask an audience who among 
them is familiar with X.400.  Very few hands get raised, yet for 15 
years, it was in exactly the legally-enforced position being proposed now.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From john-ietf@jck.com  Sat Aug 11 07:56:55 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1525221F8466; Sat, 11 Aug 2012 07:56:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.586
X-Spam-Level: 
X-Spam-Status: No, score=-102.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QCsdVSXYgM0x; Sat, 11 Aug 2012 07:56:54 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 29AA721F8464; Sat, 11 Aug 2012 07:56:54 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1T0D1R-0006he-Ug; Sat, 11 Aug 2012 10:50:37 -0400
Date: Sat, 11 Aug 2012 10:56:38 -0400
From: John C Klensin <john-ietf@jck.com>
To: Eric Burger <eburger@standardstrack.com>, Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: Last Call: Modern Global Standards Paradigm
Message-ID: <276B7D303A96E840D2F95107@JcK-HP8200.jck.com>
In-Reply-To: <1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.com>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <CAMm+Lwio8=EyW-=LZE8BA4=6N=H4f7a1Nycg25LxB920ceZ6JA@mail.gmail.com> <1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.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: IAB <iab@iab.org>, IETF list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 14:56:55 -0000

--On Friday, August 10, 2012 15:52 -0700 Eric Burger
<eburger@standardstrack.com> wrote:

> PLEASE, PLEASE, PLEASE read what the proposal is. The proposal
> being put forth is not that the ITU-T wants to write Internet
> standards. The proposal being put forth is that ONLY ITU-T
> standards will be the *legal* standards accepted by signatory
> nations.

> At best, this would be a repeat of GOSIP in the U.S., where
> the law was the U.S. government could only buy OSI products.
> The issue there was the private sector was still free to buy
> what it wanted and DoD did not really follow the rules and
> bought TCP/IP instead. TCP/IP in the market killed OSI.
>...

Eric,

In the interest of understanding our position in this area as
well as possible, I don't think the facts support "TCP/IP in the
market killed OSI" except in a vary narrow sense.  It would be
much more accurate to say that OSI self-destructed and the
TCP/IP was then available as a working technology that satisfied
most of the relevant requirements.  The self-destruction
resulted from some combination of untested specifications that
weren't quite implementable in an interoperable ways, promises
that things would be ready two years in the future (a sliding
target for more than a decade), gradually growing awareness of
excessive complexity and too many options, and possibly other
factors.  

It is worth remembering that in the most critical part of that
period, the IETF wasn't developing/pushing TCP/IP in the
marketplace but had its face firmly immersed in the KoolAid
trough: we even had a TCP/IP transition area  into the 90s.  I
might even suggest that we have abandoned the principle of
simple and clear protocols with few options and, in a few cases,
adopted the "reach consensus by giving all sides their own set
of options" model that was arguably a large component of what
made the OSI suite vunerable to self-destruction.  The
once-legendary speed with which we could do things has also
yielded to a larger and more process-encumbered IETF.   Today,
we may have more to fear from ourselves than from the ITU.

None of that has anything to do with whether the proposed
statement is appropriate.

> The difference here is some countries may take their ITR
> obligations literally and ban products that use non-ITU
> protocols. Could one go to jail for using TCP/IP or HTTP? That
> has an admittedly small, but not insignificant possibility of
> happening.

What happened last time was that a number of countries banned
their communications carriers from carrying TCP/IP (or anything
else) that didn't run over ITU protocols.  Unsurprisingly, those
bans were fairly effective in countries that were serious about
them -- and that list of countries was not limited to
out-of-the-way developing nations.

Whether that would be realistic today is another question.  The
Internet is fairly entrenched, things have not gone well for
countries who have tried to cut it off once it is well
established, and some experts have even suggested that excessive
restrictions on the Internet might constitute a non-tariff trade
barrier.  Relative to the latter and in these fragile economic
times, one can only speculate on whether countries are more
afraid of trade limitations and sanctions than of the ITU.
More important, as Phillip (with whom I generally disagree on
these sorts of matters) has pointed out, there is a long and
rather effective history of what countries do when a UN body's
behavior operates significantly against their national
interests: they refuse to sign the treaties and, in severe
cases, withdraw and stop paying dues and assessments.
Remembering that there is no such thing as a Sector Member from
a non-Member country, someone who was very cynical about these
things might even suggest that the most effective way to get the
ITU out of the Internet would be to have them pass these
measures in their most extreme form with the medium-term result
of wrecking their budget and, with it, their ability to
function.   Or one might speculate that is the reason why ITU's
senior leadership appears to have largely backed away from the
most extreme of those proposals.

> Worse yet, having treaties that obligates countries
> to ban non-ITU protocols does virtually guarantee a
> balkanization of the Internet into open and free networking
> and controlled and censored networking.

A form of that risk exists whether such treaties are created or
not.  If a country considers it sufficiently necessary to its
national interest to withdraw from the Internet and adopt a
different and non-interoperable set of protocols, it will almost
certainly do so with or without approval from Geneva.  I believe
we should make that process as easy as possible for them,
designing things so that they can't hurt others when they do so.
Countries who isolate themselves from contemporary
communications technologies have not been treated well by
history, economics, or their own populations.

We also should not discount some possible advantages: for
example, the withdrawal of a few selected countries from the
Internet and enforced requirements there to use only
non-interoperable protocols could do wonders to reduce the
amount of malicious spam introduced into the network.  :-(

> Just as it is not fair to say that if the ITU-T gets its way
> the world will end, it is also not fair to say there is no
> risk to allowing the ITU-T to get a privileged, NON-VOLUNTARY,
> position in the communications world.

Certainly there are risks.  And certainly we should be aware of
those risks and think through the various strategies we and
others might adopt.  But let's not confuse ourselves with
specious arguments about disaster scenarios.

Again, it seems to me that none of the above has much to do with
whether this statement should be issued.

   john


From dhc@dcrocker.net  Sat Aug 11 08:11:31 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C875521F8514; Sat, 11 Aug 2012 08:11:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.592
X-Spam-Level: 
X-Spam-Status: No, score=-6.592 tagged_above=-999 required=5 tests=[AWL=0.007,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5amFF09fymBQ; Sat, 11 Aug 2012 08:11:31 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3361221F84FB; Sat, 11 Aug 2012 08:11:31 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q7BFBQ8Q013797 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 11 Aug 2012 08:11:27 -0700
Message-ID: <50267612.2030301@dcrocker.net>
Date: Sat, 11 Aug 2012 08:11:14 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: IETF list <ietf@ietf.org>
Subject: Re: Last Call: Modern Global Standards Paradigm
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <CAMm+Lwio8=EyW-=LZE8BA4=6N=H4f7a1Nycg25LxB920ceZ6JA@mail.gmail.com> <1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.com> <276B7D303A96E840D2F95107@JcK-HP8200.jck.com>
In-Reply-To: <276B7D303A96E840D2F95107@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sat, 11 Aug 2012 08:11:28 -0700 (PDT)
Cc: IAB <iab@iab.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, 11 Aug 2012 15:11:31 -0000

On 8/11/2012 7:56 AM, John C Klensin wrote:
>      I don't think the facts support "TCP/IP in the
> market killed OSI" except in a vary narrow sense.  It would be
> much more accurate to say that OSI self-destructed and the
> TCP/IP was then available as a working technology that satisfied
> most of the relevant requirements.


Not really.

In much of the world, OSI created the market demand for open systems. 
And yes, TCP/IP filled it when OSI couldn't.  (In the late 80s, 25% of 
my TCP/IP product revenue was from Europe, including the IT department 
at ISO...)

However had there been no TCP/IP, the OSI folks would have had to find a 
way to make their stuff work.  While we like to think that original 
design decisions for OSI are what killed it, there's plenty of 
experience showing that really bad designs can be made viable, given 
enough effort.[1]

The underlying problems with OSI design made success for OSI massively 
more difficult.  However failure would not have been allowed had they 
been the only game in town.

The presence of a viable and -- ahem -- superior alternative to OSI is 
what finally killed it, by diverting market interest to the alternative.


d/

[1] The IETF-based characterization of this was by Marshall Rose:  With 
enough thrust, pigs /can/ fly.

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From cabo@tzi.org  Sat Aug 11 08:13:37 2012
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02BE421F852E; Sat, 11 Aug 2012 08:13:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.341
X-Spam-Level: 
X-Spam-Status: No, score=-106.341 tagged_above=-999 required=5 tests=[AWL=-0.092, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jV5bRiLroIKK; Sat, 11 Aug 2012 08:13:33 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id B7A8B21F84F3; Sat, 11 Aug 2012 08:13:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q7BFDIgJ005098; Sat, 11 Aug 2012 17:13:18 +0200 (CEST)
Received: from [192.168.217.117] (p54894979.dip.t-dialin.net [84.137.73.121]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 40A71A65; Sat, 11 Aug 2012 17:13:18 +0200 (CEST)
Subject: Re: Re: [IAB] Last Call: Modern Global Standards Paradigm
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <50266F05.5050601@dcrocker.net>
Date: Sat, 11 Aug 2012 17:13:17 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org>
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com> <50266F05.5050601@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1485)
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 15:13:37 -0000

On Aug 11, 2012, at 16:41, Dave Crocker <dhc@dcrocker.net> wrote:

> consensus-oriented process

Sometimes, though, you have to act.

While a consensus-oriented process*) document could certainly be used to =
improve (or deteriorate) the document by a couple more epsilons, I agree =
with Randy Bush: Signing it now is a no-brainer.

Gr=FC=DFe, Carsten

*) Well there was a call for comments, and it already supplied the first =
such set of epsilons. =20
That may have to do when time is of the essence.

(That's also what you choose your leadership for. =20
If we don't like the outcome, we can always decide not to re-elect Russ =
:-)


From dcrocker@bbiw.net  Sat Aug 11 08:20:20 2012
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2E3B21F857D; Sat, 11 Aug 2012 08:20:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.554
X-Spam-Level: 
X-Spam-Status: No, score=-6.554 tagged_above=-999 required=5 tests=[AWL=0.045,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WBWlcK40gj21; Sat, 11 Aug 2012 08:20:20 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 202B221F8568; Sat, 11 Aug 2012 08:20:20 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q7BFKIxC013933 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 11 Aug 2012 08:20:19 -0700
Message-ID: <50267826.70307@bbiw.net>
Date: Sat, 11 Aug 2012 08:20:06 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: [IAB] Last Call: Modern Global Standards Paradigm
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com> <50266F05.5050601@dcrocker.net> <1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org>
In-Reply-To: <1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sat, 11 Aug 2012 08:20:20 -0700 (PDT)
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 15:20:20 -0000

On 8/11/2012 8:13 AM, Carsten Bormann wrote:
> On Aug 11, 2012, at 16:41, Dave Crocker <dhc@dcrocker.net> wrote:
>> consensus-oriented process
>
> Sometimes, though, you have to act.
>
> While a consensus-oriented process*) document could certainly be used
> to improve (or deteriorate) the document by a couple more epsilons, I
> agree with Randy Bush: Signing it now is a no-brainer.


I wasn't commenting on document editing.  (It actually needs a serious 
editing pass, but I understand that the current situation mitigates 
against pursuing that.)

My point was that we have a process for assessing IETF support and it's 
not being used.  Something quite different is being used.

I'm not arguing against the document, but merely noting that an 
implication of IETF community support is going to be present, but in the 
absence of our having followed the process that makes that (formally) 
correct.

Bureaucracy sucks.  It's a hassle. It's always more appealing to just do 
whatever we feel like that feels reasonable because we have good intent.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From brian.e.carpenter@gmail.com  Sat Aug 11 08:20:21 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4523721F857D for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 08:20:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.49
X-Spam-Level: 
X-Spam-Status: No, score=-101.49 tagged_above=-999 required=5 tests=[AWL=0.201, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pblyi7thI3M0 for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 08:20:20 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 99AD321F8569 for <ietf@ietf.org>; Sat, 11 Aug 2012 08:20:20 -0700 (PDT)
Received: by weyu54 with SMTP id u54so1827036wey.31 for <ietf@ietf.org>; Sat, 11 Aug 2012 08:20:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=VVmyKCzxaJe/R1yHb/19oXUqvD08WdI+4Unzc3X7EXQ=; b=NT0OWl0Igocq4E7Q/Yv8Nq1rJLbXEGfRJzAO59JXyHhsvgQnW1Rfv9Yb4w0WRCc6f5 xEJG8kRh1S35ld1cP7CFh4BfvfsthYQVor0/jfuhYB8Af6yWwI1viO4+yDB2QtPlJTOh lg17w952J10AnSx8yOOgBSuM2XAbyfpocjvU5iAOylD0DTVhssnPwyat78bZp25zGZZo x8wBbAlKtd/7cXIesSVDkX6mbdPHzEBRC+2EAlbArEG9Ze2Nr4Tsf7N3Ha0wT8FDiH9v 98Dq+At4++C//kHaXJnBK+ZFWwgYe/bNRRRYKzDNhsF3Wpo3yNGcu8w70+y2UQS7Hfdd E3QQ==
Received: by 10.180.86.133 with SMTP id p5mr4421445wiz.17.1344698419776; Sat, 11 Aug 2012 08:20:19 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-38.as13285.net. [2.102.217.38]) by mx.google.com with ESMTPS id l6sm4670098wiz.4.2012.08.11.08.20.18 (version=SSLv3 cipher=OTHER); Sat, 11 Aug 2012 08:20:18 -0700 (PDT)
Message-ID: <50267840.5090001@gmail.com>
Date: Sat, 11 Aug 2012 16:20:32 +0100
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: VS:  Re: [IAB] Last Call: Modern Global Standards Paradigm
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com> <50266F05.5050601@dcrocker.net>
In-Reply-To: <50266F05.5050601@dcrocker.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 15:20:21 -0000

On 11/08/2012 15:41, Dave Crocker wrote:
>=20
>> Aihe: Re: [IAB] Last Call: Modern Global Standards Paradigm
>> L=C3=A4hett=C3=A4j=C3=A4: "Eggert, Lars" <lars@netapp.com>
> ...
>> (I'd even co-sign for the IRTF, but I think that isn't really
>> appropriate in this case.)
>=20
>=20
> The "for the IRTF" underscores a possible concern in the current situat=
ion.
>=20
> The perception will certainly be that the IAB and IETF chairs' signatur=
e
> do represent the support of the IETF.
>=20
> But we are a consensus-oriented group and we have not had anything that=

> even hints at a consensus-oriented process to authorize that
> representation.

Dave,

I wasn't in Vancouver, nor even listening to the audio stream, so I can't=

comment on what happened there. However, the discussion here (e.g. on
the "ITU-T Dubai Meeting" thread) and the previous opportunity to comment=

on the proposed statement, which has resulted in changes, strikes me as
an open discussion of the kind we expect in the IETF. When the goal
is agreed wording between several organisations, and it seems clear
that the two chairs are representing the ethos of the IETF in the
discussion, I don't see how we can reasonably ask for more in the
time available.

    Brian


From dhc@dcrocker.net  Sat Aug 11 08:20:44 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D2EB21F84CD; Sat, 11 Aug 2012 08:20:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.592
X-Spam-Level: 
X-Spam-Status: No, score=-6.592 tagged_above=-999 required=5 tests=[AWL=0.007,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9TzhmVTETdhk; Sat, 11 Aug 2012 08:20:43 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id B083321F8496; Sat, 11 Aug 2012 08:20:43 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q7BFKgnf013957 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 11 Aug 2012 08:20:43 -0700
Message-ID: <5026783E.301@dcrocker.net>
Date: Sat, 11 Aug 2012 08:20:30 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: [IAB] Last Call: Modern Global Standards Paradigm
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com> <50266F05.5050601@dcrocker.net> <1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org>
In-Reply-To: <1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sat, 11 Aug 2012 08:20:43 -0700 (PDT)
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 15:20:44 -0000

On 8/11/2012 8:13 AM, Carsten Bormann wrote:
> On Aug 11, 2012, at 16:41, Dave Crocker <dhc@dcrocker.net> wrote:
>> consensus-oriented process
>
> Sometimes, though, you have to act.
>
> While a consensus-oriented process*) document could certainly be used
> to improve (or deteriorate) the document by a couple more epsilons, I
> agree with Randy Bush: Signing it now is a no-brainer.


I wasn't commenting on document editing.  (It actually needs a serious 
editing pass, but I understand that the current situation mitigates 
against pursuing that.)

My point was that we have a process for assessing IETF support and it's 
not being used.  Something quite different is being used.

I'm not arguing against the document, but merely noting that an 
implication of IETF community support is going to be present, but in the 
absence of our having followed the process that makes that (formally) 
correct.

Bureaucracy sucks.  It's a hassle. It's always more appealing to just do 
whatever we feel like that feels reasonable because we have good intent.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From jnc@mercury.lcs.mit.edu  Sat Aug 11 08:20:53 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 237F621F8568 for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 08:20:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.336
X-Spam-Level: 
X-Spam-Status: No, score=-6.336 tagged_above=-999 required=5 tests=[AWL=0.263,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id htX+0K1AEAAh for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 08:20:52 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 02BA121F850B for <ietf@ietf.org>; Sat, 11 Aug 2012 08:20:50 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id C979718C132; Sat, 11 Aug 2012 11:20:49 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Last Call: Modern Global Standards Paradigm
Message-Id: <20120811152049.C979718C132@mercury.lcs.mit.edu>
Date: Sat, 11 Aug 2012 11:20:49 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: iab@iab.org, jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 15:20:53 -0000

    > From: John C Klensin <john-ietf@jck.com>

    > It is worth remembering that in the most critical part of that period,
    > the IETF wasn't developing/pushing TCP/IP in the marketplace but had
    > its face firmly immersed in the KoolAid trough

Ahem. There were quite a few of us in the IETF sphere who were not at all
fans of the OSI stack - and we worked very hard on TCP/IP, and the deployment
thereof, precisely to kill the OSI stack.

No disagreement with your other comments, just that one point.

	Noel

From hallam@gmail.com  Sat Aug 11 09:51:43 2012
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D775921F858A for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 09:51:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.44
X-Spam-Level: 
X-Spam-Status: No, score=-5.44 tagged_above=-999 required=5 tests=[AWL=-1.841,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3q66B5cthC+2 for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 09:51:41 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4F61321F8568 for <ietf@ietf.org>; Sat, 11 Aug 2012 09:51:41 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so4728574obb.31 for <ietf@ietf.org>; Sat, 11 Aug 2012 09:51:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ekeBYLI+wqukRrcSAQ5jqd0Raq3oiz6Q2CDwNxAu3Qw=; b=sv02tRIcmRmZIbKW+leaEUxFpkTglDEFHNd8vef9V656isMJ8JkHOSoSdjvGiP4yQd qIgBgj1PEDJ4wDfQ86/21oagDnykCd3QX8cMSlY+OGQ0kpipOCOtmTcnLWyDHLGxzAgn ReJ2d/T+J40QBzeDKqCeZANhPry7VNRBwaQZCW0kDxiSgUvCZIJT9I74iQY8hezmAigS xg6o8kPBDq6AG6JJ7nfxNsLOGKL1ZCFWbgO2n7DoNvTky939xK7wi0+6RDOnd0xGehPd OQKiA2M5z1XrMXbPCl/ntap3Ux9VqbNYal0TJ4msomz4VEd1ThZeOpxATW/0U+INTbG8 E/1w==
MIME-Version: 1.0
Received: by 10.182.50.103 with SMTP id b7mr3020398obo.15.1344703900958; Sat, 11 Aug 2012 09:51:40 -0700 (PDT)
Received: by 10.76.80.10 with HTTP; Sat, 11 Aug 2012 09:51:40 -0700 (PDT)
In-Reply-To: <276B7D303A96E840D2F95107@JcK-HP8200.jck.com>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <CAMm+Lwio8=EyW-=LZE8BA4=6N=H4f7a1Nycg25LxB920ceZ6JA@mail.gmail.com> <1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.com> <276B7D303A96E840D2F95107@JcK-HP8200.jck.com>
Date: Sat, 11 Aug 2012 12:51:40 -0400
Message-ID: <CAMm+LwjL=tnYrtmHkV+=+VeOCo+1PjAu+pW0LnUyHYhVX_pPZA@mail.gmail.com>
Subject: Re: Last Call: Modern Global Standards Paradigm
From: Phillip Hallam-Baker <hallam@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IAB <iab@iab.org>, IETF list <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 16:51:43 -0000

+1

But do not discount the possibility that inducing the US to withdraw
is the objective of certain parties in this little exercise.

On Sat, Aug 11, 2012 at 10:56 AM, John C Klensin <john-ietf@jck.com> wrote:
>
>
> --On Friday, August 10, 2012 15:52 -0700 Eric Burger
> <eburger@standardstrack.com> wrote:
>
>> PLEASE, PLEASE, PLEASE read what the proposal is. The proposal
>> being put forth is not that the ITU-T wants to write Internet
>> standards. The proposal being put forth is that ONLY ITU-T
>> standards will be the *legal* standards accepted by signatory
>> nations.
>
>> At best, this would be a repeat of GOSIP in the U.S., where
>> the law was the U.S. government could only buy OSI products.
>> The issue there was the private sector was still free to buy
>> what it wanted and DoD did not really follow the rules and
>> bought TCP/IP instead. TCP/IP in the market killed OSI.
>>...
>
> Eric,
>
> In the interest of understanding our position in this area as
> well as possible, I don't think the facts support "TCP/IP in the
> market killed OSI" except in a vary narrow sense.  It would be
> much more accurate to say that OSI self-destructed and the
> TCP/IP was then available as a working technology that satisfied
> most of the relevant requirements.  The self-destruction
> resulted from some combination of untested specifications that
> weren't quite implementable in an interoperable ways, promises
> that things would be ready two years in the future (a sliding
> target for more than a decade), gradually growing awareness of
> excessive complexity and too many options, and possibly other
> factors.
>
> It is worth remembering that in the most critical part of that
> period, the IETF wasn't developing/pushing TCP/IP in the
> marketplace but had its face firmly immersed in the KoolAid
> trough: we even had a TCP/IP transition area  into the 90s.  I
> might even suggest that we have abandoned the principle of
> simple and clear protocols with few options and, in a few cases,
> adopted the "reach consensus by giving all sides their own set
> of options" model that was arguably a large component of what
> made the OSI suite vunerable to self-destruction.  The
> once-legendary speed with which we could do things has also
> yielded to a larger and more process-encumbered IETF.   Today,
> we may have more to fear from ourselves than from the ITU.
>
> None of that has anything to do with whether the proposed
> statement is appropriate.
>
>> The difference here is some countries may take their ITR
>> obligations literally and ban products that use non-ITU
>> protocols. Could one go to jail for using TCP/IP or HTTP? That
>> has an admittedly small, but not insignificant possibility of
>> happening.
>
> What happened last time was that a number of countries banned
> their communications carriers from carrying TCP/IP (or anything
> else) that didn't run over ITU protocols.  Unsurprisingly, those
> bans were fairly effective in countries that were serious about
> them -- and that list of countries was not limited to
> out-of-the-way developing nations.
>
> Whether that would be realistic today is another question.  The
> Internet is fairly entrenched, things have not gone well for
> countries who have tried to cut it off once it is well
> established, and some experts have even suggested that excessive
> restrictions on the Internet might constitute a non-tariff trade
> barrier.  Relative to the latter and in these fragile economic
> times, one can only speculate on whether countries are more
> afraid of trade limitations and sanctions than of the ITU.
> More important, as Phillip (with whom I generally disagree on
> these sorts of matters) has pointed out, there is a long and
> rather effective history of what countries do when a UN body's
> behavior operates significantly against their national
> interests: they refuse to sign the treaties and, in severe
> cases, withdraw and stop paying dues and assessments.
> Remembering that there is no such thing as a Sector Member from
> a non-Member country, someone who was very cynical about these
> things might even suggest that the most effective way to get the
> ITU out of the Internet would be to have them pass these
> measures in their most extreme form with the medium-term result
> of wrecking their budget and, with it, their ability to
> function.   Or one might speculate that is the reason why ITU's
> senior leadership appears to have largely backed away from the
> most extreme of those proposals.
>
>> Worse yet, having treaties that obligates countries
>> to ban non-ITU protocols does virtually guarantee a
>> balkanization of the Internet into open and free networking
>> and controlled and censored networking.
>
> A form of that risk exists whether such treaties are created or
> not.  If a country considers it sufficiently necessary to its
> national interest to withdraw from the Internet and adopt a
> different and non-interoperable set of protocols, it will almost
> certainly do so with or without approval from Geneva.  I believe
> we should make that process as easy as possible for them,
> designing things so that they can't hurt others when they do so.
> Countries who isolate themselves from contemporary
> communications technologies have not been treated well by
> history, economics, or their own populations.
>
> We also should not discount some possible advantages: for
> example, the withdrawal of a few selected countries from the
> Internet and enforced requirements there to use only
> non-interoperable protocols could do wonders to reduce the
> amount of malicious spam introduced into the network.  :-(
>
>> Just as it is not fair to say that if the ITU-T gets its way
>> the world will end, it is also not fair to say there is no
>> risk to allowing the ITU-T to get a privileged, NON-VOLUNTARY,
>> position in the communications world.
>
> Certainly there are risks.  And certainly we should be aware of
> those risks and think through the various strategies we and
> others might adopt.  But let's not confuse ourselves with
> specious arguments about disaster scenarios.
>
> Again, it seems to me that none of the above has much to do with
> whether this statement should be issued.
>
>    john
>



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

From d3e3e3@gmail.com  Sat Aug 11 10:13:22 2012
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D482421F85D6 for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 10:13:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.522
X-Spam-Level: 
X-Spam-Status: No, score=-103.522 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j5Fca1OMnA4f for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 10:13:22 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1DB4921F85C3 for <ietf@ietf.org>; Sat, 11 Aug 2012 10:13:22 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so4755316obb.31 for <ietf@ietf.org>; Sat, 11 Aug 2012 10:13:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=1ABqO6IHkkSRpTyAjCY27ECy/G8hgHWgxLm8D0z2R+E=; b=mJdn/KAwSjdVHeSEV0mK4gmsdmyIiPPX1Plok9FCVytlxC8e7KYZueNVGz+xCmZqO0 DVOc7AVDCq8gQ0pV8OxX+4M7TP9B+Cbl7yJqvagJ9pQP/YAkR5tvQHblS1YqjmxjCKT2 NXoQOPAOQxphcuVIWxM5zxcuoWaU+2Mo73mjihxw4gnu3SmbovVHiJdG0O5AHixiVN0A dsRldtlytglsaW5bAy0xFIfEhf8kZ+fKehkE5oCfiELlRk4J7elO4NF2ja4NyEOrWmiB PpkTdxELS1Y2p4LTUjzUAvgzB/RAGnaa72KvfQeD9Qkn6xmHEpQRVvB+m0S/yZwl93u9 wFWw==
Received: by 10.50.57.168 with SMTP id j8mr1459143igq.16.1344705201539; Sat, 11 Aug 2012 10:13:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.15.6 with HTTP; Sat, 11 Aug 2012 10:13:01 -0700 (PDT)
In-Reply-To: <C2796AD0-6361-4EE0-B97B-5443D685215F@virtualized.org>
References: <CD5674C3CD99574EBA7432465FC13C1B22726A0C08@DC-US1MBEX4.global.avaya.com> <CAA=duU0_L9PUdJdFYzmQgpKSpCxcpiBfYE8Tj50+UQpyuLF6vA@mail.gmail.com> <C2796AD0-6361-4EE0-B97B-5443D685215F@virtualized.org>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sat, 11 Aug 2012 13:13:01 -0400
Message-ID: <CAF4+nEEKjSpfyDGPaYeJE6XaG9u4GZPkW5eft94MVgyM3_hxMw@mail.gmail.com>
Subject: Re: ITU-T Dubai Meeting and IPv15
To: David Conrad <drc@virtualized.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 17:13:22 -0000

One problem with excessively large fields, including variable length
addresses with a high maximum length, is that the next time someone
wants to encode some additional information, they just tuck it inside
that field in some quasi-proprietary way, instead of going to the
trouble of actually adding a field. Witness X.509 Certificate "serial
numbers", which are arbitrary precision integers, but which frequently
are used for a variety of information, all BER encoded...

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


On Fri, Aug 10, 2012 at 1:35 PM, David Conrad <drc@virtualized.org> wrote:
> On Aug 10, 2012, at 10:22 AM, "Andrew G. Malis" <agmalis@gmail.com> wrote:
>> Another alternative is self-describing variable-length addresses,
>> again do it once and we'll never have to worry about it again.
>
> Heretic!  That's OSI speak!  Why do you hate the Internet you ISO/ITU lackey?!?
>
> </flashback>
>
> Yeah, variable-length addresses would have been nice. There was even working code. Maybe next IPng.
>
> Regards,
> -drc
>

From john-ietf@jck.com  Sat Aug 11 10:17:14 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F61A21F8484; Sat, 11 Aug 2012 10:17:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.586
X-Spam-Level: 
X-Spam-Status: No, score=-102.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fnlv0yiCoJAp; Sat, 11 Aug 2012 10:17:13 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C55EA21F847C; Sat, 11 Aug 2012 10:17:13 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1T0FDF-0007EZ-GB; Sat, 11 Aug 2012 13:10:57 -0400
Date: Sat, 11 Aug 2012 13:16:58 -0400
From: John C Klensin <john-ietf@jck.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: Last Call: Modern Global Standards Paradigm
Message-ID: <C01C22690CE178AF8C2E52F7@JcK-HP8200.jck.com>
In-Reply-To: <CAMm+LwjL=tnYrtmHkV+=+VeOCo+1PjAu+pW0LnUyHYhVX_pPZA@mail.gmail.com>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <CAMm+Lwio8=EyW-=LZE8BA4=6N=H4f7a1Nycg25LxB920ceZ6JA@mail.gmail.com> <1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.com> <276B7D303A96E840D2F95107@JcK-HP8200.jck.com> <CAMm+LwjL=tnYrtmHkV+=+VeOCo+1PjAu+pW0LnUyHYhVX_pPZA@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: IAB <iab@iab.org>, IETF list <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 17:17:14 -0000

--On Saturday, August 11, 2012 12:51 -0400 Phillip Hallam-Baker
<hallam@gmail.com> wrote:

>...
> But do not discount the possibility that inducing the US to
> withdraw is the objective of certain parties in this little
> exercise.

Given the fraction of the ITU budget and the even larger
fraction of the T-Sector budget that come from the US and
US-based Sector Members, that would be fairly irrational
behavior for those who wanted to preserve a healthy and
well-staffed ITU.  On the other hand, irrational behavior would
be nothing new in this area so I can't disagree with the
possibility.

    john




From john-ietf@jck.com  Sat Aug 11 10:27:58 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EC4221F85ED; Sat, 11 Aug 2012 10:27:58 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ih1bTILJHd4x; Sat, 11 Aug 2012 10:27:57 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 86EF221F85C3; Sat, 11 Aug 2012 10:27:57 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1T0FNX-0007GW-4c; Sat, 11 Aug 2012 13:21:35 -0400
Date: Sat, 11 Aug 2012 13:27:36 -0400
From: John C Klensin <john-ietf@jck.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
Subject: Re: Last Call: Modern Global Standards Paradigm
Message-ID: <E92890DCED7635992BB03E4E@JcK-HP8200.jck.com>
In-Reply-To: <20120811152049.C979718C132@mercury.lcs.mit.edu>
References: <20120811152049.C979718C132@mercury.lcs.mit.edu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: iab@iab.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 17:27:58 -0000

--On Saturday, August 11, 2012 11:20 -0400 Noel Chiappa
<jnc@mercury.lcs.mit.edu> wrote:

>     > From: John C Klensin <john-ietf@jck.com>
> 
>     > It is worth remembering that in the most critical part
> of that period,     > the IETF wasn't developing/pushing
> TCP/IP in the marketplace but had     > its face firmly
> immersed in the KoolAid trough
> 
> Ahem. There were quite a few of us in the IETF sphere who were
> not at all fans of the OSI stack - and we worked very hard on
> TCP/IP, and the deployment thereof, precisely to kill the OSI
> stack.

Noel,

I didn't mean to suggest otherwise, only that there was
sufficient IETF consensus to keep an Area and, if I recall,
several WGs going.  

    john



From stbryant@cisco.com  Sat Aug 11 10:41:10 2012
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3226D21F84F2 for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 10:41:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.584
X-Spam-Level: 
X-Spam-Status: No, score=-110.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LTjkfEnQeaUC for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 10:41:09 -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 6109F21F84F1 for <ietf@ietf.org>; Sat, 11 Aug 2012 10:41:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=433; q=dns/txt; s=iport; t=1344706869; x=1345916469; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to:content-transfer-encoding; bh=AwNSO2v7U3BjQrhwM2bQMrb6N80KoiRj0M8vcdeItEw=; b=mdJ93Gu5LOw553JZ5cU4V5cs31aft+NK3yTi0aL9r/VSP+1iiWwFL0le QcFrv5MkpzQdpQAdiHNYBAlcZs+FCN/TNgVRSx4SJKFnjqYW6y86aavqx e0a+PHDAPfN173LaqCDnkt8tAfgx4+va2YYflC5pRYZ6FAQGdveZlD+4l Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiEFAF6YJlCQ/khR/2dsb2JhbABFhTpHs3iBB4IgAQEBBBIBAg4VNwkRCxgCAgUWCwICCQMCAQIBRRMIAQEeh2sLmEyDSBCJQZJagSGJcYMVggqBEgOVS44qgQRigmA
X-IronPort-AV: E=Sophos;i="4.77,751,1336348800"; d="scan'208";a="142294816"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-1.cisco.com with ESMTP; 11 Aug 2012 17:41:08 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q7BHf7uK016435 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Sat, 11 Aug 2012 17:41:08 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q7BHf5J9016823; Sat, 11 Aug 2012 18:41:06 +0100 (BST)
Message-ID: <50269931.4020502@cisco.com>
Date: Sat, 11 Aug 2012 18:41:05 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [MARKETING] Re: VS: Re: [IAB] Last Call: Modern Global Standards Paradigm
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com> <50266F05.5050601@dcrocker.net> <50267840.5090001@gmail.com>
In-Reply-To: <50267840.5090001@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Sat, 11 Aug 2012 17:41:10 -0000

On 11/08/2012 16:20, Brian E Carpenter wrote:
> When the goal is agreed wording between several organisations, and it 
> seems clear that the two chairs are representing the ethos of the IETF 
> in the discussion, I don't see how we can reasonably ask for more in 
> the time available. Brian 

+1

Stewart

-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


From joelja@bogus.com  Sat Aug 11 10:46:43 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEFB621F85FC for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 10:46:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.066
X-Spam-Level: 
X-Spam-Status: No, score=-102.066 tagged_above=-999 required=5 tests=[AWL=0.533, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x2SaaPkbW-Kj for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 10:46:43 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 0E49921F857D for <ietf@ietf.org>; Sat, 11 Aug 2012 10:46:36 -0700 (PDT)
Received: from joels-MacBook-Air.local (66.sub-166-250-37.myvzw.com [166.250.37.66]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q7BHkWvG099622 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sat, 11 Aug 2012 17:46:33 GMT (envelope-from joelja@bogus.com)
Message-ID: <50269A73.6020304@bogus.com>
Date: Sat, 11 Aug 2012 10:46:27 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120731 Thunderbird/15.0
MIME-Version: 1.0
To: Donald Eastlake <d3e3e3@gmail.com>
Subject: Re: ITU-T Dubai Meeting and IPv15
References: <CD5674C3CD99574EBA7432465FC13C1B22726A0C08@DC-US1MBEX4.global.avaya.com> <CAA=duU0_L9PUdJdFYzmQgpKSpCxcpiBfYE8Tj50+UQpyuLF6vA@mail.gmail.com> <C2796AD0-6361-4EE0-B97B-5443D685215F@virtualized.org> <CAF4+nEEKjSpfyDGPaYeJE6XaG9u4GZPkW5eft94MVgyM3_hxMw@mail.gmail.com>
In-Reply-To: <CAF4+nEEKjSpfyDGPaYeJE6XaG9u4GZPkW5eft94MVgyM3_hxMw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sat, 11 Aug 2012 17:46:33 +0000 (UTC)
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 17:46:43 -0000

On 8/11/12 10:13 AM, Donald Eastlake wrote:
> One problem with excessively large fields, including variable length
> addresses with a high maximum length, is that the next time someone
> wants to encode some additional information, they just tuck it inside
> that field in some quasi-proprietary way, instead of going to the
> trouble of actually adding a field. Witness X.509 Certificate "serial
> numbers", which are arbitrary precision integers, but which frequently
> are used for a variety of information, all BER encoded...
given various semantic uses of bits within ipv6 addresses that have been 
proposed or which are used informally even with only 128 bits it's 
important to make this distinction. a freely extensible bit field will 
end up with all sorts of garbage in it, that at best is only signficant 
in one context, and at worse is significant in different fashions in 
different contexts.

instead of having an locator-id you have a 
locator-qos-mpls-subscriberid-streetaddress-latlong-id
>
> Thanks,
> Donald
> =============================
>   Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>   155 Beaver Street, Milford, MA 01757 USA
>   d3e3e3@gmail.com
>
>
> On Fri, Aug 10, 2012 at 1:35 PM, David Conrad <drc@virtualized.org> wrote:
>> On Aug 10, 2012, at 10:22 AM, "Andrew G. Malis" <agmalis@gmail.com> wrote:
>>> Another alternative is self-describing variable-length addresses,
>>> again do it once and we'll never have to worry about it again.
>> Heretic!  That's OSI speak!  Why do you hate the Internet you ISO/ITU lackey?!?
>>
>> </flashback>
>>
>> Yeah, variable-length addresses would have been nice. There was even working code. Maybe next IPng.
>>
>> Regards,
>> -drc
>>


From nurit.sprecher@nsn.com  Sat Aug 11 10:53:32 2012
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 9832321F848A; Sat, 11 Aug 2012 10:53:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.46
X-Spam-Level: 
X-Spam-Status: No, score=-6.46 tagged_above=-999 required=5 tests=[AWL=0.139,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WZyLZaHpmzJ5; Sat, 11 Aug 2012 10:53:32 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id CBAA121F846C; Sat, 11 Aug 2012 10:53:31 -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 q7BHrOwI002262 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 11 Aug 2012 19:53:27 +0200
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q7BHrLip028357; Sat, 11 Aug 2012 19:53:24 +0200
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 11 Aug 2012 19:53:22 +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: Last Call: Modern Global Standards Paradigm
Date: Sat, 11 Aug 2012 19:51:10 +0200
Message-ID: <E4873516F3FC7547BCFE792C7D94039C0236BA57@DEMUEXC013.nsn-intra.net>
In-Reply-To: <06a601cd7740$6fb704d0$4f250e70$@olddog.co.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: Modern Global Standards Paradigm
Thread-Index: AQKADG0ZlSPzGQd8wC2Lw99G+a7b45XuZvoAgAFTzgA=
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <06a601cd7740$6fb704d0$4f250e70$@olddog.co.uk>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: <adrian@olddog.co.uk>, "IETF" <ietf@ietf.org>, "IAB" <iab@iab.org>, "IETF-Announce" <ietf-announce@ietf.org>
X-OriginalArrivalTime: 11 Aug 2012 17:53:22.0272 (UTC) FILETIME=[32D89600:01CD77EA]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 2352
X-purgate-ID: 151667::1344707607-00006F5F-9E4C8756/0-0/0-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, 11 Aug 2012 17:53:32 -0000

I support the IETF and IAB chairs signing the document,
Nurit

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
ext Adrian Farrel
Sent: Saturday, August 11, 2012 12:38 AM
To: 'IETF'; 'IAB'; 'IETF-Announce'
Subject: RE: Last Call: Modern Global Standards Paradigm

Hi Russ,

I am conscious that this text needs to have the consensus of the three
groups
planning to co-sign, and we also need consensus of the IETF community
that you
sign it.

Given the first of these, I think the question you ask is "Are there
strong
objections?" not "Could we wordsmith this so we would be happier with
it?"

Had you asked the second question, I would have been first in line
(actually, I
already sent my thoughts a couple of weeks ago). But I agree there is no
scope
for that at this stage.

Since you asked the other question: No, I have no strong objection, and
I
support this statement being signed by you and the IAB chair.

Thanks,
Adrian

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of IETF Chair
> Sent: 10 August 2012 16:20
> To: IETF-Announce
> Cc: IAB; IETF
> Subject: Last Call: Modern Global Standards Paradigm
>=20
>=20
> The IETF Chair and the IAB Chair intend to sign the Affirmation
> of the Modern Global Standards Paradigm, which can be found
> here:
>=20
>
http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.p
df
>=20
> An earlier version was discussed in plenary, and the IAB Chair called
> for comments on the IETF mail list.  This version includes changes
> that address those comments.
>=20
> Th IETF 84 Administrative plenary minutes have been posted, so that
> discussion can be reviewed if desired.  The minutes are here:
>=20
> http://www.ietf.org/proceedings/84/minutes/minutes-84-iesg-opsplenary
>=20
> On 8 August 2012, the IEEE Standards Association Board of Governors
> approved this version of the document.  The approval process is
> underway at the W3C as well.
>=20
> The IETF Chair and the IAB Chair intend to sign the Affirmation in the
> next few weeks. Please send strong objections to the iab@iab.org
> and the ietf@ietf.org mailing lists by 2012-08-24.
>=20
> Thank you,
>   Russ Housley
>   IETF Chair


From paul.hoffman@vpnc.org  Sat Aug 11 11:10:22 2012
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 E142621F865F; Sat, 11 Aug 2012 11:10:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.582
X-Spam-Level: 
X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rVwkHM9NZ8eY; Sat, 11 Aug 2012 11:10:22 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 608A821F865D; Sat, 11 Aug 2012 11:10:22 -0700 (PDT)
Received: from [10.20.30.100] (50-1-50-97.dsl.dynamic.fusionbroadband.com [50.1.50.97]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q7BIAKKH055751 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 11 Aug 2012 11:10:21 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: Last Call: Modern Global Standards Paradigm
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <m27gt5y6py.wl%randy@psg.com>
Date: Sat, 11 Aug 2012 11:10:24 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <18D3D2AC-57DD-41D2-A8BD-1D845956E2F4@vpnc.org>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <m27gt5y6py.wl%randy@psg.com>
To: IETF Chair <chair@ietf.org>
X-Mailer: Apple Mail (2.1278)
Cc: IAB <iab@iab.org>, ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 18:10:23 -0000

On Aug 11, 2012, at 5:05 AM, Randy Bush wrote:

>> The IETF Chair and the IAB Chair intend to sign the Affirmation
>> of the Modern Global Standards Paradigm, which can be found
>> here:
>> 
>> http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf
> 
> no brainer.

Even with a brain, the document is obviously good. Please sign it.

--Paul Hoffman

From tobias.gondrom@gondrom.org  Sat Aug 11 11:52:28 2012
Return-Path: <tobias.gondrom@gondrom.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37BF821F85C3 for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 11:52:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.123
X-Spam-Level: 
X-Spam-Status: No, score=-97.123 tagged_above=-999 required=5 tests=[AWL=-1.762, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3eJDucXqRolQ for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 11:52:27 -0700 (PDT)
Received: from lvps176-28-13-69.dedicated.hosteurope.de (lvps176-28-13-69.dedicated.hosteurope.de [176.28.13.69]) by ietfa.amsl.com (Postfix) with ESMTP id 3684221F859B for <ietf@ietf.org>; Sat, 11 Aug 2012 11:52:27 -0700 (PDT)
Received: (qmail 32675 invoked from network); 11 Aug 2012 20:52:25 +0200
Received: from 94-194-102-93.zone8.bethere.co.uk (HELO ?192.168.1.65?) (94.194.102.93) by lvps176-28-13-69.dedicated.hosteurope.de with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 11 Aug 2012 20:52:25 +0200
Message-ID: <5026A9E8.4030602@gondrom.org>
Date: Sat, 11 Aug 2012 19:52:24 +0100
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: chair@ietf.org, ietf@ietf.org
Subject: Re: Last Call: Modern Global Standards Paradigm
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <m27gt5y6py.wl%randy@psg.com> <18D3D2AC-57DD-41D2-A8BD-1D845956E2F4@vpnc.org>
In-Reply-To: <18D3D2AC-57DD-41D2-A8BD-1D845956E2F4@vpnc.org>
Content-Type: multipart/alternative; boundary="------------020605040404040008070208"
Cc: iab@iab.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 18:52:28 -0000

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

On 11/08/12 19:10, Paul Hoffman wrote:
> On Aug 11, 2012, at 5:05 AM, Randy Bush wrote:
>
>>> The IETF Chair and the IAB Chair intend to sign the Affirmation
>>> of the Modern Global Standards Paradigm, which can be found
>>> here:
>>>
>>> http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf
>> no brainer.
> Even with a brain, the document is obviously good. Please sign it.
>
> --Paul Hoffman

Agree and support.
Please sign it.
- Tobias Gondrom

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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 11/08/12 19:10, Paul Hoffman wrote:<br>
    </div>
    <blockquote cite="mid:18D3D2AC-57DD-41D2-A8BD-1D845956E2F4@vpnc.org"
      type="cite">
      <pre wrap="">On Aug 11, 2012, at 5:05 AM, Randy Bush wrote:

</pre>
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">The IETF Chair and the IAB Chair intend to sign the Affirmation
of the Modern Global Standards Paradigm, which can be found
here:

<a class="moz-txt-link-freetext" href="http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf">http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf</a>
</pre>
        </blockquote>
        <pre wrap="">
no brainer.
</pre>
      </blockquote>
      <pre wrap="">
Even with a brain, the document is obviously good. Please sign it.

--Paul Hoffman
</pre>
    </blockquote>
    <font face="Arial"><br>
      Agree and support. <br>
      Please sign it. <br>
      - Tobias Gondrom</font>
  </body>
</html>

--------------020605040404040008070208--

From sm@resistor.net  Sat Aug 11 12:06:00 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3578E21F84C9; Sat, 11 Aug 2012 12:06:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level: 
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zxL98pxOV1OM; Sat, 11 Aug 2012 12:05:56 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C5C121F84C5; Sat, 11 Aug 2012 12:05:56 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q7BJ5nGZ005053; Sat, 11 Aug 2012 12:05:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1344711955; bh=NqE+hHh5mOHTT/tuGrz/coLTqWiMNLU+2SZZkVbKEsY=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=hhJ42Wu4I+njMNS2RzUQnUmBQvEeEcAZbb/bIkNVg62Aysb2Dp2G2Bdj6DmKOBUN5 STsE72Y1UlmDWIaT6jBpx6LBbxfwcXyT3whulPPxIAS1SJJ6bPypDITsH4f7ASvurH Alx2bt7QLJRAUXAOKqvxuBrqciT6Tjl8S0evd2ds=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1344711955; i=@resistor.net; bh=NqE+hHh5mOHTT/tuGrz/coLTqWiMNLU+2SZZkVbKEsY=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=MA5PmCCBZmq2NeiotjG4DddPveXlm88WmBrIU3flOMPpsE5pahb1JyWrguSSSfRBW zEkKcItfptrHj6WI+opTC8qn/VVSYngXnqWM1q1df6xv+HiaGSwoi0HNQO3MOwHVcr vx1KZ3I/4KhGg8qYSZyfJ8VNmD4E4fXP//sfyTPw=
Message-Id: <6.2.5.6.2.20120811080806.0a6b9c38@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 11 Aug 2012 11:41:58 -0700
To: ietf@ietf.org, IAB <iab@iab.org>
From: SM <sm@resistor.net>
Subject: Re: Last Call: Modern Global Standards Paradigm
In-Reply-To: <50266500.6000507@gmail.com>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <CAMm+Lwio8=EyW-=LZE8BA4=6N=H4f7a1Nycg25LxB920ceZ6JA@mail.gmail.com> <1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.com> <CAMm+LwgBhpJhacVLrAYiUJHzEuHifonXNvCz5v5W3MDCaCRwDQ@mail.gmail.com> <50262840.6050305@tana.it> <50266500.6000507@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 19:06:00 -0000

At 06:58 11-08-2012, Brian E Carpenter wrote:
>Traditionally, and still in some countries, the telecommunications
>monopolist *is* the government, so defending the monopoly is directly
>in the government's financial interest. In other countries, where
>there's still a de facto monopoly, that monopolist is very good at
>political lobbying. So in both those types of country, the vested
>interest drives the government position. Add that to the governments
>that want central control and/or monitoring of information, and you
>get a strong bloc of political support for standards and regulations
>that support monopoly, control, and eavesdropping.

Yes.

Nowadays some governments only own a share of the telecommunications 
monopoly.  Other operators, for example some companies who are part 
of the European Telecommunications Network Operators' Association ( 
http://www.etno.be/Default.aspx?tabid=1239 ), have a financial 
interest in these monopolies.

The US does not need central control because most of the content 
accessed by its users is internal traffic.  It's easy to apply local 
laws.  The EU can also use its laws on a country basis.  Revenue 
which is a significant incentive for content providers.  Advertising 
revenue per user for a one content provider is as follows:

   US/Canada  $9.51
   EU         $4.86
   Asia       $1.79
   Other      $1.42

Here is a rough estimate of users for one content provider:

   US     158,758,940
   Brazil  54,902,560
   India   51,925,180
   UK      37,569,580
   France  24,345,920
   Italy   21,822,640
   Canada  17,474,940
   Spain   16,075,560
   Egypt   11,513,720
   Russia   5,560,080
   Romania  4,928,100
   Tunisia  3,107,040
   Libya      608,380
   China      520,780
   Uganda     444,560

If tomorrow Italy decides to adopt a "sending party pays" model it 
may still be financially viable for the content provider to remain in 
that market.  It may not work that well for Uganda.

If tomorrow Libya decides that it would be in its interest to control 
access to the Internet, operators can route around the problem as we 
all know that's how the Internet works.  Well, not really, if most of 
the traffic passes through one international gateway.  You can send 
traffic over port 443 to prevent eavesdropping as that port is 
secure.  Well, not really, if the user already trusts the wrong SSL 
certificate.

If you are on an Internet governance soapbox you might as well talk 
about how the US is evil and it should not be the only country 
running the Internet.  You might also want to add that having only 13 
root nameservers is all part of a conspiracy and that the IETF must 
fix that.  Obviously someone must be running this Internet thing or 
else you will have to review your belief system.

At 07:56 11-08-2012, John C Klensin wrote:
>Remembering that there is no such thing as a Sector Member from
>a non-Member country, someone who was very cynical about these
>things might even suggest that the most effective way to get the
>ITU out of the Internet would be to have them pass these
>measures in their most extreme form with the medium-term result
>of wrecking their budget and, with it, their ability to
>function.   Or one might speculate that is the reason why ITU's

Yes.

>A form of that risk exists whether such treaties are created or
>not.  If a country considers it sufficiently necessary to its
>national interest to withdraw from the Internet and adopt a
>different and non-interoperable set of protocols, it will almost
>certainly do so with or without approval from Geneva.  I believe
>we should make that process as easy as possible for them,
>designing things so that they can't hurt others when they do so.
>Countries who isolate themselves from contemporary
>communications technologies have not been treated well by
>history, economics, or their own populations.

Yes.

>We also should not discount some possible advantages: for
>example, the withdrawal of a few selected countries from the
>Internet and enforced requirements there to use only
>non-interoperable protocols could do wonders to reduce the
>amount of malicious spam introduced into the network.  :-(

There are advantages in everything.

At 08:11 11-08-2012, Dave Crocker wrote:
>[1] The IETF-based characterization of this was by Marshall 
>Rose:  With enough thrust, pigs /can/ fly.

FWIW the original statement was different.

At 08:13 11-08-2012, Carsten Bormann wrote:
>(That's also what you choose your leadership for.
>If we don't like the outcome, we can always decide not to re-elect Russ :-)

I am taking bets on who will be the next IETF Chair. :-)

In traditional telecommunications the cost of sending one MB of data 
is around US$30.  A user can get a one GB Internet subscription for 
the same price.  In the traditional standards organization you don't 
have a say if in the baking of the standard.  In the IETF you wring 
the neck of the WG Chair or Area Director if he/she does not let you 
have a say.

As an anecdote, I was notified that I will be unsubscribed from an 
ISOC mailing list due to technical limitations.  It is unconceivable 
for that to happen in the IETF.

Regards,
-sm 


From Michael.Tuexen@lurchi.franken.de  Sat Aug 11 12:32:21 2012
Return-Path: <Michael.Tuexen@lurchi.franken.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 0E89D21F855B; Sat, 11 Aug 2012 12:32:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Level: 
X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[AWL=0.620,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qsmLbQG-TfUn; Sat, 11 Aug 2012 12:32:20 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id 2B11C21F847C; Sat, 11 Aug 2012 12:32:09 -0700 (PDT)
Received: from [192.168.1.200] (p508FBDE3.dip.t-dialin.net [80.143.189.227]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id E594B1C0B4626; Sat, 11 Aug 2012 21:32:07 +0200 (CEST)
Subject: Re: Last Call: Modern Global Standards Paradigm
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <18D3D2AC-57DD-41D2-A8BD-1D845956E2F4@vpnc.org>
Date: Sat, 11 Aug 2012 21:32:06 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B009802C-119A-4028-8ED0-8E23FDE07ACC@lurchi.franken.de>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <m27gt5y6py.wl%randy@psg.com> <18D3D2AC-57DD-41D2-A8BD-1D845956E2F4@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1278)
Cc: IETF Chair <chair@ietf.org>, ietf list <ietf@ietf.org>, IAB <iab@iab.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 19:32:21 -0000

On Aug 11, 2012, at 8:10 PM, Paul Hoffman wrote:

> On Aug 11, 2012, at 5:05 AM, Randy Bush wrote:
>=20
>>> The IETF Chair and the IAB Chair intend to sign the Affirmation
>>> of the Modern Global Standards Paradigm, which can be found
>>> here:
>>>=20
>>> =
http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf=

>>=20
>> no brainer.
>=20
> Even with a brain, the document is obviously good. Please sign it.
I agree.

Best regards
Michael
>=20
> --Paul Hoffman
>=20


From ynir@checkpoint.com  Sat Aug 11 13:08:20 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7227921F85E1; Sat, 11 Aug 2012 13:08:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.401
X-Spam-Level: 
X-Spam-Status: No, score=-10.401 tagged_above=-999 required=5 tests=[AWL=0.198, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LiclfY9w5z4S; Sat, 11 Aug 2012 13:08:20 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 5EC5B21F85A5; Sat, 11 Aug 2012 13:08:18 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id q7BK8Bxk001293; Sat, 11 Aug 2012 23:08:12 +0300
X-CheckPoint: {5026B89E-0-1B221DC2-4FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Sat, 11 Aug 2012 23:08:11 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: SM <sm@resistor.net>
Date: Sat, 11 Aug 2012 23:08:09 +0300
Subject: Re: Last Call: Modern Global Standards Paradigm
Thread-Topic: Last Call: Modern Global Standards Paradigm
Thread-Index: Ac13/QegZ6+RQXBbR8y2cU9XkWfQOA==
Message-ID: <AD0CD892-F436-4080-ACD6-3A72DCC6CA66@checkpoint.com>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <CAMm+Lwio8=EyW-=LZE8BA4=6N=H4f7a1Nycg25LxB920ceZ6JA@mail.gmail.com> <1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.com> <CAMm+LwgBhpJhacVLrAYiUJHzEuHifonXNvCz5v5W3MDCaCRwDQ@mail.gmail.com> <50262840.6050305@tana.it> <50266500.6000507@gmail.com> <6.2.5.6.2.20120811080806.0a6b9c38@resistor.net>
In-Reply-To: <6.2.5.6.2.20120811080806.0a6b9c38@resistor.net>
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: IAB <iab@iab.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 20:08:20 -0000

On Aug 11, 2012, at 9:41 PM, SM wrote:
> Here is a rough estimate of users for one content provider:
>=20
>   US     158,758,940
>   Brazil  54,902,560
>   India   51,925,180
>   UK      37,569,580
>   France  24,345,920
>   Italy   21,822,640
>   Canada  17,474,940
>   Spain   16,075,560
>   Egypt   11,513,720
>   Russia   5,560,080
>   Romania  4,928,100
>   Tunisia  3,107,040
>   Libya      608,380
>   China      520,780
>   Uganda     444,560
>=20
> If tomorrow Italy decides to adopt a "sending party pays" model it=20
> may still be financially viable for the content provider to remain in=20
> that market.  It may not work that well for Uganda.
>=20
> If tomorrow Libya decides that it would be in its interest to control=20
> access to the Internet, operators can route around the problem as we=20
> all know that's how the Internet works.

These operators are (hypothetically) Libyan citizens, right?  Residents of =
Libya who could go to jail for routing around the problem. Most likely on a=
 charge of espionage.=20

> Well, not really, if most of=20
> the traffic passes through one international gateway. =20

The number of international gateways does not matter, if all the operators =
have to comply with the government's blacklist, or have to install a govern=
ment-mandated policy on a government-mandated firewall.

> You can send=20
> traffic over port 443 to prevent eavesdropping as that port is=20
> secure.  Well, not really, if the user already trusts the wrong SSL=20
> certificate.

Not trusting the certificate just means you get annoying warnings. It won't=
 let you circumvent it. Living in an authoritarian country means you don't =
get to play cat & mouse with your government

> If you are on an Internet governance soapbox you might as well talk=20
> about how the US is evil and it should not be the only country=20
> running the Internet.  You might also want to add that having only 13=20
> root nameservers is all part of a conspiracy and that the IETF must=20
> fix that.  Obviously someone must be running this Internet thing or=20
> else you will have to review your belief system.

I thought it was Al Gore running the Internet from his garage, no?

Yoav=

From ynir@checkpoint.com  Sat Aug 11 13:09:03 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CABF21F85E3; Sat, 11 Aug 2012 13:09:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.404
X-Spam-Level: 
X-Spam-Status: No, score=-10.404 tagged_above=-999 required=5 tests=[AWL=0.195, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c6Gk-YXv46-k; Sat, 11 Aug 2012 13:09:02 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id C518821F85A5; Sat, 11 Aug 2012 13:09:01 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id q7BK8uRV001321; Sat, 11 Aug 2012 23:09:00 +0300
X-CheckPoint: {5026B8CB-1-1B221DC2-4FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Sat, 11 Aug 2012 23:08:56 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Date: Sat, 11 Aug 2012 23:08:54 +0300
Subject: Re: Last Call: Modern Global Standards Paradigm
Thread-Topic: Last Call: Modern Global Standards Paradigm
Thread-Index: Ac13/SJA7E7Hv5wHSFipq6gNxaZmNg==
Message-ID: <9963FA79-3C26-42B4-BD85-DEF08185B967@checkpoint.com>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <m27gt5y6py.wl%randy@psg.com> <18D3D2AC-57DD-41D2-A8BD-1D845956E2F4@vpnc.org>
In-Reply-To: <18D3D2AC-57DD-41D2-A8BD-1D845956E2F4@vpnc.org>
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 Chair <chair@ietf.org>, ietf list <ietf@ietf.org>, IAB <iab@iab.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 20:09:04 -0000

On Aug 11, 2012, at 9:10 PM, Paul Hoffman wrote:

> On Aug 11, 2012, at 5:05 AM, Randy Bush wrote:
>=20
>>> The IETF Chair and the IAB Chair intend to sign the Affirmation
>>> of the Modern Global Standards Paradigm, which can be found
>>> here:
>>>=20
>>> http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.=
pdf
>>=20
>> no brainer.
>=20
> Even with a brain, the document is obviously good. Please sign it.

I'm dubious as to how much influence this will have on the outcome, but +1

Yoav



From jnc@mercury.lcs.mit.edu  Sat Aug 11 13:19:36 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB2E121F8616 for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 13:19:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.344
X-Spam-Level: 
X-Spam-Status: No, score=-6.344 tagged_above=-999 required=5 tests=[AWL=0.255,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YzYARq1QiNRB for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 13:19:36 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 3BCDF21F85D1 for <ietf@ietf.org>; Sat, 11 Aug 2012 13:19:36 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 71FE318C141; Sat, 11 Aug 2012 16:19:35 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Last Call: Modern Global Standards Paradigm
Message-Id: <20120811201935.71FE318C141@mercury.lcs.mit.edu>
Date: Sat, 11 Aug 2012 16:19:35 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 20:19:36 -0000

    > From: Yoav Nir <ynir@checkpoint.com>

    > These operators are (hypothetically) Libyan citizens, right? Residents
    > of Libya who could go to jail for routing around the problem. Most
    > likely on a charge of espionage.

That worked pretty well for Qaddhafi. Oh, wait... Yes, it cost some whom he
did catch, but in the end it didn't (couldn't) save him. He was unable to cut
off the data flow (in and out).

	Noel

From sob@sobco.com  Sat Aug 11 15:51:27 2012
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3938221F84C8; Sat, 11 Aug 2012 15:51:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.389
X-Spam-Level: 
X-Spam-Status: No, score=-0.389 tagged_above=-999 required=5 tests=[AWL=0.106,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kzjP+rXjLu8g; Sat, 11 Aug 2012 15:51:26 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 986C321F84B5; Sat, 11 Aug 2012 15:51:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 2B0F836B8C5E; Sat, 11 Aug 2012 18:51:25 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1vnSjWyUDS64; Sat, 11 Aug 2012 18:51:23 -0400 (EDT)
Received: from [10.0.1.11] (173-166-5-69-newengland.hfc.comcastbusiness.net [173.166.5.69]) by sobco.sobco.com (Postfix) with ESMTPSA id 9981536B8C4C; Sat, 11 Aug 2012 18:51:23 -0400 (EDT)
Subject: Re: Last Call: Modern Global Standards Paradigm
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Scott O Bradner <sob@sobco.com>
In-Reply-To: <18D3D2AC-57DD-41D2-A8BD-1D845956E2F4@vpnc.org>
Date: Sat, 11 Aug 2012 18:51:23 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <194C4246-928F-4D0B-95DF-A4A31540A145@sobco.com>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <m27gt5y6py.wl%randy@psg.com> <18D3D2AC-57DD-41D2-A8BD-1D845956E2F4@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1278)
Cc: IETF Chair <chair@ietf.org>, ietf list <ietf@ietf.org>, IAB <iab@iab.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 22:51:27 -0000

singing this statement is the right thing to do=20

Scott

(responding to a sorta-last-call)

On Aug 11, 2012, at 2:10 PM, Paul Hoffman wrote:

> On Aug 11, 2012, at 5:05 AM, Randy Bush wrote:
>=20
>>> The IETF Chair and the IAB Chair intend to sign the Affirmation
>>> of the Modern Global Standards Paradigm, which can be found
>>> here:
>>>=20
>>> =
http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf=

>>=20
>> no brainer.
>=20
> Even with a brain, the document is obviously good. Please sign it.
>=20
> --Paul Hoffman


From glenzorn@gmail.com  Sat Aug 11 16:01:49 2012
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B41C11E80B8 for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 16:01:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.29
X-Spam-Level: 
X-Spam-Status: No, score=-3.29 tagged_above=-999 required=5 tests=[AWL=0.308,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rzw1y7+2MtjX for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 16:01:49 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id E758611E808E for <ietf@ietf.org>; Sat, 11 Aug 2012 16:01:43 -0700 (PDT)
Received: by pbbrr4 with SMTP id rr4so4903523pbb.31 for <ietf@ietf.org>; Sat, 11 Aug 2012 16:01:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer; bh=d+U7aC+hBhvEt85+rWHL3EzlLySqe+jeUqQY+sC+tgw=; b=TxLOw0VSqqgDTviqUr1mo4Y2Kt7+IKDzuMWv/8DDRBZQAkWAiTmtSAai+ns1rZahaC oKQorOnv9AISV1rH26ZvxLlemHr3xph6C3bshfAoSQTMWM2yfE8BhPnNYcOkCvJwrnzJ uDNGoxzNGujQLGSZhhUEPT9plb0GynKCd2wUxDti7pIF09Qu84Ti3iEN71md1NCMGwyZ pqa2UTE8iQKBeLRnQ7s/kpThhN9HNzQTnrVVSUwdhNqFA8j3FYfSjgIN4NMFBnZfYf2y zi6EKxyGeEfjfZg7dsirXm+3sqzymUfmokG3lANjAs4+MipfYgbiu6Soc5gmdDN1oLDS t6wQ==
Received: by 10.68.197.70 with SMTP id is6mr8299317pbc.64.1344726103740; Sat, 11 Aug 2012 16:01:43 -0700 (PDT)
Received: from [192.168.0.102] (ppp-124-122-161-240.revip2.asianet.co.th. [124.122.161.240]) by mx.google.com with ESMTPS id te10sm2144066pbc.45.2012.08.11.16.01.41 (version=SSLv3 cipher=OTHER); Sat, 11 Aug 2012 16:01:43 -0700 (PDT)
Subject: Re: VS:  Re: [IAB] Last Call: Modern Global Standards Paradigm
From: Glen Zorn <glenzorn@gmail.com>
To: ietf@ietf.org
In-Reply-To: <50266F05.5050601@dcrocker.net>
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com> <50266F05.5050601@dcrocker.net>
Content-Type: multipart/alternative; boundary="=-+I0Wha+msqNCuC+uU5Gl"
Organization: Network Zen
Date: Sun, 12 Aug 2012 06:01:39 +0700
Message-ID: <1344726099.8891.17.camel@gwz-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 23:01:49 -0000

--=-+I0Wha+msqNCuC+uU5Gl
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit

On Sat, 2012-08-11 at 07:41 -0700, Dave Crocker wrote:

> > Aihe: Re: [IAB] Last Call: Modern Global Standards Paradigm
> > LÃ¤hettÃ¤jÃ¤: "Eggert, Lars" <lars@netapp.com>
> ...
> > (I'd even co-sign for the IRTF, but I think that isn't really appropriate in this case.)
> 
> 
> The "for the IRTF" underscores a possible concern in the current 
> situation.
> 
> The perception will certainly be that the IAB and IETF chairs' signature 
> do represent the support of the IETF.
> 
> But we are a consensus-oriented group and we have not had anything that 
> even hints at a consensus-oriented process to authorize that representation.


My thoughts exactly.


> 
> d/
> 



--=-+I0Wha+msqNCuC+uU5Gl
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
On Sat, 2012-08-11 at 07:41 -0700, Dave Crocker wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
&gt; Aihe: Re: [IAB] Last Call: Modern Global Standards Paradigm
&gt; L&#228;hett&#228;j&#228;: &quot;Eggert, Lars&quot; &lt;<A HREF="mailto:lars@netapp.com">lars@netapp.com</A>&gt;
...
&gt; (I'd even co-sign for the IRTF, but I think that isn't really appropriate in this case.)


The &quot;for the IRTF&quot; underscores a possible concern in the current 
situation.

The perception will certainly be that the IAB and IETF chairs' signature 
do represent the support of the IETF.

But we are a consensus-oriented group and we have not had anything that 
even hints at a consensus-oriented process to authorize that representation.
</PRE>
</BLOCKQUOTE>
<BR>
My thoughts exactly.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>

d/

</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>

--=-+I0Wha+msqNCuC+uU5Gl--


From cabo@tzi.org  Sat Aug 11 16:14:25 2012
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D68F21F8487; Sat, 11 Aug 2012 16:14:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.339
X-Spam-Level: 
X-Spam-Status: No, score=-106.339 tagged_above=-999 required=5 tests=[AWL=-0.090, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id StwWMSf8XcHw; Sat, 11 Aug 2012 16:14:25 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 6E68021F8468; Sat, 11 Aug 2012 16:14:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q7BNEFpX000400; Sun, 12 Aug 2012 01:14:15 +0200 (CEST)
Received: from [192.168.217.105] (p54894979.dip.t-dialin.net [84.137.73.121]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 10ADCA96; Sun, 12 Aug 2012 01:14:14 +0200 (CEST)
Subject: Re: Last Call: Modern Global Standards Paradigm
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <194C4246-928F-4D0B-95DF-A4A31540A145@sobco.com>
Date: Sun, 12 Aug 2012 01:14:13 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <EA961F5B-CB45-4C6D-B9A3-3428040D91F9@tzi.org>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <m27gt5y6py.wl%randy@psg.com> <18D3D2AC-57DD-41D2-A8BD-1D845956E2F4@vpnc.org> <194C4246-928F-4D0B-95DF-A4A31540A145@sobco.com>
To: Scott O Bradner <sob@sobco.com>
X-Mailer: Apple Mail (2.1485)
Cc: IETF Chair <chair@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, IAB <iab@iab.org>, ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 23:14:25 -0000

On Aug 12, 2012, at 00:51, Scott O Bradner <sob@sobco.com> wrote:

> singing this statement is the right thing to do=20

For 0.29 seconds, I imagined you in front of a microphone in a recording =
studio, singing "Modern Global Standards Paradigm" to the tune of "All =
the young dudes".  For 0.29 seconds...

Gr=FC=DFe, Carsten


From allison.mankin@gmail.com  Sat Aug 11 16:35:11 2012
Return-Path: <allison.mankin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1587611E80DB; Sat, 11 Aug 2012 16:35:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3lNtUzD+4+04; Sat, 11 Aug 2012 16:35:10 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 76FFE11E80D3; Sat, 11 Aug 2012 16:35:10 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so5222508obb.31 for <multiple recipients>; Sat, 11 Aug 2012 16:35:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VPQPL+vFGm90hbp/ZsLwBQuueB8tIVqVqewtw/1B0wk=; b=T7XsaJ0yEhml32PTQNe/gE1PJpt2/5bPFih5RvMf6bjOPgf5WToO1JjOPUAenxTW5p RfQIvcKAG9py4pmiC3bGseThEuEUYWPucgOr1+BtjxAI7maAmMfF4CdhZPISQKT9/oZB GjRu3iixa27LqLVbW2D/ID1skj8n5MINRxVHyqhEV755aCgq+Iw1YQHMWILJaQ9QBoFN L+nJ7VU5TF6M1I2DyMMQpxhgDlMXOxJ4TCQPC8iMeZizBK1vkyAbFyxTy2wpquJ0yEh/ eUnff4LjMIL6b5YTu0c78OJmKZlpT5B71aPDgqiIGP3ocSy4pHO8GEYinJyVJmD0Ms+R GC9Q==
MIME-Version: 1.0
Received: by 10.50.87.227 with SMTP id bb3mr1854467igb.57.1344728109877; Sat, 11 Aug 2012 16:35:09 -0700 (PDT)
Received: by 10.231.129.82 with HTTP; Sat, 11 Aug 2012 16:35:09 -0700 (PDT)
Received: by 10.231.129.82 with HTTP; Sat, 11 Aug 2012 16:35:09 -0700 (PDT)
In-Reply-To: <EA961F5B-CB45-4C6D-B9A3-3428040D91F9@tzi.org>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <m27gt5y6py.wl%randy@psg.com> <18D3D2AC-57DD-41D2-A8BD-1D845956E2F4@vpnc.org> <194C4246-928F-4D0B-95DF-A4A31540A145@sobco.com> <EA961F5B-CB45-4C6D-B9A3-3428040D91F9@tzi.org>
Date: Sat, 11 Aug 2012 19:35:09 -0400
Message-ID: <CAP8yD=tXGkra_K6ACh5u86gho9W_wb84uf=x7+HaYnPwUDDCrA@mail.gmail.com>
Subject: Re: Last Call: Modern Global Standards Paradigm
From: Allison Mankin <allison.mankin@gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary=e89a8f3ba4d34f0b2a04c705e98e
Cc: Scott O Bradner <sob@sobco.com>, IETF Chair <chair@ietf.org>, ietf list <ietf@ietf.org>, IAB <iab@iab.org>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 23:35:11 -0000

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

Wonderful image. IETF Discuss List, The Musical.

I thought very well of Russ's discussion of the statement in Vancouver. I
support signing it.

Allison
On Aug 11, 2012 7:14 PM, "Carsten Bormann" <cabo@tzi.org> wrote:

> On Aug 12, 2012, at 00:51, Scott O Bradner <sob@sobco.com> wrote:
>
> > singing this statement is the right thing to do
>
> For 0.29 seconds, I imagined you in front of a microphone in a recording
> studio, singing "Modern Global Standards Paradigm" to the tune of "All th=
e
> young dudes".  For 0.29 seconds...
>
> Gr=FC=DFe, Carsten
>
>

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

<p>Wonderful image. IETF Discuss List, The Musical.</p>
<p>I thought very well of Russ&#39;s discussion of the statement in Vancouv=
er. I support signing it. </p>
<p>Allison</p>
<div class=3D"gmail_quote">On Aug 11, 2012 7:14 PM, &quot;Carsten Bormann&q=
uot; &lt;<a href=3D"mailto:cabo@tzi.org">cabo@tzi.org</a>&gt; wrote:<br typ=
e=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">
On Aug 12, 2012, at 00:51, Scott O Bradner &lt;<a href=3D"mailto:sob@sobco.=
com">sob@sobco.com</a>&gt; wrote:<br>
<br>
&gt; singing this statement is the right thing to do<br>
<br>
For 0.29 seconds, I imagined you in front of a microphone in a recording st=
udio, singing &quot;Modern Global Standards Paradigm&quot; to the tune of &=
quot;All the young dudes&quot;. =A0For 0.29 seconds...<br>
<br>
Gr=FC=DFe, Carsten<br>
<br>
</blockquote></div>

--e89a8f3ba4d34f0b2a04c705e98e--

From sob@sobco.com  Sat Aug 11 16:55:00 2012
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D121121F85D1; Sat, 11 Aug 2012 16:55:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.359
X-Spam-Level: 
X-Spam-Status: No, score=-0.359 tagged_above=-999 required=5 tests=[AWL=0.136,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h2jqewucIGCb; Sat, 11 Aug 2012 16:55:00 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 5DE5D21F85BB; Sat, 11 Aug 2012 16:54:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 6B71A36BA1F8; Sat, 11 Aug 2012 19:54:53 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FbJHCcaX-CLk; Sat, 11 Aug 2012 19:54:51 -0400 (EDT)
Received: from golem.sobco.com (golem.sobco.com [136.248.127.162]) by sobco.sobco.com (Postfix) with ESMTPSA id AA0DF36BA1E2; Sat, 11 Aug 2012 19:54:51 -0400 (EDT)
Subject: Re: Last Call: Modern Global Standards Paradigm
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Scott O Bradner <sob@sobco.com>
In-Reply-To: <EA961F5B-CB45-4C6D-B9A3-3428040D91F9@tzi.org>
Date: Sat, 11 Aug 2012 19:54:51 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B24EAAB0-E4EB-4982-B071-79E139F4F5EA@sobco.com>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <m27gt5y6py.wl%randy@psg.com> <18D3D2AC-57DD-41D2-A8BD-1D845956E2F4@vpnc.org> <194C4246-928F-4D0B-95DF-A4A31540A145@sobco.com> <EA961F5B-CB45-4C6D-B9A3-3428040D91F9@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.1278)
Cc: IETF Chair <chair@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, IAB <iab@iab.org>, ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 23:55:01 -0000

ah yes - Mac Mail being helpful (again)

:-)

On Aug 11, 2012, at 7:14 PM, Carsten Bormann wrote:

> On Aug 12, 2012, at 00:51, Scott O Bradner <sob@sobco.com> wrote:
>=20
>> singing this statement is the right thing to do=20
>=20
> For 0.29 seconds, I imagined you in front of a microphone in a =
recording studio, singing "Modern Global Standards Paradigm" to the tune =
of "All the young dudes".  For 0.29 seconds...
>=20
> Gr=FC=DFe, Carsten
>=20


From sm@resistor.net  Sat Aug 11 17:24:45 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49D8021F85E4; Sat, 11 Aug 2012 17:24:45 -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.006, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ba3B4eUYbVZJ; Sat, 11 Aug 2012 17:24:41 -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 ED07421F85EF; Sat, 11 Aug 2012 17:24:40 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q7C0OPZi014689; Sat, 11 Aug 2012 17:24:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1344731071; bh=rqcxsY5LI8D5nAIXyGxZoNVxftNY3cVCiO+O7ejdi+U=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=v3hwOsHjCoC56T+mCl5J+hhTbrNu/1rKSIpzUaRKZPEClr+r1GjO5Q7qoAtrRBRUF bGIpW09Ffl7tdvd2qsRk+J9Jpk7bcF+oY/0Nu6J69ZGwTC3ze2BVloWDyGKOVayBgN 7A0cdx6gCFE+/KsfiA3ekJPGaBmUNEfV8PFdwpbM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1344731071; i=@resistor.net; bh=rqcxsY5LI8D5nAIXyGxZoNVxftNY3cVCiO+O7ejdi+U=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=c9sbusttJwcU767ZQxUgcrXrgLYBgeZrq/6bg3kWTwaYixNjZ+5SKhfbmhjCxtAFp epHgdAuz2tkxp27g8BA2fDPYZuiN/wfdAH48zhldXgYdGj3XlXuPmEdhPxaxwv12R0 IuwpiWu0brDFJ4KbOdbeXasCvWWiOLKbnPaAnap4=
Message-Id: <6.2.5.6.2.20120811132511.08896128@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 11 Aug 2012 14:06:08 -0700
To: Yoav Nir <ynir@checkpoint.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: Modern Global Standards Paradigm
In-Reply-To: <AD0CD892-F436-4080-ACD6-3A72DCC6CA66@checkpoint.com>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <CAMm+Lwio8=EyW-=LZE8BA4=6N=H4f7a1Nycg25LxB920ceZ6JA@mail.gmail.com> <1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.com> <CAMm+LwgBhpJhacVLrAYiUJHzEuHifonXNvCz5v5W3MDCaCRwDQ@mail.gmail.com> <50262840.6050305@tana.it> <50266500.6000507@gmail.com> <6.2.5.6.2.20120811080806.0a6b9c38@resistor.net> <AD0CD892-F436-4080-ACD6-3A72DCC6CA66@checkpoint.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: IAB <iab@iab.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Aug 2012 00:24:45 -0000

Hi Yoav,
At 13:08 11-08-2012, Yoav Nir wrote:
>These operators are (hypothetically) Libyan citizens, 
>right?  Residents of Libya who

Yes.

>The number of international gateways does not matter, if all the 
>operators have to comply with the government's blacklist, or have to 
>install a government-mandated policy on a government-mandated firewall.

Yes.

As these government-mandated policies only end up intercepting HTTP 
traffic it not worth the bother arguing about it.  The entertaining 
part of the government blacklists is that they are maintained by an 
organization in another country.

>Not trusting the certificate just means you get annoying warnings. 
>It won't let you circumvent it. Living in an authoritarian country 
>means you don't get to play cat & mouse with your government

In most countries you don't play cat and mouse with the government.

>I thought it was Al Gore running the Internet from his garage, no?

:-)

Regards,
-sm  


From glenzorn@gmail.com  Sat Aug 11 19:06:09 2012
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B364E11E80A3 for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 19:06:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.311
X-Spam-Level: 
X-Spam-Status: No, score=-3.311 tagged_above=-999 required=5 tests=[AWL=0.287,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vzjPe6l4hH7G for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 19:06:09 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 22D6611E8091 for <ietf@ietf.org>; Sat, 11 Aug 2012 19:06:09 -0700 (PDT)
Received: by pbbrr4 with SMTP id rr4so5050342pbb.31 for <ietf@ietf.org>; Sat, 11 Aug 2012 19:06:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer; bh=ErLMH54t+kxjb+NMY/0itYktjesLkSubgekWWScPZq8=; b=BFdUR6wDT2dkWTVb6ZCGgATVa7Ba08Xu9KmlBRo8D2Uejgs9zxNVUVG4+0cvx8yNDl DYo15j3Vo1UqkwfihhwzkvaCTrRtNl1UB09LFQ8FklpYWODPd1GEQxPq0Juay575/hJk cyNivmACCz16QHeoMUxp9L1twpJichhobrFv7mLBbmTHePQX0Rj2EVWNJuEAdynDcwYz jlR/SxEJLufdnYCB94MurJARPbBtmUzrkBVeGYIgcNcGlH8bEnqY3zmCgKdL14E7h34U 3hmH9eLRr6VpowrPi/6LtbAVR0pD451QkH2pRh6ytXSzi5uNe4L/cWsWbCbM1KzXa1gq fz6w==
Received: by 10.66.88.202 with SMTP id bi10mr16321423pab.10.1344737168920; Sat, 11 Aug 2012 19:06:08 -0700 (PDT)
Received: from [192.168.0.102] (ppp-124-122-161-240.revip2.asianet.co.th. [124.122.161.240]) by mx.google.com with ESMTPS id wi6sm2396194pbc.35.2012.08.11.19.06.06 (version=SSLv3 cipher=OTHER); Sat, 11 Aug 2012 19:06:08 -0700 (PDT)
Subject: Re: Re: [IAB] Last Call: Modern Global Standards Paradigm
From: Glen Zorn <glenzorn@gmail.com>
To: ietf@ietf.org
In-Reply-To: <1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org>
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com> <50266F05.5050601@dcrocker.net> <1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org>
Content-Type: multipart/alternative; boundary="=-bTBlgMwhk+EYf0sSPhFb"
Organization: Network Zen
Date: Sun, 12 Aug 2012 09:06:04 +0700
Message-ID: <1344737164.8891.29.camel@gwz-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Aug 2012 02:06:10 -0000

--=-bTBlgMwhk+EYf0sSPhFb
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit

On Sat, 2012-08-11 at 17:13 +0200, Carsten Bormann wrote:

> On Aug 11, 2012, at 16:41, Dave Crocker <dhc@dcrocker.net> wrote:
> 
> > consensus-oriented process
> 
> Sometimes, though, you have to act.
> 
> While a consensus-oriented process*) document could certainly be used to improve (or deteriorate) the document by a couple more epsilons, I agree with Randy Bush: Signing it now is a no-brainer.
> 
> GrÃ¼ÃŸe, Carsten
> 
> *) Well there was a call for comments, and it already supplied the first such set of epsilons.  
> That may have to do when time is of the essence.
> 
> (That's also what you choose your leadership for.  
> If we don't like the outcome, we can always decide not to re-elect Russ :-)


Did the IETF morph into a representative democracy while I was sleeping?
Last time I checked, Russ was the chair of a committee of managers,
chosen by a random selection of proles who may or may not have taken the
opinions of others into account in that selection.  He was not
"elected", nor does he "speak for the IETF"; ditto for Bernard.  If they
wish to sign this statement (with which I, by and large, agree, BTW),
that's fine.  If they wish to list all their titles (IETF-bestowed &
otherwise), degrees, etc., that's fine, too, but not if the intent is to
imply that they somehow "represent" me or any one other than themselves.
If support by IETF members at-large is to be signified, then an online
petition of some sort would be a much better idea & much less deceptive.


> 



--=-bTBlgMwhk+EYf0sSPhFb
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
On Sat, 2012-08-11 at 17:13 +0200, Carsten Bormann wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
On Aug 11, 2012, at 16:41, Dave Crocker &lt;<A HREF="mailto:dhc@dcrocker.net">dhc@dcrocker.net</A>&gt; wrote:

&gt; consensus-oriented process

Sometimes, though, you have to act.

While a consensus-oriented process*) document could certainly be used to improve (or deteriorate) the document by a couple more epsilons, I agree with Randy Bush: Signing it now is a no-brainer.

Gr&#252;&#223;e, Carsten

*) Well there was a call for comments, and it already supplied the first such set of epsilons.  
That may have to do when time is of the essence.

(That's also what you choose your leadership for.  
If we don't like the outcome, we can always decide not to re-elect Russ :-)
</PRE>
</BLOCKQUOTE>
<BR>
Did the IETF morph into a representative democracy while I was sleeping?&nbsp; Last time I checked, Russ was the chair of a committee of managers, chosen by a random selection of proles who may or may not have taken the opinions of others into account in that selection.&nbsp; He was not &quot;elected&quot;, nor does he &quot;speak for the IETF&quot;; ditto for Bernard.&nbsp; If they wish to sign this statement (with which I, by and large, agree, BTW), that's fine.&nbsp; If they wish to list all their titles (IETF-bestowed &amp; otherwise), degrees, etc., that's fine, too, but not if the intent is to imply that they somehow &quot;represent&quot; me or any one other than themselves.&nbsp; If support by IETF members at-large is to be signified, then an online petition of some sort would be a much better idea &amp; much less deceptive.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>

</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>

--=-bTBlgMwhk+EYf0sSPhFb--


From ynir@checkpoint.com  Sat Aug 11 20:55:16 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C06EC11E809C; Sat, 11 Aug 2012 20:55:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.413
X-Spam-Level: 
X-Spam-Status: No, score=-10.413 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vjr8MuxY4WKy; Sat, 11 Aug 2012 20:55:16 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 9CBE811E809B; Sat, 11 Aug 2012 20:55:15 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id q7C3t3XR026672; Sun, 12 Aug 2012 06:55:04 +0300
X-CheckPoint: {50272606-0-1B221DC2-4FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Sun, 12 Aug 2012 06:55:00 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: SM <sm@resistor.net>
Date: Sun, 12 Aug 2012 06:55:00 +0300
Subject: Re: Last Call: Modern Global Standards Paradigm
Thread-Topic: Last Call: Modern Global Standards Paradigm
Thread-Index: Ac14Pj7OsGH9/vhWRMSqJOSqIi4RTA==
Message-ID: <FFE828EB-20E8-4423-A788-BB8443984F88@checkpoint.com>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <CAMm+Lwio8=EyW-=LZE8BA4=6N=H4f7a1Nycg25LxB920ceZ6JA@mail.gmail.com> <1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.com> <CAMm+LwgBhpJhacVLrAYiUJHzEuHifonXNvCz5v5W3MDCaCRwDQ@mail.gmail.com> <50262840.6050305@tana.it> <50266500.6000507@gmail.com> <6.2.5.6.2.20120811080806.0a6b9c38@resistor.net> <AD0CD892-F436-4080-ACD6-3A72DCC6CA66@checkpoint.com> <6.2.5.6.2.20120811132511.08896128@resistor.net>
In-Reply-To: <6.2.5.6.2.20120811132511.08896128@resistor.net>
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: IAB <iab@iab.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: Sun, 12 Aug 2012 03:55:16 -0000

On Aug 12, 2012, at 12:06 AM, SM wrote:
>> Not trusting the certificate just means you get annoying warnings.=20
>> It won't let you circumvent it. Living in an authoritarian country=20
>> means you don't get to play cat & mouse with your government
>=20
> In most countries you don't play cat and mouse with the government.

In most western countries you can use TOR and wear a tinfoil hat. This migh=
t make some government agency suspicious, but they don't get to arrest you =
and question you about what you're hiding/

Yoav=

From sm@resistor.net  Sat Aug 11 21:17:57 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4049E21F8499; Sat, 11 Aug 2012 21:17:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level: 
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rvd5aEEFYzyS; Sat, 11 Aug 2012 21:17:53 -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 6219621F8498; Sat, 11 Aug 2012 21:17:53 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q7C4HYTj025416; Sat, 11 Aug 2012 21:17:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1344745061; bh=SxDsac6nvIim2C/+oij84oTgNT3o47+1XN/5VqZK/hw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=sWjzZD9kqegx+Oh4e2Dawpz2BayYVAO/bEpWlG2BPLGD52kjgGcd0+hGWLm864aPq sr7ZmswvPs0PbO/6XFKI3euKrqeyBTA6yoYIW1zcRTlSm3DH9QG4r7A5fY/llBK88N dlhMLNmHoFnCEvzlscIvXmMPSRuPuOO+yPWkHQNo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1344745061; i=@resistor.net; bh=SxDsac6nvIim2C/+oij84oTgNT3o47+1XN/5VqZK/hw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=hZjvFrZGTvxJ/vqSU7GJa6zouzHJYgnUB+zy+WntLx7CeF6KA3xSFyBqABIXHpHQq oLVUVHN9GAs5R9BCyCMt9VwygbipQk9pwMU2u9EOJKjfbAy7pqeUoFEWU3QJmwe3uz 8gIPdlNkMrCBWgvMh4gMVMPNtZdGsJ+WTdIQf5Bc=
Message-Id: <6.2.5.6.2.20120811184647.09367e30@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 11 Aug 2012 20:49:26 -0700
To: Dave Crocker <dcrocker@bbiw.net>, Glen Zorn <glenzorn@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: [IAB] Last Call: Modern Global Standards Paradigm
In-Reply-To: <50267826.70307@bbiw.net>
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com> <50266F05.5050601@dcrocker.net> <1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org> <50267826.70307@bbiw.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Aug 2012 04:17:57 -0000

At 08:20 11-08-2012, Dave Crocker wrote:
>My point was that we have a process for assessing IETF support and 
>it's not being used.  Something quite different is being used.
>
>I'm not arguing against the document, but merely noting that an 
>implication of IETF community support is going to be present, but in 
>the absence of our having followed the process that makes that 
>(formally) correct.

In a message at 
http://www.ietf.org/mail-archive/web/ietf/current/msg74519.html the 
IETF Chair mentioned that:

   "The IETF Chair and the IAB Chair intend to sign the Affirmation in the
    next few weeks. Please send strong objections to the iab at iab.org
    and the ietf at ietf.org mailing lists by 2012-08-24."

The subject line of that message says "Last Call".   The wording used 
(send strong objections) is uncommon.  The period for accepting 
comments is two weeks.  There has been comments and some 
noise.  Neither the IETF Chair nor the three Area Directors who 
commented attempted to stifle the noise.  In some other community you 
can expect a reminder about AUP ( 
http://lists.arin.net/pipermail/arin-ppml/2012-August/025789.html ).

   "Recognising that moral issues are fundamental to the utility and
    success of protocols designed within the IETF, and that simply making
    a wishy-washy liberal-minded statement does not necessarily provide
    adequate guarantees of a correct and proper outcome for society,"

the IETF proposes to issue a press release.

>Bureaucracy sucks.  It's a hassle. It's always more appealing to 
>just do whatever we feel like that feels reasonable because we have 
>good intent.

Yes.

At 19:06 11-08-2012, Glen Zorn wrote:
>any one other than themselves.  If support by IETF members at-large 
>is to be signified, then an online petition of some sort would be a 
>much better idea & much less deceptive.

RFCs, for example RFC 1984, have been used for such statements.

Regards,
-sm 


From glenzorn@gmail.com  Sat Aug 11 23:13:29 2012
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5958021F84F1 for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 23:13:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.056
X-Spam-Level: 
X-Spam-Status: No, score=-2.056 tagged_above=-999 required=5 tests=[AWL=-1.004, BAYES_00=-2.599, EXTRA_MPART_TYPE=1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b8H24ALVJP6V for <ietf@ietfa.amsl.com>; Sat, 11 Aug 2012 23:13:28 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id B149021F8568 for <ietf@ietf.org>; Sat, 11 Aug 2012 23:13:28 -0700 (PDT)
Received: by pbbrr4 with SMTP id rr4so5255774pbb.31 for <ietf@ietf.org>; Sat, 11 Aug 2012 23:13:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer; bh=4trHv04K3W/7hV0DTXYfPUffyLLo5ALX+uMnLIj18ss=; b=wy8ysX/QZXJ+unBIYK3dEvEMdAVOnm2kiVrNPcgCQe3kvlE6akH8S91Jr7/piwWbfM E04qi/zW/urHMXlsm3+fUlhvkp+y/7cNIdJxa08c7k5+pIKqbfnwc254vjy0LIfpiSuJ 5DIasT+pxgNm/hfkM9hR4MMr/OdqsJ7Z76N/8llQUFW3SeK3daEuCcO2LraNxG0nUwEi zM40IZy/dnUFGKIflqeNvWk0/P+V2xvcIVjIpz4V7fhhRojX4t+UgmBYFUy2KFZ4rBiP gOibpSfd/wsBJtLPKWWOQpQNwRqegAy+BckMsT3DsDBNLlep7wt3z+LZ8kihujnjmOYh oOIg==
Received: by 10.66.74.100 with SMTP id s4mr9697185pav.27.1344752008470; Sat, 11 Aug 2012 23:13:28 -0700 (PDT)
Received: from [192.168.0.102] (ppp-124-122-161-240.revip2.asianet.co.th. [124.122.161.240]) by mx.google.com with ESMTPS id hr9sm2760347pbc.36.2012.08.11.23.13.24 (version=SSLv3 cipher=OTHER); Sat, 11 Aug 2012 23:13:26 -0700 (PDT)
Subject: Re: [IAB] Last Call: Modern Global Standards Paradigm
From: Glen Zorn <glenzorn@gmail.com>
To: SM <sm@resistor.net>
In-Reply-To: <6.2.5.6.2.20120811184647.09367e30@resistor.net>
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com> <50266F05.5050601@dcrocker.net> <1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org> <50267826.70307@bbiw.net> <6.2.5.6.2.20120811184647.09367e30@resistor.net>
Content-Type: multipart/related; type="multipart/alternative"; boundary="=-W54c2woQteMqqGUxxWR7"
Organization: Network Zen
Date: Sun, 12 Aug 2012 13:13:22 +0700
Message-ID: <1344752002.8891.44.camel@gwz-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) 
Cc: IAB <iab@iab.org>, Dave Crocker <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: Sun, 12 Aug 2012 06:13:29 -0000

--=-W54c2woQteMqqGUxxWR7
Content-Type: multipart/alternative; boundary="=-e9ZHZcZU3U2UlX0Q+iYL"


--=-e9ZHZcZU3U2UlX0Q+iYL
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

On Sat, 2012-08-11 at 20:49 -0700, SM wrote:

...


> 
> At 19:06 11-08-2012, Glen Zorn wrote:
> >any one other than themselves.  If support by IETF members at-large 
> >is to be signified, then an online petition of some sort would be a 
> >much better idea & much less deceptive.
> 
> RFCs, for example RFC 1984, have been used for such statements.


Sorry, I don't get your point.  The referenced RFC says

   The Internet Architecture Board (IAB) and the Internet Engineering
   Steering Group (IESG), the bodies which oversee architecture and
   standards for the Internet, are concerned by the need for increased
   protection of international commercial transactions on the Internet,
   and by the need to offer all Internet users an adequate degree of
   privacy.

Presumably, the IAB & IESG came to this concern through consensus and
the document expresses the consensus (along with the rather typical
sense of exaggerated self-importance ;-))
of those bodies.  It pointedly does not claim to represent the opinion
of the entire IETF, but neither does the document under discussion
(unless the royal usage of "we" is intended) and that's how it should
be.  


> 
> Regards,
> -sm 
> 



--=-e9ZHZcZU3U2UlX0Q+iYL
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
On Sat, 2012-08-11 at 20:49 -0700, SM wrote:<BR>
<BR>
...<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>

At 19:06 11-08-2012, Glen Zorn wrote:
&gt;any one other than themselves.  If support by IETF members at-large 
&gt;is to be signified, then an online petition of some sort would be a 
&gt;much better idea &amp; much less deceptive.

RFCs, for example RFC 1984, have been used for such statements.
</PRE>
</BLOCKQUOTE>
<BR>
Sorry, I don't get your point.&nbsp; The referenced RFC says<BR>
<BR>
&nbsp;&nbsp; The Internet Architecture Board (IAB) and the Internet Engineering<BR>
&nbsp;&nbsp; Steering Group (IESG), the bodies which oversee architecture and<BR>
&nbsp;&nbsp; standards for the Internet, are concerned by the need for increased<BR>
&nbsp;&nbsp; protection of international commercial transactions on the Internet,<BR>
&nbsp;&nbsp; and by the need to offer all Internet users an adequate degree of<BR>
&nbsp;&nbsp; privacy.<BR>
<BR>
Presumably, the IAB &amp; IESG came to this concern through consensus and the document expresses the consensus (along with the rather typical sense of exaggerated self-importance <IMG SRC="cid:1344751305.8891.37.camel@gwz-laptop" ALIGN="middle" ALT=";-)" BORDER="0">)<BR>
of those bodies.&nbsp; It pointedly does not claim to represent the opinion of the entire IETF, but neither does the document under discussion (unless the royal usage of &quot;we&quot; is intended) and that's how it should be.&nbsp; <BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>

Regards,
-sm 

</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>

--=-e9ZHZcZU3U2UlX0Q+iYL--

--=-W54c2woQteMqqGUxxWR7
Content-ID: <1344751305.8891.37.camel@gwz-laptop>
Content-Disposition: attachment; filename="face-wink.png"
Content-Type: image/png; name="face-wink.png"
Content-Transfer-Encoding: base64

iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAABHNCSVQICAgIfAhkiAAAAAlwSFlz
AAAN1wAADdcBQiibeAAAABl0RVh0U29mdHdhcmUAd3d3Lmlua3NjYXBlLm9yZ5vuPBoAAAAXdEVY
dEF1dGhvcgBMYXBvIENhbGFtYW5kcmVp35EaKgAAACl0RVh0RGVzY3JpcHRpb24AQmFzZWQgb2Yg
SmFrdWIgU3RlaW5lciBkZXNpZ26ghAVzAAADQUlEQVQ4jWWTW2jVdQCAv//t3HbqzF3cOluL1kWi
3DTP3NAt3bAeokKCXoISFHUEhQ9d3grxKWh0gYxJSAwSKQh8KAkqtcZWtqXTww562NnZpq6dTbdz
ds75337/36/Xhd/zx/f2aUopNnL6g96koRmvhw21F13bAYBUk26gXQxUcObgx6N3NvraxsDI+30H
o/EHvnhmZ0+4ofUhs6ahEZSislJgeWFRXB0fcyvl8juHPx07fV/g2/d2/dT65Pb+1MDzEc39By1U
gJAAFLgW+M0EViejP//o5DNTFwa//PtFAB3gm3d7B1se39rf1bs7EuROId1JVAL0xnq0xnpIKALn
L2T+a/YM7Iu0tD+1d+hIahBAP3Wsr80IRYd27Hoh4lwfRgZL6PEa9FgcFY5COMZKRefDr+ZQ/iJO
+iTP7XspaljhoeMHUm26L/xD27Z1h+X8BWRplttrNQyfLXH46BgyCNCUIp1eZvxKCQWIUh5u/c7u
nr5wEIhDZiC8/vqmh43VqfMIKUi2hnjjlU7erH8Uw7sBKKLYCLcKnocmJd7tyzQ9dsAIhNdvesro
iNc2UVnPk1mFijlLe9jFMDJIz0JDo6PJ58j+NpRTQXkCsT5LYmcST+gdpi800ykuIT2X7W11nL/h
8ev1LD3P1tH5dC0AIdvltZTEKThU130iro/vVPECZZq2XU3nb17tbjUTyHKJl7u3UrQ288v4FX77
M4eUCuFJasOSjmbYUiPA3MTM9GVc10mbTsClTPZmV0MsplvOPcrzacxNLewf2IMWq0Pay8jiHHpl
CYoFgqKLG4szlclIR3DJFIEauTZTeDvZbkS3BBIdB8dboFy4hdINLBNiBigRgO0iXUVOWYxdy7ue
0EeM8enC8rmRz0Nzd+2uemvNSiiBqRS6UoS0gJAUaI4PtotX8cnZOt9P69WSLT85ezH3nQ7QVEme
KHpW9tydZHVy1WRl3Yeyjbluo63ZuEWbf4uCiXsGZ7J11ZUq2WVj/sT/XjiaSlmVB+8eV0odeyRe
irREXa056gKwWA2xUA2rmWLcUWifNTibPxqemPDvuxHg1b72Th3/LQ2tN5DaEwCGrrIKNSqxTv7w
R25qo/8f4VCvV0QXv9gAAAAASUVORK5CYII=


--=-W54c2woQteMqqGUxxWR7--


From mohta@necom830.hpcl.titech.ac.jp  Sun Aug 12 02:26:01 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AC5421F8460 for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 02:26:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.046
X-Spam-Level: 
X-Spam-Status: No, score=-0.046 tagged_above=-999 required=5 tests=[AWL=0.044,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jm-yaCmsh6AM for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 02:26:00 -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 CB83F21F8453 for <ietf@ietf.org>; Sun, 12 Aug 2012 02:25:54 -0700 (PDT)
Received: (qmail 72432 invoked from network); 12 Aug 2012 09:36: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; 12 Aug 2012 09:36:52 -0000
Message-ID: <5027767A.60601@necom830.hpcl.titech.ac.jp>
Date: Sun, 12 Aug 2012 18:25:14 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FE2715C.2090601@necom830.hpcl.titech.ac.jp> <4FF20DE7.2080208@isi.edu> <500654AB.7060500@necom830.hpcl.titech.ac.jp> <8F5CBE79-4540-4519-9F51-62B36686EE8C@isi.edu> <501C5C75.9040209@necom830.hpcl.titech.ac.jp> <501C6441.4000302@isi.edu> <5020C32A.4060907@necom830.hpcl.titech.ac.jp> <50215032.7090800@isi.edu>
In-Reply-To: <50215032.7090800@isi.edu>
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: Sun, 12 Aug 2012 09:26:01 -0000

Joe Touch wrote:

Hi,

>>>> RFC2765 specifies that translators can merely copy the
>>>> low-order bits of the field.
>>>
>>> Yes, but this is not compatible with RFC791.
>>
>> Then, which should we revice? RFC791, RFC2765 or both?
> 
> 2765.

Is it a consensus of IETF?

Note that it also imply revising RFC2460, because rfc2765 specifies
a way of ID mapping, where as rfc2460 specifies 32bit->16bit mapping
will be performed by translators.

Note also that there already are working implementations of
rfc2460 and rfc2765.

> There is no useful way to revise 791 to make the text in 2765 correct.

Revising rfc791 not requiring a very strong uniqueness is
useful reflecting current practice better than your draft,
even though your draft claims "closely reflect current
practice".

Moreover, I can see no useful way to revise rfc2765. Do you
have any suggestion?

>> Without such a decision, there is no point to publish something
>> based on RFC791 and is not compatible with RFC2765.
> 
> Sure there is - when IPv6 is not involved.

But, your draft involves IPv6 and, for example, the following
statement in your draft:

   IPv6, even at typical MTUs, is capable of 18.7 Tbps with
   fragmentation between two IP endpoints as an aggregate across all
   protocols,

is not compatible with rfc2460 and rfc2765.

> An IPv6 source might never send packets larger than IPv4 can natively
> handle - i.e., it could send packets 576 bytes or smaller. In that case,
> the IPv6 source would never get an ICMP "too big" because they're not as
> far as IPv4 is concerned. In that case, the IPv6 source would never
> insert the Fragmentation Header.

I'm afraid minimum MTU of IPv4 is 68, not 576 bytes.

Anyway, IPv6 node having no idea on PMTU will send a lot of
exactly 1280 byte long packets, because it will make TCP
most efficient.

> That is the fundamental flaw in these IPv6 RFCs, but it is behavior that
> is out of scope for an IPv4 source. My doc focuses on the behavior of
> IPv4 sources.

While I think IPv6 RFCs have many fundamental flaws, a problem
is that there are people in IETF insisting not to admit them
flaws.

Do you think you can make them admit a flaw?

>> That is the problem. That is, if you insist on RFC791 as is, not
>> enough is specified on how to generate IPv6 ID.
> 
> Yes, but that does not affect an IPv4 source; it remains a problem, but
> out of scope for this doc.

It is out of scope, if only rfc791 is not revised.


>> Thus, there can be only one way (the one in RFC2765) to map IPv6
>> ID to IPv4 ID

> Yes, this is a nice goal, but it would have required IPv6 hosts insert
> 16-bit IDs into *every* packet and make them just as unique as IPv4 does.

No, not *every* packet. But, as you wrote:

>>> Further, the source might already be inserting the fragmentation header
>>> (e.g., on a 2KB packet).

every such packet is required to have a unique 32bit ID which must
also be unique as a 16bit ID after translation.

>> Then, as fixing RFC2460 is politically impossible, we must
>> abandone IPv6 and live with IPv4 forever.
> 
> I didn't say we couldn't fix - or at least try to fix - this situation.
> But it remains out of scope for this doc.

If only you can convince people we should fix rfc2460, not rfc791.

>> but, "the specification of the similar field in IPv6" is, in
>> your opinion, incomplete, let's finish it first,
> 
> IPv6 is fine when it talks to IPv6 only. The goal is to make IPv4 work
> in a similar way.

You are saying dual stack is clean and the way to go and all the
other IPv6 deployment scenarios should be ignored.

> it doesn't make it completely correct, though - there remain
> problems that have nothing to do with the changes in this doc that need
> to be addressed separately.

The question is whether you can have a consensus that rfc2460
is not completely correct or not.

>> For another example,
>>
>>      Finally, the IPv6 ID field is
>>      32 bits, and required unique per source/destination address pair for
>>      IPv6,
>>
>> is, in your opinion, violation of RFC791.
> 
> No; the violation occurs only when the lower 16 bits are masked off and
> used by themselves by on-path translators. That has nothing to do with
> the quoted text above.

The problem is that, if rfc2460 is not "completely correct", above
text in your draft should be something based not on the current
rfc2460 but on completely correctly revised rfc2460, such as
"IPv6 ID field is required unique after translated into 16 bit
IPv4 ID".

> But neither of the above requires that IPv6 IDs must be easily
> translatable into valid IPv4 addresses using the existing mechanism.

IPv4 addresses? What do you mean?

						Masataka Ohta

From sm@resistor.net  Sun Aug 12 03:01:11 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FBC121F8512; Sun, 12 Aug 2012 03:01:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level: 
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rSs5YKoXFN7f; Sun, 12 Aug 2012 03:01:06 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id B0F8221F8504; Sun, 12 Aug 2012 03:01:06 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q7CA0rLd020456; Sun, 12 Aug 2012 03:00:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1344765663; bh=K9bZkv9lYmAK02K9QWcOtjOKX+YZ4/Bwfb+LPZC43Fw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ImZCOnMazJ3ph1j4wKGDinzEkTTUAWhsR/rIe5ICNHY89vbPp2cNNWSDL8tK0tiz/ EfqhFkxRE9YIqJIr+CLPWT2NkU4Dgh8Oc6Ff1hdUeegYTu0oUl8hRtXdMxr/WRW2+7 2LDoG0Ku1VmMp2a1maS9ho6jQSeTMfj1STvCjJYM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1344765663; i=@resistor.net; bh=K9bZkv9lYmAK02K9QWcOtjOKX+YZ4/Bwfb+LPZC43Fw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=peeNAfyPiyuu48830QJGP33abXSRDBFrgUsKJncjKvXYnakPVzgo/rhsiMT4Pcv5i fLgzkU2tJgIuKv/jlCAshVSkzkzrYtPuidG8XHJU8iZK3KoivUxgGa/qeYPv97QRD4 7zxIwwQuEnJN5zkob7X6ZNfE0cBnb3fAeXtDh2PM=
Message-Id: <6.2.5.6.2.20120812002922.09ea24f0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 12 Aug 2012 02:57:14 -0700
To: Glen Zorn <glenzorn@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: [IAB] Last Call: Modern Global Standards Paradigm
In-Reply-To: <1344752002.8891.44.camel@gwz-laptop>
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com> <50266F05.5050601@dcrocker.net> <1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org> <50267826.70307@bbiw.net> <6.2.5.6.2.20120811184647.09367e30@resistor.net> <1344752002.8891.44.camel@gwz-laptop>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="=====================_928720128==_"
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Aug 2012 10:01:11 -0000

--=====================_928720128==_
Content-Type: text/plain; charset="us-ascii"; format=flowed

Hi Glen,
At 23:13 11-08-2012, Glen Zorn wrote:
>Sorry, I don't get your point.  The referenced RFC says

It was the Spring of 1995.  The place was known as Danvers.  That 
meeting is remembered because of the Danvers Doctrine.

>Presumably, the IAB & IESG came to this concern through consensus 
>and the document expresses the consensus (along with the rather 
>typical sense of exaggerated self-

Yes.

>importance
>;-)
>)
>of those bodies.  It pointedly does not claim to represent the 
>opinion of the entire IETF, but neither does the document under 
>discussion (unless the royal usage of "we" is intended) and that's 
>how it should be.

Over the years the IAB and IETF have expressed a joint opinion on an 
issue through a RFC.    That RFC is one of the significant ones as it 
dealt with the question of "export" grade security which was on the 
political agenda of the day.  Nowadays the IETF uses BCPs to express 
IETF Consensus.

Regards,
-sm 
--=====================_928720128==_
Content-Type: application/octet-stream; name="3759cb5c.jpg"
Content-ID: <.0>
Content-Transfer-Encoding: base64
Content-Disposition: inline; filename="3759cb5c.jpg"

/9j/4AAQSkZJRgABAQAAAQABAAD/2wBDAAEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEB
AQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQH/2wBDAQEBAQEBAQEBAQEBAQEBAQEBAQEB
AQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQH/wAARCAAQABADASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD9jvAH
jbQP20vin8Lvjd+1T8H/AA/8Q/ijrfhXwvrng/4YTy+EPFvgr9kz4XfFeTT9f0zSPCOlfE/WPC+k
+INVfw+3hzxB8d/jFYeGrnx98UNY0nStM8PeCtE8KeDvAXw70DiPEfxd0j9kr4u/tPfHL9kr4LaD
8O/HvwX1LV9F8e+A7aBPA3w6/bK+GPw1+H3hX4u69pvibTPDekpo+h6/o2i+MPGR+CHxm0nQNf1z
4c+JdM8T2uoaf4s8D+OfHfw91b8ufHHi/wAe/sUfEub9nD9snwp4l8NeIPhvrer/AA8+Dfxx8c+F
fEHw/wDDX7Qfgf4Y23h3SvDnxc+DHj3wx4lu0sZNW+HuqfDfWPGfhz4ffFbXtY+GV14ksPhx8StQ
sfFumaxoVrB4V8Z/Er9uP4iwfsx/se6Z8UfHutfEnU9L+F/xd+Nukjx98XfA37L/AMN/itbeINI8
X/E74h+JvHPjSPRdHtrL4daP8RtV8IeCdc+I3g+8+K2p+G73wN4GvNW8bajpGj3/APmNTx/jVHx0
+rSwXEk80nxG6Sm6WNWTUcgWY0ZPFOr7T6hUwby2E6cVyK1Ss3K7pxUv7IfCnh//AKmy4h/t/J1w
2uF0llixOHePnnbwulL6s/8Aa44tY7lb0b5Vz8y5m1//2Q==
--=====================_928720128==_--


From bertietf@bwijnen.net  Sun Aug 12 03:52:36 2012
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 6CBFA21F84FB; Sun, 12 Aug 2012 03:52:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.875
X-Spam-Level: 
X-Spam-Status: No, score=-99.875 tagged_above=-999 required=5 tests=[AWL=0.628, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, STOX_REPLY_TYPE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WGAK3e5Y1eII; Sun, 12 Aug 2012 03:52:36 -0700 (PDT)
Received: from relay59.tele2.vuurwerk.nl (relay59.tele2.vuurwerk.nl [62.250.3.59]) by ietfa.amsl.com (Postfix) with ESMTP id D844B21F84F7; Sun, 12 Aug 2012 03:52:33 -0700 (PDT)
Received: from [87.215.199.34] (helo=BertLaptop) by relay.indetel.net with smtp (Exim 4.69) (envelope-from <bertietf@bwijnen.net>) id 1T0VmZ-0003GZ-Nh; Sun, 12 Aug 2012 12:52:31 +0200
Message-ID: <78BF47F4D3B14A40A2C82AE110863C6F@BertLaptop>
From: "Bert Wijnen \(IETF\)" <bertietf@bwijnen.net>
To: "IETF" <ietf@ietf.org>, "IAB" <iab@iab.org>, "IETF-Announce" <ietf-announce@ietf.org>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org>
In-Reply-To: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org>
Subject: Re: Last Call: Modern Global Standards Paradigm
Date: Sun, 12 Aug 2012 12:41:33 +0200
Organization: Consultant
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6002.18197
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18463
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Aug 2012 10:52:36 -0000

I support that IETF and IAB chairs sign this document.

Bert
----- Original Message ----- 
From: "IETF Chair" <chair@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: "IAB" <iab@iab.org>; "IETF" <ietf@ietf.org>
Sent: Friday, August 10, 2012 5:19 PM
Subject: Last Call: Modern Global Standards Paradigm


> 
> The IETF Chair and the IAB Chair intend to sign the Affirmation
> of the Modern Global Standards Paradigm, which can be found
> here:
> 
> http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf
> 
> An earlier version was discussed in plenary, and the IAB Chair called
> for comments on the IETF mail list.  This version includes changes
> that address those comments.
> 
> Th IETF 84 Administrative plenary minutes have been posted, so that
> discussion can be reviewed if desired.  The minutes are here:
> 
> http://www.ietf.org/proceedings/84/minutes/minutes-84-iesg-opsplenary
> 
> On 8 August 2012, the IEEE Standards Association Board of Governors
> approved this version of the document.  The approval process is
> underway at the W3C as well.
> 
> The IETF Chair and the IAB Chair intend to sign the Affirmation in the
> next few weeks. Please send strong objections to the iab@iab.org
> and the ietf@ietf.org mailing lists by 2012-08-24.
> 
> Thank you,
>  Russ Housley
>  IETF Chair

From abdussalambaryun@gmail.com  Sun Aug 12 07:30:05 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E92B21F84DF for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 07:30:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.485
X-Spam-Level: 
X-Spam-Status: No, score=-3.485 tagged_above=-999 required=5 tests=[AWL=0.114,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QNKBdUH3E+W2 for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 07:30:04 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 33B7121F8510 for <ietf@ietf.org>; Sun, 12 Aug 2012 07:30:04 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so3098205vcb.31 for <ietf@ietf.org>; Sun, 12 Aug 2012 07:30:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=qfncqupyNuJj1wjK4s6K9aCkDdxGtI8TFr9fF83TKPA=; b=m3UxsGIBFY4S93L31e0OiIxQIK3tHreYeX/78JFYKZsO3O0FUAaIY2iwF/jZdH5Xoa Pd/xayzK0rXofmTB8FSeivUnyo0r+h+ClaXAGuGlCcFrMEeqmmpjnwMALToi1ekTonw7 6Nzd0blUgdS+DbUAavmMbc/InAVbFvMxmLNebf1xV1OloSXcYn3o9Sbg1kcfQV6gC1fj y27a6VsrP0pfWoMpCNeTE1WvlPKH+ZHjYg3kyef4a8YDiYCGHdxNEVgbxJiToKzcdCiS OeGwR50dOiQLzdDW4KBwwErNWeN+9hRkKUGYos3YsQ0o9i2YVBG962qXWqksqzKU73i/ ifZg==
MIME-Version: 1.0
Received: by 10.58.154.138 with SMTP id vo10mr5378110veb.43.1344781802782; Sun, 12 Aug 2012 07:30:02 -0700 (PDT)
Received: by 10.220.62.77 with HTTP; Sun, 12 Aug 2012 07:30:02 -0700 (PDT)
Date: Sun, 12 Aug 2012 16:30:02 +0200
Message-ID: <CADnDZ8-_S9zALSz+S8eL0dFb5Vx8mWyD3-r0QeDiz3twkuzLCA@mail.gmail.com>
Subject: Re: Last Call: Modern Global Standards Paradigm
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Aug 2012 14:30:05 -0000

+1

AB

>>
>> On Aug 10, 2012, at 8:19 AM, IETF Chair wrote:
>>
>>> The IETF Chair and the IAB Chair intend to sign the Affirmation
>>> of the Modern Global Standards Paradigm, which can be found
>>> here:
>>>
>>> http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf
>>>
>>> An earlier version was discussed in plenary, and the IAB Chair called
>>> for comments on the IETF mail list.  This version includes changes
>>> that address those comments.
>>>
>>> Th IETF 84 Administrative plenary minutes have been posted, so that
>>> discussion can be reviewed if desired.  The minutes are here:
>>>
>>> http://www.ietf.org/proceedings/84/minutes/minutes-84-iesg-opsplenary
>>>
>>> On 8 August 2012, the IEEE Standards Association Board of Governors
>>> approved this version of the document.  The approval process is
>>> underway at the W3C as well.
>>>
>>> The IETF Chair and the IAB Chair intend to sign the Affirmation in the
>>> next few weeks. Please send strong objections to the iab@iab.org
>>> and the ietf@ietf.org mailing lists by 2012-08-24.
>>>
>>> Thank you,
>>>  Russ Housley
>>>  IETF Chair

From barryleiba.mailing.lists@gmail.com  Sun Aug 12 08:02:35 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFAFD21F8503 for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 08:02:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.021
X-Spam-Level: 
X-Spam-Status: No, score=-103.021 tagged_above=-999 required=5 tests=[AWL=-0.044, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XpM1UcVDRZf4 for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 08:02:34 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8396621F8505 for <ietf@ietf.org>; Sun, 12 Aug 2012 08:02:34 -0700 (PDT)
Received: by lahm15 with SMTP id m15so1680922lah.31 for <ietf@ietf.org>; Sun, 12 Aug 2012 08:02:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=G+oOy2v9HYa38fyzl188uej25UJ1nWlem8ADeUy7cwY=; b=xShnHz8MijJs9jQ5yUVKs8lDxo7bdaT6qC/qaFCndAXNBNM34TwYuaeRfrrps4dVKI h5SMaeMPsESTrlECZpyIu46kXh4bOB9b9MqWosha8SjXoZUbTu2oIrEsC+y/UxBcTeDv jIFkm+AKvgcC5F7ePH595tqMPMd3rKOYUe4FO/CE2Gh9PMiv/BoiV28Ibx80EWT6kHkU MggW/zB3hkYiH42jUUWjorbvObzYbqDJfJsPPA2pRaqTnGfmU2+VHu3ukrW17CNwUTKn wiU7secOwfrGnzb3xe1NE/xVrdq9HKAZ8k+k2iXJ2fWC8RihPBP7/eppQhLXmaOInEGz FLLA==
MIME-Version: 1.0
Received: by 10.152.112.234 with SMTP id it10mr8931890lab.36.1344783753248; Sun, 12 Aug 2012 08:02:33 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.113.196 with HTTP; Sun, 12 Aug 2012 08:02:33 -0700 (PDT)
In-Reply-To: <50267826.70307@bbiw.net>
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com> <50266F05.5050601@dcrocker.net> <1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org> <50267826.70307@bbiw.net>
Date: Sun, 12 Aug 2012 11:02:33 -0400
X-Google-Sender-Auth: wbLlVl7qMVwAt17ZYjsSvTZSp00
Message-ID: <CAC4RtVARm1fXvHR4dv9Jh0HttW+ORhRx36kwF54RRjc4aOh1AQ@mail.gmail.com>
Subject: Re: [IAB] Last Call: Modern Global Standards Paradigm
From: Barry Leiba <barryleiba@computer.org>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Aug 2012 15:02:35 -0000

> My point was that we have a process for assessing IETF support and it's not
> being used.  Something quite different is being used.

I'm not so sure.

It's true that this was not put into an Internet Draft.  Apart from
that, we seem to be doing the right thing:
- The IAB Chair announced the text and the intent to sign it on 1 Aug.
 He asked for comments.
- The IETF Chair announced updated text on 4 Aug, based on comments received.
- The IETF Chair made a last call on 10 Aug, running through 24 Aug,
noting that three organizations are approving this text (and that one
has already).  He asked for objections.
- A discussion (this) ensued, which has resulted in a great deal of
support for the signing, no objections to the document, and two
objections on process grounds.

I presume that the IETF Chair will evaluate rough consensus on or
after 24 Aug.  As I see it now, consensus appears to be strongly in
favour of their signing it, with a valid process objection that has to
be addressed.

By way of addressing that, this IETF participant thinks that our
consensus process has essentially been followed.  Text was publicly
posted, comments were incorporated, a last call was issued, and
responses are being considered.  In the end, we seem likely to have
IETF consensus that the IAB Chair and the IETF Chair sign the
document.

The parts that are not entirely as usual are (1) that the text was
publicly posted, but not in an Internet Draft, and (2) that the
community's ability to tweak the text has been limited.  That said,
both of those aspects are part of the public last call, and they have
gotten very limited objection.

Can you tell us where the above process fails in representing the
rough consensus of the IETF community, with respect to how we normally
express such consensus?  Can you tell us how what we're doing here is
"quite different" to our usual process (that is, "quite" different, as
opposed to very slightly different, with the difference having been
explained and due to the requirements of external interactions)?

Barry

From dcrocker@bbiw.net  Sun Aug 12 08:50:17 2012
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83E6421F84FD; Sun, 12 Aug 2012 08:50:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.556
X-Spam-Level: 
X-Spam-Status: No, score=-6.556 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L7hlnM0WgyEs; Sun, 12 Aug 2012 08:50:16 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5715921F84FB; Sun, 12 Aug 2012 08:50:15 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q7CFoAKB011216 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 12 Aug 2012 08:50:11 -0700
Message-ID: <5027D0B2.80306@bbiw.net>
Date: Sun, 12 Aug 2012 08:50:10 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: [IAB] Last Call: Modern Global Standards Paradigm
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com> <50266F05.5050601@dcrocker.net> <1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org> <50267826.70307@bbiw.net> <CAC4RtVARm1fXvHR4dv9Jh0HttW+ORhRx36kwF54RRjc4aOh1AQ@mail.gmail.com>
In-Reply-To: <CAC4RtVARm1fXvHR4dv9Jh0HttW+ORhRx36kwF54RRjc4aOh1AQ@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]); Sun, 12 Aug 2012 08:50:11 -0700 (PDT)
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Aug 2012 15:50:18 -0000

On 8/12/2012 8:02 AM, Barry Leiba wrote:
> It's true that this was not put into an Internet Draft.  Apart from
> that, we seem to be doing the right thing: - The IAB Chair announced
> the text and the intent to sign it on 1 Aug.

Two weeks is normal process for spontaneous consensus calls?

When did the community approve that change in process?


> He asked for comments.

No he didn't:

      "Please send strong objections..."

This asserts a forceful bias against general comments and criticisms by
establishing a very high threshhold for relevance.  While no, no one is
prevented from other kinds of postings, the bias is nonetheless established.


> - A discussion (this) ensued, which has resulted in a great deal of
> support for the signing, no objections to the document, and two
> objections on process grounds.

Note that he didn't ask for support, although explicit support
statements are exactly what is required for IETF consensus calls, absent
a history to justify the kind of "default yes" assumption made in the 
announcement.  We don't have any such documented history for this effort.

Would any of us guess that the community would support the document?
Sure.  But guessing isn't the point.

That folks have chosen to ignore the stricture specified in the 
announcement and to post public support shows how deeply ingrained our 
model is.  And, yeah, enough such postings overwhelm problems with the 
last call wording...


d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From barryleiba@gmail.com  Sun Aug 12 09:02:37 2012
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30A5521F85B4 for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 09:02:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.02
X-Spam-Level: 
X-Spam-Status: No, score=-103.02 tagged_above=-999 required=5 tests=[AWL=-0.043, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kbu+aoTPZ1HQ for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 09:02:36 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3DF6921F85AA for <ietf@ietf.org>; Sun, 12 Aug 2012 09:02:36 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so6483130obb.31 for <ietf@ietf.org>; Sun, 12 Aug 2012 09:02:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=F2HGzC+ZY394RpNMOO2f+iPkZ7AYXbxjIDARSN7RswM=; b=P7AsVlBx8/sADo85pmwVoTzG3fKhaw383BrhSJTkD6ki7n8UUZ2R1Ay9g4fjU2ILiS yfSsChXMXdfHD+oYJ/hAB5u8+f9bmZA3erl8rAcqBNqnQmy3B9DzgvthFKPXFKAlY1Gb XPSBiDf1BOrN928kjS5xSaGg8zuObFYHRRXzjf4+QnpGBtl1+2Fa52lxMFM2L14OsMKt 7RoFI9JbnguJy0mQdEGEAZ47VRMPl82JkSC3mI/Id0rxCNlOUeKILV+e/XGepJaJREbg 5akyEvuKTSZD6PZGHqaf/l73UrKieCxcl0KnmX23K4t4tqxbuCpJGhWoc5RL2IVwRRx9 APIA==
MIME-Version: 1.0
Received: by 10.60.2.42 with SMTP id 10mr8338566oer.9.1344787355910; Sun, 12 Aug 2012 09:02:35 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.76.80.198 with HTTP; Sun, 12 Aug 2012 09:02:35 -0700 (PDT)
In-Reply-To: <5027D0B2.80306@bbiw.net>
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com> <50266F05.5050601@dcrocker.net> <1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org> <50267826.70307@bbiw.net> <CAC4RtVARm1fXvHR4dv9Jh0HttW+ORhRx36kwF54RRjc4aOh1AQ@mail.gmail.com> <5027D0B2.80306@bbiw.net>
Date: Sun, 12 Aug 2012 12:02:35 -0400
X-Google-Sender-Auth: mk46FOS1cKercmKwDiXL4L5Wpgc
Message-ID: <CALaySJKzxo=oHLcDxT=RbrwMK=pTSh6vxY-VvLZ0C5wf+T-DQQ@mail.gmail.com>
Subject: Re: [IAB] Last Call: Modern Global Standards Paradigm
From: Barry Leiba <barryleiba@computer.org>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Aug 2012 16:02:37 -0000

>> It's true that this was not put into an Internet Draft.  Apart from
>> that, we seem to be doing the right thing: - The IAB Chair announced
>> the text and the intent to sign it on 1 Aug.
>
> Two weeks is normal process for spontaneous consensus calls?

1 Aug to 24 Aug strikes me as nearly four weeks, not two.  If you want
to propose that Russ add four more days, I'm sure your suggestion
would be considered.  You don't appear to be suggesting anything
constructive, though.

>> He asked for comments.
>
> No he didn't:

"He", being the IAB Chair on 1 Aug, as I said in my message, did:
<< The IAB, IESG, IEEE-SA and W3C have been developing an =93Affirmation
of the Modern Global Standards Paradigm=94.  Comments may be sent to
iab@iab.org. >>


I any case, I recommend that you make specific, constructive
suggestions about what we *should* do at this point.  Vague criticism
that we're not doing it right are much less helpful, don't you think?

Barry

From dhc@dcrocker.net  Sun Aug 12 09:14:56 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D34D121F85AC; Sun, 12 Aug 2012 09:14:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.579
X-Spam-Level: 
X-Spam-Status: No, score=-6.579 tagged_above=-999 required=5 tests=[AWL=0.020,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nKX9a+AJHy2x; Sun, 12 Aug 2012 09:14:56 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3177C21F8575; Sun, 12 Aug 2012 09:14:56 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q7CGEqqv011500 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 12 Aug 2012 09:14:53 -0700
Message-ID: <5027D67B.2030409@dcrocker.net>
Date: Sun, 12 Aug 2012 09:14:51 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: [IAB] Last Call: Modern Global Standards Paradigm
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com> <50266F05.5050601@dcrocker.net> <1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org> <50267826.70307@bbiw.net> <CAC4RtVARm1fXvHR4dv9Jh0HttW+ORhRx36kwF54RRjc4aOh1AQ@mail.gmail.com> <5027D0B2.80306@bbiw.net> <CALaySJKzxo=oHLcDxT=RbrwMK=pTSh6vxY-VvLZ0C5wf+T-DQQ@mail.gmail.com>
In-Reply-To: <CALaySJKzxo=oHLcDxT=RbrwMK=pTSh6vxY-VvLZ0C5wf+T-DQQ@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sun, 12 Aug 2012 09:14:53 -0700 (PDT)
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Aug 2012 16:14:57 -0000

On 8/12/2012 9:02 AM, Barry Leiba wrote:
>>> It's true that this was not put into an Internet Draft.  Apart from
>>> that, we seem to be doing the right thing: - The IAB Chair announced
>>> the text and the intent to sign it on 1 Aug.
>>
>> Two weeks is normal process for spontaneous consensus calls?
>
> 1 Aug to 24 Aug strikes me as nearly four weeks, not two.  If you want
> to propose that Russ add four more days, I'm sure your suggestion
> would be considered.  You don't appear to be suggesting anything
> constructive, though.

1.  You think 3 weeks is "nearly" 4?

2.  The "Last Call" was issued on 10 August, not 1 August.

Again, what's happening here is a form of 'let's ignore IETF process 
because this is such a wonderful cause'.

It is, indeed, a wonderful cause, but I don't recall our establishing 
rules that are to be applied only when we feel like it, or in varied 
manner that our management decides is sufficient.


>>> He asked for comments.
>>
>> No he didn't:
>
> "He", being the IAB Chair on 1 Aug, as I said in my message, did:
> << The IAB, IESG, IEEE-SA and W3C have been developing an “Affirmation
> of the Modern Global Standards Paradigm”.  Comments may be sent to
> iab@iab.org. >>

It's always a bit disconcerting to see an AD misinterpret process 
details this way, especially when it requires changing the reference to 
something that wasn't a Last Call.


> I any case, I recommend that you make specific, constructive
> suggestions about what we *should* do at this point.  Vague criticism
> that we're not doing it right are much less helpful, don't you think?

sigh.


d/


-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From touch@isi.edu  Sun Aug 12 10:34:08 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5834D21F85D7 for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 10:34:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.507
X-Spam-Level: 
X-Spam-Status: No, score=-103.507 tagged_above=-999 required=5 tests=[AWL=-0.908, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lplWnAefzPU6 for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 10:34:07 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 806EC21F85EF for <ietf@ietf.org>; Sun, 12 Aug 2012 10:34:07 -0700 (PDT)
Received: from [128.9.176.29] (c1-vpn3.isi.edu [128.9.176.29]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q7CHXawE005478 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 12 Aug 2012 10:33:40 -0700 (PDT)
Message-ID: <5027E8EE.8010109@isi.edu>
Date: Sun, 12 Aug 2012 10:33:34 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FE2715C.2090601@necom830.hpcl.titech.ac.jp> <4FF20DE7.2080208@isi.edu> <500654AB.7060500@necom830.hpcl.titech.ac.jp> <8F5CBE79-4540-4519-9F51-62B36686EE8C@isi.edu> <501C5C75.9040209@necom830.hpcl.titech.ac.jp> <501C6441.4000302@isi.edu> <5020C32A.4060907@necom830.hpcl.titech.ac.jp> <50215032.7090800@isi.edu> <5027767A.60601@necom830.hpcl.titech.ac.jp>
In-Reply-To: <5027767A.60601@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=ISO-2022-JP
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: Sun, 12 Aug 2012 17:34:08 -0000

Again, this doc is about updating the IPv4 ID specification in RFC791 -
which has not yet been updated.

The IPv6-IPv4 translation that creates IPv4 IDs is currently
non-compliant with RFC791 and does not override RFC791. This document's
update might make that translation easier, but it doesn't make it worse
- which is why there remains no need to address that issue in this doc.

If you disagree with that conclusion, please contact the INTAREA WG
chairs directly.

Joe

On 8/12/2012 2:25 AM, Masataka Ohta wrote:
> Joe Touch wrote:
> 
> Hi,
> 
>>>>> RFC2765 specifies that translators can merely copy the
>>>>> low-order bits of the field.
>>>>
>>>> Yes, but this is not compatible with RFC791.
>>>
>>> Then, which should we revice? RFC791, RFC2765 or both?
>>
>> 2765.
> 
> Is it a consensus of IETF?
> 
> Note that it also imply revising RFC2460, because rfc2765 specifies
> a way of ID mapping, where as rfc2460 specifies 32bit->16bit mapping
> will be performed by translators.
> 
> Note also that there already are working implementations of
> rfc2460 and rfc2765.
> 
>> There is no useful way to revise 791 to make the text in 2765 correct.
> 
> Revising rfc791 not requiring a very strong uniqueness is
> useful reflecting current practice better than your draft,
> even though your draft claims "closely reflect current
> practice".
> 
> Moreover, I can see no useful way to revise rfc2765. Do you
> have any suggestion?
> 
>>> Without such a decision, there is no point to publish something
>>> based on RFC791 and is not compatible with RFC2765.
>>
>> Sure there is - when IPv6 is not involved.
> 
> But, your draft involves IPv6 and, for example, the following
> statement in your draft:
> 
>     IPv6, even at typical MTUs, is capable of 18.7 Tbps with
>     fragmentation between two IP endpoints as an aggregate across all
>     protocols,
> 
> is not compatible with rfc2460 and rfc2765.
> 
>> An IPv6 source might never send packets larger than IPv4 can natively
>> handle - i.e., it could send packets 576 bytes or smaller. In that case,
>> the IPv6 source would never get an ICMP "too big" because they're not as
>> far as IPv4 is concerned. In that case, the IPv6 source would never
>> insert the Fragmentation Header.
> 
> I'm afraid minimum MTU of IPv4 is 68, not 576 bytes.
> 
> Anyway, IPv6 node having no idea on PMTU will send a lot of
> exactly 1280 byte long packets, because it will make TCP
> most efficient.
> 
>> That is the fundamental flaw in these IPv6 RFCs, but it is behavior that
>> is out of scope for an IPv4 source. My doc focuses on the behavior of
>> IPv4 sources.
> 
> While I think IPv6 RFCs have many fundamental flaws, a problem
> is that there are people in IETF insisting not to admit them
> flaws.
> 
> Do you think you can make them admit a flaw?
> 
>>> That is the problem. That is, if you insist on RFC791 as is, not
>>> enough is specified on how to generate IPv6 ID.
>>
>> Yes, but that does not affect an IPv4 source; it remains a problem, but
>> out of scope for this doc.
> 
> It is out of scope, if only rfc791 is not revised.
> 
> 
>>> Thus, there can be only one way (the one in RFC2765) to map IPv6
>>> ID to IPv4 ID
> 
>> Yes, this is a nice goal, but it would have required IPv6 hosts insert
>> 16-bit IDs into *every* packet and make them just as unique as IPv4 does.
> 
> No, not *every* packet. But, as you wrote:
> 
>>>> Further, the source might already be inserting the fragmentation header
>>>> (e.g., on a 2KB packet).
> 
> every such packet is required to have a unique 32bit ID which must
> also be unique as a 16bit ID after translation.
> 
>>> Then, as fixing RFC2460 is politically impossible, we must
>>> abandone IPv6 and live with IPv4 forever.
>>
>> I didn't say we couldn't fix - or at least try to fix - this situation.
>> But it remains out of scope for this doc.
> 
> If only you can convince people we should fix rfc2460, not rfc791.
> 
>>> but, "the specification of the similar field in IPv6" is, in
>>> your opinion, incomplete, let's finish it first,
>>
>> IPv6 is fine when it talks to IPv6 only. The goal is to make IPv4 work
>> in a similar way.
> 
> You are saying dual stack is clean and the way to go and all the
> other IPv6 deployment scenarios should be ignored.
> 
>> it doesn't make it completely correct, though - there remain
>> problems that have nothing to do with the changes in this doc that need
>> to be addressed separately.
> 
> The question is whether you can have a consensus that rfc2460
> is not completely correct or not.
> 
>>> For another example,
>>>
>>>       Finally, the IPv6 ID field is
>>>       32 bits, and required unique per source/destination address pair for
>>>       IPv6,
>>>
>>> is, in your opinion, violation of RFC791.
>>
>> No; the violation occurs only when the lower 16 bits are masked off and
>> used by themselves by on-path translators. That has nothing to do with
>> the quoted text above.
> 
> The problem is that, if rfc2460 is not "completely correct", above
> text in your draft should be something based not on the current
> rfc2460 but on completely correctly revised rfc2460, such as
> "IPv6 ID field is required unique after translated into 16 bit
> IPv4 ID".
> 
>> But neither of the above requires that IPv6 IDs must be easily
>> translatable into valid IPv4 addresses using the existing mechanism.
> 
> IPv4 addresses? What do you mean?
> 
> 						Masataka Ohta
> 

From brian.e.carpenter@gmail.com  Sun Aug 12 10:34:47 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E986C21F85F0 for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 10:34:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.498
X-Spam-Level: 
X-Spam-Status: No, score=-101.498 tagged_above=-999 required=5 tests=[AWL=0.193, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wibO3B+zdWi8 for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 10:34:47 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id C284521F8622 for <ietf@ietf.org>; Sun, 12 Aug 2012 10:34:46 -0700 (PDT)
Received: by weyu54 with SMTP id u54so2318253wey.31 for <ietf@ietf.org>; Sun, 12 Aug 2012 10:34:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=JJSGQBN8B3g+jgIQtuIXHWEs33cfK3lBEv9mQ3hwHu4=; b=hJcKjyZRseZIagmTKgeDcdbfc9f5ilPyxduv2gEsap3rP7nHAglGJAWVOkJqy6dPCm kDaqvinA1b6vYxDbPx51IwHluia8UotWDY6o3FfQSDHrFXioK4yUhwUH/PCbBTaMyiOS QH//9iZ7YJpz8796uVi5Nbqfg0CHRh85pdFDCFmizaXq2363pS405ZECSnCtngTQJwfD R/lqfROdOlp7FoWfh4WhE+LW/iOQrmIQDFu/9DcKZ2Gqa9xmIJ4sYc3k6DWsho8h1MIW G5Ch1SFSOj6gDugi7qxuwBfH/GfmaEiubuzEUAM+JmC4WeYtP/DWfX/gfnEbORhIfN73 g9zg==
Received: by 10.216.209.8 with SMTP id r8mr5189970weo.51.1344792885813; Sun, 12 Aug 2012 10:34:45 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-150.as13285.net. [2.102.217.150]) by mx.google.com with ESMTPS id eu4sm11666508wib.2.2012.08.12.10.34.44 (version=SSLv3 cipher=OTHER); Sun, 12 Aug 2012 10:34:44 -0700 (PDT)
Message-ID: <5027E934.7000102@gmail.com>
Date: Sun, 12 Aug 2012 18:34:44 +0100
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: Metadiscussion [Last Call: Modern Global Standards Paradigm]
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com>	<50266F05.5050601@dcrocker.net>	<1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org>	<50267826.70307@bbiw.net>	<CAC4RtVARm1fXvHR4dv9Jh0HttW+ORhRx36kwF54RRjc4aOh1AQ@mail.gmail.com>	<5027D0B2.80306@bbiw.net>	<CALaySJKzxo=oHLcDxT=RbrwMK=pTSh6vxY-VvLZ0C5wf+T-DQQ@mail.gmail.com> <5027D67B.2030409@dcrocker.net>
In-Reply-To: <5027D67B.2030409@dcrocker.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Aug 2012 17:34:48 -0000

Dave,

On 12/08/2012 17:14, Dave Crocker wrote:
...
> Again, what's happening here is a form of 'let's ignore IETF process
> because this is such a wonderful cause'.
> 
> It is, indeed, a wonderful cause, but I don't recall our establishing
> rules that are to be applied only when we feel like it, or in varied
> manner that our management decides is sufficient.

Quite true. However, RFC 2026 lays down rules for standards track
documents, and extends them to IETF process documents by stating
that they are published as BCPs.

It doesn't lay down rules for actions such as signing a declaration
of common general policy with other SDOs*. In my opinion, it is
completely appropriate for the IAB, IESG and the IETF Chair to adopt
an abbreviated or adapted procedure for such documents.

* In fact, this type of thing seems to be in the IAB's remit, BCP 39,
section 2, clause (f) "External Liaison: ...other technical and
organizational issues relevant to the world-wide Internet."

Regards
    Brian

From stbryant@cisco.com  Sun Aug 12 10:51:44 2012
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F6E421F8606 for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 10:51:44 -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.014, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nvBEgieYuaAB for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 10:51:43 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 7019121F85ED for <ietf@ietf.org>; Sun, 12 Aug 2012 10:51:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=342; q=dns/txt; s=iport; t=1344793903; x=1346003503; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=0gNJQ+s8ACYck+08HYe66v8ihtg39fSGoaFiNpLAmsM=; b=lNjpM6D/lbz8ODvLzOUZoK9j0lR9yFVCQze6dhRHq2cNdeQSgsbMJWS3 jyBR6QqYfSEL6hDisUZPGQhumrqpuz9V5nEWYtpSDVMq75924Bi0nf65C d14/C8iNkOsUHYb6QsS/8KwdFtMDV5cYIpmD1lcO3mHJNYQxBTfOFWCGd k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EANPrJ1CQ/khN/2dsb2JhbABEuXqBB4IhAQEEEgECI0ABEAshFg8JAwIBAgFFEAMBBwEBHodrmTCDSBCbP44ngxwDlUuOKoEEYoJg
X-IronPort-AV: E=Sophos;i="4.77,756,1336348800";  d="scan'208";a="7286972"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-3.cisco.com with ESMTP; 12 Aug 2012 17:51:39 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q7CHpcE1007336 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 12 Aug 2012 17:51:39 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q7CHpZ8s021313; Sun, 12 Aug 2012 18:51:36 +0100 (BST)
Message-ID: <5027ED27.2040403@cisco.com>
Date: Sun, 12 Aug 2012 18:51:35 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: [IAB] Last Call: Modern Global Standards Paradigm
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com> <50266F05.5050601@dcrocker.net> <1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org> <50267826.70307@bbiw.net> <CAC4RtVARm1fXvHR4dv9Jh0HttW+ORhRx36kwF54RRjc4aOh1AQ@mail.gmail.com> <5027D0B2.80306@bbiw.net> <CALaySJKzxo=oHLcDxT=RbrwMK=pTSh6vxY-VvLZ0C5wf+T-DQQ@mail.gmail.com> <5027D67B.2030409@dcrocker.net>
In-Reply-To: <5027D67B.2030409@dcrocker.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IAB <iab@iab.org>, Barry Leiba <barryleiba@computer.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Aug 2012 17:51:44 -0000

Dave

If I interpret what you seem to be saying, it is that you care
more for the micro-observance of IETF protocol, than
taking steps to avoid Internet governance being
transferred by government decree to a secretive
agency of the UN that runs by government majority.

Is that a correct assessments of your priorities?

Stewart


From jmabdp@gmail.com  Sun Aug 12 11:10:00 2012
Return-Path: <jmabdp@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0767121F852E for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 11:10:00 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F8emPVDguVyA for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 11:09:59 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 036C821F85ED for <ietf@ietf.org>; Sun, 12 Aug 2012 11:09:58 -0700 (PDT)
Received: by bkty7 with SMTP id y7so1312870bkt.31 for <ietf@ietf.org>; Sun, 12 Aug 2012 11:09:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=YymqBxjQfJrqs3zlwdLAqw0iNGJ1GZ22cfdD0RVMz90=; b=WeemF0rIZbCUm9UmkCKhRn6Gb2Zdelk0odlYzGHsuD9mc/XL2ROBOd4XGCHO8q9J2c ibvJFZXVPV6tWNTQYHPndX/y5eJatOpc+b4elNQ4FB76r/a/9RTNqVAwYs0Od20ByVIr nKLejfBCgl8jTmldJYnntJFK7v2R87MIELxF6VquRg9GADMmDWxsFGHCEZ88kCXBZcNq QOH2cWanbYQClTVKnWF8FpFF0jAVKbqKACW3Hp//XfnW9SjeFGEcR1j0yUB7P5EaNc4c o3FKVSrWoA0bx2PiFRtM71qOxog7EF5owHxHtycp9pC6Mpuls7wyMas8yorLMBJGrlzL LYAw==
MIME-Version: 1.0
Received: by 10.205.137.8 with SMTP id im8mr3180718bkc.135.1344794997735; Sun, 12 Aug 2012 11:09:57 -0700 (PDT)
Received: by 10.204.113.78 with HTTP; Sun, 12 Aug 2012 11:09:57 -0700 (PDT)
Date: Sun, 12 Aug 2012 20:09:57 +0200
Message-ID: <CAGzJzZ5GFPsoasfLB8hGmVB5DWGKED2acs7CwfSWbp_JFXu7Mg@mail.gmail.com>
Subject: Modern Global Standards Paradigm
From: jean-michel bernier de portzamparc <jmabdp@gmail.com>
To: IETF <ietf@ietf.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Aug 2012 18:10:00 -0000

For your information the IUSG (interested in the Intelligent Use of
the whole digital ecosystem) has just released the following statement
which reflect a friendly but non-IETF evaluation of the "Modern Global
Standards Paradigm" document proposed by the IETF and IAB Chairs to
the endorsement of other SDOs and proposes a way to best build on it.
Portzamparc

This matter is a matter of trust in the IETF (as well as in the whole
US organized I* structural set: ICANN, IANA, GAC) and how to
restore/maintain confidence.

As IUsers (Members of the IUse community interested in an intelligent
use of the whole digital ecosystem), FLOSS developers, end-users,
governments, and operators, we are accustomed to trusting the ITU in
its plug to plug basic interconnection services area. We are not
accustomed yet to trusting the =93I*=94 structural set in its end to end
value-added interoperations service area.
This is for the very reasons that the IAB started to pertinently
document but with no effective result in RFC 3869.
This is because the IETF did not want to participate in the WSIS consensus.
This is because the IETF considered us in the way that they think the
ITU considers them.
This is due to our patient and friendly (sometimes tough) experience
of the ICANN, ISOC, IETF, IANA, and GAC attitude and culture.

We want this to be corrected, the IETF to relax, and everyone to
obtain clearer documentation of the UDP/TCP/SCTP strata, to ensure
that the Internet technology and its R&D are not under direct or
indirect commercial influence and its governance is not solely
conducted by the USG. This is also the case because some of us and
commercial interests as well are engaged in exploring, testing, and
documenting, in coordination with the IETF, the fringe to fringe
extended services =93Internet+=94 area, and its non-ITU/IETF documented
layers. We need credibility, stability, and homogeneity and simple
interfaces in the Internet area as all of us currently have from the
ITU. Please understand that in this Internet+ endeavor we do not want
to obey the ITU and IETF more than you want to obey the ITU and our
emerging IUTF. However, we need non blocking clarity, transparency,
and predictability.

Our suggestion is, instead of unilaterally promoting a standardization
BCP in pure American IETF language along a non IETF documented
process, to propose an RFC 3869bis open working group with people from
all the concerned SDOs, the ITU to begin with, in order to reflect a
standardization world ethitechnical (ethic of technical
standardization) consensus on the way, not to best sign clients or
deliver to subscribers, but to intelligently serve us, the users.

To contribute to this effort, we have engaged ourselves in a
reflection on the matter at
http://iutf.org/wiki/Modern_Global_Standards_Paradigm. We will see how
it develops. Should a WG/RFC3869Bis be created, IUSG would certainly
participate.

(http://iusg.org/wiki/20120813_-_Statement_proposing_an_open_IETF/WG/RFC386=
9bis):

From paul.hoffman@vpnc.org  Sun Aug 12 11:22:22 2012
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 BFD4D21F85D4; Sun, 12 Aug 2012 11:22:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.582
X-Spam-Level: 
X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OAb5mHdWuvxI; Sun, 12 Aug 2012 11:22:22 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 3789021F85CE; Sun, 12 Aug 2012 11:22:22 -0700 (PDT)
Received: from [10.20.30.100] (50-1-50-97.dsl.dynamic.fusionbroadband.com [50.1.50.97]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q7CIMFss076506 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 12 Aug 2012 11:22:15 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: [IAB] Last Call: Modern Global Standards Paradigm
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=windows-1252
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <5027ED27.2040403@cisco.com>
Date: Sun, 12 Aug 2012 11:22:13 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <32814AA9-FAE1-464D-A696-0B43F0A53FBC@vpnc.org>
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com> <50266F05.5050601@dcrocker.net> <1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org> <50267826.70307@bbiw.net> <CAC4RtVARm1fXvHR4dv9Jh0HttW+ORhRx36kwF54RRjc4aOh1AQ@mail.gmail.com> <5027D0B2.80306@bbiw.net> <CALaySJKzxo=oHLcDxT=RbrwMK=pTSh6vxY-VvLZ0C5wf+T-DQQ@mail.gmail.com> <5027D67B.2030409@dcrocker.net> <5027ED27.2040403@cisco.com>
To: stbryant@cisco.com
X-Mailer: Apple Mail (2.1278)
Cc: IAB <iab@iab.org>, Dave Crocker <dcrocker@bbiw.net>, ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Aug 2012 18:22:22 -0000

On Aug 12, 2012, at 10:51 AM, Stewart Bryant wrote:

> If I interpret what you seem to be saying, it is that you care
> more for the micro-observance of IETF protocol, than
> taking steps to avoid Internet governance being
> transferred by government decree to a secretive
> agency of the UN that runs by government majority.
>=20
> Is that a correct assessments of your priorities?

Another possibility is that Dave simply wanted to start yet another =
process discussion, and he thought this was the appropriate time and =
thread for it. A corollary to Hanlon's razor is "never attribute to =
malice that which is adequately explained by bureaucracy".

--Paul Hoffman, whose support for the proposal remains positive=

From brian.e.carpenter@gmail.com  Sun Aug 12 11:40:29 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 947D721F85FF for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 11:40:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.756
X-Spam-Level: 
X-Spam-Status: No, score=-100.756 tagged_above=-999 required=5 tests=[AWL=-0.554, BAYES_05=-1.11, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gSTx7nqwqG-j for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 11:40:28 -0700 (PDT)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8528B21F85D7 for <ietf@ietf.org>; Sun, 12 Aug 2012 11:40:28 -0700 (PDT)
Received: by wicr5 with SMTP id r5so1474599wic.13 for <ietf@ietf.org>; Sun, 12 Aug 2012 11:40:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=tmmhDMakK3mqku9kDDyrU2/nTIV+5VdNYr5KLvMxivw=; b=0IKvHWFTp+AfQMLLzgCw5PtbpDe/GBg2QCTEx0J1vDTNrL4h45H2XUw81tYsqRsFWB ITSN7dGUjLZlECngjTfYSNcwpziDXQyfztqaA7jJI9aqKYSRR4PVgsLQaSYXMr1OilCf a/MYcQ4EvmAPurCnqCVc3eASX+oc52Wy4ZeLPmtlHCMSGiHJBp9c0ivgm6Bbf4g/8eHj LOq/ZXGYkFwA5Wi8Rl7DWF89JIyWm6vhPa5NyzSH58xdoJGBCEx7Gp0rI1UJYnpdD5JO XJ0Dg6ODcpNcHFxl5GcIrYMki9jTFy3Kq6Hk+fEERKUkGq151h8xUoNtwRZTWBPeVHhi K1XA==
Received: by 10.180.85.167 with SMTP id i7mr12209766wiz.8.1344796827511; Sun, 12 Aug 2012 11:40:27 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-150.as13285.net. [2.102.217.150]) by mx.google.com with ESMTPS id ep14sm12623661wid.0.2012.08.12.11.40.25 (version=SSLv3 cipher=OTHER); Sun, 12 Aug 2012 11:40:26 -0700 (PDT)
Message-ID: <5027F89A.4080006@gmail.com>
Date: Sun, 12 Aug 2012 19:40:26 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF <ietf@ietf.org>
Subject: Re: Modern Global Standards Paradigm
References: <CAGzJzZ5GFPsoasfLB8hGmVB5DWGKED2acs7CwfSWbp_JFXu7Mg@mail.gmail.com>
In-Reply-To: <CAGzJzZ5GFPsoasfLB8hGmVB5DWGKED2acs7CwfSWbp_JFXu7Mg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Aug 2012 18:40:29 -0000

For those utterly mystified by the recent message under the above subject
header, let me note that my spam folder earlier today included a rather
incomprehensible message from JFC Morfin. I'm about to add jean-michel
bernier de portzamparc to my spam filters too, of course.

Alternatively, you could waste your time trying to make sense of those
messages. Good luck with that.

Regards
   Brian

From bernard_aboba@hotmail.com  Sun Aug 12 12:04:24 2012
Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7B5721F866E for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 12:04:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.366
X-Spam-Level: 
X-Spam-Status: No, score=-102.366 tagged_above=-999 required=5 tests=[AWL=0.232, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ePFUzkkMuTrO for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 12:04:24 -0700 (PDT)
Received: from blu0-omc2-s2.blu0.hotmail.com (blu0-omc2-s2.blu0.hotmail.com [65.55.111.77]) by ietfa.amsl.com (Postfix) with ESMTP id 8EF4021F8668 for <ietf@ietf.org>; Sun, 12 Aug 2012 12:04:23 -0700 (PDT)
Received: from BLU169-DS8 ([65.55.111.71]) by blu0-omc2-s2.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 12 Aug 2012 12:04:23 -0700
X-Originating-IP: [24.16.96.166]
X-EIP: [L2TsDHUwpz/fn9y0yFMjv3L83V01CL0H]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU169-DS8ABEDAB29BAD65569BFC293B10@phx.gbl>
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: <ietf@ietf.org>
Subject: Re: [IAB] Last Call: Affirmation of the Modern Global Standards Paradigm
Date: Sun, 12 Aug 2012 12:05:09 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0146_01CD7882.B84B32F0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac14vTr4K9SiFg9zRUGmDQzM0ZUYnA==
Content-Language: en-us
X-OriginalArrivalTime: 12 Aug 2012 19:04:23.0066 (UTC) FILETIME=[48E3E7A0:01CD78BD]
Cc: Dave CROCKER  <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Aug 2012 19:04:25 -0000

------=_NextPart_000_0146_01CD7882.B84B32F0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

[BA] The reply below represents my personal opinion. 

 

Dave Crocker said:

 

> It's true that this was not put into an Internet Draft. Apart from 
> that, we seem to be doing the right thing: - The IAB Chair announced 
> the text and the intent to sign it on 1 Aug. 
 
Two weeks is normal process for spontaneous consensus calls? 
 
When did the community approve that change in process? 

 

[BA]  Thanks for raising this issue, Dave.  

 

A document that describes the processes utilized by Modern SDOs should
probably take extra care to follow the applicable process.  

 

Below find my best guess as to what that is. 

 

At one point the suggestion was to publish the statement as an RFC; had this
been done, the procedures to be followed would have

been governed by the procedures for publication on the selected stream.  For
example, if the document were to have been published 

as an Informational RFC within the IAB stream, then RFC 4845 would apply.
Section 3 states:

 

   5.  The chair of the IAB issues an IETF-wide Call for Comment on the

       IETF Announce mailing list.  The comment period is normally no

       shorter than four weeks.

 

However, AFAIK this document is not being considered for publication as an
RFC (at least within the IAB stream), so RFC 4845 does not apply.  

 

> He asked for comments. 
 
No he didn't: 
 
"Please send strong objections..." 
 
This asserts a forceful bias against general comments and criticisms by 
establishing a very high threshhold for relevance. While no, no one is 
prevented from other kinds of postings, the bias is nonetheless established.

 

[BA] Specifically, comments were requested to be sent to the IAB and/or to
the IETF list.   In the first iteration of comments, the IAB mailing list
was given as the place to send comments, and a number of comments were
received which resulted in changes to the document.  While it might be
considered inconvenient, similarly persuasive comments could be received in
this round as well.  

 

As noted in the announcement, the intent is for the document to be signed by
the IETF and IAB Chairs, both of whom are members of the IAB.  Were the
process followed in approval of IAB statements to be applied here, then IAB
consensus would be required for approval.  In making up their minds, members
of the IAB can consider any relevant information, including the comments in
this and the earlier round.  Personally, in making up my mind I would look
at the comments on their merit, ignoring the threshold in the announcement.



------=_NextPart_000_0146_01CD7882.B84B32F0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* 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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>[BA] The =
reply below represents my personal opinion. <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Dave Crocker =
said:<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>&gt; It's true that this was not put into an Internet =
Draft. Apart from&nbsp;<br>&gt; that, we seem to be doing the right =
thing: - The IAB Chair announced&nbsp;<br>&gt; the text and the intent =
to sign it on 1 Aug.&nbsp;<br>&nbsp;<br>Two weeks is normal process for =
spontaneous consensus calls?&nbsp;<br>&nbsp;<br>When did the community =
approve that change in process?&nbsp;<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>[BA] =
&nbsp;Thanks for raising this issue, Dave.&nbsp; <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>A document =
that describes the processes utilized by Modern SDOs should probably =
take extra care to follow the applicable process. =
&nbsp;<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Below find my best guess as to what that is. =
<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>At one point the suggestion was to publish the =
statement as an RFC; had this been done, the procedures to be followed =
would have<o:p></o:p></p><p class=3DMsoNormal>been governed by the =
procedures for publication on the selected stream. &nbsp;For example, if =
the document were to have been published <o:p></o:p></p><p =
class=3DMsoNormal>as an Informational RFC within the IAB stream, then =
RFC 4845 would apply. &nbsp;Section 3 states:<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
5.&nbsp; The chair of the IAB issues an IETF-wide Call for Comment on =
the<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IETF Announce mailing =
list.&nbsp; The comment period is normally no<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; shorter than four =
weeks.<o:p></o:p></span></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>However, AFAIK this document is not being considered =
for publication as an RFC (at least within the IAB stream), so RFC 4845 =
does not apply.&nbsp; <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>&gt; He =
asked for comments.&nbsp;<br>&nbsp;<br>No he =
didn't:&nbsp;<br>&nbsp;<br>&quot;Please send strong =
objections...&quot;&nbsp;<br>&nbsp;<br>This asserts a forceful bias =
against general comments and criticisms by&nbsp;<br>establishing a very =
high threshhold for relevance. While no, no one is&nbsp;<br>prevented =
from other kinds of postings, the bias is nonetheless =
established.&nbsp;<br>&nbsp;<o:p></o:p></p><p class=3DMsoNormal>[BA] =
Specifically, comments were requested to be sent to the IAB and/or to =
the IETF list. &nbsp;&nbsp;In the first iteration of comments, the IAB =
mailing list was given as the place to send comments, and a number of =
comments were received which resulted in changes to the document. =
&nbsp;While it might be considered inconvenient, similarly persuasive =
comments could be received in this round as well. =
&nbsp;<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>As noted in the announcement, the intent is for the =
document to be signed by the IETF and IAB Chairs, both of whom are =
members of the IAB. &nbsp;Were the process followed in approval of IAB =
statements to be applied here, then IAB consensus would be required for =
approval.&nbsp; In making up their minds, members of the IAB can =
consider any relevant information, including the comments in this and =
the earlier round. &nbsp;Personally, in making up my mind I would look =
at the comments on their merit, ignoring the threshold in the =
announcement. &nbsp;<o:p></o:p></p></div></body></html>
------=_NextPart_000_0146_01CD7882.B84B32F0--

From jmabdp@gmail.com  Sun Aug 12 12:38:15 2012
Return-Path: <jmabdp@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8936521F8679 for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 12:38:15 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n45blaIMWNaa for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 12:38:15 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id D555F21F864A for <ietf@ietf.org>; Sun, 12 Aug 2012 12:38:14 -0700 (PDT)
Received: by bkty7 with SMTP id y7so1331767bkt.31 for <ietf@ietf.org>; Sun, 12 Aug 2012 12:38:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=le1xUWtDo2Bc3gxX86p+S9L4WFJj/W3q5mVbnuLgFPg=; b=UdP7dJjw3SlOpXbIdXt9Eahr+ZHmjsxpBtbxxCpyrQbf7ClPobwKV/tuVCQx514KmC 9JRhPQB1Fz6oeTnp8d/AxaCIaq37rp+cDtWVVKudU7HO/R4/thkYCLVcZujpPCA7/egb 8VhFBBdcjfaqkFcEx28fx56tbSmblW+37P1PhXMCzAuamtWkXV9esudyREawXbzDJeRd jTKko4I6O50ufREsurgHiSZlIuoKsIKTRaBn0Ko5W+I6k9R6IZy67Eufxv7QqxZa7Dr4 rK6ZsWKi4iWtOPpdJQud9Gv2bSpi4HVQDxBmF2D9y1p9SMgFcR2GcjE996KC/b3SPj8c 7+9A==
MIME-Version: 1.0
Received: by 10.204.153.10 with SMTP id i10mr3285612bkw.67.1344800293900; Sun, 12 Aug 2012 12:38:13 -0700 (PDT)
Received: by 10.204.113.78 with HTTP; Sun, 12 Aug 2012 12:38:13 -0700 (PDT)
In-Reply-To: <5027F89A.4080006@gmail.com>
References: <CAGzJzZ5GFPsoasfLB8hGmVB5DWGKED2acs7CwfSWbp_JFXu7Mg@mail.gmail.com> <5027F89A.4080006@gmail.com>
Date: Sun, 12 Aug 2012 21:38:13 +0200
Message-ID: <CAGzJzZ44aHyq1Sq8m52dodZ5fxfyMfROFo+GvWtWB2Dd9VSnQg@mail.gmail.com>
Subject: Re: Modern Global Standards Paradigm
From: jean-michel bernier de portzamparc <jmabdp@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Aug 2012 19:38:15 -0000

Dear Mr. Carpenter,
I do not understand this.
Would you want to examplify the ITU supposed good manners?
I am lost.
Portzamparc

2012/8/12 Brian E Carpenter <brian.e.carpenter@gmail.com>:
> For those utterly mystified by the recent message under the above subject
> header, let me note that my spam folder earlier today included a rather
> incomprehensible message from JFC Morfin. I'm about to add jean-michel
> bernier de portzamparc to my spam filters too, of course.
>
> Alternatively, you could waste your time trying to make sense of those
> messages. Good luck with that.
>
> Regards
>    Brian

From mcr+ietf@sandelman.ca  Sun Aug 12 14:06:53 2012
Return-Path: <mcr+ietf@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 2456D21F8620 for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 14:06:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.319
X-Spam-Level: 
X-Spam-Status: No, score=-2.319 tagged_above=-999 required=5 tests=[AWL=0.281,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l4jRhukuri2L for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 14:06:52 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 998BC21F8606 for <ietf@ietf.org>; Sun, 12 Aug 2012 14:06:52 -0700 (PDT)
Received: from obiwan.sandelman.ca (unknown [IPv6:2607:f0b0:f:2:3a60:77ff:fe38:e647]) by tuna.sandelman.ca (Postfix) with ESMTP id 42F5E20177; Sun, 12 Aug 2012 17:19:53 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: jean-michel bernier de portzamparc <jmabdp@gmail.com>
Subject: Re: Modern Global Standards Paradigm
In-Reply-To: <CAGzJzZ44aHyq1Sq8m52dodZ5fxfyMfROFo+GvWtWB2Dd9VSnQg@mail.gmail.com>
References: <CAGzJzZ5GFPsoasfLB8hGmVB5DWGKED2acs7CwfSWbp_JFXu7Mg@mail.gmail.com> <5027F89A.4080006@gmail.com> <CAGzJzZ44aHyq1Sq8m52dodZ5fxfyMfROFo+GvWtWB2Dd9VSnQg@mail.gmail.com>
X-Mailer: MH-E 8.3; nmh 1.5; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Sun, 12 Aug 2012 17:06:42 -0400
Message-ID: <10664.1344805602@obiwan.sandelman.ca>
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, 12 Aug 2012 21:06:53 -0000

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


>>>>> "jean-michel" =3D=3D jean-michel bernier de portzamparc <jmabdp@gmail=
.com> writes:
    jean-michel> Dear Mr. Carpenter,
    jean-michel> I do not understand this.
    jean-michel> Would you want to examplify the ITU supposed good manners?
    jean-michel> I am lost.

So am I.
You process to represent open source developers.

Yes, many of us are concerned about USG control over ICANN, but
I don't know where/how you pretend to represent "us", when we can't even
agree on much at all on a good day.

It's funny though, "I*" pattern matches ITU as well.


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

{And.. why is some kind of open standards/open source person posting
messages that are in:
   Content-Type: text/plain; charset=3Dwindows-1252

(noticed the "smart-quotes" which do not render for me)... okay, 2
points for actually announcing that your message is in a non-standard
character set, but minus 10 for using that.}

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


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

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

iQCVAwUAUCga4oqHRg3pndX9AQJuMwP/YhaAmOvkhfBdTtyPNTSU1Y7gsVrP+23N
Rg5tdcPyWeNJSwz5JNs9ZmUnC9AJl5sbnw2eInSJ/kZOT4zFvHvGBlDuZSoSVCbp
F3W8ZA9/DcPYAzaErUDmCLigRyIP0aj/Nwy2R0GA1CFKHRUDrPE/Mvlw3Uzajdv2
UUvMKLJKZts=
=/yB9
-----END PGP SIGNATURE-----
--=-=-=--

From cabo@tzi.org  Sun Aug 12 14:49:58 2012
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B108F21F8605; Sun, 12 Aug 2012 14:49:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.334
X-Spam-Level: 
X-Spam-Status: No, score=-106.334 tagged_above=-999 required=5 tests=[AWL=-0.085, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IfIiFLzfMo04; Sun, 12 Aug 2012 14:49:58 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id E2ECE21F85E1; Sun, 12 Aug 2012 14:49:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q7CLnb44021008; Sun, 12 Aug 2012 23:49:37 +0200 (CEST)
Received: from [192.168.217.105] (p5489298A.dip.t-dialin.net [84.137.41.138]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id EA020B95; Sun, 12 Aug 2012 23:49:36 +0200 (CEST)
Subject: Re: [IAB] Last Call: Modern Global Standards Paradigm
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Content-Type: text/plain; charset=windows-1252
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <5027ED27.2040403@cisco.com>
Date: Sun, 12 Aug 2012 23:49:35 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DDFE0F39-380E-49DB-B0E5-451AB659AFAE@tzi.org>
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com> <50266F05.5050601@dcrocker.net> <1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org> <50267826.70307@bbiw.net> <CAC4RtVARm1fXvHR4dv9Jh0HttW+ORhRx36kwF54RRjc4aOh1AQ@mail.gmail.com> <5027D0B2.80306@bbiw.net> <CALaySJKzxo=oHLcDxT=RbrwMK=pTSh6vxY-VvLZ0C5wf+T-DQQ@mail.gmail.com> <5027D67B.2030409@dcrocker.net> <5027ED27.2040403@cisco.com>
To: stbryant@cisco.com
X-Mailer: Apple Mail (2.1485)
Cc: IAB <iab@iab.org>, "dcrocker@bbiw.net Crocker" <dcrocker@bbiw.net>, ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Aug 2012 21:49:58 -0000

On Aug 12, 2012, at 19:51, Stewart Bryant <stbryant@cisco.com> wrote:

> If I interpret what you seem to be saying, it is that you care
> more for the micro-observance of IETF protocol, than
> taking steps to avoid Internet governance being
> transferred by government decree to a secretive
> agency of the UN that runs by government majority.

That is the question that is not clear to me either.

I do believe the process question is an absolutely useful one.  We =
should have a process that is able to handle multilateral activities =
that include the IETF, with an element of negotiation, even compromise, =
and so on.  This is a case where leadership is actually required, and I =
don't think that process is an established one at all.  We do know how =
to run liaisons, which is probably the closest model to adhere to.  We =
know why we have handed the keys to this to the IAB.  (The present =
document is not prescriptive anyway, it is descriptive, and the IETF =
chair in concert with the IAB chair should be able to act on this level =
after a modicum of consultation.)

If the process question was actually raised to derail the signing of the =
current document, my reaction would be quite similar to Stewart's.
As I said before, sometimes you have to act.

Gr=FC=DFe, Carsten


From lixia@cs.ucla.edu  Sun Aug 12 15:34:55 2012
Return-Path: <lixia@cs.ucla.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9266621F86C1 for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 15:34:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LPpSMQ1KYhMZ for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 15:34:55 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by ietfa.amsl.com (Postfix) with ESMTP id D7F8421F86B0 for <ietf@ietf.org>; Sun, 12 Aug 2012 15:34:46 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 3E38EA6000B; Sun, 12 Aug 2012 15:34:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1]) by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ASsdI2UhvOSO; Sun, 12 Aug 2012 15:34:45 -0700 (PDT)
Received: from [10.0.1.5] (cpe-98-154-13-152.socal.res.rr.com [98.154.13.152]) by smtp.cs.ucla.edu (Postfix) with ESMTPSA id C5662A60002; Sun, 12 Aug 2012 15:34:45 -0700 (PDT)
Subject: Re: [IAB] Last Call: Modern Global Standards Paradigm
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=windows-1252
From: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <5027ED27.2040403@cisco.com>
Date: Sun, 12 Aug 2012 15:34:43 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A75A5D6-869F-4C19-9044-006CB9930AE4@cs.ucla.edu>
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com> <50266F05.5050601@dcrocker.net> <1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org> <50267826.70307@bbiw.net> <CAC4RtVARm1fXvHR4dv9Jh0HttW+ORhRx36kwF54RRjc4aOh1AQ@mail.gmail.com> <5027D0B2.80306@bbiw.net> <CALaySJKzxo=oHLcDxT=RbrwMK=pTSh6vxY-VvLZ0C5wf+T-DQQ@mail.gmail.com> <5027D67B.2030409@dcrocker.net> <5027ED27.2040403@cisco.com>
To: stbryant@cisco.com
X-Mailer: Apple Mail (2.1278)
Cc: IAB <iab@iab.org>, dcrocker@bbiw.net, Barry Leiba <barryleiba@computer.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Aug 2012 22:34:55 -0000

On Aug 12, 2012, at 10:51 AM, Stewart Bryant wrote:

> Dave
>=20
> If I interpret what you seem to be saying, it is that you care
> more for the micro-observance of IETF protocol, than
> taking steps to avoid Internet governance being
> transferred by government decree to a secretive
> agency of the UN that runs by government majority.
>=20
> Is that a correct assessments of your priorities?
>=20
> Stewart


Personally I do not feel the tone of this message is most appropriate in =
this ongoing discussion.

Lixia


From sm@resistor.net  Sun Aug 12 16:11:07 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF24121F85CC; Sun, 12 Aug 2012 16:11:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -92.55
X-Spam-Level: 
X-Spam-Status: No, score=-92.55 tagged_above=-999 required=5 tests=[AWL=-9.995, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, URIBL_BLACK=20, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6syMRwXr+cOf; Sun, 12 Aug 2012 16:11:03 -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 DC89A21F853E; Sun, 12 Aug 2012 16:11:03 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q7CNAvxq010813; Sun, 12 Aug 2012 16:11:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1344813062; bh=5qUmlgxdB/MBXUfyXm6hhiapuVrGZTmRyFQ/qS0BFto=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=hQh8UVekILqEbtMboL5Z0K8pxFVZapWSYP0zd/BhV3xjxfr8KkKBIinWGw4mc6pjY 7gIDcJgOLzpJe+1sRZFnLX9b+U04wtF9Ezi+DO3hqDTnjbBxvo58HpQaDeEkvMXE1Z xawNR2OJE6NDWcNEJBhar+6JfuLPTqu96JIeQexs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1344813062; i=@resistor.net; bh=5qUmlgxdB/MBXUfyXm6hhiapuVrGZTmRyFQ/qS0BFto=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=MnpZeyzpmOeLy7j7GdFHxUsGFwEtuvkklJkrifiOKth7NiYUtCngYCI9CNoHYlq+5 g4Zcc5uQ33jJ4J7bjhUxQcvS3EodyIBfQRyqapUGSpE2eslKsxLiN+PlFaMaKW6kqH 16bmzo3pmBRcMRh6hgEKKSaRv1nF/eOoXRs+G0pE=
Message-Id: <6.2.5.6.2.20120812105639.0af9bb58@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 12 Aug 2012 12:58:27 -0700
To: IAB <iab@iab.org>, IETF <ietf@ietf.org>
From: SM <sm@resistor.net>
Subject: Re: [IAB] Last Call: Modern Global Standards Paradigm
In-Reply-To: <5027ED27.2040403@cisco.com>
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com> <50266F05.5050601@dcrocker.net> <1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org> <50267826.70307@bbiw.net> <CAC4RtVARm1fXvHR4dv9Jh0HttW+ORhRx36kwF54RRjc4aOh1AQ@mail.gmail.com> <5027D0B2.80306@bbiw.net> <CALaySJKzxo=oHLcDxT=RbrwMK=pTSh6vxY-VvLZ0C5wf+T-DQQ@mail.gmail.com> <5027D67B.2030409@dcrocker.net> <5027ED27.2040403@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Aug 2012 23:11:07 -0000

At 10:51 12-08-2012, Stewart Bryant wrote:
>If I interpret what you seem to be saying, it is that you care
>more for the micro-observance of IETF protocol, than
>taking steps to avoid Internet governance being
>transferred by government decree to a secretive
>agency of the UN that runs by government majority.

Several hours ago the IAB approved collaboration guidelines with "a 
secretive agency of the UN which is run by government majority".  The 
US has already stated that it "will not support proposals that would 
increase the exercise of control over Internet governance or content" 
( http://www.state.gov/e/eb/rls/othr/telecom/196031.htm ).

Internet governance is somewhat like political prostitution ( 
http://political-prostitution.com/ ).  If the governments of the 
world want to fight about that for the benefit of humanity, it is 
their choice.  I don't see why the IETF has to get into a fight about 
Internet governance.  It is ok if the IETF Chair wants an affirmation 
supported by various SDOs to thrust under the nose of delegates in 
November.  I understand that in some venues the only way to be heard 
is to make pompous speeches.

At 14:49 12-08-2012, Carsten Bormann wrote:
>I do believe the process question is an absolutely useful one.  We 
>should have a process that is able to handle multilateral activities 
>that include the IETF, with an element of negotiation, even 
>compromise, and so on.  This is a case where leadership is actually 
>required, and I don't think that process is an established one at 
>all.  We do know how to

The IAB Charter allows it to handle multilateral activities.

>If the process question was actually raised to derail the signing of 
>the current document, my reaction would be quite similar to Stewart's.

A person expects people to behave as sheep if the person mentions 
"collective empowerment" and doesn't want anyone to raise 
questions.  The person could also smile, nod and ignore the questions 
as the sheep won't pursue the matter.

If a person wanted to derail the signing of the current document the 
person would only delay the outcome by about a month.  It would be 
somewhat entertaining as the IAB has already taken a vote on the 
matter.  Please do not ask me to elaborate on how this might be done.

>As I said before, sometimes you have to act.

And play god. :-)

The following are selected quotes:

   "Cooperation. Respectful cooperation between standards organizations,
    whereby each respects the autonomy, integrity, processes, and intellectual
    property rules of the others."

The IETF should not be disrespectful by making any comments about the 
ITU which may have a negative connotation. :-)

   "Collective empowerment. Commitment by affirming standards organizations
    and their participants to collective empowerment by striving for standards
    that:"

The affirmation is not a commitment taken by IETF participants.  The 
IESG knows the path to take if it would like to get such a commitment.

Regards,
-sm  


From mfberny@gmail.com  Sun Aug 12 17:04:02 2012
Return-Path: <mfberny@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F15F21F86A2 for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 17:04: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, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ByvD+5LWq8py for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 17:04:01 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id A761A21F85F7 for <ietf@ietf.org>; Sun, 12 Aug 2012 17:04:01 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so3293169vcb.31 for <ietf@ietf.org>; Sun, 12 Aug 2012 17:04:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bi31QEoO4gAe7NkBzqkki9YkVuPTdOuE9Y+XSIC8RAY=; b=gnGTniIe23EC0Rn3D5xXh82zmYDtkKs6LAgAlcXFRlScqazEP44stLCFod2ZLI20Fe YPpWN/dKBRqcg0/4HG8zI9oNSQYJ2CIvnqfFWVaF/U7y/6zgCpVm+XUuFRBMFaF4PSEJ S9YtFf6SO7NhVDjOo/gje/HN339/HDqTEQp5lPflpgYwUqOkDOh/FI6mm+u2jWhEstzn D/wKJCHUgeV2fM2efptWm5Zs1WrRySCAOjS8BwsSpjOcL4wkLqVt9Yl/CsrFWpY1CcDw MZ+UJvdbgh7VY2jryUq+PbTjI8QQRkB0Rc1Q9mKEGip6U7QCBegcW4ZvZ3rtnXhBU0Ky Ebhg==
MIME-Version: 1.0
Received: by 10.52.30.168 with SMTP id t8mr904500vdh.38.1344816241052; Sun, 12 Aug 2012 17:04:01 -0700 (PDT)
Received: by 10.58.253.136 with HTTP; Sun, 12 Aug 2012 17:04:00 -0700 (PDT)
In-Reply-To: <10664.1344805602@obiwan.sandelman.ca>
References: <CAGzJzZ5GFPsoasfLB8hGmVB5DWGKED2acs7CwfSWbp_JFXu7Mg@mail.gmail.com> <5027F89A.4080006@gmail.com> <CAGzJzZ44aHyq1Sq8m52dodZ5fxfyMfROFo+GvWtWB2Dd9VSnQg@mail.gmail.com> <10664.1344805602@obiwan.sandelman.ca>
Date: Mon, 13 Aug 2012 02:04:00 +0200
Message-ID: <CAL-6tfXGTJUn=nQWTp03e3TNR86DzAJ2wp4ge0=-Ma8Ge-LsZg@mail.gmail.com>
Subject: Re: Modern Global Standards Paradigm
From: Marie-France Berny <mfberny@gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=bcaec51d27fa560d2a04c71a6eb9
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 00:04:02 -0000

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

2012/8/12 Michael Richardson <mcr+ietf@sandelman.ca>

>
> >>>>> "jean-michel" == jean-michel bernier de portzamparc <
> jmabdp@gmail.com> writes:
>     jean-michel> Dear Mr. Carpenter,
>     jean-michel> I do not understand this.
>     jean-michel> Would you want to examplify the ITU supposed good manners?
>     jean-michel> I am lost.
>
> So am I.
>

I am too. So, we both are.


> You process to represent open source developers.
>

?

Yes, many of us are concerned about USG control over ICANN, but
> I don't know where/how you pretend to represent "us", when we can't even
> agree on much at all on a good day.
>

Quite true: you say we pretend something we never pretended.
Now, you welcome to help us.
Cheers.
MF Berny

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

<div class=3D"gmail_quote">2012/8/12 Michael Richardson <span dir=3D"ltr">&=
lt;<a href=3D"mailto:mcr+ietf@sandelman.ca" target=3D"_blank">mcr+ietf@sand=
elman.ca</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
&gt;&gt;&gt;&gt;&gt; &quot;jean-michel&quot; =3D=3D jean-michel bernier de =
portzamparc &lt;<a href=3D"mailto:jmabdp@gmail.com">jmabdp@gmail.com</a>&gt=
; writes:<br>
=A0 =A0 jean-michel&gt; Dear Mr. Carpenter,<br>
=A0 =A0 jean-michel&gt; I do not understand this.<br>
=A0 =A0 jean-michel&gt; Would you want to examplify the ITU supposed good m=
anners?<br>
=A0 =A0 jean-michel&gt; I am lost.<br>
<br>
So am I.<br></blockquote><div><br>I am too. So, we both are.<br>=A0<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">
You process to represent open source developers.<br></blockquote><div><br>?=
<br><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
Yes, many of us are concerned about USG control over ICANN, but<br>
I don&#39;t know where/how you pretend to represent &quot;us&quot;, when we=
 can&#39;t even<br>
agree on much at all on a good day.<br></blockquote><div><br>Quite true: yo=
u say we pretend something we never pretended.<br>Now, you welcome to help =
us. <br>Cheers.<br>MF Berny<br><br><br></div></div>

--bcaec51d27fa560d2a04c71a6eb9--

From ajs@anvilwalrusden.com  Sun Aug 12 19:58:49 2012
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 3033F21F86A4 for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 19:58:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id odfGmOhLrb21 for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 19:58:48 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id BC01521F869E for <ietf@ietf.org>; Sun, 12 Aug 2012 19:58:48 -0700 (PDT)
Received: from mail.yitter.info (ip-64-134-66-185.public.wayport.net [64.134.66.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 998938A031 for <ietf@ietf.org>; Mon, 13 Aug 2012 02:58:46 +0000 (UTC)
Date: Sun, 12 Aug 2012 22:58:49 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Please, not more process (was: [IAB] Last Call: Modern Global Standards Paradigm)
Message-ID: <20120813025849.GA93948@mail.yitter.info>
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com> <50266F05.5050601@dcrocker.net> <1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org> <50267826.70307@bbiw.net> <CAC4RtVARm1fXvHR4dv9Jh0HttW+ORhRx36kwF54RRjc4aOh1AQ@mail.gmail.com> <5027D0B2.80306@bbiw.net> <CALaySJKzxo=oHLcDxT=RbrwMK=pTSh6vxY-VvLZ0C5wf+T-DQQ@mail.gmail.com> <5027D67B.2030409@dcrocker.net> <5027ED27.2040403@cisco.com> <DDFE0F39-380E-49DB-B0E5-451AB659AFAE@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <DDFE0F39-380E-49DB-B0E5-451AB659AFAE@tzi.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 02:58:49 -0000

On Sun, Aug 12, 2012 at 11:49:35PM +0200, Carsten Bormann wrote:
> 
> I do believe the process question is an absolutely useful one.  We
> should have a process that is able to handle multilateral activities
> that include the IETF

Why is it useful?  

As far as I know, this is the very first time we have had a problem
shaped exactly like this.  There have been other issues with different
sets of parties on other multilateral activities, but they appear to
have demanded a different kind of response, since that's what they
got.  It seems to me that we could better spend our energies working
on standards (using our actual standards development model rather than
the abstract approximation in the affirmation!) than in working up
rules to govern a circumstance that, we should all hope, will not
arise again in our lifetimes.  Not every single bit of human
interaction requires a process rule.  Some things just require
judgement, and I encourage "the leadership" -- people we put (via the
nomcom) into the position to exercise such judgement -- to do so.
 
Best,

A

PS: I have on purpose not commented about the proposed statement,
because the request was for strong objections, and I have none.

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From mstjohns@comcast.net  Sun Aug 12 20:03:20 2012
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1F6721F869E for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 20:03:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.359
X-Spam-Level: 
X-Spam-Status: No, score=-101.359 tagged_above=-999 required=5 tests=[AWL=-0.157, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cSU-RYvsewk9 for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 20:03:19 -0700 (PDT)
Received: from qmta12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [76.96.27.227]) by ietfa.amsl.com (Postfix) with ESMTP id D29F321F86AA for <ietf@ietf.org>; Sun, 12 Aug 2012 20:03:19 -0700 (PDT)
Received: from omta08.emeryville.ca.mail.comcast.net ([76.96.30.12]) by qmta12.emeryville.ca.mail.comcast.net with comcast id m0BS1j00D0FhH24AC33KGW; Mon, 13 Aug 2012 03:03:19 +0000
Received: from Mike-PC3.comcast.net ([68.83.222.237]) by omta08.emeryville.ca.mail.comcast.net with comcast id m33H1j00Q57vnMg8U33JvJ; Mon, 13 Aug 2012 03:03:19 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sun, 12 Aug 2012 23:03:16 -0400
To: Glen Zorn <glenzorn@gmail.com>,ietf@ietf.org
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: Re: [IAB] Last Call: Modern Global Standards Paradigm
In-Reply-To: <1344737164.8891.29.camel@gwz-laptop>
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com> <50266F05.5050601@dcrocker.net> <1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org> <1344737164.8891.29.camel@gwz-laptop>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_26467160==.ALT"
Message-Id: <20120813030319.D29F321F86AA@ietfa.amsl.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 03:03:20 -0000

--=====================_26467160==.ALT
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Glen and others -=20

I wanted to go back and comment on the assertion that Glen made that the=
 IETF and IAB chairs do not "'represent' [him] or any one other than=
 themselves".  I believe he is correct with respect to himself, and=
 incorrect with respect to the IETF.

I agree the IETF is not a "representative democracy", the IESG and IAB (and=
 not the IETF) are probably best described as electoral meritocracies.  We=
 randomly select "electors" from a "qualified" pool which self-selects=
 mostly from the set of all participants which in turn selects the IESG and=
 the IAB from that set of all participants.  I'm pretty sure that Carsten=
 was using "elect" to describe that process.

While the IESG and IAB may not speak for the IETF participants, they de=
 facto and de jure do speak for the IETF.  It's a subtle difference, but an=
 important one.  [CF the various RFCs detailing the responsibilities and=
 duties of the IESG, IAB and their respective chairs, the RFCs detailing the=
 standards process, and the various liaison's that have been arranged over=
 the years.]

I've noted over the years that the constituency of IETF participants tends=
 to have bouts with BSDS - back seat driver syndrome, and this is mostly not=
 helpful.  We (referring to the broad set of IETF participants going back=
 25+ years) have over time evolved and agreed upon various ways of moving=
 forward for generally accepted values of "forward".  Those ways include=
 having granted the IESG the power to set the standards agenda, the IAB to=
 negotiate and approve liaison agreements with standards bodies, the IESG to=
 ultimately approve the standards, and the IESG, IETF Chair and IAB chair to=
 declare a perception of consensus. =20


We (the participants) have reserved to ourselves the rights jointly and=
 severally to comment on all of the above, to be heard on even items=
 delegated to the IESG and IAB and at times to carp and cavil on every=
 single point of order.  Some of this is good for the process.  But we go=
 too far way too often. =20

In this case, the IAB, IESG and their respective chairs are doing the jobs=
 we've asked them to do.  Russ, correctly I believe, asked for objections to=
 the issuance of such statement, he didn't ask for consensus.  I also=
 believe it would have been well within the current job description of the=
 IAB and IETF Chairs to just go ahead and sign the thing.

I think it comes down to this:

If you (an IETF participant) have an objection to the statement, make it=
 here.

If you have an objection to the process in general then - form your=
 objections, write an ID, and socialize what you want changed.   If=
 consensus shows you correct, it will apply down the line.

If you have a belief that the process has been violated, it's appropriate to=
 make that point, but give details rather than vague intimations.

If you have an objection related to the members of the IESG or IAB=
 performance, make them to the Nomcom or offer yourself as a candidate if=
 you think you can do better or both.

We've - collectively, through process established over many years - selected=
 a team of our colleagues to perform a circumscribed set of tasks. =
 Efficiency suggests we should mostly stand back and let them get on with=
 it.

Mike



At 10:06 PM 8/11/2012, Glen Zorn wrote:
>On Sat, 2012-08-11 at 17:13 +0200, Carsten Bormann wrote:=20
>>
>>
>>On Aug 11, 2012, at 16:41, Dave Crocker=
 <<mailto:dhc@dcrocker.net>dhc@dcrocker.net> wrote:
>>
>>> consensus-oriented process
>>
>>Sometimes, though, you have to act.
>>
>>While a consensus-oriented process*) document could certainly be used to=
 improve (or deteriorate) the document by a couple more epsilons, I agree=
 with Randy Bush: Signing it now is a no-brainer.
>>
>>Gr=FC=DFe, Carsten
>>
>>*) Well there was a call for comments, and it already supplied the first=
 such set of epsilons. =20
>>That may have to do when time is of the essence.
>>
>>(That's also what you choose your leadership for. =20
>>If we don't like the outcome, we can always decide not to re-elect Russ=
 :-)
>
>Did the IETF morph into a representative democracy while I was sleeping? =
 Last time I checked, Russ was the chair of a committee of managers, chosen=
 by a random selection of proles who may or may not have taken the opinions=
 of others into account in that selection.  He was not "elected", nor does=
 he "speak for the IETF"; ditto for Bernard.  If they wish to sign this=
 statement (with which I, by and large, agree, BTW), that's fine.  If they=
 wish to list all their titles (IETF-bestowed & otherwise), degrees, etc.,=
 that's fine, too, but not if the intent is to imply that they somehow=
 "represent" me or any one other than themselves.  If support by IETF=
 members at-large is to be signified, then an online petition of some sort=
 would be a much better idea & much less deceptive.
>
>>
>>
>>


--=====================_26467160==.ALT
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<body>
Glen and others - <br><br>
I wanted to go back and comment on the assertion that Glen made that the
IETF and IAB chairs do not &quot;'represent' [him] or any one other than
themselves&quot;.&nbsp; I believe he is correct with respect to himself,
and incorrect with respect to the IETF.<br><br>
I agree the IETF is not a &quot;representative democracy&quot;, the IESG
and IAB (and not the IETF) are probably best described as electoral
meritocracies.&nbsp; We randomly select &quot;electors&quot; from a
&quot;qualified&quot; pool which self-selects mostly from the set of all
participants which in turn selects the IESG and the IAB from that set of
all participants.&nbsp; I'm pretty sure that Carsten was using
&quot;elect&quot; to describe that process.<br><br>
While the IESG and IAB may not speak for the IETF participants, they de
facto and de jure do speak for the IETF.&nbsp; It's a subtle difference,
but an important one.&nbsp; [CF the various RFCs detailing the
responsibilities and duties of the IESG, IAB and their respective chairs,
the RFCs detailing the standards process, and the various liaison's that
have been arranged over the years.]<br><br>
I've noted over the years that the constituency of IETF participants
tends to have bouts with BSDS - back seat driver syndrome, and this is
mostly not helpful.&nbsp; We (referring to the broad set of IETF
participants going back 25+ years) have over time evolved and agreed upon
various ways of moving forward for generally accepted values of
&quot;forward&quot;.&nbsp; Those ways include having granted the IESG the
power to set the standards agenda, the IAB to negotiate and approve
liaison agreements with standards bodies, the IESG to ultimately approve
the standards, and the IESG, IETF Chair and IAB chair to declare a
perception of consensus.&nbsp; <br><br>
<br>
We (the participants) have reserved to ourselves the rights jointly and
severally to comment on all of the above, to be heard on even items
delegated to the IESG and IAB and at times to carp and cavil on every
single point of order.&nbsp; Some of this is good for the process.&nbsp;
But we go too far way too often.&nbsp; <br><br>
In this case, the IAB, IESG and their respective chairs are doing the
jobs we've asked them to do.&nbsp; Russ, correctly I believe, asked for
objections to the issuance of such statement, he didn't ask for
consensus.&nbsp; I also believe it would have been well within the
current job description of the IAB and IETF Chairs to just go ahead and
sign the thing.<br><br>
I think it comes down to this:<br><br>
If you (an IETF participant) have an objection to the statement, make it
here.<br><br>
If you have an objection to the process in general then - form your
objections, write an ID, and socialize what you want changed.&nbsp;&nbsp;
If consensus shows you correct, it will apply down the line.<br><br>
If you have a belief that the process has been violated, it's appropriate
to make that point, but give details rather than vague
intimations.<br><br>
If you have an objection related to the members of the IESG or IAB
performance, make them to the Nomcom or offer yourself as a candidate if
you think you can do better or both.<br><br>
We've - collectively, through process established over many years -
selected a team of our colleagues to perform a circumscribed set of
tasks.&nbsp; Efficiency suggests we should mostly stand back and let them
get on with it.<br><br>
Mike<br><br>
<br><br>
At 10:06 PM 8/11/2012, Glen Zorn wrote:<br>
<blockquote type=3Dcite class=3Dcite cite=3D"">On Sat, 2012-08-11 at 17:13
+0200, Carsten Bormann wrote: <br>
<blockquote type=3Dcite class=3Dcite cite=3D""><br>
<pre>
On Aug 11, 2012, at 16:41, Dave Crocker
&lt;<a href=3D"mailto:dhc@dcrocker.net">dhc@dcrocker.net</a>&gt; wrote:

&gt; consensus-oriented process

Sometimes, though, you have to act.

While a consensus-oriented process*) document could certainly be used to
improve (or deteriorate) the document by a couple more epsilons, I agree
with Randy Bush: Signing it now is a no-brainer.

Gr=FC=DFe, Carsten

*) Well there was a call for comments, and it already supplied the first
such set of epsilons.&nbsp;=20
That may have to do when time is of the essence.

(That's also what you choose your leadership for.&nbsp;=20
If we don't like the outcome, we can always decide not to re-elect Russ
:-)
</pre><font face=3D"Courier New, Courier"></font></blockquote><br>
Did the IETF morph into a representative democracy while I was
sleeping?&nbsp; Last time I checked, Russ was the chair of a committee of
managers, chosen by a random selection of proles who may or may not have
taken the opinions of others into account in that selection.&nbsp; He was
not &quot;elected&quot;, nor does he &quot;speak for the IETF&quot;;
ditto for Bernard.&nbsp; If they wish to sign this statement (with which
I, by and large, agree, BTW), that's fine.&nbsp; If they wish to list all
their titles (IETF-bestowed &amp; otherwise), degrees, etc., that's fine,
too, but not if the intent is to imply that they somehow
&quot;represent&quot; me or any one other than themselves.&nbsp; If
support by IETF members at-large is to be signified, then an online
petition of some sort would be a much better idea &amp; much less
deceptive.<br><br>
<blockquote type=3Dcite class=3Dcite cite=3D""><br>
<pre>

</pre><font face=3D"Courier New, Courier"></font></blockquote></blockquote>
</body>
<br>
</html>

--=====================_26467160==.ALT--


From cabo@tzi.org  Sun Aug 12 22:45:46 2012
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11EA821F853C for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 22:45:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.332
X-Spam-Level: 
X-Spam-Status: No, score=-106.332 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6LhPVwLnRCXL for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 22:45:45 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 25FD821F84D9 for <ietf@ietf.org>; Sun, 12 Aug 2012 22:45:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q7D5hX1q028376; Mon, 13 Aug 2012 07:43:33 +0200 (CEST)
Received: from [192.168.217.105] (p5489298A.dip.t-dialin.net [84.137.41.138]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 4A4E4BAF; Mon, 13 Aug 2012 07:43:33 +0200 (CEST)
Subject: Re: Please, not more process (was: [IAB] Last Call: Modern Global Standards Paradigm)
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20120813025849.GA93948@mail.yitter.info>
Date: Mon, 13 Aug 2012 07:43:31 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <428D7E1D-3641-4F94-BD3B-55D045C99AE2@tzi.org>
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com> <50266F05.5050601@dcrocker.net> <1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org> <50267826.70307@bbiw.net> <CAC4RtVARm1fXvHR4dv9Jh0HttW+ORhRx36kwF54RRjc4aOh1AQ@mail.gmail.com> <5027D0B2.80306@bbiw.net> <CALaySJKzxo=oHLcDxT=RbrwMK=pTSh6vxY-VvLZ0C5wf+T-DQQ@mail.gmail.com> <5027D67B.2030409@dcrocker.net> <5027ED27.2040403@cisco.com> <DDFE0F39-380E-49DB-B0E5-451AB659AFAE@tzi.org> <20120813025849.GA93948@mail.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1485)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 05:45:46 -0000

On Aug 13, 2012, at 04:58, Andrew Sullivan <ajs@anvilwalrusden.com> =
wrote:

> Why is it useful? =20

Because it elicits considered reactions like yours and Mike StJohns', =
and allows us to make explicit and affirm the (rough) consensus that we =
seem to share about the role and purview of our leadership.  (I'm not =
asking for another RFC, I'm just asking that we do consciously what we =
are doing, also so it may serve as a precedent.)

Gr=FC=DFe, Carsten

(This is likely my last message on this subject.)


From brian.e.carpenter@gmail.com  Sun Aug 12 23:50:33 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55B3111E80A5 for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 23:50:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.497
X-Spam-Level: 
X-Spam-Status: No, score=-101.497 tagged_above=-999 required=5 tests=[AWL=0.194, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3hvX9qyw7ZZi for <ietf@ietfa.amsl.com>; Sun, 12 Aug 2012 23:50:33 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id A488F11E8072 for <ietf@ietf.org>; Sun, 12 Aug 2012 23:50:32 -0700 (PDT)
Received: by wgbdr13 with SMTP id dr13so2060836wgb.13 for <ietf@ietf.org>; Sun, 12 Aug 2012 23:50:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=RQ3AmKo/Hk8uyWgfuO5ME8dWLKH0FIJYnqyqSpzzB3c=; b=YAq2+sYfbEfrgv18+uFIa7gWHQGc2JrHTN3xYI2dkyjeb93vTIGsUu9/FD+SRQVqGQ 8AOPVG1R5RbjlT+Yd/lTOZuk/THq+LRlwuDNJbI9tSLcuN8dIpbp/hicIoRi4wEJvqKQ ZZ2w/06aQsRsNw4xiniUmoq73dwkpVXVF98sdkW2nfh42iCYbK/8waOy3H1RdrTb2U+8 U+ITbB3frekyDprsCwdrsSrLxHaOcUqulnD1MhW2fKO8UvpuQTCdMsJL6bqgMWr78O21 f03k49ZjisUTA7z5a90X9y7gRM59L39Dz0ekyIyOJVnukww/gwvJhO/zXIWKxjOCKNbo Q51g==
Received: by 10.216.232.104 with SMTP id m82mr5881543weq.15.1344840631731; Sun, 12 Aug 2012 23:50:31 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-119.as13285.net. [2.102.216.119]) by mx.google.com with ESMTPS id k2sm21613980wiz.7.2012.08.12.23.50.30 (version=SSLv3 cipher=OTHER); Sun, 12 Aug 2012 23:50:30 -0700 (PDT)
Message-ID: <5028A3B0.8030303@gmail.com>
Date: Mon, 13 Aug 2012 07:50:24 +0100
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: Michael StJohns <mstjohns@comcast.net>
Subject: Re: [IAB] Last Call: Modern Global Standards Paradigm
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com>	<50266F05.5050601@dcrocker.net>	<1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org>	<1344737164.8891.29.camel@gwz-laptop> <20120813030319.D29F321F86AA@ietfa.amsl.com>
In-Reply-To: <20120813030319.D29F321F86AA@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 06:50:33 -0000

On 13/08/2012 04:03, Michael StJohns wrote:
...
> We've - collectively, through process established over many years - selected a team of our colleagues to perform a circumscribed set of tasks.  Efficiency suggests we should mostly stand back and let them get on with it.

At the risk of being at the top of the next "Narten" list, I can't help adding
that in the matter of liaison with other SDOs, our process formally states
that the IAB "acts as representative of the interests of the IETF and the
Internet Society". (See the same clause of BCP 39 that I cited yesterday.)

   Brian

From aalain@afribone.trstech.net  Mon Aug 13 01:46:34 2012
Return-Path: <aalain@afribone.trstech.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4641821F86C8; Mon, 13 Aug 2012 01:46:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.02
X-Spam-Level: 
X-Spam-Status: No, score=-0.02 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q1okVymJ7xLl; Mon, 13 Aug 2012 01:46:33 -0700 (PDT)
Received: from afribone.trstech.net (afribone.trstech.net [196.200.57.137]) by ietfa.amsl.com (Postfix) with ESMTP id 97D2421F8652; Mon, 13 Aug 2012 01:46:33 -0700 (PDT)
Received: from [41.207.163.5] (helo=[192.168.3.155]) by afribone.trstech.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <aalain@afribone.trstech.net>) id 1T0qI8-0001he-PM; Mon, 13 Aug 2012 08:46:30 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: ALAIN AINA <aalain@trstech.net>
In-Reply-To: <8393C34B-3BD4-4453-A315-74D93E971260@gmail.com>
Date: Mon, 13 Aug 2012 12:46:15 +0400
Content-Transfer-Encoding: 7bit
Message-Id: <95FB8F65-4B33-4681-9D18-F1D6D7DF180A@trstech.net>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <8393C34B-3BD4-4453-A315-74D93E971260@gmail.com>
To: IETF <ietf@ietf.org>, IAB <iab@iab.org>
X-Mailer: Apple Mail (2.1084)
Sender: aalain@afribone.trstech.net
X-SA-Exim-Connect-IP: 41.207.163.5
X-SA-Exim-Mail-From: aalain@afribone.trstech.net
Subject: Re: Last Call: Modern Global Standards Paradigm
X-SA-Exim-Version: 4.2.1 (built Thu, 21 Oct 2010 18:52:38 +0000)
X-SA-Exim-Scanned: Yes (on afribone.trstech.net)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 08:46:34 -0000

On Aug 11, 2012, at 2:55 AM, Bob Hinden wrote:

> I support the IETF and IAB chairs signing document.

+1

--Alain
> 
> Bob
> 
> On Aug 10, 2012, at 8:19 AM, IETF Chair wrote:
> 
>> 
>> The IETF Chair and the IAB Chair intend to sign the Affirmation
>> of the Modern Global Standards Paradigm, which can be found
>> here:
>> 
>> http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf
>> 
>> An earlier version was discussed in plenary, and the IAB Chair called
>> for comments on the IETF mail list.  This version includes changes
>> that address those comments.
>> 
>> Th IETF 84 Administrative plenary minutes have been posted, so that
>> discussion can be reviewed if desired.  The minutes are here:
>> 
>> http://www.ietf.org/proceedings/84/minutes/minutes-84-iesg-opsplenary
>> 
>> On 8 August 2012, the IEEE Standards Association Board of Governors
>> approved this version of the document.  The approval process is
>> underway at the W3C as well.
>> 
>> The IETF Chair and the IAB Chair intend to sign the Affirmation in the
>> next few weeks. Please send strong objections to the iab@iab.org
>> and the ietf@ietf.org mailing lists by 2012-08-24.
>> 
>> Thank you,
>> Russ Housley
>> IETF Chair
> 


From vesely@tana.it  Mon Aug 13 02:11:39 2012
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0F2D21F86B0; Mon, 13 Aug 2012 02:11:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.602
X-Spam-Level: 
X-Spam-Status: No, score=-4.602 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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ibxIH5I3Bl6W; Mon, 13 Aug 2012 02:11:39 -0700 (PDT)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id BC19521F86BD; Mon, 13 Aug 2012 02:11:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1344849096; bh=MEn5QbKeJM4XlYabG3hXpw4GwEZr0tyiPwskmUMzDFE=; l=1306; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=dB079ZnL5FfxVKDACxXI9iPv+dhb05Jead0ALpV3e2xfDjuaqAlY1qtZq1I2ovsaN l0KblhzXGO4c6oSaf0O3TzP4ppdtfYrg0nThIyxFnVSvzp0LEhGWHFnHB8oqyul+Od Jya8sFYbPn8ek7iWihqaGoxgKrtUZ2ZDdz1hmwbU=
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; Mon, 13 Aug 2012 11:11:36 +0200 id 00000000005DC033.000000005028C4C8.00000A0A
Message-ID: <5028C4C8.40508@tana.it>
Date: Mon, 13 Aug 2012 11:11:36 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: "ietf" <ietf@ietf.org>, internet users contributing group <iucg@ietf.org>
Subject: Re: [iucg] Last Call: Modern Global Standards Paradigm
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <CAMm+Lwio8=EyW-=LZE8BA4=6N=H4f7a1Nycg25LxB920ceZ6JA@mail.gmail.com> <1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.com> <276B7D303A96E840D2F95107@JcK-HP8200.jck.com> <CAMm+LwjL=tnYrtmHkV+=+VeOCo+1PjAu+pW0LnUyHYhVX_pPZA@mail.gmail.com> <C01C22690CE178AF8C2E52F7@JcK-HP8200.jck.com> <20120813012310.9F01A21F861E@ietfa.amsl.com>
In-Reply-To: <20120813012310.9F01A21F861E@ietfa.amsl.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: Mon, 13 Aug 2012 09:11:39 -0000

On Mon 13/Aug/2012 03:22:52 +0200 JFC Morfin wrote:
> At 19:16 11/08/2012, John C Klensin wrote:
> 
>> On the other hand, irrational behavior would be nothing new in this
>> area so I can't disagree with the possibility.
> 
> Correct. This is why, if I understand the motivation, I strongly
> disagree with the wording of the document and your evaluation of the
> situation. The US/IETF rationale being used is disagreed by non-US
> related industries and most probably by every Government (including
> the USG) because it looks like SDOs wanted to decide alone, based upon
> market results, about the standards for the people they represent.

FWIW, I'd like to recall that several governments endorse IETF
protocols by establishing Internet based procedures for official
communications with the relevant PA, possibly giving them legal
standing.  Francesco Gennai presented a brief review of such
procedures[*] at the APPSAWG meeting in Paris.  At the time, John
Klensin suggested that, while a more in-depth review of existing
practices would be appreciated, the ITU is a more suitable body for
the standardization of a unified, compatible protocol for certified
email, because of those governmental involvements.

[*] http://www.ietf.org/proceedings/83/slides/slides-83-appsawg-1.pdf


From mohta@necom830.hpcl.titech.ac.jp  Mon Aug 13 02:46:09 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55B0321F86D5 for <ietf@ietfa.amsl.com>; Mon, 13 Aug 2012 02:46:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.049
X-Spam-Level: 
X-Spam-Status: No, score=-0.049 tagged_above=-999 required=5 tests=[AWL=0.041,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0xOB0CezJDw5 for <ietf@ietfa.amsl.com>; Mon, 13 Aug 2012 02:46:08 -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 7E62421F8712 for <ietf@ietf.org>; Mon, 13 Aug 2012 02:46:08 -0700 (PDT)
Received: (qmail 1144 invoked from network); 13 Aug 2012 09:44:36 -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; 13 Aug 2012 09:44:36 -0000
Message-ID: <5028CCB9.5050503@necom830.hpcl.titech.ac.jp>
Date: Mon, 13 Aug 2012 18:45:29 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FE2715C.2090601@necom830.hpcl.titech.ac.jp> <4FF20DE7.2080208@isi.edu> <500654AB.7060500@necom830.hpcl.titech.ac.jp> <8F5CBE79-4540-4519-9F51-62B36686EE8C@isi.edu> <501C5C75.9040209@necom830.hpcl.titech.ac.jp> <501C6441.4000302@isi.edu> <5020C32A.4060907@necom830.hpcl.titech.ac.jp> <50215032.7090800@isi.edu> <5027767A.60601@necom830.hpcl.titech.ac.jp> <5027E8EE.8010109@isi.edu>
In-Reply-To: <5027E8EE.8010109@isi.edu>
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: Mon, 13 Aug 2012 09:46:09 -0000

Joe Touch wrote:

> Again, this doc is about updating the IPv4 ID specification in RFC791 -
> which has not yet been updated.

But, the way you update rfc791 requires updating rfc2460,
rfc2765 and their implementations, for which there is no
consensus.

That is, though your draft claims to "more closely reflect
current practice" and "more closely match IPv6", the way you
update rfc791 does not "reflect current practice" nor "match
IPv6".

As your draft states:

   it is clear that
   existing systems violate the current specification

and rfc2026 states:

   4.1.3  Internet Standard
   A specification for which significant implementation and successful
   operational experience has been obtained may be elevated to the
   Internet Standard level.

there is no point to insist on the ID uniqueness requirement of
rfc791 as a requirement of an Internet Standard.

> The IPv6-IPv4 translation that creates IPv4 IDs is currently
> non-compliant with RFC791 and does not override RFC791. This document's
> update might make that translation easier,

Wrong.

Insisting on rfc791 makes the translation a lot harder than
just "closely reflect current practice" to loosen uniqueness
request of rfc791, which is what almost all (if not all) the
IPv4 and IPv6 implementations today are doing.

> If you disagree with that conclusion, please contact the INTAREA WG
> chairs directly.

As we are in IETF last call stage, I can see no point you
insist on the original conclusion of the WG, which
overlooked the complication caused by 6->4 translation.

						Masataka Ohta

From touch@isi.edu  Mon Aug 13 02:59:16 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5EEC21F8569 for <ietf@ietfa.amsl.com>; Mon, 13 Aug 2012 02:59:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BN8dmj5j2rUH for <ietf@ietfa.amsl.com>; Mon, 13 Aug 2012 02:59:16 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 5353721F8541 for <ietf@ietf.org>; Mon, 13 Aug 2012 02:59:16 -0700 (PDT)
Received: from [10.0.0.56] ([193.184.126.114]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q7D9wSNH020059 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 13 Aug 2012 02:58:40 -0700 (PDT)
Message-ID: <5028CFC2.1060200@isi.edu>
Date: Mon, 13 Aug 2012 02:58:26 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FE2715C.2090601@necom830.hpcl.titech.ac.jp> <4FF20DE7.2080208@isi.edu> <500654AB.7060500@necom830.hpcl.titech.ac.jp> <8F5CBE79-4540-4519-9F51-62B36686EE8C@isi.edu> <501C5C75.9040209@necom830.hpcl.titech.ac.jp> <501C6441.4000302@isi.edu> <5020C32A.4060907@necom830.hpcl.titech.ac.jp> <50215032.7090800@isi.edu> <5027767A.60601@necom830.hpcl.titech.ac.jp> <5027E8EE.8010109@isi.edu> <5028CCB9.5050503@necom830.hpcl.titech.ac.jp>
In-Reply-To: <5028CCB9.5050503@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=ISO-2022-JP
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: Mon, 13 Aug 2012 09:59:16 -0000

On 8/13/2012 2:45 AM, Masataka Ohta wrote:
> Joe Touch wrote:
> 
>> Again, this doc is about updating the IPv4 ID specification in RFC791 -
>> which has not yet been updated.
> 
> But, the way you update rfc791 requires updating rfc2460,
> rfc2765 and their implementations, for which there is no
> consensus.

It certainly does not.

> That is, though your draft claims to "more closely reflect
> current practice" and "more closely match IPv6", the way you
> update rfc791 does not "reflect current practice" nor "match
> IPv6".

It does - it doesn't reflect the errors in IPv6-IPv4 translation, which
is not "IPv6".

Joe

From abdussalambaryun@gmail.com  Mon Aug 13 04:25:07 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43F2821F86F4 for <ietf@ietfa.amsl.com>; Mon, 13 Aug 2012 04:25:07 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W4Y0bu1dHthx for <ietf@ietfa.amsl.com>; Mon, 13 Aug 2012 04:25:06 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7DEB221F86F3 for <ietf@ietf.org>; Mon, 13 Aug 2012 04:25:06 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so3713089vcb.31 for <ietf@ietf.org>; Mon, 13 Aug 2012 04:25:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=GxYFdpk2e2OpwAbv0k9N6cUfWXDuv2WmuTqmcsvkGXY=; b=PtULrVliFOCgNnsy6U3lp87lYQgPXT6Z03R+3+SdZP4ROIqocCP1mpgQNz5nKPnC3r 7C2nSJtj8k8RrmccdrA4rWY/k0YFz0YydDj5Kjthoxb5GDYJ8qh0P20p18/YtHIh+Zxe uODv6mvH44aO6kR2wzBhTlnwNvrFVr5n2Gk0ZMBbZA9/eel8KILW44wTlU0BYox7k+Xa 40JMFQjFs7NYYYREDuJvRYrrQnxJxe4KSWefds8gezTPJz9Zw1iU6tklfezI4ZEkGmCJ 9aCCBevIdg1xH7sgkvu/qBVUOvqb2E90t+oV0q3bN7qM1YNdPZRve++xrftMLCXuoVbi WzQQ==
MIME-Version: 1.0
Received: by 10.58.12.231 with SMTP id b7mr9203060vec.28.1344857105864; Mon, 13 Aug 2012 04:25:05 -0700 (PDT)
Received: by 10.220.62.77 with HTTP; Mon, 13 Aug 2012 04:25:05 -0700 (PDT)
In-Reply-To: <CADnDZ8-nezaNodqvmdB-HtMPqxL_2kuVng9NTqKhHkrDA2XXhw@mail.gmail.com>
References: <CADnDZ8-nezaNodqvmdB-HtMPqxL_2kuVng9NTqKhHkrDA2XXhw@mail.gmail.com>
Date: Mon, 13 Aug 2012 13:25:05 +0200
Message-ID: <CADnDZ8_k4qyCYVU1PmuWKOnN6GGY6OVwvAYKGeC_kC92CEwM_A@mail.gmail.com>
Subject: Re: [IAB] Last Call: Modern Global Standards Paradigm
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: dcrocker@bbiw.net
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 11:25:07 -0000

Hi Dave,

I agree that procedure of ietf processes should be respected and
followed by all, and/or community should understand such difference in
process before asked its opinion. I hope your comments will be
considered by IETF and IAB in the future.

thanking you for your comments,

AB
 --------------------------------------------------

 From: Dave Crocker <dcrocker at bbiw.net>
 To: Barry Leiba <barryleiba at computer.org>
 Cc: IAB <iab at iab.org>, IETF <ietf at ietf.org>
 Date: Sun, 12 Aug 2012 08:50:10 -0700

> Two weeks is normal process for spontaneous consensus calls?
>
> When did the community approve that change in process?
>
> No he didn't:
>
>      "Please send strong objections..."
>
> This asserts a forceful bias against general comments and criticisms by
> establishing a very high threshhold for relevance.  While no, no one is
> prevented from other kinds of postings, the bias is nonetheless
> established.
>
> Note that he didn't ask for support, although explicit support
> statements are exactly what is required for IETF consensus calls, absent
>
> a history to justify the kind of "default yes" assumption made in the
> announcement. We don't have any such documented history for this
> effort.
> Would any of us guess that the community would support the document?
> Sure.  But guessing isn't the point.
>
>
> That folks have chosen to ignore the stricture specified in the
> announcement and to post public support shows how deeply ingrained our
> model is. And, yeah, enough such postings overwhelm problems with the
> last call wording...
>
> d/
>
> --
>  Dave Crocker
>  Brandenburg InternetWorking
>  bbiw.net
>

From john-ietf@jck.com  Mon Aug 13 07:50:51 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00D4B21F853F; Mon, 13 Aug 2012 07:50:51 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C5XOIXWouyXx; Mon, 13 Aug 2012 07:50:50 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 1D1BE21F846E; Mon, 13 Aug 2012 07:50:39 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1T0vsS-000Eju-Fj; Mon, 13 Aug 2012 10:44:20 -0400
Date: Mon, 13 Aug 2012 10:50:25 -0400
From: John C Klensin <john-ietf@jck.com>
To: Alessandro Vesely <vesely@tana.it>
Subject: Re: [iucg] Last Call: Modern Global Standards Paradigm
Message-ID: <F2E0F8B862341F3DC407A2DA@JcK-HP8200.jck.com>
In-Reply-To: <5028C4C8.40508@tana.it>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <CAMm+Lwio8=EyW-=LZE8BA4=6N=H4f7a1Nycg25LxB920ceZ6JA@mail.gmail.com> <1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.com> <276B7D303A96E840D2F95107@JcK-HP8200.jck.com> <CAMm+LwjL=tnYrtmHkV+=+VeOCo+1PjAu+pW0LnUyHYhVX_pPZA@mail.gmail.com> <C01C22690CE178AF8C2E52F7@JcK-HP8200.jck.com> <20120813012310.9F01A21F861E@ietfa.amsl.com> <5028C4C8.40508@tana.it>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf <ietf@ietf.org>, internet users contributing group <iucg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 14:50:51 -0000

--On Monday, August 13, 2012 11:11 +0200 Alessandro Vesely
<vesely@tana.it> wrote:

>...
> FWIW, I'd like to recall that several governments endorse IETF
> protocols by establishing Internet based procedures for
> official communications with the relevant PA, possibly giving
> them legal standing.  Francesco Gennai presented a brief
> review of such procedures[*] at the APPSAWG meeting in Paris.
> At the time, John Klensin suggested that, while a more
> in-depth review of existing practices would be appreciated,
> the ITU is a more suitable body for the standardization of a
> unified, compatible protocol for certified email, because of
> those governmental involvements.
> 
> [*]
>
http://www.ietf.org/proceedings/83/slides/slides-83-appsawg-1.pdf

Alessandro,

Please be a little careful about context, as your sequence of
comments above could easily be misleading.  

For the very specific case of email certified by third parties,
especially where there is a requirement for worldwide
recognition (the topic of the talk and slides you cited), the
biggest problem has, historically, been an administrative and
policy one, not a technical standards issue.  We know how to
digitally sign email in several different ways -- there is
actually no shortage of standards.   While additional standards
are certainly possible, more options in the absence of
compelling need almost always reduces practical
interoperability.  Perhaps the key question in the certified
mail matter is who does the certifying and why anyone else
should pay attention.  The thing that makes that question
complicated was famously described by Jeff Schiller (I believe
while he was still IETF Security AD) when he suggested that
someone would need to be insane to issue general-purpose
certificates that actually certified identity unless they were
an entity able to invoke sovereign immunity, i.e., a government.

For certified email (or certified postal mail), your ability to
rely on the certification in, e.g., legal matters ultimately
depends on your government being willing to say something to you
like "if you rely on this in the following ways, we will protect
you from bad consequences if it wasn't reliable or accurate".
If you want the same relationship with "foreign" mail, you still
have to rely on your government's assertions since a foreign
government can't do a thing for you if you get into trouble.
That, in turn, requires treaties or some sort of bilateral
agreements between the governments (for postal mail, some of
that is built into the postal treaties).  

International organizations, particularly UN-based ones, can
serve an important role in arranging such agreements and
possibly even in being the repository organization for the
treaties.  In the particular case of certified email, the ITU
could reasonably play that role (although it seems to me that a
very strong case could be made for having the UPU do it instead
by building on existing foundations).

But that has nothing to do with the development of technical
protocol standards.  Historical experience with development of
technical standards by governmental/legislative bodies that then
try to mandate their use has been almost universally poor and
has often included ludicrous results.

A similar example arises with the spam problem.  There are many
technical approaches to protecting the end user from spam
(especially malicious spam) and for facilitating the efforts of
mail delivery service providers and devices to apply those
protective mechanisms.  Some of them justify technical standards
that should be worked out in open forums that make their
decisions on open and technical bases.  But, if one wants to
prevent spam from imposing costs on intended recipients or third
parties, that becomes largely a law-making and law enforcement
problem, not a technical one.  If countries decide that they
want to prevent spam from being sent, or to punish the senders,
a certain amount of international cooperation (bilateral or
multilaterial) is obviously going to be necessary.   As with the
UPU and email certification, there might be better agencies or
forums for discussion than the ITU or there might not.  But it
isn't a technical protocol problem that the IETF is going to be
able to solve or should even try to address, at least without a
clear and actionable problem statement from those bodies.

I do believe that the ITU can, and should, serve a useful role
in the modern world.  The discussion above (and some of the work
of the Development and Radio Sectors) are good illustrations.
But those cases have, as far as I can tell, nothing to do with
the proposed statement, which is about the development and
deployment of technical protocol standards.

regards,
    john


From ron.even.tlv@gmail.com  Mon Aug 13 13:08:40 2012
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45DE621F84FD; Mon, 13 Aug 2012 13:08:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zXcpVYg3Oihw; Mon, 13 Aug 2012 13:08:39 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6085221F85ED; Mon, 13 Aug 2012 13:08:38 -0700 (PDT)
Received: by wgbdr13 with SMTP id dr13so2533964wgb.13 for <multiple recipients>; Mon, 13 Aug 2012 13:08:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=3RJBrl7Qzeo2Mn2R+73CZF6OD5IR6lHkUNtmkjIRI4I=; b=IKh02IfSRQaO/xSRa/hbIPpm6o7g0GiM10HJ6b/W+j67VAEXXj9BKtFUZHWkOCRbQH k/Oqm0UHzM7G7rQwuhL8wTjqwx0bnUMBhOlAVue/YGObMIwWPELKzYcBJe47MlgI2wMC PIHNABdlqRsuCZaP/Gj1b/nPhS7fRc3iuhJNiG9Ikw8YJbCOn1upm1ExBlX/b/cCumtR /8jPSxCQ5E8x7i9lI+6B+Rlfbvlt90QEIyRF4zvMbgvBE9HjY2uI3b1AGr7oVECHlLSN lSe5FCwaSXben2B00HB/JNfTZJMNIgpTC3CZSJznolS6YnXP5p9D66I27tlFJE7OjIyr Op4w==
Received: by 10.180.82.39 with SMTP id f7mr21221132wiy.2.1344888517387; Mon, 13 Aug 2012 13:08:37 -0700 (PDT)
Received: from RoniE (bzq-79-182-232-234.red.bezeqint.net. [79.182.232.234]) by mx.google.com with ESMTPS id k2sm26493072wiz.7.2012.08.13.13.08.34 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 13 Aug 2012 13:08:35 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05
Date: Mon, 13 Aug 2012 23:07:24 +0200
Message-ID: <002101cd7997$a5204330$ef60c990$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0022_01CD79A8.68A9FD90"
X-Mailer: Microsoft Outlook 14.0
Thread-index: Ac15l6K82vd14GSLS+SGruU3C7QWJA==
Content-language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 20:08:40 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0022_01CD79A8.68A9FD90
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-ccamp-rfc5787bis-05.

Reviewer: Roni Even

Review Date:2012-8-12

IETF LC End Date: 2012-8-17

IESG Telechat date:

 

Summary: This draft is almost ready for publication as a standard track RFC.

 

 

Major issues:

 

Minor issues:

In section 6.1 " If specified more than once, instances preceding the first
will be ignored and condition SHOULD be logged for possible action by the
network operator."  I am not sure what is meant by preceding the first.

 

 

Nits/editorial comments:

 

1.	The following note appears in section 10.1, 10.2 and 10.3. "Note
that the same values for the Inter-RA Export Upward sub-TLV and the Inter-RA
Export Downward Sub-TLV MUST be used when they appear in the Link TLV, Node
Attribute TLV, and Router Address TLV." - why not have it in section 10
before section 10.1.
2.	I saw in appendix  B that one of the changes from RFC 5787 was to
clarify the terminology before defining extensions, I would have found it
easier to read if the ASON hierarchy and the relation to OSPF in section 2
were presented in figures. This was more an issue to me as a reader not
familiar with the terminology and I would like to think that the more
familiar reader will not have problem.

 


------=_NextPart_000_0022_01CD79A8.68A9FD90
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:715087181;
	mso-list-type:hybrid;
	mso-list-template-ids:-1205706658 -1668626108 67698713 67698715 =
67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-bidi-font-family:Calibri;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>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><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Please resolve these comments along with any other =
Last Call comments you may receive.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span>draft-ietf-ccamp-rfc5787bis-05.<span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2012&#8211;8&#8211;12<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2012&#8211;8&#8211;17<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'> a =
standard track </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>RFC</span><=
span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoNormal>In section 6.1 &#8220; =
If specified more than once, instances preceding the first will be =
ignored and condition SHOULD be logged for possible action by the =
network operator.&#8221;&nbsp; I am not sure what is meant by preceding =
the first.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</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"'>Nits/editor=
ial comments:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><ol style=3D'margin-top:0in' start=3D1 type=3D1><li =
class=3DMsoNormal style=3D'mso-list:l0 level1 lfo1'>The following note =
appears in section 10.1, 10.2 and 10.3. &#8220;Note that the same values =
for the Inter-RA Export Upward sub-TLV and the Inter-RA Export Downward =
Sub-TLV MUST be used when they appear in the Link TLV, Node Attribute =
TLV, and Router Address TLV.&#8221; &#8211; why not have it in section =
10 before section 10.1.<o:p></o:p></li><li class=3DMsoNormal =
style=3D'mso-list:l0 level1 lfo1'>I saw in appendix&nbsp; B that one of =
the changes from RFC 5787 was to clarify the terminology before defining =
extensions, I would have found it easier to read if the ASON hierarchy =
and the relation to OSPF in section 2 were presented in figures. This =
was more an issue to me as a reader not familiar with the terminology =
and I would like to think that the more familiar reader will not have =
problem.<o:p></o:p></li></ol><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'> =
<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0022_01CD79A8.68A9FD90--


From ben@estacado.net  Mon Aug 13 13:59:48 2012
Return-Path: <ben@estacado.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4422721F867C; Mon, 13 Aug 2012 13:59:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kkgScxprJuPW; Mon, 13 Aug 2012 13:59:47 -0700 (PDT)
Received: from estacado.net (vicuna.estacado.net [4.30.77.35]) by ietfa.amsl.com (Postfix) with ESMTP id 82C5421F8671; Mon, 13 Aug 2012 13:59:47 -0700 (PDT)
Received: from [10.12.11.64] ([10.12.11.64]) (authenticated bits=0) by estacado.net (8.14.3/8.14.3) with ESMTP id q7DKwOPu081872 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 13 Aug 2012 15:58:26 -0500 (CDT) (envelope-from ben@estacado.net)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-mptcp-api-05
From: Ben Campbell <ben@estacado.net>
In-Reply-To: <9510D26531EF184D9017DF24659BB87F33D6B96847@EMV65-UKRD.domain1.systemhost.net>
Date: Mon, 13 Aug 2012 15:58:15 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4535EA27-3119-477A-8AE1-C893498D5AC5@estacado.net>
References: <CCBAA297-B839-4AEA-BB24-F4D320200415@nostrum.com> <9510D26531EF184D9017DF24659BB87F33D6B96847@EMV65-UKRD.domain1.systemhost.net>
To: philip.eardley@bt.com
X-Mailer: Apple Mail (2.1485)
Cc: ben@nostrum.com, gen-art@ietf.org, draft-ietf-mptcp-api.all@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 20:59:48 -0000

On Aug 13, 2012, at 9:14 AM, philip.eardley@bt.com wrote:

> Ben,
> Thanks for your review.=20
>=20
> The right status isn't clear-cut (I think), but when we (Chairs & Wes) =
discussed it, Info seemed best
> * mainly because precedent seems to be that API docs are =
informational, for example socket API extensions for SCTP =
http://datatracker.ietf.org/doc/rfc6458/=20

I'm willing to accept that there is precedent for doing this in an =
informational. (I wonder about the rational used previously, but that's =
probably neither here nor there.)

> * also the doc has two main parts - looking at the impact that MPTCP =
may have on application performance - and describing a basic API for =
MPTCP-aware applications. The first part seems clearly Informational. So =
if the API part is not Info, there is the effort of splitting the doc. =
Pragmatically I think this should only be done if clearly needed.

Agreed.

>=20
> I'm afraid I don't know case history of how the IETF tries to extend =
non-IETF standards.
>=20
> On the status of Posix reference, which appears twice in the doc
>>> The abstract specification is in line with the
>   Posix standard [17] as much as possible
>>> One commonly used TCP socket option (TCP_NODELAY) disables the Nagle
>   algorithm as described in [2].  This option is also specified in the
>   Posix standard [17]. =20
>=20
> The guidance:
>>> Normative references specify documents that must be read to =
understand or implement the technology in the new RFC, or whose =
technology must be present for the technology in the new RFC to work.
>=20
> On its second appearance, I think [17] is definitely being used =
informatively.
> The first appearance is less clear  cut, I think. Am inclined to say =
this is still informative - it's just explaining the style adopted for =
the abstract specification (if [17] changed then it wouldn't be =
necessary to change this doc).
>=20

Agree that the 2nd appearance is informational. But the paragraph =
containing the first citation also contains the language "=20
The de facto standard API for TCP/IP applications is the "sockets" =
interface. This document provides an abstract definition of =
MPTCP-specific extensions to this interface."  It seems to me that one =
needs to understand the sockets api in order to understand an extension =
to the sockets api. . (And, as an additional nit, the first quoted =
sentence could probably also use a citation to [17])=20

> Thanks also for the nits

You're welcome :-)

Thanks!

Ben.=

From richard@shockey.us  Mon Aug 13 18:08:18 2012
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 3207321F873E for <ietf@ietfa.amsl.com>; Mon, 13 Aug 2012 18:08:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.15
X-Spam-Level: 
X-Spam-Status: No, score=-101.15 tagged_above=-999 required=5 tests=[AWL=1.114, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Bu5rfwvLWgn for <ietf@ietfa.amsl.com>; Mon, 13 Aug 2012 18:08:13 -0700 (PDT)
Received: from oproxy6-pub.bluehost.com (oproxy6-pub.bluehost.com [67.222.54.6]) by ietfa.amsl.com (Postfix) with SMTP id F10E021F873D for <ietf@ietf.org>; Mon, 13 Aug 2012 18:08:07 -0700 (PDT)
Received: (qmail 7624 invoked by uid 0); 14 Aug 2012 01:07:45 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by cpoproxy3.bluehost.com with SMTP; 14 Aug 2012 01:07:44 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us; s=default;  h=Content-Type:MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:To:From; bh=gZl3zmurvTQJw0hZagY+hgcrv70C3kE3pXOKNUvI6RI=;  b=Nkoo9lpD0Ch+mD2cnTUcLU5HwGclaCKksssLwgDRy0meMNZN+h4NCQbR76CnojBmi//U29ClBBfrhxnVumGMUIpY3+DoCFoAMQJQjtTttWBG3usrx9xc8jpEbs+Uw69z;
Received: from [71.191.243.130] (port=57213 helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.76) (envelope-from <richard@shockey.us>) id 1T15bk-0003ZP-6f; Mon, 13 Aug 2012 19:07:44 -0600
From: "Richard Shockey" <richard@shockey.us>
To: "'Michael StJohns'" <mstjohns@comcast.net>, "'Glen Zorn'" <glenzorn@gmail.com>, <ietf@ietf.org>
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com>	<50266F05.5050601@dcrocker.net>	<1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org>	<1344737164.8891.29.camel@gwz-laptop> <20120813030319.D29F321F86AA@ietfa.amsl.com>
In-Reply-To: <20120813030319.D29F321F86AA@ietfa.amsl.com>
Subject: RE: Re: [IAB] Last Call: Modern Global Standards Paradigm
Date: Mon, 13 Aug 2012 21:07:40 -0400
Message-ID: <011901cd79b9$34bcc6f0$9e3654d0$@us>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_011A_01CD7997.ADAB26F0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac15ADM5GOB5KUVzRNS4SayarxwVAgAtc88Q
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 71.191.243.130 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, 14 Aug 2012 01:08:18 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_011A_01CD7997.ADAB26F0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

+1 Well said Mike.  For what it=92s worth I completely and =
unconditionally
support the signing of the document on behalf of the entire IETF =
community.


=20

This support is personal and does not represent any official position of =
the
SIP Forum its full members or its board. But if we were asked=85.

=20

It is totally clear to me that the WCIT process represents a substantive
threat to the multistake holder process in standards development that =
has
made the IETF and the Internet work. What is horrifying to me as well is
this idea of mandatory ITU based protocol certification testing.   The =
ITU
has ZERO business imposing this requirement on nation states. Our =
Industry
deals with compliance and certification testing in its own way without
government sanctioned intervention.=20

=20

We=92ve seen this class of threat before multiple times over the past =
decade.
Hopefully this will pass but it will certainly come up again and again.
Vigilance Vigilance. Though our focus has been pure engineering we =
cannot
ignore the forces building up to demand a return to some form of
intergovernmental control of global communications.  We won!  Now the =
forces
of darkness say .. well if it=92s going to deal with SIP/IMS telephony ( =
voice
) well it has to be regulated! Right ..!!  Wrong ..=20

=20

Granted the European PTT=92s are not helping here with totally absurd =
ideas
about abandoning the privately negotiated transit peering model with =
some
form of data sender pays abomination because they can=92t figure out =
their
business models.  Now they first had  a Whine and Cheese party in =
Brussels ,
but getting no satisfaction there they now go to the UN to support their
untenable position.=20

Richard Shockey
Shockey Consulting
Chairman of the Board of Directors SIP Forum
PSTN Mobile: +1 703.593.2683
<mailto:richard(at)shockey.us>
skype-linkedin-facebook: rshockey101
http//www.sipforum.org

=20

=20

From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Michael StJohns
Sent: Sunday, August 12, 2012 11:03 PM
To: Glen Zorn; ietf@ietf.org
Subject: Re: Re: [IAB] Last Call: Modern Global Standards Paradigm

=20

Glen and others -=20

I wanted to go back and comment on the assertion that Glen made that the
IETF and IAB chairs do not "'represent' [him] or any one other than
themselves".  I believe he is correct with respect to himself, and =
incorrect
with respect to the IETF.

I agree the IETF is not a "representative democracy", the IESG and IAB =
(and
not the IETF) are probably best described as electoral meritocracies.  =
We
randomly select "electors" from a "qualified" pool which self-selects =
mostly
from the set of all participants which in turn selects the IESG and the =
IAB
from that set of all participants.  I'm pretty sure that Carsten was =
using
"elect" to describe that process.

While the IESG and IAB may not speak for the IETF participants, they de
facto and de jure do speak for the IETF.  It's a subtle difference, but =
an
important one.  [CF the various RFCs detailing the responsibilities and
duties of the IESG, IAB and their respective chairs, the RFCs detailing =
the
standards process, and the various liaison's that have been arranged =
over
the years.]

I've noted over the years that the constituency of IETF participants =
tends
to have bouts with BSDS - back seat driver syndrome, and this is mostly =
not
helpful.  We (referring to the broad set of IETF participants going back =
25+
years) have over time evolved and agreed upon various ways of moving =
forward
for generally accepted values of "forward".  Those ways include having
granted the IESG the power to set the standards agenda, the IAB to =
negotiate
and approve liaison agreements with standards bodies, the IESG to =
ultimately
approve the standards, and the IESG, IETF Chair and IAB chair to declare =
a
perception of consensus. =20


We (the participants) have reserved to ourselves the rights jointly and
severally to comment on all of the above, to be heard on even items
delegated to the IESG and IAB and at times to carp and cavil on every =
single
point of order.  Some of this is good for the process.  But we go too =
far
way too often. =20

In this case, the IAB, IESG and their respective chairs are doing the =
jobs
we've asked them to do.  Russ, correctly I believe, asked for objections =
to
the issuance of such statement, he didn't ask for consensus.  I also =
believe
it would have been well within the current job description of the IAB =
and
IETF Chairs to just go ahead and sign the thing.

I think it comes down to this:

If you (an IETF participant) have an objection to the statement, make it
here.

If you have an objection to the process in general then - form your
objections, write an ID, and socialize what you want changed.   If =
consensus
shows you correct, it will apply down the line.

If you have a belief that the process has been violated, it's =
appropriate to
make that point, but give details rather than vague intimations.

If you have an objection related to the members of the IESG or IAB
performance, make them to the Nomcom or offer yourself as a candidate if =
you
think you can do better or both.

We've - collectively, through process established over many years - =
selected
a team of our colleagues to perform a circumscribed set of tasks.
Efficiency suggests we should mostly stand back and let them get on with =
it.

Mike



At 10:06 PM 8/11/2012, Glen Zorn wrote:



On Sat, 2012-08-11 at 17:13 +0200, Carsten Bormann wrote:=20



=20

=20
On Aug 11, 2012, at 16:41, Dave Crocker
<dhc@dcrocker.net> wrote:
=20
> consensus-oriented process
=20
Sometimes, though, you have to act.
=20
While a consensus-oriented process*) document could certainly be used to
improve (or deteriorate) the document by a couple more epsilons, I agree
with Randy Bush: Signing it now is a no-brainer.
=20
Gr=FC=DFe, Carsten
=20
*) Well there was a call for comments, and it already supplied the first
such set of epsilons. =20
That may have to do when time is of the essence.
=20
(That's also what you choose your leadership for. =20
If we don't like the outcome, we can always decide not to re-elect Russ
:-)


Did the IETF morph into a representative democracy while I was sleeping?
Last time I checked, Russ was the chair of a committee of managers, =
chosen
by a random selection of proles who may or may not have taken the =
opinions
of others into account in that selection.  He was not "elected", nor =
does he
"speak for the IETF"; ditto for Bernard.  If they wish to sign this
statement (with which I, by and large, agree, BTW), that's fine.  If =
they
wish to list all their titles (IETF-bestowed & otherwise), degrees, =
etc.,
that's fine, too, but not if the intent is to imply that they somehow
"represent" me or any one other than themselves.  If support by IETF =
members
at-large is to be signified, then an online petition of some sort would =
be a
much better idea & much less deceptive.




=20

=20
=20

=20


------=_NextPart_000_011A_01CD7997.ADAB26F0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-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=3Diso-8859-1"><meta name=3DGenerator content=3D"Microsoft Word =
12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin: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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>+1 Well said Mike.=A0 For what it&#8217;s worth I completely and =
unconditionally support the signing of the document on behalf of the =
entire IETF community. =A0<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>This support is personal and does not represent any official position =
of the SIP Forum its full members or its board. But if we were =
asked&#8230;.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>It is totally clear to me that the WCIT process represents a =
substantive threat to the multistake holder process in standards =
development that has made the IETF and the Internet work. What is =
horrifying to me as well is this idea of mandatory ITU based protocol =
certification testing. =A0=A0The ITU has ZERO business imposing this =
requirement on nation states. Our Industry deals with compliance and =
certification testing in its own way without government sanctioned =
intervention. <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>We&#8217;ve seen this class of threat before multiple times over the =
past decade.=A0 Hopefully this will pass but it will certainly come up =
again and again. Vigilance Vigilance. Though our focus has been pure =
engineering we cannot ignore the forces building up to demand a return =
to some form of intergovernmental control of global communications.=A0 =
We won! =A0Now the forces of darkness say .. well if it&#8217;s going to =
deal with SIP/IMS telephony ( voice ) well it has to be regulated! Right =
..!! =A0Wrong .. <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Granted the European PTT&#8217;s are not helping here with totally =
absurd ideas about abandoning the privately negotiated transit peering =
model with some form of data sender pays abomination because they =
can&#8217;t figure out their business models.=A0 Now they first had =A0a =
Whine and Cheese party in Brussels , but getting no satisfaction there =
they now go to the UN to support their untenable position. =
<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt'>Richard Shockey<br>Shockey =
Consulting<br>Chairman of the Board of Directors SIP Forum<br>PSTN =
Mobile: +1 703.593.2683<br>&lt;<a =
href=3D"mailto:richard(at)shockey.us">mailto:richard(at)shockey.us</a>&gt=
;<br>skype-linkedin-facebook: =
rshockey101<br>http//www.sipforum.org</span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] <b>On Behalf Of =
</b>Michael StJohns<br><b>Sent:</b> Sunday, August 12, 2012 11:03 =
PM<br><b>To:</b> Glen Zorn; ietf@ietf.org<br><b>Subject:</b> Re: Re: =
[IAB] Last Call: Modern Global Standards =
Paradigm<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Glen and =
others - <br><br>I wanted to go back and comment on the assertion that =
Glen made that the IETF and IAB chairs do not &quot;'represent' [him] or =
any one other than themselves&quot;.&nbsp; I believe he is correct with =
respect to himself, and incorrect with respect to the IETF.<br><br>I =
agree the IETF is not a &quot;representative democracy&quot;, the IESG =
and IAB (and not the IETF) are probably best described as electoral =
meritocracies.&nbsp; We randomly select &quot;electors&quot; from a =
&quot;qualified&quot; pool which self-selects mostly from the set of all =
participants which in turn selects the IESG and the IAB from that set of =
all participants.&nbsp; I'm pretty sure that Carsten was using =
&quot;elect&quot; to describe that process.<br><br>While the IESG and =
IAB may not speak for the IETF participants, they de facto and de jure =
do speak for the IETF.&nbsp; It's a subtle difference, but an important =
one.&nbsp; [CF the various RFCs detailing the responsibilities and =
duties of the IESG, IAB and their respective chairs, the RFCs detailing =
the standards process, and the various liaison's that have been arranged =
over the years.]<br><br>I've noted over the years that the constituency =
of IETF participants tends to have bouts with BSDS - back seat driver =
syndrome, and this is mostly not helpful.&nbsp; We (referring to the =
broad set of IETF participants going back 25+ years) have over time =
evolved and agreed upon various ways of moving forward for generally =
accepted values of &quot;forward&quot;.&nbsp; Those ways include having =
granted the IESG the power to set the standards agenda, the IAB to =
negotiate and approve liaison agreements with standards bodies, the IESG =
to ultimately approve the standards, and the IESG, IETF Chair and IAB =
chair to declare a perception of consensus.&nbsp; <br><br><br>We (the =
participants) have reserved to ourselves the rights jointly and =
severally to comment on all of the above, to be heard on even items =
delegated to the IESG and IAB and at times to carp and cavil on every =
single point of order.&nbsp; Some of this is good for the process.&nbsp; =
But we go too far way too often.&nbsp; <br><br>In this case, the IAB, =
IESG and their respective chairs are doing the jobs we've asked them to =
do.&nbsp; Russ, correctly I believe, asked for objections to the =
issuance of such statement, he didn't ask for consensus.&nbsp; I also =
believe it would have been well within the current job description of =
the IAB and IETF Chairs to just go ahead and sign the thing.<br><br>I =
think it comes down to this:<br><br>If you (an IETF participant) have an =
objection to the statement, make it here.<br><br>If you have an =
objection to the process in general then - form your objections, write =
an ID, and socialize what you want changed.&nbsp;&nbsp; If consensus =
shows you correct, it will apply down the line.<br><br>If you have a =
belief that the process has been violated, it's appropriate to make that =
point, but give details rather than vague intimations.<br><br>If you =
have an objection related to the members of the IESG or IAB performance, =
make them to the Nomcom or offer yourself as a candidate if you think =
you can do better or both.<br><br>We've - collectively, through process =
established over many years - selected a team of our colleagues to =
perform a circumscribed set of tasks.&nbsp; Efficiency suggests we =
should mostly stand back and let them get on with =
it.<br><br>Mike<br><br><br><br>At 10:06 PM 8/11/2012, Glen Zorn =
wrote:<br><br><o:p></o:p></p><p class=3DMsoNormal>On Sat, 2012-08-11 at =
17:13 +0200, Carsten Bormann wrote: <br><br><o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><pre><o:p>&nbsp;</o:p></pre><pre>O=
n Aug 11, 2012, at 16:41, Dave Crocker<o:p></o:p></pre><pre>&lt;<a =
href=3D"mailto:dhc@dcrocker.net">dhc@dcrocker.net</a>&gt; =
wrote:<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>&gt; =
consensus-oriented =
process<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Sometimes, =
though, you have to =
act.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>While a =
consensus-oriented process*) document could certainly be used =
to<o:p></o:p></pre><pre>improve (or deteriorate) the document by a =
couple more epsilons, I agree<o:p></o:p></pre><pre>with Randy Bush: =
Signing it now is a =
no-brainer.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Gr=FC=DFe, =
Carsten<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>*) Well there =
was a call for comments, and it already supplied the =
first<o:p></o:p></pre><pre>such set of epsilons.&nbsp; =
<o:p></o:p></pre><pre>That may have to do when time is of the =
essence.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>(That's also =
what you choose your leadership for.&nbsp; <o:p></o:p></pre><pre>If we =
don't like the outcome, we can always decide not to re-elect =
Russ<o:p></o:p></pre><pre>:-)<o:p></o:p></pre><p =
class=3DMsoNormal><br>Did the IETF morph into a representative democracy =
while I was sleeping?&nbsp; Last time I checked, Russ was the chair of a =
committee of managers, chosen by a random selection of proles who may or =
may not have taken the opinions of others into account in that =
selection.&nbsp; He was not &quot;elected&quot;, nor does he &quot;speak =
for the IETF&quot;; ditto for Bernard.&nbsp; If they wish to sign this =
statement (with which I, by and large, agree, BTW), that's fine.&nbsp; =
If they wish to list all their titles (IETF-bestowed &amp; otherwise), =
degrees, etc., that's fine, too, but not if the intent is to imply that =
they somehow &quot;represent&quot; me or any one other than =
themselves.&nbsp; If support by IETF members at-large is to be =
signified, then an online petition of some sort would be a much better =
idea &amp; much less deceptive.<br><br><br><o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><pre><o:p>&nbsp;</o:p></pre><pre><=
o:p>&nbsp;</o:p></pre><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_011A_01CD7997.ADAB26F0--


From eburger-l@standardstrack.com  Mon Aug 13 19:26:17 2012
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 1A85F21F84C8 for <ietf@ietfa.amsl.com>; Mon, 13 Aug 2012 19:26:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R+Cc7toAP+kF for <ietf@ietfa.amsl.com>; Mon, 13 Aug 2012 19:26:16 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.215.15]) by ietfa.amsl.com (Postfix) with ESMTP id 65D1921F84A0 for <ietf@ietf.org>; Mon, 13 Aug 2012 19:26:16 -0700 (PDT)
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8]:57416 helo=[192.168.15.138]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger-l@standardstrack.com>) id 1T16pZ-0005kx-DA for ietf@ietf.org; Mon, 13 Aug 2012 19:26:05 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: [iucg] Last Call: Modern Global Standards Paradigm
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <F2E0F8B862341F3DC407A2DA@JcK-HP8200.jck.com>
Date: Mon, 13 Aug 2012 22:26:12 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E521F97C-24C8-4D2E-9471-844FCD69212C@standardstrack.com>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <CAMm+Lwio8=EyW-=LZE8BA4=6N=H4f7a1Nycg25LxB920ceZ6JA@mail.gmail.com> <1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.com> <276B7D303A96E840D2F95107@JcK-HP8200.jck.com> <CAMm+LwjL=tnYrtmHkV+=+VeOCo+1PjAu+pW0LnUyHYhVX_pPZA@mail.gmail.com> <C01C22690CE178AF8C2E52F7@JcK-HP8200.jck.com> <20120813012310.9F01A21F861E@ietfa.amsl.com> <5028C4C8.40508@tana.it> <F2E0F8B862341F3DC407A2DA@JcK-HP8200.jck.com>
To: IETF list <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: Tue, 14 Aug 2012 02:26:17 -0000

+1. The ITU is not evil. It just is not the right place for Internet =
standards development. As John points out, there are potential uses of =
the ITU-T for good.

On Aug 13, 2012, at 10:50 AM, John C Klensin wrote:

>=20
>=20
> --On Monday, August 13, 2012 11:11 +0200 Alessandro Vesely
> <vesely@tana.it> wrote:
>=20
>> ...
>> FWIW, I'd like to recall that several governments endorse IETF
>> protocols by establishing Internet based procedures for
>> official communications with the relevant PA, possibly giving
>> them legal standing.  Francesco Gennai presented a brief
>> review of such procedures[*] at the APPSAWG meeting in Paris.
>> At the time, John Klensin suggested that, while a more
>> in-depth review of existing practices would be appreciated,
>> the ITU is a more suitable body for the standardization of a
>> unified, compatible protocol for certified email, because of
>> those governmental involvements.
>>=20
>> [*]
>>=20
> http://www.ietf.org/proceedings/83/slides/slides-83-appsawg-1.pdf
>=20
> Alessandro,
>=20
> Please be a little careful about context, as your sequence of
> comments above could easily be misleading. =20
>=20
> For the very specific case of email certified by third parties,
> especially where there is a requirement for worldwide
> recognition (the topic of the talk and slides you cited), the
> biggest problem has, historically, been an administrative and
> policy one, not a technical standards issue.  We know how to
> digitally sign email in several different ways -- there is
> actually no shortage of standards.   While additional standards
> are certainly possible, more options in the absence of
> compelling need almost always reduces practical
> interoperability.  Perhaps the key question in the certified
> mail matter is who does the certifying and why anyone else
> should pay attention.  The thing that makes that question
> complicated was famously described by Jeff Schiller (I believe
> while he was still IETF Security AD) when he suggested that
> someone would need to be insane to issue general-purpose
> certificates that actually certified identity unless they were
> an entity able to invoke sovereign immunity, i.e., a government.
>=20
> For certified email (or certified postal mail), your ability to
> rely on the certification in, e.g., legal matters ultimately
> depends on your government being willing to say something to you
> like "if you rely on this in the following ways, we will protect
> you from bad consequences if it wasn't reliable or accurate".
> If you want the same relationship with "foreign" mail, you still
> have to rely on your government's assertions since a foreign
> government can't do a thing for you if you get into trouble.
> That, in turn, requires treaties or some sort of bilateral
> agreements between the governments (for postal mail, some of
> that is built into the postal treaties). =20
>=20
> International organizations, particularly UN-based ones, can
> serve an important role in arranging such agreements and
> possibly even in being the repository organization for the
> treaties.  In the particular case of certified email, the ITU
> could reasonably play that role (although it seems to me that a
> very strong case could be made for having the UPU do it instead
> by building on existing foundations).
>=20
> But that has nothing to do with the development of technical
> protocol standards.  Historical experience with development of
> technical standards by governmental/legislative bodies that then
> try to mandate their use has been almost universally poor and
> has often included ludicrous results.
>=20
> A similar example arises with the spam problem.  There are many
> technical approaches to protecting the end user from spam
> (especially malicious spam) and for facilitating the efforts of
> mail delivery service providers and devices to apply those
> protective mechanisms.  Some of them justify technical standards
> that should be worked out in open forums that make their
> decisions on open and technical bases.  But, if one wants to
> prevent spam from imposing costs on intended recipients or third
> parties, that becomes largely a law-making and law enforcement
> problem, not a technical one.  If countries decide that they
> want to prevent spam from being sent, or to punish the senders,
> a certain amount of international cooperation (bilateral or
> multilaterial) is obviously going to be necessary.   As with the
> UPU and email certification, there might be better agencies or
> forums for discussion than the ITU or there might not.  But it
> isn't a technical protocol problem that the IETF is going to be
> able to solve or should even try to address, at least without a
> clear and actionable problem statement from those bodies.
>=20
> I do believe that the ITU can, and should, serve a useful role
> in the modern world.  The discussion above (and some of the work
> of the Development and Radio Sectors) are good illustrations.
> But those cases have, as far as I can tell, nothing to do with
> the proposed statement, which is about the development and
> deployment of technical protocol standards.
>=20
> regards,
>    john
>=20


From adrian@olddog.co.uk  Mon Aug 13 22:05:04 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F294521F8648; Mon, 13 Aug 2012 22:05:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.511
X-Spam-Level: 
X-Spam-Status: No, score=-2.511 tagged_above=-999 required=5 tests=[AWL=0.087,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ms+wK5KcfPnl; Mon, 13 Aug 2012 22:05:02 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 9A2C621F8621; Mon, 13 Aug 2012 22:05:01 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7E54wrC016653;  Tue, 14 Aug 2012 06:04:58 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7E54q1X016625 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 14 Aug 2012 06:04:56 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Roni Even'" <ron.even.tlv@gmail.com>, <draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org>
References: <002101cd7997$a5204330$ef60c990$@gmail.com>
In-Reply-To: <002101cd7997$a5204330$ef60c990$@gmail.com>
Subject: RE: Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05
Date: Tue, 14 Aug 2012 06:04:49 +0100
Message-ID: <09c201cd79da$570f3be0$052db3a0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_09C3_01CD79E2.B8D837C0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGVMjaGM7HZ8bSlogDWIwhoGoR3V5fJT4Qg
Content-Language: en-gb
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Aug 2012 05:05:04 -0000

This is a multipart message in MIME format.

------=_NextPart_000_09C3_01CD79E2.B8D837C0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Thanks Roni,
Good catches.
Adrian
 
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Roni
Even
Sent: 13 August 2012 22:07
To: draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org
Cc: gen-art@ietf.org; ietf@ietf.org
Subject: Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05
 
I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART,
please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
 
Please resolve these comments along with any other Last Call comments you may
receive.
 
Document: draft-ietf-ccamp-rfc5787bis-05.
Reviewer: Roni Even
Review Date:2012-8-12
IETF LC End Date: 2012-8-17
IESG Telechat date:
 
Summary: This draft is almost ready for publication as a standard track RFC.
 
 
Major issues:
 
Minor issues:
In section 6.1 " If specified more than once, instances preceding the first will
be ignored and condition SHOULD be logged for possible action by the network
operator."  I am not sure what is meant by preceding the first.
 
 
Nits/editorial comments:
 
1.	The following note appears in section 10.1, 10.2 and 10.3. "Note that
the same values for the Inter-RA Export Upward sub-TLV and the Inter-RA Export
Downward Sub-TLV MUST be used when they appear in the Link TLV, Node Attribute
TLV, and Router Address TLV." - why not have it in section 10 before section
10.1.
2.	I saw in appendix  B that one of the changes from RFC 5787 was to
clarify the terminology before defining extensions, I would have found it easier
to read if the ASON hierarchy and the relation to OSPF in section 2 were
presented in figures. This was more an issue to me as a reader not familiar with
the terminology and I would like to think that the more familiar reader will not
have problem.
 
 

------=_NextPart_000_09C3_01CD79E2.B8D837C0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DProgId content=3DWord.Document><meta =
name=3DGenerator content=3D"Microsoft Word 14"><meta name=3DOriginator =
content=3D"Microsoft Word 14"><link rel=3DFile-List =
href=3D"cid:filelist.xml@01CD79E2.796F9CE0"><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:EnvelopeVis/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-GB</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:DoNotExpandShiftReturn/>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520092929 1073786111 9 0 415 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520081665 -1073717157 41 0 66047 0;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:modern;
	mso-font-pitch:fixed;
	mso-font-signature:-520092929 1073806591 9 0 415 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.5pt;
	font-family:Consolas;
	mso-fareast-font-family:Calibri;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Plain Text";
	font-family:Consolas;
	mso-ascii-font-family:Consolas;
	mso-hansi-font-family:Consolas;
	mso-bidi-font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:Calibri;
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-size:10.0pt;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:715087181;
	mso-list-type:hybrid;
	mso-list-template-ids:-1205706658 -1668626108 67698713 67698715 =
67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-bidi-font-family:Calibri;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:1630161403;
	mso-list-template-ids:-244951626;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue =
vlink=3Dpurple style=3D'tab-interval:36.0pt'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'mso-ascii-font-family:Calibri;mso-hansi-font-family:Calibri;mso-=
bidi-font-family:"Times New Roman";color:#1F497D'>Thanks =
Roni,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'mso-ascii-font-family:Calibri;mso-hansi-font-family:Calibri;mso-=
bidi-font-family:"Times New Roman";color:#1F497D'>Good =
catches.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'mso-ascii-font-family:Calibri;mso-hansi-font-family:Calibri;mso-=
bidi-font-family:"Times New =
Roman";color:#1F497D'>Adrian<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'mso-ascii-font-family:Calibri;mso-hansi-font-family:Calibri;mso-=
bidi-font-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt;line-height:normal'><b><=
span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New =
Roman";mso-ansi-language:EN-US'>From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New Roman";mso-ansi-language:EN-US'> =
ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] <b>On Behalf Of =
</b>Roni Even<br><b>Sent:</b> 13 August 2012 22:07<br><b>To:</b> =
draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org<br><b>Cc:</b> =
gen-art@ietf.org; ietf@ietf.org<br><b>Subject:</b> Gen-ART LC review of =
draft-ietf-ccamp-rfc5787bis-05<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'mso-ansi-language:EN-US'>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></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Please resolve these comments along =
with any other Last Call comments you may =
receive.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>Document: </span><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>draft-ietf-ccamp-rfc5787bis-05.</span><=
span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>Reviewer: Roni Even<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>Review Date:2012&#8211;8&#8211;12<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>IETF LC End Date: =
2012&#8211;8&#8211;17<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>IESG Telechat date:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>Summary: This draft is almost ready for publication as a =
standard track RFC.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>Major issues:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>Minor issues:<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>In section 6.1 &#8220; If specified =
more than once, instances preceding the first will be ignored and =
condition SHOULD be logged for possible action by the network =
operator.&#8221;&nbsp; I am not sure what is meant by preceding the =
first.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>Nits/editorial comments:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p>&nbsp;</o:p></span></p><ol style=3D'margin-top:0cm' =
start=3D1 type=3D1><li class=3DMsoNormal style=3D'mso-list:l0 level1 =
lfo3'><span lang=3DEN-US style=3D'mso-fareast-font-family:"Times New =
Roman";mso-ansi-language:EN-US'>The following note appears in section =
10.1, 10.2 and 10.3. &#8220;Note that the same values for the Inter-RA =
Export Upward sub-TLV and the Inter-RA Export Downward Sub-TLV MUST be =
used when they appear in the Link TLV, Node Attribute TLV, and Router =
Address TLV.&#8221; &#8211; why not have it in section 10 before section =
10.1.<o:p></o:p></span></li><li class=3DMsoNormal style=3D'mso-list:l0 =
level1 lfo3'><span lang=3DEN-US style=3D'mso-fareast-font-family:"Times =
New Roman";mso-ansi-language:EN-US'>I saw in appendix&nbsp; B that one =
of the changes from RFC 5787 was to clarify the terminology before =
defining extensions, I would have found it easier to read if the ASON =
hierarchy and the relation to OSPF in section 2 were presented in =
figures. This was more an issue to me as a reader not familiar with the =
terminology and I would like to think that the more familiar reader will =
not have problem.<o:p></o:p></span></li></ol><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p></div></div=
></body></html>
------=_NextPart_000_09C3_01CD79E2.B8D837C0--


From lear@cisco.com  Mon Aug 13 23:08:18 2012
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 1849111E80A4; Mon, 13 Aug 2012 23:08:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lvwqXWGu0fNK; Mon, 13 Aug 2012 23:08:16 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id B436511E809C; Mon, 13 Aug 2012 23:08:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=443; q=dns/txt; s=iport; t=1344924496; x=1346134096; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=q5vm6OfaUqGPDvRl7wissjLC+ieR6gYBsc+vaafsXbY=; b=JKeOpZx0oORmIIIXjzqql/LiqA+JYpFWKwYq7g9zDsPAgZ6JHcxr619/ BbPyNJVcVR5fa3atsQTnOFaTIRMiaevW9IGI8jWFuaTUhKCXtvHjxKYRL j6t8g86LR8zgDiXEB/ycD32bZYrJ7QCZzzPkJXSmflGnwJcGpgPGR6c6F w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhEFALfqKVCrRDoG/2dsb2JhbABFhTpHtAyBB4IgAQEBAgISARBVARALGAICBRYLAgIJAwIBAgFFBg0BBwEBBRmHagyYFo0Zk2eBIYlxhR+BEgOVS44qgWaCYQ
X-IronPort-AV: E=Sophos;i="4.77,764,1336348800"; d="scan'208";a="54936220"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-4.cisco.com with ESMTP; 14 Aug 2012 06:08:16 +0000
Received: from sjc-vpn3-765.cisco.com (sjc-vpn3-765.cisco.com [10.21.66.253]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q7E68CI3029111 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);  Tue, 14 Aug 2012 06:08:14 GMT
Message-ID: <5029EB4C.2090107@cisco.com>
Date: Tue, 14 Aug 2012 08:08:12 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Last Call: Modern Global Standards Paradigm
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <m27gt5y6py.wl%randy@psg.com> <18D3D2AC-57DD-41D2-A8BD-1D845956E2F4@vpnc.org>
In-Reply-To: <18D3D2AC-57DD-41D2-A8BD-1D845956E2F4@vpnc.org>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Chair <chair@ietf.org>, ietf list <ietf@ietf.org>, IAB <iab@iab.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Aug 2012 06:08:18 -0000

+1

On 8/11/12 8:10 PM, Paul Hoffman wrote:
> On Aug 11, 2012, at 5:05 AM, Randy Bush wrote:
>
>>> The IETF Chair and the IAB Chair intend to sign the Affirmation
>>> of the Modern Global Standards Paradigm, which can be found
>>> here:
>>>
>>> http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf
>> no brainer.
> Even with a brain, the document is obviously good. Please sign it.
>
> --Paul Hoffman
>
>


From aalain@afribone.trstech.net  Tue Aug 14 05:22:36 2012
Return-Path: <aalain@afribone.trstech.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC0F021F8627 for <ietf@ietfa.amsl.com>; Tue, 14 Aug 2012 05:22:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NDMhcosIRYDr for <ietf@ietfa.amsl.com>; Tue, 14 Aug 2012 05:22:35 -0700 (PDT)
Received: from afribone.trstech.net (afribone.trstech.net [196.200.57.137]) by ietfa.amsl.com (Postfix) with ESMTP id 87A1F21F8534 for <ietf@ietf.org>; Tue, 14 Aug 2012 05:22:34 -0700 (PDT)
Received: from [80.248.74.18] (helo=[192.168.3.5]) by afribone.trstech.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <aalain@afribone.trstech.net>) id 1T1G8j-0007aj-Cc for ietf@ietf.org; Tue, 14 Aug 2012 12:22:31 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: ALAIN AINA <aalain@trstech.net>
In-Reply-To: <E521F97C-24C8-4D2E-9471-844FCD69212C@standardstrack.com>
Date: Tue, 14 Aug 2012 16:21:58 +0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <755EBCEF-6064-4BEB-920F-0FBFB4592BBB@trstech.net>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <CAMm+Lwio8=EyW-=LZE8BA4=6N=H4f7a1Nycg25LxB920ceZ6JA@mail.gmail.com> <1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.com> <276B7D303A96E840D2F95107@JcK-HP8200.jck.com> <CAMm+LwjL=tnYrtmHkV+=+VeOCo+1PjAu+pW0LnUyHYhVX_pPZA@mail.gmail.com> <C01C22690CE178AF8C2E52F7@JcK-HP8200.jck.com> <20120813012310.9F01A21F861E@ietfa.amsl.com> <5028C4C8.40508@tana.it> <F2E0F8B862341F3DC407A2DA@JcK-HP8200.jck.com> <E521F97C-24C8-4D2E-9471-844FCD69212C@standardstrack.com>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
Sender: aalain@afribone.trstech.net
X-SA-Exim-Connect-IP: 80.248.74.18
X-SA-Exim-Mail-From: aalain@afribone.trstech.net
Subject: Re: [iucg] Last Call: Modern Global Standards Paradigm
X-SA-Exim-Version: 4.2.1 (built Thu, 21 Oct 2010 18:52:38 +0000)
X-SA-Exim-Scanned: Yes (on afribone.trstech.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, 14 Aug 2012 12:22:36 -0000

I will say "there are potential uses of the  ITU for good".

--Alain

On Aug 14, 2012, at 6:26 AM, Eric Burger wrote:

> +1. The ITU is not evil. It just is not the right place for Internet =
standards development. As John points out, there are potential uses of =
the ITU-T for good.
>=20
> On Aug 13, 2012, at 10:50 AM, John C Klensin wrote:
>=20
>>=20
>>=20
>> --On Monday, August 13, 2012 11:11 +0200 Alessandro Vesely
>> <vesely@tana.it> wrote:
>>=20
>>> ...
>>> FWIW, I'd like to recall that several governments endorse IETF
>>> protocols by establishing Internet based procedures for
>>> official communications with the relevant PA, possibly giving
>>> them legal standing.  Francesco Gennai presented a brief
>>> review of such procedures[*] at the APPSAWG meeting in Paris.
>>> At the time, John Klensin suggested that, while a more
>>> in-depth review of existing practices would be appreciated,
>>> the ITU is a more suitable body for the standardization of a
>>> unified, compatible protocol for certified email, because of
>>> those governmental involvements.
>>>=20
>>> [*]
>>>=20
>> http://www.ietf.org/proceedings/83/slides/slides-83-appsawg-1.pdf
>>=20
>> Alessandro,
>>=20
>> Please be a little careful about context, as your sequence of
>> comments above could easily be misleading. =20
>>=20
>> For the very specific case of email certified by third parties,
>> especially where there is a requirement for worldwide
>> recognition (the topic of the talk and slides you cited), the
>> biggest problem has, historically, been an administrative and
>> policy one, not a technical standards issue.  We know how to
>> digitally sign email in several different ways -- there is
>> actually no shortage of standards.   While additional standards
>> are certainly possible, more options in the absence of
>> compelling need almost always reduces practical
>> interoperability.  Perhaps the key question in the certified
>> mail matter is who does the certifying and why anyone else
>> should pay attention.  The thing that makes that question
>> complicated was famously described by Jeff Schiller (I believe
>> while he was still IETF Security AD) when he suggested that
>> someone would need to be insane to issue general-purpose
>> certificates that actually certified identity unless they were
>> an entity able to invoke sovereign immunity, i.e., a government.
>>=20
>> For certified email (or certified postal mail), your ability to
>> rely on the certification in, e.g., legal matters ultimately
>> depends on your government being willing to say something to you
>> like "if you rely on this in the following ways, we will protect
>> you from bad consequences if it wasn't reliable or accurate".
>> If you want the same relationship with "foreign" mail, you still
>> have to rely on your government's assertions since a foreign
>> government can't do a thing for you if you get into trouble.
>> That, in turn, requires treaties or some sort of bilateral
>> agreements between the governments (for postal mail, some of
>> that is built into the postal treaties). =20
>>=20
>> International organizations, particularly UN-based ones, can
>> serve an important role in arranging such agreements and
>> possibly even in being the repository organization for the
>> treaties.  In the particular case of certified email, the ITU
>> could reasonably play that role (although it seems to me that a
>> very strong case could be made for having the UPU do it instead
>> by building on existing foundations).
>>=20
>> But that has nothing to do with the development of technical
>> protocol standards.  Historical experience with development of
>> technical standards by governmental/legislative bodies that then
>> try to mandate their use has been almost universally poor and
>> has often included ludicrous results.
>>=20
>> A similar example arises with the spam problem.  There are many
>> technical approaches to protecting the end user from spam
>> (especially malicious spam) and for facilitating the efforts of
>> mail delivery service providers and devices to apply those
>> protective mechanisms.  Some of them justify technical standards
>> that should be worked out in open forums that make their
>> decisions on open and technical bases.  But, if one wants to
>> prevent spam from imposing costs on intended recipients or third
>> parties, that becomes largely a law-making and law enforcement
>> problem, not a technical one.  If countries decide that they
>> want to prevent spam from being sent, or to punish the senders,
>> a certain amount of international cooperation (bilateral or
>> multilaterial) is obviously going to be necessary.   As with the
>> UPU and email certification, there might be better agencies or
>> forums for discussion than the ITU or there might not.  But it
>> isn't a technical protocol problem that the IETF is going to be
>> able to solve or should even try to address, at least without a
>> clear and actionable problem statement from those bodies.
>>=20
>> I do believe that the ITU can, and should, serve a useful role
>> in the modern world.  The discussion above (and some of the work
>> of the Development and Radio Sectors) are good illustrations.
>> But those cases have, as far as I can tell, nothing to do with
>> the proposed statement, which is about the development and
>> deployment of technical protocol standards.
>>=20
>> regards,
>>   john
>>=20
>=20


From daedulus@btconnect.com  Tue Aug 14 06:40:04 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 762CE21F8692 for <ietf@ietfa.amsl.com>; Tue, 14 Aug 2012 06:40:04 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MUgvuLLsfavJ for <ietf@ietfa.amsl.com>; Tue, 14 Aug 2012 06:40:03 -0700 (PDT)
Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe005.messaging.microsoft.com [213.199.154.143]) by ietfa.amsl.com (Postfix) with ESMTP id 0C30E21F8674 for <ietf@ietf.org>; Tue, 14 Aug 2012 06:40:02 -0700 (PDT)
Received: from mail52-db3-R.bigfish.com (10.3.81.238) by DB3EHSOBE010.bigfish.com (10.3.84.30) with Microsoft SMTP Server id 14.1.225.23; Tue, 14 Aug 2012 13:40:02 +0000
Received: from mail52-db3 (localhost [127.0.0.1])	by mail52-db3-R.bigfish.com (Postfix) with ESMTP id E68663A044A; Tue, 14 Aug 2012 13:40:01 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.224.141; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0702HT008.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -27
X-BigFish: PS-27(zz98dI9371I542M1432Izz1202hzz8275ch1033IL8275dh5eeeKz2dh2a8h5a9h668h839hd24hf0ah107ah1177h304l)
Received: from mail52-db3 (localhost.localdomain [127.0.0.1]) by mail52-db3 (MessageSwitch) id 1344951599951276_27645; Tue, 14 Aug 2012 13:39:59 +0000 (UTC)
Received: from DB3EHSMHS010.bigfish.com (unknown [10.3.81.241])	by mail52-db3.bigfish.com (Postfix) with ESMTP id E67674A0083; Tue, 14 Aug 2012 13:39:59 +0000 (UTC)
Received: from DB3PRD0702HT008.eurprd07.prod.outlook.com (157.55.224.141) by DB3EHSMHS010.bigfish.com (10.3.87.110) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 14 Aug 2012 13:39:56 +0000
Received: from SN2PRD0710HT001.namprd07.prod.outlook.com (157.56.234.149) by pod51017.outlook.com (10.3.4.173) with Microsoft SMTP Server (TLS) id 14.15.108.4; Tue, 14 Aug 2012 13:39:54 +0000
Message-ID: <035a01cd7a21$a6471c40$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: ALAIN AINA <aalain@trstech.net>, IETF <ietf@ietf.org>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org><CAMm+Lwio8=EyW-=LZE8BA4=6N=H4f7a1Nycg25LxB920ceZ6JA@mail.gmail.com><1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.com><276B7D303A96E840D2F95107@JcK-HP8200.jck.com><CAMm+LwjL=tnYrtmHkV+=+VeOCo+1PjAu+pW0LnUyHYhVX_pPZA@mail.gmail.com><C01C22690CE178AF8C2E52F7@JcK-HP8200.jck.com><20120813012310.9F01A21F861E@ietfa.amsl.com><5028C4C8.40508@tana.it><F2E0F8B862341F3DC407A2DA@JcK-HP8200.jck.com><E521F97C-24C8-4D2E-9471-844FCD69212C@standardstrack.com> <755EBCEF-6064-4BEB-920F-0FBFB4592BBB@trstech.net>
Subject: Re: [iucg] Last Call: Modern Global Standards Paradigm
Date: Tue, 14 Aug 2012 14:35:12 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.234.149]
X-OriginatorOrg: btconnect.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Aug 2012 13:40:04 -0000

----- Original Message -----
From: "ALAIN AINA" <aalain@trstech.net>
To: "IETF" <ietf@ietf.org>
Sent: Tuesday, August 14, 2012 1:21 PM

I will say "there are potential uses of the  ITU for good".

<tp>
Yes, they did a brilliant job in developing standards which allow
the proprietary phone network of one country to interface to
the proprietary phone network of another country, without
which we could never have had International Subscriber Trunk
Dialling.  Whether this is a suitable model for the Internet
seems doubtful to me.

Tom Petch

</tp>--Alain

On Aug 14, 2012, at 6:26 AM, Eric Burger wrote:

> +1. The ITU is not evil. It just is not the right place for Internet
standards development. As John points out, there are potential uses of
the ITU-T for good.
>
> On Aug 13, 2012, at 10:50 AM, John C Klensin wrote:
>
>>
>>
>> --On Monday, August 13, 2012 11:11 +0200 Alessandro Vesely
>> <vesely@tana.it> wrote:
>>
>>> ...
>>> FWIW, I'd like to recall that several governments endorse IETF
>>> protocols by establishing Internet based procedures for
>>> official communications with the relevant PA, possibly giving
>>> them legal standing.  Francesco Gennai presented a brief
>>> review of such procedures[*] at the APPSAWG meeting in Paris.
>>> At the time, John Klensin suggested that, while a more
>>> in-depth review of existing practices would be appreciated,
>>> the ITU is a more suitable body for the standardization of a
>>> unified, compatible protocol for certified email, because of
>>> those governmental involvements.
>>>
>>> [*]
>>>
>> http://www.ietf.org/proceedings/83/slides/slides-83-appsawg-1.pdf
>>
>> Alessandro,
>>
>> Please be a little careful about context, as your sequence of
>> comments above could easily be misleading.
>>
>> For the very specific case of email certified by third parties,
>> especially where there is a requirement for worldwide
>> recognition (the topic of the talk and slides you cited), the
>> biggest problem has, historically, been an administrative and
>> policy one, not a technical standards issue.  We know how to
>> digitally sign email in several different ways -- there is
>> actually no shortage of standards.   While additional standards
>> are certainly possible, more options in the absence of
>> compelling need almost always reduces practical
>> interoperability.  Perhaps the key question in the certified
>> mail matter is who does the certifying and why anyone else
>> should pay attention.  The thing that makes that question
>> complicated was famously described by Jeff Schiller (I believe
>> while he was still IETF Security AD) when he suggested that
>> someone would need to be insane to issue general-purpose
>> certificates that actually certified identity unless they were
>> an entity able to invoke sovereign immunity, i.e., a government.
>>
>> For certified email (or certified postal mail), your ability to
>> rely on the certification in, e.g., legal matters ultimately
>> depends on your government being willing to say something to you
>> like "if you rely on this in the following ways, we will protect
>> you from bad consequences if it wasn't reliable or accurate".
>> If you want the same relationship with "foreign" mail, you still
>> have to rely on your government's assertions since a foreign
>> government can't do a thing for you if you get into trouble.
>> That, in turn, requires treaties or some sort of bilateral
>> agreements between the governments (for postal mail, some of
>> that is built into the postal treaties).
>>
>> International organizations, particularly UN-based ones, can
>> serve an important role in arranging such agreements and
>> possibly even in being the repository organization for the
>> treaties.  In the particular case of certified email, the ITU
>> could reasonably play that role (although it seems to me that a
>> very strong case could be made for having the UPU do it instead
>> by building on existing foundations).
>>
>> But that has nothing to do with the development of technical
>> protocol standards.  Historical experience with development of
>> technical standards by governmental/legislative bodies that then
>> try to mandate their use has been almost universally poor and
>> has often included ludicrous results.
>>
>> A similar example arises with the spam problem.  There are many
>> technical approaches to protecting the end user from spam
>> (especially malicious spam) and for facilitating the efforts of
>> mail delivery service providers and devices to apply those
>> protective mechanisms.  Some of them justify technical standards
>> that should be worked out in open forums that make their
>> decisions on open and technical bases.  But, if one wants to
>> prevent spam from imposing costs on intended recipients or third
>> parties, that becomes largely a law-making and law enforcement
>> problem, not a technical one.  If countries decide that they
>> want to prevent spam from being sent, or to punish the senders,
>> a certain amount of international cooperation (bilateral or
>> multilaterial) is obviously going to be necessary.   As with the
>> UPU and email certification, there might be better agencies or
>> forums for discussion than the ITU or there might not.  But it
>> isn't a technical protocol problem that the IETF is going to be
>> able to solve or should even try to address, at least without a
>> clear and actionable problem statement from those bodies.
>>
>> I do believe that the ITU can, and should, serve a useful role
>> in the modern world.  The discussion above (and some of the work
>> of the Development and Radio Sectors) are good illustrations.
>> But those cases have, as far as I can tell, nothing to do with
>> the proposed statement, which is about the development and
>> deployment of technical protocol standards.
>>
>> regards,
>>   john
>>
>




From john-ietf@jck.com  Tue Aug 14 07:11:47 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E550021F855A for <ietf@ietfa.amsl.com>; Tue, 14 Aug 2012 07:11:47 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id crPdjcWxckdF for <ietf@ietfa.amsl.com>; Tue, 14 Aug 2012 07:11:47 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 63D4721F8548 for <ietf@ietf.org>; Tue, 14 Aug 2012 07:11:47 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1T1HkM-000Izl-MD; Tue, 14 Aug 2012 10:05:26 -0400
Date: Tue, 14 Aug 2012 10:11:33 -0400
From: John C Klensin <john-ietf@jck.com>
To: Eric Burger <eburger-l@standardstrack.com>, IETF list <ietf@ietf.org>
Subject: Re: [iucg] Last Call: Modern Global Standards Paradigm
Message-ID: <CB2AB8CF39768723422CB12E@JcK-HP8200.jck.com>
In-Reply-To: <E521F97C-24C8-4D2E-9471-844FCD69212C@standardstrack.com>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <CAMm+Lwio8=EyW-=LZE8BA4=6N=H4f7a1Nycg25LxB920ceZ6JA@mail.gmail.com> <1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.com> <276B7D303A96E840D2F95107@JcK-HP8200.jck.com> <CAMm+LwjL=tnYrtmHkV+=+VeOCo+1PjAu+pW0LnUyHYhVX_pPZA@mail.gmail.com> <C01C22690CE178AF8C2E52F7@JcK-HP8200.jck.com> <20120813012310.9F01A21F861E@ietfa.amsl.com> <5028C4C8.40508@tana.it> <F2E0F8B862341F3DC407A2DA@JcK-HP8200.jck.com> <E521F97C-24C8-4D2E-9471-844FCD69212C@standardstrack.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Aug 2012 14:11:48 -0000

--On Monday, August 13, 2012 22:26 -0400 Eric Burger
<eburger-l@standardstrack.com> wrote:

> +1. The ITU is not evil. It just is not the right place for
> Internet standards development. As John points out, there are
> potential uses of the ITU-T for good.

Eric,

I'd narrow your first statement further and say "Internet
technical standards development" or "Internet protocol standards
development".  There are, at least potentially, other
categories.  Those at least mostly fall outside the IETF's scope
and there may well be useful work for the ITU to do in some of
them.  

I find it interesting that ISO and many of their Member Bodies
(including, fwiw, ANSI) make a careful distinction between
standards that have direct bearing on safety issues and other
types... and use different approval criteria for the former.
The IETF doesn't do safety standards (emergency reporting is
really not in that category) and I'm not quite sure what a
safety standard at the IP layer or above would look like (I can
imagine some at physical layer, but we don't do those either).
If there were such a thing as a safety standard involving
communications technology, I could imagine an ITU role there
(although I can't think of any examples for which ISO/IEC JTC1
would not be more appropriate).

I don't see that as contradicting the proposed statement in any
way although, if we had more opportunity to quibble about
wording, I might think some fine-tuning was in order.

    john





From gtw@gtwassociates.com  Tue Aug 14 07:45:53 2012
Return-Path: <gtw@gtwassociates.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F11121F86A7; Tue, 14 Aug 2012 07:45:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.013
X-Spam-Level: **
X-Spam-Status: No, score=2.013 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FAKE_REPLY_C=2.012]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ws-pXleKlteZ; Tue, 14 Aug 2012 07:45:52 -0700 (PDT)
Received: from mail3.primary.net (mail3.primary.net [216.87.38.220]) by ietfa.amsl.com (Postfix) with ESMTP id D337421F85CC; Tue, 14 Aug 2012 07:45:51 -0700 (PDT)
Received: from 75-139-112-230.dhcp.mant.nc.charter.com ([75.139.112.230]:2331 helo=gtw8608f024389) by mail3.primary.net with esmtpa (Exim 4.63) (envelope-from <gtw@gtwassociates.com>) id 1T1INM-0003LQ-9r; Tue, 14 Aug 2012 09:45:51 -0500
Message-ID: <21A5CBA6FA054692B87DDE26D650A7F2@gtw8608f024389>
From: "GTW" <gtw@gtwassociates.com>
To: "IETF" <ietf@ietf.org>, "IAB" <iab@iab.org>, "IETF-Announce" <ietf-announce@ietf.org>
Subject: Re: Last Call: Modern Global Standards Paradigm
Date: Tue, 14 Aug 2012 10:45:43 -0400
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
X-ACL-Warn: X-The email account used to send this email was: gtw@gtwassociates.com
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: GTW <gtw@gtwassociates.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, 14 Aug 2012 14:45:53 -0000

another thought  for longer term considerataion ... the IETF may contemplate 
affirming the WTO principles for The Development Of International Standards 
(for interest also is the ANSI "Key Issues Impacting Global Standardization 
and Conformance: Today and Tomorrow" 
http://publicaa.ansi.org/sites/apdl/Documents/Standards%20Activities/Critical%20Issues/Key_Issues_Impacting_Global_Standardization_and_Conformance.pdf ) 
There is much overlap between the elements of the Modern Global standards 
paradigm and the WTO principles

Indeed a case might be made that  by some that while ITU itself is 
considered to be an international standards organizations it is in fact 
overstepping the coherence principle below


A.                 Decision Of The Committee On Principles For The 
Development Of International Standards, Guides And Recommendations With 
Relation To Articles 2, 5 And Annex 3 Of The Agreement
Decision[1]



1.                   The following principles and procedures should be 
observed, when international standards, guides and recommendations (as 
mentioned under Articles 2, 5 and Annex 3 of the TBT Agreement for the 
preparation of mandatory technical regulations, conformity assessment 
procedures and voluntary standards) are elaborated, to ensure transparency, 
openness, impartiality and consensus, effectiveness and relevance, 
coherence, and to address the concerns of developing countries.

2.                   The same principles should also be observed when 
technical work or a part of the international standard development is 
delegated under agreements or contracts by international standardizing 
bodies to other relevant organizations, including regional bodies.

1.                  Transparency
3.                   All essential information regarding current work 
programmes, as well as on proposals for standards, guides and 
recommendations under consideration and on the final results should be made 
easily accessible to at least all interested parties in the territories of 
at least all WTO Members.  Procedures should be established so that adequate 
time and opportunities are provided for written comments.  The information 
on these procedures should be effectively disseminated.

4.                   In providing the essential information,  the 
transparency procedures should, at a minimum, include:

(a)               the publication of a notice at an early appropriate stage, 
in such a manner as to enable interested parties to become acquainted with 
it, that the international standardizing body proposes to develop a 
particular standard;

(b)               the notification or other communication through 
established mechanisms to members of the international standardizing body, 
providing a brief description of the scope of the draft standard, including 
its objective and rationale.  Such communications shall take place at an 
early appropriate stage, when amendments can still be introduced and 
comments taken into account;

(c)               upon request, the prompt provision to members of the 
international standardizing body of the text of the draft standard;

(d)               the provision of an adequate period of time for interested 
parties in the territory of at least all members of the international 
standardizing body to make comments in writing and take these written 
comments into account in the further consideration of the standard;

(e)               the prompt publication of a standard upon adoption;  and

(f)                to publish periodically a work programme containing 
information on the standards currently being prepared and adopted.

5.                   It is recognized that the publication and communication 
of notices, notifications, draft standards, comments, adopted standards or 
work programmes electronically, via the Internet, where feasible, can 
provide a useful means of ensuring the timely provision of information.  At 
the same time, it is also recognized that the requisite technical means may 
not be available in some cases, particularly with regard to developing 
countries.  Accordingly, it is important that procedures are in place to 
enable hard copies of such documents to be made available upon request.

2.                  Openness
6.                   Membership of an international standardizing body 
should be open on a non-discriminatory basis to relevant bodies of at least 
all WTO Members.  This would include openness without discrimination with 
respect to the participation at the policy development level and at every 
stage of standards development, such as the:

(a)               proposal and acceptance of new work items;

(b)               technical discussion on proposals;

(c)               submission of comments on drafts in order that they can be 
taken into account;

(d)               reviewing existing standards;

(e)               voting and adoption of standards;  and

(f)                dissemination of the adopted standards.

7.                   Any interested member of the international 
standardizing body, including especially developing country Members, with an 
interest in a specific standardization activity should be provided with 
meaningful opportunities to participate at all stages of standard 
development.  It is noted that with respect to standardizing bodies within 
the territory of a WTO Member that have accepted the Code of Good Practice 
for the Preparation, Adoption and Application of Standards by Standardizing 
Bodies (Annex 3 of the TBT Agreement) participation in a particular 
international standardization activity takes place, wherever possible, 
through one delegation representing all standardizing bodies in the 
territory that have adopted, or expected to adopt, standards for the 
subject-matter to which the international standardization activity relates. 
This is illustrative of the importance of participation in the international 
standardizing process accommodating all relevant interests.

3.                  Impartiality and Consensus
8.                   All relevant bodies of WTO Members should be provided 
with meaningful opportunities to contribute to the elaboration of an 
international standard so that the standard development process will not 
give privilege to, or favour the interests of, a particular supplier/s, 
country/ies or region/s. Consensus procedures should be established that 
seek to take into account the views of all parties concerned and to 
reconcile any conflicting arguments.

9.                   Impartiality should be accorded throughout all the 
standards development process with respect to, among other things:

(a)               access to participation in work;

(b)               submission of comments on drafts;

(c)               consideration of views expressed and comments made;

(d)               decision-making through consensus;

(e)               obtaining of information and documents;

(f)                dissemination of the international standard;

(g)               fees charged for documents;

(h)               right to transpose the international standard into a 
regional or national standard;  and

(i)                 revision of the international standard.

4.                  Effectiveness and Relevance
10.               In order to serve the interests of the WTO membership in 
facilitating international trade and preventing unnecessary trade barriers, 
international standards need to be relevant and to effectively respond to 
regulatory and market needs, as well as scientific and technological 
developments in various countries.  They should not distort the global 
market, have adverse effects on fair competition, or stifle innovation and 
technological development.  In addition, they should not give preference to 
the characteristics or requirements of specific countries or regions when 
different needs or interests exist in other countries or regions.  Whenever 
possible, international standards should be performance based rather than 
based on design or descriptive characteristics.

11.               Accordingly, it is important that international 
standardizing bodies:

(a)               take account of relevant regulatory or market needs, as 
feasible and appropriate, as well as scientific and technological 
developments in the elaboration of standards;

(b)               put in place procedures aimed at identifying and reviewing 
standards that have become obsolete, inappropriate or ineffective for 
various reasons;  and

(c)               put in place procedures aimed at improving communication 
with the World Trade Organization.

5.                  Coherence
12.               In order to avoid the development of conflicting 
international standards, it is important that international standardizing 
bodies avoid duplication of, or overlap with, the work of other 
international standardizing bodies.  In this respect, cooperation and 
coordination with other relevant international bodies is essential.

6.                  Development Dimension
13.               Constraints on developing countries, in particular, to 
effectively participate in standards development, should be taken into 
consideration in the standards development process.  Tangible ways of 
facilitating developing countries' participation in international standards 
development should be sought.  The impartiality and openness of any 
international standardization process requires that developing countries are 
not excluded de facto from the process.  With respect to improving 
participation by developing countries, it may be appropriate to use 
technical assistance, in line with Article 11 of the TBT Agreement. 
Provisions for capacity building and technical assistance within 
international standardizing bodies are important in this context.



--------------------------------------------------------------------------------

[1] G/TBT/9, 13 November 2000, para. 20 and Annex 4.


George T. Willingmyre, P.E.
www.gtwassociates.com
301 421 4138
----- Original Message ----- 
From: "GTW" <gtw@gtwassociates.com>
To: "IETF" <ietf@ietf.org>; "IAB" <iab@iab.org>; "IETF-Announce" 
<ietf-announce@ietf.org>
Cc: "IAB" <iab@iab.org>; "IETF" <ietf@ietf.org>
Sent: Saturday, August 11, 2012 10:45 AM
Subject: Re: Last Call: Modern Global Standards Paradigm


>I support the thrust of the "Modern Global Standards Paradigm"  It is 
>particularly timely  as the US formally prepares for meetings of the ITU 
>and CITEL and there are some aspirations from some members and staff at ITU 
>inconsistent with the market based approach to standards setting the 
>document embraces.  I support IETF Chair and the IAB Chair signing such a 
>document.
>
> While I am content with the wording of the section on IP  this text  is 
> nevertheless imprecise.
>
> clip from 
> http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf
>
> 4. Availability. Standards specifications are made accessible to all for
>
> implementation and deployment. Affirming standards organizations have 
> defined
>
> procedures to develop specifications that can be implemented under fair 
> terms.
>
> Given market diversity, fair terms may vary from royalty-free (especially 
> where
>
> open source is commonplace) to fair, reasonable, and non-discriminatory 
> terms
>
> (FRAND).
>
>
>
> end clip
>
> If there were time for tweaking it would be helpful.  What are time 
> constraints?   The first sentence  seems to be describing the availability 
> of specifications to users ... this is the issue of copyrights and fees 
> charged for copies of standards.  Specifications have to be available to 
> users under reasonable terms but not necessarily for free.  But the words 
> are not clear that is what is being addressed. The second sentence seems 
> to describe that   licenses to practice essential patent claims related to 
> a standards  are available under "fair terms"  However the global patent 
> policy concept generally is  that such licenses should be available under 
> "reasonable and non discriminatory" terms.   The single  term 
> "reasonable and non discriminatory" covers  the situation where there may 
> be a "fee" involved or not.  There may be  non fee based terms in what 
> other wise be called "royalty free" licenses It is not that RAND and FRAND 
> are different from "royalty free" It is that "royalty free"  falls under 
> the overall condition of  fair, reasonable, and non-discriminatory term 
> when there may be non royalty terms involved.  Sometimes the "royalty 
> free" situation is described as  "RAND(0)"   I   am also curious about the 
> IETF experience with its patent policy.  What is further background  to 
> the statement that "often our IPR terms at  IETF end up being much worse 
> than that."  The comments below that the paragraph does not  accurately 
> describe the IETF experience are worrisome.
>
> clip from 
> http://www.ietf.org/proceedings/84/minutes/minutes-84-iesg-opsplenary
>
> Cullen Jennings: I was just noting that the IPR terms vary from RF to
> FRAND. I wish that was true. But I think that often our IPR terms at
> IETF end up being much worse than that.
>
> Russ: Understand.
>
> Leslie Daigle: I wanted just to help you out a bit by popping up a
> level and giving the broader context of this whole statement. You have
> alluded to the fact that it was born from discussions with a number of
> organizations. Everyone should appreciate that Russ is presenting today
> something that he thinks is viable for the IETF. The challenge has been
> that indeed the words have been discussed extensively for a period of
> time and there was fairly wide divergence exactly on the point that
> Cullen just mentioned. Have been seeking terminology that says something
> positive about how to do things, and also encompasses a broad range of
> ways that different organizations do things. We are very different from
> the WC3, which is very different from the IEEE. But we are trying to
> capture things that are positive, constructive, new -- as compared to
> the establishment, if you will, of the SDO world. So that has been the
> challenge. Having input from people in terms of support or not is
> probably quite useful. The document -- and I will personally take
> responsibility for some of this -- is not in the best English ever. So,
> some of the comments on it would be better if it were written this way,
> you'll get a polite smile and a nod, and we will take that into
> consideration in the next iteration. So, just by way of context, it is
> a joint effort, and I hope we are capturing something useful that
> expresses something the community believes in. Because personally, I
> think the really novel thing is to stand up and say, there are formal
> standards development organization in the world, and there are other
> organizations that get together and are doing something that is
> slightly different, being driven by different motivations. We are
> seeking technical excellence, are dedicated to being open, are
> dedicated to providing standards that will be built by industry. And
> that isn't an immature form. We are hoping not to grow up into the
> more traditional form. We are trying to make a statement so that more
> people understand that this is a real thing, and that it is valuable.
>
> Scott Bradner: I made some comments on this document to the authors. I
> think it is a very important thing to say, for the reasons that Leslie
> just described. But I do worry that it has to be accurate. And I do
> believe that the specific text of the IPR section is not accurate, when
> it comes to the IETF. And could be used against us because it is not
> what we do.
>
> Russ: Thank you, and I can tell you that those words are still under
> discussion. The concerns that Cullen any you raised are representative
> of a comment that I have already shared with the people trying to put
> this to together
>
> end clip
>
> George T. Willingmyre, P.E.
> www.gtwassociates.com
> 301 421 4138
> ----- Original Message ----- 
> From: "IETF Chair" <chair@ietf.org>
> To: "IETF-Announce" <ietf-announce@ietf.org>
> Cc: "IAB" <iab@iab.org>; "IETF" <ietf@ietf.org>
> Sent: Friday, August 10, 2012 11:19 AM
> Subject: Last Call: Modern Global Standards Paradigm
>
>
>>
>> The IETF Chair and the IAB Chair intend to sign the Affirmation
>> of the Modern Global Standards Paradigm, which can be found
>> here:
>>
>> http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf
>>
>> An earlier version was discussed in plenary, and the IAB Chair called
>> for comments on the IETF mail list.  This version includes changes
>> that address those comments.
>>
>> Th IETF 84 Administrative plenary minutes have been posted, so that
>> discussion can be reviewed if desired.  The minutes are here:
>>
>> http://www.ietf.org/proceedings/84/minutes/minutes-84-iesg-opsplenary
>>
>> On 8 August 2012, the IEEE Standards Association Board of Governors
>> approved this version of the document.  The approval process is
>> underway at the W3C as well.
>>
>> The IETF Chair and the IAB Chair intend to sign the Affirmation in the
>> next few weeks. Please send strong objections to the iab@iab.org
>> and the ietf@ietf.org mailing lists by 2012-08-24.
>>
>> Thank you,
>>  Russ Housley
>>  IETF Chair
>>
> 


From philip.eardley@bt.com  Mon Aug 13 07:14:09 2012
Return-Path: <philip.eardley@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 4A54F21F8766; Mon, 13 Aug 2012 07:14:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.167
X-Spam-Level: 
X-Spam-Status: No, score=-102.167 tagged_above=-999 required=5 tests=[AWL=-0.868, BAYES_00=-2.599, MANGLED_LIST=2.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0YmuNEPYbjRi; Mon, 13 Aug 2012 07:14:08 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp62.intersmtp.com [62.239.224.235]) by ietfa.amsl.com (Postfix) with ESMTP id 7528F21F8760; Mon, 13 Aug 2012 07:14:08 -0700 (PDT)
Received: from EVMHT64-UKRD.domain1.systemhost.net (10.36.3.101) by RDW083A006ED62.smtp-e2.hygiene.service (10.187.98.11) with Microsoft SMTP Server (TLS) id 8.3.264.0; Mon, 13 Aug 2012 15:14:06 +0100
Received: from EMV65-UKRD.domain1.systemhost.net ([169.254.1.58]) by EVMHT64-UKRD.domain1.systemhost.net ([10.36.3.101]) with mapi; Mon, 13 Aug 2012 15:14:06 +0100
From: <philip.eardley@bt.com>
To: <ben@nostrum.com>, <draft-ietf-mptcp-api.all@tools.ietf.org>
Date: Mon, 13 Aug 2012 15:14:06 +0100
Subject: RE: Gen-ART LC Review of draft-ietf-mptcp-api-05
Thread-Topic: Gen-ART LC Review of draft-ietf-mptcp-api-05
Thread-Index: Ac13LsLUMm/ZireBRPufxalExn9KDgCD0gwA
Message-ID: <9510D26531EF184D9017DF24659BB87F33D6B96847@EMV65-UKRD.domain1.systemhost.net>
References: <CCBAA297-B839-4AEA-BB24-F4D320200415@nostrum.com>
In-Reply-To: <CCBAA297-B839-4AEA-BB24-F4D320200415@nostrum.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: Tue, 14 Aug 2012 11:12:00 -0700
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 14:14:09 -0000

Ben,
Thanks for your review.=20

The right status isn't clear-cut (I think), but when we (Chairs & Wes) disc=
ussed it, Info seemed best
* mainly because precedent seems to be that API docs are informational, for=
 example socket API extensions for SCTP http://datatracker.ietf.org/doc/rfc=
6458/ =20
* also the doc has two main parts - looking at the impact that MPTCP may ha=
ve on application performance - and describing a basic API for MPTCP-aware =
applications. The first part seems clearly Informational. So if the API par=
t is not Info, there is the effort of splitting the doc. Pragmatically I th=
ink this should only be done if clearly needed.

I'm afraid I don't know case history of how the IETF tries to extend non-IE=
TF standards.

On the status of Posix reference, which appears twice in the doc
>> The abstract specification is in line with the
   Posix standard [17] as much as possible
>> One commonly used TCP socket option (TCP_NODELAY) disables the Nagle
   algorithm as described in [2].  This option is also specified in the
   Posix standard [17]. =20

The guidance:
>> Normative references specify documents that must be read to understand o=
r implement the technology in the new RFC, or whose technology must be pres=
ent for the technology in the new RFC to work.

On its second appearance, I think [17] is definitely being used informative=
ly.
The first appearance is less clear  cut, I think. Am inclined to say this i=
s still informative - it's just explaining the style adopted for the abstra=
ct specification (if [17] changed then it wouldn't be necessary to change t=
his doc).

Thanks also for the nits

Best wishes
phil



-----Original Message-----
From: Ben Campbell [mailto:ben@nostrum.com]=20
Sent: 10 August 2012 20:31
To: draft-ietf-mptcp-api.all@tools.ietf.org
Cc: General Area Review Team; IETF Discussion List
Subject: Gen-ART LC Review of draft-ietf-mptcp-api-05

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq> .

Please resolve these comments along with any other Last Call comments
you may receive.

Document:  draft-ietf-mptcp-api-05

Reviewer: Ben Campbell
Review Date: 2012-08-10
IETF LC End Date: 2012-08-14

Summary: This draft is almost ready for publication, but I have questions a=
bout its intended informational status.

Major issues: None

Minor issues:

-- Section 5 specifies an abstract "basic" API for MPTCP. The draft charact=
erizes this as an extension to the sockets API. On it's face, this sounds l=
ike it's creating a standard, or will at least have the effect of creating =
a standard. Is that the intent? If so, I wonder why the intended status is =
informational rather than standards track? If not, it would be useful to ex=
plicitly state the intent. (For example, is this intended as an input to in=
form a standardization effort?)

I realize that the sockets API is not an IETF standard. I don't know if tha=
t is part of the reason for making this draft informational, nor am I famil=
iar with precedent for extending non-IETF-native standards. But at the risk=
 of attacking a straw man, I am concerned that putting something that could=
 be interpreted as a "standard" in an informational RFC might not be the be=
st practice for solving that sort of process issue.


-- It seems like at least passing knowledge of the sockets API is needed to=
 understand this document. I'm curious why the POSIX reference is informati=
onal rather than normative?

Nits/editorial comments:

-- 3.3.1, 1st paragraph: "This will provide greater bandwidth for an applic=
ation. "

I assume this means "as great or greater", given the previous statements th=
at MPTCP should be at worst no worse than normal TCP?

-- 3.2.1, 1st paragraph: "...while having TCP SYN/ACK ready to reply to..."

I had to think about this a while to figure out the meaning. Perhaps it cou=
ld be rephrased?

From jdrake@juniper.net  Tue Aug 14 15:03:42 2012
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 01C9921E80BB for <ietf@ietfa.amsl.com>; Tue, 14 Aug 2012 15:03:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.202
X-Spam-Level: 
X-Spam-Status: No, score=-5.202 tagged_above=-999 required=5 tests=[AWL=1.396,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0UxB1xJC3bnC for <ietf@ietfa.amsl.com>; Tue, 14 Aug 2012 15:03:41 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id ECF7821E80BA for <ietf@ietf.org>; Tue, 14 Aug 2012 15:03:40 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKUCrLPM/HrcrVCVEph5qWslA+AQBVYXJ0@postini.com; Tue, 14 Aug 2012 15:03:40 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; Tue, 14 Aug 2012 15:03:39 -0700
From: John E Drake <jdrake@juniper.net>
To: "iab@iab.org" <iab@iab.org>
Date: Tue, 14 Aug 2012 15:03:38 -0700
Subject: FW: Affirmation of the Modern Global Standards Paradigm
Thread-Topic: Affirmation of the Modern Global Standards Paradigm
Thread-Index: Ac1wVS3rrwWGj8fZTeOY28S54inwAwKE0BTw
Message-ID: <5E893DB832F57341992548CDBB333163A5A9B462FF@EMBX01-HQ.jnpr.net>
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_5E893DB832F57341992548CDBB333163A5A9B462FFEMBX01HQjnprn_"
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, 14 Aug 2012 22:03:42 -0000

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

Hi,

Does this document actually have a purpose, and if so, what is it?

Thanks,

John

Sent from my iPhone

From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org=
] On Behalf Of IAB Chair
Sent: Wednesday, August 01, 2012 7:19 PM
To: ietf-announce@ietf.org
Subject: Affirmation of the Modern Global Standards Paradigm

The IAB, IESG, IEEE-SA and W3C have been developing an "Affirmation of the =
Modern Global Standards Paradigm"<http://www.ietf.org/proceedings/84/slides=
/slides-84-iesg-opsplenary-4.pdf>.  Comments may be sent to iab@iab.org<mai=
lto:iab@iab.org>.

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 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: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;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
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><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'c=
olor:#1F497D'>Hi,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'=
color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=
=3D'color:#1F497D'>Does this document actually have a purpose, and if so, w=
hat is it?<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'color:#=
1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'col=
or:#1F497D'>Thanks,<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span s=
tyle=3D'color:#1F497D'>John<o:p></o:p></span></p><p class=3DMsoNormal><span=
 style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><p class=3DMsoNor=
mal><span style=3D'color:#1F497D'>Sent from my iPhone<o:p></o:p></span></p>=
</div><p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p><=
/span></p><div><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;pad=
ding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'font-size:10=
.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font=
-size:10.0pt;font-family:"Tahoma","sans-serif"'> ietf-announce-bounces@ietf=
.org [mailto:ietf-announce-bounces@ietf.org] <b>On Behalf Of </b>IAB Chair<=
br><b>Sent:</b> Wednesday, August 01, 2012 7:19 PM<br><b>To:</b> ietf-annou=
nce@ietf.org<br><b>Subject:</b> Affirmation of the Modern Global Standards =
Paradigm<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;<=
/o:p></p><p class=3DMsoNormal>The IAB, IESG, IEEE-SA and W3C have been deve=
loping an <a href=3D"http://www.ietf.org/proceedings/84/slides/slides-84-ie=
sg-opsplenary-4.pdf" title=3DModern-Global-Standards-Paradigm>&#8220;Affirm=
ation of the Modern Global Standards Paradigm&#8221;</a>.&nbsp; Comments ma=
y be sent to <a href=3D"mailto:iab@iab.org" title=3D"Affirmation of the Mod=
ern Global Standards Paradigm">iab@iab.org</a>.<o:p></o:p></p></div></body>=
</html>=

--_000_5E893DB832F57341992548CDBB333163A5A9B462FFEMBX01HQjnprn_--

From lear@cisco.com  Tue Aug 14 23:25:05 2012
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 0139F21F8697 for <ietf@ietfa.amsl.com>; Tue, 14 Aug 2012 23:25:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.515
X-Spam-Level: 
X-Spam-Status: No, score=-110.515 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bZUoRjn5-qn6 for <ietf@ietfa.amsl.com>; Tue, 14 Aug 2012 23:25:04 -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 C7FB521F8687 for <ietf@ietf.org>; Tue, 14 Aug 2012 23:25:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=3568; q=dns/txt; s=iport; t=1345011904; x=1346221504; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=mDfozbuY7DTPRkpGEmZMnbpEMcUWxkYxgoGNxOxN2QE=; b=eoAsCbi9ZsVXebM0IYkeeJpdD2CBvv5VVRw5chvhW87MTN29NI9TbpNR HE8uC72DN3utOtubbmUy4nuTXx8E4UwOOmqQU3Lewd6Uba7FXlja9gWGQ cYs1CUiDFzPWwLw68ReYKurNm7K0LF7R6VxWYxhXIG5DROI1yYI3Kt7s/ A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAGFAK1CQ/khR/2dsb2JhbABFgkqDN7QrgQeCIAEBAQQSARAKSwEQCwQUCQMTCwICCQMCAQIBPAkGDQEHAQEeh2uYW40ZkzyQS4ESA5VLjiqBZoJh
X-IronPort-AV: E=Sophos;i="4.77,771,1336348800";  d="scan'208,217";a="142429499"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-1.cisco.com with ESMTP; 15 Aug 2012 06:24:56 +0000
Received: from dhcp-10-55-89-242.cisco.com (dhcp-10-55-89-242.cisco.com [10.55.89.242]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q7F6Oted002687 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Aug 2012 06:24:55 GMT
Message-ID: <502B40B7.8050100@cisco.com>
Date: Wed, 15 Aug 2012 08:24:55 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: John E Drake <jdrake@juniper.net>
Subject: Re: FW: Affirmation of the Modern Global Standards Paradigm
References: <5E893DB832F57341992548CDBB333163A5A9B462FF@EMBX01-HQ.jnpr.net>
In-Reply-To: <5E893DB832F57341992548CDBB333163A5A9B462FF@EMBX01-HQ.jnpr.net>
X-Enigmail-Version: 1.4.3
Content-Type: multipart/alternative; boundary="------------010503070409010700060108"
Cc: "iab@iab.org" <iab@iab.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, 15 Aug 2012 06:25:05 -0000

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

John,


On 8/15/12 12:03 AM, John E Drake wrote:
>
> Hi,
>
>  
>
> Does this document actually have a purpose, and if so, what is it?
>
>  
>
>

To me (and I speak only for me here), the purpose of this document is to
articulate principles that have made the Internet a success.  It is a
means to invite others to subscribe to those same principles, and there
are many standards organizations that do not.  Customers and society can
demand better, and this is an avenue for that.

Eliot

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

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    John,<br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 8/15/12 12:03 AM, John E Drake
      wrote:<br>
    </div>
    <blockquote
      cite="mid:5E893DB832F57341992548CDBB333163A5A9B462FF@EMBX01-HQ.jnpr.net"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <meta name="Generator" content="Microsoft Word 12 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family: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: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;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
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="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span style="color:#1F497D">Hi,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p>Â </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Does this
            document actually have a purpose, and if so, what is it?<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p>Â </o:p></span></p>
        <br>
      </div>
    </blockquote>
    <br>
    To me (and I speak only for me here), the purpose of this document
    is to articulate principles that have made the Internet a success.Â 
    It is a means to invite others to subscribe to those same
    principles, and there are many standards organizations that do not.Â 
    Customers and society can demand better, and this is an avenue for
    that.<br>
    <br>
    Eliot<br>
  </body>
</html>

--------------010503070409010700060108--

From brian.e.carpenter@gmail.com  Tue Aug 14 23:59:56 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0921411E80D7 for <ietf@ietfa.amsl.com>; Tue, 14 Aug 2012 23:59:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.501
X-Spam-Level: 
X-Spam-Status: No, score=-101.501 tagged_above=-999 required=5 tests=[AWL=0.190, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eaM0ZaGEOOex for <ietf@ietfa.amsl.com>; Tue, 14 Aug 2012 23:59:55 -0700 (PDT)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3F26211E80D1 for <ietf@ietf.org>; Tue, 14 Aug 2012 23:59:55 -0700 (PDT)
Received: by wicr5 with SMTP id r5so3480547wic.13 for <ietf@ietf.org>; Tue, 14 Aug 2012 23:59:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=sAkHyH04sBtiK57LQ1vgrFFSkwJuhcdxh6K6jo3fEWQ=; b=fOJ7HUZPUjhDF/T/gScal762JiUeS5JnsWjfF9Y73gGFRceY7f/uifHNV7Y/V726vl oj8WZIeI8dy1LEFThuzuR+/cccuuaqEG1CMUDXOhixsajE0WkttdLthFjYhuLJO7f5g7 Q/5n/knhrLU/811RiAZxmFa40oH77sB89wgRUlG96622qw0JkgNSWH8aM0fR/LGKaSuq xkYWh9Mur6EuhGgjQ+MZx+epWJV6AGabiwXUivrmjlkNqeWmV+TzNb91wtUWSJIu31Jj 6M5+twxcpVSNeP4crM/K5NpxH5HJwENiWjM3A7HjxD1uhT7EQq3oA8C25RK5ZS1Zxx8s mX+Q==
Received: by 10.180.99.196 with SMTP id es4mr34595069wib.18.1345013994327; Tue, 14 Aug 2012 23:59:54 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-218-63.as13285.net. [2.102.218.63]) by mx.google.com with ESMTPS id fb20sm2072933wid.1.2012.08.14.23.59.51 (version=SSLv3 cipher=OTHER); Tue, 14 Aug 2012 23:59:53 -0700 (PDT)
Message-ID: <502B48E8.7060104@gmail.com>
Date: Wed, 15 Aug 2012 07:59:52 +0100
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: Eliot Lear <lear@cisco.com>
Subject: Re: FW: Affirmation of the Modern Global Standards Paradigm
References: <5E893DB832F57341992548CDBB333163A5A9B462FF@EMBX01-HQ.jnpr.net> <502B40B7.8050100@cisco.com>
In-Reply-To: <502B40B7.8050100@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "iab@iab.org" <iab@iab.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, 15 Aug 2012 06:59:56 -0000

On 15/08/2012 07:24, Eliot Lear wrote:
> John,
> 
> On 8/15/12 12:03 AM, John E Drake wrote:
>> Hi,
>>
>> Does this document actually have a purpose, and if so, what is it?
>>
> 
> To me (and I speak only for me here), the purpose of this document is to
> articulate principles that have made the Internet a success.  It is a
> means to invite others to subscribe to those same principles, and there
> are many standards organizations that do not.  Customers and society can
> demand better, and this is an avenue for that.

I take it that John's question is really *why* do these principles need to
be articulated in public. Perhaps the IAB should answer that, but my answer
is: because there is a real danger of some SDOs, including but not limited
to the ITU-T, breaking them for a variety of commercial or political reasons.

   Brian

From jdrake@juniper.net  Wed Aug 15 05:19:30 2012
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 7B09E21F87C5 for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 05:19:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.267
X-Spam-Level: 
X-Spam-Status: No, score=-5.267 tagged_above=-999 required=5 tests=[AWL=1.332,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2kd5PltvdCIb for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 05:19:30 -0700 (PDT)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by ietfa.amsl.com (Postfix) with ESMTP id BA0CA21F87C1 for <ietf@ietf.org>; Wed, 15 Aug 2012 05:19:29 -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 DSNKUCuTz8an30iCmU8bIfayp92lf9L8pEj9@postini.com; Wed, 15 Aug 2012 05:19:29 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB03-HQ.jnpr.net ([::1]) with mapi; Wed, 15 Aug 2012 05:16:59 -0700
From: John E Drake <jdrake@juniper.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Eliot Lear <lear@cisco.com>
Date: Wed, 15 Aug 2012 05:16:59 -0700
Subject: RE: FW: Affirmation of the Modern Global Standards Paradigm
Thread-Topic: FW: Affirmation of the Modern Global Standards Paradigm
Thread-Index: Ac16s5P/Bc7dLb+dShW73OlCN9lnpwALBSEQ
Message-ID: <5E893DB832F57341992548CDBB333163A5A9B46658@EMBX01-HQ.jnpr.net>
References: <5E893DB832F57341992548CDBB333163A5A9B462FF@EMBX01-HQ.jnpr.net> <502B40B7.8050100@cisco.com> <502B48E8.7060104@gmail.com>
In-Reply-To: <502B48E8.7060104@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: "iab@iab.org" <iab@iab.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, 15 Aug 2012 12:19:30 -0000

Q29tbWVudCBpbmxpbmUNCg0KU2VudCBmcm9tIG15IGlQaG9uZQ0KDQo+IC0tLS0tT3JpZ2luYWwg
TWVzc2FnZS0tLS0tDQo+IEZyb206IEJyaWFuIEUgQ2FycGVudGVyIFttYWlsdG86YnJpYW4uZS5j
YXJwZW50ZXJAZ21haWwuY29tXQ0KPiBTZW50OiBXZWRuZXNkYXksIEF1Z3VzdCAxNSwgMjAxMiAx
MjowMCBBTQ0KPiBUbzogRWxpb3QgTGVhcg0KPiBDYzogSm9obiBFIERyYWtlOyBpYWJAaWFiLm9y
ZzsgaWV0ZkBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogRlc6IEFmZmlybWF0aW9uIG9mIHRoZSBN
b2Rlcm4gR2xvYmFsIFN0YW5kYXJkcyBQYXJhZGlnbQ0KPiANCj4gT24gMTUvMDgvMjAxMiAwNzoy
NCwgRWxpb3QgTGVhciB3cm90ZToNCj4gPiBKb2huLA0KPiA+DQo+ID4gT24gOC8xNS8xMiAxMjow
MyBBTSwgSm9obiBFIERyYWtlIHdyb3RlOg0KPiA+PiBIaSwNCj4gPj4NCj4gPj4gRG9lcyB0aGlz
IGRvY3VtZW50IGFjdHVhbGx5IGhhdmUgYSBwdXJwb3NlLCBhbmQgaWYgc28sIHdoYXQgaXMgaXQ/
DQo+ID4+DQo+ID4NCj4gPiBUbyBtZSAoYW5kIEkgc3BlYWsgb25seSBmb3IgbWUgaGVyZSksIHRo
ZSBwdXJwb3NlIG9mIHRoaXMgZG9jdW1lbnQgaXMNCj4gPiB0byBhcnRpY3VsYXRlIHByaW5jaXBs
ZXMgdGhhdCBoYXZlIG1hZGUgdGhlIEludGVybmV0IGEgc3VjY2Vzcy4gIEl0DQo+IGlzDQo+ID4g
YSBtZWFucyB0byBpbnZpdGUgb3RoZXJzIHRvIHN1YnNjcmliZSB0byB0aG9zZSBzYW1lIHByaW5j
aXBsZXMsIGFuZA0KPiA+IHRoZXJlIGFyZSBtYW55IHN0YW5kYXJkcyBvcmdhbml6YXRpb25zIHRo
YXQgZG8gbm90LiAgQ3VzdG9tZXJzIGFuZA0KPiA+IHNvY2lldHkgY2FuIGRlbWFuZCBiZXR0ZXIs
IGFuZCB0aGlzIGlzIGFuIGF2ZW51ZSBmb3IgdGhhdC4NCj4gDQo+IEkgdGFrZSBpdCB0aGF0IEpv
aG4ncyBxdWVzdGlvbiBpcyByZWFsbHkgKndoeSogZG8gdGhlc2UgcHJpbmNpcGxlcyBuZWVkDQo+
IHRvIGJlIGFydGljdWxhdGVkIGluIHB1YmxpYy4gUGVyaGFwcyB0aGUgSUFCIHNob3VsZCBhbnN3
ZXIgdGhhdCwgYnV0IG15DQo+IGFuc3dlcg0KPiBpczogYmVjYXVzZSB0aGVyZSBpcyBhIHJlYWwg
ZGFuZ2VyIG9mIHNvbWUgU0RPcywgaW5jbHVkaW5nIGJ1dCBub3QNCj4gbGltaXRlZCB0byB0aGUg
SVRVLVQsIGJyZWFraW5nIHRoZW0gZm9yIGEgdmFyaWV0eSBvZiBjb21tZXJjaWFsIG9yDQo+IHBv
bGl0aWNhbCByZWFzb25zLg0KDQpKRDogIEFuZCBob3cgZG9lcyB0aGlzIGRvY3VtZW50IHByZXZl
bnQgdGhpcyBhYnVzZT8NCiANCj4gDQo+ICAgIEJyaWFuDQo=

From jdrake@juniper.net  Wed Aug 15 05:20:27 2012
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 7F2D421F87C9 for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 05:20:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.326
X-Spam-Level: 
X-Spam-Status: No, score=-5.326 tagged_above=-999 required=5 tests=[AWL=1.272,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B8C+GJlYNDeg for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 05:20:27 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id 623E521F87CB for <ietf@ietf.org>; Wed, 15 Aug 2012 05:20:26 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUCuUCfbk0i5HanABj2xdeN7HWNqQWjjH@postini.com; Wed, 15 Aug 2012 05:20: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; Wed, 15 Aug 2012 05:15:05 -0700
From: John E Drake <jdrake@juniper.net>
To: Eliot Lear <lear@cisco.com>
Date: Wed, 15 Aug 2012 05:15:03 -0700
Subject: RE: FW: Affirmation of the Modern Global Standards Paradigm
Thread-Topic: FW: Affirmation of the Modern Global Standards Paradigm
Thread-Index: Ac16rrVuMvLjPp5LQoqWG6lSwcXDhAAMJNug
Message-ID: <5E893DB832F57341992548CDBB333163A5A9B46657@EMBX01-HQ.jnpr.net>
References: <5E893DB832F57341992548CDBB333163A5A9B462FF@EMBX01-HQ.jnpr.net> <502B40B7.8050100@cisco.com>
In-Reply-To: <502B40B7.8050100@cisco.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_5E893DB832F57341992548CDBB333163A5A9B46657EMBX01HQjnprn_"
MIME-Version: 1.0
Cc: "iab@iab.org" <iab@iab.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, 15 Aug 2012 12:20:27 -0000

--_000_5E893DB832F57341992548CDBB333163A5A9B46657EMBX01HQjnprn_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

DQoNClNlbnQgZnJvbSBteSBpUGhvbmUNCg0KRnJvbTogRWxpb3QgTGVhciBbbWFpbHRvOmxlYXJA
Y2lzY28uY29tXQ0KU2VudDogVHVlc2RheSwgQXVndXN0IDE0LCAyMDEyIDExOjI1IFBNDQpUbzog
Sm9obiBFIERyYWtlDQpDYzogaWFiQGlhYi5vcmc7IGlldGZAaWV0Zi5vcmcNClN1YmplY3Q6IFJl
OiBGVzogQWZmaXJtYXRpb24gb2YgdGhlIE1vZGVybiBHbG9iYWwgU3RhbmRhcmRzIFBhcmFkaWdt
DQoNCkpvaG4sDQoNCk9uIDgvMTUvMTIgMTI6MDMgQU0sIEpvaG4gRSBEcmFrZSB3cm90ZToNCkhp
LA0KDQpEb2VzIHRoaXMgZG9jdW1lbnQgYWN0dWFsbHkgaGF2ZSBhIHB1cnBvc2UsIGFuZCBpZiBz
bywgd2hhdCBpcyBpdD8NCg0KDQoNClRvIG1lIChhbmQgSSBzcGVhayBvbmx5IGZvciBtZSBoZXJl
KSwgdGhlIHB1cnBvc2Ugb2YgdGhpcyBkb2N1bWVudCBpcyB0byBhcnRpY3VsYXRlIHByaW5jaXBs
ZXMgdGhhdCBoYXZlIG1hZGUgdGhlIEludGVybmV0IGEgc3VjY2Vzcy4NCg0KSkQ6ICBUaGlzIHNl
ZW1zIGEgYml0IHByZXN1bXB0dW91cyB0byBtZS4NCg0KSXQgaXMgYSBtZWFucyB0byBpbnZpdGUg
b3RoZXJzIHRvIHN1YnNjcmliZSB0byB0aG9zZSBzYW1lIHByaW5jaXBsZXMsIGFuZCB0aGVyZSBh
cmUgbWFueSBzdGFuZGFyZHMgb3JnYW5pemF0aW9ucyB0aGF0IGRvIG5vdC4NCg0KSkQ6ICBJIHdv
dWxkIGJlIHdpbGxpbmcgdG8gYmV0IHRoYXQgbmVhcmx5IGV2ZXJ5IFNETyB3b3VsZCBjbGFpbSB0
aGV5IGVtYnJhY2UgdGhlc2Ugc2FtZSBwcmluY2lwbGVzLg0KDQpDdXN0b21lcnMgYW5kIHNvY2ll
dHkgY2FuIGRlbWFuZCBiZXR0ZXIsIGFuZCB0aGlzIGlzIGFuIGF2ZW51ZSBmb3IgdGhhdC4NCg0K
SkQ6ICBIb3csIGV4YWN0bHk/DQoNCkVsaW90DQo=

--_000_5E893DB832F57341992548CDBB333163A5A9B46657EMBX01HQjnprn_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij48bWV0YSBuYW1lPUdlbmVyYXRvciBjb250ZW50
PSJNaWNyb3NvZnQgV29yZCAxMiAoZmlsdGVyZWQgbWVkaXVtKSI+PHN0eWxlPjwhLS0NCi8qIEZv
bnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0
aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQt
ZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQt
ZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7DQoJcGFub3NlLTE6MiAxMSA2IDQgMyA1IDQgNCAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0K
CWNvbG9yOmJsYWNrO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnNwYW4u
RW1haWxTdHlsZTE3DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJD
YWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6d2luZG93dGV4dDt9DQpzcGFuLkVtYWlsU3R5
bGUxOA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
InNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTkNCgl7bXNv
LXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5z
LXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10
eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24x
DQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9
DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEt
LVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlk
bWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+
DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0
YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT48L2hlYWQ+PGJvZHkg
Ymdjb2xvcj13aGl0ZSBsYW5nPUVOLVVTIGxpbms9Ymx1ZSB2bGluaz1wdXJwbGU+PGRpdiBjbGFz
cz1Xb3JkU2VjdGlvbjE+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdjb2xvcjojMUY0
OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFu
IHN0eWxlPSdjb2xvcjojMUY0OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PGRpdj48
cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2NvbG9yOiMxRjQ5N0QnPlNlbnQgZnJvbSBt
eSBpUGhvbmU8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PC9kaXY+PHAgY2xhc3M9TXNvTm9ybWFsPjxz
cGFuIHN0eWxlPSdjb2xvcjojMUY0OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PGRp
diBzdHlsZT0nYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5n
OjBpbiAwaW4gMGluIDQuMHB0Jz48ZGl2PjxkaXYgc3R5bGU9J2JvcmRlcjpub25lO2JvcmRlci10
b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluJz48cCBjbGFz
cz1Nc29Ob3JtYWw+PGI+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6
IlRhaG9tYSIsInNhbnMtc2VyaWYiO2NvbG9yOndpbmRvd3RleHQnPkZyb206PC9zcGFuPjwvYj48
c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiVGFob21hIiwic2Fucy1z
ZXJpZiI7Y29sb3I6d2luZG93dGV4dCc+IEVsaW90IExlYXIgW21haWx0bzpsZWFyQGNpc2NvLmNv
bV0gPGJyPjxiPlNlbnQ6PC9iPiBUdWVzZGF5LCBBdWd1c3QgMTQsIDIwMTIgMTE6MjUgUE08YnI+
PGI+VG86PC9iPiBKb2huIEUgRHJha2U8YnI+PGI+Q2M6PC9iPiBpYWJAaWFiLm9yZzsgaWV0ZkBp
ZXRmLm9yZzxicj48Yj5TdWJqZWN0OjwvYj4gUmU6IEZXOiBBZmZpcm1hdGlvbiBvZiB0aGUgTW9k
ZXJuIEdsb2JhbCBTdGFuZGFyZHMgUGFyYWRpZ208bzpwPjwvbzpwPjwvc3Bhbj48L3A+PC9kaXY+
PC9kaXY+PHAgY2xhc3M9TXNvTm9ybWFsPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPjxwIGNsYXNzPU1z
b05vcm1hbCBzdHlsZT0nbWFyZ2luLWJvdHRvbToxMi4wcHQnPkpvaG4sPGJyPjxicj48bzpwPjwv
bzpwPjwvcD48ZGl2PjxwIGNsYXNzPU1zb05vcm1hbD5PbiA4LzE1LzEyIDEyOjAzIEFNLCBKb2hu
IEUgRHJha2Ugd3JvdGU6PG86cD48L286cD48L3A+PC9kaXY+PGJsb2NrcXVvdGUgc3R5bGU9J21h
cmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCc+PHAgY2xhc3M9TXNvTm9ybWFsPjxz
cGFuIHN0eWxlPSdjb2xvcjojMUY0OTdEJz5IaSw8L3NwYW4+PG86cD48L286cD48L3A+PHAgY2xh
c3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdjb2xvcjojMUY0OTdEJz4mbmJzcDs8L3NwYW4+PG86
cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdjb2xvcjojMUY0OTdE
Jz5Eb2VzIHRoaXMgZG9jdW1lbnQgYWN0dWFsbHkgaGF2ZSBhIHB1cnBvc2UsIGFuZCBpZiBzbywg
d2hhdCBpcyBpdD88L3NwYW4+PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFu
IHN0eWxlPSdjb2xvcjojMUY0OTdEJz4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+PHAgY2xh
c3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiJU
aW1lcyBOZXcgUm9tYW4iLCJzZXJpZiInPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48L2Js
b2NrcXVvdGU+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTIuMHB0
O2ZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiInPjxicj5UbyBtZSAoYW5kIEkg
c3BlYWsgb25seSBmb3IgbWUgaGVyZSksIHRoZSBwdXJwb3NlIG9mIHRoaXMgZG9jdW1lbnQgaXMg
dG8gYXJ0aWN1bGF0ZSBwcmluY2lwbGVzIHRoYXQgaGF2ZSBtYWRlIHRoZSBJbnRlcm5ldCBhIHN1
Y2Nlc3MuPC9zcGFuPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiJU
aW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7Y29sb3I6IzFGNDk3RCc+PG86cD48L286cD48L3NwYW4+
PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nY29sb3I6IzFGNDk3RCc+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nY29s
b3I6IzFGNDk3RCc+SkQ6wqAgVGhpcyBzZWVtcyBhIGJpdCBwcmVzdW1wdHVvdXMgdG8gbWUuPG86
cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nY29sb3I6
IzFGNDk3RCc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48
c3BhbiBzdHlsZT0nZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFu
Iiwic2VyaWYiJz5JdCBpcyBhIG1lYW5zIHRvIGludml0ZSBvdGhlcnMgdG8gc3Vic2NyaWJlIHRv
IHRob3NlIHNhbWUgcHJpbmNpcGxlcywgYW5kIHRoZXJlIGFyZSBtYW55IHN0YW5kYXJkcyBvcmdh
bml6YXRpb25zIHRoYXQgZG8gbm90Ljwvc3Bhbj48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEyLjBw
dDtmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYiO2NvbG9yOiMxRjQ5N0QnPjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2NvbG9y
OiMxRjQ5N0QnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+
PHNwYW4gc3R5bGU9J2NvbG9yOiMxRjQ5N0QnPkpEOsKgIEkgd291bGQgYmUgd2lsbGluZyB0byBi
ZXQgdGhhdCBuZWFybHkgZXZlcnkgU0RPIHdvdWxkIGNsYWltIHRoZXkgZW1icmFjZSB0aGVzZSBz
YW1lIHByaW5jaXBsZXMuPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48
c3BhbiBzdHlsZT0nY29sb3I6IzFGNDk3RCc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxw
IGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWls
eToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYiJz5DdXN0b21lcnMgYW5kIHNvY2lldHkgY2FuIGRl
bWFuZCBiZXR0ZXIsIGFuZCB0aGlzIGlzIGFuIGF2ZW51ZSBmb3IgdGhhdC48L3NwYW4+PHNwYW4g
c3R5bGU9J2ZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsInNl
cmlmIjtjb2xvcjojMUY0OTdEJz48bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9y
bWFsPjxzcGFuIHN0eWxlPSdjb2xvcjojMUY0OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdjb2xvcjojMUY0OTdEJz5KRDrCoCBI
b3csIGV4YWN0bHk/PC9zcGFuPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFt
aWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiInPjxicj48YnI+RWxpb3Q8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+PC9kaXY+PC9kaXY+PC9ib2R5PjwvaHRtbD4=

--_000_5E893DB832F57341992548CDBB333163A5A9B46657EMBX01HQjnprn_--

From hannes.tschofenig@gmx.net  Wed Aug 15 05:38:13 2012
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D18421F87D6 for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 05:38:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.608
X-Spam-Level: 
X-Spam-Status: No, score=-102.608 tagged_above=-999 required=5 tests=[AWL=-0.009, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OsIi0mCFDMp6 for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 05:38:13 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id BF46B21F877E for <ietf@ietf.org>; Wed, 15 Aug 2012 05:38:06 -0700 (PDT)
Received: (qmail invoked by alias); 15 Aug 2012 12:38:05 -0000
Received: from a88-115-216-191.elisa-laajakaista.fi (EHLO [192.168.100.105]) [88.115.216.191] by mail.gmx.net (mp024) with SMTP; 15 Aug 2012 14:38:05 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+QC7crsMuQJ5MaMVMPCmtD4hXFzP5zEgsC7UVUHo 3iRPbcL20yIt4x
Subject: Re: Affirmation of the Modern Global Standards Paradigm
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: <5E893DB832F57341992548CDBB333163A5A9B46658@EMBX01-HQ.jnpr.net>
Date: Wed, 15 Aug 2012 15:38:03 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <8972B876-DD01-474E-9234-0133DC9DC119@gmx.net>
References: <5E893DB832F57341992548CDBB333163A5A9B462FF@EMBX01-HQ.jnpr.net> <502B40B7.8050100@cisco.com> <502B48E8.7060104@gmail.com> <5E893DB832F57341992548CDBB333163A5A9B46658@EMBX01-HQ.jnpr.net>
To: John E Drake <jdrake@juniper.net>
X-Mailer: Apple Mail (2.1084)
X-Y-GMX-Trusted: 0
Cc: "iab@iab.org" <iab@iab.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, 15 Aug 2012 12:38:13 -0000

On Aug 15, 2012, at 3:16 PM, John E Drake wrote:

>> I take it that John's question is really *why* do these principles =
need
>> to be articulated in public. Perhaps the IAB should answer that, but =
my
>> answer
>> is: because there is a real danger of some SDOs, including but not
>> limited to the ITU-T, breaking them for a variety of commercial or
>> political reasons.
>=20
> JD:  And how does this document prevent this abuse?

Of course a document by itself, even if it contains the nicest =
principles, cannot prevent abuse.=20
So, see it rather as a writeup that tries to capture the understanding =
of a number of SDOs.=20


From jdrake@juniper.net  Wed Aug 15 05:44:17 2012
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 3E2CA21F880C for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 05:44:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.381
X-Spam-Level: 
X-Spam-Status: No, score=-5.381 tagged_above=-999 required=5 tests=[AWL=1.218,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GUNEF7QzM6jO for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 05:44:16 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by ietfa.amsl.com (Postfix) with ESMTP id 6278D21F8807 for <ietf@ietf.org>; Wed, 15 Aug 2012 05:44:16 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKUCuZmKAxTUBKXd+wx5fL6PZcBeiK/sPT@postini.com; Wed, 15 Aug 2012 05:44:16 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; Wed, 15 Aug 2012 05:41:16 -0700
From: John E Drake <jdrake@juniper.net>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Date: Wed, 15 Aug 2012 05:41:14 -0700
Subject: RE: Affirmation of the Modern Global Standards Paradigm
Thread-Topic: Affirmation of the Modern Global Standards Paradigm
Thread-Index: Ac164uMSlWGUcK12QsGGUWDem23AaAAAB/4A
Message-ID: <5E893DB832F57341992548CDBB333163A5A9B4665D@EMBX01-HQ.jnpr.net>
References: <5E893DB832F57341992548CDBB333163A5A9B462FF@EMBX01-HQ.jnpr.net> <502B40B7.8050100@cisco.com> <502B48E8.7060104@gmail.com> <5E893DB832F57341992548CDBB333163A5A9B46658@EMBX01-HQ.jnpr.net> <8972B876-DD01-474E-9234-0133DC9DC119@gmx.net>
In-Reply-To: <8972B876-DD01-474E-9234-0133DC9DC119@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
Cc: "iab@iab.org" <iab@iab.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, 15 Aug 2012 12:44:17 -0000

Comment inline

Sent from my iPhone


> -----Original Message-----
> From: Hannes Tschofenig [mailto:hannes.tschofenig@gmx.net]
> Sent: Wednesday, August 15, 2012 5:38 AM
> To: John E Drake
> Cc: Hannes Tschofenig; Brian E Carpenter; Eliot Lear; iab@iab.org;
> ietf@ietf.org
> Subject: Re: Affirmation of the Modern Global Standards Paradigm
>=20
>=20
> On Aug 15, 2012, at 3:16 PM, John E Drake wrote:
>=20
> >> I take it that John's question is really *why* do these principles
> >> need to be articulated in public. Perhaps the IAB should answer
> that,
> >> but my answer
> >> is: because there is a real danger of some SDOs, including but not
> >> limited to the ITU-T, breaking them for a variety of commercial or
> >> political reasons.
> >
> > JD:  And how does this document prevent this abuse?
>=20
> Of course a document by itself, even if it contains the nicest
> principles, cannot prevent abuse.
> So, see it rather as a writeup that tries to capture the understanding
> of a number of SDOs.

JD:  To what purpose?  As an aside, I get the 'feel-good' aspect, but is th=
ere anything more?


From lear@cisco.com  Wed Aug 15 05:44:21 2012
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 1278721F8808 for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 05:44:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.518
X-Spam-Level: 
X-Spam-Status: No, score=-110.518 tagged_above=-999 required=5 tests=[AWL=0.080, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29hwaI65DZrO for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 05:44:19 -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 75DE621F87D2 for <ietf@ietf.org>; Wed, 15 Aug 2012 05:44:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=9699; q=dns/txt; s=iport; t=1345034658; x=1346244258; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=eaea729R5ZW48dSgQzLxzPJGLgP8uC1oCkSc0okb2IU=; b=Xx+SlVGy6BQMmfereP8HogDKysy/sI7aO0E0iLRR2kN7eQTzQMiBRG/D P981PphQAnI/v2ss1gMxN1NcEleWQg8nme6pdleRZCuA7Y8H+khj7HYjg nEQw3rV6GGcBgf0Wwvi+CNnb9vweqDADWNE3/Pny/IuIvbCh5Q1+Gdt/k I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFANSYK1CQ/khR/2dsb2JhbABFgkqDN7QcgQeCIAEBAQMBEgEQCksBEAsYCQMTCwICCQMCAQIBPAkGDQEHAQEaBIdlBpkzjRmTNpBLgRIDkWmDYo4qgWaCYQ
X-IronPort-AV: E=Sophos;i="4.77,773,1336348800";  d="scan'208,217";a="142443993"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-1.cisco.com with ESMTP; 15 Aug 2012 12:44:17 +0000
Received: from dhcp-10-55-89-242.cisco.com (dhcp-10-55-89-242.cisco.com [10.55.89.242]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q7FCiGK1017721 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Aug 2012 12:44:16 GMT
Message-ID: <502B99A0.1050409@cisco.com>
Date: Wed, 15 Aug 2012 14:44:16 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: John E Drake <jdrake@juniper.net>
Subject: Re: FW: Affirmation of the Modern Global Standards Paradigm
References: <5E893DB832F57341992548CDBB333163A5A9B462FF@EMBX01-HQ.jnpr.net> <502B40B7.8050100@cisco.com> <5E893DB832F57341992548CDBB333163A5A9B46657@EMBX01-HQ.jnpr.net>
In-Reply-To: <5E893DB832F57341992548CDBB333163A5A9B46657@EMBX01-HQ.jnpr.net>
X-Enigmail-Version: 1.4.3
Content-Type: multipart/alternative; boundary="------------010702020301080307060609"
Cc: "iab@iab.org" <iab@iab.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Aug 2012 12:44:21 -0000

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

Hi John,

On 8/15/12 2:15 PM, John E Drake wrote:
>
>  
> To me (and I speak only for me here), the purpose of this document is
> to articulate principles that have made the Internet a success.
>
>  
>
> JD:  This seems a bit presumptuous to me.
>

It's an assertion.  I wouldn't claim, by the way, that this was the only
factor.  IMHO, it was a contributing factor.  Moore's Law and the
development of technology in general all contributed, but you had to
have a process that was open for the technology to flourish.  IMHO this
is why SNA, DECNET, Appletalk, XNS, OSI, and others did not win, where
IP did.

>  
>
> It is a means to invite others to subscribe to those same principles,
> and there are many standards organizations that do not.
>
>  
>
> JD:  I would be willing to bet that nearly every SDO would claim they
> embrace these same principles.
>

And that's a fair point.  The proof is in the pudding.  I believe, and I
know you do too, that the IETF itself can explain in clear indisputable
terms how it fulfills the principles of openness.  Anyone can join a WG
list.  Anyone can submit an Internet-Draft, anyone can comment on that
draft, anyone can request that draft's advancement, anyone can comment
on or contribute to or object to that draft's advancement, anyone can be
a part of the leadership (one needn't even have ever participated in the
IETF before!!).  Decisions are made through a consensus process.  That
process is designed to be transparent.  There are appellate avenues for
abuse of process.  They have worked and are working.  I am told for
instance that at this very moment there is an appeal before the
applications area director that seems to me particularly meaty.  That's
good.  It's important that people know that there is an appeals avenue
available.

The W3C is very similar.  The IEEE SA is also similar.  So are others,
and that's fine.  But there are many other organizations where it's just
not the case, and so...

>  
>
> Customers and society can demand better, and this is an avenue for that.
>
>  
>
> JD:  How, exactly?
>

How about a phone call?  A blog?  A press release?  Laws and regulations
requiring the use of standards based on those principles?

Eliot

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

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi John,<br>
    <br>
    <div class="moz-cite-prefix">On 8/15/12 2:15 PM, John E Drake wrote:<br>
    </div>
    <blockquote
      cite="mid:5E893DB832F57341992548CDBB333163A5A9B46657@EMBX01-HQ.jnpr.net"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <meta name="Generator" content="Microsoft Word 12 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family: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:11.0pt;
	font-family:"Calibri","sans-serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{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="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span style="color:#1F497D"><o:p>Â </o:p></span><span
            style="font-size:12.0pt;font-family:&quot;Times New
            Roman&quot;,&quot;serif&quot;"><br>
            To me (and I speak only for me here), the purpose of this
            document is to articulate principles that have made the
            Internet a success.</span><span
            style="font-size:12.0pt;font-family:&quot;Times New
            Roman&quot;,&quot;serif&quot;;color:#1F497D"><o:p></o:p></span></p>
        <div style="border:none;border-left:solid blue 1.5pt;padding:0in
          0in 0in 4.0pt">
          <p class="MsoNormal"><span style="color:#1F497D"><o:p>Â </o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D">JD:Â  This
              seems a bit presumptuous to me.<o:p></o:p></span></p>
        </div>
      </div>
    </blockquote>
    <br>
    It's an assertion.Â  I wouldn't claim, by the way, that this was the
    only factor.Â  IMHO, it was a contributing factor.Â  Moore's Law and
    the development of technology in general all contributed, but you
    had to have a process that was open for the technology to flourish.Â 
    IMHO this is why SNA, DECNET, Appletalk, XNS, OSI, and others did
    not win, where IP did.<br>
    <br>
    <blockquote
      cite="mid:5E893DB832F57341992548CDBB333163A5A9B46657@EMBX01-HQ.jnpr.net"
      type="cite">
      <div class="WordSection1">
        <div style="border:none;border-left:solid blue 1.5pt;padding:0in
          0in 0in 4.0pt">
          <p class="MsoNormal"><span style="color:#1F497D"><o:p>Â </o:p></span></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;">It is a means to invite
              others to subscribe to those same principles, and there
              are many standards organizations that do not.</span><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D"><o:p>Â </o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D">JD:Â  I would
              be willing to bet that nearly every SDO would claim they
              embrace these same principles.</span></p>
        </div>
      </div>
    </blockquote>
    <br>
    And that's a fair point.Â  The proof is in the pudding.Â  I believe,
    and I know you do too, that the IETF itself can explain in clear
    indisputable terms how it fulfills the principles of openness.Â 
    Anyone can join a WG list.Â  Anyone can submit an Internet-Draft,
    anyone can comment on that draft, anyone can request that draft's
    advancement, anyone can comment on or contribute to or object to
    that draft's advancement, anyone can be a part of the leadership
    (one needn't even have ever participated in the IETF before!!).Â 
    Decisions are made through a consensus process.Â  That process is
    designed to be transparent.Â  There are appellate avenues for abuse
    of process.Â  They have worked and are working.Â  I am told for
    instance that at this very moment there is an appeal before the
    applications area director that seems to me particularly meaty.Â 
    That's good.Â  It's important that people know that there is an
    appeals avenue available.<br>
    <br>
    The W3C is very similar.Â  The IEEE SA is also similar.Â  So are
    others, and that's fine.Â  But there are many other organizations
    where it's just not the case, and so...<br>
    <br>
    <blockquote
      cite="mid:5E893DB832F57341992548CDBB333163A5A9B46657@EMBX01-HQ.jnpr.net"
      type="cite">
      <div class="WordSection1">
        <div style="border:none;border-left:solid blue 1.5pt;padding:0in
          0in 0in 4.0pt">
          <p class="MsoNormal"><span style="color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D"><o:p>Â </o:p></span></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;">Customers and society can
              demand better, and this is an avenue for that.</span><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D"><o:p>Â </o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D">JD:Â  How,
              exactly?</span><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;"><br>
              <br>
            </span></p>
        </div>
      </div>
    </blockquote>
    <br>
    How about a phone call?Â  A blog?Â  A press release?Â  Laws and
    regulations requiring the use of standards based on those
    principles?<br>
    <br>
    Eliot<br>
  </body>
</html>

--------------010702020301080307060609--

From mfberny@gmail.com  Wed Aug 15 05:48:12 2012
Return-Path: <mfberny@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2786F21F8818 for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 05:48:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.498
X-Spam-Level: 
X-Spam-Status: No, score=-3.498 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7x6ermz0SHZ2 for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 05:48:11 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id EE2ED21F8816 for <ietf@ietf.org>; Wed, 15 Aug 2012 05:48:10 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so1670987vcb.31 for <ietf@ietf.org>; Wed, 15 Aug 2012 05:48:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=tvw6owCw0B66L9tUHhmmQJlDsrC+u8x0B3OvGjl92ls=; b=edqfTJ0h6iVUbj3FXcx7yeA3wKwk4UoXTKiY3498rdulET+ERgLWYzdSbP+zqxgUsg BCBfqo1ydhH65QU/RoWIbJEGqtmPN0JcaI20d1UbO7XGTV3NGDWvbXPcQs8WsTp3lSjy 0+mZ5OPI46+P065lIHVZB4dc6KcVTDH6hD0pZXfDvnH9JLHA6Z21cTyXEt8Q6ourXfjC czuSQOvieZ4UMn93MyHxmWWEZqqatOmBkoU0434zVpfUDaICecaDsg2r1bxWeB8XpOtk RWv6QHb/YQZQakIjslEfvEDDdWvbJkTd1TYgi1niFiTVsZGhhvh3O8vO+/9CMJ5lUgt7 ZasA==
MIME-Version: 1.0
Received: by 10.220.248.69 with SMTP id mf5mr12752847vcb.42.1345034890282; Wed, 15 Aug 2012 05:48:10 -0700 (PDT)
Received: by 10.58.253.136 with HTTP; Wed, 15 Aug 2012 05:48:10 -0700 (PDT)
In-Reply-To: <502B48E8.7060104@gmail.com>
References: <5E893DB832F57341992548CDBB333163A5A9B462FF@EMBX01-HQ.jnpr.net> <502B40B7.8050100@cisco.com> <502B48E8.7060104@gmail.com>
Date: Wed, 15 Aug 2012 14:48:10 +0200
Message-ID: <CAL-6tfX3DHBn+yZTRv+V=DDZk0yJGjkNEO3xi_hKCbRJ-wMYeg@mail.gmail.com>
Subject: Re: FW: Affirmation of the Modern Global Standards Paradigm
From: Marie-France Berny <mfberny@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec517a5b0d887e304c74d566e
Cc: "iab@iab.org" <iab@iab.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, 15 Aug 2012 12:48:12 -0000

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

Brian,

let be candid. The text of Bernard Adoba (Microsoft) is 100% in line with
the Microsoft political line broadly publish under cover of Human Rights as
the Global Network Initiative (http://www.globalnetworkinitiative.org/).
Since the co-founder/influencer of GNI is Google (with Yahoo!) also with
Microsoft a jewell member of ISOC, and that Russ Housley is security
specialist involved in the IEEE, this text, its signatoree and first
supporter were quickly identified in the political world as a confirmation
that the IAB is (now the IETF is an affiliate of ISOC) politically and
could therefore most probably technically be biaised in favor of the
interest of the US industry dominants club.

Obviously, in political situation nothing is first degree. So, the question
is why M$, Google, IBM, Yahoo!, Oracle etc. are exposing the credibility of
the IETF credibility a



2012/8/15 Brian E Carpenter <brian.e.carpenter@gmail.com>

> On 15/08/2012 07:24, Eliot Lear wrote:
> > John,
> >
> > On 8/15/12 12:03 AM, John E Drake wrote:
> >> Hi,
> >>
> >> Does this document actually have a purpose, and if so, what is it?
> >>
> >
> > To me (and I speak only for me here), the purpose of this document is to
> > articulate principles that have made the Internet a success.  It is a
> > means to invite others to subscribe to those same principles, and there
> > are many standards organizations that do not.  Customers and society can
> > demand better, and this is an avenue for that.
>
> I take it that John's question is really *why* do these principles need to
> be articulated in public. Perhaps the IAB should answer that, but my answer
> is: because there is a real danger of some SDOs, including but not limited
> to the ITU-T, breaking them for a variety of commercial or political
> reasons.
>
>    Brian
>

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

Brian,<br><br>let be candid. The text of Bernard Adoba (Microsoft) is 100% =
in line with the Microsoft political line broadly publish under cover of Hu=
man Rights as the Global Network Initiative (<a href=3D"http://www.globalne=
tworkinitiative.org/" target=3D"_blank">http://www.globalnetworkinitiative.=
org/</a>). Since the co-founder/influencer of GNI is Google (with Yahoo!) a=
lso with Microsoft a jewell member of ISOC, and that Russ Housley is securi=
ty specialist involved in the IEEE, this text, its signatoree and first sup=
porter were quickly identified in the political world as a confirmation tha=
t the IAB is (now the IETF is an affiliate of ISOC) politically and could t=
herefore most probably technically be biaised in favor of the interest of t=
he US industry dominants club.<br>

<br>Obviously, in political situation nothing is first degree. So, the ques=
tion is why M$, Google, IBM, Yahoo!, Oracle etc. are exposing the credibili=
ty of the IETF credibility a<br><br>
<br><br><div class=3D"gmail_quote">2012/8/15 Brian E Carpenter <span dir=3D=
"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">=
brian.e.carpenter@gmail.com</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div><div>On 15/08/2012 07:24, Eliot Lear wrote:<br>
&gt; John,<br>
&gt;<br>
&gt; On 8/15/12 12:03 AM, John E Drake wrote:<br>
&gt;&gt; Hi,<br>
&gt;&gt;<br>
&gt;&gt; Does this document actually have a purpose, and if so, what is it?=
<br>
&gt;&gt;<br>
&gt;<br>
&gt; To me (and I speak only for me here), the purpose of this document is =
to<br>
&gt; articulate principles that have made the Internet a success. =A0It is =
a<br>
&gt; means to invite others to subscribe to those same principles, and ther=
e<br>
&gt; are many standards organizations that do not. =A0Customers and society=
 can<br>
&gt; demand better, and this is an avenue for that.<br>
<br>
</div></div>I take it that John&#39;s question is really *why* do these pri=
nciples need to<br>
be articulated in public. Perhaps the IAB should answer that, but my answer=
<br>
is: because there is a real danger of some SDOs, including but not limited<=
br>
to the ITU-T, breaking them for a variety of commercial or political reason=
s.<br>
<span><font color=3D"#888888"><br>
=A0 =A0Brian<br>
</font></span></blockquote></div><br>

--bcaec517a5b0d887e304c74d566e--

From mfberny@gmail.com  Wed Aug 15 06:00:21 2012
Return-Path: <mfberny@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5707921F87EE for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 06:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.548
X-Spam-Level: 
X-Spam-Status: No, score=-3.548 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SsHL09gSkJdV for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 06:00:20 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id C2A1821F87DD for <ietf@ietf.org>; Wed, 15 Aug 2012 06:00:19 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so1682966vcb.31 for <ietf@ietf.org>; Wed, 15 Aug 2012 06:00:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XQ+4ZB9aJLrpKG1lZXItKZv7S9g4nfpfHqX+G+ngeiQ=; b=RcxLodqHG6Bnmwk3IM89rUmprARVjKoB9YHviBgllyfXc1ApnNLQg5Xu8IPRxaIKxw 7JnC6dA84JtUP3hZHYxup9w4qQC2aM/NScwWORQFa92sknRia/O0oHrDwKUf/TWsqlBy Ax48JLu/Iu095Y9ee9GVhhSQxmvSia7fRKCX4LhXikn8lSj0h59EkcxmTC8QoO1YLLyt xQhY8Ws8MQ1MzIlOjta9m3Qh9rb5vOzkRApHbq6vR01tYOkQXwq7lRJrZ8YHPd4QCekU zMIm//FbYDQCwhXmg8W9NSYyxp0k0Tsz84ui3NSohDdbgHhnvecXXiVLyjvw9asPbql6 PUcw==
MIME-Version: 1.0
Received: by 10.220.153.7 with SMTP id i7mr12795962vcw.34.1345035619289; Wed, 15 Aug 2012 06:00:19 -0700 (PDT)
Received: by 10.58.253.136 with HTTP; Wed, 15 Aug 2012 06:00:18 -0700 (PDT)
In-Reply-To: <CAL-6tfX3DHBn+yZTRv+V=DDZk0yJGjkNEO3xi_hKCbRJ-wMYeg@mail.gmail.com>
References: <5E893DB832F57341992548CDBB333163A5A9B462FF@EMBX01-HQ.jnpr.net> <502B40B7.8050100@cisco.com> <502B48E8.7060104@gmail.com> <CAL-6tfX3DHBn+yZTRv+V=DDZk0yJGjkNEO3xi_hKCbRJ-wMYeg@mail.gmail.com>
Date: Wed, 15 Aug 2012 15:00:18 +0200
Message-ID: <CAL-6tfWD5F0ABVy0SG-Ecb0kn-GRzSRJ+chNP1vMHsW3SzY0ng@mail.gmail.com>
Subject: Re: FW: Affirmation of the Modern Global Standards Paradigm
From: Marie-France Berny <mfberny@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=f46d043c7c7c4c4aa604c74d82fc
Cc: "iab@iab.org" <iab@iab.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, 15 Aug 2012 13:00:21 -0000

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

Sorry for sending the mail too fast. I finish it.

2012/8/15 Marie-France Berny <mfberny@gmail.com>

> Brian,
>
> let be candid. The text of Bernard Adoba (Microsoft) is 100% in line with
> the Microsoft political line broadly publish under cover of Human Rights as
> the Global Network Initiative (http://www.globalnetworkinitiative.org/).
> Since the co-founder/influencer of GNI is Google (with Yahoo!) also with
> Microsoft a jewell member of ISOC, and that Russ Housley is security
> specialist involved in the IEEE, this text, its signatoree and first
> supporter were quickly identified in the political world as a confirmation
> that the IAB is (now the IETF is an affiliate of ISOC) politically and
> could therefore most probably technically be biaised in favor of the
> interest of the US industry dominants club.
>
> Obviously, in political situations nothing is first degree. So, the
> question is why M$, Google, IBM, Yahoo!, Oracle etc. (the Unicode
> consortium, your company belongs to) are exposing the credibility of the
> IETF neutrality at this stage? There might be a global security oriented
> concern. There is certainly a concern regarding the multilinguistics of the
> Internet (leading to a multilatteral Internet). There is also the rogue
> attitude of ICANN to correct. There is also the lack of innovation due to
> the IETF slow-down. May be the Indian sub-continent oriented search of
> influence vs. China and Russia.
>

Frankly we are not interested in this in here. We are concerned by network
and network technology neutrality and best user interests. All this is to
try to defensively balkanize the net. Please, let discuss our common bits,
not the others' sins. Technical standards are not supposed to govern the
world, democratically elected government are. We are not interested in
protecting merchant interests and processes, but protocols and people.

My 3 cents.
MFBerny

>
>
>
>
> 2012/8/15 Brian E Carpenter <brian.e.carpenter@gmail.com>
>
>> On 15/08/2012 07:24, Eliot Lear wrote:
>> > John,
>> >
>> > On 8/15/12 12:03 AM, John E Drake wrote:
>> >> Hi,
>> >>
>> >> Does this document actually have a purpose, and if so, what is it?
>> >>
>> >
>> > To me (and I speak only for me here), the purpose of this document is to
>> > articulate principles that have made the Internet a success.  It is a
>> > means to invite others to subscribe to those same principles, and there
>> > are many standards organizations that do not.  Customers and society can
>> > demand better, and this is an avenue for that.
>>
>> I take it that John's question is really *why* do these principles need to
>> be articulated in public. Perhaps the IAB should answer that, but my
>> answer
>> is: because there is a real danger of some SDOs, including but not limited
>> to the ITU-T, breaking them for a variety of commercial or political
>> reasons.
>>
>>    Brian
>>
>
>

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

Sorry for sending the mail too fast. I finish it.<br><br><div class=3D"gmai=
l_quote">2012/8/15 Marie-France Berny <span dir=3D"ltr">&lt;<a href=3D"mail=
to:mfberny@gmail.com" target=3D"_blank">mfberny@gmail.com</a>&gt;</span><br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">
Brian,<br><br>let be candid. The text of Bernard Adoba (Microsoft) is 100% =
in line with the Microsoft political line broadly publish under cover of Hu=
man Rights as the Global Network Initiative (<a href=3D"http://www.globalne=
tworkinitiative.org/" target=3D"_blank">http://www.globalnetworkinitiative.=
org/</a>). Since the co-founder/influencer of GNI is Google (with Yahoo!) a=
lso with Microsoft a jewell member of ISOC, and that Russ Housley is securi=
ty specialist involved in the IEEE, this text, its signatoree and first sup=
porter were quickly identified in the political world as a confirmation tha=
t the IAB is (now the IETF is an affiliate of ISOC) politically and could t=
herefore most probably technically be biaised in favor of the interest of t=
he US industry dominants club.<br>


<br>Obviously, in political situations nothing is first degree. So, the que=
stion is why M$, Google, IBM, Yahoo!, Oracle etc. (the Unicode consortium, =
your company belongs to) are exposing the credibility of the IETF neutralit=
y at this stage? There might be a global security oriented concern. There i=
s certainly a concern regarding the multilinguistics of the Internet (leadi=
ng to a multilatteral Internet). There is also the rogue attitude of ICANN =
to correct. There is also the lack of innovation due to the IETF slow-down.=
 May be the Indian sub-continent oriented search of influence vs. China and=
 Russia.<br>
</blockquote><div><br>Frankly we are not interested in this in here. We are=
 concerned by network and network technology neutrality and best user inter=
ests. All this is to try to defensively balkanize the net. Please, let disc=
uss our common bits, not the others&#39; sins. Technical standards are not =
supposed to govern the world, democratically elected government are. We are=
 not interested in protecting merchant interests and processes, but protoco=
ls and people.<br>
<br>My 3 cents.<br>MFBerny<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div cla=
ss=3D"HOEnZb"><div class=3D"h5"><br><br>
<br><br><div class=3D"gmail_quote">2012/8/15 Brian E Carpenter <span dir=3D=
"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">=
brian.e.carpenter@gmail.com</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div><div>On 15/08/2012 07:24, Eliot Lear wrote:<br>
&gt; John,<br>
&gt;<br>
&gt; On 8/15/12 12:03 AM, John E Drake wrote:<br>
&gt;&gt; Hi,<br>
&gt;&gt;<br>
&gt;&gt; Does this document actually have a purpose, and if so, what is it?=
<br>
&gt;&gt;<br>
&gt;<br>
&gt; To me (and I speak only for me here), the purpose of this document is =
to<br>
&gt; articulate principles that have made the Internet a success. =A0It is =
a<br>
&gt; means to invite others to subscribe to those same principles, and ther=
e<br>
&gt; are many standards organizations that do not. =A0Customers and society=
 can<br>
&gt; demand better, and this is an avenue for that.<br>
<br>
</div></div>I take it that John&#39;s question is really *why* do these pri=
nciples need to<br>
be articulated in public. Perhaps the IAB should answer that, but my answer=
<br>
is: because there is a real danger of some SDOs, including but not limited<=
br>
to the ITU-T, breaking them for a variety of commercial or political reason=
s.<br>
<span><font color=3D"#888888"><br>
=A0 =A0Brian<br>
</font></span></blockquote></div><br>
</div></div></blockquote></div><br>

--f46d043c7c7c4c4aa604c74d82fc--

From jdrake@juniper.net  Wed Aug 15 06:20:26 2012
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 6489D21F8848 for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 06:20:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.476
X-Spam-Level: 
X-Spam-Status: No, score=-5.476 tagged_above=-999 required=5 tests=[AWL=1.122,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eiXX9WLSBDnK for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 06:20:25 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by ietfa.amsl.com (Postfix) with ESMTP id C14B221F8827 for <ietf@ietf.org>; Wed, 15 Aug 2012 06:20:24 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKUCuiF5Cmpl9fNerGjtL8DZjRhOuH8mYX@postini.com; Wed, 15 Aug 2012 06:20:24 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; Wed, 15 Aug 2012 06:16:36 -0700
From: John E Drake <jdrake@juniper.net>
To: Eliot Lear <lear@cisco.com>
Date: Wed, 15 Aug 2012 06:16:34 -0700
Subject: RE: FW: Affirmation of the Modern Global Standards Paradigm
Thread-Topic: FW: Affirmation of the Modern Global Standards Paradigm
Thread-Index: Ac165GTkePAF5zqhQIG2WZZrIToIcQAA0jrA
Message-ID: <5E893DB832F57341992548CDBB333163A5A9B46662@EMBX01-HQ.jnpr.net>
References: <5E893DB832F57341992548CDBB333163A5A9B462FF@EMBX01-HQ.jnpr.net> <502B40B7.8050100@cisco.com> <5E893DB832F57341992548CDBB333163A5A9B46657@EMBX01-HQ.jnpr.net> <502B99A0.1050409@cisco.com>
In-Reply-To: <502B99A0.1050409@cisco.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_5E893DB832F57341992548CDBB333163A5A9B46662EMBX01HQjnprn_"
MIME-Version: 1.0
Cc: "iab@iab.org" <iab@iab.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Aug 2012 13:20:26 -0000

--_000_5E893DB832F57341992548CDBB333163A5A9B46662EMBX01HQjnprn_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

RWxpb3QsDQoNCllvdXIgZXhwbGFuYXRpb24gb2YgdGhlIGRvY3VtZW504oCZcyBlZmZpY2FjeSBs
ZWF2ZXMgbWUgc2tlcHRpY2FsLiAgIFdlIHNob3VsZCBhbHdheXMgZG8gc29tZXRoaW5nIGZvciBh
IHJlYXNvbi4NCg0KVGhhbmtzLA0KDQpKb2huDQoNClNlbnQgZnJvbSBteSBpUGhvbmUNCg0KRnJv
bTogRWxpb3QgTGVhciBbbWFpbHRvOmxlYXJAY2lzY28uY29tXQ0KU2VudDogV2VkbmVzZGF5LCBB
dWd1c3QgMTUsIDIwMTIgNTo0NCBBTQ0KVG86IEpvaG4gRSBEcmFrZQ0KQ2M6IGlhYkBpYWIub3Jn
OyBJRVRGIERpc2N1c3Npb24NClN1YmplY3Q6IFJlOiBGVzogQWZmaXJtYXRpb24gb2YgdGhlIE1v
ZGVybiBHbG9iYWwgU3RhbmRhcmRzIFBhcmFkaWdtDQoNCkhpIEpvaG4sDQpPbiA4LzE1LzEyIDI6
MTUgUE0sIEpvaG4gRSBEcmFrZSB3cm90ZToNCg0KVG8gbWUgKGFuZCBJIHNwZWFrIG9ubHkgZm9y
IG1lIGhlcmUpLCB0aGUgcHVycG9zZSBvZiB0aGlzIGRvY3VtZW50IGlzIHRvIGFydGljdWxhdGUg
cHJpbmNpcGxlcyB0aGF0IGhhdmUgbWFkZSB0aGUgSW50ZXJuZXQgYSBzdWNjZXNzLg0KDQpKRDog
IFRoaXMgc2VlbXMgYSBiaXQgcHJlc3VtcHR1b3VzIHRvIG1lLg0KDQpJdCdzIGFuIGFzc2VydGlv
bi4gIEkgd291bGRuJ3QgY2xhaW0sIGJ5IHRoZSB3YXksIHRoYXQgdGhpcyB3YXMgdGhlIG9ubHkg
ZmFjdG9yLiAgSU1ITywgaXQgd2FzIGEgY29udHJpYnV0aW5nIGZhY3Rvci4gIE1vb3JlJ3MgTGF3
IGFuZCB0aGUgZGV2ZWxvcG1lbnQgb2YgdGVjaG5vbG9neSBpbiBnZW5lcmFsIGFsbCBjb250cmli
dXRlZCwgYnV0IHlvdSBoYWQgdG8gaGF2ZSBhIHByb2Nlc3MgdGhhdCB3YXMgb3BlbiBmb3IgdGhl
IHRlY2hub2xvZ3kgdG8gZmxvdXJpc2guICBJTUhPIHRoaXMgaXMgd2h5IFNOQSwgREVDTkVULCBB
cHBsZXRhbGssIFhOUywgT1NJLCBhbmQgb3RoZXJzIGRpZCBub3Qgd2luLCB3aGVyZSBJUCBkaWQu
DQoNCg0KDQpJdCBpcyBhIG1lYW5zIHRvIGludml0ZSBvdGhlcnMgdG8gc3Vic2NyaWJlIHRvIHRo
b3NlIHNhbWUgcHJpbmNpcGxlcywgYW5kIHRoZXJlIGFyZSBtYW55IHN0YW5kYXJkcyBvcmdhbml6
YXRpb25zIHRoYXQgZG8gbm90Lg0KDQpKRDogIEkgd291bGQgYmUgd2lsbGluZyB0byBiZXQgdGhh
dCBuZWFybHkgZXZlcnkgU0RPIHdvdWxkIGNsYWltIHRoZXkgZW1icmFjZSB0aGVzZSBzYW1lIHBy
aW5jaXBsZXMuDQoNCkFuZCB0aGF0J3MgYSBmYWlyIHBvaW50LiAgVGhlIHByb29mIGlzIGluIHRo
ZSBwdWRkaW5nLiAgSSBiZWxpZXZlLCBhbmQgSSBrbm93IHlvdSBkbyB0b28sIHRoYXQgdGhlIElF
VEYgaXRzZWxmIGNhbiBleHBsYWluIGluIGNsZWFyIGluZGlzcHV0YWJsZSB0ZXJtcyBob3cgaXQg
ZnVsZmlsbHMgdGhlIHByaW5jaXBsZXMgb2Ygb3Blbm5lc3MuICBBbnlvbmUgY2FuIGpvaW4gYSBX
RyBsaXN0LiAgQW55b25lIGNhbiBzdWJtaXQgYW4gSW50ZXJuZXQtRHJhZnQsIGFueW9uZSBjYW4g
Y29tbWVudCBvbiB0aGF0IGRyYWZ0LCBhbnlvbmUgY2FuIHJlcXVlc3QgdGhhdCBkcmFmdCdzIGFk
dmFuY2VtZW50LCBhbnlvbmUgY2FuIGNvbW1lbnQgb24gb3IgY29udHJpYnV0ZSB0byBvciBvYmpl
Y3QgdG8gdGhhdCBkcmFmdCdzIGFkdmFuY2VtZW50LCBhbnlvbmUgY2FuIGJlIGEgcGFydCBvZiB0
aGUgbGVhZGVyc2hpcCAob25lIG5lZWRuJ3QgZXZlbiBoYXZlIGV2ZXIgcGFydGljaXBhdGVkIGlu
IHRoZSBJRVRGIGJlZm9yZSEhKS4gIERlY2lzaW9ucyBhcmUgbWFkZSB0aHJvdWdoIGEgY29uc2Vu
c3VzIHByb2Nlc3MuICBUaGF0IHByb2Nlc3MgaXMgZGVzaWduZWQgdG8gYmUgdHJhbnNwYXJlbnQu
ICBUaGVyZSBhcmUgYXBwZWxsYXRlIGF2ZW51ZXMgZm9yIGFidXNlIG9mIHByb2Nlc3MuICBUaGV5
IGhhdmUgd29ya2VkIGFuZCBhcmUgd29ya2luZy4gIEkgYW0gdG9sZCBmb3IgaW5zdGFuY2UgdGhh
dCBhdCB0aGlzIHZlcnkgbW9tZW50IHRoZXJlIGlzIGFuIGFwcGVhbCBiZWZvcmUgdGhlIGFwcGxp
Y2F0aW9ucyBhcmVhIGRpcmVjdG9yIHRoYXQgc2VlbXMgdG8gbWUgcGFydGljdWxhcmx5IG1lYXR5
LiAgVGhhdCdzIGdvb2QuICBJdCdzIGltcG9ydGFudCB0aGF0IHBlb3BsZSBrbm93IHRoYXQgdGhl
cmUgaXMgYW4gYXBwZWFscyBhdmVudWUgYXZhaWxhYmxlLg0KDQpUaGUgVzNDIGlzIHZlcnkgc2lt
aWxhci4gIFRoZSBJRUVFIFNBIGlzIGFsc28gc2ltaWxhci4gIFNvIGFyZSBvdGhlcnMsIGFuZCB0
aGF0J3MgZmluZS4gIEJ1dCB0aGVyZSBhcmUgbWFueSBvdGhlciBvcmdhbml6YXRpb25zIHdoZXJl
IGl0J3MganVzdCBub3QgdGhlIGNhc2UsIGFuZCBzby4uLg0KDQoNCg0KQ3VzdG9tZXJzIGFuZCBz
b2NpZXR5IGNhbiBkZW1hbmQgYmV0dGVyLCBhbmQgdGhpcyBpcyBhbiBhdmVudWUgZm9yIHRoYXQu
DQoNCkpEOiAgSG93LCBleGFjdGx5Pw0KDQpIb3cgYWJvdXQgYSBwaG9uZSBjYWxsPyAgQSBibG9n
PyAgQSBwcmVzcyByZWxlYXNlPyAgTGF3cyBhbmQgcmVndWxhdGlvbnMgcmVxdWlyaW5nIHRoZSB1
c2Ugb2Ygc3RhbmRhcmRzIGJhc2VkIG9uIHRob3NlIHByaW5jaXBsZXM/DQoNCkVsaW90DQo=

--_000_5E893DB832F57341992548CDBB333163A5A9B46662EMBX01HQjnprn_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij48bWV0YSBuYW1lPUdlbmVyYXRvciBjb250ZW50
PSJNaWNyb3NvZnQgV29yZCAxMiAoZmlsdGVyZWQgbWVkaXVtKSI+PHN0eWxlPjwhLS0NCi8qIEZv
bnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0
aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQt
ZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQt
ZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7DQoJcGFub3NlLTE6MiAxMSA2IDQgMyA1IDQgNCAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIFwsIHNlcmlm
IjsNCglwYW5vc2UtMTowIDAgMCAwIDAgMCAwIDAgMCAwO30NCi8qIFN0eWxlIERlZmluaXRpb25z
ICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjow
aW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1m
YW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjpibGFjazt9DQphOmxpbmssIHNw
YW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0K
CXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlu
a0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4
dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxNw0KCXttc28tc3R5bGUt
dHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNv
bG9yOndpbmRvd3RleHQ7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVy
c29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0
OTdEO30NCnNwYW4uRW1haWxTdHlsZTE5DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFu
LkVtYWlsU3R5bGUyMA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZh
bWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERl
ZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9
DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGlu
IDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlv
bjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVs
dHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0t
W2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlk
bWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2Vu
ZGlmXS0tPjwvaGVhZD48Ym9keSBiZ2NvbG9yPXdoaXRlIGxhbmc9RU4tVVMgbGluaz1ibHVlIHZs
aW5rPXB1cnBsZT48ZGl2IGNsYXNzPVdvcmRTZWN0aW9uMT48cCBjbGFzcz1Nc29Ob3JtYWw+PHNw
YW4gc3R5bGU9J2NvbG9yOiMxRjQ5N0QnPkVsaW90LDxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBj
bGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2NvbG9yOiMxRjQ5N0QnPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2NvbG9yOiMxRjQ5
N0QnPllvdXIgZXhwbGFuYXRpb24gb2YgdGhlIGRvY3VtZW504oCZcyBlZmZpY2FjeSBsZWF2ZXMg
bWUgc2tlcHRpY2FsLiDCoMKgV2Ugc2hvdWxkIGFsd2F5cyBkbyBzb21ldGhpbmcgZm9yIGEgcmVh
c29uLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9
J2NvbG9yOiMxRjQ5N0QnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29O
b3JtYWw+PHNwYW4gc3R5bGU9J2NvbG9yOiMxRjQ5N0QnPlRoYW5rcyw8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdjb2xvcjojMUY0OTdEJz48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdj
b2xvcjojMUY0OTdEJz5Kb2huPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1h
bD48c3BhbiBzdHlsZT0nY29sb3I6IzFGNDk3RCc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
PjxkaXY+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdjb2xvcjojMUY0OTdEJz5TZW50
IGZyb20gbXkgaVBob25lPG86cD48L286cD48L3NwYW4+PC9wPjwvZGl2PjxwIGNsYXNzPU1zb05v
cm1hbD48c3BhbiBzdHlsZT0nY29sb3I6IzFGNDk3RCc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPjxkaXYgc3R5bGU9J2JvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7
cGFkZGluZzowaW4gMGluIDBpbiA0LjBwdCc+PGRpdj48ZGl2IHN0eWxlPSdib3JkZXI6bm9uZTti
b3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbic+
PHAgY2xhc3M9TXNvTm9ybWFsPjxiPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQt
ZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjtjb2xvcjp3aW5kb3d0ZXh0Jz5Gcm9tOjwvc3Bh
bj48L2I+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6IlRhaG9tYSIs
InNhbnMtc2VyaWYiO2NvbG9yOndpbmRvd3RleHQnPiBFbGlvdCBMZWFyIFttYWlsdG86bGVhckBj
aXNjby5jb21dIDxicj48Yj5TZW50OjwvYj4gV2VkbmVzZGF5LCBBdWd1c3QgMTUsIDIwMTIgNTo0
NCBBTTxicj48Yj5Ubzo8L2I+IEpvaG4gRSBEcmFrZTxicj48Yj5DYzo8L2I+IGlhYkBpYWIub3Jn
OyBJRVRGIERpc2N1c3Npb248YnI+PGI+U3ViamVjdDo8L2I+IFJlOiBGVzogQWZmaXJtYXRpb24g
b2YgdGhlIE1vZGVybiBHbG9iYWwgU3RhbmRhcmRzIFBhcmFkaWdtPG86cD48L286cD48L3NwYW4+
PC9wPjwvZGl2PjwvZGl2PjxwIGNsYXNzPU1zb05vcm1hbD48bzpwPiZuYnNwOzwvbzpwPjwvcD48
cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21hcmdpbi1ib3R0b206MTIuMHB0Jz5IaSBKb2huLDxv
OnA+PC9vOnA+PC9wPjxkaXY+PHAgY2xhc3M9TXNvTm9ybWFsPk9uIDgvMTUvMTIgMjoxNSBQTSwg
Sm9obiBFIERyYWtlIHdyb3RlOjxvOnA+PC9vOnA+PC9wPjwvZGl2PjxibG9ja3F1b3RlIHN0eWxl
PSdtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQnPjxwIGNsYXNzPU1zb05vcm1h
bD48c3BhbiBzdHlsZT0nY29sb3I6IzFGNDk3RCc+Jm5ic3A7PC9zcGFuPjxzcGFuIHN0eWxlPSdm
b250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4gLCBzZXJpZiIsInNl
cmlmIic+PGJyPlRvIG1lIChhbmQgSSBzcGVhayBvbmx5IGZvciBtZSBoZXJlKSwgdGhlIHB1cnBv
c2Ugb2YgdGhpcyBkb2N1bWVudCBpcyB0byBhcnRpY3VsYXRlIHByaW5jaXBsZXMgdGhhdCBoYXZl
IG1hZGUgdGhlIEludGVybmV0IGEgc3VjY2Vzcy48L3NwYW4+PG86cD48L286cD48L3A+PGRpdiBz
dHlsZT0nYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBp
biAwaW4gMGluIDQuMHB0Jz48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2NvbG9yOiMx
RjQ5N0QnPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNw
YW4gc3R5bGU9J2NvbG9yOiMxRjQ5N0QnPkpEOiZuYnNwOyBUaGlzIHNlZW1zIGEgYml0IHByZXN1
bXB0dW91cyB0byBtZS48L3NwYW4+PG86cD48L286cD48L3A+PC9kaXY+PC9ibG9ja3F1b3RlPjxw
IGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWls
eToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYiJz48YnI+SXQncyBhbiBhc3NlcnRpb24uJm5ic3A7
IEkgd291bGRuJ3QgY2xhaW0sIGJ5IHRoZSB3YXksIHRoYXQgdGhpcyB3YXMgdGhlIG9ubHkgZmFj
dG9yLiZuYnNwOyBJTUhPLCBpdCB3YXMgYSBjb250cmlidXRpbmcgZmFjdG9yLiZuYnNwOyBNb29y
ZSdzIExhdyBhbmQgdGhlIGRldmVsb3BtZW50IG9mIHRlY2hub2xvZ3kgaW4gZ2VuZXJhbCBhbGwg
Y29udHJpYnV0ZWQsIGJ1dCB5b3UgaGFkIHRvIGhhdmUgYSBwcm9jZXNzIHRoYXQgd2FzIG9wZW4g
Zm9yIHRoZSB0ZWNobm9sb2d5IHRvIGZsb3VyaXNoLiZuYnNwOyBJTUhPIHRoaXMgaXMgd2h5IFNO
QSwgREVDTkVULCBBcHBsZXRhbGssIFhOUywgT1NJLCBhbmQgb3RoZXJzIGRpZCBub3Qgd2luLCB3
aGVyZSBJUCBkaWQuPGJyPjxicj48YnI+PG86cD48L286cD48L3NwYW4+PC9wPjxkaXYgc3R5bGU9
J2JvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowaW4gMGlu
IDBpbiA0LjBwdCc+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdjb2xvcjojMUY0OTdE
Jz4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0
eWxlPSdmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4gLCBzZXJp
ZiIsInNlcmlmIic+SXQgaXMgYSBtZWFucyB0byBpbnZpdGUgb3RoZXJzIHRvIHN1YnNjcmliZSB0
byB0aG9zZSBzYW1lIHByaW5jaXBsZXMsIGFuZCB0aGVyZSBhcmUgbWFueSBzdGFuZGFyZHMgb3Jn
YW5pemF0aW9ucyB0aGF0IGRvIG5vdC48L3NwYW4+PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNv
Tm9ybWFsPjxzcGFuIHN0eWxlPSdjb2xvcjojMUY0OTdEJz4mbmJzcDs8L3NwYW4+PG86cD48L286
cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdjb2xvcjojMUY0OTdEJz5KRDom
bmJzcDsgSSB3b3VsZCBiZSB3aWxsaW5nIHRvIGJldCB0aGF0IG5lYXJseSBldmVyeSBTRE8gd291
bGQgY2xhaW0gdGhleSBlbWJyYWNlIHRoZXNlIHNhbWUgcHJpbmNpcGxlcy48L3NwYW4+PG86cD48
L286cD48L3A+PC9kaXY+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6
MTIuMHB0O2ZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiInPjxicj5BbmQgdGhh
dCdzIGEgZmFpciBwb2ludC4mbmJzcDsgVGhlIHByb29mIGlzIGluIHRoZSBwdWRkaW5nLiZuYnNw
OyBJIGJlbGlldmUsIGFuZCBJIGtub3cgeW91IGRvIHRvbywgdGhhdCB0aGUgSUVURiBpdHNlbGYg
Y2FuIGV4cGxhaW4gaW4gY2xlYXIgaW5kaXNwdXRhYmxlIHRlcm1zIGhvdyBpdCBmdWxmaWxscyB0
aGUgcHJpbmNpcGxlcyBvZiBvcGVubmVzcy4mbmJzcDsgQW55b25lIGNhbiBqb2luIGEgV0cgbGlz
dC4mbmJzcDsgQW55b25lIGNhbiBzdWJtaXQgYW4gSW50ZXJuZXQtRHJhZnQsIGFueW9uZSBjYW4g
Y29tbWVudCBvbiB0aGF0IGRyYWZ0LCBhbnlvbmUgY2FuIHJlcXVlc3QgdGhhdCBkcmFmdCdzIGFk
dmFuY2VtZW50LCBhbnlvbmUgY2FuIGNvbW1lbnQgb24gb3IgY29udHJpYnV0ZSB0byBvciBvYmpl
Y3QgdG8gdGhhdCBkcmFmdCdzIGFkdmFuY2VtZW50LCBhbnlvbmUgY2FuIGJlIGEgcGFydCBvZiB0
aGUgbGVhZGVyc2hpcCAob25lIG5lZWRuJ3QgZXZlbiBoYXZlIGV2ZXIgcGFydGljaXBhdGVkIGlu
IHRoZSBJRVRGIGJlZm9yZSEhKS4mbmJzcDsgRGVjaXNpb25zIGFyZSBtYWRlIHRocm91Z2ggYSBj
b25zZW5zdXMgcHJvY2Vzcy4mbmJzcDsgVGhhdCBwcm9jZXNzIGlzIGRlc2lnbmVkIHRvIGJlIHRy
YW5zcGFyZW50LiZuYnNwOyBUaGVyZSBhcmUgYXBwZWxsYXRlIGF2ZW51ZXMgZm9yIGFidXNlIG9m
IHByb2Nlc3MuJm5ic3A7IFRoZXkgaGF2ZSB3b3JrZWQgYW5kIGFyZSB3b3JraW5nLiZuYnNwOyBJ
IGFtIHRvbGQgZm9yIGluc3RhbmNlIHRoYXQgYXQgdGhpcyB2ZXJ5IG1vbWVudCB0aGVyZSBpcyBh
biBhcHBlYWwgYmVmb3JlIHRoZSBhcHBsaWNhdGlvbnMgYXJlYSBkaXJlY3RvciB0aGF0IHNlZW1z
IHRvIG1lIHBhcnRpY3VsYXJseSBtZWF0eS4mbmJzcDsgVGhhdCdzIGdvb2QuJm5ic3A7IEl0J3Mg
aW1wb3J0YW50IHRoYXQgcGVvcGxlIGtub3cgdGhhdCB0aGVyZSBpcyBhbiBhcHBlYWxzIGF2ZW51
ZSBhdmFpbGFibGUuPGJyPjxicj5UaGUgVzNDIGlzIHZlcnkgc2ltaWxhci4mbmJzcDsgVGhlIElF
RUUgU0EgaXMgYWxzbyBzaW1pbGFyLiZuYnNwOyBTbyBhcmUgb3RoZXJzLCBhbmQgdGhhdCdzIGZp
bmUuJm5ic3A7IEJ1dCB0aGVyZSBhcmUgbWFueSBvdGhlciBvcmdhbml6YXRpb25zIHdoZXJlIGl0
J3MganVzdCBub3QgdGhlIGNhc2UsIGFuZCBzby4uLjxicj48YnI+PGJyPjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD48ZGl2IHN0eWxlPSdib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEu
NXB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNC4wcHQnPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBz
dHlsZT0nY29sb3I6IzFGNDk3RCc+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPjxwIGNsYXNz
PU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseToiVGlt
ZXMgTmV3IFJvbWFuICwgc2VyaWYiLCJzZXJpZiInPkN1c3RvbWVycyBhbmQgc29jaWV0eSBjYW4g
ZGVtYW5kIGJldHRlciwgYW5kIHRoaXMgaXMgYW4gYXZlbnVlIGZvciB0aGF0Ljwvc3Bhbj48bzpw
PjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2NvbG9yOiMxRjQ5N0Qn
PiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21h
cmdpbi1ib3R0b206MTIuMHB0Jz48c3BhbiBzdHlsZT0nY29sb3I6IzFGNDk3RCc+SkQ6Jm5ic3A7
IEhvdywgZXhhY3RseT88L3NwYW4+PG86cD48L286cD48L3A+PC9kaXY+PHAgY2xhc3M9TXNvTm9y
bWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiJUaW1lcyBOZXcg
Um9tYW4iLCJzZXJpZiInPjxicj5Ib3cgYWJvdXQgYSBwaG9uZSBjYWxsPyZuYnNwOyBBIGJsb2c/
Jm5ic3A7IEEgcHJlc3MgcmVsZWFzZT8mbmJzcDsgTGF3cyBhbmQgcmVndWxhdGlvbnMgcmVxdWly
aW5nIHRoZSB1c2Ugb2Ygc3RhbmRhcmRzIGJhc2VkIG9uIHRob3NlIHByaW5jaXBsZXM/PGJyPjxi
cj5FbGlvdDxvOnA+PC9vOnA+PC9zcGFuPjwvcD48L2Rpdj48L2Rpdj48L2JvZHk+PC9odG1sPg==

--_000_5E893DB832F57341992548CDBB333163A5A9B46662EMBX01HQjnprn_--

From abdussalambaryun@gmail.com  Wed Aug 15 06:28:40 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B83E421F8867 for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 06:28:40 -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.111,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gvsRobO7QS2U for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 06:28:40 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 13C7621F880D for <ietf@ietf.org>; Wed, 15 Aug 2012 06:28:39 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so1712986vcb.31 for <ietf@ietf.org>; Wed, 15 Aug 2012 06:28:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=attGNiflWciDbi/SuW/apwtdnEvR32gDPL5nFf9ncmI=; b=o2r5MViPoX72DgSKyzc0fT/U/90+0rxejsQoCnQfykzXNw++Xe0Z9qPiJyyhiqVkAl fckFd0sJrPwffN6JnA0NQzUUiNFlFoLumqyRzQYg7J2avbbC7Ocbo6BaIMTUST8zS7FJ Tj+RH023o27t/tlvT6KkPpG60P787GUXLkvdg6eAp4+8Kx2jtW4Z/vRGR3/PBi5PKA4W 1TOx2Gn/IUNnVS0Q+vl65Y8whG0YK/oFQ9If4KXEkfPQtv5NzZ2YbTpftJZqgkiJ/b/u 90qr8h9vcj/UwWO9Povplo/LMACJvcLCzaG7P+vatB4BUxzJMxr+BV1cEyTjhqYZSunJ qoFg==
MIME-Version: 1.0
Received: by 10.52.99.138 with SMTP id eq10mr11187202vdb.25.1345037319487; Wed, 15 Aug 2012 06:28:39 -0700 (PDT)
Received: by 10.220.62.77 with HTTP; Wed, 15 Aug 2012 06:28:39 -0700 (PDT)
Date: Wed, 15 Aug 2012 14:28:39 +0100
Message-ID: <CADnDZ88ZxWGXau6de5YEFXbd-_vpxt4r08X4xHUfydzknnX9Ug@mail.gmail.com>
Subject: Re: FW: Affirmation of the Modern Global Standards Paradigm
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: jdrake@juniper.net
Content-Type: multipart/alternative; boundary=20cf3071cc4aa33f6204c74de765
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, 15 Aug 2012 13:28:40 -0000

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

Hi John,

>Does this document actually have a purpose, and if so, what is it?

IMO the document introduces important statements (purpose and objectives)
so that other organisations and SDOs recognise while interacting with IETF.
It may look simple or known, but necessary for IETF future cooperations.

I agree that your question is very important and that the best person to
answer is the Chair of IETF or IAB.

AB

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

<div>Hi John,</div><div>=A0</div><div>&gt;Does this document actually have =
a purpose, and if so, what is it?<br><br>IMO the document introduces import=
ant statements (purpose and objectives) so that other organisations and SDO=
s recognise while interacting with IETF. It may look simple or known, but n=
ecessary for IETF future cooperations.</div>
<div>=A0</div><div>I agree that your question is very important and that th=
e best person to answer is the Chair of IETF or IAB. </div><div>=A0</div><d=
iv>AB</div>

--20cf3071cc4aa33f6204c74de765--

From jdrake@juniper.net  Wed Aug 15 06:47:58 2012
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 9071A21F88C9 for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 06:47:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.497
X-Spam-Level: 
X-Spam-Status: No, score=-5.497 tagged_above=-999 required=5 tests=[AWL=1.101,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uRGBuHV-0fjs for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 06:47:57 -0700 (PDT)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id 26C9C21F88CB for <ietf@ietf.org>; Wed, 15 Aug 2012 06:47:55 -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 DSNKUCuoh5E5ICnGAHWmX1kjesuAvojAYNWE@postini.com; Wed, 15 Aug 2012 06:47:55 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; Wed, 15 Aug 2012 06:46:03 -0700
From: John E Drake <jdrake@juniper.net>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Wed, 15 Aug 2012 06:46:02 -0700
Subject: RE: FW: Affirmation of the Modern Global Standards Paradigm
Thread-Topic: FW: Affirmation of the Modern Global Standards Paradigm
Thread-Index: Ac166eJvLKLuN4d1StiKUBM3tx6iEQAASl+w
Message-ID: <5E893DB832F57341992548CDBB333163A5A9B46674@EMBX01-HQ.jnpr.net>
References: <CADnDZ88ZxWGXau6de5YEFXbd-_vpxt4r08X4xHUfydzknnX9Ug@mail.gmail.com>
In-Reply-To: <CADnDZ88ZxWGXau6de5YEFXbd-_vpxt4r08X4xHUfydzknnX9Ug@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_5E893DB832F57341992548CDBB333163A5A9B46674EMBX01HQjnprn_"
MIME-Version: 1.0
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Aug 2012 13:47:58 -0000

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

AB,

I don't think the principles articulated in this document will come as a su=
rprise to any SDO with which the IETF interacts and I don't think this docu=
ment will prevent another SDO from acting badly wrt the IETF if it so choos=
es.  Also, bear in mind that 'acting badly' is entirely subjective.

For example, if you were to ask the ITU leadership if they 'acted badly' du=
ring the MPLS-TP imbroglio, I think they would counter that it was the IETF=
 that 'acted badly'.  In fact, I have seen them say exactly this.

And lest we forget, we had a much more comprehensive agreement in place for=
 MPLS-TP.

Thanks,

John

Sent from my iPhone

From: Abdussalam Baryun [mailto:abdussalambaryun@gmail.com]
Sent: Wednesday, August 15, 2012 6:29 AM
To: John E Drake
Cc: ietf
Subject: Re: FW: Affirmation of the Modern Global Standards Paradigm

Hi John,

>Does this document actually have a purpose, and if so, what is it?

IMO the document introduces important statements (purpose and objectives) s=
o that other organisations and SDOs recognise while interacting with IETF. =
It may look simple or known, but necessary for IETF future cooperations.

I agree that your question is very important and that the best person to an=
swer is the Chair of IETF or IAB.

AB

--_000_5E893DB832F57341992548CDBB333163A5A9B46674EMBX01HQjnprn_
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.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;}
--></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'>AB,<o:p><=
/o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-f=
amily:"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","sa=
ns-serif";color:#1F497D'>I don&#8217;t think the principles articulated in =
this document will come as a surprise to any SDO with which the IETF intera=
cts and I don&#8217;t think this document will prevent another SDO from act=
ing badly wrt the IETF if it so chooses.&nbsp; Also, bear in mind that &#82=
16;acting badly&#8217; is entirely subjective.<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=
'>For example, if you were to ask the ITU leadership if they &#8216;acted b=
adly&#8217; during the MPLS-TP imbroglio, I think they would counter that i=
t was the IETF that &#8216;acted badly&#8217;.&nbsp; In fact, I have seen t=
hem say exactly this.<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p=
>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif";color:#1F497D'>And lest we forget, we =
had a much more comprehensive agreement in place for MPLS-TP.<o:p></o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"C=
alibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3D=
MsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif=
";color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=3DMsoNormal><span st=
yle=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11=
.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>John<o:p></o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMs=
oNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";=
color:#1F497D'>Sent from my iPhone<o:p></o:p></span></p><p class=3DMsoNorma=
l><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-left:=
solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style=3D'border:none;=
border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNor=
mal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>F=
rom:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-s=
erif"'> Abdussalam Baryun [mailto:abdussalambaryun@gmail.com] <br><b>Sent:<=
/b> Wednesday, August 15, 2012 6:29 AM<br><b>To:</b> John E Drake<br><b>Cc:=
</b> ietf<br><b>Subject:</b> Re: FW: Affirmation of the Modern Global Stand=
ards Paradigm<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&n=
bsp;</o:p></p><div><p class=3DMsoNormal>Hi John,<o:p></o:p></p></div><div><=
p class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal>&g=
t;Does this document actually have a purpose, and if so, what is it?<br><br=
>IMO the document introduces important statements (purpose and objectives) =
so that other organisations and SDOs recognise while interacting with IETF.=
 It may look simple or known, but necessary for IETF future cooperations.<o=
:p></o:p></p></div><div><p class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><di=
v><p class=3DMsoNormal>I agree that your question is very important and tha=
t the best person to answer is the Chair of IETF or IAB. <o:p></o:p></p></d=
iv><div><p class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><div><p class=3DMso=
Normal>AB<o:p></o:p></p></div></div></div></body></html>=

--_000_5E893DB832F57341992548CDBB333163A5A9B46674EMBX01HQjnprn_--

From abdussalambaryun@gmail.com  Wed Aug 15 06:57:26 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 598DC21F8668 for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 06:57:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.488
X-Spam-Level: 
X-Spam-Status: No, score=-3.488 tagged_above=-999 required=5 tests=[AWL=0.110,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WvUksvWwh11R for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 06:57:25 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8AAED21F87E3 for <ietf@ietf.org>; Wed, 15 Aug 2012 06:57:25 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so1736726vbb.31 for <ietf@ietf.org>; Wed, 15 Aug 2012 06:57:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Jzw2nbKiumXQEyeALxuZhIwdzJqUhw9vZI95hLcjqO4=; b=zv88CpW8xHj9SvQoWaxTv/aETdzV6O6DQCuDJkTzVnP9kwjOaHD2vrF/OhGQ7N3j5D 8lOYVyycQX2xo0A15Sq7I01HX1NE0p3zry4VXUr+r2FSGnJsnuefBku5diizxYEJFDkk lJzW/llw6M3QKwkIDUJ5jrHL3PT8kQvfz+zClA6PPoSBxKC2prqrhDWnqbWLwHeF7Acx z7d/CU4imigj5sA7rHikknYGdT2J8l+TLkTEJ0xxvC6YmEK+6HZdn0uTb7oT1rWWHP22 ldtIDRu7ushm6K8idh2ijjjnhSj1eBu6gTNY0OQ5m7jo+1SD3maZC+kuxdHoCVI/Dd9z xJFw==
MIME-Version: 1.0
Received: by 10.58.247.138 with SMTP id ye10mr14654710vec.20.1345039044954; Wed, 15 Aug 2012 06:57:24 -0700 (PDT)
Received: by 10.220.62.77 with HTTP; Wed, 15 Aug 2012 06:57:24 -0700 (PDT)
In-Reply-To: <5E893DB832F57341992548CDBB333163A5A9B46674@EMBX01-HQ.jnpr.net>
References: <CADnDZ88ZxWGXau6de5YEFXbd-_vpxt4r08X4xHUfydzknnX9Ug@mail.gmail.com> <5E893DB832F57341992548CDBB333163A5A9B46674@EMBX01-HQ.jnpr.net>
Date: Wed, 15 Aug 2012 14:57:24 +0100
Message-ID: <CADnDZ8-w42UTibfWcMO0CkjEUZY+9Wfh_nPmi_=PP5nmp2h_4g@mail.gmail.com>
Subject: Re: FW: Affirmation of the Modern Global Standards Paradigm
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: John E Drake <jdrake@juniper.net>
Content-Type: multipart/alternative; boundary=047d7bea44ba7bca2c04c74e4e5e
Cc: iab@iab.org, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Aug 2012 13:57:26 -0000

--047d7bea44ba7bca2c04c74e4e5e
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

John,

Could you suggest a solution to this issue or an additional statements to
the document, I think then the document may need amendment, to consider
your advise/experience.

AB

On Wed, Aug 15, 2012 at 2:46 PM, John E Drake <jdrake@juniper.net> wrote:

> AB,****
>
> ** **
>
> I don=92t think the principles articulated in this document will come as =
a
> surprise to any SDO with which the IETF interacts and I don=92t think thi=
s
> document will prevent another SDO from acting badly wrt the IETF if it so
> chooses.  Also, bear in mind that =91acting badly=92 is entirely subjecti=
ve.**
> **
>
> ** **
>
> For example, if you were to ask the ITU leadership if they =91acted badly=
=92
> during the MPLS-TP imbroglio, I think they would counter that it was the
> IETF that =91acted badly=92.  In fact, I have seen them say exactly this.=
****
>
> ** **
>
> And lest we forget, we had a much more comprehensive agreement in place
> for MPLS-TP.****
>
> ** **
>
> Thanks,****
>
> ** **
>
> John****
>
> ** **
>
> Sent from my iPhone****
>
> ** **
>
> *From:* Abdussalam Baryun [mailto:abdussalambaryun@gmail.com]
> *Sent:* Wednesday, August 15, 2012 6:29 AM
> *To:* John E Drake
> *Cc:* ietf
> *Subject:* Re: FW: Affirmation of the Modern Global Standards Paradigm***=
*
>
> ** **
>
> Hi John,****
>
>  ****
>
> >Does this document actually have a purpose, and if so, what is it?
>
> IMO the document introduces important statements (purpose and objectives)
> so that other organisations and SDOs recognise while interacting with IET=
F.
> It may look simple or known, but necessary for IETF future cooperations.*=
*
> **
>
>  ****
>
> I agree that your question is very important and that the best person to
> answer is the Chair of IETF or IAB. ****
>
>  ****
>
> AB****
>

--047d7bea44ba7bca2c04c74e4e5e
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div>John,</div><div>=A0</div><div>Could you suggest a solution to this iss=
ue or an additional statements to the document, I think then the document m=
ay need amendment, to consider your advise/experience.</div><div>=A0</div><=
div>
AB<br><br></div><div class=3D"gmail_quote">On Wed, Aug 15, 2012 at 2:46 PM,=
 John E Drake <span dir=3D"ltr">&lt;<a href=3D"mailto:jdrake@juniper.net" t=
arget=3D"_blank">jdrake@juniper.net</a>&gt;</span> wrote:<br><blockquote st=
yle=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,=
204,204);border-left-width:1px;border-left-style:solid" class=3D"gmail_quot=
e">
<div lang=3D"EN-US" vlink=3D"purple" link=3D"blue"><div><p class=3D"MsoNorm=
al"><span style=3D"color:rgb(31,73,125);font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;;font-size:11pt">AB,<u></u><u></u></span></p><p class=3D=
"MsoNormal">
<span style=3D"color:rgb(31,73,125);font-family:&quot;Calibri&quot;,&quot;s=
ans-serif&quot;;font-size:11pt"><u></u>=A0<u></u></span></p><p class=3D"Mso=
Normal"><span style=3D"color:rgb(31,73,125);font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;font-size:11pt">I don=92t think the principles arti=
culated in this document will come as a surprise to any SDO with which the =
IETF interacts and I don=92t think this document will prevent another SDO f=
rom acting badly wrt the IETF if it so chooses.=A0 Also, bear in mind that =
=91acting badly=92 is entirely subjective.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt"><u></u>=A0<u></u></s=
pan></p><p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt">For example,=
 if you were to ask the ITU leadership if they =91acted badly=92 during the=
 MPLS-TP imbroglio, I think they would counter that it was the IETF that =
=91acted badly=92.=A0 In fact, I have seen them say exactly this.<u></u><u>=
</u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt"><u></u>=A0<u></u></s=
pan></p><p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt">And lest we =
forget, we had a much more comprehensive agreement in place for MPLS-TP.<u>=
</u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt"><u></u>=A0<u></u></s=
pan></p><p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt">Thanks,<u></=
u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt"><u></u>=A0<u></u></s=
pan></p><p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt">John<u></u><=
u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt"><u></u>=A0<u></u></s=
pan></p><p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt">Sent from my=
 iPhone<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt"><u></u>=A0<u></u></s=
pan></p><div style=3D"border-width:medium medium medium 1.5pt;border-style:=
none none none solid;border-color:currentColor currentColor currentColor bl=
ue;padding:0in 0in 0in 4pt">
<div><div style=3D"border-width:1pt medium medium;border-style:solid none n=
one;border-color:rgb(181,196,223) currentColor currentColor;padding:3pt 0in=
 0in"><p class=3D"MsoNormal"><b><span style=3D"font-family:&quot;Tahoma&quo=
t;,&quot;sans-serif&quot;;font-size:10pt">From:</span></b><span style=3D"fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;font-size:10pt"> Abduss=
alam Baryun [mailto:<a href=3D"mailto:abdussalambaryun@gmail.com" target=3D=
"_blank">abdussalambaryun@gmail.com</a>] <br>
<b>Sent:</b> Wednesday, August 15, 2012 6:29 AM<br><b>To:</b> John E Drake<=
br><b>Cc:</b> ietf<br><b>Subject:</b> Re: FW: Affirmation of the Modern Glo=
bal Standards Paradigm<u></u><u></u></span></p></div></div><div><div class=
=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p><div><p class=3D"MsoNormal">Hi =
John,<u></u><u></u></p></div><div><p class=3D"MsoNormal">=A0<u></u><u></u><=
/p></div><div><p class=3D"MsoNormal">&gt;Does this document actually have a=
 purpose, and if so, what is it?<br>
<br>IMO the document introduces important statements (purpose and objective=
s) so that other organisations and SDOs recognise while interacting with IE=
TF. It may look simple or known, but necessary for IETF future cooperations=
.<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">=A0<u></u><u></u></p></div><div><p class=
=3D"MsoNormal">I agree that your question is very important and that the be=
st person to answer is the Chair of IETF or IAB. <u></u><u></u></p></div><d=
iv>
<p class=3D"MsoNormal">=A0<u></u><u></u></p></div><div><p class=3D"MsoNorma=
l">AB<u></u><u></u></p></div></div></div></div></div></div></blockquote></d=
iv><br>

--047d7bea44ba7bca2c04c74e4e5e--

From jdrake@juniper.net  Wed Aug 15 07:23:21 2012
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 69BF221F87DD for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 07:23:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.538
X-Spam-Level: 
X-Spam-Status: No, score=-5.538 tagged_above=-999 required=5 tests=[AWL=1.060,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4TMGSbP3mr1S for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 07:23:19 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id 1230521F879A for <ietf@ietf.org>; Wed, 15 Aug 2012 07:23:19 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUCuw1d/KHTmt1v031cmtfayke6A2FA+3@postini.com; Wed, 15 Aug 2012 07:23:19 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB03-HQ.jnpr.net ([::1]) with mapi; Wed, 15 Aug 2012 07:22:16 -0700
From: John E Drake <jdrake@juniper.net>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Wed, 15 Aug 2012 07:22:15 -0700
Subject: RE: FW: Affirmation of the Modern Global Standards Paradigm
Thread-Topic: FW: Affirmation of the Modern Global Standards Paradigm
Thread-Index: Ac167e7L+G12CRtuQJG5i7jRsasLEQAAuP6g
Message-ID: <5E893DB832F57341992548CDBB333163A5A9B46695@EMBX01-HQ.jnpr.net>
References: <CADnDZ88ZxWGXau6de5YEFXbd-_vpxt4r08X4xHUfydzknnX9Ug@mail.gmail.com> <5E893DB832F57341992548CDBB333163A5A9B46674@EMBX01-HQ.jnpr.net> <CADnDZ8-w42UTibfWcMO0CkjEUZY+9Wfh_nPmi_=PP5nmp2h_4g@mail.gmail.com>
In-Reply-To: <CADnDZ8-w42UTibfWcMO0CkjEUZY+9Wfh_nPmi_=PP5nmp2h_4g@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_5E893DB832F57341992548CDBB333163A5A9B46695EMBX01HQjnprn_"
MIME-Version: 1.0
Cc: "iab@iab.org" <iab@iab.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Aug 2012 14:23:21 -0000

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

AB,

I couldn't answer this until I get an answer to my original question regard=
ing the document's purpose.  I also have a related question, viz, is there =
a plan of some sort of which this document is a component, or is the docume=
nt simply a one-off?

Thanks,

John

Sent from my iPhone

From: Abdussalam Baryun [mailto:abdussalambaryun@gmail.com]
Sent: Wednesday, August 15, 2012 6:57 AM
To: John E Drake
Cc: ietf; iab@iab.org
Subject: Re: FW: Affirmation of the Modern Global Standards Paradigm

John,

Could you suggest a solution to this issue or an additional statements to t=
he document, I think then the document may need amendment, to consider your=
 advise/experience.

AB
On Wed, Aug 15, 2012 at 2:46 PM, John E Drake <jdrake@juniper.net<mailto:jd=
rake@juniper.net>> wrote:
AB,

I don't think the principles articulated in this document will come as a su=
rprise to any SDO with which the IETF interacts and I don't think this docu=
ment will prevent another SDO from acting badly wrt the IETF if it so choos=
es.  Also, bear in mind that 'acting badly' is entirely subjective.

For example, if you were to ask the ITU leadership if they 'acted badly' du=
ring the MPLS-TP imbroglio, I think they would counter that it was the IETF=
 that 'acted badly'.  In fact, I have seen them say exactly this.

And lest we forget, we had a much more comprehensive agreement in place for=
 MPLS-TP.

Thanks,

John

Sent from my iPhone

From: Abdussalam Baryun [mailto:abdussalambaryun@gmail.com<mailto:abdussala=
mbaryun@gmail.com>]
Sent: Wednesday, August 15, 2012 6:29 AM
To: John E Drake
Cc: ietf
Subject: Re: FW: Affirmation of the Modern Global Standards Paradigm

Hi John,

>Does this document actually have a purpose, and if so, what is it?

IMO the document introduces important statements (purpose and objectives) s=
o that other organisations and SDOs recognise while interacting with IETF. =
It may look simple or known, but necessary for IETF future cooperations.

I agree that your question is very important and that the best person to an=
swer is the Chair of IETF or IAB.

AB


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{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;}
--></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'>AB,<o:p><=
/o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-f=
amily:"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","sa=
ns-serif";color:#1F497D'>I couldn&#8217;t answer this until I get an answer=
 to my original question regarding the document&#8217;s purpose.&nbsp; I al=
so have a related question, viz, is there a plan of some sort of which this=
 document is a component, or is the document simply a one-off?<o:p></o:p></=
span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"=
Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=3DMsoNormal><span=
 style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D=
'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size=
:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>John<o:p></o:p></=
span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"=
Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'>Sent from my iPhone<o:p></o:p></span></p><p class=3DMso=
Normal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";c=
olor:#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;padding:3.0pt 0in 0in 0in'><p class=3DM=
soNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-seri=
f"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","s=
ans-serif"'> Abdussalam Baryun [mailto:abdussalambaryun@gmail.com] <br><b>S=
ent:</b> Wednesday, August 15, 2012 6:57 AM<br><b>To:</b> John E Drake<br><=
b>Cc:</b> ietf; iab@iab.org<br><b>Subject:</b> Re: FW: Affirmation of the M=
odern Global Standards Paradigm<o:p></o:p></span></p></div></div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>John,<o:p></o:p=
></p></div><div><p class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><div><p cla=
ss=3DMsoNormal>Could you suggest a solution to this issue or an additional =
statements to the document, I think then the document may need amendment, t=
o consider your advise/experience.<o:p></o:p></p></div><div><p class=3DMsoN=
ormal>&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'margin-=
bottom:12.0pt'>AB<o:p></o:p></p></div><div><p class=3DMsoNormal>On Wed, Aug=
 15, 2012 at 2:46 PM, John E Drake &lt;<a href=3D"mailto:jdrake@juniper.net=
" target=3D"_blank">jdrake@juniper.net</a>&gt; wrote:<o:p></o:p></p><div><d=
iv><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif=
";color:#1F497D'>AB,</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso=
-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:1=
1.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p><=
/o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-b=
ottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif";color:#1F497D'>I don&#8217;t think the principles articulated in th=
is document will come as a surprise to any SDO with which the IETF interact=
s and I don&#8217;t think this document will prevent another SDO from actin=
g badly wrt the IETF if it so chooses.&nbsp; Also, bear in mind that &#8216=
;acting badly&#8217; is entirely subjective.</span><o:p></o:p></p><p class=
=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><=
span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F=
497D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-=
top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;fo=
nt-family:"Calibri","sans-serif";color:#1F497D'>For example, if you were to=
 ask the ITU leadership if they &#8216;acted badly&#8217; during the MPLS-T=
P imbroglio, I think they would counter that it was the IETF that &#8216;ac=
ted badly&#8217;.&nbsp; In fact, I have seen them say exactly this.</span><=
o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-mar=
gin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNorma=
l style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>And =
lest we forget, we had a much more comprehensive agreement in place for MPL=
S-TP.</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt=
:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-fami=
ly:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><p cla=
ss=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'=
><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#=
1F497D'>Thanks,</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-marg=
in-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt=
;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p>=
</p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom=
-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-seri=
f";color:#1F497D'>John</span><o:p></o:p></p><p class=3DMsoNormal style=3D'm=
so-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size=
:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p=
></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin=
-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri","sa=
ns-serif";color:#1F497D'>Sent from my iPhone</span><o:p></o:p></p><p class=
=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><=
span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F=
497D'>&nbsp;</span><o:p></o:p></p><div style=3D'border:none;border-left:sol=
id windowtext 1.5pt;padding:0in 0in 0in 4.0pt;border-color:currentColor cur=
rentColor currentColor blue'><div><div style=3D'border:none;border-top:soli=
d windowtext 1.0pt;padding:3.0pt 0in 0in 0in;border-color:currentColor curr=
entColor'><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-=
bottom-alt:auto'><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","s=
ans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Ta=
homa","sans-serif"'> Abdussalam Baryun [mailto:<a href=3D"mailto:abdussalam=
baryun@gmail.com" target=3D"_blank">abdussalambaryun@gmail.com</a>] <br><b>=
Sent:</b> Wednesday, August 15, 2012 6:29 AM<br><b>To:</b> John E Drake<br>=
<b>Cc:</b> ietf<br><b>Subject:</b> Re: FW: Affirmation of the Modern Global=
 Standards Paradigm</span><o:p></o:p></p></div></div><div><div><p class=3DM=
soNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp=
;<o:p></o:p></p><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;=
mso-margin-bottom-alt:auto'>Hi John,<o:p></o:p></p></div><div><p class=3DMs=
oNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;=
<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:=
auto;mso-margin-bottom-alt:auto'>&gt;Does this document actually have a pur=
pose, and if so, what is it?<br><br>IMO the document introduces important s=
tatements (purpose and objectives) so that other organisations and SDOs rec=
ognise while interacting with IETF. It may look simple or known, but necess=
ary for IETF future cooperations.<o:p></o:p></p></div><div><p class=3DMsoNo=
rmal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:=
p></o:p></p></div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:aut=
o;mso-margin-bottom-alt:auto'>I agree that your question is very important =
and that the best person to answer is the Chair of IETF or IAB. <o:p></o:p>=
</p></div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-ma=
rgin-bottom-alt:auto'>&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>AB<o:p></o:p><=
/p></div></div></div></div></div></div></div><p class=3DMsoNormal><o:p>&nbs=
p;</o:p></p></div></div></body></html>=

--_000_5E893DB832F57341992548CDBB333163A5A9B46695EMBX01HQjnprn_--

From hannes.tschofenig@gmx.net  Wed Aug 15 07:33:32 2012
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A84E21F877C for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 07:33:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.608
X-Spam-Level: 
X-Spam-Status: No, score=-102.608 tagged_above=-999 required=5 tests=[AWL=-0.009, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CV8xBlQlcikR for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 07:33:31 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 68D2E21F8702 for <ietf@ietf.org>; Wed, 15 Aug 2012 07:33:31 -0700 (PDT)
Received: (qmail invoked by alias); 15 Aug 2012 14:33:30 -0000
Received: from a88-115-216-191.elisa-laajakaista.fi (EHLO [192.168.100.105]) [88.115.216.191] by mail.gmx.net (mp035) with SMTP; 15 Aug 2012 16:33:30 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/aNDlB4Xfa8DqgLwn/v5hn9FLCpRYeHLJN+DHPs8 oGE4GIYeChG/Yv
Subject: Re: Affirmation of the Modern Global Standards Paradigm
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: <5E893DB832F57341992548CDBB333163A5A9B4665D@EMBX01-HQ.jnpr.net>
Date: Wed, 15 Aug 2012 17:33:28 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <B8A47AD5-2038-4B59-BA43-CE243DE7B33F@gmx.net>
References: <5E893DB832F57341992548CDBB333163A5A9B462FF@EMBX01-HQ.jnpr.net> <502B40B7.8050100@cisco.com> <502B48E8.7060104@gmail.com> <5E893DB832F57341992548CDBB333163A5A9B46658@EMBX01-HQ.jnpr.net> <8972B876-DD01-474E-9234-0133DC9DC119@gmx.net> <5E893DB832F57341992548CDBB333163A5A9B4665D@EMBX01-HQ.jnpr.net>
To: John E Drake <jdrake@juniper.net>
X-Mailer: Apple Mail (2.1084)
X-Y-GMX-Trusted: 0
Cc: "iab@iab.org" <iab@iab.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, 15 Aug 2012 14:33:32 -0000

Hi John,=20

On Aug 15, 2012, at 3:41 PM, John E Drake wrote:

> JD:  To what purpose?  As an aside, I get the 'feel-good' aspect, but =
is there anything more?

I like the term - IAB documents as 'feel-good' publications.=20

The IAB publishes a variety of different documents. Some of them are =
formal communication interactions with other organizations and others =
are documenting topics that could be of interest to the IETF community =
or even beyond. These documents are not enforceable in a legal sense =
(which is good).=20

The content of this specific document did not surprise you and, as a =
regular IETF participant, it shouldn't. You look at the list of =
principles and they sound familiar - they make sense (at least to most =
of us, as folks noted in this discussion thread). The 'Openness', for =
example, is in my view extremely important since it allows relevant =
stakeholders to participate: Think about how low the barrier is to =
participate in the IETF. If you believe that the process has any impact =
on the quality of the specifications then the principles listed in the =
document may resonate with you.=20

Many may consider these principles as so obvious that they are not =
worthwhile to write down. Unfortunately, they are not as obvious as one =
might think. There are other ways to do standardization and, as we have =
seen in the discussions on this list, some would like to change the =
rules of the game. I believe that this will have negative consequences =
for the Internet eco-system and for the speed of innovation we had =
gotten so used to.=20

Whether this document can prevent bad things from happening is of course =
a separate story but it, at least, captures the views of a list of =
organizations active in Internet standardization.=20

I hope that this makes sense to you.=20

Ciao
Hannes




From brian.e.carpenter@gmail.com  Wed Aug 15 09:09:01 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49E9921F863C for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 09:09:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.504
X-Spam-Level: 
X-Spam-Status: No, score=-101.504 tagged_above=-999 required=5 tests=[AWL=0.187, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cN94uS04LyYD for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 09:09:00 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8165221F84C9 for <ietf@ietf.org>; Wed, 15 Aug 2012 09:09:00 -0700 (PDT)
Received: by wgbdr13 with SMTP id dr13so1036864wgb.13 for <ietf@ietf.org>; Wed, 15 Aug 2012 09:08:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=+seDtCdyxyKmG9UFVbTPUFCS/ccjQGUkrz6PyHAr5iM=; b=fdFmqiJ+Q+dM35jSNPg6gwb+WBH6gsx4/VbFvvSgW5kky4hT21NmMDHrz4V/AZCjW3 6ZA0+FOJKAXOcevRI/zP3rNgwZ6sL0WOwWHR+zQD15oV7OrXnXNV9Ohw4VTkY7p6PJGy AVyPJLQsegfPkOPIjoXdNK8ODiKSCUt4FN1Pcqr6KTiorYW9YmFE1YOB4YCsbLsP6Jdm MEpIABRIg2Zdgwd016MNN1GxRH4YBPOoTuhGRAOZ5l3WLDvEMCOVw+5+l03MT/dHL5wL sn+fpDo5thKBSertoa1gqqy+XpODesICOKRJIt2fFHXfoAt9ePWOorXgfkYdZYGT9Jzx BLvw==
Received: by 10.216.137.32 with SMTP id x32mr9777493wei.95.1345046939559; Wed, 15 Aug 2012 09:08:59 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-218-63.as13285.net. [2.102.218.63]) by mx.google.com with ESMTPS id o2sm5655753wiz.11.2012.08.15.09.08.57 (version=SSLv3 cipher=OTHER); Wed, 15 Aug 2012 09:08:58 -0700 (PDT)
Message-ID: <502BC99F.2090704@gmail.com>
Date: Wed, 15 Aug 2012 17:09:03 +0100
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 E Drake <jdrake@juniper.net>
Subject: Re: Affirmation of the Modern Global Standards Paradigm
References: <5E893DB832F57341992548CDBB333163A5A9B462FF@EMBX01-HQ.jnpr.net> <502B40B7.8050100@cisco.com> <502B48E8.7060104@gmail.com> <5E893DB832F57341992548CDBB333163A5A9B46658@EMBX01-HQ.jnpr.net> <8972B876-DD01-474E-9234-0133DC9DC119@gmx.net> <5E893DB832F57341992548CDBB333163A5A9B4665D@EMBX01-HQ.jnpr.net> <B8A47AD5-2038-4B59-BA43-CE243DE7B33F@gmx.net>
In-Reply-To: <B8A47AD5-2038-4B59-BA43-CE243DE7B33F@gmx.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "iab@iab.org" <iab@iab.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, 15 Aug 2012 16:09:01 -0000

On Aug 15, 2012, at 3:41 PM, John E Drake wrote:

>> JD:  To what purpose?  As an aside, I get the 'feel-good' aspect, but is there anything more?

When RFC 1984 was published, I was serving as IAB Chair and found myself invited
here and there to give talks to men in suits. Since crypto policy was a very hot
topic, it proved extremely useful to have a policy document to cite rather than
an audio recording of the Danbury plenary. Whether RFC 1984 had a significant
effect on the evolution of crypto policy is another matter, of course, but it
was a useful tool for the debate.

I think this Affirmation will be a good tool for the ongoing debate about standards
policy. As another thread has made clear, if that debate went badly, life for the
IETF could become very unpleasant.

    Brian

From sm@resistor.net  Wed Aug 15 09:17:46 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F4DB21F87F2; Wed, 15 Aug 2012 09:17:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.489
X-Spam-Level: 
X-Spam-Status: No, score=-102.489 tagged_above=-999 required=5 tests=[AWL=0.110, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KkI-xSRZCbz1; Wed, 15 Aug 2012 09:17:46 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BE3D21F880B; Wed, 15 Aug 2012 09:17:45 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q7FGHaJA018957; Wed, 15 Aug 2012 09:17:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1345047461; bh=2omoYgh9IKCQrIgPW54bkTMUz5w+Jt19mZKuPu0fhmY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=iyF3ngqoKLJb6eRBZq1Lq05tWomjTYJpD4JDuS4HbOW8sMgnlmXibDpdpfjx+A5bC 1URi9Z9aGoT7kU8FQADONZgOcubs3hAntpf1ItrMeKxBUs/Y34mRICGSEuj4FLYeHv eVw5wJ3OUODCXEvzrGXvYjLHVec2BXs5PzTTAWC8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1345047461; i=@resistor.net; bh=2omoYgh9IKCQrIgPW54bkTMUz5w+Jt19mZKuPu0fhmY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=gVFlwCMc9ffYKe42Eu0r6YZ9JtBE6aipBMha/Du1Elkp0waRg9k/tujdg3Kfyyf/s 8MK0yx/gOxkBSooLbIiQ1UeQnMez8jOdCHr7qLXfUhmkhc6Z1jM4+aUUPf7J4xC1ge YkmLsPJPDcmNjBT3KU0gxdzXAC+IMuYIejk+xmK4=
Message-Id: <6.2.5.6.2.20120815075620.09263718@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 15 Aug 2012 09:14:04 -0700
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
From: SM <sm@resistor.net>
Subject: Re: Affirmation of the Modern Global Standards Paradigm
In-Reply-To: <B8A47AD5-2038-4B59-BA43-CE243DE7B33F@gmx.net>
References: <5E893DB832F57341992548CDBB333163A5A9B462FF@EMBX01-HQ.jnpr.net> <502B40B7.8050100@cisco.com> <502B48E8.7060104@gmail.com> <5E893DB832F57341992548CDBB333163A5A9B46658@EMBX01-HQ.jnpr.net> <8972B876-DD01-474E-9234-0133DC9DC119@gmx.net> <5E893DB832F57341992548CDBB333163A5A9B4665D@EMBX01-HQ.jnpr.net> <B8A47AD5-2038-4B59-BA43-CE243DE7B33F@gmx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: iab@iab.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Aug 2012 16:17:46 -0000

Hi Hannes,
At 07:33 15-08-2012, Hannes Tschofenig wrote:
>they make sense (at least to most of us, as folks noted in this 
>discussion thread). The 'Openness', for example, is in my view 
>extremely important since it allows relevant stakeholders to 
>participate: Think about how low the barrier is to participate in 
>the IETF. If you believe that the process has any impact on the 
>quality of the specifications then the principles listed in the 
>document may resonate with you.

Here's what I read on some random web site:

   'The [removed] is an open standards organization, allowing any entity or
    individual to participate in its standards development process as long as
    they follow the [removed] rules. "Open" does not mean "free," and
    participation in standards development is never completely "free."'

Let's replace the name with "IETF":

    The IETF is an open standards organization, allowing any entity or
    individual to participate in its standards development process as long as
    they follow the "Note Well".

IETF meeting participation is not free as there is an attendance 
fee.  However, nobody will check your badge and ask you to leave if 
you don't have one.  Mailing list participation is open.  You don't 
need to pay a fee; there isn't any rule to force a participant to 
subscribe to the mailing list.

In my opinion "openness" is not about stakeholders.  Stakeholders is 
a code word for a party who stands to win or lose money or market 
share based on the outcome of a decision.

The process has a negative impact on the quality of 
specifications.  There are odd cases where it has a positive 
impact.  You can either have a specification of high quality which 
people disagree with or you can have a specification of average 
quality which people can agree with.

>Many may consider these principles as so obvious that they are not 
>worthwhile to write down. Unfortunately, they are not as obvious as 
>one might think. There are other ways to do

Yes.

>  standardization and, as we have seen in the discussions on this 
> list, some would like to change the rules of the game. I believe 
> that this will have negative consequences for the Internet eco-

You may have seen the press release where "stakeholders from across 
industry, civil society and general public are encouraged to make 
their voices heard".  The words in the affirmation will be diluted 
and they will lose their original meaning.

Regards,
-sm 


From david.black@emc.com  Tue Aug 14 16:51:54 2012
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A15DA21F86D7; Tue, 14 Aug 2012 16:51:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.411
X-Spam-Level: 
X-Spam-Status: No, score=-102.411 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7cpcjzksqQle; Tue, 14 Aug 2012 16:51:54 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 5B5A321F86D6; Tue, 14 Aug 2012 16:51:51 -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 q7ENoSmp032347 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Aug 2012 19:50:29 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Tue, 14 Aug 2012 19:50:21 -0400
Received: from mxhub07.corp.emc.com (mxhub07.corp.emc.com [128.222.70.204]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q7ENoKWY016763; Tue, 14 Aug 2012 19:50:21 -0400
Received: from mx15a.corp.emc.com ([169.254.1.66]) by mxhub07.corp.emc.com ([128.222.70.204]) with mapi; Tue, 14 Aug 2012 19:50:20 -0400
From: "Black, David" <david.black@emc.com>
To: "michelle.cotton@icann.org" <michelle.cotton@icann.org>, "leo.vegoda@icann.org" <leo.vegoda@icann.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Tue, 14 Aug 2012 19:50:19 -0400
Subject: RE: Gen-ART review of draft-vegoda-cotton-rfc5735bis-03
Thread-Topic: Gen-ART review of draft-vegoda-cotton-rfc5735bis-03
Thread-Index: Ac12g1nlR2o6ek4yS0CffYeN22Tw+AD9ATuA
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7120A2ECED3@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71208F1240F@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71208F1240F@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Wed, 15 Aug 2012 10:21:07 -0700
Cc: "Black, David" <david.black@emc.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Aug 2012 23:51:54 -0000

The -03 version of this draft addresses the nits in the Gen-ART version
of the -02 version.  Section 5 has been removed in the -03 version,
so the nit that was there is gone.

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Thursday, August 09, 2012 7:05 PM
> To: michelle.cotton@icann.org; leo.vegoda@icann.org; gen-art@ietf.org
> Cc: Black, David; ietf@ietf.org
> Subject: Gen-ART review of draft-vegoda-cotton-rfc5735bis-02
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on Gen-=
ART,
> please
> see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments you=
 may
> receive.
>=20
> Document: draft-vegoda-cotton-rfc5735bis-02
> Reviewer: David L. Black
> Review Date: August 9, 2012
> IETF LC End Date: August 9, 2012
>=20
> Summary:
> This draft is basically ready for publication, but has nits that
> should be fixed before publication.
>=20
> This draft provides an updated list of the special use IPv4 address block=
s
> that have been allocated by IANA along with explanations of their special
> uses.
>=20
> I found one nit and idnits found another one.
>=20
> Section 5 - the first sentence in the second paragraph is:
>=20
>    The domain name and IP address spaces involve policy issues (in
>    addition to technical issues) so that the requirements of [RFC2860]
>    do not apply generally to those spaces.
>=20
> I'm surprised by "do not apply generally".  I would have expected that
> the policy issues create requirements and constraints above and beyond
> the requirements in RFC 2860 as opposed to replacing those requirements.
>=20
> idnits 2.12.13 complained about a lot of IP addresses that aren't in
> the address ranges used for examples.  These complaints can be ignored,
> but idnits did find one actual nit:
>=20
>   =3D=3D Unused Reference: 'RFC6441' is defined on line 346, but no expli=
cit
>      reference was found in the text
>=20
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------
>=20


From jdrake@juniper.net  Wed Aug 15 10:41:21 2012
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 09AF121F869F for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 10:41:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.594
X-Spam-Level: 
X-Spam-Status: No, score=-5.594 tagged_above=-999 required=5 tests=[AWL=1.005,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EgPKCqWXf3gn for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 10:41:20 -0700 (PDT)
Received: from exprod7og126.obsmtp.com (exprod7og126.obsmtp.com [64.18.2.206]) by ietfa.amsl.com (Postfix) with ESMTP id D0B2321F869D for <ietf@ietf.org>; Wed, 15 Aug 2012 10:41:19 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob126.postini.com ([64.18.6.12]) with SMTP ID DSNKUCvfPJp3d45ZGyWN8f1yxbLPtxFKEVlR@postini.com; Wed, 15 Aug 2012 10:41:19 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; Wed, 15 Aug 2012 10:39:52 -0700
From: John E Drake <jdrake@juniper.net>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Date: Wed, 15 Aug 2012 10:39:51 -0700
Subject: RE: Affirmation of the Modern Global Standards Paradigm
Thread-Topic: Affirmation of the Modern Global Standards Paradigm
Thread-Index: Ac168v2NkPuQUgitQX+sVRucb9Pk6wAGRmTQ
Message-ID: <5E893DB832F57341992548CDBB333163A5A9B46866@EMBX01-HQ.jnpr.net>
References: <5E893DB832F57341992548CDBB333163A5A9B462FF@EMBX01-HQ.jnpr.net> <502B40B7.8050100@cisco.com> <502B48E8.7060104@gmail.com> <5E893DB832F57341992548CDBB333163A5A9B46658@EMBX01-HQ.jnpr.net> <8972B876-DD01-474E-9234-0133DC9DC119@gmx.net> <5E893DB832F57341992548CDBB333163A5A9B4665D@EMBX01-HQ.jnpr.net> <B8A47AD5-2038-4B59-BA43-CE243DE7B33F@gmx.net>
In-Reply-To: <B8A47AD5-2038-4B59-BA43-CE243DE7B33F@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
Cc: "iab@iab.org" <iab@iab.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, 15 Aug 2012 17:41:21 -0000

Hannes,

Let me try a different tack:

1)  Is this document intended to change the way that the IETF interacts wit=
h other SDOs?

2)  What is the document's marginal utility?  I.e., what changes if it is p=
ublished?

3)  Is there a plan of which this document is a part or is it simply a 'one=
-off'?

4)  What is the relationship between this document and the mission of the I=
SOC, which, as I understand it, is to promote the open development, evoluti=
on, and use of the Internet?

Thanks,

John

Sent from my iPhone


> -----Original Message-----
> From: Hannes Tschofenig [mailto:hannes.tschofenig@gmx.net]
> Sent: Wednesday, August 15, 2012 7:33 AM
> To: John E Drake
> Cc: Hannes Tschofenig; Brian E Carpenter; Eliot Lear; iab@iab.org;
> ietf@ietf.org
> Subject: Re: Affirmation of the Modern Global Standards Paradigm
>=20
> Hi John,
>=20
> On Aug 15, 2012, at 3:41 PM, John E Drake wrote:
>=20
> > JD:  To what purpose?  As an aside, I get the 'feel-good' aspect, but
> is there anything more?
>=20
> I like the term - IAB documents as 'feel-good' publications.
>=20
> The IAB publishes a variety of different documents. Some of them are
> formal communication interactions with other organizations and others
> are documenting topics that could be of interest to the IETF community
> or even beyond. These documents are not enforceable in a legal sense
> (which is good).
>=20
> The content of this specific document did not surprise you and, as a
> regular IETF participant, it shouldn't. You look at the list of
> principles and they sound familiar - they make sense (at least to most
> of us, as folks noted in this discussion thread). The 'Openness', for
> example, is in my view extremely important since it allows relevant
> stakeholders to participate: Think about how low the barrier is to
> participate in the IETF. If you believe that the process has any impact
> on the quality of the specifications then the principles listed in the
> document may resonate with you.
>=20
> Many may consider these principles as so obvious that they are not
> worthwhile to write down. Unfortunately, they are not as obvious as one
> might think. There are other ways to do standardization and, as we have
> seen in the discussions on this list, some would like to change the
> rules of the game. I believe that this will have negative consequences
> for the Internet eco-system and for the speed of innovation we had
> gotten so used to.
>=20
> Whether this document can prevent bad things from happening is of
> course a separate story but it, at least, captures the views of a list
> of organizations active in Internet standardization.
>=20
> I hope that this makes sense to you.
>=20
> Ciao
> Hannes
>=20
>=20


From iad@ietf.org  Wed Aug 15 12:04:55 2012
Return-Path: <iad@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B20521E80AB; Wed, 15 Aug 2012 12:04:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UbnRg8au0XWu; Wed, 15 Aug 2012 12:04:55 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EBC021E8034; Wed, 15 Aug 2012 12:04:55 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: IETF 92 in Dallas!
X-Test-IDTracker: no
X-IETF-IDTracker: 4.33
Message-ID: <20120815190455.14702.74089.idtracker@ietfa.amsl.com>
Date: Wed, 15 Aug 2012 12:04:55 -0700
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Aug 2012 19:04:56 -0000

The IAOC is pleased to announce Dallas, TX, USA as the site for IETF 92 fro=
m March 22-27, =

2015.  The IETF was last in Dallas for IETF 65 in 2006.  IETF 92 will be at=
 a different venue in =

the Dallas Arts District.

Those who may be interested in hosting or sponsoring this or any future mee=
ting are invited to =

contact Drew Dvorshak at dvorshak@isoc.org.  See Host opportunities below.

Ray Pelletier
IETF Administrative Director

IETF Meeting Schedule:

2012
	IETF 85  Atlanta  4 - 9 November   Host: North American Cable Industry

2013
	IETF 86  Orlando  10 - 15 March (Back-to-back with IEEE 802) Comcast & NBC=
 Universal
	IETF 87  Berlin  28 July - 2 Aug  Host and Sponsors Sought
	IETF 88  Vancouver  3 - 8 November  Host Sought

2014 - Hosts sought
	IETF 89	London
	IETF 90	Toronto
	IETF 91   Honolulu	=


2015 - Hosts sought
	IETF 92	Dallas
	IETF 93	Europe
	IETF 94	Yokohama  WIDE

From mary.ietf.barnes@gmail.com  Wed Aug 15 13:39:46 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47BDB21F85AF for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 13:39:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.525
X-Spam-Level: 
X-Spam-Status: No, score=-103.525 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CThaQEgv8qU5; Wed, 15 Aug 2012 13:39:45 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0921021F86B1; Wed, 15 Aug 2012 13:39:44 -0700 (PDT)
Received: by lahm15 with SMTP id m15so1104038lah.31 for <multiple recipients>; Wed, 15 Aug 2012 13:39:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=H+Ho/TzVOPwFJ0aMu+VbFqg4f22wQybiA3g4oghWGK8=; b=K9BbB78aEqqy/cKLUMxkwb0TYXbd9WjwJKhugiMWvSQ0GTNcEGTEsQ7FVlOh2wTgTd ksCuBD0n19n2fFtDW30m7XW1FpuseR42pxvNk/PPXQEkIf7usW6aoFfirpRrfUe7nJAM 9WlAs6m2oa/tYFwEfZLWvREN5PG0lj/7fGaOV+gmxl2tdNKzdGrzKTjQUzbVE2JqfY55 bBJ+p1ec0m1i6/tR+tjKIoKlTMU5sIIv+OWyJXzmeQJbri+KqqigMjHbvxcy4wHoqPa6 yDkOw1lmE+eKxF3y2AOeOVhSLMYOp8uzC2wTtDApyBN3meA3Bfz16uSVAtLtvJ0jQpu1 nzlA==
MIME-Version: 1.0
Received: by 10.152.102.238 with SMTP id fr14mr11347463lab.8.1345063183757; Wed, 15 Aug 2012 13:39:43 -0700 (PDT)
Received: by 10.112.85.196 with HTTP; Wed, 15 Aug 2012 13:39:43 -0700 (PDT)
In-Reply-To: <20120815190455.14702.74089.idtracker@ietfa.amsl.com>
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com>
Date: Wed, 15 Aug 2012 15:39:43 -0500
Message-ID: <CAHBDyN5ewsYm1kgk0WL_8mfHqdgQ6e-iPhk4po5-uR+Bmi63Eg@mail.gmail.com>
Subject: Re: [IAB] IETF 92 in Dallas!
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: IETF-Discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=f46d04083c9344b2b604c753ed32
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Aug 2012 20:39:46 -0000

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

People also should be aware that Dallas has major transit and highway work
underway right now in particular North of the airport.  By 2015 (2014
actually), you will be able to take light rail (orange line) from the
airport to downtown:
http://www.dart.org/about/expansion/orangeline.asp

Mary.

On Wed, Aug 15, 2012 at 2:04 PM, IETF Administrative Director
<iad@ietf.org>wrote:

> The IAOC is pleased to announce Dallas, TX, USA as the site for IETF 92
> from March 22-27,
> 2015.  The IETF was last in Dallas for IETF 65 in 2006.  IETF 92 will be
> at a different venue in
> the Dallas Arts District.
>
> Those who may be interested in hosting or sponsoring this or any future
> meeting are invited to
> contact Drew Dvorshak at dvorshak@isoc.org.  See Host opportunities below.
>
> Ray Pelletier
> IETF Administrative Director
>
> IETF Meeting Schedule:
>
> 2012
>         IETF 85  Atlanta  4 - 9 November   Host: North American Cable
> Industry
>
> 2013
>         IETF 86  Orlando  10 - 15 March (Back-to-back with IEEE 802)
> Comcast & NBC Universal
>         IETF 87  Berlin  28 July - 2 Aug  Host and Sponsors Sought
>         IETF 88  Vancouver  3 - 8 November  Host Sought
>
> 2014 - Hosts sought
>         IETF 89 London
>         IETF 90 Toronto
>         IETF 91   Honolulu
>
> 2015 - Hosts sought
>         IETF 92 Dallas
>         IETF 93 Europe
>         IETF 94 Yokohama  WIDE
>

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

People also should be aware that Dallas has major transit and highway work =
underway right now in particular North of the airport. =A0By 2015 (2014 act=
ually), you will be able to take light rail (orange line) from the airport =
to downtown:<div>
<a href=3D"http://www.dart.org/about/expansion/orangeline.asp">http://www.d=
art.org/about/expansion/orangeline.asp</a></div><div><br></div><div>Mary.=
=A0</div><div><br><div class=3D"gmail_quote">On Wed, Aug 15, 2012 at 2:04 P=
M, IETF Administrative Director <span dir=3D"ltr">&lt;<a href=3D"mailto:iad=
@ietf.org" target=3D"_blank">iad@ietf.org</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">The IAOC is pleased to announce Dallas, TX, =
USA as the site for IETF 92 from March 22-27,<br>
2015. =A0The IETF was last in Dallas for IETF 65 in 2006. =A0IETF 92 will b=
e at a different venue in<br>
the Dallas Arts District.<br>
<br>
Those who may be interested in hosting or sponsoring this or any future mee=
ting are invited to<br>
contact Drew Dvorshak at <a href=3D"mailto:dvorshak@isoc.org">dvorshak@isoc=
.org</a>. =A0See Host opportunities below.<br>
<br>
Ray Pelletier<br>
IETF Administrative Director<br>
<br>
IETF Meeting Schedule:<br>
<br>
2012<br>
=A0 =A0 =A0 =A0 IETF 85 =A0Atlanta =A04 - 9 November =A0 Host: North Americ=
an Cable Industry<br>
<br>
2013<br>
=A0 =A0 =A0 =A0 IETF 86 =A0Orlando =A010 - 15 March (Back-to-back with IEEE=
 802) Comcast &amp; NBC Universal<br>
=A0 =A0 =A0 =A0 IETF 87 =A0Berlin =A028 July - 2 Aug =A0Host and Sponsors S=
ought<br>
=A0 =A0 =A0 =A0 IETF 88 =A0Vancouver =A03 - 8 November =A0Host Sought<br>
<br>
2014 - Hosts sought<br>
=A0 =A0 =A0 =A0 IETF 89 London<br>
=A0 =A0 =A0 =A0 IETF 90 Toronto<br>
=A0 =A0 =A0 =A0 IETF 91 =A0 Honolulu<br>
<br>
2015 - Hosts sought<br>
=A0 =A0 =A0 =A0 IETF 92 Dallas<br>
=A0 =A0 =A0 =A0 IETF 93 Europe<br>
=A0 =A0 =A0 =A0 IETF 94 Yokohama =A0WIDE<br>
</blockquote></div><br></div>

--f46d04083c9344b2b604c753ed32--

From mohta@necom830.hpcl.titech.ac.jp  Wed Aug 15 17:45:23 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F4A421F846E for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 17:45:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.051
X-Spam-Level: 
X-Spam-Status: No, score=-0.051 tagged_above=-999 required=5 tests=[AWL=0.039,  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 Wh6b4kx9Fi+C for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2012 17:45: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 6AA3921F846C for <ietf@ietf.org>; Wed, 15 Aug 2012 17:45:22 -0700 (PDT)
Received: (qmail 34253 invoked from network); 16 Aug 2012 00:44:09 -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; 16 Aug 2012 00:44:09 -0000
Message-ID: <502C427F.7090505@necom830.hpcl.titech.ac.jp>
Date: Thu, 16 Aug 2012 09:44:47 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FE2715C.2090601@necom830.hpcl.titech.ac.jp> <4FF20DE7.2080208@isi.edu> <500654AB.7060500@necom830.hpcl.titech.ac.jp> <8F5CBE79-4540-4519-9F51-62B36686EE8C@isi.edu> <501C5C75.9040209@necom830.hpcl.titech.ac.jp> <501C6441.4000302@isi.edu> <5020C32A.4060907@necom830.hpcl.titech.ac.jp> <50215032.7090800@isi.edu> <5027767A.60601@necom830.hpcl.titech.ac.jp> <5027E8EE.8010109@isi.edu> <5028CCB9.5050503@necom830.hpcl.titech.ac.jp> <5028CFC2.1060200@isi.edu>
In-Reply-To: <5028CFC2.1060200@isi.edu>
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, 16 Aug 2012 00:45:23 -0000

Joe Touch wrote:

>>> Again, this doc is about updating the IPv4 ID specification in RFC791 -
>>> which has not yet been updated.
>>
>> But, the way you update rfc791 requires updating rfc2460,
>> rfc2765 and their implementations, for which there is no
>> consensus.
> 
> It certainly does not.

The following requirement in your draft:

   >> Sources of non-atomic IPv4 datagrams MUST rate-limit their output
   to comply with the ID uniqueness requirements.

requires updating rfc2460 and/or rfc2765 to rate-limit IPv6
datagrams with fragment headers below 6.4 Mbps (assuming
unfragmented packet is 1500B long).

>> That is, though your draft claims to "more closely reflect
>> current practice" and "more closely match IPv6", the way you
>> update rfc791 does not "reflect current practice" nor "match
>> IPv6".
> 
> It does -

The current practice, with both IPv4 and IPv6, is to have
loose uniqueness of IDs.

Or, do you mean the current practice the practice not of
the real world network operation but of the way of
discussion in intarea WG?

> it doesn't reflect the errors in IPv6-IPv4 translation, which
> is not "IPv6".

Most, if not all, implementers do not think them errors.

						Masataka Ohta

From aservin@lacnic.net  Wed Aug 15 20:37:19 2012
Return-Path: <aservin@lacnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA72A21F85B8; Wed, 15 Aug 2012 20:37:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.048
X-Spam-Level: 
X-Spam-Status: No, score=-1.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YireZhCgFNlm; Wed, 15 Aug 2012 20:37:19 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 14B4E21F85B1; Wed, 15 Aug 2012 20:37:19 -0700 (PDT)
Received: from [192.168.1.54] (unknown [190.27.215.37]) by mail.lacnic.net.uy (Postfix) with ESMTP id 83333308432; Thu, 16 Aug 2012 00:37:06 -0300 (UYT)
Subject: Re: IETF 92 in Dallas!
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Arturo Servin <aservin@lacnic.net>
In-Reply-To: <20120815190455.14702.74089.idtracker@ietfa.amsl.com>
Date: Wed, 15 Aug 2012 22:37:04 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net>
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com>
To: IETF Administrative Director <iad@ietf.org>
X-Mailer: Apple Mail (2.1278)
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, iab@iab.org, iesg@ietf.org, IETF Announcement List <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, 16 Aug 2012 03:37:20 -0000

	So "Americas" was actually "North America".

	Well, it went the possibility to have one in central or south =
america, what at shame. At least until IETF 98 in March 2017 no IETF =
down the south of Rio Grande.

	May I ask the IAOC, what are the impediments to have one IETF in =
Latin America?

Regards,
as

On 15 Aug 2012, at 14:04, IETF Administrative Director wrote:

> The IAOC is pleased to announce Dallas, TX, USA as the site for IETF =
92 from March 22-27,=20
> 2015.  The IETF was last in Dallas for IETF 65 in 2006.  IETF 92 will =
be at a different venue in=20
> the Dallas Arts District.
>=20
> Those who may be interested in hosting or sponsoring this or any =
future meeting are invited to=20
> contact Drew Dvorshak at dvorshak@isoc.org.  See Host opportunities =
below.
>=20
> Ray Pelletier
> IETF Administrative Director
>=20
> IETF Meeting Schedule:
>=20
> 2012
> 	IETF 85  Atlanta  4 - 9 November   Host: North American Cable =
Industry
>=20
> 2013
> 	IETF 86  Orlando  10 - 15 March (Back-to-back with IEEE 802) =
Comcast & NBC Universal
> 	IETF 87  Berlin  28 July - 2 Aug  Host and Sponsors Sought
> 	IETF 88  Vancouver  3 - 8 November  Host Sought
>=20
> 2014 - Hosts sought
> 	IETF 89	London
> 	IETF 90	Toronto
> 	IETF 91   Honolulu=09
>=20
> 2015 - Hosts sought
> 	IETF 92	Dallas
> 	IETF 93	Europe
> 	IETF 94	Yokohama  WIDE


From alejandroacostaalamo@gmail.com  Wed Aug 15 21:49:12 2012
Return-Path: <alejandroacostaalamo@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0A8021F8513; Wed, 15 Aug 2012 21:49:11 -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 ybq9yWkQWb9o; Wed, 15 Aug 2012 21:49:11 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4CDD421F850D; Wed, 15 Aug 2012 21:49:10 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so2413706vbb.31 for <multiple recipients>; Wed, 15 Aug 2012 21:49:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=A1yfc/UN1HDqs0Cg+ANug6tXJBdlNb71Uwv80t0sGAM=; b=ghvUxg0WPUP/S/REeRUCWVNpZIUY4UdpI6INX6vlX3Vkn0upZTp7IqCFQumL1yHLrj AZcvUFKY9z37wYoTIS67dgTh5bqXflH1xfZGnrHxn6TXsi2wg3ExyvhfbzQVlJRiRpXp B4f4b9MvZfm9QrW8Q4WsVaujcws/2QTp7kcJxl41Q68Gs0V9WVdQaFpLsu9bjcKdC1nS HzkjGRwjYeUfur9ELESDS6qhDEYhF2Ojuiot3IxNlSM39V89aeyQmjKcXtvlYE3v3ijN P3WjViJwG8tF3Pi4irBrlLfq7vSWqqsmhIR4gwL5rEbjCkUXIL9mOIRtLeuZy85d3aU8 A9Tg==
MIME-Version: 1.0
Received: by 10.220.214.208 with SMTP id hb16mr14033206vcb.56.1345092549545; Wed, 15 Aug 2012 21:49:09 -0700 (PDT)
Received: by 10.58.196.179 with HTTP; Wed, 15 Aug 2012 21:49:09 -0700 (PDT)
In-Reply-To: <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net>
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net>
Date: Thu, 16 Aug 2012 00:19:09 -0430
Message-ID: <CAOmxzdzDmbZNRfRgdxps8JAiw9BGzti+aM_CvVONHLFjrboa=A@mail.gmail.com>
Subject: Re: IETF 92 in Dallas!
From: Alejandro Acosta <alejandroacostaalamo@gmail.com>
To: Arturo Servin <aservin@lacnic.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, iab@iab.org, iesg@ietf.org, IETF Announcement List <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, 16 Aug 2012 04:49:12 -0000

Hi All,
  In my humble opinion I totally agree with Arturo. So far I do know
several cities in Latin America and I believe Sao Paulo (Brazil) or
Cancun (Mexico) might be a good options. Of course there are many more
good cities, those ware the first two that came to my mind.
  I hope IETF 100 can be done over there.

See you,

Alejandro,



On 8/15/12, Arturo Servin <aservin@lacnic.net> wrote:
>
> 	So "Americas" was actually "North America".
>
> 	Well, it went the possibility to have one in central or south america, what
> at shame. At least until IETF 98 in March 2017 no IETF down the south of Rio
> Grande.
>
> 	May I ask the IAOC, what are the impediments to have one IETF in Latin
> America?
>
> Regards,
> as
>
> On 15 Aug 2012, at 14:04, IETF Administrative Director wrote:
>
>> The IAOC is pleased to announce Dallas, TX, USA as the site for IETF 92
>> from March 22-27,
>> 2015.  The IETF was last in Dallas for IETF 65 in 2006.  IETF 92 will be
>> at a different venue in
>> the Dallas Arts District.
>>
>> Those who may be interested in hosting or sponsoring this or any future
>> meeting are invited to
>> contact Drew Dvorshak at dvorshak@isoc.org.  See Host opportunities
>> below.
>>
>> Ray Pelletier
>> IETF Administrative Director
>>
>> IETF Meeting Schedule:
>>
>> 2012
>> 	IETF 85  Atlanta  4 - 9 November   Host: North American Cable Industry
>>
>> 2013
>> 	IETF 86  Orlando  10 - 15 March (Back-to-back with IEEE 802) Comcast &
>> NBC Universal
>> 	IETF 87  Berlin  28 July - 2 Aug  Host and Sponsors Sought
>> 	IETF 88  Vancouver  3 - 8 November  Host Sought
>>
>> 2014 - Hosts sought
>> 	IETF 89	London
>> 	IETF 90	Toronto
>> 	IETF 91   Honolulu	
>>
>> 2015 - Hosts sought
>> 	IETF 92	Dallas
>> 	IETF 93	Europe
>> 	IETF 94	Yokohama  WIDE
>
>

From joelja@bogus.com  Wed Aug 15 22:15:04 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 709DB21F84DD; Wed, 15 Aug 2012 22:15:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.319
X-Spam-Level: 
X-Spam-Status: No, score=-102.319 tagged_above=-999 required=5 tests=[AWL=0.280, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UovZ-F1mVl6h; Wed, 15 Aug 2012 22:15:03 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id C9CF521F84D9; Wed, 15 Aug 2012 22:15:03 -0700 (PDT)
Received: from joels-MacBook-Air.local (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 q7G5Ex5N028696 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 16 Aug 2012 05:14:59 GMT (envelope-from joelja@bogus.com)
Message-ID: <502C81D2.3020600@bogus.com>
Date: Wed, 15 Aug 2012 22:14:58 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120808 Thunderbird/15.0
MIME-Version: 1.0
To: Alejandro Acosta <alejandroacostaalamo@gmail.com>
Subject: Re: IETF 92 in Dallas!
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net> <CAOmxzdzDmbZNRfRgdxps8JAiw9BGzti+aM_CvVONHLFjrboa=A@mail.gmail.com>
In-Reply-To: <CAOmxzdzDmbZNRfRgdxps8JAiw9BGzti+aM_CvVONHLFjrboa=A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 16 Aug 2012 05:15:00 +0000 (UTC)
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, iab@iab.org, iesg@ietf.org, IETF Announcement List <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, 16 Aug 2012 05:15:04 -0000

On 8/15/12 9:49 PM, Alejandro Acosta wrote:
> Hi All,
>    In my humble opinion I totally agree with Arturo. So far I do know
> several cities in Latin America and I believe Sao Paulo (Brazil) or
> Cancun (Mexico) might be a good options. Of course there are many more
> good cities, those ware the first two that came to my mind.
>    I hope IETF 100 can be done over there.
Notably Sao Paulo gets a train line from GRU in time for the worldcup in 
theory, which would be a substantial accessibility improvement.

Some locations in the southern hemisphere where attendees hail from have 
even more painful routing than normal to GRU e.g. syd. The observation 
would be that it's a long-haul for all but a handful of attendees.
> See you,
>
> Alejandro,
>
>
>
> On 8/15/12, Arturo Servin <aservin@lacnic.net> wrote:
>> 	So "Americas" was actually "North America".
>>
>> 	Well, it went the possibility to have one in central or south america, what
>> at shame. At least until IETF 98 in March 2017 no IETF down the south of Rio
>> Grande.
>>
>> 	May I ask the IAOC, what are the impediments to have one IETF in Latin
>> America?
>>
>> Regards,
>> as
>>
>> On 15 Aug 2012, at 14:04, IETF Administrative Director wrote:
>>
>>> The IAOC is pleased to announce Dallas, TX, USA as the site for IETF 92
>>> from March 22-27,
>>> 2015.  The IETF was last in Dallas for IETF 65 in 2006.  IETF 92 will be
>>> at a different venue in
>>> the Dallas Arts District.
>>>
>>> Those who may be interested in hosting or sponsoring this or any future
>>> meeting are invited to
>>> contact Drew Dvorshak at dvorshak@isoc.org.  See Host opportunities
>>> below.
>>>
>>> Ray Pelletier
>>> IETF Administrative Director
>>>
>>> IETF Meeting Schedule:
>>>
>>> 2012
>>> 	IETF 85  Atlanta  4 - 9 November   Host: North American Cable Industry
>>>
>>> 2013
>>> 	IETF 86  Orlando  10 - 15 March (Back-to-back with IEEE 802) Comcast &
>>> NBC Universal
>>> 	IETF 87  Berlin  28 July - 2 Aug  Host and Sponsors Sought
>>> 	IETF 88  Vancouver  3 - 8 November  Host Sought
>>>
>>> 2014 - Hosts sought
>>> 	IETF 89	London
>>> 	IETF 90	Toronto
>>> 	IETF 91   Honolulu	
>>>
>>> 2015 - Hosts sought
>>> 	IETF 92	Dallas
>>> 	IETF 93	Europe
>>> 	IETF 94	Yokohama  WIDE
>>


From hannes.tschofenig@gmx.net  Thu Aug 16 01:10:26 2012
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DC0D21F84C5 for <ietf@ietfa.amsl.com>; Thu, 16 Aug 2012 01:10:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.607
X-Spam-Level: 
X-Spam-Status: No, score=-102.607 tagged_above=-999 required=5 tests=[AWL=-0.008, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 80rqixJ8p3bC for <ietf@ietfa.amsl.com>; Thu, 16 Aug 2012 01:10:25 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id C000621F846A for <ietf@ietf.org>; Thu, 16 Aug 2012 01:10:05 -0700 (PDT)
Received: (qmail invoked by alias); 16 Aug 2012 08:10:04 -0000
Received: from a88-115-216-191.elisa-laajakaista.fi (EHLO [192.168.100.105]) [88.115.216.191] by mail.gmx.net (mp036) with SMTP; 16 Aug 2012 10:10:04 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19+ubATa4V+ka/+KnBgp0m1qumwK789R0ZiEzhQWl v3gwCQynqiT8zS
Subject: Re: Affirmation of the Modern Global Standards Paradigm
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: <5E893DB832F57341992548CDBB333163A5A9B46866@EMBX01-HQ.jnpr.net>
Date: Thu, 16 Aug 2012 11:10:02 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <E739DF84-EF5F-4855-A59A-5737E56F646F@gmx.net>
References: <5E893DB832F57341992548CDBB333163A5A9B462FF@EMBX01-HQ.jnpr.net> <502B40B7.8050100@cisco.com> <502B48E8.7060104@gmail.com> <5E893DB832F57341992548CDBB333163A5A9B46658@EMBX01-HQ.jnpr.net> <8972B876-DD01-474E-9234-0133DC9DC119@gmx.net> <5E893DB832F57341992548CDBB333163A5A9B4665D@EMBX01-HQ.jnpr.net> <B8A47AD5-2038-4B59-BA43-CE243DE7B33F@gmx.net> <5E893DB832F57341992548CDBB333163A5A9B46866@EMBX01-HQ.jnpr.net>
To: John E Drake <jdrake@juniper.net>
X-Mailer: Apple Mail (2.1084)
X-Y-GMX-Trusted: 0
Cc: "iab@iab.org" <iab@iab.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, 16 Aug 2012 08:10:26 -0000

Hi John,=20

(responding with my personal views)

On Aug 15, 2012, at 8:39 PM, John E Drake wrote:

> Hannes,
>=20
> Let me try a different tack:
>=20
> 1)  Is this document intended to change the way that the IETF =
interacts with other SDOs?
>=20
Nope. We always interact with other SDOs in the same way since the IETF =
process does not provide options.

The intensity of the interactions and the degree of information exchange =
varies over time between the different organizations (quite naturally =
due to the topics different SDOs care about).=20

The IAB has their liaison managers for the different organizations and =
just manages the liaison relationships. The actual liaison persons make =
sure that the information flows. =46rom my experience it is best if =
there are engineers that participate in both organizations and use =
informal communication (rather than liaison statements). =20

> 2)  What is the document's marginal utility?  I.e., what changes if it =
is published?

Informing others how various SDOs, including the IETF, develop =
standards. I believe there is value in education even though it is hard =
to measure: did someone learn something new from this specific document, =
did they already knew it upfront, learn it in discussions, etc.. Who =
knows.=20
=20
>=20
> 3)  Is there a plan of which this document is a part or is it simply a =
'one-off'?

Education about what the IETF is about and what are the factors that =
make IETF protocols successful is an ongoing activity.=20

Many of the IAB publications discuss different facets of this topic. =
Just pick a recently approved IAB document, namely =
http://tools.ietf.org/html/draft-iab-extension-recs-17. It builds on =
"What Makes for a Successful Protocol" [RFC5218] and discusses the =
challenging topic of how to define a protocol so that future extensions =
do not lead to interoperability problems.=20
=20
As you know, designing protocols is complex and requires a broad =
expertise. The IAB tries to provide guidance that often falls beyond a =
single protocol, working group or area. Best examples of broader =
guidance is RFC 3552 ("Guidelines for Writing RFC Text on Security =
Considerations") and =
http://tools.ietf.org/html/draft-iab-privacy-considerations-03 ("Privacy =
Considerations for Internet Protocols"). Sometimes the recommendations =
concern the interaction with other SDOs, such as with RFC 5704 =
"Uncoordinated Protocol Development Considered Harmful".=20

As you can see from the examples above the guidance ranges from =
technical aspects to process related advice.=20

The IAB, however, does not have endless resources to do everything alone =
(since the IAB charter gives us a number of functions; not only liaisons =
and architectural oversight). For that reason I am quite happy that =
there are others, like ISOC, CDT, journalists, etc. also share their =
views with the rest of the world. They use social media, blog posts, and =
all the great Web technologies to reach out to the wider Internet =
community to raise awareness.=20

> 4)  What is the relationship between this document and the mission of =
the ISOC, which, as I understand it, is to promote the open development, =
evolution, and use of the Internet?

The Internet Society needs to speak for themselves.=20

Ciao
Hannes

>=20
> Thanks,
>=20
> John
>=20
> Sent from my iPhone
>=20
>=20
>> -----Original Message-----
>> From: Hannes Tschofenig [mailto:hannes.tschofenig@gmx.net]
>> Sent: Wednesday, August 15, 2012 7:33 AM
>> To: John E Drake
>> Cc: Hannes Tschofenig; Brian E Carpenter; Eliot Lear; iab@iab.org;
>> ietf@ietf.org
>> Subject: Re: Affirmation of the Modern Global Standards Paradigm
>>=20
>> Hi John,
>>=20
>> On Aug 15, 2012, at 3:41 PM, John E Drake wrote:
>>=20
>>> JD:  To what purpose?  As an aside, I get the 'feel-good' aspect, =
but
>> is there anything more?
>>=20
>> I like the term - IAB documents as 'feel-good' publications.
>>=20
>> The IAB publishes a variety of different documents. Some of them are
>> formal communication interactions with other organizations and others
>> are documenting topics that could be of interest to the IETF =
community
>> or even beyond. These documents are not enforceable in a legal sense
>> (which is good).
>>=20
>> The content of this specific document did not surprise you and, as a
>> regular IETF participant, it shouldn't. You look at the list of
>> principles and they sound familiar - they make sense (at least to =
most
>> of us, as folks noted in this discussion thread). The 'Openness', for
>> example, is in my view extremely important since it allows relevant
>> stakeholders to participate: Think about how low the barrier is to
>> participate in the IETF. If you believe that the process has any =
impact
>> on the quality of the specifications then the principles listed in =
the
>> document may resonate with you.
>>=20
>> Many may consider these principles as so obvious that they are not
>> worthwhile to write down. Unfortunately, they are not as obvious as =
one
>> might think. There are other ways to do standardization and, as we =
have
>> seen in the discussions on this list, some would like to change the
>> rules of the game. I believe that this will have negative =
consequences
>> for the Internet eco-system and for the speed of innovation we had
>> gotten so used to.
>>=20
>> Whether this document can prevent bad things from happening is of
>> course a separate story but it, at least, captures the views of a =
list
>> of organizations active in Internet standardization.
>>=20
>> I hope that this makes sense to you.
>>=20
>> Ciao
>> Hannes
>>=20
>>=20
>=20


From marka@isc.org  Thu Aug 16 01:17:57 2012
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 2F66D21F8578; Thu, 16 Aug 2012 01:17:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VeFYIRhkzpc1; Thu, 16 Aug 2012 01:17: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 3B69E21F84F9; Thu, 16 Aug 2012 01:17:56 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id C7CE25F995A; Thu, 16 Aug 2012 08:17:44 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:e41f:b5e2:3b18:a3de]) (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 CA55A216C6E; Thu, 16 Aug 2012 08:17: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 9F7E523A314B; Thu, 16 Aug 2012 18:17:29 +1000 (EST)
To: joel jaeggli <joelja@bogus.com>
From: Mark Andrews <marka@isc.org>
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net> <CAOmxzdzDmbZNRfRgdxps8JAiw9BGzti+aM_CvVONHLFjrboa=A@mail.gmail.com> <502C81D2.3020600@bogus.com>
Subject: Re: IETF 92 in Dallas!
In-reply-to: Your message of "Wed, 15 Aug 2012 22:14:58 MST." <502C81D2.3020600@bogus.com>
Date: Thu, 16 Aug 2012 18:17:28 +1000
Message-Id: <20120816081729.9F7E523A314B@drugs.dv.isc.org>
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, iab@iab.org, iesg@ietf.org, IETF Announcement List <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, 16 Aug 2012 08:17:57 -0000

In message <502C81D2.3020600@bogus.com>, joel jaeggli writes:
> On 8/15/12 9:49 PM, Alejandro Acosta wrote:
> > Hi All,
> >    In my humble opinion I totally agree with Arturo. So far I do know
> > several cities in Latin America and I believe Sao Paulo (Brazil) or
> > Cancun (Mexico) might be a good options. Of course there are many more
> > good cities, those ware the first two that came to my mind.
> >    I hope IETF 100 can be done over there.
> Notably Sao Paulo gets a train line from GRU in time for the worldcup in 
> theory, which would be a substantial accessibility improvement.
> 
> Some locations in the southern hemisphere where attendees hail from have 
> even more painful routing than normal to GRU e.g. syd. The observation 
> would be that it's a long-haul for all but a handful of attendees.

And it would be ~$1000 (AUD) more than Vancouver was from Sydney.

		SYD -> SCL -> GRU  21:40
		GRU -> SLC -> SYD  24:30

> > See you,
> >
> > Alejandro,
> >
> >
> >
> > On 8/15/12, Arturo Servin <aservin@lacnic.net> wrote:
> >> 	So "Americas" was actually "North America".
> >>
> >> 	Well, it went the possibility to have one in central or south america, 
> what
> >> at shame. At least until IETF 98 in March 2017 no IETF down the south of R
> io
> >> Grande.
> >>
> >> 	May I ask the IAOC, what are the impediments to have one IETF in Latin
> >> America?
> >>
> >> Regards,
> >> as
> >>
> >> On 15 Aug 2012, at 14:04, IETF Administrative Director wrote:
> >>
> >>> The IAOC is pleased to announce Dallas, TX, USA as the site for IETF 92
> >>> from March 22-27,
> >>> 2015.  The IETF was last in Dallas for IETF 65 in 2006.  IETF 92 will be
> >>> at a different venue in
> >>> the Dallas Arts District.
> >>>
> >>> Those who may be interested in hosting or sponsoring this or any future
> >>> meeting are invited to
> >>> contact Drew Dvorshak at dvorshak@isoc.org.  See Host opportunities
> >>> below.
> >>>
> >>> Ray Pelletier
> >>> IETF Administrative Director
> >>>
> >>> IETF Meeting Schedule:
> >>>
> >>> 2012
> >>> 	IETF 85  Atlanta  4 - 9 November   Host: North American Cable Industry
> >>>
> >>> 2013
> >>> 	IETF 86  Orlando  10 - 15 March (Back-to-back with IEEE 802) Comcast &
> >>> NBC Universal
> >>> 	IETF 87  Berlin  28 July - 2 Aug  Host and Sponsors Sought
> >>> 	IETF 88  Vancouver  3 - 8 November  Host Sought
> >>>
> >>> 2014 - Hosts sought
> >>> 	IETF 89	London
> >>> 	IETF 90	Toronto
> >>> 	IETF 91   Honolulu	
> >>>
> >>> 2015 - Hosts sought
> >>> 	IETF 92	Dallas
> >>> 	IETF 93	Europe
> >>> 	IETF 94	Yokohama  WIDE
> >>
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From brian.e.carpenter@gmail.com  Thu Aug 16 03:02:02 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 783E321F865B for <ietf@ietfa.amsl.com>; Thu, 16 Aug 2012 03:02:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.507
X-Spam-Level: 
X-Spam-Status: No, score=-101.507 tagged_above=-999 required=5 tests=[AWL=0.184, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u4CGYTUZCKUD for <ietf@ietfa.amsl.com>; Thu, 16 Aug 2012 03:02:02 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id B5B4721F861A for <ietf@ietf.org>; Thu, 16 Aug 2012 03:02:01 -0700 (PDT)
Received: by eekb45 with SMTP id b45so726776eek.31 for <ietf@ietf.org>; Thu, 16 Aug 2012 03:02:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=q9GI35BoeHoJxxM+o5an4myBiqixiBmjq0XiC5Wt4qA=; b=mf8QMtyjr076dWAvvEnGzjsL9qXtREDBVYGBFf/m5Pk4PQhZzU2P3wec1NqCoKwMpm t1iu7PVZ3+EZhe8klssm4T/RChW9wfYJrZiqeW8IHG0EWdWblQfFl0WNhmdngeHbAVoC DQvDQXK4IWkxGJGHp0s9i0WT0YOYi2T/iKpRLsLzINeb5VvAANohlCmZy54l39gc+5/9 Z4T2Sk+peeT/3vXd7YmGRUOd17KHXezo2q+Df54vxy0eyKH/j35YT0I10/084C1o4Mg1 /BSWUg4yLzybyGNAQYNrPTn9mILWPoqnmWuJOG1aQg4nK7BOYHTOH9n09CMgHEq4qpre 8YRg==
Received: by 10.14.202.131 with SMTP id d3mr777851eeo.32.1345111320956; Thu, 16 Aug 2012 03:02:00 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-219-10.as13285.net. [2.102.219.10]) by mx.google.com with ESMTPS id h42sm10705901eem.5.2012.08.16.03.01.58 (version=SSLv3 cipher=OTHER); Thu, 16 Aug 2012 03:01:59 -0700 (PDT)
Message-ID: <502CC51E.80500@gmail.com>
Date: Thu, 16 Aug 2012 11:02:06 +0100
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: Affirmation of the Modern Global Standards Paradigm
References: <5E893DB832F57341992548CDBB333163A5A9B462FF@EMBX01-HQ.jnpr.net> <502B40B7.8050100@cisco.com> <502B48E8.7060104@gmail.com> <5E893DB832F57341992548CDBB333163A5A9B46658@EMBX01-HQ.jnpr.net> <8972B876-DD01-474E-9234-0133DC9DC119@gmx.net> <5E893DB832F57341992548CDBB333163A5A9B4665D@EMBX01-HQ.jnpr.net> <B8A47AD5-2038-4B59-BA43-CE243DE7B33F@gmx.net> <5E893DB832F57341992548CDBB333163A5A9B46866@EMBX01-HQ.jnpr.net> <E739DF84-EF5F-4855-A59A-5737E56F646F@gmx.net>
In-Reply-To: <E739DF84-EF5F-4855-A59A-5737E56F646F@gmx.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "iab@iab.org" <iab@iab.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, 16 Aug 2012 10:02:02 -0000

On 16/08/2012 09:10, Hannes Tschofenig wrote:
...
>> 4)  What is the relationship between this document and the mission of the ISOC, which, as I understand it, is to promote the open development, evolution, and use of the Internet?
> 
> The Internet Society needs to speak for themselves. 

Quite right. However, the IAB's charter includes advising the ISOC, and this
Affirmation can fit right in there.

    Brian

From hannes.tschofenig@gmx.net  Thu Aug 16 03:32:39 2012
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6DEC21F865C for <ietf@ietfa.amsl.com>; Thu, 16 Aug 2012 03:32:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.607
X-Spam-Level: 
X-Spam-Status: No, score=-102.607 tagged_above=-999 required=5 tests=[AWL=-0.008, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m1QKCi77sfaK for <ietf@ietfa.amsl.com>; Thu, 16 Aug 2012 03:32:38 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 693A121F84EB for <ietf@ietf.org>; Thu, 16 Aug 2012 03:32:38 -0700 (PDT)
Received: (qmail invoked by alias); 16 Aug 2012 10:32:37 -0000
Received: from a88-115-216-191.elisa-laajakaista.fi (EHLO [192.168.100.105]) [88.115.216.191] by mail.gmx.net (mp035) with SMTP; 16 Aug 2012 12:32:37 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19kHus6qEBket6gSfPWpPyb1x9BqG5VfgqV4anDc9 mTZBpy9BIN61DB
Subject: Re: Affirmation of the Modern Global Standards Paradigm
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: <502CC51E.80500@gmail.com>
Date: Thu, 16 Aug 2012 13:32:35 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <4C20AB79-8C0F-47E6-89D1-07D246C361A1@gmx.net>
References: <5E893DB832F57341992548CDBB333163A5A9B462FF@EMBX01-HQ.jnpr.net> <502B40B7.8050100@cisco.com> <502B48E8.7060104@gmail.com> <5E893DB832F57341992548CDBB333163A5A9B46658@EMBX01-HQ.jnpr.net> <8972B876-DD01-474E-9234-0133DC9DC119@gmx.net> <5E893DB832F57341992548CDBB333163A5A9B4665D@EMBX01-HQ.jnpr.net> <B8A47AD5-2038-4B59-BA43-CE243DE7B33F@gmx.net> <5E893DB832F57341992548CDBB333163A5A9B46866@EMBX01-HQ.jnpr.net> <E739DF84-EF5F-4855-A59A-5737E56F646F@gmx.net> <502CC51E.80500@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
X-Y-GMX-Trusted: 0
Cc: "iab@iab.org" <iab@iab.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, 16 Aug 2012 10:32:39 -0000

You seem to know the IAB charter quite well, Brian!

It is true that the mission of the Internet Society is "To promote the =
open development, evolution, and use of the Internet for the benefit of =
all people throughout the world".=20

The principles listed in the discussed document are a good fit to the =
values of the Internet Society. =20

On Aug 16, 2012, at 1:02 PM, Brian E Carpenter wrote:

> On 16/08/2012 09:10, Hannes Tschofenig wrote:
> ...
>>> 4)  What is the relationship between this document and the mission =
of the ISOC, which, as I understand it, is to promote the open =
development, evolution, and use of the Internet?
>>=20
>> The Internet Society needs to speak for themselves.=20
>=20
> Quite right. However, the IAB's charter includes advising the ISOC, =
and this
> Affirmation can fit right in there.
>=20
>    Brian


From johnl@iecc.com  Thu Aug 16 11:31:33 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8902521F85DA for <ietf@ietfa.amsl.com>; Thu, 16 Aug 2012 11:31:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.411
X-Spam-Level: 
X-Spam-Status: No, score=-110.411 tagged_above=-999 required=5 tests=[AWL=-0.701, BAYES_05=-1.11, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oeR8htfjCIh1 for <ietf@ietfa.amsl.com>; Thu, 16 Aug 2012 11:31:33 -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 7EB9821F85D0 for <ietf@ietf.org>; Thu, 16 Aug 2012 11:31:32 -0700 (PDT)
Received: (qmail 25126 invoked from network); 16 Aug 2012 18:31:30 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 16 Aug 2012 18:31:30 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=502d3c81.xn--i8sz2z.k1208; i=johnl@user.iecc.com; bh=5QI1T5SZLQKNTuff6fnKYkru8P88oq4QJhvJwAERgVU=; b=RDVWaDTuaue9MjtfcvaWnqKfeXPDzBho/SQ3cJOFNiDJvO4JB/y46BBSDpNbQVIm9qO9L52L4t7ySzEvflE2gjEvJAilWOPaBgjIlR/6B6A6PGxkgLCGC3giys4dfWx3utRGKyroRXVHIhRHYxT2iBX1JEPMfXnhXDEer8L2H4E=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=502d3c81.xn--i8sz2z.k1208; olt=johnl@user.iecc.com; bh=5QI1T5SZLQKNTuff6fnKYkru8P88oq4QJhvJwAERgVU=; b=Iq8F/JW2BCOqVMkFK+QNA4aAyahAQIoJ52SX8c+p/ypi7NSTliy7sZjxjKNHuKg63g0K7YhrtcOgg+hVItW5/Zhz0CB2kW13T8Aj9+PE1W8Pabk00rKoCmALieICt4egWIl7ltFsM8imLN9/VauKD4Fp6Fje8dyzJpfFyiIIgBs=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 16 Aug 2012 18:31:07 -0000
Message-ID: <20120816183107.69683.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: [IAB] IETF 92 in Dallas!
In-Reply-To: <CAHBDyN5ewsYm1kgk0WL_8mfHqdgQ6e-iPhk4po5-uR+Bmi63Eg@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Aug 2012 18:31:33 -0000

>People also should be aware that Dallas has major transit and highway work
>underway right now in particular North of the airport.  By 2015 (2014
>actually), you will be able to take light rail (orange line) from the
>airport to downtown:
>http://www.dart.org/about/expansion/orangeline.asp

Somehow it just won't be the same if we don't have to wade through
waist deep water.

R's,
John

From fred@cisco.com  Thu Aug 16 11:59:32 2012
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E9AC21F853F; Thu, 16 Aug 2012 11:59:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.504
X-Spam-Level: 
X-Spam-Status: No, score=-110.504 tagged_above=-999 required=5 tests=[AWL=0.095, 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 Y4Pi3fzjT4i9; Thu, 16 Aug 2012 11:59:32 -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 EAF0421F85DA; Thu, 16 Aug 2012 11:59:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=723; q=dns/txt; s=iport; t=1345143572; x=1346353172; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=UAxes00Spk1NWUMxX1rCyFpp56U9jJaKaJ8PtA5Rw3s=; b=Gi49we5RecGmdmNH3ayzItZGq5tRmuAmbof4ZxZohp7/zXGTAkqg8o3B yV+mkNG8fQjZKne+ztDoM0QHuZEkaIUyk2G/NDU8X6KGVldxrThJCrcww nKE7utOITJY5v/tSmJesrcnFSCXJ/mPktSCfVozsk4VWvMksZuOcjWYM9 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAM9CLVCtJV2c/2dsb2JhbABFui2BB4IgAQEBBBIBJz8QAgEIDgoeEDIlAgQOJ4drmk6gQIsKhXdgA5VPjiyBZoJf
X-IronPort-AV: E=Sophos;i="4.77,780,1336348800"; d="scan'208";a="112369495"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-3.cisco.com with ESMTP; 16 Aug 2012 18:59:31 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id q7GIxVgk018549 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 16 Aug 2012 18:59:31 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.97]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.02.0298.004; Thu, 16 Aug 2012 13:59:30 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Arturo Servin <aservin@lacnic.net>
Subject: Re: IETF 92 in Dallas!
Thread-Topic: IETF 92 in Dallas!
Thread-Index: AQHNexjl8crCkcCVmkiACyxTrfHTzZdcHm4AgAEBs4A=
Date: Thu, 16 Aug 2012 18:59:29 +0000
Message-ID: <E4C5EA9B-9F60-4A8F-98F9-AC86E1407F5A@cisco.com>
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net>
In-Reply-To: <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.89.130]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19120.001
x-tm-as-result: No--36.741000-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-ID: <DE65182C30DBC546BF1BAEB4F5845B75@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "wgchairs@ietf.org Group" <wgchairs@ietf.org>, IETF discussion list <ietf@ietf.org>, "iaoc@ietf.org" <iaoc@ietf.org>, IAB IAB <iab@iab.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Aug 2012 18:59:32 -0000

On Aug 15, 2012, at 8:37 PM, Arturo Servin wrote:
> 	So "Americas" was actually "North America".
>=20
> 	Well, it went the possibility to have one in central or south america, w=
hat at shame. At least until IETF 98 in March 2017 no IETF down the south o=
f Rio Grande.
>=20
> 	May I ask the IAOC, what are the impediments to have one IETF in Latin A=
merica?
>=20
> Regards,
> as

It was investigated and dropped, having gotten hotel pricing and found it u=
nusually high. I'm told that there is further discussion targeting finding =
ways to reduce that. We have had similar investigations and decisions in ot=
her places. You'll note that the IAOC is routinely tarred and feathered ove=
r prices...=

From tony@att.com  Thu Aug 16 12:49:31 2012
Return-Path: <tony@att.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1963621F8644 for <ietf@ietfa.amsl.com>; Thu, 16 Aug 2012 12:49: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=[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 040Av4Ihp7Bb for <ietf@ietfa.amsl.com>; Thu, 16 Aug 2012 12:49:30 -0700 (PDT)
Received: from nbfkord-smmo03.seg.att.com (nbfkord-smmo03.seg.att.com [209.65.160.84]) by ietfa.amsl.com (Postfix) with ESMTP id 5BACD21F8639 for <ietf@ietf.org>; Thu, 16 Aug 2012 12:49:30 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo03.seg.att.com(mxl_mta-6.11.0-10) over TLS secured channel with ESMTP id 9ce4d205.0.1026515.00-372.2799113.nbfkord-smmo03.seg.att.com (envelope-from <tony@att.com>);  Thu, 16 Aug 2012 19:49:30 +0000 (UTC)
X-MXL-Hash: 502d4eca4c1a5497-ebe607d449cc1025ede31ef7c010f4d3ef7bf6b7
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q7GJnTvc019406 for <ietf@ietf.org>; Thu, 16 Aug 2012 15:49:29 -0400
Received: from sflint02.pst.cso.att.com (sflint02.pst.cso.att.com [144.154.234.229]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q7GJnJ9U019329 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 16 Aug 2012 15:49:22 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by sflint02.pst.cso.att.com (RSA Interceptor) for <ietf@ietf.org>; Thu, 16 Aug 2012 15:49:02 -0400
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q7GJn0g6022100 for <ietf@ietf.org>; Thu, 16 Aug 2012 15:49:00 -0400
Received: from dns.maillennium.att.com (mailgw1.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q7GJmsDb021892 for <ietf@ietf.org>; Thu, 16 Aug 2012 15:48:55 -0400
Received: from [135.91.110.250] (ds135-91-110-250.dhcps.ugn.att.com[135.91.110.250]) by maillennium.att.com (mailgw1) with ESMTP id <20120816194409gw100ssp1ie> (Authid: tony); Thu, 16 Aug 2012 19:44:09 +0000
X-Originating-IP: [135.91.110.250]
Message-ID: <502D4EA5.5010102@att.com>
Date: Thu, 16 Aug 2012 15:48:53 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: [IAB] IETF 92 in Dallas!
References: <20120816183107.69683.qmail@joyce.lan>
In-Reply-To: <20120816183107.69683.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <tony@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=1.0 c=1 a=F1dFhQVZNxAA:10 a=70aWqWLk7fkA:10 a=Faw-SIVlas]
X-AnalysisOut: [YA:10 a=ofMgfj31e3cA:10 a=BLceEmwcHowA:10 a=IkcTkHD0fZMA:1]
X-AnalysisOut: [0 a=Wpo9Exr4s7IA:10 a=ZRNLZ4dFUbCvG8UMqPvVAA==:17 a=MVvioM]
X-AnalysisOut: [_dAAAA:8 a=JYdphXC1Yd2GxxcK3e0A:9 a=QEXdDO2ut3YA:10 a=QHgZ]
X-AnalysisOut: [d7p0mpgA:10]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Aug 2012 19:49:31 -0000

ah, the memories ...

     Tony Hansen

On 8/16/2012 2:31 PM, John Levine wrote:
>> People also should be aware that Dallas has major transit and highway work
>> underway right now in particular North of the airport.  By 2015 (2014
>> actually), you will be able to take light rail (orange line) from the
>> airport to downtown:
>> http://www.dart.org/about/expansion/orangeline.asp
> Somehow it just won't be the same if we don't have to wade through
> waist deep water.
>
> R's,
> John


From carlosm3011@gmail.com  Thu Aug 16 14:07:55 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81D8A21F85D7 for <ietf@ietfa.amsl.com>; Thu, 16 Aug 2012 14:07:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.539
X-Spam-Level: 
X-Spam-Status: No, score=-3.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o8Zyhfs6MwnV for <ietf@ietfa.amsl.com>; Thu, 16 Aug 2012 14:07:55 -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 E000121F8541 for <ietf@ietf.org>; Thu, 16 Aug 2012 14:07:54 -0700 (PDT)
Received: by yenm5 with SMTP id m5so3734476yen.31 for <ietf@ietf.org>; Thu, 16 Aug 2012 14:07:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=rWXLJK+BGaO7vEpD0KZph1GqFL1Rm3lrl3q+3mlJMXU=; b=mlLbcmVitaWKbBrvQKmWj6nQvGt3YijhXbOYy/anBV3gkx+oS5tWcvMN5itZEVxccx 7XgIEoSLYL0PZ+NW+2MaT2bQ116Bz8TP45+8m+jRA6ZC1SklMjL7u0IkNfMihQJLFUmL 11UK8sX0rsl7ZYnWpHHzUB3aW3O8K5gqPXmnF97EV3bKqPDgA/1A7VxSjbfcG7goTecX FWtNkwZhGEq6cql9fSKYGsMc5GoHvvJqAd4VdCQjZpwOOYGr0fEQNe+5F3JB0Qnuf9F9 VRXOhDgCpq87cJ6R5T4HeikFgNxSCNUT4bWaUqUq3n0da3W1pNa43jV3ZMORq8gcY951 Xdpg==
Received: by 10.236.73.198 with SMTP id v46mr3760408yhd.80.1345151274400; Thu, 16 Aug 2012 14:07:54 -0700 (PDT)
Received: from europa.local ([200.7.85.154]) by mx.google.com with ESMTPS id z5sm5306931ang.7.2012.08.16.14.07.52 (version=SSLv3 cipher=OTHER); Thu, 16 Aug 2012 14:07:53 -0700 (PDT)
Message-ID: <502D6126.4050201@gmail.com>
Date: Thu, 16 Aug 2012 18:07:50 -0300
From: "Carlos M. martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Tony Hansen <tony@att.com>
Subject: Re: [IAB] IETF 92 in Dallas!
References: <20120816183107.69683.qmail@joyce.lan> <502D4EA5.5010102@att.com>
In-Reply-To: <502D4EA5.5010102@att.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: John Levine <johnl@taugh.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Aug 2012 21:07:55 -0000

Fond memories of my first IETF... We were stuck at a highway exit for 4
hours unable to either cross the swollen river that had been a side road
minutes before or to go back.

:=)

~Carlos

On 8/16/12 4:48 PM, Tony Hansen wrote:
> ah, the memories ...
> 
>     Tony Hansen
> 
> On 8/16/2012 2:31 PM, John Levine wrote:
>>> People also should be aware that Dallas has major transit and highway
>>> work
>>> underway right now in particular North of the airport.  By 2015 (2014
>>> actually), you will be able to take light rail (orange line) from the
>>> airport to downtown:
>>> http://www.dart.org/about/expansion/orangeline.asp
>> Somehow it just won't be the same if we don't have to wade through
>> waist deep water.
>>
>> R's,
>> John
> 

From bob.hinden@gmail.com  Thu Aug 16 14:12:07 2012
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E901611E8097; Thu, 16 Aug 2012 14:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.504
X-Spam-Level: 
X-Spam-Status: No, score=-103.504 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RVC9ycVYymzn; Thu, 16 Aug 2012 14:12:07 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 773E021F8628; Thu, 16 Aug 2012 14:12:07 -0700 (PDT)
Received: by pbbrr4 with SMTP id rr4so2171986pbb.31 for <multiple recipients>; Thu, 16 Aug 2012 14:12:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=ocup7Hyb88OeHxFBbvmJwqvp4Yf4Gp6NrhHlx5T/saA=; b=WUjK250//Vj1wcKhD6Hqvu7jcdDJ0VtlNPZG7gRnaXTZsHXq64tNFWZ+F77BYQC652 h1GSw4qK2aFiNfZ/Qe9WWGrC7mlr68MOg4ejh9IHYTxwDYT1ZYhMDOZv/ky8IeFhkWw6 9362DAN3whqEc9bLo4uUxDFan4Wl16KxSR4mpDmASE39dogh7iidYD8Iu1mvQNhTCLTf TQ/DYngnmpTj/45/RhU9yWqNdKT04lzqzMk1tb+9ScaUSZkV3IXSDqRAonPxVxwyqtfY N2m6Fws0cjtfHui4HcS0EB9g8tcidTw7/xH5Un6iAy+/cHdAmFbC5exLYL2nkOITkmt3 /9kw==
Received: by 10.68.131.103 with SMTP id ol7mr6159566pbb.71.1345151527131; Thu, 16 Aug 2012 14:12:07 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPS id rm9sm3355972pbc.72.2012.08.16.14.12.00 (version=SSLv3 cipher=OTHER); Thu, 16 Aug 2012 14:12:01 -0700 (PDT)
Subject: Re: IETF 92 in Dallas!
Mime-Version: 1.0 (Apple Message framework v1280)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net>
Date: Thu, 16 Aug 2012 14:12:00 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <BA2EE8F7-92C8-4F10-B10A-2B6FE4FC954A@gmail.com>
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net>
To: Arturo Servin <aservin@lacnic.net>
X-Mailer: Apple Mail (2.1280)
Cc: iaoc@ietf.org, Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Aug 2012 21:12:08 -0000

Arturo,

[Reducing the cc: list to just the IETF and IAOC lists]

The IAOC seriously investigated a venue in South America for IETF92, but =
based on the data we collected it did not meet the criteria for IETF =
meetings.  We are continuing to talk with the group that suggested the =
venue and are also looking at other venues in that region for future =
meetings. =20

We have open meeting slots in 2015-2017.

Bob
IAOC Chair


On Aug 15, 2012, at 8:37 PM, Arturo Servin wrote:

>=20
> 	So "Americas" was actually "North America".
>=20
> 	Well, it went the possibility to have one in central or south =
america, what at shame. At least until IETF 98 in March 2017 no IETF =
down the south of Rio Grande.
>=20
> 	May I ask the IAOC, what are the impediments to have one IETF in =
Latin America?
>=20
> Regards,
> as
>=20
> On 15 Aug 2012, at 14:04, IETF Administrative Director wrote:
>=20
>> The IAOC is pleased to announce Dallas, TX, USA as the site for IETF =
92 from March 22-27,=20
>> 2015.  The IETF was last in Dallas for IETF 65 in 2006.  IETF 92 will =
be at a different venue in=20
>> the Dallas Arts District.
>>=20


From aservin@lacnic.net  Thu Aug 16 14:15:33 2012
Return-Path: <aservin@lacnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70E8921F84A7; Thu, 16 Aug 2012 14:15:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.048
X-Spam-Level: 
X-Spam-Status: No, score=-1.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V2DF0f2wXJqC; Thu, 16 Aug 2012 14:15:33 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id DA10C21F84C2; Thu, 16 Aug 2012 14:15:32 -0700 (PDT)
Received: from 85-7-200.lacnic.net.uy (unknown [200.7.85.90]) by mail.lacnic.net.uy (Postfix) with ESMTP id 23585308445; Thu, 16 Aug 2012 18:15:22 -0300 (UYT)
Subject: Re: IETF 92 in Dallas!
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Arturo Servin <aservin@lacnic.net>
In-Reply-To: <BA2EE8F7-92C8-4F10-B10A-2B6FE4FC954A@gmail.com>
Date: Thu, 16 Aug 2012 18:15:20 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <189DE420-3579-42F1-B82D-720305A0B70C@lacnic.net>
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net> <BA2EE8F7-92C8-4F10-B10A-2B6FE4FC954A@gmail.com>
To: Bob Hinden <bob.hinden@gmail.com>
X-Mailer: Apple Mail (2.1278)
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: iaoc@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Aug 2012 21:15:33 -0000

Bob,

	Thanks! It is very nice to hear that you were seriously =
considering adding new venues for the IETF meetings.

	Hopefully you will find something suitable and somehow not very =
hard to go for everybody in the future.

Regards,
as

On 16 Aug 2012, at 18:12, Bob Hinden wrote:

> Arturo,
>=20
> [Reducing the cc: list to just the IETF and IAOC lists]
>=20
> The IAOC seriously investigated a venue in South America for IETF92, =
but based on the data we collected it did not meet the criteria for IETF =
meetings.  We are continuing to talk with the group that suggested the =
venue and are also looking at other venues in that region for future =
meetings. =20
>=20
> We have open meeting slots in 2015-2017.
>=20
> Bob
> IAOC Chair
>=20
>=20
> On Aug 15, 2012, at 8:37 PM, Arturo Servin wrote:
>=20
>>=20
>> 	So "Americas" was actually "North America".
>>=20
>> 	Well, it went the possibility to have one in central or south =
america, what at shame. At least until IETF 98 in March 2017 no IETF =
down the south of Rio Grande.
>>=20
>> 	May I ask the IAOC, what are the impediments to have one IETF in =
Latin America?
>>=20
>> Regards,
>> as
>>=20
>> On 15 Aug 2012, at 14:04, IETF Administrative Director wrote:
>>=20
>>> The IAOC is pleased to announce Dallas, TX, USA as the site for IETF =
92 from March 22-27,=20
>>> 2015.  The IETF was last in Dallas for IETF 65 in 2006.  IETF 92 =
will be at a different venue in=20
>>> the Dallas Arts District.
>>>=20


From johnl@taugh.com  Thu Aug 16 14:23:29 2012
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1365621F8644 for <ietf@ietfa.amsl.com>; Thu, 16 Aug 2012 14:23:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.593
X-Spam-Level: 
X-Spam-Status: No, score=-2.593 tagged_above=-999 required=5 tests=[AWL=0.007,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8YLZHxgWAbtb for <ietf@ietfa.amsl.com>; Thu, 16 Aug 2012 14:23:28 -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 3982321F8634 for <ietf@ietf.org>; Thu, 16 Aug 2012 14:23:27 -0700 (PDT)
Received: (qmail 55074 invoked from network); 16 Aug 2012 21:23:25 -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=d721.502d64cd.k1208; bh=l/dOWxxgMPCscxhR7Jczd7gno9jZWO2UTjkqITSKAuM=; b=OEJ1zo4OGTU14xt6bl6OS2MAbZFx9Z027Jzn1fCWmX7ph+JBP1kGmKqgtlBGyLE9Sd0bX3T/YoKNgiHkG/vM/bvxzAeEAAyn9VAptXbv5cTyOQ3/MClQlgMSFhvl6T3E4mGTx8rBlB2xN+5UKCyS2iPlbEVzPO5tzsTLJUuwnCo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=d721.502d64cd.k1208; bh=l/dOWxxgMPCscxhR7Jczd7gno9jZWO2UTjkqITSKAuM=; b=l1covkj8WrFYBVkwJ6X4yKxa1ggg4qT/8i0E6LiewmgK8FLOjimhgwlgUo0B5V03j+c/SK41Pc8fW3nLCBPSfVYR5vprA4XzniKgVQRKrw9M88QX7l32Dzy6uud8BMZRRtDPj16ujF0PS8qgFUheQEjD+/t5QyIimx73DHkLJZk=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 16 Aug 2012 21:23:03 -0000
Date: 16 Aug 2012 17:23:25 -0400
Message-ID: <alpine.BSF.2.00.1208161721590.15565@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Carlos M. martinez" <carlosm3011@gmail.com>
Subject: Re: [IAB] IETF 92 in Dallas!
In-Reply-To: <502D6126.4050201@gmail.com>
References: <20120816183107.69683.qmail@joyce.lan> <502D4EA5.5010102@att.com> <502D6126.4050201@gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Aug 2012 21:23:29 -0000

> Fond memories of my first IETF... We were stuck at a highway exit for 4
> hours unable to either cross the swollen river that had been a side road
> minutes before or to go back.

I got to DFW, called the place I was staying (a motel across the street 
from the venue) who told me that the water was several feet deep in front, 
so I snagged an overpriced room at the airport Marriott for the night.

> On 8/16/12 4:48 PM, Tony Hansen wrote:
>> ah, the memories ...
>>
>>     Tony Hansen
>>
>> On 8/16/2012 2:31 PM, John Levine wrote:
>>>> People also should be aware that Dallas has major transit and highway
>>>> work
>>>> underway right now in particular North of the airport.  By 2015 (2014
>>>> actually), you will be able to take light rail (orange line) from the
>>>> airport to downtown:
>>>> http://www.dart.org/about/expansion/orangeline.asp
>>> Somehow it just won't be the same if we don't have to wade through
>>> waist deep water.
>>>
>>> R's,
>>> John
>>
>

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From barryleiba@gmail.com  Thu Aug 16 14:29:45 2012
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F6F611E808E for <ietf@ietfa.amsl.com>; Thu, 16 Aug 2012 14:29:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.013
X-Spam-Level: 
X-Spam-Status: No, score=-103.013 tagged_above=-999 required=5 tests=[AWL=-0.036, 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 xltOuGgJvwws for <ietf@ietfa.amsl.com>; Thu, 16 Aug 2012 14:29:45 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 46A4B21F867D for <ietf@ietf.org>; Thu, 16 Aug 2012 14:29:40 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so4773681obb.31 for <ietf@ietf.org>; Thu, 16 Aug 2012 14:29:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=oiq5Dg/WBYTjryimTqpWF5C9VQ60ZxZDk1Phd2jfyaU=; b=W2pAxXHvDCS1OfE+KVeAsK7Z/a3ppxOFbDdyJckVnZgcsP6PNrzojVK4qQhg6eB5Kx hmjvc2/5EW1A1mVtJ60MW/8uAYWz8KWXtbxu4yJghLarbNPj6c9/LRIsZd/GHkc8y4tB b4m30w8trucvZID+8wVFsWNVvZdHAxfi7BKB2Utm74E/GfEztrp92umcTgD1kLpiocrp KUt+omODuBoHdYwqS4xF9cB+tSnO8k5c2RX8j7JFUB4e3bbnsDtcGReTJuqzZyTLlq06 sqKQ3eVPoia4f4Q0LAM/w6lUu3C5aR7uYBE1MkXBN8uUg41rU1KjOx7OGlyZP2bJwZR2 GG9g==
MIME-Version: 1.0
Received: by 10.182.50.68 with SMTP id a4mr2205142obo.59.1345152579604; Thu, 16 Aug 2012 14:29:39 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.76.154.9 with HTTP; Thu, 16 Aug 2012 14:29:39 -0700 (PDT)
In-Reply-To: <20120816212429.3635.98463.idtracker@ietfa.amsl.com>
References: <20120816212429.3635.98463.idtracker@ietfa.amsl.com>
Date: Thu, 16 Aug 2012 17:29:39 -0400
X-Google-Sender-Auth: -V4adM6MnVP1xCHFgGmWKbNUoMg
Message-ID: <CALaySJKfGW-VWTQT1wUOia-=idwq0f-H=zhvFVcTxvqrvSu7pQ@mail.gmail.com>
Subject: Re: New Version Notification for draft-leiba-3777upd-eligibility-01.txt
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: Thu, 16 Aug 2012 21:29:45 -0000

SM and I have merged our 3777 update proposals, and we have posted the
merged version.  This is BCCed to the NomCom discussion list; please
take discussion of this to the main IETF discussion list now.

Reminder: the primary purpose of this is to add the IAOC to some of
the points in RFC 3777, since 3777 pre-dates the formation of the
IAOC.  Some of the IAOC-related processed are described in RFC 4333,
so this doesn't cover everything -- but it adds the IAOC to what we
think is appropriate.  It also incorporates the one Verified erratum
against 3777, and clarifies that a few other people should not be
eligible to volunteer for the NomCom -- in practical matters, it has
little effect, because most of them would not be volunteering anyway.

We aim to ask Russ to AD-sponsor this soon.  Further discussion is open.

Barry (and SM)

> A new version of I-D, draft-leiba-3777upd-eligibility-01.txt
> has been successfully submitted by Barry Leiba and posted to the
> IETF repository.
>
> Filename:        draft-leiba-3777upd-eligibility
> Revision:        01
> Title:           Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF Leadership
> Creation date:   2012-08-16
> WG ID:           Individual Submission
> Number of pages: 7
> URL:             http://www.ietf.org/internet-drafts/draft-leiba-3777upd-eligibility-01.txt
> Status:          http://datatracker.ietf.org/doc/draft-leiba-3777upd-eligibility
> Htmlized:        http://tools.ietf.org/html/draft-leiba-3777upd-eligibility-01
> Diff:            http://www.ietf.org/rfcdiff?url2=draft-leiba-3777upd-eligibility-01
>
> Abstract:
>    RFC 3777 specifies that "sitting members" of the IAB and IESG "may
>    not volunteer to serve on the nominating commitee".  Since that
>    document was written the IAOC was formed, and that body is not
>    covered by RFC 3777.  There is also uncertainty about whether ex-
>    officio members and liaisons are included as "sitting members".  This
>    document clarifies those situations.

From sarikaya2012@gmail.com  Thu Aug 16 14:41:52 2012
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F10A921F84C4 for <ietf@ietfa.amsl.com>; Thu, 16 Aug 2012 14:41:51 -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.037,  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 PEJJ6WpEh1Ld for <ietf@ietfa.amsl.com>; Thu, 16 Aug 2012 14:41: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 3FCF221F849D for <ietf@ietf.org>; Thu, 16 Aug 2012 14:41:50 -0700 (PDT)
Received: by iabz21 with SMTP id z21so608739iab.31 for <ietf@ietf.org>; Thu, 16 Aug 2012 14:41:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=MQCvAqIMZcw6ujUKGrqXC4aAN6WctOCmlr0of5Y7L4I=; b=gqALY2PWmDDC6QZbXN5Itgw4xakFHwTuEzu95K8uaceGac4pJ2/TvjiT/D5lzehbBP geYgzhFL5Y+Oom8870WvChu7GOtYKXY05dql7EUAqR/DhebOdDTAuOEXmVje6E1N2Bt7 elZDl5L03gHqZaF/LV2p86iyR8dttSYh75Jer7ULqdjmTRbY4hi4mN50LfoB4jNKL0kH sOU6HuClJmpLFf7URzLdcqtmVUOSFfGpa/svZfzX67Q5Fqow2EqPgc1ARlptK1qQlK+7 tC0wUNHq57Ymx12qE13RhPXgL1J2LZTTQty03+mOcEKQtQ9EvNaJB5RSxEH6mVLtzf6q /HlQ==
MIME-Version: 1.0
Received: by 10.42.31.5 with SMTP id x5mr2583366icc.40.1345153309531; Thu, 16 Aug 2012 14:41:49 -0700 (PDT)
Received: by 10.231.55.70 with HTTP; Thu, 16 Aug 2012 14:41:49 -0700 (PDT)
In-Reply-To: <alpine.BSF.2.00.1208161721590.15565@joyce.lan>
References: <20120816183107.69683.qmail@joyce.lan> <502D4EA5.5010102@att.com> <502D6126.4050201@gmail.com> <alpine.BSF.2.00.1208161721590.15565@joyce.lan>
Date: Thu, 16 Aug 2012 16:41:49 -0500
Message-ID: <CAC8QAcfwLrM=YBvF1SsbzqfPZE6jAAUTKEPr5qnYnDtzCbtLVA@mail.gmail.com>
Subject: Re: [IAB] IETF 92 in Dallas!
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: John R Levine <johnl@taugh.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Aug 2012 21:41:52 -0000

Folks, as a Dallas resident I have to let you know that the flooding
we had in 2006 happened after a long period of draught and the rain
was very welcome to the people at that time, may be not so much of it
of course :-).

It was a natural event that happens rarely in Dallas, in fact since
2006, it has not happened again. We do get stormy weather and a few
hour delays in DFW, so far, that's all.

Please do not equate Dallas to floods :-).

Regards,

Behcet

On Thu, Aug 16, 2012 at 4:23 PM, John R Levine <johnl@taugh.com> wrote:
>> Fond memories of my first IETF... We were stuck at a highway exit for 4
>> hours unable to either cross the swollen river that had been a side road
>> minutes before or to go back.
>
>
> I got to DFW, called the place I was staying (a motel across the street from
> the venue) who told me that the water was several feet deep in front, so I
> snagged an overpriced room at the airport Marriott for the night.
>
>
>> On 8/16/12 4:48 PM, Tony Hansen wrote:
>>>
>>> ah, the memories ...
>>>
>>>     Tony Hansen
>>>
>>> On 8/16/2012 2:31 PM, John Levine wrote:
>>>>>
>>>>> People also should be aware that Dallas has major transit and highway
>>>>> work
>>>>> underway right now in particular North of the airport.  By 2015 (2014
>>>>> actually), you will be able to take light rail (orange line) from the
>>>>> airport to downtown:
>>>>> http://www.dart.org/about/expansion/orangeline.asp
>>>>
>>>> Somehow it just won't be the same if we don't have to wade through
>>>> waist deep water.
>>>>
>>>> R's,
>>>> John
>>>
>>>
>>
>
> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> "I dropped the toothpaste", said Tom, crestfallenly.

From mary.ietf.barnes@gmail.com  Thu Aug 16 14:49:43 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33A2121F84D2 for <ietf@ietfa.amsl.com>; Thu, 16 Aug 2012 14:49:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.52
X-Spam-Level: 
X-Spam-Status: No, score=-103.52 tagged_above=-999 required=5 tests=[AWL=0.078, 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 KsPVoszuTRBE for <ietf@ietfa.amsl.com>; Thu, 16 Aug 2012 14:49:42 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id F120F21F84F9 for <ietf@ietf.org>; Thu, 16 Aug 2012 14:49:41 -0700 (PDT)
Received: by lahm15 with SMTP id m15so1784715lah.31 for <ietf@ietf.org>; Thu, 16 Aug 2012 14:49:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YG4h4z8Uci0NZHma6aRqUjY3L9lM8QplYSRqlayoEmA=; b=wTTJ9/xZgxyk+uwCzi2gnKIz83JiyVOcft2krVt3hNrv2dvsLfmBvchlLAAdCExhi4 TqOMiQBKU5NB6i5wlvgzKCP2cXOkB3awSiCkipwA1Rs9DE+I23ztoEA8kKd7uQaMo1Th 7gSG6UoZjwiGNN+B2YfsZAZcwOFyewcaVplXGfol0OBgYn60ZI3d6oG/nVp8/hCnfmgX W2drQbBGhytr40zVjpv+ZHp677BO67MFsxJ4jNlK/3xB3CIsUaRZU71O6ggu2RGmMPvi 6YsyilPIgCFO/t+9SNjdlGt0tBHuY4jK6/qgAz4Q0/da5Wa+NXvs0hziFlZDmVunT9zx 7aOQ==
MIME-Version: 1.0
Received: by 10.112.40.33 with SMTP id u1mr1320521lbk.28.1345153780088; Thu, 16 Aug 2012 14:49:40 -0700 (PDT)
Received: by 10.112.85.196 with HTTP; Thu, 16 Aug 2012 14:49:40 -0700 (PDT)
In-Reply-To: <502D4EA5.5010102@att.com>
References: <20120816183107.69683.qmail@joyce.lan> <502D4EA5.5010102@att.com>
Date: Thu, 16 Aug 2012 16:49:40 -0500
Message-ID: <CAHBDyN5XT_b0S07_fWJTWhPdqghdZCSKov1BhiBAnFqrQCx75Q@mail.gmail.com>
Subject: Re: [IAB] IETF 92 in Dallas!
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Tony Hansen <tony@att.com>
Content-Type: multipart/alternative; boundary=e0cb4efe30603b009f04c76905ad
Cc: John Levine <johnl@taugh.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Aug 2012 21:49:43 -0000

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

It is impossible to predict Dallas weather and I'd be the last person to
say I had any idea what the weather would be in March 2015.  March has some
of the most dramatic weather changes and differences - very much the lion
and the lamb.  However, I've lived in Dallas for 29 years and that was only
the 3rd time I had encountered a flash flood of that ilk.  However, I also
think that the Anatole is in one of the worse locations for flooding (right
next to the Trinity River).

That all said, Dallas has not done anything to prevent this sort of
flooding (with 2006 being the most severe recent flooding).   There is a
bond proposal to do so:
http://www.wfaa.com/news/local/Dallas-considers-bond-package-136675208.html
I guess it's a remote possibility something will be done before the meeting
in 2015.  This article references the 2006 flood.  As it does seem it might
just be time for a severe flood if we don't have one by then ;)

Mary.

On Thu, Aug 16, 2012 at 2:48 PM, Tony Hansen <tony@att.com> wrote:

> ah, the memories ...
>
>     Tony Hansen
>
> On 8/16/2012 2:31 PM, John Levine wrote:
>
>> People also should be aware that Dallas has major transit and highway work
>>> underway right now in particular North of the airport.  By 2015 (2014
>>> actually), you will be able to take light rail (orange line) from the
>>> airport to downtown:
>>> http://www.dart.org/about/**expansion/orangeline.asp<http://www.dart.org/about/expansion/orangeline.asp>
>>>
>> Somehow it just won't be the same if we don't have to wade through
>> waist deep water.
>>
>> R's,
>> John
>>
>
>

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

It is impossible to predict Dallas weather and I&#39;d be the last person t=
o say I had any idea what the weather would be in March 2015. =A0March has =
some of the most dramatic weather changes and differences - very much the l=
ion and the lamb. =A0However, I&#39;ve lived in Dallas for 29 years and tha=
t was only the 3rd time I had encountered a flash flood of that ilk. =A0How=
ever, I also think that the Anatole is in one of the worse locations for fl=
ooding (right next to the Trinity River).<div>
<br></div><div>That all said, Dallas has not done anything to prevent this =
sort of flooding (with 2006 being the most severe recent flooding). =A0 The=
re is a bond proposal to do so:</div><div><a href=3D"http://www.wfaa.com/ne=
ws/local/Dallas-considers-bond-package-136675208.html">http://www.wfaa.com/=
news/local/Dallas-considers-bond-package-136675208.html</a></div>
<div>I guess it&#39;s a remote possibility something will be done before th=
e meeting in 2015. =A0This article references the 2006 flood. =A0As it does=
 seem it might just be time for a severe flood if we don&#39;t have one by =
then ;)</div>
<div><br></div><div>Mary.=A0</div><div><br><div class=3D"gmail_quote">On Th=
u, Aug 16, 2012 at 2:48 PM, Tony Hansen <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:tony@att.com" target=3D"_blank">tony@att.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">
ah, the memories ...<br>
<br>
=A0 =A0 Tony Hansen<br>
<br>
On 8/16/2012 2:31 PM, John Levine wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
People also should be aware that Dallas has major transit and highway work<=
br>
underway right now in particular North of the airport. =A0By 2015 (2014<br>
actually), you will be able to take light rail (orange line) from the<br>
airport to downtown:<br>
<a href=3D"http://www.dart.org/about/expansion/orangeline.asp" target=3D"_b=
lank">http://www.dart.org/about/<u></u>expansion/orangeline.asp</a><br>
</blockquote>
Somehow it just won&#39;t be the same if we don&#39;t have to wade through<=
br>
waist deep water.<br>
<br>
R&#39;s,<br>
John<br>
</blockquote>
<br>
</blockquote></div><br></div>

--e0cb4efe30603b009f04c76905ad--

From hallam@gmail.com  Thu Aug 16 17:48:47 2012
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02B7221F8518; Thu, 16 Aug 2012 17:48:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.523
X-Spam-Level: 
X-Spam-Status: No, score=-5.523 tagged_above=-999 required=5 tests=[AWL=-1.924, 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 Hasu6SW-IEy7; Thu, 16 Aug 2012 17:48:45 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id A507221F851C; Thu, 16 Aug 2012 17:48:45 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so5001078obb.31 for <multiple recipients>; Thu, 16 Aug 2012 17:48:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=FZmb3AcvqBkR6BSvmONoSf+RgnWS7dcJVHjoyeyFt9Y=; b=lC5McyzhlDDWaY1YtVIeyaA+mzdYRM6rbFNooc/3smIRqiDKl7hnCdPZS+ZVEnziAi GSMJ0x9uQY/CPK4cuXuMGn+VPs+9cmFeh9mGecxIkfnglTEsg1Z2AA16zRHpzH1N+xyB NBqKWzymlFLp5/qWwtg+tz4atCbWNkb1pHbFGmaWzq6/ja0XTEHE1FsfSg0Glz8U0mbH Ujh5MfEe1Eq2s1nX4crQnfEiLGOqGh0tWqnHCSFWORYGRCA6Ae6HeZwFcDto7kStZRjL 4qhiHJKY+vhEXf7c5fPX+1qZc92qvfw77kv6Fh/mm3TGl9cUzWXwDRbHpPCPhmSkWoNv /eQQ==
MIME-Version: 1.0
Received: by 10.60.170.138 with SMTP id am10mr2445509oec.115.1345164524959; Thu, 16 Aug 2012 17:48:44 -0700 (PDT)
Received: by 10.76.80.10 with HTTP; Thu, 16 Aug 2012 17:48:44 -0700 (PDT)
In-Reply-To: <E4C5EA9B-9F60-4A8F-98F9-AC86E1407F5A@cisco.com>
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net> <E4C5EA9B-9F60-4A8F-98F9-AC86E1407F5A@cisco.com>
Date: Thu, 16 Aug 2012 20:48:44 -0400
Message-ID: <CAMm+Lwhz9VneHKvRzjcNH9_AbXisd2visc9pCc14hac5A3X4_Q@mail.gmail.com>
Subject: Re: IETF 92 in Dallas!
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "Fred Baker (fred)" <fred@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "iaoc@ietf.org" <iaoc@ietf.org>, "wgchairs@ietf.org Group" <wgchairs@ietf.org>, IAB IAB <iab@iab.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Aug 2012 00:48:47 -0000

It is possible that Brazil will be looking to host various
international conferences ahead of the Olympics as 'practice runs'.
China did that and so have other countries.

Given the Government of Brazil's interest in things Internetish it
might be an opening.

On Thu, Aug 16, 2012 at 2:59 PM, Fred Baker (fred) <fred@cisco.com> wrote:
>
> On Aug 15, 2012, at 8:37 PM, Arturo Servin wrote:
>>       So "Americas" was actually "North America".
>>
>>       Well, it went the possibility to have one in central or south amer=
ica, what at shame. At least until IETF 98 in March 2017 no IETF down the s=
outh of Rio Grande.
>>
>>       May I ask the IAOC, what are the impediments to have one IETF in L=
atin America?
>>
>> Regards,
>> as
>
> It was investigated and dropped, having gotten hotel pricing and found it=
 unusually high. I'm told that there is further discussion targeting findin=
g ways to reduce that. We have had similar investigations and decisions in =
other places. You'll note that the IAOC is routinely tarred and feathered o=
ver prices...



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

From narten@us.ibm.com  Thu Aug 16 21:53:13 2012
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D33C721F8522 for <ietf@ietfa.amsl.com>; Thu, 16 Aug 2012 21:53:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.327
X-Spam-Level: 
X-Spam-Status: No, score=-110.327 tagged_above=-999 required=5 tests=[AWL=0.272, 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 OCgsXmEQE0B5 for <ietf@ietfa.amsl.com>; Thu, 16 Aug 2012 21:53:12 -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 8E8F921F8467 for <ietf@ietf.org>; Thu, 16 Aug 2012 21:53:11 -0700 (PDT)
Received: from /spool/local by e6.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 17 Aug 2012 00:53:11 -0400
Received: from d01dlp03.pok.ibm.com (9.56.250.168) by e6.ny.us.ibm.com (192.168.1.106) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 17 Aug 2012 00:53:06 -0400
Received: from d01relay03.pok.ibm.com (d01relay03.pok.ibm.com [9.56.227.235]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id CB8FEC9003E for <ietf@ietf.org>; Fri, 17 Aug 2012 00:53:05 -0400 (EDT)
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay03.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q7H4r5Ff097058 for <ietf@ietf.org>; Fri, 17 Aug 2012 00:53:05 -0400
Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q7H4r5da010157 for <ietf@ietf.org>; Fri, 17 Aug 2012 00:53:05 -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 q7H4r5ju010154 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 17 Aug 2012 00:53:05 -0400
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q7H4r4rC014738 for <ietf@ietf.org>; Fri, 17 Aug 2012 00:53:04 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q7H4r3sW014705 for ietf@ietf.org; Fri, 17 Aug 2012 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201208170453.q7H4r3sW014705@rotala.raleigh.ibm.com>
Date: Fri, 17 Aug 2012 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-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12081704-1976-0000-0000-000010484BA0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Aug 2012 04:53:13 -0000

Total of 163 messages in the last 7 days.
 
script run at: Fri Aug 17 00:53:03 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  4.91% |    8 |  7.08% |    93340 | jdrake@juniper.net
  6.13% |   10 |  4.96% |    65386 | brian.e.carpenter@gmail.com
  4.91% |    8 |  4.77% |    62883 | sm@resistor.net
  3.68% |    6 |  4.00% |    52792 | hallam@gmail.com
  3.07% |    5 |  2.81% |    37061 | john-ietf@jck.com
  3.07% |    5 |  2.31% |    30431 | dhc@dcrocker.net
  2.45% |    4 |  2.71% |    35766 | david.black@emc.com
  1.84% |    3 |  3.11% |    40997 | richard@shockey.us
  2.45% |    4 |  2.40% |    31667 | abdussalambaryun@gmail.com
  2.45% |    4 |  2.21% |    29133 | hannes.tschofenig@gmx.net
  1.23% |    2 |  3.39% |    44784 | adrian@olddog.co.uk
  2.45% |    4 |  1.91% |    25205 | ynir@checkpoint.com
  2.45% |    4 |  1.79% |    23652 | cabo@tzi.org
  1.84% |    3 |  2.28% |    30052 | lear@cisco.com
  1.84% |    3 |  2.26% |    29764 | mfberny@gmail.com
  1.84% |    3 |  2.04% |    26922 | glenzorn@gmail.com
  1.23% |    2 |  2.54% |    33489 | gtw@gtwassociates.com
  1.84% |    3 |  1.73% |    22871 | mohta@necom830.hpcl.titech.ac.jp
  1.84% |    3 |  1.68% |    22222 | joelja@bogus.com
  1.84% |    3 |  1.60% |    21133 | barryleiba@computer.org
  1.84% |    3 |  1.52% |    20096 | ben@estacado.net
  1.84% |    3 |  1.01% |    13269 | jnc@mercury.lcs.mit.edu
  1.23% |    2 |  1.49% |    19633 | jeff.hodges@kingsmountain.com
  1.23% |    2 |  1.43% |    18863 | vesely@tana.it
  1.23% |    2 |  1.37% |    18076 | mary.ietf.barnes@gmail.com
  1.23% |    2 |  1.25% |    16504 | touch@isi.edu
  1.23% |    2 |  1.25% |    16488 | aalain@trstech.net
  1.23% |    2 |  1.21% |    15921 | tobias.gondrom@gondrom.org
  1.23% |    2 |  1.05% |    13824 | jmabdp@gmail.com
  1.23% |    2 |  0.99% |    13058 | bob.hinden@gmail.com
  1.23% |    2 |  0.95% |    12506 | mcr+ietf@sandelman.ca
  1.23% |    2 |  0.94% |    12449 | stbryant@cisco.com
  1.23% |    2 |  0.94% |    12401 | dcrocker@bbiw.net
  1.23% |    2 |  0.93% |    12321 | aservin@lacnic.net
  1.23% |    2 |  0.92% |    12117 | johnl@taugh.com
  1.23% |    2 |  0.84% |    11129 | sob@sobco.com
  1.23% |    2 |  0.84% |    11071 | mcr@sandelman.ca
  1.23% |    2 |  0.81% |    10704 | paul.hoffman@vpnc.org
  1.23% |    2 |  0.75% |     9927 | randy@psg.com
  0.61% |    1 |  1.33% |    17499 | eburger@standardstrack.com
  0.61% |    1 |  1.18% |    15504 | mstjohns@comcast.net
  0.61% |    1 |  1.12% |    14839 | ron.even.tlv@gmail.com
  0.61% |    1 |  1.02% |    13398 | bernard_aboba@hotmail.com
  0.61% |    1 |  0.91% |    12050 | daedulus@btconnect.com
  0.61% |    1 |  0.89% |    11704 | lars@netapp.com
  0.61% |    1 |  0.85% |    11149 | narten@us.ibm.com
  0.61% |    1 |  0.80% |    10523 | eburger-l@standardstrack.com
  0.61% |    1 |  0.67% |     8899 | philip.eardley@bt.com
  0.61% |    1 |  0.62% |     8165 | tbray@textuality.com
  0.61% |    1 |  0.60% |     7901 | nurit.sprecher@nsn.com
  0.61% |    1 |  0.59% |     7771 | marka@isc.org
  0.61% |    1 |  0.54% |     7189 | allison.mankin@gmail.com
  0.61% |    1 |  0.54% |     7187 | geoff@proto6.com
  0.61% |    1 |  0.53% |     7005 | agmalis@gmail.com
  0.61% |    1 |  0.53% |     6991 | stephen.farrell@cs.tcd.ie
  0.61% |    1 |  0.53% |     6947 | alejandroacostaalamo@gmail.com
  0.61% |    1 |  0.52% |     6912 | tony@att.com
  0.61% |    1 |  0.52% |     6859 | sarikaya2012@gmail.com
  0.61% |    1 |  0.51% |     6675 | fred@cisco.com
  0.61% |    1 |  0.51% |     6672 | ole@cisco.com
  0.61% |    1 |  0.50% |     6637 | ben@nostrum.com
  0.61% |    1 |  0.50% |     6583 | alastair.johnson@alcatel-lucent.com
  0.61% |    1 |  0.49% |     6481 | alexey.melnikov@isode.com
  0.61% |    1 |  0.49% |     6428 | d3e3e3@gmail.com
  0.61% |    1 |  0.47% |     6170 | ajs@anvilwalrusden.com
  0.61% |    1 |  0.46% |     6118 | ruediger.geib@telekom.de
  0.61% |    1 |  0.46% |     6097 | carlosm3011@gmail.com
  0.61% |    1 |  0.45% |     5962 | bertietf@bwijnen.net
  0.61% |    1 |  0.44% |     5858 | lixia@cs.ucla.edu
  0.61% |    1 |  0.43% |     5648 | chair@ietf.org
  0.61% |    1 |  0.40% |     5234 | drc@virtualized.org
  0.61% |    1 |  0.40% |     5216 | hartmans-ietf@mit.edu
  0.61% |    1 |  0.39% |     5172 | michael.tuexen@lurchi.franken.de
  0.61% |    1 |  0.39% |     5092 | iad@ietf.org
  0.61% |    1 |  0.37% |     4825 | jari.arkko@piuha.net
--------+------+--------+----------+------------------------
100.00% |  163 |100.00% |  1319267 | Total


From touch@isi.edu  Fri Aug 17 03:16:13 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF60E21F8473; Fri, 17 Aug 2012 03:16:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.493
X-Spam-Level: 
X-Spam-Status: No, score=-105.493 tagged_above=-999 required=5 tests=[AWL=1.106, 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 AKdD2r67lqFa; Fri, 17 Aug 2012 03:16:13 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 2107021F8467; Fri, 17 Aug 2012 03:16:13 -0700 (PDT)
Received: from [128.9.176.217] (c2-vpn05.isi.edu [128.9.176.217]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q7HAFR8H023548 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 17 Aug 2012 03:15:29 -0700 (PDT)
Message-ID: <502E19BB.2020101@isi.edu>
Date: Fri, 17 Aug 2012 03:15:23 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: philip.eardley@bt.com
Subject: Re: Gen-ART LC Review of draft-ietf-mptcp-api-05
References: <CCBAA297-B839-4AEA-BB24-F4D320200415@nostrum.com> <9510D26531EF184D9017DF24659BB87F33D6B96847@EMV65-UKRD.domain1.systemhost.net>
In-Reply-To: <9510D26531EF184D9017DF24659BB87F33D6B96847@EMV65-UKRD.domain1.systemhost.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: ben@nostrum.com, gen-art@ietf.org, draft-ietf-mptcp-api.all@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Aug 2012 10:16:13 -0000

On 8/13/2012 7:14 AM, philip.eardley@bt.com wrote:
> Ben,
> Thanks for your review.
>
> The right status isn't clear-cut (I think), but when we (Chairs & Wes) discussed it, Info seemed best
> * mainly because precedent seems to be that API docs are informational, for example socket API extensions for SCTP http://datatracker.ietf.org/doc/rfc6458/

This has been a big mistake in the past, IMO.

A key part of the definition of any protocol is its API. It is exactly 
as important as the "on the wire" component and the endpoint state and 
semantics of message exchanges.

See RFC793 for a great example. What we know as sockets there is 
basically a direct implementation of the *specified* API for TCP.

I can't argue that this document is a reason for the IETF to correct its 
past mistake, but the sooner it does the better. APIs ought to be a 
*mandatory* part of any protocol specification. As such, they should be 
at the same level as any other part of that spec (e.g.., standards track 
or experimental).

Joe

From housley@vigilsec.com  Fri Aug 17 07:06:09 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DE5621F8593 for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 07:06:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.349
X-Spam-Level: 
X-Spam-Status: No, score=-102.349 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8uuHHtl2wwmL for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 07:06:08 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 5962521F858A for <ietf@ietf.org>; Fri, 17 Aug 2012 07:06:03 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 5BB2AF240B9; Fri, 17 Aug 2012 10:06:25 -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 SkB8Mxw5Q9BG; Fri, 17 Aug 2012 10:05:36 -0400 (EDT)
Received: from [192.168.1.3] (96-37-2-47.dhcp.sffl.va.charter.com [96.37.2.47]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id CCAEFF240B8; Fri, 17 Aug 2012 10:06:23 -0400 (EDT)
Subject: Re: New Version Notification for draft-leiba-3777upd-eligibility-01.txt
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <CALaySJKfGW-VWTQT1wUOia-=idwq0f-H=zhvFVcTxvqrvSu7pQ@mail.gmail.com>
Date: Fri, 17 Aug 2012 10:05:59 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <06515DE7-EA23-45EC-9C85-E4003777073F@vigilsec.com>
References: <20120816212429.3635.98463.idtracker@ietfa.amsl.com> <CALaySJKfGW-VWTQT1wUOia-=idwq0f-H=zhvFVcTxvqrvSu7pQ@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>, S Moonesamy <sm+ietf@elandsys.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, 17 Aug 2012 14:06:09 -0000

The document says:

 	   o  Bullet 3, paragraph 1 is replaced by this:=09
 	=09
 	         The nominating committee comprises at least a Chair, 10 =
voting=09
 	         volunteers, 4 liaisons, and an advisor.

The Past Chair is missing.

The adviser is not required, as implied by the "at least" in this =
sentence.

Also, if I understand properly, the ISOC BoT is allowed to provide a =
liaison, but they are not required to do so.

Russ


On Aug 16, 2012, at 5:29 PM, Barry Leiba wrote:

> SM and I have merged our 3777 update proposals, and we have posted the
> merged version.  This is BCCed to the NomCom discussion list; please
> take discussion of this to the main IETF discussion list now.
>=20
> Reminder: the primary purpose of this is to add the IAOC to some of
> the points in RFC 3777, since 3777 pre-dates the formation of the
> IAOC.  Some of the IAOC-related processed are described in RFC 4333,
> so this doesn't cover everything -- but it adds the IAOC to what we
> think is appropriate.  It also incorporates the one Verified erratum
> against 3777, and clarifies that a few other people should not be
> eligible to volunteer for the NomCom -- in practical matters, it has
> little effect, because most of them would not be volunteering anyway.
>=20
> We aim to ask Russ to AD-sponsor this soon.  Further discussion is =
open.
>=20
> Barry (and SM)
>=20
>> A new version of I-D, draft-leiba-3777upd-eligibility-01.txt
>> has been successfully submitted by Barry Leiba and posted to the
>> IETF repository.
>>=20
>> Filename:        draft-leiba-3777upd-eligibility
>> Revision:        01
>> Title:           Update to RFC 3777 to Clarify Nominating Committee =
Eligibility of IETF Leadership
>> Creation date:   2012-08-16
>> WG ID:           Individual Submission
>> Number of pages: 7
>> URL:             =
http://www.ietf.org/internet-drafts/draft-leiba-3777upd-eligibility-01.txt=

>> Status:          =
http://datatracker.ietf.org/doc/draft-leiba-3777upd-eligibility
>> Htmlized:        =
http://tools.ietf.org/html/draft-leiba-3777upd-eligibility-01
>> Diff:            =
http://www.ietf.org/rfcdiff?url2=3Ddraft-leiba-3777upd-eligibility-01
>>=20
>> Abstract:
>>   RFC 3777 specifies that "sitting members" of the IAB and IESG "may
>>   not volunteer to serve on the nominating commitee".  Since that
>>   document was written the IAOC was formed, and that body is not
>>   covered by RFC 3777.  There is also uncertainty about whether ex-
>>   officio members and liaisons are included as "sitting members".  =
This
>>   document clarifies those situations.


From wjhns1@hardakers.net  Fri Aug 17 07:06:10 2012
Return-Path: <wjhns1@hardakers.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 635F821F859A for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 07:06:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.308
X-Spam-Level: 
X-Spam-Status: No, score=-2.308 tagged_above=-999 required=5 tests=[AWL=0.292,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2HphyXxvYLhl for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 07:06:09 -0700 (PDT)
Received: from mail.hardakers.net (unknown [IPv6:2001:470:1f00:187::1]) by ietfa.amsl.com (Postfix) with ESMTP id BB53E21F858A for <ietf@ietf.org>; Fri, 17 Aug 2012 07:06:09 -0700 (PDT)
Received: from localhost (wjhw.hardakers.net [IPv6:2001:470:1f00:187:62d8:19ff:fed4:c8b6]) by mail.hardakers.net (Postfix) with ESMTPSA id E71BE5FB; Fri, 17 Aug 2012 07:06:04 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: sarikaya@ieee.org
Subject: Re: [IAB] IETF 92 in Dallas!
References: <20120816183107.69683.qmail@joyce.lan> <502D4EA5.5010102@att.com> <502D6126.4050201@gmail.com> <alpine.BSF.2.00.1208161721590.15565@joyce.lan> <CAC8QAcfwLrM=YBvF1SsbzqfPZE6jAAUTKEPr5qnYnDtzCbtLVA@mail.gmail.com>
Date: Fri, 17 Aug 2012 07:06:04 -0700
In-Reply-To: <CAC8QAcfwLrM=YBvF1SsbzqfPZE6jAAUTKEPr5qnYnDtzCbtLVA@mail.gmail.com> (Behcet Sarikaya's message of "Thu, 16 Aug 2012 16:41:49 -0500")
Message-ID: <0lmx1twr3n.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.130004 (Ma Gnus v0.4) Emacs/23.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Cc: John R Levine <johnl@taugh.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Aug 2012 14:06:10 -0000

Behcet Sarikaya <sarikaya2012@gmail.com> writes:

> It was a natural event that happens rarely in Dallas, in fact since
> 2006, it has not happened again.

That's because we haven't been back yet.
-- 
Wes Hardaker
SPARTA, Inc.

From housley@vigilsec.com  Fri Aug 17 07:21:33 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 092FC21F8493 for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 07:21:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.362
X-Spam-Level: 
X-Spam-Status: No, score=-102.362 tagged_above=-999 required=5 tests=[AWL=0.237, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MJtBmfDsAO0O for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 07:21:32 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 4E4BF21F8462 for <ietf@ietf.org>; Fri, 17 Aug 2012 07:21:32 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 20D90F240BA; Fri, 17 Aug 2012 10:21:36 -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 6iPehpKmqYwn; Fri, 17 Aug 2012 10:21:28 -0400 (EDT)
Received: from [192.168.1.3] (96-37-2-47.dhcp.sffl.va.charter.com [96.37.2.47]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 3708EF240B9; Fri, 17 Aug 2012 10:21:34 -0400 (EDT)
Subject: Re: New Version Notification for draft-leiba-3777upd-eligibility-01.txt
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <CALaySJKfGW-VWTQT1wUOia-=idwq0f-H=zhvFVcTxvqrvSu7pQ@mail.gmail.com>
Date: Fri, 17 Aug 2012 10:21:28 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <161D0116-7034-4343-A788-03F10A0F85FC@vigilsec.com>
References: <20120816212429.3635.98463.idtracker@ietfa.amsl.com> <CALaySJKfGW-VWTQT1wUOia-=idwq0f-H=zhvFVcTxvqrvSu7pQ@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>, S Moonesamy <sm+ietf@elandsys.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, 17 Aug 2012 14:21:33 -0000

The document says:

 	   o  Bullet 15 is replaced by these two bullets:=09
 	=09
 	      15.1.  Members of the Internet Society Board of Trustees =
and=09
 	           sitting members of the IAB, the IESG, and the IAOC, =
including=09
 	           members in ex-officio positions, and not including =
liaisons,=09
 	           may not volunteer to serve as voting members of the=09=

 	           nominating committee.

I find "liaison" confusing here.  You mean liaisons to the IESG, IAB, =
and IAOC.  You do not mean liaisons to the NomCom.

Russ


On Aug 16, 2012, at 5:29 PM, Barry Leiba wrote:

> SM and I have merged our 3777 update proposals, and we have posted the
> merged version.  This is BCCed to the NomCom discussion list; please
> take discussion of this to the main IETF discussion list now.
>=20
> Reminder: the primary purpose of this is to add the IAOC to some of
> the points in RFC 3777, since 3777 pre-dates the formation of the
> IAOC.  Some of the IAOC-related processed are described in RFC 4333,
> so this doesn't cover everything -- but it adds the IAOC to what we
> think is appropriate.  It also incorporates the one Verified erratum
> against 3777, and clarifies that a few other people should not be
> eligible to volunteer for the NomCom -- in practical matters, it has
> little effect, because most of them would not be volunteering anyway.
>=20
> We aim to ask Russ to AD-sponsor this soon.  Further discussion is =
open.
>=20
> Barry (and SM)
>=20
>> A new version of I-D, draft-leiba-3777upd-eligibility-01.txt
>> has been successfully submitted by Barry Leiba and posted to the
>> IETF repository.
>>=20
>> Filename:        draft-leiba-3777upd-eligibility
>> Revision:        01
>> Title:           Update to RFC 3777 to Clarify Nominating Committee =
Eligibility of IETF Leadership
>> Creation date:   2012-08-16
>> WG ID:           Individual Submission
>> Number of pages: 7
>> URL:             =
http://www.ietf.org/internet-drafts/draft-leiba-3777upd-eligibility-01.txt=

>> Status:          =
http://datatracker.ietf.org/doc/draft-leiba-3777upd-eligibility
>> Htmlized:        =
http://tools.ietf.org/html/draft-leiba-3777upd-eligibility-01
>> Diff:            =
http://www.ietf.org/rfcdiff?url2=3Ddraft-leiba-3777upd-eligibility-01
>>=20
>> Abstract:
>>  RFC 3777 specifies that "sitting members" of the IAB and IESG "may
>>  not volunteer to serve on the nominating commitee".  Since that
>>  document was written the IAOC was formed, and that body is not
>>  covered by RFC 3777.  There is also uncertainty about whether ex-
>>  officio members and liaisons are included as "sitting members".  =
This
>>  document clarifies those situations.


From Jonne.Soininen@renesasmobile.com  Fri Aug 17 07:23:35 2012
Return-Path: <Jonne.Soininen@renesasmobile.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C15A811E80D5 for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 07:23:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6fRlatyHsVOo for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 07:23:35 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.130]) by ietfa.amsl.com (Postfix) with ESMTP id AF38711E8099 for <ietf@ietf.org>; Fri, 17 Aug 2012 07:23:34 -0700 (PDT)
Received: from [85.158.139.83:37444] by server-6.bemta-5.messagelabs.com id BB/CA-22415-3E35E205; Fri, 17 Aug 2012 14:23:31 +0000
X-Env-Sender: Jonne.Soininen@renesasmobile.com
X-Msg-Ref: server-7.tower-182.messagelabs.com!1345213410!24739364!1
X-Originating-IP: [213.174.82.10]
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26293 invoked from network); 17 Aug 2012 14:23:31 -0000
Received: from renexfe01.roe2.renesasmobile.com (HELO renexfe01.roe2.renesasmobile.com) (213.174.82.10) by server-7.tower-182.messagelabs.com with AES128-SHA encrypted SMTP; 17 Aug 2012 14:23:31 -0000
Received: from RENEXMB02.roe2.renesasmobile.com ([fe80::b101:43e1:dd7b:2fbb]) by renexfe01.roe2.renesasmobile.com ([fe80::ec94:bbb3:68e:a94a%18]) with mapi id 14.02.0283.003; Fri, 17 Aug 2012 17:23:30 +0300
From: <Jonne.Soininen@renesasmobile.com>
To: <ietf@ietf.org>, <iab@iab.org>
Subject: Re: Last Call: Modern Global Standards Paradigm
Thread-Topic: Last Call: Modern Global Standards Paradigm
Thread-Index: AQHNfIPfvd/nLtxIm0i03innDY54aw==
Date: Fri, 17 Aug 2012 14:23:30 +0000
Message-ID: <CC542E38.D4328%jonne.soininen@renesasmobile.com>
In-Reply-To: <8393C34B-3BD4-4453-A315-74D93E971260@gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.22.171]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A991750A4EB9CD4980D24FE02593ACF4@renesasmobile.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 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, 17 Aug 2012 14:23:35 -0000

Hi,

I think very strongly that IAB should sign this document.

Cheers,

Jonne.
--=20
Jonne Soininen
Renesas Mobile


Tel: +358 40 527 4634
E-mail: jonne.soininen@renesasmobile.com





On 8/11/12 1:55 AM, "Bob Hinden" <bob.hinden@gmail.com> wrote:

>I support the IETF and IAB chairs signing document.
>
>Bob
>
>On Aug 10, 2012, at 8:19 AM, IETF Chair wrote:
>
>>=20
>> The IETF Chair and the IAB Chair intend to sign the Affirmation
>> of the Modern Global Standards Paradigm, which can be found
>> here:
>>=20
>>=20
>>http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pd
>>f
>>=20
>> An earlier version was discussed in plenary, and the IAB Chair called
>> for comments on the IETF mail list.  This version includes changes
>> that address those comments.
>>=20
>> Th IETF 84 Administrative plenary minutes have been posted, so that
>> discussion can be reviewed if desired.  The minutes are here:
>>=20
>> http://www.ietf.org/proceedings/84/minutes/minutes-84-iesg-opsplenary
>>=20
>> On 8 August 2012, the IEEE Standards Association Board of Governors
>> approved this version of the document.  The approval process is
>> underway at the W3C as well.
>>=20
>> The IETF Chair and the IAB Chair intend to sign the Affirmation in the
>> next few weeks. Please send strong objections to the iab@iab.org
>> and the ietf@ietf.org mailing lists by 2012-08-24.
>>=20
>> Thank you,
>>  Russ Housley
>>  IETF Chair
>


From lear@cisco.com  Fri Aug 17 07:36:39 2012
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 D6C2021F85B4 for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 07:36:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.522
X-Spam-Level: 
X-Spam-Status: No, score=-110.522 tagged_above=-999 required=5 tests=[AWL=0.077, 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 Lmtd7FbRSvTZ for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 07:36:39 -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 0CBBA21F84A6 for <ietf@ietf.org>; Fri, 17 Aug 2012 07:36:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=684; q=dns/txt; s=iport; t=1345214199; x=1346423799; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=X23ml+YxhXirdPDnKpmg/pMNulTL1Z5D8UW9+0hAWsY=; b=XGbvvnsuKzOe9Qv2xw4qYNoO0eo75MmkuxsI7y3Z9gXOrF83HdpBB4Ny aE5FtsZwqMCmXMW6b2UtrETTOfRkY7DzUSFi/hfqgoupTDW5CEHgybFRK SPm54Bis3VotapshZOfDB3n9xnTYpxAoDKXZDgtKN4ckr8v33kNYbKbtZ s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAFlWLlCQ/khL/2dsb2JhbABFhgG0OYEHgiABAQEEEgEQVAEBEAsYAgIFFgsCAgkDAgECAUUGDQEHAQEeh2uZdo0YkzCBIY9TgRIDlU+OLIFmgmI
X-IronPort-AV: E=Sophos;i="4.77,785,1336348800"; d="scan'208";a="76068033"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 17 Aug 2012 14:36:37 +0000
Received: from dhcp-10-61-104-157.cisco.com (dhcp-10-61-104-157.cisco.com [10.61.104.157]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q7HEabZ6027870 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Aug 2012 14:36:37 GMT
Message-ID: <502E56F4.6090303@cisco.com>
Date: Fri, 17 Aug 2012 16:36:36 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: New Version Notification for draft-leiba-3777upd-eligibility-01.txt
References: <20120816212429.3635.98463.idtracker@ietfa.amsl.com> <CALaySJKfGW-VWTQT1wUOia-=idwq0f-H=zhvFVcTxvqrvSu7pQ@mail.gmail.com> <161D0116-7034-4343-A788-03F10A0F85FC@vigilsec.com>
In-Reply-To: <161D0116-7034-4343-A788-03F10A0F85FC@vigilsec.com>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Barry Leiba <barryleiba@computer.org>, S Moonesamy <sm+ietf@elandsys.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, 17 Aug 2012 14:36:40 -0000

On 8/17/12 4:21 PM, Russ Housley wrote:
> The document says:
>
>  	   o  Bullet 15 is replaced by these two bullets:	
>  		
>  	      15.1.  Members of the Internet Society Board of Trustees and	
>  	           sitting members of the IAB, the IESG, and the IAOC, including	
>  	           members in ex-officio positions, and not including liaisons,	
>  	           may not volunteer to serve as voting members of the	
>  	           nominating committee.
>
> I find "liaison" confusing here.  You mean liaisons to the IESG, IAB, and IAOC.  You do not mean liaisons to the NomCom.
>
Or do you mean liaison managers and representatives as defined in RFC-4052?

Eliot

From john-ietf@jck.com  Fri Aug 17 09:10:04 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5634C21F84A0 for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 09:10:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JKwincjiwJx0 for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 09:10:04 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 16AD521F8491 for <ietf@ietf.org>; Fri, 17 Aug 2012 09:10:04 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1T2P1N-00058U-Tb; Fri, 17 Aug 2012 12:03:37 -0400
Date: Fri, 17 Aug 2012 12:09:49 -0400
From: John C Klensin <john-ietf@jck.com>
To: Russ Housley <housley@vigilsec.com>, Barry Leiba <barryleiba@computer.org>, S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: New Version Notification for	draft-leiba-3777upd-eligibility-01.txt
Message-ID: <13DFE8EF7BE909C8663FA7D4@JcK-HP8200.jck.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Aug 2012 16:10:04 -0000

--On Friday, August 17, 2012 10:05 -0400 Russ Housley
<housley@vigilsec.com> wrote:

> The document says:
> 
>  	   o  Bullet 3, paragraph 1 is replaced by this:	
>  		
>  	         The nominating committee comprises at least a
> Chair, 10 voting	  	         volunteers, 4 liaisons, and an
> advisor.
> 
> The Past Chair is missing.
> 
> The adviser is not required, as implied by the "at least" in
> this sentence.
> 
> Also, if I understand properly, the ISOC BoT is allowed to
> provide a liaison, but they are not required to do so.

Russ,

Isn't the "advisor" the "Past Chair" in the context of that
sentence?   Note that "comprises at least a Chair, 10 voting
volunteers, 3 liaisons, and an advisor" comes straight out of
3777, where it is the first paragraph of item 3 of Section 4.

To avoid making the text ambiguous, confusing, or overly
sensitive to things that might change as other things evolve,
would it to be appropriate to say:

	The nominating committee is comprised of a Chair, ten
	voting volunteers, the immediate past nominating
	committee Chair in an advisory capacity, plus liaisons
	and optional additional advisor(s) as described in
	Section 4 of RFC 3777.

??

best,
   john



From sm@elandsys.com  Fri Aug 17 07:40:51 2012
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D75521F8517 for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 07:40:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.604
X-Spam-Level: 
X-Spam-Status: No, score=-102.604 tagged_above=-999 required=5 tests=[AWL=-0.005, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5RCC8TRxNbbB for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 07:40:50 -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 7E67621F84F9 for <ietf@ietf.org>; Fri, 17 Aug 2012 07:40:50 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.233.188]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q7HEeS3m013998 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Aug 2012 07:40:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1345214440; bh=q9Whk7GKC2xEG4MzvgoW2oJPI3qI7KAN2aeMCCnuwzw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=F65nfMGrywKKDdY/QXDu1YXLauljTlSSKBJ2vxaexrxMwNcCuqOvXCjuWHbPRc8fd nvzYm9ulnCIUSeNikeu6Wyc3ByNrR5P827RceUQlroSZn2NVJpOFj/vUs1+87A2sO7 52fVln4HMyEceVUsytQu5uwlhpdadvoJtrN10AnI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1345214440; i=@elandsys.com; bh=q9Whk7GKC2xEG4MzvgoW2oJPI3qI7KAN2aeMCCnuwzw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=0vb4iA3LExvw/3VAWbHwo303CD1UsBRlAE7YpPbYFik55t6nU2jP6ZI7WfnwHXX9G XKe0HP6Vu4xHSbzn105M1O1vlhEHSoyE4BeBTsQ4spRNx9MAD7bLCFHPHp5eJGLYsh aqrBjRmm7zpxRpi/0Icyq7wLL9QvsmtOdY1WupuI=
Message-Id: <6.2.5.6.2.20120817071954.0af1e470@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 17 Aug 2012 07:40:16 -0700
To: Russ Housley <housley@vigilsec.com>, Barry Leiba <barryleiba@computer.org>, S Moonesamy <sm+ietf@elandsys.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: New Version Notification for draft-leiba-3777upd-eligibility-01.txt
In-Reply-To: <06515DE7-EA23-45EC-9C85-E4003777073F@vigilsec.com>
References: <20120816212429.3635.98463.idtracker@ietfa.amsl.com> <CALaySJKfGW-VWTQT1wUOia-=idwq0f-H=zhvFVcTxvqrvSu7pQ@mail.gmail.com> <06515DE7-EA23-45EC-9C85-E4003777073F@vigilsec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Fri, 17 Aug 2012 11:36:04 -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: Fri, 17 Aug 2012 14:40:51 -0000

At 07:05 17-08-2012, Russ Housley wrote:
>The document says:
>
>            o  Bullet 3, paragraph 1 is replaced by this:
>
>                  The nominating committee comprises at least a 
> Chair, 10 voting
>                  volunteers, 4 liaisons, and an advisor.
>
>The Past Chair is missing.

The Past Chair is mentioned in Bullet 10.  The only change in the 
above text is the increase in liaisons from 3 to 4 to include the 
liaison from the IAOC.

>The adviser is not required, as implied by the "at least" in this sentence.

Bullet 3, paragraph 8 mentions that "the Chair of last year's 
nominating committee serves as an advisor".  The "at least" is for 
the composition of the nominating committee, i.e. it can have more 
than four liaisons (paragraph 3) or an additional advisor (paragraph 2).

>Also, if I understand properly, the ISOC BoT is allowed to provide a 
>liaison, but they are not required to do so.

Yes.

Regards,
S. Moonesamy


From john@jck.com  Fri Aug 17 09:09:24 2012
Return-Path: <john@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F41921F84BF for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 09:09:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PKVKVSlCBXPw for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 09:09:23 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C19A821F84A0 for <ietf@ietf.org>; Fri, 17 Aug 2012 09:09:23 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john@jck.com>) id 1T2P0b-00058B-Nr; Fri, 17 Aug 2012 12:02:49 -0400
Date: Fri, 17 Aug 2012 12:09:01 -0400
From: John C Klensin <john@jck.com>
To: Russ Housley <housley@vigilsec.com>, Barry Leiba <barryleiba@computer.org>, S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: New Version Notification for	draft-leiba-3777upd-eligibility-01.txt
Message-ID: <93CCDEE4ED0AB0B11FD5FF71@JcK-HP8200.jck.com>
In-Reply-To: <06515DE7-EA23-45EC-9C85-E4003777073F@vigilsec.com>
References: <20120816212429.3635.98463.idtracker@ietfa.amsl.com> <CALaySJKfGW-VWTQT1wUOia-=idwq0f-H=zhvFVcTxvqrvSu7pQ@mail.gmail.com> <06515DE7-EA23-45EC-9C85-E4003777073F@vigilsec.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Mailman-Approved-At: Fri, 17 Aug 2012 11:36:04 -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: Fri, 17 Aug 2012 16:09:24 -0000

--On Friday, August 17, 2012 10:05 -0400 Russ Housley
<housley@vigilsec.com> wrote:

> The document says:
> 
>  	   o  Bullet 3, paragraph 1 is replaced by this:	
>  		
>  	         The nominating committee comprises at least a
> Chair, 10 voting	  	         volunteers, 4 liaisons, and an
> advisor.
> 
> The Past Chair is missing.
> 
> The adviser is not required, as implied by the "at least" in
> this sentence.
> 
> Also, if I understand properly, the ISOC BoT is allowed to
> provide a liaison, but they are not required to do so.

Russ,

Isn't the "advisor" the "Past Chair" in the context of that
sentence?   Note that "comprises at least a Chair, 10 voting
volunteers, 3 liaisons, and an advisor" comes straight out of
3777, where it is the first paragraph of item 3 of Section 4.

To avoid making the text ambiguous, confusing, or overly
sensitive to things that might change as other things evolve,
would it to be appropriate to say:

	The nominating committee is comprised of a Chair, ten
	voting volunteers, the immediate past nominating
	committee Chair in an advisory capacity, plus liaisons
	and optional additional advisor(s) as described in
	Section 4 of RFC 3777.

??

best,
   john



From barryleiba@gmail.com  Fri Aug 17 12:05:07 2012
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95A8621F8468 for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 12:05:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.011
X-Spam-Level: 
X-Spam-Status: No, score=-103.011 tagged_above=-999 required=5 tests=[AWL=-0.034, 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 sZCwZaGBG3Rc for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 12:05:07 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0368221F845E for <ietf@ietf.org>; Fri, 17 Aug 2012 12:05:06 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so3754714vcb.31 for <ietf@ietf.org>; Fri, 17 Aug 2012 12:05:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=IzjVbMA/moo7mNcwIr6IhiIeluocUjbUL1dHlAbTHBs=; b=uujj/rSQUZ8ybr3HPSImnupisR6QMrQudn3NkhRuwbpXia6VEotvgpCC0sRFNIgRl2 DYA1YDf4rnUi45Jo9hpZwxd6pkQ7A+9f9uGWN5FBA58mw4ftL4/D++oYtBvcnmxyTxVZ ibsd2af1ml9I3VLuxwS9fRjp/WebNqDunUNWl/xOYD5vVEn/mxjoCAynK7/S4QPscufK 8Ahr16guD20ZhafY5VBe0R8KdGhiK8KLk97T1+a9a5asvw74BnydbTyz41yzvLHuRSQ3 eXNWtw7ixKfoVzpvF6aNkSfaxr9ZcateehsCZYgZxQsfBgNQQWa2pQvQHK0tfW3y68Vb FIOg==
MIME-Version: 1.0
Received: by 10.52.28.169 with SMTP id c9mr2835263vdh.3.1345230306275; Fri, 17 Aug 2012 12:05:06 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.58.58.41 with HTTP; Fri, 17 Aug 2012 12:05:06 -0700 (PDT)
In-Reply-To: <93CCDEE4ED0AB0B11FD5FF71@JcK-HP8200.jck.com>
References: <20120816212429.3635.98463.idtracker@ietfa.amsl.com> <CALaySJKfGW-VWTQT1wUOia-=idwq0f-H=zhvFVcTxvqrvSu7pQ@mail.gmail.com> <06515DE7-EA23-45EC-9C85-E4003777073F@vigilsec.com> <93CCDEE4ED0AB0B11FD5FF71@JcK-HP8200.jck.com>
Date: Fri, 17 Aug 2012 15:05:06 -0400
X-Google-Sender-Auth: jxcd27zYOsM4YQopjXaKiyKj8dk
Message-ID: <CALaySJLjHD4OwnnkwxuW2FVG7mOD9_UtuoJsByO4WPOoE2PF6g@mail.gmail.com>
Subject: Re: New Version Notification for draft-leiba-3777upd-eligibility-01.txt
From: Barry Leiba <barryleiba@computer.org>
To: John C Klensin <john@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: S Moonesamy <sm+ietf@elandsys.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, 17 Aug 2012 19:05:07 -0000

Russ has raised a couple of good points.  I like John's solution to
one of them, and SM has proposed a good solution to the other off
list.  I have the following changes in the pending next version.

I've slightly edited John's text, and Section 4, bullet 3, paragraph 1
will now change to this:

   The nominating committee comprises a Chair, ten voting volunteers,
   the immediate past nominating committee Chair as an advisor, plus
   liaisons and possible additional advisor(s) as described herein.

SM suggests fixing the "liaisons" issue by changing the definition of
"sitting member" instead of by trying to explain it in bullet 15.1.  I
agree that that's cleaner.

The update to Section 2, paragraph 6 will change to this:

sitting member:  A person who is currently serving a term of membership
      in, and having a standing to participate in the decisions of,
      the IESG, the IAB, the IAOC, or the ISOC Board of Trustees.
      Liaisons from other bodies are not sitting members, by this definition.
      (For example, an IESG liaison to the IAB is not a sitting member of
      the IAB, though it may be a sitting member of the IESG.)

The new bullet 15.1 in Section 4 will change to this:

15.1.  Members of the Internet Society Board of Trustees and sitting
        members of the IAB, the IESG, and the IAOC, including members
        in ex-officio positions, may not volunteer to serve as voting members
        of the nominating committee.

--
Barry

From robert@raszuk.net  Fri Aug 17 12:05:58 2012
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 47D4B21F8535 for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 12:05:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b5SDAFBdPQVn for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 12:05:57 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 7CAFF21F84F4 for <ietf@ietf.org>; Fri, 17 Aug 2012 12:05:57 -0700 (PDT)
Received: (qmail 21524 invoked by uid 399); 17 Aug 2012 19:06:57 -0000
Received: from unknown (HELO ?192.168.1.58?) (pbs:robert@raszuk.net@83.13.163.62) by mail1310.opentransfer.com with ESMTPM; 17 Aug 2012 19:06:57 -0000
X-Originating-IP: 83.13.163.62
Message-ID: <502E9614.30409@raszuk.net>
Date: Fri, 17 Aug 2012 21:05:56 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: IETF 92 in Dallas!
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net> <BA2EE8F7-92C8-4F10-B10A-2B6FE4FC954A@gmail.com>
In-Reply-To: <BA2EE8F7-92C8-4F10-B10A-2B6FE4FC954A@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: iaoc@ietf.org, 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: Fri, 17 Aug 2012 19:05:58 -0000

Hi Bob,

Is there any way to broaden the scope of IAOC choice and provide the 
candidate locations which would meet IETF criteria by any IETF member ?

For example once I know the criteria I could check around in Poland to 
see if there is any place which would satisfy the future IETF venue.

I am sure friends from South America would be glad to conduct similar 
local research in their neighborhood. So would others from other 
continents.

Are the criteria for IETF meetings published or is this some sort of top 
secret (for example how much the venue may cost) ?

Could we all contribute via a wiki page ? Could we make the IETF choice 
of location an open process ?

Thx,
R.


> Arturo,
>
> [Reducing the cc: list to just the IETF and IAOC lists]
>
> The IAOC seriously investigated a venue in South America for IETF92,
> but based on the data we collected it did not meet the criteria for
> IETF meetings.  We are continuing to talk with the group that
> suggested the venue and are also looking at other venues in that
> region for future meetings.
>
> We have open meeting slots in 2015-2017.
>
> Bob IAOC Chair

From joelja@bogus.com  Fri Aug 17 12:15:15 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8F9821F8454; Fri, 17 Aug 2012 12:15:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.429
X-Spam-Level: 
X-Spam-Status: No, score=-102.429 tagged_above=-999 required=5 tests=[AWL=0.170, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZOPZXHCMMr-v; Fri, 17 Aug 2012 12:15:15 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 37B1921F844B; Fri, 17 Aug 2012 12:15:15 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q7HJFBsr042741 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 17 Aug 2012 19:15:12 GMT (envelope-from joelja@bogus.com)
Message-ID: <502E9841.8070205@bogus.com>
Date: Fri, 17 Aug 2012 12:15:13 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120808 Thunderbird/15.0
MIME-Version: 1.0
To: robert@raszuk.net
Subject: Re: IETF 92 in Dallas!
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net> <BA2EE8F7-92C8-4F10-B10A-2B6FE4FC954A@gmail.com> <502E9614.30409@raszuk.net>
In-Reply-To: <502E9614.30409@raszuk.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 17 Aug 2012 19:15:12 +0000 (UTC)
Cc: iaoc@ietf.org, Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Aug 2012 19:15:15 -0000

On 8/17/12 12:05 PM, Robert Raszuk wrote:
> Hi Bob,
>
> Is there any way to broaden the scope of IAOC choice and provide the 
> candidate locations which would meet IETF criteria by any IETF member ?
>
> For example once I know the criteria I could check around in Poland to 
> see if there is any place which would satisfy the future IETF venue.
>
> I am sure friends from South America would be glad to conduct similar 
> local research in their neighborhood. So would others from other 
> continents.
>
> Are the criteria for IETF meetings published or is this some sort of 
> top secret (for example how much the venue may cost) ?
>
> Could we all contribute via a wiki page ? Could we make the IETF 
> choice of location an open process ?
Hotel contracts by their nature need to be negotiated under mutual NDA  
unless you want all the vendors in the region to mysteriously arrive at 
the same lower bound.

From robert@raszuk.net  Fri Aug 17 12:20:35 2012
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 7C22721F85E1 for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 12:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 3XJhDvOPWtrA for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 12:20:35 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id CA54521F85A2 for <ietf@ietf.org>; Fri, 17 Aug 2012 12:20:34 -0700 (PDT)
Received: (qmail 5796 invoked by uid 399); 17 Aug 2012 19:21:34 -0000
Received: from unknown (HELO ?192.168.1.58?) (pbs:robert@raszuk.net@83.13.163.62) by mail1310.opentransfer.com with ESMTPM; 17 Aug 2012 19:21:34 -0000
X-Originating-IP: 83.13.163.62
Message-ID: <502E9982.5080909@raszuk.net>
Date: Fri, 17 Aug 2012 21:20:34 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: joel jaeggli <joelja@bogus.com>
Subject: Re: IETF 92 in Dallas!
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net> <BA2EE8F7-92C8-4F10-B10A-2B6FE4FC954A@gmail.com> <502E9614.30409@raszuk.net> <502E9841.8070205@bogus.com>
In-Reply-To: <502E9841.8070205@bogus.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: iaoc@ietf.org, Bob Hinden <bob.hinden@gmail.com>, 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: Fri, 17 Aug 2012 19:20:35 -0000

 > Hotel contracts by their nature need to be negotiated under mutual
 > NDA unless you want all the vendors in the region to mysteriously
 > arrive at the same lower bound.

All hotel rates are wide open and published on IETF web page. It's an 
interesting NDA which permits open disclosure ;-)

Besides hotel is least worry as we do know the IETF rates for the last 
few years and it is quite easy to check with any hotel if they are 
willing to meet those targets or not.

R.


> On 8/17/12 12:05 PM, Robert Raszuk wrote:
>> Hi Bob,
>>
>> Is there any way to broaden the scope of IAOC choice and provide the
>> candidate locations which would meet IETF criteria by any IETF member ?
>>
>> For example once I know the criteria I could check around in Poland to
>> see if there is any place which would satisfy the future IETF venue.
>>
>> I am sure friends from South America would be glad to conduct similar
>> local research in their neighborhood. So would others from other
>> continents.
>>
>> Are the criteria for IETF meetings published or is this some sort of
>> top secret (for example how much the venue may cost) ?
>>
>> Could we all contribute via a wiki page ? Could we make the IETF
>> choice of location an open process ?
> Hotel contracts by their nature need to be negotiated under mutual NDA
> unless you want all the vendors in the region to mysteriously arrive at
> the same lower bound.
>
>


From mstjohns@comcast.net  Fri Aug 17 12:30:40 2012
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14D1D21F8448 for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 12:30:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.308
X-Spam-Level: 
X-Spam-Status: No, score=-101.308 tagged_above=-999 required=5 tests=[AWL=-0.104, 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 CzlnzVSiWETA for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 12:30:39 -0700 (PDT)
Received: from qmta01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [76.96.30.16]) by ietfa.amsl.com (Postfix) with ESMTP id A89C021F8447 for <ietf@ietf.org>; Fri, 17 Aug 2012 12:30:39 -0700 (PDT)
Received: from omta16.emeryville.ca.mail.comcast.net ([76.96.30.72]) by qmta01.emeryville.ca.mail.comcast.net with comcast id nsMX1j01H1ZMdJ4A1vWfV4; Fri, 17 Aug 2012 19:30:39 +0000
Received: from [192.168.1.102] ([68.83.222.237]) by omta16.emeryville.ca.mail.comcast.net with comcast id nvWd1j00D57vnMg8cvWems; Fri, 17 Aug 2012 19:30:39 +0000
References: <20120816212429.3635.98463.idtracker@ietfa.amsl.com> <CALaySJKfGW-VWTQT1wUOia-=idwq0f-H=zhvFVcTxvqrvSu7pQ@mail.gmail.com> <06515DE7-EA23-45EC-9C85-E4003777073F@vigilsec.com> <93CCDEE4ED0AB0B11FD5FF71@JcK-HP8200.jck.com>
In-Reply-To: <93CCDEE4ED0AB0B11FD5FF71@JcK-HP8200.jck.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <DFEFDF3A-7C94-4F79-95EF-C7B4DB6826B9@comcast.net>
X-Mailer: iPad Mail (9B206)
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: New Version Notification for	draft-leiba-3777upd-eligibility-01.txt
Date: Fri, 17 Aug 2012 15:30:37 -0400
To: John C Klensin <john@jck.com>
Cc: Barry Leiba <barryleiba@computer.org>, S Moonesamy <sm+ietf@elandsys.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, 17 Aug 2012 19:30:40 -0000

The advisor is the Immediately previous chair, or a member of the previous n=
oncom designated by that chair if he/she declines to serve or is otherwise u=
navailable.=20

Sent from my iPad

On Aug 17, 2012, at 12:09, John C Klensin <john@jck.com> wrote:

>=20
>=20
> --On Friday, August 17, 2012 10:05 -0400 Russ Housley
> <housley@vigilsec.com> wrote:
>=20
>> The document says:
>>=20
>>       o  Bullet 3, paragraph 1 is replaced by this:   =20
>>       =20
>>             The nominating committee comprises at least a
>> Chair, 10 voting                   volunteers, 4 liaisons, and an
>> advisor.
>>=20
>> The Past Chair is missing.
>>=20
>> The adviser is not required, as implied by the "at least" in
>> this sentence.
>>=20
>> Also, if I understand properly, the ISOC BoT is allowed to
>> provide a liaison, but they are not required to do so.
>=20
> Russ,
>=20
> Isn't the "advisor" the "Past Chair" in the context of that
> sentence?   Note that "comprises at least a Chair, 10 voting
> volunteers, 3 liaisons, and an advisor" comes straight out of
> 3777, where it is the first paragraph of item 3 of Section 4.
>=20
> To avoid making the text ambiguous, confusing, or overly
> sensitive to things that might change as other things evolve,
> would it to be appropriate to say:
>=20
>    The nominating committee is comprised of a Chair, ten
>    voting volunteers, the immediate past nominating
>    committee Chair in an advisory capacity, plus liaisons
>    and optional additional advisor(s) as described in
>    Section 4 of RFC 3777.
>=20
> ??
>=20
> best,
>   john
>=20
>=20

From john-ietf@jck.com  Fri Aug 17 12:34:14 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA63121F844E for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 12:34:14 -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 NTBgogGCOPAZ for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 12:34:14 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 23FCE21F8452 for <ietf@ietf.org>; Fri, 17 Aug 2012 12:34:14 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1T2SCu-0005jO-FS; Fri, 17 Aug 2012 15:27:44 -0400
Date: Fri, 17 Aug 2012 15:33:56 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: New Version Notification for draft-leiba-3777upd-eligibility-01.txt
Message-ID: <F2A3035E068E6FC52574866C@JcK-HP8200.jck.com>
In-Reply-To: <CALaySJLjHD4OwnnkwxuW2FVG7mOD9_UtuoJsByO4WPOoE2PF6g@mail.gmail.com>
References: <20120816212429.3635.98463.idtracker@ietfa.amsl.com> <CALaySJKfGW-VWTQT1wUOia-=idwq0f-H=zhvFVcTxvqrvSu7pQ@mail.gmail.com> <06515DE7-EA23-45EC-9C85-E4003777073F@vigilsec.com> <93CCDEE4ED0AB0B11FD5FF71@JcK-HP8200.jck.com> <CALaySJLjHD4OwnnkwxuW2FVG7mOD9_UtuoJsByO4WPOoE2PF6g@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: S Moonesamy <sm+ietf@elandsys.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, 17 Aug 2012 19:34:14 -0000

--On Friday, August 17, 2012 15:05 -0400 Barry Leiba
<barryleiba@computer.org> wrote:

> Russ has raised a couple of good points.  I like John's
> solution to one of them, and SM has proposed a good solution
> to the other off list.  I have the following changes in the
> pending next version.
> 
> I've slightly edited John's text, and Section 4, bullet 3,
> paragraph 1 will now change to this:
> 
>    The nominating committee comprises a Chair, ten voting
> volunteers,    the immediate past nominating committee Chair
> as an advisor, plus    liaisons and possible additional
> advisor(s) as described herein.

Yes, much better.  I realized after I sent the note that I
intended to say "Section 4 of RFC 3777 as amended by subsequent
documents including this one", but your text is more to the
point.

> SM suggests fixing the "liaisons" issue by changing the
> definition of "sitting member" instead of by trying to explain
> it in bullet 15.1.  I agree that that's cleaner.
> 
> The update to Section 2, paragraph 6 will change to this:
> 
> sitting member:  A person who is currently serving a term of
> membership       in, and having a standing to participate in
> the decisions of,       the IESG, the IAB, the IAOC, or the
> ISOC Board of Trustees.       Liaisons from other bodies are
> not sitting members, by this definition.       (For example,
> an IESG liaison to the IAB is not a sitting member of
> the IAB, though it may be a sitting member of the IESG.)

This is still a tad ambiguous in principle (only).  For example,
it isn't clear whether, by that definition, the IAB Chair is a
sitting member of the IESG (no vote, but excluded from the
Nomcom as a sitting member of the IAB) or whether the IETF Chair
is a sitting member of the IAB (votes, but excluded from the
Nomcom anyway as a sitting member of the IESG).  There are other
such cases, but I believe all of them are, in practice, excluded
by some other rule.

>...

So I think it is ok... and the marginal aesthetics are not worth
worrying about.

    john



From john@jck.com  Fri Aug 17 12:36:48 2012
Return-Path: <john@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F15621F8466 for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 12:36: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 U6xs5Brx+HIb for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 12:36:47 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9A23A21F8464 for <ietf@ietf.org>; Fri, 17 Aug 2012 12:36:47 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john@jck.com>) id 1T2SFQ-0005jl-C8; Fri, 17 Aug 2012 15:30:20 -0400
Date: Fri, 17 Aug 2012 15:36:32 -0400
From: John C Klensin <john@jck.com>
To: Michael StJohns <mstjohns@comcast.net>
Subject: Re: New Version Notification for	draft-leiba-3777upd-eligibility-01.txt
Message-ID: <1D53ED7B7A8C9F54343B35A1@JcK-HP8200.jck.com>
In-Reply-To: <DFEFDF3A-7C94-4F79-95EF-C7B4DB6826B9@comcast.net>
References: <20120816212429.3635.98463.idtracker@ietfa.amsl.com> <CALaySJKfGW-VWTQT1wUOia-=idwq0f-H=zhvFVcTxvqrvSu7pQ@mail.gmail.com> <06515DE7-EA23-45EC-9C85-E4003777073F@vigilsec.com> <93CCDEE4ED0AB0B11FD5FF71@JcK-HP8200.jck.com> <DFEFDF3A-7C94-4F79-95EF-C7B4DB6826B9@comcast.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: Barry Leiba <barryleiba@computer.org>, S Moonesamy <sm+ietf@elandsys.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, 17 Aug 2012 19:36:48 -0000

--On Friday, August 17, 2012 15:30 -0400 Michael StJohns
<mstjohns@comcast.net> wrote:

> The advisor is the Immediately previous chair, or a member of
> the previous noncom designated by that chair if he/she
> declines to serve or is otherwise unavailable. 

That was what I thought until I reread 3777.  It says that the
immediately previous chair serves as an advisor but also says
that the Nomcom can appoint any other advisors it feels like.  I
assume that combination is part of where "at least" came from.

But Barry's new text gets rid of that odd and possibly confusing
way of stating things and is, IMO, a considerable improvement.

    john


From joelja@bogus.com  Fri Aug 17 12:38:49 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D9D021F84DD; Fri, 17 Aug 2012 12:38:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.44
X-Spam-Level: 
X-Spam-Status: No, score=-102.44 tagged_above=-999 required=5 tests=[AWL=0.159, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XVZS-wMn-mp3; Fri, 17 Aug 2012 12:38:49 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id E878621F8494; Fri, 17 Aug 2012 12:38:48 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q7HJckm9042976 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 17 Aug 2012 19:38:46 GMT (envelope-from joelja@bogus.com)
Message-ID: <502E9DC3.2020807@bogus.com>
Date: Fri, 17 Aug 2012 12:38:43 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120808 Thunderbird/15.0
MIME-Version: 1.0
To: robert@raszuk.net
Subject: Re: IETF 92 in Dallas!
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net> <BA2EE8F7-92C8-4F10-B10A-2B6FE4FC954A@gmail.com> <502E9614.30409@raszuk.net> <502E9841.8070205@bogus.com> <502E9982.5080909@raszuk.net>
In-Reply-To: <502E9982.5080909@raszuk.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 17 Aug 2012 19:38:46 +0000 (UTC)
Cc: iaoc@ietf.org, Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Aug 2012 19:38:49 -0000

On 8/17/12 12:20 PM, Robert Raszuk wrote:
>
> > Hotel contracts by their nature need to be negotiated under mutual
> > NDA unless you want all the vendors in the region to mysteriously
> > arrive at the same lower bound.
>
> All hotel rates are wide open and published on IETF web page. It's an 
> interesting NDA which permits open disclosure ;-)
The room rate is...
> Besides hotel is least worry as we do know the IETF rates for the last 
> few years and it is quite easy to check with any hotel if they are 
> willing to meet those targets or not.

A week long meeting involving ~1200 people, dozens meeting rooms, plus 
ancillary meeting, receptions, takeover and operation of a network, av 
support, and catering is a rather different beast.

> R.
>
>
>> On 8/17/12 12:05 PM, Robert Raszuk wrote:
>>> Hi Bob,
>>>
>>> Is there any way to broaden the scope of IAOC choice and provide the
>>> candidate locations which would meet IETF criteria by any IETF member ?
>>>
>>> For example once I know the criteria I could check around in Poland to
>>> see if there is any place which would satisfy the future IETF venue.
>>>
>>> I am sure friends from South America would be glad to conduct similar
>>> local research in their neighborhood. So would others from other
>>> continents.
>>>
>>> Are the criteria for IETF meetings published or is this some sort of
>>> top secret (for example how much the venue may cost) ?
>>>
>>> Could we all contribute via a wiki page ? Could we make the IETF
>>> choice of location an open process ?
>> Hotel contracts by their nature need to be negotiated under mutual NDA
>> unless you want all the vendors in the region to mysteriously arrive at
>> the same lower bound.
>>
>>
>


From melinda.shore@gmail.com  Fri Aug 17 12:54:20 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BE4711E80E1 for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 12:54:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.574
X-Spam-Level: 
X-Spam-Status: No, score=-3.574 tagged_above=-999 required=5 tests=[AWL=0.025,  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 rfDWsjVqIfrk for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 12:54:19 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id B2D0411E80D1 for <ietf@ietf.org>; Fri, 17 Aug 2012 12:54:19 -0700 (PDT)
Received: by pbbrr4 with SMTP id rr4so3910125pbb.31 for <ietf@ietf.org>; Fri, 17 Aug 2012 12:54:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=xhTiSH1R2fH92PVQbTNiaDEvED9wd4ptwa4cQ9bqmfo=; b=jC/CdalLoRaddVPIsDD2xpYS6CYHawsUrg8LnQK8X8lFXVRX2LZ+QE00kmm9VV2BWq UpstdgRe/PI4qTCxamEPeAuWYQsEAl9IuTYLI72bF3yZdj2DnyEO/OYj1HDZH15WxbkT NgBj1rQTp3gVPSxILBk9TGK/eHeSI2Eo00mUBmFrdHhDUNTW8nrLvssI2Z8bj64Rl1JV /Ph1Ud7C9VPq6ilxRT+qhISg5nvtZ+TNJ5x89ymqY8BA/MV1QNJIVZ/6FLgfKDFCCHfk HDbWutzqZm+Kw2xUrGnMFnZTNwwgSfYN3g7YS2/vt4d54INtyodX9Y+z1sgnFYKA93pb jx1w==
Received: by 10.68.129.131 with SMTP id nw3mr14220919pbb.43.1345233259204; Fri, 17 Aug 2012 12:54:19 -0700 (PDT)
Received: from spandex.local (66-230-81-200-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.81.200]) by mx.google.com with ESMTPS id nv6sm5505538pbc.42.2012.08.17.12.54.17 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 17 Aug 2012 12:54:18 -0700 (PDT)
Message-ID: <502EA168.5080502@gmail.com>
Date: Fri, 17 Aug 2012 11:54:16 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Number of interim meetings?
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Aug 2012 19:54:20 -0000

Hi -

Is anyone tracking the number of interim meetings?  It seems as
if the number has been growing quite a bit, although that may be
a function of the number of working groups.  It might be
interesting to try to get a handle on whether or not there's been
some sort of shift in working methods within the organization.

Melinda

From bob.hinden@gmail.com  Fri Aug 17 13:24:06 2012
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 083EB21E804C for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 13:24:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.505
X-Spam-Level: 
X-Spam-Status: No, score=-103.505 tagged_above=-999 required=5 tests=[AWL=0.094, 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 5Ymk0eVO-wRs for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 13:24:05 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 80B6D21E804B for <ietf@ietf.org>; Fri, 17 Aug 2012 13:24:05 -0700 (PDT)
Received: by pbbrr4 with SMTP id rr4so3945389pbb.31 for <ietf@ietf.org>; Fri, 17 Aug 2012 13:24:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=9pBnDCDXSS7uRZI+Mj1CY7XVpUCfufROtSW4sD5eiaM=; b=HifFMW2ZZZCfkvxmOo7KyomJLo+UKdl55VUgtjzcbDuBJKIsfrCrFfK0r/AEmQkLkZ uo+g4TQkup71CuKDEMleFpQIKhOSpRiKfnSJiZzMHrsFZ65O6xz1gBPS1uDZKVwSZZy+ uIvaZMFvnuRqjrwncLL3ElJlifJ+k5xodq56730+9OlWH+G6xqP3MbMG7Ttn6wpxhAEA z6yhkmxjckh9L1g1+WTHiQ9TRdqoOXE7OZ+gXbbe4PpWmBhO9GYAXMLBBCzVnYn67tAQ HULbjVV/8hHg+Q/fyugoWj3n7GXa2TRwYb3WsBo6nENy8T17PDiJBg8WheFJ8Zs8jB6G HmeQ==
Received: by 10.68.217.100 with SMTP id ox4mr14326717pbc.87.1345235044980; Fri, 17 Aug 2012 13:24:04 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPS id uy3sm4908540pbc.29.2012.08.17.13.24.01 (version=SSLv3 cipher=OTHER); Fri, 17 Aug 2012 13:24:04 -0700 (PDT)
Subject: Re: New Version Notification for draft-leiba-3777upd-eligibility-01.txt
Mime-Version: 1.0 (Apple Message framework v1280)
Content-Type: text/plain; charset=iso-8859-1
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <CALaySJKfGW-VWTQT1wUOia-=idwq0f-H=zhvFVcTxvqrvSu7pQ@mail.gmail.com>
Date: Fri, 17 Aug 2012 13:24:00 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <54218C01-B9E3-4E04-AD6E-E3E68CCBC0CF@gmail.com>
References: <20120816212429.3635.98463.idtracker@ietfa.amsl.com> <CALaySJKfGW-VWTQT1wUOia-=idwq0f-H=zhvFVcTxvqrvSu7pQ@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>, sm+ietf@elandsys.com
X-Mailer: Apple Mail (2.1280)
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Aug 2012 20:24:06 -0000

Barry, SM,

Given what started as a simple change has turned into many changes (14 =
changed paragraphs by my count), I am starting to think that doing a =
RFC3777 update document would be a better approach.  Then it would be =
easy to look at a diff from RFC3777 and see all of the changes.

Bob

On Aug 16, 2012, at 2:29 PM, Barry Leiba wrote:

> SM and I have merged our 3777 update proposals, and we have posted the
> merged version.  This is BCCed to the NomCom discussion list; please
> take discussion of this to the main IETF discussion list now.
>=20
> Reminder: the primary purpose of this is to add the IAOC to some of
> the points in RFC 3777, since 3777 pre-dates the formation of the
> IAOC.  Some of the IAOC-related processed are described in RFC 4333,
> so this doesn't cover everything -- but it adds the IAOC to what we
> think is appropriate.  It also incorporates the one Verified erratum
> against 3777, and clarifies that a few other people should not be
> eligible to volunteer for the NomCom -- in practical matters, it has
> little effect, because most of them would not be volunteering anyway.
>=20
> We aim to ask Russ to AD-sponsor this soon.  Further discussion is =
open.
>=20
> Barry (and SM)
>=20
>> A new version of I-D, draft-leiba-3777upd-eligibility-01.txt
>> has been successfully submitted by Barry Leiba and posted to the
>> IETF repository.
>>=20
>> Filename:        draft-leiba-3777upd-eligibility
>> Revision:        01
>> Title:           Update to RFC 3777 to Clarify Nominating Committee =
Eligibility of IETF Leadership
>> Creation date:   2012-08-16
>> WG ID:           Individual Submission
>> Number of pages: 7
>> URL:             =
http://www.ietf.org/internet-drafts/draft-leiba-3777upd-eligibility-01.txt=

>> Status:          =
http://datatracker.ietf.org/doc/draft-leiba-3777upd-eligibility
>> Htmlized:        =
http://tools.ietf.org/html/draft-leiba-3777upd-eligibility-01
>> Diff:            =
http://www.ietf.org/rfcdiff?url2=3Ddraft-leiba-3777upd-eligibility-01
>>=20
>> Abstract:
>>   RFC 3777 specifies that "sitting members" of the IAB and IESG "may
>>   not volunteer to serve on the nominating commitee".  Since that
>>   document was written the IAOC was formed, and that body is not
>>   covered by RFC 3777.  There is also uncertainty about whether ex-
>>   officio members and liaisons are included as "sitting members".  =
This
>>   document clarifies those situations.


From john-ietf@jck.com  Fri Aug 17 13:34:51 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81EB711E80E1; Fri, 17 Aug 2012 13:34:51 -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 ot3taUkCRNmP; Fri, 17 Aug 2012 13:34:51 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E263311E80E0; Fri, 17 Aug 2012 13:34:50 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1T2T9c-0005pm-E6; Fri, 17 Aug 2012 16:28:24 -0400
Date: Fri, 17 Aug 2012 16:34:33 -0400
From: John C Klensin <john-ietf@jck.com>
To: robert@raszuk.net
Subject: Re: IETF 92 in Dallas!
Message-ID: <AEE96A9B18EF64F4B3914E1A@JcK-HP8200.jck.com>
In-Reply-To: <502E9982.5080909@raszuk.net>
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net> <BA2EE8F7-92C8-4F10-B10A-2B6FE4FC954A@gmail.com> <502E9614.30409@raszuk.net> <502E9841.8070205@bogus.com> <502E9982.5080909@raszuk.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: iaoc@ietf.org, Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Aug 2012 20:34:51 -0000

--On Friday, August 17, 2012 21:20 +0200 Robert Raszuk
<robert@raszuk.net> wrote:

> Besides hotel is least worry as we do know the IETF rates for
> the last few years and it is quite easy to check with any
> hotel if they are willing to meet those targets or not.

Actually, we don't (although one can deduce a lot of it from the
IAOC budget and other materials).  What we know is the room
rates in the conference hotels.  We don't know the meeting room
charges (including charges for rooms used by the IESG, IAB,
IAOC, Nomcom, etc., etc.), the catering rates and rules
(including rules about outside food), any charges associated
with Internet service, various facility charges not included in
any of the above, any accommodation arrangements that presumably
lower costs to the IETF such as free or upgraded rooms, and so
on for what I assume is a fairly long list.  Depending on the
hotel and negotiations, some of those are "free" (i.e., bundled
into the room rates for those staying in the hotel), others are
not.

And those of us who have been disturbed by the patterns of room
rates in the primary hotel would probably be very unhappy if
some average or ceiling on those rates were treated as an
acceptable target.

   john


From sm@elandsys.com  Fri Aug 17 13:45:21 2012
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0830811E80DC for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 13:45:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.604
X-Spam-Level: 
X-Spam-Status: No, score=-102.604 tagged_above=-999 required=5 tests=[AWL=-0.005, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MiCdWCceonxd for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 13:45: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 6567511E80D1 for <ietf@ietf.org>; Fri, 17 Aug 2012 13:45:20 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.233.188]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q7HKj0fN002240 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Aug 2012 13:45:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1345236313; bh=cpFl5Y4fnZ8RfhtKLVWDkL4tkiU0jBo+sdjl949IGhI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=GwdL46D42N0bfoC88mBEBmwbVUf0qhTH6PXO4fuZZE11b7q66IhRd0NB6RPYUDRnJ /GldjRkszr65GljEKfuPCTEvgE6WZ/tVHamZl26dXcKDAeTbrm8K9nMbH5f1DCzv2S XaKxunLSYlungS4/zP/rVa+MuSGpcBvQmKPT3ULs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1345236313; i=@elandsys.com; bh=cpFl5Y4fnZ8RfhtKLVWDkL4tkiU0jBo+sdjl949IGhI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=nIayym6K0i81fdYxj2YfxTGkS4I1pa2duiDM5AWNsfqidjLY4jWqwfURM7hrtFQ50 w3keXvnLT8+wQVjLbqQujzTcyF2DcFvUyEjPm/1qTkIfEz8EjAHPW5KOHyOHbB52AF AW/1hAE5RVfsY1tBfxAyDr+IGxPpJ/VKGSBMKAuU=
Message-Id: <6.2.5.6.2.20120817132720.0a2ebe40@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 17 Aug 2012 13:44:07 -0700
To: Bob Hinden <bob.hinden@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: New Version Notification for draft-leiba-3777upd-eligibility-01.txt
In-Reply-To: <54218C01-B9E3-4E04-AD6E-E3E68CCBC0CF@gmail.com>
References: <20120816212429.3635.98463.idtracker@ietfa.amsl.com> <CALaySJKfGW-VWTQT1wUOia-=idwq0f-H=zhvFVcTxvqrvSu7pQ@mail.gmail.com> <54218C01-B9E3-4E04-AD6E-E3E68CCBC0CF@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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: Fri, 17 Aug 2012 20:45:21 -0000

Hi Bob,
At 13:24 17-08-2012, Bob Hinden wrote:
>Given what started as a simple change has turned into many changes 
>(14 changed paragraphs by my count), I am starting to think that 
>doing a RFC3777 update document would be a better approach.  Then it 
>would be easy to look at a diff from RFC3777 and see all of the changes.

I thought about the update when I posted a related draft as minor 
changes look extensive due to the IAOC addition in various parts of 
the text.  I can post a draft which incorporates the changes from 
draft-leiba-3777upd-eligibility-01 to make the diff easier.

Would that help?

Regards,
S. Moonesamy




From bob.hinden@gmail.com  Fri Aug 17 13:53:41 2012
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9E1F11E80E9 for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 13:53:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.506
X-Spam-Level: 
X-Spam-Status: No, score=-103.506 tagged_above=-999 required=5 tests=[AWL=0.093, 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 pT7dgRjg1kCc for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 13:53:41 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 56D8211E80DC for <ietf@ietf.org>; Fri, 17 Aug 2012 13:53:41 -0700 (PDT)
Received: by pbbrr4 with SMTP id rr4so3979545pbb.31 for <ietf@ietf.org>; Fri, 17 Aug 2012 13:53:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=Id3IbE/x+2nt6oKXhRSH4JvIVsCBH4ZcoAidEL/9YvU=; b=ShNQYgvEPl3M3FZvXh/K5Q3PqF5/I2VbUY6x8FNf8VqTCrONSLQY+NcZPoX64QKBMQ 6Y2AHPz7qq75wgVUsI9XZB7mOJ596gmfBbSNgyoTUqNH7EBhnsQEkmBc+dlupYNhv2A5 AyhSyf0wBb2eYLeESHqN+qAPbGaXy8u4XqDQawKC5yCY0MOWW3ENAVximcYHDw+kaPNT koqKL/0B0Kb80NX/oNEoYOaxbRYEwUI1mrwWVzbd/iJdEhL58w0BLauY6lSiJf4+Xq5c o/apUh8EdyCNfa7s+UpCbqJHuM5bC60pXxUMmPynsTUYsyvrM94H2yk351yuTC5X6xJp Qq4w==
Received: by 10.68.197.198 with SMTP id iw6mr14463044pbc.78.1345236820977; Fri, 17 Aug 2012 13:53:40 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPS id qx8sm5579140pbc.63.2012.08.17.13.53.38 (version=SSLv3 cipher=OTHER); Fri, 17 Aug 2012 13:53:39 -0700 (PDT)
Subject: Re: New Version Notification for draft-leiba-3777upd-eligibility-01.txt
Mime-Version: 1.0 (Apple Message framework v1280)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <6.2.5.6.2.20120817132720.0a2ebe40@elandnews.com>
Date: Fri, 17 Aug 2012 13:53:35 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <0FB15295-6265-417F-A7A8-59A0D7C90177@gmail.com>
References: <20120816212429.3635.98463.idtracker@ietfa.amsl.com> <CALaySJKfGW-VWTQT1wUOia-=idwq0f-H=zhvFVcTxvqrvSu7pQ@mail.gmail.com> <54218C01-B9E3-4E04-AD6E-E3E68CCBC0CF@gmail.com> <6.2.5.6.2.20120817132720.0a2ebe40@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1280)
Cc: Barry Leiba <barryleiba@computer.org>, Bob Hinden <bob.hinden@gmail.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Aug 2012 20:53:41 -0000

SM,

On Aug 17, 2012, at 1:44 PM, S Moonesamy wrote:

> Hi Bob,
> At 13:24 17-08-2012, Bob Hinden wrote:
>> Given what started as a simple change has turned into many changes =
(14 changed paragraphs by my count), I am starting to think that doing a =
RFC3777 update document would be a better approach.  Then it would be =
easy to look at a diff from RFC3777 and see all of the changes.
>=20
> I thought about the update when I posted a related draft as minor =
changes look extensive due to the IAOC addition in various parts of the =
text.  I can post a draft which incorporates the changes from =
draft-leiba-3777upd-eligibility-01 to make the diff easier.
>=20
> Would that help?


Yes, it would help for reviewing this draft, but it will still make it =
complicated for future noncom's to understand the rules.  A single =
document would be easier to understand.

I suppose an alternative would be to file an errata on RFC3777 that says =
something like add "IAOC" to everywhere in the document it says IESG, =
IAB, and ISOC Board of Trustees, and leave the specific changes as an =
excise to the reader.  :-) =20

Bob



From sm@elandsys.com  Fri Aug 17 14:18:08 2012
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 040F511E80D1 for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 14:18:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.604
X-Spam-Level: 
X-Spam-Status: No, score=-102.604 tagged_above=-999 required=5 tests=[AWL=-0.005, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DBHp+Kv1GHZn for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 14:18:07 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6743D11E80EA for <ietf@ietf.org>; Fri, 17 Aug 2012 14:18:07 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.232.237]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q7HLHkGI028978 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Aug 2012 14:17:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1345238278; bh=Be1QITIqZUClSUzuNu7CXsIi2qTJCYTej9tzy8hEsvw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=FV+zS4SsBhBTqa5RRj/KyJg0Guzm5Zv+r1nDbhDYWsS/ZoHojR0glfM+EeRu+nwbg b3hD0QTceEHAVP9m2lqxqSNAqClj7YfgENDQjWvJ890MlDJgitIaSyapH523AVoEoD cZr+aIqacsVzOLdqR07NQ9wcoYxUgp/0gmshwCWw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1345238278; i=@elandsys.com; bh=Be1QITIqZUClSUzuNu7CXsIi2qTJCYTej9tzy8hEsvw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=n/NGBdZZf45Qt2n/Wn73BSGB8czTeASd1R7rdO3V+Nj2Xlp8v7dR9dcjkStCw6biq +NBoa0Ho2UdygtGaZYYV5rheSp/N0CFqIspVboOGZhKdy4IJH/Kv5cvTlm9sQh1PiJ 6wQruR/Y2+jf2vakdacU9mX8YlvF+T03kY4LgbFw=
Message-Id: <6.2.5.6.2.20120817140030.09d51f60@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 17 Aug 2012 14:15:26 -0700
To: Bob Hinden <bob.hinden@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: New Version Notification for draft-leiba-3777upd-eligibility-01.txt
In-Reply-To: <0FB15295-6265-417F-A7A8-59A0D7C90177@gmail.com>
References: <20120816212429.3635.98463.idtracker@ietfa.amsl.com> <CALaySJKfGW-VWTQT1wUOia-=idwq0f-H=zhvFVcTxvqrvSu7pQ@mail.gmail.com> <54218C01-B9E3-4E04-AD6E-E3E68CCBC0CF@gmail.com> <6.2.5.6.2.20120817132720.0a2ebe40@elandnews.com> <0FB15295-6265-417F-A7A8-59A0D7C90177@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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: Fri, 17 Aug 2012 21:18:08 -0000

Hi Bob,
At 13:53 17-08-2012, Bob Hinden wrote:
>Yes, it would help for reviewing this draft, but it will still make 
>it complicated for future noncom's to understand the rules.  A 
>single document would be easier to understand.

Ok.  I'll post a draft.

>I suppose an alternative would be to file an errata on RFC3777 that 
>says something like add "IAOC" to everywhere in the document it says 
>IESG, IAB, and ISOC Board of Trustees, and leave the specific 
>changes as an excise to the reader.  :-)

Yes. :-)  It's a little more than though as there is a change to 
Bullet 15.  There's the question of what to do about RFC 5633 and RFC 5680.

Regards,
S. Moonesamy 


From housley@vigilsec.com  Fri Aug 17 14:33:47 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7ACD21E8045 for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 14:33:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.389
X-Spam-Level: 
X-Spam-Status: No, score=-102.389 tagged_above=-999 required=5 tests=[AWL=0.210, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EHfMlhBuB34z for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 14:33:47 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 4974421F843C for <ietf@ietf.org>; Fri, 17 Aug 2012 14:33:47 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id D2C1F9A471B; Fri, 17 Aug 2012 17:33:53 -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 sAhx9tEEmRhc; Fri, 17 Aug 2012 17:33:43 -0400 (EDT)
Received: from [192.168.1.3] (96-37-2-47.dhcp.sffl.va.charter.com [96.37.2.47]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id BA9459A470F; Fri, 17 Aug 2012 17:33:51 -0400 (EDT)
Subject: Re: New Version Notification for	draft-leiba-3777upd-eligibility-01.txt
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <93CCDEE4ED0AB0B11FD5FF71@JcK-HP8200.jck.com>
Date: Fri, 17 Aug 2012 17:33:44 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <895C8A21-BD9C-4A06-B64D-45E29D8C406D@vigilsec.com>
References: <20120816212429.3635.98463.idtracker@ietfa.amsl.com> <CALaySJKfGW-VWTQT1wUOia-=idwq0f-H=zhvFVcTxvqrvSu7pQ@mail.gmail.com> <06515DE7-EA23-45EC-9C85-E4003777073F@vigilsec.com> <93CCDEE4ED0AB0B11FD5FF71@JcK-HP8200.jck.com>
To: John C Klensin <john@jck.com>
X-Mailer: Apple Mail (2.1084)
Cc: Barry Leiba <barryleiba@computer.org>, S Moonesamy <sm+ietf@elandsys.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, 17 Aug 2012 21:33:48 -0000

>> The document says:
>> 
>> 	   o  Bullet 3, paragraph 1 is replaced by this:	
>> 		
>> 	         The nominating committee comprises at least a
>> Chair, 10 voting	  	         volunteers, 4 liaisons, and an
>> advisor.
>> 
>> The Past Chair is missing.
>> 
>> The adviser is not required, as implied by the "at least" in
>> this sentence.
>> 
>> Also, if I understand properly, the ISOC BoT is allowed to
>> provide a liaison, but they are not required to do so.
> 
> Russ,
> 
> Isn't the "advisor" the "Past Chair" in the context of that
> sentence?   Note that "comprises at least a Chair, 10 voting
> volunteers, 3 liaisons, and an advisor" comes straight out of
> 3777, where it is the first paragraph of item 3 of Section 4.
> 
> To avoid making the text ambiguous, confusing, or overly
> sensitive to things that might change as other things evolve,
> would it to be appropriate to say:
> 
> 	The nominating committee is comprised of a Chair, ten
> 	voting volunteers, the immediate past nominating
> 	committee Chair in an advisory capacity, plus liaisons
> 	and optional additional advisor(s) as described in
> 	Section 4 of RFC 3777.

That is an improvement from my perspective.

Russ


From john-ietf@jck.com  Fri Aug 17 15:40:43 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8855D11E80D7; Fri, 17 Aug 2012 15:40:43 -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 ozY1qqtzJtgX; Fri, 17 Aug 2012 15:40:43 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 043A711E80D1; Fri, 17 Aug 2012 15:40:42 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1T2V7Q-00061g-0o; Fri, 17 Aug 2012 18:34:16 -0400
Date: Fri, 17 Aug 2012 18:40:28 -0400
From: John C Klensin <john-ietf@jck.com>
To: Dave Crocker <dcrocker@gmail.com>
Subject: Re: [IAOC] IETF 92 in Dallas!
Message-ID: <F3913A8723760321C6ED6601@JcK-HP8200.jck.com>
In-Reply-To: <502EAD34.8090605@gmail.com>
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net> <BA2EE8F7-92C8-4F10-B10A-2B6FE4FC954A@gmail.com> <502E9614.30409@raszuk.net> <502E9841.8070205@bogus.com> <502E9982.5080909@raszuk.net> <AEE96A9B18EF64F4B3914E1A@JcK-HP8200.jck.com> <502EAD34.8090605@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: iaoc@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Aug 2012 22:40:43 -0000

--On Friday, August 17, 2012 16:44 -0400 Dave Crocker
<dcrocker@gmail.com> wrote:

>> --On Friday, August 17, 2012 21:20 +0200 Robert Raszuk
>> <robert@raszuk.net> wrote:
>> 
>>> Besides hotel is least worry as we do know the IETF rates for
>>> the last few years and it is quite easy to check with any
>>> hotel if they are willing to meet those targets or not.
>> 
>> Actually, we don't 
> 
> 
> except for:
> 
>    http://iaoc.ietf.org/mfstatement_detail.html
> 
> might be enough detail for the concern being raised here.

I would hope so (and thanks for the link).  My more general
concern is/was associated with the comment about "targets" and
getting into a situation in which some members of the community
start doing their own negotiating and site visits and then get
upset if the IAOC says "no" to whatever they propose.  Certainly
there is not enough information in those reports to turn this
into a process in which the IAOC decisions become mechanical.

best,
   john






From mstjohns@comcast.net  Fri Aug 17 16:44:35 2012
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5776B21F8495 for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 16:44:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.281
X-Spam-Level: 
X-Spam-Status: No, score=-101.281 tagged_above=-999 required=5 tests=[AWL=-0.079, 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 RCFl9Ki5pw3L for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 16:44:34 -0700 (PDT)
Received: from qmta03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [76.96.30.32]) by ietfa.amsl.com (Postfix) with ESMTP id 8A69F21F8494 for <ietf@ietf.org>; Fri, 17 Aug 2012 16:44:34 -0700 (PDT)
Received: from omta24.emeryville.ca.mail.comcast.net ([76.96.30.92]) by qmta03.emeryville.ca.mail.comcast.net with comcast id nqKJ1j04X1zF43QA3zkanf; Fri, 17 Aug 2012 23:44:34 +0000
Received: from [192.168.1.102] ([68.83.222.237]) by omta24.emeryville.ca.mail.comcast.net with comcast id nzkY1j00A57vnMg8kzkZpr; Fri, 17 Aug 2012 23:44:34 +0000
References: <20120816212429.3635.98463.idtracker@ietfa.amsl.com> <CALaySJKfGW-VWTQT1wUOia-=idwq0f-H=zhvFVcTxvqrvSu7pQ@mail.gmail.com> <06515DE7-EA23-45EC-9C85-E4003777073F@vigilsec.com> <93CCDEE4ED0AB0B11FD5FF71@JcK-HP8200.jck.com> <DFEFDF3A-7C94-4F79-95EF-C7B4DB6826B9@comcast.net> <1D53ED7B7A8C9F54343B35A1@JcK-HP8200.jck.com>
In-Reply-To: <1D53ED7B7A8C9F54343B35A1@JcK-HP8200.jck.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary=Apple-Mail-87D84BC7-12BF-482A-B804-2535B6DF8E5B
Message-Id: <B6AC8192-A117-4DA5-AE0D-EBA2EC594E2F@comcast.net>
X-Mailer: iPad Mail (9B206)
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: New Version Notification for	draft-leiba-3777upd-eligibility-01.txt
Date: Fri, 17 Aug 2012 19:44:34 -0400
To: John C Klensin <john@jck.com>
Cc: Barry Leiba <barryleiba@computer.org>, S Moonesamy <sm+ietf@elandsys.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, 17 Aug 2012 23:44:35 -0000

--Apple-Mail-87D84BC7-12BF-482A-B804-2535B6DF8E5B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Read section 10, 3rd paragraph of RFC3777. =20

> The prior year's Chair may select a designee from a pool composed of the v=
oting
> volunteers of the prior year's committee and all prior Chairs if the Chair=
 is unavailable.
> If the prior year's Chair is unavailable or is unable or unwilling to make=
 such a
> designation in a timely fashion, the Chair of the current year's committee=
 may select a
> designee in consultation with the Internet Society President.
So it's actually, the prior chair (first choice), any member of the prior co=
mmittee, or=20
any other prior chair.

Mike=20

Sent from my iPad

On Aug 17, 2012, at 15:36, John C Klensin <john@jck.com> wrote:

>=20
>=20
> --On Friday, August 17, 2012 15:30 -0400 Michael StJohns
> <mstjohns@comcast.net> wrote:
>=20
>> The advisor is the Immediately previous chair, or a member of
>> the previous noncom designated by that chair if he/she
>> declines to serve or is otherwise unavailable.=20
>=20
> That was what I thought until I reread 3777.  It says that the
> immediately previous chair serves as an advisor but also says
> that the Nomcom can appoint any other advisors it feels like.  I
> assume that combination is part of where "at least" came from.
>=20
> But Barry's new text gets rid of that odd and possibly confusing
> way of stating things and is, IMO, a considerable improvement.
>=20
>    john
>=20

--Apple-Mail-87D84BC7-12BF-482A-B804-2535B6DF8E5B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head></head><body bgcolor=3D"#FFFFFF"><div>Read section 10, 3rd parag=
raph of RFC3777. &nbsp;</div><div><br></div><div><blockquote type=3D"cite"><=
pre style=3D"word-wrap: break-word; "><font class=3D"Apple-style-span" color=
=3D"#000000" face=3D"Helvetica"><span class=3D"Apple-style-span" style=3D"wh=
ite-space: normal;"> The prior year's Chair may select a designee from a poo=
l composed
       of the voting</span></font></pre></blockquote><blockquote type=3D"cit=
e"><pre style=3D"word-wrap: break-word; "><font class=3D"Apple-style-span" c=
olor=3D"#000000" face=3D"Helvetica"><span class=3D"Apple-style-span" style=3D=
"white-space: normal;">volunteers of the prior year's committee and all
       prior Chairs if the Chair is unavailable.</span></font></pre></blockq=
uote><blockquote type=3D"cite"><pre style=3D"word-wrap: break-word; "><font c=
lass=3D"Apple-style-span" color=3D"#000000" face=3D"Helvetica"><span class=3D=
"Apple-style-span" style=3D"white-space: normal;">If the prior year's
       Chair is unavailable or is unable or unwilling to make such a</span><=
/font></pre></blockquote><blockquote type=3D"cite"><pre style=3D"word-wrap: b=
reak-word; "><font class=3D"Apple-style-span" color=3D"#000000" face=3D"Helv=
etica"><span class=3D"Apple-style-span" style=3D"white-space: normal;">desig=
nation in a timely fashion, the Chair of the current year's
       committee may select a</span></font></pre></blockquote><blockquote ty=
pe=3D"cite"><pre style=3D"word-wrap: break-word; "><font class=3D"Apple-styl=
e-span" color=3D"#000000" face=3D"Helvetica"><span class=3D"Apple-style-span=
" style=3D"white-space: normal;">designee in consultation with the Internet
       Society President.</span></font></pre></blockquote>So it's actually, t=
he prior chair (first choice), any member of the prior committee, or&nbsp;</=
div><div><span class=3D"Apple-style-span" style=3D"-webkit-tap-highlight-col=
or: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 19=
2, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230=
469); ">any other prior chair.</span><br></div><div><span class=3D"Apple-sty=
le-span" style=3D"-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -=
webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-compos=
ition-frame-color: rgba(77, 128, 180, 0.230469); "><br></span></div><div><sp=
an class=3D"Apple-style-span" style=3D"-webkit-tap-highlight-color: rgba(26,=
 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.23=
0469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">Mike=
&nbsp;</span></div><div><span class=3D"Apple-style-span" style=3D"-webkit-ta=
p-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-colo=
r: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 1=
28, 180, 0.230469); "><br></span></div><div>Sent from my iPad</div><div><br>=
On Aug 17, 2012, at 15:36, John C Klensin &lt;<a href=3D"mailto:john@jck.com=
">john@jck.com</a>&gt; wrote:<br><br></div><div></div><blockquote type=3D"ci=
te"><div><span></span><br><span></span><br><span>--On Friday, August 17, 201=
2 15:30 -0400 Michael StJohns</span><br><span>&lt;<a href=3D"mailto:mstjohns=
@comcast.net">mstjohns@comcast.net</a>&gt; wrote:</span><br><span></span><br=
><blockquote type=3D"cite"><span>The advisor is the Immediately previous cha=
ir, or a member of</span><br></blockquote><blockquote type=3D"cite"><span>th=
e previous noncom designated by that chair if he/she</span><br></blockquote>=
<blockquote type=3D"cite"><span>declines to serve or is otherwise unavailabl=
e. </span><br></blockquote><span></span><br><span>That was what I thought un=
til I reread 3777. &nbsp;It says that the</span><br><span>immediately previo=
us chair serves as an advisor but also says</span><br><span>that the Nomcom c=
an appoint any other advisors it feels like. &nbsp;I</span><br><span>assume t=
hat combination is part of where "at least" came from.</span><br><span></spa=
n><br><span>But Barry's new text gets rid of that odd and possibly confusing=
</span><br><span>way of stating things and is, IMO, a considerable improveme=
nt.</span><br><span></span><br><span> &nbsp;&nbsp;&nbsp;john</span><br><span=
></span><br></div></blockquote></body></html>=

--Apple-Mail-87D84BC7-12BF-482A-B804-2535B6DF8E5B--

From dwm@xpasc.com  Fri Aug 17 16:58:05 2012
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAF6621F8435; Fri, 17 Aug 2012 16:58:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.261
X-Spam-Level: 
X-Spam-Status: No, score=-5.261 tagged_above=-999 required=5 tests=[AWL=-3.954, 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 XqP9CoIMEd7d; Fri, 17 Aug 2012 16:58:05 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 6FA0D21F8432; Fri, 17 Aug 2012 16:58:05 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id DBA7440779; Fri, 17 Aug 2012 23:58:04 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id q7HNw4Ix031631; Fri, 17 Aug 2012 16:58:04 -0700
Date: Fri, 17 Aug 2012 16:58:04 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
Subject: Re: IETF 92 in Dallas! ... vetting of alternatives
In-Reply-To: <502E9DC3.2020807@bogus.com>
Message-ID: <alpine.LRH.2.01.1208171513050.25946@egate.xpasc.com>
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net> <BA2EE8F7-92C8-4F10-B10A-2B6FE4FC954A@gmail.com> <502E9614.30409@raszuk.net> <502E9841.8070205@bogus.com> <502E9982.5080909@raszuk.net> <502E9DC3.2020807@bogus.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.1+13-gbab1945
X-AV-Type: clean
X-AV-Accuracy: exact
Cc: iaoc@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org, iaoc@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, 17 Aug 2012 23:58:05 -0000

On Fri, 17 Aug 2012, joel jaeggli wrote:

> On 8/17/12 12:20 PM, Robert Raszuk wrote:
> > 
> > > Hotel contracts by their nature need to be negotiated under mutual
> > > NDA unless you want all the vendors in the region to mysteriously
> > > arrive at the same lower bound.
> > 
> > All hotel rates are wide open and published on IETF web page. It's an
> > interesting NDA which permits open disclosure ;-)
> The room rate is...
> > Besides hotel is least worry as we do know the IETF rates for the last few
> > years and it is quite easy to check with any hotel if they are willing to
> > meet those targets or not.
> 
> A week long meeting involving ~1200 people, dozens meeting rooms, plus
> ancillary meeting, receptions, takeover and operation of a network, av
> support, and catering is a rather different beast.

Since folks contributing as Robert has suggested can't enter into
actual negotiations, that is probably one factor best left to a
formal inquiry. But it seems to me that the question for which
local advocates could gather information is the facility qualification
in terms of the requirments. I'd guess that IAOC creates a strawman
requirement for the meeting which will list criteria like sizes and
types of meeting facilities.

That strawman reveals a requirment, not any NDA covered negotiation.
For this discussion, it should include an analysis of travel time
and costs from some common major hubs in NA, Europe, SA, Asia as
I assume this data would be part of the IAOC decision process
and it should help if the local advocates do the travel
research. 

From michal@krsek.cz  Sat Aug 18 00:54:21 2012
Return-Path: <michal@krsek.cz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DA5821F8570 for <ietf@ietfa.amsl.com>; Sat, 18 Aug 2012 00:54:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.552
X-Spam-Level: 
X-Spam-Status: No, score=-0.552 tagged_above=-999 required=5 tests=[AWL=0.698,  BAYES_00=-2.599, HELO_EQ_CZ=0.445, HOST_EQ_CZ=0.904]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IclpCpQMvGtA for <ietf@ietfa.amsl.com>; Sat, 18 Aug 2012 00:54:20 -0700 (PDT)
Received: from io.pinknet.cz (io.pinknet.cz [217.31.57.96]) by ietfa.amsl.com (Postfix) with ESMTP id BCA1221F84D9 for <ietf@ietf.org>; Sat, 18 Aug 2012 00:54:20 -0700 (PDT)
Received: from [192.168.100.102] (ip-78-45-177-68.net.upcbroadband.cz [78.45.177.68]) by io.pinknet.cz (Postfix) with ESMTP id 773FE23B123 for <ietf@ietf.org>; Sat, 18 Aug 2012 10:13:14 +0200 (CEST)
Message-ID: <502F4A2A.8090005@krsek.cz>
Date: Sat, 18 Aug 2012 09:54:18 +0200
From: Michal Krsek <michal@krsek.cz>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF 92 in Dallas!
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net> <BA2EE8F7-92C8-4F10-B10A-2B6FE4FC954A@gmail.com> <502E9614.30409@raszuk.net> <502E9841.8070205@bogus.com> <502E9982.5080909@raszuk.net>
In-Reply-To: <502E9982.5080909@raszuk.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Aug 2012 07:54:21 -0000

Hi,

> > Hotel contracts by their nature need to be negotiated under mutual
> > NDA unless you want all the vendors in the region to mysteriously
> > arrive at the same lower bound.
>
> All hotel rates are wide open and published on IETF web page. It's an 
> interesting NDA which permits open disclosure ;-)
>
> Besides hotel is least worry as we do know the IETF rates for the last 
> few years and it is quite easy to check with any hotel if they are 
> willing to meet those targets or not.

Price for attendee rooms is only a small part of the contract.

                             MK


From mstjohns@comcast.net  Sat Aug 18 15:19:41 2012
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 876B521F84E4 for <ietf@ietfa.amsl.com>; Sat, 18 Aug 2012 15:19:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.963
X-Spam-Level: 
X-Spam-Status: No, score=-101.963 tagged_above=-999 required=5 tests=[AWL=0.635, 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 6oa+J9ho60AE for <ietf@ietfa.amsl.com>; Sat, 18 Aug 2012 15:19:40 -0700 (PDT)
Received: from qmta01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [76.96.30.16]) by ietfa.amsl.com (Postfix) with ESMTP id E5A0E21F84E1 for <ietf@ietf.org>; Sat, 18 Aug 2012 15:19:40 -0700 (PDT)
Received: from omta23.emeryville.ca.mail.comcast.net ([76.96.30.90]) by qmta01.emeryville.ca.mail.comcast.net with comcast id oMzs1j0021wfjNsA1NKg0H; Sat, 18 Aug 2012 22:19:40 +0000
Received: from Mike-PC3.comcast.net ([68.83.222.237]) by omta23.emeryville.ca.mail.comcast.net with comcast id oNKe1j00557vnMg8jNKfCl; Sat, 18 Aug 2012 22:19:40 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sat, 18 Aug 2012 18:19:35 -0400
To: John C Klensin <john@jck.com>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: New Version Notification for	draft-leiba-3777upd-eligibility-01.txt
In-Reply-To: <B6AC8192-A117-4DA5-AE0D-EBA2EC594E2F@comcast.net>
References: <20120816212429.3635.98463.idtracker@ietfa.amsl.com> <CALaySJKfGW-VWTQT1wUOia-=idwq0f-H=zhvFVcTxvqrvSu7pQ@mail.gmail.com> <06515DE7-EA23-45EC-9C85-E4003777073F@vigilsec.com> <93CCDEE4ED0AB0B11FD5FF71@JcK-HP8200.jck.com> <DFEFDF3A-7C94-4F79-95EF-C7B4DB6826B9@comcast.net> <1D53ED7B7A8C9F54343B35A1@JcK-HP8200.jck.com> <B6AC8192-A117-4DA5-AE0D-EBA2EC594E2F@comcast.net>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_159038573==.ALT"
Message-Id: <20120818221940.E5A0E21F84E1@ietfa.amsl.com>
Cc: Barry Leiba <barryleiba@computer.org>, S Moonesamy <sm+ietf@elandsys.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, 18 Aug 2012 22:19:41 -0000

--=====================_159038573==.ALT
Content-Type: text/plain; charset="us-ascii"

Below....

At 07:44 PM 8/17/2012, Michael StJohns wrote:
>Read section 10, 3rd paragraph of RFC3777.  
>
>>
>> The prior year's Chair may select a designee from a pool composed
>>       of the voting
>>volunteers of the prior year's committee and all
>>       prior Chairs if the Chair is unavailable.
>>If the prior year's
>>       Chair is unavailable or is unable or unwilling to make such a
>>designation in a timely fashion, the Chair of the current year's
>>       committee may select a
>>designee in consultation with the Internet
>>       Society President.
>So it's actually, the prior chair (first choice), any member of the prior committee, or 
>any other prior chair.
>
>Mike 


Sorry - while I love the iPad, at times its painful to edit things correctly.

The original reference to "advisor" in the collection of members in the original text is as above - the past chair or the chair's alternate selected as above.

The other reference to the "any other advisors" you mention below is elsewhere in 3777.  So we were both fondling different parts of the same elephant....

With respect to the current edit of the text I'd make one more change to make this clear:

>        The nominating committee is comprised of a Chair, ten
>        voting volunteers, the immediate past nominating
>        committee Chair 

[or their alternate]

> in an advisory capacity, plus liaisons
>        and optional additional advisor(s) as described in
>        Section 4 of RFC 3777.

Mike



>On Aug 17, 2012, at 15:36, John C Klensin <<mailto:john@jck.com>john@jck.com> wrote:
>
>>
>>
>>--On Friday, August 17, 2012 15:30 -0400 Michael StJohns
>><<mailto:mstjohns@comcast.net>mstjohns@comcast.net> wrote:
>>
>>>The advisor is the Immediately previous chair, or a member of
>>>the previous noncom designated by that chair if he/she
>>>declines to serve or is otherwise unavailable. 
>>
>>That was what I thought until I reread 3777.  It says that the
>>immediately previous chair serves as an advisor but also says
>>that the Nomcom can appoint any other advisors it feels like.  I
>>assume that combination is part of where "at least" came from.
>>
>>But Barry's new text gets rid of that odd and possibly confusing
>>way of stating things and is, IMO, a considerable improvement.
>>
>>   john


--=====================_159038573==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
Below....<br><br>
At 07:44 PM 8/17/2012, Michael StJohns wrote:<br>
<blockquote type=cite class=cite cite="">Read section 10, 3rd paragraph
of RFC3777.&nbsp; <br><br>
<blockquote type=cite class=cite cite=""><br>
<pre><font face="Helvetica, Helvetica">&nbsp;The prior year's Chair may
select a designee from a pool composed
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of the
voting</font></pre><font face="Courier New, Courier"></font><br>
<pre><font face="Helvetica, Helvetica">volunteers of the prior year's
committee and all
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; prior Chairs if the Chair is
unavailable.</font></pre><font face="Courier New, Courier"></font><br>
<pre><font face="Helvetica, Helvetica">If the prior year's
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Chair is unavailable or is unable or
unwilling to make such
a</font></pre><font face="Courier New, Courier"></font><br>
<pre><font face="Helvetica, Helvetica">designation in a timely fashion,
the Chair of the current year's
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; committee may select
a</font></pre><font face="Courier New, Courier"></font><br>
<pre><font face="Helvetica, Helvetica">designee in consultation with the
Internet
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Society
President.</font></pre><font face="Courier New, Courier"></font>
</blockquote>So it's actually, the prior chair (first choice), any member
of the prior committee, or <br>
any other prior chair.<br><br>
Mike </blockquote><br><br>
Sorry - while I love the iPad, at times its painful to edit things
correctly.<br><br>
The original reference to &quot;advisor&quot; in the collection of
members in the original text is as above - the past chair or the chair's
alternate selected as above.<br><br>
The other reference to the &quot;any other advisors&quot; you mention
below is elsewhere in 3777.&nbsp; So we were both fondling different
parts of the same elephant....<br><br>
With respect to the current edit of the text I'd make one more change to
make this clear:<br><br>
<blockquote type=cite class=cite cite=""><x-tab>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>The nominating
committee is comprised of a Chair, ten<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>voting
volunteers, the immediate past nominating<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>committee
Chair </blockquote><br>
[or their alternate]<br><br>
<blockquote type=cite class=cite cite="">&nbsp;in an advisory capacity,
plus liaisons<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>and
optional additional advisor(s) as described in<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Section 4
of RFC 3777.</blockquote><br>
Mike<br><br>
<br><br>
<blockquote type=cite class=cite cite="">On Aug 17, 2012, at 15:36, John
C Klensin &lt;<a href="mailto:john@jck.com">john@jck.com</a>&gt;
wrote:<br><br>
<blockquote type=cite class=cite cite=""><br><br>
--On Friday, August 17, 2012 15:30 -0400 Michael StJohns<br>
&lt;<a href="mailto:mstjohns@comcast.net">mstjohns@comcast.net</a>&gt;
wrote:<br><br>
<blockquote type=cite class=cite cite="">The advisor is the Immediately
previous chair, or a member of<br>
the previous noncom designated by that chair if he/she<br>
declines to serve or is otherwise unavailable. </blockquote><br>
That was what I thought until I reread 3777.&nbsp; It says that the<br>
immediately previous chair serves as an advisor but also says<br>
that the Nomcom can appoint any other advisors it feels like.&nbsp;
I<br>
assume that combination is part of where &quot;at least&quot; came
from.<br><br>
But Barry's new text gets rid of that odd and possibly confusing<br>
way of stating things and is, IMO, a considerable improvement.<br><br>
&nbsp;&nbsp; john<br>
</blockquote></blockquote></body>
<br>
</html>

--=====================_159038573==.ALT--


From barryleiba@gmail.com  Sat Aug 18 17:39:33 2012
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A71A221F8487 for <ietf@ietfa.amsl.com>; Sat, 18 Aug 2012 17:39:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.01
X-Spam-Level: 
X-Spam-Status: No, score=-103.01 tagged_above=-999 required=5 tests=[AWL=-0.033, 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 wUSg7EyaiG8X for <ietf@ietfa.amsl.com>; Sat, 18 Aug 2012 17:39:33 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD9C21F8472 for <ietf@ietf.org>; Sat, 18 Aug 2012 17:39:33 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so5080148vbb.31 for <ietf@ietf.org>; Sat, 18 Aug 2012 17:39:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=UG7Xm1ywSQ+Ju5Mp0Kgg741hZZMasrSeiAR6tAmLTS4=; b=LvjHy7AADJWQOYufIhSQbVILl3q5N/LQsWf1hEIQlXt2EAeHfS6SzWk6JD9d9TBhu0 qkWBqbl7UvXV+6o1jUakROHwWSPAWsbguSEjQJ06wYP9IgwuWNSr75QBd6SXXHgSBXLu FZTk+cmo/guk4zLgf3QLtzJKqceXuHGNui1VJ6Jx1Pb0GsBoiSYwaTh/YJWDV3h1PqFU BUR4XyBBNcgFNtLt/NIrzJzvRa787B7NOgbLb76kXvh9sSxsjYx4krtsJGJkYTp7Q00L 1zSZPZSmh5sPZpyLNWhrKcAV003A4KxseCeouC7QHZo2Rxj4SCNmzbx+4VY3U06X6PVe 4cRQ==
MIME-Version: 1.0
Received: by 10.59.8.37 with SMTP id dh5mr7028040ved.2.1345336772558; Sat, 18 Aug 2012 17:39:32 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.58.58.41 with HTTP; Sat, 18 Aug 2012 17:39:32 -0700 (PDT)
In-Reply-To: <201208182219.q7IMJeZD007195@hormel4.ieee.org>
References: <20120816212429.3635.98463.idtracker@ietfa.amsl.com> <CALaySJKfGW-VWTQT1wUOia-=idwq0f-H=zhvFVcTxvqrvSu7pQ@mail.gmail.com> <06515DE7-EA23-45EC-9C85-E4003777073F@vigilsec.com> <93CCDEE4ED0AB0B11FD5FF71@JcK-HP8200.jck.com> <DFEFDF3A-7C94-4F79-95EF-C7B4DB6826B9@comcast.net> <1D53ED7B7A8C9F54343B35A1@JcK-HP8200.jck.com> <B6AC8192-A117-4DA5-AE0D-EBA2EC594E2F@comcast.net> <201208182219.q7IMJeZD007195@hormel4.ieee.org>
Date: Sat, 18 Aug 2012 20:39:32 -0400
X-Google-Sender-Auth: yyGUquHAJcQuTUwEwYbzSBuAyRM
Message-ID: <CALaySJK5UVW6rbP9R43CxbwqfoisYkL2DdUnaO7-Yc2=PjqfZQ@mail.gmail.com>
Subject: Re: New Version Notification for draft-leiba-3777upd-eligibility-01.txt
From: Barry Leiba <barryleiba@computer.org>
To: Michael StJohns <mstjohns@comcast.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: John C Klensin <john@jck.com>, S Moonesamy <sm+ietf@elandsys.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: Sun, 19 Aug 2012 00:39:33 -0000

> With respect to the current edit of the text I'd make one more change to
> make this clear:
>
>         The nominating committee is comprised of a Chair, ten
>         voting volunteers, the immediate past nominating
>         committee Chair
>
> [or their alternate]
>
>  in an advisory capacity, plus liaisons
>         and optional additional advisor(s) as described in
>         Section 4 of RFC 3777.

Ack; makes sense.  I'll adjust my upcoming version.

Barry

From barryleiba.mailing.lists@gmail.com  Sat Aug 18 17:59:26 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47B7521F84C9 for <ietf@ietfa.amsl.com>; Sat, 18 Aug 2012 17:59:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.01
X-Spam-Level: 
X-Spam-Status: No, score=-103.01 tagged_above=-999 required=5 tests=[AWL=-0.033, 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 lqo-Aud-k+TO for <ietf@ietfa.amsl.com>; Sat, 18 Aug 2012 17:59:25 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8797321F8473 for <ietf@ietf.org>; Sat, 18 Aug 2012 17:59:25 -0700 (PDT)
Received: by lbbgg6 with SMTP id gg6so2879260lbb.31 for <ietf@ietf.org>; Sat, 18 Aug 2012 17:59:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=UD1PseUkSEd5OkpRNJHBsO0kFnlu479z/gBOcVCic60=; b=XQwP622SgeDyPi3O22bwbr1jUJ4mwWYrwitO9T/r/SsuuFXygUQYswxcIVWPxIqRwr RZpfDYjX298PWAc9r1wKfwb9oc/TqNq9P2xiMKdo1xKHZvr7M/zRvx5ZXin1Zv+lF44p kFqQRCWnOOVnjmrhsXPngAtKv53W4f/blu0NtAWHApRKWMQo7gMG9wRJ2nAzePM8A+VE cqSxUJ6xAlQ3738pPQPCfoUd9FA4toJ8n43/LS/+Cv+1CGLr6jhERHxS8evOzLrgYkhM GSBPZqbZNDPQHOmvfFpgMU9KYnstt5gONnbAXCBIE8+EHkp24V5lI9vWnFEDa0xuSlq0 +8ZA==
MIME-Version: 1.0
Received: by 10.112.10.198 with SMTP id k6mr4276663lbb.83.1345337964510; Sat, 18 Aug 2012 17:59:24 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.113.196 with HTTP; Sat, 18 Aug 2012 17:59:24 -0700 (PDT)
In-Reply-To: <CALaySJK5UVW6rbP9R43CxbwqfoisYkL2DdUnaO7-Yc2=PjqfZQ@mail.gmail.com>
References: <20120816212429.3635.98463.idtracker@ietfa.amsl.com> <CALaySJKfGW-VWTQT1wUOia-=idwq0f-H=zhvFVcTxvqrvSu7pQ@mail.gmail.com> <06515DE7-EA23-45EC-9C85-E4003777073F@vigilsec.com> <93CCDEE4ED0AB0B11FD5FF71@JcK-HP8200.jck.com> <DFEFDF3A-7C94-4F79-95EF-C7B4DB6826B9@comcast.net> <1D53ED7B7A8C9F54343B35A1@JcK-HP8200.jck.com> <B6AC8192-A117-4DA5-AE0D-EBA2EC594E2F@comcast.net> <201208182219.q7IMJeZD007195@hormel4.ieee.org> <CALaySJK5UVW6rbP9R43CxbwqfoisYkL2DdUnaO7-Yc2=PjqfZQ@mail.gmail.com>
Date: Sat, 18 Aug 2012 20:59:24 -0400
X-Google-Sender-Auth: OvQlpCXW1SURG-GDNG08E92oJxc
Message-ID: <CAC4RtVDL07d+qECoRpVydSCM4OOxOL5WuV0vMxnBb0SThbJWgw@mail.gmail.com>
Subject: Re: New Version Notification for draft-leiba-3777upd-eligibility-01.txt
From: Barry Leiba <barryleiba@computer.org>
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: S Moonesamy <sm+ietf@elandsys.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Aug 2012 00:59:26 -0000

> Ack; makes sense.  I'll adjust my upcoming version.

I went ahead and posted it:

URL:
http://www.ietf.org/internet-drafts/draft-leiba-3777upd-eligibility-02.txt
Status:          http://datatracker.ietf.org/doc/draft-leiba-3777upd-eligibility
Htmlized:        http://tools.ietf.org/html/draft-leiba-3777upd-eligibility-02
Diff:
http://www.ietf.org/rfcdiff?url2=draft-leiba-3777upd-eligibility-02

Barry

From housley@vigilsec.com  Sun Aug 19 20:56:58 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C32B21F8639 for <ietf@ietfa.amsl.com>; Sun, 19 Aug 2012 20:56:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.414
X-Spam-Level: 
X-Spam-Status: No, score=-102.414 tagged_above=-999 required=5 tests=[AWL=0.185, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UXIdNAeMS78g for <ietf@ietfa.amsl.com>; Sun, 19 Aug 2012 20:56:57 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 8C2A221F8618 for <ietf@ietf.org>; Sun, 19 Aug 2012 20:56:57 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 5C24AF2403E; Sun, 19 Aug 2012 23:57:04 -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 Zvdez8WwskBU; Sun, 19 Aug 2012 23:56:55 -0400 (EDT)
Received: from [192.168.1.3] (96-37-2-47.dhcp.sffl.va.charter.com [96.37.2.47]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 78C71F2403D; Sun, 19 Aug 2012 23:57:02 -0400 (EDT)
Subject: Re: Number of interim meetings?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <502EA168.5080502@gmail.com>
Date: Sun, 19 Aug 2012 23:56:51 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <09BB825D-D034-4927-A84D-46A5D7E0F821@vigilsec.com>
References: <502EA168.5080502@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Aug 2012 03:56:58 -0000

The announcements for interim meetings are posted here:
http://www.ietf.org/meeting/interim.html.

Without doing any statistical analysis, the list does not show a shift =
in the way the IETF is working. Some WGs like to make use of =
face-to-face or virtual interim meetings.  Most do this when they are =
really digging into a technical specification.

Russ

On Aug 17, 2012, at 3:54 PM, Melinda Shore wrote:

> Hi -
>=20
> Is anyone tracking the number of interim meetings?  It seems as
> if the number has been growing quite a bit, although that may be
> a function of the number of working groups.  It might be
> interesting to try to get a handle on whether or not there's been
> some sort of shift in working methods within the organization.
>=20
> Melinda


From dworley@avaya.com  Mon Aug 20 07:29:41 2012
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 95BDA21F851A for <ietf@ietfa.amsl.com>; Mon, 20 Aug 2012 07:29:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.29
X-Spam-Level: 
X-Spam-Status: No, score=-103.29 tagged_above=-999 required=5 tests=[AWL=0.309, 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 cRvfAgekHsr7 for <ietf@ietfa.amsl.com>; Mon, 20 Aug 2012 07:29:41 -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 1893F21F84FB for <ietf@ietf.org>; Mon, 20 Aug 2012 07:29:40 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAB1IMlDGmAcF/2dsb2JhbABFhgGzXG2BB4IhAQEEEhERNAMeAgEIDQ0CJgICAjAVEAEBBBsah2ubcoodklOBIY9qMmADm06KFIJ9
X-IronPort-AV: E=Sophos;i="4.77,798,1336363200"; d="scan'208";a="362772408"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 20 Aug 2012 10:25:10 -0400
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by co300216-co-erhwest-out.avaya.com with ESMTP; 20 Aug 2012 10:24:06 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Mon, 20 Aug 2012 10:29:40 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 20 Aug 2012 10:29:39 -0400
Subject: Re: IETF 92 in Dallas!
Thread-Topic: IETF 92 in Dallas!
Thread-Index: Ac1+4DtuexATOniIToaMfUMAFfvVGg==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A1E35@DC-US1MBEX4.global.avaya.com>
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net> <BA2EE8F7-92C8-4F10-B10A-2B6FE4FC954A@gmail.com> <502E9614.30409@raszuk.net> <502E9841.8070205@bogus.com> <502E9982.5080909@raszuk.net> <502F4A2A.8090005@krsek.cz>
In-Reply-To: <502F4A2A.8090005@krsek.cz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Aug 2012 14:29:41 -0000

V2UgYXJlIHBhaWQgd2VsbCB0byBkZXNpZ24gcHJvdG9jb2xzIGJlY2F1c2UgZGVzaWduaW5nIHBy
b3RvY29scyB0aGF0Cndvcmsgd2VsbCBpbiBwcmFjdGljZSBpcyBhIHRyaWNreSBhcnQgdGhhdCBp
cyBiZXN0IHByYWN0aWNlZCBieSBleHBlcnRzCmluIHRoZSBmaWVsZC4KCkJ1dCBuZWdvdGlhdGlu
ZyBhbGwgdGhlIGFycmFuZ2VtZW50cyBmb3IgYSBjb21wbGV4IHRlY2huaWNhbCBjb25mZXJlbmNl
CmlzIGEgc3RyYWlnaHRmb3J3YXJkIG1hdHRlciBvZiBjb21wYXJpbmcgdGhlIHB1Ymxpc2hlZCBy
b29tIHJhdGVzIG9mCnZhcmlvdXMgaG90ZWxzIGFuZCBjYW4gYmUgc3VjY2Vzc2Z1bGx5IGFjY29t
cGxpc2hlZCBieSBhbnkgbGl0ZXJhdGUKcGVyc29uIHdobyB0YWtlcyBhbiBpbnRlcmVzdCBpbiBk
b2luZyBpdC4KCk5vdyBJJ20gb2ZmIHRvIGRvIG15IG93biBkZW50YWwgd29yay4gIFRoYXQgbGVm
dCBtb2xhciBoYXMgYmVlbgpib3RoZXJpbmcgbWUuLi4KCkRhbGUKCg==

From dcrocker@gmail.com  Fri Aug 17 13:44:53 2012
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 27C9611E80E1; Fri, 17 Aug 2012 13:44:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.486
X-Spam-Level: 
X-Spam-Status: No, score=-3.486 tagged_above=-999 required=5 tests=[AWL=0.114,  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 3chNyYMhPHmX; Fri, 17 Aug 2012 13:44:52 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0CAFA11E80DC; Fri, 17 Aug 2012 13:44:51 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so3853810vcb.31 for <multiple recipients>; Fri, 17 Aug 2012 13:44:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=TUR5a9yyxpJ6K/qNlyeWgj4jykr1pp8SoT84lSsGmpw=; b=lJV990v1/nsDi/O4An7j/4oy9UhZfn+zfDXmOQQMt0hNrPH5jbLYOtQinyHOyZHybA CdajpV7zVt9qwhUt2Ld/ZF/+lGlxkxtA3D9lbeCJMym1/EJTs3da29iz0pQ+ZSozOWaf Meas3tAE40+GXDc/0ZmKvzmu+Uf8Xf877lMI7Ulffo4KnUpEJr87DpqM7pWabf3J/T1j fR2Efem6/qFx+FUQhfS/0lvj9PwLGwEe49rTq1fJm+qJdx/sRXUeKwR8Ik0R3lkD91tb nkhOmLqtWYfyeIDcNliaO+ZpP1+WqtORs60+yJzF4fEv02hMd3NjahbQ4X9z+W/zzF7M 5P0w==
Received: by 10.52.95.69 with SMTP id di5mr2984644vdb.33.1345236291276; Fri, 17 Aug 2012 13:44:51 -0700 (PDT)
Received: from [172.17.143.202] (50-78-155-157-static.hfc.comcastbusiness.net. [50.78.155.157]) by mx.google.com with ESMTPS id q19sm1441354vdf.21.2012.08.17.13.44.48 (version=SSLv3 cipher=OTHER); Fri, 17 Aug 2012 13:44:49 -0700 (PDT)
Message-ID: <502EAD34.8090605@gmail.com>
Date: Fri, 17 Aug 2012 16:44:36 -0400
From: Dave Crocker <dcrocker@gmail.com>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: [IAOC] IETF 92 in Dallas!
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net> <BA2EE8F7-92C8-4F10-B10A-2B6FE4FC954A@gmail.com> <502E9614.30409@raszuk.net> <502E9841.8070205@bogus.com> <502E9982.5080909@raszuk.net> <AEE96A9B18EF64F4B3914E1A@JcK-HP8200.jck.com>
In-Reply-To: <AEE96A9B18EF64F4B3914E1A@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 20 Aug 2012 09:53:53 -0700
Cc: iaoc@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Aug 2012 20:44:53 -0000

On 8/17/2012 4:34 PM, John C Klensin wrote:
> 
> 
> --On Friday, August 17, 2012 21:20 +0200 Robert Raszuk
> <robert@raszuk.net> wrote:
> 
>> Besides hotel is least worry as we do know the IETF rates for
>> the last few years and it is quite easy to check with any
>> hotel if they are willing to meet those targets or not.
> 
> Actually, we don't 


except for:

   http://iaoc.ietf.org/mfstatement_detail.html

might be enough detail for the concern being raised here.

d/

-- 
 Dave Crocker
 bbiw.net

From prvs=35764f35d8=lyong@ciena.com  Fri Aug 17 16:58:55 2012
Return-Path: <prvs=35764f35d8=lyong@ciena.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BEB721E80A0 for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 16:58:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.602
X-Spam-Level: 
X-Spam-Status: No, score=-102.602 tagged_above=-999 required=5 tests=[AWL=0.662, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u6I9ssrp3jJe for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 16:58:49 -0700 (PDT)
Received: from mx0b-00103a01.pphosted.com (mx0b-00103a01.pphosted.com [67.231.152.227]) by ietfa.amsl.com (Postfix) with ESMTP id 7710121E809B for <ietf@ietf.org>; Fri, 17 Aug 2012 16:58:49 -0700 (PDT)
Received: from pps.filterd (m0001124 [127.0.0.1]) by mx0b-00103a01.pphosted.com (8.14.4/8.14.4) with SMTP id q7HNufYK019564; Fri, 17 Aug 2012 19:58:48 -0400
Received: from mdwexght02.ciena.com (LIN1-118-36-29.ciena.com [63.118.36.29]) by mx0b-00103a01.pphosted.com with ESMTP id 16svsh8hb2-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 17 Aug 2012 19:58:47 -0400
Received: from MDWEXGMB02.ciena.com ([::1]) by MDWEXGHT02.ciena.com ([::1]) with mapi; Fri, 17 Aug 2012 19:58:49 -0400
From: "Ong, Lyndon" <Lyong@Ciena.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Fri, 17 Aug 2012 19:58:19 -0400
Subject: FW: re: Last Call: <draft-ietf-ccamp-rfc5787bis-05.txt> 
Thread-Topic: FW: re: Last Call: <draft-ietf-ccamp-rfc5787bis-05.txt> 
Thread-Index: Ac181C07DL/Yk6UtTwalOZbscHvIQQ==
Message-ID: <A0B4FC0A5EFBD44585414760DB4FD2749F512AA9@MDWEXGMB02.ciena.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_A0B4FC0A5EFBD44585414760DB4FD2749F512AA9MDWEXGMB02ciena_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855, 1.0.260, 0.0.0000 definitions=2012-08-17_05:2012-08-17, 2012-08-17, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=2 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1208170285
X-Mailman-Approved-At: Mon, 20 Aug 2012 09:55:02 -0700
Cc: "Shew, Stephen" <sshew@ciena.com>, "draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org" <draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Aug 2012 23:58:55 -0000

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

(Submitted on behalf of Stephen Shew)

I would like to raise an issue with draft-ietf-ccamp-rfc5787bis-05.txt.  Th=
e issue does not affect the proposed sub-TLVs or their semantics, so it wou=
ld not affect an implementation. I believe some statements in the document =
should be edited to avoid confusion over ASON terminology as defined in ITU=
-T Recommendation G.8080, for which I am editor.

It concerns the definition of "ASON reachability" which changed during the =
course of the document from being a transport plane address, the SubNetwork=
 Point Pool (SNPP) space, to the Signalling Control Network (SCN) address s=
pace.  I think the root of the issue is that the visibility of the three ad=
dress spaces described in ASON (G.8080) is not always made clear when discu=
ssing using OSPF for ASON Routing.  Section 3 of G.8080 states that:

There are three categories of identifiers used for ASON routing

   (G7715.1): transport plane names, control plane identifiers for

   components, and Signaling Communications Network (SCN) addresses.

In -03 of the document, the term SNPP was used. This is the SubNetwork Poin=
t Pool space that describes the data plane and is defined in G.8080 Section=
 10.  It names the subnetwork (and/or containing subnetworks) to which Subn=
etwork Points (SNPs) are scoped. From G.8081: "The SNP is an abstraction th=
at represents an actual or potential underlying connection point (CP) (or c=
onnection termination point (CTP)) or an actual or potential termination co=
nnection point (TCP) or trail termination point (TTP). Several SNPs (in dif=
ferent subnetwork partitions) may represent the same TCP or CP."

In concrete terms, an SNPP would name an OTN switch, and an SNP would be a =
label identifying an ODU0.  For the topology of the transport plane, SNPP a=
nd SNPP link names are used.  Path computation is performed over such a top=
ology.  If a path can be computed between two SNPPs, they are reachable in =
ASON terms. For example, and ingress OTN switch for an ODU1 connection that=
 terminates on an egress OTN switch.

The Signalling Control Network (SCN) is a separate network over which contr=
ol messages are sent. It has a topology independent of the transport plane.=
  Path computation on the SCN address space is used to connect SCN address.=
  SDH/OTN networks often have a separate IP network as the SCN network and =
the topology of the SCN network does not have to follow the topology of the=
 transport network.

ASON Control Plane Component identifiers are the third name space and ident=
ify routing and signalling instances.  It is expected that they form adjace=
ncies over the SCN.  The topology of the adjacencies is independent of the =
SCN and transport plane topologies.  "Reachability" between two control pla=
ne components would be some sequence of adjacencies.  It is entirely possib=
le to have two separate control planes running over the same SCN network, o=
r one control plane that uses several SCNs.  For example, imagine some OSPF=
 instances whose adjacencies were all targeted and each adjacency traversed=
 a separate private IP network.  The OSPF instances would need to identifie=
d by a common address space so that they are distinguished from each other,=
 but the TE interfaces could have overlapping IPv4 values because they woul=
d be in different private IP network spaces.

What makes the discussion of "TE router ID" confusing is that as applied to=
 a transport network, every node gets a "TE router ID" and so it can be use=
d in the transport topology for path computation.  In that sense it is "rea=
chable" in the dataplane.  However, it is also (I think) an address that is=
 implicitly in the SCN space in some implementations and so it takes on a d=
ual meaning of "reachability" at the IP layer as in the sentence from the I=
-D "This TLV specifies a stable OSPF TE node IP address, i.e., the IP addre=
ss is always reachable when there is IP connectivity to the associated OSPF=
 TE node.".  If a router were instantiated without any routing protocols, a=
s in one form of Software Defined Networks (SDNs), an identifier would be n=
eeded for the node itself so that path computation in a centralized control=
ler could form the router data plane topology.

Suggested changes to the draft are:
In section 3, third paragraph:  "In the context of OSPF Traffic Engineering=
 (TE), an ASON transport node corresponds to a unique OSPF TE node.  An OSP=
F TE node is uniquely identified by the TE Router Address TLV [RFC3630]. In=
 this document, this TE Router Address is referred to as the TE Router ID, =
which is in the ASON SCN name space."  However, G.8080 distinguishes betwee=
n the transport node and its associated control plane components, esp. the =
Routing Controller.  It is the control plane component that is accessed thr=
ough the SCN rather than the transport node itself.
I propose changing the statement to say: "In this document, this TE Router =
Address is referred to as the TE Router ID, which is in the ASON SNPP name =
space."
Alternatively, we could just delete the sentence "In this document, this TE=
 Router Address is referred to as the TE Router ID, which is in the ASON SN=
PP name space.".

In section 4, first paragraph, reachability of endpoints in the transport p=
lane is described as follows:
"In ASON, reachability refers to the set of endpoints reachable in the tran=
sport plane by an associated ASON transport node.  Reachable entities are i=
dentified in the ASON SCN name space."  As discussed above, only the contro=
l plane components are accessed through the SCN, not the transport nodes th=
emselves.  Entities that are reachable in the transport plane are identifie=
d through ASON SNPPs rather than ASON SCN addresses.  Therefore I suggest r=
emoving the second sentence completely so that it reads simply "In ASON, re=
achability refers to the set of endpoints reachable in the transport plane =
by an associated ASON transport node. "

Finally, in section 6.2, first paragraph following the format diagram, it i=
s stated:  "If it is not included in a Node Attribute TLV or a value of 0 i=
s specified for the Local TE Router Identifier, the Note Attribute TLV will=
 not be used for determining ASON SCN reachability."
Again, the text should be edited to make the distinction between transport =
plane and SCN clearer, I suggest modifying the statement to refer to "ASON =
reachability" rather than "ASON SCN reachability".  The statement would rea=
d as follows (also correcting the spelling of the TLV):
"If it is not included in a Node Attribute TLV or a value of 0 is specified=
 for the Local TE Router Identifier, the Node Attribute TLV will not be use=
d for determining ASON reachability."



Stephen Shew



-----Original Message-----

From: ietf-announce-bounces@ietf.org<mailto:ietf-announce-bounces@ietf.org>=
 [mailto:ietf-announce-bounces@ietf.org] On Behalf Of The IESG

Sent: Friday, July 20, 2012 11:19 AM

To: IETF-Announce

Cc: ccamp@ietf.org<mailto:ccamp@ietf.org>

Subject: Last Call: <draft-ietf-ccamp-rfc5787bis-05.txt> (ASON Routing for =
OSPFv2 Protocols) to Proposed Standard





The IESG has received a request from the Common Control and Measurement Pla=
ne WG (ccamp) to consider the following document:

- 'ASON Routing for OSPFv2 Protocols'

  <draft-ietf-ccamp-rfc5787bis-05.txt> as Proposed Standard



The IESG plans to make a decision in the next few weeks, and solicits final=
 comments on this action. Please send substantive comments to the ietf@ietf=
.org<mailto:ietf@ietf.org> mailing lists by 2012-08-17. Exceptionally, comm=
ents may be sent to iesg@ietf.org<mailto:iesg@ietf.org> instead. In either =
case, please retain the beginning of the Subject line to allow automated so=
rting. This is a four- week last call period because it spans the IETF-84 m=
eeting.



Abstract



   The ITU-T has defined an architecture and requirements for operating

   an Automatically Switched Optical Network (ASON).



   The Generalized Multiprotocol Label Switching (GMPLS) protocol suite

   is designed to provide a control plane for a range of network

   technologies including optical networks such as time division

   multiplexing (TDM) networks including SONET/SDH and Optical Transport

   Networks (OTNs), and lambda switching optical networks.



   The requirements for GMPLS routing to satisfy the requirements of

   ASON routing, and an evaluation of existing GMPLS routing protocols

   are provided in other documents.  This document defines extensions to

   the OSPFv2 Link State Routing Protocol to meet the requirements for

   routing in an ASON.



   Note that this work is scoped to the requirements and evaluation

   expressed in RFC 4258 and RFC 4652 and the ITU-T Recommendations

   current when those documents were written.  Future extensions of

   revisions of this work may be necessary if the ITU-T Recommendations

   are revised or if new requirements are introduced into a revision of

   RFC 4258. This document obsoletes RFC 5787 and updates RFC 5786.







The file can be obtained via

http://datatracker.ietf.org/doc/draft-ietf-ccamp-rfc5787bis/



IESG discussion can be tracked via

http://datatracker.ietf.org/doc/draft-ietf-ccamp-rfc5787bis/ballot/



No IPR declarations have been submitted directly on this I-D.


Stephen Shew | Director, Standards
sshew@ciena.com<mailto:jdoe@ciena.com> | 3500 Carling Ave. | Ottawa CANADA =
K2H 8E9
Direct +1.613.670.3211


--_000_A0B4FC0A5EFBD44585414760DB4FD2749F512AA9MDWEXGMB02ciena_
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:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin: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;}
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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoNoSpacing, li.MsoNoSpacing, div.MsoNoSpacing
	{mso-style-priority:1;
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.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><span lang=3DEN-=
GB>(Submitted on behalf of Stephen Shew)<o:p></o:p></span></p><p class=3DMs=
oNormal><span lang=3DEN-GB><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal=
><span lang=3DEN-GB>I would like to raise an issue with draft-ietf-ccamp-rf=
c5787bis-05.txt.&nbsp; The issue does not affect the proposed sub-TLVs or t=
heir semantics, so it would not affect an implementation. I believe some st=
atements in the document should be edited to avoid confusion over ASON term=
inology as defined in ITU-T Recommendation G.8080, for which I am editor.<o=
:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-GB><o:p>&nbsp;</o:=
p></span></p><p class=3DMsoNormal><span lang=3DEN-GB>It concerns the defini=
tion of &#8220;ASON reachability&#8221; which changed during the course of =
the document from being a transport plane address, the SubNetwork Point Poo=
l (SNPP) space, to the Signalling Control Network (SCN) address space.&nbsp=
; I think the root of the issue is that the visibility of the three address=
 spaces described in ASON (G.8080) is not always made clear when discussing=
 using OSPF for ASON Routing.&nbsp; Section 3 of G.8080 states that:<o:p></=
o:p></span></p><p class=3DMsoNoSpacing><span lang=3DEN-GB style=3D'font-fam=
ily:"Courier New"'>There are three categories of identifiers used for ASON =
routing<o:p></o:p></span></p><p class=3DMsoNoSpacing><span lang=3DEN-GB sty=
le=3D'font-family:"Courier New"'>&nbsp;&nbsp; (G7715.1): transport plane na=
mes, control plane identifiers for<o:p></o:p></span></p><p class=3DMsoNoSpa=
cing><span lang=3DEN-GB style=3D'font-family:"Courier New"'>&nbsp;&nbsp; co=
mponents, and Signaling Communications Network (SCN) addresses.<o:p></o:p><=
/span></p><p class=3DMsoNormal><span lang=3DEN-GB style=3D'font-family:"Tim=
es New Roman","serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><sp=
an lang=3DEN-GB>In -03 of the document, the term SNPP was used. This is the=
 SubNetwork Point Pool space that describes the data plane and is defined i=
n G.8080 Section 10.&nbsp; It names the subnetwork (and/or containing subne=
tworks) to which Subnetwork Points (SNPs) are scoped. From G.8081: &#8220;T=
he SNP is an abstraction that represents an actual or potential underlying =
connection point (CP) (or connection termination point (CTP)) or an actual =
or potential termination connection point (TCP) or trail termination point =
(TTP). Several SNPs (in different subnetwork partitions) may represent the =
same TCP or CP.</span><span dir=3DRTL></span><span lang=3DAR-AE dir=3DRTL s=
tyle=3D'font-family:"Arial","sans-serif"'><span dir=3DRTL></span>&quot;</sp=
an><span lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal><span lang=
=3DEN-GB><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-G=
B>In concrete terms, an SNPP would name an OTN switch, and an SNP would be =
a label identifying an ODU0.&nbsp; For the topology of the transport plane,=
 SNPP and SNPP link names are used.&nbsp; Path computation is performed ove=
r such a topology.&nbsp; If a path can be computed between two SNPPs, they =
are reachable in ASON terms. For example, and ingress OTN switch for an ODU=
1 connection that terminates on an egress OTN switch.<o:p></o:p></span></p>=
<p class=3DMsoNormal><span style=3D'font-family:"Arial","sans-serif"'><o:p>=
&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-GB>The Signalli=
ng Control Network (SCN) is a separate network over which control messages =
are sent. It has a topology independent of the transport plane.&nbsp; Path =
computation on the SCN address space is used to connect SCN address.&nbsp; =
SDH/OTN networks often have a separate IP network as the SCN network and th=
e topology of the SCN network does not have to follow the topology of the t=
ransport network.</span><span style=3D'font-family:"Times New Roman","serif=
"'><o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DAR-SA dir=3DRTL =
style=3D'font-family:"Times New Roman","serif"'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-GB>ASON Control Plane Component ident=
ifiers are the third name space and identify routing and signalling instanc=
es.&nbsp; It is expected that they form adjacencies over the SCN.&nbsp; The=
 topology of the adjacencies is independent of the SCN and transport plane =
topologies.&nbsp; &#8220;Reachability&#8221; between two control plane comp=
onents would be some sequence of adjacencies.&nbsp; It is entirely possible=
 to have two separate control planes running over the same SCN network, or =
one control plane that uses several SCNs.&nbsp; For example, imagine some O=
SPF instances whose adjacencies were all targeted and each adjacency traver=
sed a separate private IP network.&nbsp; The OSPF instances would need to i=
dentified by a common address space so that they are distinguished from eac=
h other, but the TE interfaces could have overlapping IPv4 values because t=
hey would be in different private IP network spaces.<o:p></o:p></span></p><=
p class=3DMsoNormal><span lang=3DEN-GB><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoNormal><span lang=3DEN-GB>What makes the discussion of &#8220;TE rout=
er ID&#8221; confusing is that as applied to a transport network, every nod=
e gets a &#8220;TE router ID&#8221; and so it can be used in the transport =
topology for path computation.&nbsp; In that sense it is &#8220;reachable&#=
8221; in the dataplane.&nbsp; However, it is also (I think) an address that=
 is implicitly in the SCN space in some implementations and so it takes on =
a dual meaning of &#8220;reachability&#8221; at the IP layer as in the sent=
ence from the I-D &#8220;This TLV specifies a stable OSPF TE node IP addres=
s, i.e., the IP address is always reachable when there is IP connectivity t=
o the associated OSPF TE node.&#8221;.&nbsp; If a router were instantiated =
without any routing protocols, as in one form of Software Defined Networks =
(SDNs), an identifier would be needed for the node itself so that path comp=
utation in a centralized controller could form the router data plane topolo=
gy.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-GB><o:p>&nbsp=
;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-GB>Suggested changes=
 to the draft are:<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DE=
N-GB>In section 3, third paragraph:&nbsp; &quot;In the context of OSPF Traf=
fic Engineering (TE), an ASON transport node corresponds to a unique OSPF T=
E node.&nbsp; An OSPF TE node is uniquely identified by the TE Router Addre=
ss TLV [RFC3630]. In this document, this TE Router Address is referred to a=
s the TE Router ID, which is in the ASON SCN name space.&quot;&nbsp; Howeve=
r, G.8080 distinguishes between the transport node and its associated contr=
ol plane components, esp. the Routing Controller.&nbsp; It is the control p=
lane component that is accessed through the SCN rather than the transport n=
ode itself.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-GB>I =
propose changing the statement to say: &quot;In this document, this TE Rout=
er Address is referred to as the TE Router ID, which is in the ASON SNPP na=
me space.&#8221;<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-=
GB>Alternatively, we could just delete the sentence &#8220;In this document=
, this TE Router Address is referred to as the TE Router ID, which is in th=
e ASON SNPP name space.&#8221;.<o:p></o:p></span></p><p class=3DMsoNormal><=
span lang=3DEN-GB><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span la=
ng=3DEN-GB>In section 4, first paragraph, reachability of endpoints in the =
transport plane is described as follows:<o:p></o:p></span></p><p class=3DMs=
oNormal><span lang=3DEN-GB>&quot;In ASON, reachability refers to the set of=
 endpoints reachable in the transport plane by an associated ASON transport=
 node.&nbsp; Reachable entities are identified in the ASON SCN name space.&=
quot;&nbsp; As discussed above, only the control plane components are acces=
sed through the SCN, not the transport nodes themselves.&nbsp; Entities tha=
t are reachable in the transport plane are identified through ASON SNPPs ra=
ther than ASON SCN addresses.&nbsp; Therefore I suggest removing the second=
 sentence completely so that it reads simply &quot;In ASON, reachability re=
fers to the set of endpoints reachable in the transport plane by an associa=
ted ASON transport node.&nbsp;&#8220;<o:p></o:p></span></p><p class=3DMsoNo=
rmal><span lang=3DEN-GB><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><s=
pan lang=3DEN-GB>Finally, in section 6.2, first paragraph following the for=
mat diagram, it is stated:&nbsp; &quot;If it is not included in a Node Attr=
ibute TLV or a value of 0 is specified for the Local TE Router Identifier, =
the Note Attribute TLV will not be used for determining ASON SCN reachabili=
ty.&quot;&nbsp; <o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-=
GB>Again, the text should be edited to make the distinction between transpo=
rt plane and SCN clearer, I suggest modifying the statement to refer to &qu=
ot;ASON reachability&quot; rather than &quot;ASON SCN reachability&quot;.&n=
bsp; The statement would read as follows (also correcting the spelling of t=
he TLV):<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-GB>&quot=
;If it is not included in a Node Attribute TLV or a value of 0 is specified=
 for the Local TE Router Identifier, the Node Attribute TLV will not be use=
d for determining ASON reachability.&quot;<o:p></o:p></span></p><p class=3D=
MsoPlainText><span lang=3DEN-GB><o:p>&nbsp;</o:p></span></p><p class=3DMsoP=
lainText><span lang=3DEN-GB>Stephen Shew<o:p></o:p></span></p><p class=3DMs=
oPlainText><span lang=3DEN-GB><o:p>&nbsp;</o:p></span></p><p class=3DMsoPla=
inText>-----Original Message-----<o:p></o:p></p><p class=3DMsoPlainText>Fro=
m: <a href=3D"mailto:ietf-announce-bounces@ietf.org">ietf-announce-bounces@=
ietf.org</a> [<a href=3D"mailto:ietf-announce-bounces@ietf.org">mailto:ietf=
-announce-bounces@ietf.org</a>] On Behalf Of The IESG<o:p></o:p></p><p clas=
s=3DMsoPlainText>Sent: Friday, July 20, 2012 11:19 AM<o:p></o:p></p><p clas=
s=3DMsoPlainText>To: IETF-Announce<o:p></o:p></p><p class=3DMsoPlainText>Cc=
: <a href=3D"mailto:ccamp@ietf.org">ccamp@ietf.org</a><o:p></o:p></p><p cla=
ss=3DMsoPlainText>Subject: Last Call: &lt;draft-ietf-ccamp-rfc5787bis-05.tx=
t&gt; (ASON Routing for OSPFv2 Protocols) to Proposed Standard<o:p></o:p></=
p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText><o:p=
>&nbsp;</o:p></p><p class=3DMsoPlainText>The IESG has received a request fr=
om the Common Control and Measurement Plane WG (ccamp) to consider the foll=
owing document:<o:p></o:p></p><p class=3DMsoPlainText>- 'ASON Routing for O=
SPFv2 Protocols'<o:p></o:p></p><p class=3DMsoPlainText>&nbsp; &lt;draft-iet=
f-ccamp-rfc5787bis-05.txt&gt; as Proposed Standard<o:p></o:p></p><p class=
=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>The IESG plans=
 to make a decision in the next few weeks, and solicits final comments on t=
his action. Please send substantive comments to the <a href=3D"mailto:ietf@=
ietf.org">ietf@ietf.org</a> mailing lists by 2012-08-17. Exceptionally, com=
ments may be sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> ins=
tead. In either case, please retain the beginning of the Subject line to al=
low automated sorting. This is a four- week last call period because it spa=
ns the IETF-84 meeting.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</=
o:p></p><p class=3DMsoPlainText>Abstract<o:p></o:p></p><p class=3DMsoPlainT=
ext><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>&nbsp;&nbsp; The ITU-T has=
 defined an architecture and requirements for operating<o:p></o:p></p><p cl=
ass=3DMsoPlainText>&nbsp;&nbsp; an Automatically Switched Optical Network (=
ASON).<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=
=3DMsoPlainText>&nbsp;&nbsp; The Generalized Multiprotocol Label Switching =
(GMPLS) protocol suite<o:p></o:p></p><p class=3DMsoPlainText>&nbsp;&nbsp; i=
s designed to provide a control plane for a range of network<o:p></o:p></p>=
<p class=3DMsoPlainText>&nbsp;&nbsp; technologies including optical network=
s such as time division<o:p></o:p></p><p class=3DMsoPlainText>&nbsp;&nbsp; =
multiplexing (TDM) networks including SONET/SDH and Optical Transport<o:p><=
/o:p></p><p class=3DMsoPlainText>&nbsp;&nbsp; Networks (OTNs), and lambda s=
witching optical networks.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp=
;</o:p></p><p class=3DMsoPlainText>&nbsp;&nbsp; The requirements for GMPLS =
routing to satisfy the requirements of<o:p></o:p></p><p class=3DMsoPlainTex=
t>&nbsp;&nbsp; ASON routing, and an evaluation of existing GMPLS routing pr=
otocols<o:p></o:p></p><p class=3DMsoPlainText>&nbsp;&nbsp; are provided in =
other documents.&nbsp; This document defines extensions to<o:p></o:p></p><p=
 class=3DMsoPlainText>&nbsp;&nbsp; the OSPFv2 Link State Routing Protocol t=
o meet the requirements for<o:p></o:p></p><p class=3DMsoPlainText>&nbsp;&nb=
sp; routing in an ASON.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</=
o:p></p><p class=3DMsoPlainText>&nbsp;&nbsp; Note that this work is scoped =
to the requirements and evaluation<o:p></o:p></p><p class=3DMsoPlainText>&n=
bsp;&nbsp; expressed in RFC 4258 and RFC 4652 and the ITU-T Recommendations=
<o:p></o:p></p><p class=3DMsoPlainText>&nbsp;&nbsp; current when those docu=
ments were written.&nbsp; Future extensions of<o:p></o:p></p><p class=3DMso=
PlainText>&nbsp;&nbsp; revisions of this work may be necessary if the ITU-T=
 Recommendations<o:p></o:p></p><p class=3DMsoPlainText>&nbsp;&nbsp; are rev=
ised or if new requirements are introduced into a revision of<o:p></o:p></p=
><p class=3DMsoPlainText>&nbsp;&nbsp; RFC 4258. This document obsoletes RFC=
 5787 and updates RFC 5786.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbs=
p;</o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlai=
nText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>The file can be obtained=
 via<o:p></o:p></p><p class=3DMsoPlainText><a href=3D"http://datatracker.ie=
tf.org/doc/draft-ietf-ccamp-rfc5787bis/">http://datatracker.ietf.org/doc/dr=
aft-ietf-ccamp-rfc5787bis/</a><o:p></o:p></p><p class=3DMsoPlainText><o:p>&=
nbsp;</o:p></p><p class=3DMsoPlainText>IESG discussion can be tracked via<o=
:p></o:p></p><p class=3DMsoPlainText><a href=3D"http://datatracker.ietf.org=
/doc/draft-ietf-ccamp-rfc5787bis/ballot/">http://datatracker.ietf.org/doc/d=
raft-ietf-ccamp-rfc5787bis/ballot/</a><o:p></o:p></p><p class=3DMsoPlainTex=
t><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>No IPR declarations have bee=
n submitted directly on this I-D.<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-family:"Times New Roman","serif";color:#1F497D'><o:p>&nbsp;</=
o:p></span></p><p class=3DMsoNormal><span style=3D'font-family:"Times New R=
oman","serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNorm=
al><b><span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color=
:#1F497D'>Stephen Shew</span></b><span style=3D'font-size:7.5pt;font-family=
:"Arial","sans-serif";color:#1F497D'>&nbsp;</span><span style=3D'font-size:=
7.5pt;font-family:"Arial","sans-serif";color:red'>|</span><span style=3D'fo=
nt-size:7.5pt;font-family:"Arial","sans-serif";color:#1F497D'> </span><span=
 style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:gray'>Dire=
ctor, Standards</span><span style=3D'font-size:7.5pt;font-family:"Arial","s=
ans-serif";color:#1F497D'><br></span><u><span style=3D'font-size:7.5pt;font=
-family:"Arial","sans-serif";color:blue'><a href=3D"mailto:jdoe@ciena.com">=
sshew@ciena.com</a></span></u><span style=3D'font-size:7.5pt;font-family:"A=
rial","sans-serif";color:#1F497D'> </span><span style=3D'font-size:7.5pt;fo=
nt-family:"Arial","sans-serif";color:red'>|</span><span style=3D'font-size:=
7.5pt;font-family:"Arial","sans-serif";color:purple'> </span><span style=3D=
'font-size:7.5pt;font-family:"Arial","sans-serif";color:gray'>3500 Carling =
Ave. </span><span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"=
;color:red'>|</span><span style=3D'font-size:7.5pt;font-family:"Arial","san=
s-serif";color:purple'>&nbsp;</span><span style=3D'font-size:7.5pt;font-fam=
ily:"Arial","sans-serif";color:gray'>Ottawa CANADA K2H 8E9<br>Direct +1.613=
.670.3211<o:p></o:p></span></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></=
div></body></html>=

--_000_A0B4FC0A5EFBD44585414760DB4FD2749F512AA9MDWEXGMB02ciena_--

From prvs=35764dcc2a=sshew@ciena.com  Fri Aug 17 14:16:05 2012
Return-Path: <prvs=35764dcc2a=sshew@ciena.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3098511E80EA for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 14:16:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.014
X-Spam-Level: 
X-Spam-Status: No, score=-3.014 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, MIME_BAD_LINEBREAK=0.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 jUGtDwLbNM4x for <ietf@ietfa.amsl.com>; Fri, 17 Aug 2012 14:15:59 -0700 (PDT)
Received: from mx0a-00103a01.pphosted.com (mx0a-00103a01.pphosted.com [67.231.144.234]) by ietfa.amsl.com (Postfix) with ESMTP id 562FE11E80D1 for <ietf@ietf.org>; Fri, 17 Aug 2012 14:15:59 -0700 (PDT)
Received: from pps.filterd (m0000419 [127.0.0.1]) by mx0a-00103a01.pphosted.com (8.14.4/8.14.4) with SMTP id q7HLF6pS022139 for <ietf@ietf.org>; Fri, 17 Aug 2012 17:15:59 -0400
Received: from mdwexght02.ciena.com (LIN1-118-36-29.ciena.com [63.118.36.29]) by mx0a-00103a01.pphosted.com with ESMTP id 16svk2095m-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Fri, 17 Aug 2012 17:15:58 -0400
Received: from MDWEXCHCGSIHT01.ciena.com (10.4.140.106) by MDWEXGHT02.ciena.com (10.4.140.213) with Microsoft SMTP Server (TLS) id 8.3.192.1; Fri, 17 Aug 2012 17:15:58 -0400
Received: from ONWVEXCHHT02.ciena.com (10.128.6.17) by MDWEXCHCGSIHT01.ciena.com (10.4.140.106) with Microsoft SMTP Server (TLS) id 8.3.192.1; Fri, 17 Aug 2012 17:15:58 -0400
Received: from ONWVEXCHMB02.ciena.com ([::1]) by ONWVEXCHHT02.ciena.com ([::1]) with mapi; Fri, 17 Aug 2012 17:15:57 -0400
From: "Shew, Stephen" <sshew@ciena.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Date: Fri, 17 Aug 2012 17:15:57 -0400
Subject: Fw: Last Call: <draft-ietf-ccamp-rfc5787bis-05.txt> (ASON Routing for OSPFv2 Protocols) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-ccamp-rfc5787bis-05.txt> (ASON Routing for OSPFv2 Protocols) to Proposed Standard
Thread-Index: Ac18uLqTSXOPlEipSYqOSdjpw90bzQABMN3g
Message-ID: <510C3D5C5DFBCB46AE189D936C1DD605A5FDBBD408@ONWVEXCHMB02.ciena.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_510C3D5C5DFBCB46AE189D936C1DD605A5FDBBD408ONWVEXCHMB02c_"
MIME-Version: 1.0
X-TM-AS-Product-Ver: SMEX-10.0.0.1412-7.000.1014-19120.004
X-TM-AS-Result: No--34.555800-8.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855, 1.0.260, 0.0.0000 definitions=2012-08-17_05:2012-08-17, 2012-08-17, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=2 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1208170234
X-Mailman-Approved-At: Mon, 20 Aug 2012 09:55:19 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Aug 2012 21:16:05 -0000

--_000_510C3D5C5DFBCB46AE189D936C1DD605A5FDBBD408ONWVEXCHMB02c_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

DQpTdGVwaGVuIFNoZXcgfCBUZWwuICsxLjYxMy42NzAuMzIxMQ0KDQpGcm9tOiBTaGV3LCBTdGVw
aGVuDQpTZW50OiBGcmlkYXksIEF1Z3VzdCAxNywgMjAxMiAwNDo0MSBQTQ0KVG86IGlldGYtYW5u
b3VuY2VAaWV0Zi5vcmcgPGlldGYtYW5ub3VuY2VAaWV0Zi5vcmc+DQpTdWJqZWN0OiByZTogTGFz
dCBDYWxsOiA8ZHJhZnQtaWV0Zi1jY2FtcC1yZmM1Nzg3YmlzLTA1LnR4dD4gKEFTT04gUm91dGlu
ZyBmb3IgT1NQRnYyIFByb3RvY29scykgdG8gUHJvcG9zZWQgU3RhbmRhcmQNCg0KSSB3b3VsZCBs
aWtlIHRvIHJhaXNlIGFuIGlzc3VlIHdpdGggZHJhZnQtaWV0Zi1jY2FtcC1yZmM1Nzg3YmlzLTA1
LnR4dC4gIFRoZSBpc3N1ZSBkb2VzIG5vdCBhZmZlY3QgdGhlIHByb3Bvc2VkIHN1Yi1UTFZzIG9y
IHRoZWlyIHNlbWFudGljcywgc28gaXQgd291bGQgbm90IGFmZmVjdCBhbiBpbXBsZW1lbnRhdGlv
bi4gSSBiZWxpZXZlIHNvbWUgc3RhdGVtZW50cyBpbiB0aGUgZG9jdW1lbnQgc2hvdWxkIGJlIGVk
aXRlZCB0byBhdm9pZCBjb25mdXNpb24gb3ZlciBBU09OIHRlcm1pbm9sb2d5IGFzIGRlZmluZWQg
aW4gSVRVLVQgUmVjb21tZW5kYXRpb24gRy44MDgwLCBmb3Igd2hpY2ggSSBhbSBlZGl0b3IuDQoN
Ckl0IGNvbmNlcm5zIHRoZSBkZWZpbml0aW9uIG9mIOKAnEFTT04gcmVhY2hhYmlsaXR54oCdIHdo
aWNoIHdhcyBjaGFuZ2VkIGZyb20gYmVpbmcgYSB0cmFuc3BvcnQgcGxhbmUgYWRkcmVzcywgdGhl
IFN1Yk5ldHdvcmsgUG9pbnQgUG9vbCAoU05QUCkgc3BhY2UsIHRvIHRoZSBTaWduYWxsaW5nIENv
bnRyb2wgTmV0d29yayAoU0NOKSBhZGRyZXNzIHNwYWNlLiAgSSB0aGluayB0aGUgcm9vdCBvZiB0
aGUgaXNzdWUgaXMgdGhhdCB0aGUgdmlzaWJpbGl0eSBvZiB0aGUgdGhyZWUgYWRkcmVzcyBzcGFj
ZXMgZGVzY3JpYmVkIGluIEFTT04gKEcuODA4MCkgaXMgbm90IGNsZWFyIHdoZW4gdXNpbmcgT1NQ
RiBmb3IgQVNPTiBSb3V0aW5nLiAgU2VjdGlvbiAzIG9mIEcuODA4MCBzdGF0ZXMgdGhhdDoNCg0K
VGhlcmUgYXJlIHRocmVlIGNhdGVnb3JpZXMgb2YgaWRlbnRpZmllcnMgdXNlZCBmb3IgQVNPTiBy
b3V0aW5nDQoNCiAgIChHNzcxNS4xKTogdHJhbnNwb3J0IHBsYW5lIG5hbWVzLCBjb250cm9sIHBs
YW5lIGlkZW50aWZpZXJzIGZvcg0KDQogICBjb21wb25lbnRzLCBhbmQgU2lnbmFsaW5nIENvbW11
bmljYXRpb25zIE5ldHdvcmsgKFNDTikgYWRkcmVzc2VzLg0KDQpJbiAtMDMsIHRoZSB0ZXJtIFNO
UFAgd2FzIHVzZWQuIFRoaXMgaXMgdGhlIFN1Yk5ldHdvcmsgUG9pbnQgUG9vbCBzcGFjZSB0aGF0
IGRlc2NyaWJlcyB0aGUgZGF0YSBwbGFuZSBhbmQgaXMgZGVmaW5lZCBpbiBHLjgwODAgU2VjdGlv
biAxMC4gIEl0IG5hbWVzIHRoZSBzdWJuZXR3b3JrIChhbmQvb3IgY29udGFpbmluZyBzdWJuZXR3
b3JrcykgdG8gd2hpY2ggU3VibmV0d29yayBQb2ludHMgKFNOUHMpIGFyZSBzY29wZWQuIEZyb20g
Ry44MDgxOiDigJxUaGUgU05QIGlzIGFuIGFic3RyYWN0aW9uIHRoYXQgcmVwcmVzZW50cyBhbiBh
Y3R1YWwgb3IgcG90ZW50aWFsIHVuZGVybHlpbmcgY29ubmVjdGlvbiBwb2ludCAoQ1ApIChvciBj
b25uZWN0aW9uIHRlcm1pbmF0aW9uIHBvaW50IChDVFApKSBvciBhbiBhY3R1YWwgb3IgcG90ZW50
aWFsIHRlcm1pbmF0aW9uIGNvbm5lY3Rpb24gcG9pbnQgKFRDUCkgb3IgdHJhaWwgdGVybWluYXRp
b24gcG9pbnQgKFRUUCkuIFNldmVyYWwgU05QcyAoaW4gZGlmZmVyZW50IHN1Ym5ldHdvcmsgcGFy
dGl0aW9ucykgbWF5IHJlcHJlc2VudCB0aGUgc2FtZSBUQ1Agb3IgQ1AuIg0KDQpJbiBjb25jcmV0
ZSB0ZXJtcywgYW4gU05QUCB3b3VsZCBuYW1lIGFuIE9UTiBzd2l0Y2gsIGFuZCBhbiBTTlAgd291
bGQgYmUgYSBsYWJlbCBpZGVudGlmeWluZyBhbiBPRFUwLiAgRm9yIHRoZSB0b3BvbG9neSBvZiB0
aGUgdHJhbnNwb3J0IHBsYW5lLCBTTlBQIGFuZCBTTlBQIGxpbmsgbmFtZXMgYXJlIHVzZWQuICBQ
YXRoIGNvbXB1dGF0aW9uIGlzIHBlcmZvcm1lZCBvdmVyIHN1Y2ggYSB0b3BvbG9neS4gIElmIGEg
cGF0aCBjYW4gYmUgY29tcHV0ZWQgYmV0d2VlbiB0d28gU05QUHMsIHRoZXkgYXJlIHJlYWNoYWJs
ZSBpbiBBU09OIHRlcm1zLiBGb3IgZXhhbXBsZSwgYW5kIGluZ3Jlc3MgT1ROIHN3aXRjaCBmb3Ig
YW4gT0RVMSBjb25uZWN0aW9uIHRoYXQgdGVybWluYXRlcyBvbiBhbiBlZ3Jlc3MgT1ROIHN3aXRj
aC4NCg0KVGhlIFNpZ25hbGxpbmcgQ29udHJvbCBOZXR3b3JrIChTQ04pIGlzIGEgc2VwYXJhdGUg
bmV0d29yayBvdmVyIHdoaWNoIGNvbnRyb2wgbWVzc2FnZXMgYXJlIHNlbnQuIEl0IGhhcyBhIHRv
cG9sb2d5IGluZGVwZW5kZW50IG9mIHRoZSB0cmFuc3BvcnQgcGxhbmUuICBQYXRoIGNvbXB1dGF0
aW9uIG9uIHRoZSBTQ04gYWRkcmVzcyBzcGFjZSBpcyB1c2VkIHRvIGNvbm5lY3QgU0NOIGFkZHJl
c3MuICBTREgvT1ROIG5ldHdvcmtzIG9mdGVuIGhhdmUgYSBzZXBhcmF0ZSBJUCBuZXR3b3JrIGFz
IHRoZSBTQ04gbmV0d29yayBhbmQgdGhlIHRvcG9sb2d5IG9mIHRoZSBTQ04gbmV0d29yayBkb2Vz
IG5vdCBoYXZlIHRvIGZvbGxvdyB0aGUgdG9wb2xvZ3kgb2YgdGhlIHRyYW5zcG9ydCBuZXR3b3Jr
Lg0KDQpBU09OIENvbnRyb2wgUGxhbmUgQ29tcG9uZW50IGlkZW50aWZpZXJzIGFyZSB0aGUgdGhp
cmQgbmFtZSBzcGFjZSBhbmQgaWRlbnRpZnkgcm91dGluZyBhbmQgc2lnbmFsbGluZyBpbnN0YW5j
ZXMuICBJdCBpcyBleHBlY3RlZCB0aGF0IHRoZXkgZm9ybSBhZGphY2VuY2llcyBvdmVyIHRoZSBT
Q04uICBUaGUgdG9wb2xvZ3kgb2YgdGhlIGFkamFjZW5jaWVzIGlzIGluZGVwZW5kZW50IG9mIHRo
ZSBTQ04gYW5kIHRyYW5zcG9ydCBwbGFuZSB0b3BvbG9naWVzLiAg4oCcUmVhY2hhYmlsaXR54oCd
IGJldHdlZW4gdHdvIGNvbnRyb2wgcGxhbmUgY29tcG9uZW50cyB3b3VsZCBiZSBzb21lIHNlcXVl
bmNlIG9mIGFkamFjZW5jaWVzLiAgSXQgaXMgZW50aXJlbHkgcG9zc2libGUgdG8gaGF2ZSB0d28g
c2VwYXJhdGUgY29udHJvbCBwbGFuZXMgcnVubmluZyBvdmVyIHRoZSBzYW1lIFNDTiBuZXR3b3Jr
LCBvciBvbmUgY29udHJvbCBwbGFuZSB0aGF0IHVzZXMgc2V2ZXJhbCBTQ05zLiAgRm9yIGV4YW1w
bGUsIGltYWdpbmUgc29tZSBPU1BGIGluc3RhbmNlcyB3aG9zZSBhZGphY2VuY2llcyB3ZXJlIGFs
bCB0YXJnZXRlZCBhbmQgZWFjaCBhZGphY2VuY3kgdHJhdmVyc2VkIGEgc2VwYXJhdGUgcHJpdmF0
ZSBJUCBuZXR3b3JrLiAgVGhlIE9TUEYgaW5zdGFuY2VzIHdvdWxkIG5lZWQgdG8gaWRlbnRpZmll
ZCBieSBhIGNvbW1vbiBhZGRyZXNzIHNwYWNlIHNvIHRoYXQgdGhleSBhcmUgZGlzdGluZ3Vpc2hl
ZCBmcm9tIGVhY2ggb3RoZXIsIGJ1dCB0aGUgVEUgaW50ZXJmYWNlcyBjb3VsZCBoYXZlIG92ZXJs
YXBwaW5nIElQdjQgdmFsdWVzIGJlY2F1c2UgdGhleSB3b3VsZCBiZSBpbiBkaWZmZXJlbnQgcHJp
dmF0ZSBJUCBuZXR3b3JrIHNwYWNlcy4NCg0KV2hhdCBtYWtlcyB0aGUgZGlzY3Vzc2lvbiBvZiDi
gJxURSByb3V0ZXIgSUTigJ0gY29uZnVzaW5nIGlzIHRoYXQgYXMgYXBwbGllZCB0byBhIHRyYW5z
cG9ydCBuZXR3b3JrLCBldmVyeSBub2RlIGdldHMgYSDigJxURSByb3V0ZXIgSUTigJ0gYW5kIHNv
IGl0IGNhbiBiZSB1c2VkIGluIHRoZSB0cmFuc3BvcnQgdG9wb2xvZ3kgZm9yIHBhdGggY29tcHV0
YXRpb24uICBJbiB0aGF0IHNlbnNlIGl0IGlzIOKAnHJlYWNoYWJsZeKAnSBpbiB0aGUgZGF0YXBs
YW5lLiAgSG93ZXZlciwgaXQgaXMgYWxzbyAoSSB0aGluaykgYW4gYWRkcmVzcyB0aGF0IGlzIGlt
cGxpY2l0bHkgaW4gdGhlIFNDTiBzcGFjZSBpbiBzb21lIGltcGxlbWVudGF0aW9ucyBhbmQgc28g
aXQgdGFrZXMgb24gYSBkdWFsIG1lYW5pbmcgb2Yg4oCccmVhY2hhYmlsaXR54oCdIGF0IHRoZSBJ
UCBsYXllciBhcyBpbiB0aGUgc2VudGVuY2UgZnJvbSB0aGUgSS1EIOKAnFRoaXMgVExWIHNwZWNp
ZmllcyBhIHN0YWJsZSBPU1BGIFRFIG5vZGUgSVAgYWRkcmVzcywgaS5lLiwgdGhlIElQIGFkZHJl
c3MgaXMgYWx3YXlzIHJlYWNoYWJsZSB3aGVuIHRoZXJlIGlzIElQIGNvbm5lY3Rpdml0eSB0byB0
aGUgYXNzb2NpYXRlZCBPU1BGIFRFIG5vZGUu4oCdLiAgSWYgYSByb3V0ZXIgd2VyZSBpbnN0YW50
aWF0ZWQgd2l0aG91dCBhbnkgcm91dGluZyBwcm90b2NvbHMsIGFzIGluIG9uZSBmb3JtIG9mIFNv
ZnR3YXJlIERlZmluZWQgTmV0d29ya3MgKFNETnMpLCBhbiBpZGVudGlmaWVyIHdvdWxkIGJlIG5l
ZWRlZCBmb3IgdGhlIG5vZGUgaXRzZWxmIHNvIHRoYXQgcGF0aCBjb21wdXRhdGlvbiBpbiBhIGNl
bnRyYWxpemVkIGNvbnRyb2xsZXIgY291bGQgZm9ybSB0aGUgcm91dGVyIGRhdGEgcGxhbmUgdG9w
b2xvZ3kuDQoNClN1Z2dlc3RlZCBjaGFuZ2VzIHRvIHRoZSBkcmFmdCBhcmU6DQpJbiBzZWN0aW9u
IDMsIHRoaXJkIHBhcmFncmFwaDogICJJbiB0aGUgY29udGV4dCBvZiBPU1BGIFRyYWZmaWMgRW5n
aW5lZXJpbmcgKFRFKSwgYW4gQVNPTiB0cmFuc3BvcnQgbm9kZSBjb3JyZXNwb25kcyB0byBhIHVu
aXF1ZSBPU1BGIFRFIG5vZGUuICBBbiBPU1BGIFRFIG5vZGUgaXMgdW5pcXVlbHkgaWRlbnRpZmll
ZCBieSB0aGUgVEUgUm91dGVyIEFkZHJlc3MgVExWIFtSRkMzNjMwXS4gSW4gdGhpcyBkb2N1bWVu
dCwgdGhpcyBURSBSb3V0ZXIgQWRkcmVzcyBpcyByZWZlcnJlZCB0byBhcyB0aGUgVEUgUm91dGVy
IElELCB3aGljaCBpcyBpbiB0aGUgQVNPTiBTQ04gbmFtZSBzcGFjZS4iICBIb3dldmVyLCBHLjgw
ODAgZGlzdGluZ3Vpc2hlcyBiZXR3ZWVuIHRoZSB0cmFuc3BvcnQgbm9kZSBhbmQgaXRzIGFzc29j
aWF0ZWQgY29udHJvbCBwbGFuZSBjb21wb25lbnRzLCBlc3AuIHRoZSBSb3V0aW5nIENvbnRyb2xs
ZXIuICBJdCBpcyB0aGUgY29udHJvbCBwbGFuZSBjb21wb25lbnQgdGhhdCBpcyBhY2Nlc3NlZCB0
aHJvdWdoIHRoZSBTQ04gcmF0aGVyIHRoYW4gdGhlIHRyYW5zcG9ydCBub2RlIGl0c2VsZi4NCkkg
cHJvcG9zZSBjaGFuZ2luZyB0aGUgc3RhdGVtZW50IHRvIHNheTogIkluIHRoaXMgZG9jdW1lbnQs
IHRoaXMgVEUgUm91dGVyIEFkZHJlc3MgaXMgcmVmZXJyZWQgdG8gYXMgdGhlIFRFIFJvdXRlciBJ
RCwgd2hpY2ggaXMgaW4gdGhlIEFTT04gU05QUCBuYW1lIHNwYWNlLuKAnQ0KT3IsIHdlIGNvdWxk
IGp1c3QgZGVsZXRlIHRoZSBzZW50ZW5jZSDigJxJbiB0aGlzIGRvY3VtZW50LCB0aGlzIFRFIFJv
dXRlciBBZGRyZXNzIGlzIHJlZmVycmVkIHRvIGFzIHRoZSBURSBSb3V0ZXIgSUQsIHdoaWNoIGlz
IGluIHRoZSBBU09OIFNOUFAgbmFtZSBzcGFjZS7igJ0uDQoNCkluIHNlY3Rpb24gNCwgZmlyc3Qg
cGFyYWdyYXBoLCByZWFjaGFiaWxpdHkgb2YgZW5kcG9pbnRzIGluIHRoZSB0cmFuc3BvcnQgcGxh
bmUgaXMgZGVzY3JpYmVkIGFzIGZvbGxvd3M6DQoiSW4gQVNPTiwgcmVhY2hhYmlsaXR5IHJlZmVy
cyB0byB0aGUgc2V0IG9mIGVuZHBvaW50cyByZWFjaGFibGUgaW4gdGhlIHRyYW5zcG9ydCBwbGFu
ZSBieSBhbiBhc3NvY2lhdGVkIEFTT04gdHJhbnNwb3J0IG5vZGUuICBSZWFjaGFibGUgZW50aXRp
ZXMgYXJlIGlkZW50aWZpZWQgaW4gdGhlIEFTT04gU0NOIG5hbWUgc3BhY2UuIiAgQXMgZGlzY3Vz
c2VkIGFib3ZlLCBvbmx5IHRoZSBjb250cm9sIHBsYW5lIGNvbXBvbmVudHMgYXJlIGFjY2Vzc2Vk
IHRocm91Z2ggdGhlIFNDTiwgbm90IHRoZSB0cmFuc3BvcnQgbm9kZXMgdGhlbXNlbHZlcy4gIEVu
dGl0aWVzIHRoYXQgYXJlIHJlYWNoYWJsZSBpbiB0aGUgdHJhbnNwb3J0IHBsYW5lIGFyZSBpZGVu
dGlmaWVkIHRocm91Z2ggQVNPTiBTTlBQcyByYXRoZXIgdGhhbiBBU09OIFNDTiBhZGRyZXNzZXMu
ICBUaGVyZWZvcmUgSSBzdWdnZXN0IHJlbW92aW5nIHRoZSBzZWNvbmQgc2VudGVuY2UgY29tcGxl
dGVseS4NCg0KRmluYWxseSwgaW4gc2VjdGlvbiA2LjIsIGZpcnN0IHBhcmFncmFwaCBmb2xsb3dp
bmcgdGhlIGZvcm1hdCBkaWFncmFtLCBpdCBpcyBzdGF0ZWQ6ICAiSWYgaXQgaXMgbm90IGluY2x1
ZGVkIGluIGEgTm9kZSBBdHRyaWJ1dGUgVExWIG9yIGEgdmFsdWUgb2YgMCBpcyBzcGVjaWZpZWQg
Zm9yIHRoZSBMb2NhbCBURSBSb3V0ZXIgSWRlbnRpZmllciwgdGhlIE5vdGUgQXR0cmlidXRlIFRM
ViB3aWxsIG5vdCBiZSB1c2VkIGZvciBkZXRlcm1pbmluZyBBU09OIFNDTiByZWFjaGFiaWxpdHku
Ig0KQWdhaW4sIHRoZSB0ZXh0IHNob3VsZCBiZSBlZGl0ZWQgdG8gbWFrZSB0aGUgZGlzdGluY3Rp
b24gYmV0d2VlbiB0cmFuc3BvcnQgcGxhbmUgYW5kIFNDTiBjbGVhcmVyLCBJIHN1Z2dlc3QgbW9k
aWZ5aW5nIHRoZSBzdGF0ZW1lbnQgdG8gcmVmZXIgdG8gIkFTT04gcmVhY2hhYmlsaXR5IiByYXRo
ZXIgdGhhbiAiQVNPTiBTQ04gcmVhY2hhYmlsaXR5Ii4gIFRoZSBzdGF0ZW1lbnQgd291bGQgcmVh
ZCBhcyBmb2xsb3dzIChhbHNvIGNvcnJlY3RpbmcgdGhlIHNwZWxsaW5nIG9mIHRoZSBUTFYpOg0K
IklmIGl0IGlzIG5vdCBpbmNsdWRlZCBpbiBhIE5vZGUgQXR0cmlidXRlIFRMViBvciBhIHZhbHVl
IG9mIDAgaXMgc3BlY2lmaWVkIGZvciB0aGUgTG9jYWwgVEUgUm91dGVyIElkZW50aWZpZXIsIHRo
ZSBOb2RlIEF0dHJpYnV0ZSBUTFYgd2lsbCBub3QgYmUgdXNlZCBmb3IgZGV0ZXJtaW5pbmcgQVNP
TiByZWFjaGFiaWxpdHkuIg0KDQoNCg0KU3RlcGhlbg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2Ut
LS0tLQ0KDQpGcm9tOiBpZXRmLWFubm91bmNlLWJvdW5jZXNAaWV0Zi5vcmc8bWFpbHRvOmlldGYt
YW5ub3VuY2UtYm91bmNlc0BpZXRmLm9yZz4gW21haWx0bzppZXRmLWFubm91bmNlLWJvdW5jZXNA
aWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBUaGUgSUVTRw0KDQpTZW50OiBGcmlkYXksIEp1bHkgMjAs
IDIwMTIgMTE6MTkgQU0NCg0KVG86IElFVEYtQW5ub3VuY2UNCg0KQ2M6IGNjYW1wQGlldGYub3Jn
PG1haWx0bzpjY2FtcEBpZXRmLm9yZz4NCg0KU3ViamVjdDogTGFzdCBDYWxsOiA8ZHJhZnQtaWV0
Zi1jY2FtcC1yZmM1Nzg3YmlzLTA1LnR4dD4gKEFTT04gUm91dGluZyBmb3IgT1NQRnYyIFByb3Rv
Y29scykgdG8gUHJvcG9zZWQgU3RhbmRhcmQNCg0KDQoNCg0KDQpUaGUgSUVTRyBoYXMgcmVjZWl2
ZWQgYSByZXF1ZXN0IGZyb20gdGhlIENvbW1vbiBDb250cm9sIGFuZCBNZWFzdXJlbWVudCBQbGFu
ZSBXRyAoY2NhbXApIHRvIGNvbnNpZGVyIHRoZSBmb2xsb3dpbmcgZG9jdW1lbnQ6DQoNCi0gJ0FT
T04gUm91dGluZyBmb3IgT1NQRnYyIFByb3RvY29scycNCg0KICA8ZHJhZnQtaWV0Zi1jY2FtcC1y
ZmM1Nzg3YmlzLTA1LnR4dD4gYXMgUHJvcG9zZWQgU3RhbmRhcmQNCg0KDQoNClRoZSBJRVNHIHBs
YW5zIHRvIG1ha2UgYSBkZWNpc2lvbiBpbiB0aGUgbmV4dCBmZXcgd2Vla3MsIGFuZCBzb2xpY2l0
cyBmaW5hbCBjb21tZW50cyBvbiB0aGlzIGFjdGlvbi4gUGxlYXNlIHNlbmQgc3Vic3RhbnRpdmUg
Y29tbWVudHMgdG8gdGhlIGlldGZAaWV0Zi5vcmc8bWFpbHRvOmlldGZAaWV0Zi5vcmc+IG1haWxp
bmcgbGlzdHMgYnkgMjAxMi0wOC0xNy4gRXhjZXB0aW9uYWxseSwgY29tbWVudHMgbWF5IGJlIHNl
bnQgdG8gaWVzZ0BpZXRmLm9yZzxtYWlsdG86aWVzZ0BpZXRmLm9yZz4gaW5zdGVhZC4gSW4gZWl0
aGVyIGNhc2UsIHBsZWFzZSByZXRhaW4gdGhlIGJlZ2lubmluZyBvZiB0aGUgU3ViamVjdCBsaW5l
IHRvIGFsbG93IGF1dG9tYXRlZCBzb3J0aW5nLiBUaGlzIGlzIGEgZm91ci0gd2VlayBsYXN0IGNh
bGwgcGVyaW9kIGJlY2F1c2UgaXQgc3BhbnMgdGhlIElFVEYtODQgbWVldGluZy4NCg0KDQoNCkFi
c3RyYWN0DQoNCg0KDQogICBUaGUgSVRVLVQgaGFzIGRlZmluZWQgYW4gYXJjaGl0ZWN0dXJlIGFu
ZCByZXF1aXJlbWVudHMgZm9yIG9wZXJhdGluZw0KDQogICBhbiBBdXRvbWF0aWNhbGx5IFN3aXRj
aGVkIE9wdGljYWwgTmV0d29yayAoQVNPTikuDQoNCg0KDQogICBUaGUgR2VuZXJhbGl6ZWQgTXVs
dGlwcm90b2NvbCBMYWJlbCBTd2l0Y2hpbmcgKEdNUExTKSBwcm90b2NvbCBzdWl0ZQ0KDQogICBp
cyBkZXNpZ25lZCB0byBwcm92aWRlIGEgY29udHJvbCBwbGFuZSBmb3IgYSByYW5nZSBvZiBuZXR3
b3JrDQoNCiAgIHRlY2hub2xvZ2llcyBpbmNsdWRpbmcgb3B0aWNhbCBuZXR3b3JrcyBzdWNoIGFz
IHRpbWUgZGl2aXNpb24NCg0KICAgbXVsdGlwbGV4aW5nIChURE0pIG5ldHdvcmtzIGluY2x1ZGlu
ZyBTT05FVC9TREggYW5kIE9wdGljYWwgVHJhbnNwb3J0DQoNCiAgIE5ldHdvcmtzIChPVE5zKSwg
YW5kIGxhbWJkYSBzd2l0Y2hpbmcgb3B0aWNhbCBuZXR3b3Jrcy4NCg0KDQoNCiAgIFRoZSByZXF1
aXJlbWVudHMgZm9yIEdNUExTIHJvdXRpbmcgdG8gc2F0aXNmeSB0aGUgcmVxdWlyZW1lbnRzIG9m
DQoNCiAgIEFTT04gcm91dGluZywgYW5kIGFuIGV2YWx1YXRpb24gb2YgZXhpc3RpbmcgR01QTFMg
cm91dGluZyBwcm90b2NvbHMNCg0KICAgYXJlIHByb3ZpZGVkIGluIG90aGVyIGRvY3VtZW50cy4g
IFRoaXMgZG9jdW1lbnQgZGVmaW5lcyBleHRlbnNpb25zIHRvDQoNCiAgIHRoZSBPU1BGdjIgTGlu
ayBTdGF0ZSBSb3V0aW5nIFByb3RvY29sIHRvIG1lZXQgdGhlIHJlcXVpcmVtZW50cyBmb3INCg0K
ICAgcm91dGluZyBpbiBhbiBBU09OLg0KDQoNCg0KICAgTm90ZSB0aGF0IHRoaXMgd29yayBpcyBz
Y29wZWQgdG8gdGhlIHJlcXVpcmVtZW50cyBhbmQgZXZhbHVhdGlvbg0KDQogICBleHByZXNzZWQg
aW4gUkZDIDQyNTggYW5kIFJGQyA0NjUyIGFuZCB0aGUgSVRVLVQgUmVjb21tZW5kYXRpb25zDQoN
CiAgIGN1cnJlbnQgd2hlbiB0aG9zZSBkb2N1bWVudHMgd2VyZSB3cml0dGVuLiAgRnV0dXJlIGV4
dGVuc2lvbnMgb2YNCg0KICAgcmV2aXNpb25zIG9mIHRoaXMgd29yayBtYXkgYmUgbmVjZXNzYXJ5
IGlmIHRoZSBJVFUtVCBSZWNvbW1lbmRhdGlvbnMNCg0KICAgYXJlIHJldmlzZWQgb3IgaWYgbmV3
IHJlcXVpcmVtZW50cyBhcmUgaW50cm9kdWNlZCBpbnRvIGEgcmV2aXNpb24gb2YNCg0KICAgUkZD
IDQyNTguIFRoaXMgZG9jdW1lbnQgb2Jzb2xldGVzIFJGQyA1Nzg3IGFuZCB1cGRhdGVzIFJGQyA1
Nzg2Lg0KDQoNCg0KDQoNCg0KDQpUaGUgZmlsZSBjYW4gYmUgb2J0YWluZWQgdmlhDQoNCmh0dHA6
Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1jY2FtcC1yZmM1Nzg3YmlzLw0K
DQoNCg0KSUVTRyBkaXNjdXNzaW9uIGNhbiBiZSB0cmFja2VkIHZpYQ0KDQpodHRwOi8vZGF0YXRy
YWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtY2NhbXAtcmZjNTc4N2Jpcy9iYWxsb3QvDQoN
Cg0KDQpObyBJUFIgZGVjbGFyYXRpb25zIGhhdmUgYmVlbiBzdWJtaXR0ZWQgZGlyZWN0bHkgb24g
dGhpcyBJLUQuDQoNCg0KU3RlcGhlbiBTaGV3IHwgRGlyZWN0b3IsIFN0YW5kYXJkcw0Kc3NoZXdA
Y2llbmEuY29tPG1haWx0bzpqZG9lQGNpZW5hLmNvbT4gfCAzNTAwIENhcmxpbmcgQXZlLiB8IE90
dGF3YSBDQU5BREEgSzJIIDhFOQ0KRGlyZWN0ICsxLjYxMy42NzAuMzIxMQ0KDQo=

--_000_510C3D5C5DFBCB46AE189D936C1DD605A5FDBBD408ONWVEXCHMB02c_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PXVzLWFzY2lpIj48bWV0YSBuYW1lPUdlbmVyYXRvciBjb250
ZW50PSJNaWNyb3NvZnQgV29yZCAxMiAoZmlsdGVyZWQgbWVkaXVtKSI+PHN0eWxlPjwhLS0NCi8q
IEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6U2ltU3VuOw0K
CXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWls
eToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0O30NCkBmb250
LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAz
IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDEx
IDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJcQFNpbVN1biI7
DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFt
aWx5OkNvbnNvbGFzOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDIgMiA0IDMgMiA0O30NCi8qIFN0eWxl
IERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFs
DQoJe21hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4w
cHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjt9DQphOmxpbmssIHNwYW4u
TXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRl
eHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0Zv
bGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1k
ZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLk1zb1BsYWluVGV4dCwgbGkuTXNvUGxhaW5UZXh0LCBk
aXYuTXNvUGxhaW5UZXh0DQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGlu
azoiUGxhaW4gVGV4dCBDaGFyIjsNCgltYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFw
dDsNCglmb250LXNpemU6MTAuNXB0Ow0KCWZvbnQtZmFtaWx5OkNvbnNvbGFzO30NCnAuTXNvQWNl
dGF0ZSwgbGkuTXNvQWNldGF0ZSwgZGl2Lk1zb0FjZXRhdGUNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJCYWxsb29uIFRleHQgQ2hhciI7DQoJbWFyZ2luOjBpbjsN
CgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjguMHB0Ow0KCWZvbnQtZmFtaWx5
OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjt9DQpwLk1zb05vU3BhY2luZywgbGkuTXNvTm9TcGFjaW5n
LCBkaXYuTXNvTm9TcGFjaW5nDQoJe21zby1zdHlsZS1wcmlvcml0eToxOw0KCW1hcmdpbjowaW47
DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1p
bHk6IlRpbWVzIE5ldyBSb21hbiIsInNlcmlmIjt9DQpzcGFuLkVtYWlsU3R5bGUxNw0KCXttc28t
c3R5bGUtdHlwZTpwZXJzb25hbC1jb21wb3NlOw0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9t
YW4iLCJzZXJpZiI7DQoJY29sb3I6IzFGNDk3RDsNCglmb250LXdlaWdodDpub3JtYWw7DQoJZm9u
dC1zdHlsZTpub3JtYWw7fQ0Kc3Bhbi5QbGFpblRleHRDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJQ
bGFpbiBUZXh0IENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGlu
azoiUGxhaW4gVGV4dCI7DQoJZm9udC1mYW1pbHk6Q29uc29sYXM7fQ0Kc3Bhbi5CYWxsb29uVGV4
dENoYXINCgl7bXNvLXN0eWxlLW5hbWU6IkJhbGxvb24gVGV4dCBDaGFyIjsNCgltc28tc3R5bGUt
cHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkJhbGxvb24gVGV4dCI7DQoJZm9udC1mYW1p
bHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10
eXBlOmV4cG9ydC1vbmx5O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBp
bjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0K
CXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1s
Pg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1s
PjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpl
eHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVs
YXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+PC9oZWFkPjxib2R5IGxhbmc9RU4tVVMgbGluaz1ibHVl
IHZsaW5rPXB1cnBsZT48Zm9udCBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+
DQoNPGJyPlN0ZXBoZW4gU2hldyB8IFRlbC4gKzEuNjEzLjY3MC4zMjExPC9mb250Pjxicj4mbmJz
cDs8YnI+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYg
MS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8Zm9udCBzdHlsZT0iZm9udC1zaXpl
OjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90OyI+DQo8Yj5Gcm9tPC9iPjogU2hldywgU3RlcGhlbg08YnI+PGI+U2VudDwvYj46IEZyaWRh
eSwgQXVndXN0IDE3LCAyMDEyIDA0OjQxIFBNPGJyPjxiPlRvPC9iPjogaWV0Zi1hbm5vdW5jZUBp
ZXRmLm9yZyAmbHQ7aWV0Zi1hbm5vdW5jZUBpZXRmLm9yZyZndDsNPGJyPjxiPlN1YmplY3Q8L2I+
OiByZTogTGFzdCBDYWxsOiAmbHQ7ZHJhZnQtaWV0Zi1jY2FtcC1yZmM1Nzg3YmlzLTA1LnR4dCZn
dDsgKEFTT04gUm91dGluZyBmb3IgT1NQRnYyIFByb3RvY29scykgdG8gUHJvcG9zZWQgU3RhbmRh
cmQNPGJyPjwvZm9udD4mbmJzcDs8YnI+PC9kaXY+DQo8ZGl2IGNsYXNzPVdvcmRTZWN0aW9uMT48
cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gbGFuZz1FTi1HQj5JIHdvdWxkIGxpa2UgdG8gcmFpc2Ug
YW4gaXNzdWUgd2l0aCBkcmFmdC1pZXRmLWNjYW1wLXJmYzU3ODdiaXMtMDUudHh0LiZuYnNwOyBU
aGUgaXNzdWUgZG9lcyBub3QgYWZmZWN0IHRoZSBwcm9wb3NlZCBzdWItVExWcyBvciB0aGVpciBz
ZW1hbnRpY3MsIHNvIGl0IHdvdWxkIG5vdCBhZmZlY3QgYW4gaW1wbGVtZW50YXRpb24uIEkgYmVs
aWV2ZSBzb21lIHN0YXRlbWVudHMgaW4gdGhlIGRvY3VtZW50IHNob3VsZCBiZSBlZGl0ZWQgdG8g
YXZvaWQgY29uZnVzaW9uIG92ZXIgQVNPTiB0ZXJtaW5vbG9neSBhcyBkZWZpbmVkIGluIElUVS1U
IFJlY29tbWVuZGF0aW9uIEcuODA4MCwgZm9yIHdoaWNoIEkgYW0gZWRpdG9yLjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gbGFuZz1FTi1HQj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tR0I+SXQg
Y29uY2VybnMgdGhlIGRlZmluaXRpb24gb2YgJiM4MjIwO0FTT04gcmVhY2hhYmlsaXR5JiM4MjIx
OyB3aGljaCB3YXMgY2hhbmdlZCBmcm9tIGJlaW5nIGEgdHJhbnNwb3J0IHBsYW5lIGFkZHJlc3Ms
IHRoZSBTdWJOZXR3b3JrIFBvaW50IFBvb2wgKFNOUFApIHNwYWNlLCB0byB0aGUgU2lnbmFsbGlu
ZyBDb250cm9sIE5ldHdvcmsgKFNDTikgYWRkcmVzcyBzcGFjZS4mbmJzcDsgSSB0aGluayB0aGUg
cm9vdCBvZiB0aGUgaXNzdWUgaXMgdGhhdCB0aGUgdmlzaWJpbGl0eSBvZiB0aGUgdGhyZWUgYWRk
cmVzcyBzcGFjZXMgZGVzY3JpYmVkIGluIEFTT04gKEcuODA4MCkgaXMgbm90IGNsZWFyIHdoZW4g
dXNpbmcgT1NQRiBmb3IgQVNPTiBSb3V0aW5nLiZuYnNwOyBTZWN0aW9uIDMgb2YgRy44MDgwIHN0
YXRlcyB0aGF0OjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob1NwYWNpbmc+PHNw
YW4gbGFuZz1FTi1HQiBzdHlsZT0nZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Iic+VGhlcmUgYXJl
IHRocmVlIGNhdGVnb3JpZXMgb2YgaWRlbnRpZmllcnMgdXNlZCBmb3IgQVNPTiByb3V0aW5nPG86
cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vU3BhY2luZz48c3BhbiBsYW5nPUVOLUdC
IHN0eWxlPSdmb250LWZhbWlseToiQ291cmllciBOZXciJz4mbmJzcDsmbmJzcDsgKEc3NzE1LjEp
OiB0cmFuc3BvcnQgcGxhbmUgbmFtZXMsIGNvbnRyb2wgcGxhbmUgaWRlbnRpZmllcnMgZm9yPG86
cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vU3BhY2luZz48c3BhbiBsYW5nPUVOLUdC
IHN0eWxlPSdmb250LWZhbWlseToiQ291cmllciBOZXciJz4mbmJzcDsmbmJzcDsgY29tcG9uZW50
cywgYW5kIFNpZ25hbGluZyBDb21tdW5pY2F0aW9ucyBOZXR3b3JrIChTQ04pIGFkZHJlc3Nlcy48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tR0Ig
c3R5bGU9J2ZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiInPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gbGFuZz1FTi1HQj5JbiAt
MDMsIHRoZSB0ZXJtIFNOUFAgd2FzIHVzZWQuIFRoaXMgaXMgdGhlIFN1Yk5ldHdvcmsgUG9pbnQg
UG9vbCBzcGFjZSB0aGF0IGRlc2NyaWJlcyB0aGUgZGF0YSBwbGFuZSBhbmQgaXMgZGVmaW5lZCBp
biBHLjgwODAgU2VjdGlvbiAxMC4mbmJzcDsgSXQgbmFtZXMgdGhlIHN1Ym5ldHdvcmsgKGFuZC9v
ciBjb250YWluaW5nIHN1Ym5ldHdvcmtzKSB0byB3aGljaCBTdWJuZXR3b3JrIFBvaW50cyAoU05Q
cykgYXJlIHNjb3BlZC4gRnJvbSBHLjgwODE6ICYjODIyMDtUaGUgU05QIGlzIGFuIGFic3RyYWN0
aW9uIHRoYXQgcmVwcmVzZW50cyBhbiBhY3R1YWwgb3IgcG90ZW50aWFsIHVuZGVybHlpbmcgY29u
bmVjdGlvbiBwb2ludCAoQ1ApIChvciBjb25uZWN0aW9uIHRlcm1pbmF0aW9uIHBvaW50IChDVFAp
KSBvciBhbiBhY3R1YWwgb3IgcG90ZW50aWFsIHRlcm1pbmF0aW9uIGNvbm5lY3Rpb24gcG9pbnQg
KFRDUCkgb3IgdHJhaWwgdGVybWluYXRpb24gcG9pbnQgKFRUUCkuIFNldmVyYWwgU05QcyAoaW4g
ZGlmZmVyZW50IHN1Ym5ldHdvcmsgcGFydGl0aW9ucykgbWF5IHJlcHJlc2VudCB0aGUgc2FtZSBU
Q1Agb3IgQ1AuPC9zcGFuPjxzcGFuIGRpcj1SVEw+PC9zcGFuPjxzcGFuIGxhbmc9QVItQUUgZGly
PVJUTCBzdHlsZT0nZm9udC1mYW1pbHk6IkFyaWFsIiwic2Fucy1zZXJpZiInPjxzcGFuIGRpcj1S
VEw+PC9zcGFuPiZxdW90Ozwvc3Bhbj48c3BhbiBsYW5nPUVOLUdCPjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gbGFuZz1FTi1HQj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tR0I+SW4gY29uY3Jl
dGUgdGVybXMsIGFuIFNOUFAgd291bGQgbmFtZSBhbiBPVE4gc3dpdGNoLCBhbmQgYW4gU05QIHdv
dWxkIGJlIGEgbGFiZWwgaWRlbnRpZnlpbmcgYW4gT0RVMC4mbmJzcDsgRm9yIHRoZSB0b3BvbG9n
eSBvZiB0aGUgdHJhbnNwb3J0IHBsYW5lLCBTTlBQIGFuZCBTTlBQIGxpbmsgbmFtZXMgYXJlIHVz
ZWQuJm5ic3A7IFBhdGggY29tcHV0YXRpb24gaXMgcGVyZm9ybWVkIG92ZXIgc3VjaCBhIHRvcG9s
b2d5LiZuYnNwOyBJZiBhIHBhdGggY2FuIGJlIGNvbXB1dGVkIGJldHdlZW4gdHdvIFNOUFBzLCB0
aGV5IGFyZSByZWFjaGFibGUgaW4gQVNPTiB0ZXJtcy4gRm9yIGV4YW1wbGUsIGFuZCBpbmdyZXNz
IE9UTiBzd2l0Y2ggZm9yIGFuIE9EVTEgY29ubmVjdGlvbiB0aGF0IHRlcm1pbmF0ZXMgb24gYW4g
ZWdyZXNzIE9UTiBzd2l0Y2guPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1h
bD48c3BhbiBsYW5nPUFSLUFFIGRpcj1SVEwgc3R5bGU9J2ZvbnQtZmFtaWx5OiJBcmlhbCIsInNh
bnMtc2VyaWYiJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFs
PjxzcGFuIGxhbmc9RU4tR0I+VGhlIFNpZ25hbGxpbmcgQ29udHJvbCBOZXR3b3JrIChTQ04pIGlz
IGEgc2VwYXJhdGUgbmV0d29yayBvdmVyIHdoaWNoIGNvbnRyb2wgbWVzc2FnZXMgYXJlIHNlbnQu
IEl0IGhhcyBhIHRvcG9sb2d5IGluZGVwZW5kZW50IG9mIHRoZSB0cmFuc3BvcnQgcGxhbmUuJm5i
c3A7IFBhdGggY29tcHV0YXRpb24gb24gdGhlIFNDTiBhZGRyZXNzIHNwYWNlIGlzIHVzZWQgdG8g
Y29ubmVjdCBTQ04gYWRkcmVzcy4mbmJzcDsgU0RIL09UTiBuZXR3b3JrcyBvZnRlbiBoYXZlIGEg
c2VwYXJhdGUgSVAgbmV0d29yayBhcyB0aGUgU0NOIG5ldHdvcmsgYW5kIHRoZSB0b3BvbG9neSBv
ZiB0aGUgU0NOIG5ldHdvcmsgZG9lcyBub3QgaGF2ZSB0byBmb2xsb3cgdGhlIHRvcG9sb2d5IG9m
IHRoZSB0cmFuc3BvcnQgbmV0d29yay48bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNv
Tm9ybWFsPjxzcGFuIGxhbmc9RU4tR0I+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxwIGNs
YXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVOLUdCPkFTT04gQ29udHJvbCBQbGFuZSBDb21wb25l
bnQgaWRlbnRpZmllcnMgYXJlIHRoZSB0aGlyZCBuYW1lIHNwYWNlIGFuZCBpZGVudGlmeSByb3V0
aW5nIGFuZCBzaWduYWxsaW5nIGluc3RhbmNlcy4mbmJzcDsgSXQgaXMgZXhwZWN0ZWQgdGhhdCB0
aGV5IGZvcm0gYWRqYWNlbmNpZXMgb3ZlciB0aGUgU0NOLiZuYnNwOyBUaGUgdG9wb2xvZ3kgb2Yg
dGhlIGFkamFjZW5jaWVzIGlzIGluZGVwZW5kZW50IG9mIHRoZSBTQ04gYW5kIHRyYW5zcG9ydCBw
bGFuZSB0b3BvbG9naWVzLiZuYnNwOyAmIzgyMjA7UmVhY2hhYmlsaXR5JiM4MjIxOyBiZXR3ZWVu
IHR3byBjb250cm9sIHBsYW5lIGNvbXBvbmVudHMgd291bGQgYmUgc29tZSBzZXF1ZW5jZSBvZiBh
ZGphY2VuY2llcy4mbmJzcDsgSXQgaXMgZW50aXJlbHkgcG9zc2libGUgdG8gaGF2ZSB0d28gc2Vw
YXJhdGUgY29udHJvbCBwbGFuZXMgcnVubmluZyBvdmVyIHRoZSBzYW1lIFNDTiBuZXR3b3JrLCBv
ciBvbmUgY29udHJvbCBwbGFuZSB0aGF0IHVzZXMgc2V2ZXJhbCBTQ05zLiZuYnNwOyBGb3IgZXhh
bXBsZSwgaW1hZ2luZSBzb21lIE9TUEYgaW5zdGFuY2VzIHdob3NlIGFkamFjZW5jaWVzIHdlcmUg
YWxsIHRhcmdldGVkIGFuZCBlYWNoIGFkamFjZW5jeSB0cmF2ZXJzZWQgYSBzZXBhcmF0ZSBwcml2
YXRlIElQIG5ldHdvcmsuJm5ic3A7IFRoZSBPU1BGIGluc3RhbmNlcyB3b3VsZCBuZWVkIHRvIGlk
ZW50aWZpZWQgYnkgYSBjb21tb24gYWRkcmVzcyBzcGFjZSBzbyB0aGF0IHRoZXkgYXJlIGRpc3Rp
bmd1aXNoZWQgZnJvbSBlYWNoIG90aGVyLCBidXQgdGhlIFRFIGludGVyZmFjZXMgY291bGQgaGF2
ZSBvdmVybGFwcGluZyBJUHY0IHZhbHVlcyBiZWNhdXNlIHRoZXkgd291bGQgYmUgaW4gZGlmZmVy
ZW50IHByaXZhdGUgSVAgbmV0d29yayBzcGFjZXMuPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNs
YXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVOLUdCPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gbGFuZz1FTi1HQj5XaGF0IG1ha2VzIHRoZSBkaXNj
dXNzaW9uIG9mICYjODIyMDtURSByb3V0ZXIgSUQmIzgyMjE7IGNvbmZ1c2luZyBpcyB0aGF0IGFz
IGFwcGxpZWQgdG8gYSB0cmFuc3BvcnQgbmV0d29yaywgZXZlcnkgbm9kZSBnZXRzIGEgJiM4MjIw
O1RFIHJvdXRlciBJRCYjODIyMTsgYW5kIHNvIGl0IGNhbiBiZSB1c2VkIGluIHRoZSB0cmFuc3Bv
cnQgdG9wb2xvZ3kgZm9yIHBhdGggY29tcHV0YXRpb24uJm5ic3A7IEluIHRoYXQgc2Vuc2UgaXQg
aXMgJiM4MjIwO3JlYWNoYWJsZSYjODIyMTsgaW4gdGhlIGRhdGFwbGFuZS4mbmJzcDsgSG93ZXZl
ciwgaXQgaXMgYWxzbyAoSSB0aGluaykgYW4gYWRkcmVzcyB0aGF0IGlzIGltcGxpY2l0bHkgaW4g
dGhlIFNDTiBzcGFjZSBpbiBzb21lIGltcGxlbWVudGF0aW9ucyBhbmQgc28gaXQgdGFrZXMgb24g
YSBkdWFsIG1lYW5pbmcgb2YgJiM4MjIwO3JlYWNoYWJpbGl0eSYjODIyMTsgYXQgdGhlIElQIGxh
eWVyIGFzIGluIHRoZSBzZW50ZW5jZSBmcm9tIHRoZSBJLUQgJiM4MjIwO1RoaXMgVExWIHNwZWNp
ZmllcyBhIHN0YWJsZSBPU1BGIFRFIG5vZGUgSVAgYWRkcmVzcywgaS5lLiwgdGhlIElQIGFkZHJl
c3MgaXMgYWx3YXlzIHJlYWNoYWJsZSB3aGVuIHRoZXJlIGlzIElQIGNvbm5lY3Rpdml0eSB0byB0
aGUgYXNzb2NpYXRlZCBPU1BGIFRFIG5vZGUuJiM4MjIxOy4mbmJzcDsgSWYgYSByb3V0ZXIgd2Vy
ZSBpbnN0YW50aWF0ZWQgd2l0aG91dCBhbnkgcm91dGluZyBwcm90b2NvbHMsIGFzIGluIG9uZSBm
b3JtIG9mIFNvZnR3YXJlIERlZmluZWQgTmV0d29ya3MgKFNETnMpLCBhbiBpZGVudGlmaWVyIHdv
dWxkIGJlIG5lZWRlZCBmb3IgdGhlIG5vZGUgaXRzZWxmIHNvIHRoYXQgcGF0aCBjb21wdXRhdGlv
biBpbiBhIGNlbnRyYWxpemVkIGNvbnRyb2xsZXIgY291bGQgZm9ybSB0aGUgcm91dGVyIGRhdGEg
cGxhbmUgdG9wb2xvZ3kuPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48
c3BhbiBsYW5nPUVOLUdCPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29O
b3JtYWw+PHNwYW4gbGFuZz1FTi1HQj5TdWdnZXN0ZWQgY2hhbmdlcyB0byB0aGUgZHJhZnQgYXJl
OjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gbGFuZz1FTi1H
Qj5JbiBzZWN0aW9uIDMsIHRoaXJkIHBhcmFncmFwaDombmJzcDsgJnF1b3Q7SW4gdGhlIGNvbnRl
eHQgb2YgT1NQRiBUcmFmZmljIEVuZ2luZWVyaW5nIChURSksIGFuIEFTT04gdHJhbnNwb3J0IG5v
ZGUgY29ycmVzcG9uZHMgdG8gYSB1bmlxdWUgT1NQRiBURSBub2RlLiZuYnNwOyBBbiBPU1BGIFRF
IG5vZGUgaXMgdW5pcXVlbHkgaWRlbnRpZmllZCBieSB0aGUgVEUgUm91dGVyIEFkZHJlc3MgVExW
IFtSRkMzNjMwXS4gSW4gdGhpcyBkb2N1bWVudCwgdGhpcyBURSBSb3V0ZXIgQWRkcmVzcyBpcyBy
ZWZlcnJlZCB0byBhcyB0aGUgVEUgUm91dGVyIElELCB3aGljaCBpcyBpbiB0aGUgQVNPTiBTQ04g
bmFtZSBzcGFjZS4mcXVvdDsmbmJzcDsgSG93ZXZlciwgRy44MDgwIGRpc3Rpbmd1aXNoZXMgYmV0
d2VlbiB0aGUgdHJhbnNwb3J0IG5vZGUgYW5kIGl0cyBhc3NvY2lhdGVkIGNvbnRyb2wgcGxhbmUg
Y29tcG9uZW50cywgZXNwLiB0aGUgUm91dGluZyBDb250cm9sbGVyLiZuYnNwOyBJdCBpcyB0aGUg
Y29udHJvbCBwbGFuZSBjb21wb25lbnQgdGhhdCBpcyBhY2Nlc3NlZCB0aHJvdWdoIHRoZSBTQ04g
cmF0aGVyIHRoYW4gdGhlIHRyYW5zcG9ydCBub2RlIGl0c2VsZi48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tR0I+SSBwcm9wb3NlIGNoYW5naW5n
IHRoZSBzdGF0ZW1lbnQgdG8gc2F5OiAmcXVvdDtJbiB0aGlzIGRvY3VtZW50LCB0aGlzIFRFIFJv
dXRlciBBZGRyZXNzIGlzIHJlZmVycmVkIHRvIGFzIHRoZSBURSBSb3V0ZXIgSUQsIHdoaWNoIGlz
IGluIHRoZSBBU09OIFNOUFAgbmFtZSBzcGFjZS4mIzgyMjE7PG86cD48L286cD48L3NwYW4+PC9w
PjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVOLUdCPk9yLCB3ZSBjb3VsZCBqdXN0IGRl
bGV0ZSB0aGUgc2VudGVuY2UgJiM4MjIwO0luIHRoaXMgZG9jdW1lbnQsIHRoaXMgVEUgUm91dGVy
IEFkZHJlc3MgaXMgcmVmZXJyZWQgdG8gYXMgdGhlIFRFIFJvdXRlciBJRCwgd2hpY2ggaXMgaW4g
dGhlIEFTT04gU05QUCBuYW1lIHNwYWNlLiYjODIyMTsuPG86cD48L286cD48L3NwYW4+PC9wPjxw
IGNsYXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVOLUdCPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gbGFuZz1FTi1HQj5JbiBzZWN0aW9uIDQsIGZp
cnN0IHBhcmFncmFwaCwgcmVhY2hhYmlsaXR5IG9mIGVuZHBvaW50cyBpbiB0aGUgdHJhbnNwb3J0
IHBsYW5lIGlzIGRlc2NyaWJlZCBhcyBmb2xsb3dzOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBj
bGFzcz1Nc29Ob3JtYWw+PHNwYW4gbGFuZz1FTi1HQj4mcXVvdDtJbiBBU09OLCByZWFjaGFiaWxp
dHkgcmVmZXJzIHRvIHRoZSBzZXQgb2YgZW5kcG9pbnRzIHJlYWNoYWJsZSBpbiB0aGUgdHJhbnNw
b3J0IHBsYW5lIGJ5IGFuIGFzc29jaWF0ZWQgQVNPTiB0cmFuc3BvcnQgbm9kZS4mbmJzcDsgUmVh
Y2hhYmxlIGVudGl0aWVzIGFyZSBpZGVudGlmaWVkIGluIHRoZSBBU09OIFNDTiBuYW1lIHNwYWNl
LiZxdW90OyZuYnNwOyBBcyBkaXNjdXNzZWQgYWJvdmUsIG9ubHkgdGhlIGNvbnRyb2wgcGxhbmUg
Y29tcG9uZW50cyBhcmUgYWNjZXNzZWQgdGhyb3VnaCB0aGUgU0NOLCBub3QgdGhlIHRyYW5zcG9y
dCBub2RlcyB0aGVtc2VsdmVzLiZuYnNwOyBFbnRpdGllcyB0aGF0IGFyZSByZWFjaGFibGUgaW4g
dGhlIHRyYW5zcG9ydCBwbGFuZSBhcmUgaWRlbnRpZmllZCB0aHJvdWdoIEFTT04gU05QUHMgcmF0
aGVyIHRoYW4gQVNPTiBTQ04gYWRkcmVzc2VzLiZuYnNwOyBUaGVyZWZvcmUgSSBzdWdnZXN0IHJl
bW92aW5nIHRoZSBzZWNvbmQgc2VudGVuY2UgY29tcGxldGVseS48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tR0I+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVOLUdCPkZpbmFsbHksIGlu
IHNlY3Rpb24gNi4yLCBmaXJzdCBwYXJhZ3JhcGggZm9sbG93aW5nIHRoZSBmb3JtYXQgZGlhZ3Jh
bSwgaXQgaXMgc3RhdGVkOiZuYnNwOyAmcXVvdDtJZiBpdCBpcyBub3QgaW5jbHVkZWQgaW4gYSBO
b2RlIEF0dHJpYnV0ZSBUTFYgb3IgYSB2YWx1ZSBvZiAwIGlzIHNwZWNpZmllZCBmb3IgdGhlIExv
Y2FsIFRFIFJvdXRlciBJZGVudGlmaWVyLCB0aGUgTm90ZSBBdHRyaWJ1dGUgVExWIHdpbGwgbm90
IGJlIHVzZWQgZm9yIGRldGVybWluaW5nIEFTT04gU0NOIHJlYWNoYWJpbGl0eS4mcXVvdDsmbmJz
cDsgPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVO
LUdCPkFnYWluLCB0aGUgdGV4dCBzaG91bGQgYmUgZWRpdGVkIHRvIG1ha2UgdGhlIGRpc3RpbmN0
aW9uIGJldHdlZW4gdHJhbnNwb3J0IHBsYW5lIGFuZCBTQ04gY2xlYXJlciwgSSBzdWdnZXN0IG1v
ZGlmeWluZyB0aGUgc3RhdGVtZW50IHRvIHJlZmVyIHRvICZxdW90O0FTT04gcmVhY2hhYmlsaXR5
JnF1b3Q7IHJhdGhlciB0aGFuICZxdW90O0FTT04gU0NOIHJlYWNoYWJpbGl0eSZxdW90Oy4mbmJz
cDsgVGhlIHN0YXRlbWVudCB3b3VsZCByZWFkIGFzIGZvbGxvd3MgKGFsc28gY29ycmVjdGluZyB0
aGUgc3BlbGxpbmcgb2YgdGhlIFRMVik6PG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1z
b05vcm1hbD48c3BhbiBsYW5nPUVOLUdCPiZxdW90O0lmIGl0IGlzIG5vdCBpbmNsdWRlZCBpbiBh
IE5vZGUgQXR0cmlidXRlIFRMViBvciBhIHZhbHVlIG9mIDAgaXMgc3BlY2lmaWVkIGZvciB0aGUg
TG9jYWwgVEUgUm91dGVyIElkZW50aWZpZXIsIHRoZSBOb2RlIEF0dHJpYnV0ZSBUTFYgd2lsbCBu
b3QgYmUgdXNlZCBmb3IgZGV0ZXJtaW5pbmcgQVNPTiByZWFjaGFiaWxpdHkuJnF1b3Q7PG86cD48
L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD48c3BhbiBsYW5nPUVOLUdCPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+PHNwYW4gbGFu
Zz1FTi1HQj5TdGVwaGVuPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4
dD4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1Bs
YWluVGV4dD5Gcm9tOiA8YSBocmVmPSJtYWlsdG86aWV0Zi1hbm5vdW5jZS1ib3VuY2VzQGlldGYu
b3JnIj5pZXRmLWFubm91bmNlLWJvdW5jZXNAaWV0Zi5vcmc8L2E+IFs8YSBocmVmPSJtYWlsdG86
aWV0Zi1hbm5vdW5jZS1ib3VuY2VzQGlldGYub3JnIj5tYWlsdG86aWV0Zi1hbm5vdW5jZS1ib3Vu
Y2VzQGlldGYub3JnPC9hPl0gT24gQmVoYWxmIE9mIFRoZSBJRVNHPG86cD48L286cD48L3A+PHAg
Y2xhc3M9TXNvUGxhaW5UZXh0PlNlbnQ6IEZyaWRheSwgSnVseSAyMCwgMjAxMiAxMToxOSBBTTxv
OnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD5UbzogSUVURi1Bbm5vdW5jZTxvOnA+
PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD5DYzogPGEgaHJlZj0ibWFpbHRvOmNjYW1w
QGlldGYub3JnIj5jY2FtcEBpZXRmLm9yZzwvYT48bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Q
bGFpblRleHQ+U3ViamVjdDogTGFzdCBDYWxsOiAmbHQ7ZHJhZnQtaWV0Zi1jY2FtcC1yZmM1Nzg3
YmlzLTA1LnR4dCZndDsgKEFTT04gUm91dGluZyBmb3IgT1NQRnYyIFByb3RvY29scykgdG8gUHJv
cG9zZWQgU3RhbmRhcmQ8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+PG86cD4m
bmJzcDs8L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PjxvOnA+Jm5ic3A7PC9vOnA+PC9w
PjxwIGNsYXNzPU1zb1BsYWluVGV4dD5UaGUgSUVTRyBoYXMgcmVjZWl2ZWQgYSByZXF1ZXN0IGZy
b20gdGhlIENvbW1vbiBDb250cm9sIGFuZCBNZWFzdXJlbWVudCBQbGFuZSBXRyAoY2NhbXApIHRv
IGNvbnNpZGVyIHRoZSBmb2xsb3dpbmcgZG9jdW1lbnQ6PG86cD48L286cD48L3A+PHAgY2xhc3M9
TXNvUGxhaW5UZXh0Pi0gJ0FTT04gUm91dGluZyBmb3IgT1NQRnYyIFByb3RvY29scyc8bzpwPjwv
bzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jm5ic3A7ICZsdDtkcmFmdC1pZXRmLWNjYW1w
LXJmYzU3ODdiaXMtMDUudHh0Jmd0OyBhcyBQcm9wb3NlZCBTdGFuZGFyZDxvOnA+PC9vOnA+PC9w
PjxwIGNsYXNzPU1zb1BsYWluVGV4dD48bzpwPiZuYnNwOzwvbzpwPjwvcD48cCBjbGFzcz1Nc29Q
bGFpblRleHQ+VGhlIElFU0cgcGxhbnMgdG8gbWFrZSBhIGRlY2lzaW9uIGluIHRoZSBuZXh0IGZl
dyB3ZWVrcywgYW5kIHNvbGljaXRzIGZpbmFsIGNvbW1lbnRzIG9uIHRoaXMgYWN0aW9uLiBQbGVh
c2Ugc2VuZCBzdWJzdGFudGl2ZSBjb21tZW50cyB0byB0aGUgPGEgaHJlZj0ibWFpbHRvOmlldGZA
aWV0Zi5vcmciPmlldGZAaWV0Zi5vcmc8L2E+IG1haWxpbmcgbGlzdHMgYnkgMjAxMi0wOC0xNy4g
RXhjZXB0aW9uYWxseSwgY29tbWVudHMgbWF5IGJlIHNlbnQgdG8gPGEgaHJlZj0ibWFpbHRvOmll
c2dAaWV0Zi5vcmciPmllc2dAaWV0Zi5vcmc8L2E+IGluc3RlYWQuIEluIGVpdGhlciBjYXNlLCBw
bGVhc2UgcmV0YWluIHRoZSBiZWdpbm5pbmcgb2YgdGhlIFN1YmplY3QgbGluZSB0byBhbGxvdyBh
dXRvbWF0ZWQgc29ydGluZy4gVGhpcyBpcyBhIGZvdXItIHdlZWsgbGFzdCBjYWxsIHBlcmlvZCBi
ZWNhdXNlIGl0IHNwYW5zIHRoZSBJRVRGLTg0IG1lZXRpbmcuPG86cD48L286cD48L3A+PHAgY2xh
c3M9TXNvUGxhaW5UZXh0PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4
dD5BYnN0cmFjdDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD48bzpwPiZuYnNw
OzwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jm5ic3A7Jm5ic3A7IFRoZSBJVFUtVCBo
YXMgZGVmaW5lZCBhbiBhcmNoaXRlY3R1cmUgYW5kIHJlcXVpcmVtZW50cyBmb3Igb3BlcmF0aW5n
PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZuYnNwOyZuYnNwOyBhbiBBdXRv
bWF0aWNhbGx5IFN3aXRjaGVkIE9wdGljYWwgTmV0d29yayAoQVNPTikuPG86cD48L286cD48L3A+
PHAgY2xhc3M9TXNvUGxhaW5UZXh0PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1Bs
YWluVGV4dD4mbmJzcDsmbmJzcDsgVGhlIEdlbmVyYWxpemVkIE11bHRpcHJvdG9jb2wgTGFiZWwg
U3dpdGNoaW5nIChHTVBMUykgcHJvdG9jb2wgc3VpdGU8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1N
c29QbGFpblRleHQ+Jm5ic3A7Jm5ic3A7IGlzIGRlc2lnbmVkIHRvIHByb3ZpZGUgYSBjb250cm9s
IHBsYW5lIGZvciBhIHJhbmdlIG9mIG5ldHdvcms8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Q
bGFpblRleHQ+Jm5ic3A7Jm5ic3A7IHRlY2hub2xvZ2llcyBpbmNsdWRpbmcgb3B0aWNhbCBuZXR3
b3JrcyBzdWNoIGFzIHRpbWUgZGl2aXNpb248bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFp
blRleHQ+Jm5ic3A7Jm5ic3A7IG11bHRpcGxleGluZyAoVERNKSBuZXR3b3JrcyBpbmNsdWRpbmcg
U09ORVQvU0RIIGFuZCBPcHRpY2FsIFRyYW5zcG9ydDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1z
b1BsYWluVGV4dD4mbmJzcDsmbmJzcDsgTmV0d29ya3MgKE9UTnMpLCBhbmQgbGFtYmRhIHN3aXRj
aGluZyBvcHRpY2FsIG5ldHdvcmtzLjxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4
dD48bzpwPiZuYnNwOzwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+Jm5ic3A7Jm5ic3A7
IFRoZSByZXF1aXJlbWVudHMgZm9yIEdNUExTIHJvdXRpbmcgdG8gc2F0aXNmeSB0aGUgcmVxdWly
ZW1lbnRzIG9mPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZuYnNwOyZuYnNw
OyBBU09OIHJvdXRpbmcsIGFuZCBhbiBldmFsdWF0aW9uIG9mIGV4aXN0aW5nIEdNUExTIHJvdXRp
bmcgcHJvdG9jb2xzPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZuYnNwOyZu
YnNwOyBhcmUgcHJvdmlkZWQgaW4gb3RoZXIgZG9jdW1lbnRzLiZuYnNwOyBUaGlzIGRvY3VtZW50
IGRlZmluZXMgZXh0ZW5zaW9ucyB0bzxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4
dD4mbmJzcDsmbmJzcDsgdGhlIE9TUEZ2MiBMaW5rIFN0YXRlIFJvdXRpbmcgUHJvdG9jb2wgdG8g
bWVldCB0aGUgcmVxdWlyZW1lbnRzIGZvcjxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWlu
VGV4dD4mbmJzcDsmbmJzcDsgcm91dGluZyBpbiBhbiBBU09OLjxvOnA+PC9vOnA+PC9wPjxwIGNs
YXNzPU1zb1BsYWluVGV4dD48bzpwPiZuYnNwOzwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRl
eHQ+Jm5ic3A7Jm5ic3A7IE5vdGUgdGhhdCB0aGlzIHdvcmsgaXMgc2NvcGVkIHRvIHRoZSByZXF1
aXJlbWVudHMgYW5kIGV2YWx1YXRpb248bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRl
eHQ+Jm5ic3A7Jm5ic3A7IGV4cHJlc3NlZCBpbiBSRkMgNDI1OCBhbmQgUkZDIDQ2NTIgYW5kIHRo
ZSBJVFUtVCBSZWNvbW1lbmRhdGlvbnM8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRl
eHQ+Jm5ic3A7Jm5ic3A7IGN1cnJlbnQgd2hlbiB0aG9zZSBkb2N1bWVudHMgd2VyZSB3cml0dGVu
LiZuYnNwOyBGdXR1cmUgZXh0ZW5zaW9ucyBvZjxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1Bs
YWluVGV4dD4mbmJzcDsmbmJzcDsgcmV2aXNpb25zIG9mIHRoaXMgd29yayBtYXkgYmUgbmVjZXNz
YXJ5IGlmIHRoZSBJVFUtVCBSZWNvbW1lbmRhdGlvbnM8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1N
c29QbGFpblRleHQ+Jm5ic3A7Jm5ic3A7IGFyZSByZXZpc2VkIG9yIGlmIG5ldyByZXF1aXJlbWVu
dHMgYXJlIGludHJvZHVjZWQgaW50byBhIHJldmlzaW9uIG9mPG86cD48L286cD48L3A+PHAgY2xh
c3M9TXNvUGxhaW5UZXh0PiZuYnNwOyZuYnNwOyBSRkMgNDI1OC4gVGhpcyBkb2N1bWVudCBvYnNv
bGV0ZXMgUkZDIDU3ODcgYW5kIHVwZGF0ZXMgUkZDIDU3ODYuPG86cD48L286cD48L3A+PHAgY2xh
c3M9TXNvUGxhaW5UZXh0PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4
dD48bzpwPiZuYnNwOzwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+PG86cD4mbmJzcDs8
L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PlRoZSBmaWxlIGNhbiBiZSBvYnRhaW5lZCB2
aWE8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRleHQ+PGEgaHJlZj0iaHR0cDovL2Rh
dGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLWNjYW1wLXJmYzU3ODdiaXMvIj5odHRw
Oi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtY2NhbXAtcmZjNTc4N2Jpcy88
L2E+PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD5JRVNHIGRpc2N1c3Npb24gY2FuIGJlIHRyYWNrZWQg
dmlhPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0PjxhIGhyZWY9Imh0dHA6Ly9k
YXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1jY2FtcC1yZmM1Nzg3YmlzL2JhbGxv
dC8iPmh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1jY2FtcC1yZmM1
Nzg3YmlzL2JhbGxvdC88L2E+PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0Pjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPjxwIGNsYXNzPU1zb1BsYWluVGV4dD5ObyBJUFIgZGVjbGFyYXRp
b25zIGhhdmUgYmVlbiBzdWJtaXR0ZWQgZGlyZWN0bHkgb24gdGhpcyBJLUQuPG86cD48L286cD48
L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LWZhbWlseToiVGltZXMgTmV3
IFJvbWFuIiwic2VyaWYiO2NvbG9yOiMxRjQ5N0QnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtZmFtaWx5OiJUaW1lcyBOZXcg
Um9tYW4iLCJzZXJpZiI7Y29sb3I6IzFGNDk3RCc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
PjxwIGNsYXNzPU1zb05vcm1hbD48Yj48c3BhbiBzdHlsZT0nZm9udC1zaXplOjcuNXB0O2ZvbnQt
ZmFtaWx5OiJBcmlhbCIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPlN0ZXBoZW4gU2hldzwv
c3Bhbj48L2I+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZTo3LjVwdDtmb250LWZhbWlseToiQXJpYWwi
LCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz4mbmJzcDs8L3NwYW4+PHNwYW4gc3R5bGU9J2Zv
bnQtc2l6ZTo3LjVwdDtmb250LWZhbWlseToiQXJpYWwiLCJzYW5zLXNlcmlmIjtjb2xvcjpyZWQn
Pnw8L3NwYW4+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZTo3LjVwdDtmb250LWZhbWlseToiQXJpYWwi
LCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz4gPC9zcGFuPjxzcGFuIHN0eWxlPSdmb250LXNp
emU6Ny41cHQ7Zm9udC1mYW1pbHk6IkFyaWFsIiwic2Fucy1zZXJpZiI7Y29sb3I6Z3JheSc+RGly
ZWN0b3IsIFN0YW5kYXJkczwvc3Bhbj48c3BhbiBzdHlsZT0nZm9udC1zaXplOjcuNXB0O2ZvbnQt
ZmFtaWx5OiJBcmlhbCIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPjxicj48L3NwYW4+PHU+
PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZTo3LjVwdDtmb250LWZhbWlseToiQXJpYWwiLCJzYW5zLXNl
cmlmIjtjb2xvcjpibHVlJz48YSBocmVmPSJtYWlsdG86amRvZUBjaWVuYS5jb20iPjxzcGFuIHN0
eWxlPSdjb2xvcjpibHVlJz5zc2hld0BjaWVuYS5jb208L3NwYW4+PC9hPjwvc3Bhbj48L3U+PHNw
YW4gc3R5bGU9J2ZvbnQtc2l6ZTo3LjVwdDtmb250LWZhbWlseToiQXJpYWwiLCJzYW5zLXNlcmlm
Ijtjb2xvcjojMUY0OTdEJz4gPC9zcGFuPjxzcGFuIHN0eWxlPSdmb250LXNpemU6Ny41cHQ7Zm9u
dC1mYW1pbHk6IkFyaWFsIiwic2Fucy1zZXJpZiI7Y29sb3I6cmVkJz58PC9zcGFuPjxzcGFuIHN0
eWxlPSdmb250LXNpemU6Ny41cHQ7Zm9udC1mYW1pbHk6IkFyaWFsIiwic2Fucy1zZXJpZiI7Y29s
b3I6cHVycGxlJz4gPC9zcGFuPjxzcGFuIHN0eWxlPSdmb250LXNpemU6Ny41cHQ7Zm9udC1mYW1p
bHk6IkFyaWFsIiwic2Fucy1zZXJpZiI7Y29sb3I6Z3JheSc+MzUwMCBDYXJsaW5nIEF2ZS4gPC9z
cGFuPjxzcGFuIHN0eWxlPSdmb250LXNpemU6Ny41cHQ7Zm9udC1mYW1pbHk6IkFyaWFsIiwic2Fu
cy1zZXJpZiI7Y29sb3I6cmVkJz58PC9zcGFuPjxzcGFuIHN0eWxlPSdmb250LXNpemU6Ny41cHQ7
Zm9udC1mYW1pbHk6IkFyaWFsIiwic2Fucy1zZXJpZiI7Y29sb3I6cHVycGxlJz4mbmJzcDs8L3Nw
YW4+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZTo3LjVwdDtmb250LWZhbWlseToiQXJpYWwiLCJzYW5z
LXNlcmlmIjtjb2xvcjpncmF5Jz5PdHRhd2EgQ0FOQURBIEsySCA4RTk8YnI+RGlyZWN0ICsxLjYx
My42NzAuMzIxMTxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PG86cD4m
bmJzcDs8L286cD48L3A+PC9kaXY+PC9ib2R5PjwvaHRtbD4=

--_000_510C3D5C5DFBCB46AE189D936C1DD605A5FDBBD408ONWVEXCHMB02c_--

From ole@cisco.com  Mon Aug 20 10:12:23 2012
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EB6021F84D8 for <ietf@ietfa.amsl.com>; Mon, 20 Aug 2012 10:12:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.553
X-Spam-Level: 
X-Spam-Status: No, score=-110.553 tagged_above=-999 required=5 tests=[AWL=0.046, 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 gBFhLsvSW5II for <ietf@ietfa.amsl.com>; Mon, 20 Aug 2012 10:12:22 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id C3DCC21F84C9 for <ietf@ietf.org>; Mon, 20 Aug 2012 10:12:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=1783; q=dns/txt; s=iport; t=1345482742; x=1346692342; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=FjX022kfgjFGdGAWxOns35+asJDZwQvIp3DQNoAuN7k=; b=bviI1x3xVI39LdUNmp/c4sI/VHLgT/aQ0DHBakb6SzfS9+PL7tF7U4h4 DCSvAGAzeXRGlZH3pY2+RYJz3GoV3atKmp+tTE2EaUQN1ETc9P9ZMGGye WVdTKYH0WUmZ+OqS9E0Xb2G13XXrzWpIgmKHBHigo9Wq+zfV885phrriM w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAGhuMlCrRDoI/2dsb2JhbABCA7pZgQeCIAEBAQMBEgECJS4DDgULC0ZXBhMUDodlBZkHg0cQnDaLCxqDV4MhA4hPki8uhTODHYEEYoMBgUE
X-IronPort-AV: E=Sophos;i="4.77,798,1336348800"; d="scan'208";a="55589795"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-2.cisco.com with ESMTP; 20 Aug 2012 17:12:21 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q7KHCKYb030751 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Aug 2012 17:12:21 GMT
Date: Mon, 20 Aug 2012 10:12:20 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Subject: Re: IETF 92 in Dallas!
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A1E35@DC-US1MBEX4.global.avaya.com>
Message-ID: <alpine.OSX.2.01.1208200958580.4526@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net> <BA2EE8F7-92C8-4F10-B10A-2B6FE4FC954A@gmail.com> <502E9614.30409@raszuk.net> <502E9841.8070205@bogus.com> <502E9982.5080909@raszuk.net> <502F4A2A.8090005@krsek.cz> <CD5674C3CD99574EBA7432465FC13C1B22726A1E35@DC-US1MBEX4.global.avaya.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Aug 2012 17:12:23 -0000

Dale,

We actually like to have a little fun with it. At the World IAOC 
Headquarters (WIAOCH) we have a huge world map and a set of darts.

After having some drinks to put us in the right mood, we start
tossing darts at the wall and rolling specially designed dice where 
each face has logos and names such as "Hilton," "Starwood," "Hyatt,"
"Marriott," "Fairmont," and "Low Rent." Our designated driver tries
to keep track of it all, and at the end of the meeting we dispatch
a randomly selected set of our friends to do "site visits." They are
expected to report back to us with useful information such as "the
in-room Internet sucked and was expensive," but in reality our 
selection relies more on the use of game theory and chance (hence
the dice). We tried once to pick a location with the longest train
ride, but the community didn't seem to like it...

We also sometimes write protocol specs, just to keep up with the rest
of you.

Ole

:-)


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Mon, 20 Aug 2012, Worley, Dale R (Dale) wrote:

> We are paid well to design protocols because designing protocols that
> work well in practice is a tricky art that is best practiced by experts
> in the field.
> 
> But negotiating all the arrangements for a complex technical conference
> is a straightforward matter of comparing the published room rates of
> various hotels and can be successfully accomplished by any literate
> person who takes an interest in doing it.
> 
> Now I'm off to do my own dental work.  That left molar has been
> bothering me...
> 
> Dale
> 
> 

From glenzorn@gmail.com  Mon Aug 20 21:51:51 2012
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0BE121F8578 for <ietf@ietfa.amsl.com>; Mon, 20 Aug 2012 21:51:51 -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 s-izI6y5yuRO for <ietf@ietfa.amsl.com>; Mon, 20 Aug 2012 21:51: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 302D421F8577 for <ietf@ietf.org>; Mon, 20 Aug 2012 21:51:51 -0700 (PDT)
Received: by iabz21 with SMTP id z21so3642244iab.31 for <ietf@ietf.org>; Mon, 20 Aug 2012 21:51:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=1ZstBUnavIQ6dOsmKGtFBnUXFRP1h7BzlLVYmVLyaJw=; b=xAHdv0pyM+KaFMCOLuLR59VhGOW572G/q3fJMStwnqpe7geEGauh7mu6pcQbNNwL8b XHwRxecYOTY5ZEufsJx+PnWkh3j8eE0JzYRLgRZuBtgjKarj0U/kFa/2ylmTIhR5AFBs 52+QahyEFYe1PUuXcdSOAP70uu86ot+N69vQydArbApEats37deNlLWKVw4g4uacM0ly aeioz4vWZp7VoXLce4NT698M4t3SGaJz4InYwLhZGIKL7RRc8mzAy6FEnIsy1a0rIgwB ptyRtslqFUfary6cciQP4u9e+ohbK2M9WEhZGGZyfJ6sxCOSsUPbBNFeO3i3ZhbEhVdU Zrxw==
Received: by 10.50.195.164 with SMTP id if4mr7956006igc.20.1345524710550; Mon, 20 Aug 2012 21:51:50 -0700 (PDT)
Received: from [192.168.0.102] (ppp-124-120-193-30.revip2.asianet.co.th. [124.120.193.30]) by mx.google.com with ESMTPS id gx1sm790928igb.16.2012.08.20.21.51.46 (version=SSLv3 cipher=OTHER); Mon, 20 Aug 2012 21:51:49 -0700 (PDT)
Message-ID: <503313DE.4090401@gmail.com>
Date: Tue, 21 Aug 2012 11:51:42 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120721 Thunderbird/14.0
MIME-Version: 1.0
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Subject: Re: IETF 92 in Dallas!
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net> <BA2EE8F7-92C8-4F10-B10A-2B6FE4FC954A@gmail.com> <502E9614.30409@raszuk.net> <502E9841.8070205@bogus.com> <502E9982.5080909@raszuk.net> <502F4A2A.8090005@krsek.cz> <CD5674C3CD99574EBA7432465FC13C1B22726A1E35@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A1E35@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2012 04:51:51 -0000

On 08/20/2012 09:29 PM, Worley, Dale R (Dale) wrote:
> We are paid well to design protocols because designing protocols that
> work well in practice is a tricky art that is best practiced by experts
> in the field.
>
> But negotiating all the arrangements for a complex technical conference
> is a straightforward matter of comparing the published room rates of
> various hotels and can be successfully accomplished by any literate
> person who takes an interest in doing it.

And that's undoubtedly why the IAOC is packed with professional meeting 
organizers!

>
> Now I'm off to do my own dental work.  That left molar has been
> bothering me...

Why not go to the IAOC?

>
> Dale
>


From ole@cisco.com  Mon Aug 20 23:27:49 2012
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A096611E80EE for <ietf@ietfa.amsl.com>; Mon, 20 Aug 2012 23:27:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SHLZoi5X3Jpq for <ietf@ietfa.amsl.com>; Mon, 20 Aug 2012 23:27:48 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id BE9BD11E80E7 for <ietf@ietf.org>; Mon, 20 Aug 2012 23:27:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=1099; q=dns/txt; s=iport; t=1345530468; x=1346740068; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=KekpMo617EG53RwPhNih4cOiD0Bgp77qFPpFszQgUrc=; b=FWGQcrrwwrNzdY2Kc19wqWgOM3D//9nOVGOKAQm4FskuBwhXHbOW34MQ dZOuKS/YlIz80POllb3xFMnvs2nyUVpsX3W1siw7D9YTOtnGZYxmdU3MD Aa2Zm67Vnp1rDXBPJqc1IbJryoCdk6b1CEp8DoTWb6QoHeDSkAL9boLxc 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAHIpM1CtJV2d/2dsb2JhbABFulyBB4IgAQEBAwESAScuAw4FCwIBCBgeECERJQIEDgUih1wDBgaZBZZZDYlOiidkhjxgA5N9gVOBFIl4A4MdgWaCYQ
X-IronPort-AV: E=Sophos;i="4.77,801,1336348800"; d="scan'208";a="113429598"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-1.cisco.com with ESMTP; 21 Aug 2012 06:27:48 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id q7L6RlFD006946 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 21 Aug 2012 06:27:48 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.98]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.02.0298.004; Tue, 21 Aug 2012 01:27:47 -0500
From: "Ole Jacobsen (ole)" <ole@cisco.com>
To: Glen Zorn <glenzorn@gmail.com>
Subject: Re: IETF 92 in Dallas!
Thread-Topic: IETF 92 in Dallas!
Thread-Index: AQHNf1io8Gg6XHcnPkiA5YlMcE9mMJdjzXdj
Date: Tue, 21 Aug 2012 06:27:46 +0000
Message-ID: <ACAEC3CC-7C9D-4D7C-91B0-B111AB35980E@cisco.com>
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net> <BA2EE8F7-92C8-4F10-B10A-2B6FE4FC954A@gmail.com>	<502E9614.30409@raszuk.net> <502E9841.8070205@bogus.com>	<502E9982.5080909@raszuk.net> <502F4A2A.8090005@krsek.cz> <CD5674C3CD99574EBA7432465FC13C1B22726A1E35@DC-US1MBEX4.global.avaya.com>, <503313DE.4090401@gmail.com>
In-Reply-To: <503313DE.4090401@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19128.004
x-tm-as-result: No--40.358000-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
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, 21 Aug 2012 06:27:49 -0000

Glen,

Maybe you've missed the fact that the IAOC has a rather excellent contracto=
r that does meeting planning for a living?

Maybe you prefer my darts version, oh well :-)

Ole J. Jacobsen
Editor & Publisher
http://cisco.com/ipj

Sent from my iPhone

On 21 Aug 2012, at 06:52, "Glen Zorn" <glenzorn@gmail.com> wrote:

> On 08/20/2012 09:29 PM, Worley, Dale R (Dale) wrote:
>> We are paid well to design protocols because designing protocols that
>> work well in practice is a tricky art that is best practiced by experts
>> in the field.
>>=20
>> But negotiating all the arrangements for a complex technical conference
>> is a straightforward matter of comparing the published room rates of
>> various hotels and can be successfully accomplished by any literate
>> person who takes an interest in doing it.
>=20
> And that's undoubtedly why the IAOC is packed with professional meeting o=
rganizers!
>=20
>>=20
>> Now I'm off to do my own dental work.  That left molar has been
>> bothering me...
>=20
> Why not go to the IAOC?
>=20
>>=20
>> Dale
>>=20
>=20

From randy@psg.com  Mon Aug 20 23:37:16 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E307811E80EF for <ietf@ietfa.amsl.com>; Mon, 20 Aug 2012 23:37:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level: 
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[AWL=0.049,  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 U3TyEduEC4p8 for <ietf@ietfa.amsl.com>; Mon, 20 Aug 2012 23:37:16 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 7CA6211E80E7 for <ietf@ietf.org>; Mon, 20 Aug 2012 23:37:16 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80 (FreeBSD)) (envelope-from <randy@psg.com>) id 1T3i5S-00028n-SK; Tue, 21 Aug 2012 06:37:15 +0000
Date: Tue, 21 Aug 2012 15:37:34 +0900
Message-ID: <m2txvwoimp.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Glen Zorn <glenzorn@gmail.com>
Subject: Re: IETF 92 in Dallas!
In-Reply-To: <503313DE.4090401@gmail.com>
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net> <BA2EE8F7-92C8-4F10-B10A-2B6FE4FC954A@gmail.com> <502E9614.30409@raszuk.net> <502E9841.8070205@bogus.com> <502E9982.5080909@raszuk.net> <502F4A2A.8090005@krsek.cz> <CD5674C3CD99574EBA7432465FC13C1B22726A1E35@DC-US1MBEX4.global.avaya.com> <503313DE.4090401@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2012 06:37:17 -0000

> And that's undoubtedly why the IAOC is packed with professional
> meeting organizers!

looks to me as if the iaoc knows what they do not know and have the
sense to contract it out to pros.  unlike the amateurs on list who have
never organized a medium-sized meeting such as the ietf in their lives
but can tell everyone else how to do it.

sorry, but enough is enough.

randy

From sm@resistor.net  Tue Aug 21 00:58:07 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DC3E21F86B7 for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 00:58:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.489
X-Spam-Level: 
X-Spam-Status: No, score=-102.489 tagged_above=-999 required=5 tests=[AWL=0.110, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p9DPc71Uuu2I for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 00:58:07 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D11E21F86B4 for <ietf@ietf.org>; Tue, 21 Aug 2012 00:58:07 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q7L7vr38026567; Tue, 21 Aug 2012 00:57:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1345535878; bh=TqoXE5y/Uf2xmCwo/9ZezsGZwEYJ0PbP7LEhp/5FDcc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=SqEK22nBIgDikQq76wgRrNEy39LU4cuAeBoYjF1nWntUhlsDbE0M/ZmYcrpozSNJ5 rhlLgB1lalijqunqHKX0sE6UVBhNKOz8I3IYeLD2KDwVwNdt9QWhdXodgJDCdF8eVF XnF88XlI4D/jQeF9zeGGiIYpPwdUkCTcBzFbaoD4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1345535878; i=@resistor.net; bh=TqoXE5y/Uf2xmCwo/9ZezsGZwEYJ0PbP7LEhp/5FDcc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=W0IqC8ndricauT6aTRTRlMIHbzbnH4IzYiKGuyu+fwYzfNz66R+7wceG50YW7WW0T SqEgnxuP2dOX8JkblrZv0KzMDRgDTLH9ZAY9hykkOB86fTOrABh0IwH0BJUsdhozpW LSG7gX9cnf8UL2IhK93oHMLrE2H+zCYokBHVN4mg=
Message-Id: <6.2.5.6.2.20120821002309.092cacf0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 21 Aug 2012 00:56:42 -0700
To: Lixia Zhang <lixia@cs.ucla.edu>
From: SM <sm@resistor.net>
Subject: One sentence
In-Reply-To: <7A75A5D6-869F-4C19-9044-006CB9930AE4@cs.ucla.edu>
References: <u2b8y2x43qn1esn7ege163mo.1344689258582@email.android.com> <50266F05.5050601@dcrocker.net> <1C6BB491-8B0B-4432-B633-6D8AA3B6477E@tzi.org> <50267826.70307@bbiw.net> <CAC4RtVARm1fXvHR4dv9Jh0HttW+ORhRx36kwF54RRjc4aOh1AQ@mail.gmail.com> <5027D0B2.80306@bbiw.net> <CALaySJKzxo=oHLcDxT=RbrwMK=pTSh6vxY-VvLZ0C5wf+T-DQQ@mail.gmail.com> <5027D67B.2030409@dcrocker.net> <5027ED27.2040403@cisco.com> <7A75A5D6-869F-4C19-9044-006CB9930AE4@cs.ucla.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2012 07:58:07 -0000

Hi Lixia,
At 15:34 12-08-2012, Lixia Zhang wrote:
>Personally I do not feel the tone of this message is most 
>appropriate in this ongoing discussion.

That one sentence shines on your character.  :-)

Regards,
-sm 


From adrian@olddog.co.uk  Tue Aug 21 03:10:37 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FE4A21F868A for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 03:10:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.52
X-Spam-Level: 
X-Spam-Status: No, score=-2.52 tagged_above=-999 required=5 tests=[AWL=0.079,  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 KQSv-1+K2tKn for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 03:10:36 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 2F25021F8683 for <ietf@ietf.org>; Tue, 21 Aug 2012 03:10:34 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7LAAXJR030884;  Tue, 21 Aug 2012 11:10:33 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7LAAW6q030862 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 21 Aug 2012 11:10:32 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <draft-leiba-3777upd-eligibility@tools.ietf.org>
Subject: Some thoughts about draft-leiba-3777upd-eligibility-02.txt
Date: Tue, 21 Aug 2012 11:10:30 +0100
Message-ID: <133201cd7f85$325f59a0$971e0ce0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac1/hMt6iLJeQqv5TyC6GSGTm7xwLA==
Content-Language: en-gb
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2012 10:10:37 -0000

Hi,

I have one discussion point and a number of small nits...

Cheers,
Adrian

---

Discussion point.

The Abstract makes it clear that the purpose of the document is to
handle the (new) IAOC and to resolve uncertainty about liaisons and
ex-officio members of the IAB, IESG, and IAOC.

This seems reasonable to me.

However, the document very quickly launches into a discussion of other
people to exclude from NomCom. It does this by introducing the concept
of a "conflict of interest." There may be a valid debate to have about
conflict of interest, but I personally find it a very long wedge, and
although there may be clear-cut cases at either extreme, it is by no
means clear where to draw the line.

I find the excuse used (that those excluded are unlikely to volunteer)
as rather poor taste. It may be true that such people have not 
volunteered in the past, but that should not be used as a reason. You
are removing rights that people previously had - you should have good,
stand-alone reasons and not depend on whether or not earlier holders of
certain posts exercised those rights.
                                                                         
So:

1. Since I think that CoI is a label on a really nasty box you don't
   want to open, I would prefer you to not use the term. You do
   perfectly well when you say:
     This document also excludes certain individuals who are directly
     paid for their work with the IETF...
   I think you can leave it at that.

2. Please align the Abstract and the content by updating the Abstract
   to mention exclusion of paid individuals.

3. Please don't lean on RFC 3777 for the introduction of CoI to this
   document (you do this in Section 1). RFC 3777 does not use the term
   and does not appear to have any text that is related to the concept.
   If you believe there is good reason to exclude volunteers from
   NomCom, you should make that case in this document.
                    
4. Remove the commentary on whether those excluded are or are not
   likely to volunteer.

---

Section 1 (petty)
OLD
   The selection of the NomCom, therefore, excludes those individuals
   who are in top leadership positions currently.
NEW
   The selection of the NomCom, therefore, excludes those individuals
   who are in top leadership positions at the time of selection.
END

The point being that it is not those in the positions on 8/18/12 who
are excluded.

---

Section 1 (punctuation)
   RFC 3777 specifies that "sitting members" of the IAB and IESG "may
   not volunteer to serve on the nominating committee".  Since that
   document was written the IETF Administrative Oversight Committee
   (IAOC) was formed, and that body is not covered by RFC 3777.  There
   is also uncertainty about whether ex-officio members liaisons, and
   such are included as "sitting members".     
s/members liaisons/members, liaisons/

---

Section 1 (tone)

OLD
   This document also excludes certain individuals who are directly paid
   for their work with the IETF, and who, therefore, have a direct
   personal financial incentive in the selection of the leadership
   boards.
NEW
   This document also excludes certain individuals who are directly paid
   for their work with the IETF, and who, therefore, might have a direct
   personal financial incentive in the selection of the leadership
   boards.
END

Let us not assume that the system is completely corrupt!

---
                                       
Section 2 (editorial)

The section title is wrong.

You probably need "Changes to RFC 37777"

Then you have:
OLD
   This document makes the following updates to
   add the IAOC to certain of the processes that are not covered there.
NEW
   This document makes the following updates to
   add the IAOC to certain of the processes, and to introduce other small
   process changes as described in Section 1.
END

...and delete

   Note that the change below to Section 4, bullet 15 also puts
   additional restrictions on who may volunteer as a voting member of
   the NomCom.

---

      15.2.  People serving in the IETF Secretariat and the RFC Editor
           may not volunteer to serve as voting members of the
           nominating committee.

Slight problem with the term "RFC Editor" since this is a single person
and also a service function. I suspect you mean the latter.

---

   o  In bullet 16, to correct an erratum, the last paragraph is
      replaced by this:

         One possible selection method is described in RFC 3797 [1].

Perfectly correct, but I don't think this document is the place to
correct random errata.


From david.black@emc.com  Mon Aug 20 18:58:09 2012
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF8F121F84A2; Mon, 20 Aug 2012 18:58:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.49
X-Spam-Level: 
X-Spam-Status: No, score=-102.49 tagged_above=-999 required=5 tests=[AWL=0.108, 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 KGC+ce3XGNYy; Mon, 20 Aug 2012 18:58:09 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 2C00821F84A1; Mon, 20 Aug 2012 18:58:08 -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 q7L1w39m000583 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Aug 2012 21:58:05 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.145]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Mon, 20 Aug 2012 21:57:47 -0400
Received: from mxhub23.corp.emc.com (mxhub23.corp.emc.com [128.222.70.135]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q7L1vkwO021339; Mon, 20 Aug 2012 21:57:47 -0400
Received: from mx15a.corp.emc.com ([169.254.1.66]) by mxhub23.corp.emc.com ([128.222.70.135]) with mapi; Mon, 20 Aug 2012 21:57:46 -0400
From: "Black, David" <david.black@emc.com>
To: "dinmohan@hotmail.com" <dinmohan@hotmail.com>, "nabil.n.bitar@verizon.com" <nabil.n.bitar@verizon.com>, "sajassi@cisco.com" <sajassi@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Content-Class: urn:content-classes:message
Date: Mon, 20 Aug 2012 21:57:44 -0400
Subject: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
Thread-Topic: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
Thread-Index: Ac1/QFqQF9gPSsZLRYeNSY3JGwq32g==
Message-ID: <7EB1738E-2545-4A33-B5C0-548630347568@mimectl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mimectl: Produced By Microsoft Exchange V8.3.105.0
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_7EB1738E25454A33B5C0548630347568mimectl_"
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Tue, 21 Aug 2012 08:08:15 -0700
Cc: "Black, David" <david.black@emc.com>, "pwe3@ietf.org" <pwe3@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, 21 Aug 2012 01:58:10 -0000

--_000_7EB1738E25454A33B5C0548630347568mimectl_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

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 resolve these comments along with any other Last Call comments you m=
ay receive.

Document: draft-ietf-pwe3-mpls-eth-oam-iwk-06
Reviewer: David L. Black
Review Date: August 20, 2012
IETF LC End Date: August 20, 2012

Summary:
This draft is basically ready for publication, but has nits that
should be fixed before publication.



This draft covers defect behavior for Ethernet pseudowires,

including defect state mapping and PE defect reporting behavior.

The draft is generally in good shape.  I found a few minor nits.



1) The draft uses a lot of acronyms - while each acronym appears to

be expanded on first use, an additional section near the start of the

draft listing all of them would be helpful.



2) There's a typo in the first paragraph of section 2:



     covers the following Ethernet OAM (Opertaions, Administration and



Opertaions -> Operations.



3) The following normative reference is incomplete - please add additional

information that will enable a reader to locate the referenced document:



     [MEF16] "Ethernet Local Management Interface", MEF16, January 2006.



4) idnits 2.12.13 did not like the pagination:



  =3D=3D The page length should not exceed 58 lines per page, but there was=
 22
     longer pages, the longest (page 1) being 61 lines


Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
david.black@emc.com<mailto:david.black@emc.com>        Mobile: +1 (978) 394=
-7754
----------------------------------------------------

--_000_7EB1738E25454A33B5C0548630347568mimectl_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD>
<STYLE title=3DowaParaStyle><!--P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></STYLE>
</HEAD>
<BODY ocsi=3D"x">
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 face=3D"Courier New">I am the=
 assigned Gen-ART reviewer for this draft. For background on Gen-ART, pleas=
e<BR>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/w=
iki/GenArtfaq</A>&gt;.<BR><BR>Please resolve these comments along with any =
other Last Call comments you may receive.<BR><BR>Document: <SPAN lang=3DEN>=
draft-ietf-pwe3-mpls-eth-oam-iwk-06</SPAN></FONT></DIV>
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 face=3D"Courier New"><SPAN la=
ng=3DEN></SPAN>Reviewer: David L. Black<BR>Review Date: August 20, 2012<BR>=
IETF LC End Date: August 20, 2012<BR><BR>Summary:<BR>This draft is basicall=
y ready for publication, but has nits that<BR>should be fixed before public=
ation.</FONT></DIV>
<P><FONT color=3D#000000 size=3D2 face=3D"Courier New"><FONT face=3D"courie=
r new"></FONT></FONT>&nbsp;</P>
<P><FONT color=3D#000000 size=3D2 face=3D"Courier New"><FONT face=3D"courie=
r new">This draft covers defect behavior for Ethernet pseudowires<A target=
=3D_blank></A>,</FONT></FONT></P>
<P><FONT color=3D#000000 size=3D2 face=3D"Courier New"><FONT face=3D"courie=
r new">including defect state mapping and PE defect reporting behavior.</FO=
NT></FONT></P>
<P><FONT color=3D#000000 size=3D2 face=3D"Courier New"><FONT face=3D"courie=
r new">The draft is generally in good shape.&nbsp; I found a few minor nits=
.</FONT></FONT></P>
<P><FONT size=3D2 face=3D"courier new"></FONT>&nbsp;</P>
<P><FONT size=3D2 face=3D"courier new">1) The draft uses a lot of acronyms =
- while each acronym appears to</FONT></P>
<P><FONT size=3D2 face=3D"Courier New">b<FONT face=3D"courier new">e expand=
ed on first use, an additional section near the start of the</FONT></FONT><=
/P>
<P><FONT face=3D"Courier New"><FONT face=3D"courier new"><FONT size=3D2><FO=
NT face=3D"courier new">draft listing</FONT> all of them </FONT></FONT></FO=
NT><FONT size=3D2 face=3D"courier new">would be helpful.</FONT></P>
<P><FONT size=3D2 face=3D"courier new"></FONT>&nbsp;</P>
<P><FONT size=3D2 face=3D"courier new">2) There's&nbsp;a typo in the first =
paragraph of section 2:</FONT></P>
<P><FONT size=3D2 face=3D"courier new"></FONT>&nbsp;</P><FONT color=3D#0000=
00>
<DIV dir=3Dltr><FONT size=3D2><SPAN lang=3DEN>
<P><FONT face=3D"Courier New">&nbsp;&nbsp;&nbsp; &nbsp;covers the following=
 Ethernet OAM (Opertaions<A target=3D_blank></A>, Administration and </FONT=
></P>
<P><FONT face=3D"courier new"></FONT>&nbsp;</P>
<P><FONT face=3D"courier new"><A target=3D_blank></A><FONT face=3D"courier =
new">Opertaions</FONT>&nbsp;-&gt; Operations.</FONT></P>
<P><FONT face=3D"courier new"></FONT>&nbsp;</P>
<P><FONT face=3D"courier new">3) The following normative reference is incom=
plete - please add additional</FONT></P>
<P><FONT face=3D"courier new">information that will enable a reader to loca=
te the referenced document:</FONT></P>
<P><FONT face=3D"courier new"></FONT>&nbsp;</P><FONT face=3D"courier new"><=
SPAN lang=3DEN>
<P>&nbsp;&nbsp;&nbsp; &nbsp;[MEF16] "Ethernet Local Management Interface", =
MEF16, January 2006.</P>
<P><FONT face=3D"courier new"></FONT>&nbsp;</P>
<P><FONT face=3D"courier new"><FONT face=3D"courier new">4)&nbsp;idnits<A t=
arget=3D_blank></A> 2.12.13 did not like the pagination:</FONT></FONT></P>
<P>&nbsp;</P>
<P><FONT face=3D"courier new">&nbsp; =3D=3D The page length should not exce=
ed 58 lines per page, but there was 22<BR>&nbsp;&nbsp;&nbsp;&nbsp; longer p=
ages, the longest (page 1) being 61 lines</FONT></SPAN></FONT></SPAN></FONT=
></P></DIV></FONT>
<DIV dir=3Dltr><FONT face=3D"Courier New"><FONT color=3D#000000 size=3D2>&n=
bsp;</DIV></FONT></FONT>
<DIV><FONT size=3D2 face=3D"Courier New">Thanks,</FONT></DIV>
<DIV><FONT size=3D2 face=3D"courier new">--David</FONT></DIV>
<DIV><FONT face=3D"Courier New"><FONT size=3D2>----------------------------=
------------------------<BR>David L. Black, Distinguished Engineer<BR>EMC C=
orporation, 176 South St., Hopkinton, MA&nbsp; 01748<BR>+1 (508) 293-7953&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FAX:=
 +1 (508) 293-7786<BR></FONT><FONT size=3D2><A href=3D"mailto:david.black@e=
mc.com" target=3D_blank><FONT size=3D2>david.black@emc.com</FONT></A><A tar=
get=3D_blank></A></FONT><FONT size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; Mobile: +1 (978) 394-7754<BR>---------------------------------------=
-------------<BR></FONT></DIV></FONT></BODY></HTML>

--_000_7EB1738E25454A33B5C0548630347568mimectl_--

From barryleiba.mailing.lists@gmail.com  Tue Aug 21 12:34:02 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E22C421F869E for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 12:34:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.008
X-Spam-Level: 
X-Spam-Status: No, score=-103.008 tagged_above=-999 required=5 tests=[AWL=-0.031, 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 OOVREEZk-Uuj for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 12:34:02 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 16FBE21F86B1 for <ietf@ietf.org>; Tue, 21 Aug 2012 12:34:01 -0700 (PDT)
Received: by lahm15 with SMTP id m15so102827lah.31 for <ietf@ietf.org>; Tue, 21 Aug 2012 12:34:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=2gon2sW1DHJYT6vb/kezoWG+fVMVQm7fUkn6VXRH32Y=; b=a3jKcnTInl6Vvo2SdDXccBGdoh7b/AJlNrejUDmXKou4IWTgMdQkdli9usokJQ4OXu E4qqAd8mWNDgtTMladaAKpnVGTRSPnq23V3nSean2xc+B6L8k2FF03N9uOy78VM4z4iG e3x8rX9xoEMK/U6Myedpm8FKSNrxKRoe9uvottNJG1cawSNwmmEkOhsK85WiG54h5kEb k0l3OCaONBAlr9FNNAn1LB/md51VpRF+EXymY8+KnphPTdo22kf+cQfIMnGQ5AyDfZtP nyRWlvwFir0lSKjmCH8tOsmL+Bmc0/JZ0gZ3K60hU+0mlk77Oor7aINi715jyyVnPKMO IZqQ==
MIME-Version: 1.0
Received: by 10.112.31.197 with SMTP id c5mr8226419lbi.50.1345577641038; Tue, 21 Aug 2012 12:34:01 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.113.196 with HTTP; Tue, 21 Aug 2012 12:34:00 -0700 (PDT)
In-Reply-To: <133201cd7f85$325f59a0$971e0ce0$@olddog.co.uk>
References: <133201cd7f85$325f59a0$971e0ce0$@olddog.co.uk>
Date: Tue, 21 Aug 2012 15:34:00 -0400
X-Google-Sender-Auth: fC6c08fRlUOizFoDFlV6OCbLy1U
Message-ID: <CAC4RtVB=N=CP7ManPZ=Hu65QbrX5WXnWRFFDZ-CpOcKQyqRWqg@mail.gmail.com>
Subject: Re: Some thoughts about draft-leiba-3777upd-eligibility-02.txt
From: Barry Leiba <barryleiba@computer.org>
To: adrian@olddog.co.uk
Content-Type: text/plain; charset=ISO-8859-1
Cc: draft-leiba-3777upd-eligibility@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2012 19:34:03 -0000

> I have one discussion point and a number of small nits...

Fine comments, all; thanks for taking the time.

I don't really see the discussion point as needing discussion.  You're
right, and I'll fix that set of stuff in the next version.  I could
say why certain text got in there in the first place (from early
comments and discussion), but it doesn't matter: I agree that it
should be changed.

There are just two points in your comments that I want to pursue:

>       15.2.  People serving in the IETF Secretariat and the RFC Editor
>            may not volunteer to serve as voting members of the
>            nominating committee.
>
> Slight problem with the term "RFC Editor" since this is a single person
> and also a service function. I suspect you mean the latter.

I do, and I actually had the same problem with it when I wrote it as
you do.  So help me, please: How *should* this be put?  I don't like,
"and those employed in the RFC Editor function," and I really can't
think of a concise, clean, accurate way to write it down, though we
all (today) know what it means.  Text, please, someone.

>    o  In bullet 16, to correct an erratum, the last paragraph is
>       replaced by this:
>
>          One possible selection method is described in RFC 3797 [1].
>
> Perfectly correct, but I don't think this document is the place to
> correct random errata.

I was (and am) ambivalent here.  I did not have this in my first
version.  SM did.  When we merged the proposals, I thought it was a
good idea to fix that.  But you're right that it's rather off topic,
and the right place to do that would be 3777bis, which this decidedly
is NOT.

I'm inclined to pull it out (having not checked that with SM yet,
though).  Does anyone (including SM) think it definitely needs to be
in here?

Barry

From d3e3e3@gmail.com  Tue Aug 21 12:45:56 2012
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DF6911E80D3 for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 12:45:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.527
X-Spam-Level: 
X-Spam-Status: No, score=-103.527 tagged_above=-999 required=5 tests=[AWL=0.072, 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 Tvk80askjAeM for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 12:45:55 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6E6F521F86D0 for <ietf@ietf.org>; Tue, 21 Aug 2012 12:45:55 -0700 (PDT)
Received: by ggnh4 with SMTP id h4so191994ggn.31 for <ietf@ietf.org>; Tue, 21 Aug 2012 12:45:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=F6fgGOWshE8Q1kldyIROJU9e2+iPyQ4sJM+0HbfH03c=; b=tWp08unxOv/zToNszvBjM8wx6IXsq+8NX593roa4Ax+1RMzLRLTdEalJQb6GW2CMrY Inle0Ky2N3tFUxI4taN8BklY5GDGJdahMMQPoI9Kyn1ZE1n2Jml+ctkCErWL4pT3xsg1 1RhuJAxgYDiJKyO7DQHpqg/muUQLrS6AfEUDZoS9kNDgzfD38RVN2CVuIq/PMHy4qSCm txnrp1S9Xm07a1Jr2yAkExEgfMRBD7byml6NUsI6Q6F3OFEBxY8pzsW1ys2NZ7GxfltB NXl+BHsz4hIbEJSvuRIIrx74mz5HjZF/IIa0VfHPOI7yL3WCdFKTCNkxHL72soGEO1nc 80xQ==
Received: by 10.60.3.35 with SMTP id 3mr14168147oez.139.1345578347589; Tue, 21 Aug 2012 12:45:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.60.80.100 with HTTP; Tue, 21 Aug 2012 12:45:27 -0700 (PDT)
In-Reply-To: <CAC4RtVB=N=CP7ManPZ=Hu65QbrX5WXnWRFFDZ-CpOcKQyqRWqg@mail.gmail.com>
References: <133201cd7f85$325f59a0$971e0ce0$@olddog.co.uk> <CAC4RtVB=N=CP7ManPZ=Hu65QbrX5WXnWRFFDZ-CpOcKQyqRWqg@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 21 Aug 2012 15:45:27 -0400
Message-ID: <CAF4+nEF96=yCWp7e7AUJ3iBn=gyaX8d9DxsLGL7=N00Ha8cUFw@mail.gmail.com>
Subject: Re: Some thoughts about draft-leiba-3777upd-eligibility-02.txt
To: Barry Leiba <barryleiba@computer.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: draft-leiba-3777upd-eligibility@tools.ietf.org, adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2012 19:45:56 -0000

On Tue, Aug 21, 2012 at 3:34 PM, Barry Leiba <barryleiba@computer.org> wrote:
>> I have one discussion point and a number of small nits...
>
> ...
>
> There are just two points in your comments that I want to pursue:
>
>>       15.2.  People serving in the IETF Secretariat and the RFC Editor
>>            may not volunteer to serve as voting members of the
>>            nominating committee.
>>
>> Slight problem with the term "RFC Editor" since this is a single person
>> and also a service function. I suspect you mean the latter.
>
> I do, and I actually had the same problem with it when I wrote it as
> you do.  So help me, please: How *should* this be put?  I don't like,
> "and those employed in the RFC Editor function," and I really can't
> think of a concise, clean, accurate way to write it down, though we
> all (today) know what it means.  Text, please, someone.

In particular, I believe the there are Editorial Boards that the
various fragments of the RFC Editor appoint and consult which should
not be excluded.

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

>>    o  In bullet 16, to correct an erratum, the last paragraph is
>>       replaced by this:
>>
>>          One possible selection method is described in RFC 3797 [1].
>>
>> Perfectly correct, but I don't think this document is the place to
>> correct random errata.
>
> I was (and am) ambivalent here.  I did not have this in my first
> version.  SM did.  When we merged the proposals, I thought it was a
> good idea to fix that.  But you're right that it's rather off topic,
> and the right place to do that would be 3777bis, which this decidedly
> is NOT.
>
> I'm inclined to pull it out (having not checked that with SM yet,
> though).  Does anyone (including SM) think it definitely needs to be
> in here?
>
> Barry

From adrian@olddog.co.uk  Tue Aug 21 12:58:35 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4435821F865C for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 12:58:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.525
X-Spam-Level: 
X-Spam-Status: No, score=-2.525 tagged_above=-999 required=5 tests=[AWL=0.074,  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 cR2e3YkK0msG for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 12:58:34 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 698C521F85A4 for <ietf@ietf.org>; Tue, 21 Aug 2012 12:58:34 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7LJwS7k012993;  Tue, 21 Aug 2012 20:58:29 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7LJwR6u012975 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 21 Aug 2012 20:58:28 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Donald Eastlake'" <d3e3e3@gmail.com>, "'Barry Leiba'" <barryleiba@computer.org>
References: <133201cd7f85$325f59a0$971e0ce0$@olddog.co.uk> <CAC4RtVB=N=CP7ManPZ=Hu65QbrX5WXnWRFFDZ-CpOcKQyqRWqg@mail.gmail.com> <CAF4+nEF96=yCWp7e7AUJ3iBn=gyaX8d9DxsLGL7=N00Ha8cUFw@mail.gmail.com>
In-Reply-To: <CAF4+nEF96=yCWp7e7AUJ3iBn=gyaX8d9DxsLGL7=N00Ha8cUFw@mail.gmail.com>
Subject: RE: Some thoughts about draft-leiba-3777upd-eligibility-02.txt
Date: Tue, 21 Aug 2012 20:58:26 +0100
Message-ID: <142e01cd7fd7$54725e50$fd571af0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKeymM+EHr04TPM6WVIrAnLSY7g2QJcPtJAAZ1bDpGVokzpIA==
Content-Language: en-gb
Cc: draft-leiba-3777upd-eligibility@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2012 19:58:35 -0000

How about asking Heather for the appropriate term?
Seems easier than guessing :-)

A

> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> Sent: 21 August 2012 20:45
> To: Barry Leiba
> Cc: adrian@olddog.co.uk; draft-leiba-3777upd-eligibility@tools.ietf.org;
> ietf@ietf.org
> Subject: Re: Some thoughts about draft-leiba-3777upd-eligibility-02.txt
> 
> On Tue, Aug 21, 2012 at 3:34 PM, Barry Leiba <barryleiba@computer.org> wrote:
> >> I have one discussion point and a number of small nits...
> >
> > ...
> >
> > There are just two points in your comments that I want to pursue:
> >
> >>       15.2.  People serving in the IETF Secretariat and the RFC Editor
> >>            may not volunteer to serve as voting members of the
> >>            nominating committee.
> >>
> >> Slight problem with the term "RFC Editor" since this is a single person
> >> and also a service function. I suspect you mean the latter.
> >
> > I do, and I actually had the same problem with it when I wrote it as
> > you do.  So help me, please: How *should* this be put?  I don't like,
> > "and those employed in the RFC Editor function," and I really can't
> > think of a concise, clean, accurate way to write it down, though we
> > all (today) know what it means.  Text, please, someone.
> 
> In particular, I believe the there are Editorial Boards that the
> various fragments of the RFC Editor appoint and consult which should
> not be excluded.
> 
> Thanks,
> Donald
> =============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
> 
> >>    o  In bullet 16, to correct an erratum, the last paragraph is
> >>       replaced by this:
> >>
> >>          One possible selection method is described in RFC 3797 [1].
> >>
> >> Perfectly correct, but I don't think this document is the place to
> >> correct random errata.
> >
> > I was (and am) ambivalent here.  I did not have this in my first
> > version.  SM did.  When we merged the proposals, I thought it was a
> > good idea to fix that.  But you're right that it's rather off topic,
> > and the right place to do that would be 3777bis, which this decidedly
> > is NOT.
> >
> > I'm inclined to pull it out (having not checked that with SM yet,
> > though).  Does anyone (including SM) think it definitely needs to be
> > in here?
> >
> > Barry


From barryleiba@gmail.com  Tue Aug 21 13:06:11 2012
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF8C411E80F2 for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 13:06:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.008
X-Spam-Level: 
X-Spam-Status: No, score=-103.008 tagged_above=-999 required=5 tests=[AWL=-0.031, 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 98zKkeNkpKkn for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 13:06:11 -0700 (PDT)
Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 36AEC11E80E8 for <ietf@ietf.org>; Tue, 21 Aug 2012 13:06:11 -0700 (PDT)
Received: by qadb17 with SMTP id b17so3876684qad.10 for <ietf@ietf.org>; Tue, 21 Aug 2012 13:06:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Kp387JuWN8pu0IvftGoleHtpJUWj7JRHPu08dayVwmw=; b=Tz7Vw8DIiGiS249cP1Z2vXMNMfFwCjYM0twn0IRy3II8zPNoSbyhjR0bZc8GM4YXE7 +gDmi3IzrDvI9yjUiyqjqfsQdlCszWU8vcH/gFe6GVX1oOsKsEiAO4oKnIUh6YrIOOOp R7qpXBU/d4SAchVl92yDke8OwafEcxIEh5iY36PdxRPxPlxk/N5U6uzo5looSOvOtRzP 8urUqer2OUy+DRsLM68JFxrcuE40vJPAyWOGW4cVrile1O86h9o1wLt8tAOzGNzTqBbW 1jcVfa349tOXGq+oqPZ7cR5SbwSdtFnZgB4gQWVgfJlcM3Tw5TlaA5gVHHNnW19fMJCB ns+w==
MIME-Version: 1.0
Received: by 10.59.8.37 with SMTP id dh5mr15835781ved.2.1345579570543; Tue, 21 Aug 2012 13:06:10 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.58.58.41 with HTTP; Tue, 21 Aug 2012 13:06:10 -0700 (PDT)
In-Reply-To: <142e01cd7fd7$54725e50$fd571af0$@olddog.co.uk>
References: <133201cd7f85$325f59a0$971e0ce0$@olddog.co.uk> <CAC4RtVB=N=CP7ManPZ=Hu65QbrX5WXnWRFFDZ-CpOcKQyqRWqg@mail.gmail.com> <CAF4+nEF96=yCWp7e7AUJ3iBn=gyaX8d9DxsLGL7=N00Ha8cUFw@mail.gmail.com> <142e01cd7fd7$54725e50$fd571af0$@olddog.co.uk>
Date: Tue, 21 Aug 2012 16:06:10 -0400
X-Google-Sender-Auth: t9q7Fj3asmsLHcSLApgH7t2EM3I
Message-ID: <CALaySJLvvELf5ENAbOsEgt+7ZBGdA7uUf-iCFHoGw13u0jts_A@mail.gmail.com>
Subject: Re: Some thoughts about draft-leiba-3777upd-eligibility-02.txt
From: Barry Leiba <barryleiba@computer.org>
To: adrian@olddog.co.uk
Content-Type: text/plain; charset=ISO-8859-1
Cc: draft-leiba-3777upd-eligibility@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2012 20:06:11 -0000

> How about asking Heather for the appropriate term?
> Seems easier than guessing :-)

Good idea.  The point here is to address the regular, paid employees,
not any people appointed to advise, nor any regular IETF folks who
might do occasional contracting.  I'll see if Heather has any ideas.

Barry

From bob.hinden@gmail.com  Tue Aug 21 13:52:24 2012
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B96C911E80F5 for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 13:52:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.51
X-Spam-Level: 
X-Spam-Status: No, score=-103.51 tagged_above=-999 required=5 tests=[AWL=0.089, 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 hXVZHlU6UqCi for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 13:52:23 -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 C070421F867A for <ietf@ietf.org>; Tue, 21 Aug 2012 13:52:23 -0700 (PDT)
Received: by dadf8 with SMTP id f8so148913dad.31 for <ietf@ietf.org>; Tue, 21 Aug 2012 13:52:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=wZaBxFE06GxrA2vQKsUvgssw0D6yCm1XYkZyGrrwDGE=; b=FBy3RDeOqVRyPNSKMjU6dgLl0JBTCE5WZ5xuWEJ90iDlyww3RcyrQj4Ne0si1nFL2B zPzagJLZZiK8Moz8dvO8YZaa68uNx4uA48XV8hk1OUNyh2CdrqbEn1eLjDCPf3ESPSZS 8JfltDvZGGVySOes25aC8IyyZTbPuc+/wfSrmtYE4002lvU0tb7UgbLnlJODUCc2e3qR U7nRiwM3QjkKUPEvN3hdzwip0KLBr0yQ2540X+djLUy6zT0WOj8w4wbBijBLQsL7ONz2 bvswvsMNBsXvwbBcvbrBWZyU7a90cpiW/bs/PPIzYzQMZFN4EcILOCHOznORtvS/rPji WkJQ==
Received: by 10.66.75.104 with SMTP id b8mr40910742paw.21.1345582343533; Tue, 21 Aug 2012 13:52:23 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPS id iq1sm2121154pbc.37.2012.08.21.13.52.19 (version=SSLv3 cipher=OTHER); Tue, 21 Aug 2012 13:52:22 -0700 (PDT)
Subject: Re: Some thoughts about draft-leiba-3777upd-eligibility-02.txt
Mime-Version: 1.0 (Apple Message framework v1280)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <133201cd7f85$325f59a0$971e0ce0$@olddog.co.uk>
Date: Tue, 21 Aug 2012 13:52:18 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <ABDF3549-3C24-4AD5-985C-5E1560A80D83@gmail.com>
References: <133201cd7f85$325f59a0$971e0ce0$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.1280)
Cc: draft-leiba-3777upd-eligibility@tools.ietf.org, Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2012 20:52:24 -0000

On Aug 21, 2012, at 3:10 AM, Adrian Farrel wrote:

>     This document also excludes certain individuals who are directly
>     paid for their work with the IETF...
>   I think you can leave it at that.

While on this topic, we might as well get it right.  The text in the =
draft is:

   This document also excludes certain individuals who are directly paid
   for their work with the IETF, and who, therefore, have a direct
   personal financial incentive in the selection of the leadership
   boards.  We limit this exclusion to a few people who are paid for
   long-term full-time work.  In practice, they are unlikely to
   volunteer for the NomCom anyway, so this addition makes little
   practical change.

I assume the intent is exclude people who are paid by the IETF to do =
work in the IETF.  For example, the IAD.  The problem is that no one is =
paid by the IETF.  The IETF has several people who do work at it's =
direction.  This is done as direct employees of ISOC or as contractors =
who have their contracts with ISOC.  We also hire (via ISOC) companies =
that provide services to the IETF.  This ranges from the secretariat =
services, NOC services, tools development, program management services, =
and tools specification development.  In these cases it difficult to =
tell if an individual is working for the IETF "long-term full-time =
work". =20

Further, the text as written could be interpreted to exclude people =
who's employers pay they to participate in the IETF.  For example, that =
would include me because it is part of my job to participate in the =
IETF.  I don't think that is the intent of the text in the draft, but it =
would be easy to interpret it that way.  OK, maybe I don't do it full =
time, but all of the IESG position require full time support. =20

If this text is to remain, it needs to be clearer as to what it means. =20=


Bob


Bob







From acee.lindem@ericsson.com  Tue Aug 21 14:23:35 2012
Return-Path: <acee.lindem@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 66F2621F85F9 for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 14:23:35 -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.090,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vn8ilVYhy5ac for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 14:23:33 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 7C20F21F85EA for <ietf@ietf.org>; Tue, 21 Aug 2012 14:23:33 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id q7LLNKLn029455 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 21 Aug 2012 16:23:30 -0500
Received: from EUSAACMS0702.eamcs.ericsson.se ([169.254.1.166]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Tue, 21 Aug 2012 17:23:20 -0400
From: Acee Lindem <acee.lindem@ericsson.com>
To: "Ong, Lyndon" <Lyong@Ciena.com>
Date: Tue, 21 Aug 2012 17:23:17 -0400
Subject: Re: Last Call: <draft-ietf-ccamp-rfc5787bis-05.txt> 
Thread-Topic: Last Call: <draft-ietf-ccamp-rfc5787bis-05.txt> 
Thread-Index: Ac1/4y/p8Qqt1aB6SN6NYjuVuq+4bw==
Message-ID: <D3266962-DD41-4FBA-A0A2-E1F9D5BF2B3C@ericsson.com>
References: <A0B4FC0A5EFBD44585414760DB4FD2749F512AA9@MDWEXGMB02.ciena.com>
In-Reply-To: <A0B4FC0A5EFBD44585414760DB4FD2749F512AA9@MDWEXGMB02.ciena.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; boundary="Apple-Mail-34-57293588"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: Stephen Shew <sshew@Ciena.com>, "Andrew G. \(Andy\) Malis" <andrew.g.malis@verizon.com>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org" <draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2012 21:23:35 -0000

--Apple-Mail-34-57293588
Content-Type: multipart/alternative;
	boundary=Apple-Mail-33-57293569


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

Hi Stephen, Lyndon,=20
Andy and I have had discussions with the CCAMP chairs and AD. We have =
come to the conclusion that we cannot merely change the name space for =
the advertised TE Router ID since this would imply a change to the GMPL =
model for setting up LSPs. In GMPL, the LSP endpoints are in the =
Signaling Control Network (SCN) and this cannot be changed without a =
distinct model for ASON LSP establishment complete with the =
specification of the changes to path computation, RSVP path signaling, =
and RSVP Explicit Route Object (ERO) handling. In essence, this change =
would add a level of indirection from the SNPP to the SCN. In the =
context of this draft, we are not going to deviate from the GMPLS LSP =
model and, hence, will not incorporating the suggested changes.=20
Thanks,
Acee=20
On Aug 17, 2012, at 7:58 PM, Ong, Lyndon wrote:

> (Submitted on behalf of Stephen Shew)
> =20
> I would like to raise an issue with =
draft-ietf-ccamp-rfc5787bis-05.txt.  The issue does not affect the =
proposed sub-TLVs or their semantics, so it would not affect an =
implementation. I believe some statements in the document should be =
edited to avoid confusion over ASON terminology as defined in ITU-T =
Recommendation G.8080, for which I am editor.
> =20
> It concerns the definition of =93ASON reachability=94 which changed =
during the course of the document from being a transport plane address, =
the SubNetwork Point Pool (SNPP) space, to the Signalling Control =
Network (SCN) address space.  I think the root of the issue is that the =
visibility of the three address spaces described in ASON (G.8080) is not =
always made clear when discussing using OSPF for ASON Routing.  Section =
3 of G.8080 states that:
> There are three categories of identifiers used for ASON routing
>    (G7715.1): transport plane names, control plane identifiers for
>    components, and Signaling Communications Network (SCN) addresses.
> =20
> In -03 of the document, the term SNPP was used. This is the SubNetwork =
Point Pool space that describes the data plane and is defined in G.8080 =
Section 10.  It names the subnetwork (and/or containing subnetworks) to =
which Subnetwork Points (SNPs) are scoped. =46rom G.8081: =93The SNP is =
an abstraction that represents an actual or potential underlying =
connection point (CP) (or connection termination point (CTP)) or an =
actual or potential termination connection point (TCP) or trail =
termination point (TTP). Several SNPs (in different subnetwork =
partitions) may represent the same TCP or CP."
> =20
> In concrete terms, an SNPP would name an OTN switch, and an SNP would =
be a label identifying an ODU0.  For the topology of the transport =
plane, SNPP and SNPP link names are used.  Path computation is performed =
over such a topology.  If a path can be computed between two SNPPs, they =
are reachable in ASON terms. For example, and ingress OTN switch for an =
ODU1 connection that terminates on an egress OTN switch.
> =20
> The Signalling Control Network (SCN) is a separate network over which =
control messages are sent. It has a topology independent of the =
transport plane.  Path computation on the SCN address space is used to =
connect SCN address.  SDH/OTN networks often have a separate IP network =
as the SCN network and the topology of the SCN network does not have to =
follow the topology of the transport network.
> =20
> ASON Control Plane Component identifiers are the third name space and =
identify routing and signalling instances.  It is expected that they =
form adjacencies over the SCN.  The topology of the adjacencies is =
independent of the SCN and transport plane topologies.  =93Reachability=94=
 between two control plane components would be some sequence of =
adjacencies.  It is entirely possible to have two separate control =
planes running over the same SCN network, or one control plane that uses =
several SCNs.  For example, imagine some OSPF instances whose =
adjacencies were all targeted and each adjacency traversed a separate =
private IP network.  The OSPF instances would need to identified by a =
common address space so that they are distinguished from each other, but =
the TE interfaces could have overlapping IPv4 values because they would =
be in different private IP network spaces.
> =20
> What makes the discussion of =93TE router ID=94 confusing is that as =
applied to a transport network, every node gets a =93TE router ID=94 and =
so it can be used in the transport topology for path computation.  In =
that sense it is =93reachable=94 in the dataplane.  However, it is also =
(I think) an address that is implicitly in the SCN space in some =
implementations and so it takes on a dual meaning of =93reachability=94 =
at the IP layer as in the sentence from the I-D =93This TLV specifies a =
stable OSPF TE node IP address, i.e., the IP address is always reachable =
when there is IP connectivity to the associated OSPF TE node.=94.  If a =
router were instantiated without any routing protocols, as in one form =
of Software Defined Networks (SDNs), an identifier would be needed for =
the node itself so that path computation in a centralized controller =
could form the router data plane topology.
> =20
> Suggested changes to the draft are:
> In section 3, third paragraph:  "In the context of OSPF Traffic =
Engineering (TE), an ASON transport node corresponds to a unique OSPF TE =
node.  An OSPF TE node is uniquely identified by the TE Router Address =
TLV [RFC3630]. In this document, this TE Router Address is referred to =
as the TE Router ID, which is in the ASON SCN name space."  However, =
G.8080 distinguishes between the transport node and its associated =
control plane components, esp. the Routing Controller.  It is the =
control plane component that is accessed through the SCN rather than the =
transport node itself.
> I propose changing the statement to say: "In this document, this TE =
Router Address is referred to as the TE Router ID, which is in the ASON =
SNPP name space.=94
> Alternatively, we could just delete the sentence =93In this document, =
this TE Router Address is referred to as the TE Router ID, which is in =
the ASON SNPP name space.=94.
> =20
> In section 4, first paragraph, reachability of endpoints in the =
transport plane is described as follows:
> "In ASON, reachability refers to the set of endpoints reachable in the =
transport plane by an associated ASON transport node.  Reachable =
entities are identified in the ASON SCN name space."  As discussed =
above, only the control plane components are accessed through the SCN, =
not the transport nodes themselves.  Entities that are reachable in the =
transport plane are identified through ASON SNPPs rather than ASON SCN =
addresses.  Therefore I suggest removing the second sentence completely =
so that it reads simply "In ASON, reachability refers to the set of =
endpoints reachable in the transport plane by an associated ASON =
transport node. =93
> =20
> Finally, in section 6.2, first paragraph following the format diagram, =
it is stated:  "If it is not included in a Node Attribute TLV or a value =
of 0 is specified for the Local TE Router Identifier, the Note Attribute =
TLV will not be used for determining ASON SCN reachability."=20
> Again, the text should be edited to make the distinction between =
transport plane and SCN clearer, I suggest modifying the statement to =
refer to "ASON reachability" rather than "ASON SCN reachability".  The =
statement would read as follows (also correcting the spelling of the =
TLV):
> "If it is not included in a Node Attribute TLV or a value of 0 is =
specified for the Local TE Router Identifier, the Node Attribute TLV =
will not be used for determining ASON reachability."
> =20
> Stephen Shew
> =20
> -----Original Message-----
> From: ietf-announce-bounces@ietf.org =
[mailto:ietf-announce-bounces@ietf.org] On Behalf Of The IESG
> Sent: Friday, July 20, 2012 11:19 AM
> To: IETF-Announce
> Cc: ccamp@ietf.org
> Subject: Last Call: <draft-ietf-ccamp-rfc5787bis-05.txt> (ASON Routing =
for OSPFv2 Protocols) to Proposed Standard
> =20
> =20
> The IESG has received a request from the Common Control and =
Measurement Plane WG (ccamp) to consider the following document:
> - 'ASON Routing for OSPFv2 Protocols'
>   <draft-ietf-ccamp-rfc5787bis-05.txt> as Proposed Standard
> =20
> The IESG plans to make a decision in the next few weeks, and solicits =
final comments on this action. Please send substantive comments to the =
ietf@ietf.org mailing lists by 2012-08-17. Exceptionally, comments may =
be sent to iesg@ietf.org instead. In either case, please retain the =
beginning of the Subject line to allow automated sorting. This is a =
four- week last call period because it spans the IETF-84 meeting.
> =20
> Abstract
> =20
>    The ITU-T has defined an architecture and requirements for =
operating
>    an Automatically Switched Optical Network (ASON).
> =20
>    The Generalized Multiprotocol Label Switching (GMPLS) protocol =
suite
>    is designed to provide a control plane for a range of network
>    technologies including optical networks such as time division
>    multiplexing (TDM) networks including SONET/SDH and Optical =
Transport
>    Networks (OTNs), and lambda switching optical networks.
> =20
>    The requirements for GMPLS routing to satisfy the requirements of
>    ASON routing, and an evaluation of existing GMPLS routing protocols
>    are provided in other documents.  This document defines extensions =
to
>    the OSPFv2 Link State Routing Protocol to meet the requirements for
>    routing in an ASON.
> =20
>    Note that this work is scoped to the requirements and evaluation
>    expressed in RFC 4258 and RFC 4652 and the ITU-T Recommendations
>    current when those documents were written.  Future extensions of
>    revisions of this work may be necessary if the ITU-T =
Recommendations
>    are revised or if new requirements are introduced into a revision =
of
>    RFC 4258. This document obsoletes RFC 5787 and updates RFC 5786.
> =20
> =20
> =20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-ccamp-rfc5787bis/
> =20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-ccamp-rfc5787bis/ballot/
> =20
> No IPR declarations have been submitted directly on this I-D.
> =20
> =20
> Stephen Shew | Director, Standards
> sshew@ciena.com | 3500 Carling Ave. | Ottawa CANADA K2H 8E9
> Direct +1.613.670.3211
> =20


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

<html><head><base href=3D"x-msg://221/"></head><body style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; ">Hi Stephen, Lyndon,&nbsp;<div>Andy and I have had =
discussions with the CCAMP chairs and AD. We have come to the conclusion =
that we cannot merely change the name space for the advertised TE Router =
ID since this would imply a change to the GMPL model for setting up =
LSPs. In GMPL, the LSP endpoints are in the Signaling Control Network =
(SCN) and this cannot be changed without a distinct model for ASON LSP =
establishment complete with the specification of the changes to path =
computation, RSVP path signaling, and RSVP Explicit Route Object (ERO) =
handling. In essence, this change would add a level of indirection from =
the SNPP to the SCN. In the context of this draft, we are not going to =
deviate from the GMPLS LSP model and, hence, will not incorporating the =
suggested =
changes.&nbsp;</div><div>Thanks,</div><div>Acee&nbsp;<br><div><div>On =
Aug 17, 2012, at 7:58 PM, Ong, Lyndon 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: Courier; 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 =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><span lang=3D"EN-GB">(Submitted =
on behalf of Stephen Shew)<o:p></o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; "><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; "><span lang=3D"EN-GB">I would like to raise an issue with =
draft-ietf-ccamp-rfc5787bis-05.txt.&nbsp; The issue does not affect the =
proposed sub-TLVs or their semantics, so it would not affect an =
implementation. I believe some statements in the document should be =
edited to avoid confusion over ASON terminology as defined in ITU-T =
Recommendation G.8080, for which I am =
editor.<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-GB">It concerns the definition of =93ASON reachability=94 =
which changed during the course of the document from being a transport =
plane address, the SubNetwork Point Pool (SNPP) space, to the Signalling =
Control Network (SCN) address space.&nbsp; I think the root of the issue =
is that the visibility of the three address spaces described in ASON =
(G.8080) is not always made clear when discussing using OSPF for ASON =
Routing.&nbsp; Section 3 of G.8080 states =
that:<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: 'Times New Roman', serif; "><span lang=3D"EN-GB" =
style=3D"font-family: 'Courier New'; ">There are three categories of =
identifiers used for ASON routing<o:p></o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: 'Times New =
Roman', serif; "><span lang=3D"EN-GB" style=3D"font-family: 'Courier =
New'; ">&nbsp;&nbsp; (G7715.1): transport plane names, control plane =
identifiers for<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: 'Times New Roman', serif; "><span lang=3D"EN-GB" =
style=3D"font-family: 'Courier New'; ">&nbsp;&nbsp; components, and =
Signaling Communications Network (SCN) =
addresses.<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><span lang=3D"EN-GB" =
style=3D"font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><span lang=3D"EN-GB">In -03 of =
the document, the term SNPP was used. This is the SubNetwork Point Pool =
space that describes the data plane and is defined in G.8080 Section =
10.&nbsp; It names the subnetwork (and/or containing subnetworks) to =
which Subnetwork Points (SNPs) are scoped. =46rom G.8081: =93The SNP is =
an abstraction that represents an actual or potential underlying =
connection point (CP) (or connection termination point (CTP)) or an =
actual or potential termination connection point (TCP) or trail =
termination point (TTP). Several SNPs (in different subnetwork =
partitions) may represent the same TCP or CP.</span><span =
dir=3D"RTL"></span><span lang=3D"AR-AE" dir=3D"RTL" style=3D"font-family: =
Arial, sans-serif; "><span dir=3D"RTL"></span>"</span><span =
lang=3D"EN-GB"><o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-GB">In concrete terms, an SNPP would name an OTN switch, and =
an SNP would be a label identifying an ODU0.&nbsp; For the topology of =
the transport plane, SNPP and SNPP link names are used.&nbsp; Path =
computation is performed over such a topology.&nbsp; If a path can be =
computed between two SNPPs, they are reachable in ASON terms. For =
example, and ingress OTN switch for an ODU1 connection that terminates =
on an egress OTN switch.<o:p></o:p></span></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: Arial, sans-serif; =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><span lang=3D"EN-GB">The =
Signalling Control Network (SCN) is a separate network over which =
control messages are sent. It has a topology independent of the =
transport plane.&nbsp; Path computation on the SCN address space is used =
to connect SCN address.&nbsp; SDH/OTN networks often have a separate IP =
network as the SCN network and the topology of the SCN network does not =
have to follow the topology of the transport network.</span><span =
style=3D"font-family: 'Times New Roman', serif; =
"><o:p></o:p></span></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif; "><span lang=3D"AR-SA" dir=3D"RTL" =
style=3D"font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><span lang=3D"EN-GB">ASON =
Control Plane Component identifiers are the third name space and =
identify routing and signalling instances.&nbsp; It is expected that =
they form adjacencies over the SCN.&nbsp; The topology of the =
adjacencies is independent of the SCN and transport plane =
topologies.&nbsp; =93Reachability=94 between two control plane =
components would be some sequence of adjacencies.&nbsp; It is entirely =
possible to have two separate control planes running over the same SCN =
network, or one control plane that uses several SCNs.&nbsp; For example, =
imagine some OSPF instances whose adjacencies were all targeted and each =
adjacency traversed a separate private IP network.&nbsp; The OSPF =
instances would need to identified by a common address space so that =
they are distinguished from each other, but the TE interfaces could have =
overlapping IPv4 values because they would be in different private IP =
network spaces.<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-GB">What makes the discussion of =93TE router ID=94 confusing =
is that as applied to a transport network, every node gets a =93TE =
router ID=94 and so it can be used in the transport topology for path =
computation.&nbsp; In that sense it is =93reachable=94 in the =
dataplane.&nbsp; However, it is also (I think) an address that is =
implicitly in the SCN space in some implementations and so it takes on a =
dual meaning of =93reachability=94 at the IP layer as in the sentence =
from the I-D =93This TLV specifies a stable OSPF TE node IP address, =
i.e., the IP address is always reachable when there is IP connectivity =
to the associated OSPF TE node.=94.&nbsp; If a router were instantiated =
without any routing protocols, as in one form of Software Defined =
Networks (SDNs), an identifier would be needed for the node itself so =
that path computation in a centralized controller could form the router =
data plane topology.<o:p></o:p></span></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-GB">Suggested changes to the draft =
are:<o:p></o:p></span></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif; "><span lang=3D"EN-GB">In section 3, =
third paragraph:&nbsp; "In the context of OSPF Traffic Engineering (TE), =
an ASON transport node corresponds to a unique OSPF TE node.&nbsp; An =
OSPF TE node is uniquely identified by the TE Router Address TLV =
[RFC3630]. In this document, this TE Router Address is referred to as =
the TE Router ID, which is in the ASON SCN name space."&nbsp; However, =
G.8080 distinguishes between the transport node and its associated =
control plane components, esp. the Routing Controller.&nbsp; It is the =
control plane component that is accessed through the SCN rather than the =
transport node itself.<o:p></o:p></span></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-GB">I propose changing the statement to say: "In this =
document, this TE Router Address is referred to as the TE Router ID, =
which is in the ASON SNPP name space.=94<o:p></o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; "><span lang=3D"EN-GB">Alternatively, we could just delete =
the sentence =93In this document, this TE Router Address is referred to =
as the TE Router ID, which is in the ASON SNPP name =
space.=94.<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-GB">In section 4, first paragraph, reachability of endpoints =
in the transport plane is described as =
follows:<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><span lang=3D"EN-GB">"In ASON, =
reachability refers to the set of endpoints reachable in the transport =
plane by an associated ASON transport node.&nbsp; Reachable entities are =
identified in the ASON SCN name space."&nbsp; As discussed above, only =
the control plane components are accessed through the SCN, not the =
transport nodes themselves.&nbsp; Entities that are reachable in the =
transport plane are identified through ASON SNPPs rather than ASON SCN =
addresses.&nbsp; Therefore I suggest removing the second sentence =
completely so that it reads simply "In ASON, reachability refers to the =
set of endpoints reachable in the transport plane by an associated ASON =
transport node.&nbsp;=93<o:p></o:p></span></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-GB">Finally, in section 6.2, first paragraph following the =
format diagram, it is stated:&nbsp; "If it is not included in a Node =
Attribute TLV or a value of 0 is specified for the Local TE Router =
Identifier, the Note Attribute TLV will not be used for determining ASON =
SCN reachability."&nbsp;<o:p></o:p></span></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-GB">Again, the text should be edited to make the distinction =
between transport plane and SCN clearer, I suggest modifying the =
statement to refer to "ASON reachability" rather than "ASON SCN =
reachability".&nbsp; The statement would read as follows (also =
correcting the spelling of the TLV):<o:p></o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; "><span lang=3D"EN-GB">"If it is not included in a Node =
Attribute TLV or a value of 0 is specified for the Local TE Router =
Identifier, the Node Attribute TLV will not be used for determining ASON =
reachability."<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
10.5pt; font-family: Consolas; "><span =
lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 10.5pt; font-family: Consolas; "><span lang=3D"EN-GB">Stephen =
Shew<o:p></o:p></span></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 10.5pt; =
font-family: Consolas; "><span =
lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 10.5pt; font-family: Consolas; ">-----Original =
Message-----<o:p></o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
10.5pt; font-family: Consolas; ">From:<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:ietf-announce-bounces@ietf.org" style=3D"color: blue; =
text-decoration: underline; ">ietf-announce-bounces@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>[<a =
href=3D"mailto:ietf-announce-bounces@ietf.org" style=3D"color: blue; =
text-decoration: underline; ">mailto:ietf-announce-bounces@ietf.org</a>] =
On Behalf Of The IESG<o:p></o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
10.5pt; font-family: Consolas; ">Sent: Friday, July 20, 2012 11:19 =
AM<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 0in; margin-bottom: 0.0001pt; font-size: 10.5pt; =
font-family: Consolas; ">To: IETF-Announce<o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 10.5pt; font-family: Consolas; =
">Cc:<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:ccamp@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">ccamp@ietf.org</a><o:p></o:p></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 10.5pt; font-family: Consolas; ">Subject: Last Call: =
&lt;draft-ietf-ccamp-rfc5787bis-05.txt&gt; (ASON Routing for OSPFv2 =
Protocols) to Proposed Standard<o:p></o:p></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 10.5pt; font-family: Consolas; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 10.5pt; font-family: Consolas; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 10.5pt; =
font-family: Consolas; ">The IESG has received a request from the Common =
Control and Measurement Plane WG (ccamp) to consider the following =
document:<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 10.5pt; =
font-family: Consolas; ">- 'ASON Routing for OSPFv2 =
Protocols'<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 10.5pt; =
font-family: Consolas; ">&nbsp; =
&lt;draft-ietf-ccamp-rfc5787bis-05.txt&gt; as Proposed =
Standard<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 10.5pt; =
font-family: Consolas; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 10.5pt; font-family: Consolas; ">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<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:ietf@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">ietf@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>mailing lists by =
2012-08-17. Exceptionally, comments may be sent to<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:iesg@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">iesg@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>instead. In either case, =
please retain the beginning of the Subject line to allow automated =
sorting. This is a four- week last call period because it spans the =
IETF-84 meeting.<o:p></o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
10.5pt; font-family: Consolas; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 10.5pt; font-family: Consolas; =
">Abstract<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 10.5pt; =
font-family: Consolas; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 10.5pt; font-family: Consolas; ">&nbsp;&nbsp; The ITU-T has =
defined an architecture and requirements for =
operating<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 10.5pt; =
font-family: Consolas; ">&nbsp;&nbsp; an Automatically Switched Optical =
Network (ASON).<o:p></o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
10.5pt; font-family: Consolas; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 10.5pt; font-family: Consolas; =
">&nbsp;&nbsp; The Generalized Multiprotocol Label Switching (GMPLS) =
protocol suite<o:p></o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
10.5pt; font-family: Consolas; ">&nbsp;&nbsp; is designed to provide a =
control plane for a range of network<o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 10.5pt; font-family: Consolas; =
">&nbsp;&nbsp; technologies including optical networks such as time =
division<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 10.5pt; =
font-family: Consolas; ">&nbsp;&nbsp; multiplexing (TDM) networks =
including SONET/SDH and Optical Transport<o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 10.5pt; font-family: Consolas; =
">&nbsp;&nbsp; Networks (OTNs), and lambda switching optical =
networks.<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 10.5pt; =
font-family: Consolas; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 10.5pt; font-family: Consolas; ">&nbsp;&nbsp; The =
requirements for GMPLS routing to satisfy the requirements =
of<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 0in; margin-bottom: 0.0001pt; font-size: 10.5pt; =
font-family: Consolas; ">&nbsp;&nbsp; ASON routing, and an evaluation of =
existing GMPLS routing protocols<o:p></o:p></div><div style=3D"margin-top:=
 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 10.5pt; font-family: Consolas; ">&nbsp;&nbsp; are provided in =
other documents.&nbsp; This document defines extensions =
to<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 0in; margin-bottom: 0.0001pt; font-size: 10.5pt; =
font-family: Consolas; ">&nbsp;&nbsp; the OSPFv2 Link State Routing =
Protocol to meet the requirements for<o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 10.5pt; font-family: Consolas; =
">&nbsp;&nbsp; routing in an ASON.<o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 10.5pt; font-family: Consolas; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 10.5pt; =
font-family: Consolas; ">&nbsp;&nbsp; Note that this work is scoped to =
the requirements and evaluation<o:p></o:p></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 10.5pt; font-family: Consolas; ">&nbsp;&nbsp; expressed in =
RFC 4258 and RFC 4652 and the ITU-T Recommendations<o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 10.5pt; font-family: Consolas; =
">&nbsp;&nbsp; current when those documents were written.&nbsp; Future =
extensions of<o:p></o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
10.5pt; font-family: Consolas; ">&nbsp;&nbsp; revisions of this work may =
be necessary if the ITU-T Recommendations<o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 10.5pt; font-family: Consolas; =
">&nbsp;&nbsp; are revised or if new requirements are introduced into a =
revision of<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 10.5pt; =
font-family: Consolas; ">&nbsp;&nbsp; RFC 4258. This document obsoletes =
RFC 5787 and updates RFC 5786.<o:p></o:p></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 10.5pt; font-family: Consolas; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 10.5pt; font-family: Consolas; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 10.5pt; =
font-family: Consolas; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 10.5pt; font-family: Consolas; ">The file can be obtained =
via<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 0in; margin-bottom: 0.0001pt; font-size: 10.5pt; =
font-family: Consolas; "><a =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-ccamp-rfc5787bis/" =
style=3D"color: blue; text-decoration: underline; =
">http://datatracker.ietf.org/doc/draft-ietf-ccamp-rfc5787bis/</a><o:p></o=
:p></div><div style=3D"margin-top: 0in; margin-right: 0in; margin-left: =
0in; margin-bottom: 0.0001pt; font-size: 10.5pt; font-family: Consolas; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 10.5pt; =
font-family: Consolas; ">IESG discussion can be tracked =
via<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 0in; margin-bottom: 0.0001pt; font-size: 10.5pt; =
font-family: Consolas; "><a =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-ccamp-rfc5787bis/ballot=
/" style=3D"color: blue; text-decoration: underline; =
">http://datatracker.ietf.org/doc/draft-ietf-ccamp-rfc5787bis/ballot/</a><=
o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 0in; margin-bottom: 0.0001pt; font-size: 10.5pt; =
font-family: Consolas; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 10.5pt; font-family: Consolas; ">No IPR declarations have =
been submitted directly on this I-D.<o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; "><span style=3D"font-family: 'Times New Roman', serif; =
color: rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; "><span style=3D"font-family: 'Times New Roman', serif; =
color: rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; "><b><span style=3D"font-size: 7.5pt; font-family: Arial, =
sans-serif; color: rgb(31, 73, 125); ">Stephen Shew</span></b><span =
style=3D"font-size: 7.5pt; font-family: Arial, sans-serif; color: =
rgb(31, 73, 125); ">&nbsp;</span><span style=3D"font-size: 7.5pt; =
font-family: Arial, sans-serif; color: red; ">|</span><span =
style=3D"font-size: 7.5pt; font-family: Arial, sans-serif; color: =
rgb(31, 73, 125); "><span =
class=3D"Apple-converted-space">&nbsp;</span></span><span =
style=3D"font-size: 7.5pt; font-family: Arial, sans-serif; color: gray; =
">Director, Standards</span><span style=3D"font-size: 7.5pt; =
font-family: Arial, sans-serif; color: rgb(31, 73, 125); =
"><br></span><u><span style=3D"font-size: 7.5pt; font-family: Arial, =
sans-serif; color: blue; "><a href=3D"mailto:jdoe@ciena.com" =
style=3D"color: blue; text-decoration: underline; =
">sshew@ciena.com</a></span></u><span style=3D"font-size: 7.5pt; =
font-family: Arial, sans-serif; color: rgb(31, 73, 125); "><span =
class=3D"Apple-converted-space">&nbsp;</span></span><span =
style=3D"font-size: 7.5pt; font-family: Arial, sans-serif; color: red; =
">|</span><span style=3D"font-size: 7.5pt; font-family: Arial, =
sans-serif; color: purple; "><span =
class=3D"Apple-converted-space">&nbsp;</span></span><span =
style=3D"font-size: 7.5pt; font-family: Arial, sans-serif; color: gray; =
">3500 Carling Ave.<span =
class=3D"Apple-converted-space">&nbsp;</span></span><span =
style=3D"font-size: 7.5pt; font-family: Arial, sans-serif; color: red; =
">|</span><span style=3D"font-size: 7.5pt; font-family: Arial, =
sans-serif; color: purple; ">&nbsp;</span><span style=3D"font-size: =
7.5pt; font-family: Arial, sans-serif; color: gray; ">Ottawa CANADA K2H =
8E9<br>Direct +1.613.670.3211<o:p></o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; =
"><o:p>&nbsp;</o:p></div></div></div></span></blockquote></div><br></div><=
/body></html>=

--Apple-Mail-33-57293569--

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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIM8jCCBDQw
ggMcoAMCAQICECFWwVQHDV12M/Sr0yNv0sYwDQYJKoZIhvcNAQEFBQAwOTERMA8GA1UECgwIRXJp
Y3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTAeFw0xMDEwMDEyMDA0
NTlaFw0xMzEwMDEyMDA0NDhaMG8xETAPBgNVBAoMCEVyaWNzc29uMR8wHQYDVQQDDBZBY2VlIExp
bmRlbSBMaW5kZW0gSUlJMRAwDgYDVQQFEwdlYWxmbGluMScwJQYJKoZIhvcNAQkBFhhhY2VlLmxp
bmRlbUBlcmljc3Nvbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAI/Dc9ALiZuBMyuv
bsc3eBxjXZpMi45Z0vzsUQZTJGTBeY7p9JsdzXC9J1uMisBxYVi39R3KJo6I4hXVp9wrA1rxh4AE
bnP1+Gxfpj33uWEFYbBnVAJkIWYWF7CYTn8Zm/yd13vPXtuGA6ESeLnnJafwC9Y0YwUQ+4HX7PNv
uauVAgMBAAGjggGEMIIBgDCBwAYDVR0fBIG4MIG1MIGyoIGvoIGshjdodHRwOi8vY3JsLnRydXN0
LnRlbGlhLmNvbS9Fcmljc3Nvbk5MSW5kaXZpZHVhbENBMDEuY3JshnFsZGFwOi8vbGRhcC50cnVz
dC50ZWxpYS5jb20vY249RXJpY3Nzb24lMjBOTCUyMEluZGl2aWR1YWwlMjBDQTAxLG89RXJpY3Nz
b24/Y2VydGlmaWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnk/YmFzZTAjBgNVHREEHDAagRhhY2Vl
LmxpbmRlbUBlcmljc3Nvbi5jb20wRgYDVR0gBD8wPTA7BgYqhXBrAQEwMTAvBggrBgEFBQcCARYj
aHR0cDovL3d3dy5lcmljc3Nvbi5jb20vbGVnYWwuc2h0bWwwHQYDVR0OBBYEFAgOzAPuplmPr7C1
BTqV94OyqUdhMB8GA1UdIwQYMBaAFJYnw7jepV9dRD45UuVFsXZfYzCbMA4GA1UdDwEB/wQEAwIF
oDANBgkqhkiG9w0BAQUFAAOCAQEAE1gyNW6c2t/YsLxW5sm67+gVGK0Lnge4ub+k8dgGrK7Mj7em
nkOIFkjdv/tqdJ/SoUy/WEkBXba2TfpZ+lfluMgLYux1vSvqBUxYBsUHeNth2Q/Y6A9sCaDTBPlK
vZ2jLz814NavrVfgTCLdxX6zNtGdwzhviz+FyqyxYF43Q86RP8Gd/Npaz1W8pmYAHm0+lezuTx5k
F3Av3+SaZ/MR6s+RWuXEIdED36ajeQz+OG8Mh3nplofzdrOeoWGDz53YlfRhgj+TXo+H1lclZAvD
WVaMMXPdb27h9Hngsq87dkCW9uAyv8DI993rdhqzlEgUyQIL32icAXfTmTYgoGPOwjCCBEUwggMt
oAMCAQICEBPJ6v/eJq2p3KTKI4GDR+MwDQYJKoZIhvcNAQEFBQAwRDEaMBgGA1UECgwRVGVsaWFT
b25lcmEgR3JvdXAxJjAkBgNVBAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMB4XDTA2
MTAwNjEwMDA1M1oXDTE2MTAwMjA1MDQxN1owOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMM
G0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC
ggEBALYQd+Q1HuuHxDyNGFlEPzCxuPPFO5W2xyr+nqCVnNJ4QYFe1HACqavqNLwUGIqIEyHv1rLn
fub9LBc7dQpRHjl/dggin0ONOFJ36nbGEbfHjLJz2BzOWvwl84Sc+Fx09IrDU/SZSWFSfhqTu3TT
39h79brHdRkdPBUgBYgsiFKriHI0TjP5G8628H27BDzqUpzGLSYWgt6/tpwuOH5lcfNfHWMcCYXR
lobv0Klu8lxG5amWqAnqrH6ECOyYJTRbHTsaTIZOHy9Qw/0eXPujKT7tU5xxSI2SdceJqzUbAz2o
FRQ6Px7/GydpM/Rl+qYoGPcauHUL1aSeVJZqDFqcIF0CAwEAAaOCATwwggE4MBIGA1UdEwEB/wQI
MAYBAf8CAQAwRgYDVR0gBD8wPTA7BgcqhXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVw
b3NpdG9yeS50cnVzdC50ZWxpYS5jb20wgYkGA1UdHwSBgTB/MH2ge6B5hndsZGFwOi8vbGRhcC50
cnVzdC50ZWxpYS5jb20vY249VGVsaWFTb25lcmElMjBQdWJsaWMlMjBSb290JTIwQ0ElMjB2MSxv
PVRlbGlhU29uZXJhJTIwR3JvdXA/YXV0aG9yaXR5cmV2b2NhdGlvbmxpc3Q/YmFzZTAOBgNVHQ8B
Af8EBAMCAQYwHQYDVR0OBBYEFJYnw7jepV9dRD45UuVFsXZfYzCbMB8GA1UdIwQYMBaAFEXb8I+4
GmKhqCMbY4g4o9vgGmLxMA0GCSqGSIb3DQEBBQUAA4IBAQB2AEoqQz+M3Ra9alkpn/YnwhXIv6tP
jhUvSuNs00Nhd0T9XhlIU3a65CaB/UKSqnayE0t7Q0Qq3r+x/GK3in/mik8i/PK2/q8HutzYFSzz
6Npztpo2JG7AEKOJPVaeebjng45m6vNC7RIfzU9sG2LBR/hewS8s6dFFn70w795xUwJBWZ67OzIK
XrIVVvHTOYpbWA+MESKAXwFhnVONrOTWlVwrMUi4HbiPWpOk+xQbgehCEi7mu3cXsaU1Xq3kMXui
NuC7VKoob8mFO9o9RT+dlirD2uRXwNpvCu3but6Kyhu0+nvy2iXGKjdlxlWTsdDyulXYz+OYCMZ9
lFWRzMIPMIIEbTCCA1WgAwIBAgIRAJywjASay5cieGNithuGWj0wDQYJKoZIhvcNAQEFBQAwOjEZ
MBcGA1UEChMQUlNBIFNlY3VyaXR5IEluYzEdMBsGA1UECxMUUlNBIFNlY3VyaXR5IDIwNDggVjMw
HhcNMDYxMDMxMjA0MjI3WhcNMTYxMTAxMTU0MjI1WjBEMRowGAYDVQQKDBFUZWxpYVNvbmVyYSBH
cm91cDEmMCQGA1UEAwwdVGVsaWFTb25lcmEgUHVibGljIFJvb3QgQ0EgdjEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDKTxADapCAq3mplX4R4gNt+WZe5QKGnaVEQSyY7lICKF5DuVdW
PMLHDjzhw5IzDd860ZZx/0VrhGB3DmP4SDIWCKo2PxvY5NckdBWPWp/T2uaQdOAwgqHpN0pe1X7/
jel59WsWYXKGg/81Wth73ZK/geE7Gz9Pvj1LU6N4YhLMgooxKnCS+ZjB5icWAg+Qd1QpQhF46H1i
bp6LsBWDp56MPpg8F5X6y7MGVcKYLdnLOPs84uxRW9qs1kBopzQBj6s5SyVh8A+j5liDBjghXYpw
/+paGEdqHPeSFYxZKeJatmjEKLYlxcZWRKf436KvQA9jBhMEmytMNbGicR1mRH6tAgMBAAGjggFi
MIIBXjAfBgNVHSMEGDAWgBQHw1EwpKrpRa41JPr/JCwz0LGdjDAdBgNVHQ4EFgQURdvwj7gaYqGo
IxtjiDij2+AaYvEwEgYDVR0TAQH/BAgwBgEB/wIBBDCBhQYDVR0gBH4wfDA9BgkqhkiG9w0FBgEw
MDAuBggrBgEFBQcCARYiaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhLmNvbTA7BgcqhXAj
AgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wcAYD
VR0fBGkwZzBloGOgYYZfaHR0cDovL3d3dy5yc2FzZWN1cml0eS5jb20vcHJvZHVjdHMva2Vvbi9y
ZXBvc2l0b3J5L2NlcnRpZmljYXRlX3N0YXR1cy9SU0FfU2VjdXJpdHlfMjA0OF92My5DUkwwDgYD
VR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUAA4IBAQAEXpos2CnIm7/872ytSrEHWZgvhOUEkUm2
5PWf/XkWko41TaL9vIS1S6AdWChNqWmnYiS7GfaIiDM9s1D6K7hidWBDOm46bNdM3ZwhMyDCfkDJ
SgeJ0w+7YmjvChu7gWqDZCsbtZ5gA1ixCTdDnuZB67JGSPGW6r73coraDP8diOpiQouMvM6bKuTP
BH/1poLccsUxsKgrQ23JC9LWCRb8cYHkZjXFH1K44TsIl5Lne2oT0JI3pwdA2v6jO4p/OLHntP+n
pjwPbedMPUZkDYCkd3LSxj8c3JTxtA8SlPCtIHE1hh65xihg1JRIliSphrqr9kbfwHdeVxPdOI5G
tDYPMYICEjCCAg4CAQEwTTA5MREwDwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24g
TkwgSW5kaXZpZHVhbCBDQTAxAhAhVsFUBw1ddjP0q9Mjb9LGMAkGBSsOAwIaBQCgggEbMBgGCSqG
SIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDgyMTIxMjMxN1owIwYJKoZI
hvcNAQkEMRYEFEshoLp4opDZQohbuujBel2Ep+gWMFwGCSsGAQQBgjcQBDFPME0wOTERMA8GA1UE
CgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcN
XXYz9KvTI2/SxjBeBgsqhkiG9w0BCRACCzFPoE0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNV
BAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcNXXYz9KvTI2/SxjANBgkqhkiG
9w0BAQEFAASBgC4WuV8v66Y4v/CoLHHc69Hz53/f1oLBh+hrCRtH5ZBag45IlivW5P6j0o8isvki
owvVxnWEqF/DnuRz44Cr4Dlg2mZYPM5bGmNoOO2CfR+6PXBYYgfTTJnE/JAHFViPIZO6rcZE1xmH
0QDG8sVDLfUf/p97m3bJQZGZZef8hObwAAAAAAAA

--Apple-Mail-34-57293588--

From barryleiba@gmail.com  Tue Aug 21 14:27:59 2012
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFB8A21F865D for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 14:27:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.008
X-Spam-Level: 
X-Spam-Status: No, score=-103.008 tagged_above=-999 required=5 tests=[AWL=-0.031, 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 10vziPvv8DRR for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 14:27:58 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5D34921F863F for <ietf@ietf.org>; Tue, 21 Aug 2012 14:27:58 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so326031vbb.31 for <ietf@ietf.org>; Tue, 21 Aug 2012 14:27:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=rzbadMpdwviECI1x4UMxD1a8A01Elc6ljo2Yp7MsTrk=; b=W1spcQIx/gFVlFxGIlGkoOxwjun2F54hQGrFUiY3oW9XE1kCsKnUbTo7H8l8YDuynf yOFqiiN3r1njIteeYlYowwNjBcK6kzrUicH4hZ/kHVYfiIG8/XbX5C/6n677vi21h89l zlxlQWXRR1PxmTUVpm7hWbcFvIM1UZdMBpUEteKnlUBmNwAWFzRaDvTRU9GaYVMKwBGO Xkh7WzDIrS8H1FLVP8yoDM9fttrJ5eQiffuVBj+zKDN+e1zIvo5MM71flzT+7xFuUicX 6Ig9tQ1Ts40EKJWwQkDHSBJ9N/e24vGAT5dp6G77ETXiDPIVocw10cc5sUDYILSb/BPe woSQ==
MIME-Version: 1.0
Received: by 10.52.17.48 with SMTP id l16mr2345330vdd.98.1345584477686; Tue, 21 Aug 2012 14:27:57 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.58.58.41 with HTTP; Tue, 21 Aug 2012 14:27:57 -0700 (PDT)
In-Reply-To: <ABDF3549-3C24-4AD5-985C-5E1560A80D83@gmail.com>
References: <133201cd7f85$325f59a0$971e0ce0$@olddog.co.uk> <ABDF3549-3C24-4AD5-985C-5E1560A80D83@gmail.com>
Date: Tue, 21 Aug 2012 17:27:57 -0400
X-Google-Sender-Auth: _Vhg92qIRghyMkmGqbnAK84X3HM
Message-ID: <CALaySJ+nogfk2n8u10PyaBLOhytnsXtB7Cj+DNBFaO7r4BJ3Jg@mail.gmail.com>
Subject: Re: Some thoughts about draft-leiba-3777upd-eligibility-02.txt
From: Barry Leiba <barryleiba@computer.org>
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: draft-leiba-3777upd-eligibility@tools.ietf.org, adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2012 21:27:59 -0000

> I assume the intent is exclude people who are paid by the IETF to do
> work in the IETF.  For example, the IAD.

Correct.

> In these cases it difficult to tell if an individual is working for the
> IETF "long-term full-time work".

Indeed; it's difficult in many cases.

> If this text is to remain, it needs to be clearer as to what it means.

Which may say that it should not remain.

The specific exclusions that are in the real "rules" part are for the
IETF Secretariat and the RFC Editor.  I would be just as happy to
remove those.  We can question whether we want to leave the RSE in,
specifically, but there's probably no real need to exclude the paid
RFC Editor function employees.  I'll note that the IAD is already
excluded by the "ex-officio" clause (he's an ex-officio IAOC member).
The current IAD has told me that he thinks it would be inappropriate
for the IAD to volunteer in any case, whether or not he's allowed to.

Margaret has commented that this stuff should come out.  Others, in
early conversations and discussions about all of this, thought it
should be in.  Further comments appreciated.

In particular: should bullet 15,2 (and its supporting text elsewhere)
be removed?

Barry

From sm@elandsys.com  Tue Aug 21 14:36:02 2012
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BEFA21F86A5 for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 14:36:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 DvZXUK-HIC7e for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 14:36:01 -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 AC54721F86A2 for <ietf@ietf.org>; Tue, 21 Aug 2012 14:36:01 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.234.105]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q7LLZe6E022176 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 21 Aug 2012 14:35:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1345584955; bh=NNV0ar5i0p52DSBKtENanY/DIvVuhBFEBVCpwmjI6c8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=EQG8rVtrk7ixpiBxCoeDF4XlJ8AJ/cu2MQu7d7H2/RBPHMVhnu0OtugC1nMGLy91F LFOciWkrkMPJttUm7q1PbkCaph4JGHtsbQPzb7j+lSSnQ3DBT3hVJ6Ihbf1zLQrnvh iL97Ow7w1dZdjAwdSh/K2AtcTizJ6lhit7L6kfGc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1345584955; i=@elandsys.com; bh=NNV0ar5i0p52DSBKtENanY/DIvVuhBFEBVCpwmjI6c8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=3BmISNPaktRnwvSUmJ4gk0VHnex6c7CRLZFsy1iNaE46FPJ91EDZk5uwD6vqPzG+k JkFmtktue8Fk7o093dnKulD3GWRE0hLGKf0Y5Ddwynnfv7TnD0UIGpFH3W6ECQvXvJ yGcHIn2HHdbOyfmuvAnoipF+76iB6mY1mXdFuJ+8=
Message-Id: <6.2.5.6.2.20120821123650.0a0ee688@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 21 Aug 2012 14:13:50 -0700
To: adrian@olddog.co.uk, Donald Eastlake <d3e3e3@gmail.com>, Margaret Wasserman <margaretw42@gmail.com>, Bob Hinden <bob.hinden@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Some thoughts about draft-leiba-3777upd-eligibility-02.txt
In-Reply-To: <CAC4RtVB=N=CP7ManPZ=Hu65QbrX5WXnWRFFDZ-CpOcKQyqRWqg@mail.g mail.com>
References: <133201cd7f85$325f59a0$971e0ce0$@olddog.co.uk> <CAC4RtVB=N=CP7ManPZ=Hu65QbrX5WXnWRFFDZ-CpOcKQyqRWqg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: draft-leiba-3777upd-eligibility@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2012 21:36:02 -0000

At 12:34 21-08-2012, Barry Leiba wrote:
>I do, and I actually had the same problem with it when I wrote it as
>you do.  So help me, please: How *should* this be put?  I don't like,
>"and those employed in the RFC Editor function," and I really can't
>think of a concise, clean, accurate way to write it down, though we
>all (today) know what it means.  Text, please, someone.

RFC 4844 (see Section 3.1) uses the term "RFC Editor".  RFC 6635 
mentions "RFC Editor function".  I suggest going with the RFC 4844 
argument about simplicity and using "RFC Editor".  I cannot think of 
an accurate way to write that paragraph.

>I'm inclined to pull it out (having not checked that with SM yet,
>though).  Does anyone (including SM) think it definitely needs to be
>in here?

I don't have a strong opinion about the erratum.  Pull it out.

At 12:45 21-08-2012, Donald Eastlake wrote:
>In particular, I believe the there are Editorial Boards that the
>various fragments of the RFC Editor appoint and consult which should
>not be excluded.

These bodies were left out.  There is a comment in the draft labelled 
as anchor1.

At 13:11 21-08-2012, Margaret Wasserman wrote:
>Why do you want to rule out employees of those groups?
>
>I don't think that most of them would have any interest in 
>volunteering for the nomcom, but why would it be a problem if they 
>did?  I mean, I could picture someone who worked for the RFC Editor 
>who was also technically involved in the IETF, like Aaron Falk used 
>to be, and I don't know why we would want to disqualify someone like 
>that from volunteering for the nomcom.

I'll comment as part of the message which Adrian posted.

At 03:10 21-08-2012, Adrian Farrel wrote:
>However, the document very quickly launches into a discussion of other
>people to exclude from NomCom. It does this by introducing the concept
>of a "conflict of interest." There may be a valid debate to have about
>conflict of interest, but I personally find it a very long wedge, and
>although there may be clear-cut cases at either extreme, it is by no
>means clear where to draw the line.

Yes.

>I find the excuse used (that those excluded are unlikely to volunteer)
>as rather poor taste. It may be true that such people have not
>volunteered in the past, but that should not be used as a reason. You
>are removing rights that people previously had - you should have good,
>stand-alone reasons and not depend on whether or not earlier holders of
>certain posts exercised those rights.

The last sentence broaches an interesting angle.  From RFC 3777:

   "The IETF Secretariat is responsible for confirming that
    volunteers have met the attendance requirement."

   "The IETF Secretariat is responsible for confirming that each
    signatory is qualified to be a voting member of a nominating
    committee."

As the IETF Secretariat has duties in the RFC 3777 mechanism, would 
it be a good stand-alone reason to remove the right to be a volunteer?

The RSE and ISE are under contract with the IAOC.  The other part of 
the RFC Editor (function) are external organizations.

At 13:52 21-08-2012, Bob Hinden wrote:
>While on this topic, we might as well get it right.  The text in the draft is:
>
>    This document also excludes certain individuals who are directly paid
>    for their work with the IETF, and who, therefore, have a direct
>    personal financial incentive in the selection of the leadership
>    boards.  We limit this exclusion to a few people who are paid for
>    long-term full-time work.  In practice, they are unlikely to
>    volunteer for the NomCom anyway, so this addition makes little
>    practical change.
>
>I assume the intent is exclude people who are paid by the IETF to do 
>work in the IETF.  For example, the IAD.  The problem is that no one 
>is paid by the IETF.  The IETF has several people who do work at 
>it's direction.  This is done as direct employees of ISOC or as 
>contractors who have their contracts with ISOC.  We also hire (via 
>ISOC) companies that provide services to the IETF.  This ranges from 
>the secretariat services, NOC services, tools development, program 
>management services, and tools specification development.  In these 
>cases it difficult to tell if an individual is working for the IETF 
>"long-term full-time work".

Ok. :-)

>Further, the text as written could be interpreted to exclude people 
>who's employers pay they to participate in the IETF.  For example, 
>that would include me because it is part of my job to participate in 
>the IETF.  I don't think that is the intent of the text in the 
>draft, but it would be easy to interpret it that way.  OK, maybe I 
>don't do it full time, but all of the IESG position require full time support.

It is the additions to RFC 3777 that matters as they become part of 
the RFC 3777 rules.

I'll discuss about the comments with Barry before commenting further.

Regards,
S. Moonesamy 


From bob.hinden@gmail.com  Tue Aug 21 15:10:36 2012
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 635CE21F86D1 for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 15:10:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.511
X-Spam-Level: 
X-Spam-Status: No, score=-103.511 tagged_above=-999 required=5 tests=[AWL=0.088, 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 M3Dn2F3SikpS for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 15:10:35 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id D896521F86D0 for <ietf@ietf.org>; Tue, 21 Aug 2012 15:10:35 -0700 (PDT)
Received: by pbbrr4 with SMTP id rr4so507692pbb.31 for <ietf@ietf.org>; Tue, 21 Aug 2012 15:10:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=Y088hDIvz1ZFVjXhsFhJ9t3qlZBTljHwB9swQFESJeQ=; b=cDY+m+2M4uALSX6WKqrlxECUnWc3FGGoFANKvvuijL+tYw1FmmZjAhqEKiZzb5LjIm GrtLzY1mvqcWkIqKJeePaJX1zY0ctRuk/o0e0mxxEa9FMDVojD6LtqM3LL8kUPi5KK9W WVL+8XIm/ChKh4z3N+PJLQ7kkGCSngMFsgA11KVT1AJPxFSgRN5lNkrRW+PqTRWzdOfV 4fz+RgbnH+tAptSCTLbpO76hyhfPzUQMnNUGfbVk8ckIKNUJl8fXkbNafEjtLcgJUsTo YKJkuYT9Lh7Nlaal2Il4Z/FYVSzlNYdmPN+C5QhNdX6L0zP2nTglvxbgOvX4RqltfnXM Uwpw==
Received: by 10.66.82.167 with SMTP id j7mr6921008pay.32.1345587035530; Tue, 21 Aug 2012 15:10:35 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPS id gh9sm2258146pbc.20.2012.08.21.15.10.31 (version=SSLv3 cipher=OTHER); Tue, 21 Aug 2012 15:10:34 -0700 (PDT)
Subject: Re: Some thoughts about draft-leiba-3777upd-eligibility-02.txt
Mime-Version: 1.0 (Apple Message framework v1280)
Content-Type: text/plain; charset=windows-1252
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <CALaySJ+nogfk2n8u10PyaBLOhytnsXtB7Cj+DNBFaO7r4BJ3Jg@mail.gmail.com>
Date: Tue, 21 Aug 2012 15:10:31 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7FE6283A-6066-497B-9767-3E09D18F952B@gmail.com>
References: <133201cd7f85$325f59a0$971e0ce0$@olddog.co.uk> <ABDF3549-3C24-4AD5-985C-5E1560A80D83@gmail.com> <CALaySJ+nogfk2n8u10PyaBLOhytnsXtB7Cj+DNBFaO7r4BJ3Jg@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1280)
Cc: draft-leiba-3777upd-eligibility@tools.ietf.org, adrian@olddog.co.uk, Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2012 22:10:36 -0000

Barry,

On Aug 21, 2012, at 2:27 PM, Barry Leiba wrote:

>> I assume the intent is exclude people who are paid by the IETF to do
>> work in the IETF.  For example, the IAD.
>=20
> Correct.
>=20

Thanks.

>> In these cases it difficult to tell if an individual is working for =
the
>> IETF "long-term full-time work".
>=20
> Indeed; it's difficult in many cases.
>=20
>> If this text is to remain, it needs to be clearer as to what it =
means.
>=20
> Which may say that it should not remain.
>=20
> The specific exclusions that are in the real "rules" part are for the
> IETF Secretariat and the RFC Editor.  I would be just as happy to
> remove those.  We can question whether we want to leave the RSE in,
> specifically, but there's probably no real need to exclude the paid
> RFC Editor function employees.  I'll note that the IAD is already
> excluded by the "ex-officio" clause (he's an ex-officio IAOC member).

Right, but he is one of our two paid employees (via ISOC).

> The current IAD has told me that he thinks it would be inappropriate
> for the IAD to volunteer in any case, whether or not he's allowed to.

I agree.

>=20
> Margaret has commented that this stuff should come out.  Others, in
> early conversations and discussions about all of this, thought it
> should be in.  Further comments appreciated.

I would be OK if it called out the IAD and the RSE as being ineligible.  =
It's simpler than trying to generalize it.
>=20
> In particular: should bullet 15,2 (and its supporting text elsewhere)
> be removed?

15,2 should probably say "People employed in the IETF Secretariat=85.". =20=


I would leave it in.  My thinking is that the IESG, IAB, and IAOC have =
oversight roles over the Secretariat and RFC Editor.  Having people =
employed by these organizations be directly involved in the selection of =
the IESG, IAB, and IAOC would be odd.

Bob


>=20
> Barry


From barryleiba@gmail.com  Tue Aug 21 15:44:04 2012
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D60821F85A4 for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 15:44:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.008
X-Spam-Level: 
X-Spam-Status: No, score=-103.008 tagged_above=-999 required=5 tests=[AWL=-0.031, 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 ChiemleIxbXw for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 15:44:03 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 785AA21F85A5 for <ietf@ietf.org>; Tue, 21 Aug 2012 15:44:03 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so392988vcb.31 for <ietf@ietf.org>; Tue, 21 Aug 2012 15:44:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=my6SHs9AfVoNr0jT/3DRAqsQzYHwBd2VNzpCTm9ro4Y=; b=GbGk9PIOABvjPAf+/0gNt6HWisVvyK9YwgT7wFH7HQMBINMoGvm0LVbTF1tefUvGcp 7Va4+oYTmMkOR/XE++WDrLKVihotJAwjFfP1xq60EcDH3G3m8ZoZvNo6EgoqmooJS2L8 0y1VSB5dzIIVWUwef5rU+jMWxpMoSDcJq7Q22qI8jOcyOGreYugG8gZPWhFnA9y3/R+G nlDM1hCTQeUhmQzuE/gSePKHoUSjS+bXc8y1quM88ShRWxMjJLIxukY1c8roM529hk6V q4HEPkm8NQTPkdAkknjfqW9TmCKQ+dqysbT7lN6pEFRCh9kcpDfzBzcFvxBVY/aXR4CF wQIQ==
MIME-Version: 1.0
Received: by 10.52.95.165 with SMTP id dl5mr185607vdb.23.1345589042797; Tue, 21 Aug 2012 15:44:02 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.58.58.41 with HTTP; Tue, 21 Aug 2012 15:44:02 -0700 (PDT)
In-Reply-To: <7FE6283A-6066-497B-9767-3E09D18F952B@gmail.com>
References: <133201cd7f85$325f59a0$971e0ce0$@olddog.co.uk> <ABDF3549-3C24-4AD5-985C-5E1560A80D83@gmail.com> <CALaySJ+nogfk2n8u10PyaBLOhytnsXtB7Cj+DNBFaO7r4BJ3Jg@mail.gmail.com> <7FE6283A-6066-497B-9767-3E09D18F952B@gmail.com>
Date: Tue, 21 Aug 2012 18:44:02 -0400
X-Google-Sender-Auth: hlLRAkniyq-UATVoHPAybY5pQ1Y
Message-ID: <CALaySJJ7-LGXribUKJ-HX6Wkp-SSr8dezEmsz-bbdsapWDcVMA@mail.gmail.com>
Subject: Re: Some thoughts about draft-leiba-3777upd-eligibility-02.txt
From: Barry Leiba <barryleiba@computer.org>
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: draft-leiba-3777upd-eligibility@tools.ietf.org, adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2012 22:44:04 -0000

>> In particular: should bullet 15,2 (and its supporting text elsewhere)
>> be removed?
>
> 15,2 should probably say "People employed in the IETF Secretariat=85.".
>
> I would leave it in.  My thinking is that the IESG, IAB, and IAOC have ov=
ersight
> roles over the Secretariat and RFC Editor.  Having people employed by the=
se
> organizations be directly involved in the selection of the IESG, IAB, and=
 IAOC
> would be odd.

Yes, that was the intent of having it in.  The devil, though, is in the det=
ails.

Do others have wisdom to add here?

Barry

From mcr@sandelman.ca  Tue Aug 21 17:42:01 2012
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 19EA321F8567 for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 17:42:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level: 
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[AWL=0.036,  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 KryRq2WViknZ for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 17:42:00 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 9E75821F855F for <ietf@ietf.org>; Tue, 21 Aug 2012 17:42:00 -0700 (PDT)
Received: from sandelman.ca (24-139-16-154.eastlink.ca [24.139.16.154]) by relay.sandelman.ca (Postfix) with ESMTPS id 32297865B for <ietf@ietf.org>; Tue, 21 Aug 2012 20:36:53 -0400 (EDT)
Received: from sandelman.ca (quigon.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 5137ACA0C9 for <ietf@ietf.org>; Tue, 21 Aug 2012 20:04:50 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF Disgust <ietf@ietf.org>
Subject: Re: IETF 92 in Dallas!
In-reply-to: <m2txvwoimp.wl%randy@psg.com>
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net> <BA2EE8F7-92C8-4F10-B10A-2B6FE4FC954A@gmail.com> <502E9614.30409@raszuk.net> <502E9841.8070205@bogus.com> <502E9982.5080909@raszuk.net> <502F4A2A.8090005@krsek.cz> <CD5674C3CD99574EBA7432465FC13C1B22726A1E35@DC-US1MBEX4.global.avaya.com> <503313DE.4090401@gmail.com> <m2txvwoimp.wl%randy@psg.com>
Comments: In-reply-to Randy Bush <randy@psg.com> message dated "Tue, 21 Aug 2012 15:37:34 +0900."
X-Mailer: MH-E 8.3; nmh 1.3; XEmacs 21.4 (patch 22)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 21 Aug 2012 20:04:50 -0400
Message-ID: <19159.1345593890@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, 22 Aug 2012 00:42:01 -0000

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


>>>>> "Randy" =3D=3D Randy Bush <randy@psg.com> writes:
    Randy> sorry, but enough is enough.

I still do not understand visiting a tourist destination (Orlando)=20
during it's peak (March).   I also don't understand two meetings in a
row on the US east coast.=20

=2D-=20
Michael Richardson
=2Dat the cottage-

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

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

iQEcBAABAgAGBQJQNCIiAAoJEKD0KQ7Gj3P2904IALzu6Fv9Lu15qyVcEfgk0OTQ
qfjLKiT525az4N8YGQnNqusZib198BvMc/MDz2MDJKDVAE/UJNZ6o+7HeZmNQ1Gw
H6cvCEcIGPqhhZhHEB9hmhOblyRgbXwnx6e1LdSY2c5zedQDzz3NtsMc4zttYFqR
i/+dfZ+37SZGhLo7Z9FHXKpTH9BDIX6MZH2VltWJWoUoEBH3g0eEUogjywoEXtX+
Dsx06C7QSyQAS3oocExhNNFHjzJjgMlc5GKRM2Hgiw+Angvb5ETvb7253+XK33R4
64a146cnRvlrWD42dxsr/2enagbMYRjISM2iWRXzFfcK6lytf0GR17exvA0MV7M=
=c/IG
-----END PGP SIGNATURE-----
--=-=-=--

From rpelletier@isoc.org  Tue Aug 21 17:52:38 2012
Return-Path: <rpelletier@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C01721F85A8 for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 17:52:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.329
X-Spam-Level: 
X-Spam-Status: No, score=-103.329 tagged_above=-999 required=5 tests=[AWL=0.270, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bb99YlDgymPO for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 17:52:36 -0700 (PDT)
Received: from smtp207.iad.emailsrvr.com (smtp207.iad.emailsrvr.com [207.97.245.207]) by ietfa.amsl.com (Postfix) with ESMTP id 9E88A21F85D5 for <ietf@ietf.org>; Tue, 21 Aug 2012 17:52:35 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp30.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 06465204EC; Tue, 21 Aug 2012 20:52:35 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp30.relay.iad1a.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id DD28F20249;  Tue, 21 Aug 2012 20:52:34 -0400 (EDT)
Subject: Re: IETF 92 in Dallas!
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Pelletier Ray <rpelletier@isoc.org>
In-Reply-To: <19159.1345593890@sandelman.ca>
Date: Tue, 21 Aug 2012 20:52:34 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B21722F7-BA0D-425E-B4FC-2E949F8E44B5@isoc.org>
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net> <BA2EE8F7-92C8-4F10-B10A-2B6FE4FC954A@gmail.com> <502E9614.30409@raszuk.net> <502E9841.8070205@bogus.com> <502E9982.5080909@raszuk.net> <502F4A2A.8090005@krsek.cz> <CD5674C3CD99574EBA7432465FC13C1B22726A1E35@DC-US1MBEX4.global.avaya.com> <503313DE.4090401@gmail.com> <m2txvwoimp.wl%randy@psg.com> <19159.1345593890@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Aug 2012 00:52:38 -0000

On Aug 21, 2012, at 8:04 PM, Michael Richardson wrote:

>=20
>>>>>> "Randy" =3D=3D Randy Bush <randy@psg.com> writes:
>    Randy> sorry, but enough is enough.
>=20
> I still do not understand visiting a tourist destination (Orlando)=20
> during it's peak (March).   I also don't understand two meetings in a
> row on the US east coast.=20

The first, Atlanta, IETF 85, was slipped to 2012 to accommodate an =
opportunity to go to Asia (Beijing) in Nov 2010, and the second is =
Orlando, IETF 86, in March 2013 to close on an opportunity to do a =
back-to-back meeting with IEEE 802.  Orlando was booked first then the =
stars aligned for Beijing and we couldn't pass it up.  The Hilton =
Atlanta contract permitted a postponement of two years without penalty, =
so we took advantage of the provision.

Ray
IAD



>=20
> --=20
> Michael Richardson
> -at the cottage-


From randy@psg.com  Tue Aug 21 18:52:26 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BA2211E8099 for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 18:52:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.546
X-Spam-Level: 
X-Spam-Status: No, score=-2.546 tagged_above=-999 required=5 tests=[AWL=0.053,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4V5abua4hvGr for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 18:52:25 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 19CEB11E8091 for <ietf@ietf.org>; Tue, 21 Aug 2012 18:52:25 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80 (FreeBSD)) (envelope-from <randy@psg.com>) id 1T407L-0000Kp-4o; Wed, 22 Aug 2012 01:52:23 +0000
Date: Wed, 22 Aug 2012 10:52:42 +0900
Message-ID: <m2k3wrn15h.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: IETF 92 in Dallas!
In-Reply-To: <19159.1345593890@sandelman.ca>
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net> <BA2EE8F7-92C8-4F10-B10A-2B6FE4FC954A@gmail.com> <502E9614.30409@raszuk.net> <502E9841.8070205@bogus.com> <502E9982.5080909@raszuk.net> <502F4A2A.8090005@krsek.cz> <CD5674C3CD99574EBA7432465FC13C1B22726A1E35@DC-US1MBEX4.global.avaya.com> <503313DE.4090401@gmail.com> <m2txvwoimp.wl%randy@psg.com> <19159.1345593890@sandelman.ca>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Aug 2012 01:52:26 -0000

> I still do not understand visiting a tourist destination (Orlando)
> during it's peak (March).  I also don't understand two meetings in a
> row on the US east coast.

there are lots of things i do not understand.  i try to focus on those
i need to in order to do good work.  that's hard enough.

randy

From john-ietf@jck.com  Wed Aug 22 04:16:03 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 379BF21F861B for <ietf@ietfa.amsl.com>; Wed, 22 Aug 2012 04:16:03 -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 9-1eYyuY29qH for <ietf@ietfa.amsl.com>; Wed, 22 Aug 2012 04:16:02 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 90DAE21F84CD for <ietf@ietf.org>; Wed, 22 Aug 2012 04:16:02 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1T48uf-000LJk-Dr; Wed, 22 Aug 2012 07:15:53 -0400
Date: Wed, 22 Aug 2012 07:15:48 -0400
From: John C Klensin <john-ietf@jck.com>
To: Bob Hinden <bob.hinden@gmail.com>, Barry Leiba <barryleiba@computer.org>
Subject: Re: Some thoughts about draft-leiba-3777upd-eligibility-02.txt
Message-ID: <F6CE6B7895D4FCF5B9F8AB5D@JcK-HP8200.jck.com>
In-Reply-To: <7FE6283A-6066-497B-9767-3E09D18F952B@gmail.com>
References: <133201cd7f85$325f59a0$971e0ce0$@olddog.co.uk> <ABDF3549-3C24-4AD5-985C-5E1560A80D83@gmail.com> <CALaySJ+nogfk2n8u10PyaBLOhytnsXtB7Cj+DNBFaO7r4BJ3Jg@mail.gmail.com> <7FE6283A-6066-497B-9767-3E09D18F952B@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Cc: draft-leiba-3777upd-eligibility@tools.ietf.org, adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Aug 2012 11:16:03 -0000

--On Tuesday, August 21, 2012 15:10 -0700 Bob Hinden
<bob.hinden@gmail.com> wrote:

>> In particular: should bullet 15,2 (and its supporting text
>> elsewhere) be removed?
>=20
> 15,2 should probably say "People employed in the IETF
> Secretariat=E2=80=A6.". =20
>=20
> I would leave it in.  My thinking is that the IESG, IAB, and
> IAOC have oversight roles over the Secretariat and RFC Editor.
> Having people employed by these organizations be directly
> involved in the selection of the IESG, IAB, and IAOC would be
> odd.

Bob,

There is a slippery slope of trying to make hair-splitting rules
here that I've very reluctant to see the community to start
down.  However, if one were trying to write such rules based on
real risk of inappropriate behavior --rather than leaving those
risks in place and focusing on the appearance of oddity-- it
seems to me that the focus might better be on those who bid on
or obtain short-term contracts to do specific work, such as
specification-writing or implementation, for the IETF.
Precisely because they are short-term (in both the RFP->
Contract Award -> Performance period) and because they
apparently often involve working much more closely with a few
IAOC or IESG members (although I'm not aware of its being done
in recent years, presumably anyone hired by the IAB to write a
workshop report would be in the same category), those
contractors have much more potential for "you scratch my back,
I'll scratch yours" relationships than individuals who are not
subject to direct supervision from the I* leadership.

I want to stress that I'm not aware of even the suspicion of
anything improper occurring in this area in the past.   I
continue to believe that we would be better off with general
guidance that people who are significantly dependent financially
on the IETF via ISOC or equivalent funding for IETF activities
should avoid volunteering for the Nomcom than with trying to
establish rules that are exactly right and avoid all loopholes
in them.  In practice, I'm much more concerned about the
potential for companies (or closely-aligned groups of companies)
to "pack" the Nomcom than I am for abuse from groups of people
who have generally avoided volunteering for the Nomcom in the
past.    But, if we need to try to write precise rules, let's
try to identify and sweep in all of the important cases, not
just obvious ones with bad optics but little practical risk.

best,
   john

     john


From abdussalambaryun@gmail.com  Wed Aug 22 06:17:49 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28C0E21F8450; Wed, 22 Aug 2012 06:17:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.49
X-Spam-Level: 
X-Spam-Status: No, score=-3.49 tagged_above=-999 required=5 tests=[AWL=0.109,  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 8jUQclTyUvwL; Wed, 22 Aug 2012 06:17:45 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id D10B621F8489; Wed, 22 Aug 2012 06:17:44 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so1121403vbb.31 for <multiple recipients>; Wed, 22 Aug 2012 06:17:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2auV3pf8oqdtHmgh3W37lWfsEknVvM6MUA19rZ9Xx6w=; b=rGHv58b+pIZIlRPHPqDlJXIO1vzHB3K7J0QgeBwGt8CnxOrhxR0F7Ht046GYKli5Ci cwzZv1kVgmOqMDQjac9Re2I1tBupUHnWpGL/7zPIceR5u75Ix+ZC0tPxQs4L8ZFMt51r OjaXzmgC5mzod38W2DLfHwKwDroZvYEjhhXx6fMJsInzOeinNJk+miO++MXJ1GeDGWXp zQpAlTcgPmySXhz0PLqN+KaFyDT1gFANz5c0+wQiixTwHMrQBqceUtYMG7joKo5yXW5N lrNegzFUT+y0AQES8k5hGfkfHUP5H3D21wrBVv6lfyoW0XjnpGvxogH9h7qDKE8u//aD 2ptw==
MIME-Version: 1.0
Received: by 10.58.12.231 with SMTP id b7mr18131951vec.28.1345641463993; Wed, 22 Aug 2012 06:17:43 -0700 (PDT)
Received: by 10.220.55.9 with HTTP; Wed, 22 Aug 2012 06:17:43 -0700 (PDT)
In-Reply-To: <20120728232737.23974.14830.idtracker@ietfa.amsl.com>
References: <20120728232737.23974.14830.idtracker@ietfa.amsl.com>
Date: Wed, 22 Aug 2012 15:17:43 +0200
Message-ID: <CADnDZ89YvrdvadRvCEYQA3nux-pdHH9kF5+Bqz-07gWpgYiB+A@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-manet-olsrv2-15.txt> (The Optimized Link State Routing Protocol version 2) to Proposed Standard
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "iesg@ietf.org" <iesg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Aug 2012 13:17:49 -0000

Reply to your request dated 29/08/2012

Draft Reviewed By: Abdussalam Baryun (AB)    Dated:22/08/2012

Reviewer Comment  AB2:  Related to OLSRv2 Packets.
++++++++++++++++++++++++++++++++++++++++

-The reviewer is not sure how/when the OLSRv2 generates packets
[RFC5444] or how it puts information in the packet. The I-D refers
back to the RFC5444 document but the document is a general
specification for all MANET routers, the reviewer thinks it is
important that OLSRv2-draft mentions what/how the OLSRv2 node puts
information in RFC5444 header or how a node uses the header
information.

-In OLSRv2-draft section 13.2 > This specification does not define or
use any contents of the Packet Header.
The reviewer does not know why the router generates the packet and
does not use, or the reviewer does not know who generates it.

-RFC5444 specifies that IANA is registering namespaces for: Message
Types, Packet TLV Types, Message TLV Types, and Address Block TLV
Types.
OLSRv2-draft IANA consideration section does not mention any assign
for packet header related to OLSRv2 as in RFC5444 section 6.3 (e.g.
Packet TLV Types).

Regards
AB
---------------------------------------------------------------------------------------
This message and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
This message is in compliance with the IETF regulations.
---------------------------------------------------------------------------------------

On 7/29/12, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from the Mobile Ad-hoc Networks WG
> (manet) to consider the following document:
> - 'The Optimized Link State Routing Protocol version 2'
>   <draft-ietf-manet-olsrv2-15.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-08-22. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting. This last call
> period has been extended to handle the fact that it spans the IETF-84
> meeting.
>
> This last call is being re-initiated to include a notice that this document
> includes a normative down reference to an Informational RFC:
> RFC5148, "Jitter considerations in MANETs".
>
> Abstract
>
>    This specification describes version 2 of the Optimized Link State
>    Routing (OLSRv2) protocol for Mobile Ad hoc NETworks (MANETs).
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>

From adrian@olddog.co.uk  Wed Aug 22 10:02:18 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3187F21F8629 for <ietf@ietfa.amsl.com>; Wed, 22 Aug 2012 10:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.528
X-Spam-Level: 
X-Spam-Status: No, score=-2.528 tagged_above=-999 required=5 tests=[AWL=0.070,  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 rhq5qzRe70L2 for <ietf@ietfa.amsl.com>; Wed, 22 Aug 2012 10:02:10 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 9736D21F860B for <ietf@ietf.org>; Wed, 22 Aug 2012 10:02:09 -0700 (PDT)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7MH1tFI026088;  Wed, 22 Aug 2012 18:01:55 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7MH1pTK026067 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 22 Aug 2012 18:01:52 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Shew, Stephen'" <sshew@ciena.com>, "'Acee Lindem'" <acee.lindem@ericsson.com>, "'Ong, Lyndon'" <Lyong@ciena.com>
References: <A0B4FC0A5EFBD44585414760DB4FD2749F512AA9@MDWEXGMB02.ciena.com> <D3266962-DD41-4FBA-A0A2-E1F9D5BF2B3C@ericsson.com> <510C3D5C5DFBCB46AE189D936C1DD605A60CC92886@ONWVEXCHMB02.ciena.com>
In-Reply-To: <510C3D5C5DFBCB46AE189D936C1DD605A60CC92886@ONWVEXCHMB02.ciena.com>
Subject: RE: Last Call: <draft-ietf-ccamp-rfc5787bis-05.txt> 
Date: Wed, 22 Aug 2012 18:01:49 +0100
Message-ID: <15e901cd8087$d29542b0$77bfc810$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_15EA_01CD8090.3466CA10"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJ+lUzGTIe82Frm9aji7BxsJkhI0ALTX7L3Adhqy/GV3oTUYA==
Content-Language: en-gb
Cc: draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org, "'Andrew G. \(Andy\) Malis'" <andrew.g.malis@verizon.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Aug 2012 17:02:18 -0000

This is a multipart message in MIME format.

------=_NextPart_000_15EA_01CD8090.3466CA10
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi Stephen,
 
No, there is no requirement for the control plane topology to match the data
plane topology in GMPLS. There is simply a 1:1 mapping between identifiers. We
might note, however, that there is a virtual overlay in the SCN such that
protocol controllers that control devices that are adjacent in the data plane
can be made virtually adjacent in the control plane.
 
Your final assumption is how an operator might manage their network. But it is
not a requirement since mappings can always be made at domain boundaries.
 
Adrian
 
From: Shew, Stephen [mailto:sshew@ciena.com] 
Sent: 22 August 2012 17:35
To: Acee Lindem; Ong, Lyndon
Cc: ietf@ietf.org; draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org; Andrew G.
(Andy) Malis
Subject: RE: Last Call: <draft-ietf-ccamp-rfc5787bis-05.txt> 
 
Thanks for the reply. If I understand correctly, this means that the SCN
topology must match the transport topology when applying OSPF for ASON routing.
This is because the Local TE Router Identifier and the Remote TE Router
Identifier in the Local and Remote TE Router ID sub-TLV are the same as the TE
Router ID in the TE Router Address TLV. If this is correct, then I think the
draft should state the assumption that the SCN topology and transport plane
topology are aligned. It's an important assumption to state since management
systems of SDH/OTN networks have topologies of the transport network in non-IP
address formats (esp. TL-1 TIDs) and these need to be mapped to TE Router IDs in
the SCN space when this draft is applied.  I assume it implies that there should
be a single SCN or non-overlapping IP address spaces if there are multiple SCNs,
for a given transport topology otherwise the SCN topology representing the
transport topology could have duplicate identifier values.
 
Stephen
 
From: Acee Lindem [mailto:acee.lindem@ericsson.com] 
Sent: 21 August, 2012 17:23
To: Ong, Lyndon
Cc: ietf@ietf.org; Shew, Stephen;
draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org; Andrew G. (Andy) Malis
Subject: Re: Last Call: <draft-ietf-ccamp-rfc5787bis-05.txt> 
 
Hi Stephen, Lyndon, 
Andy and I have had discussions with the CCAMP chairs and AD. We have come to
the conclusion that we cannot merely change the name space for the advertised TE
Router ID since this would imply a change to the GMPL model for setting up LSPs.
In GMPL, the LSP endpoints are in the Signaling Control Network (SCN) and this
cannot be changed without a distinct model for ASON LSP establishment complete
with the specification of the changes to path computation, RSVP path signaling,
and RSVP Explicit Route Object (ERO) handling. In essence, this change would add
a level of indirection from the SNPP to the SCN. In the context of this draft,
we are not going to deviate from the GMPLS LSP model and, hence, will not
incorporating the suggested changes. 
Thanks,
Acee 
On Aug 17, 2012, at 7:58 PM, Ong, Lyndon wrote:
 
(Submitted on behalf of Stephen Shew)
 
I would like to raise an issue with draft-ietf-ccamp-rfc5787bis-05.txt.  The
issue does not affect the proposed sub-TLVs or their semantics, so it would not
affect an implementation. I believe some statements in the document should be
edited to avoid confusion over ASON terminology as defined in ITU-T
Recommendation G.8080, for which I am editor.
 
It concerns the definition of "ASON reachability" which changed during the
course of the document from being a transport plane address, the SubNetwork
Point Pool (SNPP) space, to the Signalling Control Network (SCN) address space.
I think the root of the issue is that the visibility of the three address spaces
described in ASON (G.8080) is not always made clear when discussing using OSPF
for ASON Routing.  Section 3 of G.8080 states that:
There are three categories of identifiers used for ASON routing
   (G7715.1): transport plane names, control plane identifiers for
   components, and Signaling Communications Network (SCN) addresses.
 
In -03 of the document, the term SNPP was used. This is the SubNetwork Point
Pool space that describes the data plane and is defined in G.8080 Section 10.
It names the subnetwork (and/or containing subnetworks) to which Subnetwork
Points (SNPs) are scoped. From G.8081: "The SNP is an abstraction that
represents an actual or potential underlying connection point (CP) (or
connection termination point (CTP)) or an actual or potential termination
connection point (TCP) or trail termination point (TTP). Several SNPs (in
different subnetwork partitions) may represent the same TCP or CP."
 
In concrete terms, an SNPP would name an OTN switch, and an SNP would be a label
identifying an ODU0.  For the topology of the transport plane, SNPP and SNPP
link names are used.  Path computation is performed over such a topology.  If a
path can be computed between two SNPPs, they are reachable in ASON terms. For
example, and ingress OTN switch for an ODU1 connection that terminates on an
egress OTN switch.
 
The Signalling Control Network (SCN) is a separate network over which control
messages are sent. It has a topology independent of the transport plane.  Path
computation on the SCN address space is used to connect SCN address.  SDH/OTN
networks often have a separate IP network as the SCN network and the topology of
the SCN network does not have to follow the topology of the transport network.
 
ASON Control Plane Component identifiers are the third name space and identify
routing and signalling instances.  It is expected that they form adjacencies
over the SCN.  The topology of the adjacencies is independent of the SCN and
transport plane topologies.  "Reachability" between two control plane components
would be some sequence of adjacencies.  It is entirely possible to have two
separate control planes running over the same SCN network, or one control plane
that uses several SCNs.  For example, imagine some OSPF instances whose
adjacencies were all targeted and each adjacency traversed a separate private IP
network.  The OSPF instances would need to identified by a common address space
so that they are distinguished from each other, but the TE interfaces could have
overlapping IPv4 values because they would be in different private IP network
spaces.
 
What makes the discussion of "TE router ID" confusing is that as applied to a
transport network, every node gets a "TE router ID" and so it can be used in the
transport topology for path computation.  In that sense it is "reachable" in the
dataplane.  However, it is also (I think) an address that is implicitly in the
SCN space in some implementations and so it takes on a dual meaning of
"reachability" at the IP layer as in the sentence from the I-D "This TLV
specifies a stable OSPF TE node IP address, i.e., the IP address is always
reachable when there is IP connectivity to the associated OSPF TE node.".  If a
router were instantiated without any routing protocols, as in one form of
Software Defined Networks (SDNs), an identifier would be needed for the node
itself so that path computation in a centralized controller could form the
router data plane topology.
 
Suggested changes to the draft are:
In section 3, third paragraph:  "In the context of OSPF Traffic Engineering
(TE), an ASON transport node corresponds to a unique OSPF TE node.  An OSPF TE
node is uniquely identified by the TE Router Address TLV [RFC3630]. In this
document, this TE Router Address is referred to as the TE Router ID, which is in
the ASON SCN name space."  However, G.8080 distinguishes between the transport
node and its associated control plane components, esp. the Routing Controller.
It is the control plane component that is accessed through the SCN rather than
the transport node itself.
I propose changing the statement to say: "In this document, this TE Router
Address is referred to as the TE Router ID, which is in the ASON SNPP name
space."
Alternatively, we could just delete the sentence "In this document, this TE
Router Address is referred to as the TE Router ID, which is in the ASON SNPP
name space.".
 
In section 4, first paragraph, reachability of endpoints in the transport plane
is described as follows:
"In ASON, reachability refers to the set of endpoints reachable in the transport
plane by an associated ASON transport node.  Reachable entities are identified
in the ASON SCN name space."  As discussed above, only the control plane
components are accessed through the SCN, not the transport nodes themselves.
Entities that are reachable in the transport plane are identified through ASON
SNPPs rather than ASON SCN addresses.  Therefore I suggest removing the second
sentence completely so that it reads simply "In ASON, reachability refers to the
set of endpoints reachable in the transport plane by an associated ASON
transport node. "
 
Finally, in section 6.2, first paragraph following the format diagram, it is
stated:  "If it is not included in a Node Attribute TLV or a value of 0 is
specified for the Local TE Router Identifier, the Note Attribute TLV will not be
used for determining ASON SCN reachability." 
Again, the text should be edited to make the distinction between transport plane
and SCN clearer, I suggest modifying the statement to refer to "ASON
reachability" rather than "ASON SCN reachability".  The statement would read as
follows (also correcting the spelling of the TLV):
"If it is not included in a Node Attribute TLV or a value of 0 is specified for
the Local TE Router Identifier, the Node Attribute TLV will not be used for
determining ASON reachability."
 
Stephen Shew
 
-----Original Message-----
From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org] On
Behalf Of The IESG
Sent: Friday, July 20, 2012 11:19 AM
To: IETF-Announce
Cc: ccamp@ietf.org
Subject: Last Call: <draft-ietf-ccamp-rfc5787bis-05.txt> (ASON Routing for
OSPFv2 Protocols) to Proposed Standard
 
 
The IESG has received a request from the Common Control and Measurement Plane WG
(ccamp) to consider the following document:
- 'ASON Routing for OSPFv2 Protocols'
  <draft-ietf-ccamp-rfc5787bis-05.txt> as Proposed Standard
 
The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the ietf@ietf.org
mailing lists by 2012-08-17. Exceptionally, comments may be sent to
iesg@ietf.org instead. In either case, please retain the beginning of the
Subject line to allow automated sorting. This is a four- week last call period
because it spans the IETF-84 meeting.
 
Abstract
 
   The ITU-T has defined an architecture and requirements for operating
   an Automatically Switched Optical Network (ASON).
 
   The Generalized Multiprotocol Label Switching (GMPLS) protocol suite
   is designed to provide a control plane for a range of network
   technologies including optical networks such as time division
   multiplexing (TDM) networks including SONET/SDH and Optical Transport
   Networks (OTNs), and lambda switching optical networks.
 
   The requirements for GMPLS routing to satisfy the requirements of
   ASON routing, and an evaluation of existing GMPLS routing protocols
   are provided in other documents.  This document defines extensions to
   the OSPFv2 Link State Routing Protocol to meet the requirements for
   routing in an ASON.
 
   Note that this work is scoped to the requirements and evaluation
   expressed in RFC 4258 and RFC 4652 and the ITU-T Recommendations
   current when those documents were written.  Future extensions of
   revisions of this work may be necessary if the ITU-T Recommendations
   are revised or if new requirements are introduced into a revision of
   RFC 4258. This document obsoletes RFC 5787 and updates RFC 5786.
 
 
 
The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-ccamp-rfc5787bis/
 
IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-ccamp-rfc5787bis/ballot/
 
No IPR declarations have been submitted directly on this I-D.
 
 
Stephen Shew | Director, Standards
sshew@ciena.com <mailto:jdoe@ciena.com>  | 3500 Carling Ave. | Ottawa CANADA K2H
8E9
Direct +1.613.670.3211
 
 

------=_NextPart_000_15EA_01CD8090.3466CA10
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DProgId content=3DWord.Document><meta =
name=3DGenerator content=3D"Microsoft Word 14"><meta name=3DOriginator =
content=3D"Microsoft Word 14"><base href=3D"x-msg://221/"><link =
rel=3DFile-List href=3D"cid:filelist.xml@01CD808F.D04C6A80"><!--[if gte =
mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:EnvelopeVis/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-GB</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:DoNotExpandShiftReturn/>
<w:BreakWrappedTables/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520092929 1073786111 9 0 415 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520081665 -1073717157 41 0 66047 0;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:modern;
	mso-font-pitch:fixed;
	mso-font-signature:-520092929 1073806591 9 0 415 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	mso-fareast-font-family:Calibri;}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	mso-fareast-font-family:Calibri;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	mso-ascii-font-family:Tahoma;
	mso-hansi-font-family:Tahoma;
	mso-bidi-font-family:Tahoma;}
span.apple-style-span
	{mso-style-name:apple-style-span;
	mso-style-unhide:no;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;
	mso-style-unhide:no;}
span.EmailStyle21
	{mso-style-type:personal;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	font-family:"Times New Roman","serif";
	mso-ascii-font-family:"Times New Roman";
	mso-hansi-font-family:"Times New Roman";
	mso-bidi-font-family:"Times New Roman";
	color:#31849B;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-size:10.0pt;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue =
vlink=3Dpurple style=3D'tab-interval:36.0pt'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Hi =
Stephen,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>No, there is no requirement =
for the control plane topology to match the data plane topology in =
GMPLS. There is simply a 1:1 mapping between identifiers. We might note, =
however, that there is a virtual overlay in the SCN such that protocol =
controllers that control devices that are adjacent in the data plane can =
be made virtually adjacent in the control plane.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Your final assumption is how =
an operator might manage their network. But it is not a requirement =
since mappings can always be made at domain =
boundaries.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Adrian<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New =
Roman";mso-ansi-language:EN-US'>From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New Roman";mso-ansi-language:EN-US'> Shew, Stephen =
[mailto:sshew@ciena.com] <br><b>Sent:</b> 22 August 2012 =
17:35<br><b>To:</b> Acee Lindem; Ong, Lyndon<br><b>Cc:</b> =
ietf@ietf.org; draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org; Andrew G. =
(Andy) Malis<br><b>Subject:</b> RE: Last Call: =
&lt;draft-ietf-ccamp-rfc5787bis-05.txt&gt; =
<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;color:#31849B;mso-ansi-language:EN-US'>Thanks =
for the reply. If I understand correctly, this means that the SCN =
topology must match the transport topology when applying OSPF for ASON =
routing.&nbsp; This is because the Local TE Router Identifier and the =
Remote TE Router Identifier in the Local and Remote TE Router ID sub-TLV =
are the same as the TE Router ID in the TE Router Address TLV. If this =
is correct, then I think the draft should state the assumption that the =
SCN topology and transport plane topology are aligned. It&#8217;s an =
important assumption to state since management systems of SDH/OTN =
networks have topologies of the transport network in non-IP address =
formats (esp. TL-1 TIDs) and these need to be mapped to TE Router IDs in =
the SCN space when this draft is applied.&nbsp; I assume it implies that =
there should be a single SCN or non-overlapping IP address spaces if =
there are multiple SCNs, for a given transport topology otherwise the =
SCN topology representing the transport topology could have duplicate =
identifier values.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;color:#31849B;mso-ansi-language:EN-US'><o:p>&nb=
sp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#31849B;mso-ansi-language:EN-US'>Stephen<=
o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#31849B;mso-ansi-language:EN-US'><o:p>&nb=
sp;</o:p></span></p><div><div style=3D'border:none;border-top:solid =
#B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-ansi-lang=
uage:EN-US'>From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-ansi-lang=
uage:EN-US'> Acee Lindem [mailto:acee.lindem@ericsson.com] =
<br><b>Sent:</b> 21 August, 2012 17:23<br><b>To:</b> Ong, =
Lyndon<br><b>Cc:</b> ietf@ietf.org; Shew, Stephen; =
draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org; Andrew G. (Andy) =
Malis<br><b>Subject:</b> Re: Last Call: =
&lt;draft-ietf-ccamp-rfc5787bis-05.txt&gt; =
<o:p></o:p></span></p></div></div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Hi Stephen, =
Lyndon,&nbsp;<o:p></o:p></span></p><div><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'mso-ansi-language:EN-US'>Andy and I have had =
discussions with the CCAMP chairs and AD. We have come to the conclusion =
that we cannot merely change the name space for the advertised TE Router =
ID since this would imply a change to the GMPL model for setting up =
LSPs. In GMPL, the LSP endpoints are in the Signaling Control Network =
(SCN) and this cannot be changed without a distinct model for ASON LSP =
establishment complete with the specification of the changes to path =
computation, RSVP path signaling, and RSVP Explicit Route Object (ERO) =
handling. In essence, this change would add a level of indirection from =
the SNPP to the SCN. In the context of this draft, we are not going to =
deviate from the GMPLS LSP model and, hence, will not incorporating the =
suggested changes.&nbsp;<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Thanks,<o:p></o:p></span></p></div><div=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Acee&nbsp;<o:p></o:p></span></p><div><d=
iv><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>On Aug 17, 2012, at 7:58 PM, Ong, =
Lyndon wrote:<o:p></o:p></span></p></div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><div><div><=
p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>(Submitted =
on behalf of Stephen Shew)</span><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I would =
like to raise an issue with draft-ietf-ccamp-rfc5787bis-05.txt.&nbsp; =
The issue does not affect the proposed sub-TLVs or their semantics, so =
it would not affect an implementation. I believe some statements in the =
document should be edited to avoid confusion over ASON terminology as =
defined in ITU-T Recommendation G.8080, for which I am =
editor.</span><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>It =
concerns the definition of &#8220;ASON reachability&#8221; which changed =
during the course of the document from being a transport plane address, =
the SubNetwork Point Pool (SNPP) space, to the Signalling Control =
Network (SCN) address space.&nbsp; I think the root of the issue is that =
the visibility of the three address spaces described in ASON (G.8080) is =
not always made clear when discussing using OSPF for ASON Routing.&nbsp; =
Section 3 of G.8080 states that:</span><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Courier New"'>There are three =
categories of identifiers used for ASON routing</span><span lang=3DEN-US =
style=3D'font-size:11.0pt;mso-ansi-language:EN-US'><o:p></o:p></span></p>=
</div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
(G7715.1): transport plane names, control plane identifiers =
for</span><span lang=3DEN-US =
style=3D'font-size:11.0pt;mso-ansi-language:EN-US'><o:p></o:p></span></p>=
</div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
components, and Signaling Communications Network (SCN) =
addresses.</span><span lang=3DEN-US =
style=3D'font-size:11.0pt;mso-ansi-language:EN-US'><o:p></o:p></span></p>=
</div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt'>&nbsp;</span><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In -03 of =
the document, the term SNPP was used. This is the SubNetwork Point Pool =
space that describes the data plane and is defined in G.8080 Section =
10.&nbsp; It names the subnetwork (and/or containing subnetworks) to =
which Subnetwork Points (SNPs) are scoped. From G.8081: &#8220;The SNP =
is an abstraction that represents an actual or potential underlying =
connection point (CP) (or connection termination point (CTP)) or an =
actual or potential termination connection point (TCP) or trail =
termination point (TTP). Several SNPs (in different subnetwork =
partitions) may represent the same TCP or CP.</span><span =
dir=3DRTL></span><span dir=3DRTL></span><span lang=3DAR-AE dir=3DRTL =
style=3D'font-size:11.0pt;font-family:"Arial","sans-serif";mso-ansi-langu=
age:EN-US;mso-bidi-language:AR-AE'><span dir=3DRTL></span><span =
dir=3DRTL></span>&quot;</span><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In =
concrete terms, an SNPP would name an OTN switch, and an SNP would be a =
label identifying an ODU0.&nbsp; For the topology of the transport =
plane, SNPP and SNPP link names are used.&nbsp; Path computation is =
performed over such a topology.&nbsp; If a path can be computed between =
two SNPPs, they are reachable in ASON terms. For example, and ingress =
OTN switch for an ODU1 connection that terminates on an egress OTN =
switch.</span><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Arial","sans-serif";mso-ansi-langu=
age:EN-US'>&nbsp;</span><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>The =
Signalling Control Network (SCN) is a separate network over which =
control messages are sent. It has a topology independent of the =
transport plane.&nbsp; Path computation on the SCN address space is used =
to connect SCN address.&nbsp; SDH/OTN networks often have a separate IP =
network as the SCN network and the topology of the SCN network does not =
have to follow the topology of the transport network.</span><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
dir=3DRTL></span><span dir=3DRTL></span><span lang=3DAR-SA dir=3DRTL =
style=3D'font-size:11.0pt;mso-ansi-language:EN-US'><span =
dir=3DRTL></span><span dir=3DRTL></span>&nbsp;</span><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>ASON =
Control Plane Component identifiers are the third name space and =
identify routing and signalling instances.&nbsp; It is expected that =
they form adjacencies over the SCN.&nbsp; The topology of the =
adjacencies is independent of the SCN and transport plane =
topologies.&nbsp; &#8220;Reachability&#8221; between two control plane =
components would be some sequence of adjacencies.&nbsp; It is entirely =
possible to have two separate control planes running over the same SCN =
network, or one control plane that uses several SCNs.&nbsp; For example, =
imagine some OSPF instances whose adjacencies were all targeted and each =
adjacency traversed a separate private IP network.&nbsp; The OSPF =
instances would need to identified by a common address space so that =
they are distinguished from each other, but the TE interfaces could have =
overlapping IPv4 values because they would be in different private IP =
network spaces.</span><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>What makes =
the discussion of &#8220;TE router ID&#8221; confusing is that as =
applied to a transport network, every node gets a &#8220;TE router =
ID&#8221; and so it can be used in the transport topology for path =
computation.&nbsp; In that sense it is &#8220;reachable&#8221; in the =
dataplane.&nbsp; However, it is also (I think) an address that is =
implicitly in the SCN space in some implementations and so it takes on a =
dual meaning of &#8220;reachability&#8221; at the IP layer as in the =
sentence from the I-D &#8220;This TLV specifies a stable OSPF TE node IP =
address, i.e., the IP address is always reachable when there is IP =
connectivity to the associated OSPF TE node.&#8221;.&nbsp; If a router =
were instantiated without any routing protocols, as in one form of =
Software Defined Networks (SDNs), an identifier would be needed for the =
node itself so that path computation in a centralized controller could =
form the router data plane topology.</span><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Suggested =
changes to the draft are:</span><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3, third paragraph:&nbsp; &quot;In the context of OSPF Traffic =
Engineering (TE), an ASON transport node corresponds to a unique OSPF TE =
node.&nbsp; An OSPF TE node is uniquely identified by the TE Router =
Address TLV [RFC3630]. In this document, this TE Router Address is =
referred to as the TE Router ID, which is in the ASON SCN name =
space.&quot;&nbsp; However, G.8080 distinguishes between the transport =
node and its associated control plane components, esp. the Routing =
Controller.&nbsp; It is the control plane component that is accessed =
through the SCN rather than the transport node itself.</span><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I propose =
changing the statement to say: &quot;In this document, this TE Router =
Address is referred to as the TE Router ID, which is in the ASON SNPP =
name space.&#8221;</span><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Alternative=
ly, we could just delete the sentence &#8220;In this document, this TE =
Router Address is referred to as the TE Router ID, which is in the ASON =
SNPP name space.&#8221;.</span><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
4, first paragraph, reachability of endpoints in the transport plane is =
described as follows:</span><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&quot;In =
ASON, reachability refers to the set of endpoints reachable in the =
transport plane by an associated ASON transport node.&nbsp; Reachable =
entities are identified in the ASON SCN name space.&quot;&nbsp; As =
discussed above, only the control plane components are accessed through =
the SCN, not the transport nodes themselves.&nbsp; Entities that are =
reachable in the transport plane are identified through ASON SNPPs =
rather than ASON SCN addresses.&nbsp; Therefore I suggest removing the =
second sentence completely so that it reads simply &quot;In ASON, =
reachability refers to the set of endpoints reachable in the transport =
plane by an associated ASON transport node.&nbsp;&#8220;</span><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Finally, =
in section 6.2, first paragraph following the format diagram, it is =
stated:&nbsp; &quot;If it is not included in a Node Attribute TLV or a =
value of 0 is specified for the Local TE Router Identifier, the Note =
Attribute TLV will not be used for determining ASON SCN =
reachability.&quot;&nbsp;</span><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Again, the =
text should be edited to make the distinction between transport plane =
and SCN clearer, I suggest modifying the statement to refer to =
&quot;ASON reachability&quot; rather than &quot;ASON SCN =
reachability&quot;.&nbsp; The statement would read as follows (also =
correcting the spelling of the TLV):</span><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&quot;If =
it is not included in a Node Attribute TLV or a value of 0 is specified =
for the Local TE Router Identifier, the Node Attribute TLV will not be =
used for determining ASON reachability.&quot;</span><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;</span><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'><=
o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>Stephen Shew</span><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'><=
o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;</span><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'><=
o:p></o:p></span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>-=
----Original Message-----<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>F=
rom:<span class=3Dapple-converted-space>&nbsp;</span><a =
href=3D"mailto:ietf-announce-bounces@ietf.org">ietf-announce-bounces@ietf=
.org</a><span class=3Dapple-converted-space>&nbsp;</span>[<a =
href=3D"mailto:ietf-announce-bounces@ietf.org">mailto:ietf-announce-bounc=
es@ietf.org</a>] On Behalf Of The =
IESG<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>S=
ent: Friday, July 20, 2012 11:19 AM<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>T=
o: IETF-Announce<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>C=
c:<span class=3Dapple-converted-space>&nbsp;</span><a =
href=3D"mailto:ccamp@ietf.org">ccamp@ietf.org</a><o:p></o:p></span></p></=
div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>S=
ubject: Last Call: &lt;draft-ietf-ccamp-rfc5787bis-05.txt&gt; (ASON =
Routing for OSPFv2 Protocols) to Proposed =
Standard<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>T=
he IESG has received a request from the Common Control and Measurement =
Plane WG (ccamp) to consider the following =
document:<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>-=
 'ASON Routing for OSPFv2 Protocols'<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp; &lt;draft-ietf-ccamp-rfc5787bis-05.txt&gt; as Proposed =
Standard<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>T=
he IESG plans to make a decision in the next few weeks, and solicits =
final comments on this action. Please send substantive comments to =
the<span class=3Dapple-converted-space>&nbsp;</span><a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><span =
class=3Dapple-converted-space>&nbsp;</span>mailing lists by 2012-08-17. =
Exceptionally, comments may be sent to<span =
class=3Dapple-converted-space>&nbsp;</span><a =
href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a><span =
class=3Dapple-converted-space>&nbsp;</span>instead. In either case, =
please retain the beginning of the Subject line to allow automated =
sorting. This is a four- week last call period because it spans the =
IETF-84 meeting.<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>A=
bstract<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;&nbsp; The ITU-T has defined an architecture and requirements for =
operating<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;&nbsp; an Automatically Switched Optical Network =
(ASON).<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;&nbsp; The Generalized Multiprotocol Label Switching (GMPLS) =
protocol suite<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;&nbsp; is designed to provide a control plane for a range of =
network<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;&nbsp; technologies including optical networks such as time =
division<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;&nbsp; multiplexing (TDM) networks including SONET/SDH and Optical =
Transport<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;&nbsp; Networks (OTNs), and lambda switching optical =
networks.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;&nbsp; The requirements for GMPLS routing to satisfy the =
requirements of<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;&nbsp; ASON routing, and an evaluation of existing GMPLS routing =
protocols<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;&nbsp; are provided in other documents.&nbsp; This document defines =
extensions to<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;&nbsp; the OSPFv2 Link State Routing Protocol to meet the =
requirements for<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;&nbsp; routing in an ASON.<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;&nbsp; Note that this work is scoped to the requirements and =
evaluation<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;&nbsp; expressed in RFC 4258 and RFC 4652 and the ITU-T =
Recommendations<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;&nbsp; current when those documents were written.&nbsp; Future =
extensions of<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;&nbsp; revisions of this work may be necessary if the ITU-T =
Recommendations<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;&nbsp; are revised or if new requirements are introduced into a =
revision of<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;&nbsp; RFC 4258. This document obsoletes RFC 5787 and updates RFC =
5786.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>T=
he file can be obtained via<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'><=
a =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-ccamp-rfc5787bis/">htt=
p://datatracker.ietf.org/doc/draft-ietf-ccamp-rfc5787bis/</a><o:p></o:p><=
/span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>I=
ESG discussion can be tracked via<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'><=
a =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-ccamp-rfc5787bis/ballo=
t/">http://datatracker.ietf.org/doc/draft-ietf-ccamp-rfc5787bis/ballot/</=
a><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>&=
nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:Consolas;mso-ansi-language:EN-US'>N=
o IPR declarations have been submitted directly on this =
I-D.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D;mso-ansi-language:EN-US'>&nbsp;</=
span><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D;mso-ansi-language:EN-US'>&nbsp;</=
span><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:#1F497D;m=
so-ansi-language:EN-US'>Stephen Shew</span></b><span lang=3DEN-US =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:#1F497D;m=
so-ansi-language:EN-US'>&nbsp;</span><span lang=3DEN-US =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:red;mso-a=
nsi-language:EN-US'>|</span><span class=3Dapple-converted-space><span =
lang=3DEN-US =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:#1F497D;m=
so-ansi-language:EN-US'>&nbsp;</span></span><span lang=3DEN-US =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:gray;mso-=
ansi-language:EN-US'>Director, Standards</span><span lang=3DEN-US =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:#1F497D;m=
so-ansi-language:EN-US'><br></span><u><span lang=3DEN-US =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:blue;mso-=
ansi-language:EN-US'><a =
href=3D"mailto:jdoe@ciena.com">sshew@ciena.com</a></span></u><span =
class=3Dapple-converted-space><span lang=3DEN-US =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:#1F497D;m=
so-ansi-language:EN-US'>&nbsp;</span></span><span lang=3DEN-US =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:red;mso-a=
nsi-language:EN-US'>|</span><span class=3Dapple-converted-space><span =
lang=3DEN-US =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:purple;ms=
o-ansi-language:EN-US'>&nbsp;</span></span><span lang=3DEN-US =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:gray;mso-=
ansi-language:EN-US'>3500 Carling Ave.<span =
class=3Dapple-converted-space>&nbsp;</span></span><span lang=3DEN-US =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:red;mso-a=
nsi-language:EN-US'>|</span><span lang=3DEN-US =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:purple;ms=
o-ansi-language:EN-US'>&nbsp;</span><span lang=3DEN-US =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:gray;mso-=
ansi-language:EN-US'>Ottawa CANADA K2H 8E9<br>Direct =
+1.613.670.3211</span><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>&nbsp;<o:p></o:p></span></p></div></div></div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p></div></div=
></div></body></html>
------=_NextPart_000_15EA_01CD8090.3466CA10--


From lberger@labn.net  Wed Aug 22 10:11:34 2012
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 A1C3A21F8667 for <ietf@ietfa.amsl.com>; Wed, 22 Aug 2012 10:11:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.373
X-Spam-Level: 
X-Spam-Status: No, score=-99.373 tagged_above=-999 required=5 tests=[AWL=0.788, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, IP_NOT_FRIENDLY=0.334, 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 DIPpPTQGRATv for <ietf@ietfa.amsl.com>; Wed, 22 Aug 2012 10:11:33 -0700 (PDT)
Received: from oproxy12-pub.bluehost.com (unknown [IPv6:2605:dc00:100:2::a4]) by ietfa.amsl.com (Postfix) with SMTP id 70FC821F8628 for <ietf@ietf.org>; Wed, 22 Aug 2012 10:11:33 -0700 (PDT)
Received: (qmail 3631 invoked by uid 0); 22 Aug 2012 17:11:30 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy12.bluehost.com with SMTP; 22 Aug 2012 17:11:30 -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=Btt5DmNUkye4UCDDFcxUXoQDCj4YWWJr8aBCEyq8CIQ=;  b=dI1ZkvrAuzhIqh5mN6vGdWJyajGTFn663iIS8zk1FG10+5JsC17QRKI/qEl+XT06G/AawjVdhzda5suyq1MuRnAgSDiVmuQFeeQRYESjklXVlTnEHI0K1QlMBG5x8Jsu;
Received: from box313.bluehost.com ([69.89.31.113]:58177 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.76) (envelope-from <lberger@labn.net>) id 1T4ESo-0006hL-9m; Wed, 22 Aug 2012 11:11:30 -0600
Message-ID: <503512B7.9090904@labn.net>
Date: Wed, 22 Aug 2012 13:11:19 -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: adrian@olddog.co.uk
Subject: Re: Last Call: <draft-ietf-ccamp-rfc5787bis-05.txt>
References: <A0B4FC0A5EFBD44585414760DB4FD2749F512AA9@MDWEXGMB02.ciena.com>	<D3266962-DD41-4FBA-A0A2-E1F9D5BF2B3C@ericsson.com>	<510C3D5C5DFBCB46AE189D936C1DD605A60CC92886@ONWVEXCHMB02.ciena.com> <15e901cd8087$d29542b0$77bfc810$@olddog.co.uk>
In-Reply-To: <15e901cd8087$d29542b0$77bfc810$@olddog.co.uk>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org, ietf@ietf.org, "'Shew, Stephen'" <sshew@ciena.com>, "'Ong, Lyndon'" <Lyong@ciena.com>, "'Andrew G. \(Andy\) Malis'" <andrew.g.malis@verizon.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Aug 2012 17:11:34 -0000

Stephen,
	To add to what Adrian said, the 1:1 mapping is only for node
identifiers, interface identifiers have no such restriction.  I think
it's reasonable to add some informative text to the draft on this point
as it may help avoid such confusion in the future.

Lou

On 8/22/2012 1:01 PM, Adrian Farrel wrote:
> 
> 
> Hi Stephen,
> 
>  
> 
> No, there is no requirement for the control plane topology to match the
> data plane topology in GMPLS. There is simply a 1:1 mapping between
> identifiers. We might note, however, that there is a virtual overlay in
> the SCN such that protocol controllers that control devices that are
> adjacent in the data plane can be made virtually adjacent in the control
> plane.
> 
>  
> 
> Your final assumption is how an operator might manage their network. But
> it is not a requirement since mappings can always be made at domain
> boundaries.
> 
>  
> 
> Adrian
> 
>  
> 
> *From:* Shew, Stephen [mailto:sshew@ciena.com]
> *Sent:* 22 August 2012 17:35
> *To:* Acee Lindem; Ong, Lyndon
> *Cc:* ietf@ietf.org; draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org;
> Andrew G. (Andy) Malis
> *Subject:* RE: Last Call: <draft-ietf-ccamp-rfc5787bis-05.txt>
> 
>  
> 
> Thanks for the reply. If I understand correctly, this means that the SCN
> topology must match the transport topology when applying OSPF for ASON
> routing.  This is because the Local TE Router Identifier and the Remote
> TE Router Identifier in the Local and Remote TE Router ID sub-TLV are
> the same as the TE Router ID in the TE Router Address TLV. If this is
> correct, then I think the draft should state the assumption that the SCN
> topology and transport plane topology are aligned. It’s an important
> assumption to state since management systems of SDH/OTN networks have
> topologies of the transport network in non-IP address formats (esp. TL-1
> TIDs) and these need to be mapped to TE Router IDs in the SCN space when
> this draft is applied.  I assume it implies that there should be a
> single SCN or non-overlapping IP address spaces if there are multiple
> SCNs, for a given transport topology otherwise the SCN topology
> representing the transport topology could have duplicate identifier values.
> 
>  
> 
> Stephen
> 
>  
> 
> *From:* Acee Lindem [mailto:acee.lindem@ericsson.com]
> *Sent:* 21 August, 2012 17:23
> *To:* Ong, Lyndon
> *Cc:* ietf@ietf.org; Shew, Stephen;
> draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org; Andrew G. (Andy) Malis
> *Subject:* Re: Last Call: <draft-ietf-ccamp-rfc5787bis-05.txt>
> 
>  
> 
> Hi Stephen, Lyndon, 
> 
> Andy and I have had discussions with the CCAMP chairs and AD. We have
> come to the conclusion that we cannot merely change the name space for
> the advertised TE Router ID since this would imply a change to the GMPL
> model for setting up LSPs. In GMPL, the LSP endpoints are in the
> Signaling Control Network (SCN) and this cannot be changed without a
> distinct model for ASON LSP establishment complete with the
> specification of the changes to path computation, RSVP path signaling,
> and RSVP Explicit Route Object (ERO) handling. In essence, this change
> would add a level of indirection from the SNPP to the SCN. In the
> context of this draft, we are not going to deviate from the GMPLS LSP
> model and, hence, will not incorporating the suggested changes. 
> 
> Thanks,
> 
> Acee 
> 
> On Aug 17, 2012, at 7:58 PM, Ong, Lyndon wrote:
> 
>  
> 
> (Submitted on behalf of Stephen Shew)
> 
>  
> 
> I would like to raise an issue with draft-ietf-ccamp-rfc5787bis-05.txt. 
> The issue does not affect the proposed sub-TLVs or their semantics, so
> it would not affect an implementation. I believe some statements in the
> document should be edited to avoid confusion over ASON terminology as
> defined in ITU-T Recommendation G.8080, for which I am editor.
> 
>  
> 
> It concerns the definition of “ASON reachability” which changed during
> the course of the document from being a transport plane address, the
> SubNetwork Point Pool (SNPP) space, to the Signalling Control Network
> (SCN) address space.  I think the root of the issue is that the
> visibility of the three address spaces described in ASON (G.8080) is not
> always made clear when discussing using OSPF for ASON Routing.  Section
> 3 of G.8080 states that:
> 
> There are three categories of identifiers used for ASON routing
> 
>    (G7715.1): transport plane names, control plane identifiers for
> 
>    components, and Signaling Communications Network (SCN) addresses.
> 
>  
> 
> In -03 of the document, the term SNPP was used. This is the SubNetwork
> Point Pool space that describes the data plane and is defined in G.8080
> Section 10.  It names the subnetwork (and/or containing subnetworks) to
> which Subnetwork Points (SNPs) are scoped. From G.8081: “The SNP is an
> abstraction that represents an actual or potential underlying connection
> point (CP) (or connection termination point (CTP)) or an actual or
> potential termination connection point (TCP) or trail termination point
> (TTP). Several SNPs (in different subnetwork partitions) may represent
> the same TCP or CP."
> 
>  
> 
> In concrete terms, an SNPP would name an OTN switch, and an SNP would be
> a label identifying an ODU0.  For the topology of the transport plane,
> SNPP and SNPP link names are used.  Path computation is performed over
> such a topology.  If a path can be computed between two SNPPs, they are
> reachable in ASON terms. For example, and ingress OTN switch for an ODU1
> connection that terminates on an egress OTN switch.
> 
>  
> 
> The Signalling Control Network (SCN) is a separate network over which
> control messages are sent. It has a topology independent of the
> transport plane.  Path computation on the SCN address space is used to
> connect SCN address.  SDH/OTN networks often have a separate IP network
> as the SCN network and the topology of the SCN network does not have to
> follow the topology of the transport network.
> 
>  
> 
> ASON Control Plane Component identifiers are the third name space and
> identify routing and signalling instances.  It is expected that they
> form adjacencies over the SCN.  The topology of the adjacencies is
> independent of the SCN and transport plane topologies.  “Reachability”
> between two control plane components would be some sequence of
> adjacencies.  It is entirely possible to have two separate control
> planes running over the same SCN network, or one control plane that uses
> several SCNs.  For example, imagine some OSPF instances whose
> adjacencies were all targeted and each adjacency traversed a separate
> private IP network.  The OSPF instances would need to identified by a
> common address space so that they are distinguished from each other, but
> the TE interfaces could have overlapping IPv4 values because they would
> be in different private IP network spaces.
> 
>  
> 
> What makes the discussion of “TE router ID” confusing is that as applied
> to a transport network, every node gets a “TE router ID” and so it can
> be used in the transport topology for path computation.  In that sense
> it is “reachable” in the dataplane.  However, it is also (I think) an
> address that is implicitly in the SCN space in some implementations and
> so it takes on a dual meaning of “reachability” at the IP layer as in
> the sentence from the I-D “This TLV specifies a stable OSPF TE node IP
> address, i.e., the IP address is always reachable when there is IP
> connectivity to the associated OSPF TE node.”.  If a router were
> instantiated without any routing protocols, as in one form of Software
> Defined Networks (SDNs), an identifier would be needed for the node
> itself so that path computation in a centralized controller could form
> the router data plane topology.
> 
>  
> 
> Suggested changes to the draft are:
> 
> In section 3, third paragraph:  "In the context of OSPF Traffic
> Engineering (TE), an ASON transport node corresponds to a unique OSPF TE
> node.  An OSPF TE node is uniquely identified by the TE Router Address
> TLV [RFC3630]. In this document, this TE Router Address is referred to
> as the TE Router ID, which is in the ASON SCN name space."  However,
> G.8080 distinguishes between the transport node and its associated
> control plane components, esp. the Routing Controller.  It is the
> control plane component that is accessed through the SCN rather than the
> transport node itself.
> 
> I propose changing the statement to say: "In this document, this TE
> Router Address is referred to as the TE Router ID, which is in the ASON
> SNPP name space.”
> 
> Alternatively, we could just delete the sentence “In this document, this
> TE Router Address is referred to as the TE Router ID, which is in the
> ASON SNPP name space.”.
> 
>  
> 
> In section 4, first paragraph, reachability of endpoints in the
> transport plane is described as follows:
> 
> "In ASON, reachability refers to the set of endpoints reachable in the
> transport plane by an associated ASON transport node.  Reachable
> entities are identified in the ASON SCN name space."  As discussed
> above, only the control plane components are accessed through the SCN,
> not the transport nodes themselves.  Entities that are reachable in the
> transport plane are identified through ASON SNPPs rather than ASON SCN
> addresses.  Therefore I suggest removing the second sentence completely
> so that it reads simply "In ASON, reachability refers to the set of
> endpoints reachable in the transport plane by an associated ASON
> transport node. “
> 
>  
> 
> Finally, in section 6.2, first paragraph following the format diagram,
> it is stated:  "If it is not included in a Node Attribute TLV or a value
> of 0 is specified for the Local TE Router Identifier, the Note Attribute
> TLV will not be used for determining ASON SCN reachability." 
> 
> Again, the text should be edited to make the distinction between
> transport plane and SCN clearer, I suggest modifying the statement to
> refer to "ASON reachability" rather than "ASON SCN reachability".  The
> statement would read as follows (also correcting the spelling of the TLV):
> 
> "If it is not included in a Node Attribute TLV or a value of 0 is
> specified for the Local TE Router Identifier, the Node Attribute TLV
> will not be used for determining ASON reachability."
> 
>  
> 
> Stephen Shew
> 
>  
> 
> -----Original Message-----
> 
> From: ietf-announce-bounces@ietf.org
> <mailto:ietf-announce-bounces@ietf.org> [mailto:ietf-announce-bounces@ietf.org]
> On Behalf Of The IESG
> 
> Sent: Friday, July 20, 2012 11:19 AM
> 
> To: IETF-Announce
> 
> Cc: ccamp@ietf.org <mailto:ccamp@ietf.org>
> 
> Subject: Last Call: <draft-ietf-ccamp-rfc5787bis-05.txt> (ASON Routing
> for OSPFv2 Protocols) to Proposed Standard
> 
>  
> 
>  
> 
> The IESG has received a request from the Common Control and Measurement
> Plane WG (ccamp) to consider the following document:
> 
> - 'ASON Routing for OSPFv2 Protocols'
> 
>   <draft-ietf-ccamp-rfc5787bis-05.txt> as Proposed Standard
> 
>  
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to
> the ietf@ietf.org <mailto:ietf@ietf.org> mailing lists by 2012-08-17.
> Exceptionally, comments may be sent to iesg@ietf.org
> <mailto:iesg@ietf.org> instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting. This is a
> four- week last call period because it spans the IETF-84 meeting.
> 
>  
> 
> Abstract
> 
>  
> 
>    The ITU-T has defined an architecture and requirements for operating
> 
>    an Automatically Switched Optical Network (ASON).
> 
>  
> 
>    The Generalized Multiprotocol Label Switching (GMPLS) protocol suite
> 
>    is designed to provide a control plane for a range of network
> 
>    technologies including optical networks such as time division
> 
>    multiplexing (TDM) networks including SONET/SDH and Optical Transport
> 
>    Networks (OTNs), and lambda switching optical networks.
> 
>  
> 
>    The requirements for GMPLS routing to satisfy the requirements of
> 
>    ASON routing, and an evaluation of existing GMPLS routing protocols
> 
>    are provided in other documents.  This document defines extensions to
> 
>    the OSPFv2 Link State Routing Protocol to meet the requirements for
> 
>    routing in an ASON.
> 
>  
> 
>    Note that this work is scoped to the requirements and evaluation
> 
>    expressed in RFC 4258 and RFC 4652 and the ITU-T Recommendations
> 
>    current when those documents were written.  Future extensions of
> 
>    revisions of this work may be necessary if the ITU-T Recommendations
> 
>    are revised or if new requirements are introduced into a revision of
> 
>    RFC 4258. This document obsoletes RFC 5787 and updates RFC 5786.
> 
>  
> 
>  
> 
>  
> 
> The file can be obtained via
> 
> http://datatracker.ietf.org/doc/draft-ietf-ccamp-rfc5787bis/
> 
>  
> 
> IESG discussion can be tracked via
> 
> http://datatracker.ietf.org/doc/draft-ietf-ccamp-rfc5787bis/ballot/
> 
>  
> 
> No IPR declarations have been submitted directly on this I-D.
> 
>  
> 
>  
> 
> *Stephen Shew* | Director, Standards
> sshew@ciena.com <mailto:jdoe@ciena.com>  | 3500 Carling Ave. | Ottawa
> CANADA K2H 8E9
> Direct +1.613.670.3211
> 
>  
> 
>  
> 

From dhc@dcrocker.net  Wed Aug 22 10:12:11 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48CE021F866E; Wed, 22 Aug 2012 10:12:11 -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 vvQ2IFR59VDy; Wed, 22 Aug 2012 10:12:10 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4E3C721F8658; Wed, 22 Aug 2012 10:12:10 -0700 (PDT)
Received: from [192.168.18.72] ([12.131.211.98]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q7MHC8aA000609 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 22 Aug 2012 10:12:09 -0700
Message-ID: <503512E5.9020909@dcrocker.net>
Date: Wed, 22 Aug 2012 10:12:05 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: robert@raszuk.net
Subject: Re: IETF 92 in Dallas!
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net> <BA2EE8F7-92C8-4F10-B10A-2B6FE4FC954A@gmail.com> <502E9614.30409@raszuk.net>
In-Reply-To: <502E9614.30409@raszuk.net>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 22 Aug 2012 10:12:10 -0700 (PDT)
Cc: iaoc@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Aug 2012 17:12:11 -0000

On 8/17/2012 12:05 PM, Robert Raszuk wrote:

> For example once I know the criteria I could check around in Poland to
> see if there is any place which would satisfy the future IETF venue.


   http://www.ietf.org/meeting/hosting-an-ietf.html

d/
-- 
 Dave Crocker
 Brandenburg InternetWorking
 bbiw.net

From johnl@iecc.com  Wed Aug 22 13:12:05 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85E6721F8565 for <ietf@ietfa.amsl.com>; Wed, 22 Aug 2012 13:12:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.147
X-Spam-Level: 
X-Spam-Status: No, score=-111.147 tagged_above=-999 required=5 tests=[AWL=0.052, 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 xor2sBG-ySKQ for <ietf@ietfa.amsl.com>; Wed, 22 Aug 2012 13:12:04 -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 637D521F85AE for <ietf@ietf.org>; Wed, 22 Aug 2012 13:12:04 -0700 (PDT)
Received: (qmail 20858 invoked from network); 22 Aug 2012 20:12:02 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 22 Aug 2012 20:12:02 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50353d10.xn--i8sz2z.k1208; i=johnl@user.iecc.com; bh=Toq0Banki8D7oC9lT94ycgXoEBL+bcjf0GVUiONMe+0=; b=rwTsjj7xjnOYLUYhvkmle11wpR1YTTDpHgKxdgpN5yMmAZsLYlpW3qQSHPqI1GGugZFA8zQ6s40kD/tv5AnJCm0+/jgCU38SI5ymkzkI3XU2ENmW69qrTGd7hGZwLiTYjzwfOocj1k1KufJjr2E+geJKVKDGuvVdybsRsOVDfno=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50353d10.xn--i8sz2z.k1208; olt=johnl@user.iecc.com; bh=Toq0Banki8D7oC9lT94ycgXoEBL+bcjf0GVUiONMe+0=; b=DxFSngdUj5laiIZcyhaMGaNe8EldLyjEcrtE3YpXp08VdZALUSBq3QkqWC0AJGZiSCbZs5rLW2ra8jsqhmuB7YtOxnJsuCgFCos0B2QaZmO3Td+IpXwFerVVUFisdYGSWSKPdSW3SCKRCcT3hHqiumiM8w1oo2yvfES5eXAFskY=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 22 Aug 2012 20:11:38 -0000
Message-ID: <20120822201138.7901.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: much farther away than IETF 92 in Dallas!
In-Reply-To: <503512E5.9020909@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: Wed, 22 Aug 2012 20:12:05 -0000

>> For example once I know the criteria I could check around in Poland to
>> see if there is any place which would satisfy the future IETF venue.
>
>   http://www.ietf.org/meeting/hosting-an-ietf.html

That's about how to be a meeting host, and it's mostly about terminal
rooms and social events.

Is there a list anywhere of minimum requirements without which it's
not even worth looking at a venue?  I'd expect that if a place doesn't
have (as some examples) a meeting room big enough for a plenary, a set
of sufficently large meeting rooms for sessions, a place for a
terminal room, a place to have coffee and snacks, and the ability to
provision Internet access in meeting rooms and guest rooms, forget it.

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

PS: Meter-deep water running in the streets is presumably optional.

From dworley@avaya.com  Wed Aug 22 13:18:49 2012
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 158E821F859C for <ietf@ietfa.amsl.com>; Wed, 22 Aug 2012 13:18:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.297
X-Spam-Level: 
X-Spam-Status: No, score=-103.297 tagged_above=-999 required=5 tests=[AWL=0.302, 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 Uziqu-m5NRdK for <ietf@ietfa.amsl.com>; Wed, 22 Aug 2012 13:18:48 -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 03C0E21F85C0 for <ietf@ietf.org>; Wed, 22 Aug 2012 13:18:47 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFACo+NVCHCzI1/2dsb2JhbABFhgGzW3KBB4IgAQEBAQIBEhERRQULAgEIDQsCAiYCAgIwFRABAQQODQEZh2UGC5thih2TKIEhj3EyYAObUIoVgn8
X-IronPort-AV: E=Sophos;i="4.77,811,1336363200"; d="scan'208";a="320858247"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 22 Aug 2012 16:15:05 -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; 22 Aug 2012 15:57:42 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Wed, 22 Aug 2012 16:18:12 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "johnl@taugh.com" <johnl@taugh.com>
Date: Wed, 22 Aug 2012 16:18:12 -0400
Subject: Re: much farther away than IETF 92 in Dallas!
Thread-Topic: much farther away than IETF 92 in Dallas!
Thread-Index: Ac2Ao0FJfHJUeeDJSAKk1eP5iIGjDA==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A1E44@DC-US1MBEX4.global.avaya.com>
References: <20120822201138.7901.qmail@joyce.lan>
In-Reply-To: <20120822201138.7901.qmail@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="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: Wed, 22 Aug 2012 20:18:49 -0000

T24gV2VkLCAyMDEyLTA4LTIyIGF0IDIwOjExICswMDAwLCBKb2huIExldmluZSB3cm90ZToKPiA+
ICAgaHR0cDovL3d3dy5pZXRmLm9yZy9tZWV0aW5nL2hvc3RpbmctYW4taWV0Zi5odG1sCgo+IElz
IHRoZXJlIGEgbGlzdCBhbnl3aGVyZSBvZiBtaW5pbXVtIHJlcXVpcmVtZW50cyB3aXRob3V0IHdo
aWNoIGl0J3MKPiBub3QgZXZlbiB3b3J0aCBsb29raW5nIGF0IGEgdmVudWU/ICBJJ2QgZXhwZWN0
IHRoYXQgaWYgYSBwbGFjZSBkb2Vzbid0Cj4gaGF2ZSAoYXMgc29tZSBleGFtcGxlcykgYSBtZWV0
aW5nIHJvb20gYmlnIGVub3VnaCBmb3IgYSBwbGVuYXJ5LCBhIHNldAo+IG9mIHN1ZmZpY2VudGx5
IGxhcmdlIG1lZXRpbmcgcm9vbXMgZm9yIHNlc3Npb25zLCBhIHBsYWNlIGZvciBhCj4gdGVybWlu
YWwgcm9vbSwgYSBwbGFjZSB0byBoYXZlIGNvZmZlZSBhbmQgc25hY2tzLCBhbmQgdGhlIGFiaWxp
dHkgdG8KPiBwcm92aXNpb24gSW50ZXJuZXQgYWNjZXNzIGluIG1lZXRpbmcgcm9vbXMgYW5kIGd1
ZXN0IHJvb21zLCBmb3JnZXQgaXQuCgpEb3duIGEgd2F5cyBvbiB0aGUgcmVmZXJlbmNlZCBwYWdl
LCB0aGVyZSBpcyBhIGxpbmsgdG8KCmh0dHA6Ly93d3cuaWV0Zi5vcmcvbWVldGluZy9ob3RlbC1s
b2dpc3RpY3MuaHRtbAoKd2hpY2ggaXMgYSBiYXNpYyBsaXN0IG9mIHZlbnVlIHJlcXVpcmVtZW50
cy4KCkRhbGUKCg==

From abdussalambaryun@gmail.com  Wed Aug 22 13:24:13 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DC7C21F851B for <ietf@ietfa.amsl.com>; Wed, 22 Aug 2012 13:24:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.49
X-Spam-Level: 
X-Spam-Status: No, score=-3.49 tagged_above=-999 required=5 tests=[AWL=0.109,  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 9fcwUGKrov1t for <ietf@ietfa.amsl.com>; Wed, 22 Aug 2012 13:24:12 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3842321F8593 for <ietf@ietf.org>; Wed, 22 Aug 2012 13:24:12 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so1626189vbb.31 for <ietf@ietf.org>; Wed, 22 Aug 2012 13:24:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=zXkp6mKvHtZuB7juq3hq/ccIKeae2qgID2FrrNSu5YU=; b=lSLpy7XZ7UoRgk5MHLGyfZUXUrMGK2Nb2+uZF3SVsoHqD303Tj1XovwHDgQeSiIr7H VGN5Srw1qy6hLvpH0CCTHeCWxh9iFfAjGdsm53uIc/3Ueq2x85i0Pd6lA85ki9nsr89Y PLOw0o5uCskliAd9tpaghBNi+LF+xSkvSFudbnqAphYpq2TG84gnI7Fgx/k5ynbLJ++r lWE50YCNVOesz5cCxEsqAHJUtqp5N7OhcYSMcq9ax7EARsIaunDPV04CLiYet4yrJdBF YyNSAhAmuswvDZ/ZyBmLVoUIyKrx3nOc034lHi2dE2oMBTuKqoMA5Vlf+q3oWRJXwOLd dmvw==
MIME-Version: 1.0
Received: by 10.220.119.198 with SMTP id a6mr18052079vcr.23.1345667051594; Wed, 22 Aug 2012 13:24:11 -0700 (PDT)
Received: by 10.220.55.9 with HTTP; Wed, 22 Aug 2012 13:24:11 -0700 (PDT)
In-Reply-To: <CADnDZ8_CE4pJ7Rps9mv+6ZEm8uH19Y5fcDhKr6nk6diYm351Xw@mail.gmail.com>
References: <20120728232737.23974.14830.idtracker@ietfa.amsl.com> <CADnDZ8_CE4pJ7Rps9mv+6ZEm8uH19Y5fcDhKr6nk6diYm351Xw@mail.gmail.com>
Date: Wed, 22 Aug 2012 22:24:11 +0200
Message-ID: <CADnDZ88OB19LrdwvjY0YLA0af++zvseH-ar42OR=uzYfR28c5A@mail.gmail.com>
Subject: Fwd: Last Call: <draft-ietf-manet-olsrv2-15.txt> (The Optimized Link State Routing Protocol version 2) to Proposed Standard
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Aug 2012 20:24:13 -0000

Reply to your request dated 29/07/2012

Draft Reviewed By: Abdussalam Baryun (AB)                       Dated:
22/08/2012

Reviewer Comment  AB1: Terminology and Definition Related
++++++++++++++++++++++++++++++++++++
In [1] the olsrv2-interface runs the NHDP, and some terms in [1] are
defined as in [2]:

Interface:
A router=92s attachment to a communications medium. An interface is
assigned one or more addresses.

MANET interface:
An interface participating in a MANET and using this neighborhood
discovery protocol. A router may have several MANET interfaces.

Link:
A link between two MANET interfaces exists if either can be heard by the ot=
her.

These above terms=92 definitions are different than in [4, 5, and 6].
The reviewer may understand links are logical or/and physical as
defined in [3].
Why definitions are not in consistent with other RFCs?

References
++++++++++
1- Clausen, T., Dearlove, C., Jacquet, P., Herberg, U., =93The Optimized
Link State Routing Protocol version 2=94, work in progress, IETF, May
2012.
2-Clausen, T., Dearlove, C., Dean, J., =93Mobile Ad Hoc Network (MANET)
Neighborhood Discovery Protocol (NHDP)=94, RFC6130, IETF, April 2011.
3-  Melia, T., Gundavelli, S., =93Logical Interface Support for
multi-mode IP Hosts=94, work in progress, IETF, April, 2012.
4- Manner, J., and Kojo, M., =93Mobility Related Terminology=94, RFC3753,
IETF, June 2004.
5- Narten, T., Nordmark, E., Simpson, W., Soliman, H., =93Neighbor
Discovery for IP version 6 (IPv6)=94, RFC4861, IETF, Sep. 2007.
6- Blanchet, M., Seite, P., =93Multiple Interfaces and Provisioning
Domains Problem Statement=94, RFC6418, IETF, Nov. 2011.
7- Corson, S., Macker, J., =93Mobile Ad hoc Networking (MANET): Routing
Protocol Performance Issues and Evaluation Considerations=94, RFC2501,
IETF, Jan. 1999.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D

Thanks
AB




+++++++++++++++++++++++++++++++++++++++++++++++++++
On 7/29/12, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from the Mobile Ad-hoc Networks WG
> (manet) to consider the following document:
> - 'The Optimized Link State Routing Protocol version 2'
>   <draft-ietf-manet-olsrv2-15.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-08-22. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting. This last call
> period has been extended to handle the fact that it spans the IETF-84
> meeting.
>
> This last call is being re-initiated to include a notice that this docume=
nt
> includes a normative down reference to an Informational RFC:
> RFC5148, "Jitter considerations in MANETs".
>
> Abstract
>
>    This specification describes version 2 of the Optimized Link State
>    Routing (OLSRv2) protocol for Mobile Ad hoc NETworks (MANETs).
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>

From abdussalambaryun@gmail.com  Wed Aug 22 13:35:08 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08F0121F86C8; Wed, 22 Aug 2012 13:35:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.491
X-Spam-Level: 
X-Spam-Status: No, score=-3.491 tagged_above=-999 required=5 tests=[AWL=0.108,  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 sg+JBgfdTbO3; Wed, 22 Aug 2012 13:35:07 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id B180921F85EA; Wed, 22 Aug 2012 13:35:06 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so12256vbb.31 for <multiple recipients>; Wed, 22 Aug 2012 13:35:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=VHGCfrK8O2tLLebOjHhI5pZ1+SGBQ/HhF33ZrL5KyKY=; b=WiNoU/MEYYLfn9tW4H0UZ8s78irqD1txEzJaiCunCVNTY4eze5Z7NsjWESqVqWje4O GIOYYp7PaIr7Bbc1pQhoNHn/ePPOGzagl7JNooEO9M2NxkYPCjHFlncHCJYXN4mp/fSs vXlOHWkzHp00G4d9Ost4s56k/NaRdURPnD0+VdIvC0U73UruD4QQensFSqY0JNBrefLC u2L6Z2m42sAySCvSKn6jmbNmy9apuupBuzDBQ9CFwtKLPOuBGToY+o6xC15IWGDAWtOS ckpCbcO4y71852dUYJ+ldtW7pNZG1TElpojrJURwQLBBgugCo7cYTpvVosZHP/XTV+l5 xILg==
MIME-Version: 1.0
Received: by 10.52.174.82 with SMTP id bq18mr840355vdc.25.1345667705958; Wed, 22 Aug 2012 13:35:05 -0700 (PDT)
Received: by 10.220.55.9 with HTTP; Wed, 22 Aug 2012 13:35:05 -0700 (PDT)
In-Reply-To: <CADnDZ89YvrdvadRvCEYQA3nux-pdHH9kF5+Bqz-07gWpgYiB+A@mail.gmail.com>
References: <20120728232737.23974.14830.idtracker@ietfa.amsl.com> <CADnDZ89YvrdvadRvCEYQA3nux-pdHH9kF5+Bqz-07gWpgYiB+A@mail.gmail.com>
Date: Wed, 22 Aug 2012 22:35:05 +0200
Message-ID: <CADnDZ89UeOErnuYWNmdztnbwCchDvtmSnV9O1aiFKb+jJ222fQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-manet-olsrv2-15.txt> (The Optimized Link State Routing Protocol version 2) to Proposed Standard
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "iesg@ietf.org" <iesg@ietf.org>
Content-Type: text/plain; charset=windows-1252
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: Wed, 22 Aug 2012 20:35:08 -0000

Reply to your request dated 29/07/2012
Draft Reviewed By: Abdussalam Baryun (AB)    Dated:22/08/2012

Reviewer Comment AB3:  Related to OLSRv2 Metric
++++++++++++++++++++++++++++++++++++++

OLSRv2-draft> Note that the generation of (incoming) link metric
values is to be undertaken by a process outside this specification;
this
specification concerns only the distribution and use of those
metrics.

Comments> The OLSRv2 uses dimensionless additive metric types. The
OLSRv2 link metric is unidirectional (in document mentions
directional).

Question> The OLSRv2 specification uses dimensionless metric types,
which all nodes MUST support it. Does this mean that OLSRv2 doesn=92t
support dimensional metric types?

-The Metric distribution and use:

Section 4.5> Each HELLO or TC message carrying link (or neighbor) metrics
thus indicates which link metric information it is carrying, allowing
routers to determine if they can interoperate. If link metrics
require additional signaling to determine their values, whether in
HELLO messages or otherwise, then this is permitted but is outside
the scope of this specification.

Question> Where is metric defined in TC and hello messages between
neighbors or is it in the MPR message extension between MPRs. Does the
OLSRv2 router allow the both options or more others?

5.4.2> All routes found using this specification use a single link metric
type that is specified by the router parameter LINK_METRIC_TYPE,
which may take any value from 0 to 255, both inclusive.

Comment> links are between MANET interfaces and each router may have
more than one interface, so how can we have only one link metric per
router. IMO, recommended single link metric per interface. However, in
the introduction of section 5 it mentions that routers=92 parameters may
not be the same in MANET (does it contradict the single metric-type
parameter?).


-IANA Consideration for OLSRv2 Metric:

Comment> Metric assigned in IANA (table 13) but recommended to be
defined as [additive dimensionless link metric]. In future use of
OLSRv2 there may be non-additive metric types, and dimensional types.

Regards
AB
---------------------------------------------------------------------------=
------------
This message and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
This message is in compliance with the IETF regulations.
---------------------------------------------------------------------------=
------------


On 7/29/12, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from the Mobile Ad-hoc Networks WG
> (manet) to consider the following document:
> - 'The Optimized Link State Routing Protocol version 2'
>   <draft-ietf-manet-olsrv2-15.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-08-22. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting. This last call
> period has been extended to handle the fact that it spans the IETF-84
> meeting.
>
> This last call is being re-initiated to include a notice that this docume=
nt
> includes a normative down reference to an Informational RFC:
> RFC5148, "Jitter considerations in MANETs".
>
> Abstract
>
>    This specification describes version 2 of the Optimized Link State
>    Routing (OLSRv2) protocol for Mobile Ad hoc NETworks (MANETs).
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>

From abdussalambaryun@gmail.com  Wed Aug 22 13:59:44 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5C8121F86B6; Wed, 22 Aug 2012 13:59:43 -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 VPh2vY8vCaRU; Wed, 22 Aug 2012 13:59:43 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 03EFC21F8672; Wed, 22 Aug 2012 13:59:42 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so41623vcb.31 for <multiple recipients>; Wed, 22 Aug 2012 13:59:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=CfoG8xvqFmXD1As7Xz1bzT6abEgsAj/iqk/IfHWwf48=; b=rakBPOYcNHo1EqRa0AsfsjwfpJJ1Z/Otg+zCA44igFESBYt5ospZz0+KfA9udLlK4L xcG4iw8zWM5E8dWketb+hbtB8c/tfGWdu78ws46MFLrj75WoKZMnCmnNqYPTjFnndGfY IPO3LiMPsl56YbSznhnnuJRdNQNeCOiZ3n/xRMxhIIFsmvzMOhFHCcr6pxmqDkpfrfnf 5S8aMldfhJKaeiArFREEVRVJyuyBGs5+3fptY0DSrEV0d7Wr3IJZDTdbT3AYB25FQ4Qi U3fimnAnYemH9Cr40HBe1D8Ggn65GHkLcYdjW3ESOmxnG/p3DwvvAEJHQ+5hCbcYsgg4 k9PA==
MIME-Version: 1.0
Received: by 10.220.141.208 with SMTP id n16mr18085398vcu.22.1345669182364; Wed, 22 Aug 2012 13:59:42 -0700 (PDT)
Received: by 10.220.55.9 with HTTP; Wed, 22 Aug 2012 13:59:42 -0700 (PDT)
In-Reply-To: <CADnDZ89UeOErnuYWNmdztnbwCchDvtmSnV9O1aiFKb+jJ222fQ@mail.gmail.com>
References: <20120728232737.23974.14830.idtracker@ietfa.amsl.com> <CADnDZ89YvrdvadRvCEYQA3nux-pdHH9kF5+Bqz-07gWpgYiB+A@mail.gmail.com> <CADnDZ89UeOErnuYWNmdztnbwCchDvtmSnV9O1aiFKb+jJ222fQ@mail.gmail.com>
Date: Wed, 22 Aug 2012 22:59:42 +0200
Message-ID: <CADnDZ88T=6OhQgKgcJPrTJF5_Ed9LvQ0WYPDWEdiSxxsoK9sJQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-manet-olsrv2-15.txt> (The Optimized Link State Routing Protocol version 2) to Proposed Standard
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "iesg@ietf.org" <iesg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Aug 2012 20:59:44 -0000

Reply to your request dated 29/07/2012
Draft Reviewed By: Abdussalam Baryun (AB)   Dated: 22/08/2012

Reviewer Comment AB4: Related to OLSRv2 Messages.
++++++++++++++++++++++++++++++++++++++++

Section 13.2.> Messages with different originating routers MAY be
combined for transmission within the same packet. Messages from other
protocols defined using [RFC5444], including but not limited to
[RFC6130], MAY be combined for transmission within the same packet.
This specification does not define or use any contents of the Packet
Header.

Comment> the document describes the receive and processing of OLSRv2
messages, but not sure why not about processing of OLSRv2 packets.

Question> in case of messages from other protocols, how the OLSRv2
router receives and processes the packet and/or different routing
messages?

Question> is there possibility that OLSRv2 receives control messages
[RFC5444] which are not packed in RFC5444 packet, or is that not
allowed by the specification?

Regards
AB
---------------------------------------------------------------------------------------
This message and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
This message is in compliance with the IETF regulations.
---------------------------------------------------------------------------------------

On 7/29/12, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from the Mobile Ad-hoc Networks WG
> (manet) to consider the following document:
> - 'The Optimized Link State Routing Protocol version 2'
>   <draft-ietf-manet-olsrv2-15.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-08-22. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting. This last call
> period has been extended to handle the fact that it spans the IETF-84
> meeting.
>
> This last call is being re-initiated to include a notice that this document
> includes a normative down reference to an Informational RFC:
> RFC5148, "Jitter considerations in MANETs".
>
> Abstract
>
>    This specification describes version 2 of the Optimized Link State
>    Routing (OLSRv2) protocol for Mobile Ad hoc NETworks (MANETs).
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>

From abdussalambaryun@gmail.com  Wed Aug 22 14:03:42 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 572EA21F8698; Wed, 22 Aug 2012 14:03:42 -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 YKmay-0K5EMZ; Wed, 22 Aug 2012 14:03:41 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id EFB7F21F8650; Wed, 22 Aug 2012 14:03:34 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so43590vbb.31 for <multiple recipients>; Wed, 22 Aug 2012 14:03:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xDaegfNhwYaphQ9p+nGJPBsmPCAYeO4ly8kpHpDX+Gg=; b=H9H1Lyz/nOXkLVzfPQ9jMDB7FCPqKWUBBjTGaFJWj3yOzvf98d5qwzUqIdpHxqZ2ev IKu0WIONpUkETWxO4Ppjgo5M3ezCrodvjEArtYpToFhj6+6z4aTqPDaFRtwSUj7tvGym Xcvd5gIx+saSRlBCot/QLZPiqzBTtpqZ1vBS599eAZicw/yhr2JllVS/uJfU6hWMMByX xpP7kPg4VusjzIlQWFQwSt2ci8Mg3paVIXQbTOKyXsypj3eKzDcnaQBjf9px1e+YjgYG mxusNUn6ro40rE7myitpENOuii9eEEXoglQmQeI/5fNwF9PlJ689is1aYmdc4HuY/Hep MJ0Q==
MIME-Version: 1.0
Received: by 10.221.10.13 with SMTP id oy13mr18140360vcb.14.1345669414342; Wed, 22 Aug 2012 14:03:34 -0700 (PDT)
Received: by 10.220.55.9 with HTTP; Wed, 22 Aug 2012 14:03:34 -0700 (PDT)
In-Reply-To: <CADnDZ88T=6OhQgKgcJPrTJF5_Ed9LvQ0WYPDWEdiSxxsoK9sJQ@mail.gmail.com>
References: <20120728232737.23974.14830.idtracker@ietfa.amsl.com> <CADnDZ89YvrdvadRvCEYQA3nux-pdHH9kF5+Bqz-07gWpgYiB+A@mail.gmail.com> <CADnDZ89UeOErnuYWNmdztnbwCchDvtmSnV9O1aiFKb+jJ222fQ@mail.gmail.com> <CADnDZ88T=6OhQgKgcJPrTJF5_Ed9LvQ0WYPDWEdiSxxsoK9sJQ@mail.gmail.com>
Date: Wed, 22 Aug 2012 23:03:34 +0200
Message-ID: <CADnDZ88iDSmemGYTUYoQs4e1-R-OmxqEh83EpboKVvPO9-b6TA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-manet-olsrv2-15.txt> (The Optimized Link State Routing Protocol version 2) to Proposed Standard
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "iesg@ietf.org" <iesg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Aug 2012 21:03:42 -0000

Reply to your request dated 29/07/2012
Draft Reviewed By: Abdussalam Baryun (AB)   Dated: 22/08/2012

Reviewer Comment AB5:  Related to OLSRv2 update to IP Routing Table.
+++++++++++++++++++++++++++++++++++++++++++++++++++++

Section 4.6> It is intended that the Routing Set can be used for IP packet
routing, by using its contents to update the IP routing table. That
update, and whether any Routing Tuples are not used in the IP routing
table, is outside the scope of this specification.

Question> Why it is out of scope? For OLSRv2 router the *routing
table* update should be in-scope.

Regards
AB
---------------------------------------------------------------------------------------
This message and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
This message is in compliance with the IETF regulations.
---------------------------------------------------------------------------------------


On 7/29/12, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from the Mobile Ad-hoc Networks WG
> (manet) to consider the following document:
> - 'The Optimized Link State Routing Protocol version 2'
>   <draft-ietf-manet-olsrv2-15.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-08-22. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting. This last call
> period has been extended to handle the fact that it spans the IETF-84
> meeting.
>
> This last call is being re-initiated to include a notice that this document
> includes a normative down reference to an Informational RFC:
> RFC5148, "Jitter considerations in MANETs".
>
> Abstract
>
>    This specification describes version 2 of the Optimized Link State
>    Routing (OLSRv2) protocol for Mobile Ad hoc NETworks (MANETs).
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>

From abdussalambaryun@gmail.com  Wed Aug 22 14:40:48 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD72421F8672; Wed, 22 Aug 2012 14:40:48 -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 8riT2KpzAkRC; Wed, 22 Aug 2012 14:40:48 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id C4B9E21F8650; Wed, 22 Aug 2012 14:40:47 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so80654vbb.31 for <multiple recipients>; Wed, 22 Aug 2012 14:40:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HyfWUnV94MEhtbqOhGKq2CKfHq4BZaTfZ+kBlMFlZc8=; b=SP4VCDoyjd0KouKhowMW1MuXUwS77jlh2veNQv4fBYbIjHyUo7mvKXczIX9ZeC4BKY WvAcluNnukv1DzYkwaPod038ecU/q1GeLX+Aiu6ATJY8+5rCMtzEmLTF2QdUeX217N1T 9YyWb4ICydgMls/enb1tHcdHWJb4nuOngWrnzP0IntVZj1C8MoS260Bi0uRO9bNKf5dA Cz+IyhBQ+y1wUHtWSea4ZKRbYJbk+l2Ru9gG+1V+GvufR/N4MLxRF4OiKmmKLBTXp9l8 1uVtIfe1x+n3dRmKDQpzFHRW+48xusdLw+Zu5M7qwcybCTTmRAXxhN5Xrh8FWVBS6d69 26Tg==
MIME-Version: 1.0
Received: by 10.52.178.106 with SMTP id cx10mr8224774vdc.55.1345671647109; Wed, 22 Aug 2012 14:40:47 -0700 (PDT)
Received: by 10.220.55.9 with HTTP; Wed, 22 Aug 2012 14:40:46 -0700 (PDT)
In-Reply-To: <20120728232737.23974.14830.idtracker@ietfa.amsl.com>
References: <20120728232737.23974.14830.idtracker@ietfa.amsl.com>
Date: Wed, 22 Aug 2012 23:40:46 +0200
Message-ID: <CADnDZ89O95LVLLHJYepp-qOOD6A3fK8xnQrmnPvGPUHVGeY41Q@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-manet-olsrv2-15.txt> (The Optimized Link State Routing Protocol version 2) to Proposed Standard
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "iesg@ietf.org" <iesg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Aug 2012 21:40:49 -0000

Reply to your request dated 29/07/2012
Draft Reviewed By: Abdussalam Baryun (AB)   Dated: 22/08/2012

Reviewer Comment AB6: Related to OLSRv2 Interfaces.
++++++++++++++++++++++++++++++++++++

-Is NHDP a must for OLSRv2 routing?

Comment> The relationship between RFC6130 and the [OLSRv2] was not
clear to reviewer (does OLSRv2 depend on NHDP or it may work without
it), is it only that Hello messages are defined in RFC6130 and router
interfaces. Reviewer may understood that the draft-OLSRv2 may extend
to define Hello messages by routers for its non-MANET interfaces.

Question> is there a use case where OLSRv2 may work better without NHDP?

Section 5.> As for the parameters in [RFC6130], parameters defined in this
specification MAY be changed dynamically by a router, and need not be
the same on different routers, even in the same MANET, or, for
interface parameters, on different interfaces of the same router.

Question> but if routers may change parameters individually, what is
the consistency between routers, and how they cooperate?
Comment> it is recommended to clarify some limits and use case to this
issue for stability purposes.

Section 5.1> TC messages and HELLO messages [RFC6130] MUST, in a given
MANET, both be using the same of either of IP or UDP, in order that it
is possible to combine messages of both protocols into the same
[RFC5444] packet for transmission.

Comment> the words "both protocols" are they refering to IP and UDP or
they refer to OLSRv2 and NHDP. It should be clarified even though the
intention is NHDP/OLSRv2 (my add *port* to UDP, or replace *protocols*
with both names)

Question> if there was two different Hellow messages in terms of
information, one of OLSRv2 type and the other NHDP type, what will the
OLSRv2 router take as valid neighbor information?

-OLSRv2 Interfaces' Addresses:

Section 10.5.> R_local_iface_addr is an address of the local interface
over which
an IP packet MUST be sent to reach the destination by the selected
path.

Section 4.6> The purpose of the Routing Set is to determine and record routes
(local interface network address and next hop interface network
address) to all possible routable addresses advertised by this
protocol, as well as of all destinations that are local, i.e., within
one hop, to the router (whether using routable addresses or not).
Only symmetric links are used in such routes.

Question> From above two sections, are the local interface addresses
routable or maybe routable. Are some local interfaces not network
addresses? Are all next hop interface addresses routable.

Regards
AB
---------------------------------------------------------------------------------------
This message and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
This message is in compliance with the IETF regulations.
---------------------------------------------------------------------------------------


On 7/29/12, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from the Mobile Ad-hoc Networks WG
> (manet) to consider the following document:
> - 'The Optimized Link State Routing Protocol version 2'
>   <draft-ietf-manet-olsrv2-15.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-08-22. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting. This last call
> period has been extended to handle the fact that it spans the IETF-84
> meeting.
>
> This last call is being re-initiated to include a notice that this document
> includes a normative down reference to an Informational RFC:
> RFC5148, "Jitter considerations in MANETs".
>
> Abstract
>
>    This specification describes version 2 of the Optimized Link State
>    Routing (OLSRv2) protocol for Mobile Ad hoc NETworks (MANETs).
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>

From adrian@olddog.co.uk  Thu Aug 23 02:40:55 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A443B21F8600; Thu, 23 Aug 2012 02:40:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.511
X-Spam-Level: 
X-Spam-Status: No, score=-2.511 tagged_above=-999 required=5 tests=[AWL=0.088,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Df6PwREbYDm8; Thu, 23 Aug 2012 02:40:55 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id AEACE21F85F4; Thu, 23 Aug 2012 02:40:54 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7N9eqit022620;  Thu, 23 Aug 2012 10:40:52 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7N9epct022614 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 23 Aug 2012 10:40:51 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Abdussalam Baryun'" <abdussalambaryun@gmail.com>
Subject: Your comments on draft-ietf-manet-olsrv2-15.txt
Date: Thu, 23 Aug 2012 10:40:49 +0100
Message-ID: <170101cd8113$61658fa0$2430aee0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac2BEtt1aR3ksgeTSaO2uwdh+ms1ww==
Content-Language: en-gb
Cc: iesg@ietf.org, draft-ietf-manet-olsrv2.all@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Aug 2012 09:40:55 -0000

Hi Abdussalam,

Thank you for your review comments on draft-ietf-manet-olsrv2-15.txt

I see seven separate points raised in separate emails. Can you confirm that this
is the totality of your comments.

I also note that the seventh email was sent to only the IESG. May I have your
permission to share this email with the document authors.

Thanks,
Adrian

> -----Original Message-----
> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of
> Abdussalam Baryun
> Sent: 22 August 2012 23:01
> To: iesg@ietf.org
> Subject: Re: Last Call: <draft-ietf-manet-olsrv2-15.txt> (The Optimized Link
State
> Routing Protocol version 2) to Proposed Standard
> 
> Reply to your request dated 29/07/2012
> Draft Reviewed By: Abdussalam Baryun (AB)   Dated: 22/08/2012
> 
> Reviewer Comment AB7: Comments on text in document history [*].
> https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2/history/
> ++++++++++++++++++++++++++++++++++++
> 
> A key difference between RFC3626 and OLSRv2 is the introduction of
> support for link metrics. An individual draft
> (draft-dearlove-olsrv2-metrics-00) was submitted in 2007, discussing
> the design options, culminating in 2010 with
> draft-dearlove-olsrv2-metrics-05 documenting Working Group consensus
> on this matter. Metrics support was, then, folded into OLSRv2.
> 
> AB> the reviewer thinks the difference is that OLSRv2 is a metric base
> router that uses NHDP and RFC5444 packets which are general MANET
> interface protocol and general MANET packet format respectively.
> OLSRv2 is applicable for more scenarios and routers that are
> constraint devices.
> 
> This version of OLSRv2 was given a one month WGLC, so as to ensure
> sufficient time to review the document.
> 
> AB> my comments within the period was not considered by the authors
> and don't see any consensus from the WG.
> 
> There was an issue concerning the differences between the -14 and -15
> revisions of the document, brought up by one WG member. The consensus
> opinion from the WG is that the document should proceed, without
> additional edits.
> 
> AB> yes there was a new version update after my comments and
> discussion with the authors, but still not happy with the outcome.
> 
> Best Regards
> AB
> +++++++++++++++++
> The end of my comments (the comments were 7 including this, two only
> for the IESG and one addition for only IEFT).
> ========================================================
> 
> On 7/29/12, The IESG <iesg-secretary@ietf.org> wrote:
> >
> > The IESG has received a request from the Mobile Ad-hoc Networks WG
> > (manet) to consider the following document:
> > - 'The Optimized Link State Routing Protocol version 2'
> >   <draft-ietf-manet-olsrv2-15.txt> as Proposed Standard
> >
> > The IESG plans to make a decision in the next few weeks, and solicits
> > final comments on this action. Please send substantive comments to the
> > ietf@ietf.org mailing lists by 2012-08-22. Exceptionally, comments may be
> > sent to iesg@ietf.org instead. In either case, please retain the
> > beginning of the Subject line to allow automated sorting. This last call
> > period has been extended to handle the fact that it spans the IETF-84
> > meeting.
> >
> > This last call is being re-initiated to include a notice that this document
> > includes a normative down reference to an Informational RFC:
> > RFC5148, "Jitter considerations in MANETs".
> >
> > Abstract
> >
> >    This specification describes version 2 of the Optimized Link State
> >    Routing (OLSRv2) protocol for Mobile Ad hoc NETworks (MANETs).
> >
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2/
> >
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2/ballot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >


From ron.even.tlv@gmail.com  Thu Aug 23 03:34:25 2012
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C40121F8602; Thu, 23 Aug 2012 03:34:25 -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 JpeF6yGdxZ4p; Thu, 23 Aug 2012 03:34:24 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id BBBF421F85F7; Thu, 23 Aug 2012 03:34:23 -0700 (PDT)
Received: by bkty7 with SMTP id y7so183836bkt.31 for <multiple recipients>; Thu, 23 Aug 2012 03:34:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=1mgzAF5M7NuPvCTEFBC9S+8BIUd5rwac0BXE9UXOQ5E=; b=NL0RHNFGW9Qq0aILhQ1oxIG4GcIlkQPkBZrnYY7dCMyA2EZe/GxoCGR/r/BnM/YHnx rZgA8y/AANUYl6DVGlsjjPjMObtZRqNBzqoWuqy5Ebuo48LAIX2e5I9fBs0HVs1AZooz xLP3AfJ8IfKHj5rwsb8hl1uR/qHrriHteSpjtI5m1L8JFQ2C8XZpWcaAw/RlEyRZNj+w 8DTiimOpB7WVtHM+j6k3Xnh2Xb1BvDE6BVnmhQFSMGTBGzJM9K+20BtOWHzCwRGFhjrr hXNJkrTF2lv8WfsTfh/ScPSzssfvV7jZ1y7L8puQnAZXmQeINqkW/i40ZV53Js7k0+Np zCJg==
Received: by 10.205.130.17 with SMTP id hk17mr276618bkc.76.1345718062402; Thu, 23 Aug 2012 03:34:22 -0700 (PDT)
Received: from RoniE ([109.64.216.128]) by mx.google.com with ESMTPS id he8sm4306646bkc.3.2012.08.23.03.34.19 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 23 Aug 2012 03:34:21 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-sieve-imap-sieve.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-sieve-imap-sieve-06
Date: Thu, 23 Aug 2012 13:33:01 +0200
Message-ID: <001501cd8123$0fe75630$2fb60290$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0016_01CD8133.D37137A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac2BIwFyV1CLj99kQJaJLAKEzhv3Qg==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Aug 2012 10:34:25 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0016_01CD8133.D37137A0
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-sieve-imap-sieve-06

Reviewer: Roni Even

Review Date:2012-8-22

IETF LC End Date: 2012-8-29

IESG Telechat date:

 

Summary: This draft is ready for publication as a standard track RFC.

 

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments:

 

1.       At the end of section 3.7 and 3.8 "acton" "should be "action"

 


------=_NextPart_000_0016_01CD8133.D37137A0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:117648904;
	mso-list-type:hybrid;
	mso-list-template-ids:651336890 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Please resolve these comments along with any other =
Last Call comments you may receive.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document</s=
pan><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>: =
draft-ietf-sieve-imap-sieve-06</span><span style=3D'font-family:"Courier =
New"'><o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2012&#8211;8&#8211;22<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2012&#8211;8&#8211;29<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</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'> a =
standard track </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>RFC</span><=
span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</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"'>Nits/editor=
ial comments:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>At the end =
of section 3.7 and 3.8 &#8220;acton&#8221; &#8220;should be =
&#8220;action&#8221;<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0016_01CD8133.D37137A0--


From margaretw42@gmail.com  Tue Aug 21 13:11:20 2012
Return-Path: <margaretw42@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E603B21F8767 for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 13:11:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[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 EJy9tsYScUfY for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 13:11:20 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 494C321F8757 for <ietf@ietf.org>; Tue, 21 Aug 2012 13:11:20 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so241580vbb.31 for <ietf@ietf.org>; Tue, 21 Aug 2012 13:11:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=mCG2x47aqZ8EAmZaPz5f7b2h3jxi4YNgmyCDhNiwUXI=; b=o7CJqnHbuJjl5NyFCgzaB/1rQrojNlaYWU+7nTo5pCERek223AYRJrav0xvjfLOU7g yJFXmDDRo7axFDfBiwY/XJsDcOAXnvCcIUZz+8WpGmL9T5G0Q6d3bR0iWKnkkrOX765N jprDeLFtuU/LAyYnrNyMmOHz0flznVD9eliZ9BZodz2oLJlIBmof3bnkvZZQ2d/dXVz+ yaxtFBDYqLds2UGAyLfxV6zSryEEbBS91e3koWfcxIB31QZzD5VSWeZHd8ytku/Zb+Rr /d4HVAHM6ohwZArGa/qAu6DJlYRdxqY8fge/Lv+0NU3sa1hOwzpbFupbBbVxIsUKpYVs dwqA==
Received: by 10.52.38.42 with SMTP id d10mr12297949vdk.132.1345579879262; Tue, 21 Aug 2012 13:11:19 -0700 (PDT)
Received: from lilac-too.home (pool-71-184-120-122.bstnma.fios.verizon.net. [71.184.120.122]) by mx.google.com with ESMTPS id l9sm1058026ves.1.2012.08.21.13.11.16 (version=SSLv3 cipher=OTHER); Tue, 21 Aug 2012 13:11:17 -0700 (PDT)
Subject: Re: Some thoughts about draft-leiba-3777upd-eligibility-02.txt
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Margaret Wasserman <margaretw42@gmail.com>
In-Reply-To: <CALaySJLvvELf5ENAbOsEgt+7ZBGdA7uUf-iCFHoGw13u0jts_A@mail.gmail.com>
Date: Tue, 21 Aug 2012 16:11:04 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9F618894-B14E-49E5-B520-1E13AD439FE0@lilacglade.org>
References: <133201cd7f85$325f59a0$971e0ce0$@olddog.co.uk> <CAC4RtVB=N=CP7ManPZ=Hu65QbrX5WXnWRFFDZ-CpOcKQyqRWqg@mail.gmail.com> <CAF4+nEF96=yCWp7e7AUJ3iBn=gyaX8d9DxsLGL7=N00Ha8cUFw@mail.gmail.com> <142e01cd7fd7$54725e50$fd571af0$@olddog.co.uk> <CALaySJLvvELf5ENAbOsEgt+7ZBGdA7uUf-iCFHoGw13u0jts_A@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Thu, 23 Aug 2012 08:31:06 -0700
Cc: draft-leiba-3777upd-eligibility@tools.ietf.org, adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2012 20:11:21 -0000

Why do you want to rule out employees of those groups?

I don't think that most of them would have any interest in volunteering =
for the nomcom, but why would it be a problem if they did?  I mean, I =
could picture someone who worked for the RFC Editor who was also =
technically involved in the IETF, like Aaron Falk used to be, and I =
don't know why we would want to disqualify someone like that from =
volunteering for the nomcom.

Thoughts?

Margaret


On Aug 21, 2012, at 4:06 PM, Barry Leiba wrote:

>> How about asking Heather for the appropriate term?
>> Seems easier than guessing :-)
>=20
> Good idea.  The point here is to address the regular, paid employees,
> not any people appointed to advise, nor any regular IETF folks who
> might do occasional contracting.  I'll see if Heather has any ideas.
>=20
> Barry


From mcr@sandelman.ca  Tue Aug 21 17:42:06 2012
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 9C44C21F8581 for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 17:42:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.128
X-Spam-Level: 
X-Spam-Status: No, score=-2.128 tagged_above=-999 required=5 tests=[AWL=-0.174, 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 zG0MgEsdDoWA for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 17:42:00 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 9ECA421F8566 for <ietf@ietf.org>; Tue, 21 Aug 2012 17:42:00 -0700 (PDT)
Received: from sandelman.ca (24-139-16-154.eastlink.ca [24.139.16.154]) by relay.sandelman.ca (Postfix) with ESMTPS id 372E88667 for <ietf@ietf.org>; Tue, 21 Aug 2012 20:36:53 -0400 (EDT)
Received: from sandelman.ca (quigon.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 028AFCA0C8 for <ietf@ietf.org>; Tue, 21 Aug 2012 20:04:15 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: IETF Disgust <ietf@ietf.org>
Subject: Re: IETF 92 in Dallas!
In-reply-to: <m2txvwoimp.wl%randy@psg.com>
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net> <BA2EE8F7-92C8-4F10-B10A-2B6FE4FC954A@gmail.com> <502E9614.30409@raszuk.net> <502E9841.8070205@bogus.com> <502E9982.5080909@raszuk.net> <502F4A2A.8090005@krsek.cz> <CD5674C3CD99574EBA7432465FC13C1B22726A1E35@DC-US1MBEX4.global.avaya.com> <503313DE.4090401@gmail.com> <m2txvwoimp.wl%randy@psg.com>
Comments: In-reply-to Randy Bush <randy@psg.com> message dated "Tue, 21 Aug 2012 15:37:34 +0900."
X-Mailer: MH-E 8.3; nmh 1.3; XEmacs 21.4 (patch 22)
Date: Tue, 21 Aug 2012 20:04:15 -0400
Message-ID: <19082.1345593855@sandelman.ca>
Sender: mcr@sandelman.ca
X-Mailman-Approved-At: Thu, 23 Aug 2012 08:31:06 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Aug 2012 00:42:06 -0000

>>>>> "Randy" == Randy Bush <randy@psg.com> writes:
    Randy> sorry, but enough is enough.

I still do not understand visiting a tourist destination (Orlando) 
during it's peak (March).   I also don't understand two meetings in a
row on the US east coast. 





From prvs=358157aca1=sshew@ciena.com  Wed Aug 22 09:34:58 2012
Return-Path: <prvs=358157aca1=sshew@ciena.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55B9C21F8629 for <ietf@ietfa.amsl.com>; Wed, 22 Aug 2012 09:34:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.202
X-Spam-Level: 
X-Spam-Status: No, score=-3.202 tagged_above=-999 required=5 tests=[AWL=0.062,  BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CqquIlmtQud3 for <ietf@ietfa.amsl.com>; Wed, 22 Aug 2012 09:34:48 -0700 (PDT)
Received: from mx0a-00103a01.pphosted.com (mx0a-00103a01.pphosted.com [67.231.144.234]) by ietfa.amsl.com (Postfix) with ESMTP id 6F73A21F8625 for <ietf@ietf.org>; Wed, 22 Aug 2012 09:34:48 -0700 (PDT)
Received: from pps.filterd (m0000419 [127.0.0.1]) by mx0a-00103a01.pphosted.com (8.14.4/8.14.4) with SMTP id q7MGPZpe004658; Wed, 22 Aug 2012 12:34:44 -0400
Received: from mdwexght02.ciena.com (LIN1-118-36-29.ciena.com [63.118.36.29]) by mx0a-00103a01.pphosted.com with ESMTP id 16w2np83a2-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 22 Aug 2012 12:34:43 -0400
Received: from ONWVEXCHHT02.ciena.com (10.128.6.17) by MDWEXGHT02.ciena.com (10.4.140.213) with Microsoft SMTP Server (TLS) id 8.3.279.1; Wed, 22 Aug 2012 12:34:43 -0400
Received: from ONWVEXCHMB02.ciena.com ([::1]) by ONWVEXCHHT02.ciena.com ([::1]) with mapi; Wed, 22 Aug 2012 12:34:42 -0400
From: "Shew, Stephen" <sshew@ciena.com>
To: Acee Lindem <acee.lindem@ericsson.com>, "Ong, Lyndon" <Lyong@Ciena.com>
Date: Wed, 22 Aug 2012 12:34:39 -0400
Subject: RE: Last Call: <draft-ietf-ccamp-rfc5787bis-05.txt> 
Thread-Topic: Last Call: <draft-ietf-ccamp-rfc5787bis-05.txt> 
Thread-Index: Ac1/4y/p8Qqt1aB6SN6NYjuVuq+4bwAnNpSQ
Message-ID: <510C3D5C5DFBCB46AE189D936C1DD605A60CC92886@ONWVEXCHMB02.ciena.com>
References: <A0B4FC0A5EFBD44585414760DB4FD2749F512AA9@MDWEXGMB02.ciena.com> <D3266962-DD41-4FBA-A0A2-E1F9D5BF2B3C@ericsson.com>
In-Reply-To: <D3266962-DD41-4FBA-A0A2-E1F9D5BF2B3C@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="SHA-1 with ECDSA"; boundary="--=_NextPart_EE_123439318.571538808"
MIME-Version: 1.0
X-TM-AS-Product-Ver: SMEX-10.0.0.1412-7.000.1014-19130.006
X-TM-AS-Result: No--37.156800-8.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855, 1.0.260, 0.0.0000 definitions=2012-08-22_04:2012-08-22, 2012-08-22, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=2 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1208220152
X-Mailman-Approved-At: Thu, 23 Aug 2012 08:31:06 -0700
Cc: "draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org" <draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org>, "Andrew G. \(Andy\) Malis" <andrew.g.malis@verizon.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, 22 Aug 2012 16:34:58 -0000

----=_NextPart_EE_123439318.571538808
Content-Type: multipart/alternative;
	boundary="--=_NextPart_EE_123439225.571206488"


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

Thanks for the reply. If I understand correctly, this means that the SCN=
 topology must match the transport topology when applying OSPF for ASON r=
outing.  This is because the Local TE Router Identifier and the Remote T=
E Router Identifier in the Local and Remote TE Router ID sub-TLV are the=
 same as the TE Router ID in the TE Router Address TLV. If this is corre=
ct, then I think the draft should state the assumption that the SCN topo=
logy and transport plane topology are aligned. It=E2=80=99s an important=
 assumption to state since management systems of SDH/OTN networks have t=
opologies of the transport network in non-IP address formats (esp. TL-1 T=
IDs) and these need to be mapped to TE Router IDs in the SCN space when t=
his draft is applied.  I assume it implies that there should be a single=
 SCN or non-overlapping IP address spaces if there are multiple SCNs, fo=
r a given transport topology otherwise the SCN topology representing the=
 transport topology could have duplicate identifier values.

=20

Stephen

=20

From: Acee Lindem =5Bmailto:acee.lindem=40ericsson.com=5D=20
Sent: 21 August, 2012 17:23
To: Ong, Lyndon
Cc: ietf=40ietf.org; Shew, Stephen; draft-ietf-ccamp-rfc5787bis.all=40to=
ols.ietf.org; Andrew G. (Andy) Malis
Subject: Re: Last Call: <draft-ietf-ccamp-rfc5787bis-05.txt>=20

=20

Hi Stephen, Lyndon,=20

Andy and I have had discussions with the CCAMP chairs and AD. We have co=
me to the conclusion that we cannot merely change the name space for the=
 advertised TE Router ID since this would imply a change to the GMPL mod=
el for setting up LSPs. In GMPL, the LSP endpoints are in the Signaling C=
ontrol Network (SCN) and this cannot be changed without a distinct model=
 for ASON LSP establishment complete with the specification of the chang=
es to path computation, RSVP path signaling, and RSVP Explicit Route Obj=
ect (ERO) handling. In essence, this change would add a level of indirec=
tion from the SNPP to the SCN. In the context of this draft, we are not g=
oing to deviate from the GMPLS LSP model and, hence, will not incorporat=
ing the suggested changes.=20

Thanks,

Acee=20

On Aug 17, 2012, at 7:58 PM, Ong, Lyndon wrote:





(Submitted on behalf of Stephen Shew)

=20

I would like to raise an issue with draft-ietf-ccamp-rfc5787bis-05.txt.  =
The issue does not affect the proposed sub-TLVs or their semantics, so i=
t would not affect an implementation. I believe some statements in the d=
ocument should be edited to avoid confusion over ASON terminology as def=
ined in ITU-T Recommendation G.8080, for which I am editor.

=20

It concerns the definition of =E2=80=9CASON reachability=E2=80=9D which c=
hanged during the course of the document from being a transport plane ad=
dress, the SubNetwork Point Pool (SNPP) space, to the Signalling Control=
 Network (SCN) address space.  I think the root of the issue is that the=
 visibility of the three address spaces described in ASON (G.8080) is no=
t always made clear when discussing using OSPF for ASON Routing.  Sectio=
n 3 of G.8080 states that:

There are three categories of identifiers used for ASON routing

   (G7715.1): transport plane names, control plane identifiers for

   components, and Signaling Communications Network (SCN) addresses.

=20

In -03 of the document, the term SNPP was used. This is the SubNetwork P=
oint Pool space that describes the data plane and is defined in G.8080 S=
ection 10.  It names the subnetwork (and/or containing subnetworks) to w=
hich Subnetwork Points (SNPs) are scoped. From G.8081: =E2=80=9CThe SNP i=
s an abstraction that represents an actual or potential underlying conne=
ction point (CP) (or connection termination point (CTP)) or an actual or=
 potential termination connection point (TCP) or trail termination point=
 (TTP). Several SNPs (in different subnetwork partitions) may represent t=
he same TCP or CP.=22

=20

In concrete terms, an SNPP would name an OTN switch, and an SNP would be=
 a label identifying an ODU0.  For the topology of the transport plane, S=
NPP and SNPP link names are used.  Path computation is performed over su=
ch a topology.  If a path can be computed between two SNPPs, they are re=
achable in ASON terms. For example, and ingress OTN switch for an ODU1 c=
onnection that terminates on an egress OTN switch.

=20

The Signalling Control Network (SCN) is a separate network over which co=
ntrol messages are sent. It has a topology independent of the transport p=
lane.  Path computation on the SCN address space is used to connect SCN a=
ddress.  SDH/OTN networks often have a separate IP network as the SCN ne=
twork and the topology of the SCN network does not have to follow the to=
pology of the transport network.

=20

ASON Control Plane Component identifiers are the third name space and id=
entify routing and signalling instances.  It is expected that they form a=
djacencies over the SCN.  The topology of the adjacencies is independent=
 of the SCN and transport plane topologies.  =E2=80=9CReachability=E2=80=
=9D between two control plane components would be some sequence of adjac=
encies.  It is entirely possible to have two separate control planes run=
ning over the same SCN network, or one control plane that uses several S=
CNs.  For example, imagine some OSPF instances whose adjacencies were al=
l targeted and each adjacency traversed a separate private IP network.  T=
he OSPF instances would need to identified by a common address space so t=
hat they are distinguished from each other, but the TE interfaces could h=
ave overlapping IPv4 values because they would be in different private I=
P network spaces.

=20

What makes the discussion of =E2=80=9CTE router ID=E2=80=9D confusing is=
 that as applied to a transport network, every node gets a =E2=80=9CTE r=
outer ID=E2=80=9D and so it can be used in the transport topology for pa=
th computation.  In that sense it is =E2=80=9Creachable=E2=80=9D in the d=
ataplane.  However, it is also (I think) an address that is implicitly i=
n the SCN space in some implementations and so it takes on a dual meanin=
g of =E2=80=9Creachability=E2=80=9D at the IP layer as in the sentence f=
rom the I-D =E2=80=9CThis TLV specifies a stable OSPF TE node IP address=
, i.e., the IP address is always reachable when there is IP connectivity=
 to the associated OSPF TE node.=E2=80=9D.  If a router were instantiate=
d without any routing protocols, as in one form of Software Defined Netw=
orks (SDNs), an identifier would be needed for the node itself so that p=
ath computation in a centralized controller could form the router data p=
lane topology.

=20

Suggested changes to the draft are:

In section 3, third paragraph:  =22In the context of OSPF Traffic Engine=
ering (TE), an ASON transport node corresponds to a unique OSPF TE node.=
  An OSPF TE node is uniquely identified by the TE Router Address TLV =5B=
RFC3630=5D. In this document, this TE Router Address is referred to as t=
he TE Router ID, which is in the ASON SCN name space.=22  However, G.808=
0 distinguishes between the transport node and its associated control pl=
ane components, esp. the Routing Controller.  It is the control plane co=
mponent that is accessed through the SCN rather than the transport node i=
tself.

I propose changing the statement to say: =22In this document, this TE Ro=
uter Address is referred to as the TE Router ID, which is in the ASON SN=
PP name space.=E2=80=9D

Alternatively, we could just delete the sentence =E2=80=9CIn this docume=
nt, this TE Router Address is referred to as the TE Router ID, which is i=
n the ASON SNPP name space.=E2=80=9D.

=20

In section 4, first paragraph, reachability of endpoints in the transpor=
t plane is described as follows:

=22In ASON, reachability refers to the set of endpoints reachable in the=
 transport plane by an associated ASON transport node.  Reachable entiti=
es are identified in the ASON SCN name space.=22  As discussed above, on=
ly the control plane components are accessed through the SCN, not the tr=
ansport nodes themselves.  Entities that are reachable in the transport p=
lane are identified through ASON SNPPs rather than ASON SCN addresses.  T=
herefore I suggest removing the second sentence completely so that it re=
ads simply =22In ASON, reachability refers to the set of endpoints reach=
able in the transport plane by an associated ASON transport node. =E2=80=
=9C

=20

Finally, in section 6.2, first paragraph following the format diagram, i=
t is stated:  =22If it is not included in a Node Attribute TLV or a valu=
e of 0 is specified for the Local TE Router Identifier, the Note Attribu=
te TLV will not be used for determining ASON SCN reachability.=22=20

Again, the text should be edited to make the distinction between transpo=
rt plane and SCN clearer, I suggest modifying the statement to refer to =22=
ASON reachability=22 rather than =22ASON SCN reachability=22.  The state=
ment would read as follows (also correcting the spelling of the TLV):

=22If it is not included in a Node Attribute TLV or a value of 0 is spec=
ified for the Local TE Router Identifier, the Node Attribute TLV will no=
t be used for determining ASON reachability.=22

=20

Stephen Shew

=20

-----Original Message-----

From: ietf-announce-bounces=40ietf.org =5Bmailto:ietf-announce-bounces=40=
ietf.org=5D On Behalf Of The IESG

Sent: Friday, July 20, 2012 11:19 AM

To: IETF-Announce

Cc: ccamp=40ietf.org

Subject: Last Call: <draft-ietf-ccamp-rfc5787bis-05.txt> (ASON Routing f=
or OSPFv2 Protocols) to Proposed Standard

=20

=20

The IESG has received a request from the Common Control and Measurement P=
lane WG (ccamp) to consider the following document:

- 'ASON Routing for OSPFv2 Protocols'

  <draft-ietf-ccamp-rfc5787bis-05.txt> as Proposed Standard

=20

The IESG plans to make a decision in the next few weeks, and solicits fi=
nal comments on this action. Please send substantive comments to the iet=
f=40ietf.org mailing lists by 2012-08-17. Exceptionally, comments may be=
 sent to iesg=40ietf.org instead. In either case, please retain the begi=
nning of the Subject line to allow automated sorting. This is a four- we=
ek last call period because it spans the IETF-84 meeting.

=20

Abstract

=20

   The ITU-T has defined an architecture and requirements for operating

   an Automatically Switched Optical Network (ASON).

=20

   The Generalized Multiprotocol Label Switching (GMPLS) protocol suite

   is designed to provide a control plane for a range of network

   technologies including optical networks such as time division

   multiplexing (TDM) networks including SONET/SDH and Optical Transport=


   Networks (OTNs), and lambda switching optical networks.

=20

   The requirements for GMPLS routing to satisfy the requirements of

   ASON routing, and an evaluation of existing GMPLS routing protocols

   are provided in other documents.  This document defines extensions to=


   the OSPFv2 Link State Routing Protocol to meet the requirements for

   routing in an ASON.

=20

   Note that this work is scoped to the requirements and evaluation

   expressed in RFC 4258 and RFC 4652 and the ITU-T Recommendations

   current when those documents were written.  Future extensions of

   revisions of this work may be necessary if the ITU-T Recommendations

   are revised or if new requirements are introduced into a revision of

   RFC 4258. This document obsoletes RFC 5787 and updates RFC 5786.

=20

=20

=20

The file can be obtained via

http://datatracker.ietf.org/doc/draft-ietf-ccamp-rfc5787bis/

=20

IESG discussion can be tracked via

http://datatracker.ietf.org/doc/draft-ietf-ccamp-rfc5787bis/ballot/

=20

No IPR declarations have been submitted directly on this I-D.

=20

=20

Stephen Shew =7C Director, Standards
sshew=40ciena.com <mailto:jdoe=40ciena.com>  =7C 3500 Carling Ave. =7C O=
ttawa CANADA K2H 8E9
Direct +1.613.670.3211

=20

=20


----=_NextPart_EE_123439225.571206488
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D=22urn:schemas-microsoft-com:vml=22 xmlns:o=3D=22urn:sch=
emas-microsoft-com:office:office=22 xmlns:w=3D=22urn:schemas-microsoft-c=
om:office:word=22 xmlns:m=3D=22http://schemas.microsoft.com/office/2004/=
12/omml=22 xmlns=3D=22http://www.w3.org/TR/REC-html40=22><head><meta htt=
p-equiv=3DContent-Type content=3D=22text/html; charset=3Dus-ascii=22><me=
ta name=3DGenerator content=3D=22Microsoft Word 12 (filtered medium)=22>=
<base href=3D=22x-msg://221/=22><style><=21--
/* Font Definitions */
=40font-face
	=7Bfont-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;=7D
=40font-face
	=7Bfont-family:=22Cambria Math=22;
	panose-1:2 4 5 3 5 4 6 3 2 4;=7D
=40font-face
	=7Bfont-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;=7D
=40font-face
	=7Bfont-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;=7D
=40font-face
	=7Bfont-family:=22=5C=40SimSun=22;
	panose-1:2 1 6 0 3 1 1 1 1 1;=7D
=40font-face
	=7Bfont-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;=7D
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	=7Bmargin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:=22Times New Roman=22,=22serif=22;=7D
a:link, span.MsoHyperlink
	=7Bmso-style-priority:99;
	color:blue;
	text-decoration:underline;=7D
a:visited, span.MsoHyperlinkFollowed
	=7Bmso-style-priority:99;
	color:purple;
	text-decoration:underline;=7D
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	=7Bmso-style-priority:99;
	mso-style-link:=22Balloon Text Char=22;
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:=22Tahoma=22,=22sans-serif=22;=7D
span.apple-style-span
	=7Bmso-style-name:apple-style-span;=7D
span.apple-converted-space
	=7Bmso-style-name:apple-converted-space;=7D
span.EmailStyle19
	=7Bmso-style-type:personal-reply;
	font-family:=22Times New Roman=22,=22serif=22;
	color:=2331849B;=7D
span.BalloonTextChar
	=7Bmso-style-name:=22Balloon Text Char=22;
	mso-style-priority:99;
	mso-style-link:=22Balloon Text=22;
	font-family:=22Tahoma=22,=22sans-serif=22;=7D
=2EMsoChpDefault
	=7Bmso-style-type:export-only;
	font-size:10.0pt;=7D
=40page WordSection1
	=7Bsize:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;=7D
div.WordSection1
	=7Bpage:WordSection1;=7D
--></style><=21--=5Bif gte mso 9=5D><xml>
<o:shapedefaults v:ext=3D=22edit=22 spidmax=3D=221026=22 />
</xml><=21=5Bendif=5D--><=21--=5Bif gte mso 9=5D><xml>
<o:shapelayout v:ext=3D=22edit=22>
<o:idmap v:ext=3D=22edit=22 data=3D=221=22 />
</o:shapelayout></xml><=21=5Bendif=5D--></head><body lang=3DEN-US link=3D=
blue vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span=
 style=3D'font-size:11.0pt;color:=2331849B'>Thanks for the reply. If I u=
nderstand correctly, this means that the SCN topology must match the tra=
nsport topology when applying OSPF for ASON routing.&nbsp; This is becau=
se the </span><span style=3D'font-size:11.0pt;color:=2331849B'>Local TE R=
outer Identifier and the Remote TE Router Identifier in the Local and Re=
mote TE Router ID sub-TLV are the same as the TE Router ID in the TE Rou=
ter Address TLV. If this is correct, then I think the draft should state=
 the assumption that the SCN topology and transport plane topology are a=
ligned. It&=238217;s an important assumption to state since management s=
ystems of SDH/OTN networks have topologies of the transport network in n=
on-IP address formats (esp. TL-1 TIDs) and these need to be mapped to TE=
 Router IDs in the SCN space when this draft is applied.&nbsp; I assume i=
t implies that there should be a single SCN or non-overlapping IP addres=
s spaces if there are multiple SCNs, for a given transport topology othe=
rwise the SCN topology representing the transport topology could have du=
plicate identifier values.<o:p></o:p></span></p><p class=3DMsoNormal><sp=
an style=3D'font-size:11.0pt;color:=2331849B'><o:p>&nbsp;</o:p></span></=
p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;color:=2331849B'>=
Stephen</span><span style=3D'font-size:11.0pt;color:=2331849B'><o:p></o:=
p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;color:=
=2331849B'><o:p>&nbsp;</o:p></span></p><div><div style=3D'border:none;bo=
rder-top:solid =23B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMso=
Normal><b><span style=3D'font-size:10.0pt;font-family:=22Tahoma=22,=22sa=
ns-serif=22'>From:</span></b><span style=3D'font-size:10.0pt;font-family=
:=22Tahoma=22,=22sans-serif=22'> Acee Lindem =5Bmailto:acee.lindem=40eri=
csson.com=5D <br><b>Sent:</b> 21 August, 2012 17:23<br><b>To:</b> Ong, L=
yndon<br><b>Cc:</b> ietf=40ietf.org; Shew, Stephen; draft-ietf-ccamp-rfc=
5787bis.all=40tools.ietf.org; Andrew G. (Andy) Malis<br><b>Subject:</b> R=
e: Last Call: &lt;draft-ietf-ccamp-rfc5787bis-05.txt&gt; <o:p></o:p></sp=
an></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3D=
MsoNormal>Hi Stephen, Lyndon,&nbsp;<o:p></o:p></p><div><p class=3DMsoNor=
mal>Andy and I have had discussions with the CCAMP chairs and AD. We hav=
e come to the conclusion that we cannot merely change the name space for=
 the advertised TE Router ID since this would imply a change to the GMPL=
 model for setting up LSPs. In GMPL, the LSP endpoints are in the Signal=
ing Control Network (SCN) and this cannot be changed without a distinct m=
odel for ASON LSP establishment complete with the specification of the c=
hanges to path computation, RSVP path signaling, and RSVP Explicit Route=
 Object (ERO) handling. In essence, this change would add a level of ind=
irection from the SNPP to the SCN. In the context of this draft, we are n=
ot going to deviate from the GMPLS LSP model and, hence, will not incorp=
orating the suggested changes.&nbsp;<o:p></o:p></p></div><div><p class=3D=
MsoNormal>Thanks,<o:p></o:p></p></div><div><p class=3DMsoNormal>Acee&nbs=
p;<o:p></o:p></p><div><div><p class=3DMsoNormal>On Aug 17, 2012, at 7:58=
 PM, Ong, Lyndon wrote:<o:p></o:p></p></div><p class=3DMsoNormal><br><br=
><o:p></o:p></p><div><div><p class=3DMsoNormal><span lang=3DEN-GB style=3D=
'font-size:11.0pt;font-family:=22Calibri=22,=22sans-serif=22'>(Submitted=
 on behalf of Stephen Shew)</span><span style=3D'font-size:11.0pt;font-f=
amily:=22Calibri=22,=22sans-serif=22'><o:p></o:p></span></p></div><div><=
p class=3DMsoNormal><span lang=3DEN-GB style=3D'font-size:11.0pt;font-fa=
mily:=22Calibri=22,=22sans-serif=22'>&nbsp;</span><span style=3D'font-si=
ze:11.0pt;font-family:=22Calibri=22,=22sans-serif=22'><o:p></o:p></span>=
</p></div><div><p class=3DMsoNormal><span lang=3DEN-GB style=3D'font-siz=
e:11.0pt;font-family:=22Calibri=22,=22sans-serif=22'>I would like to rai=
se an issue with draft-ietf-ccamp-rfc5787bis-05.txt.&nbsp; The issue doe=
s not affect the proposed sub-TLVs or their semantics, so it would not a=
ffect an implementation. I believe some statements in the document shoul=
d be edited to avoid confusion over ASON terminology as defined in ITU-T=
 Recommendation G.8080, for which I am editor.</span><span style=3D'font=
-size:11.0pt;font-family:=22Calibri=22,=22sans-serif=22'><o:p></o:p></sp=
an></p></div><div><p class=3DMsoNormal><span lang=3DEN-GB style=3D'font-=
size:11.0pt;font-family:=22Calibri=22,=22sans-serif=22'>&nbsp;</span><sp=
an style=3D'font-size:11.0pt;font-family:=22Calibri=22,=22sans-serif=22'=
><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span lang=3DEN-G=
B style=3D'font-size:11.0pt;font-family:=22Calibri=22,=22sans-serif=22'>=
It concerns the definition of &=238220;ASON reachability&=238221; which c=
hanged during the course of the document from being a transport plane ad=
dress, the SubNetwork Point Pool (SNPP) space, to the Signalling Control=
 Network (SCN) address space.&nbsp; I think the root of the issue is tha=
t the visibility of the three address spaces described in ASON (G.8080) i=
s not always made clear when discussing using OSPF for ASON Routing.&nbs=
p; Section 3 of G.8080 states that:</span><span style=3D'font-size:11.0p=
t;font-family:=22Calibri=22,=22sans-serif=22'><o:p></o:p></span></p></di=
v><div><p class=3DMsoNormal><span lang=3DEN-GB style=3D'font-size:11.0pt=
;font-family:=22Courier New=22'>There are three categories of identifier=
s used for ASON routing</span><span style=3D'font-size:11.0pt'><o:p></o:=
p></span></p></div><div><p class=3DMsoNormal><span lang=3DEN-GB style=3D=
'font-size:11.0pt;font-family:=22Courier New=22'>&nbsp;&nbsp; (G7715.1):=
 transport plane names, control plane identifiers for</span><span style=3D=
'font-size:11.0pt'><o:p></o:p></span></p></div><div><p class=3DMsoNormal=
><span lang=3DEN-GB style=3D'font-size:11.0pt;font-family:=22Courier New=
=22'>&nbsp;&nbsp; components, and Signaling Communications Network (SCN)=
 addresses.</span><span style=3D'font-size:11.0pt'><o:p></o:p></span></p=
></div><div><p class=3DMsoNormal><span lang=3DEN-GB style=3D'font-size:1=
1.0pt'>&nbsp;</span><span style=3D'font-size:11.0pt;font-family:=22Calib=
ri=22,=22sans-serif=22'><o:p></o:p></span></p></div><div><p class=3DMsoN=
ormal><span lang=3DEN-GB style=3D'font-size:11.0pt;font-family:=22Calibr=
i=22,=22sans-serif=22'>In -03 of the document, the term SNPP was used. T=
his is the SubNetwork Point Pool space that describes the data plane and=
 is defined in G.8080 Section 10.&nbsp; It names the subnetwork (and/or c=
ontaining subnetworks) to which Subnetwork Points (SNPs) are scoped. Fro=
m G.8081: &=238220;The SNP is an abstraction that represents an actual o=
r potential underlying connection point (CP) (or connection termination p=
oint (CTP)) or an actual or potential termination connection point (TCP)=
 or trail termination point (TTP). Several SNPs (in different subnetwork=
 partitions) may represent the same TCP or CP.</span><span dir=3DRTL></s=
pan><span dir=3DRTL></span><span lang=3DAR-AE dir=3DRTL style=3D'font-si=
ze:11.0pt;font-family:=22Arial=22,=22sans-serif=22'><span dir=3DRTL></sp=
an><span dir=3DRTL></span>&quot;</span><span style=3D'font-size:11.0pt;f=
ont-family:=22Calibri=22,=22sans-serif=22'><o:p></o:p></span></p></div><=
div><p class=3DMsoNormal><span lang=3DEN-GB style=3D'font-size:11.0pt;fo=
nt-family:=22Calibri=22,=22sans-serif=22'>&nbsp;</span><span style=3D'fo=
nt-size:11.0pt;font-family:=22Calibri=22,=22sans-serif=22'><o:p></o:p></=
span></p></div><div><p class=3DMsoNormal><span lang=3DEN-GB style=3D'fon=
t-size:11.0pt;font-family:=22Calibri=22,=22sans-serif=22'>In concrete te=
rms, an SNPP would name an OTN switch, and an SNP would be a label ident=
ifying an ODU0.&nbsp; For the topology of the transport plane, SNPP and S=
NPP link names are used.&nbsp; Path computation is performed over such a=
 topology.&nbsp; If a path can be computed between two SNPPs, they are r=
eachable in ASON terms. For example, and ingress OTN switch for an ODU1 c=
onnection that terminates on an egress OTN switch.</span><span style=3D'=
font-size:11.0pt;font-family:=22Calibri=22,=22sans-serif=22'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span style=3D'font-size:11.0=
pt;font-family:=22Arial=22,=22sans-serif=22'>&nbsp;</span><span style=3D=
'font-size:11.0pt;font-family:=22Calibri=22,=22sans-serif=22'><o:p></o:p=
></span></p></div><div><p class=3DMsoNormal><span lang=3DEN-GB style=3D'=
font-size:11.0pt;font-family:=22Calibri=22,=22sans-serif=22'>The Signall=
ing Control Network (SCN) is a separate network over which control messa=
ges are sent. It has a topology independent of the transport plane.&nbsp=
; Path computation on the SCN address space is used to connect SCN addre=
ss.&nbsp; SDH/OTN networks often have a separate IP network as the SCN n=
etwork and the topology of the SCN network does not have to follow the t=
opology of the transport network.</span><span style=3D'font-size:11.0pt;=
font-family:=22Calibri=22,=22sans-serif=22'><o:p></o:p></span></p></div>=
<div><p class=3DMsoNormal><span dir=3DRTL></span><span dir=3DRTL></span>=
<span lang=3DAR-SA dir=3DRTL style=3D'font-size:11.0pt'><span dir=3DRTL>=
</span><span dir=3DRTL></span>&nbsp;</span><span style=3D'font-size:11.0=
pt;font-family:=22Calibri=22,=22sans-serif=22'><o:p></o:p></span></p></d=
iv><div><p class=3DMsoNormal><span lang=3DEN-GB style=3D'font-size:11.0p=
t;font-family:=22Calibri=22,=22sans-serif=22'>ASON Control Plane Compone=
nt identifiers are the third name space and identify routing and signall=
ing instances.&nbsp; It is expected that they form adjacencies over the S=
CN.&nbsp; The topology of the adjacencies is independent of the SCN and t=
ransport plane topologies.&nbsp; &=238220;Reachability&=238221; between t=
wo control plane components would be some sequence of adjacencies.&nbsp;=
 It is entirely possible to have two separate control planes running ove=
r the same SCN network, or one control plane that uses several SCNs.&nbs=
p; For example, imagine some OSPF instances whose adjacencies were all t=
argeted and each adjacency traversed a separate private IP network.&nbsp=
; The OSPF instances would need to identified by a common address space s=
o that they are distinguished from each other, but the TE interfaces cou=
ld have overlapping IPv4 values because they would be in different priva=
te IP network spaces.</span><span style=3D'font-size:11.0pt;font-family:=
=22Calibri=22,=22sans-serif=22'><o:p></o:p></span></p></div><div><p clas=
s=3DMsoNormal><span lang=3DEN-GB style=3D'font-size:11.0pt;font-family:=22=
Calibri=22,=22sans-serif=22'>&nbsp;</span><span style=3D'font-size:11.0p=
t;font-family:=22Calibri=22,=22sans-serif=22'><o:p></o:p></span></p></di=
v><div><p class=3DMsoNormal><span lang=3DEN-GB style=3D'font-size:11.0pt=
;font-family:=22Calibri=22,=22sans-serif=22'>What makes the discussion o=
f &=238220;TE router ID&=238221; confusing is that as applied to a trans=
port network, every node gets a &=238220;TE router ID&=238221; and so it=
 can be used in the transport topology for path computation.&nbsp; In th=
at sense it is &=238220;reachable&=238221; in the dataplane.&nbsp; Howev=
er, it is also (I think) an address that is implicitly in the SCN space i=
n some implementations and so it takes on a dual meaning of &=238220;rea=
chability&=238221; at the IP layer as in the sentence from the I-D &=238=
220;This TLV specifies a stable OSPF TE node IP address, i.e., the IP ad=
dress is always reachable when there is IP connectivity to the associate=
d OSPF TE node.&=238221;.&nbsp; If a router were instantiated without an=
y routing protocols, as in one form of Software Defined Networks (SDNs),=
 an identifier would be needed for the node itself so that path computat=
ion in a centralized controller could form the router data plane topolog=
y.</span><span style=3D'font-size:11.0pt;font-family:=22Calibri=22,=22sa=
ns-serif=22'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span=
 lang=3DEN-GB style=3D'font-size:11.0pt;font-family:=22Calibri=22,=22san=
s-serif=22'>&nbsp;</span><span style=3D'font-size:11.0pt;font-family:=22=
Calibri=22,=22sans-serif=22'><o:p></o:p></span></p></div><div><p class=3D=
MsoNormal><span lang=3DEN-GB style=3D'font-size:11.0pt;font-family:=22Ca=
libri=22,=22sans-serif=22'>Suggested changes to the draft are:</span><sp=
an style=3D'font-size:11.0pt;font-family:=22Calibri=22,=22sans-serif=22'=
><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span lang=3DEN-G=
B style=3D'font-size:11.0pt;font-family:=22Calibri=22,=22sans-serif=22'>=
In section 3, third paragraph:&nbsp; &quot;In the context of OSPF Traffi=
c Engineering (TE), an ASON transport node corresponds to a unique OSPF T=
E node.&nbsp; An OSPF TE node is uniquely identified by the TE Router Ad=
dress TLV =5BRFC3630=5D. In this document, this TE Router Address is ref=
erred to as the TE Router ID, which is in the ASON SCN name space.&quot;=
&nbsp; However, G.8080 distinguishes between the transport node and its a=
ssociated control plane components, esp. the Routing Controller.&nbsp; I=
t is the control plane component that is accessed through the SCN rather=
 than the transport node itself.</span><span style=3D'font-size:11.0pt;f=
ont-family:=22Calibri=22,=22sans-serif=22'><o:p></o:p></span></p></div><=
div><p class=3DMsoNormal><span lang=3DEN-GB style=3D'font-size:11.0pt;fo=
nt-family:=22Calibri=22,=22sans-serif=22'>I propose changing the stateme=
nt to say: &quot;In this document, this TE Router Address is referred to=
 as the TE Router ID, which is in the ASON SNPP name space.&=238221;</sp=
an><span style=3D'font-size:11.0pt;font-family:=22Calibri=22,=22sans-ser=
if=22'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span lang=3D=
EN-GB style=3D'font-size:11.0pt;font-family:=22Calibri=22,=22sans-serif=22=
'>Alternatively, we could just delete the sentence &=238220;In this docu=
ment, this TE Router Address is referred to as the TE Router ID, which i=
s in the ASON SNPP name space.&=238221;.</span><span style=3D'font-size:=
11.0pt;font-family:=22Calibri=22,=22sans-serif=22'><o:p></o:p></span></p=
></div><div><p class=3DMsoNormal><span lang=3DEN-GB style=3D'font-size:1=
1.0pt;font-family:=22Calibri=22,=22sans-serif=22'>&nbsp;</span><span sty=
le=3D'font-size:11.0pt;font-family:=22Calibri=22,=22sans-serif=22'><o:p>=
</o:p></span></p></div><div><p class=3DMsoNormal><span lang=3DEN-GB styl=
e=3D'font-size:11.0pt;font-family:=22Calibri=22,=22sans-serif=22'>In sec=
tion 4, first paragraph, reachability of endpoints in the transport plan=
e is described as follows:</span><span style=3D'font-size:11.0pt;font-fa=
mily:=22Calibri=22,=22sans-serif=22'><o:p></o:p></span></p></div><div><p=
 class=3DMsoNormal><span lang=3DEN-GB style=3D'font-size:11.0pt;font-fam=
ily:=22Calibri=22,=22sans-serif=22'>&quot;In ASON, reachability refers t=
o the set of endpoints reachable in the transport plane by an associated=
 ASON transport node.&nbsp; Reachable entities are identified in the ASO=
N SCN name space.&quot;&nbsp; As discussed above, only the control plane=
 components are accessed through the SCN, not the transport nodes themse=
lves.&nbsp; Entities that are reachable in the transport plane are ident=
ified through ASON SNPPs rather than ASON SCN addresses.&nbsp; Therefore=
 I suggest removing the second sentence completely so that it reads simp=
ly &quot;In ASON, reachability refers to the set of endpoints reachable i=
n the transport plane by an associated ASON transport node.&nbsp;&=23822=
0;</span><span style=3D'font-size:11.0pt;font-family:=22Calibri=22,=22sa=
ns-serif=22'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span=
 lang=3DEN-GB style=3D'font-size:11.0pt;font-family:=22Calibri=22,=22san=
s-serif=22'>&nbsp;</span><span style=3D'font-size:11.0pt;font-family:=22=
Calibri=22,=22sans-serif=22'><o:p></o:p></span></p></div><div><p class=3D=
MsoNormal><span lang=3DEN-GB style=3D'font-size:11.0pt;font-family:=22Ca=
libri=22,=22sans-serif=22'>Finally, in section 6.2, first paragraph foll=
owing the format diagram, it is stated:&nbsp; &quot;If it is not include=
d in a Node Attribute TLV or a value of 0 is specified for the Local TE R=
outer Identifier, the Note Attribute TLV will not be used for determinin=
g ASON SCN reachability.&quot;&nbsp;</span><span style=3D'font-size:11.0=
pt;font-family:=22Calibri=22,=22sans-serif=22'><o:p></o:p></span></p></d=
iv><div><p class=3DMsoNormal><span lang=3DEN-GB style=3D'font-size:11.0p=
t;font-family:=22Calibri=22,=22sans-serif=22'>Again, the text should be e=
dited to make the distinction between transport plane and SCN clearer, I=
 suggest modifying the statement to refer to &quot;ASON reachability&quo=
t; rather than &quot;ASON SCN reachability&quot;.&nbsp; The statement wo=
uld read as follows (also correcting the spelling of the TLV):</span><sp=
an style=3D'font-size:11.0pt;font-family:=22Calibri=22,=22sans-serif=22'=
><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span lang=3DEN-G=
B style=3D'font-size:11.0pt;font-family:=22Calibri=22,=22sans-serif=22'>=
&quot;If it is not included in a Node Attribute TLV or a value of 0 is s=
pecified for the Local TE Router Identifier, the Node Attribute TLV will=
 not be used for determining ASON reachability.&quot;</span><span style=3D=
'font-size:11.0pt;font-family:=22Calibri=22,=22sans-serif=22'><o:p></o:p=
></span></p></div><div><p class=3DMsoNormal><span lang=3DEN-GB style=3D'=
font-size:10.5pt;font-family:Consolas'>&nbsp;</span><span style=3D'font-=
size:10.5pt;font-family:Consolas'><o:p></o:p></span></p></div><div><p cl=
ass=3DMsoNormal><span lang=3DEN-GB style=3D'font-size:10.5pt;font-family=
:Consolas'>Stephen Shew</span><span style=3D'font-size:10.5pt;font-famil=
y:Consolas'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span l=
ang=3DEN-GB style=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;</span=
><span style=3D'font-size:10.5pt;font-family:Consolas'><o:p></o:p></span=
></p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.5pt;fon=
t-family:Consolas'>-----Original Message-----<o:p></o:p></span></p></div=
><div><p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:C=
onsolas'>From:<span class=3Dapple-converted-space>&nbsp;</span><a href=3D=
=22mailto:ietf-announce-bounces=40ietf.org=22>ietf-announce-bounces=40ie=
tf.org</a><span class=3Dapple-converted-space>&nbsp;</span>=5B<a href=3D=
=22mailto:ietf-announce-bounces=40ietf.org=22>mailto:ietf-announce-bounc=
es=40ietf.org</a>=5D On Behalf Of The IESG<o:p></o:p></span></p></div><d=
iv><p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:Cons=
olas'>Sent: Friday, July 20, 2012 11:19 AM<o:p></o:p></span></p></div><d=
iv><p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:Cons=
olas'>To: IETF-Announce<o:p></o:p></span></p></div><div><p class=3DMsoNo=
rmal><span style=3D'font-size:10.5pt;font-family:Consolas'>Cc:<span clas=
s=3Dapple-converted-space>&nbsp;</span><a href=3D=22mailto:ccamp=40ietf.=
org=22>ccamp=40ietf.org</a><o:p></o:p></span></p></div><div><p class=3DM=
soNormal><span style=3D'font-size:10.5pt;font-family:Consolas'>Subject: L=
ast Call: &lt;draft-ietf-ccamp-rfc5787bis-05.txt&gt; (ASON Routing for O=
SPFv2 Protocols) to Proposed Standard<o:p></o:p></span></p></div><div><p=
 class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:Consolas'=
>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span style=
=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;<o:p></o:p></span></p><=
/div><div><p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-fami=
ly:Consolas'>The IESG has received a request from the Common Control and=
 Measurement Plane WG (ccamp) to consider the following document:<o:p></=
o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'font-size:=
10.5pt;font-family:Consolas'>- 'ASON Routing for OSPFv2 Protocols'<o:p><=
/o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'font-size=
:10.5pt;font-family:Consolas'>&nbsp; &lt;draft-ietf-ccamp-rfc5787bis-05.=
txt&gt; as Proposed Standard<o:p></o:p></span></p></div><div><p class=3D=
MsoNormal><span style=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;<o=
:p></o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'font-=
size:10.5pt;font-family:Consolas'>The IESG plans to make a decision in t=
he next few weeks, and solicits final comments on this action. Please se=
nd substantive comments to the<span class=3Dapple-converted-space>&nbsp;=
</span><a href=3D=22mailto:ietf=40ietf.org=22>ietf=40ietf.org</a><span c=
lass=3Dapple-converted-space>&nbsp;</span>mailing lists by 2012-08-17. E=
xceptionally, comments may be sent to<span class=3Dapple-converted-space=
>&nbsp;</span><a href=3D=22mailto:iesg=40ietf.org=22>iesg=40ietf.org</a>=
<span class=3Dapple-converted-space>&nbsp;</span>instead. In either case=
, please retain the beginning of the Subject line to allow automated sor=
ting. This is a four- week last call period because it spans the IETF-84=
 meeting.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span sty=
le=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;<o:p></o:p></span></p=
></div><div><p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-fa=
mily:Consolas'>Abstract<o:p></o:p></span></p></div><div><p class=3DMsoNo=
rmal><span style=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;<o:p></=
o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'font-size:=
10.5pt;font-family:Consolas'>&nbsp;&nbsp; The ITU-T has defined an archi=
tecture and requirements for operating<o:p></o:p></span></p></div><div><=
p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:Consolas=
'>&nbsp;&nbsp; an Automatically Switched Optical Network (ASON).<o:p></o=
:p></span></p></div><div><p class=3DMsoNormal><span style=3D'font-size:1=
0.5pt;font-family:Consolas'>&nbsp;<o:p></o:p></span></p></div><div><p cl=
ass=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:Consolas'>&n=
bsp;&nbsp; The Generalized Multiprotocol Label Switching (GMPLS) protoco=
l suite<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span style=
=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;&nbsp; is designed to p=
rovide a control plane for a range of network<o:p></o:p></span></p></div=
><div><p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:C=
onsolas'>&nbsp;&nbsp; technologies including optical networks such as ti=
me division<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span s=
tyle=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;&nbsp; multiplexing=
 (TDM) networks including SONET/SDH and Optical Transport<o:p></o:p></sp=
an></p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.5pt;f=
ont-family:Consolas'>&nbsp;&nbsp; Networks (OTNs), and lambda switching o=
ptical networks.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><s=
pan style=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;<o:p></o:p></s=
pan></p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.5pt;=
font-family:Consolas'>&nbsp;&nbsp; The requirements for GMPLS routing to=
 satisfy the requirements of<o:p></o:p></span></p></div><div><p class=3D=
MsoNormal><span style=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;&n=
bsp; ASON routing, and an evaluation of existing GMPLS routing protocols=
<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'fon=
t-size:10.5pt;font-family:Consolas'>&nbsp;&nbsp; are provided in other d=
ocuments.&nbsp; This document defines extensions to<o:p></o:p></span></p=
></div><div><p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-fa=
mily:Consolas'>&nbsp;&nbsp; the OSPFv2 Link State Routing Protocol to me=
et the requirements for<o:p></o:p></span></p></div><div><p class=3DMsoNo=
rmal><span style=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;&nbsp; r=
outing in an ASON.<o:p></o:p></span></p></div><div><p class=3DMsoNormal>=
<span style=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;<o:p></o:p><=
/span></p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.5p=
t;font-family:Consolas'>&nbsp;&nbsp; Note that this work is scoped to th=
e requirements and evaluation<o:p></o:p></span></p></div><div><p class=3D=
MsoNormal><span style=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;&n=
bsp; expressed in RFC 4258 and RFC 4652 and the ITU-T Recommendations<o:=
p></o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'font-s=
ize:10.5pt;font-family:Consolas'>&nbsp;&nbsp; current when those documen=
ts were written.&nbsp; Future extensions of<o:p></o:p></span></p></div><=
div><p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:Con=
solas'>&nbsp;&nbsp; revisions of this work may be necessary if the ITU-T=
 Recommendations<o:p></o:p></span></p></div><div><p class=3DMsoNormal><s=
pan style=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;&nbsp; are rev=
ised or if new requirements are introduced into a revision of<o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.5=
pt;font-family:Consolas'>&nbsp;&nbsp; RFC 4258. This document obsoletes R=
FC 5787 and updates RFC 5786.<o:p></o:p></span></p></div><div><p class=3D=
MsoNormal><span style=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;<o=
:p></o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'font-=
size:10.5pt;font-family:Consolas'>&nbsp;<o:p></o:p></span></p></div><div=
><p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:Consol=
as'>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span st=
yle=3D'font-size:10.5pt;font-family:Consolas'>The file can be obtained v=
ia<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'f=
ont-size:10.5pt;font-family:Consolas'><a href=3D=22http://datatracker.ie=
tf.org/doc/draft-ietf-ccamp-rfc5787bis/=22>http://datatracker.ietf.org/d=
oc/draft-ietf-ccamp-rfc5787bis/</a><o:p></o:p></span></p></div><div><p c=
lass=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:Consolas'>&=
nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span style=3D=
'font-size:10.5pt;font-family:Consolas'>IESG discussion can be tracked v=
ia<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'f=
ont-size:10.5pt;font-family:Consolas'><a href=3D=22http://datatracker.ie=
tf.org/doc/draft-ietf-ccamp-rfc5787bis/ballot/=22>http://datatracker.iet=
f.org/doc/draft-ietf-ccamp-rfc5787bis/ballot/</a><o:p></o:p></span></p><=
/div><div><p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-fami=
ly:Consolas'>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal=
><span style=3D'font-size:10.5pt;font-family:Consolas'>No IPR declaratio=
ns have been submitted directly on this I-D.<o:p></o:p></span></p></div>=
<div><p class=3DMsoNormal><span style=3D'font-size:11.0pt;color:=231F497=
D'>&nbsp;</span><span style=3D'font-size:11.0pt;font-family:=22Calibri=22=
,=22sans-serif=22'><o:p></o:p></span></p></div><div><p class=3DMsoNormal=
><span style=3D'font-size:11.0pt;color:=231F497D'>&nbsp;</span><span sty=
le=3D'font-size:11.0pt;font-family:=22Calibri=22,=22sans-serif=22'><o:p>=
</o:p></span></p></div><div><p class=3DMsoNormal><b><span style=3D'font-=
size:7.5pt;font-family:=22Arial=22,=22sans-serif=22;color:=231F497D'>Ste=
phen Shew</span></b><span style=3D'font-size:7.5pt;font-family:=22Arial=22=
,=22sans-serif=22;color:=231F497D'>&nbsp;</span><span style=3D'font-size=
:7.5pt;font-family:=22Arial=22,=22sans-serif=22;color:red'>=7C</span><sp=
an class=3Dapple-converted-space><span style=3D'font-size:7.5pt;font-fam=
ily:=22Arial=22,=22sans-serif=22;color:=231F497D'>&nbsp;</span></span><s=
pan style=3D'font-size:7.5pt;font-family:=22Arial=22,=22sans-serif=22;co=
lor:gray'>Director, Standards</span><span style=3D'font-size:7.5pt;font-=
family:=22Arial=22,=22sans-serif=22;color:=231F497D'><br></span><u><span=
 style=3D'font-size:7.5pt;font-family:=22Arial=22,=22sans-serif=22;color=
:blue'><a href=3D=22mailto:jdoe=40ciena.com=22>sshew=40ciena.com</a></sp=
an></u><span class=3Dapple-converted-space><span style=3D'font-size:7.5p=
t;font-family:=22Arial=22,=22sans-serif=22;color:=231F497D'>&nbsp;</span=
></span><span style=3D'font-size:7.5pt;font-family:=22Arial=22,=22sans-s=
erif=22;color:red'>=7C</span><span class=3Dapple-converted-space><span s=
tyle=3D'font-size:7.5pt;font-family:=22Arial=22,=22sans-serif=22;color:p=
urple'>&nbsp;</span></span><span style=3D'font-size:7.5pt;font-family:=22=
Arial=22,=22sans-serif=22;color:gray'>3500 Carling Ave.<span class=3Dapp=
le-converted-space>&nbsp;</span></span><span style=3D'font-size:7.5pt;fo=
nt-family:=22Arial=22,=22sans-serif=22;color:red'>=7C</span><span style=3D=
'font-size:7.5pt;font-family:=22Arial=22,=22sans-serif=22;color:purple'>=
&nbsp;</span><span style=3D'font-size:7.5pt;font-family:=22Arial=22,=22s=
ans-serif=22;color:gray'>Ottawa CANADA K2H 8E9<br>Direct +1.613.670.3211=
</span><span style=3D'font-size:11.0pt;font-family:=22Calibri=22,=22sans=
-serif=22'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span s=
tyle=3D'font-size:11.0pt;font-family:=22Calibri=22,=22sans-serif=22'>&nb=
sp;<o:p></o:p></span></p></div></div></div><p class=3DMsoNormal><o:p>&nb=
sp;</o:p></p></div></div></body></html>
----=_NextPart_EE_123439225.571206488--

----=_NextPart_EE_123439318.571538808
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCTAHBgUrDgMCGjCABgkqhkiG9w0BBwEAAKCCCtEwggNc
MIICRKADAgECAgRJ/MqZMA0GCSqGSIb3DQEBBQUAMB0xCzAJBgNVBAYTAlVTMQ4wDAYDVQQK
EwVDSUVOQTAeFw0xMDEyMjIxNDI2MjBaFw0xMzEyMjIxNDU2MjBaMEIxCzAJBgNVBAYTAlVT
MQ4wDAYDVQQKEwVDSUVOQTEMMAoGA1UECxMDTUVOMRUwEwYDVQQDEwxTdGVwaGVuIFNoZXcw
gZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAN5zh4m8P0WK63T6VIp8A5/izsYOYd+FSOXP
Nj2J097OxVhBieX+61i3ldwDx6snKIkEZ91IhqOSj6bpruqG2YmG43iUekhTRkeicTN+i8GW
ekIHtYLYb0LV4S9GtwZXKYvO6xhWN78Ypxe1d0cMesuZjJbNzp/ww+RreLSUKwElAgMBAAGj
ggEBMIH+MAsGA1UdDwQEAwIHgDArBgNVHRAEJDAigA8yMDEwMTIyMjE0MjYyMFqBDzIwMTMw
MTI3MTg1NjIwWjAaBgNVHREEEzARgQ9zc2hld0BjaWVuYS5jb20wQAYDVR0fBDkwNzA1oDOg
MaQvMC0xCzAJBgNVBAYTAlVTMQ4wDAYDVQQKEwVDSUVOQTEOMAwGA1UEAxMFQ1JMMzQwHwYD
VR0jBBgwFoAUZ7dnIAQq11eoyM9ti0Zd5UPvgZkwHQYDVR0OBBYEFAfpgS6323uEimAGHKyH
W3gJhFy4MAkGA1UdEwQCMAAwGQYJKoZIhvZ9B0EABAwwChsEVjcuMQMCBLAwDQYJKoZIhvcN
AQEFBQADggEBADBx/Zk7mjBAwXpljedXyjn++Et//JdwevEwdNrHgoVwI84uZZkd0NHwR5UF
eHhgE83ElR0GhdJk/VeDEr7f+FHUA0W6PnKHrj6XtiA7vEyTMSTEA9cQryy/T1+Vo+gvJvqY
kt1wuVSGReMuG2kHBi289mnwarFaVK/LyI8MO8my+A5t0HIh2yB89WelaUH8U/cCLMxzpaVC
nxVNZ0C8Br65L/OGgLDkdxFg9/ZgtdUs1D38uiuENr9QKnG6nU8woHLqV4EFaQCJU7/YUF8q
ei6HKqCxTcCjh4CXKQG53EzNiqaS3+CJSHfl2r8X6IpLeM13C1P6V8wKP65+NaBJaC0wggOy
MIICmqADAgECAgRJ/MqaMA0GCSqGSIb3DQEBBQUAMB0xCzAJBgNVBAYTAlVTMQ4wDAYDVQQK
EwVDSUVOQTAeFw0xMDEyMjIxNDI2MjBaFw0xMzEyMjIxNDU2MjBaMEIxCzAJBgNVBAYTAlVT
MQ4wDAYDVQQKEwVDSUVOQTEMMAoGA1UECxMDTUVOMRUwEwYDVQQDEwxTdGVwaGVuIFNoZXcw
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQD6KTyw5LSy03+a+Y+oXSV2x2uU+Ule
Zem4dJq4H/Kdtw1tlhJhdIzoQBxI6RpHO33WeVLNkBzPn5ev0aZwlTh4l2u82VKbFQ0ln5l1
2nWQ7vdSLmuZhZVFXUvnPDM/k5z1ivRASTUcbnv6J7oVd8BPsY7HzioR7A1J7HRftXxWnqBt
2pebin/Gm0RAxZfxkwmcKT9EzVMA3L5zaRIt1t6aNYIY2ZbvqLijsH3ez9f6aRw2r1W37df0
cQBXoBXjrpVkR0cZ1i6gmJA3d2TVG33o0jYOFtz66xRtW5VcpMvI1OpgLHnND61vHO/EXGBt
poqFvlBO9meS/cTo5qsnEu6pAgMBAAGjgdQwgdEwCwYDVR0PBAQDAgUgMBoGA1UdEQQTMBGB
D3NzaGV3QGNpZW5hLmNvbTBABgNVHR8EOTA3MDWgM6AxpC8wLTELMAkGA1UEBhMCVVMxDjAM
BgNVBAoTBUNJRU5BMQ4wDAYDVQQDEwVDUkwzNDAfBgNVHSMEGDAWgBRnt2cgBCrXV6jIz22L
Rl3lQ++BmTAdBgNVHQ4EFgQUl/vMBFCGOJRV+ReANQyAyr0m7KEwCQYDVR0TBAIwADAZBgkq
hkiG9n0HQQAEDDAKGwRWNy4xAwIEsDANBgkqhkiG9w0BAQUFAAOCAQEAuZ0uBD8GJ7Pfh4yQ
aP4M9VUO2SqxbxwCJBfP0y4cFo1o66ozRzgzE/4g1oxTg2TAY3EOueQIVNgKapDVh4C09eWd
k06TFalKT538VZiAOCehNfmS52hdeak9jFZBZ2JuJrGPCri8i2Fx7lNBm5zuUILczdjmOhy+
xoVPk7ph52xS41JzP7O1N0NDm6hwxczbCuEKW/suwhSdHwYOp0BZlVFHrGYAGGqhXFAlaXmv
EKlLtHnNBHUA6O+Hq9KaVYfapIz4qmMfVjtUdn7iaF0WhatNg+nki6P35ITD20IlHCuuWM6j
Xsj7eka51+sRhRsPyj44SVi/3nTa1QcdxwM2OzCCA7cwggKfoAMCAQICBDjssoAwDQYJKoZI
hvcNAQEFBQAwHTELMAkGA1UEBhMCVVMxDjAMBgNVBAoTBUNJRU5BMB4XDTAwMDQwNjE1MjEz
M1oXDTIwMDQwNjE1NTEzM1owHTELMAkGA1UEBhMCVVMxDjAMBgNVBAoTBUNJRU5BMIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwKjVicadm6sz+cjh1w+QvSxt5dETeTEDBI1c
ytw0Ywo/NX4VqzhqUOuTF1uRNsETYWhdKwFEvwMt1CeWYGrYJMDqPYX9SwGxbXBYaIP0Jnaq
oHjtJYzkjgTracdal9OpuHfmdu35XIeUNNtYU1dS2uGnc8L7i9t1qZCLqxo8hbICimmk1NUu
8KTBwdA1G4STZC4SHApOomkomkKhI2hnhhoRPR+1ZQbAT315BWMb9g48cHsIr8ay0KPnkqA6
qjQ3ot0GtVxYyNQAaqzOsrwF7J32PoiUb8fHRAoMtplzrg9Sxl4Z26AutTfJlq2L1Xr30wP9
E3aSPmIwnxMkyhFqRQIDAQABo4H+MIH7MBEGCWCGSAGG+EIBAQQEAwIABzA/BgNVHR8EODA2
MDSgMqAwpC4wLDELMAkGA1UEBhMCVVMxDjAMBgNVBAoTBUNJRU5BMQ0wCwYDVQQDEwRDUkwx
MCsGA1UdEAQkMCKADzIwMDAwNDA2MTUyMTMzWoEPMjAyMDA0MDYxNTUxMzNaMAsGA1UdDwQE
AwIBBjAfBgNVHSMEGDAWgBRnt2cgBCrXV6jIz22LRl3lQ++BmTAdBgNVHQ4EFgQUZ7dnIAQq
11eoyM9ti0Zd5UPvgZkwDAYDVR0TBAUwAwEB/zAdBgkqhkiG9n0HQQAEEDAOGwhWNS4wOjQu
MAMCBJAwDQYJKoZIhvcNAQEFBQADggEBABjskl+ydfhu9o7KOCFRsaCgLmW7GAZUmJCO7XmI
BKZeWXCa7L7eCa2LAQhIHWWkRicqVF75VJq374JTcJP/kjyNqjrGZpHdyL8R2e6rmk4nl9rV
cZgRVURy5+yVotknIb7703TfslCEq4tvFmaFF5iKWHwCjqoEh+cOfb8OYMZoOjdStn/NhgRU
u7Q3QLIJEJAVt4+8B2eQiM45qh8e+L1VEMFN0Y11E+Aftn3MB+Qz4TSmm+hOBpbenLdCSx0Z
Kxw08Befvcg7v1WyntQ8Q2/B9cHxwzJg6TSwKeXXj+iBg9HHSWtFq1ZYVFMJL2BTBi4XGFz1
AHCYCdYaccbVorgxggI9MIICOQIBATAlMB0xCzAJBgNVBAYTAlVTMQ4wDAYDVQQKEwVDSUVO
QQIESfzKmTAHBgUrDgMCGqCCAXIwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG
9w0BCQUxDxcNMTIwODIyMTYzNDM5WjAjBgkqhkiG9w0BCQQxFgQUgKGE29TAfy6cGHiK96tb
6FGGfFMwggERBgkqhkiG9w0BCQ8xggECMIH/MAcGBSsOAwIaMAoGCCqGSIb3DQICMAoGCCqG
SIb3DQIEMAoGCCqGSIb3DQIFMAsGCWCGSAFlAwQCATALBglghkgBZQMEAgIwCwYJYIZIAWUD
BAIDMA4GCSqGSIb2fQdCAwIBQDAOBgkqhkiG9n0HQgMCASgwDwYJKoZIhvZ9B0IKAgIAgDAR
BgsrBgEEAYE8BwEBAgICAIAwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgEoMAcGBSsO
AwIHMAoGCCqGSIb3DQMHMA8GCWCGSAFlAwQBAgICAIAwDwYJYIZIAWUDBAEWAgIAwDAPBglg
hkgBZQMEASoCAgEAMAsGCSqGSIb3DQEBAQSBgL8ItR1B00U3iE8BaAUuZmqwv9MOI7+8/oP0
1MV997ihYiAyYdsqI+m0ckEISBRTHWKJSla8UGF2Ge4TM/Zr1hl/C2PnqI1E+ZvlnI//oZLv
NCHOjeXpVZR0k32DQcTDU2RjLMFc5b+EoSs3HOoRhrw4eeUYew6SnaqY2kcrCYtAAAAAAAAA

----=_NextPart_EE_123439318.571538808--

From denis.pinkas@bull.net  Thu Aug 23 11:02:22 2012
Return-Path: <denis.pinkas@bull.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D055E21F861F for <ietf@ietfa.amsl.com>; Thu, 23 Aug 2012 11:02:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.151
X-Spam-Level: 
X-Spam-Status: No, score=-2.151 tagged_above=-999 required=5 tests=[AWL=0.097,  BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 a3h8VigxuKQ8 for <ietf@ietfa.amsl.com>; Thu, 23 Aug 2012 11:02:22 -0700 (PDT)
Received: from odin2.bull.net (odin2.bull.net [129.184.85.11]) by ietfa.amsl.com (Postfix) with ESMTP id 7D6CF21F860E for <ietf@ietf.org>; Thu, 23 Aug 2012 11:02:20 -0700 (PDT)
Received: from MSGC-003.bull.fr (MSGC-003.frcl.bull.fr [129.184.87.131]) by odin2.bull.net (Bull S.A.) with ESMTP id 617FA1801A for <ietf@ietf.org>; Thu, 23 Aug 2012 20:02:19 +0200 (CEST)
In-Reply-To: <20120822150543.16802.27813.idtracker@ietfa.amsl.com>
References: <20120822150543.16802.27813.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
MIME-Version: 1.0
Subject: RE: [pkix] Last Call: <draft-ietf-pkix-rfc5280-clarifications-08.txt>	(Updates to the Internet X.509 Public Key Infrastructure	Certificate and Certificate Revocation List (CRL) Profile) to	Proposed Standard
X-KeepSent: 998F9088:0427EC5F-C1257A63:0060E0A6; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2 August 10, 2010
From: denis.pinkas@bull.net
Message-ID: <OF998F9088.0427EC5F-ONC1257A63.0060E0A6-C1257A63.006316C3@bull.net>
Date: Thu, 23 Aug 2012 20:02:18 +0200
X-MIMETrack: Serialize by Router on MSGC-003/SRV/BULL(Release 8.5.2FP1|November 29, 2010) at 23/08/2012 20:02:19, Serialize complete at 23/08/2012 20:02:19
Content-Type: multipart/alternative; boundary="=_alternative 00630FBBC1257A63_="
X-Mailman-Approved-At: Thu, 23 Aug 2012 13:43:18 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Aug 2012 18:02:23 -0000

Message en plusieurs parties au format MIME
--=_alternative 00630FBBC1257A63_=
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

A discussion has just started yesterday on the PKIX mailing list about an=20
"Errata in section 5.3 from RFC 5280".

At this time it can clearly be seen that RFC 5280 is NOT compatible with=20
X.509 for the processing of=20
crlEntryExtensions, whereas RFC 5280 is supposed to be a *profile* of=20
X.509.

For that reason, I ask the IESG to suspend its decision until the issue=20
about crlEntryExtensions is clarified=20
one way or another, since this point now needs to be clarified and will=20
impact a document whose goal is precisely=20
to clarify RFC 5280.

Denis



De :    The IESG <iesg-secretary@ietf.org>
A :     IETF-Announce <ietf-announce@ietf.org>
Cc :    pkix@ietf.org
Date :  22/08/2012 17:05
Objet : [pkix] Last Call: <draft-ietf-pkix-rfc5280-clarifications-08.txt>=20
(Updates        to the Internet X.509 Public Key Infrastructure=20
Certificate and Certificate Revocation List (CRL) Profile) to   Proposed=20
Standard
Envoy=E9 par :    pkix-bounces@ietf.org


The IESG has received a request from the Public-Key Infrastructure
(X.509) WG (pkix) to consider the following document:
- 'Updates to the Internet X.509 Public Key Infrastructure Certificate
   and Certificate Revocation List (CRL) Profile'
  <draft-ietf-pkix-rfc5280-clarifications-08.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2012-09-05. 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 updates RFC 5280, the Internet X.509 Public Key
   Infrastructure Certificate and Certificate Revocation List (CRL)
   Profile.  This document changes the set of acceptable encoding
   methods for the explicitText field of the user notice policy
   qualifier and clarifies the rules for converting internationalized
   domain name labels to ASCII.  This document also provides some
   clarifications on the use of self-signed certificates, trust anchors,
   and some updated security considerations.





The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-pkix-rfc5280-clarifications/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-pkix-rfc5280-clarifications/ball=
ot/



No IPR declarations have been submitted directly on this I-D.


=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
pkix mailing list
pkix@ietf.org
https://www.ietf.org/mailman/listinfo/pkix


--=_alternative 00630FBBC1257A63_=
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<font size=3D2 face=3D"Arial">A discussion has just started yesterday on the
PKIX mailing list about an &quot;Errata in section 5.3 from RFC 5280&quot;.=
</font>
<br>
<br><font size=3D2 face=3D"Arial">At this time it can clearly be seen that
RFC 5280 is NOT compatible with X.509 for the processing of </font>
<br><tt><font size=3D2>crlEntryExtensions</font></tt><font size=3D2 face=3D=
"Arial">,
whereas RFC 5280 is supposed to be a *profile* of X.509.</font>
<br>
<br><font size=3D2 face=3D"Arial">For that reason, I ask the IESG to suspend
its decision until the issue about </font><tt><font size=3D2>crlEntryExtens=
ions</font></tt><font size=3D2 face=3D"Arial">
is clarified <br>
one way or another, since this point now needs to be clarified and will
impact a document whose goal is precisely </font>
<br><font size=3D2 face=3D"Arial">to clarify RFC 5280.</font>
<br>
<br><font size=3D2 face=3D"Arial">Denis</font>
<br>
<br>
<br>
<br><font size=3D1 color=3D#5f5f5f face=3D"sans-serif">De : &nbsp; &nbsp; &=
nbsp;
&nbsp;</font><font size=3D1 face=3D"sans-serif">The IESG &lt;iesg-secretary=
@ietf.org&gt;</font>
<br><font size=3D1 color=3D#5f5f5f face=3D"sans-serif">A : &nbsp; &nbsp; &n=
bsp;
&nbsp;</font><font size=3D1 face=3D"sans-serif">IETF-Announce &lt;ietf-anno=
unce@ietf.org&gt;</font>
<br><font size=3D1 color=3D#5f5f5f face=3D"sans-serif">Cc&nbsp;: &nbsp; &nb=
sp;
&nbsp; &nbsp;</font><font size=3D1 face=3D"sans-serif">pkix@ietf.org</font>
<br><font size=3D1 color=3D#5f5f5f face=3D"sans-serif">Date : &nbsp; &nbsp;=
 &nbsp;
&nbsp;</font><font size=3D1 face=3D"sans-serif">22/08/2012 17:05</font>
<br><font size=3D1 color=3D#5f5f5f face=3D"sans-serif">Objet : &nbsp; &nbsp;
&nbsp; &nbsp;</font><font size=3D1 face=3D"sans-serif">[pkix] Last
Call: &lt;draft-ietf-pkix-rfc5280-clarifications-08.txt&gt; &nbsp; &nbsp;
&nbsp; &nbsp;(Updates &nbsp; &nbsp; &nbsp; &nbsp;to the
Internet X.509 Public Key Infrastructure &nbsp; &nbsp; &nbsp; &nbsp;Certifi=
cate
and &nbsp; &nbsp; &nbsp; &nbsp;Certificate Revocation List (CRL)
Profile) to &nbsp; &nbsp; &nbsp; &nbsp;Proposed Standard</font>
<br><font size=3D1 color=3D#5f5f5f face=3D"sans-serif">Envoy=E9 par : &nbsp=
; &nbsp;
&nbsp; &nbsp;</font><font size=3D1 face=3D"sans-serif">pkix-bounces@ietf.or=
g</font>
<br>
<hr noshade>
<br>
<br><tt><font size=3D2>The IESG has received a request from the Public-Key
Infrastructure<br>
(X.509) WG (pkix) to consider the following document:<br>
- 'Updates to the Internet X.509 Public Key Infrastructure Certificate<br>
 &nbsp; and Certificate Revocation List (CRL) Profile'<br>
 &nbsp;&lt;draft-ietf-pkix-rfc5280-clarifications-08.txt&gt; as Proposed
Standard<br>
<br>
The IESG plans to make a decision in the next few weeks, and solicits<br>
final comments on this action. Please send substantive comments to the<br>
ietf@ietf.org mailing lists by 2012-09-05. Exceptionally, comments may
be<br>
sent to iesg@ietf.org instead. In either case, please retain the<br>
beginning of the Subject line to allow automated sorting.<br>
<br>
Abstract<br>
<br>
<br>
 &nbsp; This document updates RFC 5280, the Internet X.509 Public Key<br>
 &nbsp; Infrastructure Certificate and Certificate Revocation List (CRL)<br>
 &nbsp; Profile. &nbsp;This document changes the set of acceptable encoding=
<br>
 &nbsp; methods for the explicitText field of the user notice policy<br>
 &nbsp; qualifier and clarifies the rules for converting internationalized<=
br>
 &nbsp; domain name labels to ASCII. &nbsp;This document also provides
some<br>
 &nbsp; clarifications on the use of self-signed certificates, trust anchor=
s,<br>
 &nbsp; and some updated security considerations.<br>
<br>
<br>
<br>
<br>
<br>
The file can be obtained via<br>
</font></tt><a href=3D"http://datatracker.ietf.org/doc/draft-ietf-pkix-rfc5=
280-clarifications/"><tt><font size=3D2>http://datatracker.ietf.org/doc/dra=
ft-ietf-pkix-rfc5280-clarifications/</font></tt></a><tt><font size=3D2><br>
<br>
IESG discussion can be tracked via<br>
</font></tt><a href=3D"http://datatracker.ietf.org/doc/draft-ietf-pkix-rfc5=
280-clarifications/ballot/"><tt><font size=3D2>http://datatracker.ietf.org/=
doc/draft-ietf-pkix-rfc5280-clarifications/ballot/</font></tt></a><tt><font=
 size=3D2><br>
<br>
<br>
No IPR declarations have been submitted directly on this I-D.<br>
<br>
<br>
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br>
pkix mailing list<br>
pkix@ietf.org<br>
</font></tt><a href=3Dhttps://www.ietf.org/mailman/listinfo/pkix><tt><font =
size=3D2>https://www.ietf.org/mailman/listinfo/pkix</font></tt></a><tt><fon=
t size=3D2><br>
</font></tt>
<br>
--=_alternative 00630FBBC1257A63_=--

From narten@us.ibm.com  Thu Aug 23 21:53:10 2012
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0258221F84FB for <ietf@ietfa.amsl.com>; Thu, 23 Aug 2012 21:53:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.147
X-Spam-Level: 
X-Spam-Status: No, score=-109.147 tagged_above=-999 required=5 tests=[AWL=-0.962, BAYES_40=-0.185, 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 VhFbzg9FfKpu for <ietf@ietfa.amsl.com>; Thu, 23 Aug 2012 21:53:09 -0700 (PDT)
Received: from e8.ny.us.ibm.com (e8.ny.us.ibm.com [32.97.182.138]) by ietfa.amsl.com (Postfix) with ESMTP id 3B44621F84F2 for <ietf@ietf.org>; Thu, 23 Aug 2012 21:53:08 -0700 (PDT)
Received: from /spool/local by e8.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 24 Aug 2012 00:53:08 -0400
Received: from d01dlp02.pok.ibm.com (9.56.250.167) by e8.ny.us.ibm.com (192.168.1.108) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 24 Aug 2012 00:53:06 -0400
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 549FE6E8039 for <ietf@ietf.org>; Fri, 24 Aug 2012 00:53:05 -0400 (EDT)
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q7O4r4La174370 for <ietf@ietf.org>; Fri, 24 Aug 2012 00:53:05 -0400
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q7O4r4Y7027998 for <ietf@ietf.org>; Thu, 23 Aug 2012 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q7O4r3H8027975 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 23 Aug 2012 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q7O4r3Cb032766 for <ietf@ietf.org>; Fri, 24 Aug 2012 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q7O4r2iY032729 for ietf@ietf.org; Fri, 24 Aug 2012 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201208240453.q7O4r2iY032729@rotala.raleigh.ibm.com>
Date: Fri, 24 Aug 2012 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-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12082404-9360-0000-0000-000009C94BD3
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Aug 2012 04:53:10 -0000

Total of 75 messages in the last 7 days.
 
script run at: Fri Aug 24 00:53:02 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  5.33% |    4 | 13.12% |   101230 | adrian@olddog.co.uk
  2.67% |    2 | 12.89% |    99449 | sshew@ciena.com
  9.33% |    7 |  5.80% |    44722 | barryleiba@computer.org
  8.00% |    6 |  6.62% |    51081 | abdussalambaryun@gmail.com
  6.67% |    5 |  4.05% |    31209 | john-ietf@jck.com
  5.33% |    4 |  3.86% |    29778 | bob.hinden@gmail.com
  5.33% |    4 |  3.80% |    29300 | sm+ietf@elandsys.com
  5.33% |    4 |  3.60% |    27781 | housley@vigilsec.com
  1.33% |    1 |  6.66% |    51385 | acee.lindem@ericsson.com
  4.00% |    3 |  3.80% |    29277 | mstjohns@comcast.net
  1.33% |    1 |  4.45% |    34342 | lyong@ciena.com
  2.67% |    2 |  1.89% |    14548 | ole@cisco.com
  2.67% |    2 |  1.60% |    12372 | joelja@bogus.com
  2.67% |    2 |  1.56% |    12006 | robert@raszuk.net
  2.67% |    2 |  1.55% |    11993 | dworley@avaya.com
  2.67% |    2 |  1.49% |    11502 | john@jck.com
  2.67% |    2 |  1.32% |    10193 | randy@psg.com
  1.33% |    1 |  2.47% |    19087 | lberger@labn.net
  1.33% |    1 |  1.71% |    13196 | ron.even.tlv@gmail.com
  1.33% |    1 |  1.63% |    12575 | denis.pinkas@bull.net
  1.33% |    1 |  1.59% |    12247 | david.black@emc.com
  1.33% |    1 |  1.35% |    10386 | narten@us.ibm.com
  1.33% |    1 |  0.93% |     7156 | d3e3e3@gmail.com
  1.33% |    1 |  0.89% |     6859 | jonne.soininen@renesasmobile.com
  1.33% |    1 |  0.87% |     6716 | margaretw42@gmail.com
  1.33% |    1 |  0.83% |     6403 | glenzorn@gmail.com
  1.33% |    1 |  0.83% |     6374 | lear@cisco.com
  1.33% |    1 |  0.82% |     6305 | dwm@xpasc.com
  1.33% |    1 |  0.81% |     6249 | johnl@taugh.com
  1.33% |    1 |  0.81% |     6242 | dcrocker@gmail.com
  1.33% |    1 |  0.78% |     6021 | rpelletier@isoc.org
  1.33% |    1 |  0.77% |     5952 | mcr+ietf@sandelman.ca
  1.33% |    1 |  0.75% |     5808 | sm@resistor.net
  1.33% |    1 |  0.75% |     5803 | touch@isi.edu
  1.33% |    1 |  0.72% |     5528 | melinda.shore@gmail.com
  1.33% |    1 |  0.68% |     5226 | michal@krsek.cz
  1.33% |    1 |  0.67% |     5184 | mcr@sandelman.ca
  1.33% |    1 |  0.66% |     5127 | dhc@dcrocker.net
  1.33% |    1 |  0.63% |     4840 | wjhns1@hardakers.net
--------+------+--------+----------+------------------------
100.00% |   75 |100.00% |   771452 | Total


From abdussalambaryun@gmail.com  Fri Aug 24 04:07:29 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D16D421F86EA; Fri, 24 Aug 2012 04:07:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.491
X-Spam-Level: 
X-Spam-Status: No, score=-3.491 tagged_above=-999 required=5 tests=[AWL=0.107,  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 vnGGVDe13Htg; Fri, 24 Aug 2012 04:07:28 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7D5AF21F85AE; Fri, 24 Aug 2012 04:07:28 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so2119712vbb.31 for <multiple recipients>; Fri, 24 Aug 2012 04:07:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5TA01upRZG5KJ2CriB4D8byjE5YoFYoN/iPxqy+CnaI=; b=x+KgHS/8WxxyCO7G5ezvAlb3Km4Efz99/EPp6eCL8YwcbeROBS5kT+LnIS21WcMLtS +ezHcU9kCj5qehNJ6tlMhOiuVTLxCuYxpW0iSO/dw7JHTHa7Xs6afsZDPgI2wN/R5PKU iwNX7vZjXN/9SOQKXsAYN9LhtWUJdUF7LMLVBYf14Cb//XdWVGSxNp/l8HQPT0oGcy/x nIn1uanPD1MgFu2hRycnCuMEvqbM8y16iwvxefRjz6jNeJTDgoxkmkkVsQDxbhJDX2fJ EGyuWuARDKG1AnR08+mJRa5/45CRBdkPQCN1s0Vg/tdgvZZyt8CKVOQ0UH5ffvDrrxg9 Q6ig==
MIME-Version: 1.0
Received: by 10.52.240.230 with SMTP id wd6mr3644826vdc.20.1345806447741; Fri, 24 Aug 2012 04:07:27 -0700 (PDT)
Received: by 10.220.55.9 with HTTP; Fri, 24 Aug 2012 04:07:27 -0700 (PDT)
In-Reply-To: <170101cd8113$61658fa0$2430aee0$@olddog.co.uk>
References: <170101cd8113$61658fa0$2430aee0$@olddog.co.uk>
Date: Fri, 24 Aug 2012 12:07:27 +0100
Message-ID: <CADnDZ89YhsO9ePB0GdTWFFx-kr9Dn1RuE1z=JkEfez_OPmJVYA@mail.gmail.com>
Subject: Re: Your comments on draft-ietf-manet-olsrv2-15.txt
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: adrian@olddog.co.uk
Content-Type: multipart/alternative; boundary=20cf307d007241094104c800fb82
Cc: iesg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Aug 2012 11:07:29 -0000

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

Hi Adrian,

Yes my comments requested by last call to be submitted to IESG for the
subject (evaluation purpose) have been ended. However, if I get any
request/receive/read any new issue in IETF, I may comment again to IETF
discuss list. For the OLSRv2 in general comments will never end as long as
there are users and as long the internet mission is development/progress,
but to IESG I have ended the comments (one additional to ietf) which I
mentioned the *end* in my last comment to IESG. They were separate to focus
each comment on separate related view.

I don't know how is the practice of IESG process or Last Call process, but
I have tried many times with the authors before, to make the document
better but they think my comments are not important (which maybe they are
right). Therefore, I don't want to give any permission to share with them,
I will leave it to IESG. If IESG agrees to share any/all comments they
received to any/all author(s), I will have no objection.

Thanking you,

Best Regards

Abdussalam Baryun (AB)
University of Glamorgan, UK
++++++++++++++++++++++
On Thu, Aug 23, 2012 at 10:40 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> Hi Abdussalam,
>
> Thank you for your review comments on draft-ietf-manet-olsrv2-15.txt
>
> I see seven separate points raised in separate emails. Can you confirm
> that this
> is the totality of your comments.
>
> I also note that the seventh email was sent to only the IESG. May I have
> your
> permission to share this email with the document authors.
>
> Thanks,
> Adrian
>
> > -----Original Message-----
> > From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of
> > Abdussalam Baryun
> > Sent: 22 August 2012 23:01
> > To: iesg@ietf.org
> > Subject: Re: Last Call: <draft-ietf-manet-olsrv2-15.txt> (The Optimized
> Link
> State
> > Routing Protocol version 2) to Proposed Standard
> >
> > Reply to your request dated 29/07/2012
> > Draft Reviewed By: Abdussalam Baryun (AB)   Dated: 22/08/2012
> >
> > Reviewer Comment AB7: Comments on text in document history [*].
> > https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2/history/
> > ++++++++++++++++++++++++++++++++++++
> >
> > A key difference between RFC3626 and OLSRv2 is the introduction of
> > support for link metrics. An individual draft
> > (draft-dearlove-olsrv2-metrics-00) was submitted in 2007, discussing
> > the design options, culminating in 2010 with
> > draft-dearlove-olsrv2-metrics-05 documenting Working Group consensus
> > on this matter. Metrics support was, then, folded into OLSRv2.
> >
> > AB> the reviewer thinks the difference is that OLSRv2 is a metric base
> > router that uses NHDP and RFC5444 packets which are general MANET
> > interface protocol and general MANET packet format respectively.
> > OLSRv2 is applicable for more scenarios and routers that are
> > constraint devices.
> >
> > This version of OLSRv2 was given a one month WGLC, so as to ensure
> > sufficient time to review the document.
> >
> > AB> my comments within the period was not considered by the authors
> > and don't see any consensus from the WG.
> >
> > There was an issue concerning the differences between the -14 and -15
> > revisions of the document, brought up by one WG member. The consensus
> > opinion from the WG is that the document should proceed, without
> > additional edits.
> >
> > AB> yes there was a new version update after my comments and
> > discussion with the authors, but still not happy with the outcome.
> >
> > Best Regards
> > AB
> > +++++++++++++++++
> > The end of my comments (the comments were 7 including this, two only
> > for the IESG and one addition for only IEFT).
> > ========================================================
> >
> > On 7/29/12, The IESG <iesg-secretary@ietf.org> wrote:
> > >
> > > The IESG has received a request from the Mobile Ad-hoc Networks WG
> > > (manet) to consider the following document:
> > > - 'The Optimized Link State Routing Protocol version 2'
> > >   <draft-ietf-manet-olsrv2-15.txt> as Proposed Standard
> > >
> > > The IESG plans to make a decision in the next few weeks, and solicits
> > > final comments on this action. Please send substantive comments to the
> > > ietf@ietf.org mailing lists by 2012-08-22. Exceptionally, comments
> may be
> > > sent to iesg@ietf.org instead. In either case, please retain the
> > > beginning of the Subject line to allow automated sorting. This last
> call
> > > period has been extended to handle the fact that it spans the IETF-84
> > > meeting.
> > >
> > > This last call is being re-initiated to include a notice that this
> document
> > > includes a normative down reference to an Informational RFC:
> > > RFC5148, "Jitter considerations in MANETs".
> > >
> > > Abstract
> > >
> > >    This specification describes version 2 of the Optimized Link State
> > >    Routing (OLSRv2) protocol for Mobile Ad hoc NETworks (MANETs).
> > >
> > > The file can be obtained via
> > > http://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2/
> > >
> > > IESG discussion can be tracked via
> > > http://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2/ballot/
> > >
> > >
> > > No IPR declarations have been submitted directly on this I-D.
> > >
>
>

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

<div>Hi Adrian,</div><div>=A0</div><div>Yes my comments requested by last c=
all to be submitted=A0to IESG for the subject (evaluation purpose)=A0have b=
een ended. However, if I get any request/receive/read any new issue in IETF=
,=A0I may comment again to IETF discuss list. For the OLSRv2 in general=A0c=
omments=A0will never end as long as there are users and=A0as long the inter=
net=A0mission is development/progress, but to IESG I have ended the=A0comme=
nts (one additional to ietf)=A0which I mentioned the *end* in my last comme=
nt to IESG. They were separate to focus each comment on separate related vi=
ew.</div>
<div>=A0</div><div>I don&#39;t know how is the practice of=A0IESG process o=
r Last Call process, but I have tried many times with the authors before, t=
o make the document better but they think my comments are not=A0important (=
which maybe they are right). Therefore, I don&#39;t want=A0to give any perm=
ission to share with them, I will leave it to IESG. If IESG=A0agrees to sha=
re=A0any/all comments they received=A0to any/all author(s),=A0I will have n=
o objection. </div>
<div>=A0</div><div>Thanking you,</div><div>=A0</div><div>Best Regards</div>=
<div>=A0</div><div>Abdussalam Baryun (AB)</div><div>University of Glamorgan=
, UK<br>++++++++++++++++++++++<br></div><div class=3D"gmail_quote">On Thu, =
Aug 23, 2012 at 10:40 AM, Adrian Farrel <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:adrian@olddog.co.uk" target=3D"_blank">adrian@olddog.co.uk</a>&gt;</sp=
an> wrote:<br>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote">Hi Abdussalam,<br>
<br>
Thank you for your review comments on draft-ietf-manet-olsrv2-15.txt<br>
<br>
I see seven separate points raised in separate emails. Can you confirm that=
 this<br>
is the totality of your comments.<br>
<br>
I also note that the seventh email was sent to only the IESG. May I have yo=
ur<br>
permission to share this email with the document authors.<br>
<br>
Thanks,<br>
Adrian<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:iesg-bounces@ietf.org">iesg-bounces@ietf.org</=
a> [mailto:<a href=3D"mailto:iesg-bounces@ietf.org">iesg-bounces@ietf.org</=
a>] On Behalf Of<br>
&gt; Abdussalam Baryun<br>
&gt; Sent: 22 August 2012 23:01<br>
&gt; To: <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a><br>
&gt; Subject: Re: Last Call: &lt;draft-ietf-manet-olsrv2-15.txt&gt; (The Op=
timized Link<br>
State<br>
&gt; Routing Protocol version 2) to Proposed Standard<br>
&gt;<br>
&gt; Reply to your request dated 29/07/2012<br>
&gt; Draft Reviewed By: Abdussalam Baryun (AB) =A0 Dated: 22/08/2012<br>
&gt;<br>
&gt; Reviewer Comment AB7: Comments on text in document history [*].<br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2/hi=
story/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-manet=
-olsrv2/history/</a><br>
&gt; ++++++++++++++++++++++++++++++++++++<br>
&gt;<br>
&gt; A key difference between RFC3626 and OLSRv2 is the introduction of<br>
&gt; support for link metrics. An individual draft<br>
&gt; (draft-dearlove-olsrv2-metrics-00) was submitted in 2007, discussing<b=
r>
&gt; the design options, culminating in 2010 with<br>
&gt; draft-dearlove-olsrv2-metrics-05 documenting Working Group consensus<b=
r>
&gt; on this matter. Metrics support was, then, folded into OLSRv2.<br>
&gt;<br>
&gt; AB&gt; the reviewer thinks the difference is that OLSRv2 is a metric b=
ase<br>
&gt; router that uses NHDP and RFC5444 packets which are general MANET<br>
&gt; interface protocol and general MANET packet format respectively.<br>
&gt; OLSRv2 is applicable for more scenarios and routers that are<br>
&gt; constraint devices.<br>
&gt;<br>
&gt; This version of OLSRv2 was given a one month WGLC, so as to ensure<br>
&gt; sufficient time to review the document.<br>
&gt;<br>
&gt; AB&gt; my comments within the period was not considered by the authors=
<br>
&gt; and don&#39;t see any consensus from the WG.<br>
&gt;<br>
&gt; There was an issue concerning the differences between the -14 and -15<=
br>
&gt; revisions of the document, brought up by one WG member. The consensus<=
br>
&gt; opinion from the WG is that the document should proceed, without<br>
&gt; additional edits.<br>
&gt;<br>
&gt; AB&gt; yes there was a new version update after my comments and<br>
&gt; discussion with the authors, but still not happy with the outcome.<br>
&gt;<br>
&gt; Best Regards<br>
&gt; AB<br>
&gt; +++++++++++++++++<br>
&gt; The end of my comments (the comments were 7 including this, two only<b=
r>
&gt; for the IESG and one addition for only IEFT).<br>
&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=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>
&gt;<br>
&gt; On 7/29/12, The IESG &lt;<a href=3D"mailto:iesg-secretary@ietf.org">ie=
sg-secretary@ietf.org</a>&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt; The IESG has received a request from the Mobile Ad-hoc Networks W=
G<br>
&gt; &gt; (manet) to consider the following document:<br>
&gt; &gt; - &#39;The Optimized Link State Routing Protocol version 2&#39;<b=
r>
&gt; &gt; =A0 &lt;draft-ietf-manet-olsrv2-15.txt&gt; as Proposed Standard<b=
r>
&gt; &gt;<br>
&gt; &gt; The IESG plans to make a decision in the next few weeks, and soli=
cits<br>
&gt; &gt; final comments on this action. Please send substantive comments t=
o the<br>
&gt; &gt; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists =
by 2012-08-22. Exceptionally, comments may be<br>
&gt; &gt; sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instea=
d. In either case, please retain the<br>
&gt; &gt; beginning of the Subject line to allow automated sorting. This la=
st call<br>
&gt; &gt; period has been extended to handle the fact that it spans the IET=
F-84<br>
&gt; &gt; meeting.<br>
&gt; &gt;<br>
&gt; &gt; This last call is being re-initiated to include a notice that thi=
s document<br>
&gt; &gt; includes a normative down reference to an Informational RFC:<br>
&gt; &gt; RFC5148, &quot;Jitter considerations in MANETs&quot;.<br>
&gt; &gt;<br>
&gt; &gt; Abstract<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0This specification describes version 2 of the Optimized Li=
nk State<br>
&gt; &gt; =A0 =A0Routing (OLSRv2) protocol for Mobile Ad hoc NETworks (MANE=
Ts).<br>
&gt; &gt;<br>
&gt; &gt; The file can be obtained via<br>
&gt; &gt; <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-manet-olsrv=
2/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-manet-olsr=
v2/</a><br>
&gt; &gt;<br>
&gt; &gt; IESG discussion can be tracked via<br>
&gt; &gt; <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-manet-olsrv=
2/ballot/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-man=
et-olsrv2/ballot/</a><br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; No IPR declarations have been submitted directly on this I-D.<br>
&gt; &gt;<br>
<br>
</blockquote></div><br>

--20cf307d007241094104c800fb82--

From abdussalambaryun@gmail.com  Fri Aug 24 04:43:59 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EF0D21F8692 for <ietf@ietfa.amsl.com>; Fri, 24 Aug 2012 04:43:59 -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.106,  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 fkEPY9gKgbqk for <ietf@ietfa.amsl.com>; Fri, 24 Aug 2012 04:43:58 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 91CB121F8683 for <ietf@ietf.org>; Fri, 24 Aug 2012 04:43:58 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so2156262vbb.31 for <ietf@ietf.org>; Fri, 24 Aug 2012 04:43:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=A5g5STn+rq8+eqQuVRFpq4SQkuizICTOqIyhCjYQ9uU=; b=u6nK7uxaNdfBV8kDLLwXjGwdU9Biuw0fpOZ3Mzmj+0mdbfAVzLQ8milsLH2JrR5V1r Y3JGaF5xzE6vEoafVj/R1dpxlnWa2cx2PxN1zt6pdBS0QB8uQh66lvCTCmIamyME6fU6 gey7XLLWGFf7siveSnAPxvf51SGroabpV9VfPFiUeUk/aw4S7lQr72Q1qlReaWVrz/Ip ToVM2CH7VncD8L+QWyG81GrYy7sQGOIih5GKMNcAhs4g/uT1mBoQRUXfLV0QqIOtqXra ZWaynRnBAWbQR4QlE0ZeRtyHMW0zWM3y1o5t/64nOwYADMcxi0wuTNTkS48gkD5bdaVG a2qw==
MIME-Version: 1.0
Received: by 10.220.37.194 with SMTP id y2mr3389076vcd.44.1345808637955; Fri, 24 Aug 2012 04:43:57 -0700 (PDT)
Received: by 10.220.55.9 with HTTP; Fri, 24 Aug 2012 04:43:57 -0700 (PDT)
Date: Fri, 24 Aug 2012 12:43:57 +0100
Message-ID: <CADnDZ8_AeRwe0sDe1a-rCZyG6s0X-hNN7T-qHz0-Ay33C_OZvQ@mail.gmail.com>
Subject: Is there: Discussions, Evaluations, Decisions, Acceptance, Progress?
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=bcaec54eea8ecd0ce304c8017d13
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Aug 2012 11:43:59 -0000

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

Hi All,

For any IETF WG discussion, we recommend reasons/references and equal
recognistion for progress.
For any IETF WG evaluation/review, we recommend two way discussions for
progress.
For any IETF WG decision, we recommend evaluation and then need rough
consensus for progress.
For any IESG decision, we recommend WG input and internet community input
and their consensus.

IMO, for any IETF-Participant's progress, he/she needs to know *why*
through discussions/questions, and he/she should make *decisions* for
the WG's I-Ds/RFCs with his/her community through rough consensus.
Decisions are accepted by community only if they are discussed or they
have clear reasons.

Please advise if you agree/disagree, thanks,

Best Regards
AB

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

<div>Hi All,</div><div>=A0</div><div>For any IETF WG discussion, we recomme=
nd reasons/references and equal recognistion for progress.</div><div><div>F=
or any IETF WG evaluation/review,=A0we recommend two way=A0discussions for =
progress.</div>
<div>For any IETF WG decision, we recommend evaluation and then need rough =
consensus for progress.</div><div>For any IESG decision, we recommend WG in=
put and internet=A0community input and their consensus.</div><div>=A0</div>
</div><div>IMO, for any IETF-Participant&#39;s progress, he/she needs to kn=
ow *why*<br>through discussions/questions, and he/she should make *decision=
s* for<br>the WG&#39;s I-Ds/RFCs with his/her community through rough conse=
nsus.<br>
Decisions are accepted by community only if they are discussed or they<br>h=
ave clear reasons.</div><div>=A0</div><div>Please advise if you agree/disag=
ree, thanks,</div><div>=A0</div><div>Best Regards</div><div>AB</div>

--bcaec54eea8ecd0ce304c8017d13--

From adrian@olddog.co.uk  Fri Aug 24 07:01:28 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6370D21F86EA for <ietf@ietfa.amsl.com>; Fri, 24 Aug 2012 07:01:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.518
X-Spam-Level: 
X-Spam-Status: No, score=-2.518 tagged_above=-999 required=5 tests=[AWL=0.081,  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 6mv6F0L7HhWh for <ietf@ietfa.amsl.com>; Fri, 24 Aug 2012 07:01:27 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 8600121F86E5 for <ietf@ietf.org>; Fri, 24 Aug 2012 07:01:27 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7OE1PiY020793;  Fri, 24 Aug 2012 15:01:25 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7OE1OXm020764 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 24 Aug 2012 15:01:24 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
Subject: FW: Last Call: <draft-ietf-manet-olsrv2-15.txt> (The Optimized Link State Routing Protocol version 2) to Proposed Standard
Date: Fri, 24 Aug 2012 15:01:21 +0100
Message-ID: <18b801cd8200$f14a6d50$d3df47f0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac2CAOHPGSa0La8sSvC+mJRl2R/NFQ==
Content-Language: en-gb
Cc: draft-ietf-manet-olsrv2.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Aug 2012 14:01:28 -0000

I consulted with the writer of this email about copying to the IETF list and he
asked the IESG to decide. I believe that it is helpful that technical comments
be aired in public, therefore I am forwarding an edited version of his email.

Authors, please include this in the responses that you will be generating.

Thanks,
Adrian

> -----Original Message-----
> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of
> Abdussalam Baryun
> Sent: 22 August 2012 23:01
> To: iesg@ietf.org
> Subject: Re: Last Call: <draft-ietf-manet-olsrv2-15.txt> (The Optimized Link
State
> Routing Protocol version 2) to Proposed Standard
> 
> Reply to your request dated 29/07/2012
> Draft Reviewed By: Abdussalam Baryun (AB)   Dated: 22/08/2012
> 
> Reviewer Comment AB7: Comments on text in document history [*].
> https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2/history/
> ++++++++++++++++++++++++++++++++++++
> 
> A key difference between RFC3626 and OLSRv2 is the introduction of
> support for link metrics. An individual draft
> (draft-dearlove-olsrv2-metrics-00) was submitted in 2007, discussing
> the design options, culminating in 2010 with
> draft-dearlove-olsrv2-metrics-05 documenting Working Group consensus
> on this matter. Metrics support was, then, folded into OLSRv2.
> 
> AB> the reviewer thinks the difference is that OLSRv2 is a metric base
> router that uses NHDP and RFC5444 packets which are general MANET
> interface protocol and general MANET packet format respectively.
> OLSRv2 is applicable for more scenarios and routers that are
> constraint devices.



From iesg-secretary@ietf.org  Fri Aug 24 07:58:30 2012
Return-Path: <iesg-secretary@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 9762321F870A; Fri, 24 Aug 2012 07:58:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7z+R5S3qYCWX; Fri, 24 Aug 2012 07:58:30 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E81821F86FE; Fri, 24 Aug 2012 07:58:30 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Closing Routing and Addressing Directorate (RADir)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20120824145830.3308.22620.idtracker@ietfa.amsl.com>
Date: Fri, 24 Aug 2012 07:58:30 -0700
Cc: iab@iab.org, ietf@ietf.org, radir@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Aug 2012 14:58:30 -0000

The Routing and Addressing Directorate (RADir) is closed. The RADir was =

chartered by Brian Carpenter and Leslie Daigle when they were IETF Chair an=
d =

IAB Chair, respectively. The RADir has not done anything in quite some time=
, and =

it is time to close. Thank you to the members of RADir for their service.

From chair@ietf.org  Fri Aug 24 08:11:16 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4D1D21F8718; Fri, 24 Aug 2012 08:11:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8kZCYOfnGioE; Fri, 24 Aug 2012 08:11:16 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 3227C21F8692; Fri, 24 Aug 2012 08:11:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 52E1612C9DA; Fri, 24 Aug 2012 08:11:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RgLOarLTAUy5; Fri, 24 Aug 2012 08:11:16 -0700 (PDT)
Received: from [192.168.1.3] (96-37-2-47.dhcp.sffl.va.charter.com [96.37.2.47]) by c8a.amsl.com (Postfix) with ESMTPSA id 9C7A712C95E; Fri, 24 Aug 2012 08:11:15 -0700 (PDT)
Subject: Re: Last Call: Modern Global Standards Paradigm
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: IETF Chair <chair@ietf.org>
In-Reply-To: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org>
Date: Fri, 24 Aug 2012 11:11:13 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C28406A5-36A0-4A58-BF2F-BBA55F25CE01@ietf.org>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Aug 2012 15:11:16 -0000

Thank you for the lively discussion.  Based on the great number of =
messages, I judge that there is rough consensus for the IETF Chair and =
the IAB Chair signing the Affirmation.  The Last Call asks for people to =
speak up if they have strong objections.  Despite the phrasing of the =
question, many people spoke in favor of this action.

A few people raised concerns about the process that lead to this =
document.  First, Bernard Aboba, acting as IAB Chair, sent the statement =
out and asked for comment.  Then, the document was discussed in the =
plenary session on Vancouver.  Finally, on August 10th, I sent out the =
Last Call.  Comments sent in reply to Bernard's message and comments =
from the plenary discussion were addresses prior to the Last Call.

Here are the versions:
Asked for comment: =
http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-4.pdf
Last Call: =
http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf=


This document is not intended for the standards track.  The IAB is =
considering publication as an Informational RFC to preserve the document =
in the RFC series.

Based on the comments received during the Last Call, one change is being =
made to the document.  The document said:

  4. Availability. Standards specifications are made accessible to all =
for
  implementation and deployment. Affirming standards organizations have =
defined
  procedures to develop specifications that can be implemented under =
fair terms.
  Given market diversity, fair terms may vary from royalty-free =
(especially where
  open source is commonplace) to fair, reasonable, and =
non-discriminatory terms
  (FRAND).

The Last Call raised a concern, asking for deletion of this phrase:

  (especially where open source is commonplace)

Based on the Last Call discussion, this change was recommended to the =
other signers.  This change was accepted, and this phrase will be =
deleted.

Thanks again,
  Russ Housley
  IETF Chair


On Aug 10, 2012, at 11:19 AM, IETF Chair wrote:

>=20
> The IETF Chair and the IAB Chair intend to sign the Affirmation
> of the Modern Global Standards Paradigm, which can be found
> here:
>=20
> =
http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf=

>=20
> An earlier version was discussed in plenary, and the IAB Chair called
> for comments on the IETF mail list.  This version includes changes
> that address those comments.
>=20
> Th IETF 84 Administrative plenary minutes have been posted, so that
> discussion can be reviewed if desired.  The minutes are here:
>=20
> http://www.ietf.org/proceedings/84/minutes/minutes-84-iesg-opsplenary
>=20
> On 8 August 2012, the IEEE Standards Association Board of Governors
> approved this version of the document.  The approval process is
> underway at the W3C as well.
>=20
> The IETF Chair and the IAB Chair intend to sign the Affirmation in the
> next few weeks. Please send strong objections to the iab@iab.org
> and the ietf@ietf.org mailing lists by 2012-08-24.
>=20
> Thank you,
>  Russ Housley
>  IETF Chair


From chair@ietf.org  Sun Aug 26 12:45:17 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D85D321F84B5; Sun, 26 Aug 2012 12:45:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YQFZDPvpxXpa; Sun, 26 Aug 2012 12:45:17 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 53FA921F84A7; Sun, 26 Aug 2012 12:45:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 402DB12C0FF; Sun, 26 Aug 2012 12:45:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0D3BtMEyFNzl; Sun, 26 Aug 2012 12:45:17 -0700 (PDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) by c8a.amsl.com (Postfix) with ESMTPSA id B6A7112C0FE; Sun, 26 Aug 2012 12:45:16 -0700 (PDT)
Subject: Re: Last Call: Modern Global Standards Paradigm
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: IETF Chair <chair@ietf.org>
In-Reply-To: <C28406A5-36A0-4A58-BF2F-BBA55F25CE01@ietf.org>
Date: Sun, 26 Aug 2012 15:45:14 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3E7D4F4F-FF49-44F3-970F-09D74C56B6CD@ietf.org>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <C28406A5-36A0-4A58-BF2F-BBA55F25CE01@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
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: Sun, 26 Aug 2012 19:45:18 -0000

The version with the phrase deleted is now available:
=
http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-16.pdf=



On Aug 24, 2012, at 11:11 AM, IETF Chair wrote:

> Thank you for the lively discussion.  Based on the great number of =
messages, I judge that there is rough consensus for the IETF Chair and =
the IAB Chair signing the Affirmation.  The Last Call asks for people to =
speak up if they have strong objections.  Despite the phrasing of the =
question, many people spoke in favor of this action.
>=20
> A few people raised concerns about the process that lead to this =
document.  First, Bernard Aboba, acting as IAB Chair, sent the statement =
out and asked for comment.  Then, the document was discussed in the =
plenary session on Vancouver.  Finally, on August 10th, I sent out the =
Last Call.  Comments sent in reply to Bernard's message and comments =
from the plenary discussion were addresses prior to the Last Call.
>=20
> Here are the versions:
> Asked for comment: =
http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-4.pdf
> Last Call: =
http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf=

>=20
> This document is not intended for the standards track.  The IAB is =
considering publication as an Informational RFC to preserve the document =
in the RFC series.
>=20
> Based on the comments received during the Last Call, one change is =
being made to the document.  The document said:
>=20
>  4. Availability. Standards specifications are made accessible to all =
for
>  implementation and deployment. Affirming standards organizations have =
defined
>  procedures to develop specifications that can be implemented under =
fair terms.
>  Given market diversity, fair terms may vary from royalty-free =
(especially where
>  open source is commonplace) to fair, reasonable, and =
non-discriminatory terms
>  (FRAND).
>=20
> The Last Call raised a concern, asking for deletion of this phrase:
>=20
>  (especially where open source is commonplace)
>=20
> Based on the Last Call discussion, this change was recommended to the =
other signers.  This change was accepted, and this phrase will be =
deleted.
>=20
> Thanks again,
>  Russ Housley
>  IETF Chair
>=20
>=20
> On Aug 10, 2012, at 11:19 AM, IETF Chair wrote:
>=20
>>=20
>> The IETF Chair and the IAB Chair intend to sign the Affirmation
>> of the Modern Global Standards Paradigm, which can be found
>> here:
>>=20
>> =
http://www.ietf.org/proceedings/84/slides/slides-84-iesg-opsplenary-15.pdf=

>>=20
>> An earlier version was discussed in plenary, and the IAB Chair called
>> for comments on the IETF mail list.  This version includes changes
>> that address those comments.
>>=20
>> Th IETF 84 Administrative plenary minutes have been posted, so that
>> discussion can be reviewed if desired.  The minutes are here:
>>=20
>> http://www.ietf.org/proceedings/84/minutes/minutes-84-iesg-opsplenary
>>=20
>> On 8 August 2012, the IEEE Standards Association Board of Governors
>> approved this version of the document.  The approval process is
>> underway at the W3C as well.
>>=20
>> The IETF Chair and the IAB Chair intend to sign the Affirmation in =
the
>> next few weeks. Please send strong objections to the iab@iab.org
>> and the ietf@ietf.org mailing lists by 2012-08-24.
>>=20
>> Thank you,
>> Russ Housley
>> IETF Chair
>=20


From abdussalambaryun@gmail.com  Tue Aug 28 03:17:51 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03C0911E8100 for <ietf@ietfa.amsl.com>; Tue, 28 Aug 2012 03:17:51 -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.099,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ho2SnMfnoVsA for <ietf@ietfa.amsl.com>; Tue, 28 Aug 2012 03:17:50 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 65C6811E80F8 for <ietf@ietf.org>; Tue, 28 Aug 2012 03:17:50 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so6218399vbb.31 for <ietf@ietf.org>; Tue, 28 Aug 2012 03:17:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=g1F9GgJAehJyszgY47RX6+Ej1jMtVjLyfv66ubBJmf0=; b=jYGPjXWHZsdcTuiHHWTzVaBxmZ3Zn/gcxvEEbGv52MOIgo19qS9bcaEnNi0h6s0QzD Vdfby0dgqYZGsLBt9C0Qdh1xScP2MPE/GreZd+75zj+YXfCdWBr5KO0DRFRofc5f40ar eHYxHl4z8pdBM12PWFI33qP5Ee6rfSAtR4zADwo7xzphDwT4fW9hHUA0jjoTKV/SNKqF w0dc8qsjSGT4RQX1N4ZIicHRigYaMj60XUs1gFzHFy/dxVKZbKNs2rFAEeMDpzug2P5/ H1j2l/ylNIy4NaSWJn0Iu1iIYljkoaCDEnWUXIMV/in1m0vK1MbqFq5A6fypQpzcpM7l YNJQ==
MIME-Version: 1.0
Received: by 10.58.249.195 with SMTP id yw3mr15431641vec.43.1346149069734; Tue, 28 Aug 2012 03:17:49 -0700 (PDT)
Received: by 10.220.55.9 with HTTP; Tue, 28 Aug 2012 03:17:49 -0700 (PDT)
Date: Tue, 28 Aug 2012 11:17:49 +0100
Message-ID: <CADnDZ8_uDPiqh+nD6VwUB-S5jQM6A_KrLCs6rv=793qbY=-RXQ@mail.gmail.com>
Subject: Minutes SHOULD include participants number
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b86f3aa1dc1b004c850c1e1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Aug 2012 10:17:51 -0000

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

Hi

Reading through some IETF WGs minutes of meetings, is it possible that we
follow a procedure in writting minutes.
I think the following items are important that SHOULD be included:

1) name of the chair, minute taker, and jabber reader.
2) number of participant in the meeting room.
3) number of participants at jabber.

Regards
AB

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

<div>Hi</div><div>=A0</div><div>Reading through some IETF WGs minutes of=A0=
meetings, is it possible that we follow a procedure in writting minutes.</d=
iv><div>I think the following items are important that SHOULD be included:<=
/div>
<div>=A0</div><div>1) name of the chair, minute taker, and jabber reader.</=
div><div>2) number of participant in the meeting room.</div><div>3) number =
of participants at jabber.</div><div>=A0</div><div>Regards</div><div>AB</di=
v>

--047d7b86f3aa1dc1b004c850c1e1--

From john-ietf@jck.com  Tue Aug 28 10:22:01 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83D4221F85B1 for <ietf@ietfa.amsl.com>; Tue, 28 Aug 2012 10:22:01 -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 1YZeIU55Ylg6 for <ietf@ietfa.amsl.com>; Tue, 28 Aug 2012 10:22:01 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 81DE221F85AE for <ietf@ietf.org>; Tue, 28 Aug 2012 10:22:00 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1T6PUF-000GO6-FU; Tue, 28 Aug 2012 13:21:59 -0400
Date: Tue, 28 Aug 2012 13:21:54 -0400
From: John C Klensin <john-ietf@jck.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, ietf <ietf@ietf.org>
Subject: Re: Minutes SHOULD include participants number
Message-ID: <2F3D65048BFCBB6AF7F2C91D@JcK-HP8200.jck.com>
In-Reply-To: <CADnDZ8_uDPiqh+nD6VwUB-S5jQM6A_KrLCs6rv=793qbY=-RXQ@mail.gmail.com>
References: <CADnDZ8_uDPiqh+nD6VwUB-S5jQM6A_KrLCs6rv=793qbY=-RXQ@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Aug 2012 17:22:02 -0000

--On Tuesday, August 28, 2012 11:17 +0100 Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:

> Hi
> 
> Reading through some IETF WGs minutes of meetings, is it
> possible that we follow a procedure in writting minutes.
> I think the following items are important that SHOULD be
> included:
> 
> 1) name of the chair, minute taker, and jabber reader.
> 2) number of participant in the meeting room.
> 3) number of participants at jabber.

It seems to me that the latter two would fall somewhere between
"useless" and "misleading".  I don't have any idea how to count
"participants" in the meeting room.  The only numbers that are
reasonably easy to capture are the number of people who signed
the blue sheets, but that doesn't capture either non-signers or
those who sign and then sit in the room and pay more attention
to email or other topics than the meeting.  If we used the
number of people signed into Jabber for anything, we'd create a
count that was extremely easy to pack as well as not
distinguishing between people who were on Jabber but in the
room, on Jabber but elsewhere at the IETF meeting (conflicts or
couldn't be bothered to attend), remote and actively following
the meeting, or others (and there are likely to be some others).

I could see somewhat more value if actual names and
organizational affiliations were listed, but the community has
(for plausible reasons, IMO) decided to not do that.

This is just a personal opinion/request, but I would really
appreciate it if you (or others making procedural
suggestions/requests like this) would carefully think through
the implications of what they are asking for and how the
information would be used before making the request.  It would
be even better if you then included an explanation of the value
that you think would occur, and maybe the tradeoffs you see,
with the request, not just "is it possible that we follow a
procedure...".  

That would have an advantage for you too because such
suggestions are more likely to be taken seriously by more people
in the IETF rather than, in the extreme case, going unread
because you have developed a history of bad and/or unjustified
ideas.

regards,
   john



From ben@nostrum.com  Tue Aug 28 12:12:23 2012
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F50E21F861E; Tue, 28 Aug 2012 12:12:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.555
X-Spam-Level: 
X-Spam-Status: No, score=-102.555 tagged_above=-999 required=5 tests=[AWL=0.045, 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 ZIaIAEHnDcBH; Tue, 28 Aug 2012 12:12:22 -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 7D2B221F85B4; Tue, 28 Aug 2012 12:12:21 -0700 (PDT)
Received: from [10.0.1.30] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q7SJCKG0028166 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 28 Aug 2012 14:12:20 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART Telechat review of draft-eggert-successful-bar-bof-08
Date: Tue, 28 Aug 2012 14:12:18 -0500
Message-Id: <F7FBD7FB-6F10-4D1E-93D8-BACC2D46867B@nostrum.com>
To: draft-eggert-successful-bar-bof.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
X-Mailer: Apple Mail (2.1486)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Aug 2012 19:12:23 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-eggert-successful-bar-bof-08
Reviewer: Ben Campbell
Review Date: 2012-08-28
IESG Telechat date: 2012-08-30

Summary: Ready for publication as an informational RFC

Note: The review assignment was for version 07, but since 08 was =
published prior to my review, I reviewed it instead. This version and =
related email correspondence address all of my concerns from my Gen-ART =
review of version 06 at IETF last call.

Major issues:

None

Minor issues:

None

Nits/editorial comments:

None=

From chair@ietf.org  Tue Aug 28 21:05:35 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE34111E80F2; Tue, 28 Aug 2012 21:05:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.299
X-Spam-Level: 
X-Spam-Status: No, score=-101.299 tagged_above=-999 required=5 tests=[AWL=-1.300, 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 Z0yMAHIGRDMt; Tue, 28 Aug 2012 21:05:34 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 5925511E80F1; Tue, 28 Aug 2012 21:05:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 764F012BB6C; Tue, 28 Aug 2012 21:05:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 34B3wSrhS4gl; Tue, 28 Aug 2012 21:05:30 -0700 (PDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) by c8a.amsl.com (Postfix) with ESMTPSA id DCB2C12BB63; Tue, 28 Aug 2012 21:05:29 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Leading Global Standards Organizations Endorse 'OpenStand' Principles that Drive Innovation and Borderless Commerce
Date: Wed, 29 Aug 2012 00:05:30 -0400
Message-Id: <E822CC92-68B6-491A-B445-E587455650C5@ietf.org>
To: IETF Announce <ietf-announce@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
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, 29 Aug 2012 04:05:35 -0000

The leaders of the IEEE Standards Association, the IAB, the IETF,
the Internet Society, and the W3C signed a statement affirming the
importance of a jointly developed set of principles establishing a
modern paradigm for global, open standards.  Below is a press release
about this event.  You can learn more about these principles at
www.open-stand.org.

Best wishes,
  Russ Housley
  IETF Chair

* * * * * * * * * *

Leading Global Standards Organizations Endorse 'OpenStand'
Principles that Drive Innovation and Borderless Commerce

IEEE, IAB, IETF, Internet Society and W3C Invite Other Standards
Organizations, Governments and Companies to Support Modern Paradigm
for Global, Open Standards 

PISCATAWAY, N.J., and WASHINGTON, D.C., United States; GENEVA,
Switzerland, and http://www.w3.org/ -- 29 August 2012 -- Five leading
global organizations -- IEEE, Internet Architecture Board (IAB),
Internet Engineering Task Force (IETF), Internet Society and
World Wide Web Consortium (W3C) -- today announced that they have
signed a statement affirming the importance of a jointly developed set
of principles establishing a modern paradigm for global, open standards.
The shared "OpenStand" principles -- based on the effective and
efficient standardization processes that have made the Internet and
Web the premiere platforms for innovation and borderless commerce -- are
proven in their ability to foster competition and cooperation, support
innovation and interoperability and drive market success. 

IEEE, IAB, IETF, Internet Society and W3C invite other standards
organizations, governments, corporations and technology innovators
globally to endorse the principles, which are available at
open-stand.org.

The OpenStand principles strive to encapsulate that successful
standardization model and make it extendable across the contemporary,
global economy's gamut of technology spaces and markets. The principles
comprise a modern paradigm in which the economics of global
markets -- fueled by technological innovation -- drive global
deployment of standards, regardless of their formal status within
traditional bodies of national representation. The OpenStand principles
demand:

 * cooperation among standards organizations; 

 * adherence to due process, broad consensus, transparency, balance
   and openness in standards development;

 * commitment to technical merit, interoperability, competition,
   innovation and benefit to humanity;

 * availability of standards to all; and

 * voluntary adoption.

"New dynamics and pressures on global industry have driven changes in
the ways that standards are developed and adopted around the world,"
said Steve Mills, president of the IEEE Standards Association.
"Increasing globalization of markets, the rapid advancement of
technology and intensifying time-to-market demands have forced
industry to seek more efficient ways to define the global standards
that help expand global markets. The OpenStand principles foster the
more efficient international standardization paradigm that the world
needs."

Added Leslie Daigle, chief Internet technology officer with the Internet
Society: "International standards development for borderless economics
is not ad hoc; rather, it has a paradigm--one that has demonstrated
agility and is driven by technical merit. The OpenStand principles
convey the power of bottom-up collaboration in harnessing global
creativity and expertise to the standards of any technology space that
will underpin the modern economy moving forward."

Standards developed and adopted via the OpenStand principles include
IEEE standards for the Internet's physical connectivity, IETF standards
for end-to-end global Internet interoperability and the W3C standards
for the World Wide Web.

"The Internet and World Wide Web have fueled an economic and social
transformation, touching billions of lives. Efficient standardization
of so many technologies has been key to the success of the global
Internet," said Russ Housley, IETF chair. "These global standards were
developed with a focus toward technical excellence and deployed through
collaboration of many participants from all around the world. The
results have literally changed the world, surpassing anything that has
ever been achieved through any other standards-development model."

Globally adopted design-automation standards, which have paved the way
for a giant leap forward in industry's ability to define complex
electronic solutions, provide another example of standards developed in
the spirit of the OpenStand principles. Another technology space that
figures to demand such standards over the next decades is the global
smart-grid effort, which seeks to augment regional facilities for
electricity generation, distribution, delivery and consumption with a
two-way, end-to-end network for communications and control.

"Think about all that the Internet and Web have enabled over the past
30 years, completely transforming society, government and commerce,"
said W3C chief executive officer Jeff Jaffe. "It is remarkable that a
small number of organizations following a small number of principles
have had such a huge impact on humanity, innovation and competition in
global markets."

Bernard Aboba, chair of the IAB: "The Internet has been built on
specifications adopted voluntarily across the globe. By valuing
running code, interoperability and deployment above formal status,
the Internet has democratized the development of standards, enabling
specifications originally developed outside of standards organizations
to gain recognition based on their technical merit and adoption,
contributing to the creation of global communities benefiting
humanity. We now invite standards organizations, as well as
governments, companies and individuals to join us at open-stand.org
in order to affirm the principles that have nurtured the Internet
and underpin many other important standards -- and will continue to
do so."


From bortzmeyer@nic.fr  Wed Aug 29 01:07:44 2012
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 5334D21F842F for <ietf@ietfa.amsl.com>; Wed, 29 Aug 2012 01:07:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.236
X-Spam-Level: 
X-Spam-Status: No, score=-101.236 tagged_above=-999 required=5 tests=[AWL=-0.476, BAYES_05=-1.11, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jM1pSGJ5igRH for <ietf@ietfa.amsl.com>; Wed, 29 Aug 2012 01:07:43 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [192.134.4.12]) by ietfa.amsl.com (Postfix) with ESMTP id 8E09521F847A for <ietf@ietf.org>; Wed, 29 Aug 2012 01:07:43 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id DF199280289 for <ietf@ietf.org>; Wed, 29 Aug 2012 10:07:09 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx4.nic.fr (Postfix) with ESMTP id DB7A5280152 for <ietf@ietf.org>; Wed, 29 Aug 2012 10:07:09 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:2219:8::6:69]) by relay2.nic.fr (Postfix) with ESMTP id D9DFEB3805C for <ietf@ietf.org>; Wed, 29 Aug 2012 10:06:39 +0200 (CEST)
Date: Wed, 29 Aug 2012 10:06:39 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: IETF <ietf@ietf.org>
Subject: Re: Leading Global Standards Organizations Endorse 'OpenStand' Principles that Drive Innovation and Borderless Commerce
Message-ID: <20120829080639.GA15710@nic.fr>
References: <E822CC92-68B6-491A-B445-E587455650C5@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E822CC92-68B6-491A-B445-E587455650C5@ietf.org>
X-Operating-System: Debian GNU/Linux wheezy/sid
X-Kernel: Linux 3.2.0-3-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Aug 2012 08:07:44 -0000

[I was on disconnected holidays during the "Last Call", sorry.]

On Wed, Aug 29, 2012 at 12:05:30AM -0400,
 IETF Chair <chair@ietf.org> wrote 
 a message of 119 lines which said:

> The leaders of the IEEE Standards Association, the IAB, the IETF,
> the Internet Society, and the W3C signed a statement affirming the
> importance of a jointly developed set of principles establishing a
> modern paradigm for global, open standards.  Below is a press
> release about this event.  

> Leading Global Standards Organizations Endorse 'OpenStand'
> Principles that Drive Innovation and Borderless Commerce

I strongly regret that "Commerce" has a specific mention, among all
the other uses of the Internet. The network is not only open for
business!

> IEEE, IAB, IETF, Internet Society and W3C Invite Other Standards
> Organizations, Governments and Companies 
...
>  * availability of standards to all; 

Unfortunately, the actual text is very short on this matter
("Standards specifications are made accessible to all for
implementation and deployment") and does not mention gratis access and
redistribution, one of the big reasons of the success of the TCP/IP
family (RFC 5218, section 2.1.5). Was it because the IEEE would not
sign otherwise
<http://www.ieee.org/publications_standards/index.html>?

From abdussalambaryun@gmail.com  Wed Aug 29 01:12:28 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DDE421F849B for <ietf@ietfa.amsl.com>; Wed, 29 Aug 2012 01:12:28 -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 3iJrkRHufgwy for <ietf@ietfa.amsl.com>; Wed, 29 Aug 2012 01:12:27 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id A073521F8491 for <ietf@ietf.org>; Wed, 29 Aug 2012 01:12:27 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so360527vbb.31 for <ietf@ietf.org>; Wed, 29 Aug 2012 01:12:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/JZewtfSwqz9xNFGjl1NKHGvEwQFECvc1Nhrqqq2ESg=; b=kvtkvItDbx5bMrYptbZyElG/s7/Gd1v221kRVZ+enJwMAivWOMswKltqmocYSS1Zt9 pPcpc1IxEO1HEgFOghr9AW4sN1BMWjOekRxSBKSHPIKhck9SO2wNVz5hqyLREnnemBzV /+/9GKOnjKpGXalNplbwNTxtAJ7t4jtl+H7/oBq0d8fQbiK9mRJ6nTsaCfjJYWlCUG73 LHuBXj3Hw5XieZIKs3C7Y+S/ygElAbg+Za0UP+g1xPHZ1RXC3lTHKdpiYNMZZBSLy4da r+W4v1MVNxhxIEQU6RKgZmnI0OHreJBeBUBjRQZT6q9PEXSFDQcOEX4rpi3pFw2VNgSK hC8w==
MIME-Version: 1.0
Received: by 10.220.119.198 with SMTP id a6mr620855vcr.23.1346227946673; Wed, 29 Aug 2012 01:12:26 -0700 (PDT)
Received: by 10.220.55.9 with HTTP; Wed, 29 Aug 2012 01:12:26 -0700 (PDT)
In-Reply-To: <2F3D65048BFCBB6AF7F2C91D@JcK-HP8200.jck.com>
References: <CADnDZ8_uDPiqh+nD6VwUB-S5jQM6A_KrLCs6rv=793qbY=-RXQ@mail.gmail.com> <2F3D65048BFCBB6AF7F2C91D@JcK-HP8200.jck.com>
Date: Wed, 29 Aug 2012 10:12:26 +0200
Message-ID: <CADnDZ8-2MbzQv7hZEOxka92hDSe2Ofyb2ThFTqr03UsLw84nBA@mail.gmail.com>
Subject: Re: Minutes SHOULD include participants number
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Aug 2012 08:12:28 -0000

Hi John,

Thanks for your advise and comments. I prefered that consensus is
documented to know its value/level as was it 60% or 70% or 80%...etc.
How do Chairs in IETF decide on the agree/disagree/no-reply from WGs

 " Note that 51% of the working group does not qualify as "rough consensus" and
   99% is better than rough.  It is up to the Chair to determine if rough
  consensus has been reached."

I see that minutes just mention WG agreed to ..., but would suggest
the value, so it does not become below 51%. Also, most participants
need more time to decide on such request from Chairs because they use
their variable-available-volunteering time to do reading/work within
each 28 days.

Regards
AB
---
On 8/28/12, John C Klensin <john-ietf@jck.com> wrote:
>
>
> --On Tuesday, August 28, 2012 11:17 +0100 Abdussalam Baryun
> <abdussalambaryun@gmail.com> wrote:
>
>> Hi
>>
>> Reading through some IETF WGs minutes of meetings, is it
>> possible that we follow a procedure in writting minutes.
>> I think the following items are important that SHOULD be
>> included:
>>
>> 1) name of the chair, minute taker, and jabber reader.
>> 2) number of participant in the meeting room.
>> 3) number of participants at jabber.
>
> It seems to me that the latter two would fall somewhere between
> "useless" and "misleading".  I don't have any idea how to count
> "participants" in the meeting room.  The only numbers that are
> reasonably easy to capture are the number of people who signed
> the blue sheets, but that doesn't capture either non-signers or
> those who sign and then sit in the room and pay more attention
> to email or other topics than the meeting.  If we used the
> number of people signed into Jabber for anything, we'd create a
> count that was extremely easy to pack as well as not
> distinguishing between people who were on Jabber but in the
> room, on Jabber but elsewhere at the IETF meeting (conflicts or
> couldn't be bothered to attend), remote and actively following
> the meeting, or others (and there are likely to be some others).
>
> I could see somewhat more value if actual names and
> organizational affiliations were listed, but the community has
> (for plausible reasons, IMO) decided to not do that.
>
> This is just a personal opinion/request, but I would really
> appreciate it if you (or others making procedural
> suggestions/requests like this) would carefully think through
> the implications of what they are asking for and how the
> information would be used before making the request.  It would
> be even better if you then included an explanation of the value
> that you think would occur, and maybe the tradeoffs you see,
> with the request, not just "is it possible that we follow a
> procedure...".
>
> That would have an advantage for you too because such
> suggestions are more likely to be taken seriously by more people
> in the IETF rather than, in the extreme case, going unread
> because you have developed a history of bad and/or unjustified
> ideas.
>
> regards,
>    john
>
>
>

From agmalis@gmail.com  Wed Aug 29 01:33:26 2012
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 631B221F8598 for <ietf@ietfa.amsl.com>; Wed, 29 Aug 2012 01:33:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.86
X-Spam-Level: 
X-Spam-Status: No, score=-2.86 tagged_above=-999 required=5 tests=[AWL=-0.261,  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 17X5uVKGQQpp for <ietf@ietfa.amsl.com>; Wed, 29 Aug 2012 01:33:25 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id A955821F8595 for <ietf@ietf.org>; Wed, 29 Aug 2012 01:33:25 -0700 (PDT)
Received: by ieak13 with SMTP id k13so111369iea.31 for <ietf@ietf.org>; Wed, 29 Aug 2012 01:33:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=wJMC0cwB+C3AkprgmslQIcR3161Q1W/TuIHyhnhggdM=; b=Cs+MAmVUogk8vU4MWwpMsFOf7rlVFRMLwj02K1qjY0X/qouz+EhCReg7EL0Coj+3L1 CtJPABmfJZ2oZWgQnTmZ86twsoD98J6Wp8KBn5iMVnbTmFQ7Fi1/xR4QiDzsqmcTL3mK rICZfDjztdLaZFE6oJeZUIoP8wEnH9cLN5+zKWlb1UYUGRxZECiK/wKiMJsFBCeD5lwG htPgEoaZx7OyQoE3XotsECc4b1YOkXSHtPz2gzew2NCpLrFf9bY6H7EjrDfG6W1+EeM/ wg9GaFg4Vm5xunLd6vrb4NmJ8NC0GsYmv1UqtVH0MFIdnQJQhAtLwO5/CjRAnK0J/HCZ Dl4g==
Received: by 10.50.184.227 with SMTP id ex3mr773457igc.26.1346229205164; Wed, 29 Aug 2012 01:33:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.124.70 with HTTP; Wed, 29 Aug 2012 01:33:04 -0700 (PDT)
In-Reply-To: <CADnDZ8-2MbzQv7hZEOxka92hDSe2Ofyb2ThFTqr03UsLw84nBA@mail.gmail.com>
References: <CADnDZ8_uDPiqh+nD6VwUB-S5jQM6A_KrLCs6rv=793qbY=-RXQ@mail.gmail.com> <2F3D65048BFCBB6AF7F2C91D@JcK-HP8200.jck.com> <CADnDZ8-2MbzQv7hZEOxka92hDSe2Ofyb2ThFTqr03UsLw84nBA@mail.gmail.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Wed, 29 Aug 2012 11:33:04 +0300
Message-ID: <CAA=duU3EnMN-sS+1xZhc3UKpQc3epC4H7-Kqjm+GrM5-4fFWSQ@mail.gmail.com>
Subject: Re: Minutes SHOULD include participants number
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: John C Klensin <john-ietf@jck.com>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Aug 2012 08:33:26 -0000

Just on a practical matter, many of us WG chairs like to get the
minutes uploaded as quickly as possible, before the blue sheet numbers
are available. Like John, I fail to see the value of recording the
number of people sitting in chairs, except to size the room for the
next meeting. One of the most productive WGs I ever participated in
usually had fewer than 10 people at a meeting, but every single one of
those people contributed to the documents.

Regarding consensus, that's a different matter altogether, and one you
didn't mention in your original email. In most WGs (certainly in
mine), consensus is not determined in the meeting, but on the list. In
the minutes, we'll sometimes report on the "sense of the room", but
it's nothing more than that.

Cheers,
Andy

On Wed, Aug 29, 2012 at 11:12 AM, Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:
> Hi John,
>
> Thanks for your advise and comments. I prefered that consensus is
> documented to know its value/level as was it 60% or 70% or 80%...etc.
> How do Chairs in IETF decide on the agree/disagree/no-reply from WGs
>
>  " Note that 51% of the working group does not qualify as "rough consensus" and
>    99% is better than rough.  It is up to the Chair to determine if rough
>   consensus has been reached."
>
> I see that minutes just mention WG agreed to ..., but would suggest
> the value, so it does not become below 51%. Also, most participants
> need more time to decide on such request from Chairs because they use
> their variable-available-volunteering time to do reading/work within
> each 28 days.
>
> Regards
> AB
> ---
> On 8/28/12, John C Klensin <john-ietf@jck.com> wrote:
>>
>>
>> --On Tuesday, August 28, 2012 11:17 +0100 Abdussalam Baryun
>> <abdussalambaryun@gmail.com> wrote:
>>
>>> Hi
>>>
>>> Reading through some IETF WGs minutes of meetings, is it
>>> possible that we follow a procedure in writting minutes.
>>> I think the following items are important that SHOULD be
>>> included:
>>>
>>> 1) name of the chair, minute taker, and jabber reader.
>>> 2) number of participant in the meeting room.
>>> 3) number of participants at jabber.
>>
>> It seems to me that the latter two would fall somewhere between
>> "useless" and "misleading".  I don't have any idea how to count
>> "participants" in the meeting room.  The only numbers that are
>> reasonably easy to capture are the number of people who signed
>> the blue sheets, but that doesn't capture either non-signers or
>> those who sign and then sit in the room and pay more attention
>> to email or other topics than the meeting.  If we used the
>> number of people signed into Jabber for anything, we'd create a
>> count that was extremely easy to pack as well as not
>> distinguishing between people who were on Jabber but in the
>> room, on Jabber but elsewhere at the IETF meeting (conflicts or
>> couldn't be bothered to attend), remote and actively following
>> the meeting, or others (and there are likely to be some others).
>>
>> I could see somewhat more value if actual names and
>> organizational affiliations were listed, but the community has
>> (for plausible reasons, IMO) decided to not do that.
>>
>> This is just a personal opinion/request, but I would really
>> appreciate it if you (or others making procedural
>> suggestions/requests like this) would carefully think through
>> the implications of what they are asking for and how the
>> information would be used before making the request.  It would
>> be even better if you then included an explanation of the value
>> that you think would occur, and maybe the tradeoffs you see,
>> with the request, not just "is it possible that we follow a
>> procedure...".
>>
>> That would have an advantage for you too because such
>> suggestions are more likely to be taken seriously by more people
>> in the IETF rather than, in the extreme case, going unread
>> because you have developed a history of bad and/or unjustified
>> ideas.
>>
>> regards,
>>    john
>>
>>
>>

From bortzmeyer@nic.fr  Wed Aug 29 01:35:50 2012
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 37A3021F85B4; Wed, 29 Aug 2012 01:35:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.941
X-Spam-Level: 
X-Spam-Status: No, score=-101.941 tagged_above=-999 required=5 tests=[AWL=0.308, BAYES_00=-2.599, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oIBpLU6XvBEU; Wed, 29 Aug 2012 01:35:49 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [192.134.4.12]) by ietfa.amsl.com (Postfix) with ESMTP id 8184121F85B1; Wed, 29 Aug 2012 01:35:49 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id E643A2803B1; Wed, 29 Aug 2012 10:35:16 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx4.nic.fr (Postfix) with ESMTP id E1C46280152; Wed, 29 Aug 2012 10:35:16 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:2219:8::6:69]) by relay2.nic.fr (Postfix) with ESMTP id D6C31B38071; Wed, 29 Aug 2012 10:35:16 +0200 (CEST)
Date: Wed, 29 Aug 2012 10:35:16 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: IETF Chair <chair@ietf.org>
Subject: Re: Leading Global Standards Organizations Endorse 'OpenStand' Principles 	that Drive Innovation and Borderless Commerce
Message-ID: <20120829083516.GA19758@nic.fr>
References: <E822CC92-68B6-491A-B445-E587455650C5@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <E822CC92-68B6-491A-B445-E587455650C5@ietf.org>
X-Operating-System: Debian GNU/Linux wheezy/sid
X-Kernel: Linux 3.2.0-3-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Aug 2012 08:35:50 -0000

On Wed, Aug 29, 2012 at 12:05:30AM -0400,
 IETF Chair <chair@ietf.org> wrote 
 a message of 119 lines which said:

> You can learn more about these principles at www.open-stand.org.

The link "Français" for the translation of the principles in French
yields a 404...

May be it was written by jean-michel bernier de portzamparc :-)

From loa@pi.nu  Wed Aug 29 01:44:51 2012
Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCF3221F8540 for <ietf@ietfa.amsl.com>; Wed, 29 Aug 2012 01:44:51 -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 3WHMWDVndJQc for <ietf@ietfa.amsl.com>; Wed, 29 Aug 2012 01:44:50 -0700 (PDT)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by ietfa.amsl.com (Postfix) with ESMTP id 5E2C721F8555 for <ietf@ietf.org>; Wed, 29 Aug 2012 01:44:50 -0700 (PDT)
Received: from [192.168.1.64] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id 6263B2A8003 for <ietf@ietf.org>; Wed, 29 Aug 2012 10:44:42 +0200 (CEST)
Message-ID: <503DD674.70602@pi.nu>
Date: Wed, 29 Aug 2012 10:44:36 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Minutes SHOULD include participants number
References: <CADnDZ8_uDPiqh+nD6VwUB-S5jQM6A_KrLCs6rv=793qbY=-RXQ@mail.gmail.com> <2F3D65048BFCBB6AF7F2C91D@JcK-HP8200.jck.com> <CADnDZ8-2MbzQv7hZEOxka92hDSe2Ofyb2ThFTqr03UsLw84nBA@mail.gmail.com> <CAA=duU3EnMN-sS+1xZhc3UKpQc3epC4H7-Kqjm+GrM5-4fFWSQ@mail.gmail.com>
In-Reply-To: <CAA=duU3EnMN-sS+1xZhc3UKpQc3epC4H7-Kqjm+GrM5-4fFWSQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Aug 2012 08:44:51 -0000

AB,

I think what Andy says is that "percentage" nothing to do with rough
consensus. Rough consensus has everything to do with finding ways
forward that the entire wg can live with. Sometimes people find
themselves "in the rough", we don't fully agree with what working group
chairs says is the wg (rough) consensus. Toe "be in the rough" It is a
critical skill that IETFers need to acquire. I can assure you that
being a wg chair and in the rough, when you call wg consensus is not
easy - but again it has nothing to do with percentage.

/Loa

On 2012-08-29 10:33, Andrew G. Malis wrote:
> Just on a practical matter, many of us WG chairs like to get the
> minutes uploaded as quickly as possible, before the blue sheet numbers
> are available. Like John, I fail to see the value of recording the
> number of people sitting in chairs, except to size the room for the
> next meeting. One of the most productive WGs I ever participated in
> usually had fewer than 10 people at a meeting, but every single one of
> those people contributed to the documents.
>
> Regarding consensus, that's a different matter altogether, and one you
> didn't mention in your original email. In most WGs (certainly in
> mine), consensus is not determined in the meeting, but on the list. In
> the minutes, we'll sometimes report on the "sense of the room", but
> it's nothing more than that.
>
> Cheers,
> Andy
>
> On Wed, Aug 29, 2012 at 11:12 AM, Abdussalam Baryun
> <abdussalambaryun@gmail.com> wrote:
>> Hi John,
>>
>> Thanks for your advise and comments. I prefered that consensus is
>> documented to know its value/level as was it 60% or 70% or 80%...etc.
>> How do Chairs in IETF decide on the agree/disagree/no-reply from WGs
>>
>>   " Note that 51% of the working group does not qualify as "rough consensus" and
>>     99% is better than rough.  It is up to the Chair to determine if rough
>>    consensus has been reached."
>>
>> I see that minutes just mention WG agreed to ..., but would suggest
>> the value, so it does not become below 51%. Also, most participants
>> need more time to decide on such request from Chairs because they use
>> their variable-available-volunteering time to do reading/work within
>> each 28 days.
>>
>> Regards
>> AB
>> ---
>> On 8/28/12, John C Klensin <john-ietf@jck.com> wrote:
>>>
>>>
>>> --On Tuesday, August 28, 2012 11:17 +0100 Abdussalam Baryun
>>> <abdussalambaryun@gmail.com> wrote:
>>>
>>>> Hi
>>>>
>>>> Reading through some IETF WGs minutes of meetings, is it
>>>> possible that we follow a procedure in writting minutes.
>>>> I think the following items are important that SHOULD be
>>>> included:
>>>>
>>>> 1) name of the chair, minute taker, and jabber reader.
>>>> 2) number of participant in the meeting room.
>>>> 3) number of participants at jabber.
>>>
>>> It seems to me that the latter two would fall somewhere between
>>> "useless" and "misleading".  I don't have any idea how to count
>>> "participants" in the meeting room.  The only numbers that are
>>> reasonably easy to capture are the number of people who signed
>>> the blue sheets, but that doesn't capture either non-signers or
>>> those who sign and then sit in the room and pay more attention
>>> to email or other topics than the meeting.  If we used the
>>> number of people signed into Jabber for anything, we'd create a
>>> count that was extremely easy to pack as well as not
>>> distinguishing between people who were on Jabber but in the
>>> room, on Jabber but elsewhere at the IETF meeting (conflicts or
>>> couldn't be bothered to attend), remote and actively following
>>> the meeting, or others (and there are likely to be some others).
>>>
>>> I could see somewhat more value if actual names and
>>> organizational affiliations were listed, but the community has
>>> (for plausible reasons, IMO) decided to not do that.
>>>
>>> This is just a personal opinion/request, but I would really
>>> appreciate it if you (or others making procedural
>>> suggestions/requests like this) would carefully think through
>>> the implications of what they are asking for and how the
>>> information would be used before making the request.  It would
>>> be even better if you then included an explanation of the value
>>> that you think would occur, and maybe the tradeoffs you see,
>>> with the request, not just "is it possible that we follow a
>>> procedure...".
>>>
>>> That would have an advantage for you too because such
>>> suggestions are more likely to be taken seriously by more people
>>> in the IETF rather than, in the extreme case, going unread
>>> because you have developed a history of bad and/or unjustified
>>> ideas.
>>>
>>> regards,
>>>     john
>>>
>>>
>>>

-- 


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 jnc@mercury.lcs.mit.edu  Wed Aug 29 02:54:03 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9967D21F84D8 for <ietf@ietfa.amsl.com>; Wed, 29 Aug 2012 02:54:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.351
X-Spam-Level: 
X-Spam-Status: No, score=-6.351 tagged_above=-999 required=5 tests=[AWL=0.248,  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 QkgBXvefR4vo for <ietf@ietfa.amsl.com>; Wed, 29 Aug 2012 02:54:03 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 0DC8921F84A2 for <ietf@ietf.org>; Wed, 29 Aug 2012 02:54:02 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 0D51E18C0B9; Wed, 29 Aug 2012 05:54:02 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Leading Global Standards Organizations Endorse 'OpenStand' Principles that Drive Innovation and Borderless Commerce
Message-Id: <20120829095402.0D51E18C0B9@mercury.lcs.mit.edu>
Date: Wed, 29 Aug 2012 05:54:02 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Aug 2012 09:54:03 -0000

    > From: Stephane Bortzmeyer <bortzmeyer@nic.fr>

    > I strongly regret that "Commerce" has a specific mention, among all the
    > other uses of the Internet. The network is not only open for business!

I hear you, but unless the Internet were a money-making system it would not
have grown as quickly, or as large. So I think it's OK to make that one
'primus inter pares'.

	Noel

From vesely@tana.it  Wed Aug 29 06:12:03 2012
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C58B811E80D1 for <ietf@ietfa.amsl.com>; Wed, 29 Aug 2012 06:11:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.719
X-Spam-Level: 
X-Spam-Status: No, score=-4.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lO2mvnyAjgAF for <ietf@ietfa.amsl.com>; Wed, 29 Aug 2012 06:11:50 -0700 (PDT)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 68FE211E809A for <ietf@ietf.org>; Wed, 29 Aug 2012 06:11:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1346245909; bh=ESgsme5M4nRUbVioO/at6giRPSdibE/QauCYUKgEZlc=; l=602; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=W9Z7XOCf0JidNMrefgrnyr3+ozD+hsOOXxworAPS2fe3RiUefUobPXmV1ubmC1BJg 33Mz77jJ2z/2MAXUL2crJEy+yXskJyaLJCAe5CjoBKRnRvKUNo4ucjtRDwCxRGfzFZ YuIZzJcoGX1yGL7lH/C+DZ1f72fpErinYrJDIBa4=
Received: from [37.159.123.133] ([37.159.123.133]) (AUTH: PLAIN 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Wed, 29 Aug 2012 15:11:48 +0200 id 00000000005DC039.00000000503E1514.0000637F
Message-ID: <503E150F.9040804@tana.it>
Date: Wed, 29 Aug 2012 15:11:43 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Leading Global Standards Organizations Endorse 'OpenStand' Principles that Drive Innovation and Borderless Commerce
References: <20120829095402.0D51E18C0B9@mercury.lcs.mit.edu>
In-Reply-To: <20120829095402.0D51E18C0B9@mercury.lcs.mit.edu>
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, 29 Aug 2012 13:12:03 -0000

On Wed 29/Aug/2012 11:54:02 +0200 Noel Chiappa wrote:
>> From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
> 
>> I strongly regret that "Commerce" has a specific mention, among all the
>> other uses of the Internet. The network is not only open for business!
> 
> I hear you, but unless the Internet were a money-making system it would not
> have grown as quickly, or as large.  So I think it's OK to make that one
> 'primus inter pares'.

Not 'secundus'?  If we were looking at what makes it grow so quickly
and large, I would have said that free/open source software deserved a
special mention.


From ajs@anvilwalrusden.com  Wed Aug 29 07:14:27 2012
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 A5C0F21F84C4 for <ietf@ietfa.amsl.com>; Wed, 29 Aug 2012 07:14:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xsiu7WAxG4pc for <ietf@ietfa.amsl.com>; Wed, 29 Aug 2012 07:14:27 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 1E53821F84A2 for <ietf@ietf.org>; Wed, 29 Aug 2012 07:14:26 -0700 (PDT)
Received: from mx1.yitter.info (unknown [205.201.170.136]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 6E0B18A031 for <ietf@ietf.org>; Wed, 29 Aug 2012 14:14:25 +0000 (UTC)
Date: Wed, 29 Aug 2012 10:14:18 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Minutes SHOULD include participants number
Message-ID: <20120829141418.GA54316@mx1.yitter.info>
References: <CADnDZ8_uDPiqh+nD6VwUB-S5jQM6A_KrLCs6rv=793qbY=-RXQ@mail.gmail.com> <2F3D65048BFCBB6AF7F2C91D@JcK-HP8200.jck.com> <CADnDZ8-2MbzQv7hZEOxka92hDSe2Ofyb2ThFTqr03UsLw84nBA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CADnDZ8-2MbzQv7hZEOxka92hDSe2Ofyb2ThFTqr03UsLw84nBA@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, 29 Aug 2012 14:14:27 -0000

On Wed, Aug 29, 2012 at 10:12:26AM +0200, Abdussalam Baryun wrote:
> documented to know its value/level as was it 60% or 70% or 80%...etc.

That's impossible to answer.  We don't do voting.

> How do Chairs in IETF decide on the agree/disagree/no-reply from WGs

We use our judgement.  That's why we are paid so well by the IETF.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From sm@resistor.net  Wed Aug 29 08:06:31 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5C4121F86B7 for <ietf@ietfa.amsl.com>; Wed, 29 Aug 2012 08:06:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.491
X-Spam-Level: 
X-Spam-Status: No, score=-102.491 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SxZlqJoP74Mi for <ietf@ietfa.amsl.com>; Wed, 29 Aug 2012 08:06:29 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 577EA21F8596 for <ietf@ietf.org>; Wed, 29 Aug 2012 08:06:29 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q7TF66Rg014744; Wed, 29 Aug 2012 08:06:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1346252773; bh=BX7TUGpfRXlQ5T6NuKv0BkhxfEaUq4Tf9tCSFeNKAZA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=yyJfCgtwEdXsryFVDmnYB161S79g63hTW6MfmsYhaG7+kBKaO8KtmIuq1FWHJRn6z t/vJs1lBwG2NG/Gi7Q/grkMMfn9kOs9t7HzVx6M4bOtcBQRtpH5Ps3irrWKvej/qlK KP8M7bT4aZ2rk88Zg7xz2WBAskBjrAm0CcjzplUQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1346252773; i=@resistor.net; bh=BX7TUGpfRXlQ5T6NuKv0BkhxfEaUq4Tf9tCSFeNKAZA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=wUSLqAEpORA9Zg/H5E+Cu+2L2FvIm1WR7m88eSWui31pnttwZkcuDaktOvqEb1xV/ 2tTLiUE1SdiBQdm2Or3aHsfzuF9dmVoNQffwMdL4b7LUSqCnoIeYsSpSBRMl6NjTgL rD6gsB9a5Jth4WsqD8G8+fNJxVKPmuCUFlzqZM3s=
Message-Id: <6.2.5.6.2.20120829060235.08d8fa38@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 29 Aug 2012 07:51:00 -0700
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Minutes SHOULD include participants number
In-Reply-To: <CADnDZ8-2MbzQv7hZEOxka92hDSe2Ofyb2ThFTqr03UsLw84nBA@mail.g mail.com>
References: <CADnDZ8_uDPiqh+nD6VwUB-S5jQM6A_KrLCs6rv=793qbY=-RXQ@mail.gmail.com> <2F3D65048BFCBB6AF7F2C91D@JcK-HP8200.jck.com> <CADnDZ8-2MbzQv7hZEOxka92hDSe2Ofyb2ThFTqr03UsLw84nBA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Aug 2012 15:06:31 -0000

At 01:12 29-08-2012, Abdussalam Baryun wrote:
>Thanks for your advise and comments. I prefered that consensus is
>documented to know its value/level as was it 60% or 70% or 80%...etc.

There isn't any percentage for consensus.

>How do Chairs in IETF decide on the agree/disagree/no-reply from WGs

[snip]

>I see that minutes just mention WG agreed to ..., but would suggest

"agreed" does not necessarily means a significant 
decision.  Decisions are taken on the mailing list anyway.

>the value, so it does not become below 51%. Also, most participants
>need more time to decide on such request from Chairs because they use
>their variable-available-volunteering time to do reading/work within
>each 28 days.

It is generally the wrong question if participants have to think 
really hard about the answer.  The decision is not written in stone anyway.

You asked an interesting question.  However, your previous message 
was framed in such a way that most people would ignore it.

You want people to agree or disagree.  A "no reply" generally 
translates into lack of interest or not enough information to take a 
decision.  You also want to be sure that participants fully 
understand what they are agreeing or disagreeing to.  There is a 
responsible Area Director in the room to perform a sanity check.

Regards,
-sm 


From lberger@labn.net  Thu Aug 30 07:25:28 2012
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 A532B21F8661 for <ietf@ietfa.amsl.com>; Thu, 30 Aug 2012 07:25:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.39
X-Spam-Level: 
X-Spam-Status: No, score=-99.39 tagged_above=-999 required=5 tests=[AWL=0.771,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  IP_NOT_FRIENDLY=0.334, 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 ChWLHqvoOsVi for <ietf@ietfa.amsl.com>; Thu, 30 Aug 2012 07:25:27 -0700 (PDT)
Received: from oproxy6-pub.bluehost.com (oproxy6.bluehost.com [IPv6:2605:dc00:100:2::a6]) by ietfa.amsl.com (Postfix) with SMTP id 6F61921F8671 for <ietf@ietf.org>; Thu, 30 Aug 2012 07:25:21 -0700 (PDT)
Received: (qmail 32682 invoked by uid 0); 30 Aug 2012 14:25:19 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by cpoproxy3.bluehost.com with SMTP; 30 Aug 2012 14:25:19 -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=jQkBnWbrQPBLdJc3dscCVkC2FPzoVRJcmGFZQOu6+UU=;  b=GIMXVLTBe2ZCQIqj7tQzsE3z6OPQ/nUVwoJT2MPo/bUjTDD8ysxi4pvVt2ttVdcQz/H7VGvqLXkvVFRWIqnHRpQJTYTjzUBs+cJ64sRF2MGlpDId8vhJ659mBM/VsaUn;
Received: from box313.bluehost.com ([69.89.31.113]:57967 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.76) (envelope-from <lberger@labn.net>) id 1T75gN-00024h-FN; Thu, 30 Aug 2012 08:25:19 -0600
Message-ID: <503F77CF.1080005@labn.net>
Date: Thu, 30 Aug 2012 10:25:19 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: Peter Yee <peter@akayla.com>
Subject: Re: Gen-ART review of draft-ietf-ccamp-assoc-ext-04
References: <005e01cd865f$e9035fe0$bb0a1fa0$@akayla.com>
In-Reply-To: <005e01cd865f$e9035fe0$bb0a1fa0$@akayla.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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: draft-ietf-ccamp-assoc-ext.all@tools.ietf.org, gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Aug 2012 14:25:28 -0000

Peter,
	Thank you for the comments.  Please see below for responses in-line.


On 8/29/2012 11:31 PM, Peter Yee 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>
>
> Document: draft-ietf-ccamp-assoc-ext-04
> Reviewer: Peter Yee
> Review Date: Aug-28-2012
> IETF LC End Date: Aug-29-2012
> IESG Telechat date: Not known
>
> Summary: This draft is basically ready for publication, but has nits that
> should be
> fixed before publication. [Ready with nits.]
>
> This document provides extensions to the scope of use of the RSVP
> ASSOCIATION
> object as well as providing an extended ASSOCIATION object capable of
> handling
> a longer Association ID.
>
> Nits:
>
> In the last example (Symmetric NAT), last sentence: "mechanisms" ->
> "mechanism".
>
> Section 2, 4th paragraph (the replacement text): "the the" -> "the".
>
> Section 3.2.1, 2nd paragraph, 1st sentence: "are" -> "is".  Alternatively,
> you
> could change "format" to "formats".
>
> Section 3.2.2, 1st sentence: "apply" -> "applies".
>
> Section 4.2, 1st sentence: "a" -> "an" in both occurrences.
>
> Section 4.2, last paragraph, 2nd sentence: "a" -> "an".
>

Thank you!

> Questions:
>
> These are questions you may wish to answer but the draft is acceptable
> without response:
>
> 1) In Section 4.2, 4th bullet, is there any implied relationship between the
> Extended Association ID and the Association ID?  Or are they independent
> values that simply must be matched?

The latter (as the text says.)

>
> 2) Section 4.2, 5th bullet, you make a first and only mention of padding
> bytes.
> Are you using a specific method for generating these padding bytes or are
> they random?

No, as it is completely up to the creator of the object to use it 
consistently.

> Given the matching requirement on ASSOCIATION objects,
> it might be best to specify the padding generation so that if the object is
> regenerated, it will still be matched by intermediary nodes.  I've presumed
> that the padding bytes are for meeting the 4-byte multiple requirement,
> but I don't know if implementations would ever be free to regenerate the
> object for subsequent transmissions of that object.

I'll add ", without modification," to the last sentence of 3.1.2 and 3.2.2.

Thank you for the comments!

Lou

From lberger@labn.net  Thu Aug 30 07:27:41 2012
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 563BC21F8670 for <ietf@ietfa.amsl.com>; Thu, 30 Aug 2012 07:27:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.409
X-Spam-Level: 
X-Spam-Status: No, score=-99.409 tagged_above=-999 required=5 tests=[AWL=0.752, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, IP_NOT_FRIENDLY=0.334, 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 76cvsPT8Atch for <ietf@ietfa.amsl.com>; Thu, 30 Aug 2012 07:27:38 -0700 (PDT)
Received: from oproxy11-pub.bluehost.com (unknown [IPv6:2605:dc00:100:2::a3]) by ietfa.amsl.com (Postfix) with SMTP id CF2E521F866A for <ietf@ietf.org>; Thu, 30 Aug 2012 07:27:37 -0700 (PDT)
Received: (qmail 23272 invoked by uid 0); 30 Aug 2012 14:27:36 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy11.bluehost.com with SMTP; 30 Aug 2012 14:27:36 -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=7ptoClnr672/RDznRSIN0sfuNpDTY8VGYIT3ri3U/xU=;  b=RzfZ30ivqsABUR6Ip3Ea9lV08VtoRgksAsI3A4gg/GLVPffWjxZMLN4P1oI78AiM0+6laVOuD062/hh2jHU+pLGHIGdXrk/2weAKjBNfK8qdwXeE/qz/ZjnCUPBsg2fz;
Received: from box313.bluehost.com ([69.89.31.113]:58175 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.76) (envelope-from <lberger@labn.net>) id 1T75iZ-0002kf-E6; Thu, 30 Aug 2012 08:27:35 -0600
Message-ID: <503F7857.3070905@labn.net>
Date: Thu, 30 Aug 2012 10:27:35 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: Adrian Farrel <adrian@olddog.co.uk>
Subject: Fwd: Re: Gen-ART review of draft-ietf-ccamp-assoc-ext-04
References: <503F77CF.1080005@labn.net>
In-Reply-To: <503F77CF.1080005@labn.net>
X-Forwarded-Message-Id: <503F77CF.1080005@labn.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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: draft-ietf-ccamp-assoc-ext.all@tools.ietf.org, gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Aug 2012 14:27:42 -0000

Adrian,
     Shout (or change the ID state) when you're ready for the update to 
be submitted.

Thanks,
Lou
-------- Original Message --------
Subject: 	Re: Gen-ART review of draft-ietf-ccamp-assoc-ext-04
Date: 	Thu, 30 Aug 2012 10:25:19 -0400
From: 	Lou Berger <lberger@labn.net>
To: 	Peter Yee <peter@akayla.com>
CC: 	draft-ietf-ccamp-assoc-ext.all@tools.ietf.org, gen-art@ietf.org, 
ietf@ietf.org



Peter,
	Thank you for the comments.  Please see below for responses in-line.


On 8/29/2012 11:31 PM, Peter Yee 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>
>
> Document: draft-ietf-ccamp-assoc-ext-04
> Reviewer: Peter Yee
> Review Date: Aug-28-2012
> IETF LC End Date: Aug-29-2012
> IESG Telechat date: Not known
>
> Summary: This draft is basically ready for publication, but has nits that
> should be
> fixed before publication. [Ready with nits.]
>
> This document provides extensions to the scope of use of the RSVP
> ASSOCIATION
> object as well as providing an extended ASSOCIATION object capable of
> handling
> a longer Association ID.
>
> Nits:
>
> In the last example (Symmetric NAT), last sentence: "mechanisms" ->
> "mechanism".
>
> Section 2, 4th paragraph (the replacement text): "the the" -> "the".
>
> Section 3.2.1, 2nd paragraph, 1st sentence: "are" -> "is".  Alternatively,
> you
> could change "format" to "formats".
>
> Section 3.2.2, 1st sentence: "apply" -> "applies".
>
> Section 4.2, 1st sentence: "a" -> "an" in both occurrences.
>
> Section 4.2, last paragraph, 2nd sentence: "a" -> "an".
>

Thank you!

> Questions:
>
> These are questions you may wish to answer but the draft is acceptable
> without response:
>
> 1) In Section 4.2, 4th bullet, is there any implied relationship between the
> Extended Association ID and the Association ID?  Or are they independent
> values that simply must be matched?

The latter (as the text says.)

>
> 2) Section 4.2, 5th bullet, you make a first and only mention of padding
> bytes.
> Are you using a specific method for generating these padding bytes or are
> they random?

No, as it is completely up to the creator of the object to use it
consistently.

> Given the matching requirement on ASSOCIATION objects,
> it might be best to specify the padding generation so that if the object is
> regenerated, it will still be matched by intermediary nodes.  I've presumed
> that the padding bytes are for meeting the 4-byte multiple requirement,
> but I don't know if implementations would ever be free to regenerate the
> object for subsequent transmissions of that object.

I'll add ", without modification," to the last sentence of 3.1.2 and 3.2.2.

Thank you for the comments!

Lou





From adrian@olddog.co.uk  Thu Aug 30 07:49:02 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45AFE21F8607; Thu, 30 Aug 2012 07:49:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lomJ1D-VYkwc; Thu, 30 Aug 2012 07:49:01 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 5A70521F8610; Thu, 30 Aug 2012 07:49:01 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7UEmx6g019133;  Thu, 30 Aug 2012 15:48:59 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7UEmtDP018970 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 30 Aug 2012 15:48:59 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Lou Berger'" <lberger@labn.net>
References: <503F77CF.1080005@labn.net> <503F7857.3070905@labn.net>
In-Reply-To: <503F7857.3070905@labn.net>
Subject: RE: Re: Gen-ART review of draft-ietf-ccamp-assoc-ext-04
Date: Thu, 30 Aug 2012 15:48:55 +0100
Message-ID: <20fa01cd86be$971b0110$c5510330$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQI1ZC8sJg8zIh0e8RXzbgNx+W88rQGw6RY+lpUs79A=
Content-Language: en-gb
Cc: draft-ietf-ccamp-assoc-ext.all@tools.ietf.org, gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Aug 2012 14:49:02 -0000

thnx

I was hoping for a routing directorate review (Dimitri) but it hasn't showed

Give it a couple of days and then we will move on w/o it. If the review comes in
late we will cross the bridge.

Aiming for telechat on 9/13

A

> -----Original Message-----
> From: Lou Berger [mailto:lberger@labn.net]
> Sent: 30 August 2012 15:28
> To: Adrian Farrel
> Cc: draft-ietf-ccamp-assoc-ext.all@tools.ietf.org; gen-art@ietf.org;
ietf@ietf.org
> Subject: Fwd: Re: Gen-ART review of draft-ietf-ccamp-assoc-ext-04
> 
> 
> 
> Adrian,
>      Shout (or change the ID state) when you're ready for the update to
> be submitted.
> 
> Thanks,
> Lou
> -------- Original Message --------
> Subject: 	Re: Gen-ART review of draft-ietf-ccamp-assoc-ext-04
> Date: 	Thu, 30 Aug 2012 10:25:19 -0400
> From: 	Lou Berger <lberger@labn.net>
> To: 	Peter Yee <peter@akayla.com>
> CC: 	draft-ietf-ccamp-assoc-ext.all@tools.ietf.org, gen-art@ietf.org,
> ietf@ietf.org
> 
> 
> 
> Peter,
> 	Thank you for the comments.  Please see below for responses in-line.
> 
> 
> On 8/29/2012 11:31 PM, Peter Yee 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>
> >
> > Document: draft-ietf-ccamp-assoc-ext-04
> > Reviewer: Peter Yee
> > Review Date: Aug-28-2012
> > IETF LC End Date: Aug-29-2012
> > IESG Telechat date: Not known
> >
> > Summary: This draft is basically ready for publication, but has nits that
> > should be
> > fixed before publication. [Ready with nits.]
> >
> > This document provides extensions to the scope of use of the RSVP
> > ASSOCIATION
> > object as well as providing an extended ASSOCIATION object capable of
> > handling
> > a longer Association ID.
> >
> > Nits:
> >
> > In the last example (Symmetric NAT), last sentence: "mechanisms" ->
> > "mechanism".
> >
> > Section 2, 4th paragraph (the replacement text): "the the" -> "the".
> >
> > Section 3.2.1, 2nd paragraph, 1st sentence: "are" -> "is".  Alternatively,
> > you
> > could change "format" to "formats".
> >
> > Section 3.2.2, 1st sentence: "apply" -> "applies".
> >
> > Section 4.2, 1st sentence: "a" -> "an" in both occurrences.
> >
> > Section 4.2, last paragraph, 2nd sentence: "a" -> "an".
> >
> 
> Thank you!
> 
> > Questions:
> >
> > These are questions you may wish to answer but the draft is acceptable
> > without response:
> >
> > 1) In Section 4.2, 4th bullet, is there any implied relationship between the
> > Extended Association ID and the Association ID?  Or are they independent
> > values that simply must be matched?
> 
> The latter (as the text says.)
> 
> >
> > 2) Section 4.2, 5th bullet, you make a first and only mention of padding
> > bytes.
> > Are you using a specific method for generating these padding bytes or are
> > they random?
> 
> No, as it is completely up to the creator of the object to use it
> consistently.
> 
> > Given the matching requirement on ASSOCIATION objects,
> > it might be best to specify the padding generation so that if the object is
> > regenerated, it will still be matched by intermediary nodes.  I've presumed
> > that the padding bytes are for meeting the 4-byte multiple requirement,
> > but I don't know if implementations would ever be free to regenerate the
> > object for subsequent transmissions of that object.
> 
> I'll add ", without modification," to the last sentence of 3.1.2 and 3.2.2.
> 
> Thank you for the comments!
> 
> Lou
> 
> 



From lberger@labn.net  Thu Aug 30 07:58:07 2012
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 5A9C721F851A for <ietf@ietfa.amsl.com>; Thu, 30 Aug 2012 07:58:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.426
X-Spam-Level: 
X-Spam-Status: No, score=-99.426 tagged_above=-999 required=5 tests=[AWL=0.735, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, IP_NOT_FRIENDLY=0.334, 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 PWbGjSiNjpXS for <ietf@ietfa.amsl.com>; Thu, 30 Aug 2012 07:58:06 -0700 (PDT)
Received: from oproxy6-pub.bluehost.com (oproxy6.bluehost.com [IPv6:2605:dc00:100:2::a6]) by ietfa.amsl.com (Postfix) with SMTP id 607B121F84C9 for <ietf@ietf.org>; Thu, 30 Aug 2012 07:58:06 -0700 (PDT)
Received: (qmail 17788 invoked by uid 0); 30 Aug 2012 14:58:05 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by cpoproxy3.bluehost.com with SMTP; 30 Aug 2012 14:58:05 -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=lB8FsGTzYwD2luv33h+mULijVBFzJURM6SjeDTWnkVA=;  b=fJA6vMJ5u8/BIIYSFsANBozw4RWMh2hvG7BE7Pky0TjwFoysKxtYolIbQP8HgERKu++ZAuFEwME1UhSWA2DDe++dQjoQQoTyIzP9D5tfPYI3fw3ahjQARuvUW6hL7/W5;
Received: from box313.bluehost.com ([69.89.31.113]:32973 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.76) (envelope-from <lberger@labn.net>) id 1T76C5-0005fU-GM; Thu, 30 Aug 2012 08:58:05 -0600
Message-ID: <503F7F7D.8080404@labn.net>
Date: Thu, 30 Aug 2012 10:58:05 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: Adrian Farrel <adrian@olddog.co.uk>, ietf@ietf.org
Subject: Re: Fwd: Re: Gen-ART review of draft-ietf-ccamp-assoc-ext-04
References: <503F77CF.1080005@labn.net> <503F7857.3070905@labn.net>
In-Reply-To: <503F7857.3070905@labn.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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: draft-ietf-ccamp-assoc-ext.all@tools.ietf.org, gen-art@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Aug 2012 14:58:07 -0000

Eek,
     I somehow managed to broadcast this!  My apologies.

Lou

On 8/30/2012 10:27 AM, Lou Berger wrote:
>
> Adrian,
>       Shout (or change the ID state) when you're ready for the update to
> be submitted.
>
> Thanks,
> Lou
> -------- Original Message --------
> Subject: 	Re: Gen-ART review of draft-ietf-ccamp-assoc-ext-04
> Date: 	Thu, 30 Aug 2012 10:25:19 -0400
> From: 	Lou Berger <lberger@labn.net>
> To: 	Peter Yee <peter@akayla.com>
> CC: 	draft-ietf-ccamp-assoc-ext.all@tools.ietf.org, gen-art@ietf.org,
> ietf@ietf.org
>
>
>
> Peter,
> 	Thank you for the comments.  Please see below for responses in-line.
>
>
> On 8/29/2012 11:31 PM, Peter Yee 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>
>>
>> Document: draft-ietf-ccamp-assoc-ext-04
>> Reviewer: Peter Yee
>> Review Date: Aug-28-2012
>> IETF LC End Date: Aug-29-2012
>> IESG Telechat date: Not known
>>
>> Summary: This draft is basically ready for publication, but has nits that
>> should be
>> fixed before publication. [Ready with nits.]
>>
>> This document provides extensions to the scope of use of the RSVP
>> ASSOCIATION
>> object as well as providing an extended ASSOCIATION object capable of
>> handling
>> a longer Association ID.
>>
>> Nits:
>>
>> In the last example (Symmetric NAT), last sentence: "mechanisms" ->
>> "mechanism".
>>
>> Section 2, 4th paragraph (the replacement text): "the the" -> "the".
>>
>> Section 3.2.1, 2nd paragraph, 1st sentence: "are" -> "is".  Alternatively,
>> you
>> could change "format" to "formats".
>>
>> Section 3.2.2, 1st sentence: "apply" -> "applies".
>>
>> Section 4.2, 1st sentence: "a" -> "an" in both occurrences.
>>
>> Section 4.2, last paragraph, 2nd sentence: "a" -> "an".
>>
> Thank you!
>
>> Questions:
>>
>> These are questions you may wish to answer but the draft is acceptable
>> without response:
>>
>> 1) In Section 4.2, 4th bullet, is there any implied relationship between the
>> Extended Association ID and the Association ID?  Or are they independent
>> values that simply must be matched?
> The latter (as the text says.)
>
>> 2) Section 4.2, 5th bullet, you make a first and only mention of padding
>> bytes.
>> Are you using a specific method for generating these padding bytes or are
>> they random?
> No, as it is completely up to the creator of the object to use it
> consistently.
>
>> Given the matching requirement on ASSOCIATION objects,
>> it might be best to specify the padding generation so that if the object is
>> regenerated, it will still be matched by intermediary nodes.  I've presumed
>> that the padding bytes are for meeting the 4-byte multiple requirement,
>> but I don't know if implementations would ever be free to regenerate the
>> object for subsequent transmissions of that object.
> I'll add ", without modification," to the last sentence of 3.1.2 and 3.2.2.
>
> Thank you for the comments!
>
> Lou
>
>
>
>


From narten@us.ibm.com  Thu Aug 30 21:53:08 2012
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E5A021F84EC for <ietf@ietfa.amsl.com>; Thu, 30 Aug 2012 21:53:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B+MzZ6i1qRJl for <ietf@ietfa.amsl.com>; Thu, 30 Aug 2012 21:53:07 -0700 (PDT)
Received: from e33.co.us.ibm.com (e33.co.us.ibm.com [32.97.110.151]) by ietfa.amsl.com (Postfix) with ESMTP id A3FBB21F84E6 for <ietf@ietf.org>; Thu, 30 Aug 2012 21:53:07 -0700 (PDT)
Received: from /spool/local by e33.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 30 Aug 2012 22:53:06 -0600
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e33.co.us.ibm.com (192.168.1.133) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 30 Aug 2012 22:53:05 -0600
Received: from d03relay01.boulder.ibm.com (d03relay01.boulder.ibm.com [9.17.195.226]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 078621FF0039 for <ietf@ietf.org>; Thu, 30 Aug 2012 22:53:04 -0600 (MDT)
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay01.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q7V4r43G186338 for <ietf@ietf.org>; Thu, 30 Aug 2012 22:53:04 -0600
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q7V4r4sn021856 for <ietf@ietf.org>; Thu, 30 Aug 2012 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q7V4r3t0021804 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 30 Aug 2012 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q7V4r26N025234 for <ietf@ietf.org>; Fri, 31 Aug 2012 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q7V4r2po025187 for ietf@ietf.org; Fri, 31 Aug 2012 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201208310453.q7V4r2po025187@rotala.raleigh.ibm.com>
Date: Fri, 31 Aug 2012 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-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12083104-2398-0000-0000-000009F4C46C
X-IBM-ISS-SpamDetectors: 
X-IBM-ISS-DetailInfo: BY=3.00000293; HX=3.00000196; KW=3.00000007; PH=3.00000001; SC=3.00000007; SDB=6.00169982; UDB=6.00038538; UTC=2012-08-31 04:53:06
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Aug 2012 04:53:08 -0000

Total of 24 messages in the last 7 days.
 
script run at: Fri Aug 31 00:53:02 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 16.67% |    4 | 21.25% |    38527 | abdussalambaryun@gmail.com
 12.50% |    3 | 14.71% |    26664 | chair@ietf.org
 12.50% |    3 | 13.45% |    24383 | lberger@labn.net
  8.33% |    2 |  8.07% |    14630 | adrian@olddog.co.uk
  8.33% |    2 |  6.30% |    11430 | bortzmeyer@nic.fr
  4.17% |    1 |  5.36% |     9722 | loa@pi.nu
  4.17% |    1 |  5.09% |     9227 | agmalis@gmail.com
  4.17% |    1 |  4.57% |     8288 | narten@us.ibm.com
  4.17% |    1 |  3.69% |     6694 | john-ietf@jck.com
  4.17% |    1 |  3.68% |     6667 | sm@resistor.net
  4.17% |    1 |  3.07% |     5557 | vesely@tana.it
  4.17% |    1 |  3.00% |     5446 | ben@nostrum.com
  4.17% |    1 |  2.78% |     5033 | ajs@anvilwalrusden.com
  4.17% |    1 |  2.49% |     4519 | iesg-secretary@ietf.org
  4.17% |    1 |  2.48% |     4501 | jnc@mercury.lcs.mit.edu
--------+------+--------+----------+------------------------
100.00% |   24 |100.00% |   181288 | Total


From Chris.Dearlove@baesystems.com  Fri Aug 31 01:58:49 2012
Return-Path: <Chris.Dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7BC221F8568; Fri, 31 Aug 2012 01:58:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.367
X-Spam-Level: 
X-Spam-Status: No, score=-10.367 tagged_above=-999 required=5 tests=[AWL=0.232, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LCIvlgT1K9WB; Fri, 31 Aug 2012 01:58:49 -0700 (PDT)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) by ietfa.amsl.com (Postfix) with ESMTP id 7FF4721F855F; Fri, 31 Aug 2012 01:58:48 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.80,346,1344207600"; d="scan'208";a="267355001"
Received: from unknown (HELO baemasmds009.greenlnk.net) ([141.245.68.246]) by baemasmds003ir.sharelnk.net with ESMTP; 31 Aug 2012 09:58:47 +0100
Received: from GLKXH0003V.GREENLNK.net ([10.109.2.34]) by baemasmds009.greenlnk.net (Switch-3.4.4/Switch-3.4.4) with ESMTP id q7V8wlAO008368 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 31 Aug 2012 09:58:47 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.208]) by GLKXH0003V.GREENLNK.net ([10.109.2.34]) with mapi id 14.02.0309.002; Fri, 31 Aug 2012 09:58:47 +0100
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Comments on draft-olsrv2-manet-olsrv2-15
Thread-Topic: Comments on draft-olsrv2-manet-olsrv2-15
Thread-Index: Ac2HVcdlDq/tJeUlTLKmtRuf7Eqiiw==
Date: Fri, 31 Aug 2012 08:58:45 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24F4D0F5@GLKXM0002V.GREENLNK.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Aug 2012 08:58:50 -0000

A number of comments on draft-olsrv2-manet-olsrv2-15 were provided by Mr. A=
bdussalam Baryun. The authors have reviewed these comments and do not feel =
that they warrant any changes. (The authors do however intend to make some =
other minor changes to produce a version -16 based on other comments receiv=
ed, including directorate reviews, one of which is still outstanding.) Thei=
r summarised reasons are given below. (Note that, on the advice of their AD=
, the review comments are summarised rather than repeated in full, and the =
several emails are not replied to separately.)

Definitions of the terms interface, MANET interface and link.

Response: These terms are defined in RFC 6130 (Proposed Standard) and used =
by reference. Significant discussion went into that document and those defi=
nitions, and were accepted by the WG and the IESG.

Dimensionless link metrics.

Response: The use of the term dimensionless is to emphasise that OLSRv2 (in=
 common with other link state routing protocols) uses those link metrics as=
 numbers, using operations of addition and comparison on them. It is possib=
le that future link metric definitions (using the TLV mechanism) will defin=
e link metrics based on dimensioned quantities (e.g. delay) but the actual =
link metric would then be e.g. delay divided by a reference delay (e.g. del=
ay / 1 ms, or "delay in ms").

OLSRv2 does not specify how to handle packets.

Response: Nor should/need it. RFC 5444 (Proposed Standard) defines in Appen=
dix A (which is required to be used by RFC 5498 (Proposed Standard) when us=
ing the manet port/protocol, as called up by OLSRv2) how packets are handle=
d by a multiplexing process, and the role of a protocols (e.g. OLSRv2) is l=
imited to messages and to limited packet-related permissions (in particular=
 to add TLVs to the packet header), but a protocol is not permitted to hand=
le the packet as a whole. However OLSRv2 does not exercise even its RFC 544=
4 granted packet related permissions, as it has no need to.

OLSRv2 specifies that updating the IP routing table is out of scope.

Response: OLSRv2 specifies that the intent of its collected information is =
to update IP's routing table, but the exact mechanism by which this may be =
done (e.g. Linux system calls, equivalent on Windows, etc.) is an implement=
ation issue that this, as indicated, outside the scope of this protocol, an=
d to include it would be a layer violation.

Is NHDP a must for OLSRv2?

Response: As the WG has chosen to specify the protocol, yes, it is. (A hist=
orical note is that NHDP was actually created as part of OLSRv2, it was spl=
it off as a separate specification because other uses were identified for N=
HDP.)

Comment on link metrics.

Response: The authors were unable to establish the exact significance of th=
e comment that OLSRv2 may have more applicability. The authors would not di=
sagree that more uses of any protocol can often be found, but the specified=
 application (to mobile ad hoc networks) is a defined area, for which the W=
G is chartered and for which the protocol was designed. Wider applicability=
 of OLSRv2 might be an interesting topic, but it would probably be out of s=
cope of the MANET WG.

--=20
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687



********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From abdussalambaryun@gmail.com  Fri Aug 31 07:56:29 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE16E21F865B; Fri, 31 Aug 2012 07:56:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.389
X-Spam-Level: 
X-Spam-Status: No, score=-3.389 tagged_above=-999 required=5 tests=[AWL=-0.017, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gTAqpV7CgpM7; Fri, 31 Aug 2012 07:56:28 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 180CA21F863C; Fri, 31 Aug 2012 07:56:28 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so3750013vbb.31 for <multiple recipients>; Fri, 31 Aug 2012 07:56:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=gwa+/pjKmHt6o+2VBRQ+DRBmLjjDlY4CG9EawJcEUnM=; b=Gga34wu/HVby6r0m2rVtNmRNWjHvHuagqFIHbNFs2r4IGkjyNrZzhRJ+sr3c0YRtqn xMr9Uw+8P1doBgpDlezrrqTQfUoSNQ0+i5yRXEj1RkI/gWv5Ozjb6yhDPbs4Thuvseyf 7ZOHQUNec6fdx+b7atNP8hLOKi5Xo7tPYZKJFjJJq3Y2BViLpLD41FdPfdRrSf/lytv9 n9PJFNpg97KbOjT0FyWlArzcIr0n3WzKHYznVEvgta8v635WuSXaBbG28gfPoUGKbefn iLg3pMemhFLu6dDfNRjIgzo71ILEO0cZ6lXHyPj+sXrP7hrCM7blcgsZJjr3dxyd5dNP hAcg==
MIME-Version: 1.0
Received: by 10.220.154.17 with SMTP id m17mr6144284vcw.31.1346424987491; Fri, 31 Aug 2012 07:56:27 -0700 (PDT)
Received: by 10.220.55.9 with HTTP; Fri, 31 Aug 2012 07:56:27 -0700 (PDT)
In-Reply-To: <20120830162535.30621.97129.idtracker@ietfa.amsl.com>
References: <20120830162535.30621.97129.idtracker@ietfa.amsl.com>
Date: Fri, 31 Aug 2012 16:56:27 +0200
Message-ID: <CADnDZ898deedFHczsOAsqfKbSomLi5_t05GFoe2_Y4Kap2JBHQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-grow-ops-reqs-for-bgp-error-handling-05.txt> (Operational Requirements for Enhanced Error Handling Behaviour in BGP-4) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "iesg@ietf.org" <iesg@ietf.org>
Content-Type: text/plain; charset=windows-1252
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, 31 Aug 2012 14:56:30 -0000

Reply to your request dated 30/08/2012
Draft Reviewed By: Abdussalam Baryun (AB)   Dated: 31/08/2012

Reviewer Comment AB1: Editorial.
++++++++++++++++++++++++++++++++++++++++++++++++++++

Overall the reviewer felt that this Informational I-D is difficult to
read/understand. Requirement level language [RFC2119] is not used,
while this I-D discusses; *requirements* of BGP error handling.
---------------------------------------------------------------------------=
-------------------------
Page 3> Whilst a number of Internet Drafts
have been written to begin to enhance the behaviour of BGP-4 in terms
of the handling of erroneous messages,
AB> please refer to those I-Ds within the paragraph
AB> what is PE device?

Page 4> within a single sub-topology or service.
AB> what is sub-topology? Do you mean subnet or domain!

Page 4-5> Both within Internet and multi-service routing architectures, a
number of BGP sessions propagate a large proportion of the required
routing information for network operation. For Internet routing,
these are typically BGP sessions which propagate the global routing
table to an AS - failure of these sessions may have a large impact on
network service, based on a single erroneous update. In an multiservice
environment, typical deployments utilise a small number of
core-facing BGP sessions, typically towards route reflector devices.
Failure of these sessions may also result in a large impact to
network operation.

AB> BGP sessions don=92t propagate within architectures, but within network=
s.
AB> =93typically BGP sessions which propagate the global routing
Table to =85=94 not clear.
AB> amend =93In an multiservice=94 to =93In a multi-service=94
---------------------------------------------------------------------------=
----

<This is not the end of the comments>

Best Regards,
AB
---------------------------------------------------------------------------=
------------
This message and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
This message is in compliance with the IETF regulations.
---------------------------------------------------------------------------=
------------

On 8/30/12, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from the Global Routing Operations WG
> (grow) to consider the following document:
> - 'Operational Requirements for Enhanced Error Handling Behaviour in
>    BGP-4'
>   <draft-ietf-grow-ops-reqs-for-bgp-error-handling-05.txt> as
> Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-09-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
>
>
>    BGP-4 is utilised as a key intra- and inter-Autonomous System routing
>    protocol in modern IP networks.  The failure modes as defined by the
>    original protocol standards are based on a number of assumptions
>    around the impact of session failure.  Numerous incidents both in the
>    global Internet routing table and within Service Provider networks
>    have been caused by strict handling of a single invalid UPDATE
>    message causing large-scale failures in one or more Autonomous
>    Systems.
>
>    This memo describes the current use of BGP-4 within Service Provider
>    networks, and outlines a set of requirements for further work to
>    enhance the mechanisms available to a BGP-4 implementation when
>    erroneous data is detected.  Whilst this document does not provide
>    specification of any standard, it is intended as an overview of a set
>    of enhancements to BGP-4 to improve the protocol's robustness to suit
>    its current deployment.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-grow-ops-reqs-for-bgp-error-ha=
ndling/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-grow-ops-reqs-for-bgp-error-ha=
ndling/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>
